
From nobody Thu Jan  4 05:08:26 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 45473126D45 for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 05:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzkqXXcokkSS for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 05:08:22 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EACF112711A for <mmusic@ietf.org>; Thu,  4 Jan 2018 05:08:21 -0800 (PST)
X-AuditID: c1b4fb25-473ff7000000341b-79-5a4e27445d11
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 85.A0.13339.4472E4A5; Thu,  4 Jan 2018 14:08:20 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0352.000; Thu, 4 Jan 2018 14:08:16 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
CC: Ben Campbell <ben@nostrum.com>, Eric Rescorla <ekr@rtfm.com>
Thread-Topic: BUNDLE: media-level c= lines in bundle-only m= sections?
Thread-Index: AQHThV0VqJ9MZItYF0GkVCGZHqpE4g==
Date: Thu, 4 Jan 2018 13:08:16 +0000
Message-ID: <D673F64D.284F7%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: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D673F64D284F7christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsUyM2J7uK6Lul+UwaoNghbzO0+zW6x4fY7d YuryxywOzB5Llvxk8pi18wmLx+THbcwBzFFcNimpOZllqUX6dglcGfOuPWAv2CZbsf3nA7YG xl0SXYycHBICJhJ7f/5l6WLk4hASOMwosXFqH5SzmFHi8pdH7F2MHBxsAhYS3f+0QRpEBNQl vu7tYQaxmQUcJI49v8AMUiIs4Cgx7boOiCki4CZxdVU0RLWexMXvC9hBbBYBFYnzh86C2bwC 1hKfZ1xnBLEZBcQkvp9awwQxUVzi1pP5TBCnCUgs2XOeGcIWlXj5+B8riC0KNHPDidtgh0kI KEos75cDMZkFEiR291ZCTBeUODnzCcsERuFZSIbOQqiahaQKosRA4v25+cwQtrbEsoWvoWx9 iY1fzjJC2NYS7/eeZkVWs4CRYxWjaHFqcVJuupGxXmpRZnJxcX6eXl5qySZGYIQd3PJbdQfj 5TeOhxgFOBiVeHg7pf2ihFgTy4orcw8xSnAwK4nw+rz2jRLiTUmsrEotyo8vKs1JLT7EKM3B oiTOe9KTN0pIID2xJDU7NbUgtQgmy8TBKdXA2M3Wftz6usWbLuO9aWt+xj4p0V/ZOnF+/a/I u5yZhemcrQbb2tUeMsxNmcu08ANvxy/+yN70fQ+frL69ti3FTi1BX4p37cSJdUk7L72cIRep IhrurL30rLkVA5exlNnMNzsWrjxmuvrfiqMO1058VlO4uOrOiVa7J5EBj9/dbD8v1bHQ+eaC eCWW4oxEQy3mouJEAO7i/ZasAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wH0V64REpb2n_YBhgAhSD_6iJ5M>
Subject: [MMUSIC] BUNDLE: media-level c= lines in bundle-only m= sections?
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, 04 Jan 2018 13:08:24 -0000

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

Hi,

BUNDLE doesn=92t say much about c=3D lines, the assumption being that there=
 are no BUNDLE-specific rules related to c=3D lines: one can use a session-=
level c=3D line, or media-level c=3D lines, also with BUNDLE. The BUNDLE ad=
dress will use whatever IP address is associated (implicitly or explicitly)=
 with the tagged m=3D section.

So far so good.

Now, Ekr raised a JSEP GitHub issue regarding media-level c=3D lines in bun=
dle-only m=3D sections. As we know, BUNDLE currently specifies that a zero =
port value is assigned to bundle-only m=3D sections, but nothing is said ab=
out media-level c=3D lines.

https://github.com/rtcweb-wg/jsep/issues/843

(The GitHub issue was initially created because of another issue, but if yo=
u follow the discussion it will end up in this)

My suggestion would be that an offerer/answerer MUST NOT assign media-level=
 c=3D lines to bundle-only m=3D sections.

Would people be ok with this? Does someone suggest something else?

Whatever the outcome, I think it would be good to clarify it in BUNDLE. I d=
on't think we need to bring the document back to the WG in order to do that=
 =96 if we can agree on the text I will implement it in a future update (e.=
g., based on the IESG reviews) of the draft.

Regards,

Christer




--_000_D673F64D284F7christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <E83D6FAA239B6E4BA5AE1439FB4DBD63@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>BUNDLE doesn=92t say much about c=3D lines, the assumption being that =
there are no BUNDLE-specific rules related to c=3D lines: one can use a ses=
sion-level c=3D line, or media-level c=3D lines, also with BUNDLE. The BUND=
LE address will use whatever IP address is
 associated (implicitly or explicitly) with the tagged m=3D section.</div>
<div><br>
</div>
<div>So far so good.</div>
<div><br>
</div>
<div>Now, Ekr raised a JSEP GitHub issue regarding media-level c=3D lines i=
n bundle-only m=3D sections. As we know, BUNDLE currently specifies that a =
zero port value is assigned to bundle-only m=3D sections, but nothing is sa=
id about media-level c=3D lines.</div>
<div><br>
</div>
<div><a href=3D"https://github.com/rtcweb-wg/jsep/issues/843">https://githu=
b.com/rtcweb-wg/jsep/issues/843</a></div>
<div><br>
</div>
<div>(The GitHub issue was initially created because of another issue, but =
if you follow the discussion it will end up in this)</div>
<div><br>
</div>
<div>My suggestion would be that an offerer/answerer MUST NOT assign media-=
level c=3D lines to bundle-only m=3D sections.</div>
<div><br>
</div>
<div>Would people be ok with this? Does someone suggest something else?</di=
v>
<div><br>
</div>
<div>Whatever the outcome, I think it would be good to clarify it in BUNDLE=
. I don't think we need to bring the document back to the WG in order to do=
 that =96 if we can agree on the text I will implement it in a future updat=
e (e.g., based on the IESG reviews)
 of the draft.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div>&nbsp;</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_D673F64D284F7christerholmbergericssoncom_--


From nobody Thu Jan  4 07:32:42 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 0F890126BFD for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 07:32:41 -0800 (PST)
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 9S9MHy_fSXw4 for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 07:32:39 -0800 (PST)
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 12EB91267BB for <mmusic@ietf.org>; Thu,  4 Jan 2018 07:32:38 -0800 (PST)
X-AuditID: 12074413-d0dff70000000aec-74-5a4e491528f6
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 56.1A.02796.5194E4A5; Thu,  4 Jan 2018 10:32:37 -0500 (EST)
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 w04FWZ9g028250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Thu, 4 Jan 2018 10:32:37 -0500
To: mmusic@ietf.org
References: <D673F64D.284F7%christer.holmberg@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c672b25e-cda3-5f6b-9a22-f53293f88bdc@alum.mit.edu>
Date: Thu, 4 Jan 2018 10:32:35 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <D673F64D.284F7%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPIsWRmVeSWpSXmKPExsUixO6iqCvq6RdlcG+nrMXU5Y9ZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV0Tz7FFvBGt6KXx3PmBsYt3N1MXJySAiYSEzffZcFxBYS2MEk sfKVbBcjF5D9jUni8vE2VpCEsICfRENHDzuILSIgLDHj7V82iAZrieMTdzGB2GwCWhJzDv0H G8QrYC/xYiqIzcHBIqAi8eaBDkhYVCBN4tWzHcwQJYISJ2c+ASvnFLCRuPf6FVicWcBW4s7c 3VC2uMStJ/OZIGx5ieats5knMPLPQtI+C0nLLCQts5C0LGBkWcUol5hTmqubm5iZU5yarFuc nJiXl1qka66Xm1mil5pSuokREpLCOxh3nZQ7xCjAwajEw7tC3S9KiDWxrLgy9xCjJAeTkihv OEiILyk/pTIjsTgjvqg0J7X4EKMEB7OSCC+nEVCONyWxsiq1KB8mJc3BoiTOq7ZE3U9IID2x JDU7NbUgtQgmq8HBIdBy8eRBJimWvPy8VCUJXk8PoCGCRanpqRVpmTklCKVMHJwgi3iAFq1w B1lUXJCYW5yZDpE/xWjM0dNz4w8Tx7OZrxuYhcDGSYnzXgIpFQApzSjNg5sGSzevGMWBHhXm /QlSxQNMVXDzXgGtYgJateqIL8iqkkSElFQDo8aj18aJ4ZlnX343qZfcs6agaXtUkI7Yn6zW W9szVyc/46qLnHEmIjovWsYxpa45UudZXl+/aXTVl6gD08r+H7xXcPG6ldKP8+2c7td2rv3Q EiK/5o8rU8P13emJKfXnl2Tmn8gw3lJ10Xzqq5OOIrYb/eual9iH7lFeNHNS1QyzjggO79WG SizFGYmGWsxFxYkAzhw0sRIDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/dWO__oDBBLh47XMG_6BhH-1qZQc>
Subject: Re: [MMUSIC] BUNDLE: media-level c= lines in bundle-only m= sections?
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, 04 Jan 2018 15:32:41 -0000

On 1/4/18 8:08 AM, Christer Holmberg wrote:
> Hi,
> 
> BUNDLE doesn’t say much about c= lines, the assumption being that there 
> are no BUNDLE-specific rules related to c= lines: one can use a 
> session-level c= line, or media-level c= lines, also with BUNDLE. The 
> BUNDLE address will use whatever IP address is associated (implicitly or 
> explicitly) with the tagged m= section.
> 
> So far so good.
> 
> Now, Ekr raised a JSEP GitHub issue regarding media-level c= lines in 
> bundle-only m= sections. As we know, BUNDLE currently specifies that a 
> zero port value is assigned to bundle-only m= sections, but nothing is 
> said about media-level c= lines.
> 
> https://github.com/rtcweb-wg/jsep/issues/843
> 
> (The GitHub issue was initially created because of another issue, but if 
> you follow the discussion it will end up in this)
> 
> My suggestion would be that an offerer/answerer MUST NOT assign 
> media-level c= lines to bundle-only m= sections.

This makes sense to me. The bundle only sections are going to get their 
address from some other section so a c= line is at best redundant.

	Thanks,
	Paul

> Would people be ok with this? Does someone suggest something else?
> 
> Whatever the outcome, I think it would be good to clarify it in BUNDLE. 
> I don't think we need to bring the document back to the WG in order to 
> do that – if we can agree on the text I will implement it in a future 
> update (e.g., based on the IESG reviews) of the draft.
> 
> Regards,
> 
> Christer
> 
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 


From nobody Thu Jan  4 08:19:12 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 2603312711B for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 08:19:11 -0800 (PST)
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 hWhMOSgNiydV for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 08:19:08 -0800 (PST)
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 97685126D3F for <mmusic@ietf.org>; Thu,  4 Jan 2018 08:19:08 -0800 (PST)
Received: by mail-wm0-x22d.google.com with SMTP id f140so4338538wmd.2 for <mmusic@ietf.org>; Thu, 04 Jan 2018 08:19:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=3nXo3DOCLu24wMNXKqjhEbLuPoUo/XVSDz+TxsvPZD8=; b=hCnrdhNiT7vg2q3E9BNtf2cdZdvLgkKP7Zr2btu2DL+QGmlMpAJbNoHohADTOxtkyq 3a9gT9eZzVemBPUHN0doHaWaGrRgqqaomk4enpLSQCbGZWibvdZcTJz+ZPUfkyEbhaCl fcGOzKlzhkGGUiNvKSKAeBwmnOjpeYYy4MAeyPGKSMmI935biJ/3verdIvrBvuvPl0B2 zcihB1Rsm77LVI3kadtdAdrwTbc/nXpYfDJC1zQFvZLxeG1GuCjLsXS5z6zl7qVZbO6Z Ui/OJDqVGf4kHxwl/P6joiIrtpw0+KBkXZthrLW8Xh2qvVsAjFcvH1dPj4uMR11+tPvX dJEg==
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:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=3nXo3DOCLu24wMNXKqjhEbLuPoUo/XVSDz+TxsvPZD8=; b=KzUSrs4yf2m8R93kgNU5PwauojU+iWh0720iMxqAPHQ2hU4cJRCzHsT9jdEpwxcE/m X5dKa7S+6eu7Az8lEedQ4jiL5FEDe+rxI5jhEo7SdY8Wq8b3w7Mk6bgNPvrJvHhBfRw+ kbcdbgNs0F+0qGRXRmZ18J+mHdMkReSQTNFm5UP1E84zeYcGovqWHgOn0ctv7e25F8LC /IT3+xkmhvHq5RcqHAmBTlG/wBU1eunhgMnG4B5dcIjELlEW14stZMd9BUhVAJFbFzB+ 3NmmpegPWPRwh0bry778ku9NHDG2locZWEEzUZt0CSwaUt/051tTGEg+xx5DebQbWPsl vWoQ==
X-Gm-Message-State: AKGB3mIc4cKcv6YnLQmF5+wQVapoXWl60WXED4l96Zu61W3RyVF/Mv8h +QizSkoI9UPOxT+U+DwfTjKfp65H
X-Google-Smtp-Source: ACJfBos/WGu7LCqotNhRzFa8E4YJuUX6LBrO8ydgnDl3SZfvIRDMfMwNSmhgpD4L/P3q1pLi3cu7Pg==
X-Received: by 10.28.247.24 with SMTP id v24mr51127wmh.140.1515082746679; Thu, 04 Jan 2018 08:19:06 -0800 (PST)
Received: from [192.168.2.110] (dsl-linz7-16-139.utaonline.at. [81.189.16.139]) by smtp.googlemail.com with ESMTPSA id a71sm2590595wme.33.2018.01.04.08.19.05 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Jan 2018 08:19:05 -0800 (PST)
To: mmusic@ietf.org
References: <D673F64D.284F7%christer.holmberg@ericsson.com> <c672b25e-cda3-5f6b-9a22-f53293f88bdc@alum.mit.edu>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <66f4f064-cb04-b68f-933f-3444f0e7f327@gmail.com>
Date: Thu, 4 Jan 2018 17:19:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <c672b25e-cda3-5f6b-9a22-f53293f88bdc@alum.mit.edu>
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/JftAnHvMxeB3B0fufzG1AtNKSwU>
Subject: Re: [MMUSIC] BUNDLE: media-level c= lines in bundle-only m= sections?
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, 04 Jan 2018 16:19:11 -0000

Christer,


On 2018-01-04 16:32, Paul Kyzivat wrote:
> On 1/4/18 8:08 AM, Christer Holmberg wrote:
>> Hi,
>>
>> BUNDLE doesn’t say much about c= lines, the assumption being that 
>> there are no BUNDLE-specific rules related to c= lines: one can use a 
>> session-level c= line, or media-level c= lines, also with BUNDLE. The 
>> BUNDLE address will use whatever IP address is associated (implicitly 
>> or explicitly) with the tagged m= section.
>>
>> So far so good.
>>
>> Now, Ekr raised a JSEP GitHub issue regarding media-level c= lines in 
>> bundle-only m= sections. As we know, BUNDLE currently specifies that 
>> a zero port value is assigned to bundle-only m= sections, but nothing 
>> is said about media-level c= lines.
>>
>> https://github.com/rtcweb-wg/jsep/issues/843
>>
>> (The GitHub issue was initially created because of another issue, but 
>> if you follow the discussion it will end up in this)
>>
>> My suggestion would be that an offerer/answerer MUST NOT assign 
>> media-level c= lines to bundle-only m= sections.
>
> This makes sense to me. The bundle only sections are going to get 
> their address from some other section so a c= line is at best redundant.
>
>     Thanks,
>     Paul
+1
maybe together with " ... a offerer/answerer  MUST ignore a received 
c-line ...."
Regards
Thomas
>
>> Would people be ok with this? Does someone suggest something else?
>>
>> Whatever the outcome, I think it would be good to clarify it in 
>> BUNDLE. I don't think we need to bring the document back to the WG in 
>> order to do that – if we can agree on the text I will implement it in 
>> a future update (e.g., based on the IESG reviews) of the draft.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Jan  4 13:53:04 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 7198412741D for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 13:53:02 -0800 (PST)
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 4-MpZrd-jKIg for <mmusic@ietfa.amsl.com>; Thu,  4 Jan 2018 13:53:00 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18BE3127077 for <mmusic@ietf.org>; Thu,  4 Jan 2018 13:52:59 -0800 (PST)
X-AuditID: c1b4fb2d-b35ff70000007932-8a-5a4ea23567c1
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 09.C4.31026.532AE4A5; Thu,  4 Jan 2018 22:52:53 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.206]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Thu, 4 Jan 2018 22:52:53 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] BUNDLE: media-level c= lines in bundle-only m= sections?
Thread-Index: AQHThV0VqJ9MZItYF0GkVCGZHqpE4qNjxv+AgAAM/QCAAG1z8A==
Date: Thu, 4 Jan 2018 21:52:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C0EAD1E@ESESSMB109.ericsson.se>
References: <D673F64D.284F7%christer.holmberg@ericsson.com> <c672b25e-cda3-5f6b-9a22-f53293f88bdc@alum.mit.edu> <66f4f064-cb04-b68f-933f-3444f0e7f327@gmail.com>
In-Reply-To: <66f4f064-cb04-b68f-933f-3444f0e7f327@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7tK7pIr8ogzef1S2mLn/MYvHpxFYm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugStjzuxmxoILQhXz1u5mbWCcxN/FyMkhIWAi 8XbeCXYQW0jgMKPE4YmVXYxcQPZiRomGic1ACQ4ONgELie5/2iA1IgKBEp/PHGcCCQsLBEi0 3DSACT/tf8IIYTtJPD54mRnEZhFQkbh/ezYbiM0r4CvR/+ImI8T4JYwSZz+eZQJJcArYSmyd cB/MZhQQk/h+ag2YzSwgLnHryXwmiDsFJJbsOc8MYYtKvHz8jxXCVpJYe3g7C0S9nsSNqVPY IGxtiWULXzNDLBaUODnzCcsERpFZSMbOQtIyC0nLLCQtCxhZVjGKFqcWF+emGxnrpRZlJhcX 5+fp5aWWbGIERsPBLb91dzCufu14iFGAg1GJh/dhv1+UEGtiWXFl7iFGCQ5mJRFeTiOgEG9K YmVValF+fFFpTmrxIUZpDhYlcd6TnrxRQgLpiSWp2ampBalFMFkmDk6pBsbYy1M1l21gSfkz YdHpC5ZHatcJHXzZ9/TrmsrWmlWPJOxmX8wQcTN9JqcdfkN38s11qs9KXyxbH32wfI5O31kj 1qBfR2//4dSxignusnJ4sa/n7v7dimp7H+ovaJ2tXzvj1KXa/+sXWMmYRBolW4l93FCinvJ8 a5H31yOREw726p0XDahc/POzEktxRqKhFnNRcSIAJiml44ICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/eXhExMJOlxmFcbO2zZaOpORNc_c>
Subject: Re: [MMUSIC] BUNDLE: media-level c= lines in bundle-only m= sections?
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, 04 Jan 2018 21:53:02 -0000

Hi,

>>> BUNDLE doesn't say much about c=3D lines, the assumption being that=20
>>> there are no BUNDLE-specific rules related to c=3D lines: one can use a=
=20
>>> session-level c=3D line, or media-level c=3D lines, also with BUNDLE. T=
he=20
>>> BUNDLE address will use whatever IP address is associated (implicitly=20
>>> or explicitly) with the tagged m=3D section.
>>>
>>> So far so good.
>>>
>>> Now, Ekr raised a JSEP GitHub issue regarding media-level c=3D lines in=
=20
>>> bundle-only m=3D sections. As we know, BUNDLE currently specifies that=
=20
>>> a zero port value is assigned to bundle-only m=3D sections, but nothing=
=20
>>> is said about media-level c=3D lines.
>>>
>>> https://github.com/rtcweb-wg/jsep/issues/843
>>>
>>> (The GitHub issue was initially created because of another issue, but=20
>>> if you follow the discussion it will end up in this)
>>>
>>> My suggestion would be that an offerer/answerer MUST NOT assign=20
>>> media-level c=3D lines to bundle-only m=3D sections.
>>
>> This makes sense to me. The bundle only sections are going to get=20
>> their address from some other section so a c=3D line is at best redundan=
t.
>>
>> =A0=A0=A0=A0Thanks,
>> =A0=A0=A0=A0Paul
>
>+1
>maybe together with " ... a offerer/answerer=A0 MUST ignore a received c-l=
ine ...."

The rules for selecting the offerer/answerer BUNDLE addresses will make sur=
e they are "rejected", so I am not sure whether we need to say anything exp=
licit.

Regards,

Christer




>> Would people be ok with this? Does someone suggest something else?
>>
>> Whatever the outcome, I think it would be good to clarify it in=20
>> BUNDLE. I don't think we need to bring the document back to the WG in=20
>> order to do that - if we can agree on the text I will implement it in=20
>> a future update (e.g., based on the IESG reviews) of the draft.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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


From nobody Thu Jan 11 21:42:17 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 6B36C12D86F for <mmusic@ietfa.amsl.com>; Thu, 11 Jan 2018 21:42:15 -0800 (PST)
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 U29Lfj5GMphU for <mmusic@ietfa.amsl.com>; Thu, 11 Jan 2018 21:42:13 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA8731201FA for <mmusic@ietf.org>; Thu, 11 Jan 2018 21:42:12 -0800 (PST)
Received: from [10.0.1.105] (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 w0C5fwhh075860 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 11 Jan 2018 23:42:02 -0600 (CST) (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.105]
From: ben@nostrum.com
Message-Id: <4ECE755B-50EF-4909-929E-D4EB80647DEC@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_35EDB2DB-46D5-4888-9577-93BC8FE13EF7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 11 Jan 2018 23:41:57 -0600
In-Reply-To: <1d992ddc-3853-791f-2bd2-ed8228b1cf8a@gmail.com>
Cc: MMUSIC <mmusic@ietf.org>, Flemming Andreasen <fandreas@cisco.com>
To: Thomas Stach <thomass.stach@gmail.com>
References: <151397853699.11984.9244404367924484838.idtracker@ietfa.amsl.com> <1d992ddc-3853-791f-2bd2-ed8228b1cf8a@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/JdphNK_78vQ-gR3-DjGZ7w2a9l4>
Subject: Re: [MMUSIC] New Version Notification for draft-ietf-mmusic-trickle-ice-sip-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: Fri, 12 Jan 2018 05:42:15 -0000

--Apple-Mail=_35EDB2DB-46D5-4888-9577-93BC8FE13EF7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I think this version is ready for IETF Last Call. I will request that =
shortly.

Thanks!

Ben.

> On Dec 22, 2017, at 3:39 PM, Thomas Stach <thomass.stach@gmail.com> =
wrote:
>=20
> All,
>=20
> this update addresses comments from Ben's AD review and from =
Christer's review as a co-author.
> Changes from draft-ietf-mmusic-trickle-ice-sip-11 include:
>    o  addressing comments from Ben Campell's AD review and Christer's
>       review
>    o  Numerous editorial improvements/corrections
>    o  Added [RFC8174] boiler plate and adapted usage of normative
>       language
>    o  Clarified terminology ICE modules .vs.  ICE agent
>    o  Added more detailed OA procedures
>    o  Corrected default values in m-line and usage of "a=3Dmid:" =
attribute
>       explicitly mentioned for offer/answer
>    o  Removed explicit mentioning of XMPP
>    o  Added Deployment Considerations section
>    o  Fixed ref for rfc5245bis
> Regards
> Thomas
>=20
>=20
> -------- Forwarded Message --------
> Subject:	New Version Notification for =
draft-ietf-mmusic-trickle-ice-sip-12.txt
> Date:	Fri, 22 Dec 2017 13:35:36 -0800
> From:	internet-drafts@ietf.org
> To:	Christer Holmberg <christer.holmberg@ericsson.com>, Enrico =
Marocco <enrico.marocco@telecomitalia.it>, Thomas Stach =
<thomass.stach@gmail.com>, Emil Ivov <emcho@jitsi.org>
>=20
> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-12.txt
> has been successfully submitted by Thomas Stach and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-mmusic-trickle-ice-sip
> Revision:	12
> Title:		A Session Initiation Protocol (SIP) usage for =
Trickle ICE
> Document date:	2017-12-22
> Group:		mmusic
> Pages:		45
> URL:
> =
https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice-sip-12.=
txt
>=20
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>=20
> Htmlized:
> https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-12
>=20
> Htmlized:
> =
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-trickle-ice-sip-12=

>=20
> Diff:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-trickle-ice-sip-12=

>=20
>=20
> Abstract:
>    The Interactive Connectivity Establishment (ICE) protocol describes =
a
>    Network Address Translator (NAT) traversal mechanism for UDP-based
>    multimedia sessions established with the Offer/Answer model.  The =
ICE
>    extension for Incremental Provisioning of Candidates (Trickle ICE)
>    defines a mechanism that allows ICE Agents to shorten session
>    establishment delays by making the candidate gathering and
>    connectivity checking phases of ICE non-blocking and by executing
>    them in parallel.
>=20
>    This document defines usage semantics for Trickle ICE with the
>    Session Initiation Protocol (SIP) and defines a new SIP Info =
Package.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
>=20


--Apple-Mail=_35EDB2DB-46D5-4888-9577-93BC8FE13EF7
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpYSqUACgkQgFZKbJXz
1A3hMQ/+NC2QmrNhX9Kgl5SgitDMY/XWRJ/JZ9Pw+N6IJKTtDB5v6wd9wgA8Dozz
iFUubRKx6zrOcR/wkdvFuEDcr3apYwUfHVl1A8z84ZeWEozYJlkbhCCCVLjcTk3Q
vMY1voTpTS24KhzaUR5PFKbD2C7NRpQRoRhR8MYUxIdNQoZ1CJvz7nsZXNSp7U6W
ISN/ekSs7i7zOmvm6SV+LikROVnxlBLzGDLcA8FMMC8yjzcH/vhMjyuvQk8RgLrZ
3loBSCRfipTlb9SHDAZgnovg1UN08aZVOL2mfR1U6Z55orsOb69Hz0QgzClWgSiJ
JDDYKYcsOtAKlXk2VICmxllMMsrmOJKep0Q/gp89VT7AC3pclSc1Q53oDdMuxKhP
EuQrU3sNks9TLL5ozBE/ts364dOpho8tBIRZJj5aMz6SloEK95gTFZHvYIHS1BqJ
aICp76WDFZXscUGVIhpAc00nlpG0+fXLGCQYau21sgLxKyaovnN5mAISXdxJYZHP
Tn31OhFnQXzg1lrrR3WggiY1zN6BqzpeHpCBJTJNevzl5i46Xx7F52re7JQzqAWu
YaBg7F3LRJAmLGGnvqsnM75So7lf3CrYA5O5zTfDaa7Pv+xQsvzwA6uwLKHRlZze
dvnm5AC5kmCgPt2ODxgQqV5XVRwZUMxvwSXWhzpxlSgWdZ75CvM=
=moHx
-----END PGP SIGNATURE-----

--Apple-Mail=_35EDB2DB-46D5-4888-9577-93BC8FE13EF7--


From nobody Fri Jan 12 06:22:42 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 3B4F712D77D; Fri, 12 Jan 2018 06:22:36 -0800 (PST)
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.68.3
Auto-Submitted: auto-generated
Precedence: bulk
CC: fandreas@cisco.com, ben@nostrum.com, draft-ietf-mmusic-trickle-ice-sip@ietf.org, mmusic@ietf.org, mmusic-chairs@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: <151576695623.18638.7468534003675516336.idtracker@ietfa.amsl.com>
Date: Fri, 12 Jan 2018 06:22:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/EEEdaUpeBwhzHwY5i3Z-D1gFTM4>
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-trickle-ice-sip-12.txt> (A Session Initiation Protocol (SIP) usage for Trickle ICE) 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: Fri, 12 Jan 2018 14:22:36 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'A Session
Initiation Protocol (SIP) usage for Trickle ICE'
  <draft-ietf-mmusic-trickle-ice-sip-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-01-26. 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


   The Interactive Connectivity Establishment (ICE) protocol describes a
   Network Address Translator (NAT) traversal mechanism for UDP-based
   multimedia sessions established with the Offer/Answer model.  The ICE
   extension for Incremental Provisioning of Candidates (Trickle ICE)
   defines a mechanism that allows ICE Agents to shorten session
   establishment delays by making the candidate gathering and
   connectivity checking phases of ICE non-blocking and by executing
   them in parallel.

   This document defines usage semantics for Trickle ICE with the
   Session Initiation Protocol (SIP) and defines a new SIP Info Package.




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

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


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


The document contains these normative downward references.
See RFC 3967 for additional information: 
    draft-ivov-mmusic-sdpfrag: Internet Media Type application/sdpfrag (None - )
    draft-ietf-mmusic-rfc5245bis: Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal (None - IETF stream)




From nobody Fri Jan 12 06:32:36 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 E989112E889 for <mmusic@ietfa.amsl.com>; Fri, 12 Jan 2018 06:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 3O6xX-par_Ys for <mmusic@ietfa.amsl.com>; Fri, 12 Jan 2018 06:32:34 -0800 (PST)
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 A74CC12E891 for <mmusic@ietf.org>; Fri, 12 Jan 2018 06:32:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=376; q=dns/txt; s=iport; t=1515767554; x=1516977154; h=to:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=cwgpz6GCvqmkRbBGTUgnYLWAMGV954QXuJah7+nb1ks=; b=Yc6dPyiGO+pU6JUSkaaSv/JhWbef5vqrtx34EuttSSJaeqn1RXH1KnuJ wjCy10xgnNHSgMyUOQQ1g2oRsOl1HG8lWm/Xvbha7O2Gs0Jc6JSRmKOE9 GwZrhbQ9kKX7SjSkdNQbO0lLEZ89BB5R3eUwb6qzSI5Nmp8Hau+lMwKSc w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AgBCxlha/5xdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYMRMIFahC6ZBIFbjyiFSIR+CoUyhExDFAEBAQEBAQEBAWsohU0?= =?us-ascii?q?VdgImAl8NCAEBiiINrxKCJ4o4AQEBAQYCASWBD4MtghWBV4ISDIRCgzaDOoJlB?= =?us-ascii?q?ZM8kCiOZoEEhWGCAAEYhh2Db4drlyWBPDYigVBMIxWCaIJfghUjjGwBAQE?=
X-IronPort-AV: E=Sophos;i="5.46,349,1511827200"; d="scan'208";a="342610654"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jan 2018 14:32:32 +0000
Received: from [10.118.10.18] (rtp-fandreas-2-881-ap.cisco.com [10.118.10.18]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w0CEWTmP020863 for <mmusic@ietf.org>; Fri, 12 Jan 2018 14:32:29 GMT
To: mmusic <mmusic@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <0ac18131-bf6f-8cb8-8874-b738e25c4012@cisco.com>
Date: Fri, 12 Jan 2018 09:32:31 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
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/TOvDC5bvkfql78USwxgdlJ0E-WE>
Subject: [MMUSIC] MMUSIC meet at IETF 101 (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, 12 Jan 2018 14:32:36 -0000

Greetings

Requests for WGs to meet at IETF 101 in London are due by February 2 and 
hence we wanted to prod the group at this point to see if anybody 
expects a need for MMUSIC to meet in London. If you do, please let the 
chairs know sooner rather than later. If we do not hear from anybody, we 
do not expect to ask for a meeting slot.

Thanks

-- Flemming & Bo


From nobody Wed Jan 17 14:48:31 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 8FA2C12D886; Wed, 17 Jan 2018 14:48:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151622930548.10246.3819483466561734213@ietfa.amsl.com>
Date: Wed, 17 Jan 2018 14:48:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/id1xp-SDUEhBncoy8NS97NdjZ_U>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rid-13.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, 17 Jan 2018 22:48:26 -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           : RTP Payload Format Restrictions
        Author          : Adam Roach
	Filename        : draft-ietf-mmusic-rid-13.txt
	Pages           : 28
	Date            : 2018-01-17

Abstract:
   In this specification, we define a framework for specifying
   restrictions on RTP streams in the Session Description Protocol.
   This framework defines a new "rid" SDP attribute to unambiguously
   identify the RTP Streams within a RTP Session and restrict the
   streams' payload format parameters in a codec-agnostic way beyond
   what is provided with the regular Payload Types.

   This specification updates RFC4855 to give additional guidance on
   choice of Format Parameter (fmtp) names, and on their relation to the
   restrictions defined by this document.


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

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

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


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

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


From nobody Thu Jan 18 06:03:56 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 D74C01241F3 for <mmusic@ietfa.amsl.com>; Thu, 18 Jan 2018 06:03:55 -0800 (PST)
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 OuFYN-0pJ5hJ for <mmusic@ietfa.amsl.com>; Thu, 18 Jan 2018 06:03:49 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F050D12025C for <mmusic@ietf.org>; Thu, 18 Jan 2018 06:03:48 -0800 (PST)
X-AuditID: c1b4fb3a-335ff700000037f2-df-5a60a943671a
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id C4.65.14322.349A06A5; Thu, 18 Jan 2018 15:03:47 +0100 (CET)
Received: from [147.214.160.123] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.78) with Microsoft SMTP Server (TLS) id 14.3.352.0; Thu, 18 Jan 2018 15:03:46 +0100
To: IETF MMUSIC WG <mmusic@ietf.org>
References: <151622930548.10246.3819483466561734213@ietfa.amsl.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <6dcfe49e-bb40-5d2f-0ec1-4641d450a6a8@ericsson.com>
Date: Thu, 18 Jan 2018 15:03:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <151622930548.10246.3819483466561734213@ietfa.amsl.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010203030003010401020805"
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCLMWRmVeSWpSXmKPExsUyM2K7n67zyoQog4MHhCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMMHkwt+uFcs3/+ApYHxuWMXIyeHhICJxO4pPexdjFwcQgKH GSXebJ3EDOFsYZSY8/YJO0iVsICpxN3Jn8FsEQEViX/vHrCB2EICzhJ/nn8Fi7MJWEjc/NEI FucVsJeYuv4DWJxFQFViwe7pYLaoQIzEguZDzBA1ghInZz5hAbE5BVwkXh6/C3YFs0A3o8TP vqWMEAu0JRqaOlghTlWSuD7vOssERv5ZSPpnIesBSTAL2ErcmbubGcLWlli28DWULS7R9GUl K4RtLTHj10E2CFtRYkr3Q3YI21Ti9dGPUHOMJN7taWRfwMi5ilG0OLW4ODfdyEgvtSgzubg4 P08vL7VkEyMw/A9u+W21g/Hgc8dDjAIcjEo8vNyTE6KEWBPLiitzDzGqAM15tGH1BUYplrz8 vFQlEd533kBp3pTEyqrUovz4otKc1OJDjNIcLErivE5pFlFCAumJJanZqakFqUUwWSYOTqkG xlzD5oTcTaFnOdTtA9cK/d26Xlvoyu1IKZXeBb9nXZcR0tP7seO7iu/D1pUNctILGz1Zr0x1 aS7YILPjH0/AH9PiGMv635ohio/0dNZquyqzNtqZ+G8+5sq5kbs+2uOecaiF2ZKOcwXy82dO PR8w5VyuDtOEPcYvTyQfj9bKUAn17I6bF+2vxFKckWioxVxUnAgA/CdubYcCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FfVP0Xdj00bK_a9Jv98-Gp7Q_OU>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-rid-13.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: Thu, 18 Jan 2018 14:03:56 -0000

--------------ms010203030003010401020805
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Language: en-GB

MMUSIC WG,

It is great that Adam has now done and performed the changes that was=20
discussed between the authors as result of the WG session in Singapore.=20
At this point I believe all the necessary changes has been performed to=20
RID and Simulcast documents. Thus, making it possible for the WG chairs=20
to go forward with publication request of simulcast and continue=20
processing of RID. However, don't take my word for it and please check=20
the changes of the documents.

Cheers

Magnus


Den 2018-01-17 kl. 23:48, skrev internet-drafts@ietf.org:
> A New Internet-Draft is available from the on-line Internet-Drafts dire=
ctories.
> This draft is a work item of the Multiparty Multimedia Session Control =
WG of the IETF.
>
>          Title           : RTP Payload Format Restrictions
>          Author          : Adam Roach
> 	Filename        : draft-ietf-mmusic-rid-13.txt
> 	Pages           : 28
> 	Date            : 2018-01-17
>
> Abstract:
>     In this specification, we define a framework for specifying
>     restrictions on RTP streams in the Session Description Protocol.
>     This framework defines a new "rid" SDP attribute to unambiguously
>     identify the RTP Streams within a RTP Session and restrict the
>     streams' payload format parameters in a codec-agnostic way beyond
>     what is provided with the regular Payload Types.
>
>     This specification updates RFC4855 to give additional guidance on
>     choice of Format Parameter (fmtp) names, and on their relation to t=
he
>     restrictions defined by this document.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-rid/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-rid-13
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rid-13
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-rid-13
>
>
> Please note that it may take a couple of minutes from the time of submi=
ssion
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--=20

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



--------------ms010203030003010401020805
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-kryptografisk signatur

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DNEwggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJ
BgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNV
BAoMCEVyaWNzc29uMRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJ
ARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+
laqg5eXTqonqnzT9ykEGL2dx9mBT+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJ
HGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iV
IiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpigGFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36o
gzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkrbdmdnjKGrYSnJigmxw14pJugxL/Vb2Ee
VcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDov
L2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNybDCBggYI
KwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29t
MEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29u
bmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rlcmx1bmRAZXJp
Y3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0
dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3
DQEBCwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4Q
ihhoQR3cvhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXD
yF9mhWYbSAkJyx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6
H3zO3nsq++KBmsOiSKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvE
lup5n7l864FqxnC2friDo4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl
60rmc8SJlt6QXKw0wXEOE1MubauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwD
ig3SZi1qP7D/Ds4V+JLIjjUJc25l9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8K
v7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLCQaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3
UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Zla71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzY
VBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd//n4YbY2QhDCCBsIwggSqoAMCAQICEFO4
foPhnJkok7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUx
MDI3MTIxNjQ2WjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMM
HEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDs8t8AALhQ8qe72FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfS
Tm+7meisbhkqUXkL7fFzoe4iIZCh/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbX
ILlLhRummTdDdxhVW4Leo0awEhfLf98MvWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfp
VdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmdvkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2
PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2
H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP1UrZaEIFu+hO+s0Nm8sOUMa4TlG4
rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0FdQDEzQlnF/h1L4AK1MOkX
1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA+yrrplCh/kYvSBjv
Zibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUrrvijPDaGK5FN
VSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQwgYoGCCsG
AQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEu
Y29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3Js
LTMudHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1Ud
JQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7
GZ6XnHasID3Y3OORauPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0G
CSqGSIb3DQEBCwUAA4ICAQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDU
JQEPRs5QtaZiObNHCZ7mmSNMVek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHG
vw5RY6vRlZrj0uKvdASzYL4KMaB7m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYn
nl2t3D3oBX2NZCQysshUcqRdUbkS13HTCIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwf
ixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNMMbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ8
5AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4Hd
Dc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0RLCi+4d4/47Zs3DC3PUNOxdOE
EHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZfAFM4HoHz8K2BZRaHKWhd
3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqGahxlHYzl/QyEG/du
jp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGCAzswggM3AgEB
MFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMA0GCWCGSAFlAwQCAQUA
oIIBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAxMTgx
NDAzNDZaMC8GCSqGSIb3DQEJBDEiBCDlpMVZH0h+A+BDVJRqBniLyxVcbhFl5EwJnnHGzMcJ
1DBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjEl
MCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBlrrZreXF5
7TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMGwGCyqGSIb3DQEJEAILMV2gWzBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nz
b24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62
a3lxee0wDQYJKoZIhvcNAQEBBQAEggEALe/ju50w8XWHtMNh8brofSZIXu8YBJB9A29+cJGB
lYmNpOazUFcQ28vsCPzUw6eVXF0TCbw/VNUQr9XEEN+Lr02IfAybP40xL96XOWHuC8RRBfHP
LtCDICgSTNr95AxebeLhntDjFO1PIpO000/uw3EKd6dv5XVBFqtQ+wJHV3ppBP8r75OferZl
UPfFKAIUssoeh1srLQsi7rwquAMjKJwiXjCrKIbkoGfMt56LN4POug86pZ8TIQa8pswUsak2
j68gJm1j7Lg9tJq3Ru3IQL1G6cdoIsdG3KzoHtKNxtlXwoXws/xcR9etOp9dnon9EC/kVSXC
yZ/WD2kQKCNOHwAAAAAAAA==
--------------ms010203030003010401020805--


From nobody Fri Jan 19 16:01:18 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 C4CC512D962; Fri, 19 Jan 2018 16:00:38 -0800 (PST)
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 aMP5Kx0-Vp1O; Fri, 19 Jan 2018 16:00:34 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C26FE126C0F; Fri, 19 Jan 2018 16:00:29 -0800 (PST)
Received: from [10.0.1.105] (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 w0K00S4d040822 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 19 Jan 2018 18:00:29 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_66D0E478-4A39-4D77-9D09-0E38BDCB7FF1"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <68E80650-0B78-4F4A-9339-BF6FE360FC8B@nostrum.com>
Date: Fri, 19 Jan 2018 18:00:27 -0600
To: draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org, MMUSIC <mmusic@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/C5gcXVIX_xGYF7C7OwwXYjf1sAI>
Subject: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47
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, 20 Jan 2018 00:00:39 -0000

--Apple-Mail=_66D0E478-4A39-4D77-9D09-0E38BDCB7FF1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

This is my AD Evaluation of  =
draft-ietf-mmusic-sdp-bundle-negotiation-47.

First, thank you for all the work on this. I know this has been a =
difficult process. I do have a few substantive comments and a number of =
editorial comments. I would like to resolve the substantive comments and =
make at least a pass over the editorial comments prior to IETF Last =
Call.

Thanks!

Ben.

=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94

*** Substantive Comments ***

- boilerplate: I assume the pre-2008 boilerplate is present due to the =
extensive quoted text from RFC 3264. I note that it is not usually =
necessary to quote large amounts of text from an RFC in order to update =
it. I don=E2=80=99t expect a change in the update approach this late in =
the process, but I suggest that for future drafts people try to avoid =
creating the need for the pre-2008 boilerplate.

- section 8, first paragraph after bullet list: I=E2=80=99m confused as =
to whether this talks about the initial offer or a subsequent offer. the =
comment about the =E2=80=9Cpreviously negotiated SDP parameters=E2=80=9D =
seems to suggest the latter. I suspect this is intended to cover all =
offers, in which case it needs clarification.

-8.3.3: IIUC, the criteria mean that the only m=3D sections that the =
answerer can move out of the bundle are those that have unique addresses =
but are not listed first in the group attribute. If that is correct, a =
sentence or two to say that would be helpful.

-8.5, first paragraph. IIUC, it=E2=80=99s not syntactically possible to =
assign more than one m=3D section the bundle address, since only one can =
be first in the group attribute. If that is correct, the MUST here is a =
statement of fact. Or am I missing something?

-9: There are several assertions that in order to do something you MUST =
have a spec saying how to do it. Formally, I think the requirement is =
really that you MUST NOT do that thing unless such a spec exists. =
(2119/8174 keywords are normally about implementation behavior.)

-10.2,
 =E2=80=94 paragraph 7: What implementations are we talking about that =
may not follow the requirements to include the tag in RTP/RTCP? Early =
implementations of this draft? Something else? As it is, it seems like =
we are talking about implementations that do not follow this spec. That =
makes the statement =E2=80=9C  =E2=80=A6 In this situation, each "m=3D" =
section MUST use unique payload type values=E2=80=A6=E2=80=9D =
problematic, as it seems to be putting requirements on implementations =
that do not follow this draft in the first place.

=E2=80=94 '  Therefore, when processing a compound packet, any contained =
SDES packet MUST be handled first.
      Note that this is a change from [RFC3550] Section 6.1 which
      states that "Each individual RTCP packet in the compound packet
      may be processed independently with no requirements upon the order
      or combination of packets=E2=80=9D.=E2=80=99

Doesn=E2=80=99t this require an update of 3550? It=E2=80=99s not merely =
a tightening of requirements, it=E2=80=99s a reversal of guidance from =
that document when used in this context.

-10.3.1.3, last paragraph: What is the expected behavior when that =
"protocol error" occurs?

-15.2, last paragraph: Is it worth recommending against patterns which =
could be used as persistent identifiers, even if they don=E2=80=99t =
expressly identify a person or application?

-16.3: Please use the IESG and =E2=80=9Ciesg@ietf.org=E2=80=9D as the =
contact for the IANA registrations.

-17, 2nd paragraph:
=E2=80=94 Again, is it worth mentioning the risk of persistent =
identifiers?
=E2=80=94  =E2=80=9C=E2=80=A6 SHOULD be 3 bytes or less, to allow them =
to efficiently fit into the MID RTP header extension.=E2=80=9D
It seems like that requirement belongs in 15.2

-17, last paragraph: Doesn=E2=80=99t that require an update to 7941

-18: Would it make sense to have one of the examples use media-level c=3D =
lines?


*** Editorial Comments and nits ***

- Terminology issues: I think some of the terminology here will confuse =
readers who are new to the concepts. In particular, IIUC, =E2=80=9Cbundle =
address=E2=80=9D means address + port. I think many readers will fall =
back to assuming that address means IP address. (Especially when we talk =
about a =E2=80=9Cunique address=E2=80=9D assigned to an m=3D section, =
when much of the time that may just mean a unique port.)

I also find defining the term =E2=80=9CBundle Tag=E2=80=9D to mean the =
first tag in the list to be confusing. It may be easier to just refer to =
the =E2=80=9Cfirst tag in the group list=E2=80=9D.

=E2=80=94 Examples: Any chance of some of the examples showing IPv6? I =
suspect it=E2=80=99s a trivial change for at least some examples, since =
they use domain names.

-abstract: The abstract seems longer and more detailed than strictly =
necessary. The first two sentences along with a brief mention of the =
update to 3264 and the SDES item/RTP header extension would be =
sufficient.

-Section 1,
=E2=80=94 first paragraph: This sort of jumps into things without much =
context. (e.g. that we are talking about media sessions signaled using =
SDP offer/answer.=E2=80=9D
s/consume/consumes
=E2=80=94 paragraphs 5-9: Most of the instances of the word =E2=80=9Calso=E2=
=80=9D are unneeded.
=E2=80=94 paragraphs 7 and 9: These paragraphs both talk about updates =
to 3264; it would be better to keep them together.
=E2=80=94 2nd to last paragraph, =E2=80=9CThe procedures in this =
specification apply independently to a given BUNDLE group.=E2=80=9D : I =
don=E2=80=99t understand what that sentence is trying to convey.

- Section 2: The terminology list would be more readable as a bullet =
list or hanging indent list.

-3: There are at least one lower case =E2=80=9Cmust=E2=80=9D and a =
number of lower case =E2=80=9Cshoulds=E2=80=9D. Please consider using =
the boilerplate from RFC 8174, or verify that the lower case versions =
are not intended to be keywords.

-5:
=E2=80=94 First paragraph: inconsistent tense. Please consider s/ =E2=80=9C=
 =E2=80=A6 section will use =E2=80=A6=E2=80=9D / =E2=80=9C=E2=80=A6 =
section uses=E2=80=A6=E2=80=9D
=E2=80=94 2nd paragraph: The citation to RFC5888 looks like a reference =
for the =E2=80=9CBUNDLE=E2=80=9D semantic value, rather than for the =
grouping framework. Please consider something to the effect of the =
following:
OLD:
     The BUNDLE extension is indicated using an SDP =E2=80=99group=E2=80=99=
 attribute with a "BUNDLE" semantics value [RFC5888].
NEW:
     The BUNDLE extension is indicated using an SDP =E2=80=99group=E2=80=99=
 attribute with a semantics value [RFC5888] of "BUNDLE=E2=80=9D.

- Section 8.1:
=E2=80=94 Consider moving this section to later in the offer/answer =
details. I think it would be easier for a reader to understand this =
section after they have some more general context.
=E2=80=94 Title: Spell out =E2=80=9CMultiplex=E2=80=9D in the title.
=E2=80=94 First Paragraph: The wording could be taken to mean that all =
attributes with a mux category of IDENTICAL or TRANSPORT must be =
included in the first place. I think the point is that, if they are =
present, they must be included in each m=3D section. I suggest something =
like the following:
OLD:
   =E2=80=A6 IDENTICAL and TRANSPORT mux category SDP attributes MUST =
explicitly be included in each bundled "m=3D=E2=80=9C section ...
NEW:
   =E2=80=A6 Any IDENTICAL and TRANSPORT mux category SDP attributes =
included in the BUNDLE group MUST explicitly be included in each bundled =
"m=3D=E2=80=9C section =E2=80=A6

-8.2.1, first paragraph:
=E2=80=94 The phrase =E2=80=9Crepresented by the =E2=80=A6 BUNDLE-tag=E2=80=
=9D occurs repeatedly throughout the document. The use of =
=E2=80=9Crepresented=E2=80=9D there seems awkward. I think =
=E2=80=9Cindicated=E2=80=9D would be a better word choice.
=E2=80=94 should =E2=80=9Cofferer BUNDLE address=E2=80=9D be =E2=80=9Coffe=
rer suggested BUNDLE address=E2=80=9D?

-8.5.2: Should =E2=80=9Cadd a bundled m=3D section=E2=80=9D be =E2=80=9Cad=
d a _new_ bundled m=3D section=E2=80=9D?

-9:
=E2=80=94 first paragraph: =E2=80=9C =E2=80=A6 different protocols on =
top of the transport-layer protocol =E2=80=A6=E2=80=9D
Upper layer protocols?
=E2=80=94 Last paragraph: This paragraph seems mostly (or entirely) =
redundant to section 9.1.

-10.2:

=E2=80=94 " RTCP packets for which no appropriate "m=3D" section can be =
identified
   MUST be processed as usual by the RTP layer, updating the metadata
   associated with the corresponding RTP streams, but are not passed to
   any "m=3D" section.=E2=80=9D

I don=E2=80=99t think things gets passed to sections of SDP. What does =
this really talk about?

=E2=80=94 =E2=80=9C Rules for additional processing of the various types =
of RTCP packets
   are explained below.=E2=80=9D

Should that say =E2=80=9CAdditional rules for processing=E2=80=A6=E2=80=9D=
?

-11, 2nd bullet: " previously selected [Section 8.3.1 ] or new suggested =
[ Section 8.5.1]=E2=80=9D
s/new/newly

=E2=80=94 last paragraph: It may be worth clarifying that this doesn't =
change any requirement specified by the application or signaling =
protocol. For example, WebRTC still requires ICE even though bundle is =
used.

11.1:
 =E2=80=94 2nd paragraph: =E2=80=9C previously selected or new suggested =
=E2=80=9C
s/new/newly

=E2=80=94 3rd paragraph: Construct of the form of =E2=80=9CMUST only=E2=80=
=9D can be ambiguous. Please consider restating in the form of a MUST =
NOT construction. (For example, =E2=80=9CMUST only do foo when=E2=80=A6.=E2=
=80=9D can be interpreted as =E2=80=9CMUST NOT do foo unless=E2=80=A6=E2=80=
=9D or =E2=80=9CMUST NOT do anything but foo when=E2=80=A6=E2=80=9D   =
[Note: This construct repeats several times in the next few sections. ]

-19, 3rd paragraph from end: It=E2=80=99s seems a bit odd to thank a =
co-author (Cullen) for text contributions :-)



















--Apple-Mail=_66D0E478-4A39-4D77-9D09-0E38BDCB7FF1
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpihpsACgkQgFZKbJXz
1A1+0BAAkb3Yfp6suxNRMbGQUPvv2Xl6FZSrMJqpYcQBbD1zE/sbbjau0ApcKGF2
eCvIlvtCLhCvGBEjwbWdwEvAbCsrlUvOUlYGb+H0AtNJyTxlUxMsHPg5WH8j0p74
WhfPDPPzzxOHpjtQmlW+Urofe24ZAhpZ6q0DY1u218AQeL1RPRzKiwFvtf+Lw74l
poCbDG+Jnr9uEySU0+sJcP2SRF2Js5KOGoEHHgFKOve38JyHwGSyqgEUPSn3u+Jr
coRKKcKDew2MEN1iOFzN5KaytLoFOwkzRAyZgwpoywbEnomi4v6TaU5EcPV5qCKt
/8wwIuccKgXZFKvxlicugn5igaDHP3Nezv6vPZcTLl47af9q/NldD5ZdpLOcaBfJ
jex0Dk5tSaUO3AoaadSTkuBZtDixvwkFR1YGm9Z+yCC5XM5cY3aJ2i4YKzh2pJHt
TgkPBS6pTtC26yJh/omQZtdhTI57wctyhofaZEK6Je/7qgBdqqLL9lMaYhhBR6NA
Ejf8+TEWvIkHraKwq+ODKMfnG6/hP3PY+dvdw9jorST9Hr4K0OhwEmhR5ZGiA5uS
gX8A8YqKVoHKp9qfR6DOUR8H+uAmfxMSJoPqlXQe6TX+g+or81hYedE5wqQZt4sF
6Pi62s9nVtOjsazc52DSjAN0FRDKe++D3laJXtlApqBVoW8RzDs=
=Q4KS
-----END PGP SIGNATURE-----

--Apple-Mail=_66D0E478-4A39-4D77-9D09-0E38BDCB7FF1--


From nobody Sat Jan 20 05:45: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 8BE99127078; Sat, 20 Jan 2018 05:45:00 -0800 (PST)
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 bZ6E0omocIqY; Sat, 20 Jan 2018 05:44:59 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7364A126C23; Sat, 20 Jan 2018 05:44:58 -0800 (PST)
X-AuditID: c1b4fb25-473ff7000000341b-c9-5a6347d8da71
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id EC.5A.13339.8D7436A5; Sat, 20 Jan 2018 14:44:56 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Sat, 20 Jan 2018 14:44:55 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
Thread-Index: AdOR5+qL7nrym0YKTg6KUgOkGJEv7Q==
Date: Sat, 20 Jan 2018 13:44:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C130970@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.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNLMWRmVeSWpSXmKPExsUyM2K7tO4N9+Qog+YF4hbzO0+zW5x4/43V YuryxywOzB5Llvxk8pi18wlLAFMUl01Kak5mWWqRvl0CV8akaR9ZCw65VtxoOsDYwHjHuYuR k0NCwERi8+HnbF2MXBxCAocZJSbtWsAE4SxhlJj75DBQhoODTcBCovufNkhcRGAzo8TLa2fZ QLqFBTIkFq68wA5iiwhkSvQt+sYIYetJ3N3+nRGkl0VAVeLA2QKQMK+Ar8SNWc1gJYwCYhLf T61hArGZBcQlbj2ZzwRxkIDEkj3nmSFsUYmXj/+xQthKEo1LnrCCjGQW0JRYv0sfolVRYkr3 Q3aI8YISJ2c+YZnAKDQLydRZCB2zkHTMQtKxgJFlFaNocWpxUm66kbFealFmcnFxfp5eXmrJ JkZgkB/c8lt1B+PlN46HGAU4GJV4eDkMkqOEWBPLiitzDzFKcDArifDq30qKEuJNSaysSi3K jy8qzUktPsQozcGiJM570pM3SkggPbEkNTs1tSC1CCbLxMEp1cCol592QmSWNmMct6FNvmGU iotB+uNcAd/0LpPFhip6z1NuOux61bzsZ6fF5MVVbxIObjmnv/bncvMow98f9HZNDzmd3Btj lamWncHjeJh9rTF75onbtz97tc/3+FQ++berbr3F8pIfhw/2hIimPdONvC7o6rExotb0fuPZ z0IbvM+8XCa0t1+JpTgj0VCLuag4EQDdc5KGbgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/xxMJQgCj4r_p_KIU8fbkRMFBusM>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 20 Jan 2018 13:45:00 -0000

SGkgQmVuLA0KDQpUaGFua3MgZm9yIHlvdXIgcmV2aWV3ISBQbGVhc2Ugc2VlIGlubGluZS4NCg0K
KEZvciBjb252ZW5pZW5jZSwgSSB3aWxsIGFkZHJlc3MgeW91ciBlZGl0b3JpYWwgY29tbWVudHMg
aW4gYSBzZXBhcmF0ZSByZXBseSkNCg0KKioqIFN1YnN0YW50aXZlIENvbW1lbnRzICoqKg0KDQot
LS0NCg0KPiAtIGJvaWxlcnBsYXRlOiBJIGFzc3VtZSB0aGUgcHJlLTIwMDggYm9pbGVycGxhdGUg
aXMgcHJlc2VudCBkdWUgdG8gdGhlIGV4dGVuc2l2ZSBxdW90ZWQgdGV4dCBmcm9tIFJGQyAzMjY0
LiANCj4gSSBub3RlIHRoYXQgaXQgaXMgbm90IHVzdWFsbHkgbmVjZXNzYXJ5IHRvIHF1b3RlIGxh
cmdlIGFtb3VudHMgb2YgdGV4dCBmcm9tIGFuIFJGQyBpbiBvcmRlciB0byB1cGRhdGUgaXQuIEkg
ZG9u4oCZdCANCj4gZXhwZWN0IGEgY2hhbmdlIGluIHRoZSB1cGRhdGUgYXBwcm9hY2ggdGhpcyBs
YXRlIGluIHRoZSBwcm9jZXNzLCBidXQgSSBzdWdnZXN0IHRoYXQgZm9yIGZ1dHVyZSBkcmFmdHMg
cGVvcGxlIHRyeSB0byANCj4gYXZvaWQgY3JlYXRpbmcgdGhlIG5lZWQgZm9yIHRoZSBwcmUtMjAw
OCBib2lsZXJwbGF0ZS4NCg0KT2suIEkgd29uJ3QgZG8gYW55IGNoYW5nZXMgYXQgdGhpcyBwb2lu
dC4NCg0KLS0tDQoNCj4gLSBzZWN0aW9uIDgsIGZpcnN0IHBhcmFncmFwaCBhZnRlciBidWxsZXQg
bGlzdDogSeKAmW0gY29uZnVzZWQgYXMgdG8gd2hldGhlciB0aGlzIHRhbGtzIGFib3V0IHRoZSBp
bml0aWFsIG9mZmVyIG9yIGEgc3Vic2VxdWVudCANCj4gb2ZmZXIuIHRoZSBjb21tZW50IGFib3V0
IHRoZSDigJxwcmV2aW91c2x5IG5lZ290aWF0ZWQgU0RQIHBhcmFtZXRlcnPigJ0gc2VlbXMgdG8g
c3VnZ2VzdCB0aGUgbGF0dGVyLiBJIHN1c3BlY3QgdGhpcyBpcyBpbnRlbmRlZCANCj4gdG8gY292
ZXIgYWxsIG9mZmVycywgaW4gd2hpY2ggY2FzZSBpdCBuZWVkcyBjbGFyaWZpY2F0aW9uLg0KDQpJ
dCdzIHRoZSBvZmZlciBpbiB3aGljaCB0aGUgQlVORExFIGdyb3VwIGlzIGNyZWF0ZWQuIEkgbWF5
IGJlIHRoZSBpbml0aWFsIG9mZmVyIG9mIHRoZSBzZXNzaW9uLCBvciBpdCBtYXkgYmUgYSBzdWJz
ZXF1ZW50IG9mZmVyIHdpdGhpbiB0aGUgc2Vzc2lvbi4gSXQncyBpcnJlbGV2YW50IGFzIGZhciBh
cyBCVU5ETEUgaXMgY29uY2VybmVkLg0KDQpBbHNvIG5vdGUgdGhhdCBzZWN0aW9uIDIgZGVmaW5l
cyAiaW5pdGlhbCBvZmZlciIgYXMgdGhlIG9mZmVyIHdoZXJlIHRoZSBCVU5ETEUgZ3JvdXAgaXMg
Y3JlYXRlZDoNCg0KICAgIkluaXRpYWwgb2ZmZXI6IFRoZSBmaXJzdCBvZmZlciwgd2l0aGluIGFu
IFNEUCBzZXNzaW9uIChlLmcuIGEgU0lQDQogICBkaWFsb2cgd2hlbiB0aGUgU2Vzc2lvbiBJbml0
aWF0aW9uIFByb3RvY29sIChTSVApIFtSRkMzMjYxXSBpcyB1c2VkDQogICB0byBjYXJyeSBTRFAp
LCBpbiB3aGljaCB0aGUgb2ZmZXJlciBpbmRpY2F0ZXMgdGhhdCBpdCB3YW50cyB0byBjcmVhdGUN
CiAgIGEgZ2l2ZW4gQlVORExFIGdyb3VwLiINCg0KQnV0LCBpZiB3ZSB3YW50IHRvIG1ha2UgaXQg
Y2xlYXIgYWxzbyBpbiBTZWN0aW9uIDgsIEkgY291bGQgYWRkIHRoZSBmb2xsb3dpbmcgbm90ZToN
Cg0KIk5PVEU6IFRoZSBvZmZlciBpbiB3aGljaCB0aGUgb2ZmZXJlciBpbmRpY2F0ZXMgdGhhdCBp
dCB3YW50cyB0byBjcmVhdGUgYSBCVU5ETEUgZ3JvdXAgY2FuIGJlIHRoZSBpbml0aWFsIG9mZmVy
IG9mIHRoZSBzZXNzaW9uLCBvciBhIHN1YnNlcXVlbnQgb2ZmZXIgd2l0aGluIHRoZSBzZXNzaW9u
LiBBcyBkZWZpbmVkIGluIHNlY3Rpb24gMiwgd2l0aGluIHRoZSBzY29wZSBvZiB0aGlzIGRvY3Vt
ZW50IHRoZSBpbml0aWFsIG9mZmVyIGFsd2F5cyByZWZlcnMgdG8gdGhlIG9mZmVyIGluIHdoaWNo
IHRoZSBvZmZlcmVyIGluZGljYXRlcyB0aGF0IGl0IHdhbnRzIHRvIGNyZWF0ZSBhIEJVTkRMRSBn
cm91cCwgbm8gbWF0dGVyIHdoZXRoZXIgdGhhdCBvZmZlciBpcyB0aGUgaW5pdGlhbCBvZmZlciwg
b3IgYSBzdWJzZXF1ZW50IG9mZmVyLCB3aXRoaW4gdGhlIHNlc3Npb24uIg0KDQotLS0NCg0KPiAt
OC4zLjM6IElJVUMsIHRoZSBjcml0ZXJpYSBtZWFuIHRoYXQgdGhlIG9ubHkgbT0gc2VjdGlvbnMg
dGhhdCB0aGUgYW5zd2VyZXIgY2FuIG1vdmUgb3V0IG9mIHRoZSBidW5kbGUgYXJlIHRob3NlIHRo
YXQgDQo+IGhhdmUgdW5pcXVlIGFkZHJlc3NlcyBidXQgYXJlIG5vdCBsaXN0ZWQgZmlyc3QgaW4g
dGhlIGdyb3VwIGF0dHJpYnV0ZS4gSWYgdGhhdCBpcyBjb3JyZWN0LCBhIHNlbnRlbmNlIG9yIHR3
byB0byBzYXkgdGhhdCB3b3VsZCBiZSBoZWxwZnVsLg0KDQpBcyBsb25nIGFzIHRoZSBtPSBzZWN0
aW9uIGNvbnRhaW5zIGEgdW5pcXVlIGFkZHJlc3MgKGFuZCBkb2VzIG5vdCBjb250YWluIGEgYnVu
ZGxlLW9ubHkgYXR0cmlidXRlKSBpdCBjYW4gYmUgbW92ZWQgb3V0IG9mIGEgQlVORExFIGdyb3Vw
LCBubyBtYXR0ZXIgd2hlcmUgaXQgaXMgbGlzdGVkIGluIHRoZSBncm91cCBhdHRyaWJ1dGUuDQoN
Ci0tLQ0KDQo+IC04LjUsIGZpcnN0IHBhcmFncmFwaC4gSUlVQywgaXTigJlzIG5vdCBzeW50YWN0
aWNhbGx5IHBvc3NpYmxlIHRvIGFzc2lnbiBtb3JlIHRoYW4gb25lIG09IHNlY3Rpb24gdGhlIGJ1
bmRsZSBhZGRyZXNzLCBzaW5jZSBvbmx5IG9uZSANCj4gY2FuIGJlIGZpcnN0IGluIHRoZSBncm91
cCBhdHRyaWJ1dGUuIElmIHRoYXQgaXMgY29ycmVjdCwgdGhlIE1VU1QgaGVyZSBpcyBhIHN0YXRl
bWVudCBvZiBmYWN0LiBPciBhbSBJIG1pc3Npbmcgc29tZXRoaW5nPw0KDQpUaGVyZSBjYW4gb25s
eSBiZSBvbmUgZmlyc3QgaW4gdGhlIGdyb3VwIGF0dHJpYnV0ZSwgYnV0IHN5bnRhY3RpY2FsbHkg
eW91IGNvdWxkIGFzc2lnbiB0aGUgYnVuZGxlIGFkZHJlc3MgdmFsdWUgKElQIGFkZHJlc3MgYW5k
IHBvcnQpIHRvIG1vcmUgdGhhbiBvbmUgbT0gc2VjdGlvbi4NCg0KKEF0IHRoZSBlbmQgb2YgdGhl
IGRheSwgdGhlIHRhZyBpcyByZWFsbHkgb25seSByZWxldmFudCBpbiB0aGUgaW5pdGlhbCBvZmZl
ciwgd2hlcmUgeW91IG1heSBhc3NpZ24gbXVsdGlwbGUgZGlmZmVyZW50IHVuaXF1ZSBhZGRyZXNz
ZXMsIGFuZCB5b3Ugd2FudCB0byBpbmRpY2F0ZSB3aGljaCBvbmUgeW91IHdhbnQgdG8gdXNlIGFz
IGJ1bmRsZSBhZGRyZXNzLiBPbmNlIHRoZSBidW5kbGUgYWRkcmVzcyBoYXMgYmVlbiBuZWdvdGlh
dGVkLCB5b3Ugd29uJ3QgYXNzaWduIGFueSBvdGhlciBhZGRyZXNzZXMgdG8gYW4gb2ZmZXIpDQoN
Ci0tLQ0KDQo+IC05OiBUaGVyZSBhcmUgc2V2ZXJhbCBhc3NlcnRpb25zIHRoYXQgaW4gb3JkZXIg
dG8gZG8gc29tZXRoaW5nIHlvdSBNVVNUIGhhdmUgYSBzcGVjIHNheWluZyBob3cgdG8gZG8gaXQu
IEZvcm1hbGx5LCANCj4gSSB0aGluayB0aGUgcmVxdWlyZW1lbnQgaXMgcmVhbGx5IHRoYXQgeW91
IE1VU1QgTk9UIGRvIHRoYXQgdGhpbmcgdW5sZXNzIHN1Y2ggYSBzcGVjIGV4aXN0cy4gKDIxMTkv
ODE3NCBrZXl3b3JkcyBhcmUgbm9ybWFsbHkgYWJvdXQgaW1wbGVtZW50YXRpb24gYmVoYXZpb3Iu
KQ0KDQpJcyBpdCBvayBpZiBJIGtlZXAgdGhhdCBpbiBtaW5kIGZvciBteSBuZXh0IGRyYWZ0PyA6
KQ0KDQotLS0NCg0KPiAtMTAuMiwNCj4g4oCUIHBhcmFncmFwaCA3OiBXaGF0IGltcGxlbWVudGF0
aW9ucyBhcmUgd2UgdGFsa2luZyBhYm91dCB0aGF0IG1heSBub3QgZm9sbG93IHRoZSByZXF1aXJl
bWVudHMgdG8gaW5jbHVkZSB0aGUgdGFnIGluIA0KPiBSVFAvUlRDUD8gRWFybHkgaW1wbGVtZW50
YXRpb25zIG9mIHRoaXMgZHJhZnQ/IFNvbWV0aGluZyBlbHNlPyBBcyBpdCBpcywgaXQgc2VlbXMg
bGlrZSB3ZSBhcmUgdGFsa2luZyBhYm91dCBpbXBsZW1lbnRhdGlvbnMgDQo+IHRoYXQgZG8gbm90
IGZvbGxvdyB0aGlzIHNwZWMuIFRoYXQgbWFrZXMgdGhlIHN0YXRlbWVudCDigJwgIOKApiBJbiB0
aGlzIHNpdHVhdGlvbiwgZWFjaCAibT0iIHNlY3Rpb24gTVVTVCB1c2UgdW5pcXVlIHBheWxvYWQg
dHlwZSANCj4gdmFsdWVz4oCm4oCdIHByb2JsZW1hdGljLCBhcyBpdCBzZWVtcyB0byBiZSBwdXR0
aW5nIHJlcXVpcmVtZW50cyBvbiBpbXBsZW1lbnRhdGlvbnMgdGhhdCBkbyBub3QgZm9sbG93IHRo
aXMgZHJhZnQgaW4gdGhlIGZpcnN0IHBsYWNlLg0KDQpUaGVyZSB3ZXJlIGxvb29vb25nIGRpc2N1
c3Npb25zIGFib3V0IHRoaXMgc2VjdGlvbiwgYW5kIEknbGwgb3V0c291cmNlIHRoZSBxdWVzdGlv
biB0byBvdGhlcnMuIA0KDQpDdWxsZW4/IEVrcj8NCg0KPiDigJQgJyAgVGhlcmVmb3JlLCB3aGVu
IHByb2Nlc3NpbmcgYSBjb21wb3VuZCBwYWNrZXQsIGFueSBjb250YWluZWQgU0RFUyBwYWNrZXQg
TVVTVCBiZSBoYW5kbGVkIGZpcnN0Lg0KPiAgICAgIE5vdGUgdGhhdCB0aGlzIGlzIGEgY2hhbmdl
IGZyb20gW1JGQzM1NTBdIFNlY3Rpb24gNi4xIHdoaWNoDQo+ICAgICAgc3RhdGVzIHRoYXQgIkVh
Y2ggaW5kaXZpZHVhbCBSVENQIHBhY2tldCBpbiB0aGUgY29tcG91bmQgcGFja2V0DQo+ICAgICAg
bWF5IGJlIHByb2Nlc3NlZCBpbmRlcGVuZGVudGx5IHdpdGggbm8gcmVxdWlyZW1lbnRzIHVwb24g
dGhlIG9yZGVyDQo+ICAgICAgb3IgY29tYmluYXRpb24gb2YgcGFja2V0c+KAnS7igJkNCj4NCj4g
RG9lc27igJl0IHRoaXMgcmVxdWlyZSBhbiB1cGRhdGUgb2YgMzU1MD8gSXTigJlzIG5vdCBtZXJl
bHkgYSB0aWdodGVuaW5nIG9mIHJlcXVpcmVtZW50cywgaXTigJlzIGEgcmV2ZXJzYWwgb2YgZ3Vp
ZGFuY2UgZnJvbSB0aGF0IGRvY3VtZW50IHdoZW4gdXNlZCBpbiB0aGlzIGNvbnRleHQuDQoNCkhv
dyB3b3VsZCB3ZSB1cGRhdGUgMzU1MD8gQWRkaW5nIGEgc2VudGVuY2Ugc2F5aW5nICIsIHVubGVz
cyBhIHNwZWNpZmljIHVzYWdlIGRlZmluZXMgb3RoZXJ3aXNlIj8NCg0KSW4gbXkgb3BpbmlvbiBp
dCBpcyBhIHRpZ2h0ZW5pbmcgb2YgcmVxdWlyZW1lbnRzLiBCdXQsIGlmIG90aGVycyB0aGluayBv
dGhlcndpc2UgSSBkb24ndCBoYXZlIGFueSBzdHJvbmcgZmVlbGluZ3MuDQoNCi0tLQ0KDQo+IC0x
MC4zLjEuMywgbGFzdCBwYXJhZ3JhcGg6IFdoYXQgaXMgdGhlIGV4cGVjdGVkIGJlaGF2aW9yIHdo
ZW4gdGhhdCAicHJvdG9jb2wgZXJyb3IiIG9jY3Vycz8NCg0KSSBkb24ndCB0aGluayB3ZSBkb24n
dCBub3JtYWxseSBzcGVjaWZ5IHRoYXQgaW4gY2FzZXMgbGlrZSB0aGlzLCBiZWNhdXNlIGl0J3Mg
YW4gaW1wbGVtZW50YXRpb24gaXNzdWUuIEFuIGltcGxlbWVudGF0aW9uIG1heSB0cmlnZ2VyIGEg
bmV3IE8vQSBleGNoYW5nZSwgb3IgbWF5IHRlcm1pbmF0ZSB0aGUgd2hvbGUgc2Vzc2lvbiwgZXRj
IGV0Yy4NCg0KLS0tDQoNCj4gLTE1LjIsIGxhc3QgcGFyYWdyYXBoOiBJcyBpdCB3b3J0aCByZWNv
bW1lbmRpbmcgYWdhaW5zdCBwYXR0ZXJucyB3aGljaCBjb3VsZCBiZSB1c2VkIGFzIHBlcnNpc3Rl
bnQgaWRlbnRpZmllcnMsIGV2ZW4gaWYgDQo+IHRoZXkgZG9u4oCZdCBleHByZXNzbHkgaWRlbnRp
ZnkgYSBwZXJzb24gb3IgYXBwbGljYXRpb24/DQoNCldoYXQgd291bGQgdGhleSBpZGVudGl0eT8N
Cg0KSnVzdCBzYXlpbmcgIi4uLiwgb3IgY291bGQgYmUgdXNlZCBhcyBwZXJzaXN0ZW50IGlkZW50
aWZpZXJzIiBzb3VuZHMgYSBsaXR0bGUgaGFsZiBiYWtlZC4NCg0KLS0tDQoNCj4gLTE2LjM6IFBs
ZWFzZSB1c2UgdGhlIElFU0cgYW5kIOKAnGllc2dAaWV0Zi5vcmfigJ0gYXMgdGhlIGNvbnRhY3Qg
Zm9yIHRoZSBJQU5BIHJlZ2lzdHJhdGlvbnMuDQoNCldpbGwgZml4IGFzIHN1Z2dlc3RlZC4NCg0K
LS0tDQoNCj4gLTE3LCAybmQgcGFyYWdyYXBoOg0KPiDigJQgQWdhaW4sIGlzIGl0IHdvcnRoIG1l
bnRpb25pbmcgdGhlIHJpc2sgb2YgcGVyc2lzdGVudCBpZGVudGlmaWVycz8NCg0KU2VlIGFib3Zl
Lg0KDQo+4oCUICDigJzigKYgU0hPVUxEIGJlIDMgYnl0ZXMgb3IgbGVzcywgdG8gYWxsb3cgdGhl
bSB0byBlZmZpY2llbnRseSBmaXQgaW50byB0aGUgTUlEIFJUUCBoZWFkZXIgZXh0ZW5zaW9uLuKA
nQ0KPiBJdCBzZWVtcyBsaWtlIHRoYXQgcmVxdWlyZW1lbnQgYmVsb25ncyBpbiAxNS4yDQoNClNl
Y3Rpb24gMTUuMiBkb2VzIHNheSB0aGF0IHRoZSBsZW5ndGggc2hhbGwgYmUgMS0zIGJ5dGVzLiAN
Cg0KLS0tDQoNCj4gLTE3LCBsYXN0IHBhcmFncmFwaDogRG9lc27igJl0IHRoYXQgcmVxdWlyZSBh
biB1cGRhdGUgdG8gNzk0MQ0KDQpJZiBJIHJlbWVtYmVyIGNvcnJlY3RseSwgdGhlcmUgd2VyZSBs
b25nIGRpc2N1c3Npb25zIGFib3V0IHRoaXMsIGFuZCBpdCBpcyBvbmUgb2YgdGhlIHRoZS1SRkMt
aXMtY29ycmVjdC1idXQtbm90LWV2ZXJ5b25lLWltcGxlbWVudC10aGF0LXJlcXVpcmVtZW50IHRo
aW5ncy4uLg0KDQpDdWxsZW4/IEVrcj8NCg0KLS0tDQoNCj4gLTE4OiBXb3VsZCBpdCBtYWtlIHNl
bnNlIHRvIGhhdmUgb25lIG9mIHRoZSBleGFtcGxlcyB1c2UgbWVkaWEtbGV2ZWwgYz0gbGluZXM/
DQoNCkkgY2FuIGFkZCBhbiBleGFtcGxlLg0KDQotLS0NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXIN
Cg==


From nobody Sun Jan 21 11:35: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 EAB2F12D7E5; Sun, 21 Jan 2018 11:35:31 -0800 (PST)
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 ie46ZcaZBPJh; Sun, 21 Jan 2018 11:35:29 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16EF6127023; Sun, 21 Jan 2018 11:35:28 -0800 (PST)
X-AuditID: c1b4fb25-473ff7000000341b-ef-5a64eb7fbdce
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 77.C5.13339.F7BE46A5; Sun, 21 Jan 2018 20:35:27 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0352.000; Sun, 21 Jan 2018 20:35:26 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments
Thread-Index: AdOR9dB2bnAJi/LDSASEU4DilGGvkg==
Date: Sun, 21 Jan 2018 19:35:25 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C13312E@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.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUyM2K7qG7965Qog8dfhSzmd55mtzjx/hur xdTlj1kcmD2WLPnJ5DFr5xOWAKYoLpuU1JzMstQifbsEroxLd+8wFSxKqdhxeB57A+ONxC5G Tg4JAROJufvWs3UxcnEICRxmlLg4fSsjhLOEUWLLjlbWLkYODjYBC4nuf9ogcRGBzYwSL6+d ZQPpFhZIkzh+fi8jiC0ikC4x8fxKdghbT2L9rF9gcRYBVYnzs1vBbF4BX4mvq1vAehkFxCS+ n1rDBGIzC4hL3HoynwniIgGJJXvOM0PYohIvH/9jhbCVJFZsv8QIcg+zgKbE+l36EK2KElO6 H7JDjBeUODnzCcsERqFZSKbOQuiYhaRjFpKOBYwsqxhFi1OLk3LTjYz1Uosyk4uL8/P08lJL NjECw/zglt+qOxgvv3E8xCjAwajEw3vpWkqUEGtiWXFl7iFGCQ5mJRHeaXlAId6UxMqq1KL8 +KLSnNTiQ4zSHCxK4rwnPXmjhATSE0tSs1NTC1KLYLJMHJxSDYxtvWddNoeHKevv7w/X426w 3fm80ewYW19VzFUmG51ntb8efZyV+2SriMCKrP9SdxdOq7NyWWb8//oLW5P7GQqr7t5XTZIu Pf16pad+74a3blm+tUbi27qd4hb9l5uw8u1vQcn8NJF+zmLboOLIkAr1dQti1vwIntD9ISky KbbT3NNd6or4FSWW4oxEQy3mouJEAL4S3mxvAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/FXiEm6_cFhEs4YmljNWr1y4cLTI>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments
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, 21 Jan 2018 19:35:32 -0000

SGksDQoNCkluIHRoaXMgcmVwbHkgSSBhZGRyZXNzIHRoZSBlZGl0b3JpYWwgY29tbWVudHMuIFBs
ZWFzZSBzZWUgaW5saW5lLg0KDQoqKiogRWRpdG9yaWFsIENvbW1lbnRzIGFuZCBuaXRzICoqKg0K
DQotLS0NCg0KPiAtIFRlcm1pbm9sb2d5IGlzc3VlczogSSB0aGluayBzb21lIG9mIHRoZSB0ZXJt
aW5vbG9neSBoZXJlIHdpbGwgY29uZnVzZSByZWFkZXJzIHdobyBhcmUgbmV3IHRvIHRoZSBjb25j
ZXB0cy4gDQo+IEluIHBhcnRpY3VsYXIsIElJVUMsIOKAnGJ1bmRsZSBhZGRyZXNz4oCdIG1lYW5z
IGFkZHJlc3MgKyBwb3J0LiBJIHRoaW5rIG1hbnkgcmVhZGVycyB3aWxsIGZhbGwgYmFjayB0byBh
c3N1bWluZyB0aGF0IA0KPiBhZGRyZXNzIG1lYW5zIElQIGFkZHJlc3MuIChFc3BlY2lhbGx5IHdo
ZW4gd2UgdGFsayBhYm91dCBhIOKAnHVuaXF1ZSBhZGRyZXNz4oCdIGFzc2lnbmVkIHRvIGFuIG09
IHNlY3Rpb24sIHdoZW4gDQo+IG11Y2ggb2YgdGhlIHRpbWUgdGhhdCBtYXkganVzdCBtZWFuIGEg
dW5pcXVlIHBvcnQuKQ0KDQpTZWN0aW9uIDIgZG9lcyBkZWZpbmUgImJ1bmRsZSBhZGRyZXNzIiBh
cyBhbiBhZGRyZXNzOnBvcnQgY29tYmluYXRpb24uDQoNCkJ1dCwgSSBzZWUgeW91ciBwb2ludC4N
Cg0KV291bGQgImJ1bmRsZSBhZGRyZXNzLXBvcnQiLCAiYnVuZGxlIGFkZHJlc3Nwb3J0IiwgImJ1
bmRsZSBhZGRycHJ0Iiwgb3Igc29tZXRoaW5nIHNpbWlsYXIsIGJlIGJldHRlcj8gSSBkb24ndCB3
YW50IHRvIHNheSAiYnVuZGxlIGFkZHJlc3M6cG9ydCBjb21iaW5hdGlvbiIgaW4gZXZlcnkgaW5z
dGFuY2UuLi4NCg0KLS0tDQoNCj4gSSBhbHNvIGZpbmQgZGVmaW5pbmcgdGhlIHRlcm0g4oCcQnVu
ZGxlIFRhZ+KAnSB0byBtZWFuIHRoZSBmaXJzdCB0YWcgaW4gdGhlIGxpc3QgdG8gYmUgY29uZnVz
aW5nLiBJdCBtYXkgYmUgZWFzaWVyIHRvIGp1c3QgcmVmZXIgdG8gdGhlIOKAnGZpcnN0IHRhZyBp
biB0aGUgZ3JvdXAgbGlzdOKAnS4NCg0KQWdhaW4sIHNlY3Rpb24gMiBkb2VzIGRlZmluZSB0aGUg
bWVhbmluZy4NCg0KLS0tDQoNCj4g4oCUIEV4YW1wbGVzOiBBbnkgY2hhbmNlIG9mIHNvbWUgb2Yg
dGhlIGV4YW1wbGVzIHNob3dpbmcgSVB2Nj8gSSBzdXNwZWN0IGl04oCZcyBhIHRyaXZpYWwgY2hh
bmdlIGZvciBhdCBsZWFzdCBzb21lIGV4YW1wbGVzLCBzaW5jZSB0aGV5IHVzZSBkb21haW4gbmFt
ZXMuDQoNCkkgY2FuIGRvIHRoYXQuDQoNCi0tLQ0KDQo+IC1hYnN0cmFjdDogVGhlIGFic3RyYWN0
IHNlZW1zIGxvbmdlciBhbmQgbW9yZSBkZXRhaWxlZCB0aGFuIHN0cmljdGx5IG5lY2Vzc2FyeS4g
VGhlIGZpcnN0IHR3byBzZW50ZW5jZXMgYWxvbmcgd2l0aCBhIGJyaWVmIG1lbnRpb24gDQo+IG9m
IHRoZSB1cGRhdGUgdG8gMzI2NCBhbmQgdGhlIFNERVMgaXRlbS9SVFAgaGVhZGVyIGV4dGVuc2lv
biB3b3VsZCBiZSBzdWZmaWNpZW50Lg0KDQpUaGF0J3MgZmluZSB3aXRoIG1lLg0KDQpJIGRvIGtu
b3cgdGhhdCBwZW9wbGUgcmVxdWVzdGVkIGNlcnRhaW4gdGhpbmdzIHRvIGJlIGluIHRoZSBBYnN0
cmFjdCwgYnV0IEkgYXNzdW1lIHRoZXkgd2lsbCBzcGVhayB1cCBpZiB0aGV5IHRoaW5rIHNvbWV0
aGluZyBzaG91bGQgYmUga2VwdC4gDQoNCi0tLQ0KDQo+IC1TZWN0aW9uIDEsDQo+IOKAlCBmaXJz
dCBwYXJhZ3JhcGg6IFRoaXMgc29ydCBvZiBqdW1wcyBpbnRvIHRoaW5ncyB3aXRob3V0IG11Y2gg
Y29udGV4dC4gKGUuZy4gdGhhdCB3ZSBhcmUgdGFsa2luZyBhYm91dCBtZWRpYSANCj4gc2Vzc2lv
bnMgc2lnbmFsZWQgdXNpbmcgU0RQIG9mZmVyL2Fuc3dlci7igJ0NCg0KSSBjb3VsZCBzYXk6DQoN
CiJXaGVuIHRoZSBTRFAgb2ZmZXIvYW5zd2VyIG1lY2hhbmlzbSBbUkZDMzI2NF0gaXMgdXNlZCB0
byBuZWdvdGlhdGUgdGhlIGVzdGFibGlzaG1lbnQgb2YgbXVsdGltZWRpYSANCmNvbW11bmljYXRp
b24gc2Vzc2lvbnMsIGlmIHNlcGFyYXRlIHRyYW5zcG9ydHMgKDUtdHVwbGVzKSBhcmUgbmVnb3Rp
YXRlZCBmb3IgZWFjaCBpbmRpdmlkdWFsIG1lZGlhIHN0cmVhbSwNCmVhY2ggdHJhbnNwb3J0IGNv
bnN1bWVzIGFkZGl0aW9uYWwgcmVzb3VyY2VzIChlc3BlY2lhbGx5IHdoZW4gSW50ZXJhY3RpdmUg
Q29ubmVjdGl2aXR5IEVzdGFibGlzaG1lbnQNCihJQ0UpIFtJLUQuaWV0Zi1pY2UtcmZjNTI0NWJp
c10gaXMgdXNlZCkuICBGb3IgdGhpcyByZWFzb24sIGl0IGlzIGF0dHJhY3RpdmUgdG8gdXNlIGEg
c2luZ2xlIHRyYW5zcG9ydCBmb3IgbXVsdGlwbGUgDQptZWRpYSBzdHJlYW1zLiINCg0KPiBzL2Nv
bnN1bWUvY29uc3VtZXMNCg0KV2lsbCBiZSBmaXhlZCBhcyBzdWdnZXN0ZWQuDQoNCj4g4oCUIHBh
cmFncmFwaHMgNS05OiBNb3N0IG9mIHRoZSBpbnN0YW5jZXMgb2YgdGhlIHdvcmQg4oCcYWxzb+KA
nSBhcmUgdW5uZWVkZWQuDQoNCkkgY2FuIHJlbW92ZSB0aGVtIHRoZSB1bm5lZWRlZCBvbmVzLg0K
DQo+IOKAlCBwYXJhZ3JhcGhzIDcgYW5kIDk6IFRoZXNlIHBhcmFncmFwaHMgYm90aCB0YWxrIGFi
b3V0IHVwZGF0ZXMgdG8gMzI2NDsgaXQgd291bGQgYmUgYmV0dGVyIHRvIGtlZXAgdGhlbSB0b2dl
dGhlci4NCg0KSSB0aGluayB0aGV5IGNhbiBiZSBjb21iaW5lZCBpbnRvIGEgc2luZ2xlIHBhcmFn
cmFwaC4NCg0KPiDigJQgMm5kIHRvIGxhc3QgcGFyYWdyYXBoLCDigJxUaGUgcHJvY2VkdXJlcyBp
biB0aGlzIHNwZWNpZmljYXRpb24gYXBwbHkgaW5kZXBlbmRlbnRseSB0byBhIGdpdmVuIEJVTkRM
RSBncm91cC7igJ0gOiBJIGRvbuKAmXQgDQo+IHVuZGVyc3RhbmQgd2hhdCB0aGF0IHNlbnRlbmNl
IGlzIHRyeWluZyB0byBjb252ZXkuDQoNCkkgc2F5cyB0aGF0LCBpZiB5b3VyIFNEUCBjb250YWlu
cyBtdWx0aXBsZSBCVU5ETEUgZ3JvdXBzLCB0aGUgcHJvY2VkdXJlcyBhcmUgYXBwbGllZCBpbmRl
cGVuZGVudGx5IHRvIGVhY2ggb2YgdGhlbS4NCg0KLS0tDQoNCj4gLSBTZWN0aW9uIDI6IFRoZSB0
ZXJtaW5vbG9neSBsaXN0IHdvdWxkIGJlIG1vcmUgcmVhZGFibGUgYXMgYSBidWxsZXQgbGlzdCBv
ciBoYW5naW5nIGluZGVudCBsaXN0Lg0KDQpJIHdpbGwgZml4IHRoYXQuDQoNCi0tLQ0KDQo+IC0z
OiBUaGVyZSBhcmUgYXQgbGVhc3Qgb25lIGxvd2VyIGNhc2Ug4oCcbXVzdOKAnSBhbmQgYSBudW1i
ZXIgb2YgbG93ZXIgY2FzZSDigJxzaG91bGRz4oCdLiBQbGVhc2UgY29uc2lkZXIgDQo+IHVzaW5n
IHRoZSBib2lsZXJwbGF0ZSBmcm9tIFJGQyA4MTc0LCBvciB2ZXJpZnkgdGhhdCB0aGUgbG93ZXIg
Y2FzZSB2ZXJzaW9ucyBhcmUgbm90IGludGVuZGVkIHRvIGJlIGtleXdvcmRzLg0KDQpJIGZvdW5k
IGEgY291cGxlIG9mICJtdXN0IiBpbnN0YW5jZXMuIEJvdGggc2hhbGwgYmUgdXBwZXIgY2FzZS4N
Cg0KVGhlcmUgYXJlIDYtNyAic2hvdWxkIiBpbnN0YW5jZXMsIGFuZCBpdCBzZWVtcyBhbGwgb2Yg
dGhlbSBjYW4gYmUgbW9kaWZpZWQgdG8gbm9uLWtleXdvcmRzLg0KDQotLS0NCg0KPiAtNToNCj4g
4oCUIEZpcnN0IHBhcmFncmFwaDogaW5jb25zaXN0ZW50IHRlbnNlLiBQbGVhc2UgY29uc2lkZXIg
cy8g4oCcIOKApiBzZWN0aW9uIHdpbGwgdXNlIOKApuKAnSAvIOKAnOKApiBzZWN0aW9uIHVzZXPi
gKbigJ0NCg0KSSB3aWxsIGZpeCBhcyBzdWdnZXN0ZWQuDQoNCj4g4oCUIDJuZCBwYXJhZ3JhcGg6
IFRoZSBjaXRhdGlvbiB0byBSRkM1ODg4IGxvb2tzIGxpa2UgYSByZWZlcmVuY2UgZm9yIHRoZSDi
gJxCVU5ETEXigJ0gc2VtYW50aWMgdmFsdWUsIHJhdGhlciB0aGFuDQo+IGZvciB0aGUgZ3JvdXBp
bmcgZnJhbWV3b3JrLiBQbGVhc2UgY29uc2lkZXIgc29tZXRoaW5nIHRvIHRoZSBlZmZlY3Qgb2Yg
dGhlIGZvbGxvd2luZzoNCj4gT0xEOg0KPiAgICAgIFRoZSBCVU5ETEUgZXh0ZW5zaW9uIGlzIGlu
ZGljYXRlZCB1c2luZyBhbiBTRFAg4oCZZ3JvdXDigJkgYXR0cmlidXRlIHdpdGggYSAiQlVORExF
IiBzZW1hbnRpY3MgdmFsdWUgW1JGQzU4ODhdLg0KPiBORVc6DQo+ICAgICBUaGUgQlVORExFIGV4
dGVuc2lvbiBpcyBpbmRpY2F0ZWQgdXNpbmcgYW4gU0RQIOKAmWdyb3Vw4oCZIGF0dHJpYnV0ZSB3
aXRoIGEgc2VtYW50aWNzIHZhbHVlIFtSRkM1ODg4XSBvZiAiQlVORExF4oCdLg0KDQpJIHdpbGwg
Zml4IGFzIHN1Z2dlc3RlZC4NCg0KLS0tDQoNCj4gLSBTZWN0aW9uIDguMToNCj4g4oCUIENvbnNp
ZGVyIG1vdmluZyB0aGlzIHNlY3Rpb24gdG8gbGF0ZXIgaW4gdGhlIG9mZmVyL2Fuc3dlciBkZXRh
aWxzLiBJIHRoaW5rIGl0IHdvdWxkIGJlIGVhc2llciBmb3IgYSByZWFkZXIgdG8gDQo+IHVuZGVy
c3RhbmQgdGhpcyBzZWN0aW9uIGFmdGVyIHRoZXkgaGF2ZSBzb21lIG1vcmUgZ2VuZXJhbCBjb250
ZXh0Lg0KDQpUaGUgcmVhc29uIGl0IGlzIGluIHRoZSBiZWdpbm5pbmcgaXMgYmVjYXVzZSBpdCBp
cyBwYXJ0IG9mIHRoZSBnZW5lcmljIHByb2NlZHVyZXMuDQoNCldvdWxkIHlvdSBsaWtlIHRvIHBs
YWNlIGl0IGF0IHRoZSBlbmQgb2YgU2VjdGlvbiA4Pw0KDQo+IOKAlCBUaXRsZTogU3BlbGwgb3V0
IOKAnE11bHRpcGxleOKAnSBpbiB0aGUgdGl0bGUuDQoNCkkgd2lsbCBmaXggYXMgc3VnZ2VzdGVk
Lg0KDQo+IOKAlCBGaXJzdCBQYXJhZ3JhcGg6IFRoZSB3b3JkaW5nIGNvdWxkIGJlIHRha2VuIHRv
IG1lYW4gdGhhdCBhbGwgYXR0cmlidXRlcyB3aXRoIGEgbXV4IGNhdGVnb3J5IG9mIA0KPiBJREVO
VElDQUwgb3IgVFJBTlNQT1JUIG11c3QgYmUgaW5jbHVkZWQgaW4gdGhlIGZpcnN0IHBsYWNlLiBJ
IHRoaW5rIHRoZSBwb2ludCBpcyB0aGF0LCBpZiB0aGV5IGFyZSANCj4gcHJlc2VudCwgdGhleSBt
dXN0IGJlIGluY2x1ZGVkIGluIGVhY2ggbT0gc2VjdGlvbi4gSSBzdWdnZXN0IHNvbWV0aGluZyBs
aWtlIHRoZSBmb2xsb3dpbmc6DQo+IE9MRDoNCj4gICAg4oCmIElERU5USUNBTCBhbmQgVFJBTlNQ
T1JUIG11eCBjYXRlZ29yeSBTRFAgYXR0cmlidXRlcyBNVVNUIGV4cGxpY2l0bHkgYmUgaW5jbHVk
ZWQgaW4gZWFjaCANCj4gYnVuZGxlZCAibT3igJwgc2VjdGlvbiAuLi4NCj4gTkVXOg0KPiAgICDi
gKYgQW55IElERU5USUNBTCBhbmQgVFJBTlNQT1JUIG11eCBjYXRlZ29yeSBTRFAgYXR0cmlidXRl
cyBpbmNsdWRlZCBpbiB0aGUgQlVORExFIGdyb3VwIA0KPiBNVVNUIGV4cGxpY2l0bHkgYmUgaW5j
bHVkZWQgaW4gZWFjaCBidW5kbGVkICJtPeKAnCBzZWN0aW9uIOKApg0KDQpJIHdpbGwgZml4IGFz
IHN1Z2dlc3RlZC4NCg0KLS0tDQoNCj4gLTguMi4xLCBmaXJzdCBwYXJhZ3JhcGg6DQo+IOKAlCBU
aGUgcGhyYXNlIOKAnHJlcHJlc2VudGVkIGJ5IHRoZSDigKYgQlVORExFLXRhZ+KAnSBvY2N1cnMg
cmVwZWF0ZWRseSB0aHJvdWdob3V0IHRoZSBkb2N1bWVudC4gVGhlIHVzZSBvZiDigJxyZXByZXNl
bnRlZOKAnSB0aGVyZSANCj4gc2VlbXMgYXdrd2FyZC4gSSB0aGluayDigJxpbmRpY2F0ZWTigJ0g
d291bGQgYmUgYSBiZXR0ZXIgd29yZCBjaG9pY2UuDQoNClRoaXMgaXMgb25lIG9mIHRoZSB3b3Jk
cyB0aGF0IGhhdmUgYmVlbiBjaGFuZ2VkIG11bHRpcGxlIHRpbWVzIHRocm91Z2hvdXQgdGhlIHdv
cmsgb2YgdGhlIGRvY3VtZW50Li4uDQoNCkkgY2FuIHNlZSB3aGV0aGVyIHlvdXIgc3VnZ2VzdGlv
biBjYW4gYmUgZG9uZSB3aXRoIGEgc2VhcmNoL3JlcGxhY2UsIGJ1dCBpZiBpdCByZXF1aXJlcyBt
b3JlIHRoYW4gdGhhdCBJIHdvdWxkIG5vdCBsaWtlIHRvIGRvIGl0Lg0KDQo+IOKAlCBzaG91bGQg
4oCcb2ZmZXJlciBCVU5ETEUgYWRkcmVzc+KAnSBiZSDigJxvZmZlcmVyIHN1Z2dlc3RlZCBCVU5E
TEUgYWRkcmVzc+KAnT8NCg0KWWVzLiBJIHdpbGwgZml4IGFzIHN1Z2dlc3RlZC4NCg0KLS0tDQoN
Cj4gLTguNS4yOiBTaG91bGQg4oCcYWRkIGEgYnVuZGxlZCBtPSBzZWN0aW9u4oCdIGJlIOKAnGFk
ZCBhIF9uZXdfIGJ1bmRsZWQgbT0gc2VjdGlvbuKAnT8NCg0KWWVzLiBJIHdpbGwgZml4IGFzIHN1
Z2dlc3RlZC4NCg0KLS0tDQoNCj4gLTk6DQo+IOKAlCBmaXJzdCBwYXJhZ3JhcGg6IOKAnCDigKYg
ZGlmZmVyZW50IHByb3RvY29scyBvbiB0b3Agb2YgdGhlIHRyYW5zcG9ydC1sYXllciBwcm90b2Nv
bCDigKbigJ0NCj4gVXBwZXIgbGF5ZXIgcHJvdG9jb2xzPw0KDQpZZXMuIFdpbGwgZml4IGFzIHN1
Z2dlc3RlZC4NCg0KPiDigJQgTGFzdCBwYXJhZ3JhcGg6IFRoaXMgcGFyYWdyYXBoIHNlZW1zIG1v
c3RseSAob3IgZW50aXJlbHkpIHJlZHVuZGFudCB0byBzZWN0aW9uIDkuMS4NCg0KVGhlIHRleHQg
Z2l2ZXMgYW4gb3ZlcnZpZXcgb2Ygd2hhdCBpcyBkb25lIGluIHRoaXMgZG9jdW1lbnQsIGFuZCB3
aGF0IG5lZWRzIHRvIGJlIGRvbmUgZWxzZXdoZXJlLiBJJ2QgbGlrZSB0byBrZWVwIGl0Lg0KDQot
LS0NCg0KLTEwLjI6DQoNCj4g4oCUICIgUlRDUCBwYWNrZXRzIGZvciB3aGljaCBubyBhcHByb3By
aWF0ZSAibT0iIHNlY3Rpb24gY2FuIGJlIGlkZW50aWZpZWQNCj4gICAgTVVTVCBiZSBwcm9jZXNz
ZWQgYXMgdXN1YWwgYnkgdGhlIFJUUCBsYXllciwgdXBkYXRpbmcgdGhlIG1ldGFkYXRhDQo+ICAg
YXNzb2NpYXRlZCB3aXRoIHRoZSBjb3JyZXNwb25kaW5nIFJUUCBzdHJlYW1zLCBidXQgYXJlIG5v
dCBwYXNzZWQgdG8NCj4gICBhbnkgIm09IiBzZWN0aW9uLuKAnQ0KPg0KPiBJIGRvbuKAmXQgdGhp
bmsgdGhpbmdzIGdldHMgcGFzc2VkIHRvIHNlY3Rpb25zIG9mIFNEUC4gV2hhdCBkb2VzIHRoaXMg
cmVhbGx5IHRhbGsgYWJvdXQ/DQoNClRoaXMgaXMgYW5vdGhlciB0aGluZyB0aGF0IGl0IHRvb2sg
Zm9yZXZlciB0byBhZ3JlZSB1cG9uLiBUaGUgaWRlYSB3YXMgdG8gdXNlIGRpZmZlcmVudCAibGF5
ZXJzIiB3aGVuIHByb2Nlc3NpbmcgcmVjZWl2ZWQgUlRQL1JUQ1AgcGFja2V0cy4NCg0KSG93ZXZl
ciwgSSBkbyBhZ3JlZSB0aGF0IHRoZSB0ZXh0IGlzIGEgbGl0dGxlIGNvbmZ1c2luZy4NCg0KUGVy
aGFwcyBzb21ldGhpbmcgbGlrZToNCg0KICAgIlJUQ1AgcGFja2V0cyB0aGF0IGNhbm5vdCBiZSBh
c3NvY2lhdGVkIHdpdGggYW4gYXBwcm9wcmlhdGUgIm09IiBzZWN0aW9uIA0KICAgTVVTVCBzdGls
bCBiZSBwcm9jZXNzZWQgYXMgdXN1YWwgYnkgdGhlIFJUUCBsYXllciwgdXBkYXRpbmcgdGhlIG1l
dGFkYXRhDQogICBhc3NvY2lhdGVkIHdpdGggdGhlIGNvcnJlc3BvbmRpbmcgUlRQIHN0cmVhbXMu
Ig0KDQouLi5hbmQgaW4gdGhlIHByaW9yIHBhcmFncmFwaDoNCg0KICAgIkZvciBlYWNoIFJUQ1Ag
cGFja2V0IHJlY2VpdmVkIChpbmNsdWRpbmcgZWFjaCBSVENQIHBhY2tldCB0aGF0IGlzDQogICBw
YXJ0IG9mIGEgY29tcG91bmQgUlRDUCBwYWNrZXQpLCB0aGUgcGFja2V0IGlzIHByb2Nlc3NlZCBh
cyB1c3VhbCBieQ0KICAgdGhlIFJUUCBsYXllciwgdGhlbiBhc3NvY2lhdGVkIHdpdGggdGhlIGFw
cHJvcHJpYXRlICJtPSIgc2VjdGlvbnMsIGFuZA0KICAgcHJvY2Vzc2VkIGZvciB0aGUgUlRQIHN0
cmVhbXMgcmVwcmVzZW50ZWQgYnkgdGhvc2UgIm09IiBzZWN0aW9ucy4iDQoNCj4g4oCUIOKAnCBS
dWxlcyBmb3IgYWRkaXRpb25hbCBwcm9jZXNzaW5nIG9mIHRoZSB2YXJpb3VzIHR5cGVzIG9mIFJU
Q1AgcGFja2V0cw0KPiAgIGFyZSBleHBsYWluZWQgYmVsb3cu4oCdDQo+DQo+IFNob3VsZCB0aGF0
IHNheSDigJxBZGRpdGlvbmFsIHJ1bGVzIGZvciBwcm9jZXNzaW5n4oCm4oCdPw0KDQpZZXMuIEkg
d2lsbCBmaXggYXMgc3VnZ2VzdGVkLg0KDQotLS0NCg0KPiAtMTEsIDJuZCBidWxsZXQ6ICIgcHJl
dmlvdXNseSBzZWxlY3RlZCBbU2VjdGlvbiA4LjMuMSBdIG9yIG5ldyBzdWdnZXN0ZWQgWyBTZWN0
aW9uIDguNS4xXeKAnQ0KPiBzL25ldy9uZXdseQ0KDQpXaWxsIGZpeCBhcyBzdWdnZXN0ZWQuDQoN
Cj4g4oCUIGxhc3QgcGFyYWdyYXBoOiBJdCBtYXkgYmUgd29ydGggY2xhcmlmeWluZyB0aGF0IHRo
aXMgZG9lc24ndCBjaGFuZ2UgYW55IHJlcXVpcmVtZW50IHNwZWNpZmllZCBieSB0aGUgDQo+IGFw
cGxpY2F0aW9uIG9yIHNpZ25hbGluZyBwcm90b2NvbC4gRm9yIGV4YW1wbGUsIFdlYlJUQyBzdGls
bCByZXF1aXJlcyBJQ0UgZXZlbiB0aG91Z2ggYnVuZGxlIGlzIHVzZWQuDQoNClF1ZXN0aW9uIGZv
ciBjbGFyaWZpY2F0aW9uOiBEbyB5b3Ugd2FudCB0byBzYXkgdGhhdCBzb21lIGFwcGxpY2F0aW9u
cyBtaWdodCBtYW5kYXRlIElDRSBldmVuIGlmIEJVTkRMRSBpcyBub3QgdXNlZCwgb3IgdGhhdCBz
b21lIGFwcGxpY2F0aW9ucyBtaWdodCBtYW5kYXRlIHN1cHBvcnQgb2YgSUNFIHRvZ2V0aGVyIHdp
dGggQlVORExFPw0KDQotLS0NCg0KPiAxMS4xOg0KPiDigJQgMm5kIHBhcmFncmFwaDog4oCcIHBy
ZXZpb3VzbHkgc2VsZWN0ZWQgb3IgbmV3IHN1Z2dlc3RlZCDigJwgcy9uZXcvbmV3bHkNCg0KV2ls
bCBmaXggYXMgc3VnZ2VzdGVkLg0KDQo+IOKAlCAzcmQgcGFyYWdyYXBoOiBDb25zdHJ1Y3Qgb2Yg
dGhlIGZvcm0gb2Yg4oCcTVVTVCBvbmx54oCdIGNhbiBiZSBhbWJpZ3VvdXMuIFBsZWFzZSBjb25z
aWRlciByZXN0YXRpbmcgDQo+IGluIHRoZSBmb3JtIG9mIGEgTVVTVCBOT1QgY29uc3RydWN0aW9u
LiAoRm9yIGV4YW1wbGUsIOKAnE1VU1Qgb25seSBkbyBmb28gd2hlbuKApi7igJ0gY2FuIGJlIGlu
dGVycHJldGVkIA0KPiBhcyDigJxNVVNUIE5PVCBkbyBmb28gdW5sZXNz4oCm4oCdIG9yIOKAnE1V
U1QgTk9UIGRvIGFueXRoaW5nIGJ1dCBmb28gd2hlbuKApuKAnSAgIFtOb3RlOiBUaGlzIGNvbnN0
cnVjdCByZXBlYXRzIA0KPiBzZXZlcmFsIHRpbWVzIGluIHRoZSBuZXh0IGZldyBzZWN0aW9ucy4g
XQ0KDQpXaGF0IGFib3V0Pw0KIA0KICAgIldoZW4gYW4gYW5zd2VyZXIgYXNzaWducyBhIEJVTkRM
RSBhZGRyZXNzIHRvIGFuICJtPSIgc2VjdGlvbiB3aXRoaW4gYQ0KICAgQlVORExFIGdyb3VwICh0
aGUgIm09IiBzZWN0aW9uIHJlcHJlc2VudGVkIGJ5IHRoZSBhbnN3ZXJlciBCVU5ETEUtDQogICB0
YWcpLCB0aGUgYW5zd2VyZXIgb25seXMgaW5jbHVkZSBTRFAgJ2NhbmRpZGF0ZScgYXR0cmlidXRl
cyAoYW5kDQogICBvdGhlciBhcHBsaWNhYmxlIElDRS1yZWxhdGVkIG1lZGlhLWxldmVsIFNEUCBh
dHRyaWJ1dGVzKSBpbiB0aGF0ICJtPSINCiAgIHNlY3Rpb24sIGZvbGxvd2luZyB0aGUgcHJvY2Vk
dXJlcyBpbiBTZWN0aW9uIDguMS4gVGhlIGFuc3dlcmVyIE1VU1QgTk9UDQogICBpbmNsdWRlIElD
RS1yZWxhdGVkIG1lZGlhLWxldmVsIFNEUCBhdHRyaWJ1dGVzIGluIGFueSBvdGhlciAibT0iIHNl
Y3Rpb25zLiINCg0KLS0tDQoNCj4gLTE5LCAzcmQgcGFyYWdyYXBoIGZyb20gZW5kOiBJdOKAmXMg
c2VlbXMgYSBiaXQgb2RkIHRvIHRoYW5rIGEgY28tYXV0aG9yIChDdWxsZW4pIGZvciB0ZXh0IGNv
bnRyaWJ1dGlvbnMgOi0pDQoNCk9rLCBJIHdpbGwgcmVtb3ZlIGhpbSBmcm9tIHNlY3Rpb24gMTkg
OikNCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg==


From nobody Tue Jan 23 19:45:53 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 96A7312D880; Tue, 23 Jan 2018 19:45:39 -0800 (PST)
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.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151676553958.24137.4237678593782258786@ietfa.amsl.com>
Date: Tue, 23 Jan 2018 19:45:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/wSHIpOyfwYWgL_aVjBiPYj_XcAk>
Subject: [MMUSIC] Genart last call review of draft-ietf-mmusic-trickle-ice-sip-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: Wed, 24 Jan 2018 03:45:40 -0000

Reviewer: Dale Worley
Review result: Ready with Issues

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.

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]

Summary:

       This draft is on the right track but has open issues, described
       in the review.

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.

** Global/major issues:

* The tokens "end-of-candidate" and "end-of-candidates" seem to be used
equivalently in this document, with the following number of uses:

     11 end-of-candidate
     19 end-of-candidates

Which is the correct form?

* The definition of application/trickle-ice-sdpfrag describes the use of
"a=charset" as an attribute, but the grammar of sdpfrag in section 9
does not permit that attribute.

* Deployment considerations (section 11)

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= lines of the initial offer or
answer, or if Trickle ICE INFO requests fail, eventually amend the
addresses to be globally routable addresses.

But the WG may have more knowledge about this situation.

* There are various locations where the language has usages that seem to
me to be excessively informal or prolix.  Cases I've noticed are:

2.  Terminology

   It is assumed that the reader will be
   familiar with the terminology from both documents.

Probably s/will be/is/.

3.1.  Discovery issues

   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.

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 expect the RFC Editor can give guidance on this subject.

** Detailed/editorial/nits:

       A Session Initiation Protocol (SIP) usage for Trickle ICE
                  draft-ietf-mmusic-trickle-ice-sip-12

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.)

Abstract

   This document defines usage semantics for Trickle ICE with the
   Session Initiation Protocol (SIP) and defines a new SIP Info Package.

Perhaps /a new SIP Info Package/a new SIP Info Package to support this
usage/.

Table of Contents

The capitalization of section titles seems to be inconsistent.

1.  Introduction

   It describes how ICE candidates
   are to be exchanged incrementally with SIP INFO requests [RFC6086]

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.

4.  Incremental Signaling of ICE candidates

   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).

I think you want to change "Offers/Answers" to "Offer/Answer".

4.3.1.  Establishing dialog state through reliable Offer/Answer delivery

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:

                   Alice                         Bob
                     |                            |
                     |     INVITE (Offer)         |
                     |     Supported: trickle-ice |
                     |--------------------------->|
                     |     183 (Answer)           |
                     |     Supported: trickle-ice |
                     |<---------------------------|

and similarly in later figures.

Something similar might be done with the "SRFLX Cand." elements to
make the figures less cramped.

4.3.2.  Establishing dialog state through unreliable Offer/Answer

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

Strictly, "a trickle-ice INFO request", as other INFO requests might
be received as part of other mechanisms.

4.3.4.  Considerations for Third Party Call Control

   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).

s/they receive/it receives/

4.4.  Delivering candidates in INFO messages

   Agents MUST include a pseudo "m=" line and an identification tag in a
   "a=mid:" attribute for every "m=" line whose candidate list they
   intend to update.  Such "a=mid:" attributes MUST immediately precede
   the list of candidates for that specific "m=" line.  All
   "a=candidate" or "a=end-of-candidates" attributes following an
   "a=mid:" attribute, up until (and excluding) the next occurrence of a
   pseudo "m=" line, pertain to the "m=" line identified by that
   identification tag.  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.

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.

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= lines in the sdpfrag correlate
with the m= lines in the offer/answer.

In addition, it seems to me that there is no requirement that the
sdpfrag 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 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.

5.  Initial discovery of Trickle ICE support

   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.

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.

5.1.  Provisioning support for Trickle ICE

   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.

What is "the option"?  Perhaps "such provisioning".

5.2.  Trickle ICE discovery with Globally Routable User Agent URIs

   This circumvents to use of forking
   for that request.

I think you want s/circumvents to/prevents the/.

5.3.  Fall-back to Half Trickle

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.

6.  Considerations for RTP and RTCP multiplexing

       INFO sip:alice@example.com SIP/2.0
       ...
       Info-Package: trickle-ice
       Content-type: application/sdp
       Content-Disposition: Info-Package
       Content-length: 161

Shouldn't this be "Content-type: application/trickle-ice-sdpfrag"?

7.  Considerations for Media Multiplexing

       INFO sip:alice@example.com SIP/2.0
       ...
       Info-Package: trickle-ice
       Content-type: application/sdp
       Content-Disposition: Info-Package
       Content-length: 219

Shouldn't this be "Content-type: application/trickle-ice-sdpfrag"?

9.2.  Grammar

   A sender SHOULD stick to lower-
   case for such grammars, but a receiver MUST treat them case-
   insensitive.

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."

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.

10.1.  Rationale - Why INFO?

   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.

   On the other hand, using Offer/Answer and UPDATE requests [RFC3311]
   would introduce the following complications:

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.

Contrarily, UPDATE or other offer/answer mechanisms assume that the
messages in each direction are tightly coupled with messages in the
other direction.

12.2.  application/trickle-ice-sdpfrag Media Type

   This section defines a new Media Type 'application/trickle-ice-
   sdpfrag' in accordance with [RFC6838].

s/This section/This document/ -- as in section 12.2.

This section should refer to the grammar of section 9 as the
definition of the media type content.

         SDP files are primarily UTF-8 format text.  

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:

   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.

Then continue with "Although the initially ...", which describes the
character set implications of "are text".

         The "a=charset:"
         attribute may be used to signal the presence of other character
         sets in certain parts of a trickle-ice-sdpfrag body (see
         [RFC4566]).

Except that "a=charset" is not permitted by the grammar of section 9.

[END]



From nobody Thu Jan 25 06:04:59 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 127CE12D944; Thu, 25 Jan 2018 06:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 ZIVPlLwx2qkL; Thu, 25 Jan 2018 06:04:55 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 797F5120726; Thu, 25 Jan 2018 06:04:54 -0800 (PST)
X-AuditID: c1b4fb30-d31ff70000006bc7-ba-5a69e404243e
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 24.B6.27591.404E96A5; Thu, 25 Jan 2018 15:04:52 +0100 (CET)
Received: from [100.94.41.225] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.51) with Microsoft SMTP Server (TLS) id 14.3.352.0; Thu, 25 Jan 2018 15:04:51 +0100
To: Ben Campbell <ben@nostrum.com>, <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
References: <68E80650-0B78-4F4A-9339-BF6FE360FC8B@nostrum.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <4fad2816-976b-4d4b-2fec-9b496375d0a6@ericsson.com>
Date: Thu, 25 Jan 2018 15:04:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <68E80650-0B78-4F4A-9339-BF6FE360FC8B@nostrum.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070909060403070809090009"
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7sS7Lk8wog587DC3md55mtzjx/hur xdTlj1kcmD2WLPnJ5DFr5xOWAKYoLpuU1JzMstQifbsEroz1e5YzF3RuYazoOWvQwHhrEmMX IyeHhICJxK/LE5m7GLk4hAQOM0r8uNMI5WxilFh8+xoTSJWwQIhE36X1YLaIQKXEg7ZXzCC2 kICdxNZjx1hAbDYBC4mbPxrZQGxeAXuJH92NYDUsAqoSR/9MBLNFBWIkFjQfYoaoEZQ4OfMJ UC8HBydQ/aJHlSB7mQW6GSXaly5ggZivLdHQ1MEKcamSxPV511kmMPLPQtI+C1kPSIJZIEzi zZNFTBC2uETTl5WsELaZxLzND5khbG2JZQtfA9kcQLaaxLJWJVRhENtaYsavg2wQtqLElO6H 7BC2qcTrox8ZIWwjiXd7GtkXMPKsYhQtTi1Oyk03MtJLLcpMLi7Oz9PLSy3ZxAiMsoNbfhvs YHz53PEQowAHoxIPb8KjzCgh1sSy4srcQ4wqQHMebVh9gVGKJS8/L1VJhPdye0aUEG9KYmVV alF+fFFpTmrxIUZpDhYlcd6TnrxRQgLpiSWp2ampBalFMFkmDk6pBkZXvi3nI3OdmxxtZ7dd qm7mb69vWX1Lwi7DTva/o+CP+Ts0NR+/j9E8+3VClOkn+zbZaf8TFavs2EVn/GuZ6frU/uzN 6+HaeQvXl7kVzF+836ekwW7eSpY1uadLMnN9PrZwOHaxVRxw5V7znfVwVkOfTPbHnzdEdevS ZW2ZZd+dKRTq7t4YpcRSnJFoqMVcVJwIAEmXHgu6AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/dCwtSusqUdnDBqEaDSjs4-Qg7Ok>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47
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, 25 Jan 2018 14:04:58 -0000

--------------ms070909060403070809090009
Content-Type: multipart/alternative;
 boundary="------------E70EC45EB70A89248B914B60"
Content-Language: en-GB

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

Hi,

Christer invoked me on the RTP related questions. Here are my views on=20
these three issues.


Den 2018-01-24 kl. 12:46, skrev Christer Holmberg:
>
>
> TEXT (Section 10.2):
>
> However, some implementations may not include this identification-tag
> =C2=A0=C2=A0=C2=A0 in their RTP and RTCP traffic when using the BUNDLE =
mechanism, and
> =C2=A0=C2=A0=C2=A0 instead use a payload type based mechanism to associ=
ate RTP streams
> =C2=A0=C2=A0=C2=A0 with SDP "m=3D" sections.=C2=A0 In this situation, e=
ach "m=3D" section MUST
> =C2=A0=C2=A0=C2=A0 use unique payload type values, in order for the pay=
load type to be a
> =C2=A0=C2=A0=C2=A0 reliable indicator of the relevant "m=3D" section fo=
r the RTP stream.
> =C2=A0=C2=A0=C2=A0 Note that when using the payload type to associate R=
TP streams with
> =C2=A0=C2=A0=C2=A0 "m=3D" sections an RTP stream, identified by its SSR=
C, will be mapped
> =C2=A0=C2=A0=C2=A0 to an "m=3D" section when the first packet of that R=
TP stream is
> =C2=A0=C2=A0=C2=A0 received, and the mapping will not be changed even i=
f the payload
> =C2=A0=C2=A0=C2=A0 type used by that RTP stream changes.=C2=A0 In other=
 words, the SSRC
> =C2=A0=C2=A0=C2=A0 cannot "move" to a different "m=3D" section simply b=
y changing the
> =C2=A0=C2=A0=C2=A0 payload type.
>
>
>
>> -10.2,
>> =E2=80=B9 paragraph 7: What implementations are we talking about that =
may not
>> follow the requirements to include the tag in RTP/RTCP? Early
>> implementations of this draft? Something else? As it is, it seems=20
>> like we
>> are talking about implementations that do not follow this spec. That
>> makes the statement =C2=B3=C2=A0 =C5=A0 In this situation, each "m=3D"=
 section MUST use
>> unique payload type values=C5=A0=C2=B2 problematic, as it seems to be =
putting
>> requirements on implementations that do not follow this draft in the
>> first place.

Yes, this is a form of legacy adaptations. It applies towards certain=20
existing systems that already follows this rule. This include 3GPP MTSI=20
clients. It also applies to clients where the signalling system or the=20
signalling part of the client can be updated to follow this requirement. =

In some cases also middleboxes or gateways can have functionality for PT =

rewriting, but lack capability of inserting the id-tag.

So, a MUST where you either follow this requirement, or it will simply=20
not work at all. It can likely be rewritten either without a MUST, or=20
with an explanation that this is just stating a hard requirement for=20
making it work.
> ----
>
> TEXT (Section 10.2):
>
> Note that if an SDES packet is received as part of a compound RTCP
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packet, the SSRC to "m=3D" section=
 mapping may not exist until the
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDES packet is handled (e.g., in t=
he case where RTCP for a source
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is received before any RTP packets=
).=C2=A0 Therefore, when processing a
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 compound packet, any contained SDE=
S packet MUST be handled first.
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that this is a change from [R=
FC3550] Section 6.1, which
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that "Each individual RTCP =
packet in the compound packet
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 may be processed independently wit=
h no requirements upon the order
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 or combination of packets".
>
>
>
>> =E2=80=B9 '=C2=A0 Therefore, when processing a compound packet, any co=
ntained SDES
>> packet MUST be handled first.
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that this is a change from [RFC355=
0] Section 6.1 which
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that "Each individual RTCP packe=
t in the compound packet
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 may be processed independently with no =
requirements upon the order
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 or combination of packets=C2=B2.=C2=B9
>>
>> Doesn=C2=B9t this require an update of 3550? It=C2=B9s not merely a ti=
ghtening of
>> requirements, it=C2=B9s a reversal of guidance from that document when=
=20
>> used in
>> this context.

Looking at this now, I think this formulation may be a bit unnecessarily =

strict. If one fails to process the SDES item with the ID-tag in a=20
timely fashion, i.e. prior to needing to route any other information=20
element to the consumer, the only implication is that either the element =

is delayed or discarded. In the case discussed here, also the ID-tag=20
will likely to have been processed before the arrival of the RTP packets.=


I would suggest that that the MUST is changed to an implementation note=20
that simply recommends implementations to prioritize processing of the=20
SDES item, or otherwise consider methods for holding the routing for the =

other elements for a new non-associated SSRC until the SDES item(s) have =

been processed.

>
> ----
>
> TEXT (Section 17):
>
> The security considerations of "RTP Header Extension for the RTP
> =C2=A0=C2=A0=C2=A0 Control Protocol (RTCP) Source Description Items" [R=
FC7941] requires
> =C2=A0=C2=A0=C2=A0 that when RTCP is confidentiality protected, and tha=
t any SDES RTP
> =C2=A0=C2=A0=C2=A0 header extension carrying an SDES item, such as the =
MID RTP header
> =C2=A0=C2=A0=C2=A0 extension, is also protected using commensurate stre=
ngth algorithms.
> =C2=A0=C2=A0=C2=A0 However, assuming the above requirements and recomme=
ndations are
> =C2=A0=C2=A0=C2=A0 followed, there are no known significant security ri=
sks with leaving
> =C2=A0=C2=A0=C2=A0 the MID RTP header extension without confidentiality=
 protection.
> =C2=A0=C2=A0=C2=A0 Thus, the requirements in RFC 7941 MAY be ignored fo=
r the MID RTP
> =C2=A0=C2=A0=C2=A0 header extension.=C2=A0 Security mechanisms for RTP/=
RTCP are discussed in
> =C2=A0=C2=A0=C2=A0 Options for Securing RTP Sessions [RFC7201], for exa=
mple SRTP
> =C2=A0=C2=A0=C2=A0 [RFC3711] can provide the necessary security functio=
ns of ensuring
> =C2=A0=C2=A0=C2=A0 the integrity and source authenticity.
>
>
>> -17, last paragraph: Doesn=C2=B9t that require an update to 7941

Maybe a question of style in how one handles exceptions. I would not=20
update 7941, as the general rule still holds. But in this particular=20
case the exception is motivated for this particular SDES item, and that=20
is documented and agreed on (when RFC is published).


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


--------------E70EC45EB70A89248B914B60
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=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    Hi,<br>
    <br>
    Christer invoked me on the RTP related questions. Here are my views
    on these three issues.<br>
    <br>
    <br>
    Den 2018-01-24 kl. 12:46, skrev Christer Holmberg:
    <br>
    <blockquote type=3D"cite" style=3D"color: #000000;"><br>
      <br>
      TEXT (Section 10.2):
      <br>
      <br>
      However, some implementations may not include this
      identification-tag
      <br>
      =C2=A0=C2=A0=C2=A0 in their RTP and RTCP traffic when using the BUN=
DLE mechanism,
      and
      <br>
      =C2=A0=C2=A0=C2=A0 instead use a payload type based mechanism to as=
sociate RTP
      streams
      <br>
      =C2=A0=C2=A0=C2=A0 with SDP "m=3D" sections.=C2=A0 In this situatio=
n, each "m=3D" section
      MUST
      <br>
      =C2=A0=C2=A0=C2=A0 use unique payload type values, in order for the=
 payload type
      to be a
      <br>
      =C2=A0=C2=A0=C2=A0 reliable indicator of the relevant "m=3D" sectio=
n for the RTP
      stream.
      <br>
      =C2=A0=C2=A0=C2=A0 Note that when using the payload type to associa=
te RTP streams
      with
      <br>
      =C2=A0=C2=A0=C2=A0 "m=3D" sections an RTP stream, identified by its=
 SSRC, will be
      mapped
      <br>
      =C2=A0=C2=A0=C2=A0 to an "m=3D" section when the first packet of th=
at RTP stream is
      <br>
      =C2=A0=C2=A0=C2=A0 received, and the mapping will not be changed ev=
en if the
      payload
      <br>
      =C2=A0=C2=A0=C2=A0 type used by that RTP stream changes.=C2=A0 In o=
ther words, the
      SSRC
      <br>
      =C2=A0=C2=A0=C2=A0 cannot "move" to a different "m=3D" section simp=
ly by changing
      the
      <br>
      =C2=A0=C2=A0=C2=A0 payload type.
      <br>
      <br>
      <br>
      <br>
      <blockquote type=3D"cite" style=3D"color: #000000;">-10.2,
        <br>
        =E2=80=B9 paragraph 7: What implementations are we talking about =
that
        may not
        <br>
        follow the requirements to include the tag in RTP/RTCP? Early
        <br>
        implementations of this draft? Something else? As it is, it
        seems like we
        <br>
        are talking about implementations that do not follow this spec.
        That
        <br>
        makes the statement =C2=B3=C2=A0 =C5=A0 In this situation, each "=
m=3D" section
        MUST use
        <br>
        unique payload type values=C5=A0=C2=B2 problematic, as it seems t=
o be
        putting
        <br>
        requirements on implementations that do not follow this draft in
        the
        <br>
        first place.
        <br>
      </blockquote>
    </blockquote>
    <br>
    Yes, this is a form of legacy adaptations. It applies towards
    certain existing systems that already follows this rule. This
    include 3GPP MTSI clients. It also applies to clients where the
    signalling system or the signalling part of the client can be
    updated to follow this requirement. In some cases also middleboxes
    or gateways can have functionality for PT rewriting, but lack
    capability of inserting the id-tag.
    <br>
    <br>
    So, a MUST where you either follow this requirement, or it will
    simply not work at all. It can likely be rewritten either without a
    MUST, or with an explanation that this is just stating a hard
    requirement for making it work.
    <br>
    <blockquote type=3D"cite" style=3D"color: #000000;">----
      <br>
      <br>
      TEXT (Section 10.2):
      <br>
      <br>
      Note that if an SDES packet is received as part of a compound RTCP
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packet, the SSRC to "m=3D" sec=
tion mapping may not exist
      until the
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDES packet is handled (e.g., =
in the case where RTCP for a
      source
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is received before any RTP pac=
kets).=C2=A0 Therefore, when
      processing a
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 compound packet, any contained=
 SDES packet MUST be handled
      first.
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that this is a change fro=
m [RFC3550] Section 6.1,
      which
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that "Each individual R=
TCP packet in the compound
      packet
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 may be processed independently=
 with no requirements upon
      the order
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 or combination of packets".
      <br>
      <br>
      <br>
      <br>
      <blockquote type=3D"cite" style=3D"color: #000000;">=E2=80=B9 '=C2=A0=
 Therefore,
        when processing a compound packet, any contained SDES
        <br>
        packet MUST be handled first.
        <br>
        =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that this is a change from [R=
FC3550] Section 6.1
        which
        <br>
        =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that "Each individual RTCP =
packet in the compound
        packet
        <br>
        =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 may be processed independently wit=
h no requirements upon
        the order
        <br>
        =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 or combination of packets=C2=B2.=C2=
=B9
        <br>
        <br>
        Doesn=C2=B9t this require an update of 3550? It=C2=B9s not merely=
 a
        tightening of
        <br>
        requirements, it=C2=B9s a reversal of guidance from that document=

        when used in
        <br>
        this context.
        <br>
      </blockquote>
    </blockquote>
    <br>
    Looking at this now, I think this formulation may be a bit
    unnecessarily strict. If one fails to process the SDES item with the
    ID-tag in a timely fashion, i.e. prior to needing to route any other
    information element to the consumer, the only implication is that
    either the element is delayed or discarded. In the case discussed
    here, also the ID-tag will likely to have been processed before the
    arrival of the RTP packets.
    <br>
    <br>
    I would suggest that that the MUST is changed to an implementation
    note that simply recommends implementations to prioritize processing
    of the SDES item, or otherwise consider methods for holding the
    routing for the other elements for a new non-associated SSRC until
    the SDES item(s) have been processed.
    <br>
    <br>
    <blockquote type=3D"cite" style=3D"color: #000000;">
      <br>
      ----
      <br>
      <br>
      TEXT (Section 17):
      <br>
      <br>
      The security considerations of "RTP Header Extension for the RTP
      <br>
      =C2=A0=C2=A0=C2=A0 Control Protocol (RTCP) Source Description Items=
" [RFC7941]
      requires
      <br>
      =C2=A0=C2=A0=C2=A0 that when RTCP is confidentiality protected, and=
 that any SDES
      RTP
      <br>
      =C2=A0=C2=A0=C2=A0 header extension carrying an SDES item, such as =
the MID RTP
      header
      <br>
      =C2=A0=C2=A0=C2=A0 extension, is also protected using commensurate =
strength
      algorithms.
      <br>
      =C2=A0=C2=A0=C2=A0 However, assuming the above requirements and rec=
ommendations
      are
      <br>
      =C2=A0=C2=A0=C2=A0 followed, there are no known significant securit=
y risks with
      leaving
      <br>
      =C2=A0=C2=A0=C2=A0 the MID RTP header extension without confidentia=
lity
      protection.
      <br>
      =C2=A0=C2=A0=C2=A0 Thus, the requirements in RFC 7941 MAY be ignore=
d for the MID
      RTP
      <br>
      =C2=A0=C2=A0=C2=A0 header extension.=C2=A0 Security mechanisms for =
RTP/RTCP are
      discussed in
      <br>
      =C2=A0=C2=A0=C2=A0 Options for Securing RTP Sessions [RFC7201], for=
 example SRTP
      <br>
      =C2=A0=C2=A0=C2=A0 [RFC3711] can provide the necessary security fun=
ctions of
      ensuring
      <br>
      =C2=A0=C2=A0=C2=A0 the integrity and source authenticity.
      <br>
      <br>
      <br>
      <blockquote type=3D"cite" style=3D"color: #000000;">-17, last
        paragraph: Doesn=C2=B9t that require an update to 7941
        <br>
      </blockquote>
    </blockquote>
    <br>
    Maybe a question of style in how one handles exceptions. I would not
    update 7941, as the general rule still holds. But in this particular
    case the exception is motivated for this particular SDES item, and
    that is documented and agreed on (when RFC is published).
    <br>
    <pre class=3D"moz-signature" cols=3D"72">

Cheers

Magnus Westerlund=20

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"moz-txt-link-abbreviate=
d" href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@erics=
son.com</a>
----------------------------------------------------------------------</p=
re>
  </body>
</html>

--------------E70EC45EB70A89248B914B60--

--------------ms070909060403070809090009
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-kryptografisk signatur

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DNEwggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJ
BgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNV
BAoMCEVyaWNzc29uMRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJ
ARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+
laqg5eXTqonqnzT9ykEGL2dx9mBT+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJ
HGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iV
IiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpigGFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36o
gzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkrbdmdnjKGrYSnJigmxw14pJugxL/Vb2Ee
VcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDov
L2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNybDCBggYI
KwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29t
MEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29u
bmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rlcmx1bmRAZXJp
Y3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0
dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3
DQEBCwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4Q
ihhoQR3cvhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXD
yF9mhWYbSAkJyx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6
H3zO3nsq++KBmsOiSKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvE
lup5n7l864FqxnC2friDo4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl
60rmc8SJlt6QXKw0wXEOE1MubauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwD
ig3SZi1qP7D/Ds4V+JLIjjUJc25l9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8K
v7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLCQaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3
UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Zla71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzY
VBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd//n4YbY2QhDCCBsIwggSqoAMCAQICEFO4
foPhnJkok7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUx
MDI3MTIxNjQ2WjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMM
HEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDs8t8AALhQ8qe72FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfS
Tm+7meisbhkqUXkL7fFzoe4iIZCh/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbX
ILlLhRummTdDdxhVW4Leo0awEhfLf98MvWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfp
VdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmdvkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2
PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2
H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP1UrZaEIFu+hO+s0Nm8sOUMa4TlG4
rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0FdQDEzQlnF/h1L4AK1MOkX
1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA+yrrplCh/kYvSBjv
Zibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUrrvijPDaGK5FN
VSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQwgYoGCCsG
AQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEu
Y29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3Js
LTMudHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1Ud
JQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7
GZ6XnHasID3Y3OORauPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0G
CSqGSIb3DQEBCwUAA4ICAQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDU
JQEPRs5QtaZiObNHCZ7mmSNMVek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHG
vw5RY6vRlZrj0uKvdASzYL4KMaB7m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYn
nl2t3D3oBX2NZCQysshUcqRdUbkS13HTCIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwf
ixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNMMbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ8
5AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4Hd
Dc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0RLCi+4d4/47Zs3DC3PUNOxdOE
EHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZfAFM4HoHz8K2BZRaHKWhd
3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqGahxlHYzl/QyEG/du
jp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGCAzswggM3AgEB
MFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMA0GCWCGSAFlAwQCAQUA
oIIBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAxMjUx
NDA0NTFaMC8GCSqGSIb3DQEJBDEiBCD9fScUu5CBa55ErfuGNa+xe4OVhSRferRG7aa/w0M7
VTBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjEl
MCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBlrrZreXF5
7TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMGwGCyqGSIb3DQEJEAILMV2gWzBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nz
b24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62
a3lxee0wDQYJKoZIhvcNAQEBBQAEggEAHAWP1JPXmENoLdesq72bWn6aNqrEBAyJGWGVaqOG
h96cQ330/5i+MhqjyGKxyV7L2fVCY+LZhQ2zUP5yVV8MqrmNs5s4NH1a8rmL5vwxT0iB536u
16Q40b7wiOijrQ6sk8L8nG93jbdXh0d3C1vat6Ue+Z/L4r4QsorRpYHeHwuQUnH4yKFUE0kW
tFFkmIXWLApPfr6yAwGczmoO/iu68LXT/jfLFthuOxTBIzScomM/fcQ4HhrR+O9wUyam5nbn
vLmiEy+m8fLHwukqxaCPZfB6+7TsmrvY5US3+eSTWGNcNxe+QmYyc2sehx57WVNWlT/b+KTX
gcLZs/iZA6oJJwAAAAAAAA==
--------------ms070909060403070809090009--


From nobody Thu Jan 25 14:35:50 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 9CEFF12D77E; Thu, 25 Jan 2018 14:35:48 -0800 (PST)
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 77X6yGoeXbVc; Thu, 25 Jan 2018 14:35:46 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 478B812D777; Thu, 25 Jan 2018 14:35:46 -0800 (PST)
Received: from [10.0.1.105] (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 w0PMZfXb093756 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Jan 2018 16:35:42 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <3C5E3CED-2E54-4B56-B378-8421EB05F1FD@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_3FD89E1E-2F79-4108-8F31-4E891ED478A9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 25 Jan 2018 16:35:40 -0600
In-Reply-To: <4fad2816-976b-4d4b-2fec-9b496375d0a6@ericsson.com>
Cc: draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org, MMUSIC <mmusic@ietf.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <68E80650-0B78-4F4A-9339-BF6FE360FC8B@nostrum.com> <4fad2816-976b-4d4b-2fec-9b496375d0a6@ericsson.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/5xm-jFhJDNqpbxIp4-6CbauEaJI>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47
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, 25 Jan 2018 22:35:49 -0000

--Apple-Mail=_3FD89E1E-2F79-4108-8F31-4E891ED478A9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 25, 2018, at 8:04 AM, Magnus Westerlund =
<magnus.westerlund@ericsson.com> wrote:
>=20
> Hi,
>=20
> Christer invoked me on the RTP related questions. Here are my views on =
these three issues.
>=20
>=20
> Den 2018-01-24 kl. 12:46, skrev Christer Holmberg:
>>=20
>>=20
>> TEXT (Section 10.2):
>>=20
>> However, some implementations may not include this identification-tag
>>     in their RTP and RTCP traffic when using the BUNDLE mechanism, =
and
>>     instead use a payload type based mechanism to associate RTP =
streams
>>     with SDP "m=3D" sections.  In this situation, each "m=3D" section =
MUST
>>     use unique payload type values, in order for the payload type to =
be a
>>     reliable indicator of the relevant "m=3D" section for the RTP =
stream.
>>     Note that when using the payload type to associate RTP streams =
with
>>     "m=3D" sections an RTP stream, identified by its SSRC, will be =
mapped
>>     to an "m=3D" section when the first packet of that RTP stream is
>>     received, and the mapping will not be changed even if the payload
>>     type used by that RTP stream changes.  In other words, the SSRC
>>     cannot "move" to a different "m=3D" section simply by changing =
the
>>     payload type.
>>=20
>>=20
>>=20
>>> -10.2,
>>> =E2=80=B9 paragraph 7: What implementations are we talking about =
that may not
>>> follow the requirements to include the tag in RTP/RTCP? Early
>>> implementations of this draft? Something else? As it is, it seems =
like we
>>> are talking about implementations that do not follow this spec. That
>>> makes the statement =C2=B3  =C5=A0 In this situation, each "m=3D" =
section MUST use
>>> unique payload type values=C5=A0=C2=B2 problematic, as it seems to =
be putting
>>> requirements on implementations that do not follow this draft in the
>>> first place.
>=20
> Yes, this is a form of legacy adaptations. It applies towards certain =
existing systems that already follows this rule. This include 3GPP MTSI =
clients. It also applies to clients where the signalling system or the =
signalling part of the client can be updated to follow this requirement. =
In some cases also middleboxes or gateways can have functionality for PT =
rewriting, but lack capability of inserting the id-tag.
>=20
> So, a MUST where you either follow this requirement, or it will simply =
not work at all. It can likely be rewritten either without a MUST, or =
with an explanation that this is just stating a hard requirement for =
making it work.

I think that could work for me, but would like to see it in text before =
commiting :-)

>> ----
>>=20
>> TEXT (Section 10.2):
>>=20
>> Note that if an SDES packet is received as part of a compound RTCP
>>        packet, the SSRC to "m=3D" section mapping may not exist until =
the
>>        SDES packet is handled (e.g., in the case where RTCP for a =
source
>>        is received before any RTP packets).  Therefore, when =
processing a
>>        compound packet, any contained SDES packet MUST be handled =
first.
>>        Note that this is a change from [RFC3550] Section 6.1, which
>>        states that "Each individual RTCP packet in the compound =
packet
>>        may be processed independently with no requirements upon the =
order
>>        or combination of packets".
>>=20
>>=20
>>=20
>>> =E2=80=B9 '  Therefore, when processing a compound packet, any =
contained SDES
>>> packet MUST be handled first.
>>>       Note that this is a change from [RFC3550] Section 6.1 which
>>>       states that "Each individual RTCP packet in the compound =
packet
>>>       may be processed independently with no requirements upon the =
order
>>>       or combination of packets=C2=B2.=C2=B9
>>>=20
>>> Doesn=C2=B9t this require an update of 3550? It=C2=B9s not merely a =
tightening of
>>> requirements, it=C2=B9s a reversal of guidance from that document =
when used in
>>> this context.
>=20
> Looking at this now, I think this formulation may be a bit =
unnecessarily strict. If one fails to process the SDES item with the =
ID-tag in a timely fashion, i.e. prior to needing to route any other =
information element to the consumer, the only implication is that either =
the element is delayed or discarded. In the case discussed here, also =
the ID-tag will likely to have been processed before the arrival of the =
RTP packets.
>=20
> I would suggest that that the MUST is changed to an implementation =
note that simply recommends implementations to prioritize processing of =
the SDES item, or otherwise consider methods for holding the routing for =
the other elements for a new non-associated SSRC until the SDES item(s) =
have been processed.

That seems reasonable.

>=20
>>=20
>> ----
>>=20
>> TEXT (Section 17):
>>=20
>> 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.
>>     However, assuming the above requirements and recommendations are
>>     followed, there are no known significant security risks with =
leaving
>>     the MID RTP header extension without confidentiality protection.
>>     Thus, the requirements in RFC 7941 MAY be ignored for the MID RTP
>>     header extension.  Security mechanisms for RTP/RTCP are discussed =
in
>>     Options for Securing RTP Sessions [RFC7201], for example SRTP
>>     [RFC3711] can provide the necessary security functions of =
ensuring
>>     the integrity and source authenticity.
>>=20
>>=20
>>> -17, last paragraph: Doesn=C2=B9t that require an update to 7941
>=20
> Maybe a question of style in how one handles exceptions. I would not =
update 7941, as the general rule still holds. But in this particular =
case the exception is motivated for this particular SDES item, and that =
is documented and agreed on (when RFC is published).

I=E2=80=99m not sure I agree. This adds an exception to a security =
related MUST from 7941. While I recognize that it may be safe to do =
that, I think it still requires an update. That doesn=E2=80=99t even =
have to be a generic update; something along the line of =E2=80=9CThis =
document updates $FC 7941 to add an exception to that requirement for =
the MID extension=E2=80=9D.

Thanks!

Ben.

--Apple-Mail=_3FD89E1E-2F79-4108-8F31-4E891ED478A9
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpqW7wACgkQgFZKbJXz
1A2Eew//QMOJre3cYNEErc84e6snZni9KVmdL2hn2EQvG9jlIP0lKFaJ7/9UITDA
R2FFWbdb5ASRn6EgJKRs9/g9tRxWehPszu8Y1ei3yzQIBW1Xk4mwhmwymBayu6WV
1WgEgYj108wl7hnF/Eo+wu3q8pMj0PIXjT0SYW2I263ckLJKG/x7enWAHnX3PA0a
hv3haaxBV+nlwW6ElkMJOwskdAqclceVbHLP1rl08yMiqhdChdWBaJRgUrxwtn1i
GGeUpImwfkQC+wMma3SAa4ONYOEmI+Mul0dn/SsYl+lzOFKwRH4LE5NJx0OjvNf3
NKsitxojD9kHKYkkDyhq7LA3xZ2UemzMyYBlBxsgJAGPaY+35NuZuuicLKgcr4th
oPZZcUrmftgNon2cupoUmDWPT7k2LaUR4J7V5DSAya31ifiZ1UaBm58f7StOU1GP
8bzheQMxz7IkDJabO+0zWosL2sc30v2iFcBIlHVrMvnJA4YxUAWGpZS+FJUYnvlH
rxh/j8nwUnGFzkD6Lgo3CqpCGjdurOfotb2LHCIM2cpEi61jxkHZehQaN/Ucn74M
nPGlObRtLRqSRe9Dyx6FhXGf5iXKkSeIyEacdE6oflk4Xh1CBwy3g48DzHOMPlkS
/e+2MBV69BzA8dH8ZGjoafIRXvnhPOFtmn6meKcoJNIWH3DlzzY=
=uJXf
-----END PGP SIGNATURE-----

--Apple-Mail=_3FD89E1E-2F79-4108-8F31-4E891ED478A9--


From nobody Thu Jan 25 14:57:54 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 C1B6312EAE1; Thu, 25 Jan 2018 14:57:52 -0800 (PST)
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 phKc6M8a-0cT; Thu, 25 Jan 2018 14:57:51 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F153112EAD5; Thu, 25 Jan 2018 14:57:50 -0800 (PST)
Received: from [10.0.1.105] (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 w0PMvjqW096119 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Jan 2018 16:57:46 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_88E69D56-CF97-49B2-8490-6C9ABEADD05E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 25 Jan 2018 16:57:44 -0600
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se>
Cc: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>,  MMUSIC <mmusic@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/AwbTvV025Gk0dohcgVvPWSQkS5w>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 25 Jan 2018 22:57:53 -0000

--Apple-Mail=_88E69D56-CF97-49B2-8490-6C9ABEADD05E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 20, 2018, at 7:44 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Ben,
>=20
> Thanks for your review! Please see inline.
>=20
> (For convenience, I will address your editorial comments in a separate =
reply)
>=20
> *** Substantive Comments ***
>=20

[=E2=80=A6]

>> - section 8, first paragraph after bullet list: I=E2=80=99m confused =
as to whether this talks about the initial offer or a subsequent
>> offer. the comment about the =E2=80=9Cpreviously negotiated SDP =
parameters=E2=80=9D seems to suggest the latter. I suspect this is =
intended
>> to cover all offers, in which case it needs clarification.
>=20
> It's the offer in which the BUNDLE group is created. I may be the =
initial offer of the session, or it may be a subsequent offer within the =
session. It's irrelevant as far as BUNDLE is concerned.

I assumed that to be the case, but I found the mention of previously =
negotiated parameters without some clarification that there might not be =
any to be confusing.

>=20
> Also note that section 2 defines "initial offer" as the offer where =
the BUNDLE group is created:
>=20
>   "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
> But, if we want to make it clear also in Section 8, I could add the =
following note:
>=20
> "NOTE: The offer in which the offerer indicates that it wants to =
create a BUNDLE group can be the initial offer of the session, or a =
subsequent offer within the session. As defined in section 2, within the =
scope of this document the initial offer always refers to the offer in =
which the offerer indicates that it wants to create a BUNDLE group, no =
matter whether that offer is the initial offer, or a subsequent offer, =
within the session.=E2=80=9D

I think that would help.

>=20
> ---
>=20
>> -8.3.3: IIUC, the criteria mean that the only m=3D sections that the =
answerer can move out of the bundle are those that
>> have unique addresses but are not listed first in the group =
attribute. If that is correct, a sentence or two to say that would be =
helpful.
>=20
> As long as the m=3D section contains a unique address (and does not =
contain a bundle-only attribute) it can be moved out of a BUNDLE group, =
no matter where it is listed in the group attribute.

Then what does this text from the first bullet under 8.3.3 mean, as part =
of the criteria for things that _can=E2=80=99t_ be moved out of the =
group?

=E2=80=9C o  In the corresponding offer, an offerer BUNDLE address =
(previously
      selected [Section 8.3.1] or new suggested [Section 8.5.1]) has
      been assigned to the "m=3D" section by the offerer;"



>=20
> ---
>=20
>> -8.5, first paragraph. IIUC, it=E2=80=99s not syntactically possible =
to assign more than one m=3D section the bundle address, since only one
>> can be first in the group attribute. If that is correct, the MUST =
here is a statement of fact. Or am I missing something?
>=20
> There can only be one first in the group attribute, but syntactically =
you could assign the bundle address value (IP address and port) to more =
than one m=3D section.

Ah, okay.

>=20
> (At the end of the day, the tag is really only relevant in the initial =
offer, where you may assign multiple different unique addresses, and you =
want to indicate which one you want to use as bundle address. Once the =
bundle address has been negotiated, you won't assign any other addresses =
to an offer)
>=20
> ---
>=20
>> -9: There are several assertions that in order to do something you =
MUST have a spec saying how to do it. Formally,
>> I think the requirement is really that you MUST NOT do that thing =
unless such a spec exists. (2119/8174 keywords are normally about =
implementation behavior.)
>=20
> Is it ok if I keep that in mind for my next draft? :)

Okay :-)

>=20
> ---
>=20
>> -10.2,
>> =E2=80=94 paragraph 7: What implementations are we talking about that =
may not follow the requirements to include the tag in
>> RTP/RTCP? Early implementations of this draft? Something else? As it =
is, it seems like we are talking about implementations
>> that do not follow this spec. That makes the statement =E2=80=9C  =E2=80=
=A6 In this situation, each "m=3D" section MUST use unique payload type
>> values=E2=80=A6=E2=80=9D problematic, as it seems to be putting =
requirements on implementations that do not follow this draft in the =
first place.
>=20
> There were looooong discussions about this section, and I'll outsource =
the question to others.
>=20
> Cullen? Ekr?

I think Magnus=E2=80=99s response to this made sense. OTOH, if messing =
with this text might undo a difficult consensus process, I could be =
convinced to leave it alone.

>=20
>> =E2=80=94 '  Therefore, when processing a compound packet, any =
contained SDES packet MUST be handled first.
>>     Note that this is a change from [RFC3550] Section 6.1 which
>>     states that "Each individual RTCP packet in the compound packet
>>     may be processed independently with no requirements upon the =
order
>>     or combination of packets=E2=80=9D.=E2=80=99
>>=20
>> Doesn=E2=80=99t this require an update of 3550? It=E2=80=99s not =
merely a tightening of requirements, it=E2=80=99s a reversal of guidance =
from that document when used in this context.
>=20
> How would we update 3550? Adding a sentence saying ", unless a =
specific usage defines otherwise"?
>=20
> In my opinion it is a tightening of requirements. But, if others think =
otherwise I don't have any strong feelings.

I think Magnus=E2=80=99s comments here made sense.


>=20
> ---
>=20
>> -10.3.1.3, last paragraph: What is the expected behavior when that =
"protocol error" occurs?
>=20
> I don't think we don't normally specify that in cases like this, =
because it's an implementation issue. An implementation may trigger a =
new O/A exchange, or may terminate the whole session, etc etc.

Those are recovery actions. Would it reasonable for the offerer to =
pretend the answerer had really meant to accept rtp/rtcp multiplexing? =
Or must the offerer give up on _this_ offer/answer exchange?

---
>=20
>> -15.2, last paragraph: Is it worth recommending against patterns =
which could be used as persistent identifiers, even if
>> they don=E2=80=99t expressly identify a person or application?
>=20
> What would they identity?
>=20
> Just saying "..., or could be used as persistent identifiers" sounds a =
little half baked.

As an example, assume that even though the implementation puts no =
user-identifying information in the tag, it puts some piece of =
information in there that is always the same for a given user. If =
someone manages to correlate that piece to other activity that _does_ =
identify the user, the piece becomes user-identifying.

[=E2=80=A6]


> ---
>=20
>> -17, 2nd paragraph:
>> =E2=80=94 Again, is it worth mentioning the risk of persistent =
identifiers?
>=20
> See above.

Ditto :-)

>=20
>> =E2=80=94  =E2=80=9C=E2=80=A6 SHOULD be 3 bytes or less, to allow =
them to efficiently fit into the MID RTP header extension.=E2=80=9D
>> It seems like that requirement belongs in 15.2
>=20
> Section 15.2 does say that the length shall be 1-3 bytes.

Okay, I missed it there.

>=20
>=20
> ---
>=20
>> -17, last paragraph: Doesn=E2=80=99t that require an update to 7941
>=20
> If I remember correctly, there were long discussions about this, and =
it is one of the =
the-RFC-is-correct-but-not-everyone-implement-that-requirement things...
>=20
> Cullen? Ekr?
>=20

See Magnus=E2=80=99s comments and my response.

[=E2=80=A6]

--Apple-Mail=_88E69D56-CF97-49B2-8490-6C9ABEADD05E
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpqYOgACgkQgFZKbJXz
1A07Ag/+IAGUpi5ETJBhGrjns1ax85SiAFWm0I2WZeNMNUG2+9fv5jZRG6wLfLZK
PUgvjZpiASRHSnuf5h0xTwU5lSnE2zir4ZGGw+omqHh5tZOwE+zAcK9idguDEBj4
h7icgX51OUqV13H1Uw2z+fPr1j02F+BnRF3k1Lpc5jMDDqy/3HryjK2NKGDl6FBV
DbnxEiMxT8tTTTnmDQSy0NXPuuRcYP4Dz5WnynZmqsAka8E2qO5gegQd9xphWfMY
CS3McBwUh3VYVaArdVYrAUo9duuEKZVCqLr13/WWVF7EXfkyLc+kzvbUR8Nhd+A7
YRAIvbapSBT8qbsgephSR6q+22+jPNC9CYnAP9WRTqQjsuos8KQ7XNxdJCx0BkkO
zwWzX/oXBvHlXYtOa39+9UvZorSWGri3K94eR7ODs9HsQ+NlYN3GGZamOEMtxN+h
JJt5AEkjC7+gBZ0ac1pYNfNmjYG/QNg8+gSy/Jv2ULURImS44lyliXB86ssZkzFf
zUNUea1Su24/miUVpIpenpDr5aC24hNP6ZOdgaTml0/p9+BOA+tffwqM+ZatwEZp
tW+ODRzrGC24un7+XVX/5EGo4YEG8dA2bEOEKOd17nwYZUHOQhvwZb7nOG4zg2sG
ozmSu4gemMVehQMju6cvBLQfMGNAiuTLudMYpCgQA1+N7n+SWdM=
=O63o
-----END PGP SIGNATURE-----

--Apple-Mail=_88E69D56-CF97-49B2-8490-6C9ABEADD05E--


From nobody Thu Jan 25 15:15:18 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 7313A12D7ED; Thu, 25 Jan 2018 15:15:17 -0800 (PST)
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 cxNJtJLIkI66; Thu, 25 Jan 2018 15:15:15 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C5B312D7E8; Thu, 25 Jan 2018 15:15:15 -0800 (PST)
Received: from [10.0.1.105] (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 w0PNFBJn098013 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 25 Jan 2018 17:15:12 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <D86D82FD-663E-4A23-9742-19F577DEDCB1@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7F19C48C-15AB-4CFE-844F-40C8350B032A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 25 Jan 2018 17:15:10 -0600
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C13312E@ESESSMB109.ericsson.se>
Cc: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>,  MMUSIC <mmusic@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C13312E@ESESSMB109.ericsson.se>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/DCab1LGRtTsQfT4KrwXa11ZP6kA>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments
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, 25 Jan 2018 23:15:17 -0000

--Apple-Mail=_7F19C48C-15AB-4CFE-844F-40C8350B032A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 21, 2018, at 1:35 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> In this reply I address the editorial comments. Please see inline.
>=20
> *** Editorial Comments and nits ***
>=20
> ---
>=20
>> - Terminology issues: I think some of the terminology here will =
confuse readers who are new to the concepts.
>> In particular, IIUC, =E2=80=9Cbundle address=E2=80=9D means address + =
port. I think many readers will fall back to assuming that
>> address means IP address. (Especially when we talk about a =E2=80=9Cuni=
que address=E2=80=9D assigned to an m=3D section, when
>> much of the time that may just mean a unique port.)
>=20
> Section 2 does define "bundle address" as an address:port combination.

Yes, it does=E2=80=94but the redefinition of a well-known term often =
fails to stick in people=E2=80=99s heads.

>=20
> But, I see your point.
>=20
> Would "bundle address-port", "bundle addressport", "bundle addrprt", =
or something similar, be better? I don't want to say "bundle =
address:port combination" in every instance=E2=80=A6

I struggled with a suggestion when I originally wrote the comment, and =
didn=E2=80=99t come up with something I liked. =E2=80=9CTransport=E2=80=9D=
 seems descriptive, but there=E2=80=99s similarly well-known usage of =
that that doesn=E2=80=99t quite match. Maybe =E2=80=9Cbundle =
address:port=E2=80=9D?

>=20
> ---
>=20
>> I also find defining the term =E2=80=9CBundle Tag=E2=80=9D to mean =
the first tag in the list to be confusing. It may be easier to just =
refer to the =E2=80=9Cfirst tag in the group list=E2=80=9D.
>=20
> Again, section 2 does define the meaning.

Again, memory of definitions may tend to slip by the time one finishes a =
67 page document. But I=E2=80=99m okay leaving this one as is, since it =
doesn=E2=80=99t collide with people=E2=80=99s preconceived definitions =
of something.

>=20
> ---
>=20
>> =E2=80=94 Examples: Any chance of some of the examples showing IPv6? =
I suspect it=E2=80=99s a trivial change for at least some examples, =
since they use domain names.
>=20

> I can do that.

I think that would be worthwhile. The lack of IPv6 examples in drafts =
has come up in IESG review recently.
>=20
>> -Section 1,
>> =E2=80=94 first paragraph: This sort of jumps into things without =
much context. (e.g. that we are talking about media
>> sessions signaled using SDP offer/answer.=E2=80=9D
>=20
> I could say:
>=20
> "When the SDP offer/answer mechanism [RFC3264] is used to negotiate =
the establishment of multimedia
> communication sessions, if separate transports (5-tuples) are =
negotiated for each individual media stream,
> each transport consumes additional resources (especially when =
Interactive Connectivity Establishment
> (ICE) [I-D.ietf-ice-rfc5245bis] is used).  For this reason, it is =
attractive to use a single transport for multiple
> media streams.=E2=80=9D
>=20
That helps, thanks.

[=E2=80=A6]
>=20

>> =E2=80=94 2nd to last paragraph, =E2=80=9CThe procedures in this =
specification apply independently to a given BUNDLE group.=E2=80=9D : I =
don=E2=80=99t
>> understand what that sentence is trying to convey.
>=20
> I says that, if your SDP contains multiple BUNDLE groups, the =
procedures are applied independently to each of them.

How about =E2=80=9CIf an SDP offer or answer contains multiple BUNDLE =
groups, the procedures in this specification apply to each group =
independently.=E2=80=9D?
>=20

[=E2=80=A6]

> ---
>=20
>> - Section 8.1:
>> =E2=80=94 Consider moving this section to later in the offer/answer =
details. I think it would be easier for a reader to
>> understand this section after they have some more general context.
>=20
> The reason it is in the beginning is because it is part of the generic =
procedures.
>=20
> Would you like to place it at the end of Section 8?
>=20

Hrm. I guess that=E2=80=99s not great either, and I understand your =
point. I withdraw the comment.

[=E2=80=A6]


> ---
>=20
>> -8.2.1, first paragraph:
>> =E2=80=94 The phrase =E2=80=9Crepresented by the =E2=80=A6 =
BUNDLE-tag=E2=80=9D occurs repeatedly throughout the document. The use =
of =E2=80=9Crepresented=E2=80=9D there
>> seems awkward. I think =E2=80=9Cindicated=E2=80=9D would be a better =
word choice.
>=20
> This is one of the words that have been changed multiple times =
throughout the work of the document...
>=20
> I can see whether your suggestion can be done with a search/replace, =
but if it requires more than that I would not like to do it.
>=20

Okay

[=E2=80=A6]


>=20
>> =E2=80=94 Last paragraph: This paragraph seems mostly (or entirely) =
redundant to section 9.1.
>=20
> The text gives an overview of what is done in this document, and what =
needs to be done elsewhere. I'd like to keep it.
>=20

Okay.

> ---
>=20
> -10.2:
>=20
>> =E2=80=94 " RTCP packets for which no appropriate "m=3D" section can =
be identified
>>   MUST be processed as usual by the RTP layer, updating the metadata
>>  associated with the corresponding RTP streams, but are not passed to
>>  any "m=3D" section.=E2=80=9D
>>=20
>> I don=E2=80=99t think things gets passed to sections of SDP. What =
does this really talk about?
>=20
> This is another thing that it took forever to agree upon. The idea was =
to use different "layers" when processing received RTP/RTCP packets.
>=20
> However, I do agree that the text is a little confusing.
>=20
> Perhaps something like:
>=20
>   "RTCP packets that cannot be associated with an appropriate "m=3D" =
section
>   MUST still be processed as usual by the RTP layer, updating the =
metadata
>   associated with the corresponding RTP streams."
>=20
> ...and in the prior paragraph:
>=20
>   "For each RTCP packet received (including each RTCP packet that is
>   part of a compound RTCP packet), the packet is processed as usual by
>   the RTP layer, then associated with the appropriate "m=3D" sections, =
and
>   processed for the RTP streams represented by those "m=3D" =
sections.=E2=80=9D

I was going to suggest changing =E2=80=9Cpassed to=E2=80=9D to =
=E2=80=9Cassociated with=E2=80=9D in the first paragraph, but I like =
your placement of that better.

[=E2=80=A6]
>=20

>> =E2=80=94 last paragraph: It may be worth clarifying that this =
doesn't change any requirement specified by the
>> application or signaling protocol. For example, WebRTC still requires =
ICE even though bundle is used.
>=20
> Question for clarification: Do you want to say that some applications =
might mandate ICE even if BUNDLE is not used, or that some applications =
might mandate support of ICE together with BUNDLE?

The latter..

[=E2=80=A6]


>> =E2=80=94 3rd paragraph: Construct of the form of =E2=80=9CMUST =
only=E2=80=9D can be ambiguous. Please consider restating
>> in the form of a MUST NOT construction. (For example, =E2=80=9CMUST =
only do foo when=E2=80=A6.=E2=80=9D can be interpreted
>> as =E2=80=9CMUST NOT do foo unless=E2=80=A6=E2=80=9D or =E2=80=9CMUST =
NOT do anything but foo when=E2=80=A6=E2=80=9D   [Note: This construct =
repeats
>> several times in the next few sections. ]
>=20
> What about?
>=20
>   "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
>   other applicable ICE-related media-level SDP attributes) in that =
"m=3D"
>   section, following the procedures in Section 8.1. The answerer MUST =
NOT
>   include ICE-related media-level SDP attributes in any other "m=3D" =
sections.=E2=80=9D

WFM.

[=E2=80=A6]

Thanks!

Ben.

--Apple-Mail=_7F19C48C-15AB-4CFE-844F-40C8350B032A
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpqZP4ACgkQgFZKbJXz
1A03ZhAAhaIZlatNZy4afyX/aocQpCJxpMobjEE12ycGDmQqNtwxSPwiJQGTSf47
jdiFIi0oNPlPl8o9XHZfn307NIzGxnxGe+8AWFme2ZB09FzYsd8GlRobKYATtYIa
QC7ij4WQhf8PkiC7/pYCjKaVrkI7X6ZsGyp7PQaMcG4+gxCSe5qLdbYl1v5Y1doU
tlY26hzfzYEGTJnrPeFeJl632e3FpZKPrQMo7CORHRkIeTF8/jlAXHYYxYYQK+cy
THDyTzgtVhrRsNN1xZPnZfW88uXfV+n8iC7Z5lQgAAzgC1MeQajk2TNBEZTpvMFS
D/F2xhr0J5cNMZE+sNdcFIh6GS460dlWATIuT16il1hSqlyOeACSGoXozjd465du
+Cd1r3jDF60cxhMO+6sll/h2JD4R+7JRcLfP5r3uhAy4SlBgpKaOZ8UP8g8bnehg
FPYz+4FAVvx2xYRq5CJsGZu14x1aKZa8j1zfd4nepFgsN9RCcfr4UnPoz1xkmnSa
naYaqL4k8meAwsD1JuqK6GZDw137ZcG+qjyPIOfTEzJAP7KODSPA1vaDSYkFpqPP
3ImCHd6yr70ZtcnYrcmlznqRGrCD1kYCnztLnoeDidme4X3UU75gaT/gdB7er9hz
3lgjCJLxvyeOo5ReC/h+6f7d+7yJqPY+A8cAZOZH7zXRr2shSlY=
=EAci
-----END PGP SIGNATURE-----

--Apple-Mail=_7F19C48C-15AB-4CFE-844F-40C8350B032A--


From nobody Fri Jan 26 03: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 51AC812E880; Fri, 26 Jan 2018 03:16:55 -0800 (PST)
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 1kGd37y6-l9X; Fri, 26 Jan 2018 03:16:49 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90E6312EA90; Fri, 26 Jan 2018 03:16:48 -0800 (PST)
X-AuditID: c1b4fb2d-f179c9c000007932-99-5a6b0e1e9c29
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 38.C1.31026.E1E0B6A5; Fri, 26 Jan 2018 12:16:46 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.03.0352.000; Fri, 26 Jan 2018 12:16:46 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
Thread-Index: AdOR5+qL7nrym0YKTg6KUgOkGJEv7QEP5ykAAB5l/AA=
Date: Fri, 26 Jan 2018 11:16:45 +0000
Message-ID: <D690D58C.29DC5%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se> <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@nostrum.com>
In-Reply-To: <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@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: [153.88.183.146]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <900323BF1D604C4EADA5FCFFB23919BB@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMIsWRmVeSWpSXmKPExsUyM2K7uq4cX3aUwYEvFhbzO0+zW5x4/43V YuryxywOzB5Llvxk8pi18wlLAFMUl01Kak5mWWqRvl0CV8a/RTuZCv7IVLTucWtgnCrexcjJ ISFgInHp60+2LkYuDiGBw4wSsz9NYgdJCAksYZS40ZzexcjBwSZgIdH9TxskLCKgJPG8eSsL SD2zwERGiUcLFrGAJIQFMiR+7vrODFGUKdG36BsjhG0lMfnzbjYQm0VAVWL97edgNbwC1hIb 7k1lgVjcxCgxbeopJpAEp4C9xJF/F8FsRgExie+n1oDZzALiEreezGeCuFpAYsme88wQtqjE y8f/WEFsUQE9iQ0nbrNDxJUkfmy4xALRayDx/tx8ZpBnmIEWty9KhghrSyxb+BrqHkGJkzOf sExgFJ+FZNssJN2zELpnIemehaR7ASPrKkbR4tTi4tx0I2O91KLM5OLi/Dy9vNSSTYzAqDu4 5bfuDsbVrx0PMQpwMCrx8G75kxUlxJpYVlyZe4hRgoNZSYTXjDM7Sog3JbGyKrUoP76oNCe1 +BCjNAeLkjjvSU/eKCGB9MSS1OzU1ILUIpgsEwenVAOjhr2UgeeXziczO1X8M/anZ65fZqaa IZbAf26rncZDtjcuN/fcM8vpyiw+W3U5c4eG2I9L4S5v4nVmlXhPmiH72vGw3Y3CyWeLtx5n NS86EFO201barY7rwNeGd4bPywMr7P9ODZTr3DJz4j2J+fnZ2r+eTfj3PvFa+fYYDYFU24JH by0X5kxRYinOSDTUYi4qTgQABCbAT7YCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bwA4KCfQDvAPOhKHDJJJL-fEk5Q>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 26 Jan 2018 11:16:55 -0000

Hi Ben,

Please see inline.

(I=B9ll address the comments where Magnus has provided input in the
dedicated thread)

...

>>=20
>>> -8.3.3: IIUC, the criteria mean that the only m=3D sections that the
>>>answerer can move out of the bundle are those that
>>> have unique addresses but are not listed first in the group attribute.
>>>If that is correct, a sentence or two to say that would be helpful.
>>=20
>> As long as the m=3D section contains a unique address (and does not
>>contain a bundle-only attribute) it can be moved out of a BUNDLE group,
>>no matter where it is listed in the group attribute.
>
>Then what does this text from the first bullet under 8.3.3 mean, as part
>of the criteria for things that _can=B9t_ be moved out of the group?
>
>=B3 o  In the corresponding offer, an offerer BUNDLE address (previously
>      selected [Section 8.3.1] or new suggested [Section 8.5.1]) has
>      been assigned to the "m=3D" section by the offerer;"


Ok, I see what you mean.

My statement regarding unique address was incorrect.

The important part is =B3new suggested=B2 - when a BUNDLE address have
previously been negotiated. Because, compared to the initial offer, when a
NEW BUNDLE address is suggested, it is only assigned to ONE m=3D line. A
zero port value is assigned to all other m=3D sections, so because of that
the m=3D section with the new suggested address cannot be moved out of the
BUNDLE group.

---

>>=20
>>> -10.3.1.3, last paragraph: What is the expected behavior when that
>>>"protocol error" occurs?
>>=20
>> I don't think we don't normally specify that in cases like this,
>>because it's an implementation issue. An implementation may trigger a
>>new O/A exchange, or may terminate the whole session, etc etc.
>
>Those are recovery actions. Would it reasonable for the offerer to
>pretend the answerer had really meant to accept rtp/rtcp multiplexing? Or
>must the offerer give up on _this_ offer/answer exchange?

I guess we could allow both alternatives.

What about:

"NOTE: It is considered a protocol error if the answerer has not
   accepted the usage of RTP/RTCP multiplexing for RTP-based "m=3D"
   sections that the answerer included in the BUNDLE group. As usage of
RTP/RTCP multiplexing is required within a BUNDLE group, the offerer
can either accept the answer and assume that RTP/RTCP multiplexing
Will be used, or reject the answer and perform proper error handling
actions (e.g., send a new offer, or terminate the whole session)."


---

>>=20
>>> -15.2, last paragraph: Is it worth recommending against patterns which
>>>could be used as persistent identifiers, even if
>>> they don=B9t expressly identify a person or application?
>>=20
>> What would they identity?
>>=20
>> Just saying "..., or could be used as persistent identifiers" sounds a
>>little half baked.
>
>As an example, assume that even though the implementation puts no
>user-identifying information in the tag, it puts some piece of
>information in there that is always the same for a given user. If someone
>manages to correlate that piece to other activity that _does_ identify
>the user, the piece becomes user-identifying.
>
>[=8A]


Isn=B9t that covered by =B3pattern=B2?

I could add say:

"The identification-tag MUST NOT contain any user information, and
applications SHALL avoid generating
   the identification-tag using a pattern that enables <new>user- or</new>
application identification.=B2


>> ---
>>=20
>>> -17, 2nd paragraph:
>>> =8B Again, is it worth mentioning the risk of persistent identifiers?
>>=20
>> See above.
>
>Ditto :-)

---

Regards,

Christer


From nobody Fri Jan 26 04:10:28 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 E709A12DA1D; Fri, 26 Jan 2018 04:10:26 -0800 (PST)
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 gq3OBDu-ot85; Fri, 26 Jan 2018 04:10:25 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC28C12D946; Fri, 26 Jan 2018 04:10:24 -0800 (PST)
X-AuditID: c1b4fb2d-b4dff70000007932-2a-5a6b1aaec343
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id EE.8A.31026.EAA1B6A5; Fri, 26 Jan 2018 13:10:23 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0352.000; Fri, 26 Jan 2018 13:10:22 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments
Thread-Index: AdOR9dB2bnAJi/LDSASEU4DilGGvkgENCYwAAB+pMYA=
Date: Fri, 26 Jan 2018 12:10:21 +0000
Message-ID: <D690E161.29E33%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C13312E@ESESSMB109.ericsson.se> <D86D82FD-663E-4A23-9742-19F577DEDCB1@nostrum.com>
In-Reply-To: <D86D82FD-663E-4A23-9742-19F577DEDCB1@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: [153.88.183.20]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <9F2922EBA17DDF4C81A7299CDC565650@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7q+56qewog3ltHBbzO0+zW5x4/43V YuryxywOzB5Llvxk8pi18wlLAFMUl01Kak5mWWqRvl0CV8a2rU9YCx5JVsz5MZu1gfGhSBcj J4eEgInE0YavbF2MXBxCAocZJd7M+s0O4SxhlHh4r4mxi5GDg03AQqL7nzZIg4iAksTz5q0s IDXMAhMZJR4tWMQCkhAWSJO4ufUuK0RRusTE8yvZIWwrib49c8FsFgFViWuT3zCB2LwC1hKf vp2E2tzEKDHzZS/YIE4Be4kzD++BDWIUEJP4fmoNWAOzgLjErSfzmSDOFpBYsuc8M4QtKvHy 8T+welEBPYkNJ26zQ8QVJa5OXw7VayDx/tx8ZgjbWqLr6CQoW1ti2cLXzBAHCUqcnPmEZQKj +Cwk62YhaZ+FpH0WkvZZSNoXMLKuYhQtTi0uzk03MtZLLcpMLi7Oz9PLSy3ZxAiMvoNbfuvu YFz92vEQowAHoxIPbzV/dpQQa2JZcWXuIUYJDmYlEV4zTqAQb0piZVVqUX58UWlOavEhRmkO FiVx3pOevFFCAumJJanZqakFqUUwWSYOTqkGxgD9vNXxckWmV2zKTof9+PnRSDpyvZb+n9Uc Nu/0OttZ77jf8VrT6sT+KXmGVJTzjILgydNNTV9NyjoTuUSpqoAzfOY/diG9C/5HD22uinrr tWvl+ZQrTF3q3laMX7ysTzX9rfh/and/t9KfFZMFFh299PrtQxY3u5q9Rz6X9t3weXyC0XpR qhJLcUaioRZzUXEiAGZ7Yd+6AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vzcCxC9rOdfwbM7X89Z2y8OqWxU>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments
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, 26 Jan 2018 12:10:27 -0000

Hi,

Please see inline.

>>>- Terminology issues: I think some of the terminology here will confuse
>>>readers who are new to the concepts.
>>> In particular, IIUC, =B3bundle address=B2 means address + port. I think
>>>many readers will fall back to assuming that
>>> address means IP address. (Especially when we talk about a =B3unique
>>>address=B2 assigned to an m=3D section, when
>>> much of the time that may just mean a unique port.)
>>=20
>> Section 2 does define "bundle address" as an address:port combination.
>
>Yes, it does=8Bbut the redefinition of a well-known term often fails to
>stick in people=B9s heads.
>
>>=20
>> But, I see your point.
>>=20
>> Would "bundle address-port", "bundle addressport", "bundle addrprt", or
>>something similar, be better? I don't want to say "bundle address:port
>>combination" in every instance=8A
>
>I struggled with a suggestion when I originally wrote the comment, and
>didn=B9t come up with something I liked. =B3Transport=B2 seems descriptive=
, but
>there=B9s similarly well-known usage of that that doesn=B9t quite match.
>Maybe =B3bundle address:port=B2?

It has previously been suggested to use =B3BUNDLE transport=B2, but that co=
uld
mean that other things have to be changed too. =B3BUNDLE address:port=B2 wo=
uld
be a smaller and "safer" change, so if you are ok with that...

---

>>> =8B 2nd to last paragraph, =B3The procedures in this specification appl=
y
>>>independently to a given BUNDLE group.=B2 : I don=B9t
>>> understand what that sentence is trying to convey.
>>=20
>> I says that, if your SDP contains multiple BUNDLE groups, the
>>procedures are applied independently to each of them.
>
>How about =B3If an SDP offer or answer contains multiple BUNDLE groups, th=
e
>procedures in this specification apply to each group independently.=B2?

Ok. I will fix as suggested.

---

>>=20
>>> -8.2.1, first paragraph:
>>> =8B The phrase =B3represented by the =8A BUNDLE-tag=B2 occurs repeatedl=
y
>>>throughout the document. The use of =B3represented=B2 there
>>> seems awkward. I think =B3indicated=B2 would be a better word choice.
>>=20
>> This is one of the words that have been changed multiple times
>>throughout the work of the document...
>>=20
>> I can see whether your suggestion can be done with a search/replace,
>>but if it requires more than that I would not like to do it.
>>=20
>
>Okay

I had a quick look, and I think I could replace with "indicated".

---

>>> =8B last paragraph: It may be worth clarifying that this doesn't change
>>>any requirement specified by the
>>> application or signaling protocol. For example, WebRTC still requires
>>>ICE even though bundle is used.
>>=20
>> Question for clarification: Do you want to say that some applications
>>might mandate ICE even if BUNDLE is not used, or that some applications
>>might mandate support of ICE together with BUNDLE?
>
>The latter..

What about:

"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."



Regards,

Christer


From nobody Fri Jan 26 07:25:59 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 8E6ED124234; Fri, 26 Jan 2018 07:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNWHeAmqwWsR; Fri, 26 Jan 2018 07:25:53 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E27C11241FC; Fri, 26 Jan 2018 07:25:52 -0800 (PST)
X-AuditID: c1b4fb3a-34dff700000037f2-82-5a6b487e88a6
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id BD.C2.14322.E784B6A5; Fri, 26 Jan 2018 16:25:50 +0100 (CET)
Received: from [100.94.37.49] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.57) with Microsoft SMTP Server (TLS) id 14.3.352.0; Fri, 26 Jan 2018 16:25:50 +0100
To: Ben Campbell <ben@nostrum.com>
CC: <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
References: <68E80650-0B78-4F4A-9339-BF6FE360FC8B@nostrum.com> <4fad2816-976b-4d4b-2fec-9b496375d0a6@ericsson.com> <3C5E3CED-2E54-4B56-B378-8421EB05F1FD@nostrum.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <2cbf93ae-f49d-f902-a736-c255b675db5e@ericsson.com>
Date: Fri, 26 Jan 2018 16:25:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <3C5E3CED-2E54-4B56-B378-8421EB05F1FD@nostrum.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms070702070908030002050005"
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrAIsWRmVeSWpSXmKPExsUyM2K7pW6dR3aUwYKP1hbzO0+zW5x4/43V YuryxywOzB5Llvxk8pi18wlLAFMUl01Kak5mWWqRvl0CV8bzU9wFG1uYKlqb/RoY+68ydjFy ckgImEg8fX2PCcQWEjjMKNF+Kg3C3sgosWuGJIgtLBAi0XdpPViNiICSxPPmrSwgNrNAuMSW GYsZIepXMkq8nMYNYrMJWEjc/NHI1sXIwcErYC+xsN0EJMwioCrR/rAXrFVUIEZiQfMhZhCb V0BQ4uTMJ2BxTqDyybPeAq3iAhrfzSjRdfIXM8R8bYmGpg5WiJuVJK7Pu84ygVFgFpL+Wch6 ZoHdFyZxYP9KJghbXKLpy0pWCNtMYt7mh1A12hLLFr4GsjmAbDWJZa1KqMIgtrXEjF8H2SBs RYkp3Q/ZIWxTiddHPzJC2EYS7/Y0si9g5FnFKFqcWlycm25kpJdalJlcXJyfp5eXWrKJERh3 B7f8ttrBePC54yFGAQ5GJR7epZbZUUKsiWXFlbmHGFWA5jzasPoCoxRLXn5eqpIIrxknUJo3 JbGyKrUoP76oNCe1+BCjNAeLkjivU5pFlJBAemJJanZqakFqEUyWiYNTqoFxzbqHcuf/2/lV rJNUSftwWFHy7/byaK1DvPe8bx7a5PFLflKN5t6JX04Izd0455La7rcWEtmLZP3N53n5fC44 8aq1Z+ncnqRpCy8+XnxGsvrRlCDzxitbtyr1XhPW72vZvJGp6VhH3nnfjL4/eocXPbn9z+ZL 8OfaTN7K9ZleuZP23y6bnMiqpcRSnJFoqMVcVJwIAP/XVGrDAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vWeurufKqtO_DnFaKujFD-V1e74>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47
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, 26 Jan 2018 15:25:57 -0000

--------------ms070702070908030002050005
Content-Type: multipart/alternative;
 boundary="------------74CAF1A5A85F004756F05FC2"
Content-Language: en-GB

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

Hi,

See inline for response and text proposals.


Den 2018-01-25 kl. 23:35, skrev Ben Campbell:
>
>> On Jan 25, 2018, at 8:04 AM, Magnus Westerlund <magnus.westerlund@eric=
sson.com> wrote:
>>
>> Hi,
>>
>> Christer invoked me on the RTP related questions. Here are my views on=
 these three issues.
>>
>>
>> Den 2018-01-24 kl. 12:46, skrev Christer Holmberg:
>>>
>>> TEXT (Section 10.2):
>>>
>>> However, some implementations may not include this identification-tag=

>>>      in their RTP and RTCP traffic when using the BUNDLE mechanism, a=
nd
>>>      instead use a payload type based mechanism to associate RTP stre=
ams
>>>      with SDP "m=3D" sections.  In this situation, each "m=3D" sectio=
n MUST
>>>      use unique payload type values, in order for the payload type to=
 be a
>>>      reliable indicator of the relevant "m=3D" section for the RTP st=
ream.
>>>      Note that when using the payload type to associate RTP streams w=
ith
>>>      "m=3D" sections an RTP stream, identified by its SSRC, will be m=
apped
>>>      to an "m=3D" section when the first packet of that RTP stream is=

>>>      received, and the mapping will not be changed even if the payloa=
d
>>>      type used by that RTP stream changes.  In other words, the SSRC
>>>      cannot "move" to a different "m=3D" section simply by changing t=
he
>>>      payload type.
>>>
>>>
>>>
>>>> -10.2,
>>>> =E2=80=B9 paragraph 7: What implementations are we talking about tha=
t may not
>>>> follow the requirements to include the tag in RTP/RTCP? Early
>>>> implementations of this draft? Something else? As it is, it seems li=
ke we
>>>> are talking about implementations that do not follow this spec. That=

>>>> makes the statement =C2=B3  =C5=A0 In this situation, each "m=3D" se=
ction MUST use
>>>> unique payload type values=C5=A0=C2=B2 problematic, as it seems to b=
e putting
>>>> requirements on implementations that do not follow this draft in the=

>>>> first place.
>> Yes, this is a form of legacy adaptations. It applies towards certain =
existing systems that already follows this rule. This include 3GPP MTSI c=
lients. It also applies to clients where the signalling system or the sig=
nalling part of the client can be updated to follow this requirement. In =
some cases also middleboxes or gateways can have functionality for PT rew=
riting, but lack capability of inserting the id-tag.
>>
>> So, a MUST where you either follow this requirement, or it will simply=
 not work at all. It can likely be rewritten either without a MUST, or wi=
th an explanation that this is just stating a hard requirement for making=
 it work.
> I think that could work for me, but would like to see it in text before=
 commiting :-)

So my proposed text is:

 =C2=A0=C2=A0 However, some legacy implementations may not include this=20
identification-tag
 =C2=A0=C2=A0 in their RTP and RTCP traffic when using the BUNDLE mechani=
sm, and
 =C2=A0=C2=A0 instead use a payload type based mechanism to associate RTP=
 streams
 =C2=A0=C2=A0 with SDP "m=3D" sections.=C2=A0 In this situation, each "m=3D=
" section needs to
 =C2=A0=C2=A0 use unique payload type values, in order for the payload ty=
pe to be a
 =C2=A0=C2=A0 reliable indicator of the relevant "m=3D" section for the R=
TP stream.=20
If an
 =C2=A0=C2=A0 implementation fails to ensure unique payload type values i=
t will be
 =C2=A0=C2=A0 impossible to associate the RTP stream using that payload t=
ype value
 =C2=A0=C2=A0 to a particular "m=3D" section.
 =C2=A0=C2=A0 Note that when using the payload type to associate RTP stre=
ams with
 =C2=A0=C2=A0 "m=3D" sections an RTP stream, identified by its SSRC, will=
 be mapped
 =C2=A0=C2=A0 to an "m=3D" section when the first packet of that RTP stre=
am is
 =C2=A0=C2=A0 received, and the mapping will not be changed even if the p=
ayload
 =C2=A0=C2=A0 type used by that RTP stream changes.=C2=A0 In other words,=
 the SSRC
 =C2=A0=C2=A0 cannot "move" to a different "m=3D" section simply by chang=
ing the
 =C2=A0=C2=A0 payload type.


>>> ----
>>>
>>> TEXT (Section 10.2):
>>>
>>> Note that if an SDES packet is received as part of a compound RTCP
>>>         packet, the SSRC to "m=3D" section mapping may not exist unti=
l the
>>>         SDES packet is handled (e.g., in the case where RTCP for a so=
urce
>>>         is received before any RTP packets).  Therefore, when process=
ing a
>>>         compound packet, any contained SDES packet MUST be handled fi=
rst.
>>>         Note that this is a change from [RFC3550] Section 6.1, which
>>>         states that "Each individual RTCP packet in the compound pack=
et
>>>         may be processed independently with no requirements upon the =
order
>>>         or combination of packets".
>>>
>>>
>>>
>>>> =E2=80=B9 '  Therefore, when processing a compound packet, any conta=
ined SDES
>>>> packet MUST be handled first.
>>>>        Note that this is a change from [RFC3550] Section 6.1 which
>>>>        states that "Each individual RTCP packet in the compound pack=
et
>>>>        may be processed independently with no requirements upon the =
order
>>>>        or combination of packets=C2=B2.=C2=B9
>>>>
>>>> Doesn=C2=B9t this require an update of 3550? It=C2=B9s not merely a =
tightening of
>>>> requirements, it=C2=B9s a reversal of guidance from that document wh=
en used in
>>>> this context.
>> Looking at this now, I think this formulation may be a bit unnecessari=
ly strict. If one fails to process the SDES item with the ID-tag in a tim=
ely fashion, i.e. prior to needing to route any other information element=
 to the consumer, the only implication is that either the element is dela=
yed or discarded. In the case discussed here, also the ID-tag will likely=
 to have been processed before the arrival of the RTP packets.
>>
>> I would suggest that that the MUST is changed to an implementation not=
e that simply recommends implementations to prioritize processing of the =
SDES item, or otherwise consider methods for holding the routing for the =
other elements for a new non-associated SSRC until the SDES item(s) have =
been processed.
> That seems reasonable.

So text proposal for this item:

OLD:
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that if an SDES packet is received a=
s part of a compound RTCP
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packet, the SSRC to "m=3D" section mappin=
g may not exist until the
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDES packet is handled (e.g., in the case=
 where RTCP for a source
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is received before any RTP packets).=C2=A0=
 Therefore, when processing a
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 compound packet, any contained SDES packe=
t MUST be handled first.
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that this is a change from [RFC3550]=
 Section 6.1, which
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that "Each individual RTCP packet =
in the compound packet
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 may be processed independently with no re=
quirements upon the order
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 or combination of packets".


NEW:
 =C2=A0=C2=A0 =C2=A0=C2=A0 Note that if an SDES packet is received as par=
t of a compound RTCP
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packet, the SSRC to "m=3D" section mappin=
g might not exist until the
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDES packet is handled (e.g., in the case=
 where RTCP for a source
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is received before any RTP packets). Ther=
efore, it can be beneficial
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 for an implementation to delay RTCP packe=
t routing, such that it
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 either prioritizes processing of the SDES=
 item to generate or update
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the mapping, or buffers the RTCP informat=
ion that needs to be
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 routed until the SDES item(s) has been pr=
ocessed. If the
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 implementation is unable to follow this r=
ecommendation, the
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 consequence could be that some RTCP infor=
mation from this
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 particular RTCP compound packet is not pr=
ovided to higher layers.
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The impact from this is likely minor, whe=
n this information relates
 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 to a future incoming RTP stream.


>
>>> ----
>>>
>>> TEXT (Section 17):
>>>
>>> The security considerations of "RTP Header Extension for the RTP
>>>      Control Protocol (RTCP) Source Description Items" [RFC7941] requ=
ires
>>>      that when RTCP is confidentiality protected, and that any SDES R=
TP
>>>      header extension carrying an SDES item, such as the MID RTP head=
er
>>>      extension, is also protected using commensurate strength algorit=
hms.
>>>      However, assuming the above requirements and recommendations are=

>>>      followed, there are no known significant security risks with lea=
ving
>>>      the MID RTP header extension without confidentiality protection.=

>>>      Thus, the requirements in RFC 7941 MAY be ignored for the MID RT=
P
>>>      header extension.  Security mechanisms for RTP/RTCP are discusse=
d in
>>>      Options for Securing RTP Sessions [RFC7201], for example SRTP
>>>      [RFC3711] can provide the necessary security functions of ensuri=
ng
>>>      the integrity and source authenticity.
>>>
>>>
>>>> -17, last paragraph: Doesn=C2=B9t that require an update to 7941
>> Maybe a question of style in how one handles exceptions. I would not u=
pdate 7941, as the general rule still holds. But in this particular case =
the exception is motivated for this particular SDES item, and that is doc=
umented and agreed on (when RFC is published).
> I=E2=80=99m not sure I agree. This adds an exception to a security rela=
ted MUST from 7941. While I recognize that it may be safe to do that, I t=
hink it still requires an update. That doesn=E2=80=99t even have to be a =
generic update; something along the line of =E2=80=9CThis document update=
s $FC 7941 to add an exception to that requirement for the MID extension=E2=
=80=9D.
>
>

I have no real issue with an Updates, as long as it is clear that this=20
is just to note that there was an exception.

Has IESG clarified in statement or RFC the use of updates, especially in =

these cases when it comes to overriding RFC2119 language of earlier=20
RFCs? From my perspective this has as long as I been active in IETF a=20
bit unclear.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


--------------74CAF1A5A85F004756F05FC2
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=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi,</p>
    <p>See inline for response and text proposals.<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">Den 2018-01-25 kl. 23:35, skrev Ben
      Campbell:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:3C5E3CED-2E54-4B56-B378-8421EB05F1FD@nostrum.com">
      <pre wrap=3D"">

</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">On Jan 25, 2018, at 8:04 AM, Magnus Westerlund <a =
class=3D"moz-txt-link-rfc2396E" href=3D"mailto:magnus.westerlund@ericsson=
=2Ecom">&lt;magnus.westerlund@ericsson.com&gt;</a> wrote:

Hi,

Christer invoked me on the RTP related questions. Here are my views on th=
ese three issues.


Den 2018-01-24 kl. 12:46, skrev Christer Holmberg:
</pre>
        <blockquote type=3D"cite">
          <pre wrap=3D"">

TEXT (Section 10.2):

However, some implementations may not include this identification-tag
    in their RTP and RTCP traffic when using the BUNDLE mechanism, and
    instead use a payload type based mechanism to associate RTP streams
    with SDP "m=3D" sections.  In this situation, each "m=3D" section MUS=
T
    use unique payload type values, in order for the payload type to be a=

    reliable indicator of the relevant "m=3D" section for the RTP stream.=

    Note that when using the payload type to associate RTP streams with
    "m=3D" sections an RTP stream, identified by its SSRC, will be mapped=

    to an "m=3D" section when the first packet of that RTP stream is
    received, and the mapping will not be changed even if the payload
    type used by that RTP stream changes.  In other words, the SSRC
    cannot "move" to a different "m=3D" section simply by changing the
    payload type.



</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">-10.2,
=E2=80=B9 paragraph 7: What implementations are we talking about that may=
 not
follow the requirements to include the tag in RTP/RTCP? Early
implementations of this draft? Something else? As it is, it seems like we=

are talking about implementations that do not follow this spec. That
makes the statement =C2=B3  =C5=A0 In this situation, each "m=3D" section=
 MUST use
unique payload type values=C5=A0=C2=B2 problematic, as it seems to be put=
ting
requirements on implementations that do not follow this draft in the
first place.
</pre>
          </blockquote>
        </blockquote>
        <pre wrap=3D"">
Yes, this is a form of legacy adaptations. It applies towards certain exi=
sting systems that already follows this rule. This include 3GPP MTSI clie=
nts. It also applies to clients where the signalling system or the signal=
ling part of the client can be updated to follow this requirement. In som=
e cases also middleboxes or gateways can have functionality for PT rewrit=
ing, but lack capability of inserting the id-tag.

So, a MUST where you either follow this requirement, or it will simply no=
t work at all. It can likely be rewritten either without a MUST, or with =
an explanation that this is just stating a hard requirement for making it=
 work.
</pre>
      </blockquote>
      <pre wrap=3D"">
I think that could work for me, but would like to see it in text before c=
ommiting :-)
</pre>
    </blockquote>
    <br>
    So my proposed text is:<br>
    <br>
    =C2=A0=C2=A0 However, some legacy implementations may not include thi=
s
    identification-tag<br>
    =C2=A0=C2=A0 in their RTP and RTCP traffic when using the BUNDLE mech=
anism,
    and<br>
    =C2=A0=C2=A0 instead use a payload type based mechanism to associate =
RTP
    streams<br>
    =C2=A0=C2=A0 with SDP "m=3D" sections.=C2=A0 In this situation, each =
"m=3D" section
    needs to<br>
    =C2=A0=C2=A0 use unique payload type values, in order for the payload=
 type to
    be a<br>
    =C2=A0=C2=A0 reliable indicator of the relevant "m=3D" section for th=
e RTP
    stream. If an<br>
    =C2=A0=C2=A0 implementation fails to ensure unique payload type value=
s it will
    be <br>
    =C2=A0=C2=A0 impossible to associate the RTP stream using that payloa=
d type
    value<br>
    =C2=A0=C2=A0 to a particular "m=3D" section. <br>
    =C2=A0=C2=A0 Note that when using the payload type to associate RTP s=
treams
    with<br>
    =C2=A0=C2=A0 "m=3D" sections an RTP stream, identified by its SSRC, w=
ill be
    mapped<br>
    =C2=A0=C2=A0 to an "m=3D" section when the first packet of that RTP s=
tream is<br>
    =C2=A0=C2=A0 received, and the mapping will not be changed even if th=
e payload<br>
    =C2=A0=C2=A0 type used by that RTP stream changes.=C2=A0 In other wor=
ds, the SSRC<br>
    =C2=A0=C2=A0 cannot "move" to a different "m=3D" section simply by ch=
anging the<br>
    =C2=A0=C2=A0 payload type.<br>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3C5E3CED-2E54-4B56-B378-8421EB05F1FD@nostrum.com">
      <pre wrap=3D"">
</pre>
      <blockquote type=3D"cite">
        <blockquote type=3D"cite">
          <pre wrap=3D"">----

TEXT (Section 10.2):

Note that if an SDES packet is received as part of a compound RTCP
       packet, the SSRC to "m=3D" section mapping may not exist until the=

       SDES packet is handled (e.g., in the case where RTCP for a source
       is received before any RTP packets).  Therefore, when processing a=

       compound packet, any contained SDES packet MUST be handled first.
       Note that this is a change from [RFC3550] Section 6.1, which
       states that "Each individual RTCP packet in the compound packet
       may be processed independently with no requirements upon the order=

       or combination of packets".



</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">=E2=80=B9 '  Therefore, when processing a comp=
ound packet, any contained SDES
packet MUST be handled first.
      Note that this is a change from [RFC3550] Section 6.1 which
      states that "Each individual RTCP packet in the compound packet
      may be processed independently with no requirements upon the order
      or combination of packets=C2=B2.=C2=B9

Doesn=C2=B9t this require an update of 3550? It=C2=B9s not merely a tight=
ening of
requirements, it=C2=B9s a reversal of guidance from that document when us=
ed in
this context.
</pre>
          </blockquote>
        </blockquote>
        <pre wrap=3D"">
Looking at this now, I think this formulation may be a bit unnecessarily =
strict. If one fails to process the SDES item with the ID-tag in a timely=
 fashion, i.e. prior to needing to route any other information element to=
 the consumer, the only implication is that either the element is delayed=
 or discarded. In the case discussed here, also the ID-tag will likely to=
 have been processed before the arrival of the RTP packets.

I would suggest that that the MUST is changed to an implementation note t=
hat simply recommends implementations to prioritize processing of the SDE=
S item, or otherwise consider methods for holding the routing for the oth=
er elements for a new non-associated SSRC until the SDES item(s) have bee=
n processed.
</pre>
      </blockquote>
      <pre wrap=3D"">
That seems reasonable.</pre>
    </blockquote>
    <br>
    So text proposal for this item: <br>
    <br>
    OLD:<br>
    <tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that if an SDES packet is rec=
eived as part of a
      compound RTCP</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packet, the SSRC to "m=3D" se=
ction mapping may not
      exist until the</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDES packet is handled (e.g.,=
 in the case where RTCP
      for a source</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is received before any RTP pa=
ckets).=C2=A0 Therefore, when
      processing a</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 compound packet, any containe=
d SDES packet MUST be
      handled first.</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Note that this is a change fr=
om [RFC3550] Section
      6.1, which</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 states that "Each individual =
RTCP packet in the
      compound packet</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 may be processed independentl=
y with no requirements
      upon the order</tt><tt><br>
    </tt><tt>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 or combination of packets".</=
tt><br>
    <br>
    <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:"Segoe UI";
	panose-1:2 11 5 2 4 2 4 2 2 3;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:8.0pt;
	margin-left:0cm;
	line-height:107%;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
=2EMsoChpDefault
	{font-family:"Calibri",sans-serif;}
=2EMsoPapDefault
	{margin-bottom:8.0pt;
	line-height:107%;}
 /* Page Definitions */
 @page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
    <div class=3D"WordSection1">
      <br>
      <tt><span style=3D"font-size: 12pt;">NEW:</span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;">
          =C2=A0=C2=A0 =C2=A0=C2=A0 Note that if an SDES packet is receiv=
ed as part of a
          compound RTCP</span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;">
          =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 packet, the SSRC to "m=3D" secti=
on
          mapping might not exist until the</span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;">
          =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 SDES packet is handled (e.g., in=
 the case where
          RTCP for a source</span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;">
          =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is received before any RTP packe=
ts). Therefore,
          it can be beneficial </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 for an
          implementation to delay RTCP packet routing, such
          that it </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;"></span></tt><tt><span
          style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 eithe=
r prioritizes processing
          of the SDES item to generate or update </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;"></span></tt><tt><span
          style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the m=
apping, or buffers the
          RTCP information that needs to be </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;"></span></tt><tt><span
          style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 route=
d until the
          SDES item(s) has been processed. If the </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;"></span></tt><tt><span
          style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 imple=
mentation is unable to
          follow this
          recommendation, the </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;"></span></tt><tt><span
          style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 conse=
quence could be that some
          RTCP information from this </span></tt><tt><br>
      </tt><tt></tt><tt><span style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 particular
          RTCP compound packet is not provided to higher layers.</span></=
tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 The impact from this
          is likely
          minor, when this information relates </span></tt><tt><br>
      </tt><tt><span style=3D"font-size: 12pt;"></span></tt><tt><span
          style=3D"font-size: 12pt;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 to a =
future incoming RTP
          stream.</span></tt><span
        style=3D"font-size:10.0pt;font-family:&quot;Segoe
        UI&quot;,sans-serif;color:black"> </span>
      <div class=3D"WordSection1">
      </div>
    </div>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:3C5E3CED-2E54-4B56-B378-8421EB05F1FD@nostrum.com">
      <pre wrap=3D"">

</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">
</pre>
        <blockquote type=3D"cite">
          <pre wrap=3D"">
----

TEXT (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.
    However, assuming the above requirements and recommendations are
    followed, there are no known significant security risks with leaving
    the MID RTP header extension without confidentiality protection.
    Thus, the requirements in RFC 7941 MAY be ignored for the MID RTP
    header extension.  Security mechanisms for RTP/RTCP are discussed in
    Options for Securing RTP Sessions [RFC7201], for example SRTP
    [RFC3711] can provide the necessary security functions of ensuring
    the integrity and source authenticity.


</pre>
          <blockquote type=3D"cite">
            <pre wrap=3D"">-17, last paragraph: Doesn=C2=B9t that require=
 an update to 7941
</pre>
          </blockquote>
        </blockquote>
        <pre wrap=3D"">
Maybe a question of style in how one handles exceptions. I would not upda=
te 7941, as the general rule still holds. But in this particular case the=
 exception is motivated for this particular SDES item, and that is docume=
nted and agreed on (when RFC is published).
</pre>
      </blockquote>
      <pre wrap=3D"">
I=E2=80=99m not sure I agree. This adds an exception to a security relate=
d MUST from 7941. While I recognize that it may be safe to do that, I thi=
nk it still requires an update. That doesn=E2=80=99t even have to be a ge=
neric update; something along the line of =E2=80=9CThis document updates =
$FC 7941 to add an exception to that requirement for the MID extension=E2=
=80=9D.


</pre>
    </blockquote>
    <br>
    I have no real issue with an Updates, as long as it is clear that
    this is just to note that there was an exception. <br>
    <br>
    Has IESG clarified in statement or RFC the use of updates,
    especially in these cases when it comes to overriding RFC2119
    language of earlier RFCs? From my perspective this has as long as I
    been active in IETF a bit unclear.<br>
    <br>
    Cheers<br>
    <pre class=3D"moz-signature" cols=3D"72">
Magnus Westerlund=20

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"moz-txt-link-abbreviate=
d" href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@erics=
son.com</a>
----------------------------------------------------------------------</p=
re>
  </body>
</html>

--------------74CAF1A5A85F004756F05FC2--

--------------ms070702070908030002050005
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-kryptografisk signatur

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DNEwggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJ
BgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNV
BAoMCEVyaWNzc29uMRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJ
ARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+
laqg5eXTqonqnzT9ykEGL2dx9mBT+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJ
HGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iV
IiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpigGFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36o
gzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkrbdmdnjKGrYSnJigmxw14pJugxL/Vb2Ee
VcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDov
L2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNybDCBggYI
KwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29t
MEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29u
bmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rlcmx1bmRAZXJp
Y3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0
dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3
DQEBCwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4Q
ihhoQR3cvhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXD
yF9mhWYbSAkJyx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6
H3zO3nsq++KBmsOiSKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvE
lup5n7l864FqxnC2friDo4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl
60rmc8SJlt6QXKw0wXEOE1MubauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwD
ig3SZi1qP7D/Ds4V+JLIjjUJc25l9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8K
v7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLCQaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3
UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Zla71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzY
VBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd//n4YbY2QhDCCBsIwggSqoAMCAQICEFO4
foPhnJkok7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUx
MDI3MTIxNjQ2WjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMM
HEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDs8t8AALhQ8qe72FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfS
Tm+7meisbhkqUXkL7fFzoe4iIZCh/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbX
ILlLhRummTdDdxhVW4Leo0awEhfLf98MvWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfp
VdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmdvkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2
PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2
H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP1UrZaEIFu+hO+s0Nm8sOUMa4TlG4
rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0FdQDEzQlnF/h1L4AK1MOkX
1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA+yrrplCh/kYvSBjv
Zibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUrrvijPDaGK5FN
VSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQwgYoGCCsG
AQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEu
Y29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3Js
LTMudHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1Ud
JQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7
GZ6XnHasID3Y3OORauPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0G
CSqGSIb3DQEBCwUAA4ICAQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDU
JQEPRs5QtaZiObNHCZ7mmSNMVek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHG
vw5RY6vRlZrj0uKvdASzYL4KMaB7m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYn
nl2t3D3oBX2NZCQysshUcqRdUbkS13HTCIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwf
ixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNMMbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ8
5AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4Hd
Dc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0RLCi+4d4/47Zs3DC3PUNOxdOE
EHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZfAFM4HoHz8K2BZRaHKWhd
3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqGahxlHYzl/QyEG/du
jp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGCAzswggM3AgEB
MFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMA0GCWCGSAFlAwQCAQUA
oIIBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAxMjYx
NTI1NDlaMC8GCSqGSIb3DQEJBDEiBCBfJabAm462GVa6B5XqJpH/IaqFkwuf8mfBNF0HYf++
1TBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjEl
MCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBlrrZreXF5
7TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMGwGCyqGSIb3DQEJEAILMV2gWzBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nz
b24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62
a3lxee0wDQYJKoZIhvcNAQEBBQAEggEAg+6wmuYcSCUWP8cY9Eu6JaoYvOG1U0GK3lZqovNf
8ZhbVTJ8TaQ4KYOdKz2i5hv0RSfKME6esUjOX1AgI03h8A7V5oLFDgmyfn5r2OlCdF3ZhUzF
jP0jngtJ5ZbHMPzg7XBlJrNZQlsIjtFiB3pupXlEg52Dnm5KRMYMt/F9Y85jihvs3YCTbuML
V8pXkOByvWmllWYWVFivWXGgfJcyW3GJkq59p+3SjO7DSdFEcYBKgSPs1JGMmMX3T4nTubGy
LjB+rJJFYqmBKY35LcPgcLCoC9sEqrRYkakIqHDPf51wGF5xO+67fMbVHwoZrbea7uu4tzw9
STXryPKFA4VdnwAAAAAAAA==
--------------ms070702070908030002050005--


From nobody Fri Jan 26 13:39:51 2018
Return-Path: <fandreas@cisco.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 CECD712762F; Fri, 26 Jan 2018 13:39:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Flemming Andreasen <fandreas@cisco.com>
To: <ben@nostrum.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.70.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, iesg-secretary@ietf.org, mmusic@ietf.org, Flemming Andreasen <fandreas@cisco.com>
Message-ID: <151700278983.4433.3004450658673591177.idtracker@ietfa.amsl.com>
Date: Fri, 26 Jan 2018 13:39:49 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MpZgvVE3JBC3qgBj-V95OBVTC40>
Subject: [MMUSIC] Publication has been requested for draft-ietf-mmusic-rid-13
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, 26 Jan 2018 21:39:50 -0000

Flemming Andreasen has requested publication of draft-ietf-mmusic-rid-13 as Proposed Standard on behalf of the MMUSIC working group.

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


From nobody Fri Jan 26 14:08:29 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 ADFC61200E5 for <mmusic@ietfa.amsl.com>; Fri, 26 Jan 2018 14:08:27 -0800 (PST)
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 4EuVB_A1AIwx for <mmusic@ietfa.amsl.com>; Fri, 26 Jan 2018 14:08:25 -0800 (PST)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001: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 8C14012711D for <mmusic@ietf.org>; Fri, 26 Jan 2018 14:08:25 -0800 (PST)
Received: by mail-io0-x22f.google.com with SMTP id p188so1929884ioe.12 for <mmusic@ietf.org>; Fri, 26 Jan 2018 14:08:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=emk0TZPen3cW2YGGPpY11Cj8YRm5TPoehJxYwF44gb8=; b=gbb1oYW+8vcxSjKVYlBhLYGtzGvZc6cZ00N0P0XFHxNl+IlmIsfLdDy7HFWtw21NLR LFtv8hBnFJE+Oh50V8oIc6wMMFzrqbmLRF6mhs/7NJoUXMIUpxao/BEH9ZvN5BcifEpc oXaaxJc9zUowulLdCee7IH2vc4SeZlvsvOLBc=
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:message-id:date :user-agent:mime-version:in-reply-to; bh=emk0TZPen3cW2YGGPpY11Cj8YRm5TPoehJxYwF44gb8=; b=kXAmlhkChVm9mv+AJkXePgjhBGkV4Qp6qHMAHI4RzpDbeGm3a04bDU8em3ob3e/0ee fdY4bhf1PQ9Cv/Bp573RS9DyfriGlRTXEpT0aYh1QMa6RUSvZQqnSMph5VyFksvoPeDT nv2+tk4V1Wq30Kxz5QCQzFcFabbznhAVUGhxHTAnQbO/FUbwd2v2BZtyvei0I8ddVYU7 bHweGGs0fHaOGwfTHOPk+Ef42oin8NepNasrM+nkpcoO6g7muqfsHsaFNVhQEr53999r ul62a8b7xBzzjPm0o2ONtk0bmKDypZUezZoLCRG2cx51RAUWcqspN55HGTK2yTiEy/A6 /1ag==
X-Gm-Message-State: AKwxytd17NDRJRTPgMeQhacYrYa5SrKwJH0QQwXWY10wE1ZURXynG8hw lNM29GJk4/tK7xLzLE2Tp9NyzQ==
X-Google-Smtp-Source: AH8x227mb1qycCVZ5RC3BJWWflUuirCIgUGTWy28lSAQ2LD5hETQsBZpyqkz1354k3pMVQQ5e10Cwg==
X-Received: by 10.107.242.14 with SMTP id q14mr4097934ioh.211.1517004504661; Fri, 26 Jan 2018 14:08:24 -0800 (PST)
Received: from dragon.local ([76.25.3.152]) by smtp.gmail.com with ESMTPSA id y62sm281106itg.11.2018.01.26.14.08.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Jan 2018 14:08:23 -0800 (PST)
To: mmusic@ietf.org
References: <151576695623.18638.7468534003675516336.idtracker@ietfa.amsl.com>
From: Peter Saint-Andre <stpeter@mozilla.com>
Message-ID: <6c0a6e87-12b8-d5e0-3cc0-ef6ab2a7cd6e@mozilla.com>
Date: Fri, 26 Jan 2018 15:08:22 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <151576695623.18638.7468534003675516336.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TvP2N7ZJ2ciB6a7rE5BILMvbqApEvbTzB"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ElF7WyxD-yeyFZj0YBZxcuRkCkw>
Subject: Re: [MMUSIC] Last Call: <draft-ietf-mmusic-trickle-ice-sip-12.txt> (A Session Initiation Protocol (SIP) usage for Trickle ICE) to Proposed Standard
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, 26 Jan 2018 22:08:27 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--TvP2N7ZJ2ciB6a7rE5BILMvbqApEvbTzB
Content-Type: multipart/mixed; boundary="omdnr5UvUu8CALGwMDQ1lGigpUsWtpTYw";
 protected-headers="v1"
From: Peter Saint-Andre <stpeter@mozilla.com>
To: mmusic@ietf.org
Message-ID: <6c0a6e87-12b8-d5e0-3cc0-ef6ab2a7cd6e@mozilla.com>
Subject: Re: [MMUSIC] Last Call: <draft-ietf-mmusic-trickle-ice-sip-12.txt> (A
 Session Initiation Protocol (SIP) usage for Trickle ICE) to Proposed Standard
References: <151576695623.18638.7468534003675516336.idtracker@ietfa.amsl.com>
In-Reply-To: <151576695623.18638.7468534003675516336.idtracker@ietfa.amsl.com>

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

I've reviewed this document and didn't find any issues.

Peter

On 1/12/18 7:22 AM, The IESG wrote:
>=20
> The IESG has received a request from the Multiparty Multimedia Session
> Control WG (mmusic) to consider the following document: - 'A Session
> Initiation Protocol (SIP) usage for Trickle ICE'
>   <draft-ietf-mmusic-trickle-ice-sip-12.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits f=
inal
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2018-01-26. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the beginn=
ing of
> the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    The Interactive Connectivity Establishment (ICE) protocol describes =
a
>    Network Address Translator (NAT) traversal mechanism for UDP-based
>    multimedia sessions established with the Offer/Answer model.  The IC=
E
>    extension for Incremental Provisioning of Candidates (Trickle ICE)
>    defines a mechanism that allows ICE Agents to shorten session
>    establishment delays by making the candidate gathering and
>    connectivity checking phases of ICE non-blocking and by executing
>    them in parallel.
>=20
>    This document defines usage semantics for Trickle ICE with the
>    Session Initiation Protocol (SIP) and defines a new SIP Info Package=
=2E
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/ball=
ot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> The document contains these normative downward references.
> See RFC 3967 for additional information:=20
>     draft-ivov-mmusic-sdpfrag: Internet Media Type application/sdpfrag =
(None - )
>     draft-ietf-mmusic-rfc5245bis: Interactive Connectivity Establishmen=
t (ICE): A Protocol for Network Address Translator (NAT) Traversal (None =
- IETF stream)
>=20
>=20
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>=20


--omdnr5UvUu8CALGwMDQ1lGigpUsWtpTYw--

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

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

iQIzBAEBCAAdFiEENVUj07j078lgnb70ZWGMGH9oFKkFAlprptYACgkQZWGMGH9o
FKlSchAA2xZ2XLr1DapymAs9XT+JQwY0kdoH/nF5Z1m35fyHmtED4Gs4mSgr4T8D
1aFg+qGB24tr8rQrGgzyEPwCjM4yIF96yDdHjlGEmxFE/M0jWHDdYRh8hccyWBcb
fhLPwyCjkay47MiHSMqtRFWNEfO+N5EwPwJzr5hTM/AnvrIwj/cGbk0vo2LCYc1i
oYWoBkJ9PTn6rQ0oaCXMW81fYp6SRMOpR5dW2Rfqen2rnVAhRQTlWDZA199QPSss
lghkv8RFpL1+2cL3lIkq4vaT97p/yMpleK8zCBrY4dfUQ5FmSTaaB19pDNZQc+H5
d7N2LE4PsJ+7VyE0nj+bJ0HW2NpierNZ/PO4Mltu892+IBXV5zDbUiNHw+yRLXhW
JIUHxNXxkVQ/wedh5X7Li8LDUUuHKQmXeSWeq+U1sr9xX+FBIAfA1q+IZ1KBaTM+
7xf4CfwllwDF/B/+do3/5SpciOHA471Jsah72gqMAOt2iMTgzZZMu/5hjyqnxSV+
BXG+aUqqt8OmGdC/s1oCX1uonf0p5318ZQYhFlQiSKpgitLKdk+E6sJ4OJrQOjny
2RjZhK8DO2NTsOjwppSwY7HrJb5JWjL6dsIIgnaMayg52lZtPBaRPp34PQjXhW5c
B4uRC9OyV/NQcXum6C6PF+LajchLwAuWTFRau9pXQweVHUJIsQ8=
=ciqC
-----END PGP SIGNATURE-----

--TvP2N7ZJ2ciB6a7rE5BILMvbqApEvbTzB--


From nobody Mon Jan 29 13:19: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 90E3A12FB63 for <mmusic@ietfa.amsl.com>; Mon, 29 Jan 2018 13:19:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i11hCnUpFHSW for <mmusic@ietfa.amsl.com>; Mon, 29 Jan 2018 13:19:56 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF8F312DB6F for <mmusic@ietf.org>; Mon, 29 Jan 2018 13:19:55 -0800 (PST)
X-AuditID: c1b4fb2d-b35ff70000007932-c0-5a6f8ffa9f36
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 40.94.31026.AFF8F6A5; Mon, 29 Jan 2018 22:19:54 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0352.000; Mon, 29 Jan 2018 22:19:54 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: MMUSIC <mmusic@ietf.org>, Ben Campbell <ben@nostrum.com>
Thread-Topic: BUNDLE: Some updates to RFC 3264 no longer needed?
Thread-Index: AdOZRuyQe1CRoQrMRkWAE44KZEId6w==
Date: Mon, 29 Jan 2018 21:19:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C147816@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.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B6C147816ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM2K7me6v/vwog+Yl/BbzO0+zW0xd/pjF gcljyZKfTB6zdj5hCWCK4rJJSc3JLEst0rdL4MpY8pe94K5mxdV/M5kbGJtVuhg5OSQETCSW PVjF0sXIxSEkcJhRYmb3I3YIZwmjxOH9W1m7GDk42AQsJLr/aYM0iAjYSGzsv88MYgsLWEus WXScESLuILHq7m8mCFtP4u+3FWwgNouAqsT7ZR0sIDavgK9E09w2dhCbUUBM4vupNWD1zALi EreezGeCOEhAYsme88wQtqjEy8f/WCFsJYm1h7ezQNTnS7y99psRYqagxMmZT1gmMArOQjJq FpKyWUjKIOI6Egt2f2KDsLUlli18zQxjnznwmAlZfAEj+ypG0eLU4uLcdCNjvdSizOTi4vw8 vbzUkk2MwGg4uOW37g7G1a8dDzEKcDAq8fBu6cuPEmJNLCuuzD3EKMHBrCTC+6AVKMSbklhZ lVqUH19UmpNafIhRmoNFSZz3pCdvlJBAemJJanZqakFqEUyWiYNTqoHRwGzevftGAQdn/m0S KQn/7x8eFblLsHRa89mPS7a9KK3x9d7nMbdPwE4gtsH9hMGPjc/n2F3mDmfRvvD2lv62R9Z+ s2c3tS2bzs99893JTpuEqZyPXy7Z9G9ugMRBjv+t6k/ljK4XxJ1itZv4/mF8yZQSgaYMXR/P 0ikCup4Z5b2vvs90496rxFKckWioxVxUnAgAq59RrYICAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/HuLz2win-RL8rVTRNYENuoSxEfU>
Subject: [MMUSIC] BUNDLE: Some updates to RFC 3264 no longer needed?
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, 29 Jan 2018 21:19:57 -0000

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

Hi,

One thing I noted when implementing the changes based on Ben's AD review.

The Introduction section of BUNDLE says:

   "This specification also updates sections 5.1, 8.1 and 8.2 of RFC 3264
   [RFC3264].  The update allows an answerer to assign a non-zero port
   value to an "m=3D" section in an SDP answer, even if the "m=3D" section
   in the associated SDP offer contained a zero port value."

The changes are then done in Section 14.

Now, since the answerer no longer assigns the answerer BUNDLE address to al=
l m=3D sections in the answer (including m=3D sections that had a zero port=
 value in the associated offer), I actually don't think this update is need=
ed anymore. That would of course be a good thing.

(We cannot completely remove Section 14, because we will still need the upd=
ate to RFC 3264 that allows usage of port zero without disabling/rejecting =
an m=3D section.)

I will create a PR for this later, once I've dealt with Ben's review commen=
ts.. Please let me know if have any questions.

Regards,

Christer



--_000_7594FB04B1934943A5C02806D1A2204B6C147816ESESSMB109erics_
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;
	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">One thing I noted when implementing the changes base=
d on Ben&#8217;s AD review.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The Introduction section of BUNDLE says:<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; &#8220;This specification also updates =
sections 5.1, 8.1 and 8.2 of RFC 3264<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; [RFC3264].&nbsp; The update allows an a=
nswerer to assign a non-zero port<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; value to an &quot;m=3D&quot; section in=
 an SDP answer, even if the &quot;m=3D&quot; section<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; in the associated SDP offer contained a=
 zero port value.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The changes are then done in Section 14.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Now, since the answerer no longer assigns the answer=
er BUNDLE address to all m=3D sections in the answer (including m=3D sectio=
ns that had a zero port value in the associated offer), I actually don&#821=
7;t think this update is needed anymore. That
 would of course be a good thing.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">(We cannot completely remove Section 14, because we =
will still need the update to RFC 3264 that allows usage of port zero witho=
ut disabling/rejecting an m=3D section.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I will create a PR for this later, once I&#8217;ve d=
ealt with Ben&#8217;s review comments.. Please let me know if have any ques=
tions.<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>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B6C147816ESESSMB109erics_--


From nobody Mon Jan 29 13:21:45 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 8D91B12D93F; Mon, 29 Jan 2018 13:21:44 -0800 (PST)
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 GXwhyTJ2VzER; Mon, 29 Jan 2018 13:21:42 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E45912D87D; Mon, 29 Jan 2018 13:21:42 -0800 (PST)
Received: from [10.0.1.105] (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 w0TLLcOs037295 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 29 Jan 2018 15:21:39 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <CEEA53FA-E653-48B8-87CB-4350181A0C6C@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A339F1A9-C01E-4F77-A9FC-13D3F3078498"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 29 Jan 2018 15:21:37 -0600
In-Reply-To: <D690E161.29E33%christer.holmberg@ericsson.com>
Cc: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>,  MMUSIC <mmusic@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C13312E@ESESSMB109.ericsson.se> <D86D82FD-663E-4A23-9742-19F577DEDCB1@nostrum.com> <D690E161.29E33%christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/SMf6edC5IiHqWM8LgN3q2TPLEgM>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments
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, 29 Jan 2018 21:21:45 -0000

--Apple-Mail=_A339F1A9-C01E-4F77-A9FC-13D3F3078498
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 26, 2018, at 6:10 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> Please see inline.
>=20
>>>> - Terminology issues: I think some of the terminology here will =
confuse
>>>> readers who are new to the concepts.
>>>> In particular, IIUC, =C5=82bundle address=CB=9B means address + =
port. I think
>>>> many readers will fall back to assuming that
>>>> address means IP address. (Especially when we talk about a =C5=82uniq=
ue
>>>> address=CB=9B assigned to an m=3D section, when
>>>> much of the time that may just mean a unique port.)
>>>=20
>>> Section 2 does define "bundle address" as an address:port =
combination.
>>=20
>> Yes, it does=E2=80=B9but the redefinition of a well-known term often =
fails to
>> stick in people=C4=85s heads.
>>=20
>>>=20
>>> But, I see your point.
>>>=20
>>> Would "bundle address-port", "bundle addressport", "bundle addrprt", =
or
>>> something similar, be better? I don't want to say "bundle =
address:port
>>> combination" in every instance=C5=A0
>>=20
>> I struggled with a suggestion when I originally wrote the comment, =
and
>> didn=C4=85t come up with something I liked. =C5=82Transport=CB=9B =
seems descriptive, but
>> there=C4=85s similarly well-known usage of that that doesn=C4=85t =
quite match.
>> Maybe =C5=82bundle address:port=CB=9B?
>=20
> It has previously been suggested to use =C5=82BUNDLE transport=CB=9B, =
but that could
> mean that other things have to be changed too. =C5=82BUNDLE =
address:port=CB=9B would
> be a smaller and "safer" change, so if you are ok with that=E2=80=A6
>=20

Okay

[=E2=80=A6]
> ---
>=20
>>>> =E2=80=B9 last paragraph: It may be worth clarifying that this =
doesn't change
>>>> any requirement specified by the
>>>> application or signaling protocol. For example, WebRTC still =
requires
>>>> ICE even though bundle is used.
>>>=20
>>> Question for clarification: Do you want to say that some =
applications
>>> might mandate ICE even if BUNDLE is not used, or that some =
applications
>>> might mandate support of ICE together with BUNDLE?
>>=20
>> The latter..
>=20
> What about:
>=20
> "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."
>=20
>=20

WFM.

Thanks!

Ben.

--Apple-Mail=_A339F1A9-C01E-4F77-A9FC-13D3F3078498
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpvkGEACgkQgFZKbJXz
1A2bQQ/+OLOINr2Qp7Pv5048TWdRmOI8hWKpVA+wnd3V2fLw1d2XLeXAIayKy1ux
b1ih7x+w6+Gyui1k4KZ7uWr6AkMtRHTo4qNz4z57RjRnwutmjfOfeqCat6/VYU3z
npfDz5LPCKlAQKRccatcoo/z70wjyPXPhytvjsL3G9B6X1vjjA7O7Ip7d7xXDVkx
AcfwrQy29fkiDQl+Fdvn+ON+q+9mcz0swFH3rvRRCrP9saI0GMXkV7kJYtFWlUX1
2lGNmbSbfmFNoAYQZTWpMg6RurrsxEsTVkJQLhO/hcdhAL89Qm+cb3t1dNRs2C4R
URxi4moY5yKoeIsMfVc1q4JFRg0ZBui83m0BaA83CCTNjPb5qUj3qYvNaK9ejyGC
bVOjT7wGfq1z1qiwssa1yNLSHgvG+o3vUnCQBbzomNq2Mpw2aaAbtQEoSalaW9KB
NFlLQEmvVlG6YcAs3l8Cwura73Pc+hqfukgF3h4KyLwkGrEQyfg58LLF7z6dzECQ
RTOAITzOMIanVcQ6fv7iEbG2GIWLUlZR/mgv560tU37YEsXkXG7kxlKQ+n1DBn0b
eubk/jsVgzVVEgo4UWfVzg4IljSII38fT2urifJtOxat8DJZ3eku5UwrOJutzvTs
zaieB0vExowo4Oxxl59ZWtIu0GOW+7IpaIllCBs/AWYU6WqDf5M=
=nsLb
-----END PGP SIGNATURE-----

--Apple-Mail=_A339F1A9-C01E-4F77-A9FC-13D3F3078498--


From nobody Mon Jan 29 13:33:23 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 822CF12D7E5; Mon, 29 Jan 2018 13:33:22 -0800 (PST)
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 KcqJielbaTYY; Mon, 29 Jan 2018 13:33:20 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5228F1267BB; Mon, 29 Jan 2018 13:33:20 -0800 (PST)
Received: from [10.0.1.105] (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 w0TLXG8V038649 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 29 Jan 2018 15:33:17 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <44296CB2-58BB-4017-B75C-87E149B17B7F@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_04BAE6C3-B7A7-4F40-80C1-0A577EF678F4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Mon, 29 Jan 2018 15:33:15 -0600
In-Reply-To: <D690D58C.29DC5%christer.holmberg@ericsson.com>
Cc: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>,  MMUSIC <mmusic@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se> <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@nostrum.com> <D690D58C.29DC5%christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MnFOxJuX42IJc5nMXa5c375eR3M>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 29 Jan 2018 21:33:22 -0000

--Apple-Mail=_04BAE6C3-B7A7-4F40-80C1-0A577EF678F4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 26, 2018, at 5:16 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi Ben,
>=20
> Please see inline.
>=20
> (I=C2=B9ll address the comments where Magnus has provided input in the
> dedicated thread)
>=20
> ...
>=20
>>>=20
>>>> -8.3.3: IIUC, the criteria mean that the only m=3D sections that =
the
>>>> answerer can move out of the bundle are those that
>>>> have unique addresses but are not listed first in the group =
attribute.
>>>> If that is correct, a sentence or two to say that would be helpful.
>>>=20
>>> As long as the m=3D section contains a unique address (and does not
>>> contain a bundle-only attribute) it can be moved out of a BUNDLE =
group,
>>> no matter where it is listed in the group attribute.
>>=20
>> Then what does this text from the first bullet under 8.3.3 mean, as =
part
>> of the criteria for things that _can=C2=B9t_ be moved out of the =
group?
>>=20
>> =C2=B3 o  In the corresponding offer, an offerer BUNDLE address =
(previously
>>     selected [Section 8.3.1] or new suggested [Section 8.5.1]) has
>>     been assigned to the "m=3D" section by the offerer;"
>=20
>=20
> Ok, I see what you mean.
>=20
> My statement regarding unique address was incorrect.
>=20
> The important part is =C2=B3new suggested=C2=B2 - when a BUNDLE =
address have
> previously been negotiated. Because, compared to the initial offer, =
when a
> NEW BUNDLE address is suggested, it is only assigned to ONE m=3D line. =
A
> zero port value is assigned to all other m=3D sections, so because of =
that
> the m=3D section with the new suggested address cannot be moved out of =
the
> BUNDLE group.

Does that mean =E2=80=9Cnew suggested=E2=80=9D does not include =
=E2=80=9Cinitial suggested=E2=80=9D?

>=20
> ---
>=20
>>>=20
>>>> -10.3.1.3, last paragraph: What is the expected behavior when that
>>>> "protocol error" occurs?
>>>=20
>>> I don't think we don't normally specify that in cases like this,
>>> because it's an implementation issue. An implementation may trigger =
a
>>> new O/A exchange, or may terminate the whole session, etc etc.
>>=20
>> Those are recovery actions. Would it reasonable for the offerer to
>> pretend the answerer had really meant to accept rtp/rtcp =
multiplexing? Or
>> must the offerer give up on _this_ offer/answer exchange?
>=20
> I guess we could allow both alternatives.
>=20
> What about:
>=20
> "NOTE: It is considered a protocol error if the answerer has not
>   accepted the usage of RTP/RTCP multiplexing for RTP-based "m=3D"
>   sections that the answerer included in the BUNDLE group. As usage of
> RTP/RTCP multiplexing is required within a BUNDLE group, the offerer
> can either accept the answer and assume that RTP/RTCP multiplexing
> Will be used, or reject the answer and perform proper error handling
> actions (e.g., send a new offer, or terminate the whole session).=E2=80=9D=

>=20
Hrm. I actually intended the bit about assuming the answerer meant =
something different from what they said to test the bounderies of =
reasonableness. I=E2=80=99m a bit hesitant to actually suggest doing =
that :-)


>=20
> ---
>=20
>>>=20
>>>> -15.2, last paragraph: Is it worth recommending against patterns =
which
>>>> could be used as persistent identifiers, even if
>>>> they don=C2=B9t expressly identify a person or application?
>>>=20
>>> What would they identity?
>>>=20
>>> Just saying "..., or could be used as persistent identifiers" sounds =
a
>>> little half baked.
>>=20
>> As an example, assume that even though the implementation puts no
>> user-identifying information in the tag, it puts some piece of
>> information in there that is always the same for a given user. If =
someone
>> manages to correlate that piece to other activity that _does_ =
identify
>> the user, the piece becomes user-identifying.
>>=20
>> [=C5=A0]
>=20
>=20
> Isn=C2=B9t that covered by =C2=B3pattern=C2=B2?

The term =E2=80=9Cpattern=E2=80=9D was used with =E2=80=9Capplication =
identification=E2=80=9D. I guess my point is that a pattern may become =
_user_ identifying, even if the tag never includes any data that =
directly identifies the user.  I think we all know that is true, but a =
naive implementer may not. But see next comment...

>=20
> I could add say:
>=20
> "The identification-tag MUST NOT contain any user information, and
> applications SHALL avoid generating
>   the identification-tag using a pattern that enables <new>user- =
or</new>
> application identification.=C2=B2

That WFM.

[=E2=80=A6]

--Apple-Mail=_04BAE6C3-B7A7-4F40-80C1-0A577EF678F4
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpvkxsACgkQgFZKbJXz
1A2fSBAAmeS9RcSmZZxo2AP9OjLkDhu+jFfV6+aK0G92CqAhYxbItbyhdgHhF75u
C3WqkDWcOkbDbdP5gVHP7Qwe4h1rjRvN3W1nh6IDzZkICFic0df5F6GlFTSnZRe/
tlTi3xKKCdvITRVPHXGVNmfLS7yJkjc0tOh6f8yR30vguqbL/9f7S6HTtHhbmn78
FkNrIOR/sx2f1k3YsJTyuOlB+4cejERlcH1WCq5K/p//Mc6BzxFOeUKXt8qlD9Jh
1QoVDGe9Z1qLoWBDBZWqI16JeoOHs+FswCH+dSAilEuJbQX+IQR4x//sWpoIhMjD
sAaDymT3HBbxNPrcQA53pPljH8aZlGJ5w297EtOA/xznC0eMJDNsQKh9qAwEO20S
tSVsXmNDi2502cI26xNt6soBNACGNZNSwq49IGb/ElDMdW1qrEvfGdW5rso/h/HY
sDwWYVWcaRYnnz9o4AvgkyFs1349m5pkL+xA8DV/fQyqBCsy0KWRo6rJtsneh4qV
NvPCdJ+QuL8uqydLKut061D55YCvMZu645IE8F/8trBz5Ux4vNQNaj3wzM+bRick
P0Wx++47l6yROx+L99Pwc0aajYybDuw8RHyWWGwolFmkPa2iGQWlyjJgoWm/Lag1
lpirKwEod2sj/z0Lk/p1CjYZuk1pIK1x6GyBq7R5HylmtK2k31s=
=koy7
-----END PGP SIGNATURE-----

--Apple-Mail=_04BAE6C3-B7A7-4F40-80C1-0A577EF678F4--


From nobody Tue Jan 30 04:26: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 C53AB131ACF; Tue, 30 Jan 2018 04:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZAIU__ZhpRH; Tue, 30 Jan 2018 04:25:54 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2A9212E8AD; Tue, 30 Jan 2018 04:24:11 -0800 (PST)
X-AuditID: c1b4fb3a-34dff700000037f2-d5-5a7063e9041c
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 88.A3.14322.9E3607A5; Tue, 30 Jan 2018 13:24:09 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0352.000; Tue, 30 Jan 2018 13:24:09 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments - PULL REQUEST
Thread-Index: AQHTmcU558DYvrAXZEChUh4oOhhmlA==
Date: Tue, 30 Jan 2018 12:24:08 +0000
Message-ID: <D69632E5.2A0B0%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: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B93F2DB841BC524EB87E4FAB5BEDE923@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprAIsWRmVeSWpSXmKPExsUyM2K7ge7L5IIog/0v9Czmd55mtzjx/hur xdTlj1kcmD2WLPnJ5DFr5xOWAKYoLpuU1JzMstQifbsErowjMy+zFqxiqlh6+RxzA+Mnxi5G Tg4JAROJGX9OA9lcHEIChxkldi/7wQzhLGGUmPp/CpDDwcEmYCHR/U8bpEFEQEniefNWFpAa ZoGJjBKPFiwCc4QFGhgldm3bB+aICDQySvyec5UJokVP4uOazWA2i4CqxJUDx1lAbF4Ba4nd v2+D3cEoICbx/dQasBpmAXGJW0/mM0HcJyCxZM95ZghbVOLl43+sILYo0MwNJ26zQ8QVJdqf NjBC9OpJ3Jg6hQ3CtpZYub+PBcLWlli28DUzxF5BiZMzn7BMYBSdhWTdLCTts5C0z0LSPgtJ +wJG1lWMosWpxcW56UZGeqlFmcnFxfl5enmpJZsYgfF0cMtvqx2MB587HmIU4GBU4uEVDiqI EmJNLCuuzD3EKMHBrCTCK7I6P0qINyWxsiq1KD++qDQntfgQozQHi5I4r1OaRZSQQHpiSWp2 ampBahFMlomDU6qB0X1qxuvoE+E7M+4sF28QCuQQ/3c7XL/wddeCnewRk8MlrbcZGf14w9XT /KrsRnnx3TtzeI2/O2WbLJ+vdTQiasriqKhNjWaLa3UOrGgM2Nj/jDV9Z0eXdsPRzfvKz4co /TLzaNq84o6f3JsQz8Z/ivG/P888t+ypw2Ehobm1nnNF+PTuZQg9V2Ipzkg01GIuKk4EAJ83 kaujAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3zTPgp_kc5Yz2TMb399vwFZUZWE>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's editorial comments - PULL REQUEST
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, 30 Jan 2018 12:26:01 -0000

Hi,

I have created a pull request for implementing the changes based on Ben=B9s
editorial AD comments. I intend to create a separate pull request for the
other comments, because otherwise it becomes unreadable.

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


Regards,

Christer


From nobody Tue Jan 30 04:32:50 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 CC38512E88B; Tue, 30 Jan 2018 04:32:48 -0800 (PST)
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 Jo27Yka7xwKK; Tue, 30 Jan 2018 04:32:42 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68BD1317B0; Tue, 30 Jan 2018 04:30:34 -0800 (PST)
X-AuditID: c1b4fb3a-34dff700000037f2-c9-5a706568ba1f
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 34.65.14322.865607A5; Tue, 30 Jan 2018 13:30:33 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0352.000; Tue, 30 Jan 2018 13:30:32 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
Thread-Index: AdOR5+qL7nrym0YKTg6KUgOkGJEv7QEP5ykAAB5l/AAAp9EXgAAj7lcA
Date: Tue, 30 Jan 2018 12:30:31 +0000
Message-ID: <D69633F4.2A0B5%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se> <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@nostrum.com> <D690D58C.29DC5%christer.holmberg@ericsson.com> <44296CB2-58BB-4017-B75C-87E149B17B7F@nostrum.com>
In-Reply-To: <44296CB2-58BB-4017-B75C-87E149B17B7F@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: [153.88.183.19]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4EF9C3F36B3D064A8D51BA6DA5D89860@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKIsWRmVeSWpSXmKPExsUyM2K7rm5makGUwYtmHov5nafZLU68/8Zq MXX5YxYHZo8lS34yecza+YQlgCmKyyYlNSezLLVI3y6BK+Pc2QesBQ16FQvaFrE2ML7Q6WLk 5JAQMJG4eOMRaxcjF4eQwGFGiaOnW6GcJYwSW5fMZeli5OBgE7CQ6P6nDdIgIqAk8bx5KwtI DbPAREaJRwsWsYAkhAUyJH7u+s4MUZQp0bfoGyOE7SaxsmMqWA2LgKrE7Sm3wGp4Bawl1vUs Y4ZY9pJR4vvSDawgCU4Be4nPO++wg9iMAmIS30+tYQKxmQXEJW49mc8EcbaAxJI955khbFGJ l4//gfWKCuhJbDhxmx0irijR/rSBEeQBZgFNifW79CHGWEvMufQDaqSixJTuh+wQ9whKnJz5 hGUCo/gsJNtmIXTPQtI9C0n3LCTdCxhZVzGKFqcWF+emGxnppRZlJhcX5+fp5aWWbGIERt7B Lb+tdjAefO54iFGAg1GJh1c4qCBKiDWxrLgy9xCjBAezkgivyOr8KCHelMTKqtSi/Pii0pzU 4kOM0hwsSuK8TmkWUUIC6YklqdmpqQWpRTBZJg5OqQbGterRuzbd29qQb/37WJmC/Um1Db1d Sx5v+ZOlJ+A+8/6Ms2U9+ummvXP9jtx9nL+SZ9KVq/aXbDZre/712XSQy01D8NvUazcN1S2X N+UbKuXkHZ+yfeIaubY3L1XkvljMEb2d1Hb2+91nUgcknh6Oqt6srH/ow1ttM/G5t17ZrnJ6 t6L5HefkBiWW4oxEQy3mouJEAC3WHVq4AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/MLBhW8uTM5kO-0Q66bl9SXoKuMY>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 30 Jan 2018 12:32:49 -0000

SGksDQoNCj4+Li4uDQo+PiANCj4+Pj4gDQo+Pj4+PiAtOC4zLjM6IElJVUMsIHRoZSBjcml0ZXJp
YSBtZWFuIHRoYXQgdGhlIG9ubHkgbT0gc2VjdGlvbnMgdGhhdCB0aGUNCj4+Pj4+IGFuc3dlcmVy
IGNhbiBtb3ZlIG91dCBvZiB0aGUgYnVuZGxlIGFyZSB0aG9zZSB0aGF0DQo+Pj4+PiBoYXZlIHVu
aXF1ZSBhZGRyZXNzZXMgYnV0IGFyZSBub3QgbGlzdGVkIGZpcnN0IGluIHRoZSBncm91cA0KPj4+
Pj5hdHRyaWJ1dGUuDQo+Pj4+PiBJZiB0aGF0IGlzIGNvcnJlY3QsIGEgc2VudGVuY2Ugb3IgdHdv
IHRvIHNheSB0aGF0IHdvdWxkIGJlIGhlbHBmdWwuDQo+Pj4+IA0KPj4+PiBBcyBsb25nIGFzIHRo
ZSBtPSBzZWN0aW9uIGNvbnRhaW5zIGEgdW5pcXVlIGFkZHJlc3MgKGFuZCBkb2VzIG5vdA0KPj4+
PiBjb250YWluIGEgYnVuZGxlLW9ubHkgYXR0cmlidXRlKSBpdCBjYW4gYmUgbW92ZWQgb3V0IG9m
IGEgQlVORExFDQo+Pj4+Z3JvdXAsDQo+Pj4+IG5vIG1hdHRlciB3aGVyZSBpdCBpcyBsaXN0ZWQg
aW4gdGhlIGdyb3VwIGF0dHJpYnV0ZS4NCj4+PiANCj4+PiBUaGVuIHdoYXQgZG9lcyB0aGlzIHRl
eHQgZnJvbSB0aGUgZmlyc3QgYnVsbGV0IHVuZGVyIDguMy4zIG1lYW4sIGFzDQo+Pj5wYXJ0DQo+
Pj4gb2YgdGhlIGNyaXRlcmlhIGZvciB0aGluZ3MgdGhhdCBfY2Fuwrl0XyBiZSBtb3ZlZCBvdXQg
b2YgdGhlIGdyb3VwPw0KPj4+IA0KPj4+IMKzIG8gIEluIHRoZSBjb3JyZXNwb25kaW5nIG9mZmVy
LCBhbiBvZmZlcmVyIEJVTkRMRSBhZGRyZXNzIChwcmV2aW91c2x5DQo+Pj4gICAgIHNlbGVjdGVk
IFtTZWN0aW9uIDguMy4xXSBvciBuZXcgc3VnZ2VzdGVkIFtTZWN0aW9uIDguNS4xXSkgaGFzDQo+
Pj4gICAgIGJlZW4gYXNzaWduZWQgdG8gdGhlICJtPSIgc2VjdGlvbiBieSB0aGUgb2ZmZXJlcjsi
DQo+PiANCj4+IA0KPj4gT2ssIEkgc2VlIHdoYXQgeW91IG1lYW4uDQo+PiANCj4+IE15IHN0YXRl
bWVudCByZWdhcmRpbmcgdW5pcXVlIGFkZHJlc3Mgd2FzIGluY29ycmVjdC4NCj4+IA0KPj4gVGhl
IGltcG9ydGFudCBwYXJ0IGlzIMKzbmV3IHN1Z2dlc3RlZMKyIC0gd2hlbiBhIEJVTkRMRSBhZGRy
ZXNzIGhhdmUNCj4+IHByZXZpb3VzbHkgYmVlbiBuZWdvdGlhdGVkLiBCZWNhdXNlLCBjb21wYXJl
ZCB0byB0aGUgaW5pdGlhbCBvZmZlciwNCj4+d2hlbiBhDQo+PiBORVcgQlVORExFIGFkZHJlc3Mg
aXMgc3VnZ2VzdGVkLCBpdCBpcyBvbmx5IGFzc2lnbmVkIHRvIE9ORSBtPSBsaW5lLiBBDQo+PiB6
ZXJvIHBvcnQgdmFsdWUgaXMgYXNzaWduZWQgdG8gYWxsIG90aGVyIG09IHNlY3Rpb25zLCBzbyBi
ZWNhdXNlIG9mIHRoYXQNCj4+IHRoZSBtPSBzZWN0aW9uIHdpdGggdGhlIG5ldyBzdWdnZXN0ZWQg
YWRkcmVzcyBjYW5ub3QgYmUgbW92ZWQgb3V0IG9mIHRoZQ0KPj4gQlVORExFIGdyb3VwLg0KPg0K
PkRvZXMgdGhhdCBtZWFuIOKAnG5ldyBzdWdnZXN0ZWTigJ0gZG9lcyBub3QgaW5jbHVkZSDigJxp
bml0aWFsIHN1Z2dlc3RlZOKAnT8NCg0KQ29ycmVjdC4NCg0KLS0tDQoNCj4+Pj4+LTEwLjMuMS4z
LCBsYXN0IHBhcmFncmFwaDogV2hhdCBpcyB0aGUgZXhwZWN0ZWQgYmVoYXZpb3Igd2hlbiB0aGF0
DQo+Pj4+PiAicHJvdG9jb2wgZXJyb3IiIG9jY3Vycz8NCj4+Pj4gDQo+Pj4+IEkgZG9uJ3QgdGhp
bmsgd2UgZG9uJ3Qgbm9ybWFsbHkgc3BlY2lmeSB0aGF0IGluIGNhc2VzIGxpa2UgdGhpcywNCj4+
Pj4gYmVjYXVzZSBpdCdzIGFuIGltcGxlbWVudGF0aW9uIGlzc3VlLiBBbiBpbXBsZW1lbnRhdGlv
biBtYXkgdHJpZ2dlciBhDQo+Pj4+IG5ldyBPL0EgZXhjaGFuZ2UsIG9yIG1heSB0ZXJtaW5hdGUg
dGhlIHdob2xlIHNlc3Npb24sIGV0YyBldGMuDQo+Pj4gDQo+Pj4gVGhvc2UgYXJlIHJlY292ZXJ5
IGFjdGlvbnMuIFdvdWxkIGl0IHJlYXNvbmFibGUgZm9yIHRoZSBvZmZlcmVyIHRvDQo+Pj4gcHJl
dGVuZCB0aGUgYW5zd2VyZXIgaGFkIHJlYWxseSBtZWFudCB0byBhY2NlcHQgcnRwL3J0Y3AgbXVs
dGlwbGV4aW5nPw0KPj4+T3INCj4+PiBtdXN0IHRoZSBvZmZlcmVyIGdpdmUgdXAgb24gX3RoaXNf
IG9mZmVyL2Fuc3dlciBleGNoYW5nZT8NCj4+IA0KPj4gSSBndWVzcyB3ZSBjb3VsZCBhbGxvdyBi
b3RoIGFsdGVybmF0aXZlcy4NCj4+IA0KPj4gV2hhdCBhYm91dDoNCj4+IA0KPj4gIk5PVEU6IEl0
IGlzIGNvbnNpZGVyZWQgYSBwcm90b2NvbCBlcnJvciBpZiB0aGUgYW5zd2VyZXIgaGFzIG5vdA0K
Pj4gICBhY2NlcHRlZCB0aGUgdXNhZ2Ugb2YgUlRQL1JUQ1AgbXVsdGlwbGV4aW5nIGZvciBSVFAt
YmFzZWQgIm09Ig0KPj4gICBzZWN0aW9ucyB0aGF0IHRoZSBhbnN3ZXJlciBpbmNsdWRlZCBpbiB0
aGUgQlVORExFIGdyb3VwLiBBcyB1c2FnZSBvZg0KPj4gUlRQL1JUQ1AgbXVsdGlwbGV4aW5nIGlz
IHJlcXVpcmVkIHdpdGhpbiBhIEJVTkRMRSBncm91cCwgdGhlIG9mZmVyZXINCj4+IGNhbiBlaXRo
ZXIgYWNjZXB0IHRoZSBhbnN3ZXIgYW5kIGFzc3VtZSB0aGF0IFJUUC9SVENQIG11bHRpcGxleGlu
Zw0KPj4gV2lsbCBiZSB1c2VkLCBvciByZWplY3QgdGhlIGFuc3dlciBhbmQgcGVyZm9ybSBwcm9w
ZXIgZXJyb3IgaGFuZGxpbmcNCj4+IGFjdGlvbnMgKGUuZy4sIHNlbmQgYSBuZXcgb2ZmZXIsIG9y
IHRlcm1pbmF0ZSB0aGUgd2hvbGUgc2Vzc2lvbiku4oCdDQo+PiANCj5Icm0uIEkgYWN0dWFsbHkg
aW50ZW5kZWQgdGhlIGJpdCBhYm91dCBhc3N1bWluZyB0aGUgYW5zd2VyZXIgbWVhbnQNCj5zb21l
dGhpbmcgZGlmZmVyZW50IGZyb20gd2hhdCB0aGV5IHNhaWQgdG8gdGVzdCB0aGUgYm91bmRlcmll
cyBvZg0KPnJlYXNvbmFibGVuZXNzLiBJ4oCZbSBhIGJpdCBoZXNpdGFudCB0byBhY3R1YWxseSBz
dWdnZXN0IGRvaW5nIHRoYXQgOi0pDQoNCk5vdCBzdXJlIEkgZm9sbG93IDopDQoNCi0tLQ0KDQo+
Pj4+Pi0xNS4yLCBsYXN0IHBhcmFncmFwaDogSXMgaXQgd29ydGggcmVjb21tZW5kaW5nIGFnYWlu
c3QgcGF0dGVybnMgd2hpY2gNCj4+Pj4+IGNvdWxkIGJlIHVzZWQgYXMgcGVyc2lzdGVudCBpZGVu
dGlmaWVycywgZXZlbiBpZg0KPj4+Pj4gdGhleSBkb27CuXQgZXhwcmVzc2x5IGlkZW50aWZ5IGEg
cGVyc29uIG9yIGFwcGxpY2F0aW9uPw0KPj4+PiANCj4+Pj4gV2hhdCB3b3VsZCB0aGV5IGlkZW50
aXR5Pw0KPj4+PiANCj4+Pj4gSnVzdCBzYXlpbmcgIi4uLiwgb3IgY291bGQgYmUgdXNlZCBhcyBw
ZXJzaXN0ZW50IGlkZW50aWZpZXJzIiBzb3VuZHMgYQ0KPj4+PiBsaXR0bGUgaGFsZiBiYWtlZC4N
Cj4+PiANCj4+PiBBcyBhbiBleGFtcGxlLCBhc3N1bWUgdGhhdCBldmVuIHRob3VnaCB0aGUgaW1w
bGVtZW50YXRpb24gcHV0cyBubw0KPj4+IHVzZXItaWRlbnRpZnlpbmcgaW5mb3JtYXRpb24gaW4g
dGhlIHRhZywgaXQgcHV0cyBzb21lIHBpZWNlIG9mDQo+Pj4gaW5mb3JtYXRpb24gaW4gdGhlcmUg
dGhhdCBpcyBhbHdheXMgdGhlIHNhbWUgZm9yIGEgZ2l2ZW4gdXNlci4gSWYNCj4+PnNvbWVvbmUN
Cj4+PiBtYW5hZ2VzIHRvIGNvcnJlbGF0ZSB0aGF0IHBpZWNlIHRvIG90aGVyIGFjdGl2aXR5IHRo
YXQgX2RvZXNfIGlkZW50aWZ5DQo+Pj4gdGhlIHVzZXIsIHRoZSBwaWVjZSBiZWNvbWVzIHVzZXIt
aWRlbnRpZnlpbmcuDQo+Pj4gDQo+Pj4gW8WgXQ0KPj4gDQo+PiANCj4+IElzbsK5dCB0aGF0IGNv
dmVyZWQgYnkgwrNwYXR0ZXJuwrI/DQo+DQo+VGhlIHRlcm0g4oCccGF0dGVybuKAnSB3YXMgdXNl
ZCB3aXRoIOKAnGFwcGxpY2F0aW9uIGlkZW50aWZpY2F0aW9u4oCdLiBJIGd1ZXNzIG15DQo+cG9p
bnQgaXMgdGhhdCBhIHBhdHRlcm4gbWF5IGJlY29tZSBfdXNlcl8gaWRlbnRpZnlpbmcsIGV2ZW4g
aWYgdGhlIHRhZw0KPm5ldmVyIGluY2x1ZGVzIGFueSBkYXRhIHRoYXQgZGlyZWN0bHkgaWRlbnRp
ZmllcyB0aGUgdXNlci4gIEkgdGhpbmsgd2UNCj5hbGwga25vdyB0aGF0IGlzIHRydWUsIGJ1dCBh
IG5haXZlIGltcGxlbWVudGVyIG1heSBub3QuIEJ1dCBzZWUgbmV4dA0KPmNvbW1lbnQuLi4NCj4N
Cj4+IA0KPj4gSSBjb3VsZCBhZGQgc2F5Og0KPj4gDQo+PiAiVGhlIGlkZW50aWZpY2F0aW9uLXRh
ZyBNVVNUIE5PVCBjb250YWluIGFueSB1c2VyIGluZm9ybWF0aW9uLCBhbmQNCj4+IGFwcGxpY2F0
aW9ucyBTSEFMTCBhdm9pZCBnZW5lcmF0aW5nDQo+PiAgIHRoZSBpZGVudGlmaWNhdGlvbi10YWcg
dXNpbmcgYSBwYXR0ZXJuIHRoYXQgZW5hYmxlcyA8bmV3PnVzZXItDQo+Pm9yPC9uZXc+DQo+PiBh
cHBsaWNhdGlvbiBpZGVudGlmaWNhdGlvbi7Csg0KPg0KPlRoYXQgV0ZNLg0KDQpHcmVhdCEgOikN
Cg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Tue Jan 30 06:17:50 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 5CC5612EB44 for <mmusic@ietfa.amsl.com>; Tue, 30 Jan 2018 06:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 8gnCSh9u1F8Z for <mmusic@ietfa.amsl.com>; Tue, 30 Jan 2018 06:17:46 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86FCD12EAD9 for <mmusic@ietf.org>; Tue, 30 Jan 2018 06:17:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=806; q=dns/txt; s=iport; t=1517321866; x=1518531466; h=subject:from:to:references:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=N8wvwALHv2xMWmH0lIw5NdNTO7h9HSsK450qHCdd5Q4=; b=WN3dpiS48PsjS888g73JyFn+nRhUb1CDcuANsmqFPDVjKqwJgtctzMNm HcTfJbDYgiCU5Vm1DYkmtq+U+YEkIIFl6BDZXjEosznuvV6h3WKlu8KGy z0MBYpQ9nGXgFeYMS6FHLZjJ5GhHc9wpKl5lyRpxsf4VnNy3pH5ELQkDb w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DHAQB+fXBa/5xdJa1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNCZnUog2CZEYICmVwKGAuESU8CgkRYFAEBAQEBAQEBAmsohSQ?= =?us-ascii?q?BAQQBASEVNhsLGAICJgICJzAGDQYCAQGKJA0QpUCCJ4pdCAEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBARsFgQ+DRYIVgVeCEYMFgUmBZgEBAoFMgzqCZQWTVJBDkAGFZ4IbhiG?= =?us-ascii?q?DcYd8l2eBPDYigVBNIxU9giqCYYI0IzePKAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,435,1511827200"; d="scan'208";a="131725513"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2018 14:17:45 +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 w0UEHjeI011977 for <mmusic@ietf.org>; Tue, 30 Jan 2018 14:17:45 GMT
From: Flemming Andreasen <fandreas@cisco.com>
To: mmusic <mmusic@ietf.org>
References: <0ac18131-bf6f-8cb8-8874-b738e25c4012@cisco.com>
Message-ID: <45a28c65-99aa-bd36-1b06-9d6b61a05e48@cisco.com>
Date: Tue, 30 Jan 2018 09:18:08 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <0ac18131-bf6f-8cb8-8874-b738e25c4012@cisco.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/bzUwyS3vH6ULMWCHwcQ8JQWDsFw>
Subject: Re: [MMUSIC] MMUSIC meet at IETF 101 (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: Tue, 30 Jan 2018 14:17:48 -0000

At this point, we have not received any agenda requests and hence we do 
not plan on meeting in London. If you have any agenda requests, please 
submit them to the chairs ASAP.

Thanks

-- Flemming & Bo

On 1/12/18 9:32 AM, Flemming Andreasen wrote:
> Greetings
>
> Requests for WGs to meet at IETF 101 in London are due by February 2 
> and hence we wanted to prod the group at this point to see if anybody 
> expects a need for MMUSIC to meet in London. If you do, please let the 
> chairs know sooner rather than later. If we do not hear from anybody, 
> we do not expect to ask for a meeting slot.
>
> Thanks
>
> -- Flemming & Bo
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> .
>


From nobody Tue Jan 30 09:20: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 531AF12E889; Tue, 30 Jan 2018 09:20:20 -0800 (PST)
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 3VMc9z2hf214; Tue, 30 Jan 2018 09:20:12 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5FC7F12EC6C; Tue, 30 Jan 2018 09:20:12 -0800 (PST)
Received: from [10.0.1.105] (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 w0UHK8Ml084877 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 30 Jan 2018 11:20:09 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <A1D05348-5201-4CA9-96F6-54A5EEDB98AE@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8B2EA140-DF7E-4E0A-ABA4-C2A67062AF11"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Tue, 30 Jan 2018 11:20:07 -0600
In-Reply-To: <D69633F4.2A0B5%christer.holmberg@ericsson.com>
Cc: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>,  MMUSIC <mmusic@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se> <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@nostrum.com> <D690D58C.29DC5%christer.holmberg@ericsson.com> <44296CB2-58BB-4017-B75C-87E149B17B7F@nostrum.com> <D69633F4.2A0B5%christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vG-S3Ghk9mdNuDbThsZkZY8svv8>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 30 Jan 2018 17:20:20 -0000

--Apple-Mail=_8B2EA140-DF7E-4E0A-ABA4-C2A67062AF11
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Jan 30, 2018, at 6:30 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
>>>>>>=20
>>>>>> -10.3.1.3, last paragraph: What is the expected behavior when =
that
>>>>>> "protocol error" occurs?
>>>>>=20
>>>>> I don't think we don't normally specify that in cases like this,
>>>>> because it's an implementation issue. An implementation may =
trigger a
>>>>> new O/A exchange, or may terminate the whole session, etc etc.
>>>>=20
>>>> Those are recovery actions. Would it reasonable for the offerer to
>>>> pretend the answerer had really meant to accept rtp/rtcp =
multiplexing?
>>>> Or
>>>> must the offerer give up on _this_ offer/answer exchange?
>>>=20
>>> I guess we could allow both alternatives.
>>>=20
>>> What about:
>>>=20
>>> "NOTE: It is considered a protocol error if the answerer has not
>>>  accepted the usage of RTP/RTCP multiplexing for RTP-based "m=3D"
>>>  sections that the answerer included in the BUNDLE group. As usage =
of
>>> RTP/RTCP multiplexing is required within a BUNDLE group, the offerer
>>> can either accept the answer and assume that RTP/RTCP multiplexing
>>> Will be used, or reject the answer and perform proper error handling
>>> actions (e.g., send a new offer, or terminate the whole session).=E2=80=
=9D
>>>=20
>> Hrm. I actually intended the bit about assuming the answerer meant
>> something different from what they said to test the bounderies of
>> reasonableness. I=E2=80=99m a bit hesitant to actually suggest doing =
that :-)
>=20
> Not sure I follow :)

That is, I didn=E2=80=99t mean to suggest that assuming the answerer =
will still do rtp/rtcp mux is a good idea, or that the text should =
suggest it. I was wondering if we should offer guidance _against_ that =
sort of thing.

I think at this point you have convinced me there is no useful guidance =
to give, so I=E2=80=99m okay with the original text.


--Apple-Mail=_8B2EA140-DF7E-4E0A-ABA4-C2A67062AF11
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpwqUcACgkQgFZKbJXz
1A2XKxAAw/mFQYoLM8aAqgOV0LVuse1IP2OQAO9dKgBXwr3PXgVgaPQS978sPXpo
+A1W+X9qzLncOmgExDKWwmV6WCgpN/AJjRG1tm5c5mps0k/+b6mtfP+oVozmZ0Ss
mvv2XEBe1XuxdEQMPiLcrOqADbCVfbbrTXbxC/0MZE+WdJMz4DSegKUpIob6zyKB
1A3OJn/yYUs3OrQVVohPOivkTZeYDs6FmtYuR0hyBcA9yIC0wxT+DhcN0/cAtbkd
JpWn6hoVvyw31DS/b2ko6A0GisPX8CldZGmw7N34quBUZ11xrFGjyFIdNsheIVtT
qFogJhXAH4y8puz6n+3LS1WfO6oE0HPG9niFFFR5rJT7OsZ5P4g3mVE8OMSyGyu9
8QUWofJ+aVUVrCvxI+7r1dK4I0qrls0wj+USlHrX88wReMUZjqz4+NGkP9qzr7lc
AQ9MUmegR4dai7Fm1H5MnG6CDWAJ5b2khc6CDe/xKQcBZCivJPymZV8SBluhUwoI
XymhVpTXYpD75Cvxewc5aedAhEZZ5PHPMmIPbZnK5ueUTKC2CiBIt9spb/fyieH4
DwtsRZ67IaarYaj7S9iOgIbHjXi1i3kNh238kijo1n0YjjngAV1F5grjeffuUrZl
JFjHRHoqgU6Rxf0UJ47Hy4pceaGSkv7+Plv4d6ERZYj7YP/ubCw=
=zLL7
-----END PGP SIGNATURE-----

--Apple-Mail=_8B2EA140-DF7E-4E0A-ABA4-C2A67062AF11--


From nobody Tue Jan 30 20:31:57 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 36F8D1275F4; Tue, 30 Jan 2018 20:31:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.70.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151737311616.7731.10004998812829615378@ietfa.amsl.com>
Date: Tue, 30 Jan 2018 20:31:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/NlX52dHI8n5m_HTgLmG-TPRpcBA>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-uks-01.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, 31 Jan 2018 04:31:56 -0000

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

        Title           : Unknown Key Share Attacks on uses of Transport Layer Security with the Session Description Protocol (SDP)
        Authors         : Martin Thomson
                          Eric Rescorla
	Filename        : draft-ietf-mmusic-sdp-uks-01.txt
	Pages           : 13
	Date            : 2018-01-30

Abstract:
   Unknown key-share attacks on the use of Datagram Transport Layer
   Security for the Secure Real-Time Transport Protocol (DTLS-SRTP) and
   its use with Web Real-Time Communications (WebRTC) identity
   assertions are described.  Simple mitigation techniques are defined.


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

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

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


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 Jan 31 00:13: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 AE02E131A58; Wed, 31 Jan 2018 00:13:53 -0800 (PST)
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 BtwANPXplrV2; Wed, 31 Jan 2018 00:13:47 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B37221319B2; Wed, 31 Jan 2018 00:11:46 -0800 (PST)
X-AuditID: c1b4fb3a-34dff700000037f2-07-5a717a4089b2
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 25.77.14322.04A717A5; Wed, 31 Jan 2018 09:11:45 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 09:11:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
Thread-Index: AdOR5+qL7nrym0YKTg6KUgOkGJEv7QEP5ykAAB5l/AAAp9EXgAAj7lcAAAWFE4AAI7v5AA==
Date: Wed, 31 Jan 2018 08:11:43 +0000
Message-ID: <D6974954.2A1E8%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C130970@ESESSMB109.ericsson.se> <DAF5F9CE-4D4D-4971-AD1C-C08DE41B6548@nostrum.com> <D690D58C.29DC5%christer.holmberg@ericsson.com> <44296CB2-58BB-4017-B75C-87E149B17B7F@nostrum.com> <D69633F4.2A0B5%christer.holmberg@ericsson.com> <A1D05348-5201-4CA9-96F6-54A5EEDB98AE@nostrum.com>
In-Reply-To: <A1D05348-5201-4CA9-96F6-54A5EEDB98AE@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: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <12F2F1149ACA2F4FBC02BDA5BEE8A894@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsUyM2K7tK5jVWGUwYUvjBbzO0+zW5x4/43V YuryxywOzB5Llvxk8pi18wlLAFMUl01Kak5mWWqRvl0CV8au/SvYCo7yVZz8sYylgfEpdxcj J4eEgInEr+uPmboYuTiEBA4zSiyfvI8RwlnCKHHkzAO2LkYODjYBC4nuf9ogDSICShLPm7ey gNQwC0xklHi0YBELSEJYIEPi567vzBBFmRJ9i74xQthhEls/9LKD2CwCqhLL5h0Hs3kFrCWm zlnBCrHsApPEgc8X2UASnAL2Ep9XtoMVMQqISXw/tYYJxGYWEJe49WQ+E8TZAhJL9pxnhrBF JV4+/scKYosK6ElsOHGbHSKuKNH+tIERoldP4sbUKWwQtrXEtb0dULa2xLKFr5khDhKUODnz CcsERvFZSNbNQtI+C0n7LCTts5C0L2BkXcUoWpxaXJybbmSkl1qUmVxcnJ+nl5dasokRGH0H t/y22sF48LnjIUYBDkYlHt4Z5YVRQqyJZcWVuYcYJTiYlUR4v8UAhXhTEiurUovy44tKc1KL DzFKc7AoifM6pVlECQmkJ5akZqemFqQWwWSZODilGhj9X9jKJ/Eap9+br2K8bt6S3gCuhu8b vzqc5HfcnvW8a6cH4xSb12lTp03ecq2D5dKx1wlPF6wJn1LeZamyyb21+vnaFP0CoZNH9Vtu +a9fJtnMz7DoelfhPM3pH4UmRs/Inrbdvd1Q/YLloheOd+7VrwtsedAva/y5vFT6TuCW6+KX rX+dLeZUYinOSDTUYi4qTgQANQx/zLoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ptEXEKwIXZf54Ukw4y0vJXrlmTs>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments
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, 31 Jan 2018 08:13:54 -0000

Hi,

>>>>>>>-10.3.1.3, last paragraph: What is the expected behavior when that
>>>>>>> "protocol error" occurs?
>>>>>>=20
>>>>>> I don't think we don't normally specify that in cases like this,
>>>>>> because it's an implementation issue. An implementation may trigger
>>>>>>a
>>>>>> new O/A exchange, or may terminate the whole session, etc etc.
>>>>>=20
>>>>> Those are recovery actions. Would it reasonable for the offerer to
>>>>> pretend the answerer had really meant to accept rtp/rtcp
>>>>>multiplexing?
>>>>> Or
>>>>> must the offerer give up on _this_ offer/answer exchange?
>>>>=20
>>>> I guess we could allow both alternatives.
>>>>=20
>>>> What about:
>>>>=20
>>>> "NOTE: It is considered a protocol error if the answerer has not
>>>>  accepted the usage of RTP/RTCP multiplexing for RTP-based "m=3D"
>>>>  sections that the answerer included in the BUNDLE group. As usage of
>>>> RTP/RTCP multiplexing is required within a BUNDLE group, the offerer
>>>> can either accept the answer and assume that RTP/RTCP multiplexing
>>>> Will be used, or reject the answer and perform proper error handling
>>>> actions (e.g., send a new offer, or terminate the whole session).=B2
>>>>=20
>>> Hrm. I actually intended the bit about assuming the answerer meant
>>> something different from what they said to test the bounderies of
>>> reasonableness. I=B9m a bit hesitant to actually suggest doing that :-)
>>=20
>> Not sure I follow :)
>
>That is, I didn=B9t mean to suggest that assuming the answerer will still
>do rtp/rtcp mux is a good idea, or that the text should suggest it. I was
>wondering if we should offer guidance _against_ that sort of thing.
>
>I think at this point you have convinced me there is no useful guidance
>to give, so I=B9m okay with the original text.

Thanks! :)

Regards,

Christer


From nobody Wed Jan 31 01:19: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 2BC1C1315C0; Wed, 31 Jan 2018 01:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KJEwDFNHCsLB; Wed, 31 Jan 2018 01:19:49 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D49512D886; Wed, 31 Jan 2018 01:19:48 -0800 (PST)
X-AuditID: c1b4fb3a-716549c0000037f2-c1-5a718a335cca
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 31.48.14322.33A817A5; Wed, 31 Jan 2018 10:19:47 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 10:19:46 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments - Pull Request
Thread-Index: AQHTmnSijXwVGLFl3EWExbzurw0hlg==
Date: Wed, 31 Jan 2018 09:19:46 +0000
Message-ID: <D6975915.2A209%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: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8F403C3B65636F4E9D4B3E35CF677CFA@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphkeLIzCtJLcpLzFFi42KZGbE9RNe4qzDKYPElKYv5nafZLU68/8Zq MXX5YxYHZo8lS34yecza+YQlgCmKyyYlNSezLLVI3y6BK6P/jkPBbeaKlhfv2BsYfzJ1MXJy SAiYSDScPcnaxcjFISRwmFGi7dVmKGcJo8T03xeBHA4ONgELie5/2iANIgJKEs+bt7KA1DAL TGSUeLRgEQtIjbBAucS5n0YQNRUSb+59ZYOw9STe9e9lB7FZBFQltt+eAWbzClhLPH/6jgXE ZhQQk/h+ag3YQcwC4hK3nsyHOk5AYsme88wQtqjEy8f/WEFsUaCZG07cZoeIK0rsPNvODNGr J3Fj6hQ2CNta4uadNqi4tsSyha+ZIfYKSpyc+YRlAqPoLCTrZiFpn4WkfRaS9llI2hcwsq5i FC1OLS7OTTcy0kstykwuLs7P08tLLdnECIyjg1t+W+1gPPjc8RCjAAejEg/vjPLCKCHWxLLi ytxDjBIczEoivN9igEK8KYmVValF+fFFpTmpxYcYpTlYlMR5ndIsooQE0hNLUrNTUwtSi2Cy TBycUg2Mfl371h4rzpTTmGj+LSw8O6Nz0uO2Y36f3rlp64oyH/hinbS6gr9G+kKC7QS/Pv9H gT8Obin32nbyz5z7G3weLmwN3GW90v1g41mRmd/YuUT4r99M3/dnsTBH+83+R1EHTsYXNmy/ aHC19dM5pnuWAjPWTczlyn1UmzaRS3SPk+Yy2QLZpWualFiKMxINtZiLihMBQTtTvp8CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/fuKljZwfLOOJpRTcJ-KPFalYGXg>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments - Pull Request
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, 31 Jan 2018 09:19:51 -0000

Hi,

I have created a pull request that implements the changes based on the
substantive comments in Ben=B9s AD review:

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


NOTE 1: The changes where Magnus provided input have not yet been
committed.

NOTE 2: The change to use media-level =B3c=3D=B3 lines in one of the exampl=
es
will be done in the pull request for the editorial changes (in order to
avoid a pull request conflict).

Regards,

Christer


From nobody Wed Jan 31 01:49:34 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 0450E131998; Wed, 31 Jan 2018 01:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wbVchkvvCu33; Wed, 31 Jan 2018 01:49:31 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C337131A23; Wed, 31 Jan 2018 01:45:41 -0800 (PST)
X-AuditID: c1b4fb30-d49ff70000006bc7-13-5a7190430492
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id F8.3F.27591.340917A5; Wed, 31 Jan 2018 10:45:39 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 10:45:39 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>
CC: "draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation.all@ietf.org>, MMUSIC <mmusic@ietf.org>
Thread-Topic: AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments - Pull Request
Thread-Index: AQHTmnSijXwVGLFl3EWExbzurw0hlqONz5cA
Date: Wed, 31 Jan 2018 09:45:39 +0000
Message-ID: <D6975F84.2A214%christer.holmberg@ericsson.com>
References: <D6975915.2A209%christer.holmberg@ericsson.com>
In-Reply-To: <D6975915.2A209%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: [153.88.183.20]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <066752DEC4E548478D52F5A98BEF1A94@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKIsWRmVeSWpSXmKPExsUyM2K7rq7zhMIogyV3DC3md55mtzjx/hur xdTlj1kcmD2WLPnJ5DFr5xOWAKYoLpuU1JzMstQifbsErozfD1uZCzrYK77dmMvUwPiBrYuR k0NCwETi/vk2xi5GLg4hgcOMEk17uqCcJYwSLX+PM3UxcnCwCVhIdP/TBmkQEVCSeN68lQWk hllgIqPEowWLWEBqhAXKJc79NIKoqZB4c+8rG4RtJPH2/HJ2EJtFQFXizrw7YDavgLXEtDc9 rCC2EJA9+dI9MJtTwEbi8ZeLLCA2o4CYxPdTa5hAbGYBcYlbT+YzQRwtILFkz3lmCFtU4uXj f2C9ogJ6EhtO3GaHiCtKXJ2+HKpXS+LLj31sELa1xOF1O6DiihJTuh9C3SMocXLmE5YJjOKz kKybhaR9FpL2WUjaZyFpX8DIuopRtDi1OCk33chIL7UoM7m4OD9PLy+1ZBMjMPIObvltsIPx 5XPHQ4wCHIxKPLyF5YVRQqyJZcWVuYcYJTiYlUR4v8UAhXhTEiurUovy44tKc1KLDzFKc7Ao ifOe9OSNEhJITyxJzU5NLUgtgskycXBKNTCKMT1/KiwuI9q55/HBDCOlnO+J3j3LljHP3c31 vfdFDis763c/BQYN/5xrW/TON2nWzdp1xfTGvDsvw8OOLXywVYRrwhPjS7k2DP9Xqv3umHR+ Ze/puSfWiM067L0jRGrhQc+8WdK8OcUtqyYeCPu+ZRvfve9+tVfecFrbeH679rHB+Ouz9wF9 SizFGYmGWsxFxYkA6PdY17gCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3dMHITsDYqxIBBnG-WP7AW40ODU>
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-bundle-negotiation-47 - Ben's substantive comments - Pull Request
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, 31 Jan 2018 09:49:33 -0000

SGksDQoNClRoZSBpbnB1dCBwcm92aWRlZCBieSBNYWdudXMgaGFzIG5vdyBiZWVuIGNvbW1pdHRl
ZC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQpPbiAzMS8wMS8xOCAxMToxOSwgIkNocmlz
dGVyIEhvbG1iZXJnIiA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPg0Kd3JvdGU6DQoN
Cj5IaSwNCj4NCj5JIGhhdmUgY3JlYXRlZCBhIHB1bGwgcmVxdWVzdCB0aGF0IGltcGxlbWVudHMg
dGhlIGNoYW5nZXMgYmFzZWQgb24gdGhlDQo+c3Vic3RhbnRpdmUgY29tbWVudHMgaW4gQmVuqfZz
IEFEIHJldmlldzoNCj4NCj5odHRwczovL2dpdGh1Yi5jb20vY2RoNHUvZHJhZnQtc2RwLWJ1bmRs
ZS9wdWxsLzU2DQo+DQo+DQo+Tk9URSAxOiBUaGUgY2hhbmdlcyB3aGVyZSBNYWdudXMgcHJvdmlk
ZWQgaW5wdXQgaGF2ZSBub3QgeWV0IGJlZW4NCj5jb21taXR0ZWQuDQo+DQo+Tk9URSAyOiBUaGUg
Y2hhbmdlIHRvIHVzZSBtZWRpYS1sZXZlbCCp+GM9qfggbGluZXMgaW4gb25lIG9mIHRoZSBleGFt
cGxlcw0KPndpbGwgYmUgZG9uZSBpbiB0aGUgcHVsbCByZXF1ZXN0IGZvciB0aGUgZWRpdG9yaWFs
IGNoYW5nZXMgKGluIG9yZGVyIHRvDQo+YXZvaWQgYSBwdWxsIHJlcXVlc3QgY29uZmxpY3QpLg0K
Pg0KPlJlZ2FyZHMsDQo+DQo+Q2hyaXN0ZXINCj4NCg0K


From nobody Wed Jan 31 03:06: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 E917112DA6B for <mmusic@ietfa.amsl.com>; Wed, 31 Jan 2018 03:06:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 6e11al2hfzxB for <mmusic@ietfa.amsl.com>; Wed, 31 Jan 2018 03:06:49 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EA5A12DA0A for <mmusic@ietf.org>; Wed, 31 Jan 2018 03:06:47 -0800 (PST)
X-AuditID: c1b4fb25-859119c00000341b-0a-5a71a345c10d
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 13.BC.13339.543A17A5; Wed, 31 Jan 2018 12:06:46 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 12:06:43 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: MMUSIC <mmusic@ietf.org>, Ben Campbell <ben@nostrum.com>
Thread-Topic: [MMUSIC] BUNDLE: Some updates to RFC 3264 no longer needed? - Pull Request
Thread-Index: AQHTmoOTW9SFxKw7OUCqwRpyz+CmgA==
Date: Wed, 31 Jan 2018 11:06:42 +0000
Message-ID: <D697724E.2A22B%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: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_D697724E2A22Bchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupgkeLIzCtJLcpLzFFi42KZGbFdUddtcWGUwe7X3BbzO0+zW0xd/pjF gcljyZKfTB6zdj5hCWCK4rJJSc3JLEst0rdL4MqYMrORpaDZruLdxCfMDYx3TbsYOTkkBEwk li77ztjFyMUhJHCYUWLJw7XsEM4SRoneb62sXYwcHGwCFhLd/7RBGkQEbCQ29t9nBrGFBSIl 5nx5zgYRj5L4s2oPI4StJ3Gj8y47iM0ioCqx7ewhsDivgLXE3g1TWEBsRgExie+n1jCB2MwC 4hK3nsxngjhIQGLJnvPMELaoxMvH/1hBbFGgmRtO3GaHiCtK7DzbzgzRmyCxasIKNoj5ghIn Zz5hmcAoNAvJ2FlIymYhKYOIG0i8PzefGcLWlli28DWUrS+x8ctZRgjbWmLNh7vsyGoWMHKs YhQtTi1Oyk03MtZLLcpMLi7Oz9PLSy3ZxAiMn4NbfqvuYLz8xvEQowAHoxIP74mphVFCrIll xZW5hxglOJiVRHi/xQCFeFMSK6tSi/Lji0pzUosPMUpzsCiJ85705I0SEkhPLEnNTk0tSC2C yTJxcEo1MOou03hi3f6rT6tl1SEW5YkPK/LCVJdOZztwSDx9qv+NqvkLE3Iec7gdOxGc7tC4 6tChgJ/FHN4Pl01yDJuVqFiz/i7bFO/DnW/zGOV0d3B/nfRt0aFWto2R0zVkd03nfhZWrnWt 5n5Uc+tXf95rVQu3hUi/j3y7odOYOUpQetvBG9vv/Prw4LoSS3FGoqEWc1FxIgBwKZkGmwIA AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lugSumaL1Yor1lqGfwxrtAp4yRw>
Subject: Re: [MMUSIC] BUNDLE: Some updates to RFC 3264 no longer needed? - Pull Request
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, 31 Jan 2018 11:06:52 -0000

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

Hi,

I had a look at the updates to RFC 3264. The updates to section 8.2 is no l=
onger needed, so I removed it.

I removed it in the pull request for editorial changes, in order to avoid m=
erge conflicts:

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

Regards,

Christer


From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Monday 29 January 2018 at 23:19
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, Ben Campbell <ben@nostrum.com<mailto:ben@nostrum.com>>
Subject: [MMUSIC] BUNDLE: Some updates to RFC 3264 no longer needed?

Hi,

One thing I noted when implementing the changes based on Ben=92s AD review.

The Introduction section of BUNDLE says:

   =93This specification also updates sections 5.1, 8.1 and 8.2 of RFC 3264
   [RFC3264].  The update allows an answerer to assign a non-zero port
   value to an "m=3D" section in an SDP answer, even if the "m=3D" section
   in the associated SDP offer contained a zero port value.=94

The changes are then done in Section 14.

Now, since the answerer no longer assigns the answerer BUNDLE address to al=
l m=3D sections in the answer (including m=3D sections that had a zero port=
 value in the associated offer), I actually don=92t think this update is ne=
eded anymore. That would of course be a good thing.

(We cannot completely remove Section 14, because we will still need the upd=
ate to RFC 3264 that allows usage of port zero without disabling/rejecting =
an m=3D section.)

I will create a PR for this later, once I=92ve dealt with Ben=92s review co=
mments.. Please let me know if have any questions.

Regards,

Christer



--_000_D697724E2A22Bchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <4CDB817D58251D4580E9CF9E2F09609D@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 had a look at the updates to RFC 3264. The updates to section 8.2 is=
 no longer needed, so I removed it.</div>
<div><br>
</div>
<div>I removed it in the pull request for editorial changes, in order to av=
oid merge conflicts:</div>
<div><br>
</div>
<div><a href=3D"https://github.com/cdh4u/draft-sdp-bundle/pull/55">https://=
github.com/cdh4u/draft-sdp-bundle/pull/55</a></div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday 29 January 2018 at 23:=
19<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;, Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com=
">ben@nostrum.com</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] BUNDLE: Some upda=
tes to RFC 3264 no longer needed?<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;
	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">One thing I noted when implementing the changes base=
d on Ben=92s AD review.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The Introduction section of BUNDLE says:<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; =93This specification also updates sect=
ions 5.1, 8.1 and 8.2 of RFC 3264<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; [RFC3264].&nbsp; The update allows an a=
nswerer to assign a non-zero port<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; value to an &quot;m=3D&quot; section in=
 an SDP answer, even if the &quot;m=3D&quot; section<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; in the associated SDP offer contained a=
 zero port value.=94<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The changes are then done in Section 14.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Now, since the answerer no longer assigns the answer=
er BUNDLE address to all m=3D sections in the answer (including m=3D sectio=
ns that had a zero port value in the associated offer), I actually don=92t =
think this update is needed anymore. That
 would of course be a good thing.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">(We cannot completely remove Section 14, because we =
will still need the update to RFC 3264 that allows usage of port zero witho=
ut disabling/rejecting an m=3D section.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I will create a PR for this later, once I=92ve dealt=
 with Ben=92s review comments.. Please let me know if have any questions.<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>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D697724E2A22Bchristerholmbergericssoncom_--


From nobody Wed Jan 31 12:14:32 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 35C3C1242EA; Wed, 31 Jan 2018 12:14:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.71.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151742967020.25735.5783626498868814736@ietfa.amsl.com>
Date: Wed, 31 Jan 2018 12:14:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LdAsZ-jYGoeKtD7_A5ICrpunpjU>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-bundle-negotiation-48.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, 31 Jan 2018 20:14:30 -0000

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

        Title           : Negotiating Media Multiplexing Using the Session Description Protocol (SDP)
        Authors         : Christer Holmberg
                          Harald Tveit Alvestrand
                          Cullen Jennings
	Filename        : draft-ietf-mmusic-sdp-bundle-negotiation-48.txt
	Pages           : 67
	Date            : 2018-01-31

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 without meaning that the media described by
   the "m=" section is disabled or rejected.

   This specification defines a new RTP Control Protocol (RTCP) source
   description (SDES) item and a new RTP header extension that van be
   used to correlate bundled RTP/RTCP packets with their appropriate
   "m=" section.


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-48
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-bundle-negotiation-48

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


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 Jan 31 12:16:50 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 1D51312ECC3 for <mmusic@ietfa.amsl.com>; Wed, 31 Jan 2018 12:16:49 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=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 q_6OetN8iAfm for <mmusic@ietfa.amsl.com>; Wed, 31 Jan 2018 12:16:48 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B91E126C89 for <mmusic@ietf.org>; Wed, 31 Jan 2018 12:16:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1517429805; 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=jQO4OlEwKfyXMxAG+92YZJohFpdVB/AWboN3eeZ9Acw=; b=JectmPewzZ5hDRVMoPefAlt4PyK7z+JLNSCH5AwEFovSGo3aDYAt52BEk7PwX6DH Q8eoCr1ffgoOyarqLIefgRnLwaiV8TTA1RRXtbVSlqMB7jgpu3u1ey1R9ARPAS7v bxa5Zx6P4b1WuHhuxv7Qe95tpQrbTHJZH9RSTqFyja0=;
X-AuditID: c1b4fb30-d31ff70000006bc7-84-5a72242cfb72
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id B7.AD.27591.C24227A5; Wed, 31 Jan 2018 21:16:44 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.195]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0352.000; Wed, 31 Jan 2018 21:16:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: MMUSIC <mmusic@ietf.org>, Ben Campbell <ben@nostrum.com>
CC: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Thread-Topic: Draft new version: BUNDLE-48
Thread-Index: AdOa0FWsQc5+caOWTKafOaU/Wj+Riw==
Date: Wed, 31 Jan 2018 20:16:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C14C665@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.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B6C14C665ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPLMWRmVeSWpSXmKPExsUyM2K7va6OSlGUwc8ZNhbzO0+zW5zfuZ7J YuryxywOzB5Llvxk8pi18wlLAFMUl01Kak5mWWqRvl0CV8btjxsZCx6LVlz895q1gXGlcBcj J4eEgInEvCmP2LoYuTiEBA4zSux9vZwRwlnCKNE+eSNrFyMHB5uAhUT3P22QBhEBG4mN/feZ QWxmAVOJh6/WMIKUCAuoSnzaVwxiighoSbw9GgxRrSfxZPk8sGoWoIpvj28zgdi8Ar4Sh8/O ZAexGQXEJL6fWsMEMVFc4taT+UwQpwlILNlznhnCFpV4+fgfK4StJLHo9meo+nyJkw93sULM FJQ4OfMJywRGoVlIRs1CUjYLSRlEXEdiwe5PbBC2tsSyha+ZYewzBx4zIYsvYGRfxShanFqc lJtuZKSXWpSZXFycn6eXl1qyiREYLQe3/DbYwfjyueMhRgEORiUeXi6Boigh1sSy4srcQ4wS HMxKIrwbRYBCvCmJlVWpRfnxRaU5qcWHGKU5WJTEeU968kYJCaQnlqRmp6YWpBbBZJk4OKUa GG0d7e5dXvW/yPGxyDn5PK9yuwYBw4tXZ0870uvIs2pekm/w19gtW0IFTmzv0K7ZvUmsbN+O 3qjU9P3OdsufNPZc9X/h6r1tGfvZtnzL00lrT6zZv7s8ouF5/uaLIcfObdywdc0rqyLjLXz/ pzSol9z31RE7VnOzbUdM5QG1xn//pk+9OaF1apYSS3FGoqEWc1FxIgDGs2mZkgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/I-Y9Ri4-6S2vu0g4Eq3Gofh7G_k>
Subject: [MMUSIC] Draft new version: BUNDLE-48
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, 31 Jan 2018 20:16:49 -0000

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

Hi,

I have submitted a new version (-48) of BUNDLE.

The new version includes the changes based on Ben's AD review.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B6C14C665ESESSMB109erics_
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 submitted a new version (-48) of BUNDLE.<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The new version includes the changes based on Ben&#8=
217;s AD review.<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_7594FB04B1934943A5C02806D1A2204B6C14C665ESESSMB109erics_--


From nobody Wed Jan 31 13:11:59 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 B1D0F12FAD9; Wed, 31 Jan 2018 13:11:56 -0800 (PST)
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 BHy70ajlfrQf; Wed, 31 Jan 2018 13:11:55 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D517F12FAD2; Wed, 31 Jan 2018 13:11:23 -0800 (PST)
Received: from [10.0.1.105] (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 w0VLBJ4X088873 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 31 Jan 2018 15:11:20 -0600 (CST) (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.105]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <AD2E55FC-E513-4EB2-ACE8-CCA5BBC7F427@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_460F73DD-4093-456F-937A-C94B040396E6"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Wed, 31 Jan 2018 15:11:18 -0600
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C14C665@ESESSMB109.ericsson.se>
Cc: MMUSIC <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B6C14C665@ESESSMB109.ericsson.se>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/88DL_dwS0Wta72Ab2doRtqcQPY0>
Subject: Re: [MMUSIC] Draft new version: BUNDLE-48
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, 31 Jan 2018 21:11:57 -0000

--Apple-Mail=_460F73DD-4093-456F-937A-C94B040396E6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I requested IETF LC on this version.

Thanks!

Ben.

> On Jan 31, 2018, at 2:16 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> I have submitted a new version (-48) of BUNDLE.
>=20
> The new version includes the changes based on Ben=E2=80=99s AD review.
>=20
> Regards,
>=20
> Christer


--Apple-Mail=_460F73DD-4093-456F-937A-C94B040396E6
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlpyMPYACgkQgFZKbJXz
1A2vcxAAoQv3/zYU62zj0uUsqNnN3x7waBl2IAiFpZ65L/VmkyUnwy2FUCSgcLtv
BYaVehyU/ThL+82xCYbGEmPD3v5fEbhN3N9PA++lCqd0LjxkWeMu6/fy8tCDDqNN
aaX72geHuea1rPXjkUesqfvECis5Nqr090Ag4yeRe0HTDB8680CVJcvEKPFrd2vr
nyIHh+yck1/LA9v6aELiAIZjg6qd0fq7iCmQtePv3u3XI1DkvoZw0zbsROiQMl3x
43X+Nci2EY4XEnLlzhaJ+YjDyqej7gCbhOZYkeHsD54gIvDH5+yjzaD1LjLdyI5P
hcc7GZaoef5iVxFpQbLGh8c6MFWniciV1jEVLqLHRnX+jpSiEheKbz7vIMJh4vzm
DT2ws3I3P5Ibf0aezOeLE+pkYY+VkaDbuD4Rdojf0sTrRIlt1B2PNAK5VQnk2/BX
eo10G/Kxbqcn93uNtwxOGb1i5/yOubWfF9/zNME2tubDhcyRjeI+g9p2hPUxmUp6
GSUroKLkUa7PBEAnOBuFF7TYtYs3F/4w45Z1si7LmbuiJNNVxIoUW5W9pgHihOvt
sXljSt9KL2IosfzMSp6gFI6O1lqMhMnEUM/7gB++vnWMOZ7IPBPg9+KcFKTtOwet
7DzGMkI4AxXReJ7YCcq223EM1RtUyJCGU7JjqJdbZPStV7zd5Gs=
=JamM
-----END PGP SIGNATURE-----

--Apple-Mail=_460F73DD-4093-456F-937A-C94B040396E6--


From nobody Wed Jan 31 14:22:35 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 483BC12FB43; Wed, 31 Jan 2018 14:22:29 -0800 (PST)
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.71.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: fandreas@cisco.com, ben@nostrum.com, mmusic-chairs@ietf.org, mmusic@ietf.org, draft-ietf-mmusic-sdp-bundle-negotiation@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: <151743734924.7936.16721766411055989855.idtracker@ietfa.amsl.com>
Date: Wed, 31 Jan 2018 14:22:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/z1Zto_VppjdG3K9orkRQASNCd64>
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-sdp-bundle-negotiation-48.txt> (Negotiating Media Multiplexing Using the Session Description Protocol (SDP)) 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: Wed, 31 Jan 2018 22:22:29 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'Negotiating Media
Multiplexing Using the Session Description Protocol
   (SDP)'
  <draft-ietf-mmusic-sdp-bundle-negotiation-48.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-02-14. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This 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 without meaning that the media described by
   the "m=" section is disabled or rejected.

   This specification defines a new RTP Control Protocol (RTCP) source
   description (SDES) item and a new RTP header extension that van be
   used to correlate bundled RTP/RTCP packets with their appropriate
   "m=" section.




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

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


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


The document contains these normative downward references.
See RFC 3967 for additional information: 
    draft-holmberg-mmusic-sdp-multiplex-negotiation: Multiplexing Negotiation Using Session Description Protocol (SDP) Port Numbers (None - )



