
From nobody Sun Apr  1 12:46:07 2018
Return-Path: <worley@ariadne.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 2C7A2127076; Sun,  1 Apr 2018 12:46:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-mmusic-trickle-ice-sip.all@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152261196012.23771.8619869714648947909@ietfa.amsl.com>
Date: Sun, 01 Apr 2018 12:46:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/NXCVfenpUqmwW9v9xczBwt8FH1E>
Subject: [MMUSIC] Genart telechat review of draft-ietf-mmusic-trickle-ice-sip-14
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 01 Apr 2018 19:46:00 -0000

Reviewer: Dale Worley
Review result: Ready

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

Document:  draft-ietf-mmusic-trickle-ice-sip-14
Reviewer:  Dale R. Worley
Review Date:  2018-04-01
IETF LC End Date:  2018-01-26
IESG Telechat date:  2018-04-05

Summary:

       This draft is ready for publication as a Proposed Standard RFC.

[END]



From nobody Sun Apr  1 18:05:32 2018
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 75441126C89 for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 18:05:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASyifresIjvM for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 18:05:29 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 9D3EA1243F3 for <mmusic@ietf.org>; Sun,  1 Apr 2018 18:05:29 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id y66so8419626pfi.7 for <mmusic@ietf.org>; Sun, 01 Apr 2018 18:05:29 -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=W+PfmSe92kB/ABvFugn/wSaWNZB6FKo3Q29e3tiu9Rs=; b=RN9wc31g4d9ROc2d1T24mICIhwflNCKkGKraIXUuLZpLI8g7fCxrluFOVmqxF6Odwk dHiYHMhhmaWgNQlD5fyGwt4iltUEASNxs0BqqXaO+Hgo32nQkA7DJKdIJdPSYGjPtvQj 0ZZy9HmTbkC3NWQkGSH0hR1suSC2yGNoZKASzN1Vl8phXxW9IyxDg+Ccs53b1UWOIDY1 k7FKOyUaIofvXPBozpbfaRzyE/c2QsV3/1o6WbKB1GDBbsOMkm++JjWlSux5g7nv7shp tUvB+T7sdmsT+J05o0PH0+3yVuafz4DmnRTcdH1Hr8I473l8KujJtIkANm9LsbGD10sz vMlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=W+PfmSe92kB/ABvFugn/wSaWNZB6FKo3Q29e3tiu9Rs=; b=nJ4mY9LLMDstwEN0Cz9TRqFFGuGqG52jGjn1JbPErL8Ra90QwTGnfkTrcjGgUB+nkF Q8LyZUIZE44otPpRWAWn2z0W47HkDNMmOXWkB8X22HWuFEAVkUKN1v9pivHtEOJfzuNL R82Rga1X0yV4NxTuzkHpp9+ujgbNbPWyAX4x5BEM0uCxatGXCWyG11HwJjSWNwze5tSx GRz9G3WZpOibl6lyaXQwFlVMXOKu88dvs2wNpKztVUaQHCLiTaIWxDQbzaFfIZIiQWCx C72U7krS1UQQmFj/NTBm4mKuAtTdA6UASsws8PVTm3W8zAfevBimCXksBcnPOZ2s2q7G PxIA==
X-Gm-Message-State: AElRT7GP+W/IxXpYwWxPUKeEjiKDmoifODB2ACt2Y6t9483+mC3HUDbW QgNBk35qr/jojazakhhUgq5Ah/rZ
X-Google-Smtp-Source: AIpwx48FMQkykD8ZR2/vpfrMZ9ExnL30y5rPBQE7+ChBSCcEZdnkK8JkRRfdJjIOhLtS1Q11YJqXKA==
X-Received: by 10.101.91.67 with SMTP id y3mr2986974pgr.264.1522631129006; Sun, 01 Apr 2018 18:05:29 -0700 (PDT)
Received: from mail-pl0-f54.google.com (mail-pl0-f54.google.com. [209.85.160.54]) by smtp.gmail.com with ESMTPSA id 67sm27889550pfp.122.2018.04.01.18.05.28 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Apr 2018 18:05:28 -0700 (PDT)
Received: by mail-pl0-f54.google.com with SMTP id v5-v6so1209700plo.4 for <mmusic@ietf.org>; Sun, 01 Apr 2018 18:05:28 -0700 (PDT)
X-Received: by 2002:a17:902:8548:: with SMTP id d8-v6mr8026323plo.241.1522631127934;  Sun, 01 Apr 2018 18:05:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.132 with HTTP; Sun, 1 Apr 2018 18:05:27 -0700 (PDT)
In-Reply-To: <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAD5OKxueCTEo7DtuiCGamo7XaHZOfBM4iVWgzCFj8T2iypOfyg@mail.gmail.com> <e16b2faa-19ed-2cc0-0276-e0d8e27a4cf1@cisco.com> <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Sun, 1 Apr 2018 21:05:27 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com>
Message-ID: <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000812bdc0568d32fd4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4baomZIXwBwDILxOE0bXy9B4vgY>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 01:05:31 -0000

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

Hi Flemming,

I think the draft should have used SHOULD instead of MUST there, as in:

If an agent uses separate ports for RTP and RTCP, the agent MUST include an
SDP rtcp attribute in the "m=3D" section, as described in [RFC3605].  In th=
e
cases where the port number for the RTCP is one higher than the RTP port
and RTCP component address is same as the address of the RTP component, the
SDP rtcp attribute *SHOULD NOT* be included.


Regards,
_____________
Roman Shpount

On Sat, Mar 31, 2018 at 6:12 PM, Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Hi Flemming
>
> Earlier version of the draft didn=E2=80=99t had that restriction. It was =
added at
> later point due to wg discussion almost 2 years back. Roman and Thomas
> Stach would know more details on the exact reasons
>
> I am mobile right now and can try finding from archives for the reasoning
>
> Thanks
> Suhas
>
> On Sat, Mar 31, 2018 at 12:38 PM Flemming Andreasen <fandreas@cisco.com>
> wrote:
>
>> Understood, however is there a need to actively forbid its use in that
>> case ?
>>
>> Thanks
>>
>> -- Flemming
>>
>> On 3/31/18 2:43 PM, Roman Shpount wrote:
>>
>> On Sat, Mar 31, 2018 at 2:27 PM, Flemming Andreasen <fandreas@cisco.com>
>> wrote:
>>
>>> - Section 3.2.2: Why is it forbidden to include the "rtcp" attribute
>>> when the RTCP port number is one higher than the RTP port number ?
>>>
>>
>> The rtcp attribute in this case is redundant since if rtcp attribute is
>> absent, RTCP will be sent to same IP as RTP and port number one higher t=
hen
>> the RTP.
>>
>> Regards,
>> _____________
>> Roman Shpount
>>
>>
>>
>>
>>

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

<div dir=3D"ltr">Hi Flemming,<div><br></div><div>I think the draft should h=
ave used SHOULD instead of MUST there, as in:</div><div><br></div><blockquo=
te style=3D"margin:0 0 0 40px;border:none;padding:0px"><div>If an agent use=
s separate ports for RTP and RTCP, the agent MUST=C2=A0include an SDP rtcp =
attribute in the &quot;m=3D&quot; section, as described in [RFC3605].=C2=A0=
 In the cases where the port number for the RTCP is one higher than the RTP=
 port and RTCP component address is same as the address of the RTP componen=
t, the SDP rtcp attribute <b>SHOULD NOT</b> be included.</div></blockquote>=
<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></div>
<br><div class=3D"gmail_quote">On Sat, Mar 31, 2018 at 6:12 PM, Suhas Nanda=
kumar <span dir=3D"ltr">&lt;<a href=3D"mailto:suhasietf@gmail.com" target=
=3D"_blank">suhasietf@gmail.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><div dir=3D"auto">Hi Flemming</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">Earlier version of the draft didn=E2=80=99t had th=
at restriction. It was added at later point due to wg discussion almost 2 y=
ears back. Roman and Thomas Stach would know more details on the exact reas=
ons</div><div dir=3D"auto"><br></div><div dir=3D"auto">I am mobile right no=
w and can try finding from archives for the reasoning=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Thanks</div><span class=3D"HOEnZb"><f=
ont color=3D"#888888"><div dir=3D"auto">Suhas=C2=A0</div></font></span><div=
><div class=3D"h5"><br><div class=3D"gmail_quote"><div>On Sat, Mar 31, 2018=
 at 12:38 PM Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" t=
arget=3D"_blank">fandreas@cisco.com</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    Understood, however is there a need to actively forbid its use in
    that case ? <br>
    <br>
    Thanks <br></div><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    -- Flemming <br></div><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    <div class=3D"m_-5485714224910789640m_-4012323158461308552moz-cite-pref=
ix">On 3/31/18 2:43 PM, Roman Shpount
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>
        <div class=3D"gmail_extra">
          <div>
            <div class=3D"m_-5485714224910789640m_-4012323158461308552gmail=
_signature" data-smartmail=3D"gmail_signature">On Sat, Mar 31, 2018 at
              2:27 PM, Flemming Andreasen <span>&lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;</span>
              wrote:<br>
            </div>
          </div>
          <div class=3D"gmail_quote">
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF">- Section 3.2.2: Wh=
y
                is it forbidden to include the &quot;rtcp&quot; attribute w=
hen the
                RTCP port number is one higher than the RTP port number
                ?=C2=A0<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>The rtcp attribute in this case is redundant since if
              rtcp attribute is absent, RTCP will be sent to same IP as
              RTP and port number one higher then the RTP.</div>
            <div><br>
            </div>
            <div>Regards,</div>
            <div>
              <div style=3D"color:rgb(34,34,34);font-family:arial,sans-seri=
f;font-size:small;font-style:normal;font-variant-ligatures:normal;font-vari=
ant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgro=
und-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-co=
lor:initial">
                <div class=3D"m_-5485714224910789640m_-4012323158461308552g=
mail_signature">_____________<br>
                  Roman Shpount</div>
              </div>
              <br class=3D"m_-5485714224910789640m_-4012323158461308552gmai=
l-Apple-interchange-newline">
              =C2=A0</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </div></blockquote></div></div></div></div>
</blockquote></div><br></div></div>

--000000000000812bdc0568d32fd4--


From nobody Sun Apr  1 18:42:17 2018
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 40ECB126CD8 for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 18:42:16 -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 Gd30-EPo6lVB for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 18:42:14 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c: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 05E25126C89 for <mmusic@ietf.org>; Sun,  1 Apr 2018 18:42:14 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id r19so3579161vkf.4 for <mmusic@ietf.org>; Sun, 01 Apr 2018 18:42:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5xZ2PclxB4EzzirFAR1Bgz5Rz3oYagk1t/zGH7fz/A8=; b=P2i2Dc09DOTDuOW3mAC5B3T04VOd0ZFavZdPvmiJHJ5NPTN23GtKhq58+qegZPXLvN juSxdlOM4o3B291qgROh/QHnhEMReEx45t9OiD/Wb0wYc5vEcut1ADx6pyyLx7H8ASyj FrJ2LFcMxr3N0y3QbDl9soYu/rQ5BLCJzSxzroWlZdp7ldR9fm1APOmlg7iMDKLQe97D uhynaWohhM3F616zvUeVLC1eJt83qK3+vK2RXQ7DwCtBexNE0xYnGB6hfjp3a9ynLNGE eypTMx4Comqmq1tanWTld5IctBIMuaWgXdDCKMvAQU/DfS5BHQwYwik8dNxduskY6r4g IcJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5xZ2PclxB4EzzirFAR1Bgz5Rz3oYagk1t/zGH7fz/A8=; b=t5GV2Y9mlc8J6KPiDbr7OUoeSkXfNOrE8mGsnSJL0qkSXZZtxKlKVLgUKZW8S8OQFs nntC+HM4ZbV4DfSBpyN83QvdheP2jPUC0LC5BBhqsuYeEvb++mt+V8N5Rh68SPy8cFJ/ mjqEp4hdvTv+nefkA3Du9WdcfkgumuTKlDxVbgxIv9WC7a46J6AdQE0/MKjpJNj042d0 wVIhgThfE7imFTjd8uEgRTK9YhHlpSlui6j49k0xwx+VjLhaeemAJr+fBY+1nOmxHEh4 mLus+mVkLTXFiIax4AseiVeUYxpuq+QhxRQ8sv0+omQj4bK6IXlJLQGhnt37J/W74tfa t3Lw==
X-Gm-Message-State: ALQs6tDaoAtOMx7ei3BzYJbSx5NmF33YowNwfAIhwkFW2mn7gh1Sbddo VrGPa8kWCMXm6g4VWoUkN7D9BanuWlLZAGyU+ig=
X-Google-Smtp-Source: AIpwx49kBe7dSHXaXRKyxlJ6sfnwM7dnGI7hmWBYrE1lEB8RnMaGdHQoFGszRt9W6wZC65T2Zb0DkzeUkbQSlYd0mMA=
X-Received: by 10.31.180.14 with SMTP id d14mr4137507vkf.20.1522633333104; Sun, 01 Apr 2018 18:42:13 -0700 (PDT)
MIME-Version: 1.0
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAD5OKxueCTEo7DtuiCGamo7XaHZOfBM4iVWgzCFj8T2iypOfyg@mail.gmail.com> <e16b2faa-19ed-2cc0-0276-e0d8e27a4cf1@cisco.com> <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com> <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com>
In-Reply-To: <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 02 Apr 2018 01:42:02 +0000
Message-ID: <CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c0b268f165810568d3b21b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7TBH5edgrB7e4EXlMlwL05jxsK8>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 01:42:16 -0000

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

On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount <roman@telurix.com> wrote:

> Hi Flemming,
>
> I think the draft should have used SHOULD instead of MUST there, as in:
>
> If an agent uses separate ports for RTP and RTCP, the agent MUST include
> an SDP rtcp attribute in the "m=3D" section, as described in [RFC3605].  =
In
> the cases where the port number for the RTCP is one higher than the RTP
> port and RTCP component address is same as the address of the RTP
> component, the SDP rtcp attribute *SHOULD NOT* be included.
>
>
Happy to make that change. Flemming, what do you think ?

Cheers
Suhas


> Regards,
> _____________
>
> Roman Shpount
>
> On Sat, Mar 31, 2018 at 6:12 PM, Suhas Nandakumar <suhasietf@gmail.com>
> wrote:
>
>> Hi Flemming
>>
>> Earlier version of the draft didn=E2=80=99t had that restriction. It was=
 added at
>> later point due to wg discussion almost 2 years back. Roman and Thomas
>> Stach would know more details on the exact reasons
>>
>> I am mobile right now and can try finding from archives for the reasonin=
g
>>
>> Thanks
>> Suhas
>>
>> On Sat, Mar 31, 2018 at 12:38 PM Flemming Andreasen <fandreas@cisco.com>
>> wrote:
>>
>>> Understood, however is there a need to actively forbid its use in that
>>> case ?
>>>
>>> Thanks
>>>
>>> -- Flemming
>>>
>>> On 3/31/18 2:43 PM, Roman Shpount wrote:
>>>
>>> On Sat, Mar 31, 2018 at 2:27 PM, Flemming Andreasen <fandreas@cisco.com=
>
>>> wrote:
>>>
>>>> - Section 3.2.2: Why is it forbidden to include the "rtcp" attribute
>>>> when the RTCP port number is one higher than the RTP port number ?
>>>>
>>>
>>> The rtcp attribute in this case is redundant since if rtcp attribute is
>>> absent, RTCP will be sent to same IP as RTP and port number one higher =
then
>>> the RTP.
>>>
>>> Regards,
>>> _____________
>>> Roman Shpount
>>>
>>>
>>>
>>>
>>>
>

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

<div><div dir=3D"auto"><br></div><br><div class=3D"gmail_quote"><div dir=3D=
"auto">On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount &lt;<a href=3D"mailto:r=
oman@telurix.com">roman@telurix.com</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div>Hi Flemming,<div><br></div><div>I think the draft shou=
ld have used SHOULD instead of MUST there, as in:</div><div><br></div><bloc=
kquote style=3D"margin:0 0 0 40px;border:none;padding:0px"><div>If an agent=
 uses separate ports for RTP and RTCP, the agent MUST=C2=A0include an SDP r=
tcp attribute in the &quot;m=3D&quot; section, as described in [RFC3605].=
=C2=A0 In the cases where the port number for the RTCP is one higher than t=
he RTP port and RTCP component address is same as the address of the RTP co=
mponent, the SDP rtcp attribute <b>SHOULD NOT</b> be included.</div></block=
quote></div></blockquote><div dir=3D"auto"><br></div><div dir=3D"auto">Happ=
y to make that change. Flemming, what do you think ?</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">Cheers=C2=A0</div><div dir=3D"auto">Suhas</div=
><div dir=3D"auto"><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><blockquot=
e style=3D"margin:0 0 0 40px;border:none;padding:0px"><div></div></blockquo=
te><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Regards,=
<br clear=3D"all"><div><div class=3D"m_-3346726337255856623gmail_signature"=
 data-smartmail=3D"gmail_signature">_____________</div></div></div></div><d=
iv><div class=3D"gmail_extra"><div><div class=3D"m_-3346726337255856623gmai=
l_signature" data-smartmail=3D"gmail_signature"><br>Roman Shpount</div></di=
v></div></div><div><div class=3D"gmail_extra">
<br><div class=3D"gmail_quote">On Sat, Mar 31, 2018 at 6:12 PM, Suhas Nanda=
kumar <span>&lt;<a href=3D"mailto:suhasietf@gmail.com" target=3D"_blank">su=
hasietf@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:1ex"><=
div><div dir=3D"auto">Hi Flemming</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Earlier version of the draft didn=E2=80=99t had that restriction.=
 It was added at later point due to wg discussion almost 2 years back. Roma=
n and Thomas Stach would know more details on the exact reasons</div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">I am mobile right now and can try f=
inding from archives for the reasoning=C2=A0</div><div dir=3D"auto"><br></d=
iv><div dir=3D"auto">Thanks</div><span class=3D"m_-3346726337255856623HOEnZ=
b"><font color=3D"#888888"><div dir=3D"auto">Suhas=C2=A0</div></font></span=
><div><div class=3D"m_-3346726337255856623h5"><br><div class=3D"gmail_quote=
"><div>On Sat, Mar 31, 2018 at 12:38 PM Flemming Andreasen &lt;<a href=3D"m=
ailto:fandreas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    Understood, however is there a need to actively forbid its use in
    that case ? <br>
    <br>
    Thanks <br></div><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    -- Flemming <br></div><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    <div class=3D"m_-3346726337255856623m_-5485714224910789640m_-4012323158=
461308552moz-cite-prefix">On 3/31/18 2:43 PM, Roman Shpount
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>
        <div class=3D"gmail_extra">
          <div>
            <div class=3D"m_-3346726337255856623m_-5485714224910789640m_-40=
12323158461308552gmail_signature" data-smartmail=3D"gmail_signature">On Sat=
, Mar 31, 2018 at
              2:27 PM, Flemming Andreasen <span>&lt;<a href=3D"mailto:fandr=
eas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;</span>
              wrote:<br>
            </div>
          </div>
          <div class=3D"gmail_quote">
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF">- Section 3.2.2: Wh=
y
                is it forbidden to include the &quot;rtcp&quot; attribute w=
hen the
                RTCP port number is one higher than the RTP port number
                ?=C2=A0<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>The rtcp attribute in this case is redundant since if
              rtcp attribute is absent, RTCP will be sent to same IP as
              RTP and port number one higher then the RTP.</div>
            <div><br>
            </div>
            <div>Regards,</div>
            <div>
              <div style=3D"color:rgb(34,34,34);font-family:arial,sans-seri=
f;font-size:small;font-style:normal;font-variant-ligatures:normal;font-vari=
ant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgro=
und-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-co=
lor:initial">
                <div class=3D"m_-3346726337255856623m_-5485714224910789640m=
_-4012323158461308552gmail_signature">_____________<br>
                  Roman Shpount</div>
              </div>
              <br class=3D"m_-3346726337255856623m_-5485714224910789640m_-4=
012323158461308552gmail-Apple-interchange-newline">
              =C2=A0</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </div></blockquote></div></div></div></div>
</blockquote></div><br></div></div></blockquote></div></div>

--001a11c0b268f165810568d3b21b--


From nobody Sun Apr  1 23:04:03 2018
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 A1DDF126C25 for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 23:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 IPH6rC2cmOwg for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 23:03:58 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::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 8000F124205 for <mmusic@ietf.org>; Sun,  1 Apr 2018 23:03:58 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id n124so7728888vkd.6 for <mmusic@ietf.org>; Sun, 01 Apr 2018 23:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BcGxxbXLBNkoRqmre8DolP2EuDzZORKYWa5cxcCf2Ow=; b=K8RClpBV0fMM8HIIOsncnuXUMizr4uYQMMYv9ig1Rv5uFcsTs7L1blxRqBweXPDYbN AZK1EnCFaPwtZ+HU9siSHDb9L36lNzvshQ6v/KNrx+zG8Zhjff2myFnfNj3tHrOzDV7d QmEUcB+tKQdoM/Xq0OAc2mYyMTLExbsJ+5vaRW8mI/7zXDoUPxztnEmYNa4VC4EwOt2/ XYFmoMeuUwbML45PwZe5NBAd7whE65fM862FI+1S+UlACTl97Zmd78QDxGURvm64hczT +N3Uk9/vaWdV/tFXOz39qjDr3Mic2H2bsnoU+BQif/oSjMt6peX7jqSewsdCGucGT/sO w57A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BcGxxbXLBNkoRqmre8DolP2EuDzZORKYWa5cxcCf2Ow=; b=s1IMlwm7WSRaqeEvX0MrIppg/PYo2SOmfYjy4NUW/UjE4BJ0E9X0CcaUA5sOHOrkdX 8aGes3xfmcpEnZtH248+2WYfu4rd4eqcEjtP4reflX3Bthyj1bTzzn+dUjCV1j20VGCA Gf0v4zCqhdDfWw+kvpa3xTTgmjdZZkYDF0KsXBW8pBHheAFBxLMrgpCj/1xv1CPNS3Kg BqUMwg6ZI5iROnDBDcoWqP4BThSazmagXMwtsYAKofkM6wc+1HOpvvtaR+HLU8L4EYaz rA6pG17jSX16GKbS5hmAcmOunAnjZ23QlHozzOo8I+XJ4vxkKKEYE7n7RHJCWEoWTfJF dxFA==
X-Gm-Message-State: ALQs6tASGHvuXtwRbonoXoIKNwGt4aVSaBCbWwjs6WRV+YkEmJtHF5Pn Ig0OCY9itkrt+12tTew98SiLnkjRdT71baNFjMQ=
X-Google-Smtp-Source: AIpwx4/yiqyOKHKMZWSdvLja7tlpJSTs/+sbKKFHVpmK6BgSG2zia4kzCgIX7uV2trhpL2JesYCTCklAY0ZrG8Hq3CM=
X-Received: by 10.31.174.80 with SMTP id x77mr4409156vke.101.1522649037658; Sun, 01 Apr 2018 23:03:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Sun, 1 Apr 2018 23:03:57 -0700 (PDT)
In-Reply-To: <b06ff217-df66-7588-be01-99a27231900e@cisco.com>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sun, 1 Apr 2018 23:03:57 -0700
Message-ID: <CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143fa3a01debf0568d75be9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/A89_QhOCxl5hqodmwqMEeVFydoc>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 06:04:02 -0000

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

Hello Flemming

 Thanks for the review. Answered inline. Please let me know your thoughts.

cheers
Suhas

On Sat, Mar 31, 2018 at 11:27 AM, Flemming Andreasen <fandreas@cisco.com>
wrote:

> Hi Suhas
>
> Thanks for quickly updating and submitting the document, which I have
> reviewed. A couple of questions:
>
> - Section 3.2.2: Why is it forbidden to include the "rtcp" attribute when
> the RTCP port number is one higher than the RTP port number ?
>
>
[Suhas]  Since this topic is being discussed at present, i will wait on it
for the decision

- Section 3.2.5, list item 3 says:
> <quote>
>
>    3.  If the default candidates were relayed candidates learned through
>        a TURN server, the agent MUST create permissions in the TURN
>        server for the IP addresses learned from its peer in the SDP it
>        just received.  If this is not done, initial packets in the data
>        stream from the peer may be lost.
>
> </quote>
> The text in and by itself seems reasonable, however I am not following how
> this relates to ICE mismatch and hence why it is part of this list (which
> in turn makes it difficult to understand). Let's say it's an offer SDP:
> The default candidates are relayed through a TURN server that the offerer
> uses, however you are now saying the answerer (agent) needs to create a
> permission in the TURN server?
>



[Suhas]  This section was originally under title "Verifying ICE support"
and was Answerer specific procedures. We renamed to "ICE-Mismatch" to align
with ICE-Bis. Would the following clarification be more suitable
<quote>

3.  If the default candidates were relayed candidates learned through
       a TURN server, the responder agent MUST create permissions in the TURN
       server for the IP addresses learned from its peer in the Offer SDP it
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.

</quote>



> - Section 3.3.4: What is considered the "lifetime of the ICE session" ?
> Does it end when we do an ICE restart ? Some clarification would be
> helpful.
>

[Suhas]. By lifetime, it meant ICE Restart. I will add text to clarify.


>
> - Section 10, IANA Considerations, SDP Attributes: Contact information has
> been changed to IESG and there is a new "URIs" section related to this in
> the References. I haven't heard about this new practice before - can you
> elaborate ?
>

[Suhas] The SDP contact information was updated based on feedback from
Christer where he suggested this is the new way. Bundle spec also does the
same. I will check on the new "URIs" section , its addition was
unintentional.


>
> - Section 10.1.8: Why not use a mux category of NORMAL instead of
> TRANSPORT for the session-level ice-pacing attribute (not that it matters
> much in practice since it's a session-level attribute) ?
>

[Suhas] I thought about it and decided to go with TRANSPORT to align with
ice and transport context for other similar attributes. Do you have a
strong recommendation for using NORMAL ?

>
> I also have some editorial comments which I will send to you off-line.
>

[Suhas] Thanks much. I will get to it ASAP.

>
> Thanks
>
> -- Flemming
>
>
>
> On 3/30/18 5:09 PM, Suhas Nandakumar wrote:
>
> Hello All
>
>   We submitted version 18 that fixes the section numbering issues pointed
> out by Christer
>
> Thanks
> Suhas
>
> On Fri, Mar 30, 2018 at 2:08 PM, <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiparty Multimedia Session Control WG
>> of the IETF.
>>
>>         Title           : Session Description Protocol (SDP) Offer/Answer
>> procedures for Interactive Connectivity Establishment (ICE)
>>         Authors         : Marc Petit-Huguenin
>>                           Suhas Nandakumar
>>                           Ari Keranen
>>         Filename        : draft-ietf-mmusic-ice-sip-sdp-18.txt
>>         Pages           : 42
>>         Date            : 2018-03-30
>>
>> Abstract:
>>    This document describes Session Description Protocol (SDP) Offer/
>>    Answer procedures for carrying out Interactive Connectivity
>>    Establishment (ICE) between the agents.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-18
>> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-18
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-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/
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
>
>
> _______________________________________________
> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>
>
>

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

<div dir=3D"ltr">Hello Flemming<div><br></div><div>=C2=A0Thanks for the rev=
iew. Answered inline. Please let me know your thoughts.</div><div><br></div=
><div>cheers</div><div>Suhas</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Sat, Mar 31, 2018 at 11:27 AM, Flemming Andreasen <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fa=
ndreas@cisco.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">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    Hi Suhas<br>
    <br>
    Thanks for quickly updating and submitting the document, which I
    have reviewed. A couple of questions:<br>
    <br>
    - Section 3.2.2: Why is it forbidden to include the &quot;rtcp&quot; at=
tribute
    when the RTCP port number is one higher than the RTP port number ? <br>
    <br></div></blockquote><div><br></div><div>[Suhas]=C2=A0 Since this top=
ic is being discussed at present, i will wait on it for the decision</div><=
div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolor=
=3D"#FFFFFF">
    - Section 3.2.5, list item 3 says:<br>
    &lt;quote&gt;<br>
    <pre style=3D"color:rgb(0,0,0);font-style:normal;font-variant-ligatures=
:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text=
-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-deco=
ration-style:initial;text-decoration-color:initial;word-wrap:break-word;whi=
te-space:pre-wrap">   3.  If the default candidates were relayed candidates=
 learned through
       a TURN server, the agent MUST create permissions in the TURN
       server for the IP addresses learned from its peer in the SDP it
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.</pre>
    &lt;/quote&gt;<br>
    The text in and by itself seems reasonable, however I am not
    following how this relates to ICE mismatch and hence why it is part
    of this list (which in turn makes it difficult to understand).
    <span>Let&#39;s say it&#39;s an offer SDP: The
      default
      candidates are relayed through a TURN server that the offerer
      uses, however you
      are now saying the answerer (agent) needs to create a permission
      in the TURN
      server?=C2=A0 </span></div></blockquote><div><br></div><div>=C2=A0</d=
iv><div><br></div><div>[Suhas]=C2=A0 This section was originally under titl=
e &quot;Verifying ICE support&quot; and was Answerer specific procedures. W=
e renamed to &quot;ICE-Mismatch&quot; to align with ICE-Bis. Would the foll=
owing clarification be more suitable=C2=A0</div><div>&lt;quote&gt;</div><di=
v><pre style=3D"font-style:normal;font-variant-ligatures:normal;font-varian=
t-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255=
,255);text-decoration-style:initial;text-decoration-color:initial;color:rgb=
(0,0,0);word-wrap:break-word;white-space:pre-wrap">3.  If the default candi=
dates were relayed candidates learned through
       a TURN server, the responder agent MUST create permissions in the TU=
RN
       server for the IP addresses learned from its peer in the Offer SDP i=
t
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.</pre>&lt;/quote&gt;</div><div><br>=
</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 text=3D"#000000"=
 bgcolor=3D"#FFFFFF">
    - Section 3.3.4: What is considered the &quot;lifetime of the ICE
    session&quot; ? Does it end when we do an ICE restart ? Some
    clarification would be helpful. <br></div></blockquote><div><br></div><=
div>[Suhas]. By lifetime, it meant ICE Restart. I will add text to clarify.=
</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 text=3D"#000000"=
 bgcolor=3D"#FFFFFF">
    <br>
    - Section 10, IANA Considerations, SDP Attributes: Contact
    information has been changed to IESG and there is a new &quot;URIs&quot=
;
    section related to this in the References. I haven&#39;t heard about
    this new practice before - can you elaborate ? <br></div></blockquote><=
div><br></div><div>[Suhas] The SDP contact information was updated based on=
 feedback from Christer where he suggested this is the new way. Bundle spec=
 also does the same. I will check on the new &quot;URIs&quot; section , its=
 addition was unintentional.</div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    - Section 10.1.8: Why not use a mux category of NORMAL instead of
    TRANSPORT for the session-level ice-pacing attribute (not that it
    matters much in practice since it&#39;s a session-level attribute) ? <b=
r></div></blockquote><div><br></div><div>[Suhas] I thought about it and dec=
ided to go with TRANSPORT to align with ice and transport context for other=
 similar attributes. Do you have a strong recommendation for using NORMAL ?=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D=
"#FFFFFF">
    <br>
    I also have some editorial comments which I will send to you
    off-line. <br></div></blockquote><div><br></div><div>[Suhas] Thanks muc=
h. I will get to it ASAP.=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div te=
xt=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    Thanks <br><span class=3D"m_8918453818703888169HOEnZb"><font color=3D"#=
888888">
    <br>
    -- Flemming <br></font></span><div><div class=3D"m_8918453818703888169h=
5">
    <br>
    <br>
    <br>
    <div class=3D"m_8918453818703888169m_2437396702497347294moz-cite-prefix=
">On 3/30/18 5:09 PM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Hello All
        <div><br>
        </div>
        <div>=C2=A0 We submitted version 18 that fixes the section numberin=
g
          issues pointed out by Christer</div>
        <div><br>
        </div>
        <div>Thanks</div>
        <div>Suhas</div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Fri, Mar 30, 2018 at 2:08 PM, <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank=
">internet-drafts@ietf.org</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><br>
            A New Internet-Draft is available from the on-line
            Internet-Drafts directories.<br>
            This draft is a work item of the Multiparty Multimedia
            Session Control WG of the IETF.<br>
            <br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0: Session Description Protocol (SDP)
            Offer/Answer procedures for Interactive Connectivity
            Establishment (ICE)<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0: Marc Petit-Huguenin<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Ari Keranen<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 : draft-ietf-mmusic-ice-sip-sdp-<wbr>18.txt<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0: 42<br>
            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 : 2018-03-30<br>
            <br>
            Abstract:<br>
            =C2=A0 =C2=A0This document describes Session Description Protoc=
ol
            (SDP) Offer/<br>
            =C2=A0 =C2=A0Answer procedures for carrying out Interactive
            Connectivity<br>
            =C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
            <br>
            <br>
            The IETF datatracker status page for this draft is:<br>
            <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-i=
ce-sip-sdp/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/d<wbr>oc/draft-ietf-mmusic-ice-sip-s<wbr>dp/</a><br>
            <br>
            There are also htmlized versions available at:<br>
            <a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-si=
p-sdp-18" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/=
dr<wbr>aft-ietf-mmusic-ice-sip-sdp-18</a><br>
            <a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmu=
sic-ice-sip-sdp-18" rel=3D"noreferrer" target=3D"_blank">https://datatracke=
r.ietf.org/d<wbr>oc/html/draft-ietf-mmusic-ice-<wbr>sip-sdp-18</a><br>
            <br>
            A diff from the previous version is available at:<br>
            <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusi=
c-ice-sip-sdp-18" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org=
/rfcdiff?u<wbr>rl2=3Ddraft-ietf-mmusic-ice-sip-<wbr>sdp-18</a><br>
            <br>
            <br>
            Please note that it may take a couple of minutes from the
            time of submission<br>
            until the htmlized version and diff are available at <a href=3D=
"http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org=
</a>.<br>
            <br>
            Internet-Drafts are also available by anonymous FTP at:<br>
            <a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferr=
er" target=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
            <br>
            ______________________________<wbr>_________________<br>
            mmusic mailing list<br>
            <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@iet=
f.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/m=
music</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class=3D"m_8918453818703888169m_2437396702497347294mimeAtta=
chmentHeader"></fieldset>
      <br>
      <pre>______________________________<wbr>_________________
mmusic mailing list
<a class=3D"m_8918453818703888169m_2437396702497347294moz-txt-link-abbrevia=
ted" href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>
<a class=3D"m_8918453818703888169m_2437396702497347294moz-txt-link-freetext=
" href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">h=
ttps://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
  </div></div></div>

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

--001a1143fa3a01debf0568d75be9--


From nobody Sun Apr  1 23:38:46 2018
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 D5EB1120047; Sun,  1 Apr 2018 23:38:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152265111883.7510.17758585389165083007@ietfa.amsl.com>
Date: Sun, 01 Apr 2018 23:38:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qoL82UDKcZIHbpFzT17GgLqpArM>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-19.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 06:38:39 -0000

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

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

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


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-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 Sun Apr  1 23:41:06 2018
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 A029A126C25 for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 23:41:05 -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 gLwlarOwBFx4 for <mmusic@ietfa.amsl.com>; Sun,  1 Apr 2018 23:41:04 -0700 (PDT)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::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 D2C61120047 for <mmusic@ietf.org>; Sun,  1 Apr 2018 23:41:03 -0700 (PDT)
Received: by mail-ua0-x229.google.com with SMTP id m47so8381707uae.6 for <mmusic@ietf.org>; Sun, 01 Apr 2018 23:41:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=96GRXXXqXr4P4y+80PRVCEF2f4qSVxGLV9K41WnA6jM=; b=mfOQStmtPbeAG8BMJ26ATXL1aTzi12aZrTlCbU+ERn+B20zPqUCon/UTdfYz6FPR8J 3+bR9CBJzE59RK2bp/KVl2k95M7I9yRtSZ51IeV7IsVLfNcu1lQHk7ceecXUGHsYS9tr S51Yyx0O+Ydn8GH1qcbyD2oqDAQ4EZ+4Otag/KBIrjw0vS13EMkO8TVoOW/9zP9ppe5D VmMPznrs/P7TbyUKiNJec/n1Y50UvuBYMmEwyTBVySITQ0ZW4HSFS2K+WnqtGIzZvAyl s/Qjlj8QB6YO8PDwc0aC96yHxepOKVciSZMke0XtpAky1alkMQrs4ypTx3auryBGKo5T RFow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=96GRXXXqXr4P4y+80PRVCEF2f4qSVxGLV9K41WnA6jM=; b=YQ4z8AIu9xcjpN9j6nNCCMGQepWjbNrWuq99w8hHhM4jhjp5RQF/V2QkYm2WtgTzT1 L+Y+8zRuoOUtR73qle05qh4mDiHNwVa5G3A3jYvAV4SGtoiUf3bxYJHXxCUrNbVNbU+w qvllKFGvS3v/UATiSQiWmBy5tnf43isP78Vi+fSutD81B9kzdClEXQHyDKBeH1J2AXCd BY1/AjguOngxh44aYUlzx8tFY/rgRG7K1fqy5gCQptX01qRZ+x8N6NYV8pvfQ/+AOfbb ssWA/Wuo1ACv1zg8Fuyr/7CNQ7Tu3CWL8V3z4USXblUfBVr9lWrBU6G9pft5qYoYokg/ sZKg==
X-Gm-Message-State: ALQs6tAViD7StQR+Jd3z/A3jYkUievkDRKAV0zuaz+CV+z+J8hvzobOa yRfO4waA+hKXyUEg44Qln3Sb1FiksPwakRUfeMc=
X-Google-Smtp-Source: AIpwx4/+7PGBHZJYARblzxfcldVMu4tx2NjDWFBn0f/sOh/Yo2Almwv+Kc3ahd+jpLfh9dFcZ1q8NxgUVbqH2I+6B7Q=
X-Received: by 10.176.48.169 with SMTP id b9mr4763865uam.55.1522651262835; Sun, 01 Apr 2018 23:41:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Sun, 1 Apr 2018 23:41:02 -0700 (PDT)
In-Reply-To: <152265111883.7510.17758585389165083007@ietfa.amsl.com>
References: <152265111883.7510.17758585389165083007@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sun, 1 Apr 2018 23:41:02 -0700
Message-ID: <CAMRcRGRCCtUfV9aa+jPZxh9upwXpbC43Z=qA_oq6qCAy3GB_pA@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="089e08329e90a361010568d7df33"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uxQIfQtRlbChE21mpevCQHe_rbE>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-19.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 06:41:05 -0000

--089e08329e90a361010568d7df33
Content-Type: text/plain; charset="UTF-8"

Version 19 addresses all the editorial comments from Flemming's review.
 Still to do is the issues reported by Flemming, currently being discussed
on the mailing list

Cheers
Suhas

On Sun, Apr 1, 2018 at 11:38 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : Session Description Protocol (SDP) Offer/Answer
> procedures for Interactive Connectivity Establishment (ICE)
>         Authors         : Marc Petit-Huguenin
>                           Suhas Nandakumar
>                           Ari Keranen
>         Filename        : draft-ietf-mmusic-ice-sip-sdp-19.txt
>         Pages           : 42
>         Date            : 2018-04-01
>
> Abstract:
>    This document describes Session Description Protocol (SDP) Offer/
>    Answer procedures for carrying out Interactive Connectivity
>    Establishment (ICE) between the agents.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-19
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-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/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Version 19 addresses all the editorial comments from Flemm=
ing&#39;s review.=C2=A0<div>=C2=A0Still to do is the issues reported by Fle=
mming, currently being discussed on the mailing list<div><br></div><div>Che=
ers</div><div>Suhas</div></div></div><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Sun, Apr 1, 2018 at 11:38 PM,  <span dir=3D"ltr">&lt=
;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-dra=
fts@ietf.org</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"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-<wbr>19.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-04-01<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc=
/draft-ietf-mmusic-ice-sip-<wbr>sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-i=
etf-mmusic-ice-sip-sdp-<wbr>19</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-19" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<=
wbr>doc/html/draft-ietf-mmusic-<wbr>ice-sip-sdp-19</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-19" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?<wb=
r>url2=3Ddraft-ietf-mmusic-ice-<wbr>sip-sdp-19</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-<wbr>drafts/</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>

--089e08329e90a361010568d7df33--


From nobody Mon Apr  2 06:42:56 2018
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 AD7B612783A for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 06:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 ddddaVWvufXy for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 06:42:52 -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 B5DA3126FB3 for <mmusic@ietf.org>; Mon,  2 Apr 2018 06:42:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13179; q=dns/txt; s=iport; t=1522676572; x=1523886172; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=gP/jqDa8Hc7ObMIbr+dUht0+MetvAofoU+YvFZN2Ftk=; b=bwrab7hqEfKXDR8tns53kMxRjmfjP1s0PyehMtbxPlaHwxA0TZIXEcVf zZG+JKIg//rleeJKQQWUoNUQgm+UfdmCUWQL85Shs+y7d+mI/oTqOSogX MHPglfeMrl8LL1weEqO7nOTBtQpTK8+Hktfc8S0wCU/t0YysHHVlmlbM3 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A0AgAOMsJa/5RdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNCgVAog1yVAYFTIYEPhmGHDoRkgXoLhQQChDIhNhYBAgE?= =?us-ascii?q?BAQEBAQJrKIUlAQUjVhALGCcDAgIhJREGAQwGAgEBhHEDCA2uN4IcH4Q2gi0?= =?us-ascii?q?NgSyCK4dhgVQ/gQwiDIJWgk+CVoJKglQClw4sCIsygnYGh0CEd4lQhi2BJSM?= =?us-ascii?q?IKYFSTSMVgn2QaSMwjioBAQ?=
X-IronPort-AV: E=Sophos; i="5.48,395,1517875200"; d="scan'208,217"; a="93155463"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Apr 2018 13:42:51 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w32Dgp8e026740; Mon, 2 Apr 2018 13:42:51 GMT
To: Suhas Nandakumar <suhasietf@gmail.com>, Roman Shpount <roman@telurix.com>
Cc: mmusic WG <mmusic@ietf.org>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAD5OKxueCTEo7DtuiCGamo7XaHZOfBM4iVWgzCFj8T2iypOfyg@mail.gmail.com> <e16b2faa-19ed-2cc0-0276-e0d8e27a4cf1@cisco.com> <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com> <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com> <CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <4238df55-84d4-46b0-7348-dc0001640cfc@cisco.com>
Date: Mon, 2 Apr 2018 09:42:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C70EA5B7EB612EC4502E7C70"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/aWkbVSq7pFDyULxfrSVR-nNbvzM>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 13:42:55 -0000

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



On 4/1/18 9:42 PM, Suhas Nandakumar wrote:
>
>
> On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount <roman@telurix.com 
> <mailto:roman@telurix.com>> wrote:
>
>     Hi Flemming,
>
>     I think the draft should have used SHOULD instead of MUST there,
>     as in:
>
>         If an agent uses separate ports for RTP and RTCP, the agent
>         MUST include an SDP rtcp attribute in the "m=" section, as
>         described in [RFC3605].  In the cases where the port number
>         for the RTCP is one higher than the RTP port and RTCP
>         component address is same as the address of the RTP component,
>         the SDP rtcp attribute *SHOULD NOT* be included.
>
>
> Happy to make that change. Flemming, what do you think ?
I think it's fine, but it could just as well be "MAY be included".

-- Flemming
>
> Cheers
> Suhas
>
>
>     Regards,
>     _____________
>
>     Roman Shpount
>
>     On Sat, Mar 31, 2018 at 6:12 PM, Suhas Nandakumar
>     <suhasietf@gmail.com <mailto:suhasietf@gmail.com>> wrote:
>
>         Hi Flemming
>
>         Earlier version of the draft didn’t had that restriction. It
>         was added at later point due to wg discussion almost 2 years
>         back. Roman and Thomas Stach would know more details on the
>         exact reasons
>
>         I am mobile right now and can try finding from archives for
>         the reasoning
>
>         Thanks
>         Suhas
>
>         On Sat, Mar 31, 2018 at 12:38 PM Flemming Andreasen
>         <fandreas@cisco.com <mailto:fandreas@cisco.com>> wrote:
>
>             Understood, however is there a need to actively forbid its
>             use in that case ?
>
>             Thanks
>
>             -- Flemming
>
>             On 3/31/18 2:43 PM, Roman Shpount wrote:
>>             On Sat, Mar 31, 2018 at 2:27 PM, Flemming Andreasen
>>             <fandreas@cisco.com <mailto:fandreas@cisco.com>> wrote:
>>
>>                 - Section 3.2.2: Why is it forbidden to include the
>>                 "rtcp" attribute when the RTCP port number is one
>>                 higher than the RTP port number ?
>>
>>
>>             The rtcp attribute in this case is redundant since if
>>             rtcp attribute is absent, RTCP will be sent to same IP as
>>             RTP and port number one higher then the RTP.
>>
>>             Regards,
>>             _____________
>>             Roman Shpount
>>
>
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/1/18 9:42 PM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div>
        <div dir="auto"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="auto">On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount
            &lt;<a href="mailto:roman@telurix.com"
              moz-do-not-send="true">roman@telurix.com</a>&gt; wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div>Hi Flemming,
              <div><br>
              </div>
              <div>I think the draft should have used SHOULD instead of
                MUST there, as in:</div>
              <div><br>
              </div>
              <blockquote style="margin:0 0 0
                40px;border:none;padding:0px">
                <div>If an agent uses separate ports for RTP and RTCP,
                  the agent MUST include an SDP rtcp attribute in the
                  "m=" section, as described in [RFC3605].  In the cases
                  where the port number for the RTCP is one higher than
                  the RTP port and RTCP component address is same as the
                  address of the RTP component, the SDP rtcp attribute <b>SHOULD
                    NOT</b> be included.</div>
              </blockquote>
            </div>
          </blockquote>
          <div dir="auto"><br>
          </div>
          <div dir="auto">Happy to make that change. Flemming, what do
            you think ?</div>
        </div>
      </div>
    </blockquote>
    I think it's fine, but it could just as well be "MAY be included". <br>
    <br>
    -- Flemming <br>
    <blockquote type="cite"
cite="mid:CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <div dir="auto"><br>
          </div>
          <div dir="auto">Cheers </div>
          <div dir="auto">Suhas</div>
          <div dir="auto"><br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div>
              <div class="gmail_extra"><br>
              </div>
              <div class="gmail_extra">Regards,<br clear="all">
                <div>
                  <div class="m_-3346726337255856623gmail_signature"
                    data-smartmail="gmail_signature">_____________</div>
                </div>
              </div>
            </div>
            <div>
              <div class="gmail_extra">
                <div>
                  <div class="m_-3346726337255856623gmail_signature"
                    data-smartmail="gmail_signature"><br>
                    Roman Shpount</div>
                </div>
              </div>
            </div>
            <div>
              <div class="gmail_extra">
                <br>
                <div class="gmail_quote">On Sat, Mar 31, 2018 at 6:12
                  PM, Suhas Nandakumar <span>&lt;<a
                      href="mailto:suhasietf@gmail.com" target="_blank"
                      moz-do-not-send="true">suhasietf@gmail.com</a>&gt;</span>
                  wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    <div>
                      <div dir="auto">Hi Flemming</div>
                      <div dir="auto"><br>
                      </div>
                      <div dir="auto">Earlier version of the draft
                        didn’t had that restriction. It was added at
                        later point due to wg discussion almost 2 years
                        back. Roman and Thomas Stach would know more
                        details on the exact reasons</div>
                      <div dir="auto"><br>
                      </div>
                      <div dir="auto">I am mobile right now and can try
                        finding from archives for the reasoning </div>
                      <div dir="auto"><br>
                      </div>
                      <div dir="auto">Thanks</div>
                      <span class="m_-3346726337255856623HOEnZb"><font
                          color="#888888">
                          <div dir="auto">Suhas </div>
                        </font></span>
                      <div>
                        <div class="m_-3346726337255856623h5"><br>
                          <div class="gmail_quote">
                            <div>On Sat, Mar 31, 2018 at 12:38 PM
                              Flemming Andreasen &lt;<a
                                href="mailto:fandreas@cisco.com"
                                target="_blank" moz-do-not-send="true">fandreas@cisco.com</a>&gt;
                              wrote:<br>
                            </div>
                            <blockquote class="gmail_quote"
                              style="margin:0 0 0 .8ex;border-left:1px
                              #ccc solid;padding-left:1ex">
                              <div text="#000000" bgcolor="#FFFFFF">
                                Understood, however is there a need to
                                actively forbid its use in that case ? <br>
                                <br>
                                Thanks <br>
                              </div>
                              <div text="#000000" bgcolor="#FFFFFF"> <br>
                                -- Flemming <br>
                              </div>
                              <div text="#000000" bgcolor="#FFFFFF"> <br>
                                <div
class="m_-3346726337255856623m_-5485714224910789640m_-4012323158461308552moz-cite-prefix">On
                                  3/31/18 2:43 PM, Roman Shpount wrote:<br>
                                </div>
                                <blockquote type="cite">
                                  <div>
                                    <div class="gmail_extra">
                                      <div>
                                        <div
class="m_-3346726337255856623m_-5485714224910789640m_-4012323158461308552gmail_signature"
data-smartmail="gmail_signature">On Sat, Mar 31, 2018 at 2:27 PM,
                                          Flemming Andreasen <span>&lt;<a
href="mailto:fandreas@cisco.com" target="_blank" moz-do-not-send="true">fandreas@cisco.com</a>&gt;</span>
                                          wrote:<br>
                                        </div>
                                      </div>
                                      <div class="gmail_quote">
                                        <blockquote class="gmail_quote"
                                          style="margin:0 0 0
                                          .8ex;border-left:1px #ccc
                                          solid;padding-left:1ex">
                                          <div text="#000000"
                                            bgcolor="#FFFFFF">- Section
                                            3.2.2: Why is it forbidden
                                            to include the "rtcp"
                                            attribute when the RTCP port
                                            number is one higher than
                                            the RTP port number ? <br>
                                          </div>
                                        </blockquote>
                                        <div><br>
                                        </div>
                                        <div>The rtcp attribute in this
                                          case is redundant since if
                                          rtcp attribute is absent, RTCP
                                          will be sent to same IP as RTP
                                          and port number one higher
                                          then the RTP.</div>
                                        <div><br>
                                        </div>
                                        <div>Regards,</div>
                                        <div>
                                          <div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">
                                            <div
class="m_-3346726337255856623m_-5485714224910789640m_-4012323158461308552gmail_signature">_____________<br>
                                              Roman Shpount</div>
                                          </div>
                                          <br
class="m_-3346726337255856623m_-5485714224910789640m_-4012323158461308552gmail-Apple-interchange-newline">
                                           </div>
                                      </div>
                                    </div>
                                  </div>
                                </blockquote>
                                <br>
                              </div>
                            </blockquote>
                          </div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </div>
                <br>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------C70EA5B7EB612EC4502E7C70--


From nobody Mon Apr  2 06:53:11 2018
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 EFA4B127867 for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 06:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 MOtK6u9ei6_K for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 06:53:06 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3128D129C6B for <mmusic@ietf.org>; Mon,  2 Apr 2018 06:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27801; q=dns/txt; s=iport; t=1522677178; x=1523886778; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=8uiT744dFyIQ4+5iBBpiYbct5lo+zEVRH1OTRGbpotI=; b=gnH7ql6nKC7RIB08Psqg2RfgDKOwj+toIqGLiaPZ/208WJhUo0CFL3p5 AoOBD27WM+DqPw8UitiNE0IerjeGfVNDKQuOwlnV98lFGdyu7gE26t+YD +U8T73ByKCBDdqxDQkwqkmw7rzE4HHfn2UY8NkA9/UAUxPKsEN0yIUZrP w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DAAABrNMJa/51dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMXK2FvKINciACNAYF0gQ+SU4F6CxgBCoQVTAKEMiE0GAECAQE?= =?us-ascii?q?BAQEBAmsohSQBAQEBAgEBASFLCxAJAhggBwMCAicfEQYNBgIBAYR8BQgPkm2bO?= =?us-ascii?q?oIcH4Q2g2aCK4dhgVQ/gQwigmKDEQEBAgEBFoEsgxaCVAKQRIZ2CIVRiFcGgTA?= =?us-ascii?q?6gx+CN4R3iRWGaIElHDiBPA4ITSMVGSGCQwmBZ4FBAQmNLiMwjioBAQ?=
X-IronPort-AV: E=Sophos;i="5.48,395,1517875200";  d="scan'208,217";a="157603017"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Apr 2018 13:52:56 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id w32Dqteh020400; Mon, 2 Apr 2018 13:52:55 GMT
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: mmusic WG <mmusic@ietf.org>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <37e4b6d6-33d9-122c-a452-98cc8c309c1e@cisco.com>
Date: Mon, 2 Apr 2018 09:52:55 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------809A12CB510D73C4CFC4283B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ZsY9KGe20y95QR5GaBGUaNjfKfg>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 13:53:09 -0000

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



On 4/2/18 2:03 AM, Suhas Nandakumar wrote:
> Hello Flemming
>
>  Thanks for the review. Answered inline. Please let me know your thoughts.
>
> cheers
> Suhas
>
> On Sat, Mar 31, 2018 at 11:27 AM, Flemming Andreasen 
> <fandreas@cisco.com <mailto:fandreas@cisco.com>> wrote:
>
>     Hi Suhas
>
>     Thanks for quickly updating and submitting the document, which I
>     have reviewed. A couple of questions:
>
>     - Section 3.2.2: Why is it forbidden to include the "rtcp"
>     attribute when the RTCP port number is one higher than the RTP
>     port number ?
>
>
> [Suhas]  Since this topic is being discussed at present, i will wait 
> on it for the decision
Ok
>
>     - Section 3.2.5, list item 3 says:
>     <quote>
>
>         3.  If the default candidates were relayed candidates learned through
>             a TURN server, the agent MUST create permissions in the TURN
>             server for the IP addresses learned from its peer in the SDP it
>             just received.  If this is not done, initial packets in the data
>             stream from the peer may be lost.
>
>     </quote>
>     The text in and by itself seems reasonable, however I am not
>     following how this relates to ICE mismatch and hence why it is
>     part of this list (which in turn makes it difficult to
>     understand). Let's say it's an offer SDP: The default candidates
>     are relayed through a TURN server that the offerer uses, however
>     you are now saying the answerer (agent) needs to create a
>     permission in the TURN server?
>
>
>
> [Suhas]  This section was originally under title "Verifying ICE 
> support" and was Answerer specific procedures. We renamed to 
> "ICE-Mismatch" to align with ICE-Bis. Would the following 
> clarification be more suitable
> <quote>
> 3.  If the default candidates were relayed candidates learned through
>         a TURN server, the responder agent MUST create permissions in the TURN
>         server for the IP addresses learned from its peer in the Offer SDP it
>         just received.  If this is not done, initial packets in the data
>         stream from the peer may be lost.
> </quote>
>

The problem is that it is preceded by the following:
<quote>

    The agent will proceed with the ICE procedures defined in [ICE-BIS]
    and this specification if, for each data stream in the SDP it
    received, the default destination for each component of that data
    stream appears in a candidate attribute.  For example, in the case of
    RTP, the IP address and port in the "c=" and "m=" lines,
    respectively, appear in a candidate attribute and the value in the
    rtcp attribute appears in a candidate attribute.

    If this condition is not met, the agent MUST process the SDP based on
    normal [RFC3264] procedures, without using any of the ICE mechanisms
    described in the remainder of this specification with the following
    exceptions:

......
</quote>

and hence the text reads as an exception to normal ICE processing (due 
to a mismatch), which I don't believe is what it should (on the contrary 
- it applies to normal ICE processing).


>     - Section 3.3.4: What is considered the "lifetime of the ICE
>     session" ? Does it end when we do an ICE restart ? Some
>     clarification would be helpful.
>
>
> [Suhas]. By lifetime, it meant ICE Restart. I will add text to clarify.
Sounds good.
>
>
>     - Section 10, IANA Considerations, SDP Attributes: Contact
>     information has been changed to IESG and there is a new "URIs"
>     section related to this in the References. I haven't heard about
>     this new practice before - can you elaborate ?
>
>
> [Suhas] The SDP contact information was updated based on feedback from 
> Christer where he suggested this is the new way. Bundle spec also does 
> the same. I will check on the new "URIs" section , its addition was 
> unintentional.
Ok -maybe we can get Christer to clarify where he got that from.

>
>     - Section 10.1.8: Why not use a mux category of NORMAL instead of
>     TRANSPORT for the session-level ice-pacing attribute (not that it
>     matters much in practice since it's a session-level attribute) ?
>
>
> [Suhas] I thought about it and decided to go with TRANSPORT to align 
> with ice and transport context for other similar attributes. Do you 
> have a strong recommendation for using NORMAL ?
At some level, it doesn't really matter since it's a session-level 
attribute and hence the whole idea behind mux category doesn't really 
apply (but I guess we decided we need to specify it anyway). NORMAL 
seems to be the "least" non-sense way of specifying it then and also 
seems to be consistent with the majority of existing session-level 
attribute mux categories.

>
>     I also have some editorial comments which I will send to you
>     off-line.
>
>
> [Suhas] Thanks much. I will get to it ASAP.

Sounds good.

Thanks

-- Flemming
>
>
>     Thanks
>
>     -- Flemming
>
>
>
>     On 3/30/18 5:09 PM, Suhas Nandakumar wrote:
>>     Hello All
>>
>>       We submitted version 18 that fixes the section numbering issues
>>     pointed out by Christer
>>
>>     Thanks
>>     Suhas
>>
>>     On Fri, Mar 30, 2018 at 2:08 PM, <internet-drafts@ietf.org
>>     <mailto:internet-drafts@ietf.org>> wrote:
>>
>>
>>         A New Internet-Draft is available from the on-line
>>         Internet-Drafts directories.
>>         This draft is a work item of the Multiparty Multimedia
>>         Session Control WG of the IETF.
>>
>>                 Title           : Session Description Protocol (SDP)
>>         Offer/Answer procedures for Interactive Connectivity
>>         Establishment (ICE)
>>                 Authors         : Marc Petit-Huguenin
>>                                   Suhas Nandakumar
>>                                   Ari Keranen
>>                 Filename        : draft-ietf-mmusic-ice-sip-sdp-18.txt
>>                 Pages           : 42
>>                 Date            : 2018-03-30
>>
>>         Abstract:
>>            This document describes Session Description Protocol (SDP)
>>         Offer/
>>            Answer procedures for carrying out Interactive Connectivity
>>            Establishment (ICE) between the agents.
>>
>>
>>         The IETF datatracker status page for this draft is:
>>         https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>         <https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/>
>>
>>         There are also htmlized versions available at:
>>         https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-18
>>         <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-18>
>>         https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-18
>>         <https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-18>
>>
>>         A diff from the previous version is available at:
>>         https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-18
>>         <https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-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 <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/>
>>
>>         _______________________________________________
>>         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>
>
>


--------------809A12CB510D73C4CFC4283B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/2/18 2:03 AM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">Hello Flemming
        <div><br>
        </div>
        <div> Thanks for the review. Answered inline. Please let me know
          your thoughts.</div>
        <div><br>
        </div>
        <div>cheers</div>
        <div>Suhas</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Sat, Mar 31, 2018 at 11:27 AM,
            Flemming Andreasen <span dir="ltr">&lt;<a
                href="mailto:fandreas@cisco.com" target="_blank"
                moz-do-not-send="true">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">
              <div text="#000000" bgcolor="#FFFFFF"> Hi Suhas<br>
                <br>
                Thanks for quickly updating and submitting the document,
                which I have reviewed. A couple of questions:<br>
                <br>
                - Section 3.2.2: Why is it forbidden to include the
                "rtcp" attribute when the RTCP port number is one higher
                than the RTP port number ? <br>
                <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas]  Since this topic is being discussed at
              present, i will wait on it for the decision</div>
          </div>
        </div>
      </div>
    </blockquote>
    Ok<br>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> - Section 3.2.5,
                list item 3 says:<br>
                &lt;quote&gt;<br>
                <pre style="color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;word-wrap:break-word;white-space:pre-wrap">   3.  If the default candidates were relayed candidates learned through
       a TURN server, the agent MUST create permissions in the TURN
       server for the IP addresses learned from its peer in the SDP it
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.</pre>
                &lt;/quote&gt;<br>
                The text in and by itself seems reasonable, however I am
                not following how this relates to ICE mismatch and hence
                why it is part of this list (which in turn makes it
                difficult to understand). <span>Let's say it's an offer
                  SDP: The default candidates are relayed through a TURN
                  server that the offerer uses, however you are now
                  saying the answerer (agent) needs to create a
                  permission in the TURN server?  </span></div>
            </blockquote>
            <div><br>
            </div>
            <div> </div>
            <div><br>
            </div>
            <div>[Suhas]  This section was originally under title
              "Verifying ICE support" and was Answerer specific
              procedures. We renamed to "ICE-Mismatch" to align with
              ICE-Bis. Would the following clarification be more
              suitable </div>
            <div>&lt;quote&gt;</div>
            <div>
              <pre style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">3.  If the default candidates were relayed candidates learned through
       a TURN server, the responder agent MUST create permissions in the TURN
       server for the IP addresses learned from its peer in the Offer SDP it
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.</pre>
              &lt;/quote&gt;</div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    The problem is that it is preceded by the following:<br>
    &lt;quote&gt;<br>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; word-wrap: break-word; white-space: pre-wrap;">   The agent will proceed with the ICE procedures defined in [ICE-BIS]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the "c=" and "m=" lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.

   If this condition is not met, the agent MUST process the SDP based on
   normal [RFC3264] procedures, without using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:</pre>
    ......<br>
    &lt;/quote&gt;<br>
    <br>
    and hence the text reads as an exception to normal ICE processing
    (due to a mismatch), which I don't believe is what it should (on the
    contrary - it applies to normal ICE processing). <br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div> </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> - Section 3.3.4:
                What is considered the "lifetime of the ICE session" ?
                Does it end when we do an ICE restart ? Some
                clarification would be helpful. <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas]. By lifetime, it meant ICE Restart. I will add
              text to clarify.</div>
            <div> </div>
          </div>
        </div>
      </div>
    </blockquote>
    Sounds good. <br>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> <br>
                - Section 10, IANA Considerations, SDP Attributes:
                Contact information has been changed to IESG and there
                is a new "URIs" section related to this in the
                References. I haven't heard about this new practice
                before - can you elaborate ? <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] The SDP contact information was updated based
              on feedback from Christer where he suggested this is the
              new way. Bundle spec also does the same. I will check on
              the new "URIs" section , its addition was unintentional.</div>
            <div> </div>
          </div>
        </div>
      </div>
    </blockquote>
    Ok -maybe we can get Christer to clarify where he got that from. <br>
    <br>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> <br>
                - Section 10.1.8: Why not use a mux category of NORMAL
                instead of TRANSPORT for the session-level ice-pacing
                attribute (not that it matters much in practice since
                it's a session-level attribute) ? <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] I thought about it and decided to go with
              TRANSPORT to align with ice and transport context for
              other similar attributes. Do you have a strong
              recommendation for using NORMAL ? <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    At some level, it doesn't really matter since it's a session-level
    attribute and hence the whole idea behind mux category doesn't
    really apply (but I guess we decided we need to specify it anyway).
    NORMAL seems to be the "least" non-sense way of specifying it then
    and also seems to be consistent with the majority of existing
    session-level attribute mux categories. <br>
    <br>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> <br>
                I also have some editorial comments which I will send to
                you off-line. <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] Thanks much. I will get to it ASAP. <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Sounds good. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <blockquote type="cite"
cite="mid:CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"> <br>
                Thanks <br>
                <span class="m_8918453818703888169HOEnZb"><font
                    color="#888888"> <br>
                    -- Flemming <br>
                  </font></span>
                <div>
                  <div class="m_8918453818703888169h5"> <br>
                    <br>
                    <br>
                    <div
                      class="m_8918453818703888169m_2437396702497347294moz-cite-prefix">On
                      3/30/18 5:09 PM, Suhas Nandakumar wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div dir="ltr">Hello All
                        <div><br>
                        </div>
                        <div>  We submitted version 18 that fixes the
                          section numbering issues pointed out by
                          Christer</div>
                        <div><br>
                        </div>
                        <div>Thanks</div>
                        <div>Suhas</div>
                      </div>
                      <div class="gmail_extra"><br>
                        <div class="gmail_quote">On Fri, Mar 30, 2018 at
                          2:08 PM, <span dir="ltr">&lt;<a
                              href="mailto:internet-drafts@ietf.org"
                              target="_blank" moz-do-not-send="true">internet-drafts@ietf.org</a>&gt;</span>
                          wrote:<br>
                          <blockquote class="gmail_quote"
                            style="margin:0 0 0 .8ex;border-left:1px
                            #ccc solid;padding-left:1ex"><br>
                            A New Internet-Draft is available from the
                            on-line Internet-Drafts directories.<br>
                            This draft is a work item of the Multiparty
                            Multimedia Session Control WG of the IETF.<br>
                            <br>
                                    Title           : Session
                            Description Protocol (SDP) Offer/Answer
                            procedures for Interactive Connectivity
                            Establishment (ICE)<br>
                                    Authors         : Marc
                            Petit-Huguenin<br>
                                                      Suhas Nandakumar<br>
                                                      Ari Keranen<br>
                                    Filename        :
                            draft-ietf-mmusic-ice-sip-sdp-<wbr>18.txt<br>
                                    Pages           : 42<br>
                                    Date            : 2018-03-30<br>
                            <br>
                            Abstract:<br>
                               This document describes Session
                            Description Protocol (SDP) Offer/<br>
                               Answer procedures for carrying out
                            Interactive Connectivity<br>
                               Establishment (ICE) between the agents.<br>
                            <br>
                            <br>
                            The IETF datatracker status page for this
                            draft is:<br>
                            <a
                              href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">https://datatracker.ietf.org/d<wbr>oc/draft-ietf-mmusic-ice-sip-s<wbr>dp/</a><br>
                            <br>
                            There are also htmlized versions available
                            at:<br>
                            <a
                              href="https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-18"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">https://tools.ietf.org/html/dr<wbr>aft-ietf-mmusic-ice-sip-sdp-18</a><br>
                            <a
href="https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-18"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">https://datatracker.ietf.org/d<wbr>oc/html/draft-ietf-mmusic-ice-<wbr>sip-sdp-18</a><br>
                            <br>
                            A diff from the previous version is
                            available at:<br>
                            <a
href="https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-18"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">https://www.ietf.org/rfcdiff?u<wbr>rl2=draft-ietf-mmusic-ice-sip-<wbr>sdp-18</a><br>
                            <br>
                            <br>
                            Please note that it may take a couple of
                            minutes from the time of submission<br>
                            until the htmlized version and diff are
                            available at <a
                              href="http://tools.ietf.org"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">tools.ietf.org</a>.<br>
                            <br>
                            Internet-Drafts are also available by
                            anonymous FTP at:<br>
                            <a
                              href="ftp://ftp.ietf.org/internet-drafts/"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
                            <br>
                            ______________________________<wbr>_________________<br>
                            mmusic mailing list<br>
                            <a href="mailto:mmusic@ietf.org"
                              target="_blank" moz-do-not-send="true">mmusic@ietf.org</a><br>
                            <a
                              href="https://www.ietf.org/mailman/listinfo/mmusic"
                              rel="noreferrer" target="_blank"
                              moz-do-not-send="true">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a><br>
                          </blockquote>
                        </div>
                        <br>
                      </div>
                      <br>
                      <fieldset
                        class="m_8918453818703888169m_2437396702497347294mimeAttachmentHeader"></fieldset>
                      <br>
                      <pre>______________________________<wbr>_________________
mmusic mailing list
<a class="m_8918453818703888169m_2437396702497347294moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org" target="_blank" moz-do-not-send="true">mmusic@ietf.org</a>
<a class="m_8918453818703888169m_2437396702497347294moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a>
</pre>
                    </blockquote>
                    <br>
                  </div>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------809A12CB510D73C4CFC4283B--


From nobody Mon Apr  2 10:44:38 2018
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 5FC00126D85 for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 10:44:37 -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 4qDu76ERUbfP for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 10:44:34 -0700 (PDT)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c: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 A1167126B72 for <mmusic@ietf.org>; Mon,  2 Apr 2018 10:44:33 -0700 (PDT)
Received: by mail-vk0-x229.google.com with SMTP id q198so8675691vke.3 for <mmusic@ietf.org>; Mon, 02 Apr 2018 10:44:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gH8QOYVd+izp/iuXo1GEf6VlGeZ9x9pbHUHTtzGeoJI=; b=HY2gwCbbS8R44lF9ZxT8NIG5jAhQOvSpaZK9AzEUMdgg9leaswmmWMsg7JXr94Sb83 9rYQsKGkdgQ5fJml7W1fnvN4Erpp1JGm/R8i9QKw1uv2uoGW0PrHjah5pMUkUQRjCpYL mi4vmDO0SVUZME99oF9SAnSYqH8onFbc3hjC27C4F+J62nUXmG/mkVg/3Ra51C4SGAAn 83CFVqscAdiN9nKNno427uYIyVS1sVvh87ZAGe0pfqMSqH8DMf6ADd2l+MsydRgR5LmA THAwjTEVSB0GN6xdvjMNCmVnV8HPo3uF5NjjB0f+AT5ZMnM6pLY3p6qm5Vzum27R15ME TgQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gH8QOYVd+izp/iuXo1GEf6VlGeZ9x9pbHUHTtzGeoJI=; b=DAWwmLNIbOBIhengPz2C5PEHqihFe0aF9vAyG94KGENddUOEcGVBr5i294gaTdCSiB yAc10I87Uw72O4Ip4aWGirP5Mcl9Q0nug3G0o94zvCFvAGggRZwcBlbk28e8FzDAQirO +rqGK/nOBjZCRZe/4WlZ35rIsQyN3J1vOda+UYeTEhqVJJxKzTLqlECm210h/6lRzHLT 0jRKVcGTyfBnGOiO62QhhNFwzShAcXpW6C/d8DwaL+Ew7hRFdtP09ARHyPIhE3KB+sLG 0IocLVRymvrCkSwW0DC2WN6UQf8CS40gaTWMHOgjnTkHBPiyOmxuxGoRwilDeHZQQkum 4kew==
X-Gm-Message-State: ALQs6tBvUD1BkNOAaA1PsobtLSa9JNRfCVKEmAkRGZejuuuKJBX9T6TL MBWLjiLBeppUVye3HforsmM8eMOT3bDeUuo04P4IsA==
X-Google-Smtp-Source: AIpwx49Qkt0kqao9DVOFLAmTpazx/NeVIbpK1nO3Y5ru63eXUfaGXgco3uTMEl0V3K3Ib7rC1WN7u1fgUiUa6HT88rY=
X-Received: by 10.31.177.141 with SMTP id a135mr5786385vkf.88.1522691072622; Mon, 02 Apr 2018 10:44:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Mon, 2 Apr 2018 10:44:32 -0700 (PDT)
In-Reply-To: <37e4b6d6-33d9-122c-a452-98cc8c309c1e@cisco.com>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAMRcRGS45OES6c8fzQuwHi+SnQ48Nr-tgDZ+rs5n=nUV8aM95A@mail.gmail.com> <37e4b6d6-33d9-122c-a452-98cc8c309c1e@cisco.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 2 Apr 2018 10:44:32 -0700
Message-ID: <CAMRcRGQhD+_fakm8seKYORcG=PStc=F7hfoYXOTkOtsXT0HRxw@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c029707c85a00568e1248c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CHWHnVfNbhGZKTH0lWmCZpspTIY>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 17:44:37 -0000

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

Hello Flemming

 Please see inline.

Thanks
Suhas

On Mon, Apr 2, 2018 at 6:52 AM, Flemming Andreasen <fandreas@cisco.com>
wrote:

>
>
> On 4/2/18 2:03 AM, Suhas Nandakumar wrote:
>
> Hello Flemming
>
>  Thanks for the review. Answered inline. Please let me know your thoughts.
>
> cheers
> Suhas
>
> On Sat, Mar 31, 2018 at 11:27 AM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
>
>> Hi Suhas
>>
>> Thanks for quickly updating and submitting the document, which I have
>> reviewed. A couple of questions:
>>
>> - Section 3.2.2: Why is it forbidden to include the "rtcp" attribute when
>> the RTCP port number is one higher than the RTP port number ?
>>
>>
> [Suhas]  Since this topic is being discussed at present, i will wait on it
> for the decision
>
> Ok
>

[Suhas] Will update to say "MAY be included" as suggested.


>
>
> - Section 3.2.5, list item 3 says:
>> <quote>
>>
>>    3.  If the default candidates were relayed candidates learned through
>>        a TURN server, the agent MUST create permissions in the TURN
>>        server for the IP addresses learned from its peer in the SDP it
>>        just received.  If this is not done, initial packets in the data
>>        stream from the peer may be lost.
>>
>> </quote>
>> The text in and by itself seems reasonable, however I am not following
>> how this relates to ICE mismatch and hence why it is part of this list
>> (which in turn makes it difficult to understand). Let's say it's an
>> offer SDP: The default candidates are relayed through a TURN server that
>> the offerer uses, however you are now saying the answerer (agent) needs to
>> create a permission in the TURN server?
>>
>
>
>
> [Suhas]  This section was originally under title "Verifying ICE support"
> and was Answerer specific procedures. We renamed to "ICE-Mismatch" to align
> with ICE-Bis. Would the following clarification be more suitable
> <quote>
>
> 3.  If the default candidates were relayed candidates learned through
>        a TURN server, the responder agent MUST create permissions in the TURN
>        server for the IP addresses learned from its peer in the Offer SDP it
>        just received.  If this is not done, initial packets in the data
>        stream from the peer may be lost.
>
> </quote>
>
>
> The problem is that it is preceded by the following:
> <quote>
>
>    The agent will proceed with the ICE procedures defined in [ICE-BIS]
>    and this specification if, for each data stream in the SDP it
>    received, the default destination for each component of that data
>    stream appears in a candidate attribute.  For example, in the case of
>    RTP, the IP address and port in the "c=" and "m=" lines,
>    respectively, appear in a candidate attribute and the value in the
>    rtcp attribute appears in a candidate attribute.
>
>    If this condition is not met, the agent MUST process the SDP based on
>    normal [RFC3264] procedures, without using any of the ICE mechanisms
>    described in the remainder of this specification with the following
>    exceptions:
>
> ......
> </quote>
>
> and hence the text reads as an exception to normal ICE processing (due to
> a mismatch), which I don't believe is what it should (on the contrary - it
> applies to normal ICE processing).
>
>

[Suhas]. I will send a different email to keep the discussion focussed on
this topic.




>
>
>
>> - Section 3.3.4: What is considered the "lifetime of the ICE session" ?
>> Does it end when we do an ICE restart ? Some clarification would be
>> helpful.
>>
>
> [Suhas]. By lifetime, it meant ICE Restart. I will add text to clarify.
>
>
> Sounds good.
>
>
>> - Section 10, IANA Considerations, SDP Attributes: Contact information
>> has been changed to IESG and there is a new "URIs" section related to this
>> in the References. I haven't heard about this new practice before - can you
>> elaborate ?
>>
>
> [Suhas] The SDP contact information was updated based on feedback from
> Christer where he suggested this is the new way. Bundle spec also does the
> same. I will check on the new "URIs" section , its addition was
> unintentional.
>
>
> Ok -maybe we can get Christer to clarify where he got that from.
>
>
>> - Section 10.1.8: Why not use a mux category of NORMAL instead of
>> TRANSPORT for the session-level ice-pacing attribute (not that it matters
>> much in practice since it's a session-level attribute) ?
>>
>
> [Suhas] I thought about it and decided to go with TRANSPORT to align with
> ice and transport context for other similar attributes. Do you have a
> strong recommendation for using NORMAL ?
>
> At some level, it doesn't really matter since it's a session-level
> attribute and hence the whole idea behind mux category doesn't really apply
> (but I guess we decided we need to specify it anyway). NORMAL seems to be
> the "least" non-sense way of specifying it then and also seems to be
> consistent with the majority of existing session-level attribute mux
> categories.
>
>
>> I also have some editorial comments which I will send to you off-line.
>>
>
> [Suhas] Thanks much. I will get to it ASAP.
>
>
> Sounds good.
>
> Thanks
>
> -- Flemming
>
>
>> Thanks
>>
>> -- Flemming
>>
>>
>>
>> On 3/30/18 5:09 PM, Suhas Nandakumar wrote:
>>
>> Hello All
>>
>>   We submitted version 18 that fixes the section numbering issues pointed
>> out by Christer
>>
>> Thanks
>> Suhas
>>
>> On Fri, Mar 30, 2018 at 2:08 PM, <internet-drafts@ietf.org> wrote:
>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the Multiparty Multimedia Session Control
>>> WG of the IETF.
>>>
>>>         Title           : Session Description Protocol (SDP)
>>> Offer/Answer procedures for Interactive Connectivity Establishment (ICE)
>>>         Authors         : Marc Petit-Huguenin
>>>                           Suhas Nandakumar
>>>                           Ari Keranen
>>>         Filename        : draft-ietf-mmusic-ice-sip-sdp-18.txt
>>>         Pages           : 42
>>>         Date            : 2018-03-30
>>>
>>> Abstract:
>>>    This document describes Session Description Protocol (SDP) Offer/
>>>    Answer procedures for carrying out Interactive Connectivity
>>>    Establishment (ICE) between the agents.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-18
>>> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-18
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-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/
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>>
>
>

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

<div dir=3D"ltr">Hello Flemming<div><br></div><div>=C2=A0Please see inline.=
</div><div><br></div><div>Thanks</div><div>Suhas</div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Mon, Apr 2, 2018 at 6:52 AM, Flemmi=
ng Andreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" ta=
rget=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D"">
    <br>
    <br>
    <div class=3D"m_-141900853735448583moz-cite-prefix">On 4/2/18 2:03 AM, =
Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Hello Flemming
        <div><br>
        </div>
        <div>=C2=A0Thanks for the review. Answered inline. Please let me kn=
ow
          your thoughts.</div>
        <div><br>
        </div>
        <div>cheers</div>
        <div>Suhas</div>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Sat, Mar 31, 2018 at 11:27 AM,
            Flemming Andreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fand=
reas@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;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> Hi Suhas<br>
                <br>
                Thanks for quickly updating and submitting the document,
                which I have reviewed. A couple of questions:<br>
                <br>
                - Section 3.2.2: Why is it forbidden to include the
                &quot;rtcp&quot; attribute when the RTCP port number is one=
 higher
                than the RTP port number ? <br>
                <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas]=C2=A0 Since this topic is being discussed at
              present, i will wait on it for the decision</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Ok</div></blockquote><div><br></div><div>[Suhas] Will update to say &qu=
ot;MAY be included&quot; as suggested.</div><div>=C2=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D""=
><br>
    <blockquote type=3D"cite">
      <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:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> - Section 3.2.5,
                list item 3 says:<br>
                &lt;quote&gt;<br>
                <pre style=3D"color:rgb(0,0,0);font-style:normal;font-varia=
nt-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing=
:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0=
px;text-decoration-style:initial;text-decoration-color:initial;word-wrap:br=
eak-word;white-space:pre-wrap">   3.  If the default candidates were relaye=
d candidates learned through
       a TURN server, the agent MUST create permissions in the TURN
       server for the IP addresses learned from its peer in the SDP it
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.</pre>
                &lt;/quote&gt;<br>
                The text in and by itself seems reasonable, however I am
                not following how this relates to ICE mismatch and hence
                why it is part of this list (which in turn makes it
                difficult to understand). <span>Let&#39;s say it&#39;s an o=
ffer
                  SDP: The default candidates are relayed through a TURN
                  server that the offerer uses, however you are now
                  saying the answerer (agent) needs to create a
                  permission in the TURN server?=C2=A0 </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>=C2=A0</div>
            <div><br>
            </div>
            <div>[Suhas]=C2=A0 This section was originally under title
              &quot;Verifying ICE support&quot; and was Answerer specific
              procedures. We renamed to &quot;ICE-Mismatch&quot; to align w=
ith
              ICE-Bis. Would the following clarification be more
              suitable=C2=A0</div>
            <div>&lt;quote&gt;</div>
            <div>
              <pre style=3D"font-style:normal;font-variant-ligatures:normal=
;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;word-spacing:0px;background-color=
:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initi=
al;color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">3.  If the d=
efault candidates were relayed candidates learned through
       a TURN server, the responder agent MUST create permissions in the TU=
RN
       server for the IP addresses learned from its peer in the Offer SDP i=
t
       just received.  If this is not done, initial packets in the data
       stream from the peer may be lost.</pre>
              &lt;/quote&gt;</div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></span>
    The problem is that it is preceded by the following:<br>
    &lt;quote&gt;<br>
    <pre style=3D"color:rgb(0,0,0);font-style:normal;font-variant-ligatures=
:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text=
-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-deco=
ration-style:initial;text-decoration-color:initial;word-wrap:break-word;whi=
te-space:pre-wrap">   The agent will proceed with the ICE procedures define=
d in [ICE-BIS]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the &quot;c=3D&quot; and &quot;m=3D&quot=
; lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.

   If this condition is not met, the agent MUST process the SDP based on
   normal [RFC3264] procedures, without using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:</pre>
    ......<br>
    &lt;/quote&gt;<br>
    <br>
    and hence the text reads as an exception to normal ICE processing
    (due to a mismatch), which I don&#39;t believe is what it should (on th=
e
    contrary - it applies to normal ICE processing). <br><span class=3D"">
    <br></span></div></blockquote><div><br></div><div><br></div><div>[Suhas=
]. I will send a different email to keep the discussion focussed on this to=
pic.</div><div><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;ma=
rgin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;font-vari=
ant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:=
0px;text-decoration-style:initial;text-decoration-color:initial"> </pre><br=
></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 text=3D"#000000=
" bgcolor=3D"#FFFFFF"><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <div>=C2=A0</div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> - Section 3.3.4:
                What is considered the &quot;lifetime of the ICE session&qu=
ot; ?
                Does it end when we do an ICE restart ? Some
                clarification would be helpful. <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas]. By lifetime, it meant ICE Restart. I will add
              text to clarify.</div>
            <div>=C2=A0</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Sounds good. <br><span class=3D"">
    <blockquote type=3D"cite">
      <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;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> <br>
                - Section 10, IANA Considerations, SDP Attributes:
                Contact information has been changed to IESG and there
                is a new &quot;URIs&quot; section related to this in the
                References. I haven&#39;t heard about this new practice
                before - can you elaborate ? <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] The SDP contact information was updated based
              on feedback from Christer where he suggested this is the
              new way. Bundle spec also does the same. I will check on
              the new &quot;URIs&quot; section , its addition was unintenti=
onal.</div>
            <div>=C2=A0</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Ok -maybe we can get Christer to clarify where he got that from. <br><s=
pan class=3D"">
    <br>
    <blockquote type=3D"cite">
      <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;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> <br>
                - Section 10.1.8: Why not use a mux category of NORMAL
                instead of TRANSPORT for the session-level ice-pacing
                attribute (not that it matters much in practice since
                it&#39;s a session-level attribute) ? <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] I thought about it and decided to go with
              TRANSPORT to align with ice and transport context for
              other similar attributes. Do you have a strong
              recommendation for using NORMAL ? <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote></span>
    At some level, it doesn&#39;t really matter since it&#39;s a session-le=
vel
    attribute and hence the whole idea behind mux category doesn&#39;t
    really apply (but I guess we decided we need to specify it anyway).
    NORMAL seems to be the &quot;least&quot; non-sense way of specifying it=
 then
    and also seems to be consistent with the majority of existing
    session-level attribute mux categories. <br><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <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;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> <br>
                I also have some editorial comments which I will send to
                you off-line. <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] Thanks much. I will get to it ASAP. <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br></span>
    Sounds good. <br>
    <br>
    Thanks <br><span class=3D"HOEnZb"><font color=3D"#888888">
    <br>
    -- Flemming <br></font></span><div><div class=3D"h5">
    <blockquote type=3D"cite">
      <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;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"> <br>
                Thanks <br>
                <span class=3D"m_-141900853735448583m_8918453818703888169HO=
EnZb"><font color=3D"#888888"> <br>
                    -- Flemming <br>
                  </font></span>
                <div>
                  <div class=3D"m_-141900853735448583m_8918453818703888169h=
5"> <br>
                    <br>
                    <br>
                    <div class=3D"m_-141900853735448583m_891845381870388816=
9m_2437396702497347294moz-cite-prefix">On
                      3/30/18 5:09 PM, Suhas Nandakumar wrote:<br>
                    </div>
                    <blockquote type=3D"cite">
                      <div dir=3D"ltr">Hello All
                        <div><br>
                        </div>
                        <div>=C2=A0 We submitted version 18 that fixes the
                          section numbering issues pointed out by
                          Christer</div>
                        <div><br>
                        </div>
                        <div>Thanks</div>
                        <div>Suhas</div>
                      </div>
                      <div class=3D"gmail_extra"><br>
                        <div class=3D"gmail_quote">On Fri, Mar 30, 2018 at
                          2:08 PM, <span dir=3D"ltr">&lt;<a href=3D"mailto:=
internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</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>
                            A New Internet-Draft is available from the
                            on-line Internet-Drafts directories.<br>
                            This draft is a work item of the Multiparty
                            Multimedia Session Control WG of the IETF.<br>
                            <br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0: Session
                            Description Protocol (SDP) Offer/Answer
                            procedures for Interactive Connectivity
                            Establishment (ICE)<br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0: Marc
                            Petit-Huguenin<br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ari Keranen<br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 :
                            draft-ietf-mmusic-ice-sip-sdp-<wbr>18.txt<br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0: 42<br>
                            =C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 : 2018-03-30<br>
                            <br>
                            Abstract:<br>
                            =C2=A0 =C2=A0This document describes Session
                            Description Protocol (SDP) Offer/<br>
                            =C2=A0 =C2=A0Answer procedures for carrying out
                            Interactive Connectivity<br>
                            =C2=A0 =C2=A0Establishment (ICE) between the ag=
ents.<br>
                            <br>
                            <br>
                            The IETF datatracker status page for this
                            draft is:<br>
                            <a href=3D"https://datatracker.ietf.org/doc/dra=
ft-ietf-mmusic-ice-sip-sdp/" rel=3D"noreferrer" target=3D"_blank">https://d=
atatracker.ietf.org/d<wbr>oc/draft-ietf-mmusic-ice-sip-s<wbr>dp/</a><br>
                            <br>
                            There are also htmlized versions available
                            at:<br>
                            <a href=3D"https://tools.ietf.org/html/draft-ie=
tf-mmusic-ice-sip-sdp-18" rel=3D"noreferrer" target=3D"_blank">https://tool=
s.ietf.org/html/dr<wbr>aft-ietf-mmusic-ice-sip-sdp-18</a><br>
                            <a href=3D"https://datatracker.ietf.org/doc/htm=
l/draft-ietf-mmusic-ice-sip-sdp-18" rel=3D"noreferrer" target=3D"_blank">ht=
tps://datatracker.ietf.org/d<wbr>oc/html/draft-ietf-mmusic-ice-<wbr>sip-sdp=
-18</a><br>
                            <br>
                            A diff from the previous version is
                            available at:<br>
                            <a href=3D"https://www.ietf.org/rfcdiff?url2=3D=
draft-ietf-mmusic-ice-sip-sdp-18" rel=3D"noreferrer" target=3D"_blank">http=
s://www.ietf.org/rfcdiff?u<wbr>rl2=3Ddraft-ietf-mmusic-ice-sip-<wbr>sdp-18<=
/a><br>
                            <br>
                            <br>
                            Please note that it may take a couple of
                            minutes from the time of submission<br>
                            until the htmlized version and diff are
                            available at <a href=3D"http://tools.ietf.org" =
rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
                            <br>
                            Internet-Drafts are also available by
                            anonymous FTP at:<br>
                            <a href=3D"ftp://ftp.ietf.org/internet-drafts/"=
 rel=3D"noreferrer" target=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>af=
ts/</a><br>
                            <br>
                            ______________________________<wbr>____________=
_____<br>
                            mmusic mailing list<br>
                            <a href=3D"mailto:mmusic@ietf.org" target=3D"_b=
lank">mmusic@ietf.org</a><br>
                            <a href=3D"https://www.ietf.org/mailman/listinf=
o/mmusic" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/l<wbr>istinfo/mmusic</a><br>
                          </blockquote>
                        </div>
                        <br>
                      </div>
                      <br>
                      <fieldset class=3D"m_-141900853735448583m_89184538187=
03888169m_2437396702497347294mimeAttachmentHeader"></fieldset>
                      <br>
                      <pre>______________________________<wbr>_____________=
____
mmusic mailing list
<a class=3D"m_-141900853735448583m_8918453818703888169m_2437396702497347294=
moz-txt-link-abbreviated" href=3D"mailto:mmusic@ietf.org" target=3D"_blank"=
>mmusic@ietf.org</a>
<a class=3D"m_-141900853735448583m_8918453818703888169m_2437396702497347294=
moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/listinfo/mmusic=
" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a>
</pre>
                    </blockquote>
                    <br>
                  </div>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

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

--001a11c029707c85a00568e1248c--


From nobody Mon Apr  2 10:56:41 2018
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 1A96F12D7F9 for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 10:56:39 -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 2ZbOkPyf-GPS for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 10:56:36 -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 E8523127010 for <mmusic@ietf.org>; Mon,  2 Apr 2018 10:56:35 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id y127so8693519vky.9 for <mmusic@ietf.org>; Mon, 02 Apr 2018 10:56:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=/37F9arSCQZ4xSgKT6RtKSgWtmF8rvpBZb3fvAELR3E=; b=QDYkTZhyEjWWCyAZC876fWlQO2zUFAGZbo6R0gD27Rc+PbayKlPy530vhLEG+h1WcJ ++OSrKf4bQppAErkgFlGHomFiTpSKrdXu1lzKC/jnt6V1sjz4G/lWbNWzGEzigK1hGjx p1KasTA9ad9ekLhXQLAw1eCqxdw0z28e+Xs66H3BhwgC1aarLKh8Q3ImdO7wVlW1BoWi biTpRANmjm0Shu5rd+SIewyd68GdNGUa4O0VCQ+G1at0mH11au7pfJC6me+rSZlzhG6n 2Mi+Or+fwFRnMPn1QY7k0HhiTStS9nKk6MOnfIz3SlSvN0nEmN5XzmwA9VaN7FItfgsI 2gXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/37F9arSCQZ4xSgKT6RtKSgWtmF8rvpBZb3fvAELR3E=; b=lvECzyFRyGBYK9zhlbrW3wab4eBwWJ6WUQa5SZhDBWXbS56lJp3OnjkG1JxXG2fkdy r4ORVvAtjIJEUzIkY3pjxKTib6+0NKTXermm81qjfETGQKZPxH6WOESGAK/pvPNf/vAs kRUl2mRPMuGgsA68fBiq+tklvX9SoXTy9JBmQXXJ0FBz1szqETQODvT5CTzDGTmisF8A ZxD+OsWJtMhL9BSbUj1JxNweWIluWbc2skvavwnEtvGpMAXx2iMiARHJs9RKjqt5jx+c Sx/KI27QnP4U7lAZD14J1S7uPe0P95NXanMUsaC1jawB1/Rn+1pKjh9313HKTGfWfl6F Yhow==
X-Gm-Message-State: ALQs6tBO6j6/iaMX0/PIImJO4iXdkB9XMMqqmDK5JuXU4Gf2B4zPOSUq BSG0qTnO4qRWfHZz+vkykUdzmlqxP+otwcwFA5zRWA==
X-Google-Smtp-Source: AIpwx49K5iGndwNYgFwc5cLhDYEyIW108nrRycfcmHkJ2ajFxsxhfP8vT5i7YGjqnKVdV8xTvf8ytc2g+by6r6K/e/Q=
X-Received: by 10.31.180.14 with SMTP id d14mr5782078vkf.20.1522691794900; Mon, 02 Apr 2018 10:56:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Mon, 2 Apr 2018 10:56:34 -0700 (PDT)
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 2 Apr 2018 10:56:34 -0700
Message-ID: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c0b268899c3d0568e14f82"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CtV0HGJWyL6-f9Jyg8fxqH03d_Q>
Subject: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 17:56:39 -0000

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

Hi Flemming

Moving the discussion in a separate thread to keep it focussed. How about
following rewording of the section 3.2.5.



3.2.5 <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5>.
Verifying ICE Support

   The agents will proceed with the ICE procedures defined in [ICE-BIS
<https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the "c=" and "m=" lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.

   If this condition is not met, the agents MUST process the SDP based on
   normal [RFC3264 <https://tools.ietf.org/html/rfc3264>] procedures,
without using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:

   1.  An controlled/responding agent MUST follow the rules of

       section 11 of [ICE-BIS
<https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>],
which describe keepalive procedures

       for all agents. Also, If the default candidates were relayed

       candidates learned through a TURN server, the controlled agent

       MUST create permissions in the TURN server for the IP addresses

       learned from its peer in the offer SDP it just received.

       If this is not done, initial packets in the data stream from the

       peer may be lost.


   2.  On the other hand, if the controlled agent is not proceeding

       with ICE because there were a=candidate attributes, but none that

       matched the default destination of the data stream, it MUST include

       an a=ice-mismatch attribute in its answer and MAY omit a=candidate
       attributes for such data streams.  See Section 9.2.2
<https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2>
for a
       discussion of cases where this can happen. This specification provides

       no guidance on how an controlled agent should proceed in such a

       failure case.




Cheers
Suhas

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

<div dir=3D"ltr"><div style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-=
variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;=
text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;bac=
kground-color:rgb(255,255,255);text-decoration-style:initial;text-decoratio=
n-color:initial">Hi Flemming</div><div style=3D"color:rgb(34,34,34);font-fa=
mily:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligat=
ures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;=
text-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initi=
al;text-decoration-color:initial"><br></div><div style=3D"color:rgb(34,34,3=
4);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-var=
iant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spaci=
ng:normal;text-align:start;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-s=
tyle:initial;text-decoration-color:initial">Moving the discussion in a sepa=
rate thread to keep it focussed. How about following rewording of the secti=
on 3.2.5.=C2=A0</div><pre class=3D"gmail-newpage" style=3D"font-style:norma=
l;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;le=
tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wo=
rd-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:init=
ial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin=
-bottom:0px;color:rgb(0,0,0)"><span class=3D"gmail-h4" style=3D"line-height=
:0pt;display:inline;white-space:pre;font-family:monospace;font-size:1em;fon=
t-weight:bold"><br></span></pre><pre class=3D"gmail-newpage" style=3D"font-=
style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-we=
ight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transf=
orm:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration=
-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top=
:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"gmail-h4" style=3D"=
line-height:0pt;display:inline;white-space:pre;font-family:monospace;font-s=
ize:1em;font-weight:bold"><br></span></pre><pre class=3D"gmail-newpage" sty=
le=3D"font-style:normal;font-variant-ligatures:normal;font-variant-caps:nor=
mal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;=
text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text=
-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px=
;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"gmail-h4=
" style=3D"line-height:0pt;display:inline;white-space:pre;font-family:monos=
pace;font-size:1em;font-weight:bold"><h4 style=3D"line-height:0pt;display:i=
nline;white-space:pre;font-family:monospace;font-size:1em;font-weight:bold"=
><a class=3D"gmail-selflink" name=3D"section-3.2.5" href=3D"https://tools.i=
etf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5" style=3D"color=
:black;text-decoration:none">3.2.5</a>.  Verifying ICE Support</h4></span>

   The agents will proceed with the ICE procedures defined in [<a href=3D"h=
ttps://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" ti=
tle=3D"&quot;Interactive Connectivity Establishment (ICE): A Protocol for N=
etwork Address Translator (NAT) Traversal for Offer/Answer Protocols&quot;"=
 style=3D"color:rgb(17,85,204)">ICE-BIS</a>]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the &quot;c=3D&quot; and &quot;m=3D&quot=
; lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.

   If this condition is not met, the agents MUST process the SDP based on
   normal [<a href=3D"https://tools.ietf.org/html/rfc3264" title=3D"&quot;A=
n Offer/Answer Model with Session Description Protocol (SDP)&quot;" style=
=3D"color:rgb(17,85,204)">RFC3264</a>] procedures, without using any of the=
 ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:
</pre><pre class=3D"gmail-newpage" style=3D"font-style:normal;font-variant-=
ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:no=
rmal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;=
background-color:rgb(255,255,255);text-decoration-style:initial;text-decora=
tion-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;col=
or:rgb(0,0,0)">   1.  An controlled/responding agent MUST follow the rules =
of </pre><pre class=3D"gmail-newpage" style=3D"font-style:normal;font-varia=
nt-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing=
:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0=
px;background-color:rgb(255,255,255);text-decoration-style:initial;text-dec=
oration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;=
color:rgb(0,0,0)">       section 11 of [<a href=3D"https://tools.ietf.org/h=
tml/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" title=3D"&quot;Interactiv=
e Connectivity Establishment (ICE): A Protocol for Network Address Translat=
or (NAT) Traversal for Offer/Answer Protocols&quot;" style=3D"color:rgb(17,=
85,204)">ICE-BIS</a>], which describe keepalive procedures </pre><pre class=
=3D"gmail-newpage" style=3D"font-style:normal;font-variant-ligatures:normal=
;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;word-spacing:0px;background-color=
:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initi=
al;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"> =
      for all agents. Also, If the default candidates were relayed </pre><p=
re class=3D"gmail-newpage" style=3D"font-style:normal;font-variant-ligature=
s:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;tex=
t-align:start;text-indent:0px;text-transform:none;word-spacing:0px;backgrou=
nd-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-col=
or:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0=
,0,0)">       candidates learned through a TURN server, the controlled agen=
t </pre><pre class=3D"gmail-newpage" style=3D"font-style:normal;font-varian=
t-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:=
normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0p=
x;background-color:rgb(255,255,255);text-decoration-style:initial;text-deco=
ration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;c=
olor:rgb(0,0,0)">       MUST create permissions in the TURN server for the =
IP addresses </pre><pre class=3D"gmail-newpage" style=3D"font-style:normal;=
font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;lett=
er-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word=
-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initia=
l;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-b=
ottom:0px;color:rgb(0,0,0)">       learned from its peer in the offer SDP i=
t just received.  </pre><pre class=3D"gmail-newpage" style=3D"font-style:no=
rmal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400=
;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none=
;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:i=
nitial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;mar=
gin-bottom:0px;color:rgb(0,0,0)">       If this is not done, initial packet=
s in the data stream from the </pre><pre class=3D"gmail-newpage" style=3D"f=
ont-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;fon=
t-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-tr=
ansform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decora=
tion-style:initial;text-decoration-color:initial;font-size:13.3333px;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       peer may be lost.<br>

   2.  On the other hand, if the controlled agent is not proceeding </pre><=
pre class=3D"gmail-newpage" style=3D"font-style:normal;font-variant-ligatur=
es:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;te=
xt-align:start;text-indent:0px;text-transform:none;word-spacing:0px;backgro=
und-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-co=
lor:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(=
0,0,0)">       with ICE because there were a=3Dcandidate attributes, but no=
ne that </pre><pre class=3D"gmail-newpage" style=3D"font-style:normal;font-=
variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-sp=
acing:normal;text-align:start;text-indent:0px;text-transform:none;word-spac=
ing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;tex=
t-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">       matched the default destination of the data s=
tream, it MUST include </pre><pre class=3D"gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       an a=3Dice-mismatch attribute =
in its answer and MAY omit a=3Dcandidate
       attributes for such data streams.  See <a href=3D"https://tools.ietf=
.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2" style=3D"color:rg=
b(17,85,204)">Section 9.2.2</a> for a
       discussion of cases where this can happen. This specification provid=
es </pre><pre class=3D"gmail-newpage" style=3D"font-style:normal;font-varia=
nt-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing=
:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0=
px;background-color:rgb(255,255,255);text-decoration-style:initial;text-dec=
oration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;=
color:rgb(0,0,0)">       no guidance on how an controlled agent should proc=
eed in such a </pre><pre class=3D"gmail-newpage" style=3D"font-style:normal=
;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wor=
d-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initi=
al;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-=
bottom:0px;color:rgb(0,0,0)">       failure case.</pre><br class=3D"gmail-A=
pple-interchange-newline"><br><div><br></div><div>Cheers</div><div>Suhas</d=
iv></div>

--001a11c0b268899c3d0568e14f82--


From nobody Mon Apr  2 11:08:33 2018
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 1986612D864 for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 11:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuYbfoXRSNrz for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 11:08:29 -0700 (PDT)
Received: from mail-pl0-x234.google.com (mail-pl0-x234.google.com [IPv6:2607:f8b0:400e:c01::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 AB17B12D7FC for <mmusic@ietf.org>; Mon,  2 Apr 2018 11:08:29 -0700 (PDT)
Received: by mail-pl0-x234.google.com with SMTP id v5-v6so3144934plo.4 for <mmusic@ietf.org>; Mon, 02 Apr 2018 11:08:29 -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=rsQ+lJ8M6S//+YFKKh3hXce/TJZpq9xGu448XowRlhY=; b=0J+pZmDXXJtThZ0xiTwnK2RoFvgzAPOo/ESaRwyCACYPAVuLl6ZGnGmWUNjd1l81u4 nXy7khvgM98Yx/gYv7uqLr9s5oTBvmcwVp3oqI6s9sAC8zowAYLnncQlG8drOpAvsH5Z H6hbOFnxHWQFwLTDW3owk02fKtUF9npp+uS6b3U3KefbfhnbXZw2zricL1QE8o2SFBNE gphA3/gUzfNwpbMu3NLCDCbfq0imsa6GSM/iNg7LMW8QlrYHM3NAdrNqxYeGt5GFQBx+ JKQhqxwuT6MI61Q9VmvY06gyCZUf7hNkzsbs7jE4Img33YoKfOwxKVfyhxnYo4G/9PTn j6DA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rsQ+lJ8M6S//+YFKKh3hXce/TJZpq9xGu448XowRlhY=; b=XAof0bEozpTIWGfQT8wpJ55f8pV4UyvUUvxlyf5c+GBsIu/tdBKeceS2a9RwlhbLjX thKJodOxaLivJByxtXE57Hn7JCbkBIiewwEYOzrtAYshGxLgIFrutyx+3sNMwNUndPf3 5bydYwJnDsJXJHiq7XnCmN2yZ+2HBPG6uj76ip3k6TWetjyIIxzL0fvVtJeBCpdBYiOO 2ZgZ+TmMnymEjCFwQ/LSm8G6o17fmWJ9yegaN5so17AfyjJdl3W9utAwM1a12s0M+f2L WF1MPHzuQ1POWQ0U9PJkxCVnK2SlOaoGmUkNcwWnv1gin3n8LjjROIort983l4ZuBnnv UKow==
X-Gm-Message-State: AElRT7FzWYCz4WwhFlMfwtZovm1AHXVR/6FVSVBYBijpZimk1gWf8vd0 5dCX6QOZxbYv6TdglK85wOOGyyd0
X-Google-Smtp-Source: AIpwx499FlKLR6W8u3hhTpwM/uKIsfFioCMwQZvC3ny70Hb11k9Obid2/ecmUWeTy7lGT2OYcEbjaA==
X-Received: by 10.98.13.151 with SMTP id 23mr8139799pfn.120.1522692508791; Mon, 02 Apr 2018 11:08:28 -0700 (PDT)
Received: from mail-pl0-f48.google.com (mail-pl0-f48.google.com. [209.85.160.48]) by smtp.gmail.com with ESMTPSA id v12sm1459399pgs.21.2018.04.02.11.08.27 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Apr 2018 11:08:27 -0700 (PDT)
Received: by mail-pl0-f48.google.com with SMTP id x4-v6so5120485pln.7 for <mmusic@ietf.org>; Mon, 02 Apr 2018 11:08:27 -0700 (PDT)
X-Received: by 2002:a17:902:8b82:: with SMTP id ay2-v6mr10607149plb.12.1522692507553;  Mon, 02 Apr 2018 11:08:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.132 with HTTP; Mon, 2 Apr 2018 11:08:26 -0700 (PDT)
In-Reply-To: <4238df55-84d4-46b0-7348-dc0001640cfc@cisco.com>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAD5OKxueCTEo7DtuiCGamo7XaHZOfBM4iVWgzCFj8T2iypOfyg@mail.gmail.com> <e16b2faa-19ed-2cc0-0276-e0d8e27a4cf1@cisco.com> <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com> <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com> <CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com> <4238df55-84d4-46b0-7348-dc0001640cfc@cisco.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 2 Apr 2018 14:08:26 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvNECsRi+zvoD5ZqeqEWyMHZCpByRbOXBqonW1a6-7GxQ@mail.gmail.com>
Message-ID: <CAD5OKxvNECsRi+zvoD5ZqeqEWyMHZCpByRbOXBqonW1a6-7GxQ@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000003d7440568e17ac0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/X2XSwG5rX4lyQdQKnpGlGm8ydlg>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 18:08:32 -0000

--00000000000003d7440568e17ac0
Content-Type: text/plain; charset="UTF-8"

Hi Flemming,

On Mon, Apr 2, 2018 at 9:42 AM, Flemming Andreasen <fandreas@cisco.com>
wrote:

>
> On 4/1/18 9:42 PM, Suhas Nandakumar wrote:
>
>
>
> On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount <roman@telurix.com> wrote:
>
>> Hi Flemming,
>>
>> I think the draft should have used SHOULD instead of MUST there, as in:
>>
>> If an agent uses separate ports for RTP and RTCP, the agent MUST include
>> an SDP rtcp attribute in the "m=" section, as described in [RFC3605].  In
>> the cases where the port number for the RTCP is one higher than the RTP
>> port and RTCP component address is same as the address of the RTP
>> component, the SDP rtcp attribute *SHOULD NOT* be included.
>>
>>
> Happy to make that change. Flemming, what do you think ?
>
> I think it's fine, but it could just as well be "MAY be included".
>

I think "SHOULD NOT be included" is cleaner. In the described case rtcp
attribute serves no purpose, so there is a reason not to add it. This
attribute will not break anything but it really should not be there.

Regards,
_____________
Roman Shpount

--00000000000003d7440568e17ac0
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" data-smartmail=3D"gmail_signature">Hi Flemming,</div><div class=3D"gma=
il_signature" data-smartmail=3D"gmail_signature"><br></div><div class=3D"gm=
ail_signature" data-smartmail=3D"gmail_signature">On Mon, Apr 2, 2018 at 9:=
42 AM, 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></=
div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D""><br>
    <div class=3D"m_-7244827835921304023moz-cite-prefix">On 4/1/18 9:42 PM,=
 Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>
        <div dir=3D"auto"><br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"auto">On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount
            &lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roma=
n@telurix.com</a>&gt; wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div>Hi Flemming,
              <div><br>
              </div>
              <div>I think the draft should have used SHOULD instead of
                MUST there, as in:</div>
              <div><br>
              </div>
              <blockquote style=3D"margin:0 0 0 40px;border:none;padding:0p=
x">
                <div>If an agent uses separate ports for RTP and RTCP,
                  the agent MUST=C2=A0include an SDP rtcp attribute in the
                  &quot;m=3D&quot; section, as described in [RFC3605].=C2=
=A0 In the cases
                  where the port number for the RTCP is one higher than
                  the RTP port and RTCP component address is same as the
                  address of the RTP component, the SDP rtcp attribute <b>S=
HOULD
                    NOT</b> be included.</div>
              </blockquote>
            </div>
          </blockquote>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">Happy to make that change. Flemming, what do
            you think ?</div>
        </div>
      </div>
    </blockquote></span>
    I think it&#39;s fine, but it could just as well be &quot;MAY be includ=
ed&quot;.=C2=A0<br></div></blockquote><div><br></div><div>I think &quot;SHO=
ULD NOT be included&quot; is cleaner. In the described case rtcp attribute =
serves no purpose, so there is a reason not to add it. This attribute will =
not break anything but it really should not be there.</div><div><br></div><=
div>Regards,</div><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br=
 class=3D"gmail-Apple-interchange-newline">

=C2=A0</div></div></div></div>

--00000000000003d7440568e17ac0--


From nobody Mon Apr  2 11:39:05 2018
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 CAA4112D864 for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 11:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fNUN-g3-BFcv for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 11:39:00 -0700 (PDT)
Received: from mail-pl0-x22a.google.com (mail-pl0-x22a.google.com [IPv6:2607:f8b0:400e:c01::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 D82FC126DFF for <mmusic@ietf.org>; Mon,  2 Apr 2018 11:39:00 -0700 (PDT)
Received: by mail-pl0-x22a.google.com with SMTP id 59-v6so2539468plc.13 for <mmusic@ietf.org>; Mon, 02 Apr 2018 11:39:00 -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=CeG6RM39p0QnLnuyVnBanh4I5Mr7RNeC6A8AvDq/RiE=; b=VT+dE/fN2vXiB4yyODONcMNK76CbZVaqbxGHLcM6F80LzdkphsIB4uUHAIinIvJWAS WOJ3eV5eocT2pxOfFUe4kM+r5KyqBctFRiRUUQNj8IIgMYMEqbZIR3FlkZKczOwVR7RC UX9UMdf7PqU+tA/My5Gj8yeiY8J1lyYJpk5GlKYqpaW/56CgbvDrSkLtWtRV/LoYrcq6 uuHTnZjhltu4WJC/QezpEVtgHcZ0umjVSTYtV8YE0HGAaEJ2K8SjHQUuayIPfiJOxCwg Yi1CgkcGTFVXIk7/u/1tCgt5Xa4xGqtX3yDccC2BiOZxhnpvBKBFNL9BQnHFF/jUW1g6 lQ6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CeG6RM39p0QnLnuyVnBanh4I5Mr7RNeC6A8AvDq/RiE=; b=o0pbYHGBkmx1hGJBcM+qRFgZWgiBdZ2Y4MU2woXBjJ/wrGsRfCVdd6z7DkUhnrtG+x JaZr2s6I1ODVEJ2zocrxAb6ZBC//L89jDbbIEmvsufMHnoBx1froOY/zAn8H7nwO5kZD nYmXjWxR12YcepDWzmpOUFm6xBrYPLUdkTRCz778ZmDDaJvT4PA1PBO2vCo0xACL5I4A z3ok1AxleX0Xo7I10UzZ4JBzwUlaovdBvcsu3MeCfm8jNX+/ccGH29KDo7SBxsf6nJ4Y gaBkst/vkAahK99a4z+egSQbA2vbpGfSulChzKlTzIPjlZakvl+IVxgM5iOJeDM8n8na oBSQ==
X-Gm-Message-State: AElRT7HmdGXSzgIp1icQqTFd2lXVzPKKTiPVzzd1XzRKRi75zjbaGT9n tI6iC4+o9pIWvhm9UHq/SM6wmePH
X-Google-Smtp-Source: AIpwx49IXuC+VDa7hNO8v1/hshwqH2A4NWMayXl/yYXIOaLE7Sqh8LDH5jigLkJK260Mtx9upR6UIw==
X-Received: by 10.98.139.143 with SMTP id e15mr8212371pfl.134.1522694339422; Mon, 02 Apr 2018 11:38:59 -0700 (PDT)
Received: from mail-pl0-f53.google.com (mail-pl0-f53.google.com. [209.85.160.53]) by smtp.gmail.com with ESMTPSA id p71sm2088151pfl.89.2018.04.02.11.38.58 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Apr 2018 11:38:58 -0700 (PDT)
Received: by mail-pl0-f53.google.com with SMTP id b6-v6so3250627pla.11 for <mmusic@ietf.org>; Mon, 02 Apr 2018 11:38:58 -0700 (PDT)
X-Received: by 10.99.98.134 with SMTP id w128mr6967641pgb.217.1522694338411; Mon, 02 Apr 2018 11:38:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.132 with HTTP; Mon, 2 Apr 2018 11:38:57 -0700 (PDT)
In-Reply-To: <CAD5OKxvNECsRi+zvoD5ZqeqEWyMHZCpByRbOXBqonW1a6-7GxQ@mail.gmail.com>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAD5OKxueCTEo7DtuiCGamo7XaHZOfBM4iVWgzCFj8T2iypOfyg@mail.gmail.com> <e16b2faa-19ed-2cc0-0276-e0d8e27a4cf1@cisco.com> <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com> <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com> <CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com> <4238df55-84d4-46b0-7348-dc0001640cfc@cisco.com> <CAD5OKxvNECsRi+zvoD5ZqeqEWyMHZCpByRbOXBqonW1a6-7GxQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 2 Apr 2018 14:38:57 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuQOFHiV7RwmAnU0sk7XWLL4YgOq4JBsoAKopfYmXg-=Q@mail.gmail.com>
Message-ID: <CAD5OKxuQOFHiV7RwmAnU0sk7XWLL4YgOq4JBsoAKopfYmXg-=Q@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c11d69a2482e70568e1e7fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2lsQT75V04r2wKHS8__J5quC0oc>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 18:39:03 -0000

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

On Mon, Apr 2, 2018 at 2:08 PM, Roman Shpount <roman@telurix.com> wrote:

> Hi Flemming,
>
> On Mon, Apr 2, 2018 at 9:42 AM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
>
>>
>> On 4/1/18 9:42 PM, Suhas Nandakumar wrote:
>>
>>
>>
>> On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount <roman@telurix.com> wrote:
>>
>>> Hi Flemming,
>>>
>>> I think the draft should have used SHOULD instead of MUST there, as in:
>>>
>>> If an agent uses separate ports for RTP and RTCP, the agent MUST include
>>> an SDP rtcp attribute in the "m=" section, as described in [RFC3605].  In
>>> the cases where the port number for the RTCP is one higher than the RTP
>>> port and RTCP component address is same as the address of the RTP
>>> component, the SDP rtcp attribute *SHOULD NOT* be included.
>>>
>>>
>> Happy to make that change. Flemming, what do you think ?
>>
>> I think it's fine, but it could just as well be "MAY be included".
>>
>
> I think "SHOULD NOT be included" is cleaner. In the described case rtcp
> attribute serves no purpose, so there is a reason not to add it. This
> attribute will not break anything but it really should not be there.
>
>
After thinking about this a bit more "MAY be omitted" also works for me and
makes more sense together with the previous sentence where rtcp attribute
MUST be included.
_____________
Roman Shpount

--94eb2c11d69a2482e70568e1e7fa
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" data-smartmail=3D"gmail_signature">On Mon, Apr 2, 2018 at 2:08 PM, Rom=
an Shpount <span dir=3D"ltr">&lt;<a href=3D"mailto:roman@telurix.com" targe=
t=3D"_blank">roman@telurix.com</a>&gt;</span> wrote:<br></div></div><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div cl=
ass=3D"gmail_extra"><div><div class=3D"m_7396668075697656374gmail_signature=
" data-smartmail=3D"gmail_signature">Hi Flemming,</div><span class=3D""><di=
v class=3D"m_7396668075697656374gmail_signature" data-smartmail=3D"gmail_si=
gnature"><br></div><div class=3D"m_7396668075697656374gmail_signature" data=
-smartmail=3D"gmail_signature">On Mon, Apr 2, 2018 at 9:42 AM, Flemming And=
reasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=
=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br></div></span></div>=
<div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><span><br>
    <div class=3D"m_7396668075697656374m_-7244827835921304023moz-cite-prefi=
x">On 4/1/18 9:42 PM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>
        <div dir=3D"auto"><br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"auto">On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount
            &lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roma=
n@telurix.com</a>&gt; wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div>Hi Flemming,
              <div><br>
              </div>
              <div>I think the draft should have used SHOULD instead of
                MUST there, as in:</div>
              <div><br>
              </div>
              <blockquote style=3D"margin:0 0 0 40px;border:none;padding:0p=
x">
                <div>If an agent uses separate ports for RTP and RTCP,
                  the agent MUST=C2=A0include an SDP rtcp attribute in the
                  &quot;m=3D&quot; section, as described in [RFC3605].=C2=
=A0 In the cases
                  where the port number for the RTCP is one higher than
                  the RTP port and RTCP component address is same as the
                  address of the RTP component, the SDP rtcp attribute <b>S=
HOULD
                    NOT</b> be included.</div>
              </blockquote>
            </div>
          </blockquote>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">Happy to make that change. Flemming, what do
            you think ?</div>
        </div>
      </div>
    </blockquote></span>
    I think it&#39;s fine, but it could just as well be &quot;MAY be includ=
ed&quot;.=C2=A0<br></div></blockquote><div><br></div></span><div>I think &q=
uot;SHOULD NOT be included&quot; is cleaner. In the described case rtcp att=
ribute serves no purpose, so there is a reason not to add it. This attribut=
e will not break anything but it really should not be there.</div><div><br>=
</div></div></div></div></blockquote><div><br></div><div>After thinking abo=
ut this a bit more &quot;MAY be omitted&quot; also works for me and makes m=
ore sense together with the previous sentence where rtcp attribute MUST be =
included.</div><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br=
 class=3D"gmail-Apple-interchange-newline">

=C2=A0</div></div></div></div>

--94eb2c11d69a2482e70568e1e7fa--


From nobody Mon Apr  2 11:51:39 2018
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 11D8E12D86A for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 11:51:37 -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 9FMJTVWKXihJ for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 11:51:34 -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 808931241F8 for <mmusic@ietf.org>; Mon,  2 Apr 2018 11:51:34 -0700 (PDT)
Received: by mail-vk0-x22d.google.com with SMTP id v134so8793255vkd.10 for <mmusic@ietf.org>; Mon, 02 Apr 2018 11:51:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NiRirQ1kY57SY8aoj+AsBudTr+NuJOyvLJh87ot7yuA=; b=dE3iYFuCUqSiewvcaONmBWa2Yaign+BIEWH/lBt9cKjhfhu0lyRFWmT5DzbRxkLPt0 ZCbnNHcAUqJXmVOYqjRviZJEnjsz0HUeTIquH9zjvuArntBaKbR6Qljo105+wSf+82Yf Z/f6xmsyKZNXoDYS+6ezbiYT3570lb9iiaJAoRTBdrcqXLRGkrt8V7AqqI+vHx8hXgwu 0A6q/QFv9Rwbj/v/M345LE6KRvSsmkEbbDHnKQ3nJ6A5VKrstOx295G3N4jLsx9hx2uU BUUl7zdvFFJ/bFmn5QvcICOFQx+/uNMQC+wX/y+loJxMkVLnWT+PRj0QCHxBchpDXoNP DnOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NiRirQ1kY57SY8aoj+AsBudTr+NuJOyvLJh87ot7yuA=; b=rh2u7jJ9msfPasl7By/SaVm9BdKQf2K4fje39vUzjEmswkHDXQkDSWvgRlaWYfmYGd K2gx+85zl/fK4aw06Wv5cdRNRPYu+CBWmd40Q/VHsvQZ7iluTZwkqTcFcAFult+17gi5 IMTh0eYpfTb7nOxegkVl1n2DENNPRnXKy5sTg/lLE3TJZvlnvKyyJo6dloHQIrAhknPd DiLe6ouUgnku0hSt6kn9kD29haVr4ep+cnt89ZgTPCo9lqhPSm6VylXrEsXSKDhj4UVK u7Ki974ETuwE6kQt7iDKjlozJLIsPqUs19r0ae61hCtSwjVGBp75VyqdyHXA/Z47ybyZ OY7Q==
X-Gm-Message-State: ALQs6tBS3pQXuhRQetaq/J0B5Xd3gFevC0IjtgTRZCpV7rbCb9Bp80Of GFE7KqsW1Phdb9maynltL5BWkYfFCtVIKLDtJmI=
X-Google-Smtp-Source: AIpwx497QmW+C/6HguDgAyz+EzgeuUPxtCvP4jAMUiyMHKV7sdD5SbTmTdQC+IWxabkyCs5vDBOSn5gmmffUCbAWMEo=
X-Received: by 10.31.140.196 with SMTP id o187mr2777646vkd.4.1522695093450; Mon, 02 Apr 2018 11:51:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Mon, 2 Apr 2018 11:51:33 -0700 (PDT)
In-Reply-To: <CAD5OKxuQOFHiV7RwmAnU0sk7XWLL4YgOq4JBsoAKopfYmXg-=Q@mail.gmail.com>
References: <152244408666.20516.13092465844540705990@ietfa.amsl.com> <CAMRcRGS8yAL78x2+5=b+L5GdFMt_JosXca-nHGAZU28e6s=-Pg@mail.gmail.com> <b06ff217-df66-7588-be01-99a27231900e@cisco.com> <CAD5OKxueCTEo7DtuiCGamo7XaHZOfBM4iVWgzCFj8T2iypOfyg@mail.gmail.com> <e16b2faa-19ed-2cc0-0276-e0d8e27a4cf1@cisco.com> <CAMRcRGRho_6411Z3E+LgT9w12VqKQUkNgDxPYcikT-LRs7xyeQ@mail.gmail.com> <CAD5OKxt3gKipBE21MsrPt5KoRJ3exJzUUkX3Ls3xGOEYhGRMaw@mail.gmail.com> <CAMRcRGTCxCXL=_cKwiOtJ-NY2cnt7QikxO7g-Zx6fv2X_rGGyA@mail.gmail.com> <4238df55-84d4-46b0-7348-dc0001640cfc@cisco.com> <CAD5OKxvNECsRi+zvoD5ZqeqEWyMHZCpByRbOXBqonW1a6-7GxQ@mail.gmail.com> <CAD5OKxuQOFHiV7RwmAnU0sk7XWLL4YgOq4JBsoAKopfYmXg-=Q@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 2 Apr 2018 11:51:33 -0700
Message-ID: <CAMRcRGRSo27XCoHsMao9JZs1cVDLa7qN4uc2Yy+K72L7-p2-oQ@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11426378257cb50568e21439"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jzGBRqyE3wy3L__hlHSxTpFZsFM>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-18.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 18:51:37 -0000

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

On Mon, Apr 2, 2018 at 11:38 AM, Roman Shpount <roman@telurix.com> wrote:

> On Mon, Apr 2, 2018 at 2:08 PM, Roman Shpount <roman@telurix.com> wrote:
>
>> Hi Flemming,
>>
>> On Mon, Apr 2, 2018 at 9:42 AM, Flemming Andreasen <fandreas@cisco.com>
>> wrote:
>>
>>>
>>> On 4/1/18 9:42 PM, Suhas Nandakumar wrote:
>>>
>>>
>>>
>>> On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount <roman@telurix.com> wrote:
>>>
>>>> Hi Flemming,
>>>>
>>>> I think the draft should have used SHOULD instead of MUST there, as in:
>>>>
>>>> If an agent uses separate ports for RTP and RTCP, the agent
>>>> MUST include an SDP rtcp attribute in the "m=" section, as described in
>>>> [RFC3605].  In the cases where the port number for the RTCP is one higher
>>>> than the RTP port and RTCP component address is same as the address of the
>>>> RTP component, the SDP rtcp attribute *SHOULD NOT* be included.
>>>>
>>>>
>>> Happy to make that change. Flemming, what do you think ?
>>>
>>> I think it's fine, but it could just as well be "MAY be included".
>>>
>>
>> I think "SHOULD NOT be included" is cleaner. In the described case rtcp
>> attribute serves no purpose, so there is a reason not to add it. This
>> attribute will not break anything but it really should not be there.
>>
>>
> After thinking about this a bit more "MAY be omitted" also works for me
> and makes more sense together with the previous sentence where rtcp
> attribute MUST be included.
>


[Suhas] Thanks Roman and Flemming. Will update in the next version.

> _____________
> Roman Shpount
>
>
>

--001a11426378257cb50568e21439
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, Apr 2, 2018 at 11:38 AM, Roman Shpount <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:roman@telurix.com" target=3D"_blank">roman@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"><div dir=3D"ltr"><div c=
lass=3D"gmail_extra"><span class=3D""><div><div class=3D"m_2903123315202552=
180gmail_signature" data-smartmail=3D"gmail_signature">On Mon, Apr 2, 2018 =
at 2:08 PM, Roman Shpount <span dir=3D"ltr">&lt;<a href=3D"mailto:roman@tel=
urix.com" target=3D"_blank">roman@telurix.com</a>&gt;</span> wrote:<br></di=
v></div></span><div class=3D"gmail_quote"><span class=3D""><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=
=3D"m_2903123315202552180m_7396668075697656374gmail_signature" data-smartma=
il=3D"gmail_signature">Hi Flemming,</div><span><div class=3D"m_290312331520=
2552180m_7396668075697656374gmail_signature" data-smartmail=3D"gmail_signat=
ure"><br></div><div class=3D"m_2903123315202552180m_7396668075697656374gmai=
l_signature" data-smartmail=3D"gmail_signature">On Mon, Apr 2, 2018 at 9:42=
 AM, Flemming Andreasen <span dir=3D"ltr">&lt;<a href=3D"mailto:fandreas@ci=
sco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;</span> wrote:<br></di=
v></span></div><div class=3D"gmail_quote"><span><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><span><br>
    <div class=3D"m_2903123315202552180m_7396668075697656374m_-724482783592=
1304023moz-cite-prefix">On 4/1/18 9:42 PM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div>
        <div dir=3D"auto"><br>
        </div>
        <br>
        <div class=3D"gmail_quote">
          <div dir=3D"auto">On Sun, Apr 1, 2018 at 6:05 PM Roman Shpount
            &lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roma=
n@telurix.com</a>&gt; wrote:<br>
          </div>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div>Hi Flemming,
              <div><br>
              </div>
              <div>I think the draft should have used SHOULD instead of
                MUST there, as in:</div>
              <div><br>
              </div>
              <blockquote style=3D"margin:0 0 0 40px;border:none;padding:0p=
x">
                <div>If an agent uses separate ports for RTP and RTCP,
                  the agent MUST=C2=A0include an SDP rtcp attribute in the
                  &quot;m=3D&quot; section, as described in [RFC3605].=C2=
=A0 In the cases
                  where the port number for the RTCP is one higher than
                  the RTP port and RTCP component address is same as the
                  address of the RTP component, the SDP rtcp attribute <b>S=
HOULD
                    NOT</b> be included.</div>
              </blockquote>
            </div>
          </blockquote>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">Happy to make that change. Flemming, what do
            you think ?</div>
        </div>
      </div>
    </blockquote></span>
    I think it&#39;s fine, but it could just as well be &quot;MAY be includ=
ed&quot;.=C2=A0<br></div></blockquote><div><br></div></span><div>I think &q=
uot;SHOULD NOT be included&quot; is cleaner. In the described case rtcp att=
ribute serves no purpose, so there is a reason not to add it. This attribut=
e will not break anything but it really should not be there.</div><div><br>=
</div></div></div></div></blockquote><div><br></div></span><div>After think=
ing about this a bit more &quot;MAY be omitted&quot; also works for me and =
makes more sense together with the previous sentence where rtcp attribute M=
UST be included.</div></div></div></div></blockquote><div><br></div><div><b=
r></div><div>[Suhas] Thanks Roman and Flemming. Will update in the next ver=
sion.</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gm=
ail_extra"><div class=3D"gmail_quote"><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"m_2903123315202552180gmail_signature">_____________<span class=
=3D"HOEnZb"><font color=3D"#888888"><br>Roman Shpount</font></span></div></=
div><br class=3D"m_2903123315202552180gmail-Apple-interchange-newline">

=C2=A0</div></div></div></div>
</blockquote></div><br></div></div>

--001a11426378257cb50568e21439--


From nobody Mon Apr  2 13:50:51 2018
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 C1BF512D940; Mon,  2 Apr 2018 13:50:44 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1.t1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152270224474.26554.17874469923323277712@ietfa.amsl.com>
Date: Mon, 02 Apr 2018 13:50:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AL5hBJ6m9cK96wq4_Py7yXrOCG4>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-20.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 20:50:45 -0000

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

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

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


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-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.

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


From nobody Mon Apr  2 13:52:50 2018
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 9D8CE12D94A for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 13:52:48 -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 xm4-Ct2Yv_bX for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 13:52:46 -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 723A312D944 for <mmusic@ietf.org>; Mon,  2 Apr 2018 13:52:46 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id m69so6991167vka.8 for <mmusic@ietf.org>; Mon, 02 Apr 2018 13:52:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=n6hIZDk5Y33JbuSj1hKDx5COyqwwt/IAL/RYaDXM3G4=; b=iBx8kqQgwOlrf1ivvEC7NOFnCYIO4dKvcJs6NvFVFkSasNulkU5q1s4p/YVfW7IOEH LViiNvN/v0Crd8IRGFTRF5KxLlYfRHM0NhrEhvaGWVi9r1Hpm4nUu1XFbKw7WxqlFO4o v821Ijjok7IzkC08BhsIveHZFYw0Xi2KCUvo/+v97zBqDSK57VsW4cr9EdB/3zpAQfDd +EG/f6qYJmo4+2h9f/rc4ZRtcIlBuMEotCGb2P+FEooafkfl3AM8HHvHEbzOaSfEbtfY IQsdYQM76VNTrKVrYqbJL7zOGRykWHP68/mPWj0Azkwrg5bd5iRtDt5spSz3/ATjXeA2 V5rQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=n6hIZDk5Y33JbuSj1hKDx5COyqwwt/IAL/RYaDXM3G4=; b=cYXkoOSCF9JOEVIo6LWVDCoFbMLtLfT14+IvVhuzViGdKlj+fjfFeuxBY1ZQJG+AWO 03e7B2br3eW7ErTniZzMq4pS6zV1gdoroGLSVyXoCTP66R9zPSJYqWCdZSLej8TFkog7 f4GHdxF3Ebpf/vFdY1cf99dxaGi2ZOW3TmKgH+sIC3+fzO3+vyyoU+uDEUsOr/Iz5siJ fRYUnwwCPfK0jPNuCrfNtbUeylaYdMK6Zktkufo3xuqWqiGayMUl/ZI0wJ3augyzcuFT MBii5pMXI91j88bL+SJtl7nT/WK6zihe8D7pk04c3reXenhvx28PS8p5y4n9Ej5x5JWf H+qw==
X-Gm-Message-State: ALQs6tCSon7rAxWpTGfRmglf5a+/en+kbiqlzlt+Pjh80EQNDJR2EbBR 4zzlOCgBwuB8xl9WQzGZZOva3+ngK3N95/4wcVI=
X-Google-Smtp-Source: AIpwx48ewGWNHMi5CDCgnVcgv2WaKw7w4upXEqxRW0nmVb7OOLRehIpSWmxQb6Px3qCX9GraC+Y/H/Z7lkC+9RbhVl4=
X-Received: by 10.31.140.196 with SMTP id o187mr3023716vkd.4.1522702365246; Mon, 02 Apr 2018 13:52:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Mon, 2 Apr 2018 13:52:44 -0700 (PDT)
In-Reply-To: <152270224474.26554.17874469923323277712@ietfa.amsl.com>
References: <152270224474.26554.17874469923323277712@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 2 Apr 2018 13:52:44 -0700
Message-ID: <CAMRcRGToQh+XwCbRZ9T_dD_J0Z7c7jmTSYNWFE0_=U0KavmCPw@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11426378944c670568e3c537"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ljDZzy6fzeNIVP2XoiLngIXDqIg>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-20.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 20:52:49 -0000

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

Version 20 address RTCP port review feedback and first pass at ICE Mismatch
feedback. IANA section to use iesg contact name is still unresolved.

Flemming/Roman, please let me know if your concerns are met.

Cheers
Suhas

On Mon, Apr 2, 2018 at 1:50 PM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : Session Description Protocol (SDP) Offer/Answer
> procedures for Interactive Connectivity Establishment (ICE)
>         Authors         : Marc Petit-Huguenin
>                           Suhas Nandakumar
>                           Ari Keranen
>         Filename        : draft-ietf-mmusic-ice-sip-sdp-20.txt
>         Pages           : 42
>         Date            : 2018-04-02
>
> Abstract:
>    This document describes Session Description Protocol (SDP) Offer/
>    Answer procedures for carrying out Interactive Connectivity
>    Establishment (ICE) between the agents.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-20
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-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.
>
> 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
>

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

<div dir=3D"ltr">Version 20 address RTCP port review feedback and first pas=
s at ICE Mismatch feedback. IANA section to use iesg contact name is still =
unresolved.<div><br></div><div>Flemming/Roman, please let me know if your c=
oncerns are met.</div><div><br></div><div>Cheers</div><div>Suhas</div></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Apr 2, 2=
018 at 1:50 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ie=
tf.org" target=3D"_blank">internet-drafts@ietf.org</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>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-<wbr>20.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-04-02<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc=
/draft-ietf-mmusic-ice-sip-<wbr>sdp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-i=
etf-mmusic-ice-sip-sdp-<wbr>20</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-20" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<=
wbr>doc/html/draft-ietf-mmusic-<wbr>ice-sip-sdp-20</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-20" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?<wb=
r>url2=3Ddraft-ietf-mmusic-ice-<wbr>sip-sdp-20</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-<wbr>drafts/</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>

--001a11426378944c670568e3c537--


From nobody Mon Apr  2 13:57:37 2018
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 DA07912D94D for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 13:57:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOmLzGZVVx-y for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 13:57:33 -0700 (PDT)
Received: from mail-pl0-x235.google.com (mail-pl0-x235.google.com [IPv6:2607:f8b0:400e:c01::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 BAD1A12D94C for <mmusic@ietf.org>; Mon,  2 Apr 2018 13:57:33 -0700 (PDT)
Received: by mail-pl0-x235.google.com with SMTP id s24-v6so5753219plq.6 for <mmusic@ietf.org>; Mon, 02 Apr 2018 13:57: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=KDl0mLMAnq3J7CN+5gZ0sU5khCoxK5I564QbgHENCmY=; b=b8lqU13RfPkgPOQbxc029+SeLGoj8RNiR/6ObdMGJiqfd1jsxkQB4Qs11Epn70dYdf Vj0uBlrrMebz7LkK6A4ak6Bz38DlTmTP/Mw1Itf9p5ne0rJ278/1tkUJC+5SU4tQhVpk 0PYfgnuIWjpuAinY1ZD+Mv4fR76wlaSYHyGwWskdzMIqF/pC9EVUJRmnjIdlhcOfDuRk 0JXm1EclEugExs9z+DRnwSzqicoC2MmNZhOV5/16UTgf2pFs92mx9Ygsi3rq6DGBqw/Q PlBTAARyXUreoK6WvNMGjkYB/L5O1uMzzVWp0ICJDPhiLDnD7hUhtTZvq3PUd8earC9c 3H9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KDl0mLMAnq3J7CN+5gZ0sU5khCoxK5I564QbgHENCmY=; b=XbOqVmCD1zOgQqg9eA6Vrvx+HpHSxVy582ul+wNXPS8xZm3Fv7nX+VVZPIOTI3qH2N MrcZOTNEXnYO/vYRpSQpjIZoiGp6K1C5kKE5qCAdsSm1+IiIbwRuH84f0fNqJ20O3Du7 5vfzducxR0WYVIvpBlRfWmCyT0wdFvEIWmM9InObsMo0mS45t/yaXEt31dJkzKaGeJVj Xs+ozadc3PSI97ujQpR45fJO1xMGcfkbsn+sFuI6qr9S1yU7PQLwWMQ6a8d+Q5jbIT7E Q1h9JC5oWq6TOSb2nBsQ4vvn1IQW5kY/cEPj7+Wbj89PrKXzofZZQm2WeFdZ2P5QmOX9 6icw==
X-Gm-Message-State: AElRT7G7oz6+rPu4EM3IRLFxgKXpO7MsPicoSP5pThEKgMCVau3vlYDi WbLkH7bXUus/vbLnp0un7LImPGMc
X-Google-Smtp-Source: AIpwx4+yxSD8cv8KqjzKGuu0XlkFiFz3ib5MBSgKV8LTQ3uCCTsPvOc+DNdEirYFwYh/GbfTrhjOcg==
X-Received: by 2002:a17:902:24c7:: with SMTP id l7-v6mr11146654plg.320.1522702652685;  Mon, 02 Apr 2018 13:57:32 -0700 (PDT)
Received: from mail-pl0-f53.google.com (mail-pl0-f53.google.com. [209.85.160.53]) by smtp.gmail.com with ESMTPSA id p6sm2247149pfk.104.2018.04.02.13.57.31 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Apr 2018 13:57:32 -0700 (PDT)
Received: by mail-pl0-f53.google.com with SMTP id g20-v6so5745399plo.9 for <mmusic@ietf.org>; Mon, 02 Apr 2018 13:57:31 -0700 (PDT)
X-Received: by 10.101.93.136 with SMTP id f8mr2512332pgt.265.1522702651770; Mon, 02 Apr 2018 13:57:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.241.132 with HTTP; Mon, 2 Apr 2018 13:57:31 -0700 (PDT)
In-Reply-To: <CAMRcRGToQh+XwCbRZ9T_dD_J0Z7c7jmTSYNWFE0_=U0KavmCPw@mail.gmail.com>
References: <152270224474.26554.17874469923323277712@ietfa.amsl.com> <CAMRcRGToQh+XwCbRZ9T_dD_J0Z7c7jmTSYNWFE0_=U0KavmCPw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 2 Apr 2018 16:57:31 -0400
X-Gmail-Original-Message-ID: <CAD5OKxttrtbYx0zx3S=Wx7uTreoKYMMj3o0JU6cuX2+oZRMYhA@mail.gmail.com>
Message-ID: <CAD5OKxttrtbYx0zx3S=Wx7uTreoKYMMj3o0JU6cuX2+oZRMYhA@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="089e08251f60a84d4b0568e3d636"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/O_HNVjKees023fZ7W7PMQWHBNxA>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-ice-sip-sdp-20.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 20:57:36 -0000

--089e08251f60a84d4b0568e3d636
Content-Type: text/plain; charset="UTF-8"

Suhas,

RTCP section looks good to me.

Regards,

_____________
Roman Shpount

On Mon, Apr 2, 2018 at 4:52 PM, Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Version 20 address RTCP port review feedback and first pass at ICE
> Mismatch feedback. IANA section to use iesg contact name is still
> unresolved.
>
> Flemming/Roman, please let me know if your concerns are met.
>
> Cheers
> Suhas
>
> On Mon, Apr 2, 2018 at 1:50 PM, <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Multiparty Multimedia Session Control WG
>> of the IETF.
>>
>>         Title           : Session Description Protocol (SDP) Offer/Answer
>> procedures for Interactive Connectivity Establishment (ICE)
>>         Authors         : Marc Petit-Huguenin
>>                           Suhas Nandakumar
>>                           Ari Keranen
>>         Filename        : draft-ietf-mmusic-ice-sip-sdp-20.txt
>>         Pages           : 42
>>         Date            : 2018-04-02
>>
>> Abstract:
>>    This document describes Session Description Protocol (SDP) Offer/
>>    Answer procedures for carrying out Interactive Connectivity
>>    Establishment (ICE) between the agents.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20
>> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-sdp-20
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-ice-sip-sdp-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.
>>
>> 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
>>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr">Suhas,<div><br></div><div>RTCP section looks good to me.</=
div><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_s=
ignature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Mon, Apr 2, 2018 at 4:52 PM, Suhas Nandak=
umar <span dir=3D"ltr">&lt;<a href=3D"mailto:suhasietf@gmail.com" target=3D=
"_blank">suhasietf@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:1ex"><div dir=3D"ltr">Version 20 address RTCP port review feedback and=
 first pass at ICE Mismatch feedback. IANA section to use iesg contact name=
 is still unresolved.<div><br></div><div>Flemming/Roman, please let me know=
 if your concerns are met.</div><div><br></div><div>Cheers</div><span class=
=3D"HOEnZb"><font color=3D"#888888"><div>Suhas</div></font></span></div><di=
v class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Mon, Apr 2, 2018 at 1:50 PM,  <span dir=3D"ltr">&lt;=
<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-draf=
ts@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Session Description Protocol (SDP) Offer/Answer procedures for Interactive=
 Connectivity Establishment (ICE)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Marc=
 Petit-Huguenin<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Suhas Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ari Keranen<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-ice-sip-sdp-<wbr>20.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 42<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-04-02<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes Session Description Protocol (SDP) Off=
er/<br>
=C2=A0 =C2=A0Answer procedures for carrying out Interactive Connectivity<br=
>
=C2=A0 =C2=A0Establishment (ICE) between the agents.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-sip-sdp/"=
 rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr>oc=
/draft-ietf-mmusic-ice-sip-s<wbr>dp/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20" re=
l=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr<wbr>aft-i=
etf-mmusic-ice-sip-sdp-20</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-ice-sip-=
sdp-20" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
<wbr>oc/html/draft-ietf-mmusic-ice-<wbr>sip-sdp-20</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-ice-sip-sd=
p-20" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?u<w=
br>rl2=3Ddraft-ietf-mmusic-ice-sip-<wbr>sdp-20</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</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" 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>

--089e08251f60a84d4b0568e3d636--


From nobody Mon Apr  2 15:54:41 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C476C1252BA; Mon,  2 Apr 2018 15:54:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com>
Date: Mon, 02 Apr 2018 15:54:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DrFsz9OnCstNVHoEnqWb3D1OnnU>
Subject: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 22:54:36 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-sip-14: Discuss

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


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


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



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

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?

   'application/trickle-ice-sdpfrag' bodies do not interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.

   sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.


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

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that's not true.

   include in each "m="-line a "a=mid:" attribute in accordance to
   [RFC5888].

Why is this required?

   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it's an implicit ACK of your INFO?

   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes.

This whole section needs to be rewritten to make clear what's going on:

    candidates are grouped in sections headed by "pseudo" m=lines
    These sections contain a=mid values which point back to the true m=line.



From nobody Mon Apr  2 16:46:03 2018
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 4005212E035 for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 16:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 OjDCnPUr_cKE for <mmusic@ietfa.amsl.com>; Mon,  2 Apr 2018 16:45:55 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 047A612E049 for <mmusic@ietf.org>; Mon,  2 Apr 2018 16:45:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21629; q=dns/txt; s=iport; t=1522712755; x=1523922355; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=M6LB+cASRJSWwBnguS/XdjCwLHJSLK7jmy7OuyvQBzA=; b=Issx4bM0N9YcJOfrfDYKj8LlerXPxSUMotRhmtVObA40Sbvx0BpC++qj 0+EO8DbRM3FrWAqWNkBrj2Hw47aF9XMJWEwmndE2403xPE6DUMbrXvKD3 KtBvrKra+kYpd+hkBuxGEUQSJucnkc9ACQavD0f0VL5sQX+CqJC5FVKl3 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DAAgCiv8Ja/5RdJa0ZAUMZAQEBAQE?= =?us-ascii?q?BAQEBAQEBBwEBAQEBgk11YW8og1yIAI0DgUspgQ+SU4F6CxgBDIQTTAKEMiE?= =?us-ascii?q?0GAECAQEBAQEBAmsohSQBAQEBAgEBASFLEAsLGCAKAgInMAYBDAYCAQGEfAU?= =?us-ascii?q?ID5EFnFOCHB+ENoNtgiAFh2GBVD+BDCKCYoMRAQECAYFDgxaCVAKHLYkXhnY?= =?us-ascii?q?IhVGIVwaHQIR3iRWGaIElHDiBUk0jFTqCQ4IgFxGOISMwAQGOUQEB?=
X-IronPort-AV: E=Sophos; i="5.48,398,1517875200"; d="scan'208,217"; a="93066740"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Apr 2018 23:45:54 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w32NjrJO011063; Mon, 2 Apr 2018 23:45:53 GMT
To: Suhas Nandakumar <suhasietf@gmail.com>, mmusic WG <mmusic@ietf.org>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com>
Date: Mon, 2 Apr 2018 19:45:53 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------51C827121F1E08F4BCE1C2FF"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UYOxdCAngB0QM6eOUJIYXnS-PIE>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 02 Apr 2018 23:46:02 -0000

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

I'm still having a hard time following this - let me try and elaborate 
below

On 4/2/18 1:56 PM, Suhas Nandakumar wrote:
> Hi Flemming
>
> Moving the discussion in a separate thread to keep it focussed. How 
> about following rewording of the section 3.2.5.
>
>
>         3.2.5
>         <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5>.
>         Verifying ICE Support
>
>
>
>     The agents will proceed with the ICE procedures defined in [ICE-BIS 
> <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>]
>     and this specification if, for each data stream in the SDP it
>     received, the default destination for each component of that data
>     stream appears in a candidate attribute.  For example, in the case of
>     RTP, the IP address and port in the "c=" and "m=" lines,
>     respectively, appear in a candidate attribute and the value in the
>     rtcp attribute appears in a candidate attribute.
So far so good.
>     If this condition is not met, the agents MUST process the SDP based on
>     normal [RFC3264 <https://tools.ietf.org/html/rfc3264>] procedures, without using any of the ICE mechanisms
>     described in the remainder of this specification with the following
>     exceptions:
Ok, so at this point, there is mismatch between at least one default 
destination in a component and all of its corresponding candidate 
attributes. The above says to do normal offer/answer instead of ICE, 
except as follows:

>     1.  An controlled/responding agent MUST follow the rules of
>         section 11 of [ICE-BIS 
> <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>], which describe keepalive procedures
>         for all agents.
Earlier, the document says the answerer acts as the responding agent, 
and the controlling/controlled roles are determined by ICE procedures. 
Here you seem to say responding = controlled. In any case, it must mean 
we are dealing with the answerer (which would be easiser to understand 
from an O/A point of view which is the perspective this documenet should 
have to the extent possible).

So it says, the answer will still follow the keep-alive procedures, but 
we are not doing ICE. I'm not quite sure what that means, but I'm 
guessing it means we must stop sending keepalives if we were previously 
sending them (since the ICE session is terminated).
> Also, If the default candidates were relayed
>         candidates learned through a TURN server, the controlled agent
>         MUST create permissions in the TURN server for the IP addresses
>         learned from its peer in the offer SDP it just received.
>         If this is not done, initial packets in the data stream from the
>         peer may be lost.
Here it's not entirely clear whether this is a rule for the offerer or 
the answerer:
1) Answerer
The default candidates were present in the offer and apparently they are 
marked as relayed candidates. However, since the text refers to 
controlled, per the above, this cannot be test for the answerer.

2) Offerer
This must be an answer SDP that came back to us, however the text 
clearly talks about the offer SDP.

I'm confused at this point.

>
>     2.  On the other hand, if the controlled agent is not proceeding
>         with ICE because there were a=candidate attributes, but none that
>         matched the default destination of the data stream, it MUST include
>         an a=ice-mismatch attribute in its answer and MAY omit a=candidate
>         attributes for such data streams.
Above you said this list was supposed to be exceptions to this rule, but 
this is the rule itself repeated !?

Let me know if I am missing something here (but in either case, we need 
to make the write-up clearer).


Thanks

-- Flemming

>   SeeSection 9.2.2 
> <https://tools.ietf..org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2>  for a
>         discussion of cases where this can happen. This specification provides
>         no guidance on how an controlled agent should proceed in such a
>         failure case.
>
>
>
> Cheers
> Suhas
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--------------51C827121F1E08F4BCE1C2FF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    I'm still having a hard time following this - let me try and
    elaborate below <br>
    <br>
    <div class="moz-cite-prefix">On 4/2/18 1:56 PM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">
        <div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">Hi
          Flemming</div>
        <div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><br>
        </div>
        <div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">Moving
          the discussion in a separate thread to keep it focussed. How
          about following rewording of the section 3.2.5. </div>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class="gmail-h4" style="line-height:0pt;display:inline;white-space:pre;font-family:monospace;font-size:1em;font-weight:bold">
</span></pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class="gmail-h4" style="line-height:0pt;display:inline;white-space:pre;font-family:monospace;font-size:1em;font-weight:bold">
</span></pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class="gmail-h4" style="line-height:0pt;display:inline;white-space:pre;font-family:monospace;font-size:1em;font-weight:bold"><h4 style="line-height:0pt;display:inline;white-space:pre;font-family:monospace;font-size:1em;font-weight:bold"><a class="gmail-selflink" name="section-3.2.5" href="https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5" style="color:black;text-decoration:none" moz-do-not-send="true">3.2.5</a>.  Verifying ICE Support</h4></span>

   The agents will proceed with the ICE procedures defined in [<a href="https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" title="&quot;Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols&quot;" style="color:rgb(17,85,204)" moz-do-not-send="true">ICE-BIS</a>]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the "c=" and "m=" lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.
</pre>
      </div>
    </blockquote>
    So far so good. <br>
    <blockquote type="cite"
cite="mid:CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com">
      <div dir="ltr">
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
   If this condition is not met, the agents MUST process the SDP based on
   normal [<a href="https://tools.ietf.org/html/rfc3264" title="&quot;An Offer/Answer Model with Session Description Protocol (SDP)&quot;" style="color:rgb(17,85,204)" moz-do-not-send="true">RFC3264</a>] procedures, without using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:</pre>
      </div>
    </blockquote>
    Ok, so at this point, there is mismatch between at least one default
    destination in a component and all of its corresponding candidate
    attributes. The above says to do normal offer/answer instead of ICE,
    except as follows: <br>
    <br>
    <blockquote type="cite"
cite="mid:CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com">
      <div dir="ltr">
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   1.  An controlled/responding agent MUST follow the rules of </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       section 11 of [<a href="https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" title="&quot;Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols&quot;" style="color:rgb(17,85,204)" moz-do-not-send="true">ICE-BIS</a>], which describe keepalive procedures </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       for all agents. </pre>
      </div>
    </blockquote>
    Earlier, the document says the answerer acts as the responding
    agent, and the controlling/controlled roles are determined by ICE
    procedures. Here you seem to say responding = controlled. In any
    case, it must mean we are dealing with the answerer (which would be
    easiser to understand from an O/A point of view which is the
    perspective this documenet should have to the extent possible). <br>
    <br>
    So it says, the answer will still follow the keep-alive procedures,
    but we are not doing ICE. I'm not quite sure what that means, but
    I'm guessing it means we must stop sending keepalives if we were
    previously sending them (since the ICE session is terminated).  <br>
    <blockquote type="cite"
cite="mid:CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com">
      <div dir="ltr">
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Also, If the default candidates were relayed </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       candidates learned through a TURN server, the controlled agent </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       MUST create permissions in the TURN server for the IP addresses </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       learned from its peer in the offer SDP it just received.  </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       If this is not done, initial packets in the data stream from the </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       peer may be lost.
</pre>
      </div>
    </blockquote>
    Here it's not entirely clear whether this is a rule for the offerer
    or the answerer:<br>
    1) Answerer<br>
    The default candidates were present in the offer and apparently they
    are marked as relayed candidates. However, since the text refers to
    controlled, per the above, this cannot be test for the answerer.<br>
    <br>
    2) Offerer<br>
    This must be an answer SDP that came back to us, however the text
    clearly talks about the offer SDP. <br>
    <br>
    I'm confused at this point. <br>
    <br>
    <blockquote type="cite"
cite="mid:CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com">
      <div dir="ltr">
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">

   2.  On the other hand, if the controlled agent is not proceeding </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       with ICE because there were a=candidate attributes, but none that </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       matched the default destination of the data stream, it MUST include </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       an a=ice-mismatch attribute in its answer and MAY omit a=candidate
       attributes for such data streams. </pre>
      </div>
    </blockquote>
    Above you said this list was supposed to be exceptions to this rule,
    but this is the rule itself repeated !?<br>
    <br>
    Let me know if I am missing something here (but in either case, we
    need to make the write-up clearer). <br>
    <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <blockquote type="cite"
cite="mid:CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com">
      <div dir="ltr">
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"> See <a href="https://tools.ietf..org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2" style="color:rgb(17,85,204)" moz-do-not-send="true">Section 9.2.2</a> for a
       discussion of cases where this can happen. This specification provides </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       no guidance on how an controlled agent should proceed in such a </pre>
        <pre class="gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       failure case.</pre>
        <br class="gmail-Apple-interchange-newline">
        <br>
        <div><br>
        </div>
        <div>Cheers</div>
        <div>Suhas</div>
      </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>

--------------51C827121F1E08F4BCE1C2FF--


From nobody Tue Apr  3 00:29:21 2018
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 1D12C1201FA for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 00:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rPRscfWg7Ymy for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 00:29:17 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 454D8124205 for <mmusic@ietf.org>; Tue,  3 Apr 2018 00:29:17 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id u4so10379645uaf.10 for <mmusic@ietf.org>; Tue, 03 Apr 2018 00:29:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OtxCZw76RqnzOjvFxIV16krJgGS94/xJe5GCrSLfiBc=; b=ddV/sJuCQW1SKpm9ByQklsNVPFrmAXSAmCWjHGurWoo+i+Ct/ZGCzC6CCfGQw0gewP Lc/naEPaGEIPu2TuVRmBG2v12GUk2Mkk9f7WUOYYwg9VZbi+dq9PUghH/tefWhVOMoxS n4i3luWn69gxnPziGNRgN9CoCFufVYWioFDqtuyQ3aGVvp1U1jlrK3bKHM52ZlCaQxAi VXKdgEvuXYsAEAuIIVs65uT8a1OF0NimnNIYqM20a+gBjKfgqlm/ZhiLALmscZgZg4bl wIZjPd86/TMkDSDwOxI9drzeVF9CGGI4QcvjJBK7QkEOrnWNDYjwopty8tyDR57YQCJN VE5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OtxCZw76RqnzOjvFxIV16krJgGS94/xJe5GCrSLfiBc=; b=rTUWHMr3pJUtz0KSmnLDbC5qGce40HfjNDEpf29RPcCJzhF3u8khwgk1V7ICQ/LR4V aPlk9u44DRT3SeLnpo5P8/4oESGMr5fBGSDBLG1AK0eKPFQFALkrqcn7vnRZSAgIT77e msJxKxwXvmWRI2lLRvP91Lm1S5p4t6pQq+7iUJHqLH4QcGlXJvMXN95arnpiXmOiDMtx AJzML97B/NYiYWaq/yA+ZWdTCF4tmhOUWqqXqbBTwrdEQw+YX1df7Rl7wOCRYWp5tDlA ++MKtEPpEX64TXEuPyy0bMQL8ofir0RyFYPhoez7TIH3uJHsiHNd9ksYQTeBnRD6is0y Ztaw==
X-Gm-Message-State: ALQs6tC38ayPOdGb1FYy+FYpdBFaJfUOxTNLftoyjm2cUOxyCYtWgj7g IhLJxFGnKnxTHSxfiPSFbVPZ5nR5RlrCbr61Ej887Q==
X-Google-Smtp-Source: AIpwx4/2w/eqXSbppAF02DJC7V0aiOG+x3X7JfsVX3RTbEQvkI7jA4yfS+ldkF9fixHCsogmutWR/pkEx3YFPBUVmPQ=
X-Received: by 10.159.55.199 with SMTP id q65mr7432089uaq.90.1522740556256; Tue, 03 Apr 2018 00:29:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Tue, 3 Apr 2018 00:29:15 -0700 (PDT)
In-Reply-To: <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 3 Apr 2018 00:29:15 -0700
Message-ID: <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c04c9a6f0d8c80568eca989"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KZieKo7ZrW10yO3iFZw4Rcq9Cpo>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 07:29:20 -0000

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

Hello Flemming

  The original text was take from RFC5245 sections
https://tools.ietf.org/html/rfc5245#section-5.1 and 6.1 where it is defines
procedures for answerer and the offerer for verifying ice support. The
versions pre 13 for the current ice-sip-sdp had the exact same content.

Wondering if we should get back to the original format since it seems to be
more clearer in explaining ?


Thanks
Suhas


On Mon, Apr 2, 2018 at 4:45 PM, Flemming Andreasen <fandreas@cisco.com>
wrote:

> I'm still having a hard time following this - let me try and elaborate
> below
>
> On 4/2/18 1:56 PM, Suhas Nandakumar wrote:
>
> Hi Flemming
>
> Moving the discussion in a separate thread to keep it focussed. How about
> following rewording of the section 3.2.5.
>
>   3.2.5 <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5>.  Verifying ICE Support
>
>    The agents will proceed with the ICE procedures defined in [ICE-BIS <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>]
>    and this specification if, for each data stream in the SDP it
>    received, the default destination for each component of that data
>    stream appears in a candidate attribute.  For example, in the case of
>    RTP, the IP address and port in the "c=" and "m=" lines,
>    respectively, appear in a candidate attribute and the value in the
>    rtcp attribute appears in a candidate attribute.
>
> So far so good.
>
>    If this condition is not met, the agents MUST process the SDP based on
>    normal [RFC3264 <https://tools.ietf.org/html/rfc3264>] procedures, without using any of the ICE mechanisms
>    described in the remainder of this specification with the following
>    exceptions:
>
> Ok, so at this point, there is mismatch between at least one default
> destination in a component and all of its corresponding candidate
> attributes. The above says to do normal offer/answer instead of ICE, except
> as follows:
>
>    1.  An controlled/responding agent MUST follow the rules of
>
>        section 11 of [ICE-BIS <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>], which describe keepalive procedures
>
>        for all agents.
>
> Earlier, the document says the answerer acts as the responding agent, and
> the controlling/controlled roles are determined by ICE procedures. Here you
> seem to say responding = controlled. In any case, it must mean we are
> dealing with the answerer (which would be easiser to understand from an O/A
> point of view which is the perspective this documenet should have to the
> extent possible).
>
> So it says, the answer will still follow the keep-alive procedures, but we
> are not doing ICE. I'm not quite sure what that means, but I'm guessing it
> means we must stop sending keepalives if we were previously sending them
> (since the ICE session is terminated).
>
> Also, If the default candidates were relayed
>
>        candidates learned through a TURN server, the controlled agent
>
>        MUST create permissions in the TURN server for the IP addresses
>
>        learned from its peer in the offer SDP it just received.
>
>        If this is not done, initial packets in the data stream from the
>
>        peer may be lost.
>
> Here it's not entirely clear whether this is a rule for the offerer or the
> answerer:
> 1) Answerer
> The default candidates were present in the offer and apparently they are
> marked as relayed candidates. However, since the text refers to controlled,
> per the above, this cannot be test for the answerer.
>
> 2) Offerer
> This must be an answer SDP that came back to us, however the text clearly
> talks about the offer SDP.
>
> I'm confused at this point.
>
>
>    2.  On the other hand, if the controlled agent is not proceeding
>
>        with ICE because there were a=candidate attributes, but none that
>
>        matched the default destination of the data stream, it MUST include
>
>        an a=ice-mismatch attribute in its answer and MAY omit a=candidate
>        attributes for such data streams.
>
> Above you said this list was supposed to be exceptions to this rule, but
> this is the rule itself repeated !?
>
> Let me know if I am missing something here (but in either case, we need to
> make the write-up clearer).
>
>
> Thanks
>
> -- Flemming
>
>  See Section 9.2.2 <https://tools.ietf..org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2> for a
>        discussion of cases where this can happen. This specification provides
>
>        no guidance on how an controlled agent should proceed in such a
>
>        failure case.
>
>
>
>
> Cheers
> Suhas
>
>
> _______________________________________________
> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>
>
>

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

<div dir=3D"ltr">Hello Flemming<div><br></div><div>=C2=A0 The original text=
 was take from RFC5245 sections=C2=A0<a href=3D"https://tools.ietf.org/html=
/rfc5245#section-5.1">https://tools.ietf.org/html/rfc5245#section-5.1</a> a=
nd 6.1 where it is defines procedures for answerer and the offerer for veri=
fying ice support. The versions pre 13 for the current ice-sip-sdp had the =
exact same content.=C2=A0</div><div><br></div><div>Wondering if we should g=
et back to the original format since it seems to be more clearer in explain=
ing ?</div><div><br></div><div><br></div><div>Thanks</div><div>Suhas</div><=
div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Mon, Apr 2, 2018 at 4:45 PM, 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:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    I&#39;m still having a hard time following this - let me try and
    elaborate below <br><span class=3D"">
    <br>
    <div class=3D"m_8509342672748520900moz-cite-prefix">On 4/2/18 1:56 PM, =
Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial">Hi
          Flemming</div>
        <div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial"><br>
        </div>
        <div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial">Moving
          the discussion in a separate thread to keep it focussed. How
          about following rewording of the section 3.2.5.=C2=A0</div>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"m_8509342672748520900g=
mail-h4" style=3D"line-height:0pt;display:inline;white-space:pre-wrap;font-=
family:monospace;font-size:1em;font-weight:bold">
</span></pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"m_8509342672748520900g=
mail-h4" style=3D"line-height:0pt;display:inline;white-space:pre-wrap;font-=
family:monospace;font-size:1em;font-weight:bold">
</span></pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"m_8509342672748520900g=
mail-h4" style=3D"line-height:0pt;display:inline;white-space:pre-wrap;font-=
family:monospace;font-size:1em;font-weight:bold"><h4 style=3D"line-height:0=
pt;display:inline;white-space:pre-wrap;font-family:monospace;font-size:1em;=
font-weight:bold"><a class=3D"m_8509342672748520900gmail-selflink" name=3D"=
m_8509342672748520900_section-3.2.5" href=3D"https://tools.ietf.org/html/dr=
aft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5" style=3D"color:black;text-dec=
oration:none" target=3D"_blank">3.2.5</a>.  Verifying ICE Support</h4></spa=
n>

   The agents will proceed with the ICE procedures defined in [<a href=3D"h=
ttps://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" ti=
tle=3D"&quot;Interactive Connectivity Establishment (ICE): A Protocol for N=
etwork Address Translator (NAT) Traversal for Offer/Answer Protocols&quot;"=
 style=3D"color:rgb(17,85,204)" target=3D"_blank">ICE-BIS</a>]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the &quot;c=3D&quot; and &quot;m=3D&quot=
; lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.
</pre>
      </div>
    </blockquote></span>
    So far so good. <br><span class=3D"">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">   If this condition is not met, the =
agents MUST process the SDP based on
   normal [<a href=3D"https://tools.ietf.org/html/rfc3264" title=3D"&quot;A=
n Offer/Answer Model with Session Description Protocol (SDP)&quot;" style=
=3D"color:rgb(17,85,204)" target=3D"_blank">RFC3264</a>] procedures, withou=
t using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:</pre>
      </div>
    </blockquote></span>
    Ok, so at this point, there is mismatch between at least one default
    destination in a component and all of its corresponding candidate
    attributes. The above says to do normal offer/answer instead of ICE,
    except as follows: <br><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"></pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">   1.  An controlled/responding agent=
 MUST follow the rules of </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       section 11 of [<a href=3D"http=
s://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" title=
=3D"&quot;Interactive Connectivity Establishment (ICE): A Protocol for Netw=
ork Address Translator (NAT) Traversal for Offer/Answer Protocols&quot;" st=
yle=3D"color:rgb(17,85,204)" target=3D"_blank">ICE-BIS</a>], which describe=
 keepalive procedures </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       for all agents. </pre>
      </div>
    </blockquote></span>
    Earlier, the document says the answerer acts as the responding
    agent, and the controlling/controlled roles are determined by ICE
    procedures. Here you seem to say responding =3D controlled. In any
    case, it must mean we are dealing with the answerer (which would be
    easiser to understand from an O/A point of view which is the
    perspective this documenet should have to the extent possible). <br>
    <br>
    So it says, the answer will still follow the keep-alive procedures,
    but we are not doing ICE. I&#39;m not quite sure what that means, but
    I&#39;m guessing it means we must stop sending keepalives if we were
    previously sending them (since the ICE session is terminated).=C2=A0 <b=
r><span class=3D"">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">Also, If the default candidates were =
relayed </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       candidates learned through a T=
URN server, the controlled agent </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       MUST create permissions in the=
 TURN server for the IP addresses </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       learned from its peer in the o=
ffer SDP it just received.  </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       If this is not done, initial p=
ackets in the data stream from the </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       peer may be lost.
</pre>
      </div>
    </blockquote></span>
    Here it&#39;s not entirely clear whether this is a rule for the offerer
    or the answerer:<br>
    1) Answerer<br>
    The default candidates were present in the offer and apparently they
    are marked as relayed candidates. However, since the text refers to
    controlled, per the above, this cannot be test for the answerer.<br>
    <br>
    2) Offerer<br>
    This must be an answer SDP that came back to us, however the text
    clearly talks about the offer SDP. <br>
    <br>
    I&#39;m confused at this point. <br><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">
   2.  On the other hand, if the controlled agent is not proceeding </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       with ICE because there were a=
=3Dcandidate attributes, but none that </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       matched the default destinatio=
n of the data stream, it MUST include </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       an a=3Dice-mismatch attribute =
in its answer and MAY omit a=3Dcandidate
       attributes for such data streams. </pre>
      </div>
    </blockquote></span>
    Above you said this list was supposed to be exceptions to this rule,
    but this is the rule itself repeated !?<br>
    <br>
    Let me know if I am missing something here (but in either case, we
    need to make the write-up clearer). <br>
    <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <blockquote type=3D"cite"><span class=3D"">
      <div dir=3D"ltr">
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)"> See <a href=3D"https://tools.ietf..o=
rg/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2" style=3D"color:rgb(=
17,85,204)" target=3D"_blank">Section 9.2.2</a> for a
       discussion of cases where this can happen. This specification provid=
es </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       no guidance on how an controll=
ed agent should proceed in such a </pre>
        <pre class=3D"m_8509342672748520900gmail-newpage" style=3D"font-sty=
le:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weigh=
t:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-st=
yle:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0p=
x;margin-bottom:0px;color:rgb(0,0,0)">       failure case.</pre>
        <br class=3D"m_8509342672748520900gmail-Apple-interchange-newline">
        <br>
        <div><br>
        </div>
        <div>Cheers</div>
        <div>Suhas</div>
      </div>
      <br>
      <fieldset class=3D"m_8509342672748520900mimeAttachmentHeader"></field=
set>
      <br>
      </span><pre>______________________________<wbr>_________________
mmusic mailing list
<a class=3D"m_8509342672748520900moz-txt-link-abbreviated" href=3D"mailto:m=
music@ietf.org" target=3D"_blank">mmusic@ietf.org</a>
<a class=3D"m_8509342672748520900moz-txt-link-freetext" href=3D"https://www=
.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">https://www.ietf.org/m=
ailman/<wbr>listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
  </div>

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

--94eb2c04c9a6f0d8c80568eca989--


From nobody Tue Apr  3 00:29:54 2018
Return-Path: <adam@nostrum.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 09EB8124205; Tue,  3 Apr 2018 00:29:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
Date: Tue, 03 Apr 2018 00:29:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Njei4mMkyiyYFLIjH52OJsBVZGo>
Subject: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 07:29:53 -0000

Adam Roach has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-sip-14: Discuss

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


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


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



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

Thanks to everyone who worked on this document. I have a couple of concerns that
need to be cleared up before the document can move forward.

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

§4.3.4 discusses the interaction of 3PCC with the trickle ICE mechanism.
Unfortunately, the diagrams used in this section do not show a 3PCC signaling
flow; they show a two-party call flow with an offerless INVITE. A 3PCC call flow
would necessarily involve a 3PCC controller sending an offerless INVITE to one
party, receiving an offer from that party (typically in a reliable provisional
response or in a 200 OK), and then sending an INVITE to the other party
containing that offer.

The text in this section matches the diagrams, and consequently does not appear
to be an analysis of 3PCC behavior. It is an analysis of two-party offerless
INVITE behavior.

If this section remains, it needs to be substantially re-worked: the diagrams
need to show three parties, with a 3PCC controller performing the controlling
role as described in RFC 3725. While I haven't stepped through the implications
for Trickle ICE when a controller is actually involved and is moving offers and
answers around between different message types, I suspect that the analysis in
here is substantially different once this starts happening.

I would personally be okay if the entire section were removed; however, I
have no desire to override working group consensus regarding the value of a
section dealing with 3PCC considerations.

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

The second issue doesn't necessarily pertain to this document per se as much
as it does the interaction among this document, draft-ietf-ice-trickle (Trickle
ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep
(JSEP). The problem doesn't lie with any single document, but in the overall
result of how they're currently structured.

JSEP (in the RFC editor queue) refers to the "a=end-of-candidates" SDP attribute
as appearing in Trickle ICE, section 9.3, which was true at one point in time.
Somewhere along the line, this attribute's definition was moved from there
into this document.

There are several ways to fix this, each with their own drawbacks:

1. Move the SDP syntax for "a=end-of-candidates" back into the Trickle ICE
   draft. Drawback: Trickle ICE does not currently define any normative SDP
   behavior; and, in fact, could work in a system that doesn't use SDP at all.

2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant from the
   perspective that ICE SDP defines SDP syntax for ICE in general (for both
   SIP and JSEP), and such a move aggregates all of the SDP syntax into a
   single document that is already necessary to reference from any document
   that uses SDP for Trickle ICE. Drawback: the document doesn't presently
   discuss Trickle ICE at all, and this would require a somewhat awkward
   section that basically says "If you use [Trickle ICE] with SDP, the syntax
   for the end-of-candidate marker is..."

3. Change JSEP to normatively depend on this document for the
   "a=end-of-candidates" syntax. Drawback: This document is extremely
   SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC 3264
   behavior, independent of any SIP semantics.  Forcing JSEP to normatively
   depend on a SIP specific document for a simple attribute syntax definition
   seems to be letting the tail wag the dog.

I believe that #2 is the least inelegant option, but I'm open to #1 and #3.
However, The *current* situation -- in which JSEP normatively points to a
document from which the text is cites has been removed out from under it -- is
clearly wrong.


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

§4.1.4:

>  If the initial Answer included the attribute a=ice-options:trickle,
>  the Offerer MUST be prepared for receiving trickled candidates later
>  on.

I don't think this makes sense. If the initial *Offer* includes that option,
then the Offerer must be prepared to receive trickled candidates, even before
the Answer arrives. Figure 6 shows an example of this. I believe that the
paragraph I quote above needs to be entirely removed, as it may lead
implementors to incorrectly assume that they can't get trickled candidates prior
to an Answer.

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

§4.3:

>    o  The dialog at both peers MUST be in early or confirmed state.

This makes no sense. Dialogs exist in precisely two states, ever: early or
confirmed. Prior to "early," they don't exist. The only exit from "confirmed" is
destruction. (See RFC 3261 §12).

I think what this means to say is "A dialog MUST have been created between the
peers."

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

§4.3.2:

>  These retransmissions MUST
>  cease on receipt of an INFO request carrying a 'trickle-ice' Info
>  Package body or on transmission of the Answer in a 2xx response.

Why does this require that specific INFO to stop retransmission? The only
requirement is that the answerer knows that the offerer has received the
provisional response. The offerer cannot send post-INVITE requests to the
answerer until a dialog is established, and the only ways a dialog can be
established at the offerer is receipt of a provisional or final response. So, as
soon as you get *any* request from the offerer, you know that the provisional
response has arrived.

I think this passage means to say "These retransmissions MUST cease on receipt
of any in-dialog request from the offerer. The offerer cannot send in-dialog
requests until it receives a response, so the arrival of such a request proves
that the response has arrived."

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

§4.3.2:

>  The Offerer MUST send a Trickle ICE INFO request as soon as it
>  receives an SDP Answer in an unreliable provisional response.  This
>  INFO request MUST repeat the candidates that were already provided in
>  the Offer (as would be the case when Half Trickle is performed or
>  when new candidates have not been learned since then).

It is probably worth mentioning that it's possible that this INFO contains no
candidates, depending on how the offerer gathers its candidates and how long it
takes to do so.

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

§4.3.3:

>  These retransmissions MUST cease on receipt
>  of an INFO request or on transmission of the Answer in a 2xx
>  response.

Same comment as above for §4.3.2.

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

§4.3.4:

>  As specified in Section 4 this offerless INVITE
>  MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
>  header field in order to indicate support for Trickle-ICE to the
>  Offerer (at the User Agent Server (UAS)).

How does the 3PCC controller know to include this option tag? Is it simply
indicating that the 3PCC controller supports the Trickle mechanism? If so,
what happens if the second party (the one who receives the offer in an INVITE)
doesn't support Trickle ICE? This is one of the sharper corner cases that I
think arises when you go to fix the analysis I describe in my DISCUSS above.

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

§4.4:

>     a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 5000 typ srflx
>         raddr 2001:db8:a0b:12f0::1 rport 8998

Thanks for the IPv6 example; however, I have a *lot* of heartburn with the
selection of an example that demonstrates IPv6 NAT behavior. Since ICE's srflx
behavior is fundamentally tied to IPv4 NATs (and should not be an issue with
IPv6, as NATs are unnecessary), I think it's okay for the srvflx examples to go
ahead and show IPv4 addresses.

I *really* don't want to publish an RFC that demonstrates NATting of IPv6.

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

§4.4:

>  An "a=end-of-candidates" attribute, preceding any pseudo "m=" line,
>  indicates the end of all trickling from that agent, as opposed to end
>  of trickling for a specific "m=" line, which would be indicated by a
>  media level "a=end-of-candidates" attribute.

I finally did figure out what this meant, but it's confusing. The use of "any"
in the phrase "any pseudo 'm=' line" implies that the following sdpfrag would
qualify:

      a=ice-pwd:asd88fgpdd777uzjYhagZg
      a=ice-ufrag:8hhY
      m=audio 9 RTP/AVP 0
      a=mid:1
      a=candidate:1 1 UDP 2130706431 2001:db8:a0b:12f0::1 5000 typ host
      a=candidate:1 2 UDP 2130706431 2001:db8:a0b:12f0::1 5001 typ host
      a=end-of-candidates
      m=audio 9 RTP/AVP 0
      a=mid:2
      a=candidate:1 1 UDP 2130706431 2001:db8:a0b:12f0::1 6000 typ host
      a=candidate:1 2 UDP 2130706431 2001:db8:a0b:12f0::1 6001 typ host

The end-of-candidates *does* appear before the second pseudo "m=" line, which is
one of the lines (thereby satisfying the "any" criteria).

I think you mean "preceding the first pseudo 'm=' line..."

This is true later in the section also:

>  will not send any further candidates.  When included at session
>  level, i.e. before any pseudo "m=" line, this indication applies to

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

§4.4:

>  Note: At the time of writing this specification there were ongoing
>  discussions if a functionality for removing already exchanged
>  candidates would be useful.  Such a functionality is out of the scope
>  of this specification and most likely needs to be signaled by means
>  of a yet to be defined ICE extension, although it could in principle
>  be achieved quite easily, e.g. without anticipating any solution by
>  simply omitting a previously sent candidate from a subsequent INFO
>  request.  However, if an implementation according to this
>  specification receives such an INFO request with a missing candidate
>  it would have to treat that as an exceptional case.  Implementing
>  appropriate recovery procedures at the receiving side is advisable
>  for this situation.  Ignoring that a candidate was missing might be a
>  sensible strategy.

This seems like an interop nightmare. If you want a note about this possibly
being included in the future, please simply indicate that such an ability will
need to be explicitly signaled. Don't imply that implementations might get SDP
that violates the behavior defined in this document in some ill-defined way,
and just need to kind of gracefully deal with it, even if we don't really know
what it means at this point in time. There's no sensible way to code for that.

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

§4.4:

>     a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 5000 typ srflx
>        raddr 2001:db8:a0b:12f0::1 rport 8998
>     a=candidate:2 2 UDP 1694498815 2001:db8:a0b:12f0::3 5001 typ srflx
>        raddr 2001:db8:a0b:12f0::1 rport 8998
...
>     a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 6000 typ srflx
>        raddr 2001:db8:a0b:12f0::1 rport 9998
>     a=candidate:2 2 UDP 1694498815 2001:db8:a0b:12f0::3 6001 typ srflx
>        raddr 2001:db8:a0b:12f0::1 rport 9998

Same comment as above regarding IPv6 and NATs. Note that it would be Good and
Helpful to show SDP with a mixture of IPv4 and IPv6 anyway.

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

§5:

>  SIP User Agents (UAs) that support and intend to use trickle ICE are
>  required by [I-D.ietf-ice-trickle] to indicate that in their Offers
>  and Answers using the attribute "a=ice-options:trickle" and MUST
>  include the SIP option-tag "trickle-ice" in a SIP Supported: header
>  field.

Is this intended to imply that the option tag cannot be used in a Require header
field? I don't think that's a good idea; however, if that is the working group's
intention, please say so explicitly.

Suggest "...in a SIP 'Supported' or 'Require' header field."

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

§5.1:

This section discusses behavior in a walled garden. I'm generally fine with
this, as long as the failure modes when someone starts adding doors to the
walled garden are well-defined. I don't think this kind of provisioning is
okay unless it has a requirement that Offerers assuming Trickle ICE support
MUST include a "Require: trickle-ice" header field. That way, if the
provisioned assumption of Trickle ICE support ends up being incorrect, the
failure is (a) operationally easy to track down, and (b) recoverable by the
client (i.e.: they can re-send the request without the "Require" header field
and without the assumption of Trickle ICE support).

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

§6:

>  This INFO request indicates that the Answerer supports and uses RTP
>  and RTCP multiplexing as well.  It allows the Offerer to omit
>  gathering of RTCP candidates or releasing already gathered RTCP
>  candidates.

It's not clear how this "releasing already gathered RTCP candidates" interacts
with the requirement in §4.4:

>  In other words, the sequence
>  of a previously sent list of candidates MUST NOT change in subsequent
>  INFO requests and newly gathered candidates MUST be added at the end
>  of that list.

So, if I had already trickled candidates for the RTCP component of a connection
and *then* got an INFO from the Answerer indicating that it supports
multiplexing, does that mean I free the resources and exclude them from future
INFO messages? That seems to contravene the §4.4 requirement. Or do I free them
but continue to include them? I suppose that's okay (maybe?), but it's
extremely counterintuitive, and would need to be called out explicitly if you
expect implementors to get it right.

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

§7:

>  A Trickle Answerer SHOULD include an "a=group: BUNDLE" attribute
>  [I-D.ietf-mmusic-sdp-bundle-negotiation] in the application/trickle-
>  ice-sdpfrag body if it supports and uses bundling.

This needs to clearly indicate that this needs to be included at the session
level (rather than the media level).

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

§7:

>  The Offerer can use this information e.g. for stopping the gathering
>  of candidates for the remaining "m=" lines in a bundle and/or for
>  freeing corresponding resources.

Same comment as for §6, above (regarding interaction with the requirement from
§4.4)

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

§7:

>      a=group:BUNDLE foo bar
>      a=ice-pwd:asd88fgpdd777uzjYhagZg
>      a=ice-ufrag:8hhY
>      m=audio 9 RTP/AVP 0
>      a=mid:foo
>      a=rtcp-mux
>      a=candidate:1 1 UDP 1658497328 2001:db8:a0b:12f0::3 5000 typ host
>      m=audio 9 RTP/AVP 0
>      a=mid:bar

The presence of the second m= line here is confusing, given the following text
from §4.4:

>  Note, that there is no requirement that the Info request body
>  contains as many pseudo m= lines as the Offer/Answer contains m=
>  lines, nor that the pseudo m= lines be in the same order as the
>  m=lines that they pertain to.  The correspondence can be made via the
>  "a=mid:" attributes.

The §4.4 text strongly implies that it is nonsensical to include an m= section
without candidates. Is the example in §7 intended to imply that the section
needs to be included because its mid is mentioned in the "a=group:BUNDLE" line?
If so, please say so. If not, please remove the second m= section.

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

§9.2:

The syntax for "session-level-fields", "pseudo-media-descriptions", and
"trickle-ice-attribute-fields" include extremely strict rules around ordering of
fields (e.g., including ice-ufrag before ice-pwd would be syntactically
invalid). That level of strictness seems unlikely to lead to interoperable
implementations.

If the intention is to be rigid in this fashion, please add prominent prose
that warns implementors that fields MUST appear in the order specified, and
that all other orders are invalid and MUST be rejected.

If that's *not* your intention (and I suspect it isn't), then please fix the
syntax definition to allow for arbitrary ordering of attributes in the same way
as SDP does. For example:

    session-level-fields = *(session-level-field CRLF)

    session-level-field = bundle-group-attribute /
                          ice-lite-attribute /
                          ice-pwd-attribute /
                          ice-ufrag-attribute /
                          ice-options-attribute /
                          ice-pacing-attribute /
                          end-of-candidates-attribute /
                          extension-attribute-fields
                                 ; for future extensions


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

§9.2:

The syntax for "session-level-fields" implies that "ice-pwd" and "ice-ufrag" are
mandatory at the session level. This seems to conflict with the text in §4.4:

>  The "a=ice-pwd:" and "a=ice-ufrag:" attributes MUST appear at the
>  same level as the ones in the Offer/Answer exchange.  In other words,
>  if they were present as session-level attributes, they will also
>  appear at the beginning of all INFO request payloads, i.e. preceding
>  all pseudo "m=" lines.  If they were originally exchanged as media
>  level attributes, potentially overriding session-level values, then
>  they will also be included in INFO request payloads following the
>  corresponding pseudo "m=" lines.

The fix I propose above removes this implication that such attributes are
mandatory at the session level; however, if you choose to fix it some other way,
please ensure that the ABNF does not conflict with the normative language I
quote above.

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

§10.6:

Same comment as for §5 above.

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

§10.9:

>  If the INFO requests are sent on top of TCP, which is probably the
>  standard way, this is not an issue for the network anymore, but it
>  can remain one for SIP proxies and other intermediaries forwarding
>  the SIP INFO messages.  Also, an endpoint may not be able to tell
>  that it has congestion controlled transport all the way.

This seems kind of blithe about congestion control, as it concedes that the INFO
requests might end up on UDP at some point. Minimally, I would think that you
want to require some minimum quarantine period between INFO requests (probably
something in the range of 20 ms), during which any new candidates that are
gathered are aggregated into the next INFO message.

===========================================================================

Nits:

Expand "ICE" in the title.

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

draft-ietf-mmusic-ice-sip-sdp has undergone a major restructuring since version
16; as a consequence, all notes of the form:

>  [RFC EDITOR NOTE: The section 4.2.1.2.1 in above sentence is correct
>  for version 16 of said I-D.  Authors need to cross-check during
>  Auth48 since it could have have changed in the meantime.]

...are already out of date. It's probably worthwhile to fix these now, as they
are (in my opinion) quite unlikely to change again; and the current misdirection
makes it somewhat difficult to use the draft in its current form.

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

§4.1.3:

>  If the Answerer includes candidates in its initial Answerer, it MUST

"...initial Answer..."

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

§7:

>  A Trickle Answerer SHOULD include an "a=group: BUNDLE" attribute

Remove the space before "BUNDLE"

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

§11:

>  Trickle ICE uses two mechanism for exchange of candidate information.

"mechanisms"



From nobody Tue Apr  3 02:13:30 2018
Return-Path: <jo@acm.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 6C2951270A0; Tue,  3 Apr 2018 02:13:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Joerg Ott <jo@acm.org>
To: <tsv-art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-mmusic-trickle-ice-sip.all@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152274679141.14016.5925633506809938876@ietfa.amsl.com>
Date: Tue, 03 Apr 2018 02:13:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Om0jM8-oFSimVdZYFh-PpU9fHaM>
Subject: [MMUSIC] Tsvart telechat review of draft-ietf-mmusic-trickle-ice-sip-14
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 09:13:11 -0000

Reviewer: Joerg Ott
Review result: Ready with Nits

Reviewer: Jörg Ott
Review result: Ready with Nits

This is a re-review of draft-ietf-mmusic-trickle-ice-sip.  The previous review
was on draft-ietf-mmusic-trickle-ice-sip-12. Revision -14 of the draft largely
addresses the issues on congestion-controlled transport.

Recap from the previous review for completeness:
I've reviewed this document as part of TSV-ART's ongoing effort to review key
IETF documents. These comments were written primarily for the transport area
directors, but are copied to the document's authors for their information and
to allow them to address any issues raised.  When done at the time of IETF Last
Call, the authors should consider this review together with any other last-call
comments they receive. Please always CC tsv-art@ietf.org if you reply to or
forward this review.

The draft defines a how the Session Initiation Protocol (SIP) shall
make use the incremental discovery and exchange of IP addresses as
provided by tricke ICE; the main purpose is reducing call setup latency.

The draft defines address the SIP aspects comprehensively with all
necessary features.  From a transport perspective relevant is primarily
its use the SIP INFO method for carrying updates to the collected
addresses to notify the respective peer that further ones can now
be tried and inform when when the address gathering is complete.

The revisions to section 10.9 largely address the congestion control
issues I raised before.  But there is new issue coming up:

10.9 Rate of INFO Requests
   Given that IP addresses may be gathered rapidly a Trickle ICE Agent
   with many network interfaces might create a high rate of INFO
   requests if every newly detected candidate is trickled individually
   without aggregation.  Implementors MUST consider aggregating ICE
   candidates in case that UDP is used as transport protocol and sending send
   INFOs only at some configurable intervals.

The aggregation now raises the issue of SIP INFO messages exceeding MTU size.
Measurements in the wild have shown that SIP INVITE messages may easily be
larger than MTU size, so this should be factored in.  If an INFO requests
exceeds a reasonable MTU size (say, 1280 bytes),  it should be sent, but not
earlier than 200ms after the previous INFO message was sent -- or something
along these lines.  Such a rare limit could be specified in general and, if
aggregation is employed, too, probably not harm the call setup process.

Nit: Put the statement "Also, an endpoint may not be able to tell
that it has congestion controlled transport all the way." into its own paragraph
so that this stands out.



From nobody Tue Apr  3 06:55:00 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927AC12E8D2; Tue,  3 Apr 2018 06:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=DPau2Gvr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XCi8IuG+
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cNljZ1OWjNAA; Tue,  3 Apr 2018 06:54:55 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28F2912E8E4; Tue,  3 Apr 2018 06:54:50 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8E05B20A59; Tue,  3 Apr 2018 09:54:49 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Tue, 03 Apr 2018 09:54:49 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=uup3b5ncS/JDs6UDfMr86CihEslSI pWIT6x8QSH6mIo=; b=DPau2Gvrhv5HOM9k9ZAg7NHrQKvSaTiQRpqB4Fl1CqXmZ CD5cbr6WENhNi7RsH7H/h5XYQwgy3aOPKLbu5thSs598y20DG5Q1hPXbH0ZSuMXK DVyyykfhg+443/S6BmCKO1GTz7pM8Eb9HFZkbeqdFZzx0XrcLsbovHy+xBa/TmN6 q9U+EcmLfbeB3tn+XRcBccTuV5Nc+EAeLoHTbTHEH7eWrSX+ErIu0W6e8hdKunpP 61sqr4Brmg/2xU+/VLBBbAV/S6QneI+WFfR+LWwuapi6BhwcM/yhJ93oXR8bDFOB 6F4/EA1lLRJ8sdsweFF3RQG6fD5tG9K8NOCXvrTDw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=uup3b5 ncS/JDs6UDfMr86CihEslSIpWIT6x8QSH6mIo=; b=XCi8IuG+uqaMtaxUzT8PhV 1WQXHDDrx6vgrIBPEg1/wSM1G4U+abZiVYlI86bBBTX3wmNwUbkeVk23BhKCFlhv DocHxYhgkH0l9q3WsObBwId1nnoPjxxf+6nFtfoyZZHokktv+JEI7FF/uYNy+V59 I8xErYHG4iw5npl2sk3anMyNRFWVzEEARRE1LGNeV3qRzEGKs0+j+qvJGZz6r4Gm VgbHzzxYs5bmzax1svR1XYeyIuc34o9y8d9WZpcEVSMWQhSMyFG89BnNObii3kjR aztj2P7NfCdhs+Y7cnKzNMPaIlSMQoksjTupD+Bb1eNacWrbPNNKTX6yJwcohLQQ ==
X-ME-Sender: <xms:qYfDWhqjkDN1oZPWcnPGadv7MwoZ5sxGVKC_1MybVzmWqZ75xNccJw>
Received: from rtp-alcoop-nitro3.cisco.com (unknown [173.38.117.78]) by mail.messagingengine.com (Postfix) with ESMTPA id EC935E4412; Tue,  3 Apr 2018 09:54:48 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <d8a18070-83c1-e5fa-8b5b-fa47fbed11cc@gmail.com>
Date: Tue, 3 Apr 2018 09:54:47 -0400
Cc: Dale Worley <worley@ariadne.com>, gen-art@ietf.org, mmusic@ietf.org, draft-ietf-mmusic-trickle-ice-sip.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7328CC2-A8C9-4E69-82E9-8D910444C0EA@cooperw.in>
References: <151676553958.24137.4237678593782258786@ietfa.amsl.com> <d8a18070-83c1-e5fa-8b5b-fa47fbed11cc@gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VYqK7L5r6qnPCRBdyMpzxajVjMs>
Subject: Re: [MMUSIC] [Gen-art] Genart last call review of draft-ietf-mmusic-trickle-ice-sip-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 13:54:59 -0000

Dale, thanks for your review. Thomas, thanks for your responses. I have =
entered a No Objection ballot.

Alissa

> On Feb 1, 2018, at 5:47 PM, Thomas Stach <thomass.stach@gmail.com> =
wrote:
>=20
> Dale,
>=20
> first of all apologies for the delay in responding to your thorough =
review.
>=20
> Thanks for your effort.
>=20
> more inline
>=20
>=20
> On 2018-01-24 04:45, Dale Worley wrote:
>> Reviewer: Dale Worley
>> Review result: Ready with Issues
>>=20
>> I am the assigned Gen-ART reviewer for this draft.  The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>=20
>> Document:  draft-ietf-mmusic-trickle-ice-sip-12
>> Reviewer:  Dale R. Worley
>> Review Date:  2018-01-23
>> IETF LC End Date:  2018-01-26
>> IESG Telechat date:  [unknown]
>>=20
>> Summary:
>>=20
>>        This draft is on the right track but has open issues, =
described
>>        in the review.
>>=20
>> This draft is technically quite good, and except for various nits,
>> quite well written.  But there are some significant technical issues
>> that need to be properly settled before the protocol is well-defined
>> with good advice on robust usage.  I don't think settling these =
issues
>> will be difficult.
>>=20
>> ** Global/major issues:
>>=20
>> * The tokens "end-of-candidate" and "end-of-candidates" seem to be =
used
>> equivalently in this document, with the following number of uses:
>>=20
>>      11 end-of-candidate
>>      19 end-of-candidates
>>=20
>> Which is the correct form?
> Hm, as the grammar says "end-of-candidates ", I'll change to the =
latter.
>> * The definition of application/trickle-ice-sdpfrag describes the use =
of
>> "a=3Dcharset" as an attribute, but the grammar of sdpfrag in section =
9
>> does not permit that attribute.
> The grammar allows for using extension attributes.
> "a=3Dcharset" would be one of these, but might only be needed if =
non-ASCII characters are possibly introduced via some potential =
extension.
>>=20
>> * Deployment considerations (section 11)
>>=20
>> It might be worth mentioning here what happens if a middlebox deletes
>> Trickle ICE INFO requests because it does not understand them, but
>> does not delete "Supported: trickle-ice" headers.  It seems to me =
that
>> in order to be robust in this situation, a UA should provide a
>> globally routable address in the m=3D lines of the initial offer or
>> answer, or if Trickle ICE INFO requests fail, eventually amend the
>> addresses to be globally routable addresses.
> There are so many ways how middle boxes can break any mechanism, that =
we can't do much to cover everything.
> RFC 5245 has recommendations (e.g. relayed candidates will always =
work) on how to choose the default destination as provided in the =
m/c-line.
> I don't think we need to repeat that reasoning here , and after all =
the user agent might not want to use such a globally routable address.
>>=20
>> But the WG may have more knowledge about this situation.
>>=20
>> * There are various locations where the language has usages that seem =
to
>> me to be excessively informal or prolix.  Cases I've noticed are:
>>=20
>> 2.  Terminology
>>=20
>>    It is assumed that the reader will be
>>    familiar with the terminology from both documents.
>>=20
>> Probably s/will be/is/.
> OK
>>=20
>> 3.1.  Discovery issues
>>=20
>>    Such Offers and Answers can
>>    only be handled meaningfully by agents that actually support
>>    incremental candidate provisioning, which implies the need to =
confirm
>>    such support before actually using it.
>>=20
>> It's probably best to omit "actually" here and elsewhere.  There is
>> also a use of "right from the first Offer".  And in some places
>> "would" is used where it is not needed or could be replaced by "do";
>> "would" should (IMO) be restricted to situations that are
>> counter-factual.  There is also a use of "like for example" instead =
of
>> "for example".
> I'll have pass through the document and look for these.
>>=20
>> I expect the RFC Editor can give guidance on this subject.
>>=20
>> ** Detailed/editorial/nits:
>>=20
>>        A Session Initiation Protocol (SIP) usage for Trickle ICE
>>                   draft-ietf-mmusic-trickle-ice-sip-12
>>=20
>> The current practice is to capitalize "usage" in this situation.
>> (I expect the RFC Editor can give guidance on the current
>> capitalization style for RFCs.)
> We switch to capitalized "Usage" as that  seems correct to me.
>>=20
>> Abstract
>>=20
>>    This document defines usage semantics for Trickle ICE with the
>>    Session Initiation Protocol (SIP) and defines a new SIP Info =
Package.
>>=20
>> Perhaps /a new SIP Info Package/a new SIP Info Package to support =
this
>> usage/.
>>=20
>> Table of Contents
>>=20
>> The capitalization of section titles seems to be inconsistent.
> I'll have a pass through the section titles that are taken over into =
the ToC
>>=20
>> 1.  Introduction
>>=20
>>    It describes how ICE candidates
>>    are to be exchanged incrementally with SIP INFO requests [RFC6086]
>>=20
>> Probably s/exchanged incrementally with/exchanged incrementally
>> using/, as "with" can be read to mean that the SIP INFO requests are
>> one party which is exchanging.
> ok
>>=20
>> 4.  Incremental Signaling of ICE candidates
>>=20
>>    The following sections provide further details on how Trickle ICE
>>    Agents perform the initial Offers/Answers exchange (Section 4.1),
>>    perform subsequent Offers/Answers exchanges (Section 4.2) and
>>    establish the INVITE dialog usage (Section 4.3) such that they can
>>    incrementally trickle candidates (Section 4.4).
>>=20
>> I think you want to change "Offers/Answers" to "Offer/Answer".
> Yes
>>=20
>> 4.3.1.  Establishing dialog state through reliable Offer/Answer =
delivery
>>=20
>> It was stated in section 4.1, "Trickle ICE Agents MUST indicate
>> support for Trickle ICE by including the SIP option-tag 'trickle-ice'
>> in a SIP Supported:  header field within all SIP INVITE requests and
>> responses.", but it would be helpful to remind the reader in figure 3
>> by showing the Supported: headers:
>>=20
>>                    Alice                         Bob
>>                      |                            |
>>                      |     INVITE (Offer)         |
>>                      |     Supported: trickle-ice |
>>                      |--------------------------->|
>>                      |     183 (Answer)           |
>>                      |     Supported: trickle-ice |
>>                      |<---------------------------|
>>=20
>> and similarly in later figures.
>>=20
>> Something similar might be done with the "SRFLX Cand." elements to
>> make the figures less cramped.
>>=20
>> 4.3.2.  Establishing dialog state through unreliable Offer/Answer
>>=20
>>    These retransmissions MUST
>>    cease on receipt of an INFO request or on transmission of the =
Answer
>>    in a 2xx response.
>>=20
>> Strictly, "a trickle-ice INFO request", as other INFO requests might
>> be received as part of other mechanisms.
> OK
> I'll change to
> "These retransmissions MUST cease on receipt of an INFO request
>             carrying  a 'trickle-ice' Info Package body  or on ..."
>>=20
>> 4.3.4.  Considerations for Third Party Call Control
>>=20
>>    The peer
>>    Trickle ICE Agent (the UAC) MUST send a Trickle ICE INFO request =
as
>>    soon as they receive an unreliable provisional response (see
>>    Figure 8).
>>=20
>> s/they receive/it receives/
> OK
>>=20
>> 4.4.  Delivering candidates in INFO messages
>>=20
>>    Agents MUST include a pseudo "m=3D" line and an identification tag =
in a
>>    "a=3Dmid:" attribute for every "m=3D" line whose candidate list =
they
>>    intend to update.  Such "a=3Dmid:" attributes MUST immediately =
precede
>>    the list of candidates for that specific "m=3D" line.  All
>>    "a=3Dcandidate" or "a=3Dend-of-candidates" attributes following an
>>    "a=3Dmid:" attribute, up until (and excluding) the next occurrence =
of a
>>    pseudo "m=3D" line, pertain to the "m=3D" line identified by that
>>    identification tag.  An "a=3Dend-of-candidates" attribute, =
preceding
>>    any pseudo "m=3D" line, indicates the end of all trickling from =
that
>>    agent, as opposed to end of trickling for a specific "m=3D" line, =
which
>>    would be indicated by a media level "a=3Dend-of-candidates" =
attribute.
>>=20
>> This seems to be the first section that involves the detailed
>> structure of trickle-ice INFO messages.  It would probably be useful
>> here to tell the reader that there is a grammar in section 9.
> OK
>>=20
>> This paragraph is very dense and you should see if you can split it =
in
>> some way.  In particular, I think it is possible to separate the =
first
>> part, which discusses the structure of the sdpfrag, from the second
>> part, which specifies how the pseudo m=3D lines in the sdpfrag =
correlate
>> with the m=3D lines in the offer/answer.
> I will have a look into this in order to improve
>>=20
>> In addition, it seems to me that there is no requirement that the
>> sdpfrag contains as many pseudo m=3D lines as the offer/answer =
contains
>> m=3D lines, nor that the pseudo m=3D lines be in the same order as =
the m=3D
>> lines that they pertain to (the correspondence being made via the mid
>> attributes).  Since this is very different from the semantics of SDP
>> proper, I think it should be pointed out explicitly.
> Makes sense, I'll add a note.
>>=20
>> 5.  Initial discovery of Trickle ICE support
>>=20
>>    This makes discovery fairly straightforward for Answerers or for
>>    cases where Offers need to be generated within existing dialogs
>>    (i.e., when sending UPDATE or re-INVITE requests).  In both =
scenarios
>>    prior SDP would have provided the necessary information.
>>=20
>> I think you need to expand this to note that INVITE requests are
>> required to include "Supported: trickle-ice" if the UA supports
>> Trickle-ICE.  This is important because a UA may receive an offerless
>> re-INVITE as part of initiating a 3PCC -- the peer UA may be
>> attempting to connect media between the UA and a third UA, and the
>> third UA may not support Trickle ICE, even though the peer UA does.
>> (See, e.g., RFC 3725 section 4.1 and RFC 7088 section 2.3.
>> In this situation, the offerless re-INVITE would not contain
>> "Supported:  trickle-ice" unless the peer UA knows that the third UA
>> supports Trickle-ICE.  The UA, seeing the absence of "Supported:
>> trickle-ice", would send a non-Trickle-ICE offer, even if the =
previous
>> SDP had indicated support for Trickle-ICE.
> Good point. I'll add an explanation along the lines of your reasoning
>>=20
>> 5.1.  Provisioning support for Trickle ICE
>>=20
>>    While the exact mechanism for allowing such provisioning is out of
>>    scope here, this specification encourages trickle ICE =
implementations
>>    to allow the option in the way they find most appropriate.
>>=20
>> What is "the option"?  Perhaps "such provisioning".
> Yes. I'll change accordingly
>>=20
>> 5.2.  Trickle ICE discovery with Globally Routable User Agent URIs
>>=20
>>    This circumvents to use of forking
>>    for that request.
>>=20
>> I think you want s/circumvents to/prevents the/.
> OK
>>=20
>> 5.3.  Fall-back to Half Trickle
>>=20
>> Figure 11 seems to be incorrect -- since Alice is using Half-Trickle
>> ICE, all her candidates are sent in the INVITE, and she shouldn't =
send
>> any INFO requests.  But an INFO request from Alice is shown.
> No, that is correct. The INFO from Alice acknowledges the receipt of =
the 183 and stop retransmissions (see section 4.3.2)
>>=20
>> 6.  Considerations for RTP and RTCP multiplexing
>>=20
>>        INFO sip:alice@example.com SIP/2.0
>>        ...
>>        Info-Package: trickle-ice
>>        Content-type: application/sdp
>>        Content-Disposition: Info-Package
>>        Content-length: 161
>>=20
>> Shouldn't this be "Content-type: application/trickle-ice-sdpfrag"?
> Yes. Thanks for spotting this.
>>=20
>> 7.  Considerations for Media Multiplexing
>>=20
>>        INFO sip:alice@example.com SIP/2.0
>>        ...
>>        Info-Package: trickle-ice
>>        Content-type: application/sdp
>>        Content-Disposition: Info-Package
>>        Content-length: 219
>>=20
>> Shouldn't this be "Content-type: application/trickle-ice-sdpfrag"?
> ditto
>>=20
>> 9.2.  Grammar
>>=20
>>    A sender SHOULD stick to lower-
>>    case for such grammars, but a receiver MUST treat them case-
>>    insensitive.
>>=20
>> This is awkward.  Perhaps better is "A sender SHOULD use lower-case
>> for attributes from such earlier grammars, but a receiver MUST treat
>> them case-insensitively."
> OK
>>=20
>> I don't know the practice regarding the overall grammar of SDP, but
>> the grammar shown here is very rigid regarding the order of fields in
>> <session-level-fields> and in <trickle-ice-attribute-fields>.  If =
this
>> rigidity is not intended, there should be some notation on the =
grammar
>> to show this.
> I don't see any benefit in making it less rigid and I'm somewhat =
reluctant to change this at this point of the process.
>>=20
>> 10.1.  Rationale - Why INFO?
>>=20
>>    The decision to use SIP INFO requests as a candidate transport =
method
>>    is based primarily on their lightweight nature.  Once a dialog has
>>    been established, INFO requests can be exchanged both ways with no
>>    restrictions on timing and frequency and no risk of collision.
>>=20
>>    On the other hand, using Offer/Answer and UPDATE requests =
[RFC3311]
>>    would introduce the following complications:
>>=20
>> A critical fact is that the sending of Trickle ICE candidates in one
>> direction is entirely uncoupled from sending candidates in the other
>> direction.  Thus, the sending of candidates in each direction can be
>> done by a stream of INFO requests that is not correlated with the
>> stream of INFO requests in the other direction.  And since each INFO
>> request is cumulatively includes the contents of all previous INFO
>> requests in that direction, ordering between INFO requests need not =
be
>> preserved.  All of this permits using largely-independent INFO
>> requests.
>>=20
>> Contrarily, UPDATE or other offer/answer mechanisms assume that the
>> messages in each direction are tightly coupled with messages in the
>> other direction.
> I like this text and will take it over, unless somebody objects.
>>=20
>> 12.2.  application/trickle-ice-sdpfrag Media Type
>>=20
>>    This section defines a new Media Type 'application/trickle-ice-
>>    sdpfrag' in accordance with [RFC6838].
>>=20
>> s/This section/This document/ -- as in section 12.2.
> OK
>>=20
>> This section should refer to the grammar of section 9 as the
>> definition of the media type content.
>>=20
>>          SDP files are primarily UTF-8 format text.
>>=20
>> The content of application/trickle-ice-sdpfrag is not SDP, strictly
>> speaking.  And as noted later in the document, not all of them are
>> UTF-8.  I think you want something like this:
>>=20
>>    The media contents follow the same rules as SDP, except as noted
>>    in this document.  The media contents are text, with the grammar
>>    specified in section 9.
>>=20
>> Then continue with "Although the initially ...", which describes the
>> character set implications of "are text".
> OK, will do.
>>=20
>>          The "a=3Dcharset:"
>>          attribute may be used to signal the presence of other =
character
>>          sets in certain parts of a trickle-ice-sdpfrag body (see
>>          [RFC4566]).
>>=20
>> Except that "a=3Dcharset" is not permitted by the grammar of section =
9.
> As above, it will fall into the extension-attribute bucket if not =
understood.
>=20
> Thanks again for your thorough review and numerous proposal for =
improvement.
> Regards
> Thomas
>>=20
>> [END]
>>=20
>>=20
>>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr  3 07:26:06 2018
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 1D3E31271DF; Tue,  3 Apr 2018 07:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id urYGQbhmSyAC; Tue,  3 Apr 2018 07:25:56 -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 AD094124D68; Tue,  3 Apr 2018 07:25:53 -0700 (PDT)
Received: by mail-yb0-x232.google.com with SMTP id p126-v6so548854ybg.8; Tue, 03 Apr 2018 07:25:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EcMHxJqd+ZkgYh8K/pRpxJVkGWcbXp1kHbjS4elTmSc=; b=HAJdz0uraMX0Y3Am1l1LUHI1rttthQSqin9KBl+5l7Arc7GPp7rr4QnmeYcoIJJuyV 3qNyKnyrZ2t8enm9TiVIQKxJyt0c+4mKeqJuuB55BN4Ek/RG/E1v4NSDTNidkSv4V4qz QI+9syM5HL/2dRHcvKD/hO6iHrF9xPbNzgp6FxfAM+bkBsX020njPHh9uYbIYQ9yWWo4 U1AuskU5aa1LUoxfmX/449xjJjXXFEyn0fBAIVOz4mp+RTeMK2MZhY+EEs/Zo3Dc8Oh8 yBDundMng/zvmpTaopCqW2ds+9Nmxxl2vVNBDTCx1iyFlZGIbIsSbn6hPwDkt4U9txIy GtPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EcMHxJqd+ZkgYh8K/pRpxJVkGWcbXp1kHbjS4elTmSc=; b=PJw7mWAIY0/QAVbzqZo590OBAYD/m2OAygeWOT69l8/ODNiUgoaa+d4cbFjei53OPH vu3Fv2RsoGcqMTIOt/TCVud9MFbXJ91X5tZDU+NO8U3SQYZMt+/eynBUvsWqrK6lrkyR lA6plgvykfq+C/v1gH9draPgEQVZTlOfylkcnuGEe0nqEdH0TwFCsG/y0zNyYIfdiuFK HawazDE6SgCfmfaLVY6lRcqQ4P2UHC7VWvDi+Wl7xleHEgZsL1wJSB3ZvzBYnCp1Y05e XeP/0m2+LZ1g7dVKEfnpVx3KiWn8wTcVAxPg4Pbsp7ccH+iaBu4DA/8qCfh0thaX0AOm BX7g==
X-Gm-Message-State: ALQs6tDRxZNLJuJaZioEw6IE4m8UPoipJAgu7Seh+RhEmdfFNIzXz6Xc GZCxRK03n2sknl60ugxY1+AKW+ixdRwbssUbhoo=
X-Google-Smtp-Source: AIpwx4/BuczbWKQTecmE5WbZP0v76Z0VpTimSbLDseuTDhVzCQR0df9O7vQqXbvuY0gBIQMpY2CRaC/Z3GuyQ/PBI6o=
X-Received: by 2002:a25:1e44:: with SMTP id e65-v6mr8000197ybe.221.1522765552679;  Tue, 03 Apr 2018 07:25:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:e757:0:0:0:0:0 with HTTP; Tue, 3 Apr 2018 07:25:52 -0700 (PDT)
In-Reply-To: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 3 Apr 2018 09:25:52 -0500
Message-ID: <CAKKJt-c7=faN+4JQ8xaLpiuBA1OGd-1HDyZbscukQGV=uY12sg@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: The IESG <iesg@ietf.org>, fandreas@cisco.com, mmusic-chairs@ietf.org,  draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000d7ff6c0568f27b65"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LpNjoPQhUO9k5oAqTwxTRk7iBOA>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 14:25:59 -0000

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

For what it's worth ...

On Tue, Apr 3, 2018 at 2:29 AM, Adam Roach <adam@nostrum.com> wrote:

> Adam Roach has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks to everyone who worked on this document. I have a couple of
> concerns that
> need to be cleared up before the document can move forward.
>
> ------------------------------------------------------------
> ---------------
>
> =C2=A74.3.4 discusses the interaction of 3PCC with the trickle ICE mechan=
ism.
> Unfortunately, the diagrams used in this section do not show a 3PCC
> signaling
> flow; they show a two-party call flow with an offerless INVITE. A 3PCC
> call flow
> would necessarily involve a 3PCC controller sending an offerless INVITE t=
o
> one
> party, receiving an offer from that party (typically in a reliable
> provisional
> response or in a 200 OK), and then sending an INVITE to the other party
> containing that offer.
>
> The text in this section matches the diagrams, and consequently does not
> appear
> to be an analysis of 3PCC behavior. It is an analysis of two-party
> offerless
> INVITE behavior.


I THOUGHT that was wrong!

Thanks for being smart enough to ask about it ...

Spencer

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

<div dir=3D"ltr">For what it&#39;s worth ...=C2=A0<div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Tue, Apr 3, 2018 at 2:29 AM, Adam Roach=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:adam@nostrum.com" target=3D"_blank=
">adam@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Adam Roach has entered the following ballot position for<br>
draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss<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-trickle-ice-s=
ip/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr=
>doc/draft-ietf-mmusic-trickle-<wbr>ice-sip/</a><br>
<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
DISCUSS:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
Thanks to everyone who worked on this document. I have a couple of concerns=
 that<br>
need to be cleared up before the document can move forward.<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
----------<br>
<br>
=C2=A74.3.4 discusses the interaction of 3PCC with the trickle ICE mechanis=
m.<br>
Unfortunately, the diagrams used in this section do not show a 3PCC signali=
ng<br>
flow; they show a two-party call flow with an offerless INVITE. A 3PCC call=
 flow<br>
would necessarily involve a 3PCC controller sending an offerless INVITE to =
one<br>
party, receiving an offer from that party (typically in a reliable provisio=
nal<br>
response or in a 200 OK), and then sending an INVITE to the other party<br>
containing that offer.<br>
<br>
The text in this section matches the diagrams, and consequently does not ap=
pear<br>
to be an analysis of 3PCC behavior. It is an analysis of two-party offerles=
s<br>
INVITE behavior.</blockquote><div><br></div><div>I THOUGHT that was wrong!<=
/div><div><br></div><div>Thanks for being smart enough to ask about it ...<=
/div><div><br></div><div>Spencer=C2=A0</div></div></div></div>

--000000000000d7ff6c0568f27b65--


From nobody Tue Apr  3 07:37:10 2018
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 BD2A01271DF; Tue,  3 Apr 2018 07:37:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com>
Date: Tue, 03 Apr 2018 07:37:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/dfL3qulnPudvWylJnlVu65zYD4Y>
Subject: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-ietf?= =?utf-8?q?-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 14:37:03 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-sip-14: Discuss

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


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


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



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

Thanks for the well-written doc and the quick response to the initial tsv
review. Also thanks to Jörg for the thorough and very helpful review!

As flagged by the tsv review, there can be an issue with the aggregation of
candidates in one INFO message when rate limited and the path MTU/UPD
fragmentation. While this is a small point only and I'm sure it can be easily
addressed, it important enough that I decided to put a discuss in. I'm sure
this can be resolved quickly as well.

Also if the document could give further guidance on an acceptable maximum for
the rate of INFO requests that be even better!


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

Editorial comments:

1) sec 4.3.2: "When sending the Answer in the 200 OK response to the INVITE
request,
   the Answerer needs to repeat exactly the same Answer that was
   previously sent in the unreliable provisional response in order to
   fulfill the corresponding requirements in [RFC3264].  Thus, the
   Offerer needs to be prepared for receiving a different number of
   candidates in that repeated Answer than previously exchanged via
   trickling and MUST ignore the candidate information in that 200 OK
   response."
   What do I miss? Why can there be a different number of candidates if the
   repeated Answer needs to be exactly the same...? Or is there an "not"
   missing? Not an expert though, so might be just me...

2) I guess section 10.1 could also be moved to the appendix but it is short
enough that leaving it in the body is fine as well.



From nobody Tue Apr  3 09:23:03 2018
Return-Path: <stpeter@mozilla.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 B8A8F12EA76 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 09:22:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 ZNe-FeZP7OcO for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 09:22:46 -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 E34B112EA42 for <mmusic@ietf.org>; Tue,  3 Apr 2018 09:22:42 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id 141so22694048iou.12 for <mmusic@ietf.org>; Tue, 03 Apr 2018 09:22:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to; bh=cONZS0n96z7VIaBKTmfhtIRvM32+nB0cG1YdpNhinA0=; b=PK1bfsGhHg33krAqFARxD1fuN8NxNEVU78tYn6TlW7VdJrYlI3Ckpk1jwsf62dD1ZJ mZi3srLhyfXVncls5Er89PSD+t8Rih4XAHpf/WLsbZ41zvhLo6TWXavPY0KYRTiC+jLS bkEpglZgFFvgnDVc1AcNmcWjLeXp4wl2rC0bY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to; bh=cONZS0n96z7VIaBKTmfhtIRvM32+nB0cG1YdpNhinA0=; b=uflag+lUVBx2tKIjRo+LenMk6BarqWXEp/vfTWxyF5qP/1zk7moguWGo3eoSfHNuAa CmvFATyATM+i6WGrgMiHuXEmZNS/ijw34OEVPABh/2IjqxfCWf31djHHzD3ceg5PNxyK KtjCNCCmIY/iV+d7zw2i6c3D2NxVORAECDXy9XdqtoZSLpVY8uinBPzYg4Zqcmsm/4KT te/RspCGG0X1hBdtMQQ7VRLOvgWFv9rqMDmxu8FAR33ylVzk3NBvfQB5TMp/rDCar+qp ey5yxcy0N8nAyx+w6obTF6DNpvObsrarzFmMDHidNBLJKKYYiswhA0O2E3QZAFtX3kQh VNMQ==
X-Gm-Message-State: ALQs6tA+QJKA6JokX9miiyJvfO+1L2KMvFBSrSdvqdhtq1mHihBxDLGb EpBqr+xNijlnJiSRjFDNbOnmAQ==
X-Google-Smtp-Source: AIpwx49w9dKhaD+yqGzWrOJWw5VpPDrE5v4zG6jOFOnQA3tVD87XGJ4lWgLSdYT/m9jtvBKPGEIbUg==
X-Received: by 10.107.133.232 with SMTP id p101mr13314251ioi.44.1522772561518;  Tue, 03 Apr 2018 09:22:41 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id a46-v6sm640573itj.1.2018.04.03.09.22.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 09:22:40 -0700 (PDT)
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org, "ice@ietf.org" <ice@ietf.org>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com>
Date: Tue, 3 Apr 2018 10:22:39 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DisIHne6WLUo46VsbP3d4kdsRSDnAQe7B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/dUggDvGxkQmCPUOAU8oVlYYCNgE>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 16:22:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--DisIHne6WLUo46VsbP3d4kdsRSDnAQe7B
Content-Type: multipart/mixed; boundary="zxolWByxpD9xuzxoLYSs9Ma01HhOq3Xi4";
 protected-headers="v1"
From: Peter Saint-Andre <stpeter@mozilla.com>
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org,
 draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org,
 "ice@ietf.org" <ice@ietf.org>
Message-ID: <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com>
Subject: Re: [MMUSIC] Adam Roach's Discuss on
 draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
In-Reply-To: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>

--zxolWByxpD9xuzxoLYSs9Ma01HhOq3Xi4
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

+ ICE WG to address the cross-document DISCUSS only.

On 4/3/18 1:29 AM, Adam Roach wrote:

<snip/>

> The second issue doesn't necessarily pertain to this document per se as=
 much
> as it does the interaction among this document, draft-ietf-ice-trickle =
(Trickle
> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-js=
ep
> (JSEP). The problem doesn't lie with any single document, but in the ov=
erall
> result of how they're currently structured.
>=20
> JSEP (in the RFC editor queue) refers to the "a=3Dend-of-candidates" SD=
P attribute
> as appearing in Trickle ICE, section 9.3, which was true at one point i=
n time.
> Somewhere along the line, this attribute's definition was moved from th=
ere
> into this document.
>=20
> There are several ways to fix this, each with their own drawbacks:
>=20
> 1. Move the SDP syntax for "a=3Dend-of-candidates" back into the Trickl=
e ICE
>    draft. Drawback: Trickle ICE does not currently define any normative=
 SDP
>    behavior; and, in fact, could work in a system that doesn't use SDP =
at all.
>=20
> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant f=
rom the
>    perspective that ICE SDP defines SDP syntax for ICE in general (for =
both
>    SIP and JSEP), and such a move aggregates all of the SDP syntax into=
 a
>    single document that is already necessary to reference from any docu=
ment
>    that uses SDP for Trickle ICE. Drawback: the document doesn't presen=
tly
>    discuss Trickle ICE at all, and this would require a somewhat awkwar=
d
>    section that basically says "If you use [Trickle ICE] with SDP, the =
syntax
>    for the end-of-candidate marker is..."
>=20
> 3. Change JSEP to normatively depend on this document for the
>    "a=3Dend-of-candidates" syntax. Drawback: This document is extremely=

>    SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC =
3264
>    behavior, independent of any SIP semantics.  Forcing JSEP to normati=
vely
>    depend on a SIP specific document for a simple attribute syntax defi=
nition
>    seems to be letting the tail wag the dog.
>=20
> I believe that #2 is the least inelegant option, but I'm open to #1 and=
 #3.
> However, The *current* situation -- in which JSEP normatively points to=
 a
> document from which the text is cites has been removed out from under i=
t -- is
> clearly wrong.

IMHO the ICE WG had consensus to remove all normative SDP references
from draft-ietf-ice-trickle and place them in
draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
document JSEP points to, as long as the "a=3Dend-of-candidates" definitio=
n
can be found there?

Peter




--zxolWByxpD9xuzxoLYSs9Ma01HhOq3Xi4--

--DisIHne6WLUo46VsbP3d4kdsRSDnAQe7B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENVUj07j078lgnb70ZWGMGH9oFKkFAlrDqk8ACgkQZWGMGH9o
FKk5ng//SqMYOxzzFS9mN6QNykgWaa8EThSDwcU0y2uw1yxZL37qSVMOBjvntrBf
mfkIGhNo2c0CLSyfCKY2CaoVopL8TauMeQkRNH4xKxmQheWhsIZWpaRfVeMJVWxA
kOC/PjtQCmuP+x7GnB5b6rH+oFefWiMUVsCfZRmS9d0hmSAfi1eDKqkAi3jYsmAt
71DfSSs/0Vwj+HXPIxp4l8yUnCY66tGjL6FT/6w+Com2RxBXjb7Tarl2Mo5dUPmX
2CsrwKBFwnuSs0eCIaTQSnghPW5J3rYQj3vHeXEGmBHKUD2ykGO2NMsQcHG6PDZK
qLvomBdChNp4sDXAd65YYcBbWgIYsgl1Qe/Up/wg+7vu7CeFZEjV8/epAeLdVw9I
2kk3w7kX/O+oEiUvzEyZSyk4cTpAPalmhxrE5lhxpfOmnUvNccsmeHlvul25PsK4
TX3aGpnSrlZTxTINGo41njyOAjJT54ADrdfbrfLdabU1SPT0osOwseX4b6fyoBMO
Hseg6BwoYtFJpf/64r3g20bzpE4scmXj8y+Vl2YZ8JdNE42hlV2trjO/BsthkpxM
5Lfy5H8Glru9YOxMoulxnrDEdqkWDlv2Wow3Q+DhPQHjX8WsbFz4Ycn9hZp1ATFw
hTelQjdwzgzAQ19uSEpTlXflr8w2zqDydTOd7tgdQaIO/AUlMVs=
=iujG
-----END PGP SIGNATURE-----

--DisIHne6WLUo46VsbP3d4kdsRSDnAQe7B--


From nobody Tue Apr  3 09:42:36 2018
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 D9D1D129C53; Tue,  3 Apr 2018 09:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vA_tT1LyWheg; Tue,  3 Apr 2018 09:42:27 -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 CE54212EA54; Tue,  3 Apr 2018 09:42:23 -0700 (PDT)
Received: from [10.0.1.91] (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 w33GgGGe079349 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 11:42:17 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <4EA9C047-54A7-4FC3-A1F7-AFCC91F85529@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_162F89FE-6EB0-4455-B1E8-C1A1E1DA5CCC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 11:42:15 -0500
In-Reply-To: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
Cc: The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
To: Adam Roach <adam@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DOqFiUitaqIHfduzu-8WZbIycck>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 16:42:31 -0000

--Apple-Mail=_162F89FE-6EB0-4455-B1E8-C1A1E1DA5CCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Comment on first discuss point:

> On Apr 3, 2018, at 2:29 AM, Adam Roach <adam@nostrum.com> wrote:
>=20
> Adam Roach has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>=20
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut =
this
> introductory paragraph, however.)
>=20
>=20
> Please refer to =
https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>=20
>=20
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>=20
>=20
>=20
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>=20
> Thanks to everyone who worked on this document. I have a couple of =
concerns that
> need to be cleared up before the document can move forward.
>=20
> =
--------------------------------------------------------------------------=
-
>=20
> =C2=A74.3.4 discusses the interaction of 3PCC with the trickle ICE =
mechanism.
> Unfortunately, the diagrams used in this section do not show a 3PCC =
signaling
> flow; they show a two-party call flow with an offerless INVITE. A 3PCC =
call flow
> would necessarily involve a 3PCC controller sending an offerless =
INVITE to one
> party, receiving an offer from that party (typically in a reliable =
provisional
> response or in a 200 OK), and then sending an INVITE to the other =
party
> containing that offer.
>=20
> The text in this section matches the diagrams, and consequently does =
not appear
> to be an analysis of 3PCC behavior. It is an analysis of two-party =
offerless
> INVITE behavior.
>=20
> If this section remains, it needs to be substantially re-worked: the =
diagrams
> need to show three parties, with a 3PCC controller performing the =
controlling
> role as described in RFC 3725. While I haven't stepped through the =
implications
> for Trickle ICE when a controller is actually involved and is moving =
offers and
> answers around between different message types, I suspect that the =
analysis in
> here is substantially different once this starts happening.
>=20
> I would personally be okay if the entire section were removed; =
however, I
> have no desire to override working group consensus regarding the value =
of a
> section dealing with 3PCC considerations.

I suspect (and assumed while reading this) is that the consideration =
that matters is the offer/answer exchange with a delayed offer. It calls =
it a 3PCC consideration because 3PCC uses it. I doubt people had in mind =
to fully specify 3PCC. If the WG agrees that is the case, would it make =
sense to re-label the section as =E2=80=9Cdelayed offer =
considerations=E2=80=9D, and merely mention that 3PCC uses that =
technique?

[=E2=80=A6]



--Apple-Mail=_162F89FE-6EB0-4455-B1E8-C1A1E1DA5CCC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrDrucACgkQgFZKbJXz
1A0AUA//dHBC3SYjGFpGeKEqjGskOwdZ+bjJjCN8JR3+04VHjiDekYD9K89kYjLZ
7ooPxmzQahWQ8eXFvetcdKD2HG30kl/egUPfbP/5CZXDugnwExVNLNt94jOyn/LF
Rd5+1lpR56trfHC2GaO+vcilSNuX5C40k1O83tzEd2blbPRm12l3xMVxRj2SOi/9
yGOTyvZsU/jvtZdwPH152b/EO/FpzAu4+gKgJwi6GznTI1WrkVhlM6qsLoLZT8Ac
Z2Z3I9ASaGF92RE78NlBcPPEKf6vRd+GgFYLHzt732fk9VNt4cmmaN3TmBeecu3q
iAnYEXiJa28ZQphETmVgFQaWI+C72zM20fujiTPBAApXb+hBCfUl5CHdAUucXSed
f4tIB97tJZbMvOnKxUaATRZ5+0s7UR1sNCunE9COpU3n/eISrBLl5phCJTZq7VxU
lMlzx/vi40EaGcvMDPQlb5U4FAbz1LvvYTGZMe/96EYCmA0RCnk6l3jZBS9AmsTN
MCwY+0uqyiGdKvOfq6Fr1TRNXbLyX8XmvTEIAAJ7C2zFrHk6CbYYDHisVsC9LvFs
4r4QYUCWNGGeRZd2pYbngGjU+ZGVaFsRAMS31MxDRxvlvy6w/TCDk+ZfN6Dg+4TF
eo/mjbWiJPFWaUkfE5EbSBESdCaJ68DICG9NE44JTafGtqdzCog=
=5L5e
-----END PGP SIGNATURE-----

--Apple-Mail=_162F89FE-6EB0-4455-B1E8-C1A1E1DA5CCC--


From nobody Tue Apr  3 09:55:42 2018
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 B211F12D7E6; Tue,  3 Apr 2018 09:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GqOvQfQcemku; Tue,  3 Apr 2018 09:55:33 -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 A5A65126BFD; Tue,  3 Apr 2018 09:55:33 -0700 (PDT)
Received: from [10.0.1.91] (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 w33GtSH6081558 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 11:55:28 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BACB3D2F-C7CB-497A-A9F9-30DEF0AE0003"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 11:55:27 -0500
In-Reply-To: <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com>
Cc: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org, "ice@ietf.org" <ice@ietf.org>
To: Peter Saint-Andre <stpeter@mozilla.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gRsUWEwfpuF8LLeEVteWnGh9Mkk>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 16:55:36 -0000

--Apple-Mail=_BACB3D2F-C7CB-497A-A9F9-30DEF0AE0003
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 3, 2018, at 11:22 AM, Peter Saint-Andre <stpeter@mozilla.com> =
wrote:
>=20
> + ICE WG to address the cross-document DISCUSS only.
>=20
> On 4/3/18 1:29 AM, Adam Roach wrote:
>=20
> <snip/>
>=20
>> The second issue doesn't necessarily pertain to this document per se =
as much
>> as it does the interaction among this document, =
draft-ietf-ice-trickle (Trickle
>> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and =
draft-ietf-rtcweb-jsep
>> (JSEP). The problem doesn't lie with any single document, but in the =
overall
>> result of how they're currently structured.
>>=20
>> JSEP (in the RFC editor queue) refers to the "a=3Dend-of-candidates" =
SDP attribute
>> as appearing in Trickle ICE, section 9.3, which was true at one point =
in time.
>> Somewhere along the line, this attribute's definition was moved from =
there
>> into this document.
>>=20
>> There are several ways to fix this, each with their own drawbacks:
>>=20
>> 1. Move the SDP syntax for "a=3Dend-of-candidates" back into the =
Trickle ICE
>>   draft. Drawback: Trickle ICE does not currently define any =
normative SDP
>>   behavior; and, in fact, could work in a system that doesn't use SDP =
at all.
>>=20
>> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant =
from the
>>   perspective that ICE SDP defines SDP syntax for ICE in general (for =
both
>>   SIP and JSEP), and such a move aggregates all of the SDP syntax =
into a
>>   single document that is already necessary to reference from any =
document
>>   that uses SDP for Trickle ICE. Drawback: the document doesn't =
presently
>>   discuss Trickle ICE at all, and this would require a somewhat =
awkward
>>   section that basically says "If you use [Trickle ICE] with SDP, the =
syntax
>>   for the end-of-candidate marker is..."
>>=20
>> 3. Change JSEP to normatively depend on this document for the
>>   "a=3Dend-of-candidates" syntax. Drawback: This document is =
extremely
>>   SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC =
3264
>>   behavior, independent of any SIP semantics.  Forcing JSEP to =
normatively
>>   depend on a SIP specific document for a simple attribute syntax =
definition
>>   seems to be letting the tail wag the dog.
>>=20
>> I believe that #2 is the least inelegant option, but I'm open to #1 =
and #3.
>> However, The *current* situation -- in which JSEP normatively points =
to a
>> document from which the text is cites has been removed out from under =
it -- is
>> clearly wrong.
>=20
> IMHO the ICE WG had consensus to remove all normative SDP references
> from draft-ietf-ice-trickle and place them in
> draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
> document JSEP points to, as long as the "a=3Dend-of-candidates" =
definition
> can be found there?

I was working on a comment to the same effect when I saw Peter=E2=80=99s.

I see Adam=E2=80=99s option 1 as a non-starter since it explicitly =
reverses that consensus. I see 2 and 3 to be equally awkward, in which =
case 3 requires the least amount of structural change. If there was an =
option that required no change to jsep at all(since it is currently with =
the RFC editor), but IIUC, none of the choices allow for that.

Thanks!

Ben.


--Apple-Mail=_BACB3D2F-C7CB-497A-A9F9-30DEF0AE0003
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrDsf8ACgkQgFZKbJXz
1A24fQ//QXFkHY/yNQJeiQnjRF08h68nsx8U8GLBZ1621BkphIGCCtN7zM9FHzai
dGj0jSyLCYGzhI3AJSOGCcc38BIQCYsbvIV1aTFzpH57Sa7rEMQHYqH4Ey0PaupW
lHIgclGXgy75RpgU5Zgrwv6VYioASHc1sWo2sNfoihNPukDdFdvbhJJYSux1GJ2p
LUcaebFUqLi6wRQ9ovgfoMmjFqrdG0HNQSAvTPBpksvLFle7kQPy3I9t3u/3/fGm
RMzinNHcaTnjfO1yx2D339TcxyLgJNWBqJuQT+6GWF2vkLqq36MMSvYaZ2I7FglC
m3XTAJQJ2IHR7tsrz/lvdwYpVxmj5mgvqVD5hQo7yhzBnKaKDXbjW6th9a6souMt
ZB1q0vIjAGVTLqFwtGB+Pdqctn/M95F6Z3hT93TbNHak1b9VohMDLQ4dxf/PxY6c
Uay0IOxtxUd//1X28d9ffu7GFn/v3TMO9nt6yWxrJwZAWUr54EMboMHEmh8iN8y2
OkmM2HMyYc0+ej3wfphHNecuVtntWhe0uoZlj3tzauzKyBE5kx9PZfX4qhTopKod
o6s30LHjWFR3H7SN8GRL1i+VQncMLSbDhcjkXYZ+WJNf5n/Pzr934OjX6iVmTGPG
xuuhHgG0hnM3vLKhjXf6A5bAHHY2wNVG4v8wJ0KGNip9rIZGi8M=
=LMu0
-----END PGP SIGNATURE-----

--Apple-Mail=_BACB3D2F-C7CB-497A-A9F9-30DEF0AE0003--


From nobody Tue Apr  3 10:00:41 2018
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 2106B126C22; Tue,  3 Apr 2018 10:00:33 -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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 7g1d4Qgqj5SS; Tue,  3 Apr 2018 10:00:31 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c: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 B731B126BF6; Tue,  3 Apr 2018 10:00:30 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id o23so17339662wmf.0; Tue, 03 Apr 2018 10:00:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=ukvPMl+FnPeAJO4mArFL+6DP7MwzpLYtST+KIdJYQ74=; b=PmWne7n+52D/VjTU3hHDJTqys9XGuguIg/0s9Zx4G/0GZJ9cRxmOxomLZJcOg2DLA7 87myjWJ50hzbF2mBRk2EtcH3xxwnLfbTBKf5RV703TyaoqjF3PVr7F5tnG/FIPF4cPQ1 AkNNAfIOwip34WWDtHzmniXBZ9CSfPVPqyeVovQHx9Zdg/V8dJaeN5g3EZ7liyPVWpoT J7voWru5y2g00TojnnOSz4twDJFov7exCTqR63FBhk8eeXUuyXws6TXGgfvZkOUcudb2 xznuGFMArWeSTm4J6bCweMBIWNyyVpXMWCTamn1bQg7koZ5e89Rs2547jHRNUJJfpQY6 UXoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ukvPMl+FnPeAJO4mArFL+6DP7MwzpLYtST+KIdJYQ74=; b=MvXRVCl86EOsdR0HENn4znGBJ0Q3+8fOeNaRg73nGFj4atfRYIlzCvYdFFe65msmwI d4F7TDG7lne9rwcEn5Heo0QGgc4hOPq06H+CgZ/yqtSlwOS1sgow2DboUNHkbWVXselv A/5NJdvEP5IXFnoH1/yyZpMZE3LOZOwMo9+oc8aSYz44gTdsM8ECvZmg/zINTRefRnB1 IU/pb4IylbLA8h1R/Pp4758ZnDClsw8C+iYeWkdppzujO3lB9BkYJhwXaAdfRJ7yXiQu t2s8TpKQgR2QpkGvTSdzSO8gaQkP8hYvczc0xA2KM1IRgaV8s+gdGHnc8JSkZcRUtQ33 pJLA==
X-Gm-Message-State: AElRT7FCEFa1+6gceSqXQMOmOgINQqBbNSVxPzo9FbA/E04u4g3/HfsZ 0943XkQUkicG3VG6zpSc+8yJW4v9
X-Google-Smtp-Source: AIpwx4+8mS+SSu/cuvr+XHtDZcyLzIAV5M3KUvynAZy5RNpYSiBqMBqKo1ujtxSpgTke/jnGCe/wYQ==
X-Received: by 10.28.245.9 with SMTP id t9mr5118576wmh.33.1522774828752; Tue, 03 Apr 2018 10:00:28 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id c57sm3086627wrg.84.2018.04.03.10.00.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 10:00:27 -0700 (PDT)
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <152235756539.4292.8471914546680733627.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <9c483471-0c24-5c5f-b57e-5c1cf01e7343@gmail.com>
Date: Tue, 3 Apr 2018 19:00:26 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152235756539.4292.8471914546680733627.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/M31cpwNztpa9eM90lfv1j52GdxM>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-trickle-ice-sip-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:00:33 -0000

Benjamin,

thanks for your comments, responses inline


On 2018-03-29 23:06, Benjamin Kaduk wrote:
> Benjamin Kaduk has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-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-trickle-ice-sip/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Section 5 has (and IIRC other places are similar):
>
>     SIP User Agents (UAs) that support and intend to use trickle ICE are
>     required by [I-D.ietf-ice-trickle] to indicate that in their Offers
>     and Answers using the attribute "a=ice-options:trickle" and MUST
>     include the SIP option-tag "trickle-ice" in a SIP Supported: header
>     field.
>
> It's a little strange to me to say that the core trickle spec mandates specifically the
> "a=ice-options:trickle" attribute, which is only defined in this document.  The core
> spec does mandate some form of indication, but maybe it is more clear to phrase as
> something like:
>
>     SIP User Agents (UAs) that support and intend to use trickle ICE are
>     required by [I-D.ietf-ice-trickle] to indicate that support in their Offers
>     and Answers.  For SIP, this is done using the attribute "a=ice-options:trickle", and
>     the SIP option-tag "trickle-ice" MUST be included in a SIP Supported: header
>     field.
I'll include your proposed text.
> In the scenario depicted in Figure 10, how is it indicated to Bob that Alice supports
> trickle (and should that mechanism be indicated in the figure)?
Well, in the INVITE as described elsewhere in the document.
In order to make the figure complete and consistent I'll add Supported: 
trickle-ice to the INVITE
(together with an indication for an Offer in the INVITE body).

Thanks
Thomas
>
>


From nobody Tue Apr  3 10:17:56 2018
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 A377912EA42; Tue,  3 Apr 2018 10:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5McRyT3PFMLP; Tue,  3 Apr 2018 10:17:48 -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 9AF5012E8A4; Tue,  3 Apr 2018 10:17:48 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w33HHgMK085255 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:17:45 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Ben Campbell <ben@nostrum.com>
Cc: The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <4EA9C047-54A7-4FC3-A1F7-AFCC91F85529@nostrum.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <f8ec9593-3637-8e21-ccbb-a918b0e410e6@nostrum.com>
Date: Tue, 3 Apr 2018 12:17:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <4EA9C047-54A7-4FC3-A1F7-AFCC91F85529@nostrum.com>
Content-Type: multipart/alternative; boundary="------------385DD3D0045AEE9DE9243E49"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/6677q-T3HS74K8iq2Ia0RqDGTbM>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:17:51 -0000

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

On 4/3/18 11:42 AM, Ben Campbell wrote:
> I suspect (and assumed while reading this) is that the consideration that matters is the offer/answer exchange with a delayed offer. It calls it a 3PCC consideration because 3PCC uses it. I doubt people had in mind to fully specify 3PCC. If the WG agrees that is the case, would it make sense to re-label the section as “delayed offer considerations”, and merely mention that 3PCC uses that technique?


I'm not sure how useful that is, as it's not entirely clear that Trickle 
ICE works with 3PCC at all -- see, for example, my later comment:


> §4.3.4:
>
>>   As specified in Section 4 this offerless INVITE
>>   MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
>>   header field in order to indicate support for Trickle-ICE to the
>>   Offerer (at the User Agent Server (UAS)).
> How does the 3PCC controller know to include this option tag? Is it simply
> indicating that the 3PCC controller supports the Trickle mechanism? If so,
> what happens if the second party (the one who receives the offer in an INVITE)
> doesn't support Trickle ICE? This is one of the sharper corner cases that I
> think arises when you go to fix the analysis I describe in my DISCUSS above.


Absent 3PCC, the "early offer" case is not interesting. Aside from 3PCC, 
its only purpose is interop with a version of H.323 that was obsoleted 
in 1998.

/a


--------------385DD3D0045AEE9DE9243E49
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 4/3/18 11:42 AM, Ben Campbell wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:4EA9C047-54A7-4FC3-A1F7-AFCC91F85529@nostrum.com">
      <pre wrap="">I suspect (and assumed while reading this) is that the consideration that matters is the offer/answer exchange with a delayed offer. It calls it a 3PCC consideration because 3PCC uses it. I doubt people had in mind to fully specify 3PCC. If the WG agrees that is the case, would it make sense to re-label the section as “delayed offer considerations”, and merely mention that 3PCC uses that technique?</pre>
    </blockquote>
    <p><br>
    </p>
    <p>I'm not sure how useful that is, as it's not entirely clear that
      Trickle ICE works with 3PCC at all -- see, for example, my later
      comment:</p>
    <p><br>
    </p>
    <p>
      <blockquote type="cite">
        <pre wrap="">§4.3.4:

</pre>
        <blockquote type="cite" style="color: #000000;">
          <pre wrap=""> As specified in Section 4 this offerless INVITE
 MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
 header field in order to indicate support for Trickle-ICE to the
 Offerer (at the User Agent Server (UAS)).
</pre>
        </blockquote>
        <pre wrap="">How does the 3PCC controller know to include this option tag? Is it simply
indicating that the 3PCC controller supports the Trickle mechanism? If so,
what happens if the second party (the one who receives the offer in an INVITE)
doesn't support Trickle ICE? This is one of the sharper corner cases that I
think arises when you go to fix the analysis I describe in my DISCUSS above.</pre>
      </blockquote>
    </p>
    <p><br>
    </p>
    <p>Absent 3PCC, the "early offer" case is not interesting. Aside
      from 3PCC, its only purpose is interop with a version of H.323
      that was obsoleted in 1998.<br>
    </p>
    <p>/a<br>
      <br>
    </p>
  </body>
</html>

--------------385DD3D0045AEE9DE9243E49--


From nobody Tue Apr  3 10:24:42 2018
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 31BA912D7E8; Tue,  3 Apr 2018 10:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rtkOJ9MPvr4j; Tue,  3 Apr 2018 10:24:28 -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 2A17D124239; Tue,  3 Apr 2018 10:24:28 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w33HONFv086318 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:24:24 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Ben Campbell <ben@nostrum.com>, Peter Saint-Andre <stpeter@mozilla.com>
Cc: The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org, "ice@ietf.org" <ice@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com>
Date: Tue, 3 Apr 2018 12:24:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ia3VNxVmRye2840YnSkz6n3oc-E>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:24:30 -0000

+rtcweb. This is a three-WG situation, and I suspect rtcweb participants 
have an opinion on the topic.

/a

On 4/3/18 11:55 AM, Ben Campbell wrote:
>
>> On Apr 3, 2018, at 11:22 AM, Peter Saint-Andre <stpeter@mozilla.com> wrote:
>>
>> + ICE WG to address the cross-document DISCUSS only.
>>
>> On 4/3/18 1:29 AM, Adam Roach wrote:
>>
>> <snip/>
>>
>>> The second issue doesn't necessarily pertain to this document per se as much
>>> as it does the interaction among this document, draft-ietf-ice-trickle (Trickle
>>> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep
>>> (JSEP). The problem doesn't lie with any single document, but in the overall
>>> result of how they're currently structured.
>>>
>>> JSEP (in the RFC editor queue) refers to the "a=end-of-candidates" SDP attribute
>>> as appearing in Trickle ICE, section 9.3, which was true at one point in time.
>>> Somewhere along the line, this attribute's definition was moved from there
>>> into this document.
>>>
>>> There are several ways to fix this, each with their own drawbacks:
>>>
>>> 1. Move the SDP syntax for "a=end-of-candidates" back into the Trickle ICE
>>>    draft. Drawback: Trickle ICE does not currently define any normative SDP
>>>    behavior; and, in fact, could work in a system that doesn't use SDP at all.
>>>
>>> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant from the
>>>    perspective that ICE SDP defines SDP syntax for ICE in general (for both
>>>    SIP and JSEP), and such a move aggregates all of the SDP syntax into a
>>>    single document that is already necessary to reference from any document
>>>    that uses SDP for Trickle ICE. Drawback: the document doesn't presently
>>>    discuss Trickle ICE at all, and this would require a somewhat awkward
>>>    section that basically says "If you use [Trickle ICE] with SDP, the syntax
>>>    for the end-of-candidate marker is..."
>>>
>>> 3. Change JSEP to normatively depend on this document for the
>>>    "a=end-of-candidates" syntax. Drawback: This document is extremely
>>>    SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC 3264
>>>    behavior, independent of any SIP semantics.  Forcing JSEP to normatively
>>>    depend on a SIP specific document for a simple attribute syntax definition
>>>    seems to be letting the tail wag the dog.
>>>
>>> I believe that #2 is the least inelegant option, but I'm open to #1 and #3.
>>> However, The *current* situation -- in which JSEP normatively points to a
>>> document from which the text is cites has been removed out from under it -- is
>>> clearly wrong.
>> IMHO the ICE WG had consensus to remove all normative SDP references
>> from draft-ietf-ice-trickle and place them in
>> draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
>> document JSEP points to, as long as the "a=end-of-candidates" definition
>> can be found there?
> I was working on a comment to the same effect when I saw Peter’s.
>
> I see Adam’s option 1 as a non-starter since it explicitly reverses that consensus. I see 2 and 3 to be equally awkward, in which case 3 requires the least amount of structural change. If there was an option that required no change to jsep at all(since it is currently with the RFC editor), but IIUC, none of the choices allow for that.
>
> Thanks!
>
> Ben.
>


From nobody Tue Apr  3 10:26:32 2018
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 4A6F412D7E4; Tue,  3 Apr 2018 10:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5dhwjYtyKXHQ; Tue,  3 Apr 2018 10:26:28 -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 6D96F124239; Tue,  3 Apr 2018 10:26:28 -0700 (PDT)
Received: from [10.0.1.91] (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 w33HQPS7086736 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:26:26 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <1E208275-CECD-4907-BEA5-ECC2B06A80DA@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A872A1B8-3882-4E24-B005-38E34D8868FF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 12:26:24 -0500
In-Reply-To: <f8ec9593-3637-8e21-ccbb-a918b0e410e6@nostrum.com>
Cc: The IESG <iesg@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
To: Adam Roach <adam@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <4EA9C047-54A7-4FC3-A1F7-AFCC91F85529@nostrum.com> <f8ec9593-3637-8e21-ccbb-a918b0e410e6@nostrum.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Uq3kPZOy0GCw4cXJWyf46rpXPQs>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:26:30 -0000

--Apple-Mail=_A872A1B8-3882-4E24-B005-38E34D8868FF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 3, 2018, at 12:17 PM, Adam Roach <adam@nostrum.com> wrote:
>=20
> On 4/3/18 11:42 AM, Ben Campbell wrote:
>> I suspect (and assumed while reading this) is that the consideration =
that matters is the offer/answer exchange with a delayed offer. It calls =
it a 3PCC consideration because 3PCC uses it. I doubt people had in mind =
to fully specify 3PCC. If the WG agrees that is the case, would it make =
sense to re-label the section as =E2=80=9Cdelayed offer =
considerations=E2=80=9D, and merely mention that 3PCC uses that =
technique?
>=20
> I'm not sure how useful that is, as it's not entirely clear that =
Trickle ICE works with 3PCC at all -- see, for example, my later =
comment:

I=E2=80=99d also be perfectly happy to remove it, if the WG agrees. If =
someone cares, they can write a separate draft :-)

>=20
>=20
>=20
>> =C2=A74.3.4:
>>=20
>>=20
>>>  As specified in Section 4 this offerless INVITE
>>>  MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
>>>  header field in order to indicate support for Trickle-ICE to the
>>>  Offerer (at the User Agent Server (UAS)).
>>>=20
>> How does the 3PCC controller know to include this option tag? Is it =
simply
>> indicating that the 3PCC controller supports the Trickle mechanism? =
If so,
>> what happens if the second party (the one who receives the offer in =
an INVITE)
>> doesn't support Trickle ICE? This is one of the sharper corner cases =
that I
>> think arises when you go to fix the analysis I describe in my DISCUSS =
above.
>>=20
>=20
>=20
> Absent 3PCC, the "early offer" case is not interesting. Aside from =
3PCC, its only purpose is interop with a version of H.323 that was =
obsoleted in 1998.



--Apple-Mail=_A872A1B8-3882-4E24-B005-38E34D8868FF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrDuUAACgkQgFZKbJXz
1A3gExAAsB2BzigdS0R65QiCx5BBtgB0MWPoXBoAGzCEzCowax9co/63ulNMUWBn
H4YgtGDz7+p6RYToppjxyhpTGmyt0CeWHj1q5j87tIExSCWDEheypGQ0LDP8ptil
q/0PedHvOXmmPN2X6xmagrO87qHZD+bw41m3WZKlXVJf5b8Ubee8RtOXqeIvU41m
03MU9bc0Auih7hkowIxGqxOQ6Hr72AknjlK8oyqIp+wYlXTuY1q+4YHgDCtYxiV3
lazRwYZ9SU/R1jIi5XGK30mBLEJjXO4IZKE+94EuDiiEOsQyqhkrCA9fUlKIK9Qp
ZWvOpFrxov8zvARv+kMkg819UP3SyMxtB12QBZwmdYAXt0M7Zq4bX9PUr0xFJCO1
jo2eTGrklLB8bZqfws6YniDUE/MU21lgSoyBzS3+L1I4DsCda3ZykBR9f8b4/QKL
94mmN7n48NbZHu/wzkemK++cvXj/a0Pj2eSocizjFdIJ/ZkL+nHMhGQ4BqD3uu92
KFeXK7h7J2mkNRhwhlSLIPby6084WrIePONe5fEqgIC6v6fVjPLwqLVKEuNR05OZ
w4CPMNEaOJ2hCSi1ci5Ypc7bTDXSHR/+fZTSTvYYrMcY50dkJob5q+qN5NGoBrNn
bziNu5E3ADNgdAgLojt6TWQfPDFeLP9YM70vh3rcj2HXJkGWfCo=
=D9Sb
-----END PGP SIGNATURE-----

--Apple-Mail=_A872A1B8-3882-4E24-B005-38E34D8868FF--


From nobody Tue Apr  3 10:27:30 2018
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 D8AAB12EA55 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 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, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eeDgo6F0yLp1 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:27:23 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 7E26712EA42 for <mmusic@ietf.org>; Tue,  3 Apr 2018 10:27:20 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id j143-v6so16668876oih.11 for <mmusic@ietf.org>; Tue, 03 Apr 2018 10:27: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=G1O9nTQ4sadQaByb4/ey+xHWYMSBZAQ4eH3tlOAnrgU=; b=zxs+IRIGNShwuDXo/bhCiGPdCmXx411cc0biRt0in8w7mnyF3fpiJ+TnwIq29vHZsD 1EaJ8/7ZOdklB4inz5V4lMx+1Jyrqi7r6jRJzAgzTKtJbHm1uN2iLbO7CZsgIEeybvrs 8BSWYB27KdMHim4ZBEK/RMcOYrtyVXC1GqAifCn0CMdSONFFhZZLkWpnSA1VqOngdjvU 93/hNnAqdJV4498cWuerD3kFutuA7cWM8lkJZ9M/U3xw9ClBHnWTGVJIcbkZet+v8tfq 5BU78D0M1zCQuCCEYBcLHf34AMMJV7bwT+FrvSGpbfanLxA6aDUba8rMiuvQd6GwOz2Q EyJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=G1O9nTQ4sadQaByb4/ey+xHWYMSBZAQ4eH3tlOAnrgU=; b=J7kFrjko3am8v23bCMipiAi20NvkVfjoVo95YINSIbli+35BKfCpSyfc2bL566/5u+ n5ZZwufn/nGFNbmdQAPJ/YaC/mo8tM/zDV2TFjlkwA8xFIISZrcdUeKCPI8odCJp3QbN Rxe9L65Ppb+Wo0CojaJO18O7L2Mt7KYHwbYD6La1YCD4rVryyFrxK3iia8R9uvu0aRXb BaKpcS1WtIMJhMeIawZVNzlXx4rv2YXjyk0PIHne4wpjqhCJiBVyhTMB3K13neHG4Qul lvJak6gxyPR33Ngt6i3UQqLy61Njg7ISVXq5qo+OOwpcXH3hCxlXdswkw4adIHhIw4y6 Y3kw==
X-Gm-Message-State: ALQs6tALHNojKYG5y66HQAYcrR/L+1YtrtbvmzGDZeFLOsmJC+1xLxcZ LDeDh+ss1eAHf/VhHn1jF462uwet3Qa1E6WPNk5XAw==
X-Google-Smtp-Source: AIpwx4+Un7e+7Va9JzAIHX1EWkvd2b/zoro/1EhceaibBYa5mpKhI4NxSnwz0Rrda1ry9rYHma+vRckImraVLyuRE4Y=
X-Received: by 2002:aca:cc53:: with SMTP id c80-v6mr8207674oig.174.1522776439907;  Tue, 03 Apr 2018 10:27:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.130 with HTTP; Tue, 3 Apr 2018 10:26:39 -0700 (PDT)
In-Reply-To: <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 3 Apr 2018 10:26:39 -0700
Message-ID: <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Ben Campbell <ben@nostrum.com>, Peter Saint-Andre <stpeter@mozilla.com>, mmusic-chairs@ietf.org,  mmusic WG <mmusic@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>,  "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>,  draft-ietf-mmusic-trickle-ice-sip@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c601cc0568f504b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/zy0VrpejLxbbtWToBlf_YBoVNPo>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:27:25 -0000

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

On Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <adam@nostrum.com> wrote:

> +rtcweb. This is a three-WG situation, and I suspect rtcweb participants
> have an opinion on the topic.
>
> /a
>
>
> On 4/3/18 11:55 AM, Ben Campbell wrote:
>
>>
>> On Apr 3, 2018, at 11:22 AM, Peter Saint-Andre <stpeter@mozilla.com>
>>> wrote:
>>>
>>> + ICE WG to address the cross-document DISCUSS only.
>>>
>>> On 4/3/18 1:29 AM, Adam Roach wrote:
>>>
>>> <snip/>
>>>
>>> The second issue doesn't necessarily pertain to this document per se as
>>>> much
>>>> as it does the interaction among this document, draft-ietf-ice-trickle
>>>> (Trickle
>>>> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and
>>>> draft-ietf-rtcweb-jsep
>>>> (JSEP). The problem doesn't lie with any single document, but in the
>>>> overall
>>>> result of how they're currently structured.
>>>>
>>>> JSEP (in the RFC editor queue) refers to the "a=3Dend-of-candidates" S=
DP
>>>> attribute
>>>> as appearing in Trickle ICE, section 9.3, which was true at one point
>>>> in time.
>>>> Somewhere along the line, this attribute's definition was moved from
>>>> there
>>>> into this document.
>>>>
>>>> There are several ways to fix this, each with their own drawbacks:
>>>>
>>>> 1. Move the SDP syntax for "a=3Dend-of-candidates" back into the Trick=
le
>>>> ICE
>>>>    draft. Drawback: Trickle ICE does not currently define any normativ=
e
>>>> SDP
>>>>    behavior; and, in fact, could work in a system that doesn't use SDP
>>>> at all.
>>>>
>>>> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant
>>>> from the
>>>>    perspective that ICE SDP defines SDP syntax for ICE in general (for
>>>> both
>>>>    SIP and JSEP), and such a move aggregates all of the SDP syntax int=
o
>>>> a
>>>>    single document that is already necessary to reference from any
>>>> document
>>>>    that uses SDP for Trickle ICE. Drawback: the document doesn't
>>>> presently
>>>>    discuss Trickle ICE at all, and this would require a somewhat awkwa=
rd
>>>>    section that basically says "If you use [Trickle ICE] with SDP, the
>>>> syntax
>>>>    for the end-of-candidate marker is..."
>>>>
>>>> 3. Change JSEP to normatively depend on this document for the
>>>>    "a=3Dend-of-candidates" syntax. Drawback: This document is extremel=
y
>>>>    SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC
>>>> 3264
>>>>    behavior, independent of any SIP semantics.  Forcing JSEP to
>>>> normatively
>>>>    depend on a SIP specific document for a simple attribute syntax
>>>> definition
>>>>    seems to be letting the tail wag the dog.
>>>>
>>>> I believe that #2 is the least inelegant option, but I'm open to #1 an=
d
>>>> #3.
>>>> However, The *current* situation -- in which JSEP normatively points t=
o
>>>> a
>>>> document from which the text is cites has been removed out from under
>>>> it -- is
>>>> clearly wrong.
>>>>
>>> IMHO the ICE WG had consensus to remove all normative SDP references
>>> from draft-ietf-ice-trickle and place them in
>>> draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
>>> document JSEP points to, as long as the "a=3Dend-of-candidates" definit=
ion
>>> can be found there?
>>>
>> I was working on a comment to the same effect when I saw Peter=E2=80=99s=
.
>>
>> I see Adam=E2=80=99s option 1 as a non-starter since it explicitly rever=
ses that
>> consensus. I see 2 and 3 to be equally awkward, in which case 3 requires
>> the least amount of structural change. If there was an option that requi=
red
>> no change to jsep at all(since it is currently with the RFC editor), but
>> IIUC, none of the choices allow for that.
>>
>
I don't think #3 is acceptable. AFAIK JSEP has no other dependencies on
SIP. If you think #2 and #3 are equally awkward, lets do #2.

-Ekr


>> Thanks!
>>
>> Ben.
>>
>>
>

--000000000000c601cc0568f504b6
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 Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@nostrum.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">+rtcweb. This is a three-WG =
situation, and I suspect rtcweb participants have an opinion on the topic.<=
span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
/a</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On 4/3/18 11:55 AM, 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">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Apr 3, 2018, at 11:22 AM, Peter Saint-Andre &lt;<a href=3D"mailto:stpete=
r@mozilla.com" target=3D"_blank">stpeter@mozilla.com</a>&gt; wrote:<br>
<br>
+ ICE WG to address the cross-document DISCUSS only.<br>
<br>
On 4/3/18 1:29 AM, Adam Roach wrote:<br>
<br>
&lt;snip/&gt;<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The second issue doesn&#39;t necessarily pertain to this document per se as=
 much<br>
as it does the interaction among this document, draft-ietf-ice-trickle (Tri=
ckle<br>
ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep<b=
r>
(JSEP). The problem doesn&#39;t lie with any single document, but in the ov=
erall<br>
result of how they&#39;re currently structured.<br>
<br>
JSEP (in the RFC editor queue) refers to the &quot;a=3Dend-of-candidates&qu=
ot; SDP attribute<br>
as appearing in Trickle ICE, section 9.3, which was true at one point in ti=
me.<br>
Somewhere along the line, this attribute&#39;s definition was moved from th=
ere<br>
into this document.<br>
<br>
There are several ways to fix this, each with their own drawbacks:<br>
<br>
1. Move the SDP syntax for &quot;a=3Dend-of-candidates&quot; back into the =
Trickle ICE<br>
=C2=A0 =C2=A0draft. Drawback: Trickle ICE does not currently define any nor=
mative SDP<br>
=C2=A0 =C2=A0behavior; and, in fact, could work in a system that doesn&#39;=
t use SDP at all.<br>
<br>
2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant from =
the<br>
=C2=A0 =C2=A0perspective that ICE SDP defines SDP syntax for ICE in general=
 (for both<br>
=C2=A0 =C2=A0SIP and JSEP), and such a move aggregates all of the SDP synta=
x into a<br>
=C2=A0 =C2=A0single document that is already necessary to reference from an=
y document<br>
=C2=A0 =C2=A0that uses SDP for Trickle ICE. Drawback: the document doesn&#3=
9;t presently<br>
=C2=A0 =C2=A0discuss Trickle ICE at all, and this would require a somewhat =
awkward<br>
=C2=A0 =C2=A0section that basically says &quot;If you use [Trickle ICE] wit=
h SDP, the syntax<br>
=C2=A0 =C2=A0for the end-of-candidate marker is...&quot;<br>
<br>
3. Change JSEP to normatively depend on this document for the<br>
=C2=A0 =C2=A0&quot;a=3Dend-of-candidates&quot; syntax. Drawback: This docum=
ent is extremely<br>
=C2=A0 =C2=A0SIP-specific, while JSEP is based solely on RFC 4566 syntax an=
d RFC 3264<br>
=C2=A0 =C2=A0behavior, independent of any SIP semantics.=C2=A0 Forcing JSEP=
 to normatively<br>
=C2=A0 =C2=A0depend on a SIP specific document for a simple attribute synta=
x definition<br>
=C2=A0 =C2=A0seems to be letting the tail wag the dog.<br>
<br>
I believe that #2 is the least inelegant option, but I&#39;m open to #1 and=
 #3.<br>
However, The *current* situation -- in which JSEP normatively points to a<b=
r>
document from which the text is cites has been removed out from under it --=
 is<br>
clearly wrong.<br>
</blockquote>
IMHO the ICE WG had consensus to remove all normative SDP references<br>
from draft-ietf-ice-trickle and place them in<br>
draft-ietf-mmusic-trickle-ice-<wbr>sip. Does it really matter what kind of<=
br>
document JSEP points to, as long as the &quot;a=3Dend-of-candidates&quot; d=
efinition<br>
can be found there?<br>
</blockquote>
I was working on a comment to the same effect when I saw Peter=E2=80=99s.<b=
r>
<br>
I see Adam=E2=80=99s option 1 as a non-starter since it explicitly reverses=
 that consensus. I see 2 and 3 to be equally awkward, in which case 3 requi=
res the least amount of structural change. If there was an option that requ=
ired no change to jsep at all(since it is currently with the RFC editor), b=
ut IIUC, none of the choices allow for that.<br></blockquote></div></div></=
blockquote><div><br></div><div>I don&#39;t think #3 is acceptable. AFAIK JS=
EP has no other dependencies on SIP. If you think #2 and #3 are equally awk=
ward, lets do #2.<br></div><div><br></div><div>-Ekr</div><div><br></div><bl=
ockquote 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"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div></div>

--000000000000c601cc0568f504b6--


From nobody Tue Apr  3 10:36:02 2018
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 E489F12D7E8; Tue,  3 Apr 2018 10:35:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SB27yzaLq0yu; Tue,  3 Apr 2018 10:35:57 -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 0611012D7E5; Tue,  3 Apr 2018 10:35:56 -0700 (PDT)
Received: from [10.0.1.91] (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 w33HZrU7088315 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:35:54 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B408C13E-FC4A-41CD-9814-E8C43E6D6732"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 12:35:52 -0500
In-Reply-To: <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com>
Cc: Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@mozilla.com>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
To: Eric Rescorla <ekr@rtfm.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Dvx_doAyIeTdIuMOlXnP53QqrAU>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:35:59 -0000

--Apple-Mail=_B408C13E-FC4A-41CD-9814-E8C43E6D6732
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies =
on SIP. If you think #2 and #3 are equally awkward, lets do #2.
>=20

I said they are equally awkward (by which I mean equally awkward for =
readers after publication), but 3 requires fewer changes (that is, less =
effort.).

If we want to go for least awkward, that probably means a separate =
trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99s=
 the past of most effort.

But honestly, I think this is the sort of point that we should defer to =
WG consensus.

Ben.

--Apple-Mail=_B408C13E-FC4A-41CD-9814-E8C43E6D6732
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrDu3gACgkQgFZKbJXz
1A0c4A/+Jje2dM1gnZrawy5A+JrKVqHwZ2oDQT59NU6u8B1tjSbB9Dg4DSMvJq9V
bEFfzf68UqQBbtT82qdxtYsrCnYLqHmwfP6NxDBhIyRPCYaumoXEAnHdRuV4iWCL
oYpnqmRpxWa1S7odvvF5bsoo3DCsePedxvMGI/Y88xp7QA2nX1ULu5HZhZ6GxHR2
KoAZAqbX+sB3Te4pOh3FG8HVH79D4KLkkFca+nSPQTJiK1r4SY1bbA4VcYeOmvCa
1/3+b9Hrk6FZTXxj3cs8EEAHNI0KzC4up64QmkuGU9leu6DvOiR2rZx0AOzoIEHs
RnziWWWVvYBIn084KmsvxyzPmG/fYJcnrHyggct1r6U8Dl+ZJPbKn/TLT8LDDJU1
kUW/RZYaRONiKWnZU/zUOfNY+y1x+XhEvUAsxxcFyr8eLXE9Pqndu/JaQQDm/CGQ
dM95sWz5WcB6x5GraMz3YAVzWqPpE0lG79uD41PrL/AR7ZR+WeKCYnobgNEBTGks
xoZh55nYIwz5uq1YVacdJpcnb9n4pL6mem1htbn5wIqzKtCaE68h9ERGqK8IEddw
pJfH5tPm/qCiL/KAz01Uoe/unLMp1bpdKKnl198HB9wAb3gtkbVgRayTlwY36/3O
Dr8kp3XxNjBujE5H7hG8hgroQGpQWmy/srGjk700e741p88seoQ=
=vtUO
-----END PGP SIGNATURE-----

--Apple-Mail=_B408C13E-FC4A-41CD-9814-E8C43E6D6732--


From nobody Tue Apr  3 10:39:02 2018
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 ACFE512D7E8 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jIz8vLhz13q for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:38:57 -0700 (PDT)
Received: from mail-pl0-x232.google.com (mail-pl0-x232.google.com [IPv6:2607:f8b0:400e:c01::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 343B412EADD for <mmusic@ietf.org>; Tue,  3 Apr 2018 10:38:43 -0700 (PDT)
Received: by mail-pl0-x232.google.com with SMTP id u11-v6so9847389plq.1 for <mmusic@ietf.org>; Tue, 03 Apr 2018 10:38:43 -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=r0jnHAg/mfl7AF7pE4yFS9tRKui789opIZmUZylMp2Q=; b=ogI3rVhbqRR7FEOXvkLHM+rIBXcIPAxI7EKOkCEQLGoJDwn9Cn05OyoVVgAWcN/p16 x5R5AsxXiTKnKltb1EmkNPzZm5yZ9iwVKNQekdScg+Yey9nEeDqxtYNtT0MoFquFinK1 7sCIw+YBnna2SRKbfnGkB4HXzNsHIkhPWDFNB+iK1tdGIiR8MALjjSjkTd53I4gZRU5J 0xP+d+bYBkgXjQF3lBwncilbjRlFHrCm+e+V8bzW5mN9e5y7Ksu0hGYWq7nFXiCYZEor Iijz3TJnoNbm+k/+wFxPAtjZfchogwpvqRpmhElxHbeJY5bkF3dq1U+DXxh4j9sXOoJh /qpQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=r0jnHAg/mfl7AF7pE4yFS9tRKui789opIZmUZylMp2Q=; b=oxXV5d5DzoBKgUfq5gvtIq0vlNezqtqIXylHDLkZ2GfQYdfM0r7v0cW3WJeNUgw/zn P7SGrW+GHr0myGkjfAjxPNnnTYwhBa/Cjmqr6wqawEpl7F76Eww1YS3+XLBcZQ6yBzfj dXXWFFj+n4Z4c8hFrRDJ0a43owGp14VtSIQ7l4BSE6xqkUz1VDACCymgJeLsravQa94X EcDxsh2caL0dsNxFdrF6eetmXq2YhiQG4AB4mG009nbysHHUgjQMgJd4nmSBx/MulTPI 9YgL4V4aBEw+YPcAqRpk5y/MSB+iXubMnIV+P67nNQIihYYRtT9Ml+58e+7t75i2QqaG Ir5A==
X-Gm-Message-State: AElRT7EgLmeI8iB3fRs9UTn0cE3hQPIb0l/0i1oPiFAzaOTEPHym/A+e lOpaIB3dvaYECkhCoeNnPXATAUY1
X-Google-Smtp-Source: AIpwx498FnUeZ4XCg7hdEq1PKhaP+zWG4f44HZsYgATHlLFb7En1FHOmZPAj1xsTUPVyfJrKQx53QQ==
X-Received: by 2002:a17:902:566:: with SMTP id 93-v6mr14653900plf.327.1522777122694;  Tue, 03 Apr 2018 10:38:42 -0700 (PDT)
Received: from mail-pl0-f54.google.com (mail-pl0-f54.google.com. [209.85.160.54]) by smtp.gmail.com with ESMTPSA id f86sm6183078pfk.153.2018.04.03.10.38.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 10:38:41 -0700 (PDT)
Received: by mail-pl0-f54.google.com with SMTP id b6-v6so7846326pla.11; Tue, 03 Apr 2018 10:38:41 -0700 (PDT)
X-Received: by 2002:a17:902:8d84:: with SMTP id v4-v6mr14819021plo.215.1522777121234;  Tue, 03 Apr 2018 10:38:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.182.102 with HTTP; Tue, 3 Apr 2018 10:38:39 -0700 (PDT)
In-Reply-To: <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 3 Apr 2018 13:38:39 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com>
Message-ID: <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Adam Roach <adam@nostrum.com>, Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>,  mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>,  Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>,  The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
Content-Type: multipart/alternative; boundary="00000000000062241f0568f52d24"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/s9KpmfQ2mCueRn7kAzrzDTGiIbs>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:39:00 -0000

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

On Tue, Apr 3, 2018 at 1:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <adam@nostrum.com> wrote:
>
>> On 4/3/18 1:29 AM, Adam Roach wrote:
>>>>
>>>> <snip/>
>>>>
>>>> The second issue doesn't necessarily pertain to this document per se a=
s
>>>>> much
>>>>> as it does the interaction among this document, draft-ietf-ice-trickl=
e
>>>>> (Trickle
>>>>> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and
>>>>> draft-ietf-rtcweb-jsep
>>>>> (JSEP). The problem doesn't lie with any single document, but in the
>>>>> overall
>>>>> result of how they're currently structured.
>>>>>
>>>>> JSEP (in the RFC editor queue) refers to the "a=3Dend-of-candidates" =
SDP
>>>>> attribute
>>>>> as appearing in Trickle ICE, section 9.3, which was true at one point
>>>>> in time.
>>>>> Somewhere along the line, this attribute's definition was moved from
>>>>> there
>>>>> into this document.
>>>>>
>>>>> There are several ways to fix this, each with their own drawbacks:
>>>>>
>>>>> 1. Move the SDP syntax for "a=3Dend-of-candidates" back into the Tric=
kle
>>>>> ICE
>>>>>    draft. Drawback: Trickle ICE does not currently define any
>>>>> normative SDP
>>>>>    behavior; and, in fact, could work in a system that doesn't use SD=
P
>>>>> at all.
>>>>>
>>>>> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant
>>>>> from the
>>>>>    perspective that ICE SDP defines SDP syntax for ICE in general (fo=
r
>>>>> both
>>>>>    SIP and JSEP), and such a move aggregates all of the SDP syntax
>>>>> into a
>>>>>    single document that is already necessary to reference from any
>>>>> document
>>>>>    that uses SDP for Trickle ICE. Drawback: the document doesn't
>>>>> presently
>>>>>    discuss Trickle ICE at all, and this would require a somewhat
>>>>> awkward
>>>>>    section that basically says "If you use [Trickle ICE] with SDP, th=
e
>>>>> syntax
>>>>>    for the end-of-candidate marker is..."
>>>>>
>>>>> 3. Change JSEP to normatively depend on this document for the
>>>>>    "a=3Dend-of-candidates" syntax. Drawback: This document is extreme=
ly
>>>>>    SIP-specific, while JSEP is based solely on RFC 4566 syntax and RF=
C
>>>>> 3264
>>>>>    behavior, independent of any SIP semantics.  Forcing JSEP to
>>>>> normatively
>>>>>    depend on a SIP specific document for a simple attribute syntax
>>>>> definition
>>>>>    seems to be letting the tail wag the dog.
>>>>>
>>>>> I believe that #2 is the least inelegant option, but I'm open to #1
>>>>> and #3.
>>>>> However, The *current* situation -- in which JSEP normatively points
>>>>> to a
>>>>> document from which the text is cites has been removed out from under
>>>>> it -- is
>>>>> clearly wrong.
>>>>>
>>>> IMHO the ICE WG had consensus to remove all normative SDP references
>>>> from draft-ietf-ice-trickle and place them in
>>>> draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
>>>> document JSEP points to, as long as the "a=3Dend-of-candidates" defini=
tion
>>>> can be found there?
>>>>
>>> I was working on a comment to the same effect when I saw Peter=E2=80=99=
s.
>>>
>>> I see Adam=E2=80=99s option 1 as a non-starter since it explicitly reve=
rses that
>>> consensus. I see 2 and 3 to be equally awkward, in which case 3 require=
s
>>> the least amount of structural change. If there was an option that requ=
ired
>>> no change to jsep at all(since it is currently with the RFC editor), bu=
t
>>> IIUC, none of the choices allow for that.
>>>
>>
> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies on
> SIP. If you think #2 and #3 are equally awkward, lets do #2.
>
>
Do you want to move all other trickle ICE specific SDP related changes from
 draft-ietf-mmusic-trickle-ice-sip to draft-ietf-mmusic-ice-sip-sdp?

It is not just end-of-candidates, but also support for c=3D0.0.0.0 in offer=
s,
SDP offers without the candidates, different mismatch rules. As it stands,
draft-ietf-mmusic-trickle-ice-sip changes how
draft-ietf-mmusic-ice-sip-sdp works
when trickle ICE is used.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
 class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><br></div></d=
iv><div class=3D"gmail_quote">On Tue, Apr 3, 2018 at 1:26 PM, Eric Rescorla=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ek=
r@rtfm.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 dir=
=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div=
><div class=3D"h5">On Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <span dir=3D=
"ltr">&lt;<a href=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@nostru=
m.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D=
"m_6587937063968571836HOEnZb"><div class=3D"m_6587937063968571836h5"><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 4/3/18 1:29 AM, =
Adam Roach wrote:<br>
<br>
&lt;snip/&gt;<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The second issue doesn&#39;t necessarily pertain to this document per se as=
 much<br>
as it does the interaction among this document, draft-ietf-ice-trickle (Tri=
ckle<br>
ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep<b=
r>
(JSEP). The problem doesn&#39;t lie with any single document, but in the ov=
erall<br>
result of how they&#39;re currently structured.<br>
<br>
JSEP (in the RFC editor queue) refers to the &quot;a=3Dend-of-candidates&qu=
ot; SDP attribute<br>
as appearing in Trickle ICE, section 9.3, which was true at one point in ti=
me.<br>
Somewhere along the line, this attribute&#39;s definition was moved from th=
ere<br>
into this document.<br>
<br>
There are several ways to fix this, each with their own drawbacks:<br>
<br>
1. Move the SDP syntax for &quot;a=3Dend-of-candidates&quot; back into the =
Trickle ICE<br>
=C2=A0 =C2=A0draft. Drawback: Trickle ICE does not currently define any nor=
mative SDP<br>
=C2=A0 =C2=A0behavior; and, in fact, could work in a system that doesn&#39;=
t use SDP at all.<br>
<br>
2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant from =
the<br>
=C2=A0 =C2=A0perspective that ICE SDP defines SDP syntax for ICE in general=
 (for both<br>
=C2=A0 =C2=A0SIP and JSEP), and such a move aggregates all of the SDP synta=
x into a<br>
=C2=A0 =C2=A0single document that is already necessary to reference from an=
y document<br>
=C2=A0 =C2=A0that uses SDP for Trickle ICE. Drawback: the document doesn&#3=
9;t presently<br>
=C2=A0 =C2=A0discuss Trickle ICE at all, and this would require a somewhat =
awkward<br>
=C2=A0 =C2=A0section that basically says &quot;If you use [Trickle ICE] wit=
h SDP, the syntax<br>
=C2=A0 =C2=A0for the end-of-candidate marker is...&quot;<br>
<br>
3. Change JSEP to normatively depend on this document for the<br>
=C2=A0 =C2=A0&quot;a=3Dend-of-candidates&quot; syntax. Drawback: This docum=
ent is extremely<br>
=C2=A0 =C2=A0SIP-specific, while JSEP is based solely on RFC 4566 syntax an=
d RFC 3264<br>
=C2=A0 =C2=A0behavior, independent of any SIP semantics.=C2=A0 Forcing JSEP=
 to normatively<br>
=C2=A0 =C2=A0depend on a SIP specific document for a simple attribute synta=
x definition<br>
=C2=A0 =C2=A0seems to be letting the tail wag the dog.<br>
<br>
I believe that #2 is the least inelegant option, but I&#39;m open to #1 and=
 #3.<br>
However, The *current* situation -- in which JSEP normatively points to a<b=
r>
document from which the text is cites has been removed out from under it --=
 is<br>
clearly wrong.<br>
</blockquote>
IMHO the ICE WG had consensus to remove all normative SDP references<br>
from draft-ietf-ice-trickle and place them in<br>
draft-ietf-mmusic-trickle-ice-<wbr>sip. Does it really matter what kind of<=
br>
document JSEP points to, as long as the &quot;a=3Dend-of-candidates&quot; d=
efinition<br>
can be found there?<br>
</blockquote>
I was working on a comment to the same effect when I saw Peter=E2=80=99s.<b=
r>
<br>
I see Adam=E2=80=99s option 1 as a non-starter since it explicitly reverses=
 that consensus. I see 2 and 3 to be equally awkward, in which case 3 requi=
res the least amount of structural change. If there was an option that requ=
ired no change to jsep at all(since it is currently with the RFC editor), b=
ut IIUC, none of the choices allow for that.<br></blockquote></div></div></=
blockquote><div><br></div></div></div><div>I don&#39;t think #3 is acceptab=
le. AFAIK JSEP has no other dependencies on SIP. If you think #2 and #3 are=
 equally awkward, lets do #2.<br></div><div><br></div></div></div></div></b=
lockquote><div><br></div>Do you want to move all other trickle ICE specific=
 SDP related changes from =C2=A0draft-ietf-mmusic-trickle-ice-sip to draft-=
ietf-mmusic-ice-sip-sdp?</div><div class=3D"gmail_quote"><br></div><div cla=
ss=3D"gmail_quote">It is not just end-of-candidates, but also support for c=
=3D0.0.0.0 in offers, SDP offers without the candidates, different mismatch=
 rules. As it stands,=C2=A0

<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:s=
mall;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm=
al;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;t=
ext-transform:none;white-space:normal;word-spacing:0px;background-color:rgb=
(255,255,255);text-decoration-style:initial;text-decoration-color:initial;f=
loat:none;display:inline">draft-ietf-mmusic-trickle-ice-sip</span>=C2=A0cha=
nges how=C2=A0<span style=3D"color:rgb(34,34,34);font-family:arial,sans-ser=
if;font-size:small;font-style:normal;font-variant-ligatures:normal;font-var=
iant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;tex=
t-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgr=
ound-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-c=
olor:initial;float:none;display:inline">draft-ietf-mmusic-ice-sip-sdp</span=
>=C2=A0works when trickle ICE is used.</div><div class=3D"gmail_quote"><br>=
</div><div class=3D"gmail_quote">Regards,<br><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br=
 class=3D"gmail-Apple-interchange-newline">

=C2=A0</div></div></div></div>

--00000000000062241f0568f52d24--


From nobody Tue Apr  3 10:43:52 2018
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 0556812D7E5 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8o5Maa-XRO1b for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:43:48 -0700 (PDT)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::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 EF13112E8A4 for <mmusic@ietf.org>; Tue,  3 Apr 2018 10:43:42 -0700 (PDT)
Received: by mail-ot0-x22a.google.com with SMTP id y46-v6so20336441otd.4 for <mmusic@ietf.org>; Tue, 03 Apr 2018 10:43:42 -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=tE9HlUbly+CiDnlEaCOYfi08zdkA8PkOcCK6gnWiEmI=; b=pISTsTrVmvTrgfo+xknkhFWxX5XOslVKnF6G0lTMhKqkX7fgyWlpCTjXPmHiK0Oz0O Ob/7J7ZghHJKdwQclILRit1DUU2MQuTGXMxvcQUts+7+3we69onY8sRgkSuIREqZk4OW AfeiFRHX36oRVXS1YkxxwL6ChCLDHfnQfpup1ozRyLzKP+6MHnRSkEuCmXpm18A4wgGh EFsemtdJ7xB5WSxFf16nyez4u5e7882l3zZFcFkHZxr2t5L7zLHw8BNjDH0e7HD1/zcN QOBlI24t2Hrv2Z4dF0HiQ3WpoewufPbfDCafLb+2PWC814lTEdkuDnn7lcfEEEmf8gAj tjpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tE9HlUbly+CiDnlEaCOYfi08zdkA8PkOcCK6gnWiEmI=; b=IYe3HM0K8oYP09tRrgKmXPn5F+fADQ+mtNsxlJ2jNWqWCMfePyZEU9NCvjcuq3En8Q Y0TY8ukCRKNUyBDWA1cxFmgYVhvAtG3S+ltOoYzH1/lhQ2S8fFVaKxCE+X7sm+9KAqi4 KNp8O1e5Yfewj8Ppt+m4Mn0nY4lJFjZ9SHY5Yg2GJk/h438+OK04j9ws4b8PylVFupE7 7dLuJG2i5JR2dqyZrAUESTWeq5xGPr92Anm6HdF401MLY8uwoFRhnIrDw0uO7q9NGRnG iCq3ro1e9iQuz3Tms7rslI5oW8qqIpYogbTykgw20DSTRmp10Ns+m6i6vFuJjfydmG5p 77Tw==
X-Gm-Message-State: ALQs6tDzWMWiH3O8c54n3MlfeVid4KAByM5KMBgVbgdGCDogXeDUtHAu kVvyUjBjQ81MCOPq+iQRYy62OzDwVcBQDL/RgyKjsw==
X-Google-Smtp-Source: AIpwx49170UyZZP306Vxy3u3NlPB1qF1gIJiVcfDff6NEc4zyRumGbc327wYOdU7nr5O5rwnXezRuletSRAR/cUskcg=
X-Received: by 2002:a9d:4289:: with SMTP id r9-v6mr9192797ote.44.1522777422318;  Tue, 03 Apr 2018 10:43:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.130 with HTTP; Tue, 3 Apr 2018 10:43:01 -0700 (PDT)
In-Reply-To: <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 3 Apr 2018 10:43:01 -0700
Message-ID: <CABcZeBMwmisiM0Vpc9Pr53wOPi=J6RAKiNiO8JEkPOtcTjOZvA@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Adam Roach <adam@nostrum.com>, Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>,  mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>,  Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>,  The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005467310568f53f55"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uvh3Bj04bexEVUJIF4UVC6DWRRs>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:43:50 -0000

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

On Tue, Apr 3, 2018 at 10:38 AM, Roman Shpount <roman@telurix.com> wrote:

>
>
>
> On Tue, Apr 3, 2018 at 1:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>>
>> On Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <adam@nostrum.com> wrote:
>>
>>> On 4/3/18 1:29 AM, Adam Roach wrote:
>>>>>
>>>>> <snip/>
>>>>>
>>>>> The second issue doesn't necessarily pertain to this document per se
>>>>>> as much
>>>>>> as it does the interaction among this document,
>>>>>> draft-ietf-ice-trickle (Trickle
>>>>>> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and
>>>>>> draft-ietf-rtcweb-jsep
>>>>>> (JSEP). The problem doesn't lie with any single document, but in the
>>>>>> overall
>>>>>> result of how they're currently structured.
>>>>>>
>>>>>> JSEP (in the RFC editor queue) refers to the "a=3Dend-of-candidates"
>>>>>> SDP attribute
>>>>>> as appearing in Trickle ICE, section 9.3, which was true at one poin=
t
>>>>>> in time.
>>>>>> Somewhere along the line, this attribute's definition was moved from
>>>>>> there
>>>>>> into this document.
>>>>>>
>>>>>> There are several ways to fix this, each with their own drawbacks:
>>>>>>
>>>>>> 1. Move the SDP syntax for "a=3Dend-of-candidates" back into the
>>>>>> Trickle ICE
>>>>>>    draft. Drawback: Trickle ICE does not currently define any
>>>>>> normative SDP
>>>>>>    behavior; and, in fact, could work in a system that doesn't use
>>>>>> SDP at all.
>>>>>>
>>>>>> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegan=
t
>>>>>> from the
>>>>>>    perspective that ICE SDP defines SDP syntax for ICE in general
>>>>>> (for both
>>>>>>    SIP and JSEP), and such a move aggregates all of the SDP syntax
>>>>>> into a
>>>>>>    single document that is already necessary to reference from any
>>>>>> document
>>>>>>    that uses SDP for Trickle ICE. Drawback: the document doesn't
>>>>>> presently
>>>>>>    discuss Trickle ICE at all, and this would require a somewhat
>>>>>> awkward
>>>>>>    section that basically says "If you use [Trickle ICE] with SDP,
>>>>>> the syntax
>>>>>>    for the end-of-candidate marker is..."
>>>>>>
>>>>>> 3. Change JSEP to normatively depend on this document for the
>>>>>>    "a=3Dend-of-candidates" syntax. Drawback: This document is extrem=
ely
>>>>>>    SIP-specific, while JSEP is based solely on RFC 4566 syntax and
>>>>>> RFC 3264
>>>>>>    behavior, independent of any SIP semantics.  Forcing JSEP to
>>>>>> normatively
>>>>>>    depend on a SIP specific document for a simple attribute syntax
>>>>>> definition
>>>>>>    seems to be letting the tail wag the dog.
>>>>>>
>>>>>> I believe that #2 is the least inelegant option, but I'm open to #1
>>>>>> and #3.
>>>>>> However, The *current* situation -- in which JSEP normatively points
>>>>>> to a
>>>>>> document from which the text is cites has been removed out from unde=
r
>>>>>> it -- is
>>>>>> clearly wrong.
>>>>>>
>>>>> IMHO the ICE WG had consensus to remove all normative SDP references
>>>>> from draft-ietf-ice-trickle and place them in
>>>>> draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
>>>>> document JSEP points to, as long as the "a=3Dend-of-candidates"
>>>>> definition
>>>>> can be found there?
>>>>>
>>>> I was working on a comment to the same effect when I saw Peter=E2=80=
=99s.
>>>>
>>>> I see Adam=E2=80=99s option 1 as a non-starter since it explicitly rev=
erses
>>>> that consensus. I see 2 and 3 to be equally awkward, in which case 3
>>>> requires the least amount of structural change. If there was an option=
 that
>>>> required no change to jsep at all(since it is currently with the RFC
>>>> editor), but IIUC, none of the choices allow for that.
>>>>
>>>
>> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies on
>> SIP. If you think #2 and #3 are equally awkward, lets do #2.
>>
>>
> Do you want to move all other trickle ICE specific SDP related changes
> from  draft-ietf-mmusic-trickle-ice-sip to draft-ietf-mmusic-ice-sip-sdp?
>
> It is not just end-of-candidates, but also support for c=3D0.0.0.0 in
> offers, SDP offers without the candidates, different mismatch rules. As i=
t
> stands,  draft-ietf-mmusic-trickle-ice-sip changes how
> draft-ietf-mmusic-ice-sip-sdp works when trickle ICE is used.
>

I want to do whatever is necessary to remove the normative dependency from
JSEP to SIP

-Ekr


> Regards,
> _____________
> Roman Shpount
>
>
>

--0000000000005467310568f53f55
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 Tue, Apr 3, 2018 at 10:38 AM, Roman Shpount <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:roman@telurix.com" target=3D"_blank">roman@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"><div dir=3D"ltr"><br><d=
iv class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"m_31435758290=
03259321gmail_signature" data-smartmail=3D"gmail_signature"><br></div></div=
><div class=3D"gmail_quote"><span class=3D"">On Tue, Apr 3, 2018 at 1:26 PM=
, Eric Rescorla <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" targe=
t=3D"_blank">ekr@rtfm.com</a>&gt;</span> wrote:<br></span><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote"><div><div class=3D"m_3143575829003259321h5"><span class=
=3D"">On Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <span dir=3D"ltr">&lt;<a =
href=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@nostrum.com</a>&gt;=
</span> wrote:<br></span><div><div class=3D"h5"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div class=3D"m_3143575829003259321m_6587937063968571836HOEnZb"><div cl=
ass=3D"m_3143575829003259321m_6587937063968571836h5"><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">On 4/3/18 1:29 AM, Adam Roach wrote=
:<br>
<br>
&lt;snip/&gt;<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The second issue doesn&#39;t necessarily pertain to this document per se as=
 much<br>
as it does the interaction among this document, draft-ietf-ice-trickle (Tri=
ckle<br>
ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep<b=
r>
(JSEP). The problem doesn&#39;t lie with any single document, but in the ov=
erall<br>
result of how they&#39;re currently structured.<br>
<br>
JSEP (in the RFC editor queue) refers to the &quot;a=3Dend-of-candidates&qu=
ot; SDP attribute<br>
as appearing in Trickle ICE, section 9.3, which was true at one point in ti=
me.<br>
Somewhere along the line, this attribute&#39;s definition was moved from th=
ere<br>
into this document.<br>
<br>
There are several ways to fix this, each with their own drawbacks:<br>
<br>
1. Move the SDP syntax for &quot;a=3Dend-of-candidates&quot; back into the =
Trickle ICE<br>
=C2=A0 =C2=A0draft. Drawback: Trickle ICE does not currently define any nor=
mative SDP<br>
=C2=A0 =C2=A0behavior; and, in fact, could work in a system that doesn&#39;=
t use SDP at all.<br>
<br>
2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant from =
the<br>
=C2=A0 =C2=A0perspective that ICE SDP defines SDP syntax for ICE in general=
 (for both<br>
=C2=A0 =C2=A0SIP and JSEP), and such a move aggregates all of the SDP synta=
x into a<br>
=C2=A0 =C2=A0single document that is already necessary to reference from an=
y document<br>
=C2=A0 =C2=A0that uses SDP for Trickle ICE. Drawback: the document doesn&#3=
9;t presently<br>
=C2=A0 =C2=A0discuss Trickle ICE at all, and this would require a somewhat =
awkward<br>
=C2=A0 =C2=A0section that basically says &quot;If you use [Trickle ICE] wit=
h SDP, the syntax<br>
=C2=A0 =C2=A0for the end-of-candidate marker is...&quot;<br>
<br>
3. Change JSEP to normatively depend on this document for the<br>
=C2=A0 =C2=A0&quot;a=3Dend-of-candidates&quot; syntax. Drawback: This docum=
ent is extremely<br>
=C2=A0 =C2=A0SIP-specific, while JSEP is based solely on RFC 4566 syntax an=
d RFC 3264<br>
=C2=A0 =C2=A0behavior, independent of any SIP semantics.=C2=A0 Forcing JSEP=
 to normatively<br>
=C2=A0 =C2=A0depend on a SIP specific document for a simple attribute synta=
x definition<br>
=C2=A0 =C2=A0seems to be letting the tail wag the dog.<br>
<br>
I believe that #2 is the least inelegant option, but I&#39;m open to #1 and=
 #3.<br>
However, The *current* situation -- in which JSEP normatively points to a<b=
r>
document from which the text is cites has been removed out from under it --=
 is<br>
clearly wrong.<br>
</blockquote>
IMHO the ICE WG had consensus to remove all normative SDP references<br>
from draft-ietf-ice-trickle and place them in<br>
draft-ietf-mmusic-trickle-ice-<wbr>sip. Does it really matter what kind of<=
br>
document JSEP points to, as long as the &quot;a=3Dend-of-candidates&quot; d=
efinition<br>
can be found there?<br>
</blockquote>
I was working on a comment to the same effect when I saw Peter=E2=80=99s.<b=
r>
<br>
I see Adam=E2=80=99s option 1 as a non-starter since it explicitly reverses=
 that consensus. I see 2 and 3 to be equally awkward, in which case 3 requi=
res the least amount of structural change. If there was an option that requ=
ired no change to jsep at all(since it is currently with the RFC editor), b=
ut IIUC, none of the choices allow for that.<br></blockquote></div></div></=
blockquote><div><br></div></div></div></div></div><div><div class=3D"h5"><d=
iv>I don&#39;t think #3 is acceptable. AFAIK JSEP has no other dependencies=
 on SIP. If you think #2 and #3 are equally awkward, lets do #2.<br></div><=
div><br></div></div></div></div></div></div></blockquote><div><br></div>Do =
you want to move all other trickle ICE specific SDP related changes from =
=C2=A0draft-ietf-mmusic-trickle-<wbr>ice-sip to draft-ietf-mmusic-ice-sip-s=
dp?</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">It=
 is not just end-of-candidates, but also support for c=3D0.0.0.0 in offers,=
 SDP offers without the candidates, different mismatch rules. As it stands,=
=C2=A0

<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:s=
mall;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm=
al;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;t=
ext-transform:none;white-space:normal;word-spacing:0px;background-color:rgb=
(255,255,255);text-decoration-style:initial;text-decoration-color:initial;f=
loat:none;display:inline">draft-ietf-mmusic-trickle-ice-<wbr>sip</span>=C2=
=A0changes how=C2=A0<span style=3D"color:rgb(34,34,34);font-family:arial,sa=
ns-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;fo=
nt-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:sta=
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
background-color:rgb(255,255,255);text-decoration-style:initial;text-decora=
tion-color:initial;float:none;display:inline">draft-ietf-mmusic-ice-sip-<wb=
r>sdp</span>=C2=A0works when trickle ICE is used.</div></div></div></blockq=
uote><div><br></div><div>I want to do whatever is necessary to remove the n=
ormative dependency from JSEP to SIP</div><div><br></div><div>-Ekr</div><di=
v><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"g=
mail_extra"><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"=
>Regards,<br><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"m_3143575829003259321gmail_signature">_____________<span class=
=3D"HOEnZb"><font color=3D"#888888"><br>Roman Shpount</font></span></div></=
div><br class=3D"m_3143575829003259321gmail-Apple-interchange-newline">

=C2=A0</div></div></div></div>
</blockquote></div><br></div></div>

--0000000000005467310568f53f55--


From nobody Tue Apr  3 10:44:47 2018
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 6848412D7F8 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9flk7q28Q-6u for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 10:44:42 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::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 5F85812EAD4 for <mmusic@ietf.org>; Tue,  3 Apr 2018 10:44:39 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id i28-v6so20331199otf.8 for <mmusic@ietf.org>; Tue, 03 Apr 2018 10:44:39 -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=TUjegsqoiwL3SLwaBbImu0Oi+scGVMqqQEs2rJdTsW0=; b=EescMfCDFtKo7INuYz4kThZWiNlkpsgG1yWyu7bYc47vJmnCiadY4UaIN7vyHwtc3n NzyvCktJ9HiAeV8ynw7CoN3LYotumnMVXYu0BKbnJ05ImRR+Ho6EC3BwJAZoy1a7Eoqc 5OGMW6iFgVF25Dhh25rn+iaSLiesPaAgjLC5bmSlu+VZ2kHDjfGMTJagXyrb1MIFG06R Vf5F/isYQlJVV1sH1+VPLz87nIlTQn1TO1ehNWn4WlYh6qdk4UzHC/emLK4qDOeFbbKw rSNpZT09krJLijoLK8keha/713KuSEOP6F8M3wxjEoBuhg7Leqsled8tyeLw7eOjmPJy B5Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TUjegsqoiwL3SLwaBbImu0Oi+scGVMqqQEs2rJdTsW0=; b=d0Vwje6lLiaKY4spVVXP8UA8gnvNBap6qGsLfhQnOpRTXSvToOHLRlJud4U9LS8rYY jQBYVuzon9SbN//jvz0D08t5utI84BCBxiWe3AYBN+XzEtXPqzeohNbYW5ImDC73zEbo ua95FwrG1vpFHMH77ont/2MH+0JY4OxtVKAhm+i0s8IUXBINANwpD+Tx4Dn/JoFNiOVu 4tm3yjVoubVufkUyw9q9NrQNm2/r7axmzU6k1MHhaEKJ03HN96C4e1q+BAHWu2s/0t9S Nz4+cFqalbnZfvPJSFdrAHzCilld87HUhVs4QqHlOr6R/YQdZnIX/JOEcbab7Fabbc+s W+qA==
X-Gm-Message-State: ALQs6tC4xvmNqAv8mqKDQCyjC+cD4FhNZi42WVYXmXYB34T6wH03AIA3 9nJOOSvhqUQTv2huCVT8Pmkpk2/ZuNukIuNNAvMLEg==
X-Google-Smtp-Source: AIpwx486VRFRKB5/jYqC7qll4imVq7HhQTlnE/gquSaL6erpJArF2wfg5g9vLnhKhixWUN2QcdjCOjQfGM9MWLxMvsA=
X-Received: by 2002:a9d:2a09:: with SMTP id t9-v6mr347200ota.392.1522777478799;  Tue, 03 Apr 2018 10:44:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.130 with HTTP; Tue, 3 Apr 2018 10:43:58 -0700 (PDT)
In-Reply-To: <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 3 Apr 2018 10:43:58 -0700
Message-ID: <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org,  "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>,  The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@mozilla.com>,  draft-ietf-mmusic-trickle-ice-sip@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b2373e0568f54261"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kKbCRrpUs15PpN5tqMzSDJEnePg>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:44:46 -0000

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

On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com> wrote:

>
>
> > On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> >
> > I don't think #3 is acceptable. AFAIK JSEP has no other dependencies on
> SIP. If you think #2 and #3 are equally awkward, lets do #2.
> >
>
> I said they are equally awkward (by which I mean equally awkward for
> readers after publication), but 3 requires fewer changes (that is, less
> effort.).
>
> If we want to go for least awkward, that probably means a separate
> trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99=
s the past
> of most effort.
>
> But honestly, I think this is the sort of point that we should defer to W=
G
> consensus.
>

Which WG? As I understand it, this would require a change to JSEP, which
would also require WG consensus, plus a change to an IESG-approved document=
.

-Ekr


> Ben.
>

--000000000000b2373e0568f54261
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 Tue, Apr 3, 2018 at 10:35 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:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
&gt; On Apr 3, 2018, at 12:26 PM, Eric Rescorla &lt;<a href=3D"mailto:ekr@r=
tfm.com">ekr@rtfm.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I don&#39;t think #3 is acceptable. AFAIK JSEP has no other dependenci=
es on SIP. If you think #2 and #3 are equally awkward, lets do #2.<br>
&gt;<br>
<br>
</span>I said they are equally awkward (by which I mean equally awkward for=
 readers after publication), but 3 requires fewer changes (that is, less ef=
fort.).<br>
<br>
If we want to go for least awkward, that probably means a separate trickle-=
ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99s the past=
 of most effort.<br>
<br>
But honestly, I think this is the sort of point that we should defer to WG =
consensus.<br></blockquote><div><br></div><div>Which WG? As I understand it=
, this would require a change to JSEP, which would also require WG consensu=
s, plus a change to an IESG-approved document.</div><div><br></div><div>-Ek=
r</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Ben.<br>
</font></span></blockquote></div><br></div></div>

--000000000000b2373e0568f54261--


From nobody Tue Apr  3 10:48:40 2018
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 4B69812D7F8; Tue,  3 Apr 2018 10:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.629
X-Spam-Level: 
X-Spam-Status: No, score=-1.629 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yXcPuXF7gTa; Tue,  3 Apr 2018 10:48:31 -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 AC4D21243F6; Tue,  3 Apr 2018 10:48:31 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w33HmQar090499 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:48:27 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Roman Shpount <roman@telurix.com>, Eric Rescorla <ekr@rtfm.com>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <fce2e727-9fc4-a0c3-c28d-e5cca5d4bc90@nostrum.com>
Date: Tue, 3 Apr 2018 12:48:21 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------6539FF7135EF8D048AB08991"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-rS9YE6LiEqX76NLxQIvYNaXR70>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:48:33 -0000

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

On 4/3/18 12:38 PM, Roman Shpount wrote:
> Do you want to move all other trickle ICE specific SDP related changes 
> from  draft-ietf-mmusic-trickle-ice-sip to draft-ietf-mmusic-ice-sip-sdp?
>
> It is not just end-of-candidates, but also support for c=0.0.0.0 in 
> offers, SDP offers without the candidates, different mismatch rules. 
> As it stands, draft-ietf-mmusic-trickle-ice-sip changes how 
> draft-ietf-mmusic-ice-sip-sdp works when trickle ICE is used.

To be clear, the other changes you cite are specific to SIP, as 
evidenced by the fact that JSEP does not need to make use of them. I 
don't see a major problem with moving them (other than it being 
make-work), but I also don't see any value in doing so.

/a

--------------6539FF7135EF8D048AB08991
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 4/3/18 12:38 PM, Roman Shpount
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com">
      <div dir="ltr">Do you want to move all other trickle ICE specific
        SDP related changes from  draft-ietf-mmusic-trickle-ice-sip to
        draft-ietf-mmusic-ice-sip-sdp?
        <div class="gmail_extra">
          <div class="gmail_quote"><br>
          </div>
          <div class="gmail_quote">It is not just end-of-candidates, but
            also support for c=0.0.0.0 in offers, SDP offers without the
            candidates, different mismatch rules. As it stands, 
            <span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">draft-ietf-mmusic-trickle-ice-sip</span> changes
            how <span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">draft-ietf-mmusic-ice-sip-sdp</span> works
            when trickle ICE is used.</div>
        </div>
      </div>
    </blockquote>
    <br>
    To be clear, the other changes you cite are specific to SIP, as
    evidenced by the fact that JSEP does not need to make use of them. I
    don't see a major problem with moving them (other than it being
    make-work), but I also don't see any value in doing so.<br>
    <br>
    /a<br>
  </body>
</html>

--------------6539FF7135EF8D048AB08991--


From nobody Tue Apr  3 10:49:48 2018
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 0831412D778; Tue,  3 Apr 2018 10:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAfZgc1zd411; Tue,  3 Apr 2018 10:49:39 -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 1A4A61243F6; Tue,  3 Apr 2018 10:49:39 -0700 (PDT)
Received: from [10.0.1.91] (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 w33HnZ43090702 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:49:36 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <D8A836A6-B042-4F28-953D-C1F430E8787A@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4D4B2462-31B0-44E2-8B9D-2C50238E69A7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 12:49:34 -0500
In-Reply-To: <CABcZeBMwmisiM0Vpc9Pr53wOPi=J6RAKiNiO8JEkPOtcTjOZvA@mail.gmail.com>
Cc: Roman Shpount <roman@telurix.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
To: Eric Rescorla <ekr@rtfm.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com> <CABcZeBMwmisiM0Vpc9Pr53wOPi=J6RAKiNiO8JEkPOtcTjOZvA@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3FZtteoRlVT4GJqbfAVQ3yyQHnM>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:49:41 -0000

--Apple-Mail=_4D4B2462-31B0-44E2-8B9D-2C50238E69A7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
>=20
> On Tue, Apr 3, 2018 at 10:38 AM, Roman Shpount <roman@telurix.com> =
wrote:
>=20
>=20
>=20
> On Tue, Apr 3, 2018 at 1:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
> On Tue, Apr 3, 2018 at 10:24 AM, Adam Roach <adam@nostrum.com> wrote:
> On 4/3/18 1:29 AM, Adam Roach wrote:
>=20
> <snip/>
>=20
> The second issue doesn't necessarily pertain to this document per se =
as much
> as it does the interaction among this document, draft-ietf-ice-trickle =
(Trickle
> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and =
draft-ietf-rtcweb-jsep
> (JSEP). The problem doesn't lie with any single document, but in the =
overall
> result of how they're currently structured.
>=20
> JSEP (in the RFC editor queue) refers to the "a=3Dend-of-candidates" =
SDP attribute
> as appearing in Trickle ICE, section 9.3, which was true at one point =
in time.
> Somewhere along the line, this attribute's definition was moved from =
there
> into this document.
>=20
> There are several ways to fix this, each with their own drawbacks:
>=20
> 1. Move the SDP syntax for "a=3Dend-of-candidates" back into the =
Trickle ICE
>    draft. Drawback: Trickle ICE does not currently define any =
normative SDP
>    behavior; and, in fact, could work in a system that doesn't use SDP =
at all.
>=20
> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant =
from the
>    perspective that ICE SDP defines SDP syntax for ICE in general (for =
both
>    SIP and JSEP), and such a move aggregates all of the SDP syntax =
into a
>    single document that is already necessary to reference from any =
document
>    that uses SDP for Trickle ICE. Drawback: the document doesn't =
presently
>    discuss Trickle ICE at all, and this would require a somewhat =
awkward
>    section that basically says "If you use [Trickle ICE] with SDP, the =
syntax
>    for the end-of-candidate marker is..."
>=20
> 3. Change JSEP to normatively depend on this document for the
>    "a=3Dend-of-candidates" syntax. Drawback: This document is =
extremely
>    SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC =
3264
>    behavior, independent of any SIP semantics.  Forcing JSEP to =
normatively
>    depend on a SIP specific document for a simple attribute syntax =
definition
>    seems to be letting the tail wag the dog.
>=20
> I believe that #2 is the least inelegant option, but I'm open to #1 =
and #3.
> However, The *current* situation -- in which JSEP normatively points =
to a
> document from which the text is cites has been removed out from under =
it -- is
> clearly wrong.
> IMHO the ICE WG had consensus to remove all normative SDP references
> from draft-ietf-ice-trickle and place them in
> draft-ietf-mmusic-trickle-ice-sip. Does it really matter what kind of
> document JSEP points to, as long as the "a=3Dend-of-candidates" =
definition
> can be found there?
> I was working on a comment to the same effect when I saw Peter=E2=80=99s=
.
>=20
> I see Adam=E2=80=99s option 1 as a non-starter since it explicitly =
reverses that consensus. I see 2 and 3 to be equally awkward, in which =
case 3 requires the least amount of structural change. If there was an =
option that required no change to jsep at all(since it is currently with =
the RFC editor), but IIUC, none of the choices allow for that.
>=20
> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies =
on SIP. If you think #2 and #3 are equally awkward, lets do #2.
>=20
>=20
> Do you want to move all other trickle ICE specific SDP related changes =
from  draft-ietf-mmusic-trickle-ice-sip to =
draft-ietf-mmusic-ice-sip-sdp?
>=20
> It is not just end-of-candidates, but also support for c=3D0.0.0.0 in =
offers, SDP offers without the candidates, different mismatch rules. As =
it stands,  draft-ietf-mmusic-trickle-ice-sip changes how =
draft-ietf-mmusic-ice-sip-sdp works when trickle ICE is used.
>=20
> I want to do whatever is necessary to remove the normative dependency =
from JSEP to SIP

We do references to =E2=80=9Csection XXX of RFC YYYY=E2=80=9D all the =
time to refer to specific points in an RFC of larger scope. I agree =
it=E2=80=99s not ideal, but =E2=80=9Cnot done=E2=80=9D is also not =
ideal.

Ben.




--Apple-Mail=_4D4B2462-31B0-44E2-8B9D-2C50238E69A7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrDvq4ACgkQgFZKbJXz
1A32oQ/9ELqhvYrRgIsPJYvpWe1hEOygoyRTHuQDYlZYkwJtqbdf6kit1bb1dwyI
TmWP0LwPhJrbdYjhKhGFv9hfml6JoAYPmy6uvmqTjGy0aZSD0va1LEa6dfo25Bd7
+0shDQ93gki+aRK1AaH+xxrMGMUBAYGHFfuGZ669AkBZpCnVBb31/JBsEzOguNGE
Gn4w/OxmoiDsL+rjHM3YNBdNg4ZGOVhOYOn2eOaH45BeRgRvDnzcewxFAom/496F
o/vVNgzzYQk6ig4RG/5wamHftc2+7hVQEIEBmJQi5uLMmIyRwy//+TWRFideYfVB
F2hpncRXCKPkcMcv/QGoOUcM3Nkf07bXkqYS+/+do0ObyZ95bRCJDSRo17DfFblW
N6bIW7/G9AAHLWpWt9m7C3/3BDH4YC8oCP+qJd7spff9Pf8TX99dw4+b7wbIfr+A
mEcfGbARV9bO/ek2wCXLuR6auoO4Zj0cS5bwr0OAtKgl1Gy+705E2AepHHKUC7N3
mkj3hXcUwSj6k/t4p87P5QqcJiDUuEjeKPUc04lTmKP1ZsmTPxy1qiasYOBrhozJ
SFJzfdHNesaMY718yboELjekW5E8r9X0PQmd5NxVKfKS0LfSUF0XrQ60ghbIl5jY
NYwwXT3CGg3ey3gdM3LdmQPUUZO2xwJ4jI92MbtwwuGPM1DingU=
=Vjx/
-----END PGP SIGNATURE-----

--Apple-Mail=_4D4B2462-31B0-44E2-8B9D-2C50238E69A7--


From nobody Tue Apr  3 10:54:33 2018
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 CD566126D85; Tue,  3 Apr 2018 10:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4yZue13ztZg; Tue,  3 Apr 2018 10:54: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 D9EA5126C83; Tue,  3 Apr 2018 10:54:24 -0700 (PDT)
Received: from [10.0.1.91] (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 w33HsKvk091488 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 12:54:21 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_356BC256-487E-4960-9F0C-D1C83B302531"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 12:54:19 -0500
In-Reply-To: <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com>
Cc: Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@mozilla.com>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
To: Eric Rescorla <ekr@rtfm.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/yNxnZJaxjSC2DerSPOVj1naRrRE>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 17:54:27 -0000

--Apple-Mail=_356BC256-487E-4960-9F0C-D1C83B302531
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
>=20
> On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com> wrote:
>=20
>=20
> > On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> >
> > I don't think #3 is acceptable. AFAIK JSEP has no other dependencies =
on SIP. If you think #2 and #3 are equally awkward, lets do #2.
> >
>=20
> I said they are equally awkward (by which I mean equally awkward for =
readers after publication), but 3 requires fewer changes (that is, less =
effort.).
>=20
> If we want to go for least awkward, that probably means a separate =
trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99s=
 the past of most effort.
>=20
> But honestly, I think this is the sort of point that we should defer =
to WG consensus.
>=20
> Which WG? As I understand it, this would require a change to JSEP, =
which would also require WG consensus, plus a change to an IESG-approved =
document.


I mean consensus of the WGs producing the documents. it=E2=80=99s quite =
reasonable for a dependent WG to offer feedback, but I don=E2=80=99t =
think a dependent WG gets to just override that consensus.

Ben.

--Apple-Mail=_356BC256-487E-4960-9F0C-D1C83B302531
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrDv8sACgkQgFZKbJXz
1A0w/g/9Hwquq5N2mTLwnJjZi9HJvFeTAao2SfZmb3qGmvRb364h5tA7IxAS46ZU
KKxUvPwMNY27rhromHvbkFLYpZS6xdet+hBxMDwhbcA7kK/FO1Hhf28emdCtXsob
wCDUUwGmAeViVFztZhYy4kHiQIRw84oLP/bLXF1knEVVnHL3WHlxtW/WVcLMBszW
yeA6SEafDQvu7pptq3ilEeAw4ytsp+TmwmsQfDz5kGZzxCPnS9I6uqmRI31uZUjz
hT2d3rgVseiSO3Dh6ECSh+XNdDErA3kDai2iuwGHa9+HwllDZJLmSlK15Km32zz+
VOSvyp8Js05mND6VWRJFGAkTmAVhF3kz93ejBSRwP6a5t6s9o9szX+5VRNjRD0ce
XjGp7d5l/jh2wmWtovjp7JR+u43ttFhtmMJ72KS72BsxCgkyI3JkOATGi4QroyiV
QSEnXy/I0ULol1hDG5Cs5qZq9qJTEfwvOh04tOyANDW5cSDH6+9gK2iKhsvY9R8q
tcm8vITjnTfVaRelaWORkUjxu1bUpUFYYotB3cAohFGIg1wcvVKH1HbXtuoHVG86
vXfXzDg4m3ghGISG77q9d48gzpjIVL3cAaYLVIIbGcKk/dXOuSxD+B4/eYORY/OJ
e2gDmI8ywnqkPeC21odNOZlHT7y0O3F4klLv5cXTRwdu1YejmzE=
=i+EF
-----END PGP SIGNATURE-----

--Apple-Mail=_356BC256-487E-4960-9F0C-D1C83B302531--


From nobody Tue Apr  3 11:01:38 2018
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 319F112EA64 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 11:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vCSzFOd9h9aX for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 11:01:01 -0700 (PDT)
Received: from mail-pl0-x231.google.com (mail-pl0-x231.google.com [IPv6:2607:f8b0:400e:c01::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 25E4612EAED for <mmusic@ietf.org>; Tue,  3 Apr 2018 11:00:37 -0700 (PDT)
Received: by mail-pl0-x231.google.com with SMTP id s10-v6so7931870plp.0 for <mmusic@ietf.org>; Tue, 03 Apr 2018 11:00:37 -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=i6LuCc25YMYr+Q2zGRJr1vtPUSAl8OoFlkMt1XF4bzg=; b=GIm4wPBheeBE6SlPNCd6sKIwKo7tRZLTl2qKY6/ByymFbmtZS8vvMmI8A/+5ZGPAky 67Qxe+FQVlOvAiBxnGV3Exfu8qHgvbumlQCPg5LEcd5zAr3nZxWVdVQojWYd9fVWmFX9 /+SUxwDknVA0My+E9FeXRluyyz1xxJsAU6opo7EduA2SKzV3L6AvNm83L5vZW+assOKc U334mLDj/GA9eI4ZK8VluBBLD6uKfnQF/2+FZpWrcVV+GvEAe6m3v1C6VsTYXxZo/cqk aWuut9J5Om8fWrpzhIpZ5xaDZ4tv8Rt0DCElJtSoDjBicTUOIh/+ARSGKOinoJ2+s3Vu nSEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=i6LuCc25YMYr+Q2zGRJr1vtPUSAl8OoFlkMt1XF4bzg=; b=O9xhg3j0WS90LbRaEI6onvTEZwDi/NjfxNtnCr9DjpbTi7gAvQRRqIn+MdUbyicsa8 3G7FI6MmGNvJ+qbH0yaqPc0PdICTveRiiylyDNvtZKMgXhlpmc3zJqvtVQnjja2diLzC ZRY4xUK1dpD2i1A5Nbz9ezNbrF26ziYUXXF+t7ghTcWBTgWRg2w/jbvQG8agxLEZ2d23 LLvStjlVqpAI7FKoZezRN5D2847GH1vz/zaD3h50srtXH/8MV9EecyPFxY8R3QY5PUNA wDGV7Q7vIvYcOhJb9UnH7vg8XK2cNI4HF2MB60n1fuT3Z65NQUtHGCsWw7t9Vk4KsPW3 5Arw==
X-Gm-Message-State: AElRT7FwHag3Dfpsw5IN823Hd6X5ceI7Xx1D0a8wL7X1v8UmdAmsh9CJ kzX5JwszlPmrg51yUhbfX4fLdZxW
X-Google-Smtp-Source: AIpwx4+zMAosxmlEf8IfhtdIj0DsuFrXZrKODEAVNXwKiSt0WBcAMeDYLPkTi7ITWQHWZ43Jl63qjw==
X-Received: by 10.98.80.145 with SMTP id g17mr11361581pfj.71.1522778436576; Tue, 03 Apr 2018 11:00:36 -0700 (PDT)
Received: from mail-pl0-f54.google.com (mail-pl0-f54.google.com. [209.85.160.54]) by smtp.gmail.com with ESMTPSA id 86sm7805956pfh.93.2018.04.03.11.00.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 11:00:36 -0700 (PDT)
Received: by mail-pl0-f54.google.com with SMTP id g20-v6so9890785plo.9; Tue, 03 Apr 2018 11:00:35 -0700 (PDT)
X-Received: by 2002:a17:902:8548:: with SMTP id d8-v6mr15506600plo.241.1522778435567;  Tue, 03 Apr 2018 11:00:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.185.79 with HTTP; Tue, 3 Apr 2018 11:00:34 -0700 (PDT)
In-Reply-To: <fce2e727-9fc4-a0c3-c28d-e5cca5d4bc90@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com> <fce2e727-9fc4-a0c3-c28d-e5cca5d4bc90@nostrum.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 3 Apr 2018 14:00:34 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtL6DqBZEvvV7RnurtnDVhp5zTtGEMZ=MwfUZVm6XvmdA@mail.gmail.com>
Message-ID: <CAD5OKxtL6DqBZEvvV7RnurtnDVhp5zTtGEMZ=MwfUZVm6XvmdA@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Eric Rescorla <ekr@rtfm.com>, Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>,  mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>,  Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>,  The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b948dd0568f57b39"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QGhqfwBDQJIClDt6CjcgOfVVvMc>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:01:12 -0000

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

On Tue, Apr 3, 2018 at 1:48 PM, Adam Roach <adam@nostrum.com> wrote:

> On 4/3/18 12:38 PM, Roman Shpount wrote:
>
> Do you want to move all other trickle ICE specific SDP related changes
> from  draft-ietf-mmusic-trickle-ice-sip to draft-ietf-mmusic-ice-sip-sdp?
>
> It is not just end-of-candidates, but also support for c=0.0.0.0 in
> offers, SDP offers without the candidates, different mismatch rules. As it
> stands,  draft-ietf-mmusic-trickle-ice-sip changes how
> draft-ietf-mmusic-ice-sip-sdp works when trickle ICE is used.
>
>
> To be clear, the other changes you cite are specific to SIP, as evidenced
> by the fact that JSEP does not need to make use of them. I don't see a
> major problem with moving them (other than it being make-work), but I also
> don't see any value in doing so.
>

All the things I have referenced are being used by JSEP.

For instance current in draft-ietf-rtcweb-jsep-24 (
https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24#section-5.2.1):

If the m= section is marked as bundle-only, then the port value MUST be set
to 0.  Otherwise, the port value is set to the port of the default ICE
candidate for this m= section, but given that no candidates are available
yet, the "dummy" port value of 9 (Discard) MUST be used, as indicated in
[I-D.ietf-ice-trickle], Section 5.1.

I am fairly sure this is no longer in ietf-ice-trickle  and was moved to
draft-ietf-mmusic-trickle-ice-sip (
https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-14#section-4.1.1
).

Regards,
_____________
Roman Shpount

--000000000000b948dd0568f57b39
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 Tue, Apr 3, 2018 at 1:48 PM, Adam Roach <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@nostrum.com</a>&gt;</=
span> wrote:<br></div></div><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF"><span class=3D"gmail-">
    <div class=3D"gmail-m_-8910676831484441992moz-cite-prefix">On 4/3/18 12=
:38 PM, Roman Shpount
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Do you want to move all other trickle ICE specific
        SDP related changes from =C2=A0draft-ietf-mmusic-trickle-<wbr>ice-s=
ip to
        draft-ietf-mmusic-ice-sip-sdp?
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote"><br>
          </div>
          <div class=3D"gmail_quote">It is not just end-of-candidates, but
            also support for c=3D0.0.0.0 in offers, SDP offers without the
            candidates, different mismatch rules. As it stands,=C2=A0
            <span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif=
;font-size:small;font-style:normal;font-variant-ligatures:normal;font-varia=
nt-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-=
indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgrou=
nd-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-col=
or:initial;float:none;display:inline">draft-ietf-mmusic-trickle-ice-<wbr>si=
p</span>=C2=A0changes
            how=C2=A0<span style=3D"color:rgb(34,34,34);font-family:arial,s=
ans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;f=
ont-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:st=
art;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px=
;background-color:rgb(255,255,255);text-decoration-style:initial;text-decor=
ation-color:initial;float:none;display:inline">draft-ietf-mmusic-ice-sip-<w=
br>sdp</span>=C2=A0works
            when trickle ICE is used.</div>
        </div>
      </div>
    </blockquote>
    <br></span>
    To be clear, the other changes you cite are specific to SIP, as
    evidenced by the fact that JSEP does not need to make use of them. I
    don&#39;t see a major problem with moving them (other than it being
    make-work), but I also don&#39;t see any value in doing so.</div></bloc=
kquote><div><br></div><div>All the things I have referenced are being used =
by JSEP.</div><div><br></div><div>For instance current in draft-ietf-rtcweb=
-jsep-24 (<a href=3D"https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24#=
section-5.2.1">https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24#sectio=
n-5.2.1</a>):</div><div><br></div></div></div><blockquote style=3D"margin:0=
px 0px 0px 40px;border:none;padding:0px"><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote"><div>

If the m=3D section is marked as bundle-only, then the port value MUST be s=
et to 0.=C2=A0 Otherwise, the port value is set to the port of the default =
ICE candidate for this m=3D section, but given that no candidates are avail=
able yet, the &quot;dummy&quot; port value of 9 (Discard) MUST be used, as =
indicated in [I-D.ietf-ice-trickle], Section 5.1.

=C2=A0</div><div><br></div></div></div></blockquote>I am fairly sure this i=
s no longer in=20

<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:s=
mall;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norm=
al;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;t=
ext-transform:none;white-space:normal;word-spacing:0px;background-color:rgb=
(255,255,255);text-decoration-style:initial;text-decoration-color:initial;f=
loat:none;display:inline">ietf-ice-trickle</span>=C2=A0 and was moved to dr=
aft-ietf-mmusic-trickle-ice-sip (<a href=3D"https://tools.ietf.org/html/dra=
ft-ietf-mmusic-trickle-ice-sip-14#section-4.1.1">https://tools.ietf.org/htm=
l/draft-ietf-mmusic-trickle-ice-sip-14#section-4.1.1</a>).<div><br></div><d=
iv><div>Regards,</div><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br=
 class=3D"gmail-Apple-interchange-newline">

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

--000000000000b948dd0568f57b39--


From nobody Tue Apr  3 11:04:27 2018
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 79E4612D7F9; Tue,  3 Apr 2018 11:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CyqCrLtLjaDo; Tue,  3 Apr 2018 11:04:19 -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 35A2812EA42; Tue,  3 Apr 2018 11:03:38 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w33I3XsT093111 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 13:03:34 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
Cc: mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@mozilla.com>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com>
Date: Tue, 3 Apr 2018 13:03:28 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/r8Pw255vL6ePbiklh1DuBPxrAP4>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:04:21 -0000

On 4/3/18 12:54 PM, Ben Campbell wrote:
>
>> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>
>>
>> On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com> wrote:
>>
>>
>>> On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>>>
>>> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies on SIP. If you think #2 and #3 are equally awkward, lets do #2.
>>>
>> I said they are equally awkward (by which I mean equally awkward for readers after publication), but 3 requires fewer changes (that is, less effort.).
>>
>> If we want to go for least awkward, that probably means a separate trickle-ice-sdp draft in parallel to the ice sdp draft. But that’s the past of most effort.
>>
>> But honestly, I think this is the sort of point that we should defer to WG consensus.
>>
>> Which WG? As I understand it, this would require a change to JSEP, which would also require WG consensus, plus a change to an IESG-approved document.
>
> I mean consensus of the WGs producing the documents. it’s quite reasonable for a dependent WG to offer feedback, but I don’t think a dependent WG gets to just override that consensus.

I don't think it's as clean cut as that. JSEP could have defined the 
"a=end-of-candidates" syntax, and certainly would have if MMUSIC and ICE 
had pulled it out of their documents. But I don't think we want both 
documents independently registering identical syntaxes with identical 
meanings, right? Or I suppose JSEP could have decided -- having finished 
first -- that they should define the syntax and have the trickle-ice-sip 
document reference JSEP?

I'm offering those up as examples, not proposals. I think the first is a 
nonstarter, and the second is... well, it's as awkward as what you're 
proposing.

I'm beginning to think we need to to take the question to ART rather 
than the three working groups.

/a


From nobody Tue Apr  3 11:22:16 2018
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 BF46012E8A4; Tue,  3 Apr 2018 11:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01xH36K864T8; Tue,  3 Apr 2018 11:22:11 -0700 (PDT)
Received: from mail-ua0-x22c.google.com (mail-ua0-x22c.google.com [IPv6:2607:f8b0:400c:c08::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 29ECB12D80E; Tue,  3 Apr 2018 11:22:11 -0700 (PDT)
Received: by mail-ua0-x22c.google.com with SMTP id l21so11627968uak.1; Tue, 03 Apr 2018 11:22:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Jk7EvySYIjrC1R635lzoIDDuJcckB/u7zCl84MxPMic=; b=RH5wwDnBXZg+PXJexS9ZDuzHybId2y0guLUXGW9xVbQTWj52+2jJB7j9AGhLXARVXk yH0f23x+eV9cZlGuulxEjWT+NrFes20dC0bzo/HPv40FmLncT6GDPcT/74HsQbE7wRGE dPc3B1iVUiAj/QeoGuc3rNkmVNiP1NU+AKtlZ8QYAB9LEE0diNOTZ2nAeOOLC6LTQGv1 kKeQsgLDUr7Qr/KBc6Pk4mqpPx4IjE2tPTBhmiipe7i1DB1RiyFd/8NIYd6V5lEzW1/b v5Vt4FmBddXSNWVFrvnd4r6kedE6wCkpMR0Jm+qQ2kj1GgwVK8hAsx/nxaYt0mX52/uk f2Vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Jk7EvySYIjrC1R635lzoIDDuJcckB/u7zCl84MxPMic=; b=HxXKAZcPNppqQYmyUc/76e3MQq3GOY2n0T3VXQqUVcTGkZrzyPpmupu4Dbf9yuoAUN fph+c3068/69gFOQoQGWDwokI+i5lkOvhpldp52mmKPm3tRm79lG7qf2MnB1selODYKE RtlLu6rGOPGk4KpBPk2JzRFH0QONRgGoxV11iu+PHx7wLCX0b6DRHSLPZq/px1IXJhL9 Vl7uBo4mrhPdDaf/fxxlmHbKPNGIV2wR/2O77yDg2XGe1VCiri+PJFRMxRwwgJOSLpfB kgshensN4o/hlwAhvMKii/kweNX/9p/6UVqSspQMZ4FHzwJl4cQr4cPy9KYEBXNxP9Ro 240w==
X-Gm-Message-State: ALQs6tAdLwrLMtMMChTOzXRVPOlcPMKyNPR3+dmVDp5w2i6fD9axw7ry eTgujyCMZJWZrtlUW2EccjTeqfkNaFUKMFSjvpI=
X-Google-Smtp-Source: AIpwx49LVGOYABrhIKSHIbUgv+7WT4uTh5z1B88dNHPoIEk3IxRukhqacXCMUhuRIr+YJKJmYW2lP//irgdHepKUl+A=
X-Received: by 10.159.55.104 with SMTP id a37mr9002406uae.11.1522779730112; Tue, 03 Apr 2018 11:22:10 -0700 (PDT)
MIME-Version: 1.0
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com>
In-Reply-To: <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 03 Apr 2018 18:21:59 +0000
Message-ID: <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>,  Flemming Andreasen <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  draft-ietf-mmusic-trickle-ice-sip@ietf.org, "ice@ietf.org" <ice@ietf.org>,  mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org,  "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a114067bee275610568f5c854"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MsqTszbXql7UUKLLbyueqc0pqh0>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:22:15 -0000

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

Adding a data point

Icebis doesn=E2=80=99t talk about trickle ice and hence ice-sip-SDP doesn=
=E2=80=99t either.

In the same context, would ice trickle and ice-trickle-sip-SDP focussing on
trickle ice only procedures and usages makes sense ?


Does that work ?


On Tue, Apr 3, 2018 at 11:04 AM Adam Roach <adam@nostrum.com> wrote:

> On 4/3/18 12:54 PM, Ben Campbell wrote:
> >
> >> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> >>
> >>
> >>
> >> On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com> wrote:
> >>
> >>
> >>> On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
> >>>
> >>> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies
> on SIP. If you think #2 and #3 are equally awkward, lets do #2.
> >>>
> >> I said they are equally awkward (by which I mean equally awkward for
> readers after publication), but 3 requires fewer changes (that is, less
> effort.).
> >>
> >> If we want to go for least awkward, that probably means a separate
> trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99=
s the past
> of most effort.
> >>
> >> But honestly, I think this is the sort of point that we should defer t=
o
> WG consensus.
> >>
> >> Which WG? As I understand it, this would require a change to JSEP,
> which would also require WG consensus, plus a change to an IESG-approved
> document.
> >
> > I mean consensus of the WGs producing the documents. it=E2=80=99s quite
> reasonable for a dependent WG to offer feedback, but I don=E2=80=99t thin=
k a
> dependent WG gets to just override that consensus.
>
> I don't think it's as clean cut as that. JSEP could have defined the
> "a=3Dend-of-candidates" syntax, and certainly would have if MMUSIC and IC=
E
> had pulled it out of their documents. But I don't think we want both
> documents independently registering identical syntaxes with identical
> meanings, right? Or I suppose JSEP could have decided -- having finished
> first -- that they should define the syntax and have the trickle-ice-sip
> document reference JSEP?
>
> I'm offering those up as examples, not proposals. I think the first is a
> nonstarter, and the second is... well, it's as awkward as what you're
> proposing.
>
> I'm beginning to think we need to to take the question to ART rather
> than the three working groups.
>
> /a
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div><div dir=3D"auto">Adding a data point=C2=A0</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">Icebis doesn=E2=80=99t talk about trickle ice and =
hence ice-sip-SDP doesn=E2=80=99t either.</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">In the same context, would ice trickle and ice-trickle-si=
p-SDP focussing on trickle ice only procedures and usages makes sense ?</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Does that work ?=C2=A0</div><div dir=3D"auto"><br></div><br><div class=3D"=
gmail_quote"><div>On Tue, Apr 3, 2018 at 11:04 AM Adam Roach &lt;<a href=3D=
"mailto:adam@nostrum.com">adam@nostrum.com</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">On 4/3/18 12:54 PM, Ben Campbell wrote:<br>
&gt;<br>
&gt;&gt; On Apr 3, 2018, at 12:43 PM, Eric Rescorla &lt;<a href=3D"mailto:e=
kr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell &lt;<a href=3D"mailt=
o:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Apr 3, 2018, at 12:26 PM, Eric Rescorla &lt;<a href=3D"mail=
to:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don&#39;t think #3 is acceptable. AFAIK JSEP has no other de=
pendencies on SIP. If you think #2 and #3 are equally awkward, lets do #2.<=
br>
&gt;&gt;&gt;<br>
&gt;&gt; I said they are equally awkward (by which I mean equally awkward f=
or readers after publication), but 3 requires fewer changes (that is, less =
effort.).<br>
&gt;&gt;<br>
&gt;&gt; If we want to go for least awkward, that probably means a separate=
 trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99s=
 the past of most effort.<br>
&gt;&gt;<br>
&gt;&gt; But honestly, I think this is the sort of point that we should def=
er to WG consensus.<br>
&gt;&gt;<br>
&gt;&gt; Which WG? As I understand it, this would require a change to JSEP,=
 which would also require WG consensus, plus a change to an IESG-approved d=
ocument.<br>
&gt;<br>
&gt; I mean consensus of the WGs producing the documents. it=E2=80=99s quit=
e reasonable for a dependent WG to offer feedback, but I don=E2=80=99t thin=
k a dependent WG gets to just override that consensus.<br>
<br>
I don&#39;t think it&#39;s as clean cut as that. JSEP could have defined th=
e<br>
&quot;a=3Dend-of-candidates&quot; syntax, and certainly would have if MMUSI=
C and ICE<br>
had pulled it out of their documents. But I don&#39;t think we want both<br=
>
documents independently registering identical syntaxes with identical<br>
meanings, right? Or I suppose JSEP could have decided -- having finished<br=
>
first -- that they should define the syntax and have the trickle-ice-sip<br=
>
document reference JSEP?<br>
<br>
I&#39;m offering those up as examples, not proposals. I think the first is =
a<br>
nonstarter, and the second is... well, it&#39;s as awkward as what you&#39;=
re<br>
proposing.<br>
<br>
I&#39;m beginning to think we need to to take the question to ART rather<br=
>
than the three working groups.<br>
<br>
/a<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div>

--001a114067bee275610568f5c854--


From nobody Tue Apr  3 11:28:21 2018
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 1071612D7F7; Tue,  3 Apr 2018 11:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvAiV84Dx8hM; Tue,  3 Apr 2018 11:28:10 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c: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 405E7124BE8; Tue,  3 Apr 2018 11:28:10 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id n64so7626343vkf.12; Tue, 03 Apr 2018 11:28:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mysX+mSoNWlATAiKXpXaPKWd5hqPtiQnD7wj1XB4yo4=; b=an2bBKk0BRZFAy2/roizruZOrQjOCgyQjdZe+BDPSVJ4bg7g/K9zv7AFtdYm1xg7yZ XcLfLzCOg5wnt7ycFNyGPMfUv/R+/90x4z4V25x698LJujOf1xXHIFSgWi9xYAp7BX/Y bQW3CoG3JZGp7jn8bhOXmq+u52tAai2z3CGd2JSjc9iPzexQrw0llTOJrFpRcY+yMIh7 AyNVKzicGOXlu+u1ujx1+Hf9Ra9L5VpQgKev1yxE5CfYKiwIj5EefUOmvR+TGJlsmmY3 XDfKLwFORcVK4Y3HQruXGnL+d6AJYVMMmV0yxWMQ9yEeN13wiHfQ3Qi4nb4RHzqCyNZc WZhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mysX+mSoNWlATAiKXpXaPKWd5hqPtiQnD7wj1XB4yo4=; b=LjWLMJ6QFqtMWoY8t+aungW56Qe01I/GJ9ojO5GDp7LYFG8xgjjZjsFgSxcI4hnAN6 PUsqeCzhz/2Crj8sLR4K+FQdbslIuadZG/3btb5JE79Q6BIir2CXS2eKbrfKJ/Ho5aLE dZzgybVAPI7kXr2Ec7f5ItBmBMlZNXmEk1neBS0TxejUTWBXhvZh73I5WYqrUchgDzzP 7zD1gVNhVsRZqZlf18hpp6I6CDoYqJOZd+jLN258MbbAgsPstEWsY2S129esQ/I3o7Mr zw3zrzwHCCk0CSQpzfScZLStoFAdi1vKj7w/dkJK0+ExWD6lx/58QH6kCb0imzQEFGcu NY4A==
X-Gm-Message-State: ALQs6tDxz95Oi6V9DGRUIxJIly6IDFZYn+C3S3bap7JLociyRcbR06fp xFZVw06ryz/KXBFRxnspV8Jt5tTdGHBl3pTb/P0=
X-Google-Smtp-Source: AIpwx49u6PwQ36oLkpL2BOo+NXAZBUoNiSBFCaTpNPMhY6fLL3HBeoXNBdXH/dlAPXqiFfMw6ATPlyrWuaHLPIrcz4U=
X-Received: by 10.31.174.80 with SMTP id x77mr8595019vke.101.1522780089273; Tue, 03 Apr 2018 11:28:09 -0700 (PDT)
MIME-Version: 1.0
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com>
In-Reply-To: <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 03 Apr 2018 18:27:58 +0000
Message-ID: <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>,  Flemming Andreasen <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  draft-ietf-mmusic-trickle-ice-sip@ietf.org, "ice@ietf.org" <ice@ietf.org>,  mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org,  "rtcweb@ietf.org" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143fa3a4ad2460568f5de4e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HsR5bPpPdWtl-hjm8iSZNvcoc_A>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:28:13 -0000

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

Just to complete, ice-bis doesn=E2=80=99t normatively reference ice-sip-SDP=
 draft
when it moved to using =E2=80=9Cusages =E2=80=9C indirections for signaling=
 protocols.


Trickle ice can use similar approach and refer to trickle-sip as usage for
trickle.

Thanks
Suhas

On Tue, Apr 3, 2018 at 11:21 AM Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Adding a data point
>
> Icebis doesn=E2=80=99t talk about trickle ice and hence ice-sip-SDP doesn=
=E2=80=99t either.
>
> In the same context, would ice trickle and ice-trickle-sip-SDP focussing
> on trickle ice only procedures and usages makes sense ?
>
>
> Does that work ?
>
>
> On Tue, Apr 3, 2018 at 11:04 AM Adam Roach <adam@nostrum.com> wrote:
>
>> On 4/3/18 12:54 PM, Ben Campbell wrote:
>> >
>> >> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>> >>
>> >>
>> >>
>> >> On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com> wrote=
:
>> >>
>> >>
>> >>> On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>> >>>
>> >>> I don't think #3 is acceptable. AFAIK JSEP has no other dependencies
>> on SIP. If you think #2 and #3 are equally awkward, lets do #2.
>> >>>
>> >> I said they are equally awkward (by which I mean equally awkward for
>> readers after publication), but 3 requires fewer changes (that is, less
>> effort.).
>> >>
>> >> If we want to go for least awkward, that probably means a separate
>> trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=
=99s the past
>> of most effort.
>> >>
>> >> But honestly, I think this is the sort of point that we should defer
>> to WG consensus.
>> >>
>> >> Which WG? As I understand it, this would require a change to JSEP,
>> which would also require WG consensus, plus a change to an IESG-approved
>> document.
>> >
>> > I mean consensus of the WGs producing the documents. it=E2=80=99s quit=
e
>> reasonable for a dependent WG to offer feedback, but I don=E2=80=99t thi=
nk a
>> dependent WG gets to just override that consensus.
>>
>> I don't think it's as clean cut as that. JSEP could have defined the
>> "a=3Dend-of-candidates" syntax, and certainly would have if MMUSIC and I=
CE
>> had pulled it out of their documents. But I don't think we want both
>> documents independently registering identical syntaxes with identical
>> meanings, right? Or I suppose JSEP could have decided -- having finished
>> first -- that they should define the syntax and have the trickle-ice-sip
>> document reference JSEP?
>>
>> I'm offering those up as examples, not proposals. I think the first is a
>> nonstarter, and the second is... well, it's as awkward as what you're
>> proposing.
>>
>> I'm beginning to think we need to to take the question to ART rather
>> than the three working groups.
>>
>> /a
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>

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

<div><div dir=3D"auto">Just to complete, ice-bis doesn=E2=80=99t normativel=
y reference ice-sip-SDP draft when it moved to using =E2=80=9Cusages =E2=80=
=9C indirections for signaling protocols.</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Trickle ice can use similar a=
pproach and refer to trickle-sip as usage for trickle.</div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">Thanks</div><div dir=3D"auto">Suhas=C2=A0</d=
iv><br><div class=3D"gmail_quote"><div>On Tue, Apr 3, 2018 at 11:21 AM Suha=
s Nandakumar &lt;<a href=3D"mailto:suhasietf@gmail.com">suhasietf@gmail.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir=3D"au=
to">Adding a data point=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"=
auto">Icebis doesn=E2=80=99t talk about trickle ice and hence ice-sip-SDP d=
oesn=E2=80=99t either.</div><div dir=3D"auto"><br></div><div dir=3D"auto">I=
n the same context, would ice trickle and ice-trickle-sip-SDP focussing on =
trickle ice only procedures and usages makes sense ?</div><div dir=3D"auto"=
><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">Does that work ?=
=C2=A0</div></div><div><div dir=3D"auto"><br></div><br><div class=3D"gmail_=
quote"><div>On Tue, Apr 3, 2018 at 11:04 AM Adam Roach &lt;<a href=3D"mailt=
o:adam@nostrum.com" target=3D"_blank">adam@nostrum.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">On 4/3/18 12:54 PM, Ben Campbell wrote:<=
br>
&gt;<br>
&gt;&gt; On Apr 3, 2018, at 12:43 PM, Eric Rescorla &lt;<a href=3D"mailto:e=
kr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell &lt;<a href=3D"mailt=
o:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;&gt; On Apr 3, 2018, at 12:26 PM, Eric Rescorla &lt;<a href=3D"mail=
to:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don&#39;t think #3 is acceptable. AFAIK JSEP has no other de=
pendencies on SIP. If you think #2 and #3 are equally awkward, lets do #2.<=
br>
&gt;&gt;&gt;<br>
&gt;&gt; I said they are equally awkward (by which I mean equally awkward f=
or readers after publication), but 3 requires fewer changes (that is, less =
effort.).<br>
&gt;&gt;<br>
&gt;&gt; If we want to go for least awkward, that probably means a separate=
 trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99s=
 the past of most effort.<br>
&gt;&gt;<br>
&gt;&gt; But honestly, I think this is the sort of point that we should def=
er to WG consensus.<br>
&gt;&gt;<br>
&gt;&gt; Which WG? As I understand it, this would require a change to JSEP,=
 which would also require WG consensus, plus a change to an IESG-approved d=
ocument.<br>
&gt;<br>
&gt; I mean consensus of the WGs producing the documents. it=E2=80=99s quit=
e reasonable for a dependent WG to offer feedback, but I don=E2=80=99t thin=
k a dependent WG gets to just override that consensus.<br>
<br>
I don&#39;t think it&#39;s as clean cut as that. JSEP could have defined th=
e<br>
&quot;a=3Dend-of-candidates&quot; syntax, and certainly would have if MMUSI=
C and ICE<br>
had pulled it out of their documents. But I don&#39;t think we want both<br=
>
documents independently registering identical syntaxes with identical<br>
meanings, right? Or I suppose JSEP could have decided -- having finished<br=
>
first -- that they should define the syntax and have the trickle-ice-sip<br=
>
document reference JSEP?<br>
<br>
I&#39;m offering those up as examples, not proposals. I think the first is =
a<br>
nonstarter, and the second is... well, it&#39;s as awkward as what you&#39;=
re<br>
proposing.<br>
<br>
I&#39;m beginning to think we need to to take the question to ART rather<br=
>
than the three working groups.<br>
<br>
/a<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div></blockquote></div></div>

--001a1143fa3a4ad2460568f5de4e--


From nobody Tue Apr  3 11:29:26 2018
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 F008612EA5A; Tue,  3 Apr 2018 11:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2mgxobLuAWH; Tue,  3 Apr 2018 11:29:08 -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 092AD12EA87; Tue,  3 Apr 2018 11:29:08 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w33IT1bn097356 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 13:29:02 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>, Flemming Andreasen <fandreas@cisco.com>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, "ice@ietf.org" <ice@ietf.org>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <0503b397-787a-a0de-15aa-dc6dee57a4f8@nostrum.com>
Date: Tue, 3 Apr 2018 13:28:56 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F126C25807B9208D48B05CB1"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/a_60ez6nrIuE6wgFldyo0iSm4qA>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:29:23 -0000

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

Like I said originally, none of these are particularly clean. Your 
proposal points towards either #1 or #3, and I highlighted their 
drawbacks in my original message.

Fundamentally, the suggestion Ben made is the only clean one: split 
trickle-ice-sip into two documents: one deals with SIP (think a parallel 
to RFC 3261) while the other deals with SDP (think a parallel to RFC 
3264). But I also agree with him that sending the document back to the 
WG for such a split would introduce a significant amount of work.

Absent that, we need to pick which wart we're going to accept.

/a

On 4/3/18 1:21 PM, Suhas Nandakumar wrote:
> Adding a data point
>
> Icebis doesn’t talk about trickle ice and hence ice-sip-SDP doesn’t 
> either.
>
> In the same context, would ice trickle and ice-trickle-sip-SDP 
> focussing on trickle ice only procedures and usages makes sense ?
>
>
> Does that work ?
>
>
> On Tue, Apr 3, 2018 at 11:04 AM Adam Roach <adam@nostrum.com 
> <mailto:adam@nostrum.com>> wrote:
>
>     On 4/3/18 12:54 PM, Ben Campbell wrote:
>     >
>     >> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com
>     <mailto:ekr@rtfm.com>> wrote:
>     >>
>     >>
>     >>
>     >> On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com
>     <mailto:ben@nostrum.com>> wrote:
>     >>
>     >>
>     >>> On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com
>     <mailto:ekr@rtfm.com>> wrote:
>     >>>
>     >>> I don't think #3 is acceptable. AFAIK JSEP has no other
>     dependencies on SIP. If you think #2 and #3 are equally awkward,
>     lets do #2.
>     >>>
>     >> I said they are equally awkward (by which I mean equally
>     awkward for readers after publication), but 3 requires fewer
>     changes (that is, less effort.).
>     >>
>     >> If we want to go for least awkward, that probably means a
>     separate trickle-ice-sdp draft in parallel to the ice sdp draft.
>     But that’s the past of most effort.
>     >>
>     >> But honestly, I think this is the sort of point that we should
>     defer to WG consensus.
>     >>
>     >> Which WG? As I understand it, this would require a change to
>     JSEP, which would also require WG consensus, plus a change to an
>     IESG-approved document.
>     >
>     > I mean consensus of the WGs producing the documents. it’s quite
>     reasonable for a dependent WG to offer feedback, but I don’t think
>     a dependent WG gets to just override that consensus.
>
>     I don't think it's as clean cut as that. JSEP could have defined the
>     "a=end-of-candidates" syntax, and certainly would have if MMUSIC
>     and ICE
>     had pulled it out of their documents. But I don't think we want both
>     documents independently registering identical syntaxes with identical
>     meanings, right? Or I suppose JSEP could have decided -- having
>     finished
>     first -- that they should define the syntax and have the
>     trickle-ice-sip
>     document reference JSEP?
>
>     I'm offering those up as examples, not proposals. I think the
>     first is a
>     nonstarter, and the second is... well, it's as awkward as what you're
>     proposing.
>
>     I'm beginning to think we need to to take the question to ART rather
>     than the three working groups.
>
>     /a
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Like I said originally, none of these
      are particularly clean. Your proposal points towards either #1 or
      #3, and I highlighted their drawbacks in my original message.<br>
      <br>
      Fundamentally, the suggestion Ben made is the only clean one:
      split trickle-ice-sip into two documents: one deals with SIP
      (think a parallel to RFC 3261) while the other deals with SDP
      (think a parallel to RFC 3264). But I also agree with him that
      sending the document back to the WG for such a split would
      introduce a significant amount of work.<br>
      <br>
      Absent that, we need to pick which wart we're going to accept.<br>
      <br>
      /a<br>
      <br>
      On 4/3/18 1:21 PM, Suhas Nandakumar wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com">
      <div>
        <div dir="auto">Adding a data point </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Icebis doesn’t talk about trickle ice and hence
          ice-sip-SDP doesn’t either.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">In the same context, would ice trickle and
          ice-trickle-sip-SDP focussing on trickle ice only procedures
          and usages makes sense ?</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Does that work ? </div>
        <div dir="auto"><br>
        </div>
        <br>
        <div class="gmail_quote">
          <div>On Tue, Apr 3, 2018 at 11:04 AM Adam Roach &lt;<a
              href="mailto:adam@nostrum.com" moz-do-not-send="true">adam@nostrum.com</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">On 4/3/18
            12:54 PM, Ben Campbell wrote:<br>
            &gt;<br>
            &gt;&gt; On Apr 3, 2018, at 12:43 PM, Eric Rescorla &lt;<a
              href="mailto:ekr@rtfm.com" target="_blank"
              moz-do-not-send="true">ekr@rtfm.com</a>&gt; wrote:<br>
            &gt;&gt;<br>
            &gt;&gt;<br>
            &gt;&gt;<br>
            &gt;&gt; On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell &lt;<a
              href="mailto:ben@nostrum.com" target="_blank"
              moz-do-not-send="true">ben@nostrum.com</a>&gt; wrote:<br>
            &gt;&gt;<br>
            &gt;&gt;<br>
            &gt;&gt;&gt; On Apr 3, 2018, at 12:26 PM, Eric Rescorla &lt;<a
              href="mailto:ekr@rtfm.com" target="_blank"
              moz-do-not-send="true">ekr@rtfm.com</a>&gt; wrote:<br>
            &gt;&gt;&gt;<br>
            &gt;&gt;&gt; I don't think #3 is acceptable. AFAIK JSEP has
            no other dependencies on SIP. If you think #2 and #3 are
            equally awkward, lets do #2.<br>
            &gt;&gt;&gt;<br>
            &gt;&gt; I said they are equally awkward (by which I mean
            equally awkward for readers after publication), but 3
            requires fewer changes (that is, less effort.).<br>
            &gt;&gt;<br>
            &gt;&gt; If we want to go for least awkward, that probably
            means a separate trickle-ice-sdp draft in parallel to the
            ice sdp draft. But that’s the past of most effort.<br>
            &gt;&gt;<br>
            &gt;&gt; But honestly, I think this is the sort of point
            that we should defer to WG consensus.<br>
            &gt;&gt;<br>
            &gt;&gt; Which WG? As I understand it, this would require a
            change to JSEP, which would also require WG consensus, plus
            a change to an IESG-approved document.<br>
            &gt;<br>
            &gt; I mean consensus of the WGs producing the documents.
            it’s quite reasonable for a dependent WG to offer feedback,
            but I don’t think a dependent WG gets to just override that
            consensus.<br>
            <br>
            I don't think it's as clean cut as that. JSEP could have
            defined the<br>
            "a=end-of-candidates" syntax, and certainly would have if
            MMUSIC and ICE<br>
            had pulled it out of their documents. But I don't think we
            want both<br>
            documents independently registering identical syntaxes with
            identical<br>
            meanings, right? Or I suppose JSEP could have decided --
            having finished<br>
            first -- that they should define the syntax and have the
            trickle-ice-sip<br>
            document reference JSEP?<br>
            <br>
            I'm offering those up as examples, not proposals. I think
            the first is a<br>
            nonstarter, and the second is... well, it's as awkward as
            what you're<br>
            proposing.<br>
            <br>
            I'm beginning to think we need to to take the question to
            ART rather<br>
            than the three working groups.<br>
            <br>
            /a<br>
            <br>
            _______________________________________________<br>
            mmusic mailing list<br>
            <a href="mailto:mmusic@ietf.org" target="_blank"
              moz-do-not-send="true">mmusic@ietf.org</a><br>
            <a href="https://www.ietf.org/mailman/listinfo/mmusic"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------F126C25807B9208D48B05CB1--


From nobody Tue Apr  3 11:40:03 2018
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 F287C12EAB7 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 11:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wqXsO7KycNmz for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 11:39:58 -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 63C4B12E8A4 for <mmusic@ietf.org>; Tue,  3 Apr 2018 11:39:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522780791; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=66tWBZRNlTx7cAjqhDh0S2oFq22lcKHRFI7hDKVIkNk=; b=URDp+6DgYzyj9dRIxaYW+Q9Sp1tIROkIQnD6VWMDrXuACQcIC3jBivmBmNHNS8nw saKnRkkvXmo16WdA/mdtPjlMGLfwjq94ahI6vjosewXDxZirbb3DhAoSsEKMdkBD C7Gcuz4VtSeoXVITDw0YZPf78LSaTcAO6xJeOevohmk=;
X-AuditID: c1b4fb25-1dfff7000000522b-ed-5ac3ca776171
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 91.9B.21035.77AC3CA5; Tue,  3 Apr 2018 20:39:51 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0382.000; Tue, 3 Apr 2018 20:39:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>, Ben Campbell <ben@nostrum.com>, "Eric Rescorla" <ekr@rtfm.com>
CC: mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, Peter Saint-Andre <stpeter@mozilla.com>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAAJqMw
Date: Tue, 3 Apr 2018 18:39:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E43E23@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com>
In-Reply-To: <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCIsWRmVeSWpSXmKPExsUyM2K7tG75qcNRBvOeaFjs+buI3WJ+52l2 ix9rlzNbrHh9jt3i/QVdi28Xai1m/JnIbHF+53omi6nLH7NYrP3Xzm7xbOUpRgdujym/N7J6 LFnyk8mj70AXq8esnU9YPCY/bmMOYI3isklJzcksSy3St0vgyrjz9jJLwQbOip7dF9gaGCdw djFyckgImEhcX3acFcQWEjjCKPHpVCGEvZhRYuchny5GDg42AQuJ7n/aIGERgWSJ9Rva2LsY uTiYBZ4zSdw8/4kdJCEsUCCxcU4rG0RRocTaHY+g7CiJyYufs4DYLAIqEjN7jjOC2LwCvhIz Fu1hAxkkJDCTRWLS6ltgDZwC9hL9a7eCNTAKiEl8P7WGCcRmFhCXuPVkPhPE0QISS/acZ4aw RSVePv7HCmErSTz9v4QJ5GhmAU2J9bv0IVoVJaZ0P2SH2CsocXLmE5YJjKKzkEydhdAxC0nH LCQdCxhZVjGKFqcWJ+WmGxnrpRZlJhcX5+fp5aWWbGIExuXBLb9VdzBefuN4iFGAg1GJh9fp 6OEoIdbEsuLK3EOMEhzMSiK8CpuBQrwpiZVVqUX58UWlOanFhxilOViUxHkfmm+OEhJITyxJ zU5NLUgtgskycXBKNTC62HBnhYv1RHT/XtHT35LK2XbYIn5JVVpZ0aZwiWUm5se2fnH0eDQ/ upst3jnikPr89PLvDNbTzvcyfngsKcC9rHAhE3+enbV9DeeBnOaZ/otWnvRf4uSwQjrC7vPk lnVTZiWmdjFMZ7rTNWXysovebfN4lIM6Q249VmXvflX5/Gm2d7ygnxJLcUaioRZzUXEiAJdK /afHAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/k43FoGoXfyPUIK-sOXHoeLtml6w>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:40:03 -0000

SGksDQoNCj4gSSBkb24ndCB0aGluayBpdCdzIGFzIGNsZWFuIGN1dCBhcyB0aGF0LiBKU0VQIGNv
dWxkIGhhdmUgZGVmaW5lZCB0aGUgImE9ZW5kLW9mLWNhbmRpZGF0ZXMiIHN5bnRheCwgYW5kIGNl
cnRhaW5seSANCj4gd291bGQgaGF2ZSBpZiBNTVVTSUMgYW5kIElDRSBoYWQgcHVsbGVkIGl0IG91
dCBvZiB0aGVpciBkb2N1bWVudHMuIEJ1dCBJIGRvbid0IHRoaW5rIHdlIHdhbnQgYm90aCBkb2N1
bWVudHMgDQo+IGluZGVwZW5kZW50bHkgcmVnaXN0ZXJpbmcgaWRlbnRpY2FsIHN5bnRheGVzIHdp
dGggaWRlbnRpY2FsIG1lYW5pbmdzLCByaWdodD8gT3IgSSBzdXBwb3NlIEpTRVAgY291bGQgaGF2
ZSBkZWNpZGVkIA0KPiAtLSBoYXZpbmcgZmluaXNoZWQgZmlyc3QgLS0gdGhhdCB0aGV5IHNob3Vs
ZCBkZWZpbmUgdGhlIHN5bnRheCBhbmQgaGF2ZSB0aGUgdHJpY2tsZS1pY2Utc2lwIGRvY3VtZW50
IHJlZmVyZW5jZSBKU0VQPw0KPg0KPiBJJ20gb2ZmZXJpbmcgdGhvc2UgdXAgYXMgZXhhbXBsZXMs
IG5vdCBwcm9wb3NhbHMuIEkgdGhpbmsgdGhlIGZpcnN0IGlzIGEgbm9uc3RhcnRlciwgYW5kIHRo
ZSBzZWNvbmQgaXMuLi4gd2VsbCwgaXQncyBhcyANCj4gYXdrd2FyZCBhcyB3aGF0IHlvdSdyZSBw
cm9wb3NpbmcuDQoNCkhhdmluZyB0cmlja2xlLWljZS1zaXAgcmVmZXJlbmNpbmcgSlNFUCwganVz
dCBmb3IgdGhlIGF0dHJpYnV0ZSwgd291bGQgYmUgZXZlbiBtb3JlIGF3a3dhcmQgaW4gbXkgb3Bp
bmlvbiA6KSANCg0KSW4gYWRkaXRpb24sIHdlIHdvdWxkIGFsc28gaGF2ZSB0byBhZGQgdGhlIGdl
bmVyaWMgTy9BIHByb2NlZHVyZXMgZm9yIHRoZSBhdHRyaWJ1dGUgdG8gSlNFUC4NCg0KUmVnYXJk
cywNCg0KQ2hyaXN0ZXINCg0KDQo=


From nobody Tue Apr  3 11:44:01 2018
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 5478112D80F for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 11:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level: 
X-Spam-Status: No, score=-4.309 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_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, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4nHfjrQ8iSh4 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 11:43: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 381F9124BE8 for <mmusic@ietf.org>; Tue,  3 Apr 2018 11:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522781029; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=f1Dh/dTp8PHYPdzmIEhGrJ318h9S8Op9Q1EmdeBAOOw=; b=gonY3+gx8XU3Uo4Jcmmd+4jK/rfvU59Np1r+TXkyEvJY8E677z+wBuDMp6JApLjS ejyHCTk8aUu2cfk/S8bEeLfbwsrVz94T4AjTlJK0BqSfnT4Vs2+u0T+UwrfgTXpp kRLTh2I8rIhdnTYOS2maypExyjW09zGGNq7BPKgolBI=;
X-AuditID: c1b4fb25-5a75a9c00000522b-2a-5ac3cb65703a
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 81.FB.21035.56BC3CA5; Tue,  3 Apr 2018 20:43:49 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0382.000; Tue, 3 Apr 2018 20:43:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>, Suhas Nandakumar <suhasietf@gmail.com>
CC: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>, "Flemming Andreasen" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>, "ice@ietf.org" <ice@ietf.org>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAABSyAgAAB8QCAACT40A==
Date: Tue, 3 Apr 2018 18:43:09 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E43E90@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <0503b397-787a-a0de-15aa-dc6dee57a4f8@nostrum.com>
In-Reply-To: <0503b397-787a-a0de-15aa-dc6dee57a4f8@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72E43E90ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHIsWRmVeSWpSXmKPExsUyM2K7vW7q6cNRBt8btSz2/F3EbjG/8zS7 xY+1y5ktVrw+x27x/oKuxbcLtRYz/kxktji/cz2TxdTlj1ks1v5rZ7fYObeD2YHbY8rvjawe O2fdZfdYsuQnk8esnU9YPCY/bmMOYI3isklJzcksSy3St0vgyph6ayNzwaVGxoo7iw8wNTBO qeti5OSQEDCRmPbpBVsXIxeHkMARRomWk83MEM5iRon9xz4AORwcbAIWEt3/tEFMEQFPidOz lEFKmAX+MUks37CdCWSQsECBxMY5rWwgtohAocTaHY+g7CyJhgOnmEFsFgEVie7fK9hBbF4B X4l9vz8wQuyayipxuOMlI8gCTgF7iS8LdEBqGAXEJL6fWgM2n1lAXOLWk/lMEEcLSCzZc54Z whaVePn4HyuErSTx9P8SqPp8iaM7TjBC7BKUODnzCcsERpFZSEbNQlI2C0nZLKArmAU0Jdbv 0ocoUZSY0v2QHcLWkGidM5cdWXwBI/sqRtHi1OKk3HQjY73Uoszk4uL8PL281JJNjMBYPrjl t+oOxstvHA8xCnAwKvHwOh09HCXEmlhWXJl7iFGCg1lJhFdhM1CINyWxsiq1KD++qDQntfgQ ozQHi5I470PzzVFCAumJJanZqakFqUUwWSYOTqkGxog7l/a13t7Ufevie//7BXYb1hpULu5Z 6vupbG2MUvxBUzXpx6clGJmvb5pW9Cz66cETzB9/JN7jTVhmEpbYYvWk8P+RuPRNZ1NLX3l5 TNi0kX1T9Ms3kqW9Cw4aeXHk5PNMUfh+2ua6QvN53jsXPD9ZZc/R8ttx3uXbAuMk3u9hyif3 1Ok92qvEUpyRaKjFXFScCAD0LJTZ4QIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2zN8VuAhIh7fXG-X9zD3uC17rIs>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:43:56 -0000

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

SGksDQoNCj5MaWtlIEkgc2FpZCBvcmlnaW5hbGx5LCBub25lIG9mIHRoZXNlIGFyZSBwYXJ0aWN1
bGFybHkgY2xlYW4uIFlvdXIgcHJvcG9zYWwgcG9pbnRzIHRvd2FyZHMgZWl0aGVyICMxIG9yICMz
LCBhbmQNCj5JIGhpZ2hsaWdodGVkIHRoZWlyIGRyYXdiYWNrcyBpbiBteSBvcmlnaW5hbCBtZXNz
YWdlLg0KPg0KPkZ1bmRhbWVudGFsbHksIHRoZSBzdWdnZXN0aW9uIEJlbiBtYWRlIGlzIHRoZSBv
bmx5IGNsZWFuIG9uZTogc3BsaXQgdHJpY2tsZS1pY2Utc2lwIGludG8gdHdvIGRvY3VtZW50czog
b25lIGRlYWxzIHdpdGggU0lQICh0aGluayBhIHBhcmFsbGVsIHRvIFJGQyAzMjYxKSA+d2hpbGUg
dGhlIG90aGVyIGRlYWxzIHdpdGggU0RQICh0aGluayBhIHBhcmFsbGVsIHRvIFJGQyAzMjY0KS4g
QnV0IEkgYWxzbyBhZ3JlZSB3aXRoIGhpbSB0aGF0IHNlbmRpbmcgdGhlIGRvY3VtZW50IGJhY2sg
dG8gdGhlIFdHIGZvciBzdWNoIGEgc3BsaXQgd291bGQgPmludHJvZHVjZSBhIHNpZ25pZmljYW50
IGFtb3VudCBvZiB3b3JrLg0KDQpOb3QgZXhhY3RseSBzdXJlIHdoYXQg4oCcZGVhbHMgd2l0aCBT
RFDigJ0gd291bGQgbWVhbiwgYnV0IG9uZSBpZGVhIHdvdWxkIGJlIHRvIE9OTFkgZGVmaW5lIHRo
ZSBhdHRyaWJ1dGUsIGFuZCB0aGUgYXNzb2NpYXRlZCBPL0EgcHJvY2VkdXJlcywgaW4gYSBzZXBh
cmF0ZSBkcmFmdCwgdGhhdCB3b3VsZCBiZSByZWZlcmVuY2VkIGJ5IGRyYWZ0LWlldGYtbW11c2lj
LXRyaWNrbGUtaWNlLXNpcCBhbmQgSlNFUC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQpP
biA0LzMvMTggMToyMSBQTSwgU3VoYXMgTmFuZGFrdW1hciB3cm90ZToNCkFkZGluZyBhIGRhdGEg
cG9pbnQNCg0KSWNlYmlzIGRvZXNu4oCZdCB0YWxrIGFib3V0IHRyaWNrbGUgaWNlIGFuZCBoZW5j
ZSBpY2Utc2lwLVNEUCBkb2VzbuKAmXQgZWl0aGVyLg0KDQpJbiB0aGUgc2FtZSBjb250ZXh0LCB3
b3VsZCBpY2UgdHJpY2tsZSBhbmQgaWNlLXRyaWNrbGUtc2lwLVNEUCBmb2N1c3Npbmcgb24gdHJp
Y2tsZSBpY2Ugb25seSBwcm9jZWR1cmVzIGFuZCB1c2FnZXMgbWFrZXMgc2Vuc2UgPw0KDQoNCkRv
ZXMgdGhhdCB3b3JrID8NCg0KDQpPbiBUdWUsIEFwciAzLCAyMDE4IGF0IDExOjA0IEFNIEFkYW0g
Um9hY2ggPGFkYW1Abm9zdHJ1bS5jb208bWFpbHRvOmFkYW1Abm9zdHJ1bS5jb20+PiB3cm90ZToN
Ck9uIDQvMy8xOCAxMjo1NCBQTSwgQmVuIENhbXBiZWxsIHdyb3RlOg0KPg0KPj4gT24gQXByIDMs
IDIwMTgsIGF0IDEyOjQzIFBNLCBFcmljIFJlc2NvcmxhIDxla3JAcnRmbS5jb208bWFpbHRvOmVr
ckBydGZtLmNvbT4+IHdyb3RlOg0KPj4NCj4+DQo+Pg0KPj4gT24gVHVlLCBBcHIgMywgMjAxOCBh
dCAxMDozNSBBTSwgQmVuIENhbXBiZWxsIDxiZW5Abm9zdHJ1bS5jb208bWFpbHRvOmJlbkBub3N0
cnVtLmNvbT4+IHdyb3RlOg0KPj4NCj4+DQo+Pj4gT24gQXByIDMsIDIwMTgsIGF0IDEyOjI2IFBN
LCBFcmljIFJlc2NvcmxhIDxla3JAcnRmbS5jb208bWFpbHRvOmVrckBydGZtLmNvbT4+IHdyb3Rl
Og0KPj4+DQo+Pj4gSSBkb24ndCB0aGluayAjMyBpcyBhY2NlcHRhYmxlLiBBRkFJSyBKU0VQIGhh
cyBubyBvdGhlciBkZXBlbmRlbmNpZXMgb24gU0lQLiBJZiB5b3UgdGhpbmsgIzIgYW5kICMzIGFy
ZSBlcXVhbGx5IGF3a3dhcmQsIGxldHMgZG8gIzIuDQo+Pj4NCj4+IEkgc2FpZCB0aGV5IGFyZSBl
cXVhbGx5IGF3a3dhcmQgKGJ5IHdoaWNoIEkgbWVhbiBlcXVhbGx5IGF3a3dhcmQgZm9yIHJlYWRl
cnMgYWZ0ZXIgcHVibGljYXRpb24pLCBidXQgMyByZXF1aXJlcyBmZXdlciBjaGFuZ2VzICh0aGF0
IGlzLCBsZXNzIGVmZm9ydC4pLg0KPj4NCj4+IElmIHdlIHdhbnQgdG8gZ28gZm9yIGxlYXN0IGF3
a3dhcmQsIHRoYXQgcHJvYmFibHkgbWVhbnMgYSBzZXBhcmF0ZSB0cmlja2xlLWljZS1zZHAgZHJh
ZnQgaW4gcGFyYWxsZWwgdG8gdGhlIGljZSBzZHAgZHJhZnQuIEJ1dCB0aGF04oCZcyB0aGUgcGFz
dCBvZiBtb3N0IGVmZm9ydC4NCj4+DQo+PiBCdXQgaG9uZXN0bHksIEkgdGhpbmsgdGhpcyBpcyB0
aGUgc29ydCBvZiBwb2ludCB0aGF0IHdlIHNob3VsZCBkZWZlciB0byBXRyBjb25zZW5zdXMuDQo+
Pg0KPj4gV2hpY2ggV0c/IEFzIEkgdW5kZXJzdGFuZCBpdCwgdGhpcyB3b3VsZCByZXF1aXJlIGEg
Y2hhbmdlIHRvIEpTRVAsIHdoaWNoIHdvdWxkIGFsc28gcmVxdWlyZSBXRyBjb25zZW5zdXMsIHBs
dXMgYSBjaGFuZ2UgdG8gYW4gSUVTRy1hcHByb3ZlZCBkb2N1bWVudC4NCj4NCj4gSSBtZWFuIGNv
bnNlbnN1cyBvZiB0aGUgV0dzIHByb2R1Y2luZyB0aGUgZG9jdW1lbnRzLiBpdOKAmXMgcXVpdGUg
cmVhc29uYWJsZSBmb3IgYSBkZXBlbmRlbnQgV0cgdG8gb2ZmZXIgZmVlZGJhY2ssIGJ1dCBJIGRv
buKAmXQgdGhpbmsgYSBkZXBlbmRlbnQgV0cgZ2V0cyB0byBqdXN0IG92ZXJyaWRlIHRoYXQgY29u
c2Vuc3VzLg0KDQpJIGRvbid0IHRoaW5rIGl0J3MgYXMgY2xlYW4gY3V0IGFzIHRoYXQuIEpTRVAg
Y291bGQgaGF2ZSBkZWZpbmVkIHRoZQ0KImE9ZW5kLW9mLWNhbmRpZGF0ZXMiIHN5bnRheCwgYW5k
IGNlcnRhaW5seSB3b3VsZCBoYXZlIGlmIE1NVVNJQyBhbmQgSUNFDQpoYWQgcHVsbGVkIGl0IG91
dCBvZiB0aGVpciBkb2N1bWVudHMuIEJ1dCBJIGRvbid0IHRoaW5rIHdlIHdhbnQgYm90aA0KZG9j
dW1lbnRzIGluZGVwZW5kZW50bHkgcmVnaXN0ZXJpbmcgaWRlbnRpY2FsIHN5bnRheGVzIHdpdGgg
aWRlbnRpY2FsDQptZWFuaW5ncywgcmlnaHQ/IE9yIEkgc3VwcG9zZSBKU0VQIGNvdWxkIGhhdmUg
ZGVjaWRlZCAtLSBoYXZpbmcgZmluaXNoZWQNCmZpcnN0IC0tIHRoYXQgdGhleSBzaG91bGQgZGVm
aW5lIHRoZSBzeW50YXggYW5kIGhhdmUgdGhlIHRyaWNrbGUtaWNlLXNpcA0KZG9jdW1lbnQgcmVm
ZXJlbmNlIEpTRVA/DQoNCkknbSBvZmZlcmluZyB0aG9zZSB1cCBhcyBleGFtcGxlcywgbm90IHBy
b3Bvc2Fscy4gSSB0aGluayB0aGUgZmlyc3QgaXMgYQ0Kbm9uc3RhcnRlciwgYW5kIHRoZSBzZWNv
bmQgaXMuLi4gd2VsbCwgaXQncyBhcyBhd2t3YXJkIGFzIHdoYXQgeW91J3JlDQpwcm9wb3Npbmcu
DQoNCkknbSBiZWdpbm5pbmcgdG8gdGhpbmsgd2UgbmVlZCB0byB0byB0YWtlIHRoZSBxdWVzdGlv
biB0byBBUlQgcmF0aGVyDQp0aGFuIHRoZSB0aHJlZSB3b3JraW5nIGdyb3Vwcy4NCg0KL2ENCg0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBt
YWlsaW5nIGxpc3QNCm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjsN
Cgljb2xvcjpibGFjazt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K
YTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJn
aW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0
OjBjbTsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4i
LHNlcmlmOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9y
OiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwt
Y29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3
OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRT
ZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIg
Lz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVs
YXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8
L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBiZ2NvbG9y
PSJ3aGl0ZSIgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBj
bGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
Zjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5IaSw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4
dCI+Jmd0Ozwvc3Bhbj5MaWtlIEkgc2FpZCBvcmlnaW5hbGx5LCBub25lIG9mIHRoZXNlIGFyZSBw
YXJ0aWN1bGFybHkgY2xlYW4uIFlvdXIgcHJvcG9zYWwgcG9pbnRzIHRvd2FyZHMgZWl0aGVyICMx
IG9yICMzLCBhbmQNCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0Ij48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6d2lu
ZG93dGV4dCI+Jmd0Ozwvc3Bhbj5JIGhpZ2hsaWdodGVkIHRoZWlyIGRyYXdiYWNrcyBpbiBteSBv
cmlnaW5hbCBtZXNzYWdlLjxicj4NCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0Ij4mZ3Q7
PC9zcGFuPjxicj4NCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0Ij4mZ3Q7PC9zcGFuPkZ1
bmRhbWVudGFsbHksIHRoZSBzdWdnZXN0aW9uIEJlbiBtYWRlIGlzIHRoZSBvbmx5IGNsZWFuIG9u
ZTogc3BsaXQgdHJpY2tsZS1pY2Utc2lwIGludG8gdHdvIGRvY3VtZW50czogb25lIGRlYWxzIHdp
dGggU0lQICh0aGluayBhIHBhcmFsbGVsIHRvIFJGQyAzMjYxKQ0KPHNwYW4gc3R5bGU9ImNvbG9y
OndpbmRvd3RleHQiPiZndDs8L3NwYW4+d2hpbGUgdGhlIG90aGVyIGRlYWxzIHdpdGggU0RQICh0
aGluayBhIHBhcmFsbGVsIHRvIFJGQyAzMjY0KS4gQnV0IEkgYWxzbyBhZ3JlZSB3aXRoIGhpbSB0
aGF0IHNlbmRpbmcgdGhlIGRvY3VtZW50IGJhY2sgdG8gdGhlIFdHIGZvciBzdWNoIGEgc3BsaXQg
d291bGQNCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0Ij4mZ3Q7PC9zcGFuPmludHJvZHVj
ZSBhIHNpZ25pZmljYW50IGFtb3VudCBvZiB3b3JrLjxicj4NCjxicj4NCjxzcGFuIHN0eWxlPSJj
b2xvcjp3aW5kb3d0ZXh0Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6d2luZG93dGV4dCI+Tm90IGV4YWN0bHkgc3VyZSB3
aGF0IOKAnGRlYWxzIHdpdGggU0RQ4oCdIHdvdWxkIG1lYW4sIGJ1dCBvbmUgaWRlYSB3b3VsZCBi
ZSB0byBPTkxZIGRlZmluZSB0aGUgYXR0cmlidXRlLCBhbmQgdGhlIGFzc29jaWF0ZWQgTy9BIHBy
b2NlZHVyZXMsIGluIGEgc2VwYXJhdGUgZHJhZnQsDQogdGhhdCB3b3VsZCBiZSByZWZlcmVuY2Vk
IGJ5IGRyYWZ0LWlldGYtbW11c2ljLXRyaWNrbGUtaWNlLXNpcCBhbmQgSlNFUC48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
d2luZG93dGV4dCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOndpbmRvd3RleHQiPlJlZ2FyZHMsPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OndpbmRvd3RleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjp3aW5kb3d0ZXh0Ij5DaHJpc3RlcjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjp3aW5kb3d0ZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6d2luZG93dGV4dCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gNC8zLzE4IDE6MjEgUE0sIFN1
aGFzIE5hbmRha3VtYXIgd3JvdGU6PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOndpbmRvd3RleHQiPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10
b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkFkZGluZyBhIGRhdGEgcG9pbnQmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWNlYmlzIGRvZXNu4oCZdCB0YWxrIGFi
b3V0IHRyaWNrbGUgaWNlIGFuZCBoZW5jZSBpY2Utc2lwLVNEUCBkb2VzbuKAmXQgZWl0aGVyLjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JbiB0
aGUgc2FtZSBjb250ZXh0LCB3b3VsZCBpY2UgdHJpY2tsZSBhbmQgaWNlLXRyaWNrbGUtc2lwLVNE
UCBmb2N1c3Npbmcgb24gdHJpY2tsZSBpY2Ugb25seSBwcm9jZWR1cmVzIGFuZCB1c2FnZXMgbWFr
ZXMgc2Vuc2UgPzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkRvZXMgdGhhdCB3b3JrID8mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVHVlLCBBcHIgMywgMjAxOCBhdCAxMTowNCBBTSBB
ZGFtIFJvYWNoICZsdDs8YSBocmVmPSJtYWlsdG86YWRhbUBub3N0cnVtLmNvbSI+YWRhbUBub3N0
cnVtLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90
ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRk
aW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gNC8zLzE4IDEyOjU0IFBNLCBCZW4gQ2FtcGJlbGwg
d3JvdGU6PGJyPg0KJmd0Ozxicj4NCiZndDsmZ3Q7IE9uIEFwciAzLCAyMDE4LCBhdCAxMjo0MyBQ
TSwgRXJpYyBSZXNjb3JsYSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmVrckBydGZtLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPmVrckBydGZtLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsmZ3Q7PGJyPg0K
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IE9uIFR1ZSwgQXByIDMsIDIwMTgg
YXQgMTA6MzUgQU0sIEJlbiBDYW1wYmVsbCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmJlbkBub3N0cnVt
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmJlbkBub3N0cnVtLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4N
CiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZndDsgT24gQXByIDMsIDIwMTgs
IGF0IDEyOjI2IFBNLCBFcmljIFJlc2NvcmxhICZsdDs8YSBocmVmPSJtYWlsdG86ZWtyQHJ0Zm0u
Y29tIiB0YXJnZXQ9Il9ibGFuayI+ZWtyQHJ0Zm0uY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KJmd0
OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IEkgZG9uJ3QgdGhpbmsgIzMgaXMgYWNjZXB0YWJs
ZS4gQUZBSUsgSlNFUCBoYXMgbm8gb3RoZXIgZGVwZW5kZW5jaWVzIG9uIFNJUC4gSWYgeW91IHRo
aW5rICMyIGFuZCAjMyBhcmUgZXF1YWxseSBhd2t3YXJkLCBsZXRzIGRvICMyLjxicj4NCiZndDsm
Z3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IEkgc2FpZCB0aGV5IGFyZSBlcXVhbGx5IGF3a3dhcmQgKGJ5
IHdoaWNoIEkgbWVhbiBlcXVhbGx5IGF3a3dhcmQgZm9yIHJlYWRlcnMgYWZ0ZXIgcHVibGljYXRp
b24pLCBidXQgMyByZXF1aXJlcyBmZXdlciBjaGFuZ2VzICh0aGF0IGlzLCBsZXNzIGVmZm9ydC4p
Ljxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgSWYgd2Ugd2FudCB0byBnbyBmb3IgbGVhc3Qg
YXdrd2FyZCwgdGhhdCBwcm9iYWJseSBtZWFucyBhIHNlcGFyYXRlIHRyaWNrbGUtaWNlLXNkcCBk
cmFmdCBpbiBwYXJhbGxlbCB0byB0aGUgaWNlIHNkcCBkcmFmdC4gQnV0IHRoYXTigJlzIHRoZSBw
YXN0IG9mIG1vc3QgZWZmb3J0Ljxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgQnV0IGhvbmVz
dGx5LCBJIHRoaW5rIHRoaXMgaXMgdGhlIHNvcnQgb2YgcG9pbnQgdGhhdCB3ZSBzaG91bGQgZGVm
ZXIgdG8gV0cgY29uc2Vuc3VzLjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgV2hpY2ggV0c/
IEFzIEkgdW5kZXJzdGFuZCBpdCwgdGhpcyB3b3VsZCByZXF1aXJlIGEgY2hhbmdlIHRvIEpTRVAs
IHdoaWNoIHdvdWxkIGFsc28gcmVxdWlyZSBXRyBjb25zZW5zdXMsIHBsdXMgYSBjaGFuZ2UgdG8g
YW4gSUVTRy1hcHByb3ZlZCBkb2N1bWVudC48YnI+DQomZ3Q7PGJyPg0KJmd0OyBJIG1lYW4gY29u
c2Vuc3VzIG9mIHRoZSBXR3MgcHJvZHVjaW5nIHRoZSBkb2N1bWVudHMuIGl04oCZcyBxdWl0ZSBy
ZWFzb25hYmxlIGZvciBhIGRlcGVuZGVudCBXRyB0byBvZmZlciBmZWVkYmFjaywgYnV0IEkgZG9u
4oCZdCB0aGluayBhIGRlcGVuZGVudCBXRyBnZXRzIHRvIGp1c3Qgb3ZlcnJpZGUgdGhhdCBjb25z
ZW5zdXMuPGJyPg0KPGJyPg0KSSBkb24ndCB0aGluayBpdCdzIGFzIGNsZWFuIGN1dCBhcyB0aGF0
LiBKU0VQIGNvdWxkIGhhdmUgZGVmaW5lZCB0aGU8YnI+DQomcXVvdDthPWVuZC1vZi1jYW5kaWRh
dGVzJnF1b3Q7IHN5bnRheCwgYW5kIGNlcnRhaW5seSB3b3VsZCBoYXZlIGlmIE1NVVNJQyBhbmQg
SUNFPGJyPg0KaGFkIHB1bGxlZCBpdCBvdXQgb2YgdGhlaXIgZG9jdW1lbnRzLiBCdXQgSSBkb24n
dCB0aGluayB3ZSB3YW50IGJvdGg8YnI+DQpkb2N1bWVudHMgaW5kZXBlbmRlbnRseSByZWdpc3Rl
cmluZyBpZGVudGljYWwgc3ludGF4ZXMgd2l0aCBpZGVudGljYWw8YnI+DQptZWFuaW5ncywgcmln
aHQ/IE9yIEkgc3VwcG9zZSBKU0VQIGNvdWxkIGhhdmUgZGVjaWRlZCAtLSBoYXZpbmcgZmluaXNo
ZWQ8YnI+DQpmaXJzdCAtLSB0aGF0IHRoZXkgc2hvdWxkIGRlZmluZSB0aGUgc3ludGF4IGFuZCBo
YXZlIHRoZSB0cmlja2xlLWljZS1zaXA8YnI+DQpkb2N1bWVudCByZWZlcmVuY2UgSlNFUD88YnI+
DQo8YnI+DQpJJ20gb2ZmZXJpbmcgdGhvc2UgdXAgYXMgZXhhbXBsZXMsIG5vdCBwcm9wb3NhbHMu
IEkgdGhpbmsgdGhlIGZpcnN0IGlzIGE8YnI+DQpub25zdGFydGVyLCBhbmQgdGhlIHNlY29uZCBp
cy4uLiB3ZWxsLCBpdCdzIGFzIGF3a3dhcmQgYXMgd2hhdCB5b3UncmU8YnI+DQpwcm9wb3Npbmcu
PGJyPg0KPGJyPg0KSSdtIGJlZ2lubmluZyB0byB0aGluayB3ZSBuZWVkIHRvIHRvIHRha2UgdGhl
IHF1ZXN0aW9uIHRvIEFSVCByYXRoZXI8YnI+DQp0aGFuIHRoZSB0aHJlZSB3b3JraW5nIGdyb3Vw
cy48YnI+DQo8YnI+DQovYTxicj4NCjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPGJyPg0KbW11c2ljIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9
Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tbXVzaWNAaWV0Zi5vcmc8
L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
bXVzaWMiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL21tdXNpYzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8cD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_7594FB04B1934943A5C02806D1A2204B72E43E90ESESSMB109erics_--


From nobody Tue Apr  3 11:46:13 2018
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 C25FA12EA52; Tue,  3 Apr 2018 11:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UMt4qOEsWlF2; Tue,  3 Apr 2018 11:46:09 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c: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 BE45F12D80F; Tue,  3 Apr 2018 11:46:08 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id t67so15835892wmt.0; Tue, 03 Apr 2018 11:46:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=Tiyn+xpiwIcOC31yUkBG1twpQ61acr8ce0cBomdg2WY=; b=fCmvKMaAK6H5amLaBa0bQSUTBfWcaRh/bultl06zIdLe80sidNvFjiM5VcS+eXAXJE Pkmhj1t7dpOj6bEmFvcqj9HVCbjhKjD0nCq9nwF0ndvIYGhGZ1DJQ5fag+T1Yy8JGuWX 2Nv6B8VLBnSrNK+qPoa4UbrntZ1wwkeNGfIlkxCMusyjlhRnBNlMOERUcf1UmwmnZ9Qp A1i8OuJwd84cl3Lqv9VFGsaUUnMLbWAO4n24Sr3XF3D7VHK7duWxZdO0pzi3TCmF3El/ aX1E45s5dmg0r5MPpxz2Ju5SZgCcCFNK4vae2RCIG/dX9fy2mbPRoOJp5eIO5kjWLYgf RPog==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=Tiyn+xpiwIcOC31yUkBG1twpQ61acr8ce0cBomdg2WY=; b=Md2+4ggmyvsgJM8JORU57YxxeRmp/xJYCjBLyYEQdKLpRp3AUDK9JPDT4LDTGRWbm9 FgmRWpi/Mr99GhyWzKDLyu9K4M21XovB2TxuJwb86RqnVZH1EMEi9bd72lIihG5cxfXt Ka7nO2KgCNrgivkQxsiarsaeY2C2khkK2AdTLrfh+pP6MRBhnw6S2ww/o8sZqFpy9Bu2 fo541nGcMT9TupZXM0W3WS/TnyGNXQnt1A3CZDOpF8deZfVeXRt72q5gilUNapBqeL/M mQlK5GAIJboysGLW38yiTw8FpPraGV9HO0OETiL0AguYiiulvkysDr+/9abhswgIYayE yBKA==
X-Gm-Message-State: AElRT7GSOFFu+QCU5IxUzulc+BpKhh7TjlphaD5hvXOZ/Ikd077qmHsn A05kzVxAp7mtx4jI9a68uha7azZvC5Y=
X-Google-Smtp-Source: AIpwx4+a4HHBRn7zFhjENzHrj3ETnyLA/h3gu46BE+y/Hoj3qlVzttfC6H4iaLixIh4xVTms5kgggg==
X-Received: by 10.28.30.85 with SMTP id e82mr4843447wme.67.1522781166815; Tue, 03 Apr 2018 11:46:06 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id m7sm2286745wrb.61.2018.04.03.11.46.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 11:46:06 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com>
Date: Tue, 3 Apr 2018 20:46:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------A044B65225864C190F2B4457"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/C5ld21M-0DpM2gf0TLDdGGiR9Ew>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 18:46:12 -0000

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

EKR,

thanks for your comments, responses inline


On 2018-04-03 00:54, Eric Rescorla wrote:
> Eric Rescorla has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
>     the Offer (as would be the case when Half Trickle is performed or
>     when new candidates have not been learned since then).
> IMPORTANT: They must be in order, right?
I'm not sure what the issues is here.
The cited text addresses the first of two cases, i.e. the case where the 
INFO requests repeats
  the exact same set of candidates that was already provided in the 
initial offer.
This could happen when
a) Half Trickle is used (all candidate were already in the initial offer) or
b) Full Trickle is used where  the offerer is currently gathering 
additional candidates, but did not yet get them.

The second case (Full Trickle with additional candidates already 
available) is addressed in the subsequent paragraph.
.. and yes the candidates are sent in the order as they were gathered.
>
>     'application/trickle-ice-sdpfrag' bodies do not interfere with the
>     Offer/Answer procedures as specified in [RFC3264].
> IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.
5888 is cited as it defines the a=mid: attribute that we used for 
identifying the m-line to which a candidate belongs.
The a=mid: attribute helps in case of multiple m-lines, when we already 
have gathered candidates
for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>
>     sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
>     the same order as they were gathered.  In other words, the sequence
>     of a previously sent list of candidates MUST NOT change in subsequent
>
> IMPORTANT: This appears to conflict with the guidance in Section 6 of
> the trickle document, which is about reordering candidates from how
> they were gathered.

Do you mean section 7  which talks about reordering candidate _pairs_ at 
the IE agents?
We  require that the ordering of the _candidates_ MUST not change
when the candidates are sent several times from one  ICE agent to its 
peer in subsequent INFO requests.
I don't see a conflict.
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>    SIP message.  At the remote agent the gathering procedure is repeated
>     and candidates are sent to the first agent.  Finally, a third phase
>     starts where connectivity between all candidates in both sets is
>
> This suggests that they have to happen in sequence, but that's not true.
>
>     include in each "m="-line a "a=mid:" attribute in accordance to
>     [RFC5888].
>
> Why is this required?
As above, the a=mid: attribute helps in case of multiple m-lines, when 
we already have gathered candidates
for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>
>     section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
>     is not yet provided.
>
> Can you explain why you cease retransmitting on receiving INFO? I assume
> because it's an implicit ACK of your INFO?
The INFO is an ACK that an early dialog is now established, such that 
INFOs can be send in the reverse direction as well.
>
>     m=lines that they pertain to.  The correspondence can be made via the
>     "a=mid:" attributes.
>
> This whole section needs to be rewritten to make clear what's going on:
>
>      candidates are grouped in sections headed by "pseudo" m=lines
>      These sections contain a=mid values which point back to the true m=line.
Would it be sufficient to rephrase as follows?

Note, that there is no requirement that the Info request body
    contains as many pseudo m= lines as the Offer/Answer contains m=
    lines, nor that the pseudo m= lines be in the same order as the
    m=lines that they pertain to.  The correspondence can be made via the
    "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
     These sections contain a=mid: attribute values which point back to the true m=line.

Kind regards
Thomas




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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>EKR,</p>
    <p>thanks for your comments, responses inline<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2018-04-03 00:54, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com">
      <pre wrap="">Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-sip-14: Discuss

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


Please refer to <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html">https://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/">https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/</a>



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

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?</pre>
    </blockquote>
    I'm not sure what the issues is here.<br>
    The cited text addresses the first of two cases, i.e. the case 
    where the INFO requests repeats <br>
     the exact same set of candidates that was already provided in the
    initial offer. <br>
    This could happen when <br>
    a) Half Trickle is used (all candidate were already in the initial
    offer) or<br>
    b) Full Trickle is used where  the offerer is currently gathering
    additional candidates, but did not yet get them.<br>
    <br>
    The second case (Full Trickle with additional candidates already
    available) is addressed in the subsequent paragraph.<br>
    .. and yes the candidates are sent in the order as they were
    gathered.<br>
    <blockquote type="cite"
cite="mid:152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com">
      <pre wrap="">

   'application/trickle-ice-sdpfrag' bodies do not interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.</pre>
    </blockquote>
    5888 is cited as it defines the a=mid: attribute that we used for
    identifying the m-line to which a candidate belongs.<br>
    The a=mid: attribute helps in case of multiple m-lines, when we
    already have gathered candidates <br>
    for e.g. the first and fourth m-line, but not for the 2nd and 3rd. <br>
    <blockquote type="cite"
cite="mid:152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com">
      <pre wrap="">

   sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.</pre>
    </blockquote>
    <br>
    Do you mean section 7  which talks about reordering candidate
    _pairs_ at the IE agents?<br>
    We  require that the ordering of the _candidates_ MUST not change  <br>
    when the candidates are sent several times from one  ICE agent to
    its peer in subsequent INFO requests.<br>
    I don't see a conflict.<br>
    <blockquote type="cite"
cite="mid:152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com">
      <pre wrap="">


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

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that's not true.

   include in each "m="-line a "a=mid:" attribute in accordance to
   [RFC5888].

Why is this required?</pre>
    </blockquote>
    As above, the a=mid: attribute helps in case of multiple m-lines,
    when we already have gathered candidates <br>
    for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
    <blockquote type="cite"
cite="mid:152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com">
      <pre wrap="">

   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it's an implicit ACK of your INFO?</pre>
    </blockquote>
    The INFO is an ACK that an early dialog is now established, such
    that INFOs can be send in the reverse direction as well.<br>
    <blockquote type="cite"
cite="mid:152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com">
      <pre wrap="">

   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes.

This whole section needs to be rewritten to make clear what's going on:

    candidates are grouped in sections headed by "pseudo" m=lines
    These sections contain a=mid values which point back to the true m=line.
</pre>
    </blockquote>
    Would it be sufficient to rephrase as follows?<br>
    <pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">Note, that there is no requirement that the Info request body
   contains as many pseudo m= lines as the Offer/Answer contains m=
   lines, nor that the pseudo m= lines be in the same order as the
   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
    These sections contain a=mid: attribute values which point back to the true m=line.

Kind regards
Thomas 
</pre>
    <br>
    <br>
  </body>
</html>

--------------A044B65225864C190F2B4457--


From nobody Tue Apr  3 12:20:20 2018
Return-Path: <stpeter@mozilla.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 78FAC12D868 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 12:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 rtdzb4jmhDEe for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 12:20:12 -0700 (PDT)
Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::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 A53D71242F7 for <mmusic@ietf.org>; Tue,  3 Apr 2018 12:20:10 -0700 (PDT)
Received: by mail-it0-x235.google.com with SMTP id 15-v6so14055653itl.1 for <mmusic@ietf.org>; Tue, 03 Apr 2018 12:20:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bzH2tNo5SSXPsue2nlimcG4u0gM3hKtBF3RlXVqb8i4=; b=Li4EwRk5wEypliSg11A0RLyQQOk+3oJOHZWTYmmi3QKww7mJ03WcWfViJQM7JsTj/h 1/DiT5WT+kdHwqP8BfyN/QrAufxSerfhfpgDWKn39OUgdtjSz6LwlvpwMIKauYETCc75 K0XjGv2DpYXIwYHUZvZdwUTuqvOL8DuSraMjE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=bzH2tNo5SSXPsue2nlimcG4u0gM3hKtBF3RlXVqb8i4=; b=FULWyH/EN52toS8Jsmme328NnPYPm0qh0RhTJSQ90X3UBoXP6flmm/bKttqYq9+lMO fCB+pRuegLWyKirprI4H8GPrmT7j/wIWUSRZGPH6mRrcsN8wgtsC7bpp5kDOLlaRI4UJ 66CljZTVgWzH03BSMO228wKPQWlxNl80/dGnfABdm1BuGB43s+HovX9JTcWGAjUAAGgE 9CDiciuXTTDMzqZ9MrmgZrb+RghdRfMJQ47VI+wc7ZLApqEWmC49UgHA1/R/T+qSXUpP T5PXuaOAPIIlDZpKSg/d0/CQIRrETAfBCZxzEXuJLk3OgOubI/0rlCa4f9Yo5BbJgMCR 625Q==
X-Gm-Message-State: ALQs6tCkNE8cb7Z21XG7o5Tz02pHdeC0yaY6UFajoFvDP8vyuwSaSuyJ g7savZtMSbABK/EJfH9bK1zc2A==
X-Google-Smtp-Source: AIpwx48JdPBtTwV/N7XlQfI7cq7AiaqjHJ3X+nrlXZOj9xEU4JVz+78UDc3E6xMtGFMQxKMoBk5kVQ==
X-Received: by 2002:a24:c902:: with SMTP id h2-v6mr6051865itg.61.1522783210030;  Tue, 03 Apr 2018 12:20:10 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id 194-v6sm862143itm.15.2018.04.03.12.20.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 12:20:09 -0700 (PDT)
To: Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com>
Date: Tue, 3 Apr 2018 13:20:08 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/YoM391hsbqWhsCEJXrg2Y7B0tWc>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 19:20:13 -0000

On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
> Just to complete, ice-bis doesn’t normatively reference ice-sip-SDP
> draft when it moved to using “usages “ indirections for signaling protocols.
> 
> 
> Trickle ice can use similar approach and refer to trickle-sip as usage
> for trickle.

It already does. That's why we pulled all the SDP/SIP stuff out of
draft-ietf-ice-trickle.

Peter


From nobody Tue Apr  3 12:22:21 2018
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 24D2612D868; Tue,  3 Apr 2018 12:22:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q5LrD4cLvM7m; Tue,  3 Apr 2018 12:22:13 -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 61B671242F7; Tue,  3 Apr 2018 12:22:13 -0700 (PDT)
Received: from [10.0.1.91] (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 w33JM7P6006475 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 14:22:08 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F245D20C-39E2-4BD0-9212-91B2FF7723BE"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 14:22:07 -0500
In-Reply-To: <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
To: Peter Saint-Andre <stpeter@mozilla.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/t8z766_VIS9dPqaEXvcNWTl7NVI>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 19:22:15 -0000

--Apple-Mail=_F245D20C-39E2-4BD0-9212-91B2FF7723BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com> =
wrote:
>=20
> On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
>> Just to complete, ice-bis doesn=E2=80=99t normatively reference =
ice-sip-SDP
>> draft when it moved to using =E2=80=9Cusages =E2=80=9C indirections =
for signaling protocols.
>>=20
>>=20
>> Trickle ice can use similar approach and refer to trickle-sip as =
usage
>> for trickle.
>=20
> It already does. That's why we pulled all the SDP/SIP stuff out of
> draft-ietf-ice-trickle.

I assume Suhas meant separating the SDP stuff from the SIP stuff. (I =
also assume he will correct me if I am wrong.)

Thanks,

Ben.


--Apple-Mail=_F245D20C-39E2-4BD0-9212-91B2FF7723BE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrD1F8ACgkQgFZKbJXz
1A2Iqw//WgI389gyLqsJz5beKg5/rdC5MHTRXbQg0qxCGI32jhmKqmootFjmT4lK
Dx3BZB5yJBT/Ny7v3aXcbD7pz8UWFFXKYtn0svO0M4tk8VBRW6ti8H6zq1it6H+8
6nAvaSVj5e1+H++4CrrBmzxrnxmjSFSIDFtBqiByickXiaKzTDRtJCWriwhCQRgf
Q4xWXo81WmD6RTuPlvusr3PtQykzhxsQSe+buprrGvrAL+eQuic96ZKvwTsWS2HY
gimFCENGifQ3oW8UrUtJcwnBVAN70PMjmZxqL4FfTolTTNjTpFxvCsktoNr18985
QsPynmxWOEgQjcryZZht6KU0S9UNeIf957S6/n+JVOizSgvx7xCMU4R9m8B2YT4o
JxMlWy7x1PL7gHNou0UAEhug8XM0fnR+Bp6XyLfhh4CYTTMpnEV71Q9O0CbDhwlV
qumq7VVLUr95x+Vd6OnIqZY2QyUROsV0T+fZMm1uawgLbBKARPvBbCoE2v8FbdM5
ut0PvFbg6Jvj951NrIl4acLkbn7EAYGYsECcGKR6s2xUpNXOUEvCDl6u77vXjk2w
ETDP+NLlJdbgsxP2pFMDgG/5/I3ayUYKo6VQkzTwGTWLz/dCU98nG9AH96hWsATh
q2DhRin1i9TeiF6KbgDcvLrB/JEHsVojnQx6n6eXGpyWn7mOp+I=
=D3vU
-----END PGP SIGNATURE-----

--Apple-Mail=_F245D20C-39E2-4BD0-9212-91B2FF7723BE--


From nobody Tue Apr  3 12:34:36 2018
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 52E3112EA64; Tue,  3 Apr 2018 12:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgZIR5PTDs_M; Tue,  3 Apr 2018 12:34:27 -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 834B312D864; Tue,  3 Apr 2018 12:34:25 -0700 (PDT)
Received: from [10.0.1.91] (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 w33JYLsL008394 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 3 Apr 2018 14:34:21 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <9AE05B60-9E8E-42C8-B114-3A92A0186604@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_ED5E25F7-8FAC-49FF-92D7-180512CF7808"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 3 Apr 2018 14:34:20 -0500
In-Reply-To: <0503b397-787a-a0de-15aa-dc6dee57a4f8@nostrum.com>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
To: Adam Roach <adam@nostrum.com>, Roman Shpount <roman@telurix.com>, Peter Saint-Andre <stpeter@mozilla.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <0503b397-787a-a0de-15aa-dc6dee57a4f8@nostrum.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hX41vX-XYoY1a83f1akV8ZvD4zE>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 19:34:29 -0000

--Apple-Mail=_ED5E25F7-8FAC-49FF-92D7-180512CF7808
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Apr 3, 2018, at 1:28 PM, Adam Roach <adam@nostrum.com> wrote:
>=20
> Like I said originally, none of these are particularly clean. Your =
proposal points towards either #1 or #3, and I highlighted their =
drawbacks in my original message.
>=20
> Fundamentally, the suggestion Ben made is the only clean one: split =
trickle-ice-sip into two documents: one deals with SIP (think a parallel =
to RFC 3261) while the other deals with SDP (think a parallel to RFC =
3264). But I also agree with him that sending the document back to the =
WG for such a split would introduce a significant amount of work.
>=20
> Absent that, we need to pick which wart we're going to accept.

Roman suggested in s separate thread branch that there is more to this =
than just "a=3Dend-of-candidates=E2=80=9D. Roman said:

> It is not just end-of-candidates, but also support for c=3D0.0.0.0 in =
offers, SDP offers without the candidates, different mismatch rules. As =
it stands, draft-ietf-mmusic-trickle-ice-sip changes how =
draft-ietf-mmusic-ice-sip-sdp works when trickle ICE is used.
>=20

=E2=80=A6 and also =E2=80=A6

> For instance current in draft-ietf-rtcweb-jsep-24 =
(https://tools.ietf.org/html/draft-ietf-rtcweb-jsep-24#section-5.2.1):
>=20
> If the m=3D section is marked as bundle-only, then the port value MUST =
be set to 0.  Otherwise, the port value is set to the port of the =
default ICE candidate for this m=3D section, but given that no =
candidates are available yet, the "dummy" port value of 9 (Discard) MUST =
be used, as indicated in [I-D.ietf-ice-trickle], Section 5.1.
>=20
> I am fairly sure this is no longer in ietf-ice-trickle  and was moved =
to draft-ietf-mmusic-trickle-ice-sip =
(https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-14#section-=
4.1.1).

I think maybe we need a sweep of jsep to get a definitive list of =
references that need to change due the current document structure. =
Without that list, it=E2=80=99s hard to really assess the amount of work =
implied by each proposed fix. (Note that we will need such a list one =
way or another before JSEP can be published=E2=80=94so this does not add =
new work per se.)

Roman and Peter: Can you compile a list? Perhaps with the assistance of =
a JSEP author?  (I=E2=80=99d suggest Ekr, but I know that as an AD his =
time is scarce this week.)

Thanks!

Ben.

>=20
> /a
>=20
> On 4/3/18 1:21 PM, Suhas Nandakumar wrote:
>> Adding a data point
>>=20
>> Icebis doesn=E2=80=99t talk about trickle ice and hence ice-sip-SDP =
doesn=E2=80=99t either.
>>=20
>> In the same context, would ice trickle and ice-trickle-sip-SDP =
focussing on trickle ice only procedures and usages makes sense ?
>>=20
>>=20
>> Does that work ?
>>=20
>>=20
>> On Tue, Apr 3, 2018 at 11:04 AM Adam Roach <adam@nostrum.com> wrote:
>> On 4/3/18 12:54 PM, Ben Campbell wrote:
>> >
>> >> On Apr 3, 2018, at 12:43 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>> >>
>> >>
>> >>
>> >> On Tue, Apr 3, 2018 at 10:35 AM, Ben Campbell <ben@nostrum.com> =
wrote:
>> >>
>> >>
>> >>> On Apr 3, 2018, at 12:26 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>> >>>
>> >>> I don't think #3 is acceptable. AFAIK JSEP has no other =
dependencies on SIP. If you think #2 and #3 are equally awkward, lets do =
#2.
>> >>>
>> >> I said they are equally awkward (by which I mean equally awkward =
for readers after publication), but 3 requires fewer changes (that is, =
less effort.).
>> >>
>> >> If we want to go for least awkward, that probably means a separate =
trickle-ice-sdp draft in parallel to the ice sdp draft. But that=E2=80=99s=
 the past of most effort.
>> >>
>> >> But honestly, I think this is the sort of point that we should =
defer to WG consensus.
>> >>
>> >> Which WG? As I understand it, this would require a change to JSEP, =
which would also require WG consensus, plus a change to an IESG-approved =
document.
>> >
>> > I mean consensus of the WGs producing the documents. it=E2=80=99s =
quite reasonable for a dependent WG to offer feedback, but I don=E2=80=99t=
 think a dependent WG gets to just override that consensus.
>>=20
>> I don't think it's as clean cut as that. JSEP could have defined the
>> "a=3Dend-of-candidates" syntax, and certainly would have if MMUSIC =
and ICE
>> had pulled it out of their documents. But I don't think we want both
>> documents independently registering identical syntaxes with identical
>> meanings, right? Or I suppose JSEP could have decided -- having =
finished
>> first -- that they should define the syntax and have the =
trickle-ice-sip
>> document reference JSEP?
>>=20
>> I'm offering those up as examples, not proposals. I think the first =
is a
>> nonstarter, and the second is... well, it's as awkward as what you're
>> proposing.
>>=20
>> I'm beginning to think we need to to take the question to ART rather
>> than the three working groups.
>>=20
>> /a
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>=20


--Apple-Mail=_ED5E25F7-8FAC-49FF-92D7-180512CF7808
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrD1zwACgkQgFZKbJXz
1A0K9w//R89RIGaomYmvm/2UeSPSunfm3nMeOkEDmqGFgMlZrIg2orHim+DOvWXF
a4skwAnf18KnC0GncSup5V6T7DFUBtWL73mgBpuwhJugCCLdZFekL9mNeuyVbWAt
MyZDROE11Q+WI4XneCX6Fguv0DSxVglsMtvyfSYYvsYH7fAqVngYjhDnzA5uf2BW
EItlXajYqTERZyzZD9bjsakJUuB0kbf3Kah+WS0ENtsrCgLESJ9124+r9E7B6jiW
1byMSuDDIY1O0oVDpZImGuIos6h+xVmIxuMd1ZkWxM6JpmR9xTECMb8kmx+eQoaP
XVIHpOa4BIhU+EkZEEwsHP0Lur5eP+3aknh8Bg3fdOACqb/IQrnqRkSpz/VGb9j0
cA5eQnjmY6h9L6Z3dknb/Q0SnJQ2SpUV3WHjbSn3zjeoSBBDlwrprHn1qRofw1Wh
cl8kab4UNnmfX67lb+i+fy2TQw3flA8U2PtSdqmlU/+aGbbMQFQBWLv7WhCyx+6g
AZ2XKBMcc0KzG89WB4UdNlGyloGpd/qSSfCMXoHhTPPAJSeotDmJlsJ5BlBjgVKg
8GJ86UIftcd0/MAow+n4MAxoin4iB1h93XqxKY983DidjoCGvyhQ6sR6r1hNJFNo
qOJnhMS45neWvtG7Z4h3oUmlfcC1zdQhOKd9yYtSW+kxHDhfK+8=
=++aR
-----END PGP SIGNATURE-----

--Apple-Mail=_ED5E25F7-8FAC-49FF-92D7-180512CF7808--


From nobody Tue Apr  3 13:12:33 2018
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 642E612D876 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 13:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level: 
X-Spam-Status: No, score=-4.32 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBie5diIEdrZ for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 13:12:30 -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 5661212D86C for <mmusic@ietf.org>; Tue,  3 Apr 2018 13:12:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522786348; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=baPLodCsgz6QszvzwuHZczTKUetnJbc3AxyHV8MXy0M=; b=fP9Y8ipinDs8xzDFQ2Wpnbl/WebmQ0UD65w0eDbikEd0in5UFMA/lb60jfJDnggg Ce/lraPXZ9cgvGq/affFnfZ4QP8KNTmUf5gssQ+H2uPniWq5BjsmAZxoB2G+TZWF xmiWdX3twNJ/x9dz2RAzARTPy5Sx0JoIBi2LJtLLU9I=;
X-AuditID: c1b4fb2d-e19ff700000073d9-62-5ac3e02c68c6
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id B5.6D.29657.C20E3CA5; Tue,  3 Apr 2018 22:12:28 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Tue, 3 Apr 2018 22:12:27 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Adam Roach <adam@nostrum.com>, "Roman Shpount" <roman@telurix.com>, Peter Saint-Andre <stpeter@mozilla.com>
CC: Suhas Nandakumar <suhasietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAABSyAgAAB8QCAABJGAIAAJ6xw
Date: Tue, 3 Apr 2018 20:12:27 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E4424B@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <0503b397-787a-a0de-15aa-dc6dee57a4f8@nostrum.com> <9AE05B60-9E8E-42C8-B114-3A92A0186604@nostrum.com>
In-Reply-To: <9AE05B60-9E8E-42C8-B114-3A92A0186604@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJIsWRmVeSWpSXmKPExsUyM2K7uq7Og8NRBvtey1rs+buI3WJ+52l2 ix9rlzNbrHh9jt3i/QVdi28Xai1m/JnIbHF+53omi6nLH7NYzLgwldli7b92dotnK08xWuyc 28HswOsx5fdGVo+ds+6yeyxZ8pPJo+9AF6vHrJ1PWDwmP25j9rg1pSCAPYrLJiU1J7MstUjf LoEr48GMt6wF+xQrrs5ew9LAeEGhi5GTQ0LAROLjuZlsXYxcHEICRxglrly7yg7hLGaUeLJr DmsXIwcHm4CFRPc/bZC4iMBERolPM4+AFTELtDBL3Pv+kR1klLBAgcTGOa1sILaIQKHE2h2P 2ECaRQTyJA4eFAYJswioSKz7vp4JxOYV8JX4tn8NE8SyU6wSv5c2gM3hFLCXuDrxBguIzSgg JvH91BqwBmYBcYlbT+YzQZwtILFkz3lmCFtU4uXjf6wQtpLE0/9LmED2MgtoSqzfpQ/Rqigx pfshO8ReQYmTM5+wTGAUnYVk6iyEjllIOmYh6VjAyLKKUbQ4tbg4N93IWC+1KDO5uDg/Ty8v tWQTIzCCD275rbuDcfVrx0OMAhyMSjy8p+8ejhJiTSwrrsw9xCjBwawkwquwGSjEm5JYWZVa lB9fVJqTWnyIUZqDRUmcV2/VnighgfTEktTs1NSC1CKYLBMHp1QDo1rDQ4NNhTcMnoSU+T4U LJDbXsJt4rHoVNxGjunXz21vrvM5lBo65bK88tR/RtvWFGa0FF1b8J2n+tfzukd5BfZCHB5X Zu5pDIm74mhRzjpf4yrHolv/VnmLX//sycF3uMde7u7aeMcWefYLipNcJzMzchxnc9vt53mg 0CBpitzkv3aOPheuKLEUZyQaajEXFScCAJNWe9bcAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2sSRsmL-JruWbHr_TPkl-Uwz3lA>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 20:12:32 -0000

SGksDQoNCj4+IExpa2UgSSBzYWlkIG9yaWdpbmFsbHksIG5vbmUgb2YgdGhlc2UgYXJlIHBhcnRp
Y3VsYXJseSBjbGVhbi4gWW91ciBwcm9wb3NhbCBwb2ludHMgdG93YXJkcyBlaXRoZXIgIzEgb3Ig
IzMsIGFuZCBJIGhpZ2hsaWdodGVkIHRoZWlyIGRyYXdiYWNrcyBpbiBteSBvcmlnaW5hbCBtZXNz
YWdlLg0KPj4gDQo+PiBGdW5kYW1lbnRhbGx5LCB0aGUgc3VnZ2VzdGlvbiBCZW4gbWFkZSBpcyB0
aGUgb25seSBjbGVhbiBvbmU6IHNwbGl0IHRyaWNrbGUtaWNlLXNpcCBpbnRvIHR3byBkb2N1bWVu
dHM6IG9uZSBkZWFscyB3aXRoIA0KPj4gU0lQICh0aGluayBhIHBhcmFsbGVsIHRvIFJGQyAzMjYx
KSB3aGlsZSB0aGUgb3RoZXIgZGVhbHMgd2l0aCBTRFAgKHRoaW5rIGEgcGFyYWxsZWwgdG8gUkZD
IDMyNjQpLiBCdXQgSSBhbHNvIGFncmVlIHdpdGggaGltIA0KPj4gdGhhdCBzZW5kaW5nIHRoZSBk
b2N1bWVudCBiYWNrIHRvIHRoZSBXRyBmb3Igc3VjaCBhIHNwbGl0IHdvdWxkIGludHJvZHVjZSBh
IHNpZ25pZmljYW50IGFtb3VudCBvZiB3b3JrLg0KPj4gDQo+PiBBYnNlbnQgdGhhdCwgd2UgbmVl
ZCB0byBwaWNrIHdoaWNoIHdhcnQgd2UncmUgZ29pbmcgdG8gYWNjZXB0Lg0KPg0KPiBSb21hbiBz
dWdnZXN0ZWQgaW4gYSBzZXBhcmF0ZSB0aHJlYWQgYnJhbmNoIHRoYXQgdGhlcmUgaXMgbW9yZSB0
byB0aGlzIHRoYW4ganVzdCAiYT1lbmQtb2YtY2FuZGlkYXRlc+KAnS4gUm9tYW4gc2FpZDoNCj4N
Cj4gSXQgaXMgbm90IGp1c3QgZW5kLW9mLWNhbmRpZGF0ZXMsIGJ1dCBhbHNvIHN1cHBvcnQgZm9y
IGM9MC4wLjAuMCBpbiBvZmZlcnMsIFNEUCBvZmZlcnMgd2l0aG91dCB0aGUgY2FuZGlkYXRlcywg
ZGlmZmVyZW50IG1pc21hdGNoIA0KPiBydWxlcy4gQXMgaXQgc3RhbmRzLCBkcmFmdC1pZXRmLW1t
dXNpYy10cmlja2xlLWljZS1zaXAgY2hhbmdlcyBob3cgZHJhZnQtaWV0Zi1tbXVzaWMtaWNlLXNp
cC1zZHAgd29ya3Mgd2hlbiB0cmlja2xlIElDRSBpcyB1c2VkLg0KPg0KPuKApiBhbmQgYWxzbyDi
gKYNCj4NCj4gRm9yIGluc3RhbmNlIGN1cnJlbnQgaW4gZHJhZnQtaWV0Zi1ydGN3ZWItanNlcC0y
NCAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtcnRjd2ViLWpzZXAtMjQj
c2VjdGlvbi01LjIuMSk6DQo+IA0KPiBJZiB0aGUgbT0gc2VjdGlvbiBpcyBtYXJrZWQgYXMgYnVu
ZGxlLW9ubHksIHRoZW4gdGhlIHBvcnQgdmFsdWUgTVVTVCBiZSBzZXQgdG8gMC4gIE90aGVyd2lz
ZSwgdGhlIHBvcnQgdmFsdWUgaXMgc2V0IHRvIHRoZSBwb3J0IA0KPiBvZiB0aGUgZGVmYXVsdCBJ
Q0UgY2FuZGlkYXRlIGZvciB0aGlzIG09IHNlY3Rpb24sIGJ1dCBnaXZlbiB0aGF0IG5vIGNhbmRp
ZGF0ZXMgYXJlIGF2YWlsYWJsZSB5ZXQsIHRoZSAiZHVtbXkiIHBvcnQgdmFsdWUgb2YgDQo+IDkg
KERpc2NhcmQpIE1VU1QgYmUgdXNlZCwgYXMgaW5kaWNhdGVkIGluIFtJLUQuaWV0Zi1pY2UtdHJp
Y2tsZV0sIFNlY3Rpb24gNS4xLg0KPiANCj4gSSBhbSBmYWlybHkgc3VyZSB0aGlzIGlzIG5vIGxv
bmdlciBpbiBpZXRmLWljZS10cmlja2xlICBhbmQgd2FzIG1vdmVkIHRvIGRyYWZ0LWlldGYtbW11
c2ljLXRyaWNrbGUtaWNlLXNpcCANCj4gKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLW1tdXNpYy10cmlja2xlLWljZS1zaXAtMTQjc2VjdGlvbi00LjEuMSkuDQoNCkluIGFk
ZGl0aW9uIHRvIHRoYXQsIGRyYWZ0LWlldGYtbW11c2ljLXRyaWNrbGUtaWNlLXNpcCBhbHNvIGRl
ZmluZXMgdGhlIFNEUCB1c2FnZSBvZiAiYT1pY2Utb3B0aW9uczp0cmlja2xlIi4gSlNFUCBjdXJy
ZW50bHkgcmVmZXJlbmNlcyBkcmFmdC1pZXRmLWljZS10cmlja2xlIHJlZ2FyZGluZyB1c2FnZSBv
ZiB0aGUgYXR0cmlidXRlIChzZWUgYmVsb3cpLCBidXQgdGhlIG9ubHkgdGhpbmcgZHJhZnQtaWV0
Zi1pY2UtdHJpY2tsZSBkb2VzIGlzIHJlZ2lzdGVyaW5nIHRoZSAidHJpY2tsZSIgdG9rZW4uIA0K
DQpFeGFtcGxlczoNCg0KU2VjdGlvbiA1LjIuMSBzYXlzOg0KDQoibyAgQW4gImE9aWNlLW9wdGlv
bnMiIGxpbmUgd2l0aCB0aGUgInRyaWNrbGUiIG9wdGlvbiBNVVNUIGJlIGFkZGVkLA0KICAgICAg
YXMgc3BlY2lmaWVkIGluIFtJLUQuaWV0Zi1pY2UtdHJpY2tsZV0sIFNlY3Rpb24gNC4iDQoNClRo
ZXJlIGlzIG5vIHRleHQgYWJvdXQgdGhlICJ0cmlja2xlIiBvcHRpb24gaW4gU2VjdGlvbiA0IG9m
IGRyYWZ0LWlldGYtaWNlLXRyaWNrbGUuDQoNCg0KU2VjdGlvbiA1LjIuMSBhbHNvIHNheXM6DQoN
CiAgICAgICJJZiB0aGUgbT0gc2VjdGlvbiBpcyBtYXJrZWQgYXMgYnVuZGxlLW9ubHksIHRoZW4g
dGhlIHBvcnQgdmFsdWUNCiAgICAgIE1VU1QgYmUgc2V0IHRvIDAuICBPdGhlcndpc2UsIHRoZSBw
b3J0IHZhbHVlIGlzIHNldCB0byB0aGUgcG9ydCBvZg0KICAgICAgdGhlIGRlZmF1bHQgSUNFIGNh
bmRpZGF0ZSBmb3IgdGhpcyBtPSBzZWN0aW9uLCBidXQgZ2l2ZW4gdGhhdCBubw0KICAgICAgY2Fu
ZGlkYXRlcyBhcmUgYXZhaWxhYmxlIHlldCwgdGhlICJkdW1teSIgcG9ydCB2YWx1ZSBvZiA5DQog
ICAgICAoRGlzY2FyZCkgTVVTVCBiZSB1c2VkLCBhcyBpbmRpY2F0ZWQgaW4gW0ktRC5pZXRmLWlj
ZS10cmlja2xlXSwNCiAgICAgIFNlY3Rpb24gNS4xLiINCg0KLi4uYW5kOg0KDQogICAiVGhlIG09
IGxpbmUgTVVTVCBiZSBmb2xsb3dlZCBpbW1lZGlhdGVseSBieSBhICJjPSIgbGluZSwgYXMgc3Bl
Y2lmaWVkDQogICBpbiBbUkZDNDU2Nl0sIFNlY3Rpb24gNS43LiAgQWdhaW4sIGFzIG5vIGNhbmRp
ZGF0ZXMgYXJlIGF2YWlsYWJsZQ0KICAgeWV0LCB0aGUgImM9IiBsaW5lIG11c3QgY29udGFpbiB0
aGUgImR1bW15IiB2YWx1ZSAiSU4gSVA0IDAuMC4wLjAiLA0KICAgYXMgZGVmaW5lZCBpbiBbSS1E
LmlldGYtaWNlLXRyaWNrbGVdLCBTZWN0aW9uIDUuMS4iDQoNClRoZXJlIGlzIG5vIHRleHQgYWJv
dXQgZHVtbXkgdmFsdWVzIChwb3J0cyBvciBhZGRyZXNzZXMpIGV0YyBpbiBTZWN0aW9uIDUuMSBv
ZiBkcmFmdC1pZXRmLWljZS10cmlja2xlLg0KDQpTaW1pbGFyIHRleHQgZXhpc3RzIGZvciB0aGUg
YW5zd2VyIGluIHNlY3Rpb24gNS4zLjEuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Tue Apr  3 13:41:35 2018
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 EC731128C0A; Tue,  3 Apr 2018 13:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k50qt1Wna9Wo; Tue,  3 Apr 2018 13:41:31 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c: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 0A66A12706D; Tue,  3 Apr 2018 13:41:30 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id d201so6676446vke.0; Tue, 03 Apr 2018 13:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jnqQ3AS0Vc0Jd/S6psKReE5OAtSHnvUtdevBMf83534=; b=QQDUUNFE0DV/Jo908Hbtye0VMz6SYPMwd++jj4mvIW69Ks55fqR8NPabM405oXgXpw e52ywdCPblWgdxC6HiGFF8UIcFKnsyYmcfywdN/rimHeF0tHGC5womK0D+khx1LknPTA xjNBZwfaMzDzc3qzH/HqSfvWK7mcXkesbLDILqhvtXkbU37XmNtavvOEEFa3AU43lZhk GfbmgUsvGarJORpgkl6tGqdY37OyJq0u7AYl8hL3OWMGKizQwSHEeUswdVNM6/6e3c4s LVEIgP8uKNSpiHSdSCN/vGa8V4daJRagyf3HxhGGm9kL+Vjw0b7VamLZkBxdwKGkAUDR QyZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jnqQ3AS0Vc0Jd/S6psKReE5OAtSHnvUtdevBMf83534=; b=D6fpxIntzIIUo4R+2nU66A3QUTAOUfcUvgWioGt1geN7y8wpMN8J7VMgtX3joycr1F yndzwI34lI32QQ0As69z6WBCe9+/23j5ISVetTjU38Na4n1FaeBKxJt0jdRuoyaailza oktfnOVnDf/NlAwGnqTgAIGTmzuNkXOt3sV3Q1CiwZdA0ijeEIOMElA2EAlKo8eHc5iQ 03GmiSWfdMmekIW7KvCYSh6LgmwPXgbVV4h+v/gFRojYuo9mVHKAEM/ZM49f67dmWkPx LcGvcLiWpkp9Dfl/EJTSfJpOB59WLm35mzviunKoFQc2qToHOvaTaLq96hh4/Z1b8346 6I+Q==
X-Gm-Message-State: ALQs6tAVjZnx+ViLwx9yStCWzl/tm7eNsWIJ8Nm3Fo7FWLDaWdNjGP6W 35wUs6ku6TELn2FVhOInP7Xe8MkROX4tAG9DeJQ=
X-Google-Smtp-Source: AIpwx49+MgG/kU1DwQwRSyHmvu1tHKid2ILoLswSOR+e3walVx0mskpirKxc4H5MiiniaFy3m5ZjqgV5iOrdgJz2Ly8=
X-Received: by 10.31.140.196 with SMTP id o187mr5712588vkd.4.1522788089811; Tue, 03 Apr 2018 13:41:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Tue, 3 Apr 2018 13:41:29 -0700 (PDT)
In-Reply-To: <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 3 Apr 2018 13:41:29 -0700
Message-ID: <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Peter Saint-Andre <stpeter@mozilla.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>,  mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>,  Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>,  The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
Content-Type: multipart/alternative; boundary="001a1142637829567c0568f7bb27"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/csQLMuEVr1QMDCVm9_ZFk0mhsOY>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 20:41:33 -0000

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

On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com> wrote:

>
>
> > On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com>
> wrote:
> >
> > On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
> >> Just to complete, ice-bis doesn=E2=80=99t normatively reference ice-si=
p-SDP
> >> draft when it moved to using =E2=80=9Cusages =E2=80=9C indirections fo=
r signaling
> protocols.
> >>
> >>
> >> Trickle ice can use similar approach and refer to trickle-sip as usage
> >> for trickle.
> >
> > It already does. That's why we pulled all the SDP/SIP stuff out of
> > draft-ietf-ice-trickle.
>
> I assume Suhas meant separating the SDP stuff from the SIP stuff. (I also
> assume he will correct me if I am wrong.)
>
>
That's right Ben .. I was just thinking minimal localized changes (thus
small time to get new draft done) and then asking trickle, trickle-sip to
refer to the new one. (work done to refer is much smaller for these drafts
that are at the very end of approval journey)

I do agree with Adam, no matter what version of the proposal we pick, there
is some work that needs to be done and we
should do it.



> Thanks,
>
> Ben.
>
>

--001a1142637829567c0568f7bb27
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 Tue, Apr 3, 2018 at 12:22 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"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
&gt; On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre &lt;<a href=3D"mailto:st=
peter@mozilla.com">stpeter@mozilla.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 4/3/18 12:27 PM, Suhas Nandakumar wrote:<br>
&gt;&gt; Just to complete, ice-bis doesn=E2=80=99t normatively reference ic=
e-sip-SDP<br>
&gt;&gt; draft when it moved to using =E2=80=9Cusages =E2=80=9C indirection=
s for signaling protocols.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Trickle ice can use similar approach and refer to trickle-sip as u=
sage<br>
&gt;&gt; for trickle.<br>
&gt;<br>
&gt; It already does. That&#39;s why we pulled all the SDP/SIP stuff out of=
<br>
&gt; draft-ietf-ice-trickle.<br>
<br>
</span>I assume Suhas meant separating the SDP stuff from the SIP stuff. (I=
 also assume he will correct me if I am wrong.)<br>
<br></blockquote><div><br></div><div>That&#39;s right Ben .. I was just thi=
nking minimal localized changes (thus small time to get new draft done) and=
 then asking trickle, trickle-sip to=C2=A0</div><div>refer to the new one. =
(work done to refer is much smaller for these drafts that are at the very e=
nd of approval journey)</div><div><br></div><div>I do agree with Adam, no m=
atter what version of the proposal we pick, there is some work that needs t=
o be done and we</div><div>should do it.</div><div>=C2=A0</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
Thanks,<br>
<br>
Ben.<br>
<br>
</blockquote></div><br></div></div>

--001a1142637829567c0568f7bb27--


From nobody Tue Apr  3 13:42:39 2018
Return-Path: <Linda.dunbar@huawei.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 3CAD312D879; Tue,  3 Apr 2018 13:41:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar <Linda.dunbar@huawei.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152278809420.22755.15521672481164240628@ietfa.amsl.com>
Date: Tue, 03 Apr 2018 13:41:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/flU-7uKRiZsUf9oNhGiN15SvREo>
Subject: [MMUSIC] Genart telechat review of draft-ietf-mmusic-sdp-bundle-negotiation-49
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 03 Apr 2018 20:41:34 -0000

Reviewer: Linda Dunbar
Review result: Ready

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

For more information, please see the FAQ at

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

Document: draft-ietf-mmusic-sdp-bundle-negotiation-??
Reviewer: Linda Dunbar
Review Date: 2018-04-03
IETF LC End Date: 2018-02-14
IESG Telechat date: 2018-04-19

Summary:
The document is written very clear, easy to understand even for people like me
who is not an expert in the media transport. A dump question, is "media
description" same as a "media flow"? Is it always one to one mapping?

Major issues: None

Minor issues: None

Nits/editorial comments:



From nobody Tue Apr  3 20:44:39 2018
Return-Path: <worley@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 49A7D126C89 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 20:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.686
X-Spam-Level: 
X-Spam-Status: No, score=-1.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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 yZVaFy5M3AYK for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 20:44:36 -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 153EA126CD8 for <mmusic@ietf.org>; Tue,  3 Apr 2018 20:44:36 -0700 (PDT)
Received: from resomta-ch2-15v.sys.comcast.net ([69.252.207.111]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id 3ZLafRQowrSBO3ZLefYfuS; Wed, 04 Apr 2018 03:44:34 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-15v.sys.comcast.net with SMTP id 3ZLdfSSOjA1BJ3ZLef0k5P; Wed, 04 Apr 2018 03:44:34 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w343iXDM001427; Tue, 3 Apr 2018 23:44:33 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w343iWeo001424; Tue, 3 Apr 2018 23:44:32 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Adam Roach <adam@nostrum.com>
Cc: iesg@ietf.org, fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
In-Reply-To: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> (adam@nostrum.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 03 Apr 2018 23:44:32 -0400
Message-ID: <874lkr3aan.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfAovv8f5dkvvQJfs1Rl1mQtsVEZbQM7yv5LYq5HpQqDxttbqRhM4ky1420+c+HF5jOMh3Jheoz56f1SZ33uVqhhdrsuo2AcGEHwg2gCNyaO064TCE7+Y LcWdcq33Dd4N6+KgigTs8Z2Fd2fAi1aA8vIS9+prmtnBsfq36WMXUpGL7a5m9hqR8+dA807MZBwDcI/niDAaZhX43ktnKxfDFEXWBf3ET9WkdPtrekzK9L57 5YR/VS6qjMB+zjkdqHcGg1AMFJaG0GFqJ/vEwf9wsnlCDvS5jR5y7YiVM63IXB09cktM6qaBAB8pNjiwxOyDXFkqTyobEqyxA4SMpWnwKYU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8Pc3dO3pyPfD_t_D1bF4igypW5Y>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 03:44:37 -0000

Adam Roach <adam@nostrum.com> writes:
> The second issue doesn't necessarily pertain to this document per se as much
> as it does the interaction among this document, draft-ietf-ice-trickle (Trickle
> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep
> (JSEP). The problem doesn't lie with any single document, but in the overall
> result of how they're currently structured.
>
> JSEP (in the RFC editor queue) refers to the "a=end-of-candidates" SDP attribute
> as appearing in Trickle ICE, section 9.3, which was true at one point in time.
> Somewhere along the line, this attribute's definition was moved from there
> into this document.

It seems to me that the problem is that the documents have these
combinations of topics:

    ice-trickle
    ice-sdp-sip
    ice-trickle-sdp-rtcweb
    ice-trickle-sdp-sip

and that the definition of "a=end-of-candidates" is in the domain
ice-trickle-sdp.  Viz., the only documents that include both ice-trickle
and sdp include either rtcweb or sip.  As such, there is no document in
which to place the definition of the attribute on which the documents
that need the attribute can nicely depend.

As Roman says, there's a bunch of "trickle ICE specific SDP related
changes", and they need to go into a document with topic
ice-trickle-sdp.  You could avoid having an additional document by
putting them in an "SDP topics" section of ice-trickle (the section is
ice-trickle-sdp), but Peter notes "IMHO the ICE WG had consensus to
remove all normative SDP references from draft-ietf-ice-trickle and
place them in draft-ietf-mmusic-trickle-ice-sip."

Dale


From nobody Tue Apr  3 21:24:14 2018
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 DB918126CE8 for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 21:24:12 -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 IUEMrt_JAFYW for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 21:24:10 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::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 D5369124207 for <mmusic@ietf.org>; Tue,  3 Apr 2018 21:24:09 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id r184so11579909vke.11 for <mmusic@ietf.org>; Tue, 03 Apr 2018 21:24:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Tky+jP4j7UN12d+Qca5A9MC9VZwSeKrAJ/yn47pDCug=; b=A0Qmaosc31UWK5z6jLaJi+7XmjYZI7MYQ3L1pHBSXzsnMlpFyua2gKsYkmKjYDVlQ4 53M5wkoiCz2kCABJ2URflZygNjONVN9CD0voz1tYUjpPsBEQrfMmQv3xKm1J/lLktg4+ 3mGRZ8sEPKVJQYLXbmKgbM/InxjiFATNaa+zE0IKt9TTMY3NagB2opEfqEXw1Z41N8cd Vwqbmi5ioiRwCZKWltwQvFITTV88fPvbubqJTM1cB6ojFizubNftfzuxv5Wg8wDghs2e OdA9CY5KGA5ha8b/efifHelcVYPW5ucDHRLxG4OKlY4tDxmvs8MjduXSX8+odt/k9KG2 CXxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Tky+jP4j7UN12d+Qca5A9MC9VZwSeKrAJ/yn47pDCug=; b=XYn1wlv40BYSwWIok0B/Xoaz05XlIOKrtNkV2Ub0+Yj6tRlio+dR4Ok4tBPWQBMDNY 6Up5xkNj7TA9e0J27gT06p05wX+C9Qxq/HM1nyDvdLyYFN6zSBFDAt8T1E2t5u9xUfgP v5KcJEV4h6wxZMaVP2pVi199CuzX/NS3I7sXbYJ1UFeg57GUkcwhkbfYQLLGvBPdCSOe aD83VURjIRqL6Ox2s3kX8CjRRYY2GwsAPKpo4Ef4JsZ2V+3YI+Mex6rxAIHYrFlJ1GgX u1u7VCM8m5p7uAohP9XN4i9NIHL8L/hj4/BlvzQHYBGZa0VFgrJkDXaWLDIKZ5QM9+Ti MZ3w==
X-Gm-Message-State: ALQs6tAg4YGq/mDNzxSfuZycfuT5K6Nk108OXujUntNB52fh79pQkeR0 mBJP1h+DlgZBGMJb7STQvWVR/ZNxqT0e6YkcMmA=
X-Google-Smtp-Source: AIpwx48iV3HBKI/nI38nlflDxNg1VRekuGkpmz8FmMSAbGs72e56Pp129Jqh4+El6LMPxU4avwNHzDqRyQAumYySCE4=
X-Received: by 10.31.177.141 with SMTP id a135mr9602263vkf.88.1522815848857; Tue, 03 Apr 2018 21:24:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Tue, 3 Apr 2018 21:24:08 -0700 (PDT)
In-Reply-To: <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com> <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Tue, 3 Apr 2018 21:24:08 -0700
Message-ID: <CAMRcRGQZnWytKkap9kXPh0Zq4fJXmwArvPny0fNK5KWYJ=uThA@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c02970bac55d0568fe31f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XLVJY9tz37N_uYa7LHnoWsCGwcQ>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 04:24:13 -0000

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

Hello Flemming


On Tue, Apr 3, 2018 at 12:29 AM, Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Hello Flemming
>
>   The original text was take from RFC5245 sections https://tools.ietf.
> org/html/rfc5245#section-5.1 and 6.1 where it is defines procedures for
> answerer and the offerer for verifying ice support. The versions pre 13 for
> the current ice-sip-sdp had the exact same content.
>
> Wondering if we should get back to the original format since it seems to
> be more clearer in explaining ?
>


Any thoughts on this proposal ? please let me know

>
>
> Thanks
> Suhas
>
>
> On Mon, Apr 2, 2018 at 4:45 PM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
>
>> I'm still having a hard time following this - let me try and elaborate
>> below
>>
>> On 4/2/18 1:56 PM, Suhas Nandakumar wrote:
>>
>> Hi Flemming
>>
>> Moving the discussion in a separate thread to keep it focussed. How about
>> following rewording of the section 3.2.5.
>>
>>   3.2.5 <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5>.  Verifying ICE Support
>>
>>    The agents will proceed with the ICE procedures defined in [ICE-BIS <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>]
>>    and this specification if, for each data stream in the SDP it
>>    received, the default destination for each component of that data
>>    stream appears in a candidate attribute.  For example, in the case of
>>    RTP, the IP address and port in the "c=" and "m=" lines,
>>    respectively, appear in a candidate attribute and the value in the
>>    rtcp attribute appears in a candidate attribute.
>>
>> So far so good.
>>
>>    If this condition is not met, the agents MUST process the SDP based on
>>    normal [RFC3264 <https://tools.ietf.org/html/rfc3264>] procedures, without using any of the ICE mechanisms
>>    described in the remainder of this specification with the following
>>    exceptions:
>>
>> Ok, so at this point, there is mismatch between at least one default
>> destination in a component and all of its corresponding candidate
>> attributes. The above says to do normal offer/answer instead of ICE, except
>> as follows:
>>
>>    1.  An controlled/responding agent MUST follow the rules of
>>
>>        section 11 of [ICE-BIS <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>], which describe keepalive procedures
>>
>>        for all agents.
>>
>> Earlier, the document says the answerer acts as the responding agent, and
>> the controlling/controlled roles are determined by ICE procedures. Here you
>> seem to say responding = controlled. In any case, it must mean we are
>> dealing with the answerer (which would be easiser to understand from an O/A
>> point of view which is the perspective this documenet should have to the
>> extent possible).
>>
>> So it says, the answer will still follow the keep-alive procedures, but
>> we are not doing ICE. I'm not quite sure what that means, but I'm guessing
>> it means we must stop sending keepalives if we were previously sending them
>> (since the ICE session is terminated).
>>
>> Also, If the default candidates were relayed
>>
>>        candidates learned through a TURN server, the controlled agent
>>
>>        MUST create permissions in the TURN server for the IP addresses
>>
>>        learned from its peer in the offer SDP it just received.
>>
>>        If this is not done, initial packets in the data stream from the
>>
>>        peer may be lost.
>>
>> Here it's not entirely clear whether this is a rule for the offerer or
>> the answerer:
>> 1) Answerer
>> The default candidates were present in the offer and apparently they are
>> marked as relayed candidates. However, since the text refers to controlled,
>> per the above, this cannot be test for the answerer.
>>
>> 2) Offerer
>> This must be an answer SDP that came back to us, however the text clearly
>> talks about the offer SDP.
>>
>> I'm confused at this point.
>>
>>    2.  On the other hand, if the controlled agent is not proceeding
>>
>>        with ICE because there were a=candidate attributes, but none that
>>
>>        matched the default destination of the data stream, it MUST include
>>
>>        an a=ice-mismatch attribute in its answer and MAY omit a=candidate
>>        attributes for such data streams.
>>
>> Above you said this list was supposed to be exceptions to this rule, but
>> this is the rule itself repeated !?
>>
>> Let me know if I am missing something here (but in either case, we need
>> to make the write-up clearer).
>>
>>
>> Thanks
>>
>> -- Flemming
>>
>>  See Section 9.2.2 <https://tools.ietf..org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2> for a
>>        discussion of cases where this can happen. This specification provides
>>
>>        no guidance on how an controlled agent should proceed in such a
>>
>>        failure case.
>>
>>
>>
>>
>> Cheers
>> Suhas
>>
>>
>> _______________________________________________
>> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>>
>

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

<div dir=3D"ltr">Hello Flemming=C2=A0<div><br></div><div><br></div><div cla=
ss=3D"gmail_extra"><div class=3D"gmail_quote">On Tue, Apr 3, 2018 at 12:29 =
AM, Suhas Nandakumar <span dir=3D"ltr">&lt;<a href=3D"mailto:suhasietf@gmai=
l.com" target=3D"_blank">suhasietf@gmail.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr">Hello Flemming<div><br></div><di=
v>=C2=A0 The original text was take from RFC5245 sections=C2=A0<a href=3D"h=
ttps://tools.ietf.org/html/rfc5245#section-5.1" target=3D"_blank">https://t=
ools.ietf.<wbr>org/html/rfc5245#section-5.1</a> and 6.1 where it is defines=
 procedures for answerer and the offerer for verifying ice support. The ver=
sions pre 13 for the current ice-sip-sdp had the exact same content.=C2=A0<=
/div><div><br></div><div>Wondering if we should get back to the original fo=
rmat since it seems to be more clearer in explaining ?</div></div></blockqu=
ote><div><br></div><div><br></div><div>Any thoughts on this proposal ? plea=
se let me know=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div><br></div><div><br></div><div>Thanks</div><span class=3D"HOEnZb"><font =
color=3D"#888888"><div>Suhas</div><div><br></div></font></span></div><div c=
lass=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Apr 2, 2018 at 4:45 PM, Flemming Andreasen <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fand=
reas@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    I&#39;m still having a hard time following this - let me try and
    elaborate below <br><span>
    <br>
    <div class=3D"m_7105189085525493750m_8509342672748520900moz-cite-prefix=
">On 4/2/18 1:56 PM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial">Hi
          Flemming</div>
        <div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial"><br>
        </div>
        <div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;background-c=
olor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:i=
nitial">Moving
          the discussion in a separate thread to keep it focussed. How
          about following rewording of the section 3.2.5.=C2=A0</div>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"m=
_7105189085525493750m_8509342672748520900gmail-h4" style=3D"line-height:0pt=
;display:inline;white-space:pre-wrap;font-family:monospace;font-size:1em;fo=
nt-weight:bold">
</span></pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"m=
_7105189085525493750m_8509342672748520900gmail-h4" style=3D"line-height:0pt=
;display:inline;white-space:pre-wrap;font-family:monospace;font-size:1em;fo=
nt-weight:bold">
</span></pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class=3D"m=
_7105189085525493750m_8509342672748520900gmail-h4" style=3D"line-height:0pt=
;display:inline;white-space:pre-wrap;font-family:monospace;font-size:1em;fo=
nt-weight:bold"><h4 style=3D"line-height:0pt;display:inline;white-space:pre=
-wrap;font-family:monospace;font-size:1em;font-weight:bold"><a class=3D"m_7=
105189085525493750m_8509342672748520900gmail-selflink" name=3D"m_7105189085=
525493750_m_8509342672748520900_section-3.2.5" href=3D"https://tools.ietf.o=
rg/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5" style=3D"color:blac=
k;text-decoration:none" target=3D"_blank">3.2.5</a>.  Verifying ICE Support=
</h4></span>

   The agents will proceed with the ICE procedures defined in [<a href=3D"h=
ttps://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS" ti=
tle=3D"&quot;Interactive Connectivity Establishment (ICE): A Protocol for N=
etwork Address Translator (NAT) Traversal for Offer/Answer Protocols&quot;"=
 style=3D"color:rgb(17,85,204)" target=3D"_blank">ICE-BIS</a>]
   and this specification if, for each data stream in the SDP it
   received, the default destination for each component of that data
   stream appears in a candidate attribute.  For example, in the case of
   RTP, the IP address and port in the &quot;c=3D&quot; and &quot;m=3D&quot=
; lines,
   respectively, appear in a candidate attribute and the value in the
   rtcp attribute appears in a candidate attribute.
</pre>
      </div>
    </blockquote></span>
    So far so good. <br><span>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   If this condi=
tion is not met, the agents MUST process the SDP based on
   normal [<a href=3D"https://tools.ietf.org/html/rfc3264" title=3D"&quot;A=
n Offer/Answer Model with Session Description Protocol (SDP)&quot;" style=
=3D"color:rgb(17,85,204)" target=3D"_blank">RFC3264</a>] procedures, withou=
t using any of the ICE mechanisms
   described in the remainder of this specification with the following
   exceptions:</pre>
      </div>
    </blockquote></span>
    Ok, so at this point, there is mismatch between at least one default
    destination in a component and all of its corresponding candidate
    attributes. The above says to do normal offer/answer instead of ICE,
    except as follows: <br><span>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   1.  An contro=
lled/responding agent MUST follow the rules of </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       section 1=
1 of [<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-=
19#ref-ICE-BIS" title=3D"&quot;Interactive Connectivity Establishment (ICE)=
: A Protocol for Network Address Translator (NAT) Traversal for Offer/Answe=
r Protocols&quot;" style=3D"color:rgb(17,85,204)" target=3D"_blank">ICE-BIS=
</a>], which describe keepalive procedures </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       for all a=
gents. </pre>
      </div>
    </blockquote></span>
    Earlier, the document says the answerer acts as the responding
    agent, and the controlling/controlled roles are determined by ICE
    procedures. Here you seem to say responding =3D controlled. In any
    case, it must mean we are dealing with the answerer (which would be
    easiser to understand from an O/A point of view which is the
    perspective this documenet should have to the extent possible). <br>
    <br>
    So it says, the answer will still follow the keep-alive procedures,
    but we are not doing ICE. I&#39;m not quite sure what that means, but
    I&#39;m guessing it means we must stop sending keepalives if we were
    previously sending them (since the ICE session is terminated).=C2=A0 <b=
r><span>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Also, If the def=
ault candidates were relayed </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       candidate=
s learned through a TURN server, the controlled agent </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       MUST crea=
te permissions in the TURN server for the IP addresses </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       learned f=
rom its peer in the offer SDP it just received.  </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       If this i=
s not done, initial packets in the data stream from the </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       peer may =
be lost.
</pre>
      </div>
    </blockquote></span>
    Here it&#39;s not entirely clear whether this is a rule for the offerer
    or the answerer:<br>
    1) Answerer<br>
    The default candidates were present in the offer and apparently they
    are marked as relayed candidates. However, since the text refers to
    controlled, per the above, this cannot be test for the answerer.<br>
    <br>
    2) Offerer<br>
    This must be an answer SDP that came back to us, however the text
    clearly talks about the offer SDP. <br>
    <br>
    I&#39;m confused at this point. <br><span>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   2.  On the ot=
her hand, if the controlled agent is not proceeding </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       with ICE =
because there were a=3Dcandidate attributes, but none that </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       matched t=
he default destination of the data stream, it MUST include </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       an a=3Dic=
e-mismatch attribute in its answer and MAY omit a=3Dcandidate
       attributes for such data streams. </pre>
      </div>
    </blockquote></span>
    Above you said this list was supposed to be exceptions to this rule,
    but this is the rule itself repeated !?<br>
    <br>
    Let me know if I am missing something here (but in either case, we
    need to make the write-up clearer). <br>
    <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <blockquote type=3D"cite"><span>
      <div dir=3D"ltr">
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"> See <a href=3D"=
https://tools.ietf..org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2=
" style=3D"color:rgb(17,85,204)" target=3D"_blank">Section 9.2.2</a> for a
       discussion of cases where this can happen. This specification provid=
es </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       no guidan=
ce on how an controlled agent should proceed in such a </pre>
        <pre class=3D"m_7105189085525493750m_8509342672748520900gmail-newpa=
ge" style=3D"font-style:normal;font-variant-ligatures:normal;font-variant-c=
aps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;word-spacing:0px;background-color:rgb(255,255,25=
5);text-decoration-style:initial;text-decoration-color:initial;font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">       failure c=
ase.</pre>
        <br class=3D"m_7105189085525493750m_8509342672748520900gmail-Apple-=
interchange-newline">
        <br>
        <div><br>
        </div>
        <div>Cheers</div>
        <div>Suhas</div>
      </div>
      <br>
      <fieldset class=3D"m_7105189085525493750m_8509342672748520900mimeAtta=
chmentHeader"></fieldset>
      <br>
      </span><pre>______________________________<wbr>_________________
mmusic mailing list
<a class=3D"m_7105189085525493750m_8509342672748520900moz-txt-link-abbrevia=
ted" href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>
<a class=3D"m_7105189085525493750m_8509342672748520900moz-txt-link-freetext=
" href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">h=
ttps://www.ietf.org/mailman/l<wbr>istinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
  </div>

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

--001a11c02970bac55d0568fe31f2--


From nobody Tue Apr  3 22:12:02 2018
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 4FFF3126DED for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 22:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] 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 vM9b4wLozKWC for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 22:11:54 -0700 (PDT)
Received: from mail-pl0-x22d.google.com (mail-pl0-x22d.google.com [IPv6:2607:f8b0:400e:c01::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 B4C201200FC for <mmusic@ietf.org>; Tue,  3 Apr 2018 22:11:52 -0700 (PDT)
Received: by mail-pl0-x22d.google.com with SMTP id s24-v6so12461448plq.6 for <mmusic@ietf.org>; Tue, 03 Apr 2018 22:11:52 -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=EHvP6WbKgoq89u1UnAKfhv6pT5rebMYhku14ZJcYxHc=; b=zKgeLxfdMavkSzrQyCWBIaHaYNllg3fAHFm3U9ngVVoHsWA9JLpDPhExp6hxMl4SEC NM0yNmukDlVqkTgvjfX6ZZbq0u4zb7wjJX3ePoIe1fRdxMSKbgFB2uF+AjA/DaDGGxjE n6CdMxFYF34BWKGIh/hBEQXPXm00ixAlzNnAwKWT8Um8WM3pdqL0Tvpn3mvrfx82TruG w2OYhjH6hORnrLwJdvcJXpYnlpVLNcemz3/TnTSgP2tE8WjmIPy+MmOwcUl+yz1t2zC+ adyoAZTvVfSKPPH/lK3FrzV2w0esm76cLgsO1UG+KA2WHJZBwMxLMT6fvRmQ+HUTQC/y Ho+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EHvP6WbKgoq89u1UnAKfhv6pT5rebMYhku14ZJcYxHc=; b=dy8Ej87CmX+ku+i2/v1vQPtykX361Er7fMcwcP9a0arnkivo5eWa+RE1eC2zcPROY5 +NrhM0O2JfGqc2Aya1QeYWTbGoh1Lh2oYEWrT/LLd4tfsMoVx0HWPphWY/cMOBDiXPfb ec0wVk4tVb+iXSSUCni9rAGwsTKdEFi6opNwZA4BtRfiaVkziPiY+WjrT0Km1jLgzytX wLCQ3UlleKFH54VJQ2qL0sjXf24lvKaH+JANxZFrGuhK7lD0YlwahZJNHETywRqsJIHy 4PWldhyUA5APc3SKFmLFtzBPSiU1M/0HIDPsui1ek4rXLkhglsBBbpta7cA9qg6RbAg4 bd1Q==
X-Gm-Message-State: AElRT7FWbHLYl8fQbrzwv7h28z37zsoAYW+q/8B378cB6egagEgfJt+Z jjWzYtWGwVTGfrRyMjO7igVEmA==
X-Google-Smtp-Source: AIpwx4/M6PuR+gVAyao6kDMQxB78eJ2+re87GK6Dvq9iHzKnclmBx/WyhFKDdSqqIGHpQwdWw0BTqw==
X-Received: by 2002:a17:902:ba87:: with SMTP id k7-v6mr17362315pls.124.1522818712377;  Tue, 03 Apr 2018 22:11:52 -0700 (PDT)
Received: from mail-pl0-f47.google.com (mail-pl0-f47.google.com. [209.85.160.47]) by smtp.gmail.com with ESMTPSA id c186sm2730934pfb.40.2018.04.03.22.11.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 22:11:51 -0700 (PDT)
Received: by mail-pl0-f47.google.com with SMTP id g20-v6so12438660plo.9; Tue, 03 Apr 2018 22:11:50 -0700 (PDT)
X-Received: by 10.98.89.70 with SMTP id n67mr12857493pfb.150.1522818710425; Tue, 03 Apr 2018 22:11:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.185.79 with HTTP; Tue, 3 Apr 2018 22:11:49 -0700 (PDT)
In-Reply-To: <874lkr3aan.fsf@hobgoblin.ariadne.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <874lkr3aan.fsf@hobgoblin.ariadne.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 4 Apr 2018 01:11:49 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsgOLopjF7c2q4hCerjMmtXzZ2CKuauq88pM8v47Z8UsA@mail.gmail.com>
Message-ID: <CAD5OKxsgOLopjF7c2q4hCerjMmtXzZ2CKuauq88pM8v47Z8UsA@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Cc: Adam Roach <adam@nostrum.com>, lemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org,  draft-ietf-mmusic-trickle-ice-sip@ietf.org, IESG <iesg@ietf.org>,  mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a114916f84ad91c0568fedce0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/zh6JneJJtLd9RZrzl9S9CScXht0>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 05:11:55 -0000

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

Dale,

I think the best approach is to treat trickle-ice-sip as an update to
ice-sip-sdp with trickle specific procedures, i.e. make it trickle-ice-sip-sdp.
It seems, no one has a problem that ice-sip-sdp, which deals with both SIP
and SDP specific issues. It should be straight forward to separate generic
SDP issues from SIP specific issues in trickle-ice-sip similar to ice-sip-sdp.
This way we will have nice parallel structure between the base ICE/ICE-SDP
drafts and trickle-ice/tricle-ice-sdp drafts. In any case, I think this
would be cleaner then adding SDP related topics to trickle-ice.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr">Dale,<div><br></div>I think the best approach is to treat =
trickle-ice-sip as an update to ice-sip-sdp with trickle specific procedure=
s, i.e. make it=C2=A0<span style=3D"color:rgb(34,34,34);font-family:arial,s=
ans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;f=
ont-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:st=
art;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px=
;background-color:rgb(255,255,255);text-decoration-style:initial;text-decor=
ation-color:initial;float:none;display:inline">trickle-ice-sip-sdp. It seem=
s, no one has a problem that=C2=A0<span style=3D"color:rgb(34,34,34);font-f=
amily:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligat=
ures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;=
text-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initi=
al;text-decoration-color:initial;float:none;display:inline">ice-sip-sdp, wh=
ich deals with both SIP and SDP specific issues. It should be straight forw=
ard to separate generic SDP issues from SIP specific issues in=C2=A0<span s=
tyle=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;fo=
nt-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font=
-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,25=
5,255);text-decoration-style:initial;text-decoration-color:initial;float:no=
ne;display:inline">trickle-ice-sip similar to=C2=A0<span style=3D"color:rgb=
(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;f=
ont-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;lette=
r-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decor=
ation-style:initial;text-decoration-color:initial;float:none;display:inline=
">ice-sip-sdp. This way we will have nice parallel structure between the ba=
se ICE/ICE-SDP drafts and trickle-ice/tricle-ice-sdp drafts. In any case, I=
 think this would be cleaner then adding SDP related topics to trickle-ice.=
</span></span></span></span><div><span style=3D"color:rgb(34,34,34);font-fa=
mily:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatu=
res:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;t=
ext-align:start;text-indent:0px;text-transform:none;white-space:normal;word=
-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initia=
l;text-decoration-color:initial;float:none;display:inline"><span style=3D"c=
olor:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:=
normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:4=
00;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:no=
ne;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);te=
xt-decoration-style:initial;text-decoration-color:initial;float:none;displa=
y:inline"><span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;f=
ont-size:small;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-in=
dent:0px;text-transform:none;white-space:normal;word-spacing:0px;background=
-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color=
:initial;float:none;display:inline"><span style=3D"color:rgb(34,34,34);font=
-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-lig=
atures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:norma=
l;text-align:start;text-indent:0px;text-transform:none;white-space:normal;w=
ord-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:ini=
tial;text-decoration-color:initial;float:none;display:inline"><br></span></=
span></span></span></div><div><span style=3D"color:rgb(34,34,34);font-famil=
y:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures=
:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text=
-align:start;text-indent:0px;text-transform:none;white-space:normal;word-sp=
acing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;t=
ext-decoration-color:initial;float:none;display:inline"><span style=3D"colo=
r:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:nor=
mal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;=
letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;=
white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-=
decoration-style:initial;text-decoration-color:initial;float:none;display:i=
nline"><span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font=
-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-ca=
ps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inden=
t:0px;text-transform:none;white-space:normal;word-spacing:0px;background-co=
lor:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:in=
itial;float:none;display:inline"><span style=3D"color:rgb(34,34,34);font-fa=
mily:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatu=
res:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;t=
ext-align:start;text-indent:0px;text-transform:none;white-space:normal;word=
-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initia=
l;text-decoration-color:initial;float:none;display:inline">Regards,=C2=A0</=
span></span></span></span></div><div class=3D"gmail_extra"><div><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">_____________<br>Ro=
man Shpount</div></div></div></div>

--001a114916f84ad91c0568fedce0--


From nobody Tue Apr  3 22:15:55 2018
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 3B0941200FC for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 22:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VXzN8ZdhLWj for <mmusic@ietfa.amsl.com>; Tue,  3 Apr 2018 22:15:52 -0700 (PDT)
Received: from mail-pl0-x231.google.com (mail-pl0-x231.google.com [IPv6:2607:f8b0:400e:c01::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 41365126DD9 for <mmusic@ietf.org>; Tue,  3 Apr 2018 22:15:52 -0700 (PDT)
Received: by mail-pl0-x231.google.com with SMTP id s10-v6so10492580plp.0 for <mmusic@ietf.org>; Tue, 03 Apr 2018 22:15:52 -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=zTZC4r3pGWcyp4o6IAqXrpElLUR7C/md5u47proTej0=; b=Iy3RqPvx9tNp6Wu/Swv0U4os8E8DNodTXOhCOsvSe0Zaq6s14GTo0GF3U2y5BEutYR 6hNcOeX+nAqiJFPGRXA7cfzPDiwrp+DjBud8FAXmUxqgdxeHHidOqUEBAO4i4KbzLQYl 3Ybeik5PivHMzeNLHLxO9IgKvxcRpnw9TWTnK/WfqBMgMoD061R9Tz9+piWHC+PpJXz6 fUoUfwqY9YJJPd/9nUnem0vINAciLB0cFp9ULFgm5VMUDfAjeTAx9XHcHivD+7JJCwy8 bLwWP0y9jpT2J5MjToGAQX0C9TzS7M7xAK1U5lSRsKL5U8IL1QKgCLwyJpzFiJC/Sr8y 5xCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zTZC4r3pGWcyp4o6IAqXrpElLUR7C/md5u47proTej0=; b=nMFERf0q9IYBgorVu3SLDWErsOyEM2qAt5M0re5VyWOgWCZOF1arpYyVMeSQhnS+QR aXEBea7IuFOCHSl3QZZcxB84dp9hpw+vv8f3BjBn6d/cB9JJZsjMm/vCfHTb/dlpM0Ot CeD6mSkH7iZc4Bw79BRZ4gGPpgJPZ766WNkqiYLcA1WuxZOkXTbKyjvt7SAvKVI1wyfL vXqX2LaxsE5GNdmmVFe9zTywEJFiAjhOisLdRICMjrpr7m5P3Rn2ypJVRlN3VIMkZ5ah LJkKuXYjvZIFHy/DG+khPHhuKPfeAZ4a07wLaVQ4xXSiVRMkIohHpCIrL+vPy+ByMEpS Gn/Q==
X-Gm-Message-State: AElRT7HXuGwUlZ6efYHF1GyR/WrAwBQiQO4zyHZzuYoBjxowFSCByrmW U30FGlsj7GSY45aBBTi1NtZz9Wtr
X-Google-Smtp-Source: AIpwx49UAW+J971gDz7dSjyKnZy6Z/CZm9G60IRkTN0o6wMo0xZbC58TDIkCbOaTm1R6WcaKV0iL5g==
X-Received: by 10.101.97.205 with SMTP id j13mr10857600pgv.266.1522818951701;  Tue, 03 Apr 2018 22:15:51 -0700 (PDT)
Received: from mail-pl0-f44.google.com (mail-pl0-f44.google.com. [209.85.160.44]) by smtp.gmail.com with ESMTPSA id j188sm7784365pfc.7.2018.04.03.22.15.50 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Apr 2018 22:15:51 -0700 (PDT)
Received: by mail-pl0-f44.google.com with SMTP id x4-v6so12457117pln.7 for <mmusic@ietf.org>; Tue, 03 Apr 2018 22:15:50 -0700 (PDT)
X-Received: by 10.99.98.134 with SMTP id w128mr11018452pgb.217.1522818950652;  Tue, 03 Apr 2018 22:15:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.185.79 with HTTP; Tue, 3 Apr 2018 22:15:50 -0700 (PDT)
In-Reply-To: <CAMRcRGQZnWytKkap9kXPh0Zq4fJXmwArvPny0fNK5KWYJ=uThA@mail.gmail.com>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com> <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com> <CAMRcRGQZnWytKkap9kXPh0Zq4fJXmwArvPny0fNK5KWYJ=uThA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 4 Apr 2018 01:15:50 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuHnOROHnBmT=w4e=PK85BFeNZdTnYNdNZ0J7DJafdSJQ@mail.gmail.com>
Message-ID: <CAD5OKxuHnOROHnBmT=w4e=PK85BFeNZdTnYNdNZ0J7DJafdSJQ@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c11d69a9c6d380568feea0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uN0jb9QOLLLqVlJUJeSv5WrxCTc>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 05:15:54 -0000

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

Hi Suhas,

On Wed, Apr 4, 2018 at 12:24 AM, Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> On Tue, Apr 3, 2018 at 12:29 AM, Suhas Nandakumar <suhasietf@gmail.com>
> wrote:
>
>>   The original text was take from RFC5245 sections https://tools.ietf.or
>> g/html/rfc5245#section-5.1 and 6.1 where it is defines procedures for
>> answerer and the offerer for verifying ice support. The versions pre 13 for
>> the current ice-sip-sdp had the exact same content.
>>
>> Wondering if we should get back to the original format since it seems to
>> be more clearer in explaining ?
>>
>
>
> Any thoughts on this proposal ? please let me know
>

Original text in https://tools.ietf.org/html/rfc5245#section-5.1 should be
updated to accommodate the following two issues :

1. rtcp attribute is now optional
2. ICE implementation MAY choose to ignore ICE mismatch and not examine
address in c= line and rtcp attribute

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr">Hi Suhas,<br><div class=3D"gmail_extra"><br clear=3D"all">=
<div><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature">On W=
ed, Apr 4, 2018 at 12:24 AM, Suhas Nandakumar <span dir=3D"ltr">&lt;<a href=
=3D"mailto:suhasietf@gmail.com" target=3D"_blank">suhasietf@gmail.com</a>&g=
t;</span> wrote:<br></div></div><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote"><span class=3D"">On Tue, Apr 3, 2018 at 12:29 AM, Suhas Nandakum=
ar <span dir=3D"ltr">&lt;<a href=3D"mailto:suhasietf@gmail.com" target=3D"_=
blank">suhasietf@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"><div>=C2=A0 The original text was take from RFC524=
5 sections=C2=A0<a href=3D"https://tools.ietf.org/html/rfc5245#section-5.1"=
 target=3D"_blank">https://tools.ietf.or<wbr>g/html/rfc5245#section-5.1</a>=
 and 6.1 where it is defines procedures for answerer and the offerer for ve=
rifying ice support. The versions pre 13 for the current ice-sip-sdp had th=
e exact same content.=C2=A0</div><div><br></div><div>Wondering if we should=
 get back to the original format since it seems to be more clearer in expla=
ining ?</div></div></blockquote><div><br></div><div><br></div></span><div>A=
ny thoughts on this proposal ? please let me know=C2=A0</div></div></div></=
div></blockquote><div><br></div><div>Original text in=C2=A0<a href=3D"https=
://tools.ietf.org/html/rfc5245#section-5.1" target=3D"_blank" style=3D"colo=
r:rgb(17,85,204);font-family:arial,sans-serif;font-size:small;font-style:no=
rmal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400=
;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none=
;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">htt=
ps://tools.ietf.or<wbr>g/html/rfc5245#section-5.1</a>=C2=A0should be update=
d to accommodate the following two issues :</div><div><br></div><div>1. rtc=
p attribute is now optional</div><div>2. ICE implementation MAY choose to i=
gnore ICE mismatch and not examine address in c=3D line and rtcp attribute<=
/div><div><br></div><div>Regards,</div><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br=
 class=3D"gmail-Apple-interchange-newline">

=C2=A0</div><div>=C2=A0</div></div></div></div>

--94eb2c11d69a9c6d380568feea0a--


From nobody Wed Apr  4 00:00:25 2018
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 6004D1270AE for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 00:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JG3T0vD7dmht for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 00:00: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 6B7421270A7 for <mmusic@ietf.org>; Wed,  4 Apr 2018 00:00:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522825209; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=2KBFhuWGf9b7arxjnztH9IIra74/lFj2yURLRkW3hNI=; b=UZGmkm0CFoV+sz5WsYyvWsw40yNDcK0Zy5zjB7g8juYO8lY/+3WNK5KUwmRLdTGw liLNtNrsnWj594iPVEnrF/A+PlnA0sRvARU4PBZbroDOkX0qwR8/2/TRmlQifWGt T6ag+Xoa8Tal/KuKMPYDfRtlnSLOqQI0GXjWYUX1c+s=;
X-AuditID: c1b4fb3a-e21ff70000005d56-6c-5ac477f84d90
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id EC.72.23894.8F774CA5; Wed,  4 Apr 2018 09:00:09 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0382.000; Wed, 4 Apr 2018 09:00:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Linda.dunbar@huawei.com" <Linda.dunbar@huawei.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Genart telechat review of draft-ietf-mmusic-sdp-bundle-negotiation-49
Thread-Index: AQHTy4wpEXvS278d80WaMvzUkmdiaKPviVYA///hmQCAANQ+gA==
Date: Wed, 4 Apr 2018 07:00:07 +0000
Message-ID: <D6EA51DD.2D839%christer.holmberg@ericsson.com>
References: <152278809420.22755.15521672481164240628@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E44446@ESESSMB109.ericsson.se> <HE1PR07MB10810E2B46F366DCB0AE05FB8DA50@HE1PR07MB1081.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB10810E2B46F366DCB0AE05FB8DA50@HE1PR07MB1081.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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <428B1A7B24C5E842AEE4B4FFCA13941B@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGIsWRmVeSWpSXmKPExsUyM2K7k+7P8iNRBtcfclqceP+N1eLZxvks FndbJjJZTF3+mMWBxaPlyFtWjyVLfjIFMEVx2aSk5mSWpRbp2yVwZfx9dJm54AhnxY4taxkb GM+ydzFyckgImEjsX9APZgsJHGGU6GvI7WLkArIXM0q0zjzK0sXIwcEmYCHR/U8bxBQRMJdY 0yAJUsIssJdR4ljfDiaQXmGBEInTB+6DzRERCJWYd30nK0S9k8SEd9EgYRYBFYnv08+AlfAK WEv8WtDADrHqNqPElQ9vwBKcArESfe9PMIPYjAJiEt9PrQGbzywgLnHryXwmiJsFJJbsOc8M YYtKvHz8jxXEFhXQk9hw4jY7yF4JASWJ2xucIFr1JG5MncIGEmYG2vv6jyVEWFti2cLXzBDn CEqcnPmEZQKj+Cwky2Yh6Z6F0D0LSfcsJN0LGFlXMYoWpxYX56YbGemlFmUmFxfn5+nlpZZs YgTG3sEtv612MB587niIUYCDUYmHtzzvSJQQa2JZcWXuIUYJDmYlEd4dSkAh3pTEyqrUovz4 otKc1OJDjNIcLErivE5pFlFCAumJJanZqakFqUUwWSYOTqkGRrNFQjt7hPVube6sCympKWe9 w5+d9zjVSInX9IAk36G559t/8RhbX+g4el+lNp+Jidlh0Z6//X5PctVdFlc4rVnvPSno04Sp S7X14gTCS1/M3PuKc/at4H2rT5T06Pgvy++5nqdS85eRtc3U8MUFsYVzs+RVP0l+mWbpX8DR yHF1bvqqJZmXlViKMxINtZiLihMB8V6BhrkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/TwHmAVJ-lvmWPd591aCnvxyNgRk>
Subject: Re: [MMUSIC] Genart telechat review of draft-ietf-mmusic-sdp-bundle-negotiation-49
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 07:00:23 -0000

Hi Linda,

Thank You for your review!

Regarding your question on =B3media description=B2, I would say that it
represents a =B3media source=B2. See section 4.2 of RFC 7656 for more
information :)

Regards,

Christer




>> Reviewer: Linda Dunbar
>> Review result: Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>Review Team (Gen-ART) reviews all IETF documents
>> being processed by the IESG for the IETF Chair. Please wait for
>>direction from your document shepherd or AD before
>> posting a new version of the draft.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-mmusic-sdp-bundle-negotiation-??
>> Reviewer: Linda Dunbar
>> Review Date: 2018-04-03
>> IETF LC End Date: 2018-02-14
>> IESG Telechat date: 2018-04-19
>>
>> Summary:
>> The document is written very clear, easy to understand even for people
>>like me who is not an expert in the media
>> transport. A dump question, is "media description" same as a "media
>>flow"? Is it always one to one mapping?
>>
>> Major issues: None
>>
>> Minor issues: None
>>
>> Nits/editorial comments:
>>
>>


From nobody Wed Apr  4 00:43:51 2018
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 504241270A0 for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 00:43:49 -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 wcTZR2X-hFBu for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 00:43:47 -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 102B21200F1 for <mmusic@ietf.org>; Wed,  4 Apr 2018 00:43:47 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id n124so11799835vkd.6 for <mmusic@ietf.org>; Wed, 04 Apr 2018 00:43:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qd1ExiYIjCpYT8mQU4kiaI0PbNBbqYP6jXYwsBALWt4=; b=NSoWv3OvK3WUJtSz4gyjiQz/qUPf8lA8IusHf+fbsCtyVrJCxnz1+U8YRoaXsouRqR QicMcRDHvFRttwZ5LnTkROf3OA1xZZCuPALi0PhGo1PR2L0eK7Ug26waRLwLPi2hbWtx psxv1xAQoXnybzxy3jwPDhVCXkYL2P3rdpEeo5+y8rJ/YfZcG882AW2FDEoubFHWPEcx GG1peYzkSMbO98NXnx9lGX3deQvUtIxAu/F0xlS4KouK3yX+pVWZMXAECk0Y/zFu2UMw 53j537nRRZWTlFDyT8lwTjLQ9nZqBp6/6xSUlsCZNSgCS1ULb6Lf3ugu98KfxdZAYDk8 XMgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qd1ExiYIjCpYT8mQU4kiaI0PbNBbqYP6jXYwsBALWt4=; b=C+dzzFb8oXY2ku8cccjc5ZYREKSRaCQVl7HDAQrtZlIvvbkn4ru5dE28tpzAu2InFo h42F/5G5OzBu5TjexRlQuc97wPamqGNDqgwqVWFNdEOPGZNfEzKm6DFa5XWJRseuSip0 Y8giaR6+2dZzEBDfMdOHvSLfxysI3G59Yv5yV+KjzA3HaSNXSZl0lcqck7gKBbxT7V55 LIaTRQVC61j4okoWs65TAIgeIoV0tWuAL1TfGkPZt9LUJQRucvvkH7hlSeISx6pHh5V1 sAuRD2Vmhc0RMjatyJRd8mQxIKtpknlNU5k3dj95I+bwrsCaE48rjuPQOsFTuOi8r+Gq DCLg==
X-Gm-Message-State: ALQs6tAiMR3dF2cvEn34FEj6G2e6oJCBt9nsrTd6QRNxOxAu9cEmbQI6 KH6W3FIZ+BSM9oXxuvpNgKUdFkWVIGMYBpfsurg=
X-Google-Smtp-Source: AIpwx48JbVaNDetm68tGN+1E/R5niPS6Mjq+FbILj/0rqPF7DjR4HRSjPVWoCgneNywsokNpN5jQ5eea+WMtDQzTKeI=
X-Received: by 10.31.174.80 with SMTP id x77mr9916723vke.101.1522827826137; Wed, 04 Apr 2018 00:43:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Wed, 4 Apr 2018 00:43:45 -0700 (PDT)
In-Reply-To: <CAD5OKxuHnOROHnBmT=w4e=PK85BFeNZdTnYNdNZ0J7DJafdSJQ@mail.gmail.com>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com> <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com> <CAMRcRGQZnWytKkap9kXPh0Zq4fJXmwArvPny0fNK5KWYJ=uThA@mail.gmail.com> <CAD5OKxuHnOROHnBmT=w4e=PK85BFeNZdTnYNdNZ0J7DJafdSJQ@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 4 Apr 2018 00:43:45 -0700
Message-ID: <CAMRcRGSZdZHhaNXba1_A_ASrvTueEX23bq1oTeAtRO9pgCtMwg@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143fa3aa18e3a056900fb90"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/TkOZxOu30dB8dfMAvaRHktQyS8k>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 07:43:49 -0000

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

Hello Roman

Thanks for the inputs, Have a clarification question inline

On Tue, Apr 3, 2018 at 10:15 PM, Roman Shpount <roman@telurix.com> wrote:

> Hi Suhas,
>
> On Wed, Apr 4, 2018 at 12:24 AM, Suhas Nandakumar <suhasietf@gmail.com>
> wrote:
>
>> On Tue, Apr 3, 2018 at 12:29 AM, Suhas Nandakumar <suhasietf@gmail.com>
>> wrote:
>>
>>>   The original text was take from RFC5245 sections https://tools.ietf.or
>>> g/html/rfc5245#section-5.1 and 6.1 where it is defines procedures for
>>> answerer and the offerer for verifying ice support. The versions pre 13 for
>>> the current ice-sip-sdp had the exact same content.
>>>
>>> Wondering if we should get back to the original format since it seems to
>>> be more clearer in explaining ?
>>>
>>
>>
>> Any thoughts on this proposal ? please let me know
>>
>
> Original text in https://tools.ietf.org/html/rfc5245#section-5.1 should
> be updated to accommodate the following two issues :
>
> 1. rtcp attribute is now optional
> 2. ICE implementation MAY choose to ignore ICE mismatch and not examine
> address in c= line and rtcp attribute
>

[Suhas] On 2, we need to say exactly the behavior here. If answers sets the
ice-mismatch in multiple m=lines (not all) and offer decides to ignore some
but not others might lead to confusing interpretations. RFC5245 made it
clear that offerer's handling of ice-mismatch is outside the scope.
I tend to incline with that as well. What are your thoughts ?


>
> Regards,
> _____________
> Roman Shpount
>
>
>
>

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

<div dir=3D"ltr">Hello Roman<div><br></div><div>Thanks for the inputs, Have=
 a clarification question inline</div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Tue, Apr 3, 2018 at 10:15 PM, Roman Shpount <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:roman@telurix.com" target=3D"_blank">roman=
@telurix.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">Hi Suhas,<br><div class=3D"gmail_extra"><span class=3D""><br cle=
ar=3D"all"><div><div class=3D"m_8188863876085344499gmail_signature" data-sm=
artmail=3D"gmail_signature">On Wed, Apr 4, 2018 at 12:24 AM, Suhas Nandakum=
ar <span dir=3D"ltr">&lt;<a href=3D"mailto:suhasietf@gmail.com" target=3D"_=
blank">suhasietf@gmail.com</a>&gt;</span> wrote:<br></div></div></span><div=
 class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote"><span><span class=3D"">On=
 Tue, Apr 3, 2018 at 12:29 AM, Suhas Nandakumar <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:suhasietf@gmail.com" target=3D"_blank">suhasietf@gmail.com</a>=
&gt;</span> wrote:<br></span><span class=3D""><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div dir=3D"ltr"><div>=C2=A0 The original text was take from RFC5245 sect=
ions=C2=A0<a href=3D"https://tools.ietf.org/html/rfc5245#section-5.1" targe=
t=3D"_blank">https://tools.ietf.or<wbr>g/html/rfc5245#section-5.1</a> and 6=
.1 where it is defines procedures for answerer and the offerer for verifyin=
g ice support. The versions pre 13 for the current ice-sip-sdp had the exac=
t same content.=C2=A0</div><div><br></div><div>Wondering if we should get b=
ack to the original format since it seems to be more clearer in explaining =
?</div></div></blockquote><div><br></div><div><br></div></span></span><span=
 class=3D""><div>Any thoughts on this proposal ? please let me know=C2=A0</=
div></span></div></div></div></blockquote><div><br></div><div>Original text=
 in=C2=A0<a href=3D"https://tools.ietf.org/html/rfc5245#section-5.1" style=
=3D"color:rgb(17,85,204);font-family:arial,sans-serif;font-size:small;font-=
style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-we=
ight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transf=
orm:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,2=
55)" target=3D"_blank">https://tools.ietf.org/<wbr>html/rfc5245#section-5.1=
</a>=C2=A0<wbr>should be updated to accommodate the following two issues :<=
/div><div><br></div><div>1. rtcp attribute is now optional</div><div>2. ICE=
 implementation MAY choose to ignore ICE mismatch and not examine address i=
n c=3D line and rtcp attribute</div></div></div></div></blockquote><div><br=
></div><div>[Suhas] On 2, we need to say exactly the behavior here. If answ=
ers sets the ice-mismatch in multiple m=3Dlines (not all) and offer decides=
 to ignore some=C2=A0</div><div>but not others might lead to confusing inte=
rpretations. RFC5245 made it clear that offerer&#39;s handling of ice-misma=
tch is outside the scope.</div><div>I tend to incline with that as well. Wh=
at are your thoughts ?</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 dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><di=
v><br></div><div>Regards,</div><div>

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"m_8188863876085344499gmail_signature">_____________<span class=
=3D"HOEnZb"><font color=3D"#888888"><br>Roman Shpount</font></span></div></=
div><br class=3D"m_8188863876085344499gmail-Apple-interchange-newline">

=C2=A0</div><div>=C2=A0</div></div></div></div>
</blockquote></div><br></div></div>

--001a1143fa3aa18e3a056900fb90--


From nobody Wed Apr  4 05:30:00 2018
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 97887120726; Wed,  4 Apr 2018 05:29: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>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152284499153.24047.4415332098208931262@ietfa.amsl.com>
Date: Wed, 04 Apr 2018 05:29:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MD3MsxS-q51ezHYKROqCP0vACsc>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-data-channel-sdpneg-17.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 12:29: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 WG of the IETF.

        Title           : SDP-based Data Channel Negotiation
        Authors         : Keith Drage
                          Maridi R. Makaraju (Raju)
                          Juergen Stoetzer-Bradler
                          Richard Ejzak
                          Jerome Marcon
                          Roni Even
	Filename        : draft-ietf-mmusic-data-channel-sdpneg-17.txt
	Pages           : 42
	Date            : 2018-04-04

Abstract:
   The Real-Time Communication in WEB-browsers (RTCWeb) working group is
   charged to provide protocols to support direct interactive rich
   communications using audio, video, and data between two peers' web-
   browsers.  For the support of data communication, the RTCWeb working
   group has in particular defined the concept of bi-directional data
   channels over SCTP (Stream Control Transmission Protocol), where each
   data channel might be used to transport other protocols, called
   subprotocols.  Data channel setup can be done using either the in-
   band Data Channel Establishment Protocol (DCEP) or using some out-of-
   band non-DCEP protocol.  This document specifies how the SDP (Session
   Description Protocol) offer/answer exchange can be used to achieve
   such an out-of-band non-DCEP negotiation.  Even though data channels
   are designed for RTCWeb use initially, they may be used by other
   protocols like, but not limited to, the CLUE protocol (which is
   defined by the IETF "ControLling mUltiple streams for tElepresence"
   working group).  This document is intended to be used wherever data
   channels are used.


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

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

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


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 Apr  4 05:34:09 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD6F1250B8 for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 05:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 9-XL7TcTkjHH for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 05:34:06 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F1A7120726 for <mmusic@ietf.org>; Wed,  4 Apr 2018 05:34:06 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id C14B21619A17A for <mmusic@ietf.org>; Wed,  4 Apr 2018 13:34:01 +0100 (IST)
Received: from DGGEMM422-HUB.china.huawei.com (10.1.198.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 4 Apr 2018 13:34:03 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by dggemm422-hub.china.huawei.com ([10.1.198.39]) with mapi id 14.03.0361.001; Wed, 4 Apr 2018 20:33:56 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: new revision in draft-ietf-mmusic-data-channel-sdpneg-17 
Thread-Index: AdPMES0/R3+uRXojQVG2VsIr3NCqRw==
Date: Wed, 4 Apr 2018 12:33:57 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD870EA5@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.203.73]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD870EA5DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/So8obTLJj9bVtyMW75Hh1Vw8_E4>
Subject: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 12:34:08 -0000

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

Hi,
I submitted a new revision of  https://tools.ietf.org/html/draft-ietf-mmusi=
c-data-channel-sdpneg-17 trying to address comments from Christer and Bo.
Thanks
Roni Even

--_000_6E58094ECC8D8344914996DAD28F1CCD870EA5DGGEMM506MBXchina_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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:0in;
	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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
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">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">I submitted a new revision of &nbsp;<a href=3D"https=
://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-17">https://to=
ols.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-17</a> trying to ad=
dress comments from Christer and Bo.<o:p></o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal">Roni Even<o:p></o:p></p>
</div>
</body>
</html>

--_000_6E58094ECC8D8344914996DAD28F1CCD870EA5DGGEMM506MBXchina_--


From nobody Wed Apr  4 06:13:04 2018
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 8A3B1129C6B for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 06:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 yY8PcNomLXpR for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 06:13:00 -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 DDFD9127333 for <mmusic@ietf.org>; Wed,  4 Apr 2018 06:12:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=40126; q=dns/txt; s=iport; t=1522847579; x=1524057179; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=4q+H1yBYf7+j+LtIHcif0RKkBTE4nHWpY+jf73hmrpg=; b=eFh9U9rXwBM61zopSu8176bxJEP4tm/g1NLL8/1gulpHGMghjOd9E85d bNb/CoQLWMGMW3U/H6tXX4LB5FKzhKWZrHGlJfr9MUa0xRuh+xGm3e8qV R8yK0TxX5snqKjSxrGkNvYQwAENR0qC21dJ5rnWa6BMJun+WDZDgkab6E 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BQAgCQzsRa/4ENJK0ZAUIZAQEBAQE?= =?us-ascii?q?BAQEBAQEBBwEBAQEBgk11YW8og1+IAI0IgXSBD5JVgXgCCxgBDIQTSwIahDI?= =?us-ascii?q?hNBgBAgEBAQEBAQJsHAyFIgEBAQECAQEBIUsLBQsJAhggAQYDAgICJR8RBg0?= =?us-ascii?q?GAgEBhHwFCA+PMGabPIIcH4Q4g2yCIAWHYoFUP4EMIoJigxEBAQIBgUODFoJ?= =?us-ascii?q?UAocuiRqGdgiFU4hYBodChHqJFYZogSUcOIFSTSMVOoJDgXAwFxGISIVaIzA?= =?us-ascii?q?BAY1vAQE?=
X-IronPort-AV: E=Sophos;i="5.48,406,1517875200";  d="scan'208,217";a="377719617"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2018 13:12:58 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w34DCv8c014232; Wed, 4 Apr 2018 13:12:58 GMT
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: mmusic WG <mmusic@ietf.org>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com> <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <0cb51011-c02a-0ddf-d844-36ab92752658@cisco.com>
Date: Wed, 4 Apr 2018 09:12:57 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------E1797C481FB1B4A6DCC74C65"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kd8FL40A04wOO8eqJN8MpcUb-zc>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 13:13:03 -0000

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



On 4/3/18 3:29 AM, Suhas Nandakumar wrote:
> Hello Flemming
>
>   The original text was take from RFC5245 sections 
> https://tools.ietf.org/html/rfc5245#section-5.1
RFC 5245 Section 5.1 describes answerer procedures and says:
<quote>
5.1.  Verifying ICE Support

    The agent will proceed with the ICE procedures defined in this
    specification if, for each media stream in the SDP it received, the
    default destination for each component of that media stream appears
    in a candidate attribute.  For example, in the case of RTP, the IP
    address and port in the c and m lines, respectively, appear in a
    candidate attribute and the value in the rtcp attribute appears in a
    candidate attribute.

    If this condition is not met, the agent MUST process the SDP based on
    normal RFC 3264 procedures, without using any of the ICE mechanisms
    described in the remainder of this specification with the following
    exceptions:

    1.  The agent MUST follow the rules of Section 10, which describe
        keepalive procedures for all agents.

    2.  If the agent is not proceeding with ICE because there were
        a=candidate attributes, but none that matched the default
        destination of the media stream, the agent MUST include an a=ice-
        mismatch attribute in its answer.

    3.  If the default candidates were relayed candidates learned through
        a TURN server, the agent MUST create permissions in the TURN
        server for the IP addresses learned from its peer in the SDP it
        just received.  If this is not done, initial packets in the media
        stream from the peer may be lost.
<quote>

Everything up to bullet 2 looks good. Bullet 3 is unclear to me:
- Which default candidates are we referring to ?
- If they were from the offer SDP, then how can the answerer create 
permissions in the offerer's TURN server ?
- I guess that means we are actually talking about the answerers default 
candidates, which seems like a somewhat convoluted way of saying that if 
the answerer is using a TURN server for its media stream, then it needs 
to create permissions for whatever the default candidate is in the offer 
SDP (whether relayed or not), or am I missing something ? In either 
case, some clarification is needed here.


> and 6.1 where it is defines procedures for answerer and the offerer 
> for verifying ice support.
RFC 5245 Section 6.1 looks good to me.
> The versions pre 13 for the current ice-sip-sdp had the exact same 
> content.
>
> Wondering if we should get back to the original format since it seems 
> to be more clearer in explaining ?
>
I think so (modulo the above).

Thanks

-- Flemming

>
> Thanks
> Suhas
>
>
> On Mon, Apr 2, 2018 at 4:45 PM, Flemming Andreasen <fandreas@cisco.com 
> <mailto:fandreas@cisco.com>> wrote:
>
>     I'm still having a hard time following this - let me try and
>     elaborate below
>
>     On 4/2/18 1:56 PM, Suhas Nandakumar wrote:
>>     Hi Flemming
>>
>>     Moving the discussion in a separate thread to keep it focussed.
>>     How about following rewording of the section 3.2.5.
>>
>>
>>             3.2.5
>>             <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-3.2.5>.
>>             Verifying ICE Support
>>
>>
>>
>>         The agents will proceed with the ICE procedures defined in [ICE-BIS
>>     <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>]
>>         and this specification if, for each data stream in the SDP it
>>         received, the default destination for each component of that data
>>         stream appears in a candidate attribute.  For example, in the case of
>>         RTP, the IP address and port in the "c=" and "m=" lines,
>>         respectively, appear in a candidate attribute and the value in the
>>         rtcp attribute appears in a candidate attribute.
>     So far so good.
>>         If this condition is not met, the agents MUST process the SDP based on
>>         normal [RFC3264 <https://tools.ietf.org/html/rfc3264>] procedures, without using any of the ICE mechanisms
>>         described in the remainder of this specification with the following
>>         exceptions:
>     Ok, so at this point, there is mismatch between at least one
>     default destination in a component and all of its corresponding
>     candidate attributes. The above says to do normal offer/answer
>     instead of ICE, except as follows:
>
>>         1.  An controlled/responding agent MUST follow the rules of
>>             section 11 of [ICE-BIS
>>     <https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-19#ref-ICE-BIS>], which describe keepalive procedures
>>             for all agents.
>     Earlier, the document says the answerer acts as the responding
>     agent, and the controlling/controlled roles are determined by ICE
>     procedures. Here you seem to say responding = controlled. In any
>     case, it must mean we are dealing with the answerer (which would
>     be easiser to understand from an O/A point of view which is the
>     perspective this documenet should have to the extent possible).
>
>     So it says, the answer will still follow the keep-alive
>     procedures, but we are not doing ICE. I'm not quite sure what that
>     means, but I'm guessing it means we must stop sending keepalives
>     if we were previously sending them (since the ICE session is
>     terminated).
>>     Also, If the default candidates were relayed
>>             candidates learned through a TURN server, the controlled agent
>>             MUST create permissions in the TURN server for the IP addresses
>>             learned from its peer in the offer SDP it just received.
>>             If this is not done, initial packets in the data stream from the
>>             peer may be lost.
>     Here it's not entirely clear whether this is a rule for the
>     offerer or the answerer:
>     1) Answerer
>     The default candidates were present in the offer and apparently
>     they are marked as relayed candidates. However, since the text
>     refers to controlled, per the above, this cannot be test for the
>     answerer.
>
>     2) Offerer
>     This must be an answer SDP that came back to us, however the text
>     clearly talks about the offer SDP.
>
>     I'm confused at this point.
>
>>         2.  On the other hand, if the controlled agent is not proceeding
>>             with ICE because there were a=candidate attributes, but none that
>>             matched the default destination of the data stream, it MUST include
>>             an a=ice-mismatch attribute in its answer and MAY omit a=candidate
>>             attributes for such data streams.
>     Above you said this list was supposed to be exceptions to this
>     rule, but this is the rule itself repeated !?
>
>     Let me know if I am missing something here (but in either case, we
>     need to make the write-up clearer).
>
>
>     Thanks
>
>     -- Flemming
>
>>       SeeSection 9.2.2
>>     <https://tools.ietf..org/html/draft-ietf-mmusic-ice-sip-sdp-19#section-9.2.2>  for a
>>             discussion of cases where this can happen. This specification provides
>>             no guidance on how an controlled agent should proceed in such a
>>             failure case.
>>
>>
>>
>>     Cheers
>>     Suhas
>>
>>
>>     _______________________________________________
>>     mmusic mailing list
>>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/mmusic
>>     <https://www.ietf.org/mailman/listinfo/mmusic>
>
>


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

PGh0bWw+CiAgPGhlYWQ+CiAgICA8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNv
bnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+CiAgPC9oZWFkPgogIDxib2R5IHRl
eHQ9IiMwMDAwMDAiIGJnY29sb3I9IiNGRkZGRkYiPgogICAgPGJyPgogICAgPGJyPgogICAg
PGRpdiBjbGFzcz0ibW96LWNpdGUtcHJlZml4Ij5PbiA0LzMvMTggMzoyOSBBTSwgU3VoYXMg
TmFuZGFrdW1hcgogICAgICB3cm90ZTo8YnI+CiAgICA8L2Rpdj4KICAgIDxibG9ja3F1b3Rl
IHR5cGU9ImNpdGUiCmNpdGU9Im1pZDpDQU1SY1JHU2tlMlMrTURlOE0rN0oyOG5hUmM9bzd1
czNQPW1QVHpzaXR0U3IwaENScXdAbWFpbC5nbWFpbC5jb20iPgogICAgICA8bWV0YSBodHRw
LWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYt
OCI+CiAgICAgIDxkaXYgZGlyPSJsdHIiPkhlbGxvIEZsZW1taW5nCiAgICAgICAgPGRpdj48
YnI+CiAgICAgICAgPC9kaXY+CiAgICAgICAgPGRpdj7CoCBUaGUgb3JpZ2luYWwgdGV4dCB3
YXMgdGFrZSBmcm9tIFJGQzUyNDUgc2VjdGlvbnPCoDxhCiAgICAgICAgICAgIGhyZWY9Imh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1MjQ1I3NlY3Rpb24tNS4xIgogICAgICAg
ICAgICBtb3otZG8tbm90LXNlbmQ9InRydWUiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9yZmM1MjQ1I3NlY3Rpb24tNS4xPC9hPgogICAgICAgIDwvZGl2PgogICAgICA8L2Rpdj4K
ICAgIDwvYmxvY2txdW90ZT4KICAgIFJGQyA1MjQ1IFNlY3Rpb24gNS4xIGRlc2NyaWJlcyBh
bnN3ZXJlciBwcm9jZWR1cmVzIGFuZCBzYXlzOjxicj4KICAgICZsdDtxdW90ZSZndDs8YnI+
CiAgICA1LjEuwqAgVmVyaWZ5aW5nIElDRSBTdXBwb3J0PGJyPgogICAgPGJyPgogICAgwqDC
oCBUaGUgYWdlbnQgd2lsbCBwcm9jZWVkIHdpdGggdGhlIElDRSBwcm9jZWR1cmVzIGRlZmlu
ZWQgaW4gdGhpczxicj4KICAgIMKgwqAgc3BlY2lmaWNhdGlvbiBpZiwgZm9yIGVhY2ggbWVk
aWEgc3RyZWFtIGluIHRoZSBTRFAgaXQgcmVjZWl2ZWQsCiAgICB0aGU8YnI+CiAgICDCoMKg
IGRlZmF1bHQgZGVzdGluYXRpb24gZm9yIGVhY2ggY29tcG9uZW50IG9mIHRoYXQgbWVkaWEg
c3RyZWFtCiAgICBhcHBlYXJzPGJyPgogICAgwqDCoCBpbiBhIGNhbmRpZGF0ZSBhdHRyaWJ1
dGUuwqAgRm9yIGV4YW1wbGUsIGluIHRoZSBjYXNlIG9mIFJUUCwgdGhlCiAgICBJUDxicj4K
ICAgIMKgwqAgYWRkcmVzcyBhbmQgcG9ydCBpbiB0aGUgYyBhbmQgbSBsaW5lcywgcmVzcGVj
dGl2ZWx5LCBhcHBlYXIgaW4gYTxicj4KICAgIMKgwqAgY2FuZGlkYXRlIGF0dHJpYnV0ZSBh
bmQgdGhlIHZhbHVlIGluIHRoZSBydGNwIGF0dHJpYnV0ZSBhcHBlYXJzCiAgICBpbiBhPGJy
PgogICAgwqDCoCBjYW5kaWRhdGUgYXR0cmlidXRlLjxicj4KICAgIDxicj4KICAgIMKgwqAg
SWYgdGhpcyBjb25kaXRpb24gaXMgbm90IG1ldCwgdGhlIGFnZW50IE1VU1QgcHJvY2VzcyB0
aGUgU0RQCiAgICBiYXNlZCBvbjxicj4KICAgIMKgwqAgbm9ybWFsIFJGQyAzMjY0IHByb2Nl
ZHVyZXMsIHdpdGhvdXQgdXNpbmcgYW55IG9mIHRoZSBJQ0UKICAgIG1lY2hhbmlzbXM8YnI+
CiAgICDCoMKgIGRlc2NyaWJlZCBpbiB0aGUgcmVtYWluZGVyIG9mIHRoaXMgc3BlY2lmaWNh
dGlvbiB3aXRoIHRoZQogICAgZm9sbG93aW5nPGJyPgogICAgwqDCoCBleGNlcHRpb25zOjxi
cj4KICAgIDxicj4KICAgIMKgwqAgMS7CoCBUaGUgYWdlbnQgTVVTVCBmb2xsb3cgdGhlIHJ1
bGVzIG9mIFNlY3Rpb24gMTAsIHdoaWNoIGRlc2NyaWJlPGJyPgogICAgwqDCoMKgwqDCoMKg
IGtlZXBhbGl2ZSBwcm9jZWR1cmVzIGZvciBhbGwgYWdlbnRzLjxicj4KICAgIDxicj4KICAg
IMKgwqAgMi7CoCBJZiB0aGUgYWdlbnQgaXMgbm90IHByb2NlZWRpbmcgd2l0aCBJQ0UgYmVj
YXVzZSB0aGVyZSB3ZXJlPGJyPgogICAgwqDCoMKgwqDCoMKgIGE9Y2FuZGlkYXRlIGF0dHJp
YnV0ZXMsIGJ1dCBub25lIHRoYXQgbWF0Y2hlZCB0aGUgZGVmYXVsdDxicj4KICAgIMKgwqDC
oMKgwqDCoCBkZXN0aW5hdGlvbiBvZiB0aGUgbWVkaWEgc3RyZWFtLCB0aGUgYWdlbnQgTVVT
VCBpbmNsdWRlIGFuCiAgICBhPWljZS08YnI+CiAgICDCoMKgwqDCoMKgwqAgbWlzbWF0Y2gg
YXR0cmlidXRlIGluIGl0cyBhbnN3ZXIuPGJyPgogICAgPGJyPgogICAgwqDCoCAzLsKgIElm
IHRoZSBkZWZhdWx0IGNhbmRpZGF0ZXMgd2VyZSByZWxheWVkIGNhbmRpZGF0ZXMgbGVhcm5l
ZAogICAgdGhyb3VnaDxicj4KICAgIMKgwqDCoMKgwqDCoCBhIFRVUk4gc2VydmVyLCB0aGUg
YWdlbnQgTVVTVCBjcmVhdGUgcGVybWlzc2lvbnMgaW4gdGhlIFRVUk48YnI+CiAgICDCoMKg
wqDCoMKgwqAgc2VydmVyIGZvciB0aGUgSVAgYWRkcmVzc2VzIGxlYXJuZWQgZnJvbSBpdHMg
cGVlciBpbiB0aGUgU0RQCiAgICBpdDxicj4KICAgIMKgwqDCoMKgwqDCoCBqdXN0IHJlY2Vp
dmVkLsKgIElmIHRoaXMgaXMgbm90IGRvbmUsIGluaXRpYWwgcGFja2V0cyBpbiB0aGUKICAg
IG1lZGlhPGJyPgogICAgwqDCoMKgwqDCoMKgIHN0cmVhbSBmcm9tIHRoZSBwZWVyIG1heSBi
ZSBsb3N0Ljxicj4KICAgICZsdDtxdW90ZSZndDs8YnI+CiAgICA8YnI+CiAgICBFdmVyeXRo
aW5nIHVwIHRvIGJ1bGxldCAyIGxvb2tzIGdvb2QuIEJ1bGxldCAzIGlzIHVuY2xlYXIgdG8g
bWU6PGJyPgogICAgLSBXaGljaCBkZWZhdWx0IGNhbmRpZGF0ZXMgYXJlIHdlIHJlZmVycmlu
ZyB0byA/IDxicj4KICAgIC0gSWYgdGhleSB3ZXJlIGZyb20gdGhlIG9mZmVyIFNEUCwgdGhl
biBob3cgY2FuIHRoZSBhbnN3ZXJlciBjcmVhdGUKICAgIHBlcm1pc3Npb25zIGluIHRoZSBv
ZmZlcmVyJ3MgVFVSTiBzZXJ2ZXIgPyA8YnI+CiAgICAtIEkgZ3Vlc3MgdGhhdCBtZWFucyB3
ZSBhcmUgYWN0dWFsbHkgdGFsa2luZyBhYm91dCB0aGUgYW5zd2VyZXJzCiAgICBkZWZhdWx0
IGNhbmRpZGF0ZXMsIHdoaWNoIHNlZW1zIGxpa2UgYSBzb21ld2hhdCBjb252b2x1dGVkIHdh
eSBvZgogICAgc2F5aW5nIHRoYXQgaWYgdGhlIGFuc3dlcmVyIGlzIHVzaW5nIGEgVFVSTiBz
ZXJ2ZXIgZm9yIGl0cyBtZWRpYQogICAgc3RyZWFtLCB0aGVuIGl0IG5lZWRzIHRvIGNyZWF0
ZSBwZXJtaXNzaW9ucyBmb3Igd2hhdGV2ZXIgdGhlIGRlZmF1bHQKICAgIGNhbmRpZGF0ZSBp
cyBpbiB0aGUgb2ZmZXIgU0RQICh3aGV0aGVyIHJlbGF5ZWQgb3Igbm90KSwgb3IgYW0gSQog
ICAgbWlzc2luZyBzb21ldGhpbmcgPyBJbiBlaXRoZXIgY2FzZSwgc29tZSBjbGFyaWZpY2F0
aW9uIGlzIG5lZWRlZAogICAgaGVyZS4gPGJyPgogICAgPGJyPgogICAgPGJyPgogICAgPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSIKY2l0ZT0ibWlkOkNBTVJjUkdTa2UyUytNRGU4TSs3SjI4
bmFSYz1vN3VzM1A9bVBUenNpdHRTcjBoQ1Jxd0BtYWlsLmdtYWlsLmNvbSI+CiAgICAgIDxk
aXYgZGlyPSJsdHIiPgogICAgICAgIDxkaXY+YW5kIDYuMSB3aGVyZSBpdCBpcyBkZWZpbmVz
IHByb2NlZHVyZXMgZm9yIGFuc3dlcmVyIGFuZCB0aGUKICAgICAgICAgIG9mZmVyZXIgZm9y
IHZlcmlmeWluZyBpY2Ugc3VwcG9ydC48L2Rpdj4KICAgICAgPC9kaXY+CiAgICA8L2Jsb2Nr
cXVvdGU+CiAgICBSRkMgNTI0NSBTZWN0aW9uIDYuMSBsb29rcyBnb29kIHRvIG1lLiA8YnI+
CiAgICA8YmxvY2txdW90ZSB0eXBlPSJjaXRlIgpjaXRlPSJtaWQ6Q0FNUmNSR1NrZTJTK01E
ZThNKzdKMjhuYVJjPW83dXMzUD1tUFR6c2l0dFNyMGhDUnF3QG1haWwuZ21haWwuY29tIj4K
ICAgICAgPGRpdiBkaXI9Imx0ciI+CiAgICAgICAgPGRpdj4gVGhlIHZlcnNpb25zIHByZSAx
MyBmb3IgdGhlIGN1cnJlbnQgaWNlLXNpcC1zZHAgaGFkIHRoZQogICAgICAgICAgZXhhY3Qg
c2FtZSBjb250ZW50Ljxicj4KICAgICAgICA8L2Rpdj4KICAgICAgPC9kaXY+CiAgICA8L2Js
b2NrcXVvdGU+CiAgICA8YmxvY2txdW90ZSB0eXBlPSJjaXRlIgpjaXRlPSJtaWQ6Q0FNUmNS
R1NrZTJTK01EZThNKzdKMjhuYVJjPW83dXMzUD1tUFR6c2l0dFNyMGhDUnF3QG1haWwuZ21h
aWwuY29tIj4KICAgICAgPGRpdiBkaXI9Imx0ciI+PGJyPgogICAgICAgIDxkaXY+V29uZGVy
aW5nIGlmIHdlIHNob3VsZCBnZXQgYmFjayB0byB0aGUgb3JpZ2luYWwgZm9ybWF0CiAgICAg
ICAgICBzaW5jZSBpdCBzZWVtcyB0byBiZSBtb3JlIGNsZWFyZXIgaW4gZXhwbGFpbmluZyA/
PC9kaXY+CiAgICAgICAgPGRpdj48YnI+CiAgICAgICAgPC9kaXY+CiAgICAgIDwvZGl2Pgog
ICAgPC9ibG9ja3F1b3RlPgogICAgSSB0aGluayBzbyAobW9kdWxvIHRoZSBhYm92ZSkuIDxi
cj4KICAgIDxicj4KICAgIFRoYW5rcyA8YnI+CiAgICA8YnI+CiAgICAtLSBGbGVtbWluZyA8
YnI+CiAgICA8YnI+CiAgICA8YmxvY2txdW90ZSB0eXBlPSJjaXRlIgpjaXRlPSJtaWQ6Q0FN
UmNSR1NrZTJTK01EZThNKzdKMjhuYVJjPW83dXMzUD1tUFR6c2l0dFNyMGhDUnF3QG1haWwu
Z21haWwuY29tIj4KICAgICAgPGRpdiBkaXI9Imx0ciI+CiAgICAgICAgPGRpdj48YnI+CiAg
ICAgICAgPC9kaXY+CiAgICAgICAgPGRpdj5UaGFua3M8L2Rpdj4KICAgICAgICA8ZGl2PlN1
aGFzPC9kaXY+CiAgICAgICAgPGRpdj48YnI+CiAgICAgICAgPC9kaXY+CiAgICAgIDwvZGl2
PgogICAgICA8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyPgogICAgICAgIDxkaXYgY2xh
c3M9ImdtYWlsX3F1b3RlIj5PbiBNb24sIEFwciAyLCAyMDE4IGF0IDQ6NDUgUE0sCiAgICAg
ICAgICBGbGVtbWluZyBBbmRyZWFzZW4gPHNwYW4gZGlyPSJsdHIiPiZsdDs8YQogICAgICAg
ICAgICAgIGhyZWY9Im1haWx0bzpmYW5kcmVhc0BjaXNjby5jb20iIHRhcmdldD0iX2JsYW5r
IgogICAgICAgICAgICAgIG1vei1kby1ub3Qtc2VuZD0idHJ1ZSI+ZmFuZHJlYXNAY2lzY28u
Y29tPC9hPiZndDs8L3NwYW4+CiAgICAgICAgICB3cm90ZTo8YnI+CiAgICAgICAgICA8Ymxv
Y2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAKICAgICAg
ICAgICAgLjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4
Ij4KICAgICAgICAgICAgPGRpdiB0ZXh0PSIjMDAwMDAwIiBiZ2NvbG9yPSIjRkZGRkZGIj4g
SSdtIHN0aWxsIGhhdmluZyBhCiAgICAgICAgICAgICAgaGFyZCB0aW1lIGZvbGxvd2luZyB0
aGlzIC0gbGV0IG1lIHRyeSBhbmQgZWxhYm9yYXRlIGJlbG93CiAgICAgICAgICAgICAgPGJy
PgogICAgICAgICAgICAgIDxzcGFuIGNsYXNzPSIiPiA8YnI+CiAgICAgICAgICAgICAgICA8
ZGl2IGNsYXNzPSJtXzg1MDkzNDI2NzI3NDg1MjA5MDBtb3otY2l0ZS1wcmVmaXgiPk9uCiAg
ICAgICAgICAgICAgICAgIDQvMi8xOCAxOjU2IFBNLCBTdWhhcyBOYW5kYWt1bWFyIHdyb3Rl
Ojxicj4KICAgICAgICAgICAgICAgIDwvZGl2PgogICAgICAgICAgICAgICAgPGJsb2NrcXVv
dGUgdHlwZT0iY2l0ZSI+CiAgICAgICAgICAgICAgICAgIDxkaXYgZGlyPSJsdHIiPgogICAg
ICAgICAgICAgICAgICAgIDxkaXYKc3R5bGU9ImNvbG9yOnJnYigzNCwzNCwzNCk7Zm9udC1m
YW1pbHk6YXJpYWwsc2Fucy1zZXJpZjtmb250LXNpemU6MTIuOHB4O2ZvbnQtc3R5bGU6bm9y
bWFsO2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5v
cm1hbDtmb250LXdlaWdodDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9ybWFsO3RleHQtYWxpZ246
c3RhcnQ7dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7d2hpdGUtc3BhY2U6
bm9ybWFsO3dvcmQtc3BhY2luZzowcHg7YmFja2dyb3VuZC1jb2xvcjpyZ2IoMjU1LDI1NSwy
NTUpO3RleHQtZGVjb3JhdGlvbi1zdHlsZTppbml0aWFsO3RleHQtZGVjb3JhdGlvbi1jb2xv
cjppbml0aWFsIj5IaQogICAgICAgICAgICAgICAgICAgICAgRmxlbW1pbmc8L2Rpdj4KICAg
ICAgICAgICAgICAgICAgICA8ZGl2CnN0eWxlPSJjb2xvcjpyZ2IoMzQsMzQsMzQpO2ZvbnQt
ZmFtaWx5OmFyaWFsLHNhbnMtc2VyaWY7Zm9udC1zaXplOjEyLjhweDtmb250LXN0eWxlOm5v
cm1hbDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250LXZhcmlhbnQtY2Fwczpu
b3JtYWw7Zm9udC13ZWlnaHQ6NDAwO2xldHRlci1zcGFjaW5nOm5vcm1hbDt0ZXh0LWFsaWdu
OnN0YXJ0O3RleHQtaW5kZW50OjBweDt0ZXh0LXRyYW5zZm9ybTpub25lO3doaXRlLXNwYWNl
Om5vcm1hbDt3b3JkLXNwYWNpbmc6MHB4O2JhY2tncm91bmQtY29sb3I6cmdiKDI1NSwyNTUs
MjU1KTt0ZXh0LWRlY29yYXRpb24tc3R5bGU6aW5pdGlhbDt0ZXh0LWRlY29yYXRpb24tY29s
b3I6aW5pdGlhbCI+PGJyPgogICAgICAgICAgICAgICAgICAgIDwvZGl2PgogICAgICAgICAg
ICAgICAgICAgIDxkaXYKc3R5bGU9ImNvbG9yOnJnYigzNCwzNCwzNCk7Zm9udC1mYW1pbHk6
YXJpYWwsc2Fucy1zZXJpZjtmb250LXNpemU6MTIuOHB4O2ZvbnQtc3R5bGU6bm9ybWFsO2Zv
bnQtdmFyaWFudC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5vcm1hbDtm
b250LXdlaWdodDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7
dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7d2hpdGUtc3BhY2U6bm9ybWFs
O3dvcmQtc3BhY2luZzowcHg7YmFja2dyb3VuZC1jb2xvcjpyZ2IoMjU1LDI1NSwyNTUpO3Rl
eHQtZGVjb3JhdGlvbi1zdHlsZTppbml0aWFsO3RleHQtZGVjb3JhdGlvbi1jb2xvcjppbml0
aWFsIj5Nb3ZpbmcKICAgICAgICAgICAgICAgICAgICAgIHRoZSBkaXNjdXNzaW9uIGluIGEg
c2VwYXJhdGUgdGhyZWFkIHRvIGtlZXAgaXQKICAgICAgICAgICAgICAgICAgICAgIGZvY3Vz
c2VkLiBIb3cgYWJvdXQgZm9sbG93aW5nIHJld29yZGluZyBvZiB0aGUKICAgICAgICAgICAg
ICAgICAgICAgIHNlY3Rpb24gMy4yLjUuwqA8L2Rpdj4KICAgICAgICAgICAgICAgICAgICA8
cHJlIGNsYXNzPSJtXzg1MDkzNDI2NzI3NDg1MjA5MDBnbWFpbC1uZXdwYWdlIiBzdHlsZT0i
Zm9udC1zdHlsZTpub3JtYWw7Zm9udC12YXJpYW50LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12
YXJpYW50LWNhcHM6bm9ybWFsO2ZvbnQtd2VpZ2h0OjQwMDtsZXR0ZXItc3BhY2luZzpub3Jt
YWw7dGV4dC1hbGlnbjpzdGFydDt0ZXh0LWluZGVudDowcHg7dGV4dC10cmFuc2Zvcm06bm9u
ZTt3b3JkLXNwYWNpbmc6MHB4O2JhY2tncm91bmQtY29sb3I6cmdiKDI1NSwyNTUsMjU1KTt0
ZXh0LWRlY29yYXRpb24tc3R5bGU6aW5pdGlhbDt0ZXh0LWRlY29yYXRpb24tY29sb3I6aW5p
dGlhbDtmb250LXNpemU6MTMuMzMzM3B4O21hcmdpbi10b3A6MHB4O21hcmdpbi1ib3R0b206
MHB4O2NvbG9yOnJnYigwLDAsMCkiPjxzcGFuIGNsYXNzPSJtXzg1MDkzNDI2NzI3NDg1MjA5
MDBnbWFpbC1oNCIgc3R5bGU9ImxpbmUtaGVpZ2h0OjBwdDtkaXNwbGF5OmlubGluZTt3aGl0
ZS1zcGFjZTpwcmUtd3JhcDtmb250LWZhbWlseTptb25vc3BhY2U7Zm9udC1zaXplOjFlbTtm
b250LXdlaWdodDpib2xkIj4KPC9zcGFuPjwvcHJlPgogICAgICAgICAgICAgICAgICAgIDxw
cmUgY2xhc3M9Im1fODUwOTM0MjY3Mjc0ODUyMDkwMGdtYWlsLW5ld3BhZ2UiIHN0eWxlPSJm
b250LXN0eWxlOm5vcm1hbDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250LXZh
cmlhbnQtY2Fwczpub3JtYWw7Zm9udC13ZWlnaHQ6NDAwO2xldHRlci1zcGFjaW5nOm5vcm1h
bDt0ZXh0LWFsaWduOnN0YXJ0O3RleHQtaW5kZW50OjBweDt0ZXh0LXRyYW5zZm9ybTpub25l
O3dvcmQtc3BhY2luZzowcHg7YmFja2dyb3VuZC1jb2xvcjpyZ2IoMjU1LDI1NSwyNTUpO3Rl
eHQtZGVjb3JhdGlvbi1zdHlsZTppbml0aWFsO3RleHQtZGVjb3JhdGlvbi1jb2xvcjppbml0
aWFsO2ZvbnQtc2l6ZToxMy4zMzMzcHg7bWFyZ2luLXRvcDowcHg7bWFyZ2luLWJvdHRvbTow
cHg7Y29sb3I6cmdiKDAsMCwwKSI+PHNwYW4gY2xhc3M9Im1fODUwOTM0MjY3Mjc0ODUyMDkw
MGdtYWlsLWg0IiBzdHlsZT0ibGluZS1oZWlnaHQ6MHB0O2Rpc3BsYXk6aW5saW5lO3doaXRl
LXNwYWNlOnByZS13cmFwO2ZvbnQtZmFtaWx5Om1vbm9zcGFjZTtmb250LXNpemU6MWVtO2Zv
bnQtd2VpZ2h0OmJvbGQiPgo8L3NwYW4+PC9wcmU+CiAgICAgICAgICAgICAgICAgICAgPHBy
ZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwZ21haWwtbmV3cGFnZSIgc3R5bGU9ImZv
bnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQtdmFy
aWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdodDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9ybWFs
O3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7
d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5kLWNvbG9yOnJnYigyNTUsMjU1LDI1NSk7dGV4
dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9uLWNvbG9yOmluaXRp
YWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJnaW4tdG9wOjBweDttYXJnaW4tYm90dG9tOjBw
eDtjb2xvcjpyZ2IoMCwwLDApIj48c3BhbiBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAw
Z21haWwtaDQiIHN0eWxlPSJsaW5lLWhlaWdodDowcHQ7ZGlzcGxheTppbmxpbmU7d2hpdGUt
c3BhY2U6cHJlLXdyYXA7Zm9udC1mYW1pbHk6bW9ub3NwYWNlO2ZvbnQtc2l6ZToxZW07Zm9u
dC13ZWlnaHQ6Ym9sZCI+PGg0IHN0eWxlPSJsaW5lLWhlaWdodDowcHQ7ZGlzcGxheTppbmxp
bmU7d2hpdGUtc3BhY2U6cHJlLXdyYXA7Zm9udC1mYW1pbHk6bW9ub3NwYWNlO2ZvbnQtc2l6
ZToxZW07Zm9udC13ZWlnaHQ6Ym9sZCI+PGEgY2xhc3M9Im1fODUwOTM0MjY3Mjc0ODUyMDkw
MGdtYWlsLXNlbGZsaW5rIiBuYW1lPSJtXzg1MDkzNDI2NzI3NDg1MjA5MDBfc2VjdGlvbi0z
LjIuNSIgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbW11
c2ljLWljZS1zaXAtc2RwLTE5I3NlY3Rpb24tMy4yLjUiIHN0eWxlPSJjb2xvcjpibGFjazt0
ZXh0LWRlY29yYXRpb246bm9uZSIgdGFyZ2V0PSJfYmxhbmsiIG1vei1kby1ub3Qtc2VuZD0i
dHJ1ZSI+My4yLjU8L2E+LiAgVmVyaWZ5aW5nIElDRSBTdXBwb3J0PC9oND48L3NwYW4+Cgog
ICBUaGUgYWdlbnRzIHdpbGwgcHJvY2VlZCB3aXRoIHRoZSBJQ0UgcHJvY2VkdXJlcyBkZWZp
bmVkIGluIFs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0
Zi1tbXVzaWMtaWNlLXNpcC1zZHAtMTkjcmVmLUlDRS1CSVMiIHRpdGxlPSImcXVvdDtJbnRl
cmFjdGl2ZSBDb25uZWN0aXZpdHkgRXN0YWJsaXNobWVudCAoSUNFKTogQSBQcm90b2NvbCBm
b3IgTmV0d29yayBBZGRyZXNzIFRyYW5zbGF0b3IgKE5BVCkgVHJhdmVyc2FsIGZvciBPZmZl
ci9BbnN3ZXIgUHJvdG9jb2xzJnF1b3Q7IiBzdHlsZT0iY29sb3I6cmdiKDE3LDg1LDIwNCki
IHRhcmdldD0iX2JsYW5rIiBtb3otZG8tbm90LXNlbmQ9InRydWUiPklDRS1CSVM8L2E+XQog
ICBhbmQgdGhpcyBzcGVjaWZpY2F0aW9uIGlmLCBmb3IgZWFjaCBkYXRhIHN0cmVhbSBpbiB0
aGUgU0RQIGl0CiAgIHJlY2VpdmVkLCB0aGUgZGVmYXVsdCBkZXN0aW5hdGlvbiBmb3IgZWFj
aCBjb21wb25lbnQgb2YgdGhhdCBkYXRhCiAgIHN0cmVhbSBhcHBlYXJzIGluIGEgY2FuZGlk
YXRlIGF0dHJpYnV0ZS4gIEZvciBleGFtcGxlLCBpbiB0aGUgY2FzZSBvZgogICBSVFAsIHRo
ZSBJUCBhZGRyZXNzIGFuZCBwb3J0IGluIHRoZSAiYz0iIGFuZCAibT0iIGxpbmVzLAogICBy
ZXNwZWN0aXZlbHksIGFwcGVhciBpbiBhIGNhbmRpZGF0ZSBhdHRyaWJ1dGUgYW5kIHRoZSB2
YWx1ZSBpbiB0aGUKICAgcnRjcCBhdHRyaWJ1dGUgYXBwZWFycyBpbiBhIGNhbmRpZGF0ZSBh
dHRyaWJ1dGUuCjwvcHJlPgogICAgICAgICAgICAgICAgICA8L2Rpdj4KICAgICAgICAgICAg
ICAgIDwvYmxvY2txdW90ZT4KICAgICAgICAgICAgICA8L3NwYW4+IFNvIGZhciBzbyBnb29k
LiA8YnI+CiAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9IiI+CiAgICAgICAgICAgICAgICA8
YmxvY2txdW90ZSB0eXBlPSJjaXRlIj4KICAgICAgICAgICAgICAgICAgPGRpdiBkaXI9Imx0
ciI+CiAgICAgICAgICAgICAgICAgICAgPHByZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIw
OTAwZ21haWwtbmV3cGFnZSIgc3R5bGU9ImZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFu
dC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdo
dDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRl
bnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5k
LWNvbG9yOnJnYigyNTUsMjU1LDI1NSk7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7
dGV4dC1kZWNvcmF0aW9uLWNvbG9yOmluaXRpYWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJn
aW4tdG9wOjBweDttYXJnaW4tYm90dG9tOjBweDtjb2xvcjpyZ2IoMCwwLDApIj4gICBJZiB0
aGlzIGNvbmRpdGlvbiBpcyBub3QgbWV0LCB0aGUgYWdlbnRzIE1VU1QgcHJvY2VzcyB0aGUg
U0RQIGJhc2VkIG9uCiAgIG5vcm1hbCBbPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL3JmYzMyNjQiIHRpdGxlPSImcXVvdDtBbiBPZmZlci9BbnN3ZXIgTW9kZWwgd2l0
aCBTZXNzaW9uIERlc2NyaXB0aW9uIFByb3RvY29sIChTRFApJnF1b3Q7IiBzdHlsZT0iY29s
b3I6cmdiKDE3LDg1LDIwNCkiIHRhcmdldD0iX2JsYW5rIiBtb3otZG8tbm90LXNlbmQ9InRy
dWUiPlJGQzMyNjQ8L2E+XSBwcm9jZWR1cmVzLCB3aXRob3V0IHVzaW5nIGFueSBvZiB0aGUg
SUNFIG1lY2hhbmlzbXMKICAgZGVzY3JpYmVkIGluIHRoZSByZW1haW5kZXIgb2YgdGhpcyBz
cGVjaWZpY2F0aW9uIHdpdGggdGhlIGZvbGxvd2luZwogICBleGNlcHRpb25zOjwvcHJlPgog
ICAgICAgICAgICAgICAgICA8L2Rpdj4KICAgICAgICAgICAgICAgIDwvYmxvY2txdW90ZT4K
ICAgICAgICAgICAgICA8L3NwYW4+IE9rLCBzbyBhdCB0aGlzIHBvaW50LCB0aGVyZSBpcyBt
aXNtYXRjaCBiZXR3ZWVuIGF0CiAgICAgICAgICAgICAgbGVhc3Qgb25lIGRlZmF1bHQgZGVz
dGluYXRpb24gaW4gYSBjb21wb25lbnQgYW5kIGFsbCBvZgogICAgICAgICAgICAgIGl0cyBj
b3JyZXNwb25kaW5nIGNhbmRpZGF0ZSBhdHRyaWJ1dGVzLiBUaGUgYWJvdmUgc2F5cyB0bwog
ICAgICAgICAgICAgIGRvIG5vcm1hbCBvZmZlci9hbnN3ZXIgaW5zdGVhZCBvZiBJQ0UsIGV4
Y2VwdCBhcyBmb2xsb3dzOgogICAgICAgICAgICAgIDxicj4KICAgICAgICAgICAgICA8c3Bh
biBjbGFzcz0iIj4gPGJyPgogICAgICAgICAgICAgICAgPGJsb2NrcXVvdGUgdHlwZT0iY2l0
ZSI+CiAgICAgICAgICAgICAgICAgIDxkaXYgZGlyPSJsdHIiPgogICAgICAgICAgICAgICAg
ICAgIDxwcmUgY2xhc3M9Im1fODUwOTM0MjY3Mjc0ODUyMDkwMGdtYWlsLW5ld3BhZ2UiIHN0
eWxlPSJmb250LXN0eWxlOm5vcm1hbDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtm
b250LXZhcmlhbnQtY2Fwczpub3JtYWw7Zm9udC13ZWlnaHQ6NDAwO2xldHRlci1zcGFjaW5n
Om5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0O3RleHQtaW5kZW50OjBweDt0ZXh0LXRyYW5zZm9y
bTpub25lO3dvcmQtc3BhY2luZzowcHg7YmFja2dyb3VuZC1jb2xvcjpyZ2IoMjU1LDI1NSwy
NTUpO3RleHQtZGVjb3JhdGlvbi1zdHlsZTppbml0aWFsO3RleHQtZGVjb3JhdGlvbi1jb2xv
cjppbml0aWFsO2ZvbnQtc2l6ZToxMy4zMzMzcHg7bWFyZ2luLXRvcDowcHg7bWFyZ2luLWJv
dHRvbTowcHg7Y29sb3I6cmdiKDAsMCwwKSI+ICAgMS4gIEFuIGNvbnRyb2xsZWQvcmVzcG9u
ZGluZyBhZ2VudCBNVVNUIGZvbGxvdyB0aGUgcnVsZXMgb2YgPC9wcmU+CiAgICAgICAgICAg
ICAgICAgICAgPHByZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwZ21haWwtbmV3cGFn
ZSIgc3R5bGU9ImZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6bm9y
bWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdodDo0MDA7bGV0dGVyLXNw
YWNpbmc6bm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJh
bnNmb3JtOm5vbmU7d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5kLWNvbG9yOnJnYigyNTUs
MjU1LDI1NSk7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9u
LWNvbG9yOmluaXRpYWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJnaW4tdG9wOjBweDttYXJn
aW4tYm90dG9tOjBweDtjb2xvcjpyZ2IoMCwwLDApIj4gICAgICAgc2VjdGlvbiAxMSBvZiBb
PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbW11c2lj
LWljZS1zaXAtc2RwLTE5I3JlZi1JQ0UtQklTIiB0aXRsZT0iJnF1b3Q7SW50ZXJhY3RpdmUg
Q29ubmVjdGl2aXR5IEVzdGFibGlzaG1lbnQgKElDRSk6IEEgUHJvdG9jb2wgZm9yIE5ldHdv
cmsgQWRkcmVzcyBUcmFuc2xhdG9yIChOQVQpIFRyYXZlcnNhbCBmb3IgT2ZmZXIvQW5zd2Vy
IFByb3RvY29scyZxdW90OyIgc3R5bGU9ImNvbG9yOnJnYigxNyw4NSwyMDQpIiB0YXJnZXQ9
Il9ibGFuayIgbW96LWRvLW5vdC1zZW5kPSJ0cnVlIj5JQ0UtQklTPC9hPl0sIHdoaWNoIGRl
c2NyaWJlIGtlZXBhbGl2ZSBwcm9jZWR1cmVzIDwvcHJlPgogICAgICAgICAgICAgICAgICAg
IDxwcmUgY2xhc3M9Im1fODUwOTM0MjY3Mjc0ODUyMDkwMGdtYWlsLW5ld3BhZ2UiIHN0eWxl
PSJmb250LXN0eWxlOm5vcm1hbDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250
LXZhcmlhbnQtY2Fwczpub3JtYWw7Zm9udC13ZWlnaHQ6NDAwO2xldHRlci1zcGFjaW5nOm5v
cm1hbDt0ZXh0LWFsaWduOnN0YXJ0O3RleHQtaW5kZW50OjBweDt0ZXh0LXRyYW5zZm9ybTpu
b25lO3dvcmQtc3BhY2luZzowcHg7YmFja2dyb3VuZC1jb2xvcjpyZ2IoMjU1LDI1NSwyNTUp
O3RleHQtZGVjb3JhdGlvbi1zdHlsZTppbml0aWFsO3RleHQtZGVjb3JhdGlvbi1jb2xvcjpp
bml0aWFsO2ZvbnQtc2l6ZToxMy4zMzMzcHg7bWFyZ2luLXRvcDowcHg7bWFyZ2luLWJvdHRv
bTowcHg7Y29sb3I6cmdiKDAsMCwwKSI+ICAgICAgIGZvciBhbGwgYWdlbnRzLiA8L3ByZT4K
ICAgICAgICAgICAgICAgICAgPC9kaXY+CiAgICAgICAgICAgICAgICA8L2Jsb2NrcXVvdGU+
CiAgICAgICAgICAgICAgPC9zcGFuPiBFYXJsaWVyLCB0aGUgZG9jdW1lbnQgc2F5cyB0aGUg
YW5zd2VyZXIgYWN0cyBhcwogICAgICAgICAgICAgIHRoZSByZXNwb25kaW5nIGFnZW50LCBh
bmQgdGhlIGNvbnRyb2xsaW5nL2NvbnRyb2xsZWQgcm9sZXMKICAgICAgICAgICAgICBhcmUg
ZGV0ZXJtaW5lZCBieSBJQ0UgcHJvY2VkdXJlcy4gSGVyZSB5b3Ugc2VlbSB0byBzYXkKICAg
ICAgICAgICAgICByZXNwb25kaW5nID0gY29udHJvbGxlZC4gSW4gYW55IGNhc2UsIGl0IG11
c3QgbWVhbiB3ZSBhcmUKICAgICAgICAgICAgICBkZWFsaW5nIHdpdGggdGhlIGFuc3dlcmVy
ICh3aGljaCB3b3VsZCBiZSBlYXNpc2VyIHRvCiAgICAgICAgICAgICAgdW5kZXJzdGFuZCBm
cm9tIGFuIE8vQSBwb2ludCBvZiB2aWV3IHdoaWNoIGlzIHRoZQogICAgICAgICAgICAgIHBl
cnNwZWN0aXZlIHRoaXMgZG9jdW1lbmV0IHNob3VsZCBoYXZlIHRvIHRoZSBleHRlbnQKICAg
ICAgICAgICAgICBwb3NzaWJsZSkuIDxicj4KICAgICAgICAgICAgICA8YnI+CiAgICAgICAg
ICAgICAgU28gaXQgc2F5cywgdGhlIGFuc3dlciB3aWxsIHN0aWxsIGZvbGxvdyB0aGUga2Vl
cC1hbGl2ZQogICAgICAgICAgICAgIHByb2NlZHVyZXMsIGJ1dCB3ZSBhcmUgbm90IGRvaW5n
IElDRS4gSSdtIG5vdCBxdWl0ZSBzdXJlCiAgICAgICAgICAgICAgd2hhdCB0aGF0IG1lYW5z
LCBidXQgSSdtIGd1ZXNzaW5nIGl0IG1lYW5zIHdlIG11c3Qgc3RvcAogICAgICAgICAgICAg
IHNlbmRpbmcga2VlcGFsaXZlcyBpZiB3ZSB3ZXJlIHByZXZpb3VzbHkgc2VuZGluZyB0aGVt
CiAgICAgICAgICAgICAgKHNpbmNlIHRoZSBJQ0Ugc2Vzc2lvbiBpcyB0ZXJtaW5hdGVkKS7C
oCA8YnI+CiAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9IiI+CiAgICAgICAgICAgICAgICA8
YmxvY2txdW90ZSB0eXBlPSJjaXRlIj4KICAgICAgICAgICAgICAgICAgPGRpdiBkaXI9Imx0
ciI+CiAgICAgICAgICAgICAgICAgICAgPHByZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIw
OTAwZ21haWwtbmV3cGFnZSIgc3R5bGU9ImZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFu
dC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdo
dDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRl
bnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5k
LWNvbG9yOnJnYigyNTUsMjU1LDI1NSk7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7
dGV4dC1kZWNvcmF0aW9uLWNvbG9yOmluaXRpYWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJn
aW4tdG9wOjBweDttYXJnaW4tYm90dG9tOjBweDtjb2xvcjpyZ2IoMCwwLDApIj5BbHNvLCBJ
ZiB0aGUgZGVmYXVsdCBjYW5kaWRhdGVzIHdlcmUgcmVsYXllZCA8L3ByZT4KICAgICAgICAg
ICAgICAgICAgICA8cHJlIGNsYXNzPSJtXzg1MDkzNDI2NzI3NDg1MjA5MDBnbWFpbC1uZXdw
YWdlIiBzdHlsZT0iZm9udC1zdHlsZTpub3JtYWw7Zm9udC12YXJpYW50LWxpZ2F0dXJlczpu
b3JtYWw7Zm9udC12YXJpYW50LWNhcHM6bm9ybWFsO2ZvbnQtd2VpZ2h0OjQwMDtsZXR0ZXIt
c3BhY2luZzpub3JtYWw7dGV4dC1hbGlnbjpzdGFydDt0ZXh0LWluZGVudDowcHg7dGV4dC10
cmFuc2Zvcm06bm9uZTt3b3JkLXNwYWNpbmc6MHB4O2JhY2tncm91bmQtY29sb3I6cmdiKDI1
NSwyNTUsMjU1KTt0ZXh0LWRlY29yYXRpb24tc3R5bGU6aW5pdGlhbDt0ZXh0LWRlY29yYXRp
b24tY29sb3I6aW5pdGlhbDtmb250LXNpemU6MTMuMzMzM3B4O21hcmdpbi10b3A6MHB4O21h
cmdpbi1ib3R0b206MHB4O2NvbG9yOnJnYigwLDAsMCkiPiAgICAgICBjYW5kaWRhdGVzIGxl
YXJuZWQgdGhyb3VnaCBhIFRVUk4gc2VydmVyLCB0aGUgY29udHJvbGxlZCBhZ2VudCA8L3By
ZT4KICAgICAgICAgICAgICAgICAgICA8cHJlIGNsYXNzPSJtXzg1MDkzNDI2NzI3NDg1MjA5
MDBnbWFpbC1uZXdwYWdlIiBzdHlsZT0iZm9udC1zdHlsZTpub3JtYWw7Zm9udC12YXJpYW50
LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12YXJpYW50LWNhcHM6bm9ybWFsO2ZvbnQtd2VpZ2h0
OjQwMDtsZXR0ZXItc3BhY2luZzpub3JtYWw7dGV4dC1hbGlnbjpzdGFydDt0ZXh0LWluZGVu
dDowcHg7dGV4dC10cmFuc2Zvcm06bm9uZTt3b3JkLXNwYWNpbmc6MHB4O2JhY2tncm91bmQt
Y29sb3I6cmdiKDI1NSwyNTUsMjU1KTt0ZXh0LWRlY29yYXRpb24tc3R5bGU6aW5pdGlhbDt0
ZXh0LWRlY29yYXRpb24tY29sb3I6aW5pdGlhbDtmb250LXNpemU6MTMuMzMzM3B4O21hcmdp
bi10b3A6MHB4O21hcmdpbi1ib3R0b206MHB4O2NvbG9yOnJnYigwLDAsMCkiPiAgICAgICBN
VVNUIGNyZWF0ZSBwZXJtaXNzaW9ucyBpbiB0aGUgVFVSTiBzZXJ2ZXIgZm9yIHRoZSBJUCBh
ZGRyZXNzZXMgPC9wcmU+CiAgICAgICAgICAgICAgICAgICAgPHByZSBjbGFzcz0ibV84NTA5
MzQyNjcyNzQ4NTIwOTAwZ21haWwtbmV3cGFnZSIgc3R5bGU9ImZvbnQtc3R5bGU6bm9ybWFs
O2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5vcm1h
bDtmb250LXdlaWdodDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9ybWFsO3RleHQtYWxpZ246c3Rh
cnQ7dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7d29yZC1zcGFjaW5nOjBw
eDtiYWNrZ3JvdW5kLWNvbG9yOnJnYigyNTUsMjU1LDI1NSk7dGV4dC1kZWNvcmF0aW9uLXN0
eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9uLWNvbG9yOmluaXRpYWw7Zm9udC1zaXplOjEz
LjMzMzNweDttYXJnaW4tdG9wOjBweDttYXJnaW4tYm90dG9tOjBweDtjb2xvcjpyZ2IoMCww
LDApIj4gICAgICAgbGVhcm5lZCBmcm9tIGl0cyBwZWVyIGluIHRoZSBvZmZlciBTRFAgaXQg
anVzdCByZWNlaXZlZC4gIDwvcHJlPgogICAgICAgICAgICAgICAgICAgIDxwcmUgY2xhc3M9
Im1fODUwOTM0MjY3Mjc0ODUyMDkwMGdtYWlsLW5ld3BhZ2UiIHN0eWxlPSJmb250LXN0eWxl
Om5vcm1hbDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250LXZhcmlhbnQtY2Fw
czpub3JtYWw7Zm9udC13ZWlnaHQ6NDAwO2xldHRlci1zcGFjaW5nOm5vcm1hbDt0ZXh0LWFs
aWduOnN0YXJ0O3RleHQtaW5kZW50OjBweDt0ZXh0LXRyYW5zZm9ybTpub25lO3dvcmQtc3Bh
Y2luZzowcHg7YmFja2dyb3VuZC1jb2xvcjpyZ2IoMjU1LDI1NSwyNTUpO3RleHQtZGVjb3Jh
dGlvbi1zdHlsZTppbml0aWFsO3RleHQtZGVjb3JhdGlvbi1jb2xvcjppbml0aWFsO2ZvbnQt
c2l6ZToxMy4zMzMzcHg7bWFyZ2luLXRvcDowcHg7bWFyZ2luLWJvdHRvbTowcHg7Y29sb3I6
cmdiKDAsMCwwKSI+ICAgICAgIElmIHRoaXMgaXMgbm90IGRvbmUsIGluaXRpYWwgcGFja2V0
cyBpbiB0aGUgZGF0YSBzdHJlYW0gZnJvbSB0aGUgPC9wcmU+CiAgICAgICAgICAgICAgICAg
ICAgPHByZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwZ21haWwtbmV3cGFnZSIgc3R5
bGU9ImZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6bm9ybWFsO2Zv
bnQtdmFyaWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdodDo0MDA7bGV0dGVyLXNwYWNpbmc6
bm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJhbnNmb3Jt
Om5vbmU7d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5kLWNvbG9yOnJnYigyNTUsMjU1LDI1
NSk7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9uLWNvbG9y
OmluaXRpYWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJnaW4tdG9wOjBweDttYXJnaW4tYm90
dG9tOjBweDtjb2xvcjpyZ2IoMCwwLDApIj4gICAgICAgcGVlciBtYXkgYmUgbG9zdC4KPC9w
cmU+CiAgICAgICAgICAgICAgICAgIDwvZGl2PgogICAgICAgICAgICAgICAgPC9ibG9ja3F1
b3RlPgogICAgICAgICAgICAgIDwvc3Bhbj4gSGVyZSBpdCdzIG5vdCBlbnRpcmVseSBjbGVh
ciB3aGV0aGVyIHRoaXMgaXMgYQogICAgICAgICAgICAgIHJ1bGUgZm9yIHRoZSBvZmZlcmVy
IG9yIHRoZSBhbnN3ZXJlcjo8YnI+CiAgICAgICAgICAgICAgMSkgQW5zd2VyZXI8YnI+CiAg
ICAgICAgICAgICAgVGhlIGRlZmF1bHQgY2FuZGlkYXRlcyB3ZXJlIHByZXNlbnQgaW4gdGhl
IG9mZmVyIGFuZAogICAgICAgICAgICAgIGFwcGFyZW50bHkgdGhleSBhcmUgbWFya2VkIGFz
IHJlbGF5ZWQgY2FuZGlkYXRlcy4gSG93ZXZlciwKICAgICAgICAgICAgICBzaW5jZSB0aGUg
dGV4dCByZWZlcnMgdG8gY29udHJvbGxlZCwgcGVyIHRoZSBhYm92ZSwgdGhpcwogICAgICAg
ICAgICAgIGNhbm5vdCBiZSB0ZXN0IGZvciB0aGUgYW5zd2VyZXIuPGJyPgogICAgICAgICAg
ICAgIDxicj4KICAgICAgICAgICAgICAyKSBPZmZlcmVyPGJyPgogICAgICAgICAgICAgIFRo
aXMgbXVzdCBiZSBhbiBhbnN3ZXIgU0RQIHRoYXQgY2FtZSBiYWNrIHRvIHVzLCBob3dldmVy
CiAgICAgICAgICAgICAgdGhlIHRleHQgY2xlYXJseSB0YWxrcyBhYm91dCB0aGUgb2ZmZXIg
U0RQLiA8YnI+CiAgICAgICAgICAgICAgPGJyPgogICAgICAgICAgICAgIEknbSBjb25mdXNl
ZCBhdCB0aGlzIHBvaW50LiA8YnI+CiAgICAgICAgICAgICAgPHNwYW4gY2xhc3M9IiI+IDxi
cj4KICAgICAgICAgICAgICAgIDxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPgogICAgICAgICAg
ICAgICAgICA8ZGl2IGRpcj0ibHRyIj4KICAgICAgICAgICAgICAgICAgICA8cHJlIGNsYXNz
PSJtXzg1MDkzNDI2NzI3NDg1MjA5MDBnbWFpbC1uZXdwYWdlIiBzdHlsZT0iZm9udC1zdHls
ZTpub3JtYWw7Zm9udC12YXJpYW50LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12YXJpYW50LWNh
cHM6bm9ybWFsO2ZvbnQtd2VpZ2h0OjQwMDtsZXR0ZXItc3BhY2luZzpub3JtYWw7dGV4dC1h
bGlnbjpzdGFydDt0ZXh0LWluZGVudDowcHg7dGV4dC10cmFuc2Zvcm06bm9uZTt3b3JkLXNw
YWNpbmc6MHB4O2JhY2tncm91bmQtY29sb3I6cmdiKDI1NSwyNTUsMjU1KTt0ZXh0LWRlY29y
YXRpb24tc3R5bGU6aW5pdGlhbDt0ZXh0LWRlY29yYXRpb24tY29sb3I6aW5pdGlhbDtmb250
LXNpemU6MTMuMzMzM3B4O21hcmdpbi10b3A6MHB4O21hcmdpbi1ib3R0b206MHB4O2NvbG9y
OnJnYigwLDAsMCkiPiAgIDIuICBPbiB0aGUgb3RoZXIgaGFuZCwgaWYgdGhlIGNvbnRyb2xs
ZWQgYWdlbnQgaXMgbm90IHByb2NlZWRpbmcgPC9wcmU+CiAgICAgICAgICAgICAgICAgICAg
PHByZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwZ21haWwtbmV3cGFnZSIgc3R5bGU9
ImZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFudC1saWdhdHVyZXM6bm9ybWFsO2ZvbnQt
dmFyaWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdodDo0MDA7bGV0dGVyLXNwYWNpbmc6bm9y
bWFsO3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRlbnQ6MHB4O3RleHQtdHJhbnNmb3JtOm5v
bmU7d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5kLWNvbG9yOnJnYigyNTUsMjU1LDI1NSk7
dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9uLWNvbG9yOmlu
aXRpYWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJnaW4tdG9wOjBweDttYXJnaW4tYm90dG9t
OjBweDtjb2xvcjpyZ2IoMCwwLDApIj4gICAgICAgd2l0aCBJQ0UgYmVjYXVzZSB0aGVyZSB3
ZXJlIGE9Y2FuZGlkYXRlIGF0dHJpYnV0ZXMsIGJ1dCBub25lIHRoYXQgPC9wcmU+CiAgICAg
ICAgICAgICAgICAgICAgPHByZSBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwZ21haWwt
bmV3cGFnZSIgc3R5bGU9ImZvbnQtc3R5bGU6bm9ybWFsO2ZvbnQtdmFyaWFudC1saWdhdHVy
ZXM6bm9ybWFsO2ZvbnQtdmFyaWFudC1jYXBzOm5vcm1hbDtmb250LXdlaWdodDo0MDA7bGV0
dGVyLXNwYWNpbmc6bm9ybWFsO3RleHQtYWxpZ246c3RhcnQ7dGV4dC1pbmRlbnQ6MHB4O3Rl
eHQtdHJhbnNmb3JtOm5vbmU7d29yZC1zcGFjaW5nOjBweDtiYWNrZ3JvdW5kLWNvbG9yOnJn
YigyNTUsMjU1LDI1NSk7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNv
cmF0aW9uLWNvbG9yOmluaXRpYWw7Zm9udC1zaXplOjEzLjMzMzNweDttYXJnaW4tdG9wOjBw
eDttYXJnaW4tYm90dG9tOjBweDtjb2xvcjpyZ2IoMCwwLDApIj4gICAgICAgbWF0Y2hlZCB0
aGUgZGVmYXVsdCBkZXN0aW5hdGlvbiBvZiB0aGUgZGF0YSBzdHJlYW0sIGl0IE1VU1QgaW5j
bHVkZSA8L3ByZT4KICAgICAgICAgICAgICAgICAgICA8cHJlIGNsYXNzPSJtXzg1MDkzNDI2
NzI3NDg1MjA5MDBnbWFpbC1uZXdwYWdlIiBzdHlsZT0iZm9udC1zdHlsZTpub3JtYWw7Zm9u
dC12YXJpYW50LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12YXJpYW50LWNhcHM6bm9ybWFsO2Zv
bnQtd2VpZ2h0OjQwMDtsZXR0ZXItc3BhY2luZzpub3JtYWw7dGV4dC1hbGlnbjpzdGFydDt0
ZXh0LWluZGVudDowcHg7dGV4dC10cmFuc2Zvcm06bm9uZTt3b3JkLXNwYWNpbmc6MHB4O2Jh
Y2tncm91bmQtY29sb3I6cmdiKDI1NSwyNTUsMjU1KTt0ZXh0LWRlY29yYXRpb24tc3R5bGU6
aW5pdGlhbDt0ZXh0LWRlY29yYXRpb24tY29sb3I6aW5pdGlhbDtmb250LXNpemU6MTMuMzMz
M3B4O21hcmdpbi10b3A6MHB4O21hcmdpbi1ib3R0b206MHB4O2NvbG9yOnJnYigwLDAsMCki
PiAgICAgICBhbiBhPWljZS1taXNtYXRjaCBhdHRyaWJ1dGUgaW4gaXRzIGFuc3dlciBhbmQg
TUFZIG9taXQgYT1jYW5kaWRhdGUKICAgICAgIGF0dHJpYnV0ZXMgZm9yIHN1Y2ggZGF0YSBz
dHJlYW1zLiA8L3ByZT4KICAgICAgICAgICAgICAgICAgPC9kaXY+CiAgICAgICAgICAgICAg
ICA8L2Jsb2NrcXVvdGU+CiAgICAgICAgICAgICAgPC9zcGFuPiBBYm92ZSB5b3Ugc2FpZCB0
aGlzIGxpc3Qgd2FzIHN1cHBvc2VkIHRvIGJlCiAgICAgICAgICAgICAgZXhjZXB0aW9ucyB0
byB0aGlzIHJ1bGUsIGJ1dCB0aGlzIGlzIHRoZSBydWxlIGl0c2VsZgogICAgICAgICAgICAg
IHJlcGVhdGVkICE/PGJyPgogICAgICAgICAgICAgIDxicj4KICAgICAgICAgICAgICBMZXQg
bWUga25vdyBpZiBJIGFtIG1pc3Npbmcgc29tZXRoaW5nIGhlcmUgKGJ1dCBpbiBlaXRoZXIK
ICAgICAgICAgICAgICBjYXNlLCB3ZSBuZWVkIHRvIG1ha2UgdGhlIHdyaXRlLXVwIGNsZWFy
ZXIpLiA8YnI+CiAgICAgICAgICAgICAgPGJyPgogICAgICAgICAgICAgIDxicj4KICAgICAg
ICAgICAgICBUaGFua3MgPGJyPgogICAgICAgICAgICAgIDxicj4KICAgICAgICAgICAgICAt
LSBGbGVtbWluZyA8YnI+CiAgICAgICAgICAgICAgPGJyPgogICAgICAgICAgICAgIDxibG9j
a3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuIGNsYXNzPSIiPgogICAgICAgICAgICAgICAgICA8
ZGl2IGRpcj0ibHRyIj4KICAgICAgICAgICAgICAgICAgICA8cHJlIGNsYXNzPSJtXzg1MDkz
NDI2NzI3NDg1MjA5MDBnbWFpbC1uZXdwYWdlIiBzdHlsZT0iZm9udC1zdHlsZTpub3JtYWw7
Zm9udC12YXJpYW50LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12YXJpYW50LWNhcHM6bm9ybWFs
O2ZvbnQtd2VpZ2h0OjQwMDtsZXR0ZXItc3BhY2luZzpub3JtYWw7dGV4dC1hbGlnbjpzdGFy
dDt0ZXh0LWluZGVudDowcHg7dGV4dC10cmFuc2Zvcm06bm9uZTt3b3JkLXNwYWNpbmc6MHB4
O2JhY2tncm91bmQtY29sb3I6cmdiKDI1NSwyNTUsMjU1KTt0ZXh0LWRlY29yYXRpb24tc3R5
bGU6aW5pdGlhbDt0ZXh0LWRlY29yYXRpb24tY29sb3I6aW5pdGlhbDtmb250LXNpemU6MTMu
MzMzM3B4O21hcmdpbi10b3A6MHB4O21hcmdpbi1ib3R0b206MHB4O2NvbG9yOnJnYigwLDAs
MCkiPiBTZWUgPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLi5vcmcvaHRtbC9kcmFmdC1p
ZXRmLW1tdXNpYy1pY2Utc2lwLXNkcC0xOSNzZWN0aW9uLTkuMi4yIiBzdHlsZT0iY29sb3I6
cmdiKDE3LDg1LDIwNCkiIHRhcmdldD0iX2JsYW5rIiBtb3otZG8tbm90LXNlbmQ9InRydWUi
PlNlY3Rpb24gOS4yLjI8L2E+IGZvciBhCiAgICAgICBkaXNjdXNzaW9uIG9mIGNhc2VzIHdo
ZXJlIHRoaXMgY2FuIGhhcHBlbi4gVGhpcyBzcGVjaWZpY2F0aW9uIHByb3ZpZGVzIDwvcHJl
PgogICAgICAgICAgICAgICAgICAgIDxwcmUgY2xhc3M9Im1fODUwOTM0MjY3Mjc0ODUyMDkw
MGdtYWlsLW5ld3BhZ2UiIHN0eWxlPSJmb250LXN0eWxlOm5vcm1hbDtmb250LXZhcmlhbnQt
bGlnYXR1cmVzOm5vcm1hbDtmb250LXZhcmlhbnQtY2Fwczpub3JtYWw7Zm9udC13ZWlnaHQ6
NDAwO2xldHRlci1zcGFjaW5nOm5vcm1hbDt0ZXh0LWFsaWduOnN0YXJ0O3RleHQtaW5kZW50
OjBweDt0ZXh0LXRyYW5zZm9ybTpub25lO3dvcmQtc3BhY2luZzowcHg7YmFja2dyb3VuZC1j
b2xvcjpyZ2IoMjU1LDI1NSwyNTUpO3RleHQtZGVjb3JhdGlvbi1zdHlsZTppbml0aWFsO3Rl
eHQtZGVjb3JhdGlvbi1jb2xvcjppbml0aWFsO2ZvbnQtc2l6ZToxMy4zMzMzcHg7bWFyZ2lu
LXRvcDowcHg7bWFyZ2luLWJvdHRvbTowcHg7Y29sb3I6cmdiKDAsMCwwKSI+ICAgICAgIG5v
IGd1aWRhbmNlIG9uIGhvdyBhbiBjb250cm9sbGVkIGFnZW50IHNob3VsZCBwcm9jZWVkIGlu
IHN1Y2ggYSA8L3ByZT4KICAgICAgICAgICAgICAgICAgICA8cHJlIGNsYXNzPSJtXzg1MDkz
NDI2NzI3NDg1MjA5MDBnbWFpbC1uZXdwYWdlIiBzdHlsZT0iZm9udC1zdHlsZTpub3JtYWw7
Zm9udC12YXJpYW50LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12YXJpYW50LWNhcHM6bm9ybWFs
O2ZvbnQtd2VpZ2h0OjQwMDtsZXR0ZXItc3BhY2luZzpub3JtYWw7dGV4dC1hbGlnbjpzdGFy
dDt0ZXh0LWluZGVudDowcHg7dGV4dC10cmFuc2Zvcm06bm9uZTt3b3JkLXNwYWNpbmc6MHB4
O2JhY2tncm91bmQtY29sb3I6cmdiKDI1NSwyNTUsMjU1KTt0ZXh0LWRlY29yYXRpb24tc3R5
bGU6aW5pdGlhbDt0ZXh0LWRlY29yYXRpb24tY29sb3I6aW5pdGlhbDtmb250LXNpemU6MTMu
MzMzM3B4O21hcmdpbi10b3A6MHB4O21hcmdpbi1ib3R0b206MHB4O2NvbG9yOnJnYigwLDAs
MCkiPiAgICAgICBmYWlsdXJlIGNhc2UuPC9wcmU+CiAgICAgICAgICAgICAgICAgICAgPGJy
CiAgICAgICAgICAgICAgICAgICAgICBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwZ21h
aWwtQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGluZSI+CiAgICAgICAgICAgICAgICAgICAgPGJy
PgogICAgICAgICAgICAgICAgICAgIDxkaXY+PGJyPgogICAgICAgICAgICAgICAgICAgIDwv
ZGl2PgogICAgICAgICAgICAgICAgICAgIDxkaXY+Q2hlZXJzPC9kaXY+CiAgICAgICAgICAg
ICAgICAgICAgPGRpdj5TdWhhczwvZGl2PgogICAgICAgICAgICAgICAgICA8L2Rpdj4KICAg
ICAgICAgICAgICAgICAgPGJyPgogICAgICAgICAgICAgICAgICA8ZmllbGRzZXQKICAgICAg
ICAgICAgICAgICAgICBjbGFzcz0ibV84NTA5MzQyNjcyNzQ4NTIwOTAwbWltZUF0dGFjaG1l
bnRIZWFkZXIiPjwvZmllbGRzZXQ+CiAgICAgICAgICAgICAgICAgIDxicj4KICAgICAgICAg
ICAgICAgIDwvc3Bhbj4KICAgICAgICAgICAgICAgIDxwcmU+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPHdicj5fX19fX19fX19fX19fX19fXwptbXVzaWMgbWFpbGluZyBsaXN0
CjxhIGNsYXNzPSJtXzg1MDkzNDI2NzI3NDg1MjA5MDBtb3otdHh0LWxpbmstYWJicmV2aWF0
ZWQiIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIiBtb3ot
ZG8tbm90LXNlbmQ9InRydWUiPm1tdXNpY0BpZXRmLm9yZzwvYT4KPGEgY2xhc3M9Im1fODUw
OTM0MjY3Mjc0ODUyMDkwMG1vei10eHQtbGluay1mcmVldGV4dCIgaHJlZj0iaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMiIHRhcmdldD0iX2JsYW5rIiBt
b3otZG8tbm90LXNlbmQ9InRydWUiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vPHdi
cj5saXN0aW5mby9tbXVzaWM8L2E+CjwvcHJlPgogICAgICAgICAgICAgIDwvYmxvY2txdW90
ZT4KICAgICAgICAgICAgICA8YnI+CiAgICAgICAgICAgIDwvZGl2PgogICAgICAgICAgPC9i
bG9ja3F1b3RlPgogICAgICAgIDwvZGl2PgogICAgICAgIDxicj4KICAgICAgPC9kaXY+CiAg
ICA8L2Jsb2NrcXVvdGU+CiAgICA8YnI+CiAgPC9ib2R5Pgo8L2h0bWw+Cg==
--------------E1797C481FB1B4A6DCC74C65--


From nobody Wed Apr  4 06:13:45 2018
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 7AB22129C6B for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 06:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 Sdxzvsj_b3kX for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 06:13:41 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A2A2127333 for <mmusic@ietf.org>; Wed,  4 Apr 2018 06:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10449; q=dns/txt; s=iport; t=1522847621; x=1524057221; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=A4wU0QJM962Jx8e3PrJ96G3lx6UfHEQw4BAHVktP430=; b=KsSsrAZg8+7z8Ijfd8P3fcypJbABeozplwK01xnCaYY//KmJlw/YLfTl ICfopU9LPpEnyuijvvsCgdSCZHcr71bxluj4xOn2Z8ev5GklDyIBxWuKo yJ5ppQ+bnM5AKaFB9xhoH1eGzFqFVw32LnvJKMOYJISLnwCWf9VVubZK9 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BBBgCQzsRa/4cNJK0ZAUIZAQEBAQE?= =?us-ascii?q?BAQEBAQEBBwEBAQEBg0JhbyiDX5UIgXSBD4ZhhxCGXgsjgx6BQgKETCE4FAE?= =?us-ascii?q?CAQEBAQEBAmwcDIUjAQUjVhALGCcDAgIhJREGAQwGAgEBhHEDCA0PjzCcIoI?= =?us-ascii?q?cH4Q4gjQNgSuCIAWHYoFUP4EugmKCT0IBAQIBhFmCVAKQSIZKLAiFU4Vhgnc?= =?us-ascii?q?GgTKDWYI3hHqJFTuGLYElMyGBUk0jFYJ9gXBYiEiFWiMwAY1wAQE?=
X-IronPort-AV: E=Sophos;i="5.48,406,1517875200";  d="scan'208,217";a="366059648"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2018 13:13:40 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w34DDdIk010153; Wed, 4 Apr 2018 13:13:40 GMT
To: Suhas Nandakumar <suhasietf@gmail.com>, Roman Shpount <roman@telurix.com>
Cc: mmusic WG <mmusic@ietf.org>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com> <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com> <CAMRcRGQZnWytKkap9kXPh0Zq4fJXmwArvPny0fNK5KWYJ=uThA@mail.gmail.com> <CAD5OKxuHnOROHnBmT=w4e=PK85BFeNZdTnYNdNZ0J7DJafdSJQ@mail.gmail.com> <CAMRcRGSZdZHhaNXba1_A_ASrvTueEX23bq1oTeAtRO9pgCtMwg@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <3453aecf-6fce-500f-a4c6-df039ea5d836@cisco.com>
Date: Wed, 4 Apr 2018 09:13:39 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGSZdZHhaNXba1_A_ASrvTueEX23bq1oTeAtRO9pgCtMwg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------51485A74B370E273659F7310"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XZ6qX4ZLtvZnNM5UYls7xUwVgyM>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 13:13:43 -0000

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



On 4/4/18 3:43 AM, Suhas Nandakumar wrote:
> Hello Roman
>
> Thanks for the inputs, Have a clarification question inline
>
> On Tue, Apr 3, 2018 at 10:15 PM, Roman Shpount <roman@telurix.com 
> <mailto:roman@telurix.com>> wrote:
>
>     Hi Suhas,
>
>     On Wed, Apr 4, 2018 at 12:24 AM, Suhas Nandakumar
>     <suhasietf@gmail.com <mailto:suhasietf@gmail.com>> wrote:
>
>         On Tue, Apr 3, 2018 at 12:29 AM, Suhas Nandakumar
>         <suhasietf@gmail.com <mailto:suhasietf@gmail.com>> wrote:
>
>               The original text was take from RFC5245 sections
>             https://tools.ietf.org/html/rfc5245#section-5.1
>             <https://tools.ietf.org/html/rfc5245#section-5.1> and 6.1
>             where it is defines procedures for answerer and the
>             offerer for verifying ice support. The versions pre 13 for
>             the current ice-sip-sdp had the exact same content.
>
>             Wondering if we should get back to the original format
>             since it seems to be more clearer in explaining ?
>
>
>
>         Any thoughts on this proposal ? please let me know
>
>
>     Original text in https://tools.ietf.org/html/rfc5245#section-5.1
>     <https://tools.ietf.org/html/rfc5245#section-5.1> should be
>     updated to accommodate the following two issues :
>
>     1. rtcp attribute is now optional
>     2. ICE implementation MAY choose to ignore ICE mismatch and not
>     examine address in c= line and rtcp attribute
>
>
> [Suhas] On 2, we need to say exactly the behavior here. If answers 
> sets the ice-mismatch in multiple m=lines (not all) and offer decides 
> to ignore some
> but not others might lead to confusing interpretations. RFC5245 made 
> it clear that offerer's handling of ice-mismatch is outside the scope.
> I tend to incline with that as well. What are your thoughts ?
Seems reasonable.

-- Flemming
>
>
>     Regards,
>     _____________
>     Roman Shpount
>
>


--------------51485A74B370E273659F7310
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/4/18 3:43 AM, Suhas Nandakumar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAMRcRGSZdZHhaNXba1_A_ASrvTueEX23bq1oTeAtRO9pgCtMwg@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">Hello Roman
        <div><br>
        </div>
        <div>Thanks for the inputs, Have a clarification question inline</div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Tue, Apr 3, 2018 at 10:15 PM,
            Roman Shpount <span dir="ltr">&lt;<a
                href="mailto:roman@telurix.com" target="_blank"
                moz-do-not-send="true">roman@telurix.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">Hi Suhas,<br>
                <div class="gmail_extra"><span class=""><br clear="all">
                    <div>
                      <div class="m_8188863876085344499gmail_signature"
                        data-smartmail="gmail_signature">On Wed, Apr 4,
                        2018 at 12:24 AM, Suhas Nandakumar <span
                          dir="ltr">&lt;<a
                            href="mailto:suhasietf@gmail.com"
                            target="_blank" moz-do-not-send="true">suhasietf@gmail.com</a>&gt;</span>
                        wrote:<br>
                      </div>
                    </div>
                  </span>
                  <div class="gmail_quote">
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <div dir="ltr">
                        <div class="gmail_extra">
                          <div class="gmail_quote"><span><span class="">On
                                Tue, Apr 3, 2018 at 12:29 AM, Suhas
                                Nandakumar <span dir="ltr">&lt;<a
                                    href="mailto:suhasietf@gmail.com"
                                    target="_blank"
                                    moz-do-not-send="true">suhasietf@gmail.com</a>&gt;</span>
                                wrote:<br>
                              </span><span class="">
                                <blockquote class="gmail_quote"
                                  style="margin:0 0 0
                                  .8ex;border-left:1px #ccc
                                  solid;padding-left:1ex">
                                  <div dir="ltr">
                                    <div>  The original text was take
                                      from RFC5245 sections <a
                                        href="https://tools.ietf.org/html/rfc5245#section-5.1"
                                        target="_blank"
                                        moz-do-not-send="true">https://tools.ietf.or<wbr>g/html/rfc5245#section-5.1</a>
                                      and 6.1 where it is defines
                                      procedures for answerer and the
                                      offerer for verifying ice support.
                                      The versions pre 13 for the
                                      current ice-sip-sdp had the exact
                                      same content. </div>
                                    <div><br>
                                    </div>
                                    <div>Wondering if we should get back
                                      to the original format since it
                                      seems to be more clearer in
                                      explaining ?</div>
                                  </div>
                                </blockquote>
                                <div><br>
                                </div>
                                <div><br>
                                </div>
                              </span></span><span class="">
                              <div>Any thoughts on this proposal ?
                                please let me know </div>
                            </span></div>
                        </div>
                      </div>
                    </blockquote>
                    <div><br>
                    </div>
                    <div>Original text in <a
                        href="https://tools.ietf.org/html/rfc5245#section-5.1"
style="color:rgb(17,85,204);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)"
                        target="_blank" moz-do-not-send="true">https://tools.ietf.org/<wbr>html/rfc5245#section-5.1</a> <wbr>should
                      be updated to accommodate the following two issues
                      :</div>
                    <div><br>
                    </div>
                    <div>1. rtcp attribute is now optional</div>
                    <div>2. ICE implementation MAY choose to ignore ICE
                      mismatch and not examine address in c= line and
                      rtcp attribute</div>
                  </div>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>[Suhas] On 2, we need to say exactly the behavior here.
              If answers sets the ice-mismatch in multiple m=lines (not
              all) and offer decides to ignore some </div>
            <div>but not others might lead to confusing interpretations.
              RFC5245 made it clear that offerer's handling of
              ice-mismatch is outside the scope.</div>
            <div>I tend to incline with that as well. What are your
              thoughts ?</div>
            <div> </div>
          </div>
        </div>
      </div>
    </blockquote>
    Seems reasonable. <br>
    <br>
    -- Flemming <br>
    <blockquote type="cite"
cite="mid:CAMRcRGSZdZHhaNXba1_A_ASrvTueEX23bq1oTeAtRO9pgCtMwg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">
                <div class="gmail_extra">
                  <div class="gmail_quote">
                    <div><br>
                    </div>
                    <div>Regards,</div>
                    <div>
                      <div
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">
                        <div
                          class="m_8188863876085344499gmail_signature">_____________<span
                            class="HOEnZb"><font color="#888888"><br>
                              Roman Shpount</font></span></div>
                      </div>
                      <br
                        class="m_8188863876085344499gmail-Apple-interchange-newline">
                       </div>
                    <div> </div>
                  </div>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------51485A74B370E273659F7310--


From nobody Wed Apr  4 09:07:54 2018
Return-Path: <stpeter@mozilla.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 091E21201F8 for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 09:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 px6K7LkG1WtV for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 09:07:45 -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 A4F4812DA4B for <mmusic@ietf.org>; Wed,  4 Apr 2018 09:07:42 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id q84so26972323iod.10 for <mmusic@ietf.org>; Wed, 04 Apr 2018 09:07:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hDer+iK/tTTmFkzy+VFVYo69/yS2Rg4C9pWlrPu+IRo=; b=PBN2MpOBfwUH1/d5uYpYZBmIv2hovc7WCzxrRg6j5tu+B39u3elJyXnrZFUvQuCA0d MwkVEwuVxbsQ/TWl+Ff2EchuhfIKu/6EZcsv6peYFHgN7Rj6SoWuZcMJtAgEbqq3sdL5 CW8HpQG8/HQXotEvxGEekBje8um3F3LMEptKs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=hDer+iK/tTTmFkzy+VFVYo69/yS2Rg4C9pWlrPu+IRo=; b=Vxjo2CFgqQcpp3EWr5P8QIdcVgkK69fWHWB11YO2yIYry82CYclIH42ll7pXrY0JJv 5cUqqwcJ48WJGrLtkZeQsbMrrjf4DjJqnTu+cWbRoPyFgG4j7d8IyW4TQBFFkqhN4bGr o1zyLPoQSZ7FqA81edzvvdDhq0r9THT4QSG9DhTki/y9gx82MtYlUquChyRPfqPBCGyd S7n6VuK3baLgRaGC6u7IayseyGmyVs5kAALAOspKxeG15LSAwMex8NXsevJGfoRBwlfX sykCjhDNnSsM/z3LYnUb4+eJSY6HZJ6AxHvqiczbe2LfvM0ve5InHbpQv2JHXCsjwJaI M9TA==
X-Gm-Message-State: ALQs6tDazxU/tapAQxo+VpdktHL1LP+sHt28hJOVjxDVLPIABkWxBVYC JAkBETBVUY+YkqvytxdV/qFJ2Q==
X-Google-Smtp-Source: AIpwx49sQXx0mKcljzSHtJLJRVizaY1/+L80TqEY5cSYMIEySDNYxjphzP7KO0n71Q8nDjIqIdcuNQ==
X-Received: by 10.107.179.84 with SMTP id c81mr15534381iof.99.1522858061845; Wed, 04 Apr 2018 09:07:41 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id t134-v6sm2518518itt.43.2018.04.04.09.07.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 09:07:40 -0700 (PDT)
To: Suhas Nandakumar <suhasietf@gmail.com>, Ben Campbell <ben@nostrum.com>
Cc: Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com>
Date: Wed, 4 Apr 2018 10:07:39 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ldsCElwO_gjhy7oqZhZeOogIHjg>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 16:07:47 -0000

On 4/3/18 2:41 PM, Suhas Nandakumar wrote:
> 
> 
> On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com
> <mailto:ben@nostrum.com>> wrote:
> 
> 
> 
>     > On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com <mailto:stpeter@mozilla.com>> wrote:
>     >
>     > On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
>     >> Just to complete, ice-bis doesn’t normatively reference ice-sip-SDP
>     >> draft when it moved to using “usages “ indirections for signaling protocols.
>     >>
>     >>
>     >> Trickle ice can use similar approach and refer to trickle-sip as usage
>     >> for trickle.
>     >
>     > It already does. That's why we pulled all the SDP/SIP stuff out of
>     > draft-ietf-ice-trickle.
> 
>     I assume Suhas meant separating the SDP stuff from the SIP stuff. (I
>     also assume he will correct me if I am wrong.)
> 
> 
> That's right Ben .. I was just thinking minimal localized changes (thus
> small time to get new draft done) and then asking trickle, trickle-sip to 
> refer to the new one. (work done to refer is much smaller for these
> drafts that are at the very end of approval journey)
> 
> I do agree with Adam, no matter what version of the proposal we pick,
> there is some work that needs to be done and we
> should do it.

These documents are on the telechat tomorrow. Are we proposing to delay
consideration by the IESG while we get this mess sorted out? ;-)

Peter


From nobody Wed Apr  4 09:47:35 2018
Return-Path: <fluffy@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 B061D129C5D; Wed,  4 Apr 2018 09:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 RyDJ3mfpGmur; Wed,  4 Apr 2018 09:47:32 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16AE120724; Wed,  4 Apr 2018 09:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2707; q=dns/txt; s=iport; t=1522860452; x=1524070052; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CVGDyZk8+h7fHipLl8NjZBJdmUDeJOLp3CPEr0rjGj4=; b=I4eahyy6kCdgc+2ssoVWVUnR85LqbwBKhkjiBIjFayh9ZQLsbvBPMCZf QfNpYcO9jfnIu11qw/9loM+vhCL0US4v0o7oFANSACqenXq91RorKNCCj Q/cgXK57jWN9RLHnUMeSYb/dblbl10HQoU47QyiYuY2uisU4A+R4sEC++ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AWAgCAAMVa/5RdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJNdYFQKAqYXYMDjXGEZIF6C4UDAoRAITYWAQIBAQEBAQE?= =?us-ascii?q?CbCiFIwZ5EAIBCAQKLQQHMhQRAgQOBRSEFWSuH4hCgiWHYoITgQwigmKIH4I?= =?us-ascii?q?kApc+CAKOL4w8j1YCERMBgSQBIwYrgVJwFWQBghiCSI4Gb4xXgRcBAQ?=
X-IronPort-AV: E=Sophos; i="5.48,407,1517875200"; d="scan'208,217"; a="93647902"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2018 16:47:31 +0000
Received: from XCH-RTP-001.cisco.com (xch-rtp-001.cisco.com [64.101.220.141]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w34GlUtF022110 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Apr 2018 16:47:30 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-001.cisco.com (64.101.220.141) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 4 Apr 2018 12:47:30 -0400
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1320.000; Wed, 4 Apr 2018 12:47:30 -0400
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Roman Shpount <roman@telurix.com>, Ben Campbell <ben@nostrum.com>, "Adam Roach" <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, "RTCWeb IETF" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [Ice] [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2gFmEK6jl7hIUqOkWqvx/vbz6PvhV+AgAAIEACAAAg0m////QaAgAGC0AA=
Date: Wed, 4 Apr 2018 16:47:30 +0000
Message-ID: <2B936029-9DC7-491C-893F-AE6D05723E4B@cisco.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com> <CABcZeBMwmisiM0Vpc9Pr53wOPi=J6RAKiNiO8JEkPOtcTjOZvA@mail.gmail.com>
In-Reply-To: <CABcZeBMwmisiM0Vpc9Pr53wOPi=J6RAKiNiO8JEkPOtcTjOZvA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.19.228.210]
Content-Type: multipart/alternative; boundary="_000_2B9360299DC7491C893FAE6D05723E4Bciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3xDBD90KCx1IBE2l4h7d0NendG8>
Subject: Re: [MMUSIC] [Ice] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 16:47:34 -0000

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



On Apr 3, 2018, at 11:43 AM, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.co=
m>> wrote:


I want to do whatever is necessary to remove the normative dependency from =
JSEP to SIP

-Ekr


I think a big part of the RTCWeb/WebRTC community would strongly object to =
JSEP normatively depending on SIP.

--_000_2B9360299DC7491C893FAE6D05723E4Bciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <929464B6EA23234BB72F61487F45C971@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break:=
 after-white-space;" class=3D"">
<br class=3D"">
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Apr 3, 2018, at 11:43 AM, Eric Rescorla &lt;<a href=3D"m=
ailto:ekr@rtfm.com" class=3D"">ekr@rtfm.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size:=
 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform=
: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px; text-decoration: none;" class=3D"">
<br class=3D"Apple-interchange-newline">
I want to do whatever is necessary to remove the normative dependency from =
JSEP to SIP</div>
<div style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size:=
 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform=
: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px; text-decoration: none;" class=3D"">
<br class=3D"">
</div>
<div style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size:=
 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform=
: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px; text-decoration: none;" class=3D"">
-Ekr</div>
<br class=3D"Apple-interchange-newline">
</div>
</blockquote>
</div>
<br class=3D"">
<div class=3D"">I think a big part of the RTCWeb/WebRTC community would str=
ongly object to JSEP normatively depending on SIP.&nbsp;</div>
</body>
</html>

--_000_2B9360299DC7491C893FAE6D05723E4Bciscocom_--


From nobody Wed Apr  4 10:06:20 2018
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 6A045129C6D for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 10:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] 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 ncJ7uZK-WZ_l for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 10:06:06 -0700 (PDT)
Received: from mail-pl0-x236.google.com (mail-pl0-x236.google.com [IPv6:2607:f8b0:400e:c01::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 6313912DA49 for <mmusic@ietf.org>; Wed,  4 Apr 2018 10:05:56 -0700 (PDT)
Received: by mail-pl0-x236.google.com with SMTP id bj1-v6so12474638plb.8 for <mmusic@ietf.org>; Wed, 04 Apr 2018 10:05:56 -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=C6loMDHa8scYgqYof7mziGVsZau/p22LZWGmKOM1gOI=; b=TFTK2+ap0548gFGpjVT+s7j/8rLM+K/7SST/b2+aKn1NbF7Fc+xPV4OYqRPeNYdyhx AEuZbHkauKK+AQ9UjOBFEUv1Dflq7eCrb5J0Jbi0aRWAmQM4DlPg5ns1OCCkdjYQSTPz D0kVA3HgscF7RakPY4z9horgDkDdAS4ceaf+F7lHRC3M+94yAfwiAV4Lo7ZkdSCKbhAS hdukphl83Jyezd2cTac/zgtcRrKVjn+ApngAVAR43bY8XvvvdfE2cSKJnLww+EUczatX 9KcNAInsQ1hjQ6fJ65VGKfKz36ygh3YhXGFLogsnyiuQur6+BqgiKClV8+GlSW2ndaTs FKGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C6loMDHa8scYgqYof7mziGVsZau/p22LZWGmKOM1gOI=; b=idnnDfSlk2NZy83LdaJGzpCemijVP78gw4yF+zgGQqKvpQ58wYZ0+1sQIt7unaWhn7 q9W/ifQZB6FtW71by1eNQ7SqS3pvWYXHLCgCl19nhxfOJnWQR8Uccx7v9E11YhDuPIqD s2fl86F53qjjjfF4WjQUSS0weDy8Z70KXokdRdl91dVYL+nfOUKzwcE3A4QSg/2Y7Bmx 5VwQyjIf2zCKuy6ujBoJKD4p13Kqhlhc89E96l/S6v+RPehqBFhf0p3xknYHPu7bwvDC AOXe+X7UupSgpjdBhFvA9gWiPgcwAiyFzISslSDhftwPTkb8wtZJrQc3t2YSThy4uOu7 uMsA==
X-Gm-Message-State: AElRT7G/QKBYxr2Z6Ze51o8jHYAALBYSSzvgjvHbc2T7mYxg1j8P5cbR MZdjh9mPS8I3lg1nRyuM5v7YSk5s
X-Google-Smtp-Source: AIpwx48j9yQmvKSfN3T72wPsoZZZHlUi8xtnMgQMXzrCYJhFAZcyswcz4uTlx7OMQsZ89JFcZjE5OQ==
X-Received: by 10.99.114.1 with SMTP id n1mr12510209pgc.107.1522861555922; Wed, 04 Apr 2018 10:05:55 -0700 (PDT)
Received: from mail-pl0-f48.google.com (mail-pl0-f48.google.com. [209.85.160.48]) by smtp.gmail.com with ESMTPSA id w17sm4209785pfa.125.2018.04.04.10.05.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 10:05:55 -0700 (PDT)
Received: by mail-pl0-f48.google.com with SMTP id c21-v6so11297593plz.10; Wed, 04 Apr 2018 10:05:54 -0700 (PDT)
X-Received: by 2002:a17:902:7185:: with SMTP id b5-v6mr19348304pll.221.1522861554782;  Wed, 04 Apr 2018 10:05:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.185.79 with HTTP; Wed, 4 Apr 2018 10:05:54 -0700 (PDT)
In-Reply-To: <2B936029-9DC7-491C-893F-AE6D05723E4B@cisco.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <CAD5OKxsWkCb=yE7D=-9uyO1Q8rx9R4uWMLOWRTLR72_GAkdNKg@mail.gmail.com> <CABcZeBMwmisiM0Vpc9Pr53wOPi=J6RAKiNiO8JEkPOtcTjOZvA@mail.gmail.com> <2B936029-9DC7-491C-893F-AE6D05723E4B@cisco.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 4 Apr 2018 13:05:54 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvzzTK0gu1VY=d3XPLW117ffDmX1mAOJFRFhO_-F-e=4w@mail.gmail.com>
Message-ID: <CAD5OKxvzzTK0gu1VY=d3XPLW117ffDmX1mAOJFRFhO_-F-e=4w@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: Eric Rescorla <ekr@rtfm.com>, Ben Campbell <ben@nostrum.com>, Adam Roach <adam@nostrum.com>,  mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>,  "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, RTCWeb IETF <rtcweb@ietf.org>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000003d981056908d6c2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/82LZz9mMnEx0rfb7Izd5W0s5Ya8>
Subject: Re: [MMUSIC] [Ice] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 17:06:12 -0000

--00000000000003d981056908d6c2
Content-Type: text/plain; charset="UTF-8"

On Wed, Apr 4, 2018 at 12:47 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>
wrote:

>
> On Apr 3, 2018, at 11:43 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>
> I want to do whatever is necessary to remove the normative dependency from
> JSEP to SIP
>
>
> I think a big part of the RTCWeb/WebRTC community would strongly object to
> JSEP normatively depending on SIP.
>

Do you have any issues with dependency on RFC5245 and the portion of it
which went into draft-mmusic-ice-sip-sdp? Both define SIP procedures in
addition to offer/answer. We are kind of dealing with the same thing here.
Other drafts, like mmusic-dtls-sdp have SIP consideration sections in them.
It did not seem to cause any issues either.

As I have mentioned earlier, I think,  trickle-ice-sip should internally
clearly identify generic offer/answer SDP procedures and SIP specific
considerations. Once it is done it would be no different then all the other
offer/answer drafts we put together recently.
_____________
Roman Shpount

--00000000000003d981056908d6c2
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" data-smartmail=3D"gmail_signature">On Wed, Apr 4, 2018 at 12:47 PM, Cu=
llen Jennings (fluffy) <span dir=3D"ltr">&lt;<a href=3D"mailto:fluffy@cisco=
.com" target=3D"_blank">fluffy@cisco.com</a>&gt;</span> wrote:<br></div></d=
iv><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;line-break:after-white-space"><span clas=
s=3D""><div><br>
<blockquote type=3D"cite">
<div>On Apr 3, 2018, at 11:43 AM, Eric Rescorla &lt;<a href=3D"mailto:ekr@r=
tfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wrote:</div>
<div><div style=3D"font-family:Helvetica;font-size:12px;font-style:normal;f=
ont-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align=
:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:=
0px;text-decoration:none"><br class=3D"m_-7218414645586878398Apple-intercha=
nge-newline">
I want to do whatever is necessary to remove the normative dependency from =
JSEP to SIP</div>
</div></blockquote></div><br>
</span><div>I think a big part of the RTCWeb/WebRTC community would strongl=
y object to JSEP normatively depending on SIP.=C2=A0</div>
</div>

</blockquote></div><br></div><div class=3D"gmail_extra">Do you have any iss=
ues with dependency on=20

<a name=3D"ref-RFC5245" id=3D"gmail-ref-RFC5245" style=3D"color:rgb(34,34,3=
4);font-family:arial,sans-serif;font-style:normal;font-variant-ligatures:no=
rmal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text=
-decoration-color:initial;font-size:13.3333px">RFC5245 and the portion of i=
t which went into</a>

draft-mmusic-ice-sip-sdp? Both define SIP procedures in addition to offer/a=
nswer. We are kind of dealing with the same thing here. Other drafts, like =
mmusic-dtls-sdp have SIP consideration sections in them. It did not seem to=
 cause any issues either.</div><div class=3D"gmail_extra"><br></div>As I ha=
ve mentioned earlier, I think,=C2=A0 trickle-ice-sip should internally clea=
rly identify generic offer/answer SDP procedures and SIP specific considera=
tions. Once it is done it would be no different then all the other offer/an=
swer drafts we put together recently.<div class=3D"gmail_extra">

<div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:sm=
all;font-style:normal;font-variant-ligatures:normal;font-variant-caps:norma=
l;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(=
255,255,255);text-decoration-style:initial;text-decoration-color:initial"><=
div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><br=
 class=3D"gmail-Apple-interchange-newline">

<br></div></div>

--00000000000003d981056908d6c2--


From nobody Wed Apr  4 10:23:21 2018
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 2A73D126C22; Wed,  4 Apr 2018 10:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pgBW-Ku13g9; Wed,  4 Apr 2018 10:23:11 -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 2D3F112D775; Wed,  4 Apr 2018 10:23:11 -0700 (PDT)
Received: from [10.0.1.91] (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 w34HN5U0025759 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 4 Apr 2018 12:23:06 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6382D4F8-A6C7-47D0-BE19-DAA943570D77"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Wed, 4 Apr 2018 12:23:04 -0500
In-Reply-To: <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, mmusic-chairs@ietf.org, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org
To: Peter Saint-Andre <stpeter@mozilla.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3tlTD31IgvnOX7OXP6kvTn7gq9E>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 17:23:14 -0000

--Apple-Mail=_6382D4F8-A6C7-47D0-BE19-DAA943570D77
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 4, 2018, at 11:07 AM, Peter Saint-Andre <stpeter@mozilla.com> =
wrote:
>=20
> On 4/3/18 2:41 PM, Suhas Nandakumar wrote:
>>=20
>>=20
>> On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com
>> <mailto:ben@nostrum.com>> wrote:
>>=20
>>=20
>>=20
>>> On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com =
<mailto:stpeter@mozilla.com>> wrote:
>>>=20
>>> On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
>>>> Just to complete, ice-bis doesn=E2=80=99t normatively reference =
ice-sip-SDP
>>>> draft when it moved to using =E2=80=9Cusages =E2=80=9C indirections =
for signaling protocols.
>>>>=20
>>>>=20
>>>> Trickle ice can use similar approach and refer to trickle-sip as =
usage
>>>> for trickle.
>>>=20
>>> It already does. That's why we pulled all the SDP/SIP stuff out of
>>> draft-ietf-ice-trickle.
>>=20
>>    I assume Suhas meant separating the SDP stuff from the SIP stuff. =
(I
>>    also assume he will correct me if I am wrong.)
>>=20
>>=20
>> That's right Ben .. I was just thinking minimal localized changes =
(thus
>> small time to get new draft done) and then asking trickle, =
trickle-sip to
>> refer to the new one. (work done to refer is much smaller for these
>> drafts that are at the very end of approval journey)
>>=20
>> I do agree with Adam, no matter what version of the proposal we pick,
>> there is some work that needs to be done and we
>> should do it.
>=20
> These documents are on the telechat tomorrow. Are we proposing to =
delay
> consideration by the IESG while we get this mess sorted out? ;-)

Hi Peter,

I currently plan to leave it on. We may discuss a way forward on the =
telechat. Also, I=E2=80=99d like to get feedback on the rest of the =
draft(s) from the other ADs sooner than later.

Thanks!

Ben.

--Apple-Mail=_6382D4F8-A6C7-47D0-BE19-DAA943570D77
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrFCfgACgkQgFZKbJXz
1A3/VBAAqDvaaL3WVTzh4ooufivb/cH+C7BHR6W3v1FcnQAVsfQR8XT4WysJIm38
Ks7llDVLN3XtybXBrGeTM6VALocI/XuYS2Rqyr5q34WnQhcdJA5RDvKIrV+qBMrU
sPFmjX85NzRwJv3zGlXUsjdSjMysrdySqyBqr686g/pLMufUXmgAxoKppyNQWHBs
lhSCXjvoJKdDxLvnny34e7hIM2/IQvrA01R1ThZsbg0a3ppSnc1aUbpxtHA41Pq3
EINCTjT4idSMi1MijCCGg29yITaLizAGbZi+gwIG0AeVJcguOYDK0u5XsSkBCD5F
QML8MOZri0OjM5ss3vNr9NspcrUYxc3MJcyP1KN7IgAljP258ygTuwksgwcUZqU4
NnG3UguWfxYNDsUUM6vnap6g3oYIQHrk4r6XKEwOKkFjs19Owu0PZc4Ipn0RTmzn
7ZRiR5Qsme9RPZeFwsteiYLtxPtciplvMny0QdlvdSojVEwAK+5Be7T52oovx8tS
NzcVOzQZI5/Q10OZoQ0iiWEojvHWQNsbGkSDxiGy+LSbgeBEJos3PbAbFox5b/zd
gvNyhKMNIIp/rTT+xrn/GNFGk79vIIbHMJGqOqKIspX9x48jwJO1FSZVFHNeApYV
SQkn3/s+i7RWNFckWL/tvE09dC6MGLZbE3nHX8V9IXpx4sn1lZU=
=sfbx
-----END PGP SIGNATURE-----

--Apple-Mail=_6382D4F8-A6C7-47D0-BE19-DAA943570D77--


From nobody Wed Apr  4 12:13:00 2018
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 AEFB512DA68; Wed,  4 Apr 2018 12:12:58 -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 usadmCaEnHG1; Wed,  4 Apr 2018 12:12:55 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 49722126D45; Wed,  4 Apr 2018 12:12:55 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id o23so23087560wmf.0; Wed, 04 Apr 2018 12:12:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=H4pJJXOcO5GL4ZkG6n8vNAD6a7YKiVdKbkCKoBT5Zuc=; b=uRFrk7jjn+1wwq7MIu4HbZx1ElN2AYQ4OqUq0glF9rP+HPq3dCLeb7K7tkpQrYT6+g 6LMrM3N/Foq8vbeHkgrxW88CX9H03OY1v560SB9Iz56qeSXF4V14/hLoqQW+4TnlRcuN IeYjcxL9usPEyL5CeDtdvRmIIL3+GY9fMdem/zom1vxGCxTvQheuscYfw+BsiOuFKdsZ vsQN/4DVuMrKHsItV02Z4CP5fF5tBsrbbT0yJgXUrZDjzlNAVO+rllSfo9VURwBPK08/ 9ithjTuVSrOa24AGi1vxHy2kG9pt7VTo6BNVredm371IRd5XbXw4jj+QUKXQ+XXP118a +2bA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=H4pJJXOcO5GL4ZkG6n8vNAD6a7YKiVdKbkCKoBT5Zuc=; b=Q9jBiEOLw0luOeypYqbxae7J6MZtqggQAPYlDlSu8B2EKvBQKJY0lAp6AmbYm87Q3l 18aXWTBTMGzDj76SHU61BRyKGHp4GVX/jJmPaqD0U0zsNSlWraKENQ/KuD0QQArqvm+e HVSMhFD0jAPeMrJuTi22m4JXfXP7elEsF0PJsQHba+GftIREWwAiBX0xF01lajv+S9vE rKkVz8VLx4JtVTye0R5Lq5cqfxljX5XIsvrQtFCrI9uF6dSuKVCSvDKlYaKnKATWPiCF Zq/eyAOCnHgY+TXTTvOnH3Soqrbyca43SZ+zkaaGvgcoDgHbV7tb1YNnJuHEN41GEntM b/4w==
X-Gm-Message-State: ALQs6tBsKOZtTsDP64Hrr6s5mjzWIULNe3af0SjXryP6rj7J8tu68WX+ QJlhvmu4rxCaRwenDOKN0yYLkoUOfuI=
X-Google-Smtp-Source: AIpwx49BnVD9B0wEBCx4lFs+sOTSrufyjh7LA4laMSNb9Dg7a6OYbM1b73yHQ27k6EiwC+LSsrkh2g==
X-Received: by 10.28.108.1 with SMTP id h1mr6443450wmc.72.1522869172612; Wed, 04 Apr 2018 12:12:52 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id a205sm3829853wmf.18.2018.04.04.12.12.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 12:12:51 -0700 (PDT)
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com>
Date: Wed, 4 Apr 2018 21:12:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/YtJL2ZM9P3YWTdRI1fjXdF8_0fo>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 19:12:59 -0000

Adam,
thanks for the comments.
As your DISCUSS points are already treated on other threads,
There are  just some replies in the comment section below.


On 2018-04-03 09:29, Adam Roach wrote:
> Adam Roach has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks to everyone who worked on this document. I have a couple of concerns that
> need to be cleared up before the document can move forward.
>
> ---------------------------------------------------------------------------
>
> §4.3.4 discusses the interaction of 3PCC with the trickle ICE mechanism.
> Unfortunately, the diagrams used in this section do not show a 3PCC signaling
> flow; they show a two-party call flow with an offerless INVITE. A 3PCC call flow
> would necessarily involve a 3PCC controller sending an offerless INVITE to one
> party, receiving an offer from that party (typically in a reliable provisional
> response or in a 200 OK), and then sending an INVITE to the other party
> containing that offer.
>
> The text in this section matches the diagrams, and consequently does not appear
> to be an analysis of 3PCC behavior. It is an analysis of two-party offerless
> INVITE behavior.
>
> If this section remains, it needs to be substantially re-worked: the diagrams
> need to show three parties, with a 3PCC controller performing the controlling
> role as described in RFC 3725. While I haven't stepped through the implications
> for Trickle ICE when a controller is actually involved and is moving offers and
> answers around between different message types, I suspect that the analysis in
> here is substantially different once this starts happening.
>
> I would personally be okay if the entire section were removed; however, I
> have no desire to override working group consensus regarding the value of a
> section dealing with 3PCC considerations.
>
> ---------------------------------------------------------------------------
>
> The second issue doesn't necessarily pertain to this document per se as much
> as it does the interaction among this document, draft-ietf-ice-trickle (Trickle
> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and draft-ietf-rtcweb-jsep
> (JSEP). The problem doesn't lie with any single document, but in the overall
> result of how they're currently structured.
>
> JSEP (in the RFC editor queue) refers to the "a=end-of-candidates" SDP attribute
> as appearing in Trickle ICE, section 9.3, which was true at one point in time.
> Somewhere along the line, this attribute's definition was moved from there
> into this document.
>
> There are several ways to fix this, each with their own drawbacks:
>
> 1. Move the SDP syntax for "a=end-of-candidates" back into the Trickle ICE
>     draft. Drawback: Trickle ICE does not currently define any normative SDP
>     behavior; and, in fact, could work in a system that doesn't use SDP at all.
>
> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant from the
>     perspective that ICE SDP defines SDP syntax for ICE in general (for both
>     SIP and JSEP), and such a move aggregates all of the SDP syntax into a
>     single document that is already necessary to reference from any document
>     that uses SDP for Trickle ICE. Drawback: the document doesn't presently
>     discuss Trickle ICE at all, and this would require a somewhat awkward
>     section that basically says "If you use [Trickle ICE] with SDP, the syntax
>     for the end-of-candidate marker is..."
>
> 3. Change JSEP to normatively depend on this document for the
>     "a=end-of-candidates" syntax. Drawback: This document is extremely
>     SIP-specific, while JSEP is based solely on RFC 4566 syntax and RFC 3264
>     behavior, independent of any SIP semantics.  Forcing JSEP to normatively
>     depend on a SIP specific document for a simple attribute syntax definition
>     seems to be letting the tail wag the dog.
>
> I believe that #2 is the least inelegant option, but I'm open to #1 and #3.
> However, The *current* situation -- in which JSEP normatively points to a
> document from which the text is cites has been removed out from under it -- is
> clearly wrong.
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> §4.1.4:
>
>>   If the initial Answer included the attribute a=ice-options:trickle,
>>   the Offerer MUST be prepared for receiving trickled candidates later
>>   on.
> I don't think this makes sense. If the initial *Offer* includes that option,
> then the Offerer must be prepared to receive trickled candidates, even before
> the Answer arrives. Figure 6 shows an example of this. I believe that the
> paragraph I quote above needs to be entirely removed, as it may lead
> implementors to incorrectly assume that they can't get trickled candidates prior
> to an Answer.
>
> ---------------------------------------------------------------------------
Will remove
>
> §4.3:
>
>>     o  The dialog at both peers MUST be in early or confirmed state.
> This makes no sense. Dialogs exist in precisely two states, ever: early or
> confirmed. Prior to "early," they don't exist. The only exit from "confirmed" is
> destruction. (See RFC 3261 §12).
>
> I think what this means to say is "A dialog MUST have been created between the
> peers."
>
> ---------------------------------------------------------------------------
I'll change to your wording
>
> §4.3.2:
>
>>   These retransmissions MUST
>>   cease on receipt of an INFO request carrying a 'trickle-ice' Info
>>   Package body or on transmission of the Answer in a 2xx response.
> Why does this require that specific INFO to stop retransmission? The only
> requirement is that the answerer knows that the offerer has received the
> provisional response. The offerer cannot send post-INVITE requests to the
> answerer until a dialog is established, and the only ways a dialog can be
> established at the offerer is receipt of a provisional or final response. So, as
> soon as you get *any* request from the offerer, you know that the provisional
> response has arrived.
>
> I think this passage means to say "These retransmissions MUST cease on receipt
> of any in-dialog request from the offerer. The offerer cannot send in-dialog
> requests until it receives a response, so the arrival of such a request proves
> that the response has arrived."
>
> ---------------------------------------------------------------------------
Sure, any other request will do the trick as well. However, as it is not 
guaranteed that a request
other than said INFO is sent, I'd prefer to say

"These retransmissions MUST cease on receipt
of an INFO request carrying a 'trickle-ice' Info
  Package body, on receipt any in-dialog request from the offerer or on transmission
of the Answer in a 2xx response. The offerer cannot send in-dialog
requests until it receives a response, so the arrival of such a request proves
that the response has arrived."


> §4.3.2:
>
>>   The Offerer MUST send a Trickle ICE INFO request as soon as it
>>   receives an SDP Answer in an unreliable provisional response.  This
>>   INFO request MUST repeat the candidates that were already provided in
>>   the Offer (as would be the case when Half Trickle is performed or
>>   when new candidates have not been learned since then).
> It is probably worth mentioning that it's possible that this INFO contains no
> candidates, depending on how the offerer gathers its candidates and how long it
> takes to do so.
>
> ---------------------------------------------------------------------------
Will add
>
> §4.3.3:
>
>>   These retransmissions MUST cease on receipt
>>   of an INFO request or on transmission of the Answer in a 2xx
>>   response.
> Same comment as above for §4.3.2.
>
> ---------------------------------------------------------------------------
sane answer
>
> §4.3.4:
>
>>   As specified in Section 4 this offerless INVITE
>>   MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
>>   header field in order to indicate support for Trickle-ICE to the
>>   Offerer (at the User Agent Server (UAS)).
> How does the 3PCC controller know to include this option tag? Is it simply
> indicating that the 3PCC controller supports the Trickle mechanism? If so,
> what happens if the second party (the one who receives the offer in an INVITE)
> doesn't support Trickle ICE? This is one of the sharper corner cases that I
> think arises when you go to fix the analysis I describe in my DISCUSS above.
>
> ---------------------------------------------------------------------------
Well, the 3PCC is usually in the signaling path and can detect if 
Trickle-ICE is supported at the parties...
However there will certainly appear other corner cases that are not yet 
covered in that section.
Thus, like Ben, I'd also be happy to remove that section, if we get WG 
consensus for doing so.
@Fleming, would you be OK to ask for that?
>
> §4.4:
>
>>      a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 5000 typ srflx
>>          raddr 2001:db8:a0b:12f0::1 rport 8998
> Thanks for the IPv6 example; however, I have a *lot* of heartburn with the
> selection of an example that demonstrates IPv6 NAT behavior. Since ICE's srflx
> behavior is fundamentally tied to IPv4 NATs (and should not be an issue with
> IPv6, as NATs are unnecessary), I think it's okay for the srvflx examples to go
> ahead and show IPv4 addresses.
>
> I *really* don't want to publish an RFC that demonstrates NATting of IPv6.
I concur with Peter's response on your same comment on draft-ice-trickle 
and use another candidate type for IPv6
>
> ---------------------------------------------------------------------------
>
> §4.4:
>
>>   An "a=end-of-candidates" attribute, preceding any pseudo "m=" line,
>>   indicates the end of all trickling from that agent, as opposed to end
>>   of trickling for a specific "m=" line, which would be indicated by a
>>   media level "a=end-of-candidates" attribute.
> I finally did figure out what this meant, but it's confusing. The use of "any"
> in the phrase "any pseudo 'm=' line" implies that the following sdpfrag would
> qualify:
>
>        a=ice-pwd:asd88fgpdd777uzjYhagZg
>        a=ice-ufrag:8hhY
>        m=audio 9 RTP/AVP 0
>        a=mid:1
>        a=candidate:1 1 UDP 2130706431 2001:db8:a0b:12f0::1 5000 typ host
>        a=candidate:1 2 UDP 2130706431 2001:db8:a0b:12f0::1 5001 typ host
>        a=end-of-candidates
>        m=audio 9 RTP/AVP 0
>        a=mid:2
>        a=candidate:1 1 UDP 2130706431 2001:db8:a0b:12f0::1 6000 typ host
>        a=candidate:1 2 UDP 2130706431 2001:db8:a0b:12f0::1 6001 typ host
>
> The end-of-candidates *does* appear before the second pseudo "m=" line, which is
> one of the lines (thereby satisfying the "any" criteria).
>
> I think you mean "preceding the first pseudo 'm=' line..."
Will change to your wording
>
> This is true later in the section also:
>
>>   will not send any further candidates.  When included at session
>>   level, i.e. before any pseudo "m=" line, this indication applies to
> ---------------------------------------------------------------------------
>
> §4.4:
>
>>   Note: At the time of writing this specification there were ongoing
>>   discussions if a functionality for removing already exchanged
>>   candidates would be useful.  Such a functionality is out of the scope
>>   of this specification and most likely needs to be signaled by means
>>   of a yet to be defined ICE extension, although it could in principle
>>   be achieved quite easily, e.g. without anticipating any solution by
>>   simply omitting a previously sent candidate from a subsequent INFO
>>   request.  However, if an implementation according to this
>>   specification receives such an INFO request with a missing candidate
>>   it would have to treat that as an exceptional case.  Implementing
>>   appropriate recovery procedures at the receiving side is advisable
>>   for this situation.  Ignoring that a candidate was missing might be a
>>   sensible strategy.
> This seems like an interop nightmare. If you want a note about this possibly
> being included in the future, please simply indicate that such an ability will
> need to be explicitly signaled. Don't imply that implementations might get SDP
> that violates the behavior defined in this document in some ill-defined way,
> and just need to kind of gracefully deal with it, even if we don't really know
> what it means at this point in time. There's no sensible way to code for that.
>
> ---------------------------------------------------------------------------
>
> §4.4:
>
>>      a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 5000 typ srflx
>>         raddr 2001:db8:a0b:12f0::1 rport 8998
>>      a=candidate:2 2 UDP 1694498815 2001:db8:a0b:12f0::3 5001 typ srflx
>>         raddr 2001:db8:a0b:12f0::1 rport 8998
> ...
>>      a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 6000 typ srflx
>>         raddr 2001:db8:a0b:12f0::1 rport 9998
>>      a=candidate:2 2 UDP 1694498815 2001:db8:a0b:12f0::3 6001 typ srflx
>>         raddr 2001:db8:a0b:12f0::1 rport 9998
> Same comment as above regarding IPv6 and NATs. Note that it would be Good and
> Helpful to show SDP with a mixture of IPv4 and IPv6 anyway.
Ok, I'll change the address family to IPv4 for the srvflx and add IPv4 
host candidates
>
> ---------------------------------------------------------------------------
>
> §5:
>
>>   SIP User Agents (UAs) that support and intend to use trickle ICE are
>>   required by [I-D.ietf-ice-trickle] to indicate that in their Offers
>>   and Answers using the attribute "a=ice-options:trickle" and MUST
>>   include the SIP option-tag "trickle-ice" in a SIP Supported: header
>>   field.
> Is this intended to imply that the option tag cannot be used in a Require header
> field? I don't think that's a good idea; however, if that is the working group's
> intention, please say so explicitly.
>
> Suggest "...in a SIP 'Supported' or 'Require' header field."
Ok. It wasn't intended to disallow usage of Require: Trickle-ice
>
> ---------------------------------------------------------------------------
>
> §5.1:
>
> This section discusses behavior in a walled garden. I'm generally fine with
> this, as long as the failure modes when someone starts adding doors to the
> walled garden are well-defined. I don't think this kind of provisioning is
> okay unless it has a requirement that Offerers assuming Trickle ICE support
> MUST include a "Require: trickle-ice" header field. That way, if the
> provisioned assumption of Trickle ICE support ends up being incorrect, the
> failure is (a) operationally easy to track down, and (b) recoverable by the
> client (i.e.: they can re-send the request without the "Require" header field
> and without the assumption of Trickle ICE support).
Ok. I could add (re-using some of your text):
" An Offerer assuming Trickle ICE support MUST include a "Require: 
trickle-ice" header field.
That way, if the provisioned assumption of Trickle ICE support ends up 
being incorrect,
the failure is (a) operationally easy to track down, and (b) recoverable 
by the client,
i.e., they can re-send the request without the Require: header field and 
without the assumption of Trickle ICE support."
> ---------------------------------------------------------------------------
>
> §6:
>
>>   This INFO request indicates that the Answerer supports and uses RTP
>>   and RTCP multiplexing as well.  It allows the Offerer to omit
>>   gathering of RTCP candidates or releasing already gathered RTCP
>>   candidates.
> It's not clear how this "releasing already gathered RTCP candidates" interacts
> with the requirement in §4.4:
>
>>   In other words, the sequence
>>   of a previously sent list of candidates MUST NOT change in subsequent
>>   INFO requests and newly gathered candidates MUST be added at the end
>>   of that list.
> So, if I had already trickled candidates for the RTCP component of a connection
> and *then* got an INFO from the Answerer indicating that it supports
> multiplexing, does that mean I free the resources and exclude them from future
> INFO messages? That seems to contravene the §4.4 requirement. Or do I free them
> but continue to include them? I suppose that's okay (maybe?), but it's
> extremely counterintuitive, and would need to be called out explicitly if you
> expect implementors to get it right.
Well, the implicit assumption was that the RTCP might have been 
gathered, but not yet been sent to the peer.
If there were sent in a previous INFO they would still need to be included.
I will call this out explicitly
>
> ---------------------------------------------------------------------------
>
> §7:
>
>>   A Trickle Answerer SHOULD include an "a=group: BUNDLE" attribute
>>   [I-D.ietf-mmusic-sdp-bundle-negotiation] in the application/trickle-
>>   ice-sdpfrag body if it supports and uses bundling.
> This needs to clearly indicate that this needs to be included at the session
> level (rather than the media level).
OK
>
> ---------------------------------------------------------------------------
>
> §7:
>
>>   The Offerer can use this information e.g. for stopping the gathering
>>   of candidates for the remaining "m=" lines in a bundle and/or for
>>   freeing corresponding resources.
> Same comment as for §6, above (regarding interaction with the requirement from
> §4.4)
Same handling envisaged as above
>
> ---------------------------------------------------------------------------
>
> §7:
>
>>       a=group:BUNDLE foo bar
>>       a=ice-pwd:asd88fgpdd777uzjYhagZg
>>       a=ice-ufrag:8hhY
>>       m=audio 9 RTP/AVP 0
>>       a=mid:foo
>>       a=rtcp-mux
>>       a=candidate:1 1 UDP 1658497328 2001:db8:a0b:12f0::3 5000 typ host
>>       m=audio 9 RTP/AVP 0
>>       a=mid:bar
> The presence of the second m= line here is confusing, given the following text
> from §4.4:
>
>>   Note, that there is no requirement that the Info request body
>>   contains as many pseudo m= lines as the Offer/Answer contains m=
>>   lines, nor that the pseudo m= lines be in the same order as the
>>   m=lines that they pertain to.  The correspondence can be made via the
>>   "a=mid:" attributes.
> The §4.4 text strongly implies that it is nonsensical to include an m= section
> without candidates. Is the example in §7 intended to imply that the section
> needs to be included because its mid is mentioned in the "a=group:BUNDLE" line?
> If so, please say so. If not, please remove the second m= section.
I'll remove
>
> ---------------------------------------------------------------------------
>
> §9.2:
>
> The syntax for "session-level-fields", "pseudo-media-descriptions", and
> "trickle-ice-attribute-fields" include extremely strict rules around ordering of
> fields (e.g., including ice-ufrag before ice-pwd would be syntactically
> invalid). That level of strictness seems unlikely to lead to interoperable
> implementations.
>
> If the intention is to be rigid in this fashion, please add prominent prose
> that warns implementors that fields MUST appear in the order specified, and
> that all other orders are invalid and MUST be rejected.
>
> If that's *not* your intention (and I suspect it isn't), then please fix the
> syntax definition to allow for arbitrary ordering of attributes in the same way
> as SDP does. For example:
>
>      session-level-fields = *(session-level-field CRLF)
>
>      session-level-field = bundle-group-attribute /
>                            ice-lite-attribute /
>                            ice-pwd-attribute /
>                            ice-ufrag-attribute /
>                            ice-options-attribute /
>                            ice-pacing-attribute /
>                            end-of-candidates-attribute /
>                            extension-attribute-fields
>                                   ; for future extensions
I'll change.
>
> ---------------------------------------------------------------------------
>
> §9.2:
>
> The syntax for "session-level-fields" implies that "ice-pwd" and "ice-ufrag" are
> mandatory at the session level. This seems to conflict with the text in §4.4:
>
>>   The "a=ice-pwd:" and "a=ice-ufrag:" attributes MUST appear at the
>>   same level as the ones in the Offer/Answer exchange.  In other words,
>>   if they were present as session-level attributes, they will also
>>   appear at the beginning of all INFO request payloads, i.e. preceding
>>   all pseudo "m=" lines.  If they were originally exchanged as media
>>   level attributes, potentially overriding session-level values, then
>>   they will also be included in INFO request payloads following the
>>   corresponding pseudo "m=" lines.
> The fix I propose above removes this implication that such attributes are
> mandatory at the session level; however, if you choose to fix it some other way,
> please ensure that the ABNF does not conflict with the normative language I
> quote above.
I'd go with your proposal
> ---------------------------------------------------------------------------
>
> §10.6:
>
> Same comment as for §5 above.
Ok. It wasn't intended to disallow usage of Require: trickle-ice.
>
> ---------------------------------------------------------------------------
>
> §10.9:
>
>>   If the INFO requests are sent on top of TCP, which is probably the
>>   standard way, this is not an issue for the network anymore, but it
>>   can remain one for SIP proxies and other intermediaries forwarding
>>   the SIP INFO messages.  Also, an endpoint may not be able to tell
>>   that it has congestion controlled transport all the way.
> This seems kind of blithe about congestion control, as it concedes that the INFO
> requests might end up on UDP at some point. Minimally, I would think that you
> want to require some minimum quarantine period between INFO requests (probably
> something in the range of 20 ms), during which any new candidates that are
> gathered are aggregated into the next INFO message.
I can add this
> ===========================================================================
>
> Nits:
>
> Expand "ICE" in the title.
>
> ---------------------------------------------------------------------------
>
> draft-ietf-mmusic-ice-sip-sdp has undergone a major restructuring since version
> 16; as a consequence, all notes of the form:
>
>>   [RFC EDITOR NOTE: The section 4.2.1.2.1 in above sentence is correct
>>   for version 16 of said I-D.  Authors need to cross-check during
>>   Auth48 since it could have have changed in the meantime.]
> ...are already out of date. It's probably worthwhile to fix these now, as they
> are (in my opinion) quite unlikely to change again; and the current misdirection
> makes it somewhat difficult to use the draft in its current form.
That note was intended for covering exactly this scenario and catch such 
numbering changes.
Will updated in the revision
>
> ---------------------------------------------------------------------------
>
> §4.1.3:
>
>>   If the Answerer includes candidates in its initial Answerer, it MUST
> "...initial Answer..."
thx
>
> ---------------------------------------------------------------------------
>
> §7:
>
>>   A Trickle Answerer SHOULD include an "a=group: BUNDLE" attribute
> Remove the space before "BUNDLE"
thx
>
> ---------------------------------------------------------------------------
>
> §11:
>
>>   Trickle ICE uses two mechanism for exchange of candidate information.
> "mechanisms"
thx

Thanks again for the thorough review!
Thomas
>


From nobody Wed Apr  4 12:40:57 2018
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 8F6CF126E64 for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 12:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CPRX6mdEMyUJ for <mmusic@ietfa.amsl.com>; Wed,  4 Apr 2018 12:40:53 -0700 (PDT)
Received: from mail-pl0-x22c.google.com (mail-pl0-x22c.google.com [IPv6:2607:f8b0:400e:c01::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 03066126DCA for <mmusic@ietf.org>; Wed,  4 Apr 2018 12:40:53 -0700 (PDT)
Received: by mail-pl0-x22c.google.com with SMTP id v5-v6so13545633plo.4 for <mmusic@ietf.org>; Wed, 04 Apr 2018 12:40:52 -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=xlj+GX5c+qKNaRAUKGPdOhfSdq4w9IAddJVWsH7ElNI=; b=rc9tRncJ0EfcUzRfaHf3hze0f5JxB0ZkmOA/DhFCBHxGxjTShlVeh53tde0XVs5D1g Divg+zJ83MbOU+ilA6YS0WMY/6dZUK2WQ51Z7B6rS7Ef4z0xB1pYoLw5Iwy8C27t4iY/ E3HAXIQIp7G62s2H7aY4iRmyJy/cv1tIkrjRVHx87MItOHIhhc++/iNr4rYR8jvK3+jQ gLUVgOPVpeMcuT3szlI9L3h3/XL4zrZ9TUR99SohX0vD+cu3wy6jJ9W3/iFYJ7XE7dnI +kx8AMWqqaNLi0fAbWpRWMmhCGIm+JDH8VuQUXb8ZFq+JCinNYzfZVjHlfjnmXYPhTx8 xHOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xlj+GX5c+qKNaRAUKGPdOhfSdq4w9IAddJVWsH7ElNI=; b=jcnjC8okW4qWIP9+c5DzTty7S84/SzJhRmbv3avgC10uZ8PZXnV/f7slY7FhiBFsae g3F+64kvxcAMmjKn7VxHTWkPLtVzpGHTMYdnCAxYe+peoTPLaDaxKelsgeh/oVcwM0VO R2x+OfJlknqbjBuOVSND0ox2u1H22ggV0GZk56jWnTeDVJAjoYCnlGvJARuf0QTIN2BW wYzHLbGpuc82hOmKxXrj4ZQQmg9O/FPCLlP9+YemI8mIHxBLwE7x/SlVdU4On/5p8Nto K6E/y+KviWbPuGvSM+9nn+LvJD0Gd/Z222AhuWDzPoQFy4MJ5PFad7l1PvwQCdxEuh+W OtSQ==
X-Gm-Message-State: AElRT7HnJ1+w6nT/ISXm4zbIPJnqYe5ynVwB3QBzLZHHVfEAbDLhqG/3 uRS6mMlTQ3LctadbdSvqSvj3sZSu
X-Google-Smtp-Source: AIpwx48ZGHqeMiWfCzkeTarur5qowgWVx7Slu9FDZHnHXzEAvaKXTTE1C962Y5dLN2ruSqus0RZxaQ==
X-Received: by 2002:a17:902:8545:: with SMTP id d5-v6mr19647627plo.20.1522870852459;  Wed, 04 Apr 2018 12:40:52 -0700 (PDT)
Received: from mail-pl0-f44.google.com (mail-pl0-f44.google.com. [209.85.160.44]) by smtp.gmail.com with ESMTPSA id x76sm12735449pfi.151.2018.04.04.12.40.51 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 12:40:51 -0700 (PDT)
Received: by mail-pl0-f44.google.com with SMTP id 91-v6so15536420pld.3 for <mmusic@ietf.org>; Wed, 04 Apr 2018 12:40:51 -0700 (PDT)
X-Received: by 2002:a17:902:8501:: with SMTP id bj1-v6mr20303768plb.239.1522870851111;  Wed, 04 Apr 2018 12:40:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.160.14 with HTTP; Wed, 4 Apr 2018 12:40:50 -0700 (PDT)
In-Reply-To: <3453aecf-6fce-500f-a4c6-df039ea5d836@cisco.com>
References: <CAMRcRGQx2F8gYrkq7Pbq0RTYpUa+w+q2vnWzsZxmL-zq8j9YFw@mail.gmail.com> <a39fb778-43f2-67a0-c269-6e653e802281@cisco.com> <CAMRcRGSke2S+MDe8M+7J28naRc=o7us3P=mPTzsittSr0hCRqw@mail.gmail.com> <CAMRcRGQZnWytKkap9kXPh0Zq4fJXmwArvPny0fNK5KWYJ=uThA@mail.gmail.com> <CAD5OKxuHnOROHnBmT=w4e=PK85BFeNZdTnYNdNZ0J7DJafdSJQ@mail.gmail.com> <CAMRcRGSZdZHhaNXba1_A_ASrvTueEX23bq1oTeAtRO9pgCtMwg@mail.gmail.com> <3453aecf-6fce-500f-a4c6-df039ea5d836@cisco.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 4 Apr 2018 15:40:50 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvo01xZNcfgg1J9H_z2aVKV=seEYLsZJyKdzp3j1413nA@mail.gmail.com>
Message-ID: <CAD5OKxvo01xZNcfgg1J9H_z2aVKV=seEYLsZJyKdzp3j1413nA@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: mmusic WG <mmusic@ietf.org>, Flemming Andreasen <fandreas@cisco.com>
Content-Type: multipart/alternative; boundary="0000000000001e93ea05690b008d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qd2syxQYcGyTz5bA2-yOnieEov0>
Subject: Re: [MMUSIC] ice-sip-sdp-19: Flemming's comment on Section 3.2.5 on ICE Mismatch
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 19:40:55 -0000

--0000000000001e93ea05690b008d
Content-Type: text/plain; charset="UTF-8"

Hi All,

I think I need to try to provide some background to this section of the
specification.

First of all, address provided in c= line and port in m= line together with
address in rctp SDP attribute (or address from c= line and port from m=
line +1) are refereed to as default candidates. These are the addresses
which will be used if answering end point would not understand ICE and RFC
3264 procedures were used.

Section 5.1 of RFC 5245 is there in order to support SIP ALG or SIP aware
firewalls (which are evil -- https://wiki.freeswitch.org/wiki/ALG). The
assumption in this section is if the SIP ALG is present and modified the
session description, ICE nomination should not happen and addresses from
default candidates should be used. Also, in order to indicate to the
offerer that this happened, ice-mismatch attribute needs to be added the
answer, so that offerer will not follow ICE nomination procedures and use
RFC 3264 procedures as well.

In practice following this guidance is typically the worst thing that you
can do. Procedure which is the most likely to succeed is to add
address/ports from c=/m= line and rtcp SDP attribute to the list of
candidates, if they are not already there and proceed with ICE nomination.
Do not insert ice-mismatch in the answer in order not to confuse the
offerer. This way, if SIP ALG works, then ICE nomination process will
verify the addresses that SIP ALG inserted. If SIP ALG is broken (as it
almost always is), then correct candidate will be picked via the normal ICE
process.

Even better option is to use secure communications channel for signaling
and make sure SDP is not modified by ALG.

Furthermore, a fair number of implementations (including some WebRTC and
trickle ice), insert c=IN IP4 0.0.0.0 and port 9 in m= line even when ICE
candidates are present. Based on the RFC5245 text this causes ICE mismatch.

To conclude, at the very least, I would suggest making the whole procedure
of matching candidates to addresses in c= and m= lines and rtcp SDP
attribute optional so that devices which do not do this are still
compliant. Better yet, add default candidates to candidate list, if these
addresses did not match any of the candidates and do not send ice-mismatch,
since it is more likely to succeed.

Answering some of the Flemming's questions:

- Which default candidates are we referring to ?

Default candidates in the offer. Default candidates are candidates defined
in c= and m= lines of SDP and in rtcp SDP attribute i.e. default
destination for this m= line if this end point was not ICE aware and RFC
3264 procedures were used. See
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-2

- If they were from the offer SDP, then how can the answerer create
permissions in the offerer's TURN server ?

If answerer's default candidates are TURN candidates, then answerer MUST
create permissions in the answerer's TURN server for the IP addresses from
offer default candidates. The intent there is that answerer will
communicate through answerer's TURN server with addressees/ports in c= and
m= line and rtcp attribute from the offer.

- I guess that means we are actually talking about the answerers default
candidates, which seems like a somewhat convoluted way of saying that if
the answerer is using a TURN server for its media stream, then it needs to
create permissions for whatever the default candidate is in the offer SDP
(whether relayed or not), or am I missing something ? In either case, some
clarification is needed here.

Yes. You are correct and clarification is needed.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr">Hi All,<div><br></div><div>I think I need to try to provid=
e some background to this section of the specification.</div><div><br></div=
><div>First of all, address provided in c=3D line and port in m=3D line tog=
ether with address in rctp SDP attribute (or address from c=3D line and por=
t from m=3D line +1) are refereed to as default candidates. These are the a=
ddresses which will be used if answering end point would not understand ICE=
 and RFC 3264 procedures were used.=C2=A0</div><div><br></div><div>Section =
5.1 of RFC 5245 is there in order to support SIP ALG or SIP aware firewalls=
 (which are evil -- <a href=3D"https://wiki.freeswitch.org/wiki/ALG">https:=
//wiki.freeswitch.org/wiki/ALG</a>). The assumption in this section is if t=
he SIP ALG is present and modified the session description, ICE nomination =
should not happen and addresses from default candidates should be used. Als=
o, in order to indicate to the offerer that this happened, ice-mismatch att=
ribute needs to be added the answer, so that offerer will not follow ICE no=
mination procedures and use RFC 3264 procedures as well.</div><div><br></di=
v><div>In practice following this guidance is typically the worst thing tha=
t you can do. Procedure which is the most likely to succeed is to add addre=
ss/ports from c=3D/m=3D line and rtcp SDP attribute to the list of candidat=
es, if they are not already there and proceed with ICE nomination. Do not i=
nsert ice-mismatch in the answer in order not to confuse the offerer. This =
way, if SIP ALG works, then ICE nomination process will verify the addresse=
s that SIP ALG inserted. If SIP ALG is broken (as it almost always is), the=
n correct candidate will be picked via the normal ICE process.</div><div><b=
r></div><div>Even better option is to use secure communications channel for=
 signaling and make sure SDP is not modified by ALG.</div><div><br></div><d=
iv>Furthermore, a fair number of implementations (including some WebRTC and=
 trickle ice), insert c=3DIN IP4 0.0.0.0 and port 9 in m=3D line even when =
ICE candidates are present. Based on the RFC5245 text this causes ICE misma=
tch.</div><div><br></div><div>To conclude, at the very least, I would sugge=
st making the whole procedure of matching candidates to addresses in c=3D a=
nd m=3D lines and rtcp SDP attribute optional so that devices which do not =
do this are still compliant. Better yet, add default candidates to candidat=
e list, if these addresses did not match any of the candidates and do not s=
end ice-mismatch, since it is more likely to succeed.<br><div class=3D"gmai=
l_extra"><br></div><div class=3D"gmail_extra">Answering some of the Flemmin=
g&#39;s questions:</div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">

<span style=3D"color:rgb(0,0,0);font-family:arial,sans-serif;font-size:12.8=
px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal=
;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;tex=
t-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(2=
55,255,255);text-decoration-style:initial;text-decoration-color:initial;flo=
at:none;display:inline">- Which default candidates are we referring to ?<sp=
an>=C2=A0</span></span></div><div class=3D"gmail_extra"><br></div><div clas=
s=3D"gmail_extra">Default candidates in the offer. Default candidates are c=
andidates defined in c=3D and m=3D lines of SDP and in rtcp SDP attribute i=
.e. default destination for this m=3D line if this end point was not ICE aw=
are and RFC 3264 procedures were used. See=C2=A0<a href=3D"https://tools.ie=
tf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-2">https://tools.ietf.=
org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-2</a></div><div class=3D"=
gmail_extra"><br style=3D"font-family:arial,sans-serif;font-style:normal;fo=
nt-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter=
-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-=
space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decora=
tion-style:initial;text-decoration-color:initial"><span style=3D"color:rgb(=
0,0,0);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font=
-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-s=
pacing:normal;text-align:start;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decorati=
on-style:initial;text-decoration-color:initial;float:none;display:inline">-=
 If they were from the offer SDP, then how can the answerer create permissi=
ons in the offerer&#39;s TURN server ?<span>=C2=A0</span></span></div><div =
class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">If answerer&#39;=
s default candidates are TURN candidates, then answerer <span style=3D"colo=
r:rgb(0,0,0);font-family:arial,sans-serif;font-size:12.8px;font-style:norma=
l;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;le=
tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wh=
ite-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-de=
coration-style:initial;text-decoration-color:initial;float:none;display:inl=
ine">MUST create permissions in the answerer&#39;s TURN=C2=A0</span><span s=
tyle=3D"color:rgb(0,0,0);font-family:arial,sans-serif;font-size:12.8px;font=
-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-w=
eight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-trans=
form:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,=
255);text-decoration-style:initial;text-decoration-color:initial;float:none=
;display:inline">server for the IP addresses from offer default candidates.=
 The intent there is that answerer will communicate through answerer&#39;s =
TURN server with addressees/ports in c=3D and m=3D line and rtcp attribute =
from the offer.</span></div><div class=3D"gmail_extra"><br style=3D"font-fa=
mily:arial,sans-serif;font-style:normal;font-variant-ligatures:normal;font-=
variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;=
text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;bac=
kground-color:rgb(255,255,255);text-decoration-style:initial;text-decoratio=
n-color:initial"><span style=3D"color:rgb(0,0,0);font-family:arial,sans-ser=
if;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-va=
riant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backg=
round-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-=
color:initial;float:none;display:inline">- I guess that means we are actual=
ly talking about the answerers default candidates, which seems like a somew=
hat convoluted way of saying that if the answerer is using a TURN server fo=
r its media stream, then it needs to create permissions for whatever the de=
fault candidate is in the offer SDP (whether relayed or not), or am I missi=
ng something ? In either case, some clarification is needed here.<span>=C2=
=A0</span></span><br style=3D"color:rgb(0,0,0);font-family:arial,sans-serif=
;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-vari=
ant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgro=
und-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-co=
lor:initial">

<br>Yes. You are correct and clarification is needed.</div><div class=3D"gm=
ail_extra"><br></div><div class=3D"gmail_extra">Regards,<br clear=3D"all"><=
div><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></di=
v></div></div></div>

--0000000000001e93ea05690b008d--


From nobody Wed Apr  4 12:42:50 2018
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 D3803126E64; Wed,  4 Apr 2018 12:42:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bgHLGemrB9rq; Wed,  4 Apr 2018 12:42:42 -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 E4BC3126DCA; Wed,  4 Apr 2018 12:42:41 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w34JgajJ048916 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 4 Apr 2018 14:42:36 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Thomas Stach <thomass.stach@gmail.com>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com>
Date: Wed, 4 Apr 2018 14:42:30 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ARddFniccmWZ4auDsNI3eUH03W0>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 19:42:45 -0000

Thanks for your quick responses! Your proposed resolutions all look good 
to me. I notice that you didn't respond to my comment on the "NOTE" in 
§4.4. Should I expect an additional reply to address that comment?

/a

On 4/4/18 2:12 PM, Thomas Stach wrote:
> Adam,
> thanks for the comments.
> As your DISCUSS points are already treated on other threads,
> There are  just some replies in the comment section below.
>
>
> On 2018-04-03 09:29, Adam Roach wrote:
>> Adam Roach has entered the following ballot position for
>> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to 
>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> Thanks to everyone who worked on this document. I have a couple of 
>> concerns that
>> need to be cleared up before the document can move forward.
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §4.3.4 discusses the interaction of 3PCC with the trickle ICE mechanism.
>> Unfortunately, the diagrams used in this section do not show a 3PCC 
>> signaling
>> flow; they show a two-party call flow with an offerless INVITE. A 
>> 3PCC call flow
>> would necessarily involve a 3PCC controller sending an offerless 
>> INVITE to one
>> party, receiving an offer from that party (typically in a reliable 
>> provisional
>> response or in a 200 OK), and then sending an INVITE to the other party
>> containing that offer.
>>
>> The text in this section matches the diagrams, and consequently does 
>> not appear
>> to be an analysis of 3PCC behavior. It is an analysis of two-party 
>> offerless
>> INVITE behavior.
>>
>> If this section remains, it needs to be substantially re-worked: the 
>> diagrams
>> need to show three parties, with a 3PCC controller performing the 
>> controlling
>> role as described in RFC 3725. While I haven't stepped through the 
>> implications
>> for Trickle ICE when a controller is actually involved and is moving 
>> offers and
>> answers around between different message types, I suspect that the 
>> analysis in
>> here is substantially different once this starts happening.
>>
>> I would personally be okay if the entire section were removed; 
>> however, I
>> have no desire to override working group consensus regarding the 
>> value of a
>> section dealing with 3PCC considerations.
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> The second issue doesn't necessarily pertain to this document per se 
>> as much
>> as it does the interaction among this document, 
>> draft-ietf-ice-trickle (Trickle
>> ICE), draft-ietf-mmusic-ice-sip-sdp (ICE SDP), and 
>> draft-ietf-rtcweb-jsep
>> (JSEP). The problem doesn't lie with any single document, but in the 
>> overall
>> result of how they're currently structured.
>>
>> JSEP (in the RFC editor queue) refers to the "a=end-of-candidates" 
>> SDP attribute
>> as appearing in Trickle ICE, section 9.3, which was true at one point 
>> in time.
>> Somewhere along the line, this attribute's definition was moved from 
>> there
>> into this document.
>>
>> There are several ways to fix this, each with their own drawbacks:
>>
>> 1. Move the SDP syntax for "a=end-of-candidates" back into the 
>> Trickle ICE
>>     draft. Drawback: Trickle ICE does not currently define any 
>> normative SDP
>>     behavior; and, in fact, could work in a system that doesn't use 
>> SDP at all.
>>
>> 2. Move the SDP syntax into the ICE SDP draft. This is pretty elegant 
>> from the
>>     perspective that ICE SDP defines SDP syntax for ICE in general 
>> (for both
>>     SIP and JSEP), and such a move aggregates all of the SDP syntax 
>> into a
>>     single document that is already necessary to reference from any 
>> document
>>     that uses SDP for Trickle ICE. Drawback: the document doesn't 
>> presently
>>     discuss Trickle ICE at all, and this would require a somewhat 
>> awkward
>>     section that basically says "If you use [Trickle ICE] with SDP, 
>> the syntax
>>     for the end-of-candidate marker is..."
>>
>> 3. Change JSEP to normatively depend on this document for the
>>     "a=end-of-candidates" syntax. Drawback: This document is extremely
>>     SIP-specific, while JSEP is based solely on RFC 4566 syntax and 
>> RFC 3264
>>     behavior, independent of any SIP semantics.  Forcing JSEP to 
>> normatively
>>     depend on a SIP specific document for a simple attribute syntax 
>> definition
>>     seems to be letting the tail wag the dog.
>>
>> I believe that #2 is the least inelegant option, but I'm open to #1 
>> and #3.
>> However, The *current* situation -- in which JSEP normatively points 
>> to a
>> document from which the text is cites has been removed out from under 
>> it -- is
>> clearly wrong.
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> §4.1.4:
>>
>>>   If the initial Answer included the attribute a=ice-options:trickle,
>>>   the Offerer MUST be prepared for receiving trickled candidates later
>>>   on.
>> I don't think this makes sense. If the initial *Offer* includes that 
>> option,
>> then the Offerer must be prepared to receive trickled candidates, 
>> even before
>> the Answer arrives. Figure 6 shows an example of this. I believe that 
>> the
>> paragraph I quote above needs to be entirely removed, as it may lead
>> implementors to incorrectly assume that they can't get trickled 
>> candidates prior
>> to an Answer.
>>
>> --------------------------------------------------------------------------- 
>>
> Will remove
>>
>> §4.3:
>>
>>>     o  The dialog at both peers MUST be in early or confirmed state.
>> This makes no sense. Dialogs exist in precisely two states, ever: 
>> early or
>> confirmed. Prior to "early," they don't exist. The only exit from 
>> "confirmed" is
>> destruction. (See RFC 3261 §12).
>>
>> I think what this means to say is "A dialog MUST have been created 
>> between the
>> peers."
>>
>> --------------------------------------------------------------------------- 
>>
> I'll change to your wording
>>
>> §4.3.2:
>>
>>>   These retransmissions MUST
>>>   cease on receipt of an INFO request carrying a 'trickle-ice' Info
>>>   Package body or on transmission of the Answer in a 2xx response.
>> Why does this require that specific INFO to stop retransmission? The 
>> only
>> requirement is that the answerer knows that the offerer has received the
>> provisional response. The offerer cannot send post-INVITE requests to 
>> the
>> answerer until a dialog is established, and the only ways a dialog 
>> can be
>> established at the offerer is receipt of a provisional or final 
>> response. So, as
>> soon as you get *any* request from the offerer, you know that the 
>> provisional
>> response has arrived.
>>
>> I think this passage means to say "These retransmissions MUST cease 
>> on receipt
>> of any in-dialog request from the offerer. The offerer cannot send 
>> in-dialog
>> requests until it receives a response, so the arrival of such a 
>> request proves
>> that the response has arrived."
>>
>> --------------------------------------------------------------------------- 
>>
> Sure, any other request will do the trick as well. However, as it is 
> not guaranteed that a request
> other than said INFO is sent, I'd prefer to say
>
> "These retransmissions MUST cease on receipt
> of an INFO request carrying a 'trickle-ice' Info
>  Package body, on receipt any in-dialog request from the offerer or on 
> transmission
> of the Answer in a 2xx response. The offerer cannot send in-dialog
> requests until it receives a response, so the arrival of such a 
> request proves
> that the response has arrived."
>
>
>> §4.3.2:
>>
>>>   The Offerer MUST send a Trickle ICE INFO request as soon as it
>>>   receives an SDP Answer in an unreliable provisional response.  This
>>>   INFO request MUST repeat the candidates that were already provided in
>>>   the Offer (as would be the case when Half Trickle is performed or
>>>   when new candidates have not been learned since then).
>> It is probably worth mentioning that it's possible that this INFO 
>> contains no
>> candidates, depending on how the offerer gathers its candidates and 
>> how long it
>> takes to do so.
>>
>> --------------------------------------------------------------------------- 
>>
> Will add
>>
>> §4.3.3:
>>
>>>   These retransmissions MUST cease on receipt
>>>   of an INFO request or on transmission of the Answer in a 2xx
>>>   response.
>> Same comment as above for §4.3.2.
>>
>> --------------------------------------------------------------------------- 
>>
> sane answer
>>
>> §4.3.4:
>>
>>>   As specified in Section 4 this offerless INVITE
>>>   MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
>>>   header field in order to indicate support for Trickle-ICE to the
>>>   Offerer (at the User Agent Server (UAS)).
>> How does the 3PCC controller know to include this option tag? Is it 
>> simply
>> indicating that the 3PCC controller supports the Trickle mechanism? 
>> If so,
>> what happens if the second party (the one who receives the offer in 
>> an INVITE)
>> doesn't support Trickle ICE? This is one of the sharper corner cases 
>> that I
>> think arises when you go to fix the analysis I describe in my DISCUSS 
>> above.
>>
>> --------------------------------------------------------------------------- 
>>
> Well, the 3PCC is usually in the signaling path and can detect if 
> Trickle-ICE is supported at the parties...
> However there will certainly appear other corner cases that are not 
> yet covered in that section.
> Thus, like Ben, I'd also be happy to remove that section, if we get WG 
> consensus for doing so.
> @Fleming, would you be OK to ask for that?
>>
>> §4.4:
>>
>>>      a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 5000 typ srflx
>>>          raddr 2001:db8:a0b:12f0::1 rport 8998
>> Thanks for the IPv6 example; however, I have a *lot* of heartburn 
>> with the
>> selection of an example that demonstrates IPv6 NAT behavior. Since 
>> ICE's srflx
>> behavior is fundamentally tied to IPv4 NATs (and should not be an 
>> issue with
>> IPv6, as NATs are unnecessary), I think it's okay for the srvflx 
>> examples to go
>> ahead and show IPv4 addresses.
>>
>> I *really* don't want to publish an RFC that demonstrates NATting of 
>> IPv6.
> I concur with Peter's response on your same comment on 
> draft-ice-trickle and use another candidate type for IPv6
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §4.4:
>>
>>>   An "a=end-of-candidates" attribute, preceding any pseudo "m=" line,
>>>   indicates the end of all trickling from that agent, as opposed to end
>>>   of trickling for a specific "m=" line, which would be indicated by a
>>>   media level "a=end-of-candidates" attribute.
>> I finally did figure out what this meant, but it's confusing. The use 
>> of "any"
>> in the phrase "any pseudo 'm=' line" implies that the following 
>> sdpfrag would
>> qualify:
>>
>>        a=ice-pwd:asd88fgpdd777uzjYhagZg
>>        a=ice-ufrag:8hhY
>>        m=audio 9 RTP/AVP 0
>>        a=mid:1
>>        a=candidate:1 1 UDP 2130706431 2001:db8:a0b:12f0::1 5000 typ host
>>        a=candidate:1 2 UDP 2130706431 2001:db8:a0b:12f0::1 5001 typ host
>>        a=end-of-candidates
>>        m=audio 9 RTP/AVP 0
>>        a=mid:2
>>        a=candidate:1 1 UDP 2130706431 2001:db8:a0b:12f0::1 6000 typ host
>>        a=candidate:1 2 UDP 2130706431 2001:db8:a0b:12f0::1 6001 typ host
>>
>> The end-of-candidates *does* appear before the second pseudo "m=" 
>> line, which is
>> one of the lines (thereby satisfying the "any" criteria).
>>
>> I think you mean "preceding the first pseudo 'm=' line..."
> Will change to your wording
>>
>> This is true later in the section also:
>>
>>>   will not send any further candidates. When included at session
>>>   level, i.e. before any pseudo "m=" line, this indication applies to
>> --------------------------------------------------------------------------- 
>>
>>
>> §4.4:
>>
>>>   Note: At the time of writing this specification there were ongoing
>>>   discussions if a functionality for removing already exchanged
>>>   candidates would be useful.  Such a functionality is out of the scope
>>>   of this specification and most likely needs to be signaled by means
>>>   of a yet to be defined ICE extension, although it could in principle
>>>   be achieved quite easily, e.g. without anticipating any solution by
>>>   simply omitting a previously sent candidate from a subsequent INFO
>>>   request.  However, if an implementation according to this
>>>   specification receives such an INFO request with a missing candidate
>>>   it would have to treat that as an exceptional case. Implementing
>>>   appropriate recovery procedures at the receiving side is advisable
>>>   for this situation.  Ignoring that a candidate was missing might be a
>>>   sensible strategy.
>> This seems like an interop nightmare. If you want a note about this 
>> possibly
>> being included in the future, please simply indicate that such an 
>> ability will
>> need to be explicitly signaled. Don't imply that implementations 
>> might get SDP
>> that violates the behavior defined in this document in some 
>> ill-defined way,
>> and just need to kind of gracefully deal with it, even if we don't 
>> really know
>> what it means at this point in time. There's no sensible way to code 
>> for that.
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §4.4:
>>
>>>      a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 5000 typ srflx
>>>         raddr 2001:db8:a0b:12f0::1 rport 8998
>>>      a=candidate:2 2 UDP 1694498815 2001:db8:a0b:12f0::3 5001 typ srflx
>>>         raddr 2001:db8:a0b:12f0::1 rport 8998
>> ...
>>>      a=candidate:2 1 UDP 1694498815 2001:db8:a0b:12f0::3 6000 typ srflx
>>>         raddr 2001:db8:a0b:12f0::1 rport 9998
>>>      a=candidate:2 2 UDP 1694498815 2001:db8:a0b:12f0::3 6001 typ srflx
>>>         raddr 2001:db8:a0b:12f0::1 rport 9998
>> Same comment as above regarding IPv6 and NATs. Note that it would be 
>> Good and
>> Helpful to show SDP with a mixture of IPv4 and IPv6 anyway.
> Ok, I'll change the address family to IPv4 for the srvflx and add IPv4 
> host candidates
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §5:
>>
>>>   SIP User Agents (UAs) that support and intend to use trickle ICE are
>>>   required by [I-D.ietf-ice-trickle] to indicate that in their Offers
>>>   and Answers using the attribute "a=ice-options:trickle" and MUST
>>>   include the SIP option-tag "trickle-ice" in a SIP Supported: header
>>>   field.
>> Is this intended to imply that the option tag cannot be used in a 
>> Require header
>> field? I don't think that's a good idea; however, if that is the 
>> working group's
>> intention, please say so explicitly.
>>
>> Suggest "...in a SIP 'Supported' or 'Require' header field."
> Ok. It wasn't intended to disallow usage of Require: Trickle-ice
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §5.1:
>>
>> This section discusses behavior in a walled garden. I'm generally 
>> fine with
>> this, as long as the failure modes when someone starts adding doors 
>> to the
>> walled garden are well-defined. I don't think this kind of 
>> provisioning is
>> okay unless it has a requirement that Offerers assuming Trickle ICE 
>> support
>> MUST include a "Require: trickle-ice" header field. That way, if the
>> provisioned assumption of Trickle ICE support ends up being 
>> incorrect, the
>> failure is (a) operationally easy to track down, and (b) recoverable 
>> by the
>> client (i.e.: they can re-send the request without the "Require" 
>> header field
>> and without the assumption of Trickle ICE support).
> Ok. I could add (re-using some of your text):
> " An Offerer assuming Trickle ICE support MUST include a "Require: 
> trickle-ice" header field.
> That way, if the provisioned assumption of Trickle ICE support ends up 
> being incorrect,
> the failure is (a) operationally easy to track down, and (b) 
> recoverable by the client,
> i.e., they can re-send the request without the Require: header field 
> and without the assumption of Trickle ICE support."
>> --------------------------------------------------------------------------- 
>>
>>
>> §6:
>>
>>>   This INFO request indicates that the Answerer supports and uses RTP
>>>   and RTCP multiplexing as well.  It allows the Offerer to omit
>>>   gathering of RTCP candidates or releasing already gathered RTCP
>>>   candidates.
>> It's not clear how this "releasing already gathered RTCP candidates" 
>> interacts
>> with the requirement in §4.4:
>>
>>>   In other words, the sequence
>>>   of a previously sent list of candidates MUST NOT change in subsequent
>>>   INFO requests and newly gathered candidates MUST be added at the end
>>>   of that list.
>> So, if I had already trickled candidates for the RTCP component of a 
>> connection
>> and *then* got an INFO from the Answerer indicating that it supports
>> multiplexing, does that mean I free the resources and exclude them 
>> from future
>> INFO messages? That seems to contravene the §4.4 requirement. Or do I 
>> free them
>> but continue to include them? I suppose that's okay (maybe?), but it's
>> extremely counterintuitive, and would need to be called out 
>> explicitly if you
>> expect implementors to get it right.
> Well, the implicit assumption was that the RTCP might have been 
> gathered, but not yet been sent to the peer.
> If there were sent in a previous INFO they would still need to be 
> included.
> I will call this out explicitly
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §7:
>>
>>>   A Trickle Answerer SHOULD include an "a=group: BUNDLE" attribute
>>>   [I-D.ietf-mmusic-sdp-bundle-negotiation] in the application/trickle-
>>>   ice-sdpfrag body if it supports and uses bundling.
>> This needs to clearly indicate that this needs to be included at the 
>> session
>> level (rather than the media level).
> OK
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §7:
>>
>>>   The Offerer can use this information e.g. for stopping the gathering
>>>   of candidates for the remaining "m=" lines in a bundle and/or for
>>>   freeing corresponding resources.
>> Same comment as for §6, above (regarding interaction with the 
>> requirement from
>> §4.4)
> Same handling envisaged as above
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §7:
>>
>>>       a=group:BUNDLE foo bar
>>>       a=ice-pwd:asd88fgpdd777uzjYhagZg
>>>       a=ice-ufrag:8hhY
>>>       m=audio 9 RTP/AVP 0
>>>       a=mid:foo
>>>       a=rtcp-mux
>>>       a=candidate:1 1 UDP 1658497328 2001:db8:a0b:12f0::3 5000 typ host
>>>       m=audio 9 RTP/AVP 0
>>>       a=mid:bar
>> The presence of the second m= line here is confusing, given the 
>> following text
>> from §4.4:
>>
>>>   Note, that there is no requirement that the Info request body
>>>   contains as many pseudo m= lines as the Offer/Answer contains m=
>>>   lines, nor that the pseudo m= lines be in the same order as the
>>>   m=lines that they pertain to.  The correspondence can be made via the
>>>   "a=mid:" attributes.
>> The §4.4 text strongly implies that it is nonsensical to include an 
>> m= section
>> without candidates. Is the example in §7 intended to imply that the 
>> section
>> needs to be included because its mid is mentioned in the 
>> "a=group:BUNDLE" line?
>> If so, please say so. If not, please remove the second m= section.
> I'll remove
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §9.2:
>>
>> The syntax for "session-level-fields", "pseudo-media-descriptions", and
>> "trickle-ice-attribute-fields" include extremely strict rules around 
>> ordering of
>> fields (e.g., including ice-ufrag before ice-pwd would be syntactically
>> invalid). That level of strictness seems unlikely to lead to 
>> interoperable
>> implementations.
>>
>> If the intention is to be rigid in this fashion, please add prominent 
>> prose
>> that warns implementors that fields MUST appear in the order 
>> specified, and
>> that all other orders are invalid and MUST be rejected.
>>
>> If that's *not* your intention (and I suspect it isn't), then please 
>> fix the
>> syntax definition to allow for arbitrary ordering of attributes in 
>> the same way
>> as SDP does. For example:
>>
>>      session-level-fields = *(session-level-field CRLF)
>>
>>      session-level-field = bundle-group-attribute /
>>                            ice-lite-attribute /
>>                            ice-pwd-attribute /
>>                            ice-ufrag-attribute /
>>                            ice-options-attribute /
>>                            ice-pacing-attribute /
>>                            end-of-candidates-attribute /
>>                            extension-attribute-fields
>>                                   ; for future extensions
> I'll change.
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §9.2:
>>
>> The syntax for "session-level-fields" implies that "ice-pwd" and 
>> "ice-ufrag" are
>> mandatory at the session level. This seems to conflict with the text 
>> in §4.4:
>>
>>>   The "a=ice-pwd:" and "a=ice-ufrag:" attributes MUST appear at the
>>>   same level as the ones in the Offer/Answer exchange.  In other words,
>>>   if they were present as session-level attributes, they will also
>>>   appear at the beginning of all INFO request payloads, i.e. preceding
>>>   all pseudo "m=" lines.  If they were originally exchanged as media
>>>   level attributes, potentially overriding session-level values, then
>>>   they will also be included in INFO request payloads following the
>>>   corresponding pseudo "m=" lines.
>> The fix I propose above removes this implication that such attributes 
>> are
>> mandatory at the session level; however, if you choose to fix it some 
>> other way,
>> please ensure that the ABNF does not conflict with the normative 
>> language I
>> quote above.
> I'd go with your proposal
>> --------------------------------------------------------------------------- 
>>
>>
>> §10.6:
>>
>> Same comment as for §5 above.
> Ok. It wasn't intended to disallow usage of Require: trickle-ice.
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §10.9:
>>
>>>   If the INFO requests are sent on top of TCP, which is probably the
>>>   standard way, this is not an issue for the network anymore, but it
>>>   can remain one for SIP proxies and other intermediaries forwarding
>>>   the SIP INFO messages.  Also, an endpoint may not be able to tell
>>>   that it has congestion controlled transport all the way.
>> This seems kind of blithe about congestion control, as it concedes 
>> that the INFO
>> requests might end up on UDP at some point. Minimally, I would think 
>> that you
>> want to require some minimum quarantine period between INFO requests 
>> (probably
>> something in the range of 20 ms), during which any new candidates 
>> that are
>> gathered are aggregated into the next INFO message.
> I can add this
>> =========================================================================== 
>>
>>
>> Nits:
>>
>> Expand "ICE" in the title.
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> draft-ietf-mmusic-ice-sip-sdp has undergone a major restructuring 
>> since version
>> 16; as a consequence, all notes of the form:
>>
>>>   [RFC EDITOR NOTE: The section 4.2.1.2.1 in above sentence is correct
>>>   for version 16 of said I-D.  Authors need to cross-check during
>>>   Auth48 since it could have have changed in the meantime.]
>> ...are already out of date. It's probably worthwhile to fix these 
>> now, as they
>> are (in my opinion) quite unlikely to change again; and the current 
>> misdirection
>> makes it somewhat difficult to use the draft in its current form.
> That note was intended for covering exactly this scenario and catch 
> such numbering changes.
> Will updated in the revision
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §4.1.3:
>>
>>>   If the Answerer includes candidates in its initial Answerer, it MUST
>> "...initial Answer..."
> thx
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §7:
>>
>>>   A Trickle Answerer SHOULD include an "a=group: BUNDLE" attribute
>> Remove the space before "BUNDLE"
> thx
>>
>> --------------------------------------------------------------------------- 
>>
>>
>> §11:
>>
>>>   Trickle ICE uses two mechanism for exchange of candidate information.
>> "mechanisms"
> thx
>
> Thanks again for the thorough review!
> Thomas
>>
>


From nobody Wed Apr  4 12:55:06 2018
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 CC94812D82F; Wed,  4 Apr 2018 12:54:58 -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 njUt24jYoGWp; Wed,  4 Apr 2018 12:54:56 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c: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 D95C4126DCA; Wed,  4 Apr 2018 12:54:55 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id b127so219604wmf.5; Wed, 04 Apr 2018 12:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=DIWwajwiN33TF0wpZa6U7GYv03pgnoZSXhR26TBIuUg=; b=O9xriynefqwYardgZVJLG/SQf5jHR7yMQFdztMSIz9itImSEh+BNbCC/u1GF6MLCR0 6177cqtaKNlU3y9tXPc34N0Hd0m43FN9sHfq67kzdt3HPbJ6sonGiU8RT/Wcw09/90Lo en6R/ySE7U1ZnyPNfWHB8POHooCbc3eeWxYhAyAb2yNcI6y7ebbU2DqyF4wrw456BO8e cn35K/I2pzLZWIy8EgOZagje1TQdKrqAA59334sJ6SCR2vMREvSm6+5tG9aXy3gjgAH+ Ijhv5KzAXGYCi3NZEr2UPPdsGghl9PQ7Fy6pC8omHcLKmPNiTHAdp4ewW2IZf4BYq+7d Sz6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=DIWwajwiN33TF0wpZa6U7GYv03pgnoZSXhR26TBIuUg=; b=d7F6+qwm4bv/SjuupAhQS0FwpiI0v+0ficQwJrfZbOADB3hamfQ7V+50J3N0pIeCMu x+nov6P1FbCurF7QpqzIfhzxoi6VrbOWGdKXU2o6X6R2+vgR9F/qOLbs86QoEF8PbpOy VgDwLxmIglzmutDxrH1Q7kjqP1fyvzKRy88086YVY1vc6qK7xyyWDFdFfzNkJ1DAhnGG IZKOonTsxpJV1kifS5CFNsXh0mWnivtJmo5ceiHgGvpaK3DNCamI0xklbDt2vtfMe7cZ 8Sy4CUw4Tz89Cq57dKDMmV4gkdKUgrPHKWGiwQ6+hgu41rVx/5Cuja2st5A2TAhPmg2p 6RTg==
X-Gm-Message-State: AElRT7HmCcdhd4K2meVIlxTrOk8OtcEe7mcL7MF+jmsPM87PPYEXpN7S rijMrT/xVBY8QDIJd4r9WfOc7XOd3vI=
X-Google-Smtp-Source: AIpwx48MwsgVBXAKoYRWykG5P6GxIWdabKRLd/++l+u8KJ3rTh8UDwqF+na+PrGDKUkpqg9tlvdotw==
X-Received: by 10.28.230.148 with SMTP id e20mr7850365wmi.89.1522871694035; Wed, 04 Apr 2018 12:54:54 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id r196sm3831081wmf.9.2018.04.04.12.54.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Apr 2018 12:54:53 -0700 (PDT)
To: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com>
Date: Wed, 4 Apr 2018 21:54:52 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------93544F1BBF7D098BC560966D"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3RsSvupr4O3pYHlY2DP4atLFSm4>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 19:54:59 -0000

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

Mirja,

thanks for your comments.


On 2018-04-03 16:37, Mirja Kühlewind wrote:
> Mirja Kühlewind has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Thanks for the well-written doc and the quick response to the initial tsv
> review. Also thanks to Jörg for the thorough and very helpful review!
>
> As flagged by the tsv review, there can be an issue with the aggregation of
> candidates in one INFO message when rate limited and the path MTU/UPD
> fragmentation. While this is a small point only and I'm sure it can be easily
> addressed, it important enough that I decided to put a discuss in. I'm sure
> this can be resolved quickly as well.
As large messages are already addressed in RFC 3261, I could add 
something like
"As a potentially large number of candidates are aggregated in a INFO 
request,
the message size can easily exceed the path MTU. SIP [RF3261] requires 
that if a request
is within 200 bytes of the path MTU, or if it is larger than 1300 bytes 
and the path MTU is unknown,
that the request is sent using an RFC 2914 
<https://tools.ietf.org/html/rfc2914> [43 
<https://tools.ietf.org/html/rfc3261#ref-43>] congestion controlled 
transport protocol,
such as TCP.
"
> Also if the document could give further guidance on an acceptable maximum for
> the rate of INFO requests that be even better!
Adam proposed in his review to

"... require some minimum quarantine period between INFO requests 
(probably something in the range of 20 ms),
during which any new candidates that are gathered are aggregated into 
the next INFO message."

Would that be enough of a guidance?
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Editorial comments:
>
> 1) sec 4.3.2: "When sending the Answer in the 200 OK response to the INVITE
> request,
>     the Answerer needs to repeat exactly the same Answer that was
>     previously sent in the unreliable provisional response in order to
>     fulfill the corresponding requirements in [RFC3264].  Thus, the
>     Offerer needs to be prepared for receiving a different number of
>     candidates in that repeated Answer than previously exchanged via
>     trickling and MUST ignore the candidate information in that 200 OK
>     response."
>     What do I miss? Why can there be a different number of candidates if the
>     repeated Answer needs to be exactly the same...? Or is there an "not"
>     missing? Not an expert though, so might be just me...
If the answer is sent in a provisional response, it might have included 
a small  number (or even 0) of candidates.
Before the 200 OK is sent the answerer might have trickled additional 
candidates in INFOs.
However, the additional candidates will not appear in the answer in the 
body of the 200OK.
This is due to a requirement in RFC3264, that the answer in the 
provisional response must be exactly the same as in the 200OK.
So the total number of candidates that the offerer received will be 
different from the number of candidates in that answer.

> ,
>
> 2) I guess section 10.1 could also be moved to the appendix but it is short
> enough that leaving it in the body is fine as well.
So, I probably leave it where it is.

Thanks for your review

Thomas
>


--------------93544F1BBF7D098BC560966D
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><tt>Mirja,</tt></p>
    <p><tt>thanks for your comments.</tt><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2018-04-03 16:37, Mirja Kühlewind
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com">
      <pre wrap="">Mirja Kühlewind has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-sip-14: Discuss

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


Please refer to <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html">https://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/">https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/</a>



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

Thanks for the well-written doc and the quick response to the initial tsv
review. Also thanks to Jörg for the thorough and very helpful review!

As flagged by the tsv review, there can be an issue with the aggregation of
candidates in one INFO message when rate limited and the path MTU/UPD
fragmentation. While this is a small point only and I'm sure it can be easily
addressed, it important enough that I decided to put a discuss in. I'm sure
this can be resolved quickly as well.</pre>
    </blockquote>
    As large messages are already addressed in RFC 3261, I could add
    something like<br>
    "As a potentially large number of candidates are aggregated in a
    INFO request, <br>
    the message size can easily exceed the path MTU. SIP [RF3261]
    requires that if a request<br>
    is within 200 bytes of the path MTU, or if it is larger than 1300
    bytes and the path MTU is unknown,<br>
    that the request is sent using an <a
      href="https://tools.ietf.org/html/rfc2914">RFC 2914</a> [<a
      href="https://tools.ietf.org/html/rfc3261#ref-43"
      title="&quot;Congestion Control Principles&quot;">43</a>]
    congestion controlled transport protocol, <br>
    such as TCP.<br>
    "<br>
    <blockquote type="cite"
cite="mid:152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com">
      <pre wrap="">Also if the document could give further guidance on an acceptable maximum for
the rate of INFO requests that be even better!</pre>
    </blockquote>
    Adam proposed in his review to <br>
    <br>
    "... require some minimum quarantine period between INFO requests
    (probably something in the range of 20 ms), <br>
    during which any new candidates that are gathered are aggregated
    into the next INFO message."<br>
    <br>
    Would that be enough of a guidance?<br>
    <blockquote type="cite"
cite="mid:152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com">
      <pre wrap="">


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

Editorial comments:

1) sec 4.3.2: "When sending the Answer in the 200 OK response to the INVITE
request,
   the Answerer needs to repeat exactly the same Answer that was
   previously sent in the unreliable provisional response in order to
   fulfill the corresponding requirements in [RFC3264].  Thus, the
   Offerer needs to be prepared for receiving a different number of
   candidates in that repeated Answer than previously exchanged via
   trickling and MUST ignore the candidate information in that 200 OK
   response."
   What do I miss? Why can there be a different number of candidates if the
   repeated Answer needs to be exactly the same...? Or is there an "not"
   missing? Not an expert though, so might be just me...</pre>
    </blockquote>
    If the answer is sent in a provisional response, it might have
    included a small  number (or even 0) of candidates.<br>
    Before the 200 OK is sent the answerer might have trickled
    additional candidates in INFOs. <br>
    However, the additional candidates will not appear in the answer in
    the body of the 200OK. <br>
    This is due to a requirement in RFC3264, that the answer in the
    provisional response must be exactly the same as in the 200OK.<br>
    So the total number of candidates that the offerer received will be
    different from the number of candidates in that answer.<br>
    <br>
    <blockquote type="cite"
cite="mid:152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com">
      <pre wrap="">,

2) I guess section 10.1 could also be moved to the appendix but it is short
enough that leaving it in the body is fine as well.</pre>
    </blockquote>
    So, I probably leave it where it is.<br>
    <br>
    Thanks for your review<br>
    <br>
    Thomas<br>
    <blockquote type="cite"
cite="mid:152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com">
      <pre wrap="">

</pre>
    </blockquote>
    <blockquote type="cite"
cite="mid:152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com"></blockquote>
    <br>
  </body>
</html>

--------------93544F1BBF7D098BC560966D--


From nobody Wed Apr  4 13:56:22 2018
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 02265127AD4; Wed,  4 Apr 2018 13:56:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 tWWtyYsJ2ajk; Wed,  4 Apr 2018 13:56:18 -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 4C456126BF0; Wed,  4 Apr 2018 13:56:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1335; q=dns/txt; s=iport; t=1522875378; x=1524084978; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=wECnc1oDWI4dbWzrzg3jmT6Tw3NAw+/idw66hApams8=; b=GvYSnEhJQG/mu7+aFfl6t4+99ZEAjPmV9rLTWVOSN3+RT9V7VVwmdaxv ZY/DUCtfxdd2wk8YRM4KwHSjsLQ1KirCx5rl5Ivm8UNBpP8OoDhg0Z+GE bbleTuB5Rmd/Iv3cGnSGF6UqFszTOzj9PQMPu20S1Vtcan6kNqpvBD45I E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DmAADZOsVa/5JdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNCgVCEB4gAjQmBSymBD5JVgXoLhQMChEAhNBgBAgEBAQE?= =?us-ascii?q?BAQJsKIUjAQUjDwEFQRALGAICJgICVwYBDAgBAYR8Daw/ghyEV4NsgiWBCYZ?= =?us-ascii?q?ZgVQ/gQwigmKEWYMWglQChyOQGwiIIIYLBodChHqPfYElHDiBUk0jFTqCRIJ?= =?us-ascii?q?HjiIjjh4BAQ?=
X-IronPort-AV: E=Sophos;i="5.48,408,1517875200"; d="scan'208";a="94568914"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2018 20:56:17 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id w34KuG2v012303; Wed, 4 Apr 2018 20:56:17 GMT
To: Thomas Stach <thomass.stach@gmail.com>, Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, mmusic@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <e59079dd-a85b-7b3e-3af1-b2be428d4fb9@cisco.com>
Date: Wed, 4 Apr 2018 16:56:16 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Up06Vw5CwHTjAt_9mgGKv_1paQI>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 04 Apr 2018 20:56:20 -0000

On 4/4/18 3:12 PM, Thomas Stach wrote:
>
>>
>> §4.3.4:
>>
>>>   As specified in Section 4 this offerless INVITE
>>>   MUST include the SIP option-tag 'trickle-ice' in a SIP Supported:
>>>   header field in order to indicate support for Trickle-ICE to the
>>>   Offerer (at the User Agent Server (UAS)).
>> How does the 3PCC controller know to include this option tag? Is it 
>> simply
>> indicating that the 3PCC controller supports the Trickle mechanism? 
>> If so,
>> what happens if the second party (the one who receives the offer in 
>> an INVITE)
>> doesn't support Trickle ICE? This is one of the sharper corner cases 
>> that I
>> think arises when you go to fix the analysis I describe in my DISCUSS 
>> above.
>>
>> --------------------------------------------------------------------------- 
>>
> Well, the 3PCC is usually in the signaling path and can detect if 
> Trickle-ICE is supported at the parties...
> However there will certainly appear other corner cases that are not 
> yet covered in that section.
> Thus, like Ben, I'd also be happy to remove that section, if we get WG 
> consensus for doing so.
> @Fleming, would you be OK to ask for that?
Sure - just start a new thread on the MMUSIC list explaining the issue 
and with a clear Subject-line.

Thanks

-- Flemming



From nobody Thu Apr  5 00:54:06 2018
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 DC740120725 for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 00:53:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zdzgs9fZGcCK for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 00:53:58 -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 CAFE4124B17 for <mmusic@ietf.org>; Thu,  5 Apr 2018 00:53:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522914833; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=wEIhXv3awgYAIfg6wwi64nejhH7n6wd1FXJHbw9fvUQ=; b=PY4KFvb0cRFUW6paP1Y22F+krORZoLUgq/hQMwGy8gtoSdoc51Xgh3kjrae3FqoI xX/mid5M2omjRMqFchnwqOthXtU+1xeMhi/iVbJWeOtIYcuq5TjpDhUOKiLOsiHE 8nw0mmkdGy/Y0fsqXwZjg1bFDKVzuTBFphGkwZzAx/E=;
X-AuditID: c1b4fb30-a99ff70000005e22-34-5ac5d6105ea5
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 9D.98.24098.116D5CA5; Thu,  5 Apr 2018 09:53:53 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0382.000; Thu, 5 Apr 2018 09:53:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>, Thomas Stach <thomass.stach@gmail.com>, "The IESG" <iesg@ietf.org>
CC: "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTyx2P005KrT20W0WCmZj7phUtbaPw2hYAgAAISgCAAOwY8A==
Date: Thu, 5 Apr 2018 07:53:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E48374@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com> <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com>
In-Reply-To: <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.171]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM2K7oq7gtaNRBj0neC32/F3EbvFj7XJm i/cXdC1m/JnIbHF+53omi6nLH7NYfDqxlcmB3WPK742sHjtn3WX3WLLkJ5PHrJ1PWAJYorhs UlJzMstSi/TtErgyPtzNLtghXLHzZitTA+MPoS5GTg4JAROJCTv7WbsYuTiEBI4wSqy6PY0R wlnMKLH66X/mLkYODjYBC4nuf9ogDSIC6RILjq4Fa2AWeMYo8eT+b1aQhDBQYvPNKawQRRkS 59qmskDYThJH1q9mAZnDIqAisfytIkiYV8BXYsGyPiYQW0hgK6PEibcKIDangL1E38/lzCA2 o4CYxPdTa8BqmAXEJW49mc8EcbSAxJI955khbFGJl4//sULYShInHjaCncwsoCmxfpc+RKui xJTuh+wQawUlTs58wjKBUXQWkqmzEDpmIemYhaRjASPLKkbR4tTipNx0IyO91KLM5OLi/Dy9 vNSSTYzAKDu45bfBDsaXzx0PMQpwMCrx8C45fDRKiDWxrLgy9xCjBAezkggvazNQiDclsbIq tSg/vqg0J7X4EKM0B4uSOK+F3+YoIYH0xJLU7NTUgtQimCwTB6dUA6MGv837lwH7umIviSvp Ha1yEfx7rOHnPC6R1BNaJ5oDxH21dX+W3hAT+RqhJafH6er04N6/K7V772SlvjPhkE7+0fem 6u23Bzcvr5qcymyYvpW9U+Y+11TXIteFc/PN+Gb269j4qRbULpB7oNUdoqmzaVapR9cU24xf XQXMQVe2lc2YFSZupsRSnJFoqMVcVJwIALYNTyiuAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_j02INZpvaVaRc63uu8wzcuFBk0>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 07:54:00 -0000

SGksDQoNCi4uLg0KDQo+PiDCpzQuMy4yOg0KPj4NCj4+PiDCoCBUaGVzZSByZXRyYW5zbWlzc2lv
bnMgTVVTVA0KPj4+IMKgIGNlYXNlIG9uIHJlY2VpcHQgb2YgYW4gSU5GTyByZXF1ZXN0IGNhcnJ5
aW5nIGEgJ3RyaWNrbGUtaWNlJyBJbmZvDQo+Pj4gwqAgUGFja2FnZSBib2R5IG9yIG9uIHRyYW5z
bWlzc2lvbiBvZiB0aGUgQW5zd2VyIGluIGEgMnh4IHJlc3BvbnNlLg0KPj4gV2h5IGRvZXMgdGhp
cyByZXF1aXJlIHRoYXQgc3BlY2lmaWMgSU5GTyB0byBzdG9wIHJldHJhbnNtaXNzaW9uPyBUaGUg
DQo+PiBvbmx5IHJlcXVpcmVtZW50IGlzIHRoYXQgdGhlIGFuc3dlcmVyIGtub3dzIHRoYXQgdGhl
IG9mZmVyZXIgaGFzIA0KPj4gcmVjZWl2ZWQgdGhlIHByb3Zpc2lvbmFsIHJlc3BvbnNlLiBUaGUg
b2ZmZXJlciBjYW5ub3Qgc2VuZCANCj4+IHBvc3QtSU5WSVRFIHJlcXVlc3RzIHRvIHRoZSBhbnN3
ZXJlciB1bnRpbCBhIGRpYWxvZyBpcyBlc3RhYmxpc2hlZCwgDQo+PiBhbmQgdGhlIG9ubHkgd2F5
cyBhIGRpYWxvZyBjYW4gYmUgZXN0YWJsaXNoZWQgYXQgdGhlIG9mZmVyZXIgaXMgDQo+PiByZWNl
aXB0IG9mIGEgcHJvdmlzaW9uYWwgb3IgZmluYWwgcmVzcG9uc2UuIFNvLCBhcyBzb29uIGFzIHlv
dSBnZXQgDQo+PiAqYW55KiByZXF1ZXN0IGZyb20gdGhlIG9mZmVyZXIsIHlvdSBrbm93IHRoYXQg
dGhlIHByb3Zpc2lvbmFsIA0KPj4gcmVzcG9uc2UgaGFzIGFycml2ZWQuDQo+Pg0KPj4gSSB0aGlu
ayB0aGlzIHBhc3NhZ2UgbWVhbnMgdG8gc2F5ICJUaGVzZSByZXRyYW5zbWlzc2lvbnMgTVVTVCBj
ZWFzZSANCj4+IG9uIHJlY2VpcHQgb2YgYW55IGluLWRpYWxvZyByZXF1ZXN0IGZyb20gdGhlIG9m
ZmVyZXIuIFRoZSBvZmZlcmVyIA0KPj4gY2Fubm90IHNlbmQgaW4tZGlhbG9nIHJlcXVlc3RzIHVu
dGlsIGl0IHJlY2VpdmVzIGEgcmVzcG9uc2UsIHNvIHRoZSANCj4+IGFycml2YWwgb2Ygc3VjaCBh
IHJlcXVlc3QgcHJvdmVzIHRoYXQgdGhlIHJlc3BvbnNlIGhhcyBhcnJpdmVkLiINCj4+DQo+PiAt
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0NCj4+IC0tLS0tLQ0KPj4NCj4gU3VyZSwgYW55IG90aGVyIHJlcXVlc3Qgd2ls
bCBkbyB0aGUgdHJpY2sgYXMgd2VsbC4gSG93ZXZlciwgYXMgaXQgaXMgDQo+IG5vdCBndWFyYW50
ZWVkIHRoYXQgYSByZXF1ZXN0IG90aGVyIHRoYW4gc2FpZCBJTkZPIGlzIHNlbnQsIEknZCBwcmVm
ZXIgDQo+IHRvIHNheQ0KPg0KPiAiVGhlc2UgcmV0cmFuc21pc3Npb25zIE1VU1QgY2Vhc2Ugb24g
cmVjZWlwdCBvZiBhbiBJTkZPIHJlcXVlc3QgDQo+IGNhcnJ5aW5nIGEgJ3RyaWNrbGUtaWNlJyBJ
bmZvDQo+IMKgUGFja2FnZSBib2R5LCBvbiByZWNlaXB0IGFueSBpbi1kaWFsb2cgcmVxdWVzdCBm
cm9tIHRoZSBvZmZlcmVyIG9yIG9uIA0KPiB0cmFuc21pc3Npb24gb2YgdGhlIEFuc3dlciBpbiBh
IDJ4eCByZXNwb25zZS4gVGhlIG9mZmVyZXIgY2Fubm90IHNlbmQgDQo+IGluLWRpYWxvZyByZXF1
ZXN0cyB1bnRpbCBpdCByZWNlaXZlcyBhIHJlc3BvbnNlLCBzbyB0aGUgYXJyaXZhbCBvZiANCj4g
c3VjaCBhIHJlcXVlc3QgcHJvdmVzIHRoYXQgdGhlIHJlc3BvbnNlIGhhcyBhcnJpdmVkLiINCg0K
RG8geW91IG5lZWQgdG8gdGFsayBhYm91dCByZWNlaXB0IG9mIGEgYm9keT8gDQoNCkkgc3VnZ2Vz
dCAib24gcmVjZWlwdCBvZiBhbiBJTkZPIHJlcXVlc3QgYXNzb2NpYXRlZCB3aXRoIHRoZSAndHJp
Y2tsZS1pY2UnIEluZm8gUGFja2FnZSIuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQo=


From nobody Thu Apr  5 06:58:19 2018
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 920D9124B0A for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 06:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXblcZLBcavh for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 06:58:10 -0700 (PDT)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::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 B2A4112741D for <mmusic@ietf.org>; Thu,  5 Apr 2018 06:58:05 -0700 (PDT)
Received: by mail-ot0-x231.google.com with SMTP id n40-v6so27256109otd.3 for <mmusic@ietf.org>; Thu, 05 Apr 2018 06:58:05 -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=WLpmyIDqOMUf5s2AIrD0Pc00WHD3ar2vHK0HTfOie4o=; b=NY6J8zd645eIdxLACjLUmfwGUe5xRl0nYCZl73oM5WH1zcvhuTSAXllBkPCM8h0/j/ 31XF/eVppy0TcdQNVU9AeRw6jCSAhpbn0iQBF09+B+cjt9szpvQhO9ZMy7Ktg4zR2Irv KLGID9tgQqFSO6jcM2sjje+B7uwCJbP0Tv2+U1zpTFmgEXaCOCGyl4OAJxwSmV+OxSbp 1KpjEu4pYv8ImPNQhDNjjIw+Jdd5Gy0Tre2I0iEy0jDvvnSubHiTu5cVC1ShTsxamEz3 u6jtm9mCDVrjeWZONX/DzIEtdxmxM/k6bBzwAOaPSEtoPyr+FgAtnSlO+ZBENCqbIMjq Gehg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WLpmyIDqOMUf5s2AIrD0Pc00WHD3ar2vHK0HTfOie4o=; b=pVLNrbgJduYm8zO//RkMzuvqO5v+SDYA2GzuTVrN1YDAHV+4hlId0ungFuAQDzWyxN AaQvQ2Mw1EzKX3sYqVxEMjHoa2ag2rkCQoY+kyqirtwy4RMijMRcy+mOEHjlP72qicPa 4/WBST/OzNj7z3bfg4AT5rKPhNNS0zoQE2ThRp6YTUzhK8Jnw5BzRL6pBFdzYooq+frH nYgeKcfRh8Qkewccb2sFhKIQ2et6oX/4ep0fXyjV7c/wYNTdTXRx6C7NELzaEkUvjj4y FuhgohY3n1PlKZd9+LoQN4GIhimoZ/vtz2pM08IWu7tCEjzqmLtcNI0TjegIzX/wlm9J XVng==
X-Gm-Message-State: ALQs6tCOi+DD9YxwCeiAOIv/MXS0NVg8dK0ah78aPIVIVo7wFgiir4DY 4f4fMlUef5MqXYs0UwC+eb5XauWPtyR4df/p0ORmMw==
X-Google-Smtp-Source: AIpwx4/7pNdtGRJEneaLIxLg8U12MLi+ldmUybxCDyKn1U60WqPl4vgosED+XEBg0LqIAF6CSz9ejJsi00O5FcujC7M=
X-Received: by 2002:a9d:4c16:: with SMTP id l22-v6mr2856280otf.176.1522936684910;  Thu, 05 Apr 2018 06:58:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.130 with HTTP; Thu, 5 Apr 2018 06:57:24 -0700 (PDT)
In-Reply-To: <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com>
References: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com> <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 5 Apr 2018 06:57:24 -0700
Message-ID: <CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org,  mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001eafb105691a54ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Rp9_kC14t5cAL1np1u3dlEe3P3w>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 13:58:13 -0000

--0000000000001eafb105691a54ef
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 3, 2018 at 11:46 AM, Thomas Stach <thomass.stach@gmail.com>
wrote:

> EKR,
>
> thanks for your comments, responses inline
>
> On 2018-04-03 00:54, Eric Rescorla wrote:
>
> Eric Rescorla has entered the following ballot position for
> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
>    the Offer (as would be the case when Half Trickle is performed or
>    when new candidates have not been learned since then).
> IMPORTANT: They must be in order, right?
>
> I'm not sure what the issues is here.
> The cited text addresses the first of two cases, i.e. the case  where the
> INFO requests repeats
>  the exact same set of candidates that was already provided in the initial
> offer.
> This could happen when
> a) Half Trickle is used (all candidate were already in the initial offer)
> or
> b) Full Trickle is used where  the offerer is currently gathering
> additional candidates, but did not yet get them.
>
> The second case (Full Trickle with additional candidates already
> available) is addressed in the subsequent paragraph.
> .. and yes the candidates are sent in the order as they were gathered.
>

Right. I'm saying you need to say that.


   'application/trickle-ice-sdpfrag' bodies do not interfere with the
>    Offer/Answer procedures as specified in [RFC3264].
> IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.
>
> 5888 is cited as it defines the a=mid: attribute that we used for
> identifying the m-line to which a candidate belongs.
> The a=mid: attribute helps in case of multiple m-lines, when we already
> have gathered candidates
> for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>

Right. You need to describe what a pseudo-m= line is because it's not
defined anywhere.


   sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
>    the same order as they were gathered.  In other words, the sequence
>    of a previously sent list of candidates MUST NOT change in subsequent
>
> IMPORTANT: This appears to conflict with the guidance in Section 6 of
> the trickle document, which is about reordering candidates from how
> they were gathered.
>
>
> Do you mean section 7  which talks about reordering candidate _pairs_ at
> the IE agents?
>

No. Section 16, sorry for the typo.

   To achieve this, when trickling candidates, agents MUST respect the
   order in which the components and streams appear (implicitly or
   explicitly) as they have been negotiated by means of the relevant
   candidate information.  Therefore candidates for a given component
   MUST NOT be conveyed prior to candidates for a component with a lower
   ID number within the same foundation.  In addition, candidates MUST
   be paired, following the procedures in Section 8.1.1, in the same
   order they are conveyed.



We  require that the ordering of the _candidates_ MUST not change
> when the candidates are sent several times from one  ICE agent to its peer
> in subsequent INFO requests.
>

The problem is the text "same order they were gathered" because the ICE
trickle text
requires sending them in an order different from when they were gathered.


I don't see a conflict.
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
>   SIP message.  At the remote agent the gathering procedure is repeated
>    and candidates are sent to the first agent.  Finally, a third phase
>    starts where connectivity between all candidates in both sets is
>
> This suggests that they have to happen in sequence, but that's not true.
>
>    include in each "m="-line a "a=mid:" attribute in accordance to
>    [RFC5888].
>
> Why is this required?
>
> As above, the a=mid: attribute helps in case of multiple m-lines, when we
> already have gathered candidates
> for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>

Right. You need to actually explain this.


   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
>    is not yet provided.
>
> Can you explain why you cease retransmitting on receiving INFO? I assume
> because it's an implicit ACK of your INFO?
>
> The INFO is an ACK that an early dialog is now established, such that
> INFOs can be send in the reverse direction as well.
>

It would be helpful to explain this as well. I defer to the ART ADs on the
suitability of this technique.


   m=lines that they pertain to.  The correspondence can be made via the
>    "a=mid:" attributes.
>
> This whole section needs to be rewritten to make clear what's going on:
>
>     candidates are grouped in sections headed by "pseudo" m=lines
>     These sections contain a=mid values which point back to the true m=line.
>
> Would it be sufficient to rephrase as follows?
>
> Note, that there is no requirement that the Info request body
>    contains as many pseudo m= lines as the Offer/Answer contains m=
>    lines, nor that the pseudo m= lines be in the same order as the
>    m=lines that they pertain to.  The correspondence can be made via the
>    "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
>     These sections contain a=mid: attribute values which point back to the true m=line.
>
>
Sure.



> Kind regards
> Thomas
>
>
>
>

--0000000000001eafb105691a54ef
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 Tue, Apr 3, 2018 at 11:46 AM, Thomas Stach <span dir=3D"ltr">&lt;<a =
href=3D"mailto:thomass.stach@gmail.com" target=3D"_blank">thomass.stach@gma=
il.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-lef=
t:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <p>EKR,</p>
    <p>thanks for your comments, responses inline<br>
    </p><span class=3D"gmail-">
    <br>
    <div class=3D"gmail-m_-3709797337778756038moz-cite-prefix">On 2018-04-0=
3 00:54, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <pre>Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss

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


Please refer to <a class=3D"gmail-m_-3709797337778756038moz-txt-link-freete=
xt" href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" targ=
et=3D"_blank">https://www.ietf.org/iesg/<wbr>statement/discuss-criteria.<wb=
r>html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class=3D"gmail-m_-3709797337778756038moz-txt-link-freetext" href=3D"http=
s://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/" target=3D"=
_blank">https://datatracker.ietf.org/<wbr>doc/draft-ietf-mmusic-trickle-<wb=
r>ice-sip/</a>



------------------------------<wbr>------------------------------<wbr>-----=
-----
DISCUSS:
------------------------------<wbr>------------------------------<wbr>-----=
-----

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?</pre>
    </blockquote></span>
    I&#39;m not sure what the issues is here.<br>
    The cited text addresses the first of two cases, i.e. the case=C2=A0
    where the INFO requests repeats <br>
    =C2=A0the exact same set of candidates that was already provided in the
    initial offer. <br>
    This could happen when <br>
    a) Half Trickle is used (all candidate were already in the initial
    offer) or<br>
    b) Full Trickle is used where=C2=A0 the offerer is currently gathering
    additional candidates, but did not yet get them.<br>
    <br>
    The second case (Full Trickle with additional candidates already
    available) is addressed in the subsequent paragraph.<br>
    .. and yes the candidates are sent in the order as they were
    gathered.<span class=3D"gmail-"><br></span></div></blockquote><div><br>=
</div><div>Right. I&#39;m saying you need to say that.</div><div><br></div>=
<div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgco=
lor=3D"#FFFFFF"><span class=3D"gmail-">
    <blockquote type=3D"cite">
      <pre>   &#39;application/trickle-ice-<wbr>sdpfrag&#39; bodies do not =
interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: &quot;pseudo&quot; m=3D lines are not defined in 5888 so this is=
 very unclear.</pre>
    </blockquote></span>
    5888 is cited as it defines the a=3Dmid: attribute that we used for
    identifying the m-line to which a candidate belongs.<br>
    The a=3Dmid: attribute helps in case of multiple m-lines, when we
    already have gathered candidates <br>
    for e.g. the first and fourth m-line, but not for the 2nd and 3rd. <br>=
</div></blockquote><div><br></div><div>Right. You need to describe what a p=
seudo-m=3D line is because it&#39;s not defined anywhere.</div><div><br></d=
iv><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bg=
color=3D"#FFFFFF"><span class=3D"gmail-">
    <blockquote type=3D"cite">
      <pre>   sent under the same combination of &quot;a=3Dice-pwd:&quot; a=
nd &quot;a=3Dice-ufrag:&quot; in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.</pre>
    </blockquote>
    <br></span>
    Do you mean section 7=C2=A0 which talks about reordering candidate
    _pairs_ at the IE agents?<br></div></blockquote><div><br></div><div>No.=
 Section 16, sorry for the typo.</div><div><br></div><div>=C2=A0=C2=A0 To a=
chieve this, when trickling candidates, agents MUST respect the<br>=C2=A0=
=C2=A0 order in which the components and streams appear (implicitly or<br>=
=C2=A0=C2=A0 explicitly) as they have been negotiated by means of the relev=
ant<br>=C2=A0=C2=A0 candidate information.=C2=A0 Therefore candidates for a=
 given component<br>=C2=A0=C2=A0 MUST NOT be conveyed prior to candidates f=
or a component with a lower<br>=C2=A0=C2=A0 ID number within the same found=
ation.=C2=A0 In addition, candidates MUST<br>=C2=A0=C2=A0 be paired, follow=
ing the procedures in Section 8.1.1, in the same<br>=C2=A0=C2=A0 order they=
 are conveyed.<br><br></div><div><br></div><div> <br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF">
    We=C2=A0 require that the ordering of the _candidates_ MUST not change=
=C2=A0 <br>
    when the candidates are sent several times from one=C2=A0 ICE agent to
    its peer in subsequent INFO requests.<br></div></blockquote><div><br></=
div><div>The problem is the text &quot;same order they were gathered&quot; =
because the ICE trickle text</div><div>requires sending them in an order di=
fferent from when they were gathered.</div><div><br></div><div><br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF">
    I don&#39;t see a conflict.<span class=3D"gmail-"><br>
    <blockquote type=3D"cite">
      <pre>------------------------------<wbr>-----------------------------=
-<wbr>----------
COMMENT:
------------------------------<wbr>------------------------------<wbr>-----=
-----

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that&#39;s not true=
.

   include in each &quot;m=3D&quot;-line a &quot;a=3Dmid:&quot; attribute i=
n accordance to
   [RFC5888].

Why is this required?</pre>
    </blockquote></span>
    As above, the a=3Dmid: attribute helps in case of multiple m-lines,
    when we already have gathered candidates <br>
    for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
    </div></blockquote><div><br></div><div>Right. You need to actually expl=
ain this.</div><div><br></div><div> <br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><span class=3D"gmail-"><block=
quote type=3D"cite">
      <pre>   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an=
 Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it&#39;s an implicit ACK of your INFO?</pre>
    </blockquote></span>
    The INFO is an ACK that an early dialog is now established, such
    that INFOs can be send in the reverse direction as well.<span class=3D"=
gmail-"><br></span></div></blockquote><div><br></div><div>It would be helpf=
ul to explain this as well. I defer to the ART ADs on the suitability of th=
is technique.</div><div><br></div><div> <br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><span class=3D"gmail-">
    <blockquote type=3D"cite">
      <pre>   m=3Dlines that they pertain to.  The correspondence can be ma=
de via the
   &quot;a=3Dmid:&quot; attributes.

This whole section needs to be rewritten to make clear what&#39;s going on:

    candidates are grouped in sections headed by &quot;pseudo&quot; m=3Dlin=
es
    These sections contain a=3Dmid values which point back to the true m=3D=
line.
</pre>
    </blockquote></span>
    Would it be sufficient to rephrase as follows?<br>
    <pre class=3D"gmail-m_-3709797337778756038newpage" style=3D"font-size:1=
3.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:norma=
l;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;le=
tter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;wo=
rd-spacing:0px;text-decoration-style:initial;text-decoration-color:initial"=
>Note, that there is no requirement that the Info request body
   contains as many pseudo m=3D lines as the Offer/Answer contains m=3D
   lines, nor that the pseudo m=3D lines be in the same order as the
   m=3Dlines that they pertain to.  The correspondence can be made via the
   &quot;a=3Dmid:&quot; attributes since candidates are grouped in sections=
 headed by &quot;pseudo&quot; m=3Dlines.
    These sections contain a=3Dmid: attribute values which point back to th=
e true m=3Dline.</pre></div></blockquote><div><br></div><div>Sure.</div><di=
v><br></div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div bgcolor=3D"#FFFFFF"><pre class=3D"gmail-m_-3709797337778756038newpa=
ge" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb=
(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:n=
ormal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0p=
x;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-d=
ecoration-color:initial">
Kind regards
Thomas=20
</pre>
    <br>
    <br>
  </div>

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

--0000000000001eafb105691a54ef--


From nobody Thu Apr  5 07:26:43 2018
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 2D51C12D94A for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 07:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgmRqXTG28eo for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 07:26:35 -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 060A612D944 for <mmusic@ietf.org>; Thu,  5 Apr 2018 07:26:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=uyMg8Q6YPYoedXYSDCyVteBwkjuvmcaEkVmOkC/Z1EQ5dVyzkVd4V8KdrvNVlM/p0x6ky2p1te/M7edakXdL9O1nTiPcG5NX6dbY6yvlZGvMsukDiJYuUt8l/OUfJ7v0C1GJ3ZeVlIRSNi5TLf6eJgAadI0pj+lit0EXnvL//G0=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 22618 invoked from network); 5 Apr 2018 16:19:52 +0200
Received: from i577bcef2.versanet.de (HELO ?192.168.178.24?) (87.123.206.242) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 5 Apr 2018 16:19:52 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com>
Date: Thu, 5 Apr 2018 16:19:50 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net>
References: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com> <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
X-PPP-Message-ID: <20180405141952.22609.17457@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/r077t5y7MpB3wRq-aHsiREyEnxU>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 14:26:37 -0000

Hi Thomas,

> Am 04.04.2018 um 21:54 schrieb Thomas Stach <thomass.stach@gmail.com>:
>=20
> Mirja,
>=20
> thanks for your comments.
>=20
> On 2018-04-03 16:37, Mirja K=C3=BChlewind wrote:
>> Mirja K=C3=BChlewind has entered the following ballot position for
>> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>=20
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut =
this
>> introductory paragraph, however.)
>>=20
>>=20
>> Please refer to=20
>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>=20
>> for more information about IESG DISCUSS and COMMENT positions.
>>=20
>>=20
>> The document, along with other ballot positions, can be found here:
>>=20
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>>=20
>>=20
>>=20
>>=20
>> =
----------------------------------------------------------------------
>> DISCUSS:
>> =
----------------------------------------------------------------------
>>=20
>> Thanks for the well-written doc and the quick response to the initial =
tsv
>> review. Also thanks to J=C3=B6rg for the thorough and very helpful =
review!
>>=20
>> As flagged by the tsv review, there can be an issue with the =
aggregation of
>> candidates in one INFO message when rate limited and the path MTU/UPD
>> fragmentation. While this is a small point only and I'm sure it can =
be easily
>> addressed, it important enough that I decided to put a discuss in. =
I'm sure
>> this can be resolved quickly as well.
>>=20
> As large messages are already addressed in RFC 3261, I could add =
something like
> "As a potentially large number of candidates are aggregated in a INFO =
request,=20
> the message size can easily exceed the path MTU. SIP [RF3261] requires =
that if a request
> is within 200 bytes of the path MTU, or if it is larger than 1300 =
bytes and the path MTU is unknown,
> that the request is sent using an RFC 2914 [43] congestion controlled =
transport protocol,=20
> such as TCP.

The only point is the interaction with the rate limit here. If you have =
to split up into two/multiple messages, you will not be able to send =
both immediately but have to wait for another interval. Maybe that can =
be further clarified with an additional sentence.

> "
>> Also if the document could give further guidance on an acceptable =
maximum for
>> the rate of INFO requests that be even better!
>>=20
> Adam proposed in his review to=20
>=20
> "... require some minimum quarantine period between INFO requests =
(probably something in the range of 20 ms),=20
> during which any new candidates that are gathered are aggregated into =
the next INFO message."
>=20
> Would that be enough of a guidance?

Yes, that would be good! Usually we recommends something like one =
message per RTT. So probably 100ms or 200ms would be on the safe side =
but lower might be fine as well if the typically deployment scenario =
assumes a shorter RTT.


>>=20
>>=20
>> =
----------------------------------------------------------------------
>> COMMENT:
>> =
----------------------------------------------------------------------
>>=20
>> Editorial comments:
>>=20
>> 1) sec 4.3.2: "When sending the Answer in the 200 OK response to the =
INVITE
>> request,
>>    the Answerer needs to repeat exactly the same Answer that was
>>    previously sent in the unreliable provisional response in order to
>>    fulfill the corresponding requirements in [RFC3264].  Thus, the
>>    Offerer needs to be prepared for receiving a different number of
>>    candidates in that repeated Answer than previously exchanged via
>>    trickling and MUST ignore the candidate information in that 200 OK
>>    response."
>>    What do I miss? Why can there be a different number of candidates =
if the
>>    repeated Answer needs to be exactly the same...? Or is there an =
"not"
>>    missing? Not an expert though, so might be just me...
>>=20
> If the answer is sent in a provisional response, it might have =
included a small  number (or even 0) of candidates.
> Before the 200 OK is sent the answerer might have trickled additional =
candidates in INFOs.=20
> However, the additional candidates will not appear in the answer in =
the body of the 200OK.=20
> This is due to a requirement in RFC3264, that the answer in the =
provisional response must be exactly the same as in the 200OK.
> So the total number of candidates that the offerer received will be =
different from the number of candidates in that answer.

Ah this is about the 200Ok answer. Somehow I missed that.

>=20
>> ,
>>=20
>> 2) I guess section 10.1 could also be moved to the appendix but it is =
short
>> enough that leaving it in the body is fine as well.
>>=20
> So, I probably leave it where it is.

Sure!

Thanks!

Mirja


>=20
> Thanks for your review
>=20
> Thomas
>>=20
>=20


From nobody Thu Apr  5 10:12:54 2018
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 51CE21201F8; Thu,  5 Apr 2018 10:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gkuVrMIsUudi; Thu,  5 Apr 2018 10:12:45 -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 577FF120724; Thu,  5 Apr 2018 10:12:45 -0700 (PDT)
Received: by mail-yb0-x234.google.com with SMTP id y18-v6so3787979ybb.7; Thu, 05 Apr 2018 10:12:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5IhczkT0taZ8P/dj+6SDHZgPpXU5j5jk8V60S/SxO7w=; b=Nh4H+JTr8D+vaw2g09dAq27FqXoiHy5lR4KRE9vSUZ7WhcUC/LtGoN92HzfgodNlCB aqURJkEAgzPUifGSgNbmPZZ/qOlDwmtSiMMpmBM+oxBY5iWLUJ0UEoU43vNWS4eesFtq YT/zp+e7k2p79pl7nejfITQdN7gh5CvZLXphGGimaYrDw+aU+usguHlkCf/WVhRlW8Zw F1qG8+kDN2IcMNbRoa9F1HgSxwy+BLUxBhzXYwg7hBFkNvrTjT+1e/RPFFD1kv5RcvW7 XaegbEtMAqWKu6JaDQXipfqWvaT2jNYJryP/wCPqBTOT4esv4aEBq+yFFOTO9fXq2SWE qh0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5IhczkT0taZ8P/dj+6SDHZgPpXU5j5jk8V60S/SxO7w=; b=dBL9+SMblGiOPC5cJT1qohxhSlpkP1GMylk97BrQmT22yL1EHfRAkBtG7N0S77VU0U vWyT0tfk+bMoC1mfqFgdoe90kz9HSAq6pftVEb+W5x6n8JIU39YSmrU/uhy8i6sqmh/k dyBe+WxWDTCKPMxDtP6jFiLKnVE7Hk1MUXKGpUbtpDUKs1L8US8P0salvj4Xz0LrDHot fO5xTuJ1k7z0zgcOjf3WhLa67Wgjii+hp0yskWzJcaPiwI1un45Y6Nfj+JfvKLDE+0X1 FKeYcemHkuq/E4j4rDB80xJYb1DeFM1sIV7FbvtyDGEWScZmh1lAKooo3SczOn1dB4wt 1SHA==
X-Gm-Message-State: ALQs6tB9cNMGjqBXBZ2rPXJuwyaYcqMHmly/cm/zwQ6Gh3LugfEG15Yc TzNXhJQOZnhBfrLjHXBDeRL3FVtZZppEUMOp8/8=
X-Google-Smtp-Source: AIpwx4+GEW/I/uMtYVUq3qwx+yzIBYFlSuRzYDc4xM2h0b8SOSNdxvGFDGsfoiO8dAHCRdx5+ygWmNJZedhzaqUZn5E=
X-Received: by 10.129.79.199 with SMTP id d190mr5114819ywb.19.1522948364498; Thu, 05 Apr 2018 10:12:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:e757:0:0:0:0:0 with HTTP; Thu, 5 Apr 2018 10:12:44 -0700 (PDT)
In-Reply-To: <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net>
References: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com> <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com> <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 5 Apr 2018 12:12:44 -0500
Message-ID: <CAKKJt-datvsoPwZ=pO28XPMKuKm0bGGV5SdDZvW0=cbpfh9DRQ@mail.gmail.com>
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: Thomas Stach <thomass.stach@gmail.com>, fandreas@cisco.com, mmusic-chairs@ietf.org,  draft-ietf-mmusic-trickle-ice-sip@ietf.org, The IESG <iesg@ietf.org>, mmusic@ietf.org
Content-Type: multipart/alternative; boundary="001a114dd9a046fd7b05691d0c9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AWg8ZqNchhjpzDqfQ10BcSmyQRM>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 17:12:48 -0000

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

This is Mirja's ballot thread, but ...

On Thu, Apr 5, 2018 at 9:19 AM, Mirja Kuehlewind (IETF) <ietf@kuehlewind.ne=
t
> wrote:

> Hi Thomas,
>
> > Am 04.04.2018 um 21:54 schrieb Thomas Stach <thomass.stach@gmail.com>:
> >
> > Mirja,
> >
> > thanks for your comments.
> >
> > On 2018-04-03 16:37, Mirja K=C3=BChlewind wrote:
> >> Mirja K=C3=BChlewind has entered the following ballot position for
> >> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
> >>
> >> When responding, please keep the subject line intact and reply to all
> >> email addresses included in the To and CC lines. (Feel free to cut thi=
s
> >> 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-trickle-ice-sip/
> >>
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> DISCUSS:
> >> ----------------------------------------------------------------------
> >>
> >> Thanks for the well-written doc and the quick response to the initial
> tsv
> >> review. Also thanks to J=C3=B6rg for the thorough and very helpful rev=
iew!
> >>
> >> As flagged by the tsv review, there can be an issue with the
> aggregation of
> >> candidates in one INFO message when rate limited and the path MTU/UPD
> >> fragmentation. While this is a small point only and I'm sure it can be
> easily
> >> addressed, it important enough that I decided to put a discuss in. I'm
> sure
> >> this can be resolved quickly as well.
> >>
> > As large messages are already addressed in RFC 3261, I could add
> something like
> > "As a potentially large number of candidates are aggregated in a INFO
> request,
> > the message size can easily exceed the path MTU. SIP [RF3261] requires
> that if a request
> > is within 200 bytes of the path MTU, or if it is larger than 1300 bytes
> and the path MTU is unknown,
> > that the request is sent using an RFC 2914 [43] congestion controlled
> transport protocol,
> > such as TCP.
>
> The only point is the interaction with the rate limit here. If you have t=
o
> split up into two/multiple messages, you will not be able to send both
> immediately but have to wait for another interval. Maybe that can be
> further clarified with an additional sentence.
>
> > "
> >> Also if the document could give further guidance on an acceptable
> maximum for
> >> the rate of INFO requests that be even better!
> >>
> > Adam proposed in his review to
> >
> > "... require some minimum quarantine period between INFO requests
> (probably something in the range of 20 ms),
> > during which any new candidates that are gathered are aggregated into
> the next INFO message."
> >
> > Would that be enough of a guidance?
>
> Yes, that would be good! Usually we recommends something like one message
> per RTT. So probably 100ms or 200ms would be on the safe side but lower
> might be fine as well if the typically deployment scenario assumes a
> shorter RTT.
>

I also appreciate this guidance (with or without Mirja's friendly
amendment). What I usually hope for, is "not saturating a path by retrying
at line rate" :-)

Anything that's not that, is a step in the right direction.

Spencer


>
>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> COMMENT:
> >> ----------------------------------------------------------------------
> >>
> >> Editorial comments:
> >>
> >> 1) sec 4.3.2: "When sending the Answer in the 200 OK response to the
> INVITE
> >> request,
> >>    the Answerer needs to repeat exactly the same Answer that was
> >>    previously sent in the unreliable provisional response in order to
> >>    fulfill the corresponding requirements in [RFC3264].  Thus, the
> >>    Offerer needs to be prepared for receiving a different number of
> >>    candidates in that repeated Answer than previously exchanged via
> >>    trickling and MUST ignore the candidate information in that 200 OK
> >>    response."
> >>    What do I miss? Why can there be a different number of candidates i=
f
> the
> >>    repeated Answer needs to be exactly the same...? Or is there an "no=
t"
> >>    missing? Not an expert though, so might be just me...
> >>
> > If the answer is sent in a provisional response, it might have included
> a small  number (or even 0) of candidates.
> > Before the 200 OK is sent the answerer might have trickled additional
> candidates in INFOs.
> > However, the additional candidates will not appear in the answer in the
> body of the 200OK.
> > This is due to a requirement in RFC3264, that the answer in the
> provisional response must be exactly the same as in the 200OK.
> > So the total number of candidates that the offerer received will be
> different from the number of candidates in that answer.
>
> Ah this is about the 200Ok answer. Somehow I missed that.
>
> >
> >> ,
> >>
> >> 2) I guess section 10.1 could also be moved to the appendix but it is
> short
> >> enough that leaving it in the body is fine as well.
> >>
> > So, I probably leave it where it is.
>
> Sure!
>
> Thanks!
>
> Mirja
>
>
> >
> > Thanks for your review
> >
> > Thomas
> >>
> >
>
>

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

<div dir=3D"ltr">This is Mirja&#39;s ballot thread, but ...=C2=A0<div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Apr 5, 2018 at 9:19=
 AM, Mirja Kuehlewind (IETF) <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@k=
uehlewind.net" target=3D"_blank">ietf@kuehlewind.net</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">Hi Thomas,<br>
<div><div class=3D"h5"><br>
&gt; Am 04.04.2018 um 21:54 schrieb Thomas Stach &lt;<a href=3D"mailto:thom=
ass.stach@gmail.com">thomass.stach@gmail.com</a>&gt;:<br>
&gt;<br>
&gt; Mirja,<br>
&gt;<br>
&gt; thanks for your comments.<br>
&gt;<br>
&gt; On 2018-04-03 16:37, Mirja K=C3=BChlewind wrote:<br>
&gt;&gt; Mirja K=C3=BChlewind has entered the following ballot position for=
<br>
&gt;&gt; draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss<br>
&gt;&gt;<br>
&gt;&gt; When responding, please keep the subject line intact and reply to =
all<br>
&gt;&gt; email addresses included in the To and CC lines. (Feel free to cut=
 this<br>
&gt;&gt; introductory paragraph, however.)<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Please refer to<br>
&gt;&gt; <a href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/iesg/<wbr>sta=
tement/discuss-criteria.<wbr>html</a><br>
&gt;&gt;<br>
&gt;&gt; for more information about IESG DISCUSS and COMMENT positions.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The document, along with other ballot positions, can be found here=
:<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-tric=
kle-ice-sip/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf=
.org/<wbr>doc/draft-ietf-mmusic-trickle-<wbr>ice-sip/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>----------<br>
&gt;&gt; DISCUSS:<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>----------<br>
&gt;&gt;<br>
&gt;&gt; Thanks for the well-written doc and the quick response to the init=
ial tsv<br>
&gt;&gt; review. Also thanks to J=C3=B6rg for the thorough and very helpful=
 review!<br>
&gt;&gt;<br>
&gt;&gt; As flagged by the tsv review, there can be an issue with the aggre=
gation of<br>
&gt;&gt; candidates in one INFO message when rate limited and the path MTU/=
UPD<br>
&gt;&gt; fragmentation. While this is a small point only and I&#39;m sure i=
t can be easily<br>
&gt;&gt; addressed, it important enough that I decided to put a discuss in.=
 I&#39;m sure<br>
&gt;&gt; this can be resolved quickly as well.<br>
&gt;&gt;<br>
&gt; As large messages are already addressed in RFC 3261, I could add somet=
hing like<br>
&gt; &quot;As a potentially large number of candidates are aggregated in a =
INFO request,<br>
&gt; the message size can easily exceed the path MTU. SIP [RF3261] requires=
 that if a request<br>
&gt; is within 200 bytes of the path MTU, or if it is larger than 1300 byte=
s and the path MTU is unknown,<br>
&gt; that the request is sent using an RFC 2914 [43] congestion controlled =
transport protocol,<br>
&gt; such as TCP.<br>
<br>
</div></div>The only point is the interaction with the rate limit here. If =
you have to split up into two/multiple messages, you will not be able to se=
nd both immediately but have to wait for another interval. Maybe that can b=
e further clarified with an additional sentence.<br>
<span class=3D""><br>
&gt; &quot;<br>
&gt;&gt; Also if the document could give further guidance on an acceptable =
maximum for<br>
&gt;&gt; the rate of INFO requests that be even better!<br>
&gt;&gt;<br>
&gt; Adam proposed in his review to<br>
&gt;<br>
&gt; &quot;... require some minimum quarantine period between INFO requests=
 (probably something in the range of 20 ms),<br>
&gt; during which any new candidates that are gathered are aggregated into =
the next INFO message.&quot;<br>
&gt;<br>
&gt; Would that be enough of a guidance?<br>
<br>
</span>Yes, that would be good! Usually we recommends something like one me=
ssage per RTT. So probably 100ms or 200ms would be on the safe side but low=
er might be fine as well if the typically deployment scenario assumes a sho=
rter RTT.<br></blockquote><div><br></div><div>I also appreciate this guidan=
ce (with or without Mirja&#39;s friendly amendment). What I usually hope fo=
r, is &quot;not saturating a path by retrying at line rate&quot; :-)</div><=
div><br></div><div>Anything that&#39;s not that, is a step in the right dir=
ection.</div><div><br></div><div>Spencer</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""><br>
<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>----------<br>
&gt;&gt; COMMENT:<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>----------<br>
&gt;&gt;<br>
&gt;&gt; Editorial comments:<br>
&gt;&gt;<br>
&gt;&gt; 1) sec 4.3.2: &quot;When sending the Answer in the 200 OK response=
 to the INVITE<br>
&gt;&gt; request,<br>
&gt;&gt;=C2=A0 =C2=A0 the Answerer needs to repeat exactly the same Answer =
that was<br>
&gt;&gt;=C2=A0 =C2=A0 previously sent in the unreliable provisional respons=
e in order to<br>
&gt;&gt;=C2=A0 =C2=A0 fulfill the corresponding requirements in [RFC3264].=
=C2=A0 Thus, the<br>
&gt;&gt;=C2=A0 =C2=A0 Offerer needs to be prepared for receiving a differen=
t number of<br>
&gt;&gt;=C2=A0 =C2=A0 candidates in that repeated Answer than previously ex=
changed via<br>
&gt;&gt;=C2=A0 =C2=A0 trickling and MUST ignore the candidate information i=
n that 200 OK<br>
&gt;&gt;=C2=A0 =C2=A0 response.&quot;<br>
&gt;&gt;=C2=A0 =C2=A0 What do I miss? Why can there be a different number o=
f candidates if the<br>
&gt;&gt;=C2=A0 =C2=A0 repeated Answer needs to be exactly the same...? Or i=
s there an &quot;not&quot;<br>
&gt;&gt;=C2=A0 =C2=A0 missing? Not an expert though, so might be just me...=
<br>
&gt;&gt;<br>
&gt; If the answer is sent in a provisional response, it might have include=
d a small=C2=A0 number (or even 0) of candidates.<br>
&gt; Before the 200 OK is sent the answerer might have trickled additional =
candidates in INFOs.<br>
&gt; However, the additional candidates will not appear in the answer in th=
e body of the 200OK.<br>
&gt; This is due to a requirement in RFC3264, that the answer in the provis=
ional response must be exactly the same as in the 200OK.<br>
&gt; So the total number of candidates that the offerer received will be di=
fferent from the number of candidates in that answer.<br>
<br>
</span>Ah this is about the 200Ok answer. Somehow I missed that.<br>
<span class=3D""><br>
&gt;<br>
&gt;&gt; ,<br>
&gt;&gt;<br>
&gt;&gt; 2) I guess section 10.1 could also be moved to the appendix but it=
 is short<br>
&gt;&gt; enough that leaving it in the body is fine as well.<br>
&gt;&gt;<br>
&gt; So, I probably leave it where it is.<br>
<br>
</span>Sure!<br>
<br>
Thanks!<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Mirja<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
&gt;<br>
&gt; Thanks for your review<br>
&gt;<br>
&gt; Thomas<br>
&gt;&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a114dd9a046fd7b05691d0c9d--


From nobody Thu Apr  5 12:48:46 2018
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 574C01242EA; Thu,  5 Apr 2018 12:48:45 -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 QtWLUXMCSwfg; Thu,  5 Apr 2018 12:48:43 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c: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 2CC1B120713; Thu,  5 Apr 2018 12:48:43 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id r131so10381773wmb.2; Thu, 05 Apr 2018 12:48:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=T6PfJBHK6IgVClp+vops+jrH/ubu2Em9J1BvZT42he4=; b=VIJGcG7EUnQWM4cwhZHNCKb5nL8aL18CfNoozxvIHN5+DIdXhQ+gLC6gxOVlxn/QZb dcVFC41gu8HHddE2sZ54eqtwOibWQ85nRSFen+T6qXvk/ByYhRnGHd0Cy37cj8fknEJs 4eiuJxGFLi16KyRW1i3DQIdNHe+p4GfmRr4i0RAQnt9XJW9EM+R4MAljrcnIN3RZGndQ Ja1K2KaLLx3535lIfpgHmhUDmvD/E8bS4J0BYLMDSPMg9NXUrOQxzksUhQwCuj9qszXe 8aeUsrkdQ7BAGDUJ79rlwKDCX4Twj2+nmIJNqVci4Nl7I9L68FLPPu2hKxYifzEzk4WW jF7A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=T6PfJBHK6IgVClp+vops+jrH/ubu2Em9J1BvZT42he4=; b=O40Ew6MdbZ90/vHiBEELQIKPJoeAdwffy678NFt9n9VmG7Gmlh7iDN7MUqAJBG133e lswZeNMo2zVC2PIZ5uugagLZrx5xwMPHxopGJkc8yPAiIjYqmvxC7h6s7+cHaFXPQVV5 rUwUDJjz917fPDbm+0LaJHIhj+MGQcG3jFPbd2wu9/WeUg3q/VPtdPCRvN9d8SJHfh9y x5JB+8gQ7yaSWwZdyFme9Ge+MtCCWpgzsTsv0RA9I9d8w6E/6+AZXlKWbSFHBo3jPABq kclISV+0tGoRP6sOppGzVxYKnZ3sJYQctFW05PKuU0C83X1UVGWLycxswlC5FZuN2a6G ZMSA==
X-Gm-Message-State: ALQs6tDE8vGy39wZ+8IAa3xqLfvcWm1yOxHCQjRwM2YrD7jTRx1WjsiT iwnhMs0ANLIl2uB+kVJYvObcaAGWXWs=
X-Google-Smtp-Source: AIpwx4+gBgDK+WTiDjAarcF3IKlskr3ZoNzqSqycMSHPdXWQCiJgrWvJmzwxV/Tm4pms4n4li8TqHA==
X-Received: by 10.28.249.18 with SMTP id x18mr177721wmh.122.1522957721267; Thu, 05 Apr 2018 12:48:41 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id m7sm7258406wrh.11.2018.04.05.12.48.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Apr 2018 12:48:40 -0700 (PDT)
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com> <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <76fa313a-d25b-d9a2-dbed-1290a48adfe0@gmail.com>
Date: Thu, 5 Apr 2018 21:48:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/IIsD2QC33QlG5gc_5PbdHrka2a0>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 19:48:45 -0000

Adam,


On 2018-04-04 21:42, Adam Roach wrote:
> Thanks for your quick responses! Your proposed resolutions all look 
> good to me. 
Thanks!
> I notice that you didn't respond to my comment on the "NOTE" in §4.4. 
> Should I expect an additional reply to address that comment?
Yes, you should.
I was distracted and then ....


>
> /a
>
<snip/>
> --------------------------------------------------------------------------- 
>
>>>
>>> §4.4:
>>>
>>>>   Note: At the time of writing this specification there were ongoing
>>>>   discussions if a functionality for removing already exchanged
>>>>   candidates would be useful.  Such a functionality is out of the 
>>>> scope
>>>>   of this specification and most likely needs to be signaled by means
>>>>   of a yet to be defined ICE extension, although it could in principle
>>>>   be achieved quite easily, e.g. without anticipating any solution by
>>>>   simply omitting a previously sent candidate from a subsequent INFO
>>>>   request.  However, if an implementation according to this
>>>>   specification receives such an INFO request with a missing candidate
>>>>   it would have to treat that as an exceptional case. Implementing
>>>>   appropriate recovery procedures at the receiving side is advisable
>>>>   for this situation.  Ignoring that a candidate was missing might 
>>>> be a
>>>>   sensible strategy.
>>> This seems like an interop nightmare. If you want a note about this 
>>> possibly
>>> being included in the future, please simply indicate that such an 
>>> ability will
>>> need to be explicitly signaled. Don't imply that implementations 
>>> might get SDP
>>> that violates the behavior defined in this document in some 
>>> ill-defined way,
>>> and just need to kind of gracefully deal with it, even if we don't 
>>> really know
>>> what it means at this point in time. There's no sensible way to code 
>>> for that.
As the discussion that led to the text ceased long ago, I would be happy 
to remove the text,
especially as it is just a note.
OK ?

Thanks
Thomas


From nobody Thu Apr  5 12:55:25 2018
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 B28751242EA; Thu,  5 Apr 2018 12:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZbCvC75j_WG; Thu,  5 Apr 2018 12:55:20 -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 D8B25120713; Thu,  5 Apr 2018 12:55:20 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w35JtEGi093801 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 5 Apr 2018 14:55:15 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Thomas Stach <thomass.stach@gmail.com>, The IESG <iesg@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com> <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com> <76fa313a-d25b-d9a2-dbed-1290a48adfe0@gmail.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <b60ce648-d9a0-2b7c-0998-2ce1d48b1e01@nostrum.com>
Date: Thu, 5 Apr 2018 14:55:09 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <76fa313a-d25b-d9a2-dbed-1290a48adfe0@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Ue4ZIh1Ip1Qee8yYpGeryMqfRRk>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 19:55:24 -0000

On 4/5/18 2:48 PM, Thomas Stach wrote:
> Adam,
>
>
> On 2018-04-04 21:42, Adam Roach wrote:
>> Thanks for your quick responses! Your proposed resolutions all look 
>> good to me. 
> Thanks!
>> I notice that you didn't respond to my comment on the "NOTE" in §4.4. 
>> Should I expect an additional reply to address that comment?
> Yes, you should.
> I was distracted and then ....
>
>
>>
>> /a
>>
> <snip/>
>> --------------------------------------------------------------------------- 
>>
>>>>
>>>> §4.4:
>>>>
>>>>>   Note: At the time of writing this specification there were ongoing
>>>>>   discussions if a functionality for removing already exchanged
>>>>>   candidates would be useful.  Such a functionality is out of the 
>>>>> scope
>>>>>   of this specification and most likely needs to be signaled by means
>>>>>   of a yet to be defined ICE extension, although it could in 
>>>>> principle
>>>>>   be achieved quite easily, e.g. without anticipating any solution by
>>>>>   simply omitting a previously sent candidate from a subsequent INFO
>>>>>   request.  However, if an implementation according to this
>>>>>   specification receives such an INFO request with a missing 
>>>>> candidate
>>>>>   it would have to treat that as an exceptional case. Implementing
>>>>>   appropriate recovery procedures at the receiving side is advisable
>>>>>   for this situation.  Ignoring that a candidate was missing might 
>>>>> be a
>>>>>   sensible strategy.
>>>> This seems like an interop nightmare. If you want a note about this 
>>>> possibly
>>>> being included in the future, please simply indicate that such an 
>>>> ability will
>>>> need to be explicitly signaled. Don't imply that implementations 
>>>> might get SDP
>>>> that violates the behavior defined in this document in some 
>>>> ill-defined way,
>>>> and just need to kind of gracefully deal with it, even if we don't 
>>>> really know
>>>> what it means at this point in time. There's no sensible way to 
>>>> code for that.
> As the discussion that led to the text ceased long ago, I would be 
> happy to remove the text,
> especially as it is just a note.
> OK ? 

I think that would be fine.

/a


From nobody Thu Apr  5 12:55:49 2018
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 499C512D7F2; Thu,  5 Apr 2018 12:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 9HiP1a1BXjZA; Thu,  5 Apr 2018 12:55:25 -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 6C24A126CD6; Thu,  5 Apr 2018 12:55:25 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id f125so10395985wme.4; Thu, 05 Apr 2018 12:55:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=rV1XaRuilA/Xe5w7nEPJ1h0i+WScg1xNW1Cp7KkMpL8=; b=Ju2NuDZ1PK1+W0O7//jOm+ZUloz8YgQE3s2eJ4DuQvmf8qdtNzf3l+702rLqesMnkY bqBFXIiImFUxZoU83tnivZ+kwHkHtI7JJ/p6Isjbp4T7msnKgIdP7vlcatm5QauX1ZPd EW/c/D2rh/90kapR9CxzSXUiTOnRPf4COs3hpCvMpfcgsGryy69SxbFhmplL+Tf2AIPs aAIcf6cK6+DD27fmBYCRvZeTjoW8eA4Myo/EEDZr9Mfkoi5qCp7NagMTnTmeC8o7uMth cUGFt2T0uto0qcMEIWzoC+l1JzuXUfdV5P+kc37Dhapsl39KhQ3tSBk1doeFey6tPrIf Z4YA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=rV1XaRuilA/Xe5w7nEPJ1h0i+WScg1xNW1Cp7KkMpL8=; b=lGo9LRo7FF7RcV6t6l6POvYztheeTWy+nH+x/KTVfFXqgZy81Bcvdu6xP9zlix1rlU 4V6jOY5v2UAbpjNhM+8AMHM77uWxf0+VXY6qtOAv36AWUPl7tjXKcmTl5m+OxsM88VKk aN1eWmcAYqNKvAlLeZvSHNPNidHeFdf6DhW8YJaJIBOCxILkdZVIVFXH0ReucMoJcL6j r1gCwgBkV0Wc4fz3XlOcbyqtBLwjsaz/FOgu+K1V+cq+Tr+QOW9iEHacC7HivxsuOgXp JT+rfKsbpMOZgJXMsfCf9+UwrQ0nVkklKiVJtwaJTnhcf3+cpnPAJv2n48z5ft4sdwes UVsQ==
X-Gm-Message-State: AElRT7FheFcK3h11YnMpsVuUw/vEbP5p1GIuYfeBCHb4CFZ48XaVfl4i dD4lKh0224eu3DwzlFLFTzM5qKhljyw=
X-Google-Smtp-Source: AIpwx4+HNLK7OFXp8Ul0mHj5bkjZ8t2qd6gXFWfUd3jmC6CaOVQN+F0Yce4HWAUa9/1Mu0lnJ77YsA==
X-Received: by 10.28.34.7 with SMTP id i7mr10561917wmi.97.1522958123607; Thu, 05 Apr 2018 12:55:23 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id c15sm11537119wrc.64.2018.04.05.12.55.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Apr 2018 12:55:22 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com> <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com> <7594FB04B1934943A5C02806D1A2204B72E48374@ESESSMB109.ericsson.se>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <6860212c-f34b-faed-a391-f8fcf519437c@gmail.com>
Date: Thu, 5 Apr 2018 21:55:21 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E48374@ESESSMB109.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/IIwFx-NZBZFct8NvDtPxtB6WfmQ>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 19:55:30 -0000

Christer,


On 2018-04-05 09:53, Christer Holmberg wrote:
> Hi,
>
> ...
>
>>> §4.3.2:
>>>
>>>>    These retransmissions MUST
>>>>    cease on receipt of an INFO request carrying a 'trickle-ice' Info
>>>>    Package body or on transmission of the Answer in a 2xx response.
>>> Why does this require that specific INFO to stop retransmission? The
>>> only requirement is that the answerer knows that the offerer has
>>> received the provisional response. The offerer cannot send
>>> post-INVITE requests to the answerer until a dialog is established,
>>> and the only ways a dialog can be established at the offerer is
>>> receipt of a provisional or final response. So, as soon as you get
>>> *any* request from the offerer, you know that the provisional
>>> response has arrived.
>>>
>>> I think this passage means to say "These retransmissions MUST cease
>>> on receipt of any in-dialog request from the offerer. The offerer
>>> cannot send in-dialog requests until it receives a response, so the
>>> arrival of such a request proves that the response has arrived."
>>>
>>> ---------------------------------------------------------------------
>>> ------
>>>
>> Sure, any other request will do the trick as well. However, as it is
>> not guaranteed that a request other than said INFO is sent, I'd prefer
>> to say
>>
>> "These retransmissions MUST cease on receipt of an INFO request
>> carrying a 'trickle-ice' Info
>>   Package body, on receipt any in-dialog request from the offerer or on
>> transmission of the Answer in a 2xx response. The offerer cannot send
>> in-dialog requests until it receives a response, so the arrival of
>> such a request proves that the response has arrived."
> Do you need to talk about receipt of a body?
I just want to mirror what is specified to be  sent by  the offerer.
An INFO with another body would fall in the "receipt of any in-dialog 
request" bucket
>
> I suggest "on receipt of an INFO request associated with the 'trickle-ice' Info Package".
I'd prefer not to over-use the verb "associate"

Thanks
Thomas
>
> Regards,
>
> Christer


From nobody Thu Apr  5 13:11:13 2018
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 B7B7B12D77B; Thu,  5 Apr 2018 13:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtJW7A91fsMu; Thu,  5 Apr 2018 13:11:03 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 D022B12D778; Thu,  5 Apr 2018 13:11:02 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id g8so8743098wmd.2; Thu, 05 Apr 2018 13:11:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=v3GzLbqV7JgDfV/vJVv5xiHNqxNplfrZIEACuCJ+p4U=; b=SAtf4to7slc/10rqlcWQRCdf+pvn65ndQvDsVzhjBAA+rnPGoJ/bs1poiYh1afj3iK 7FKHEh6sC+3o7/SiXTetbzyNve/e3gWOyISsOQFTz2lfYllwVat4uCouvUXLAPbTQn3U bIvviEDiflt5Kk77J+Ms9GAF1LDrzS21C3s/y0BLTso6cSAtW7O3xALdpoY40tOgdHNB O9OgsrLIYqyPThMvECuwGgwMNnWSEIuiFGJOqMqKB+zhNc5UQZDvizoGbR7qqu7u+8r6 Sg39uq50Le07HxOOKXG7N/XSy4CF+AsqY2lhIp8JpQ2oWdUGE3hAmXOPOXuQbeaj/iR3 vWkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=v3GzLbqV7JgDfV/vJVv5xiHNqxNplfrZIEACuCJ+p4U=; b=Gr43Fyeq0tZRsfbz6+UqAuk7aIsPaE7tQEgfnvkSzip8ps+TcqRTwLmwWQvb1ZZ3qz 1GZsERbqNIg0wetaLnwXvuLZXUIR4UYiQS/XVTx/naZc9XWJFx6ajg2z1bAxr9tUqNp4 Hv32guVmRGWsiOayzTkLCO3jy5ea19ym3petq+F24VzyS2D5e+xsccNvwTIrVhSZGSJl rwfDeuEGhDKwj2toPRxBdKD4ymrhPw61EiIY9bUzRbmp3YPtvpTMEqKymkhmemk0koZ3 qzjLh5aiJng6kOllYwsjzLXbL1NRYEn462c1cXjs3NrnKfN2S5UdJdPYtiFoePS8YYhj Bjpg==
X-Gm-Message-State: ALQs6tAGuZWUMxYXhy+2yeauAyJNcq70SXw1xJ0Z+CToAiKpMWyXBWPG fwQs3KaJzW1Ilxi1Hs4TBex0CFQ7kiY=
X-Google-Smtp-Source: AIpwx49Wl5h35giBCnc7VHuX+PKgp8OArKfPoo/xIzhxInYk2ry5Q1idggOe8uoa2nBmE0vHD46Lfg==
X-Received: by 10.28.53.194 with SMTP id c185mr12875111wma.27.1522959060990; Thu, 05 Apr 2018 13:11:00 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id n20sm6194435wmc.24.2018.04.05.13.10.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Apr 2018 13:10:59 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
References: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com> <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com> <CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <587c07b6-c086-c429-761a-ca655372f32e@gmail.com>
Date: Thu, 5 Apr 2018 22:10:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------3933EC3950E44741452B3EE2"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/WrbjhhdlNWQeIGCFwPiDpa-gHco>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 20:11:06 -0000

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

EKR,


On 2018-04-05 15:57, Eric Rescorla wrote:
>
>
> On Tue, Apr 3, 2018 at 11:46 AM, Thomas Stach <thomass.stach@gmail.com 
> <mailto:thomass.stach@gmail.com>> wrote:
>
>     EKR,
>
>     thanks for your comments, responses inline
>
>
>     On 2018-04-03 00:54, Eric Rescorla wrote:
>>     Eric Rescorla has entered the following ballot position for
>>     draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>
>>     When responding, please keep the subject line intact and reply to all
>>     email addresses included in the To and CC lines. (Feel free to cut this
>>     introductory paragraph, however.)
>>
>>
>>     Please refer tohttps://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-trickle-ice-sip/
>>     <https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/>
>>
>>
>>
>>     ----------------------------------------------------------------------
>>     DISCUSS:
>>     ----------------------------------------------------------------------
>>
>>         the Offer (as would be the case when Half Trickle is performed or
>>         when new candidates have not been learned since then).
>>     IMPORTANT: They must be in order, right?
>     I'm not sure what the issues is here.
>     The cited text addresses the first of two cases, i.e. the case 
>     where the INFO requests repeats
>      the exact same set of candidates that was already provided in the
>     initial offer.
>     This could happen when
>     a) Half Trickle is used (all candidate were already in the initial
>     offer) or
>     b) Full Trickle is used where  the offerer is currently gathering
>     additional candidates, but did not yet get them.
>
>     The second case (Full Trickle with additional candidates already
>     available) is addressed in the subsequent paragraph.
>     .. and yes the candidates are sent in the order as they were gathered.
>
>
> Right. I'm saying you need to say that.
OK, will do
>
>
>>         'application/trickle-ice-sdpfrag' bodies do not interfere with the
>>         Offer/Answer procedures as specified in [RFC3264].
>>     IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.
>     5888 is cited as it defines the a=mid: attribute that we used for
>     identifying the m-line to which a candidate belongs.
>     The a=mid: attribute helps in case of multiple m-lines, when we
>     already have gathered candidates
>     for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>
>
> Right. You need to describe what a pseudo-m= line is because it's not 
> defined anywhere.
Well, we have this text in section 4.4 at the first occurrence of the term.

    "... this is handled through the use of pseudo "m=" lines
    and identification tags in "a=mid:" attributes as defined in
    [RFC5888 <https://tools.ietf.org/html/rfc5888>].  Pseudo "m=" lines follow the SDP syntax for "m=" lines as
    defined in [RFC4566 <https://tools.ietf.org/html/rfc4566>], but provide no semantics other than indicating
    to which "m=" line a candidate belongs. "


Isn't that good enough?
>
>
>>         sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
>>         the same order as they were gathered.  In other words, the sequence
>>         of a previously sent list of candidates MUST NOT change in subsequent
>>
>>     IMPORTANT: This appears to conflict with the guidance in Section 6 of
>>     the trickle document, which is about reordering candidates from how
>>     they were gathered.
>
>     Do you mean section 7  which talks about reordering candidate
>     _pairs_ at the IE agents?
>
>
> No. Section 16, sorry for the typo.
Section 15? :-)
>
>    To achieve this, when trickling candidates, agents MUST respect the
>    order in which the components and streams appear (implicitly or
>    explicitly) as they have been negotiated by means of the relevant
>    candidate information.  Therefore candidates for a given component
>    MUST NOT be conveyed prior to candidates for a component with a lower
>    ID number within the same foundation.  In addition, candidates MUST
>    be paired, following the procedures in Section 8.1.1, in the same
>    order they are conveyed.
>
>
>
>     We  require that the ordering of the _candidates_ MUST not change
>     when the candidates are sent several times from one  ICE agent to
>     its peer in subsequent INFO requests.
>
>
> The problem is the text "same order they were gathered" because the 
> ICE trickle text
> requires sending them in an order different from when they were gathered.
OK, now I see. I will clarify and refer to section 15 of draft-ice-trickle
>
>
>     I don't see a conflict.
>>     ----------------------------------------------------------------------
>>     COMMENT:
>>     ----------------------------------------------------------------------
>>
>>        SIP message.  At the remote agent the gathering procedure is repeated
>>         and candidates are sent to the first agent.  Finally, a third phase
>>         starts where connectivity between all candidates in both sets is
>>
>>     This suggests that they have to happen in sequence, but that's not true.
>>
>>         include in each "m="-line a "a=mid:" attribute in accordance to
>>         [RFC5888].
>>
>>     Why is this required?
>     As above, the a=mid: attribute helps in case of multiple m-lines,
>     when we already have gathered candidates
>     for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>
>
> Right. You need to actually explain this.
I'll do
>
>
>>         section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
>>         is not yet provided.
>>
>>     Can you explain why you cease retransmitting on receiving INFO? I assume
>>     because it's an implicit ACK of your INFO?
>     The INFO is an ACK that an early dialog is now established, such
>     that INFOs can be send in the reverse direction as well.
>
>
> It would be helpful to explain this as well. I defer to the ART ADs on 
> the suitability of this technique.
I'll do
>
>
>>         m=lines that they pertain to.  The correspondence can be made via the
>>         "a=mid:" attributes.
>>
>>     This whole section needs to be rewritten to make clear what's going on:
>>
>>          candidates are grouped in sections headed by "pseudo" m=lines
>>          These sections contain a=mid values which point back to the true m=line.
>     Would it be sufficient to rephrase as follows?
>
>     Note, that there is no requirement that the Info request body
>         contains as many pseudo m= lines as the Offer/Answer contains m=
>         lines, nor that the pseudo m= lines be in the same order as the
>         m=lines that they pertain to.  The correspondence can be made via the
>         "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
>          These sections contain a=mid: attribute values which point back to the true m=line.
>
>
> Sure.
Thanks
Thomas


--------------3933EC3950E44741452B3EE2
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><tt>EKR,</tt><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2018-04-05 15:57, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Tue, Apr 3, 2018 at 11:46 AM,
            Thomas Stach <span dir="ltr">&lt;<a
                href="mailto:thomass.stach@gmail.com" target="_blank"
                moz-do-not-send="true">thomass.stach@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF">
                <p>EKR,</p>
                <p>thanks for your comments, responses inline<br>
                </p>
                <span class="gmail-"> <br>
                  <div
                    class="gmail-m_-3709797337778756038moz-cite-prefix">On
                    2018-04-03 00:54, Eric Rescorla wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <pre>Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss

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


Please refer to <a class="gmail-m_-3709797337778756038moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html" target="_blank" moz-do-not-send="true">https://www.ietf.org/iesg/<wbr>statement/discuss-criteria.<wbr>html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="gmail-m_-3709797337778756038moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/" target="_blank" moz-do-not-send="true">https://datatracker.ietf.org/<wbr>doc/draft-ietf-mmusic-trickle-<wbr>ice-sip/</a>



------------------------------<wbr>------------------------------<wbr>----------
DISCUSS:
------------------------------<wbr>------------------------------<wbr>----------

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?</pre>
                  </blockquote>
                </span> I'm not sure what the issues is here.<br>
                The cited text addresses the first of two cases, i.e.
                the case  where the INFO requests repeats <br>
                 the exact same set of candidates that was already
                provided in the initial offer. <br>
                This could happen when <br>
                a) Half Trickle is used (all candidate were already in
                the initial offer) or<br>
                b) Full Trickle is used where  the offerer is currently
                gathering additional candidates, but did not yet get
                them.<br>
                <br>
                The second case (Full Trickle with additional candidates
                already available) is addressed in the subsequent
                paragraph.<br>
                .. and yes the candidates are sent in the order as they
                were gathered.<span class="gmail-"><br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>Right. I'm saying you need to say that.</div>
          </div>
        </div>
      </div>
    </blockquote>
    OK, will do<br>
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF"><span class="gmail-">
                  <blockquote type="cite">
                    <pre>   'application/trickle-ice-<wbr>sdpfrag' bodies do not interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.</pre>
                  </blockquote>
                </span> 5888 is cited as it defines the a=mid: attribute
                that we used for identifying the m-line to which a
                candidate belongs.<br>
                The a=mid: attribute helps in case of multiple m-lines,
                when we already have gathered candidates <br>
                for e.g. the first and fourth m-line, but not for the
                2nd and 3rd. <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Right. You need to describe what a pseudo-m= line is
              because it's not defined anywhere.</div>
          </div>
        </div>
      </div>
    </blockquote>
    Well, we have this text in section 4.4 at the first occurrence of
    the term.<br>
    <br>
    <pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">   "... this is handled through the use of pseudo "m=" lines 
   and identification tags in "a=mid:" attributes as defined in
   [<a href="https://tools.ietf.org/html/rfc5888" title="&quot;The Session Description Protocol (SDP) Grouping Framework&quot;">RFC5888</a>].  Pseudo "m=" lines follow the SDP syntax for "m=" lines as
   defined in [<a href="https://tools.ietf.org/html/rfc4566" title="&quot;SDP: Session Description Protocol&quot;">RFC4566</a>], but provide no semantics other than indicating
   to which "m=" line a candidate belongs. "
</pre>
    <br>
    Isn't that good enough?<br>
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF"><span class="gmail-">
                  <blockquote type="cite">
                    <pre>   sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.</pre>
                  </blockquote>
                  <br>
                </span> Do you mean section 7  which talks about
                reordering candidate _pairs_ at the IE agents?<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>No. Section 16, sorry for the typo.</div>
          </div>
        </div>
      </div>
    </blockquote>
    Section 15? :-)<br>
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>   To achieve this, when trickling candidates, agents
              MUST respect the<br>
                 order in which the components and streams appear
              (implicitly or<br>
                 explicitly) as they have been negotiated by means of
              the relevant<br>
                 candidate information.  Therefore candidates for a
              given component<br>
                 MUST NOT be conveyed prior to candidates for a
              component with a lower<br>
                 ID number within the same foundation.  In addition,
              candidates MUST<br>
                 be paired, following the procedures in Section 8.1.1,
              in the same<br>
                 order they are conveyed.<br>
              <br>
            </div>
            <div><br>
            </div>
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF"> We  require that the ordering of
                the _candidates_ MUST not change  <br>
                when the candidates are sent several times from one  ICE
                agent to its peer in subsequent INFO requests.<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>The problem is the text "same order they were gathered"
              because the ICE trickle text</div>
            <div>requires sending them in an order different from when
              they were gathered.</div>
          </div>
        </div>
      </div>
    </blockquote>
    OK, now I see. I will clarify and refer to section 15 of
    draft-ice-trickle<br>
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF"> I don't see a conflict.<span
                  class="gmail-"><br>
                  <blockquote type="cite">
                    <pre>------------------------------<wbr>------------------------------<wbr>----------
COMMENT:
------------------------------<wbr>------------------------------<wbr>----------

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that's not true.

   include in each "m="-line a "a=mid:" attribute in accordance to
   [RFC5888].

Why is this required?</pre>
                  </blockquote>
                </span> As above, the a=mid: attribute helps in case of
                multiple m-lines, when we already have gathered
                candidates <br>
                for e.g. the first and fourth m-line, but not for the
                2nd and 3rd. </div>
            </blockquote>
            <div><br>
            </div>
            <div>Right. You need to actually explain this.</div>
          </div>
        </div>
      </div>
    </blockquote>
    I'll do<br>
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF"><span class="gmail-">
                  <blockquote type="cite">
                    <pre>   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it's an implicit ACK of your INFO?</pre>
                  </blockquote>
                </span> The INFO is an ACK that an early dialog is now
                established, such that INFOs can be send in the reverse
                direction as well.<span class="gmail-"><br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>It would be helpful to explain this as well. I defer to
              the ART ADs on the suitability of this technique.</div>
          </div>
        </div>
      </div>
    </blockquote>
    I'll do
    <blockquote type="cite"
cite="mid:CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div> <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div bgcolor="#FFFFFF"><span class="gmail-">
                  <blockquote type="cite">
                    <pre>   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes.

This whole section needs to be rewritten to make clear what's going on:

    candidates are grouped in sections headed by "pseudo" m=lines
    These sections contain a=mid values which point back to the true m=line.
</pre>
                  </blockquote>
                </span> Would it be sufficient to rephrase as follows?<br>
                <pre class="gmail-m_-3709797337778756038newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Note, that there is no requirement that the Info request body
   contains as many pseudo m= lines as the Offer/Answer contains m=
   lines, nor that the pseudo m= lines be in the same order as the
   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
    These sections contain a=mid: attribute values which point back to the true m=line.</pre>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Sure.</div>
          </div>
        </div>
      </div>
    </blockquote>
    Thanks <br>
    Thomas<br>
    <br>
  </body>
</html>

--------------3933EC3950E44741452B3EE2--


From nobody Thu Apr  5 13:28:11 2018
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 A758D12D779 for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 13:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 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, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Td7swJxwCeL6 for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 13:28:03 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 97F1112D77D for <mmusic@ietf.org>; Thu,  5 Apr 2018 13:27:59 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id 126-v6so23620706oig.0 for <mmusic@ietf.org>; Thu, 05 Apr 2018 13:27: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=tzOp/Hq+tFptiJse4uuc+ioESjrDOdDbBCPCf+n+qxQ=; b=H9zQGYqtWL5tOJV37B+zZGpI8Sy8GnQuvdlvVd/CBuQ1NrtT23Ujzupi4qISDL3tYe gKJV2I7ftr6JamcISKl8ppO5kH7cS2aAY0WrA6UAfBUKQ+9a+6vFFu2gq3y5PwDADD9D EFdLrk4fcVLu8VYwJAf+LndaejwCqCUi/eK1WkC2Nn9z+7DPg/sVvHnNDT7fzdz575J+ gF0WSiT+anGv+ERYOj6yJ7KuAlws/6fe2QW6wDkb+rT0Wr231yqBL0EdmLkTPTEnOwrM 2EIQ3DQR+PlPghbdHUziYcQ1/eOVOoSQuY1ct2eOFBwCy8e8xqgFv3QGUg9sTUZrJCxH rtJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tzOp/Hq+tFptiJse4uuc+ioESjrDOdDbBCPCf+n+qxQ=; b=H7CkV0bGN9o9s0U6DT6TOLxdzm5KxCxjNvWE7h158lNyLRaJih7fRKtp/K1tePJsXr gvz3hhpBGBYWWKoLSiLXrtr6fQFVPtrrecDbDDEapiuPEd0xuEHDC/PqMCVcokLOaITV 2cK4ivBaSoB9i2skM1UqsZZUtd9WdpwQ1a9Luj08towNb710ZkUFUi6Zk1YIhKIpui19 4QWlnRwBuC3svWb7dt9yj0dnZSWG2hmX4SHW8e/vc/JK1EVFmxUl0DcHnQoCcA1wCKuL DtrbCJpkdHEAxGeng1f+Iyh583g8jY9xN1KEAoZktCy5BFCgm9e6QrW7+/DIESFCPqXS 5o/g==
X-Gm-Message-State: ALQs6tBaqab6P6Avj/nLNhmFRz/I1RuSdChQGvUTClYYYUfL+GGCpsrw /KQfvuxtw+YPwQWSh5MPJcaXfYWaU0+3Hsc8tj0O1g==
X-Google-Smtp-Source: AIpwx4+2ZNumvWDkLOxWCDBjksL8HouSQsUW9rqsSHvnCymQWi6Mis9qXfhnDxfYrg36M06KWFQ18260H81/Z/v5NLo=
X-Received: by 2002:aca:3114:: with SMTP id x20-v6mr14123079oix.108.1522960078894;  Thu, 05 Apr 2018 13:27:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.130 with HTTP; Thu, 5 Apr 2018 13:27:18 -0700 (PDT)
In-Reply-To: <587c07b6-c086-c429-761a-ca655372f32e@gmail.com>
References: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com> <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com> <CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com> <587c07b6-c086-c429-761a-ca655372f32e@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 5 Apr 2018 13:27:18 -0700
Message-ID: <CABcZeBO6FY58=_B64G7g3tA+niWP1sGsY6r09=2DKMp8j40mDQ@mail.gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org,  mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000828bd505691fc657"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/13g9Sc8PXgj2u-qZ87yLNG8K3Sw>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 20:28:06 -0000

--000000000000828bd505691fc657
Content-Type: text/plain; charset="UTF-8"

On Thu, Apr 5, 2018 at 1:10 PM, Thomas Stach <thomass.stach@gmail.com>
wrote:

> EKR,
>
> On 2018-04-05 15:57, Eric Rescorla wrote:
>
>
>
> On Tue, Apr 3, 2018 at 11:46 AM, Thomas Stach <thomass.stach@gmail.com>
> wrote:
>
>> EKR,
>>
>> thanks for your comments, responses inline
>>
>> On 2018-04-03 00:54, Eric Rescorla wrote:
>>
>> Eric Rescorla has entered the following ballot position for
>> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>>    the Offer (as would be the case when Half Trickle is performed or
>>    when new candidates have not been learned since then).
>> IMPORTANT: They must be in order, right?
>>
>> I'm not sure what the issues is here.
>> The cited text addresses the first of two cases, i.e. the case  where the
>> INFO requests repeats
>>  the exact same set of candidates that was already provided in the
>> initial offer.
>> This could happen when
>> a) Half Trickle is used (all candidate were already in the initial offer)
>> or
>> b) Full Trickle is used where  the offerer is currently gathering
>> additional candidates, but did not yet get them.
>>
>> The second case (Full Trickle with additional candidates already
>> available) is addressed in the subsequent paragraph.
>> .. and yes the candidates are sent in the order as they were gathered.
>>
>
> Right. I'm saying you need to say that.
>
> OK, will do
>
>
>
>    'application/trickle-ice-sdpfrag' bodies do not interfere with the
>>    Offer/Answer procedures as specified in [RFC3264].
>> IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.
>>
>> 5888 is cited as it defines the a=mid: attribute that we used for
>> identifying the m-line to which a candidate belongs.
>> The a=mid: attribute helps in case of multiple m-lines, when we already
>> have gathered candidates
>> for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>>
>
> Right. You need to describe what a pseudo-m= line is because it's not
> defined anywhere.
>
> Well, we have this text in section 4.4 at the first occurrence of the term.
>
>    "... this is handled through the use of pseudo "m=" lines
>    and identification tags in "a=mid:" attributes as defined in
>    [RFC5888 <https://tools.ietf.org/html/rfc5888>].  Pseudo "m=" lines follow the SDP syntax for "m=" lines as
>    defined in [RFC4566 <https://tools.ietf.org/html/rfc4566>], but provide no semantics other than indicating
>    to which "m=" line a candidate belongs. "
>
>
> Isn't that good enough?
>

Not really. The way it reads is that pseudo m= lines are defines in 5888
but they're not. This is the
normative source of them. I would rephrase
"use of pseudo "m=" lines, which follow the SDP syntax of..." and then talk
about mid in the next
sentence.

-Ekr

   sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
>    the same order as they were gathered.  In other words, the sequence
>    of a previously sent list of candidates MUST NOT change in subsequent
>
> IMPORTANT: This appears to conflict with the guidance in Section 6 of
> the trickle document, which is about reordering candidates from how
> they were gathered.
>
>
> Do you mean section 7  which talks about reordering candidate _pairs_ at
> the IE agents?
>

No. Section 16, sorry for the typo.

> Section 15? :-)
>
>
>    To achieve this, when trickling candidates, agents MUST respect the
>    order in which the components and streams appear (implicitly or
>    explicitly) as they have been negotiated by means of the relevant
>    candidate information.  Therefore candidates for a given component
>    MUST NOT be conveyed prior to candidates for a component with a lower
>    ID number within the same foundation.  In addition, candidates MUST
>    be paired, following the procedures in Section 8.1.1, in the same
>    order they are conveyed.
>
>
>
> We  require that the ordering of the _candidates_ MUST not change
>> when the candidates are sent several times from one  ICE agent to its
>> peer in subsequent INFO requests.
>>
>
> The problem is the text "same order they were gathered" because the ICE
> trickle text
> requires sending them in an order different from when they were gathered.
>
> OK, now I see. I will clarify and refer to section 15 of draft-ice-trickle
>
>
>
> I don't see a conflict.
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>>   SIP message.  At the remote agent the gathering procedure is repeated
>>    and candidates are sent to the first agent.  Finally, a third phase
>>    starts where connectivity between all candidates in both sets is
>>
>> This suggests that they have to happen in sequence, but that's not true.
>>
>>    include in each "m="-line a "a=mid:" attribute in accordance to
>>    [RFC5888].
>>
>> Why is this required?
>>
>> As above, the a=mid: attribute helps in case of multiple m-lines, when we
>> already have gathered candidates
>> for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>>
>
> Right. You need to actually explain this.
>
> I'll do
>
>
>
>    section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
>>    is not yet provided.
>>
>> Can you explain why you cease retransmitting on receiving INFO? I assume
>> because it's an implicit ACK of your INFO?
>>
>> The INFO is an ACK that an early dialog is now established, such that
>> INFOs can be send in the reverse direction as well.
>>
>
> It would be helpful to explain this as well. I defer to the ART ADs on the
> suitability of this technique.
>
> I'll do
>
>
>
>    m=lines that they pertain to.  The correspondence can be made via the
>>    "a=mid:" attributes.
>>
>> This whole section needs to be rewritten to make clear what's going on:
>>
>>     candidates are grouped in sections headed by "pseudo" m=lines
>>     These sections contain a=mid values which point back to the true m=line.
>>
>> Would it be sufficient to rephrase as follows?
>>
>> Note, that there is no requirement that the Info request body
>>    contains as many pseudo m= lines as the Offer/Answer contains m=
>>    lines, nor that the pseudo m= lines be in the same order as the
>>    m=lines that they pertain to.  The correspondence can be made via the
>>    "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
>>     These sections contain a=mid: attribute values which point back to the true m=line.
>>
>>
> Sure.
>
> Thanks
> Thomas
>
>

--000000000000828bd505691fc657
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, Apr 5, 2018 at 1:10 PM, Thomas Stach <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:thomass.stach@gmail.com" target=3D"_blank">thomass.stach@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p><tt>EKR,</tt><br>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_-7821002768604845176moz-cite-prefix">On 2018-04-05 15:5=
7, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Tue, Apr 3, 2018 at 11:46 AM,
            Thomas Stach <span dir=3D"ltr">&lt;<a href=3D"mailto:thomass.st=
ach@gmail.com" target=3D"_blank">thomass.stach@gmail.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">
              <div bgcolor=3D"#FFFFFF">
                <p>EKR,</p>
                <p>thanks for your comments, responses inline<br>
                </p>
                <span class=3D"m_-7821002768604845176gmail-"> <br>
                  <div class=3D"m_-7821002768604845176gmail-m_-370979733777=
8756038moz-cite-prefix">On
                    2018-04-03 00:54, Eric Rescorla wrote:<br>
                  </div>
                  <blockquote type=3D"cite">
                    <pre>Eric Rescorla has entered the following ballot pos=
ition for
draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss

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


Please refer to <a class=3D"m_-7821002768604845176gmail-m_-3709797337778756=
038moz-txt-link-freetext" href=3D"https://www.ietf.org/iesg/statement/discu=
ss-criteria.html" target=3D"_blank">https://www.ietf.org/iesg/stat<wbr>emen=
t/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class=3D"m_-7821002768604845176gmail-m_-3709797337778756038moz-txt-link-=
freetext" href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickl=
e-ice-sip/" target=3D"_blank">https://datatracker.ietf.org/d<wbr>oc/draft-i=
etf-mmusic-trickle-i<wbr>ce-sip/</a>



------------------------------<wbr>------------------------------<wbr>-----=
-----
DISCUSS:
------------------------------<wbr>------------------------------<wbr>-----=
-----

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?</pre>
                  </blockquote>
                </span> I&#39;m not sure what the issues is here.<br>
                The cited text addresses the first of two cases, i.e.
                the case=C2=A0 where the INFO requests repeats <br>
                =C2=A0the exact same set of candidates that was already
                provided in the initial offer. <br>
                This could happen when <br>
                a) Half Trickle is used (all candidate were already in
                the initial offer) or<br>
                b) Full Trickle is used where=C2=A0 the offerer is currentl=
y
                gathering additional candidates, but did not yet get
                them.<br>
                <br>
                The second case (Full Trickle with additional candidates
                already available) is addressed in the subsequent
                paragraph.<br>
                .. and yes the candidates are sent in the order as they
                were gathered.<span class=3D"m_-7821002768604845176gmail-">=
<br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>Right. I&#39;m saying you need to say that.</div>
          </div>
        </div>
      </div>
    </blockquote></div></div>
    OK, will do<span class=3D""><br>
    <blockquote type=3D"cite">
      <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-782100276860484517=
6gmail-">
                  <blockquote type=3D"cite">
                    <pre>   &#39;application/trickle-ice-sdpfr<wbr>ag&#39; =
bodies do not interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: &quot;pseudo&quot; m=3D lines are not defined in 5888 so this is=
 very unclear.</pre>
                  </blockquote>
                </span> 5888 is cited as it defines the a=3Dmid: attribute
                that we used for identifying the m-line to which a
                candidate belongs.<br>
                The a=3Dmid: attribute helps in case of multiple m-lines,
                when we already have gathered candidates <br>
                for e.g. the first and fourth m-line, but not for the
                2nd and 3rd. <br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Right. You need to describe what a pseudo-m=3D line is
              because it&#39;s not defined anywhere.</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Well, we have this text in section 4.4 at the first occurrence of
    the term.<br>
    <br>
    <pre class=3D"m_-7821002768604845176newpage" style=3D"font-size:13.3333=
px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;font=
-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-s=
pacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spa=
cing:0px;text-decoration-style:initial;text-decoration-color:initial">   &q=
uot;... this is handled through the use of pseudo &quot;m=3D&quot; lines=20
   and identification tags in &quot;a=3Dmid:&quot; attributes as defined in
   [<a href=3D"https://tools.ietf.org/html/rfc5888" title=3D"&quot;The Sess=
ion Description Protocol (SDP) Grouping Framework&quot;" target=3D"_blank">=
RFC5888</a>].  Pseudo &quot;m=3D&quot; lines follow the SDP syntax for &quo=
t;m=3D&quot; lines as
   defined in [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&qu=
ot;SDP: Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>],=
 but provide no semantics other than indicating
   to which &quot;m=3D&quot; line a candidate belongs. &quot;
</pre>
    <br>
    Isn&#39;t that good enough?<span class=3D""><br></span></div></blockquo=
te><div><br></div><div>Not really. The way it reads is that pseudo m=3D lin=
es are defines in 5888 but they&#39;re not. This is the</div><div class=3D"=
gmail_quote">normative source of them. I would rephrase <br></div><div clas=
s=3D"gmail_quote">&quot;use of pseudo &quot;m=3D&quot; lines, which follow =
the SDP syntax of...&quot; and then talk about mid in the next</div><div cl=
ass=3D"gmail_quote">sentence.</div><div class=3D"gmail_quote"><br></div><di=
v class=3D"gmail_quote">-Ekr<br></div><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 bgcolor=3D"#FFFFFF"><span class=3D"m_-782100276860484517=
6gmail-">
                  <blockquote type=3D"cite">
                    <pre>   sent under the same combination of &quot;a=3Dic=
e-pwd:&quot; and &quot;a=3Dice-ufrag:&quot; in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.</pre>
                  </blockquote>
                  <br>
                </span> Do you mean section 7=C2=A0 which talks about
                reordering candidate _pairs_ at the IE agents?<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>No. Section 16, sorry for the typo.</div>
          </div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolo=
r=3D"#FFFFFF"><span class=3D""><blockquote type=3D"cite"><div dir=3D"ltr"><=
div class=3D"gmail_extra">
        </div>
      </div>
    </blockquote></span>
    Section 15? :-)<span class=3D""><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <div><br>
            </div>
            <div>=C2=A0=C2=A0 To achieve this, when trickling candidates, a=
gents
              MUST respect the<br>
              =C2=A0=C2=A0 order in which the components and streams appear
              (implicitly or<br>
              =C2=A0=C2=A0 explicitly) as they have been negotiated by mean=
s of
              the relevant<br>
              =C2=A0=C2=A0 candidate information.=C2=A0 Therefore candidate=
s for a
              given component<br>
              =C2=A0=C2=A0 MUST NOT be conveyed prior to candidates for a
              component with a lower<br>
              =C2=A0=C2=A0 ID number within the same foundation.=C2=A0 In a=
ddition,
              candidates MUST<br>
              =C2=A0=C2=A0 be paired, following the procedures in Section 8=
.1.1,
              in the same<br>
              =C2=A0=C2=A0 order they are conveyed.<br>
              <br>
            </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">
              <div bgcolor=3D"#FFFFFF"> We=C2=A0 require that the ordering =
of
                the _candidates_ MUST not change=C2=A0 <br>
                when the candidates are sent several times from one=C2=A0 I=
CE
                agent to its peer in subsequent INFO requests.<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>The problem is the text &quot;same order they were gathere=
d&quot;
              because the ICE trickle text</div>
            <div>requires sending them in an order different from when
              they were gathered.</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    OK, now I see. I will clarify and refer to section 15 of
    draft-ice-trickle<span class=3D""><br>
    <blockquote type=3D"cite">
      <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 bgcolor=3D"#FFFFFF"> I don&#39;t see a conflict.<span cl=
ass=3D"m_-7821002768604845176gmail-"><br>
                  <blockquote type=3D"cite">
                    <pre>------------------------------<wbr>---------------=
---------------<wbr>----------
COMMENT:
------------------------------<wbr>------------------------------<wbr>-----=
-----

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that&#39;s not true=
.

   include in each &quot;m=3D&quot;-line a &quot;a=3Dmid:&quot; attribute i=
n accordance to
   [RFC5888].

Why is this required?</pre>
                  </blockquote>
                </span> As above, the a=3Dmid: attribute helps in case of
                multiple m-lines, when we already have gathered
                candidates <br>
                for e.g. the first and fourth m-line, but not for the
                2nd and 3rd. </div>
            </blockquote>
            <div><br>
            </div>
            <div>Right. You need to actually explain this.</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    I&#39;ll do<span class=3D""><br>
    <blockquote type=3D"cite">
      <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-782100276860484517=
6gmail-">
                  <blockquote type=3D"cite">
                    <pre>   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] =
except that an Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it&#39;s an implicit ACK of your INFO?</pre>
                  </blockquote>
                </span> The INFO is an ACK that an early dialog is now
                established, such that INFOs can be send in the reverse
                direction as well.<span class=3D"m_-7821002768604845176gmai=
l-"><br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>It would be helpful to explain this as well. I defer to
              the ART ADs on the suitability of this technique.</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    I&#39;ll do
    <span class=3D""><blockquote type=3D"cite">
      <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-782100276860484517=
6gmail-">
                  <blockquote type=3D"cite">
                    <pre>   m=3Dlines that they pertain to.  The correspond=
ence can be made via the
   &quot;a=3Dmid:&quot; attributes.

This whole section needs to be rewritten to make clear what&#39;s going on:

    candidates are grouped in sections headed by &quot;pseudo&quot; m=3Dlin=
es
    These sections contain a=3Dmid values which point back to the true m=3D=
line.
</pre>
                  </blockquote>
                </span> Would it be sufficient to rephrase as follows?<br>
                <pre class=3D"m_-7821002768604845176gmail-m_-37097973377787=
56038newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px=
;color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-vari=
ant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:init=
ial;text-decoration-color:initial">Note, that there is no requirement that =
the Info request body
   contains as many pseudo m=3D lines as the Offer/Answer contains m=3D
   lines, nor that the pseudo m=3D lines be in the same order as the
   m=3Dlines that they pertain to.  The correspondence can be made via the
   &quot;a=3Dmid:&quot; attributes since candidates are grouped in sections=
 headed by &quot;pseudo&quot; m=3Dlines.
    These sections contain a=3Dmid: attribute values which point back to th=
e true m=3Dline.</pre>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Sure.</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Thanks <br><span class=3D"HOEnZb"><font color=3D"#888888">
    Thomas<br>
    <br>
  </font></span></div>

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

--000000000000828bd505691fc657--


From nobody Thu Apr  5 14:17:09 2018
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 4B12712D7F6 for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 14:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 Dz-fMshSiGdP for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 14:17:05 -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 1282412D7EC for <mmusic@ietf.org>; Thu,  5 Apr 2018 14:17:04 -0700 (PDT)
X-AuditID: 12074413-b6bff70000006608-cb-5ac6925071da
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id 50.DC.26120.05296CA5; Thu,  5 Apr 2018 17:17:04 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w35LH338015357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 5 Apr 2018 17:17:04 -0400
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu>
Date: Thu, 5 Apr 2018 17:17:03 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGIsWRmVeSWpSXmKPExsUixO6iqBsw6ViUwdrpkhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxoo5p5gKJolUfN16grmB8S5/FyMnh4SAiURf6wfmLkYuDiGB HUwSezrXsYIkhAS+MUnMWaYPYosIqEj8e/eADcRmE9CSmHPoPwuILSzgKrF22yFGEJtXwF7i 2sluMJsFqH7W4bNgNaICaRL3N0+CqhGUODnzCVicWcBMYt7mh8wQtrjErSfzmSBseYntb+cw T2DknYWkZRaSlllIWmYhaVnAyLKKUS4xpzRXNzcxM6c4NVm3ODkxLy+1SNdcLzezRC81pXQT IyTIhHcw7jopd4hRgINRiYdXIOxYlBBrYllxZe4hRkkOJiVR3i26QCG+pPyUyozE4oz4otKc 1OJDjBIczEoivM4g5bwpiZVVqUX5MClpDhYlcV5mk71RQgLpiSWp2ampBalFMFkZDg4lCd6i iUCNgkWp6akVaZk5JQhpJg5OkOE8QMM3gdTwFhck5hZnpkPkTzHqckx53t/DLMSSl5+XKiXO awlSJABSlFGaBzcHlhxeMYoDvSXM2wdSxQNMLHCTXgEtYQJaMiHxCMiSkkSElFQD445tvIbz 1eIecy1c/NhcRU97e++zuv6rIZfNb1gGsya6OyyrzfzCIBUaMeux68unlQ/DXn8u43ruwJKy y4VzSjz32lB3YZs8JY70E43yi+s2XX5761p95FrGUqbzr+aYSj9+056hoS060+X/ctY5ed8W 8J6++kI1uSsxIFfFrfSPlNWriiRXJZbijERDLeai4kQAP3IIwekCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9HiXMVFBpxEuQKsp8b6Lh913HUY>
Subject: [MMUSIC] INPUT NEEDED: Edits to 4566bis based on discussion in London
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 05 Apr 2018 21:17:07 -0000

I'm working on making the changes to 4566bis that were called for based 
on the discussion in London. After reviewing all of that I have some 
questions for which I need feedback from the wg.

* Open Issue 3 - Regarding section 5.11 (z=):

After reviewing the text for t=, r=, z=, the meaning of z= seems pretty 
clear to me. The text for z= only talks about how it works with r=. In 
principle, if the adjustment time precedes the start time from t= then I 
suppose it *might* also apply there, and perhaps to stop time as well.

 From the text and examples it is clear that this isn't usable for 
anything else. E.g., it does *not* provide an adjustment that yields 
local time.

I could reword to say that it does *not* apply to the start/stop times 
in t=, or that it definitely only applies to r=. Thoughts?

* Open Issue 7 - Regarding section 8.2.2 ("proto"):

The minutes (regarding udptl) say:

"Action: will grandfather T.38 and keep the text as is. Also change to 
currently defined registration procedure."

What was meant here? The registration procedure says RFC Required. 
Changing to conform to that is different from grandfathering T.38.

ISTM that all is well as it is.

* Open Issue 8 - Regarding section 8.2.3 ("fmt"):

The text implies that the namespace for udp formats consists of mime 
types. It says:

    ... If no media
    subtype exists, it is RECOMMENDED that a suitable one be registered
    through the IETF process [RFC6838] by production of, or reference to,
    a standards-track RFC that defines the transport protocol for the
    format.

But IIUC rfc6838 makes no provision for defining a *transport protocol* 
for a mime type.

I'm not even entirely sure what rfc4566 intended here. Was it that the 
content of each UDP packet is to conform to the definition of the mime 
type? What about ordering rules that impose requirements on sequences of 
packets?

Is it intended that the media types suitable for use as udp formats are 
only those that have something special in their definitions? Or may any 
mime type be used if it can fit in a UDP packet?

* Open Issue 9 - Regarding section 8.2.5 ("bwtype"):

The notes say:

"Check the current IANA registry, did they change the registry and 
update accordingly."

The registry does now have the mux category, and the entries for CT and 
AS reference both 4566 and mux-attributes.

AFAICT the only thing to do is update these two registry entries to 
reference this bis rather than 4566. Did I miss anything?

	Thanks,
	Paul


From nobody Thu Apr  5 23:52:15 2018
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 6408212DA3F for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 23:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEyo0T98vzbz for <mmusic@ietfa.amsl.com>; Thu,  5 Apr 2018 23:52:09 -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 9394C12E896 for <mmusic@ietf.org>; Thu,  5 Apr 2018 23:52:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1522997525; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=P61l/NWU4YFFEToM1EdG0Ilopf+xNa7McxqP2oMINzU=; b=QLb/ZgVwGKIShuOAdo/OYUvsyn7aRcQvmBGSPe6wz7L8qUAA7mfRaG1yVFLnBkE2 ukeST5sloIeNN5LfeTnmAWiV0ZSK3gXiGmQzL+lkCIEH/3eCITisWizD/Qj38/o1 gRPQuHlC9NRB8OmWbGPhr/apppUdTxrRKFkqIqDNbnY=;
X-AuditID: c1b4fb25-5a75a9c00000522b-d6-5ac71914e1ee
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 0B.3C.21035.41917CA5; Fri,  6 Apr 2018 08:52:05 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0382.000; Fri, 6 Apr 2018 08:52:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, Adam Roach <adam@nostrum.com>, "The IESG" <iesg@ietf.org>
CC: "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTyx2P005KrT20W0WCmZj7phUtbaPw2hYAgAAISgCAAOwY8IAAqdSAgADYXTA=
Date: Fri, 6 Apr 2018 06:52:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E4B248@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <fb4e77e6-3fe0-f983-1491-3f6de101e36f@gmail.com> <75d8a114-8957-2bbd-a36b-d9f6cc83d5ee@nostrum.com> <7594FB04B1934943A5C02806D1A2204B72E48374@ESESSMB109.ericsson.se> <6860212c-f34b-faed-a391-f8fcf519437c@gmail.com>
In-Reply-To: <6860212c-f34b-faed-a391-f8fcf519437c@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.171]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM2K7t66o5PEogwnfmC32/F3EbvFj7XJm i/cXdC1m/JnIbHF+53omi6nLH7NYfDqxlcmB3WPK742sHjtn3WX3WLLkJ5PHrJ1PWAJYorhs UlJzMstSi/TtErgyLm++ylzQxVLx/sJ5lgbGP8xdjJwcEgImEl/fLWPpYuTiEBI4wigx48Bh ZghnMaPE4Tk3GLsYOTjYBCwkuv9pg5giAukSe3fYgZQwCzxjlHhy/zcryCBhoPjmm1PAbBGB DIlzbVNZIGw/iV9H97CB2CwCKhI7PsxnBLF5BXwllre+gFq8hklix8mrYAlOAVuJ28/7wK5j FBCT+H5qDROIzSwgLnHryXwmiKsFJJbsOQ/1gajEy8f/WCFsJYkTDxuZQQ5lFtCUWL9LH6JV UWJK90N2iL2CEidnPmGZwCg6C8nUWQgds5B0zELSsYCRZRWjaHFqcVJuupGxXmpRZnJxcX6e Xl5qySZGYKQd3PJbdQfj5TeOhxgFOBiVeHhnih6PEmJNLCuuzD3EKMHBrCTCu/vPsSgh3pTE yqrUovz4otKc1OJDjNIcLErivA/NN0cJCaQnlqRmp6YWpBbBZJk4OKUaGKPFdi6XyknmV54d VW15e+G240aV+7p2Zl/NnZ4Xd6JNb+b+tPU7hRc8FKm7eupcqKr2hVnnz4nPfvNMb1MQQxeD 3SnR+bbn1rJmWkubpxlbflm/p0h00YZ9nQmhFgqTzacfP7SxZ7PyltUKv/z5AqeEL7xo7pEs 2KCjGSz9V3JpVp3mjNsMJkosxRmJhlrMRcWJAP1Wp5GwAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/y778blX2gTva3a3SHJ20lz_VPv8>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 06 Apr 2018 06:52:10 -0000

SGksDQoNCi4uLg0KDQo+PiBJIHN1Z2dlc3QgIm9uIHJlY2VpcHQgb2YgYW4gSU5GTyByZXF1ZXN0
IGFzc29jaWF0ZWQgd2l0aCB0aGUgJ3RyaWNrbGUtaWNlJyBJbmZvIFBhY2thZ2UiLg0KPiBJJ2Qg
cHJlZmVyIG5vdCB0byBvdmVyLXVzZSB0aGUgdmVyYiAiYXNzb2NpYXRlIg0KDQpZb3UgY2FuIHVz
ZSBhbm90aGVyIHdvcmQgaWYgeW91IHdhbnQsIGJ1dCBteSBwb2ludCBpcyB0aGF0IHlvdSByZWNl
aXZlIGFuIElORk8gcmVxdWVzdCBhc3NvY2lhdGVkIHdpdGggdGhlICd0cmlja2xlLWljZScgSW5m
byBQYWNrYWdlIC0gd2hldGhlciB0aGUgSU5GTyBjb250YWlucyBhIGJvZHkgb3Igbm90IGlzIGly
cmVsZXZhbnQuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Fri Apr  6 02:48:09 2018
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 197EC1241F5 for <mmusic@ietfa.amsl.com>; Fri,  6 Apr 2018 02:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8GrCDmRhG_ry for <mmusic@ietfa.amsl.com>; Fri,  6 Apr 2018 02:48: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 5BE931241F3 for <mmusic@ietf.org>; Fri,  6 Apr 2018 02:48:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523008082; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=7VOQ85M4u6u0uvPpdpEyrwQsLDaDMvxtN1VtPRHrrfI=; b=APctFiKDi0/JuYLvikmHEPXHz60SZLVd43pci2IkLYl8d3TA7OzpfRvQi3knm0jE 88QjHnBeCiA6bEm7f4TQ6N/j0FzpQOt523KzhWwc+Rt9Pl+/nmi0oH9UVo+knBwj hp68gMB96q3tjlZPRkcggRyPqupBx2+nqXhDuBud3nQ=;
X-AuditID: c1b4fb3a-e39ff70000005d56-ce-5ac74252ff05
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id E8.25.23894.25247CA5; Fri,  6 Apr 2018 11:48:02 +0200 (CEST)
Received: from [147.214.162.192] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.75) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 6 Apr 2018 11:48:01 +0200
References: <deb45e70-d5a8-e75e-225d-a3e8375d91f0@ericsson.com>
To: IETF MMUSIC WG <mmusic@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Forwarded-Message-Id: <deb45e70-d5a8-e75e-225d-a3e8375d91f0@ericsson.com>
Message-ID: <b769eae8-3c59-9fac-43cb-bb87fe9980c8@ericsson.com>
Date: Fri, 6 Apr 2018 11:48:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <deb45e70-d5a8-e75e-225d-a3e8375d91f0@ericsson.com>
Content-Type: multipart/alternative; boundary="------------FE7D32CBB4DC987CC5DFAD96"
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBLMWRmVeSWpSXmKPExsUyM2K7t26Q0/EogyNztCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujIbOX2wFz/8zVrQeX8bUwDj5GGMXIyeHhICJxLE/t9m7GLk4 hASOMEpM3LaWBSQhJLCZUWLJAxkQW1jAVWLv979MEHF7iUMvD4HZIgIqEv/ePWADsdkELCRu /mhkgxjqLfGh6zlYDS9Q/Z5VK5hBbBag+pOPp4DNFxWIkfhxtIsFokZQ4uTMJ2A2p4CDxJY1 t8DmMAuESfxedIUZwhaXaPqykhXiBm2JhqYOVohdShLX511nmcAoOAvJqFlI2mchaYewLSRm zj/PCGHLSzRvnQ1VoyHROmcuO7L4Akb2VYyixanFxbnpRkZ6qUWZycXF+Xl6eaklmxiB4X9w y2+rHYwHnzseYhTgYFTi4Z2lfjxKiDWxrLgy9xCjBAezkgjv7j/HooR4UxIrq1KL8uOLSnNS iw8xSnOwKInzOqVZRAkJpCeWpGanphakFsFkmTg4pRoYfY3MvpRuNbB4oMxlcCp07f/5U11v uhcKxD3sWfx6T8HWx3M3v895mNq0Y1n28V9T+pmWpBXc2HeRc/eE7U6eeZUe51Nv1yeIX9F5 cneJX275ac1iu+nKuzT5GKsml3YdfJy8PrftCFPkxrNLXJPid6+XMOnJe2e111B0gpmwbP7y duniFWz7lViKMxINtZiLihMB+C8e2HsCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/YS8cR3K2rIfxDia5vMeVaiRvxkc>
Subject: [MMUSIC] Fwd: Re: AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 06 Apr 2018 09:48:08 -0000

--------------FE7D32CBB4DC987CC5DFAD96
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

WG,

We authors have received Ben's AD review comments. Here are our response 
to them. Note this email includes proposed changes to the draft.

/Magnus Westerlund



-------- Vidarebefordrat meddelande --------
Ämne: 	Re: AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11
Datum: 	Fri, 6 Apr 2018 11:43:10 +0200
Från: 	Magnus Westerlund <magnus.westerlund@ericsson.com>
Till: 	Ben Campbell <ben@nostrum.com>, 
draft-ietf-mmusic-sdp-simulcast.all@ietf.org



Hi  Ben,

We have now reviewed your comments in detail and done edits to resolve 
them. We have a version ready to be submitted, but I am holding it until 
you have had a chance to see our proposed edits.

See inline for comments and suggestions.


Den 2018-03-30 kl. 05:44, skrev Ben Campbell:
> Hi,
>
> This is my AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11.Thanks for all the work on this; overall it’s in good shape. I do, however, have some comments. I’d like to address my substantive comments and significatn editorial comments prior to IETF LC.
>
> Thanks!
>
> Ben.
>
> ---------------------------------
>
> Substantive:
>
> §5.2, paragraph 12:
>
> — " RTP duplication [RFC7104 ] procedures SHOULD be considered instead of simulcast”
>
> “considered” seems weak for a normative statement. Should this say “SHOULD use”?

Yes, I think that is what is intended. But, I suggest that we change 
this to:

...required, it is RECOMMENDED to use RTP duplication [RFC7104] procedures instead of simulcast"



> — " Note that this does not eliminate use of simulcast as an RTP duplication mechanism, since it is possible to define multiple different rid-id that are effectively equivalent.”
>
> Didn’t the first part of the paragraph say (or at least imply) that you SHOULD NOT do that?

Well, we recommend that one uses duplication if that is the user's only intention. However, the sentence in between forbids one to re-use the same RID ID twice to indicate duplication. It is in that context that we note that duplication could be achieved despite that restriction by defining multiple RID ID with the same semantic definition.

And if one actually likes to have duplication and some variant then I think it may actually be reasonable to use simulcast for both, rather than requiring an additional mechanism. So, I have a preference for leaving it there.


> §7: Is there anything to say about congestion? (I don’t know that there is; I just want to make sure people thought about it.)

Maybe the adaptation section is to assuming. We do assume that there 
will be congestion control or circuit breakers in place and that the 
sender will adapt the total bitrate of the stream to the available 
capacity. Maybe we should clarify that in the beginning of section 7.1. 
We also realized that maybe we should clarify that the combined 
bandwidth is bounded by the b= attribute applicable on the media stream 
level.

Maybe something like this:

    Use of multiple simulcast streams can require a significant amount of
    network resources.  The aggregate bandwidth for all simulcast streams
    for a media source (and thus SDP media description) is bounded by any
    SDP "b=" line applicable to that media source.  It is assumed that a
    suitable congestion control mechanism is used by the application to
    ensure that it doesn't cause persistent congestion.  If the amount of
    available network resources varies during an RTP session such that it
    does not match what is negotiated in SDP, the bitrate used by the
    different simulcast streams may have to be reduced dynamically.  When
    a simulcasting media source uses a single media transport for all of
    the simulcast streams, it is likely that a joint congestion control
    across all simulcast streams is used for that media source.


> §9: Is there any reason not to make the registration contact “The IESG  (iesg@ietf.org)” ?

No.

> Appendix A: Are the requirements met by this document? If so, is there value to the reader to keep the requirements in the document?

Yes, I think they are met. And Yes, I think there is a point of 
maintaining the requirements to show what space it solves.

I suggest to change the intro sentence to say:

The following requirements are met by the defined solution to support 
the use cases (Section 3):



> Significant Editorial:
>
> §2.2: Please use the boilerplate from RFC 8174—there are  at least several lower case “should”s in the document.

Agree.

> §3, 2nd bullet: “…  and does not require RTP Mixer (full) access to media content.”
>
> That’s a potentially strong advantage. Should there be a reciprocal “disadvantage” for the transcoding case?

Yes, but to actually deny the middlebox the access to the encoded 
content the system also needs to implement the PERC security solution. 
And it is mentioned at the end of the Transcoding case: The main 
disadvantages are ..., and requires RTP Mixer access to media content.

So I don't think there is need for a change here.

> §4, 4th paragraph: “ Each simulcast RTP stream identifier (rid-id) is separated by a semicolon (";").  When rid-ids are separated by a comma (","), they describe alternative representations for that particular simulcast RTP stream.”
>
> That text is confusing, it says instances of rid-id are separated by semicolons, then says “when separated by commas”. I think you mean that a semicolon separates rids for different streams, and a comma separates multiple rids for the same stream?

Agreed, propose to change this to:

Each simulcast stream is described by one or more RTP stream identifiers 
(rid-id), each group of rid-ids for a simulcast stream is separated by a 
semicolon (";"). When a simulcast stream has multiple rid-ids that are 
separated by a comma (","), they describe alternative representations 
for that particular simulcast RTP stream.



> §4, last paragraph: This paragraph seems like it belongs earlier in the section.

It is actually a summary of the section. To make this clearer, I suggest 
that we change the start of the paragraph to:

To summarize, the "a=simulcast" line ...

> §5.2:
> — First paragraph: "The meaning of the attribute on SDP session level is undefined, MUST NOT be used by implementations of this specification and MUST be ignored if received on session level.”
>
> Convoluted sentence. I suggest something to the effect of:
>
>     “The use of this attribute at the session level is undefined. Implementations of this specification MUST NOT use it at the session level and MUST ignore it if received at the session level.”

Thanks, good suggestion.
> — same paragraph: “ Extensions to this specification MAY define such session level usage.”
>
> That “MAY" seems more a statement of fact than permission. I suggest stating it without the normative keyword.

Agreed, implementing.

> — 6th paragraph: "In this case, it is not possible to align what alternative rid-id that are used across different simulcast streams, like requiring all simulcast streams to use rid-id alternatives referring to the same codec format.”
>
> I don’t understand the sentence.

The intention of the sentence is to make clear that there exists no
protocol mechanism to force the peer to choose the same alternative
in both simulcast streams in case there are multiple alternatives,
e.g. when both simulcast stream A and simulcast stream B have the
choice between HEVC and VP9, i.e. ensure that only HEVC or only VP9
is used for both simulcast streams. I propose to address this by
removing the sentence you didn't understand, and instead add a new
sentence last in the paragraph. Thus the whole paragraph reads:

Use of more than a single, alternative simulcast format for a
simulcast stream MAY be specified as part of the attribute parameters
by expressing the simulcast stream as a comma-separated list of
alternative rid-id. The order of the rid-id alternatives within a
simulcast stream is significant; the rid-id alternatives are listed
from (left) most preferred to (right) least preferred. For the use of
simulcast, this overrides the normal codec preference as expressed by
format type ordering on the "m=" line, using regular SDP rules. This
is to enable a separation of general codec preferences and simulcast
stream configuration preferences. However, the choice of which
alternative to use per simulcast stream is independent, and there is
currently no mechanism to align the choice of alternative rid-ids
between different simulcast streams.


Better?
> — 10th paragraph: The first sentence is hard to parse.

I agree that this sentence is hard:

Including an initially paused simulcast stream in "recv" direction for 
the part sending the SDP, sent towards an RTP sender, SHOULD cause the 
remote RTP sender to put the stream as unsolicited locally paused, 
unless there are other RTP stream receivers that do not mark the 
simulcast stream as initially paused.

Is this reworded sentence better?

If the endpoint sending the SDP includes an "recv" direction simulcast 
stream that is initially paused, then the remote RTP sender receiving 
the SDP SHOULD put its RTP stream in a unsolicited locally paused state. 
This unless there are there are other RTP stream receivers that do not 
mark the simulcast stream as initially paused.


> §5.3.2, paragraph 3: “The answerer MUST be prepared to receive any of the receive direction rid-id alternatives, and MAY send any of the send direction alternatives that are kept in the answer.”
>
> I think from reading further that you intend “that are kept in the answer” to restrict both the alternatives one must be ready to receive and may choose to send. But the comma before “and MAY” makes it seem like it only restricts the alternatives the answerer can choose to send.
>
An what the answer can sends is what is important. And the answer can 
actually add alternatives to what it can receive. Thus, "kept" is 
actually wrong. I suggest that we modify the sentence to read:

The answerer MUST be prepared to receive any of the receive direction 
rid-id alternatives and MAY send any of the send direction alternatives 
that are part of the answer.

Does that resolve the unclarity?


> Editorial and Nits:
>
> §1, last paragraph: Unclear antecedent for “it”.  (The document is motivated?)

This document describes a few scenarios that motivates the use of 
simulcast, and also defines the needed RTP/RTCP and SDP signaling for it.

> §3.1, Codec: “… (such as SDP MIME type) …”: Should that be SDP payload MIME type? (We aren’t talking about application/sdp, are we)

(such as RTP payload format MIME type)
> - Bitrate: s/amount/number

Ok


> §3.3: I want to say s/ “ preferences to “ / “ preferences for”, but that seems wrong with “apply preferences”. So now I think there’s something awkward about the phrase “apply preference to the characteristics”. Does this mean the same as “state preferences for the characteristics”?

Does this formulation resolve the issue?

The application logic that controls the communication session may
    allow receiving participants to state their preferences on the
    characteristics of the RTP stream they like to receive, for example
    in terms of the aspects listed in Section 3.1.


> §4, 5th paragraph (starting with “The RID mechanism, as defined…”: It would make things easier to understand if you moved this paragraph before most of the discussion that talks about rids.

Agreed, move it up to be the second paragraph.

> — 8th paragraph: "interpreted on a high level” s/on/at
Ok

> §5.2:
> — paragraph 9: Missing “the” before send. “part” seems like the wrong word choice, but I’m not sure what was intended, maybe “peer”? (Same for paragraph 10).

endpoint I think works.

> — Paragraph 10: Please expand “ TMMBR/TMMBN”

Done.
> §6.1, 2nd paragraph: s/“may not”/“might not"

Done.

>
>
>
>
>
>
>

-- 

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto:magnus.westerlund@ericsson.com
----------------------------------------------------------------------


--------------FE7D32CBB4DC987CC5DFAD96
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>WG,</p>
    <p>We authors have received Ben's AD review comments. Here are our
      response to them. Note this email includes proposed changes to the
      draft.</p>
    <p>/Magnus Westerlund<br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Vidarebefordrat meddelande --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Ämne: </th>
            <td>Re: AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Datum: </th>
            <td>Fri, 6 Apr 2018 11:43:10 +0200</td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Från: </th>
            <td>Magnus Westerlund <a class="moz-txt-link-rfc2396E" href="mailto:magnus.westerlund@ericsson.com">&lt;magnus.westerlund@ericsson.com&gt;</a></td>
          </tr>
          <tr>
            <th nowrap="nowrap" valign="BASELINE" align="RIGHT">Till: </th>
            <td>Ben Campbell <a class="moz-txt-link-rfc2396E" href="mailto:ben@nostrum.com">&lt;ben@nostrum.com&gt;</a>,
              <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-mmusic-sdp-simulcast.all@ietf.org">draft-ietf-mmusic-sdp-simulcast.all@ietf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <p>Hi  Ben,</p>
      <p>We have now reviewed your comments in detail and done edits to
        resolve them. We have a version ready to be submitted, but I am
        holding it until you have had a chance to see our proposed
        edits. </p>
      <p>See inline for comments and suggestions.<br>
      </p>
      <br>
      <div class="moz-cite-prefix">Den 2018-03-30 kl. 05:44, skrev Ben
        Campbell:<br>
      </div>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">Hi,

This is my AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11.Thanks for all the work on this; overall it’s in good shape. I do, however, have some comments. I’d like to address my substantive comments and significatn editorial comments prior to IETF LC.

Thanks!

Ben.

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

Substantive:

§5.2, paragraph 12:

— " RTP duplication [RFC7104 ] procedures SHOULD be considered instead of simulcast”

“considered” seems weak for a normative statement. Should this say “SHOULD use”?</pre>
      </blockquote>
      <br>
      Yes, I think that is what is intended. But, I suggest that we
      change this to: <br>
      <pre wrap="">...required, it is RECOMMENDED to use RTP duplication [RFC7104] procedures instead of simulcast"</pre>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">— " Note that this does not eliminate use of simulcast as an RTP duplication mechanism, since it is possible to define multiple different rid-id that are effectively equivalent.”

Didn’t the first part of the paragraph say (or at least imply) that you SHOULD NOT do that?</pre>
      </blockquote>
      <br>
      <pre wrap="">Well, we recommend that one uses duplication if that is the user's only intention. However, the sentence in between forbids one to re-use the same RID ID twice to indicate duplication. It is in that context that we note that duplication could be achieved despite that restriction by defining multiple RID ID with the same semantic definition.

And if one actually likes to have duplication and some variant then I think it may actually be reasonable to use simulcast for both, rather than requiring an additional mechanism. So, I have a preference for leaving it there.
</pre>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§7: Is there anything to say about congestion? (I don’t know that there is; I just want to make sure people thought about it.)</pre>
      </blockquote>
      <br>
      Maybe the adaptation section is to assuming. We do assume that
      there will be congestion control or circuit breakers in place and
      that the sender will adapt the total bitrate of the stream to the
      available capacity. Maybe we should clarify that in the beginning
      of section 7.1. We also realized that maybe we should clarify that
      the combined bandwidth is bounded by the b= attribute applicable
      on the media stream level.<br>
      <br>
      Maybe something like this:<br>
      <br>
         Use of multiple simulcast streams can require a significant
      amount of<br>
         network resources.  The aggregate bandwidth for all simulcast
      streams<br>
         for a media source (and thus SDP media description) is bounded
      by any<br>
         SDP "b=" line applicable to that media source.  It is assumed
      that a<br>
         suitable congestion control mechanism is used by the
      application to<br>
         ensure that it doesn't cause persistent congestion.  If the
      amount of<br>
         available network resources varies during an RTP session such
      that it<br>
         does not match what is negotiated in SDP, the bitrate used by
      the<br>
         different simulcast streams may have to be reduced
      dynamically.  When<br>
         a simulcasting media source uses a single media transport for
      all of<br>
         the simulcast streams, it is likely that a joint congestion
      control<br>
         across all simulcast streams is used for that media source.<br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§9: Is there any reason not to make the registration contact “The IESG  (<a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org" moz-do-not-send="true">iesg@ietf.org</a>)” ?</pre>
      </blockquote>
      <br>
      No. <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">Appendix A: Are the requirements met by this document? If so, is there value to the reader to keep the requirements in the document?</pre>
      </blockquote>
      <br>
      Yes, I think they are met. And Yes, I think there is a point of
      maintaining the requirements to show what space it solves. <br>
      <br>
      I suggest to change the intro sentence to say:<br>
      <br>
      The following requirements are met by the defined solution to
      support the use cases (Section 3):<br>
      <br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">
Significant Editorial:

§2.2: Please use the boilerplate from RFC 8174—there are  at least several lower case “should”s in the document.</pre>
      </blockquote>
      <br>
      Agree.<br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§3, 2nd bullet: “…  and does not require RTP Mixer (full) access to media content.”

That’s a potentially strong advantage. Should there be a reciprocal “disadvantage” for the transcoding case?</pre>
      </blockquote>
      <br>
      Yes, but to actually deny the middlebox the access to the encoded
      content the system also needs to implement the PERC security
      solution. And it is mentioned at the end of the Transcoding case:
      The main disadvantages are ..., and requires RTP Mixer access to
      media content.<br>
      <br>
      So I don't think there is need for a change here.  <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§4, 4th paragraph: “ Each simulcast RTP stream identifier (rid-id) is separated by a semicolon (";").  When rid-ids are separated by a comma (","), they describe alternative representations for that particular simulcast RTP stream.”

That text is confusing, it says instances of rid-id are separated by semicolons, then says “when separated by commas”. I think you mean that a semicolon separates rids for different streams, and a comma separates multiple rids for the same stream?</pre>
      </blockquote>
      <br>
      Agreed, propose to change this to:<br>
      <br>
      Each simulcast stream is described by one or more RTP stream
      identifiers (rid-id), each group of rid-ids for a simulcast stream
      is separated by a semicolon (";"). When a simulcast stream has
      multiple rid-ids that are separated by a comma (","), they
      describe alternative representations for that particular simulcast
      RTP stream.<br>
      <br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§4, last paragraph: This paragraph seems like it belongs earlier in the section.</pre>
      </blockquote>
      <br>
      It is actually a summary of the section. To make this clearer, I
      suggest that we change the start of the paragraph to:<br>
      <br>
      To summarize, the "a=simulcast" line ...<br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§5.2:
— First paragraph: "The meaning of the attribute on SDP session level is undefined, MUST NOT be used by implementations of this specification and MUST be ignored if received on session level.”

Convoluted sentence. I suggest something to the effect of:

   “The use of this attribute at the session level is undefined. Implementations of this specification MUST NOT use it at the session level and MUST ignore it if received at the session level.”</pre>
      </blockquote>
      <br>
      Thanks, good suggestion. <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">— same paragraph: “ Extensions to this specification MAY define such session level usage.”

That “MAY" seems more a statement of fact than permission. I suggest stating it without the normative keyword.</pre>
      </blockquote>
      <br>
      Agreed, implementing. <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">— 6th paragraph: "In this case, it is not possible to align what alternative rid-id that are used across different simulcast streams, like requiring all simulcast streams to use rid-id alternatives referring to the same codec format.”

I don’t understand the sentence.</pre>
      </blockquote>
      <br>
      The intention of the sentence is to make clear that there exists
      no<br>
      protocol mechanism to force the peer to choose the same
      alternative<br>
      in both simulcast streams in case there are multiple alternatives,<br>
      e.g. when both simulcast stream A and simulcast stream B have the<br>
      choice between HEVC and VP9, i.e. ensure that only HEVC or only
      VP9<br>
      is used for both simulcast streams. I propose to address this by<br>
      removing the sentence you didn't understand, and instead add a new<br>
      sentence last in the paragraph. Thus the whole paragraph reads:<br>
      <br>
      Use of more than a single, alternative simulcast format for a<br>
      simulcast stream MAY be specified as part of the attribute
      parameters<br>
      by expressing the simulcast stream as a comma-separated list of<br>
      alternative rid-id. The order of the rid-id alternatives within a<br>
      simulcast stream is significant; the rid-id alternatives are
      listed<br>
      from (left) most preferred to (right) least preferred. For the use
      of<br>
      simulcast, this overrides the normal codec preference as expressed
      by<br>
      format type ordering on the "m=" line, using regular SDP rules.
      This<br>
      is to enable a separation of general codec preferences and
      simulcast<br>
      stream configuration preferences. However, the choice of which<br>
      alternative to use per simulcast stream is independent, and there
      is<br>
      currently no mechanism to align the choice of alternative rid-ids<br>
      between different simulcast streams.<br>
      <br>
      <br>
      Better?<br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">— 10th paragraph: The first sentence is hard to parse.</pre>
      </blockquote>
      <br>
      I agree that this sentence is hard: <br>
      <br>
      Including an initially paused simulcast stream in "recv" direction
      for the part sending the SDP, sent towards an RTP sender, SHOULD
      cause the remote RTP sender to put the stream as unsolicited
      locally paused, unless there are other RTP stream receivers that
      do not mark the simulcast stream as initially paused.<br>
      <br>
      Is this reworded sentence better?<br>
      <br>
      If the endpoint sending the SDP includes an "recv" direction
      simulcast stream that is initially paused, then the remote RTP
      sender receiving the SDP SHOULD put its RTP stream in a
      unsolicited locally paused state. This unless there are there are
      other RTP stream receivers that do not mark the simulcast stream
      as initially paused.<br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§5.3.2, paragraph 3: “The answerer MUST be prepared to receive any of the receive direction rid-id alternatives, and MAY send any of the send direction alternatives that are kept in the answer.”

I think from reading further that you intend “that are kept in the answer” to restrict both the alternatives one must be ready to receive and may choose to send. But the comma before “and MAY” makes it seem like it only restricts the alternatives the answerer can choose to send.

</pre>
      </blockquote>
      An what the answer can sends is what is important. And the answer
      can actually add alternatives to what it can receive. Thus, "kept"
      is actually wrong. I suggest that we modify the sentence to read:<br>
      <br>
      The answerer MUST be prepared to receive any of the receive
      direction rid-id alternatives and MAY send any of the send
      direction alternatives that are part of the answer.<br>
      <br>
      Does that resolve the unclarity?<br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">
Editorial and Nits:

§1, last paragraph: Unclear antecedent for “it”.  (The document is motivated?)
</pre>
      </blockquote>
      <br>
      This document describes a few scenarios that motivates the use of
      simulcast, and also defines the needed RTP/RTCP and SDP signaling
      for it.<br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§3.1, Codec: “… (such as SDP MIME type) …”: Should that be SDP payload MIME type? (We aren’t talking about application/sdp, are we)</pre>
      </blockquote>
      <br>
      (such as RTP payload format MIME type)<br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">- Bitrate: s/amount/number</pre>
      </blockquote>
      <br>
      Ok<br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§3.3: I want to say s/ “ preferences to “ / “ preferences for”, but that seems wrong with “apply preferences”. So now I think there’s something awkward about the phrase “apply preference to the characteristics”. Does this mean the same as “state preferences for the characteristics”?
</pre>
      </blockquote>
      <br>
      Does this formulation resolve the issue?<br>
      <br>
      The application logic that controls the communication session may<br>
         allow receiving participants to state their preferences on the<br>
         characteristics of the RTP stream they like to receive, for
      example<br>
         in terms of the aspects listed in Section 3.1.<br>
      <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§4, 5th paragraph (starting with “The RID mechanism, as defined…”: It would make things easier to understand if you moved this paragraph before most of the discussion that talks about rids.</pre>
      </blockquote>
      <br>
      Agreed, move it up to be the second paragraph. <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">— 8th paragraph: "interpreted on a high level” s/on/at</pre>
      </blockquote>
      Ok<br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§5.2:
— paragraph 9: Missing “the” before send. “part” seems like the wrong word choice, but I’m not sure what was intended, maybe “peer”? (Same for paragraph 10).</pre>
      </blockquote>
      <br>
      endpoint I think works. <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">— Paragraph 10: Please expand “ TMMBR/TMMBN”</pre>
      </blockquote>
      <br>
      Done.<br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">§6.1, 2nd paragraph: s/“may not”/“might not"
</pre>
      </blockquote>
      <br>
      Done. <br>
      <br>
      <blockquote type="cite"
        cite="mid:2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com">
        <pre wrap="">







</pre>
      </blockquote>
      <br>
      <pre class="moz-signature" cols="72">-- 

Magnus Westerlund 

----------------------------------------------------------------------
Network Architecture &amp; Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class="moz-txt-link-abbreviated" href="mailto:magnus.westerlund@ericsson.com" moz-do-not-send="true">magnus.westerlund@ericsson.com</a>
----------------------------------------------------------------------</pre>
    </div>
  </body>
</html>

--------------FE7D32CBB4DC987CC5DFAD96--


From nobody Fri Apr  6 08:18:06 2018
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 3EC07127136 for <mmusic@ietfa.amsl.com>; Fri,  6 Apr 2018 08:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=GWtN2Lik; dkim=pass (1024-bit key) header.d=ericsson.com header.b=IPn/ccXj
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8__UE07GFyK for <mmusic@ietfa.amsl.com>; Fri,  6 Apr 2018 08:18:02 -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 3418D120726 for <mmusic@ietf.org>; Fri,  6 Apr 2018 08:18:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523027880; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ux3sQj9RmV2awZrBo/taSVrB5n56cwFKMbpHuVntd5U=; b=GWtN2LikdZB/KSqJ5FsJ1/aoWIOwtNvrCHLcmO0+0yldUB4PTOmicMbcqfxY5VHt S07jx2c0MiS3RI3aMUuYp5S3830AS9xlNfqKVh+QopKCxb2xMnCWd9YPU/QrGIRT 57peAMMMRiUU9L2iJEVp9JARepALCrQnQPlQ5MbN4eg=;
X-AuditID: c1b4fb3a-e39ff70000005d56-b7-5ac78fa7b31a
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id FB.9E.23894.7AF87CA5; Fri,  6 Apr 2018 17:18:00 +0200 (CEST)
Received: from ESESSMB501.ericsson.se (153.88.183.162) by ESESSHC002.ericsson.se (153.88.183.24) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 6 Apr 2018 17:17:59 +0200
Received: from ESESSMB504.ericsson.se (153.88.183.165) by ESESSMB501.ericsson.se (153.88.183.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.26; Fri, 6 Apr 2018 17:17:59 +0200
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB504.ericsson.se (153.88.183.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.26 via Frontend Transport; Fri, 6 Apr 2018 17:17:59 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wu0tmmtTOCNFdHxXxrdLQMAPB0qEDSyc9tpcZJSQySI=; b=IPn/ccXjUrCUrLUup+VDeSO31UczzF54PB2c/LJMRqhi3KlHvTXAIHA8eNbmCkyR/cnLa3WGpJ+At6ks5Mjwj+qtKde2wDDWvGvYgP6vaZd3JueOynXSfxDC41pfFp0qAeXPBji6abWMaOeRm7b9TkrD+iuGmX3coRbN4o4G3ug=
Received: from DB5PR07MB1078.eurprd07.prod.outlook.com (10.163.103.144) by DB5PR07MB1319.eurprd07.prod.outlook.com (10.164.42.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.675.4; Fri, 6 Apr 2018 15:17:57 +0000
Received: from DB5PR07MB1078.eurprd07.prod.outlook.com ([fe80::4992:86cc:7dfc:837d]) by DB5PR07MB1078.eurprd07.prod.outlook.com ([fe80::4992:86cc:7dfc:837d%4]) with mapi id 15.20.0675.004; Fri, 6 Apr 2018 15:17:57 +0000
From: Bo Burman <bo.burman@ericsson.com>
To: "Roni Even (A)" <roni.even@huawei.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
Thread-Index: AdPMES0/R3+uRXojQVG2VsIr3NCqRwBqS4Vg
Date: Fri, 6 Apr 2018 15:17:56 +0000
Message-ID: <DB5PR07MB107811003A4497F734FA69BD8DBA0@DB5PR07MB1078.eurprd07.prod.outlook.com>
References: <6E58094ECC8D8344914996DAD28F1CCD870EA5@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD870EA5@DGGEMM506-MBX.china.huawei.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=bo.burman@ericsson.com; 
x-originating-ip: [192.176.1.84]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB5PR07MB1319; 7:AJQNCiKTT6Ck33XSM5PHdvP2JsffUJfpdQhBpKiBmxyniqkbae3BGPfv97XFUkxmunCleENRmWkR6ZSaWBJz1js6Eo1ywNiT7s25FE/hsiF64wkBU8WU27hcyc6PwGnlXYVUxqpFoTaNV07d9+nVVuMa1NnqsfLD42O7IGwsyDMnmhCmLCoZdNN92RRe6pQS4dD/4M+Rykpx1fBRX5rzpNu4S77cQxf/JJfgUtiksgN6rLKC3AUlKlI9TrNWzLKF
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: c955c222-7ba8-4cd0-301b-08d59bd193a1
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:DB5PR07MB1319; 
x-ms-traffictypediagnostic: DB5PR07MB1319:
x-microsoft-antispam-prvs: <DB5PR07MB13197130A09C1352694C882A8DBA0@DB5PR07MB1319.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(3231221)(944501327)(52105095)(10201501046)(93006095)(93001095)(6041310)(20161123558120)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(6072148)(201708071742011); SRVR:DB5PR07MB1319; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1319; 
x-forefront-prvs: 0634F37BFF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(376002)(396003)(39380400002)(39860400002)(189003)(199004)(81156014)(3846002)(86362001)(316002)(6116002)(110136005)(790700001)(478600001)(6506007)(53546011)(66066001)(229853002)(33656002)(74316002)(99286004)(7736002)(5660300001)(105586002)(25786009)(7696005)(76176011)(2900100001)(966005)(6436002)(6306002)(55016002)(19609705001)(2501003)(14454004)(236005)(54896002)(9686003)(106356001)(476003)(186003)(26005)(102836004)(53936002)(11346002)(446003)(68736007)(6246003)(606006)(486006)(5250100002)(8936002)(81166006)(3660700001)(8676002)(3280700002)(97736004)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB5PR07MB1319; H:DB5PR07MB1078.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: dMiNXQzqBZv52LP7O3bDVME/BN2I24jk34JWQu22QXO3CL8OK9SAxjAK0enXLr0S29bUDLwaU6TmeWifsSb4O9YJrj2pydHZLD2YuKZuBlvkDL9NviP5EJNtk0x/j7+6hOA4RBI6xYgl9S9G8RX1upHuzQ8LwEotM8zQ6vrFxW3Je85UATT77bKxHmrkx1snW6Jq6+1ObcxmtZlCfCPYmkYo93rII1IK7nofLySnWRpzTeK3RHJa4L1xoKv5AMbg9A5zMuGKL7mAZV95Ogg9mOaA4TXto5Xmh1Eaz6IUA2KSw+OfDcRq7hkjIpHUQ0KU1zqMArHQqcBN+iFCzLXt0fWlO+iG5O89jkUCyd4g4rNZg+dSXbWO0l1bkwNt1izGh41lO5TYjuHwRZn1HZH38j8N2V5iWuDcd8LWACycydo=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR07MB107811003A4497F734FA69BD8DBA0DB5PR07MB1078eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c955c222-7ba8-4cd0-301b-08d59bd193a1
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Apr 2018 15:17:56.8827 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1319
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0hTcRTH+d17t13F1a/l8GBZsiSW5ZMQkworMBESJYkaZq68+Zhueu8U jSBNJdN8lE3ZCrfSVAxCm+DCIF/5CE1URhk1CQXTHpSQYr5yuxP873O+3+85nPPjR5OS5wJP OlWtZVi1Ml0mdKX0FzvAr7lyQBH4uJ4I1TVNU6EL/aNUOBFZ1PdTENnQsEzEEArX40lMemoO wwacTHRNMVgrqEyjd661+iOVj8b2liIXGvBRqK2eFpQiV1qC+xBY9R8ovjAj+FFXTNlTEryI oKjiAm80ENBqXhfaCwovEPCvQEfwThUBD0fWnMVXBH3lJcjeL8RyMFq+ONgdx8JE96LAzrtx NBibuoRbetvqEMlzMHQMFInsTGEf6N247ciIcTwUro+K+J3Ow9ORws08TbvgOOjtl9tlhL1g asnmWJvEHvBpxkjwh2JoeD1K8iyFuel1AZ+/BNX3R0S87g3zZflCnr1g3FiG7LcAbifgj/WO c5Af/NbpnIPOQXFTjYgPDW4+2NJ7AW/4wtvyUWeDCqZme516FGwMV5J8wzMSbAUGYRUKMGzb lmcNrA+WiQyOo3fBkH6G4vUjYOpcEPJ8GBqffCe3eLhrmtium5CoBUk5huMykoOD/Rk29RrH adT+akb7Em1+oe72lTAL6p491YMwjWRuYjM7oJAIlDlcXkYPApqUuYs7V/sVEnGSMu8Gw2qu sNnpDNeD9tCUzEN8+nqoQoKTlVpGxTCZDLvlErSLZz5Kazv4zuXb55t5B/bXJ0G7+PLfuKtj QcdiFxhVR6wGymulXskxLTsfUZOTWY2/ClUTryLm6TrdmeiEbCZxJWxI5dZq1obI1+4uTYUM l7wIlO6IOpF7yyf8zT6uoMqkXzUlPAixWeLGDmXNdUmolbPjaVlu8TY/efO9muW8CAsto7gU ZZAvyXLK/0f2JjU+AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JJoCOeXdeyPeLew20KLBup1glek>
Subject: Re: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 06 Apr 2018 15:18:04 -0000

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

Thanks Roni,

I believe this addresses my shepherd's review nits.

/Bo

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Roni Even (A)
Sent: den 4 april 2018 14:34
To: mmusic@ietf.org
Subject: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17

Hi,
I submitted a new revision of  https://tools.ietf.org/html/draft-ietf-mmusi=
c-data-channel-sdpneg-17 trying to address comments from Christer and Bo.
Thanks
Roni Even

--_000_DB5PR07MB107811003A4497F734FA69BD8DBA0DB5PR07MB1078eurp_
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.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: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]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Thanks Roni,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I believe this addresses my shepherd&#8217;s review =
nits.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">/Bo<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b>From:</b> mmusic [mailto:mmusic-bounces@ietf.org]=
 <b>On Behalf Of
</b>Roni Even (A)<br>
<b>Sent:</b> den 4 april 2018 14:34<br>
<b>To:</b> mmusic@ietf.org<br>
<b>Subject:</b> [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdp=
neg-17<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">I submitted a new revision of &nbsp;<a href=3D"https=
://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-17">https://to=
ols.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-17</a> trying to ad=
dress comments from Christer and Bo.<o:p></o:p></p>
<p class=3D"MsoNormal">Thanks<o:p></o:p></p>
<p class=3D"MsoNormal">Roni Even<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_DB5PR07MB107811003A4497F734FA69BD8DBA0DB5PR07MB1078eurp_--


From nobody Sun Apr  8 11:57:54 2018
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 C484E12D7E6; Sun,  8 Apr 2018 11:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 gOyMv0SfHlEA; Sun,  8 Apr 2018 11:57:44 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 662D512422F; Sun,  8 Apr 2018 11:57:44 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id r82so11946046wme.0; Sun, 08 Apr 2018 11:57:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=ry6h+VEV8x7gNj8ZgqpKQ1cWu3EXn1T1SKDW/Onl0wA=; b=G954YdE5qekSuNda6iq1tfEHI10aUEhOqyiWTdgabB5eyi0qQav4l1O7rl0Q7Stx0A YejmJghsm7tqz79rWD2TpBXwWgj9zz5eGx71/9ANBgXhFZzvgTmddPn+tl8nr876Swlg yhPsH1oB+pQhe7KTTxImpQ6KtDGJ5hfq/YhMJZ5+5qh9IrPrtxw2AaplFKKjZgk8PrWV w/3erjCZ9RiybgASCbWA+HyqIEgpxCKMgEVrx9okUGuAgNyoJnWbvfP/JVh4JSYp710j /baPhur+xa8lPui+1eG9yoYoJZGQXSeCbieW8xA1xs4D35YWJYTF6YuG1y6MUnnYfG8R FIPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ry6h+VEV8x7gNj8ZgqpKQ1cWu3EXn1T1SKDW/Onl0wA=; b=mXTQoJCCd/p5DMrhdT18mQ7hn/8/LWpTGuVl8E0z4JK70b9ikn1MJugv4q9icduJOH mwCbFJTTfkp1Wx07JTJZ9Wuvk49qOuDkULp3tikdoLsqkTX5j0+abUAy1v47EuwL9g9i iY7MVjEBSJGpsFl5kAOP+0jQMgZUqZPaVyCqf7tb3GgYDiwRnWeMZnMtTDazRIv8O18o jFu1+h88J8QbNTOiYPAGf+gpoTFo3A+OC4xtekR5TGdhnSff1ANYG5NA7j1HqLus5+r4 HOFWANGdcdY90EpOdZDrh+RVrJBsjdJkSPBN8QzONZCSybI/FVu6czi2nAGl/LwkJmVS qdCw==
X-Gm-Message-State: ALQs6tCrUzt2UixFJMLZJVqMVJs//Oqy8CpGAMsC4tFsoOHHDgsflms6 rRP7ENjs8rgOhuPmhZJH4KLeO198
X-Google-Smtp-Source: AIpwx4+k3wlYLf/AuzMsDUksQo9JvOk0nRb3nAUUdZowWBmPVw5C4SY16+d60EGbjAGZUFWOvQmoSw==
X-Received: by 10.46.153.147 with SMTP id w19mr21081484lji.93.1523213862490; Sun, 08 Apr 2018 11:57:42 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id y70-v6sm3086262lfd.29.2018.04.08.11.57.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Apr 2018 11:57:41 -0700 (PDT)
To: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
References: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com> <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com> <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <6ce0a44f-cca8-2105-73f5-75689dd8c611@gmail.com>
Date: Sun, 8 Apr 2018 20:57:39 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9RYbfouRQJ2TR39rMFYTnaHf8ws>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 08 Apr 2018 18:57:47 -0000

Mirja,

On 2018-04-05 16:19, Mirja Kuehlewind (IETF) wrote:
> Hi Thomas,
>
>> Am 04.04.2018 um 21:54 schrieb Thomas Stach <thomass.stach@gmail.com>:
>>
>> Mirja,
>>
>> thanks for your comments.
>>
>> On 2018-04-03 16:37, Mirja Kühlewind wrote:
>>> Mirja Kühlewind has entered the following ballot position for
>>> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>>
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to
>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:
>>>
>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>>>
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>> Thanks for the well-written doc and the quick response to the initial tsv
>>> review. Also thanks to Jörg for the thorough and very helpful review!
>>>
>>> As flagged by the tsv review, there can be an issue with the aggregation of
>>> candidates in one INFO message when rate limited and the path MTU/UPD
>>> fragmentation. While this is a small point only and I'm sure it can be easily
>>> addressed, it important enough that I decided to put a discuss in. I'm sure
>>> this can be resolved quickly as well.
>>>
>> As large messages are already addressed in RFC 3261, I could add something like
>> "As a potentially large number of candidates are aggregated in a INFO request,
>> the message size can easily exceed the path MTU. SIP [RF3261] requires that if a request
>> is within 200 bytes of the path MTU, or if it is larger than 1300 bytes and the path MTU is unknown,
>> that the request is sent using an RFC 2914 [43] congestion controlled transport protocol,
>> such as TCP.
> The only point is the interaction with the rate limit here. If you have to split up into two/multiple messages, you will not be able to send both immediately but have to wait for another interval. Maybe that can be further clarified with an additional sentence.
Well, as SIP already prohibits fragmenting a packet that that is larger 
than 1300 bytes, do we need to say something about the rate of for 
sending such "illegal" packets?

>
>> "
>>> Also if the document could give further guidance on an acceptable maximum for
>>> the rate of INFO requests that be even better!
>>>
>> Adam proposed in his review to
>>
>> "... require some minimum quarantine period between INFO requests (probably something in the range of 20 ms),
>> during which any new candidates that are gathered are aggregated into the next INFO message."
>>
>> Would that be enough of a guidance?
> Yes, that would be good! Usually we recommends something like one message per RTT. So probably 100ms or 200ms would be on the safe side but lower might be fine as well if the typically deployment scenario assumes a shorter RTT.

  I propose to add a 3rd paragraph to section 10.9

"As a potentially large number of candidates are aggregated in an INFO 
request,
the message size can easily exceed the path MTU. SIP [RF3261] requires 
that if a request
is within 200 bytes of the path MTU, or if it is larger than 1300 bytes 
and the path MTU is unknown,
that the request is sent using an RFC 2914 [43] congestion controlled 
transport protocol,
such as TCP.
In general, it is RECOMMENDED that a Trickle ICE Agent sends only one 
INFO request per RTT.
A quarantine period of 100ms would be on the safe side, but lower values 
might be fine as well
if the typically deployment scenario assumes a shorter RT."

Kind Regards
Thomas

<\snip>


From nobody Sun Apr  8 12:11:56 2018
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 ABF6F1272E1; Sun,  8 Apr 2018 12:11:48 -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 2UFQu36pZU88; Sun,  8 Apr 2018 12:11:46 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 EF33C1204DA; Sun,  8 Apr 2018 12:11:45 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id 80so6527228wrb.2; Sun, 08 Apr 2018 12:11:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=KG1SuGJamBbmXreJxlnmCEt1PDqPsRc/LURvAzTJehM=; b=U1qE4dKocq9mT1MAKvlszJDTI8BO30n3XrE+AihCZKEfJvQFSncQ2AYd2IDJ41Kfs9 ARD6Dll8+KWOxwz7YYEcYB86aljfs8Wu3LplnOZ9eN2Td83oE4Xl4aURts5gLxSDMjxF t+u0wfSolNMSRni2vMntawvnw90wKHAuBi7l92xV/O35d1RJbFTIuXE7Epxjs/hJdeWN A3f8QNpnLQsaYShfHOlaPByibA3HpPN186qTNQ74leTQgc4YoVqbHIKJ51Btyi77nnb3 CEeiU3f/bCbQ4p23qHX9amAvZr+3htHkqK+fJE5tRJFBMTnj67jOEckFMhZz0NNKhIfT zfbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=KG1SuGJamBbmXreJxlnmCEt1PDqPsRc/LURvAzTJehM=; b=FtvTneG83gbmz6lQ2MqrtWJXvnFa+tX3ORIKntlA0r1NZdBvOdAy99KHF7HQUdHWRW skKUsJ5W0ksAj5SpfW0FJeL5UpWBK33X2mSVnYjMmHpbNx1SUsJN+9uRJiRWL0X+wE+P 19oRTwynDVdohAwwn2dwjCPsIQGdESL+JVXjhbBelDB145jxAI+zpmGdfjfs4xkNGjy+ cJFqD/OSq5p9IaMvZ9qX82ShIuuKT+uPNBfUHKeETGUX2klN7rIsjO4juBesb/x4+Mbq WpI2ElBjcEhQNv4sxY3uneX8g9kJ4RgIMk3iZURs8HlaGbkvA4Yhg7BDIIsWF1vpAgK3 K7qQ==
X-Gm-Message-State: ALQs6tACrqTUCBorOozfwAnkkXfdlpZty+xyxYY4+sd8hudPTBuuV5Ho 8uS8/EW10uQuFasxstofIbrasHvk
X-Google-Smtp-Source: AIpwx48gLR5SZaebWJ8UEZVpCm9S59qTiBRLYH/68BsBU0Wpwm4PMcc7FPeh8fI7KF1bIOXNxZeudw==
X-Received: by 2002:a19:cc10:: with SMTP id c16-v6mr4966515lfg.62.1523214704035;  Sun, 08 Apr 2018 12:11:44 -0700 (PDT)
Received: from [192.168.2.112] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id c64-v6sm1028380lfc.67.2018.04.08.12.11.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 08 Apr 2018 12:11:43 -0700 (PDT)
To: Eric Rescorla <ekr@rtfm.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
References: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com> <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com> <CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com> <587c07b6-c086-c429-761a-ca655372f32e@gmail.com> <CABcZeBO6FY58=_B64G7g3tA+niWP1sGsY6r09=2DKMp8j40mDQ@mail.gmail.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <bd243fd0-f868-2a57-cac1-f61d1b9b09a7@gmail.com>
Date: Sun, 8 Apr 2018 21:11:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBO6FY58=_B64G7g3tA+niWP1sGsY6r09=2DKMp8j40mDQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------13BCA5874801A096BBB13EDF"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/pyV5IPOUHuaqJ5RQjKThgP_Pl3M>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 08 Apr 2018 19:11:49 -0000

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

EKR,


On 2018-04-05 22:27, Eric Rescorla wrote:
>
>
> On Thu, Apr 5, 2018 at 1:10 PM, Thomas Stach <thomass.stach@gmail.com 
> <mailto:thomass.stach@gmail.com>> wrote:
>
>     EKR,
>
>
>     On 2018-04-05 15:57, Eric Rescorla wrote:
>>
>>
>>     On Tue, Apr 3, 2018 at 11:46 AM, Thomas Stach
>>     <thomass.stach@gmail.com <mailto:thomass.stach@gmail.com>> wrote:
>>
>>         EKR,
>>
>>         thanks for your comments, responses inline
>>
>>
>>         On 2018-04-03 00:54, Eric Rescorla wrote:
>>>         Eric Rescorla has entered the following ballot position for
>>>         draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>>
>>>         When responding, please keep the subject line intact and reply to all
>>>         email addresses included in the To and CC lines. (Feel free to cut this
>>>         introductory paragraph, however.)
>>>
>>>
>>>         Please refer tohttps://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-trickle-ice-sip/
>>>         <https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/>
>>>
>>>
>>>
>>>         ----------------------------------------------------------------------
>>>         DISCUSS:
>>>         ----------------------------------------------------------------------
>>>
>>>             the Offer (as would be the case when Half Trickle is performed or
>>>             when new candidates have not been learned since then).
>>>         IMPORTANT: They must be in order, right?
>>         I'm not sure what the issues is here.
>>         The cited text addresses the first of two cases, i.e. the
>>         case  where the INFO requests repeats
>>          the exact same set of candidates that was already provided
>>         in the initial offer.
>>         This could happen when
>>         a) Half Trickle is used (all candidate were already in the
>>         initial offer) or
>>         b) Full Trickle is used where  the offerer is currently
>>         gathering additional candidates, but did not yet get them.
>>
>>         The second case (Full Trickle with additional candidates
>>         already available) is addressed in the subsequent paragraph.
>>         .. and yes the candidates are sent in the order as they were
>>         gathered.
>>
>>
>>     Right. I'm saying you need to say that.
>     OK, will do
>>
>>
>>>             'application/trickle-ice-sdpfrag' bodies do not interfere with the
>>>             Offer/Answer procedures as specified in [RFC3264].
>>>         IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.
>>         5888 is cited as it defines the a=mid: attribute that we used
>>         for identifying the m-line to which a candidate belongs.
>>         The a=mid: attribute helps in case of multiple m-lines, when
>>         we already have gathered candidates
>>         for e.g. the first and fourth m-line, but not for the 2nd and
>>         3rd.
>>
>>
>>     Right. You need to describe what a pseudo-m= line is because it's
>>     not defined anywhere.
>     Well, we have this text in section 4.4 at the first occurrence of
>     the term.
>
>         "... this is handled through the use of pseudo "m=" lines
>         and identification tags in "a=mid:" attributes as defined in
>         [RFC5888 <https://tools.ietf.org/html/rfc5888>].  Pseudo "m=" lines follow the SDP syntax for "m=" lines as
>         defined in [RFC4566 <https://tools.ietf.org/html/rfc4566>], but provide no semantics other than indicating
>         to which "m=" line a candidate belongs. "
>
>
>     Isn't that good enough?
>
>
> Not really. The way it reads is that pseudo m= lines are defines in 
> 5888 but they're not. This is the
> normative source of them. I would rephrase
> "use of pseudo "m=" lines, which follow the SDP syntax of..." and then 
> talk about mid in the next
> sentence.
I'll change to

"... this is handled through the use of pseudo "m=" lines.
     Pseudo "m=" lines follow the SDP syntax for "m=" lines as
    defined in [RFC4566 <https://tools.ietf.org/html/rfc4566>], but provide no semantics other than indicating
    to which "m=" line a candidate belongs.
    A pseudo  "m=" line is linked to the corresponding "m=" line in the
    SDP Offer or Answer via the identification tag in a "a=mid:" attribute as defined in [RFC5888 <https://tools.ietf.org/html/rfc5888>].
"


Kind Regards
Thomas

>
> -Ekr
>
>>         sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
>>         the same order as they were gathered.  In other words, the sequence
>>         of a previously sent list of candidates MUST NOT change in subsequent
>>
>>     IMPORTANT: This appears to conflict with the guidance in Section 6 of
>>     the trickle document, which is about reordering candidates from how
>>     they were gathered.
>
>     Do you mean section 7  which talks about reordering candidate
>     _pairs_ at the IE agents?
>
>
> No. Section 16, sorry for the typo.
>
>     Section 15? :-)
>>
>>        To achieve this, when trickling candidates, agents MUST
>>     respect the
>>        order in which the components and streams appear (implicitly or
>>        explicitly) as they have been negotiated by means of the relevant
>>        candidate information.  Therefore candidates for a given component
>>        MUST NOT be conveyed prior to candidates for a component with
>>     a lower
>>        ID number within the same foundation.  In addition, candidates
>>     MUST
>>        be paired, following the procedures in Section 8.1.1, in the same
>>        order they are conveyed.
>>
>>
>>
>>         We  require that the ordering of the _candidates_ MUST not
>>         change
>>         when the candidates are sent several times from one  ICE
>>         agent to its peer in subsequent INFO requests.
>>
>>
>>     The problem is the text "same order they were gathered" because
>>     the ICE trickle text
>>     requires sending them in an order different from when they were
>>     gathered.
>     OK, now I see. I will clarify and refer to section 15 of
>     draft-ice-trickle
>>
>>
>>         I don't see a conflict.
>>>         ----------------------------------------------------------------------
>>>         COMMENT:
>>>         ----------------------------------------------------------------------
>>>
>>>            SIP message.  At the remote agent the gathering procedure is repeated
>>>             and candidates are sent to the first agent.  Finally, a third phase
>>>             starts where connectivity between all candidates in both sets is
>>>
>>>         This suggests that they have to happen in sequence, but that's not true.
>>>
>>>             include in each "m="-line a "a=mid:" attribute in accordance to
>>>             [RFC5888].
>>>
>>>         Why is this required?
>>         As above, the a=mid: attribute helps in case of multiple
>>         m-lines, when we already have gathered candidates
>>         for e.g. the first and fourth m-line, but not for the 2nd and
>>         3rd.
>>
>>
>>     Right. You need to actually explain this.
>     I'll do
>>
>>
>>>             section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
>>>             is not yet provided.
>>>
>>>         Can you explain why you cease retransmitting on receiving INFO? I assume
>>>         because it's an implicit ACK of your INFO?
>>         The INFO is an ACK that an early dialog is now established,
>>         such that INFOs can be send in the reverse direction as well.
>>
>>
>>     It would be helpful to explain this as well. I defer to the ART
>>     ADs on the suitability of this technique.
>     I'll do
>>
>>
>>>             m=lines that they pertain to.  The correspondence can be made via the
>>>             "a=mid:" attributes.
>>>
>>>         This whole section needs to be rewritten to make clear what's going on:
>>>
>>>              candidates are grouped in sections headed by "pseudo" m=lines
>>>              These sections contain a=mid values which point back to the true m=line.
>>         Would it be sufficient to rephrase as follows?
>>
>>         Note, that there is no requirement that the Info request body
>>             contains as many pseudo m= lines as the Offer/Answer contains m=
>>             lines, nor that the pseudo m= lines be in the same order as the
>>             m=lines that they pertain to.  The correspondence can be made via the
>>             "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
>>              These sections contain a=mid: attribute values which point back to the true m=line.
>>
>>
>>     Sure.
>     Thanks
>     Thomas
>
>


--------------13BCA5874801A096BBB13EDF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><tt>EKR,</tt></p>
    <br>
    <div class="moz-cite-prefix">On 2018-04-05 22:27, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABcZeBO6FY58=_B64G7g3tA+niWP1sGsY6r09=2DKMp8j40mDQ@mail.gmail.com">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Thu, Apr 5, 2018 at 1:10 PM,
            Thomas Stach <span dir="ltr">&lt;<a
                href="mailto:thomass.stach@gmail.com" target="_blank"
                moz-do-not-send="true">thomass.stach@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF">
                <p><tt>EKR,</tt><br>
                </p>
                <div>
                  <div class="h5"> <br>
                    <div class="m_-7821002768604845176moz-cite-prefix">On
                      2018-04-05 15:57, Eric Rescorla wrote:<br>
                    </div>
                    <blockquote type="cite">
                      <div dir="ltr"><br>
                        <div class="gmail_extra"><br>
                          <div class="gmail_quote">On Tue, Apr 3, 2018
                            at 11:46 AM, Thomas Stach <span dir="ltr">&lt;<a
                                href="mailto:thomass.stach@gmail.com"
                                target="_blank" moz-do-not-send="true">thomass.stach@gmail.com</a>&gt;</span>
                            wrote:<br>
                            <blockquote class="gmail_quote"
                              style="margin:0px 0px 0px
                              0.8ex;border-left:1px solid
                              rgb(204,204,204);padding-left:1ex">
                              <div bgcolor="#FFFFFF">
                                <p>EKR,</p>
                                <p>thanks for your comments, responses
                                  inline<br>
                                </p>
                                <span
                                  class="m_-7821002768604845176gmail-">
                                  <br>
                                  <div
class="m_-7821002768604845176gmail-m_-3709797337778756038moz-cite-prefix">On
                                    2018-04-03 00:54, Eric Rescorla
                                    wrote:<br>
                                  </div>
                                  <blockquote type="cite">
                                    <pre>Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss

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


Please refer to <a class="m_-7821002768604845176gmail-m_-3709797337778756038moz-txt-link-freetext" href="https://www.ietf.org/iesg/statement/discuss-criteria.html" target="_blank" moz-do-not-send="true">https://www.ietf.org/iesg/stat<wbr>ement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="m_-7821002768604845176gmail-m_-3709797337778756038moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/" target="_blank" moz-do-not-send="true">https://datatracker.ietf.org/d<wbr>oc/draft-ietf-mmusic-trickle-i<wbr>ce-sip/</a>



------------------------------<wbr>------------------------------<wbr>----------
DISCUSS:
------------------------------<wbr>------------------------------<wbr>----------

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?</pre>
                                  </blockquote>
                                </span> I'm not sure what the issues is
                                here.<br>
                                The cited text addresses the first of
                                two cases, i.e. the case  where the INFO
                                requests repeats <br>
                                 the exact same set of candidates that
                                was already provided in the initial
                                offer. <br>
                                This could happen when <br>
                                a) Half Trickle is used (all candidate
                                were already in the initial offer) or<br>
                                b) Full Trickle is used where  the
                                offerer is currently gathering
                                additional candidates, but did not yet
                                get them.<br>
                                <br>
                                The second case (Full Trickle with
                                additional candidates already available)
                                is addressed in the subsequent
                                paragraph.<br>
                                .. and yes the candidates are sent in
                                the order as they were gathered.<span
                                  class="m_-7821002768604845176gmail-"><br>
                                </span></div>
                            </blockquote>
                            <div><br>
                            </div>
                            <div>Right. I'm saying you need to say that.</div>
                          </div>
                        </div>
                      </div>
                    </blockquote>
                  </div>
                </div>
                OK, will do<span class=""><br>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div class="gmail_quote">
                          <div><br>
                          </div>
                          <div> <br>
                          </div>
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <div bgcolor="#FFFFFF"><span
                                class="m_-7821002768604845176gmail-">
                                <blockquote type="cite">
                                  <pre>   'application/trickle-ice-sdpfr<wbr>ag' bodies do not interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.</pre>
                                </blockquote>
                              </span> 5888 is cited as it defines the
                              a=mid: attribute that we used for
                              identifying the m-line to which a
                              candidate belongs.<br>
                              The a=mid: attribute helps in case of
                              multiple m-lines, when we already have
                              gathered candidates <br>
                              for e.g. the first and fourth m-line, but
                              not for the 2nd and 3rd. <br>
                            </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>Right. You need to describe what a
                            pseudo-m= line is because it's not defined
                            anywhere.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> Well, we have this text in section 4.4 at the
                first occurrence of the term.<br>
                <br>
                <pre class="m_-7821002768604845176newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">   "... this is handled through the use of pseudo "m=" lines 
   and identification tags in "a=mid:" attributes as defined in
   [<a href="https://tools.ietf.org/html/rfc5888" title="&quot;The Session Description Protocol (SDP) Grouping Framework&quot;" target="_blank" moz-do-not-send="true">RFC5888</a>].  Pseudo "m=" lines follow the SDP syntax for "m=" lines as
   defined in [<a href="https://tools.ietf.org/html/rfc4566" title="&quot;SDP: Session Description Protocol&quot;" target="_blank" moz-do-not-send="true">RFC4566</a>], but provide no semantics other than indicating
   to which "m=" line a candidate belongs. "
</pre>
                <br>
                Isn't that good enough?<span class=""><br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>Not really. The way it reads is that pseudo m= lines
              are defines in 5888 but they're not. This is the</div>
            <div class="gmail_quote">normative source of them. I would
              rephrase <br>
            </div>
            <div class="gmail_quote">"use of pseudo "m=" lines, which
              follow the SDP syntax of..." and then talk about mid in
              the next</div>
            <div class="gmail_quote">sentence.</div>
          </div>
        </div>
      </div>
    </blockquote>
    I'll change to<br>
    <br>
    <pre class="m_-7821002768604845176newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">"... this is handled through the use of pseudo "m=" lines.
    Pseudo "m=" lines follow the SDP syntax for "m=" lines as
   defined in [<a href="https://tools.ietf.org/html/rfc4566" title="&quot;SDP: Session Description Protocol&quot;" target="_blank">RFC4566</a>], but provide no semantics other than indicating
   to which "m=" line a candidate belongs. 
   A pseudo  "m=" line is linked to the corresponding "m=" line in the 
   SDP Offer or Answer via the identification tag in a "a=mid:" attribute as defined in [<a href="https://tools.ietf.org/html/rfc5888" title="&quot;The Session Description Protocol (SDP) Grouping Framework&quot;" target="_blank">RFC5888</a>]. 
"


Kind Regards
Thomas

</pre>
    <blockquote type="cite"
cite="mid:CABcZeBO6FY58=_B64G7g3tA+niWP1sGsY6r09=2DKMp8j40mDQ@mail.gmail.com">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote"><br>
            <div class="gmail_quote">-Ekr<br>
            </div>
            <div class="gmail_quote">
              <div><br>
              </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">
                <div bgcolor="#FFFFFF"><span
                    class="m_-7821002768604845176gmail-">
                    <blockquote type="cite">
                      <pre>   sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.</pre>
                    </blockquote>
                    <br>
                  </span> Do you mean section 7  which talks about
                  reordering candidate _pairs_ at the IE agents?<br>
                </div>
              </blockquote>
              <div><br>
              </div>
              <div>No. Section 16, sorry for the typo.</div>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div text="#000000" bgcolor="#FFFFFF"><span class="">
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra"> </div>
                    </div>
                  </blockquote>
                </span> Section 15? :-)<span class=""><br>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div class="gmail_quote">
                          <div><br>
                          </div>
                          <div>   To achieve this, when trickling
                            candidates, agents MUST respect the<br>
                               order in which the components and streams
                            appear (implicitly or<br>
                               explicitly) as they have been negotiated
                            by means of the relevant<br>
                               candidate information.  Therefore
                            candidates for a given component<br>
                               MUST NOT be conveyed prior to candidates
                            for a component with a lower<br>
                               ID number within the same foundation.  In
                            addition, candidates MUST<br>
                               be paired, following the procedures in
                            Section 8.1.1, in the same<br>
                               order they are conveyed.<br>
                            <br>
                          </div>
                          <div><br>
                          </div>
                          <div> <br>
                          </div>
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <div bgcolor="#FFFFFF"> We  require that the
                              ordering of the _candidates_ MUST not
                              change  <br>
                              when the candidates are sent several times
                              from one  ICE agent to its peer in
                              subsequent INFO requests.<br>
                            </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>The problem is the text "same order they
                            were gathered" because the ICE trickle text</div>
                          <div>requires sending them in an order
                            different from when they were gathered.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> OK, now I see. I will clarify and refer to
                section 15 of draft-ice-trickle<span class=""><br>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div class="gmail_quote">
                          <div><br>
                          </div>
                          <div><br>
                          </div>
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <div bgcolor="#FFFFFF"> I don't see a
                              conflict.<span
                                class="m_-7821002768604845176gmail-"><br>
                                <blockquote type="cite">
                                  <pre>------------------------------<wbr>------------------------------<wbr>----------
COMMENT:
------------------------------<wbr>------------------------------<wbr>----------

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that's not true.

   include in each "m="-line a "a=mid:" attribute in accordance to
   [RFC5888].

Why is this required?</pre>
                                </blockquote>
                              </span> As above, the a=mid: attribute
                              helps in case of multiple m-lines, when we
                              already have gathered candidates <br>
                              for e.g. the first and fourth m-line, but
                              not for the 2nd and 3rd. </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>Right. You need to actually explain this.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> I'll do<span class=""><br>
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div class="gmail_quote">
                          <div><br>
                          </div>
                          <div> <br>
                          </div>
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <div bgcolor="#FFFFFF"><span
                                class="m_-7821002768604845176gmail-">
                                <blockquote type="cite">
                                  <pre>   section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it's an implicit ACK of your INFO?</pre>
                                </blockquote>
                              </span> The INFO is an ACK that an early
                              dialog is now established, such that INFOs
                              can be send in the reverse direction as
                              well.<span
                                class="m_-7821002768604845176gmail-"><br>
                              </span></div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>It would be helpful to explain this as
                            well. I defer to the ART ADs on the
                            suitability of this technique.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> I'll do <span class="">
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div class="gmail_extra">
                        <div class="gmail_quote">
                          <div><br>
                          </div>
                          <div> <br>
                          </div>
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <div bgcolor="#FFFFFF"><span
                                class="m_-7821002768604845176gmail-">
                                <blockquote type="cite">
                                  <pre>   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes.

This whole section needs to be rewritten to make clear what's going on:

    candidates are grouped in sections headed by "pseudo" m=lines
    These sections contain a=mid values which point back to the true m=line.
</pre>
                                </blockquote>
                              </span> Would it be sufficient to rephrase
                              as follows?<br>
                              <pre class="m_-7821002768604845176gmail-m_-3709797337778756038newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">Note, that there is no requirement that the Info request body
   contains as many pseudo m= lines as the Offer/Answer contains m=
   lines, nor that the pseudo m= lines be in the same order as the
   m=lines that they pertain to.  The correspondence can be made via the
   "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
    These sections contain a=mid: attribute values which point back to the true m=line.</pre>
                            </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>Sure.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> Thanks <br>
                <span class="HOEnZb"><font color="#888888"> Thomas<br>
                    <br>
                  </font></span></div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------13BCA5874801A096BBB13EDF--


From nobody Sun Apr  8 15:10:39 2018
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 4B7EC12D881 for <mmusic@ietfa.amsl.com>; Sun,  8 Apr 2018 15:10:37 -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=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 sIBaroFGuaY3 for <mmusic@ietfa.amsl.com>; Sun,  8 Apr 2018 15:10:34 -0700 (PDT)
Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 6444712D879 for <mmusic@ietf.org>; Sun,  8 Apr 2018 15:10:29 -0700 (PDT)
Received: by mail-ot0-x233.google.com with SMTP id m22-v6so3565395otf.8 for <mmusic@ietf.org>; Sun, 08 Apr 2018 15:10: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=WECFx9PXtBbuhIurGTIIMCpxEvzDzB+2YoKVm0b1nrM=; b=ORrAfot1JTM1iNU3MU4wzqcJRwSBchzAPqMTjmSiL6qujHd6neVfVOyo3QpBydmlaK GKSHkXJMryF8VjBXi+YhM/hNfnVuqE8ayAOrxUd2QAmo/1hUjtbqmqH+StCaV8prPLat QbwXDCyhkcu1M84RSBXXwS5f+lXRGdOfLcQ+m88XjpBSgdRyuPJq6+swnJ2rNJP5Ty6Z DBXlq00JaDTUTg2kh8GRKwgPSktVrJ5OSWv7h7WAHR9HmBn5gvbwqfekdzo2GsAFfgDf Q6G/jC9cvmswRwO+LtFZxZAKmiJV1WIWADCFQOCHLHXiXvf7dCHeoatU3MwNH1+GX3W7 iGgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WECFx9PXtBbuhIurGTIIMCpxEvzDzB+2YoKVm0b1nrM=; b=r3ahuRwH4pQAwQ5FGqXzg7bNrUHs/QhJvm36deosIqCgfCTtG0hPr4e3Zb9U701qPo 7RNKDogGiNYT6JDPPIUtkNkpSQNaHuZ8pKQEZrpmDV94AzhqWcGPiOkcRyaLq0s9Nd2H cHTt4xN82U7m3HmF7UpWLUSKreQ363wMp2S9vBI/zSPgRQezIud66d/PuvT/MXWteZCG aYITNEzJPmqVCkJDORr/+DrNuiPC6nN6Ho3JIomeiSreH7e9fQa1oBeSIUThsLly5elM 0t2D6ZSFh714E/Q8Kt4j8+K4WfT/XUKnADj+3j1BYPJS4fC3IpBjGPxZ4nZrUhg1VMjM 7/Xw==
X-Gm-Message-State: ALQs6tAQSqc06z/eRq+hMRw5YwcCx7fkcBPGCB1xJ7rJxiSWFdJ2O8dX Zya4Pd4egmvxKPqpXGteFqURWOoViZgLe0wFSuanlA==
X-Google-Smtp-Source: AIpwx49iNCaKeBHjw4X/utvz0aapjFZyM89lm5od9m2QutEGfZf/6vz202rxTV5d4KwaZ062etycHPmajhnEmvMgoho=
X-Received: by 2002:a9d:3636:: with SMTP id w51-v6mr21564160otb.101.1523225428666;  Sun, 08 Apr 2018 15:10:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.130 with HTTP; Sun, 8 Apr 2018 15:09:48 -0700 (PDT)
In-Reply-To: <bd243fd0-f868-2a57-cac1-f61d1b9b09a7@gmail.com>
References: <152270967580.17934.13551066196088636469.idtracker@ietfa.amsl.com> <bc0718f4-cd39-9b75-e1c5-db501928cc9c@gmail.com> <CABcZeBNbz8h7N08UUmusOQL8ae=8aU9Z05d6yHfui-YdCX0Bqg@mail.gmail.com> <587c07b6-c086-c429-761a-ca655372f32e@gmail.com> <CABcZeBO6FY58=_B64G7g3tA+niWP1sGsY6r09=2DKMp8j40mDQ@mail.gmail.com> <bd243fd0-f868-2a57-cac1-f61d1b9b09a7@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 8 Apr 2018 15:09:48 -0700
Message-ID: <CABcZeBOY_PUV2vMUhv-wgEK_z0bH6jG-07P8oiit6Y=JYmzXAw@mail.gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org,  mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000096c00e05695d8e39"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2qXtfaGXnaOahjFfYDX6XBWhxNo>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 08 Apr 2018 22:10:37 -0000

--00000000000096c00e05695d8e39
Content-Type: text/plain; charset="UTF-8"

LGTM.



On Sun, Apr 8, 2018 at 12:11 PM, Thomas Stach <thomass.stach@gmail.com>
wrote:

> EKR,
>
> On 2018-04-05 22:27, Eric Rescorla wrote:
>
>
>
> On Thu, Apr 5, 2018 at 1:10 PM, Thomas Stach <thomass.stach@gmail.com>
> wrote:
>
>> EKR,
>>
>> On 2018-04-05 15:57, Eric Rescorla wrote:
>>
>>
>>
>> On Tue, Apr 3, 2018 at 11:46 AM, Thomas Stach <thomass.stach@gmail.com>
>> wrote:
>>
>>> EKR,
>>>
>>> thanks for your comments, responses inline
>>>
>>> On 2018-04-03 00:54, Eric Rescorla wrote:
>>>
>>> Eric Rescorla has entered the following ballot position for
>>> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>>
>>> When responding, please keep the subject line intact and reply to all
>>> email addresses included in the To and CC lines. (Feel free to cut this
>>> introductory paragraph, however.)
>>>
>>>
>>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>>> for more information about IESG DISCUSS and COMMENT positions.
>>>
>>>
>>> The document, along with other ballot positions, can be found here:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>>>
>>>
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>>    the Offer (as would be the case when Half Trickle is performed or
>>>    when new candidates have not been learned since then).
>>> IMPORTANT: They must be in order, right?
>>>
>>> I'm not sure what the issues is here.
>>> The cited text addresses the first of two cases, i.e. the case  where
>>> the INFO requests repeats
>>>  the exact same set of candidates that was already provided in the
>>> initial offer.
>>> This could happen when
>>> a) Half Trickle is used (all candidate were already in the initial
>>> offer) or
>>> b) Full Trickle is used where  the offerer is currently gathering
>>> additional candidates, but did not yet get them.
>>>
>>> The second case (Full Trickle with additional candidates already
>>> available) is addressed in the subsequent paragraph.
>>> .. and yes the candidates are sent in the order as they were gathered.
>>>
>>
>> Right. I'm saying you need to say that.
>>
>> OK, will do
>>
>>
>>
>>    'application/trickle-ice-sdpfrag' bodies do not interfere with the
>>>    Offer/Answer procedures as specified in [RFC3264].
>>> IMPORTANT: "pseudo" m= lines are not defined in 5888 so this is very unclear.
>>>
>>> 5888 is cited as it defines the a=mid: attribute that we used for
>>> identifying the m-line to which a candidate belongs.
>>> The a=mid: attribute helps in case of multiple m-lines, when we already
>>> have gathered candidates
>>> for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>>>
>>
>> Right. You need to describe what a pseudo-m= line is because it's not
>> defined anywhere.
>>
>> Well, we have this text in section 4.4 at the first occurrence of the
>> term.
>>
>>    "... this is handled through the use of pseudo "m=" lines
>>    and identification tags in "a=mid:" attributes as defined in
>>    [RFC5888 <https://tools.ietf.org/html/rfc5888>].  Pseudo "m=" lines follow the SDP syntax for "m=" lines as
>>    defined in [RFC4566 <https://tools.ietf.org/html/rfc4566>], but provide no semantics other than indicating
>>    to which "m=" line a candidate belongs. "
>>
>>
>> Isn't that good enough?
>>
>
> Not really. The way it reads is that pseudo m= lines are defines in 5888
> but they're not. This is the
> normative source of them. I would rephrase
> "use of pseudo "m=" lines, which follow the SDP syntax of..." and then
> talk about mid in the next
> sentence.
>
> I'll change to
>
> "... this is handled through the use of pseudo "m=" lines.
>     Pseudo "m=" lines follow the SDP syntax for "m=" lines as
>    defined in [RFC4566 <https://tools.ietf.org/html/rfc4566>], but provide no semantics other than indicating
>    to which "m=" line a candidate belongs.
>    A pseudo  "m=" line is linked to the corresponding "m=" line in the
>    SDP Offer or Answer via the identification tag in a "a=mid:" attribute as defined in [RFC5888 <https://tools.ietf.org/html/rfc5888>].
> "
>
>
> Kind Regards
> Thomas
>
>
>
> -Ekr
>
>    sent under the same combination of "a=ice-pwd:" and "a=ice-ufrag:" in
>>    the same order as they were gathered.  In other words, the sequence
>>    of a previously sent list of candidates MUST NOT change in subsequent
>>
>> IMPORTANT: This appears to conflict with the guidance in Section 6 of
>> the trickle document, which is about reordering candidates from how
>> they were gathered.
>>
>>
>> Do you mean section 7  which talks about reordering candidate _pairs_ at
>> the IE agents?
>>
>
> No. Section 16, sorry for the typo.
>
>> Section 15? :-)
>>
>>
>>    To achieve this, when trickling candidates, agents MUST respect the
>>    order in which the components and streams appear (implicitly or
>>    explicitly) as they have been negotiated by means of the relevant
>>    candidate information.  Therefore candidates for a given component
>>    MUST NOT be conveyed prior to candidates for a component with a lower
>>    ID number within the same foundation.  In addition, candidates MUST
>>    be paired, following the procedures in Section 8.1.1, in the same
>>    order they are conveyed.
>>
>>
>>
>> We  require that the ordering of the _candidates_ MUST not change
>>> when the candidates are sent several times from one  ICE agent to its
>>> peer in subsequent INFO requests.
>>>
>>
>> The problem is the text "same order they were gathered" because the ICE
>> trickle text
>> requires sending them in an order different from when they were gathered.
>>
>> OK, now I see. I will clarify and refer to section 15 of draft-ice-trickle
>>
>>
>>
>> I don't see a conflict.
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>>   SIP message.  At the remote agent the gathering procedure is repeated
>>>    and candidates are sent to the first agent.  Finally, a third phase
>>>    starts where connectivity between all candidates in both sets is
>>>
>>> This suggests that they have to happen in sequence, but that's not true.
>>>
>>>    include in each "m="-line a "a=mid:" attribute in accordance to
>>>    [RFC5888].
>>>
>>> Why is this required?
>>>
>>> As above, the a=mid: attribute helps in case of multiple m-lines, when
>>> we already have gathered candidates
>>> for e.g. the first and fourth m-line, but not for the 2nd and 3rd.
>>>
>>
>> Right. You need to actually explain this.
>>
>> I'll do
>>
>>
>>
>>    section 8.1.1 of [I-D.ietf-mmusic-ice-sip-sdp] except that an Answer
>>>    is not yet provided.
>>>
>>> Can you explain why you cease retransmitting on receiving INFO? I assume
>>> because it's an implicit ACK of your INFO?
>>>
>>> The INFO is an ACK that an early dialog is now established, such that
>>> INFOs can be send in the reverse direction as well.
>>>
>>
>> It would be helpful to explain this as well. I defer to the ART ADs on
>> the suitability of this technique.
>>
>> I'll do
>>
>>
>>
>>    m=lines that they pertain to.  The correspondence can be made via the
>>>    "a=mid:" attributes.
>>>
>>> This whole section needs to be rewritten to make clear what's going on:
>>>
>>>     candidates are grouped in sections headed by "pseudo" m=lines
>>>     These sections contain a=mid values which point back to the true m=line.
>>>
>>> Would it be sufficient to rephrase as follows?
>>>
>>> Note, that there is no requirement that the Info request body
>>>    contains as many pseudo m= lines as the Offer/Answer contains m=
>>>    lines, nor that the pseudo m= lines be in the same order as the
>>>    m=lines that they pertain to.  The correspondence can be made via the
>>>    "a=mid:" attributes since candidates are grouped in sections headed by "pseudo" m=lines.
>>>     These sections contain a=mid: attribute values which point back to the true m=line.
>>>
>>>
>> Sure.
>>
>> Thanks
>> Thomas
>>
>>
>
>

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

<div dir=3D"ltr"><div>LGTM.</div><div><br></div><div><br></div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Apr 8, 2018 at =
12:11 PM, Thomas Stach <span dir=3D"ltr">&lt;<a href=3D"mailto:thomass.stac=
h@gmail.com" target=3D"_blank">thomass.stach@gmail.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p><tt>EKR,</tt></p><div><div class=3D"h5">
    <br>
    <div class=3D"m_-7086147813399818777moz-cite-prefix">On 2018-04-05 22:2=
7, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr"><br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Thu, Apr 5, 2018 at 1:10 PM,
            Thomas Stach <span dir=3D"ltr">&lt;<a href=3D"mailto:thomass.st=
ach@gmail.com" target=3D"_blank">thomass.stach@gmail.com</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">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF">
                <p><tt>EKR,</tt><br>
                </p>
                <div>
                  <div class=3D"m_-7086147813399818777h5"> <br>
                    <div class=3D"m_-7086147813399818777m_-7821002768604845=
176moz-cite-prefix">On
                      2018-04-05 15:57, Eric Rescorla wrote:<br>
                    </div>
                    <blockquote type=3D"cite">
                      <div dir=3D"ltr"><br>
                        <div class=3D"gmail_extra"><br>
                          <div class=3D"gmail_quote">On Tue, Apr 3, 2018
                            at 11:46 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"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
                              <div bgcolor=3D"#FFFFFF">
                                <p>EKR,</p>
                                <p>thanks for your comments, responses
                                  inline<br>
                                </p>
                                <span class=3D"m_-7086147813399818777m_-782=
1002768604845176gmail-">
                                  <br>
                                  <div class=3D"m_-7086147813399818777m_-78=
21002768604845176gmail-m_-3709797337778756038moz-cite-prefix">On
                                    2018-04-03 00:54, Eric Rescorla
                                    wrote:<br>
                                  </div>
                                  <blockquote type=3D"cite">
                                    <pre>Eric Rescorla has entered the foll=
owing ballot position for
draft-ietf-mmusic-trickle-ice-<wbr>sip-14: Discuss

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


Please refer to <a class=3D"m_-7086147813399818777m_-7821002768604845176gma=
il-m_-3709797337778756038moz-txt-link-freetext" href=3D"https://www.ietf.or=
g/iesg/statement/discuss-criteria.html" target=3D"_blank">https://www.ietf.=
org/iesg/stat<wbr>ement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class=3D"m_-7086147813399818777m_-7821002768604845176gmail-m_-3709797337=
778756038moz-txt-link-freetext" href=3D"https://datatracker.ietf.org/doc/dr=
aft-ietf-mmusic-trickle-ice-sip/" target=3D"_blank">https://datatracker.iet=
f.org/d<wbr>oc/draft-ietf-mmusic-trickle-i<wbr>ce-sip/</a>



------------------------------<wbr>------------------------------<wbr>-----=
-----
DISCUSS:
------------------------------<wbr>------------------------------<wbr>-----=
-----

   the Offer (as would be the case when Half Trickle is performed or
   when new candidates have not been learned since then).
IMPORTANT: They must be in order, right?</pre>
                                  </blockquote>
                                </span> I&#39;m not sure what the issues is
                                here.<br>
                                The cited text addresses the first of
                                two cases, i.e. the case=C2=A0 where the IN=
FO
                                requests repeats <br>
                                =C2=A0the exact same set of candidates that
                                was already provided in the initial
                                offer. <br>
                                This could happen when <br>
                                a) Half Trickle is used (all candidate
                                were already in the initial offer) or<br>
                                b) Full Trickle is used where=C2=A0 the
                                offerer is currently gathering
                                additional candidates, but did not yet
                                get them.<br>
                                <br>
                                The second case (Full Trickle with
                                additional candidates already available)
                                is addressed in the subsequent
                                paragraph.<br>
                                .. and yes the candidates are sent in
                                the order as they were gathered.<span class=
=3D"m_-7086147813399818777m_-7821002768604845176gmail-"><br>
                                </span></div>
                            </blockquote>
                            <div><br>
                            </div>
                            <div>Right. I&#39;m saying you need to say that=
.</div>
                          </div>
                        </div>
                      </div>
                    </blockquote>
                  </div>
                </div>
                OK, will do<span><br>
                  <blockquote type=3D"cite">
                    <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-7086=
147813399818777m_-7821002768604845176gmail-">
                                <blockquote type=3D"cite">
                                  <pre>   &#39;application/trickle-ice-sdpf=
r<wbr>ag&#39; bodies do not interfere with the
   Offer/Answer procedures as specified in [RFC3264].
IMPORTANT: &quot;pseudo&quot; m=3D lines are not defined in 5888 so this is=
 very unclear.</pre>
                                </blockquote>
                              </span> 5888 is cited as it defines the
                              a=3Dmid: attribute that we used for
                              identifying the m-line to which a
                              candidate belongs.<br>
                              The a=3Dmid: attribute helps in case of
                              multiple m-lines, when we already have
                              gathered candidates <br>
                              for e.g. the first and fourth m-line, but
                              not for the 2nd and 3rd. <br>
                            </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>Right. You need to describe what a
                            pseudo-m=3D line is because it&#39;s not define=
d
                            anywhere.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> Well, we have this text in section 4.4 at the
                first occurrence of the term.<br>
                <br>
                <pre class=3D"m_-7086147813399818777m_-7821002768604845176n=
ewpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color=
:rgb(0,0,0);font-style:normal;font-variant-ligatures:normal;font-variant-ca=
ps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-inden=
t:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;te=
xt-decoration-color:initial">   &quot;... this is handled through the use o=
f pseudo &quot;m=3D&quot; lines=20
   and identification tags in &quot;a=3Dmid:&quot; attributes as defined in
   [<a href=3D"https://tools.ietf.org/html/rfc5888" title=3D"&quot;The Sess=
ion Description Protocol (SDP) Grouping Framework&quot;" target=3D"_blank">=
RFC5888</a>].  Pseudo &quot;m=3D&quot; lines follow the SDP syntax for &quo=
t;m=3D&quot; lines as
   defined in [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&qu=
ot;SDP: Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>],=
 but provide no semantics other than indicating
   to which &quot;m=3D&quot; line a candidate belongs. &quot;
</pre>
                <br>
                Isn&#39;t that good enough?<span><br>
                </span></div>
            </blockquote>
            <div><br>
            </div>
            <div>Not really. The way it reads is that pseudo m=3D lines
              are defines in 5888 but they&#39;re not. This is the</div>
            <div class=3D"gmail_quote">normative source of them. I would
              rephrase <br>
            </div>
            <div class=3D"gmail_quote">&quot;use of pseudo &quot;m=3D&quot;=
 lines, which
              follow the SDP syntax of...&quot; and then talk about mid in
              the next</div>
            <div class=3D"gmail_quote">sentence.</div>
          </div>
        </div>
      </div>
    </blockquote></div></div>
    I&#39;ll change to<br>
    <br>
    <pre class=3D"m_-7086147813399818777m_-7821002768604845176newpage" styl=
e=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);=
font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;fo=
nt-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-t=
ransform:none;word-spacing:0px;text-decoration-style:initial;text-decoratio=
n-color:initial">&quot;... this is handled through the use of pseudo &quot;=
m=3D&quot; lines.
    Pseudo &quot;m=3D&quot; lines follow the SDP syntax for &quot;m=3D&quot=
; lines as
   defined in [<a href=3D"https://tools.ietf.org/html/rfc4566" title=3D"&qu=
ot;SDP: Session Description Protocol&quot;" target=3D"_blank">RFC4566</a>],=
 but provide no semantics other than indicating
   to which &quot;m=3D&quot; line a candidate belongs.=20
   A pseudo  &quot;m=3D&quot; line is linked to the corresponding &quot;m=
=3D&quot; line in the=20
   SDP Offer or Answer via the identification tag in a &quot;a=3Dmid:&quot;=
 attribute as defined in [<a href=3D"https://tools.ietf.org/html/rfc5888" t=
itle=3D"&quot;The Session Description Protocol (SDP) Grouping Framework&quo=
t;" target=3D"_blank">RFC5888</a>].=20
&quot;


Kind Regards
Thomas

</pre><div><div class=3D"h5">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote"><br>
            <div class=3D"gmail_quote">-Ekr<br>
            </div>
            <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-7086147813399818=
777m_-7821002768604845176gmail-">
                    <blockquote type=3D"cite">
                      <pre>   sent under the same combination of &quot;a=3D=
ice-pwd:&quot; and &quot;a=3Dice-ufrag:&quot; in
   the same order as they were gathered.  In other words, the sequence
   of a previously sent list of candidates MUST NOT change in subsequent

IMPORTANT: This appears to conflict with the guidance in Section 6 of
the trickle document, which is about reordering candidates from how
they were gathered.</pre>
                    </blockquote>
                    <br>
                  </span> Do you mean section 7=C2=A0 which talks about
                  reordering candidate _pairs_ at the IE agents?<br>
                </div>
              </blockquote>
              <div><br>
              </div>
              <div>No. Section 16, sorry for the typo.</div>
            </div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div text=3D"#000000" bgcolor=3D"#FFFFFF"><span>
                  <blockquote type=3D"cite">
                    <div dir=3D"ltr">
                      <div class=3D"gmail_extra"> </div>
                    </div>
                  </blockquote>
                </span> Section 15? :-)<span><br>
                  <blockquote type=3D"cite">
                    <div dir=3D"ltr">
                      <div class=3D"gmail_extra">
                        <div class=3D"gmail_quote">
                          <div><br>
                          </div>
                          <div>=C2=A0=C2=A0 To achieve this, when trickling
                            candidates, agents MUST respect the<br>
                            =C2=A0=C2=A0 order in which the components and =
streams
                            appear (implicitly or<br>
                            =C2=A0=C2=A0 explicitly) as they have been nego=
tiated
                            by means of the relevant<br>
                            =C2=A0=C2=A0 candidate information.=C2=A0 There=
fore
                            candidates for a given component<br>
                            =C2=A0=C2=A0 MUST NOT be conveyed prior to cand=
idates
                            for a component with a lower<br>
                            =C2=A0=C2=A0 ID number within the same foundati=
on.=C2=A0 In
                            addition, candidates MUST<br>
                            =C2=A0=C2=A0 be paired, following the procedure=
s in
                            Section 8.1.1, in the same<br>
                            =C2=A0=C2=A0 order they are conveyed.<br>
                            <br>
                          </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"=
>
                            <div bgcolor=3D"#FFFFFF"> We=C2=A0 require that=
 the
                              ordering of the _candidates_ MUST not
                              change=C2=A0 <br>
                              when the candidates are sent several times
                              from one=C2=A0 ICE agent to its peer in
                              subsequent INFO requests.<br>
                            </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>The problem is the text &quot;same order the=
y
                            were gathered&quot; because the ICE trickle tex=
t</div>
                          <div>requires sending them in an order
                            different from when they were gathered.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> OK, now I see. I will clarify and refer to
                section 15 of draft-ice-trickle<span><br>
                  <blockquote type=3D"cite">
                    <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 bgcolor=3D"#FFFFFF"> I don&#39;t see a
                              conflict.<span class=3D"m_-708614781339981877=
7m_-7821002768604845176gmail-"><br>
                                <blockquote type=3D"cite">
                                  <pre>------------------------------<wbr>-=
-----------------------------<wbr>----------
COMMENT:
------------------------------<wbr>------------------------------<wbr>-----=
-----

  SIP message.  At the remote agent the gathering procedure is repeated
   and candidates are sent to the first agent.  Finally, a third phase
   starts where connectivity between all candidates in both sets is

This suggests that they have to happen in sequence, but that&#39;s not true=
.

   include in each &quot;m=3D&quot;-line a &quot;a=3Dmid:&quot; attribute i=
n accordance to
   [RFC5888].

Why is this required?</pre>
                                </blockquote>
                              </span> As above, the a=3Dmid: attribute
                              helps in case of multiple m-lines, when we
                              already have gathered candidates <br>
                              for e.g. the first and fourth m-line, but
                              not for the 2nd and 3rd. </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>Right. You need to actually explain this.</d=
iv>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> I&#39;ll do<span><br>
                  <blockquote type=3D"cite">
                    <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-7086=
147813399818777m_-7821002768604845176gmail-">
                                <blockquote type=3D"cite">
                                  <pre>   section 8.1.1 of [I-D.ietf-mmusic=
-ice-sip-sdp] except that an Answer
   is not yet provided.

Can you explain why you cease retransmitting on receiving INFO? I assume
because it&#39;s an implicit ACK of your INFO?</pre>
                                </blockquote>
                              </span> The INFO is an ACK that an early
                              dialog is now established, such that INFOs
                              can be send in the reverse direction as
                              well.<span class=3D"m_-7086147813399818777m_-=
7821002768604845176gmail-"><br>
                              </span></div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>It would be helpful to explain this as
                            well. I defer to the ART ADs on the
                            suitability of this technique.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> I&#39;ll do <span>
                  <blockquote type=3D"cite">
                    <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 bgcolor=3D"#FFFFFF"><span class=3D"m_-7086=
147813399818777m_-7821002768604845176gmail-">
                                <blockquote type=3D"cite">
                                  <pre>   m=3Dlines that they pertain to.  =
The correspondence can be made via the
   &quot;a=3Dmid:&quot; attributes.

This whole section needs to be rewritten to make clear what&#39;s going on:

    candidates are grouped in sections headed by &quot;pseudo&quot; m=3Dlin=
es
    These sections contain a=3Dmid values which point back to the true m=3D=
line.
</pre>
                                </blockquote>
                              </span> Would it be sufficient to rephrase
                              as follows?<br>
                              <pre class=3D"m_-7086147813399818777m_-782100=
2768604845176gmail-m_-3709797337778756038newpage" style=3D"font-size:13.333=
3px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-style:normal;fon=
t-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-=
spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-sp=
acing:0px;text-decoration-style:initial;text-decoration-color:initial">Note=
, that there is no requirement that the Info request body
   contains as many pseudo m=3D lines as the Offer/Answer contains m=3D
   lines, nor that the pseudo m=3D lines be in the same order as the
   m=3Dlines that they pertain to.  The correspondence can be made via the
   &quot;a=3Dmid:&quot; attributes since candidates are grouped in sections=
 headed by &quot;pseudo&quot; m=3Dlines.
    These sections contain a=3Dmid: attribute values which point back to th=
e true m=3Dline.</pre>
                            </div>
                          </blockquote>
                          <div><br>
                          </div>
                          <div>Sure.</div>
                        </div>
                      </div>
                    </div>
                  </blockquote>
                </span> Thanks <br>
                <span class=3D"m_-7086147813399818777HOEnZb"><font color=3D=
"#888888"> Thomas<br>
                    <br>
                  </font></span></div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

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

--00000000000096c00e05695d8e39--


From nobody Mon Apr  9 07:52:41 2018
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 3E4391270AE for <mmusic@ietfa.amsl.com>; Mon,  9 Apr 2018 07:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLqNV5-p2mqJ for <mmusic@ietfa.amsl.com>; Mon,  9 Apr 2018 07:52:37 -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 3C524126C25 for <mmusic@ietf.org>; Mon,  9 Apr 2018 07:52:37 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=pnKvTPU2sP704MeWLS9fiX0Vr/Tp4GdEqpA4FQakBGTyczp3gTQJNQACpAXJKmIjQByJtb554IlHChuuDXRGG4l8LCiwCVoTVug1Bv8eFTNpkELa4LozvavQwB0HrQiS+BTxmPSIPWJAWcJo9TTmd/N17lkssdbhzMTFXJinMVE=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 29165 invoked from network); 9 Apr 2018 16:51:35 +0200
Received: from 108-227-160-179.lightspeed.sntcca.sbcglobal.net (HELO ?172.31.99.149?) (108.227.160.179) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 9 Apr 2018 16:51:34 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <6ce0a44f-cca8-2105-73f5-75689dd8c611@gmail.com>
Date: Mon, 9 Apr 2018 07:51:29 -0700
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B194210D-FEE7-4581-A03A-581A26920BAC@kuehlewind.net>
References: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com> <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com> <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net> <6ce0a44f-cca8-2105-73f5-75689dd8c611@gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
X-PPP-Message-ID: <20180409145135.29156.27926@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hxGBU8d7qTL0dMSMCihdjgP0fbE>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 09 Apr 2018 14:52:40 -0000

Hi Thomas,

see below.

> Am 08.04.2018 um 11:57 schrieb Thomas Stach <thomass.stach@gmail.com>:
>=20
> Mirja,
>=20
> On 2018-04-05 16:19, Mirja Kuehlewind (IETF) wrote:
>> Hi Thomas,
>>=20
>>> Am 04.04.2018 um 21:54 schrieb Thomas Stach =
<thomass.stach@gmail.com>:
>>>=20
>>> Mirja,
>>>=20
>>> thanks for your comments.
>>>=20
>>> On 2018-04-03 16:37, Mirja K=C3=BChlewind wrote:
>>>> Mirja K=C3=BChlewind has entered the following ballot position for
>>>> draft-ietf-mmusic-trickle-ice-sip-14: Discuss
>>>>=20
>>>> When responding, please keep the subject line intact and reply to =
all
>>>> email addresses included in the To and CC lines. (Feel free to cut =
this
>>>> introductory paragraph, however.)
>>>>=20
>>>>=20
>>>> Please refer to
>>>> https://www.ietf.org/iesg/statement/discuss-criteria.html
>>>>=20
>>>> for more information about IESG DISCUSS and COMMENT positions.
>>>>=20
>>>>=20
>>>> The document, along with other ballot positions, can be found here:
>>>>=20
>>>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> =
----------------------------------------------------------------------
>>>> DISCUSS:
>>>> =
----------------------------------------------------------------------
>>>>=20
>>>> Thanks for the well-written doc and the quick response to the =
initial tsv
>>>> review. Also thanks to J=C3=B6rg for the thorough and very helpful =
review!
>>>>=20
>>>> As flagged by the tsv review, there can be an issue with the =
aggregation of
>>>> candidates in one INFO message when rate limited and the path =
MTU/UPD
>>>> fragmentation. While this is a small point only and I'm sure it can =
be easily
>>>> addressed, it important enough that I decided to put a discuss in. =
I'm sure
>>>> this can be resolved quickly as well.
>>>>=20
>>> As large messages are already addressed in RFC 3261, I could add =
something like
>>> "As a potentially large number of candidates are aggregated in a =
INFO request,
>>> the message size can easily exceed the path MTU. SIP [RF3261] =
requires that if a request
>>> is within 200 bytes of the path MTU, or if it is larger than 1300 =
bytes and the path MTU is unknown,
>>> that the request is sent using an RFC 2914 [43] congestion =
controlled transport protocol,
>>> such as TCP.
>> The only point is the interaction with the rate limit here. If you =
have to split up into two/multiple messages, you will not be able to =
send both immediately but have to wait for another interval. Maybe that =
can be further clarified with an additional sentence.
> Well, as SIP already prohibits fragmenting a packet that that is =
larger than 1300 bytes, do we need to say something about the rate of =
for sending such "illegal" packets?

Sorry, yes that is fine. Didn=E2=80=99t read your earlier reply =
correctly.=20

>=20
>>=20
>>> "
>>>> Also if the document could give further guidance on an acceptable =
maximum for
>>>> the rate of INFO requests that be even better!
>>>>=20
>>> Adam proposed in his review to
>>>=20
>>> "... require some minimum quarantine period between INFO requests =
(probably something in the range of 20 ms),
>>> during which any new candidates that are gathered are aggregated =
into the next INFO message."
>>>=20
>>> Would that be enough of a guidance?
>> Yes, that would be good! Usually we recommends something like one =
message per RTT. So probably 100ms or 200ms would be on the safe side =
but lower might be fine as well if the typically deployment scenario =
assumes a shorter RTT.
>=20
>  I propose to add a 3rd paragraph to section 10.9
>=20
> "As a potentially large number of candidates are aggregated in an INFO =
request,
> the message size can easily exceed the path MTU. SIP [RF3261] requires =
that if a request
> is within 200 bytes of the path MTU, or if it is larger than 1300 =
bytes and the path MTU is unknown,
> that the request is sent using an RFC 2914 [43] congestion controlled =
transport protocol,
> such as TCP.
> In general, it is RECOMMENDED that a Trickle ICE Agent sends only one =
INFO request per RTT.
> A quarantine period of 100ms would be on the safe side, but lower =
values might be fine as well
> if the typically deployment scenario assumes a shorter RT.=E2=80=9C

Thanks! Please update and I=E2=80=99ll clear!

Mirja


>=20
> Kind Regards
> Thomas
>=20
> <\snip>
>=20


From nobody Tue Apr 10 06:10:41 2018
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 D54121201FA; Tue, 10 Apr 2018 06:10: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>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152336583382.13368.4074585194543598103@ietfa.amsl.com>
Date: Tue, 10 Apr 2018 06:10:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9EAdidWXA3okUKp-1ZkUnKIkXl4>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-simulcast-12.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 10 Apr 2018 13:10:34 -0000

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

        Title           : Using Simulcast in SDP and RTP Sessions
        Authors         : Bo Burman
                          Magnus Westerlund
                          Suhas Nandakumar
                          Mo Zanaty
	Filename        : draft-ietf-mmusic-sdp-simulcast-12.txt
	Pages           : 40
	Date            : 2018-04-10

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 are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-12
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-simulcast-12

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


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 Apr 10 06:11:17 2018
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 9D38E1275FD for <mmusic@ietfa.amsl.com>; Tue, 10 Apr 2018 06:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uMVJ3gnoeHU0 for <mmusic@ietfa.amsl.com>; Tue, 10 Apr 2018 06:11:15 -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 B6C6C127241 for <mmusic@ietf.org>; Tue, 10 Apr 2018 06:11:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523365872; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=o9zQDm1jInDLPGYIVKcD0IHaORkwgdgXGeifZB5dz5E=; b=FsiSh4A6gssWzYP2xou4wj8gecAMXhVuJnIfbjfV0CcZ/2KB633iY2n6o5aEQtlR UsCR/dl7aiAy5c3IL5sPaK7JIvyFZvtw9YMi1Rfd3ezsBumzPBXS/6YbqejWfi+G mmJ3fj46+9huRuRCWQ3jefj1EcS5xUDm9QwlcztCfa0=;
X-AuditID: c1b4fb3a-e39ff70000005d56-3c-5accb7f07a84
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 7E.F3.23894.0F7BCCA5; Tue, 10 Apr 2018 15:11:12 +0200 (CEST)
Received: from [100.94.35.108] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.54) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 10 Apr 2018 15:11:12 +0200
To: Ben Campbell <ben@nostrum.com>
CC: <draft-ietf-mmusic-sdp-simulcast.all@ietf.org>, IETF MMUSIC WG <mmusic@ietf.org>
References: <2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com> <deb45e70-d5a8-e75e-225d-a3e8375d91f0@ericsson.com> <90EA95CC-E673-41CB-BA5B-362D2E668B41@nostrum.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <418fa4a1-ce5f-762d-564b-bf474e8b7fb8@ericsson.com>
Date: Tue, 10 Apr 2018 15:11:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <90EA95CC-E673-41CB-BA5B-362D2E668B41@nostrum.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrLLMWRmVeSWpSXmKPExsUyM2K7me6H7WeiDM5v0LOY33ma3eL3+2KL qcsfszgweyxZ8pPJY9bOJywBTFFcNimpOZllqUX6dglcGW8evWMvmKNYcWvBL5YGxk7pLkYO DgkBE4mPx126GLk4hASOMEpsX7ySBcLZxCjR8fghkMPJISzgIPGkazsziC0ioCTxvHkrWJxZ IEzi5KzZ7BANKxklJl25CJZgE7CQuPmjkQ3E5hWwl3i66QojiM0ioCpx9GgzO4gtKhAj8eNo FwtEjaDEyZlPwGxOoPpvl46xQiywkJg5/zwjhC0v0bx1NjOELS7R9GUlWI2QgLZEQ1MHmC0B dNz1eddZJjAKzUIydhaSUbOQjJqFZNQCRpZVjKLFqcXFuelGRnqpRZnJxcX5eXp5qSWbGIGB fnDLb6sdjAefOx5iFOBgVOLhfb3gTJQQa2JZcWXuIUYJDmYlEd6ctUAh3pTEyqrUovz4otKc 1OJDjNIcLErivE5pFlFCAumJJanZqakFqUUwWSYOTqkGxnWx3nyLXC7ONcio9V1ufY3DL+Zx 0wX7xz/sJ3wx4Vx+T4RN6uXuVVH9a71+8pUly2v5Lnxx0J+l5ZbbwbfTyzNePHnHZbn9ivzH CDML34ULMxIFN++pe1o5U8i56QXjNPPTeyZPrBC+JiIj/ZHv2gX5zeHLnQ7pc+X4FlUFJDnL MT4VXtEwWYmlOCPRUIu5qDgRANgt045wAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/s2nXhuqmwBnEfFcHxwrpncbCPSI>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 10 Apr 2018 13:11:16 -0000

Hi,

Removing down to the items requiring response. I will now submit a 
version as I don't see any additional outstanding changes. I hope my 
explantation of the design choice to forbid multiple simulcast streams 
using the same rid-id for a particular media source.


Den 2018-04-09 kl. 22:32, skrev Ben Campbell:
> Thanks for the response. My followup comments are also inline. I removed sections that do not seem to need further discussion.
>
> Ben.
>
>> On Apr 6, 2018, at 4:43 AM, Magnus Westerlund <magnus.westerlund@ericsson.com> wrote:
>>
>>
>>> — " Note that this does not eliminate use of simulcast as an RTP duplication mechanism, since it is possible to define multiple different rid-id that are effectively equivalent.”
>>>
>>> Didn’t the first part of the paragraph say (or at least imply) that you SHOULD NOT do that?
>>>
>> Well, we recommend that one uses duplication if that is the user's only intention. However, the sentence in between forbids one to re-use the same RID ID twice to indicate duplication. It is in that context that we note that duplication could be achieved despite that restriction by defining multiple RID ID with the same semantic definition.
>>
>> And if one actually likes to have duplication and some variant then I think it may actually be reasonable to use simulcast for both, rather than requiring an additional mechanism. So, I have a preference for leaving it there.
> Why do literally identical  rid-ids cause complications for this, but semantically identical ones do not?

There are several reasons here, addressing various different cases. So 
there are some cases where it would not be an issue, but it is in 
others. Thus, we agreed when doing the design that it would be simplest 
to disallow identical rid-ids to be reused.

The first one has to with identification of a particular simulcast 
stream for a media source. If they would re-use the rid-id, on the RTP 
level we would have two RTP streams with different SSRCs, but otherwise 
be identical in MID, rid-id. Thus, there are no real identification 
between the simulcast layer and the RTP stream level for which 
duplicated stream one changes. Thus, with pause or renegotiation there 
could be confusion about with of the RTP streams will be affected.

Secondly, when dealing with legacy receivers using PT mapping this type 
can't be done, as each simulcast stream needs an unique pt and thus 
individual rid-id also.

So thus we took the decision that not allowing multiple simulcast 
streams with identical rid-ids was simpler, and would eliminate some 
complexities from the implementations.
>> Better?
>>> — 10th paragraph: The first sentence is hard to parse.
>> I agree that this sentence is hard:
>>
>> Including an initially paused simulcast stream in "recv" direction for the part sending the SDP, sent towards an RTP sender, SHOULD cause the remote RTP sender to put the stream as unsolicited locally paused, unless there are other RTP stream receivers that do not mark the simulcast stream as initially paused.
>>
>> Is this reworded sentence better?
>>
>> If the endpoint sending the SDP includes an "recv" direction simulcast stream that is initially paused, then the remote RTP sender receiving the SDP SHOULD put its RTP stream in a unsolicited locally paused state. This unless there are there are other RTP stream receivers that do not mark the simulcast stream as initially paused.
> Would it make sense to replace the last sentence with “However, this does not apply if there are other RTP stream receivers that do not mark the simulcast stream as initially paused.” ?

Yes, I think this is clear that there is an exception to this.

I will incorporate this change.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue Apr 10 06:22:43 2018
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 D76D7127241 for <mmusic@ietfa.amsl.com>; Tue, 10 Apr 2018 06:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8c00blVOS3ZJ for <mmusic@ietfa.amsl.com>; Tue, 10 Apr 2018 06:22: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 C175C126DC2 for <mmusic@ietf.org>; Tue, 10 Apr 2018 06:22:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523366558; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=qFFtDAKWqp3g2phwr9D3vSP9tZLw4ACRCncQdNXhOHE=; b=dH9GLPMLwfqcJBguwg3OfrrVgAPqFy6Htz3Hx5CqfmYlv/t1LsgaMM3cFTfZ0G/n wbu3FoJ1nvYLU6+VOvEwFTiU01xrpYLRDIDRxt7P21keFQ8oRbhQOGelsHI7arGm twN/w/MdA7FUZnhTtJWS2n1YeacyrHYSMHYA3vhfg1g=;
X-AuditID: c1b4fb2d-e31ff700000073d9-f6-5accba9dfb79
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 1B.CE.29657.D9ABCCA5; Tue, 10 Apr 2018 15:22:38 +0200 (CEST)
Received: from [100.94.35.108] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.24) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 10 Apr 2018 15:22:37 +0200
To: IETF MMUSIC WG <mmusic@ietf.org>
References: <152336583382.13368.4074585194543598103@ietfa.amsl.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <cab65868-9b05-a71e-98d5-8c9b843751da@ericsson.com>
Date: Tue, 10 Apr 2018 15:22:37 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <152336583382.13368.4074585194543598103@ietfa.amsl.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM2K7hO68XWeiDH7+Z7eYuvwxiwOjx5Il P5kCGKO4bFJSczLLUov07RK4Mm58OstcsFi6YnPrdrYGxp2iXYycHBICJhKbpl5i7GLk4hAS OMIocfHNBFYIZxOjxJXZl1hBqoQF7CUed5xjBrFFBFQk/r17wAZiCwk4S9y5tIYJxGYTsJC4 +aMRLM4LVP+/sZ8dxGYRUJVY+nwqWK+oQIzEj6NdLBA1ghInZz4BszkFXCTe738IdAUHBzNQ 74OtZSBhZgF5ieats5khbHGJpi8rWSHWaks0NHWwQjygJHF93nWWCYyCs5BMnYUwaRaSSbOQ TFrAyLKKUbQ4tbg4N93IWC+1KDO5uDg/Ty8vtWQTIzBgD275rbuDcfVrx0OMAhyMSjy8P3ee iRJiTSwrrsw9xCjBwawkwpuzFijEm5JYWZValB9fVJqTWnyIUZqDRUmcV2/VnighgfTEktTs 1NSC1CKYLBMHp1QDo7hb3ALpmBeneF0c1G+47FlQnumz+/jar/9/Oalc/vn/vWHwPkFJ1XNV ea+2X2mekmVuK+i1cZpbnUOI3P6ofrUOuw3bj1UZ97n1sxQfdOS4eIkryCcqxrjcU7cs9mKv SeuVvxWsTOmXTxpV3332rEnwVY2P5sfYlq65mX12dcn+yQ3Gb88psRRnJBpqMRcVJwIAMIdv h1QCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ssh1DGppYfxI9rryhI5jCeOAzZ0>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-simulcast-12.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 10 Apr 2018 13:22:42 -0000

Hi,

This version addresses the AD review issues raised. The changes are 
basically the below ones. But please review the diff:

https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-simulcast-12

B.1.  Modifications Between WG Version -11 and -12

    o  Modified Normative statement regarding RTP stream duplication in
       Section 5.2.

    o  Clarified assumption about use of congestion control by
       applications.

    o  Changed to use RFC 8174 boilerplate instead of RFC 2119.

    o  Clarified explanation of syntax for simulcast attribute in
       Section 4.

    o  Editorial clarification in Section 5.2 and 5.3.2.

    o  Various minor editorials and nits.


Den 2018-04-10 kl. 15:10, skrev internet-drafts@ietf.org:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.
>
>          Title           : Using Simulcast in SDP and RTP Sessions
>          Authors         : Bo Burman
>                            Magnus Westerlund
>                            Suhas Nandakumar
>                            Mo Zanaty
> 	Filename        : draft-ietf-mmusic-sdp-simulcast-12.txt
> 	Pages           : 40
> 	Date            : 2018-04-10
>
> 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 are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-12
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-simulcast-12
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-simulcast-12
>
>
> 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

-- 

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue Apr 10 08:19:00 2018
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 4A23712D88F; Tue, 10 Apr 2018 08:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DGjK9rN4AHbm; Tue, 10 Apr 2018 08:18:55 -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 60EB112D95E; Tue, 10 Apr 2018 08:18:55 -0700 (PDT)
Received: from [10.0.1.91] (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 w3AFIovv035786 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 10 Apr 2018 10:18:51 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <C3F62C1B-E5EB-430C-8DA9-EE0B8CB38161@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_74ADB225-A317-4027-8C6D-01F6F227DBDF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 10 Apr 2018 10:18:49 -0500
In-Reply-To: <418fa4a1-ce5f-762d-564b-bf474e8b7fb8@ericsson.com>
Cc: draft-ietf-mmusic-sdp-simulcast.all@ietf.org, IETF MMUSIC WG <mmusic@ietf.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <2D6D4BF2-30E1-48A9-BC9C-9AB1AB3C39EA@nostrum.com> <deb45e70-d5a8-e75e-225d-a3e8375d91f0@ericsson.com> <90EA95CC-E673-41CB-BA5B-362D2E668B41@nostrum.com> <418fa4a1-ce5f-762d-564b-bf474e8b7fb8@ericsson.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jhI6i2fRfPDfk42fUYn29AE4soM>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-simulcast-11
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 10 Apr 2018 15:18:57 -0000

--Apple-Mail=_74ADB225-A317-4027-8C6D-01F6F227DBDF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This looks good. I=E2=80=99ve requested IETF last call.

Thanks!

Ben.

> On Apr 10, 2018, at 8:11 AM, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
>=20
> Hi,
>=20
> Removing down to the items requiring response. I will now submit a =
version as I don't see any additional outstanding changes. I hope my =
explantation of the design choice to forbid multiple simulcast streams =
using the same rid-id for a particular media source.
>=20
>=20
> Den 2018-04-09 kl. 22:32, skrev Ben Campbell:
>> Thanks for the response. My followup comments are also inline. I =
removed sections that do not seem to need further discussion.
>>=20
>> Ben.
>>=20
>>> On Apr 6, 2018, at 4:43 AM, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
>>>=20
>>>=20
>>>> =E2=80=94 " Note that this does not eliminate use of simulcast as =
an RTP duplication mechanism, since it is possible to define multiple =
different rid-id that are effectively equivalent.=E2=80=9D
>>>>=20
>>>> Didn=E2=80=99t the first part of the paragraph say (or at least =
imply) that you SHOULD NOT do that?
>>>>=20
>>> Well, we recommend that one uses duplication if that is the user's =
only intention. However, the sentence in between forbids one to re-use =
the same RID ID twice to indicate duplication. It is in that context =
that we note that duplication could be achieved despite that restriction =
by defining multiple RID ID with the same semantic definition.
>>>=20
>>> And if one actually likes to have duplication and some variant then =
I think it may actually be reasonable to use simulcast for both, rather =
than requiring an additional mechanism. So, I have a preference for =
leaving it there.
>> Why do literally identical  rid-ids cause complications for this, but =
semantically identical ones do not?
>=20
> There are several reasons here, addressing various different cases. So =
there are some cases where it would not be an issue, but it is in =
others. Thus, we agreed when doing the design that it would be simplest =
to disallow identical rid-ids to be reused.
>=20
> The first one has to with identification of a particular simulcast =
stream for a media source. If they would re-use the rid-id, on the RTP =
level we would have two RTP streams with different SSRCs, but otherwise =
be identical in MID, rid-id. Thus, there are no real identification =
between the simulcast layer and the RTP stream level for which =
duplicated stream one changes. Thus, with pause or renegotiation there =
could be confusion about with of the RTP streams will be affected.
>=20
> Secondly, when dealing with legacy receivers using PT mapping this =
type can't be done, as each simulcast stream needs an unique pt and thus =
individual rid-id also.
>=20
> So thus we took the decision that not allowing multiple simulcast =
streams with identical rid-ids was simpler, and would eliminate some =
complexities from the implementations.
>>> Better?
>>>> =E2=80=94 10th paragraph: The first sentence is hard to parse.
>>> I agree that this sentence is hard:
>>>=20
>>> Including an initially paused simulcast stream in "recv" direction =
for the part sending the SDP, sent towards an RTP sender, SHOULD cause =
the remote RTP sender to put the stream as unsolicited locally paused, =
unless there are other RTP stream receivers that do not mark the =
simulcast stream as initially paused.
>>>=20
>>> Is this reworded sentence better?
>>>=20
>>> If the endpoint sending the SDP includes an "recv" direction =
simulcast stream that is initially paused, then the remote RTP sender =
receiving the SDP SHOULD put its RTP stream in a unsolicited locally =
paused state. This unless there are there are other RTP stream receivers =
that do not mark the simulcast stream as initially paused.
>> Would it make sense to replace the last sentence with =E2=80=9CHowever,=
 this does not apply if there are other RTP stream receivers that do not =
mark the simulcast stream as initially paused.=E2=80=9D ?
>=20
> Yes, I think this is clear that there is an exception to this.
>=20
> I will incorporate this change.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Network Architecture & Protocols, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Torshamnsgatan 23           | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20


--Apple-Mail=_74ADB225-A317-4027-8C6D-01F6F227DBDF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrM1dkACgkQgFZKbJXz
1A0/2hAAjoo04x48/uMymBLs92gMLob3uC8/BvAFZ5JuA6qx6dZRCaEUEtP+yf3Q
qVGWMx5QsyUL2g0rsaX9WJ6doDvhSzZEHLm+bP9wVtQ5E9C6z5zXE2tzPrAcRb8l
xhZ1UUbGWcABeXdXSG6+GQdJ8K19R4jwnjAbQOOebEO6f124iXyT7eQOnlp+USES
IN+LVFrZWKUAfE1VylIgkQKcMG95Bj9UfBQdB6DSzH5DWM4lHLImJwKV0UNOosQR
hW+RMXM1hDvF8v2e/3GBtlmXu/LmmED+FEhDVI4jejGQECGRofI8BsLuVbKA1OyL
jKVSTfYZt/NsZm82oS5aGnESpItV5vyLiQFubPYGSIbVcrtUUlV9JKMKxX8tHtzh
1YL0fe1H58hZwI8G1B39Un/QsTUamO5pHKT+HLuoV94e5S0c757nDQHY+/sc9L78
hQ6vSyN8UVEiL95dLj35LLv11JqK0R3zrPQFoCpwC+TBcLOVFc3vByN9TMsvmzpI
JV9tY3S0+Dfr4DY4oLtBSB/T6hrgbWI0wE91pwaecLOTlEC7qpwJqGIdSEeUp3k8
w5M6K43v5dIwYPGtkjVLTqYrCaeNrcL837oUxKy8biFz/N0Wj/8dQDp7Fvs1sy0G
VqxTAxxa8DKHocu30vnQkLcxB0rPgQ9y9cjJg1if02VbMYidNaM=
=w0jC
-----END PGP SIGNATURE-----

--Apple-Mail=_74ADB225-A317-4027-8C6D-01F6F227DBDF--


From nobody Tue Apr 10 09:26:23 2018
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA63212D0C3; Tue, 10 Apr 2018 09:26:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.77.1
Auto-Submitted: auto-generated
Precedence: bulk
CC: fandreas@cisco.com, ben@nostrum.com, mmusic-chairs@ietf.org, mmusic@ietf.org, draft-ietf-mmusic-sdp-simulcast@ietf.org
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <152337758091.13384.13736000252835511497.idtracker@ietfa.amsl.com>
Date: Tue, 10 Apr 2018 09:26:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LTz3poG--qLPRyYJeqF1GiduzKA>
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-sdp-simulcast-12.txt> (Using Simulcast in SDP and RTP Sessions) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 10 Apr 2018 16:26:21 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'Using Simulcast in
SDP and RTP Sessions'
  <draft-ietf-mmusic-sdp-simulcast-12.txt> as Proposed Standard

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

Abstract


   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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-simulcast/

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

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/2536/






From nobody Fri Apr 13 05:07:17 2018
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 C09261242F5 for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 05:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9BurFxNzIou for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 05:07:09 -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 C22CF128896 for <mmusic@ietf.org>; Fri, 13 Apr 2018 05:07:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523621223; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ijw5WuhwTwdfyf9+Zs5LNTOBuD0ezql6RgZDXYsrhAk=; b=RwqnIzke8zowsjX1UTTlUCox2M1R/k3vnll7SqZUlB38bcH3TL/fhtJDjDKSyAXo /ggbNw2iKYplZkm/KLsIs+WuUd2O7SXM/FQUdVRcSHFpC4PUCotdF++ftTm6Xx+w s9a7KZKuo3T/48zdKZ/QRLklt9BWF9Lllyh7KouewKk=;
X-AuditID: c1b4fb2d-1f6969c0000073d9-6e-5ad09d67121b
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 49.CC.29657.76D90DA5; Fri, 13 Apr 2018 14:07:03 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0382.000; Fri, 13 Apr 2018 14:06:53 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Peter Saint-Andre <stpeter@mozilla.com>
CC: Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAABSyAgAABrACAAA6TAIAAAI6AgAAWLYCAAUXTgIAAFRIAgA3/bYA=
Date: Fri, 13 Apr 2018 12:06:52 +0000
Message-ID: <D6F67849.2DED5%christer.holmberg@ericsson.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com>
In-Reply-To: <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4B39094A9B29F742988D260CF0620309@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDIsWRmVeSWpSXmKPExsUyM2J7iG763AtRBv3b5C32/F3EbjG/8zS7 xY+1y5kt3l/Qtfh2odZixp+JzBbnd65nspi6/DGLxdp/7ewWz1aeYrTYObeD2YHbY8rvjawe O2fdZfdYsuQnk0ffgS5Wj1k7n7AEsEZx2aSk5mSWpRbp2yVwZWx7/oK9YCl/xfzP/UwNjLN5 uhg5OSQETCQWT5jM3sXIxSEkcIRR4uyp02wQzhJGifMTZjF3MXJwsAlYSHT/0wZpEBHwlpjZ 8hGshlmglVni7YQbbCAJYYECiZ69+1kgigol1u54BFYkItDFKDFl3RSwIhYBVYmz9/8yg9i8 AtYS7Qf+sUJsO8Qu8fr6QVaQBKeAvcTDyS/ZQWxGATGJ76fWMIHYzALiEreezGeCuFtAYsme 88wQtqjEy8f/wHpFBfQkNpy4zQ5ytYSAksTtDU4QrXoSN6ZC3MAMtLf75UZ2CFtbYtnC11D3 CEqcnPmEZQKj+Cwk22YhaZ+FpH0WkvZZSNoXMLKuYhQtTi0uzk03MtZLLcpMLi7Oz9PLSy3Z xAiM84NbfuvuYFz92vEQowAHoxIP7+qaC1FCrIllxZW5hxglOJiVRHhvFgCFeFMSK6tSi/Lj i0pzUosPMUpzsCiJ8+qt2hMlJJCeWJKanZpakFoEk2Xi4JRqYKwwXPL3g8CpCMGgkk07o6Ks SvkqZL0+ZNwsvlO3cMWBd0pS5sFXD/RVql27FbO9/+LyTja17COFu0VOm7Et6Shd4vh+SuKM 1E1iRz5t7ko66CLNGaXMffenzOopxzO4whfneJo9DPteKhrm9aPgW2PY9E9+MREpFtnHYoLN NopsZefct7bLV4mlOCPRUIu5qDgRACma4wfvAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/l6658r4PLosfq-z5CbdCF5FJiik>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 12:07:11 -0000

Hi,

>>On Apr 4, 2018, at 11:07 AM, Peter Saint-Andre <stpeter@mozilla.com>
>>wrote:
>>=20
>> On 4/3/18 2:41 PM, Suhas Nandakumar wrote:
>>>=20
>>>=20
>>> On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com
>>> <mailto:ben@nostrum.com>> wrote:
>>>=20
>>>=20
>>>=20
>>>> On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com
>>>><mailto:stpeter@mozilla.com>> wrote:
>>>>=20
>>>> On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
>>>>> Just to complete, ice-bis doesn=B9t normatively reference ice-sip-SDP
>>>>> draft when it moved to using =B3usages =B3 indirections for signaling
>>>>>protocols.
>>>>>=20
>>>>>=20
>>>>> Trickle ice can use similar approach and refer to trickle-sip as
>>>>>usage
>>>>> for trickle.
>>>>=20
>>>> It already does. That's why we pulled all the SDP/SIP stuff out of
>>>> draft-ietf-ice-trickle.
>>>=20
>>>    I assume Suhas meant separating the SDP stuff from the SIP stuff. (I
>>>    also assume he will correct me if I am wrong.)
>>>=20
>>>=20
>>> That's right Ben .. I was just thinking minimal localized changes (thus
>>> small time to get new draft done) and then asking trickle, trickle-sip
>>>to
>>> refer to the new one. (work done to refer is much smaller for these
>>> drafts that are at the very end of approval journey)
>>>=20
>>> I do agree with Adam, no matter what version of the proposal we pick,
>>> there is some work that needs to be done and we
>>> should do it.
>>=20
>> These documents are on the telechat tomorrow. Are we proposing to delay
>> consideration by the IESG while we get this mess sorted out? ;-)
>
>Hi Peter,
>
>I currently plan to leave it on. We may discuss a way forward on the
>telechat. Also, I=B9d like to get feedback on the rest of the draft(s) fro=
m
>the other ADs sooner than later.

Did you discuss this at the telechat?

Any other discussions on how to move forward with this?

Regards,

Christer



From nobody Fri Apr 13 05:30:59 2018
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 06CCE127078 for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 05:30:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.331
X-Spam-Level: 
X-Spam-Status: No, score=-4.331 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VCWp2kYQuBjI for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 05:30:56 -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 4EFFD12420B for <mmusic@ietf.org>; Fri, 13 Apr 2018 05:30:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523622654; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=z/60U4qOFEBPbA5G65j0IGId6ItPZowmqlfxBroZ6M8=; b=fvTgqFONqiESm/qSNSk2ZY3kyeywMmrvZ+ujrOYhFGzk5GVCnryCetkQygHCetIG y0M+LDqcUljPKFe7Hqfw9AiJY6z2kqJVI30B5g5N5haNn2S0ddGYRY0qb+49DUoL 6Yfc/jdppcW7tCsgDItjrF86qEFYgCr+HPYXHaoI1mQ=;
X-AuditID: c1b4fb25-5a75a9c00000522b-7e-5ad0a2fe4d4c
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id AC.6E.21035.EF2A0DA5; Fri, 13 Apr 2018 14:30:54 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0382.000; Fri, 13 Apr 2018 14:30:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: trickle-ice-sip: Usage of PRACK instead of INFO?
Thread-Index: AQHT0yNDysD30rqVpkOhHdNW/3gL1g==
Date: Fri, 13 Apr 2018 12:30:52 +0000
Message-ID: <D6F67E18.2DEF8%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CF50D1F253FAB34F84947AB21115BFC3@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7h+6/RReiDOYclraYuvwxiwOjx5Il P5kCGKO4bFJSczLLUov07RK4Mh7O2sJecJez4vdnlgbGu+xdjBwcEgImEs3HEroYuTiEBI4w Suz5N50JwlnCKPFh4UNmkCI2AQuJ7n/aXYycHCIC6hJf9/Ywg9jCApYS776eZIOI20lc+nab EcLWk9h57AoTiM0ioCqx/PdJsDivgLXE6psbwOoZBcQkvp9aA1bDLCAucevJfDBbQkBAYsme 88wQtqjEy8f/WEFsUaCZG07chrpZSeL2BieIVh2JBbs/sUHY1hKr1kxhhLC1JZYtfM0MsVZQ 4uTMJywTGEVmIdk2C0n7LCTts5C0z0LSvoCRdRWjaHFqcVJuupGxXmpRZnJxcX6eXl5qySZG YDQc3PJbdQfj5TeOhxgFOBiVeHhn112IEmJNLCuuzD3EKMHBrCTC+28+UIg3JbGyKrUoP76o NCe1+BCjNAeLkjjvQ/PNUUIC6YklqdmpqQWpRTBZJg5OqQZGX17nvgbx7YoN9XM3aVv7Oi8z UF18KWnPuxuht714j9ZNtwpbdjxwfX31BNWX/y0OSn+Of2qzODOzKc/YOL1zpvYFN26JdI3S M+/39psZ/BE2TYtds/qGfOvB1altR2bn2rn8UF7CnhOg33me5bAyj0JxYwDz5B8PZNuFX/M5 Trd3/O6ywluJpTgj0VCLuag4EQB0VLcMggIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uIDL8WfTloahMj8S7BOZ61VL1Sk>
Subject: [MMUSIC] trickle-ice-sip: Usage of PRACK instead of INFO?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 12:30:58 -0000

Hi,

Section 4.3.2 of draft-ietf-mmusic-trickle-ice-sip says:

   "In order to clear this ambiguity as soon as possible, the Answerer
   needs to retransmit the provisional response with the exponential
   back-off timers described in [RFC3262].  These retransmissions MUST
   cease on receipt of an INFO request carrying a 'trickle-ice' Info
   Package body or on transmission of the Answer in a 2xx response.
   This is similar to the procedure described in section 8.1.1 of
   [I-D.ietf-mmusic-ice-sip-sdp] except that the STUN binding Request is
   replaced by the INFO request."

Section 6.1.1 (the reference in the text above needs to be updated, as
indicated in a note) of draft-ietf-mmusic-ice-sip-sdp says:

   "It should be noted that the ICE specific optimization is very
   specific to provisional response carrying answers that start ICE
   processing and it is not a general technique for 1xx reliability.
   Also such an optimization SHOULD NOT be used if both agents support
   PRACK."


Q: Does the use-PRACK-if-both-agents-support-it apply to trickle-ICE too?
Section 4.3.1 describes the usage of PRACK, but there is no text regarding
whether one should use it if supported.

Regards,

Christer


From nobody Fri Apr 13 07:56:26 2018
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 90492124BE8; Fri, 13 Apr 2018 07:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EudqZ1Z56x-b; Fri, 13 Apr 2018 07:56:17 -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 09765120721; Fri, 13 Apr 2018 07:56:17 -0700 (PDT)
Received: from [10.0.1.91] (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 w3DEu4tV048275 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 13 Apr 2018 09:56:05 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8BD6D9F6-B063-4141-9B42-5338EDFAFB33"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Fri, 13 Apr 2018 09:56:02 -0500
In-Reply-To: <D6F67849.2DED5%christer.holmberg@ericsson.com>
Cc: Peter Saint-Andre <stpeter@mozilla.com>, Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com> <D6F67849.2DED5%christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gVVKF4hi2O88kuydJS8QNTaHn-E>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 14:56:19 -0000

--Apple-Mail=_8BD6D9F6-B063-4141-9B42-5338EDFAFB33
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 13, 2018, at 7:06 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
>>> On Apr 4, 2018, at 11:07 AM, Peter Saint-Andre <stpeter@mozilla.com>
>>> wrote:
>>>=20
>>> On 4/3/18 2:41 PM, Suhas Nandakumar wrote:
>>>>=20
>>>>=20
>>>> On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com
>>>> <mailto:ben@nostrum.com>> wrote:
>>>>=20
>>>>=20
>>>>=20
>>>>> On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com
>>>>> <mailto:stpeter@mozilla.com>> wrote:
>>>>>=20
>>>>> On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
>>>>>> Just to complete, ice-bis doesn=C4=85t normatively reference =
ice-sip-SDP
>>>>>> draft when it moved to using =C5=82usages =C5=82 indirections for =
signaling
>>>>>> protocols.
>>>>>>=20
>>>>>>=20
>>>>>> Trickle ice can use similar approach and refer to trickle-sip as
>>>>>> usage
>>>>>> for trickle.
>>>>>=20
>>>>> It already does. That's why we pulled all the SDP/SIP stuff out of
>>>>> draft-ietf-ice-trickle.
>>>>=20
>>>>   I assume Suhas meant separating the SDP stuff from the SIP stuff. =
(I
>>>>   also assume he will correct me if I am wrong.)
>>>>=20
>>>>=20
>>>> That's right Ben .. I was just thinking minimal localized changes =
(thus
>>>> small time to get new draft done) and then asking trickle, =
trickle-sip
>>>> to
>>>> refer to the new one. (work done to refer is much smaller for these
>>>> drafts that are at the very end of approval journey)
>>>>=20
>>>> I do agree with Adam, no matter what version of the proposal we =
pick,
>>>> there is some work that needs to be done and we
>>>> should do it.
>>>=20
>>> These documents are on the telechat tomorrow. Are we proposing to =
delay
>>> consideration by the IESG while we get this mess sorted out? ;-)
>>=20
>> Hi Peter,
>>=20
>> I currently plan to leave it on. We may discuss a way forward on the
>> telechat. Also, I=C4=85d like to get feedback on the rest of the =
draft(s) from
>> the other ADs sooner than later.
>=20
> Did you discuss this at the telechat?
>=20
> Any other discussions on how to move forward with this?

Yes, Adam and I have been discussing this with the RTCWEB chairs. =
We=E2=80=99ve since discovered that this is not the only JSEP normative =
reference chain back to SIP. The RTCWEB chairs are currently discussing =
whether they can live with that. They may decide to just reference =
things as they stand. If their answer involves a request to restructure =
anything, I will pull in the authors and MMUSIC/ICE chairs.

Thanks!

Ben.


--Apple-Mail=_8BD6D9F6-B063-4141-9B42-5338EDFAFB33
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrQxQIACgkQgFZKbJXz
1A1ddw//d1NHWF9kYk4y2EeYSz+WOdJnNYexOzBxS1RWzV0hbUOWVxq/D83xG/zA
JNOEUHaHNP0tdWfYzS7McTqmzR1Vy+Y/zGytXOj+NMJDNwmMmQnFl1l7IHU1rl1X
OcbQjXjBN86cqAldKfVpLZvKDYnx3ZLviwY590dOG1K1ppJGu0VykEljwab73HuH
J68AOQWztYqn/M5bRtv8Vnt/gzTVswQS4NSIIVChqbifPqztwDt7vOY/y/nO6wTX
MBsbWpR0GvNKAWen19MjZbjTccg6fgP7AcdNDMVyqnm1UvMQVm1so/93Rb/j9aOY
2f35jI4M45g/YHh+IXD8djOFogsmkrVb8T3tBC+KXz+Vz3HY3ha2bR3Oth6yMWuo
XRRuvUu4Im62mKGcWCWCFjiYOv40pDqfnnHjHww8ZiGYzQ+65S+CElM2N+pwG+82
CkLB1Zo+x5M+maDOJvbPvREV5kuU9rPF7DkjG6DTCmpVBosbXlcRkfELvzFm2b5z
cepdgkoCuJZvYc6lIdOGWz36EQXZ6/1niegZ2dZZWwa8IxD8losz+tZHVa5Gjb7o
Oyit9aWLRyJcvtxoVXtiPLKnGzrI41/Nsuhh8aIUGQrX4NTojIweaF6IvkoGnr4b
rnKJcFOhePi9pbcnTy3mR5jqNFnCBoOD8FbEIDOuHVeDsY/VgLg=
=lJ2X
-----END PGP SIGNATURE-----

--Apple-Mail=_8BD6D9F6-B063-4141-9B42-5338EDFAFB33--


From nobody Fri Apr 13 08:07:21 2018
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 287B7124BE8 for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 08:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=ietf@kuehlewind.net header.d=kuehlewind.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oOLgUcbnw5C5 for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 08:07:13 -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 C08F2126CF6 for <mmusic@ietf.org>; Fri, 13 Apr 2018 08:07:12 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kuehlewind.net;  b=hgopqNIw7cok7Gy0kBsMWn0MkQ2vOvssmmRZtQ+P1NNVUhVNvrcZ88PJWUHlDgCNZDVsVwa+ynRQfH0h5qUezYt81JiHmLPoo47ust8+hPqhb+AaZS76KHvgMe/OSU6ZbvRuoBfBfATRjwJ2eQIckRWsDE1oASMndbhaMT65hjY=; h=Received:Received:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-PPP-Message-ID:X-PPP-Vhost;
Received: (qmail 32146 invoked from network); 13 Apr 2018 17:06:10 +0200
Received: from i577bce4c.versanet.de (HELO ?192.168.178.24?) (87.123.206.76) by kuehlewind.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 13 Apr 2018 17:06:10 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <6ce0a44f-cca8-2105-73f5-75689dd8c611@gmail.com>
Date: Fri, 13 Apr 2018 17:06:09 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A91DAFC-8022-4B11-92F0-E6B7644A7218@kuehlewind.net>
References: <152276622276.14060.4683526444260158304.idtracker@ietfa.amsl.com> <d87ca5f9-3b36-d71e-667b-1396ea8a7ee9@gmail.com> <7CED4E17-86D2-407D-AF36-89C075121E9D@kuehlewind.net> <6ce0a44f-cca8-2105-73f5-75689dd8c611@gmail.com>
To: Thomas Stach <thomass.stach@gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
X-PPP-Message-ID: <20180413150610.32137.11649@lvps83-169-45-111.dedicated.hosteurope.de>
X-PPP-Vhost: kuehlewind.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_uoXbu1snItM7-clLUbf3rgU1ow>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_Discuss_on_draft-iet?= =?utf-8?q?f-mmusic-trickle-ice-sip-14=3A_=28with_DISCUSS_and_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 15:07:15 -0000

Hi again!

I actually looked up the recommendation in RFC8085 section 3.1.3 which =
says:

"A second case of applications cannot maintain an RTT estimate for
       a destination, because the destination does not send return
       traffic.  Such applications SHOULD NOT send more than one UDP
       datagram every 3 seconds and SHOULD use an even less aggressive
       rate when possible."

> Am 08.04.2018 um 20:57 schrieb Thomas Stach <thomass.stach@gmail.com>:
>=20
> In general, it is RECOMMENDED that a Trickle ICE Agent sends only one =
INFO request per RTT.
> A quarantine period of 100ms would be on the safe side, but lower =
values might be fine as well
> if the typically deployment scenario assumes a shorter RT.=E2=80=9C

So a recommendation of 100ms is probably not appropriate here. Inline =
with RFC8085 it would be 3 seconds. Thus it probably makes sense to =
strongly recommend to implement a way to estimate RTT. Please also add a =
reference to RFC8085.

Sorry for my late input. I should have double checked with RFC8085 =
earlier. I hope this can still be addressed appropriately.

Mirja


From nobody Fri Apr 13 11:29:29 2018
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 074C412778D for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 11:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oBlRW0zgvKlg for <mmusic@ietfa.amsl.com>; Fri, 13 Apr 2018 11:29: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 9B388124E15 for <mmusic@ietf.org>; Fri, 13 Apr 2018 11:29:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523644162; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=uvMBGZlR6ODzJqzE+6bYwsSknzkdZJ8HhP2XXUY15rk=; b=X7jb/ME0XCoRnfoVA+bVP5VsJrofidI+mq3Wwnx6R1EQcdplcTkK/Ak21gqdMs8z ER0jeNbv32L8S8oHPMd41NtXD2Godz8Md2W05709dkMoUinvbKQJ8sWzYBK9La6l 8AcopifT/Hci6DOK16mIP2SjCD7PYxUEo5+zhDhcr4E=;
X-AuditID: c1b4fb25-5a75a9c00000522b-91-5ad0f702059e
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 5C.D8.21035.207F0DA5; Fri, 13 Apr 2018 20:29:22 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.115]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Fri, 13 Apr 2018 20:29:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: Peter Saint-Andre <stpeter@mozilla.com>, Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAABSyAgAABrACAAA6TAIAAAI6AgAAWLYCAAUXTgIAAFRIAgA3/bYD///x6AIAAXRFN
Date: Fri, 13 Apr 2018 18:29:08 +0000
Message-ID: <7B683890-F38A-4D78-BEAC-02F6F90025D1@ericsson.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com> <D6F67849.2DED5%christer.holmberg@ericsson.com>, <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com>
In-Reply-To: <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7B683890F38A4D78BEAC02F6F90025D1ericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrEIsWRmVeSWpSXmKPExsUyM2K7ui7T9wtRBlN36Vvs+buI3WJ+52l2 ix9rlzNbvL+ga/HtQq3FjD8TmS3O71zPZDF1+WMWi7X/2tktnq08xWixc24HswO3x5TfG1k9 ds66y+6xZMlPJo++A12sHrN2PmEJYI3isklJzcksSy3St0vgytiyw7ngXANjxZq9h9kaGH/m dzFyckgImEi0v37ICmILCRxhlFjawN7FyAVkL2GU+DrvHZDDwcEmYCHR/U8bpEZEQEniefNW FpAaZoENzBIrW6+BNQsLFEj07N3PAlFUKLF2xyM2kCIRgWmMEv83vgUrYhFQlXi4eSsjiM0r YC9x4M8lVohtyzkkFkxrBktwAiUWPFnDDmIzCohJfD+1hgnEZhYQl7j1ZD4TxNkCEkv2nGeG sEUlXj7+xwpRkyzxrwniHV4BQYmTM5+wTGAUnoWkfRaSsllIymYBPcosYCDxaJ83RIm2xLKF r5khwvoSt69lIgsvYGRfxShanFqclJtuZKyXWpSZXFycn6eXl1qyiREYswe3/FbdwXj5jeMh RgEORiUe3ukfL0QJsSaWFVfmHmKU4GBWEuGNvQEU4k1JrKxKLcqPLyrNSS0+xCjNwaIkzvvQ fHOUkEB6YklqdmpqQWoRTJaJg1OqgTF/za1c1adHfM1rV94uuf3IdbnzbK49Dd3a4g/nH5i2 iaFdXvdoRfo+3wfGP64d5tDouStsfjHu5JNrR1/lVJk4RAQK7RA5+G1l3tT0kP+3t5k4qJd0 LTLtXXn9x+ryZPM+tzj+DQ1ussuu//T9yrhtddvDJIVXm5r4Xm+zFD7WFM7+Z6pi1T4lluKM REMt5qLiRADJDvM+1QIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/39skxGNFMfIe3e7zSkxK4i56KoA>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 18:29:27 -0000

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

Hi,

In addition, as I mentioned earlier, there are cases where JSEP references =
draft-ice-trickle for things and procedures that don=92t exist in draft-ice=
-trickle. Instead those references should be to draft-mmusic-trickle.

Regards,

Christer

Sent from my iPhone

On 13 Apr 2018, at 17.56, Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.=
com>> wrote:



On Apr 13, 2018, at 7:06 AM, Christer Holmberg <christer.holmberg@ericsson.=
com<mailto:christer.holmberg@ericsson.com>> wrote:

Hi,

On Apr 4, 2018, at 11:07 AM, Peter Saint-Andre <stpeter@mozilla.com<mailto:=
stpeter@mozilla.com>>
wrote:

On 4/3/18 2:41 PM, Suhas Nandakumar wrote:


On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com<mailto:ben@n=
ostrum.com>
<mailto:ben@nostrum.com>> wrote:



On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre <stpeter@mozilla.com<mailto:s=
tpeter@mozilla.com>
<mailto:stpeter@mozilla.com>> wrote:

On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
Just to complete, ice-bis doesn=B9t normatively reference ice-sip-SDP
draft when it moved to using =B3usages =B3 indirections for signaling
protocols.


Trickle ice can use similar approach and refer to trickle-sip as
usage
for trickle.

It already does. That's why we pulled all the SDP/SIP stuff out of
draft-ietf-ice-trickle.

 I assume Suhas meant separating the SDP stuff from the SIP stuff. (I
 also assume he will correct me if I am wrong.)


That's right Ben .. I was just thinking minimal localized changes (thus
small time to get new draft done) and then asking trickle, trickle-sip
to
refer to the new one. (work done to refer is much smaller for these
drafts that are at the very end of approval journey)

I do agree with Adam, no matter what version of the proposal we pick,
there is some work that needs to be done and we
should do it.

These documents are on the telechat tomorrow. Are we proposing to delay
consideration by the IESG while we get this mess sorted out? ;-)

Hi Peter,

I currently plan to leave it on. We may discuss a way forward on the
telechat. Also, I=B9d like to get feedback on the rest of the draft(s) from
the other ADs sooner than later.

Did you discuss this at the telechat?

Any other discussions on how to move forward with this?

Yes, Adam and I have been discussing this with the RTCWEB chairs. We=92ve s=
ince discovered that this is not the only JSEP normative reference chain ba=
ck to SIP. The RTCWEB chairs are currently discussing whether they can live=
 with that. They may decide to just reference things as they stand. If thei=
r answer involves a request to restructure anything, I will pull in the aut=
hors and MMUSIC/ICE chairs.

Thanks!

Ben.


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
250">
</head>
<body dir=3D"auto">
Hi,
<div><br>
</div>
<div>In addition, as I mentioned earlier, there are cases where JSEP refere=
nces draft-ice-trickle for things and procedures that don=92t exist in draf=
t-ice-trickle. Instead those references should be to draft-mmusic-trickle.<=
/div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer&nbsp;<br>
<br>
<div id=3D"AppleMailSignature">Sent from my iPhone</div>
<div><br>
On 13 Apr 2018, at 17.56, Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.co=
m">ben@nostrum.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div><span></span><br>
<span></span><br>
<blockquote type=3D"cite"><span>On Apr 13, 2018, at 7:06 AM, Christer Holmb=
erg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg=
@ericsson.com</a>&gt; wrote:</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Hi,</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>On Apr 4, 2018, at 11:07 AM, Peter Saint-An=
dre &lt;<a href=3D"mailto:stpeter@mozilla.com">stpeter@mozilla.com</a>&gt;<=
/span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>wrote:</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>On 4/3/18 2:41 PM, Suhas Nandakumar wrote:<=
/span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbe=
ll &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&lt;<a href=3D"mailto:ben@nostrum.com">mail=
to:ben@nostrum.com</a>&gt;&gt; wrote:</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>On Apr 3, 2018, at 2:20 PM, Peter Saint-And=
re &lt;<a href=3D"mailto:stpeter@mozilla.com">stpeter@mozilla.com</a></span=
><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&lt;<a href=3D"mailto:stpeter@mozilla.com">=
mailto:stpeter@mozilla.com</a>&gt;&gt; wrote:</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>On 4/3/18 12:27 PM, Suhas Nandakumar wrote:=
</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Just to complete, ice-bis doesn=B9t normati=
vely reference ice-sip-SDP</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>draft when it moved to using =B3usages =B3 =
indirections for signaling</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>protocols.</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Trickle ice can use similar approach and re=
fer to trickle-sip as</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>usage</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>for trickle.</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>It already does. That's why we pulled all t=
he SDP/SIP stuff out of</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>draft-ietf-ice-trickle.</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&nbsp;I assume Suhas meant separating the S=
DP stuff from the SIP stuff. (I</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>&nbsp;also assume he will correct me if I a=
m wrong.)</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>That's right Ben .. I was just thinking min=
imal localized changes (thus</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>small time to get new draft done) and then =
asking trickle, trickle-sip</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>to</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>refer to the new one. (work done to refer i=
s much smaller for these</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>drafts that are at the very end of approval=
 journey)</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>I do agree with Adam, no matter what versio=
n of the proposal we pick,</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>there is some work that needs to be done an=
d we</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>should do it.</span><br>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>These documents are on the telechat tomorro=
w. Are we proposing to delay</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>consideration by the IESG while we get this=
 mess sorted out? ;-)</span><br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Hi Peter,</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>I currently plan to leave it on. We may dis=
cuss a way forward on the</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>telechat. Also, I=B9d like to get feedback =
on the rest of the draft(s) from</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>the other ADs sooner than later.</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Did you discuss this at the telechat?</span=
><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Any other discussions on how to move forwar=
d with this?</span><br>
</blockquote>
<span></span><br>
<span>Yes, Adam and I have been discussing this with the RTCWEB chairs. We=
=92ve since discovered that this is not the only JSEP normative reference c=
hain back to SIP. The RTCWEB chairs are currently discussing whether they c=
an live with that. They may decide
 to just reference things as they stand. If their answer involves a request=
 to restructure anything, I will pull in the authors and MMUSIC/ICE chairs.=
</span><br>
<span></span><br>
<span>Thanks!</span><br>
<span></span><br>
<span>Ben.</span><br>
<span></span><br>
</div>
</blockquote>
</div>
</body>
</html>

--_000_7B683890F38A4D78BEAC02F6F90025D1ericssoncom_--


From nobody Fri Apr 13 12:56:22 2018
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 D5680127978; Fri, 13 Apr 2018 12:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GfK14ufvrUby; Fri, 13 Apr 2018 12:56:12 -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 C1683127AD4; Fri, 13 Apr 2018 12:56:12 -0700 (PDT)
Received: from [10.0.1.91] (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 w3DJu08a097300 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 13 Apr 2018 14:56:01 -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.91]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <14DA7FB6-2F60-4106-BC80-8F43CA621740@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_019D8A7C-D803-4A66-9249-3D5C4AE90557"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Fri, 13 Apr 2018 14:55:59 -0500
In-Reply-To: <7B683890-F38A-4D78-BEAC-02F6F90025D1@ericsson.com>
Cc: Peter Saint-Andre <stpeter@mozilla.com>, Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com> <D6F67849.2DED5%christer.holmberg@ericsson.com> <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com> <7B683890-F38A-4D78-BEAC-02F6F90025D1@ericsson.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8L4yJKQTh3dLywKJTrw0oi4eSs8>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 19:56:15 -0000

--Apple-Mail=_019D8A7C-D803-4A66-9249-3D5C4AE90557
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Yes. The question is whether to just move the references in JSEP to =
point to mmusic-trickle-sip, or do something different.

> On Apr 13, 2018, at 1:29 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> In addition, as I mentioned earlier, there are cases where JSEP =
references draft-ice-trickle for things and procedures that don=E2=80=99t =
exist in draft-ice-trickle. Instead those references should be to =
draft-mmusic-trickle.
>=20
> Regards,
>=20
> Christer
>=20
> Sent from my iPhone
>=20
> On 13 Apr 2018, at 17.56, Ben Campbell <ben@nostrum.com> wrote:
>=20
>>=20
>>=20
>>> On Apr 13, 2018, at 7:06 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>>>=20
>>> Hi,
>>>=20
>>>>> On Apr 4, 2018, at 11:07 AM, Peter Saint-Andre =
<stpeter@mozilla.com>
>>>>> wrote:
>>>>>=20
>>>>> On 4/3/18 2:41 PM, Suhas Nandakumar wrote:
>>>>>>=20
>>>>>>=20
>>>>>> On Tue, Apr 3, 2018 at 12:22 PM, Ben Campbell <ben@nostrum.com
>>>>>> <mailto:ben@nostrum.com>> wrote:
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>> On Apr 3, 2018, at 2:20 PM, Peter Saint-Andre =
<stpeter@mozilla.com
>>>>>>> <mailto:stpeter@mozilla.com>> wrote:
>>>>>>>=20
>>>>>>> On 4/3/18 12:27 PM, Suhas Nandakumar wrote:
>>>>>>>> Just to complete, ice-bis doesn=C4=85t normatively reference =
ice-sip-SDP
>>>>>>>> draft when it moved to using =C5=82usages =C5=82 indirections =
for signaling
>>>>>>>> protocols.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> Trickle ice can use similar approach and refer to trickle-sip =
as
>>>>>>>> usage
>>>>>>>> for trickle.
>>>>>>>=20
>>>>>>> It already does. That's why we pulled all the SDP/SIP stuff out =
of
>>>>>>> draft-ietf-ice-trickle.
>>>>>>=20
>>>>>>  I assume Suhas meant separating the SDP stuff from the SIP =
stuff. (I
>>>>>>  also assume he will correct me if I am wrong.)
>>>>>>=20
>>>>>>=20
>>>>>> That's right Ben .. I was just thinking minimal localized changes =
(thus
>>>>>> small time to get new draft done) and then asking trickle, =
trickle-sip
>>>>>> to
>>>>>> refer to the new one. (work done to refer is much smaller for =
these
>>>>>> drafts that are at the very end of approval journey)
>>>>>>=20
>>>>>> I do agree with Adam, no matter what version of the proposal we =
pick,
>>>>>> there is some work that needs to be done and we
>>>>>> should do it.
>>>>>=20
>>>>> These documents are on the telechat tomorrow. Are we proposing to =
delay
>>>>> consideration by the IESG while we get this mess sorted out? ;-)
>>>>=20
>>>> Hi Peter,
>>>>=20
>>>> I currently plan to leave it on. We may discuss a way forward on =
the
>>>> telechat. Also, I=C4=85d like to get feedback on the rest of the =
draft(s) from
>>>> the other ADs sooner than later.
>>>=20
>>> Did you discuss this at the telechat?
>>>=20
>>> Any other discussions on how to move forward with this?
>>=20
>> Yes, Adam and I have been discussing this with the RTCWEB chairs. =
We=E2=80=99ve since discovered that this is not the only JSEP normative =
reference chain back to SIP. The RTCWEB chairs are currently discussing =
whether they can live with that. They may decide to just reference =
things as they stand. If their answer involves a request to restructure =
anything, I will pull in the authors and MMUSIC/ICE chairs.
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20


--Apple-Mail=_019D8A7C-D803-4A66-9249-3D5C4AE90557
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrRC08ACgkQgFZKbJXz
1A2hiA/9HWxY+Sx4AS7gQv8QvWVmlnixvhco+MEMklzIjhooTOfm+Ejf0V5QN+bN
20rqSCPgBImwWRfE1Ob8+Vtpdmj9L2WR52zzbNuPAYZuqRt6R+1Hur4a8JmokLzh
zeWoJM9pHBFrTAWx2kZVaaLvmDYW2ZL1glTZwydzzckYqX9AZWZanAkwOW51kfSQ
7uiM82WE0fymik9Ngmo9K8nG4mnVPBbxQ2WUJG1Wi5/zvEkXBtmcC4vX3vnvdgLz
unLGEXZ6E030GMYAHp2J4D5ADktwg4y+EsMW49gxbuE+pMaBaDQ+eXlg6jWryDl3
JO6rEODqzL3ikiGCPRLkgBiOsc30bKhSjSDynOboAfS+6YudxkP9AVVHLgcBwi3w
ILqGvdyb0HbqAtwxoBgNPyYyF37O2T8yAI7RBp56KmIH4lPzxIN5Y+yZx2cJw/Y3
qPWiKODPCrze3hXoHKUSzMAF0q+q2MQHhEymv6FuiylAr53XKlkcKOqroxU5B85G
G34NDSa05Z01NMQes+DEPHj5qeaPWUe05r87FRUE1b+GYBP1ZHQIG4l2vkwUFfDs
7Xul8SyFCXI1y6/2iDwBYWbXXeuFrVjdNrR5pkOcnuli0+s9TNA1nTzAgrbrMMhE
ks++fZN0ys+oq1/Ogr3Pg43sDcHm3h1HbJTmEVBraRoD6/VACkY=
=JgB4
-----END PGP SIGNATURE-----

--Apple-Mail=_019D8A7C-D803-4A66-9249-3D5C4AE90557--


From nobody Fri Apr 13 13:46:23 2018
Return-Path: <kaduk@mit.edu>
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 33D39127978; Fri, 13 Apr 2018 13:46:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk <kaduk@mit.edu>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org,  fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com>
Date: Fri, 13 Apr 2018 13:46:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/dB6VxXwA9VVt14h-0NyWOpQjCGQ>
Subject: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 13 Apr 2018 20:46:21 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-mmusic-sdp-bundle-negotiation-49: 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-bundle-negotiation/



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

Should the NOTE in Section 8.5.2 explicitly reaffirm that only one
m= section within the BUNDLE group can have the offerer BUNDLE
address:port, regardless of whether it is a new or preexisting
address:port?  That is, that you cannot use an existing BUNDLE
address:port and offer a new one in the same BUNDLE group.


When we talk about how the offerer must move a section out of one
BUNDLE group and then generate a second offer where that section is
added to the other BUNDLE group (this occurs in several places,
IIRC), do we need to say anything about the offer that moves the
section out of the first BUNDLE group must be accepted before the
second offer is offered?


In Section 10.2, page 23, I appreciate the description of the
payload type/m= mapping used by legacy implementations, but I worry
that there may not be sufficient description of when an SDP participant
should take the care to ensure the uniqueness of the mapping (versus
when the legacy considerations can be ignored).


Does the first paragraph of Section 10.3.1.2 imply that an
implementation of BUNDLE must also implement rtcp-mux-only?


Should the RTP SDES header extension URI be mentioned somewhere
other than the IANA considerations?


In Section 17:
   The security considerations of "RTP Header Extension for the RTP
   Control Protocol (RTCP) Source Description Items" [RFC7941] requires
   that when RTCP is confidentiality protected, and that any SDES RTP
   header extension carrying an SDES item, such as the MID RTP header
   extension, is also protected using commensurate strength algorithms.
"that when [...], and that" seems the wrong construction here; I
think that just "that when [...]," is the intended meaning.



From nobody Sat Apr 14 08:06:41 2018
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 514FE1201F2 for <mmusic@ietfa.amsl.com>; Sat, 14 Apr 2018 08:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.331
X-Spam-Level: 
X-Spam-Status: No, score=-4.331 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iinaK7_apV5T for <mmusic@ietfa.amsl.com>; Sat, 14 Apr 2018 08:06:37 -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 2256C12420B for <mmusic@ietf.org>; Sat, 14 Apr 2018 08:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523718394; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ea9c9gODZnkM1j4/crhM5UQMpeiiEh+roYKZb+Kmgx4=; b=I5fsTFzMdfVfYTkzD28mOUCb1DM2/CTKpTyxmyaujajpAKROpjqyfrzJvbr+sTKn FPFdyvDAER0vPzswOMTNEUMoykdzrij66Zwk8quGocN/+n7mhk0weEm3/XkuH/Ag 4IaBnCq9popk+uP9MilaCXMAEXWBqWckc8pmWFcrxdc=;
X-AuditID: c1b4fb25-1c7ff7000000522b-8d-5ad218fa2a89
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 0D.47.21035.AF812DA5; Sat, 14 Apr 2018 17:06:34 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Sat, 14 Apr 2018 17:06:34 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "Colin Perkins (csp@csperkins.org)" <csp@csperkins.org>
Thread-Topic: Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT02h7nl6LsadKeEO3frGUURdVt6P/5WiA
Date: Sat, 14 Apr 2018 15:06:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se>
References: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com>
In-Reply-To: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.170]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsUyM2K7je4viUtRBus2a1ssf3mC0WL6rHds Fu8v6FrM+DOR2WL5xplMFud3rmeymLr8MYsDu8eU3xtZPabdv8/msWTJTyaPpjNHmQNYorhs UlJzMstSi/TtErgyOm/+ZS5o0Kh4cW0HWwPjH7UuRg4OCQETiSmr/bsYuTiEBI4wSiy7/p0V wlnMKHH31WJmkCI2AQuJ7n/aXYycHCICNhKL7+5lBqlhFnjKJPH8xRxGkBphgWyJTVf0IWpy JN4vnQ0WFhEwkjj20x3EZBFQlXh4RBWkglfAV2LCvkPMILYQkH2x9S8jiM0p4Cdxta+ZHcRm FBCT+H5qDROIzSwgLnHryXwwW0JAQGLJnvPMELaoxMvH/1ghbCWJM5ues4CsYhbQlFi/Sx+i VVFiSvdDdoi1ghInZz5hmcAoOgvJ1FkIHbOQdMxC0rGAkWUVo2hxanFSbrqRsV5qUWZycXF+ nl5easkmRmCEHdzyW3UH4+U3jocYBTgYlXh4uQQuRQmxJpYVV+YeYpTgYFYS4c3adTFKiDcl sbIqtSg/vqg0J7X4EKM0B4uSOO9D881RQgLpiSWp2ampBalFMFkmDk6pBsaerjPqZ1cZGfYd iN17+te3jPwNa3lrNixzzdSWaBM1KltqZiiau8Z4p99Rg2nv1rCqfl+bntNoIZp8Osra1jms MT73zSXJHW0NvjcOe/fefCyheLx5cW6h8QzltBy2o+13fncutOU60rDtahRvvdW+OQVaDEIr 9l44XWD8cKar3z4z3lz5W0osxRmJhlrMRcWJAFZOD5asAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kfd1X0wzJrgRkbNN737oxVKOE8A>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 14 Apr 2018 15:06:39 -0000

SGkgQmVuamFtaW4sDQoNClRoYW5rIFlvdSBmb3IgdGhlIHJldmlldyEgUGxlYXNlIHNlZSBpbmxp
bmUuDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNPTU1FTlQ6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCj4gU2hvdWxk
IHRoZSBOT1RFIGluIFNlY3Rpb24gOC41LjIgZXhwbGljaXRseSByZWFmZmlybSB0aGF0IG9ubHkg
b25lIG09IHNlY3Rpb24gd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXAgDQo+IGNhbiBoYXZlIHRoZSBv
ZmZlcmVyIEJVTkRMRSBhZGRyZXNzOnBvcnQsIHJlZ2FyZGxlc3Mgb2Ygd2hldGhlciBpdCBpcyBh
IG5ldyBvciBwcmVleGlzdGluZyBhZGRyZXNzOnBvcnQ/ICANCj4gVGhhdCBpcywgdGhhdCB5b3Ug
Y2Fubm90IHVzZSBhbiBleGlzdGluZyBCVU5ETEUgYWRkcmVzczpwb3J0IGFuZCBvZmZlciBhIG5l
dyBvbmUgaW4gdGhlIHNhbWUgQlVORExFIGdyb3VwLg0KDQpJIGNhbiBhZGQgYSBzZW50ZW5jZSB0
byB0aGUgZW5kIG9mIHRoZSBOb3RlOg0KDQogICAiTk9URTogSWYgdGhlIG9mZmVyZXIgYWxzbyB3
YW50cyB0byBzdWdnZXN0IGEgbmV3IG9mZmVyZXIgQlVORExFDQogICBhZGRyZXNzOnBvcnQgdG8g
dGhlIEJVTkRMRSBncm91cCwgdGhlIG9mZmVyZXIgY2FuIGFzc2lnbiB0aGUgbmV3bHkNCiAgIHN1
Z2dlc3RlZCBvZmZlcmVyIEJVTkRMRSBhZGRyZXNzOnBvcnQgZWl0aGVyIHRvIHRoZSBhZGRlZCAi
bT0iDQogICBzZWN0aW9uLCBvciB0byBzb21lIG90aGVyICJtPSIgc2VjdGlvbiB3aXRoaW4gdGhl
IEJVTkRMRSBncm91cA0KICAgW1NlY3Rpb24gOC41LjFdLiBUbyBldmVyeSBvdGhlciAibT0iIHNl
Y3Rpb24gd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXANCiAgIHRoZSBvZmZlcmVyIHdpbGwgYXNzaWdu
IGEgemVybyBwb3J0IHZhbHVlIGFuZCBhbiBTRFAgJ2J1bmRsZS1vbmx5JyBhdHRyaWJ1dGUNCiAg
IFtTZWN0aW9uIDguNS4xXS4iDQogICAgICANCi0tLQ0KDQo+IFdoZW4gd2UgdGFsayBhYm91dCBo
b3cgdGhlIG9mZmVyZXIgbXVzdCBtb3ZlIGEgc2VjdGlvbiBvdXQgb2Ygb25lIEJVTkRMRSBncm91
cCBhbmQgdGhlbiBnZW5lcmF0ZSBhIHNlY29uZCBvZmZlcg0KPiB3aGVyZSB0aGF0IHNlY3Rpb24g
aXMgYWRkZWQgdG8gdGhlIG90aGVyIEJVTkRMRSBncm91cCAodGhpcyBvY2N1cnMgaW4gc2V2ZXJh
bCBwbGFjZXMsIElJUkMpLCBkbyB3ZSBuZWVkIHRvIHNheSBhbnl0aGluZw0KPiBhYm91dCB0aGUg
b2ZmZXIgdGhhdCBtb3ZlcyB0aGUgc2VjdGlvbiBvdXQgb2YgdGhlIGZpcnN0IEJVTkRMRSBncm91
cCBtdXN0IGJlIGFjY2VwdGVkIGJlZm9yZSB0aGUgc2Vjb25kIG9mZmVyIGlzIG9mZmVyZWQ/DQoN
Ckl0IGlzIGEgYmFzaWMgMzI2NCBydWxlIHRoYXQgd2hhdGV2ZXIgY2hhbmdlcyBhcmUgZG9uZSBp
biBhbiBvZmZlciBvbmx5IGJlY29tZSB2YWxpZCBvbmNlIHRoZXkgaGF2ZSBiZWVuIGFjY2VwdGVk
IGJ5IHRoZSBhbnN3ZXJlci4NCg0KLS0tDQoNCj4gSW4gU2VjdGlvbiAxMC4yLCBwYWdlIDIzLCBJ
IGFwcHJlY2lhdGUgdGhlIGRlc2NyaXB0aW9uIG9mIHRoZSBwYXlsb2FkIHR5cGUvbT0gbWFwcGlu
ZyB1c2VkIGJ5IGxlZ2FjeQ0KPiBpbXBsZW1lbnRhdGlvbnMsIGJ1dCBJIHdvcnJ5IHRoYXQgdGhl
cmUgbWF5IG5vdCBiZSBzdWZmaWNpZW50IGRlc2NyaXB0aW9uIG9mIHdoZW4gYW4gU0RQIHBhcnRp
Y2lwYW50IHNob3VsZCANCj4gdGFrZSB0aGUgY2FyZSB0byBlbnN1cmUgdGhlIHVuaXF1ZW5lc3Mg
b2YgdGhlIG1hcHBpbmcgKHZlcnN1cyB3aGVuIHRoZSBsZWdhY3kgY29uc2lkZXJhdGlvbnMgY2Fu
IGJlIGlnbm9yZWQpLg0KDQpTZWN0aW9uIDEwIHdhcyAib3V0c291cmNlZCIsIHNvIEkgd2lsbCBh
c2sgdGhlIGZvbGtzIHdobyBwcm92aWRlZCB0aGUgdGV4dCB0byByZXBseSA6KQ0KDQpNYWdudXMs
IENvbGluPw0KDQotLS0tDQoNCj4gRG9lcyB0aGUgZmlyc3QgcGFyYWdyYXBoIG9mIFNlY3Rpb24g
MTAuMy4xLjIgaW1wbHkgdGhhdCBhbiBpbXBsZW1lbnRhdGlvbiBvZiBCVU5ETEUgbXVzdCBhbHNv
IGltcGxlbWVudCBydGNwLW11eC1vbmx5Pw0KDQpZZXMuIEkgY291bGQgYWRkIGEgc2VudGVuY2Ug
dG8gdGhlIGZvbGxvd2luZyBwYXJhZ3JhcGggaW4gc2VjdGlvbiAxMC4yLjoNCg0KICAgIldpdGhp
biBhIEJVTkRMRSBncm91cCwgdGhlIG9mZmVyZXIgYW5kIGFuc3dlcmVyIE1VU1QgZW5hYmxlIFJU
UC9SVENQDQogICBtdWx0aXBsZXhpbmcgW1JGQzU3NjFdIGZvciB0aGUgUlRQLWJhc2VkIG1lZGlh
IHNwZWNpZmllZCBieSB0aGUNCiAgIEJVTkRMRSBncm91cC4gSW4gYWRkaXRpb24sIHRoZSBvZmZl
cmVyIGFuZCBhbnN3ZXJlciBNVVNUIHN1cHBvcnQgdGhlDQogICBTRFAgJ3J0Y3AtbXV4LW9ubHkn
IGF0dHJpYnV0ZSBbSS1ELmlldGYtbW11c2ljLW11eC1leGNsdXNpdmVdLiINCg0KLS0tLQ0KDQo+
IFNob3VsZCB0aGUgUlRQIFNERVMgaGVhZGVyIGV4dGVuc2lvbiBVUkkgYmUgbWVudGlvbmVkIHNv
bWV3aGVyZSBvdGhlciB0aGFuIHRoZSBJQU5BIGNvbnNpZGVyYXRpb25zPw0KDQpJdCBpcyBtZW50
aW9uZWQgaW4gU2VjdGlvbiAxMC4xOg0KDQogICAgICAibyAgVGhlIFJUUCBNSUQgaGVhZGVyIGV4
dGVuc2lvbiBNVVNUIGJlIGVuYWJsZWQsIGJ5IGluY2x1ZGluZyBhbiBTRFANCiAgICAgICdleHRt
YXAnIGF0dHJpYnV0ZSBbUkZDODI4NV0sIHdpdGggYSAndXJuOmlldGY6cGFyYW1zOnJ0cC0NCiAg
ICAgIGhkcmV4dDpzZGVzOm1pZCcgVVJJIHZhbHVlLCBpbiBlYWNoIGJ1bmRsZWQgUlRQLWJhc2Vk
ICJtPSIgc2VjdGlvbg0KICAgICAgaW4gZXZlcnkgb2ZmZXIgYW5kIGFuc3dlci4iDQoNCi0tLQ0K
DQo+SW4gU2VjdGlvbiAxNzoNCj4NCj4gICBUaGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgb2Yg
IlJUUCBIZWFkZXIgRXh0ZW5zaW9uIGZvciB0aGUgUlRQDQo+ICAgQ29udHJvbCBQcm90b2NvbCAo
UlRDUCkgU291cmNlIERlc2NyaXB0aW9uIEl0ZW1zIiBbUkZDNzk0MV0gcmVxdWlyZXMNCj4gICB0
aGF0IHdoZW4gUlRDUCBpcyBjb25maWRlbnRpYWxpdHkgcHJvdGVjdGVkLCBhbmQgdGhhdCBhbnkg
U0RFUyBSVFANCj4gICBoZWFkZXIgZXh0ZW5zaW9uIGNhcnJ5aW5nIGFuIFNERVMgaXRlbSwgc3Vj
aCBhcyB0aGUgTUlEIFJUUCBoZWFkZXINCj4gICBleHRlbnNpb24sIGlzIGFsc28gcHJvdGVjdGVk
IHVzaW5nIGNvbW1lbnN1cmF0ZSBzdHJlbmd0aCBhbGdvcml0aG1zLg0KPg0KPiAidGhhdCB3aGVu
IFsuLi5dLCBhbmQgdGhhdCIgc2VlbXMgdGhlIHdyb25nIGNvbnN0cnVjdGlvbiBoZXJlOyBJIHRo
aW5rIHRoYXQganVzdCAidGhhdCB3aGVuIFsuLi5dLCIgaXMgdGhlIGludGVuZGVkIG1lYW5pbmcu
DQoNCkNvcnJlY3QuIEkgc3VnZ2VzdDoNCg0KICAgIlRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9u
cyBvZiAiUlRQIEhlYWRlciBFeHRlbnNpb24gZm9yIHRoZSBSVFANCiAgIENvbnRyb2wgUHJvdG9j
b2wgKFJUQ1ApIFNvdXJjZSBEZXNjcmlwdGlvbiBJdGVtcyIgW1JGQzc5NDFdIHJlcXVpcmVzDQog
ICB0aGF0IHdoZW4gUlRDUCBpcyBjb25maWRlbnRpYWxpdHkgcHJvdGVjdGVkLCB0aGVuIGFueSBT
REVTIFJUUA0KICAgaGVhZGVyIGV4dGVuc2lvbiBjYXJyeWluZyBhbiBTREVTIGl0ZW0sLi4uIg0K
DQotLS0NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQo=


From nobody Sun Apr 15 00:16:56 2018
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 EF65B127601 for <mmusic@ietfa.amsl.com>; Sun, 15 Apr 2018 00:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gdyZl1i4ELiE for <mmusic@ietfa.amsl.com>; Sun, 15 Apr 2018 00:16:52 -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 D134E124239 for <mmusic@ietf.org>; Sun, 15 Apr 2018 00:16:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523776610; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ScDIy4cAoVJ6ynkQZLSQ4QpubT8ryhvVFR8IFfTtWJI=; b=DJiMUCc8+gav6KOPmoH1fQQzVWnJt/fnveWkYqHV1jiV6XzXKaUzxJc9K8ns4xTB 85VJtJdoX7iobRziDwWGSe6gTCZTGG5sdYK3LWI234GzCDCQsUYlJWPT8jEPUKAl 9wMuuOjLyXFzMQTttDeCMW4gY9obp+PZQG+ryObWlxI=;
X-AuditID: c1b4fb2d-82dff70000003563-2a-5ad2fc616201
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 24.D7.13667.16CF2DA5; Sun, 15 Apr 2018 09:16:50 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0382.000; Sun, 15 Apr 2018 09:16:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: Peter Saint-Andre <stpeter@mozilla.com>, Suhas Nandakumar <suhasietf@gmail.com>, Adam Roach <adam@nostrum.com>, mmusic WG <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "ice@ietf.org" <ice@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAABSyAgAABrACAAA6TAIAAAI6AgAAWLYCAAUXTgIAAFRIAgA3/bYD///x6AIAAXRFN///2vYCAAnGPMA==
Date: Sun, 15 Apr 2018 07:16:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E72F58@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com> <D6F67849.2DED5%christer.holmberg@ericsson.com> <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com> <7B683890-F38A-4D78-BEAC-02F6F90025D1@ericsson.com> <14DA7FB6-2F60-4106-BC80-8F43CA621740@nostrum.com>
In-Reply-To: <14DA7FB6-2F60-4106-BC80-8F43CA621740@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2K7k27Sn0tRBnfeMVvs+buI3WJ+52l2 ix9rlzNbvL+ga/HtQq3FjD8TmS3O71zPZDF1+WMWi7X/2tktnq08xWixc24HswO3x5TfG1k9 ds66y+6xZMlPJo++A12sHrN2PmEJYI3isklJzcksSy3St0vgyph19wB7QY9KxZQ5BxkbGKco dzFyckgImEgcbbjN1sXIxSEkcIRRoqfxOyuEs5hRYsu8u0xdjBwcbAIWEt3/tEEaRASUJJ43 b2UBqWEW2MAssbL1GitIQligQGLjnFY2iKJCibU7HoFNFRFYxiixcMUidpAEi4CqxKNT98Aa eAV8JS6eOcMCsW0Kp8SP05+ZQRKcAvYS6/evBStiFBCT+H5qDROIzSwgLnHryXwmiLsFJJbs Oc8MYYtKvHz8jxXCVpJ4+n8J2NXMApoS63fpQ7QqSkzpfsgOsVdQ4uTMJywTGEVnIZk6C6Fj FpKOWUg6FjCyrGIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQIjM6DW37r7mBc/drxEKMAB6MS D2/X+0tRQqyJZcWVuYcYJTiYlUR4S9yBQrwpiZVVqUX58UWlOanFhxilOViUxHn1Vu2JEhJI TyxJzU5NLUgtgskycXBKNTDmlRzYUqQqJjfrmsB/25iEbzZP4vt+vr47r2zxPJc5fuke70Xm vBa86/t9zjYh9+i6b7Mm3FEv+/Nv/8KrTszmS0tajNlrmv9ktZzdvOeZPfOjOD7FSMWVpypV 9TbtfbqrQuKU4OuG870hu3IjGM2E/uY/2xqTf3X615Kz+zfLf3uzdI/C2YIlSizFGYmGWsxF xYkAhmDsscoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xp8om98BZJ1KyS-kONIch-Elrak>
Subject: Re: [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 15 Apr 2018 07:16:54 -0000

SGksDQoNCj4gWWVzLiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciB0byBqdXN0IG1vdmUgdGhlIHJl
ZmVyZW5jZXMgaW4gSlNFUCB0byBwb2ludCB0byBtbXVzaWMtdHJpY2tsZS1zaXAsIG9yIGRvIHNv
bWV0aGluZyBkaWZmZXJlbnQuDQoNCkkgdGhpbmsgaXQgd291bGQgYmUgZ29vZCB0byBoYXZlIGEg
bGlzdCBvZiBhbGwgdGhlIHJlZmVyZW5jZSBpbnN0YW5jZXMgdGhhdCBuZWVkIHRvIGJlIG1vZGlm
aWVkLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo+IE9uIEFwciAxMywgMjAxOCwgYXQgMToy
OSBQTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4g
d3JvdGU6DQo+IA0KPiBIaSwNCj4gDQo+IEluIGFkZGl0aW9uLCBhcyBJIG1lbnRpb25lZCBlYXJs
aWVyLCB0aGVyZSBhcmUgY2FzZXMgd2hlcmUgSlNFUCByZWZlcmVuY2VzIGRyYWZ0LWljZS10cmlj
a2xlIGZvciB0aGluZ3MgYW5kIHByb2NlZHVyZXMgdGhhdCBkb27igJl0IGV4aXN0IGluIGRyYWZ0
LWljZS10cmlja2xlLiBJbnN0ZWFkIHRob3NlIHJlZmVyZW5jZXMgc2hvdWxkIGJlIHRvIGRyYWZ0
LW1tdXNpYy10cmlja2xlLg0KPiANCj4gUmVnYXJkcywNCj4gDQo+IENocmlzdGVyDQo+IA0KPiBT
ZW50IGZyb20gbXkgaVBob25lDQo+IA0KPiBPbiAxMyBBcHIgMjAxOCwgYXQgMTcuNTYsIEJlbiBD
YW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPiB3cm90ZToNCj4gDQo+PiANCj4+IA0KPj4+IE9uIEFw
ciAxMywgMjAxOCwgYXQgNzowNiBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+Pj4gDQo+Pj4gSGksDQo+Pj4gDQo+Pj4+PiBPbiBB
cHIgNCwgMjAxOCwgYXQgMTE6MDcgQU0sIFBldGVyIFNhaW50LUFuZHJlIA0KPj4+Pj4gPHN0cGV0
ZXJAbW96aWxsYS5jb20+DQo+Pj4+PiB3cm90ZToNCj4+Pj4+IA0KPj4+Pj4gT24gNC8zLzE4IDI6
NDEgUE0sIFN1aGFzIE5hbmRha3VtYXIgd3JvdGU6DQo+Pj4+Pj4gDQo+Pj4+Pj4gDQo+Pj4+Pj4g
T24gVHVlLCBBcHIgMywgMjAxOCBhdCAxMjoyMiBQTSwgQmVuIENhbXBiZWxsIDxiZW5Abm9zdHJ1
bS5jb20gDQo+Pj4+Pj4gPG1haWx0bzpiZW5Abm9zdHJ1bS5jb20+PiB3cm90ZToNCj4+Pj4+PiAN
Cj4+Pj4+PiANCj4+Pj4+PiANCj4+Pj4+Pj4gT24gQXByIDMsIDIwMTgsIGF0IDI6MjAgUE0sIFBl
dGVyIFNhaW50LUFuZHJlIA0KPj4+Pj4+PiA8c3RwZXRlckBtb3ppbGxhLmNvbSA8bWFpbHRvOnN0
cGV0ZXJAbW96aWxsYS5jb20+PiB3cm90ZToNCj4+Pj4+Pj4gDQo+Pj4+Pj4+IE9uIDQvMy8xOCAx
MjoyNyBQTSwgU3VoYXMgTmFuZGFrdW1hciB3cm90ZToNCj4+Pj4+Pj4+IEp1c3QgdG8gY29tcGxl
dGUsIGljZS1iaXMgZG9lc27EhXQgbm9ybWF0aXZlbHkgcmVmZXJlbmNlIA0KPj4+Pj4+Pj4gaWNl
LXNpcC1TRFAgZHJhZnQgd2hlbiBpdCBtb3ZlZCB0byB1c2luZyDFgnVzYWdlcyDFgiBpbmRpcmVj
dGlvbnMgDQo+Pj4+Pj4+PiBmb3Igc2lnbmFsaW5nIHByb3RvY29scy4NCj4+Pj4+Pj4+IA0KPj4+
Pj4+Pj4gDQo+Pj4+Pj4+PiBUcmlja2xlIGljZSBjYW4gdXNlIHNpbWlsYXIgYXBwcm9hY2ggYW5k
IHJlZmVyIHRvIHRyaWNrbGUtc2lwIA0KPj4+Pj4+Pj4gYXMgdXNhZ2UgZm9yIHRyaWNrbGUuDQo+
Pj4+Pj4+IA0KPj4+Pj4+PiBJdCBhbHJlYWR5IGRvZXMuIFRoYXQncyB3aHkgd2UgcHVsbGVkIGFs
bCB0aGUgU0RQL1NJUCBzdHVmZiBvdXQgDQo+Pj4+Pj4+IG9mIGRyYWZ0LWlldGYtaWNlLXRyaWNr
bGUuDQo+Pj4+Pj4gDQo+Pj4+Pj4gIEkgYXNzdW1lIFN1aGFzIG1lYW50IHNlcGFyYXRpbmcgdGhl
IFNEUCBzdHVmZiBmcm9tIHRoZSBTSVAgDQo+Pj4+Pj4gc3R1ZmYuIChJICBhbHNvIGFzc3VtZSBo
ZSB3aWxsIGNvcnJlY3QgbWUgaWYgSSBhbSB3cm9uZy4pDQo+Pj4+Pj4gDQo+Pj4+Pj4gDQo+Pj4+
Pj4gVGhhdCdzIHJpZ2h0IEJlbiAuLiBJIHdhcyBqdXN0IHRoaW5raW5nIG1pbmltYWwgbG9jYWxp
emVkIGNoYW5nZXMgDQo+Pj4+Pj4gKHRodXMgc21hbGwgdGltZSB0byBnZXQgbmV3IGRyYWZ0IGRv
bmUpIGFuZCB0aGVuIGFza2luZyB0cmlja2xlLCANCj4+Pj4+PiB0cmlja2xlLXNpcCB0byByZWZl
ciB0byB0aGUgbmV3IG9uZS4gKHdvcmsgZG9uZSB0byByZWZlciBpcyBtdWNoIA0KPj4+Pj4+IHNt
YWxsZXIgZm9yIHRoZXNlIGRyYWZ0cyB0aGF0IGFyZSBhdCB0aGUgdmVyeSBlbmQgb2YgYXBwcm92
YWwgDQo+Pj4+Pj4gam91cm5leSkNCj4+Pj4+PiANCj4+Pj4+PiBJIGRvIGFncmVlIHdpdGggQWRh
bSwgbm8gbWF0dGVyIHdoYXQgdmVyc2lvbiBvZiB0aGUgcHJvcG9zYWwgd2UgDQo+Pj4+Pj4gcGlj
aywgdGhlcmUgaXMgc29tZSB3b3JrIHRoYXQgbmVlZHMgdG8gYmUgZG9uZSBhbmQgd2Ugc2hvdWxk
IGRvIA0KPj4+Pj4+IGl0Lg0KPj4+Pj4gDQo+Pj4+PiBUaGVzZSBkb2N1bWVudHMgYXJlIG9uIHRo
ZSB0ZWxlY2hhdCB0b21vcnJvdy4gQXJlIHdlIHByb3Bvc2luZyB0byANCj4+Pj4+IGRlbGF5IGNv
bnNpZGVyYXRpb24gYnkgdGhlIElFU0cgd2hpbGUgd2UgZ2V0IHRoaXMgbWVzcyBzb3J0ZWQgb3V0
PyANCj4+Pj4+IDstKQ0KPj4+PiANCj4+Pj4gSGkgUGV0ZXIsDQo+Pj4+IA0KPj4+PiBJIGN1cnJl
bnRseSBwbGFuIHRvIGxlYXZlIGl0IG9uLiBXZSBtYXkgZGlzY3VzcyBhIHdheSBmb3J3YXJkIG9u
IA0KPj4+PiB0aGUgdGVsZWNoYXQuIEFsc28sIEnEhWQgbGlrZSB0byBnZXQgZmVlZGJhY2sgb24g
dGhlIHJlc3Qgb2YgdGhlIA0KPj4+PiBkcmFmdChzKSBmcm9tIHRoZSBvdGhlciBBRHMgc29vbmVy
IHRoYW4gbGF0ZXIuDQo+Pj4gDQo+Pj4gRGlkIHlvdSBkaXNjdXNzIHRoaXMgYXQgdGhlIHRlbGVj
aGF0Pw0KPj4+IA0KPj4+IEFueSBvdGhlciBkaXNjdXNzaW9ucyBvbiBob3cgdG8gbW92ZSBmb3J3
YXJkIHdpdGggdGhpcz8NCj4+IA0KPj4gWWVzLCBBZGFtIGFuZCBJIGhhdmUgYmVlbiBkaXNjdXNz
aW5nIHRoaXMgd2l0aCB0aGUgUlRDV0VCIGNoYWlycy4gV2XigJl2ZSBzaW5jZSBkaXNjb3ZlcmVk
IHRoYXQgdGhpcyBpcyBub3QgdGhlIG9ubHkgSlNFUCBub3JtYXRpdmUgcmVmZXJlbmNlIGNoYWlu
IGJhY2sgdG8gU0lQLiBUaGUgUlRDV0VCIGNoYWlycyBhcmUgY3VycmVudGx5IGRpc2N1c3Npbmcg
d2hldGhlciB0aGV5IGNhbiBsaXZlIHdpdGggdGhhdC4gVGhleSBtYXkgZGVjaWRlIHRvIGp1c3Qg
cmVmZXJlbmNlIHRoaW5ncyBhcyB0aGV5IHN0YW5kLiBJZiB0aGVpciBhbnN3ZXIgaW52b2x2ZXMg
YSByZXF1ZXN0IHRvIHJlc3RydWN0dXJlIGFueXRoaW5nLCBJIHdpbGwgcHVsbCBpbiB0aGUgYXV0
aG9ycyBhbmQgTU1VU0lDL0lDRSBjaGFpcnMuDQo+PiANCj4+IFRoYW5rcyENCj4+IA0KPj4gQmVu
Lg0KPj4gDQoNCg==


From nobody Sun Apr 15 00:49:51 2018
Return-Path: <thp@westhawk.co.uk>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5960A1275FD for <mmusic@ietfa.amsl.com>; Sun, 15 Apr 2018 00:49:44 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 7Z6MB_Hqe-AZ for <mmusic@ietfa.amsl.com>; Sun, 15 Apr 2018 00:49:42 -0700 (PDT)
Received: from smtp002.apm-internet.net (smtp002.apm-internet.net [85.119.248.221]) (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 670461275AB for <mmusic@ietf.org>; Sun, 15 Apr 2018 00:49:42 -0700 (PDT)
Received: (qmail 75467 invoked from network); 15 Apr 2018 07:22:59 -0000
X-APM-Authkey: 255286/0(159927/0) 31
Received: from unknown (HELO zimbra003.verygoodemail.com) (85.119.248.218) by smtp002.apm-internet.net with SMTP; 15 Apr 2018 07:22:59 -0000
Received: from localhost (localhost [127.0.0.1]) by zimbra003.verygoodemail.com (Postfix) with ESMTP id E51C818A04B3; Sun, 15 Apr 2018 08:22:58 +0100 (BST)
Received: from zimbra003.verygoodemail.com ([127.0.0.1]) by localhost (zimbra003.verygoodemail.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id maBFJt62cK91; Sun, 15 Apr 2018 08:22:58 +0100 (BST)
Received: from [192.168.0.3] (cable-82-119-15-228.cust.telecolumbus.net [82.119.15.228]) by zimbra003.verygoodemail.com (Postfix) with ESMTPSA id 23F9F18A049B; Sun, 15 Apr 2018 08:22:58 +0100 (BST)
From: westhawk <thp@westhawk.co.uk>
Message-Id: <251716DB-7292-4D75-8FD9-ABF2182302A1@westhawk.co.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7E54B455-3B2B-4CC5-B564-E76F3B84FF4D"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Sun, 15 Apr 2018 09:22:56 +0200
In-Reply-To: <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic WG <mmusic@ietf.org>, "ice@ietf.org" <ice@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
To: Ben Campbell <ben@nostrum.com>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com> <D6F67849.2DED5%christer.holmberg@ericsson.com> <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cfn4PlCe0YDaNy1HwEktnlJYV3A>
Subject: Re: [MMUSIC] [rtcweb] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 15 Apr 2018 07:49:44 -0000

--Apple-Mail=_7E54B455-3B2B-4CC5-B564-E76F3B84FF4D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 13 Apr 2018, at 16:56, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Yes, Adam and I have been discussing this with the RTCWEB chairs. =
We=E2=80=99ve since discovered that this is not the only JSEP normative =
reference chain back to SIP. The RTCWEB chairs are currently discussing =
whether they can live with that. They may decide to just reference =
things as they stand. If their answer involves a request to restructure =
anything, I will pull in the authors and MMUSIC/ICE chairs.
>=20
> Thanks!
>=20
> Ben.

For what it is worth, I=E2=80=99d argue we can live with it.
My thinking is that having a reference chain back to SIP in the =
documents reflects
the reality of RTCWeb 1.0 implementations. The SDP is there because it =
was believed
that using it would make interop with other (typically SIP based) =
systems easier.

Much of the actual implementations grew out of SIP heritage codebases.

I think it is only reasonable that the documents reflect this reality.

T.

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

--Apple-Mail=_7E54B455-3B2B-4CC5-B564-E76F3B84FF4D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><br =
class=3D""><div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 13 Apr 2018, at 16:56, Ben Campbell &lt;<a =
href=3D"mailto:ben@nostrum.com" class=3D"">ben@nostrum.com</a>&gt; =
wrote:</div><div class=3D""><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Yes, Adam and I have been discussing this with the RTCWEB =
chairs. We=E2=80=99ve since discovered that this is not the only JSEP =
normative reference chain back to SIP. The RTCWEB chairs are currently =
discussing whether they can live with that. They may decide to just =
reference things as they stand. If their answer involves a request to =
restructure anything, I will pull in the authors and MMUSIC/ICE =
chairs.</span><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><br style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;" class=3D""><span style=3D"caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none; float: none; display: inline !important;" =
class=3D"">Thanks!</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><br style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">Ben.</span><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""></div></blockquote><div><br =
class=3D""></div><div>For what it is worth, I=E2=80=99d argue we can =
live with it.</div><div>My thinking is that having a reference chain =
back to SIP in the documents reflects</div><div>the reality of RTCWeb =
1.0 implementations. The SDP is there because it was =
believed</div><div>that using it would make interop with other =
(typically SIP based) systems easier.</div><div><br =
class=3D""></div><div>Much of the actual implementations grew out of SIP =
heritage codebases.</div><div><br class=3D""></div><div>I think it is =
only reasonable that the documents reflect this reality.</div><div><br =
class=3D""></div><div>T.</div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><br style=3D"caret-color: rgb(0, 0, 0); =
font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;" class=3D""><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">rtcweb mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:rtcweb@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">rtcweb@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/rtcweb" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/rtcweb</a></div></blockqu=
ote></div><br class=3D""></body></html>=

--Apple-Mail=_7E54B455-3B2B-4CC5-B564-E76F3B84FF4D--


From nobody Sun Apr 15 08:36:27 2018
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 41BAC12D880 for <mmusic@ietfa.amsl.com>; Sun, 15 Apr 2018 08:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.33
X-Spam-Level: 
X-Spam-Status: No, score=-4.33 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_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R3lHjPeqB-wx for <mmusic@ietfa.amsl.com>; Sun, 15 Apr 2018 08:36:09 -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 6A359128954 for <mmusic@ietf.org>; Sun, 15 Apr 2018 08:36:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523806562; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ZR9MokGsnAl4K7SPzPqdCCmRtfAQHnv6mNaSef6r350=; b=fy7rD9jx8YQIKgfycYQtDW+8K8KsCgVg41DqEDSBxXapgwKspEKn3k4TWtj0Ype6 pfdSvSWswKFdazV1S2Y5n1VVZdzzg3Ohxk7Le0TZyzYILBIZbH25VkjSIJ0oqnxx u2qZwXlqW5GHXDfOxDrJthf3pRLFmdLp6ZK0JCPY9fU=;
X-AuditID: c1b4fb25-1c7ff7000000522b-8e-5ad3716244d6
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 01.EC.21035.26173DA5; Sun, 15 Apr 2018 17:36:02 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0382.000; Sun, 15 Apr 2018 17:36:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: westhawk <thp@westhawk.co.uk>, Ben Campbell <ben@nostrum.com>
CC: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic WG <mmusic@ietf.org>, "ice@ietf.org" <ice@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-trickle-ice-sip@ietf.org" <draft-ietf-mmusic-trickle-ice-sip@ietf.org>
Thread-Topic: [rtcweb] [MMUSIC] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
Thread-Index: AQHTy2yX73Ehi4UWF02QdXKK9x8zEKPvKNAAgAAAqICAAAKUAIAAAkMAgAAC5ICAAAKPAIAABSyAgAABrACAAA6TAIAAAI6AgAAWLYCAAUXTgIAAFRIAgA3/bYD///x6AIACphEAgACqduA=
Date: Sun, 15 Apr 2018 15:36:01 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E74697@ESESSMB109.ericsson.se>
References: <152274059303.13991.7963954297164952826.idtracker@ietfa.amsl.com> <abc6dbc9-5500-bf51-c003-c4d9affe612f@mozilla.com> <E24F839C-DC79-41DA-8742-33F2EB9634BC@nostrum.com> <ba4a3f03-9180-4b30-c672-b893fc19d241@nostrum.com> <CABcZeBPQ32XX1j1a0VCuytC+mv9b7Gv_uNK5kbufPfOMGxPw-A@mail.gmail.com> <F5C281C6-2B72-4B33-AACC-DA8E7B43CB94@nostrum.com> <CABcZeBMNFxJ+OjffyFOSB4YPg+i9YTTC+KetqL-6HtO0BHsY+w@mail.gmail.com> <BDA42C0E-1CBC-4F1D-860B-A5BD513362F7@nostrum.com> <6b2e132d-88ee-9274-b19d-c24937e46ad2@nostrum.com> <CAMRcRGTWTqNfO_v911JN4wcWtyd8TXQFgp_rR9z13ug=YQWtWA@mail.gmail.com> <CAMRcRGROerxxcS-9KUAt6rfceWBL=GJ9GrhjzJAC4Q17p7gcLw@mail.gmail.com> <07de7983-293d-f97e-8ca9-08713ce48e1c@mozilla.com> <3E157C5A-A2CD-4361-9BFE-B87EA71D8FFD@nostrum.com> <CAMRcRGRcMZim6J+Ts-wSrbPzjrr3c6m9gBkKosk1Xi56UuLusQ@mail.gmail.com> <dfce4246-b000-3421-25a4-844f6865053c@mozilla.com> <8BBC3434-DEA2-437B-AB32-DA113AE085AA@nostrum.com> <D6F67849.2DED5%christer.holmberg@ericsson.com> <A5F42D69-6ECB-4A03-8A54-F081624F13D0@nostrum.com> <251716DB-7292-4D75-8FD9-ABF2182302A1@westhawk.co.uk>
In-Reply-To: <251716DB-7292-4D75-8FD9-ABF2182302A1@westhawk.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.171]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72E74697ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2K7im5S4eUogzmLjCzmd55mt/ixdjmz xbcLtRYz/kxktji/cz2TxdTlj1ks1v5rZ7dY9/4YiwOHx5IlP5k8Zu18wuJxcdp+pgDmKC6b lNSczLLUIn27BK6MdbMmsRY8yKxo+PeLpYHxQ1oXIyeHhICJxOXWS8xdjFwcQgJHGCUOrt3G AuEsZpR4OecsWxcjBwebgIVE9z9tkAYRAUeJy33zWEFsZoHJTBKvf0qA2MIClRKX7p5jhKip klhz6jfYUBGBeYwSZ+dvYANJsAioSjTMvckEYvMK+Er8nbIXavNDDonOU1vBijgFnCRuzroL VsQoICbx/dQaJoht4hK3nsxngjhbQGLJnvPMELaoxMvH/1ghbCWJEw8bmSHq8yX+3HjBArFM UOLkzCcsExhFZiEZNQtJ2SwkZbOAfmYW0JRYv0sfokRRYkr3Q3YIW0Oidc5cdmTxBYzsqxhF i1OLk3LTjYz1Uosyk4uL8/P08lJLNjECo/Pglt+qOxgvv3E8xCjAwajEwzs5+3KUEGtiWXFl 7iFGCQ5mJRHeZYlAId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwPzTdHCQmkJ5akZqemFqQWwWSZ ODilGhilXvFNuZP4L+Lx1pVZb/5Pu1S4RbeiM54jVVHojJ2d0Y7UpyErthxpXs9gG1BiVsef kPM6KF5vQXT59GurzLcvixFcc7xa7ier2Eqn5xPk7obXZM25dolTRuN145W/Khtv1j5aL8sv nz1pFoNveHq2WGzmwS3MLzyP/jxX+7r/cMPkTgOzJTxKLMUZiYZazEXFiQCBjDpCygIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JzHkZOgiamnu7IjXDGZz-JDFDMw>
Subject: Re: [MMUSIC] [rtcweb] Adam Roach's Discuss on draft-ietf-mmusic-trickle-ice-sip-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 15 Apr 2018 15:36:13 -0000

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

SGksDQoNCkFzIGZhciBhcyB0aGUgTU1VU0lDIElDRSBhbmQgdHJpY2tsZS1JQ0UgZHJhZnRzIGFy
ZSBjb25jZXJuZWQsIGNhbuKAmXQgd2Ugc2ltcGx5IGFkZCBhIHNlbnRlbmNlIHRvIGVhY2ggb2Yg
dGhvc2UgZHJhZnRzIHNheWluZyBzb21ldGhpbmcgbGlrZToNCg0K4oCcVGhlIFNJUCBwcm9jZWR1
cmVzIGFuZCByZXF1aXJlbWVudHMgaW4gdGhpcyBzcGVjaWZpY2F0aW9uIGRvIG5vdCBhcHBseSB0
byBzY2VuYXJpb3Mgd2hlcmUgdGhlIFNEUCBvZmZlci9hbnN3ZXIgcHJvY2VkdXJlcyBhcmUgdXNl
ZCB3aXRoIG90aGVyIHByb3RvY29scyBhbmQgQVBJcyB0aGFuIFNJUC7igJ0NCg0KUHJvYmxlbSBz
b2x2ZWQ/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCkZyb206IHdlc3RoYXdrIFttYWlsdG86
dGhwQHdlc3RoYXdrLmNvLnVrXQ0KU2VudDogMTUgQXByaWwgMjAxOCAwOToyMw0KVG86IEJlbiBD
YW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPg0KQ2M6IENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rl
ci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+OyBtbXVzaWMtY2hhaXJzQGlldGYub3JnOyBtbXVzaWMg
V0cgPG1tdXNpY0BpZXRmLm9yZz47IGljZUBpZXRmLm9yZzsgcnRjd2ViQGlldGYub3JnOyBUaGUg
SUVTRyA8aWVzZ0BpZXRmLm9yZz47IGRyYWZ0LWlldGYtbW11c2ljLXRyaWNrbGUtaWNlLXNpcEBp
ZXRmLm9yZw0KU3ViamVjdDogUmU6IFtydGN3ZWJdIFtNTVVTSUNdIEFkYW0gUm9hY2gncyBEaXNj
dXNzIG9uIGRyYWZ0LWlldGYtbW11c2ljLXRyaWNrbGUtaWNlLXNpcC0xNDogKHdpdGggRElTQ1VT
UyBhbmQgQ09NTUVOVCkNCg0KDQoNCg0KT24gMTMgQXByIDIwMTgsIGF0IDE2OjU2LCBCZW4gQ2Ft
cGJlbGwgPGJlbkBub3N0cnVtLmNvbTxtYWlsdG86YmVuQG5vc3RydW0uY29tPj4gd3JvdGU6DQoN
ClllcywgQWRhbSBhbmQgSSBoYXZlIGJlZW4gZGlzY3Vzc2luZyB0aGlzIHdpdGggdGhlIFJUQ1dF
QiBjaGFpcnMuIFdl4oCZdmUgc2luY2UgZGlzY292ZXJlZCB0aGF0IHRoaXMgaXMgbm90IHRoZSBv
bmx5IEpTRVAgbm9ybWF0aXZlIHJlZmVyZW5jZSBjaGFpbiBiYWNrIHRvIFNJUC4gVGhlIFJUQ1dF
QiBjaGFpcnMgYXJlIGN1cnJlbnRseSBkaXNjdXNzaW5nIHdoZXRoZXIgdGhleSBjYW4gbGl2ZSB3
aXRoIHRoYXQuIFRoZXkgbWF5IGRlY2lkZSB0byBqdXN0IHJlZmVyZW5jZSB0aGluZ3MgYXMgdGhl
eSBzdGFuZC4gSWYgdGhlaXIgYW5zd2VyIGludm9sdmVzIGEgcmVxdWVzdCB0byByZXN0cnVjdHVy
ZSBhbnl0aGluZywgSSB3aWxsIHB1bGwgaW4gdGhlIGF1dGhvcnMgYW5kIE1NVVNJQy9JQ0UgY2hh
aXJzLg0KDQpUaGFua3MhDQoNCkJlbi4NCg0KRm9yIHdoYXQgaXQgaXMgd29ydGgsIEnigJlkIGFy
Z3VlIHdlIGNhbiBsaXZlIHdpdGggaXQuDQpNeSB0aGlua2luZyBpcyB0aGF0IGhhdmluZyBhIHJl
ZmVyZW5jZSBjaGFpbiBiYWNrIHRvIFNJUCBpbiB0aGUgZG9jdW1lbnRzIHJlZmxlY3RzDQp0aGUg
cmVhbGl0eSBvZiBSVENXZWIgMS4wIGltcGxlbWVudGF0aW9ucy4gVGhlIFNEUCBpcyB0aGVyZSBi
ZWNhdXNlIGl0IHdhcyBiZWxpZXZlZA0KdGhhdCB1c2luZyBpdCB3b3VsZCBtYWtlIGludGVyb3Ag
d2l0aCBvdGhlciAodHlwaWNhbGx5IFNJUCBiYXNlZCkgc3lzdGVtcyBlYXNpZXIuDQoNCk11Y2gg
b2YgdGhlIGFjdHVhbCBpbXBsZW1lbnRhdGlvbnMgZ3JldyBvdXQgb2YgU0lQIGhlcml0YWdlIGNv
ZGViYXNlcy4NCg0KSSB0aGluayBpdCBpcyBvbmx5IHJlYXNvbmFibGUgdGhhdCB0aGUgZG9jdW1l
bnRzIHJlZmxlY3QgdGhpcyByZWFsaXR5Lg0KDQpULg0KDQoNCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCnJ0Y3dlYiBtYWlsaW5nIGxpc3QNCnJ0Y3dl
YkBpZXRmLm9yZzxtYWlsdG86cnRjd2ViQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9ydGN3ZWINCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAx
NSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFs
LCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIixzZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K
YTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFu
LkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZh
dWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4w
cHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRT
ZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVk
ZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0t
PjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0K
PG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+
PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1ZSIgdmxp
bms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+QXMgZmFy
IGFzIHRoZSBNTVVTSUMgSUNFIGFuZCB0cmlja2xlLUlDRSBkcmFmdHMgYXJlIGNvbmNlcm5lZCwg
Y2Fu4oCZdCB3ZSBzaW1wbHkgYWRkIGEgc2VudGVuY2UgdG8gZWFjaCBvZiB0aG9zZSBkcmFmdHMg
c2F5aW5nIHNvbWV0aGluZw0KIGxpa2U6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj7igJxUaGUgU0lQIHByb2NlZHVyZXMgYW5kIHJlcXVpcmVtZW50cyBpbiB0aGlzIHNw
ZWNpZmljYXRpb24gZG8gbm90IGFwcGx5IHRvIHNjZW5hcmlvcyB3aGVyZSB0aGUgU0RQIG9mZmVy
L2Fuc3dlciBwcm9jZWR1cmVzIGFyZSB1c2VkDQogd2l0aCBvdGhlciBwcm90b2NvbHMgYW5kIEFQ
SXMgdGhhbiBTSVAu4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5Q
cm9ibGVtIHNvbHZlZD88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlJl
Z2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5DaHJpc3Rlcjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWls
RW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvYT48L3A+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWYiPiB3ZXN0aGF3ayBbbWFpbHRvOnRocEB3ZXN0aGF3ay5jby51a10NCjxicj4NCjxi
PlNlbnQ6PC9iPiAxNSBBcHJpbCAyMDE4IDA5OjIzPGJyPg0KPGI+VG86PC9iPiBCZW4gQ2FtcGJl
bGwgJmx0O2JlbkBub3N0cnVtLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IENocmlzdGVyIEhvbG1i
ZXJnICZsdDtjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20mZ3Q7OyBtbXVzaWMtY2hhaXJz
QGlldGYub3JnOyBtbXVzaWMgV0cgJmx0O21tdXNpY0BpZXRmLm9yZyZndDs7IGljZUBpZXRmLm9y
ZzsgcnRjd2ViQGlldGYub3JnOyBUaGUgSUVTRyAmbHQ7aWVzZ0BpZXRmLm9yZyZndDs7IGRyYWZ0
LWlldGYtbW11c2ljLXRyaWNrbGUtaWNlLXNpcEBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9i
PiBSZTogW3J0Y3dlYl0gW01NVVNJQ10gQWRhbSBSb2FjaCdzIERpc2N1c3Mgb24gZHJhZnQtaWV0
Zi1tbXVzaWMtdHJpY2tsZS1pY2Utc2lwLTE0OiAod2l0aCBESVNDVVNTIGFuZCBDT01NRU5UKTxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCjxicj4NCjxvOnA+
PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJv
dHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gMTMgQXByIDIwMTgs
IGF0IDE2OjU2LCBCZW4gQ2FtcGJlbGwgJmx0OzxhIGhyZWY9Im1haWx0bzpiZW5Abm9zdHJ1bS5j
b20iPmJlbkBub3N0cnVtLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBw
dDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PGJyPg0KWWVz
LCBBZGFtIGFuZCBJIGhhdmUgYmVlbiBkaXNjdXNzaW5nIHRoaXMgd2l0aCB0aGUgUlRDV0VCIGNo
YWlycy4gV2XigJl2ZSBzaW5jZSBkaXNjb3ZlcmVkIHRoYXQgdGhpcyBpcyBub3QgdGhlIG9ubHkg
SlNFUCBub3JtYXRpdmUgcmVmZXJlbmNlIGNoYWluIGJhY2sgdG8gU0lQLiBUaGUgUlRDV0VCIGNo
YWlycyBhcmUgY3VycmVudGx5IGRpc2N1c3Npbmcgd2hldGhlciB0aGV5IGNhbiBsaXZlIHdpdGgg
dGhhdC4gVGhleSBtYXkgZGVjaWRlIHRvIGp1c3QNCiByZWZlcmVuY2UgdGhpbmdzIGFzIHRoZXkg
c3RhbmQuIElmIHRoZWlyIGFuc3dlciBpbnZvbHZlcyBhIHJlcXVlc3QgdG8gcmVzdHJ1Y3R1cmUg
YW55dGhpbmcsIEkgd2lsbCBwdWxsIGluIHRoZSBhdXRob3JzIGFuZCBNTVVTSUMvSUNFIGNoYWly
cy48YnI+DQo8YnI+DQpUaGFua3MhPGJyPg0KPGJyPg0KQmVuLjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Rm9yIHdoYXQgaXQgaXMgd29ydGgsIEnigJlkIGFyZ3VlIHdlIGNhbiBsaXZlIHdpdGggaXQuPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5NeSB0aGlu
a2luZyBpcyB0aGF0IGhhdmluZyBhIHJlZmVyZW5jZSBjaGFpbiBiYWNrIHRvIFNJUCBpbiB0aGUg
ZG9jdW1lbnRzIHJlZmxlY3RzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj50aGUgcmVhbGl0eSBvZiBSVENXZWIgMS4wIGltcGxlbWVudGF0aW9ucy4g
VGhlIFNEUCBpcyB0aGVyZSBiZWNhdXNlIGl0IHdhcyBiZWxpZXZlZDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+dGhhdCB1c2luZyBpdCB3b3VsZCBt
YWtlIGludGVyb3Agd2l0aCBvdGhlciAodHlwaWNhbGx5IFNJUCBiYXNlZCkgc3lzdGVtcyBlYXNp
ZXIuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
Pk11Y2ggb2YgdGhlIGFjdHVhbCBpbXBsZW1lbnRhdGlvbnMgZ3JldyBvdXQgb2YgU0lQIGhlcml0
YWdlIGNvZGViYXNlcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+SSB0aGluayBpdCBpcyBvbmx5IHJlYXNvbmFibGUgdGhhdCB0aGUgZG9jdW1l
bnRzIHJlZmxlY3QgdGhpcyByZWFsaXR5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5ULjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxicj4NCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KcnRjd2ViIG1haWxpbmcgbGlzdDxi
cj4NCjwvc3Bhbj48YSBocmVmPSJtYWlsdG86cnRjd2ViQGlldGYub3JnIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjkuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNl
cmlmIj5ydGN3ZWJAaWV0Zi5vcmc8L3NwYW4+PC9hPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxicj4NCjwv
c3Bhbj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3J0Y3dl
YiI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRp
Y2EmcXVvdDssc2Fucy1zZXJpZiI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9ydGN3ZWI8L3NwYW4+PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B72E74697ESESSMB109erics_--


From nobody Mon Apr 16 05:25:47 2018
Return-Path: <aamelnikov@fastmail.fm>
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 2EF3F126E64; Mon, 16 Apr 2018 05:25:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org,  fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152388154018.20846.5464685108645943278.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 05:25:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/L0MuyePxPzd7VQ31XVlOJ-rfbbQ>
Subject: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 12:25:40 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-mmusic-sdp-bundle-negotiation-49: 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-bundle-negotiation/



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

Please add a reference on first mention of UTF-8.



From nobody Mon Apr 16 05:33:47 2018
Return-Path: <aamelnikov@fastmail.fm>
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 4E4121241FC; Mon, 16 Apr 2018 05:33:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152388202529.20918.5276930624330307536.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 05:33:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1v7qDkKz9uJ3-89xTGWekV0ZH8U>
Subject: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-rid-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 12:33:45 -0000

Alexey Melnikov has entered the following ballot position for
draft-ietf-mmusic-rid-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-rid/



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

The document is generally fine, but I have a few minor comments:

In the ABNF:

   rid-width-param   = "max-width" [ "=" int-param-val ]

   rid-height-param  = "max-height" [ "=" int-param-val ]

   rid-fps-param     = "max-fps" [ "=" int-param-val ]

   rid-fs-param      = "max-fs" [ "=" int-param-val ]

   rid-br-param      = "max-br" [ "=" int-param-val ]

   rid-pps-param     = "max-pps" [ "=" int-param-val ]

   rid-bpp-param     = "max-bpp" [ "=" float-param-val ]

Maybe I missed that, but what is the meaning of "max-width" (and others) with
no value? Or to rephrase that: are the values really optional?

12.2.  Registry for RID-Level Parameters

   New restriction registrations are accepted according to the
   "Specification Required" policy of [RFC5226], provided that the
   specification includes the following information:

   o  contact name, email address, and telephone number

Considering the European GDPR directive is going to come into force in May: is
there any legitimate use for collecting phone numbers for this registry?

   o  restriction name (as it will appear in SDP)

   o  long-form restriction name in English

   o  whether the restriction value is subject to the charset attribute

   o  an explanation of the purpose of the restriction

   o  a specification of appropriate attribute values for this
      restriction

   o  an ABNF definition of the restriction

   The initial set of "a=rid" restriction names, with definitions in
   Section 5 of this document, is given below:

     RID Parameter Name           Reference
     ------------------           ---------
     max-width                    [RFCXXXX]
     max-height                   [RFCXXXX]
     max-fps                      [RFCXXXX]
     max-fs                       [RFCXXXX]
     max-br                       [RFCXXXX]
     max-pps                      [RFCXXXX]
     max-bpp                      [RFCXXXX]
     depend                       [RFCXXXX]

And now you just registered them without following your registration template
that you've specified above ;-).



From nobody Mon Apr 16 05:36:54 2018
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 B903F12D87B for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 05:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dacaMJ_iyniS for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 05:36:43 -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 E3DA31241FC for <mmusic@ietf.org>; Mon, 16 Apr 2018 05:36:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523882201; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=qhlQhTXIVbv0N9ax9DaL0NroNY1be8IPsCjxyttlyaQ=; b=ZHB5/E/Q0mfgPpp1giGCoXXMb1OUAMRazyPZ8+Zyqpw0tDx14lzpvEB6mtRO7HBI NC9LC2bzXTccYhmE3G+15207ysp+h0ZhrH+7Q+7AbtuQIR+Vffkp0Dlyri30P8mw /ioGSwTzob66aeaewra1/WZwTZ7EsELB1SheZL3cukA=;
X-AuditID: c1b4fb2d-bf68e9c000003563-7e-5ad498d9910d
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 1E.DA.13667.9D894DA5; Mon, 16 Apr 2018 14:36:41 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Mon, 16 Apr 2018 14:36:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Alexey Melnikov's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1X4JLgvHg6rfEEqUP6xZpUZBK6QDZXQA
Date: Mon, 16 Apr 2018 12:36:40 +0000
Message-ID: <D6FA71B8.2E036%christer.holmberg@ericsson.com>
References: <152388154018.20846.5464685108645943278.idtracker@ietfa.amsl.com>
In-Reply-To: <152388154018.20846.5464685108645943278.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D9582B74D7CEDF4BAD83D5F8AD3FE03C@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2K7uu7NGVeiDP7+ErDY//4Qk8X0We/Y LN5f0LWY8Wcis8X5neuZLKYuf8ziwOYx5fdGVo+dpw6weSxZ8pMpgDmKyyYlNSezLLVI3y6B K2P9G76CDywVq76fY2tgbGPpYuTkkBAwkbj56AtjFyMXh5DAEUaJWZt/skA4ixklvvXdBXI4 ONgELCS6/2mDmCICbhIPrzuClDALfGGUePb5KCPIIGGBHIkdkzaxQdTkSmycqw0SFhEwkrj7 9TJYCYuAqkTv3VawvbwC1hLfN7xlB7GFBHwltl5ZxwRicwr4SbSv6AaLMwqISXw/tQYsziwg LnHryXwmiJsFJJbsOc8MYYtKvHz8jxXEFhXQk9hw4jY7yAkSAkoStzc4QbTqSCzY/YkNwraW WHL4GNRIbYllC18zQ5wjKHFy5hOWCYzis5Bsm4WkfRaS9llI2mchaV/AyLqKUbQ4tbg4N93I WC+1KDO5uDg/Ty8vtWQTIzAyD275rbuDcfVrx0OMAhyMSjy87l1XooRYE8uKK3MPMUpwMCuJ 8C5LvBwlxJuSWFmVWpQfX1Sak1p8iFGag0VJnFdv1Z4oIYH0xJLU7NTUgtQimCwTB6dUAyOn pnPL+v2e/Zsvab+YHVkfHrkiw+zePq+vKuZXZ87keOKn/0Li5OmUgGk8u+r9f5qwifbO1++3 vS3x3T9sYUXy+bNc3Ib6bSdze5UeH0x+n/h+75HJP7daP6xY3R3n48/Kni1/ILA7xPOStI/j yZDt7yx0r0SWMaVd5lyxvu+VD/djg7NHspVYijMSDbWYi4oTAYiO91XIAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GeAB_-owCwNCDlrawW0W6hpJZlA>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 12:36:50 -0000

Hi Alexey,

Thank You for your review! Please see inline.

>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>Please add a reference on first mention of UTF-8.

I will add a reference.

Just to verify, it shall be a reference to the unicode standard of the
unicode consortium?

    "The Unicode Consortium. The Unicode Standard, Version 10.0.0,
(Mountain View, CA: The Unicode Consortium, 2017. ISBN 978-1-936213-16-0)
     http://www.unicode.org/versions/Unicode10.0.0/"


Regards,

Christer


From nobody Mon Apr 16 06:11:42 2018
Return-Path: <aamelnikov@fastmail.fm>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A39412D96A; Mon, 16 Apr 2018 06:11: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=fastmail.fm header.b=RuafLKUh; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=SAjJSmt3
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XFUcOnxJeXyP; Mon, 16 Apr 2018 06:11:27 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A38D12D95A; Mon, 16 Apr 2018 06:11:27 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id ED8A12115C; Mon, 16 Apr 2018 09:11:26 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute7.internal (MEProxy); Mon, 16 Apr 2018 09:11:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=8V9Nc+PBO3pB4Hno8afiR+2wuLf8l HMZk6y8Hlve7Ek=; b=RuafLKUhreiLUk7uTGcnINCvmnQozYYzMTKH3FnaF2NP5 K6y00WPkJhTS7xW83NgJZDqirmLKOKO+dQiiJqJvD091Oa+2YULfSzJrFT5pqJQF SIERb3ryDblnLUFGDrWEjFlnB7zsaoSOaMnvD1CFQEfxxNI9CJxPbn3m4AM6a7b5 weE8B5djQSGrAnt5zZnlZq7IYeX/acH+XsD8RZa33f8AeIf0qxyCAbFqF8tb8/HY mRTjELGYSrdCLb9i7kbF2SrOYRWVU97SfBt6tvPp74fSH0wwNeuHW31+xi+FygOQ xDTaWogRSruyovotZLuwx5qkBeiWorM3UaiBipSAw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=8V9Nc+ PBO3pB4Hno8afiR+2wuLf8lHMZk6y8Hlve7Ek=; b=SAjJSmt3dXGxxTcqnjrLtc H7RRe7tkeikFIaSQZOVJQMtqJ1Qo7cmk65AJQZB/wyUovUoPYoNRRwsJaDL+bG0P smxzven+WeinUyzy0DBNnm5CijABGWhcSZrC+loKs8NKdLD7rzElwHpOdaomm6sx xU9ZAugnZXUxuEHnHXfmp3YBcGP6OrtDoGTdkyG6xLLKvoRsovsxD9saVmNiiwhL 7V24hhs5NWjjs9k6KiuONjjcz3O6BpHFnHKFLVl3g0T2kB2lPHf1+xmfQToNQdEa Dvygn8Pm1Q9V37Ydc1yrEtS61yc8gRNn08MKRzcGrma1rS66iTKRbPKbnU6ri26w ==
X-ME-Sender: <xms:_qDUWuOd7kLGG9n4AXpxvux5SBBFSiUB16p9dCAk8nHnM7X8cAvgvg>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id C1FE89E0BD; Mon, 16 Apr 2018 09:11:26 -0400 (EDT)
Message-Id: <1523884286.3222363.1339568992.41C57BFE@webmail.messagingengine.com>
From: Alexey Melnikov <aamelnikov@fastmail.fm>
To: Christer Holmberg <christer.holmberg@ericsson.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-f2937c11
References: <152388154018.20846.5464685108645943278.idtracker@ietfa.amsl.com> <D6FA71B8.2E036%christer.holmberg@ericsson.com>
Date: Mon, 16 Apr 2018 14:11:26 +0100
In-Reply-To: <D6FA71B8.2E036%christer.holmberg@ericsson.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5BKtrmE18-k85TEgoA2GZbqt0EE>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 13:11:31 -0000

Hi Christer,

On Mon, Apr 16, 2018, at 1:36 PM, Christer Holmberg wrote:
> Hi Alexey,
> 
> Thank You for your review! Please see inline.
> 
> >----------------------------------------------------------------------
> >COMMENT:
> >----------------------------------------------------------------------
> >
> >Please add a reference on first mention of UTF-8.
> 
> I will add a reference.
> 
> Just to verify, it shall be a reference to the unicode standard of the
> unicode consortium?
> 
>     "The Unicode Consortium. The Unicode Standard, Version 10.0.0,
> (Mountain View, CA: The Unicode Consortium, 2017. ISBN 978-1-936213-16-0)
>      http://www.unicode.org/versions/Unicode10.0.0/"

No, RFC 3629, which is an Internet Standard.

Best Regards,
Alexey


From nobody Mon Apr 16 06:16:23 2018
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 5FDB9126E64 for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 06:16:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ge37isM7uGzd for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 06:16:17 -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 50808127522 for <mmusic@ietf.org>; Mon, 16 Apr 2018 06:16:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523884572; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ohBDP4lr+JThaVrFlCxq2HMJD9ouVKKbmTR2Oy0/Eq4=; b=CGh5KC8QPCBsanj22ti06ab915Fu+VzvY5C0LWnvXlt3W1zMqiMRhIzQ6FkoeoPM qJ9Xzq2RPy27OSLREjAtL6yKybekCtaQHuNIwP3IL1bmsEVc15ZioKH/7X6VZv7g TRZ0BBEKfMQ8h7tBlyWVeW/JXYPqi/S9xGv96vj+yHc=;
X-AuditID: c1b4fb30-1ebff70000005970-4d-5ad4a21c141e
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id C6.F3.22896.C12A4DA5; Mon, 16 Apr 2018 15:16:12 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0382.000; Mon, 16 Apr 2018 15:16:12 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alexey Melnikov <aamelnikov@fastmail.fm>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Alexey Melnikov's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1X4JLgvHg6rfEEqUP6xZpUZBK6QDZXQA///W4gCAADQogA==
Date: Mon, 16 Apr 2018 13:16:11 +0000
Message-ID: <D6FA7D28.2E055%christer.holmberg@ericsson.com>
References: <152388154018.20846.5464685108645943278.idtracker@ietfa.amsl.com> <D6FA71B8.2E036%christer.holmberg@ericsson.com> <1523884286.3222363.1339568992.41C57BFE@webmail.messagingengine.com>
In-Reply-To: <1523884286.3222363.1339568992.41C57BFE@webmail.messagingengine.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3C7243E42E25CD4997EA71EC57AF86C7@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2K7t67MoitRBkvf6lrsf3+IyWL6rHds Fu8v6FrM+DOR2eL8zvVMFlOXP2ZxYPOY8nsjq8fOUwfYPJYs+ckUwBzFZZOSmpNZllqkb5fA lXG/7RVrwVPWiv/rt7E3MD5i6WLk5JAQMJGYsn8SkM3FISRwhFGiadkKZghnMaPEyzOzWLsY OTjYBCwkuv9pg5giAm4SD687gpQwC3xhlHj2+SgjyCBhgRyJHZM2sUHU5EpsnKsNEhYRcJJY 8GMDK4jNIqAqcfPGRWYQm1fAWmL52utMEKuOMUp8WniXCSTBKRAosXjjcrCZjAJiEt9PrQGL MwuIS9x6Mp8J4mgBiSV7zjND2KISLx//A1sgKqAnseHEbXaQGyQElCRub3CCaNWRWLD7ExuE bS2xecZnVghbW2LZwtdQ9whKnJz5hGUCo/gsJNtmIWmfhaR9FpL2WUjaFzCyrmIULU4tTspN NzLSSy3KTC4uzs/Ty0st2cQIjM6DW34b7GB8+dzxEKMAB6MSD69B55UoIdbEsuLK3EOMEhzM SiK8yxIvRwnxpiRWVqUW5ccXleakFh9ilOZgURLntfDbHCUkkJ5YkpqdmlqQWgSTZeLglGpg zAotvOGaVWCosUJr/7bN22Z83dg+0eFko+UfsRVN/IUlGy+/MGdIidxjpWOcX+GT3eav6rwu 1/UEb+i/3/9NlJOydKPmviiO2jpzd4VW98Hl59V59ZNf9b6tfea7/9GmOeuXrv556eVKneOv V623WPB1BuM6P73GmVz7le5Nvb5kC/+Nvuq3LEosxRmJhlrMRcWJAPMEDHzKAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ZPXTWMXdzNNVJXTUwUgt_OZHmWg>
Subject: Re: [MMUSIC] Alexey Melnikov's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 13:16:18 -0000

Hi,

>>Thank You for your review! Please see inline.
>>=20
>> >----------------------------------------------------------------------
>> >COMMENT:
>> >----------------------------------------------------------------------
>> >
>> >Please add a reference on first mention of UTF-8.
>>=20
>> I will add a reference.
>>=20
>> Just to verify, it shall be a reference to the unicode standard of the
>> unicode consortium?
>>=20
>>     "The Unicode Consortium. The Unicode Standard, Version 10.0.0,
>> (Mountain View, CA: The Unicode Consortium, 2017. ISBN
>>978-1-936213-16-0)
>>      http://www.unicode.org/versions/Unicode10.0.0/"
>
>No, RFC 3629, which is an Internet Standard.

Gotha. Thanks!

Regards,

Christer


From nobody Mon Apr 16 07:43:39 2018
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 C044012DA02; Mon, 16 Apr 2018 07:43:32 -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>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org,  fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152388981277.20891.5120775227766869176.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 07:43:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qLlZRLPIJyLjbqfflm56aeKwhcM>
Subject: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 14:43:33 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-mmusic-sdp-bundle-negotiation-49: 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-bundle-negotiation/



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

Thanks for doing this work. It's important.

I wonder if it's worth adding a mention of https://tools.ietf.org/html/rfc7657
as an Informational reference, because bundling makes it easier for you to
shoot yourself in the foot by using different DSCP codepoints for different
packets carried on a single 5-tuple.

If there's a better document to point that out to people who are considering
using bundling for their applications, that's a fine answer ...



From nobody Mon Apr 16 08:25:58 2018
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 C1C7B12E056 for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 08:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.331
X-Spam-Level: 
X-Spam-Status: No, score=-4.331 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gQVBlkgpN9LJ for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 08:25:51 -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 9462212E854 for <mmusic@ietf.org>; Mon, 16 Apr 2018 08:25:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523892348; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=aw6MbNC39wGaaCp5R9XaTS0OZyPfGGLeXA6QfPhJwhM=; b=f1S+WkTR2VcZYMu2K/lj42gzngp3pQrq+CLdzkdVouZp2/yu+NBBsupHi47toeJg pEcsjt3yHii+5Jvro9D9LKpvO5WpjYzz0aF7KZNyHUo+KDoMFv7SBoC+3qafijnz RlUs11tpAdJ8riPPLAKPg2QhtoP5rbKc/9qId4YuaTI=;
X-AuditID: c1b4fb25-1dfff7000000522b-2f-5ad4c07b0aa3
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 44.55.21035.B70C4DA5; Mon, 16 Apr 2018 17:25:48 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Mon, 16 Apr 2018 17:25:47 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1ZFMzBNS0LUxI06sGFjMrf6dGaQDgJ4Q
Date: Mon, 16 Apr 2018 15:25:47 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E7CE99@ESESSMB109.ericsson.se>
References: <152388981277.20891.5120775227766869176.idtracker@ietfa.amsl.com>
In-Reply-To: <152388981277.20891.5120775227766869176.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.170]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7um7NgStRBo9vc1lMn/WOzeL9BV2L GX8mMluc37meyWLq8scsFsum7GF2YPOY8nsjq8fOWXfZPZYs+ckUwBzFZZOSmpNZllqkb5fA lbFn2lu2gk/sFV/PvWRqYLzB3sXIySEhYCJxuGsjSxcjF4eQwBFGiY/TzzBBOIsZJV5fWAWU 4eBgE7CQ6P6nDdIgIuArcWXyUjaQGmaBL4wSzz4fZQRJCAskSRz/1scGUZQscfX1fFYI20ji 4o5/YNtYBFQlrq36DVbDCzSoa8MfMFsIyP7e8ZkJxOYU8JOY8eUvmM0oICbx/dQaMJtZQFzi 1pP5TBBXC0gs2XOeGcIWlXj5+B8rhK0kcWbTc7CbmQU0Jdbv0odoVZSY0v2QHWKtoMTJmU9Y JjCKzkIydRZCxywkHbOQdCxgZFnFKFqcWpyUm25krJdalJlcXJyfp5eXWrKJERhVB7f8Vt3B ePmN4yFGAQ5GJR7emQuvRAmxJpYVV+YeYpTgYFYS4S3YCRTiTUmsrEotyo8vKs1JLT7EKM3B oiTO+9B8c5SQQHpiSWp2ampBahFMlomDU6qBMfvFwcnrrxx91XM6fobtf77At6/cu55JhbkX JgZzavR3/BZ33hZuIn8qnOfjsdJirwnOUwRD9v21m/OIpfa4wM3HKnfaMy7ZNfnf/Cf60Zz1 x/SqzvjdW/n3lnbeTTn3dltM3baTwamlvfLHt69utJfMrl84XeUcM8O8gjmV6yydl4Yb77LJ V2Ipzkg01GIuKk4EACgFDIGmAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0yGyTrlfSE9lDh-C01E_IEhgcBI>
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 15:25:53 -0000

SGkgU3BlbmNlciwNCg0KVGhhbmsgWW91IGZvciB0aGUgcmV2aWV3ISBQbGVhc2Ugc2VlIGlubGlu
ZS4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KQ09NTUVOVDoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KPiBUaGFua3Mg
Zm9yIGRvaW5nIHRoaXMgd29yay4gSXQncyBpbXBvcnRhbnQuDQoNClRoYW5rcyEgOikNCg0KPiBJ
IHdvbmRlciBpZiBpdCdzIHdvcnRoIGFkZGluZyBhIG1lbnRpb24gb2YgaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL3JmYzc2NTcNCj4gYXMgYW4gSW5mb3JtYXRpb25hbCByZWZlcmVuY2UsIGJl
Y2F1c2UgYnVuZGxpbmcgbWFrZXMgaXQgZWFzaWVyIGZvciB5b3UgdG8gc2hvb3QgDQo+IHlvdXJz
ZWxmIGluIHRoZSBmb290IGJ5IHVzaW5nIGRpZmZlcmVudCBEU0NQIGNvZGVwb2ludHMgZm9yIGRp
ZmZlcmVudCBwYWNrZXRzIGNhcnJpZWQgDQo+IG9uIGEgc2luZ2xlIDUtdHVwbGUuDQoNCkFyZSB5
b3UgdGhpbmtpbmcgb2Ygc29tZXRoaW5nIGxpa2U6DQoNCiJbUkZDNzY1N10gZGVmaW5lcyBEaWZm
ZXJlbnRpYXRlZCBTZXJ2aWNlcyAoRGlmZnNlcnYpIGNvbnNpZGVyYXRpb25zIGZvciBSVFAtYmFz
ZWQgYnVuZGxlZCBtZWRpYS4iDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg0KDQoNCg==


From nobody Mon Apr 16 08:54:47 2018
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 4580A12E8CB; Mon, 16 Apr 2018 08:54:40 -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>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152389408023.19677.17859893415945751945.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 08:54:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Nj9bwCnVAn3qlpuUmVb99TsNLzE>
Subject: [MMUSIC] Spencer Dawkins' Discuss on draft-ietf-mmusic-rid-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 15:54:40 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-mmusic-rid-14: Discuss

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


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


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



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

Please consider this to be an opportunity to explain something to an AD who
doesn't understand codecs super well ... so I doubt it will be hard to clear my
Discuss.

I'm not entirely comfortable that Section 8 isn't normative. Is the theory that
if (for example) I decide that my H.264 format parameter maps onto a
codec-independent parameter that you don't think it maps to, then you and I
probably would probably end up ignoring the rid and doing what we would do, if
one of us didn't support rids? If not, what's supposed to happen (normatively)?


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

If "rid" actually means something, it might be nice to expand it in the
Abstract and Introduction. After the first couple of pages, I was guessing that
it means something like "RTP Stream Identifier", based on a quick scan of
https://tools.ietf.org/html/draft-ietf-avtext-rid-09, but that draft doesn't
ever expand "rid" or use "rid" in the text, so then I think I'm wrong, because
this draft also uses "rid-id", and I'm guessing that's probably not "RTP Stream
Identifier Identifier". By the time I get down to Section 5, I decide it means
"Restriction Identifier", but then I'm not any happier that I'm guessing
"rid-id" means "Restriction Identifier Identifier" :-)

I'm confused by the SHOULD NOT in

  o  max-fps, for frame rate in frames per second.  For encoders that
      do not use a fixed framerate for encoding, this value should
      restrict the minimum amount of time between frames: the time
      between any two consecutive frames SHOULD NOT be less than 1/max-
      fps seconds.

The related description of max-pps, also uses a SHOULD, but explains why
excursions outside this value are permissible.

(I'm also confused by "this value should restrict the minimum amount of time
between frames" - I saw that you're using RFC 8174 for keywords, but is this
just saying "this value restricts the minimum amount of time between frames",
or something else?)

I note that 8.1 and 8.2 both include something like

   Both
   correspond to restrictions on receiver capabilities, and never
   indicate sending restrictions.

Is that true for all format parameters, for all codecs? If so, perhaps that
should be explicit, in one of the normative sections (in which case, it
wouldn't be useful here). If not, are implementations supposed to know what to
do?



From nobody Mon Apr 16 09:13:29 2018
Return-Path: <kaduk@mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0793112E8E8; Mon, 16 Apr 2018 09:13: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 yWf7HilH3XLR; Mon, 16 Apr 2018 09:13:21 -0700 (PDT)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9325A120454; Mon, 16 Apr 2018 09:13:20 -0700 (PDT)
X-AuditID: 12074422-0c5ff7000000622f-3a-5ad4cb9dfaff
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 62.D0.25135.E9BC4DA5; Mon, 16 Apr 2018 12:13:18 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id w3GGDGhL021111; Mon, 16 Apr 2018 12:13:16 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w3GGDBj2015227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 16 Apr 2018 12:13:13 -0400
Date: Mon, 16 Apr 2018 11:13:11 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "Colin Perkins (csp@csperkins.org)" <csp@csperkins.org>
Message-ID: <20180416161310.GD54168@kduck.kaduk.org>
References: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHKsWRmVeSWpSXmKPExsUixCmqrDvv9JUogwWbjSwuzDzMaLH85QlG i+mz3rFZvL+gazHjz0Rmi0vr7zFZnN+5nsli6vLHLA4cHlN+b2T1mHb/PpvHr69X2TyWLPnJ FMASxWWTkpqTWZZapG+XwJWxc/5Z1oITShXzWnvYGhh7pLsYOTgkBEwk+jv4uxi5OIQEFjNJ /L72nQXC2cgoMe9OL3MXIyeQc5VJ4v5jRRCbRUBV4s2bDSwgNpuAikRD92WwGhEBM4nrn3uZ QJqZBVYzS1y88Y8NJCEskC3RcX89mM0LtO3XmmmsEBsmMkqs3vweKiEocXLmE7CpzAJaEjf+ vWQCOY9ZQFpi+T8OkDCngJ9Ey45OVhBbVEBZYm/fIfYJjAKzkHTPQtI9C6F7ASPzKkbZlNwq 3dzEzJzi1GTd4uTEvLzUIl1TvdzMEr3UlNJNjKCgZ3dR2sE48Z/XIUYBDkYlHl6JHVeihFgT y4orcw8xSnIwKYnyHp0JFOJLyk+pzEgszogvKs1JLT7EKMHBrCTCO/8QUI43JbGyKrUoHyYl zcGiJM67eP/eKCGB9MSS1OzU1ILUIpisDAeHkgRv5SmgRsGi1PTUirTMnBKENBMHJ8hwHqDh s0FqeIsLEnOLM9Mh8qcYdTkuHJ3cwyzEkpeflyolztsPUiQAUpRRmgc3B5SsJLL317xiFAd6 S5jXGqSKB5jo4Ca9AlrCBLTkmjHYkpJEhJRUA6PCkoRf3hPsvaY2KFvdzqoxrt/EdeT2N6YP 3RMO3FTsPDUtLJ3Vf1lntK6ci0aFwxKR3hkTntQ5vhJP/BF189C0aW7qV9umF6hxuc9WkWfq 4FJj3xUieq9TJ7Zux0sl10UHN3tzLJnd6v53yfuqC/P/xShqnM5awxD8KL/HQeeq/J7Cxs7P aUosxRmJhlrMRcWJAAnv9SkxAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DGt4LXGdbQnwC0YEnVCC0Qlqx3U>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 16:13:24 -0000

On Sat, Apr 14, 2018 at 03:06:34PM +0000, Christer Holmberg wrote:
> Hi Benjamin,
> 
> Thank You for the review! Please see inline.
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> > Should the NOTE in Section 8.5.2 explicitly reaffirm that only one m= section within the BUNDLE group 
> > can have the offerer BUNDLE address:port, regardless of whether it is a new or preexisting address:port?  
> > That is, that you cannot use an existing BUNDLE address:port and offer a new one in the same BUNDLE group.
> 
> I can add a sentence to the end of the Note:
> 
>    "NOTE: If the offerer also wants to suggest a new offerer BUNDLE
>    address:port to the BUNDLE group, the offerer can assign the newly
>    suggested offerer BUNDLE address:port either to the added "m="
>    section, or to some other "m=" section within the BUNDLE group
>    [Section 8.5.1]. To every other "m=" section within the BUNDLE group
>    the offerer will assign a zero port value and an SDP 'bundle-only' attribute
>    [Section 8.5.1]."
>       
> ---

That seems consistent with the rest of the document and addresses my
question, thanks.

> > When we talk about how the offerer must move a section out of one BUNDLE group and then generate a second offer
> > where that section is added to the other BUNDLE group (this occurs in several places, IIRC), do we need to say anything
> > about the offer that moves the section out of the first BUNDLE group must be accepted before the second offer is offered?
> 
> It is a basic 3264 rule that whatever changes are done in an offer only become valid once they have been accepted by the answerer.

OK

> ---
> 
> > In Section 10.2, page 23, I appreciate the description of the payload type/m= mapping used by legacy
> > implementations, but I worry that there may not be sufficient description of when an SDP participant should 
> > take the care to ensure the uniqueness of the mapping (versus when the legacy considerations can be ignored).
> 
> Section 10 was "outsourced", so I will ask the folks who provided the text to reply :)
> 
> Magnus, Colin?

OK, I'll look for another reply.

> ----
> 
> > Does the first paragraph of Section 10.3.1.2 imply that an implementation of BUNDLE must also implement rtcp-mux-only?
> 
> Yes. I could add a sentence to the following paragraph in section 10.2.:
> 
>    "Within a BUNDLE group, the offerer and answerer MUST enable RTP/RTCP
>    multiplexing [RFC5761] for the RTP-based media specified by the
>    BUNDLE group. In addition, the offerer and answerer MUST support the
>    SDP 'rtcp-mux-only' attribute [I-D.ietf-mmusic-mux-exclusive]."

That will probably make things more clear (not that I expect many
folks to actually be confused by it), in the goal of making
depnedencies explicit.

> ----
> 
> > Should the RTP SDES header extension URI be mentioned somewhere other than the IANA considerations?
> 
> It is mentioned in Section 10.1:
> 
>       "o  The RTP MID header extension MUST be enabled, by including an SDP
>       'extmap' attribute [RFC8285], with a 'urn:ietf:params:rtp-
>       hdrext:sdes:mid' URI value, in each bundled RTP-based "m=" section
>       in every offer and answer."

That must have gone by too quickly while I was searching for the
keyword through the document, sorry for missing it.  Do we want to
say that it's a new thing, at this mention?

> ---
> 
> >In Section 17:
> >
> >   The security considerations of "RTP Header Extension for the RTP
> >   Control Protocol (RTCP) Source Description Items" [RFC7941] requires
> >   that when RTCP is confidentiality protected, and that any SDES RTP
> >   header extension carrying an SDES item, such as the MID RTP header
> >   extension, is also protected using commensurate strength algorithms.
> >
> > "that when [...], and that" seems the wrong construction here; I think that just "that when [...]," is the intended meaning.
> 
> Correct. I suggest:
> 
>    "The security considerations of "RTP Header Extension for the RTP
>    Control Protocol (RTCP) Source Description Items" [RFC7941] requires
>    that when RTCP is confidentiality protected, then any SDES RTP
>    header extension carrying an SDES item,..."

SGTM.

Thanks!

-Benjamin


From nobody Mon Apr 16 09:32:16 2018
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 4D13A12EA94; Mon, 16 Apr 2018 09:32:15 -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 mx3k5Gv0c86f; Mon, 16 Apr 2018 09:32:13 -0700 (PDT)
Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002: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 5F4FF12EA95; Mon, 16 Apr 2018 09:32:13 -0700 (PDT)
Received: by mail-yb0-x22d.google.com with SMTP id t8-v6so7270804ybo.9; Mon, 16 Apr 2018 09:32:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xsgc/QTlHYaaLOWkY19eyDBFaxvCU8oSd6GvaZlMVc0=; b=EWGKmcFkphcMEf7GD9lCH2WCp3b9mnbpqZ8xbNYsDeVLH0L/mfV/HvoN5p+t1ijM8e 37sYdIbVf+MvDlk7J/BWL7+phZ1aAP/2SAWxv2zi3T0n6D7Wo5BquUOvMNGB831y+Nkx Hmz6lM9z+imJsonaoiUmcasHBwWsi2qQR0RmDSQob1Exief6k84/tGeqO7QJYeQ+04Pl tGDiRr5LasVBw+x0zu5d0+21MpppbpKbqqOi4Os3NCMtii4FssVpzf83aSZLQnTFTv+B EHD/HEeyl4On35OWMOveTN1eucntCkFGvHPaWsuHTkaeBYbF/I3uhKidfV70BSm8C7hv zrYg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xsgc/QTlHYaaLOWkY19eyDBFaxvCU8oSd6GvaZlMVc0=; b=Ucy2MN+wAFWZCT7ms+ycpjz+h4sgjC9twDXQ9BUOLLLm4GRWiVkHcX7npeHICSGU9D nMufrPvCXuEd0Oabn1Fuv47oKdp9oROy0MYZYWz1xRnKXprgIZWDEF0ghsijOwwD+PPG yI30sNX1S2GrnBY4gCPGAMHzpd3OJTd9xv4qHBNKR50gCirxFtSqmw3NjW+3FTssSYxU 65CluYEvhpFpMWpuYjrAdznaalQ5JkPbZvocqY2E5mdxjk4PvoZT5v60gP03fDnjPI8g IPBTjDCMnwVoqHXwylSGBem058PTXrJvY3y68IAMVdBVoef9guJViok+vodISYM/QR7e gAOQ==
X-Gm-Message-State: ALQs6tB96zGEu9emUSsYfUX42+t1yRopdzrxNo3f89JXH5emCJiaugtY ZIt4cBqB4p9KTl+9RSm362mr5pn8T2X5N8ZcfMaibQ==
X-Google-Smtp-Source: AIpwx49wsexzVDFe8I5hc0L8IXgL5Tme0YndjQ7roBQgbLnyMdRvEL5HnXcxaF+AJc7V5H/j8YIAF8neOmxmLRr2XRc=
X-Received: by 2002:a25:6a46:: with SMTP id f67-v6mr11634592ybc.235.1523896332220;  Mon, 16 Apr 2018 09:32:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a5b:c06:0:0:0:0:0 with HTTP; Mon, 16 Apr 2018 09:32:11 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E7CE99@ESESSMB109.ericsson.se>
References: <152388981277.20891.5120775227766869176.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E7CE99@ESESSMB109.ericsson.se>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 16 Apr 2018 11:32:11 -0500
Message-ID: <CAKKJt-eMoOh6g3kiGw_ZFsiPPau4xyDTShbATMjtZFOSxfTjMQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008e7fe90569f9c374"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/raw-OcOWnKHhehZO-22XAsJhTHg>
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 16:32:15 -0000

--0000000000008e7fe90569f9c374
Content-Type: text/plain; charset="UTF-8"

Hi, Christer,

On Mon, Apr 16, 2018 at 10:25 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi Spencer,
>
> Thank You for the review! Please see inline.
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> > Thanks for doing this work. It's important.
>
> Thanks! :)
>
> > I wonder if it's worth adding a mention of https://tools.ietf.org/html/
> rfc7657
> > as an Informational reference, because bundling makes it easier for you
> to shoot
> > yourself in the foot by using different DSCP codepoints for different
> packets carried
> > on a single 5-tuple.
>
> Are you thinking of something like:
>
> "[RFC7657] defines Differentiated Services (Diffserv) considerations for
> RTP-based bundled media."


Something like that. I might suggest something a bit more concrete, like

"[RFC7657] defines Differentiated Services (Diffserv) considerations for
RTP-based bundled media sent using a mixture of Diffserv Codepoints."


but I trust you folks to Do The Right Thing.

Spencer

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

<div dir=3D"ltr">Hi, Christer,=C2=A0<div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Mon, Apr 16, 2018 at 10:25 AM, Christer Holmberg <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=
=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">Hi Spencer,<br>
<br>
Thank You for the review! Please see inline.<br>
<span class=3D"gmail-"><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
COMMENT:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt; Thanks for doing this work. It&#39;s important.<br>
<br>
</span>Thanks! :)<br>
<span class=3D"gmail-"><br>
&gt; I wonder if it&#39;s worth adding a mention of <a href=3D"https://tool=
s.ietf.org/html/rfc7657" rel=3D"noreferrer" target=3D"_blank">https://tools=
.ietf.org/html/<wbr>rfc7657</a><br>
&gt; as an Informational reference, because bundling makes it easier for yo=
u to shoot <br>
&gt; yourself in the foot by using different DSCP codepoints for different =
packets carried <br>
&gt; on a single 5-tuple.<br>
<br>
</span>Are you thinking of something like:<br>
<br>
&quot;[RFC7657] defines Differentiated Services (Diffserv) considerations f=
or RTP-based bundled media.&quot;</blockquote><div><br></div><div>Something=
 like that. I might suggest something a bit more concrete, like=C2=A0=C2=A0=
</div><div><br></div></div></div><blockquote style=3D"margin:0px 0px 0px 40=
px;border:none;padding:0px"><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><div>&quot;[RFC7657] defines Differentiated Services (Diffserv) cons=
iderations for RTP-based bundled media sent using a mixture of Diffserv Cod=
epoints.&quot;<br></div></div></div></blockquote><br><div>but I trust you f=
olks to Do The Right Thing.</div><div><br></div><div>Spencer</div></div>

--0000000000008e7fe90569f9c374--


From nobody Mon Apr 16 11:05:00 2018
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 3D2A612D95F for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 11:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U_n3IYAqtKGv for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 11:04: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 4767B12426E for <mmusic@ietf.org>; Mon, 16 Apr 2018 11:04:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523901895; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=G5f4w+xjDYWA7UJwLHouj8yuRnOLJ1QB8lzlryuEZxI=; b=cxELp3bg+6qQhEujxJMWpbAkDWbVqi/avgH1fTziTyNKPiFykIPihuyVIemjSUL5 dpuDK6HOP0rPB0b13pVFupe2k3+NKwk4uPOdIKkBd3svB1lMIkluuVwFYErpet/E ZYvnI+6E584TIHcU7KJK1Rg300R+wmYnCGClN3RMuhU=;
X-AuditID: c1b4fb2d-82dff70000003563-28-5ad4e5c7952a
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id B5.E6.13667.7C5E4DA5; Mon, 16 Apr 2018 20:04:55 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0382.000; Mon, 16 Apr 2018 20:04:54 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1ZFMzBNS0LUxI06sGFjMrf6dGaQDgJ4Q///zqICAADrUMA==
Date: Mon, 16 Apr 2018 18:04:54 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E7D6DC@ESESSMB109.ericsson.se>
References: <152388981277.20891.5120775227766869176.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E7CE99@ESESSMB109.ericsson.se> <CAKKJt-eMoOh6g3kiGw_ZFsiPPau4xyDTShbATMjtZFOSxfTjMQ@mail.gmail.com>
In-Reply-To: <CAKKJt-eMoOh6g3kiGw_ZFsiPPau4xyDTShbATMjtZFOSxfTjMQ@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.168]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7qO7xp1eiDHq2ClpMn/WOzeL9BV2L GX8mMluc37meyWLq8scsFsum7GF2YPOY8nsjq8fOWXfZPZYs+ckUwBzFZZOSmpNZllqkb5fA lfHn837WgnlcFd8PbGdvYPzD2cXIySEhYCJxa8o91i5GLg4hgSOMEt+fLmYCSQgJLGaUOPXf pouRg4NNwEKi+582SFhEwFpiS18nG0g9s8AEJomrf1ezgiSEBZIkjn/rY4MoSpa4+no+K4Tt JHF6znNGEJtFQFXi0PRXYDavgK/Eos4tjBCLbzBKbL/0gxkkwSkQKLF31hd2EJtRQEzi+6k1 YAcxC4hL3HoynwniagGJJXvOM0PYohIvH/9jhbCVJHru32MCOZpZQFNi/S59iFZFiSndD9kh 9gpKnJz5hGUCo+gsJFNnIXTMQtIxC0nHAkaWVYyixanFxbnpRsZ6qUWZycXF+Xl6eaklmxiB UXVwy2/dHYyrXzseYhTgYFTi4T248EqUEGtiWXFl7iFGCQ5mJRHenY+BQrwpiZVVqUX58UWl OanFhxilOViUxHn1Vu2JEhJITyxJzU5NLUgtgskycXBKNTBmdjl6t0qWlBsaRz7mT64Uf2Zk ++Tglj9HznF7GjsEmRQs3qHh+fzJvyvZ+2PiE59w9vjJ/LTPWP/3VqmSjp9954v/bus2eiqp TI3nj1lz/V1Mm21A0ilPQ7EJcfIGf+b/n+h/MSneQZ814Wr5jTPOOSIMV4qbAqy3bghp4/wa fUz8k89+JyWW4oxEQy3mouJEAMWNAGumAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wth7b2VAa56O3qIB-5tL58Zz-3s>
Subject: Re: [MMUSIC] Spencer Dawkins' Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 18:04:59 -0000

SGksDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNPTU1FTlQ6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCj4+PiBJIHdv
bmRlciBpZiBpdCdzIHdvcnRoIGFkZGluZyBhIG1lbnRpb24gb2YgaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL3JmYzc2NTcNCj4+PiBhcyBhbiBJbmZvcm1hdGlvbmFsIHJlZmVyZW5jZSwgYmVj
YXVzZSBidW5kbGluZyBtYWtlcyBpdCBlYXNpZXIgZm9yIHlvdSB0byBzaG9vdCANCj4+PiB5b3Vy
c2VsZiBpbiB0aGUgZm9vdCBieSB1c2luZyBkaWZmZXJlbnQgRFNDUCBjb2RlcG9pbnRzIGZvciBk
aWZmZXJlbnQgcGFja2V0cyBjYXJyaWVkIA0KPj4+IG9uIGEgc2luZ2xlIDUtdHVwbGUuDQo+Pg0K
Pj4gQXJlIHlvdSB0aGlua2luZyBvZiBzb21ldGhpbmcgbGlrZToNCj4+DQo+PiAiW1JGQzc2NTdd
IGRlZmluZXMgRGlmZmVyZW50aWF0ZWQgU2VydmljZXMgKERpZmZzZXJ2KSBjb25zaWRlcmF0aW9u
cyBmb3IgUlRQLWJhc2VkIGJ1bmRsZWQgbWVkaWEuIg0KPg0KPiBTb21ldGhpbmcgbGlrZSB0aGF0
LiBJIG1pZ2h0IHN1Z2dlc3Qgc29tZXRoaW5nIGEgYml0IG1vcmUgY29uY3JldGUsIGxpa2XCoMKg
DQo+DQo+ICJbUkZDNzY1N10gZGVmaW5lcyBEaWZmZXJlbnRpYXRlZCBTZXJ2aWNlcyAoRGlmZnNl
cnYpIGNvbnNpZGVyYXRpb25zIGZvciBSVFAtYmFzZWQgDQo+IGJ1bmRsZWQgbWVkaWEgc2VudCB1
c2luZyBhIG1peHR1cmUgb2YgRGlmZnNlcnYgQ29kZXBvaW50cy4iDQo+DQo+IGJ1dCBJIHRydXN0
IHlvdSBmb2xrcyB0byBEbyBUaGUgUmlnaHQgVGhpbmcuDQoNClRoZSB0ZXh0IHlvdSBzdWdnZXN0
ZWQgbG9va3MgZ29vZCA6KQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo=


From nobody Mon Apr 16 11:14:02 2018
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 D975E12E874 for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 11:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.331
X-Spam-Level: 
X-Spam-Status: No, score=-4.331 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a46Hudv3j0Qd for <mmusic@ietfa.amsl.com>; Mon, 16 Apr 2018 11:13:59 -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 5D168127909 for <mmusic@ietf.org>; Mon, 16 Apr 2018 11:13:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523902437; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ghKIPaaL3/55ZgGiUOZSk3JiqMdYY09wrJ7VBCcXVdE=; b=FTIvmvjmta8oPwZJ9CKzjz0+BBtE0KeHWdyaJmRO3ByOvBstT+c6xgDbkplmPVAO cYHGKkF5Eli+PxydsDL+WBxVbwgmiraj5055yp81RpRdnW1CBawLpYdY3yyRq9Xv LHGCSGb1Rl397BeR6wBausYGHT8wJV6enHm89pzgAL4=;
X-AuditID: c1b4fb25-1dfff7000000522b-74-5ad4e7e58a4f
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id A0.0D.21035.5E7E4DA5; Mon, 16 Apr 2018 20:13:57 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Mon, 16 Apr 2018 20:13:57 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Benjamin Kaduk <kaduk@mit.edu>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "Colin Perkins (csp@csperkins.org)" <csp@csperkins.org>
Thread-Topic: Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT02h7nl6LsadKeEO3frGUURdVt6P/5WiAgAON4YCAAEF40A==
Date: Mon, 16 Apr 2018 18:13:56 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E7D717@ESESSMB109.ericsson.se>
References: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se> <20180416161310.GD54168@kduck.kaduk.org>
In-Reply-To: <20180416161310.GD54168@kduck.kaduk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.168]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7je7T51eiDHq+q1osf3mC0WL6rHds Fu8v6FrM+DOR2WL5xplMFud3rmeymLr8MYsDu8eU3xtZPabdv8/msWTJTyaPpjNHmQNYorhs UlJzMstSi/TtErgyNuw6w1owj73i/bykBsbnrF2MnBwSAiYSpy5fZOxi5OIQEjjCKLFyZzcb hLOYUWLCk06WLkYODjYBC4nuf9ogDSICShKLz7aA1TALNDJLnP35mxWkRlggW2LTFX2ImhyJ 90tnM0LYThJXFrQzgdgsAqoSTy5vBlvMK+ArMfffXiaIXXsYJRouXAIr4hQwlbi8cDkziM0o ICbx/dQasDizgLjErSfzmSCuFpBYsuc8M4QtKvHy8T+ob5Qkeu7fg6rXkViw+xMbhK0tsWzh a2aIxYISJ2c+YZnAKDoLydhZSFpmIWmZhaRlASPLKkbR4tTipNx0I2O91KLM5OLi/Dy9vNSS TYzAWDu45bfqDsbLbxwPMQpwMCrx8M5ceCVKiDWxrLgy9xCjBAezkgjvzsdAId6UxMqq1KL8 +KLSnNTiQ4zSHCxK4rwPzTdHCQmkJ5akZqemFqQWwWSZODilGhgDtm8+r9/6QsrDXy97lubZ v3tPuoScED/6ydT16v3mP2rz98pcb/9R9OKY8eHUa0ypv17+e7ZOzvv427nn3z823bjicaKw ad2J1vSCeX9/Watv2Nz0vSiyspx/o5GvrGr41GtcrEYGOYsdPRbVzLy6/aHxOWNmoZQIB78H Mfd+H+fbqhdwRI5ViaU4I9FQi7moOBEAMdlX2bECAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jTJ7e4REalVnMhMDBxqYNbLnga0>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 18:14:01 -0000

Hi,

----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
=20
>>> Should the RTP SDES header extension URI be mentioned somewhere other t=
han the IANA considerations?
>>=20
>> It is mentioned in Section 10.1:
>>=20
>>       "o  The RTP MID header extension MUST be enabled, by including an =
SDP
>>       'extmap' attribute [RFC8285], with a 'urn:ietf:params:rtp-
>>       hdrext:sdes:mid' URI value, in each bundled RTP-based "m=3D" secti=
on
>>       in every offer and answer."
>
> That must have gone by too quickly while I was searching for the keyword =
through the document, sorry for missing it. =20
> Do we want to say that it's a new thing, at this mention?

Something like:

"with the 'urn:ietf:params:rtp-hdrext:sdes:mid' URI value defined in this s=
pecification"

Regards,

Christer


From nobody Mon Apr 16 11:21:36 2018
Return-Path: <kaduk@mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E874912E05D; Mon, 16 Apr 2018 11:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M_gEVyNaMbCa; Mon, 16 Apr 2018 11:21:33 -0700 (PDT)
Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.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 C8F6812D96B; Mon, 16 Apr 2018 11:21:32 -0700 (PDT)
X-AuditID: 12074425-dd9ff700000042da-83-5ad4e9aabb04
Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 5D.4A.17114.AA9E4DA5; Mon, 16 Apr 2018 14:21:31 -0400 (EDT)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id w3GILSZB004506; Mon, 16 Apr 2018 14:21:28 -0400
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w3GILN0f021801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 16 Apr 2018 14:21:26 -0400
Date: Mon, 16 Apr 2018 13:21:23 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "Colin Perkins (csp@csperkins.org)" <csp@csperkins.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Message-ID: <20180416182123.GI54168@kduck.kaduk.org>
References: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se> <20180416161310.GD54168@kduck.kaduk.org> <7594FB04B1934943A5C02806D1A2204B72E7D717@ESESSMB109.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E7D717@ESESSMB109.ericsson.se>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIKsWRmVeSWpSXmKPExsUixCmqrLv65ZUog09XmC0uzDzMaLH85QlG i+mz3rFZvL+gazHjz0Rmi0vr7zFZnN+5nsli6vLHLA4cHlN+b2T1mHb/PpvHr69X2TyWLPnJ FMASxWWTkpqTWZZapG+XwJVx/e9j9oIWzoppXSvYGhinsXcxcnJICJhI/Nx3hbmLkYtDSGAx k8TrX41gCSGBjYwSfw75QCSuMknMXL2IDSTBIqAq8WvhFiYQm01ARaKh+zIziC0iYCZx/XMv E0gDs8AiZoljD+6ygiSEBbIlOu6vB2vmBVq3u2s6M8SGBiaJj9slIeKCEidnPmEBsZkFtCRu /HsJNIgDyJaWWP6PA8TkFPCT2LdfAqRCVEBZYm/fIfYJjAKzkDTPQtI8C6F5ASPzKkbZlNwq 3dzEzJzi1GTd4uTEvLzUIl0LvdzMEr3UlNJNjKCQZ3dR3cE456/XIUYBDkYlHl6JHVeihFgT y4orcw8xSnIwKYnyHp0JFOJLyk+pzEgszogvKs1JLT7EKMHBrCTCu/MxUI43JbGyKrUoHyYl zcGiJM67eP/eKCGB9MSS1OzU1ILUIpisDAeHkgTv2RdAjYJFqempFWmZOSUIaSYOTpDhPEDD 1V+CDC8uSMwtzkyHyJ9iVJQS59UESQiAJDJK8+B6QSlJInt/zStGcaBXhHnTQFbwANMZXPcr oMFMQIOvGYMNLklESEk1MAqe/1ieonHtxCnHEm2W0nXMZ33L5/snaISdltjHMbdQMZuTT3fe uR1PugoEwuwC3gTMUt7/Ta51jaBExiWR2P0Zv6NuHJwdsUZh0VdZEaGOd58bS2fP8whZ/7T1 mMzV2/JZTQ4K9trvxFYcOFP8g3uKX0tyktjO99FHs1lntjtN9p90rljxuRJLcUaioRZzUXEi ADDS75gkAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/eFxsB6G-_LmrEDMSOxfc16tzVhU>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 18:21:35 -0000

On Mon, Apr 16, 2018 at 06:13:56PM +0000, Christer Holmberg wrote:
> Hi,
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>  
> >>> Should the RTP SDES header extension URI be mentioned somewhere other than the IANA considerations?
> >> 
> >> It is mentioned in Section 10.1:
> >> 
> >>       "o  The RTP MID header extension MUST be enabled, by including an SDP
> >>       'extmap' attribute [RFC8285], with a 'urn:ietf:params:rtp-
> >>       hdrext:sdes:mid' URI value, in each bundled RTP-based "m=" section
> >>       in every offer and answer."
> >
> > That must have gone by too quickly while I was searching for the keyword through the document, sorry for missing it.  
> > Do we want to say that it's a new thing, at this mention?
> 
> Something like:
> 
> "with the 'urn:ietf:params:rtp-hdrext:sdes:mid' URI value defined in this specification"

Yeah, something like that.  Maybe "as defined" or "(defined in this
specification)", but I'm sure you can come up with something
reasonable.

Thanks,

Benjamin


From nobody Mon Apr 16 12:56:45 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2604E126FB3; Mon, 16 Apr 2018 12:56:24 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152390858415.19615.15984889141901987605.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 12:56:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3_rlLRDUB65L3kIe2HJOtegmqiY>
Subject: [MMUSIC] Eric Rescorla's No Objection on draft-ietf-mmusic-rid-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 19:56:27 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-rid-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-rid/



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

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


It took me a while to figure out how this works. I think I would
instead say something like "This document makes it possible to specify
multiple media profiles in a given session, e.g., for different
sending rates for simulcast. Each profile is associated with one or
more payload type and identified by a rid value which is carried in
the RTP payload [REF], thus allowing the receiver to demultiplex
different profiles (and hence sending streams within the session)"




COMMENTS
>      payload format and the associated SDP media description.  The SDP
>      rtpmap and/or fmtp attributes are used, for a given PT, to describe
>      the properties of the media that is carried in the RTP payload.
>
>      Recent advances in standards have given rise to rich multimedia
>      applications requiring support for multiple RTP Streams within a RTP

Nit; "an RTP"


>      To expand on these points: [RFC3550] assigns 7 bits for the PT in the
>      RTP header.  However, the assignment of static mapping of RTP payload
>      type numbers to payload formats and multiplexing of RTP with other
>      protocols (such as RTCP) could result in a limited number of payload
>      type numbers available for application usage.  In scenarios where the
>      number of possible RTP payload configurations exceed the available PT

Nit: exceeds


>      a=rid:<rid-id> <direction> [pt=<fmt-list>;]<restriction>=<value>...
>
>      An "a=rid" SDP media attribute specifies restrictions defining a
>      unique RTP payload configuration identified via the "rid-id" field.
>      This value binds the restriction to the RTP Stream identified by its
>      RTP Stream Identifier SDES item [I-D.ietf-avtext-rid].  To be clear,

SDES is kind of an overloaded term at this point.


>      the RtpStreamId SDES item described in [I-D.ietf-avtext-rid].  Such
>      implementations MUST send it for all streams in an SDP media
>      description ("m=") that have "a=rid" lines remaining after applying
>      the rules in Section 6 and its subsections.
>
>      Implementations that use the "a=rid" parameter in SDP and that make

This is pretty hard to follow. Let me see if I understand this.  You
have a bunch of PTs and then each RID further restricts the parameters
for the set of PTs that it applies to?


>      media section ("m-line"); they do not necessarily need to be unique
>      within an entire RTP session.  In traditional usage, each media
>      section is sent on its own unique 5-tuple, which provides an
>      unambiguous scope.  Similarly, when using BUNDLE
>      [I-D.ietf-mmusic-sdp-bundle-negotiation], MID values associate RTP
>      streams uniquely to a single media description.

So you send both MID and RID in this case? That doesn't seem ideal,
but perhaps it should be stated.


>
>      1.  The answerer ensures that the "a=rid" line is syntactically well
>          formed.  In the case of a syntax error, the "a=rid" line is
>          discarded.
>
>      2.  Extract the rid-id from the "a=rid" line and verify its

This is in the imperative mode whereas the other steps are
descriptive. You probably want them to match


>      1.  The value of the "direction" field is reversed: "send" is changed
>          to "recv", and "recv" is changed to "send".
>
>      2.  The answerer MAY choose to modify specific "a=rid" restriction
>          values in the answer SDP.  In such a case, the modified value
>          MUST be more restricted than the ones specified in the offer.

restrictive?


>          the offer, then the offerer SHALL discard the "a=rid" line.
>
>      3.  If the restrictions have been changed between the offer and the
>          answer, the offerer MUST ensure that the modifications can be
>          supported; if they cannot, the offerer SHALL discard the "a=rid"
>          line.

Should you be checking for "more restricted"


>          comparison necessarily requires an understanding of the meaning
>          of codec parameters, rather than a rote byte-wise comparison of
>          their values.
>
>      6.  If the "a=rid" line contains a "pt=", the offerer verifies that
>          the attribute values provided in the "a=rid" attributes are

Why did you break this out. It seems to just be an addition (5)



From nobody Mon Apr 16 12:58:14 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C6C6A12D883; Mon, 16 Apr 2018 12:57:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org,  fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152390866180.19628.9060717092922213820.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 12:57:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/IVlDNs0rHVqCnxn9_HjE_yZz57M>
Subject: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 19:57:52 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-mmusic-sdp-bundle-negotiation-49: Discuss

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


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


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



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

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









DETAIL
>      When an offerer generates an offer, in which it wants to add a new
>      bundled "m=" section, the offerer MUST:
>
>      o  Assign the offerer BUNDLE address:port (previously selected
>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the added
>         "m=" section; or

IMPORTANT: This doesn't sound right. You can't use the existing
address:port, because if the peer rejects BUNDLE but accepts the m=
section then it's broken.


>      o  When the BUNDLE transport has been established, ICE connectivity
>         checks and keep-alives only need to be performed for the BUNDLE
>         transport, instead of per individual "m=" section within the
>         BUNDLE group.
>
>      o  In an offer, if the offer assigns a unique address:port to one or

IMPORTANT: This does not define how to interact with trickle ICE.


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

>
>    Negotiating Media Multiplexing Using the Session Description Protocol
>                                    (SDP)
>               draft-ietf-mmusic-sdp-bundle-negotiation-49.txt
>
>   Abstract

This document is quite a bit improved from when I read it before, but
it's still very confusing. The primary problem here is the repeated
use of "address;port" as synechdoche for the m= section which is the
"head" of the BUNDLE group (i.e., that which is indicated by the
BUNDLE-tag). That's not what's going on and it's misplaced
concreteness. I would invent some new term ("head" is actually not
bad) and then use it throughout for this concept.


>      to negotiate which "m=" sections will become part of a BUNDLE group.
>      Within a BUNDLE group, each "m=" section will use a BUNDLE transport
>      for sending and receiving bundled media.
>
>      Within a BUNDLE group, each endpoint uses a single address:port
>      combination for sending and receiving bundled media.  The

Nit: "pair"?


>      combination for sending and receiving bundled media.  The
>      address:port combination is referred to as the BUNDLE address:port.
>      In addition to negotiating the BUNDLE group, the offerer and answerer
>      [RFC3264] use the BUNDLE extension to negotiate the BUNDLE
>      addresses:ports, one for the offerer (offerer BUNDLE address) and one
>      for the answerer (answerer BUNDLE address:port).  Once the offerer

Why is one of these called "address" and the other "address:port"?


>      can be used to request that specific media is only used if the "m="
>      section describing the media is kept within a BUNDLE group.
>
>      This specification updates RFC 3264 [RFC3264], to allow assigning a
>      zero port value to a "m=" section without meaning that the media
>      described by the "m=" section is disabled or rejected.

1. Bundle lets you have multiple SDP m= sections on a single 5-tuple
2. The underling mechanism here is that you put those m= sections in
the same BUNDLE group
3. In order to facilitate demuxing, we define a new RTP extension for
MID.
4. It is sometimes desirable to say that an m= section should only be
negotiated if it can be bundled. This is done with port=0 and a
=bundle-only.



>      can be used to request that specific media is only used if the "m="
>      section describing the media is kept within a BUNDLE group.
>
>      This specification updates RFC 3264 [RFC3264], to allow assigning a
>      zero port value to a "m=" section without meaning that the media
>      described by the "m=" section is disabled or rejected.

This section is kind of a laundry list. I think it would be helpful to
break it out conceptually. Specifically.

1.
2.
3.



>
>      "m=" section: SDP bodies contain one or more media descriptions,
>      referred to as "m=" sections.  Each "m=" section is represented by an
>      SDP "m=" line, and zero or more SDP attributes associated with the
>      "m=" line.  A local address:port combination is assigned to each "m="
>      section.

Was this intended to be a bullet?


>      o  Bundled media: All media associated with a given BUNDLE group.
>
>      o  Initial offer: The first offer, within an SDP session (e.g. a SIP
>         dialog when the Session Initiation Protocol (SIP) [RFC3261] is
>         used to carry SDP), in which the offerer indicates that it wants
>         to create a given BUNDLE group.

This is a very idiosyncratic definition, because it's *not* the first
offer in the session, but the one where the BUNDLE group is
introduced. Given that 3264 has a different meaning for this same
term, and the difference is critical, I would strongly urge you to
pick a different term.


>      The BUNDLE extension is indicated using an SDP 'group' attribute with
>      a semantics value [RFC5888] of "BUNDLE".  An identification-tag is
>      assigned to each bundled "m=" section, and each identification-tag is
>      listed in the SDP 'group:BUNDLE' attribute identification-tag list.
>      Each "m=" section whose identification-tag is listed in the
>      identification-tag list is associated with a given BUNDLE group.

How about "is part of" instead of "associated with"


>      Each "m=" section whose identification-tag is listed in the
>      identification-tag list is associated with a given BUNDLE group.
>
>      SDP bodies can contain multiple BUNDLE groups.  Any given bundled
>      "m=" section MUST NOT be associated with more than one BUNDLE group
>      at any given time.

Again "part of"


>      assign a zero port value to the "m=" section.  According to [RFC3264]
>      an answerer will reject such an "m=" section.  By including an SDP
>      'bundle-only' attribute in such an "m=" section, the offerer can
>      request that the answerer accepts the "m=" section if the answerer
>      supports the BUNDLE extension, and if the answerer keeps the "m="
>      section within the associated BUNDLE group.

I would put some of this text up before the attribute definition to
explain why the attribute exists.


>
>      SDP offers and answers can contain multiple BUNDLE groups.  The
>      procedures in this section apply independently to a given BUNDLE
>      group.
>
>   8.1.  Multiplex Category Considerations

Multiplexing?


>      When a BUNDLE group is initially negotiated, and a unique
>      address:port is assigned to each bundled "m=" section (excluding any
>      bundle-only "m=" section) in the initial offer [Section 8.2], any
>      IDENTICAL and TRANSPORT mux category SDP attributes included in the
>      BUNDLE group MUST explicitly be included in each bundled
>      "m=a&#128;&#156; section (excluding any bundle-only "m=" sections).

Something bad happened here with your editor.


>      BUNDLE group MUST explicitly be included in each bundled
>      "m=a&#128;&#156; section (excluding any bundle-only "m=" sections).
>
>      When an offerer or answerer includes SDP attributes in bundled "m="
>      sections within a BUNDLE group for which the offerer and answerer
>      BUNDLE addresses:ports have been selected, IDENTICAL and TRANSPORT

This is pretty opaque. It's not that the address:port pair have been
selected but rather that BUNDLE has been negotiated for that m=
section (though of course the address:port being selected is a side
effect of this).




>      The semantics of some SDP attributes only apply to specific types of
>      media.  For example, the semantics of the SDP 'rtcp-mux' and SDP
>      'rtcp-mux-only' attributes only apply to "m=" sections describing
>      RTP-based media.  However, as described in Section 8.1, there are
>      cases where IDENTICAL and TRANSPORT mux category SDP attributes are
>      only included in the "m=" sections indicated by the BUNDLE-tag.  That

Huh? This is section 8.1.

This whole paragraph is a mess. I would say

"One consequence of these rules is that because SDP attributes which
are appropriate only to some other m= section may appear in the m=
section indicated by the BUNDLE-tag. For instance, the BUNDLE-tag may
indicate a data channel but contain the 'rtcp-mux' attribute because
that applies to an RTP m= section that is part of the BUNDLE group"




>      type of media.
>
>   8.2.  Generating the Initial SDP Offer
>
>      When an offerer generates an initial offer, to negotiate a BUNDLE
>      group, it MUST:

This sentence is ungrammatical. "In order to negotiate a BUNDLE group
in an initial offer, the offerer MUST"


>      within the BUNDLE group, the offerer MUST:
>
>      o  Include an SDP 'bundle-only' attribute [Section 8.2.1] in the "m="
>         section; and
>
>      o  Assign a zero port value to the "m=" section.

I would reorder these, because the zero port is the main semantic.


>
>      NOTE: If the offerer assigns unique addresses:ports to multiple
>      bundled "m=" sections, the offerer needs to be prepared to receive
>      bundled media on each unique address:port, until it receives the
>      associated answer and finds out which address:port combination has
>      been selected as the offerer BUNDLE-address.

Why is this an "If"? There are only two choices: "unique" and "zero".
Just put this graf up before the discussion of bundle-only and you can
remove the conditional


>
>      It is RECOMMENDED that the offerer assigns the suggested offerer
>      BUNDLE address:port to a bundled "m=" section that the offerer
>      assumes it is unlikely that the answerer will reject, or move out of
>      the BUNDLE group.  How such assumption is made is outside the scope
>      of this document.

I would say "believes" rather than "assumes"


>        b=AS:1000
>        a=mid:bar
>        a=rtcp-mux
>        a=rtpmap:31 H261/90000
>        a=rtpmap:32 MPV/90000
>        a=extmap 1 urn:ietf:params:rtp-hdrext:sdes:mid

Line breaks between the m= sections would help here.


>
>      When an answerer generates an answer that contains a BUNDLE group,
>      the following general SDP grouping framework restrictions, defined in
>      [RFC5888], also apply to the BUNDLE group:
>
>      o  The answerer MUST NOT include a BUNDLE group in the answer, unless

Comma not needed here. Also, this negative phrasing is hard to follow.
I would say "MUST only ... if" here and below


>      o  The answerer MUST NOT include an "m=" section within a BUNDLE
>         group, unless the offerer requested the "m=" section to be within
>         that BUNDLE group in the corresponding offer.
>
>      o  If the answer contains multiple BUNDLE groups, the answerer MUST
>         NOT move an "m=" section from one BUNDLE group to another.

This bullet is unnecessary as it immediately follows from the
preoceeding bukllet.


>
>      If the answer contains a BUNDLE group, the answerer MUST:
>
>      o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
>
>      o  Select an answerer BUNDLE address:port [Section 8.3.2].

This isn't right, because each BUNDLE group has its own address:port,
so instead "For each BUNDLE group" contained in the offer.

More importantly, it's not the address:port that the answerer chooses,
but rather the m= section. I.e.,

o Determine the first m= section in the BUNDLE group which will be
BUNDLEd in the answer
o Select an answerer BUNDLE address:port


>      o  The answerer will not reject the "m=" section [Section 8.3.4]; and
>
>      o  The "m=" section does not contain a zero port value.
>
>      If all of the criteria above are fulfilled, the answerer MUST select
>      the suggested offerer BUNDLE address:port.

Again, this isn't selecting the address:port but rather the m=section


>      bundled "m=" section the answerer MUST assign a zero port value and
>      include an SDP 'bundle-only' attribute.
>
>      The answerer MUST NOT assign an answerer BUNDLE address:port to an
>      "m=" section that is not within the BUNDLE group, or to an "m="
>      section that is within another BUNDLE group.

This repeats text in S 8.3.


>      group in an answer, it MUST first check the following criteria:
>
>      o  In the corresponding offer, an offerer BUNDLE address:port
>         (previously selected [Section 8.3.1] or newly suggested
>         [Section 8.5.1]) has been assigned to the "m=" section by the
>         offerer; or

This text is baffling. As far as I can see, the first condition is
"don't pick it as the head m= section if you intend to move it out".
The second is some entirely different case. Can you rewrite it so it
makes sense.


>      either reject the whole offer, reject each bundled "m=" section
>      within the BUNDLE group [Section 8.3.4], or keep the "m=" section
>      within the BUNDLE group in the answer and later create an offer where
>      the "m=" section is moved out of the BUNDLE group [Section 8.5.3].
>
>      When the answerer generates an answer, in which it moves a bundled

No comma


>
>      o  MUST NOT assign an SDP 'bundle-only' attribute to the "m="
>         section.
>
>      An answerer MUST NOT move an "m=" section from one BUNDLE group to
>      another within an answer.  If the answerer wants to move an "m="

This is the third time you have said this. If you want to say it here,
say "Because ..., if"


>      it MUST first check the following criteria:
>
>      o  In the corresponding offer, an offerer BUNDLE address:port
>         (previously selected [Section 8.3.1] or newly suggested
>         [Section 8.5.1]) has been assigned to the "m=" section by the
>         offerer.

Same comment here as above. These are entirely different conditions.


>      o  In the corresponding offer, an offerer BUNDLE address:port
>         (previously selected [Section 8.3.1] or newly suggested
>         [Section 8.5.1]) has been assigned to the "m=" section by the
>         offerer.
>
>      If the criteria above is fulfilled, the answerer can not reject the

"criteria... are"


>      reject the whole offer, reject each bundled "m=" section within the
>      BUNDLE group, or keep the "m=" section within the BUNDLE group in the
>      answer and later create an offer where the "m=" section is disabled
>      within the BUNDLE group [Section 8.5.4].
>
>      When an answerer generates an answer, in which it rejects a bundled

No comma


>        m=video 0 RTP/AVP 32
>        b=AS:1000
>        a=mid:bar
>        a=bundle-only
>        a=rtpmap:32 MPV/90000
>        a=extmap 1 urn:ietf:params:rtp-hdrext:sdes:mid

Please put line breaks in between m= sections here too


>   8.4.  Offerer Processing of the SDP Answer
>
>      When an offerer receives an answer, if the answer contains a BUNDLE
>      group, the offerer MUST check that any bundled "m=" section in the
>      answer was indicated as bundled in the corresponding offer.  If there
>      is no mismatch, the offerer MUST use the offerer BUNDLE address:port,

address:port, again. It's the m=section that's relevant.


>      bundled "m=" section.
>
>      NOTE: As the answerer might reject one or more bundled "m=" sections,
>      or move a bundled "m=" section out of a BUNDLE group, each bundled
>      "m=" section in the offer might not be indicated as bundled in the
>      answer.

"each" -> "an given"


>      When the offerer generates a subsequent offer, the offerer BUNDLE-tag
>      MUST represent the bundled "m=" section to which the offerer BUNDLE
>      address:port (previously negotiated or newly suggested) has been
>      assigned.
>
>   8.5.1.  Suggesting a New Offerer BUNDLE Address:Port

Again it would make more sense to describe this as suggesting a new m=
section.


>      section out of a BUNDLE group.
>
>   8.5.4.  Disabling a Media Description in a BUNDLE Group
>
>      When an offerer generates an offer, in which it wants to disable a
>      bundled "m=" section, the offerer:

Are you sure disable -> port 0, as opposed to "inactive"


>      configuration and packetization.
>      [I-D.ietf-mmusic-sdp-mux-attributes] lists SDP attributes, whose
>      attribute values are required to be identical for all codecs that use
>      the same payload type value.
>
>   10.2.  Associating RTP/RTCP Streams with Correct SDP Media Description

Nit "the correct"


>      "m=" sections), following the procedures for IDENTICAL mux category
>      attributes in Section 8.1.  In addition, the offerer MAY include an
>      SDP 'rtcp-mux-only' attribute [I-D.ietf-mmusic-mux-exclusive] in a
>      RTP-based bundled "m=" section.
>
>      NOTE: Whether the offerer associates the SDP 'rtcp-mux-only'

associates -> includes


>         an offerer BUNDLE address:port (previously selected
>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to a bundled
>         "m=" section (the "m=" section indicated by the offerer BUNDLE-
>         tag), the offerer only includes ICE-related media-level SDP
>         attributes in that "m=" section, following the procedures in
>         Section 8.1.

You should rewrite this graf and the one below to be about BUNDLED-
ness not port assignment. I.e., if you are definitely bundled, willing
to bundle, or not bundled.


>      Support and usage of ICE mechanism together with the BUNDLE extension
>      is OPTIONAL, and the procedures in this section only apply when the
>      ICE mechanism is used.  Note that applications might mandate usage of
>      the ICE mechanism even if the BUNDLE extension is not used.
>
>   11.1.  SDP Offer/Answer Procedures

Same point here as above. Talking about address:port isn't helpful.



From nobody Mon Apr 16 16:08:24 2018
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 7F61D12711A; Mon, 16 Apr 2018 16:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFeGyC0XbCyM; Mon, 16 Apr 2018 16:08:14 -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 CDAE112702E; Mon, 16 Apr 2018 16:08:11 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3GN84jD035468 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 16 Apr 2018 18:08:05 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, mmusic@ietf.org
References: <152389408023.19677.17859893415945751945.idtracker@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <cbdc22dc-bb93-7685-8ff5-c1b92a743dbc@nostrum.com>
Date: Mon, 16 Apr 2018 18:07:59 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <152389408023.19677.17859893415945751945.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/OK5XLs30s9yM_PE4kgEn0ODfSHY>
Subject: Re: [MMUSIC] Spencer Dawkins' Discuss on draft-ietf-mmusic-rid-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 16 Apr 2018 23:08:17 -0000

On 4/16/18 10:54 AM, Spencer Dawkins wrote:
> I'm not entirely comfortable that Section 8 isn't normative. Is the theory that
> if (for example) I decide that my H.264 format parameter maps onto a
> codec-independent parameter that you don't think it maps to, then you and I
> probably would probably end up ignoring the rid and doing what we would do, if
> one of us didn't support rids? If not, what's supposed to happen (normatively)?


I think what might have gotten lost here is that Section 8 is most 
emphatically *not* a mapping.

Section 8 is effectively an example section, serving to reinforce this 
statement from earlier in the document:

    The additional restrictions on individual streams are indicated with
    a new "a=rid" SDP attribute.  Note that the restrictions communicated
    via this attribute only serve to further restrict the parameters that
    are established on a PT format.  They do not relax any existing
    restrictions.

In terms of the possibility of varying interpretations, the guiding 
principle that this section is intended to drive home is: the RID 
restrictions, if understood, are honored independently of any other 
restrictions. So, if you came to the conclusion that (e.g.) the H.264 
parameter "MaxMBPS" didn't have the relationship with the RID "max-pps" 
parameter in this document, you're *still* signing up to keep your 
pixel-per-second count down below the value indicated in "max-pps."

Whether you do so is something that can be objectively evaluated. It's 
not really open for debate if you sign up to send no more than 10 
million pixels per second and yet send 100 million pixels per second 
whether you're honoring the constraint, and that evaluation occurs 
regardless of what you think about how many macroblocks you think you 
can send per second.

/a


From nobody Mon Apr 16 17:09:02 2018
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 A635C127241; Mon, 16 Apr 2018 17:09: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 yqCO6rsXGB7F; Mon, 16 Apr 2018 17:09:00 -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 CF0C012D7E4; Mon, 16 Apr 2018 17:08:59 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id q12so7275963ywj.0; Mon, 16 Apr 2018 17:08:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZbsK+VS/W92bKP6HgIRMDdRislF0aowwmGoCrFFlSkQ=; b=NsfuEx70vx0+T6+fq1b9irjpAtnM46NbVx7PjdGa6vr3UbkG5FpQFw+iLTt+epGVhY 73DD6ZUxTkw9amQwQxsF16vDF57xALYbnwgtm/2Q/i+U8eO9VMkoqHtZNlEPfjKO3ndW oP6+9obj2M36/qZt8GlapReSIXmiEwhSD1CVyVVPCUoTdg+/cwPjBIL1PsoNQAp8R75V 2uGCYE8FjZEY4x3WMcrJv6R9NJTucvcnQQ/H26KDrGI9tmOSQve5cez+EdGXT2gxKYxZ EgA96Jq5VKr9/OX2iwgjotd98oYL6u4XaEKxPj6DImUU1iN0tbPRnSssBM5abTrq9dhs sA/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZbsK+VS/W92bKP6HgIRMDdRislF0aowwmGoCrFFlSkQ=; b=MJ/UK+tjPlbl21CiVNQktYSskX/zmgyWvtXDgthWAkaaLLDWQ2YPxxKmIsuiQ47Nmx wrBP6qVvPpkum6lz4RhLrmf4HlAquwqp3gMcNPhn/LnJLTy7R1y1R0XsWMrDYot4lB7j r6Wks26jaNhLt4t2m2/hQPpLia9sBIu2+zKyN476M1xJEYqxPrc+ryLAD4mKSwFqmw79 /9J4wZtFSNejp6bFpRGCqIp4PGOzTxAnuFz54KdQ+efaCf6skzeqEacyUXaZ7MVLiWD1 CAZMK+zBUBFhIUkRMtxXk1Tq11JXlukrWrxOH18l2QaO4xKPhebQpUpAx6pTIrIXxcab 2cfA==
X-Gm-Message-State: ALQs6tBZrSP7Zb0rZnTSkjbaqh33WKopdu3usYJmhdrc2cjaYd4tYPze a0P/ct0zuBPerMCxUPZplJCFawzkw+6rnRq0WzY=
X-Google-Smtp-Source: AIpwx49eS/mQ63C93EB6jXOG1sqJFXPbgHRGjy0JMo6q72zwD1CNMBJ6jdADYcmYqvPUTg07mbgppkRIDQeLuuMxCII=
X-Received: by 10.129.236.20 with SMTP id j20mr2697829ywm.311.1523923738885; Mon, 16 Apr 2018 17:08:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a5b:c06:0:0:0:0:0 with HTTP; Mon, 16 Apr 2018 17:08:58 -0700 (PDT)
In-Reply-To: <cbdc22dc-bb93-7685-8ff5-c1b92a743dbc@nostrum.com>
References: <152389408023.19677.17859893415945751945.idtracker@ietfa.amsl.com> <cbdc22dc-bb93-7685-8ff5-c1b92a743dbc@nostrum.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 16 Apr 2018 19:08:58 -0500
Message-ID: <CAKKJt-fVX6YtZXvqAMC8QMtM41K0kbV0bKfaLoPR_fkEMfgkzg@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-mmusic-rid@ietf.org,  Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, mmusic@ietf.org
Content-Type: multipart/alternative; boundary="089e082d6cd81f04c9056a0025ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/td_1xudnT_N7185l9eNCPfkwsfE>
Subject: Re: [MMUSIC] Spencer Dawkins' Discuss on draft-ietf-mmusic-rid-14: (with DISCUSS and COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 00:09:02 -0000

--089e082d6cd81f04c9056a0025ad
Content-Type: text/plain; charset="UTF-8"

Hi, Adam,

On Mon, Apr 16, 2018 at 6:07 PM, Adam Roach <adam@nostrum.com> wrote:

> On 4/16/18 10:54 AM, Spencer Dawkins wrote:
>
>> I'm not entirely comfortable that Section 8 isn't normative. Is the
>> theory that
>> if (for example) I decide that my H.264 format parameter maps onto a
>> codec-independent parameter that you don't think it maps to, then you and
>> I
>> probably would probably end up ignoring the rid and doing what we would
>> do, if
>> one of us didn't support rids? If not, what's supposed to happen
>> (normatively)?
>>
>
>
> I think what might have gotten lost here is that Section 8 is most
> emphatically *not* a mapping.
>
> Section 8 is effectively an example section, serving to reinforce this
> statement from earlier in the document:
>
>    The additional restrictions on individual streams are indicated with
>    a new "a=rid" SDP attribute.  Note that the restrictions communicated
>    via this attribute only serve to further restrict the parameters that
>    are established on a PT format.  They do not relax any existing
>    restrictions.
>
> In terms of the possibility of varying interpretations, the guiding
> principle that this section is intended to drive home is: the RID
> restrictions, if understood, are honored independently of any other
> restrictions. So, if you came to the conclusion that (e.g.) the H.264
> parameter "MaxMBPS" didn't have the relationship with the RID "max-pps"
> parameter in this document, you're *still* signing up to keep your
> pixel-per-second count down below the value indicated in "max-pps."
>
> Whether you do so is something that can be objectively evaluated. It's not
> really open for debate if you sign up to send no more than 10 million
> pixels per second and yet send 100 million pixels per second whether you're
> honoring the constraint, and that evaluation occurs regardless of what you
> think about how many macroblocks you think you can send per second.


That's roughly what I suspected, except smart.

I'll clear now, and thanks for the quick clue!

Spencer

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

<div dir=3D"ltr">Hi, Adam,<div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Mon, Apr 16, 2018 at 6:07 PM, Adam Roach <span dir=3D"ltr">&lt;=
<a href=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@nostrum.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"><span class=3D"">On 4/1=
6/18 10:54 AM, Spencer Dawkins wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I&#39;m not entirely comfortable that Section 8 isn&#39;t normative. Is the=
 theory that<br>
if (for example) I decide that my H.264 format parameter maps onto a<br>
codec-independent parameter that you don&#39;t think it maps to, then you a=
nd I<br>
probably would probably end up ignoring the rid and doing what we would do,=
 if<br>
one of us didn&#39;t support rids? If not, what&#39;s supposed to happen (n=
ormatively)?<br>
</blockquote>
<br>
<br></span>
I think what might have gotten lost here is that Section 8 is most emphatic=
ally *not* a mapping.<br>
<br>
Section 8 is effectively an example section, serving to reinforce this stat=
ement from earlier in the document:<br>
<br>
=C2=A0 =C2=A0The additional restrictions on individual streams are indicate=
d with<br>
=C2=A0 =C2=A0a new &quot;a=3Drid&quot; SDP attribute.=C2=A0 Note that the r=
estrictions communicated<br>
=C2=A0 =C2=A0via this attribute only serve to further restrict the paramete=
rs that<br>
=C2=A0 =C2=A0are established on a PT format.=C2=A0 They do not relax any ex=
isting<br>
=C2=A0 =C2=A0restrictions.<br>
<br>
In terms of the possibility of varying interpretations, the guiding princip=
le that this section is intended to drive home is: the RID restrictions, if=
 understood, are honored independently of any other restrictions. So, if yo=
u came to the conclusion that (e.g.) the H.264 parameter &quot;MaxMBPS&quot=
; didn&#39;t have the relationship with the RID &quot;max-pps&quot; paramet=
er in this document, you&#39;re *still* signing up to keep your pixel-per-s=
econd count down below the value indicated in &quot;max-pps.&quot;<br>
<br>
Whether you do so is something that can be objectively evaluated. It&#39;s =
not really open for debate if you sign up to send no more than 10 million p=
ixels per second and yet send 100 million pixels per second whether you&#39=
;re honoring the constraint, and that evaluation occurs regardless of what =
you think about how many macroblocks you think you can send per second.</bl=
ockquote><div><br></div><div>That&#39;s roughly what I suspected, except sm=
art.=C2=A0</div><div><br></div><div>I&#39;ll clear now, and thanks for the =
quick clue!</div><div><br></div><div>Spencer=C2=A0</div></div></div></div>

--089e082d6cd81f04c9056a0025ad--


From nobody Mon Apr 16 17:11:52 2018
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 7F4B9127873; Mon, 16 Apr 2018 17:11:44 -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>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152392390447.26084.8630666548463367333.idtracker@ietfa.amsl.com>
Date: Mon, 16 Apr 2018 17:11:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GiRjHVoMFzMjYU-Vn5fhxKcx3p8>
Subject: [MMUSIC] Spencer Dawkins' No Objection on draft-ietf-mmusic-rid-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 00:11:45 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-mmusic-rid-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-rid/



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

(Meta-comment - thanks for helping me understand what's going on in Section 8,
when discussing my previous Discuss)

If "rid" actually means something, it might be nice to expand it in the
Abstract and Introduction. After the first couple of pages, I was guessing that
it means something like "RTP Stream Identifier", based on a quick scan of
https://tools.ietf.org/html/draft-ietf-avtext-rid-09, but that draft doesn't
ever expand "rid" or use "rid" in the text, so then I think I'm wrong, because
this draft also uses "rid-id", and I'm guessing that's probably not "RTP Stream
Identifier Identifier". By the time I get down to Section 5, I decide it means
"Restriction Identifier", but then I'm not any happier that I'm guessing
"rid-id" means "Restriction Identifier Identifier" :-)

I'm confused by the SHOULD NOT in

  o  max-fps, for frame rate in frames per second.  For encoders that
      do not use a fixed framerate for encoding, this value should
      restrict the minimum amount of time between frames: the time
      between any two consecutive frames SHOULD NOT be less than 1/max-
      fps seconds.

The related description of max-pps, also uses a SHOULD, but explains why
excursions outside this value are permissible.

(I'm also confused by "this value should restrict the minimum amount of time
between frames" - I saw that you're using RFC 8174 for keywords, but is this
just saying "this value restricts the minimum amount of time between frames",
or something else?)

I note that 8.1 and 8.2 both include something like

   Both
   correspond to restrictions on receiver capabilities, and never
   indicate sending restrictions.

Is that true for all format parameters, for all codecs? If so, perhaps that
should be explicit, in one of the normative sections (in which case, it
wouldn't be useful here). If not, are implementations supposed to know what to
do?



From nobody Tue Apr 17 00:07:13 2018
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 26094126CBF for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 00:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6KHhqEuLrVN for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 00:06:59 -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 01AD812EB05 for <mmusic@ietf.org>; Tue, 17 Apr 2018 00:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523948817; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ohX5NXt2EKJcddCQPpAbYCJ68vzEr9YEO3syGaFqywc=; b=aDbBy7N2HE1MBFE0nkZeGZa/Nus7AEzhe0aaDqitQKP4COzS2Jok8Sh5IjCy3ILY Yy8vocWilb0w4iFDIil7s/GgfpFIHzIRnPfj+z4zcRvuaWbCFHMx6FAShSx8Fc8G FyA1rOpdj2bKTDWmxUmpGWZFfTew8NP56k9lxKg894o=;
X-AuditID: c1b4fb3a-7f01c9c000001a0d-bc-5ad59d10543e
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 27.37.06669.01D95DA5; Tue, 17 Apr 2018 09:06:57 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 09:06:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
Thread-Index: AQHT1hqq+aK53d5eAEK3FlM1W8whYQ==
Date: Tue, 17 Apr 2018 07:06:55 +0000
Message-ID: <D6FB735E.2E0AD%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4C7347BF3467A44CA17ACA9E2D30DA87@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2K7qK7g3KtRBk2bOCymz3rHZrHi9Tl2 i/cXdC1m/JnIbHF+53omi6nLH7M4sHlM+b2R1WPJkp9MHpMftzEHMEdx2aSk5mSWpRbp2yVw ZXz918lY8JS/4vyDZvYGxlU8XYycHBICJhKHZm1i7mLk4hASOMIo0Tqhhx3CWcwo0bHuGlMX IwcHm4CFRPc/bZAGEQEriVe/r7GA1DALfGGUePb5KCNIQligVuJYww4miKI6iVNz1jJD2HoS y04fAqthEVCVWLnuIlicV8BaYsHJE2A2o4CYxPdTa8B6mQXEJW49mc8EcZ2AxJI955khbFGJ l4//sYLYokAzN5y4zQ5ym4SAksTtDU4QrToSC3Z/YoOwrSV6by5kh7C1JZYtfA21VlDi5Mwn LBMYRWch2TYLSfssJO2zkLTPQtK+gJF1FaNocWpxcW66kZFealFmcnFxfp5eXmrJJkZgvB3c 8ttqB+PB546HGAU4GJV4eJ2KrkYJsSaWFVfmHmKU4GBWEuHd+fhKlBBvSmJlVWpRfnxRaU5q 8SFGaQ4WJXFepzSLKCGB9MSS1OzU1ILUIpgsEwenVANjeV1MtPaFnLIc8Q1Ku7IC/N/ZnfSZ pcsSlOnVu/h0pat9r2fFUisuByO23/HRy/5ue8GQyrFz0ZNz0/7eOJTx3Gfm5R+nOJW6a+pz Fz5IO3ZYeO3GKScmqRa8rO5I/Rl9Wzb8gNDjxZt2Gv7/E8t+QO7/78UMLw2df+/M/BKyUP/Y 4T//7wjUK7EUZyQaajEXFScCAJPWKZqzAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/u_r40tNX3xDrvdcwCR5oMeUuOIA>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 07:07:01 -0000

Hi,

Thank You for the review! In this reply I will address the DISCUSSes.


>----------------------------------------------------------------------
>DISCUSS:
>----------------------------------------------------------------------
>
>>      When an offerer generates an offer, in which it wants to add a new
>>      bundled "m=3D" section, the offerer MUST:
>>
>>      o  Assign the offerer BUNDLE address:port (previously selected
>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the added
>>         "m=3D" section; or
>
>IMPORTANT: This doesn't sound right. You can't use the existing
>address:port, because if the peer rejects BUNDLE but accepts the m=3D
>section then it's broken.


Note that in this case the usage of BUNDLE has already been negotiated.
Then, if the answerer does not accept the new m=3D section into the BUNDLE
group, it needs to send an offer where it removes it, as described in
section 8.3.3.

---



>>      o  When the BUNDLE transport has been established, ICE connectivity
>>         checks and keep-alives only need to be performed for the BUNDLE
>>         transport, instead of per individual "m=3D" section within the
>>         BUNDLE group.
>>
>>      o  In an offer, if the offer assigns a unique address:port to one
>>or
>
>IMPORTANT: This does not define how to interact with trickle ICE.

I assume you refer to the usage of port 9 and/or address 0.0.0.0 in
trickle ICE?

I guess we could add a statement saying that, when trickle ICE is used,
the same port 9 and/or 0.0.0.0 combination might be assigned to one or
more bundled m- sections, even though the usage of BUNDLE has not yet been
assigned. However, as far as BUNDLE is concerned, they should be processed
as unique address:port combinations, meaning that answerer e.g., can
remove such m- sections from the BUNDLE group in the answer, that the
answerer needs to select one combination as offerer/answerer bundle
address etc.

Regards,


Christer


From nobody Tue Apr 17 00:21:27 2018
Return-Path: <adam@nostrum.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 C70EE1250B8; Tue, 17 Apr 2018 00:21:26 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org,  fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com>
Date: Tue, 17 Apr 2018 00:21:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Gs1oUTUlS6gLzS1W3k14AFHHIvU>
Subject: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 07:21:27 -0000

Adam Roach has entered the following ballot position for
draft-ietf-mmusic-sdp-bundle-negotiation-49: 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-bundle-negotiation/



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

Thanks to everyone who spent time over the past seven years getting this
document complete and out the door.

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

Abstract:

Please indicate that the document updates RFC 7941.

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

§1:

>  This specification updates RFC 3264 [RFC3264], to allow assigning a
>  zero port value to a "m=" section without meaning that the media
>  described by the "m=" section is disabled or rejected.

This needs further qualification: the exception is very narrow, while this
paragraph makes it sound like the meaning of "0" to reject a media section has
been removed altogether.

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

§10.2:

>  Applications can implement RTP stacks in many different ways.  The
>  algorithm below details one way that RTP streams can be associated
>  with "m=" sections, but is not meant to be prescriptive about exactly
>  how an RTP stack needs to be implemented.
...
>  To prepare to associate RTP streams with the correct "m=" section,
>  the following steps MUST be followed for each BUNDLE group:

This "MUST" seems to be at odds with the text about not being prescriptive.
Please clarify whether the steps following this statement are prescriptive
(normative) or not.

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

§10.2:

>     Layer Refresh Request (LRR):  [I-D.ietf-avtext-lrr] (PT=PSFB,
>        FMT=TBD).

Please replace "TBD" with "10" (cf
https://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-9)

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

§11.1:

>  NOTE: The following ICE-related media-level SDP attributes are
>  defined in [I-D.ietf-mmusic-ice-sip-sdp]: 'candidate', 'remote-
>  candidates', 'ice-mismatch', 'ice-ufrag', 'ice-pwd', and 'ice-
>  pacing'.

This seems to leave "ice-options" out.

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

§15.2:

>  applications SHALL avoid generating
>  the identification-tag using a pattern that enables user- or
>  application identification.

Without some kind of recommended MID-generation algorithm, application
identification will be nearly a foregone conclusion. RID makes a concrete
suggestion to start with "1" and go up from there. You may want to consider
doing the same thing, or at least something similar.

This has an impact on §17 as well.

===========================================================================
Nits
===========================================================================

General:

I agree with EKR that the use of "address:port" is cumbersome. For the places
where this is not a stand-in for the term "'m=' section", I would suggest that
the well-known term "3-tuple" would serve the purpose in a much more readable
way.

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

§1:

>  As defined in RFC 4566 [RFC4566], the semantics of assigning the same
>  transport address (IP address and port) to multiple "m=" sections are
>  undefined, and there is no grouping defined by such means.  Instead,
>  an explicit grouping mechanism needs to be used to express the
>  intended semantics.  This specification provides such an extension.

This reads as if the present document is going to define semantics associated
with having the same port and address associated with a multiple m-lines. I
think this was true of BUNDLE at some point in its history, but the present
mechanism uses port=0/bundle-only rather than duplicate port numbers. The
preceding paragraph probably needs to be heavily edited or -- more likely --
removed.

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


§3:

Please consider updating to use RFC 8174 boilerplate.

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

§6:

>  The offerer and answerer assign a zero
>  port value and includes an SDP 'bundle-only' attribute to every other
>  bundled "m=" section.

"...and include..."

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

§8.3.4:

>  it MUST first check the following criteria:

"...criterion:"

>  If the criteria above is fulfilled, the answerer can not reject the

"If the criterion..."

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

§8.3.5:

>    o=bob 2808844564 2808844564 IN IP6 2001:db8::3
...
>    c=IN IP6 2001:db8::3

As this is supposed to be an answer to the offer in §8.2.2, please select a
different address for the answerer than the offerer.

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

§11.1:

>  When an answerer assigns a BUNDLE address to an "m=" section within a
>  BUNDLE group (the "m=" section represented by the answerer BUNDLE-
>  tag), the answerer onlys include SDP 'candidate' attributes (and

Nit: "...only includes..."

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

§12:

>  o  If the DTLS client supports DTLS-SRTP [RFC5764] it MUST include
>     the 'use_srtp' extension [RFC5764] in the DTLS ClientHello message
>     [RFC5764].  The client MUST include the extension even if the
>     usage of DTLS-SRTP is not negotiated as part of the multimedia
>     session (e.g., SIP session [RFC3261].

Fix missing closing paren.

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

§14.3 & §14.4:

The update described by these sections appears unnecessary, as the original text
does not preclude the additional meaning assigned to port=0 by this document. If
this has already been discussed, I don't want to revisit WG consensus; but, if
not, I would recommend removing these sections as superfluous.

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



From nobody Tue Apr 17 02:31:59 2018
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 9400812EAF5 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 02:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5VmLHtZMyd5X for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 02:31: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 E4C6712E891 for <mmusic@ietf.org>; Tue, 17 Apr 2018 02:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523957506; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=rWE+R1hNUjXrbRHxtZRsC1TdS/wIgtAaUg8HyK4UKDc=; b=YMaXt7PJYOfJUkbLZo/apH2XgSiH1m4bKHq+N21veWZpPViNEz9tvwIgbHs4QJcX BHflsUJ3bvcPbETAM6Uj6lacRba2dYwIVGs7ristzVXFmBYxA1+cX6QW1bVUBpj/ squHVThBXm+mGou2cU6gSNkPxtXItBnWEaNRbXQ+9KE=;
X-AuditID: c1b4fb2d-82dff70000003563-df-5ad5bf027a21
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 6D.30.13667.20FB5DA5; Tue, 17 Apr 2018 11:31:46 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 11:31:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyA
Date: Tue, 17 Apr 2018 09:31:39 +0000
Message-ID: <D6FB7DAD.2E10A%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com>
In-Reply-To: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <EE1B3D02161DA64C85637098AD1301BA@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2K7gS7T/qtRBi8fi1js+buI3WL6rHds Fu8v6FrM+DOR2eL8zvVMFlOXP2ZxYPOY8nsjq8eSJT+ZPGbtfMISwBzFZZOSmpNZllqkb5fA lXG5Zy1bQb9LxdtFF1gaGHstuhg5OSQETCSmv/nJ3MXIxSEkcIRR4vqOFUwQzmJGiavTd7N1 MXJwsAlYSHT/0wZpEBGwljjdfBKsgVngC6PEs89HGUESwgJxElP/v2ODKIqXWLSkFco2kriy oJ8ZZA6LgKpE6zJFkDAv0JzOH8/BSoQEfCW+tk1jArE5BfwkDiybyw5iMwqISXw/tQYsziwg LnHryXwmiKMFJJbsOc8MYYtKvHz8jxXEFhXQk9hw4jY7yCoJASWJ2xucIFr1JG5MncIGYVtL nLz3lh3C1pZYtvA1M8Q5ghInZz5hmcAoPgvJtllI2mchaZ+FpH0WkvYFjKyrGEWLU4uLc9ON jPVSizKTi4vz8/TyUks2MQKj8+CW37o7GFe/djzEKMDBqMTDe2jO1Sgh1sSy4srcQ4wSHMxK Irw7H1+JEuJNSaysSi3Kjy8qzUktPsQozcGiJM6rt2pPlJBAemJJanZqakFqEUyWiYNTqoFx iWmh8du+XcqcPLJnNLu0Peq4E1fmf9CMyPQJZuwsy5IprTy8iOF2u7G98zaZmRZTdn2Te6d2 9K59b9KKVT2ej876VF2y2XU1YrbHv589vosPLLmrf3SRWztnwcLj20Mc6nwmry96Ffb6SFH/ u4J3E96oOy19aOfw+/BEB5Z1bxitF5ycuHeqEktxRqKhFnNRcSIAf1D5MsoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sH530wcXTKQu9s4TSrIN8r3Vvz0>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 09:31:57 -0000

Hi Adam,

Thank You for the review! Please see inline.

>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>Thanks to everyone who spent time over the past seven years getting this
>document complete and out the door.
>
>--------------------------------------------------------------------------
>-
>
>Abstract:
>
>Please indicate that the document updates RFC 7941.

Will do.


>--------------------------------------------------------------------------
>-
>
>=A71:
>
>>  This specification updates RFC 3264 [RFC3264], to allow assigning a
>>  zero port value to a "m=3D" section without meaning that the media
>>  described by the "m=3D" section is disabled or rejected.
>
>This needs further qualification: the exception is very narrow, while this
>paragraph makes it sound like the meaning of "0" to reject a media
>section has
>been removed altogether.


What about:

 "This specification updates RFC 3264 [RFC3264], to allow assigning a
  zero port value to a "m=3D=B3 section also in cases where the media
  described by the "m=3D" section is disabled or rejected."



>--------------------------------------------------------------------------
>-
>
>=A710.2:
>
>>  Applications can implement RTP stacks in many different ways.  The
>>  algorithm below details one way that RTP streams can be associated
>>  with "m=3D" sections, but is not meant to be prescriptive about exactly
>>  how an RTP stack needs to be implemented.
>...
>>  To prepare to associate RTP streams with the correct "m=3D" section,
>>  the following steps MUST be followed for each BUNDLE group:
>
>This "MUST" seems to be at odds with the text about not being
>prescriptive.
>Please clarify whether the steps following this statement are prescriptive
>(normative) or not.


I will ask Magnus/Colin to address this.


>--------------------------------------------------------------------------
>-
>
>=A710.2:
>
>>     Layer Refresh Request (LRR):  [I-D.ietf-avtext-lrr] (PT=3DPSFB,
>>        FMT=3DTBD).
>
>Please replace "TBD" with "10" (cf
>https://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-p
>arameters-9)


Will fix as suggested.


>--------------------------------------------------------------------------
>-
>
>=A711.1:
>
>>  NOTE: The following ICE-related media-level SDP attributes are
>>  defined in [I-D.ietf-mmusic-ice-sip-sdp]: 'candidate', 'remote-
>>  candidates', 'ice-mismatch', 'ice-ufrag', 'ice-pwd', and 'ice-
>>  pacing'.
>
>This seems to leave "ice-options" out.

I assumed ice-options was a session-level attribute. Also in
draft-ietf-mmusic-sdp-mux-attributes it is only indicated as a
session-level attribute.

However, when looking in draft-ietf-mmusic-ice-sip-sdp it is defined as
both a session- and media-level attribute. I can add it to the list.

Having said that, draft-ietf-mmusic-ice-sip-sdp does not define any
semantics for media-level usage. Does it mean that the indicated ICE
option only applies to ICE for the given media section, but not to other
media sections? I will send an e-mail on the MMUSIC list.


>--------------------------------------------------------------------------
>-
>
>=A715.2:
>
>>  applications SHALL avoid generating
>>  the identification-tag using a pattern that enables user- or
>>  application identification.
>
>Without some kind of recommended MID-generation algorithm, application
>identification will be nearly a foregone conclusion. RID makes a concrete
>suggestion to start with "1" and go up from there. You may want to
>consider
>doing the same thing, or at least something similar.
>
>This has an impact on =A717 as well.

Section 17 says:

  "Therefore, the identification-tag values MUST be
   generated in a fashion that does not leak user information, e.g.,
   randomly or using a per-bundle group counter, and SHOULD be 3 bytes
   or less, to allow them to efficiently fit into the MID RTP header
   extension."=20



>=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=3D
>Nits
>=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=3D
>
>General:
>
>I agree with EKR that the use of "address:port" is cumbersome. For the
>places
>where this is not a stand-in for the term "'m=3D' section", I would sugges=
t
>that
>the well-known term "3-tuple" would serve the purpose in a much more
>readable
>way.

I personally have nothing against =B33-tuple=B2, =B3transport=B2 (suggested=
 by
Taylor at some point), etc.

The problem is that whenever I change the terminology someone later wants
something else, and then I again have to change it.


>--------------------------------------------------------------------------
>-
>
>=A71:
>
>>  As defined in RFC 4566 [RFC4566], the semantics of assigning the same
>>  transport address (IP address and port) to multiple "m=3D" sections are
>>  undefined, and there is no grouping defined by such means.  Instead,
>>  an explicit grouping mechanism needs to be used to express the
>>  intended semantics.  This specification provides such an extension.
>
>This reads as if the present document is going to define semantics
>associated
>with having the same port and address associated with a multiple m-lines.
>I
>think this was true of BUNDLE at some point in its history, but the
>present
>mechanism uses port=3D0/bundle-only rather than duplicate port numbers. Th=
e
>preceding paragraph probably needs to be heavily edited or -- more likely
>--
>removed.

Unless someone wants to keep it - and will suggest modified text - I will
remove it.


>--------------------------------------------------------------------------
>-
>
>
>=A73:
>
>Please consider updating to use RFC 8174 boilerplate.

Will fix.


>--------------------------------------------------------------------------
>-
>
>=A76:
>
>>  The offerer and answerer assign a zero
>>  port value and includes an SDP 'bundle-only' attribute to every other
>>  bundled "m=3D" section.
>
>"...and include..."

Will fix.


>--------------------------------------------------------------------------
>-
>
>=A78.3.4:
>
>>  it MUST first check the following criteria:
>
>"...criterion:"
>
>>  If the criteria above is fulfilled, the answerer can not reject the
>
>"If the criterion..."

Will fix.


>--------------------------------------------------------------------------
>-
>
>=A78.3.5:
>
>>    o=3Dbob 2808844564 2808844564 IN IP6 2001:db8::3
>...
>>    c=3DIN IP6 2001:db8::3
>
>As this is supposed to be an answer to the offer in =A78.2.2, please selec=
t
>a
>different address for the answerer than the offerer.

Will fix.


>--------------------------------------------------------------------------
>-
>
>=A711.1:
>
>>  When an answerer assigns a BUNDLE address to an "m=3D" section within a
>>  BUNDLE group (the "m=3D" section represented by the answerer BUNDLE-
>>  tag), the answerer onlys include SDP 'candidate' attributes (and
>
>Nit: "...only includes..."

Will fix.


>--------------------------------------------------------------------------
>-
>
>=A712:
>
>>  o  If the DTLS client supports DTLS-SRTP [RFC5764] it MUST include
>>     the 'use_srtp' extension [RFC5764] in the DTLS ClientHello message
>>     [RFC5764].  The client MUST include the extension even if the
>>     usage of DTLS-SRTP is not negotiated as part of the multimedia
>>     session (e.g., SIP session [RFC3261].
>
>Fix missing closing paren.

Will fix.


>--------------------------------------------------------------------------
>-
>
>=A714.3 & =A714.4:
>
>The update described by these sections appears unnecessary, as the
>original text
>does not preclude the additional meaning assigned to port=3D0 by this
>document. If
>this has already been discussed, I don't want to revisit WG consensus;
>but, if
>not, I would recommend removing these sections as superfluous.

I don=B9t think there have been much discussions about this, so unless
someone wants to keep it I can remove it.


>--------------------------------------------------------------------------
>-

Regards,

Christer


From nobody Tue Apr 17 02:42:16 2018
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 8712112741D for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 02:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AeUq05xLJKrW for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 02:42: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 344C5127077 for <mmusic@ietf.org>; Tue, 17 Apr 2018 02:42:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523958132; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=P2bjc1560UGo4lV1z9yYFWzpQvNhx6AG5+CARn/ZpR0=; b=EKNDTgyflMwCcf+eAFbAUMECyD1nxtMxgHiGEZm0KBhybiM4KGTE0zOOGHhmnXPB aUqAPKMmAVDh0w+MbpDcmi3LWWygtPODT+kQmlj5Te1kdkxVoczjcxG11tnfLEbu 6kgNCj7NABhrmYqlRDND7hqlv1AfeWpd2YkFCJHsJDg=;
X-AuditID: c1b4fb3a-427ff70000001a0d-29-5ad5c1748f7b
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id ED.BE.06669.471C5DA5; Tue, 17 Apr 2018 11:42:12 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 11:42:12 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: ice-options attribute: session- and media-level?
Thread-Index: AQHT1jBbREv5MGUFKUOXKyVx3A3GgQ==
Date: Tue, 17 Apr 2018 09:42:10 +0000
Message-ID: <D6FB9C98.2E1E0%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D6FB9C982E1E0christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2K7jW7JwatRBk82KVlMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGcun/GAr2MpfsXr9HdYGxvm8XYwcHBICJhK3Pwl0MXJxCAkc YZRYcLuPDcJZzCjRO7+dHaSITcBCovufdhcjJ4eIgLrE1709zCC2sIClxPHz05kg4nYSL7dv Y4aw9SS+LrgNFmcRUJXY9nIJI4jNK2At8fPlBHYQm1FATOL7qTVgNcwC4hK3nswHsyUEBCSW 7DnPDGGLSrx8/I8VxBYFmrnhxG12iJuVJG5vcIJoTZA42wTRyisgKHFy5hOWCYxCs5BMnYWk bBaSMoi4gcT7c/OZIWxtiWULX0PZ+hIbv5xlhLCtJfZfX8+IrGYBI8cqRtHi1OLi3HQjI73U oszk4uL8PL281JJNjMA4Objlt9UOxoPPHQ8xCnAwKvHw1s25GiXEmlhWXJl7iFGCg1lJhHfn 4ytRQrwpiZVVqUX58UWlOanFhxilOViUxHmd0iyihATSE0tSs1NTC1KLYLJMHJxSDYwTlt45 sFr2tSLf1/M98Ro/VfSjunjt+W/LSSc/vPLx8p/7l5uEvz7I+98zV3f1klPsW6XFpZcpNPCs 4Vz/ZM7vSXv4DO79Edt9h03cafM+1uJZMrL79MKWZlxdUDZh+rMT33rykrqKPjR17WPIjso5 dDAv1vSk8pFPl/92Mpy2X5YrWHRJqF1fiaU4I9FQi7moOBEAZH02lY8CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xP_r1W94jKzOo7QP0ZOmE23sUcw>
Subject: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 09:42:15 -0000

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

Hi,

Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =91ice-options=
=92 attribute as both session- and media-level.

However, there is no description of what it means to use the attribute on m=
edia-level. Does it mean that the indicated ICE extension is only used for =
that particular media stream?

Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16 indicates the=
 attribute as session only (=93S=94).

Is there a need to define it as media-level attribute?

Regards,

Christer


--_000_D6FB9C982E1E0christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <B8CD5A14B5B1FB4A886DDBA4463FEFE1@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>Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =91ice-opt=
ions=92 attribute as both session- and media-level.</div>
<div><br>
</div>
<div>However, there is no description of what it means to use the attribute=
 on media-level. Does it mean that the indicated ICE extension is only used=
 for that particular media stream?</div>
<div><br>
</div>
<div>Also, section 5.12 of&nbsp;draft-ietf-mmusic-sdp-mux-attributes-16 ind=
icates the attribute as session only (=93S=94).</div>
<div><br>
</div>
<div>Is there a need to define it as media-level attribute?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
</body>
</html>

--_000_D6FB9C982E1E0christerholmbergericssoncom_--


From nobody Tue Apr 17 06:44:46 2018
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 717A512EB4A for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 06:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 CItPqAlB_ilN for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 06:44:39 -0700 (PDT)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::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 2C8EF12EB45 for <mmusic@ietf.org>; Tue, 17 Apr 2018 06:44:37 -0700 (PDT)
Received: by mail-ot0-x236.google.com with SMTP id y46-v6so21414295otd.4 for <mmusic@ietf.org>; Tue, 17 Apr 2018 06:44: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=pusd0EMeLH+okaBf9+vWwMuQt0h9ZRTH3CNqbmJXGVs=; b=ryvT9FWVJgsWG3nfwXkh7WCbO238zzWo5nq9Jx6sORj7vBOuEE/Dcg2ZATxPa7THeg oMJE1sLcGr7/KBz7tu6jZXXBqKH61hOnLyYyqALYtlUYCuH5WxO6SL3hO1Oq60JwDdIa wPT8HNbiaVoQoUcW+WK/rBB3unvQwKQy8Y0mza5cCTteaLl/1zbuToBSs1B6uh7ronGU qrLq366vKX2d3CFWG/il6lI1M7wT7F+0CBSn/SnXAvH3Wv4VUuinqH0Rd8yBmooVNTQD 5YzAapOqb65kGq7z0Cpp8FbCRWbokP8jUWH78xh0ppUxa7xvKGF31YJXrQdO8zeR/ngZ lpLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pusd0EMeLH+okaBf9+vWwMuQt0h9ZRTH3CNqbmJXGVs=; b=F/W2HN9yREtmLG9IXX4mIf0EUp1GqLS9OzLHq1jVNKF7FL+f0mnU4drrv7njxKtcTd ADT1+FyqGasUx5STbSe6kw4oCyaymOdQ07Bo2gafnYwas6Ho8Ms3Y/zlRBoenup21Xih u+TFN/Q5tjFuk2qzerkV8qFVWwyG0cmEJn3LSc9ivACatXlp+giJrw0F5vBRJYQh6Bxl 4Z30nqcFNN7s9VokCtao5UKEWTtmtVo9gl3S3t1dLk+B7qW/ZRlkXBKo/N0KOM58cOk5 +yF1iFRaGYTBelw77jua2XjUZUXi2JLQ+VDsq6Ay4cS4D0AanQQA25IW/vc87m7IG4/c 9tDA==
X-Gm-Message-State: ALQs6tCKfTbpkhKHx35eLuSiMMZfnz78Qy96/+JE7igDAFIwpaiSWOu3 DD1w3trtrd6IlDEKxzKZuzwGOykzGXj4kKtbbISvDQ==
X-Google-Smtp-Source: AIpwx49UlhvDUgZkQgBW/Gi8GRE4Uw6pDcI2hJlodcGs6KkGdzXQa8BCxavfSi/7+ovWJoOXb3rFCp5hUKGAPXZHHZI=
X-Received: by 2002:a9d:3ec6:: with SMTP id b64-v6mr1348462otc.371.1523972676527;  Tue, 17 Apr 2018 06:44:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 06:43:55 -0700 (PDT)
In-Reply-To: <D6FB735E.2E0AD%christer.holmberg@ericsson.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 06:43:55 -0700
Message-ID: <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000008412e056a0b8a93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0W8RnLf3MKKmOEwqd9D7kz8URcg>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 13:44:42 -0000

--00000000000008412e056a0b8a93
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 17, 2018 at 12:06 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> Thank You for the review! In this reply I will address the DISCUSSes.
>
>
> >----------------------------------------------------------------------
> >DISCUSS:
> >----------------------------------------------------------------------
> >
> >>      When an offerer generates an offer, in which it wants to add a new
> >>      bundled "m=" section, the offerer MUST:
> >>
> >>      o  Assign the offerer BUNDLE address:port (previously selected
> >>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the added
> >>         "m=" section; or
> >
> >IMPORTANT: This doesn't sound right. You can't use the existing
> >address:port, because if the peer rejects BUNDLE but accepts the m=
> >section then it's broken.
>
>
> Note that in this case the usage of BUNDLE has already been negotiated.
> Then, if the answerer does not accept the new m= section into the BUNDLE
> group, it needs to send an offer where it removes it, as described in
> section 8.3.3.
>

Well, both of these options correspond to insisting that the m= section be
in
the BUNDLE group. If I just want to suggest it, I would have to provide a
fresh
unique address. Or are you saying that's impossible.


>>      o  When the BUNDLE transport has been established, ICE connectivity
> >>         checks and keep-alives only need to be performed for the BUNDLE
> >>         transport, instead of per individual "m=" section within the
> >>         BUNDLE group.
> >>
> >>      o  In an offer, if the offer assigns a unique address:port to one
> >>or
> >
> >IMPORTANT: This does not define how to interact with trickle ICE.
>
> I assume you refer to the usage of port 9 and/or address 0.0.0.0 in
> trickle ICE?
>
> I guess we could add a statement saying that, when trickle ICE is used,
> the same port 9 and/or 0.0.0.0 combination might be assigned to one or
> more bundled m- sections, even though the usage of BUNDLE has not yet been
> assigned. However, as far as BUNDLE is concerned, they should be processed
> as unique address:port combinations, meaning that answerer e.g., can
> remove such m- sections from the BUNDLE group in the answer, that the
> answerer needs to select one combination as offerer/answerer bundle
> address etc.
>

That would seem like a reasonable option.

-Ekr


> Regards,
>
>
> Christer
>
>

--00000000000008412e056a0b8a93
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 Tue, Apr 17, 2018 at 12:06 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><br>
Hi,<br>
<br>
Thank You for the review! In this reply I will address the DISCUSSes.<br>
<br>
<br>
&gt;-----------------------------<wbr>------------------------------<wbr>--=
---------<br>
&gt;DISCUSS:<br>
&gt;-----------------------------<wbr>------------------------------<wbr>--=
---------<br>
&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 When an offerer generates an offer, in which i=
t wants to add a new<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 bundled &quot;m=3D&quot; section, the offerer =
MUST:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 Assign the offerer BUNDLE address:port=
 (previously selected<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[Section 8.3.1] or newly suggeste=
d [Section 8.5.1]) to the added<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;m=3D&quot; section; or<br>
&gt;<br>
&gt;IMPORTANT: This doesn&#39;t sound right. You can&#39;t use the existing=
<br>
&gt;address:port, because if the peer rejects BUNDLE but accepts the m=3D<b=
r>
&gt;section then it&#39;s broken.<br>
<br>
<br>
Note that in this case the usage of BUNDLE has already been negotiated.<br>
Then, if the answerer does not accept the new m=3D section into the BUNDLE<=
br>
group, it needs to send an offer where it removes it, as described in<br>
section 8.3.3.<br></blockquote><div><br></div><div>Well, both of these opti=
ons correspond to insisting that the m=3D section be in</div><div>the BUNDL=
E group. If I just want to suggest it, I would have to provide a fresh</div=
><div>unique address. Or are you saying that&#39;s impossible.<br></div><di=
v><br></div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 When the BUNDLE transport has been est=
ablished, ICE connectivity<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0checks and keep-alives only need =
to be performed for the BUNDLE<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0transport, instead of per individ=
ual &quot;m=3D&quot; section within the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0BUNDLE group.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 In an offer, if the offer assigns a un=
ique address:port to one<br>
&gt;&gt;or<br>
&gt;<br>
&gt;IMPORTANT: This does not define how to interact with trickle ICE.<br>
<br>
I assume you refer to the usage of port 9 and/or address 0.0.0.0 in<br>
trickle ICE?<br>
<br>
I guess we could add a statement saying that, when trickle ICE is used,<br>
the same port 9 and/or 0.0.0.0 combination might be assigned to one or<br>
more bundled m- sections, even though the usage of BUNDLE has not yet been<=
br>
assigned. However, as far as BUNDLE is concerned, they should be processed<=
br>
as unique address:port combinations, meaning that answerer e.g., can<br>
remove such m- sections from the BUNDLE group in the answer, that the<br>
answerer needs to select one combination as offerer/answerer bundle<br>
address etc.<br></blockquote><div><br></div><div>That would seem like a rea=
sonable option.</div><div><br></div><div>-Ekr</div><div><br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<br>
Regards,<br>
<br>
<br>
Christer<br>
<br>
</blockquote></div><br></div></div>

--00000000000008412e056a0b8a93--


From nobody Tue Apr 17 06:47:03 2018
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 39CAF12EB47 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 06:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 hMjUUyLVOU5B for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 06:46:59 -0700 (PDT)
Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 3195912D870 for <mmusic@ietf.org>; Tue, 17 Apr 2018 06:46:59 -0700 (PDT)
Received: by mail-ot0-x233.google.com with SMTP id w4-v6so2418203ote.12 for <mmusic@ietf.org>; Tue, 17 Apr 2018 06:46: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=pt3jtGv4lWUkjXcbFxTIwFwYaYTCU4XN5ntCOpS6qWc=; b=Jz+jxOSX2ux1vgcyKiAGchphCWE+O/QzqLx3TjrhKMyBw71mypC4DeCtmrz78lVtDS TreKYXyiD/v9YyMnBMYWmeNWrxpxX6nBuDENN/DcchphqP7lGkqGw4GA+x9MWN/Ux/BO 00RmbWfIlJ0pJrigDd5OXLrluW14pSeyytW9WdnUrxiN1fxP9k/rxCC4bspysobFBPbJ 5BnweF+7wnvG9Um6dnHFnYv7u/qC/kK704dWqcmlx7MG4Nn+/TSMLhI6L5VAKFoTxCbv ss/kLJ8/g9dTN5bJMCjjzjvUMusK9VKjy82Dmvy0atRono7gEw58xjrag6Rw/lRse5d8 rZBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pt3jtGv4lWUkjXcbFxTIwFwYaYTCU4XN5ntCOpS6qWc=; b=Zjz1o5Fqc5SnCKuYHQgQevppNN0aRma8z/IOrtRzfTapTt8uBECyatdXBnEz58+UZQ eBgKtsf426gx7QBjILRR5CxGGKpgzYLNrou8+EQvKfGgFT2uR5HmNpDBufXKKpJziuXe qMqVLVK9ILztWh3Vq2RMwZNByGWl7YyFAROAAkHICbk11qfwhzA5k7w0nidCuqVRUC1M J2ntHSOnss+6VxwNHkG5lVgJDUIlGSukLZIP8DajlSXeuqB6O2KYK4HWfe9RlsOpLrkW FHh9RQWgQU5REc+veSUFiLYDG2Gm6Ebdusg0IVyW8zs879SZ1ZRI/Eoj5X95DORGEMkQ 2xnA==
X-Gm-Message-State: ALQs6tDz0MXexABeDQH3jXSRGL1BsRhU6osWRp3yr8wfd6QjQh4hZ8WZ 2EZtaAuAqakNd8w05LfJhuXbk1bhQdzTpYSYp46zHnzN
X-Google-Smtp-Source: AIpwx493OVwPyWsaDqA9JMi5NONxY/xARUA4xydfRo0ZGVcyXketSv75U+S650gO6w19N9g5ULP9Yu7qTOeQbEKhvWA=
X-Received: by 2002:a9d:4c16:: with SMTP id l22-v6mr1366199otf.176.1523972818618;  Tue, 17 Apr 2018 06:46:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 06:46:18 -0700 (PDT)
In-Reply-To: <D6FB7DAD.2E10A%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 06:46:18 -0700
Message-ID: <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  "mmusic@ietf.org" <mmusic@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000806028056a0b9265"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/OMAZOyvIV6M-XVQUeqWAab5PsW4>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 13:47:01 -0000

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

On Tue, Apr 17, 2018 at 2:31 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> >=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=3D
> >Nits
> >=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=3D
> >
> >General:
> >
> >I agree with EKR that the use of "address:port" is cumbersome. For the
> >places
> >where this is not a stand-in for the term "'m=3D' section", I would sugg=
est
> >that
> >the well-known term "3-tuple" would serve the purpose in a much more
> >readable
> >way.
>
> I personally have nothing against =C2=B33-tuple=C2=B2, =C2=B3transport=C2=
=B2 (suggested by
> Taylor at some point), etc.
>
> The problem is that whenever I change the terminology someone later wants
> something else, and then I again have to change it.
>

Well, we're at IESG review now, so this is the last round.

Who, specifically, is in favor of the current terminology?

-Ekr

--000000000000806028056a0b9265
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 Tue, Apr 17, 2018 at 2:31 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"><br>
&gt;=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<wbr>=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<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>
&gt;=3D<br>
&gt;Nits<br>
&gt;=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<wbr>=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<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>
<span class=3D"">&gt;=3D<br>
&gt;<br>
&gt;General:<br>
&gt;<br>
&gt;I agree with EKR that the use of &quot;address:port&quot; is cumbersome=
. For the<br>
&gt;places<br>
&gt;where this is not a stand-in for the term &quot;&#39;m=3D&#39; section&=
quot;, I would suggest<br>
&gt;that<br>
&gt;the well-known term &quot;3-tuple&quot; would serve the purpose in a mu=
ch more<br>
&gt;readable<br>
&gt;way.<br>
<br>
</span>I personally have nothing against =C2=B33-tuple=C2=B2, =C2=B3transpo=
rt=C2=B2 (suggested by<br>
Taylor at some point), etc.<br>
<br>
The problem is that whenever I change the terminology someone later wants<b=
r>
something else, and then I again have to change it.<br></blockquote><div><b=
r></div><div>Well, we&#39;re at IESG review now, so this is the last round.=
</div><div><br></div><div>Who, specifically, is in favor of the current ter=
minology?</div><div><br></div><div>-Ekr</div></div><br></div></div>

--000000000000806028056a0b9265--


From nobody Tue Apr 17 06:57:36 2018
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 CDE8312EB48 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 06:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXfBbiGyQsZ3 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 06:57:33 -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 1C8F7127337 for <mmusic@ietf.org>; Tue, 17 Apr 2018 06:57:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523973451; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VTNkCRaEBLt0p9xole4G66NtUKsTxsRsGEkusuuXvfg=; b=NKUzK8HKeA4beMPueZV64IkyvRh+fxIF4gLh8nCydq051SkPcJ6YAeeM4tIKKCZ3 rPJKOZvZjklYedtVlaNDLM0WnAd7/el2Us8HI/JO9Yq/blyYtMDweZdRV3P/SYum XmBnQ9gaBf0DI6WnptI6v7A2p67bwwee/GqHZXk9HIQ=;
X-AuditID: c1b4fb2d-bf68e9c000003563-d0-5ad5fd4b2a69
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 46.91.13667.B4DF5DA5; Tue, 17 Apr 2018 15:57:31 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 15:57:30 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AA==
Date: Tue, 17 Apr 2018 13:57:29 +0000
Message-ID: <D6FBD6CA.2E401%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com>
In-Reply-To: <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <3310D6D2F151CA4E9D45F7748380C06C@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAIsWRmVeSWpSXmKPExsUyM2K7ja7336tRBlufCVjs+buI3WL6rHds Fiten2O3eH9B12LGn4nMFud3rmeymLr8MYsDu8eU3xtZPZYs+cnkMWvnExaPyY/bmANYorhs UlJzMstSi/TtErgyVu/bxVzQwVPRM/sEUwNjH1cXIyeHhICJxK7eE0xdjFwcQgJHGCVWr21h AkkICSxmlFi60auLkYODTcBCovufNkhYREBB4tefEywg9cwC65kkFp2+zAqSEBZIl7jxYBEL SL2IQIbE/QeZEPVOEqsmHwILswioSrw7WQwS5hWwlpg76TQrxNpjjBLfLr5mBElwCgRK/Jw/ CcxmFBCT+H5qDdg5zALiEreezGeCuFlAYsme88wQtqjEy8f/wE4QFdCT2HDiNjvILgkBJYnb G5wgWg0k3p+bzwxhW0vsXzqZHcLWlli28DUzxD2CEidnPmGZwCg+C8m2WUjaZyFpn4WkfRaS 9gWMrKsYRYtTi4tz042M9VKLMpOLi/Pz9PJSSzYxAuP14JbfujsYV792PMQowMGoxMPb++tq lBBrYllxZe4hRgkOZiUR3p2Pr0QJ8aYkVlalFuXHF5XmpBYfYpTmYFES59VbtSdKSCA9sSQ1 OzW1ILUIJsvEwSnVwMhk/nRDOHfn7vV7ilR0jgvy8v9UL3PvXvY3KOS2zpFqv/9/DVcxGSyL fJnymmW9FePcw7UlZY+il0vfmPZYREMkX0TnGLvj09BjM4te39t/o9fI8GQVe6SLvH31xORl 22+Fp0xUms/1OibQYnrdaae5NWuSxNap3OpwPJO1wdfM+OMjeSWVQiWW4oxEQy3mouJEAOB1 3RfTAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EssIKI9OvAV5wYpisspZnAONQjo>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 13:57:35 -0000

Hi,


=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Nits
=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

General:

>>> I agree with EKR that the use of "address:port" is cumbersome. For the
>>>places
>>> where this is not a stand-in for the term "'m=3D' section", I would
>>>suggest that
>>> the well-known term "3-tuple" would serve the purpose in a much more
>>>readable
>>> way.
>>
>> I personally have nothing against '3-tuple', =8Ctransport' (suggested by
>> Taylor at some point), etc.
>>
>> The problem is that whenever I change the terminology someone later
>>wants
>> something else, and then I again have to change it.
>
> Well, we're at IESG review now, so this is the last round.
>
> Who, specifically, is in favor of the current terminology?

I see it more as terminology that people in the WG could live with.

Having said that, if we can change it with a search/replace operation I am
happy to discuss it. I THINK we could do that e.g., with =B3transport=B2 or
=B33-tuple=B2.=20

But I don=B9t want to make yet another re-write of the document just to onc=
e
again change the terminology.

Regards,

Christer





From nobody Tue Apr 17 07:09:20 2018
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 F082B12D94E for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 07:09:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ta9J4qEh2gKJ for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 07:09: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 96DA612D948 for <mmusic@ietf.org>; Tue, 17 Apr 2018 07:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523974150; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=q9Q6Sl1oUG0dBiFZB3JlQuEgKj9NNALS6uayw7PTToo=; b=T38qaUuQJiO+SKy8MJ6IX/OGbUjj+31Fq+KRg5J5r6q9qExa2kqcdWImkCfOuGDG 0mMTy0oJEpxcwKdNhP9FIuR0cuRCMp5CG4dJWa5I8i5EhTu6XR9O4Syh9UbrbnhY AiwW/L3++4Ixu7VBu5ESWkk1+eUamJin2Uvwo075njg=;
X-AuditID: c1b4fb25-1dfff7000000522b-fd-5ad600064c90
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id B3.DB.21035.60006DA5; Tue, 17 Apr 2018 16:09:10 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 16:09:10 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
Thread-Index: AQHT1hqq+aK53d5eAEK3FlM1W8whYaQE1oWAgAA55IA=
Date: Tue, 17 Apr 2018 14:09:09 +0000
Message-ID: <D6FBD89F.2E420%christer.holmberg@ericsson.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com>
In-Reply-To: <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C76985509CAA1E4CA1100067A05AD7C6@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBIsWRmVeSWpSXmKPExsUyM2K7ky4bw7Uog2v3TS2mz3rHZrHi9Tl2 i/cXdC1m/JnIbHF+53omi6nLH7M4sHlM+b2R1WPJkp9MHpMftzEHMEdx2aSk5mSWpRbp2yVw Zax/8ZKx4I5oxYznv9kaGOcIdjFyckgImEjMXPqQsYuRi0NI4AijxKzlr1khnMWMEmubvgE5 HBxsAhYS3f+0QRpEBBQkfv05wQJSwywwgUni6t/VrCAJYYFaiWMNO5ggiuokTs1ZywxhW0ns mfsPzGYRUJXY/38iM8hMXgFriYafzBC7mhglrtzZzwJSwykQKPHl9X92EJtRQEzi+6k1YDOZ BcQlbj2ZzwRxtYDEkj3nmSFsUYmXj/+B3SAqoCex4cRtdpD5EgJKErc3OEG06kgs2P2JDcK2 lmh/1MAIYWtLLFv4GmwMr4CgxMmZT1gmMIrPQrJtFpL2WUjaZyFpn4WkfQEj6ypG0eLU4qTc dCNjvdSizOTi4vw8vbzUkk2MwPg8uOW36g7Gy28cDzEKcDAq8fDe+HM1Sog1say4MvcQowQH s5II787HV6KEeFMSK6tSi/Lji0pzUosPMUpzsCiJ8z403xwlJJCeWJKanZpakFoEk2Xi4JRq YGTJ493d4clucv1Cx7ILmZ/Cmopz9/52SzVeqJ93VXC6OoPhT9tz+zyOFC573ZnUx1Hy27Qw TFrQZzPXM6PjLj3TWgt8Y38xZ/J+FfhdHfPW7nRCgFO82MaApRtSN2UmW6zJyfYQe/3q5Xep ntySfyynXlgsmWXXdu+wVp6qzbxZqVwLzk+UVGIpzkg01GIuKk4EAHmayjLLAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/p2T3-8q9I2766v-8uEXhhdgzb0A>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 14:09:15 -0000

Hi,

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

>>>>      When an offerer generates an offer, in which it wants to add a
>>>>new
>>>>      bundled "m=3D" section, the offerer MUST:
>>>>
>>>>      o  Assign the offerer BUNDLE address:port (previously selected
>>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the
>>>>added
>>>>         "m=3D" section; or
>>>
>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>> address:port, because if the peer rejects BUNDLE but accepts the m=3D
>>> section then it's broken.
>>
>> Note that in this case the usage of BUNDLE has already been negotiated.
>> Then, if the answerer does not accept the new m=3D section into the BUND=
LE
>> group, it needs to send an offer where it removes it, as described in
>> section 8.3.3.
>
> Well, both of these options correspond to insisting that the m=3D section
>be in
> the BUNDLE group. If I just want to suggest it, I would have to provide
>a fresh
> unique address. Or are you saying that's impossible.

Yes.

Previously, when the offerer wanted to add a new m- section to a BUNDLE
group, it had to choice of either assigning a unique address or a
previously negotiated bundle address.

That option was removed as part of task (triggered by WGLC comments etc)
trying to simplifying the procedures. Currently the offerer must either
assign a bundle address (previously negotiated or new suggested) or
indicate it as bundle-only.

---

>>>> o  When the BUNDLE transport has been established, ICE connectivity
>>>>    checks and keep-alives only need to be performed for the BUNDLE
>>>>    transport, instead of per individual "m=3D" section within the
>>>>    BUNDLE group.
>>>>
>>>> o  In an offer, if the offer assigns a unique address:port to one
>>>>    or
>>>
>>> IMPORTANT: This does not define how to interact with trickle ICE.
>>
>> I assume you refer to the usage of port 9 and/or address 0.0.0.0 in
>> trickle ICE?
>>
>> I guess we could add a statement saying that, when trickle ICE is used,
>> the same port 9 and/or 0.0.0.0 combination might be assigned to one or
>> more bundled m- sections, even though the usage of BUNDLE has not yet
>>been
>> assigned. However, as far as BUNDLE is concerned, they should be
>>processed
>> as unique address:port combinations, meaning that answerer e.g., can
>> remove such m- sections from the BUNDLE group in the answer, that the
>> answerer needs to select one combination as offerer/answerer bundle
>> address etc.
>
> That would seem like a reasonable option.

Ok, I will try to come up with some text.

Regards,

Christer


From nobody Tue Apr 17 08:26:26 2018
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 F012912D967; Tue, 17 Apr 2018 08:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AF7MgwbpN6fU; Tue, 17 Apr 2018 08:26:17 -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 7814412DA2C; Tue, 17 Apr 2018 08:26:17 -0700 (PDT)
Received: from [10.0.1.86] (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 w3HFQ6x3097772 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 17 Apr 2018 10:26:08 -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.86]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <20F89F5E-D0EF-4E9B-A3A1-0E5D0510E9FE@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4DBA46C5-6626-4235-A886-89A063EF5173"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Tue, 17 Apr 2018 10:26:05 -0500
In-Reply-To: <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
To: Eric Rescorla <ekr@rtfm.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FWpuYjmK_RCPfht6gt1sJQlG1J0>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 15:26:24 -0000

--Apple-Mail=_4DBA46C5-6626-4235-A886-89A063EF5173
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 17, 2018, at 8:46 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
>=20
> On Tue, Apr 17, 2018 at 2:31 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> =
>=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=3D
> >Nits
> =
>=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=3D
> >
> >General:
> >
> >I agree with EKR that the use of "address:port" is cumbersome.. For =
the
> >places
> >where this is not a stand-in for the term "'m=3D' section", I would =
suggest
> >that
> >the well-known term "3-tuple" would serve the purpose in a much more
> >readable
> >way.
>=20
> I personally have nothing against =C2=B33-tuple=C2=B2, =C2=B3transport=C2=
=B2 (suggested by
> Taylor at some point), etc.
>=20
> The problem is that whenever I change the terminology someone later =
wants
> something else, and then I again have to change it.
>=20
> Well, we're at IESG review now, so this is the last round.
>=20
> Who, specifically, is in favor of the current terminology?

The current terminology may be my fault. IIRC (and I may have this =
confused with a different document), the pubreq=E2=80=99d version used =
=E2=80=9Cbundle address=E2=80=9D to mean address and port, and I =
objected to this being different than the commonly used meaning of =
=E2=80=9Caddress=E2=80=9D.

I am not particularly fond of address:port, though, and agree that =
=E2=80=9C3-tuple=E2=80=9D would be better, as long as the usage is =
clearly defined early in the document.

>=20
> -Ekr
>=20


--Apple-Mail=_4DBA46C5-6626-4235-A886-89A063EF5173
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrWEg0ACgkQgFZKbJXz
1A167A/+M9L3gpacLe1N15gHM9Yt2/m5KQxCF1K5s90UonKhw6WzS/BQ7mFDSQbw
bTwA6S8Gscz9jgaz3t+7PMBFJkGx8vaeC5sQF+Jr0HNBVHLWG/fmtpfVQsfbtoAM
2yg2xjit6J7Ew0Eaj3QYnnDgNg9xNIWEsW4Hzu6gqYp491PUrZclP9vVL36ccj1+
H22JYDHJWEx3zyuxz5ebaQweCLsO/HZTBoVxRA68YqkppuuR7K6rxr89G/PVOf32
0HmuHsBKCRxhEp62Q/7lIHdvAHH3qCXE/vhnc1OmB9DhGP2EUVmAwEXQE4HjumKS
HegFPbLKO+h0bmfOPqHOfHD0PCyvlXZ0NvaZ2HdKl4XduK5sNiVGEd3mAeZ2iCIt
GLCOXka4fobBK9IAziyLrqMX3ho9HcjL0NzjvIbYYB+XCxIGaCFNA00X+M8OSvnV
LUl6yw7V8zwNEKHlPLhGQWvYiAZsOLviXpQslUrKtQSynNYm+02+/Ree0S4itgZI
QGn1YMXewkH7s1XKcF6d3jqeLJu0nvv2KSfz5RkQ9aaVST9QXiy8QN57gfc30pEo
qeT7pl/RPdo8BkjghWFG7lz+Gru79Z3O52rQgiYlB8jiwgHPQ9LR1kiS3LAulVw5
fKq2SdyoZRwi/UmuNDIyIthHjbl3TBZPWZMuqZDp7zUdNhs9FE4=
=3MoB
-----END PGP SIGNATURE-----

--Apple-Mail=_4DBA46C5-6626-4235-A886-89A063EF5173--


From nobody Tue Apr 17 10:04:01 2018
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 3939512D956 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 10:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 sQxPCff1uNio for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 10:03:57 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003: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 8C0A4124207 for <mmusic@ietf.org>; Tue, 17 Apr 2018 10:03:57 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id e123-v6so18638449oih.13 for <mmusic@ietf.org>; Tue, 17 Apr 2018 10:03: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=Lp9Twl9Uzxa0hef6bnTv8tCPd6flNatUKMU/7P668kg=; b=KX8jlOHBuhBJ18/lU0vyE42/+dByGODsxK7Ajmdevlo2S5AetejD2mvfR9uCgCcE7u rmVbT2yTvnV6Zs0qVp95jUALesh92UbfKRqL0trgTvPUm7Mi8QmkZBuNIlxpR8xRKRuI hrWG9W10u3tn7CCWNL/fQwTkW2tr2npAAv8JATt6ZTdfd/OCF3cblfuwcS3wsKkEAMIt 3Ei+I8owKIFWneTSbPaPbvVW3RM73xTdoDetvwKLN9R6u7xBOU4y685Nz4SQ5cVFpaeF 1Q8OcySqAjV13eRtTmcWExJ4jVjVmrGV9IxLH+F8S8E0jGiE80uamg+5naG5uKyt2Qbd tVTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Lp9Twl9Uzxa0hef6bnTv8tCPd6flNatUKMU/7P668kg=; b=JlPBYc8UTFtuyThXf7M+PGQi+Q+PgPksbUvtkA3IfTMEL1BTRKIyYOP+wOrWXZAaB0 rOgOAYE7MGoYV2hFJySvQyNDSDvPJ0tegopFdVDUEyZLPXyqD/EuNkwN3WOX2ayf67ZT N0YliLCQt2ePqpggTRIt0Tat5tgkPqwAOZTX71hXK3Zj5t6gMFgmATQOwBXlnD319kvM s1PvhDm0cTE4D+85IllWCNqUDQhmTO5a2m4EXmGqk5exL3dfRXjagQloJR0STa+mj/Ln ZJ+2l7kvsY6jUY1OXWDK4qMjraR5iCv/YSfm+DyIqlI2EaNXlpgLBemDOPRwrrZDiLcd Yr9w==
X-Gm-Message-State: ALQs6tCB88KiF90dcuzDZmLpsGFAT+gPQiAPlu251v3quEJfG4Gw1was MuzaS0vo+Ni2bJAMjb3Stc0x/hwbKInGPBh3d23JlA==
X-Google-Smtp-Source: AIpwx4/zloNgZr2zeY3dT5XOIoujkEmuUpAXwGoQXLC/YrbdoC7V8okZ8TEp1wnvPJmHHrUTNGw7Wd5qNGBHtns1rIA=
X-Received: by 2002:aca:c744:: with SMTP id x65-v6mr1616990oif.43.1523984636737;  Tue, 17 Apr 2018 10:03:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 10:03:16 -0700 (PDT)
In-Reply-To: <D6FBD89F.2E420%christer.holmberg@ericsson.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 10:03:16 -0700
Message-ID: <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ea9514056a0e52d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/PiChwse75naghOa3Kk0t1NA4X-s>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 17:04:00 -0000

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

On Tue, Apr 17, 2018 at 7:09 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> >>>>      When an offerer generates an offer, in which it wants to add a
> >>>>new
> >>>>      bundled "m=" section, the offerer MUST:
> >>>>
> >>>>      o  Assign the offerer BUNDLE address:port (previously selected
> >>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the
> >>>>added
> >>>>         "m=" section; or
> >>>
> >>> IMPORTANT: This doesn't sound right. You can't use the existing
> >>> address:port, because if the peer rejects BUNDLE but accepts the m=
> >>> section then it's broken.
> >>
> >> Note that in this case the usage of BUNDLE has already been negotiated.
> >> Then, if the answerer does not accept the new m= section into the BUNDLE
> >> group, it needs to send an offer where it removes it, as described in
> >> section 8.3.3.
> >
> > Well, both of these options correspond to insisting that the m= section
> >be in
> > the BUNDLE group. If I just want to suggest it, I would have to provide
> >a fresh
> > unique address. Or are you saying that's impossible.
>
> Yes.
>
> Previously, when the offerer wanted to add a new m- section to a BUNDLE
> group, it had to choice of either assigning a unique address or a
> previously negotiated bundle address.
>
> That option was removed as part of task (triggered by WGLC comments etc)
>

That seems like a pretty material change. Was there a call for consensus on
that?


trying to simplifying the procedures. Currently the offerer must either
> assign a bundle address (previously negotiated or new suggested) or
> indicate it as bundle-only.
>

At minimum this needs to be clearly stated

-Ekr
-

>
> >>>> o  When the BUNDLE transport has been established, ICE connectivity
> >>>>    checks and keep-alives only need to be performed for the BUNDLE
> >>>>    transport, instead of per individual "m=" section within the
> >>>>    BUNDLE group.
> >>>>
> >>>> o  In an offer, if the offer assigns a unique address:port to one
> >>>>    or
> >>>
> >>> IMPORTANT: This does not define how to interact with trickle ICE.
> >>
> >> I assume you refer to the usage of port 9 and/or address 0.0.0.0 in
> >> trickle ICE?
> >>
> >> I guess we could add a statement saying that, when trickle ICE is used,
> >> the same port 9 and/or 0.0.0.0 combination might be assigned to one or
> >> more bundled m- sections, even though the usage of BUNDLE has not yet
> >>been
> >> assigned. However, as far as BUNDLE is concerned, they should be
> >>processed
> >> as unique address:port combinations, meaning that answerer e.g., can
> >> remove such m- sections from the BUNDLE group in the answer, that the
> >> answerer needs to select one combination as offerer/answerer bundle
> >> address etc.
> >
> > That would seem like a reasonable option.
>
> Ok, I will try to come up with some text.
>
> Regards,
>
> Christer
>
>

--000000000000ea9514056a0e52d6
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 Tue, Apr 17, 2018 at 7:09 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">Hi,<br>
<span class=3D""><br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
DISCUSS:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 When an offerer generates an offer, in=
 which it wants to add a<br>
&gt;&gt;&gt;&gt;new<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 bundled &quot;m=3D&quot; section, the =
offerer MUST:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 Assign the offerer BUNDLE addr=
ess:port (previously selected<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[Section 8.3.1] or newly =
suggested [Section 8.5.1]) to the<br>
&gt;&gt;&gt;&gt;added<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;m=3D&quot; section;=
 or<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; IMPORTANT: This doesn&#39;t sound right. You can&#39;t use the=
 existing<br>
&gt;&gt;&gt; address:port, because if the peer rejects BUNDLE but accepts t=
he m=3D<br>
&gt;&gt;&gt; section then it&#39;s broken.<br>
&gt;&gt;<br>
&gt;&gt; Note that in this case the usage of BUNDLE has already been negoti=
ated.<br>
&gt;&gt; Then, if the answerer does not accept the new m=3D section into th=
e BUNDLE<br>
&gt;&gt; group, it needs to send an offer where it removes it, as described=
 in<br>
&gt;&gt; section 8.3.3.<br>
&gt;<br>
&gt; Well, both of these options correspond to insisting that the m=3D sect=
ion<br>
&gt;be in<br>
&gt; the BUNDLE group. If I just want to suggest it, I would have to provid=
e<br>
&gt;a fresh<br>
&gt; unique address. Or are you saying that&#39;s impossible.<br>
<br>
</span>Yes.<br>
<br>
Previously, when the offerer wanted to add a new m- section to a BUNDLE<br>
group, it had to choice of either assigning a unique address or a<br>
previously negotiated bundle address.<br>
<br>
That option was removed as part of task (triggered by WGLC comments etc)<br=
></blockquote><div><br></div><div>That seems like a pretty material change.=
 Was there a call for consensus on that?</div><div><br></div><div><br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
trying to simplifying the procedures. Currently the offerer must either<br>
assign a bundle address (previously negotiated or new suggested) or<br>
indicate it as bundle-only.<br></blockquote><div><br></div><div>At minimum =
this needs to be clearly stated</div><div><br></div><div>-Ekr</div><div>-<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
<span class=3D""><br>
&gt;&gt;&gt;&gt; o=C2=A0 When the BUNDLE transport has been established, IC=
E connectivity<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 checks and keep-alives only need to be perfor=
med for the BUNDLE<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 transport, instead of per individual &quot;m=
=3D&quot; section within the<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 BUNDLE group.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; o=C2=A0 In an offer, if the offer assigns a unique address=
:port to one<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 or<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; IMPORTANT: This does not define how to interact with trickle I=
CE.<br>
&gt;&gt;<br>
&gt;&gt; I assume you refer to the usage of port 9 and/or address 0.0.0.0 i=
n<br>
&gt;&gt; trickle ICE?<br>
&gt;&gt;<br>
&gt;&gt; I guess we could add a statement saying that, when trickle ICE is =
used,<br>
&gt;&gt; the same port 9 and/or 0.0.0.0 combination might be assigned to on=
e or<br>
&gt;&gt; more bundled m- sections, even though the usage of BUNDLE has not =
yet<br>
&gt;&gt;been<br>
&gt;&gt; assigned. However, as far as BUNDLE is concerned, they should be<b=
r>
&gt;&gt;processed<br>
&gt;&gt; as unique address:port combinations, meaning that answerer e.g., c=
an<br>
&gt;&gt; remove such m- sections from the BUNDLE group in the answer, that =
the<br>
&gt;&gt; answerer needs to select one combination as offerer/answerer bundl=
e<br>
&gt;&gt; address etc.<br>
&gt;<br>
&gt; That would seem like a reasonable option.<br>
<br>
</span>Ok, I will try to come up with some text.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote></div><br></div></div>

--000000000000ea9514056a0e52d6--


From nobody Tue Apr 17 11:11:25 2018
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 3F18212D960 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 11:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61uYd3lpyMOk for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 11:11:17 -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 4A00D12D963 for <mmusic@ietf.org>; Tue, 17 Apr 2018 11:11:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523988673; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=7dyF+kW5DvmzuzRe3wxsdI24mlQYYdoBroroJyi8eh0=; b=f34i7CymWX+pg1BkNjXy5pFwLJovR8hQkq6DrN2I6qTW99/vBPzuptpRuRT6RqN1 CPTZjyBo1qX8HasxaTA0xYE604qfX+yjKRISB2OgJProvmfRvuZ58czxdQJxDm38 pczp1Dmi8QRg8zRfzcQx8AEpAwI+qiqns/qmJTD52vw=;
X-AuditID: c1b4fb2d-815ff70000003563-b2-5ad638c1f9ab
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 43.EB.13667.1C836DA5; Tue, 17 Apr 2018 20:11:13 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 20:11:13 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
Thread-Index: AQHT1hqq+aK53d5eAEK3FlM1W8whYaQE1oWAgAA55ID///3OAIAAM2Cw
Date: Tue, 17 Apr 2018 18:11:12 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com>
In-Reply-To: <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@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.172]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM2J7iO5Bi2tRBvcWWFpMn/WOzWLF63Ps Fu8v6FrM+DOR2eL8zvVMFlOXP2ZxYPOY8nsjq8eSJT+ZPCY/bmMOYI7isklJzcksSy3St0vg yvg54ypLwR3RircL+pkaGKeIdjFyckgImEisXN7P2MXIxSEkcIRRYlbfWWYIZzGjxLKWY0AO BwebgIVE9z9tkAYRAQWJX39OsIDUMAtMYJK4+nc1K0hCWKBWorfnETtEUZ3EqTlrwXpFBNwk vnxJBAmzCKhKLO6/xQJi8wr4Sixc3csKses3o8THZWuZQBKcAoESa1a3gM1hFBCT+H5qDVic WUBc4taT+UwQVwtILNlznhnCFpV4+fgfK8guCQEliYaZLCAms4CmxPpd+hCdihJTuh+yQ6wV lDg58wnLBEbRWUiGzkLomIWkYxaSjgWMLKsYRYtTi4tz042M9VKLMpOLi/Pz9PJSSzYxAmPq 4JbfujsYV792PMQowMGoxMNbKHItSog1say4MvcQowQHs5II787HV6KEeFMSK6tSi/Lji0pz UosPMUpzsCiJ8+qt2hMlJJCeWJKanZpakFoEk2Xi4JRqYMztbrBht49Wfp1oob57ocyGpgUP gmW+6TvyreA+0FRll/hz8stysyWCszkLZsxkF0s6z7CchT0oJk5oJafZtXDtj7/WS/W+m/j5 9NPYxFfbmFO99mTP2n+t9eCn+LUSO7cZO/5UTJU35LuR5vPs23Oryv7ywEaTo2yb/aZJWG39 UXCvrDrisxJLcUaioRZzUXEiAJx1cwqlAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/6ngkXnDpgYcRI_qTivUrvP5cZbU>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 18:11:18 -0000

SGksDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCkRJU0NVU1M6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCj4+Pj4+PsKg
V2hlbiBhbiBvZmZlcmVyIGdlbmVyYXRlcyBhbiBvZmZlciwgaW4gd2hpY2ggaXQgd2FudHMgdG8g
YWRkIGEgbmV3DQo+Pj4+Pj7CoGJ1bmRsZWQgIm09IiBzZWN0aW9uLCB0aGUgb2ZmZXJlciBNVVNU
Og0KPj4+Pj4+DQo+Pj4+Pj7CoCDCoCDCoCBvwqAgQXNzaWduIHRoZSBvZmZlcmVyIEJVTkRMRSBh
ZGRyZXNzOnBvcnQgKHByZXZpb3VzbHkgc2VsZWN0ZWQNCj4+Pj4+PsKgIMKgIMKgIMKgIMKgW1Nl
Y3Rpb24gOC4zLjFdIG9yIG5ld2x5IHN1Z2dlc3RlZCBbU2VjdGlvbiA4LjUuMV0pIHRvIHRoZSBh
ZGRlZA0KPj4+Pj4+wqAgwqAgwqAgwqAgwqAibT0iIHNlY3Rpb247IG9yDQo+Pj4+Pg0KPj4+Pj4g
SU1QT1JUQU5UOiBUaGlzIGRvZXNuJ3Qgc291bmQgcmlnaHQuIFlvdSBjYW4ndCB1c2UgdGhlIGV4
aXN0aW5nDQo+Pj4+PiBhZGRyZXNzOnBvcnQsIGJlY2F1c2UgaWYgdGhlIHBlZXIgcmVqZWN0cyBC
VU5ETEUgYnV0IGFjY2VwdHMgdGhlIG09DQo+Pj4+PiBzZWN0aW9uIHRoZW4gaXQncyBicm9rZW4u
DQo+Pj4+DQo+Pj4+IE5vdGUgdGhhdCBpbiB0aGlzIGNhc2UgdGhlIHVzYWdlIG9mIEJVTkRMRSBo
YXMgYWxyZWFkeSBiZWVuIG5lZ290aWF0ZWQuDQo+Pj4+IFRoZW4sIGlmIHRoZSBhbnN3ZXJlciBk
b2VzIG5vdCBhY2NlcHQgdGhlIG5ldyBtPSBzZWN0aW9uIGludG8gdGhlIEJVTkRMRQ0KPj4+PiBn
cm91cCwgaXQgbmVlZHMgdG8gc2VuZCBhbiBvZmZlciB3aGVyZSBpdCByZW1vdmVzIGl0LCBhcyBk
ZXNjcmliZWQgaW4NCj4+Pj4gc2VjdGlvbiA4LjMuMy4NCj4+Pg0KPj4+IFdlbGwsIGJvdGggb2Yg
dGhlc2Ugb3B0aW9ucyBjb3JyZXNwb25kIHRvIGluc2lzdGluZyB0aGF0IHRoZSBtPSBzZWN0aW9u
DQo+Pj4gYmUgaW4gdGhlIEJVTkRMRSBncm91cC4gSWYgSSBqdXN0IHdhbnQgdG8gc3VnZ2VzdCBp
dCwgSSB3b3VsZCBoYXZlIHRvIHByb3ZpZGUNCj4+PiBhIGZyZXNoIHVuaXF1ZSBhZGRyZXNzLiBP
ciBhcmUgeW91IHNheWluZyB0aGF0J3MgaW1wb3NzaWJsZS4NCj4+Pg0KPj4gWWVzLg0KPj4NCj4+
IFByZXZpb3VzbHksIHdoZW4gdGhlIG9mZmVyZXIgd2FudGVkIHRvIGFkZCBhIG5ldyBtLSBzZWN0
aW9uIHRvIGEgQlVORExFDQo+PiBncm91cCwgaXQgaGFkIHRvIGNob2ljZSBvZiBlaXRoZXIgYXNz
aWduaW5nIGEgdW5pcXVlIGFkZHJlc3Mgb3IgYQ0KPj4gcHJldmlvdXNseSBuZWdvdGlhdGVkIGJ1
bmRsZSBhZGRyZXNzLg0KPj4NCj4+IFRoYXQgb3B0aW9uIHdhcyByZW1vdmVkIGFzIHBhcnQgb2Yg
dGFzayAodHJpZ2dlcmVkIGJ5IFdHTEMgY29tbWVudHMgZXRjKQ0KPg0KPiBUaGF0IHNlZW1zIGxp
a2UgYSBwcmV0dHkgbWF0ZXJpYWwgY2hhbmdlLiBXYXMgdGhlcmUgYSBjYWxsIGZvciBjb25zZW5z
dXMgb24gdGhhdD8NCg0KTm8uIEJ1dCwgdGhlIHN1Z2dlc3RlZCBjaGFuZ2VzIHdlcmUgaW5kaWNh
dGVkIG9uIHRoZSBsaXN0LCB0aGVyZSB3ZXJlIHB1bGwgcmVxdWVzdHMgZXRjLCBzbyBwZW9wbGUg
d2VyZSBpbmZvcm1lZCBhYm91dCBpdCBhbmQgaGFkIGEgY2hhbmNlIHRvIGNvbW1lbnQvb2JqZWN0
Lg0KDQo+IHRyeWluZyB0byBzaW1wbGlmeWluZyB0aGUgcHJvY2VkdXJlcy4gQ3VycmVudGx5IHRo
ZSBvZmZlcmVyIG11c3QgZWl0aGVyDQo+IGFzc2lnbiBhIGJ1bmRsZSBhZGRyZXNzIChwcmV2aW91
c2x5IG5lZ290aWF0ZWQgb3IgbmV3IHN1Z2dlc3RlZCkgb3INCj4gaW5kaWNhdGUgaXQgYXMgYnVu
ZGxlLW9ubHkuDQo+DQo+IEF0IG1pbmltdW0gdGhpcyBuZWVkcyB0byBiZSBjbGVhcmx5IHN0YXRl
ZA0KDQpJIG5lZWQgdG8gbW9kaWZ5IHRoZSBzZWN0aW9uLCBzbyBJIHdpbGwgYWRkIHRleHQgYWJv
dXQgaXQuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Tue Apr 17 11:15:31 2018
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 374EF12D960 for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 11:15:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYx7YVz8eo0s for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 11:15:29 -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 4D092126C26 for <mmusic@ietf.org>; Tue, 17 Apr 2018 11:15:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523988924; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=YbADOyu4qU3og/I/jQjDlbZbKXT8bVj6yVg+kd5hWuI=; b=fMAQmlK2s2cw1IJKAbEmTrxcyGdl+NbA9r2sLQefJZhi5ubC+nvDW5024nKB73zt yUCqtalI/bWlPZpbFxQY4/u7gVLFTY+cjy1saewnAisxm/89YDVZklGfc1yHGCN0 BjOY7NSdfG41+bJHnyu8fvaCT+aYlMG0vDm8aNM3Dj4=;
X-AuditID: c1b4fb3a-40fff70000001a0d-65-5ad639bcdb74
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 71.E6.06669.CB936DA5; Tue, 17 Apr 2018 20:15:24 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 20:15:23 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
CC: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Flemming Andreasen <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAABvhgIAAT/ww
Date: Tue, 17 Apr 2018 18:15:22 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E86F43@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <20F89F5E-D0EF-4E9B-A3A1-0E5D0510E9FE@nostrum.com>
In-Reply-To: <20F89F5E-D0EF-4E9B-A3A1-0E5D0510E9FE@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.172]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2K7se4ey2tRBouaZCz2/F3EbjG/8zS7 xfRZ79gsVrw+x27x/oKuxYw/E5ktzu9cz2QxdfljFgcOjym/N7J6LFnyk8lj1s4nLB6TH7cx B7BEcdmkpOZklqUW6dslcGV8nfCLveAcb0Xvnz6WBsYFvF2MnBwSAiYSc99tZ+pi5OIQEjjC KPFk3x42CGcxo8T8zY/Yuxg5ONgELCS6/2mDNIgIOEhM+n6BFaSGWWAtk8SbxiXMIAlhgXSJ OauWMYPUiwhkSNx/kAlR7ybR/es/C4jNIqAqcXzCJFaQEl4BX4m98x0gVv1mlFjQsZ4JpIZT wF7iS+9SVhCbUUBM4vupNWBxZgFxiVtP5jNBHC0gsWTPeWYIW1Ti5eN/YDMlBJQkGmaygJjM ApoS63fpQ3QqSkzpfsgOYvMKCEqcnPmEZQKj6CwkQ2chdMxC0jELSccCRpZVjKLFqcXFuelG RnqpRZnJxcX5eXp5qSWbGIHxdnDLb6sdjAefOx5iFOBgVOLhVRK5FiXEmlhWXJl7iFGCg1lJ hHfn4ytRQrwpiZVVqUX58UWlOanFhxilOViUxHmd0iyihATSE0tSs1NTC1KLYLJMHJxSDYyO h54+UytuCTvpIqkZdUWQxWh7xhHfyEeHDWJD7sqe3HShINOCX+nm/d1GKh1zlY87TPtc2GUs YqMS9O7rtstxy4//ikn+9oIrXOr2z3jVg8wVX6tV5fbv+PtgJ+fd9g63hzVFIo7TXyt+bSmX lg9ykv/yqf3SXt3crxc0vqjtD7m+Y1b1oQolluKMREMt5qLiRAAuhzTHswIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Q7pglr1UMMLyFcIJ4p1LGJ8lF-k>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 18:15:30 -0000

SGksDQoNCj4+PkdlbmVyYWw6DQo+Pj4NCj4+PiBJIGFncmVlIHdpdGggRUtSIHRoYXQgdGhlIHVz
ZSBvZiAiYWRkcmVzczpwb3J0IiBpcyBjdW1iZXJzb21lLi4gRm9yIA0KPj4+IHRoZSBwbGFjZXMg
d2hlcmUgdGhpcyBpcyBub3QgYSBzdGFuZC1pbiBmb3IgdGhlIHRlcm0gIidtPScgc2VjdGlvbiIs
IA0KPj4+IEkgd291bGQgc3VnZ2VzdCB0aGF0IHRoZSB3ZWxsLWtub3duIHRlcm0gIjMtdHVwbGUi
IHdvdWxkIHNlcnZlIHRoZSANCj4+PiBwdXJwb3NlIGluIGEgbXVjaCBtb3JlIHJlYWRhYmxlIHdh
eS4NCj4+IA0KPj4gSSBwZXJzb25hbGx5IGhhdmUgbm90aGluZyBhZ2FpbnN0ICIzLXR1cGxlIiwg
InRyYW5zcG9ydCIgKHN1Z2dlc3RlZCBieSANCj4+IFRheWxvciBhdCBzb21lIHBvaW50KSwgZXRj
Lg0KPj4gDQo+PiBUaGUgcHJvYmxlbSBpcyB0aGF0IHdoZW5ldmVyIEkgY2hhbmdlIHRoZSB0ZXJt
aW5vbG9neSBzb21lb25lIGxhdGVyIA0KPj4gd2FudHMgc29tZXRoaW5nIGVsc2UsIGFuZCB0aGVu
IEkgYWdhaW4gaGF2ZSB0byBjaGFuZ2UgaXQuDQo+PiANCj4+IFdlbGwsIHdlJ3JlIGF0IElFU0cg
cmV2aWV3IG5vdywgc28gdGhpcyBpcyB0aGUgbGFzdCByb3VuZC4NCj4+IA0KPj4gV2hvLCBzcGVj
aWZpY2FsbHksIGlzIGluIGZhdm9yIG9mIHRoZSBjdXJyZW50IHRlcm1pbm9sb2d5Pw0KPg0KPiBU
aGUgY3VycmVudCB0ZXJtaW5vbG9neSBtYXkgYmUgbXkgZmF1bHQuIElJUkMgKGFuZCBJIG1heSBo
YXZlIHRoaXMgY29uZnVzZWQgd2l0aCBhIGRpZmZlcmVudCBkb2N1bWVudCksIA0KPiB0aGUgcHVi
cmVx4oCZZCB2ZXJzaW9uIHVzZWQg4oCcYnVuZGxlIGFkZHJlc3PigJ0gdG8gbWVhbiBhZGRyZXNz
IGFuZCBwb3J0LCBhbmQgSSBvYmplY3RlZCB0byB0aGlzIGJlaW5nIGRpZmZlcmVudCANCj4gdGhh
biB0aGUgY29tbW9ubHkgdXNlZCBtZWFuaW5nIG9mIOKAnGFkZHJlc3PigJ0uDQo+DQo+IEkgYW0g
bm90IHBhcnRpY3VsYXJseSBmb25kIG9mIGFkZHJlc3M6cG9ydCwgdGhvdWdoLCBhbmQgYWdyZWUg
dGhhdCDigJwzLXR1cGxl4oCdIHdvdWxkIGJlIGJldHRlciwgYXMgbG9uZyBhcyB0aGUgDQo+IHVz
YWdlIGlzIGNsZWFybHkgZGVmaW5lZCBlYXJseSBpbiB0aGUgZG9jdW1lbnQuDQoNClBlcnNvbmFs
bHkgSSdkIHByZWZlciAidHJhbnNwb3J0IiwgYmVjYXVzZSAiQlVORExFIHRyYW5zcG9ydCIgc291
bmRzIGJldHRlciB0aGFuICJCVU5ETEUgMy10dXBsZSIgaW4gbXkgZWFycy4gDQoNClJlZ2FyZHMs
DQoNCkNocmlzdGVyDQoNCg==


From nobody Tue Apr 17 11:19:13 2018
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 CB76312706D for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 11:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 moUidyOpcbCG for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 11:19:09 -0700 (PDT)
Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 284D4126DEE for <mmusic@ietf.org>; Tue, 17 Apr 2018 11:19:06 -0700 (PDT)
Received: by mail-ot0-x233.google.com with SMTP id m22-v6so22422730otf.8 for <mmusic@ietf.org>; Tue, 17 Apr 2018 11:19:06 -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=s6dxchL1W1Esm3RPfmyqVfyjdWbL3pP0YkpI61asiBE=; b=bX0LQC4xXMbKygbeK/rp636sm1E7J/I96iFIlT3nekzRH7V0aLvxyKnbs/4idcWrzl Id3e2Fnuf5I8GdTzFmOZLkK0BoIupWSHI6HT+6OBvuzCxWBTiwSJQxJsW2ZoCLX3JgSL WOU3ewTu4ld3VaRMCJw6yclOXsn0J1feHeFtQOYbfjoev2z89DW4tdBgY1t/j6upo3ZW 4ZzhUbJlbzlHgoasH4h9H0mi7LYAIU/9hV4Fe+p5v8Bz90pSdJWpbYjMurLdG6xrZCDS t2J1Fdn5e0umCeHisT1rmQ9xS2hh8p57LX9QROvWitv+xtsNo7detWoF7Qgi5E5r1KSx 8MXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s6dxchL1W1Esm3RPfmyqVfyjdWbL3pP0YkpI61asiBE=; b=ZHRQzvzAAFF6a6I+g6nbmyAgF9dLQvi8iffYACpdLx4UI9LPpWfi5uiBfakazK3AJz gPPhj6b9rsQ06o6Bj6OxPQknsnPLKpJxjeY4k5YNDvU0nZ0t0OzZUCo54Ka0zlVb4KX+ yU7sbMASBjOLhPVLADAIS05BQB72LjIpDpVosS1PB1Qye2tepcT67ht9B+o9yZfMDqu4 LOwcn28x/igVZU84RPXn6gG4wL4AV3ojbCbvOi6f+JeAbsEoROBZmtF61Cnz1HW5CS+i t+sLfCCYgvezpE59SCzS7kJxp4WjM8gESy3EZuiF2rbZD/Mv3M+pXTuma3pUZ+vVWEyD 8mpQ==
X-Gm-Message-State: ALQs6tBYwzhImvQOB1cJnGj39VJhMxfW4d0xLs1RJHvxosY20zEJbQIY Pv0+bC224rtoYtWVWcmjp2dQurouaMGl6meJnZ2s5Q==
X-Google-Smtp-Source: AIpwx49piCZ2lY4LLnTSMr9uSU9HGB7nUJwMLTD1OopYLU5broK5NZh4ixtEnnZdWRbaGzpLc5+YkGkM7eaz62YOJPc=
X-Received: by 2002:a9d:23f6:: with SMTP id t109-v6mr2039609otb.44.1523989145464;  Tue, 17 Apr 2018 11:19:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 11:18:24 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 11:18:24 -0700
Message-ID: <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a846b5056a0f5fe3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AbqSgTYN8MujBUavFyUDQBRiNPc>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 18:19:11 -0000

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

On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> >>>>>> When an offerer generates an offer, in which it wants to add a new
> >>>>>> bundled "m=" section, the offerer MUST:
> >>>>>>
> >>>>>>      o  Assign the offerer BUNDLE address:port (previously selected
> >>>>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the
> added
> >>>>>>         "m=" section; or
> >>>>>
> >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
> >>>>> address:port, because if the peer rejects BUNDLE but accepts the m=
> >>>>> section then it's broken.
> >>>>
> >>>> Note that in this case the usage of BUNDLE has already been
> negotiated.
> >>>> Then, if the answerer does not accept the new m= section into the
> BUNDLE
> >>>> group, it needs to send an offer where it removes it, as described in
> >>>> section 8.3.3.
> >>>
> >>> Well, both of these options correspond to insisting that the m= section
> >>> be in the BUNDLE group. If I just want to suggest it, I would have to
> provide
> >>> a fresh unique address. Or are you saying that's impossible.
> >>>
> >> Yes.
> >>
> >> Previously, when the offerer wanted to add a new m- section to a BUNDLE
> >> group, it had to choice of either assigning a unique address or a
> >> previously negotiated bundle address.
> >>
> >> That option was removed as part of task (triggered by WGLC comments etc)
> >
> > That seems like a pretty material change. Was there a call for consensus
> on that?
>
> No. But, the suggested changes were indicated on the list, there were pull
> requests etc, so people were informed about it and had a chance to
> comment/object.
>

Hmm... Ben, do you think these were properly surfaced to the WG?

-Ekr


> trying to simplifying the procedures. Currently the offerer must either
> > assign a bundle address (previously negotiated or new suggested) or
> > indicate it as bundle-only.
> >
> > At minimum this needs to be clearly stated
>
> I need to modify the section, so I will add text about it.
>
> Regards,
>
> Christer
>
>

--000000000000a846b5056a0f5fe3
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 Tue, Apr 17, 2018 at 11:11 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div class=3D"HOEnZb"><div class=3D"h5">Hi,<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
DISCUSS:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0When an offerer generates an offer, in which =
it wants to add a new<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0bundled &quot;m=3D&quot; section, the offerer=
 MUST:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 Assign the offerer BUN=
DLE address:port (previously selected<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[Section 8.3.1] o=
r newly suggested [Section 8.5.1]) to the added<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;m=3D&quot; =
section; or<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn&#39;t sound right. You can&#39;t=
 use the existing<br>
&gt;&gt;&gt;&gt;&gt; address:port, because if the peer rejects BUNDLE but a=
ccepts the m=3D<br>
&gt;&gt;&gt;&gt;&gt; section then it&#39;s broken.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that in this case the usage of BUNDLE has already bee=
n negotiated.<br>
&gt;&gt;&gt;&gt; Then, if the answerer does not accept the new m=3D section=
 into the BUNDLE<br>
&gt;&gt;&gt;&gt; group, it needs to send an offer where it removes it, as d=
escribed in<br>
&gt;&gt;&gt;&gt; section 8.3.3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Well, both of these options correspond to insisting that the m=
=3D section<br>
&gt;&gt;&gt; be in the BUNDLE group. If I just want to suggest it, I would =
have to provide<br>
&gt;&gt;&gt; a fresh unique address. Or are you saying that&#39;s impossibl=
e.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Yes.<br>
&gt;&gt;<br>
&gt;&gt; Previously, when the offerer wanted to add a new m- section to a B=
UNDLE<br>
&gt;&gt; group, it had to choice of either assigning a unique address or a<=
br>
&gt;&gt; previously negotiated bundle address.<br>
&gt;&gt;<br>
&gt;&gt; That option was removed as part of task (triggered by WGLC comment=
s etc)<br>
&gt;<br>
&gt; That seems like a pretty material change. Was there a call for consens=
us on that?<br>
<br>
</div></div>No. But, the suggested changes were indicated on the list, ther=
e were pull requests etc, so people were informed about it and had a chance=
 to comment/object.<br></blockquote><div><br></div><div>Hmm... Ben, do you =
think these were properly surfaced to the WG?</div><div><br></div><div>-Ekr=
</div><div><br></div><div><br><span class=3D""></span><span class=3D""></sp=
an></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
&gt; trying to simplifying the procedures. Currently the offerer must eithe=
r<br>
&gt; assign a bundle address (previously negotiated or new suggested) or<br=
>
&gt; indicate it as bundle-only.<br>
&gt;<br>
&gt; At minimum this needs to be clearly stated<br>
<br>
</span>I need to modify the section, so I will add text about it.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote></div><br></div></div>

--000000000000a846b5056a0f5fe3--


From nobody Tue Apr 17 12:22:57 2018
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 3D4C812D96B for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 12:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lr3-DpGU8Z3o for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 12:22:52 -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 3FB61127909 for <mmusic@ietf.org>; Tue, 17 Apr 2018 12:22:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1523992970; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+DK+PwHg7uIVUbG3G1Lrksmyp0x1cu2+TRZDfiEBUjE=; b=BGGLwgd3m44cBG9D7MjgGQzyfRnh7coGH/Oqan7bBcyBf2l+ACUPCAIh6SUnSw/x nJLnwjCN37S4vpCGpQk9GqDucKHF7TDiQ1xF5cvLMStTk0XKb1B5NuQmN4k8SHBD j/ZTAPTtH+T8+YrRoh8qMwO54qYPcMsWNKFLECKBtS4=;
X-AuditID: c1b4fb30-1ebff70000005970-00-5ad6498adbaf
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id A8.91.22896.A8946DA5; Tue, 17 Apr 2018 21:22:50 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0382.000; Tue, 17 Apr 2018 21:22:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
Thread-Index: AQHT1lZf0qxFmZgCwkeSofFpx7VVFA==
Date: Tue, 17 Apr 2018 19:22:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [153.88.183.172]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8A1A834633F9D447BF4376B8B681ADD8@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEIsWRmVeSWpSXmKPExsUyM2J7iG6X57Uog57vEhbTZ71js1jx+hy7 xfsLuhYz/kxktji/cz2TxdTlj1kc2Dym/N7I6rFkyU8mj8mP25gDmKO4bFJSczLLUov07RK4 Mnbc7GAt2LaSseJ9+3aWBsY3LYxdjJwcEgImEl9W/WbuYuTiEBI4wijR3bEBylnMKPH51E62 LkYODjYBC4nuf9ogDSICVhKvfl9jAalhFvjCKPHs81GwScICtRKbfx5jgSiqk1iw+DAThK0n caH1CVgNi4CqxLZbt9hBbF4BX4mdl08xg9iMAmIS30+tAatnFhCXuPVkPhPEdQISS/acZ4aw RSVePv7HCmKLAs3ccOI2O8htEgJKEg0zWSBa9SRuTJ3CBmFbS3QcPARla0ssW/iaGWKtoMTJ mU9YJjCKzkKybRaS9llI2mchaZ+FpH0BI+sqRtHi1OKk3HQjI73Uoszk4uL8PL281JJNjMCY O7jlt8EOxpfPHQ8xCnAwKvHwPnW7FiXEmlhWXJl7iFGCg1lJhHfn4ytRQrwpiZVVqUX58UWl OanFhxilOViUxHkt/DZHCQmkJ5akZqemFqQWwWSZODilGhiX/e07Vqf+bXH/YtXNxVZXwo3Z 4xnnf9a9Iajs/VUpjkt+w0un7act9ykJVjBoueefrpV/kdY/8eitLdPOTmpXPrpb92PRjjuh QUpbDRNa/73w0bn9QHg6x8yTnA/mfj8o/t1e4cNdmYMXuPtsfD7fD8g79H/d7x8degKmv9ZW xPfKymaUT49RYinOSDTUYi4qTgQAUiQMXLUCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/yn8Bp8hgkPnCB1YHFDpHIdxCvaA>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 19:22:56 -0000

Hi,

In this reply I address the COMMENTs.

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

>>    Negotiating Media Multiplexing Using the Session Description Protocol
>>                                    (SDP)
>>               draft-ietf-mmusic-sdp-bundle-negotiation-49.txt
>>  =20
>>   Abstract
>=20
> This document is quite a bit improved from when I read it before, but
> it's still very confusing. The primary problem here is the repeated
> use of "address;port" as synechdoche for the m=3D section which is the
> "head" of the BUNDLE group (i.e., that which is indicated by the
> BUNDLE-tag). That's not what's going on and it's misplaced
> concreteness. I would invent some new term ("head" is actually not
> bad) and then use it throughout for this concept.

This is discussed in the thread following Adam's comments.

---

>> to negotiate which "m=3D" sections will become part of a BUNDLE group.
>> Within a BUNDLE group, each "m=3D" section will use a BUNDLE
>> transport for sending and receiving bundled media.
>>  =20
>> Within a BUNDLE group, each endpoint uses a single address:port
>> combination for sending and receiving bundled media.  The
>=20
> Nit: "pair"?

"combination" has been used in the draft for a long time, and is also used
in other places.

Anyway, I guess this may go away depending on the outcome of the "address:p=
ort" discussion.

---

>> combination for sending and receiving bundled media.  The
>> address:port combination is referred to as the BUNDLE address:port.
>> In addition to negotiating the BUNDLE group, the offerer and answerer
>> [RFC3264] use the BUNDLE extension to negotiate the BUNDLE
>> addresses:ports, one for the offerer (offerer BUNDLE address) and
>> one for the answerer (answerer BUNDLE address:port).  Once the offerer
>
> Why is one of these called "address" and the other "address:port"?

Both shall be "address:port".=20

Again, I guess this may also go away depending on the outcome of the "addre=
ss:port" discussion.

---

>> can be used to request that specific media is only used if the "m=3D"
>> section describing the media is kept within a BUNDLE group.
>>  =20
>> This specification updates RFC 3264 [RFC3264], to allow assigning a
>> zero port value to a "m=3D" section without meaning that the media
>> described by the "m=3D" section is disabled or rejected.
>=20
> 1. Bundle lets you have multiple SDP m=3D sections on a single 5-tuple
> 2. The underling mechanism here is that you put those m=3D sections in th=
e
> same BUNDLE group
> 3. In order to facilitate demuxing, we define a new RTP extension for
> MID.
> 4. It is sometimes desirable to say that an m=3D section should only be
> negotiated if it can be bundled.
> This is done with port=3D0 and a=3Dbundle-only.
>
>> can be used to request that specific media is only used if the "m=3D"
>> section describing the media is kept within a BUNDLE group.
>>  =20
>> This specification updates RFC 3264 [RFC3264], to allow assigning a
>> zero port value to a "m=3D" section without meaning that the media
>> described by the "m=3D" section is disabled or rejected.
>=20
> This section is kind of a laundry list. I think it would be helpful to
> break it out conceptually. Specifically.
> 1.
> 2.
> 3.

I will take a look.

---

>> "m=3D" section: SDP bodies contain one or more media descriptions,
>> referred to as "m=3D" sections.  Each "m=3D" section is represented by
>> an SDP "m=3D" line, and zero or more SDP attributes associated with the
>> "m=3D" line.  A local address:port combination is assigned to each
>> "m=3D" section.
>
> Was this intended to be a bullet?

Yes. Will be fixed.

---

>> o  Bundled media: All media associated with a given BUNDLE group.
>>  =20
>> o  Initial offer: The first offer, within an SDP session (e.g. a
>>     SIP dialog when the Session Initiation Protocol (SIP) [RFC3261] is
>>     used to carry SDP), in which the offerer indicates that it wants
>>     to create a given BUNDLE group.
>=20
> This is a very idiosyncratic definition, because it's *not* the first
> offer in the session, but the one where the BUNDLE group is
> introduced. Given that 3264 has a different meaning for this same
> term, and the difference is critical, I would strongly urge you to
> pick a different term.

I believe there are other drafts with similar definitions of "Initial
Offer".

Anyway, would something like "Initial BUNDLE offer" be better?

---

>> The BUNDLE extension is indicated using an SDP 'group' attribute
>> with a semantics value [RFC5888] of "BUNDLE".  An identification-tag is
>> assigned to each bundled "m=3D" section, and each identification-tag
>> is listed in the SDP 'group:BUNDLE' attribute identification-tag list.
>> Each "m=3D" section whose identification-tag is listed in the
>> identification-tag list is associated with a given BUNDLE group.
>=20
> How about "is part of" instead of "associated with"

There are most likely other instances that would have to be fixed, and I'd =
like to try to maintain consistent terminology.=20

---

>>      Each "m=3D" section whose identification-tag is listed in the
>>      identification-tag list is associated with a given BUNDLE group.
>>  =20
>>      SDP bodies can contain multiple BUNDLE groups.  Any given bundled
>>      "m=3D" section MUST NOT be associated with more than one BUNDLE gro=
up
>>      at any given time.
>=20
> Again "part of"

There are multiple instances of "associated with BUNDLE group" terminology =
throughout the document.

---

>> assign a zero port value to the "m=3D" section.  According to
>> [RFC3264] an answerer will reject such an "m=3D" section.  By including =
an SDP
>> 'bundle-only' attribute in such an "m=3D" section, the offerer can
>> request that the answerer accepts the "m=3D" section if the answerer
>> supports the BUNDLE extension, and if the answerer keeps the "m=3D"
>> section within the associated BUNDLE group.
>=20
> I would put some of this text up before the attribute definition to
> explain why the attribute exists.

I suggest moving up the whole paragraph.

---

>> SDP offers and answers can contain multiple BUNDLE groups.  The
>> procedures in this section apply independently to a given BUNDLE
>> group.
>>  =20
>> 8.1.  Multiplex Category Considerations
>=20
> Multiplexing?

It used to be "Mux Category Considerations", but someone requested to modif=
y to "Multiplex".

But, I am ok with "Multiplexing", as that is also used in draft-ietf-mmusic=
-sdp-mux-attributes, so I will fix as suggested.

---

>> When a BUNDLE group is initially negotiated, and a unique
>> address:port is assigned to each bundled "m=3D" section (excluding
>> any bundle-only "m=3D" section) in the initial offer [Section 8.2], any
>> IDENTICAL and TRANSPORT mux category SDP attributes included in the
>> BUNDLE group MUST explicitly be included in each bundled
>>  "m=3Da&#128;&#156; section (excluding any bundle-only "m=3D" sections).
>=20
> Something bad happened here with your editor.

Will be fixed.

---

>> BUNDLE group MUST explicitly be included in each bundled
>> "m=3Da&#128;&#156; section (excluding any bundle-only "m=3D" sections).
>>  =20
>> When an offerer or answerer includes SDP attributes in bundled "m=3D"
>> sections within a BUNDLE group for which the offerer and answerer
>> BUNDLE addresses:ports have been selected, IDENTICAL and TRANSPORT
>=20
> This is pretty opaque. It's not that the address:port pair have been
> selected but rather that BUNDLE has been negotiated for that m=3D
> section (though of course the address:port being selected is a side
> effect of this).

I suggest to remove "for which the offerer and answerer BUNDLE addresses:po=
rts have been selected".

---

>> The semantics of some SDP attributes only apply to specific types of
>> media.  For example, the semantics of the SDP 'rtcp-mux' and SDP
>> 'rtcp-mux-only' attributes only apply to "m=3D" sections describing
>> RTP-based media.  However, as described in Section 8.1, there are
>> cases where IDENTICAL and TRANSPORT mux category SDP attributes are
>> only included in the "m=3D" sections indicated by the BUNDLE-tag.
>> That
>=20
> Huh? This is section 8.1.

It should be "as described above".

> This whole paragraph is a mess. I would say
>=20
> "One consequence of these rules is that because SDP attributes which
> are appropriate only to some other m=3D section may appear in the m=3D
> section indicated by the BUNDLE-tag. For instance, the BUNDLE-tag may
> indicate a data channel but contain the 'rtcp-mux' attribute because
> that applies to an RTP m=3D section that is part of the BUNDLE group"
> type of media.

I will take a look.

---

>> 8.2.  Generating the Initial SDP Offer
>>  =20
>>     When an offerer generates an initial offer, to negotiate a BUNDLE
>>     group, it MUST:
>=20
> This sentence is ungrammatical. "In order to negotiate a BUNDLE group
> in an initial offer, the offerer MUST"

In an earlier version of the draft the text said:

"When an offerer generates an initial offer, in order to create a BUNDLE
group, it MUST:"

I was then asked to remove the "in order to".

But, I can modify as suggested, because I do agree that it sounds better.

---

>> within the BUNDLE group, the offerer MUST:
>>  =20
>> o  Include an SDP 'bundle-only' attribute [Section 8.2.1] in the
>>     "m=3D" section; and
>>  =20
>> o  Assign a zero port value to the "m=3D" section.
>=20
> I would reorder these, because the zero port is the main semantic.

I will modify as suggested.

---

>> NOTE: If the offerer assigns unique addresses:ports to multiple
>> bundled "m=3D" sections, the offerer needs to be prepared to receive
>> bundled media on each unique address:port, until it receives the
>> associated answer and finds out which address:port combination has
>> been selected as the offerer BUNDLE-address.
>=20
> Why is this an "If"? There are only two choices: "unique" and "zero".
> Just put this graf up before the discussion of bundle-only and you can
> remove the conditional

I suggest to move up the paragraph, and replace "If" with "When".

---

>> It is RECOMMENDED that the offerer assigns the suggested offerer
>> BUNDLE address:port to a bundled "m=3D" section that the offerer
>> assumes it is unlikely that the answerer will reject, or move out
>> of the BUNDLE group.  How such assumption is made is outside the scope
>> of this document.
>
> I would say "believes" rather than "assumes"

I will modify as suggested.

---

>> b=3DAS:1000
>> a=3Dmid:bar
>> a=3Drtcp-mux
>> a=3Drtpmap:31 H261/90000
>> a=3Drtpmap:32 MPV/90000
>> a=3Dextmap 1 urn:ietf:params:rtp-hdrext:sees:mid
>
> Line breaks between the m=3D sections would help here.

I will modify as suggested.

---

>> When an answerer generates an answer that contains a BUNDLE group,
>> the following general SDP grouping framework restrictions, defined
>> in [RFC5888], also apply to the BUNDLE group:
>>  =20
>> o  The answerer MUST NOT include a BUNDLE group in the answer,
>>     unless
>
> Comma not needed here.

Will fix.

>Also, this negative phrasing is hard to follow. I would say "MUST only
>... if" here and below

That would result in:

      o  The answerer MUST only include a BUNDLE group in the answer if
        the offerer requested the BUNDLE group to be negotiated in the
        corresponding offer; and

      o  The answerer MUST only include an "m=3D" section within a BUNDLE
        Group if the offerer requested the "m=3D" section to be within
        that BUNDLE group in the corresponding offer.

I think that is weird. If I do the change, I guess "MUST" should be
replaced with e.g., "can":

      o The answerer can only include a BUNDLE group in the answer if
        the offerer requested the BUNDLE group to be negotiated in the
        corresponding offer; and

      o The answerer can only include an "m=3D" section within a BUNDLE
        Group if the offerer requested the "m=3D" section to be within
        that BUNDLE group in the corresponding offer.

---

>> o  The answerer MUST NOT include an "m=3D" section within a BUNDLE
>>     group, unless the offerer requested the "m=3D" section to be within
>>     that BUNDLE group in the corresponding offer.
>>  =20
>> o  If the answer contains multiple BUNDLE groups, the answerer MUST
>>     NOT move an "m=3D" section from one BUNDLE group to another.
>
> This bullet is unnecessary as it immediately follows from the
> proceeding bullet.

I will remove the second bullet.

---

>> If the answer contains a BUNDLE group, the answerer MUST:
>>  =20
>> o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
>>  =20
>> o  Select an answerer BUNDLE address:port [Section 8.3.2].
>
> This isn't right, because each BUNDLE group has its own address:port,
> so instead "For each BUNDLE group" contained in the offer.

The procedures is for individual BUNDLE groups, as indicated in Section 8:

 "SDP offers and answers can contain multiple BUNDLE groups.  The
  procedures in this section apply independently to a given BUNDLE
  group."

> More importantly, it's not the address:port that the answerer chooses,
> but rather the m=3D section. I.e.,
>
> o Determine the first m=3D section in the BUNDLE group which will be
>   BUNDLEd in the answer
> o Select an answerer BUNDLE address:port

I don't understand what "first m=3D section which will be BUNDLEd" means. W=
hat is "first"?

---

>> o  The answerer will not reject the "m=3D" section [Section 8.3.4];
>>     and
>>
>> o  The "m=3D" section does not contain a zero port value.
>>
>> If all of the criteria above are fulfilled, the answerer MUST select
> the suggested offerer BUNDLE address:port.
>
> Again, this isn't selecting the address:port but rather the m=3Dsection

Sure, but it picks the address:port of that selected m=3D section.

---

>> bundled "m=3D" section the answerer MUST assign a zero port value and
>> include an SDP 'bundle-only' attribute.
>>
>> The answerer MUST NOT assign an answerer BUNDLE address:port to an
>> "m=3D" section that is not within the BUNDLE group, or to an "m=3D"
>> section that is within another BUNDLE group.
>
> This repeats text in S 8.3.

What text do you think is repeated?

---

>> group in an answer, it MUST first check the following criteria:
>>
>> o  In the corresponding offer, an offerer BUNDLE address:port
>>     (previously selected [Section 8.3.1] or newly suggested
>>     [Section 8.5.1]) has been assigned to the "m=3D" section by the
>>     offerer; or
>
> This text is baffling. As far as I can see, the first condition is
> "don't pick it as the head m=3D section if you intend to move it out".
> The second is some entirely different case. Can you rewrite it so it
> makes sense.

Actually, based on the current procedures, if the BUNDLE group exists,
either criteria will always be fulfilled, so the only way for the answerer
to move a bundled m- line out of a group is by sending an offer, as
described later in the section.

Also, the text contains "includes a BUNDLE group" terminology, but also
covers cases where the BUNDLE group has not yet been created. So, I think
the procedures for the answerer needs to be split into:

1. Creating initial answer, where the offerer asks for a BUNDLE group to
be negotiated
2. Creating answer to subsequent answer, where a BUNDLE group has
previously been negotiated.

I will try to come up with something.

---

>> either reject the whole offer, reject each bundled "m=3D" section
>> within the BUNDLE group [Section 8.3.4], or keep the "m=3D" section
>> within the BUNDLE group in the answer and later create an offer
>> where the "m=3D" section is moved out of the BUNDLE group [Section 8.5.3=
].
>>
>> When the answerer generates an answer, in which it moves a bundled
>
> No comma

Will fix.

---

>> o  MUST NOT assign an SDP 'bundle-only' attribute to the "m=3D"
>>      section.
>>
>> An answerer MUST NOT move an "m=3D" section from one BUNDLE group to
>> another within an answer.  If the answerer wants to move an "m=3D"
>
> This is the third time you have said this. If you want to say it here,
> say "Because ..., if"

I will modify as suggested.

---

>> it MUST first check the following criteria:
>>
>> o  In the corresponding offer, an offerer BUNDLE address:port
>>     (previously selected [Section 8.3.1] or newly suggested
>>     [Section 8.5.1]) has been assigned to the "m=3D" section by the
>>     offerer.
>
> Same comment here as above. These are entirely different conditions.

See above.

---

>> o  In the corresponding offer, an offerer BUNDLE address:port
>>     (previously selected [Section 8.3.1] or newly suggested
>>     [Section 8.5.1]) has been assigned to the "m=3D" section by the
>>     offerer.
>>
> If the criteria above is fulfilled, the answerer can not reject the
>=20
> "criteria... are"

Someone said it should be "is", but I am fine using "are", and can fix as s=
uggested.

---

>> reject the whole offer, reject each bundled "m=3D" section within the
>> BUNDLE group, or keep the "m=3D" section within the BUNDLE group in
>> the answer and later create an offer where the "m=3D" section is disable=
d
>> within the BUNDLE group [Section 8.5.4].
>>  =20
>> When an answerer generates an answer, in which it rejects a bundled
>=20
> No comma

Will fix.

---

>> m=3Dvideo 0 RTP/AVP 32
>> b=3DAS:1000
>> a=3Dmid:bar
>> a=3Dbundle-only
>> a=3Drtpmap:32 MPV/90000
>> a=3Dextmap 1 urn:ietf:params:rtp-hdrext:sdes:mid
>=20
> Please put line breaks in between m=3D sections here too

Will do.

---

>>   8.4.  Offerer Processing of the SDP Answer
>>  =20
>>      When an offerer receives an answer, if the answer contains a BUNDLE
>>      group, the offerer MUST check that any bundled "m=3D" section in th=
e
>>      answer was indicated as bundled in the corresponding offer.  If
>>      there is no mismatch, the offerer MUST use the offerer BUNDLE
>>      address:port,
>
> address:port, again. It's the m=3Dsection that's relevant.

Yes, but it uses the address:port of the m=3D section.

What do you suggest to say instead?

---

>> bundled "m=3D" section.
>>  =20
>> NOTE: As the answerer might reject one or more bundled "m=3D" sections,
>> or move a bundled "m=3D" section out of a BUNDLE group, each bundled
>> "m=3D" section in the offer might not be indicated as bundled in the
>> answer.
>=20
> "each" -> "an given"

I will change as suggested (I assume you mean "a given").

---

>> When the offerer generates a subsequent offer, the offerer
>> BUNDLE-tag MUST represent the bundled "m=3D" section to which the offere=
r BUNDLE
>> address:port (previously negotiated or newly suggested) has been assigne=
d.
>>  =20
>> 8.5.1.  Suggesting a New Offerer BUNDLE Address:Port
>=20
> Again it would make more sense to describe this as suggesting a new m=3D =
section.

It does not have to be a new "m=3D" section. The new address:port can be as=
signed to an existing "m=3D" section.

---

>> section out of a BUNDLE group.
>>  =20
>> 8.5.4.  Disabling a Media Description in a BUNDLE Group
>>  =20
>> When an offerer generates an offer, in which it wants to disable a
>> bundled "m=3D" section, the offerer:
>=20
> Are you sure disable -> port 0, as opposed to "inactive"

Yes. "disable" terminology is also used in RFC 3264.

---

>> configuration and packetization.
>> [I-D.ietf-mmusic-sdp-mux-attributes] lists SDP attributes, whose
>> attribute values are required to be identical for all codecs that
>> use the same payload type value.
>>  =20
>>   10.2.  Associating RTP/RTCP Streams with Correct SDP Media Description
>=20
> Nit "the correct"

Will fix.

---

>> "m=3D" sections), following the procedures for IDENTICAL mux category
>> attributes in Section 8.1.  In addition, the offerer MAY include an
>> SDP 'rtcp-mux-only' attribute [I-D.ietf-mmusic-mux-exclusive] in a
>> RTP-based bundled "m=3D" section.
>>  =20
>> NOTE: Whether the offerer associates the SDP 'rtcp-mux-only=B9
>
> associates -> includes

Will fix.

---

>> an offerer BUNDLE address:port (previously selected
>> [Section 8.3.1] or newly suggested [Section 8.5.1]) to a bundled
>> "m=3D" section (the "m=3D" section indicated by the offerer BUNDLE-
>> tag), the offerer only includes ICE-related media-level SDP
>> attributes in that "m=3D" section, following the procedures in
>> Section 8.1.
>
> You should rewrite this graf and the one below to be about BUNDLED-
> ness not port assignment. I.e., if you are definitely bundled, willing
> to bundle, or not bundled.

Will look into it.

---

>> Support and usage of ICE mechanism together with the BUNDLE
>> extension is OPTIONAL, and the procedures in this section only apply whe=
n the
>> ICE mechanism is used.  Note that applications might mandate usage
>> of the ICE mechanism even if the BUNDLE extension is not used.
>>  =20
>>   11.1.  SDP Offer/Answer Procedures
>=20
> Same point here as above. Talking about address:port isn't helpful.

Will look into it.

---

Regards,

Christer


From nobody Tue Apr 17 12:46:36 2018
Return-Path: <kaduk@mit.edu>
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 0CB7D126CF6; Tue, 17 Apr 2018 12:46:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk <kaduk@mit.edu>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152399439000.11503.16295774125201082539.idtracker@ietfa.amsl.com>
Date: Tue, 17 Apr 2018 12:46:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/hamqpSSqVvdTf2hSY6FN-cHkFNQ>
Subject: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-rid-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 19:46:30 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-mmusic-rid-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-rid/



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

Presumably I'm just being dense, but from perusing the formal grammar
I couldn't decide if it's allowed to have both PT and parameter
restrictions applied on the same rid-id.

Section 5

Similarly (me being dense), I'm a bit confused at the relationship between
max-fps and max-pps -- aren't there encodings that can send update frames that
do not include the full pixel density of a frame?

Section 6.2.2

   4.  If the "direction" field is "recv", The answerer ensures that
       "a=rid" restrictions are supported.  In the case of an
       unsupported restriction, the "a=rid" line is discarded.

"that "a=rid" restrictions are supported" reads like a feature test
for being able to parse a=rid at all, but the context suggests that
this is intended to refer to the Section-5 restriction stanzas that
appear on an a=rid line.

Section 8

I thought I remembered something going by to the effect of s/non-empty
union/non-empty intersection/ but didn't find it in a quick search, so dropping
a note just in case.

Section 8.2

   The following codec format parameters correspond to restrictions on
   receiver capabilities, and never indicate sending restrictions.

Maybe "The codec format parameters covered in the following
subsections [...]"?

Section 10

Should
    float-param-val   = 1*DIGIT "." 1*DIGIT
have the last entry be 1*4DIGIT to catch the "four digits after the
decimal place" requirement of max-bpp, or are we leaving the float-param-value
grammar less restricted in case of potential future use?



From nobody Tue Apr 17 13:14:37 2018
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 E066912DA0D for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 13:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 uk4ECf4g6P0I for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 13:14:31 -0700 (PDT)
Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::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 0731012D9FF for <mmusic@ietf.org>; Tue, 17 Apr 2018 13:14:27 -0700 (PDT)
Received: by mail-ot0-x22f.google.com with SMTP id m22-v6so22801275otf.8 for <mmusic@ietf.org>; Tue, 17 Apr 2018 13:14:27 -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=WAEmoefQTsF5wdKtXI8FDG1NTd/dyALnx9UNOjMbef0=; b=V0KuWjTeubmRLjx8th0kqcXhqcUMY/eArxtTmf6LLwji29JpI1JtJe76sUR4mKH/lH GKXeRxBd8dozy2ty91CVAAXval06X4xLc6S8wgpAxUqUb8hRTLyiZK+kdHi4GUHAxH0z adrpgCceI6Ti4KUV1mfi3nq4DVZJAI44029akWgmCbwg87owz7bIg+REAiXG07Cu3ziK FL8okzEhbxX9JnkMN3uZv9HzRZuRztuWALIB76W7ySEzcUCxesbGrH72CxZFY1d6q+4R QG5DqLhl6Z65AA8AAzv6jRNHs5zESqAmvMiD2pv+WAqMZRoDM4AyL8oV9hhZzX4M0ZY4 wWwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WAEmoefQTsF5wdKtXI8FDG1NTd/dyALnx9UNOjMbef0=; b=hkqKAhcPLFEw8FYQ1T9EO8nv8LfJ4mOxXkHgvaAGz5Q7bJQNbcHNdhQ1Oei5JNOFMf fP4ggjDaloLiI+nSHzXvF0CDBWGxTVj4Ld2+Hngw7oOAfRRk5693HBQwMEHQD9Y3XZY9 zUyqmvQ7DJmTjbgyylHWuRVLKq1pEIqpC7m8Y9v3pq2cQricHtt0XODLIPKg0tVt1pU0 K7xgqmZcF0O1HSoVmZekMk/ozUuL8kBLrQ2S32/DLX8AnkvACRl1I8NP36WL5rE8OyeW 9a8iVNkSMqvBJdzJhHDxeduF9hKFiqOatAJXng8iu+Crap6LghhvbKw9VqnOAA/q+zoZ hCuw==
X-Gm-Message-State: ALQs6tDSYuCXY350Eyz8dJL62LYfsRGFkYtZwTD86PG2ye9juyTJ3q8z EqfJZnXRxqTSFnWZ4PWd4/WxP89bw3DkMmYIY4u7Gg==
X-Google-Smtp-Source: AIpwx49ht0KQoJtZfxK4QVTugtLJznJcJpQRqS6rDi8Z+4q5N3yTo/AmXX76xnquCQIVUt/oGSWAtnJUwdGDaldHh2U=
X-Received: by 2002:a9d:36dc:: with SMTP id s28-v6mr2053725otd.214.1523996066272;  Tue, 17 Apr 2018 13:14:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 13:13:45 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 13:13:45 -0700
Message-ID: <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002b6cbc056a10fc19"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wKFuLyisxee0QTy4tyFgG2WtJgI>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 20:14:34 -0000

--0000000000002b6cbc056a10fc19
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 17, 2018 at 12:22 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> In this reply I address the COMMENTs.
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> >>    Negotiating Media Multiplexing Using the Session Description Protocol
> >>                                    (SDP)
> >>               draft-ietf-mmusic-sdp-bundle-negotiation-49.txt
> >>
> >>   Abstract
> >
> > This document is quite a bit improved from when I read it before, but
> > it's still very confusing. The primary problem here is the repeated
> > use of "address;port" as synechdoche for the m= section which is the
> > "head" of the BUNDLE group (i.e., that which is indicated by the
> > BUNDLE-tag). That's not what's going on and it's misplaced
> > concreteness. I would invent some new term ("head" is actually not
> > bad) and then use it throughout for this concept.
>
> This is discussed in the thread following Adam's comments.
>

OK.



> >> to negotiate which "m=" sections will become part of a BUNDLE group.
> >> Within a BUNDLE group, each "m=" section will use a BUNDLE
> >> transport for sending and receiving bundled media.
> >>
> >> Within a BUNDLE group, each endpoint uses a single address:port
> >> combination for sending and receiving bundled media.  The
> >
> > Nit: "pair"?
>
> "combination" has been used in the draft for a long time, and is also used
> in other places.
>

I'm prepared to believe both of these statements, but in my experience
"pair" is far more common.


> Anyway, I guess this may go away depending on the outcome of the
> "address:port" discussion.
>
> ---
>
>
>
> ---
>
> >> "m=" section: SDP bodies contain one or more media descriptions,
> >> referred to as "m=" sections.  Each "m=" section is represented by
> >> an SDP "m=" line, and zero or more SDP attributes associated with the
> >> "m=" line.  A local address:port combination is assigned to each
> >> "m=" section.
> >
> > Was this intended to be a bullet?
>
> Yes. Will be fixed.
>
> ---
>
> >> o  Bundled media: All media associated with a given BUNDLE group.
> >>
> >> o  Initial offer: The first offer, within an SDP session (e.g. a
> >>     SIP dialog when the Session Initiation Protocol (SIP) [RFC3261] is
> >>     used to carry SDP), in which the offerer indicates that it wants
> >>     to create a given BUNDLE group.
> >
> > This is a very idiosyncratic definition, because it's *not* the first
> > offer in the session, but the one where the BUNDLE group is
> > introduced. Given that 3264 has a different meaning for this same
> > term, and the difference is critical, I would strongly urge you to
> > pick a different term.
>
> I believe there are other drafts with similar definitions of "Initial
> Offer".
>

Perhaps, but as I noted, 3264s disagrees.


> Anyway, would something like "Initial BUNDLE offer" be better?
>

Not really.


> ---
>
> >> The BUNDLE extension is indicated using an SDP 'group' attribute
> >> with a semantics value [RFC5888] of "BUNDLE".  An identification-tag is
> >> assigned to each bundled "m=" section, and each identification-tag
> >> is listed in the SDP 'group:BUNDLE' attribute identification-tag list.
> >> Each "m=" section whose identification-tag is listed in the
> >> identification-tag list is associated with a given BUNDLE group.
> >
> > How about "is part of" instead of "associated with"
>
> There are most likely other instances that would have to be fixed, and I'd
> like to try to maintain consistent terminology.
>

Yes, I would change all of them.

>
> ---
>
> >>      Each "m=" section whose identification-tag is listed in the
> >>      identification-tag list is associated with a given BUNDLE group.
> >>
> >>      SDP bodies can contain multiple BUNDLE groups.  Any given bundled
> >>      "m=" section MUST NOT be associated with more than one BUNDLE group
> >>      at any given time.
> >
> > Again "part of"
>
> There are multiple instances of "associated with BUNDLE group" terminology
> throughout the document.
>

Yes, and they're all bad.


> ---
>
> >> assign a zero port value to the "m=" section.  According to
> >> [RFC3264] an answerer will reject such an "m=" section.  By including
> an SDP
> >> 'bundle-only' attribute in such an "m=" section, the offerer can
> >> request that the answerer accepts the "m=" section if the answerer
> >> supports the BUNDLE extension, and if the answerer keeps the "m="
> >> section within the associated BUNDLE group.
> >
> > I would put some of this text up before the attribute definition to
> > explain why the attribute exists.
>
> I suggest moving up the whole paragraph.
>

OK.




>
> >> BUNDLE group MUST explicitly be included in each bundled
> >> "m=a&#128;&#156; section (excluding any bundle-only "m=" sections).
> >>
> >> When an offerer or answerer includes SDP attributes in bundled "m="
> >> sections within a BUNDLE group for which the offerer and answerer
> >> BUNDLE addresses:ports have been selected, IDENTICAL and TRANSPORT
> >
> > This is pretty opaque. It's not that the address:port pair have been
> > selected but rather that BUNDLE has been negotiated for that m=
> > section (though of course the address:port being selected is a side
> > effect of this).
>
> I suggest to remove "for which the offerer and answerer BUNDLE
> addresses:ports have been selected".
>

O


> >> NOTE: If the offerer assigns unique addresses:ports to multiple
> >> bundled "m=" sections, the offerer needs to be prepared to receive
> >> bundled media on each unique address:port, until it receives the
> >> associated answer and finds out which address:port combination has
> >> been selected as the offerer BUNDLE-address.
> >
> > Why is this an "If"? There are only two choices: "unique" and "zero".
> > Just put this graf up before the discussion of bundle-only and you can
> > remove the conditional
>
> I suggest to move up the paragraph, and replace "If" with "When".
>

OK.


> >> When an answerer generates an answer that contains a BUNDLE group,
> >> the following general SDP grouping framework restrictions, defined
> >> in [RFC5888], also apply to the BUNDLE group:
> >>
> >> o  The answerer MUST NOT include a BUNDLE group in the answer,
> >>     unless
> >
> > Comma not needed here.
>
> Will fix.
>
>

> >Also, this negative phrasing is hard to follow. I would say "MUST only
> >... if" here and below
>
> That would result in:
>
>       o  The answerer MUST only include a BUNDLE group in the answer if
>         the offerer requested the BUNDLE group to be negotiated in the
>         corresponding offer; and
>
>       o  The answerer MUST only include an "m=" section within a BUNDLE
>         Group if the offerer requested the "m=" section to be within
>         that BUNDLE group in the corresponding offer.
>
> I think that is weird. If I do the change, I guess "MUST" should be
> replaced with e.g., "can":
>
>       o The answerer can only include a BUNDLE group in the answer if
>         the offerer requested the BUNDLE group to be negotiated in the
>         corresponding offer; and
>
>       o The answerer can only include an "m=" section within a BUNDLE
>         Group if the offerer requested the "m=" section to be within
>         that BUNDLE group in the corresponding offer.
>

OK.




>
> >> If the answer contains a BUNDLE group, the answerer MUST:
> >>
> >> o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
> >>
> >> o  Select an answerer BUNDLE address:port [Section 8.3.2].
> >
> > This isn't right, because each BUNDLE group has its own address:port,
> > so instead "For each BUNDLE group" contained in the offer.
>
> The procedures is for individual BUNDLE groups, as indicated in Section 8:
>
>  "SDP offers and answers can contain multiple BUNDLE groups.  The
>   procedures in this section apply independently to a given BUNDLE
>   group."'


I don't find this very clear.



> > More importantly, it's not the address:port that the answerer chooses,
> > but rather the m= section. I.e.,
> >
> > o Determine the first m= section in the BUNDLE group which will be
> >   BUNDLEd in the answer
> > o Select an answerer BUNDLE address:port
>
> I don't understand what "first m= section which will be BUNDLEd" means.
> What is "first"?
>

The one indicated by the bundle tag.


> ---
>
> >> o  The answerer will not reject the "m=" section [Section 8.3.4];
> >>     and
> >>
> >> o  The "m=" section does not contain a zero port value.
> >>
> >> If all of the criteria above are fulfilled, the answerer MUST select
> > the suggested offerer BUNDLE address:port.
> >
> > Again, this isn't selecting the address:port but rather the m=section
>
> Sure, but it picks the address:port of that selected m= section.
>

No, it picks the m= section and then uses the attached address:port.


> ---
>
> >> bundled "m=" section the answerer MUST assign a zero port value and
> >> include an SDP 'bundle-only' attribute.
> >>
> >> The answerer MUST NOT assign an answerer BUNDLE address:port to an
> >> "m=" section that is not within the BUNDLE group, or to an "m="
> >> section that is within another BUNDLE group.
> >
> > This repeats text in S 8.3.
>
> What text do you think is repeated?
>


8.3. already says you can't move between BUNDLE groups.


> ---
>
> >> group in an answer, it MUST first check the following criteria:
> >>
> >> o  In the corresponding offer, an offerer BUNDLE address:port
> >>     (previously selected [Section 8.3.1] or newly suggested
> >>     [Section 8.5.1]) has been assigned to the "m=" section by the
> >>     offerer; or
> >
> > This text is baffling. As far as I can see, the first condition is
> > "don't pick it as the head m= section if you intend to move it out".
> > The second is some entirely different case. Can you rewrite it so it
> > makes sense.
>
> Actually, based on the current procedures, if the BUNDLE group exists,
> either criteria will always be fulfilled, so the only way for the answerer
> to move a bundled m- line out of a group is by sending an offer, as
> described later in the section.
>
> Also, the text contains "includes a BUNDLE group" terminology, but also
> covers cases where the BUNDLE group has not yet been created. So, I think
> the procedures for the answerer needs to be split into:
>
> 1. Creating initial answer, where the offerer asks for a BUNDLE group to
> be negotiated
> 2. Creating answer to subsequent answer, where a BUNDLE group has
> previously been negotiated.
>
> I will try to come up with something.
>

OK.



>
> >> o  In the corresponding offer, an offerer BUNDLE address:port
> >>     (previously selected [Section 8.3.1] or newly suggested
> >>     [Section 8.5.1]) has been assigned to the "m=" section by the
> >>     offerer.
> >>
> > If the criteria above is fulfilled, the answerer can not reject the
> >
> > "criteria... are"
>
> Someone said it should be "is", but I am fine using "are", and can fix as
> suggested.
>

OK, well, "criteria" is the plural of "criterion"




> >>   8.4.  Offerer Processing of the SDP Answer
> >>
> >>      When an offerer receives an answer, if the answer contains a BUNDLE
> >>      group, the offerer MUST check that any bundled "m=" section in the
> >>      answer was indicated as bundled in the corresponding offer.  If
> >>      there is no mismatch, the offerer MUST use the offerer BUNDLE
> >>      address:port,
> >
> > address:port, again. It's the m=section that's relevant.
>
> Yes, but it uses the address:port of the m= section.
>
> What do you suggest to say instead?
>

"MUST use the indicated m= section as the bundle <whatever term we choose>"



>
> >> bundled "m=" section.
> >>
> >> NOTE: As the answerer might reject one or more bundled "m=" sections,
> >> or move a bundled "m=" section out of a BUNDLE group, each bundled
> >> "m=" section in the offer might not be indicated as bundled in the
> >> answer.
> >
> > "each" -> "an given"
>
> I will change as suggested (I assume you mean "a given").
>
> ---
>
> >> When the offerer generates a subsequent offer, the offerer
> >> BUNDLE-tag MUST represent the bundled "m=" section to which the offerer
> BUNDLE
> >> address:port (previously negotiated or newly suggested) has been
> assigned.
> >>
> >> 8.5.1.  Suggesting a New Offerer BUNDLE Address:Port
> >
> > Again it would make more sense to describe this as suggesting a new m=
> section.
>
> It does not have to be a new "m=" section. The new address:port can be
> assigned to an existing "m=" section.
>

You're suggesting that a new m= section be the one that things are bundled
into.


> ---
>
> >> section out of a BUNDLE group.
> >>
> >> 8.5.4.  Disabling a Media Description in a BUNDLE Group
> >>
> >> When an offerer generates an offer, in which it wants to disable a
> >> bundled "m=" section, the offerer:
> >
> > Are you sure disable -> port 0, as opposed to "inactive"
>
> Yes. "disable" terminology is also used in RFC 3264.
>

All right.

-Ekr


> Regards,
>
> Christer
>

--0000000000002b6cbc056a10fc19
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 Tue, Apr 17, 2018 at 12:22 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><br>
Hi,<br>
<br>
In this reply I address the COMMENTs.<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
COMMENT:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt;&gt;=C2=A0 =C2=A0 Negotiating Media Multiplexing Using the Session Desc=
ription Protocol<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (SDP)<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-m=
music-sdp-bundle-<wbr>negotiation-49.txt<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;=C2=A0 =C2=A0Abstract<br>
&gt; <br>
&gt; This document is quite a bit improved from when I read it before, but<=
br>
&gt; it&#39;s still very confusing. The primary problem here is the repeate=
d<br>
&gt; use of &quot;address;port&quot; as synechdoche for the m=3D section wh=
ich is the<br>
&gt; &quot;head&quot; of the BUNDLE group (i.e., that which is indicated by=
 the<br>
&gt; BUNDLE-tag). That&#39;s not what&#39;s going on and it&#39;s misplaced=
<br>
&gt; concreteness. I would invent some new term (&quot;head&quot; is actual=
ly not<br>
&gt; bad) and then use it throughout for this concept.<br>
<br>
This is discussed in the thread following Adam&#39;s comments.<br></blockqu=
ote><div><br></div><div>OK.</div><div> <br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
&gt;&gt; to negotiate which &quot;m=3D&quot; sections will become part of a=
 BUNDLE group.<br>
&gt;&gt; Within a BUNDLE group, each &quot;m=3D&quot; section will use a BU=
NDLE<br>
&gt;&gt; transport for sending and receiving bundled media.<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; Within a BUNDLE group, each endpoint uses a single address:port<br=
>
&gt;&gt; combination for sending and receiving bundled media.=C2=A0 The<br>
&gt; <br>
&gt; Nit: &quot;pair&quot;?<br>
<br>
&quot;combination&quot; has been used in the draft for a long time, and is =
also used<br>
in other places.<br></blockquote><div><br></div><div>I&#39;m prepared to be=
lieve both of these statements, but in my experience</div><div>&quot;pair&q=
uot; is far more common.</div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
Anyway, I guess this may go away depending on the outcome of the &quot;addr=
ess:port&quot; discussion.<br>
<br>
---<br>
<br><br>
<br>
---<br>
<br>
&gt;&gt; &quot;m=3D&quot; section: SDP bodies contain one or more media des=
criptions,<br>
&gt;&gt; referred to as &quot;m=3D&quot; sections.=C2=A0 Each &quot;m=3D&qu=
ot; section is represented by<br>
&gt;&gt; an SDP &quot;m=3D&quot; line, and zero or more SDP attributes asso=
ciated with the<br>
&gt;&gt; &quot;m=3D&quot; line.=C2=A0 A local address:port combination is a=
ssigned to each<br>
&gt;&gt; &quot;m=3D&quot; section.<br>
&gt;<br>
&gt; Was this intended to be a bullet?<br>
<br>
Yes. Will be fixed.<br>
<br>
---<br>
<br>
&gt;&gt; o=C2=A0 Bundled media: All media associated with a given BUNDLE gr=
oup.<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; o=C2=A0 Initial offer: The first offer, within an SDP session (e.g=
. a<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0SIP dialog when the Session Initiation Protocol=
 (SIP) [RFC3261] is<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0used to carry SDP), in which the offerer indica=
tes that it wants<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0to create a given BUNDLE group.<br>
&gt; <br>
&gt; This is a very idiosyncratic definition, because it&#39;s *not* the fi=
rst<br>
&gt; offer in the session, but the one where the BUNDLE group is<br>
&gt; introduced. Given that 3264 has a different meaning for this same<br>
&gt; term, and the difference is critical, I would strongly urge you to<br>
&gt; pick a different term.<br>
<br>
I believe there are other drafts with similar definitions of &quot;Initial<=
br>
Offer&quot;.<br></blockquote><div><br></div><div>Perhaps, but as I noted, 3=
264s disagrees.</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Anyway, would something like &quot;Initial BUNDLE offer&quot; be better?<br=
></blockquote><div><br></div><div>Not really.</div><div> <br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
<br>
---<br>
<br>
&gt;&gt; The BUNDLE extension is indicated using an SDP &#39;group&#39; att=
ribute<br>
&gt;&gt; with a semantics value [RFC5888] of &quot;BUNDLE&quot;.=C2=A0 An i=
dentification-tag is<br>
&gt;&gt; assigned to each bundled &quot;m=3D&quot; section, and each identi=
fication-tag<br>
&gt;&gt; is listed in the SDP &#39;group:BUNDLE&#39; attribute identificati=
on-tag list.<br>
&gt;&gt; Each &quot;m=3D&quot; section whose identification-tag is listed i=
n the<br>
&gt;&gt; identification-tag list is associated with a given BUNDLE group.<b=
r>
&gt; <br>
&gt; How about &quot;is part of&quot; instead of &quot;associated with&quot=
;<br>
<br>
There are most likely other instances that would have to be fixed, and I&#3=
9;d like to try to maintain consistent terminology. <br></blockquote><div><=
br></div><div>Yes, I would change all of them.<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
---<br>
<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Each &quot;m=3D&quot; section whose identifica=
tion-tag is listed in the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 identification-tag list is associated with a g=
iven BUNDLE group.<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 SDP bodies can contain multiple BUNDLE groups.=
=C2=A0 Any given bundled<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &quot;m=3D&quot; section MUST NOT be associate=
d with more than one BUNDLE group<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 at any given time.<br>
&gt; <br>
&gt; Again &quot;part of&quot;<br>
<br>
There are multiple instances of &quot;associated with BUNDLE group&quot; te=
rminology throughout the document.<br></blockquote><div><br></div><div>Yes,=
 and they&#39;re all bad.</div><div> <br></div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<br>
---<br>
<br>
&gt;&gt; assign a zero port value to the &quot;m=3D&quot; section.=C2=A0 Ac=
cording to<br>
&gt;&gt; [RFC3264] an answerer will reject such an &quot;m=3D&quot; section=
.=C2=A0 By including an SDP<br>
&gt;&gt; &#39;bundle-only&#39; attribute in such an &quot;m=3D&quot; sectio=
n, the offerer can<br>
&gt;&gt; request that the answerer accepts the &quot;m=3D&quot; section if =
the answerer<br>
&gt;&gt; supports the BUNDLE extension, and if the answerer keeps the &quot=
;m=3D&quot;<br>
&gt;&gt; section within the associated BUNDLE group.<br>
&gt; <br>
&gt; I would put some of this text up before the attribute definition to<br=
>
&gt; explain why the attribute exists.<br>
<br>
I suggest moving up the whole paragraph.<br></blockquote><div><br></div><di=
v>OK.</div><br><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">
<br>
&gt;&gt; BUNDLE group MUST explicitly be included in each bundled<br>
&gt;&gt; &quot;m=3Da&amp;#128;&amp;#156; section (excluding any bundle-only=
 &quot;m=3D&quot; sections).<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; When an offerer or answerer includes SDP attributes in bundled &qu=
ot;m=3D&quot;<br>
&gt;&gt; sections within a BUNDLE group for which the offerer and answerer<=
br>
&gt;&gt; BUNDLE addresses:ports have been selected, IDENTICAL and TRANSPORT=
<br>
&gt; <br>
&gt; This is pretty opaque. It&#39;s not that the address:port pair have be=
en<br>
&gt; selected but rather that BUNDLE has been negotiated for that m=3D<br>
&gt; section (though of course the address:port being selected is a side<br=
>
&gt; effect of this).<br>
<br>
I suggest to remove &quot;for which the offerer and answerer BUNDLE address=
es:ports have been selected&quot;.<br></blockquote><div><br></div><div>O</d=
iv><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt;&gt; NOTE: If the offerer assigns unique addresses:ports to multiple<br=
>
&gt;&gt; bundled &quot;m=3D&quot; sections, the offerer needs to be prepare=
d to receive<br>
&gt;&gt; bundled media on each unique address:port, until it receives the<b=
r>
&gt;&gt; associated answer and finds out which address:port combination has=
<br>
&gt;&gt; been selected as the offerer BUNDLE-address.<br>
&gt; <br>
&gt; Why is this an &quot;If&quot;? There are only two choices: &quot;uniqu=
e&quot; and &quot;zero&quot;.<br>
&gt; Just put this graf up before the discussion of bundle-only and you can=
<br>
&gt; remove the conditional<br>
<br>
I suggest to move up the paragraph, and replace &quot;If&quot; with &quot;W=
hen&quot;.<br></blockquote><div><br></div><div>OK.</div><div> <br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
<br>
&gt;&gt; When an answerer generates an answer that contains a BUNDLE group,=
<br>
&gt;&gt; the following general SDP grouping framework restrictions, defined=
<br>
&gt;&gt; in [RFC5888], also apply to the BUNDLE group:<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; o=C2=A0 The answerer MUST NOT include a BUNDLE group in the answer=
,<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0unless<br>
&gt;<br>
&gt; Comma not needed here.<br>
<br>
Will fix.<br>
<br></blockquote><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&gt;Also, this negative phrasing is hard to follow. I would say &quot;MUST =
only<br>
&gt;... if&quot; here and below<br>
<br>
That would result in:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 o=C2=A0 The answerer MUST only include a BUNDLE group =
in the answer if<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the offerer requested the BUNDLE group to be ne=
gotiated in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 corresponding offer; and<br>
<br>
=C2=A0 =C2=A0 =C2=A0 o=C2=A0 The answerer MUST only include an &quot;m=3D&q=
uot; section within a BUNDLE<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Group if the offerer requested the &quot;m=3D&q=
uot; section to be within<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that BUNDLE group in the corresponding offer.<b=
r>
<br>
I think that is weird. If I do the change, I guess &quot;MUST&quot; should =
be<br>
replaced with e.g., &quot;can&quot;:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 o The answerer can only include a BUNDLE group in the =
answer if<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 the offerer requested the BUNDLE group to be ne=
gotiated in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 corresponding offer; and<br>
<br>
=C2=A0 =C2=A0 =C2=A0 o The answerer can only include an &quot;m=3D&quot; se=
ction within a BUNDLE<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Group if the offerer requested the &quot;m=3D&q=
uot; section to be within<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 that BUNDLE group in the corresponding offer.<b=
r></blockquote><div><br></div><div>OK.</div><div> <br></div><div><br></div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
&gt;&gt; If the answer contains a BUNDLE group, the answerer MUST:<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; o=C2=A0 Select an offerer BUNDLE address:port [Section 8.3.1]; and=
<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; o=C2=A0 Select an answerer BUNDLE address:port [Section 8.3.2].<br=
>
&gt;<br>
&gt; This isn&#39;t right, because each BUNDLE group has its own address:po=
rt,<br>
&gt; so instead &quot;For each BUNDLE group&quot; contained in the offer.<b=
r>
<br>
The procedures is for individual BUNDLE groups, as indicated in Section 8:<=
br>
<br>
=C2=A0&quot;SDP offers and answers can contain multiple BUNDLE groups.=C2=
=A0 The<br>
=C2=A0 procedures in this section apply independently to a given BUNDLE<br>
=C2=A0 group.&quot;&#39;=C2=A0</blockquote><div><br></div><div>I don&#39;t =
find this very clear.</div><div><br></div><div> <br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
&gt; More importantly, it&#39;s not the address:port that the answerer choo=
ses,<br>
&gt; but rather the m=3D section. I.e.,<br>
&gt;<br>
&gt; o Determine the first m=3D section in the BUNDLE group which will be<b=
r>
&gt;=C2=A0 =C2=A0BUNDLEd in the answer<br>
&gt; o Select an answerer BUNDLE address:port<br>
<br>
I don&#39;t understand what &quot;first m=3D section which will be BUNDLEd&=
quot; means. What is &quot;first&quot;?<br></blockquote><div><br></div><div=
>The one indicated by the bundle tag.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
---<br>
<br>
&gt;&gt; o=C2=A0 The answerer will not reject the &quot;m=3D&quot; section =
[Section 8.3.4];<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0and<br>
&gt;&gt;<br>
&gt;&gt; o=C2=A0 The &quot;m=3D&quot; section does not contain a zero port =
value.<br>
&gt;&gt;<br>
&gt;&gt; If all of the criteria above are fulfilled, the answerer MUST sele=
ct<br>
&gt; the suggested offerer BUNDLE address:port.<br>
&gt;<br>
&gt; Again, this isn&#39;t selecting the address:port but rather the m=3Dse=
ction<br>
<br>
Sure, but it picks the address:port of that selected m=3D section.<br></blo=
ckquote><div><br></div><div>No, it picks the m=3D section and then uses the=
 attached address:port.</div><div> <br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
---<br>
<br>
&gt;&gt; bundled &quot;m=3D&quot; section the answerer MUST assign a zero p=
ort value and<br>
&gt;&gt; include an SDP &#39;bundle-only&#39; attribute.<br>
&gt;&gt;<br>
&gt;&gt; The answerer MUST NOT assign an answerer BUNDLE address:port to an=
<br>
&gt;&gt; &quot;m=3D&quot; section that is not within the BUNDLE group, or t=
o an &quot;m=3D&quot;<br>
&gt;&gt; section that is within another BUNDLE group.<br>
&gt;<br>
&gt; This repeats text in S 8.3.<br>
<br>
What text do you think is repeated?<br></blockquote><div><br></div><div><br=
></div><div>8.3. already says you can&#39;t move between BUNDLE groups.</di=
v><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
---<br>
<br>
&gt;&gt; group in an answer, it MUST first check the following criteria:<br=
>
&gt;&gt;<br>
&gt;&gt; o=C2=A0 In the corresponding offer, an offerer BUNDLE address:port=
<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0(previously selected [Section 8.3.1] or newly s=
uggested<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0[Section 8.5.1]) has been assigned to the &quot=
;m=3D&quot; section by the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0offerer; or<br>
&gt;<br>
&gt; This text is baffling. As far as I can see, the first condition is<br>
&gt; &quot;don&#39;t pick it as the head m=3D section if you intend to move=
 it out&quot;.<br>
&gt; The second is some entirely different case. Can you rewrite it so it<b=
r>
&gt; makes sense.<br>
<br>
Actually, based on the current procedures, if the BUNDLE group exists,<br>
either criteria will always be fulfilled, so the only way for the answerer<=
br>
to move a bundled m- line out of a group is by sending an offer, as<br>
described later in the section.<br>
<br>
Also, the text contains &quot;includes a BUNDLE group&quot; terminology, bu=
t also<br>
covers cases where the BUNDLE group has not yet been created. So, I think<b=
r>
the procedures for the answerer needs to be split into:<br>
<br>
1. Creating initial answer, where the offerer asks for a BUNDLE group to<br=
>
be negotiated<br>
2. Creating answer to subsequent answer, where a BUNDLE group has<br>
previously been negotiated.<br>
<br>
I will try to come up with something.<br></blockquote><div><br></div><div>O=
K.</div><div><br></div><div> <br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
&gt;&gt; o=C2=A0 In the corresponding offer, an offerer BUNDLE address:port=
<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0(previously selected [Section 8.3.1] or newly s=
uggested<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0[Section 8.5.1]) has been assigned to the &quot=
;m=3D&quot; section by the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0offerer.<br>
&gt;&gt;<br>
&gt; If the criteria above is fulfilled, the answerer can not reject the<br=
>
&gt; <br>
&gt; &quot;criteria... are&quot;<br>
<br>
Someone said it should be &quot;is&quot;, but I am fine using &quot;are&quo=
t;, and can fix as suggested.<br></blockquote><div><br></div><div>OK, well,=
 &quot;criteria&quot; is the plural of &quot;criterion&quot;</div><div> <br=
></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&gt;&gt;=C2=A0 =C2=A08.4.=C2=A0 Offerer Processing of the SDP Answer<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 When an offerer receives an answer, if the ans=
wer contains a BUNDLE<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 group, the offerer MUST check that any bundled=
 &quot;m=3D&quot; section in the<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 answer was indicated as bundled in the corresp=
onding offer.=C2=A0 If<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 there is no mismatch, the offerer MUST use the=
 offerer BUNDLE<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 address:port,<br>
&gt;<br>
&gt; address:port, again. It&#39;s the m=3Dsection that&#39;s relevant.<br>
<br>
Yes, but it uses the address:port of the m=3D section.<br>
<br>
What do you suggest to say instead?<br></blockquote><div><br></div><div>&qu=
ot;MUST use the indicated m=3D section as the bundle &lt;whatever term we c=
hoose&gt;&quot;</div><div><br></div><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<br>
&gt;&gt; bundled &quot;m=3D&quot; section.<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; NOTE: As the answerer might reject one or more bundled &quot;m=3D&=
quot; sections,<br>
&gt;&gt; or move a bundled &quot;m=3D&quot; section out of a BUNDLE group, =
each bundled<br>
&gt;&gt; &quot;m=3D&quot; section in the offer might not be indicated as bu=
ndled in the<br>
&gt;&gt; answer.<br>
&gt; <br>
&gt; &quot;each&quot; -&gt; &quot;an given&quot;<br>
<br>
I will change as suggested (I assume you mean &quot;a given&quot;).<br>
<br>
---<br>
<br>
&gt;&gt; When the offerer generates a subsequent offer, the offerer<br>
&gt;&gt; BUNDLE-tag MUST represent the bundled &quot;m=3D&quot; section to =
which the offerer BUNDLE<br>
&gt;&gt; address:port (previously negotiated or newly suggested) has been a=
ssigned.<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; 8.5.1.=C2=A0 Suggesting a New Offerer BUNDLE Address:Port<br>
&gt; <br>
&gt; Again it would make more sense to describe this as suggesting a new m=
=3D section.<br>
<br>
It does not have to be a new &quot;m=3D&quot; section. The new address:port=
 can be assigned to an existing &quot;m=3D&quot; section.<br></blockquote><=
div><br></div><div>You&#39;re suggesting that a new m=3D section be the one=
 that things are bundled into.</div><div><br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">
<br>
---<br>
<br>
&gt;&gt; section out of a BUNDLE group.<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; 8.5.4.=C2=A0 Disabling a Media Description in a BUNDLE Group<br>
&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt; When an offerer generates an offer, in which it wants to disable a=
<br>
&gt;&gt; bundled &quot;m=3D&quot; section, the offerer:<br>
&gt; <br>
&gt; Are you sure disable -&gt; port 0, as opposed to &quot;inactive&quot;<=
br>
<br>
Yes. &quot;disable&quot; terminology is also used in RFC 3264.<br></blockqu=
ote><div><br></div><div>All right.</div><div><br></div>-Ekr</div><div class=
=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<br>
Regards,<br>
<br>
Christer<br>
</blockquote></div><br></div></div>

--0000000000002b6cbc056a10fc19--


From nobody Tue Apr 17 13:16:13 2018
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 81D0F12D9FE for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 13:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 DhjO2gsTjKai for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 13:16:10 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 2EB7112DA00 for <mmusic@ietf.org>; Tue, 17 Apr 2018 13:16:08 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id 126-v6so19213456oig.0 for <mmusic@ietf.org>; Tue, 17 Apr 2018 13:16:08 -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=bs82y7jcCKHaKmx01RNAwCoiAIo+VD7SI97TZXw4Yv8=; b=mT2nPK39jJyjxztLXjDPoMCN1Abmk10Qajpm5wwGsKWSpj/e+P5J8CKv9U99mLupTP zQyyuE4lVYWHkoCXeM4n+xK+ZHl184j+0g3TCCvwclRyPzXzkWkMMJ63hDUDWlgXGoD5 K70mpCyVXYHA6Ro1B/DxITnHtyWGUIMQnq9k+vNZWEUVjloT2/uhu1NfiMMCCV2GwAat tFcGECDDnDLVlB7lGZ27bn8BlBzQJCwmF4xIXV5REcVi2BDnn+ns4nhlHZxcuwberl2B 2vbSCjOcFvr22E3q8gJpHUQKZz2tBenAvspP0ygtnrz8U71NPzhsITuD5gcUyEMN3gJc +yeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bs82y7jcCKHaKmx01RNAwCoiAIo+VD7SI97TZXw4Yv8=; b=B5E8nrbfDPdXb68os4+9q9u2TkxX0ii/b0Ek5eRC4bDkYe0uQ6Ih5prbLTi+pkMuin sfLveylyhYk2x5qwDOFlRbcp+6FxAfKTtgJf7/y4E9SZjq/nrfJWVweIahin2ijfqk3o UKCxbSitMT7cxKJ4b2dyly89ggLKWvvIpQSa2lKtfiyFxzGb10FQECNhsAUqDVEySvj3 xpm4YxM8y+XFrYvdOUuKr0YHzjUVEZ2p109y5+Caj0oSyDWr/ZPfpaiDseCW0ar4UA0v AiEpcxicB3ty3XeGYRPIeglHOJT9no8iqHNLxpAiu9sCIVAB8OpxthdQx35JDhnMJhLl FC0A==
X-Gm-Message-State: ALQs6tBtkXpv1LaSEK0fGpPbQ/xsfv7hsvd1a5v5P58NbtSnSt95+znb aEsDkOpPEIZH4ThSAwfG3AWOa14Jlmdue0Kj194i1bBe
X-Google-Smtp-Source: AIpwx4/5Zu9WXUhmFxrqCXJ7tJniTKFmR5KoKP+lCGVQN3r5eRV+WwwaYTDGBpqFgPN8N4MaGaYXDmxmjRbTk++skPc=
X-Received: by 2002:aca:c744:: with SMTP id x65-v6mr2005790oif.43.1523996167534;  Tue, 17 Apr 2018 13:16:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 13:15:27 -0700 (PDT)
In-Reply-To: <D6FBD6CA.2E401%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 13:15:27 -0700
Message-ID: <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  "mmusic@ietf.org" <mmusic@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000034acd3056a11022e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EnR_UEoyfV27OkmR6ypnuNK4msw>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 20:16:11 -0000

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

On Tue, Apr 17, 2018 at 6:57 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
> =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Nits
> =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> General:
>
> >>> I agree with EKR that the use of "address:port" is cumbersome. For th=
e
> >>>places
> >>> where this is not a stand-in for the term "'m=3D' section", I would
> >>>suggest that
> >>> the well-known term "3-tuple" would serve the purpose in a much more
> >>>readable
> >>> way.
> >>
> >> I personally have nothing against '3-tuple', =C5=92transport' (suggest=
ed by
> >> Taylor at some point), etc.
> >>
> >> The problem is that whenever I change the terminology someone later
> >>wants
> >> something else, and then I again have to change it.
> >
> > Well, we're at IESG review now, so this is the last round.
> >
> > Who, specifically, is in favor of the current terminology?
>
> I see it more as terminology that people in the WG could live with.
>

This doesn't answer my question. Who, specifically, thinks that this
terminology
of focusing on the address:port and not the m=3D section is good?


> Having said that, if we can change it with a search/replace operation I a=
m
> happy to discuss it. I THINK we could do that e.g., with =C2=B3transport=
=C2=B2 or
> =C2=B33-tuple=C2=B2.
>
> But I don=C2=B9t want to make yet another re-write of the document just t=
o once
> again change the terminology.
>

This document is going to be used by a lot of people. It's important that
it be
clear.


-Ekr



> Regards,
>
> Christer
>
>
>
>
>

--00000000000034acd3056a11022e
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 Tue, Apr 17, 2018 at 6:57 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">Hi,<br>
<br>
<br>
=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<wbr>=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<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
Nits<br>
=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<wbr>=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<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
<span class=3D""><br>
General:<br>
<br>
&gt;&gt;&gt; I agree with EKR that the use of &quot;address:port&quot; is c=
umbersome. For the<br>
&gt;&gt;&gt;places<br>
&gt;&gt;&gt; where this is not a stand-in for the term &quot;&#39;m=3D&#39;=
 section&quot;, I would<br>
&gt;&gt;&gt;suggest that<br>
&gt;&gt;&gt; the well-known term &quot;3-tuple&quot; would serve the purpos=
e in a much more<br>
&gt;&gt;&gt;readable<br>
&gt;&gt;&gt; way.<br>
&gt;&gt;<br>
</span>&gt;&gt; I personally have nothing against &#39;3-tuple&#39;, =C5=92=
transport&#39; (suggested by<br>
<span class=3D"">&gt;&gt; Taylor at some point), etc.<br>
&gt;&gt;<br>
&gt;&gt; The problem is that whenever I change the terminology someone late=
r<br>
&gt;&gt;wants<br>
&gt;&gt; something else, and then I again have to change it.<br>
&gt;<br>
&gt; Well, we&#39;re at IESG review now, so this is the last round.<br>
&gt;<br>
&gt; Who, specifically, is in favor of the current terminology?<br>
<br>
</span>I see it more as terminology that people in the WG could live with.<=
br></blockquote><div><br></div><div>This doesn&#39;t answer my question. Wh=
o, specifically, thinks that this terminology</div><div>of focusing on the =
address:port and not the m=3D section is good?</div><div><br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
<br>
Having said that, if we can change it with a search/replace operation I am<=
br>
happy to discuss it. I THINK we could do that e.g., with =C2=B3transport=C2=
=B2 or<br>
=C2=B33-tuple=C2=B2. <br>
<br>
But I don=C2=B9t want to make yet another re-write of the document just to =
once<br>
again change the terminology.<br></blockquote><div><br></div><div>This docu=
ment is going to be used by a lot of people. It&#39;s important that it be<=
/div><div>clear.</div><div><br></div><div><br></div><div>-Ekr</div><div><br=
></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>

--00000000000034acd3056a11022e--


From nobody Tue Apr 17 15:24:23 2018
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 1E76F124B0A for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 15:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 aT5L80eBLXwp for <mmusic@ietfa.amsl.com>; Tue, 17 Apr 2018 15:24:15 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::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 1FB94126DED for <mmusic@ietf.org>; Tue, 17 Apr 2018 15:24:12 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id f69-v6so2067887otf.2 for <mmusic@ietf.org>; Tue, 17 Apr 2018 15:24:12 -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=rL+ftrpVe/C7CkT3VYxs+6M4jBN2XdzEAi8YKkXqt4Q=; b=LKLRYJkliKwJsLjieAjACgf7OQtk2rznG9buhFvDZ/6ZFUB15Y87CI8YbZt6wqx2UR NgkSmb5M0mXEaNaKPsr7T0eaYoHzuTH2SFCOsVtS8EG2+feDN6RNM/9bJaFO0yD0v1I6 hitdXsrRz298MTevSl+r/kUxEbubEBeKrrGGY2XziCrf76NnXDegRG8h83NoPh6kls+o wDdGaKXq7znoWPDhHK7LHcistWVKZ0wEFwfKLYZ5lZCattTpi24100usJ9qBu7oryob5 r8uvbRPQydtqDZlJ6EVHi/ElFlHTN/i6SwItDrnHP36HHR9eQSxR/LsNpFR/wMoUVJ4N K2HQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rL+ftrpVe/C7CkT3VYxs+6M4jBN2XdzEAi8YKkXqt4Q=; b=eA5qmW9HhR7JIE0k/DnuG3RF1rxAuDMVFD2QP4BxHTyOWs/SDMGzTeX+pP8TocPzII zcMM07kHt0ue5wsWGMIOIc4t9ztO29ygjKCGEzOi17SlxY7e1oTdA/PGk9nsIiy5UtFN PwW+ZZ10tOCIA/O13t9966tiyN+hilsoycDTT4VF05NgHQ+S1ONnd5CCL5cbzypAM431 MOmsJI+BNodqh65QSley2CQalwcCCVVb+e95rbv9Mb4f9ye0IViGVFYBIyx+dpWdl/3A 8u2s9d3Vw+QkzWEp4hSH6+z+bQQTjdWt31BYNRwLAYhIaQjrEaPEInpiNIVMlAzsnanm Qn8A==
X-Gm-Message-State: ALQs6tBMuPtcJ+EuANUly8Li2gDxszXQuLqh6J0p4Ucak34e9z5YO3T4 UyW+y/Gd+JZ09wmSd5WVM1yP/Btk1VEr7xjIB6MHAg==
X-Google-Smtp-Source: AIpwx4+H7kpv/xPdrGj5DDknF1WBnePI7108N212ZVxi095cA+opu9avHLdx9//h4f/44WsBP5gnVo1a+1/wvhQnYjo=
X-Received: by 2002:a9d:4c16:: with SMTP id l22-v6mr2569270otf.176.1524003851253;  Tue, 17 Apr 2018 15:24:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Tue, 17 Apr 2018 15:23:30 -0700 (PDT)
In-Reply-To: <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 17 Apr 2018 15:23:30 -0700
Message-ID: <CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000030cce4056a12ccf7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-INBUCTVqVP4EBpzuEfZJ050T3w>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 17 Apr 2018 22:24:17 -0000

--00000000000030cce4056a12ccf7
Content-Type: text/plain; charset="UTF-8"

Hi folks,

This is an attempt to sharpen my point about talking about the
"BUNDLE address:port", when what we really mean is "use the
parameters from the "m=" section". Here's an example where this
creates a real problem. S 8.4 says:

   When an offerer receives an answer, if the answer contains a BUNDLE
   group, the offerer MUST check that any bundled "m=" section in the
   answer was indicated as bundled in the corresponding offer.  If there
   is no mismatch, the offerer MUST use the offerer BUNDLE address:port,
   selected by the answerer [Section 8.3.1], as the address for each
   bundled "m=" section.

Now consider the case where I am doing trickle ICE. The offer will
contain:

   a=group:BUNDLE foo bar
   m=audio 9 RTP/AVP 97
   c=IN IP4 0.0.0.0
   a=rtpmap:97 iLBC/8000
   a=mid:foo

   m=video 9 RTP/AVP 98
   c=IN IP4 0.0.0.0
   a=rtpmap:98 H261/90000
   a=mid:bar

Now, if the answer contains:

   a=group:BUNDLE foo bar

Then the semantics are that we are supposed to use the parameters from
the m=audio line as the parameters for the bundle group. Specifically,
we are supposed to use the ICE candidates that belong to that m=audio
line. But there's no way to get that from this text. Ordinarily, if
each m=section contained a distinct address:port, then you might say
there was an implicit map from address:port to m= section parameters,
but in this case because all the address:port values are the same,
that's not possible, and so this paragraph just doesn't work.  The
right fix is to stop talking about the address:port and instead talk
about the m= section.

   When an offerer receives an answer, if the answer contains a BUNDLE
   group, the offerer MUST check that any bundled "m=" section in the
   answer was indicated as bundled in the corresponding offer.  If there
   is no mismatch, the offerer MUST use the relevant parameters
   [specific text from Suhas's draft needed here] from the
   "m=" section indicated by the BUNDLE tag [again, it would be helpful
   to have a better name here] for each "m=" section which is bundled
   with it.

There are other places where this creates confusion, but this is
a nice clear one.

-Ekr





On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> >>>>>> When an offerer generates an offer, in which it wants to add a new
>> >>>>>> bundled "m=" section, the offerer MUST:
>> >>>>>>
>> >>>>>>      o  Assign the offerer BUNDLE address:port (previously selected
>> >>>>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the
>> added
>> >>>>>>         "m=" section; or
>> >>>>>
>> >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>> >>>>> address:port, because if the peer rejects BUNDLE but accepts the m=
>> >>>>> section then it's broken.
>> >>>>
>> >>>> Note that in this case the usage of BUNDLE has already been
>> negotiated.
>> >>>> Then, if the answerer does not accept the new m= section into the
>> BUNDLE
>> >>>> group, it needs to send an offer where it removes it, as described in
>> >>>> section 8.3.3.
>> >>>
>> >>> Well, both of these options correspond to insisting that the m=
>> section
>> >>> be in the BUNDLE group. If I just want to suggest it, I would have to
>> provide
>> >>> a fresh unique address. Or are you saying that's impossible.
>> >>>
>> >> Yes.
>> >>
>> >> Previously, when the offerer wanted to add a new m- section to a BUNDLE
>> >> group, it had to choice of either assigning a unique address or a
>> >> previously negotiated bundle address.
>> >>
>> >> That option was removed as part of task (triggered by WGLC comments
>> etc)
>> >
>> > That seems like a pretty material change. Was there a call for
>> consensus on that?
>>
>> No. But, the suggested changes were indicated on the list, there were
>> pull requests etc, so people were informed about it and had a chance to
>> comment/object.
>>
>
> Hmm... Ben, do you think these were properly surfaced to the WG?
>
> -Ekr
>
>
> > trying to simplifying the procedures. Currently the offerer must either
>> > assign a bundle address (previously negotiated or new suggested) or
>> > indicate it as bundle-only.
>> >
>> > At minimum this needs to be clearly stated
>>
>> I need to modify the section, so I will add text about it.
>>
>> Regards,
>>
>> Christer
>>
>>
>

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

<div dir=3D"ltr">Hi folks,<br><br>This is an attempt to sharpen my point ab=
out talking about the<br>&quot;BUNDLE address:port&quot;, when what we real=
ly mean is &quot;use the<br>parameters from the &quot;m=3D&quot; section&qu=
ot;. Here&#39;s an example where this<br>creates a real problem. S 8.4 says=
:<br><br>=C2=A0=C2=A0 When an offerer receives an answer, if the answer con=
tains a BUNDLE<br>=C2=A0=C2=A0 group, the offerer MUST check that any bundl=
ed &quot;m=3D&quot; section in the<br>=C2=A0=C2=A0 answer was indicated as =
bundled in the corresponding offer.=C2=A0 If there<br>=C2=A0=C2=A0 is no mi=
smatch, the offerer MUST use the offerer BUNDLE address:port,<br>=C2=A0=C2=
=A0 selected by the answerer [Section 8.3.1], as the address for each<br>=
=C2=A0=C2=A0 bundled &quot;m=3D&quot; section.<br><br>Now consider the case=
 where I am doing trickle ICE. The offer will<br>contain:<br><br>=C2=A0=C2=
=A0 a=3Dgroup:BUNDLE foo bar<br>=C2=A0=C2=A0 m=3Daudio 9 RTP/AVP 97<br>=C2=
=A0=C2=A0 c=3DIN IP4 0.0.0.0=C2=A0=C2=A0 <br>=C2=A0=C2=A0 a=3Drtpmap:97 iLB=
C/8000<br>=C2=A0=C2=A0 a=3Dmid:foo<br>=C2=A0=C2=A0 <br>=C2=A0=C2=A0 m=3Dvid=
eo 9 RTP/AVP 98<br>=C2=A0=C2=A0 c=3DIN IP4 0.0.0.0=C2=A0=C2=A0 <br>=C2=A0=
=C2=A0 a=3Drtpmap:98 H261/90000<br>=C2=A0=C2=A0 a=3Dmid:bar<br><br>Now, if =
the answer contains:<br><br>=C2=A0=C2=A0 a=3Dgroup:BUNDLE foo bar<br><br>Th=
en the semantics are that we are supposed to use the parameters from<br>the=
 m=3Daudio line as the parameters for the bundle group. Specifically,<br>we=
 are supposed to use the ICE candidates that belong to that m=3Daudio<br>li=
ne. But there&#39;s no way to get that from this text. Ordinarily, if<br>ea=
ch m=3Dsection contained a distinct address:port, then you might say<br>the=
re was an implicit map from address:port to m=3D section parameters,<br>but=
 in this case because all the address:port values are the same,<br>that&#39=
;s not possible, and so this paragraph just doesn&#39;t work.=C2=A0 The<br>=
right fix is to stop talking about the address:port and instead talk<br>abo=
ut the m=3D section.<br><br>=C2=A0=C2=A0 When an offerer receives an answer=
, if the answer contains a BUNDLE<br>=C2=A0=C2=A0 group, the offerer MUST c=
heck that any bundled &quot;m=3D&quot; section in the<br>=C2=A0=C2=A0 answe=
r was indicated as bundled in the corresponding offer.=C2=A0 If there<br>=
=C2=A0=C2=A0 is no mismatch, the offerer MUST use the relevant parameters<b=
r>=C2=A0=C2=A0 [specific text from Suhas&#39;s draft needed here] from the<=
br>=C2=A0=C2=A0 &quot;m=3D&quot; section indicated by the BUNDLE tag [again=
, it would be helpful<br>=C2=A0=C2=A0 to have a better name here] for each =
&quot;m=3D&quot; section which is bundled<br>=C2=A0=C2=A0 with it.<br><br>T=
here are other places where this creates confusion, but this is<br>a nice c=
lear one.<br><br>-Ekr<br><br><br><br><br></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote">On Tue, Apr 17, 2018 at 11:18 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"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><d=
iv><div class=3D"h5">On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" targe=
t=3D"_blank">christer.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;padding-left:1ex"><div class=3D"m_3202404282620514461HOEnZb"><d=
iv class=3D"m_3202404282620514461h5">Hi,<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
DISCUSS:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0When an offerer generates an offer, in which =
it wants to add a new<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0bundled &quot;m=3D&quot; section, the offerer=
 MUST:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 Assign the offerer BUN=
DLE address:port (previously selected<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[Section 8.3.1] o=
r newly suggested [Section 8.5.1]) to the added<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;m=3D&quot; =
section; or<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn&#39;t sound right. You can&#39;t=
 use the existing<br>
&gt;&gt;&gt;&gt;&gt; address:port, because if the peer rejects BUNDLE but a=
ccepts the m=3D<br>
&gt;&gt;&gt;&gt;&gt; section then it&#39;s broken.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that in this case the usage of BUNDLE has already bee=
n negotiated.<br>
&gt;&gt;&gt;&gt; Then, if the answerer does not accept the new m=3D section=
 into the BUNDLE<br>
&gt;&gt;&gt;&gt; group, it needs to send an offer where it removes it, as d=
escribed in<br>
&gt;&gt;&gt;&gt; section 8.3.3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Well, both of these options correspond to insisting that the m=
=3D section<br>
&gt;&gt;&gt; be in the BUNDLE group. If I just want to suggest it, I would =
have to provide<br>
&gt;&gt;&gt; a fresh unique address. Or are you saying that&#39;s impossibl=
e.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Yes.<br>
&gt;&gt;<br>
&gt;&gt; Previously, when the offerer wanted to add a new m- section to a B=
UNDLE<br>
&gt;&gt; group, it had to choice of either assigning a unique address or a<=
br>
&gt;&gt; previously negotiated bundle address.<br>
&gt;&gt;<br>
&gt;&gt; That option was removed as part of task (triggered by WGLC comment=
s etc)<br>
&gt;<br>
&gt; That seems like a pretty material change. Was there a call for consens=
us on that?<br>
<br>
</div></div>No. But, the suggested changes were indicated on the list, ther=
e were pull requests etc, so people were informed about it and had a chance=
 to comment/object.<br></blockquote><div><br></div></div></div><div>Hmm... =
Ben, do you think these were properly surfaced to the WG?</div><div><br></d=
iv><div>-Ekr</div><span class=3D""><div><br></div><div><br><span></span><sp=
an></span></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span>
&gt; trying to simplifying the procedures. Currently the offerer must eithe=
r<br>
&gt; assign a bundle address (previously negotiated or new suggested) or<br=
>
&gt; indicate it as bundle-only.<br>
&gt;<br>
&gt; At minimum this needs to be clearly stated<br>
<br>
</span>I need to modify the section, so I will add text about it.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote></span></div><br></div></div>
</blockquote></div><br></div>

--00000000000030cce4056a12ccf7--


From nobody Wed Apr 18 00:23:20 2018
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 44C0412D868 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 00:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vyoBt9OM-maj for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 00:23:17 -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 3091B12D810 for <mmusic@ietf.org>; Wed, 18 Apr 2018 00:23:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524036193; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=LdTc41MeEvBMM9lY9ar7N1noqvDYxP4ovHF6UXS0OCU=; b=Zx1HiCjskyoWPeyFzOTf5YDWMVDA8NqpXc3ElAujNyEsNEAvUTUlxxv5cT7dHYcw dVAGUNl7LW2KE/H+t9ubWTLBYfpo2TL/2aAU6Ka9dwlDjdkjWcv0eRV6ZdrpiiEC O2pNEwAAegqKQdcKh+di8t3gcQuq6EvkypA2RuDfVAI=;
X-AuditID: c1b4fb2d-bf68e9c000003563-fe-5ad6f261bd70
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id C1.85.13667.162F6DA5; Wed, 18 Apr 2018 09:23:13 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0382.000; Wed, 18 Apr 2018 09:23:10 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseA=
Date: Wed, 18 Apr 2018 07:23:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com>
In-Reply-To: <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@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.169]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDIsWRmVeSWpSXmKPExsUyM2K7pW7ip2tRBms3G1rs+buI3WL6rHds Fiten2O3eH9B12LGn4nMFud3rmeymLr8MYsDu8eU3xtZPZYs+cnkMWvnExaPyY/bmANYorhs UlJzMstSi/TtErgynq44yFrwTKRi0rT/TA2MC0S6GDk5JARMJI48fsUGYgsJHGGU+D/doouR C8hezCjRdKiDpYuRg4NNwEKi+582SI2IgILErz8nWEBqmAXWM0ksOn2ZFSQhLJAuMWfVMmaQ ehGBDIn7DzIh6v0k1na1MoHYLAKqEvfnbwEr5xXwlVh39z8zxK79TBKNzy+wgCQ4BQIlHl87 ANbAKCAm8f3UGjCbWUBc4taT+UwQRwtILNlznhnCFpV4+fgfK4StJHGyezPYzcwCmhLrd+lD tCpKTOl+yA6xV1Di5MwnLBMYRWchmToLoWMWko5ZSDoWMLKsYhQtTi0uzk03MtZLLcpMLi7O z9PLSy3ZxAiMs4NbfuvuYFz92vEQowAHoxIPr/29a1FCrIllxZW5hxglOJiVRHh3Pr4SJcSb klhZlVqUH19UmpNafIhRmoNFSZxXb9WeKCGB9MSS1OzU1ILUIpgsEwenVAMjd9zGGqnzFZt8 LmXEiV1elqltv3wCh+F+5hZWW9W0t2sl17f99Xq2snSbXl+aZu18G89VC7WabzklF13IjPox ySr+UN9dFaOzxzZZpLTpV/I6858Qm7H+mOe3NY/PMbm9i+nPil2w/3Da3xDnqTGCButyJWIn VCdWrExesl2r7CXPhWr1361KLMUZiYZazEXFiQAEfL7GrwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mQhTcMWQ_H6G3eqTu_xUV9krzRQ>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 07:23:18 -0000

DQpIaSwNCg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpOaXRzDQo9PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCg0K
R2VuZXJhbDoNCg0KPj4+PiBJIGFncmVlIHdpdGggRUtSIHRoYXQgdGhlIHVzZSBvZiAiYWRkcmVz
czpwb3J0IiBpcyBjdW1iZXJzb21lLiBGb3IgdGhlDQo+Pj4+IHBsYWNlcyB3aGVyZSB0aGlzIGlz
IG5vdCBhIHN0YW5kLWluIGZvciB0aGUgdGVybSAiJ209JyBzZWN0aW9uIiwgSSB3b3VsZA0KPj4+
PiBzdWdnZXN0IHRoYXQgdGhlIHdlbGwta25vd24gdGVybSAiMy10dXBsZSIgd291bGQgc2VydmUg
dGhlIHB1cnBvc2UgaW4gYSBtdWNoIG1vcmUNCj4+Pj4gcmVhZGFibGUgd2F5Lg0KPj4+DQo+Pj4g
SSBwZXJzb25hbGx5IGhhdmUgbm90aGluZyBhZ2FpbnN0ICczLXR1cGxlJywgxZJ0cmFuc3BvcnQn
IChzdWdnZXN0ZWQgYnkNCj4+PiBUYXlsb3IgYXQgc29tZSBwb2ludCksIGV0Yy4NCj4+Pg0KPj4+
IFRoZSBwcm9ibGVtIGlzIHRoYXQgd2hlbmV2ZXIgSSBjaGFuZ2UgdGhlIHRlcm1pbm9sb2d5IHNv
bWVvbmUgbGF0ZXINCj4+PiB3YW50cyBzb21ldGhpbmcgZWxzZSwgYW5kIHRoZW4gSSBhZ2FpbiBo
YXZlIHRvIGNoYW5nZSBpdC4NCj4+DQo+PiBXZWxsLCB3ZSdyZSBhdCBJRVNHIHJldmlldyBub3cs
IHNvIHRoaXMgaXMgdGhlIGxhc3Qgcm91bmQuDQo+Pg0KPj4gV2hvLCBzcGVjaWZpY2FsbHksIGlz
IGluIGZhdm9yIG9mIHRoZSBjdXJyZW50IHRlcm1pbm9sb2d5Pw0KPg0KPiBJIHNlZSBpdCBtb3Jl
IGFzIHRlcm1pbm9sb2d5IHRoYXQgcGVvcGxlIGluIHRoZSBXRyBjb3VsZCBsaXZlIHdpdGguDQo+
DQo+IFRoaXMgZG9lc24ndCBhbnN3ZXIgbXkgcXVlc3Rpb24uIFdobywgc3BlY2lmaWNhbGx5LCB0
aGlua3MgdGhhdCB0aGlzIHRlcm1pbm9sb2d5DQo+IG9mIGZvY3VzaW5nIG9uIHRoZSBhZGRyZXNz
OnBvcnQgYW5kIG5vdCB0aGUgbT0gc2VjdGlvbiBpcyBnb29kPw0KDQpDb25zaWRlcmluZyB0aGF0
IHRoZSBmb2N1cyBoYXMgYmVlbiBvbiB0aGUgYWRkcmVzcyBhbmQgcG9ydCBzaW5jZSBkYXkgb25l
LCBmb3IgNyB5ZWFycywgSSB0aGluayBpdCBpcyBnb29kLiBBZnRlciBhbGwsIHdoaWxlIHRoZXJl
IGlzIG1vcmUgdG8gaXQgdGhhbiB0aGUgYWRkcmVzczpwb3J0LCB0aGUgbWFpbiByZWFzb24gZm9y
IEJVTkRMRSBpcyB0byBiZSBhYmxlIHRvIG11bHRpcGxleCBpbiBhIHNpbmdsZSBhZGRyZXNzOnBv
cnQuDQoNCk5vdywgd2UgSEFWRSBkaXNjdXNzZWQgY2hhbmdpbmcgImFkZHJlc3M6cG9ydCIgdG8g
InRyYW5zcG9ydCIsIGJ1dCBpdCB3b3VsZCBzdGlsbCBub3QgYmUgYWJvdXQgdGhlIG09IHNlY3Rp
b24uDQoNCj4+IEhhdmluZyBzYWlkIHRoYXQsIGlmIHdlIGNhbiBjaGFuZ2UgaXQgd2l0aCBhIHNl
YXJjaC9yZXBsYWNlIG9wZXJhdGlvbiBJIGFtDQo+PiBoYXBweSB0byBkaXNjdXNzIGl0LiBJIFRI
SU5LIHdlIGNvdWxkIGRvIHRoYXQgZS5nLiwgd2l0aCAidHJhbnNwb3J0IiBvcg0KPj4gIjMtdHVw
bGUiLiANCj4+DQo+PiBCdXQgSSBkb27CuXQgd2FudCB0byBtYWtlIHlldCBhbm90aGVyIHJlLXdy
aXRlIG9mIHRoZSBkb2N1bWVudCBqdXN0IHRvIG9uY2UNCj4+IGFnYWluIGNoYW5nZSB0aGUgdGVy
bWlub2xvZ3kuDQo+DQo+IFRoaXMgZG9jdW1lbnQgaXMgZ29pbmcgdG8gYmUgdXNlZCBieSBhIGxv
dCBvZiBwZW9wbGUuIEl0J3MgaW1wb3J0YW50IHRoYXQgaXQgYmUNCj4gY2xlYXIuDQoNCkkgZnVs
bHkgYWdyZWUuIEJ1dCwgSSBhbSBub3Qgc3VyZSB0aGF0IGVuZGxlc3MgcmUtd3JpdGluZ3MgdGhl
IGRvY3VtZW50IGlzIGdvaW5nIHRvIGFjaGlldmUgdGhhdC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0
ZXINCg0K


From nobody Wed Apr 18 02:28:56 2018
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 4D6B3126BFD for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 02:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLruz2rQtN21 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 02:28: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 F12EC12D874 for <mmusic@ietf.org>; Wed, 18 Apr 2018 02:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524043727; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ZJKwlS0PnmGC1XD9sumdGvcjSO9i7DbuoO7uvCVNcnA=; b=ODJRLozrqwD4yJ/CUxOUIT4a/8r18AFCEQckIrgyfAO5tPdm63S69evfEREmAWd5 K87Rc8K5cfyevvpjC7O6oklPxY2u3QQ5DEDvvQwASVGYj23btJsiwlKlKNByHUGh b/DhvUCJz/FxR5yfP/qh8bqPBZLXL8lBSz/p/Z0qdUA=;
X-AuditID: c1b4fb3a-eae319c00000795a-c2-5ad70fcf581c
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6A.1C.31066.FCF07DA5; Wed, 18 Apr 2018 11:28:47 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0382.000; Wed, 18 Apr 2018 11:28:46 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
Thread-Index: AQHT1lZf0qxFmZgCwkeSofFpx7VVFKQFQviAgADjodA=
Date: Wed, 18 Apr 2018 09:28:46 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com>
In-Reply-To: <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@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.169]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7hO55/utRBn2rlSymz3rHZrHi9Tl2 i/cXdC1m/JnIbHF+53omi6nLH7M4sHlM+b2R1WPJkp9MHpMftzEHMEdx2aSk5mSWpRbp2yVw ZTx+OYW9oCO0YuPF4+wNjB+Cuhg5OSQETCQ6bm1m62Lk4hASOMIocWb3SyYIZzGjxKXmyUAZ Dg42AQuJ7n/aIA0iAgoSv/6cYAGpYRaYwCRx9e9qVpCEsECtxKwfyxkhiuokFiw+zARhW0ns mTMZLM4ioCrxY2YXO4jNK+ArsX/rdRYQW0hgCqPE4xl2IDanQKDElkc3wGYyCohJfD+1BmwO s4C4xK0n85kgrhaQWLLnPDOELSrx8vE/VghbSeJk92YWkJuZBTQl1u/Sh2hVlJjS/RBqraDE yZlPWCYwis5CMnUWQscsJB2zkHQsYGRZxShanFpcnJtuZKSXWpSZXFycn6eXl1qyiREYVQe3 /LbawXjwueMhRgEORiUeXktgtAmxJpYVV+YeYpTgYFYS4d35+EqUEG9KYmVValF+fFFpTmrx IUZpDhYlcV6nNIsoIYH0xJLU7NTUgtQimCwTB6dUA2OW940M2ZoXpfydOjGTVzXPZpzFmid4 SjvGa8/ls9KfQvyYf9m+9N+5OowzYcMX7+Nufpn31luxPj7Q5PKIt8qyVCTLdZKX6tZ/TJyz DnFxvVT3DL+SFvnwgsc6zm3PDp+XvXZJ59EUT9/Qc7WXZ93ydpuyekVRy5MV0xYr+jvuk2ud e/upnJgSS3FGoqEWc1FxIgB3HgE+pgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/1FhpMsEphj3-vwmRM6aAVtkamNA>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 09:28:54 -0000

SGksDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNPTU1FTlQ6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQrCoA0KPj4+PiB0
byBuZWdvdGlhdGUgd2hpY2ggIm09IiBzZWN0aW9ucyB3aWxsIGJlY29tZSBwYXJ0IG9mIGEgQlVO
RExFIGdyb3VwLg0KPj4+PiBXaXRoaW4gYSBCVU5ETEUgZ3JvdXAsIGVhY2ggIm09IiBzZWN0aW9u
IHdpbGwgdXNlIGEgQlVORExFDQo+Pj4+IHRyYW5zcG9ydCBmb3Igc2VuZGluZyBhbmQgcmVjZWl2
aW5nIGJ1bmRsZWQgbWVkaWEuDQo+Pj4+wqAgwqANCj4+Pj4gV2l0aGluIGEgQlVORExFIGdyb3Vw
LCBlYWNoIGVuZHBvaW50IHVzZXMgYSBzaW5nbGUgYWRkcmVzczpwb3J0DQo+Pj4+IGNvbWJpbmF0
aW9uIGZvciBzZW5kaW5nIGFuZCByZWNlaXZpbmcgYnVuZGxlZCBtZWRpYS7CoCBUaGUNCj4+PiAN
Cj4+PiBOaXQ6ICJwYWlyIj8NCj4+DQo+PiAiY29tYmluYXRpb24iIGhhcyBiZWVuIHVzZWQgaW4g
dGhlIGRyYWZ0IGZvciBhIGxvbmcgdGltZSwgYW5kIGlzIGFsc28gdXNlZA0KPj4gaW4gb3RoZXIg
cGxhY2VzLg0KPg0KPiBJJ20gcHJlcGFyZWQgdG8gYmVsaWV2ZSBib3RoIG9mIHRoZXNlIHN0YXRl
bWVudHMsIGJ1dCBpbiBteSBleHBlcmllbmNlDQo+ICJwYWlyIiBpcyBmYXIgbW9yZSBjb21tb24u
DQoNCk9rLiBTbywgaWYgd2UgZW5kIHVwIHVzaW5nICJhZGRyZXNzOnBvcnQiIEkgd2lsbCBjaGFu
Z2UgImNvbWJpbmF0aW9uIiB0byAicGFpciIuDQoNCi0tLQ0KDQo+Pj4+IG/CoCBCdW5kbGVkIG1l
ZGlhOiBBbGwgbWVkaWEgYXNzb2NpYXRlZCB3aXRoIGEgZ2l2ZW4gQlVORExFIGdyb3VwLg0KPj4+
PsKgIMKgDQo+Pj4+IG/CoCBJbml0aWFsIG9mZmVyOiBUaGUgZmlyc3Qgb2ZmZXIsIHdpdGhpbiBh
biBTRFAgc2Vzc2lvbiAoZS5nLiBhDQo+Pj4+wqAgwqAgwqBTSVAgZGlhbG9nIHdoZW4gdGhlIFNl
c3Npb24gSW5pdGlhdGlvbiBQcm90b2NvbCAoU0lQKSBbUkZDMzI2MV0gaXMNCj4+Pj7CoCDCoCDC
oHVzZWQgdG8gY2FycnkgU0RQKSwgaW4gd2hpY2ggdGhlIG9mZmVyZXIgaW5kaWNhdGVzIHRoYXQg
aXQgd2FudHMNCj4+Pj7CoCDCoCDCoHRvIGNyZWF0ZSBhIGdpdmVuIEJVTkRMRSBncm91cC4NCj4+
PiANCj4+PiBUaGlzIGlzIGEgdmVyeSBpZGlvc3luY3JhdGljIGRlZmluaXRpb24sIGJlY2F1c2Ug
aXQncyAqbm90KiB0aGUgZmlyc3QNCj4+PiBvZmZlciBpbiB0aGUgc2Vzc2lvbiwgYnV0IHRoZSBv
bmUgd2hlcmUgdGhlIEJVTkRMRSBncm91cCBpcw0KPj4+IGludHJvZHVjZWQuIEdpdmVuIHRoYXQg
MzI2NCBoYXMgYSBkaWZmZXJlbnQgbWVhbmluZyBmb3IgdGhpcyBzYW1lDQo+Pj4gdGVybSwgYW5k
IHRoZSBkaWZmZXJlbmNlIGlzIGNyaXRpY2FsLCBJIHdvdWxkIHN0cm9uZ2x5IHVyZ2UgeW91IHRv
DQo+Pj4gcGljayBhIGRpZmZlcmVudCB0ZXJtLg0KPj4+DQo+PiBJIGJlbGlldmUgdGhlcmUgYXJl
IG90aGVyIGRyYWZ0cyB3aXRoIHNpbWlsYXIgZGVmaW5pdGlvbnMgb2YgIkluaXRpYWwgT2ZmZXIi
Lg0KPj4NCj4gUGVyaGFwcywgYnV0IGFzIEkgbm90ZWQsIDMyNjRzIGRpc2FncmVlcy4NCj4NCj4+
IEFueXdheSwgd291bGQgc29tZXRoaW5nIGxpa2UgIkluaXRpYWwgQlVORExFIG9mZmVyIiBiZSBi
ZXR0ZXI/DQo+DQo+IE5vdCByZWFsbHkuDQoNClNvLCB3aGF0IGRvIHlvdSBzdWdnZXN0Pw0KDQpO
b3RlIHRoYXQsIGZvciBtb3N0IFNEUCBleHRlbnNpb25zIEkgY2FuIHRoaW5rIG9mLCAiaW5pdGlh
bCBvZmZlciIgcmVmZXJzIHRvIHRoZSBvZmZlciB3aGVyZSB5b3UgYWN0dWFsbHkgc3RhcnQgdXNp
bmcgdGhlIGV4dGVuc2lvbiAoZXhwbGljaXRseSBvciBpbXBsaWNpdGx5KS4gDQoNCi0tLQ0KDQo+
Pj4+IFRoZSBCVU5ETEUgZXh0ZW5zaW9uIGlzIGluZGljYXRlZCB1c2luZyBhbiBTRFAgJ2dyb3Vw
JyBhdHRyaWJ1dGUNCj4+Pj4gd2l0aCBhIHNlbWFudGljcyB2YWx1ZSBbUkZDNTg4OF0gb2YgIkJV
TkRMRSIuwqAgQW4gaWRlbnRpZmljYXRpb24tdGFnIGlzDQo+Pj4+IGFzc2lnbmVkIHRvIGVhY2gg
YnVuZGxlZCAibT0iIHNlY3Rpb24sIGFuZCBlYWNoIGlkZW50aWZpY2F0aW9uLXRhZw0KPj4+PiBp
cyBsaXN0ZWQgaW4gdGhlIFNEUCAnZ3JvdXA6QlVORExFJyBhdHRyaWJ1dGUgaWRlbnRpZmljYXRp
b24tdGFnIGxpc3QuDQo+Pj4+IEVhY2ggIm09IiBzZWN0aW9uIHdob3NlIGlkZW50aWZpY2F0aW9u
LXRhZyBpcyBsaXN0ZWQgaW4gdGhlDQo+Pj4+IGlkZW50aWZpY2F0aW9uLXRhZyBsaXN0IGlzIGFz
c29jaWF0ZWQgd2l0aCBhIGdpdmVuIEJVTkRMRSBncm91cC4NCj4+PiANCj4+PiBIb3cgYWJvdXQg
ImlzIHBhcnQgb2YiIGluc3RlYWQgb2YgImFzc29jaWF0ZWQgd2l0aCINCj4+Pg0KPj4+IFRoZXJl
IGFyZSBtb3N0IGxpa2VseSBvdGhlciBpbnN0YW5jZXMgdGhhdCB3b3VsZCBoYXZlIHRvIGJlIGZp
eGVkLCBhbmQgSSdkIGxpa2UgdG8gdHJ5IHRvIG1haW50YWluIGNvbnNpc3RlbnQgdGVybWlub2xv
Z3kuIA0KPj4NCj4gWWVzLCBJIHdvdWxkIGNoYW5nZSBhbGwgb2YgdGhlbS4NCg0KSSBoYXZlIGEg
cXVpY2sgbG9vaywgYW5kIEkgYW0gbm90IHN1cmUgd2UgY2FuIGNoYW5nZSBhbGwgaW5zdGFuY2Vz
IG9mICJhc3NvY2lhdGVkIHdpdGgiIHRvICJpcyBwYXJ0IG9mIi4NCg0KLS0tDQoNCj4+PiBFYWNo
ICJtPSIgc2VjdGlvbiB3aG9zZSBpZGVudGlmaWNhdGlvbi10YWcgaXMgbGlzdGVkIGluIHRoZQ0K
Pj4+IGlkZW50aWZpY2F0aW9uLXRhZyBsaXN0IGlzIGFzc29jaWF0ZWQgd2l0aCBhIGdpdmVuIEJV
TkRMRSBncm91cC4NCj4+PsKgIMKgDQo+Pj4gU0RQIGJvZGllcyBjYW4gY29udGFpbiBtdWx0aXBs
ZSBCVU5ETEUgZ3JvdXBzLsKgIEFueSBnaXZlbiBidW5kbGVkDQo+Pj4gIm09IiBzZWN0aW9uIE1V
U1QgTk9UIGJlIGFzc29jaWF0ZWQgd2l0aCBtb3JlIHRoYW4gb25lIEJVTkRMRSBncm91cA0KPj4+
IGF0IGFueSBnaXZlbiB0aW1lLg0KPj4+IA0KPj4+IEFnYWluICJwYXJ0IG9mIg0KPj4NCj4+IFRo
ZXJlIGFyZSBtdWx0aXBsZSBpbnN0YW5jZXMgb2YgImFzc29jaWF0ZWQgd2l0aCBCVU5ETEUgZ3Jv
dXAiIHRlcm1pbm9sb2d5IHRocm91Z2hvdXQgdGhlIGRvY3VtZW50Lg0KPg0KPiBZZXMsIGFuZCB0
aGV5J3JlIGFsbCBiYWQuDQoNCldoeT8NCg0KLS0tDQrCoA0KPj4+PiBJZiB0aGUgYW5zd2VyIGNv
bnRhaW5zIGEgQlVORExFIGdyb3VwLCB0aGUgYW5zd2VyZXIgTVVTVDoNCj4+Pj7CoCDCoA0KPj4+
PiBvwqAgU2VsZWN0IGFuIG9mZmVyZXIgQlVORExFIGFkZHJlc3M6cG9ydCBbU2VjdGlvbiA4LjMu
MV07IGFuZA0KPj4+PsKgIMKgDQo+Pj4+IG/CoCBTZWxlY3QgYW4gYW5zd2VyZXIgQlVORExFIGFk
ZHJlc3M6cG9ydCBbU2VjdGlvbiA4LjMuMl0uDQo+Pj4NCj4+PiBUaGlzIGlzbid0IHJpZ2h0LCBi
ZWNhdXNlIGVhY2ggQlVORExFIGdyb3VwIGhhcyBpdHMgb3duIGFkZHJlc3M6cG9ydCwNCj4+PiBz
byBpbnN0ZWFkICJGb3IgZWFjaCBCVU5ETEUgZ3JvdXAiIGNvbnRhaW5lZCBpbiB0aGUgb2ZmZXIu
DQo+Pg0KPj4gVGhlIHByb2NlZHVyZXMgaXMgZm9yIGluZGl2aWR1YWwgQlVORExFIGdyb3Vwcywg
YXMgaW5kaWNhdGVkIGluIFNlY3Rpb24gODoNCj4+DQo+PsKgIlNEUCBvZmZlcnMgYW5kIGFuc3dl
cnMgY2FuIGNvbnRhaW4gbXVsdGlwbGUgQlVORExFIGdyb3Vwcy7CoCBUaGUNCj4+wqAgcHJvY2Vk
dXJlcyBpbiB0aGlzIHNlY3Rpb24gYXBwbHkgaW5kZXBlbmRlbnRseSB0byBhIGdpdmVuIEJVTkRM
RQ0KPj7CoCBncm91cC4iJ8KgDQo+DQo+IEkgZG9uJ3QgZmluZCB0aGlzIHZlcnkgY2xlYXIuDQoN
CkkgYW0gbm90IHN1cmUgYWRkaW5nICJGb3IgZWFjaCBCVU5ETEUgZ3JvdXAiIGFsbCBvdmVyIChp
dCB3b3VsZCBiZSBuZWVkZWQgaW4gbW9yZSBwbGFjZXMgdGhhbiBpbmRpY2F0ZWQgYWJvdmUpIHdv
dWxkIG1ha2UgaXQgYmV0dGVyLg0KDQpTbywgbXkgcHJlZmVyZW5jZSB3b3VsZCBiZSB0byB3b3Jr
IG9uIHRoZSBjbGFyaWZpY2F0aW9uIHRleHQgYWJvdmUsIGlmIHlvdSB0aGluayBpdCBuZWVkcyB0
byBiZSBtb3JlIGNsZWFyLg0KDQotLS0NCg0KPj4+IE1vcmUgaW1wb3J0YW50bHksIGl0J3Mgbm90
IHRoZSBhZGRyZXNzOnBvcnQgdGhhdCB0aGUgYW5zd2VyZXIgY2hvb3NlcywNCj4+PiBidXQgcmF0
aGVyIHRoZSBtPSBzZWN0aW9uLiBJLmUuLA0KPj4+DQo+Pj4gbyBEZXRlcm1pbmUgdGhlIGZpcnN0
IG09IHNlY3Rpb24gaW4gdGhlIEJVTkRMRSBncm91cCB3aGljaCB3aWxsIGJlDQo+Pj7CoCDCoEJV
TkRMRWQgaW4gdGhlIGFuc3dlcg0KPj4+IG8gU2VsZWN0IGFuIGFuc3dlcmVyIEJVTkRMRSBhZGRy
ZXNzOnBvcnQNCj4+DQo+PiBJIGRvbid0IHVuZGVyc3RhbmQgd2hhdCAiZmlyc3QgbT0gc2VjdGlv
biB3aGljaCB3aWxsIGJlIEJVTkRMRWQiIG1lYW5zLiBXaGF0IGlzICJmaXJzdCI/DQo+DQo+IFRo
ZSBvbmUgaW5kaWNhdGVkIGJ5IHRoZSBidW5kbGUgdGFnLg0KDQpJbiBteSBlYXJzICJGaXJzdCIg
c2VlbXMgdG8gcmVmZXJlbmNlIHRoZSBvcmRlciBvZiB0aGUgIm09IiBzZWN0aW9uIGluIHRoZSBT
RFAsIGJ1dCB0aGUgYnVuZGxlIHRhZyBjYW4gaW5kaWNhdGUgYW55IG9mIHRoZSAibT0iIHNlY3Rp
b25zLg0KDQotLS0NCg0KPj4+PiBvwqAgVGhlIGFuc3dlcmVyIHdpbGwgbm90IHJlamVjdCB0aGUg
Im09IiBzZWN0aW9uIFtTZWN0aW9uIDguMy40XTsNCj4+Pj7CoCDCoCDCoGFuZA0KPj4+Pg0KPj4+
PiBvwqAgVGhlICJtPSIgc2VjdGlvbiBkb2VzIG5vdCBjb250YWluIGEgemVybyBwb3J0IHZhbHVl
Lg0KPj4+Pg0KPj4+PiBJZiBhbGwgb2YgdGhlIGNyaXRlcmlhIGFib3ZlIGFyZSBmdWxmaWxsZWQs
IHRoZSBhbnN3ZXJlciBNVVNUIHNlbGVjdA0KPj4+IHRoZSBzdWdnZXN0ZWQgb2ZmZXJlciBCVU5E
TEUgYWRkcmVzczpwb3J0Lg0KPj4NCj4+IEFnYWluLCB0aGlzIGlzbid0IHNlbGVjdGluZyB0aGUg
YWRkcmVzczpwb3J0IGJ1dCByYXRoZXIgdGhlIG09c2VjdGlvbg0KPj4NCj4gU3VyZSwgYnV0IGl0
IHBpY2tzIHRoZSBhZGRyZXNzOnBvcnQgb2YgdGhhdCBzZWxlY3RlZCBtPSBzZWN0aW9uLg0KPg0K
PiBObywgaXQgcGlja3MgdGhlIG09IHNlY3Rpb24gYW5kIHRoZW4gdXNlcyB0aGUgYXR0YWNoZWQg
YWRkcmVzczpwb3J0Lg0KDQpJIGRvbid0IGRpc2FncmVlLg0KDQotLS0NCg0KPj4+IGJ1bmRsZWQg
Im09IiBzZWN0aW9uIHRoZSBhbnN3ZXJlciBNVVNUIGFzc2lnbiBhIHplcm8gcG9ydCB2YWx1ZSBh
bmQNCj4+PiBpbmNsdWRlIGFuIFNEUCAnYnVuZGxlLW9ubHknIGF0dHJpYnV0ZS4NCj4+Pg0KPj4+
IFRoZSBhbnN3ZXJlciBNVVNUIE5PVCBhc3NpZ24gYW4gYW5zd2VyZXIgQlVORExFIGFkZHJlc3M6
cG9ydCB0byBhbg0KPj4+ICJtPSIgc2VjdGlvbiB0aGF0IGlzIG5vdCB3aXRoaW4gdGhlIEJVTkRM
RSBncm91cCwgb3IgdG8gYW4gIm09Ig0KPj4+IHNlY3Rpb24gdGhhdCBpcyB3aXRoaW4gYW5vdGhl
ciBCVU5ETEUgZ3JvdXAuDQo+Pj4NCj4+PiBUaGlzIHJlcGVhdHMgdGV4dCBpbiBTIDguMy4NCj4+
DQo+PiBXaGF0IHRleHQgZG8geW91IHRoaW5rIGlzIHJlcGVhdGVkPw0KPg0KPiA4LjMuIGFscmVh
ZHkgc2F5cyB5b3UgY2FuJ3QgbW92ZSBiZXR3ZWVuIEJVTkRMRSBncm91cHMuDQoNCk9rLCBidXQg
SSBkb24ndCB0aGluayB0aGF0IGNvdmVycyB0aGUgZmFjdCB0aGF0IHlvdSBjYW4ndCBhc3NpZ24g
dGhlIGFkZHJlc3M6cG9ydCB0byBhbiBtPSBzZWN0aW9uIHRoYXQgaXNuJ3QgcGFydCBvZiBhIEJV
TkRMRSBncm91cC4NCg0KLS0tDQoNCj4+PiBvwqAgSW4gdGhlIGNvcnJlc3BvbmRpbmcgb2ZmZXIs
IGFuIG9mZmVyZXIgQlVORExFIGFkZHJlc3M6cG9ydA0KPj4+wqAgwqAgwqAocHJldmlvdXNseSBz
ZWxlY3RlZCBbU2VjdGlvbiA4LjMuMV0gb3IgbmV3bHkgc3VnZ2VzdGVkDQo+Pj7CoCDCoCDCoFtT
ZWN0aW9uIDguNS4xXSkgaGFzIGJlZW4gYXNzaWduZWQgdG8gdGhlICJtPSIgc2VjdGlvbiBieSB0
aGUNCj4+PsKgIMKgIMKgb2ZmZXJlci4NCj4+Pg0KPj4+IElmIHRoZSBjcml0ZXJpYSBhYm92ZSBp
cyBmdWxmaWxsZWQsIHRoZSBhbnN3ZXJlciBjYW4gbm90IHJlamVjdCB0aGUNCj4+PiANCj4+PiAi
Y3JpdGVyaWEuLi4gYXJlIg0KPj4NCj4+IFNvbWVvbmUgc2FpZCBpdCBzaG91bGQgYmUgImlzIiwg
YnV0IEkgYW0gZmluZSB1c2luZyAiYXJlIiwgYW5kIGNhbiBmaXggYXMgc3VnZ2VzdGVkLg0KPg0K
PiBPSywgd2VsbCwgImNyaXRlcmlhIiBpcyB0aGUgcGx1cmFsIG9mICJjcml0ZXJpb24iDQoNCk9r
Lg0KDQotLS0NCg0KPj4+wqAgwqA4LjQuwqAgT2ZmZXJlciBQcm9jZXNzaW5nIG9mIHRoZSBTRFAg
QW5zd2VyDQo+Pj7CoCDCoA0KPj4+wqAgwqAgwqAgV2hlbiBhbiBvZmZlcmVyIHJlY2VpdmVzIGFu
IGFuc3dlciwgaWYgdGhlIGFuc3dlciBjb250YWlucyBhIEJVTkRMRQ0KPj4+wqAgwqAgwqAgZ3Jv
dXAsIHRoZSBvZmZlcmVyIE1VU1QgY2hlY2sgdGhhdCBhbnkgYnVuZGxlZCAibT0iIHNlY3Rpb24g
aW4gdGhlDQo+Pj7CoCDCoCDCoCBhbnN3ZXIgd2FzIGluZGljYXRlZCBhcyBidW5kbGVkIGluIHRo
ZSBjb3JyZXNwb25kaW5nIG9mZmVyLsKgIElmDQo+Pj7CoCDCoCDCoCB0aGVyZSBpcyBubyBtaXNt
YXRjaCwgdGhlIG9mZmVyZXIgTVVTVCB1c2UgdGhlIG9mZmVyZXIgQlVORExFDQo+Pj7CoCDCoCDC
oCBhZGRyZXNzOnBvcnQsDQo+Pj4NCj4+PiBhZGRyZXNzOnBvcnQsIGFnYWluLiBJdCdzIHRoZSBt
PXNlY3Rpb24gdGhhdCdzIHJlbGV2YW50Lg0KPj4NCj4+IFllcywgYnV0IGl0IHVzZXMgdGhlIGFk
ZHJlc3M6cG9ydCBvZiB0aGUgbT0gc2VjdGlvbi4NCj4+DQo+PiBXaGF0IGRvIHlvdSBzdWdnZXN0
IHRvIHNheSBpbnN0ZWFkPw0KPg0KPiAiTVVTVCB1c2UgdGhlIGluZGljYXRlZCBtPSBzZWN0aW9u
IGFzIHRoZSBidW5kbGUgPHdoYXRldmVyIHRlcm0gd2UgY2hvb3NlPiINCg0KImJ1bmRsZSBtLSBz
ZWN0aW9uIiB3b3VsZCBiZSBhIHN0cmFpZ2h0IGZvcndhcmQgY2hvaWNlLiBIb3dldmVyLCB0aGF0
IGlzIHZlcnkgc2ltaWxhciB0byAiYnVuZGxlZCBtLSBzZWN0aW9uIiwgd2hpY2ggcmVmZXJzIHRv
IGFueSBtLSBzZWN0aW9uIHdpdGhpbiBhIEJVTkRMRSBncm91cC4uLg0KDQotLS0NCg0KPj4+IFdo
ZW4gdGhlIG9mZmVyZXIgZ2VuZXJhdGVzIGEgc3Vic2VxdWVudCBvZmZlciwgdGhlIG9mZmVyZXIN
Cj4+PiBCVU5ETEUtdGFnIE1VU1QgcmVwcmVzZW50IHRoZSBidW5kbGVkICJtPSIgc2VjdGlvbiB0
byB3aGljaCB0aGUgb2ZmZXJlciBCVU5ETEUNCj4+PiBhZGRyZXNzOnBvcnQgKHByZXZpb3VzbHkg
bmVnb3RpYXRlZCBvciBuZXdseSBzdWdnZXN0ZWQpIGhhcyBiZWVuIGFzc2lnbmVkLg0KPj4+wqAg
wqANCj4+PiA4LjUuMS7CoCBTdWdnZXN0aW5nIGEgTmV3IE9mZmVyZXIgQlVORExFIEFkZHJlc3M6
UG9ydA0KPj4+IA0KPj4+IEFnYWluIGl0IHdvdWxkIG1ha2UgbW9yZSBzZW5zZSB0byBkZXNjcmli
ZSB0aGlzIGFzIHN1Z2dlc3RpbmcgYSBuZXcgbT0gc2VjdGlvbi4NCj4+DQo+PiBJdCBkb2VzIG5v
dCBoYXZlIHRvIGJlIGEgbmV3ICJtPSIgc2VjdGlvbi4gVGhlIG5ldyBhZGRyZXNzOnBvcnQgY2Fu
IGJlIGFzc2lnbmVkIHRvIGFuIGV4aXN0aW5nICJtPSIgc2VjdGlvbi4NCj4NCj4gWW91J3JlIHN1
Z2dlc3RpbmcgdGhhdCBhIG5ldyBtPSBzZWN0aW9uIGJlIHRoZSBvbmUgdGhhdCB0aGluZ3MgYXJl
IGJ1bmRsZWQgaW50by4NCg0KTm90IG5lY2Vzc2FyaWx5LiBUaGUgbmV3IGFkZHJlc3M6cG9ydCBp
cyBhc3NpZ25lZCB0byAqYSogYnVuZGxlZCBtPSBzZWN0aW9uLCB3aGljaCBjb3VsZCBiZSB0aGUg
KnNhbWUqIG09IHNlY3Rpb24gY3VycmVudGx5IHVzZWQgdG8gYnVuZGxlIHRoaW5ncyBpbnRvLg0K
DQotLS0NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Wed Apr 18 05:34:48 2018
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 E1A4B129C53; Wed, 18 Apr 2018 05:34:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org, mmusic-chairs@ietf.org,  fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152405488591.31812.8842902591498905286.idtracker@ietfa.amsl.com>
Date: Wed, 18 Apr 2018 05:34:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qpSZDMDtO5eoTIVZZgT5QxWDRpA>
Subject: [MMUSIC] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-mmusic-sdp-bundle-negotiation-49=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 12:34:46 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-mmusic-sdp-bundle-negotiation-49: 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-bundle-negotiation/



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

Maybe also briefly say in the abstract how/why RFC7941 is updated.



From nobody Wed Apr 18 05:50:33 2018
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 4075E12D80E for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 05:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 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, T_DKIMWL_WL_MED=-0.01] 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 F6F74Bdld87c for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 05:50:29 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 3DBEF12D7E8 for <mmusic@ietf.org>; Wed, 18 Apr 2018 05:50:29 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id f63-v6so1450233oic.4 for <mmusic@ietf.org>; Wed, 18 Apr 2018 05:50: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=X3afc8dthRbh3A6BZyKB6U+kntcFbmlCXK2HdxHv8gU=; b=n3BqcTJCOJV732vJoOBnOBiw2YhBUejvC6522yNv6KMyO105bT+c8EsVau6YTZM1ST efgx/ZJS0uPvRfX6eP22s8S/SWcxy5hWZ7M0LwvwD3JTlBK8cGtFp7XV0IDWKfE4W9fJ ujBXWbkN/ZBawQd/0QFJxNsYRGP+FBUjk73xhET3apsQuRrdR68gbGLHBDyejBiE4N2O Lg1RLOdv0hpuL8pOgDrzS0TwySsyb+rlAi2y7H/3Z+dPUwETCitOXV3/KFUYjTxzWheZ jurOk1euwlZjqNPqChjNNdDXih8oTHbfeppSq53KuPoqq1ymcqothTgqQL5VOljTH0/l mK9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=X3afc8dthRbh3A6BZyKB6U+kntcFbmlCXK2HdxHv8gU=; b=eonpXfxKQ5TQfu0rNmLXHYBRxqbJIEKbrtj6FnUucNi2XK9d7pleme6HoOfoqwZJru of9yKLF204lpKdMplEiPdWx3xkJGo1E7PwruLBsu8xDuXj1Aw0emIbovegfdwSz7BvOI ClYQWiBDDZGaERkqjcfSVcd2Im61MbkGsrSjBdS4AEnd0PPOZogEWqRKMzwULZSF3+xM 9xmcW+H0vCB1MENgxhFh2GCNMANLXhuyLRjrZIk4cRTT6EVE51VJVdtqPIowJE3iTlzp xDA1K7bdgGRNQ2zb3WhB5eAqd5CvSQBdpWJI51wSe4Uc105gvrcLu8BPHRYnLkbqzr2U xqSA==
X-Gm-Message-State: ALQs6tDmLqyh15PF1ph3R+L/M8wy0lytEPF4PHhLqzO8bqYH0CTKRl0l E3e41rIGsOgmaR+hhsd1Co6UD2LUmQUCqIBvSlIphw==
X-Google-Smtp-Source: AIpwx49hFE/y/5B4E5ALV69Ox/Bc4/4n8UnXHlP/Fy0wgliuHwB3esib3qwkYTGEMClVmapGFSQfY6AdMlL0X56iNto=
X-Received: by 2002:aca:3114:: with SMTP id x20-v6mr1109339oix.108.1524055828571;  Wed, 18 Apr 2018 05:50:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Wed, 18 Apr 2018 05:49:48 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 18 Apr 2018 05:49:48 -0700
Message-ID: <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000047d60a056a1ee69d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UIyGrS-sOAtOFDganwSVXXxOqqU>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 12:50:32 -0000

--00000000000047d60a056a1ee69d
Content-Type: text/plain; charset="UTF-8"

On Wed, Apr 18, 2018 at 2:28 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >>>> o  Bundled media: All media associated with a given BUNDLE group.
> >>>>
> >>>> o  Initial offer: The first offer, within an SDP session (e.g. a
> >>>>     SIP dialog when the Session Initiation Protocol (SIP) [RFC3261] is
> >>>>     used to carry SDP), in which the offerer indicates that it wants
> >>>>     to create a given BUNDLE group.
> >>>
> >>> This is a very idiosyncratic definition, because it's *not* the first
> >>> offer in the session, but the one where the BUNDLE group is
> >>> introduced. Given that 3264 has a different meaning for this same
> >>> term, and the difference is critical, I would strongly urge you to
> >>> pick a different term.
> >>>
> >> I believe there are other drafts with similar definitions of "Initial
> Offer".
> >>
> > Perhaps, but as I noted, 3264s disagrees.
> >
> >> Anyway, would something like "Initial BUNDLE offer" be better?
> >
> > Not really.
>
> So, what do you suggest?
>
> Note that, for most SDP extensions I can think of, "initial offer" refers
> to the offer where you actually start using the extension (explicitly or
> implicitly).
>

But that's not the case here, because this is the one for this BUNDLE
group, not for BUNDLE as a whole

I'm not sure you need a specific term here. How often do you use it?


---
>
> >>>> The BUNDLE extension is indicated using an SDP 'group' attribute
> >>>> with a semantics value [RFC5888] of "BUNDLE".  An identification-tag
> is
> >>>> assigned to each bundled "m=" section, and each identification-tag
> >>>> is listed in the SDP 'group:BUNDLE' attribute identification-tag list.
> >>>> Each "m=" section whose identification-tag is listed in the
> >>>> identification-tag list is associated with a given BUNDLE group.
> >>>
> >>> How about "is part of" instead of "associated with"
> >>>
> >>> There are most likely other instances that would have to be fixed, and
> I'd like to try to maintain consistent terminology.
> >>
> > Yes, I would change all of them.
>
> I have a quick look, and I am not sure we can change all instances of
> "associated with" to "is part of".
>

Yes, quite possibly, but that's an argument against using "associated" in
this way. Find a set of more specific terms and use them.

>
> ---
>
> >>> Each "m=" section whose identification-tag is listed in the
> >>> identification-tag list is associated with a given BUNDLE group.
> >>>
> >>> SDP bodies can contain multiple BUNDLE groups.  Any given bundled
> >>> "m=" section MUST NOT be associated with more than one BUNDLE group
> >>> at any given time.
> >>>
> >>> Again "part of"
> >>
> >> There are multiple instances of "associated with BUNDLE group"
> terminology throughout the document.
> >
> > Yes, and they're all bad.
>
> Why?
>

Because it's a generic term when specific ones would be bette



> ---
>
> >>>> If the answer contains a BUNDLE group, the answerer MUST:
> >>>>
> >>>> o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
> >>>>
> >>>> o  Select an answerer BUNDLE address:port [Section 8.3.2].
> >>>
> >>> This isn't right, because each BUNDLE group has its own address:port,
> >>> so instead "For each BUNDLE group" contained in the offer.
> >>
> >> The procedures is for individual BUNDLE groups, as indicated in Section
> 8:
> >>
> >> "SDP offers and answers can contain multiple BUNDLE groups.  The
> >>  procedures in this section apply independently to a given BUNDLE
> >>  group."'
> >
> > I don't find this very clear.
>
> I am not sure adding "For each BUNDLE group" all over (it would be needed
> in more places than indicated above) would make it better.
>
> So, my preference would be to work on the clarification text above, if you
> think it needs to be more clear.
>

I'm not sure how to fix this. Perhaps it needs a real rewrite

>
> ---
>
> >>> More importantly, it's not the address:port that the answerer chooses,
> >>> but rather the m= section. I.e.,
> >>>
> >>> o Determine the first m= section in the BUNDLE group which will be
> >>>   BUNDLEd in the answer
> >>> o Select an answerer BUNDLE address:port
> >>
> >> I don't understand what "first m= section which will be BUNDLEd" means.
> What is "first"?
> >
> > The one indicated by the bundle tag.
>
> In my ears "First" seems to reference the order of the "m=" section in the
> SDP, but the bundle tag can indicate any of the "m=" sections.
>

Sure. I'm not suggesting text in this specific case, I'm trying to provide
a structure that explains what's going on

>
> ---
>
> >>>> o  The answerer will not reject the "m=" section [Section 8.3.4];
> >>>>     and
> >>>>
> >>>> o  The "m=" section does not contain a zero port value.
> >>>>
> >>>> If all of the criteria above are fulfilled, the answerer MUST select
> >>> the suggested offerer BUNDLE address:port.
> >>
> >> Again, this isn't selecting the address:port but rather the m=section
> >>
> > Sure, but it picks the address:port of that selected m= section.
> >
> > No, it picks the m= section and then uses the attached address:port.
>
> I don't disagree.
>

Right, but the document throughout (see my other email about trickle) acts
like its the address that is the key

>
> ---
>
> >>> bundled "m=" section the answerer MUST assign a zero port value and
> >>> include an SDP 'bundle-only' attribute.
> >>>
> >>> The answerer MUST NOT assign an answerer BUNDLE address:port to an
> >>> "m=" section that is not within the BUNDLE group, or to an "m="
> >>> section that is within another BUNDLE group.
> >>>
> >>> This repeats text in S 8.3.
> >>
> >> What text do you think is repeated?
> >
> > 8.3. already says you can't move between BUNDLE groups.
>
> Ok, but I don't think that covers the fact that you can't assign the
> address:port to an m= section that isn't part of a BUNDLE group.
>

Sure, so state the rules in one place


>>>   8.4.  Offerer Processing of the SDP Answer
> >>>
> >>>      When an offerer receives an answer, if the answer contains a
> BUNDLE
> >>>      group, the offerer MUST check that any bundled "m=" section in the
> >>>      answer was indicated as bundled in the corresponding offer.  If
> >>>      there is no mismatch, the offerer MUST use the offerer BUNDLE
> >>>      address:port,
> >>>
> >>> address:port, again. It's the m=section that's relevant.
> >>
> >> Yes, but it uses the address:port of the m= section.
> >>
> >> What do you suggest to say instead?
> >
> > "MUST use the indicated m= section as the bundle <whatever term we
> choose>"
>
> "bundle m- section" would be a straight forward choice. However, that is
> very similar to "bundled m- section", which refers to any m- section within
> a BUNDLE group...
>

When Adam and I were talking yesterday he suggested "lead" m= section.

>
> ---
>
> >>> When the offerer generates a subsequent offer, the offerer
> >>> BUNDLE-tag MUST represent the bundled "m=" section to which the
> offerer BUNDLE
> >>> address:port (previously negotiated or newly suggested) has been
> assigned.
> >>>
> >>> 8.5.1.  Suggesting a New Offerer BUNDLE Address:Port
> >>>
> >>> Again it would make more sense to describe this as suggesting a new m=
> section.
> >>
> >> It does not have to be a new "m=" section. The new address:port can be
> assigned to an existing "m=" section.
> >
> > You're suggesting that a new m= section be the one that things are
> bundled into.
>
> Not necessarily. The new address:port is assigned to *a* bundled m=
> section, which could be the *same* m= section currently used to bundle
> things into.
>

Sure, but again, it's not the address:port that's being suggested, it's its
parameters

-Ekr


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

--00000000000047d60a056a1ee69d
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, Apr 18, 2018 at 2:28 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:<span class=3D""></span><br>=
<span class=3D""></span><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
&gt;&gt;&gt;&gt; o=C2=A0 Bundled media: All media associated with a given B=
UNDLE group.<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt; o=C2=A0 Initial offer: The first offer, within an SDP sess=
ion (e.g. a<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0SIP dialog when the Session Initiation =
Protocol (SIP) [RFC3261] is<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0used to carry SDP), in which the offere=
r indicates that it wants<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0to create a given BUNDLE group.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; This is a very idiosyncratic definition, because it&#39;s *not=
* the first<br>
&gt;&gt;&gt; offer in the session, but the one where the BUNDLE group is<br=
>
&gt;&gt;&gt; introduced. Given that 3264 has a different meaning for this s=
ame<br>
&gt;&gt;&gt; term, and the difference is critical, I would strongly urge yo=
u to<br>
&gt;&gt;&gt; pick a different term.<br>
&gt;&gt;&gt;<br>
&gt;&gt; I believe there are other drafts with similar definitions of &quot=
;Initial Offer&quot;.<br>
&gt;&gt;<br>
&gt; Perhaps, but as I noted, 3264s disagrees.<br>
&gt;<br>
&gt;&gt; Anyway, would something like &quot;Initial BUNDLE offer&quot; be b=
etter?<br>
&gt;<br>
&gt; Not really.<br>
<br>
</span>So, what do you suggest?<br>
<br>
Note that, for most SDP extensions I can think of, &quot;initial offer&quot=
; refers to the offer where you actually start using the extension (explici=
tly or implicitly). <br></blockquote><div><br></div><div>But that&#39;s not=
 the case here, because this is the one for this BUNDLE group, not for BUND=
LE as a whole<br></div><div><br></div><div>I&#39;m not sure you need a spec=
ific term here. How often do you use it?</div><div><br></div><div><br><span=
 class=3D""></span><span class=3D""></span></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><span class=3D"">
---<br>
<br>
&gt;&gt;&gt;&gt; The BUNDLE extension is indicated using an SDP &#39;group&=
#39; attribute<br>
&gt;&gt;&gt;&gt; with a semantics value [RFC5888] of &quot;BUNDLE&quot;.=C2=
=A0 An identification-tag is<br>
&gt;&gt;&gt;&gt; assigned to each bundled &quot;m=3D&quot; section, and eac=
h identification-tag<br>
&gt;&gt;&gt;&gt; is listed in the SDP &#39;group:BUNDLE&#39; attribute iden=
tification-tag list.<br>
&gt;&gt;&gt;&gt; Each &quot;m=3D&quot; section whose identification-tag is =
listed in the<br>
&gt;&gt;&gt;&gt; identification-tag list is associated with a given BUNDLE =
group.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; How about &quot;is part of&quot; instead of &quot;associated w=
ith&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There are most likely other instances that would have to be fi=
xed, and I&#39;d like to try to maintain consistent terminology. <br>
&gt;&gt;<br>
&gt; Yes, I would change all of them.<br>
<br>
</span>I have a quick look, and I am not sure we can change all instances o=
f &quot;associated with&quot; to &quot;is part of&quot;.<br></blockquote><d=
iv><br></div><div>Yes, quite possibly, but that&#39;s an argument against u=
sing &quot;associated&quot; in this way. Find a set of more specific terms =
and use them.<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D""><br>
---<br>
<br>
&gt;&gt;&gt; Each &quot;m=3D&quot; section whose identification-tag is list=
ed in the<br>
&gt;&gt;&gt; identification-tag list is associated with a given BUNDLE grou=
p.<br>
&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt; SDP bodies can contain multiple BUNDLE groups.=C2=A0 Any given=
 bundled<br>
&gt;&gt;&gt; &quot;m=3D&quot; section MUST NOT be associated with more than=
 one BUNDLE group<br>
&gt;&gt;&gt; at any given time.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Again &quot;part of&quot;<br>
&gt;&gt;<br>
&gt;&gt; There are multiple instances of &quot;associated with BUNDLE group=
&quot; terminology throughout the document.<br>
&gt;<br>
&gt; Yes, and they&#39;re all bad.<br>
<br>
</span>Why?<br></blockquote><div><br></div><div>Because it&#39;s a generic =
term when specific ones would be bette</div><div><br></div><div><br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
<br>
---<br>
<span class=3D"">=C2=A0<br>
&gt;&gt;&gt;&gt; If the answer contains a BUNDLE group, the answerer MUST:<=
br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt; o=C2=A0 Select an offerer BUNDLE address:port [Section 8.3=
.1]; and<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt; o=C2=A0 Select an answerer BUNDLE address:port [Section 8.=
3.2].<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; This isn&#39;t right, because each BUNDLE group has its own ad=
dress:port,<br>
&gt;&gt;&gt; so instead &quot;For each BUNDLE group&quot; contained in the =
offer.<br>
&gt;&gt;<br>
&gt;&gt; The procedures is for individual BUNDLE groups, as indicated in Se=
ction 8:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0&quot;SDP offers and answers can contain multiple BUNDLE grou=
ps.=C2=A0 The<br>
&gt;&gt;=C2=A0 procedures in this section apply independently to a given BU=
NDLE<br>
&gt;&gt;=C2=A0 group.&quot;&#39;=C2=A0<br>
&gt;<br>
&gt; I don&#39;t find this very clear.<br>
<br>
</span>I am not sure adding &quot;For each BUNDLE group&quot; all over (it =
would be needed in more places than indicated above) would make it better.<=
br>
<br>
So, my preference would be to work on the clarification text above, if you =
think it needs to be more clear.<br></blockquote><div><br></div><div>I&#39;=
m not sure how to fix this. Perhaps it needs a real rewrite <br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
<br>
---<br>
<span class=3D""><br>
&gt;&gt;&gt; More importantly, it&#39;s not the address:port that the answe=
rer chooses,<br>
&gt;&gt;&gt; but rather the m=3D section. I.e.,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; o Determine the first m=3D section in the BUNDLE group which w=
ill be<br>
&gt;&gt;&gt;=C2=A0 =C2=A0BUNDLEd in the answer<br>
&gt;&gt;&gt; o Select an answerer BUNDLE address:port<br>
&gt;&gt;<br>
&gt;&gt; I don&#39;t understand what &quot;first m=3D section which will be=
 BUNDLEd&quot; means. What is &quot;first&quot;?<br>
&gt;<br>
&gt; The one indicated by the bundle tag.<br>
<br>
</span>In my ears &quot;First&quot; seems to reference the order of the &qu=
ot;m=3D&quot; section in the SDP, but the bundle tag can indicate any of th=
e &quot;m=3D&quot; sections.<br></blockquote><div><br></div><div>Sure. I&#3=
9;m not suggesting text in this specific case, I&#39;m trying to provide a =
structure that explains what&#39;s going on<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<span class=3D""><br>
---<br>
<br>
&gt;&gt;&gt;&gt; o=C2=A0 The answerer will not reject the &quot;m=3D&quot; =
section [Section 8.3.4];<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0and<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; o=C2=A0 The &quot;m=3D&quot; section does not contain a ze=
ro port value.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; If all of the criteria above are fulfilled, the answerer M=
UST select<br>
&gt;&gt;&gt; the suggested offerer BUNDLE address:port.<br>
&gt;&gt;<br>
&gt;&gt; Again, this isn&#39;t selecting the address:port but rather the m=
=3Dsection<br>
&gt;&gt;<br>
&gt; Sure, but it picks the address:port of that selected m=3D section.<br>
&gt;<br>
&gt; No, it picks the m=3D section and then uses the attached address:port.=
<br>
<br>
</span>I don&#39;t disagree.<br></blockquote><div><br></div><div>Right, but=
 the document throughout (see my other email about trickle) acts like its t=
he address that is the key <br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D""><br>
---<br>
<br>
&gt;&gt;&gt; bundled &quot;m=3D&quot; section the answerer MUST assign a ze=
ro port value and<br>
&gt;&gt;&gt; include an SDP &#39;bundle-only&#39; attribute.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The answerer MUST NOT assign an answerer BUNDLE address:port t=
o an<br>
&gt;&gt;&gt; &quot;m=3D&quot; section that is not within the BUNDLE group, =
or to an &quot;m=3D&quot;<br>
&gt;&gt;&gt; section that is within another BUNDLE group.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; This repeats text in S 8.3.<br>
&gt;&gt;<br>
&gt;&gt; What text do you think is repeated?<br>
&gt;<br>
&gt; 8.3. already says you can&#39;t move between BUNDLE groups.<br>
<br>
</span>Ok, but I don&#39;t think that covers the fact that you can&#39;t as=
sign the address:port to an m=3D section that isn&#39;t part of a BUNDLE gr=
oup.<br></blockquote><div><br></div><div>Sure, so state the rules in one pl=
ace<br></div><div>=C2=A0</div><div><span class=3D""></span><br><span class=
=3D""></span></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;&gt;&gt;=C2=A0 =C2=A08.4.=C2=A0 Offerer Processing of the SDP Answer<br=
>
&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 When an offerer receives an answer, if the=
 answer contains a BUNDLE<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 group, the offerer MUST check that any bun=
dled &quot;m=3D&quot; section in the<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 answer was indicated as bundled in the cor=
responding offer.=C2=A0 If<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 there is no mismatch, the offerer MUST use=
 the offerer BUNDLE<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 address:port,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; address:port, again. It&#39;s the m=3Dsection that&#39;s relev=
ant.<br>
&gt;&gt;<br>
&gt;&gt; Yes, but it uses the address:port of the m=3D section.<br>
&gt;&gt;<br>
&gt;&gt; What do you suggest to say instead?<br>
&gt;<br>
&gt; &quot;MUST use the indicated m=3D section as the bundle &lt;whatever t=
erm we choose&gt;&quot;<br>
<br>
</span>&quot;bundle m- section&quot; would be a straight forward choice. Ho=
wever, that is very similar to &quot;bundled m- section&quot;, which refers=
 to any m- section within a BUNDLE group...<br></blockquote><div><br></div>=
<div>When Adam and I were talking yesterday he suggested &quot;lead&quot; m=
=3D section. <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D""><br>
---<br>
<br>
&gt;&gt;&gt; When the offerer generates a subsequent offer, the offerer<br>
&gt;&gt;&gt; BUNDLE-tag MUST represent the bundled &quot;m=3D&quot; section=
 to which the offerer BUNDLE<br>
&gt;&gt;&gt; address:port (previously negotiated or newly suggested) has be=
en assigned.<br>
&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt; 8.5.1.=C2=A0 Suggesting a New Offerer BUNDLE Address:Port<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Again it would make more sense to describe this as suggesting =
a new m=3D section.<br>
&gt;&gt;<br>
&gt;&gt; It does not have to be a new &quot;m=3D&quot; section. The new add=
ress:port can be assigned to an existing &quot;m=3D&quot; section.<br>
&gt;<br>
&gt; You&#39;re suggesting that a new m=3D section be the one that things a=
re bundled into.<br>
<br>
</span>Not necessarily. The new address:port is assigned to *a* bundled m=
=3D section, which could be the *same* m=3D section currently used to bundl=
e things into.<br></blockquote><div><br></div><div>Sure, but again, it&#39;=
s not the address:port that&#39;s being suggested, it&#39;s its parameters<=
/div><div><br></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<br>
---<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote></div><br></div></div>

--00000000000047d60a056a1ee69d--


From nobody Wed Apr 18 05:53:25 2018
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 3BB4E12D80E for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 05:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01] 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 vitxP2b1PGDp for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 05:53:22 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::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 55AF712D7E6 for <mmusic@ietf.org>; Wed, 18 Apr 2018 05:53:22 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id w2-v6so1763055otj.0 for <mmusic@ietf.org>; Wed, 18 Apr 2018 05:53:22 -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=Xr2gFjdydrgBMXRKja/BlAsPfNyf5k+rTu8xuNimdts=; b=Y88LouB2VYVxU60fJw936t/TIuTJ/tSyQgI6QDrtjqjQAIc0WQXT9eSfHnWXGQy5+q usIHa6/pPjbBMQSddBOh7SCKfCqmuOnW0q+YF0g7p5+Mso65HtXO271QQR6seOj8Lt1k EvbuouVk4OnXdbwbeXblSzRPE/hrfH000cQhQThmHvOfjFYThmvxJjMrCCcD3nm16mpy Or8Svb086CVrspvvV4+73cKk2djP9u2VXeNHHkzJMzDPl2cYO23V1y09zXK+jvH1jQui FkK2fdrcsOVfe69QakrT6T10ahSYL/2zcP9ztLKGGR8LoeQ0+G1IT+LtHBxWg/kfBz0w ydYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Xr2gFjdydrgBMXRKja/BlAsPfNyf5k+rTu8xuNimdts=; b=snLo0//TzHVkI2vlQsG64l6wu72v8746f1WtDZaGizpltKui+MB/Zw2WifboZvSTfj Z/iqIV5WCuV9CYLmzDm8edUBsEBeg27viTP/UM3MIeeVzTUNZ6BUEQP5Pbcm5hxggrv+ bmaNSMvkJ2ZRPJxze+gGrySBwXzIFuneOoYOIOl08hNdpU5pDWUAihT2b7P8nc8gZFeW VQO0vj6LVDBd43bAteZLHjKSE5USX1jziZw1IicVWZ5UzWR5CWL/0M4lq66/jLhykc2F NmzCyehRQcItQeIWwNgbbxACmsGsJosr2wZCHSrpDBcTPZwm5iHxRjplezC3z2MaFwW9 41VA==
X-Gm-Message-State: ALQs6tAkncm2tunbEEt7fGBGDH88YiiUKDT8BhoVFTApQbloY1ttPXWv 1M5kfT2tqh2yrrhWfAyfg4iPQ5jvAmZzMftoKWnaWg==
X-Google-Smtp-Source: AIpwx4+Gcd5prdgRXF8Pk4+BOepsuNk2oNzoHn9TmU2FYDgpLzhdRFiZ0Tu0VBYKhWU517Lc3xlWkCZF2+x/UPCdGdY=
X-Received: by 2002:a9d:23f6:: with SMTP id t109-v6mr1245006otb.44.1524056001744;  Wed, 18 Apr 2018 05:53:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Wed, 18 Apr 2018 05:52:41 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 18 Apr 2018 05:52:41 -0700
Message-ID: <CABcZeBOSQZVzjQvAs5syEDQ9bZ1y95yNoDy2-spH4-D8gmvU6A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  "mmusic@ietf.org" <mmusic@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009a5c22056a1ef028"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/yix0AE5VF74wBv8wiz_GFOGqrhw>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 12:53:24 -0000

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

On Wed, Apr 18, 2018 at 12:23 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Nits
> =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> General:
>
> >>>> I agree with EKR that the use of "address:port" is cumbersome. For t=
he
> >>>> places where this is not a stand-in for the term "'m=3D' section", I
> would
> >>>> suggest that the well-known term "3-tuple" would serve the purpose i=
n
> a much more
> >>>> readable way.
> >>>
> >>> I personally have nothing against '3-tuple', =C5=92transport' (sugges=
ted by
> >>> Taylor at some point), etc.
> >>>
> >>> The problem is that whenever I change the terminology someone later
> >>> wants something else, and then I again have to change it.
> >>
> >> Well, we're at IESG review now, so this is the last round.
> >>
> >> Who, specifically, is in favor of the current terminology?
> >
> > I see it more as terminology that people in the WG could live with.
> >
> > This doesn't answer my question. Who, specifically, thinks that this
> terminology
> > of focusing on the address:port and not the m=3D section is good?
>
> Considering that the focus has been on the address and port since day one=
,
> for 7 years, I think it is good.


Yes, who besides you? Because in the text above your argument is that if we
change it, then you will
have to change it again because someone else will object. That's different
from *you* disagreeing


After all, while there is more to it than the address:port, the main reason
> for BUNDLE is to be able to multiplex in a single address:port.
>

Perhaps, but not necessarily the one in the m=3D line, because of ICE.

-Ekr

--0000000000009a5c22056a1ef028
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, Apr 18, 2018 at 12:23 AM, 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"><span><br>
Hi,<br>
<br>
=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<wbr>=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<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
Nits<br>
=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<wbr>=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<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
<br>
General:<br>
<br>
&gt;&gt;&gt;&gt; I agree with EKR that the use of &quot;address:port&quot; =
is cumbersome. For the<br>
&gt;&gt;&gt;&gt; places where this is not a stand-in for the term &quot;&#3=
9;m=3D&#39; section&quot;, I would<br>
&gt;&gt;&gt;&gt; suggest that the well-known term &quot;3-tuple&quot; would=
 serve the purpose in a much more<br>
&gt;&gt;&gt;&gt; readable way.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I personally have nothing against &#39;3-tuple&#39;, =C5=92tra=
nsport&#39; (suggested by<br>
&gt;&gt;&gt; Taylor at some point), etc.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The problem is that whenever I change the terminology someone =
later<br>
&gt;&gt;&gt; wants something else, and then I again have to change it.<br>
&gt;&gt;<br>
&gt;&gt; Well, we&#39;re at IESG review now, so this is the last round.<br>
&gt;&gt;<br>
&gt;&gt; Who, specifically, is in favor of the current terminology?<br>
&gt;<br>
&gt; I see it more as terminology that people in the WG could live with.<br=
>
&gt;<br>
&gt; This doesn&#39;t answer my question. Who, specifically, thinks that th=
is terminology<br>
&gt; of focusing on the address:port and not the m=3D section is good?<br>
<br>
</span>Considering that the focus has been on the address and port since da=
y one, for 7 years, I think it is good. </blockquote><div><br></div><div>Ye=
s, who besides you? Because in the text above your argument is that if we c=
hange it, then you will</div><div>have to change it again because someone e=
lse will object. That&#39;s different from *you* disagreeing<br></div><div>=
<br></div><div> <br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">After all, while t=
here is more to it than the address:port, the main reason for BUNDLE is to =
be able to multiplex in a single address:port.<br></blockquote><div><br></d=
iv><div>Perhaps, but not necessarily the one in the m=3D line, because of I=
CE.</div><div><br></div><div>-Ekr</div><div><br></div></div></div></div>

--0000000000009a5c22056a1ef028--


From nobody Wed Apr 18 07:31:09 2018
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 4DD9C12E88B for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 07:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zoac_rJOkdRk for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 07:30: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 D564F12DA29 for <mmusic@ietf.org>; Wed, 18 Apr 2018 07:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524061843; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=HaDxHYx9UIqBDNLNgirp4eKnZfgkE9wJbsnNuGS3WbU=; b=Ey9xI1PhCt8sPCwPPZAtPU19kJw3pF0lZw3ZMFOdV2jhHphvPEbdKCGozOUnTUa1 Zv4N9B92AmtJmT1DmOJkfXL9nr5pFeqVG6hEC8tkU+FsG0CJiSgCCaGWN4OWmQgu OYTUXlt0lWMzTNUYe9UAp+WrgwvnZc4gm/jhDaBrQrM=;
X-AuditID: c1b4fb2d-82dff70000003563-f2-5ad7569239bb
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 6A.86.13667.29657DA5; Wed, 18 Apr 2018 16:30:43 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0382.000; Wed, 18 Apr 2018 16:30:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
Thread-Index: AQHT1lZf0qxFmZgCwkeSofFpx7VVFKQFQviAgADjodCAADKqAIAATwsA
Date: Wed, 18 Apr 2018 14:30:42 +0000
Message-ID: <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com>
In-Reply-To: <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D6FD2AE52E4F5christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGIsWRmVeSWpSXmKPExsUyM2J7uO7ksOtRBp8fcFtMn/WOzWLF63Ps Fu8v6FrM+DOR2eL8zvVMFlOXP2ZxYPOY8nsjq8eSJT+ZPCY/bmMOYI7isklJzcksSy3St0vg yrh6+wRrweR3jBV/3q9hbGDcdIyxi5GTQ0LARGL10k3MXYxcHEICRxglpk34wg7hLGaU+PZ2 AmsXIwcHm4CFRPc/bZAGEQEFiV9/TrCA1DALTGCSuPp3NStIQligVmLzz2MsEEV1EgsWH2aC sN0kDk66ygwyh0VAVaJ1Gg9ImFfAWmLK6atsELvmM0mc+rIBrJ5TIFDi7Nmn7CA2o4CYxPdT a8DizALiEreezGeCuFpAYsme88wQtqjEy8f/wG4QFdCT2HDiNjvILgkBJYnbG5wgWhMkWqd+ YILYKyhxcuYTlgmMorOQTJ2FpGwWkjKIuIHE+3PzmSFsbYllC19D2foSG7+cZYSwrSXuLjnH iqxmASPHKkbR4tTi4tx0I2O91KLM5OLi/Dy9vNSSTYzA2D245bfuDsbVrx0PMQpwMCrx8N5w uB4lxJpYVlyZe4hRgoNZSYR35+MrUUK8KYmVValF+fFFpTmpxYcYpTlYlMR59VbtiRISSE8s Sc1OTS1ILYLJMnFwSjUwir9/ljl1e+1uyb8Ln88/fm3uLavGH//CVxvO3r6bcUfMTg7Xp9LW DTUX0lTdO8Q9d5+6yLrSPufdhd3V5tZBQS55t6XvTTlycXtC+ym3PT8Djp/TX/vwTrDnzkkX Tn3i4ZPPq5XcvODw5Yq/Kd6cxiXfOuU+XPzgJ3ahrTlg7QI2YbNl9cYMnUosxRmJhlrMRcWJ ANdEOcbZAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DVDAnmNUw3dNE3WsmucjdH0qyxg>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 14:31:02 -0000

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

Hi,

>>>>> o  Bundled media: All media associated with a given BUNDLE group.
>>>>>
>>>>> o  Initial offer: The first offer, within an SDP session (e.g. a
>>>>>     SIP dialog when the Session Initiation Protocol (SIP) [RFC3261] i=
s
>>>>>     used to carry SDP), in which the offerer indicates that it wants
>>>>>     to create a given BUNDLE group.
>>>>
>>>> This is a very idiosyncratic definition, because it's *not* the first
>>>> offer in the session, but the one where the BUNDLE group is
>>>> introduced. Given that 3264 has a different meaning for this same
>>>> term, and the difference is critical, I would strongly urge you to
>>>> pick a different term.
>>>
>>> I believe there are other drafts with similar definitions of "Initial O=
ffer".
>>>
>> Perhaps, but as I noted, 3264s disagrees.
>>
>> Anyway, would something like "Initial BUNDLE offer" be better?
>>
>> Not really.
>>
>> So, what do you suggest?
>>
>> Note that, for most SDP extensions I can think of, "initial offer" refer=
s to the offer where you actually start using the extension (explicitly or =
implicitly).
>>
>> But that's not the case here, because this is the one for this BUNDLE gr=
oup, not for BUNDLE as a whole
>>
> I'm not sure you need a specific term here. How often do you use it?

It=92s based on the generic structure that MMUSIC has defined for the O/A p=
rocedures of new attributes:

  *   Generating initial offer
  *   Generating answer
  *   Modifying the session

Sure, we could use a structure like:

  *   Creating BUNDLE group
     *   Generating offer
     *   Generating answer
  *   Modifying BUNDLE group
     *   Generating offer
        *   Add/remove m- section etc
     *   Generating answer
        *   Add/remove m- section etc

=85where the focus would be on whether a bundle group is created or modifie=
d, without caring about whether it=92s the initial offer of the session or =
not.

But, we would not be using the generic O/A structure.

---

>>>>>> The BUNDLE extension is indicated using an SDP 'group' attribute
>>>>>> with a semantics value [RFC5888] of "BUNDLE".  An identification-tag=
 is
>>>>>> assigned to each bundled "m=3D" section, and each identification-tag
>>>>>> is listed in the SDP 'group:BUNDLE' attribute identification-tag lis=
t.
>>>>>> Each "m=3D" section whose identification-tag is listed in the
>>>>>> identification-tag list is associated with a given BUNDLE group.
>>>>>
>>>>> How about "is part of" instead of "associated with"
>>>>>
>>>>> There are most likely other instances that would have to be fixed, an=
d I'd like to try to maintain consistent terminology.
>>>>
>>> Yes, I would change all of them.
>>>
>>> I have a quick look, and I am not sure we can change all instances of "=
associated with" to "is part of".
> Yes, quite possibly, but that's an argument against using "associated" in=
 this way. Find a set of more specific terms and use them.
>>>>> Each "m=3D" section whose identification-tag is listed in the
>>>>> identification-tag list is associated with a given BUNDLE group.
>>>>
>>>> SDP bodies can contain multiple BUNDLE groups.  Any given bundled
>>>> "m=3D" section MUST NOT be associated with more than one BUNDLE group
>>>> at any given time.
>>>>
>>>> Again "part of"
>>>
>>> There are multiple instances of "associated with BUNDLE group" terminol=
ogy throughout the document.
>>>
>>> Yes, and they're all bad.
>>
>> Why?
>
> Because it's a generic term when specific ones would be better

How do I know in which cases to use something more =93specific=94?

For example:

 "media associated with the BUNDLE group": Is media part of the group? Or, =
is there some other more specific word to use?

 "identification-tag list is associated with a given BUNDLE group": Is the =
list part of the group? Or, is there some other more specific word to use?

 "The c=3D line net type value associated with  the bundled m=3D section=94=
: Is the c=3D line part of the m=3D section? I don=92t think so =96 at leas=
t not in case of a session-level c=3D line.

Etc=85

---

>>>>>> If the answer contains a BUNDLE group, the answerer MUST:
>>>>>>
>>>>>> o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
>>>>>>
>>>>>> o  Select an answerer BUNDLE address:port [Section 8.3.2].
>>>>>
>>>>> This isn't right, because each BUNDLE group has its own address:port,
>>>>> so instead "For each BUNDLE group" contained in the offer.
>>>>
>>>> The procedures is for individual BUNDLE groups, as indicated in Sectio=
n 8:
>>>>
>>>> "SDP offers and answers can contain multiple BUNDLE groups.  The
>>>>  procedures in this section apply independently to a given BUNDLE
>>>>  group."'
>>>
>>> I don't find this very clear.
>>
>> I am not sure adding "For each BUNDLE group" all over (it would be neede=
d in more places than indicated above) would make it better.
>>
>> So, my preference would be to work on the clarification text above, if y=
ou think it needs to be more clear.
>
> I'm not sure how to fix this. Perhaps it needs a real rewrite

What needs a rewrite?

---

>>>>> More importantly, it's not the address:port that the answerer chooses=
,
>>>>> but rather the m=3D section. I.e.,
>>>>>
>>>>> o Determine the first m=3D section in the BUNDLE group which will be
>>>>>   BUNDLEd in the answer
>>>>> o Select an answerer BUNDLE address:port
>>>>
>>>> I don't understand what "first m=3D section which will be BUNDLEd" mea=
ns. What is "first"?
>>>>
>>> The one indicated by the bundle tag.
>>
>> In my ears "First" seems to reference the order of the "m=3D" section in=
 the SDP, but the bundle tag can indicate any of the "m=3D" sections.
>
> Sure. I'm not suggesting text in this specific case, I'm trying to provid=
e a structure that explains what's going on

Ok.

---

>>>>>> o  The answerer will not reject the "m=3D" section [Section 8.3.4];
>>>>>>     and
>>>>>>
>>>>>> o  The "m=3D" section does not contain a zero port value.
>>>>>>
>>>>>> If all of the criteria above are fulfilled, the answerer MUST select
>>>>> the suggested offerer BUNDLE address:port.
>>>>>
>>>> Again, this isn't selecting the address:port but rather the m=3Dsectio=
n
>>>>
>>> Sure, but it picks the address:port of that selected m=3D section.
>>>
>>> No, it picks the m=3D section and then uses the attached address:port.
>>
>> I don't disagree.
>
> Right, but the document throughout (see my other email about trickle) act=
s like its the address that is the key

Even though trickle is a special case, I get your point. I assume the usage=
 of address:port is because that is what triggered the work in the first pl=
ace. Later we added the procedures regarding other parts (SDP attributes et=
c).

---

>>>>> bundled "m=3D" section the answerer MUST assign a zero port value and
>>>>> include an SDP 'bundle-only' attribute.
>>>>>
>>>>> The answerer MUST NOT assign an answerer BUNDLE address:port to an
>>>>> "m=3D" section that is not within the BUNDLE group, or to an "m=3D=93
>>>>> section that is within another BUNDLE group.
>>>>>
>>>>> This repeats text in S 8.3.
>>>>
>>>> What text do you think is repeated?
>>>
>>> 8.3. already says you can't move between BUNDLE groups.
>>
>> Ok, but I don't think that covers the fact that you can't assign the add=
ress:port to an m=3D section that isn't part of a BUNDLE group.
>
> Sure, so state the rules in one place

I will look into it.

---

>>>>>>   8.4.  Offerer Processing of the SDP Answer
>>>>>>
>>>>>      When an offerer receives an answer, if the answer contains a BUN=
DLE
>>>>>      group, the offerer MUST check that any bundled "m=3D" section in=
 the
>>>>>      answer was indicated as bundled in the corresponding offer.  If
>>>>>      there is no mismatch, the offerer MUST use the offerer BUNDLE
>>>>>      address:port,
>>>>>
>>>>> address:port, again. It's the m=3Dsection that's relevant.
>>>>
>>>> Yes, but it uses the address:port of the m=3D section.
>>>>
>>>> What do you suggest to say instead?
>>>
>>> "MUST use the indicated m=3D section as the bundle <whatever term we ch=
oose>"
>>
>> "bundle m- section" would be a straight forward choice. However, that is=
 very similar to "bundled m- section", which refers to any m- section withi=
n a BUNDLE group...
>
> When Adam and I were talking yesterday he suggested "lead" m=3D section.

Ok.

---

>>>>> When the offerer generates a subsequent offer, the offerer
>>>>> BUNDLE-tag MUST represent the bundled "m=3D" section to which the off=
erer BUNDLE
>>>>> address:port (previously negotiated or newly suggested) has been assi=
gned.
>>>>>
>>>>> 8.5.1.  Suggesting a New Offerer BUNDLE Address:Port
>>>>
>>>> Again it would make more sense to describe this as suggesting a new m=
=3D section.
>>>>
>>>> It does not have to be a new "m=3D" section. The new address:port can =
be assigned to an existing "m=3D" section.
>>>
>>> You're suggesting that a new m=3D section be the one that things are bu=
ndled into.
>>>
>> Not necessarily. The new address:port is assigned to *a* bundled m=3D se=
ction, which could be the *same* m=3D section currently used to bundle thin=
gs into.
>
> Sure, but again, it's not the address:port that's being suggested, it's i=
ts parameters

Well, in this particular case, the text is about changing the address:port.

But, even if we change that and talk about parameters, it still doesn=92t h=
ave to be a new m=3D section. You can modify the parameters of the existing=
 bundle/lead/whatever m=3D section.

---

Regards,

Christer



--_000_D6FD2AE52E4F5christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <784E8A5C7EB5AD44B8AC80EFF0B2E2D0@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>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt; o&nbsp; Bundled media: All media=
 associated with a given BUNDLE group.<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;<br>
&gt;&gt;&gt;&gt;&gt; o&nbsp; Initial offer: The first offer, within an SDP =
session (e.g. a<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp;SIP dialog when the Session Initiat=
ion Protocol (SIP) [RFC3261] is<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp;used to carry SDP), in which the of=
ferer indicates that it wants<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp;to create a given BUNDLE group.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; This is a very idiosyncratic definition, because it's *not=
* the first<br>
&gt;&gt;&gt;&gt; offer in the session, but the one where the BUNDLE group i=
s<br>
&gt;&gt;&gt;&gt; introduced. Given that 3264 has a different meaning for th=
is same<br>
&gt;&gt;&gt;&gt; term, and the difference is critical, I would strongly urg=
e you to<br>
&gt;&gt;&gt;&gt; pick a different term.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I believe there are other drafts with similar definitions of &=
quot;Initial Offer&quot;.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Perhaps, but as I noted, 3264s disagrees.<br>
&gt;&gt;<br>
&gt;&gt; Anyway, would something like &quot;Initial BUNDLE offer&quot; be b=
etter?<br>
&gt;&gt;<br>
&gt;&gt; Not really.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; So, what do you suggest?</div>
<div>&gt;&gt;</div>
<div>&gt;&gt; Note that, for most SDP extensions I can think of, &quot;init=
ial offer&quot; refers to the offer where you actually start using the exte=
nsion (explicitly or implicitly).
</div>
<div>&gt;&gt;</div>
<div>&gt;&gt; But that's not the case here, because this is the one for thi=
s BUNDLE group, not for BUNDLE as a whole<br>
</div>
<div>&gt;&gt;</div>
<div>&gt; I'm not sure you need a specific term here. How often do you use =
it?</div>
</div>
</div>
</div>
</span>
<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;">
It=92s based on the generic structure that MMUSIC has defined for the O/A p=
rocedures of new attributes:</div>
<ul style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li>Generating initial offer</li><li>Generating answer</li><li>Modifying th=
e session&nbsp;</li></ul>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Sure, we could use a structure like:</div>
<ul style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-si=
ze: 14px;">
<li>Creating BUNDLE group
<ul>
<li>Generating offer</li><li>Generating answer</li></ul>
</li><li>Modifying BUNDLE group
<ul>
<li>Generating offer
<ul>
<li>Add/remove m- section etc</li></ul>
</li><li>Generating answer
<ul>
<li>Add/remove m- section etc</li></ul>
</li></ul>
</li></ul>
<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;">
=85where the focus would be on whether a bundle group is created or modifie=
d, without caring about whether it=92s the initial offer of the session or =
not.</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;">
But, we would not be using the generic O/A structure.</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;">
---</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt;&gt; The BUNDLE extension is indi=
cated using an SDP 'group' attribute<br>
&gt;&gt;&gt;&gt;&gt;&gt; with a semantics value [RFC5888] of &quot;BUNDLE&q=
uot;.&nbsp; An identification-tag is<br>
&gt;&gt;&gt;&gt;&gt;&gt; assigned to each bundled &quot;m=3D&quot; section,=
 and each identification-tag<br>
&gt;&gt;&gt;&gt;&gt;&gt; is listed in the SDP 'group:BUNDLE' attribute iden=
tification-tag list.<br>
&gt;&gt;&gt;&gt;&gt;&gt; Each &quot;m=3D&quot; section whose identification=
-tag is listed in the<br>
&gt;&gt;&gt;&gt;&gt;&gt; identification-tag list is associated with a given=
 BUNDLE group.<br>
&gt;&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; How about &quot;is part of&quot; instead of &quot;asso=
ciated with&quot;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; There are most likely other instances that would have =
to be fixed, and I'd like to try to maintain consistent terminology.
<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; Yes, I would change all of them.<br>
&gt;&gt;&gt;</span></div>
<div>&gt;&gt;&gt; I have a quick look, and I am not sure we can change all =
instances of &quot;associated with&quot; to &quot;is part of&quot;.</div>
<div>&gt; Yes, quite possibly, but that's an argument against using &quot;a=
ssociated&quot; in this way. Find a set of more specific terms and use them=
.</div>
</div>
</div>
</div>
</div>
</div>
</span><span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font=
-family: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt; Each &quot;m=3D&quot; section wh=
ose identification-tag is listed in the<br>
&gt;&gt;&gt;&gt;&gt; identification-tag list is associated with a given BUN=
DLE group.<br>
&gt;&gt;&gt;&gt;&nbsp; &nbsp;<br>
&gt;&gt;&gt;&gt; SDP bodies can contain multiple BUNDLE groups.&nbsp; Any g=
iven bundled<br>
&gt;&gt;&gt;&gt; &quot;m=3D&quot; section MUST NOT be associated with more =
than one BUNDLE group<br>
&gt;&gt;&gt;&gt; at any given time.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Again &quot;part of&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There are multiple instances of &quot;associated with BUNDLE g=
roup&quot; terminology throughout the document.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Yes, and they're all bad.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; Why?</div>
<div>&gt;</div>
<div>&gt; Because it's a generic term when specific ones would be better</d=
iv>
</div>
</div>
</div>
</div>
</div>
</span>
<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;">
How do I know in which cases to use something more =93specific=94?</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;">
For example:</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;">
<span style=3D"font-size: medium; orphans: 2; widows: 2;">&nbsp;&quot;</spa=
n>media associated with the BUNDLE group<span style=3D"font-size: medium; o=
rphans: 2; widows: 2;">&quot;</span>: Is media part of the group? Or, is th=
ere some other more specific word to use?</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">&nb=
sp;&quot;</font><span style=3D"color: rgb(0, 0, 0); font-family: Calibri, s=
ans-serif; font-size: 14px; orphans: 2; white-space: pre-wrap; widows: 2;">=
identification-tag list is associated with a given
 BUNDLE group</span><span style=3D"font-family: Calibri, sans-serif;">&quot=
;</span><font face=3D"Calibri,sans-serif"><span style=3D"white-space: pre-w=
rap;">:
</span></font><font face=3D"Calibri,sans-serif"><span style=3D"white-space:=
 pre-wrap;">Is the list part of the group? Or, is there some other more spe=
cific word to use?</span></font></div>
<div><br>
</div>
<div style=3D"orphans: 2; widows: 2; ">&nbsp;<span style=3D"font-family: Ca=
libri, sans-serif; orphans: 2; widows: 2;">&quot;</span>The c=3D line net t=
ype value associated with &nbsp;the bundled m=3D section<span style=3D"orph=
ans: 2; widows: 2;"><font face=3D"Calibri,sans-serif">=94:&nbsp;</font></sp=
an>Is
 the c=3D line part of the m=3D section? I don=92t think so =96 at least no=
t in case of a session-level c=3D line.</div>
<div><br>
</div>
<div>Etc=85</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>---</div>
<div>&nbsp;</div>
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt;&gt; If the answer contains a BUN=
DLE group, the answerer MUST:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;<br>
&gt;&gt;&gt;&gt;&gt;&gt; o&nbsp; Select an offerer BUNDLE address:port [Sec=
tion 8.3.1]; and<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;<br>
&gt;&gt;&gt;&gt;&gt;&gt; o&nbsp; Select an answerer BUNDLE address:port [Se=
ction 8.3.2].<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; This isn't right, because each BUNDLE group has its ow=
n address:port,<br>
&gt;&gt;&gt;&gt;&gt; so instead &quot;For each BUNDLE group&quot; contained=
 in the offer.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The procedures is for individual BUNDLE groups, as indicat=
ed in Section 8:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&nbsp;&quot;SDP offers and answers can contain multiple BUN=
DLE groups.&nbsp; The<br>
&gt;&gt;&gt;&gt;&nbsp; procedures in this section apply independently to a =
given BUNDLE<br>
&gt;&gt;&gt;&gt;&nbsp; group.&quot;'&nbsp;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don't find this very clear.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; I am not sure adding &quot;For each BUNDLE group&quot; all ov=
er (it would be needed in more places than indicated above) would make it b=
etter.</div>
<div>&gt;&gt;</div>
<div>&gt;&gt; So, my preference would be to work on the clarification text =
above, if you think it needs to be more clear.</div>
<div>&gt;</div>
<div>&gt; I'm not sure how to fix this. Perhaps it needs a real rewrite </d=
iv>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>What needs a rewrite?</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt; More importantly, it's not the a=
ddress:port that the answerer chooses,<br>
&gt;&gt;&gt;&gt;&gt; but rather the m=3D section. I.e.,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; o Determine the first m=3D section in the BUNDLE group=
 which will be<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;BUNDLEd in the answer<br>
&gt;&gt;&gt;&gt;&gt; o Select an answerer BUNDLE address:port<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I don't understand what &quot;first m=3D section which wil=
l be BUNDLEd&quot; means. What is &quot;first&quot;?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; The one indicated by the bundle tag.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; In my ears &quot;First&quot; seems to reference the order of =
the &quot;m=3D&quot; section in the SDP, but the bundle tag can indicate an=
y of the &quot;m=3D&quot; sections.</div>
<div>&gt;</div>
<div>&gt; Sure. I'm not suggesting text in this specific case, I'm trying t=
o provide a structure that explains what's going on<br>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Ok.</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span class=3D""><br>
---<br>
<br>
&gt;&gt;&gt;&gt;&gt;&gt; o&nbsp; The answerer will not reject the &quot;m=
=3D&quot; section [Section 8.3.4];<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp;and<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; o&nbsp; The &quot;m=3D&quot; section does not cont=
ain a zero port value.<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; If all of the criteria above are fulfilled, the an=
swerer MUST select<br>
&gt;&gt;&gt;&gt;&gt; the suggested offerer BUNDLE address:port.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Again, this isn't selecting the address:port but rather th=
e m=3Dsection<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; Sure, but it picks the address:port of that selected m=3D sect=
ion.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; No, it picks the m=3D section and then uses the attached addre=
ss:port.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; I don't disagree.</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div>&gt;</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>&gt; Right, but the document throughout (see my other email about tric=
kle) acts like its the address that is the key
</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Even though trickle is a special case, I get your point. I assume the =
usage of address:port is because that is what triggered the work in the fir=
st place. Later we added the procedures regarding other parts (SDP attribut=
es etc).</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt; bundled &quot;m=3D&quot; section=
 the answerer MUST assign a zero port value and<br>
&gt;&gt;&gt;&gt;&gt; include an SDP 'bundle-only' attribute.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; The answerer MUST NOT assign an answerer BUNDLE addres=
s:port to an<br>
&gt;&gt;&gt;&gt;&gt; &quot;m=3D&quot; section that is not within the BUNDLE=
 group, or to an &quot;m=3D=93<br>
&gt;&gt;&gt;&gt;&gt; section that is within another BUNDLE group.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; This repeats text in S 8.3.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; What text do you think is repeated?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; 8.3. already says you can't move between BUNDLE groups.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; Ok, but I don't think that covers the fact that you can't ass=
ign the address:port to an m=3D section that isn't part of a BUNDLE group.<=
/div>
</div>
</div>
</div>
</div>
</div>
</span>
<div>&gt;</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>&gt; Sure, so state the rules in one place<br>
</div>
<div>&nbsp;</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div>I will look into it.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;8.4.&nbsp; Offerer Processing of =
the SDP Answer<span class=3D""></span></div>
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; When an offerer receives an answer=
, if the answer contains a BUNDLE<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; group, the offerer MUST check that=
 any bundled &quot;m=3D&quot; section in the<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; answer was indicated as bundled in=
 the corresponding offer.&nbsp; If<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; there is no mismatch, the offerer =
MUST use the offerer BUNDLE<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; address:port,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; address:port, again. It's the m=3Dsection that's relev=
ant.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Yes, but it uses the address:port of the m=3D section.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; What do you suggest to say instead?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; &quot;MUST use the indicated m=3D section as the bundle &lt;wh=
atever term we choose&gt;&quot;<br>
&gt;&gt;</span></div>
<div>&gt;&gt; &quot;bundle m- section&quot; would be a straight forward cho=
ice. However, that is very similar to &quot;bundled m- section&quot;, which=
 refers to any m- section within a BUNDLE group...</div>
<div>&gt;</div>
<div>&gt; When Adam and I were talking yesterday he suggested &quot;lead&qu=
ot; m=3D section. </div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Ok.</div>
<div><br>
</div>
<div>---</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div><span class=3D"">&gt;&gt;&gt;&gt;&gt; When the offerer generates a sub=
sequent offer, the offerer<br>
&gt;&gt;&gt;&gt;&gt; BUNDLE-tag MUST represent the bundled &quot;m=3D&quot;=
 section to which the offerer BUNDLE<br>
&gt;&gt;&gt;&gt;&gt; address:port (previously negotiated or newly suggested=
) has been assigned.<br>
&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp;<br>
&gt;&gt;&gt;&gt;&gt; 8.5.1.&nbsp; Suggesting a New Offerer BUNDLE Address:P=
ort<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Again it would make more sense to describe this as suggest=
ing a new m=3D section.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; It does not have to be a new &quot;m=3D&quot; section. The=
 new address:port can be assigned to an existing &quot;m=3D&quot; section.<=
br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; You're suggesting that a new m=3D section be the one that thin=
gs are bundled into.<br>
&gt;&gt;&gt;</span></div>
<div>&gt;&gt; Not necessarily. The new address:port is assigned to *a* bund=
led m=3D section, which could be the *same* m=3D section currently used to =
bundle things into.</div>
<div>&gt;</div>
<div>&gt; Sure, but again, it's not the address:port that's being suggested=
, it's its parameters</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>Well, in this particular case, the text is about changing the address:=
port.</div>
<div><br>
</div>
<div>But, even if we change that and talk about parameters, it still doesn=
=92t have to be a new m=3D section. You can modify the parameters of the ex=
isting bundle/lead/whatever m=3D section.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_D6FD2AE52E4F5christerholmbergericssoncom_--


From nobody Wed Apr 18 07:46:46 2018
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 C587E12D872 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 07:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmJSYsVHJN_Y for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 07:46:43 -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 4359E12D870 for <mmusic@ietf.org>; Wed, 18 Apr 2018 07:46:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524062799; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=fCb+ySpw9SXHL1ObYZIMujC3lMxw3ZQpLFeOJfKn8dk=; b=QgqEJsJw86ZEcKLp+Cq2+4RQBQO8QBbZnuOsOYXBQ3kGBTI9/LLZ3eegO3HDFlQw QSmVoyLH+x/WwI6m+jCY5npaSuqGNZd8bkmkAymYe/Qzxu7HeMJTNp/5sU5eBxga bojTWnZ+DxCUi7YZHlHsi8X0lDAkFyq1kXe3KM2nYrI=;
X-AuditID: c1b4fb25-c69d49c000006561-24-5ad75a4f5bb3
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 56.B1.25953.F4A57DA5; Wed, 18 Apr 2018 16:46:39 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0382.000; Wed, 18 Apr 2018 16:46:05 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseCAAD7vgIAAUomA
Date: Wed, 18 Apr 2018 14:46:04 +0000
Message-ID: <D6FD31FF.2E536%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <CABcZeBOSQZVzjQvAs5syEDQ9bZ1y95yNoDy2-spH4-D8gmvU6A@mail.gmail.com>
In-Reply-To: <CABcZeBOSQZVzjQvAs5syEDQ9bZ1y95yNoDy2-spH4-D8gmvU6A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D6FD31FF2E536christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNIsWRmVeSWpSXmKPExsUyM2K7tK5/1PUogzVTDCz2/F3EbjF91js2 ixWvz7FbvL+gazHjz0Rmi/M71zNZTF3+mMWB3WPK742sHkuW/GTymLXzCYvH5MdtzAEsUVw2 Kak5mWWpRfp2CVwZC94sYCy4Yl7xddFJxgbGVrMuRk4OCQETiYvfr7N1MXJxCAkcYZR48XYG K4SzmFFi+48PzF2MHBxsAhYS3f+0QRpEBBQkfv05wQJSwyywnkli0enLrCAJYYF0iRsPFrGA 1IsIZEjcf5AJUR8l8eLfVnYQm0VAVaL7zlYmEJtXwFqi5+5qZohdp5glFr5+BpbgFAiU6Hje CGYzCohJfD+1BsxmFhCXuPVkPhPE1QISS/acZ4awRSVePv4HdoOogJ7EhhO32UFukBBQkri9 wQnEZBZIkJjyuABiraDEyZlPWCYwis5CMnQWQtUsJFUQYU2J9bv0IaoVJaZ0P2SHsDUkWufM hbKtJf7d6mBCVrOAkWMVo2hxanFSbrqRsV5qUWZycXF+nl5easkmRmAUH9zyW3UH4+U3jocY BTgYlXh4bzpcjxJiTSwrrsw9xCjBwawkwrvz8ZUoId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwP zTdHCQmkJ5akZqemFqQWwWSZODilGhijPjC6vFvWvXgD03GVdvO4KdxNfRndLZavc7tKPphc 28XrMiemIiFuduGSxR2xt21PsRkX5W2z86rXsal4oFD8lzFDsTjhZeRNqbVb+pctXuRpx+15 4sJZPtMetws5dfbPJE9O2bXM8evr69rndx/7/FO2b1LqzhtH+Go/HD8Z3vas9/GVB5xKLMUZ iYZazEXFiQD8Pz5b3gIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7H8PIAGoeyB4cqeWS-zM_-yXTHE>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 14:46:45 -0000

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

SGksDQoNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PQ0KTml0cw0KPT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoNCkdl
bmVyYWw6DQoNCj4+Pj4+PiBJIGFncmVlIHdpdGggRUtSIHRoYXQgdGhlIHVzZSBvZiAiYWRkcmVz
czpwb3J0IiBpcyBjdW1iZXJzb21lLiBGb3IgdGhlDQo+Pj4+Pj4gcGxhY2VzIHdoZXJlIHRoaXMg
aXMgbm90IGEgc3RhbmQtaW4gZm9yIHRoZSB0ZXJtICInbT0nIHNlY3Rpb24iLCBJIHdvdWxkDQo+
Pj4+Pj4gc3VnZ2VzdCB0aGF0IHRoZSB3ZWxsLWtub3duIHRlcm0gIjMtdHVwbGUiIHdvdWxkIHNl
cnZlIHRoZSBwdXJwb3NlIGluIGEgbXVjaCBtb3JlDQo+Pj4+Pj4gcmVhZGFibGUgd2F5Lg0KPj4+
Pj4NCj4+Pj4+IEkgcGVyc29uYWxseSBoYXZlIG5vdGhpbmcgYWdhaW5zdCAnMy10dXBsZScsIMWS
dHJhbnNwb3J0JyAoc3VnZ2VzdGVkIGJ5DQo+Pj4+PiBUYXlsb3IgYXQgc29tZSBwb2ludCksIGV0
Yy4NCj4+Pj4NCj4+Pj4gVGhlIHByb2JsZW0gaXMgdGhhdCB3aGVuZXZlciBJIGNoYW5nZSB0aGUg
dGVybWlub2xvZ3kgc29tZW9uZSBsYXRlcg0KPj4+IHdhbnRzIHNvbWV0aGluZyBlbHNlLCBhbmQg
dGhlbiBJIGFnYWluIGhhdmUgdG8gY2hhbmdlIGl0Lg0KPj4+DQo+Pj4gV2VsbCwgd2UncmUgYXQg
SUVTRyByZXZpZXcgbm93LCBzbyB0aGlzIGlzIHRoZSBsYXN0IHJvdW5kLg0KPj4+DQo+Pj4gV2hv
LCBzcGVjaWZpY2FsbHksIGlzIGluIGZhdm9yIG9mIHRoZSBjdXJyZW50IHRlcm1pbm9sb2d5Pw0K
Pj4NCj4+IEkgc2VlIGl0IG1vcmUgYXMgdGVybWlub2xvZ3kgdGhhdCBwZW9wbGUgaW4gdGhlIFdH
IGNvdWxkIGxpdmUgd2l0aC4NCj4+DQo+Pj4gVGhpcyBkb2Vzbid0IGFuc3dlciBteSBxdWVzdGlv
bi4gV2hvLCBzcGVjaWZpY2FsbHksIHRoaW5rcyB0aGF0IHRoaXMgdGVybWlub2xvZ3kNCj4+PiBv
ZiBmb2N1c2luZyBvbiB0aGUgYWRkcmVzczpwb3J0IGFuZCBub3QgdGhlIG09IHNlY3Rpb24gaXMg
Z29vZD8NCj4+DQo+PiBDb25zaWRlcmluZyB0aGF0IHRoZSBmb2N1cyBoYXMgYmVlbiBvbiB0aGUg
YWRkcmVzcyBhbmQgcG9ydCBzaW5jZSBkYXkgb25lLCBmb3IgNyB5ZWFycywgSSB0aGluayBpdCBp
cyBnb29kLg0KPg0KPiBZZXMsIHdobyBiZXNpZGVzIHlvdT8NCg0KQXMgdGhlIE1NVVNJQyBXRyBk
ZWNpZGVkIHRvIG1vdmUgdGhlIGRvY3VtZW50IGZvcndhcmQsIEkgYXNzdW1lIHRoYXQgdGhlIGlu
dGVyZXN0ZWQgcGFydGllcyB0aGluayBpdOKAmXMgYXQgbGVhc3QgZ29vZCBlbm91Z2guDQoNCj4g
QmVjYXVzZSBpbiB0aGUgdGV4dCBhYm92ZSB5b3VyIGFyZ3VtZW50IGlzIHRoYXQgaWYgd2UgY2hh
bmdlIGl0LCB0aGVuIHlvdSB3aWxsIGhhdmUgdG8gY2hhbmdlIGl0IGFnYWluIGJlY2F1c2Ugc29t
ZW9uZSBlbHNlIHdpbGwgb2JqZWN0Lg0KDQpDb25zaWRlcmluZyB0aGUgaGlzdG9yeSBvZiB0aGlz
IGRyYWZ0LCBhbmQgYWxsIHRoZSByZS13cml0ZXMsIGFzIGF1dGhvciBJIHRoaW5rIHRoYXQgaXMg
YSBmYWlyIGFyZ3VtZW50IDopDQoNCkhhdmluZyBzYWlkIHRoYXQsIEkgd2lsbCBvZiBjb3Vyc2Ug
aW1wbGVtZW50IHdoYXRldmVyIHRoZSBjb21tdW5pdHkgZGVjaWRlcy4NCg0KUmVnYXJkcywNCg0K
Q2hyaXN0ZXINCg0KDQo=

--_000_D6FD31FF2E536christerholmbergericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <3A51E5ABFEEB6142A03B7C113D6F7CC8@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5IaSw8L2Rpdj4N
CjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj4NCjxk
aXYgY2xhc3M9ImdtYWlsX3F1b3RlIj4NCjxkaXY+PHNwYW4+PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PHdicj49PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08d2JyPj09PT09PT09
PT09PT09PTxicj4NCk5pdHM8YnI+DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT08d2Jy
Pj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PTx3YnI+PT09PT09PT09PT09PT09PGJyPg0K
PGJyPg0KR2VuZXJhbDo8YnI+DQo8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgSSBhZ3Jl
ZSB3aXRoIEVLUiB0aGF0IHRoZSB1c2Ugb2YgJnF1b3Q7YWRkcmVzczpwb3J0JnF1b3Q7IGlzIGN1
bWJlcnNvbWUuIEZvciB0aGU8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyZndDsgcGxhY2VzIHdo
ZXJlIHRoaXMgaXMgbm90IGEgc3RhbmQtaW4gZm9yIHRoZSB0ZXJtICZxdW90OydtPScgc2VjdGlv
biZxdW90OywgSSB3b3VsZDxicj4NCiZndDsmZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBzdWdnZXN0IHRo
YXQgdGhlIHdlbGwta25vd24gdGVybSAmcXVvdDszLXR1cGxlJnF1b3Q7IHdvdWxkIHNlcnZlIHRo
ZSBwdXJwb3NlIGluIGEgbXVjaCBtb3JlPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsmZ3Q7IHJl
YWRhYmxlIHdheS48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyZn
dDsmZ3Q7IEkgcGVyc29uYWxseSBoYXZlIG5vdGhpbmcgYWdhaW5zdCAnMy10dXBsZScsIMWSdHJh
bnNwb3J0JyAoc3VnZ2VzdGVkIGJ5PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZndDsgVGF5bG9yIGF0
IHNvbWUgcG9pbnQpLCBldGMuPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsgVGhlIHByb2JsZW0gaXMgdGhhdCB3aGVuZXZlciBJIGNoYW5nZSB0aGUgdGVybWlub2xv
Z3kgc29tZW9uZSBsYXRlcjxicj4NCiZndDsmZ3Q7Jmd0OyB3YW50cyBzb21ldGhpbmcgZWxzZSwg
YW5kIHRoZW4gSSBhZ2FpbiBoYXZlIHRvIGNoYW5nZSBpdC48YnI+DQomZ3Q7Jmd0OyZndDs8YnI+
DQomZ3Q7Jmd0OyZndDsgV2VsbCwgd2UncmUgYXQgSUVTRyByZXZpZXcgbm93LCBzbyB0aGlzIGlz
IHRoZSBsYXN0IHJvdW5kLjxicj4NCiZndDsmZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jmd0OyBXaG8s
IHNwZWNpZmljYWxseSwgaXMgaW4gZmF2b3Igb2YgdGhlIGN1cnJlbnQgdGVybWlub2xvZ3k/PGJy
Pg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBJIHNlZSBpdCBtb3JlIGFzIHRlcm1pbm9sb2d5IHRo
YXQgcGVvcGxlIGluIHRoZSBXRyBjb3VsZCBsaXZlIHdpdGguPGJyPg0KJmd0OyZndDs8YnI+DQom
Z3Q7Jmd0OyZndDsgVGhpcyBkb2Vzbid0IGFuc3dlciBteSBxdWVzdGlvbi4gV2hvLCBzcGVjaWZp
Y2FsbHksIHRoaW5rcyB0aGF0IHRoaXMgdGVybWlub2xvZ3k8YnI+DQomZ3Q7Jmd0OyZndDsgb2Yg
Zm9jdXNpbmcgb24gdGhlIGFkZHJlc3M6cG9ydCBhbmQgbm90IHRoZSBtPSBzZWN0aW9uIGlzIGdv
b2Q/PGJyPg0KJmd0OyZndDs8L3NwYW4+PC9kaXY+DQo8ZGl2PiZndDsmZ3Q7IENvbnNpZGVyaW5n
IHRoYXQgdGhlIGZvY3VzIGhhcyBiZWVuIG9uIHRoZSBhZGRyZXNzIGFuZCBwb3J0IHNpbmNlIGRh
eSBvbmUsIGZvciA3IHllYXJzLCBJIHRoaW5rIGl0IGlzIGdvb2QuDQo8L2Rpdj4NCjxkaXY+Jmd0
OzwvZGl2Pg0KPGRpdj4mZ3Q7IFllcywgd2hvIGJlc2lkZXMgeW91PzwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8ZGl2PkFzIHRoZSBNTVVTSUMgV0cgZGVjaWRlZCB0byBtb3ZlIHRoZSBkb2N1bWVudCBmb3J3
YXJkLCBJIGFzc3VtZSB0aGF0IHRoZSBpbnRlcmVzdGVkIHBhcnRpZXMgdGhpbmsgaXTigJlzIGF0
IGxlYXN0IGdvb2QgZW5vdWdoLiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFu
IGlkPSJPTEtfU1JDX0JPRFlfU0VDVElPTiI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIi
Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPg0KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPg0K
PGRpdj4mZ3Q7IEJlY2F1c2UgaW4gdGhlIHRleHQgYWJvdmUgeW91ciBhcmd1bWVudCBpcyB0aGF0
IGlmIHdlIGNoYW5nZSBpdCwgdGhlbiB5b3Ugd2lsbCBoYXZlIHRvIGNoYW5nZSBpdCBhZ2FpbiBi
ZWNhdXNlIHNvbWVvbmUgZWxzZSB3aWxsIG9iamVjdC48L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5D
b25zaWRlcmluZyB0aGUgaGlzdG9yeSBvZiB0aGlzIGRyYWZ0LCBhbmQgYWxsIHRoZSByZS13cml0
ZXMsIGFzIGF1dGhvciBJIHRoaW5rIHRoYXQgaXMgYSBmYWlyIGFyZ3VtZW50IDopPC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5IYXZpbmcgc2FpZCB0aGF0LCBJIHdpbGwgb2YgY291cnNl
IGltcGxlbWVudCB3aGF0ZXZlciB0aGUgY29tbXVuaXR5IGRlY2lkZXMuPC9kaXY+DQo8ZGl2Pjxi
cj4NCjwvZGl2Pg0KPGRpdj5SZWdhcmRzLDwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+
Q2hyaXN0ZXI8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZ
X1NFQ1RJT04iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxkaXYgY2xhc3M9Imdt
YWlsX2V4dHJhIj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPg0KPC9ib2R5
Pg0KPC9odG1sPg0K

--_000_D6FD31FF2E536christerholmbergericssoncom_--


From nobody Wed Apr 18 08:06:02 2018
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 7D0D212D86E for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 08:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 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, T_DKIMWL_WL_MED=-0.01] 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 4MD8PCPuQWdI for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 08:05:58 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::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 4520B126BF3 for <mmusic@ietf.org>; Wed, 18 Apr 2018 08:05:56 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id 126-v6so1884992oig.0 for <mmusic@ietf.org>; Wed, 18 Apr 2018 08:05:56 -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=h9cy1HqroUYy7yQT9EG4n0ySSBVQE3DGracylkBQD6c=; b=e+SJW/WX6FH2kPb8ziQJDlPwm0+m4lJrbX69s48FhMCLiL/AsGvBIMu3DsaZV5Mjsn DGfo9TgyZLIiTFb3jhaWE6LtEY0Ks6gLXU/hZUw4waKuXqGip15SuDtiGmzzFjJHWCmr tf/sg3OtDEtKbt+yF0f69wJHtq+BFI/GJ5yo1QyYP1GxYLpV+euDacwdzIdEK/yqaKJI 3Gp27tAg/EEAzbfNduXHRkgFLvGJqWO5LFy53DJXHrMT+BS162jXZeKHKeePN7yDzpn/ c7h2OO0vsuBO//0vi6BAuVgK2u6JMjcMaIWIJAOvokDyqVDRIAo6L4Z9mdQXPdrwYBlC ND0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h9cy1HqroUYy7yQT9EG4n0ySSBVQE3DGracylkBQD6c=; b=o4AhYJhqFkIjSOoox/9u1ztswhylHZ4MeNcH2yecfbb6YNCZj4qKCVn2lvnuiReOoM 0VCZrBxaexNYgXW+5nOtupHyREdfk2OJlMrd20/Pn8q3ybqwLxWQq4Xci53iayG7D744 IZQDUhtV/BTQGE2Yg2QFHOxh8abcDZ/T2xY18c0Fx+KB/3hT7nklE4Ke7xUblmjUmGvw xdkwSp47bimTl3kG4X6kftrcEMyUkLHQJZchGDwS0f8DN3b2QEQ7wy70hkKMDHcoHK3F q6wsu/mqyBCaE9BTEwBbvl3oZ3Q+QimxdkBjGyEneAobaXjbH5m7RBNqLw9r5k6tNEun r+3w==
X-Gm-Message-State: ALQs6tCrUAyp5Y08bSw5iKvrvRUCM8wu6LoTG0gl62WqfhBzTYyBxN9G bR57OjMUDvl68/NLUK/a0JihjaXgelHlK2t2DXYFNg==
X-Google-Smtp-Source: AIpwx4/dIv6ag7qypqMVQm8RXjZqzZQEromfY4/hoxNTNg4MaeeUh5alNL8sSkKGYU2EMBdYP/FeHyi8WzhhL+NeZk8=
X-Received: by 2002:aca:b06:: with SMTP id 6-v6mr135860oil.108.1524063955589;  Wed, 18 Apr 2018 08:05:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Wed, 18 Apr 2018 08:05:15 -0700 (PDT)
In-Reply-To: <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 18 Apr 2018 08:05:15 -0700
Message-ID: <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b06208056a20cae0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5i5t7DUaYxUcfJZNCTEJ6z1E5PE>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 15:06:00 -0000

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

On Wed, Apr 18, 2018 at 7:30 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> >>>>> o  Bundled media: All media associated with a given BUNDLE group.
> >>>>>
> >>>>> o  Initial offer: The first offer, within an SDP session (e.g. a
> >>>>>     SIP dialog when the Session Initiation Protocol (SIP) [RFC3261]
> is
> >>>>>     used to carry SDP), in which the offerer indicates that it want=
s
> >>>>>     to create a given BUNDLE group.
> >>>>
> >>>> This is a very idiosyncratic definition, because it's *not* the firs=
t
> >>>> offer in the session, but the one where the BUNDLE group is
> >>>> introduced. Given that 3264 has a different meaning for this same
> >>>> term, and the difference is critical, I would strongly urge you to
> >>>> pick a different term.
> >>>
> >>> I believe there are other drafts with similar definitions of "Initial
> Offer".
> >>>
> >> Perhaps, but as I noted, 3264s disagrees.
> >>
> >> Anyway, would something like "Initial BUNDLE offer" be better?
> >>
> >> Not really.
> >>
> >> So, what do you suggest?
> >>
> >> Note that, for most SDP extensions I can think of, "initial offer"
> refers to the offer where you actually start using the extension
> (explicitly or implicitly).
> >>
> >> But that's not the case here, because this is the one for this BUNDLE
> group, not for BUNDLE as a whole
> >>
> > I'm not sure you need a specific term here. How often do you use it?
>
> It=E2=80=99s based on the generic structure that MMUSIC has defined for t=
he O/A
> procedures of new attributes:
>
>    - Generating initial offer
>    - Generating answer
>    - Modifying the session
>
> Sure, we could use a structure like:
>
>    - Creating BUNDLE group
>       - Generating offer
>       - Generating answer
>    - Modifying BUNDLE group
>       - Generating offer
>          - Add/remove m- section etc
>       - Generating answer
>          - Add/remove m- section etc
>
>
> =E2=80=A6where the focus would be on whether a bundle group is created or
> modified, without caring about whether it=E2=80=99s the initial offer of =
the
> session or not.
>
> But, we would not be using the generic O/A structure.
>

I'm not seeing a problem with that



> >>>>>> The BUNDLE extension is indicated using an SDP 'group' attribute
> >>>>>> with a semantics value [RFC5888] of "BUNDLE".  An
> identification-tag is
> >>>>>> assigned to each bundled "m=3D" section, and each identification-t=
ag
> >>>>>> is listed in the SDP 'group:BUNDLE' attribute identification-tag
> list.
> >>>>>> Each "m=3D" section whose identification-tag is listed in the
> >>>>>> identification-tag list is associated with a given BUNDLE group.
> >>>>>
> >>>>> How about "is part of" instead of "associated with"
> >>>>>
> >>>>> There are most likely other instances that would have to be fixed,
> and I'd like to try to maintain consistent terminology.
> >>>>
> >>> Yes, I would change all of them.
> >>>
> >>> I have a quick look, and I am not sure we can change all instances of
> "associated with" to "is part of".
> > Yes, quite possibly, but that's an argument against using "associated"
> in this way. Find a set of more specific terms and use them.
> >>>>> Each "m=3D" section whose identification-tag is listed in the
> >>>>> identification-tag list is associated with a given BUNDLE group.
> >>>>
> >>>> SDP bodies can contain multiple BUNDLE groups.  Any given bundled
> >>>> "m=3D" section MUST NOT be associated with more than one BUNDLE grou=
p
> >>>> at any given time.
> >>>>
> >>>> Again "part of"
> >>>
> >>> There are multiple instances of "associated with BUNDLE group"
> terminology throughout the document.
> >>>
> >>> Yes, and they're all bad.
> >>
> >> Why?
> >
> > Because it's a generic term when specific ones would be better
>
> How do I know in which cases to use something more =E2=80=9Cspecific=E2=
=80=9D?
>

Almost every case




> For example:
>
>  "media associated with the BUNDLE group": Is media part of the group?
> Or, is there some other more specific word to use?
>

"m=3D" section that is part of a bundle group

 "identification-tag list is associated with a given
BUNDLE group": Is the list part of the group? Or, is there some other more
specific word to use?

"identification-tag list for a given bundle group"



 "The c=3D line net type value associated with  the bundled m=3D section=E2=
=80=9D: Is
the c=3D line part of the m=3D section? I don=E2=80=99t think so =E2=80=93 =
at least not in case
of a session-level c=3D line.

"the c=3Dline net type value that applies to the bundled m=3D section"


>>>>>> If the answer contains a BUNDLE group, the answerer MUST:
>>>>>>
>>>>>> o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
>>>>>>
>>>>>> o  Select an answerer BUNDLE address:port [Section 8.3.2].
>>>>>
>>>>> This isn't right, because each BUNDLE group has its own address:port,
>>>>> so instead "For each BUNDLE group" contained in the offer.
>>>>
>>>> The procedures is for individual BUNDLE groups, as indicated in
Section 8:
>>>>
>>>> "SDP offers and answers can contain multiple BUNDLE groups.  The
>>>>  procedures in this section apply independently to a given BUNDLE
>>>>  group."'
>>>
>>> I don't find this very clear.
>>
>> I am not sure adding "For each BUNDLE group" all over (it would be
needed in more places than indicated above) would make it better.
>>
>> So, my preference would be to work on the clarification text above, if
you think it needs to be more clear.
>
> I'm not sure how to fix this. Perhaps it needs a real rewrite

What needs a rewrite?

The section we are discussing




>>>>> When the offerer generates a subsequent offer, the offerer
>>>>> BUNDLE-tag MUST represent the bundled "m=3D" section to which the
offerer BUNDLE
>>>>> address:port (previously negotiated or newly suggested) has been
assigned.
>>>>>
>>>>> 8.5.1.  Suggesting a New Offerer BUNDLE Address:Port
>>>>
>>>> Again it would make more sense to describe this as suggesting a new m=
=3D
section.
>>>>
>>>> It does not have to be a new "m=3D" section. The new address:port can =
be
assigned to an existing "m=3D" section.
>>>
>>> You're suggesting that a new m=3D section be the one that things are
bundled into.
>>>
>> Not necessarily. The new address:port is assigned to *a* bundled m=3D
section, which could be the *same* m=3D section currently used to bundle
things into.
>
> Sure, but again, it's not the address:port that's being suggested, it's
its parameters

Well, in this particular case, the text is about changing the address:port.

But, even if we change that and talk about parameters, it still doesn=E2=80=
=99t
have to be a new m=3D section. You can modify the parameters of the existin=
g
bundle/lead/whatever m=3D section.


Yes, I agree with that

-Ekr

--000000000000b06208056a20cae0
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, Apr 18, 2018 at 7:30 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 style=3D"word-wrap:break-word">
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
Hi,</div><span class=3D"">
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<br>
</div>
<span id=3D"m_-6095139036913115OLK_SRC_BODY_SECTION" style=3D"color:rgb(0,0=
,0);font-family:Calibri,sans-serif;font-size:14px">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span>&gt;&gt;&gt;&gt;&gt; o=C2=A0 Bundled media: All media associated=
 with a given BUNDLE group.<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt;&gt; o=C2=A0 Initial offer: The first offer, within an SDP =
session (e.g. a<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0SIP dialog when the Session Initiat=
ion Protocol (SIP) [RFC3261] is<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0used to carry SDP), in which the of=
ferer indicates that it wants<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0to create a given BUNDLE group.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; This is a very idiosyncratic definition, because it&#39;s =
*not* the first<br>
&gt;&gt;&gt;&gt; offer in the session, but the one where the BUNDLE group i=
s<br>
&gt;&gt;&gt;&gt; introduced. Given that 3264 has a different meaning for th=
is same<br>
&gt;&gt;&gt;&gt; term, and the difference is critical, I would strongly urg=
e you to<br>
&gt;&gt;&gt;&gt; pick a different term.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I believe there are other drafts with similar definitions of &=
quot;Initial Offer&quot;.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Perhaps, but as I noted, 3264s disagrees.<br>
&gt;&gt;<br>
&gt;&gt; Anyway, would something like &quot;Initial BUNDLE offer&quot; be b=
etter?<br>
&gt;&gt;<br>
&gt;&gt; Not really.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; So, what do you suggest?</div>
<div>&gt;&gt;</div>
<div>&gt;&gt; Note that, for most SDP extensions I can think of, &quot;init=
ial offer&quot; refers to the offer where you actually start using the exte=
nsion (explicitly or implicitly).
</div>
<div>&gt;&gt;</div>
<div>&gt;&gt; But that&#39;s not the case here, because this is the one for=
 this BUNDLE group, not for BUNDLE as a whole<br>
</div>
<div>&gt;&gt;</div>
<div>&gt; I&#39;m not sure you need a specific term here. How often do you =
use it?</div>
</div>
</div>
</div>
</span>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<br>
</div>
</span><div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-s=
ize:14px">
It=E2=80=99s based on the generic structure that MMUSIC has defined for the=
 O/A procedures of new attributes:</div>
<ul style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px=
">
<li>Generating initial offer</li><li>Generating answer</li><li>Modifying th=
e session=C2=A0</li></ul>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
Sure, we could use a structure like:</div>
<ul style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px=
">
<li>Creating BUNDLE group
<ul>
<li>Generating offer</li><li>Generating answer</li></ul>
</li><li>Modifying BUNDLE group
<ul>
<li>Generating offer
<ul>
<li>Add/remove m- section etc</li></ul>
</li><li>Generating answer
<ul>
<li>Add/remove m- section etc</li></ul>
</li></ul>
</li></ul>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<br>
</div>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
=E2=80=A6where the focus would be on whether a bundle group is created or m=
odified, without caring about whether it=E2=80=99s the initial offer of the=
 session or not.</div>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<br>
</div>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
But, we would not be using the generic O/A structure.</div></div></blockquo=
te><div><br></div><div>I&#39;m not seeing a problem with that<br></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 id=3D"m_-6095139036913115OLK_SRC=
_BODY_SECTION" style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;fon=
t-size:14px"><div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span>&gt;&gt;&gt;&gt;&gt;&gt; The BUNDLE extension is indicated using=
 an SDP &#39;group&#39; attribute<br>
&gt;&gt;&gt;&gt;&gt;&gt; with a semantics value [RFC5888] of &quot;BUNDLE&q=
uot;.=C2=A0 An identification-tag is<br>
&gt;&gt;&gt;&gt;&gt;&gt; assigned to each bundled &quot;m=3D&quot; section,=
 and each identification-tag<br>
&gt;&gt;&gt;&gt;&gt;&gt; is listed in the SDP &#39;group:BUNDLE&#39; attrib=
ute identification-tag list.<br>
&gt;&gt;&gt;&gt;&gt;&gt; Each &quot;m=3D&quot; section whose identification=
-tag is listed in the<br>
&gt;&gt;&gt;&gt;&gt;&gt; identification-tag list is associated with a given=
 BUNDLE group.<br>
&gt;&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; How about &quot;is part of&quot; instead of &quot;asso=
ciated with&quot;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; There are most likely other instances that would have =
to be fixed, and I&#39;d like to try to maintain consistent terminology.
<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt; Yes, I would change all of them.<br>
&gt;&gt;&gt;</span></div>
<div>&gt;&gt;&gt; I have a quick look, and I am not sure we can change all =
instances of &quot;associated with&quot; to &quot;is part of&quot;.</div>
<div>&gt; Yes, quite possibly, but that&#39;s an argument against using &qu=
ot;associated&quot; in this way. Find a set of more specific terms and use =
them.</div>
</div>
</div>
</div>
</div>
</div>
</span></span><span id=3D"m_-6095139036913115OLK_SRC_BODY_SECTION" style=3D=
"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote"><span class=3D"">
<div><span>&gt;&gt;&gt;&gt;&gt; Each &quot;m=3D&quot; section whose identif=
ication-tag is listed in the<br>
&gt;&gt;&gt;&gt;&gt; identification-tag list is associated with a given BUN=
DLE group.<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt; SDP bodies can contain multiple BUNDLE groups.=C2=A0 Any g=
iven bundled<br>
&gt;&gt;&gt;&gt; &quot;m=3D&quot; section MUST NOT be associated with more =
than one BUNDLE group<br>
&gt;&gt;&gt;&gt; at any given time.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Again &quot;part of&quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There are multiple instances of &quot;associated with BUNDLE g=
roup&quot; terminology throughout the document.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Yes, and they&#39;re all bad.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; Why?</div>
<div>&gt;</div>
</span><div>&gt; Because it&#39;s a generic term when specific ones would b=
e better</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<br>
</div>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
How do I know in which cases to use something more =E2=80=9Cspecific=E2=80=
=9D?</div></div></blockquote><div><br></div><div>Almost every case</div><di=
v> <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 style=3D"word-wrap:break-word">
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
For example:</div>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<br>
</div>
<div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x">
<span style=3D"font-size:medium">=C2=A0&quot;</span>media associated with t=
he BUNDLE group<span style=3D"font-size:medium">&quot;</span>: Is media par=
t of the group? Or, is there some other more specific word to use?</div></d=
iv></blockquote><div><br></div><div>&quot;m=3D&quot; section that is part o=
f a bundle group</div><div><br></div><div style=3D"word-wrap:break-word"><d=
iv><font face=3D"Calibri,sans-serif">=C2=A0&quot;</font><span style=3D"colo=
r:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px;white-space:pre-=
wrap">identification-tag list is associated with a given</span></div><div><=
span style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14p=
x;white-space:pre-wrap"> BUNDLE group</span><span style=3D"font-family:Cali=
bri,sans-serif">&quot;</span><font face=3D"Calibri,sans-serif"><span style=
=3D"white-space:pre-wrap">:
</span></font><font face=3D"Calibri,sans-serif"><span style=3D"white-space:=
pre-wrap">Is the list part of the group? Or, is there some other more speci=
fic word to use?</span></font></div><div><font face=3D"Calibri,sans-serif">=
<span style=3D"white-space:pre-wrap"><br></span></font></div><div><font fac=
e=3D"Calibri,sans-serif"><span style=3D"white-space:pre-wrap">&quot;identif=
ication-tag list for a given bundle group&quot;</span></font></div><div><fo=
nt face=3D"Calibri,sans-serif"><span style=3D"white-space:pre-wrap"><br></s=
pan></font></div><div><font face=3D"Calibri,sans-serif"><span style=3D"whit=
e-space:pre-wrap"><br></span></font></div>
<div><br>
</div>
<div>=C2=A0<span style=3D"font-family:Calibri,sans-serif">&quot;</span>The =
c=3D line net type value associated with =C2=A0the bundled m=3D section<spa=
n><font face=3D"Calibri,sans-serif">=E2=80=9D:=C2=A0</font></span>Is
 the c=3D line part of the m=3D section? I don=E2=80=99t think so =E2=80=93=
 at least not in case of a session-level c=3D line.</div><div><br></div><di=
v>&quot;the c=3Dline net type value that applies to the bundled m=3D sectio=
n&quot;<br></div>
<div><br>
</div><br></div><div style=3D"word-wrap:break-word"><span class=3D""><span =
id=3D"m_-6095139036913115OLK_SRC_BODY_SECTION" style=3D"color:rgb(0,0,0);fo=
nt-family:Calibri,sans-serif;font-size:14px"><div><div><div dir=3D"ltr"><di=
v class=3D"gmail_extra"><div class=3D"gmail_quote"><div><span>&gt;&gt;&gt;&=
gt;&gt;&gt; If the answer contains a BUNDLE group, the answerer MUST:<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt;&gt;&gt; o=C2=A0 Select an offerer BUNDLE address:port [Sec=
tion 8.3.1]; and<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt;&gt;&gt; o=C2=A0 Select an answerer BUNDLE address:port [Se=
ction 8.3.2].<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; This isn&#39;t right, because each BUNDLE group has it=
s own address:port,<br>
&gt;&gt;&gt;&gt;&gt; so instead &quot;For each BUNDLE group&quot; contained=
 in the offer.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The procedures is for individual BUNDLE groups, as indicat=
ed in Section 8:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0&quot;SDP offers and answers can contain multiple BUN=
DLE groups.=C2=A0 The<br>
&gt;&gt;&gt;&gt;=C2=A0 procedures in this section apply independently to a =
given BUNDLE<br>
&gt;&gt;&gt;&gt;=C2=A0 group.&quot;&#39;=C2=A0<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don&#39;t find this very clear.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; I am not sure adding &quot;For each BUNDLE group&quot; all ov=
er (it would be needed in more places than indicated above) would make it b=
etter.</div>
<div>&gt;&gt;</div>
<div>&gt;&gt; So, my preference would be to work on the clarification text =
above, if you think it needs to be more clear.</div>
<div>&gt;</div>
<div>&gt; I&#39;m not sure how to fix this. Perhaps it needs a real rewrite=
 </div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>What needs a rewrite?</div><div><br></div><div>The section we a=
re discussing<br></div><span class=3D""><br></span></div><div style=3D"word=
-wrap:break-word"><span class=3D""></span><span class=3D""><br></span></div=
><div style=3D"word-wrap:break-word"><span class=3D""><br></span></div><div=
 style=3D"word-wrap:break-word"><span class=3D""></span><span class=3D""><s=
pan id=3D"m_-6095139036913115OLK_SRC_BODY_SECTION" style=3D"color:rgb(0,0,0=
);font-family:Calibri,sans-serif;font-size:14px"><div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div><span>&gt;&gt;&gt;&gt;&gt; When the offerer generates a subsequent off=
er, the offerer<br>
&gt;&gt;&gt;&gt;&gt; BUNDLE-tag MUST represent the bundled &quot;m=3D&quot;=
 section to which the offerer BUNDLE<br>
&gt;&gt;&gt;&gt;&gt; address:port (previously negotiated or newly suggested=
) has been assigned.<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0<br>
&gt;&gt;&gt;&gt;&gt; 8.5.1.=C2=A0 Suggesting a New Offerer BUNDLE Address:P=
ort<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Again it would make more sense to describe this as suggest=
ing a new m=3D section.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; It does not have to be a new &quot;m=3D&quot; section. The=
 new address:port can be assigned to an existing &quot;m=3D&quot; section.<=
br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; You&#39;re suggesting that a new m=3D section be the one that =
things are bundled into.<br>
&gt;&gt;&gt;</span></div>
<div>&gt;&gt; Not necessarily. The new address:port is assigned to *a* bund=
led m=3D section, which could be the *same* m=3D section currently used to =
bundle things into.</div>
<div>&gt;</div>
<div>&gt; Sure, but again, it&#39;s not the address:port that&#39;s being s=
uggested, it&#39;s its parameters</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>Well, in this particular case, the text is about changing the a=
ddress:port.</div>
<div><br>
</div>
<div>But, even if we change that and talk about parameters, it still doesn=
=E2=80=99t have to be a new m=3D section. You can modify the parameters of =
the existing bundle/lead/whatever m=3D section.</div>
<div><br>
</div>
</div><div style=3D"word-wrap:break-word"><br></div><div style=3D"word-wrap=
:break-word">Yes, I agree with that</div><div style=3D"word-wrap:break-word=
"><br></div><div style=3D"word-wrap:break-word">-Ekr</div><div style=3D"wor=
d-wrap:break-word"><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

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

--000000000000b06208056a20cae0--


From nobody Wed Apr 18 11:29:21 2018
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 3B158127735 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 11:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPnXyzctAP45 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 11:29:17 -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 F08931200FC for <mmusic@ietf.org>; Wed, 18 Apr 2018 11:29:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524076155; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=pHiFJ/tebVZ9s7ogVKbzk006Iub3yKqGV4GZ//Qq+n0=; b=YxzUaLfHe5LQy8zymH781vaHGyEyZh5wKdqIglwDKHHIomI2og8cWO95IQGrMX6l P6PpHhoUmOtVWaY0rz2XNI0bxk8V4rJZlBInRPHWumENvy/CVne67Dd22yxVT8kz /gNb54ayeLmnwujBObNY82FtIefH2eeOLwdmvv9cFnU=;
X-AuditID: c1b4fb2d-815ff70000003563-1f-5ad78e7ad67d
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id BC.4A.13667.A7E87DA5; Wed, 18 Apr 2018 20:29:15 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0382.000; Wed, 18 Apr 2018 20:29:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
Thread-Index: AQHT1lZf0qxFmZgCwkeSofFpx7VVFKQFQviAgADjodCAADKqAIAATwsA///WzoCAAFZ94A==
Date: Wed, 18 Apr 2018 18:29:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com>
In-Reply-To: <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@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.166]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCIsWRmVeSWpSXmKPExsUyM2J7lG513/Uog+9b2Cymz3rHZrHi9Tl2 i/cXdC1m/JnIbHF+53omi6nLH7M4sHlM+b2R1WPJkp9MHpMftzEHMEdx2aSk5mSWpRbp2yVw ZbQ8mc9U8M2q4uDMl2wNjFssuxg5OSQETCT2LjjG3sXIxSEkcIRRYtf8JawQzmJGidObp7B1 MXJwsAlYSHT/0wZpEBFQkPj15wQLSA2zwAQmiat/V7OCJIQFaiVm/VjOCFFUJ7Fg8WEmCDtM Yva9dWwgNouAqsS9JQtZQGxeAV+Jt+8nMEEsm8EsMX3uH2aQBKdAoMT2L3vZQWxGATGJ76fW gA1iFhCXuAX0AsTZAhJL9pxnhrBFJV4+/scKYStJHD19iRXkaGYBTYn1u/QhWhUlpnQ/ZIfY KyhxcuYTlgmMorOQTJ2F0DELSccsJB0LGFlWMYoWpxYX56YbGeulFmUmFxfn5+nlpZZsYgTG 1cEtv3V3MK5+7XiIUYCDUYmHV6PoepQQa2JZcWXuIUYJDmYlEd6dj69ECfGmJFZWpRblxxeV 5qQWH2KU5mBREufVW7UnSkggPbEkNTs1tSC1CCbLxMEp1cBoP+1k22y7o7YP625k7Z48KWhF qNCf/FIDmx17Zh8MTJs/L+DXPUfzL8Lnjn27/catxMbMLu5mXofMzQ1LLshuq7FMsJKWEpy7 NGLu4YhUqbhVm58utt5iMlcxfsnhC11M0p1Vz7sWKf6detDg2EOpIJNpYYr7+JhuZ36ZfUu2 5ojnZ1MbmXciSizFGYmGWsxFxYkAL9nv16cCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SWQ37gx8gdO0aNaVsx5MRenASKI>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 18:29:19 -0000

SGksDQoNCj4+Pj4+PiBvwqAgQnVuZGxlZCBtZWRpYTogQWxsIG1lZGlhIGFzc29jaWF0ZWQgd2l0
aCBhIGdpdmVuIEJVTkRMRSBncm91cC4NCj4+Pj4+PsKgIMKgDQo+Pj4+Pj4gb8KgIEluaXRpYWwg
b2ZmZXI6IFRoZSBmaXJzdCBvZmZlciwgd2l0aGluIGFuIFNEUCBzZXNzaW9uIChlLmcuIGENCj4+
Pj4+PsKgIMKgIMKgU0lQIGRpYWxvZyB3aGVuIHRoZSBTZXNzaW9uIEluaXRpYXRpb24gUHJvdG9j
b2wgKFNJUCkgW1JGQzMyNjFdIGlzDQo+Pj4+Pj7CoCDCoCDCoHVzZWQgdG8gY2FycnkgU0RQKSwg
aW4gd2hpY2ggdGhlIG9mZmVyZXIgaW5kaWNhdGVzIHRoYXQgaXQgd2FudHMNCj4+Pj4+PsKgIMKg
IMKgdG8gY3JlYXRlIGEgZ2l2ZW4gQlVORExFIGdyb3VwLg0KPj4+Pj4gDQo+Pj4+PiBUaGlzIGlz
IGEgdmVyeSBpZGlvc3luY3JhdGljIGRlZmluaXRpb24sIGJlY2F1c2UgaXQncyAqbm90KiB0aGUg
Zmlyc3QNCj4+Pj4+IG9mZmVyIGluIHRoZSBzZXNzaW9uLCBidXQgdGhlIG9uZSB3aGVyZSB0aGUg
QlVORExFIGdyb3VwIGlzDQo+Pj4+PiBpbnRyb2R1Y2VkLiBHaXZlbiB0aGF0IDMyNjQgaGFzIGEg
ZGlmZmVyZW50IG1lYW5pbmcgZm9yIHRoaXMgc2FtZQ0KPj4+Pj4gdGVybSwgYW5kIHRoZSBkaWZm
ZXJlbmNlIGlzIGNyaXRpY2FsLCBJIHdvdWxkIHN0cm9uZ2x5IHVyZ2UgeW91IHRvDQo+Pj4+PiBw
aWNrIGEgZGlmZmVyZW50IHRlcm0uDQo+Pj4+DQo+Pj4+IEkgYmVsaWV2ZSB0aGVyZSBhcmUgb3Ro
ZXIgZHJhZnRzIHdpdGggc2ltaWxhciBkZWZpbml0aW9ucyBvZiAiSW5pdGlhbCBPZmZlciIuDQo+
Pj4+DQo+Pj4gUGVyaGFwcywgYnV0IGFzIEkgbm90ZWQsIDMyNjRzIGRpc2FncmVlcy4NCj4+Pg0K
Pj4+IEFueXdheSwgd291bGQgc29tZXRoaW5nIGxpa2UgIkluaXRpYWwgQlVORExFIG9mZmVyIiBi
ZSBiZXR0ZXI/DQo+Pj4NCj4+PiBOb3QgcmVhbGx5Lg0KPj4+DQo+Pj4+IFNvLCB3aGF0IGRvIHlv
dSBzdWdnZXN0Pw0KPj4+DQo+Pj4+IE5vdGUgdGhhdCwgZm9yIG1vc3QgU0RQIGV4dGVuc2lvbnMg
SSBjYW4gdGhpbmsgb2YsICJpbml0aWFsIG9mZmVyIiByZWZlcnMgdG8gdGhlIG9mZmVyIHdoZXJl
IHlvdSBhY3R1YWxseSBzdGFydCB1c2luZyB0aGUgZXh0ZW5zaW9uIChleHBsaWNpdGx5IG9yIGlt
cGxpY2l0bHkpLiANCj4+Pg0KPj4+PiBCdXQgdGhhdCdzIG5vdCB0aGUgY2FzZSBoZXJlLCBiZWNh
dXNlIHRoaXMgaXMgdGhlIG9uZSBmb3IgdGhpcyBCVU5ETEUgZ3JvdXAsIG5vdCBmb3IgQlVORExF
IGFzIGEgd2hvbGUNCj4+Pg0KPj4+IEknbSBub3Qgc3VyZSB5b3UgbmVlZCBhIHNwZWNpZmljIHRl
cm0gaGVyZS4gSG93IG9mdGVuIGRvIHlvdSB1c2UgaXQ/DQo+Pg0KPj4gSXTigJlzIGJhc2VkIG9u
IHRoZSBnZW5lcmljIHN0cnVjdHVyZSB0aGF0IE1NVVNJQyBoYXMgZGVmaW5lZCBmb3IgdGhlIE8v
QSBwcm9jZWR1cmVzIG9mIG5ldyBhdHRyaWJ1dGVzOg0KPj4NCj4+IOKAoiBHZW5lcmF0aW5nIGlu
aXRpYWwgb2ZmZXINCj4+IOKAoiBHZW5lcmF0aW5nIGFuc3dlcg0KPj4g4oCiIE1vZGlmeWluZyB0
aGUgc2Vzc2lvbg0KPj7CoA0KPj4gU3VyZSwgd2UgY291bGQgdXNlIGEgc3RydWN0dXJlIGxpa2U6
DQo+Pg0KPj4g4oCiIENyZWF0aW5nIEJVTkRMRSBncm91cCANCj4+ICAgIG8gR2VuZXJhdGluZyBv
ZmZlcg0KPj4gICAgbyBHZW5lcmF0aW5nIGFuc3dlcg0KPj4g4oCiIE1vZGlmeWluZyBCVU5ETEUg
Z3JvdXAgDQo+PiAgICBvIEdlbmVyYXRpbmcgb2ZmZXIgDQo+PiAgICAgICAgIOKAoiBBZGQvcmVt
b3ZlIG0tIHNlY3Rpb24gZXRjDQo+PiAgICBvIEdlbmVyYXRpbmcgYW5zd2VyIA0KPj4gICAgICAg
ICDigKIgQWRkL3JlbW92ZSBtLSBzZWN0aW9uIGV0Yw0KPj4NCj4+IOKApndoZXJlIHRoZSBmb2N1
cyB3b3VsZCBiZSBvbiB3aGV0aGVyIGEgYnVuZGxlIGdyb3VwIGlzIGNyZWF0ZWQgb3IgbW9kaWZp
ZWQsIHdpdGhvdXQgY2FyaW5nIGFib3V0IA0KPj4gd2hldGhlciBpdOKAmXMgdGhlIGluaXRpYWwg
b2ZmZXIgb2YgdGhlIHNlc3Npb24gb3Igbm90Lg0KPj4NCj4+IEJ1dCwgd2Ugd291bGQgbm90IGJl
IHVzaW5nIHRoZSBnZW5lcmljIE8vQSBzdHJ1Y3R1cmUuDQo+DQo+IEknbSBub3Qgc2VlaW5nIGEg
cHJvYmxlbSB3aXRoIHRoYXQNCg0KSSB0aGluayBzb21lIGRvLCBlLmcuLCB0aGUgY2hhaXJzLg0K
DQpJIGhhdmUgcGVyc29uYWxseSBhbHNvIGJlZW4gc3RyaWN0IGFib3V0IGl0IHdoZW4gcmV2aWV3
aW5nIGRvY3VtZW50cyB3cml0dGVuIGJ5IG90aGVycywgYnV0IEkgaGF2ZSBubyBwcm9ibGVtIGFs
bG93aW5nIG90aGVyIHN0cnVjdHVyZXMgaWYgc2VlbiBtb3JlIGFwcHJvcHJpYXRlIC0gaWYgZXZl
cnlvbmUgaXMgb2sgd2l0aCBpdC4NCg0KLS0tDQoNCj4+Pj4+Pj4gVGhlIEJVTkRMRSBleHRlbnNp
b24gaXMgaW5kaWNhdGVkIHVzaW5nIGFuIFNEUCAnZ3JvdXAnIGF0dHJpYnV0ZQ0KPj4+Pj4+PiB3
aXRoIGEgc2VtYW50aWNzIHZhbHVlIFtSRkM1ODg4XSBvZiAiQlVORExFIi7CoCBBbiBpZGVudGlm
aWNhdGlvbi10YWcgaXMNCj4+Pj4+Pj4gYXNzaWduZWQgdG8gZWFjaCBidW5kbGVkICJtPSIgc2Vj
dGlvbiwgYW5kIGVhY2ggaWRlbnRpZmljYXRpb24tdGFnDQo+Pj4+Pj4+IGlzIGxpc3RlZCBpbiB0
aGUgU0RQICdncm91cDpCVU5ETEUnIGF0dHJpYnV0ZSBpZGVudGlmaWNhdGlvbi10YWcgbGlzdC4N
Cj4+Pj4+Pj4gRWFjaCAibT0iIHNlY3Rpb24gd2hvc2UgaWRlbnRpZmljYXRpb24tdGFnIGlzIGxp
c3RlZCBpbiB0aGUNCj4+Pj4+Pj4gaWRlbnRpZmljYXRpb24tdGFnIGxpc3QgaXMgYXNzb2NpYXRl
ZCB3aXRoIGEgZ2l2ZW4gQlVORExFIGdyb3VwLg0KPj4+Pj4+IA0KPj4+Pj4+IEhvdyBhYm91dCAi
aXMgcGFydCBvZiIgaW5zdGVhZCBvZiAiYXNzb2NpYXRlZCB3aXRoIg0KPj4+Pj4+DQo+Pj4+Pj4g
VGhlcmUgYXJlIG1vc3QgbGlrZWx5IG90aGVyIGluc3RhbmNlcyB0aGF0IHdvdWxkIGhhdmUgdG8g
YmUgZml4ZWQsIGFuZCBJJ2QgbGlrZSB0byB0cnkgdG8gbWFpbnRhaW4gY29uc2lzdGVudCB0ZXJt
aW5vbG9neS4gDQo+Pj4+Pg0KPj4+Pj4gWWVzLCBJIHdvdWxkIGNoYW5nZSBhbGwgb2YgdGhlbS4N
Cj4+Pj4NCj4+Pj4gSSBoYXZlIGEgcXVpY2sgbG9vaywgYW5kIEkgYW0gbm90IHN1cmUgd2UgY2Fu
IGNoYW5nZSBhbGwgaW5zdGFuY2VzIG9mICJhc3NvY2lhdGVkIHdpdGgiIHRvICJpcyBwYXJ0IG9m
Ii4NCj4+PiBZZXMsIHF1aXRlIHBvc3NpYmx5LCBidXQgdGhhdCdzIGFuIGFyZ3VtZW50IGFnYWlu
c3QgdXNpbmcgImFzc29jaWF0ZWQiIGluIHRoaXMgd2F5LiBGaW5kIGEgc2V0IG9mIG1vcmUgc3Bl
Y2lmaWMgdGVybXMgYW5kIHVzZSB0aGVtLg0KPj4+Pj4+IEVhY2ggIm09IiBzZWN0aW9uIHdob3Nl
IGlkZW50aWZpY2F0aW9uLXRhZyBpcyBsaXN0ZWQgaW4gdGhlDQo+Pj4+Pj4gaWRlbnRpZmljYXRp
b24tdGFnIGxpc3QgaXMgYXNzb2NpYXRlZCB3aXRoIGEgZ2l2ZW4gQlVORExFIGdyb3VwLg0KPj4+
Pj7CoCDCoA0KPj4+Pj4gU0RQIGJvZGllcyBjYW4gY29udGFpbiBtdWx0aXBsZSBCVU5ETEUgZ3Jv
dXBzLsKgIEFueSBnaXZlbiBidW5kbGVkDQo+Pj4+PiAibT0iIHNlY3Rpb24gTVVTVCBOT1QgYmUg
YXNzb2NpYXRlZCB3aXRoIG1vcmUgdGhhbiBvbmUgQlVORExFIGdyb3VwDQo+Pj4+PiBhdCBhbnkg
Z2l2ZW4gdGltZS4NCj4+Pj4+IA0KPj4+Pj4gQWdhaW4gInBhcnQgb2YiDQo+Pj4+DQo+Pj4+IFRo
ZXJlIGFyZSBtdWx0aXBsZSBpbnN0YW5jZXMgb2YgImFzc29jaWF0ZWQgd2l0aCBCVU5ETEUgZ3Jv
dXAiIHRlcm1pbm9sb2d5IHRocm91Z2hvdXQgdGhlIGRvY3VtZW50Lg0KPj4+Pg0KPj4+PiBZZXMs
IGFuZCB0aGV5J3JlIGFsbCBiYWQuDQo+Pj4NCj4+PiBXaHk/DQo+Pg0KPj4gQmVjYXVzZSBpdCdz
IGEgZ2VuZXJpYyB0ZXJtIHdoZW4gc3BlY2lmaWMgb25lcyB3b3VsZCBiZSBiZXR0ZXINCj4+DQo+
PiBIb3cgZG8gSSBrbm93IGluIHdoaWNoIGNhc2VzIHRvIHVzZSBzb21ldGhpbmcgbW9yZSDigJxz
cGVjaWZpY+KAnT8NCj4+DQo+PiBBbG1vc3QgZXZlcnkgY2FzZQ0KPj4NCj4+IEZvciBleGFtcGxl
Og0KPj4NCj4+wqAibWVkaWEgYXNzb2NpYXRlZCB3aXRoIHRoZSBCVU5ETEUgZ3JvdXAiOiBJcyBt
ZWRpYSBwYXJ0IG9mIHRoZSBncm91cD8gT3IsIGlzIHRoZXJlIHNvbWUgb3RoZXIgbW9yZSBzcGVj
aWZpYyB3b3JkIHRvIHVzZT8NCj4NCj4gIm09IiBzZWN0aW9uIHRoYXQgaXMgcGFydCBvZiBhIGJ1
bmRsZSBncm91cA0KDQpZZXMsIGJ1dCBJIGFtIHRhbGtpbmcgYWJvdXQgdGhlIG1lZGlhLiBJcyBt
ZWRpYSBwYXJ0IG9mIHRoZSBncm91cD8NCg0KPj7CoCJpZGVudGlmaWNhdGlvbi10YWcgbGlzdCBp
cyBhc3NvY2lhdGVkIHdpdGggYSBnaXZlbg0KPj4gQlVORExFIGdyb3VwIjogSXMgdGhlIGxpc3Qg
cGFydCBvZiB0aGUgZ3JvdXA/IE9yLCBpcyB0aGVyZSBzb21lIG90aGVyIG1vcmUgc3BlY2lmaWMg
d29yZCB0byB1c2U/DQo+DQo+ICJpZGVudGlmaWNhdGlvbi10YWcgbGlzdCBmb3IgYSBnaXZlbiBi
dW5kbGUgZ3JvdXAiDQoNCkhvdyBpcyAiZm9yIiBtb3JlIHNwZWNpZmljIHRoYW4gImFzc29jaWF0
ZWQiPw0KDQo+PsKgIlRoZSBjPSBsaW5lIG5ldCB0eXBlIHZhbHVlIGFzc29jaWF0ZWQgd2l0aCDC
oHRoZSBidW5kbGVkIG09IHNlY3Rpb27igJ06wqBJcyB0aGUgYz0gbGluZSBwYXJ0IG9mIHRoZSBt
PSBzZWN0aW9uPyANCj4+IEkgZG9u4oCZdCB0aGluayBzbyDigJMgYXQgbGVhc3Qgbm90IGluIGNh
c2Ugb2YgYSBzZXNzaW9uLWxldmVsIGM9IGxpbmUuDQo+DQo+ICJ0aGUgYz1saW5lIG5ldCB0eXBl
IHZhbHVlIHRoYXQgYXBwbGllcyB0byB0aGUgYnVuZGxlZCBtPSBzZWN0aW9uIg0KDQpIb3cgaXMg
ImFwcGxpZXMiIG1vcmUgc3BlY2lmaWMgdGhhbiAiYXNzb2NpYXRlZCI/DQoNCkkgZ2V0IHRoYXQg
eW91IGRvbid0IGxpa2UgdGhlIHVzZSBvZiB0aGUgd29yZCAiYXNzb2NpYXRlZCIuIEJ1dCwgaW4g
Z2VuZXJhbCwgY29taW5nIHVwIHdpdGggYSBidW5jaCBvZiBkaWZmZXJlbnQgd29yZHMganVzdCB0
byBnZXQgcmlkIG9mICJhc3NvY2lhdGVkIiBkb2Vzbid0IG1ha2Ugc2Vuc2UgdG8gbWUuIEl0J3Mg
YSBwdXJlIGVkaXRvcmlhbCBjaG9pY2UsIGFuZCBldmVyeSBhdXRob3IgaGFzIGhpcy9oZXIgZmF2
b3VyaXRlIHByZWZlcmVuY2UsIGFuZCBJIHRoaW5rIGhhdmluZyBjb25zaXN0ZW50IHRlcm1pbm9s
b2d5IGlzIG1vcmUgaW1wb3J0YW50IHRoYW4gZmluZGluZyB0aGUgYmVzdCB3b3JkLg0KDQpIYXZp
bmcgc2FpZCB0aGF0LCBpZiB0aGVyZSBpcyBhIGNhc2Ugd2hlcmUgYSBkaWZmZXJlbnQgd29yZCB3
b3VsZCByZWFsbHkgbWFrZSB0aGluZ3MgbW9yZSBjbGVhciwgSSBhbSBoYXBweSB0byBsb29rIGF0
IGl0Lg0KDQooQWxzbyBub3RlIHRoYXQgSSBkaWQgZ2V0IHJpZCBvZiBhIG51bWJlciBvZiAiYXNz
b2NpYXRlZCIgaW5zdGFuY2VzIGR1cmluZyB0aGUgY2hhbmdlcyBkb25lIGJhc2VkIG9uIFdHTEMg
cmV2aWV3cyBldGMuKQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0K


From nobody Wed Apr 18 11:44:49 2018
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 6EC0C12783A for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 11:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1-4eSNA0ld6 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 11:44:47 -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 D19FA1200FC for <mmusic@ietf.org>; Wed, 18 Apr 2018 11:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524077084; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=uJWgxOFt99s4/sJecBJ5LWxJ+5GPoq3E7Ies3nNrc0E=; b=bY2ag4UZOi569w0/neQ0qRZ2GzQe4ahzs+KK1XHelacj9in4mWoNJux7KncUi/T3 TOZeaYPwosyS4MG+lJeQJfCegBekdNivP63p41ldQM2rv5i0L+yRLD1vFAxnJiZQ Doh7piI3bDBDiMuhugmQl+NJIDD1bpnZ2xkfwj3XPPw=;
X-AuditID: c1b4fb3a-acfff7000000795a-b2-5ad7921cae95
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 29.E3.31066.C1297DA5; Wed, 18 Apr 2018 20:44:44 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0382.000; Wed, 18 Apr 2018 20:44:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: =?utf-8?B?TWlyamEgS8O8aGxld2luZCdzIE5vIE9iamVjdGlvbiBvbiBkcmFmdC1pZXRm?= =?utf-8?B?LW1tdXNpYy1zZHAtYnVuZGxlLW5lZ290aWF0aW9uLTQ5OiAod2l0aCBDT01N?= =?utf-8?Q?ENT)?=
Thread-Index: AQHT1xGjyqZ6y5jHNEyixintO6xk7aQG3Frg
Date: Wed, 18 Apr 2018 18:44:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E8DE44@ESESSMB109.ericsson.se>
References: <152405488591.31812.8842902591498905286.idtracker@ietfa.amsl.com>
In-Reply-To: <152405488591.31812.8842902591498905286.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.166]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7qK7MpOtRBle+WVhMn/WOzeL9BV2L GX8mMlu8uP6R2eL8zvVMFlOXP2ZxYPOY8nsjq8eSJT+ZPFo+LmQNYI7isklJzcksSy3St0vg ytjz6zVLwQXmirkvd7I3MB5h7mLk5JAQMJFo+zKFFcQWEjjCKPHqp0cXIxeQvZhRYtaWdyxd jBwcbAIWEt3/tEFqRASiJJ7s/cIOUsMs8IVR4tnno4wgjrDAZkaJk+ebmUEcEYEtQJnWJmaI FiOJ3hMnwSaxCKhKHN1pDxLmFfAFWrCGEWKzr8Tnxc1gV3AK+En0PXsN1sooICbx/dQaJhCb WUBc4taT+UwQVwtILNlzHuoDUYmXj/+xQthKEkdPX2IFWcUsoCmxfpc+RKuixJTuh+wQawUl Ts58wjKBUXQWkqmzEDpmIemYhaRjASPLKkbR4tTi4tx0IyO91KLM5OLi/Dy9vNSSTYzAqDq4 5bfVDsaDzx0PMQpwMCrx8P7pvR4lxJpYVlyZe4hRgoNZSYR35+MrUUK8KYmVValF+fFFpTmp xYcYpTlYlMR5ndIsooQE0hNLUrNTUwtSi2CyTBycUg2MjJnZ8tHHVSb+v2lykqfwyZILHIeV vpueZHumeIb1lUSOVYSdIpepZZA9W82Rx+pbnp60UcgMEb98ufStEfeChwnTwo9tu8ftfEwt fE5B5/OFpa7R1hO63nWscecNd97IwCRRoaedsdFA2Up222FdpfTnTZ90RDtWLZnq1lm165NH 2h7/zi9KLMUZiYZazEXFiQDCscQDpgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Tq3Wkm_e0pJ1xDi_1yV1A905YaI>
Subject: Re: [MMUSIC]  =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draf?= =?utf-8?q?t-ietf-mmusic-sdp-bundle-negotiation-49=3A_=28with_COMMENT=29?=
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 18:44:48 -0000

SGkgTWlyamEsDQoNClRoYW5rIFlvdSBmb3IgdGhlIHJldmlldyEgUGxlYXNlIHNlZSBpbmxpbmUu
DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCkNPTU1FTlQ6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCj4gTWF5YmUgYWxz
byBicmllZmx5IHNheSBpbiB0aGUgYWJzdHJhY3QgaG93L3doeSBSRkM3OTQxIGlzIHVwZGF0ZWQu
DQoNCkknbGwgbG9vayBpbnRvIHRoYXQgOikNCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Wed Apr 18 12:22:57 2018
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 699FF126C26 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 12:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 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, T_DKIMWL_WL_MED=-0.01] 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 jW60YB8AcORJ for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 12:22:49 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 063E5126CC7 for <mmusic@ietf.org>; Wed, 18 Apr 2018 12:22:49 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id e123-v6so2630930oih.13 for <mmusic@ietf.org>; Wed, 18 Apr 2018 12:22:48 -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=XNkmUoCWN6iNV+japbk3kK21ueHMrjpLSyPCKAPA3gs=; b=vtSqPAvdIoiN4bFid3A9pli1EEPfrjgYYFfO8GcjXaTyFJBj0q/tvCgAbbpMpEvhsO UBZBDY08fdMXA15OHt5LwmV+iPOpJDTabapyUifmMx6AVQubjLL8LKNww7HxIFrEkgRF jitohhxC2fVDOsAc+Lsy7ENOFrFKbNkF22Xv0EY3MCp8ENsDwamgW67t8lriEfvWrCjg qKx1/v9erTic+pgq6/vtuzl0QjnYBSCJdIIgUTR6/136RzcVWdx5L4xBT4yy+MFXKJA3 /3h2ZyqB7nr+b8fYUG6c9VScBof7oVgVkrNfrbOXtzRMeaqVAxRhc2lwbCJRMbWsamtm fkOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XNkmUoCWN6iNV+japbk3kK21ueHMrjpLSyPCKAPA3gs=; b=UbA4GyNERcW16ukYxOwIQVLhf120BSvd6x3/f7GXCdUA3WoPTgqtrxTrPWNtz0cf2k E8XxK0JWG5ruToGtWYHU4SD/Mh/8HrrS9MJUSVOlG4YIq50IyZ87Fk8yqPZb/6QUrSLS 8Qm8eZBGqemNL0Lr0Knwampkz6VG1ZKvxEjOdAwGEZJ4PIFPWm6gVGgqmaNpVn8YT7fS SR8c7k3P2UcanyUpOJZCA0DaAdWpjIC1aG7RGef5UPDZduu37CrWMnxGvMUVeXJbYFlB 86vZ8ZXg3Rm6CYQ383xxo/eHhy73yWKybpnReVvsffKhyZ5ykIsSso5o/H5IqdKdA08J F0zA==
X-Gm-Message-State: ALQs6tAUE8pTCd1jX+XC/gZhit05/TPVbdjJ4APnrc5sdthfaCJ0VySx Iyn6LxARXQLOA9nvF/zPt2cqqFAywez1fqN1odTeDQ==
X-Google-Smtp-Source: AIpwx4+7Sa2l+QJbzvTOl9Khgi3T90dKvorHtt6DZm7JybbdwBCfHrck/htNJJUqVvJlPqcFwz1iOMR0cqVD84INZSw=
X-Received: by 2002:aca:4f46:: with SMTP id d67-v6mr1842699oib.138.1524079368405;  Wed, 18 Apr 2018 12:22:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.138.18.132 with HTTP; Wed, 18 Apr 2018 12:22:07 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 18 Apr 2018 12:22:07 -0700
Message-ID: <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005d2c8e056a24612c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/mu1cRp2fL8c5vXfhmYLVKlNVlsU>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 18 Apr 2018 19:22:51 -0000

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

On Wed, Apr 18, 2018 at 11:29 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> >> Because it's a generic term when specific ones would be better
> >>
> >> How do I know in which cases to use something more =E2=80=9Cspecific=
=E2=80=9D?
> >>
> >> Almost every case
> >>
> >> For example:
> >>
> >> "media associated with the BUNDLE group": Is media part of the group?
> Or, is there some other more specific word to use?
> >
> > "m=3D" section that is part of a bundle group
>
> Yes, but I am talking about the media. Is media part of the group?
>

I would have to see the text in context.

>
> >> "identification-tag list is associated with a given
> >> BUNDLE group": Is the list part of the group? Or, is there some other
> more specific word to use?
> >
> > "identification-tag list for a given bundle group"
>
> How is "for" more specific than "associated"?
>
> >> "The c=3D line net type value associated with  the bundled m=3D
> section=E2=80=9D: Is the c=3D line part of the m=3D section?
> >> I don=E2=80=99t think so =E2=80=93 at least not in case of a session-l=
evel c=3D line.
> >
> > "the c=3Dline net type value that applies to the bundled m=3D section"
>
> How is "applies" more specific than "associated"?
>

The answer to both of these is the same. You are using the word associated
for a number of different things, and so having different terms is clearer.


> I get that you don't like the use of the word "associated". But, in
> general, coming up with a bunch of different words just to get rid of
> "associated" doesn't make sense to me. It's a pure editorial choice, and
> every author has his/her favourite preference, and I think having
> consistent terminology is more important than finding the best word.
>

It's not a pure editorial choice. It's a source of confusion to have an
overloaded term.

-Ekr


Having said that, if there is a case where a different word would really
> make things more clear, I am happy to look at it.
>
> (Also note that I did get rid of a number of "associated" instances durin=
g
> the changes done based on WGLC reviews etc.)
>
> Regards,
>
> Christer
>

--0000000000005d2c8e056a24612c
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, Apr 18, 2018 at 11:29 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><br><div><div class=3D"h5">
&gt;&gt; Because it&#39;s a generic term when specific ones would be better=
<br>
&gt;&gt;<br>
&gt;&gt; How do I know in which cases to use something more =E2=80=9Cspecif=
ic=E2=80=9D?<br>
&gt;&gt;<br>
&gt;&gt; Almost every case<br>
&gt;&gt;<br>
&gt;&gt; For example:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0&quot;media associated with the BUNDLE group&quot;: Is media =
part of the group? Or, is there some other more specific word to use?<br>
&gt;<br>
&gt; &quot;m=3D&quot; section that is part of a bundle group<br>
<br>
</div></div>Yes, but I am talking about the media. Is media part of the gro=
up?<br></blockquote><div><br></div><div>I would have to see the text in con=
text.<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D""><br>
&gt;&gt;=C2=A0&quot;identification-tag list is associated with a given<br>
&gt;&gt; BUNDLE group&quot;: Is the list part of the group? Or, is there so=
me other more specific word to use?<br>
&gt;<br>
&gt; &quot;identification-tag list for a given bundle group&quot;<br>
<br>
</span>How is &quot;for&quot; more specific than &quot;associated&quot;?<br=
>
<span class=3D""><br>
&gt;&gt;=C2=A0&quot;The c=3D line net type value associated with =C2=A0the =
bundled m=3D section=E2=80=9D:=C2=A0Is the c=3D line part of the m=3D secti=
on? <br>
&gt;&gt; I don=E2=80=99t think so =E2=80=93 at least not in case of a sessi=
on-level c=3D line.<br>
&gt;<br>
&gt; &quot;the c=3Dline net type value that applies to the bundled m=3D sec=
tion&quot;<br>
<br>
</span>How is &quot;applies&quot; more specific than &quot;associated&quot;=
?<br></blockquote><div><br></div><div>The answer to both of these is the sa=
me. You are using the word associated for a number of different things, and=
 so having different terms is clearer.</div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<br>
I get that you don&#39;t like the use of the word &quot;associated&quot;. B=
ut, in general, coming up with a bunch of different words just to get rid o=
f &quot;associated&quot; doesn&#39;t make sense to me. It&#39;s a pure edit=
orial choice, and every author has his/her favourite preference, and I thin=
k having consistent terminology is more important than finding the best wor=
d.<br>
</blockquote><div><br></div><div>It&#39;s not a pure editorial choice. It&#=
39;s a source of confusion to have an overloaded term.</div><div><br></div>=
<div>-Ekr</div><div><br></div><div> <br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
Having said that, if there is a case where a different word would really ma=
ke things more clear, I am happy to look at it.<br>
<br>
(Also note that I did get rid of a number of &quot;associated&quot; instanc=
es during the changes done based on WGLC reviews etc.)<br>
<br>
Regards,<br>
<br>
Christer<br>
</blockquote></div><br></div></div>

--0000000000005d2c8e056a24612c--


From nobody Wed Apr 18 18:32:52 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A198F126C89; Wed, 18 Apr 2018 18:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=PrV//5rD; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=k6ldlGsy
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ul9blGGoa_9E; Wed, 18 Apr 2018 18:32:47 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADFFC12711A; Wed, 18 Apr 2018 18:32:47 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 10BD621D32; Wed, 18 Apr 2018 21:32:47 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 18 Apr 2018 21:32:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=rYC4rHwPoda/4FZ/MLsqtKSgOOUWp mpgZu5oeW+HiQE=; b=PrV//5rDPFWy+N4680TNQnf+6LxzLO3negxBI6XFu34Id S9v6hOkis5dTuZsghOVwktNhFNI3YpPEoQQ84ihxw3/47R+DRcNXUr4sSVxCP41d DtqiYeJV6jnveE9o4z11RM0zQgN8DwGvf5Zfr9QXhIP4qSyO3VZfXnjMzHJeLP5x fDqwA4G5r1s6p9q9pD4r4BwL49s8oKVV3Zv10bdOxZa6o6xRyqiFJxplh1LR6BG8 8kFAFiLW7lRScCA1Qq+ANsTWkkjFyuo6cjukxIQVb0deA+wDeexNMgojhThIThDV TYZt0R6UOExGoCvIG2tmqvdyJfeQGlIDExRDPb8HQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=rYC4rH wPoda/4FZ/MLsqtKSgOOUWpmpgZu5oeW+HiQE=; b=k6ldlGsyt94ZJL6cucWmkz sOrP/CTU5yw193N7l4O55QJ8eX1BGuWWxbnEwJpICo0dTZN5I5Br9RHdZ0rYSXUV 1XYstRVXkLwxM4HrS2esTPH0Fx9afs+9s86CpWSkyA22vY8W7/JFN/BiE8w2X9We X10LpeRe6pZqjaYS4iEB6ykm+Uy8Zm9PpFvLjPBVksW2c5alYQFqeKlZ3nyBeZji AEH4CqnhYQwCDJYg16clccbq4KufhSdOdYOyn9crrcFKOflGRqqNmKE2it3iYFyy vV+Pb4oYs43sfB+Mlssh/MMuOp6S0/NWbwdfOolAspP/xaZVd6fKad4eO7veM4iw ==
X-ME-Sender: <xms:v_HXWspnvkVaLA51sMePmH7TLDgWzQTAyD61kpO9Dy7VHrWpiby_qg>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.67]) by mail.messagingengine.com (Postfix) with ESMTPA id A46DEE4350; Wed, 18 Apr 2018 21:32:46 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <152278809420.22755.15521672481164240628@ietfa.amsl.com>
Date: Wed, 18 Apr 2018 21:32:46 -0400
Cc: IETF Gen-ART <gen-art@ietf.org>, draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B88BB6FA-B1EE-44F1-A5C4-713319BD41FB@cooperw.in>
References: <152278809420.22755.15521672481164240628@ietfa.amsl.com>
To: Linda Dunbar <linda.dunbar@huawei.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/F2i9NGQwc8EeYlwVwkCdmtjQ5nw>
Subject: Re: [MMUSIC] [Gen-art] Genart telechat review of draft-ietf-mmusic-sdp-bundle-negotiation-49
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 01:32:50 -0000

Linda, thanks for your reviews. I have entered a No Objection ballot.

Alissa

> On Apr 3, 2018, at 4:41 PM, Linda Dunbar <linda.dunbar@huawei.com> =
wrote:
>=20
> Reviewer: Linda Dunbar
> Review result: Ready
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-mmusic-sdp-bundle-negotiation-??
> Reviewer: Linda Dunbar
> Review Date: 2018-04-03
> IETF LC End Date: 2018-02-14
> IESG Telechat date: 2018-04-19
>=20
> Summary:
> The document is written very clear, easy to understand even for people =
like me
> who is not an expert in the media transport. A dump question, is =
"media
> description" same as a "media flow"? Is it always one to one mapping?
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 18 18:51:37 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A76127333; Wed, 18 Apr 2018 18:51:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-mmusic-rid@ietf.org, Flemming Andreasen <fandreas@cisco.com>, mmusic-chairs@ietf.org, fandreas@cisco.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152410269032.28761.17181858949377320428.idtracker@ietfa.amsl.com>
Date: Wed, 18 Apr 2018 18:51:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/8h275NoD1VChosFe2zIGj1cmfcc>
Subject: [MMUSIC] Alissa Cooper's No Objection on draft-ietf-mmusic-rid-14: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 01:51:30 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-mmusic-rid-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-rid/



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

The Gen-ART reviewer made some useful suggestions. Please take a look.
https://datatracker.ietf.org/doc/review-ietf-mmusic-rid-14-genart-lc-sparks-2018-02-27/



From nobody Wed Apr 18 18:52:15 2018
Return-Path: <alissa@cooperw.in>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42E15127871; Wed, 18 Apr 2018 18:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=L8NlkHW4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dS0k1zMj
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A3pIQmGdePEC; Wed, 18 Apr 2018 18:52:06 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D160127333; Wed, 18 Apr 2018 18:52:03 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5E37921AEF; Wed, 18 Apr 2018 21:52:02 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 18 Apr 2018 21:52:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=iPJ2/BrFAdugFuGid3eNX1uAZGYkV idAdbhQdwWDnRQ=; b=L8NlkHW4LuElRRLXmXfUJFX18WVnI5PAk2lrVkRERZwze O3XqM1zSTz6MhwBxAI+Tv/cnK3i91qQdwghZ+dNIF0bVJBRGVAX9AohBFeP0JCjT ZcZBSqsc5OV7ENRjckWZHYOEcsVD1MGOkVOsxb4zQ3fzVyroroZkgQxFJCqzqJd1 pfqw5T9+dTTeODmqQfB/JarWqIQoH5gG9fY3Zdx6Jra03jElA32Fg5Z3kCbCl0T2 ZADjZM2KQFBIBex9LJUsnq5J+kI+ogrrb1Y7jBFJTtsghzybk1M+T9MOrLW1WrTW WS4RrCINgKmrrRCavrX2CMqqH4oP2USWgfsH9NdjQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=iPJ2/B rFAdugFuGid3eNX1uAZGYkVidAdbhQdwWDnRQ=; b=dS0k1zMjGakAPmbKS6Bi2f u+0r9FB0jcipq14Wbd7Q5Wjn+aTN1g2OscwCTGLmCNiQlt/vvUyAZHTphGaXlyaD /3ZF1RJs9s1X7b2nuE7PYt4ZV0Kq2egTg+ipFtVeWwZhxvgDQtGDflATlivurnxC G9Wm7eCf5sWAqrUTsLskLchIJg2EQ9Gb3Z9TQOFW7Ywps4QKFzy29sxQJTjRhhDm l1QeV44mkEC1Au36PHIdHDtG7kI7AuMc8msNJwYpcTuynJv8pxuDTSOk8e9BXQ36 CF5D83yHiww6/gH5WCWoab9UBxNnsQyMm8N2dlTbzwQ5o32MSpfltyRcTplV2rdA ==
X-ME-Sender: <xms:QvbXWngRf_wEuU9gGGGeOzsU32nRPhahVALqYsPMiBLDP5gAaHnHnA>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.67]) by mail.messagingengine.com (Postfix) with ESMTPA id DD6B1E4122; Wed, 18 Apr 2018 21:52:01 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <151976486707.28513.8133879591048964555@ietfa.amsl.com>
Date: Wed, 18 Apr 2018 21:52:01 -0400
Cc: IETF Gen-ART <gen-art@ietf.org>, draft-ietf-mmusic-rid.all@ietf.org, mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <16AA205B-3922-4459-B0BE-0E0B92885A38@cooperw.in>
References: <151976486707.28513.8133879591048964555@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-ReHTl7dlNNu4iZ1GZbh3FZmh1U>
Subject: Re: [MMUSIC] [Gen-art] Genart last call review of draft-ietf-mmusic-rid-14
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 01:52:08 -0000

Robert, thanks for your review. I have entered a No Objection ballot and =
flagged your comments to the authors.

Alissa

> On Feb 27, 2018, at 3:54 PM, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>=20
> Reviewer: Robert Sparks
> Review result: Ready with Nits
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-mmusic-rid-14
> Reviewer: Robert Sparks
> Review Date: 2018-02-27
> IETF LC End Date: 2018-03-30
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Ready with nits
>=20
> Nits:
>=20
> I could see implementor disagreement around what's allowed when =
modifying a
> session driven by the statement in the introduction that "They do not =
relax any
> existing descriptions." (where "They" here are the restrictions =
communicated
> with this attribute). Please look for a way to make it clear that an =
updating
> offer-answer round _can_ result in fewer restrictions than the =
original round
> did, just not fewer restrictions than the description places on the =
media if
> the "rid" extension is not present.
>=20
> (Micronit): I don't think the "To be clear" in the first paragraph on =
page 5
> helps. I also worry that "it" may not have a clear meaning in "Such
> implementations must send it" later in that paragraph.
>=20
> At the description of max-bpp on page 7, the last sentence is awkward. =
Do you
> perhaps mean "These values MUST NOT be encoded with more than four =
digits to
> the right of the decimal point."?
>=20
> In the second paragraph of section 6, "its own unique 5-tuple" is =
arcane if the
> reader hasn't read the rest of the rtcweb work. Could you provide a =
description
> or a pointer to a description here?
>=20
> At section 6.3, where you say 'For each "a=3Drid" line:', should you =
say 'For
> each "a=3Drid" line that has not been discarded by the requirements in =
section
> 6.2:'?
>=20
> I found "a non-empty union" to be a confusing description of the =
condition you
> are trying to convey in section 8. (A union of two sets, at least one =
of which
> is not empty is going to be non-empty). I'm not sure intersection is =
the right
> word here either. Perhaps you could find a different way to =
characterize the
> condition?
>=20
> The BNF for rid-id allows rid-ids like "This-is_my-favorite" or
> "Gm-Cqzkj4VHVD". But all the examples use single digits for rid-ids. I =
see the
> statement that "the actual identifiers used for RIDs are expected to =
be
> opaque". I strongly encourage putting some opaque ones in the =
examples.
>=20
> Consider reminding people that ABNF quoted strings are =
case-insensitive, and
> that the grammar as written will allow things like "MaX-WiDtH" and =
"rECv". If
> that's not what you want, consider bringing in RFC7405.=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 18 20:35:23 2018
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 65394120713 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 20:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cQGqs-4Yu86j for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 20:35:19 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 619CD128C0A for <mmusic@ietf.org>; Wed, 18 Apr 2018 20:35:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14994; q=dns/txt; s=iport; t=1524108919; x=1525318519; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=VCFdLAVkxcf+uYN9DdkRFrBkkMROWDaWoG+YGaJ4QLQ=; b=B1EhUzc7X1lRygvmjbqMArWKquzKF6LSAiZRgsp1iK/c3DgpgoU93936 3A4CRuqCg5uW8uVWoJuNziKTwC2UJjVWfgjWTfH5p2ZcbQsOlADQ37Kfj MNnhZKQMofgfs8gmq+DkeXnDLqO+1a5EW9n9aFiWgVOJnu1+PWrEHYBmF 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AtAwDkDdha/4gNJK0aAUIODAEBAQE?= =?us-ascii?q?BAgEBAQEIAQEBAYNCYRdjKINoiAKNCoFLKYEPjgeEa4F4CxgBCoQARgKCYyE?= =?us-ascii?q?0GAECAQEBAQEBAmwcDIUjAQEBAwEBIUsbCQIOCioCAicwBgEMBgIBAYR8DQ+?= =?us-ascii?q?JQ4EVm0CCHB+EOYNsgiAFiAaBVD+BDyOBUmgugxEBAQOBOoMjglQCkGSHBwi?= =?us-ascii?q?FWYUrgzIGgTSGFYUEhzaBfYZzgSUcOIFSTSMVO4IzAQEOgiAXiFmFBFYjMI9?= =?us-ascii?q?MAQE?=
X-IronPort-AV: E=Sophos;i="5.48,467,1517875200";  d="scan'208,217";a="383242043"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Apr 2018 03:35:18 +0000
Received: from [10.24.26.104] ([10.24.26.104]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w3J3ZHM6009074; Thu, 19 Apr 2018 03:35:18 GMT
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, IETF MMUSIC WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com>
Date: Wed, 18 Apr 2018 23:35:17 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu>
Content-Type: multipart/alternative; boundary="------------AD21F40B170DA2AC9C99A207"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bJ9XDGy3qT4XQYtoNvxJ1G9AOz8>
Subject: Re: [MMUSIC] INPUT NEEDED: Edits to 4566bis based on discussion in London
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 03:35:22 -0000

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



On 4/5/18 5:17 PM, Paul Kyzivat wrote:
> I'm working on making the changes to 4566bis that were called for 
> based on the discussion in London. After reviewing all of that I have 
> some questions for which I need feedback from the wg.
>
> * Open Issue 3 - Regarding section 5.11 (z=):
>
> After reviewing the text for t=, r=, z=, the meaning of z= seems 
> pretty clear to me. The text for z= only talks about how it works with 
> r=. In principle, if the adjustment time precedes the start time from 
> t= then I suppose it *might* also apply there, and perhaps to stop 
> time as well.
>
> From the text and examples it is clear that this isn't usable for 
> anything else. E.g., it does *not* provide an adjustment that yields 
> local time.
>
> I could reword to say that it does *not* apply to the start/stop times 
> in t=, or that it definitely only applies to r=. Thoughts?
>
Section 5.11 (z=) says:
<quote>

  Adjustments apply to all "t=" and
    "r=" lines in a session description.

</quote>

If I understood Colin's explanation in London correctly, then I believe 
it *should* only apply to the "r=" line, but that's not what it 
currently says. Maybe Colin can weigh in again ? In either case, I don't 
find the text as clear as you do, so adding a few more lines of text 
would be helpful.

> * Open Issue 7 - Regarding section 8.2.2 ("proto"):
>
> The minutes (regarding udptl) say:
>
> "Action: will grandfather T.38 and keep the text as is. Also change to 
> currently defined registration procedure."
>
> What was meant here? The registration procedure says RFC Required. 
> Changing to conform to that is different from grandfathering T.38.
>
> ISTM that all is well as it is.
>
The minutes 
(https://datatracker.ietf.org/meeting/101/materials/minutes-101-mmusic/) 
say that:
<quote>

	There was also discussion on how to handle udptl, concluding that the
	registry information for udptl is incorrect but that 4566bis will
	grandfather T.38 and keep the text as is. The currently defined
	registration procedure should however be changed to not only allow
	referencing standards track RFC. [Action: Authors]

</quote>

My memory may not serve me well here, but I thought we said that it 
should in fact reference a standards track RFC (there was some back and 
forth discussion between our ADs on this point after the initial 
conclusion I believe). Probably best to listen to the meeting recording 
on this one to verify what the final conclusion was.

> * Open Issue 8 - Regarding section 8.2.3 ("fmt"):
>
> The text implies that the namespace for udp formats consists of mime 
> types. It says:
>
>    ... If no media
>    subtype exists, it is RECOMMENDED that a suitable one be registered
>    through the IETF process [RFC6838] by production of, or reference to,
>    a standards-track RFC that defines the transport protocol for the
>    format.
>
> But IIUC rfc6838 makes no provision for defining a *transport 
> protocol* for a mime type.
>
> I'm not even entirely sure what rfc4566 intended here. Was it that the 
> content of each UDP packet is to conform to the definition of the mime 
> type? What about ordering rules that impose requirements on sequences 
> of packets?
>
> Is it intended that the media types suitable for use as udp formats 
> are only those that have something special in their definitions? Or 
> may any mime type be used if it can fit in a UDP packet?
Here is what the minutes say:
<quote>

     *	Open Issue #8 - Where are media format (“fmt”) registrations to be
     	done?
	Colin commented that the only “proto” that currently has a
	well-defined registration policy (in RFC 3555) are the ones based on
	RTP. A discussion concluded to clarify that the media format namespace
	and registration procedures depends on “proto” value and that “fmt”
	registration procedures must also be specified when registering a new
	“proto”. Jonathan offered to provide text giving some guidance.
	[Action: Jonathan and authors]

</quote>

I'd prod Jonathan for some text here.
>
> * Open Issue 9 - Regarding section 8.2.5 ("bwtype"):
>
> The notes say:
>
> "Check the current IANA registry, did they change the registry and 
> update accordingly."
>
> The registry does now have the mux category, and the entries for CT 
> and AS reference both 4566 and mux-attributes.
>
> AFAICT the only thing to do is update these two registry entries to 
> reference this bis rather than 4566. Did I miss anything?
>

Here is what we have in the minutes:
<quote>

     *	Open Issue #9 - Should IANA registration of “CT” and “AS” bandwidth
     	specifiers be updated to point to 4566bis instead of to RFC 4566 and
	draft-ietf-mmusic-sdp-mux-attributes as today?
	Ben C commented that the current text “should be registered” seems
	un-enforceable and that the WG should pick a text pointing to one of
	the currently defined procedures. This is also applicable to open
	issue #7. It was concluded to re-check IANA registry and refine text
	in 4566bis accordingly. [Action: Authors]

</quote>

Hope this helps.

-- Flemming

>     Thanks,
>     Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/5/18 5:17 PM, Paul Kyzivat wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu">I'm
      working on making the changes to 4566bis that were called for
      based on the discussion in London. After reviewing all of that I
      have some questions for which I need feedback from the wg.
      <br>
      <br>
      * Open Issue 3 - Regarding section 5.11 (z=):
      <br>
      <br>
      After reviewing the text for t=, r=, z=, the meaning of z= seems
      pretty clear to me. The text for z= only talks about how it works
      with r=. In principle, if the adjustment time precedes the start
      time from t= then I suppose it *might* also apply there, and
      perhaps to stop time as well.
      <br>
      <br>
      From the text and examples it is clear that this isn't usable for
      anything else. E.g., it does *not* provide an adjustment that
      yields local time.
      <br>
      <br>
      I could reword to say that it does *not* apply to the start/stop
      times in t=, or that it definitely only applies to r=. Thoughts?
      <br>
      <br>
    </blockquote>
    Section 5.11 (z=) says:<br>
    &lt;quote&gt;<br>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; word-wrap: break-word; white-space: pre-wrap;"> Adjustments apply to all "t=" and
   "r=" lines in a session description.</pre>
    &lt;/quote&gt;<br>
    <br>
    If I understood Colin's explanation in London correctly, then I
    believe it *should* only apply to the "r=" line, but that's not what
    it currently says. Maybe Colin can weigh in again ? In either case,
    I don't find the text as clear as you do, so adding a few more lines
    of text would be helpful. <br>
    <br>
    <blockquote type="cite"
      cite="mid:08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu">*
      Open Issue 7 - Regarding section 8.2.2 ("proto"):
      <br>
      <br>
      The minutes (regarding udptl) say:
      <br>
      <br>
      "Action: will grandfather T.38 and keep the text as is. Also
      change to currently defined registration procedure."
      <br>
      <br>
      What was meant here? The registration procedure says RFC Required.
      Changing to conform to that is different from grandfathering T.38.
      <br>
      <br>
      ISTM that all is well as it is.
      <br>
      <br>
    </blockquote>
    The minutes
    (<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/meeting/101/materials/minutes-101-mmusic/">https://datatracker.ietf.org/meeting/101/materials/minutes-101-mmusic/</a>)
    say that:<br>
    &lt;quote&gt;<br>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; word-wrap: break-word; white-space: pre-wrap;">	There was also discussion on how to handle udptl, concluding that the
	registry information for udptl is incorrect but that 4566bis will
	grandfather T.38 and keep the text as is. The currently defined
	registration procedure should however be changed to not only allow
	referencing standards track RFC. [Action: Authors]
</pre>
    &lt;/quote&gt;<br>
    <br>
    My memory may not serve me well here, but I thought we said that it
    should in fact reference a standards track RFC (there was some back
    and forth discussion between our ADs on this point after the initial
    conclusion I believe). Probably best to listen to the meeting
    recording on this one to verify what the final conclusion was. <br>
    <br>
    <blockquote type="cite"
      cite="mid:08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu">*
      Open Issue 8 - Regarding section 8.2.3 ("fmt"):
      <br>
      <br>
      The text implies that the namespace for udp formats consists of
      mime types. It says:
      <br>
      <br>
         ... If no media
      <br>
         subtype exists, it is RECOMMENDED that a suitable one be
      registered
      <br>
         through the IETF process [RFC6838] by production of, or
      reference to,
      <br>
         a standards-track RFC that defines the transport protocol for
      the
      <br>
         format.
      <br>
      <br>
      But IIUC rfc6838 makes no provision for defining a *transport
      protocol* for a mime type.
      <br>
      <br>
      I'm not even entirely sure what rfc4566 intended here. Was it that
      the content of each UDP packet is to conform to the definition of
      the mime type? What about ordering rules that impose requirements
      on sequences of packets?
      <br>
      <br>
      Is it intended that the media types suitable for use as udp
      formats are only those that have something special in their
      definitions? Or may any mime type be used if it can fit in a UDP
      packet?
      <br>
    </blockquote>
    Here is what the minutes say:<br>
    &lt;quote&gt;<br>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; word-wrap: break-word; white-space: pre-wrap;">    *	Open Issue #8 - Where are media format (“fmt”) registrations to be
    	done?
	Colin commented that the only “proto” that currently has a
	well-defined registration policy (in RFC 3555) are the ones based on
	RTP. A discussion concluded to clarify that the media format namespace
	and registration procedures depends on “proto” value and that “fmt”
	registration procedures must also be specified when registering a new
	“proto”. Jonathan offered to provide text giving some guidance.
	[Action: Jonathan and authors]</pre>
    &lt;/quote&gt; <br>
    <br>
    I'd prod Jonathan for some text here. <br>
    <blockquote type="cite"
      cite="mid:08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu">
      <br>
      * Open Issue 9 - Regarding section 8.2.5 ("bwtype"):
      <br>
      <br>
      The notes say:
      <br>
      <br>
      "Check the current IANA registry, did they change the registry and
      update accordingly."
      <br>
      <br>
      The registry does now have the mux category, and the entries for
      CT and AS reference both 4566 and mux-attributes.
      <br>
      <br>
      AFAICT the only thing to do is update these two registry entries
      to reference this bis rather than 4566. Did I miss anything?
      <br>
      <br>
    </blockquote>
    <br>
    Here is what we have in the minutes:<br>
    &lt;quote&gt;<br>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; word-wrap: break-word; white-space: pre-wrap;">    *	Open Issue #9 - Should IANA registration of “CT” and “AS” bandwidth
    	specifiers be updated to point to 4566bis instead of to RFC 4566 and
	draft-ietf-mmusic-sdp-mux-attributes as today?
	Ben C commented that the current text “should be registered” seems
	un-enforceable and that the WG should pick a text pointing to one of
	the currently defined procedures. This is also applicable to open
	issue #7. It was concluded to re-check IANA registry and refine text
	in 4566bis accordingly. [Action: Authors]</pre>
    &lt;/quote&gt;<br>
    <br>
    Hope this helps. <br>
    <br>
    -- Flemming <br>
    <br>
    <blockquote type="cite"
      cite="mid:08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu">    Thanks,
      <br>
          Paul
      <br>
      <br>
      _______________________________________________
      <br>
      mmusic mailing list
      <br>
      <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
      <br>
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
      <br>
      .
      <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------AD21F40B170DA2AC9C99A207--


From nobody Wed Apr 18 23:49:49 2018
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 8767A12AAB6 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 23:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnqYQS56E6h5 for <mmusic@ietfa.amsl.com>; Wed, 18 Apr 2018 23:49:45 -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 DE46C129C70 for <mmusic@ietf.org>; Wed, 18 Apr 2018 23:49:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524120582; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=eV+ORemXMNDvx+g8ORPEm0nHVXqcv397G6bwOl1XnRY=; b=BeGygpyCLJvhxhOgUmil2nNRLgTGfMs7aF9esOLPLP7ZEyvJ8emRx3y1WBQ3lhEa U0LDU9HZs6a+IquudsIK6c7ApilrFi9BsMvgEbf3BH4zk6U4qyv/W1Bs4bniFC9s 7UGQirta6NDCukMN74W/A/nGizFaTggr5IezznmHA8k=;
X-AuditID: c1b4fb30-4c8039c000007681-e4-5ad83c06b7c3
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 86.0D.30337.60C38DA5; Thu, 19 Apr 2018 08:49:42 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0382.000; Thu, 19 Apr 2018 08:49:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
Thread-Index: AQHT1lZf0qxFmZgCwkeSofFpx7VVFKQFQviAgADjodCAADKqAIAATwsA///WzoCAAFZ94P//8UeAgADy8QA=
Date: Thu, 19 Apr 2018 06:49:36 +0000
Message-ID: <D6FE16FE.2E5F6%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com>
In-Reply-To: <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D6FE16FE2E5F6christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrIIsWRmVeSWpSXmKPExsUyM2K7ii6bzY0og56pJhbTZ71js1jx+hy7 xfsLuhYz/kxktji/cz2TxdTlj1kc2Dym/N7I6rFkyU8mj8mP25gDmKO4bFJSczLLUov07RK4 MjrbdAsOSFQcnPqDvYHxukgXIyeHhICJxKw1b1i6GLk4hASOMEq8OjKNEcJZzCixaMlDIIeD g03AQqL7nzZIg4iAgsSvPyfAGpgFJjBJXP27mhUkISxQK7H55zEWiKI6iQWLDzNB2EkSky+s YgexWQRUJS6suAUW5xWwlli67x4T1DIWiUv/vrGBJDgFAiXOzF4LZjMKiEl8P7UGrIFZQFzi 1pP5TBBnC0gs2XOeGcIWlXj5+B/YEaICehIbTtxmBzlaQkBJ4vYGJxCTWSBBYsOXAIi1ghIn Zz5hmcAoOgvJ0FkIVbOQVEGUGEi8PzefGcLWlli28DWUrS+x8ctZRohWa4k9OyKRlSxg5FjF KFqcWpyUm25kpJdalJlcXJyfp5eXWrKJERixB7f8NtjB+PK54yFGAQ5GJR7eA1Y3ooRYE8uK K3MPMUpwMCuJ8IqfvR4lxJuSWFmVWpQfX1Sak1p8iFGag0VJnNfCb3OUkEB6YklqdmpqQWoR TJaJg1OqgTHhVcm9o8/73yuv/nu85s8D6cUHOg/VtO+3v8z59+nZBqb9gtutLu4vv749vGxe YYvx8+4rHOWp83wUm+7PMUmNt4vWPlbqeO+axrdJc/L2a5cyhe54Md3UTTOjqDUoj9n2e0aJ 3vnGv0+bPuxffv6jt4TTza8fV6xkqjltrp1jeVbxfmbLWjYlluKMREMt5qLiRABhNnzq1AIA AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ILSmTcVA6ws47OO9iJmyrbBTfhE>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 06:49:47 -0000

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

Hi,

>>> Because it's a generic term when specific ones would be better
>>>
>>> How do I know in which cases to use something more =93specific=94?
>>>
>>> Almost every case
>>>
>>> For example:
>>>
>>> "media associated with the BUNDLE group": Is media part of the group? O=
r, is there some other more specific word to use?
>>
>> "m=3D" section that is part of a bundle group
>>
>> Yes, but I am talking about the media. Is media part of the group?
>
> I would have to see the text in context.

E.g., section 1 contains the following sentence:

 =93The endpoints then use the BUNDLE addresses:ports for sending and
  receiving the bundled media associated with the BUNDLE group."

Regards,

Christer


--_000_D6FE16FE2E5F6christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <EA30F358FF78B644B28D3C3CE00DAB82@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 dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>
<div class=3D"h5">&gt;&gt;&gt; Because it's a generic term when specific on=
es would be better</div>
</div>
</div>
</div>
</div>
</span><span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>
<div class=3D"h5">&gt;&gt;&gt;<br>
&gt;&gt;&gt; How do I know in which cases to use something more =93specific=
=94?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Almost every case<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; For example:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&nbsp;&quot;media associated with the BUNDLE group&quot;: Is me=
dia part of the group? Or, is there some other more specific word to use?<b=
r>
&gt;&gt;<br>
&gt;&gt; &quot;m=3D&quot; section that is part of a bundle group<br>
&gt;&gt;</div>
</div>
<div>&gt;&gt; Yes, but I am talking about the media. Is media part of the g=
roup?</div>
<div>&gt;</div>
<div>&gt; I would have to see the text in context.</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
<div>
<div>E.g., section 1 contains the following sentence:</div>
<div>
<pre style=3D"font-variant-ligatures: normal; orphans: 2; widows: 2; word-w=
rap: break-word; white-space: pre-wrap;"> =93The endpoints then use the BUN=
DLE addresses:ports for sending and
  receiving the bundled media associated with the BUNDLE group.&quot;</pre>
</div>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra"><br>
</div>
</div>
</span>
</body>
</html>

--_000_D6FE16FE2E5F6christerholmbergericssoncom_--


From nobody Thu Apr 19 02:28:46 2018
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 032C112D868; Thu, 19 Apr 2018 02:28:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level: 
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 my9XG_FRK3Vm; Thu, 19 Apr 2018 02:28:43 -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 AC87C124C27; Thu, 19 Apr 2018 02:28:43 -0700 (PDT)
Received: from [10.0.2.161] (ip-57-232-239-173.texas.us.northamericancoax.com [173.239.232.57]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3J9SWa7011579 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 19 Apr 2018 04:28:34 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-57-232-239-173.texas.us.northamericancoax.com [173.239.232.57] claimed to be [10.0.2.161]
Content-Type: multipart/alternative; boundary=Apple-Mail-91DE3CD1-F3EF-4E2A-9E42-6FD5A4D58E42
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (15E216)
In-Reply-To: <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com>
Date: Thu, 19 Apr 2018 11:28:31 +0200
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <A8A3827C-D8AD-4DAE-BE81-2D577F8B4EBD@nostrum.com>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lMec4I70MkVBGgFl9E-UmLgPflI>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 09:28:45 -0000

--Apple-Mail-91DE3CD1-F3EF-4E2A-9E42-6FD5A4D58E42
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



On Apr 18, 2018, at 9:22 PM, Eric Rescorla <ekr@rtfm.com> wrote:

>> How is "applies" more specific than "associated"?
>=20
> The answer to both of these is the same. You are using the word associated=
 for a number of different things, and so having different terms is clearer.=

>=20
>>=20
>> I get that you don't like the use of the word "associated". But, in gener=
al, coming up with a bunch of different words just to get rid of "associated=
" doesn't make sense to me. It's a pure editorial choice, and every author h=
as his/her favourite preference, and I think having consistent terminology i=
s more important than finding the best word.
>=20
> It's not a pure editorial choice. It's a source of confusion to have an ov=
erloaded term.

I think it is an editorial choice. Furthermore, I think it=E2=80=99s a quest=
ion of style, in which the authors have a fair amount of latitude. Does anyo=
ne think that the choice is going to cause implementors to make material err=
ors?

Ben.=

--Apple-Mail-91DE3CD1-F3EF-4E2A-9E42-6FD5A4D58E42
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div></div><div><br></div><div><br>On Apr 1=
8, 2018, at 9:22 PM, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@r=
tfm.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">How is "applies" more specific than "associated"?<br></=
blockquote><div><br></div><div>The answer to both of these is the same. You a=
re using the word associated for a number of different things, and so having=
 different terms is clearer.</div><div><br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<br>
I get that you don't like the use of the word "associated". But, in general,=
 coming up with a bunch of different words just to get rid of "associated" d=
oesn't make sense to me. It's a pure editorial choice, and every author has h=
is/her favourite preference, and I think having consistent terminology is mo=
re important than finding the best word.<br>
</blockquote><div><br></div><div>It's not a pure editorial choice. It's a so=
urce of confusion to have an overloaded term.</div><div></div></div></blockq=
uote><br><div>I think it is an editorial choice. Furthermore, I think it=E2=80=
=99s a question of style, in which the authors have a fair amount of latitud=
e. Does anyone think that the choice is going to cause implementors to make m=
aterial errors?</div><div><br></div><div>Ben.</div></body></html>=

--Apple-Mail-91DE3CD1-F3EF-4E2A-9E42-6FD5A4D58E42--


From nobody Thu Apr 19 02:41:42 2018
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 2E92312D7EA; Thu, 19 Apr 2018 02:41:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wYycIwRXWVgJ; Thu, 19 Apr 2018 02:41:39 -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 8A5E2124C27; Thu, 19 Apr 2018 02:41:39 -0700 (PDT)
Received: from [10.0.2.111] (ip-32-232-239-173.texas.us.northamericancoax.com [173.239.232.32]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3J9fUmx013753 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 19 Apr 2018 04:41:32 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-32-232-239-173.texas.us.northamericancoax.com [173.239.232.32] claimed to be [10.0.2.111]
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (15E216)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se>
Date: Thu, 19 Apr 2018 11:41:30 +0200
Cc: Eric Rescorla <ekr@rtfm.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/PmwjwuEEh0zeRRoyefkVRA03NiY>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 09:41:41 -0000

On Apr 18, 2018, at 9:23 AM, Christer Holmberg <christer.holmberg@ericsson.c=
om> wrote:

>> This doesn't answer my question. Who, specifically, thinks that this term=
inology
>> of focusing on the address:port and not the m=3D section is good?
>=20
> Considering that the focus has been on the address and port since day one,=
 for 7 years, I think it is good. After all, while there is more to it than t=
he address:port, the main reason for BUNDLE is to be able to multiplex in a s=
ingle address:port.
>=20
> Now, we HAVE discussed changing "address:port" to "transport", but it woul=
d still not be about the m=3D section.
>=20
>>> Having said that, if we can change it with a search/replace operation I a=
m
>>> happy to discuss it. I THINK we could do that e.g., with "transport" or
>>> "3-tuple".=20
>>>=20
>>> But I don=C2=B9t want to make yet another re-write of the document just t=
o once
>>> again change the terminology.
>>=20
>> This document is going to be used by a lot of people. It's important that=
 it be
>> clear.
>=20
> I fully agree. But, I am not sure that endless re-writings the document is=
 going to achieve that.

I think this has turned into an argument about style. One usage may be more p=
leasing to the =E2=80=9Cear=E2=80=9D than the other, but I don=E2=80=99t see=
 issues of technical correctness or clarity here. As I asked for the the =E2=
=80=9Cassociated with=E2=80=9D question, is anyone arguing that the word cho=
ice here is likely to cause material implementation errors?

Ben.=


From nobody Thu Apr 19 02:56:27 2018
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 7D34912D883; Thu, 19 Apr 2018 02:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.877
X-Spam-Level: 
X-Spam-Status: No, score=-1.877 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=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 NijGWCR7V5gZ; Thu, 19 Apr 2018 02:56:21 -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 0A49312D88F; Thu, 19 Apr 2018 02:56:21 -0700 (PDT)
Received: from [10.0.2.129] (ip-27-232-239-173.texas.us.northamericancoax.com [173.239.232.27]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3J9uDpC016665 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 19 Apr 2018 04:56:15 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-27-232-239-173.texas.us.northamericancoax.com [173.239.232.27] claimed to be [10.0.2.129]
Content-Type: multipart/alternative; boundary=Apple-Mail-5BA61501-C02A-4D03-BDDB-2A6C3DE5EA5B
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (15E216)
In-Reply-To: <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com>
Date: Thu, 19 Apr 2018 11:56:12 +0200
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kRhXtYmbvTI83_VvRqiqauHinbc>
Subject: [MMUSIC] [ MMUSIC Chairs: Note action required ]. Re: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 09:56:22 -0000

--Apple-Mail-5BA61501-C02A-4D03-BDDB-2A6C3DE5EA5B
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

MMUSIC chairs, please see request below:

On Apr 17, 2018, at 8:18 PM, Eric Rescorla <ekr@rtfm.com> wrote:

>> >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>> >>>>> address:port, because if the peer rejects BUNDLE but accepts the m=3D=

>> >>>>> section then it's broken.
>> >>>>
>> >>>> Note that in this case the usage of BUNDLE has already been negotiat=
ed.
>> >>>> Then, if the answerer does not accept the new m=3D section into the B=
UNDLE
>> >>>> group, it needs to send an offer where it removes it, as described i=
n
>> >>>> section 8.3.3.
>> >>>
>> >>> Well, both of these options correspond to insisting that the m=3D sec=
tion
>> >>> be in the BUNDLE group. If I just want to suggest it, I would have to=
 provide
>> >>> a fresh unique address. Or are you saying that's impossible.
>> >>>
>> >> Yes.
>> >>
>> >> Previously, when the offerer wanted to add a new m- section to a BUNDL=
E
>> >> group, it had to choice of either assigning a unique address or a
>> >> previously negotiated bundle address.
>> >>
>> >> That option was removed as part of task (triggered by WGLC comments et=
c)
>> >
>> > That seems like a pretty material change. Was there a call for consensu=
s on that?
>>=20
>> No. But, the suggested changes were indicated on the list, there were pul=
l requests etc, so people were informed about it and had a chance to comment=
/object.
>=20
> Hmm... Ben, do you think these were properly surfaced to the WG?

I seem to recall non-trivial discussion about it on list, but I am not in a p=
osition to verify it prior to the telechat.=20

Chairs/shepherd: Please comment on whether you believe the aforementioned ch=
ange represents wg consensus.

Thanks!

Ben.

>=20
> -Ekr
>=20

--Apple-Mail-5BA61501-C02A-4D03-BDDB-2A6C3DE5EA5B
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>MMUSIC chairs, please see request below:</div><div><br></div><div>On Apr 17, 2018, at 8:18 PM, Eric Rescorla &lt;<a href="mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt; wrote:</div><div><br></div><blockquote type="cite"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">&gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn't sound right. You can't use the existing<br>
&gt;&gt;&gt;&gt;&gt; address:port, because if the peer rejects BUNDLE but accepts the m=<br>
&gt;&gt;&gt;&gt;&gt; section then it's broken.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that in this case the usage of BUNDLE has already been negotiated.<br>
&gt;&gt;&gt;&gt; Then, if the answerer does not accept the new m= section into the BUNDLE<br>
&gt;&gt;&gt;&gt; group, it needs to send an offer where it removes it, as described in<br>
&gt;&gt;&gt;&gt; section 8.3.3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Well, both of these options correspond to insisting that the m= section<br>
&gt;&gt;&gt; be in the BUNDLE group. If I just want to suggest it, I would have to provide<br>
&gt;&gt;&gt; a fresh unique address. Or are you saying that's impossible.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Yes.<br>
&gt;&gt;<br>
&gt;&gt; Previously, when the offerer wanted to add a new m- section to a BUNDLE<br>
&gt;&gt; group, it had to choice of either assigning a unique address or a<br>
&gt;&gt; previously negotiated bundle address.<br>
&gt;&gt;<br>
&gt;&gt; That option was removed as part of task (triggered by WGLC comments etc)<br>
&gt;<br>
&gt; That seems like a pretty material change. Was there a call for consensus on that?<br>
<br>
</div></div>No. But, the suggested changes were indicated on the list, there were pull requests etc, so people were informed about it and had a chance to comment/object.<br></blockquote><div><br></div><div>Hmm... Ben, do you think these were properly surfaced to the WG?</div></div></blockquote><div><br></div><div>I seem to recall non-trivial discussion about it on list, but I am not in a position to verify it prior to the telechat.&nbsp;</div><div><br></div><div>Chairs/shepherd: Please comment on whether you believe the aforementioned change represents wg consensus.</div><div><br></div><div>Thanks!</div><div><br></div><div>Ben.</div><br><blockquote type="cite"><div><div><br></div><div>-Ekr</div><div><br></div><div></div></div></blockquote></body></html>
--Apple-Mail-5BA61501-C02A-4D03-BDDB-2A6C3DE5EA5B--


From nobody Thu Apr 19 05:33:08 2018
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 3BD9A1271FD for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 05:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id veAD7gMZFk_c for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 05:33:05 -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 7F50212D959 for <mmusic@ietf.org>; Thu, 19 Apr 2018 05:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524140758; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=5AHJtHk1is8lMnNmeB7f7SxOl6q9nB8+WQPILD40+Qg=; b=e6b6GaxB0UnGtzr1Nl0PuiCr0Yvi5SjKq88HnFHqpEKCH3WsIIu7euBK/2/uTLEs ASqq0pHKmb5I9pDkGZ5eHNECYauIRdQIZMlseOqwpKMVtLI4SGik1Rssk0wNwYZ6 woadpO3LdqyEdzaXNfk9HKYcLtjP7kB/46PCM+B1Alc=;
X-AuditID: c1b4fb25-88bff70000006561-c7-5ad88ad6443e
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E4.60.25953.6DA88DA5; Thu, 19 Apr 2018 14:25:58 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0382.000; Thu, 19 Apr 2018 14:25:58 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Alexey Melnikov <aamelnikov@fastmail.fm>, Benjamin Kaduk <kaduk@mit.edu>, "Spencer Dawkins at IETF" <spencerdawkins.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, "Adam Roach" <adam@nostrum.com>, =?iso-8859-1?Q?Mirja_K=FChlewind?= <ietf@kuehlewind.net>, Warren Kumari <warren@kumari.net>
Thread-Topic: draft-ietf-mmusic-sdp-bundle-negotiation-49: Pull request based on IESG review
Thread-Index: AQHT19mRV9cz/eK1qk+B6fLJavAdBg==
Date: Thu, 19 Apr 2018 12:25:58 +0000
Message-ID: <D6FE6373.2E672%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <EA1EF5B67A6C8448A2F681C58895F530@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNIsWRmVeSWpSXmKPExsUyM2K7hO61rhtRBkuX6Fvsf3+IyWLP30Xs FtNnvWOzWPH6HLvF+wu6FjP+TGS2eHH9I7PF8o0zmSzO71zPZDF1+WMWi2VT9jBbHD52mcmB x2PK742sHjtPHWDz2DnrLrvHkiU/mTxaPi5k9bh94w+7R9OZo8wes3Y+YfGY/LiNOYAzissm JTUnsyy1SN8ugSvjxrQDTAWfWCr+/OphaWD8wNzFyMkhIWAi8WHJY5YuRi4OIYEjjBLn1n5l g3AWM0p8W93D1MXIwcEmYCHR/U8bpEFEQEbiS/sUZpAaZoG5LBIL218wgSSEBSIlVi15zwhR FCcx+8lmJghbT2LN8bNgc1gEVCXObLEDCfMKWEs82/eHHcRmFBCT+H5qDVg5s4C4xK0n85kg jhOQWLLnPNShohIvH/9jBbFFgUZuOHGbHWSkhICSxO0NThCtehI3pk5hg7CtJXZ0tDJC2NoS yxa+ZoZYKyhxcuYTlgmMorOQbJuFpH0WkvZZSNpnIWlfwMi6ilG0OLU4KTfdyFgvtSgzubg4 P08vL7VkEyMwyg9u+a26g/HyG8dDjAIcjEo8vDlNN6KEWBPLiitzDzFKcDArifB6twOFeFMS K6tSi/Lji0pzUosPMUpzsCiJ8z403xwlJJCeWJKanZpakFoEk2Xi4JRqYEzL+Mus3Rc80WXL 1AKH5rMrW0VmP5fKTOuv8etu83j7K/eazGKBOL+u9ydEdKPP1MQsC+e+Xbrvky230PeobRs2 8utcFyxP2KFzNCBT1/DYH6l6hojmlhWs349/zD2y8vzCpBmiGj43C8tOnK5du8rrY/v23iKp EyLJPT6r1u853OLGna6yQYmlOCPRUIu5qDgRAG1MDdDuAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/i6zgxYDFcFkHM-OIOLGju-sb1HU>
Subject: [MMUSIC] draft-ietf-mmusic-sdp-bundle-negotiation-49: Pull request based on IESG review
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 12:33:06 -0000

Hi,

Based on the IESG reviews, I have created a pull request:

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


The pull request does NOT contain changes related to the following
comments given by Ekr:

- usage of "address:port"
- usage of "associated"
- modify content within section 1 into a numbered list

In addition, as identified by myself when addressing Ekr=B9s comments, ther=
e
may be a need to modify section 8.3. The pull request does not yet do that.

Finally, the pull request does not contain changes related to section 10
(I am waiting for input from others).

Regards,

Christer


From nobody Thu Apr 19 05:47:03 2018
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 10F5512D95C for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 05:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lum0nR4jVZsh for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 05:46:50 -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 AB5661271FD for <mmusic@ietf.org>; Thu, 19 Apr 2018 05:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524142008; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=GSCUEt5szJSZm+RzG9o10U9GMPj993gO0G/a53yisIY=; b=XZ8AHNmu7XdeZHvA8De7DyvGcJ+24Zew35ItgWeBv9DsROLd+ktphgVZ/mlzyRTF J0AEqNuu23EKdJxieS098TOr0/ghPs2XbIz4aVXWmRVBSKF1isOLk/zgr/RF/j12 XgtWjXfIKkqEutK/gRosBNdYE61US6eWmqage4Qd5BI=;
X-AuditID: c1b4fb30-0dfff70000007681-71-5ad88fb7f292
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id A0.01.30337.7BF88DA5; Thu, 19 Apr 2018 14:46:47 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Thu, 19 Apr 2018 14:46:47 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Eric Rescorla <ekr@rtfm.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT - Introduction
Thread-Index: AQHT19x6FOX0P+1llk+ClT1GtRE4kg==
Date: Thu, 19 Apr 2018 12:46:47 +0000
Message-ID: <D6FE6A0F.2E68E%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <657FC182062B8D4AA9CBCE7798D8730C@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrIIsWRmVeSWpSXmKPExsUyM2K7je72/htRBpsabSymz3rHZrHi9Tl2 i/cXdC1m/JnIbHF+53omi6nLH7M4sHlM+b2R1WPJkp9MHpMftzEHMEdx2aSk5mSWpRbp2yVw ZezeM4ux4DFPxaq9r1kaGFu5uhg5OSQETCRmXGhi7mLk4hASOMIosfDuFjYIZzGjRMeU44xd jBwcbAIWEt3/tEFMEYECiXMvYkFKmAW+MEo8+3yUEcQRFuhhlDhyvoEFxBER6GWUuPRvIhvI ChEBPYk/cy4wgtgsAqoSO9/PBIvzClhLtC/fwQpiMwqISXw/tYYJxGYWEJe49WQ+E8R5AhJL 9pxnhrBFJV4+/gdWLwo0c8OJ2+wgF0kIKEnc3uAE0Wog8f7cfGYI21qi7epRVghbW2LZwtfM EGsFJU7OfMIygVF0FpJts5C0z0LSPgtJ+ywk7QsYWVcxihanFiflphsZ6aUWZSYXF+fn6eWl lmxiBEbcwS2/DXYwvnzueIhRgINRiYdXvvFGlBBrYllxZe4hRgkOZiURXu92oBBvSmJlVWpR fnxRaU5q8SFGaQ4WJXFeC7/NUUIC6YklqdmpqQWpRTBZJg5OqQbGmHgdtRh5EX+/BD/f2Lnt Ph5XW5VDmZ/FcU2YW54Rbt4p3H3doecwu2i9iCl3XdG70NM9cxNNVDwvb+NyrXz8dfO7x4un KsdKcy08dP4G7+z7nF6Wt83Lgg3WPP0r7TfZWzFFwKqpZZXMcVWed3yy73nZm8RifTUS/XaV rDY/mWGX5LB0qRJLcUaioRZzUXEiALUebwq0AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2ZLbILV066mLgs1nMaW7Oabsclo>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT - Introduction
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 12:46:52 -0000

Hi,

>>>can be used to request that specific media is only used if the "m=3D"
>>> section describing the media is kept within a BUNDLE group.
>>>  =20
>>> This specification updates RFC 3264 [RFC3264], to allow assigning a
>>> zero port value to a "m=3D" section without meaning that the media
>>> described by the "m=3D" section is disabled or rejected.
>>=20
>> 1. Bundle lets you have multiple SDP m=3D sections on a single 5-tuple
>> 2. The underling mechanism here is that you put those m=3D sections in t=
he
>> same BUNDLE group
>> 3. In order to facilitate demuxing, we define a new RTP extension for
>> MID.
>> 4. It is sometimes desirable to say that an m=3D section should only be
>> negotiated if it can be bundled.
>> This is done with port=3D0 and a=3Dbundle-only.
>>
>>> can be used to request that specific media is only used if the "m=3D"
>>> section describing the media is kept within a BUNDLE group.
>>>  =20
>>> This specification updates RFC 3264 [RFC3264], to allow assigning a
>>> zero port value to a "m=3D" section without meaning that the media
>>> described by the "m=3D" section is disabled or rejected.
>>=20
>> This section is kind of a laundry list. I think it would be helpful to
>> break it out conceptually. Specifically.
>> 1.
>> 2.
>> 3.
>
>I will take a look.

I had a look at this, but I am not sure how to implement what you suggest.

I could combine the 3rd and 4th paragraph, but I don=B9t think that would
help much.

Also, some paragraphs may not even be needed in the Introduction, but
people asked them to be there, so=8A

Regards,

Christer


From nobody Thu Apr 19 06:27:55 2018
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 516B212DA01 for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 06:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 34yQLB3J_mjt for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 06:27:48 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 B6B2B12DA00 for <mmusic@ietf.org>; Thu, 19 Apr 2018 06:27:46 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id e23-v6so4823728oiy.1 for <mmusic@ietf.org>; Thu, 19 Apr 2018 06:27:46 -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=M5v+JQ462EW/+0noyYx2HzB15ys+XWVbnAmZn47LbTk=; b=1fEEYH0EmCsO7Nb7mNTqxLMMZSjoDK8hrIapVACC0P6QnMKeBclj8bTgZChOzB6BbT i0GKnsfQTr3i20ZDm3NIzPlMORABC5Z6AGmGm32YSgFEOaA+FS3I/Lhbo9yQ/niRqjpV feOjURrCbl7YI9q5lZqRSxkKP049XJSg9BMGtjkgFkXAvQqbW6wwxaiK2EAYh/xSFuU6 TZlwsAAPSDNNQ1FuDZpQ8lPx5EB6MwF/EGQiZXm8MeaOACFrZD5o5Y/XdtGfv/TPYCyf dbd9lB/a3dVpIGdTXwiVbg2FyVRhAov+su2mFh2/YEBhINCeF2R8x6FlvoQL9f5U6mAy Z2EQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=M5v+JQ462EW/+0noyYx2HzB15ys+XWVbnAmZn47LbTk=; b=sYnZes9Z/wFZRN69HGAE9WvHHyBaVMygB6pQqpQdgos3ESSCmTLqJDXYFXgeDOwRMO BU5Wgcx6yOnlLyBkcmtQHvtf0VkE5U66Odw8iUmy+EiNpBp22JLreQUXbosLgJppm+tr RvMF0jVstYS8ZFl9+C5KOHQZX0Lf+HtjudW+leT15ptR0spDPPcl0muBft2/6XECRKMm 4DH6ecFChqAr72IlMpa+RRcL9I7GB0SIJykgXabbyMkqVj4KS8NJHCDwm4SCVh+tdiDB HSbWoKNaj5l/7cD894oSmkQzSn/ojS6qem1SJ//NhEVItOttt0KKEdkM5Z9njcUJGgP5 MPFw==
X-Gm-Message-State: ALQs6tCpbLHlg1X67JTVI4gyiynIr0wYRcZgly7/hnKFZukkTwQJQId9 kaOvCFPHzEiYqUZhjyBngwxT5XsADlchjxccXkJ5pQ==
X-Google-Smtp-Source: AIpwx4+xruQ6QgkGRnq8TEX8QtmuZ89tQh1N//uRDIpNHKpEmHmvYr3fUlLd9s0U48DU9Q3IkJqyPNcwiao6AjB+98s=
X-Received: by 2002:aca:5405:: with SMTP id i5-v6mr3824481oib.262.1524144466011;  Thu, 19 Apr 2018 06:27:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Thu, 19 Apr 2018 06:27:05 -0700 (PDT)
In-Reply-To: <D6FE16FE.2E5F6%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com> <D6FE16FE.2E5F6%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 19 Apr 2018 06:27:05 -0700
Message-ID: <CABcZeBPDpoMHOuOJ0kgMfQfNWJdtrv=d733yjasEL6sordPumw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007bd69b056a338978"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sXBTzMVMg1j5Ny2uoK9mVy1duS0>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 13:27:49 -0000

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

On Wed, Apr 18, 2018 at 11:49 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> >>> Because it's a generic term when specific ones would be better
> >>>
> >>> How do I know in which cases to use something more =E2=80=9Cspecific=
=E2=80=9D?
> >>>
> >>> Almost every case
> >>>
> >>> For example:
> >>>
> >>> "media associated with the BUNDLE group": Is media part of the group?
> Or, is there some other more specific word to use?
> >>
> >> "m=3D" section that is part of a bundle group
> >>
> >> Yes, but I am talking about the media. Is media part of the group?
> >
> > I would have to see the text in context.
>
> E.g., section 1 contains the following sentence:
>
>  =E2=80=9CThe endpoints then use the BUNDLE addresses:ports for sending a=
nd
>   receiving the bundled media associated with the BUNDLE group."
>
> This actually seems like a time that "associated" would be fine.

-Ekr

Regards,
>
> Christer
>
>

--0000000000007bd69b056a338978
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, Apr 18, 2018 at 11:49 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft: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><span class=3D"">
<div><br>
</div>
<span id=3D"m_3685953154636705214OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>
<div class=3D"m_3685953154636705214h5">&gt;&gt;&gt; Because it&#39;s a gene=
ric term when specific ones would be better</div>
</div>
</div>
</div>
</div>
</span><span id=3D"m_3685953154636705214OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>
<div class=3D"m_3685953154636705214h5">&gt;&gt;&gt;<br>
&gt;&gt;&gt; How do I know in which cases to use something more =E2=80=9Csp=
ecific=E2=80=9D?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Almost every case<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; For example:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0&quot;media associated with the BUNDLE group&quot;: Is me=
dia part of the group? Or, is there some other more specific word to use?<b=
r>
&gt;&gt;<br>
&gt;&gt; &quot;m=3D&quot; section that is part of a bundle group<br>
&gt;&gt;</div>
</div>
<div>&gt;&gt; Yes, but I am talking about the media. Is media part of the g=
roup?</div>
<div>&gt;</div>
<div>&gt; I would have to see the text in context.</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>
<div>E.g., section 1 contains the following sentence:</div>
<div>
<pre style=3D"font-variant-ligatures:normal;word-wrap:break-word;white-spac=
e:pre-wrap"> =E2=80=9CThe endpoints then use the BUNDLE addresses:ports for=
 sending and
  receiving the bundled media associated with the BUNDLE group.&quot;</pre>=
</div></div></div></blockquote><div>This actually seems like a time that &q=
uot;associated&quot; would be fine.<br></div><div><br></div><div>-Ekr</div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break=
-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif"><div>=
<div>
</div>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<span id=3D"m_3685953154636705214OLK_SRC_BODY_SECTION">
<div dir=3D"ltr">
<div class=3D"gmail_extra"><br>
</div>
</div>
</span>
</div>

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

--0000000000007bd69b056a338978--


From nobody Thu Apr 19 06:29:32 2018
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 89BAB12DA17 for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 06:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 MpUMYxqHXA9R for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 06:29:27 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 C811012D9FF for <mmusic@ietf.org>; Thu, 19 Apr 2018 06:29:24 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id e11-v6so4808455oii.11 for <mmusic@ietf.org>; Thu, 19 Apr 2018 06:29:24 -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=H4+rNcKAmQ4oTdVmovcvtAXgIegSUMO0KMPRGu1822w=; b=na/nfVGg3rGOwZRxZ9HE3O44f6Ku4P93leVAGF15Hvcbzw5mLUMmtni+qKJe2URPmQ DPBWh8EQvQB9ZDne2HcirnXhsNHMGltI4Nauxyb4ZfwmdCa+BNyBk1m+DTWPl6+ya2Ns qkjcMBzKBcMYbkWin0uNeJ1xYjuAIxPtO/9jdSHqU32rrzwRik/slypuVf3y/sUhA6ST vbhv5Vt8Kun5zRenCi86pqP6juF5od9iFUGQyuimMtLc+F88wJm3JgKbwrDZBlZujZNi RbU5OmFjL2Xsoe2v3PfXHH8Gqp8oOMMKqD1fSmB5EeQWH0B6LTDzZh5q+ggk6uOKzjgC h+Dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=H4+rNcKAmQ4oTdVmovcvtAXgIegSUMO0KMPRGu1822w=; b=iFR7m/v3gQ06NgwZZ84VgHDmKpsxjPHl9MMKlG7AuJMTOugAA8x5FfFD6H4knsieZd KmoIDbqLuJSegzQwVkG/X/OAva5XiHyMdkrwmNAsQajNAb1XqGIYRGefoH0FKjsfDEOE OvsaPMJVy6sraqzgmAzgEJKVkdYVf6CSdk022tE4Lk+tPKWZU18jFRcXsQz82PYbW0wJ PR6mzsJcbij3IsEfl6HGUKEwiLcBktfihqXWLflnGpKupkfEw0WrE0gKlvdwyW/iC1t6 e+Vq5OW9GPg/UMo9asaNUnpTKdU4tVdgbgn06ld3nnDM5b2P0g6OQDpU88mIQYSpMRSZ bSKg==
X-Gm-Message-State: ALQs6tCrOWLpbfSRM7N81zN2y2JVSUwY33sZqE0zAv8Q14jrF7E2OeSk q9dr0FgNk7xQ30VatFoycIlsuqEP2Ywk2idSQ922btUj
X-Google-Smtp-Source: AIpwx4+rXUrYd7BvwxqzrCvI9vY+3g7mGds2NykBXMfz2+4xWmsouEi1c62WOREwiHJDaaWOam6qwBod+CSrC3Tisk0=
X-Received: by 2002:aca:c744:: with SMTP id x65-v6mr3475263oif.43.1524144564135;  Thu, 19 Apr 2018 06:29:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Thu, 19 Apr 2018 06:28:43 -0700 (PDT)
In-Reply-To: <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 19 Apr 2018 06:28:43 -0700
Message-ID: <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>,  "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000055029c056a338f33"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qwe1rU8Pn94ivKacarEp23scNAM>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 13:29:29 -0000

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

On Thu, Apr 19, 2018 at 2:41 AM, Ben Campbell <ben@nostrum.com> wrote:

>
>
> On Apr 18, 2018, at 9:23 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> >> This doesn't answer my question. Who, specifically, thinks that this
> terminology
> >> of focusing on the address:port and not the m=3D section is good?
> >
> > Considering that the focus has been on the address and port since day
> one, for 7 years, I think it is good. After all, while there is more to i=
t
> than the address:port, the main reason for BUNDLE is to be able to
> multiplex in a single address:port.
> >
> > Now, we HAVE discussed changing "address:port" to "transport", but it
> would still not be about the m=3D section.
> >
> >>> Having said that, if we can change it with a search/replace operation
> I am
> >>> happy to discuss it. I THINK we could do that e.g., with "transport" =
or
> >>> "3-tuple".
> >>>
> >>> But I don=C2=B9t want to make yet another re-write of the document ju=
st to
> once
> >>> again change the terminology.
> >>
> >> This document is going to be used by a lot of people. It's important
> that it be
> >> clear.
> >
> > I fully agree. But, I am not sure that endless re-writings the document
> is going to achieve that.
>
> I think this has turned into an argument about style. One usage may be
> more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but I don=E2=
=80=99t see issues of
> technical correctness or clarity here. As I asked for the the =E2=80=9Cas=
sociated
> with=E2=80=9D question, is anyone arguing that the word choice here is li=
kely to
> cause material implementation errors?
>

I don't think "address:port" versus "transport" will, but I do think
"address:port" versus "m=3Dsection" or "transport parameters" will, and in
fact I identified a material issue around trickle the other day, that I
haven't seen a response to.

-Ekr

Ben.
>

--00000000000055029c056a338f33
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, Apr 19, 2018 at 2:41 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:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
On Apr 18, 2018, at 9:23 AM, Christer Holmberg &lt;<a href=3D"mailto:christ=
er.holmberg@ericsson.com">christer.holmberg@ericsson.<wbr>com</a>&gt; wrote=
:<br>
<br>
&gt;&gt; This doesn&#39;t answer my question. Who, specifically, thinks tha=
t this terminology<br>
&gt;&gt; of focusing on the address:port and not the m=3D section is good?<=
br>
&gt; <br>
&gt; Considering that the focus has been on the address and port since day =
one, for 7 years, I think it is good. After all, while there is more to it =
than the address:port, the main reason for BUNDLE is to be able to multiple=
x in a single address:port.<br>
&gt; <br>
&gt; Now, we HAVE discussed changing &quot;address:port&quot; to &quot;tran=
sport&quot;, but it would still not be about the m=3D section.<br>
&gt; <br>
&gt;&gt;&gt; Having said that, if we can change it with a search/replace op=
eration I am<br>
&gt;&gt;&gt; happy to discuss it. I THINK we could do that e.g., with &quot=
;transport&quot; or<br>
&gt;&gt;&gt; &quot;3-tuple&quot;. <br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; But I don=C2=B9t want to make yet another re-write of the docu=
ment just to once<br>
&gt;&gt;&gt; again change the terminology.<br>
&gt;&gt; <br>
&gt;&gt; This document is going to be used by a lot of people. It&#39;s imp=
ortant that it be<br>
&gt;&gt; clear.<br>
&gt; <br>
&gt; I fully agree. But, I am not sure that endless re-writings the documen=
t is going to achieve that.<br>
<br>
</span>I think this has turned into an argument about style. One usage may =
be more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but I don=E2=
=80=99t see issues of technical correctness or clarity here. As I asked for=
 the the =E2=80=9Cassociated with=E2=80=9D question, is anyone arguing that=
 the word choice here is likely to cause material implementation errors?<sp=
an class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquote>=
<div><br></div><div>I don&#39;t think &quot;address:port&quot; versus &quot=
;transport&quot; will, but I do think &quot;address:port&quot; versus &quot=
;m=3Dsection&quot; or &quot;transport parameters&quot; will, and in fact I =
identified a material issue around trickle the other day, that I haven&#39;=
t seen a response to.</div><div><br></div><div>-Ekr</div><div><br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=3D"#888888">
Ben.<br>
</font></span></blockquote></div><br></div></div>

--00000000000055029c056a338f33--


From nobody Thu Apr 19 06:35:27 2018
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 BE19112D9FF for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 06:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7HOJ7QJz5PPe for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 06:35: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 CB7E312DA00 for <mmusic@ietf.org>; Thu, 19 Apr 2018 06:35:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524144915; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3PKBa9O3lkkfyHFHv2Z2OSnWFWnoAR3bzarEBFAOCmo=; b=K3uGVWACWzQtPiK2inlLCHCcCJKUkjJAn7uqxFJkj1VO+MlxRHzAjePffa6It+NX Bh7fim1TXsSbn7EKDezaW4dpZF7SP2vzrh8HX5lGh8rNz33ECXCiTzM/kRc3302O 2ZyrY53dfd05jR0X/1kLmzDLp10GsSFkaHX/Ne3A9F4=;
X-AuditID: c1b4fb3a-ae7ff7000000795a-a3-5ad89b124416
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 2D.9C.31066.21B98DA5; Thu, 19 Apr 2018 15:35:15 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0382.000; Thu, 19 Apr 2018 15:35:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, Ben Campbell <ben@nostrum.com>
CC: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseCAAZvZAIAAP3yAgAA0rgA=
Date: Thu, 19 Apr 2018 13:35:14 +0000
Message-ID: <D6FE753F.2E6A0%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com>
In-Reply-To: <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D6FE753F2E6A0christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHIsWRmVeSWpSXmKPExsUyM2J7iK7w7BtRBn1bOC32/F3EbjG/8zS7 xfRZ79gsVrw+x27x/oKuxYw/E5ktzu9cz2QxdfljFgcOjym/N7J6LFnyk8lj1s4nLB6TH7cx B7BEcdmkpOZklqUW6dslcGWsv3eCteCTRcXLM/uYGhjnm3cxcnJICJhI/LrXy9bFyMUhJHCE UeLg3S9sIAkhgcWMEnd/K3cxcnCwCVhIdP/TBgmLCDhInJnQyApSzyywnkni7uq7jCAJYYF0 iRsPFrGA1IsIZEjcf5AJUZ8kcX79LTaQMIuAqsSfNfYgYV4Ba4kV948yQaz9zyyx8cdvFpAE p0CgxKorx5hBbEYBMYnvp9YwgdjMAuISt57MZ4K4WUBiyZ7zzBC2qMTLx/9YQWxRAT2JDSdu s4PskhBQkri9wQnEZBZIkNj2qxxiraDEyZlPWCYwis5CMnQWQtUsJFUQJVoSX37sY4OwFSWm dD9khyjXlHjzsBYibC1x+OgrFmQlCxg5VjGKFqcWF+emGxnppRZlJhcX5+fp5aWWbGIExvLB Lb+tdjAefO54iFGAg1GJh5er6UaUEGtiWXFl7iFGCQ5mJRFe73agEG9KYmVValF+fFFpTmrx IUZpDhYlcV6nNIsoIYH0xJLU7NTUgtQimCwTB6dUA2PkXid79m/ml7s28fjL/WBVeL7Frdu8 aOvRmj3NZz7vVLS9dzgiePVHK6aYqxGt/PxRemZG8x1/cZxy4rl7ZN3Sig91lyu/cx2TsamR i/ML3qm+4OeKYO/ebzc75prkS527VbtEhafwi8msBc888/Pmyn/9+TjGcFuos7uRwIXAz+ZM hhef8iqxFGckGmoxFxUnAgD9gVt/4QIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/kD0U4r7EEkSf7PiD0uZRzhLwMk0>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 13:35:21 -0000

--_000_D6FE753F2E6A0christerholmbergericssoncom_
Content-Type: text/plain; charset="euc-kr"
Content-Transfer-Encoding: base64

SGksDQoNCj4+Pj4+IFRoaXMgZG9lc24ndCBhbnN3ZXIgbXkgcXVlc3Rpb24uIFdobywgc3BlY2lm
aWNhbGx5LCB0aGlua3MgdGhhdCB0aGlzIHRlcm1pbm9sb2d5DQo+Pj4+PiBvZiBmb2N1c2luZyBv
biB0aGUgYWRkcmVzczpwb3J0IGFuZCBub3QgdGhlIG09IHNlY3Rpb24gaXMgZ29vZD8NCj4+Pj4N
Cj4+Pj4gQ29uc2lkZXJpbmcgdGhhdCB0aGUgZm9jdXMgaGFzIGJlZW4gb24gdGhlIGFkZHJlc3Mg
YW5kIHBvcnQgc2luY2UgZGF5IG9uZSwgZm9yIDcgeWVhcnMsIEkgdGhpbmsgaXQgaXMgZ29vZC4g
QWZ0ZXIgYWxsLCB3aGlsZSB0aGVyZSBpcyBtb3JlIHRvIGl0IHRoYW4gdGhlIGFkZHJlc3M6cG9y
dCwgdGhlIG1haW4gcmVhc29uIGZvciBCVU5ETEUgaXMgdG8gYmUgYWJsZSB0byBtdWx0aXBsZXgg
aW4gYSBzaW5nbGUgYWRkcmVzczpwb3J0Lg0KPj4+Pg0KPj4+PiBOb3csIHdlIEhBVkUgZGlzY3Vz
c2VkIGNoYW5naW5nICJhZGRyZXNzOnBvcnQiIHRvICJ0cmFuc3BvcnQiLCBidXQgaXQgd291bGQg
c3RpbGwgbm90IGJlIGFib3V0IHRoZSBtPSBzZWN0aW9uLg0KPj4+Pg0KPj4+Pj4+IEhhdmluZyBz
YWlkIHRoYXQsIGlmIHdlIGNhbiBjaGFuZ2UgaXQgd2l0aCBhIHNlYXJjaC9yZXBsYWNlIG9wZXJh
dGlvbiBJIGFtDQo+Pj4+Pj4gaGFwcHkgdG8gZGlzY3VzcyBpdC4gSSBUSElOSyB3ZSBjb3VsZCBk
byB0aGF0IGUuZy4sIHdpdGggInRyYW5zcG9ydCIgb3INCj4+Pj4+PiAiMy10dXBsZSIuDQo+Pj4+
Pg0KPj4+Pj4gQnV0IEkgZG9uqfZ0IHdhbnQgdG8gbWFrZSB5ZXQgYW5vdGhlciByZS13cml0ZSBv
ZiB0aGUgZG9jdW1lbnQganVzdCB0byBvbmNlDQo+Pj4+PiBhZ2FpbiBjaGFuZ2UgdGhlIHRlcm1p
bm9sb2d5Lg0KPj4+Pg0KPj4+PiBUaGlzIGRvY3VtZW50IGlzIGdvaW5nIHRvIGJlIHVzZWQgYnkg
YSBsb3Qgb2YgcGVvcGxlLiBJdCdzIGltcG9ydGFudCB0aGF0IGl0IGJlDQo+Pj4+IGNsZWFyLg0K
Pj4+Pg0KPj4+ICBJIGZ1bGx5IGFncmVlLiBCdXQsIEkgYW0gbm90IHN1cmUgdGhhdCBlbmRsZXNz
IHJlLXdyaXRpbmdzIHRoZSBkb2N1bWVudCBpcyBnb2luZyB0byBhY2hpZXZlIHRoYXQuDQo+Pg0K
Pj4gSSB0aGluayB0aGlzIGhhcyB0dXJuZWQgaW50byBhbiBhcmd1bWVudCBhYm91dCBzdHlsZS4g
T25lIHVzYWdlIG1heSBiZSBtb3JlIHBsZWFzaW5nIHRvIHRoZSChsGVhcqGxIHRoYW4gdGhlIG90
aGVyLCBidXQgSSBkb26hr3Qgc2VlIGlzc3VlcyBvZiB0ZWNobmljYWwgY29ycmVjdG5lc3Mgb3Ig
Y2xhcml0eSBoZXJlLiBBcyBJIGFza2VkIGZvciB0aGUgdGhlIKGwYXNzb2NpYXRlZCB3aXRoobEg
cXVlc3Rpb24sIGlzIGFueW9uZSBhcmd1aW5nIHRoYXQgdGhlIHdvcmQgY2hvaWNlIGhlcmUgaXMg
bGlrZWx5IHRvIGNhdXNlIG1hdGVyaWFsIGltcGxlbWVudGF0aW9uIGVycm9ycz8NCj4NCj4gSSBk
b24ndCB0aGluayAiYWRkcmVzczpwb3J0IiB2ZXJzdXMgInRyYW5zcG9ydCIgd2lsbCwgYnV0IEkg
ZG8gdGhpbmsgImFkZHJlc3M6cG9ydCIgdmVyc3VzICJtPXNlY3Rpb24iIG9yICJ0cmFuc3BvcnQg
cGFyYW1ldGVycyIgd2lsbCwgYW5kIGluIGZhY3QgSSBpZGVudGlmaWVkIGEgbWF0ZXJpYWwgaXNz
dWUgYXJvdW5kIHRyaWNrbGUgdGhlIG90aGVyIGRheSwgdGhhdCBJIGhhdmVuJ3Qgc2VlbiBhIHJl
c3BvbnNlIHRvLg0KDQpNeSBzdWdnZXN0aW9uIHdhcyB0byBhZGQgdGV4dCBhYm91dCB0aGUgc3Bl
Y2lhbCBjYXNlIG9mIHBvcnQgOSBhbmQgSVAgYWRkcmVzcyAwLjAuMC4wLg0KDQpCZWNhdXNlLCB3
aGVuIHlvdSB1c2UgdHJpY2tsZSwgdGhlIG9mZmVyIG1heSBub3QgY29udGFpbiBhbnkgYWRkcmVz
cyBpbmZvcm1hdGlvbiBhdCBhbGwgKHlvdSBjYW4gc2VuZCBhbiBvZmZlciB3aXRob3V0IGFueSBj
YW5kaWRhdGVzKSwgc28gaXQgaXMgYSBzcGVjaWFsIGNhc2Ugbm8gbWF0dGVyIHdoYXQuDQoNClJl
Z2FyZHMsDQoNCkNocmlzdGVyDQoNCg==

--_000_D6FE753F2E6A0christerholmbergericssoncom_
Content-Type: text/html; charset="euc-kr"
Content-ID: <017626F8DD6E1146B3AF4FBD97A8D5DF@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PWV1Yy1rciI+DQo8L2hlYWQ+DQo8Ym9keSBzdHlsZT0id29yZC13
cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1i
cmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTog
MTRweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NCjxkaXY+SGksPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+DQo8
ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+DQo8ZGl2PjxzcGFuIGNsYXNzPSIiPiZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IFRoaXMgZG9lc24ndCBhbnN3ZXIgbXkgcXVlc3Rpb24uIFdobywgc3BlY2lmaWNh
bGx5LCB0aGlua3MgdGhhdCB0aGlzIHRlcm1pbm9sb2d5PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyZn
dDsgb2YgZm9jdXNpbmcgb24gdGhlIGFkZHJlc3M6cG9ydCBhbmQgbm90IHRoZSBtPSBzZWN0aW9u
IGlzIGdvb2Q/PGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyA8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IENv
bnNpZGVyaW5nIHRoYXQgdGhlIGZvY3VzIGhhcyBiZWVuIG9uIHRoZSBhZGRyZXNzIGFuZCBwb3J0
IHNpbmNlIGRheSBvbmUsIGZvciA3IHllYXJzLCBJIHRoaW5rIGl0IGlzIGdvb2QuIEFmdGVyIGFs
bCwgd2hpbGUgdGhlcmUgaXMgbW9yZSB0byBpdCB0aGFuIHRoZSBhZGRyZXNzOnBvcnQsIHRoZSBt
YWluIHJlYXNvbiBmb3IgQlVORExFIGlzIHRvIGJlIGFibGUgdG8gbXVsdGlwbGV4IGluIGEgc2lu
Z2xlIGFkZHJlc3M6cG9ydC48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IDxicj4NCiZndDsmZ3Q7Jmd0
OyZndDsgTm93LCB3ZSBIQVZFIGRpc2N1c3NlZCBjaGFuZ2luZyAmcXVvdDthZGRyZXNzOnBvcnQm
cXVvdDsgdG8gJnF1b3Q7dHJhbnNwb3J0JnF1b3Q7LCBidXQgaXQgd291bGQgc3RpbGwgbm90IGJl
IGFib3V0IHRoZSBtPSBzZWN0aW9uLjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsgPGJyPg0KJmd0OyZn
dDsmZ3Q7Jmd0OyZndDsmZ3Q7IEhhdmluZyBzYWlkIHRoYXQsIGlmIHdlIGNhbiBjaGFuZ2UgaXQg
d2l0aCBhIHNlYXJjaC9yZXBsYWNlIG9wZXJhdGlvbiBJIGFtPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0
OyZndDsmZ3Q7IGhhcHB5IHRvIGRpc2N1c3MgaXQuIEkgVEhJTksgd2UgY291bGQgZG8gdGhhdCBl
LmcuLCB3aXRoICZxdW90O3RyYW5zcG9ydCZxdW90OyBvcjxicj4NCiZndDsmZ3Q7Jmd0OyZndDsm
Z3Q7Jmd0OyAmcXVvdDszLXR1cGxlJnF1b3Q7LiA8YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyA8
YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7Jmd0OyBCdXQgSSBkb26p9nQgd2FudCB0byBtYWtlIHlldCBh
bm90aGVyIHJlLXdyaXRlIG9mIHRoZSBkb2N1bWVudCBqdXN0IHRvIG9uY2U8YnI+DQomZ3Q7Jmd0
OyZndDsmZ3Q7Jmd0OyBhZ2FpbiBjaGFuZ2UgdGhlIHRlcm1pbm9sb2d5Ljxicj4NCiZndDsmZ3Q7
Jmd0OyZndDsgPGJyPg0KJmd0OyZndDsmZ3Q7Jmd0OyBUaGlzIGRvY3VtZW50IGlzIGdvaW5nIHRv
IGJlIHVzZWQgYnkgYSBsb3Qgb2YgcGVvcGxlLiBJdCdzIGltcG9ydGFudCB0aGF0IGl0IGJlPGJy
Pg0KJmd0OyZndDsmZ3Q7Jmd0OyBjbGVhci48YnI+DQomZ3Q7Jmd0OyZndDsmZ3Q7IDxicj4NCiZn
dDsmZ3Q7Jmd0OyAmbmJzcDtJIGZ1bGx5IGFncmVlLiBCdXQsIEkgYW0gbm90IHN1cmUgdGhhdCBl
bmRsZXNzIHJlLXdyaXRpbmdzIHRoZSBkb2N1bWVudCBpcyBnb2luZyB0byBhY2hpZXZlIHRoYXQu
PGJyPg0KJmd0OyZndDs8L3NwYW4+PC9kaXY+DQo8ZGl2PiZndDsmZ3Q7IEkgdGhpbmsgdGhpcyBo
YXMgdHVybmVkIGludG8gYW4gYXJndW1lbnQgYWJvdXQgc3R5bGUuIE9uZSB1c2FnZSBtYXkgYmUg
bW9yZSBwbGVhc2luZyB0byB0aGUgobBlYXKhsSB0aGFuIHRoZSBvdGhlciwgYnV0IEkgZG9uoa90
IHNlZSBpc3N1ZXMgb2YgdGVjaG5pY2FsIGNvcnJlY3RuZXNzIG9yIGNsYXJpdHkgaGVyZS4gQXMg
SSBhc2tlZCBmb3IgdGhlIHRoZSChsGFzc29jaWF0ZWQgd2l0aKGxIHF1ZXN0aW9uLCBpcyBhbnlv
bmUgYXJndWluZyB0aGF0DQogdGhlIHdvcmQgY2hvaWNlIGhlcmUgaXMgbGlrZWx5IHRvIGNhdXNl
IG1hdGVyaWFsIGltcGxlbWVudGF0aW9uIGVycm9ycz88L2Rpdj4NCjxkaXY+Jmd0OzwvZGl2Pg0K
PGRpdj4mZ3Q7IEkgZG9uJ3QgdGhpbmsgJnF1b3Q7YWRkcmVzczpwb3J0JnF1b3Q7IHZlcnN1cyAm
cXVvdDt0cmFuc3BvcnQmcXVvdDsgd2lsbCwgYnV0IEkgZG8gdGhpbmsgJnF1b3Q7YWRkcmVzczpw
b3J0JnF1b3Q7IHZlcnN1cyAmcXVvdDttPXNlY3Rpb24mcXVvdDsgb3IgJnF1b3Q7dHJhbnNwb3J0
IHBhcmFtZXRlcnMmcXVvdDsgd2lsbCwgYW5kIGluIGZhY3QgSSBpZGVudGlmaWVkIGEgbWF0ZXJp
YWwgaXNzdWUgYXJvdW5kIHRyaWNrbGUgdGhlIG90aGVyIGRheSwgdGhhdCBJIGhhdmVuJ3Qgc2Vl
biBhIHJlc3BvbnNlIHRvLjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pk15IHN1Z2dlc3Rpb24gd2Fz
IHRvIGFkZCB0ZXh0IGFib3V0IHRoZSBzcGVjaWFsIGNhc2Ugb2YgcG9ydCA5IGFuZCBJUCBhZGRy
ZXNzIDAuMC4wLjAuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5CZWNhdXNlLCB3aGVu
IHlvdSB1c2UgdHJpY2tsZSwgdGhlIG9mZmVyIG1heSBub3QgY29udGFpbiBhbnkgYWRkcmVzcyBp
bmZvcm1hdGlvbiBhdCBhbGwgKHlvdSBjYW4gc2VuZCBhbiBvZmZlciB3aXRob3V0IGFueSBjYW5k
aWRhdGVzKSwgc28gaXQgaXMgYSBzcGVjaWFsIGNhc2Ugbm8gbWF0dGVyIHdoYXQuPC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5SZWdhcmRzLDwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4N
CjxkaXY+Q2hyaXN0ZXI8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_D6FE753F2E6A0christerholmbergericssoncom_--


From nobody Thu Apr 19 07:06:26 2018
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 0A58212D7E6 for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 07:06:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 yJr9mjX1IfGu for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 07:06:22 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::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 2A5CA12DA14 for <mmusic@ietf.org>; Thu, 19 Apr 2018 07:06:20 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id q10-v6so1233699oth.9 for <mmusic@ietf.org>; Thu, 19 Apr 2018 07:06: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=5rAUPczeXM0zYF7F3rdkTEo//2ITpzcZbKqB/opGIn0=; b=onJZGqacW4/QEQoMOMdLAmbmE1f13tJ+naccuGaIveLWRAJ2ecx5rU9oa7b2VHfQ/V FQh+nLL88F1JALkGQXORdcy7MeBPg3XsiZVnhj+XKxnPC0fdtIljJDdijZmJsuRV+8v2 jhgS1fKSBwyqQH/FqxwbvNJQr7xleqZkPJn3P8e4k4ukugWaitnT3HA3u99E3YlR3sv2 yl2pGGL8kUoNNpHxcwH2s4ZHrksBT1SXmSmuWYyYMvfMhAELaPLtGd7D3wiDI6l56pVV 8AmdIeTlaIO1P8mGfSIFWUKJeb8V3VlPBuG2jWLHYMvS13vFEAT9ST2eVbjSzrmZVlkU xasg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5rAUPczeXM0zYF7F3rdkTEo//2ITpzcZbKqB/opGIn0=; b=sauCIi1cVNd7nqXgXqsScda1vPFrvpuDxzO3pZNCKZYjKjdpv8nN4Qiv9RdoeOs60I U/6QHNECEVtJRRP/TCcOmCeTA4s88U6Ichzcr1I3CAFv/U1xB3RCOnz1Ohi8T1VjRJUx 3AJ/304YbyX2dM++TrsMhHSw0tvTMuFC0k1wcFXG3q68PamCBJktNkiFGeKvDH9ZV7iF SrtJGpHcQd9+FTLsju4Y/6zF/CLbAMAWBFzG/lq55zJISRqA3iITfEYVWxvS/3DPbxL9 z1/cGxH+kyUsfRZeQ2+CEhrP/OocCdCRAs+C07zRPEc50Z0RgWMEzmpUfGqEENbwBO/g 09NA==
X-Gm-Message-State: ALQs6tA7xOcVM21ooy6M8y66+4HixyPCtgS+RTa1tg6dXAYyG4IQUoio KUuaryyKZXuFzd9250Pjq/spKeP4NS6RIZstLL7PDw==
X-Google-Smtp-Source: AIpwx4+oeQ8IBZmxcGdZhF1WK7SArF/H4oAKaW7ZqiKK5l/wHAEJsyGreqJL09cqmvmpgrsuMg/mTi7HaX3cp/McTHY=
X-Received: by 2002:a9d:4c16:: with SMTP id l22-v6mr4290973otf.176.1524146779248;  Thu, 19 Apr 2018 07:06:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Thu, 19 Apr 2018 07:05:38 -0700 (PDT)
In-Reply-To: <D6FE753F.2E6A0%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 19 Apr 2018 07:05:38 -0700
Message-ID: <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005d0395056a34135d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Xs_YciqPf76PaoOyzs8i2rMYz0o>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 14:06:24 -0000

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

On Thu, Apr 19, 2018 at 6:35 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> >>>>> This doesn't answer my question. Who, specifically, thinks that thi=
s
> terminology
> >>>>> of focusing on the address:port and not the m=3D section is good?
> >>>>
> >>>> Considering that the focus has been on the address and port since da=
y
> one, for 7 years, I think it is good. After all, while there is more to i=
t
> than the address:port, the main reason for BUNDLE is to be able to
> multiplex in a single address:port.
> >>>>
> >>>> Now, we HAVE discussed changing "address:port" to "transport", but i=
t
> would still not be about the m=3D section.
> >>>>
> >>>>>> Having said that, if we can change it with a search/replace
> operation I am
> >>>>>> happy to discuss it. I THINK we could do that e.g., with
> "transport" or
> >>>>>> "3-tuple".
> >>>>>
> >>>>> But I don=C2=B9t want to make yet another re-write of the document =
just
> to once
> >>>>> again change the terminology.
> >>>>
> >>>> This document is going to be used by a lot of people. It's important
> that it be
> >>>> clear.
> >>>>
> >>>  I fully agree. But, I am not sure that endless re-writings the
> document is going to achieve that.
> >>
> >> I think this has turned into an argument about style. One usage may be
> more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but I don=E2=
=80=99t see issues of
> technical correctness or clarity here. As I asked for the the =E2=80=9Cas=
sociated
> with=E2=80=9D question, is anyone arguing that the word choice here is li=
kely to
> cause material implementation errors?
> >
> > I don't think "address:port" versus "transport" will, but I do think
> "address:port" versus "m=3Dsection" or "transport parameters" will, and i=
n
> fact I identified a material issue around trickle the other day, that I
> haven't seen a response to.
>
> My suggestion was to add text about the special case of port 9 and IP
> address 0.0.0.0.
>
> Because, when you use trickle, the offer may not contain any address
> information at all (you can send an offer without any candidates), so it =
is
> a special case no matter what.
>

Yes, but the point is that you cannot address the m=3Dsection parameters vi=
a
address:port, so every piece of text in the document that suggests that you
do so needs to be repaired.

-Ekr


> Regards,
>
> Christer
>
>

--0000000000005d0395056a34135d
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, Apr 19, 2018 at 6:35 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 style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi,</div><span class=3D"">
<div><br>
</div>
<span id=3D"m_3913364755621987350OLK_SRC_BODY_SECTION">
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><span>&gt;&gt;&gt;&gt;&gt; This doesn&#39;t answer my question. Who, s=
pecifically, thinks that this terminology<br>
&gt;&gt;&gt;&gt;&gt; of focusing on the address:port and not the m=3D secti=
on is good?<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Considering that the focus has been on the address and por=
t since day one, for 7 years, I think it is good. After all, while there is=
 more to it than the address:port, the main reason for BUNDLE is to be able=
 to multiplex in a single address:port.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Now, we HAVE discussed changing &quot;address:port&quot; t=
o &quot;transport&quot;, but it would still not be about the m=3D section.<=
br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt;&gt; Having said that, if we can change it with a searc=
h/replace operation I am<br>
&gt;&gt;&gt;&gt;&gt;&gt; happy to discuss it. I THINK we could do that e.g.=
, with &quot;transport&quot; or<br>
&gt;&gt;&gt;&gt;&gt;&gt; &quot;3-tuple&quot;. <br>
&gt;&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; But I don=C2=B9t want to make yet another re-write of =
the document just to once<br>
&gt;&gt;&gt;&gt;&gt; again change the terminology.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; This document is going to be used by a lot of people. It&#=
39;s important that it be<br>
&gt;&gt;&gt;&gt; clear.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt; =C2=A0I fully agree. But, I am not sure that endless re-writin=
gs the document is going to achieve that.<br>
&gt;&gt;</span></div>
<div>&gt;&gt; I think this has turned into an argument about style. One usa=
ge may be more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but I =
don=E2=80=99t see issues of technical correctness or clarity here. As I ask=
ed for the the =E2=80=9Cassociated with=E2=80=9D question, is anyone arguin=
g that
 the word choice here is likely to cause material implementation errors?</d=
iv>
<div>&gt;</div>
<div>&gt; I don&#39;t think &quot;address:port&quot; versus &quot;transport=
&quot; will, but I do think &quot;address:port&quot; versus &quot;m=3Dsecti=
on&quot; or &quot;transport parameters&quot; will, and in fact I identified=
 a material issue around trickle the other day, that I haven&#39;t seen a r=
esponse to.</div>
</div>
</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>My suggestion was to add text about the special case of port 9 =
and IP address 0.0.0.0.</div>
<div><br>
</div>
<div>Because, when you use trickle, the offer may not contain any address i=
nformation at all (you can send an offer without any candidates), so it is =
a special case no matter what.</div></div></blockquote><div><br></div><div>=
Yes, but the point is that you cannot address the m=3Dsection parameters vi=
a address:port, so every piece of text in the document that suggests that y=
ou do so needs to be repaired.</div><div><br></div><div>-Ekr</div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word;col=
or:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
</div>

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

--0000000000005d0395056a34135d--


From nobody Thu Apr 19 07:31:27 2018
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 D1B6E12DA13 for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 07:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xcAwuhPVCuBV for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 07:31: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 8379D126DFF for <mmusic@ietf.org>; Thu, 19 Apr 2018 07:31:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524148276; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=o0B/m8fIInBleV2G/sqGmodCs9zAtxpU6MctH0nfvOs=; b=EuNcij1T4HlKh6m6AD0bB3kFX3JwGuSwmdskKZISXpHZsIP6YxSXMwN2mew1kt4r EFcCMveoUi5nAdb50CgCKrck3Aeq5KmXhJpVJFGkIEJVRGN3eNa+sdI3yi1cuyBA HlIw2xzcHEIPPMu1WThH/VWRVhzbyuKH0UMSfcnRnZo=;
X-AuditID: c1b4fb3a-ae7ff7000000795a-c9-5ad8a8348140
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 7E.F8.31066.438A8DA5; Thu, 19 Apr 2018 16:31:16 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0382.000; Thu, 19 Apr 2018 16:31:16 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseCAAZvZAIAAP3yAgAA0rgD//9WjAIAAJksw
Date: Thu, 19 Apr 2018 14:31:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com>
In-Reply-To: <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@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.170]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72E8FE63ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFIsWRmVeSWpSXmKPExsUyM2K7hK7JihtRBje6lC32/F3EbjG/8zS7 xfRZ79gsVrw+x27x/oKuxYw/E5ktzu9cz2QxdfljFgcOjym/N7J6LFnyk8lj1s4nLB6TH7cx B7BEcdmkpOZklqUW6dslcGXsPrOFueBKUkXb2+0sDYx/4rsYOTkkBEwkfh64xN7FyMUhJHCE UeLJjmlMEM5iRol7h88xdjFycLAJWEh0/9MGaRARUJD49ecEC0gNs8B5Jom525rZQBLCAukS c1YtYwapFxHIkLj/IBOiPk9i9+ZTrCA2i4CqxPnmtywgNq+Ar8T/43MYQWwhgR8sEl+/gM3n FAiUOHunhRnEZhQQk/h+ag0TiM0sIC5x68l8JoijBSSW7DnPDGGLSrx8/I8VwlaSOLPpOQtE fb5E34yzzBC7BCVOznzCMoFRZBaSUbOQlM1CUjYL6ANmAU2J9bv0IUoUJaZ0P2SHsDUkWufM ZUcWX8DIvopRtDi1uDg33chIL7UoM7m4OD9PLy+1ZBMjMEYPbvlttYPx4HPHQ4wCHIxKPLy3 Zt+IEmJNLCuuzD3EKMHBrCTC690OFOJNSaysSi3Kjy8qzUktPsQozcGiJM7rlGYRJSSQnliS mp2aWpBaBJNl4uCUamDUYuu7tNF28cnWZXvDDr76Kfz71PxldQaKL2/fSg/maTU6MfH5gjQh 62KnxP9Ry9YzCeQabf94JkTArjfKpn0698E3fxveqx8q+uRnJnTdb6O10/3rT3rf/kxIrTon ddz6PWu0k/HaS4yzoibeztS50rTs0cstT4/+ONVamrf2hUVQnnJFfO9eJZbijERDLeai4kQA 5Lk/tc0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/81VC5rUAaGCcwL9oR3yfFxkR8QY>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 14:31:26 -0000

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

SGksDQoNCuKApg0KDQo+PiBJIHRoaW5rIHRoaXMgaGFzIHR1cm5lZCBpbnRvIGFuIGFyZ3VtZW50
IGFib3V0IHN0eWxlLiBPbmUgdXNhZ2UgbWF5IGJlIG1vcmUgcGxlYXNpbmcgdG8gdGhlIOKAnGVh
cuKAnSB0aGFuIHRoZSBvdGhlciwgYnV0IEkNCj4+IGRvbuKAmXQgc2VlIGlzc3VlcyBvZiB0ZWNo
bmljYWwgY29ycmVjdG5lc3Mgb3IgY2xhcml0eSBoZXJlLiBBcyBJIGFza2VkIGZvciB0aGUgdGhl
IOKAnGFzc29jaWF0ZWQgd2l0aOKAnSBxdWVzdGlvbiwgaXMgYW55b25lIGFyZ3VpbmcNCj4+IHRo
YXQgdGhlIHdvcmQgY2hvaWNlIGhlcmUgaXMgbGlrZWx5IHRvIGNhdXNlIG1hdGVyaWFsIGltcGxl
bWVudGF0aW9uIGVycm9ycz8NCj4NCj4gSSBkb24ndCB0aGluayAiYWRkcmVzczpwb3J0IiB2ZXJz
dXMgInRyYW5zcG9ydCIgd2lsbCwgYnV0IEkgZG8gdGhpbmsgImFkZHJlc3M6cG9ydCIgdmVyc3Vz
ICJtPXNlY3Rpb24iIG9yICJ0cmFuc3BvcnQgcGFyYW1ldGVycyIgd2lsbCwNCj4gYW5kIGluIGZh
Y3QgSSBpZGVudGlmaWVkIGEgbWF0ZXJpYWwgaXNzdWUgYXJvdW5kIHRyaWNrbGUgdGhlIG90aGVy
IGRheSwgdGhhdCBJIGhhdmVuJ3Qgc2VlbiBhIHJlc3BvbnNlIHRvLg0KPg0KPj4gTXkgc3VnZ2Vz
dGlvbiB3YXMgdG8gYWRkIHRleHQgYWJvdXQgdGhlIHNwZWNpYWwgY2FzZSBvZiBwb3J0IDkgYW5k
IElQIGFkZHJlc3MgMC4wLjAuMC4NCj4+IEJlY2F1c2UsIHdoZW4geW91IHVzZSB0cmlja2xlLCB0
aGUgb2ZmZXIgbWF5IG5vdCBjb250YWluIGFueSBhZGRyZXNzIGluZm9ybWF0aW9uIGF0IGFsbA0K
Pj4gKHlvdSBjYW4gc2VuZCBhbiBvZmZlciB3aXRob3V0IGFueSBjYW5kaWRhdGVzKSwgc28gaXQg
aXMgYSBzcGVjaWFsIGNhc2Ugbm8gbWF0dGVyIHdoYXQuDQo+DQo+IFllcywgYnV0IHRoZSBwb2lu
dCBpcyB0aGF0IHlvdSBjYW5ub3QgYWRkcmVzcyB0aGUgbT1zZWN0aW9uIHBhcmFtZXRlcnMgdmlh
IGFkZHJlc3M6cG9ydCwgc28gZXZlcnkNCj4gcGllY2Ugb2YgdGV4dCBpbiB0aGUgZG9jdW1lbnQg
dGhhdCBzdWdnZXN0cyB0aGF0IHlvdSBkbyBzbyBuZWVkcyB0byBiZSByZXBhaXJlZC4NCg0KWW91
IGRvbuKAmXQgbmVlZCB0byBhZGRyZXNzIHRoZSBwYXJhbWV0ZXJzIHZpYSBhZGRyZXNzOnBvcnQu
IFlvdSB3aWxsIGFkZHJlc3MgdGhlIHBhcmFtZXRlcnMgdmlhIHRoZSBCVU5ETEUtdGFnLg0KDQpZ
ZXMsIHRoZSBhbnN3ZXJlciBwaWNrcyB0aGUgQlVORExFIGFkZHJlc3M6cG9ydCDigJMgd2hpY2gg
aXQgaGFzIHRvIGRvIG5vIG1hdHRlciB3aGF0IOKAkyBidXQgd2hhdCBpcyBkb2VzIGlzIHBpY2tp
bmcgYW4gbS0gbGluZSAodGhlIG0tIGxpbmUgY29udGFpbmluZyB0aGUgYWRkcmVzczpwb3J0IHNl
bGVjdGVkIHRvIGJlIHVzZWQpIGFuZCBhc3NpZ25zIHRoZSBCVU5ETEUtdGFnIHRvIGl0Lg0KDQpS
ZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo=

--_000_7594FB04B1934943A5C02806D1A2204B72E8FE63ESESSMB109erics_
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
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl
eHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0
IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29y
ZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9
IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0
aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj7igKY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+Jmd0OyZndDsg
SSB0aGluayB0aGlzIGhhcyB0dXJuZWQgaW50byBhbiBhcmd1bWVudCBhYm91dCBzdHlsZS4gT25l
IHVzYWdlIG1heSBiZSBtb3JlIHBsZWFzaW5nIHRvIHRoZSDigJxlYXLigJ0gdGhhbiB0aGUgb3Ro
ZXIsIGJ1dCBJDQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZndDsmZ3Q7DQo8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5kb27igJl0IHNlZSBpc3N1ZXMgb2YgdGVjaG5p
Y2FsIGNvcnJlY3RuZXNzIG9yIGNsYXJpdHkgaGVyZS4gQXMgSSBhc2tlZCBmb3IgdGhlIHRoZSDi
gJxhc3NvY2lhdGVkIHdpdGjigJ0gcXVlc3Rpb24sIGlzIGFueW9uZSBhcmd1aW5nDQo8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZndDsmZ3Q7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOmJsYWNrIj50aGF0IHRoZSB3b3JkIGNob2ljZSBoZXJlIGlzIGxpa2VseSB0byBjYXVzZSBt
YXRlcmlhbCBpbXBsZW1lbnRhdGlvbiBlcnJvcnM/PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrIj4mZ3Q7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmJsYWNrIj4mZ3Q7IEkgZG9uJ3QgdGhpbmsgJnF1b3Q7YWRkcmVzczpwb3J0JnF1b3Q7IHZlcnN1
cyAmcXVvdDt0cmFuc3BvcnQmcXVvdDsgd2lsbCwgYnV0IEkgZG8gdGhpbmsgJnF1b3Q7YWRkcmVz
czpwb3J0JnF1b3Q7IHZlcnN1cyAmcXVvdDttPXNlY3Rpb24mcXVvdDsgb3IgJnF1b3Q7dHJhbnNw
b3J0IHBhcmFtZXRlcnMmcXVvdDsgd2lsbCwNCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
Jmd0Ow0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+YW5kIGluIGZhY3QgSSBp
ZGVudGlmaWVkIGEgbWF0ZXJpYWwgaXNzdWUgYXJvdW5kIHRyaWNrbGUgdGhlIG90aGVyIGRheSwg
dGhhdCBJIGhhdmVuJ3Qgc2VlbiBhIHJlc3BvbnNlIHRvLjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+Jmd0OyZndDsNCjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+
TXkgc3VnZ2VzdGlvbiB3YXMgdG8gYWRkIHRleHQgYWJvdXQgdGhlIHNwZWNpYWwgY2FzZSBvZiBw
b3J0IDkgYW5kIElQIGFkZHJlc3MgMC4wLjAuPC9zcGFuPjAuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7Jmd0Ow0KPHNwYW4g
c3R5bGU9ImNvbG9yOmJsYWNrIj5CZWNhdXNlLCB3aGVuIHlvdSB1c2UgdHJpY2tsZSwgdGhlIG9m
ZmVyIG1heSBub3QgY29udGFpbiBhbnkgYWRkcmVzcyBpbmZvcm1hdGlvbiBhdCBhbGwNCjwvc3Bh
bj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWYiPiZndDsmZ3Q7DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4oeW91
IGNhbiBzZW5kIGFuIG9mZmVyIHdpdGhvdXQgYW55IGNhbmRpZGF0ZXMpLCBzbyBpdCBpcyBhIHNw
ZWNpYWwgY2FzZSBubyBtYXR0ZXIgd2hhdC48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+Jmd0OyBZZXMsIGJ1dCB0aGUgcG9pbnQgaXMgdGhhdCB5b3UgY2Fubm90
IGFkZHJlc3MgdGhlIG09c2VjdGlvbiBwYXJhbWV0ZXJzIHZpYSBhZGRyZXNzOnBvcnQsIHNvIGV2
ZXJ5DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+Jmd0Ow0KPC9zcGFuPnBpZWNlIG9mIHRleHQgaW4gdGhlIGRvY3VtZW50IHRoYXQgc3VnZ2Vz
dHMgdGhhdCB5b3UgZG8gc28gbmVlZHMgdG8gYmUgcmVwYWlyZWQuPHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+WW91IGRvbuKAmXQgbmVlZCB0byBhZGRyZXNzIHRoZSBwYXJhbWV0ZXJzIHZpYSBhZGRy
ZXNzOnBvcnQuIFlvdSB3aWxsIGFkZHJlc3MgdGhlIHBhcmFtZXRlcnMgdmlhIHRoZSBCVU5ETEUt
dGFnLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmIj5ZZXMsIHRoZSBhbnN3ZXJlciBwaWNrcyB0aGUgQlVORExFIGFk
ZHJlc3M6cG9ydCDigJMgd2hpY2ggaXQgaGFzIHRvIGRvIG5vIG1hdHRlciB3aGF0IOKAkyBidXQg
d2hhdCBpcyBkb2VzIGlzIHBpY2tpbmcgYW4gbS0gbGluZSAodGhlIG0tIGxpbmUgY29udGFpbmlu
ZyB0aGUgYWRkcmVzczpwb3J0IHNlbGVjdGVkDQogdG8gYmUgdXNlZCkgYW5kIGFzc2lnbnMgdGhl
IEJVTkRMRS10YWcgdG8gaXQuIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B72E8FE63ESESSMB109erics_--


From nobody Thu Apr 19 07:34:05 2018
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 08CD01267BB for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 07:34:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 dRRH7aOLuwfY for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 07:34:01 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::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 7A49412DB6D for <mmusic@ietf.org>; Thu, 19 Apr 2018 07:33:15 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id t27-v6so5009881oij.9 for <mmusic@ietf.org>; Thu, 19 Apr 2018 07:33:15 -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=t5dRDPeDSgHyti67+Lk8Z0VeS/9Og+HjFlnRBUyBYYI=; b=COd8UtwNG36Nr3VBThj6BaB+7vQPFn+Ts7yNZwy07ZPEXpNm2u3lkgcSwRaue22mCH UhWQ8ECt3GqWYQVy+6TYdnfq4yAmZXWa9dM96l5Wg24Mg2YIw0fLnzNYGrRPy9tiWPf6 BIZQoUljSCSz2dxIMEvTLFQUHHIJU9aWqQ247AybR8Y9leyr10RNDKSZmcweCV4nl5Nu nilwGC6eDrBEVO2o4E0xwhXSKdCG6UYGgXxP8NxNqpReuOVjBRXZUL7r+btObRSWodSy 2Ua4giBRdP7Zz95jrGprnITtty00ZEJOs/f8V8oSgHPJx6w4UBhFLs6iLYA72mcwJqEI OJDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t5dRDPeDSgHyti67+Lk8Z0VeS/9Og+HjFlnRBUyBYYI=; b=de7x48W1wWum+/tLA4Go9R51SxRUQst3AeO+V24eO4NYv9Dye9001NC94S0vl+V/tx FZVBl4Q1MGWioq5RF3pA5whB+uIfw752vNnA3PpTYFjDXP8pkw4dgpoe+rQHaseSIZ36 OvIWcsKYJt2iS6LNxVpieFkk56EhgGORp51x8Ay3LxyM76muXRnGEPsQ8Whuv1RlXBES WUb1DI1gBNefZ8GLbLnNiFeHCQwf2NeniVJJ2hmnGeUuEEdTMEA43uJirx/mkraNhzuF eBsq+FFK/qr3MKnFM8gspMrXTL+PFw7MVUVktAdLvwR6s+aUO6y93agoXa7hDEgtco65 EpdQ==
X-Gm-Message-State: ALQs6tDVlI2wKxjwJWqETkUDkHwod2Lj54X/9RHmaW8f/9IOYiFHj0HA IuKZfdJ71pDWYWT+Ddq8AbaauzMt5Ks1lKNg6FVF3A==
X-Google-Smtp-Source: AIpwx4+Dx43CAo05pr1ypvCtJfOFLiM81y2LsxK6CIWuZwBXBiROwcScTyobK1eRzzBiTmRUhGKersI0bZwP6qEisM4=
X-Received: by 2002:aca:ea46:: with SMTP id i67-v6mr3867638oih.174.1524148394796;  Thu, 19 Apr 2018 07:33:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Thu, 19 Apr 2018 07:32:34 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 19 Apr 2018 07:32:34 -0700
Message-ID: <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a83fad056a34735d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2N2KZ-slVbWckqmEc5PrwBhUgz0>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 14:34:03 -0000

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

On Thu, Apr 19, 2018 at 7:31 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> =E2=80=A6
>
>
>
> >> I think this has turned into an argument about style. One usage may be
> more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but I
>
> >> don=E2=80=99t see issues of technical correctness or clarity here. As =
I asked
> for the the =E2=80=9Cassociated with=E2=80=9D question, is anyone arguing
>
> >> that the word choice here is likely to cause material implementation
> errors?
>
> >
>
> > I don't think "address:port" versus "transport" will, but I do think
> "address:port" versus "m=3Dsection" or "transport parameters" will,
>
> > and in fact I identified a material issue around trickle the other day,
> that I haven't seen a response to.
>
> >
>
> >> My suggestion was to add text about the special case of port 9 and IP
> address 0.0.0.0.
>
> >> Because, when you use trickle, the offer may not contain any address
> information at all
>
> >> (you can send an offer without any candidates), so it is a special
> case no matter what.
>
> >
>
> > Yes, but the point is that you cannot address the m=3Dsection parameter=
s
> via address:port, so every
>
> > piece of text in the document that suggests that you do so needs to be
> repaired.
>
>
>
> You don=E2=80=99t need to address the parameters via address:port. You wi=
ll
> address the parameters via the BUNDLE-tag.
>
>
>
> Yes, the answerer picks the BUNDLE address:port =E2=80=93 which it has to=
 do no
> matter what =E2=80=93 but what is does is picking an m- line (the m- line
> containing the address:port selected to be used) and assigns the BUNDLE-t=
ag
> to it.
>


Yes, but that's not in fact what the text I quoted says, or is implied by
much of the rest of the document does.

-Ekr



> Regards,
>
>
>
> Christer
>
>
>

--000000000000a83fad056a34735d
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, Apr 19, 2018 at 7:31 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 link=3D"blue" vlink=3D"purple" lang=3D"EN-GB">
<div class=3D"m_-6573004089341623604WordSection1">
<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">=E2=80=A6<u></u><u></u></span></p><sp=
an class=3D"">
<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:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt;&gt; I think this has turned into a=
n argument about style. One usage may be more pleasing to the =E2=80=9Cear=
=E2=80=9D than the other, but I
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif"><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">&gt;&gt;
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif;color:black">don=E2=80=99t see issues of technical correctness or cl=
arity here. As I asked for the the =E2=80=9Cassociated with=E2=80=9D questi=
on, is anyone arguing
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif"><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">&gt;&gt;
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif;color:black">that the word choice here is likely to cause material i=
mplementation errors?</span><span style=3D"font-size:11.0pt;font-family:&qu=
ot;Calibri&quot;,sans-serif"><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">&gt;</span><span 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 style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:black">&gt; I don&#39;t think &quot;address:po=
rt&quot; versus &quot;transport&quot; will, but I do think &quot;address:po=
rt&quot; versus &quot;m=3Dsection&quot; or &quot;transport parameters&quot;=
 will,
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif"><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">&gt;
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif;color:black">and in fact I identified a material issue around trickl=
e the other day, that I haven&#39;t seen a response to.</span><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"><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">&gt;<u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt;&gt;
<span style=3D"color:black">My suggestion was to add text about the special=
 case of port 9 and IP address 0.0.0.</span>0.<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">&gt;&gt;
<span style=3D"color:black">Because, when you use trickle, the offer may no=
t contain any address information at all
</span><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">&gt;&gt;
</span><span style=3D"font-size:10.5pt;font-family:&quot;Calibri&quot;,sans=
-serif;color:black">(you can send an offer without any candidates), so it i=
s a special case no matter what.</span><span style=3D"font-size:11.0pt;font=
-family:&quot;Calibri&quot;,sans-serif"><u></u><u></u></span></p>
</span><div>
<div>
<div><span class=3D"">
<div>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&gt; Yes, but the point is that you cannot address t=
he m=3Dsection parameters via address:port, so every
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">&gt;
</span>piece of text in the document that suggests that you do so needs to =
be repaired.<span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,sans-serif"><u></u><u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">You don=E2=80=99t need to address the parameters vi=
a address:port. You will address the parameters via the BUNDLE-tag.<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">Yes, the answerer picks the BUNDLE address:port =E2=
=80=93 which it has to do no matter what =E2=80=93 but what is does is pick=
ing an m- line (the m- line containing the address:port selected
 to be used) and assigns the BUNDLE-tag to it. <u></u><u></u></span></p>
</div></div></div></div></div></div></blockquote><div><br></div><div><div><=
br></div><div>Yes, but that&#39;s not in fact what the text I quoted says, =
or is implied by much of the rest of the document does.<br></div><div><br><=
/div><div>-Ekr</div><div><br></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 link=3D"blue" vlink=3D"purple" lang=3D"EN-GB"><div class=3D"m_-6573=
004089341623604WordSection1"><div><div><div><div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif">Regards,<span class=3D"HOEnZb"><font color=3D"#8888=
88"><u></u><u></u></font></span></span></p><span class=3D"HOEnZb"><font col=
or=3D"#888888">
<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">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>
</font></span></div>
</div>
</div>
</div>
</div>
</div>

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

--000000000000a83fad056a34735d--


From nobody Thu Apr 19 11:10:44 2018
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 81976124207 for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 11:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0yHLNjOmMPU for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 11:10: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 88AF612D87F for <mmusic@ietf.org>; Thu, 19 Apr 2018 11:10:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524161438; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=b4w2fWq550FG128xvSfOI6wCvg4I0Q3P+6ahkBgLxa0=; b=MWivTcux0Uc56xVc8jht1iuNBvKaw92f/4nm4p1hJeO9b+Pjdws4wIbkfRuKOXP6 iAzV6q5CXTsw/sDiyED1vcOQxnP2hbFs81TA/sawspRogau7OKeazk6TFhO7P54h gHUb1AG5byslS03KTB8zmbvdK09rx7OLWFv6miNc1Lg=;
X-AuditID: c1b4fb2d-82dff70000003563-a8-5ad8db9eb7cc
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 41.43.13667.E9BD8DA5; Thu, 19 Apr 2018 20:10:38 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0382.000; Thu, 19 Apr 2018 20:10:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseCAAZvZAIAAP3yAgAA0rgD//9WjAIAAJksw///hOwCAAFstgA==
Date: Thu, 19 Apr 2018 18:10:37 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E905A2@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se> <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com>
In-Reply-To: <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@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.163]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2J7iO682zeiDG48NrPY83cRu8X8ztPs FtNnvWOzWPH6HLvF+wu6FjP+TGS2OL9zPZPF1OWPWRw4PKb83sjqsWTJTyaPWTufsHhMftzG HMASxWWTkpqTWZZapG+XwJUxq/UMU8Eh8YqZrZ9ZGhi/iHUxcnJICJhIrF74ga2LkYtDSOAI o8S6j9uZIZzFjBK3nvwEcjg42AQsJLr/aYM0iAgoSPz6c4IFpIZZ4DyTxNxtzWwgCWGBdIk5 q5aB1YsIZEjcf5AJUV8nca/hD1gJi4CqxIpNf1lAbF4BX4mv3w4yg9hCAs1sEnMX+IO0cgoE SkxpVAAJMwqISXw/tYYJxGYWEAe6Zj4TxM0CEkv2nGeGsEUlXj7+xwphK0ksn7aFHWQMs4Cm xPpd+hCtihJTuh+yQ2wVlDg58wnLBEbRWUimzkLomIWkYxaSjgWMLKsYRYtTi4tz042M9VKL MpOLi/Pz9PJSSzYxAuPt4JbfujsYV792PMQowMGoxMO7b/ONKCHWxLLiytxDjBIczEoivN7t QCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8eqv2RAkJpCeWpGanphakFsFkmTg4pRoYWa6tbrQt /NYWsl0nRMOtYe71Q8vWT/u61LchVq1n3sSr3/P7zAzeNolOnv+K/2m6qkbAxcRrTGuXitbe n5N468YzFpblazdn+fTxtvTrLWn5uzLl2rFP/Cy7rWdN63RY1Gcu6brWNpZ9idOtv/2u9kUG AmFyX/iWb9A5qblhq7G5Go+G5smjSizFGYmGWsxFxYkA6jC1LbMCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lwy0UlvqPAWSZK8eZQ0PQh52m04>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 18:10:43 -0000

SGksDQrCoA0K4oCmDQrCoA0KPj4+PiBJIHRoaW5rIHRoaXMgaGFzIHR1cm5lZCBpbnRvIGFuIGFy
Z3VtZW50IGFib3V0IHN0eWxlLiBPbmUgdXNhZ2UgbWF5IGJlIG1vcmUgcGxlYXNpbmcgdG8gdGhl
IOKAnGVhcuKAnSB0aGFuIHRoZSBvdGhlciwgYnV0IEkgDQo+Pj4+IGRvbuKAmXQgc2VlIGlzc3Vl
cyBvZiB0ZWNobmljYWwgY29ycmVjdG5lc3Mgb3IgY2xhcml0eSBoZXJlLiBBcyBJIGFza2VkIGZv
ciB0aGUgdGhlIOKAnGFzc29jaWF0ZWQgd2l0aOKAnSBxdWVzdGlvbiwgaXMgYW55b25lIGFyZ3Vp
bmcgDQo+Pj4+IHRoYXQgdGhlIHdvcmQgY2hvaWNlIGhlcmUgaXMgbGlrZWx5IHRvIGNhdXNlIG1h
dGVyaWFsIGltcGxlbWVudGF0aW9uIGVycm9ycz8NCj4+PsKgDQo+Pj4gSSBkb24ndCB0aGluayAi
YWRkcmVzczpwb3J0IiB2ZXJzdXMgInRyYW5zcG9ydCIgd2lsbCwgYnV0IEkgZG8gdGhpbmsgImFk
ZHJlc3M6cG9ydCIgdmVyc3VzICJtPXNlY3Rpb24iIG9yICJ0cmFuc3BvcnQgcGFyYW1ldGVycyIg
d2lsbCwgDQo+Pj4gYW5kIGluIGZhY3QgSSBpZGVudGlmaWVkIGEgbWF0ZXJpYWwgaXNzdWUgYXJv
dW5kIHRyaWNrbGUgdGhlIG90aGVyIGRheSwgdGhhdCBJIGhhdmVuJ3Qgc2VlbiBhIHJlc3BvbnNl
IHRvLg0KPj4+wqANCj4+Pj4gTXkgc3VnZ2VzdGlvbiB3YXMgdG8gYWRkIHRleHQgYWJvdXQgdGhl
IHNwZWNpYWwgY2FzZSBvZiBwb3J0IDkgYW5kIElQIGFkZHJlc3MgMC4wLjAuMC4NCj4+Pj4gQmVj
YXVzZSwgd2hlbiB5b3UgdXNlIHRyaWNrbGUsIHRoZSBvZmZlciBtYXkgbm90IGNvbnRhaW4gYW55
IGFkZHJlc3MgaW5mb3JtYXRpb24gYXQgYWxsIA0KPj4+PiAoeW91IGNhbiBzZW5kIGFuIG9mZmVy
IHdpdGhvdXQgYW55IGNhbmRpZGF0ZXMpLCBzbyBpdCBpcyBhIHNwZWNpYWwgY2FzZSBubyBtYXR0
ZXIgd2hhdC4NCj4+PsKgDQo+Pj4gWWVzLCBidXQgdGhlIHBvaW50IGlzIHRoYXQgeW91IGNhbm5v
dCBhZGRyZXNzIHRoZSBtPXNlY3Rpb24gcGFyYW1ldGVycyB2aWEgYWRkcmVzczpwb3J0LCBzbyBl
dmVyeSANCj4+PiBwaWVjZSBvZiB0ZXh0IGluIHRoZSBkb2N1bWVudCB0aGF0IHN1Z2dlc3RzIHRo
YXQgeW91IGRvIHNvIG5lZWRzIHRvIGJlIHJlcGFpcmVkLg0KPj7CoA0KPj4+IFlvdSBkb27igJl0
IG5lZWQgdG8gYWRkcmVzcyB0aGUgcGFyYW1ldGVycyB2aWEgYWRkcmVzczpwb3J0LiBZb3Ugd2ls
bCBhZGRyZXNzIHRoZSBwYXJhbWV0ZXJzIHZpYSB0aGUgQlVORExFLXRhZy4NCj4+Pg0KPj4gWWVz
LCB0aGUgYW5zd2VyZXIgcGlja3MgdGhlIEJVTkRMRSBhZGRyZXNzOnBvcnQg4oCTIHdoaWNoIGl0
IGhhcyB0byBkbyBubyBtYXR0ZXIgd2hhdCDigJMgYnV0IHdoYXQgaXMgZG9lcyBpcyBwaWNraW5n
IGFuIA0KPj4gbS0gbGluZSAodGhlIG0tIGxpbmUgY29udGFpbmluZyB0aGUgYWRkcmVzczpwb3J0
IHNlbGVjdGVkIHRvIGJlIHVzZWQpIGFuZCBhc3NpZ25zIHRoZSBCVU5ETEUtdGFnIHRvIGl0LiAN
Cj4NCj4gWWVzLCBidXQgdGhhdCdzIG5vdCBpbiBmYWN0IHdoYXQgdGhlIHRleHQgSSBxdW90ZWQg
c2F5cywgb3IgaXMgaW1wbGllZCBieSBtdWNoIG9mIHRoZSByZXN0IG9mIHRoZSBkb2N1bWVudCBk
b2VzLg0KDQpTZWN0aW9ucyA4LjMuMSB0YWxrcyBhYm91dCBzZWxlY3RpbmcgYW4gbT0gc2VjdGlv
bi4NCg0KQXMgZmFyIGFzIHRoZSByZXN0IG9mIHRoZSBkb2N1bWVudCBpcyBjb25jZXJuZWQsIEkg
ZG9uJ3QgdGhpbmsgd2UgY2FuIGdldCByaWQgb2YgdGhlIGFkZHJlc3M6cG9ydCB0ZXh0LCBiZWNh
dXNlIG1hbnkgb2YgdGhlIG9mZmVyZXIgcHJvY2VkdXJlcyBhYm91dCBhc3NpZ25pbmcgYSBnaXZl
biBhZGRyZXNzOnBvcnQgdG8gYSBnaXZlbiBtLSBzZWN0aW9uLg0KDQpBbHNvLCBtYW55IG9mIHRo
ZSBhbnN3ZXJlciBwcm9jZWR1cmVzIChyZW1vdmluZyBtLSBzZWN0aW9ucyBldGMpIGFyZSBiYXNl
ZCBvbiB0aGUgYWRkcmVzczpwb3J0IHZhbHVlIG9mIHRoZSBtLSBzZWN0aW9uIGluIHRoZSBjb3Jy
ZXNwb25kaW5nIG9mZmVyLg0KwqANClNvLCB3aGlsZSBpdCBtYXkgYmUgcG9zc2libGUgdG8gaW50
cm9kdWNlIGEgaGVhZC90YWdnZWQvYnVuZGxlIG0tIHNlY3Rpb24gY29uY2VwdCwgSSBkb24ndCB0
aGluayB3ZSBhcmUgZ29pbmcgdG8gZ2V0IHJpZCBvZiB0aGUgYWRkcmVzczpwb3J0IHRleHQuDQoN
ClJlZ2FyZHMsDQrCoA0KQ2hyaXN0ZXINCsKgDQoNCg==


From nobody Thu Apr 19 13:22:59 2018
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 2AC3712DB70 for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 13:22:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 kSlmoWi3r6eM for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 13:22:55 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 A36AD1252BA for <mmusic@ietf.org>; Thu, 19 Apr 2018 13:22:55 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id h11-v6so6069203oic.3 for <mmusic@ietf.org>; Thu, 19 Apr 2018 13:22:55 -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=ot+bu2xSc8c6OuUMkxeSO+dJZZB1XtdSRh9GdK4iVdY=; b=DPH5brFf7QcgIlHLrW/lxn2l/gZvFqxs/Rbt331xZdJoBdpp883qAwNnr8QDb4EghK M+3YB7N/KhaKvq9m9fLMFQecmYVAg3V2qSPk52ysRqA5+/ZRWq01ZhESTZ8MykJ3kBRP attVpYZDNd/W8Ck9W0S0he67i+njszm6mFaIkgOhH6ccCzPYwdhKI6iP3GrWvw4bC3q8 jt/q/PxnfwLXE4tnDnqNKDHho5EPgZ3Sz+rjeVg0hsucXOfJmZ3okHZEJfN6pYOF289q KmYXSrghZUWHd5iYDSExIh9YKMOW8YRhScq3wbKpuMP6x+8QPHbkJjKuNhxe3lDux0/C XXbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ot+bu2xSc8c6OuUMkxeSO+dJZZB1XtdSRh9GdK4iVdY=; b=VvkF22dzTGGHwKe1I09O1gjKIkWcqgPsXj3fJI1Ns0JY68lvQ6rpbhauJIIlg8jYC3 39ZGl1mUi8XmEGwFNJuVZXv6GEmdRlbtiTxlU52f6sR86QaCOozHRiHJ87GzJUOWUPUq uLX8yYOIyd5okQoM3WXQjMq9Ju3c5JBzq8lN6hdc4M6L26WIkOMR9tOsOBldNB4N3YM1 zQZmrTkjlG5yQIkuuic+pR/vRHgVzgW8m/zWv6dcgZgUuiKbbgj5840HTOZU/OYzrUTM F5nSTO9UauRMBnTyaWmE4vAHeWtzQivNBzULYpcwd8BCY0hbItbpZFBpgZmLwb/NCWPV B8lw==
X-Gm-Message-State: ALQs6tCiWj3xtgbIHR0wHJuOW44Dz7na3Eo/ku4Zq0UvirPKkyXlP1pt p9tOZ1i9TqlEhomEUTZt5+kWP2gvIH0T+iBpXZGwhQ==
X-Google-Smtp-Source: AIpwx49Lj7faXpTw/zZFbEks3ONS9RU+H9TPKCshYxi+xQzHcSqnq1cudM/RtsEwpsnqQJF302V/CRYwc34O1EMXDuk=
X-Received: by 2002:aca:c589:: with SMTP id v131-v6mr4826245oif.92.1524169374976;  Thu, 19 Apr 2018 13:22:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Thu, 19 Apr 2018 13:22:14 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E905A2@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se> <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E905A2@ESESSMB109.ericsson.se>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 19 Apr 2018 13:22:14 -0700
Message-ID: <CABcZeBPAvudhT1wfPCOa0SGv5-i-Jdmap2RNVq6qn4eC8=VLcA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002c5df8056a39568f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/seW4ne6Vqe8cxZPJip7wxsXRCJY>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 20:22:58 -0000

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

On Thu, Apr 19, 2018 at 11:10 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> =E2=80=A6
>
> >>>> I think this has turned into an argument about style. One usage may
> be more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but I
> >>>> don=E2=80=99t see issues of technical correctness or clarity here. A=
s I asked
> for the the =E2=80=9Cassociated with=E2=80=9D question, is anyone arguing
> >>>> that the word choice here is likely to cause material implementation
> errors?
> >>>
> >>> I don't think "address:port" versus "transport" will, but I do think
> "address:port" versus "m=3Dsection" or "transport parameters" will,
> >>> and in fact I identified a material issue around trickle the other
> day, that I haven't seen a response to.
> >>>
> >>>> My suggestion was to add text about the special case of port 9 and I=
P
> address 0.0.0.0.
> >>>> Because, when you use trickle, the offer may not contain any address
> information at all
> >>>> (you can send an offer without any candidates), so it is a special
> case no matter what.
> >>>
> >>> Yes, but the point is that you cannot address the m=3Dsection paramet=
ers
> via address:port, so every
> >>> piece of text in the document that suggests that you do so needs to b=
e
> repaired.
> >>
> >>> You don=E2=80=99t need to address the parameters via address:port. Yo=
u will
> address the parameters via the BUNDLE-tag.
> >>>
> >> Yes, the answerer picks the BUNDLE address:port =E2=80=93 which it has=
 to do no
> matter what =E2=80=93 but what is does is picking an
> >> m- line (the m- line containing the address:port selected to be used)
> and assigns the BUNDLE-tag to it.
> >
> > Yes, but that's not in fact what the text I quoted says, or is implied
> by much of the rest of the document does.
>
> Sections 8.3.1 talks about selecting an m=3D section.


Yes. I haven't carefully studied that section, but this is the offerer text
and as I said, this is incorrect.


As far as the rest of the document is concerned, I don't think we can get
> rid of the address:port text, because many of the offerer procedures abou=
t
> assigning a given address:port to a given m- section.
>
> Also, many of the answerer procedures (removing m- sections etc) are base=
d
> on the address:port value of the m- section in the corresponding offer.


Yes, I agree we have to be clear that the address:port needs to be assigned
to a given m=3D section, just as all the other parameters need to be assign=
ed
properly. My concern is about treating address:port as special; that seems
to conflict with trickle.

-Ekr

So, while it may be possible to introduce a head/tagged/bundle m- section
> concept, I don't think we are going to get rid of the address:port text.
>
> Regards,
>
> Christer
>
>
>

--0000000000002c5df8056a39568f
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, Apr 19, 2018 at 11:10 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><span class=3D"">Hi,<br>
=C2=A0<br>
=E2=80=A6<br>
=C2=A0<br>
&gt;&gt;&gt;&gt; I think this has turned into an argument about style. One =
usage may be more pleasing to the =E2=80=9Cear=E2=80=9D than the other, but=
 I <br>
&gt;&gt;&gt;&gt; don=E2=80=99t see issues of technical correctness or clari=
ty here. As I asked for the the =E2=80=9Cassociated with=E2=80=9D question,=
 is anyone arguing <br>
&gt;&gt;&gt;&gt; that the word choice here is likely to cause material impl=
ementation errors?<br>
&gt;&gt;&gt;=C2=A0<br>
&gt;&gt;&gt; I don&#39;t think &quot;address:port&quot; versus &quot;transp=
ort&quot; will, but I do think &quot;address:port&quot; versus &quot;m=3Dse=
ction&quot; or &quot;transport parameters&quot; will, <br>
&gt;&gt;&gt; and in fact I identified a material issue around trickle the o=
ther day, that I haven&#39;t seen a response to.<br>
&gt;&gt;&gt;=C2=A0<br>
&gt;&gt;&gt;&gt; My suggestion was to add text about the special case of po=
rt 9 and IP address 0.0.0.0.<br>
&gt;&gt;&gt;&gt; Because, when you use trickle, the offer may not contain a=
ny address information at all <br>
&gt;&gt;&gt;&gt; (you can send an offer without any candidates), so it is a=
 special case no matter what.<br>
&gt;&gt;&gt;=C2=A0<br>
&gt;&gt;&gt; Yes, but the point is that you cannot address the m=3Dsection =
parameters via address:port, so every <br>
&gt;&gt;&gt; piece of text in the document that suggests that you do so nee=
ds to be repaired.<br>
&gt;&gt;=C2=A0<br>
&gt;&gt;&gt; You don=E2=80=99t need to address the parameters via address:p=
ort. You will address the parameters via the BUNDLE-tag.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Yes, the answerer picks the BUNDLE address:port =E2=80=93 which it=
 has to do no matter what =E2=80=93 but what is does is picking an <br>
&gt;&gt; m- line (the m- line containing the address:port selected to be us=
ed) and assigns the BUNDLE-tag to it. <br>
&gt;<br>
&gt; Yes, but that&#39;s not in fact what the text I quoted says, or is imp=
lied by much of the rest of the document does.<br>
<br>
</span>Sections 8.3.1 talks about selecting an m=3D section.</blockquote><d=
iv><br></div><div>Yes. I haven&#39;t carefully studied that section, but th=
is is the offerer text and as I said, this is incorrect.</div><div><br></di=
v><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
As far as the rest of the document is concerned, I don&#39;t think we can g=
et rid of the address:port text, because many of the offerer procedures abo=
ut assigning a given address:port to a given m- section.<br>
<br>
Also, many of the answerer procedures (removing m- sections etc) are based =
on the address:port value of the m- section in the corresponding offer.</bl=
ockquote><div><br></div><div>Yes, I agree we have to be clear that the addr=
ess:port needs to be assigned to a given m=3D section, just as all the othe=
r parameters need to be assigned properly. My concern is about treating add=
ress:port as special; that seems to conflict with trickle.</div><div><br></=
div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, while it may be possible to introduce a head/tagged/bundle m- section c=
oncept, I don&#39;t think we are going to get rid of the address:port text.=
<br>
<br>
Regards,<br>
<span class=3D"HOEnZb"><font color=3D"#888888">=C2=A0<br>
Christer<br>
=C2=A0<br>
<br>
</font></span></blockquote></div><br></div></div>

--0000000000002c5df8056a39568f--


From nobody Thu Apr 19 14:48:07 2018
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 C947A126DFB for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 14:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyElgNtsw0uI for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 14:48:03 -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 3FE1512420B for <mmusic@ietf.org>; Thu, 19 Apr 2018 14:48:03 -0700 (PDT)
X-AuditID: 1207440e-7bfff70000000ced-2e-5ad90e904956
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 37.96.03309.19E09DA5; Thu, 19 Apr 2018 17:48:01 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w3JLlwj8010471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 19 Apr 2018 17:47:59 -0400
To: Flemming Andreasen <fandreas@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>,  Colin Perkins <csp@csperkins.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu>
Date: Thu, 19 Apr 2018 17:47:58 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupileLIzCtJLcpLzFFi42IRYndR1J3IdzPK4OMxG4vlL08wWry/oGux f/F5Zoupyx+zOLB4TPm9kdVj2v37bB5Llvxk8mh7doc9gCWKyyYlNSezLLVI3y6BK+PE/Yes BR9MK669W8/UwDhBq4uRg0NCwETiwgfdLkYuDiGBHUwS92//YodwHjJJvG7pYgYpEhYIkVjy UgkkLiKwilHiwIV1jCBxIYEiidfTbboYOTnYBLQk5hz6zwJi8wrYS+y8cIUVxGYRUJV4d2cB I4gtKpAmcX/zJEaIGkGJkzOfgNVzCthKNPZ2gNnMAmYS8zY/ZIawxSVuPZnPBGHLSzRvnc08 gZF/FpL2WUhaZiFpmYWkZQEjyypGucSc0lzd3MTMnOLUZN3i5MS8vNQiXWO93MwSvdSU0k2M kGDm28HYvl7mEKMAB6MSD++HdTeihFgTy4orcw8xSnIwKYnyHpsMFOJLyk+pzEgszogvKs1J LT7EKMHBrCTCW8p0M0qINyWxsiq1KB8mJc3BoiTOy2ayN0pIID2xJDU7NbUgtQgmK8PBoSTB u5QXqFGwKDU9tSItM6cEIc3EwQkynAdo+H2QGt7igsTc4sx0iPwpRl2OKc/7e5iFWPLy81Kl xHlLQYoEQIoySvPg5sCS0CtGcaC3hHnjQKp4gAkMbtIroCVMQEsMVG6ALClJREhJNTB2Kan/ dpzqLNMy4UTRL6/axepJc7JUjp+4+fiJZo2n3x3pZ4V1OcKqz+4V8v2UXV+WO+28+BO3Db9c c8qtp5hPOvUs9XFywjSnXWdD5Jxu/DY6WyEj/mKmyaUH9+dErz+Rue4G4z2bIvOlLZpF4hyN R8qNKlVVPq1Rvv9rRdePtay519bL/M9UYinOSDTUYi4qTgQASc86qh0DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uEC6jSUpUKPTailekqpOmTJvFeY>
Subject: Re: [MMUSIC] INPUT NEEDED: Edits to 4566bis based on discussion in London
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 21:48:06 -0000

Flemming,

Thanks for responding. I was despairing at getting anyone to respond.

On 4/18/18 11:35 PM, Flemming Andreasen wrote:
> 
> 
> On 4/5/18 5:17 PM, Paul Kyzivat wrote:
>> I'm working on making the changes to 4566bis that were called for 
>> based on the discussion in London. After reviewing all of that I have 
>> some questions for which I need feedback from the wg.
>>
>> * Open Issue 3 - Regarding section 5.11 (z=):
>>
>> After reviewing the text for t=, r=, z=, the meaning of z= seems 
>> pretty clear to me. The text for z= only talks about how it works with 
>> r=. In principle, if the adjustment time precedes the start time from 
>> t= then I suppose it *might* also apply there, and perhaps to stop 
>> time as well.
>>
>> From the text and examples it is clear that this isn't usable for 
>> anything else. E.g., it does *not* provide an adjustment that yields 
>> local time.
>>
>> I could reword to say that it does *not* apply to the start/stop times 
>> in t=, or that it definitely only applies to r=. Thoughts?
>>
> Section 5.11 (z=) says:
> <quote>
> 
>   Adjustments apply to all "t=" and
>     "r=" lines in a session description.
> 
> </quote>
> 
> If I understood Colin's explanation in London correctly, then I believe 
> it *should* only apply to the "r=" line, but that's not what it 
> currently says. Maybe Colin can weigh in again ? In either case, I don't 
> find the text as clear as you do, so adding a few more lines of text 
> would be helpful.

OK. I'll just add some additional text making it even clearer.

>> * Open Issue 7 - Regarding section 8.2.2 ("proto"):
>>
>> The minutes (regarding udptl) say:
>>
>> "Action: will grandfather T.38 and keep the text as is. Also change to 
>> currently defined registration procedure."
>>
>> What was meant here? The registration procedure says RFC Required. 
>> Changing to conform to that is different from grandfathering T.38.
>>
>> ISTM that all is well as it is.
>>
> The minutes 
> (https://datatracker.ietf.org/meeting/101/materials/minutes-101-mmusic/) 
> say that:
> <quote>
> 
> 	There was also discussion on how to handle udptl, concluding that the
> 	registry information for udptl is incorrect but that 4566bis will
> 	grandfather T.38 and keep the text as is. The currently defined
> 	registration procedure should however be changed to not only allow
> 	referencing standards track RFC. [Action: Authors]
> 
> </quote>
> 
> My memory may not serve me well here, but I thought we said that it 
> should in fact reference a standards track RFC (there was some back and 
> forth discussion between our ADs on this point after the initial 
> conclusion I believe). Probably best to listen to the meeting recording 
> on this one to verify what the final conclusion was.

I listened to the discussion live. I can go back and double check. But 
my recollection was that referencing an RFC was brought up. (I think by 
me.) But there is currently no such RFC, so following that path would 
entail writing one, and there was no interest in doing that. My 
understanding was that the decision was to grandfather the registry 
referencing T.38 even though the rules require reference to an RFC.

But that is the status quo, so it appears to me that no change is required.

>> * Open Issue 8 - Regarding section 8.2.3 ("fmt"):
>>
>> The text implies that the namespace for udp formats consists of mime 
>> types. It says:
>>
>>    ... If no media
>>    subtype exists, it is RECOMMENDED that a suitable one be registered
>>    through the IETF process [RFC6838] by production of, or reference to,
>>    a standards-track RFC that defines the transport protocol for the
>>    format.
>>
>> But IIUC rfc6838 makes no provision for defining a *transport 
>> protocol* for a mime type.
>>
>> I'm not even entirely sure what rfc4566 intended here. Was it that the 
>> content of each UDP packet is to conform to the definition of the mime 
>> type? What about ordering rules that impose requirements on sequences 
>> of packets?
>>
>> Is it intended that the media types suitable for use as udp formats 
>> are only those that have something special in their definitions? Or 
>> may any mime type be used if it can fit in a UDP packet?
> Here is what the minutes say:
> <quote>
> 
>      *	Open Issue #8 - Where are media format (“fmt”) registrations to be
>      	done?
> 	Colin commented that the only “proto” that currently has a
> 	well-defined registration policy (in RFC 3555) are the ones based on
> 	RTP. A discussion concluded to clarify that the media format namespace
> 	and registration procedures depends on “proto” value and that “fmt”
> 	registration procedures must also be specified when registering a new
> 	“proto”. Jonathan offered to provide text giving some guidance.
> 	[Action: Jonathan and authors]
> 
> </quote>
> 
> I'd prod Jonathan for some text here.

I'll contact Jonathan. But my question was a bigger one than that. My 
question is what does it *mean* for the fmt for UDP to be a mime type? 
This was never explained, from the beginning. I *guess* that the intent 
was that every UDP packet body conform to the mime type. Was that the 
original intent? Or is the mime type somehow to describe the whole 
stream of packets?

IOW, it seems to me that the definition of fmt for UDP is 
underspecified. I would like to complete the specification but don't 
know what the intent is. I can make something up, but that seems like a 
bad idea.

I'll also note that I'm not aware of any cases that actually use UDP as 
transport and a mime type as the fmt.


>> * Open Issue 9 - Regarding section 8.2.5 ("bwtype"):
>>
>> The notes say:
>>
>> "Check the current IANA registry, did they change the registry and 
>> update accordingly."
>>
>> The registry does now have the mux category, and the entries for CT 
>> and AS reference both 4566 and mux-attributes.
>>
>> AFAICT the only thing to do is update these two registry entries to 
>> reference this bis rather than 4566. Did I miss anything?
>>
> 
> Here is what we have in the minutes:
> <quote>
> 
>      *	Open Issue #9 - Should IANA registration of “CT” and “AS” bandwidth
>      	specifiers be updated to point to 4566bis instead of to RFC 4566 and
> 	draft-ietf-mmusic-sdp-mux-attributes as today?
> 	Ben C commented that the current text “should be registered” seems
> 	un-enforceable and that the WG should pick a text pointing to one of
> 	the currently defined procedures. This is also applicable to open
> 	issue #7. It was concluded to re-check IANA registry and refine text
> 	in 4566bis accordingly. [Action: Authors]
> 
> </quote>

Not really. I'll query Ben for more about what he meant.

	Thanks,
	Paul


From nobody Thu Apr 19 15:01:13 2018
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 2EED3126C3D for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 15:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEULA8gD2zsN for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 15:01:08 -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 6076B12E85B for <mmusic@ietf.org>; Thu, 19 Apr 2018 15:01:08 -0700 (PDT)
X-AuditID: 1207440d-7e7ff70000006fd3-66-5ad911a1a260
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id AE.6A.28627.2A119DA5; Thu, 19 Apr 2018 18:01:06 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w3JM14WE011176 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 19 Apr 2018 18:01:05 -0400
To: mmusic@ietf.org
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <0900a2bc-371f-42fa-19cd-357986c8e1bc@alum.mit.edu>
Date: Thu, 19 Apr 2018 18:01:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrAIsWRmVeSWpSXmKPExsUixO6iqLtY8GaUwedlbBZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRs+PxIK3EhXXj11kbGC8KtTFyMkhIWAiMf3zFLYuRi4OIYEd TBInPn9ignC+M0kcvP2cFcQRFtjMKLH1wB8WkBYRAWGJGW//QrXsZpY48nsfWIJNQEtizqH/ YDavgL3Eg/XXmUFsFgFVib65X8DiogJpEvc3T2KEqBGUODnzCVicE6j+3aSFTCA2s4CZxLzN D5khbHGJW0/mQ8XlJba/ncM8gZF/FpL2WUhaZiFpmYWkZQEjyypGucSc0lzd3MTMnOLUZN3i 5MS8vNQiXSO93MwSvdSU0k2MkMDk3cH4f53MIUYBDkYlHt4P625ECbEmlhVX5h5ilORgUhLl PTYZKMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmEt5TpZpQQb0piZVVqUT5MSpqDRUmcl81kb5SQ QHpiSWp2ampBahFMVoaDQ0mC11IAqFGwKDU9tSItM6cEIc3EwQkynAdouBVIDW9xQWJucWY6 RP4Uoy7HlOf9PcxCLHn5ealS4rw+IEUCIEUZpXlwc2AJ5RWjONBbwrx5IFU8wGQEN+kV0BIm oCUGKjdAlpQkIqSkGhhl7G44P//8iNl5v7B3n3DlN4W2qYav5yctmMG7pOlxxYxK01kLe1yT bJ37WKUWhRu5Olk9EFdSOHSqaeEWt64TapxpofvKN855PP+H9u3nR77d3eygseKS/L6UlbGn Nynsn5KTrv0hdcXUlAtxs38cb2N6EWKx194xv/7NvOKw/R1nHu1YYZiuxFKckWioxVxUnAgA woHA/QMDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/v9guQXMETcK3Eh_l-UQuQ_Ic3eE>
Subject: Re: [MMUSIC] [ MMUSIC Chairs: Note action required ]. Re: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 19 Apr 2018 22:01:10 -0000

See end.

On 4/19/18 5:56 AM, Ben Campbell wrote:
> MMUSIC chairs, please see request below:
> 
> On Apr 17, 2018, at 8:18 PM, Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>> wrote:
> 
>>     >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>     >>>>> address:port, because if the peer rejects BUNDLE but accepts
>>     the m=
>>     >>>>> section then it's broken.
>>     >>>>
>>     >>>> Note that in this case the usage of BUNDLE has already been
>>     negotiated.
>>     >>>> Then, if the answerer does not accept the new m= section into
>>     the BUNDLE
>>     >>>> group, it needs to send an offer where it removes it, as
>>     described in
>>     >>>> section 8.3.3.
>>     >>>
>>     >>> Well, both of these options correspond to insisting that the
>>     m= section
>>     >>> be in the BUNDLE group. If I just want to suggest it, I would
>>     have to provide
>>     >>> a fresh unique address. Or are you saying that's impossible.
>>     >>>
>>     >> Yes.
>>     >>
>>     >> Previously, when the offerer wanted to add a new m- section to
>>     a BUNDLE
>>     >> group, it had to choice of either assigning a unique address or a
>>     >> previously negotiated bundle address.
>>     >>
>>     >> That option was removed as part of task (triggered by WGLC
>>     comments etc)
>>     >
>>     > That seems like a pretty material change. Was there a call for
>>     consensus on that?
>>
>>     No. But, the suggested changes were indicated on the list, there
>>     were pull requests etc, so people were informed about it and had a
>>     chance to comment/object.
>>
>>
>> Hmm... Ben, do you think these were properly surfaced to the WG?
> 
> I seem to recall non-trivial discussion about it on list, but I am not 
> in a position to verify it prior to the telechat.
> 
> Chairs/shepherd: Please comment on whether you believe the 
> aforementioned change represents wg consensus.

I'm neither, but I'll comment.

Finding suitable terminology here has been a struggle from the 
beginning. I was the instigator of one wholesale change, but it was 
subsequently heavily revised (I think multiple times). Everything has 
been word smithed to work around many people's objections. Through those 
changes I have generally been quiet because I had my say, and each 
change seemed "good enough" to me, though never something that I thought 
was "great". I would be pleased to have something better.

Clearly it is hard to get the wording to be both precise and clear. I 
suspect it might be possible to do better, but I don't know that for 
sure. The only way to verify that seems to be to make the change across 
the document and then review it again. (It never seems to be something 
that can be done adequately via a global search and replace.)

I sympathize with Christer that this seems to be a "fetch a rock" 
exercise. If anything is to be done, I think we should not ask Christer 
to fix it. Rather, I think those who aren't satisfied with the current 
text should create a variant of the whole document and then we can have 
a bake off.

	Thanks,
	Paul


From nobody Thu Apr 19 18:48:33 2018
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 A69B712EC1B for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 18:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 jaASqbSrfJof for <mmusic@ietfa.amsl.com>; Thu, 19 Apr 2018 18:48:25 -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 4784F12EB47 for <mmusic@ietf.org>; Thu, 19 Apr 2018 18:48:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7730; q=dns/txt; s=iport; t=1524188895; x=1525398495; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=Yvxrbpac4g7aIQozeszxBRYcGaUbCcZY57GlglvXUWY=; b=g7csqVpl0fARA1CPw8cpMmxnD1IVTWOY0yy9FsdUiQnvH42lxUJDQ05x oyGjPTg4Dr6Dokm3xRJSEcT5R4uzlmHZ7NFlfiCak6m3brU1b+7+Ql61F NK94fK3jk8X2tmkxHnlatif6RkvRm/h4u7Frm1NTnENANZOVrldTLpkYJ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/CABfRtla/5xdJa1bDg4BAQEEAQE?= =?us-ascii?q?KAQGDQmF6hBKUeYFLCCGBD5RrCyOERgKCQSE3FQECAQEBAQEBAmwcDIUjAQU?= =?us-ascii?q?jDwEFUQkCDgoCAiYCAlcGAQwIAQGEfA0Pi1ebQIIchFiDaoIWBYEJhn2BVD+?= =?us-ascii?q?BDyMMgUZoLoMRAgOBOoMjglQCl20IhVmFLIMyBoE0hhWFBIc3gX2Gc4ElMiK?= =?us-ascii?q?BUk0jFYJuAQEPgh8XiFmFBFYjkAIBAQ?=
X-IronPort-AV: E=Sophos;i="5.49,299,1520899200"; d="scan'208";a="102153182"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Apr 2018 01:48:14 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w3K1mF4g016898; Fri, 20 Apr 2018 01:48:15 GMT
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, IETF MMUSIC WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <a1c8b578-59f8-fbed-6690-6a66e11c95f2@cisco.com>
Date: Thu, 19 Apr 2018 21:48:15 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/fURR2ipjPJooq1RWSZfRKpWN8rA>
Subject: Re: [MMUSIC] INPUT NEEDED: Edits to 4566bis based on discussion in London
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 01:48:32 -0000

On 4/19/18 5:47 PM, Paul Kyzivat wrote:
> Flemming,
>
> Thanks for responding. I was despairing at getting anyone to respond.
>
> On 4/18/18 11:35 PM, Flemming Andreasen wrote:
>>
>>
>> On 4/5/18 5:17 PM, Paul Kyzivat wrote:
>>> I'm working on making the changes to 4566bis that were called for 
>>> based on the discussion in London. After reviewing all of that I 
>>> have some questions for which I need feedback from the wg.
>>>
>>> * Open Issue 3 - Regarding section 5.11 (z=):
>>>
>>> After reviewing the text for t=, r=, z=, the meaning of z= seems 
>>> pretty clear to me. The text for z= only talks about how it works 
>>> with r=. In principle, if the adjustment time precedes the start 
>>> time from t= then I suppose it *might* also apply there, and perhaps 
>>> to stop time as well.
>>>
>>> From the text and examples it is clear that this isn't usable for 
>>> anything else. E.g., it does *not* provide an adjustment that yields 
>>> local time.
>>>
>>> I could reword to say that it does *not* apply to the start/stop 
>>> times in t=, or that it definitely only applies to r=. Thoughts?
>>>
>> Section 5.11 (z=) says:
>> <quote>
>>
>>   Adjustments apply to all "t=" and
>>     "r=" lines in a session description.
>>
>> </quote>
>>
>> If I understood Colin's explanation in London correctly, then I 
>> believe it *should* only apply to the "r=" line, but that's not what 
>> it currently says. Maybe Colin can weigh in again ? In either case, I 
>> don't find the text as clear as you do, so adding a few more lines of 
>> text would be helpful.
>
> OK. I'll just add some additional text making it even clearer.
>
>>> * Open Issue 7 - Regarding section 8.2.2 ("proto"):
>>>
>>> The minutes (regarding udptl) say:
>>>
>>> "Action: will grandfather T.38 and keep the text as is. Also change 
>>> to currently defined registration procedure."
>>>
>>> What was meant here? The registration procedure says RFC Required. 
>>> Changing to conform to that is different from grandfathering T.38.
>>>
>>> ISTM that all is well as it is.
>>>
>> The minutes 
>> (https://datatracker.ietf.org/meeting/101/materials/minutes-101-mmusic/) 
>> say that:
>> <quote>
>>
>>     There was also discussion on how to handle udptl, concluding that 
>> the
>>     registry information for udptl is incorrect but that 4566bis will
>>     grandfather T.38 and keep the text as is. The currently defined
>>     registration procedure should however be changed to not only allow
>>     referencing standards track RFC. [Action: Authors]
>>
>> </quote>
>>
>> My memory may not serve me well here, but I thought we said that it 
>> should in fact reference a standards track RFC (there was some back 
>> and forth discussion between our ADs on this point after the initial 
>> conclusion I believe). Probably best to listen to the meeting 
>> recording on this one to verify what the final conclusion was.
>
> I listened to the discussion live. I can go back and double check. But 
> my recollection was that referencing an RFC was brought up. (I think 
> by me.) But there is currently no such RFC, so following that path 
> would entail writing one, and there was no interest in doing that. My 
> understanding was that the decision was to grandfather the registry 
> referencing T.38 even though the rules require reference to an RFC.
>
> But that is the status quo, so it appears to me that no change is 
> required.
I agree wrt. the existing T.38 registration. I'm not sure about whether 
we wanted to make changes to the registration procedures documented in 
4566bis in general.

>
>>> * Open Issue 8 - Regarding section 8.2.3 ("fmt"):
>>>
>>> The text implies that the namespace for udp formats consists of mime 
>>> types. It says:
>>>
>>>    ... If no media
>>>    subtype exists, it is RECOMMENDED that a suitable one be registered
>>>    through the IETF process [RFC6838] by production of, or reference 
>>> to,
>>>    a standards-track RFC that defines the transport protocol for the
>>>    format.
>>>
>>> But IIUC rfc6838 makes no provision for defining a *transport 
>>> protocol* for a mime type.
>>>
>>> I'm not even entirely sure what rfc4566 intended here. Was it that 
>>> the content of each UDP packet is to conform to the definition of 
>>> the mime type? What about ordering rules that impose requirements on 
>>> sequences of packets?
>>>
>>> Is it intended that the media types suitable for use as udp formats 
>>> are only those that have something special in their definitions? Or 
>>> may any mime type be used if it can fit in a UDP packet?
>> Here is what the minutes say:
>> <quote>
>>
>>      *    Open Issue #8 - Where are media format (“fmt”) 
>> registrations to be
>>          done?
>>     Colin commented that the only “proto” that currently has a
>>     well-defined registration policy (in RFC 3555) are the ones based on
>>     RTP. A discussion concluded to clarify that the media format 
>> namespace
>>     and registration procedures depends on “proto” value and that “fmt”
>>     registration procedures must also be specified when registering a 
>> new
>>     “proto”. Jonathan offered to provide text giving some guidance.
>>     [Action: Jonathan and authors]
>>
>> </quote>
>>
>> I'd prod Jonathan for some text here.
>
> I'll contact Jonathan. But my question was a bigger one than that. My 
> question is what does it *mean* for the fmt for UDP to be a mime type? 
> This was never explained, from the beginning. I *guess* that the 
> intent was that every UDP packet body conform to the mime type. Was 
> that the original intent? Or is the mime type somehow to describe the 
> whole stream of packets?
>
I'm not sure either.
> IOW, it seems to me that the definition of fmt for UDP is underspecified. 
I agree.
> I would like to complete the specification but don't know what the 
> intent is. I can make something up, but that seems like a bad idea.
>
> I'll also note that I'm not aware of any cases that actually use UDP 
> as transport and a mime type as the fmt.
>
Maybe Colin and Jonathan can help with additional input here. In the 
absence of that, I'd suggest you come up with a proposal.

>
>>> * Open Issue 9 - Regarding section 8.2.5 ("bwtype"):
>>>
>>> The notes say:
>>>
>>> "Check the current IANA registry, did they change the registry and 
>>> update accordingly."
>>>
>>> The registry does now have the mux category, and the entries for CT 
>>> and AS reference both 4566 and mux-attributes.
>>>
>>> AFAICT the only thing to do is update these two registry entries to 
>>> reference this bis rather than 4566. Did I miss anything?
>>>
>>
>> Here is what we have in the minutes:
>> <quote>
>>
>>      *    Open Issue #9 - Should IANA registration of “CT” and “AS” 
>> bandwidth
>>          specifiers be updated to point to 4566bis instead of to RFC 
>> 4566 and
>>     draft-ietf-mmusic-sdp-mux-attributes as today?
>>     Ben C commented that the current text “should be registered” seems
>>     un-enforceable and that the WG should pick a text pointing to one of
>>     the currently defined procedures. This is also applicable to open
>>     issue #7. It was concluded to re-check IANA registry and refine text
>>     in 4566bis accordingly. [Action: Authors]
>>
>> </quote>
>
> Not really. I'll query Ben for more about what he meant.
>
Sounds good.

Thanks

-- Flemming


>     Thanks,
>     Paul
> .
>


From nobody Fri Apr 20 00:16:08 2018
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 7B05E12D87A for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 00:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXpVDnLljnNg for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 00:16: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 B679012D775 for <mmusic@ietf.org>; Fri, 20 Apr 2018 00:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524208560; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=5KvN/5QN8MlRJSKzE+CHU/YYpyyV96ZZJMTufNz4hSI=; b=Qd2upBrOHN2FPtqc+3xMo14TIpa8g2BNBTStreBBTGl70jy4tbH7zJIun/1M7HMz 9cpo2sJICWh68Lb2dECYAzIauLaELk4f95FSZDQsQJWgPN64iNdcWnnJqDgfo8t9 2KNDPEv4qOouOXxjuwYT9BA4uWJITqYyGjtdiBG9Gwg=;
X-AuditID: c1b4fb3a-ae7ff7000000795a-94-5ad993af230d
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D8.EA.31066.FA399DA5; Fri, 20 Apr 2018 09:16:00 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Fri, 20 Apr 2018 09:15:59 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseCAAZvZAIAAP3yAgAA0rgD//9WjAIAAJksw///hOwCAAUs4gA==
Date: Fri, 20 Apr 2018 07:15:58 +0000
Message-ID: <D6FF62E6.2E737%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se> <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com>
In-Reply-To: <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <34FD8A3F52133C4C823A2A1BBFEF14BE@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsUyM2K7uu6GyTejDPbMY7PY83cRu8X8ztPs FtNnvWOzWPH6HLvF+wu6FjP+TGS2OL9zPZPF1OWPWRw4PKb83sjqsWTJTyaPWTufsHhMftzG HMASxWWTkpqTWZZapG+XwJVx9EALU8E/04qdLzYyNzCe1+pi5OSQEDCRaOz+z9zFyMUhJHCE UWLeqTNsIAkhgcWMEuf2R3QxcnCwCVhIdP/TBgmLCChI/PpzggWknlngPJPE3G3NYPXCAukS Nx4sYgGpFxHIkLj/IBOivk7iV98cZpAwi4CqxM+f1iBhXgFriR9PJzBBbGpmk5i7wB+khFMg UGJKowJImFFATOL7qTVgJcwC4hK3nsxngrhYQGLJnvPMELaoxMvH/1hBbFEBPYkNJ26zg4yR EFCSuL3BCaJVT+LG1ClsELa1xIXfl6BsbYllC18zQ1wjKHFy5hOWCYzis5Bsm4WkfRaS9llI 2mchaV/AyLqKUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzBqD275bbWD8eBzx0OMAhyMSjy8 5W03o4RYE8uKK3MPMUpwMCuJ8CaYAYV4UxIrq1KL8uOLSnNSiw8xSnOwKInzOqVZRAkJpCeW pGanphakFsFkmTg4pRoY5wo84T34J9J80pwv81fZHdaovnQtZsITvc1mxz6xxO7NCnFhKbjh dl4kY83yDy+eh8mcjfFf5HrLa8qyGyt9rXS002eW+bj+En1QGH1rQaPP15QFN3XEOorDc9K4 Q/827DA+/+NM16u2xF5v9aa+qhlKTh6vDlQpFp1VmSmscZZpn0v3tL7dSizFGYmGWsxFxYkA Uj+hV9YCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/iT7TNgJH00dC3Ru6-BCdD8USWnQ>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 07:16:06 -0000

Hi,

>>>> I think this has turned into an argument about style. One usage may
>>>>be more pleasing to the =B3ear=B2 than the other, but I don=B9t see iss=
ues
>>>>of=20
>>>> technical correctness or clarity here. As I asked for the the
>>>>=B3associated with=B2 question, is anyone arguing that the word choice
>>>>here is likely to cause material implementation errors?
>>>
>>> I don't think "address:port" versus "transport" will, but I do think
>>>"address:port" versus "m=3Dsection" or "transport parameters" will, and
>>>in fact I identified a material issue around trickle the other day,
>>>that I haven't seen a response to.
>>
>>
My suggestion was to add text about the special case of port 9 and IP
address 0.0.0.0.
>>
>>
Because, when you use trickle, the offer may not contain any address
information at all (you can send an offer without any candidates), so it
is a special case no matter what.
>
> Yes, but the point is that you cannot address the m=3Dsection parameters
>via address:port, so every piece of text in the document that suggests
>that you do so needs to be repaired.
>
> You don=B9t need to address the parameters via address:port. You will
>address the parameters via the BUNDLE-tag.
>
> Yes, the answerer picks the BUNDLE address:port =AD which it has to do no
>matter what =AD but what is does is picking an m- line
> (the m- line containing the address:port selected
 to be used) and assigns the BUNDLE-tag to it.
>
> Yes, but that's not in fact what the text I quoted says, or is implied
>by much of the rest of the document does.


You quoted the text in the following sections (I would be really useful to
have the section numbers in the review e-mail, btw, because I assume I
have to address them in a reply):


Section 8.1.:
-------------

   "When an offerer or answerer includes SDP attributes in bundled "m=3D=B3
   sections within a BUNDLE group for which the offerer and answerer
   BUNDLE addresses:ports have been selected, IDENTICAL and TRANSPORT
   mux category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are
   only included in the "m=3D" section indicated by the BUNDLE-tag in the
   offer or answer."

As I indicated earlier, I DO agree that we don=B9t need to talk about
address:port here, and it has been removed in the pull request I created.

So, the new text will only talk about the m=3D section:

   "When an offerer or answerer includes SDP attributes in bundled "m=3D=B3
    sections within a BUNDLE group, IDENTICAL and TRANSPORT
    mux category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are
    only included in the "m=3D" section indicated by the BUNDLE-tag in the
    offer or answer.=B2


Section 8.3.:
-------------

    "If the answer contains a BUNDLE group, the answerer MUST:

     o  Select an offerer BUNDLE address:port [Section 8.3.1]; and

     o  Select an answerer BUNDLE address:port [Section 8.3.2].=B2



Regarding the offerer BUNDLE address:port, the functional task performed
by the answerer IS selecting the offerer address:port. Section 8.3.1
describes the detailed SDP procedures for that, and it does talk the m=3D
section.

Regarding the answerer BUNDLE address:port, I don=B9t think we can change
anything there, because the task performed by the answerer IS selecting
the answerer address:port. AFTER that it will assign the address:port to
an m=3D section in the answer, as described in Section 8.3.2.


So, while we for sure could say something like =B3Select an offerer
tagged/head m=3D section=B2, the procedures would still describe the select=
ion
of the offerer BUNDLE address:port.




Section 8.3.1:
--------------

    "If all of the criteria above are fulfilled, the answerer MUST select
the suggested offerer BUNDLE address:port.=B2

In the beginning of the section, the text DOES talk about m=3D section, but
the specific text above IS about the answerer selecting the offerer BUNDLE
address:port, i.e., the address:port that the offerer is going to use.



Section 8.4:
------------
 =20

    "When an offerer receives an answer, if the answer contains a BUNDLE
     group, the offerer MUST check that any bundled "m=3D" section in the
     answer was indicated as bundled in the corresponding offer.  If there
     is no mismatch, the offerer MUST use the offerer BUNDLE address:port,
     selected by the answerer [Section 8.3.1], as the address for each
     bundled "m=3D" section.=B2


This text talks about the offerer determining what address:port it will
use.=20

Now, I do agree that we could modify this text by saying that the offerer
picks the tagged m=3D section, and then picks the address:port (and other
parameters) from that m=3D section.



Section 11:
-----------


     "In an offer, if the offer assigns a unique address:port to one or
      more bundled "m=3D" sections (excluding any bundle-only "m=3D"
      sections), the offerer MUST include ICE-related media-level
      attributes in each of those "m=3D" sections.  If the offerer assigns
      an offerer BUNDLE address:port (previously selected
      [Section 8.3.1] or newly suggested [Section 8.5.1]) to a bundled
      "m=3D" section (the "m=3D" section indicated by the offerer BUNDLE-
      tag), the offerer only includes ICE-related media-level SDP
      attributes in that "m=3D" section, following the procedures in
      Section 8.1.=B2


Similar to section 8.1, I DO agree that we can remove the text about
address:port here, and talk about including ICE attributes in bundled m=3D
sections.


Section 11.1.:
--------------

The first paragraph talks about assigning a unique address:port (i.e.,
before the BUNDLE group has been negotiated), so I am not sure we can
modify that. Or, perhaps we could talk about assigning attributes to m=3D
sections before a BUNDLE group has been negotiated.

The second and third paragraphs talk about the case when a BUNDLE group
has been negotiated. Similar to section 11, I do agree that we don=B9t need
to talk about address:port here. It=B9s enough to talk about assigning
attributes to the tagged m=3D section.


HISTORY:
--------

When writing the comments above, I think one of the reasons we talk about
address:port is because previously I think the draft talked about =B3BUNDLE
group=B2 even before it had been negotiated - so we had to distinguish
between the cases where the BUNDLE addresses:ports had been selected and
where they had not (initial offer). Currently, a BUNDLE group does not
exist until it has been negotiated, so the m=3D sections within a BUNDLE
group will ALWAYS contain the BUNDLE address:port (or bundle-only plus
port zero). So, while the procedures were clarified, some parts may have
become redundant.



Regards,

Christer












From nobody Fri Apr 20 00:21:25 2018
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 8806B12D574 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 00:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqu0uKO66JK2 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 00:21:20 -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 81F791201F8 for <mmusic@ietf.org>; Fri, 20 Apr 2018 00:21:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524208878; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=EDlfhr2KTQNlpZBGiKgvaFIVDEPeZ4xpUQpSMptHXHE=; b=B790rl5SWAXi1qM4y0Vjw67TEKkrfAe6X8YakdAdCC6weFPf8UYqFLXiR11HRjA8 ibInaC4xdU1QHunEMQOY3NmioxjqekrkRWcBx5p4LacmNiVOpfftQQiQXmhrAsMO Xx7CIr4u+rNP4PKirvup9goshYTeSkhDuDpeP02uheE=;
X-AuditID: c1b4fb25-8a3ff70000006561-52-5ad994eecbe0
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id DC.41.25953.EE499DA5; Fri, 20 Apr 2018 09:21:18 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0382.000; Fri, 20 Apr 2018 09:21:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] ice-options attribute: session- and media-level?
Thread-Index: AQHT2HgrgUz1UGYUZkWOyWP9nrLzRg==
Date: Fri, 20 Apr 2018 07:21:17 +0000
Message-ID: <D6FF6FE7.2E7A2%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D6FF6FE72E7A2christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNLMWRmVeSWpSXmKPExsUyM2K7pe67KTejDHYd0rKYuvwxiwOjx5Il P5kCGKO4bFJSczLLUov07RK4Mv4/Dyi4LVexbppsA+M9qS5GTg4JAROJq78esHQxcnEICRxh lFjYtpQJwlnMKDFr4iSgDAcHm4CFRPc/bZAGEQF1ia97e5hBbGEBN4l55xawQcTdJT59vcsK YetJTG/aDhZnEVCVWPt2JhOIzStgLTHh5USwOKOAmMT3U2vA4swC4hK3nsxngjhIQGLJnvPM ELaoxMvH/8BmigLN3HDiNjvIORICShK3NzhBtCZIvH10jxVivKDEyZlPWCYwCs1CMnUWkrJZ SMog4gYS78/NZ4awtSWWLXwNZetLbPxylhHCtpaYu/03E7KaBYwcqxhFi1OLk3LTjYz1Uosy k4uL8/P08lJLNjECo+Tglt+qOxgvv3E8xCjAwajEw3ux7WaUEGtiWXFl7iFGCQ5mJRHeBDOg EG9KYmVValF+fFFpTmrxIUZpDhYlcd6H5pujhATSE0tSs1NTC1KLYLJMHJxSDYx10W5PPy1p n3bi3Ku6nQadMw/cv6jNeKt5xSl3P3+edacOH5T9tjFI5wS3BKOxvHzSfa+fk+t2fLVct32y /TXpg8mLfi6KFnrGobNlWwevl/DnF1unmy0IfM/lICvBviTJZcOyKVWPlEVMgxZuNi+9MGnN 15lv89/cqjEssd3vOWvSB2WXyI4SJZbijERDLeai4kQAXlnD/44CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Z3ss29kO7SNnPgoA0gSYT7mUyho>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 07:21:23 -0000

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

Anyone???

I need this clarification to be able to address IESG comments given on BUND=
LE.

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 17 April 2018 at 12:42
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] ice-options attribute: session- and media-level?

Hi,

Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =91ice-options=
=92 attribute as both session- and media-level.

However, there is no description of what it means to use the attribute on m=
edia-level. Does it mean that the indicated ICE extension is only used for =
that particular media stream?

Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16 indicates the=
 attribute as session only (=93S=94).

Is there a need to define it as media-level attribute?

Regards,

Christer


--_000_D6FF6FE72E7A2christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <2EC5A0B7D8776C45AC60EACF376B9A46@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???&nbsp;</div>
<div><br>
</div>
<div>I need this clarification to be able to address IESG comments given on=
 BUNDLE.</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>Tuesday 17 April 2018 at 12:4=
2<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] ice-options attri=
bute: session- and media-level?<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>Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =91ice-opt=
ions=92 attribute as both session- and media-level.</div>
<div><br>
</div>
<div>However, there is no description of what it means to use the attribute=
 on media-level. Does it mean that the indicated ICE extension is only used=
 for that particular media stream?</div>
<div><br>
</div>
<div>Also, section 5.12 of&nbsp;draft-ietf-mmusic-sdp-mux-attributes-16 ind=
icates the attribute as session only (=93S=94).</div>
<div><br>
</div>
<div>Is there a need to define it as media-level attribute?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D6FF6FE72E7A2christerholmbergericssoncom_--


From nobody Fri Apr 20 02:54:17 2018
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 04BFD126B6D for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 02:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wr7O-JYtz_t1 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 02:54: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 E1056126C25 for <mmusic@ietf.org>; Fri, 20 Apr 2018 02:54:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524218051; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=8Wk7LxjqxNNA2I/e2OdymtYE0pXYFT7YLoD5xvsblW4=; b=MekshQKurg4+5HigwXwcmC67x4k0pOlzVvNFeMojUQwyME8TrTD7QOg8++hlsMM2 kMoWR17MOUya3ZXaGtFIfE95UwkhLBeq/h2AHLUceO8CJTi433z1b947u/rfHZe4 3Hl5KDYo145fl75nfd1m/eQXrzyEDRyadZl7PWWgWsc=;
X-AuditID: c1b4fb25-88bff70000006561-a7-5ad9b8c3d124
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 9E.71.25953.3C8B9DA5; Fri, 20 Apr 2018 11:54:11 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Fri, 20 Apr 2018 11:54:10 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Bo Burman <bo.burman@ericsson.com>, "Roni Even (A)" <roni.even@huawei.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
Thread-Index: AdPMES0/R3+uRXojQVG2VsIr3NCqRwBqS4VgArb2H4A=
Date: Fri, 20 Apr 2018 09:54:09 +0000
Message-ID: <D6FF8C39.2E810%christer.holmberg@ericsson.com>
References: <6E58094ECC8D8344914996DAD28F1CCD870EA5@DGGEMM506-MBX.china.huawei.com> <DB5PR07MB107811003A4497F734FA69BD8DBA0@DB5PR07MB1078.eurprd07.prod.outlook.com>
In-Reply-To: <DB5PR07MB107811003A4497F734FA69BD8DBA0@DB5PR07MB1078.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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <7143FF8B5CF8A04EA231EDB399BE682E@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM2K7je7hHTejDLZMFLSYuvwxi8WnY+dZ HJg8Wo68ZfVYsuQnUwBTFJdNSmpOZllqkb5dAlfG2TU/WAreq1TsaFjG1MC4WLaLkZNDQsBE 4tPuw+xdjFwcQgJHGCWajz9hg3AWM0p07V7L2MXIwcEmYCHR/U8bpEFEoFTizNY1TCC2sECA xJUFM9gh4oESG/+cZIawrSSWvOpkA7FZBFQlnv04DWbzClhLNBxcDbVsGaNE74xlYA2cArES R59NBBvKKCAm8f0UxAJmAXGJW0/mM0FcKiCxZM95ZghbVOLl43+sILaogJ7EhhO32UHulBBQ kri9wQmiVU/ixtQpbCBhZqC9M47LQYS1JZYtfM0McY6gxMmZT1gmMIrNQrJsFpLuWQjds5B0 z0LSvYCRdRWjaHFqcVJuupGxXmpRZnJxcX6eXl5qySZGYEwd3PJbdQfj5TeOhxgFOBiVeHgX LLgZJcSaWFZcmXuIUYKDWUmEN8EMKMSbklhZlVqUH19UmpNafIhRmoNFSZz3ofnmKCGB9MSS 1OzU1ILUIpgsEwenVANjhfUxHlYhkcTCQ9IqF8ok2RTWCQl1lUTEX7qZ8O2adfgxCx0m317z 7UvX1mcyeb2sO3rKvfWcbn+6rlOu/2I1vqglR76z/rZPCq/V+fCopKLm2KFv73Y5s1w75vD3 Noszu3xG3uK9idXzNbr15ncLrL7VkWfc0lAv9W5KssCMpfPkPoccD1ViKc5INNRiLipOBAB8 nwKbpQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7wLh14vA2NylPneuDr2SReOGCiQ>
Subject: Re: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 09:54:16 -0000

Hi,

I have reviewed the new version. Thank you for addressing my comments.

However, I think there is still some work (mostly editorial) to do.


SECTION 1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q1:

I think the Introduction is rather messy, but I don=B9t have a suggestion o=
n
how to fix it. However, there is the following statement:
   "This document defines SDP offer/answer [RFC3264] negotiation
   procedures to establish data channels for transport of well-defined
   subprotocols, to enable out-of-band negotiation.=B2

 I suggest to say=20

   "This document defines SDP offer/answer [RFC3264]
   Procedures that enable out-of-band negotiation for establishing data
channels for transport of well-defined
   subprotocols.=B2=20

---

Q2:

I suggest to remove the following:

   =B3In the future, data channels could be defined over other SCTP based
   protocols, such as SCTP over IP.  However, corresponding potential
   other "m=3D" line proto values are not considered in this document."

It is enough to specify what the draft does - not what may potentially
perhaps be done in future.

---

Q3:

Please add references to MSRP and BFCP on first occurrence.



SECTION 5:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q4:

The 3rd paragraph repeats much of the 1st paragraph. I think they can be
combined.


Q5:

There is no need to repeat text about =B3without the usage of DCEP=B2. It i=
s
enough to make it clear once in the beginning of document. This applies to
other sections too.



SECTION 5.1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


Q6:

The text talks about =B3The intention of the attribute is to blah blah=B2.
That sounds weird. Instead say =B3The attribute is used to blah blah=B2.



SECTION 5.1.9:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q7:

I think you can remove the first paragraph. Simply include the
[I-D.ietf-mmusic-sdp-mux-attributes] reference in the next sentence:

   "The multiplexing category [I-D.ietf-mmusic-sdp-mux-attributes] of the
"a=3Ddcmap:" attribute is SPECIAL."




SECTIONS 6.3 & 6.4:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q8:

You don=B9t have to say =B3Sends the offer=B2/=B3Sends the answer=B2.



SECTION 6.6:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q9:

The text seems to be about adding a new data channel. You should have a
separate sub-section (6.6.x) for that.

But, you should also have text about when sending a subsequent offer
without impacting the data channel. For example, the offer must (I assume)
include all attributes associated with the currently open data channels.



SECTION 6.6.1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q10:

The text says:

   "When the application requests the closing of a data channel that was
    negotiated via SDP offer/answer, the data channel stack always
    performs an SCTP SSN reset for this channel.=B2


However, it later says that a data channel is closed once the offer send
in order to close the data channel has been accepted.


Q11:

The text says:

   "If a client receives a data channel close indication (due to inband
    SCTP SSN reset or some other reason) without associated SDP offer
    then the client SHOULD generate an SDP offer which excludes this
    closed data channel.=B2


But, earlier in the section it says that it is subprotocol-specific
whether a O/A exchange is needed in order to close a data channel.



SECTION 6.7:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q12:

I think most of the text (apart from the error cases) could be
incorporated into the earlier offer/answer sections.

For example, the offer section should make it clear when "a=3Ddcmap:" is
included in an offer, and when it is not. There is no need for a separate
section to describe the case when "SDP offer has no "a=3Ddcmap:=B2 attribut=
es".


Regards,

Christer




From:  mmusic <mmusic-bounces@ietf.org> on behalf of Bo Burman
<bo.burman@ericsson.com>
Date:  Friday 6 April 2018 at 18:17
To:  "Roni Even (A)" <roni.even@huawei.com>, "mmusic@ietf.org"
<mmusic@ietf.org>
Subject:  Re: [MMUSIC] new revision in
draft-ietf-mmusic-data-channel-sdpneg-17


Thanks Roni,
=20
I believe this addresses my shepherd=B9s review nits.
=20
/Bo
=20
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of
Roni Even (A)
Sent: den 4 april 2018 14:34
To: mmusic@ietf.org
Subject: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17


=20
Hi,
I submitted a new revision of
https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-17
trying to address comments from Christer and Bo.
Thanks
Roni Even


From nobody Fri Apr 20 11:37:26 2018
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 57C7B127863 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 11:37:25 -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, T_DKIMWL_WL_MED=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZvhAoVbNSz6 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 11:37:23 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 13D521200F1 for <mmusic@ietf.org>; Fri, 20 Apr 2018 11:37:23 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id a2so4664522pff.8 for <mmusic@ietf.org>; Fri, 20 Apr 2018 11:37:22 -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=YJ5w65vCcsffgbHhLkkuxOrujcwwxBKEX6KFV5g9Ab0=; b=RrWmKwBM/Cmt+fLj/EeJcYJz19ZUNmePnmOk3OpqOLxv6Qt2uIoLeB+bXMQIrknJff jxLxUOmyh7CnMi36LhvODUP418IoeTQLWdRCMlgvyai3xqY6DfzB7GeFgrh0MmKnFazE 3zySCffVsifTljgI48mlJDN8nD3kuFQL0V9qsjktpHSYubf9WOzjFqkMtcNfQxcb3a3k f6TeM8Pa2Gcjf4oVVsXTwIWthnSzoj/qMr22UjQsICVK8vhpMZknh9vntmdMiayMQnUB oVTe1UOtKq3Pv8T1UN+a3pNubkXtTlladkrei6++VQQuPtkO2oIciq19lrc5HgjVn6/A 3XoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YJ5w65vCcsffgbHhLkkuxOrujcwwxBKEX6KFV5g9Ab0=; b=H1Jpc0mTsCZCvThSYXQjBAbuW86p+j3EaHVRExNxcZWDmmiuBbleOQMY5Jp/GdGQ6z RpMfeLGjwJsGfCry8GwVNm0pQcAgka6q3BQ1nfDC6rBJZOh5VHZDg7ND9hPNqCUK09ok eeMa4aihzToSPUTZh+xfPzKR0PblCelcii0qb4nnf9BunlW4Mm6yW7xBoHRB0VijWJXO dLHhOsxWnxFwfqHYq5WNwiFis4tqIl8DWJYlkwlSTvOP5y03x/3apNewnjmk/SvaHNBY bo8sdlbpbatnxQGKxvKWmyic1uWv71bW/cvI3lGPhlHuCI6C7oqAdXykTnPCmzxhDoNm /4gQ==
X-Gm-Message-State: ALQs6tCogG5S8qGu6mY0i583siUV2z97JsCj+SH57Kd4vlOcIX20WMzq 9DCbxvLCZJy6NPnjF14dVhA/J0g3
X-Google-Smtp-Source: AIpwx4+OcF9fleyB+m1tDdVX06jnKqEcdKZn563qWYoy3gOVRHp1kojrqrioli1aeLx4/Z4rLw5R4g==
X-Received: by 10.98.155.141 with SMTP id e13mr1145573pfk.157.1524249442426; Fri, 20 Apr 2018 11:37:22 -0700 (PDT)
Received: from mail-pl0-f47.google.com (mail-pl0-f47.google.com. [209.85.160.47]) by smtp.gmail.com with ESMTPSA id k14sm14321671pfb.139.2018.04.20.11.37.21 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 11:37:21 -0700 (PDT)
Received: by mail-pl0-f47.google.com with SMTP id z12-v6so5721692plo.1 for <mmusic@ietf.org>; Fri, 20 Apr 2018 11:37:21 -0700 (PDT)
X-Received: by 2002:a17:902:7042:: with SMTP id h2-v6mr11358613plt.249.1524249441311;  Fri, 20 Apr 2018 11:37:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.149.74 with HTTP; Fri, 20 Apr 2018 11:37:20 -0700 (PDT)
In-Reply-To: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com>
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com>
From: Roman Shpount <roman@telurix.com>
Date: Fri, 20 Apr 2018 14:37:20 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>
Message-ID: <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007fa2fb056a4bfa6b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xgB1WY-LtFh4QOhXfgNSLBtNTMo>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 18:37:25 -0000

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

Hi All,

I do not think ice-options was ever used as a media level attribute. Only
two ice-options defined in IANA registry (
https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and  rtp+ecn,
which are both session level.

Furthermore, RFC 5245 section 15.5 (
https://tools.ietf.org/html/rfc5245#section-15.5,) defined that ice-options
attribute is session level only. Thus, ice-options should be kept session
level for backwards compatibility.

If something more granular then session is needed, I think it should go
into candidate extension attribute, not into media level ice-options.

Bottom line, I think ice-options should be a a session level only attribute=
.

Regards,

_____________
Roman Shpount

On Fri, Apr 20, 2018 at 3:21 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Anyone???
>
> I need this clarification to be able to address IESG comments given on
> BUNDLE.
>
> Regards,
>
> Christer
>
> From: mmusic <mmusic-bounces@ietf.org> on behalf of Christer Holmberg <
> christer..holmberg@ericsson.com <christer.holmberg@ericsson.com>>
> Date: Tuesday 17 April 2018 at 12:42
> To: "mmusic@ietf.org" <mmusic@ietf.org>
> Subject: [MMUSIC] ice-options attribute: session- and media-level?
>
> Hi,
>
> Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =E2=80=98ice-=
options=E2=80=99
> attribute as both session- and media-level.
>
> However, there is no description of what it means to use the attribute on
> media-level. Does it mean that the indicated ICE extension is only used f=
or
> that particular media stream?
>
> Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16 indicates
> the attribute as session only (=E2=80=9CS=E2=80=9D).
>
> Is there a need to define it as media-level attribute?
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr"><div>Hi All,</div><div><br></div>I do not think ice-option=
s was ever used as a media level attribute. Only two ice-options defined in=
 IANA registry (<a href=3D"https://www.iana.org/assignments/ice/ice.xhtml">=
https://www.iana.org/assignments/ice/ice.xhtml</a>) are ice2 and =C2=A0rtp+=
ecn, which are both session level.<br><div><br></div><div>Furthermore, RFC =
5245 section 15.5 (<a href=3D"https://tools.ietf.org/html/rfc5245#section-1=
5.5,">https://tools.ietf.org/html/rfc5245#section-15.5,</a>) defined that i=
ce-options attribute is session level only. Thus, ice-options should be kep=
t session level for backwards compatibility.</div><div><br></div><div>If so=
mething more granular then session is needed, I think it should go into can=
didate extension attribute, not into media level ice-options.</div><div><br=
></div><div>Bottom line, I think ice-options should be a a session level on=
ly attribute.</div><div><br></div><div>Regards,</div></div><div class=3D"gm=
ail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature" data-smart=
mail=3D"gmail_signature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Fri, Apr 20, 2018 at 3:21 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>Anyone???=C2=A0</div>
<div><br>
</div>
<div>I need this clarification to be able to address IESG comments given on=
 BUNDLE.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"m_1649730924640007806OLK_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>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>Tuesday 17 April 2018 at 12:4=
2<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] ice-options attri=
bute: session- and media-level?<br>
</div>
<div><br>
</div>
<div>
<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>Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-<wbr>20 defines the =E2=
=80=98ice-options=E2=80=99 attribute as both session- and media-level.</div=
>
<div><br>
</div>
<div>However, there is no description of what it means to use the attribute=
 on media-level. Does it mean that the indicated ICE extension is only used=
 for that particular media stream?</div>
<div><br>
</div>
<div>Also, section 5.12 of=C2=A0draft-ietf-mmusic-sdp-mux-<wbr>attributes-1=
6 indicates the attribute as session only (=E2=80=9CS=E2=80=9D).</div>
<div><br>
</div>
<div>Is there a need to define it as media-level attribute?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</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>

--0000000000007fa2fb056a4bfa6b--


From nobody Fri Apr 20 11:44:56 2018
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 9A1A4129C6D for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 11:44:54 -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, T_DKIMWL_WL_MED=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJCNRPTqawQz for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 11:44:52 -0700 (PDT)
Received: from mail-pl0-x236.google.com (mail-pl0-x236.google.com [IPv6:2607:f8b0:400e:c01::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 B5D02127863 for <mmusic@ietf.org>; Fri, 20 Apr 2018 11:44:52 -0700 (PDT)
Received: by mail-pl0-x236.google.com with SMTP id s13-v6so5713901plq.11 for <mmusic@ietf.org>; Fri, 20 Apr 2018 11:44:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=CNnkLJn9DA9jWNIZnQ2aPdpnmrgz0tqnzbgty+iVwqU=; b=bNzVVmmQh4dRLRQhks0NsD5n+/XVfvXFUe8khLzg2ut0a4iRphbtj+iF+8QOxLYoDP BZoVqWIykhrjzfso1mRh6LdH53fCTuk9k2lHOlBAZnLnGagW1tjGFcw1TXVKktXx8dXQ 4rjVMs3G0qHfeqc79KBcg1taV1B9Z8BeXeS5VHAPqAO/YIpm3hlhPSSx1fEUd6gs1veq RjFtZ3QUHBP3qsdlankYa5dRPFUsr1kpRQs+vF5W11WBBZPsUiMyZBwG/6Vim0s4/IAG pVO2nUV/SZEbGFp7e78ljXC0Jjc/A2lh5WVaIyK1439xgboaF12b3GIgvTMrmswDtN7T EPnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=CNnkLJn9DA9jWNIZnQ2aPdpnmrgz0tqnzbgty+iVwqU=; b=p06+gd8Ik2tvmDjtGVsJKvedIldq8UoozwcdzVLRGK7kravKCMo7fTED7WA99iAsTC nDDRVnea01DI+9v2MNtfBDNYrlzASYolqsN+JNDLwzzb3uzVW8q0U6uFUgXWiaPusw4s OSkdvfBlUWG0n4U9Fiq3iTlrYZdhNOIuWG4q3g8s0yZuP6ulfHUr9woRxu2b/t/HOB9s BdBJ9rDom+a1ixrZYM5lIECxifBk4VcRV/0rXngtxcobX+coHxZlQk1Kx/zXgpL/MJq+ GEx9J0PffQihVN3svDeJ7dB9r71DkuNvZToham44dKa/H7/egesrCJMg4O5zLId3ePea m9AA==
X-Gm-Message-State: ALQs6tCnqoXkca1WchFBNJnbVJYuQ46N7Ic6OK95McGRK02j2c6ZIhM2 INuGDq6XxgU0sFKeRKEJREEhksDW
X-Google-Smtp-Source: AIpwx4/PXTH5gqoZNVeG2zVep7OdqqQUNgE+11G6sFMYvcNog/RyVFRgUacLGpxxpPqv4KrDbE3m1Q==
X-Received: by 2002:a17:902:7d86:: with SMTP id a6-v6mr11535708plm.264.1524249892215;  Fri, 20 Apr 2018 11:44:52 -0700 (PDT)
Received: from mail-pf0-f171.google.com (mail-pf0-f171.google.com. [209.85.192.171]) by smtp.gmail.com with ESMTPSA id f22sm14650668pff.146.2018.04.20.11.44.51 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 11:44:51 -0700 (PDT)
Received: by mail-pf0-f171.google.com with SMTP id q9so4674359pff.1 for <mmusic@ietf.org>; Fri, 20 Apr 2018 11:44:51 -0700 (PDT)
X-Received: by 10.167.128.207 with SMTP id a15mr10631556pfn.116.1524249891497;  Fri, 20 Apr 2018 11:44:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.149.74 with HTTP; Fri, 20 Apr 2018 11:44:51 -0700 (PDT)
From: Roman Shpount <roman@telurix.com>
Date: Fri, 20 Apr 2018 14:44:51 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtdj8ztLkPQdY0u=KWKm0wSca+8xZR1Sr8uKQ+nhgyBTA@mail.gmail.com>
Message-ID: <CAD5OKxtdj8ztLkPQdY0u=KWKm0wSca+8xZR1Sr8uKQ+nhgyBTA@mail.gmail.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="f4f5e80d8ff054ef6a056a4c156e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xJFqPpkcS_w7iT3WUyXVG4y7J5s>
Subject: [MMUSIC] Registry for candidate attributes extensions
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 18:44:55 -0000

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

Hi All,

Section 4.1 of ice-sip-sdp defines extension attributes for ICE candidates:

candidate-attribute   = "candidate" ":" foundation SP component-id SP
                        transport SP
                        priority SP
                        connection-address SP     ;from RFC 4566
<https://tools.ietf.org/html/rfc4566>
                        port         ;port from RFC 4566
<https://tools.ietf.org/html/rfc4566>
                        SP cand-type
                        [SP rel-addr]
                        [SP rel-port]
                        *(SP extension-att-name SP
                                extension-att-value)


extension-att-name    = token
extension-att-value   = *VCHAR


There is surprising little written about these extension attributes. Should
there be a requirement that these attributes must be defined in RFC and
that IANA registry for this attributes should be created?

Only attribute like this I saw in the wild is "generation". For example:

a=candidate:750991856 1 udp 25108223 237.30.30.30 58779 typ relay raddr
47.61.61.61 rport 54761 generation 0

This attribute is widely used, but I do not think this attribute is
actually defined anywhere.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr">Hi All,<div><br></div><div>Section 4.1 of ice-sip-sdp defi=
nes extension attributes for ICE candidates:</div><div><br></div><div>

<pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;ma=
rgin-bottom:0px;break-before:page;color:rgb(0,0,0);font-style:normal;font-v=
ariant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spa=
cing:normal;text-align:start;text-indent:0px;text-transform:none;word-spaci=
ng:0px;text-decoration-style:initial;text-decoration-color:initial">candida=
te-attribute   =3D &quot;candidate&quot; &quot;:&quot; foundation SP compon=
ent-id SP
                        transport SP
                        priority SP
                        connection-address SP     ;from <a href=3D"https://=
tools.ietf.org/html/rfc4566">RFC 4566</a>
                        port         ;port from <a href=3D"https://tools.ie=
tf.org/html/rfc4566">RFC 4566</a>
                        SP cand-type
                        [SP rel-addr]
                        [SP rel-port]
                        *(SP extension-att-name SP
                                extension-att-value)</pre>

<br><div class=3D"gmail_extra">

<pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;ma=
rgin-bottom:0px;break-before:page;color:rgb(0,0,0);font-style:normal;font-v=
ariant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spa=
cing:normal;text-align:start;text-indent:0px;text-transform:none;word-spaci=
ng:0px;text-decoration-style:initial;text-decoration-color:initial">extensi=
on-att-name    =3D token
extension-att-value   =3D *VCHAR</pre>

<div class=3D"gmail_extra"><br></div>There is surprising little written abo=
ut these extension attributes. Should there be a requirement that these att=
ributes must be defined in RFC and that IANA registry for this attributes s=
hould be created?</div><div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra">Only attribute like this I saw in the wild is &quot;generation&=
quot;. For example:</div><div class=3D"gmail_extra"><br>a=3Dcandidate:75099=
1856 1 udp 25108223 237.30.30.30 58779 typ relay raddr 47.61.61.61 rport 54=
761 generation 0</div><div class=3D"gmail_extra"><br></div><div class=3D"gm=
ail_extra">This attribute is widely used, but I do not think this attribute=
 is actually defined anywhere.</div><div class=3D"gmail_extra"><br></div><d=
iv class=3D"gmail_extra">Regards,</div><div class=3D"gmail_extra">_________=
____<br></div><div class=3D"gmail_extra"><div><div class=3D"gmail_signature=
" data-smartmail=3D"gmail_signature">Roman Shpount</div></div></div></div><=
/div>

--f4f5e80d8ff054ef6a056a4c156e--


From nobody Fri Apr 20 12:07:49 2018
Return-Path: <stpeter@mozilla.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 14907127599 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 12:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 fvUleYHE72LE for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 12:07:46 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::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 AB80C126D85 for <mmusic@ietf.org>; Fri, 20 Apr 2018 12:07:46 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id e20-v6so3727369itc.1 for <mmusic@ietf.org>; Fri, 20 Apr 2018 12:07:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to; bh=3+sE1hCcq6nG5VWBTXj49qCcmr6S7Y8G3chEPC/YDow=; b=bwZHKFfpcTfs+vyJ0rmzge6RACCr5L9fwE/FEyJK6EYkBMdeFZMpAUTP/zbUlF3foW /fbARkgx5fFwJDI2ZN6zi0ZQ2kVhmIw+msYaM5wirZHVGRoLeSJtLOL8I1f19bBTymU6 UqeZeasXVJUyMoMqDvUyifuVP8EMYHboiv3rQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to; bh=3+sE1hCcq6nG5VWBTXj49qCcmr6S7Y8G3chEPC/YDow=; b=Mr0imY1f3dngy1vlekhj1yn7YmijzA0SkMx2yFMl/F7s7a19XryioG12I4eq8ZQGJn GeaZNfyQIyNkNiImfeAAr0UZ5CM2iwULyOthtYGDtZVQyleR58Sb6P1HyX0coweGCkWe WputVQpMmsxmZMEhbsoLTAxQOKiF6tdOFsT4trjO7H7bdzmhEt7eNY/8LZXB8WCDodw3 WfX1L2gVTS0GM8OJLpaxuPfVECgffzuWok4HGBtFT70LaSrgtGTv/U1d9SOkcCkMVxIz nsz7pzhhuqdu47EoVqo45ObmGwSz2HQ6ImWka9p/B+AW8ToLuNgbLqPiTFXn0n41T5jO IV3w==
X-Gm-Message-State: ALQs6tAi0cqv171tuAaEzThXITR6YBMEO4BBJVuXYw0sPJwiUKhYtngk iV+JqyfJomnX+QbKLxm4Vy7rHA==
X-Google-Smtp-Source: AIpwx4/m4Et20wL9/BlPsCzVb07GpoO07G5ppjnkOVl/KYkDJ5eYHEvIL6FKKuUhHT91FT7pZdSv4w==
X-Received: by 2002:a24:7590:: with SMTP id y138-v6mr4630626itc.48.1524251266023;  Fri, 20 Apr 2018 12:07:46 -0700 (PDT)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id y192-v6sm1184564itb.0.2018.04.20.12.07.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 12:07:45 -0700 (PDT)
To: mmusic@ietf.org
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com> <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Openpgp: preference=signencrypt
Autocrypt: addr=stpeter@mozilla.com; prefer-encrypt=mutual; keydata= xsFNBFonEf4BEADvZ+RGsJoOyZaw2rKedB9pBb2nNXVGgymNS9+FAL/9SsfcrKaGYSiWEz7P Lvc97hWH3LACFAHvnzoktv+4IWHjItvhdi9kUQ3Gcbahe55OcdZuSXXH3w5cHF0rKz9aYRpN jENqXM5dA8x4zIymJraqYvHlFsuuPB8rcRIV9SKsvcy14w9iRqu770NjXfE/aIsyRwwmTPiU FQ0fOSDPA/x2DLjed/GYHem90C5vF4Er9InMqH5KAMLnjIYZ9DbPx5c5EME4zW/d648HOvPB bm+roZs4JTHBhjlrTtzDDpMcxHq1e8YPvSdDLPvgFXDcTD4+ztkdO5rvDkbc61QFcLlidU8H 3KBiOVMA/5Rgl4lcWZzGfJBnwvSrKVPsxzpuCYDg01Y/7TH4AuVkv5Na6jKymJegjxEuJUNw CBzAhxOb0H9dXROkvxnRdYS9f0slcNDBrq/9h9dIBOqLhoIvhu+Bhz6L/NP5VunQWsEleGaO 3gxGh9PP/LMyjweDjPz74+7pbyOW0b5VnIDFcvCTJKP0sBJjRU/uqmQ25ckozuYrml0kqVGp EfxhSKVqCFoAS4Q7ux99yT4re2X1kmlHh3xntzmOaRpcZsS8mJEnVyhJZBMOhqE280m80ZbS CYghd2K0EIuRbexd+lfdjZ+t8ROMMdW5L51CJVigF0anyYTcAwARAQABzSdQZXRlciBTYWlu dC1BbmRyZSA8c3RwZXRlckBtb3ppbGxhLmNvbT7CwZQEEwEIAD4WIQQ1VSPTuPTvyWCdvvRl YYwYf2gUqQUCWicR/gIbIwUJCWYBgAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRBlYYwY f2gUqdaREAChG8qU1853mP0sv2Mersns8TLG1ztgoKHvMXFlMUpNz6Oi6CjjaMNFhP7eUY4T D43+yQs7f4qCkOAPWuuqO8FbNWQ+yUoVkqF8NUrrVkZUlZ1VZBMQHNlaEwwu1CGoHsLoRohP SiZ0hpmGTWB3V6cDDK4KN6nl610WJbzE9LeKY1AxtePdJi2KM281U0Fz8ntij1jWu0gF2xU4 Sez46JDogHLWKgd0srauhcCVzZjAhiWrXp1+ryzSWYaZO8Kh8SnF1f4o6jtYikMqkxUaI5nX wvD3kNX4AMSkCAZfG7Jcfj/SLDojTcREgO87g7B9bcOOsHN4lj3lHoFV0aXpgPmjfIvAjJHu fHkXZAQAH8w0u9bgJqRn703+A4NPfLopnjegyhlNi7fQ3cMQV1H7Oj7WrB/pCcprx+1u/6Uq oTtDwWh1U5uVthVAI0QojpNWR08zABDX19TlGtVoeygaQV3CAEolxTiYQtCfVavUzUplCZ/t 3v4YiRov+NylflJd+1akyOs1IAgARf444BnoH1fotkpfXNOpp9wUXXwsQcFRdP7vpMkSCkc0 sxPNTVX3ei0QImp4NsrFdaep7LV3zEb3wkAp6KE5Qno4hVVEypULbvB0G6twNZbeRfcs2Rjp jnPb2fofvg2WhAKB20dnRfIfK8OKTD/P+JDcauJANjmekM7BTQRaJxH+ARAApPwkbOTChAQu jMvteb/xcwuL5JZElmLxIqvJhqybV7JknM+3ATyN0CTYQFvPTgIrhpk4zSn0A6pEePdK8mKK 5/aHyd7pr7rLEi1sI/X3UE8ld/E83MExksKrYbs0UX1wSQwYXU6g64KicnuP2Abqg+8wrQ18 1nPcZci9jJI75XVPnTdUpZD5aaQWGp7IJ06NTbiOk30I50ORfulgKoe4m3UfsMALFxIx3pJk oy76xC2tjxYGf+4Uq1M0iK3Wy655GrcwXq/5ieODNUcAZzvK5hsUVRodBq0Lq3g1ivQF4ba7 RQayDzlW6XgoeU49xnCr9XdZYnTnj4iaPmr2NtY6AacBwRz+bJsyugeSyGgHsnVGyUSMk8YN wZHvUykMjH21LLzIUX5NFlcumLUXDOECELCJwewui4W81sI5Sq/WDJet+iJwwylUX22TSulG VwDS+j66TLZpk1hEwPanGLwFBSosafqSNBMDVWegKWvZZVyoNHIaaQbrTIoAwuAGvdVncSQz ttC6KkaFlAtlZt3+eUFWlMUOQ9jxQKTWymyliWKrx+S6O1cr4hwVRbg7RQkpfA8E2Loa13oO vRSQy/M2YBRZzRecTKY6nslJo6FWTftpGO7cNcvbmQ6I++5cBG1B1eNy2RFGJUzGh1vlYo51 pdfSg0U1oPHBPCHNvPYCJ7UAEQEAAcLBfAQYAQgAJhYhBDVVI9O49O/JYJ2+9GVhjBh/aBSp BQJaJxH+AhsMBQkJZgGAAAoJEGVhjBh/aBSpAw0P/1tEcEaZUO1uLenNtqysi3mQ6qAHYALR Df3p2z/RBKRVx0DJlzDfDvJ2R/GRwoo+vyCviecuG2RNKmJbf1vSm/QTtbQMUjwut9mx6KCY CyKwniqdhaMBmjCfV2DB2MxxZLYMtDfx/2mY7vzAci7AkjC+RkSUByMEOkyscUydKC/ETdf9 tvI8GhTY/8Q7JSylS3lQA5pMUHiIf+KpSmqKZeBPkGc7nSKM1w1UKUvFAsyyVsiG6A/hWrTr 7tTQAl7YfjtOGE8n4IKGktvrT99bbh9wdWKZ5FdHUN9hx2Q8VP8+0lR1CH2laVFbEwCOv1vM W4cgQDLxwwpo1iOTdHBVtQDxlQ9hPMKVlB1KP9KjchxuiLc24wLmCjP3pDMml4LQxOYB34Eq cgPZ3uHvJZG309sb2wTMTWaXobWNI++ZrsRD5GTmuzF3kkx3krtrq6HI5NSaemxK6MTDTjDN Rj/OwTl0yU35eJXuuryB20GFOSUsxiw00I2hMGQ1Cy9L/+IW6Dvotd8O3LmKh2tFArzXaKLx /rZyGNurS/Go5YjHp8wdJOs7Ka2p1U31js24PMWO6hf6hIiY2WRUsnE6xZNhvBTgKOY6u0KT V6hTevFqEw7OAZDCWUoE2Ob2/oHGZCCMW5SLAMgp7eihF0kGf2S2CmpIFYXGb61hAD8SqSY7 Fn7V
Message-ID: <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com>
Date: Fri, 20 Apr 2018 13:07:44 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DKX7aMlnQaKACqE5dikjBEpRQPpYMLXuO"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/662nOvb3dX-p7s0pZhky2ofbpgo>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 19:07:49 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--DKX7aMlnQaKACqE5dikjBEpRQPpYMLXuO
Content-Type: multipart/mixed; boundary="sYNVhnqcYuGHMIxNzV5ID2MpCHjPoAtFk";
 protected-headers="v1"
From: Peter Saint-Andre <stpeter@mozilla.com>
To: mmusic@ietf.org
Message-ID: <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com>
 <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>
In-Reply-To: <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>

--sYNVhnqcYuGHMIxNzV5ID2MpCHjPoAtFk
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 4/20/18 12:37 PM, Roman Shpount wrote:
> Hi All,
>=20
> I do not think ice-options was ever used as a media level attribute.
> Only two ice-options defined in IANA registry
> (https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and =C2=A0rtp=
+ecn,
> which are both session level.
>=20
> Furthermore, RFC 5245 section 15.5
> (https://tools.ietf.org/html/rfc5245#section-15.5,) defined that
> ice-options attribute is session level only. Thus, ice-options should b=
e
> kept session level for backwards compatibility.
>=20
> If something more granular then session is needed, I think it should go=

> into candidate extension attribute, not into media level ice-options.
>=20
> Bottom line, I think ice-options should be a a session level only attri=
bute.

Agreed.

In the Trickle ICE spec, we also limited the `trickle` option to session
level only.

Peter



--sYNVhnqcYuGHMIxNzV5ID2MpCHjPoAtFk--

--DKX7aMlnQaKACqE5dikjBEpRQPpYMLXuO
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENVUj07j078lgnb70ZWGMGH9oFKkFAlraOoAACgkQZWGMGH9o
FKl6ZhAAiqwaCHgrj2AsBVwFWXch08Dwb8ypzGCfH62+Dd/bKQcnS9xhU27N4BqH
GTZTDdkKUJBJu9xo1IeOyCBVl8Owotl6vg0lfpNC9WSzypq8bTMQOgL3uDu/3fS+
+AsY+1asKF2vDHJbg16YL1yE0EH+3NcKXH5s7X5LCRdm/G2rOPXUn344yBhuMXMa
o/eeyrqIKolKrY/q+s3Ch6DXAkur0unFgANNPosAKL0OLKfL1m7OPlVCkO7QOUiN
lNreC+0ff/wBvnZkhGRNTOpY8X2qJj2s0r/0h5dUVCPyY3oI0UthH8IDY5wd2ZSe
dQFqc2rhy32QcaO1kyGdkUnfdhD5XD8iguRB1h4Au/COA48NfpDFNoKlBwPOJEhG
DQsAUAyh5LWqBVHmwptj61s7t4YDMn8i3HY5a8cmmx2C5Oacw+kJwQYPlMo69wLn
JXj3TF3WR33qxXAwRyc+kVwGzPIhGrPm63PeFgEfFYK1FoTFFGv4aE0b1QlJxNdd
O5jJRNWe2E0FDAmGogNsP4a+lvI9eeYFHDZmOu7X3rrMh2DDSGmnxUizFaksfJlV
zXuKYAuPJTzMMsP3G9/95wSUOPVMyUlO5BM8dsR+5fSTwkq8nN6Jg5cY1pub3NEF
lRbJXAjuZ+OBgknKJDjN9USddrJHYgGeXHFLWUsGXlElRKxVUpE=
=277A
-----END PGP SIGNATURE-----

--DKX7aMlnQaKACqE5dikjBEpRQPpYMLXuO--


From nobody Fri Apr 20 13:46:07 2018
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 AD4201200FC for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 13:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01] 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 eJXs_hojjXhm for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 13:46:00 -0700 (PDT)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::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 8B0E812D880 for <mmusic@ietf.org>; Fri, 20 Apr 2018 13:45:55 -0700 (PDT)
Received: by mail-ot0-x232.google.com with SMTP id i5-v6so11030140oth.1 for <mmusic@ietf.org>; Fri, 20 Apr 2018 13:45:55 -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=n4FI1LaYfXP0uYoMlpdsyMgPT0Cjhnzm4OB6aZea+Hc=; b=zqVJyjsN+22z0EDtZo5JW3UhHHshC2ATB/84VIIRq73KhZpXCKXsB2OMM9h1oQrte9 ELT+trEXSmStwKhXb9tRsD5Y1tNyGwNORWZRfxBUkUDMIHbfBzPb3VaUFZFQVW79Am4Q pvshgYXZ4yZFh1tHJNwm8R5ss+RRNivV93KLkPpboYJYp9oBiHmgY8O6qRqg0RRCBXix DcXk3CutlUirJfi/YzaRwiSogBLtnJm8ooyeme30aQ64TmxJ8EHGpY/IXldW/eef32lo 9DTs0knmBE/LV4jx1UkrA1Uj8hcYHkRi3Aza9iz2jw7zkcgKMiMN7hExpARhZsZtSVHZ sAhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n4FI1LaYfXP0uYoMlpdsyMgPT0Cjhnzm4OB6aZea+Hc=; b=KI0z/IJQkZ6yVuNM2GZUEaaLH63l/dZevSX7Ixip0cXKqdXPaeky2nbucZjBAuSm70 g21wUb0bmjqsch8a0dk3HeWxSCjUrYOIcCOQ4bsATQsulLJTAYHUVMexOIpaZjZnn8qM iKO70Jyu0pIkU/VZk+HLp1ww5prmlwy2c9EnwUZeF+uSvKymgM0pgkCv8VQ23XCjh++A OhZYjWKbt2qD0TQpq9zEOUT5tghPAvJU6xneyrlxzoQp247pvzP8khXgQXP0sIhjmxxY zj/kDTaGcZtH5G9QBp8oAmhhMkaEI4/SLY5jUGyc4XrgHf++ft5KTClCmag3ZnT4RhTw /ncw==
X-Gm-Message-State: ALQs6tDi37Iqm2Hiq+om6tKViATpOWYqpqf8jJ9VPVojqBeyVhAhqdcq Br9+B/QgUz2Rq8+bXc66p1LLqSmXZrzhU3CcH3fF/Q==
X-Google-Smtp-Source: AIpwx4+N8rptoK8nYogrnX82g3PWJ+hWsVkhu5/fB5Ds7u8IcwzGFEefNMqxc6RZ5ae00JOokxbbm3WWPJX6FxhNYFo=
X-Received: by 2002:a9d:36dc:: with SMTP id s28-v6mr7282610otd.214.1524257154873;  Fri, 20 Apr 2018 13:45:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.1.39 with HTTP; Fri, 20 Apr 2018 13:45:13 -0700 (PDT)
In-Reply-To: <D6FF62E6.2E737%christer.holmberg@ericsson.com>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se> <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com> <D6FF62E6.2E737%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 20 Apr 2018 13:45:13 -0700
Message-ID: <CABcZeBOwDgK+SScxkGdY4hGx2ecngJmzs5=fxvVG0oJaV6kEiQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>,  "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000434dae056a4dc654"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/GFeYwSPWHUboywgi-_SX2zoSq7A>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 20 Apr 2018 20:46:02 -0000

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

On Fri, Apr 20, 2018 at 12:15 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> >>>> I think this has turned into an argument about style. One usage may
> >>>>be more pleasing to the =C2=B3ear=C2=B2 than the other, but I don=C2=
=B9t see issues
> >>>>of
> >>>> technical correctness or clarity here. As I asked for the the
> >>>>=C2=B3associated with=C2=B2 question, is anyone arguing that the word=
 choice
> >>>>here is likely to cause material implementation errors?
> >>>
> >>> I don't think "address:port" versus "transport" will, but I do think
> >>>"address:port" versus "m=3Dsection" or "transport parameters" will, an=
d
> >>>in fact I identified a material issue around trickle the other day,
> >>>that I haven't seen a response to.
> >>
> >>
> My suggestion was to add text about the special case of port 9 and IP
> address 0.0.0.0.
> >>
> >>
> Because, when you use trickle, the offer may not contain any address
> information at all (you can send an offer without any candidates), so it
> is a special case no matter what.
> >
> > Yes, but the point is that you cannot address the m=3Dsection parameter=
s
> >via address:port, so every piece of text in the document that suggests
> >that you do so needs to be repaired.
> >
> > You don=C2=B9t need to address the parameters via address:port. You wil=
l
> >address the parameters via the BUNDLE-tag.
> >
> > Yes, the answerer picks the BUNDLE address:port =C2=AD which it has to =
do no
> >matter what =C2=AD but what is does is picking an m- line
> > (the m- line containing the address:port selected
>  to be used) and assigns the BUNDLE-tag to it.
> >
> > Yes, but that's not in fact what the text I quoted says, or is implied
> >by much of the rest of the document does.
>
>
> You quoted the text in the following sections (I would be really useful t=
o
> have the section numbers in the review e-mail, btw, because I assume I
> have to address them in a reply):
>

You might find it easier to read the review on Phabricator:

https://mozphab-ietf.devsvcdev.mozaws.net/D3382

> Section 8.1.:
> -------------
>
>    "When an offerer or answerer includes SDP attributes in bundled "m=3D=
=C2=B3
>    sections within a BUNDLE group for which the offerer and answerer
>    BUNDLE addresses:ports have been selected, IDENTICAL and TRANSPORT
>    mux category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are
>    only included in the "m=3D" section indicated by the BUNDLE-tag in the
>    offer or answer."
>
> As I indicated earlier, I DO agree that we don=C2=B9t need to talk about
> address:port here, and it has been removed in the pull request I created.
>
> So, the new text will only talk about the m=3D section:
>
>    "When an offerer or answerer includes SDP attributes in bundled "m=3D=
=C2=B3
>     sections within a BUNDLE group, IDENTICAL and TRANSPORT
>     mux category SDP attributes [I-D.ietf-mmusic-sdp-mux-attributes] are
>     only included in the "m=3D" section indicated by the BUNDLE-tag in th=
e
>     offer or answer.=C2=B2
>

Yes, this seems fine.

>
>
> Section 8.3.:
> -------------
>
>     "If the answer contains a BUNDLE group, the answerer MUST:
>
>      o  Select an offerer BUNDLE address:port [Section 8.3.1]; and
>
>      o  Select an answerer BUNDLE address:port [Section 8.3.2].=C2=B2
>
>
>
> Regarding the offerer BUNDLE address:port, the functional task performed
> by the answerer IS selecting the offerer address:port. Section 8.3.1
> describes the detailed SDP procedures for that, and it does talk the m=3D
> section.
>
> Regarding the answerer BUNDLE address:port, I don=C2=B9t think we can cha=
nge
> anything there, because the task performed by the answerer IS selecting
> the answerer address:port. AFTER that it will assign the address:port to
> an m=3D section in the answer, as described in Section 8.3.2.
>

I don't see how you get that. The task is to select the m=3D section to use
as the lead m=3D section and then use its parameters, which include the
address:port. Again, if things were as you say, then trickle wouldn't make
sense.

>
>
> So, while we for sure could say something like =C2=B3Select an offerer
> tagged/head m=3D section=C2=B2, the procedures would still describe the s=
election
> of the offerer BUNDLE address:port.
>
>
>
>
> Section 8.3.1:
> --------------
>
>     "If all of the criteria above are fulfilled, the answerer MUST select
> the suggested offerer BUNDLE address:port.=C2=B2
>
> In the beginning of the section, the text DOES talk about m=3D section, b=
ut
> the specific text above IS about the answerer selecting the offerer BUNDL=
E
> address:port, i.e., the address:port that the offerer is going to use.
>

Right, but then it totally omits the text about the *other* parameters,
which
are equally important. Where does this document tell me to use the
ICE candidates from that m=3D section.

Section 8.4:
> ------------
>
>
>     "When an offerer receives an answer, if the answer contains a BUNDLE
>      group, the offerer MUST check that any bundled "m=3D" section in the
>      answer was indicated as bundled in the corresponding offer.  If ther=
e
>      is no mismatch, the offerer MUST use the offerer BUNDLE address:port=
,
>      selected by the answerer [Section 8.3.1], as the address for each
>      bundled "m=3D" section.=C2=B2
>
>
> This text talks about the offerer determining what address:port it will
> use.
>

Yes, My point is that the emphasis on this is wrong.


>
Now, I do agree that we could modify this text by saying that the offerer
> picks the tagged m=3D section, and then picks the address:port (and other
> parameters) from that m=3D section.
>

Yes, that's what the test needs to say.


>
>
> Section 11:
> -----------
>
>
>      "In an offer, if the offer assigns a unique address:port to one or
>       more bundled "m=3D" sections (excluding any bundle-only "m=3D"
>       sections), the offerer MUST include ICE-related media-level
>       attributes in each of those "m=3D" sections.  If the offerer assign=
s
>       an offerer BUNDLE address:port (previously selected
>       [Section 8.3.1] or newly suggested [Section 8.5.1]) to a bundled
>       "m=3D" section (the "m=3D" section indicated by the offerer BUNDLE-
>       tag), the offerer only includes ICE-related media-level SDP
>       attributes in that "m=3D" section, following the procedures in
>       Section 8.1.=C2=B2
>
>
> Similar to section 8.1, I DO agree that we can remove the text about
> address:port here, and talk about including ICE attributes in bundled m=
=3D
> sections.
>
>
> Section 11.1.:
> --------------
>
> The first paragraph talks about assigning a unique address:port (i.e.,
> before the BUNDLE group has been negotiated), so I am not sure we can
> modify that. Or, perhaps we could talk about assigning attributes to m=3D
> sections before a BUNDLE group has been negotiated.
>

Or something.

m=3D sections can exist in a variety of states (proposed bundled, proposed
bundle
lead, bundle-only, etc.) and each of those has various properties and
requirements,
which include, but are not limited to address.


> When writing the comments above, I think one of the reasons we talk about
> address:port is because previously I think the draft talked about =C2=B3B=
UNDLE
> group=C2=B2 even before it had been negotiated - so we had to distinguish
> between the cases where the BUNDLE addresses:ports had been selected and
> where they had not (initial offer). Currently, a BUNDLE group does not
> exist until it has been negotiated, so the m=3D sections within a BUNDLE
> group will ALWAYS contain the BUNDLE address:port (or bundle-only plus
> port zero).


Or, again, 9...

-Ekr

So, while the procedures were clarified, some parts may have
> become redundant.
>
>
>
> Regards,
>
> Christer
>
>
>
>
>
>
>
>
>
>
>
>

--000000000000434dae056a4dc654
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 Fri, Apr 20, 2018 at 12:15 AM, 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 class=3D"gmail-HOEnZb"><div class=3D"gmail-=
h5">Hi,<br>
<br>
&gt;&gt;&gt;&gt; I think this has turned into an argument about style. One =
usage may<br>
&gt;&gt;&gt;&gt;be more pleasing to the =C2=B3ear=C2=B2 than the other, but=
 I don=C2=B9t see issues<br>
&gt;&gt;&gt;&gt;of <br>
&gt;&gt;&gt;&gt; technical correctness or clarity here. As I asked for the =
the<br>
&gt;&gt;&gt;&gt;=C2=B3associated with=C2=B2 question, is anyone arguing tha=
t the word choice<br>
&gt;&gt;&gt;&gt;here is likely to cause material implementation errors?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don&#39;t think &quot;address:port&quot; versus &quot;transp=
ort&quot; will, but I do think<br>
&gt;&gt;&gt;&quot;address:port&quot; versus &quot;m=3Dsection&quot; or &quo=
t;transport parameters&quot; will, and<br>
&gt;&gt;&gt;in fact I identified a material issue around trickle the other =
day,<br>
&gt;&gt;&gt;that I haven&#39;t seen a response to.<br>
&gt;&gt;<br>
&gt;&gt;<br>
My suggestion was to add text about the special case of port 9 and IP<br>
address 0.0.0.0.<br>
&gt;&gt;<br>
&gt;&gt;<br>
Because, when you use trickle, the offer may not contain any address<br>
information at all (you can send an offer without any candidates), so it<br=
>
is a special case no matter what.<br>
&gt;<br>
&gt; Yes, but the point is that you cannot address the m=3Dsection paramete=
rs<br>
&gt;via address:port, so every piece of text in the document that suggests<=
br>
&gt;that you do so needs to be repaired.<br>
&gt;<br>
&gt; You don=C2=B9t need to address the parameters via address:port. You wi=
ll<br>
&gt;address the parameters via the BUNDLE-tag.<br>
&gt;<br>
&gt; Yes, the answerer picks the BUNDLE address:port =C2=AD which it has to=
 do no<br>
&gt;matter what =C2=AD but what is does is picking an m- line<br>
&gt; (the m- line containing the address:port selected<br>
=C2=A0to be used) and assigns the BUNDLE-tag to it.<br>
&gt;<br>
&gt; Yes, but that&#39;s not in fact what the text I quoted says, or is imp=
lied<br>
&gt;by much of the rest of the document does.<br>
<br>
<br>
</div></div>You quoted the text in the following sections (I would be reall=
y useful to<br>
have the section numbers in the review e-mail, btw, because I assume I<br>
have to address them in a reply):<br></blockquote><div><br></div><div>You m=
ight find it easier to read the review on Phabricator:</div><div><br></div>=
<div><a href=3D"https://mozphab-ietf.devsvcdev.mozaws.net/D3382">https://mo=
zphab-ietf.devsvcdev.mozaws.net/D3382</a><br></div><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">
Section 8.1.:<br>
-------------<br>
<br>
=C2=A0 =C2=A0&quot;When an offerer or answerer includes SDP attributes in b=
undled &quot;m=3D=C2=B3<br>
=C2=A0 =C2=A0sections within a BUNDLE group for which the offerer and answe=
rer<br>
=C2=A0 =C2=A0BUNDLE addresses:ports have been selected, IDENTICAL and TRANS=
PORT<br>
=C2=A0 =C2=A0mux category SDP attributes [I-D.ietf-mmusic-sdp-mux-<wbr>attr=
ibutes] are<br>
=C2=A0 =C2=A0only included in the &quot;m=3D&quot; section indicated by the=
 BUNDLE-tag in the<br>
=C2=A0 =C2=A0offer or answer.&quot;<br>
<br>
As I indicated earlier, I DO agree that we don=C2=B9t need to talk about<br=
>
address:port here, and it has been removed in the pull request I created.<b=
r>
<br>
So, the new text will only talk about the m=3D section:<br>
<br>
=C2=A0 =C2=A0&quot;When an offerer or answerer includes SDP attributes in b=
undled &quot;m=3D=C2=B3<br>
=C2=A0 =C2=A0 sections within a BUNDLE group, IDENTICAL and TRANSPORT<br>
=C2=A0 =C2=A0 mux category SDP attributes [I-D.ietf-mmusic-sdp-mux-<wbr>att=
ributes] are<br>
=C2=A0 =C2=A0 only included in the &quot;m=3D&quot; section indicated by th=
e BUNDLE-tag in the<br>
=C2=A0 =C2=A0 offer or answer.=C2=B2<br></blockquote><div><br></div><div>Ye=
s, this seems fine. <br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
<br>
<br>
Section 8.3.:<br>
-------------<br>
<br>
=C2=A0 =C2=A0 &quot;If the answer contains a BUNDLE group, the answerer MUS=
T:<br>
<br>
=C2=A0 =C2=A0 =C2=A0o=C2=A0 Select an offerer BUNDLE address:port [Section =
8.3.1]; and<br>
<br>
=C2=A0 =C2=A0 =C2=A0o=C2=A0 Select an answerer BUNDLE address:port [Section=
 8.3.2].=C2=B2<br>
<br>
<br>
<br>
Regarding the offerer BUNDLE address:port, the functional task performed<br=
>
by the answerer IS selecting the offerer address:port. Section 8.3.1<br>
describes the detailed SDP procedures for that, and it does talk the m=3D<b=
r>
section.<br>
<br>
Regarding the answerer BUNDLE address:port, I don=C2=B9t think we can chang=
e<br>
anything there, because the task performed by the answerer IS selecting<br>
the answerer address:port. AFTER that it will assign the address:port to<br=
>
an m=3D section in the answer, as described in Section 8.3.2.<br></blockquo=
te><div><br></div><div>I don&#39;t see how you get that. The task is to sel=
ect the m=3D section to use</div><div>as the lead m=3D section and then use=
 its parameters, which include the</div><div>address:port. Again, if things=
 were as you say, then trickle wouldn&#39;t make <br></div><div>sense.<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
So, while we for sure could say something like =C2=B3Select an offerer<br>
tagged/head m=3D section=C2=B2, the procedures would still describe the sel=
ection<br>
of the offerer BUNDLE address:port.<br>
<br>
<br>
<br>
<br>
Section 8.3.1:<br>
--------------<br>
<br>
=C2=A0 =C2=A0 &quot;If all of the criteria above are fulfilled, the answere=
r MUST select<br>
the suggested offerer BUNDLE address:port.=C2=B2<br>
<br>
In the beginning of the section, the text DOES talk about m=3D section, but=
<br>
the specific text above IS about the answerer selecting the offerer BUNDLE<=
br>
address:port, i.e., the address:port that the offerer is going to use.<br><=
/blockquote><div><br></div><div>Right, but then it totally omits the text a=
bout the *other* parameters, which</div><div>are equally important. Where d=
oes this document tell me to use the</div><div>ICE candidates from that m=
=3D section.<br></div><div><br></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">
Section 8.4:<br>
------------<br>
<br>
<br>
=C2=A0 =C2=A0 &quot;When an offerer receives an answer, if the answer conta=
ins a BUNDLE<br>
=C2=A0 =C2=A0 =C2=A0group, the offerer MUST check that any bundled &quot;m=
=3D&quot; section in the<br>
=C2=A0 =C2=A0 =C2=A0answer was indicated as bundled in the corresponding of=
fer.=C2=A0 If there<br>
=C2=A0 =C2=A0 =C2=A0is no mismatch, the offerer MUST use the offerer BUNDLE=
 address:port,<br>
=C2=A0 =C2=A0 =C2=A0selected by the answerer [Section 8.3.1], as the addres=
s for each<br>
=C2=A0 =C2=A0 =C2=A0bundled &quot;m=3D&quot; section.=C2=B2<br>
<br>
<br>
This text talks about the offerer determining what address:port it will<br>
use. <br></blockquote><div><br></div><div>Yes, My point is that the emphasi=
s on this is wrong.</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);pa=
dding-left:1ex">=C2=A0<br></blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">
Now, I do agree that we could modify this text by saying that the offerer<b=
r>
picks the tagged m=3D section, and then picks the address:port (and other<b=
r>
parameters) from that m=3D section.<br></blockquote><div><br></div><div>Yes=
, that&#39;s what the test needs to say.</div><div> <br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
<br>
<br>
<br>
Section 11:<br>
-----------<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0&quot;In an offer, if the offer assigns a unique addres=
s:port to one or<br>
=C2=A0 =C2=A0 =C2=A0 more bundled &quot;m=3D&quot; sections (excluding any =
bundle-only &quot;m=3D&quot;<br>
=C2=A0 =C2=A0 =C2=A0 sections), the offerer MUST include ICE-related media-=
level<br>
=C2=A0 =C2=A0 =C2=A0 attributes in each of those &quot;m=3D&quot; sections.=
=C2=A0 If the offerer assigns<br>
=C2=A0 =C2=A0 =C2=A0 an offerer BUNDLE address:port (previously selected<br=
>
=C2=A0 =C2=A0 =C2=A0 [Section 8.3.1] or newly suggested [Section 8.5.1]) to=
 a bundled<br>
=C2=A0 =C2=A0 =C2=A0 &quot;m=3D&quot; section (the &quot;m=3D&quot; section=
 indicated by the offerer BUNDLE-<br>
=C2=A0 =C2=A0 =C2=A0 tag), the offerer only includes ICE-related media-leve=
l SDP<br>
=C2=A0 =C2=A0 =C2=A0 attributes in that &quot;m=3D&quot; section, following=
 the procedures in<br>
=C2=A0 =C2=A0 =C2=A0 Section 8.1.=C2=B2<br>
<br>
<br>
Similar to section 8.1, I DO agree that we can remove the text about<br>
address:port here, and talk about including ICE attributes in bundled m=3D<=
br>
sections.<br>
<br>
<br>
Section 11.1.:<br>
--------------<br>
<br>
The first paragraph talks about assigning a unique address:port (i.e.,<br>
before the BUNDLE group has been negotiated), so I am not sure we can<br>
modify that. Or, perhaps we could talk about assigning attributes to m=3D<b=
r>
sections before a BUNDLE group has been negotiated.<br></blockquote><div><b=
r></div><div>Or something.</div><div><br></div><div>m=3D sections can exist=
 in a variety of states (proposed bundled, proposed bundle</div><div>lead, =
bundle-only, etc.) and each of those has various properties and requirement=
s,</div><div>which include, but are not limited to address.<br></div><div><=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
When writing the comments above, I think one of the reasons we talk about<b=
r>
address:port is because previously I think the draft talked about =C2=B3BUN=
DLE<br>
group=C2=B2 even before it had been negotiated - so we had to distinguish<b=
r>
between the cases where the BUNDLE addresses:ports had been selected and<br=
>
where they had not (initial offer). Currently, a BUNDLE group does not<br>
exist until it has been negotiated, so the m=3D sections within a BUNDLE<br=
>
group will ALWAYS contain the BUNDLE address:port (or bundle-only plus<br>
port zero). </blockquote><div><br></div><div>Or, again, 9...</div><div><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 rgb(204,204,204);padding=
-left:1ex">So, while the procedures were clarified, some parts may have<br>
become redundant.<br>
<br>
<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>

--000000000000434dae056a4dc654--


From nobody Fri Apr 20 23:09:21 2018
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 0F67B127871 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 23:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEAfbmCsOcc1 for <mmusic@ietfa.amsl.com>; Fri, 20 Apr 2018 23:09:18 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::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 E2AA5127867 for <mmusic@ietf.org>; Fri, 20 Apr 2018 23:09:17 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id q26so7070414uab.0 for <mmusic@ietf.org>; Fri, 20 Apr 2018 23:09:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8cb6kC98fUw4LTr07PjJSoEQ7e5UmluAstkKGEqqn7U=; b=l4JamEM4lp70l33qq3234TW3Jl3K43IIKsQy8bd8+nKjKboF23R/Kf3Rzi38MqsgUt hzKBHjh8wmBnrXSSuNZ7654Dl2Z9d34yLSE/XKuvmL4xXpOGfJiaEbEveyzs++JrUZy6 Zv55NWvsKv2hrhEtEFdFblcMVEhDT+b3Dfdp1UWSEigVpBR/5xrkbXVZ4ayebDmJJaa2 C672bwHHoKK850gcPTrQzcu3595C8f7ajPP1GOJFXOYHITyKW29XP6ajiayvdDXSEpyp U1exkmnV1W7w3GORV3GBmu9WDEDU9ScJp12AvH0YALJCmxv59zyxOqPFGn0sJpiUbpst GCLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8cb6kC98fUw4LTr07PjJSoEQ7e5UmluAstkKGEqqn7U=; b=MEADBKdLWWJYofHxNy26hDa+MWnrPdQEk/4iSCyRGgxyUVNQsSP3Pb+D83jKPFs8rs mOhNBQqMS00zIrW+vApQwjCwNIU8/ENkswk1v0VYS5ZSb6hkKwEiKou8ISt06IZV3SBF ZLftbLVspimtcMDACabLVAMxSW2AsaVqt0OJpjF15KuxXnqxA3A5kFxXXOewl6nlAYCE sIakAZ5X1OwCs7I03OnOJjRZwdUBiepA8A4zxbtAfC9SDTHE0MP0bWEsE+dUnq6EOZ0T wro4ikxdgZ+aq3bQCouENFXGldUt5vZr+E2nsfaDzcCbe+G5hHEAeO1HH5yyP7tkiIBt 3aqg==
X-Gm-Message-State: ALQs6tCZ2tjqrXsV4QwB+bIsEo7YgZ2LYPuWlo6r0vnJhZDDM9rA5ybE hUjhnP40RNuV2cvJUZkUn5nh+RNgUZI7Nf/t81E=
X-Google-Smtp-Source: AIpwx48EX2Het29P0GhZVlCS8K3OdlcQ35RgCzezxQRjzuzVK59lclpk+LkEMXJK4Mnhaux8jC0mBIFbhrY6lF8EqDo=
X-Received: by 10.176.20.143 with SMTP id d15mr10023143uae.10.1524290957035; Fri, 20 Apr 2018 23:09:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Fri, 20 Apr 2018 23:09:16 -0700 (PDT)
In-Reply-To: <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com>
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com> <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com> <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Fri, 20 Apr 2018 23:09:16 -0700
Message-ID: <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com>
To: Peter Saint-Andre <stpeter@mozilla.com>
Cc: mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>
Content-Type: multipart/alternative; boundary="001a114542880750d2056a55a5a7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P_Ysb0EqTWgSLee_Yl0hM_dfbuk>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 21 Apr 2018 06:09:20 -0000

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

I am fine with considering ice-options has session level too. I wonder if
Marc can chime in on considering it as  media level in the ice-sip-sdp.

On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre <stpeter@mozilla.com>
wrote:

> On 4/20/18 12:37 PM, Roman Shpount wrote:
> > Hi All,
> >
> > I do not think ice-options was ever used as a media level attribute.
> > Only two ice-options defined in IANA registry
> > (https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and  rtp+ecn,
> > which are both session level.
> >
> > Furthermore, RFC 5245 section 15.5
> > (https://tools.ietf.org/html/rfc5245#section-15.5,) defined that
> > ice-options attribute is session level only. Thus, ice-options should be
> > kept session level for backwards compatibility.
> >
> > If something more granular then session is needed, I think it should go
> > into candidate extension attribute, not into media level ice-options.
> >
> > Bottom line, I think ice-options should be a a session level only
> attribute.
>
> Agreed.
>
> In the Trickle ICE spec, we also limited the `trickle` option to session
> level only.
>
> Peter
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr">I am fine with considering ice-options has session level t=
oo. I wonder if Marc can chime in on considering it as=C2=A0 media level in=
 the ice-sip-sdp.=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre <span dir=
=3D"ltr">&lt;<a href=3D"mailto:stpeter@mozilla.com" target=3D"_blank">stpet=
er@mozilla.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><spa=
n class=3D"">On 4/20/18 12:37 PM, Roman Shpount wrote:<br>
&gt; Hi All,<br>
&gt; <br>
&gt; I do not think ice-options was ever used as a media level attribute.<b=
r>
&gt; Only two ice-options defined in IANA registry<br>
&gt; (<a href=3D"https://www.iana.org/assignments/ice/ice.xhtml" rel=3D"nor=
eferrer" target=3D"_blank">https://www.iana.org/<wbr>assignments/ice/ice.xh=
tml</a>) are ice2 and =C2=A0rtp+ecn,<br>
&gt; which are both session level.<br>
&gt; <br>
&gt; Furthermore, RFC 5245 section 15.5<br>
&gt; (<a href=3D"https://tools.ietf.org/html/rfc5245#section-15.5," rel=3D"=
noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc5245#sect=
ion-15.5,</a>) defined that<br>
&gt; ice-options attribute is session level only. Thus, ice-options should =
be<br>
&gt; kept session level for backwards compatibility.<br>
&gt; <br>
&gt; If something more granular then session is needed, I think it should g=
o<br>
&gt; into candidate extension attribute, not into media level ice-options.<=
br>
&gt; <br>
&gt; Bottom line, I think ice-options should be a a session level only attr=
ibute.<br>
<br>
</span>Agreed.<br>
<br>
In the Trickle ICE spec, we also limited the `trickle` option to session<br=
>
level only.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Peter<br>
<br>
<br>
</font></span><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>

--001a114542880750d2056a55a5a7--


From nobody Sat Apr 21 08:27:00 2018
Return-Path: <linuxwolf+ietf@outer-planes.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 65C861274D2; Sat, 21 Apr 2018 08:26:53 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-mmusic-sdp-simulcast.all@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.78.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152432441334.20552.1917131199687495570@ietfa.amsl.com>
Date: Sat, 21 Apr 2018 08:26:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VQjyu8tV_A2ECggO_lWgnLCZ2mc>
Subject: [MMUSIC] Genart last call review of draft-ietf-mmusic-sdp-simulcast-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 21 Apr 2018 15:26:53 -0000

Reviewer: Matthew Miller
Review result: Ready

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

For more information, please see the FAQ at

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

Document: draft-ietf-mmusic-sdp-simulcast-12
Reviewer: Matthew A. Miller
Review Date: 2018-04-21
IETF LC End Date: 2018-04-24
IESG Telechat date: N/A

Summary:  This document is ready to be published as a Standards
Track document.

Major issues: NONE

Minor issues: NONE

Nits/editorial comments: NONE



From nobody Sun Apr 22 05:25:38 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A239D126BFD for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 05:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QMojkQXJAk9u for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 05:25:35 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 068B31204DA for <mmusic@ietf.org>; Sun, 22 Apr 2018 05:25:35 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 5E8DA9290F60E; Sun, 22 Apr 2018 13:25:30 +0100 (IST)
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.382.0; Sun, 22 Apr 2018 13:25:31 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0361.001; Sun, 22 Apr 2018 20:25:25 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Bo Burman <bo.burman@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
Thread-Index: AQHT2jT95+LEqgEgvEGVklWf8voyQA==
Date: Sun, 22 Apr 2018 12:25:25 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD87537A@DGGEMM506-MBX.china.huawei.com>
References: <6E58094ECC8D8344914996DAD28F1CCD870EA5@DGGEMM506-MBX.china.huawei.com> <DB5PR07MB107811003A4497F734FA69BD8DBA0@DB5PR07MB1078.eurprd07.prod.outlook.com> <D6FF8C39.2E810%christer.holmberg@ericsson.com>
In-Reply-To: <D6FF8C39.2E810%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.72]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5Tp95y0WsqGzrGfR7OOMYc5rhQc>
Subject: Re: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 12:25:38 -0000

Hi Christer,
Thanks for the review, see inline
Roni

-----Original Message-----
From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]=20
Sent: Friday, April 20, 2018 12:54 PM
To: Bo Burman; Roni Even (A); mmusic@ietf.org
Subject: Re: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg=
-17

Hi,

I have reviewed the new version. Thank you for addressing my comments.

However, I think there is still some work (mostly editorial) to do.


SECTION 1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q1:

I think the Introduction is rather messy, but I don=B9t have a suggestion o=
n how to fix it. However, there is the following statement:
   "This document defines SDP offer/answer [RFC3264] negotiation
   procedures to establish data channels for transport of well-defined
   subprotocols, to enable out-of-band negotiation.=B2

 I suggest to say=20

   "This document defines SDP offer/answer [RFC3264]
   Procedures that enable out-of-band negotiation for establishing data cha=
nnels for transport of well-defined
   subprotocols.=B2=20

[RE] OK

---

Q2:

I suggest to remove the following:

   =B3In the future, data channels could be defined over other SCTP based
   protocols, such as SCTP over IP.  However, corresponding potential
   other "m=3D" line proto values are not considered in this document."

It is enough to specify what the draft does - not what may potentially perh=
aps be done in future.

[RE] OK

---

Q3:

Please add references to MSRP and BFCP on first occurrence.

[RE] OK



SECTION 5:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q4:

The 3rd paragraph repeats much of the 1st paragraph. I think they can be co=
mbined.

[RE} OK


Q5:

There is no need to repeat text about =B3without the usage of DCEP=B2. It i=
s enough to make it clear once in the beginning of document. This applies t=
o other sections too.

[RE} left it here and remove from next section



SECTION 5.1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


Q6:

The text talks about =B3The intention of the attribute is to blah blah=B2.
That sounds weird. Instead say =B3The attribute is used to blah blah=B2.
[RE}OK



SECTION 5.1.9:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q7:

I think you can remove the first paragraph. Simply include the [I-D.ietf-mm=
usic-sdp-mux-attributes] reference in the next sentence:

   "The multiplexing category [I-D.ietf-mmusic-sdp-mux-attributes] of the "=
a=3Ddcmap:" attribute is SPECIAL."

[RE]OK



SECTIONS 6.3 & 6.4:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q8:

You don=B9t have to say =B3Sends the offer=B2/=B3Sends the answer=B2.

[RE] OK



SECTION 6.6:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q9:

The text seems to be about adding a new data channel. You should have a sep=
arate sub-section (6.6.x) for that.

But, you should also have text about when sending a subsequent offer withou=
t impacting the data channel. For example, the offer must (I assume) includ=
e all attributes associated with the currently open data channels.

[RE} Will see how to do it



SECTION 6.6.1:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q10:

The text says:

   "When the application requests the closing of a data channel that was
    negotiated via SDP offer/answer, the data channel stack always
    performs an SCTP SSN reset for this channel.=B2


However, it later says that a data channel is closed once the offer send in=
 order to close the data channel has been accepted.

[RE] I looked at it and will change the text also for Q11

Q11:

The text says:

   "If a client receives a data channel close indication (due to inband
    SCTP SSN reset or some other reason) without associated SDP offer
    then the client SHOULD generate an SDP offer which excludes this
    closed data channel.=B2


But, earlier in the section it says that it is subprotocol-specific whether=
 a O/A exchange is needed in order to close a data channel.



SECTION 6.7:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Q12:

I think most of the text (apart from the error cases) could be incorporated=
 into the earlier offer/answer sections.

For example, the offer section should make it clear when "a=3Ddcmap:" is in=
cluded in an offer, and when it is not. There is no need for a separate sec=
tion to describe the case when "SDP offer has no "a=3Ddcmap:=B2 attributes"=
.

[RE} I am not sure, I can move the cases like for example  no a=3Ddcmap in =
intial offer to section 6.3 but I think these cases are not the usual ones =
since 6.3 creates the "normal" offer and it reads better at least to me thi=
s way. Anyhow if you feel this is important I will move parts of section 6.=
7 to earlier sections



Regards,

Christer




From:  mmusic <mmusic-bounces@ietf.org> on behalf of Bo Burman <bo.burman@e=
ricsson.com>
Date:  Friday 6 April 2018 at 18:17
To:  "Roni Even (A)" <roni.even@huawei.com>, "mmusic@ietf.org"
<mmusic@ietf.org>
Subject:  Re: [MMUSIC] new revision in
draft-ietf-mmusic-data-channel-sdpneg-17


Thanks Roni,
=20
I believe this addresses my shepherd=B9s review nits.
=20
/Bo
=20
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Roni Even (A)
Sent: den 4 april 2018 14:34
To: mmusic@ietf.org
Subject: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17


=20
Hi,
I submitted a new revision of
https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-17
trying to address comments from Christer and Bo.
Thanks
Roni Even


From nobody Sun Apr 22 07:36:33 2018
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 E72031201F2; Sun, 22 Apr 2018 07:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 1YkpAGAxHHHl; Sun, 22 Apr 2018 07:36:24 -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 124221200A0; Sun, 22 Apr 2018 07:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2732; q=dns/txt; s=iport; t=1524407784; x=1525617384; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=wHEe1exj27A4bq7zqLqmXe242oNZERfahcqNiwHr4bY=; b=IbMfe8Z740PJgdBFjTJmWPCubbqFQrtK+IOZru/3xKsMaUkOonn7Lml6 r0k+pruXfy8TacCDqV3b7UPaLkokB7Nat8CEwXNpWeNhetEalS22sHBL4 ptn4RVMZvfXgV30P1VSDE2cGIfdbMcDkjS3S49gNL3WwV4QCwRb/PfUmw c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C2AgB8ndxa/5FdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDgVuEEpR4gUspgQ+UeAuEawKCRSE3FQECAQEBAQEBAmw?= =?us-ascii?q?ohSMBBSMPAQVBEAsYAgIfBwICVwYBDAgBAYR+DacXghyEWINmgi6BCYcDgVQ?= =?us-ascii?q?/gTKCaIdzglQCl3MIjjoGh0qFBJAtgSUyIoFSTSMVgn+CR44iI5B9AQE?=
X-IronPort-AV: E=Sophos;i="5.49,312,1520899200"; d="scan'208";a="388033738"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Apr 2018 14:36:22 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w3MEaLIG015622; Sun, 22 Apr 2018 14:36:22 GMT
To: Christer Holmberg <christer.holmberg@ericsson.com>, Eric Rescorla <ekr@rtfm.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <9d453c11-d225-422e-ad8d-2e8ce9d90fb1@cisco.com>
Date: Sun, 22 Apr 2018 10:36:21 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/-2kNKq8K8rYgv8Td8URKQtu91Ow>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 14:36:26 -0000

On 4/18/18 2:29 PM, Christer Holmberg wrote:
> Hi,
>
>>>>>>> o  Bundled media: All media associated with a given BUNDLE group.
>>>>>>>     
>>>>>>> o  Initial offer: The first offer, within an SDP session (e.g. a
>>>>>>>       SIP dialog when the Session Initiation Protocol (SIP) [RFC3261] is
>>>>>>>       used to carry SDP), in which the offerer indicates that it wants
>>>>>>>       to create a given BUNDLE group.
>>>>>> This is a very idiosyncratic definition, because it's *not* the first
>>>>>> offer in the session, but the one where the BUNDLE group is
>>>>>> introduced. Given that 3264 has a different meaning for this same
>>>>>> term, and the difference is critical, I would strongly urge you to
>>>>>> pick a different term.
>>>>> I believe there are other drafts with similar definitions of "Initial Offer".
>>>>>
>>>> Perhaps, but as I noted, 3264s disagrees.
>>>>
>>>> Anyway, would something like "Initial BUNDLE offer" be better?
>>>>
>>>> Not really.
>>>>
>>>>> So, what do you suggest?
>>>>> Note that, for most SDP extensions I can think of, "initial offer" refers to the offer where you actually start using the extension (explicitly or implicitly).
>>>>> But that's not the case here, because this is the one for this BUNDLE group, not for BUNDLE as a whole
>>>> I'm not sure you need a specific term here. How often do you use it?
>>> It’s based on the generic structure that MMUSIC has defined for the O/A procedures of new attributes:
>>>
>>> • Generating initial offer
>>> • Generating answer
>>> • Modifying the session
>>>   
>>> Sure, we could use a structure like:
>>>
>>> • Creating BUNDLE group
>>>     o Generating offer
>>>     o Generating answer
>>> • Modifying BUNDLE group
>>>     o Generating offer
>>>          • Add/remove m- section etc
>>>     o Generating answer
>>>          • Add/remove m- section etc
>>>
>>> …where the focus would be on whether a bundle group is created or modified, without caring about
>>> whether it’s the initial offer of the session or not.
>>>
>>> But, we would not be using the generic O/A structure.
>> I'm not seeing a problem with that
> I think some do, e.g., the chairs.
>
> I have personally also been strict about it when reviewing documents written by others, but I have no problem allowing other structures if seen more appropriate - if everyone is ok with it.

Agreed. We have been using this structure and consistently asked authors 
to use it as well for a long time. It's an established MMUSIC practice 
in dealing with offer/answer procedures and I'm not in favor of changing 
this.

Thanks

-- Flemming (with both my individual and chair hat on).







From nobody Sun Apr 22 07:41:57 2018
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 1B9EA120454; Sun, 22 Apr 2018 07:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 aulZfB6aUYxN; Sun, 22 Apr 2018 07:41:53 -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 EF8EC1200A0; Sun, 22 Apr 2018 07:41:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4852; q=dns/txt; s=iport; t=1524408113; x=1525617713; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=5Gdy8DceKYu9KyXZSgnNM+gglhnH71OtY41pgX86PBo=; b=LOvMvt7uPOyWju8WaXECAPp+w5xUIVrMnqDvaMLycjITytI2qSWvAMVI TlY19GUSFIPn9Pu4m/l3TC8pSgEDWKlFQwVe2LqVYg9I4z1rxRT9poL8n CqUtYnQTIEL2lClQGzb9bshkZUD7uHfFMEYUw1tNhYInjjOq0XCmsrGBJ 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AjAwDyndxa/5hdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDeGMog2qUeIFLCCGBD44ShmYLhGsCgkUhNxUBAgEBAQE?= =?us-ascii?q?BAQJsKIUiAQEBAQIBI1YFCwsEFCMEAwICRhEGAQwGAgEBhH4FCKcWghwfhDm?= =?us-ascii?q?DZoIuiAyBVD+BMgyCXIdzglQCl3MIjjoGh0qFBJAtgSUyIoFSTSMVgn6CIBc?= =?us-ascii?q?RjiIjMJBNAQE?=
X-IronPort-AV: E=Sophos;i="5.49,312,1520899200";  d="scan'208,217";a="384820065"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Apr 2018 14:41:52 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w3MEfp4o029078; Sun, 22 Apr 2018 14:41:51 GMT
To: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <CABcZeBNke+CcxuV4H8PUHavaeoMRP9nop6aOdgr6UwvFy3bzOw@mail.gmail.com> <A8A3827C-D8AD-4DAE-BE81-2D577F8B4EBD@nostrum.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <4748450e-2434-11f9-215f-944c8b3bd4b7@cisco.com>
Date: Sun, 22 Apr 2018 10:41:51 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <A8A3827C-D8AD-4DAE-BE81-2D577F8B4EBD@nostrum.com>
Content-Type: multipart/alternative; boundary="------------9BB432A59BEFA6DD53517269"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/o-9wq2gle9ckxLLzWzdX8YXF6K8>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 14:41:55 -0000

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



On 4/19/18 5:28 AM, Ben Campbell wrote:
>
>
> On Apr 18, 2018, at 9:22 PM, Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>> wrote:
>
>>     How is "applies" more specific than "associated"?
>>
>>
>> The answer to both of these is the same. You are using the word 
>> associated for a number of different things, and so having different 
>> terms is clearer.
>>
>>
>>     I get that you don't like the use of the word "associated". But,
>>     in general, coming up with a bunch of different words just to get
>>     rid of "associated" doesn't make sense to me. It's a pure
>>     editorial choice, and every author has his/her favourite
>>     preference, and I think having consistent terminology is more
>>     important than finding the best word.
>>
>>
>> It's not a pure editorial choice. It's a source of confusion to have 
>> an overloaded term.
>
> I think it is an editorial choice. Furthermore, I think it’s a 
> question of style, in which the authors have a fair amount of 
> latitude. Does anyone think that the choice is going to cause 
> implementors to make material errors?
>
I don't. I will also note that the document has undergone numerous 
revisions with significant terminology rewrite on multiple occasions to 
try and satisfy diverse comments from a significant number of people. 
The terminology that is found in the document represents a compromise 
that the WG participants have consensus on.

Thanks

-- Flemming (with chair and individual hat on)


> Ben.


--------------9BB432A59BEFA6DD53517269
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/19/18 5:28 AM, Ben Campbell wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:A8A3827C-D8AD-4DAE-BE81-2D577F8B4EBD@nostrum.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div><br>
      </div>
      <div><br>
        On Apr 18, 2018, at 9:22 PM, Eric Rescorla &lt;<a
          href="mailto:ekr@rtfm.com" moz-do-not-send="true">ekr@rtfm.com</a>&gt;
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">How is
            "applies" more specific than "associated"?<br>
          </blockquote>
          <div><br>
          </div>
          <div>The answer to both of these is the same. You are using
            the word associated for a number of different things, and so
            having different terms is clearer.</div>
          <div><br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            I get that you don't like the use of the word "associated".
            But, in general, coming up with a bunch of different words
            just to get rid of "associated" doesn't make sense to me.
            It's a pure editorial choice, and every author has his/her
            favourite preference, and I think having consistent
            terminology is more important than finding the best word.<br>
          </blockquote>
          <div><br>
          </div>
          <div>It's not a pure editorial choice. It's a source of
            confusion to have an overloaded term.</div>
        </div>
      </blockquote>
      <br>
      <div>I think it is an editorial choice. Furthermore, I think it’s
        a question of style, in which the authors have a fair amount of
        latitude. Does anyone think that the choice is going to cause
        implementors to make material errors?</div>
      <div><br>
      </div>
    </blockquote>
    I don't. I will also note that the document has undergone numerous
    revisions with significant terminology rewrite on multiple occasions
    to try and satisfy diverse comments from a significant number of
    people. The terminology that is found in the document represents a
    compromise that the WG participants have consensus on. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming (with chair and individual hat on)<br>
    <br>
    <br>
    <blockquote type="cite"
      cite="mid:A8A3827C-D8AD-4DAE-BE81-2D577F8B4EBD@nostrum.com">
      <div>Ben.</div>
    </blockquote>
    <br>
  </body>
</html>

--------------9BB432A59BEFA6DD53517269--


From nobody Sun Apr 22 08:21:45 2018
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 BFB801242F7; Sun, 22 Apr 2018 08:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 Us9mf7jgFnc3; Sun, 22 Apr 2018 08:21:41 -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 4E50C120454; Sun, 22 Apr 2018 08:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9163; q=dns/txt; s=iport; t=1524410501; x=1525620101; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=b8vlNOo6P3reBbhWL+LubmLWoQFMTKHV4Sax6VxJ8cM=; b=MV+d9XvzuEwSyVFgrNnY86mfU0FhwrhfcS1ZUbBzk4qwE43+x+7yRpWT hT4nYrQ2/tU/Hne/eyHCgX4uYS2qfoC/feiYLTwJoe3BFc93UFTJ773u/ cPJFJrAiIwF4OwmKRVcsat6D8AJ5TW6D2b+yxkDOtGcBB2uoEMYq7fwVZ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AoAwAJp9xa/4ENJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDYRdjKINqlHiBSwghdRqOEoUCgWQLI4QCRgKCRSE4FAE?= =?us-ascii?q?CAQEBAQEBAmwcDIUiAQEBAQIBHQZWEAsYIwQDAgJGEQYBDAYCAQGEfgUID6c?= =?us-ascii?q?WghwfhDmDZoIpBYgMgVQ/gQ8jDIInNYMRAgGBPwEBBoMYglQCkGiHCwiOOga?= =?us-ascii?q?BNINdgjmFBJAtgSUzIYFSTSMVO4F1ToJIiEiFWiMwAY4VgjcBAQ?=
X-IronPort-AV: E=Sophos;i="5.49,312,1520899200";  d="scan'208,217";a="385095967"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Apr 2018 15:21:40 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w3MFLdJj021008; Sun, 22 Apr 2018 15:21:39 GMT
To: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <74812b37-f073-8e40-8637-a0244798227b@cisco.com>
Date: Sun, 22 Apr 2018 11:21:39 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com>
Content-Type: multipart/alternative; boundary="------------4766AED2D7DE070FF41DFF41"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/E-ZEqOUpw-StBc4k8xw77_W0ruo>
Subject: Re: [MMUSIC] [ MMUSIC Chairs: Note action required ]. Re: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 15:21:44 -0000

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



On 4/19/18 5:56 AM, Ben Campbell wrote:
> MMUSIC chairs, please see request below:
>
> On Apr 17, 2018, at 8:18 PM, Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>> wrote:
>
>>     >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>     >>>>> address:port, because if the peer rejects BUNDLE but
>>     accepts the m=
>>     >>>>> section then it's broken.
>>     >>>>
>>     >>>> Note that in this case the usage of BUNDLE has already been
>>     negotiated.
>>     >>>> Then, if the answerer does not accept the new m= section
>>     into the BUNDLE
>>     >>>> group, it needs to send an offer where it removes it, as
>>     described in
>>     >>>> section 8.3.3.
>>     >>>
>>     >>> Well, both of these options correspond to insisting that the
>>     m= section
>>     >>> be in the BUNDLE group. If I just want to suggest it, I would
>>     have to provide
>>     >>> a fresh unique address. Or are you saying that's impossible.
>>     >>>
>>     >> Yes.
>>     >>
>>     >> Previously, when the offerer wanted to add a new m- section to
>>     a BUNDLE
>>     >> group, it had to choice of either assigning a unique address or a
>>     >> previously negotiated bundle address.
>>     >>
>>     >> That option was removed as part of task (triggered by WGLC
>>     comments etc)
>>     >
>>     > That seems like a pretty material change. Was there a call for
>>     consensus on that?
>>
>>     No. But, the suggested changes were indicated on the list, there
>>     were pull requests etc, so people were informed about it and had
>>     a chance to comment/object.
>>
>>
>> Hmm... Ben, do you think these were properly surfaced to the WG?
>
> I seem to recall non-trivial discussion about it on list, but I am not 
> in a position to verify it prior to the telechat.
>
> Chairs/shepherd: Please comment on whether you believe the 
> aforementioned change represents wg consensus.

The change in question was introduced in the -41 version of the 
document, and the author announced both the change as well as the 
updated document (pointing out the change) on the MMUSIC list on 
November 24, 2017, see:

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

A few additional updates where made in -42, and on November 28, 2017, we 
announced a final chance for people to comment on the document before we 
would move ahead with the publication request

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

We received only 1 comment back, which was addressed in -43. Both of the 
chairs reviewed this updated document as well.


In summary, the change has clearly been surfaced to the WG and people 
have been given more than one opportunity to comment on it. The comments 
that were provided have been addressed, and hence the resulting document 
represents WG consensus.

Thanks

-- Flemming (as MMUSIC co-chair)



>
> Thanks!
>
> Ben.
>
>>
>> -Ekr
>>


--------------4766AED2D7DE070FF41DFF41
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/19/18 5:56 AM, Ben Campbell wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div>MMUSIC chairs, please see request below:</div>
      <div><br>
      </div>
      <div>On Apr 17, 2018, at 8:18 PM, Eric Rescorla &lt;<a
          href="mailto:ekr@rtfm.com" moz-do-not-send="true">ekr@rtfm.com</a>&gt;
        wrote:</div>
      <div><br>
      </div>
      <blockquote type="cite">
        <div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div class="HOEnZb">
              <div class="h5">&gt;&gt;&gt;&gt;&gt; IMPORTANT: This
                doesn't sound right. You can't use the existing<br>
                &gt;&gt;&gt;&gt;&gt; address:port, because if the peer
                rejects BUNDLE but accepts the m=<br>
                &gt;&gt;&gt;&gt;&gt; section then it's broken.<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; Note that in this case the usage of
                BUNDLE has already been negotiated.<br>
                &gt;&gt;&gt;&gt; Then, if the answerer does not accept
                the new m= section into the BUNDLE<br>
                &gt;&gt;&gt;&gt; group, it needs to send an offer where
                it removes it, as described in<br>
                &gt;&gt;&gt;&gt; section 8.3.3.<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; Well, both of these options correspond to
                insisting that the m= section<br>
                &gt;&gt;&gt; be in the BUNDLE group. If I just want to
                suggest it, I would have to provide<br>
                &gt;&gt;&gt; a fresh unique address. Or are you saying
                that's impossible.<br>
                &gt;&gt;&gt;<br>
                &gt;&gt; Yes.<br>
                &gt;&gt;<br>
                &gt;&gt; Previously, when the offerer wanted to add a
                new m- section to a BUNDLE<br>
                &gt;&gt; group, it had to choice of either assigning a
                unique address or a<br>
                &gt;&gt; previously negotiated bundle address.<br>
                &gt;&gt;<br>
                &gt;&gt; That option was removed as part of task
                (triggered by WGLC comments etc)<br>
                &gt;<br>
                &gt; That seems like a pretty material change. Was there
                a call for consensus on that?<br>
                <br>
              </div>
            </div>
            No. But, the suggested changes were indicated on the list,
            there were pull requests etc, so people were informed about
            it and had a chance to comment/object.<br>
          </blockquote>
          <div><br>
          </div>
          <div>Hmm... Ben, do you think these were properly surfaced to
            the WG?</div>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>I seem to recall non-trivial discussion about it on list, but
        I am not in a position to verify it prior to the telechat. </div>
      <div><br>
      </div>
      <div>Chairs/shepherd: Please comment on whether you believe the
        aforementioned change represents wg consensus.</div>
    </blockquote>
    <br>
    The change in question was introduced in the -41 version of the
    document, and the author announced both the change as well as the
    updated document (pointing out the change) on the MMUSIC list on
    November 24, 2017, see:<br>
    <br>
       
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/mmusic/current/msg18364.html">https://www.ietf.org/mail-archive/web/mmusic/current/msg18364.html</a><br>
       
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/mmusic/current/msg18367.html">https://www.ietf.org/mail-archive/web/mmusic/current/msg18367.html</a><br>
    <br>
    A few additional updates where made in -42, and on November 28,
    2017, we announced a final chance for people to comment on the
    document before we would move ahead with the publication request<br>
    <br>
       
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/mmusic/current/msg18373.html">https://www.ietf.org/mail-archive/web/mmusic/current/msg18373.html</a><br>
    <br>
    We received only 1 comment back, which was addressed in -43. Both of
    the chairs reviewed this updated document as well. <br>
    <br>
    <br>
    In summary, the change has clearly been surfaced to the WG and
    people have been given more than one opportunity to comment on it. 
    The comments that were provided have been addressed, and hence the
    resulting document represents WG consensus. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming (as MMUSIC co-chair)<br>
    <br>
    <br>
    <br>
    <blockquote type="cite"
      cite="mid:5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com">
      <div><br>
      </div>
      <div>Thanks!</div>
      <div><br>
      </div>
      <div>Ben.</div>
      <br>
      <blockquote type="cite">
        <div>
          <div><br>
          </div>
          <div>-Ekr</div>
          <div><br>
          </div>
        </div>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

--------------4766AED2D7DE070FF41DFF41--


From nobody Sun Apr 22 08:27:51 2018
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 77F04124D68; Sun, 22 Apr 2018 08:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 20b8XEOxqNHE; Sun, 22 Apr 2018 08:27:42 -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 DE0A4120454; Sun, 22 Apr 2018 08:27:41 -0700 (PDT)
Received: from [10.0.2.31] (ip-131-232-239-173.texas.us.northamericancoax.com [173.239.232.131]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w3MFRUoK084518 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 22 Apr 2018 10:27:32 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host ip-131-232-239-173.texas.us.northamericancoax.com [173.239.232.131] claimed to be [10.0.2.31]
Content-Type: multipart/alternative; boundary=Apple-Mail-BB8B27D9-24DE-4E0B-BD3F-0991A3D3757F
Mime-Version: 1.0 (1.0)
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (15E216)
In-Reply-To: <74812b37-f073-8e40-8637-a0244798227b@cisco.com>
Date: Sun, 22 Apr 2018 17:27:29 +0200
Cc: Eric Rescorla <ekr@rtfm.com>, Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <F7EAC026-BF6D-4464-9719-3CD0F544C987@nostrum.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com> <74812b37-f073-8e40-8637-a0244798227b@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RQjbXZ69vY0nBI3TxZ_0FQzmTPw>
Subject: Re: [MMUSIC] [ MMUSIC Chairs: Note action required ]. Re: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 15:27:44 -0000

--Apple-Mail-BB8B27D9-24DE-4E0B-BD3F-0991A3D3757F
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Thanks, Flemming!

> On Apr 22, 2018, at 5:21 PM, Flemming Andreasen <fandreas@cisco.com> wrote=
:
>=20
>=20
>=20
>> On 4/19/18 5:56 AM, Ben Campbell wrote:
>> MMUSIC chairs, please see request below:
>>=20
>> On Apr 17, 2018, at 8:18 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>>=20
>>>> >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>>> >>>>> address:port, because if the peer rejects BUNDLE but accepts the m=
=3D
>>>> >>>>> section then it's broken.
>>>> >>>>
>>>> >>>> Note that in this case the usage of BUNDLE has already been negoti=
ated.
>>>> >>>> Then, if the answerer does not accept the new m=3D section into th=
e BUNDLE
>>>> >>>> group, it needs to send an offer where it removes it, as described=
 in
>>>> >>>> section 8.3.3.
>>>> >>>
>>>> >>> Well, both of these options correspond to insisting that the m=3D s=
ection
>>>> >>> be in the BUNDLE group. If I just want to suggest it, I would have t=
o provide
>>>> >>> a fresh unique address. Or are you saying that's impossible.
>>>> >>>
>>>> >> Yes.
>>>> >>
>>>> >> Previously, when the offerer wanted to add a new m- section to a BUN=
DLE
>>>> >> group, it had to choice of either assigning a unique address or a
>>>> >> previously negotiated bundle address.
>>>> >>
>>>> >> That option was removed as part of task (triggered by WGLC comments e=
tc)
>>>> >
>>>> > That seems like a pretty material change. Was there a call for consen=
sus on that?
>>>>=20
>>>> No. But, the suggested changes were indicated on the list, there were p=
ull requests etc, so people were informed about it and had a chance to comme=
nt/object.
>>>=20
>>> Hmm... Ben, do you think these were properly surfaced to the WG?
>>=20
>> I seem to recall non-trivial discussion about it on list, but I am not in=
 a position to verify it prior to the telechat.=20
>>=20
>> Chairs/shepherd: Please comment on whether you believe the aforementioned=
 change represents wg consensus.
>=20
> The change in question was introduced in the -41 version of the document, a=
nd the author announced both the change as well as the updated document (poi=
nting out the change) on the MMUSIC list on November 24, 2017, see:
>=20
>     https://www.ietf.org/mail-archive/web/mmusic/current/msg18364.html
>     https://www.ietf.org/mail-archive/web/mmusic/current/msg18367.html
>=20
> A few additional updates where made in -42, and on November 28, 2017, we a=
nnounced a final chance for people to comment on the document before we woul=
d move ahead with the publication request
>=20
>     https://www.ietf.org/mail-archive/web/mmusic/current/msg18373.html
>=20
> We received only 1 comment back, which was addressed in -43. Both of the c=
hairs reviewed this updated document as well.=20
>=20
>=20
> In summary, the change has clearly been surfaced to the WG and people have=
 been given more than one opportunity to comment on it.  The comments that w=
ere provided have been addressed, and hence the resulting document represent=
s WG consensus.=20
>=20
> Thanks=20
>=20
> -- Flemming (as MMUSIC co-chair)
>=20
>=20
>=20
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>>>=20
>>> -Ekr
>>>=20
>=20

--Apple-Mail-BB8B27D9-24DE-4E0B-BD3F-0991A3D3757F
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Thanks, Flemming!</div><div><br>On Apr 22, 2018, at 5:21 PM, Flemming Andreasen &lt;<a href="mailto:fandreas@cisco.com">fandreas@cisco.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  
  
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/19/18 5:56 AM, Ben Campbell wrote:<br>
    </div>
    <blockquote type="cite" cite="mid:5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div>MMUSIC chairs, please see request below:</div>
      <div><br>
      </div>
      <div>On Apr 17, 2018, at 8:18 PM, Eric Rescorla &lt;<a href="mailto:ekr@rtfm.com" moz-do-not-send="true">ekr@rtfm.com</a>&gt;
        wrote:</div>
      <div><br>
      </div>
      <blockquote type="cite">
        <div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div class="HOEnZb">
              <div class="h5">&gt;&gt;&gt;&gt;&gt; IMPORTANT: This
                doesn't sound right. You can't use the existing<br>
                &gt;&gt;&gt;&gt;&gt; address:port, because if the peer
                rejects BUNDLE but accepts the m=<br>
                &gt;&gt;&gt;&gt;&gt; section then it's broken.<br>
                &gt;&gt;&gt;&gt;<br>
                &gt;&gt;&gt;&gt; Note that in this case the usage of
                BUNDLE has already been negotiated.<br>
                &gt;&gt;&gt;&gt; Then, if the answerer does not accept
                the new m= section into the BUNDLE<br>
                &gt;&gt;&gt;&gt; group, it needs to send an offer where
                it removes it, as described in<br>
                &gt;&gt;&gt;&gt; section 8.3.3.<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; Well, both of these options correspond to
                insisting that the m= section<br>
                &gt;&gt;&gt; be in the BUNDLE group. If I just want to
                suggest it, I would have to provide<br>
                &gt;&gt;&gt; a fresh unique address. Or are you saying
                that's impossible.<br>
                &gt;&gt;&gt;<br>
                &gt;&gt; Yes.<br>
                &gt;&gt;<br>
                &gt;&gt; Previously, when the offerer wanted to add a
                new m- section to a BUNDLE<br>
                &gt;&gt; group, it had to choice of either assigning a
                unique address or a<br>
                &gt;&gt; previously negotiated bundle address.<br>
                &gt;&gt;<br>
                &gt;&gt; That option was removed as part of task
                (triggered by WGLC comments etc)<br>
                &gt;<br>
                &gt; That seems like a pretty material change. Was there
                a call for consensus on that?<br>
                <br>
              </div>
            </div>
            No. But, the suggested changes were indicated on the list,
            there were pull requests etc, so people were informed about
            it and had a chance to comment/object.<br>
          </blockquote>
          <div><br>
          </div>
          <div>Hmm... Ben, do you think these were properly surfaced to
            the WG?</div>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>I seem to recall non-trivial discussion about it on list, but
        I am not in a position to verify it prior to the telechat.&nbsp;</div>
      <div><br>
      </div>
      <div>Chairs/shepherd: Please comment on whether you believe the
        aforementioned change represents wg consensus.</div>
    </blockquote>
    <br>
    The change in question was introduced in the -41 version of the
    document, and the author announced both the change as well as the
    updated document (pointing out the change) on the MMUSIC list on
    November 24, 2017, see:<br>
    <br>
    &nbsp;&nbsp;&nbsp;
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/mmusic/current/msg18364.html">https://www.ietf.org/mail-archive/web/mmusic/current/msg18364.html</a><br>
    &nbsp;&nbsp;&nbsp;
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/mmusic/current/msg18367.html">https://www.ietf.org/mail-archive/web/mmusic/current/msg18367.html</a><br>
    <br>
    A few additional updates where made in -42, and on November 28,
    2017, we announced a final chance for people to comment on the
    document before we would move ahead with the publication request<br>
    <br>
    &nbsp;&nbsp;&nbsp;
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/mmusic/current/msg18373.html">https://www.ietf.org/mail-archive/web/mmusic/current/msg18373.html</a><br>
    <br>
    We received only 1 comment back, which was addressed in -43. Both of
    the chairs reviewed this updated document as well. <br>
    <br>
    <br>
    In summary, the change has clearly been surfaced to the WG and
    people have been given more than one opportunity to comment on it.&nbsp;
    The comments that were provided have been addressed, and hence the
    resulting document represents WG consensus. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming (as MMUSIC co-chair)<br>
    <br>
    <br>
    <br>
    <blockquote type="cite" cite="mid:5FDCE11E-015B-4E44-BA04-89D71107A540@nostrum.com">
      <div><br>
      </div>
      <div>Thanks!</div>
      <div><br>
      </div>
      <div>Ben.</div>
      <br>
      <blockquote type="cite">
        <div>
          <div><br>
          </div>
          <div>-Ekr</div>
          <div><br>
          </div>
        </div>
      </blockquote>
    </blockquote>
    <br>
  

</div></blockquote></body></html>
--Apple-Mail-BB8B27D9-24DE-4E0B-BD3F-0991A3D3757F--


From nobody Sun Apr 22 11:43:16 2018
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 EABA2120227 for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 11:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnwzyBbnk4RI for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 11:43:08 -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 C270A126D3F for <mmusic@ietf.org>; Sun, 22 Apr 2018 11:43:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524422584; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=pNSj5je5u+8VgA8k22P9twPYsy33IjPaVvuFbQDDrD4=; b=Iwsf77rDk6AnNxd9jJC5Qe9pVl86X4LkI23FKcNn0BCALvaHcsWKVFHiABMXznLM cW4/ekXciMLtlMSNzVvQlZe5bhKHeLTHBRySM+3klbbxPd4DLNFv+wSrf4y88TFv jzO1OTliHdFSnBR5jHvWZ+pE3b1avJqePryh/FpQexU=;
X-AuditID: c1b4fb25-8a3ff70000006561-c6-5adcd7b7e61d
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id F4.5A.25953.7B7DCDA5; Sun, 22 Apr 2018 20:43:04 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0382.000; Sun, 22 Apr 2018 20:43:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>
CC: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Adam Roach <adam@nostrum.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
Thread-Index: AQHT1hyzAELqwkkTZUijiT6B4HRdwqQEwtyAgAAUTwCAADX2AIAANsSAgADXseCAAZvZAIAAP3yAgAA0rgD//9WjAIAAJksw///hOwCAAUs4gIAArzuAgAEPekA=
Date: Sun, 22 Apr 2018 18:43:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E96707@ESESSMB109.ericsson.se>
References: <152394968680.26207.6988610273307864563.idtracker@ietfa.amsl.com> <D6FB7DAD.2E10A%christer.holmberg@ericsson.com> <CABcZeBPo3tGbAH=45mX7nEtJN=YQQ9vY9hH4WeLhnfNVYJ__cQ@mail.gmail.com> <D6FBD6CA.2E401%christer.holmberg@ericsson.com> <CABcZeBO3rQyMBUvROxU1AbCLSjNkrEZvYXSyKb=t_tTX1ATGxA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E87BE7@ESESSMB109.ericsson.se> <29FAF45F-5A95-42FC-9FDB-DA8257B85D67@nostrum.com> <CABcZeBNr2pthZvDmZuEzEGJgs6Ef+1tKmCd+yfbaogGfAep27Q@mail.gmail.com> <D6FE753F.2E6A0%christer.holmberg@ericsson.com> <CABcZeBNiXxphB_Lg=oMjuYdcF0TjUT458Ac4Tvr_M+x+gK5qSA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8FE63@ESESSMB109.ericsson.se> <CABcZeBO=Akn6uLwZRwAQXujO7ViVR53re1HdfgXE_MUFdhy94w@mail.gmail.com> <D6FF62E6.2E737%christer.holmberg@ericsson.com> <CABcZeBOwDgK+SScxkGdY4hGx2ecngJmzs5=fxvVG0oJaV6kEiQ@mail.gmail.com>
In-Reply-To: <CABcZeBOwDgK+SScxkGdY4hGx2ecngJmzs5=fxvVG0oJaV6kEiQ@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.164]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEIsWRmVeSWpSXmKPExsUyM2K7pe6O63eiDG6cZ7fY83cRu8X8ztPs FtNnvWOzWPH6HLvF+wu6FjP+TGS2OL9zPZPF1OWPWRw4PKb83sjqsWTJTyaPWTufsHhMftzG HMASxWWTkpqTWZZapG+XwJUx7+ZK1oJvHBX/3k5kbGC8wdHFyMEhIWAi8fhaQhcjF4eQwBFG iQO71jNDOIsZJZ6+P8EOUsQmYCHR/U+7i5GTQ0RAQeLXnxMsIDXMAueZJOZua2YDSQgLpEvM WbWMGaReRCBD4v6DTJAaEYEuRonp946B1bAIqEp8+HqOGcTmFfCVOLL2DQvEsj9sEp/7HjCB JDgFAiWebW5iBLEZBcQkvp9aAxZnFhCXuPVkPpgtISAgsWTPeWYIW1Ti5eN/rBC2ksTZL1PY QI5gFtCUWL9LH6JVUWJK90N2iL2CEidnPmGZwCg6C8nUWQgds5B0zELSsYCRZRWjaHFqcVJu upGxXmpRZnJxcX6eXl5qySZGYMwd3PJbdQfj5TeOhxgFOBiVeHj/Xr0TJcSaWFZcmXuIUYKD WUmE91kuUIg3JbGyKrUoP76oNCe1+BCjNAeLkjjvQ/PNUUIC6YklqdmpqQWpRTBZJg5OqQbG usxJrDq/fp65t+5v87pp6pmqO1q+v7m9l1/8ziOZwGSZKDG3VTVfoqfe+GlzdOUiFsVLj6MU EnrOnVzmnK+of/hKlqTWcjvueb38ItLv8mI3p3zZqsJ/ID9owRGZA0uvT5t9N2CbGH8xW/Hp o7OyZa66l7LckJur+mqCus/T6KkhigblKdIsSizFGYmGWsxFxYkAD252TrUCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rnmZlmgjn2uwSj55Zr6doFLoXBM>
Subject: Re: [MMUSIC] Adam Roach's Yes on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 18:43:10 -0000

SGksDQoNCi4uLg0KDQpTZWN0aW9uIDguMy4xOg0KLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQo+PsKg
IklmIGFsbCBvZiB0aGUgY3JpdGVyaWEgYWJvdmUgYXJlIGZ1bGZpbGxlZCwgdGhlIGFuc3dlcmVy
IE1VU1Qgc2VsZWN0DQo+PiB0aGUgc3VnZ2VzdGVkIG9mZmVyZXIgQlVORExFIGFkZHJlc3M6cG9y
dC7Csg0KPj4NCj4+IEluIHRoZSBiZWdpbm5pbmcgb2YgdGhlIHNlY3Rpb24sIHRoZSB0ZXh0IERP
RVMgdGFsayBhYm91dCBtPSBzZWN0aW9uLCBidXQNCj4+IHRoZSBzcGVjaWZpYyB0ZXh0IGFib3Zl
IElTIGFib3V0IHRoZSBhbnN3ZXJlciBzZWxlY3RpbmcgdGhlIG9mZmVyZXIgQlVORExFDQo+PiBh
ZGRyZXNzOnBvcnQsIGkuZS4sIHRoZSBhZGRyZXNzOnBvcnQgdGhhdCB0aGUgb2ZmZXJlciBpcyBn
b2luZyB0byB1c2UuDQo+DQo+IFJpZ2h0LCBidXQgdGhlbiBpdCB0b3RhbGx5IG9taXRzIHRoZSB0
ZXh0IGFib3V0IHRoZSAqb3RoZXIqIHBhcmFtZXRlcnMsIHdoaWNoDQo+IGFyZSBlcXVhbGx5IGlt
cG9ydGFudC4gV2hlcmUgZG9lcyB0aGlzIGRvY3VtZW50IHRlbGwgbWUgdG8gdXNlIHRoZQ0KPklD
RSBjYW5kaWRhdGVzIGZyb20gdGhhdCBtPSBzZWN0aW9uLg0KDQpPaywgSSBhZ3JlZSB0aGF0IG5l
ZWRzIHRvIGJlIGNsYXJpZmllZC4NCg0KKFNlY3Rpb24gOC4xIGRlZmluZXMgaG93L3doZXJlIFNE
UCBhdHRyaWJ1dGVzIGFyZSBhc3NpZ25lZCwgYnV0IGl0IGRvZXNuJ3Qgc2F5IGZyb20gd2hpY2gg
bT0gc2VjdGlvbiBhbmQgb2ZmZXJlci9hbnN3ZXJlciBwaWNrcyB0aGUgYXR0cmlidXRlcyBvZiB0
aGUgcGVlcikNCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Sun Apr 22 13:13:02 2018
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 08BCC126DC2 for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 13:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJtRclhuPlIO for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 13:12:59 -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 7D16C126D3F for <mmusic@ietf.org>; Sun, 22 Apr 2018 13:12:59 -0700 (PDT)
X-AuditID: 1207440c-309ff70000002b7e-ac-5adcecc8ff3c
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 98.A6.11134.9CCECDA5; Sun, 22 Apr 2018 16:12:57 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w3MKCt9D030344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Sun, 22 Apr 2018 16:12:56 -0400
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <9d453c11-d225-422e-ad8d-2e8ce9d90fb1@cisco.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <328adc10-0b8c-f682-3df6-ba7015105f65@alum.mit.edu>
Date: Sun, 22 Apr 2018 16:12:55 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <9d453c11-d225-422e-ad8d-2e8ce9d90fb1@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsUixO6iqHvqzZ0og6Pb2C2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujIaF79gKFnBWPDxwir2BcRF7FyMnh4SAicTGm2eYuxi5OIQE djBJnDtyhwnC+c4k8WhVJxNIlbBAG6PE7Kt6ILaIgLDEjLd/2SCK+lkk1q+5ygKSYBPQkphz 6D+YzStgL7H3/hU2EJtFQFXi3cmDYHFRgTSJ+5snMULUCEqcnPkEKM7BwSlgKzFvdT5ImFnA TGLe5ofMELa4xK0n85kgbHmJ7W/nME9g5J+FpHsWkpZZSFpmIWlZwMiyilEuMac0Vzc3MTOn ODVZtzg5MS8vtUjXUC83s0QvNaV0EyMkLHl2MH5bJ3OIUYCDUYmHd8as21FCrIllxZW5hxgl OZiURHmDs25FCfEl5adUZiQWZ8QXleakFh9ilOBgVhLhfZZ7J0qINyWxsiq1KB8mJc3BoiTO y2qyN0pIID2xJDU7NbUgtQgmK8PBoSTBu/Y1UKNgUWp6akVaZk4JQpqJgxNkOA/QcBuQGt7i gsTc4sx0iPwpRl2OKc/7e5iFWPLy81KlxHm1QIoEQIoySvPg5sDSyStGcaC3hHk3gFTxAFMR 3KRXQEuYgJZ0SIItKUlESEk1MMaxFmffUY3a76Sd9UYulcfLsyPJTEtid7zpp+k35vfP2/il xc170hLxG6v/yRR4zBQ/VTfnxFXGoEP3V85iPrQ7JL+WYwWjtkPnex3Li3Xr6r8uUJdvD3Oy ini0cF8Zb098R8+nlMKvHEdL1eO+1x/941nrsd2gN72C/0VgMGPenXuPNBITlViKMxINtZiL ihMBahMtRwIDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Qo9mlvhOsgaVofDLltiHRhdiBXg>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 20:13:01 -0000

On 4/22/18 10:36 AM, Flemming Andreasen wrote:

>>>> But, we would not be using the generic O/A structure.
>>> I'm not seeing a problem with that
>> I think some do, e.g., the chairs.
>>
>> I have personally also been strict about it when reviewing documents 
>> written by others, but I have no problem allowing other structures if 
>> seen more appropriate - if everyone is ok with it.
> 
> Agreed. We have been using this structure and consistently asked authors 
> to use it as well for a long time. It's an established MMUSIC practice 
> in dealing with offer/answer procedures and I'm not in favor of changing 
> this.

This has also bothered me a bit. The structure was adopted for SDP O/A 
in the context of a dialog. And in that context the structure is well 
defined, where the first O/A really requires some different 
consideration than subsequent O/A.

*This* usage is different, in the the first offer of a bundle might not 
be the first offer of SDP in the dialog. It is potentially confusing to 
mix these two. Reusing the *structure* makes sense, but doing something 
to make clear that this is not the same is a good idea.

	Thanks,
	Paul


From nobody Sun Apr 22 14:41:15 2018
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 C673B124BE8 for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 14:41:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6J1_iOJPzRM for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 14:41:11 -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 833C8126C2F for <mmusic@ietf.org>; Sun, 22 Apr 2018 14:40:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524433252; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=e04PBYyF0ktjuo1KnfcPOPK0Aptiot3f/Kg3HOKu2lM=; b=Ex1J+8iZPKV6sHQXzbXsYgCV6NVb8jrcEskmAtFUX9TF9Gk4sMmOtRFNu4HnNsbx /i4u4WY6K7mCiV64Phh/MGGSK6yL86rxWF+8mq8Caj9vn0ueLw45cz6VsJtCtZoS 9dwMIFScJM9CtecLVeVjklcXYnZPj8yg5pqNEvTD2hI=;
X-AuditID: c1b4fb30-0dfff70000007681-ce-5add01647d26
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id F7.38.30337.4610DDA5; Sun, 22 Apr 2018 23:40:52 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0382.000; Sun, 22 Apr 2018 23:40:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
Thread-Index: AQHT1lZf0qxFmZgCwkeSofFpx7VVFKQFQviAgADjodCAADKqAIAATwsA///WzoCAAFZ94IAF6sOAgABeCYCAADhiQA==
Date: Sun, 22 Apr 2018 21:40:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E96A8D@ESESSMB109.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <9d453c11-d225-422e-ad8d-2e8ce9d90fb1@cisco.com> <328adc10-0b8c-f682-3df6-ba7015105f65@alum.mit.edu>
In-Reply-To: <328adc10-0b8c-f682-3df6-ba7015105f65@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.162]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyM2K7tG4K490og4bZshZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJWxYX1CwXreiqaHHSwNjDu5uhg5OSQETCQa thxj7mLk4hASOMIo0b7iDJSzmFHi9Ks/7F2MHBxsAhYS3f+0QRpEBHwlnj2+zQZSIyzQxijx 7/IHFhBHRKCdUWLj2XvsEFVZEjvnP2AEsVkEVCV6V+5iArF5gbrnrdvHCrHhKIvEzZVXWUAS nAIOEvO2/mQGsRkFxCS+n1oD1sAsIC5x68l8JohbBSSW7DnPDGGLSrx8/I8VwlaSePp/CVS9 jsSC3Z/YIGxtiWULXzNDLBaUODnzCcsERpFZSMbOQtIyC0nLLCQtCxhZVjGKFqcWJ+WmGxnp pRZlJhcX5+fp5aWWbGIExsTBLb8NdjC+fO54iFGAg1GJh3f7hztRQqyJZcWVuYcYJTiYlUR4 n+UChXhTEiurUovy44tKc1KLDzFKc7AoifNa+G2OEhJITyxJzU5NLUgtgskycXBKNTAu29aW JFv/fmuOoeZa5p3GBxt55r3pP28R+rGn5cXf9UI+02ra2VqN732ezvCl+tCl2I33XUQ9zxg/ 2zp9g0Xlij/TuzoSd09lcWypaPLr++1b6C6/+8Tn189ftn9jWWV9ZqrcjSIDI7MbFhJb4iYL C34Vc9/34dLXBB0+2wlXoj5snZ60hP+5EktxRqKhFnNRcSIAmrmk4oUCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/F5TTy-UC4pc7QEW2bJy1Q9mW7oA>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 22 Apr 2018 21:41:14 -0000

Hi,

>>>>> But, we would not be using the generic O/A structure.
>>>> I'm not seeing a problem with that
>>> I think some do, e.g., the chairs.
>>>
>>> I have personally also been strict about it when reviewing documents=20
>>> written by others, but I have no problem allowing other structures if=20
>>> seen more appropriate - if everyone is ok with it.
>>=20
>> Agreed. We have been using this structure and consistently asked=20
>> authors to use it as well for a long time. It's an established MMUSIC=20
>> practice in dealing with offer/answer procedures and I'm not in favor=20
>> of changing this.
>
> This has also bothered me a bit. The structure was adopted for SDP O/A in=
 the context of a dialog.=20
> And in that context the structure is well defined, where the first O/A re=
ally requires some different consideration than subsequent O/A.
>
> *This* usage is different, in the the first offer of a bundle might not b=
e the first offer of SDP in the dialog.=20
> It is potentially confusing to mix these two. Reusing the *structure* mak=
es sense, but doing something to=20
> make clear that this is not the same is a good idea.

There IS text in the draft clarifying that:

      "Initial offer: The first offer, within an SDP session (e.g. a SIP
      dialog when the Session Initiation Protocol (SIP) [RFC3261] is
      used to carry SDP), in which the offerer indicates that it wants
      to create a given BUNDLE group."

This is not even BUNDLE specific - I think there are very few (I can't thin=
k of any straight from my head) SDP extension where you would be required t=
o do something in the initial offer of the dialog.

Regards,

Christer


From nobody Sun Apr 22 22:28:20 2018
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 87D3C120227 for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 22:28:18 -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 HQqh7N9aazDt for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 22:28:16 -0700 (PDT)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::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 5F3E11272E1 for <mmusic@ietf.org>; Sun, 22 Apr 2018 22:28:16 -0700 (PDT)
Received: by mail-ua0-x22e.google.com with SMTP id a17so9374232uaf.13 for <mmusic@ietf.org>; Sun, 22 Apr 2018 22:28:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xQes3dO17owHRFkBL6Uj1bkz8wDKbZosIXWze3lcYjg=; b=EmYGYIO9qoaPa3k8jJVpVDkCxWoiLnLxuICnmBDlQCTlhu9VimgonjtvYBN1fR6cni CSZm44QJqr8amgyAAl6iReksJNPYh85MNi7xbCC1KF1ChONPEFmR2m13HsAyJd19LCrb xAnUuvc9xw3RG5kEdij3UuskYR2ERfcuk2ZTvVOz9wn/RCtr2amsWKGDeP/opW8zUfaH WJecnukeq3QO0jyr24FsQ1dM7LdPVnZYIOjgQtcxXc7sy9kv4Zy6MOSOOP4J90dnr3jR K1+/qpkXNwSD7SGH2SxA0nCW49epGsJfbmIM1CSEo1ajW050Z2ddiLlrCBhp7FcRBmdB lp0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xQes3dO17owHRFkBL6Uj1bkz8wDKbZosIXWze3lcYjg=; b=E3Ckpt3vFuPhUgyqHcg6a1fYk9Z441BZUW+Qhz/i42sD0VYCrO/M1Qxu5AfXmrmVpS DqJ9Ci2QgKRtQIvzWLtbpreyRvO/LJfP/r4UEP/X+vmgsFnPhavDt6mklD1GOjSIE2tP LWpZ1JApxoTcHrixNM1L49gYD0J6PZnxBGKZFrJqFNE7mYLWvmxdI7HtDAUYQg/e+aon 18gRXxCkQb1VC2Bj1x823/QZoGobKEd75yc/S6lgZymQYLn1NJbZS3KPE1rTiHxYK0+6 28zxnbPlzt1bPDSpbHkbKqzPg3re2Ad/Bv7FYgN4LaQnSPCxHR5YQ04JoFzkTsKVnXLl dX9w==
X-Gm-Message-State: ALQs6tAqW74zabpc2gKQNuCbsA5LYNXCRxF1EWgTk4WrWiJyJIKPUc1U +47j2TS0XLHLELI6/QeNLnV+t1OXqTZ7aaAfBRg=
X-Google-Smtp-Source: AB8JxZql03vbWjY4Pu3PEu6qSVtuwS4VN5pD4NCBMFTWx2cT/u8WvnbH/rlg/m7EK1GTLnZRi4UVm17OZAiVLbjpSbk=
X-Received: by 10.176.48.176 with SMTP id b16mr4819807uam.28.1524461295514; Sun, 22 Apr 2018 22:28:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Sun, 22 Apr 2018 22:28:15 -0700 (PDT)
In-Reply-To: <D6FB9C98.2E1E0%christer.holmberg@ericsson.com>
References: <D6FB9C98.2E1E0%christer.holmberg@ericsson.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sun, 22 Apr 2018 22:28:15 -0700
Message-ID: <CAMRcRGT7Kf=GvutamNZZ5Rua3SOgCjoKebjfc6k8cbjHT054ig@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="089e0832c6fcfe3982056a7d4d19"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UJKDe8y8P4TomLQ_JhX0iYnMGpw>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 05:28:18 -0000

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

Hi Christer,

 Please see response inline

Cheers
Suhas

On Tue, Apr 17, 2018 at 2:42 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =E2=80=98ice-=
options=E2=80=99
> attribute as both session- and media-level.
>
> However, there is no description of what it means to use the attribute on
> media-level. Does it mean that the indicated ICE extension is only used f=
or
> that particular media stream?
>
>
[Suhas] Section 10.2 defines explanation of each ice-options attributes for
media-level and session level considerations.
https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2



> Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16 indicates
> the attribute as session only (=E2=80=9CS=E2=80=9D).
>
> Is there a need to define it as media-level attribute?
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr">Hi Christer,<div><br></div><div>=C2=A0Please see response =
inline</div><div><br></div><div>Cheers</div><div>Suhas<br><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Tue, Apr 17, 2018 at 2:42 AM, C=
hrister Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@=
ericsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</spa=
n> 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">



<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>Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-<wbr>20 defines the =E2=
=80=98ice-options=E2=80=99 attribute as both session- and media-level.</div=
>
<div><br>
</div>
<div>However, there is no description of what it means to use the attribute=
 on media-level. Does it mean that the indicated ICE extension is only used=
 for that particular media stream?</div>
<div><br></div></div></blockquote><div><br></div><div>[Suhas] Section 10.2 =
defines explanation of each ice-options attributes for media-level and sess=
ion level considerations.</div><div><a href=3D"https://tools.ietf.org/html/=
draft-ietf-mmusic-ice-sip-sdp-20#section-10.2">https://tools.ietf.org/html/=
draft-ietf-mmusic-ice-sip-sdp-20#section-10.2</a><br></div><div><br></div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div styl=
e=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calib=
ri,sans-serif"><div>
</div>
<div>Also, section 5.12 of=C2=A0draft-ietf-mmusic-sdp-mux-<wbr>attributes-1=
6 indicates the attribute as session only (=E2=80=9CS=E2=80=9D).</div>
<div><br>
</div>
<div>Is there a need to define it as media-level attribute?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</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></div>

--089e0832c6fcfe3982056a7d4d19--


From nobody Sun Apr 22 22:48:45 2018
Return-Path: <jose@ch3m4.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10841270AC for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 22:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ch3m4.com header.b=T8rsniQf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Oo8DPWw2
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeySo7Tiqcyr for <mmusic@ietfa.amsl.com>; Sun, 22 Apr 2018 22:48:42 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 120B61270AB for <mmusic@ietf.org>; Sun, 22 Apr 2018 22:48:42 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 0745921660 for <mmusic@ietf.org>; Mon, 23 Apr 2018 01:48:41 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 23 Apr 2018 01:48:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ch3m4.com; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=hnCkmGkxyhUckyqAlVDI6cn5BpnSwlZLLYgkIfCB83c=; b=T8rsniQf QnEKz+MqPBkkNaXx5MLpbkPcFYb6UsWC4sbH5gDY9MDTHmUP2UbU9zF5bdO3iPKn 75OAaf/sJFmKhbVSB1jt4uZBszhzJN4sxEd+4C/wDqmt76r5lhydhSTp5bba0AI7 VtnlEQABCedOBkiEOKmC4AmFyOKAwoTt6OFRbCpTLiDtZj3lqZzGhQxoZb50IVdY OgS07z35Ve4ksRIxcaUWgyJKbQi4PgOAQ8Fv6l6DQpwC+iU1a/jCY/mYl2M4LMDS 0bTa620iaPfPaYudWQoec1yzpHhPbkGwCJxNzVVgcDZTSVf8+KCsHtli5Pfvjudn RfKdY5Q+hSBFVA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=hnCkmGkxyhUckyqAlVDI6cn5BpnSw lZLLYgkIfCB83c=; b=Oo8DPWw2n7lERZC6RDhcahptV91fOP4G8aX4nuIv+nWDc /rA0jKfelWS8anZD47CY5zCYcC2+OSjLm5RueBa7qKshjQOn7IU148EYp1mC4DLL boz3BdjaF34ZUFz2fuUxG89B2+j9Fb7XjB5x+g74738Dh1CrRT1fLfQH12tztTdB VlSog6fuMY+q4ZHa8bOae/iI2ajbn+30/KJq8bXiPx96J5ppBxq0MqNZ24aw1f9E cBVKbBDr9nWZtlpEvevwfdwx5sKsKXUyJWZjNRFcHrI/D9HJW5XPqDPeNPbPkHiR GOZyZMt0gvBb0GFyV/GRRvJGiWXUOroqpYHx74n9A==
X-ME-Sender: <xms:uHPdWv7ZMMpCoi0shYsM9c0dFdH9Y-7hd1qgTofRPDZrKK4I4Idmfg>
Received: from [192.168.1.61] (unknown [66.96.204.147]) by mail.messagingengine.com (Postfix) with ESMTPA id 135C7102CD for <mmusic@ietf.org>; Mon, 23 Apr 2018 01:48:39 -0400 (EDT)
From: Jose M Recio <jose@ch3m4.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Message-ID: <fee2d2da-ff37-9360-e3d7-d581a85a4c00@ch3m4.com>
Date: Mon, 23 Apr 2018 13:48:38 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/BZo4FM5RM9uj1V0KjOFtq2aKjKE>
Subject: [MMUSIC] Feedback requested - draft-ietf-mmusic-msrp-usage-data-channel
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 05:48:44 -0000

Hello, all,

Looking for feedback on a question about msrp-usage-data-channel draft:

In section 4.4, current draft says URI scheme

> is always "msrps", which indicates that the MSRP data channel is 
> always secured using DTLS
>
This is overloading the original meaning in RFC4975, that specified that

> "A scheme of "msrps" indicates that the underlying connection MUST be 
> protected with TLS."

Question: Should IANA info on msrps parameter be updated to include 
DTLS, including usage over WebRTC data channel, to reference to this 
draft? Or can we understand that DTLS is legitimately covered by the 
IANA registry described in RFC4975, so there's no need to update IANA?

Many thanks for your input, regards,

JM


From nobody Mon Apr 23 00:13:24 2018
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 3BF7C1271DF for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 00:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60hWqqwGcnCC for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 00:13: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 C5D85126DEE for <mmusic@ietf.org>; Mon, 23 Apr 2018 00:13:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524467596; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=/9tvzDlDymGfoKYQ8vp5DnOro9xWAizIxQF0qJwXLV0=; b=hN6I6hxoElqdYZ3PDRUaSyAUuBitYvCwth+0VLEExGfjvgTspp13Bg7vivuS5yuy kjDmZLHrjDB3GDUmPov2gvzQ6HRRFI5GQptCIuc1ZtyEed7URXYA9Ulx7mEGp0yS JkPQPeSTbqm+SWg/2S5LX+1NpUJzUqtk6b2Z8ZnuuQY=;
X-AuditID: c1b4fb3a-eae319c00000795a-bd-5add878ccbde
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 49.0C.31066.C878DDA5; Mon, 23 Apr 2018 09:13:16 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0382.000; Mon, 23 Apr 2018 09:12:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
CC: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] ice-options attribute: session- and media-level?
Thread-Index: AQHT1jBbREv5MGUFKUOXKyVx3A3GgaQNudmAgABQJ4A=
Date: Mon, 23 Apr 2018 07:12:54 +0000
Message-ID: <D703578D.2E9A2%christer.holmberg@ericsson.com>
References: <D6FB9C98.2E1E0%christer.holmberg@ericsson.com> <CAMRcRGT7Kf=GvutamNZZ5Rua3SOgCjoKebjfc6k8cbjHT054ig@mail.gmail.com>
In-Reply-To: <CAMRcRGT7Kf=GvutamNZZ5Rua3SOgCjoKebjfc6k8cbjHT054ig@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D703578D2E9A2christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNIsWRmVeSWpSXmKPExsUyM2K7im5P+90og8tnDCymLn/MYrFzbgez A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJWx5nQ3W8EXo4qj8z4zNjD26nQxcnJICJhI LLrRy9jFyMUhJHCEUeLnxX3MEM5iRondHQeAMhwcbAIWEt3/tEEaRAS0JFYvnssEEmYWUJe4 ujgIJCws4CYx79wCNogSd4lPX++yQthWEu8OfQeLswioSrRvOABm8wpYS6x7txpqbxOjxKS3 LxlBEpwCgRKnXrcxg9iMAmIS30+tYQKxmQXEJW49mc8EcbSAxJI955khbFGJl4//gS0TFdCT 2HDiNjvIbRICShK3NzhBtCZIfNp2lB1ir6DEyZlPWCYwis5CMnUWkrJZSMog4gYS78/NZ4aw tSWWLXwNZetLbPxylhHCtpZ4duw9C7KaBYwcqxhFi1OLi3PTjYz0Uosyk4uL8/P08lJLNjEC o/Dglt9WOxgPPnc8xCjAwajEw+tfczdKiDWxrLgy9xCjBAezkghvsR9QiDclsbIqtSg/vqg0 J7X4EKM0B4uSOK9TmkWUkEB6YklqdmpqQWoRTJaJg1OqgTGQs0dq3ZfQ6Xd6dltMOuF9SSPp xMN0bs6ZLofDN3mlsrgHhXDO8H+Z9eya/OTAZZNyk7OSnaYUWUxZymDOeuPHg+aSCUck1Jnn F3YLlR8zt49ZbWeXxvPWS8Ts6ETDG0FL33xS+Zl6Ua9a5aR8+vx9txlf7LyRMXPOrKKP6xfY cduczf3c+0eJpTgj0VCLuag4EQCPkLB/vgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/TgqeC4rTNu7DEQ2H4xJPKbwVZZk>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 07:13:22 -0000

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

Hi Suhas,

>> Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the =91ice-optio=
ns=92 attribute as both session- and media-level.
>>
>>However, there is no description of what it means to use the attribute on=
 media-level. Does it mean that the indicated ICE extension is only used fo=
r that particular media stream?
>
> [Suhas] Section 10.2 defines explanation of each ice-options attributes f=
or media-level and session level considerations.
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2

That text is VERY confusing  - especially the stuff about =93media-level at=
tributes being MUST be aggregated on session-level=94.

Also, the text seems to define such =93aggregation rules" for the =93rtp+ec=
n=94 option. If so, shouldn=92t the draft update RFC 6679?

Related to that, the text says that the the =93rtp+ecn=94 option can only b=
e used on session-level if it applies to all media, otherwise it has to be =
on the media-level. How does that fulfil the =93MUST aggregate to session-l=
evel=94 requirement?

Regards,

Christer





Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16 indicates the=
 attribute as session only (=93S=94).

Is there a need to define it as media-level attribute?

Regards,

Christer


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



--_000_D703578D2E9A2christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <07BD3C6CD1A1B6469C0300BA8B6E1396@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 style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
Hi Suhas,</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-s=
ize: 14px;">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); 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"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>&gt;&gt; Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-<wbr>20 defines =
the =91ice-options=92 attribute as both session- and media-level.</div>
<div>&gt;&gt;</div>
<div>&gt;&gt;However, there is no description of what it means to use the a=
ttribute on media-level. Does it mean that the indicated ICE extension is o=
nly used for that particular media stream?</div>
<div>&gt;</div>
</div>
<div>&gt; [Suhas] Section 10.2 defines explanation of each ice-options attr=
ibutes for media-level and session level considerations.</div>
<div>&gt;&nbsp;<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-ice=
-sip-sdp-20#section-10.2">https://tools.ietf.org/html/draft-ietf-mmusic-ice=
-sip-sdp-20#section-10.2</a><br>
</div>
</div>
</div>
</div>
</span>
<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;">
That text is VERY confusing &nbsp;- especially the stuff about =93media-lev=
el attributes being MUST be aggregated on session-level=94.</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;">
Also, the text seems to define such =93aggregation rules&quot; for the =93r=
tp&#43;ecn=94 option. If so, shouldn=92t the draft update RFC 6679?</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;">
Related to that, the text says that the the =93rtp&#43;ecn=94 option can on=
ly be used on session-level if it applies to all media, otherwise it has to=
 be on the media-level. How does that fulfil the =93MUST aggregate to sessi=
on-level=94 requirement?</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">Reg=
ards,</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif"><br=
>
</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif">Chr=
ister</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif"><br=
>
</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif"><br=
>
</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri,sans-serif"><br=
>
</font></div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"color: rgb(0, 0, 0); font-family=
: Calibri, sans-serif; font-size: 14px;">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div>&nbsp;</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div></div>
<div>Also, section 5.12 of&nbsp;draft-ietf-mmusic-sdp-mux-<wbr>attributes-1=
6 indicates the attribute as session only (=93S=94).</div>
<div><br>
</div>
<div>Is there a need to define it as media-level attribute?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</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>
</span>
</body>
</html>

--_000_D703578D2E9A2christerholmbergericssoncom_--


From nobody Mon Apr 23 01:07:20 2018
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 C9F99127286 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 01:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lhqXktqhqEZh for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 01:07:17 -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 74EB7127241 for <mmusic@ietf.org>; Mon, 23 Apr 2018 01:07:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524470835; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=234toE4HShbefXam5s959FRXZrLWmQMS6PJ7K77YvkY=; b=I9fesB8+I7wxRZ0PxG7fJyO3qfPb55HcVVtpRsvOsxf9bbeR5geUUztLKZNlAuW3 ljCa1a8uJBirZ+OKow2w9U2HuOTWJtMdaejmeCEhP8ezZTCmOg4l31QMcSXWMrlA 7HdPEjP7HAfjPZimAMOlQ3bVwzkfq0qR0aDV5619Otk=;
X-AuditID: c1b4fb30-4c8039c000007681-a7-5add9433959b
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 21.DA.30337.3349DDA5; Mon, 23 Apr 2018 10:07:15 +0200 (CEST)
Received: from [100.94.45.194] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.51) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 23 Apr 2018 10:07:14 +0200
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Flemming Andreasen <fandreas@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com>
Date: Mon, 23 Apr 2018 10:07:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM2K7sa7xlLtRBifma1gsf3mC0eL9BV2L /YvPM1tMXf6YxWLFhgOsDqwef99/YPKY8nsjq8e0+/fZPJYs+cnk0fbsDnsAaxSXTUpqTmZZ apG+XQJXxr9JyxkLbrlU/F0R28D41KyLkZNDQsBE4vW5syxdjFwcQgJHGCXOHz/CCOFsYpSY 1NoD5HBwCAuESCx5qQTSICJwgFFi5ndZiJoVjBJz5t5iBkmwCVhI3PzRyAZi8wrYS5zbPZcV xGYRUJVY1raNBcQWFYiR+HG0iwWiRlDi5MwnYDangIPEunkHwHqZgebMnH+eEcKWl2jeOpsZ whaXaPqyEmymkIC2RENTByvEB0oS1+ddZ5nAKDgLydhZSEbNQjJqFpJRCxhZVjGKFqcWJ+Wm GxnppRZlJhcX5+fp5aWWbGIERsDBLb8NdjC+fO54iFGAg1GJh3fSpLtRQqyJZcWVuYcYJTiY lUR4i/2AQrwpiZVVqUX58UWlOanFhxilOViUxHkt/DZHCQmkJ5akZqemFqQWwWSZODilGhg9 +IpkC2YcKvzNvNRhVhvPiVupAnU8cUezn+oWThVw6oxcOpPp4PRFE+7JPha6uWvKanuTd7eD PdTePWOxf9/08JSVreq13T+uzlt7YWWebk9P+3UhzwXyegKZ/+43Tyll3TBd9PKDqhVcb7mi qu+etow8/v1558eoapllmZ53/7EdTp3AvH6KEktxRqKhFnNRcSIA0ByqN3wCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0CvCG1BlGOauyx0iQQmwk5l_v7Y>
Subject: Re: [MMUSIC] INPUT NEEDED: Edits to 4566bis based on discussion in London
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 08:07:20 -0000

Hi Paul,

See inline.


Den 2018-04-19 kl. 23:47, skrev Paul Kyzivat:
> Flemming,
>
> Thanks for responding. I was despairing at getting anyone to respond.
>
> On 4/18/18 11:35 PM, Flemming Andreasen wrote:
>>
>>
>> On 4/5/18 5:17 PM, Paul Kyzivat wrote:
>>> I'm working on making the changes to 4566bis that were called for 
>>> based on the discussion in London. After reviewing all of that I 
>>> have some questions for which I need feedback from the wg.
>>>
>>> * Open Issue 3 - Regarding section 5.11 (z=):
>>>
>>> After reviewing the text for t=, r=, z=, the meaning of z= seems 
>>> pretty clear to me. The text for z= only talks about how it works 
>>> with r=. In principle, if the adjustment time precedes the start 
>>> time from t= then I suppose it *might* also apply there, and perhaps 
>>> to stop time as well.
>>>
>>> From the text and examples it is clear that this isn't usable for 
>>> anything else. E.g., it does *not* provide an adjustment that yields 
>>> local time.
>>>
>>> I could reword to say that it does *not* apply to the start/stop 
>>> times in t=, or that it definitely only applies to r=. Thoughts?
>>>
>> Section 5.11 (z=) says:
>> <quote>
>>
>>   Adjustments apply to all "t=" and
>>     "r=" lines in a session description.
>>
>> </quote>
>>
>> If I understood Colin's explanation in London correctly, then I 
>> believe it *should* only apply to the "r=" line, but that's not what 
>> it currently says. Maybe Colin can weigh in again ? In either case, I 
>> don't find the text as clear as you do, so adding a few more lines of 
>> text would be helpful.
>
> OK. I'll just add some additional text making it even clearer.
>
>>> * Open Issue 7 - Regarding section 8.2.2 ("proto"):
>>>
>>> The minutes (regarding udptl) say:
>>>
>>> "Action: will grandfather T.38 and keep the text as is. Also change 
>>> to currently defined registration procedure."
>>>
>>> What was meant here? The registration procedure says RFC Required. 
>>> Changing to conform to that is different from grandfathering T.38.
>>>
>>> ISTM that all is well as it is.
>>>
>> The minutes 
>> (https://datatracker.ietf.org/meeting/101/materials/minutes-101-mmusic/) 
>> say that:
>> <quote>
>>
>>     There was also discussion on how to handle udptl, concluding that 
>> the
>>     registry information for udptl is incorrect but that 4566bis will
>>     grandfather T.38 and keep the text as is. The currently defined
>>     registration procedure should however be changed to not only allow
>>     referencing standards track RFC. [Action: Authors]
>>
>> </quote>
>>
>> My memory may not serve me well here, but I thought we said that it 
>> should in fact reference a standards track RFC (there was some back 
>> and forth discussion between our ADs on this point after the initial 
>> conclusion I believe). Probably best to listen to the meeting 
>> recording on this one to verify what the final conclusion was.
>
> I listened to the discussion live. I can go back and double check. But 
> my recollection was that referencing an RFC was brought up. (I think 
> by me.) But there is currently no such RFC, so following that path 
> would entail writing one, and there was no interest in doing that. My 
> understanding was that the decision was to grandfather the registry 
> referencing T.38 even though the rules require reference to an RFC.
>
> But that is the status quo, so it appears to me that no change is 
> required.
>
>>> * Open Issue 8 - Regarding section 8.2.3 ("fmt"):
>>>
>>> The text implies that the namespace for udp formats consists of mime 
>>> types. It says:
>>>
>>>    ... If no media
>>>    subtype exists, it is RECOMMENDED that a suitable one be registered
>>>    through the IETF process [RFC6838] by production of, or reference 
>>> to,
>>>    a standards-track RFC that defines the transport protocol for the
>>>    format.
>>>
>>> But IIUC rfc6838 makes no provision for defining a *transport 
>>> protocol* for a mime type.
>>>
>>> I'm not even entirely sure what rfc4566 intended here. Was it that 
>>> the content of each UDP packet is to conform to the definition of 
>>> the mime type? What about ordering rules that impose requirements on 
>>> sequences of packets?
>>>
>>> Is it intended that the media types suitable for use as udp formats 
>>> are only those that have something special in their definitions? Or 
>>> may any mime type be used if it can fit in a UDP packet?
>> Here is what the minutes say:
>> <quote>
>>
>>      *    Open Issue #8 - Where are media format (“fmt”) 
>> registrations to be
>>          done?
>>     Colin commented that the only “proto” that currently has a
>>     well-defined registration policy (in RFC 3555) are the ones based on
>>     RTP. A discussion concluded to clarify that the media format 
>> namespace
>>     and registration procedures depends on “proto” value and that “fmt”
>>     registration procedures must also be specified when registering a 
>> new
>>     “proto”. Jonathan offered to provide text giving some guidance.
>>     [Action: Jonathan and authors]
>>
>> </quote>
>>
>> I'd prod Jonathan for some text here.
>
> I'll contact Jonathan. But my question was a bigger one than that. My 
> question is what does it *mean* for the fmt for UDP to be a mime type? 
> This was never explained, from the beginning. I *guess* that the 
> intent was that every UDP packet body conform to the mime type. Was 
> that the original intent? Or is the mime type somehow to describe the 
> whole stream of packets?
>
> IOW, it seems to me that the definition of fmt for UDP is 
> underspecified. I would like to complete the specification but don't 
> know what the intent is. I can make something up, but that seems like 
> a bad idea.
>
> I'll also note that I'm not aware of any cases that actually use UDP 
> as transport and a mime type as the fmt.

So Colin, may have a better recollection of those early discussions. 
But, yes I do think that the original intention was to put the subtype 
of the MIME type in the fmt space. However, based on the later 
discussions around use of MIME types I think that is problematic. The 
proto + fmt combination does basically identify a specific transport 
protocol and format to be used. That doesn't match MIME, which is a 
specific format only. We had a long discussion around the MIME type 
usage with RTP, which is much more specific.

What I would do here is to create a SDP specific registry but maintain 
the MIME syntax for any entry, and make it clear that what ever like to 
register here needs to define what foo over UDP is. So specification 
required at least.

/Magnus

>
>
>>> * Open Issue 9 - Regarding section 8.2.5 ("bwtype"):
>>>
>>> The notes say:
>>>
>>> "Check the current IANA registry, did they change the registry and 
>>> update accordingly."
>>>
>>> The registry does now have the mux category, and the entries for CT 
>>> and AS reference both 4566 and mux-attributes.
>>>
>>> AFAICT the only thing to do is update these two registry entries to 
>>> reference this bis rather than 4566. Did I miss anything?
>>>
>>
>> Here is what we have in the minutes:
>> <quote>
>>
>>      *    Open Issue #9 - Should IANA registration of “CT” and “AS” 
>> bandwidth
>>          specifiers be updated to point to 4566bis instead of to RFC 
>> 4566 and
>>     draft-ietf-mmusic-sdp-mux-attributes as today?
>>     Ben C commented that the current text “should be registered” seems
>>     un-enforceable and that the WG should pick a text pointing to one of
>>     the currently defined procedures. This is also applicable to open
>>     issue #7. It was concluded to re-check IANA registry and refine text
>>     in 4566bis accordingly. [Action: Authors]
>>
>> </quote>
>
> Not really. I'll query Ben for more about what he meant.
>
>     Thanks,
>     Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

-- 

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Apr 23 04:09:46 2018
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 72B78127871 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 04:09:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMn_7BRnjRXU for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 04:09: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 0287C12783A for <mmusic@ietf.org>; Mon, 23 Apr 2018 04:09:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524481781; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=z1mZM7Nqk+2MOgSkxwW3aFSFvEx0EX+BATWg2VGdZDc=; b=Mwxl0kBhvExC9J3XQX1NhhdQULHzEfYOSSLUQzUIb43Sm/ExDPuVDxRqnaoq5Sf6 jwjB05OlD3cmvcV94H1ElDsfwV87gc47Byx8oKvg2ag5vFYDTMrOHHKstzUD9wm0 DRXZqNHz8gZrSErJfWjHGr8jdlE8MjUH+M+1veCFuy4=;
X-AuditID: c1b4fb3a-eae319c00000795a-f8-5addbef46325
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 36.69.31066.4FEBDDA5; Mon, 23 Apr 2018 13:09:41 +0200 (CEST)
Received: from [100.94.45.194] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.69) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 23 Apr 2018 13:09:27 +0200
To: Christer Holmberg <christer.holmberg@ericsson.com>, Suhas Nandakumar <suhasietf@gmail.com>
CC: "mmusic@ietf.org" <mmusic@ietf.org>
References: <D6FB9C98.2E1E0%christer.holmberg@ericsson.com> <CAMRcRGT7Kf=GvutamNZZ5Rua3SOgCjoKebjfc6k8cbjHT054ig@mail.gmail.com> <D703578D.2E9A2%christer.holmberg@ericsson.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <3a91f217-3b5e-ffc5-0ab8-03911baebb07@ericsson.com>
Date: Mon, 23 Apr 2018 13:09:27 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <D703578D.2E9A2%christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="------------CDC27604D16E91806908DB33"
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7q+7XfXejDPr3cllMXf6YxWLn3A5m ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStj9ry/TAX7EiqufJ7O2MDY7N7FyMkhIWAi cWLCXdYuRi4OIYEjjBI3z95nhHA2MUrc3bCeEaRKWMBNYt65BWxdjBwcIgIJEmcavUBMZgF1 iauLgyDKtzBKPLm8lw2knE3AQuLmj0Ywm1fAXuL3shWsIDaLgKrE+ddtTCC2qECMxI+jXSwQ NYISJ2c+AbM5BWwkvl9fAVbDLBAmsa9hPZQtLtH0ZSXYHCEBbYmGpg5WiAeUJK7Pu84ygVFw FpJRs5C0z0LSPgvsbHuJB1vLIMLyEs1bZzND2PoS1+/cZ0UWX8DIvopRtDi1uDg33chIL7Uo M7m4OD9PLy+1ZBMjMBoObvlttYPx4HPHQ4wCHIxKPLz9y+5GCbEmlhVX5h5ilOBgVhLh9dgG FOJNSaysSi3Kjy8qzUktPsQozcGiJM7rlGYRJSSQnliSmp2aWpBaBJNl4uCUamCc03zgyLzD m6ef4Sln4AvX9xM51F+unHd19TKJzkdLTv5be51b/LukeLKN+Mt3ugwn3j46lbH1/Y4U8b0X r1oU9eV9OXlp1+f7qkefXNFPmHDxjUzXMuu5MUGlfcE6lstKynK2z5x82eV5jmzp/hkKwscZ o71vLzjybY+DxRruJ8Kmk/9y1vQUKLEUZyQaajEXFScCAEGcZCCCAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_AOd_Xtmi1YsryM0w577r1DR0pE>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 11:09:45 -0000

--------------CDC27604D16E91806908DB33
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit

Hi,

I have to say, that I don't quite understand the reasons for changing 
the ice-options attribute. ECN for RTP's ICE ECN capable path check 
procedure is not a good argument for the need for media level. The 
rtp+ecn option is a session level capability attribute, where the 
a=ecn-capable-rtp attribute indicates which media levels where the path 
shall be checked.

However, if the consensus is to prepare for any potential future option 
that would use media level ICE options, then okay, but it is difficult 
to evaluate the changes without any clear requirements.

However, the draft do need to be updated. I have to agree with Christer, 
the normative 2119 language affecting the rtp+ecn option thus results in 
an updates: RFC 6679. And in addition section 10.2 also seem to update 
or replace the registration rules in RFC 6336. Which of it is needs to 
be made explicit.

And if one is to allow to use rtp+ecn option on media level then I think 
you need to define that better. As ecn+rtp option indicates an endpoint 
capability it is not clear what media level version of that means. You 
will clearly also need to tackle the meaning of the different option in 
an bundle group.

Cheers

Magnus


Den 2018-04-23 kl. 09:12, skrev Christer Holmberg:
> Hi Suhas,
>
> >> Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the ‘ice-options’ attribute 
> as both session- and media-level.
> >>
> >>However, there is no description of what it means to use the attribute on media-level. Does it mean that the 
> indicated ICE extension is only used for that particular media stream?
> >
> > [Suhas] Section 10.2 defines explanation of each ice-options attributes for media-level and session level considerations.
> > https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2
>
> That text is VERY confusing  - especially the stuff about “media-level 
> attributes being MUST be aggregated on session-level”.
>
> Also, the text seems to define such “aggregation rules" for the 
> “rtp+ecn” option. If so, shouldn’t the draft update RFC 6679?
>
> Related to that, the text says that the the “rtp+ecn” option can only 
> be used on session-level if it applies to all media, otherwise it has 
> to be on the media-level. How does that fulfil the “MUST aggregate to 
> session-level” requirement?
>
> Regards,
>
> Christer
>
>
>
>
>     Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16
>     indicates the attribute as session only (“S”).
>
>     Is there a need to define it as media-level attribute?
>
>     Regards,
>
>     Christer
>
>
>     _______________________________________________
>     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

-- 

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


--------------CDC27604D16E91806908DB33
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi,</p>
    <p>I have to say, that I don't quite understand the reasons for
      changing the ice-options attribute. ECN for RTP's ICE ECN capable
      path check procedure is not a good argument for the need for media
      level. The rtp+ecn option is a session level capability attribute,
      where the a=ecn-capable-rtp attribute indicates which media levels
      where the path shall be checked.  <br>
    </p>
    <p>However, if the consensus is to prepare for any potential future
      option that would use media level ICE options, then okay, but it
      is difficult to evaluate the changes without any clear
      requirements. <br>
    </p>
    <p>However, the draft do need to be updated. I have to agree with
      Christer, the normative 2119 language affecting the rtp+ecn option
      thus results in an updates: RFC 6679. And in addition section 10.2
      also seem to update or replace the registration rules in RFC 6336.
      Which of it is needs to be made explicit. <br>
    </p>
    <p>And if one is to allow to use rtp+ecn option on media level then
      I think you need to define that better. As ecn+rtp option
      indicates an endpoint capability it is not clear what media level
      version of that means. You will clearly also need to tackle the
      meaning of the different option in an bundle group. <br>
    </p>
    <p> Cheers</p>
    <p>Magnus<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Den 2018-04-23 kl. 09:12, skrev
      Christer Holmberg:<br>
    </div>
    <blockquote type="cite"
      cite="mid:D703578D.2E9A2%25christer.holmberg@ericsson.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        Hi Suhas,</div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        <br>
      </div>
      <span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0);
        font-family: Calibri, sans-serif; font-size: 14px;">
        <div dir="ltr">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
                <div>&gt;&gt; Section 4.6 of
                  draft-ietf-mmusic-ice-sip-sdp-<wbr>20 defines the
                  ‘ice-options’ attribute as both session- and
                  media-level.</div>
                <div>&gt;&gt;</div>
                <div>&gt;&gt;However, there is no description of what it
                  means to use the attribute on media-level. Does it
                  mean that the indicated ICE extension is only used for
                  that particular media stream?</div>
                <div>&gt;</div>
              </div>
              <div>&gt; [Suhas] Section 10.2 defines explanation of each
                ice-options attributes for media-level and session level
                considerations.</div>
              <div>&gt; <a
href="https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2"
                  moz-do-not-send="true">https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2</a><br>
              </div>
            </div>
          </div>
        </div>
      </span>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        <br>
      </div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        That text is VERY confusing  - especially the stuff about
        “media-level attributes being MUST be aggregated on
        session-level”.</div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        <br>
      </div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        Also, the text seems to define such “aggregation rules" for the
        “rtp+ecn” option. If so, shouldn’t the draft update RFC 6679?</div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        <br>
      </div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        Related to that, the text says that the the “rtp+ecn” option can
        only be used on session-level if it applies to all media,
        otherwise it has to be on the media-level. How does that fulfil
        the “MUST aggregate to session-level” requirement?</div>
      <div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif;
        font-size: 14px;">
        <br>
      </div>
      <div style="orphans: 2; widows: 2;"><font
          face="Calibri,sans-serif">Regards,</font></div>
      <div style="orphans: 2; widows: 2;"><font
          face="Calibri,sans-serif"><br>
        </font></div>
      <div style="orphans: 2; widows: 2;"><font
          face="Calibri,sans-serif">Christer</font></div>
      <div style="orphans: 2; widows: 2;"><font
          face="Calibri,sans-serif"><br>
        </font></div>
      <div style="orphans: 2; widows: 2;"><font
          face="Calibri,sans-serif"><br>
        </font></div>
      <div style="orphans: 2; widows: 2;"><font
          face="Calibri,sans-serif"><br>
        </font></div>
      <span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0);
        font-family: Calibri, sans-serif; font-size: 14px;">
        <div dir="ltr">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <div><br>
              </div>
              <div> </div>
              <blockquote class="gmail_quote" style="margin:0px 0px 0px
                0.8ex;border-left:1px solid
                rgb(204,204,204);padding-left:1ex">
                <div
style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
                  <div>Also, section 5.12 of draft-ietf-mmusic-sdp-mux-<wbr>attributes-16
                    indicates the attribute as session only (“S”).</div>
                  <div><br>
                  </div>
                  <div>Is there a need to define it as media-level
                    attribute?</div>
                  <div><br>
                  </div>
                  <div>Regards,</div>
                  <div><br>
                  </div>
                  <div>Christer</div>
                  <div><br>
                  </div>
                </div>
                <br>
                ______________________________<wbr>_________________<br>
                mmusic mailing list<br>
                <a href="mailto:mmusic@ietf.org" moz-do-not-send="true">mmusic@ietf.org</a><br>
                <a href="https://www.ietf.org/mailman/listinfo/mmusic"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://www.ietf.org/mailman/<wbr>listinfo/mmusic</a><br>
                <br>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </span>
      <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>
    <pre class="moz-signature" cols="72">-- 

Magnus Westerlund 

----------------------------------------------------------------------
Network Architecture &amp; Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class="moz-txt-link-abbreviated" href="mailto:magnus.westerlund@ericsson.com">magnus.westerlund@ericsson.com</a>
----------------------------------------------------------------------</pre>
  </body>
</html>

--------------CDC27604D16E91806908DB33--


From nobody Mon Apr 23 07:59:34 2018
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 E1A1E1270A7 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 07:59:32 -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 cjPEKYBa57pN for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 07:59:30 -0700 (PDT)
Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::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 2E9AE1200E5 for <mmusic@ietf.org>; Mon, 23 Apr 2018 07:59:30 -0700 (PDT)
Received: by mail-ua0-x230.google.com with SMTP id q26so10412162uab.0 for <mmusic@ietf.org>; Mon, 23 Apr 2018 07:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+mKJag6uiNwF7OEDqLcgaQ+kqJ54FB4ads9x6L/tGNE=; b=aE8EXqBNoLD8av+MovI33E5dZx9ukaRFQatAGjpwklrzxwXUfiA1/f03rVDe/mfXnl k8MrQj11/Qwcdd98syw6sZgMP+iAPzSZtK3sNUiHx6Zm1Td11nssPcow8Cb5uIa2JY8s Qm4/BrWUUEcB7ZaO45OMQO1Q2z3h6bRkiCWVU+i3DqQCpYzFyVis46r2L1XlEleuCsK3 0flFq5oquEGw5E7oltPBYpcbYSU3Kd12ghiJ02+e5nUxC4phAYcHDfBqRkAOB7z3gXr0 E84EhHNq0/ndSmFxXwOAQv+cW19MZCYRseiVx2FecDrVz3hpCMPmo7LyFmcok9ODbBZ+ 0fAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+mKJag6uiNwF7OEDqLcgaQ+kqJ54FB4ads9x6L/tGNE=; b=FJDWvh8AfvdYxQMB1yz000YwG6AZHjpcE2tK+YFfsWMmxcOwTBFlBUeqSCUFu7VNzo 3GUOvhNFY2od9UwVgO01MwiqHAV+fPXZrFVOBCd764q5iJ6iOQbjis06gLIs0o5iWY7n pfKg5PO/fwAdosgkH/BUw1u5tLaHns+At1UDopzFcIBmnXPHULMpuZWLxQh/DtHvu88i cl+tfIIkwt4pB+Ql9cwwsc2ujuHI3CDn8Ul3MUsVwIoBU4rzYgZeWg1Hk7zrqlRpwddR Gz79kB+fENjdHkBJnGYO5oUB7zW+f6vRUiZDUpgkqKQeEvMpCttj37BcaGokGoRGyQTT RnWQ==
X-Gm-Message-State: ALQs6tAsYP9gLeRzH0t6KRd98/o1TVJfXt8gZtdsoPY25b56kQr+CEX/ qyD1nfaPz5AIkBUCrH88sr0+76PGDMX+s2qvTio=
X-Google-Smtp-Source: AIpwx4+7HCITQePI23g7csnxIEDm7tyrmvpMkKN1opY3RH1QjGS3ics1Z4P/w3O7EmuQouA1lYlYLgaDp+v04d1YrR8=
X-Received: by 10.176.71.7 with SMTP id h7mr15797839uac.11.1524495569260; Mon, 23 Apr 2018 07:59:29 -0700 (PDT)
MIME-Version: 1.0
References: <D6FB9C98.2E1E0%christer.holmberg@ericsson.com> <CAMRcRGT7Kf=GvutamNZZ5Rua3SOgCjoKebjfc6k8cbjHT054ig@mail.gmail.com> <D703578D.2E9A2%christer.holmberg@ericsson.com> <3a91f217-3b5e-ffc5-0ab8-03911baebb07@ericsson.com>
In-Reply-To: <3a91f217-3b5e-ffc5-0ab8-03911baebb07@ericsson.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Mon, 23 Apr 2018 14:59:18 +0000
Message-ID: <CAMRcRGSjf2baM7XUDW1NAzqhUMyp2q_gxRvs9pqg6-1XKm3M9w@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="f403045e6248de1604056a854827"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RbTsGKh-KJGF0Kz2ia-cH88WnIo>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 14:59:33 -0000

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

Thanks for the responses Magnus and Christer.
The more I think about it, the more I am confused on having a media level
option.

Unfortunately, this section predatesme joining as a co-author and hence
Marc/Ari might have a better reasoning.

We can wait on them to respond or can go with session level only
ice-options and write a new spec if we decide a media level version is
needed in the future

Cheers
Suhas

On Mon, Apr 23, 2018 at 4:09 AM Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Hi,
>
> I have to say, that I don't quite understand the reasons for changing the
> ice-options attribute. ECN for RTP's ICE ECN capable path check procedure
> is not a good argument for the need for media level. The rtp+ecn option i=
s
> a session level capability attribute, where the a=3Decn-capable-rtp attri=
bute
> indicates which media levels where the path shall be checked.
>
> However, if the consensus is to prepare for any potential future option
> that would use media level ICE options, then okay, but it is difficult to
> evaluate the changes without any clear requirements.
>
> However, the draft do need to be updated. I have to agree with Christer,
> the normative 2119 language affecting the rtp+ecn option thus results in =
an
> updates: RFC 6679. And in addition section 10.2 also seem to update or
> replace the registration rules in RFC 6336. Which of it is needs to be ma=
de
> explicit.
>
> And if one is to allow to use rtp+ecn option on media level then I think
> you need to define that better. As ecn+rtp option indicates an endpoint
> capability it is not clear what media level version of that means. You wi=
ll
> clearly also need to tackle the meaning of the different option in an
> bundle group.
>
> Cheers
>
> Magnus
>
> Den 2018-04-23 kl. 09:12, skrev Christer Holmberg:
>
> Hi Suhas,
>
> >> Section 4.6 of draft-ietf-mmusic-ice-sip-sdp-20 defines the
> =E2=80=98ice-options=E2=80=99 attribute as both session- and media-level.
> >>
> >>However, there is no description of what it means to use the attribute
> on media-level. Does it mean that the indicated ICE extension is only use=
d
> for that particular media stream?
> >
> > [Suhas] Section 10.2 defines explanation of each ice-options attributes
> for media-level and session level considerations.
> >
> https://tools.ietf.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2
>
> That text is VERY confusing  - especially the stuff about =E2=80=9Cmedia-=
level
> attributes being MUST be aggregated on session-level=E2=80=9D.
>
> Also, the text seems to define such =E2=80=9Caggregation rules" for the =
=E2=80=9Crtp+ecn=E2=80=9D
> option. If so, shouldn=E2=80=99t the draft update RFC 6679?
>
> Related to that, the text says that the the =E2=80=9Crtp+ecn=E2=80=9D opt=
ion can only be
> used on session-level if it applies to all media, otherwise it has to be =
on
> the media-level. How does that fulfil the =E2=80=9CMUST aggregate to sess=
ion-level=E2=80=9D
> requirement?
>
> Regards,
>
> Christer
>
>
>
>
>
>
>> Also, section 5.12 of draft-ietf-mmusic-sdp-mux-attributes-16 indicates
>> the attribute as session only (=E2=80=9CS=E2=80=9D).
>>
>> Is there a need to define it as media-level attribute?
>>
>> Regards,
>>
>> Christer
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>
>
> _______________________________________________
> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/m=
music
>
>
> --
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Network Architecture & Protocols, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287Torshamnsgatan 23 <htt=
ps://maps.google.com/?q=3DTorshamnsgatan+23&entry=3Dgmail&source=3Dg>      =
     | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>

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

<div><div dir=3D"auto">Thanks for the responses Magnus and Christer.=C2=A0<=
/div><div dir=3D"auto">The more I think about it, the more I am confused on=
 having a media level option.</div><div dir=3D"auto"><br></div><div dir=3D"=
auto">Unfortunately, this section predatesme joining as a co-author and hen=
ce Marc/Ari might have a better reasoning.</div><div dir=3D"auto"><br></div=
><div dir=3D"auto">We can wait on them to respond or can go with session le=
vel only ice-options and write a new spec if we decide a media level versio=
n is needed in the future=C2=A0</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Cheers</div><div dir=3D"auto">Suhas=C2=A0</div><br><div class=3D"=
gmail_quote"><div>On Mon, Apr 23, 2018 at 4:09 AM Magnus Westerlund &lt;<a =
href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@ericsson.c=
om</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi,</p>
    <p>I have to say, that I don&#39;t quite understand the reasons for
      changing the ice-options attribute. ECN for RTP&#39;s ICE ECN capable
      path check procedure is not a good argument for the need for media
      level. The rtp+ecn option is a session level capability attribute,
      where the a=3Decn-capable-rtp attribute indicates which media levels
      where the path shall be checked.=C2=A0 <br>
    </p>
    <p>However, if the consensus is to prepare for any potential future
      option that would use media level ICE options, then okay, but it
      is difficult to evaluate the changes without any clear
      requirements. <br>
    </p>
    <p>However, the draft do need to be updated. I have to agree with
      Christer, the normative 2119 language affecting the rtp+ecn option
      thus results in an updates: RFC 6679. And in addition section 10.2
      also seem to update or replace the registration rules in RFC 6336.
      Which of it is needs to be made explicit. <br>
    </p>
    <p>And if one is to allow to use rtp+ecn option on media level then
      I think you need to define that better. As ecn+rtp option
      indicates an endpoint capability it is not clear what media level
      version of that means. You will clearly also need to tackle the
      meaning of the different option in an bundle group. <br>
    </p>
    <p> Cheers</p>
    <p>Magnus<br>
    </p></div><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    <div class=3D"m_5094747274881209827moz-cite-prefix">Den 2018-04-23 kl. =
09:12, skrev
      Christer Holmberg:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        Hi Suhas,</div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        <br>
      </div>
      <span id=3D"m_5094747274881209827OLK_SRC_BODY_SECTION" style=3D"color=
:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
        <div>
          <div class=3D"gmail_extra">
            <div class=3D"gmail_quote">
              <div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size=
:14px;font-family:Calibri,sans-serif">
                <div>&gt;&gt; Section 4.6 of
                  draft-ietf-mmusic-ice-sip-sdp-20 defines the
                  =E2=80=98ice-options=E2=80=99 attribute as both session- =
and
                  media-level.</div>
                <div>&gt;&gt;</div>
                <div>&gt;&gt;However, there is no description of what it
                  means to use the attribute on media-level. Does it
                  mean that the indicated ICE extension is only used for
                  that particular media stream?</div>
                <div>&gt;</div>
              </div>
              <div>&gt; [Suhas] Section 10.2 defines explanation of each
                ice-options attributes for media-level and session level
                considerations.</div>
              <div>&gt;=C2=A0<a href=3D"https://tools.ietf.org/html/draft-i=
etf-mmusic-ice-sip-sdp-20#section-10.2" target=3D"_blank">https://tools.iet=
f.org/html/draft-ietf-mmusic-ice-sip-sdp-20#section-10.2</a><br>
              </div>
            </div>
          </div>
        </div>
      </span>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        <br>
      </div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        That text is VERY confusing =C2=A0- especially the stuff about
        =E2=80=9Cmedia-level attributes being MUST be aggregated on
        session-level=E2=80=9D.</div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        <br>
      </div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        Also, the text seems to define such =E2=80=9Caggregation rules&quot=
; for the
        =E2=80=9Crtp+ecn=E2=80=9D option. If so, shouldn=E2=80=99t the draf=
t update RFC 6679?</div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        <br>
      </div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        Related to that, the text says that the the =E2=80=9Crtp+ecn=E2=80=
=9D option can
        only be used on session-level if it applies to all media,
        otherwise it has to be on the media-level. How does that fulfil
        the =E2=80=9CMUST aggregate to session-level=E2=80=9D requirement?<=
/div>
      <div style=3D"color:rgb(0,0,0);font-family:Calibri,sans-serif;font-si=
ze:14px">
        <br>
      </div>
      <div><font face=3D"Calibri,sans-serif">Regards,</font></div>
      <div><font face=3D"Calibri,sans-serif"><br>
        </font></div>
      <div><font face=3D"Calibri,sans-serif">Christer</font></div>
      <div><font face=3D"Calibri,sans-serif"><br>
        </font></div>
      <div><font face=3D"Calibri,sans-serif"><br>
        </font></div>
      <div><font face=3D"Calibri,sans-serif"><br>
        </font></div>
      <span id=3D"m_5094747274881209827OLK_SRC_BODY_SECTION" style=3D"color=
:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">
        <div>
          <div class=3D"gmail_extra">
            <div class=3D"gmail_quote">
              <div><br>
              </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 style=3D"word-wrap:break-word;color:rgb(0,0,0);font-si=
ze:14px;font-family:Calibri,sans-serif">
                  <div>Also, section 5.12 of=C2=A0draft-ietf-mmusic-sdp-mux=
-attributes-16
                    indicates the attribute as session only (=E2=80=9CS=E2=
=80=9D).</div>
                  <div><br>
                  </div>
                  <div>Is there a need to define it as media-level
                    attribute?</div>
                  <div><br>
                  </div>
                  <div>Regards,</div>
                  <div><br>
                  </div>
                  <div>Christer</div>
                  <div><br>
                  </div>
                </div>
                <br>
                _______________________________________________<br>
                mmusic mailing list<br>
                <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic=
@ietf.org</a><br>
                <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" re=
l=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mm=
usic</a><br>
                <br>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </span>
      <br>
      <fieldset class=3D"m_5094747274881209827mimeAttachmentHeader"></field=
set>
      <br>
      <pre>_______________________________________________
mmusic mailing list
<a class=3D"m_5094747274881209827moz-txt-link-abbreviated" href=3D"mailto:m=
music@ietf.org" target=3D"_blank">mmusic@ietf.org</a>
<a class=3D"m_5094747274881209827moz-txt-link-freetext" href=3D"https://www=
.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">https://www.ietf.org/m=
ailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
    </div><div text=3D"#000000" bgcolor=3D"#FFFFFF"><pre class=3D"m_5094747=
274881209827moz-signature" cols=3D"72">--=20

Magnus Westerlund=20

----------------------------------------------------------------------
Network Architecture &amp; Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
<a href=3D"https://maps.google.com/?q=3DTorshamnsgatan+23&amp;entry=3Dgmail=
&amp;source=3Dg">Torshamnsgatan 23</a>           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"m_5094747274881209827moz-=
txt-link-abbreviated" href=3D"mailto:magnus.westerlund@ericsson.com" target=
=3D"_blank">magnus.westerlund@ericsson.com</a>
----------------------------------------------------------------------</pre=
>
  </div>

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

--f403045e6248de1604056a854827--


From nobody Mon Apr 23 08:36:43 2018
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 03E1E12D777 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 08:36:42 -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 jIXEEounoCyQ for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 08:36:40 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (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 AD1CD1205D3 for <mmusic@ietf.org>; Mon, 23 Apr 2018 08:36:40 -0700 (PDT)
Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id Aafdf9zFSsMEoAdWBfdiez; Mon, 23 Apr 2018 15:36:39 +0000
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-04v.sys.comcast.net with ESMTPA id AdW8fMDM6ZIKaAdW9fC2Cc; Mon, 23 Apr 2018 15:36:38 +0000
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Flemming Andreasen <fandreas@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>, Colin Perkins <csp@csperkins.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu> <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <de456926-ef1a-4e99-813c-19d7b9995d18@alum.mit.edu>
Date: Mon, 23 Apr 2018 11:36:36 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfHmsVLhFzh708NQTki75IXf1zWlr2lfOPkWyCJ3R6oO3SaN0DKt+miJg4vpYZCMXl71RVEPX2xhAQD+Pthoi0krvUSzr80zyiCT4kDiS1bKRxOjKmyrq 6CSu8xtHOUIweWlvAIff1m2MXYjbtPLoWNR7x3oxNrCgBBIHLygXZt4xmQ7sHdWfonaRLFqkdkgVafrYBoqZzR/v51kLLWvEmpWcaU9zBz3o7LNiPwAzlnS/ mhXlU/RjtjG8KJJd7n/LVMDbOX6gmp0ILYtfAiNymfPAjTIi04Jlibe+Yvod6P/OkHiVfnb2szzDVDwBeh2t1Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gHAVH-2IJAUilGZuF-keiaBfuuk>
Subject: [MMUSIC] Meaning of fmt when proto is UDP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 15:36:42 -0000

Magnus, Colin, Flemming, and others,

On 4/23/18 4:07 AM, Magnus Westerlund wrote:

>> ... But my question was a bigger one than that. My 
>> question is what does it *mean* for the fmt for UDP to be a mime type? 
>> This was never explained, from the beginning. I *guess* that the 
>> intent was that every UDP packet body conform to the mime type. Was 
>> that the original intent? Or is the mime type somehow to describe the 
>> whole stream of packets?
>>
>> IOW, it seems to me that the definition of fmt for UDP is 
>> underspecified. I would like to complete the specification but don't 
>> know what the intent is. I can make something up, but that seems like 
>> a bad idea.
>>
>> I'll also note that I'm not aware of any cases that actually use UDP 
>> as transport and a mime type as the fmt.
> 
> So Colin, may have a better recollection of those early discussions. 
> But, yes I do think that the original intention was to put the subtype 
> of the MIME type in the fmt space. However, based on the later 
> discussions around use of MIME types I think that is problematic. The 
> proto + fmt combination does basically identify a specific transport 
> protocol and format to be used. That doesn't match MIME, which is a 
> specific format only. We had a long discussion around the MIME type 
> usage with RTP, which is much more specific.
> 
> What I would do here is to create a SDP specific registry but maintain 
> the MIME syntax for any entry, and make it clear that what ever like to 
> register here needs to define what foo over UDP is. So specification 
> required at least.
> 
> /Magnus
That seems like a prudent direction to take. But it also seems like 
something well in excess of a simple editorial action. I can propose 
something, but I would think it would deserve some serious discussion in 
the WG. (If it is possible to find enough people to have that discussion.)

The things that I can recall that use UDP have all chosen to define a 
new proto value and then specify how to use fmt with that.

Are there *any* cases of RFCs where a proto of UDP is used with a mime 
subtype as fmt? Maybe we could simply deprecate this usage.

	Thanks,
	Paul


From nobody Mon Apr 23 09:33:49 2018
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 81D8912D7F6 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 09:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRibYdu7D1jZ for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 09:33:45 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 711F612D80F for <mmusic@ietf.org>; Mon, 23 Apr 2018 09:33:40 -0700 (PDT)
Received: from [81.187.2.149] (port=48091 helo=[192.168.0.71]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1fAePG-0004Zh-AG; Mon, 23 Apr 2018 17:33:36 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <de456926-ef1a-4e99-813c-19d7b9995d18@alum.mit.edu>
Date: Mon, 23 Apr 2018 17:33:24 +0100
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Flemming Andreasen <fandreas@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>, Jonathan Lennox <jonathan@vidyo.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9B15009-10B5-4FA1-9AD2-457B7693F073@csperkins.org>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu> <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com> <de456926-ef1a-4e99-813c-19d7b9995d18@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5tEWZgprB4QCpIC3FmcZNey1NKg>
Subject: Re: [MMUSIC] Meaning of fmt when proto is UDP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 16:33:47 -0000

Paul,

> On 23 Apr 2018, at 16:36, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> Magnus, Colin, Flemming, and others,
>=20
> On 4/23/18 4:07 AM, Magnus Westerlund wrote:
>=20
>>> ... But my question was a bigger one than that. My question is what =
does it *mean* for the fmt for UDP to be a mime type? This was never =
explained, from the beginning. I *guess* that the intent was that every =
UDP packet body conform to the mime type. Was that the original intent? =
Or is the mime type somehow to describe the whole stream of packets?

The contents of each UDP packet have to conform to the signalled media =
type. This is exactly the same as when RTP is used, where the contents =
of every RTP packet have to conform to the signalled media type (i.e., =
the RTP payload format).=20

>>> IOW, it seems to me that the definition of fmt for UDP is =
underspecified. I would like to complete the specification but don't =
know what the intent is. I can make something up, but that seems like a =
bad idea.
>>>=20
>>> I'll also note that I'm not aware of any cases that actually use UDP =
as transport and a mime type as the fmt.
>> So Colin, may have a better recollection of those early discussions. =
But, yes I do think that the original intention was to put the subtype =
of the MIME type in the fmt space. However, based on the later =
discussions around use of MIME types I think that is problematic. The =
proto + fmt combination does basically identify a specific transport =
protocol and format to be used. That doesn't match MIME, which is a =
specific format only. We had a long discussion around the MIME type =
usage with RTP, which is much more specific.
>> What I would do here is to create a SDP specific registry but =
maintain the MIME syntax for any entry, and make it clear that what ever =
like to register here needs to define what foo over UDP is. So =
specification required at least.
>> /Magnus
> That seems like a prudent direction to take. But it also seems like =
something well in excess of a simple editorial action. I can propose =
something, but I would think it would deserve some serious discussion in =
the WG. (If it is possible to find enough people to have that =
discussion.)
>=20
> The things that I can recall that use UDP have all chosen to define a =
new proto value and then specify how to use fmt with that.
>=20
> Are there *any* cases of RFCs where a proto of UDP is used with a mime =
subtype as fmt? Maybe we could simply deprecate this usage.


SDP specifies the transport protocol and the data format that=E2=80=99s =
conveyed within that transport protocol. The transport protocol is =
identified by the =E2=80=9Cproto=E2=80=9D field. The data format is =
identified by the combination of the media type (=E2=80=9Cmedia=E2=80=9D) =
and the subtype (=E2=80=9Cfmt=E2=80=9D).

For RTP, the fmt field references a media subtype indirectly:

	m=3Dvideo 51372 RTP/AVP 99
	a=3Drtpmap:99 h263-1998/90000

Here the transport is =E2=80=9CRTP/AVP" and the media type is =
=E2=80=9Cvideo/h263-1990; rate=3D90000=E2=80=9D. RFC 3555 describes the =
process for mapping media type names and parameters onto SDP using the =
combination of =E2=80=9Ca=3Drtpmap:=E2=80=9D, =E2=80=9Ca=3Dptime:=E2=80=9D=
, =E2=80=9Ca=3Dmaxptime:=E2=80=9D,  and =E2=80=9Ca=3Dfmtp:=E2=80=9D =
lines.=20

For UDP, the fmt directly references a media subtype:

	m=3Dapplication 10000 udp foo

In this case, the media type is =E2=80=9Capplication/foo=E2=80=9D, and =
the UDP packets contain data that is formatted as described in the media =
type registration for "application/foo=E2=80=9D. We don=E2=80=99t need =
an SDP specific registry: it=E2=80=99s just a standard media type =
registration, presumably with a note in its Encoding Considerations =
section to the effect that =E2=80=9CThis media type is only defined for =
transmission over UDP=E2=80=9D.=20

What seems to be missing in RFC 4566 is a statement that =E2=80=9Ca=3Dfmtp=
:=E2=80=9D parameters can be used to convey media type parameters for =
media formats sent over UDP.=20

For other transport protocols, the registration of the =E2=80=9Cproto=E2=80=
=9D value denoting the transport states whether media types are used to =
describe the payload with that transport too, or whether the =E2=80=9Cfmt=E2=
=80=9D namespace is managed differently. It would likely be a good idea =
to say that new protocols SHOULD use the media type namespace, for =
consistency, but there=E2=80=99s nothing in SDP that requires they do =
so.

Using UDP as the transport doesn=E2=80=99t seem especially useful, since =
in most cases I=E2=80=99d expect some additional framing to be needed to =
allow loss or reordering to be detected, but it seems conceptually well =
specified (although perhaps the text could be clearer in places). I =
don=E2=80=99t think deprecating UDP as a transport is appropriate, =
although clarifying when it should be used might be a good idea.

Colin




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





From nobody Mon Apr 23 09:45:27 2018
Return-Path: <marc@petit-huguenin.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 7CD9312D871 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 09:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, 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 FMC0wnG0Djtw for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 09:45:24 -0700 (PDT)
Received: from implementers.org (unknown [IPv6:2001:4b98:dc0:45:216:3eff:fe7f:7abd]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BECBE12D86A for <mmusic@ietf.org>; Mon, 23 Apr 2018 09:45:24 -0700 (PDT)
Received: from [IPv6:2601:648:8301:730f:fdb6:1cc8:478a:5b55] (unknown [IPv6:2601:648:8301:730f:fdb6:1cc8:478a:5b55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 4BDA0AE844; Mon, 23 Apr 2018 18:45:21 +0200 (CEST)
To: Suhas Nandakumar <suhasietf@gmail.com>, Peter Saint-Andre <stpeter@mozilla.com>
Cc: mmusic WG <mmusic@ietf.org>
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com> <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com> <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com> <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com>
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
Message-ID: <9865a04c-312c-1a81-7f96-5baa237f3d55@petit-huguenin.org>
Date: Mon, 23 Apr 2018 09:45:14 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2SVQOscErh7Wl5UZygxPLGLclFQX83LF3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bnsEY0stmEBYjUX732R-xMJWg5k>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 16:45:26 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2SVQOscErh7Wl5UZygxPLGLclFQX83LF3
Content-Type: multipart/mixed; boundary="udJyE6vwcjud0RK0JpV3FNK1BhKUKSPqs";
 protected-headers="v1"
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Suhas Nandakumar <suhasietf@gmail.com>,
 Peter Saint-Andre <stpeter@mozilla.com>
Cc: mmusic WG <mmusic@ietf.org>
Message-ID: <9865a04c-312c-1a81-7f96-5baa237f3d55@petit-huguenin.org>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com>
 <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com>
 <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com>
 <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com>
In-Reply-To: <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com>

--udJyE6vwcjud0RK0JpV3FNK1BhKUKSPqs
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

This was done as a consequence of merging this draft in ice-bis:

https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-ice-attributes=
-level-04.txt

There is probably discussions that can be found in the minutes of IETF me=
etings around that time when the WG agreed to that modification.

On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:
> I am fine with considering ice-options has session level too. I wonder =
if
> Marc can chime in on considering it as  media level in the ice-sip-sdp.=

>=20
> On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre <stpeter@mozilla.co=
m>
> wrote:
>=20
>> On 4/20/18 12:37 PM, Roman Shpount wrote:
>>> Hi All,
>>>
>>> I do not think ice-options was ever used as a media level attribute.
>>> Only two ice-options defined in IANA registry
>>> (https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and  rtp+ec=
n,
>>> which are both session level.
>>>
>>> Furthermore, RFC 5245 section 15.5
>>> (https://tools.ietf.org/html/rfc5245#section-15.5,) defined that
>>> ice-options attribute is session level only. Thus, ice-options should=
 be
>>> kept session level for backwards compatibility.
>>>
>>> If something more granular then session is needed, I think it should =
go
>>> into candidate extension attribute, not into media level ice-options.=

>>>
>>> Bottom line, I think ice-options should be a a session level only
>> attribute.
>>
>> Agreed.
>>
>> In the Trickle ICE spec, we also limited the `trickle` option to sessi=
on
>> level only.
>>
>> Peter
>>
>>


--=20
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


--udJyE6vwcjud0RK0JpV3FNK1BhKUKSPqs--

--2SVQOscErh7Wl5UZygxPLGLclFQX83LF3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEBSI+IuCHU8MsI1GjKcRFldZqfsQFAlreDZ4ACgkQKcRFldZq
fsR3pA/9HvySikGyOOhtiRiRxWEF/SRMcmahtdHVwvHt3rSyvXO0yYW35C5qkw0l
mvg4Ihk/C9b5Ufq3e6kzcZ/gY3dJhrSShEz5pdX1Hw6JCs9KNpZivkPsIIOTw1Sh
68fGI2IibPGnn0IiaU9pvoNUWFWsSobxOQssCaCgSc41CY4UIm3mgS6sp/b2gT/V
aiO8naRUneKTcjoTtTBaYRZiiULk0J47OVLL7fMH6rJY6LbIEGXqgzgU4ehhQDhI
nCfvXtSwtM1ML3/Nc+n2WUBcEtFUBzhS4vTPgeCH0R90DtElJbuHIUTN+ngjpaCs
708ww3F8YX70MgER1/GEZHeSKcfnHRDesTWNxW8Y2vsCt5cyiU/IvB27R4gH5hjG
Zn/vHIhrYeyFwxybk2fSC1pp6cXerq05Vm+P27ZvhSghJvq/gxRndzGd+qUppDna
55CHh9bbIVJyPXZ3YD6fXaCvl7XYiXSwCZuoAUXYxCrXeRi+HQDSm9HNevAfU3f5
JTwnuh+tcOFj31tSoqL3P17zqKQy17SEMAXVW4hoVS56eQBwcG04oAK2Ac7cfHBB
slRkyT9qt/PY4CaUKj4d+8MuNtIr7AWt+qRn3+ryuxxaTSQVkwZTaV2t5s1wpeiT
0b0mdonrfqXF25RXVFZvSAMo9RuEmGKESASozeQCJ3KblCHJB78=
=cb0u
-----END PGP SIGNATURE-----

--2SVQOscErh7Wl5UZygxPLGLclFQX83LF3--


From nobody Mon Apr 23 10:03:54 2018
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 27C2F12D7F1 for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 10:03:53 -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, T_DKIMWL_WL_MED=-0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fjsAHnsFSCjy for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 10:03:49 -0700 (PDT)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e: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 0D33912D87A for <mmusic@ietf.org>; Mon, 23 Apr 2018 10:03:49 -0700 (PDT)
Received: by mail-pg0-x22d.google.com with SMTP id a13so4354756pgu.4 for <mmusic@ietf.org>; Mon, 23 Apr 2018 10:03:49 -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=LRtWcUNlYxPdG2qTalS9ul3mlrfg9V17VIask71oiuM=; b=BUPrv6Zj5tH+hjhQsTKjxYgEVGYx3UKnDpdXXlQZiUMvmYfrz+Bg4F9Z1pCxabtTcA FQJs3Wk+RZZJYxV/bHgIlROH7DjBUCQpxuDqP4UCYPi5C1yY4UNg+IeMS5YQ7BZcEIfR JFEwclRDFjexTA4sK9j1E5rwBQEWvjMl6KZH7YJnpcH3f69hPQfAhfRXD/TaBXwLZC0U 9L4I4vDhn/b+BH3rV1zM8zKwyUMZfvI1ghQFEwCY4fZp2SWIlOL6M8yMvmGmuF2A4qD0 btLT/u7B+0fGzPfYZeLBxxB7EndbIKaQeDi1yGFVbFu3sKeoP5yFtYs+ETYLJHm4DecQ Gumg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LRtWcUNlYxPdG2qTalS9ul3mlrfg9V17VIask71oiuM=; b=YAWyUhOgHd3zn/4Q9nGGOROLHuK8mO26NPnfSmld6VIeHNTelmsJqICKJjgXVGnxYn ow1aCCFYCsZe6PGtO2GhCrFRQIzwseKa7wtKI4RDlP5WMTXGzIZEefEYy+G3hINecKii ECPdYbRPxw6x0PylmtMsm+m9C8IaDSFelGFn0zEel6Ag9BRRo9HdwedVDWinpRIJeDV1 ksZbfDNBxf38HexUSe5Y7Y3gAp2bO0mlOCIHmswI2Qso4ZK7EmzIAaSA7SZGd4G3dIKx JTQgA9GAwTIG4UuqB4GJs8hw4O1ok1vaj/zF+xBnlbI5MMHvQqIlv+2XUzmDxYnw7Lg4 WY1A==
X-Gm-Message-State: ALQs6tDpcb2KmDhJUrlSxfSSb1k38Er+FhvFFz+04AKqUzp38fSSrc/U 95yKCVXwSpC1aNv69Oay6B6L8ajS
X-Google-Smtp-Source: AIpwx4/Z91Zz836GAwbYiFNGmErbYRiM7F6WjbftS36d0SPV7oYgXdYW/SHgUDy8vxUe/DOEEHg78g==
X-Received: by 10.99.94.197 with SMTP id s188mr17592403pgb.21.1524503028232; Mon, 23 Apr 2018 10:03:48 -0700 (PDT)
Received: from mail-pg0-f46.google.com (mail-pg0-f46.google.com. [74.125.83.46]) by smtp.gmail.com with ESMTPSA id s65sm34657961pfj.124.2018.04.23.10.03.47 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Apr 2018 10:03:47 -0700 (PDT)
Received: by mail-pg0-f46.google.com with SMTP id f132so8800070pgc.10 for <mmusic@ietf.org>; Mon, 23 Apr 2018 10:03:47 -0700 (PDT)
X-Received: by 2002:a17:902:4003:: with SMTP id b3-v6mr21165636pld.15.1524503027192;  Mon, 23 Apr 2018 10:03:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.149.74 with HTTP; Mon, 23 Apr 2018 10:03:46 -0700 (PDT)
In-Reply-To: <9865a04c-312c-1a81-7f96-5baa237f3d55@petit-huguenin.org>
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com> <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com> <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com> <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com> <9865a04c-312c-1a81-7f96-5baa237f3d55@petit-huguenin.org>
From: Roman Shpount <roman@telurix.com>
Date: Mon, 23 Apr 2018 13:03:46 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt+1OspnDEOx9LvmPOZDsAUP+neypPWbuc0cA0ECx_tow@mail.gmail.com>
Message-ID: <CAD5OKxt+1OspnDEOx9LvmPOZDsAUP+neypPWbuc0cA0ECx_tow@mail.gmail.com>
To: Marc Petit-Huguenin <marc@petit-huguenin.org>
Cc: Suhas Nandakumar <suhasietf@gmail.com>, Peter Saint-Andre <stpeter@mozilla.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000065184b056a870535"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/7qRMb0RJlW7tdBncJ_sh7rASrBU>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 23 Apr 2018 17:03:53 -0000

--00000000000065184b056a870535
Content-Type: text/plain; charset="UTF-8"

Hi All,

I would prefer disaggregated media to be handled separately and keep
ice-options a session level attribute. Dealing with disaggregated media is
a much bigger issue then just adjusting ice-options. For instance, why
ice-options are handled there and ice-lite is excluded? I think ice-lite is
potentially as big of the problem when aggregating media from several
sources. Also, I we sure that making singe ICE agent dealing with two
independent ICE agents does not have any issues? I do not think this was
examined in sufficient detail.

Furthermore, it is possible to define per ICE candidate specific parameters
using ICE candidate extension attributes. I think it would be cleaner to
define things which are specific to only some candidates using this
mechanism vs medial level ice-options.

Regards,

_____________
Roman Shpount

On Mon, Apr 23, 2018 at 12:45 PM, Marc Petit-Huguenin <
marc@petit-huguenin.org> wrote:

> This was done as a consequence of merging this draft in ice-bis:
>
> https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-
> ice-attributes-level-04.txt
>
> There is probably discussions that can be found in the minutes of IETF
> meetings around that time when the WG agreed to that modification.
>
> On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:
> > I am fine with considering ice-options has session level too. I wonder if
> > Marc can chime in on considering it as  media level in the ice-sip-sdp.
> >
> > On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre <stpeter@mozilla.com
> >
> > wrote:
> >
> >> On 4/20/18 12:37 PM, Roman Shpount wrote:
> >>> Hi All,
> >>>
> >>> I do not think ice-options was ever used as a media level attribute.
> >>> Only two ice-options defined in IANA registry
> >>> (https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and
> rtp+ecn,
> >>> which are both session level.
> >>>
> >>> Furthermore, RFC 5245 section 15.5
> >>> (https://tools.ietf.org/html/rfc5245#section-15.5,) defined that
> >>> ice-options attribute is session level only. Thus, ice-options should
> be
> >>> kept session level for backwards compatibility.
> >>>
> >>> If something more granular then session is needed, I think it should go
> >>> into candidate extension attribute, not into media level ice-options.
> >>>
> >>> Bottom line, I think ice-options should be a a session level only
> >> attribute.
> >>
> >> Agreed.
> >>
> >> In the Trickle ICE spec, we also limited the `trickle` option to session
> >> level only.
> >>
> >> Peter
> >>
> >>
>
>
> --
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: https://marc.petit-huguenin.org
> Profile: https://www.linkedin.com/in/petithug
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr">Hi All,<div><br></div><div>I would prefer disaggregated me=
dia to be handled separately and keep ice-options a session level attribute=
. Dealing with disaggregated media is a much bigger issue then just adjusti=
ng ice-options. For instance, why ice-options are handled there and ice-lit=
e is excluded? I think ice-lite is potentially as big of the problem when a=
ggregating media from several sources. Also, I we sure that making singe IC=
E agent dealing with two independent ICE agents does not have any issues? I=
 do not think this was examined in sufficient detail.=C2=A0</div><div><br><=
/div><div>Furthermore, it is possible to define per ICE candidate specific =
parameters using ICE candidate extension attributes. I think it would be cl=
eaner to define things which are specific to only some candidates using thi=
s mechanism vs medial level ice-options.</div><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 =
Shpount</div></div>
<br><div class=3D"gmail_quote">On Mon, Apr 23, 2018 at 12:45 PM, Marc Petit=
-Huguenin <span dir=3D"ltr">&lt;<a href=3D"mailto:marc@petit-huguenin.org" =
target=3D"_blank">marc@petit-huguenin.org</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">This was done as a consequence of merging this draft=
 in ice-bis:<br>
<br>
<a href=3D"https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-ice-a=
ttributes-level-04.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/archive/<wbr>id/draft-petithuguenin-mmusic-<wbr>ice-attributes-level=
-04.txt</a><br>
<br>
There is probably discussions that can be found in the minutes of IETF meet=
ings around that time when the WG agreed to that modification.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:<br>
&gt; I am fine with considering ice-options has session level too. I wonder=
 if<br>
&gt; Marc can chime in on considering it as=C2=A0 media level in the ice-si=
p-sdp.<br>
&gt; <br>
&gt; On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre &lt;<a href=3D"mai=
lto:stpeter@mozilla.com">stpeter@mozilla.com</a>&gt;<br>
&gt; wrote:<br>
&gt; <br>
&gt;&gt; On 4/20/18 12:37 PM, Roman Shpount wrote:<br>
&gt;&gt;&gt; Hi All,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I do not think ice-options was ever used as a media level attr=
ibute.<br>
&gt;&gt;&gt; Only two ice-options defined in IANA registry<br>
&gt;&gt;&gt; (<a href=3D"https://www.iana.org/assignments/ice/ice.xhtml" re=
l=3D"noreferrer" target=3D"_blank">https://www.iana.org/<wbr>assignments/ic=
e/ice.xhtml</a>) are ice2 and=C2=A0 rtp+ecn,<br>
&gt;&gt;&gt; which are both session level.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Furthermore, RFC 5245 section 15.5<br>
&gt;&gt;&gt; (<a href=3D"https://tools.ietf.org/html/rfc5245#section-15.5,"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc5=
245#section-15.5,</a>) defined that<br>
&gt;&gt;&gt; ice-options attribute is session level only. Thus, ice-options=
 should be<br>
&gt;&gt;&gt; kept session level for backwards compatibility.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If something more granular then session is needed, I think it =
should go<br>
&gt;&gt;&gt; into candidate extension attribute, not into media level ice-o=
ptions.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Bottom line, I think ice-options should be a a session level o=
nly<br>
&gt;&gt; attribute.<br>
&gt;&gt;<br>
&gt;&gt; Agreed.<br>
&gt;&gt;<br>
&gt;&gt; In the Trickle ICE spec, we also limited the `trickle` option to s=
ession<br>
&gt;&gt; level only.<br>
&gt;&gt;<br>
&gt;&gt; Peter<br>
&gt;&gt;<br>
&gt;&gt;<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Marc Petit-Huguenin<br>
Email: <a href=3D"mailto:marc@petit-huguenin.org">marc@petit-huguenin.org</=
a><br>
Blog: <a href=3D"https://marc.petit-huguenin.org" rel=3D"noreferrer" target=
=3D"_blank">https://marc.petit-huguenin.<wbr>org</a><br>
Profile: <a href=3D"https://www.linkedin.com/in/petithug" rel=3D"noreferrer=
" target=3D"_blank">https://www.linkedin.com/in/<wbr>petithug</a><br>
<br>
</font></span><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>

--00000000000065184b056a870535--


From nobody Mon Apr 23 23:43:31 2018
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 0EC0D124B0A for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 23:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level: 
X-Spam-Status: No, score=-4.309 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4KfWH-sl1Uj for <mmusic@ietfa.amsl.com>; Mon, 23 Apr 2018 23:43: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 2147F12420B for <mmusic@ietf.org>; Mon, 23 Apr 2018 23:43:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524552205; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=o7tbITGaY4Bcc5yz4eAlQn21szjydUHhBx+rmZRJ0b8=; b=bz7TeF7wtiWR/IVZhcdyL1MN4fhWuXqgvptj3fPl94q5tDfZ0oFR2rBZGspqyFNg eKL+nwITq1xVhB2beZKYdoUm4MtjWmTEuyV4YZpF634R1hfnndbQATZjLo1K5Du+ nIl8KK6dcHKCux+84dUwotH9iZcDY+mUy/WhMRBt2js=;
X-AuditID: c1b4fb30-4c8039c000007681-f3-5aded20d81f3
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E2.03.30337.D02DEDA5; Tue, 24 Apr 2018 08:43:25 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0382.000; Tue, 24 Apr 2018 08:43:04 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Marc Petit-Huguenin <marc@petit-huguenin.org>
CC: mmusic WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] ice-options attribute: session- and media-level?
Thread-Index: AQHT2HgrgUz1UGYUZkWOyWP9nrLzRqQJ2sMAgAAIfgCAALjVAIAD1lkAgAAFLgCAARfUgA==
Date: Tue, 24 Apr 2018 06:43:04 +0000
Message-ID: <D704AD26.2EAAF%christer.holmberg@ericsson.com>
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com> <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com> <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com> <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com> <9865a04c-312c-1a81-7f96-5baa237f3d55@petit-huguenin.org> <CAD5OKxt+1OspnDEOx9LvmPOZDsAUP+neypPWbuc0cA0ECx_tow@mail.gmail.com>
In-Reply-To: <CAD5OKxt+1OspnDEOx9LvmPOZDsAUP+neypPWbuc0cA0ECx_tow@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D704AD262EAAFchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrEIsWRmVeSWpSXmKPExsUyM2K7ui7vpXtRBp83SlusPX6T0WLq8scs FjMuTGV2YPZYsuQnk8fx09dZPW5NKQhgjuKySUnNySxLLdK3S+DKmN1wkbngn3/F/0NN7A2M c1y7GDk4JARMJJ62sXQxcnEICRxhlFjw9gwbhLOYUeLM+qWMIEVsAhYS3f+0uxg5OUQEwiQu rvzCCGIzC8hLXFiyhgnEFhZwk5h3bgEbRI27xKevd1lh6pc82c8OYrMIqErsO/aVGcTmFbCW OLy1DaxXSKCRWWLPVLD5nAKBEq3vu8HijAJiEt9PQcxnFhCXuPVkPpgtISAgsWTPeWYIW1Ti 5eN/YLtEBfQkNpy4zQ7xl5LE7Q1OEK0JEq1Nv1gh1gpKnJz5hGUCo+gsJFNnISmbhaQMIq4j sWD3JzYIW1ti2cLXzDD2mQOPgXo5gGxriSlzcpCVLGDkWMUoWpxanJSbbmSkl1qUmVxcnJ+n l5dasokRGJMHt/w22MH48rnjIUYBDkYlHt4nR+9FCbEmlhVX5h5ilOBgVhLh3SsHFOJNSays Si3Kjy8qzUktPsQozcGiJM5r4bc5SkggPbEkNTs1tSC1CCbLxMEp1cA4WXjhfoMIs79vFyVw dm8KOLRllVrgzDn/vskpxQabqG3MfaW7bN8uTb7bk0XPXFDzecxYbHTv576JD8J9cjOahRJ9 J2xZx8G/UenKhw12t+S/V2ywvJvw2zFjMlf9jd8C7bcmbY48YpvFHyMr86OaYcmtcP/QVxIS T+q/R5q53lv9QH2V0GUBJZbijERDLeai4kQAet9th8UCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Upgpcxd2HaNwLYjvMdVvgAjhC8g>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 06:43:30 -0000

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

+1

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Date: Monday 23 April 2018 at 20:03
To: "marc@petit-huguenin.org<mailto:marc@petit-huguenin.org>" <marc@petit-h=
uguenin.org<mailto:marc@petit-huguenin.org>>
Cc: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?

Hi All,

I would prefer disaggregated media to be handled separately and keep ice-op=
tions a session level attribute.. Dealing with disaggregated media is a muc=
h bigger issue then just adjusting ice-options. For instance, why ice-optio=
ns are handled there and ice-lite is excluded? I think ice-lite is potentia=
lly as big of the problem when aggregating media from several sources. Also=
, I we sure that making singe ICE agent dealing with two independent ICE ag=
ents does not have any issues? I do not think this was examined in sufficie=
nt detail.

Furthermore, it is possible to define per ICE candidate specific parameters=
 using ICE candidate extension attributes. I think it would be cleaner to d=
efine things which are specific to only some candidates using this mechanis=
m vs medial level ice-options.

Regards,

_____________
Roman Shpount

On Mon, Apr 23, 2018 at 12:45 PM, Marc Petit-Huguenin <marc@petit-huguenin.=
org<mailto:marc@petit-huguenin.org>> wrote:
This was done as a consequence of merging this draft in ice-bis:

https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-ice-attributes-l=
evel-04.txt

There is probably discussions that can be found in the minutes of IETF meet=
ings around that time when the WG agreed to that modification.

On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:
> I am fine with considering ice-options has session level too. I wonder if
> Marc can chime in on considering it as  media level in the ice-sip-sdp.
>
> On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre <stpeter@mozilla.com<=
mailto:stpeter@mozilla.com>>
> wrote:
>
>> On 4/20/18 12:37 PM, Roman Shpount wrote:
>>> Hi All,
>>>
>>> I do not think ice-options was ever used as a media level attribute.
>>> Only two ice-options defined in IANA registry
>>> (https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and  rtp+ecn,
>>> which are both session level.
>>>
>>> Furthermore, RFC 5245 section 15.5
>>> (https://tools.ietf.org/html/rfc5245#section-15.5,) defined that
>>> ice-options attribute is session level only. Thus, ice-options should b=
e
>>> kept session level for backwards compatibility.
>>>
>>> If something more granular then session is needed, I think it should go
>>> into candidate extension attribute, not into media level ice-options.
>>>
>>> Bottom line, I think ice-options should be a a session level only
>> attribute.
>>
>> Agreed.
>>
>> In the Trickle ICE spec, we also limited the `trickle` option to session
>> level only.
>>
>> Peter
>>
>>


--
Marc Petit-Huguenin
Email: marc@petit-huguenin.org<mailto:marc@petit-huguenin.org>
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


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



--_000_D704AD262EAAFchristerholmbergericssoncom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <71F0BBDCE04EE8418F094A7A087B882A@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</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>&#43;1</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 Roman=
 Shpount &lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Date: </span>Monday 23 April 2018 at 20:03=
<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:marc@pe=
tit-huguenin.org">marc@petit-huguenin.org</a>&quot; &lt;<a href=3D"mailto:m=
arc@petit-huguenin.org">marc@petit-huguenin.org</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] ice-options a=
ttribute: session- and media-level?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Hi All,
<div><br>
</div>
<div>I would prefer disaggregated media to be handled separately and keep i=
ce-options a session level attribute.. Dealing with disaggregated media is =
a much bigger issue then just adjusting ice-options. For instance, why ice-=
options are handled there and ice-lite
 is excluded? I think ice-lite is potentially as big of the problem when ag=
gregating media from several sources. Also, I we sure that making singe ICE=
 agent dealing with two independent ICE agents does not have any issues? I =
do not think this was examined in
 sufficient detail.&nbsp;</div>
<div><br>
</div>
<div>Furthermore, it is possible to define per ICE candidate specific param=
eters using ICE candidate extension attributes. I think it would be cleaner=
 to define things which are specific to only some candidates using this mec=
hanism vs medial level ice-options.</div>
<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 Shpount</div>
</div>
<br>
<div class=3D"gmail_quote">On Mon, Apr 23, 2018 at 12:45 PM, Marc Petit-Hug=
uenin <span dir=3D"ltr">
&lt;<a href=3D"mailto:marc@petit-huguenin.org" target=3D"_blank">marc@petit=
-huguenin.org</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">
This was done as a consequence of merging this draft in ice-bis:<br>
<br>
<a href=3D"https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-ice-a=
ttributes-level-04.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/archive/<wbr>id/draft-petithuguenin-mmusic-<wbr>ice-attributes-level=
-04.txt</a><br>
<br>
There is probably discussions that can be found in the minutes of IETF meet=
ings around that time when the WG agreed to that modification.<br>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:<br>
&gt; I am fine with considering ice-options has session level too. I wonder=
 if<br>
&gt; Marc can chime in on considering it as&nbsp; media level in the ice-si=
p-sdp.<br>
&gt; <br>
&gt; On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre &lt;<a href=3D"mai=
lto:stpeter@mozilla.com">stpeter@mozilla.com</a>&gt;<br>
&gt; wrote:<br>
&gt; <br>
&gt;&gt; On 4/20/18 12:37 PM, Roman Shpount wrote:<br>
&gt;&gt;&gt; Hi All,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I do not think ice-options was ever used as a media level attr=
ibute.<br>
&gt;&gt;&gt; Only two ice-options defined in IANA registry<br>
&gt;&gt;&gt; (<a href=3D"https://www.iana.org/assignments/ice/ice.xhtml" re=
l=3D"noreferrer" target=3D"_blank">https://www.iana.org/<wbr>assignments/ic=
e/ice.xhtml</a>) are ice2 and&nbsp; rtp&#43;ecn,<br>
&gt;&gt;&gt; which are both session level.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Furthermore, RFC 5245 section 15.5<br>
&gt;&gt;&gt; (<a href=3D"https://tools.ietf.org/html/rfc5245#section-15.5,"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc5=
245#section-15.5,</a>) defined that<br>
&gt;&gt;&gt; ice-options attribute is session level only. Thus, ice-options=
 should be<br>
&gt;&gt;&gt; kept session level for backwards compatibility.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If something more granular then session is needed, I think it =
should go<br>
&gt;&gt;&gt; into candidate extension attribute, not into media level ice-o=
ptions.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Bottom line, I think ice-options should be a a session level o=
nly<br>
&gt;&gt; attribute.<br>
&gt;&gt;<br>
&gt;&gt; Agreed.<br>
&gt;&gt;<br>
&gt;&gt; In the Trickle ICE spec, we also limited the `trickle` option to s=
ession<br>
&gt;&gt; level only.<br>
&gt;&gt;<br>
&gt;&gt; Peter<br>
&gt;&gt;<br>
&gt;&gt;<br>
<br>
<br>
</div>
</div>
<span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Marc Petit-Huguenin<br>
Email: <a href=3D"mailto:marc@petit-huguenin.org">marc@petit-huguenin.org</=
a><br>
Blog: <a href=3D"https://marc.petit-huguenin.org" rel=3D"noreferrer" target=
=3D"_blank">
https://marc.petit-huguenin.<wbr>org</a><br>
Profile: <a href=3D"https://www.linkedin.com/in/petithug" rel=3D"noreferrer=
" target=3D"_blank">
https://www.linkedin.com/in/<wbr>petithug</a><br>
<br>
</font></span><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_D704AD262EAAFchristerholmbergericssoncom_--


From nobody Tue Apr 24 00:08:01 2018
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 D21BE127337 for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 00:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level: 
X-Spam-Status: No, score=-4.309 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q32OyF461B1Q for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 00:07:57 -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 C7985124B0A for <mmusic@ietf.org>; Tue, 24 Apr 2018 00:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524553675; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=p/zQcZPgbq7e807bjDelhPW+O4zFNwggIUXNzJlmhM8=; b=IlLGvSphsrPYBFtEts/gtwdgvsTVNofEPKudyDQQnsaSMtZbAMqlXtbW7RKssMwA LvGw8QaDRzZsRsZI83U0hfsYBYkEraokqYWpxnxp3iowZThvoH3lIWYm7c1CvKm/ /YuJQp9IHqvGNdOWZMSu8o3hrunJJZvsGs+F7dXS7xc=;
X-AuditID: c1b4fb30-0dfff70000007681-da-5aded7ca8966
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 7F.89.30337.AC7DEDA5; Tue, 24 Apr 2018 09:07:55 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0382.000; Tue, 24 Apr 2018 09:07:54 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Marc Petit-Huguenin <marc@petit-huguenin.org>
CC: mmusic WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] ice-options attribute: session- and media-level?
Thread-Index: AQHT2HgrgUz1UGYUZkWOyWP9nrLzRqQJ2sMAgAAIfgCAALjVAIAD1lkAgAAFLgCAAR7EAA==
Date: Tue, 24 Apr 2018 07:07:54 +0000
Message-ID: <D704AF8C.2EAB4%christer.holmberg@ericsson.com>
References: <D6FF6FE7.2E7A2%christer.holmberg@ericsson.com> <CAD5OKxuiaQEd=vpU=W65kGGi8wWUvuQq0X=_=x_4w6TOu_qFOw@mail.gmail.com> <2a27e3fb-528a-92a9-bdfc-e4f303d34221@mozilla.com> <CAMRcRGT=KvEyafM=bNwfmF0B5A70BrHXUBSoFFrEDPKY=fSMmg@mail.gmail.com> <9865a04c-312c-1a81-7f96-5baa237f3d55@petit-huguenin.org> <CAD5OKxt+1OspnDEOx9LvmPOZDsAUP+neypPWbuc0cA0ECx_tow@mail.gmail.com>
In-Reply-To: <CAD5OKxt+1OspnDEOx9LvmPOZDsAUP+neypPWbuc0cA0ECx_tow@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D704AF8C2EAB4christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrCIsWRmVeSWpSXmKPExsUyM2K7tO7p6/eiDF6dYLRYe/wmo8XU5Y9Z LGZcmMrswOyxZMlPJo/jp6+zetyaUhDAHMVlk5Kak1mWWqRvl8CVcWp5G3NBm0/F2+ermRoY Tzh0MXJySAiYSNzff5O1i5GLQ0jgCKPE+WvHmCGcxYwS2958Z+pi5OBgE7CQ6P6nDdIgIhAm cXHlF0YQm1lAXuLCkjVMILawgJvEvHML2CBq3CU+fb3LClM/7+NeFhCbRUBVYvreTWD1vALW Eid3tYPZQgKNzBJ7poLN5xQIlGh93w0WZxQQk/h+CmI+s4C4xK0n85kgjhaQWLLnPDOELSrx 8vE/sF2iAnoSG07cZgc5WUJASeL2BieI1gSJxzefs0KsFZQ4OfMJywRG0VlIps5CUjYLSRlE 3EDi/bn5zBC2tsSyha+hbH2JjV/OMkLY1hLPT79iQ1azgJFjFaNocWpxUm66kZFealFmcnFx fp5eXmrJJkZgXB7c8ttgB+PL546HGAU4GJV4eJ8cvRclxJpYVlyZe4hRgoNZSYR3rxxQiDcl sbIqtSg/vqg0J7X4EKM0B4uSOK+F3+YoIYH0xJLU7NTUgtQimCwTB6dUA2PK1luuD96K/V7L XHRNtlzM/lb3Sb8ZzskHt3yvEfF/kCi7xn7rbtmV/+d5713LlzGJwUKx4+2uJyIvjoj9Yn7I +CaujSfJ2fPvbt0Jma0l7NZsfAUFLelNcu95mDbUTa8zbSlyztl/5LPsSpUT5hWH06sZVbhz 4idYPn6k56MvK/j4hMCf30osxRmJhlrMRcWJAKixh9jHAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FpdQahL5R0ctYEhpl6PgTOZeFKI>
Subject: Re: [MMUSIC] ice-options attribute: session- and media-level?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 07:08:00 -0000

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

Hi,

> I would prefer disaggregated media to be handled separately and keep ice-=
options a session level attribute.. Dealing with disaggregated media is a m=
uch bigger issue then just adjusting ice-options.
> For instance, why ice-options are handled there and ice-lite is excluded?=
 I think ice-lite is potentially as big of the problem when aggregating med=
ia from several sources. Also, I we sure that making singe ICE agent
> dealing with two independent ICE agents does not have any issues? I do no=
t think this was examined in sufficient detail.

If you are going to use disaggregated media with ICE, I think there are mor=
e issues than signalling.

For example, keep in mind that the check lists impact each other (e.g., a s=
tate change of a pair in list X might impact the state of a pair in list Y)=
. How would that work if check lists X and Y are handled by different ICE a=
gents?

With ICE trickle, one agent would need to know that candidates the other ag=
ent(s) is trickling.

Etc.

There would either need to be some "inter-agent communication=94 mechanism,=
 or we would need to "de-couple=94 how media streams (check lists) depend o=
n each other.

So, if people want to specify disaggregated-media-with-ICE, I think it shou=
ld be done as a separate deliverable (possibly in a separate WG).

Regards,

Christer





On Mon, Apr 23, 2018 at 12:45 PM, Marc Petit-Huguenin <marc@petit-huguenin.=
org<mailto:marc@petit-huguenin.org>> wrote:
This was done as a consequence of merging this draft in ice-bis:

https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-ice-attributes-l=
evel-04.txt

There is probably discussions that can be found in the minutes of IETF meet=
ings around that time when the WG agreed to that modification.

On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:
> I am fine with considering ice-options has session level too. I wonder if
> Marc can chime in on considering it as  media level in the ice-sip-sdp.
>
> On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre <stpeter@mozilla.com<=
mailto:stpeter@mozilla.com>>
> wrote:
>
>> On 4/20/18 12:37 PM, Roman Shpount wrote:
>>> Hi All,
>>>
>>> I do not think ice-options was ever used as a media level attribute.
>>> Only two ice-options defined in IANA registry
>>> (https://www.iana.org/assignments/ice/ice.xhtml) are ice2 and  rtp+ecn,
>>> which are both session level.
>>>
>>> Furthermore, RFC 5245 section 15.5
>>> (https://tools.ietf.org/html/rfc5245#section-15.5,) defined that
>>> ice-options attribute is session level only. Thus, ice-options should b=
e
>>> kept session level for backwards compatibility.
>>>
>>> If something more granular then session is needed, I think it should go
>>> into candidate extension attribute, not into media level ice-options.
>>>
>>> Bottom line, I think ice-options should be a a session level only
>> attribute.
>>
>> Agreed.
>>
>> In the Trickle ICE spec, we also limited the `trickle` option to session
>> level only.
>>
>> Peter
>>
>>


--
Marc Petit-Huguenin
Email: marc@petit-huguenin.org<mailto:marc@petit-huguenin.org>
Blog: https://marc.petit-huguenin.org
Profile: https://www.linkedin.com/in/petithug


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



--_000_D704AF8C2EAB4christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <6241458A4BCEF649A24770AC251A752E@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">
<div>&gt; I would prefer disaggregated media to be handled separately and k=
eep ice-options a session level attribute.. Dealing with disaggregated medi=
a is a much bigger issue then just adjusting ice-options.
</div>
</div>
</div>
</div>
</span>
<div>&gt; For instance, why ice-options are handled there and ice-lite is e=
xcluded? I think ice-lite is potentially as big of the problem when aggrega=
ting media from several sources. Also, I we sure that making singe ICE agen=
t&nbsp;</div>
<div>&gt; dealing with two independent ICE agents does not have any issues?=
 I do not think this was examined in sufficient detail.&nbsp;</div>
<div><br>
</div>
<div>If you are going to use disaggregated media with ICE, I think there ar=
e more issues than signalling.</div>
<div><br>
</div>
<div>For example, keep in mind that the check lists impact each other (e.g.=
, a state change of a pair in list X might impact the state of a pair in li=
st Y). How would that work if check lists X and Y are handled by different =
ICE agents?&nbsp;</div>
<div><br>
</div>
<div>With ICE trickle, one agent would need to know that candidates the oth=
er agent(s) is trickling.&nbsp;</div>
<div><br>
</div>
<div>Etc.</div>
<div><br>
</div>
<div>There would either need to be some &quot;inter-agent communication=94 =
mechanism, or we would need to &quot;de-couple=94 how media streams (check =
lists) depend on each other.</div>
<div><br>
</div>
<div>So, if people want to specify disaggregated-media-with-ICE, I think it=
 should be done as a separate deliverable (possibly in a separate WG).</div=
>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">On Mon, Apr 23, 2018 at 12:45 PM, Marc Petit-Hug=
uenin <span dir=3D"ltr">
&lt;<a href=3D"mailto:marc@petit-huguenin.org" target=3D"_blank">marc@petit=
-huguenin.org</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">
This was done as a consequence of merging this draft in ice-bis:<br>
<br>
<a href=3D"https://www.ietf.org/archive/id/draft-petithuguenin-mmusic-ice-a=
ttributes-level-04.txt" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/archive/<wbr>id/draft-petithuguenin-mmusic-<wbr>ice-attributes-level=
-04.txt</a><br>
<br>
There is probably discussions that can be found in the minutes of IETF meet=
ings around that time when the WG agreed to that modification.<br>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
On 04/20/2018 11:09 PM, Suhas Nandakumar wrote:<br>
&gt; I am fine with considering ice-options has session level too. I wonder=
 if<br>
&gt; Marc can chime in on considering it as&nbsp; media level in the ice-si=
p-sdp.<br>
&gt; <br>
&gt; On Fri, Apr 20, 2018 at 12:07 PM, Peter Saint-Andre &lt;<a href=3D"mai=
lto:stpeter@mozilla.com">stpeter@mozilla.com</a>&gt;<br>
&gt; wrote:<br>
&gt; <br>
&gt;&gt; On 4/20/18 12:37 PM, Roman Shpount wrote:<br>
&gt;&gt;&gt; Hi All,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I do not think ice-options was ever used as a media level attr=
ibute.<br>
&gt;&gt;&gt; Only two ice-options defined in IANA registry<br>
&gt;&gt;&gt; (<a href=3D"https://www.iana.org/assignments/ice/ice.xhtml" re=
l=3D"noreferrer" target=3D"_blank">https://www.iana.org/<wbr>assignments/ic=
e/ice.xhtml</a>) are ice2 and&nbsp; rtp&#43;ecn,<br>
&gt;&gt;&gt; which are both session level.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Furthermore, RFC 5245 section 15.5<br>
&gt;&gt;&gt; (<a href=3D"https://tools.ietf.org/html/rfc5245#section-15.5,"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc5=
245#section-15.5,</a>) defined that<br>
&gt;&gt;&gt; ice-options attribute is session level only. Thus, ice-options=
 should be<br>
&gt;&gt;&gt; kept session level for backwards compatibility.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If something more granular then session is needed, I think it =
should go<br>
&gt;&gt;&gt; into candidate extension attribute, not into media level ice-o=
ptions.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Bottom line, I think ice-options should be a a session level o=
nly<br>
&gt;&gt; attribute.<br>
&gt;&gt;<br>
&gt;&gt; Agreed.<br>
&gt;&gt;<br>
&gt;&gt; In the Trickle ICE spec, we also limited the `trickle` option to s=
ession<br>
&gt;&gt; level only.<br>
&gt;&gt;<br>
&gt;&gt; Peter<br>
&gt;&gt;<br>
&gt;&gt;<br>
<br>
<br>
</div>
</div>
<span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Marc Petit-Huguenin<br>
Email: <a href=3D"mailto:marc@petit-huguenin.org">marc@petit-huguenin.org</=
a><br>
Blog: <a href=3D"https://marc.petit-huguenin.org" rel=3D"noreferrer" target=
=3D"_blank">
https://marc.petit-huguenin.<wbr>org</a><br>
Profile: <a href=3D"https://www.linkedin.com/in/petithug" rel=3D"noreferrer=
" target=3D"_blank">
https://www.linkedin.com/in/<wbr>petithug</a><br>
<br>
</font></span><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>
</span>
</body>
</html>

--_000_D704AF8C2EAB4christerholmbergericssoncom_--


From nobody Tue Apr 24 06:23:41 2018
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 2C3BD129BBF; Tue, 24 Apr 2018 06:23: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>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.79.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152457622013.28851.9197483965555943061@ietfa.amsl.com>
Date: Tue, 24 Apr 2018 06:23:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LjLT1bHsDY9w1VHRFBvvhFuF--c>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-50.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 13:23: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 WG 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-50.txt
	Pages           : 68
	Date            : 2018-04-24

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 transport (5-tuple) for sending and receiving media described
   by multiple SDP media descriptions ("m=" sections).  Such transport
   is referred to as a BUNDLE transport, and the media is referred to as
   bundled media.  The "m=" sections that use the BUNDLE transport form
   a BUNDLE group.

   This specification updates RFC 3264, to allow assigning a zero port
   value to a "m=" section also in cases where the media described by
   the "m=" section is not disabled or rejected.

   This specification defines a new RTP Control Protocol (RTCP) source
   description (SDES) item and a new RTP header extension that can be
   used to correlate bundled RTP/RTCP packets with their appropriate
   "m=" section.

   This specification updates RFC 7941, by adding an exception, for the
   MID RTP header extension, to the requirement regarding protection of
   an SDES RTP header extension carrying an SDES item for the MID RTP
   header extension.


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

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

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


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 Apr 24 06:26:38 2018
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 165FF12AF83 for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 06:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JOCupi0ZcKHt for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 06:26:34 -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 92595129C51 for <mmusic@ietf.org>; Tue, 24 Apr 2018 06:26:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524576392; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=JOA/4amZda0vAevUFZqA5VUKKyodrHwExRIE7HjDeZ0=; b=ditbsrSZF6/h46YuBpKPtIjQW6DFIsIctgz9bNDC3w65YvlIFUHeERxWsllbWrBP UOKsKI+fJZ5JnfGU2DNQY93qmjRqnW+kiEb8RmhxdAJrQk+wwsuWtjlh9D+SMsrd yc2T7mkYQd2juu4KM5qUgwDBWf7UYFknMThHGt5/8N0=;
X-AuditID: c1b4fb25-88bff70000006561-f2-5adf3088ada4
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 9F.03.25953.8803FDA5; Tue, 24 Apr 2018 15:26:32 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Tue, 24 Apr 2018 15:26:32 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: Draft new version: BUNDLE-50
Thread-Index: AQHT28/b7An4xOLDl0izAdB2uaWBtQ==
Date: Tue, 24 Apr 2018 13:26:32 +0000
Message-ID: <D7050B3F.2EB58%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <84E6EC3A6C882B4EA08C18B41C744905@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupikeLIzCtJLcpLzFFi42KZGbHdRrfD4H6UwctnRhbzO0+zW0yf9Y7N YsaficwW53euZ7KYuvwxiwOrx5IlP5k8Zu18whLAFMVlk5Kak1mWWqRvl8CVsfC4ScFCpoqF t+6xNDA+Y+xi5OSQEDCRmLVgJXMXIxeHkMARRokjB3qgnMWMEq/enGHtYuTgYBOwkOj+pw0S FxFoZpL4seULC0i3sICqxL7Ov2C2iICWxMYPk1khbD2Jj7sXgMVZgGq63p5lA7F5BawlGr/1 s4PYjAJiEt9PrWECsZkFxCVuPZnPBHGRgMSSPeeZIWxRiZeP/4HNFAWaueHEbXaQeyQElCRu b3CCaNWTuDF1ChuEbS1xa+IiVghbW2LZwtfMEGsFJU7OfMIygVFkFpJts5C0z0LSPgtJ+ywk 7QsYWVcxihanFiflphsZ66UWZSYXF+fn6eWllmxiBMbQwS2/VXcwXn7jeIhRgINRiYd3p/r9 KCHWxLLiytxDjBIczEoivHvl7kUJ8aYkVlalFuXHF5XmpBYfYpTmYFES531ovjlKSCA9sSQ1 OzW1ILUIJsvEwSnVwGi2Ibzj8eaNhYWL2gXS/sdK6PNeeV0fG/76e5j7pPkLJLSrOsO3mTY1 lrwN7lfY59itka496/LxgJ6TW04vfr/+1DLhB6qTjD953b6288nUGZaXmr8aKkS+T9k4MfDQ pdu/eBqf3RXxVS364c38ye+yzY9bNlaGnecsfltrWuRLp56pPFBgtUuJpTgj0VCLuag4EQA4 RN7knQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EgebxWKTPBUyYtmok4lPcIp1Us4>
Subject: [MMUSIC] Draft new version: BUNDLE-50
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 13:26:37 -0000

Hi,

I have submitted a new version (-50) of
draft-ietf-mmusic-sdp-bundle-negotiation.

The new version addresses most of the IESG review comments.

We still need to address some of the comments given on section 10, and
Ekr=B9s =B3address:port=B2 issue.

Regards,

Christer


From nobody Tue Apr 24 06:54:44 2018
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 4274712D77D for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 06:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.312
X-Spam-Level: 
X-Spam-Status: No, score=-4.312 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yx8TznkHVsqF for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 06:54:41 -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 5F989129BBF for <mmusic@ietf.org>; Tue, 24 Apr 2018 06:54:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524578079; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ql78rHRvLKO9RDRLomni33EgnZI5TPP/hibSo+GRpVw=; b=C7S1zfB2cDnNse3mpFTFszCi95WvcCcFJ+nMjd+8mOzXhFGZb1G8YPDQHlpzc69b 9ICDTmLicQmBcvCO7oxguJOHxeIxlAFhN3R4VdNOCpxIUoo8d/QBPBYFgvvbEteJ 1IQKr7qz2R6z6YL77AXe3bfJEJ4mRHa1DWofGmIwukM=;
X-AuditID: c1b4fb3a-ae7ff7000000795a-5d-5adf371f847c
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id CA.EA.31066.F173FDA5; Tue, 24 Apr 2018 15:54:39 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0382.000; Tue, 24 Apr 2018 15:54:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: draft-ice-sip-sdp: Comments on section 4.4
Thread-Index: AQHT29PHLxi1RX6zWUCJ+OHk7AtJUg==
Date: Tue, 24 Apr 2018 13:54:35 +0000
Message-ID: <D7051253.2EB7A%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <B4F8A15DDF25084CB42E54C6273B031A@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7n668+f0og6UHtCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujO034wp2slfMbtrB3MB4jLWLkZNDQsBE4l77GaYuRi4OIYEj jBL3Py9khnAWM0pMbp7N2MXIwcEmYCHR/U8bpEFEQF3i694eZhBbWMBY4tm7FnaIuIXEmWWr GCFsPYnmplY2EJtFQFXiwryZLCBjeAWsJRa/NwEJMwqISXw/tYYJxGYWEJe49WQ+E8Q9AhJL 9pxnhrBFJV4+/gd2pyjQyA0nbrODjJEQUJK4vcEJotVA4v25+cwQtrXEht6TLBC2tsSyha/B 4rwCghInZz5hmcAoMgvJtllI2mchaZ+FpH0WkvYFjKyrGEWLU4uLc9ONjPRSizKTi4vz8/Ty Uks2MQKj4eCW31Y7GA8+dzzEKMDBqMTDu0T9fpQQa2JZcWXuIUYJDmYlEd69cveihHhTEiur Uovy44tKc1KLDzFKc7AoifM6pVlECQmkJ5akZqemFqQWwWSZODilGhi9VXWexR90kvntYMNz u6BU/UOBY/6n/P3JLx1qX37TLm5iOJa9z+BUe1eOVizzypMPDioX7Pr3ZjEH8yQtg31ijmsN PU5xul2+NYVzR2tXp+KfuK7TsWfXBh11UE3cOkm22+F+z9GpuQ0M68rEJ3xo6xLl+B3j38d3 yGnHRXPlVTw7l0UttFRiKc5INNRiLipOBACDgCsLggIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/rC2VsX-AX6nwcwzkvOqxoqaX3Q0>
Subject: [MMUSIC] draft-ice-sip-sdp: Comments on section 4.4
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 13:54:43 -0000

Hi,


Section 4.4 says:

   "When present in both, the value in the
    media-level takes precedence.  Thus, the value at the session-level
    is effectively a default that applies to all data streams, unless
    overridden by a media-level value.=B2


This is basic offer/answer, so I suggest to remove the text.


----


Section 4.4 says:

    "If two data streams have identical ice-ufrag=B9s, they MUST have
identical ice-pwd=B9s.=B2


This requirements does not exist in 5245bis, and in RFC 5245 it was only
mentioned in the SDP attribute section. Is there a reason for this?


---


Section 4.4 says:


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

This is correct. But, it is defined in 5245bis, so I would suggest to add:
=B3As defined in [ICE-BIS], the=8A=B2.



Regards,

Christer


From nobody Tue Apr 24 07:31:38 2018
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 4969D128954 for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 07:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxP8ZuJB49i1 for <mmusic@ietfa.amsl.com>; Tue, 24 Apr 2018 07:29:41 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32E12124205 for <mmusic@ietf.org>; Tue, 24 Apr 2018 07:29:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1922; q=dns/txt; s=iport; t=1524580181; x=1525789781; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=acMS9+27T5JXDmMShnRmS+T9PY7/2ofqvUjBaechGkM=; b=I0s1or9ztwCZRnZhmKycQ9q2gExav2NMK4NSpFm28h8RZvULrtY/X400 2zULdG7UzxgAb/vdQXvXufTNcLI2jh5gSyewEZ37VuUZ8Yv11Hh748WEL cVe8O0dGAJ9MQamp5bIj2zvHnx97MBrUGHCTr2ldiAgYB+88CVONK41qJ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DkAwAKP99a/4wNJK1cDgsBAQEBAQE?= =?us-ascii?q?BAQEBAQEHAQEBAQGDQ2F6KINqlH6BSwghgQ+UewsYC4QDRgKCeCE4FAECAQE?= =?us-ascii?q?BAQEBAmwcDIUjAQEBAwEBIRU2GwsYAgIfBwICJzAGAQwGAgEBhH4ND6Vyghy?= =?us-ascii?q?EWINtgjQFgQmHA4FUP4EyDIJcgxEBAYRgglQCl30IjjwGh0yFBJAygSUzIYF?= =?us-ascii?q?STSMVO4JDgkiISIUEViMwkQsBAQ?=
X-IronPort-AV: E=Sophos;i="5.49,323,1520899200"; d="scan'208";a="104232272"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2018 14:29:40 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id w3OETd7M002668; Tue, 24 Apr 2018 14:29:39 GMT
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B72E870BA@ESESSMB109.ericsson.se> <CABcZeBP7viYgH+PEkpvUNn4Z5NychjO6ChVdt+YVdoa6o82FYg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E88F08@ESESSMB109.ericsson.se> <CABcZeBNdZSFnVfbxtvy4FXTjjXsqg3CO7Dr2TpwcbPkMQQ_jXg@mail.gmail.com> <D6FD2AE5.2E4F5%christer.holmberg@ericsson.com> <CABcZeBNLgTW8=i223ibKa2nxibZF+uxZJABShZyxRE3T9eUoUA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E8CCB3@ESESSMB109.ericsson.se> <9d453c11-d225-422e-ad8d-2e8ce9d90fb1@cisco.com> <328adc10-0b8c-f682-3df6-ba7015105f65@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B72E96A8D@ESESSMB109.ericsson.se>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <0db025d3-a503-4671-4f0d-edf2e49e450e@cisco.com>
Date: Tue, 24 Apr 2018 10:29:39 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E96A8D@ESESSMB109.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AcZ7ip_mcoDeaM3YIMEqUjXE8-E>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - COMMENT
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 14:29:47 -0000

On 4/22/18 5:40 PM, Christer Holmberg wrote:
> Hi,
>
>>>>>> But, we would not be using the generic O/A structure.
>>>>> I'm not seeing a problem with that
>>>> I think some do, e.g., the chairs.
>>>>
>>>> I have personally also been strict about it when reviewing documents
>>>> written by others, but I have no problem allowing other structures if
>>>> seen more appropriate - if everyone is ok with it.
>>> Agreed. We have been using this structure and consistently asked
>>> authors to use it as well for a long time. It's an established MMUSIC
>>> practice in dealing with offer/answer procedures and I'm not in favor
>>> of changing this.
>> This has also bothered me a bit. The structure was adopted for SDP O/A in the context of a dialog.
>> And in that context the structure is well defined, where the first O/A really requires some different consideration than subsequent O/A.
>>
>> *This* usage is different, in the the first offer of a bundle might not be the first offer of SDP in the dialog.
>> It is potentially confusing to mix these two. Reusing the *structure* makes sense, but doing something to
>> make clear that this is not the same is a good idea.
> There IS text in the draft clarifying that:
>
>        "Initial offer: The first offer, within an SDP session (e.g. a SIP
>        dialog when the Session Initiation Protocol (SIP) [RFC3261] is
>        used to carry SDP), in which the offerer indicates that it wants
>        to create a given BUNDLE group."
>
> This is not even BUNDLE specific - I think there are very few (I can't think of any straight from my head) SDP extension where you would be required to do something in the initial offer of the dialog.
Agreed.

-- Flemming
> Regards,
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>


From nobody Tue Apr 24 08:12:03 2018
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 EB28E12D88A; Tue, 24 Apr 2018 08:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eg1_oQqij_dv; Tue, 24 Apr 2018 08:11:59 -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 3E91E12D880; Tue, 24 Apr 2018 08:11:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18221; q=dns/txt; s=iport; t=1524582719; x=1525792319; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=mqg3wO8KYpJZFpFZjUGkLDHouRe4k7c5sLC+gSBT/5I=; b=KZR/NP0Vd72kK503jFeT2meKE6oGCTtTqcbI4XXQDsOmwphWe1S57JpD kDuc9eCEiCeF4hDnznCCBBzJRaA4wvRW6ngUCEyRFXPamaP/Ef8m+2z+J oVnrmpH2ljGQUZyNpkdfD0gDDX3rfNvFe6xvBirgV7lh64dQdG4taBagT g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AKBQBtSN9a/4YNJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDeGMog2qUfoFLCCGBD44VhQKBZAuEbAKCeCE4FAECAQE?= =?us-ascii?q?BAQEBAmwohSIBAQEBAgEdBlYFCwkCDgojBAMCAkYRBgEMBgIBAYR+BQiKQJt?= =?us-ascii?q?BghwfhDmDaYI5iAyBVD+BDyMMglyEW4MYglQChzGEWotyCI48BodMhQSQMoE?= =?us-ascii?q?lMyEmgSxNIxU7gkOCIBcRjiIjMJELAQE?=
X-IronPort-AV: E=Sophos;i="5.49,323,1520899200";  d="scan'208,217";a="378378946"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2018 15:11:57 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w3OFBuvk001676; Tue, 24 Apr 2018 15:11:56 GMT
To: Eric Rescorla <ekr@rtfm.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Cc: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <95979e47-0199-99c4-383a-8a26cb7bbde6@cisco.com>
Date: Tue, 24 Apr 2018 11:11:56 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------7D1D400DEFBB0AE5F8E4F51A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/OkdUcW0F3GO29peYfUXviZ65Z6U>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 24 Apr 2018 15:12:02 -0000

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



On 4/17/18 6:23 PM, Eric Rescorla wrote:
> Hi folks,
>
> This is an attempt to sharpen my point about talking about the
> "BUNDLE address:port", when what we really mean is "use the
> parameters from the "m=" section". Here's an example where this
> creates a real problem. S 8.4 says:
>
>    When an offerer receives an answer, if the answer contains a BUNDLE
>    group, the offerer MUST check that any bundled "m=" section in the
>    answer was indicated as bundled in the corresponding offer. If there
>    is no mismatch, the offerer MUST use the offerer BUNDLE address:port,
>    selected by the answerer [Section 8.3.1], as the address for each
>    bundled "m=" section.
>
> Now consider the case where I am doing trickle ICE. The offer will
> contain:
>
>    a=group:BUNDLE foo bar
>    m=audio 9 RTP/AVP 97
>    c=IN IP4 0.0.0.0
>    a=rtpmap:97 iLBC/8000
>    a=mid:foo
>
>    m=video 9 RTP/AVP 98
>    c=IN IP4 0.0.0.0
>    a=rtpmap:98 H261/90000
>    a=mid:bar
>
> Now, if the answer contains:
>
>    a=group:BUNDLE foo bar
>
> Then the semantics are that we are supposed to use the parameters from
> the m=audio line as the parameters for the bundle group. Specifically,
> we are supposed to use the ICE candidates that belong to that m=audio
> line. But there's no way to get that from this text.
True, but it's an inherent part of the definition of the BUNDLE-tag as 
described in the preceding sections covering the overall offer/answer 
procedures.

> Ordinarily, if
> each m=section contained a distinct address:port, then you might say
> there was an implicit map from address:port to m= section parameters,
> but in this case because all the address:port values are the same,
> that's not possible, and so this paragraph just doesn't work.
Why not ? The BUNDLE-tag in the answer indicates which "m=" section the 
answerer chose and hence you will use the corresponding BUNDLE 
address:port.

> The
> right fix is to stop talking about the address:port and instead talk
> about the m= section.
>
>    When an offerer receives an answer, if the answer contains a BUNDLE
>    group, the offerer MUST check that any bundled "m=" section in the
>    answer was indicated as bundled in the corresponding offer. If there
>    is no mismatch, the offerer MUST use the relevant parameters
>    [specific text from Suhas's draft needed here] from the
>    "m=" section indicated by the BUNDLE tag [again, it would be helpful
>    to have a better name here] for each "m=" section which is bundled
>    with it.
>
> There are other places where this creates confusion, but this is
> a nice clear one.
>
I think we are saying the same thing here, but you are just asking for 
the BUNDLE-tag to be called out more explicitly as opposed to focusing 
on the BUNDLE address:port. Is that right ?

Thanks

-- Flemming


> -Ekr
>
>
>
>
>
> On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>> wrote:
>
>
>
>     On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg
>     <christer.holmberg@ericsson.com
>     <mailto:christer.holmberg@ericsson.com>> wrote:
>
>         Hi,
>
>         ----------------------------------------------------------------------
>         DISCUSS:
>         ----------------------------------------------------------------------
>
>         >>>>>> When an offerer generates an offer, in which it wants
>         to add a new
>         >>>>>> bundled "m=" section, the offerer MUST:
>         >>>>>>
>         >>>>>>      o  Assign the offerer BUNDLE address:port
>         (previously selected
>         >>>>>>         [Section 8.3.1] or newly suggested [Section
>         8.5.1]) to the added
>         >>>>>>         "m=" section; or
>         >>>>>
>         >>>>> IMPORTANT: This doesn't sound right. You can't use the
>         existing
>         >>>>> address:port, because if the peer rejects BUNDLE but
>         accepts the m=
>         >>>>> section then it's broken.
>         >>>>
>         >>>> Note that in this case the usage of BUNDLE has already
>         been negotiated.
>         >>>> Then, if the answerer does not accept the new m= section
>         into the BUNDLE
>         >>>> group, it needs to send an offer where it removes it, as
>         described in
>         >>>> section 8.3.3.
>         >>>
>         >>> Well, both of these options correspond to insisting that
>         the m= section
>         >>> be in the BUNDLE group. If I just want to suggest it, I
>         would have to provide
>         >>> a fresh unique address. Or are you saying that's impossible.
>         >>>
>         >> Yes.
>         >>
>         >> Previously, when the offerer wanted to add a new m- section
>         to a BUNDLE
>         >> group, it had to choice of either assigning a unique
>         address or a
>         >> previously negotiated bundle address.
>         >>
>         >> That option was removed as part of task (triggered by WGLC
>         comments etc)
>         >
>         > That seems like a pretty material change. Was there a call
>         for consensus on that?
>
>         No. But, the suggested changes were indicated on the list,
>         there were pull requests etc, so people were informed about it
>         and had a chance to comment/object.
>
>
>     Hmm... Ben, do you think these were properly surfaced to the WG?
>
>     -Ekr
>
>
>         > trying to simplifying the procedures. Currently the offerer
>         must either
>         > assign a bundle address (previously negotiated or new
>         suggested) or
>         > indicate it as bundle-only.
>         >
>         > At minimum this needs to be clearly stated
>
>         I need to modify the section, so I will add text about it.
>
>         Regards,
>
>         Christer
>
>
>


--------------7D1D400DEFBB0AE5F8E4F51A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/17/18 6:23 PM, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">Hi folks,<br>
        <br>
        This is an attempt to sharpen my point about talking about the<br>
        "BUNDLE address:port", when what we really mean is "use the<br>
        parameters from the "m=" section". Here's an example where this<br>
        creates a real problem. S 8.4 says:<br>
        <br>
           When an offerer receives an answer, if the answer contains a
        BUNDLE<br>
           group, the offerer MUST check that any bundled "m=" section
        in the<br>
           answer was indicated as bundled in the corresponding offer. 
        If there<br>
           is no mismatch, the offerer MUST use the offerer BUNDLE
        address:port,<br>
           selected by the answerer [Section 8.3.1], as the address for
        each<br>
           bundled "m=" section.<br>
        <br>
        Now consider the case where I am doing trickle ICE. The offer
        will<br>
        contain:<br>
        <br>
           a=<a class="moz-txt-link-freetext" href="group:BUNDLE">group:BUNDLE</a> foo bar<br>
           m=audio 9 RTP/AVP 97<br>
           c=IN IP4 0.0.0.0   <br>
           a=rtpmap:97 iLBC/8000<br>
           a=mid:foo<br>
           <br>
           m=video 9 RTP/AVP 98<br>
           c=IN IP4 0.0.0.0   <br>
           a=rtpmap:98 H261/90000<br>
           a=mid:bar<br>
        <br>
        Now, if the answer contains:<br>
        <br>
           a=<a class="moz-txt-link-freetext" href="group:BUNDLE">group:BUNDLE</a> foo bar<br>
        <br>
        Then the semantics are that we are supposed to use the
        parameters from<br>
        the m=audio line as the parameters for the bundle group.
        Specifically,<br>
        we are supposed to use the ICE candidates that belong to that
        m=audio<br>
        line. But there's no way to get that from this text.</div>
    </blockquote>
    True, but it's an inherent part of the definition of the BUNDLE-tag
    as described in the preceding sections covering the overall
    offer/answer procedures. <br>
    <br>
    <blockquote type="cite"
cite="mid:CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com">
      <div dir="ltr"> Ordinarily, if<br>
        each m=section contained a distinct address:port, then you might
        say<br>
        there was an implicit map from address:port to m= section
        parameters,<br>
        but in this case because all the address:port values are the
        same,<br>
        that's not possible, and so this paragraph just doesn't work.  </div>
    </blockquote>
    Why not ? The BUNDLE-tag in the answer indicates which "m=" section
    the answerer chose and hence you will use the corresponding BUNDLE
    address:port. <br>
    <br>
    <blockquote type="cite"
cite="mid:CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com">
      <div dir="ltr">The<br>
        right fix is to stop talking about the address:port and instead
        talk<br>
        about the m= section.<br>
        <br>
           When an offerer receives an answer, if the answer contains a
        BUNDLE<br>
           group, the offerer MUST check that any bundled "m=" section
        in the<br>
           answer was indicated as bundled in the corresponding offer. 
        If there<br>
           is no mismatch, the offerer MUST use the relevant parameters<br>
           [specific text from Suhas's draft needed here] from the<br>
           "m=" section indicated by the BUNDLE tag [again, it would be
        helpful<br>
           to have a better name here] for each "m=" section which is
        bundled<br>
           with it.<br>
        <br>
        There are other places where this creates confusion, but this is<br>
        a nice clear one.<br>
        <br>
      </div>
    </blockquote>
    I think we are saying the same thing here, but you are just asking
    for the BUNDLE-tag to be called out more explicitly as opposed to
    focusing on the BUNDLE address:port. Is that right ? <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming <br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com">
      <div dir="ltr">-Ekr<br>
        <br>
        <br>
        <br>
        <br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Tue, Apr 17, 2018 at 11:18 AM, Eric
          Rescorla <span dir="ltr">&lt;<a href="mailto:ekr@rtfm.com"
              target="_blank" moz-do-not-send="true">ekr@rtfm.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr"><br>
              <div class="gmail_extra"><br>
                <div class="gmail_quote">
                  <div>
                    <div class="h5">On Tue, Apr 17, 2018 at 11:11 AM,
                      Christer Holmberg <span dir="ltr">&lt;<a
                          href="mailto:christer.holmberg@ericsson.com"
                          target="_blank" moz-do-not-send="true">christer.holmberg@ericsson.<wbr>com</a>&gt;</span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div class="m_3202404282620514461HOEnZb">
                          <div class="m_3202404282620514461h5">Hi,<br>
                            <br>
                            ------------------------------<wbr>------------------------------<wbr>----------<br>
                            DISCUSS:<br>
                            ------------------------------<wbr>------------------------------<wbr>----------<br>
                            <br>
                            &gt;&gt;&gt;&gt;&gt;&gt; When an offerer
                            generates an offer, in which it wants to add
                            a new<br>
                            &gt;&gt;&gt;&gt;&gt;&gt; bundled "m="
                            section, the offerer MUST:<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;      o  Assign the
                            offerer BUNDLE address:port (previously
                            selected<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;         [Section
                            8.3.1] or newly suggested [Section 8.5.1])
                            to the added<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;         "m="
                            section; or<br>
                            &gt;&gt;&gt;&gt;&gt;<br>
                            &gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn't
                            sound right. You can't use the existing<br>
                            &gt;&gt;&gt;&gt;&gt; address:port, because
                            if the peer rejects BUNDLE but accepts the
                            m=<br>
                            &gt;&gt;&gt;&gt;&gt; section then it's
                            broken.<br>
                            &gt;&gt;&gt;&gt;<br>
                            &gt;&gt;&gt;&gt; Note that in this case the
                            usage of BUNDLE has already been negotiated.<br>
                            &gt;&gt;&gt;&gt; Then, if the answerer does
                            not accept the new m= section into the
                            BUNDLE<br>
                            &gt;&gt;&gt;&gt; group, it needs to send an
                            offer where it removes it, as described in<br>
                            &gt;&gt;&gt;&gt; section 8.3.3.<br>
                            &gt;&gt;&gt;<br>
                            &gt;&gt;&gt; Well, both of these options
                            correspond to insisting that the m= section<br>
                            &gt;&gt;&gt; be in the BUNDLE group. If I
                            just want to suggest it, I would have to
                            provide<br>
                            &gt;&gt;&gt; a fresh unique address. Or are
                            you saying that's impossible.<br>
                            &gt;&gt;&gt;<br>
                            &gt;&gt; Yes.<br>
                            &gt;&gt;<br>
                            &gt;&gt; Previously, when the offerer wanted
                            to add a new m- section to a BUNDLE<br>
                            &gt;&gt; group, it had to choice of either
                            assigning a unique address or a<br>
                            &gt;&gt; previously negotiated bundle
                            address.<br>
                            &gt;&gt;<br>
                            &gt;&gt; That option was removed as part of
                            task (triggered by WGLC comments etc)<br>
                            &gt;<br>
                            &gt; That seems like a pretty material
                            change. Was there a call for consensus on
                            that?<br>
                            <br>
                          </div>
                        </div>
                        No. But, the suggested changes were indicated on
                        the list, there were pull requests etc, so
                        people were informed about it and had a chance
                        to comment/object.<br>
                      </blockquote>
                      <div><br>
                      </div>
                    </div>
                  </div>
                  <div>Hmm... Ben, do you think these were properly
                    surfaced to the WG?</div>
                  <div><br>
                  </div>
                  <div>-Ekr</div>
                  <span class="">
                    <div><br>
                    </div>
                    <div><br>
                      <span></span><span></span></div>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
                        &gt; trying to simplifying the procedures.
                        Currently the offerer must either<br>
                        &gt; assign a bundle address (previously
                        negotiated or new suggested) or<br>
                        &gt; indicate it as bundle-only.<br>
                        &gt;<br>
                        &gt; At minimum this needs to be clearly stated<br>
                        <br>
                      </span>I need to modify the section, so I will add
                      text about it.<br>
                      <br>
                      Regards,<br>
                      <br>
                      Christer<br>
                      <br>
                    </blockquote>
                  </span></div>
                <br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------7D1D400DEFBB0AE5F8E4F51A--


From nobody Wed Apr 25 01:24:26 2018
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 CB24C1270AE for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 01:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01] 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 UrL7-RP3s27i for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 01:24:21 -0700 (PDT)
Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 B61E512708C for <mmusic@ietf.org>; Wed, 25 Apr 2018 01:24:20 -0700 (PDT)
Received: by mail-ot0-x233.google.com with SMTP id p2-v6so24377591otf.3 for <mmusic@ietf.org>; Wed, 25 Apr 2018 01:24: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=+f4AfRm13B0Ee12fcXOZQvmKga168/+/YfXdOgC61eA=; b=tOF1kFvMN9hZ3qCEYmebvs7m+d8aA3Pi/89nKZ/zbfvT+Afjn68xjlWn57EKnrrkM2 wOYzPhQ9SvBweR5NfrATr4iZVKPdO8wfeXDV7kOBDt57/xQBCKmfWb8LDXKu4yc/S1Ru t9khGPtWD9ANw89xhxCK5S+SSoRRA4/145mZ5NAsyfjqhb4JihNuM6r7oZZF0rke/bek s2QreFv2+z+vBnfBamjQDq9KXPCRqD2cw1lHyEtlXHDjsy3PaK52J4Xo2ZrGORT+rdML mTgJmNcM3IKqbO0pZevm5z/Y+Nf/xRBrqaojaqYp0dDxfbpRSoint4PLYwA+q9y6lcTm pD2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+f4AfRm13B0Ee12fcXOZQvmKga168/+/YfXdOgC61eA=; b=p/RZXqqzW4lDDny3X9XaiokcTFqWJD583l1MsEHM485fEBJXLIB0vjfA/CB/ewCKdP 0nTBIdIxbyEQ0+4vpxn+VWkEU00Y6kKF+6rZjA8odcc5ALm75/amiVNz9TTBbFaQKUZg 8B7r700B/vlxV1rFRD8otLcxlM2g+H7hi4rncyw4wcyfsHYWlRI4XMfbTibvfmNyFt6r jE9IoW6RVWryeV9WQRP+40huTmcT/xh5ru6TrzWGh0IVkyYwhLexoV8dOGkd2Dq4nzwR cp7WaT9VytnQp1t0ZGI4Jh11qNyu32zeHvxR9A55pxFOhk9zrHQYvC+r72SJG4n1dVRl Z+Rg==
X-Gm-Message-State: ALQs6tBjsJQY265QONc64wr9fIszTsJ4p1FftLOCmcXpo1fgXnxK6UqG NmNlG8yLFHbuSYLi0PlOIa2jLreocr7vFIXv3iAqZA==
X-Google-Smtp-Source: AIpwx4/rIc6PB3vGytI4zDktRCB4qV5LbRS1oJHWd5vmhpUvZgE2yEAQRXEf5pZNwkJTJDssE+6vW5VTcw27fmH4Kb0=
X-Received: by 2002:a9d:3b03:: with SMTP id z3-v6mr17900970otb.392.1524644660062;  Wed, 25 Apr 2018 01:24:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Wed, 25 Apr 2018 01:23:39 -0700 (PDT)
In-Reply-To: <95979e47-0199-99c4-383a-8a26cb7bbde6@cisco.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com> <95979e47-0199-99c4-383a-8a26cb7bbde6@cisco.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 25 Apr 2018 01:23:39 -0700
Message-ID: <CABcZeBMfb3C=9ho6xAAB+Dp+KPP3Jvfdm13zd4VUF6Eyje8wRQ@mail.gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005f3f1d056aa7ff73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/BMcATqllDZ3vaD9qzRgg_5BQv0E>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 08:24:24 -0000

--0000000000005f3f1d056aa7ff73
Content-Type: text/plain; charset="UTF-8"

On Tue, Apr 24, 2018 at 8:11 AM, Flemming Andreasen <fandreas@cisco.com>
wrote:

>
>
> On 4/17/18 6:23 PM, Eric Rescorla wrote:
>
> Hi folks,
>
> This is an attempt to sharpen my point about talking about the
> "BUNDLE address:port", when what we really mean is "use the
> parameters from the "m=" section". Here's an example where this
> creates a real problem. S 8.4 says:
>
>    When an offerer receives an answer, if the answer contains a BUNDLE
>    group, the offerer MUST check that any bundled "m=" section in the
>    answer was indicated as bundled in the corresponding offer.  If there
>    is no mismatch, the offerer MUST use the offerer BUNDLE address:port,
>    selected by the answerer [Section 8.3.1], as the address for each
>    bundled "m=" section.
>
> Now consider the case where I am doing trickle ICE. The offer will
> contain:
>
>    a=group:BUNDLE foo bar
>    m=audio 9 RTP/AVP 97
>    c=IN IP4 0.0.0.0
>    a=rtpmap:97 iLBC/8000
>    a=mid:foo
>
>    m=video 9 RTP/AVP 98
>    c=IN IP4 0.0.0.0
>    a=rtpmap:98 H261/90000
>    a=mid:bar
>
> Now, if the answer contains:
>
>    a=group:BUNDLE foo bar
>
> Then the semantics are that we are supposed to use the parameters from
> the m=audio line as the parameters for the bundle group. Specifically,
> we are supposed to use the ICE candidates that belong to that m=audio
> line. But there's no way to get that from this text.
>
> True, but it's an inherent part of the definition of the BUNDLE-tag as
> described in the preceding sections covering the overall offer/answer
> procedures.
>

But this text doesn't say anything about the BUNDLE-tag. It says to select
the address.

>
> Ordinarily, if
> each m=section contained a distinct address:port, then you might say
> there was an implicit map from address:port to m= section parameters,
> but in this case because all the address:port values are the same,
> that's not possible, and so this paragraph just doesn't work.
>
> Why not ? The BUNDLE-tag in the answer indicates which "m=" section the
> answerer chose and hence you will use the corresponding BUNDLE
> address:port.
>

But that's not in this text.


> The
> right fix is to stop talking about the address:port and instead talk
> about the m= section.
>
>    When an offerer receives an answer, if the answer contains a BUNDLE
>    group, the offerer MUST check that any bundled "m=" section in the
>    answer was indicated as bundled in the corresponding offer.  If there
>    is no mismatch, the offerer MUST use the relevant parameters
>    [specific text from Suhas's draft needed here] from the
>    "m=" section indicated by the BUNDLE tag [again, it would be helpful
>    to have a better name here] for each "m=" section which is bundled
>    with it.
>
> There are other places where this creates confusion, but this is
> a nice clear one.
>
> I think we are saying the same thing here, but you are just asking for the
> BUNDLE-tag to be called out more explicitly as opposed to focusing on the
> BUNDLE address:port. Is that right ?
>

Yes, more or less. I'm asking for it to be the primary unit of analysis.

-Ekr

>
> Thanks
>
> -- Flemming
>
>
> -Ekr
>
>
>
>
>
> On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>>
>> On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg <
>> christer.holmberg@ericsson.com> wrote:
>>
>>> Hi,
>>>
>>> ----------------------------------------------------------------------
>>> DISCUSS:
>>> ----------------------------------------------------------------------
>>>
>>> >>>>>> When an offerer generates an offer, in which it wants to add a new
>>> >>>>>> bundled "m=" section, the offerer MUST:
>>> >>>>>>
>>> >>>>>>      o  Assign the offerer BUNDLE address:port (previously
>>> selected
>>> >>>>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to
>>> the added
>>> >>>>>>         "m=" section; or
>>> >>>>>
>>> >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>> >>>>> address:port, because if the peer rejects BUNDLE but accepts the m=
>>> >>>>> section then it's broken.
>>> >>>>
>>> >>>> Note that in this case the usage of BUNDLE has already been
>>> negotiated.
>>> >>>> Then, if the answerer does not accept the new m= section into the
>>> BUNDLE
>>> >>>> group, it needs to send an offer where it removes it, as described
>>> in
>>> >>>> section 8.3.3.
>>> >>>
>>> >>> Well, both of these options correspond to insisting that the m=
>>> section
>>> >>> be in the BUNDLE group. If I just want to suggest it, I would have
>>> to provide
>>> >>> a fresh unique address. Or are you saying that's impossible.
>>> >>>
>>> >> Yes.
>>> >>
>>> >> Previously, when the offerer wanted to add a new m- section to a
>>> BUNDLE
>>> >> group, it had to choice of either assigning a unique address or a
>>> >> previously negotiated bundle address.
>>> >>
>>> >> That option was removed as part of task (triggered by WGLC comments
>>> etc)
>>> >
>>> > That seems like a pretty material change. Was there a call for
>>> consensus on that?
>>>
>>> No. But, the suggested changes were indicated on the list, there were
>>> pull requests etc, so people were informed about it and had a chance to
>>> comment/object.
>>>
>>
>> Hmm... Ben, do you think these were properly surfaced to the WG?
>>
>> -Ekr
>>
>>
>> > trying to simplifying the procedures. Currently the offerer must either
>>> > assign a bundle address (previously negotiated or new suggested) or
>>> > indicate it as bundle-only.
>>> >
>>> > At minimum this needs to be clearly stated
>>>
>>> I need to modify the section, so I will add text about it.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>
>
>

--0000000000005f3f1d056aa7ff73
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 Tue, Apr 24, 2018 at 8:11 AM, Flemming Andreasen <span dir=3D"ltr">&=
lt;<a href=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@cisco.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><div><div class=3D"h5">
    <br>
    <br>
    <div class=3D"m_9125571528848928878moz-cite-prefix">On 4/17/18 6:23 PM,=
 Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">Hi folks,<br>
        <br>
        This is an attempt to sharpen my point about talking about the<br>
        &quot;BUNDLE address:port&quot;, when what we really mean is &quot;=
use the<br>
        parameters from the &quot;m=3D&quot; section&quot;. Here&#39;s an e=
xample where this<br>
        creates a real problem. S 8.4 says:<br>
        <br>
        =C2=A0=C2=A0 When an offerer receives an answer, if the answer cont=
ains a
        BUNDLE<br>
        =C2=A0=C2=A0 group, the offerer MUST check that any bundled &quot;m=
=3D&quot; section
        in the<br>
        =C2=A0=C2=A0 answer was indicated as bundled in the corresponding o=
ffer.=C2=A0
        If there<br>
        =C2=A0=C2=A0 is no mismatch, the offerer MUST use the offerer BUNDL=
E
        address:port,<br>
        =C2=A0=C2=A0 selected by the answerer [Section 8.3.1], as the addre=
ss for
        each<br>
        =C2=A0=C2=A0 bundled &quot;m=3D&quot; section.<br>
        <br>
        Now consider the case where I am doing trickle ICE. The offer
        will<br>
        contain:<br>
        <br>
        =C2=A0=C2=A0 a=3D<a class=3D"m_9125571528848928878moz-txt-link-free=
text">group:BUNDLE</a> foo bar<br>
        =C2=A0=C2=A0 m=3Daudio 9 RTP/AVP 97<br>
        =C2=A0=C2=A0 c=3DIN IP4 0.0.0.0=C2=A0=C2=A0 <br>
        =C2=A0=C2=A0 a=3Drtpmap:97 iLBC/8000<br>
        =C2=A0=C2=A0 a=3Dmid:foo<br>
        =C2=A0=C2=A0 <br>
        =C2=A0=C2=A0 m=3Dvideo 9 RTP/AVP 98<br>
        =C2=A0=C2=A0 c=3DIN IP4 0.0.0.0=C2=A0=C2=A0 <br>
        =C2=A0=C2=A0 a=3Drtpmap:98 H261/90000<br>
        =C2=A0=C2=A0 a=3Dmid:bar<br>
        <br>
        Now, if the answer contains:<br>
        <br>
        =C2=A0=C2=A0 a=3D<a class=3D"m_9125571528848928878moz-txt-link-free=
text">group:BUNDLE</a> foo bar<br>
        <br>
        Then the semantics are that we are supposed to use the
        parameters from<br>
        the m=3Daudio line as the parameters for the bundle group.
        Specifically,<br>
        we are supposed to use the ICE candidates that belong to that
        m=3Daudio<br>
        line. But there&#39;s no way to get that from this text.</div>
    </blockquote></div></div>
    True, but it&#39;s an inherent part of the definition of the BUNDLE-tag
    as described in the preceding sections covering the overall
    offer/answer procedures. <br></div></blockquote><div><br></div><div>But=
 this text doesn&#39;t say anything about the BUNDLE-tag. It says to select=
 the address.<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000"=
 bgcolor=3D"#FFFFFF"><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr"> Ordinarily, if<br>
        each m=3Dsection contained a distinct address:port, then you might
        say<br>
        there was an implicit map from address:port to m=3D section
        parameters,<br>
        but in this case because all the address:port values are the
        same,<br>
        that&#39;s not possible, and so this paragraph just doesn&#39;t wor=
k.=C2=A0 </div>
    </blockquote></span>
    Why not ? The BUNDLE-tag in the answer indicates which &quot;m=3D&quot;=
 section
    the answerer chose and hence you will use the corresponding BUNDLE
    address:port. <br></div></blockquote><div><br></div><div>But that&#39;s=
 not in this text.</div><div> <br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div=
 text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">The<br>
        right fix is to stop talking about the address:port and instead
        talk<br>
        about the m=3D section.<br>
        <br>
        =C2=A0=C2=A0 When an offerer receives an answer, if the answer cont=
ains a
        BUNDLE<br>
        =C2=A0=C2=A0 group, the offerer MUST check that any bundled &quot;m=
=3D&quot; section
        in the<br>
        =C2=A0=C2=A0 answer was indicated as bundled in the corresponding o=
ffer.=C2=A0
        If there<br>
        =C2=A0=C2=A0 is no mismatch, the offerer MUST use the relevant para=
meters<br>
        =C2=A0=C2=A0 [specific text from Suhas&#39;s draft needed here] fro=
m the<br>
        =C2=A0=C2=A0 &quot;m=3D&quot; section indicated by the BUNDLE tag [=
again, it would be
        helpful<br>
        =C2=A0=C2=A0 to have a better name here] for each &quot;m=3D&quot; =
section which is
        bundled<br>
        =C2=A0=C2=A0 with it.<br>
        <br>
        There are other places where this creates confusion, but this is<br=
>
        a nice clear one.<br>
        <br>
      </div>
    </blockquote></span>
    I think we are saying the same thing here, but you are just asking
    for the BUNDLE-tag to be called out more explicitly as opposed to
    focusing on the BUNDLE address:port. Is that right ? <br></div></blockq=
uote><div><br></div><div>Yes, more or less. I&#39;m asking for it to be the=
 primary unit of analysis.</div><div><br></div><div>-Ekr<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <br>
    Thanks <br><span class=3D"HOEnZb"><font color=3D"#888888">
    <br>
    -- Flemming <br></font></span><div><div class=3D"h5">
    <br>
    <br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">-Ekr<br>
        <br>
        <br>
        <br>
        <br>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Tue, Apr 17, 2018 at 11:18 AM, Eric
          Rescorla <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" ta=
rget=3D"_blank">ekr@rtfm.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div dir=3D"ltr"><br>
              <div class=3D"gmail_extra"><br>
                <div class=3D"gmail_quote">
                  <div>
                    <div class=3D"m_9125571528848928878h5">On Tue, Apr 17, =
2018 at 11:11 AM,
                      Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@er=
icsson.co<wbr>m</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"m_9125571528848928878m_32024042826205=
14461HOEnZb">
                          <div class=3D"m_9125571528848928878m_320240428262=
0514461h5">Hi,<br>
                            <br>
                            ------------------------------<wbr>------------=
------------------<wbr>----------<br>
                            DISCUSS:<br>
                            ------------------------------<wbr>------------=
------------------<wbr>----------<br>
                            <br>
                            &gt;&gt;&gt;&gt;&gt;&gt;=C2=A0When an offerer
                            generates an offer, in which it wants to add
                            a new<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;=C2=A0bundled &quot;m=
=3D&quot;
                            section, the offerer MUST:<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=
=C2=A0 Assign the
                            offerer BUNDLE address:port (previously
                            selected<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0[Section
                            8.3.1] or newly suggested [Section 8.5.1])
                            to the added<br>
                            &gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0&quot;m=3D&quot;
                            section; or<br>
                            &gt;&gt;&gt;&gt;&gt;<br>
                            &gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn&#39;=
t
                            sound right. You can&#39;t use the existing<br>
                            &gt;&gt;&gt;&gt;&gt; address:port, because
                            if the peer rejects BUNDLE but accepts the
                            m=3D<br>
                            &gt;&gt;&gt;&gt;&gt; section then it&#39;s
                            broken.<br>
                            &gt;&gt;&gt;&gt;<br>
                            &gt;&gt;&gt;&gt; Note that in this case the
                            usage of BUNDLE has already been negotiated.<br=
>
                            &gt;&gt;&gt;&gt; Then, if the answerer does
                            not accept the new m=3D section into the
                            BUNDLE<br>
                            &gt;&gt;&gt;&gt; group, it needs to send an
                            offer where it removes it, as described in<br>
                            &gt;&gt;&gt;&gt; section 8.3.3.<br>
                            &gt;&gt;&gt;<br>
                            &gt;&gt;&gt; Well, both of these options
                            correspond to insisting that the m=3D section<b=
r>
                            &gt;&gt;&gt; be in the BUNDLE group. If I
                            just want to suggest it, I would have to
                            provide<br>
                            &gt;&gt;&gt; a fresh unique address. Or are
                            you saying that&#39;s impossible.<br>
                            &gt;&gt;&gt;<br>
                            &gt;&gt; Yes.<br>
                            &gt;&gt;<br>
                            &gt;&gt; Previously, when the offerer wanted
                            to add a new m- section to a BUNDLE<br>
                            &gt;&gt; group, it had to choice of either
                            assigning a unique address or a<br>
                            &gt;&gt; previously negotiated bundle
                            address.<br>
                            &gt;&gt;<br>
                            &gt;&gt; That option was removed as part of
                            task (triggered by WGLC comments etc)<br>
                            &gt;<br>
                            &gt; That seems like a pretty material
                            change. Was there a call for consensus on
                            that?<br>
                            <br>
                          </div>
                        </div>
                        No. But, the suggested changes were indicated on
                        the list, there were pull requests etc, so
                        people were informed about it and had a chance
                        to comment/object.<br>
                      </blockquote>
                      <div><br>
                      </div>
                    </div>
                  </div>
                  <div>Hmm... Ben, do you think these were properly
                    surfaced to the WG?</div>
                  <div><br>
                  </div>
                  <div>-Ekr</div>
                  <span>
                    <div><br>
                    </div>
                    <div><br>
                      <span></span><span></span></div>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
                        &gt; trying to simplifying the procedures.
                        Currently the offerer must either<br>
                        &gt; assign a bundle address (previously
                        negotiated or new suggested) or<br>
                        &gt; indicate it as bundle-only.<br>
                        &gt;<br>
                        &gt; At minimum this needs to be clearly stated<br>
                        <br>
                      </span>I need to modify the section, so I will add
                      text about it.<br>
                      <br>
                      Regards,<br>
                      <br>
                      Christer<br>
                      <br>
                    </blockquote>
                  </span></div>
                <br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </div></div></div>

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

--0000000000005f3f1d056aa7ff73--


From nobody Wed Apr 25 04:36:09 2018
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 AA3DA1289B0; Wed, 25 Apr 2018 04:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2XxKuLASvxZQ; Wed, 25 Apr 2018 04:36:00 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 759681275AB; Wed, 25 Apr 2018 04:36:00 -0700 (PDT)
Received: from [130.209.247.112] (port=65412 helo=mangole.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1fBIiI-0006ju-EF; Wed, 25 Apr 2018 12:35:56 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se>
Date: Wed, 25 Apr 2018 12:35:44 +0100
Cc: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "fandreas@cisco.com" <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <44221E08-773F-4120-8C68-6B78B0FDC9A4@csperkins.org>
References: <152365238120.5549.12322147978999456800.idtracker@ietfa.amsl.com> <7594FB04B1934943A5C02806D1A2204B72E6E46B@ESESSMB109.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vBmdS5ie_SRi8dfGgmyP07Gc8A4>
Subject: Re: [MMUSIC] Benjamin Kaduk's No Objection on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with COMMENT)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 11:36:03 -0000

[Apologies for the slow response]

> On 14 Apr 2018, at 16:06, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Benjamin,
>=20
> Thank You for the review! Please see inline.
>=20
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
=E2=80=A6
>> In Section 10.2, page 23, I appreciate the description of the payload =
type/m=3D mapping used by legacy implementations, but I worry that there =
may not be sufficient description of when an SDP participant should take =
the care to ensure the uniqueness of the mapping (versus when the legacy =
considerations can be ignored).
>=20
> Section 10 was "outsourced", so I will ask the folks who provided the =
text to reply :)
>=20
> Magnus, Colin?


The legacy considerations can be ignored when both participants =
understand and use the identification-tag carried in the RTP and RTCP =
packets. If the identification-tag is not used, or not understood, then =
the comments about associating RTP flows with =E2=80=9Cm=3D=E2=80=9C =
sections based on payload type values apply.

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





From nobody Wed Apr 25 04:44:52 2018
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 E990B1275AB for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 04:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9N99W1TqxCgS for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 04:44: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 CF9081200A0 for <mmusic@ietf.org>; Wed, 25 Apr 2018 04:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524656685; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=L3/WN8kn2MB5ih9U5rSBVwxs7vO2/7tKMK2Na8eviWs=; b=Qf7DR2PRuIrZQi36HMMVy+GBnKlMRzUgI3WbVY7ffaxdxT0TL4I5KkFmVNNekoq4 rmWSL7r5E/PlJ4rVZUH25EYSQoE4+OtTROfermKAY6rXTxh7SnCvF+FJbM/1jvMW Mea6qcz2uAYlMA7hc0Qk2mxIDIgvQF3Y260KAauGfL0=;
X-AuditID: c1b4fb2d-daba19c0000068bb-6f-5ae06a2c60c9
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id AA.D1.26811.C2A60EA5; Wed, 25 Apr 2018 13:44:44 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0382.000; Wed, 25 Apr 2018 13:44:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Eric Rescorla <ekr@rtfm.com>, Flemming Andreasen <fandreas@cisco.com>
CC: The IESG <iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
Thread-Index: AQHT1hqq+aK53d5eAEK3FlM1W8whYaQE1oWAgAA55ID///3OAIAAM2Cw///hngCAAER7AIAKh74AgAEgQoCAAGsXAA==
Date: Wed, 25 Apr 2018 11:44:37 +0000
Message-ID: <D70641FF.2EC5B%christer.holmberg@ericsson.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com> <95979e47-0199-99c4-383a-8a26cb7bbde6@cisco.com> <CABcZeBMfb3C=9ho6xAAB+Dp+KPP3Jvfdm13zd4VUF6Eyje8wRQ@mail.gmail.com>
In-Reply-To: <CABcZeBMfb3C=9ho6xAAB+Dp+KPP3Jvfdm13zd4VUF6Eyje8wRQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D70641FF2EC5Bchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKIsWRmVeSWpSXmKPExsUyM2K7q65O1oMog3OvbSymz3rHZrHi9Tl2 i/cXdC1m/JnIbHF+53omi6nLH7M4sHlM+b2R1WPJkp9MHpMftzEHMEdx2aSk5mSWpRbp2yVw ZVy6eJitYPFMxoq5d/uYGhjnNzJ2MXJySAiYSJzd9pa9i5GLQ0jgCKPEh84OJghnMaPEvbZ9 bF2MHBxsAhYS3f+0QUwRAU+JK/f9QEqYBR4DlbxsZwcZJCxQK3GsYQcTiC0iUCdxas5aZgg7 S6L7ySswm0VAVWLv6xdgNbwC1hJvr9xgg9h1nEVi3vIuNpAEp0CgxN67u1hAbEYBMYnvp9aA NTALiEvcejKfCeJqAYkle84zQ9iiEi8f/2MFsUUF9CQ2nLjNDnKohICSxO0NThCtCRLr981k hNgrKHFy5hOWCYyis5BMnYWkbBaSMoi4gcT7c/OZIWxtiWULX0PZ+hIbv5wFqucAsq0lXh4V Q1aygJFjFaNocWpxcW66kbFealFmcnFxfp5eXmrJJkZg5B7c8lt3B+Pq146HGAU4GJV4eC9H PIgSYk0sK67MPcQowcGsJMK7V+5elBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFevVV7ooQE0hNL UrNTUwtSi2CyTBycUg2MXMzyTsqPJ06RfLHK4/rzvVKH/37RuadQOeVgocnrR99+7tnMns8s eMJ842XfB04Ob+1v1yul7q3PbhO6u8qBia3lTlzdx7pfsVMbL1qyL587Md6r8njitT0LAh2f nLrLxR39bhf3VkWvNy+VRQKSzipeW8GefMn41JI78yqcl/rvSN8rsf+3jxJLcUaioRZzUXEi AGtFi1vYAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/E1rDyVPojyzJ9mu-ldMRj71vtxs>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 11:44:50 -0000

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

Hi,

As it would not be very convenient to talk about =93the m=3D section identi=
fied by the BUNDLE-tag=94, there has been a suggestion to e.g., talk about =
=93the lead m- section=94.

My suggestion would be to talk about =93tagged m- section=94 or =93BUNDLE-t=
agged m- section=94. We don=92t need to add more fancy words into the docum=
ent :)

Regards,

Christer

From: Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtfm.com>>
Date: Wednesday 25 April 2018 at 11:23
To: Flemming Andreasen <fandreas@cisco.com<mailto:fandreas@cisco.com>>
Cc: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>, "iesg@ietf.org<mailto:iesg@ietf.org>" <iesg@ietf.org<ma=
ilto:iesg@ietf.org>>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org<ma=
ilto:draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>" <draft-ietf-mmusic=
-sdp-bundle-negotiation@ietf.org<mailto:draft-ietf-mmusic-sdp-bundle-negoti=
ation@ietf.org>>, "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <=
mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>, "mmusic@ietf.org<ma=
ilto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Subject: Re: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negoti=
ation-49: (with DISCUSS and COMMENT) - DISCUSS



On Tue, Apr 24, 2018 at 8:11 AM, Flemming Andreasen <fandreas@cisco.com<mai=
lto:fandreas@cisco.com>> wrote:


On 4/17/18 6:23 PM, Eric Rescorla wrote:
Hi folks,

This is an attempt to sharpen my point about talking about the
"BUNDLE address:port", when what we really mean is "use the
parameters from the "m=3D" section". Here's an example where this
creates a real problem. S 8.4 says:

   When an offerer receives an answer, if the answer contains a BUNDLE
   group, the offerer MUST check that any bundled "m=3D" section in the
   answer was indicated as bundled in the corresponding offer.  If there
   is no mismatch, the offerer MUST use the offerer BUNDLE address:port,
   selected by the answerer [Section 8.3.1], as the address for each
   bundled "m=3D" section.

Now consider the case where I am doing trickle ICE. The offer will
contain:

   a=3Dgroup:BUNDLE foo bar
   m=3Daudio 9 RTP/AVP 97
   c=3DIN IP4 0.0.0.0
   a=3Drtpmap:97 iLBC/8000
   a=3Dmid:foo

   m=3Dvideo 9 RTP/AVP 98
   c=3DIN IP4 0.0.0.0
   a=3Drtpmap:98 H261/90000
   a=3Dmid:bar

Now, if the answer contains:

   a=3Dgroup:BUNDLE foo bar

Then the semantics are that we are supposed to use the parameters from
the m=3Daudio line as the parameters for the bundle group. Specifically,
we are supposed to use the ICE candidates that belong to that m=3Daudio
line. But there's no way to get that from this text.
True, but it's an inherent part of the definition of the BUNDLE-tag as desc=
ribed in the preceding sections covering the overall offer/answer procedure=
s.

But this text doesn't say anything about the BUNDLE-tag. It says to select =
the address.

Ordinarily, if
each m=3Dsection contained a distinct address:port, then you might say
there was an implicit map from address:port to m=3D section parameters,
but in this case because all the address:port values are the same,
that's not possible, and so this paragraph just doesn't work.
Why not ? The BUNDLE-tag in the answer indicates which "m=3D" section the a=
nswerer chose and hence you will use the corresponding BUNDLE address:port.

But that's not in this text.


The
right fix is to stop talking about the address:port and instead talk
about the m=3D section.

   When an offerer receives an answer, if the answer contains a BUNDLE
   group, the offerer MUST check that any bundled "m=3D" section in the
   answer was indicated as bundled in the corresponding offer.  If there
   is no mismatch, the offerer MUST use the relevant parameters
   [specific text from Suhas's draft needed here] from the
   "m=3D" section indicated by the BUNDLE tag [again, it would be helpful
   to have a better name here] for each "m=3D" section which is bundled
   with it.

There are other places where this creates confusion, but this is
a nice clear one.

I think we are saying the same thing here, but you are just asking for the =
BUNDLE-tag to be called out more explicitly as opposed to focusing on the B=
UNDLE address:port. Is that right ?

Yes, more or less. I'm asking for it to be the primary unit of analysis.

-Ekr

Thanks

-- Flemming


-Ekr





On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rt=
fm.com>> wrote:


On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg <christer.holmberg@eric=
sson.com<mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

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

>>>>>> When an offerer generates an offer, in which it wants to add a new
>>>>>> bundled "m=3D" section, the offerer MUST:
>>>>>>
>>>>>>      o  Assign the offerer BUNDLE address:port (previously selected
>>>>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to the a=
dded
>>>>>>         "m=3D" section; or
>>>>>
>>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>>>> address:port, because if the peer rejects BUNDLE but accepts the m=3D
>>>>> section then it's broken.
>>>>
>>>> Note that in this case the usage of BUNDLE has already been negotiated=
.
>>>> Then, if the answerer does not accept the new m=3D section into the BU=
NDLE
>>>> group, it needs to send an offer where it removes it, as described in
>>>> section 8.3.3.
>>>
>>> Well, both of these options correspond to insisting that the m=3D secti=
on
>>> be in the BUNDLE group. If I just want to suggest it, I would have to p=
rovide
>>> a fresh unique address. Or are you saying that's impossible.
>>>
>> Yes.
>>
>> Previously, when the offerer wanted to add a new m- section to a BUNDLE
>> group, it had to choice of either assigning a unique address or a
>> previously negotiated bundle address.
>>
>> That option was removed as part of task (triggered by WGLC comments etc)
>
> That seems like a pretty material change. Was there a call for consensus =
on that?

No. But, the suggested changes were indicated on the list, there were pull =
requests etc, so people were informed about it and had a chance to comment/=
object.

Hmm... Ben, do you think these were properly surfaced to the WG?

-Ekr


> trying to simplifying the procedures. Currently the offerer must either
> assign a bundle address (previously negotiated or new suggested) or
> indicate it as bundle-only.
>
> At minimum this needs to be clearly stated

I need to modify the section, so I will add text about it.

Regards,

Christer






--_000_D70641FF2EC5Bchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <DDDA309DFA9A9649916FA653AC4CC77B@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>As it would not be very convenient to talk about =93the m=3D section i=
dentified by the BUNDLE-tag=94, there has been a suggestion to e.g., talk a=
bout =93the lead m- section=94.</div>
<div><br>
</div>
<div>My suggestion would be to talk about =93tagged m- section=94 or =93BUN=
DLE-tagged m- section=94. We don=92t need to add more fancy words into the =
document :)</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>Eric Rescorla &lt;<a href=3D"=
mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday 25 April 2018 at 11=
:23<br>
<span style=3D"font-weight:bold">To: </span>Flemming Andreasen &lt;<a href=
=3D"mailto:fandreas@cisco.com">fandreas@cisco.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;, &quot;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&quot; &lt;=
<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>&gt;, &quot;<a href=3D"ma=
ilto:draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org">draft-ietf-mmusic-s=
dp-bundle-negotiation@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org">d=
raft-ietf-mmusic-sdp-bundle-negotiation@ietf.org</a>&gt;, &quot;<a href=3D"=
mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</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: Eric Rescorla's Discus=
s on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT=
) - DISCUSS<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Apr 24, 2018 at 8:11 AM, 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"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF">
<div>
<div class=3D"h5"><br>
<br>
<div class=3D"m_9125571528848928878moz-cite-prefix">On 4/17/18 6:23 PM, Eri=
c Rescorla wrote:<br>
</div>
<blockquote type=3D"cite">
<div dir=3D"ltr">Hi folks,<br>
<br>
This is an attempt to sharpen my point about talking about the<br>
&quot;BUNDLE address:port&quot;, when what we really mean is &quot;use the<=
br>
parameters from the &quot;m=3D&quot; section&quot;. Here's an example where=
 this<br>
creates a real problem. S 8.4 says:<br>
<br>
&nbsp;&nbsp; When an offerer receives an answer, if the answer contains a B=
UNDLE<br>
&nbsp;&nbsp; group, the offerer MUST check that any bundled &quot;m=3D&quot=
; section in the<br>
&nbsp;&nbsp; answer was indicated as bundled in the corresponding offer.&nb=
sp; If there<br>
&nbsp;&nbsp; is no mismatch, the offerer MUST use the offerer BUNDLE addres=
s:port,<br>
&nbsp;&nbsp; selected by the answerer [Section 8.3.1], as the address for e=
ach<br>
&nbsp;&nbsp; bundled &quot;m=3D&quot; section.<br>
<br>
Now consider the case where I am doing trickle ICE. The offer will<br>
contain:<br>
<br>
&nbsp;&nbsp; a=3D<a class=3D"m_9125571528848928878moz-txt-link-freetext">gr=
oup:BUNDLE</a> foo bar<br>
&nbsp;&nbsp; m=3Daudio 9 RTP/AVP 97<br>
&nbsp;&nbsp; c=3DIN IP4 0.0.0.0&nbsp;&nbsp; <br>
&nbsp;&nbsp; a=3Drtpmap:97 iLBC/8000<br>
&nbsp;&nbsp; a=3Dmid:foo<br>
&nbsp;&nbsp; <br>
&nbsp;&nbsp; m=3Dvideo 9 RTP/AVP 98<br>
&nbsp;&nbsp; c=3DIN IP4 0.0.0.0&nbsp;&nbsp; <br>
&nbsp;&nbsp; a=3Drtpmap:98 H261/90000<br>
&nbsp;&nbsp; a=3Dmid:bar<br>
<br>
Now, if the answer contains:<br>
<br>
&nbsp;&nbsp; a=3D<a class=3D"m_9125571528848928878moz-txt-link-freetext">gr=
oup:BUNDLE</a> foo bar<br>
<br>
Then the semantics are that we are supposed to use the parameters from<br>
the m=3Daudio line as the parameters for the bundle group. Specifically,<br=
>
we are supposed to use the ICE candidates that belong to that m=3Daudio<br>
line. But there's no way to get that from this text.</div>
</blockquote>
</div>
</div>
True, but it's an inherent part of the definition of the BUNDLE-tag as desc=
ribed in the preceding sections covering the overall offer/answer procedure=
s.
<br>
</div>
</blockquote>
<div><br>
</div>
<div>But this text doesn't say anything about the BUNDLE-tag. It says to se=
lect the address.<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D""><br>
<blockquote type=3D"cite">
<div dir=3D"ltr">Ordinarily, if<br>
each m=3Dsection contained a distinct address:port, then you might say<br>
there was an implicit map from address:port to m=3D section parameters,<br>
but in this case because all the address:port values are the same,<br>
that's not possible, and so this paragraph just doesn't work.&nbsp; </div>
</blockquote>
</span>Why not ? The BUNDLE-tag in the answer indicates which &quot;m=3D&qu=
ot; section the answerer chose and hence you will use the corresponding BUN=
DLE address:port.
<br>
</div>
</blockquote>
<div><br>
</div>
<div>But that's not in this text.</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D""><br>
<blockquote type=3D"cite">
<div dir=3D"ltr">The<br>
right fix is to stop talking about the address:port and instead talk<br>
about the m=3D section.<br>
<br>
&nbsp;&nbsp; When an offerer receives an answer, if the answer contains a B=
UNDLE<br>
&nbsp;&nbsp; group, the offerer MUST check that any bundled &quot;m=3D&quot=
; section in the<br>
&nbsp;&nbsp; answer was indicated as bundled in the corresponding offer.&nb=
sp; If there<br>
&nbsp;&nbsp; is no mismatch, the offerer MUST use the relevant parameters<b=
r>
&nbsp;&nbsp; [specific text from Suhas's draft needed here] from the<br>
&nbsp;&nbsp; &quot;m=3D&quot; section indicated by the BUNDLE tag [again, i=
t would be helpful<br>
&nbsp;&nbsp; to have a better name here] for each &quot;m=3D&quot; section =
which is bundled<br>
&nbsp;&nbsp; with it.<br>
<br>
There are other places where this creates confusion, but this is<br>
a nice clear one.<br>
<br>
</div>
</blockquote>
</span>I think we are saying the same thing here, but you are just asking f=
or the BUNDLE-tag to be called out more explicitly as opposed to focusing o=
n the BUNDLE address:port. Is that right ?
<br>
</div>
</blockquote>
<div><br>
</div>
<div>Yes, more or less. I'm asking for it to be the primary unit of analysi=
s.</div>
<div><br>
</div>
<div>-Ekr<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF"><br>
Thanks <br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Flemming <br>
</font></span>
<div>
<div class=3D"h5"><br>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr">-Ekr<br>
<br>
<br>
<br>
<br>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla =
<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" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">
<div>
<div class=3D"m_9125571528848928878h5">On Tue, Apr 17, 2018 at 11:11 AM, Ch=
rister Holmberg
<span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" tar=
get=3D"_blank">christer.holmberg@ericsson.co<wbr>m</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 class=3D"m_9125571528848928878m_3202404282620514461HOEnZb">
<div class=3D"m_9125571528848928878m_3202404282620514461h5">Hi,<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
DISCUSS:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp;When an offerer generates an offer, in which =
it wants to add a new<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp;bundled &quot;m=3D&quot; section, the offerer=
 MUST:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; o&nbsp; Assign the offerer BUN=
DLE address:port (previously selected<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;[Section 8.3.1] o=
r newly suggested [Section 8.5.1]) to the added<br>
&gt;&gt;&gt;&gt;&gt;&gt;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&quot;m=3D&quot; =
section; or<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn't sound right. You can't use the=
 existing<br>
&gt;&gt;&gt;&gt;&gt; address:port, because if the peer rejects BUNDLE but a=
ccepts the m=3D<br>
&gt;&gt;&gt;&gt;&gt; section then it's broken.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that in this case the usage of BUNDLE has already bee=
n negotiated.<br>
&gt;&gt;&gt;&gt; Then, if the answerer does not accept the new m=3D section=
 into the BUNDLE<br>
&gt;&gt;&gt;&gt; group, it needs to send an offer where it removes it, as d=
escribed in<br>
&gt;&gt;&gt;&gt; section 8.3.3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Well, both of these options correspond to insisting that the m=
=3D section<br>
&gt;&gt;&gt; be in the BUNDLE group. If I just want to suggest it, I would =
have to provide<br>
&gt;&gt;&gt; a fresh unique address. Or are you saying that's impossible.<b=
r>
&gt;&gt;&gt;<br>
&gt;&gt; Yes.<br>
&gt;&gt;<br>
&gt;&gt; Previously, when the offerer wanted to add a new m- section to a B=
UNDLE<br>
&gt;&gt; group, it had to choice of either assigning a unique address or a<=
br>
&gt;&gt; previously negotiated bundle address.<br>
&gt;&gt;<br>
&gt;&gt; That option was removed as part of task (triggered by WGLC comment=
s etc)<br>
&gt;<br>
&gt; That seems like a pretty material change. Was there a call for consens=
us on that?<br>
<br>
</div>
</div>
No. But, the suggested changes were indicated on the list, there were pull =
requests etc, so people were informed about it and had a chance to comment/=
object.<br>
</blockquote>
<div><br>
</div>
</div>
</div>
<div>Hmm... Ben, do you think these were properly surfaced to the WG?</div>
<div><br>
</div>
<div>-Ekr</div>
<span>
<div><br>
</div>
<div><br>
<span></span><span></span></div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span>&gt; trying to simplifying the procedures. Currently the offerer must=
 either<br>
&gt; assign a bundle address (previously negotiated or new suggested) or<br=
>
&gt; indicate it as bundle-only.<br>
&gt;<br>
&gt; At minimum this needs to be clearly stated<br>
<br>
</span>I need to modify the section, so I will add text about it.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote>
</span></div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D70641FF2EC5Bchristerholmbergericssoncom_--


From nobody Wed Apr 25 04:55:02 2018
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 0843A127522 for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 04:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 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, T_DKIMWL_WL_MED=-0.01] 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 VxMXk3fVOlSr for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 04:54:54 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::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 5A3F1127419 for <mmusic@ietf.org>; Wed, 25 Apr 2018 04:54:51 -0700 (PDT)
Received: by mail-oi0-x22b.google.com with SMTP id c203-v6so640859oib.7 for <mmusic@ietf.org>; Wed, 25 Apr 2018 04:54:51 -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=LzUzraQswwnc6QgvVoaxpk4zlmnrPLrk8s3Ex5mwCOM=; b=GmYq6mPbxV3TaWKztnkgSFn7zC1R6bWQicDRT0RlG1pDFttctUGLIUlWyorrIs+PQW 3UrRTrIuggn3l5o18tEViIWBfqU8Ni1Vku0iyU32oSOHIUuQaZXsF+kQ/3fcU2Z0vsgU l39V0uVH8PwpdSm7xkacHI/RO1lpVl2HIMaPMDgym6obKi+ZFCd6DqBc+s3hohgwQjdL dnhXYxvVk9KvqEE6DMY8bGKUSpldhdWd6LNxJof8i2CpGsGjHtm0UUYdcN9xrYRe0VlE a56zjMxqh49Dx8RaJLQRya3kbA+sPUYeG+3ixSwgAEyX9qakvQNfCjrJL4RFhAW3OjiZ CHbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LzUzraQswwnc6QgvVoaxpk4zlmnrPLrk8s3Ex5mwCOM=; b=aoCOiYWSeaucfB8xanVMUrBrPbmRJZBQpe8jcAWigchrE4HfF9gUpLtnwKcWnCYL+w SU0cZbrot/AFEAtvmkZ7DLWhcQgUSjdDp6RpnFTYnsy5h/IJGdezjSnN3O0kZ0moyeeL zbg1FwE0xETBocTaSCxq8LwgzOHaJU8bJhh1SPYe0ecpk257+Zak5Pprfrp0FhqDmhPq 1Go4wgRESg8cRwzGM48YPT+C0173O00qBtGW1FavloxQmFWFGeJ2uBtnz2nUpoOzlzxU W5ndRgkf6VG68o1Yh7Wel+7uHHyNKMGG5yO7JojtZz1YQZ80AHT6KZQPN0xR4HC149Pw T8YQ==
X-Gm-Message-State: ALQs6tChTcqwEVqRTUrZgWdN25K1MoeMNbE51sUpCesPepm85bFMOe2u IJ9R3hrfkyEnmitaMVgx1J3LFK6nHzuoWfkDd/kJ5g==
X-Google-Smtp-Source: AIpwx48Qw8qLqdVXEoKGeTYH69dU80ITREb2IdYG3kumavE/LGeG5Xn2/kstunv8RiMpEt/hB+stmb8gj++wQA/XxHU=
X-Received: by 2002:aca:ea46:: with SMTP id i67-v6mr17923365oih.174.1524657290692;  Wed, 25 Apr 2018 04:54:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.118.130 with HTTP; Wed, 25 Apr 2018 04:54:10 -0700 (PDT)
In-Reply-To: <D70641FF.2EC5B%christer.holmberg@ericsson.com>
References: <D6FB735E.2E0AD%christer.holmberg@ericsson.com> <CABcZeBOX-0KFVeHFcwe_S5wde8MyZRxXCP1-dwAqt+SKYKdNVg@mail.gmail.com> <D6FBD89F.2E420%christer.holmberg@ericsson.com> <CABcZeBP8U+d1Sxen96EU0ZA=-6QvszSX7ib+iHKaVLiRwjMnmw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E86EE8@ESESSMB109.ericsson.se> <CABcZeBMrYW06e=7u5ZyVquGae5iM_GB06XJTDFs4Z3p=UTbpFA@mail.gmail.com> <CABcZeBMnnCZiibKBnDUzpnAtHWxc1aq9qD+pGe3KZ7q8SJQa=w@mail.gmail.com> <95979e47-0199-99c4-383a-8a26cb7bbde6@cisco.com> <CABcZeBMfb3C=9ho6xAAB+Dp+KPP3Jvfdm13zd4VUF6Eyje8wRQ@mail.gmail.com> <D70641FF.2EC5B%christer.holmberg@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 25 Apr 2018 04:54:10 -0700
Message-ID: <CABcZeBO9fGNULee1a3fvxUxdcMJziHt40BmgeUE0qWfJNMi4GQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Flemming Andreasen <fandreas@cisco.com>, The IESG <iesg@ietf.org>,  "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>,  "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000037621f056aaaf091"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gq1qAQbqo0WUfWWhq1fJxbWL9_A>
Subject: Re: [MMUSIC] Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-negotiation-49: (with DISCUSS and COMMENT) - DISCUSS
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 11:54:57 -0000

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

Let's do "tagged" b/c BUNDLE-tagged is long

-Ekr


On Wed, Apr 25, 2018 at 4:44 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> As it would not be very convenient to talk about =E2=80=9Cthe m=3D sectio=
n
> identified by the BUNDLE-tag=E2=80=9D, there has been a suggestion to e.g=
., talk
> about =E2=80=9Cthe lead m- section=E2=80=9D.
>
> My suggestion would be to talk about =E2=80=9Ctagged m- section=E2=80=9D =
or =E2=80=9CBUNDLE-tagged
> m- section=E2=80=9D. We don=E2=80=99t need to add more fancy words into t=
he document :)
>
> Regards,
>
> Christer
>
> From: Eric Rescorla <ekr@rtfm.com>
> Date: Wednesday 25 April 2018 at 11:23
> To: Flemming Andreasen <fandreas@cisco.com>
> Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "iesg@ietf.org" <
> iesg@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <
> draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>, "
> mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <
> mmusic@ietf.org>
> Subject: Re: Eric Rescorla's Discuss on draft-ietf-mmusic-sdp-bundle-nego=
tiation-49:
> (with DISCUSS and COMMENT) - DISCUSS
>
>
>
> On Tue, Apr 24, 2018 at 8:11 AM, Flemming Andreasen <fandreas@cisco.com>
> wrote:
>
>>
>>
>> On 4/17/18 6:23 PM, Eric Rescorla wrote:
>>
>> Hi folks,
>>
>> This is an attempt to sharpen my point about talking about the
>> "BUNDLE address:port", when what we really mean is "use the
>> parameters from the "m=3D" section". Here's an example where this
>> creates a real problem. S 8.4 says:
>>
>>    When an offerer receives an answer, if the answer contains a BUNDLE
>>    group, the offerer MUST check that any bundled "m=3D" section in the
>>    answer was indicated as bundled in the corresponding offer.  If there
>>    is no mismatch, the offerer MUST use the offerer BUNDLE address:port,
>>    selected by the answerer [Section 8.3.1], as the address for each
>>    bundled "m=3D" section.
>>
>> Now consider the case where I am doing trickle ICE. The offer will
>> contain:
>>
>>    a=3Dgroup:BUNDLE foo bar
>>    m=3Daudio 9 RTP/AVP 97
>>    c=3DIN IP4 0.0.0.0
>>    a=3Drtpmap:97 iLBC/8000
>>    a=3Dmid:foo
>>
>>    m=3Dvideo 9 RTP/AVP 98
>>    c=3DIN IP4 0.0.0.0
>>    a=3Drtpmap:98 H261/90000
>>    a=3Dmid:bar
>>
>> Now, if the answer contains:
>>
>>    a=3Dgroup:BUNDLE foo bar
>>
>> Then the semantics are that we are supposed to use the parameters from
>> the m=3Daudio line as the parameters for the bundle group. Specifically,
>> we are supposed to use the ICE candidates that belong to that m=3Daudio
>> line. But there's no way to get that from this text.
>>
>> True, but it's an inherent part of the definition of the BUNDLE-tag as
>> described in the preceding sections covering the overall offer/answer
>> procedures.
>>
>
> But this text doesn't say anything about the BUNDLE-tag. It says to selec=
t
> the address.
>
>>
>> Ordinarily, if
>> each m=3Dsection contained a distinct address:port, then you might say
>> there was an implicit map from address:port to m=3D section parameters,
>> but in this case because all the address:port values are the same,
>> that's not possible, and so this paragraph just doesn't work.
>>
>> Why not ? The BUNDLE-tag in the answer indicates which "m=3D" section th=
e
>> answerer chose and hence you will use the corresponding BUNDLE
>> address:port.
>>
>
> But that's not in this text.
>
>
>> The
>> right fix is to stop talking about the address:port and instead talk
>> about the m=3D section.
>>
>>    When an offerer receives an answer, if the answer contains a BUNDLE
>>    group, the offerer MUST check that any bundled "m=3D" section in the
>>    answer was indicated as bundled in the corresponding offer.  If there
>>    is no mismatch, the offerer MUST use the relevant parameters
>>    [specific text from Suhas's draft needed here] from the
>>    "m=3D" section indicated by the BUNDLE tag [again, it would be helpfu=
l
>>    to have a better name here] for each "m=3D" section which is bundled
>>    with it.
>>
>> There are other places where this creates confusion, but this is
>> a nice clear one.
>>
>> I think we are saying the same thing here, but you are just asking for
>> the BUNDLE-tag to be called out more explicitly as opposed to focusing o=
n
>> the BUNDLE address:port. Is that right ?
>>
>
> Yes, more or less. I'm asking for it to be the primary unit of analysis.
>
> -Ekr
>
>>
>> Thanks
>>
>> -- Flemming
>>
>>
>> -Ekr
>>
>>
>>
>>
>>
>> On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>>
>>>
>>>
>>> On Tue, Apr 17, 2018 at 11:11 AM, Christer Holmberg <
>>> christer.holmberg@ericsson.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> ----------------------------------------------------------------------
>>>> DISCUSS:
>>>> ----------------------------------------------------------------------
>>>>
>>>> >>>>>> When an offerer generates an offer, in which it wants to add a
>>>> new
>>>> >>>>>> bundled "m=3D" section, the offerer MUST:
>>>> >>>>>>
>>>> >>>>>>      o  Assign the offerer BUNDLE address:port (previously
>>>> selected
>>>> >>>>>>         [Section 8.3.1] or newly suggested [Section 8.5.1]) to
>>>> the added
>>>> >>>>>>         "m=3D" section; or
>>>> >>>>>
>>>> >>>>> IMPORTANT: This doesn't sound right. You can't use the existing
>>>> >>>>> address:port, because if the peer rejects BUNDLE but accepts the
>>>> m=3D
>>>> >>>>> section then it's broken.
>>>> >>>>
>>>> >>>> Note that in this case the usage of BUNDLE has already been
>>>> negotiated.
>>>> >>>> Then, if the answerer does not accept the new m=3D section into t=
he
>>>> BUNDLE
>>>> >>>> group, it needs to send an offer where it removes it, as describe=
d
>>>> in
>>>> >>>> section 8.3.3.
>>>> >>>
>>>> >>> Well, both of these options correspond to insisting that the m=3D
>>>> section
>>>> >>> be in the BUNDLE group. If I just want to suggest it, I would have
>>>> to provide
>>>> >>> a fresh unique address. Or are you saying that's impossible.
>>>> >>>
>>>> >> Yes.
>>>> >>
>>>> >> Previously, when the offerer wanted to add a new m- section to a
>>>> BUNDLE
>>>> >> group, it had to choice of either assigning a unique address or a
>>>> >> previously negotiated bundle address.
>>>> >>
>>>> >> That option was removed as part of task (triggered by WGLC comments
>>>> etc)
>>>> >
>>>> > That seems like a pretty material change. Was there a call for
>>>> consensus on that?
>>>>
>>>> No. But, the suggested changes were indicated on the list, there were
>>>> pull requests etc, so people were informed about it and had a chance t=
o
>>>> comment/object.
>>>>
>>>
>>> Hmm... Ben, do you think these were properly surfaced to the WG?
>>>
>>> -Ekr
>>>
>>>
>>> > trying to simplifying the procedures. Currently the offerer must eith=
er
>>>> > assign a bundle address (previously negotiated or new suggested) or
>>>> > indicate it as bundle-only.
>>>> >
>>>> > At minimum this needs to be clearly stated
>>>>
>>>> I need to modify the section, so I will add text about it.
>>>>
>>>> Regards,
>>>>
>>>> Christer
>>>>
>>>>
>>>
>>
>>
>

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

<div dir=3D"ltr"><div>Let&#39;s do &quot;tagged&quot; b/c BUNDLE-tagged is =
long</div><div><br></div><div>-Ekr</div><div><br></div></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On Wed, Apr 25, 2018 at 4:44 AM=
, Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmbe=
rg@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 .8e=
x;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>As it would not be very convenient to talk about =E2=80=9Cthe m=3D sec=
tion identified by the BUNDLE-tag=E2=80=9D, there has been a suggestion to =
e.g., talk about =E2=80=9Cthe lead m- section=E2=80=9D.</div>
<div><br>
</div>
<div>My suggestion would be to talk about =E2=80=9Ctagged m- section=E2=80=
=9D or =E2=80=9CBUNDLE-tagged m- section=E2=80=9D. We don=E2=80=99t need to=
 add more fancy words into the document :)</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"m_3448998904287833824OLK_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>Eric Rescorla &lt;<a href=3D"=
mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Wednesday 25 April 2018 at 11=
:23<br>
<span style=3D"font-weight:bold">To: </span>Flemming Andreasen &lt;<a href=
=3D"mailto:fandreas@cisco.com" target=3D"_blank">fandreas@cisco.com</a>&gt;=
<br>
<span style=3D"font-weight:bold">Cc: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.<wbr>com</a>&gt;, &quot;<a href=3D"mailto:iesg@ietf.org" targe=
t=3D"_blank">iesg@ietf.org</a>&quot; &lt;<a href=3D"mailto:iesg@ietf.org" t=
arget=3D"_blank">iesg@ietf.org</a>&gt;, &quot;<a href=3D"mailto:draft-ietf-=
mmusic-sdp-bundle-negotiation@ietf.org" target=3D"_blank">draft-ietf-mmusic=
-sdp-bundle-<wbr>negotiation@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" t=
arget=3D"_blank">draft-ietf-mmusic-sdp-bundle-<wbr>negotiation@ietf.org</a>=
&gt;, &quot;<a href=3D"mailto:mmusic-chairs@ietf.org" target=3D"_blank">mmu=
sic-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic-chairs@ietf.org"=
 target=3D"_blank">mmusic-chairs@ietf.org</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" target=3D"_blank">mmusic@=
ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: Eric Rescorla&#39;s Di=
scuss on draft-ietf-mmusic-sdp-bundle-<wbr>negotiation-49: (with DISCUSS an=
d COMMENT) - DISCUSS<br>
</div><div><div class=3D"h5">
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Apr 24, 2018 at 8:11 AM, 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"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF">
<div>
<div class=3D"m_3448998904287833824h5"><br>
<br>
<div class=3D"m_3448998904287833824m_9125571528848928878moz-cite-prefix">On=
 4/17/18 6:23 PM, Eric Rescorla wrote:<br>
</div>
<blockquote type=3D"cite">
<div dir=3D"ltr">Hi folks,<br>
<br>
This is an attempt to sharpen my point about talking about the<br>
&quot;BUNDLE address:port&quot;, when what we really mean is &quot;use the<=
br>
parameters from the &quot;m=3D&quot; section&quot;. Here&#39;s an example w=
here this<br>
creates a real problem. S 8.4 says:<br>
<br>
=C2=A0=C2=A0 When an offerer receives an answer, if the answer contains a B=
UNDLE<br>
=C2=A0=C2=A0 group, the offerer MUST check that any bundled &quot;m=3D&quot=
; section in the<br>
=C2=A0=C2=A0 answer was indicated as bundled in the corresponding offer.=C2=
=A0 If there<br>
=C2=A0=C2=A0 is no mismatch, the offerer MUST use the offerer BUNDLE addres=
s:port,<br>
=C2=A0=C2=A0 selected by the answerer [Section 8.3.1], as the address for e=
ach<br>
=C2=A0=C2=A0 bundled &quot;m=3D&quot; section.<br>
<br>
Now consider the case where I am doing trickle ICE. The offer will<br>
contain:<br>
<br>
=C2=A0=C2=A0 a=3D<a class=3D"m_3448998904287833824m_9125571528848928878moz-=
txt-link-freetext">group:BUNDLE</a> foo bar<br>
=C2=A0=C2=A0 m=3Daudio 9 RTP/AVP 97<br>
=C2=A0=C2=A0 c=3DIN IP4 0.0.0.0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0 a=3Drtpmap:97 iLBC/8000<br>
=C2=A0=C2=A0 a=3Dmid:foo<br>
=C2=A0=C2=A0 <br>
=C2=A0=C2=A0 m=3Dvideo 9 RTP/AVP 98<br>
=C2=A0=C2=A0 c=3DIN IP4 0.0.0.0=C2=A0=C2=A0 <br>
=C2=A0=C2=A0 a=3Drtpmap:98 H261/90000<br>
=C2=A0=C2=A0 a=3Dmid:bar<br>
<br>
Now, if the answer contains:<br>
<br>
=C2=A0=C2=A0 a=3D<a class=3D"m_3448998904287833824m_9125571528848928878moz-=
txt-link-freetext">group:BUNDLE</a> foo bar<br>
<br>
Then the semantics are that we are supposed to use the parameters from<br>
the m=3Daudio line as the parameters for the bundle group. Specifically,<br=
>
we are supposed to use the ICE candidates that belong to that m=3Daudio<br>
line. But there&#39;s no way to get that from this text.</div>
</blockquote>
</div>
</div>
True, but it&#39;s an inherent part of the definition of the BUNDLE-tag as =
described in the preceding sections covering the overall offer/answer proce=
dures.
<br>
</div>
</blockquote>
<div><br>
</div>
<div>But this text doesn&#39;t say anything about the BUNDLE-tag. It says t=
o select the address.<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF"><span><br>
<blockquote type=3D"cite">
<div dir=3D"ltr">Ordinarily, if<br>
each m=3Dsection contained a distinct address:port, then you might say<br>
there was an implicit map from address:port to m=3D section parameters,<br>
but in this case because all the address:port values are the same,<br>
that&#39;s not possible, and so this paragraph just doesn&#39;t work.=C2=A0=
 </div>
</blockquote>
</span>Why not ? The BUNDLE-tag in the answer indicates which &quot;m=3D&qu=
ot; section the answerer chose and hence you will use the corresponding BUN=
DLE address:port.
<br>
</div>
</blockquote>
<div><br>
</div>
<div>But that&#39;s not in this text.</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF"><span><br>
<blockquote type=3D"cite">
<div dir=3D"ltr">The<br>
right fix is to stop talking about the address:port and instead talk<br>
about the m=3D section.<br>
<br>
=C2=A0=C2=A0 When an offerer receives an answer, if the answer contains a B=
UNDLE<br>
=C2=A0=C2=A0 group, the offerer MUST check that any bundled &quot;m=3D&quot=
; section in the<br>
=C2=A0=C2=A0 answer was indicated as bundled in the corresponding offer.=C2=
=A0 If there<br>
=C2=A0=C2=A0 is no mismatch, the offerer MUST use the relevant parameters<b=
r>
=C2=A0=C2=A0 [specific text from Suhas&#39;s draft needed here] from the<br=
>
=C2=A0=C2=A0 &quot;m=3D&quot; section indicated by the BUNDLE tag [again, i=
t would be helpful<br>
=C2=A0=C2=A0 to have a better name here] for each &quot;m=3D&quot; section =
which is bundled<br>
=C2=A0=C2=A0 with it.<br>
<br>
There are other places where this creates confusion, but this is<br>
a nice clear one.<br>
<br>
</div>
</blockquote>
</span>I think we are saying the same thing here, but you are just asking f=
or the BUNDLE-tag to be called out more explicitly as opposed to focusing o=
n the BUNDLE address:port. Is that right ?
<br>
</div>
</blockquote>
<div><br>
</div>
<div>Yes, more or less. I&#39;m asking for it to be the primary unit of ana=
lysis.</div>
<div><br>
</div>
<div>-Ekr<br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div text=3D"#000000" bgcolor=3D"#FFFFFF"><br>
Thanks <br>
<span class=3D"m_3448998904287833824HOEnZb"><font color=3D"#888888"><br>
-- Flemming <br>
</font></span>
<div>
<div class=3D"m_3448998904287833824h5"><br>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr">-Ekr<br>
<br>
<br>
<br>
<br>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Apr 17, 2018 at 11:18 AM, Eric Rescorla =
<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" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">
<div>
<div class=3D"m_3448998904287833824m_9125571528848928878h5">On Tue, Apr 17,=
 2018 at 11:11 AM, Christer Holmberg
<span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" tar=
get=3D"_blank">christer.holmberg@ericsson.co<wbr>m</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 class=3D"m_3448998904287833824m_9125571528848928878m_32024042826205144=
61HOEnZb">
<div class=3D"m_3448998904287833824m_9125571528848928878m_32024042826205144=
61h5">Hi,<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
DISCUSS:<br>
------------------------------<wbr>------------------------------<wbr>-----=
-----<br>
<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0When an offerer generates an offer, in which =
it wants to add a new<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0bundled &quot;m=3D&quot; section, the offerer=
 MUST:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 o=C2=A0 Assign the offerer BUN=
DLE address:port (previously selected<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[Section 8.3.1] o=
r newly suggested [Section 8.5.1]) to the added<br>
&gt;&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;m=3D&quot; =
section; or<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; IMPORTANT: This doesn&#39;t sound right. You can&#39;t=
 use the existing<br>
&gt;&gt;&gt;&gt;&gt; address:port, because if the peer rejects BUNDLE but a=
ccepts the m=3D<br>
&gt;&gt;&gt;&gt;&gt; section then it&#39;s broken.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Note that in this case the usage of BUNDLE has already bee=
n negotiated.<br>
&gt;&gt;&gt;&gt; Then, if the answerer does not accept the new m=3D section=
 into the BUNDLE<br>
&gt;&gt;&gt;&gt; group, it needs to send an offer where it removes it, as d=
escribed in<br>
&gt;&gt;&gt;&gt; section 8.3.3.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Well, both of these options correspond to insisting that the m=
=3D section<br>
&gt;&gt;&gt; be in the BUNDLE group. If I just want to suggest it, I would =
have to provide<br>
&gt;&gt;&gt; a fresh unique address. Or are you saying that&#39;s impossibl=
e.<br>
&gt;&gt;&gt;<br>
&gt;&gt; Yes.<br>
&gt;&gt;<br>
&gt;&gt; Previously, when the offerer wanted to add a new m- section to a B=
UNDLE<br>
&gt;&gt; group, it had to choice of either assigning a unique address or a<=
br>
&gt;&gt; previously negotiated bundle address.<br>
&gt;&gt;<br>
&gt;&gt; That option was removed as part of task (triggered by WGLC comment=
s etc)<br>
&gt;<br>
&gt; That seems like a pretty material change. Was there a call for consens=
us on that?<br>
<br>
</div>
</div>
No. But, the suggested changes were indicated on the list, there were pull =
requests etc, so people were informed about it and had a chance to comment/=
object.<br>
</blockquote>
<div><br>
</div>
</div>
</div>
<div>Hmm... Ben, do you think these were properly surfaced to the WG?</div>
<div><br>
</div>
<div>-Ekr</div>
<span>
<div><br>
</div>
<div><br>
<span></span><span></span></div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span>&gt; trying to simplifying the procedures. Currently the offerer must=
 either<br>
&gt; assign a bundle address (previously negotiated or new suggested) or<br=
>
&gt; indicate it as bundle-only.<br>
&gt;<br>
&gt; At minimum this needs to be clearly stated<br>
<br>
</span>I need to modify the section, so I will add text about it.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
</blockquote>
</span></div>
<br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div></div></span>
</div>

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

--00000000000037621f056aaaf091--


From nobody Wed Apr 25 09:43:03 2018
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 8085912895E for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 09:43:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8yjnyZf2Viu for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 09:42:59 -0700 (PDT)
Received: from alum-mailsec-scanner-8.mit.edu (alum-mailsec-scanner-8.mit.edu [18.7.68.20]) by ietfa.amsl.com (Postfix) with ESMTP id 21FE91200C5 for <mmusic@ietf.org>; Wed, 25 Apr 2018 09:42:59 -0700 (PDT)
X-AuditID: 12074414-aa9ff700000073ca-17-5ae0b012c58a
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 37.F0.29642.210B0EA5; Wed, 25 Apr 2018 12:42:58 -0400 (EDT)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w3PGgtOx023035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 25 Apr 2018 12:42:57 -0400
To: Colin Perkins <csp@csperkins.org>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Flemming Andreasen <fandreas@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu> <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com> <de456926-ef1a-4e99-813c-19d7b9995d18@alum.mit.edu> <B9B15009-10B5-4FA1-9AD2-457B7693F073@csperkins.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <7af16e92-f151-d561-32b1-c7c9044d2e36@alum.mit.edu>
Date: Wed, 25 Apr 2018 12:42:55 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <B9B15009-10B5-4FA1-9AD2-457B7693F073@csperkins.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBKsWRmVeSWpSXmKPExsUixO6iqCu04UGUwdxWMYvlL08wWry/oGux f/F5ZotL6+8xWUxd/pjFgdVjyu+NrB7T7t9n8/j19Sqbx5IlP5k82p7dYQ9gjeKySUnNySxL LdK3S+DKOPH0PXvBLb2K9ZefMjcwXlXtYuTkkBAwkTj46BFTFyMXh5DADiaJn9M7GCGch0wS M7/9ZAWpEhbQlZgyayKYLSKgKrHj+D+wImaBnYwSbxa/ZgZJCAmcZpI4tN0RxGYT0JKYc+g/ SxcjBwevgL3Eh/flIGEWoN4nP/eBlYsKpEnc3zyJEcTmFRCUODnzCQuIzSngKPHy2g4mEJtZ wExi3uaHzBC2uMStJ/Oh4vISzVtnM09gFJiFpH0WkpZZSFpmIWlZwMiyilEuMac0Vzc3MTOn ODVZtzg5MS8vtUjXQi83s0QvNaV0EyMk+EV2MB45KXeIUYCDUYmHN2Dhgygh1sSy4srcQ4yS HExKorzTme5HCfEl5adUZiQWZ8QXleakFh9ilOBgVhLhjegFKudNSaysSi3Kh0lJc7AoifMy m+yNEhJITyxJzU5NLUgtgsnKcHAoSfC2rwNqFCxKTU+tSMvMKUFIM3FwggznARq+GqSGt7gg Mbc4Mx0if4rRmGPK8/4eZo6O91N6mIVY8vLzUqXEeaPWA5UKgJRmlObBTYMlsFeM4kDPCfMe BBnIA0x+cPNeAa1iAlqVKAi2qiQRISXVwMhYn7+nTS9SJnmpJ+/hRcVNXGxh2hLfNkyRey42 6yynesrTqvYnsso/vTbGfLWZtKb/2nx/lgOLq42nVXx59yx/f/oir7u717XlaeydsCokmiuK 3cA7QPmyJnNG62/3r+ouW/eHLa46MZ37cq7z0zdvsr4vUcrIupInc1Mx6LdjtGm1l3FErxJL cUaioRZzUXEiABM7mJI7AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lO0SIG_9UpNmOW7QIVjwUnogOCE>
Subject: Re: [MMUSIC] Meaning of fmt when proto is UDP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 16:43:01 -0000

On 4/23/18 12:33 PM, Colin Perkins wrote:
> Paul,
> 
>> On 23 Apr 2018, at 16:36, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> Magnus, Colin, Flemming, and others,
>>
>> On 4/23/18 4:07 AM, Magnus Westerlund wrote:
>>
>>>> ... But my question was a bigger one than that. My question is what does it *mean* for the fmt for UDP to be a mime type? This was never explained, from the beginning. I *guess* that the intent was that every UDP packet body conform to the mime type. Was that the original intent? Or is the mime type somehow to describe the whole stream of packets?
> 
> The contents of each UDP packet have to conform to the signalled media type. This is exactly the same as when RTP is used, where the contents of every RTP packet have to conform to the signalled media type (i.e., the RTP payload format).
> 
>>>> IOW, it seems to me that the definition of fmt for UDP is underspecified. I would like to complete the specification but don't know what the intent is. I can make something up, but that seems like a bad idea.
>>>>
>>>> I'll also note that I'm not aware of any cases that actually use UDP as transport and a mime type as the fmt.
>>> So Colin, may have a better recollection of those early discussions. But, yes I do think that the original intention was to put the subtype of the MIME type in the fmt space. However, based on the later discussions around use of MIME types I think that is problematic. The proto + fmt combination does basically identify a specific transport protocol and format to be used. That doesn't match MIME, which is a specific format only. We had a long discussion around the MIME type usage with RTP, which is much more specific.
>>> What I would do here is to create a SDP specific registry but maintain the MIME syntax for any entry, and make it clear that what ever like to register here needs to define what foo over UDP is. So specification required at least.
>>> /Magnus
>> That seems like a prudent direction to take. But it also seems like something well in excess of a simple editorial action. I can propose something, but I would think it would deserve some serious discussion in the WG. (If it is possible to find enough people to have that discussion.)
>>
>> The things that I can recall that use UDP have all chosen to define a new proto value and then specify how to use fmt with that.
>>
>> Are there *any* cases of RFCs where a proto of UDP is used with a mime subtype as fmt? Maybe we could simply deprecate this usage.
> 
> 
> SDP specifies the transport protocol and the data format that’s conveyed within that transport protocol. The transport protocol is identified by the “proto” field. The data format is identified by the combination of the media type (“media”) and the subtype (“fmt”).
> 
> For RTP, the fmt field references a media subtype indirectly:
> 
> 	m=video 51372 RTP/AVP 99
> 	a=rtpmap:99 h263-1998/90000
> 
> Here the transport is “RTP/AVP" and the media type is “video/h263-1990; rate=90000”. RFC 3555 describes the process for mapping media type names and parameters onto SDP using the combination of “a=rtpmap:”, “a=ptime:”, “a=maxptime:”,  and “a=fmtp:” lines.
> 
> For UDP, the fmt directly references a media subtype:
> 
> 	m=application 10000 udp foo
> 
> In this case, the media type is “application/foo”, and the UDP packets contain data that is formatted as described in the media type registration for "application/foo”. We don’t need an SDP specific registry: it’s just a standard media type registration, presumably with a note in its Encoding Considerations section to the effect that “This media type is only defined for transmission over UDP”.

Thanks. You are confirming what I *thought* was intended, though it 
isn't stated very clearly.

> What seems to be missing in RFC 4566 is a statement that “a=fmtp:” parameters can be used to convey media type parameters for media formats sent over UDP.

OK. That is something that we can do.

> For other transport protocols, the registration of the “proto” value denoting the transport states whether media types are used to describe the payload with that transport too, or whether the “fmt” namespace is managed differently. It would likely be a good idea to say that new protocols SHOULD use the media type namespace, for consistency, but there’s nothing in SDP that requires they do so.
> 
> Using UDP as the transport doesn’t seem especially useful, since in most cases I’d expect some additional framing to be needed to allow loss or reordering to be detected, but it seems conceptually well specified (although perhaps the text could be clearer in places). I don’t think deprecating UDP as a transport is appropriate, although clarifying when it should be used might be a good idea.

OK. I do have another question about one point. The text currently says:

    "udp" indicates an unspecified protocol over UDP.

This implies that there is some other protocol over UDP. But indeed 
there is no mechanism for specifying such. ISTM that this statement is 
wrong - that this proto means that UDP is used directly as the protocol.

For instance, you could conceivably specify

   m=text 50000 UDP plain

and then just sending plain text in UDP packets. But you would then have 
to live with the fact that reordering and packet loss may occur.

Alternatively you could define a new mime type that has packet sequence 
numbers and use those to do *something* to cope with packet loss and 
reordering. *That* might be functionally equivalent to defining another 
protocol layer, but it is then not "unspecified", and as far as SDP is 
concerned it isn't a protocol since it is part of the fmt.

Bottom line, ISTM the above should not say "unspecified protocol". Perhaps:

    "udp" indicates direct use of the UDP protocol.

How does that work for people?

	Thanks,
	Paul


From nobody Wed Apr 25 16:07:15 2018
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 9597612D88E for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 16:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y_o62TZA3UWd for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 16:07:11 -0700 (PDT)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBDB612D86E for <mmusic@ietf.org>; Wed, 25 Apr 2018 16:07:10 -0700 (PDT)
Received: from [81.187.2.149] (port=33687 helo=[192.168.0.71]) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1fBTVA-0001GX-0l; Thu, 26 Apr 2018 00:07:06 +0100
From: Colin Perkins <csp@csperkins.org>
Message-Id: <77623858-233D-4A42-A7D4-A0437F45A643@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6C9932CC-8898-487A-B3C4-903E6C9E2AD5"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 26 Apr 2018 00:06:59 +0100
In-Reply-To: <7af16e92-f151-d561-32b1-c7c9044d2e36@alum.mit.edu>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Flemming Andreasen <fandreas@cisco.com>, IETF MMUSIC WG <mmusic@ietf.org>, Jonathan Lennox <jonathan@vidyo.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu> <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com> <de456926-ef1a-4e99-813c-19d7b9995d18@alum.mit.edu> <B9B15009-10B5-4FA1-9AD2-457B7693F073@csperkins.org> <7af16e92-f151-d561-32b1-c7c9044d2e36@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2J4_bU1fuHhJqTjtGjUBYG0P7as>
Subject: Re: [MMUSIC] Meaning of fmt when proto is UDP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 23:07:13 -0000

--Apple-Mail=_6C9932CC-8898-487A-B3C4-903E6C9E2AD5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 25 Apr 2018, at 17:42, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> On 4/23/18 12:33 PM, Colin Perkins wrote:
>> Paul,
>>> On 23 Apr 2018, at 16:36, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>>>=20
>>> Magnus, Colin, Flemming, and others,
>>>=20
>>> On 4/23/18 4:07 AM, Magnus Westerlund wrote:
>>>=20
>>>>> ... But my question was a bigger one than that. My question is =
what does it *mean* for the fmt for UDP to be a mime type? This was =
never explained, from the beginning. I *guess* that the intent was that =
every UDP packet body conform to the mime type. Was that the original =
intent? Or is the mime type somehow to describe the whole stream of =
packets?
>> The contents of each UDP packet have to conform to the signalled =
media type. This is exactly the same as when RTP is used, where the =
contents of every RTP packet have to conform to the signalled media type =
(i.e., the RTP payload format).
>>>>> IOW, it seems to me that the definition of fmt for UDP is =
underspecified. I would like to complete the specification but don't =
know what the intent is. I can make something up, but that seems like a =
bad idea.
>>>>>=20
>>>>> I'll also note that I'm not aware of any cases that actually use =
UDP as transport and a mime type as the fmt.
>>>> So Colin, may have a better recollection of those early =
discussions. But, yes I do think that the original intention was to put =
the subtype of the MIME type in the fmt space. However, based on the =
later discussions around use of MIME types I think that is problematic. =
The proto + fmt combination does basically identify a specific transport =
protocol and format to be used. That doesn't match MIME, which is a =
specific format only. We had a long discussion around the MIME type =
usage with RTP, which is much more specific.
>>>> What I would do here is to create a SDP specific registry but =
maintain the MIME syntax for any entry, and make it clear that what ever =
like to register here needs to define what foo over UDP is. So =
specification required at least.
>>>> /Magnus
>>> That seems like a prudent direction to take. But it also seems like =
something well in excess of a simple editorial action. I can propose =
something, but I would think it would deserve some serious discussion in =
the WG. (If it is possible to find enough people to have that =
discussion.)
>>>=20
>>> The things that I can recall that use UDP have all chosen to define =
a new proto value and then specify how to use fmt with that.
>>>=20
>>> Are there *any* cases of RFCs where a proto of UDP is used with a =
mime subtype as fmt? Maybe we could simply deprecate this usage.
>> SDP specifies the transport protocol and the data format that=E2=80=99s=
 conveyed within that transport protocol. The transport protocol is =
identified by the =E2=80=9Cproto=E2=80=9D field. The data format is =
identified by the combination of the media type (=E2=80=9Cmedia=E2=80=9D) =
and the subtype (=E2=80=9Cfmt=E2=80=9D).
>> For RTP, the fmt field references a media subtype indirectly:
>> 	m=3Dvideo 51372 RTP/AVP 99
>> 	a=3Drtpmap:99 h263-1998/90000
>> Here the transport is =E2=80=9CRTP/AVP" and the media type is =
=E2=80=9Cvideo/h263-1990; rate=3D90000=E2=80=9D. RFC 3555 describes the =
process for mapping media type names and parameters onto SDP using the =
combination of =E2=80=9Ca=3Drtpmap:=E2=80=9D, =E2=80=9Ca=3Dptime:=E2=80=9D=
, =E2=80=9Ca=3Dmaxptime:=E2=80=9D, and =E2=80=9Ca=3Dfmtp:=E2=80=9D =
lines.
>> For UDP, the fmt directly references a media subtype:
>> 	m=3Dapplication 10000 udp foo
>> In this case, the media type is =E2=80=9Capplication/foo=E2=80=9D, =
and the UDP packets contain data that is formatted as described in the =
media type registration for "application/foo=E2=80=9D. We don=E2=80=99t =
need an SDP specific registry: it=E2=80=99s just a standard media type =
registration, presumably with a note in its Encoding Considerations =
section to the effect that =E2=80=9CThis media type is only defined for =
transmission over UDP=E2=80=9D.
>=20
> Thanks. You are confirming what I *thought* was intended, though it =
isn't stated very clearly.
>=20
>> What seems to be missing in RFC 4566 is a statement that =
=E2=80=9Ca=3Dfmtp:=E2=80=9D parameters can be used to convey media type =
parameters for media formats sent over UDP.
>=20
> OK. That is something that we can do.
>=20
>> For other transport protocols, the registration of the =E2=80=9Cproto=E2=
=80=9D value denoting the transport states whether media types are used =
to describe the payload with that transport too, or whether the =
=E2=80=9Cfmt=E2=80=9D namespace is managed differently. It would likely =
be a good idea to say that new protocols SHOULD use the media type =
namespace, for consistency, but there=E2=80=99s nothing in SDP that =
requires they do so.
>> Using UDP as the transport doesn=E2=80=99t seem especially useful, =
since in most cases I=E2=80=99d expect some additional framing to be =
needed to allow loss or reordering to be detected, but it seems =
conceptually well specified (although perhaps the text could be clearer =
in places). I don=E2=80=99t think deprecating UDP as a transport is =
appropriate, although clarifying when it should be used might be a good =
idea.
>=20
> OK. I do have another question about one point. The text currently =
says:
>=20
>   "udp" indicates an unspecified protocol over UDP.
>=20
> This implies that there is some other protocol over UDP. But indeed =
there is no mechanism for specifying such. ISTM that this statement is =
wrong - that this proto means that UDP is used directly as the protocol.
>=20
> For instance, you could conceivably specify
>=20
>  m=3Dtext 50000 UDP plain
>=20
> and then just sending plain text in UDP packets. But you would then =
have to live with the fact that reordering and packet loss may occur.

Agree.

> Alternatively you could define a new mime type that has packet =
sequence numbers and use those to do *something* to cope with packet =
loss and reordering. *That* might be functionally equivalent to defining =
another protocol layer, but it is then not "unspecified", and as far as =
SDP is concerned it isn't a protocol since it is part of the fmt.
>=20
> Bottom line, ISTM the above should not say "unspecified protocol". =
Perhaps:
>=20
>   "udp" indicates direct use of the UDP protocol.
>=20
> How does that work for people?


Makes sense to me. Or maybe something like =E2=80=9C=E2=80=A6indicates =
that the data is transported directly in UDP with no additional =
framing=E2=80=9D, if we want to be verbose?

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





--Apple-Mail=_6C9932CC-8898-487A-B3C4-903E6C9E2AD5
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""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 25 Apr 2018, at 17:42, 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""><span =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">On 4/23/18 12:33 PM, Colin =
Perkins wrote:</span><br style=3D"font-family: Inconsolata; font-size: =
10px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><blockquote type=3D"cite" =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">Paul,<br class=3D""><blockquote type=3D"cite" class=3D"">On =
23 Apr 2018, at 16:36, Paul Kyzivat &lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" =
class=3D"">pkyzivat@alum.mit.edu</a>&gt; wrote:<br class=3D""><br =
class=3D"">Magnus, Colin, Flemming, and others,<br class=3D""><br =
class=3D"">On 4/23/18 4:07 AM, Magnus Westerlund wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">... But my question was a bigger one than that. My question =
is what does it *mean* for the fmt for UDP to be a mime type? This was =
never explained, from the beginning. I *guess* that the intent was that =
every UDP packet body conform to the mime type. Was that the original =
intent? Or is the mime type somehow to describe the whole stream of =
packets?<br class=3D""></blockquote></blockquote></blockquote>The =
contents of each UDP packet have to conform to the signalled media type. =
This is exactly the same as when RTP is used, where the contents of =
every RTP packet have to conform to the signalled media type (i.e., the =
RTP payload format).<br class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D"">IOW, it seems to me that the definition of fmt for UDP is =
underspecified. I would like to complete the specification but don't =
know what the intent is. I can make something up, but that seems like a =
bad idea.<br class=3D""><br class=3D"">I'll also note that I'm not aware =
of any cases that actually use UDP as transport and a mime type as the =
fmt.<br class=3D""></blockquote>So Colin, may have a better recollection =
of those early discussions. But, yes I do think that the original =
intention was to put the subtype of the MIME type in the fmt space. =
However, based on the later discussions around use of MIME types I think =
that is problematic. The proto + fmt combination does basically identify =
a specific transport protocol and format to be used. That doesn't match =
MIME, which is a specific format only. We had a long discussion around =
the MIME type usage with RTP, which is much more specific.<br =
class=3D"">What I would do here is to create a SDP specific registry but =
maintain the MIME syntax for any entry, and make it clear that what ever =
like to register here needs to define what foo over UDP is. So =
specification required at least.<br class=3D"">/Magnus<br =
class=3D""></blockquote>That seems like a prudent direction to take. But =
it also seems like something well in excess of a simple editorial =
action. I can propose something, but I would think it would deserve some =
serious discussion in the WG. (If it is possible to find enough people =
to have that discussion.)<br class=3D""><br class=3D"">The things that I =
can recall that use UDP have all chosen to define a new proto value and =
then specify how to use fmt with that.<br class=3D""><br class=3D"">Are =
there *any* cases of RFCs where a proto of UDP is used with a mime =
subtype as fmt? Maybe we could simply deprecate this usage.<br =
class=3D""></blockquote>SDP specifies the transport protocol and the =
data format that=E2=80=99s conveyed within that transport protocol. The =
transport protocol is identified by the =E2=80=9Cproto=E2=80=9D field. =
The data format is identified by the combination of the media type =
(=E2=80=9Cmedia=E2=80=9D) and the subtype (=E2=80=9Cfmt=E2=80=9D).<br =
class=3D"">For RTP, the fmt field references a media subtype =
indirectly:<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space: pre;">	</span>m=3Dvideo 51372 RTP/AVP 99<br =
class=3D""><span class=3D"Apple-tab-span" style=3D"white-space: pre;">	=
</span>a=3Drtpmap:99 h263-1998/90000<br class=3D"">Here the transport is =
=E2=80=9CRTP/AVP" and the media type is =E2=80=9Cvideo/h263-1990; =
rate=3D90000=E2=80=9D. RFC 3555 describes the process for mapping media =
type names and parameters onto SDP using the combination of =
=E2=80=9Ca=3Drtpmap:=E2=80=9D, =E2=80=9Ca=3Dptime:=E2=80=9D, =
=E2=80=9Ca=3Dmaxptime:=E2=80=9D, and =E2=80=9Ca=3Dfmtp:=E2=80=9D =
lines.<br class=3D"">For UDP, the fmt directly references a media =
subtype:<br class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space: pre;">	</span>m=3Dapplication 10000 udp foo<br =
class=3D"">In this case, the media type is =E2=80=9Capplication/foo=E2=80=9D=
, and the UDP packets contain data that is formatted as described in the =
media type registration for "application/foo=E2=80=9D. We don=E2=80=99t =
need an SDP specific registry: it=E2=80=99s just a standard media type =
registration, presumably with a note in its Encoding Considerations =
section to the effect that =E2=80=9CThis media type is only defined for =
transmission over UDP=E2=80=9D.<br class=3D""></blockquote><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Thanks. You are confirming what I *thought* was =
intended, though it isn't stated very clearly.</span><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br=
 style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><blockquote type=3D"cite" style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">What seems to be missing in =
RFC 4566 is a statement that =E2=80=9Ca=3Dfmtp:=E2=80=9D parameters can =
be used to convey media type parameters for media formats sent over =
UDP.<br class=3D""></blockquote><br style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">OK. That is something that we =
can do.</span><br style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">For other transport =
protocols, the registration of the =E2=80=9Cproto=E2=80=9D value =
denoting the transport states whether media types are used to describe =
the payload with that transport too, or whether the =E2=80=9Cfmt=E2=80=9D =
namespace is managed differently. It would likely be a good idea to say =
that new protocols SHOULD use the media type namespace, for consistency, =
but there=E2=80=99s nothing in SDP that requires they do so.<br =
class=3D"">Using UDP as the transport doesn=E2=80=99t seem especially =
useful, since in most cases I=E2=80=99d expect some additional framing =
to be needed to allow loss or reordering to be detected, but it seems =
conceptually well specified (although perhaps the text could be clearer =
in places). I don=E2=80=99t think deprecating UDP as a transport is =
appropriate, although clarifying when it should be used might be a good =
idea.<br class=3D""></blockquote><br style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">OK. I do have another question =
about one point. The text currently says:</span><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">&nbsp;&nbsp;"udp" indicates an unspecified =
protocol over UDP.</span><br style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">This implies that there is some other protocol =
over UDP. But indeed there is no mechanism for specifying such. ISTM =
that this statement is wrong - that this proto means that UDP is used =
directly as the protocol.</span><br style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">For instance, you could conceivably =
specify</span><br style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">&nbsp;m=3Dtext 50000 UDP =
plain</span><br style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">and then just sending plain text =
in UDP packets. But you would then have to live with the fact that =
reordering and packet loss may occur.</span><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br =
class=3D""></div>Agree.</div><div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D""><span style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Alternatively you could define a new mime =
type that has packet sequence numbers and use those to do *something* to =
cope with packet loss and reordering. *That* might be functionally =
equivalent to defining another protocol layer, but it is then not =
"unspecified", and as far as SDP is concerned it isn't a protocol since =
it is part of the fmt.</span><br style=3D"font-family: Inconsolata; =
font-size: 10px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Bottom line, ISTM the above should not say =
"unspecified protocol". Perhaps:</span><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">&nbsp;&nbsp;"udp" indicates direct use of the =
UDP protocol.</span><br style=3D"font-family: Inconsolata; font-size: =
10px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Inconsolata; font-size: 10px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Inconsolata; font-size: 10px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">How does that work for =
people?</span><br style=3D"font-family: Inconsolata; font-size: 10px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote></div><div =
class=3D""><br class=3D""></div>Makes sense to me. Or maybe something =
like =E2=80=9C=E2=80=A6indicates that the data is transported directly =
in UDP with no additional framing=E2=80=9D, if we want to be verbose?<br =
class=3D""><div class=3D""><br class=3D"">--&nbsp;<br class=3D"">Colin =
Perkins<br class=3D""><a href=3D"https://csperkins.org/" =
class=3D"">https://csperkins.org/</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">

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

--Apple-Mail=_6C9932CC-8898-487A-B3C4-903E6C9E2AD5--


From nobody Wed Apr 25 16:47:19 2018
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 A839A12D77E for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 16:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 uJEqSp4ib7-W for <mmusic@ietfa.amsl.com>; Wed, 25 Apr 2018 16:47:15 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38B9E124BE8 for <mmusic@ietf.org>; Wed, 25 Apr 2018 16:47:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35121; q=dns/txt; s=iport; t=1524700035; x=1525909635; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=BKyDoqfvQXglUammzt/tBTTkyFvTcySN/MMWbPuYmPo=; b=TXNyFiMsqboNCPgwKFKes7eNTSJbiVDZCPyNyaJlh2jWrrfYIn/5U89u uWudTH+RqdzKatjhoA6HTvkHzoPMT3cAELfu0OiOR0ZoZGBHkfOT2BEfB ipTfXb1o8pUTeFUR9xwjoj9pnvxbNkfDVY3XH9iSPPoFWSwskZ+6Jt4jl U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5CABkEuFa/5ldJa1SCg4LAQEBAQE?= =?us-ascii?q?BAQEBAQEBBwEBAQEBgk12YRcxATEog2uUeYFTIYEPlQULG4RRAoMLITgUAQI?= =?us-ascii?q?BAQEBAQECbBwMhSMBBSNWEAkCDgogAQYDAgJGEQYBDAYCAQGEfg2LaJtBghw?= =?us-ascii?q?fhDmDaoJABYgQgVQ/gQ8jDIIuLoRIgyuCVAKQcIcTCIVhiF4Gh0yFBIk7hny?= =?us-ascii?q?BJTMhgVJNIxWCfosQhQRWIzCQGgEB?=
X-IronPort-AV: E=Sophos;i="5.49,328,1520899200";  d="scan'208,217";a="105048464"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Apr 2018 23:47:13 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w3PNlCN3017305; Wed, 25 Apr 2018 23:47:13 GMT
To: Colin Perkins <csp@csperkins.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF MMUSIC WG <mmusic@ietf.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <08fefc6e-faaa-f40a-060a-35f286b25e97@alum.mit.edu> <d826d988-5ca8-732d-f9de-61482f27fecb@cisco.com> <19f99895-c3a9-c5ff-9b57-5c9ae3cf2ff6@alum.mit.edu> <c44de893-0c89-a611-1e2e-63dd03b898e6@ericsson.com> <de456926-ef1a-4e99-813c-19d7b9995d18@alum.mit.edu> <B9B15009-10B5-4FA1-9AD2-457B7693F073@csperkins.org> <7af16e92-f151-d561-32b1-c7c9044d2e36@alum.mit.edu> <77623858-233D-4A42-A7D4-A0437F45A643@csperkins.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <95de69ea-085f-c017-4053-811341f869f1@cisco.com>
Date: Wed, 25 Apr 2018 19:47:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <77623858-233D-4A42-A7D4-A0437F45A643@csperkins.org>
Content-Type: multipart/alternative; boundary="------------E245A6CC9FDDE63D5CACA08B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CTDOVCOTdnzW3xAvrFufkWC7iJA>
Subject: Re: [MMUSIC] Meaning of fmt when proto is UDP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 25 Apr 2018 23:47:18 -0000

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



On 4/25/18 7:06 PM, Colin Perkins wrote:
>
>> On 25 Apr 2018, at 17:42, Paul Kyzivat <pkyzivat@alum.mit.edu 
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>
>> On 4/23/18 12:33 PM, Colin Perkins wrote:
>>> Paul,
>>>> On 23 Apr 2018, at 16:36, Paul Kyzivat <pkyzivat@alum.mit.edu 
>>>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>>>
>>>> Magnus, Colin, Flemming, and others,
>>>>
>>>> On 4/23/18 4:07 AM, Magnus Westerlund wrote:
>>>>
>>>>>> ... But my question was a bigger one than that. My question is 
>>>>>> what does it *mean* for the fmt for UDP to be a mime type? This 
>>>>>> was never explained, from the beginning. I *guess* that the 
>>>>>> intent was that every UDP packet body conform to the mime type. 
>>>>>> Was that the original intent? Or is the mime type somehow to 
>>>>>> describe the whole stream of packets?
>>> The contents of each UDP packet have to conform to the signalled 
>>> media type. This is exactly the same as when RTP is used, where the 
>>> contents of every RTP packet have to conform to the signalled media 
>>> type (i.e., the RTP payload format).
>>>>>> IOW, it seems to me that the definition of fmt for UDP is 
>>>>>> underspecified. I would like to complete the specification but 
>>>>>> don't know what the intent is. I can make something up, but that 
>>>>>> seems like a bad idea.
>>>>>>
>>>>>> I'll also note that I'm not aware of any cases that actually use 
>>>>>> UDP as transport and a mime type as the fmt.
>>>>> So Colin, may have a better recollection of those early 
>>>>> discussions. But, yes I do think that the original intention was 
>>>>> to put the subtype of the MIME type in the fmt space. However, 
>>>>> based on the later discussions around use of MIME types I think 
>>>>> that is problematic. The proto + fmt combination does basically 
>>>>> identify a specific transport protocol and format to be used. That 
>>>>> doesn't match MIME, which is a specific format only. We had a long 
>>>>> discussion around the MIME type usage with RTP, which is much more 
>>>>> specific.
>>>>> What I would do here is to create a SDP specific registry but 
>>>>> maintain the MIME syntax for any entry, and make it clear that 
>>>>> what ever like to register here needs to define what foo over UDP 
>>>>> is. So specification required at least.
>>>>> /Magnus
>>>> That seems like a prudent direction to take. But it also seems like 
>>>> something well in excess of a simple editorial action. I can 
>>>> propose something, but I would think it would deserve some serious 
>>>> discussion in the WG. (If it is possible to find enough people to 
>>>> have that discussion.)
>>>>
>>>> The things that I can recall that use UDP have all chosen to define 
>>>> a new proto value and then specify how to use fmt with that.
>>>>
>>>> Are there *any* cases of RFCs where a proto of UDP is used with a 
>>>> mime subtype as fmt? Maybe we could simply deprecate this usage.
>>> SDP specifies the transport protocol and the data format that’s 
>>> conveyed within that transport protocol. The transport protocol is 
>>> identified by the “proto” field. The data format is identified by 
>>> the combination of the media type (“media”) and the subtype (“fmt”).
>>> For RTP, the fmt field references a media subtype indirectly:
>>> m=video 51372 RTP/AVP 99
>>> a=rtpmap:99 h263-1998/90000
>>> Here the transport is “RTP/AVP" and the media type is 
>>> “video/h263-1990; rate=90000”. RFC 3555 describes the process for 
>>> mapping media type names and parameters onto SDP using the 
>>> combination of “a=rtpmap:”, “a=ptime:”, “a=maxptime:”, and “a=fmtp:” 
>>> lines.
>>> For UDP, the fmt directly references a media subtype:
>>> m=application 10000 udp foo
>>> In this case, the media type is “application/foo”, and the UDP 
>>> packets contain data that is formatted as described in the media 
>>> type registration for "application/foo”. We don’t need an SDP 
>>> specific registry: it’s just a standard media type registration, 
>>> presumably with a note in its Encoding Considerations section to the 
>>> effect that “This media type is only defined for transmission over UDP”.
>>
>> Thanks. You are confirming what I *thought* was intended, though it 
>> isn't stated very clearly.
>>
>>> What seems to be missing in RFC 4566 is a statement that “a=fmtp:” 
>>> parameters can be used to convey media type parameters for media 
>>> formats sent over UDP.
>>
>> OK. That is something that we can do.
>>
>>> For other transport protocols, the registration of the “proto” value 
>>> denoting the transport states whether media types are used to 
>>> describe the payload with that transport too, or whether the “fmt” 
>>> namespace is managed differently. It would likely be a good idea to 
>>> say that new protocols SHOULD use the media type namespace, for 
>>> consistency, but there’s nothing in SDP that requires they do so.
>>> Using UDP as the transport doesn’t seem especially useful, since in 
>>> most cases I’d expect some additional framing to be needed to allow 
>>> loss or reordering to be detected, but it seems conceptually well 
>>> specified (although perhaps the text could be clearer in places). I 
>>> don’t think deprecating UDP as a transport is appropriate, although 
>>> clarifying when it should be used might be a good idea.
>>
>> OK. I do have another question about one point. The text currently says:
>>
>>   "udp" indicates an unspecified protocol over UDP.
>>
>> This implies that there is some other protocol over UDP. But indeed 
>> there is no mechanism for specifying such. ISTM that this statement 
>> is wrong - that this proto means that UDP is used directly as the 
>> protocol.
>>
>> For instance, you could conceivably specify
>>
>>  m=text 50000 UDP plain
>>
>> and then just sending plain text in UDP packets. But you would then 
>> have to live with the fact that reordering and packet loss may occur.
>
> Agree.
>
>> Alternatively you could define a new mime type that has packet 
>> sequence numbers and use those to do *something* to cope with packet 
>> loss and reordering. *That* might be functionally equivalent to 
>> defining another protocol layer, but it is then not "unspecified", 
>> and as far as SDP is concerned it isn't a protocol since it is part 
>> of the fmt.
>>
>> Bottom line, ISTM the above should not say "unspecified protocol". 
>> Perhaps:
>>
>>   "udp" indicates direct use of the UDP protocol.
>>
>> How does that work for people?
>
> Makes sense to me. Or maybe something like “…indicates that the data 
> is transported directly in UDP with no additional framing”, if we want 
> to be verbose?
>
Sounds good.

-- Flemming
> -- 
> Colin Perkins
> https://csperkins.org/
>
>
>
>


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/25/18 7:06 PM, Colin Perkins
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:77623858-233D-4A42-A7D4-A0437F45A643@csperkins.org">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <br class="">
      <div>
        <blockquote type="cite" class="">
          <div class="">On 25 Apr 2018, at 17:42, Paul Kyzivat &lt;<a
              href="mailto:pkyzivat@alum.mit.edu" class=""
              moz-do-not-send="true">pkyzivat@alum.mit.edu</a>&gt;
            wrote:</div>
          <br class="Apple-interchange-newline">
          <div class=""><span style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">On 4/23/18 12:33 PM, Colin
              Perkins wrote:</span><br style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <blockquote type="cite" style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-size-adjust: auto;
              -webkit-text-stroke-width: 0px;" class="">Paul,<br
                class="">
              <blockquote type="cite" class="">On 23 Apr 2018, at 16:36,
                Paul Kyzivat &lt;<a href="mailto:pkyzivat@alum.mit.edu"
                  class="" moz-do-not-send="true">pkyzivat@alum.mit.edu</a>&gt;
                wrote:<br class="">
                <br class="">
                Magnus, Colin, Flemming, and others,<br class="">
                <br class="">
                On 4/23/18 4:07 AM, Magnus Westerlund wrote:<br class="">
                <br class="">
                <blockquote type="cite" class="">
                  <blockquote type="cite" class="">... But my question
                    was a bigger one than that. My question is what does
                    it *mean* for the fmt for UDP to be a mime type?
                    This was never explained, from the beginning. I
                    *guess* that the intent was that every UDP packet
                    body conform to the mime type. Was that the original
                    intent? Or is the mime type somehow to describe the
                    whole stream of packets?<br class="">
                  </blockquote>
                </blockquote>
              </blockquote>
              The contents of each UDP packet have to conform to the
              signalled media type. This is exactly the same as when RTP
              is used, where the contents of every RTP packet have to
              conform to the signalled media type (i.e., the RTP payload
              format).<br class="">
              <blockquote type="cite" class="">
                <blockquote type="cite" class="">
                  <blockquote type="cite" class="">IOW, it seems to me
                    that the definition of fmt for UDP is
                    underspecified. I would like to complete the
                    specification but don't know what the intent is. I
                    can make something up, but that seems like a bad
                    idea.<br class="">
                    <br class="">
                    I'll also note that I'm not aware of any cases that
                    actually use UDP as transport and a mime type as the
                    fmt.<br class="">
                  </blockquote>
                  So Colin, may have a better recollection of those
                  early discussions. But, yes I do think that the
                  original intention was to put the subtype of the MIME
                  type in the fmt space. However, based on the later
                  discussions around use of MIME types I think that is
                  problematic. The proto + fmt combination does
                  basically identify a specific transport protocol and
                  format to be used. That doesn't match MIME, which is a
                  specific format only. We had a long discussion around
                  the MIME type usage with RTP, which is much more
                  specific.<br class="">
                  What I would do here is to create a SDP specific
                  registry but maintain the MIME syntax for any entry,
                  and make it clear that what ever like to register here
                  needs to define what foo over UDP is. So specification
                  required at least.<br class="">
                  /Magnus<br class="">
                </blockquote>
                That seems like a prudent direction to take. But it also
                seems like something well in excess of a simple
                editorial action. I can propose something, but I would
                think it would deserve some serious discussion in the
                WG. (If it is possible to find enough people to have
                that discussion.)<br class="">
                <br class="">
                The things that I can recall that use UDP have all
                chosen to define a new proto value and then specify how
                to use fmt with that.<br class="">
                <br class="">
                Are there *any* cases of RFCs where a proto of UDP is
                used with a mime subtype as fmt? Maybe we could simply
                deprecate this usage.<br class="">
              </blockquote>
              SDP specifies the transport protocol and the data format
              that’s conveyed within that transport protocol. The
              transport protocol is identified by the “proto” field. The
              data format is identified by the combination of the media
              type (“media”) and the subtype (“fmt”).<br class="">
              For RTP, the fmt field references a media subtype
              indirectly:<br class="">
              <span class="Apple-tab-span" style="white-space: pre;">	</span>m=video
              51372 RTP/AVP 99<br class="">
              <span class="Apple-tab-span" style="white-space: pre;">	</span>a=rtpmap:99
              h263-1998/90000<br class="">
              Here the transport is “RTP/AVP" and the media type is
              “video/h263-1990; rate=90000”. RFC 3555 describes the
              process for mapping media type names and parameters onto
              SDP using the combination of “a=rtpmap:”, “a=ptime:”,
              “a=maxptime:”, and “a=fmtp:” lines.<br class="">
              For UDP, the fmt directly references a media subtype:<br
                class="">
              <span class="Apple-tab-span" style="white-space: pre;">	</span>m=application
              10000 udp foo<br class="">
              In this case, the media type is “application/foo”, and the
              UDP packets contain data that is formatted as described in
              the media type registration for "application/foo”. We
              don’t need an SDP specific registry: it’s just a standard
              media type registration, presumably with a note in its
              Encoding Considerations section to the effect that “This
              media type is only defined for transmission over UDP”.<br
                class="">
            </blockquote>
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">Thanks. You are confirming
              what I *thought* was intended, though it isn't stated very
              clearly.</span><br style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <blockquote type="cite" style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-size-adjust: auto;
              -webkit-text-stroke-width: 0px;" class="">What seems to be
              missing in RFC 4566 is a statement that “a=fmtp:”
              parameters can be used to convey media type parameters for
              media formats sent over UDP.<br class="">
            </blockquote>
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">OK. That is something that we
              can do.</span><br style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <blockquote type="cite" style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-size-adjust: auto;
              -webkit-text-stroke-width: 0px;" class="">For other
              transport protocols, the registration of the “proto” value
              denoting the transport states whether media types are used
              to describe the payload with that transport too, or
              whether the “fmt” namespace is managed differently. It
              would likely be a good idea to say that new protocols
              SHOULD use the media type namespace, for consistency, but
              there’s nothing in SDP that requires they do so.<br
                class="">
              Using UDP as the transport doesn’t seem especially useful,
              since in most cases I’d expect some additional framing to
              be needed to allow loss or reordering to be detected, but
              it seems conceptually well specified (although perhaps the
              text could be clearer in places). I don’t think
              deprecating UDP as a transport is appropriate, although
              clarifying when it should be used might be a good idea.<br
                class="">
            </blockquote>
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">OK. I do have another
              question about one point. The text currently says:</span><br
              style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">  "udp" indicates an
              unspecified protocol over UDP.</span><br
              style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">This implies that there is
              some other protocol over UDP. But indeed there is no
              mechanism for specifying such. ISTM that this statement is
              wrong - that this proto means that UDP is used directly as
              the protocol.</span><br style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">For instance, you could
              conceivably specify</span><br style="font-family:
              Inconsolata; font-size: 10px; font-style: normal;
              font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;"
              class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class=""> m=text 50000 UDP plain</span><br
              style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">and then just sending plain
              text in UDP packets. But you would then have to live with
              the fact that reordering and packet loss may occur.</span><br
              style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
          </div>
        </blockquote>
        <div><br class="">
        </div>
        Agree.</div>
      <div><br class="">
        <blockquote type="cite" class="">
          <div class=""><span style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">Alternatively you could
              define a new mime type that has packet sequence numbers
              and use those to do *something* to cope with packet loss
              and reordering. *That* might be functionally equivalent to
              defining another protocol layer, but it is then not
              "unspecified", and as far as SDP is concerned it isn't a
              protocol since it is part of the fmt.</span><br
              style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">Bottom line, ISTM the above
              should not say "unspecified protocol". Perhaps:</span><br
              style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">  "udp" indicates direct use
              of the UDP protocol.</span><br style="font-family:
              Inconsolata; font-size: 10px; font-style: normal;
              font-variant-caps: normal; font-weight: normal;
              letter-spacing: normal; text-align: start; text-indent:
              0px; text-transform: none; white-space: normal;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;"
              class="">
            <br style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
            <span style="font-family: Inconsolata; font-size: 10px;
              font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; text-align:
              start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px; float: none; display:
              inline !important;" class="">How does that work for
              people?</span><br style="font-family: Inconsolata;
              font-size: 10px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              text-align: start; text-indent: 0px; text-transform: none;
              white-space: normal; word-spacing: 0px;
              -webkit-text-stroke-width: 0px;" class="">
          </div>
        </blockquote>
      </div>
      <div class=""><br class="">
      </div>
      Makes sense to me. Or maybe something like “…indicates that the
      data is transported directly in UDP with no additional framing”,
      if we want to be verbose?<br class="">
      <div class=""><br class="">
      </div>
    </blockquote>
    Sounds good. <br>
    <br>
    -- Flemming <br>
    <blockquote type="cite"
      cite="mid:77623858-233D-4A42-A7D4-A0437F45A643@csperkins.org">
      <div class="">-- <br class="">
        Colin Perkins<br class="">
        <a href="https://csperkins.org/" class="" moz-do-not-send="true">https://csperkins.org/</a><br
          class="">
        <br class="">
        <br class="">
        <br class="">
      </div>
      <br class="">
    </blockquote>
    <br>
  </body>
</html>

--------------E245A6CC9FDDE63D5CACA08B--


From nobody Thu Apr 26 10:34:26 2018
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 6D07112783A for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 10:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7bW-eaLMHN7i for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 10:34:22 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91244124205 for <mmusic@ietf.org>; Thu, 26 Apr 2018 10:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1314; q=dns/txt; s=iport; t=1524764062; x=1525973662; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=k5u61qlCtHMpU4OF6CbtMO6DFp9cNf4nLazhGplYZFc=; b=AKGKPPAqtU+uOYbdw4r3NJ+qzlCIPHeyzT+IL6LKiwKb6vk990hNER2t J7pKWVoAPXahJJKJSjpnDheGh1aWiQcnjuYyjgz42qchMDWlQbghZfkx0 hss9aXoj4iHiQ9PuriedEOpuc5YCx4jhfxmtem8Qku9TX1Qsnq6e2mgVH I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C7AgALDeJa/4UNJK1bGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDYXoomGWBdIEPlQsLGAuEA0YCgkghOBQBAgEBAQEBAQJ?= =?us-ascii?q?sHAyFIwEBAQMBATABBTYbCxguJzAGAQwGAgEBhH4ND6pGhFiDboJABYgRgVQ?= =?us-ascii?q?/gQ8jgmiDEQEBhzQCmAkIjkIGh06FB5A7gSUzIYFSTSMVO4JDixCFWiMwkTQ?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos;i="5.49,331,1520899200"; d="scan'208";a="105485727"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Apr 2018 17:34:22 +0000
Received: from [10.118.10.19] (rtp-fandreas-2-8812.cisco.com [10.118.10.19]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id w3QHYLAd015559; Thu, 26 Apr 2018 17:34:21 GMT
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D7051253.2EB7A%christer.holmberg@ericsson.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <a2541e9a-121a-fc4c-a54d-5ec3737867d4@cisco.com>
Date: Thu, 26 Apr 2018 13:34:21 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <D7051253.2EB7A%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_6_fFH1E5Ur5ki8GXbEBMaKrbz0>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: Comments on section 4.4
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 26 Apr 2018 17:34:24 -0000

On 4/24/18 9:54 AM, Christer Holmberg wrote:
> Hi,
>
>
> Section 4.4 says:
>
>     "When present in both, the value in the
>      media-level takes precedence.  Thus, the value at the session-level
>      is effectively a default that applies to all data streams, unless
>      overridden by a media-level value.²
>
>
> This is basic offer/answer, so I suggest to remove the text.
Is that actually called out in RFC 3264 ? In either case, I'd prefer 
keeping the text.

-- Flemming
>
> ----
>
>
> Section 4.4 says:
>
>      "If two data streams have identical ice-ufrag¹s, they MUST have
> identical ice-pwd¹s.²
>
>
> This requirements does not exist in 5245bis, and in RFC 5245 it was only
> mentioned in the SDP attribute section. Is there a reason for this?
>
>
> ---
>
>
> Section 4.4 says:
>
>
>      "The ice-ufrag attribute MUST contain at least 24 bits of randomness,
>       and the ice-pwd attribute MUST contain at least 128 bits of
>       randomness.²
>
> This is correct. But, it is defined in 5245bis, so I would suggest to add:
> ³As defined in [ICE-BIS], theŠ².
>
>
>
> Regards,
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>


From nobody Thu Apr 26 10:37:41 2018
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 7A43B1200C5 for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 10:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bsaAiby4ETGz for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 10:37:36 -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 D57CC12783A for <mmusic@ietf.org>; Thu, 26 Apr 2018 10:37:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524764254; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=G6VZn1clBseaVqK+EeGMTA7Lg/JLI1xhWIGXK9VZwn0=; b=cQ4x2pZM3avgBskQPpHdqXvWu9/arvJGL5NHlXTdj6W/FhyJxkHCynWBIesFC+cf opc9HAvx7tqsrjv0shvTWcbKMMeEG9lThH9JnC5d2zlGk+5k20TyRG82GaUpAhy3 E4qCfGjGA5JmuvAwC1eSYCXgiATv0rh+3ajRj0i0xjY=;
X-AuditID: c1b4fb30-0dfff70000007681-a8-5ae20e5df982
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 23.81.30337.D5E02EA5; Thu, 26 Apr 2018 19:37:34 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0382.000; Thu, 26 Apr 2018 19:37:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Flemming Andreasen <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: Comments on section 4.4
Thread-Index: AQHT29PHLxi1RX6zWUCJ+OHk7AtJUqQTMHCAgAAiDSA=
Date: Thu, 26 Apr 2018 17:37:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E9FB97@ESESSMB109.ericsson.se>
References: <D7051253.2EB7A%christer.holmberg@ericsson.com> <a2541e9a-121a-fc4c-a54d-5ec3737867d4@cisco.com>
In-Reply-To: <a2541e9a-121a-fc4c-a54d-5ec3737867d4@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7jW4c36Mog5mfWC3eX9C1mLr8MYsD k8eU3xtZPZYs+ckUwBTFZZOSmpNZllqkb5fAlXF/8VX2goUsFXO/f2duYJzC3MXIySEhYCLR 3vWdvYuRi0NI4AijROP8o0wQzmJGic4n84GqODjYBCwkuv9pgzSICARJrL6/mwnEFhZwkPh3 ZSETRNxR4tGHo4wQtpXE0U2X2UBsFgFVicOPXoIt4xXwlbh0diEriC0kkCcxef8UFhCbU8BW oq/1O1g9o4CYxPdTa8BmMguIS9x6Mp8J4lABiSV7zkMdLSrx8vE/VghbSeLp/yVQ9XoSN6ZO YYOwtSWWLXwNtVdQ4uTMJywTGEVmIRk7C0nLLCQts5C0LGBkWcUoWpxanJSbbmSkl1qUmVxc nJ+nl5dasokRGA0Ht/w22MH48rnjIUYBDkYlHl4nzkdRQqyJZcWVuYcYJTiYlUR4d9x+GCXE m5JYWZValB9fVJqTWnyIUZqDRUmc18Jvc5SQQHpiSWp2ampBahFMlomDU6qBsfYiR0eksmRj ze7XLvlLBGYdCAx0EmnVn7rU6vC5Rf3ntmb+i8q1uHw03KR9/2qeTW9POufNNj+Sxs+xzmjh IXV94UlGFkcYPz79f1voDU9vU7uEiNEJUevvJ6+5fPcNDTuSlWXIWuFw27Vll7pGcWPDuUzN jtbpcqsmXKv7fu/FvLUJBsExSizFGYmGWsxFxYkAlrGNCYICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Vy9-7UbNYw77Lx4yYtDGLFie9u4>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: Comments on section 4.4
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 26 Apr 2018 17:37:37 -0000

Hi,

>> Section 4.4 says:
>>
>>     "When present in both, the value in the
>>      media-level takes precedence.  Thus, the value at the session-level
>>      is effectively a default that applies to all data streams, unless
>>      overridden by a media-level value.=B2
>>
>>
>> This is basic offer/answer, so I suggest to remove the text.
> Is that actually called out in RFC 3264 ?

It may be in RFC 4566. It's basic SDP.

We can keep it if you want, but we don't normally say this in other drafts.

Regards,

Christer


From nobody Thu Apr 26 11:15:53 2018
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 49694127978 for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 11:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juksJQdE9dTD for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 11:15:51 -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 AD88F1200E5 for <mmusic@ietf.org>; Thu, 26 Apr 2018 11:15:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524766548; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=+c97SZUSgn73afCp50PpkBsXqBd67ZA82wjgu28sf+0=; b=NncjB3o4viwog4nVsaeGkscQw2UvbAf2m7fb8MRkfj6bj26R6NT0pCEX1rENGkvC gMALPBtnuL0tAFYAXYp7RolHLp/Cb9bq6e98yTsl95mrsmhL7vgt5wsjAPDA8Drh yY5kabV8L+yRJkJOAh0VZ0GvOpGEMyw9+bJwp1p+zBc=;
X-AuditID: c1b4fb3a-112a09c00000729c-eb-5ae21753f2b5
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 0E.F2.29340.35712EA5; Thu, 26 Apr 2018 20:15:48 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0382.000; Thu, 26 Apr 2018 20:15:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AdPdifsa1+A9rByXQouU5ShxWGTTTw==
Date: Thu, 26 Apr 2018 18:15:09 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E9FC68@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72E9FC68ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyM2K7pW6I+KMog9Xr2C3md55mt1jx+hy7 xfmd65kspi5/zOLA4rFkyU8mj1k7n7B4TH7cxhzAHMVlk5Kak1mWWqRvl8CVsfPGGcaCPrmK yQsnsTYwrpbqYuTgkBAwkfjd7t3FyMUhJHCEUWLe3x/MEM5iRol/+1cyghSxCVhIdP/TBomL CKxllNj+5jxTFyMnh7CAjcShdQvAbBEBR4l3q0+zQth6Egvn97GA2CwCqhJzX61kBrF5BXwl 9r4+DFbPKCAm8f3UGjCbWUBc4taT+WC2hICAxJI955khbFGJl4//sULYShJP/y+Bqs+X+P6y hR1ipqDEyZlPWCYwCs5CMmoWkrJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7KkbR 4tTi4tx0IyO91KLM5OLi/Dy9vNSSTYzAaDm45bfVDsaDzx0PMQpwMCrx8M7hehQlxJpYVlyZ e4hRgoNZSYR3x+2HUUK8KYmVValF+fFFpTmpxYcYpTlYlMR5ndIsooQE0hNLUrNTUwtSi2Cy TBycUg2Mete6rjGpv2kRrprZUuds9Y3T4nZosjqPWHruuXzrn3NjiwSjPFWX3m+UleGW6dt5 8I3zdYfCD6kHIqYUJ+64acXRcKiVrT5zc4PxAblm4+PbbC4mbr/+4Ed3f2d+xyT3sCaPV3ce KHEppP+wCf3JcUn0zfzJyQeF35gYKFlO8Tm7mW3myqlKLMUZiYZazEXFiQCEOElXkgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/o3hvouuheq8jSNBxYfq5uzkUvEM>
Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 26 Apr 2018 18:15:52 -0000

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

Hi,

I have put together a pull request, where I start to suggest how to introdu=
ce the tagged m=3D section concept into BUNDLE, and to include more text on=
 how SDP attributes are included in BUNDLE groups.

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

Note that there is still work to do, and even the changes I have already do=
ne probably need some fine tuning and spell correction.

At this point I would like to know whether people (in particular Ekr - but =
also others) are ok with the approach in general.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B72E9FC68ESESSMB109erics_
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;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
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;
	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]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have put together a pull request, where I start to=
 suggest how to introduce the tagged m=3D section concept into BUNDLE, and =
to include more text on how SDP attributes are included in BUNDLE groups.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://github.com/cdh4u/draft-sdp-bundle=
/pull/59">https://github.com/cdh4u/draft-sdp-bundle/pull/59</a><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Note that there is still work to do, and even the ch=
anges I have already done probably need some fine tuning and spell correcti=
on.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At this point I would like to know whether people (i=
n particular Ekr &#8211; but also others) are ok with the approach in gener=
al.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B72E9FC68ESESSMB109erics_--


From nobody Thu Apr 26 11:27:06 2018
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 C62571200E5 for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 11:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1vEU6s0w8Us for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 11:27:02 -0700 (PDT)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::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 A801012DA54 for <mmusic@ietf.org>; Thu, 26 Apr 2018 11:26:49 -0700 (PDT)
Received: by mail-ua0-x236.google.com with SMTP id t4so17884745ual.1 for <mmusic@ietf.org>; Thu, 26 Apr 2018 11:26:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=EARmLcXYZerPUUY5lSe/6NMpmpCuATEVpiXoGTIrx54=; b=hqXJmzCF+Q9O7v7mS7GOWCXXqFp+Tc6ztL4JkqTDqhoTFTVBhz6vDfxUVYqUKTxtES LPtsrYo2Or7HJMDdm9MaNknsMmyAJeOZR8YLyqh/JGmrQlNvLEv9pcb162fJa/eiiYcd DC2EZtwLQNU/koIPdh0l2X68rHJhkvDlKA6DfmxDChqKJnrcBKBYOmMyFtaSC4VvVX54 JGkf4509UOUMX6ZgBla9yyB+Afji27VyGAVoSUQ5SpxApRkoKiWAkqxN2s75T2YycQcE 1rT92zP6j60a1z6QSF9QuZtj0l9xu05MLEBQa+pSoxTwY41GgHqu/QUGk56B9pUBPdHc jBzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=EARmLcXYZerPUUY5lSe/6NMpmpCuATEVpiXoGTIrx54=; b=anO7ELZyu/UNYnMExbkFB9/HNpPDv9dqfHuhZbx2/PgoOcAMsH8/WKZa7NefEB+Id7 T0P1JtWCNiUePRVs0tSVmLEKRFdZVlxCMwJoK7K3YRQmUzIFmMobBqJBXwbVt1MDDNv7 c+IHhoM5vhOdsTPaBvRMBltOUTL5gzlNURaJ40/7agjO8EDY0eGwmqRr3cjR0YvGKXfr eD4Tlx8pEeKMzYMB9blpo9leB4i2qO4OAtte8OIj1rm7+2SDQVIdP1jVGbLfeB3oXK4O y4iMZidrgyV8UZAf/UZrV5BiuvzNqJAKQRzw3TUnB7tSqVZqUaAYH88aKruF4YeVVPns NEsQ==
X-Gm-Message-State: ALQs6tCILmFr95mih3nMXzi/e8nv+1i7itR8Yz+hQfX+bUaQJR1Jy6hk payj/7bwgYzue2HmLtJGTWv8BIIM1mqDIo1140yxyg==
X-Google-Smtp-Source: AB8JxZqfDPhTbnRhcWnvL2ALHTQSszbBEDwJKaw/ozfoJPa6TIl0YdCPqxXdjQlFgeSRACPlSGsTWXsLpgPGAJy2LbQ=
X-Received: by 10.176.89.206 with SMTP id k14mr8116774uad.88.1524767208542; Thu, 26 Apr 2018 11:26:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.82 with HTTP; Thu, 26 Apr 2018 11:26:48 -0700 (PDT)
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 26 Apr 2018 11:26:48 -0700
Message-ID: <CAMRcRGRwPJUPPG0NB47088EMXpoDUktMgxLQ=T5YggHLC+z-HQ@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a114738c0d49884056ac4876b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gghu0TPcuWl0tysDdmZvAVKg8qI>
Subject: [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 26 Apr 2018 18:27:05 -0000

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

Hello All

  Flemming, Roman and myself met this morning to discuss the path forward
with ICE mismatch changes for ice-sip-sdp draft.

@flemming/@roman please feel free to correct if I have messed up somethings
:-)


Context:
------------
  Current version of the draft says, if the answerer finds that IP Address
in c= and port in m line doesn't match any of the candidates for a given m
section. the answerer MUST insert an ice-mismatch attribute and default to
RFC3264 procedures. Also the offerer's handling of ice-mismatch is
application dependent. [This was written this way in RFC5245 when dealing
with ALGs modifying the SDP in transit]

Roman's Observations:
-------------------------------
1. Above requirement is too restrictive given the current deployments of
ALGs where if the Answerer treated the new IP and port it found in C= and m
lines as candidates it learnt (say peer reflexive over signaling channel),
the ICE process may continue and even succeed. In these cases, it makes
more sense to not  include a=ice-mismatch attribute in the answer.

2. WebRTC implementations today populate IP (0.0.0.0/::) and port (9) when
trickling and the current draft text has implication to call such offers as
ice-mismatch.


Proposed Direction
-------------------------

Answerer Behavior:

If IP in C= attribute is one of [0.0.0.0/::] and port is 9, don't treat it
as ice-mismatch and continue normal processing.


When the Answerer sees IP in C= and port in m line that doesn't match any
of the candidates, treat it as a new candidate that it learnt via signaling
and continue normal ICE processing.  OTOH if the answerer isn't one such
implementation or does't want to do so, then it MUST insert a=ice-mismatch
and default to RFC3264 procedures.



Look forward for your inputs in making progress on this draft.


Cheers
Suhas Nandakumar

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

<div dir=3D"ltr">Hello All<div>=C2=A0</div><div>=C2=A0 Flemming, Roman and =
myself met this morning to discuss the path forward with ICE mismatch chang=
es for ice-sip-sdp draft.=C2=A0</div><div><br></div><div><div style=3D"colo=
r:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:nor=
mal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;=
letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;=
white-space:normal;word-spacing:0px;text-decoration-style:initial;text-deco=
ration-color:initial">@flemming/@roman please feel free to correct if I hav=
e messed up somethings :-)</div><br></div><div><br></div><div>Context:</div=
><div>------------</div><div>=C2=A0 Current version of the draft says, if t=
he answerer finds that IP Address in c=3D and port in m line doesn&#39;t ma=
tch any of the candidates for a given m section. the answerer MUST insert a=
n ice-mismatch attribute and default to RFC3264 procedures. Also the offere=
r&#39;s handling of ice-mismatch is application dependent. [This was writte=
n this way in RFC5245 when dealing with ALGs modifying the SDP in transit]<=
/div><div><br></div><div>Roman&#39;s Observations:</div><div>--------------=
-----------------</div><div>1. Above requirement is too restrictive given t=
he current deployments of ALGs where if the Answerer treated the new IP and=
 port it found in C=3D and m lines as candidates it learnt (say peer reflex=
ive over signaling channel), the ICE process may continue and even succeed.=
 In these cases, it makes more sense to not=C2=A0 include a=3Dice-mismatch =
attribute in the answer.</div><div><br></div><div>2. WebRTC implementations=
 today populate IP (<a href=3D"http://0.0.0.0/:">0.0.0.0/:</a>:) and port (=
9) when trickling and the current draft text has implication to call such o=
ffers as ice-mismatch.</div><div><br></div><div><br></div><div>Proposed Dir=
ection</div><div>-------------------------</div><div><div style=3D"color:rg=
b(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;=
font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;lett=
er-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whit=
e-space:normal;word-spacing:0px;text-decoration-style:initial;text-decorati=
on-color:initial"><br></div><div style=3D"color:rgb(34,34,34);font-family:a=
rial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:no=
rmal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;text-decoration-style:initial;text-decoration-color:initial">Answere=
r Behavior:</div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-s=
erif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-v=
ariant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;t=
ext-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text=
-decoration-style:initial;text-decoration-color:initial"><br></div><div sty=
le=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font=
-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-w=
eight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-trans=
form:none;white-space:normal;word-spacing:0px;text-decoration-style:initial=
;text-decoration-color:initial">If IP in C=3D attribute is one of [<a href=
=3D"http://0.0.0.0/:">0.0.0.0/:</a>:] and port is 9, don&#39;t treat it as =
ice-mismatch and continue normal processing.</div><br></div><div><br></div>=
<div>When the Answerer sees IP in C=3D and port in m line that doesn&#39;t =
match any of the candidates, treat it as a new candidate that it learnt via=
 signaling and continue normal ICE processing.=C2=A0 OTOH if the answerer i=
sn&#39;t one such implementation or does&#39;t want to do so, then it MUST =
insert a=3Dice-mismatch and default to RFC3264 procedures.=C2=A0<br></div><=
div><br></div><div><br></div><div><br></div><div>Look forward for your inpu=
ts in making progress on this draft.</div><div><br></div><div><br></div><di=
v>Cheers</div><div>Suhas Nandakumar</div></div>

--001a114738c0d49884056ac4876b--


From nobody Thu Apr 26 11:38:27 2018
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 913EC129C51 for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 11:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.308
X-Spam-Level: 
X-Spam-Status: No, score=-4.308 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, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVkjLNiO0Puf for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 11:38: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 3BB191200E5 for <mmusic@ietf.org>; Thu, 26 Apr 2018 11:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524767901; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=clGGhyyNuOMh87UbubD2jMG5IXNAnuWLtd9nsMpLnrM=; b=XiQvrCi7IgWgLV/FjKoUrJRC7m4o71Cs0NxUladhZgZkpwPeWcKVwMKKMitNmu7j h3mMZGc0oXGpmd+H6zgtbcRj8YUwc6rm/vRCaYuq5Y0lCvb0fE49P3P0C/fAAjg+ RUSrhzKCQ32yj6YEbpkxIna7sM6CSPOxA8TwCKanT0k=;
X-AuditID: c1b4fb25-5abff700000064d0-3e-5ae21c9d05dd
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id A3.85.25808.D9C12EA5; Thu, 26 Apr 2018 20:38:21 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0382.000; Thu, 26 Apr 2018 20:38:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>, mmusic WG <mmusic@ietf.org>
Thread-Topic: [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
Thread-Index: AQHT3Ywwt0rqRyhLmUaNDJ7/U7f8laQTYBHw
Date: Thu, 26 Apr 2018 18:38:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72E9FD28@ESESSMB109.ericsson.se>
References: <CAMRcRGRwPJUPPG0NB47088EMXpoDUktMgxLQ=T5YggHLC+z-HQ@mail.gmail.com>
In-Reply-To: <CAMRcRGRwPJUPPG0NB47088EMXpoDUktMgxLQ=T5YggHLC+z-HQ@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.162]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72E9FD28ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGbFdVHeuzKMog3sr5SymLn/MYrFzbgez A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJWxc/cM5oITeRWtM/ayNDCeyO5i5OSQEDCR +P+9lbmLkYtDSOAIo8SbI6vYIJzFjBLHv/4GynBwsAlYSHT/0wZpEBFwl9h3/TMriC0s4CLR O6OBGSLuKrGqYzkrhG0ksXTGOUYQm0VAVeL9hIlsIDavgK9ES+9PMFtIIEDi3YOjYPWcAoES L/ZtYQexGQXEJL6fWsMEYjMLiEvcejKfCeJQAYkle84zQ9iiEi8f/2OFsJUknv5fAlWfLzG1 cRU7xC5BiZMzn7BMYBSehWTULCRls5CUzQL6kllAU2L9Ln2IEkWJKd0P2SFsDYnWOXPZkcUX MLKvYhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAiMnoNbfqvuYLz8xvEQowAHoxIP7xauR1FC rIllxZW5hxglOJiVRHh33H4YJcSbklhZlVqUH19UmpNafIhRmoNFSZz3ofnmKCGB9MSS1OzU 1ILUIpgsEwenVANj0afsF63f9205N2WhXvieRZseL/y16/327OmXJx+5m3Tw9bOXDayvTSye daZdttE5tzg/9d0hdddtK5kTnLJvsqW0B084cmiSyO9wi4jTaUoejfrfS+t/lWnYvG3qidTc 3Po11HJ3bf9kldS/9+2bv3Off7pVyOZRY8bMHY2/Xhb0GbUbVtw5pMRSnJFoqMVcVJwIAJFt dAmaAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Q036UH57VPt9Cfu0uDK5hZUpWDM>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 26 Apr 2018 18:38:25 -0000

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

SGksDQoNClNob3VsZG7igJl0IHRoZSB0cmlja2xlIGNhc2UgKDAuMC4wLjA6OSkgYmUgZGVzY3Jp
YmVkIGluIHRoZSB0cmlja2xlIGRyYWZ0Pw0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpGcm9t
OiBtbXVzaWMgW21haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFN1
aGFzIE5hbmRha3VtYXINClNlbnQ6IDI2IEFwcmlsIDIwMTggMjA6MjcNClRvOiBtbXVzaWMgV0cg
PG1tdXNpY0BpZXRmLm9yZz4NClN1YmplY3Q6IFtNTVVTSUNdIGRyYWZ0LWljZS1zaXAtc2RwOiBJ
Q0UgTWlzbWF0Y2ggQ29uc2lkZXJhdGlvbnMNCg0KSGVsbG8gQWxsDQoNCiAgRmxlbW1pbmcsIFJv
bWFuIGFuZCBteXNlbGYgbWV0IHRoaXMgbW9ybmluZyB0byBkaXNjdXNzIHRoZSBwYXRoIGZvcndh
cmQgd2l0aCBJQ0UgbWlzbWF0Y2ggY2hhbmdlcyBmb3IgaWNlLXNpcC1zZHAgZHJhZnQuDQoNCkBm
bGVtbWluZy9Acm9tYW4gcGxlYXNlIGZlZWwgZnJlZSB0byBjb3JyZWN0IGlmIEkgaGF2ZSBtZXNz
ZWQgdXAgc29tZXRoaW5ncyA6LSkNCg0KDQpDb250ZXh0Og0KLS0tLS0tLS0tLS0tDQogIEN1cnJl
bnQgdmVyc2lvbiBvZiB0aGUgZHJhZnQgc2F5cywgaWYgdGhlIGFuc3dlcmVyIGZpbmRzIHRoYXQg
SVAgQWRkcmVzcyBpbiBjPSBhbmQgcG9ydCBpbiBtIGxpbmUgZG9lc24ndCBtYXRjaCBhbnkgb2Yg
dGhlIGNhbmRpZGF0ZXMgZm9yIGEgZ2l2ZW4gbSBzZWN0aW9uLiB0aGUgYW5zd2VyZXIgTVVTVCBp
bnNlcnQgYW4gaWNlLW1pc21hdGNoIGF0dHJpYnV0ZSBhbmQgZGVmYXVsdCB0byBSRkMzMjY0IHBy
b2NlZHVyZXMuIEFsc28gdGhlIG9mZmVyZXIncyBoYW5kbGluZyBvZiBpY2UtbWlzbWF0Y2ggaXMg
YXBwbGljYXRpb24gZGVwZW5kZW50LiBbVGhpcyB3YXMgd3JpdHRlbiB0aGlzIHdheSBpbiBSRkM1
MjQ1IHdoZW4gZGVhbGluZyB3aXRoIEFMR3MgbW9kaWZ5aW5nIHRoZSBTRFAgaW4gdHJhbnNpdF0N
Cg0KUm9tYW4ncyBPYnNlcnZhdGlvbnM6DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQoxLiBBYm92ZSByZXF1aXJlbWVudCBpcyB0b28gcmVzdHJpY3RpdmUgZ2l2ZW4gdGhlIGN1cnJl
bnQgZGVwbG95bWVudHMgb2YgQUxHcyB3aGVyZSBpZiB0aGUgQW5zd2VyZXIgdHJlYXRlZCB0aGUg
bmV3IElQIGFuZCBwb3J0IGl0IGZvdW5kIGluIEM9IGFuZCBtIGxpbmVzIGFzIGNhbmRpZGF0ZXMg
aXQgbGVhcm50IChzYXkgcGVlciByZWZsZXhpdmUgb3ZlciBzaWduYWxpbmcgY2hhbm5lbCksIHRo
ZSBJQ0UgcHJvY2VzcyBtYXkgY29udGludWUgYW5kIGV2ZW4gc3VjY2VlZC4gSW4gdGhlc2UgY2Fz
ZXMsIGl0IG1ha2VzIG1vcmUgc2Vuc2UgdG8gbm90ICBpbmNsdWRlIGE9aWNlLW1pc21hdGNoIGF0
dHJpYnV0ZSBpbiB0aGUgYW5zd2VyLg0KDQoyLiBXZWJSVEMgaW1wbGVtZW50YXRpb25zIHRvZGF5
IHBvcHVsYXRlIElQICgwLjAuMC4wLzo8aHR0cDovLzAuMC4wLjAvOj46KSBhbmQgcG9ydCAoOSkg
d2hlbiB0cmlja2xpbmcgYW5kIHRoZSBjdXJyZW50IGRyYWZ0IHRleHQgaGFzIGltcGxpY2F0aW9u
IHRvIGNhbGwgc3VjaCBvZmZlcnMgYXMgaWNlLW1pc21hdGNoLg0KDQoNClByb3Bvc2VkIERpcmVj
dGlvbg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpBbnN3ZXJlciBCZWhhdmlvcjoNCg0K
SWYgSVAgaW4gQz0gYXR0cmlidXRlIGlzIG9uZSBvZiBbMC4wLjAuMC86PGh0dHA6Ly8wLjAuMC4w
Lzo+Ol0gYW5kIHBvcnQgaXMgOSwgZG9uJ3QgdHJlYXQgaXQgYXMgaWNlLW1pc21hdGNoIGFuZCBj
b250aW51ZSBub3JtYWwgcHJvY2Vzc2luZy4NCg0KDQpXaGVuIHRoZSBBbnN3ZXJlciBzZWVzIElQ
IGluIEM9IGFuZCBwb3J0IGluIG0gbGluZSB0aGF0IGRvZXNuJ3QgbWF0Y2ggYW55IG9mIHRoZSBj
YW5kaWRhdGVzLCB0cmVhdCBpdCBhcyBhIG5ldyBjYW5kaWRhdGUgdGhhdCBpdCBsZWFybnQgdmlh
IHNpZ25hbGluZyBhbmQgY29udGludWUgbm9ybWFsIElDRSBwcm9jZXNzaW5nLiAgT1RPSCBpZiB0
aGUgYW5zd2VyZXIgaXNuJ3Qgb25lIHN1Y2ggaW1wbGVtZW50YXRpb24gb3IgZG9lcyd0IHdhbnQg
dG8gZG8gc28sIHRoZW4gaXQgTVVTVCBpbnNlcnQgYT1pY2UtbWlzbWF0Y2ggYW5kIGRlZmF1bHQg
dG8gUkZDMzI2NCBwcm9jZWR1cmVzLg0KDQoNCg0KTG9vayBmb3J3YXJkIGZvciB5b3VyIGlucHV0
cyBpbiBtYWtpbmcgcHJvZ3Jlc3Mgb24gdGhpcyBkcmFmdC4NCg0KDQpDaGVlcnMNClN1aGFzIE5h
bmRha3VtYXINCg==

--_000_7594FB04B1934943A5C02806D1A2204B72E9FD28ESESSMB109erics_
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
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlNob3VsZG7igJl0IHRoZSB0cmlja2xlIGNhc2UgKDAu
MC4wLjA6OSkgYmUgZGVzY3JpYmVkIGluIHRoZSB0cmlja2xlIGRyYWZ0PzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDtt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28t
ZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPkNocmlzdGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxFbmRDb21wb3NlIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9hPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj4gbW11c2ljIFttYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhh
bGYgT2YgPC9iPlN1aGFzIE5hbmRha3VtYXI8YnI+DQo8Yj5TZW50OjwvYj4gMjYgQXByaWwgMjAx
OCAyMDoyNzxicj4NCjxiPlRvOjwvYj4gbW11c2ljIFdHICZsdDttbXVzaWNAaWV0Zi5vcmcmZ3Q7
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFtNTVVTSUNdIGRyYWZ0LWljZS1zaXAtc2RwOiBJQ0UgTWlz
bWF0Y2ggQ29uc2lkZXJhdGlvbnM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5IZWxsbyBBbGw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PiZuYnNwOyBGbGVtbWluZywgUm9tYW4gYW5kIG15c2VsZiBtZXQgdGhpcyBtb3JuaW5nIHRvIGRp
c2N1c3MgdGhlIHBhdGggZm9yd2FyZCB3aXRoIElDRSBtaXNtYXRjaCBjaGFuZ2VzIGZvciBpY2Ut
c2lwLXNkcCBkcmFmdC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMjIyMjIiPkBmbGVtbWluZy9Acm9tYW4gcGxl
YXNlIGZlZWwgZnJlZSB0byBjb3JyZWN0IGlmIEkgaGF2ZSBtZXNzZWQgdXAgc29tZXRoaW5ncyA6
LSk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5Db250ZXh0OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+LS0tLS0tLS0tLS0tPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj4mbmJzcDsgQ3VycmVudCB2ZXJzaW9uIG9mIHRoZSBkcmFmdCBzYXlzLCBp
ZiB0aGUgYW5zd2VyZXIgZmluZHMgdGhhdCBJUCBBZGRyZXNzIGluIGM9IGFuZCBwb3J0IGluIG0g
bGluZSBkb2Vzbid0IG1hdGNoIGFueSBvZiB0aGUgY2FuZGlkYXRlcyBmb3IgYSBnaXZlbiBtIHNl
Y3Rpb24uIHRoZSBhbnN3ZXJlciBNVVNUIGluc2VydCBhbiBpY2UtbWlzbWF0Y2ggYXR0cmlidXRl
IGFuZCBkZWZhdWx0IHRvIFJGQzMyNjQgcHJvY2VkdXJlcy4NCiBBbHNvIHRoZSBvZmZlcmVyJ3Mg
aGFuZGxpbmcgb2YgaWNlLW1pc21hdGNoIGlzIGFwcGxpY2F0aW9uIGRlcGVuZGVudC4gW1RoaXMg
d2FzIHdyaXR0ZW4gdGhpcyB3YXkgaW4gUkZDNTI0NSB3aGVuIGRlYWxpbmcgd2l0aCBBTEdzIG1v
ZGlmeWluZyB0aGUgU0RQIGluIHRyYW5zaXRdPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlJvbWFuJ3MgT2JzZXJ2YXRpb25zOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+MS4gQWJvdmUgcmVxdWlyZW1lbnQgaXMgdG9vIHJlc3RyaWN0aXZlIGdpdmVu
IHRoZSBjdXJyZW50IGRlcGxveW1lbnRzIG9mIEFMR3Mgd2hlcmUgaWYgdGhlIEFuc3dlcmVyIHRy
ZWF0ZWQgdGhlIG5ldyBJUCBhbmQgcG9ydCBpdCBmb3VuZCBpbiBDPSBhbmQgbSBsaW5lcyBhcyBj
YW5kaWRhdGVzIGl0IGxlYXJudCAoc2F5IHBlZXIgcmVmbGV4aXZlIG92ZXIgc2lnbmFsaW5nIGNo
YW5uZWwpLCB0aGUgSUNFIHByb2Nlc3MNCiBtYXkgY29udGludWUgYW5kIGV2ZW4gc3VjY2VlZC4g
SW4gdGhlc2UgY2FzZXMsIGl0IG1ha2VzIG1vcmUgc2Vuc2UgdG8gbm90Jm5ic3A7IGluY2x1ZGUg
YT1pY2UtbWlzbWF0Y2ggYXR0cmlidXRlIGluIHRoZSBhbnN3ZXIuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjIuIFdlYlJUQyBpbXBsZW1lbnRh
dGlvbnMgdG9kYXkgcG9wdWxhdGUgSVAgKDxhIGhyZWY9Imh0dHA6Ly8wLjAuMC4wLzoiPjAuMC4w
LjAvOjwvYT46KSBhbmQgcG9ydCAoOSkgd2hlbiB0cmlja2xpbmcgYW5kIHRoZSBjdXJyZW50IGRy
YWZ0IHRleHQgaGFzIGltcGxpY2F0aW9uIHRvIGNhbGwgc3VjaCBvZmZlcnMgYXMgaWNlLW1pc21h
dGNoLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlByb3Bvc2VkIERpcmVjdGlvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMjIyMjIi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5z
LXNlcmlmO2NvbG9yOiMyMjIyMjIiPkFuc3dlcmVyIEJlaGF2aW9yOjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyMjIyMjIiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMyMjIyMjIiPklmIElQIGluIEM9IGF0dHJpYnV0ZSBpcyBvbmUgb2YgWzxhIGhy
ZWY9Imh0dHA6Ly8wLjAuMC4wLzoiPjAuMC4wLjAvOjwvYT46XSBhbmQgcG9ydCBpcyA5LCBkb24n
dCB0cmVhdCBpdCBhcyBpY2UtbWlzbWF0Y2ggYW5kIGNvbnRpbnVlIG5vcm1hbCBwcm9jZXNzaW5n
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PldoZW4gdGhlIEFuc3dlcmVyIHNlZXMgSVAgaW4gQz0gYW5kIHBvcnQgaW4gbSBsaW5lIHRoYXQg
ZG9lc24ndCBtYXRjaCBhbnkgb2YgdGhlIGNhbmRpZGF0ZXMsIHRyZWF0IGl0IGFzIGEgbmV3IGNh
bmRpZGF0ZSB0aGF0IGl0IGxlYXJudCB2aWEgc2lnbmFsaW5nIGFuZCBjb250aW51ZSBub3JtYWwg
SUNFIHByb2Nlc3NpbmcuJm5ic3A7IE9UT0ggaWYgdGhlIGFuc3dlcmVyIGlzbid0IG9uZSBzdWNo
IGltcGxlbWVudGF0aW9uDQogb3IgZG9lcyd0IHdhbnQgdG8gZG8gc28sIHRoZW4gaXQgTVVTVCBp
bnNlcnQgYT1pY2UtbWlzbWF0Y2ggYW5kIGRlZmF1bHQgdG8gUkZDMzI2NCBwcm9jZWR1cmVzLiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+TG9vayBmb3J3YXJkIGZvciB5b3VyIGlucHV0cyBpbiBtYWtpbmcgcHJvZ3Jlc3Mgb24g
dGhpcyBkcmFmdC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5DaGVlcnM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlN1aGFzIE5hbmRha3VtYXI8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B72E9FD28ESESSMB109erics_--


From nobody Thu Apr 26 12:51:16 2018
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 728BE127698 for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 12:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=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 AieJvgwsnim6 for <mmusic@ietfa.amsl.com>; Thu, 26 Apr 2018 12:51:12 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 DB990126C26 for <mmusic@ietf.org>; Thu, 26 Apr 2018 12:51:11 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id t4so18045520ual.1 for <mmusic@ietf.org>; Thu, 26 Apr 2018 12:51:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=popDyktwLAgLwd5AqF+k2zlqXL4iU9LkCs1dRbpBniM=; b=UYY6tTUT9Qx7BLv+dDw+/5otthTOrTjSi1kQmUJakmxOPygDNz2Nc6GffqDA1RH6w/ Q2Jn4NGGjET9coAjCazYwRwi/zUumSX9zQBCTQgmLTsk3rQZunVc9fbtxi7qBq2Lxz60 34cfBQHOc9idNrBmr/BsVwb5wbwYNq3oV+MhCHqhcA9Qf9VlTu+edI4fD3EMGR0gj9qh 5plxwa5uVNuiICzg9ihfVWlj/6SzJY27ykH/fgAdGyiCTbGnlaboBTcWHd6GJm4HdyQT tivAxWBKY1SfEhuLeDwZNAyJy08cZbmbem0mwDfFgBx5iDSyWh/G0y2+gw8unIbkhp49 fApw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=popDyktwLAgLwd5AqF+k2zlqXL4iU9LkCs1dRbpBniM=; b=BKpZpd/V71ENtJGfozo8cyaXNiJ73a2c9MTzUPra84x2XnksBMYXoT0YQHRb5MXeJ5 mb2ZvtR7CFpYl2sh+jbWO9nmrpSGtqxux4HRWYymyjGBtLYRiJNssw2KXP1iA+vDFMSn dDv3IVRtk5oCipSefk20N3EQfGWELmMDQoQ0jFGv8TdlNTbfFrPXuCa2Q/9dOWvRtipk CCyEU+9zJ56Ulknekg6G2E221rTnAE6sOOfHYIUB33Oj9j/klhyYrvq41EigDfZ1LGQ6 cXJhuKUX4L/V5BSVeEi4bA2wVWo6wlCc6Xg9ux6aY3BPQ6DBmP09+Y4A/GJ+y9DAFGXS ABtA==
X-Gm-Message-State: ALQs6tADyn5bsSqYXhWbntx/JOhWfy0DZaD6oQwMsAfXZy9lxTTjFjvQ CjV7ppSW9Fqy/++5mDt7/jv9DRGv/HzX9WGYZ/o=
X-Google-Smtp-Source: AB8JxZof02Fq8cU47WgAyqhP99I0Mg7716vbvOB78Up/1yEL1/wSLzQyfwQVJcCj9Owu1nfflt0lnhIHYdQHdPDOE/Y=
X-Received: by 10.176.37.8 with SMTP id j8mr7430635uan.83.1524772271060; Thu, 26 Apr 2018 12:51:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAMRcRGRwPJUPPG0NB47088EMXpoDUktMgxLQ=T5YggHLC+z-HQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E9FD28@ESESSMB109.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E9FD28@ESESSMB109.ericsson.se>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 26 Apr 2018 19:51:00 +0000
Message-ID: <CAMRcRGTRcti7vf7OS-z2HfUjc97+opnnUbu41peiGLTXJU2MRg@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="089e0832e270947b84056ac5b536"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0zM3LABP9WzsA7uECvZzK57BsPk>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 26 Apr 2018 19:51:15 -0000

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

Hi Christer

 Please see in-line

On Thu, Apr 26, 2018 at 11:38 AM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> Shouldn=E2=80=99t the trickle case (0.0.0.0:9) be described in the trickl=
e draft?
>

Trickle defines it , but the idea was not to call such thing as ice
mismatch in this draft.


>
> Regards,
>
>
>
> Christer
>
>
>
> *From:* mmusic [mailto:mmusic-bounces@ietf.org] *On Behalf Of *Suhas
> Nandakumar
> *Sent:* 26 April 2018 20:27
> *To:* mmusic WG <mmusic@ietf.org>
> *Subject:* [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
>
>
>
> Hello All
>
>
>
>   Flemming, Roman and myself met this morning to discuss the path forward
> with ICE mismatch changes for ice-sip-sdp draft.
>
>
>
> @flemming/@roman please feel free to correct if I have messed up
> somethings :-)
>
>
>
>
>
> Context:
>
> ------------
>
>   Current version of the draft says, if the answerer finds that IP Addres=
s
> in c=3D and port in m line doesn't match any of the candidates for a give=
n m
> section. the answerer MUST insert an ice-mismatch attribute and default t=
o
> RFC3264 procedures. Also the offerer's handling of ice-mismatch is
> application dependent. [This was written this way in RFC5245 when dealing
> with ALGs modifying the SDP in transit]
>
>
>
> Roman's Observations:
>
> -------------------------------
>
> 1. Above requirement is too restrictive given the current deployments of
> ALGs where if the Answerer treated the new IP and port it found in C=3D a=
nd m
> lines as candidates it learnt (say peer reflexive over signaling channel)=
,
> the ICE process may continue and even succeed. In these cases, it makes
> more sense to not  include a=3Dice-mismatch attribute in the answer.
>
>
>
> 2. WebRTC implementations today populate IP (0.0.0.0/::) and port (9)
> when trickling and the current draft text has implication to call such
> offers as ice-mismatch.
>
>
>
>
>
> Proposed Direction
>
> -------------------------
>
>
>
> Answerer Behavior:
>
>
>
> If IP in C=3D attribute is one of [0.0.0.0/::] and port is 9, don't treat
> it as ice-mismatch and continue normal processing.
>
>
>
>
>
> When the Answerer sees IP in C=3D and port in m line that doesn't match a=
ny
> of the candidates, treat it as a new candidate that it learnt via signali=
ng
> and continue normal ICE processing.  OTOH if the answerer isn't one such
> implementation or does't want to do so, then it MUST insert a=3Dice-misma=
tch
> and default to RFC3264 procedures.
>
>
>
>
>
>
>
> Look forward for your inputs in making progress on this draft.
>
>
>
>
>
> Cheers
>
> Suhas Nandakumar
>

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

<div><div dir=3D"auto">Hi Christer</div><div dir=3D"auto"><br></div><div di=
r=3D"auto">=C2=A0Please see in-line=C2=A0</div><br><div class=3D"gmail_quot=
e"><div dir=3D"auto">On Thu, Apr 26, 2018 at 11:38 AM Christer Holmberg &lt=
;<a href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericss=
on.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin: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_-5470866409716081805WordSection1">
<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">Shouldn=E2=80=99t the trickle case (<=
a href=3D"http://0.0.0.0:9" target=3D"_blank">0.0.0.0:9</a>) be described i=
n the trickle draft?</span></p></div></div></blockquote><div dir=3D"auto"><=
br></div><div dir=3D"auto">Trickle defines it , but the idea was not to cal=
l such thing as ice mismatch in this draft.</div><div dir=3D"auto"><br></di=
v><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_-5470866409716081805WordSection1"><p class=3D"MsoN=
ormal"><span 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 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_-5470866409716081805__MailEndCompose"><=
span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;c=
olor:#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.org</a>]
<b>On Behalf Of </b>Suhas Nandakumar<br>
<b>Sent:</b> 26 April 2018 20:27<br>
<b>To:</b> mmusic WG &lt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blan=
k">mmusic@ietf.org</a>&gt;<br>
<b>Subject:</b> [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations<u><=
/u><u></u></span></p></div></div><div lang=3D"EN-GB" link=3D"blue" vlink=3D=
"purple"><div class=3D"m_-5470866409716081805WordSection1">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Hello All<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 Flemming, Roman and myself met this morning t=
o discuss the path forward with ICE mismatch changes for ice-sip-sdp draft.=
=C2=A0<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"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222">@flemming/@roman please feel free to correct if I have m=
essed up somethings :-)<u></u><u></u></span></p>
</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">Context:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">------------<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 Current version of the draft says, if the ans=
werer finds that IP Address in c=3D and port in m line doesn&#39;t match an=
y of the candidates for a given m section. the answerer MUST insert an ice-=
mismatch attribute and default to RFC3264 procedures.
 Also the offerer&#39;s handling of ice-mismatch is application dependent. =
[This was written this way in RFC5245 when dealing with ALGs modifying the =
SDP in transit]<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Roman&#39;s Observations:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-------------------------------<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">1. Above requirement is too restrictive given the cu=
rrent deployments of ALGs where if the Answerer treated the new IP and port=
 it found in C=3D and m lines as candidates it learnt (say peer reflexive o=
ver signaling channel), the ICE process
 may continue and even succeed. In these cases, it makes more sense to not=
=C2=A0 include a=3Dice-mismatch attribute in the answer.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. WebRTC implementations today populate IP (<a href=
=3D"http://0.0.0.0/:" target=3D"_blank">0.0.0.0/:</a>:) and port (9) when t=
rickling and the current draft text has implication to call such offers as =
ice-mismatch.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Proposed Direction<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-------------------------<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222">Answerer Behavior:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222">If IP in C=3D attribute is one of [<a href=3D"http://0.0=
.0.0/:" target=3D"_blank">0.0.0.0/:</a>:] and port is 9, don&#39;t treat it=
 as ice-mismatch and continue normal processing.<u></u><u></u></span></p>
</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">When the Answerer sees IP in C=3D and port in m line=
 that doesn&#39;t match any of the candidates, treat it as a new candidate =
that it learnt via signaling and continue normal ICE processing.=C2=A0 OTOH=
 if the answerer isn&#39;t one such implementation
 or does&#39;t want to do so, then it MUST insert a=3Dice-mismatch and defa=
ult to RFC3264 procedures.=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"><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">Look forward for your inputs in making progress on t=
his draft.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Suhas Nandakumar<u></u><u></u></p>
</div>
</div>
</div></div></blockquote></div></div>

--089e0832e270947b84056ac5b536--


From nobody Fri Apr 27 06:29:56 2018
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 4C2DF124239 for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 06:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1YrWbyu_46S8 for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 06:29: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 07EC612421A for <mmusic@ietf.org>; Fri, 27 Apr 2018 06:29:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524835791; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=5hBykQId8IMqF4P+v1bPIqAPHu8l/BwNi08CjwzKzFY=; b=XRfBFdHXUdOOWyVvrHhwrGE+OVWVReyrcklAKDbt0OqEtUqBDjEGygpMZeeM083M rNzWpxV8CbCet60XvwJInBbwa4ajBzOyN6LPiXazHu6y8vsE43kyOEYJ/TIFdtqd HZMEAbk6oGs9UtGRr72ZqFsxqdi0aioR1lZiiNAvyAc=;
X-AuditID: c1b4fb30-0f7ff70000007681-46-5ae325cf3130
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 8F.DD.30337.FC523EA5; Fri, 27 Apr 2018 15:29:51 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0382.000; Fri, 27 Apr 2018 15:29:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Ben Campbell" <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/A==
Date: Fri, 27 Apr 2018 13:29:50 +0000
Message-ID: <D70900B4.2EFCA%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.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D70900B42EFCAchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2K7hO551cdRBht2iVrM7zzNbrHi9Tl2 i/M71zNZTF3+mMWBxWPJkp9MHrN2PmHxmPy4jTmAOYrLJiU1J7MstUjfLoEr4+CtuywF70wr Gjr/MDYwTtbvYuTkkBAwkdh25zp7FyMXh5DAEUaJLau2MEI4ixkl5r04BuRwcLAJWEh0/9MG iYsIPGaU2LRpGiNIt7CAp8S0twvZQGwRAS+JUwuns0DYehIdG+ezg9gsAqoSe2d8ZwKxeQWs JW5OfQhWzyggJvH91BqwOLOAuMStJ/OZIC4SkFiy5zwzhC0q8fLxP1YQWxRo5oYTt9lB7pEQ UJK4vcEJojVBYvuF5WwQ4wUlTs58wjKBUWgWkqmzkJTNQlIGETeQeH9uPjOErS2xbOFrKFtf YuOXs4wQtrXE7Ku/WZHVLGDkWMUoWpxanJSbbmSkl1qUmVxcnJ+nl5dasokRGF0Ht/w22MH4 8rnjIUYBDkYlHt5IocdRQqyJZcWVuYcYJTiYlUR4d9x+GCXEm5JYWZValB9fVJqTWnyIUZqD RUmc18Jvc5SQQHpiSWp2ampBahFMlomDU6qBkbUinrP26a9HO/SaYo40mKkcD9ofn1f01Xbh MZ7lPjadYrz/Gf29D/mJt15YXew8p7RsAtO08+dvMJ0osuNgerXJvnu/h5jWPg3PzZ7TpDe2 WssuWuO+omPnkimsKn5P0n5G2k3w/2X9bWn89dJ9seeX/J1vZnfY9Nuve26vn9/Tcrr29lT5 ISWW4oxEQy3mouJEAL2yV0CqAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/miJP4quhHT9LZFg_vEAd9HcwDSs>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 27 Apr 2018 13:29:55 -0000

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

Hi,

I have added more changes to the pull request. Basically, the whole SDP Off=
er/Answer section has now been modified.

I would like people to take a look at the changes. In case it=92s difficult=
 to read the text in GitHub, you can download the XML and generate a text v=
ersion (I have verified that xml2rfc works).

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: Thursday 26 April 2018 at 21:15
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmus=
ic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>, Ben Campbell <ben@nostr=
um.com<mailto:ben@nostrum.com>>, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtf=
m.com>>
Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have put together a pull request, where I start to suggest how to introdu=
ce the tagged m=3D section concept into BUNDLE, and to include more text on=
 how SDP attributes are included in BUNDLE groups.

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

Note that there is still work to do, and even the changes I have already do=
ne probably need some fine tuning and spell correction.

At this point I would like to know whether people (in particular Ekr =96 bu=
t also others) are ok with the approach in general.

Regards,

Christer

--_000_D70900B42EFCAchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <EBEBA4293318CC4DAEA7CC45DAA93096@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 have added more changes to the pull request. Basically, the whole SD=
P Offer/Answer section has now been modified.</div>
<div><br>
</div>
<div>I would like people to take a look at the changes. In case it=92s diff=
icult to read the text in GitHub, you can download the XML and generate a t=
ext version (I have verified that xml2rfc works).</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>Thursday 26 April 2018 at 21:=
15<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;, &quot;<a href=3D"mailto:mmusic-chairs@ietf.org">mm=
usic-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic-chairs@ietf.org=
">mmusic-chairs@ietf.org</a>&gt;,
 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt=
;, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<b=
r>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] BUNDLE: Pull requ=
est to introduce tagged m=3D section<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:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
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;
	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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have put together a pull request, where I start to=
 suggest how to introduce the tagged m=3D section concept into BUNDLE, and =
to include more text on how SDP attributes are included in BUNDLE groups.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://github.com/cdh4u/draft-sdp-bundle=
/pull/59">https://github.com/cdh4u/draft-sdp-bundle/pull/59</a><o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Note that there is still work to do, and even the ch=
anges I have already done probably need some fine tuning and spell correcti=
on.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At this point I would like to know whether people (i=
n particular Ekr =96 but also others) are ok with the approach in general.<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D70900B42EFCAchristerholmbergericssoncom_--


From nobody Fri Apr 27 11:22:12 2018
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 9D81212778D for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 11:22:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NelfGo34Qmhx for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 11:22:09 -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 5A4CA124205 for <mmusic@ietf.org>; Fri, 27 Apr 2018 11:22:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524853327; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=crgagE6fOq0FL73qcFZLi58wpNsxZA4wRjcxtXBQ8QQ=; b=Hsx+zUvWwQ2b2Qy2nUVwe1Fc8OY93VaqIZb5HFwQbMoGGNGM7l15p5te+TRj9BG7 Xc8rsJzCghyT4xmpDwXssTkKJFm3k44dRKg59uNS7i7UvkXHHJMLiPwyPDsM1esP 4Xq9y2KMEvzETtlKz2AuOwRydaCBD5vzFQ+2TXIBpYM=;
X-AuditID: c1b4fb30-4c8039c000007681-bb-5ae36a4f0a34
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 79.F8.30337.F4A63EA5; Fri, 27 Apr 2018 20:22:07 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0382.000; Fri, 27 Apr 2018 20:22:07 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/KQU7OCA
Date: Fri, 27 Apr 2018 18:22:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com>
In-Reply-To: <D70900B4.2EFCA%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.165]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72EA21EBESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUyM2K7rq5/1uMog4urtC3md55mt1jx+hy7 xfmd65kspi5/zOLA4rFkyU8mj1k7n7B4TH7cxhzAHMVlk5Kak1mWWqRvl8CVMWPVMqaC7T4V 8/rvsTYwvnPuYuTkkBAwkdjV9Yyxi5GLQ0jgCKPExfUHmSGcxYwSvRtAMhwcbAIWEt3/tEHi IgJrGSW2vznPBNItLOAp8e7NYzYQW0TAS+LUwuksELaRxNa/31lBbBYBVYnuz//BbF4BX4nv 3ZfBbCEBa4npz56BzeEUsJHYsnsT2BxGATGJ76fWgMWZBcQlbj2ZzwRxqYDEkj3nmSFsUYmX j/+xQthKErNubYSqz5foPnaaGWKXoMTJmU9YJjAKz0IyahaSsllIyiDiOhILdn9ig7C1JZYt fM0MY5858JgJWXwBI/sqRtHi1OKk3HQjI73Uoszk4uL8PL281JJNjMD4Orjlt8EOxpfPHQ8x CnAwKvHwLnB+HCXEmlhWXJl7iFGCg1lJhHfH7YdRQrwpiZVVqUX58UWlOanFhxilOViUxHkt /DZHCQmkJ5akZqemFqQWwWSZODilGhhnv/VxOLdtwZtbx5wlrBVK+Rfc+fpn4wrXCT+lw2/q VkSt+KPv+MDK66ruVZ7NKw0794kzBh7+edj22KcVbL3Nbj7vWj+cZgrfdGOy3fbSJclh9ZV7 hW6e3veXw/kL56ZOhTKeJ8kyoh/Pm2hfzPdLeVXlua3HzEztU93CZN43OzWZJHoczV4psRRn JBpqMRcVJwIAbMgNsKsCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bXl10KPuzZZ5mvpQ7kVfl_MmAk8>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 27 Apr 2018 18:22:12 -0000

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

New commit with updated ICE Considerations.

Regards,

Christer

From: Christer Holmberg
Sent: 27 April 2018 15:30
To: Christer Holmberg <christer.holmberg@ericsson.com>; mmusic@ietf.org; mm=
usic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>; Eric Rescorla (ekr@rt=
fm.com) <ekr@rtfm.com>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have added more changes to the pull request. Basically, the whole SDP Off=
er/Answer section has now been modified.

I would like people to take a look at the changes. In case it's difficult t=
o read the text in GitHub, you can download the XML and generate a text ver=
sion (I have verified that xml2rfc works).

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: Thursday 26 April 2018 at 21:15
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmus=
ic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>, Ben Campbell <ben@nostr=
um.com<mailto:ben@nostrum.com>>, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtf=
m.com>>
Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have put together a pull request, where I start to suggest how to introdu=
ce the tagged m=3D section concept into BUNDLE, and to include more text on=
 how SDP attributes are included in BUNDLE groups.

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

Note that there is still work to do, and even the changes I have already do=
ne probably need some fine tuning and spell correction.

At this point I would like to know whether people (in particular Ekr - but =
also others) are ok with the approach in general.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B72EA21EBESESSMB109erics_
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;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">New commit with update=
d ICE Considerations.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></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" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Christer Holmberg
<br>
<b>Sent:</b> 27 April 2018 15:30<br>
<b>To:</b> Christer Holmberg &lt;christer.holmberg@ericsson.com&gt;; mmusic=
@ietf.org; mmusic-chairs@ietf.org; Ben Campbell &lt;ben@nostrum.com&gt;; Er=
ic Rescorla (ekr@rtfm.com) &lt;ekr@rtfm.com&gt;<br>
<b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section<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;color:black">Hi,</sp=
an><span style=3D"font-size:10.5pt;color:black;mso-fareast-language:EN-GB">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I have =
added more changes to the pull request. Basically, the whole SDP Offer/Answ=
er section has now been modified.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I would=
 like people to take a look at the changes. In case it&#8217;s difficult to=
 read the text in GitHub, you can download the XML and generate a text vers=
ion (I have verified that xml2rfc works).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Christe=
r<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></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"color:black">From: </span></b><spa=
n style=3D"color:black">mmusic &lt;<a href=3D"mailto:mmusic-bounces@ietf.or=
g">mmusic-bounces@ietf.org</a>&gt; on behalf of Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt;<br>
<b>Date: </b>Thursday 26 April 2018 at 21:15<br>
<b>To: </b>&quot;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&quo=
t; &lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;, &quot;<a=
 href=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&quot; &l=
t;<a href=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&gt;,
 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt=
;, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<b=
r>
<b>Subject: </b>[MMUSIC] BUNDLE: Pull request to introduce tagged m=3D sect=
ion<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">I have put together a pu=
ll request, where I start to suggest how to introduce the tagged m=3D secti=
on concept into BUNDLE, and to include more text on how SDP attributes are =
included in BUNDLE groups.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"https://githu=
b.com/cdh4u/draft-sdp-bundle/pull/59">https://github.com/cdh4u/draft-sdp-bu=
ndle/pull/59</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Note that there is still=
 work to do, and even the changes I have already done probably need some fi=
ne tuning and spell correction.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">At this point I would li=
ke to know whether people (in particular Ekr &#8211; but also others) are o=
k with the approach in general.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Regards,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Christer<o:p></o:p></spa=
n></p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B72EA21EBESESSMB109erics_--


From nobody Fri Apr 27 11:43:35 2018
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 178F312778D for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 11:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level: 
X-Spam-Status: No, score=-2.008 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, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, WEIRD_PORT=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 koy8kvacrjB2 for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 11:43:31 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c: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 658A9126D85 for <mmusic@ietf.org>; Fri, 27 Apr 2018 11:43:31 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id h134-v6so1682962vke.2 for <mmusic@ietf.org>; Fri, 27 Apr 2018 11:43:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BMI3+R5qQHgTyIrNa/MJRqrT8gWwGuaKTsZTt00yTYg=; b=X9F87UB/IzAbC7WgH3VdAw+cPobxoK5ruQV1h+xO3+8lthsJ2m+dthT3vCMtPLGEfz +8XHGANDuqIXcX3DHyghRSaYJgM3RVaqNy9X+4o+xVURvwC3mWWB9AqVfBj1iGcP6r/s wbyo0LTSKrKhRqo4lxedzOn1B3fFCkA52qTCtGSdBRbAGZOwA5pPPoYeIyNttXnz7cx9 YlLyPKgikc+jOoqUPu0MOId0RlANzPl3mpPimr8LRn1oOFcvV2S3JXPde0eEo5Sx5sQ1 NGnb54KTkvMO2oU91ureKPm7sam6pIJirMVqmRKu8GUOPtN3nF7ajDBOGgiDXfynWJa3 4G3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BMI3+R5qQHgTyIrNa/MJRqrT8gWwGuaKTsZTt00yTYg=; b=G4sG3ZemufcO3lkS1TefVGb0eRUv2xv+9+iTgNR+8UDwf6aaY3sIAqDSjfph452ceN 4ol7fofMYoYB5Eb2W0Dxko8A3CQ6G4lkUgbCTiW0BVL5VV4xa/fK6wt7XcpTXb5c+K8A mmv6Dfzu8Nday+piZ7rte9iZgXcvlEgPYU9YDlC5eUDx9WJ4oH8+5NBFxF49vmPEbwpm /TofJlkbM+lc+GQptVKCwZXE6Ei1cJkcsCUEzFft+D33fL0f/7f9hfJtivDMMIBY6NyP wHN8KE5qPs3AY0cS/ZbL1YDSs4MXesxzxvF2k/Bp3hoi+iMB+ODoLoX88/dnYyX/XbnZ z54w==
X-Gm-Message-State: ALQs6tBAP96tmTK6Ga+wv7haCTEJyJ7hTAEOI3/b+4LBUGWSivatmRpl h5a+Xs5KKvqd+Rhb8dcm5AJPeZXhI9q9g83dNqf49lYFM34=
X-Google-Smtp-Source: AB8JxZpCTTGxeVfBgdq+zu7+UXUkkx4C+KhkSACZVCfIhConkl6pg92DeFU1aMRpB6a88AF7pgzbv+wef1fJxlylXQY=
X-Received: by 2002:a1f:954:: with SMTP id 81-v6mr2269582vkj.46.1524854609871;  Fri, 27 Apr 2018 11:43:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.171.198 with HTTP; Fri, 27 Apr 2018 11:43:29 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se>
From: Taylor Brandstetter <deadbeef@google.com>
Date: Fri, 27 Apr 2018 11:43:29 -0700
Message-ID: <CAK35n0arRUfMO6vosi+KkudPPE-t8ej9-+2no9Fih2ruGE2R7Q@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>,  Ben Campbell <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary="0000000000005b977f056ad8e137"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DuptlxdGN7lXFbYMQdzSN3L74zA>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 27 Apr 2018 18:43:34 -0000

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

I'm happy with this approach in general; I believe it resolves the concerns
I had related to trickle ICE when used with BUNDLE (where "unique address"
may not be meaningful, since every m=3D section may have an address of "
0.0.0.0:9").

For some more context, see:
https://github.com/w3c/webrtc-pc/issues/1563#issuecomment-385051864

On Fri, Apr 27, 2018 at 11:22 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> New commit with updated ICE Considerations.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> *From:* Christer Holmberg
> *Sent:* 27 April 2018 15:30
> *To:* Christer Holmberg <christer.holmberg@ericsson.com>; mmusic@ietf.org=
;
> mmusic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>; Eric Rescorla (
> ekr@rtfm.com) <ekr@rtfm.com>
> *Subject:* Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D
> section
>
>
>
> Hi,
>
>
>
> I have added more changes to the pull request. Basically, the whole SDP
> Offer/Answer section has now been modified.
>
>
>
> I would like people to take a look at the changes. In case it=E2=80=99s d=
ifficult
> to read the text in GitHub, you can download the XML and generate a text
> version (I have verified that xml2rfc works).
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> *From: *mmusic <mmusic-bounces@ietf.org> on behalf of Christer Holmberg <
> christer.holmberg@ericsson.com>
> *Date: *Thursday 26 April 2018 at 21:15
> *To: *"mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <
> mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, Eric Rescorla <
> ekr@rtfm.com>
> *Subject: *[MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section
>
>
>
> Hi,
>
>
>
> I have put together a pull request, where I start to suggest how to
> introduce the tagged m=3D section concept into BUNDLE, and to include mor=
e
> text on how SDP attributes are included in BUNDLE groups.
>
>
>
> https://github.com/cdh4u/draft-sdp-bundle/pull/59
>
>
>
> Note that there is still work to do, and even the changes I have already
> done probably need some fine tuning and spell correction.
>
>
>
> At this point I would like to know whether people (in particular Ekr =E2=
=80=93 but
> also others) are ok with the approach in general.
>
>
>
> Regards,
>
>
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr"><div>I&#39;m happy with this approach in general; I believ=
e it resolves the concerns I had related to trickle ICE when used with BUND=
LE (where &quot;unique address&quot; may not be meaningful, since every m=
=3D section may have an address of &quot;<a href=3D"http://0.0.0.0:9">0.0.0=
.0:9</a>&quot;).</div><div><br></div>For some more context, see: <a href=3D=
"https://github.com/w3c/webrtc-pc/issues/1563#issuecomment-385051864">https=
://github.com/w3c/webrtc-pc/issues/1563#issuecomment-385051864</a><br></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Apr 27, =
2018 at 11:22 AM, Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto=
:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericss=
on.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 lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"m_4459091694900030118WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">New commit with update=
d ICE Considerations.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Regards,<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>=C2=A0<u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d">Christer<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><a name=3D"m_4459091694900030118__MailEndCompose"><s=
pan style=3D"color:#1f497d"><u></u>=C2=A0<u></u></span></a></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"> Christer Holmberg
<br>
<b>Sent:</b> 27 April 2018 15:30<br>
<b>To:</b> Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericss=
on.com" target=3D"_blank">christer.holmberg@ericsson.<wbr>com</a>&gt;; <a h=
ref=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>; <a hr=
ef=3D"mailto:mmusic-chairs@ietf.org" target=3D"_blank">mmusic-chairs@ietf.o=
rg</a>; Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blan=
k">ben@nostrum.com</a>&gt;; Eric Rescorla (<a href=3D"mailto:ekr@rtfm.com" =
target=3D"_blank">ekr@rtfm.com</a>) &lt;<a href=3D"mailto:ekr@rtfm.com" tar=
get=3D"_blank">ekr@rtfm.com</a>&gt;<br>
<b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Hi,</sp=
an><span style=3D"font-size:10.5pt;color:black"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I have =
added more changes to the pull request. Basically, the whole SDP Offer/Answ=
er section has now been modified.<u></u><u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I would=
 like people to take a look at the changes. In case it=E2=80=99s difficult =
to read the text in GitHub, you can download the XML and generate a text ve=
rsion (I have verified that xml2rfc works).<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Christe=
r<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
</span><div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0=
pt 0cm 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From: </span></b><spa=
n style=3D"color:black">mmusic &lt;<a href=3D"mailto:mmusic-bounces@ietf.or=
g" target=3D"_blank">mmusic-bounces@ietf.org</a>&gt; on behalf of Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_b=
lank">christer.holmberg@ericsson.<wbr>com</a>&gt;<span class=3D""><br>
<b>Date: </b>Thursday 26 April 2018 at 21:15<br>
<b>To: </b>&quot;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusi=
c@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blan=
k">mmusic@ietf.org</a>&gt;, &quot;<a href=3D"mailto:mmusic-chairs@ietf.org"=
 target=3D"_blank">mmusic-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:m=
music-chairs@ietf.org" target=3D"_blank">mmusic-chairs@ietf.org</a>&gt;,
 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_blank">ben@=
nostrum.com</a>&gt;, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" targ=
et=3D"_blank">ekr@rtfm.com</a>&gt;<br>
<b>Subject: </b>[MMUSIC] BUNDLE: Pull request to introduce tagged m=3D sect=
ion<u></u><u></u></span></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><u></u>=
=C2=A0<u></u></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi,<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">I have put together a pu=
ll request, where I start to suggest how to introduce the tagged m=3D secti=
on concept into BUNDLE, and to include more text on how SDP attributes are =
included in BUNDLE groups.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"https://githu=
b.com/cdh4u/draft-sdp-bundle/pull/59" target=3D"_blank">https://github.com/=
cdh4u/<wbr>draft-sdp-bundle/pull/59</a><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Note that there is still=
 work to do, and even the changes I have already done probably need some fi=
ne tuning and spell correction.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">At this point I would li=
ke to know whether people (in particular Ekr =E2=80=93 but also others) are=
 ok with the approach in general.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Regards,<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">=C2=A0<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:black">Christer<u></u><u></u></=
span></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>

--0000000000005b977f056ad8e137--


From nobody Fri Apr 27 11:53:51 2018
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 42F1412778D for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 11:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.308
X-Spam-Level: 
X-Spam-Status: No, score=-4.308 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, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzV7qf9FMHCE for <mmusic@ietfa.amsl.com>; Fri, 27 Apr 2018 11:53: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 3724C124205 for <mmusic@ietf.org>; Fri, 27 Apr 2018 11:53:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1524855225; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=sqLmmdJC9Dw1riX8yAro8epdAfZpTlQGNLx80+1r6Gc=; b=f3htf3lebwzrG+2IbKbmdo2j0iiTugR6Y/d4/vCeHPoKnWbWA7QNnoZ60GsRv4uH Lhfcy10a1rFSyYSJnqqSTaz10audx7/fZodp76fzQ1W0Eyo0BaNQPUbowI+wCg2J NU+J9gvOMW4i1NwG1x5UZw7mOELMmR0GdEde+DAEn4M=;
X-AuditID: c1b4fb2d-9d1ff700000068bb-6a-5ae371b81b91
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id FA.8E.26811.8B173EA5; Fri, 27 Apr 2018 20:53:45 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0382.000; Fri, 27 Apr 2018 20:53:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Taylor Brandstetter <deadbeef@google.com>
CC: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/KQU7OCA///khYCAACOsgA==
Date: Fri, 27 Apr 2018 18:53:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72EA23FD@ESESSMB109.ericsson.se>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <CAK35n0arRUfMO6vosi+KkudPPE-t8ej9-+2no9Fih2ruGE2R7Q@mail.gmail.com>
In-Reply-To: <CAK35n0arRUfMO6vosi+KkudPPE-t8ej9-+2no9Fih2ruGE2R7Q@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.171]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72EA23FDESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLIsWRmVeSWpSXmKPExsUyM2K7qO7OwsdRBuuOcljM7zzNbnF5xUNW ixWvz7FbnN+5nsli6vLHLA6sHgs2lXosWfKTyWPWzicsHpMftzEHsERx2aSk5mSWpRbp2yVw ZXy5+Zql4N4Wxopb7XUNjD/WM3YxcnJICJhIPDy2jrmLkYtDSOAIo0TrmiY2CGcxo8Sb69dZ uhg5ONgELCS6/2mDNIgI6Erc/LoQrIZZYC2jxJ3P59lAEsICnhLv3jxmgyjykji1cDoLhO0k 0da6hR3EZhFQlfi3bCMzyExeAV+JlfPUIXYdY5Q4+eofE0gNp0CgxLP9y8DmMAqISXw/tQYs ziwgLnHryXwmiKsFJJbsOc8MYYtKvHz8jxXCVpI48bCRGaI+X2LXukdge3kFBCVOznzCMoFR ZBaSUbOQlM1CUjYL6DxmAU2J9bv0IUoUJaZ0P2SHsDUkWufMZUcWX8DIvopRtDi1uDg33chY L7UoM7m4OD9PLy+1ZBMjMBIPbvmtu4Nx9WvHQ4wCHIxKPLx/nR5HCbEmlhVX5h5ilOBgVhLh 3XH7YZQQb0piZVVqUX58UWlOavEhRmkOFiVxXr1Ve6KEBNITS1KzU1MLUotgskwcnFINjO7f 4tScth7LE5JPUPmkH/tkT2ak8tX71dNc90tND81tnGoz6YwDa+/6x8wx96L7Ny/58tPvyFqm M/9YJ9c3rpCq/cK8bEKz5omkaS3mWo1mi8N/fVhpnCQhaXU0eIdK1xpWpuVLSrS6i7YHKa95 x7B3xkQOhiUdvuJyeZVaW87xe0X9/fJzgxJLcUaioRZzUXEiADIEWFzAAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FNIfKaQlm0pF0Qe8OXyi5XHn7K4>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 27 Apr 2018 18:53:50 -0000

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

SGksDQoNCk15IGFzc3VtcHRpb24gaXMgdGhhdCwgZXZlbiB3aXRoIHRyaWNrbGUgSUNFLCBpbiB0
aGUgaW5pdGlhbCBvZmZlciB5b3Ugd291bGQgc3RpbGwgYXNzaWduIGEgemVybyBwb3J0IHZhbHVl
IHRvIGJ1bmRsZS1vbmx5IG09IHNlY3Rpb25zLCBhbmQgb25jZSB0aGUgQlVORExFIGdyb3VwIGhh
cyBiZWVuIG5lZ290aWF0ZWQgd291bGQgYXNzaWduIGEgemVybyBwb3J0IHZhbHVlIHRvIGFsbCBi
dW5kbGVkIG09IHNlY3Rpb25zIGV4Y2VwdCB0aGUgdGFnZ2VkIG09IHNlY3Rpb25zLiBPbmx5IHRo
ZSB0YWdnZWQgbT0gc2VjdGlvbnMgd291bGQgY29udGFpbiB0aGUgbmluZSBwb3J0IHZhbHVlICh1
bnRpbCB0aGUgaG9zdCBjYW5kaWRhdGUgcG9ydCBpcyBldmVudHVhbGx5IGFzc2lnbmVkIHRvIHRo
ZSBtPSBzZWN0aW9uKS4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KRnJvbTogVGF5bG9yIEJy
YW5kc3RldHRlciBbbWFpbHRvOmRlYWRiZWVmQGdvb2dsZS5jb21dDQpTZW50OiAyNyBBcHJpbCAy
MDE4IDIwOjQzDQpUbzogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNz
c29uLmNvbT4NCkNjOiBtbXVzaWNAaWV0Zi5vcmc7IG1tdXNpYy1jaGFpcnNAaWV0Zi5vcmc7IEJl
biBDYW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPjsgRXJpYyBSZXNjb3JsYSAoZWtyQHJ0Zm0uY29t
KSA8ZWtyQHJ0Zm0uY29tPg0KU3ViamVjdDogUmU6IFtNTVVTSUNdIEJVTkRMRTogUHVsbCByZXF1
ZXN0IHRvIGludHJvZHVjZSB0YWdnZWQgbT0gc2VjdGlvbg0KDQpJJ20gaGFwcHkgd2l0aCB0aGlz
IGFwcHJvYWNoIGluIGdlbmVyYWw7IEkgYmVsaWV2ZSBpdCByZXNvbHZlcyB0aGUgY29uY2VybnMg
SSBoYWQgcmVsYXRlZCB0byB0cmlja2xlIElDRSB3aGVuIHVzZWQgd2l0aCBCVU5ETEUgKHdoZXJl
ICJ1bmlxdWUgYWRkcmVzcyIgbWF5IG5vdCBiZSBtZWFuaW5nZnVsLCBzaW5jZSBldmVyeSBtPSBz
ZWN0aW9uIG1heSBoYXZlIGFuIGFkZHJlc3Mgb2YgIjAuMC4wLjA6OTxodHRwOi8vMC4wLjAuMDo5
PiIpLg0KDQpGb3Igc29tZSBtb3JlIGNvbnRleHQsIHNlZTogaHR0cHM6Ly9naXRodWIuY29tL3cz
Yy93ZWJydGMtcGMvaXNzdWVzLzE1NjMjaXNzdWVjb21tZW50LTM4NTA1MTg2NA0KDQpPbiBGcmks
IEFwciAyNywgMjAxOCBhdCAxMToyMiBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhv
bG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29t
Pj4gd3JvdGU6DQpOZXcgY29tbWl0IHdpdGggdXBkYXRlZCBJQ0UgQ29uc2lkZXJhdGlvbnMuDQoN
ClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCkZyb206IENocmlzdGVyIEhvbG1iZXJnDQpTZW50OiAy
NyBBcHJpbCAyMDE4IDE1OjMwDQpUbzogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj47
IG1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPjsgbW11c2ljLWNoYWlyc0Bp
ZXRmLm9yZzxtYWlsdG86bW11c2ljLWNoYWlyc0BpZXRmLm9yZz47IEJlbiBDYW1wYmVsbCA8YmVu
QG5vc3RydW0uY29tPG1haWx0bzpiZW5Abm9zdHJ1bS5jb20+PjsgRXJpYyBSZXNjb3JsYSAoZWty
QHJ0Zm0uY29tPG1haWx0bzpla3JAcnRmbS5jb20+KSA8ZWtyQHJ0Zm0uY29tPG1haWx0bzpla3JA
cnRmbS5jb20+Pg0KU3ViamVjdDogUmU6IFtNTVVTSUNdIEJVTkRMRTogUHVsbCByZXF1ZXN0IHRv
IGludHJvZHVjZSB0YWdnZWQgbT0gc2VjdGlvbg0KDQpIaSwNCg0KSSBoYXZlIGFkZGVkIG1vcmUg
Y2hhbmdlcyB0byB0aGUgcHVsbCByZXF1ZXN0LiBCYXNpY2FsbHksIHRoZSB3aG9sZSBTRFAgT2Zm
ZXIvQW5zd2VyIHNlY3Rpb24gaGFzIG5vdyBiZWVuIG1vZGlmaWVkLg0KDQpJIHdvdWxkIGxpa2Ug
cGVvcGxlIHRvIHRha2UgYSBsb29rIGF0IHRoZSBjaGFuZ2VzLiBJbiBjYXNlIGl04oCZcyBkaWZm
aWN1bHQgdG8gcmVhZCB0aGUgdGV4dCBpbiBHaXRIdWIsIHlvdSBjYW4gZG93bmxvYWQgdGhlIFhN
TCBhbmQgZ2VuZXJhdGUgYSB0ZXh0IHZlcnNpb24gKEkgaGF2ZSB2ZXJpZmllZCB0aGF0IHhtbDJy
ZmMgd29ya3MpLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpGcm9tOiBtbXVzaWMgPG1tdXNp
Yy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZz4+IG9uIGJl
aGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29t
PG1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+Pg0KRGF0ZTogVGh1cnNkYXkg
MjYgQXByaWwgMjAxOCBhdCAyMToxNQ0KVG86ICJtbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNp
Y0BpZXRmLm9yZz4iIDxtbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4+LCAi
bW11c2ljLWNoYWlyc0BpZXRmLm9yZzxtYWlsdG86bW11c2ljLWNoYWlyc0BpZXRmLm9yZz4iIDxt
bXVzaWMtY2hhaXJzQGlldGYub3JnPG1haWx0bzptbXVzaWMtY2hhaXJzQGlldGYub3JnPj4sIEJl
biBDYW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPG1haWx0bzpiZW5Abm9zdHJ1bS5jb20+PiwgRXJp
YyBSZXNjb3JsYSA8ZWtyQHJ0Zm0uY29tPG1haWx0bzpla3JAcnRmbS5jb20+Pg0KU3ViamVjdDog
W01NVVNJQ10gQlVORExFOiBQdWxsIHJlcXVlc3QgdG8gaW50cm9kdWNlIHRhZ2dlZCBtPSBzZWN0
aW9uDQoNCkhpLA0KDQpJIGhhdmUgcHV0IHRvZ2V0aGVyIGEgcHVsbCByZXF1ZXN0LCB3aGVyZSBJ
IHN0YXJ0IHRvIHN1Z2dlc3QgaG93IHRvIGludHJvZHVjZSB0aGUgdGFnZ2VkIG09IHNlY3Rpb24g
Y29uY2VwdCBpbnRvIEJVTkRMRSwgYW5kIHRvIGluY2x1ZGUgbW9yZSB0ZXh0IG9uIGhvdyBTRFAg
YXR0cmlidXRlcyBhcmUgaW5jbHVkZWQgaW4gQlVORExFIGdyb3Vwcy4NCg0KaHR0cHM6Ly9naXRo
dWIuY29tL2NkaDR1L2RyYWZ0LXNkcC1idW5kbGUvcHVsbC81OQ0KDQpOb3RlIHRoYXQgdGhlcmUg
aXMgc3RpbGwgd29yayB0byBkbywgYW5kIGV2ZW4gdGhlIGNoYW5nZXMgSSBoYXZlIGFscmVhZHkg
ZG9uZSBwcm9iYWJseSBuZWVkIHNvbWUgZmluZSB0dW5pbmcgYW5kIHNwZWxsIGNvcnJlY3Rpb24u
DQoNCkF0IHRoaXMgcG9pbnQgSSB3b3VsZCBsaWtlIHRvIGtub3cgd2hldGhlciBwZW9wbGUgKGlu
IHBhcnRpY3VsYXIgRWtyIOKAkyBidXQgYWxzbyBvdGhlcnMpIGFyZSBvayB3aXRoIHRoZSBhcHBy
b2FjaCBpbiBnZW5lcmFsLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbW11c2ljIG1haWxpbmcgbGlzdA0K
bW11c2ljQGlldGYub3JnPG1haWx0bzptbXVzaWNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KDQo=

--_000_7594FB04B1934943A5C02806D1A2204B72EA23FDESESSMB109erics_
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
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPk15IGFzc3VtcHRpb24gaXMgdGhhdCwgZXZlbiB3aXRo
IHRyaWNrbGUgSUNFLCBpbiB0aGUgaW5pdGlhbCBvZmZlciB5b3Ugd291bGQgc3RpbGwgYXNzaWdu
IGEgemVybyBwb3J0IHZhbHVlIHRvIGJ1bmRsZS1vbmx5IG09IHNlY3Rpb25zLA0KIGFuZCBvbmNl
IHRoZSBCVU5ETEUgZ3JvdXAgaGFzIGJlZW4gbmVnb3RpYXRlZCB3b3VsZCBhc3NpZ24gYSB6ZXJv
IHBvcnQgdmFsdWUgdG8gYWxsIGJ1bmRsZWQgbT0gc2VjdGlvbnMgZXhjZXB0IHRoZSB0YWdnZWQg
bT0gc2VjdGlvbnMuIE9ubHkgdGhlIHRhZ2dlZCBtPSBzZWN0aW9ucyB3b3VsZCBjb250YWluIHRo
ZSBuaW5lIHBvcnQgdmFsdWUgKHVudGlsIHRoZSBob3N0IGNhbmRpZGF0ZSBwb3J0IGlzIGV2ZW50
dWFsbHkgYXNzaWduZWQgdG8gdGhlDQogbT0gc2VjdGlvbikuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJl
YXN0LWxhbmd1YWdlOkVOLVVTIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48YSBuYW1lPSJfTWFpbEVuZENvbXBvc2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L2E+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBU
YXlsb3IgQnJhbmRzdGV0dGVyIFttYWlsdG86ZGVhZGJlZWZAZ29vZ2xlLmNvbV0NCjxicj4NCjxi
PlNlbnQ6PC9iPiAyNyBBcHJpbCAyMDE4IDIwOjQzPGJyPg0KPGI+VG86PC9iPiBDaHJpc3RlciBI
b2xtYmVyZyAmbHQ7Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tJmd0Ozxicj4NCjxiPkNj
OjwvYj4gbW11c2ljQGlldGYub3JnOyBtbXVzaWMtY2hhaXJzQGlldGYub3JnOyBCZW4gQ2FtcGJl
bGwgJmx0O2JlbkBub3N0cnVtLmNvbSZndDs7IEVyaWMgUmVzY29ybGEgKGVrckBydGZtLmNvbSkg
Jmx0O2VrckBydGZtLmNvbSZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtNTVVTSUNdIEJV
TkRMRTogUHVsbCByZXF1ZXN0IHRvIGludHJvZHVjZSB0YWdnZWQgbT0gc2VjdGlvbjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JJ20gaGFwcHkgd2l0aCB0aGlz
IGFwcHJvYWNoIGluIGdlbmVyYWw7IEkgYmVsaWV2ZSBpdCByZXNvbHZlcyB0aGUgY29uY2VybnMg
SSBoYWQgcmVsYXRlZCB0byB0cmlja2xlIElDRSB3aGVuIHVzZWQgd2l0aCBCVU5ETEUgKHdoZXJl
ICZxdW90O3VuaXF1ZSBhZGRyZXNzJnF1b3Q7IG1heSBub3QgYmUgbWVhbmluZ2Z1bCwgc2luY2Ug
ZXZlcnkgbT0gc2VjdGlvbiBtYXkgaGF2ZSBhbiBhZGRyZXNzIG9mICZxdW90OzxhIGhyZWY9Imh0
dHA6Ly8wLjAuMC4wOjkiPjAuMC4wLjA6OTwvYT4mcXVvdDspLjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkZvciBzb21lIG1vcmUgY29udGV4dCwgc2VlOiA8
YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vdzNjL3dlYnJ0Yy1wYy9pc3N1ZXMvMTU2MyNpc3N1
ZWNvbW1lbnQtMzg1MDUxODY0Ij4NCmh0dHBzOi8vZ2l0aHViLmNvbS93M2Mvd2VicnRjLXBjL2lz
c3Vlcy8xNTYzI2lzc3VlY29tbWVudC0zODUwNTE4NjQ8L2E+PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBGcmksIEFwciAyNywgMjAxOCBhdCAxMToyMiBB
TSwgQ2hyaXN0ZXIgSG9sbWJlcmcgJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVy
Z0Blcmljc3Nvbi5jb20iIHRhcmdldD0iX2JsYW5rIj5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nv
bi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0Qi
Pk5ldyBjb21taXQgd2l0aCB1cGRhdGVkIElDRSBDb25zaWRlcmF0aW9ucy48L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5SZWdhcmRzLDwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPiZu
YnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4g
c3R5bGU9ImNvbG9yOiMxRjQ5N0QiPkNocmlzdGVyPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48YSBuYW1lPSJtXzQ0NTkwOTE2OTQ5MDAwMzAxMThfX01haWxF
bmRDb21wb3NlIj48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jm5ic3A7PC9zcGFuPjwvYT48
bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9w
OnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPjxiPjxzcGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNw
YW4gbGFuZz0iRU4tVVMiPiBDaHJpc3RlciBIb2xtYmVyZw0KPGJyPg0KPGI+U2VudDo8L2I+IDI3
IEFwcmlsIDIwMTggMTU6MzA8YnI+DQo8Yj5Ubzo8L2I+IENocmlzdGVyIEhvbG1iZXJnICZsdDs8
YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tIiB0YXJnZXQ9Il9i
bGFuayI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDs7DQo8YSBocmVmPSJt
YWlsdG86bW11c2ljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bW11c2ljQGlldGYub3JnPC9h
PjsgPGEgaHJlZj0ibWFpbHRvOm1tdXNpYy1jaGFpcnNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5r
Ij4NCm1tdXNpYy1jaGFpcnNAaWV0Zi5vcmc8L2E+OyBCZW4gQ2FtcGJlbGwgJmx0OzxhIGhyZWY9
Im1haWx0bzpiZW5Abm9zdHJ1bS5jb20iIHRhcmdldD0iX2JsYW5rIj5iZW5Abm9zdHJ1bS5jb208
L2E+Jmd0OzsgRXJpYyBSZXNjb3JsYSAoPGEgaHJlZj0ibWFpbHRvOmVrckBydGZtLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPmVrckBydGZtLmNvbTwvYT4pICZsdDs8YSBocmVmPSJtYWlsdG86ZWtyQHJ0
Zm0uY29tIiB0YXJnZXQ9Il9ibGFuayI+ZWtyQHJ0Zm0uY29tPC9hPiZndDs8YnI+DQo8Yj5TdWJq
ZWN0OjwvYj4gUmU6IFtNTVVTSUNdIEJVTkRMRTogUHVsbCByZXF1ZXN0IHRvIGludHJvZHVjZSB0
YWdnZWQgbT0gc2VjdGlvbjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6Ymxh
Y2siPkhpLDwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6YmxhY2siPiZu
YnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6YmxhY2siPkkgaGF2
ZSBhZGRlZCBtb3JlIGNoYW5nZXMgdG8gdGhlIHB1bGwgcmVxdWVzdC4gQmFzaWNhbGx5LCB0aGUg
d2hvbGUgU0RQIE9mZmVyL0Fuc3dlciBzZWN0aW9uIGhhcyBub3cgYmVlbiBtb2RpZmllZC48L3Nw
YW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrIj5JIHdvdWxkIGxpa2UgcGVv
cGxlIHRvIHRha2UgYSBsb29rIGF0IHRoZSBjaGFuZ2VzLiBJbiBjYXNlIGl04oCZcyBkaWZmaWN1
bHQgdG8gcmVhZCB0aGUgdGV4dCBpbiBHaXRIdWIsIHlvdSBjYW4gZG93bmxvYWQgdGhlIFhNTCBh
bmQgZ2VuZXJhdGUNCiBhIHRleHQgdmVyc2lvbiAoSSBoYXZlIHZlcmlmaWVkIHRoYXQgeG1sMnJm
YyB3b3JrcykuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjpibGFjayI+
Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjpibGFjayI+UmVn
YXJkcyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrIj4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOmJsYWNrIj5DaHJpc3Rl
cjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6YmxhY2siPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkZyb206
DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+bW11c2ljICZsdDs8YSBocmVm
PSJtYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5tbXVzaWMt
Ym91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+
RGF0ZTogPC9iPlRodXJzZGF5IDI2IEFwcmlsIDIwMTggYXQgMjE6MTU8YnI+DQo8Yj5UbzogPC9i
PiZxdW90OzxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5t
bXVzaWNAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+bW11c2ljQGlldGYub3JnPC9hPiZndDssICZxdW90OzxhIGhy
ZWY9Im1haWx0bzptbXVzaWMtY2hhaXJzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bW11c2lj
LWNoYWlyc0BpZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptbXVzaWMtY2hh
aXJzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+bW11c2ljLWNoYWlyc0BpZXRmLm9yZzwvYT4m
Z3Q7LA0KIEJlbiBDYW1wYmVsbCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmJlbkBub3N0cnVtLmNvbSIg
dGFyZ2V0PSJfYmxhbmsiPmJlbkBub3N0cnVtLmNvbTwvYT4mZ3Q7LCBFcmljIFJlc2NvcmxhICZs
dDs8YSBocmVmPSJtYWlsdG86ZWtyQHJ0Zm0uY29tIiB0YXJnZXQ9Il9ibGFuayI+ZWtyQHJ0Zm0u
Y29tPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+W01NVVNJQ10gQlVORExFOiBQdWxsIHJl
cXVlc3QgdG8gaW50cm9kdWNlIHRhZ2dlZCBtPSBzZWN0aW9uPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjVwdDtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9
ImNvbG9yOmJsYWNrIj5IaSw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkkg
aGF2ZSBwdXQgdG9nZXRoZXIgYSBwdWxsIHJlcXVlc3QsIHdoZXJlIEkgc3RhcnQgdG8gc3VnZ2Vz
dCBob3cgdG8gaW50cm9kdWNlIHRoZSB0YWdnZWQgbT0gc2VjdGlvbiBjb25jZXB0IGludG8gQlVO
RExFLCBhbmQgdG8gaW5jbHVkZSBtb3JlIHRleHQgb24gaG93DQogU0RQIGF0dHJpYnV0ZXMgYXJl
IGluY2x1ZGVkIGluIEJVTkRMRSBncm91cHMuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImNvbG9y
OmJsYWNrIj48YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vY2RoNHUvZHJhZnQtc2RwLWJ1bmRs
ZS9wdWxsLzU5IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9naXRodWIuY29tL2NkaDR1L2RyYWZ0
LXNkcC1idW5kbGUvcHVsbC81OTwvYT48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6Ymxh
Y2siPk5vdGUgdGhhdCB0aGVyZSBpcyBzdGlsbCB3b3JrIHRvIGRvLCBhbmQgZXZlbiB0aGUgY2hh
bmdlcyBJIGhhdmUgYWxyZWFkeSBkb25lIHByb2JhYmx5IG5lZWQgc29tZSBmaW5lIHR1bmluZyBh
bmQgc3BlbGwgY29ycmVjdGlvbi48L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2si
PkF0IHRoaXMgcG9pbnQgSSB3b3VsZCBsaWtlIHRvIGtub3cgd2hldGhlciBwZW9wbGUgKGluIHBh
cnRpY3VsYXIgRWtyIOKAkyBidXQgYWxzbyBvdGhlcnMpIGFyZSBvayB3aXRoIHRoZSBhcHByb2Fj
aCBpbiBnZW5lcmFsLjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+UmVnYXJk
cyw8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0
eWxlPSJjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkNocmlzdGVyPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KbW11c2ljIG1haWxpbmcg
bGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciPm1tdXNpY0BpZXRmLm9y
ZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L21tdXNpYyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vbW11c2ljPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B72EA23FDESESSMB109erics_--


From nobody Sat Apr 28 17:07:32 2018
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 0F9E8127871 for <mmusic@ietfa.amsl.com>; Sat, 28 Apr 2018 17:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, WEIRD_PORT=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 OJFHQPMPGYQ9 for <mmusic@ietfa.amsl.com>; Sat, 28 Apr 2018 17:07:28 -0700 (PDT)
Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::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 720391273E2 for <mmusic@ietf.org>; Sat, 28 Apr 2018 17:07:28 -0700 (PDT)
Received: by mail-ua0-x234.google.com with SMTP id s15so3421975uae.10 for <mmusic@ietf.org>; Sat, 28 Apr 2018 17:07:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JZd038XEjWFtIAUXwdjJmGkNllpPOE+MCNNCUZZvvSU=; b=Y6QYN9HfORxKX2QkU5Fuchi3cQna4zFaI0/xRcyQKvkEeY1kaQQrDA48pPDLufWfzL egg4NEgi9mDdOh3TqV1R5u3lHpbKzEy4lgMcujbPRJZv/v5uIf/fyTgwelt/mIYjV11F 51L/ykU6se2ME1SG85tCYkBhxOkjvxmXrxF17IIPN7u6KRsHzSl9L/n6ZZX4aB9XnoNo 9ESQ9m6Fjc36IuIk6PMS/Ai/JinY0fhKLh8iayDM1lKn6S0kwcQGiVS/jwAvqEXvcDVw uRZlkFclJDBG09cpIc/P2bGL60lmjurYiu8XMVwtOj0RDohLG1D8w681Pe7/Z+eQ7sZU WHSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JZd038XEjWFtIAUXwdjJmGkNllpPOE+MCNNCUZZvvSU=; b=RDvvCj9cjXJT5KhjPQrtbPgYheibef59+zOoNyltqsK97kQJ7YtELYVb52oqjR5uqX Ct5aQO2hvUmL1ZbKtWyoVn/XMl5VNSjuDPY6KNi/SS1kKDZ5FDJ7Z50ELdkLptulWKOY g+f2uYADc00PfqqVsYchvRDRIVQAt69gaO+CGDtUVEbHZ7u+njARSCHMOs8p1pIeM8LS HlmVEqK27VeUWHW6taOhFV7JBMrREds5D7UGmuE0b9Mc6VLLBeUnijq4Cz+GD0390++3 veyoCW/ra8o5XOOPmHdNwHbwLLC+XQOkro3LbIdgeJ+sy7LDpMn6vPzPZBcB1jDejhkc RV5Q==
X-Gm-Message-State: ALQs6tCEtUkN4LOjQOn15EMubKbltISyPC8NCgpiSjQE4tN2kWl/a2oD ZzPkxrDId2uLPubo1TI0frbocPgva4WQ5fYv+v0=
X-Google-Smtp-Source: AB8JxZqIhZ9lO9t6Dy1rBLJ/f2eK8NPKU3ZACRKzS8/5jcBCs8WxsqZo+KykQdT7HeAbRtW6rBnxQ+Snmo/rhC7wK0k=
X-Received: by 10.176.48.176 with SMTP id b16mr5304927uam.28.1524960447433; Sat, 28 Apr 2018 17:07:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.64.73 with HTTP; Sat, 28 Apr 2018 17:07:27 -0700 (PDT)
In-Reply-To: <CAMRcRGTRcti7vf7OS-z2HfUjc97+opnnUbu41peiGLTXJU2MRg@mail.gmail.com>
References: <CAMRcRGRwPJUPPG0NB47088EMXpoDUktMgxLQ=T5YggHLC+z-HQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B72E9FD28@ESESSMB109.ericsson.se> <CAMRcRGTRcti7vf7OS-z2HfUjc97+opnnUbu41peiGLTXJU2MRg@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Sat, 28 Apr 2018 17:07:27 -0700
Message-ID: <CAMRcRGQE6ocu6G-skOPEBoOqRNm0uMg32gzRyGE0YHuWGa=0FA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="089e0832c6fcc40e6a056af1857c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/N-d1k14ApGR6R4Cf-Dv5NSjunw8>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 29 Apr 2018 00:07:31 -0000

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

Hello All

   Wondering if its fine to make changes to the draft based on the above ?

Please let me know

Cheers
Suhas

On Thu, Apr 26, 2018 at 12:51 PM, Suhas Nandakumar <suhasietf@gmail.com>
wrote:

> Hi Christer
>
>  Please see in-line
>
> On Thu, Apr 26, 2018 at 11:38 AM Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>> Hi,
>>
>>
>>
>> Shouldn=E2=80=99t the trickle case (0.0.0.0:9) be described in the trick=
le draft?
>>
>
> Trickle defines it , but the idea was not to call such thing as ice
> mismatch in this draft.
>
>
>>
>> Regards,
>>
>>
>>
>> Christer
>>
>>
>>
>> *From:* mmusic [mailto:mmusic-bounces@ietf.org] *On Behalf Of *Suhas
>> Nandakumar
>> *Sent:* 26 April 2018 20:27
>> *To:* mmusic WG <mmusic@ietf.org>
>> *Subject:* [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations
>>
>>
>>
>> Hello All
>>
>>
>>
>>   Flemming, Roman and myself met this morning to discuss the path forwar=
d
>> with ICE mismatch changes for ice-sip-sdp draft.
>>
>>
>>
>> @flemming/@roman please feel free to correct if I have messed up
>> somethings :-)
>>
>>
>>
>>
>>
>> Context:
>>
>> ------------
>>
>>   Current version of the draft says, if the answerer finds that IP
>> Address in c=3D and port in m line doesn't match any of the candidates f=
or a
>> given m section. the answerer MUST insert an ice-mismatch attribute and
>> default to RFC3264 procedures. Also the offerer's handling of ice-mismat=
ch
>> is application dependent. [This was written this way in RFC5245 when
>> dealing with ALGs modifying the SDP in transit]
>>
>>
>>
>> Roman's Observations:
>>
>> -------------------------------
>>
>> 1. Above requirement is too restrictive given the current deployments of
>> ALGs where if the Answerer treated the new IP and port it found in C=3D =
and m
>> lines as candidates it learnt (say peer reflexive over signaling channel=
),
>> the ICE process may continue and even succeed. In these cases, it makes
>> more sense to not  include a=3Dice-mismatch attribute in the answer.
>>
>>
>>
>> 2. WebRTC implementations today populate IP (0.0.0.0/::) and port (9)
>> when trickling and the current draft text has implication to call such
>> offers as ice-mismatch.
>>
>>
>>
>>
>>
>> Proposed Direction
>>
>> -------------------------
>>
>>
>>
>> Answerer Behavior:
>>
>>
>>
>> If IP in C=3D attribute is one of [0.0.0.0/::] and port is 9, don't trea=
t
>> it as ice-mismatch and continue normal processing.
>>
>>
>>
>>
>>
>> When the Answerer sees IP in C=3D and port in m line that doesn't match =
any
>> of the candidates, treat it as a new candidate that it learnt via signal=
ing
>> and continue normal ICE processing.  OTOH if the answerer isn't one such
>> implementation or does't want to do so, then it MUST insert a=3Dice-mism=
atch
>> and default to RFC3264 procedures.
>>
>>
>>
>>
>>
>>
>>
>> Look forward for your inputs in making progress on this draft.
>>
>>
>>
>>
>>
>> Cheers
>>
>> Suhas Nandakumar
>>
>

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

<div dir=3D"ltr">Hello All<div><br></div><div>=C2=A0 =C2=A0Wondering if its=
 fine to make changes to the draft based on the above ?</div><div><br></div=
><div>Please let me know</div><div><br></div><div>Cheers</div><div>Suhas</d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, =
Apr 26, 2018 at 12:51 PM, Suhas Nandakumar <span dir=3D"ltr">&lt;<a href=3D=
"mailto:suhasietf@gmail.com" target=3D"_blank">suhasietf@gmail.com</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"><div><div dir=3D"auto">Hi C=
hrister</div><div dir=3D"auto"><br></div><div dir=3D"auto">=C2=A0Please see=
 in-line=C2=A0</div><br><div class=3D"gmail_quote"><span class=3D""><div di=
r=3D"auto">On Thu, Apr 26, 2018 at 11:38 AM Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.<wbr>com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" 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_1380419078540849575m_-5470866409716081805WordSection1">
<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">Shouldn=E2=80=99t the trickle case (<=
a href=3D"http://0.0.0.0:9" target=3D"_blank">0.0.0.0:9</a>) be described i=
n the trickle draft?</span></p></div></div></blockquote><div dir=3D"auto"><=
br></div></span><div dir=3D"auto">Trickle defines it , but the idea was not=
 to call such thing as ice mismatch in this draft.</div><span class=3D""><d=
iv dir=3D"auto"><br></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_1380419078540849575m_-5470=
866409716081805WordSection1"><p class=3D"MsoNormal"><span style=3D"font-siz=
e:11.0pt;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_1380419078540849575_m_-5470866409716081=
805__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.<wbr>org</a>]
<b>On Behalf Of </b>Suhas Nandakumar<br>
<b>Sent:</b> 26 April 2018 20:27<br>
<b>To:</b> mmusic WG &lt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blan=
k">mmusic@ietf.org</a>&gt;<br>
<b>Subject:</b> [MMUSIC] draft-ice-sip-sdp: ICE Mismatch Considerations<u><=
/u><u></u></span></p></div></div><div lang=3D"EN-GB" link=3D"blue" vlink=3D=
"purple"><div class=3D"m_1380419078540849575m_-5470866409716081805WordSecti=
on1">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Hello All<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 Flemming, Roman and myself met this morning t=
o discuss the path forward with ICE mismatch changes for ice-sip-sdp draft.=
=C2=A0<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"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222">@flemming/@roman please feel free to correct if I have m=
essed up somethings :-)<u></u><u></u></span></p>
</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">Context:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">------------<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 Current version of the draft says, if the ans=
werer finds that IP Address in c=3D and port in m line doesn&#39;t match an=
y of the candidates for a given m section. the answerer MUST insert an ice-=
mismatch attribute and default to RFC3264 procedures.
 Also the offerer&#39;s handling of ice-mismatch is application dependent. =
[This was written this way in RFC5245 when dealing with ALGs modifying the =
SDP in transit]<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Roman&#39;s Observations:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">------------------------------<wbr>-<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal">1. Above requirement is too restrictive given the cu=
rrent deployments of ALGs where if the Answerer treated the new IP and port=
 it found in C=3D and m lines as candidates it learnt (say peer reflexive o=
ver signaling channel), the ICE process
 may continue and even succeed. In these cases, it makes more sense to not=
=C2=A0 include a=3Dice-mismatch attribute in the answer.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. WebRTC implementations today populate IP (<a href=
=3D"http://0.0.0.0/:" target=3D"_blank">0.0.0.0/:</a>:) and port (9) when t=
rickling and the current draft text has implication to call such offers as =
ice-mismatch.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Proposed Direction<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-------------------------<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222">Answerer Behavior:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:#222222">If IP in C=3D attribute is one of [<a href=3D"http://0.0=
.0.0/:" target=3D"_blank">0.0.0.0/:</a>:] and port is 9, don&#39;t treat it=
 as ice-mismatch and continue normal processing.<u></u><u></u></span></p>
</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">When the Answerer sees IP in C=3D and port in m line=
 that doesn&#39;t match any of the candidates, treat it as a new candidate =
that it learnt via signaling and continue normal ICE processing.=C2=A0 OTOH=
 if the answerer isn&#39;t one such implementation
 or does&#39;t want to do so, then it MUST insert a=3Dice-mismatch and defa=
ult to RFC3264 procedures.=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"><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">Look forward for your inputs in making progress on t=
his draft.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Suhas Nandakumar<u></u><u></u></p>
</div>
</div>
</div></div></blockquote></span></div></div></blockquote></div><br></div>

--089e0832c6fcc40e6a056af1857c--


From nobody Sun Apr 29 13:39:10 2018
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 A4BB012711E for <mmusic@ietfa.amsl.com>; Sun, 29 Apr 2018 13:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RPJ0-xoVsArd for <mmusic@ietfa.amsl.com>; Sun, 29 Apr 2018 13:39:06 -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 89BA21271DF for <mmusic@ietf.org>; Sun, 29 Apr 2018 13:39:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1525034340; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=XccgcYiWHYgB9pXDL7UkK4w1kKkFrcdc8MxjDkj/dvY=; b=CwGKoyZ13yJV+ZAICVgM4FO0SuZtQZwiujkGRagmejVDma6AxWnS1WXGqn0rPfn+ ANNgkt3EuXQPD8wv9fWz8ANNcADWbHvRjodqX8bdH/d747bfurxoTGiMxCWzSQSk veOxzcQuvdUbioyZ07z0vE4aM92tY++/9QhReZnPrsk=;
X-AuditID: c1b4fb30-4c8039c000007681-97-5ae62d6460bd
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 04.93.30337.46D26EA5; Sun, 29 Apr 2018 22:39:00 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0382.000; Sun, 29 Apr 2018 22:38:59 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/KQU7OCAgANKT1A=
Date: Sun, 29 Apr 2018 20:38:59 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.170]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B72EA527AESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2K7qG6K7rMogz+HxS3md55mt1jx+hy7 xfmd65kspi5/zOLA4rFkyU8mj1k7n7B4TH7cxhzAHMVlk5Kak1mWWqRvl8CVserHNZaChqyK JfvqGhjfxHYxcnJICJhINE98wtTFyMUhJHCEUeLY7VNQzmJGiXur5zN2MXJwsAlYSHT/0waJ iwisZZTY/uY8E0i3sICnxLs3j9lAbBEBL4lTC6ezQNhWErvbl4LFWQRUJZobV4LFeQV8Jc7v OwwWFxKol+iatB7M5hTwk7i79S7YTEYBMYnvp9aA2cwC4hK3nsxngrhUQGLJnvPMELaoxMvH /1ghbCWJM5ues0DU50u8vnqVHWKXoMTJmU9YJjAKz0IyahaSsllIyiDiOhILdn9ig7C1JZYt fM0MY5858JgJWXwBI/sqRtHi1OKk3HQjI73Uoszk4uL8PL281JJNjMDoOrjlt8EOxpfPHQ8x CnAwKvHwTpF/FiXEmlhWXJl7iFGCg1lJhPdb5JMoId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwW fpujhATSE0tSs1NTC1KLYLJMHJxSDYx2v+a35koetnzbXWa+/HNpjkC8+8wVW6b9PdB5L+67 peu9o6YMxpO2MW6ZseetD9vmCz99trzvVLp1yCZUJ9PON9x2ems2T9WHW1rqRfoHeZSdz2Uq VX3tM/Q4YFGTb7YrlaffUCtA+DVzQMO6OT/Z7TOZdhiGX/lzMOr/gj1nbfaudZtUzqDEUpyR aKjFXFScCABOnVhHqgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wU-Rq6PAnijt1XX8PDP2bzjU8kg>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 29 Apr 2018 20:39:09 -0000

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

Hi,

I have now gone through the whole BUNDLE document, and modified the parts t=
hat I think need to be modified.

I would encourage anyone who is interested in BUNDLE to take a look at the =
pull request (or download the XML and generate a text document), because th=
ere have been quite a bit of changes. The good part is that most of the O/A=
 procedures in the document have been simplified.

I'd also like to chairs to give some guidance on how to move forward. Do we=
 need yet another WGLC? Etc.

Regards,

Christer



From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 27 April 2018 20:22
To: mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>=
; Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

New commit with updated ICE Considerations.

Regards,

Christer

From: Christer Holmberg
Sent: 27 April 2018 15:30
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>; mmusic@ietf.org<mailto:mmusic@ietf.org>; mmusic-chairs@=
ietf.org<mailto:mmusic-chairs@ietf.org>; Ben Campbell <ben@nostrum.com<mail=
to:ben@nostrum.com>>; Eric Rescorla (ekr@rtfm.com<mailto:ekr@rtfm.com>) <ek=
r@rtfm.com<mailto:ekr@rtfm.com>>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have added more changes to the pull request. Basically, the whole SDP Off=
er/Answer section has now been modified.

I would like people to take a look at the changes. In case it's difficult t=
o read the text in GitHub, you can download the XML and generate a text ver=
sion (I have verified that xml2rfc works).

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: Thursday 26 April 2018 at 21:15
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmus=
ic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>, Ben Campbell <ben@nostr=
um.com<mailto:ben@nostrum.com>>, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtf=
m.com>>
Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have put together a pull request, where I start to suggest how to introdu=
ce the tagged m=3D section concept into BUNDLE, and to include more text on=
 how SDP attributes are included in BUNDLE groups.

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

Note that there is still work to do, and even the changes I have already do=
ne probably need some fine tuning and spell correction.

At this point I would like to know whether people (in particular Ekr - but =
also others) are ok with the approach in general.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B72EA527AESESSMB109erics_
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;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have now gone throug=
h the whole BUNDLE document, and modified the parts that I think need to be=
 modified.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I would encourage anyo=
ne who is interested in BUNDLE to take a look at the pull request (or downl=
oad the XML and generate a text document), because there have been quite a =
bit of changes. The good part is that
 most of the O/A procedures in the document have been simplified.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I&#8217;d also like to=
 chairs to give some guidance on how to move forward. Do we need yet anothe=
r WGLC? Etc.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></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" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> mmusic [mailto:mmusic-bounces@ietf.org]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> 27 April 2018 20:22<br>
<b>To:</b> mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell &lt;ben@no=
strum.com&gt;; Eric Rescorla (ekr@rtfm.com) &lt;ekr@rtfm.com&gt;<br>
<b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">New commit with update=
d ICE Considerations.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></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" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Christer Holmberg
<br>
<b>Sent:</b> 27 April 2018 15:30<br>
<b>To:</b> Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericss=
on.com">christer.holmberg@ericsson.com</a>&gt;;
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a href=3D"mailto:m=
music-chairs@ietf.org">
mmusic-chairs@ietf.org</a>; Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.=
com">ben@nostrum.com</a>&gt;; Eric Rescorla (<a href=3D"mailto:ekr@rtfm.com=
">ekr@rtfm.com</a>) &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt=
;<br>
<b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section<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;color:black">Hi,</sp=
an><span style=3D"font-size:10.5pt;color:black;mso-fareast-language:EN-GB">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I have =
added more changes to the pull request. Basically, the whole SDP Offer/Answ=
er section has now been modified.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I would=
 like people to take a look at the changes. In case it&#8217;s difficult to=
 read the text in GitHub, you can download the XML and generate a text vers=
ion (I have verified that xml2rfc works).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Christe=
r<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></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"color:black">From: </span></b><spa=
n style=3D"color:black">mmusic &lt;<a href=3D"mailto:mmusic-bounces@ietf.or=
g">mmusic-bounces@ietf.org</a>&gt; on behalf of Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt;<br>
<b>Date: </b>Thursday 26 April 2018 at 21:15<br>
<b>To: </b>&quot;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&quo=
t; &lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;, &quot;<a=
 href=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&quot; &l=
t;<a href=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&gt;,
 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt=
;, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<b=
r>
<b>Subject: </b>[MMUSIC] BUNDLE: Pull request to introduce tagged m=3D sect=
ion<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">I have put together a pu=
ll request, where I start to suggest how to introduce the tagged m=3D secti=
on concept into BUNDLE, and to include more text on how SDP attributes are =
included in BUNDLE groups.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"https://githu=
b.com/cdh4u/draft-sdp-bundle/pull/59">https://github.com/cdh4u/draft-sdp-bu=
ndle/pull/59</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Note that there is still=
 work to do, and even the changes I have already done probably need some fi=
ne tuning and spell correction.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">At this point I would li=
ke to know whether people (in particular Ekr &#8211; but also others) are o=
k with the approach in general.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Regards,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Christer<o:p></o:p></spa=
n></p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B72EA527AESESSMB109erics_--


From nobody Sun Apr 29 14:38:19 2018
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 9C99112741D; Sun, 29 Apr 2018 14:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 kApWErQeydol; Sun, 29 Apr 2018 14:38:14 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87DEB127342; Sun, 29 Apr 2018 14:38:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17177; q=dns/txt; s=iport; t=1525037894; x=1526247494; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=aIXARIwyeZMvPTaNX4hcacmMGBBkHd1o78oZ4M3pRpI=; b=EeWBZrwy8STvPczAoD/V2W+GRY+gaJJrO4ITb5VXD1lCQjxoFfUMFNef 70rAKrx9kGzJM72kPzgVoYXSpAnswXslyKNSHHb/1wMzgCU4iEE26ujVf CGuiUQeePsps42SW2afXX8+xK/8rJTrRnosC4ragTbEWTuftu2VjEz4zz 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BuAgBWOuZa/5FdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJNdmEXYyiYZ4FTIYEPkxSBeAsjhEkCgk4hNhYBAgEBAQE?= =?us-ascii?q?BAQJsHAyFKAEBAQECAS1RCwsRAwEBAQEnB0YJCAYBDAYCAQGEfgUID6ZHEYM?= =?us-ascii?q?8H4NaAV6DZYJCBYgWgVQ/gQ8jDIJcgSiBaQKCABaFHgKIHI92CIVkiGEGgTW?= =?us-ascii?q?GGSKEZ4k8hwCBJSMHKiaBLE0jFYJ+CYVzihwBUSMwkQUBAQ?=
X-IronPort-AV: E=Sophos;i="5.49,344,1520899200";  d="scan'208,217";a="106835998"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Apr 2018 21:38:13 +0000
Received: from [10.118.10.23] (rtp-fandreas-2-8816.cisco.com [10.118.10.23]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w3TLcCsx018828; Sun, 29 Apr 2018 21:38:12 GMT
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com>
Date: Sun, 29 Apr 2018 17:38:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se>
Content-Type: multipart/alternative; boundary="------------423E853FF63D1D5DC5833CBE"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0WjLAki0RuZUBtPyVOoKzMZaTCM>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 29 Apr 2018 21:38:18 -0000

This is a multi-part message in MIME format.
--------------423E853FF63D1D5DC5833CBE
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit



On 4/29/18 4:38 PM, Christer Holmberg wrote:
>
> Hi,
>
> I have now gone through the whole BUNDLE document, and modified the 
> parts that I think need to be modified.
>
> I would encourage anyone who is interested in BUNDLE to take a look at 
> the pull request (or download the XML and generate a text document), 
> because there have been quite a bit of changes. The good part is that 
> most of the O/A procedures in the document have been simplified.
>
> I’d also like to chairs to give some guidance on how to move forward. 
> Do we need yet another WGLC? Etc.
>
We need input from the WG in general on this, and in particular from 
Ekr, since he is the one that has been asking for a change here. Once we 
understand whether
a) this proposal addresses the concers and
b) the WG participants in general are in favor of it

then we can decide how to proceed.

Thanks

-- Flemming (as MMUSIC co-chair)


> Regards,
>
> Christer
>
> *From:*mmusic [mailto:mmusic-bounces@ietf.org] *On Behalf Of *Christer 
> Holmberg
> *Sent:* 27 April 2018 20:22
> *To:* mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell 
> <ben@nostrum.com>; Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
> *Subject:* Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= 
> section
>
> New commit with updated ICE Considerations.
>
> Regards,
>
> Christer
>
> *From:*Christer Holmberg
> *Sent:* 27 April 2018 15:30
> *To:* Christer Holmberg <christer.holmberg@ericsson.com 
> <mailto:christer.holmberg@ericsson.com>>; mmusic@ietf.org 
> <mailto:mmusic@ietf.org>; mmusic-chairs@ietf.org 
> <mailto:mmusic-chairs@ietf.org>; Ben Campbell <ben@nostrum.com 
> <mailto:ben@nostrum.com>>; Eric Rescorla (ekr@rtfm.com 
> <mailto:ekr@rtfm.com>) <ekr@rtfm.com <mailto:ekr@rtfm.com>>
> *Subject:* Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= 
> section
>
> Hi,
>
> I have added more changes to the pull request. Basically, the whole 
> SDP Offer/Answer section has now been modified.
>
> I would like people to take a look at the changes. In case it’s 
> difficult to read the text in GitHub, you can download the XML and 
> generate a text version (I have verified that xml2rfc works).
>
> Regards,
>
> Christer
>
> *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: *Thursday 26 April 2018 at 21:15
> *To: *"mmusic@ietf.org <mailto:mmusic@ietf.org>" <mmusic@ietf.org 
> <mailto:mmusic@ietf.org>>, "mmusic-chairs@ietf.org 
> <mailto:mmusic-chairs@ietf.org>" <mmusic-chairs@ietf.org 
> <mailto:mmusic-chairs@ietf.org>>, Ben Campbell <ben@nostrum.com 
> <mailto:ben@nostrum.com>>, Eric Rescorla <ekr@rtfm.com 
> <mailto:ekr@rtfm.com>>
> *Subject: *[MMUSIC] BUNDLE: Pull request to introduce tagged m= section
>
> Hi,
>
> I have put together a pull request, where I start to suggest how to 
> introduce the tagged m= section concept into BUNDLE, and to include 
> more text on how SDP attributes are included in BUNDLE groups.
>
> https://github.com/cdh4u/draft-sdp-bundle/pull/59
>
> Note that there is still work to do, and even the changes I have 
> already done probably need some fine tuning and spell correction.
>
> At this point I would like to know whether people (in particular Ekr – 
> but also others) are ok with the approach in general.
>
> Regards,
>
> Christer
>


--------------423E853FF63D1D5DC5833CBE
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 4/29/18 4:38 PM, Christer Holmberg
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D">Hi,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">I have now gone
            through the whole BUNDLE document, and modified the parts
            that I think need to be modified.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">I would
            encourage anyone who is interested in BUNDLE to take a look
            at the pull request (or download the XML and generate a text
            document), because there have been quite a bit of changes.
            The good part is that most of the O/A procedures in the
            document have been simplified.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">I’d also like
            to chairs to give some guidance on how to move forward. Do
            we need yet another WGLC? Etc.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
      </div>
    </blockquote>
    We need input from the WG in general on this, and in particular from
    Ekr, since he is the one that has been asking for a change here.
    Once we understand whether<br>
    a) this proposal addresses the concers and <br>
    b) the WG participants in general are in favor of it<br>
    <br>
    then we can decide how to proceed. <br>
    <br>
    Thanks <br>
    <br>
    -- Flemming (as MMUSIC co-chair)<br>
    <br>
    <br>
    <blockquote type="cite"
cite="mid:7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se">
      <div class="WordSection1">
        <p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Christer<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><a name="_MailEndCompose"
            moz-do-not-send="true"><span style="color:#1F497D"><o:p> </o:p></span></a></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span
                  style="mso-fareast-language:EN-GB" lang="EN-US">From:</span></b><span
                style="mso-fareast-language:EN-GB" lang="EN-US"> mmusic
                [<a class="moz-txt-link-freetext" href="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</a>]
                <b>On Behalf Of </b>Christer Holmberg<br>
                <b>Sent:</b> 27 April 2018 20:22<br>
                <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>; Ben
                Campbell <a class="moz-txt-link-rfc2396E" href="mailto:ben@nostrum.com">&lt;ben@nostrum.com&gt;</a>; Eric Rescorla
                (<a class="moz-txt-link-abbreviated" href="mailto:ekr@rtfm.com">ekr@rtfm.com</a>) <a class="moz-txt-link-rfc2396E" href="mailto:ekr@rtfm.com">&lt;ekr@rtfm.com&gt;</a><br>
                <b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to
                introduce tagged m= section<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal"><span style="color:#1F497D">New commit with
            updated ICE Considerations.<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D">Christer<o:p></o:p></span></p>
        <p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0cm 0cm 0cm">
            <p class="MsoNormal"><b><span
                  style="mso-fareast-language:EN-GB" lang="EN-US">From:</span></b><span
                style="mso-fareast-language:EN-GB" lang="EN-US">
                Christer Holmberg
                <br>
                <b>Sent:</b> 27 April 2018 15:30<br>
                <b>To:</b> Christer Holmberg &lt;<a
                  href="mailto:christer.holmberg@ericsson.com"
                  moz-do-not-send="true">christer.holmberg@ericsson.com</a>&gt;;
                <a href="mailto:mmusic@ietf.org" moz-do-not-send="true">mmusic@ietf.org</a>;
                <a href="mailto:mmusic-chairs@ietf.org"
                  moz-do-not-send="true">
                  mmusic-chairs@ietf.org</a>; Ben Campbell &lt;<a
                  href="mailto:ben@nostrum.com" moz-do-not-send="true">ben@nostrum.com</a>&gt;;
                Eric Rescorla (<a href="mailto:ekr@rtfm.com"
                  moz-do-not-send="true">ekr@rtfm.com</a>) &lt;<a
                  href="mailto:ekr@rtfm.com" moz-do-not-send="true">ekr@rtfm.com</a>&gt;<br>
                <b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to
                introduce tagged m= section<o:p></o:p></span></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black">Hi,</span><span
              style="font-size:10.5pt;color:black;mso-fareast-language:EN-GB"><o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black">I have added more
              changes to the pull request. Basically, the whole SDP
              Offer/Answer section has now been modified.<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black">I would like people
              to take a look at the changes. In case it’s difficult to
              read the text in GitHub, you can download the XML and
              generate a text version (I have verified that xml2rfc
              works).<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black">Regards,<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black">Christer<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
        </div>
        <div style="border:none;border-top:solid #B5C4DF
          1.0pt;padding:3.0pt 0cm 0cm 0cm">
          <p class="MsoNormal"><b><span style="color:black">From: </span></b><span
              style="color:black">mmusic &lt;<a
                href="mailto:mmusic-bounces@ietf.org"
                moz-do-not-send="true">mmusic-bounces@ietf.org</a>&gt;
              on behalf of Christer Holmberg &lt;<a
                href="mailto:christer.holmberg@ericsson.com"
                moz-do-not-send="true">christer.holmberg@ericsson.com</a>&gt;<br>
              <b>Date: </b>Thursday 26 April 2018 at 21:15<br>
              <b>To: </b>"<a href="mailto:mmusic@ietf.org"
                moz-do-not-send="true">mmusic@ietf.org</a>" &lt;<a
                href="mailto:mmusic@ietf.org" moz-do-not-send="true">mmusic@ietf.org</a>&gt;,
              "<a href="mailto:mmusic-chairs@ietf.org"
                moz-do-not-send="true">mmusic-chairs@ietf.org</a>" &lt;<a
                href="mailto:mmusic-chairs@ietf.org"
                moz-do-not-send="true">mmusic-chairs@ietf.org</a>&gt;,
              Ben Campbell &lt;<a href="mailto:ben@nostrum.com"
                moz-do-not-send="true">ben@nostrum.com</a>&gt;, Eric
              Rescorla &lt;<a href="mailto:ekr@rtfm.com"
                moz-do-not-send="true">ekr@rtfm.com</a>&gt;<br>
              <b>Subject: </b>[MMUSIC] BUNDLE: Pull request to
              introduce tagged m= section<o:p></o:p></span></p>
        </div>
        <div>
          <p class="MsoNormal"><span
              style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
        </div>
        <div>
          <div>
            <p class="MsoNormal"><span style="color:black">Hi,<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black">I have put
                together a pull request, where I start to suggest how to
                introduce the tagged m= section concept into BUNDLE, and
                to include more text on how SDP attributes are included
                in BUNDLE groups.<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"><a
                  href="https://github.com/cdh4u/draft-sdp-bundle/pull/59"
                  moz-do-not-send="true">https://github.com/cdh4u/draft-sdp-bundle/pull/59</a><o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black">Note that
                there is still work to do, and even the changes I have
                already done probably need some fine tuning and spell
                correction.<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black">At this point
                I would like to know whether people (in particular Ekr –
                but also others) are ok with the approach in general.<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black">Regards,<o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
            <p class="MsoNormal"><span style="color:black">Christer<o:p></o:p></span></p>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------423E853FF63D1D5DC5833CBE--


From nobody Sun Apr 29 14:52:24 2018
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 33BAD12D7EF for <mmusic@ietfa.amsl.com>; Sun, 29 Apr 2018 14:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 R4pC78I0yNZJ for <mmusic@ietfa.amsl.com>; Sun, 29 Apr 2018 14:52:18 -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 85A8B127522 for <mmusic@ietf.org>; Sun, 29 Apr 2018 14:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=678; q=dns/txt; s=iport; t=1525038738; x=1526248338; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=cxZMpRhpzrmO4XxkjhdNB06iEgx3IW70bizX1f8XWtQ=; b=Vw8yr1hwBgMXtzDDxH3NXi3WoH5GtrpVmUJRqfQMskBvqXr+wzhmIXRm Sd8hSSVUrzcQkB5/0kdDfJooGX0mDvmXefKM3xSShiyvn3rvm+VOZSB8n gaXWGo5jPhgiL216G6JwZ+Km6La/LRF6np1Rdj/abC6mIA30WJkDWfOwW c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BrAgAWPuZa/40NJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDgVuEFJR7gXSBD5UMC4RsAoJOITgUAQIBAQEBAQECbCi?= =?us-ascii?q?FKQEFIw8BBVELGAICJgICVwYBDAgBAYR+DagGghyEWINlgkeBCYcNgVQ/gTK?= =?us-ascii?q?CaIdzglQCmBIIjkUGgSeGJ4UJkDyBJTMhgVJNIxWCf5BpI5E1AQE?=
X-IronPort-AV: E=Sophos;i="5.49,344,1520899200"; d="scan'208";a="107191114"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Apr 2018 21:52:02 +0000
Received: from [10.118.10.23] (rtp-fandreas-2-8816.cisco.com [10.118.10.23]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w3TLq29Y012996; Sun, 29 Apr 2018 21:52:02 GMT
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <D7051253.2EB7A%christer.holmberg@ericsson.com> <a2541e9a-121a-fc4c-a54d-5ec3737867d4@cisco.com> <7594FB04B1934943A5C02806D1A2204B72E9FB97@ESESSMB109.ericsson.se>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <476b864f-4f43-1a53-94f1-29a9bb610ac9@cisco.com>
Date: Sun, 29 Apr 2018 17:52:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72E9FB97@ESESSMB109.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UBoYTOueF0CfWX8aBKcCHD_jEpE>
Subject: Re: [MMUSIC] draft-ice-sip-sdp: Comments on section 4.4
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 29 Apr 2018 21:52:22 -0000

On 4/26/18 1:37 PM, Christer Holmberg wrote:
> Hi,
>
>>> Section 4.4 says:
>>>
>>>      "When present in both, the value in the
>>>       media-level takes precedence.  Thus, the value at the session-level
>>>       is effectively a default that applies to all data streams, unless
>>>       overridden by a media-level value.²
>>>
>>>
>>> This is basic offer/answer, so I suggest to remove the text.
>> Is that actually called out in RFC 3264 ?
> It may be in RFC 4566. It's basic SDP.
>
> We can keep it if you want, but we don't normally say this in other drafts.
I'd prefer to keep it.

Thanks

-- Flemming
>
> Regards,
>
> Christer
>
> .
>


From nobody Mon Apr 30 02:57:57 2018
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 589F7127136 for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 02:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-jU1Oh7OHKs for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 02:57:54 -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 7BAB912426E for <mmusic@ietf.org>; Mon, 30 Apr 2018 02:57:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1525082271; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=AR0AjP2cVMrUW1LnsCsrGQEThfz256vh6iufstNvZWQ=; b=bbgPNYJefzw23IvxQBxG3i02ynLCB1ABVI4E648rKuBFLvt0+vymkSgihoqgKjtj t13zMRrdBiUXwmHa3XAIBzfRHxLsuVJsEw67gjoFGWT/nCwgPDt2ss3KrQacrho7 CZlnhNTd4KYoSqx6rhaS230Hg8z0/8pcC+PSFlbwIXA=;
X-AuditID: c1b4fb30-0f7ff70000007681-2b-5ae6e89ff234
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 05.C9.30337.F98E6EA5; Mon, 30 Apr 2018 11:57:51 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0382.000; Mon, 30 Apr 2018 11:57:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Ben Campbell" <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/KQU7OCAgANKT1CAAPFYgA==
Date: Mon, 30 Apr 2018 09:57:51 +0000
Message-ID: <D70CC3AC.2F08F%christer.holmberg@ericsson.com>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: multipart/alternative; boundary="_000_D70CC3AC2F08Fchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAIsWRmVeSWpSXmKPExsUyM2K7me78F8+iDM42KljM7zzNbrHi9Tl2 i/M71zNZTF3+mMWBxWPJkp9MHrN2PmHxmPy4jTmAOYrLJiU1J7MstUjfLoEr48v2F0wFy5oZ K36uyWtgXFLSxcjJISFgIrH7wSLGLkYuDiGBI4wS007cZodwFjNKtGzoZ+1i5OBgE7CQ6P6n DRIXEXjMKLFp0zRGkG5hAU+JaW8XsoHYIgJeEqcWTmeBsJ0kdiyawgxiswioSkxYeZEJxOYV sJb4tWQJK8SCw4wSi3f/BCviFPCTWHP4F1gzo4CYxPdTa8AamAXEJW49mc8EcaqAxJI955kh bFGJl4//sYLYogJ6EhvAruYAiitJ3N7gBNGaILF9w3lGiL2CEidnPmGZwCgyC8nUWUjKZiEp g4gbSLw/N58ZwtaWWLbwNZStL7Hxy1lGCNta4sCFi2zIahYwcqxiFC1OLU7KTTcy0kstykwu Ls7P08tLLdnECIzHg1t+G+xgfPnc8RCjAAejEg/vl/vPooRYE8uKK3MPMUpwMCuJ8K7sAArx piRWVqUW5ccXleakFh9ilOZgURLntfDbHCUkkJ5YkpqdmlqQWgSTZeLglGpgXNaRxs27LfzI kcc2y5hFaz//k1xoXvqjpcpX9nXD0+qH7nwFl/N+Zwq+W1bxQfQky4L7bFE5d3kdLc9/VCos 5T2msv+FOMecTr2PK7PXe1x5b/FM956HTMq2+svxPQZSO76LZOts8PSzdpIwlheftHW7gWWj LCfn3SVrZyiwG/f6Ss798tBaiaU4I9FQi7moOBEAMSYmNcMCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/puBUh_V4bUz1MoftrPTPVMBaEMU>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 09:57:56 -0000

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

Hi,

Ekr also had a comment on the Introduction section, that it is confusing to=
 read.

I have tried to re-structure, and add some sub sections, in order to make i=
t more clear. The changes can be seen in the same pull request.

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: Sunday 29 April 2018 at 23:38
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmus=
ic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>, Ben Campbell <ben@nostr=
um.com<mailto:ben@nostrum.com>>, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtf=
m.com>>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have now gone through the whole BUNDLE document, and modified the parts t=
hat I think need to be modified.

I would encourage anyone who is interested in BUNDLE to take a look at the =
pull request (or download the XML and generate a text document), because th=
ere have been quite a bit of changes. The good part is that most of the O/A=
 procedures in the document have been simplified.

I=92d also like to chairs to give some guidance on how to move forward. Do =
we need yet another WGLC? Etc.

Regards,

Christer



From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 27 April 2018 20:22
To: mmusic@ietf.org<mailto:mmusic@ietf.org>; mmusic-chairs@ietf.org<mailto:=
mmusic-chairs@ietf.org>; Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.c=
om>>; Eric Rescorla (ekr@rtfm.com<mailto:ekr@rtfm.com>) <ekr@rtfm.com<mailt=
o:ekr@rtfm.com>>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

New commit with updated ICE Considerations.

Regards,

Christer

From: Christer Holmberg
Sent: 27 April 2018 15:30
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>; mmusic@ietf.org<mailto:mmusic@ietf.org>; mmusic-chairs@=
ietf.org<mailto:mmusic-chairs@ietf.org>; Ben Campbell <ben@nostrum.com<mail=
to:ben@nostrum.com>>; Eric Rescorla (ekr@rtfm.com<mailto:ekr@rtfm.com>) <ek=
r@rtfm.com<mailto:ekr@rtfm.com>>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have added more changes to the pull request. Basically, the whole SDP Off=
er/Answer section has now been modified.

I would like people to take a look at the changes. In case it=92s difficult=
 to read the text in GitHub, you can download the XML and generate a text v=
ersion (I have verified that xml2rfc works).

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: Thursday 26 April 2018 at 21:15
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmus=
ic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>, Ben Campbell <ben@nostr=
um.com<mailto:ben@nostrum.com>>, Eric Rescorla <ekr@rtfm.com<mailto:ekr@rtf=
m.com>>
Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section

Hi,

I have put together a pull request, where I start to suggest how to introdu=
ce the tagged m=3D section concept into BUNDLE, and to include more text on=
 how SDP attributes are included in BUNDLE groups.

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

Note that there is still work to do, and even the changes I have already do=
ne probably need some fine tuning and spell correction.

At this point I would like to know whether people (in particular Ekr =96 bu=
t also others) are ok with the approach in general.

Regards,

Christer

--_000_D70CC3AC2F08Fchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A617F9D58E95244B8BD9CDB038501B49@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>Ekr also had a comment on the Introduction section, that it is confusi=
ng to read.</div>
<div><br>
</div>
<div>I have tried to re-structure, and add some sub sections, in order to m=
ake it more clear. The changes can be seen in the same pull request.</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>Sunday 29 April 2018 at 23:38=
<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;, &quot;<a href=3D"mailto:mmusic-chairs@ietf.org">mm=
usic-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic-chairs@ietf.org=
">mmusic-chairs@ietf.org</a>&gt;,
 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt=
;, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<b=
r>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] BUNDLE: Pull =
request to introduce tagged m=3D section<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:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
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: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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I have now gone throug=
h the whole BUNDLE document, and modified the parts that I think need to be=
 modified.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I would encourage anyo=
ne who is interested in BUNDLE to take a look at the pull request (or downl=
oad the XML and generate a text document), because there have been quite a =
bit of changes. The good part is that
 most of the O/A procedures in the document have been simplified.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I=92d also like to cha=
irs to give some guidance on how to move forward. Do we need yet another WG=
LC? Etc.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></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" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org">mailto:mmusic-b=
ounces@ietf.org</a>]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> 27 April 2018 20:22<br>
<b>To:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a href=
=3D"mailto:mmusic-chairs@ietf.org">
mmusic-chairs@ietf.org</a>; Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.=
com">ben@nostrum.com</a>&gt;; Eric Rescorla (<a href=3D"mailto:ekr@rtfm.com=
">ekr@rtfm.com</a>) &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt=
;<br>
<b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">New commit with update=
d ICE Considerations.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></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" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Christer Holmberg
<br>
<b>Sent:</b> 27 April 2018 15:30<br>
<b>To:</b> Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericss=
on.com">christer.holmberg@ericsson.com</a>&gt;;
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a href=3D"mailto:m=
music-chairs@ietf.org">
mmusic-chairs@ietf.org</a>; Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.=
com">ben@nostrum.com</a>&gt;; Eric Rescorla (<a href=3D"mailto:ekr@rtfm.com=
">ekr@rtfm.com</a>) &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt=
;<br>
<b>Subject:</b> Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section<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;color:black">Hi,</sp=
an><span style=3D"font-size:10.5pt;color:black;mso-fareast-language:EN-GB">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I have =
added more changes to the pull request. Basically, the whole SDP Offer/Answ=
er section has now been modified.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">I would=
 like people to take a look at the changes. In case it=92s difficult to rea=
d the text in GitHub, you can download the XML and generate a text version =
(I have verified that xml2rfc works).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Regards=
,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black">Christe=
r<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></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"color:black">From: </span></b><spa=
n style=3D"color:black">mmusic &lt;<a href=3D"mailto:mmusic-bounces@ietf.or=
g">mmusic-bounces@ietf.org</a>&gt; on behalf of Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt;<br>
<b>Date: </b>Thursday 26 April 2018 at 21:15<br>
<b>To: </b>&quot;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&quo=
t; &lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;, &quot;<a=
 href=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&quot; &l=
t;<a href=3D"mailto:mmusic-chairs@ietf.org">mmusic-chairs@ietf.org</a>&gt;,
 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt=
;, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<b=
r>
<b>Subject: </b>[MMUSIC] BUNDLE: Pull request to introduce tagged m=3D sect=
ion<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:black"><o:p>&n=
bsp;</o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">I have put together a pu=
ll request, where I start to suggest how to introduce the tagged m=3D secti=
on concept into BUNDLE, and to include more text on how SDP attributes are =
included in BUNDLE groups.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black"><a href=3D"https://githu=
b.com/cdh4u/draft-sdp-bundle/pull/59">https://github.com/cdh4u/draft-sdp-bu=
ndle/pull/59</a><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Note that there is still=
 work to do, and even the changes I have already done probably need some fi=
ne tuning and spell correction.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">At this point I would li=
ke to know whether people (in particular Ekr =96 but also others) are ok wi=
th the approach in general.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Regards,<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:black">&nbsp;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Christer<o:p></o:p></spa=
n></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D70CC3AC2F08Fchristerholmbergericssoncom_--


From nobody Mon Apr 30 03:21:31 2018
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 83EA5124205 for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 03:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rByY9aIKeMIH for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 03:21: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 8EA2C1200F1 for <mmusic@ietf.org>; Mon, 30 Apr 2018 03:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1525083685; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=/qCyzCVGeAj7U89kNEv0xoK3h/4uoKFYJ7+BSwkojJ8=; b=DG1Q9fdbKq1gkUs8qkR6CmDkU6xvEUb9H8lgzXPvtFs+SmPnjpNLaZl2EWT3/kt4 yj7I5pghNBOMYYhtWTr8pXXLmAYgWq4fEMkU+SeEakdBtCi8FMM8+TIas5XFZbrP mvbWifHeC7Ifq20YVIfl2VmlhtkJIZvLMTlnzrrYrZY=;
X-AuditID: c1b4fb30-0dfff70000007681-06-5ae6ee25b0b5
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id BC.EE.30337.52EE6EA5; Mon, 30 Apr 2018 12:21:25 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0382.000; Mon, 30 Apr 2018 12:21:25 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "Roni Even (A)" <roni.even@huawei.com>, Bo Burman <bo.burman@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
Thread-Index: AdPMES0/R3+uRXojQVG2VsIr3NCqRwBqS4VgArb2H4AAY4GJgAGUYCiA
Date: Mon, 30 Apr 2018 10:21:25 +0000
Message-ID: <D70CC7AE.2F097%christer.holmberg@ericsson.com>
References: <6E58094ECC8D8344914996DAD28F1CCD870EA5@DGGEMM506-MBX.china.huawei.com> <DB5PR07MB107811003A4497F734FA69BD8DBA0@DB5PR07MB1078.eurprd07.prod.outlook.com> <D6FF8C39.2E810%christer.holmberg@ericsson.com> <6E58094ECC8D8344914996DAD28F1CCD87537A@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD87537A@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.7.170905
x-originating-ip: [131.160.50.130]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <FB8185037691DA49B40E2EF2B68BBBD2@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAIsWRmVeSWpSXmKPExsUyM2K7rq7qu2dRBkdvWlpMXf6YxeLTsfMs DkweLUfesnosWfKTKYApissmJTUnsyy1SN8ugSvj+lWvghVSFdOnrGdsYLwg2cXIySEhYCIx a3kLK4gtJHCEUWLNXUkIezGjxIbp5V2MHBxsAhYS3f+0QcIiAqUSU7/eZQOxhQUCJK4smMEO EQ+U2PjnJDNIuYiAm8SOK/EgYRYBVYmjdy4wgdi8AtYSDQueA7VyAU1fxCTx5N1JsDmcAiES n+9vZgGxGQXEJL6fWgPWwCwgLnHryXwmiDMFJJbsOc8MYYtKvHz8D+xkUQE9iQ0nbrOD7JUQ UJK4vcEJolVL4suPfWwQtrXEtqk7GCFsRYkp3Q/ZIe4RlDg58wnLBEaxWUi2zULSPgtJ+ywk 7bOQtC9gZF3FKFqcWpyUm25kpJdalJlcXJyfp5eXWrKJERhPB7f8NtjB+PK54yFGAQ5GJR7e L/efRQmxJpYVV+YeYpTgYFYS4V3ZARTiTUmsrEotyo8vKs1JLT7EKM3BoiTOa+G3OUpIID2x JDU7NbUgtQgmy8TBKdXAuKY+/NXOcs3zRYb/7R7H+ArvOb46nnX29WMuHW+T3iWyTZ/ewXHE uzzY88zSppOmS97eeq/evVqH73GxeLeVT/ut/8rPzfY8ORma4Cn6MHSGSPU+R6u1jpO5n57d +bX/D3ON9uwXMjybu1/c5Kr8FJlypP6k4ZOcWb/5dt39VDkpwH0Fi7f+VSWW4oxEQy3mouJE ACtMgT6jAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/jNvd73lrbPsQPMktJ8L4BA-_nvQ>
Subject: Re: [MMUSIC] new revision in draft-ietf-mmusic-data-channel-sdpneg-17
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 10:21:30 -0000

SGksDQoNCi4uLg0KDQo+U0VDVElPTiA2Ljc6DQo+PT09PT09PT09PT09DQo+DQo+UTEyOg0KPg0K
PkkgdGhpbmsgbW9zdCBvZiB0aGUgdGV4dCAoYXBhcnQgZnJvbSB0aGUgZXJyb3IgY2FzZXMpIGNv
dWxkIGJlDQo+aW5jb3Jwb3JhdGVkIGludG8gdGhlIGVhcmxpZXIgb2ZmZXIvYW5zd2VyIHNlY3Rp
b25zLg0KPg0KPkZvciBleGFtcGxlLCB0aGUgb2ZmZXIgc2VjdGlvbiBzaG91bGQgbWFrZSBpdCBj
bGVhciB3aGVuICJhPWRjbWFwOiIgaXMNCj5pbmNsdWRlZCBpbiBhbiBvZmZlciwgYW5kIHdoZW4g
aXQgaXMgbm90LiBUaGVyZSBpcyBubyBuZWVkIGZvciBhIHNlcGFyYXRlDQo+c2VjdGlvbiB0byBk
ZXNjcmliZSB0aGUgY2FzZSB3aGVuICJTRFAgb2ZmZXIgaGFzIG5vICJhPWRjbWFwOqn3DQo+YXR0
cmlidXRlcyIuDQo+DQo+W1JFfSBJIGFtIG5vdCBzdXJlLCBJIGNhbiBtb3ZlIHRoZSBjYXNlcyBs
aWtlIGZvciBleGFtcGxlICBubyBhPWRjbWFwIGluDQo+aW50aWFsIG9mZmVyIHRvIHNlY3Rpb24g
Ni4zIGJ1dCBJIHRoaW5rIHRoZXNlIGNhc2VzIGFyZSBub3QgdGhlIHVzdWFsDQo+b25lcyBzaW5j
ZSA2LjMgY3JlYXRlcyB0aGUgIm5vcm1hbCIgb2ZmZXIgYW5kIGl0IHJlYWRzIGJldHRlciBhdCBs
ZWFzdCB0bw0KPm1lIHRoaXMgd2F5LiBBbnlob3cgaWYgeW91IGZlZWwgdGhpcyBpcyBpbXBvcnRh
bnQgSSB3aWxsIG1vdmUgcGFydHMgb2YNCj5zZWN0aW9uIDYuNyB0byBlYXJsaWVyIHNlY3Rpb25z
DQoNCg0KVG8gdGFrZSBkZWNhbXAgYXMgYW4gZXhhbXBsZSwgdGhlIHRleHQgaW4gc2VjdGlvbiA2
Ljcgc2F5czoNCg0KICAgIkluaXRpYWwgU0RQIG9mZmVyOiBObyBkYXRhIGNoYW5uZWwgaXMgbmVn
b3RpYXRlZCB5ZXQuICBUaGUgRFRMUw0KICAgIGFzc29jaWF0aW9uIGFuZCBTQ1RQIGFzc29jaWF0
aW9uIGlzIG5lZ290aWF0ZWQgYW5kLCBpZiBhZ3JlZWQsDQogICAgZXN0YWJsaXNoZWQgYXMgcGVy
IFtJLUQuaWV0Zi1tbXVzaWMtc2N0cC1zZHBdLqGxDQoNCg0KVGhlIGluaXRpYWwgb2ZmZXIgaXMg
dGhlIGZpcnN0IG9mZmVyIHdoZXJlIHlvdSBuZWdvdGlhdGUgdGhlIGRhdGEgY2hhbm5lbA0KLSB3
aGF0ZXZlciBvZmZlci9hbnN3ZXJzIHlvdSBoYXZlIGRvbmUgYmVmb3JlIHRoYXQgaXMgaXJyZWxl
dmFudC4gQXMgd2UgZG8NCmluIG90aGVyIGRyYWZ0cywgeW91IGNvdWxkIGNsYXJpZnkgdGhhdCBp
biB0aGUgZHJhZnQuDQoNCk5vdywgaWYgeW91IHdhbnQsIHlvdSBjYW4gY2xhcmlmeSBpbiBzZWN0
aW9uIDYuMyB0aGF0IHRoZSBEVExTL1NDVFANCmFzc29jaWF0aW9uIG1heSBoYXZlIGJlZW4gcHJl
dmlvdXNseSBuZWdvdGlhdGVkLg0KDQpUaGVuIHRoZSB0ZXh0IHNheXM6DQoNCiAgICJTdWJzZXF1
ZW50IFNEUCBvZmZlcjogQWxsIHRoZSBTRFAgb2ZmZXIvYW5zd2VyIG5lZ290aWF0ZWQgZGF0YQ0K
ICAgIGNoYW5uZWxzIGFyZSBleHBlY3RlZCB0byBiZSBjbG9zZWQgbm93LiAgVGhlIERUTFMvU0NU
UA0KICAgIGFzc29jaWF0aW9uIHJlbWFpbnMgb3BlbiBmb3IgU0RQIG9mZmVyL2Fuc3dlciBvciBE
Q0VQDQogICAgbmVnb3RpYXRpb24gb2YgZGF0YSBjaGFubmVscy6hsQ0KDQoNClRoaXMgc2hvdWxk
IGJlIGluIHNlY3Rpb24gNi42LCBpbiBteSBvcGluaW9uLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rl
cg0KDQoNCg0KDQo+RnJvbTogIG1tdXNpYyA8bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJl
aGFsZiBvZiBCbyBCdXJtYW4NCj48Ym8uYnVybWFuQGVyaWNzc29uLmNvbT4NCj5EYXRlOiAgRnJp
ZGF5IDYgQXByaWwgMjAxOCBhdCAxODoxNw0KPlRvOiAgIlJvbmkgRXZlbiAoQSkiIDxyb25pLmV2
ZW5AaHVhd2VpLmNvbT4sICJtbXVzaWNAaWV0Zi5vcmciDQo+PG1tdXNpY0BpZXRmLm9yZz4NCj5T
dWJqZWN0OiAgUmU6IFtNTVVTSUNdIG5ldyByZXZpc2lvbiBpbg0KPmRyYWZ0LWlldGYtbW11c2lj
LWRhdGEtY2hhbm5lbC1zZHBuZWctMTcNCj4NCj4NCj5UaGFua3MgUm9uaSwNCj4gDQo+SSBiZWxp
ZXZlIHRoaXMgYWRkcmVzc2VzIG15IHNoZXBoZXJkqfZzIHJldmlldyBuaXRzLg0KPiANCj4vQm8N
Cj4gDQo+RnJvbTogbW11c2ljIFttYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJl
aGFsZiBPZiBSb25pIEV2ZW4gKEEpDQo+U2VudDogZGVuIDQgYXByaWwgMjAxOCAxNDozNA0KPlRv
OiBtbXVzaWNAaWV0Zi5vcmcNCj5TdWJqZWN0OiBbTU1VU0lDXSBuZXcgcmV2aXNpb24gaW4gZHJh
ZnQtaWV0Zi1tbXVzaWMtZGF0YS1jaGFubmVsLXNkcG5lZy0xNw0KPg0KPg0KPiANCj5IaSwNCj5J
IHN1Ym1pdHRlZCBhIG5ldyByZXZpc2lvbiBvZg0KPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1pZXRmLW1tdXNpYy1kYXRhLWNoYW5uZWwtc2RwbmVnLTE3DQo+dHJ5aW5nIHRvIGFk
ZHJlc3MgY29tbWVudHMgZnJvbSBDaHJpc3RlciBhbmQgQm8uDQo+VGhhbmtzDQo+Um9uaSBFdmVu
DQo+DQoNCg==


From nobody Mon Apr 30 05:10:02 2018
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 6C68612778D for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 05:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mshiEinYQql0 for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 05:09:59 -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 B3253127AD4 for <mmusic@ietf.org>; Mon, 30 Apr 2018 05:09:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1525090196; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=5cQfvWxcJN/UuKRnx0OVTMMppLaw/t1+l4wa6RtUCS0=; b=HbKreuJQ7hT4eHAyy/JhC0lUt83pfvEwoytsh1MvwC/Ltng8sjFN5SXpT6QrGxSY yPT4pZvApoN539q7n88EEMOoeQtpsLoOBqFgR+kzVr6cQ21tC8y2BX1GgMkTH52D do5iV4jcT2oiRvzuHnNKqxmvMuUgikscX6vpFi07Oms=;
X-AuditID: c1b4fb3a-112a09c00000729c-eb-5ae70794c5e3
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 7B.4C.29340.49707EA5; Mon, 30 Apr 2018 14:09:56 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0382.000; Mon, 30 Apr 2018 14:08:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Flemming Andreasen <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Ben Campbell" <ben@nostrum.com>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/KQU7OCAgANKT1D//++xAIABE3rw
Date: Mon, 30 Apr 2018 12:08:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72EA6FF8@ESESSMB109.ericsson.se>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se> <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com>
In-Reply-To: <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.162]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZGbFdV3cK+/Mogzlr+Szmd55mt1jx+hy7 xfsLuhbnd65nspi6/DGLA6vHlN8bWT2WLPnJ5DFr5xMWj8mP25gDWKK4bFJSczLLUov07RK4 Mq4e8ymYLV2xdEorewPjX9EuRk4OCQETifXTTzN2MXJxCAkcYZT4tKODDcJZzCjRvPUJUIaD g03AQqL7nzZIXETgBqPErs9LmEG6hQU8Jd69ecwGYosIeEmcWjidBaReRMBNYuNxGZAwi4Cq xKnL+1hAbF4BX4m5T6ZBzf/GKLHpayNYL6eArUTHtCNMIDajgJjE91NrwGxmAXGJW0/mM0Fc KiCxZM95ZghbVOLl43+sELaSxNP/S6Dq9SRuTJ3CBmFrSyxb+JoZYrGgxMmZT1gmMIrMQjJ2 FpKWWUhaZiFpWcDIsopRtDi1uDg33chIL7UoM7m4OD9PLy+1ZBMjMH4ObvlttYPx4HPHQ4wC HIxKPLz7vj2LEmJNLCuuzD3EKMHBrCTCu7IDKMSbklhZlVqUH19UmpNafIhRmoNFSZzXKc0i SkggPbEkNTs1tSC1CCbLxMEp1cAYf2rV4ierD5+/cXvRnYcfvq3edrT/4DEJJpuDNooLf249 MsH6EIu+zsygmKSAwm9Wtm1HPJ87Xe6LedpqVvTN/WV8Z2/7gVeLvSofhLou4N6ln8X3LO/7 ut1BfTFZe17HzpQoXHTiQanzcb792g3/IyTVAkq/XTvU8HM58z7R/WvkZphLLeOUUGIpzkg0 1GIuKk4EAJb275ubAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/BUay4_SMo6wPYyot1KHucZbrtx0>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 12:10:00 -0000

Hi Flemming,
=A0
>> I have now gone through the whole BUNDLE document, and modified the=20
>> parts that I think need to be modified.=20
>>=A0
>> I would encourage anyone who is interested in BUNDLE to take a look at t=
he pull=20
>> request (or download the XML and generate a text document), because ther=
e have=20
>> been quite a bit of changes. The good part is that most of the O/A proce=
dures in the=20
>> document have been simplified.
>
> I'd also like to chairs to give some guidance on how to move forward. Do =
we need yet another WGLC? Etc.
>
> We need input from the WG in general on this, and in particular from Ekr,=
 since he is the one that has=20
> been asking for a change here. Once we understand whether
> a) this proposal addresses the concers and=20
> b) the WG participants in general are in favor of it
>
> then we can decide how to proceed.=20

I agree. I guess my questions are:

1) Do we assume that people will be able to comment based on the pull reque=
st (or, that people will download the XML and create a text version)? Or, d=
o we need to submit a new "official" version of the draft? That needs to be=
 clear, if e.g., someone is waiting for a new version to be submitted befor=
e giving comments.

2) What is the timeline for giving comments? I don't want to end up in a si=
tuation where nothing happens for weeks/months.

Regards,

Christer

=A0
=A0
=A0
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 27 April 2018 20:22
To: mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>=
; Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section
=A0
New commit with updated ICE Considerations.
=A0
Regards,
=A0
Christer
=A0
From: Christer Holmberg=20
Sent: 27 April 2018 15:30
To: Christer Holmberg <christer.holmberg@ericsson.com>; mmusic@ietf.org; mm=
usic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>; Eric Rescorla (ekr@rt=
fm.com) <ekr@rtfm.com>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section
=A0
Hi,
=A0
I have added more changes to the pull request. Basically, the whole SDP Off=
er/Answer section has now been modified.
=A0
I would like people to take a look at the changes. In case it's difficult t=
o read the text in GitHub, you can download the XML and generate a text ver=
sion (I have verified that xml2rfc works).
=A0
Regards,
=A0
Christer
=A0
From: mmusic <mmusic-bounces@ietf.org> on behalf of Christer Holmberg <chri=
ster.holmberg@ericsson.com>
Date: Thursday 26 April 2018 at 21:15
To: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-c=
hairs@ietf.org>, Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.co=
m>
Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D section
=A0
Hi,
=A0
I have put together a pull request, where I start to suggest how to introdu=
ce the tagged m=3D section concept into BUNDLE, and to include more text on=
 how SDP attributes are included in BUNDLE groups.
=A0
https://github.com/cdh4u/draft-sdp-bundle/pull/59
=A0
Note that there is still work to do, and even the changes I have already do=
ne probably need some fine tuning and spell correction.
=A0
At this point I would like to know whether people (in particular Ekr - but =
also others) are ok with the approach in general.
=A0
Regards,
=A0
Christer


From nobody Mon Apr 30 07:32:25 2018
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 381DE12895E; Mon, 30 Apr 2018 07:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hkzNzWcuYA2f; Mon, 30 Apr 2018 07:32:20 -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 B5BA7124D37; Mon, 30 Apr 2018 07:32:20 -0700 (PDT)
Received: from [10.0.1.86] (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 w3UEWCA2089243 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 30 Apr 2018 09:32:12 -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.86]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C0C18474-21E8-4A5F-9913-F9667277F159"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Date: Mon, 30 Apr 2018 09:32:10 -0500
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B72EA6FF8@ESESSMB109.ericsson.se>
Cc: Flemming Andreasen <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se> <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com> <7594FB04B1934943A5C02806D1A2204B72EA6FF8@ESESSMB109.ericsson.se>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/d_JU-06meRSEX1iXDTj9NIXCb4Q>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 14:32:24 -0000

--Apple-Mail=_C0C18474-21E8-4A5F-9913-F9667277F159
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Apr 30, 2018, at 7:08 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Flemming,
>=20
>>> I have now gone through the whole BUNDLE document, and modified the
>>> parts that I think need to be modified.
>>>=20
>>> I would encourage anyone who is interested in BUNDLE to take a look =
at the pull
>>> request (or download the XML and generate a text document), because =
there have
>>> been quite a bit of changes. The good part is that most of the O/A =
procedures in the
>>> document have been simplified.
>>=20
>> I'd also like to chairs to give some guidance on how to move forward. =
Do we need yet another WGLC? Etc.
>>=20
>> We need input from the WG in general on this, and in particular from =
Ekr, since he is the one that has
>> been asking for a change here. Once we understand whether
>> a) this proposal addresses the concers and
>> b) the WG participants in general are in favor of it
>>=20
>> then we can decide how to proceed.
>=20
> I agree. I guess my questions are:
>=20
> 1) Do we assume that people will be able to comment based on the pull =
request (or, that people will download the XML and create a text =
version)? Or, do we need to submit a new "official" version of the =
draft? That needs to be clear, if e.g., someone is waiting for a new =
version to be submitted before giving comments.
>=20
> 2) What is the timeline for giving comments? I don't want to end up in =
a situation where nothing happens for weeks/months.

My preference is a new version, followed by a potentially abbreviated =
WGLC for just the changes. (I take Flemming=E2=80=99s comments to mean =
he thinks a WGLC.)

Ben.

>=20
> Regards,
>=20
> Christer
>=20
>=20
>=20
>=20
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer =
Holmberg
> Sent: 27 April 2018 20:22
> To: mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell =
<ben@nostrum.com>; Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
> Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section
>=20
> New commit with updated ICE Considerations.
>=20
> Regards,
>=20
> Christer
>=20
> From: Christer Holmberg
> Sent: 27 April 2018 15:30
> To: Christer Holmberg <christer.holmberg@ericsson.com>; =
mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>; =
Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
> Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section
>=20
> Hi,
>=20
> I have added more changes to the pull request. Basically, the whole =
SDP Offer/Answer section has now been modified.
>=20
> I would like people to take a look at the changes. In case it's =
difficult to read the text in GitHub, you can download the XML and =
generate a text version (I have verified that xml2rfc works).
>=20
> Regards,
>=20
> Christer
>=20
> From: mmusic <mmusic-bounces@ietf.org> on behalf of Christer Holmberg =
<christer.holmberg@ericsson.com>
> Date: Thursday 26 April 2018 at 21:15
> To: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" =
<mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, Eric Rescorla =
<ekr@rtfm.com>
> Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m=3D =
section
>=20
> Hi,
>=20
> I have put together a pull request, where I start to suggest how to =
introduce the tagged m=3D section concept into BUNDLE, and to include =
more text on how SDP attributes are included in BUNDLE groups.
>=20
> https://github.com/cdh4u/draft-sdp-bundle/pull/59
>=20
> Note that there is still work to do, and even the changes I have =
already done probably need some fine tuning and spell correction.
>=20
> At this point I would like to know whether people (in particular Ekr - =
but also others) are ok with the approach in general.
>=20
> Regards,
>=20
> Christer
>=20


--Apple-Mail=_C0C18474-21E8-4A5F-9913-F9667277F159
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlrnKOoACgkQgFZKbJXz
1A07sRAAscS5tk40VKcRjOaQX9ic5BVlwR4MRD2tKCzZZezV1oPkuqGMIpyqgSWt
lN8ePWNx/IfyHtDNj+TKgJNg7ipMmNlIJEel/S8ARcfqL80q0F71b791zuh94CkO
1pHNshft/RXo5vKUwAd6Q14yk6VLU5zk3vy7/xUfi8r/TPLUNEiRDCDkbWFYJmer
f3y8w6BTrX4Q80qIKhq/88SAdeO27moosdzmXPxQRkgqsIznW8aChwut5IUNTdSQ
AoJ1BLMxpN0cb0e/+s06X+7GhYfI2tp55AJ4C8wbiUN/MNglYhrc14H1q1uKCx6q
mouWoTK0UHRk74VhhITvB4OVXxsBxHXAit8Kk3X+6e+WTb7qA/KeCg2k9/q7lEKs
6+08kutJGEPjCfsDon6GOhL8wUfpI8OglsK/rF27RePZcM3AF+kBgM7fKQ7QinS/
dt1S6akDwDjxnr/rIJKcy7XSxw8SLy6Bvdon1gaCxljIb9C641e5kjBBDodQOfsV
z8qXfS9XQfSNy/BW2x8vuFbQm9Na//Bv3wNGn6k799CvPT44tAS6ooJlaG4EFdnO
WVfU4aPmogzflSQAyR5mns/r1vXVUKgFkzUfI6WJIgCnAMHV3yTRCBYYePVtJYvd
NeSyQcwl3+d0JijYtEjnX7x2pqiQIN2zboLp16maco8QE6Vn3hE=
=5QpB
-----END PGP SIGNATURE-----

--Apple-Mail=_C0C18474-21E8-4A5F-9913-F9667277F159--


From nobody Mon Apr 30 08:15:43 2018
Return-Path: <paul.kyzivat@comcast.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 7AAE712DA6F for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 08:15:35 -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=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7L9Q2BjQe4_h for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 08:15:34 -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 17971126C25 for <mmusic@ietf.org>; Mon, 30 Apr 2018 08:15:34 -0700 (PDT)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-06v.sys.comcast.net with ESMTP id D9vBfA5ZezQTiDAWbfdout; Mon, 30 Apr 2018 15:15:33 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1525101333; bh=BeMckYro1rO/N0rOGRXNOwll6GjJPi/nHzLzX0avDtQ=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=f7Mdp+2hDJ+M6uG67PejJglJpif0FNFdLT1nvXgjM01wY5UxxY1jNJZb34EB+Bg08 cDZtWjJ8aaiFQCjhKA0/6c3LMU9Lgpgq6b8D/jWLlgpJvdzgUhWFB9QD8dR7tt0EQX bMIhFpstDYevJhUBHzr6ddP7yKImSyMcUAgP/UR+GYbfLKp1hkTrBPwpneBl7yo29N PzY7ceECqyoU+k7KByiz2P3tF/G5GxCc0ZQNkLl0rcegIltyxuyF7mPFIbRLiSttt6 aKnUAn7YAcUYecMMbGHxv148bKo4vUZSgPfRtjZRE1zsSv8EXgfAGZi5i266Vtfaqf lJnh+E6rVVIfg==
Received: from PaulKyzivatsMBP.localdomain ([24.62.227.142]) by resomta-ch2-02v.sys.comcast.net with ESMTPA id DAWafEGBHZD7iDAWbflNZ4; Mon, 30 Apr 2018 15:15:33 +0000
To: mmusic@ietf.org
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se> <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com> <7594FB04B1934943A5C02806D1A2204B72EA6FF8@ESESSMB109.ericsson.se> <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
Message-ID: <c4b2d2b9-34e7-99f5-3666-c567d5d1beba@comcast.net>
Date: Mon, 30 Apr 2018 11:15:32 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfEzzmAHVbGH4tKvA/O7uUx7WqcWiQkAgkBE1x/SVAoqn0UkI2eX9t4l7p4flIGbotXdY3r2Q3cdWrcHB+DHJEEu7+g6WuyvqTDnd9NC6klIw70kx/x/g uvVMn6nnwnjz8qHZOj3R8wOPO/kX5t8sM8icNehmZ5lugUlI2l3M+jyIAoq2Z4R/GztDp/7e0bCaBw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RlKSZyzWjc6f6P5a9uH1aAhjVMs>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 15:15:38 -0000

On 4/30/18 10:32 AM, Ben Campbell wrote:

> My preference is a new version, followed by a potentially abbreviated WGLC for just the changes. (I take Flemming’s comments to mean he thinks a WGLC.)

+1


From nobody Mon Apr 30 08:26:55 2018
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 8E08B120724 for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 08:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7xVMW0vqkEB7 for <mmusic@ietfa.amsl.com>; Mon, 30 Apr 2018 08:26: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 02D01120713 for <mmusic@ietf.org>; Mon, 30 Apr 2018 08:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1525102008; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=fWYKBgzPZLE/QAHX0O7NNRtiW3bocVetBhND5chL9JQ=; b=Mlk+6JJbJkYz/LuIoC5S6KLCusIdsHRJwzV5gVPomU3wK8L/D/ZQD3ybSzNA+jFD +aFp/6PX8uKpeQAmXjvAP3nBpCVpCLriHSweW8qIWZAjNkXooa3oAeDoefUPej0p sK/A3sxlOhTzah/y/GCFjNtn23OvHtEJy21hM96xgb8=;
X-AuditID: c1b4fb2d-ac3ff700000055bf-4d-5ae735b747c6
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id A6.05.21951.7B537EA5; Mon, 30 Apr 2018 17:26:48 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.34]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0382.000; Mon, 30 Apr 2018 17:23:53 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: Flemming Andreasen <fandreas@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
Thread-Topic: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
Thread-Index: AQHT3ivRj0ufAPQsL0q5amAAmWGE/KQU7OCAgANKT1D//++xAIABE3rwgAAH0gCAAC47UA==
Date: Mon, 30 Apr 2018 15:23:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B72EA7685@ESESSMB109.ericsson.se>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se> <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com> <7594FB04B1934943A5C02806D1A2204B72EA6FF8@ESESSMB109.ericsson.se> <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
In-Reply-To: <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.166]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM2K7ve4O0+dRBm0rWCzmd55mt1jx+hy7 xfsLuhbnd65nspi6/DGLA6vHlN8bWT2WLPnJ5DFr5xMWj8mP25gDWKK4bFJSczLLUov07RK4 Mv4/OctWsEa74uLGhAbGOVpdjJwcEgImEj/ufWbsYuTiEBI4wiixfckHNghnMaNEx8JprF2M HBxsAhYS3f+0QRpEBJQknjdvZQGpYRbYxihxc+kTNpCEsICnxLs3j9kgirwkTi2czgLSKyIQ JrF6kS9ImEVAVeLV5Q1gJbwCvhLHv59ghdj1nkni76QnrCAJTgF7iU0nJ4PZjAJiEt9PrWEC sZkFxCVuPZnPBHG1gMSSPeeZIWxRiZeP/7FC2EoSR09fAruZWUBTYv0ufYhWRYkp3Q/ZIfYK Spyc+YRlAqPoLCRTZyF0zELSMQtJxwJGllWMosWpxcW56UbGeqlFmcnFxfl5enmpJZsYgTF1 cMtv3R2Mq187HmIU4GBU4uH10XgeJcSaWFZcmXuIUYKDWUmEd2XHsygh3pTEyqrUovz4otKc 1OJDjNIcLErivHqr9kQJCaQnlqRmp6YWpBbBZJk4OKUaGCMk/nItlpzpYtC0R8A3fU5tTtWs 4t/VSS2M33bv5VskfHlxRH3qpK1XNgvFNpeciVsr2j/54x/1qKccBvWtrN9zb85PfXEg4R7H 1/n832x6fS6Z/XqeFBsi3V/03WOV5LLjIU9K30ueFvt8X/BGctDWvPANRq+r+a7OLvu+L2mK lOGcTROv2SmxFGckGmoxFxUnAgDVGvC8pQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/N4kFgc2HbM8pijW08K4A4HX2bjQ>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 15:26:53 -0000

SGksDQogDQo+Pj4+IEkgaGF2ZSBub3cgZ29uZSB0aHJvdWdoIHRoZSB3aG9sZSBCVU5ETEUgZG9j
dW1lbnQsIGFuZCBtb2RpZmllZCB0aGUgDQo+Pj4+IHBhcnRzIHRoYXQgSSB0aGluayBuZWVkIHRv
IGJlIG1vZGlmaWVkLg0KPj4+PiANCj4+Pj4gSSB3b3VsZCBlbmNvdXJhZ2UgYW55b25lIHdobyBp
cyBpbnRlcmVzdGVkIGluIEJVTkRMRSB0byB0YWtlIGEgbG9vayANCj4+Pj4gYXQgdGhlIHB1bGwg
cmVxdWVzdCAob3IgZG93bmxvYWQgdGhlIFhNTCBhbmQgZ2VuZXJhdGUgYSB0ZXh0IA0KPj4+PiBk
b2N1bWVudCksIGJlY2F1c2UgdGhlcmUgaGF2ZSBiZWVuIHF1aXRlIGEgYml0IG9mIGNoYW5nZXMu
IFRoZSBnb29kIA0KPj4+PiBwYXJ0IGlzIHRoYXQgbW9zdCBvZiB0aGUgTy9BIHByb2NlZHVyZXMg
aW4gdGhlIGRvY3VtZW50IGhhdmUgYmVlbiBzaW1wbGlmaWVkLg0KPj4+IA0KPj4+IEknZCBhbHNv
IGxpa2UgdG8gY2hhaXJzIHRvIGdpdmUgc29tZSBndWlkYW5jZSBvbiBob3cgdG8gbW92ZSBmb3J3
YXJkLiBEbyB3ZSBuZWVkIHlldCBhbm90aGVyIFdHTEM/IEV0Yy4NCj4+PiANCj4+PiBXZSBuZWVk
IGlucHV0IGZyb20gdGhlIFdHIGluIGdlbmVyYWwgb24gdGhpcywgYW5kIGluIHBhcnRpY3VsYXIg
ZnJvbSANCj4+PiBFa3IsIHNpbmNlIGhlIGlzIHRoZSBvbmUgdGhhdCBoYXMgYmVlbiBhc2tpbmcg
Zm9yIGEgY2hhbmdlIGhlcmUuIE9uY2UgDQo+Pj4gd2UgdW5kZXJzdGFuZCB3aGV0aGVyDQo+Pj4g
YSkgdGhpcyBwcm9wb3NhbCBhZGRyZXNzZXMgdGhlIGNvbmNlcnMgYW5kDQo+Pj4gYikgdGhlIFdH
IHBhcnRpY2lwYW50cyBpbiBnZW5lcmFsIGFyZSBpbiBmYXZvciBvZiBpdA0KPj4+IA0KPj4+IHRo
ZW4gd2UgY2FuIGRlY2lkZSBob3cgdG8gcHJvY2VlZC4NCj4+IA0KPj4gSSBhZ3JlZS4gSSBndWVz
cyBteSBxdWVzdGlvbnMgYXJlOg0KPj4gDQo+PiAxKSBEbyB3ZSBhc3N1bWUgdGhhdCBwZW9wbGUg
d2lsbCBiZSBhYmxlIHRvIGNvbW1lbnQgYmFzZWQgb24gdGhlIHB1bGwgcmVxdWVzdCAob3IsIHRo
YXQgDQo+PiBwZW9wbGUgd2lsbCBkb3dubG9hZCB0aGUgWE1MIGFuZCBjcmVhdGUgYSB0ZXh0IHZl
cnNpb24pPyBPciwgZG8gd2UgbmVlZCB0byBzdWJtaXQgYSBuZXcgDQo+PiAib2ZmaWNpYWwiIHZl
cnNpb24gb2YgdGhlIGRyYWZ0PyBUaGF0IG5lZWRzIHRvIGJlIGNsZWFyLCBpZiBlLmcuLCBzb21l
b25lIGlzIHdhaXRpbmcgZm9yIGEgbmV3IA0KPj4gdmVyc2lvbiB0byBiZSBzdWJtaXR0ZWQgYmVm
b3JlIGdpdmluZyBjb21tZW50cy4NCj4+IA0KPj4gMikgV2hhdCBpcyB0aGUgdGltZWxpbmUgZm9y
IGdpdmluZyBjb21tZW50cz8gSSBkb24ndCB3YW50IHRvIGVuZCB1cCBpbiBhIHNpdHVhdGlvbiB3
aGVyZQ0KPj4gbm90aGluZyBoYXBwZW5zIGZvciB3ZWVrcy9tb250aHMuDQo+DQo+IE15IHByZWZl
cmVuY2UgaXMgYSBuZXcgdmVyc2lvbiwgZm9sbG93ZWQgYnkgYSBwb3RlbnRpYWxseSBhYmJyZXZp
YXRlZCBXR0xDIGZvciBqdXN0IHRoZSBjaGFuZ2VzLiAoSSB0YWtlIEZsZW1taW5n4oCZcyBjb21t
ZW50cyB0byBtZWFuIGhlIHRoaW5rcyBhIFdHTEMuKQ0KDQpPay4NCg0KSG93ZXZlciwgYmVmb3Jl
IEkgc3VibWl0IGEgbmV3IHZlcnNpb24gSSdkIGxpa2UgRWtyIHRvIHRha2UgYSBsb29rIGF0IHRo
ZSBwdWxsIHJlcXVlc3QsIGFuZCBpbmRpY2F0ZSB3aGV0aGVyIGl0IGF0IGxlYXN0IGxvb2tzIGxp
a2Ugd2hhdCBoZSBoYXMgYmVlbiBhc2tpbmcgZm9yLg0KDQpBZ2FpbiwgdGhlIG1ham9yaXR5IG9m
IHRoZSBjaGFuZ2VzIGFyZSByZWxhdGVkIHRvIHRoZSBpbnRyb2R1Y3Rpb24gb2YgdGhlICJ0YWdn
ZWQgbT0gc2VjdGlvbiIgY29uY2VwdCwgYnV0IGUuZy4sIHRoZSBjaGFuZ2UgdG8gdGhlIEludHJv
ZHVjdGlvbiBzZWN0aW9uIGlzIG1vc3RseSBpbiBvcmRlciB0byByZS1zdHJ1Y3R1cmUgYW5kIGNs
YXJpZnkuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg0KIA0KDQoNCg0KPiBGcm9tOiBtbXVz
aWMgW21haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIENocmlzdGVy
IA0KPiBIb2xtYmVyZw0KPiBTZW50OiAyNyBBcHJpbCAyMDE4IDIwOjIyDQo+IFRvOiBtbXVzaWNA
aWV0Zi5vcmc7IG1tdXNpYy1jaGFpcnNAaWV0Zi5vcmc7IEJlbiBDYW1wYmVsbCANCj4gPGJlbkBu
b3N0cnVtLmNvbT47IEVyaWMgUmVzY29ybGEgKGVrckBydGZtLmNvbSkgPGVrckBydGZtLmNvbT4N
Cj4gU3ViamVjdDogUmU6IFtNTVVTSUNdIEJVTkRMRTogUHVsbCByZXF1ZXN0IHRvIGludHJvZHVj
ZSB0YWdnZWQgbT0gDQo+IHNlY3Rpb24NCj4gDQo+IE5ldyBjb21taXQgd2l0aCB1cGRhdGVkIElD
RSBDb25zaWRlcmF0aW9ucy4NCj4gDQo+IFJlZ2FyZHMsDQo+IA0KPiBDaHJpc3Rlcg0KPiANCj4g
RnJvbTogQ2hyaXN0ZXIgSG9sbWJlcmcNCj4gU2VudDogMjcgQXByaWwgMjAxOCAxNTozMA0KPiBU
bzogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT47IA0K
PiBtbXVzaWNAaWV0Zi5vcmc7IG1tdXNpYy1jaGFpcnNAaWV0Zi5vcmc7IEJlbiBDYW1wYmVsbCAN
Cj4gPGJlbkBub3N0cnVtLmNvbT47IEVyaWMgUmVzY29ybGEgKGVrckBydGZtLmNvbSkgPGVrckBy
dGZtLmNvbT4NCj4gU3ViamVjdDogUmU6IFtNTVVTSUNdIEJVTkRMRTogUHVsbCByZXF1ZXN0IHRv
IGludHJvZHVjZSB0YWdnZWQgbT0gDQo+IHNlY3Rpb24NCj4gDQo+IEhpLA0KPiANCj4gSSBoYXZl
IGFkZGVkIG1vcmUgY2hhbmdlcyB0byB0aGUgcHVsbCByZXF1ZXN0LiBCYXNpY2FsbHksIHRoZSB3
aG9sZSBTRFAgT2ZmZXIvQW5zd2VyIHNlY3Rpb24gaGFzIG5vdyBiZWVuIG1vZGlmaWVkLg0KPiAN
Cj4gSSB3b3VsZCBsaWtlIHBlb3BsZSB0byB0YWtlIGEgbG9vayBhdCB0aGUgY2hhbmdlcy4gSW4g
Y2FzZSBpdCdzIGRpZmZpY3VsdCB0byByZWFkIHRoZSB0ZXh0IGluIEdpdEh1YiwgeW91IGNhbiBk
b3dubG9hZCB0aGUgWE1MIGFuZCBnZW5lcmF0ZSBhIHRleHQgdmVyc2lvbiAoSSBoYXZlIHZlcmlm
aWVkIHRoYXQgeG1sMnJmYyB3b3JrcykuDQo+IA0KPiBSZWdhcmRzLA0KPiANCj4gQ2hyaXN0ZXIN
Cj4gDQo+IEZyb206IG1tdXNpYyA8bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBv
ZiBDaHJpc3RlciBIb2xtYmVyZyANCj4gPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4N
Cj4gRGF0ZTogVGh1cnNkYXkgMjYgQXByaWwgMjAxOCBhdCAyMToxNQ0KPiBUbzogIm1tdXNpY0Bp
ZXRmLm9yZyIgPG1tdXNpY0BpZXRmLm9yZz4sICJtbXVzaWMtY2hhaXJzQGlldGYub3JnIiANCj4g
PG1tdXNpYy1jaGFpcnNAaWV0Zi5vcmc+LCBCZW4gQ2FtcGJlbGwgPGJlbkBub3N0cnVtLmNvbT4s
IEVyaWMgDQo+IFJlc2NvcmxhIDxla3JAcnRmbS5jb20+DQo+IFN1YmplY3Q6IFtNTVVTSUNdIEJV
TkRMRTogUHVsbCByZXF1ZXN0IHRvIGludHJvZHVjZSB0YWdnZWQgbT0gc2VjdGlvbg0KPiANCj4g
SGksDQo+IA0KPiBJIGhhdmUgcHV0IHRvZ2V0aGVyIGEgcHVsbCByZXF1ZXN0LCB3aGVyZSBJIHN0
YXJ0IHRvIHN1Z2dlc3QgaG93IHRvIGludHJvZHVjZSB0aGUgdGFnZ2VkIG09IHNlY3Rpb24gY29u
Y2VwdCBpbnRvIEJVTkRMRSwgYW5kIHRvIGluY2x1ZGUgbW9yZSB0ZXh0IG9uIGhvdyBTRFAgYXR0
cmlidXRlcyBhcmUgaW5jbHVkZWQgaW4gQlVORExFIGdyb3Vwcy4NCj4gDQo+IGh0dHBzOi8vZ2l0
aHViLmNvbS9jZGg0dS9kcmFmdC1zZHAtYnVuZGxlL3B1bGwvNTkNCj4gDQo+IE5vdGUgdGhhdCB0
aGVyZSBpcyBzdGlsbCB3b3JrIHRvIGRvLCBhbmQgZXZlbiB0aGUgY2hhbmdlcyBJIGhhdmUgYWxy
ZWFkeSBkb25lIHByb2JhYmx5IG5lZWQgc29tZSBmaW5lIHR1bmluZyBhbmQgc3BlbGwgY29ycmVj
dGlvbi4NCj4gDQo+IEF0IHRoaXMgcG9pbnQgSSB3b3VsZCBsaWtlIHRvIGtub3cgd2hldGhlciBw
ZW9wbGUgKGluIHBhcnRpY3VsYXIgRWtyIC0gYnV0IGFsc28gb3RoZXJzKSBhcmUgb2sgd2l0aCB0
aGUgYXBwcm9hY2ggaW4gZ2VuZXJhbC4NCj4gDQo+IFJlZ2FyZHMsDQo+IA0KPiBDaHJpc3Rlcg0K
PiANCg0K


From nobody Mon Apr 30 13:10:25 2018
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 589A012D86E; Mon, 30 Apr 2018 13:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 FJCxB0zUBjp4; Mon, 30 Apr 2018 13:10:22 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE8A9127775; Mon, 30 Apr 2018 13:10:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3828; q=dns/txt; s=iport; t=1525119021; x=1526328621; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=TDmZ45i3TOOfhtrUw2yqfFr2sEQIMm0+yC5xlMB5TA4=; b=JZKB9JcvMQPnV1bPoGm3vt2oaBTe8nvGHzE8ef0r4vRnozxhz3Bgak8H TPa4nHN0WSUfiSOBw7WEwX0dHsQjePKGFvQjNU1LOw4Xpu6qvO6xxGHMi YrSKVg0I6sQg5LprkC9j386O8dqcVd9grdu2Z1pkdwlT6Piejpi1oVMLn c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DmAgDDduda/5BdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNDYXoog2yUfYFLCCGBD5UMCyOESQKCcyE4FAECAQEBAQE?= =?us-ascii?q?BAmwcDIUoAQEBAQMjDwEFQRALEQMBAQEBAgIjAwICRgkIBgEMBgIBAYR+DQ+?= =?us-ascii?q?mMhGBIIIchFiDa4JCBYEJhw2BVD+BDyMMglyBKIFpAoRgglQCmBIIhWSIYQa?= =?us-ascii?q?BNYYZIoRniTyHAIElMyGBUk0jFYJ+hXyKbiMwj2cBAQ?=
X-IronPort-AV: E=Sophos;i="5.49,348,1520899200"; d="scan'208";a="170759738"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Apr 2018 20:10:20 +0000
Received: from [10.118.10.23] (rtp-fandreas-2-8816.cisco.com [10.118.10.23]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w3UKAKEp021735; Mon, 30 Apr 2018 20:10:20 GMT
To: Ben Campbell <ben@nostrum.com>, Christer Holmberg <christer.holmberg@ericsson.com>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "Eric Rescorla (ekr@rtfm.com)" <ekr@rtfm.com>
References: <D70900B4.2EFCA%christer.holmberg@ericsson.com> <7594FB04B1934943A5C02806D1A2204B72EA21EB@ESESSMB109.ericsson.se> <7594FB04B1934943A5C02806D1A2204B72EA527A@ESESSMB109.ericsson.se> <5684a1f3-2cd7-1708-33a8-ef8a35b6b4af@cisco.com> <7594FB04B1934943A5C02806D1A2204B72EA6FF8@ESESSMB109.ericsson.se> <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <7a61721f-bf06-6396-ed6b-62b3e04dcaa4@cisco.com>
Date: Mon, 30 Apr 2018 16:10:20 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <EA4EBAAF-A996-4E5E-BEB6-870F362F8F62@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/d_eQzGOOg5copyqRYG9X3cPHXZM>
Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@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, 30 Apr 2018 20:10:24 -0000

On 4/30/18 10:32 AM, Ben Campbell wrote:
>
>> On Apr 30, 2018, at 7:08 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>>
>> Hi Flemming,
>>
>>>> I have now gone through the whole BUNDLE document, and modified the
>>>> parts that I think need to be modified.
>>>>
>>>> I would encourage anyone who is interested in BUNDLE to take a look at the pull
>>>> request (or download the XML and generate a text document), because there have
>>>> been quite a bit of changes. The good part is that most of the O/A procedures in the
>>>> document have been simplified.
>>> I'd also like to chairs to give some guidance on how to move forward. Do we need yet another WGLC? Etc.
>>>
>>> We need input from the WG in general on this, and in particular from Ekr, since he is the one that has
>>> been asking for a change here. Once we understand whether
>>> a) this proposal addresses the concers and
>>> b) the WG participants in general are in favor of it
>>>
>>> then we can decide how to proceed.
>> I agree. I guess my questions are:
>>
>> 1) Do we assume that people will be able to comment based on the pull request (or, that people will download the XML and create a text version)? Or, do we need to submit a new "official" version of the draft? That needs to be clear, if e.g., someone is waiting for a new version to be submitted before giving comments.
>>
>> 2) What is the timeline for giving comments? I don't want to end up in a situation where nothing happens for weeks/months.
> My preference is a new version, followed by a potentially abbreviated WGLC for just the changes. (I take Flemming’s comments to mean he thinks a WGLC.)
Most likely.

-- Flemming
>
> Ben.
>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg
>> Sent: 27 April 2018 20:22
>> To: mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>; Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
>> Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
>>
>> New commit with updated ICE Considerations.
>>
>> Regards,
>>
>> Christer
>>
>> From: Christer Holmberg
>> Sent: 27 April 2018 15:30
>> To: Christer Holmberg <christer.holmberg@ericsson.com>; mmusic@ietf.org; mmusic-chairs@ietf.org; Ben Campbell <ben@nostrum.com>; Eric Rescorla (ekr@rtfm.com) <ekr@rtfm.com>
>> Subject: Re: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
>>
>> Hi,
>>
>> I have added more changes to the pull request. Basically, the whole SDP Offer/Answer section has now been modified.
>>
>> I would like people to take a look at the changes. In case it's difficult to read the text in GitHub, you can download the XML and generate a text version (I have verified that xml2rfc works).
>>
>> Regards,
>>
>> Christer
>>
>> From: mmusic <mmusic-bounces@ietf.org> on behalf of Christer Holmberg <christer.holmberg@ericsson.com>
>> Date: Thursday 26 April 2018 at 21:15
>> To: "mmusic@ietf.org" <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
>> Subject: [MMUSIC] BUNDLE: Pull request to introduce tagged m= section
>>
>> Hi,
>>
>> I have put together a pull request, where I start to suggest how to introduce the tagged m= section concept into BUNDLE, and to include more text on how SDP attributes are included in BUNDLE groups.
>>
>> https://github.com/cdh4u/draft-sdp-bundle/pull/59
>>
>> Note that there is still work to do, and even the changes I have already done probably need some fine tuning and spell correction.
>>
>> At this point I would like to know whether people (in particular Ekr - but also others) are ok with the approach in general.
>>
>> Regards,
>>
>> Christer
>>

