
From nobody Mon May  2 12:06:38 2016
Return-Path: <alissa@cooperw.in>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E54412D602 for <mmusic@ietfa.amsl.com>; Mon,  2 May 2016 12:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=XBSdaKcf; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=lgxVC0+H
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BPe3GDbiybmT for <mmusic@ietfa.amsl.com>; Mon,  2 May 2016 12:06:34 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7792612D0BE for <mmusic@ietf.org>; Mon,  2 May 2016 12:06:34 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id D86E720391 for <mmusic@ietf.org>; Mon,  2 May 2016 15:06:33 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 02 May 2016 15:06:33 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=6sOhj l77T6MM63AMJM/20W6czJw=; b=XBSdaKcfNlwPhNhFIa9RIrlI6xC4cnDxhvjBt Jlc45tilGjVtFNbwMbcNSSwankjULWZm3e9Qtigp+JBTLaFCGPHWL1cKjVlHhwfh x3K+s9eYsLhQKyeis5KCZ7Gpqkh/j2G/eHwys2PzKO31nt3BG17HbQs+iNSkyRu8 7hsgE8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=6sOhjl77T6MM63AMJM/20W6czJw=; b=lgxVC 0+H+g5kivWWBUhYxTV9g5I7hZIdwFf+bzKDtQFIK4yPbInLXzu18Jg7fI6DUJhnK NQlPtRHRZ3QWG1yhUxB+oORLt8BooT/eQ3cujCI9ZZ6hqilzExiTmzkD9YOcJ2PP TJLuvHE9pTVT+6ehkkEMyDyIGurI8xlx5nshwI=
X-Sasl-enc: X7BGs6LibK91jLsvHTn8oR0p6HcP0D4E2OtIpl1g5KIe 1462215993
Received: from dhcp-171-68-20-160.cisco.com (dhcp-171-68-20-160.cisco.com [171.68.20.160]) by mail.messagingengine.com (Postfix) with ESMTPA id 16856C00012; Mon,  2 May 2016 15:06:33 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_47FF5856-8D80-419F-BC8C-407B31C2C9DB"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <90408933-ab1d-8636-9dfb-1b75443a04b8@cisco.com>
Date: Mon, 2 May 2016 12:06:31 -0700
Message-Id: <F8623009-9BC8-4C57-A7E4-19ABCFAF993F@cooperw.in>
References: <90408933-ab1d-8636-9dfb-1b75443a04b8@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/8PJCJqN1yqJ3Guk6GqKku8B9scw>
Cc: mmusic <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 May 2016 19:06:36 -0000

--Apple-Mail=_47FF5856-8D80-419F-BC8C-407B31C2C9DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

A few small things Ben and I noticed while reviewing =
draft-ietf-avtext-sdes-hdr-ext, which references this document:

In 15.1, the registry being referred to should be =E2=80=9CRTP SDES item =
types,=E2=80=9D not =E2=80=9CRTCP SDES item types.=E2=80=9D

In 15.2, the registry being referred to should be the "RTP SDES Compact =
Header Extensions=E2=80=9D sub-registry of the RTP Compact Header =
Extensions sub-registry (as defined in draft-ietf-avtext-sdes-hdr-ext).

I would also note that if the RTP SDES Compact Header Extensions =
sub-registry gets defined as described in =
draft-ietf-avtext-sdes-hdr-ext, it will require a number of items in the =
registration documentation for new entires (see 5.2 of that draft), so =
those would be required here to register MID.

Alissa

> On Apr 29, 2016, at 11:32 AM, Flemming Andreasen <fandreas@cisco.com> =
wrote:
>=20
> Greetings
>=20
> This is to announce a 2 week Working Last Call for
>=20
>    draft-ietf-mmusic-sdp-bundle-negotiation-29
>=20
> as Proposed Standard. Please note that we previously issued a WGLC on =
the -22 version (in June 2015), however, since there has been various =
updates since then, we want to give people a chance to properly review =
the current version one last time (hopefully).
>=20
> Please review and provide any comments you may have on the document by =
Friday, May 13, 2016. Comments should be sent to the document authors =
and the MMUSIC WG list. If you review the document but do not have any =
comments, please send a note to that effect as well.
>=20
> Thanks
>=20
>        Flemming (MMUSIC co-chair)
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


--Apple-Mail=_47FF5856-8D80-419F-BC8C-407B31C2C9DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">A few small things Ben and I noticed while =
reviewing draft-ietf-avtext-sdes-hdr-ext, which references this =
document:</div><div class=3D""><br class=3D""></div><div class=3D"">In =
15.1, the registry being referred to should be =E2=80=9CRTP SDES item =
types,=E2=80=9D not =E2=80=9CRTCP SDES item types.=E2=80=9D</div><div =
class=3D""><br class=3D""></div><div style=3D"widows: 1;" class=3D"">In =
15.2, the registry being referred to should be the "<span style=3D"widows:=
 1;" class=3D""><font size=3D"2" class=3D"">RTP SDES Compact Header =
Extensions=E2=80=9D sub-registry of the RTP Compact Header Extensions =
sub-registry (as defined in&nbsp;</font></span><font size=3D"2" =
class=3D"">draft-ietf-avtext-sdes-hdr-ext).</font></div><div =
style=3D"widows: 1;" class=3D""><font size=3D"2" class=3D""><br =
class=3D""></font></div><div style=3D"widows: 1;" class=3D""><font =
size=3D"2" class=3D"">I would also note that if the RTP SDES Compact =
Header Extensions sub-registry gets defined as described in =
draft-ietf-avtext-sdes-hdr-ext, it will require a number of items in the =
registration documentation for new entires (see 5.2 of that draft), so =
those would be required here to register MID.</font></div><div =
style=3D"widows: 1;" class=3D""><font size=3D"2" class=3D""><br =
class=3D""></font></div><div style=3D"widows: 1;" class=3D""><font =
size=3D"2" class=3D"">Alissa</font></div><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Apr 29, 2016, at 11:32 AM, =
Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com" =
class=3D"">fandreas@cisco.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Greetings<br class=3D""><br class=3D"">This is to announce a =
2 week Working Last Call for<br class=3D""><br class=3D""> =
&nbsp;&nbsp;&nbsp;draft-ietf-mmusic-sdp-bundle-negotiation-29<br =
class=3D""><br class=3D"">as Proposed Standard. Please note that we =
previously issued a WGLC on the -22 version (in June 2015), however, =
since there has been various updates since then, we want to give people =
a chance to properly review the current version one last time =
(hopefully).<br class=3D""><br class=3D"">Please review and provide any =
comments you may have on the document by Friday, May 13, 2016. Comments =
should be sent to the document authors and the MMUSIC WG list. If you =
review the document but do not have any comments, please send a note to =
that effect as well.<br class=3D""><br class=3D"">Thanks<br class=3D""><br=
 class=3D""> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Flemming (MMUSIC =
co-chair)<br class=3D""><br =
class=3D"">_______________________________________________<br =
class=3D"">mmusic mailing list<br class=3D""><a =
href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/mmusic<br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_47FF5856-8D80-419F-BC8C-407B31C2C9DB--


From nobody Wed May  4 11:31:08 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 280EF12D116; Wed,  4 May 2016 11:31:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160504183104.8370.17707.idtracker@ietfa.amsl.com>
Date: Wed, 04 May 2016 11:31:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/hI4OAo1yc7JxYkRKBvxeUUsJ7Qc>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 May 2016 18:31:04 -0000

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

        Title           : Updates to RFC 4572
        Author          : Christer Holmberg
	Filename        : draft-ietf-mmusic-4572-update-00.txt
	Pages           : 5
	Date            : 2016-05-04

Abstract:
   This document updates RFC 4572 by clarifying the usage of multiple
   SDP 'fingerprint' attributes with a single TLS connection.  The
   document also updates the preferred cipher suite to be used, and
   removes the requirement to use the same hash function for calculating
   the certificate fingerprint that is used to calculate the certificate
   signature.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-00


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 May  4 11:33:50 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF9D12D5B0 for <mmusic@ietfa.amsl.com>; Wed,  4 May 2016 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jBRjowoFmdgd for <mmusic@ietfa.amsl.com>; Wed,  4 May 2016 11:33:47 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F082612D5A4 for <mmusic@ietf.org>; Wed,  4 May 2016 11:33:46 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-57-572a40886e79
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6B.E7.18043.8804A275; Wed,  4 May 2016 20:33:44 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0248.002; Wed, 4 May 2016 20:33:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft submission: draft-ietf-mmusic-4572-update-00
Thread-Index: AdGmMGMNcrzaZ38ZTbuZaYPeelRyLA==
Date: Wed, 4 May 2016 18:33:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F93A64@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37F93A64ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsUyM2K7tG6Hg1a4weJpVhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxprehUwF3yUrvrb+ZGtg/CTWxcjJISFgIrHr8jcmCFtM4sK9 9WxdjFwcQgJHGCVeHprHDOEsZpTYcfEBUBUHB5uAhUT3P22QBhEBdYmve3uYQWxhAWuJbwdX MkPEHST6WyexQNh6En9uTWQEaWURUJHY9kQZJMwr4Cvxe8F0sL2MQHu/n1oDZjMLiEvcejIf 6h4BiSV7zjND2KISLx//Y4WwlSQalzxhhajPl5jyYjkLxExBiZMzn7BMYBSahWTULCRls5CU QcR1JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWMosWpxcW56UZGeqlFmcnFxfl5enmpJZsY gRFxcMtvqx2MB587HmIU4GBU4uFdEK4ZLsSaWFZcmXuIUYKDWUmE96etVrgQb0piZVVqUX58 UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGxtLHcd5VQiEfPd9sW80f9puN qf5m7w/1yxzNFVGzZ0+PUy3ftvbG9wmhNa88f/SY6ft5rZnXkSdQUDFJ4+KCPon1dY6v2QK7 jq67tOBH3Z8jE68tkwg44/ByGn/CI8dPF64FK+1Xd/q91GP7Mt2NLsF7k5NKc9ev+j6zprFy f35eMcedw+Glq5RYijMSDbWYi4oTAYJr3fqEAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/jVrkdmm5KE2qjS-mx0XDMO7aJsM>
Subject: [MMUSIC] Draft submission: draft-ietf-mmusic-4572-update-00
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 May 2016 18:33:49 -0000

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

Hi,

I've submitted the first version (-00) of draft-ietf-mmusic-4572-update-00.

This is just a copy (IANA considerations section added, though) of the late=
st version of draft-holmberg, and does *not* implement the recent discussio=
ns we've had regarding multiple fingerprints etc. That will be implemented =
in the next version, which will be submitted soon.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37F93A64ESESSMB209erics_
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-size:10.0pt;
	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&#8217;ve submitted the first version (-00) of draf=
t-ietf-mmusic-4572-update-00.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is just a copy (IANA considerations section add=
ed, though) of the latest version of draft-holmberg, and does *<b>not</b>* =
implement the recent discussions we&#8217;ve had regarding multiple fingerp=
rints etc. That will be implemented in the
 next version, which will be submitted soon.<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_7594FB04B1934943A5C02806D1A2204B37F93A64ESESSMB209erics_--


From nobody Thu May  5 23:53:57 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4809A12D0F2; Thu,  5 May 2016 23:53:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160506065354.26818.25092.idtracker@ietfa.amsl.com>
Date: Thu, 05 May 2016 23:53:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/7_emfRC1wLq7Dise0HY63jUTGwI>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-01.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2016 06:53:54 -0000

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

        Title           : Updates to RFC 4572
        Author          : Christer Holmberg
	Filename        : draft-ietf-mmusic-4572-update-01.txt
	Pages           : 6
	Date            : 2016-05-05

Abstract:
   This document updates RFC 4572 by clarifying the usage of multiple
   SDP 'fingerprint' attributes with a single TLS connection.  The
   document also updates the preferred cipher suite to be used, and
   removes the requirement to use the same hash function for calculating
   the certificate fingerprint that is used to calculate the certificate
   signature.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-4572-update-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 Thu May  5 23:57:22 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D360212D4FF; Thu,  5 May 2016 23:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHPnClePTam8; Thu,  5 May 2016 23:57:19 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93A9A12D1C9; Thu,  5 May 2016 23:57:18 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-c2-572c404ba9aa
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 55.8B.18043.B404C275; Fri,  6 May 2016 08:57:16 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0248.002; Fri, 6 May 2016 08:57:15 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrg==
Date: Fri, 6 May 2016 06:57:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37F95326ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42KZGbHdXtfHQSfcYFqHvsX5neuZLKYuf8zi wOSxZMlPpgDGKC6blNSczLLUIn27BK6Mt3tnsxbslK54OOsaSwNjm0QXIyeHhICJxO4Vd1kg bDGJC/fWs3UxcnEICRxhlJixbA0jhLOYUaL5+kTWLkYODjYBC4nuf9ogDSIC6hJf9/Ywg9jM AqYSD1+B1HNyCAvYSKxcv5wJosZRomX7RGYIW0/i7dqnYDaLgIpE59TZYDavgK/E06vbwI5g BDri+6k1TBAzxSVuPZnPBHGcgMSSPeeZIWxRiZeP/7FC2EoSi25/ZgI5jVkgX2LKYkmIkYIS J2c+YZnAKDwLyaRZCFWzkFRBlOhILNj9iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxhFi1OLi3PT jYz0Uosyk4uL8/P08lJLNjECI+bglt9WOxgPPnc8xCjAwajEw7vgl3a4EGtiWXFl7iFGCQ5m JRHeCfY64UK8KYmVValF+fFFpTmpxYcYpTlYlMR5/V8qhgsJpCeWpGanphakFsFkmTg4pRoY i4V3b3EQmOxjzKLv11envu31b1v9p9fX/Jge/H+zsdJx/9vallvSp0WdvMv+fN6TnL0rXte1 emgvnlXz6NTL1jn9ZiYRD+W5t2x37zftqNIuOni+POGroEHAIsu9/Plrbt6OrPunui398qc/ +y2ZYyV3dC871/Hyb8+yo9+ar8hEv3R6xf14qRJLcUaioRZzUXEiAKJhwCOUAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/--yd-pW-5noetcZ1UAxKYaB5yyg>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2016 06:57:21 -0000

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

Hi,

I've submitted a new version (-01) of draft-ietf-mmusic-4572-update. It now=
 contains updated fingerprint handling procedures, based on the discussions=
: the number of calculated fingerprints for a given cipher suite are indepe=
ndent of each other. And, it's enough that one fingerprint, calculated usin=
g an algorithm the receiver considers secure enough, matches the used certi=
ficiate.

There are currently no open issues in the draft, so I encourage people to t=
ake a look :)

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37F95326ESESSMB209erics_
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">I&#8217;ve submitted a new version (-01) of draft-ie=
tf-mmusic-4572-update. It now contains updated fingerprint handling procedu=
res, based on the discussions: the number of calculated fingerprints for a =
given cipher suite are independent of each
 other. And, it&#8217;s enough that one fingerprint, calculated using an al=
gorithm the receiver considers secure enough, matches the used certificiate=
.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are currently no open issues in the draft, so =
I encourage people to take a look :)<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_7594FB04B1934943A5C02806D1A2204B37F95326ESESSMB209erics_--


From nobody Fri May  6 01:35:16 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04DB412D0D3; Fri,  6 May 2016 01:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8JooEa1bTwy; Fri,  6 May 2016 01:35:12 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFB43126FDC; Fri,  6 May 2016 01:35:11 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-31-572c573d3b8e
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 92.A9.27088.D375C275; Fri,  6 May 2016 10:35:10 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0248.002; Fri, 6 May 2016 10:35:09 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Alissa Cooper <alissa@cooperw.in>, Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29
Thread-Index: AQHRokV1UogGos41jEypb/mBLiYWPp+l5WeAgAWuVjA=
Date: Fri, 6 May 2016 08:35:09 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F95743@ESESSMB209.ericsson.se>
References: <90408933-ab1d-8636-9dfb-1b75443a04b8@cisco.com> <F8623009-9BC8-4C57-A7E4-19ABCFAF993F@cooperw.in>
In-Reply-To: <F8623009-9BC8-4C57-A7E4-19ABCFAF993F@cooperw.in>
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_7594FB04B1934943A5C02806D1A2204B37F95743ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrPIsWRmVeSWpSXmKPExsUyM2K7h65duE64Qf8rHovpZ/4yWkyf9Y7N 4v0FXYupyx+zOLB4TPm9kdXjy5OXTB5LlvxkCmCO4rJJSc3JLEst0rdL4MqY/fgLW8G/3YwV q24sYWpgbNjO2MXIySEhYCJx4tYJKFtM4sK99WxdjFwcQgJHGCXW3vrJDOEsZpQ4PmcVSxcj BwebgIVE9z9tkAYRAT+J6ZsawGqYBToZJTZdngg2SVjAS+LG0VZWiCJvic//JrJA2FYSZ/b3 MYPMYRFQkXjRFwUS5hXwlXj67zgziC0kUCCxef9LNhCbU8BOYs6ihWBjGIGO+35qDROIzSwg LnHryXwmiKMFJJbsOc8MYYtKvHz8jxXCVpJYdPszVH2+xKlNO1ghdglKnJz5hGUCo+gsJKNm ISmbhaRsFtClzAKaEut36UOUKEpM6X7IDmFrSLTOmcuOLL6AkX0Vo2hxanFSbrqRkV5qUWZy cXF+nl5easkmRmA0Htzy22AH48vnjocYBTgYlXh4F/zSDhdiTSwrrsw9xCjBwawkwqsTohMu xJuSWFmVWpQfX1Sak1p8iFGag0VJnNf/pWK4kEB6YklqdmpqQWoRTJaJg1OqgVHU00uTK7d3 4+dGl8+eopkfnPzZsw+2pqizHf1V1vXUde309cWSF+WffnT4Y6bULlPey6x3s3Z2QQf3np/z o1jSrJ5K61oGv02cxGUYkbgm457J23U3vux9tK8j7Fzv+dbjh/bW+7DWbS7s56k5qxezZdfE 6jz9z9ssjGNZd/tL/fzOMcWuTomlOCPRUIu5qDgRAGbSZJbCAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-UxozMtAEmj-TUogQaQBzVP2OVc>
Cc: mmusic <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2016 08:35:15 -0000

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

SGkgQWxpc3NhLA0KDQpUaGFua3MgZm9yIHlvdXIgY29tbWVudHMhIFJlcGx5IGJlbG93Lg0KDQo+
QSBmZXcgc21hbGwgdGhpbmdzIEJlbiBhbmQgSSBub3RpY2VkIHdoaWxlIHJldmlld2luZyBkcmFm
dC1pZXRmLWF2dGV4dC1zZGVzLWhkci1leHQsIHdoaWNoIHJlZmVyZW5jZXMgdGhpcyBkb2N1bWVu
dDoNCj4NCj5JbiAxNS4xLCB0aGUgcmVnaXN0cnkgYmVpbmcgcmVmZXJyZWQgdG8gc2hvdWxkIGJl
IOKAnFJUUCBTREVTIGl0ZW0gdHlwZXMs4oCdIG5vdCDigJxSVENQIFNERVMgaXRlbSB0eXBlcy7i
gJ0NCg0KQ29ycmVjdC4gSeKAmWxsIGZpeCB0aGF0Lg0KDQo+SW4gMTUuMiwgdGhlIHJlZ2lzdHJ5
IGJlaW5nIHJlZmVycmVkIHRvIHNob3VsZCBiZSB0aGUgIlJUUCBTREVTIENvbXBhY3QgSGVhZGVy
IEV4dGVuc2lvbnPigJ0gc3ViLXJlZ2lzdHJ5IG9mIHRoZSBSVFAgQ29tcGFjdCBIZWFkZXIgRXh0
ZW5zaW9ucyBzdWItcmVnaXN0cnkgKGFzIGRlZmluZWQgaW4gZHJhZnQtaWV0Zi1hdnRleHQtc2Rl
cy1oZHItZXh0KS4NCg0KT2suDQoNCldoZW4gY2FuIHdlIGV4cGVjdCB0aGF0IG5ldyBzdWItcmVn
aXN0cnkgdG8gYmUgY3JlYXRlZD8gV2hhdCBpcyB0aGUgc3RhdHVzIG9mIGRyYWZ0LWlldGYtYXZ0
ZXh0LXNkZXMtaGRyLWV4dD8NCg0KPkkgd291bGQgYWxzbyBub3RlIHRoYXQgaWYgdGhlIFJUUCBT
REVTIENvbXBhY3QgSGVhZGVyIEV4dGVuc2lvbnMgc3ViLXJlZ2lzdHJ5IGdldHMgZGVmaW5lZCBh
cyBkZXNjcmliZWQgaW4gZHJhZnQtaWV0Zi1hdnRleHQtc2Rlcy1oZHItZXh0LCBpdCB3aWxsDQo+
cmVxdWlyZSBhIG51bWJlciBvZiBpdGVtcyBpbiB0aGUgcmVnaXN0cmF0aW9uIGRvY3VtZW50YXRp
b24gZm9yIG5ldyBlbnRpcmVzIChzZWUgNS4yIG9mIHRoYXQgZHJhZnQpLCBzbyB0aG9zZSB3b3Vs
ZCBiZSByZXF1aXJlZCBoZXJlIHRvIHJlZ2lzdGVyIE1JRC4NCg0KT2ssIEkgc2VlIHRoZSBmb2xs
b3dpbmc6DQoNCiAgICAgIOKAnFJldmlldyBwcm9jZXNzOiBTYW1lIGFzIGZvciBSVFAgSGVhZGVy
IEV4dGVuc2lvbnMgW1JGQzUyODVdDQogICAgICByZWdpc3RyeSwgd2l0aCB0aGUgZm9sbG93aW5n
IHJlcXVpcmVtZW50cyBhZGRlZCB0byB0aGUgZXhwZXJ0DQogICAgICByZXZpZXc64oCdDQoNCiAg
ICAgICAgICAgICAgV2hlbiBsb29raW5nIGF0IHNlY3Rpb24gOS4xIG9mIFJGQyA1Mjg1LCBhbGwg
dGhlIHJlcXVpcmVkIGluZm9ybWF0aW9uIGlzIHByb3ZpZGVkLiBSZWdhcmRpbmcgdGhlIHRoaW5n
cyB0aGUgZXhwZXJ0IHJldmlld2VyIGlzIHJlcXVpcmVkIHRvIGxvb2sgYXQsIGluIG15IG9waW5p
b24gaXQgaXMgYWxsIGNvdmVyZWQuIEJ1bGxldCA1IG9mIHNlY3Rpb24gOS4xIHdpbGwgYmUgY292
ZXJlZCB3aXRoIHRoZSBzdWdnZXN0ZWQgc2VjdXJpdHkvcHJpdmFjeSB0ZXh0IGJlbG93Lg0KDQog
ICAgICDigJwxLiAgQW55IHJlZ2lzdHJhdGlvbiB1c2luZyBhbiBFeHRlbnNpb24gVVJJIHRoYXQg
c3RhcnRzIHdpdGgNCiAgICAgICAgICAidXJuOmlldGY6cGFyYW1zOnJ0cC1oZHJleHQ6c2Rlczoi
IChTZWN0aW9uIDUuMSkgTVVTVCBhbHNvDQogICAgICAgICAgaGF2ZSBhIHJlZ2lzdGVyZWQgU291
cmNlIERlc2NyaXB0aW9uIGl0ZW0gaW4gdGhlICJSVFAgU0RFUw0KICAgICAgICAgIGl0ZW0gdHlw
ZXMiIHJlZ2lzdHJ5LuKAnQ0KDQogICAgICAgICAgICAgIERvbmUuIFNlZSBzZWN0aW9uIDE1LjEu
DQoNCg0KICAgICAg4oCcMi4gIEEgc2VjdXJpdHkgYW5kIHByaXZhY3kgY29uc2lkZXJhdGlvbiBm
b3IgdGhlIFNERVMgaXRlbSBNVVNUIGJlDQogICAgICAgICAgcHJvdmlkZWQgd2l0aCB0aGUgcmVn
aXN0cmF0aW9uLuKAnQ0KDQogICAgICAgICAgIEkgc3VnZ2VzdCB0aGUgZm9sbG93aW5nIHRleHQ6
DQoNCiAgICAgICAgICAg4oCcVGhlIFNERVMgaXRlbSBkb2VzIG5vdCByZXZlYWwgcHJpdmFjeSBp
bmZvcm1hdGlvbiBhYm91dCB0aGUgdXNlcnMuIEl0DQogICAgICAgICAgICAgaXMgc2ltcGx5IHVz
ZWQgdG8gYXNzb2NpYXRlIFJUUC1iYXNlZCBtZWRpYSB3aXRoIHRoZSBjb3JyZWN0IFNEUCBtZWRp
YQ0KICAgICAgICAgICAgIGRlc2NyaXB0aW9uIChtLSBsaW5lKSBpbiB0aGUgU0RQIHVzZWQgdG8g
bmVnb3RpYXRlIHRoZSBtZWRpYS7igJ0NCg0KDQogICAgICDigJwzLiAgSW5mb3JtYXRpb24gTVVT
VCBiZSBwcm92aWRlZCBvbiB3aHkgdGhpcyBTREVTIGl0ZW0gcmVxdWlyZXMNCiAgICAgICAgICB0
aW1lbHkgZGVsaXZlcnksIG1vdGl2YXRpbmcgaXQgdG8gYmUgdHJhbnNwb3J0ZWQgaW4gYSBoZWFk
ZXINCiAgICAgICAgICBleHRlbnNpb24gcmF0aGVyIHRoYW4gYXMgUlRDUCBvbmx5LuKAnQ0KDQog
ICAgICAgICAgICAgIEkgc3VnZ2VzdCB0aGUgZm9sbG93aW5nIHRleHQ6DQoNCiAgICAgICAgICAg
ICAg4oCcVGhlIHB1cnBvc2Ugb2YgdGhlIGV4dGVuc2lvbiBpcyBmb3IgdGhlIG9mZmVyZXIgdG8g
YmUgYWJsZSB0byBhc3NvY2lhdGUNCiAgICAgICAgICAgICAgcmVjZWl2ZWQgbXVsdGlwbGV4ZWQg
UlRQLWJhc2VkIG1lZGlhIGJlZm9yZSB0aGUgb2ZmZXJlciByZWNlaXZlcyB0aGUNCiAgICAgICAg
ICAgICAgYXNzb2NpYXRlZCBTRFAgYW5zd2VyLiBTZWUgc2VjdGlvbiAxNCBmb3IgbW9yZSBkZXRh
aWxzLuKAnQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCk9uIEFwciAyOSwgMjAxNiwgYXQg
MTE6MzIgQU0sIEZsZW1taW5nIEFuZHJlYXNlbiA8ZmFuZHJlYXNAY2lzY28uY29tPG1haWx0bzpm
YW5kcmVhc0BjaXNjby5jb20+PiB3cm90ZToNCg0KR3JlZXRpbmdzDQoNClRoaXMgaXMgdG8gYW5u
b3VuY2UgYSAyIHdlZWsgV29ya2luZyBMYXN0IENhbGwgZm9yDQoNCiAgIGRyYWZ0LWlldGYtbW11
c2ljLXNkcC1idW5kbGUtbmVnb3RpYXRpb24tMjkNCg0KYXMgUHJvcG9zZWQgU3RhbmRhcmQuIFBs
ZWFzZSBub3RlIHRoYXQgd2UgcHJldmlvdXNseSBpc3N1ZWQgYSBXR0xDIG9uIHRoZSAtMjIgdmVy
c2lvbiAoaW4gSnVuZSAyMDE1KSwgaG93ZXZlciwgc2luY2UgdGhlcmUgaGFzIGJlZW4gdmFyaW91
cyB1cGRhdGVzIHNpbmNlIHRoZW4sIHdlIHdhbnQgdG8gZ2l2ZSBwZW9wbGUgYSBjaGFuY2UgdG8g
cHJvcGVybHkgcmV2aWV3IHRoZSBjdXJyZW50IHZlcnNpb24gb25lIGxhc3QgdGltZSAoaG9wZWZ1
bGx5KS4NCg0KUGxlYXNlIHJldmlldyBhbmQgcHJvdmlkZSBhbnkgY29tbWVudHMgeW91IG1heSBo
YXZlIG9uIHRoZSBkb2N1bWVudCBieSBGcmlkYXksIE1heSAxMywgMjAxNi4gQ29tbWVudHMgc2hv
dWxkIGJlIHNlbnQgdG8gdGhlIGRvY3VtZW50IGF1dGhvcnMgYW5kIHRoZSBNTVVTSUMgV0cgbGlz
dC4gSWYgeW91IHJldmlldyB0aGUgZG9jdW1lbnQgYnV0IGRvIG5vdCBoYXZlIGFueSBjb21tZW50
cywgcGxlYXNlIHNlbmQgYSBub3RlIHRvIHRoYXQgZWZmZWN0IGFzIHdlbGwuDQoNClRoYW5rcw0K
DQogICAgICAgRmxlbW1pbmcgKE1NVVNJQyBjby1jaGFpcikNCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5nIGxpc3QNCm1tdXNp
Y0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl
eHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtz
aXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0
O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNw
aWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHht
bD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBk
YXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0K
PGJvZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFz
cz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5IaSBBbGlzc2EsPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UaGFua3MgZm9yIHlvdXIgY29tbWVu
dHMhIFJlcGx5IGJlbG93LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZn
dDtBIGZldyBzbWFsbCB0aGluZ3MgQmVuIGFuZCBJIG5vdGljZWQgd2hpbGUgcmV2aWV3aW5nIGRy
YWZ0LWlldGYtYXZ0ZXh0LXNkZXMtaGRyLWV4dCwgd2hpY2ggcmVmZXJlbmNlcyB0aGlzIGRvY3Vt
ZW50OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jmd0O0luIDE1LjEsIHRoZSByZWdpc3RyeSBiZWluZyByZWZlcnJlZCB0byBzaG91bGQg
YmUg4oCcUlRQIFNERVMgaXRlbSB0eXBlcyzigJ0gbm90IOKAnFJUQ1AgU0RFUyBpdGVtIHR5cGVz
LuKAnTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPkNvcnJlY3QuIEnigJlsbCBmaXggdGhhdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDtJbiAxNS4yLCB0
aGUgcmVnaXN0cnkgYmVpbmcgcmVmZXJyZWQgdG8gc2hvdWxkIGJlIHRoZSAmcXVvdDs8c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdCI+UlRQIFNERVMgQ29tcGFjdCBIZWFkZXIgRXh0ZW5zaW9u
c+KAnSBzdWItcmVnaXN0cnkgb2YgdGhlIFJUUCBDb21wYWN0IEhlYWRlciBFeHRlbnNpb25zIHN1
Yi1yZWdpc3RyeSAoYXMgZGVmaW5lZCBpbiZuYnNwO2RyYWZ0LWlldGYtYXZ0ZXh0LXNkZXMtaGRy
LWV4dCkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPk9rLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5XaGVuIGNhbiB3ZSBleHBl
Y3QgdGhhdCBuZXcgc3ViLXJlZ2lzdHJ5IHRvIGJlIGNyZWF0ZWQ/IFdoYXQgaXMgdGhlIHN0YXR1
cyBvZiBkcmFmdC1pZXRmLWF2dGV4dC1zZGVzLWhkci1leHQ/PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdCI+Jmd0O0kgd291bGQgYWxzbyBub3RlIHRoYXQgaWYgdGhlIFJUUCBTREVT
IENvbXBhY3QgSGVhZGVyIEV4dGVuc2lvbnMgc3ViLXJlZ2lzdHJ5IGdldHMgZGVmaW5lZCBhcyBk
ZXNjcmliZWQgaW4gZHJhZnQtaWV0Zi1hdnRleHQtc2Rlcy1oZHItZXh0LCBpdCB3aWxsDQo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PiZndDs8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPnJlcXVpcmUgYSBudW1i
ZXIgb2YgaXRlbXMgaW4gdGhlIHJlZ2lzdHJhdGlvbiBkb2N1bWVudGF0aW9uIGZvciBuZXcgZW50
aXJlcyAoc2VlIDUuMiBvZiB0aGF0IGRyYWZ0KSwgc28gdGhvc2Ugd291bGQgYmUgcmVxdWlyZWQg
aGVyZQ0KIHRvIHJlZ2lzdGVyIE1JRC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+T2ssIEkgc2VlIHRoZSBmb2xs
b3dpbmc6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyDigJxS
ZXZpZXcgcHJvY2VzczogU2FtZSBhcyBmb3IgUlRQIEhlYWRlciBFeHRlbnNpb25zIFtSRkM1Mjg1
XTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJlZ2lzdHJ5LCB3aXRoIHRoZSBm
b2xsb3dpbmcgcmVxdWlyZW1lbnRzIGFkZGVkIHRvIHRoZSBleHBlcnQ8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyByZXZpZXc64oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBXaGVuIGxvb2tpbmcgYXQgc2VjdGlvbiA5LjEgb2YgUkZDIDUyODUsIGFsbCB0
aGUgcmVxdWlyZWQgaW5mb3JtYXRpb24gaXMgcHJvdmlkZWQuIFJlZ2FyZGluZyB0aGUgdGhpbmdz
IHRoZSBleHBlcnQgcmV2aWV3ZXIgaXMgcmVxdWlyZWQgdG8gbG9vayBhdCwgaW4gbXkgb3Bpbmlv
bg0KIGl0IGlzIGFsbCBjb3ZlcmVkLiBCdWxsZXQgNSBvZiBzZWN0aW9uIDkuMSB3aWxsIGJlIGNv
dmVyZWQgd2l0aCB0aGUgc3VnZ2VzdGVkIHNlY3VyaXR5L3ByaXZhY3kgdGV4dCBiZWxvdy48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwO+KAnDEuJm5ic3A7IEFu
eSByZWdpc3RyYXRpb24gdXNpbmcgYW4gRXh0ZW5zaW9uIFVSSSB0aGF0IHN0YXJ0cyB3aXRoPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
JnF1b3Q7dXJuOmlldGY6cGFyYW1zOnJ0cC1oZHJleHQ6c2RlczomcXVvdDsgKFNlY3Rpb24gNS4x
KSBNVVNUIGFsc288bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBoYXZlIGEgcmVnaXN0ZXJlZCBTb3VyY2UgRGVzY3JpcHRpb24gaXRlbSBp
biB0aGUgJnF1b3Q7UlRQIFNERVM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBpdGVtIHR5cGVzJnF1b3Q7IHJlZ2lzdHJ5LuKAnTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgRG9uZS4gU2VlIHNlY3Rpb24gMTUuMS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
4oCcMi4mbmJzcDsgQSBzZWN1cml0eSBhbmQgcHJpdmFjeSBjb25zaWRlcmF0aW9uIGZvciB0aGUg
U0RFUyBpdGVtIE1VU1QgYmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyBwcm92aWRlZCB3aXRoIHRoZSByZWdpc3RyYXRpb24u4oCdPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBJIHN1Z2dlc3QgdGhlIGZvbGxvd2luZyB0ZXh0OjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsg4oCcVGhlIFNERVMgaXRlbSBkb2VzIG5vdCByZXZlYWwgcHJpdmFjeSBpbmZvcm1h
dGlvbiBhYm91dCB0aGUgdXNlcnMuIEl0PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgaXMgc2ltcGx5IHVz
ZWQgdG8gYXNzb2NpYXRlIFJUUC1iYXNlZCBtZWRpYSB3aXRoIHRoZSBjb3JyZWN0IFNEUCBtZWRp
YTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRlc2NyaXB0aW9uIChtLSBsaW5lKSBpbiB0aGUgU0RQIHVz
ZWQgdG8gbmVnb3RpYXRlIHRoZSBtZWRpYS7igJ08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg4oCcMy4mbmJzcDsgSW5mb3JtYXRpb24gTVVT
VCBiZSBwcm92aWRlZCBvbiB3aHkgdGhpcyBTREVTIGl0ZW0gcmVxdWlyZXM8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0aW1lbHkgZGVs
aXZlcnksIG1vdGl2YXRpbmcgaXQgdG8gYmUgdHJhbnNwb3J0ZWQgaW4gYSBoZWFkZXI8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBleHRl
bnNpb24gcmF0aGVyIHRoYW4gYXMgUlRDUCBvbmx5LuKAnTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgSSBzdWdnZXN0IHRoZSBmb2xsb3dpbmcgdGV4dDo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IOKAnFRoZSBwdXJwb3NlIG9mIHRoZSBleHRlbnNpb24g
aXMgZm9yIHRoZSBvZmZlcmVyIHRvIGJlIGFibGUgdG8gYXNzb2NpYXRlPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgcmVjZWl2ZWQgbXVsdGlwbGV4ZWQgUlRQLWJhc2VkIG1lZGlhIGJlZm9yZSB0
aGUgb2ZmZXJlciByZWNlaXZlcyB0aGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBhc3NvY2lh
dGVkIFNEUCBhbnN3ZXIuIFNlZSBzZWN0aW9uIDE0IGZvciBtb3JlIGRldGFpbHMu4oCdPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWYiPlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkNocmlzdGVyDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4w
cHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24g
QXByIDI5LCAyMDE2LCBhdCAxMTozMiBBTSwgRmxlbW1pbmcgQW5kcmVhc2VuICZsdDs8YSBocmVm
PSJtYWlsdG86ZmFuZHJlYXNAY2lzY28uY29tIj5mYW5kcmVhc0BjaXNjby5jb208L2E+Jmd0OyB3
cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkdyZWV0
aW5nczxicj4NCjxicj4NClRoaXMgaXMgdG8gYW5ub3VuY2UgYSAyIHdlZWsgV29ya2luZyBMYXN0
IENhbGwgZm9yPGJyPg0KPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7ZHJhZnQtaWV0Zi1tbXVzaWMt
c2RwLWJ1bmRsZS1uZWdvdGlhdGlvbi0yOTxicj4NCjxicj4NCmFzIFByb3Bvc2VkIFN0YW5kYXJk
LiBQbGVhc2Ugbm90ZSB0aGF0IHdlIHByZXZpb3VzbHkgaXNzdWVkIGEgV0dMQyBvbiB0aGUgLTIy
IHZlcnNpb24gKGluIEp1bmUgMjAxNSksIGhvd2V2ZXIsIHNpbmNlIHRoZXJlIGhhcyBiZWVuIHZh
cmlvdXMgdXBkYXRlcyBzaW5jZSB0aGVuLCB3ZSB3YW50IHRvIGdpdmUgcGVvcGxlIGEgY2hhbmNl
IHRvIHByb3Blcmx5IHJldmlldyB0aGUgY3VycmVudCB2ZXJzaW9uIG9uZSBsYXN0IHRpbWUgKGhv
cGVmdWxseSkuPGJyPg0KPGJyPg0KUGxlYXNlIHJldmlldyBhbmQgcHJvdmlkZSBhbnkgY29tbWVu
dHMgeW91IG1heSBoYXZlIG9uIHRoZSBkb2N1bWVudCBieSBGcmlkYXksIE1heSAxMywgMjAxNi4g
Q29tbWVudHMgc2hvdWxkIGJlIHNlbnQgdG8gdGhlIGRvY3VtZW50IGF1dGhvcnMgYW5kIHRoZSBN
TVVTSUMgV0cgbGlzdC4gSWYgeW91IHJldmlldyB0aGUgZG9jdW1lbnQgYnV0IGRvIG5vdCBoYXZl
IGFueSBjb21tZW50cywgcGxlYXNlIHNlbmQgYSBub3RlIHRvIHRoYXQgZWZmZWN0IGFzDQogd2Vs
bC48YnI+DQo8YnI+DQpUaGFua3M8YnI+DQo8YnI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDtGbGVtbWluZyAoTU1VU0lDIGNvLWNoYWlyKTxicj4NCjxicj4NCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KbW11c2lj
IG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciPm1tdXNp
Y0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21tdXNpYyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
bXVzaWM8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_7594FB04B1934943A5C02806D1A2204B37F95743ESESSMB209erics_--


From nobody Fri May  6 08:55:32 2016
Return-Path: <docfaraday@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 A9E4012B03D for <mmusic@ietfa.amsl.com>; Fri,  6 May 2016 08:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 aEiBF3T3ZYbZ for <mmusic@ietfa.amsl.com>; Fri,  6 May 2016 08:55:29 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56FEF12D097 for <mmusic@ietf.org>; Fri,  6 May 2016 08:45:54 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id v145so142911769oie.0 for <mmusic@ietf.org>; Fri, 06 May 2016 08:45:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=3T8Ncgqx7scYZ6cGR3wbO0/Wt4YTIcpehZgK+TiHVqQ=; b=VsEU3fLjIHSv69vUR9kIeUU53HcatNnQ3JWLHdEcJyhHoWnRjk07r2H5tcXj9GiX3D xs1pdtPRkP23Vf+O/BlWK6lqr6VyxT9XB1f7u4QZO4uK/YgxkLnJRM/HjsFunZonewuP cufJCab/qIk19YLelve8la1QEwMTPZn7OwFme8Qy67SJP5Ama18wO6yGg6pTcvGeJr/3 plQ5LOHIgjoY05CpEBOiHvSsJkNWgiC6K7lbfSzWnuM1AspUUGelA/pe3wJTFufcI92/ npHF3Y+aID1QznokQjs11EcrlcOtXvcsGD1kwK/NxCH/cHurnyoFH8ihmSe4lYho4xJp AYQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=3T8Ncgqx7scYZ6cGR3wbO0/Wt4YTIcpehZgK+TiHVqQ=; b=AwKjs7pxizSexsQ8/kBMaw/BmzK4I2tTdakyPry6rqTo1QxxLZa3RZBiH4WAwMcZe0 vG7TLwCYMxhjI7RRH4IjxoA5NJpQK+vQO62eDzcuxc2ZdiTH+bEMxSQODXsKhPkJOB3i tmgZtsvDOa9GHn72lc5+VXBwVqenLH3Ed4u5nxdugHAyYB5/0pN6XjR/Z5dkY00Jukzj PyCWOsdOFaQRwXrRYSiNiC4IgElnUp2oNtpZKy6d4BCYEadsFirMkjIC3+xY7VUP63hT jqpqcQTOSxgnrWqStaxip6xVsxRuX0Gu9OwUQpoNNpjrHCBC1yKEOLvpVINx5invQ3Sm ubfA==
X-Gm-Message-State: AOPr4FVQ4MdPdsObwbeUGIz4JXFRhgK00VKIrtjg1BxHt8P9uXzRWkDDDKHahIRqZcla4A==
X-Received: by 10.157.14.236 with SMTP id 99mr9757195otj.83.1462549553727; Fri, 06 May 2016 08:45:53 -0700 (PDT)
Received: from ?IPv6:2602:306:83ae:c480:e8d8:beed:3ac4:d21c? ([2602:306:83ae:c480:e8d8:beed:3ac4:d21c]) by smtp.googlemail.com with ESMTPSA id w140sm4975898oif.24.2016.05.06.08.45.52 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 May 2016 08:45:52 -0700 (PDT)
To: mmusic@ietf.org
From: Byron Campen <docfaraday@gmail.com>
Message-ID: <aa358143-2c23-0351-a8b2-0b815dd2a767@gmail.com>
Date: Fri, 6 May 2016 10:45:54 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/gMbxd-RYRoK_LzXlWnwEWPwkuq0>
Subject: [MMUSIC] ICE triggered check behavior can backfire when using aggressive nomination
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2016 15:55:30 -0000

     I've written out the details at 
https://bugzilla.mozilla.org/show_bug.cgi?id=1268961 , but the essence 
of the problem is that an incoming ICE check can cause a high priority 
in-progress pair to transition to waiting (due to the triggered check 
rules), which leaves it vulnerable to removal from the check list when 
nomination happens on a lower priority pair. Without the incoming ICE 
check, the high priority pair would have remained in-progress, and would 
eventually have reached nomination.

     It doesn't seem right to me that an incoming ICE check on a high 
priority pair could prevent that pair from reaching nomination when 
aggressive nomination is in use. It also doesn't seem right to me that 
receiving an incoming ICE check would cause a pair to transition from 
in-progress to waiting, given that the intent in the spec is to fast 
track that pair, and not put it on the back burner.

     It seems to me that prohibiting this in-progress -> waiting 
transition is the way to go, but it would also be reasonable to take 
priority into account when removing pairs from the triggered check queue 
(or maybe even never remove pairs from the triggered check queue).

Best regards,
Byron Campen


From nobody Fri May  6 16:10:24 2016
Return-Path: <pthatcher@google.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC7612D0C1 for <mmusic@ietfa.amsl.com>; Fri,  6 May 2016 16:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.696
X-Spam-Level: 
X-Spam-Status: No, score=-3.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyelOrqWS1sd for <mmusic@ietfa.amsl.com>; Fri,  6 May 2016 16:10:20 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22C0A12B017 for <mmusic@ietf.org>; Fri,  6 May 2016 16:10:20 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id m64so146831348lfd.1 for <mmusic@ietf.org>; Fri, 06 May 2016 16:10:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uYRBrNAneVVrZ+Lefm9cLq/Nxx8Kwu82LGvGHNgUoKQ=; b=b+5+5o28QU9yubrtjUmUZO+6s0+LoROEcaraQS4LllNn89P474V1+uD0boVufjzCfu bl6e1H6JYhOx1m/1cYUIYxxcWXjY4jwXjJLqPoZqcpntEaM/M3/yvPkkxCdyPDqc3tJi z/+vvkbtvwG1h9qMrM0xVKBd1GXQ6CsuLHuBLmW2CNMpVRe701FjnKblHHhjsud9hkFt Ce3F0A6zD+5NmFAIWt1JWn292rbUeh0LInit6f44VUw56fV13G99XhWoK90/3b7dJlBS 4pIWsh7WJyx36ssOW9+HQh8UWoe26ajsQA9XM5+GRbJIi/GmKRj0aZRkG7MMaTgk+7bL c52g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uYRBrNAneVVrZ+Lefm9cLq/Nxx8Kwu82LGvGHNgUoKQ=; b=IB/4Gxf4in0YSyY4+eBzmlMwCoPR4jifW9cg9zCjXwozpOpCIURmsilGB3aLY0jcFk my/g6FrBPOZBzMaiX/MfkDqqp0JDJWEcq3QPqO7zkC6ZzI97BEEg74cbBngZFr+quZqH 1sh1MJX8rp0tWZEhKmh5At5WdFakViyS+gEOTstzPL//0fLsTdCoLCCFH61y8FHrl7sZ md+7FLiz3Wi5/2IwnGcZVjCUZu75ulFaxCNt+haa6E12KZuXxXGoj+SkHPhinVXNmA6g 7+O49wdmw5+QKh00zSeRV/AupN0e1Z0tHumqdiNOmn5+YLuxZWIwdb8MQ/bzE7kSd8UQ t7LQ==
X-Gm-Message-State: AOPr4FXb/+47mIRXjG2DuHlWLGAlT/BeDsF5wn+lKq7ftFfa/gtJxu3m4YmlTxpWW5h4mzVsabYJ/Uk1sTqcrq7U
X-Received: by 10.25.32.213 with SMTP id g204mr10638819lfg.119.1462576218212;  Fri, 06 May 2016 16:10:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.208.208 with HTTP; Fri, 6 May 2016 16:09:38 -0700 (PDT)
In-Reply-To: <aa358143-2c23-0351-a8b2-0b815dd2a767@gmail.com>
References: <aa358143-2c23-0351-a8b2-0b815dd2a767@gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 6 May 2016 16:09:38 -0700
Message-ID: <CAJrXDUEzaNzannB2aBygvt1w-N7WgmUqdHX_uw=QXdF6LjUjMA@mail.gmail.com>
To: Byron Campen <docfaraday@gmail.com>
Content-Type: multipart/alternative; boundary=001a11401fecf1d5690532348fc5
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/q4o6HohajcP9IEyEUqdjxGw-REg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE triggered check behavior can backfire when using aggressive nomination
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 May 2016 23:10:23 -0000

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

=E2=80=8BShouldn't this be posted to the ICE WG?=E2=80=8B

On Fri, May 6, 2016 at 8:45 AM, Byron Campen <docfaraday@gmail.com> wrote:

>     I've written out the details at
> https://bugzilla.mozilla.org/show_bug.cgi?id=3D1268961 , but the essence =
of
> the problem is that an incoming ICE check can cause a high priority
> in-progress pair to transition to waiting (due to the triggered check
> rules), which leaves it vulnerable to removal from the check list when
> nomination happens on a lower priority pair. Without the incoming ICE
> check, the high priority pair would have remained in-progress, and would
> eventually have reached nomination.
>
>     It doesn't seem right to me that an incoming ICE check on a high
> priority pair could prevent that pair from reaching nomination when
> aggressive nomination is in use. It also doesn't seem right to me that
> receiving an incoming ICE check would cause a pair to transition from
> in-progress to waiting, given that the intent in the spec is to fast trac=
k
> that pair, and not put it on the back burner.
>
>     It seems to me that prohibiting this in-progress -> waiting transitio=
n
> is the way to go, but it would also be reasonable to take priority into
> account when removing pairs from the triggered check queue (or maybe even
> never remove pairs from the triggered check queue).
>
> Best regards,
> Byron Campen
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">=E2=80=8BShouldn&#39;t this be posted to the ICE WG?=E2=
=80=8B</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Fri, May 6, 2016 at 8:45 AM, Byron Campen <span dir=3D"ltr">&lt;<a href=
=3D"mailto:docfaraday@gmail.com" target=3D"_blank">docfaraday@gmail.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=C2=A0 =C2=A0 I&#39;ve=
 written out the details at <a href=3D"https://bugzilla.mozilla.org/show_bu=
g.cgi?id=3D1268961" rel=3D"noreferrer" target=3D"_blank">https://bugzilla.m=
ozilla.org/show_bug.cgi?id=3D1268961</a> , but the essence of the problem i=
s that an incoming ICE check can cause a high priority in-progress pair to =
transition to waiting (due to the triggered check rules), which leaves it v=
ulnerable to removal from the check list when nomination happens on a lower=
 priority pair. Without the incoming ICE check, the high priority pair woul=
d have remained in-progress, and would eventually have reached nomination.<=
br>
<br>
=C2=A0 =C2=A0 It doesn&#39;t seem right to me that an incoming ICE check on=
 a high priority pair could prevent that pair from reaching nomination when=
 aggressive nomination is in use. It also doesn&#39;t seem right to me that=
 receiving an incoming ICE check would cause a pair to transition from in-p=
rogress to waiting, given that the intent in the spec is to fast track that=
 pair, and not put it on the back burner.<br>
<br>
=C2=A0 =C2=A0 It seems to me that prohibiting this in-progress -&gt; waitin=
g transition is the way to go, but it would also be reasonable to take prio=
rity into account when removing pairs from the triggered check queue (or ma=
ybe even never remove pairs from the triggered check queue).<br>
<br>
Best regards,<br>
Byron Campen<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div><br></div>

--001a11401fecf1d5690532348fc5--


From nobody Sun May  8 16:55:25 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A079512D0FE; Sun,  8 May 2016 16:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WwtM-2B8bO-g; Sun,  8 May 2016 16:55:22 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66FE12D0D8; Sun,  8 May 2016 16:55:21 -0700 (PDT)
Received: by mail-ig0-x236.google.com with SMTP id bi2so91013083igb.0; Sun, 08 May 2016 16:55:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=BxN4K3oMlfr4aGXDAO3o5a1nebtEK2fqFhrEoZeSHjA=; b=tD1l+1oWZTymA3xJiijLzY05H8pIzwluy+YzuI97kufdBI0gg5T0X9ZqTHs5Wt8WOz WcrsLotFcOkpzU6MDyIp3hnqNB7EnpwhquLQbWHzpLo0HltWGufeHBwcKV512PCTi8o0 gT7SDqNwTnFiHG/HTGgLIectTFAC5pMVxKA7HrttVh94+E+JBiUy9ZQ2ArHsPDhKaTL+ DcfFJljvEztQNlaHctd/lafxFhBacrmZlxSGWYOdAKOR2+Dj0JDjYgnzYKDIur+A3LcU 5rx8aiJwuYhfJB3/Y/cudNikf0d6/RbSJIADhK9LI9Q9kl4paYnjb1UDE6qezZuXQlBl oCKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=BxN4K3oMlfr4aGXDAO3o5a1nebtEK2fqFhrEoZeSHjA=; b=IoclyWwOIg2C3O8nsenjGRxtwJwe+zqx7bNJh+Dh4Raw2t+VPpQQO7wpz0PArXd8Pl cymzLD6Ihx/gnlrXojWU0pEQWrET6RB7HEWOUBjld+x9ospfH+i/VIYzSbRdrSTeJgMp uP0zRNUEqUOUNZCcbHSXnBrfWBSRQNOI5qEhPcLQq6CjQll+OAsXZDdpKtOYd5xVmz9J E9LIMTJzbvrp8B4uwYcJO/AtapiKrDETWyGF7NPHoczfiR1621sCQz46vH1B9zIc+1p7 DbcxHtRLIhQ9oznerp/A8Cy9Aqg7C9Gj5UH12TA7V8dyZWebStIYACrt8R4/4ou/DO+1 HW1Q==
X-Gm-Message-State: AOPr4FUJK+/FRnrPRJM0M9yRN1jaikdGRjf3BwZNw/EMRt2FA2SWPkOWX35Z8KVnPe5GLjzZ7cl2qrQ2ezhWOQ==
MIME-Version: 1.0
X-Received: by 10.50.59.211 with SMTP id b19mr8397273igr.58.1462751721198; Sun, 08 May 2016 16:55:21 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sun, 8 May 2016 16:55:21 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se>
Date: Mon, 9 May 2016 09:55:21 +1000
Message-ID: <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/2y0oj3sHQilUij7oN0RrM6Jg7Uc>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 May 2016 23:55:23 -0000

Aside from a bunch of grammatical errors (below), my concern is that
this design ends up relying on the weakest mutually supported hash
function.  If SHA-1 is bad (hint: it is), but we have to support it, I
would prefer an algorithm that matched ALL mutually supported hashes.
That is, if a peer supports SHA-256 it either includes SHA-256 for
every certificate or checks that there is a match for SHA-256 if any
SHA-256 hash is present.

Detailed nits and comments:

s1p2

However,
   RFC 4572 is currently unclear on whether multiple 'fingerprint'
[attributes] can
   be associated

s1p2

OLD
Multiple 'fingerprint'
   attributes are needed when an endpoint wants to provide multiple
   fingerprint, using different hash functions, for a certificate.
MAYBE
Multiple 'fingerprint'
   attributes are needed when an endpoint wants to support updated
hash functions without sacrificing interoperability with existing
implementations.

...However I think that this is not a feature that 4572 implies, so
you should instead remove this and add to p4 (my wording is clumsy,
but I hope the idea is OK):

NEW
This change also requires that multiple 'fingerprint' attribute are
included so that implementations are able to add hashes generated with
updated hash functions alongside those that are needed to interoperate
with existing implementations.


s1p5

OLD
The document also updates the preferred cipher suite to be used [to
SHA-256], and
   removes the requirement to use the same hash function for calculating
   the certificate fingerprint and certificate signature.

s6
<delete the 'p' please>


On 6 May 2016 at 16:57, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Hi,
>
>
>
> I=E2=80=99ve submitted a new version (-01) of draft-ietf-mmusic-4572-upda=
te. It now
> contains updated fingerprint handling procedures, based on the discussion=
s:
> the number of calculated fingerprints for a given cipher suite are
> independent of each other. And, it=E2=80=99s enough that one fingerprint,=
 calculated
> using an algorithm the receiver considers secure enough, matches the used
> certificiate.
>
>
>
> There are currently no open issues in the draft, so I encourage people to
> take a look :)
>
>
>
> Regards,
>
>
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Mon May  9 00:42:36 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10ED12D19B; Mon,  9 May 2016 00:42:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXMcA5YwNQ2x; Mon,  9 May 2016 00:42:32 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EFAD12B067; Mon,  9 May 2016 00:42:31 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-8f-57303f6554e2
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 68.C5.12516.56F30375; Mon,  9 May 2016 09:42:30 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC002.ericsson.se ([153.88.183.24]) with mapi id 14.03.0248.002; Mon, 9 May 2016 09:42:15 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's editorial comments
Thread-Index: AQHRqcZN4jecUrXHa0qFHVVmcwfV3g==
Date: Mon, 9 May 2016 07:42:14 +0000
Message-ID: <D35613FF.8106%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <99353A3B72C9354E918B8F3AF450B125@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsUyM2K7hG6avUG4wa3tAhbXzvxjtDi/cz2T xdTlj1kcmD12zrrL7rFkyU+mAKYoLpuU1JzMstQifbsEroyWO3fZCn7KVFzdeYmlgbFLvIuR k0NCwERi15E9zBC2mMSFe+vZuhi5OIQEjjBKXF67gQXCWcwocWflYcYuRg4ONgELie5/2iAN IgK6EovOPmAHsZkFYiTuHuhnBbGFBTIldu56zgJRkyXR/WQjE4StJ7Fx7QMwm0VARWLxqy6w Gl4BK4nje1vBehmBjvh+ag0TxExxiVtP5jNBHCcgsWTPeahDRSVePv4HVi8KNHPfi/OMEHFF iavTl0P1Gki8PzefGcK2lrg1tYsVwtaWWLbwNTPEXkGJkzOfsExgFJuFZN0sJO2zkLTPQtI+ C0n7AkbWVYyixanFxbnpRsZ6qUWZycXF+Xl6eaklmxiBEXZwy2/dHYyrXzseYhTgYFTi4VV4 rx8uxJpYVlyZe4hRgoNZSYS3xNQgXIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv/0vFcCGB9MSS 1OzU1ILUIpgsEwenVAPjqrpPsx7t+s/M/NBy8wnRufHSa7nCv3XsChC+t+r8go/Oe7ftfH3C R4u17otlrXL7l8ViPzbq58uUM2WGTwpoPRux4jurimTZC3u1WRPuh0YV8J/aqdN8t5/1ulTi o71NTp+kfOR1aifxKG7z87PtEpr63UT9EFfnvZJHSRbFLy0W6nsEf5ytxFKckWioxVxUnAgA 0zeCz6wCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/4sTR-kVDkm_WjWJ6nPBU8Wz6xAI>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's editorial comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 07:42:35 -0000

Hi Martin,

Thanks for your comments! This reply addresses the editorial nits and
comments.

>Detailed nits and comments:
>
>s1p2
>
> However, RFC 4572 is currently unclear on whether multiple 'fingerprint'
> [attributes] can be associated

I=B9ll fix as suggested.


>s1p2
>
> OLD=20
>
> Multiple 'fingerprint' attributes are needed when an endpoint wants to
>provide multiple
> fingerprint, using different hash functions, for a certificate. MAYBE
> Multiple 'fingerprint' attributes are needed when an endpoint wants to
>support updated
> hash functions without sacrificing interoperability with existing
>implementations.
>
> ...However I think that this is not a feature that 4572 implies, so
> you should instead remove this and add to p4 (my wording is clumsy,
> but I hope the idea is OK):
>
> NEW
>
> This change also requires that multiple 'fingerprint' attribute are
> included so that implementations are able to add hashes generated with
> updated hash functions alongside those that are needed to interoperate
> with existing implementations.

Ok.

So, p2 will say:

"RFC 4572 defines the SDP 'fingerprint' attribute, which is used to
   carry a secure hash value associated with a certificate.  However,
   RFC 4572 is currently unclear on whether multiple 'fingerprint'
   attributes can be associated with a single SDP media description ("m=3D
   line") [RFC4566], and the associated semantics.  Multiple
   'fingerprint' attributes are also needed if an endpoint wants to
   provide fingerprints associated with multiple certificates.  For
   example, with RTP-based media, an endpoint might use different
   certificates for RTP and RTCP."


=8Aand p4 will say:

"RFC 4572 mandates that the hash function used to calculate the
   fingerprint is the same hash function used to calculate the
   certificate signature.  That requirement might prevent usage of
   newer, stronger and more collision-safe hash functions for
   calculating certificate fingerprints.  This change also requires that
   multiple 'fingerprint' attributes can be associated with a single
   "m=3D" line, so that implementations are able to provide hashes
   generated with updated hash functions alongside those that are needed
   to interoperate with existing implementations.=B2

=8Abecause I assume you want to keep the text regarding multiple
certificates in p2, while moving the text regarding multiple hashes to p4?



>s1p5
>
> OLD
>
> The document also updates the preferred cipher suite to be used [to
>SHA-256], and
> removes the requirement to use the same hash function for calculating
>the certificate=20
> fingerprint and certificate signature.

I=B9ll fix as suggested.


>s6
><delete the 'p' please>

Done :)


Thanks!

Regards,

Christer


>
>
>On 6 May 2016 at 16:57, Christer Holmberg
><christer.holmberg@ericsson.com> wrote:
>> Hi,
>>
>>
>>
>> I=B9ve submitted a new version (-01) of draft-ietf-mmusic-4572-update. I=
t
>>now
>> contains updated fingerprint handling procedures, based on the
>>discussions:
>> the number of calculated fingerprints for a given cipher suite are
>> independent of each other. And, it=B9s enough that one fingerprint,
>>calculated
>> using an algorithm the receiver considers secure enough, matches the
>>used
>> certificiate.
>>
>>
>>
>> There are currently no open issues in the draft, so I encourage people
>>to
>> take a look :)
>>
>>
>>
>> Regards,
>>
>>
>>
>> Christer
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>


From nobody Mon May  9 01:43:18 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 318E212B036; Mon,  9 May 2016 01:43:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9ZjtGuC01VX; Mon,  9 May 2016 01:43:11 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3816612B023; Mon,  9 May 2016 01:43:11 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id u185so193041013iod.3; Mon, 09 May 2016 01:43:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=2fCh9UkBLB/Qx1l0a1wDgzdue8ZgL/DsqYfVXweJXPQ=; b=DtPCV8/0uXFXwPZerV8/rb4poxU1HT4wRWvo9YBaRRIaVJLKQaaaR7w0ru8ThdUZyp Ik+0ZYg7NafWUmD/lJiVsqfLwGGNwyMPVfQYdY08pwm+E1tEWlO6sjCvW27Pw7S7EdpE dNP7WVoUSLdIZmbwtCUZxLOxm8WuQ1iIbHwd001khAw5NNKrkFY6xHL5Jf0gkgdTWZx/ oyW0Lm01nagDY1bwmqSzFpxcSJFz4GoqtIjLlrPFv3sIvb/FeG2ymEoI5+Mp13bV2+2+ mh7EvB7KvQ25NGugZLf5h/tJD+dau96dQ+OU+7b+pjQF6ZJBGXMo5MCWeG9efq1R167u 5HRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=2fCh9UkBLB/Qx1l0a1wDgzdue8ZgL/DsqYfVXweJXPQ=; b=exD9o5vPyZnMK2hRjmM5Oyqn0qMqt+JHZgbVrOBNRXM2aSbysQ9epp+dc7wA+8wf/x QpE9wigKO7uBiPMdijYjUvUlG/pInhDL0BXQxGJpPlnP/LwBgRNZJwDlnvr96GXe/u1f XofgQQrkA3GcqHmFRS7D/eF/4fTgCw2iJEQD5AxGVrMFyeba8VMCFXgvJBexFdqGnU7W /rPvsgIU2w3dO+E/UMa90vQEW1xC9VL7LQNYYfy5yudQ4dMQD+u5B62sJvgxMoDqNpT0 FmSp2HGV6KJsdftoO0s01+Onft0NsQssV1zzue2B7SYpAB0egsy0uh4y0lSr84ibH7eQ 7brg==
X-Gm-Message-State: AOPr4FX0rdnpXFvgCFg+1cf+/iPVCnzK9e58zJDXznVwt8WhmelwNWXbxRkwrcMEkDBz74yGCoogMh9FtqI19Q==
MIME-Version: 1.0
X-Received: by 10.107.136.76 with SMTP id k73mr37337466iod.100.1462783390651;  Mon, 09 May 2016 01:43:10 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 01:43:10 -0700 (PDT)
In-Reply-To: <D35613FF.8106%christer.holmberg@ericsson.com>
References: <D35613FF.8106%christer.holmberg@ericsson.com>
Date: Mon, 9 May 2016 18:43:10 +1000
Message-ID: <CABkgnnVCQEjCvyb7jZ=ZjYUwb6n1T=n7V98FpwgLu9YXytq36Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Dal383v4L7_7aqBx2swF7H3xVFE>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's editorial comments
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 08:43:16 -0000

On 9 May 2016 at 17:42, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> =C5=A0because I assume you want to keep the text regarding multiple
> certificates in p2, while moving the text regarding multiple hashes to p4=
?

That was my thought.  It keeps thing sane.


From nobody Mon May  9 08:23:21 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2097512D52B; Mon,  9 May 2016 08:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9v4Dtx2HSLT; Mon,  9 May 2016 08:23:18 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BFB312D1F0; Mon,  9 May 2016 08:23:17 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-89-5730ab64d502
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.183.30]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 49.A5.12516.46BA0375; Mon,  9 May 2016 17:23:16 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0248.002; Mon, 9 May 2016 17:23:15 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
Thread-Index: AdGqBkUKuoOsDxVkQqmFJT/p3H5FTg==
Date: Mon, 9 May 2016 15:23:15 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrILMWRmVeSWpSXmKPExsUyM2K7nG7KaoNwg8kXRCyunfnHaHF+53om i6nLH7M4MHvsnHWX3WPJkp9MAUxRXDYpqTmZZalF+nYJXBl/5t9jKfjEUbH4Tz9jA+MVji5G Tg4JAROJ7Y0PWSFsMYkL99azdTFycQgJHGGUuLbmCzuEs5hRYvLdZyxdjBwcbAIWEt3/tEEa RAR0JRadfcAOYjMLxEjcPdDPClIiLJAhsfknF4gpIpAp0THXDKJaT6Jp5wlGEJtFQEXi8OZW FhCbV8BXYv3n/2A2I9AJ30+tYYKYKC5x68l8JojTBCSW7DnPDGGLSrx8/A/qZCWJRbc/M4Gs YhbQlFi/Sx+iVVFiSvdDdojxghInZz5hmcAoMgvJ1FkIHbOQdMxC0rGAkWUVo2hxanFxbrqR sV5qUWZycXF+nl5easkmRmBEHNzyW3cH4+rXjocYBTgYlXh4Fd7rhwuxJpYVV+YeYpTgYFYS 4c1fZhAuxJuSWFmVWpQfX1Sak1p8iFGag0VJnNf/pWK4kEB6YklqdmpqQWoRTJaJg1OqgZGZ r7HeesUa14fPyqfOCzR/tmX3YdlTbotKtqdezT/Tt87zofaMP0XtcfNU907rPV3Ts+VYmv9X 62mG4seTWsRjK86Z3lnf0PSI73x3spjzfMfk8wu9711edfTv4Xk775xUqDR00l8klivT5ha9 67rs0hc5D7o09Jgl4u3OrrBhj1jzZXlMZIMSS3FGoqEWc1FxIgAl9kCZhAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ifeKo6-jwD0oFCiLNY1BHDQeyZE>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 15:23:20 -0000

SGksDQoNCj5Bc2lkZSBmcm9tIGEgYnVuY2ggb2YgZ3JhbW1hdGljYWwgZXJyb3JzIChiZWxvdyks
IG15IGNvbmNlcm4gaXMgdGhhdCB0aGlzIGRlc2lnbiBlbmRzIHVwIHJlbHlpbmcgb24gPnRoZSB3
ZWFrZXN0IG11dHVhbGx5IHN1cHBvcnRlZCBoYXNoIGZ1bmN0aW9uLiAgSWYgU0hBLTEgaXMgYmFk
IChoaW50OiBpdCBpcyksIGJ1dCB3ZSBoYXZlIHRvIHN1cHBvcnQgaXQsIEkgPndvdWxkIHByZWZl
ciBhbiBhbGdvcml0aG0gdGhhdCBtYXRjaGVkIEFMTCBtdXR1YWxseSBzdXBwb3J0ZWQgaGFzaGVz
Lg0KPlRoYXQgaXMsIGlmIGEgcGVlciBzdXBwb3J0cyBTSEEtMjU2IGl0IGVpdGhlciBpbmNsdWRl
cyBTSEEtMjU2IGZvciBldmVyeSBjZXJ0aWZpY2F0ZSBvciBjaGVja3MgdGhhdCB0aGVyZSA+aXMg
YSBtYXRjaCBmb3IgU0hBLTI1NiBpZiBhbnkgU0hBLTI1NiBoYXNoIGlzIHByZXNlbnQuDQoNClNv
LCB3ZSBjYW4ndCBhc3N1bWUgdGhhdCwgaWYgdGhlcmUgaXMgYSBTSEEtMSBoYXNoIGFuZCBhIFNI
QS0yNTYgaGFzaCwgdGhlIHJlY2VpdmVyIHdvdWxkbid0IHVzZSB0byBTSEEtMjU2IGhhcyB0byBj
aGVjayBmb3IgYSBtYXRjaCAoYXNzdW1pbmcgdGhlIHJlY2VpdmVyIHN1cHBvcnRzIFNIQS0yNTYs
IHRoYXQgaXMpPw0KDQpJc24ndCB0aGlzIGEgY2FzZSB3aGVyZSB3ZSBoYXZlIHRvIHRydXN0IHRo
YXQgaW1wbGVtZW50ZXJzIHRvICJ0aGUgcmlnaHQgdGhpbmciPyBBbiBpbXBsZW1lbnRlciBjb3Vs
ZCBjaG9vc2UgdG8gbm90IGNoZWNrIGFueXRoaW5nIC0gbm8gbWF0dGVyIHdoYXQgd2Ugc3BlY2lm
eS4uLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo=


From nobody Mon May  9 08:25:35 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFFFB12B03F; Mon,  9 May 2016 08:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3lWRw_oHYlaH; Mon,  9 May 2016 08:25:28 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7503012D1F0; Mon,  9 May 2016 08:25:27 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-2f-5730abe5dd05
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F5.F5.12516.5EBA0375; Mon,  9 May 2016 17:25:25 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0248.002; Mon, 9 May 2016 17:25:24 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
Thread-Index: AdGqBkUKuoOsDxVkQqmFJT/p3H5FTgAAKleg
Date: Mon, 9 May 2016 15:25:23 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupikeLIzCtJLcpLzFFi42KZGbFdWvfpaoNwgyffzCyunfnHaHF+53om i6nLH7M4MHvsnHWX3WPJkp9MAUxRXDYpqTmZZalF+nYJXBlLH2xiLJjLU7Hp1hG2Bsb/nF2M nBwSAiYSp55/Z4ewxSQu3FvP1sXIxSEkcIRRYvHTz8wQzmJGid4z01m6GDk42AQsJLr/aYM0 iAgkS5x5sZAZJMwsECMxbSEXiCkskCGx+SeYKSKQKdEx1wyi2Eji3rmJbCA2i4CKxP0/T8Fs XgFfieO/D4DZQkB208zFYDangJ9Ec+tCRhCbEeiy76fWMIHYzALiEreezGeCuFhAYsme88wQ tqjEy8f/WCFsJYlFtz9D1etILNj9iQ3C1pZYtvA1M8ReQYmTM5+wTGAUm4Vk7CwkLbOQtMxC 0rKAkWUVo2hxanFxbrqRsV5qUWZycXF+nl5easkmRmAMHdzyW3cH4+rXjocYBTgYlXh4Fd7r hwuxJpYVV+YeYpTgYFYS4c1fZhAuxJuSWFmVWpQfX1Sak1p8iFGag0VJnNf/pWK4kEB6Yklq dmpqQWoRTJaJg1OqgdGkNPfv631TDqpfCXfcdS9kznQnrgWH277/VpPiuFR55MWRHdPOczbU XP7/sSDqdHjRLKVA0YavjwQt3Pa/iJLJd+L65ZwluCdca/1jloQln19pWloa6PB9ev7JZXlk He/mF+cXOzVzf9WpljrYt5bZPXmltIHnC5ZrjilHA9x/L1raf/v6LT4lluKMREMt5qLiRADU kphhnQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/nAHzyeeGl32CH2WF26ItLP4Y0gQ>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 15:25:34 -0000

Spelling error. The first sentence should say:

So, we can't assume that, if there is a SHA-1 hash and a SHA-256 hash, the =
receiver wouldn't use the SHA-256 to check for a match (assuming the receiv=
er supports SHA-256, that is)?

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 09 May 2016 18:23
To: Martin Thomson <martin.thomson@gmail.com>
Cc: mmusic-chairs@ietf.org; mmusic@ietf.org
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 -=
 Martin's technical comment

Hi,

>Aside from a bunch of grammatical errors (below), my concern is that this =
design ends up relying on >the weakest mutually supported hash function.  I=
f SHA-1 is bad (hint: it is), but we have to support it, I >would prefer an=
 algorithm that matched ALL mutually supported hashes.
>That is, if a peer supports SHA-256 it either includes SHA-256 for every c=
ertificate or checks that there >is a match for SHA-256 if any SHA-256 hash=
 is present.

So, we can't assume that, if there is a SHA-1 hash and a SHA-256 hash, the =
receiver wouldn't use to SHA-256 has to check for a match (assuming the rec=
eiver supports SHA-256, that is)?

Isn't this a case where we have to trust that implementers to "the right th=
ing"? An implementer could choose to not check anything - no matter what we=
 specify...

Regards,

Christer

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


From nobody Mon May  9 09:14:07 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2725012D0DE for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 09:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RoI546q6DQeu for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 09:14:05 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7B9D12D093 for <mmusic@ietf.org>; Mon,  9 May 2016 09:14:04 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by comcast with SMTP id znofaHRmNnIc7znopa5T4a; Mon, 09 May 2016 16:14:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1462810443; bh=WQbWA3Snt7RUbnwQUbQLIl9KFmI81cmpUMYJf7MDYlA=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Ve/WhCwUgnXi5oz+ZDSR+SdvN7zEaTDfpKn9DYfZBchy/5lT0h6XA+/2PoFv0RkO/ j+L6KWkZnJRNhjUpLS623pfMO88mYQttgXYr5srqwaWGywhZISmjwGfsROYykLaIYC shcdPC+ggn9oxJSjpssAxwcykEbv7f6dldZspNImcQakRTz6QNdVfJ5GcfBCk8by3k 33Ke68FEHnDHVyMI/kipEWRWyVyOCNZuNS2qEHLD1KKVp9d0zRgGCjtKqdS3IY8Eb/ WQVPPl+XRKno3OJqVubuLqqGBWhJvH1IEkFirXgzUGQzAYUeioTxf1RQIYZVG6KmRl y7jcaGnRylLfQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-20v.sys.comcast.net with comcast id sGE31s0033KdFy101GE3t4; Mon, 09 May 2016 16:14:03 +0000
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu>
Date: Mon, 9 May 2016 12:14:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/iDxdbQ-qwhatVyuyNu3fSLMG5og>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 16:14:06 -0000

On 5/8/16 7:55 PM, Martin Thomson wrote:
> Aside from a bunch of grammatical errors (below), my concern is that
> this design ends up relying on the weakest mutually supported hash
> function.  If SHA-1 is bad (hint: it is), but we have to support it, I
> would prefer an algorithm that matched ALL mutually supported hashes.
> That is, if a peer supports SHA-256 it either includes SHA-256 for
> every certificate or checks that there is a match for SHA-256 if any
> SHA-256 hash is present.

This is complicated by the need to support fingerprints for multiple 
certificates, without any indication of which certificate a given 
fingerprint is intended to match.

IIUC you want it to work so that if there are only SHA-1 fingerprints 
then matching one of them is ok, but if there are any SHA-256 
fingerprints, and the receiver supports those, then there should be 
failure if none of the SHA-256 fingerprints match even if an SHA-1 
fingerprint does match.

I'm not sure how to write a matching rule that works that way, 
especially one that is clear.

What are existing implementations doing? Are there any that support 
multiple certificates?

	Thanks,
	Paul


From nobody Mon May  9 09:23:43 2016
Return-Path: <prvs=99371a2704=jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9850D12D550; Mon,  9 May 2016 09:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.831
X-Spam-Level: 
X-Spam-Status: No, score=-1.831 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, 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 nWmPS9JhcwbV; Mon,  9 May 2016 09:23:32 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3D4012D548; Mon,  9 May 2016 09:23:29 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u49GNK6o032421; Mon, 9 May 2016 12:23:20 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 22tr3p863j-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 09 May 2016 12:23:20 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Mon, 9 May 2016 11:23:19 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
Thread-Index: AdGqBkUKuoOsDxVkQqmFJT/p3H5FTgAAKlegAAyFJIA=
Date: Mon, 9 May 2016 16:23:18 +0000
Message-ID: <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <CFE3FEF9FA493F48810018D8894E37B5@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-05-09_07:2016-05-09,2016-05-09,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1605090237
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/WacvW_W4YfknDH0yZzUyAuk0F2U>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 16:23:42 -0000

DQo+IE9uIE1heSA5LCAyMDE2LCBhdCAxMToyNSBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlz
dGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+IA0KPiBTcGVsbGluZyBlcnJvci4g
VGhlIGZpcnN0IHNlbnRlbmNlIHNob3VsZCBzYXk6DQo+IA0KPiBTbywgd2UgY2FuJ3QgYXNzdW1l
IHRoYXQsIGlmIHRoZXJlIGlzIGEgU0hBLTEgaGFzaCBhbmQgYSBTSEEtMjU2IGhhc2gsIHRoZSBy
ZWNlaXZlciB3b3VsZG4ndCB1c2UgdGhlIFNIQS0yNTYgdG8gY2hlY2sgZm9yIGEgbWF0Y2ggKGFz
c3VtaW5nIHRoZSByZWNlaXZlciBzdXBwb3J0cyBTSEEtMjU2LCB0aGF0IGlzKT8NCg0KVGhlIHBy
b2JsZW0gaXMgdGhhdCB3ZSBjYW7igJl0IGVhc2lseSBkaXN0aW5ndWlzaCBSb21hbuKAmXMgdXNl
IGNhc2UgKHNlcGFyYXRlZCBSVFAvUlRDUCwgd2hlcmUgdGhlIFJUUCBpbXBsZW1lbnRhdGlvbiBz
dXBwb3J0cyBTSEEtMjU2IGJ1dCB0aGUgUlRDUCBpbXBsZW1lbnRhdGlvbiBkb2VzbuKAmXQpIGZy
b20gYSBjYXNlIHdoZXJlIGFuIGF0dGFja2VyIGhhcyBzb21laG93IHN1YnZlcnRlZCBTSEEtMS4g
IEluIGJvdGggY2FzZXMsIHRoZSBwcmVzZW50ZWQgKFJUQ1ApIGNlcnRpZmljYXRlIG1hdGNoZXMg
Zm9yIG9uZSBvZiB0aGUgU0hBLTEgZmluZ2VycHJpbnRzLCBidXQgbm90IGZvciBhbnkgb2YgdGhl
IFNIQS0yNTYgZmluZ2VycHJpbnRzLg0KDQpXZSBjb3VsZCBwb3RlbnRpYWxseSBkZWNsYXJlIFJv
bWFu4oCZcyB1c2UgY2FzZSB0byBiZSBkaXNhbGxvd2VkLCBvZiBjb3Vyc2UuDQoNCj4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogbW11c2ljIFttYWlsdG86bW11c2ljLWJvdW5j
ZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBDaHJpc3RlciBIb2xtYmVyZw0KPiBTZW50OiAwOSBN
YXkgMjAxNiAxODoyMw0KPiBUbzogTWFydGluIFRob21zb24gPG1hcnRpbi50aG9tc29uQGdtYWls
LmNvbT4NCj4gQ2M6IG1tdXNpYy1jaGFpcnNAaWV0Zi5vcmc7IG1tdXNpY0BpZXRmLm9yZw0KPiBT
dWJqZWN0OiBSZTogW01NVVNJQ10gRHJhZnQgbmV3IHZlcnNpb246IGRyYWZ0LWlldGYtbW11c2lj
LTQ1NzItdXBkYXRlLTAxIC0gTWFydGluJ3MgdGVjaG5pY2FsIGNvbW1lbnQNCj4gDQo+IEhpLA0K
PiANCj4+IEFzaWRlIGZyb20gYSBidW5jaCBvZiBncmFtbWF0aWNhbCBlcnJvcnMgKGJlbG93KSwg
bXkgY29uY2VybiBpcyB0aGF0IHRoaXMgZGVzaWduIGVuZHMgdXAgcmVseWluZyBvbiA+dGhlIHdl
YWtlc3QgbXV0dWFsbHkgc3VwcG9ydGVkIGhhc2ggZnVuY3Rpb24uICBJZiBTSEEtMSBpcyBiYWQg
KGhpbnQ6IGl0IGlzKSwgYnV0IHdlIGhhdmUgdG8gc3VwcG9ydCBpdCwgSSA+d291bGQgcHJlZmVy
IGFuIGFsZ29yaXRobSB0aGF0IG1hdGNoZWQgQUxMIG11dHVhbGx5IHN1cHBvcnRlZCBoYXNoZXMu
DQo+PiBUaGF0IGlzLCBpZiBhIHBlZXIgc3VwcG9ydHMgU0hBLTI1NiBpdCBlaXRoZXIgaW5jbHVk
ZXMgU0hBLTI1NiBmb3IgZXZlcnkgY2VydGlmaWNhdGUgb3IgY2hlY2tzIHRoYXQgdGhlcmUgPmlz
IGEgbWF0Y2ggZm9yIFNIQS0yNTYgaWYgYW55IFNIQS0yNTYgaGFzaCBpcyBwcmVzZW50Lg0KPiAN
Cj4gU28sIHdlIGNhbid0IGFzc3VtZSB0aGF0LCBpZiB0aGVyZSBpcyBhIFNIQS0xIGhhc2ggYW5k
IGEgU0hBLTI1NiBoYXNoLCB0aGUgcmVjZWl2ZXIgd291bGRuJ3QgdXNlIHRvIFNIQS0yNTYgaGFz
IHRvIGNoZWNrIGZvciBhIG1hdGNoIChhc3N1bWluZyB0aGUgcmVjZWl2ZXIgc3VwcG9ydHMgU0hB
LTI1NiwgdGhhdCBpcyk/DQo+IA0KPiBJc24ndCB0aGlzIGEgY2FzZSB3aGVyZSB3ZSBoYXZlIHRv
IHRydXN0IHRoYXQgaW1wbGVtZW50ZXJzIHRvICJ0aGUgcmlnaHQgdGhpbmciPyBBbiBpbXBsZW1l
bnRlciBjb3VsZCBjaG9vc2UgdG8gbm90IGNoZWNrIGFueXRoaW5nIC0gbm8gbWF0dGVyIHdoYXQg
d2Ugc3BlY2lmeS4uLg0KPiANCj4gUmVnYXJkcywNCj4gDQo+IENocmlzdGVyDQo+IA0KPiBfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBtbXVzaWMgbWFp
bGluZyBsaXN0DQo+IG1tdXNpY0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL21tdXNpYw0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gbW11c2ljIG1haWxpbmcgbGlzdA0KPiBtbXVzaWNAaWV0Zi5v
cmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCj4gDQoN
Cg==


From nobody Mon May  9 09:29:29 2016
Return-Path: <prvs=99371a2704=jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2ECA12D555; Mon,  9 May 2016 09:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.83
X-Spam-Level: 
X-Spam-Status: No, score=-1.83 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, 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 vgZGEJaS_NYO; Mon,  9 May 2016 09:29:25 -0700 (PDT)
Received: from mx0a-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.202]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67BC612D549; Mon,  9 May 2016 09:29:25 -0700 (PDT)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u49GRgqD018186; Mon, 9 May 2016 12:29:22 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 22eba13fpn-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 09 May 2016 12:29:22 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Mon, 9 May 2016 11:29:21 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgC1bVyA
Date: Mon, 9 May 2016 16:29:21 +0000
Message-ID: <14DD2BED-1A5C-431B-98F4-6C9509CC0F77@vidyo.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: multipart/alternative; boundary="_000_14DD2BED1A5C431B98F46C9509CC0F77vidyocom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-05-09_07:2016-05-09,2016-05-09,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1605090238
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/vNpFcR-Ax8ASL6zIt9LQVdLETMM>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 16:29:27 -0000

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

DQpPbiBNYXkgNiwgMjAxNiwgYXQgMjo1NyBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVy
LmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24u
Y29tPj4gd3JvdGU6DQoNCkhpLA0KDQpJ4oCZdmUgc3VibWl0dGVkIGEgbmV3IHZlcnNpb24gKC0w
MSkgb2YgZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUuIEl0IG5vdyBjb250YWlucyB1cGRh
dGVkIGZpbmdlcnByaW50IGhhbmRsaW5nIHByb2NlZHVyZXMsIGJhc2VkIG9uIHRoZSBkaXNjdXNz
aW9uczogdGhlIG51bWJlciBvZiBjYWxjdWxhdGVkIGZpbmdlcnByaW50cyBmb3IgYSBnaXZlbiBj
aXBoZXIgc3VpdGUgYXJlIGluZGVwZW5kZW50IG9mIGVhY2ggb3RoZXIuIEFuZCwgaXTigJlzIGVu
b3VnaCB0aGF0IG9uZSBmaW5nZXJwcmludCwgY2FsY3VsYXRlZCB1c2luZyBhbiBhbGdvcml0aG0g
dGhlIHJlY2VpdmVyIGNvbnNpZGVycyBzZWN1cmUgZW5vdWdoLCBtYXRjaGVzIHRoZSB1c2VkIGNl
cnRpZmljaWF0ZS4NCg0KVGhlcmUgYXJlIGN1cnJlbnRseSBubyBvcGVuIGlzc3VlcyBpbiB0aGUg
ZHJhZnQsIHNvIEkgZW5jb3VyYWdlIHBlb3BsZSB0byB0YWtlIGEgbG9vayA6KQ0KDQpBbiBlZGl0
b3JpYWwgcXVlc3Rpb24g4oCUIDQ1NzIgaXNu4oCZdCBhIHZlcnkgbG9uZyBkb2N1bWVudCwgc28g
d291bGQgaXQgbWFrZSBtb3JlIHNlbnNlIHRvIHN0cnVjdHVyZSB0aGlzIGFzIGEgNDU3MmJpcyB0
aGFuIGFzIHVwZGF0ZXMgdG8gNDU3Mj8gIEkgdGhpbmsgaXTigJlkIGJlIGNsZWFyZXIgZm9yIGlt
cGxlbWVudG9ycy4gIChPZiBjb3Vyc2UsIGl0IGFsc28gbWVhbnMgdGhhdCBhbGwgb2YgNDU3MuKA
mXMgdGV4dCBnb2VzIHRocm91Z2ggc2VjdXJpdHkgcmV2aWV3IGFnYWluOyB3aGljaCBoYXMgaXRz
IGdvb2Qgc2lkZXMgYW5kIGl0cyBiYWQgc2lkZXMuKQ0K

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGRpdj4N
CjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBNYXkg
NiwgMjAxNiwgYXQgMjo1NyBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgJmx0OzxhIGhyZWY9Im1haWx0
bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20iIGNsYXNzPSIiPmNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbTwvYT4mZ3Q7IHdyb3RlOjwvZGl2Pg0KPGJyIGNsYXNzPSJBcHBsZS1p
bnRlcmNoYW5nZS1uZXdsaW5lIj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2Vj
dGlvbjEiIHN0eWxlPSJwYWdlOiBXb3JkU2VjdGlvbjE7IGZvbnQtZmFtaWx5OiBIZWx2ZXRpY2E7
IGZvbnQtc2l6ZTogMTJweDsgZm9udC1zdHlsZTogbm9ybWFsOyBmb250LXZhcmlhbnQtY2Fwczog
bm9ybWFsOyBmb250LXdlaWdodDogbm9ybWFsOyBsZXR0ZXItc3BhY2luZzogbm9ybWFsOyBvcnBo
YW5zOiBhdXRvOyB0ZXh0LWFsaWduOiBzdGFydDsgdGV4dC1pbmRlbnQ6IDBweDsgdGV4dC10cmFu
c2Zvcm06IG5vbmU7IHdoaXRlLXNwYWNlOiBub3JtYWw7IHdpZG93czogYXV0bzsgd29yZC1zcGFj
aW5nOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDsiPg0KPGRpdiBzdHlsZT0i
bWFyZ2luOiAwY20gMGNtIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBD
YWxpYnJpLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQpIaSw8bzpwIGNsYXNzPSIiPjwvbzpwPjwv
ZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAuMDAwMXB0OyBmb250LXNpemU6IDEx
cHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyIgY2xhc3M9IiI+DQo8bzpwIGNs
YXNzPSIiPiZuYnNwOzwvbzpwPjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luOiAwY20gMGNtIDAu
MDAwMXB0OyBmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlm
OyIgY2xhc3M9IiI+DQpJ4oCZdmUgc3VibWl0dGVkIGEgbmV3IHZlcnNpb24gKC0wMSkgb2YgZHJh
ZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUuIEl0IG5vdyBjb250YWlucyB1cGRhdGVkIGZpbmdl
cnByaW50IGhhbmRsaW5nIHByb2NlZHVyZXMsIGJhc2VkIG9uIHRoZSBkaXNjdXNzaW9uczogdGhl
IG51bWJlciBvZiBjYWxjdWxhdGVkIGZpbmdlcnByaW50cyBmb3IgYSBnaXZlbiBjaXBoZXIgc3Vp
dGUgYXJlIGluZGVwZW5kZW50IG9mIGVhY2ggb3RoZXIuIEFuZCwgaXTigJlzIGVub3VnaA0KIHRo
YXQgb25lIGZpbmdlcnByaW50LCBjYWxjdWxhdGVkIHVzaW5nIGFuIGFsZ29yaXRobSB0aGUgcmVj
ZWl2ZXIgY29uc2lkZXJzIHNlY3VyZSBlbm91Z2gsIG1hdGNoZXMgdGhlIHVzZWQgY2VydGlmaWNp
YXRlLjxvOnAgY2xhc3M9IiI+PC9vOnA+PC9kaXY+DQo8ZGl2IHN0eWxlPSJtYXJnaW46IDBjbSAw
Y20gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMt
c2VyaWY7IiBjbGFzcz0iIj4NCjxvOnAgY2xhc3M9IiI+Jm5ic3A7PC9vOnA+PC9kaXY+DQo8ZGl2
IHN0eWxlPSJtYXJnaW46IDBjbSAwY20gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsgZm9udC1m
YW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IiBjbGFzcz0iIj4NClRoZXJlIGFyZSBjdXJyZW50
bHkgbm8gb3BlbiBpc3N1ZXMgaW4gdGhlIGRyYWZ0LCBzbyBJIGVuY291cmFnZSBwZW9wbGUgdG8g
dGFrZSBhIGxvb2sgOik8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXY+QW4gZWRpdG9yaWFsIHF1ZXN0aW9uIOKAlCA0NTcyIGlz
buKAmXQgYSB2ZXJ5IGxvbmcgZG9jdW1lbnQsIHNvIHdvdWxkIGl0IG1ha2UgbW9yZSBzZW5zZSB0
byBzdHJ1Y3R1cmUgdGhpcyBhcyBhIDQ1NzJiaXMgdGhhbiBhcyB1cGRhdGVzIHRvIDQ1NzI/ICZu
YnNwO0kgdGhpbmsgaXTigJlkIGJlIGNsZWFyZXIgZm9yIGltcGxlbWVudG9ycy4gJm5ic3A7KE9m
IGNvdXJzZSwgaXQgYWxzbyBtZWFucyB0aGF0IGFsbCBvZiA0NTcy4oCZcyB0ZXh0IGdvZXMgdGhy
b3VnaCBzZWN1cml0eQ0KIHJldmlldyBhZ2Fpbjsgd2hpY2ggaGFzIGl0cyBnb29kIHNpZGVzIGFu
ZCBpdHMgYmFkIHNpZGVzLik8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_14DD2BED1A5C431B98F46C9509CC0F77vidyocom_--


From nobody Mon May  9 10:58:12 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0CD12D5BA; Mon,  9 May 2016 10:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5DuyheRnsWRh; Mon,  9 May 2016 10:58:09 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EE5A12D5B9; Mon,  9 May 2016 10:57:39 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-33-5730cf9182d0
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id BA.76.18043.19FC0375; Mon,  9 May 2016 19:57:37 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0248.002; Mon, 9 May 2016 19:57:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
Thread-Index: AdGqBkUKuoOsDxVkQqmFJT/p3H5FTgAAKlegAAyFJIAAB1Uw4A==
Date: Mon, 9 May 2016 17:57:35 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com>
In-Reply-To: <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2J7uO7E8wbhBhfXC1jsX3ye2eLamX+M Fud3rmeymLr8MYsDi8fOWXfZPZYs+cnk0fbsDnsAcxSXTUpqTmZZapG+XQJXxp7Dy5gLXkhV 7Jzt1MA4QaqLkZNDQsBE4tiT2UwQtpjEhXvr2boYuTiEBI4wSjzdc48VwlnMKDFt8WqgDAcH m4CFRPc/bZAGEQENiYvPPrCB2MwCNRJzX5xnASkRFsiQ2PyTC8QUEciU6JhrBlHtJPF8XTNY NYuAisTqsyuYQWxeAV+J5ZvXsMOtXbn3N1gRp4CtxNxTM8CKGIFu+35qDRPEKnGJW0/mQ90s ILFkz3lmCFtU4uXjf6wQtpJE45InrCA3MAtoSqzfpQ/RqigxpfshO8ReQYmTM5+wTGAUm4Vk 6iyEjllIOmYh6VjAyLKKUbQ4tbg4N93ISC+1KDO5uDg/Ty8vtWQTIzCqDm75bbWD8eBzx0OM AhyMSjy8Cu/1w4VYE8uKK3MPMUpwMCuJ8PYfMggX4k1JrKxKLcqPLyrNSS0+xCjNwaIkzuv/ UjFcSCA9sSQ1OzW1ILUIJsvEwSnVwFix1cg9Urn6cHyO9bPA3KKlD+ynF6cFLzmm2LxV8n7k lvtqE88mnbE//jbhxo53R8p8y0WvH4mJ3s5c9M/2ruv+24ker/h8ln508ZNaxLaj/a6CVtPz qf0Gy9vm5gj/Vi3/ElrPtcaFP5MpUOST7N4jh2t3re1sFliSEajq9/eJvODFjwdytiixFGck GmoxFxUnAgDiGH6JpgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/mnQjsBJBohjdDVnczd7_oob3SyA>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 17:58:11 -0000

SGksDQoNCj4+IFNwZWxsaW5nIGVycm9yLiBUaGUgZmlyc3Qgc2VudGVuY2Ugc2hvdWxkIHNheToN
Cj4+IA0KPj4gU28sIHdlIGNhbid0IGFzc3VtZSB0aGF0LCBpZiB0aGVyZSBpcyBhIFNIQS0xIGhh
c2ggYW5kIGEgU0hBLTI1NiBoYXNoLCB0aGUgcmVjZWl2ZXIgd291bGRuJ3QgdXNlIHRoZSBTSEEt
MjU2IHRvIGNoZWNrIGZvciBhIG1hdGNoIChhc3N1bWluZyB0aGUgcmVjZWl2ZXIgc3VwcG9ydHMg
U0hBLTI1NiwgdGhhdCBpcyk/DQo+DQo+VGhlIHByb2JsZW0gaXMgdGhhdCB3ZSBjYW7igJl0IGVh
c2lseSBkaXN0aW5ndWlzaCBSb21hbuKAmXMgdXNlIGNhc2UgKHNlcGFyYXRlZCBSVFAvUlRDUCwg
d2hlcmUgdGhlIFJUUCBpbXBsZW1lbnRhdGlvbiBzdXBwb3J0cyBTSEEtMjU2IGJ1dCB0aGUgUlRD
UCBpbXBsZW1lbnRhdGlvbiBkb2VzbuKAmXQpIGZyb20gYSBjYXNlIHdoZXJlIGFuID5hdHRhY2tl
ciBoYXMgc29tZWhvdyBzdWJ2ZXJ0ZWQgU0hBLTEuICBJbiBib3RoIGNhc2VzLCB0aGUgcHJlc2Vu
dGVkIChSVENQKSBjZXJ0aWZpY2F0ZSBtYXRjaGVzIGZvciBvbmUgb2YgdGhlIFNIQS0xIGZpbmdl
cnByaW50cywgYnV0IG5vdCBmb3IgYW55IG9mIHRoZSBTSEEtMjU2IGZpbmdlcnByaW50cy4NCj4N
Cj5XZSBjb3VsZCBwb3RlbnRpYWxseSBkZWNsYXJlIFJvbWFu4oCZcyB1c2UgY2FzZSB0byBiZSBk
aXNhbGxvd2VkLCBvZiBjb3Vyc2UuDQoNCkVhcmxpZXIgaXQgd2FzIHN1Z2dlc3RlZCB0aGF0IHlv
dSBtdXN0IHByb3ZpZGUgdGhlIHNhbWUgc2V0IG9mIGhhc2hlcyBmb3IgZXZlcnkgY2VydGlmaWNh
dGUuIFRoYXQgbWVhbnMgdGhhdCwgZm9yIGVhY2ggY2VydGlmaWNhdGUsIHRoZXJlIG11c3QgYmUg
b25lIG1hdGNoIGZvciBlYWNoIGhhc2ggYWxnb3JpdGhtLg0KDQpRdWVzdGlvbjogaG93IG1hbnkg
aGFzaGVzIGNhbiB3ZSBleHBlY3QgcGVvcGxlIHRvIHByb3ZpZGUgZm9yIGVhY2ggY2VydGlmaWNh
dGU/IE1vcmUgdGhhbiB0d28/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg0KPiAtLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBtbXVzaWMgW21haWx0bzptbXVzaWMtYm91bmNl
c0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIENocmlzdGVyIEhvbG1iZXJnDQo+IFNlbnQ6IDA5IE1h
eSAyMDE2IDE4OjIzDQo+IFRvOiBNYXJ0aW4gVGhvbXNvbiA8bWFydGluLnRob21zb25AZ21haWwu
Y29tPg0KPiBDYzogbW11c2ljLWNoYWlyc0BpZXRmLm9yZzsgbW11c2ljQGlldGYub3JnDQo+IFN1
YmplY3Q6IFJlOiBbTU1VU0lDXSBEcmFmdCBuZXcgdmVyc2lvbjogZHJhZnQtaWV0Zi1tbXVzaWMt
NDU3Mi11cGRhdGUtMDEgLSBNYXJ0aW4ncyB0ZWNobmljYWwgY29tbWVudA0KPiANCj4gSGksDQo+
IA0KPj4gQXNpZGUgZnJvbSBhIGJ1bmNoIG9mIGdyYW1tYXRpY2FsIGVycm9ycyAoYmVsb3cpLCBt
eSBjb25jZXJuIGlzIHRoYXQgdGhpcyBkZXNpZ24gZW5kcyB1cCByZWx5aW5nIG9uID50aGUgd2Vh
a2VzdCBtdXR1YWxseSBzdXBwb3J0ZWQgaGFzaCBmdW5jdGlvbi4gIElmIFNIQS0xIGlzIGJhZCAo
aGludDogaXQgaXMpLCBidXQgd2UgaGF2ZSB0byBzdXBwb3J0IGl0LCBJID53b3VsZCBwcmVmZXIg
YW4gYWxnb3JpdGhtIHRoYXQgbWF0Y2hlZCBBTEwgbXV0dWFsbHkgc3VwcG9ydGVkIGhhc2hlcy4N
Cj4+IFRoYXQgaXMsIGlmIGEgcGVlciBzdXBwb3J0cyBTSEEtMjU2IGl0IGVpdGhlciBpbmNsdWRl
cyBTSEEtMjU2IGZvciBldmVyeSBjZXJ0aWZpY2F0ZSBvciBjaGVja3MgdGhhdCB0aGVyZSA+aXMg
YSBtYXRjaCBmb3IgU0hBLTI1NiBpZiBhbnkgU0hBLTI1NiBoYXNoIGlzIHByZXNlbnQuDQo+IA0K
PiBTbywgd2UgY2FuJ3QgYXNzdW1lIHRoYXQsIGlmIHRoZXJlIGlzIGEgU0hBLTEgaGFzaCBhbmQg
YSBTSEEtMjU2IGhhc2gsIHRoZSByZWNlaXZlciB3b3VsZG4ndCB1c2UgdG8gU0hBLTI1NiBoYXMg
dG8gY2hlY2sgZm9yIGEgbWF0Y2ggKGFzc3VtaW5nIHRoZSByZWNlaXZlciBzdXBwb3J0cyBTSEEt
MjU2LCB0aGF0IGlzKT8NCj4gDQo+IElzbid0IHRoaXMgYSBjYXNlIHdoZXJlIHdlIGhhdmUgdG8g
dHJ1c3QgdGhhdCBpbXBsZW1lbnRlcnMgdG8gInRoZSByaWdodCB0aGluZyI/IEFuIGltcGxlbWVu
dGVyIGNvdWxkIGNob29zZSB0byBub3QgY2hlY2sgYW55dGhpbmcgLSBubyBtYXR0ZXIgd2hhdCB3
ZSBzcGVjaWZ5Li4uDQo+IA0KPiBSZWdhcmRzLA0KPiANCj4gQ2hyaXN0ZXINCj4gDQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1tdXNpYyBtYWls
aW5nIGxpc3QNCj4gbW11c2ljQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbW11c2ljDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KPiBtbXVzaWMgbWFpbGluZyBsaXN0DQo+IG1tdXNpY0BpZXRmLm9y
Zw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KPiANCg0K


From nobody Mon May  9 12:15:25 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADFC512D5C0 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 12:15:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g_k37Iyblvv7 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 12:15:21 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9197D12D61D for <mmusic@ietf.org>; Mon,  9 May 2016 12:13:41 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id 190so182706990iow.1 for <mmusic@ietf.org>; Mon, 09 May 2016 12:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=2gLTSRpgI13lGH1aNBQ2fc3KnaKajFUIClOV0GUIRns=; b=uRSHkbfvc/DS/iINy+HcbFSJWbWaoJ3ea2oaBpEWa/sq3nmKIiWVQxPSnNzmXy++4o WncWKEOO8NifU9JTW20LsVz9FJ9Mxl779OK2zvSWSl3y46oznj+wQctkzwfCPv1gMtVN Ax/V0cNi8V0neVfrOkIh+MhbZrxN9wsL8jG5h/O33ed+hVEr1GGQsJrUJ+QXXRAAeJyS rLeM2lw5di6T35uf729gUuOKSClYHPtTIj+kgPCfZW+5RbXrezCeBKFy1WCgJn80nn3P uLZNGz5+/ttaVU4VRRt/ANxZnUKO6e+1dNkHlup+xKaNPU70N2fwycco0nkKb9g2AeZf SmcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=2gLTSRpgI13lGH1aNBQ2fc3KnaKajFUIClOV0GUIRns=; b=iQJ2gJMyf17Fqf2i07VGqKN1HyNJzGpgYB4MA7w7OovX/OQwXscIRzAdKNWn3az8AW Jsn+0fJ4eNc+nP1pOIzT0MykcHia/1sX44VP8Sul+m1jQ1RMiAHGFXb5Zbhh2e12jfXR FdJvE3SQRkXcOSROibb7g8N3r0WVTLmoBkar9bgeyIE4TcpiGx5watfigdeaT9BtCFT7 DLHdIAx26N88Fl56Q23zySW1F4x/iCJezANnmcUrhG816LA+cHK1847PB1SRg/EtPs29 DcfWyZvgcP6L3gEjP6FZw+v6oEIXWZWtTOdhblquSN/Di71KP0MG/Ki2vVddl+TeUYvT 9FFg==
X-Gm-Message-State: AOPr4FXFVDfm4xWPDvBmnY4JnJg6stXJun7nfOSP+oUaaQciGBLdjVb6jSFEi3Vi1zroPg==
X-Received: by 10.107.16.195 with SMTP id 64mr30459015ioq.194.1462821220865; Mon, 09 May 2016 12:13:40 -0700 (PDT)
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com. [209.85.213.182]) by smtp.gmail.com with ESMTPSA id ef3sm11989837igb.12.2016.05.09.12.13.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 12:13:40 -0700 (PDT)
Received: by mail-ig0-f182.google.com with SMTP id bi2so113515849igb.0; Mon, 09 May 2016 12:13:40 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.62.13 with SMTP id u13mr12704520igr.42.1462821219882; Mon, 09 May 2016 12:13:39 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 12:13:39 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se>
Date: Mon, 9 May 2016 15:13:39 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com>
Message-ID: <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7bdc07a82e7aba05326d9ba9
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/20UiSBNkZEuFrd99zAqSTWrQp1Y>
Cc: Jonathan Lennox <jonathan@vidyo.com>, mmusic <mmusic@ietf.org>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 19:15:24 -0000

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

On Mon, May 9, 2016 at 1:57 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >> Spelling error. The first sentence should say:
> >>
> >> So, we can't assume that, if there is a SHA-1 hash and a SHA-256 hash,
> the receiver wouldn't use the SHA-256 to check for a match (assuming the
> receiver supports SHA-256, that is)?
> >
> >The problem is that we can=E2=80=99t easily distinguish Roman=E2=80=99s =
use case
> (separated RTP/RTCP, where the RTP implementation supports SHA-256 but th=
e
> RTCP implementation doesn=E2=80=99t) from a case where an >attacker has s=
omehow
> subverted SHA-1.  In both cases, the presented (RTCP) certificate matches
> for one of the SHA-1 fingerprints, but not for any of the SHA-256
> fingerprints.
> >
> >We could potentially declare Roman=E2=80=99s use case to be disallowed, =
of course.
>

This is not just my use case. This also affects Cullen's use case where it
is not known in advance which server will generate the media, so you
provide fingerprints for multiple unrelated servers. Each of those servers
can implement different hashes. Removing these use cases will be
inconvenient (multiple servers will have to be updated at the same time),
but it is workable since all those servers are typically under a single
party control.

Earlier it was suggested that you must provide the same set of hashes for
> every certificate. That means that, for each certificate, there must be o=
ne
> match for each hash algorithm.
>
> Question: how many hashes can we expect people to provide for each
> certificate? More than two?
>

This all depends if all certificates must provide a fingerprint for each
hash algorithms. If this is a requirement, then providing multiple
fingerprints can be used to improve connection security. This means the
more different fingerprints are provided, the more secure is the
connection. Because of this, someone can provide several fingerprints per
certificate to improve security.

If different certificates can provide different hashes, then numbers of
fingerprints per certificate will depend on the number of "legacy" hash
algorithms end point need to support. If end point can communicate with
three different end point versions all supporting different hashes, then it
will need to include three fingerprints per certificate. If you are working
with hardware end points, you need to support a lot of legacy versions.
Normally with software clients such as webrtc, number of legacy versions is
limited, and I do not expect to have more then two hashes per certificate
at any given time.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 1:57 PM, Christer Holmberg <span dir=3D"ltr">&l=
t;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chris=
ter.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"><span class=3D"">&gt;&gt; Spelling error.=
 The first sentence should say:<br>
&gt;&gt;<br>
&gt;&gt; So, we can&#39;t assume that, if there is a SHA-1 hash and a SHA-2=
56 hash, the receiver wouldn&#39;t use the SHA-256 to check for a match (as=
suming the receiver supports SHA-256, that is)?<br>
&gt;<br>
&gt;The problem is that we can=E2=80=99t easily distinguish Roman=E2=80=99s=
 use case (separated RTP/RTCP, where the RTP implementation supports SHA-25=
6 but the RTCP implementation doesn=E2=80=99t) from a case where an &gt;att=
acker has somehow subverted SHA-1.=C2=A0 In both cases, the presented (RTCP=
) certificate matches for one of the SHA-1 fingerprints, but not for any of=
 the SHA-256 fingerprints.<br>
&gt;<br>
&gt;We could potentially declare Roman=E2=80=99s use case to be disallowed,=
 of course.<br></span></blockquote><div><br></div><div>This is not just my =
use case. This also affects Cullen&#39;s use case where it is not known in =
advance which server will generate the media, so you provide fingerprints f=
or multiple unrelated servers. Each of those servers can implement differen=
t hashes. Removing these use cases will be inconvenient (multiple servers w=
ill have to be updated at the same time), but it is workable since all thos=
e servers are typically under a single party control.</div><div><br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pa=
dding-left:1ex">Earlier it was suggested that you must provide the same set=
 of hashes for every certificate. That means that, for each certificate, th=
ere must be one match for each hash algorithm.<br>
<br>
Question: how many hashes can we expect people to provide for each certific=
ate? More than two?<br></blockquote><div><br></div><div>This all depends if=
 all certificates must provide a fingerprint for each hash algorithms. If t=
his is a requirement, then providing multiple fingerprints can be used to i=
mprove connection security. This means the more different fingerprints are =
provided, the more secure is the connection. Because of this, someone can p=
rovide several fingerprints per certificate to improve security.</div><div>=
<br></div><div>If different certificates can provide different hashes, then=
 numbers of fingerprints per certificate will depend on the number of &quot=
;legacy&quot; hash algorithms end point need to support. If end point can c=
ommunicate with three different end point versions all supporting different=
 hashes, then it will need to include three fingerprints per certificate. I=
f you are working with hardware end points, you need to support a lot of le=
gacy versions. Normally with software clients such as webrtc, number of leg=
acy versions is limited, and I do not expect to have more then two hashes p=
er certificate at any given time.</div><div><br></div><div>Regards,</div><d=
iv><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div=
><div>=C2=A0</div></div></div></div>

--047d7bdc07a82e7aba05326d9ba9--


From nobody Mon May  9 12:20:50 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B4812D0E9; Mon,  9 May 2016 12:20:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMROMeJ1tYzE; Mon,  9 May 2016 12:20:47 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C664912D097; Mon,  9 May 2016 12:20:46 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-24-5730e30dbb00
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 87.8A.12926.D03E0375; Mon,  9 May 2016 21:20:45 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0248.002; Mon, 9 May 2016 21:20:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgC1bVyAAASat6A=
Date: Mon, 9 May 2016 19:20:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F992B6@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <14DD2BED-1A5C-431B-98F4-6C9509CC0F77@vidyo.com>
In-Reply-To: <14DD2BED-1A5C-431B-98F4-6C9509CC0F77@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGbFdUZf3sUG4wallfBb7F59ntji/cz2T xdTlj1kcmD2WLPnJ5NH27A57AFMUl01Kak5mWWqRvl0CV8b9R28YCzZxV/x+voqtgbGHu4uR g0NCwERiw/OMLkZOIFNM4sK99WxdjFwcQgJHGCW+rH7HCOEsZpS4un4eK0gDm4CFRPc/bZAG EQENiYvPPrCBhJkFAiWmrdUDCQsLeEpcP/2ZDaLES+LC1AXsELaVxOmPz5hAbBYBFYmTzT3M IDavgK/Ej4ZzzBCrGhglfv9dxwwyk1PAVmJSUzJIDSPQbd9PrQHrZRYQl7j1ZD4TxM0CEkv2 nGeGsEUlXj7+xwphK0k0LnnCCnGapsT6XfoQrYoSU7ofskOsFZQ4OfMJywRGsVlIps5C6JiF pGMWko4FjCyrGEWLU4uTctONjPVSizKTi4vz8/TyUks2MQIj6OCW36o7GC+/cTzEKMDBqMTD q/BeP1yINbGsuDL3EKMEB7OSCO/JewbhQrwpiZVVqUX58UWlOanFhxilOViUxHn9XyqGCwmk J5akZqemFqQWwWSZODilGhgtPfKZTtb9KK+XYjr+66iM3c7jO6zuXXmt32t1t9i8/tsX8TNi B30/GO8Qu1x3d9vlPaf/pTpUtt/kexJps7lPdfn8xpWrVW4p+19x3nFQ/PRvoYRyDz3P+PX3 NuR+usSgeu3XUZ+ze2f4djh0TNnv2mW9/PAn1lMr06RWqZ3XEnuY/e8nf0WOEktxRqKhFnNR cSIA+pi0U5wCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/SyDRsAoKrg9scrWY00RH7zvSJwY>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 19:20:49 -0000

SGksDQrCoA0KPj4gSeKAmXZlIHN1Ym1pdHRlZCBhIG5ldyB2ZXJzaW9uICgtMDEpIG9mIGRyYWZ0
LWlldGYtbW11c2ljLTQ1NzItdXBkYXRlLiBJdCBub3cgY29udGFpbnMgdXBkYXRlZCBmaW5nZXJw
cmludCANCj4+IGhhbmRsaW5nIHByb2NlZHVyZXMsIGJhc2VkIG9uIHRoZSBkaXNjdXNzaW9uczog
dGhlIG51bWJlciBvZiBjYWxjdWxhdGVkIGZpbmdlcnByaW50cyBmb3IgYSBnaXZlbiBjaXBoZXIg
c3VpdGUgDQo+PiBhcmUgaW5kZXBlbmRlbnQgb2YgZWFjaCBvdGhlci4gQW5kLCBpdOKAmXMgZW5v
dWdoIHRoYXQgb25lIGZpbmdlcnByaW50LCBjYWxjdWxhdGVkIHVzaW5nIGFuIGFsZ29yaXRobSB0
aGUgcmVjZWl2ZXIgDQo+PiBjb25zaWRlcnMgc2VjdXJlIGVub3VnaCwgbWF0Y2hlcyB0aGUgdXNl
ZCBjZXJ0aWZpY2F0ZS4NCj4+wqANCj4+IFRoZXJlIGFyZSBjdXJyZW50bHkgbm8gb3BlbiBpc3N1
ZXMgaW4gdGhlIGRyYWZ0LCBzbyBJIGVuY291cmFnZSBwZW9wbGUgdG8gdGFrZSBhIGxvb2sgOikN
Cj4NCj4gQW4gZWRpdG9yaWFsIHF1ZXN0aW9uIOKAlCA0NTcyIGlzbuKAmXQgYSB2ZXJ5IGxvbmcg
ZG9jdW1lbnQsIHNvIHdvdWxkIGl0IG1ha2UgbW9yZSBzZW5zZSB0byBzdHJ1Y3R1cmUgdGhpcyBh
cyBhIA0KPiA0NTcyYmlzIHRoYW4gYXMgdXBkYXRlcyB0byA0NTcyPyDCoEkgdGhpbmsgaXTigJlk
IGJlIGNsZWFyZXIgZm9yIGltcGxlbWVudG9ycy4gwqAoT2YgY291cnNlLCBpdCBhbHNvIG1lYW5z
IHRoYXQgYWxsIA0KPiBvZiA0NTcy4oCZcyB0ZXh0IGdvZXMgdGhyb3VnaCBzZWN1cml0eSByZXZp
ZXcgYWdhaW47IHdoaWNoIGhhcyBpdHMgZ29vZCBzaWRlcyBhbmQgaXRzIGJhZCBzaWRlcy4pDQoN
CkFzc3VtaW5nIHdlIChyZWFkOiB0aGUgTU1VU0lDIFdHKSB3b3VsZG4ndCBtYWtlIGFueSBvdGhl
ciBjaGFuZ2UsIHRoZSBsZW5ndGggb2YgdGhlIGRvY3VtZW50IGlzbid0IHRoYXQgcmVsZXZhbnQu
IA0KDQpCdXQsIGRvIHlvdSB0aGluayBzdWNoIHNlY3VyaXR5IHJldmlldyB3b3VsZCBjYXVzZSBs
b3RzIG9mIHdvcms/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQo=


From nobody Mon May  9 14:42:43 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1666812B02B for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 14:42:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id smY87yK4EthX for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 14:42:41 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 846B312B00A for <mmusic@ietf.org>; Mon,  9 May 2016 14:42:40 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by comcast with SMTP id zswfa7JsdLCmUzswqawI0K; Mon, 09 May 2016 21:42:40 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1462830160; bh=mKnhh8YPZziPiU+BWJunAizXgFwTeykH7wLDdwTkqc4=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=YRPxhtGCU157JnMY9wm6KmZK4LN1W/GLmO+SniqlsJCEFoLRQaOh6n7Qci9b+FYdE Gjhq3foD1EZdaHdtYxHz/7eSJ1qkc7WwneZyB8vDy4K+Q6PolG9wPg/uNNO5b/UrHi 6qIi/eVMNUOwy2bXs25oQ3R8vW3QNFUNRb62JKPiiOC0wpafe5JlC47X3txkosK7Wn jZBI6LCX7D6W2eawfrLjFAlcbAi+JYya25d9UO99Q3QFJvUUSQFD/0YJE9IyQO4wVY 5UoEhbr3/oOnIuF+oqH5ZDDnaRY1Gqk3K/0PYjTHfv2fx0d1oyUCvqWIX+Qii+5SJB WqwaTCwHAOnpg==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-17v.sys.comcast.net with comcast id sMif1s00N3KdFy101Mif4n; Mon, 09 May 2016 21:42:40 +0000
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <f69d19d4-13e2-51ef-feeb-9e7b22bf6777@alum.mit.edu>
Date: Mon, 9 May 2016 17:42:38 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/jmlbp5nfvSlM7PLXVi6p69u-CzQ>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 21:42:43 -0000

On 5/9/16 3:13 PM, Roman Shpount wrote:
> On Mon, May 9, 2016 at 1:57 PM, Christer Holmberg
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> wrote:
>
>     >> Spelling error. The first sentence should say:
>     >>
>     >> So, we can't assume that, if there is a SHA-1 hash and a SHA-256 hash, the receiver wouldn't use the SHA-256 to check for a match (assuming the receiver supports SHA-256, that is)?
>     >
>     >The problem is that we can’t easily distinguish Roman’s use case (separated RTP/RTCP, where the RTP implementation supports SHA-256 but the RTCP implementation doesn’t) from a case where an >attacker has somehow subverted SHA-1.  In both cases, the presented (RTCP) certificate matches for one of the SHA-1 fingerprints, but not for any of the SHA-256 fingerprints.
>     >
>     >We could potentially declare Roman’s use case to be disallowed, of course.
>
>
> This is not just my use case. This also affects Cullen's use case where
> it is not known in advance which server will generate the media, so you
> provide fingerprints for multiple unrelated servers. Each of those
> servers can implement different hashes. Removing these use cases will be
> inconvenient (multiple servers will have to be updated at the same
> time), but it is workable since all those servers are typically under a
> single party control.
>
>     Earlier it was suggested that you must provide the same set of
>     hashes for every certificate. That means that, for each certificate,
>     there must be one match for each hash algorithm.
>
>     Question: how many hashes can we expect people to provide for each
>     certificate? More than two?
>
>
> This all depends if all certificates must provide a fingerprint for each
> hash algorithms. If this is a requirement, then providing multiple
> fingerprints can be used to improve connection security. This means the
> more different fingerprints are provided, the more secure is the
> connection. Because of this, someone can provide several fingerprints
> per certificate to improve security.
>
> If different certificates can provide different hashes, then numbers of
> fingerprints per certificate will depend on the number of "legacy" hash
> algorithms end point need to support. If end point can communicate with
> three different end point versions all supporting different hashes, then
> it will need to include three fingerprints per certificate. If you are
> working with hardware end points, you need to support a lot of legacy
> versions. Normally with software clients such as webrtc, number of
> legacy versions is limited, and I do not expect to have more then two
> hashes per certificate at any given time.

Is providing fingerprints for multiple certificates a use case that is 
currently deployed? Or is it only a potential future use case?

If it is a current use case, how is it working given the lack of 
consensus on how fingerprints are to be interpreted?

If it is only a future use case, then I suggest we devise an extension 
to the fingerprint attribute that allows the association of fingerprints 
with particular certificates, or to be placed in groups that each apply 
to a particular certificate.

	Thanks,
	Paul


From nobody Mon May  9 14:51:19 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C2712B051 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 14:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKDYkcBo7bxy for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 14:51:14 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00BC412D152 for <mmusic@ietf.org>; Mon,  9 May 2016 14:51:13 -0700 (PDT)
Received: by mail-ig0-x22a.google.com with SMTP id m9so103497116ige.1 for <mmusic@ietf.org>; Mon, 09 May 2016 14:51:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=U8up6es/w5IfqudBCvjpCsf8rakJ6oNZRSDIpDx9J+o=; b=iUVi08WQpMaqt8LF7LA64hgdEYgSSLH8DxjysuMvjU4kacSGOKGwu4t2BqV0cD8cfU kxNd1iAQaPDRM4t8mhpUu4Xp8jStqwp+dw1Vv1wWmvGRoiWTeqXPAwCLiJ330tTh/kqF lfML+kJJrkPbFm2ihRCoIygqhIWjBMbsBgRJEiy9vhOGrQwiXDsDTBLcAmDAdJ/35vC9 S0zd7rzeYHLQMd3t/NTqdfOipN60WzSOZNkBn0XESWVZNvhOkbksFQf6eSJSWWpRgkSd Z+AEj5CY+pSB1u2GYpms8Qo+SEijN9yudky/BQQiU5rwMkbnJ9Shmmx0/LHV/1GB7PIg V+qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=U8up6es/w5IfqudBCvjpCsf8rakJ6oNZRSDIpDx9J+o=; b=m0mjdm4y9ztW9NK5IZ4Ve45bojMlW6mlL11fHr0wxO3HCf9DxIbQzj1oPjEw/vq5Db ke39sHh3BFBM1RJC3/M2F5dmw1YSgGABf7rgHYVvtKvL4cZ78+mt0GIrZNmRMWonHXpv gNkAGEbRyAnfCD7aVPqcN8uREUqdolTj06cFSDDO00NUaYt8Zb9U1nG8rCvKRuwZ4Xux z3gsk5a7nIX9Kj+ppjBS+deKk2V5vt8tHA6zdXh/MO6oPTMy2bmVhfGbGsEyZsjEfnC8 Vs+ppIsuSEct4qQR5WljqU4LL+uf01JCwzAN4FVCX9/vhlOmOGenAEsWhRjrHqAD1pmZ gtyQ==
X-Gm-Message-State: AOPr4FVh1vA1TqRwFafxwFTm1VA0LG/2c8ZIAGMFdDh+cb1RSaow3LvhbOGDtj95/D2hiQ==
X-Received: by 10.50.250.165 with SMTP id zd5mr13744757igc.85.1462830673271; Mon, 09 May 2016 14:51:13 -0700 (PDT)
Received: from mail-io0-f169.google.com (mail-io0-f169.google.com. [209.85.223.169]) by smtp.gmail.com with ESMTPSA id b9sm12336987igv.6.2016.05.09.14.51.12 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 14:51:12 -0700 (PDT)
Received: by mail-io0-f169.google.com with SMTP id u185so216193033iod.3 for <mmusic@ietf.org>; Mon, 09 May 2016 14:51:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.160.76 with SMTP id j73mr39055929ioe.66.1462830672355; Mon, 09 May 2016 14:51:12 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 14:51:12 -0700 (PDT)
In-Reply-To: <f69d19d4-13e2-51ef-feeb-9e7b22bf6777@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com> <f69d19d4-13e2-51ef-feeb-9e7b22bf6777@alum.mit.edu>
Date: Mon, 9 May 2016 17:51:12 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsHp-bXAyNqBmEtpQrYVdGpg9cxv=fXU=+=BSrobGeGxg@mail.gmail.com>
Message-ID: <CAD5OKxsHp-bXAyNqBmEtpQrYVdGpg9cxv=fXU=+=BSrobGeGxg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=001a114027b897b2f505326fce0b
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/fSQkPrvU1op2bsBb_kpJ5_OKmeo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 21:51:16 -0000

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

On Mon, May 9, 2016 at 5:42 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> Is providing fingerprints for multiple certificates a use case that is
> currently deployed? Or is it only a potential future use case?
>

This is currently supported. I will do a small survey of the open source
DTLS-SRTP implementations and will report what they do exactly. I am fairly
sure they accept the media if any fingerprint matches.


If it is a current use case, how is it working given the lack of consensus
> on how fingerprints are to be interpreted?
>
> If it is only a future use case, then I suggest we devise an extension to
> the fingerprint attribute that allows the association of fingerprints with
> particular certificates, or to be placed in groups that each apply to a
> particular certificate.
>

I am not sure there is a reason to complicate things even for the future
use case. At least no use case why more then one fingerprint match is
needed was ever provided.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 5:42 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.e=
du</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wid=
th:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-l=
eft:1ex">Is providing fingerprints for multiple certificates a use case tha=
t is currently deployed? Or is it only a potential future use case?<br></bl=
ockquote><div><br></div><div>This is currently supported. I will do a small=
 survey of the open source DTLS-SRTP implementations and will report what t=
hey do exactly. I am fairly sure they accept the media if any fingerprint m=
atches.</div><div><br></div><div><br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style=
:solid;border-left-color:rgb(204,204,204);padding-left:1ex">If it is a curr=
ent use case, how is it working given the lack of consensus on how fingerpr=
ints are to be interpreted?<br>
<br>
If it is only a future use case, then I suggest we devise an extension to t=
he fingerprint attribute that allows the association of fingerprints with p=
articular certificates, or to be placed in groups that each apply to a part=
icular certificate.<br></blockquote><div><br></div><div>I am not sure there=
 is a reason to complicate things even for the future use case. At least no=
 use case why more then one fingerprint match is needed was ever provided.<=
/div><div><div class=3D"gmail_signature">_____________<br>Roman Shpount</di=
v></div><div>=C2=A0</div></div></div></div>

--001a114027b897b2f505326fce0b--


From nobody Mon May  9 16:53:02 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8388512B041 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 16:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1fBZRfAyiU7w for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 16:52:58 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFBD41200A0 for <mmusic@ietf.org>; Mon,  9 May 2016 16:52:58 -0700 (PDT)
Received: by mail-ig0-x22b.google.com with SMTP id u10so119091875igr.1 for <mmusic@ietf.org>; Mon, 09 May 2016 16:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=6YF5JOQYWIu6/ZqKIk0+D0AGwtv5ous7hMcZgs+NNzE=; b=IXLGZjvHb3apQ8LTC7EiYX3q4xsfqtXWjd5y6aYTcy93MbnyezXlwtqhMg4ThAz/Bf PeBZNTxYPqSeKUx7DPF7cTOh46l42rkP1txb7dSeJYU9y8gImekphcolX/avRkEPVJJH DOiAajqr5vdkktWs/0CklwyyUMVA0ZO+W+qr3moj6bNU3+hW+mOc/KqCilyk4zfho3MB 5cg6sHlKEFjl7THK65vOVNGBxcUx7HkTtGAFpBzTf3i36+HjLPezQtGcHOmTdZpVsdLk zgzeM9xUaFAZa71WDLZEbO0lYSjDd2i5sBtD4y8hsKV/n9BCOMP9RwFhgZiW/U0Rz4Aw DfZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=6YF5JOQYWIu6/ZqKIk0+D0AGwtv5ous7hMcZgs+NNzE=; b=JPTxnblr3XbAw2DFsJbWvoLKgIZRzP4N1RQzFlUnOYH738V73cc59dHbjOXm8ywY6E D1aJ0mahZdVE0ho0bbpcKqex08bl8GOqg+020/wUd1QzaxfiFm9Bf28gWa0IqN1hZlCT K22YVgPn2wDTZewFFWQFg71M897irHLNAiIk4I2UcsKf4XbCrwCTB4m3fPFUfM7jCOse akn6xVDMkoYCDMkkZqmGiuEcYJQAcTPrvBg6AzpOxak8D9DhwZC2Jhkj2rdU0spPnSP5 O9G4IMJ3wsCom5gSj3dY0Mx7fHpEbEZq+6l8UsH2MXpulC6xnXOR2c9702zNm6oGx/Tg OcjA==
X-Gm-Message-State: AOPr4FUOtz0llJTg3WFAAn3JJKf+YVYy6fCCJwL3RrMUe3NN3Rp5Jn80GieToY1RtM+xHsYVLcPAtnDiBLCecw==
MIME-Version: 1.0
X-Received: by 10.50.59.211 with SMTP id b19mr14414912igr.58.1462837977831; Mon, 09 May 2016 16:52:57 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 16:52:57 -0700 (PDT)
In-Reply-To: <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu>
Date: Tue, 10 May 2016 09:52:57 +1000
Message-ID: <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/lHJhxEWQIIEqIzTDUasvTR_p08Q>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 23:53:00 -0000

On 10 May 2016 at 02:14, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> IIUC you want it to work so that if there are only SHA-1 fingerprints then
> matching one of them is ok, but if there are any SHA-256 fingerprints, and
> the receiver supports those, then there should be failure if none of the
> SHA-256 fingerprints match even if an SHA-1 fingerprint does match.
>
> I'm not sure how to write a matching rule that works that way, especially
> one that is clear.

How about this:

anyMatched := false
for (hashName : supportedHashes) {
  found := false
  match := false
  for (fingerprint : fingerprintAttributes) {
    if (fingerprint.hashName == hashName) {
      found = true
      match = fingerprint.value == hash(hashName, certificate)
    }
  }
  if (match) {
    anyMatched = true
  } else if (found) {
    throw 'no matches for ' + hashName
  }
}
if (!anyMatched) {
  throw 'no matches at all'
}

Or you can go with the more succinct version:

For every hash function that is both supported AND present, check that
there is at least one matching value.  If there are no matching
values, abort.

> What are existing implementations doing? Are there any that support
> multiple certificates?

Firefox has done for a while (though it didn't for even longer due to
a bug).  I'm sure that's not much help though :)


From nobody Mon May  9 16:59:57 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B89A412B041; Mon,  9 May 2016 16:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tno0OEVqOy2g; Mon,  9 May 2016 16:59:55 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEBED1200A0; Mon,  9 May 2016 16:59:54 -0700 (PDT)
Received: by mail-ig0-x233.google.com with SMTP id bi2so119262550igb.0; Mon, 09 May 2016 16:59:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=XlvBHuCB/UkbQuM/X/3lYLpBHvhubJ+mYdA+xWcARug=; b=FpBW6oT5QTcH04+MoUEEX4cV4APXLLDwOauwAGJevys/AJOmH7/mZT5Ek1ZbLtjhSZ TPEJglry/lpQ6rgU2IWP+6DVuloPI/zex6jAf/7fxcI+MAt0VduWV/XAWNYt7dMPd1U1 4N5WcQ0cO/f7ejLpVuTMubeWA/92vFEbXkUePCEu63X0RA8RFB3KMtT5X3Z1RkG/Q5Dz pYeaHcyf1ECADowG2O9NTwm2RTSIQ+aUn9Zz6XlEXoBu1hoMh8q1CO4nlkrehSrVaqb/ R1CbLSRqBsZ9bar0oZ+JrXcCLpA62FMpigtlpWB86f22F257VrcuykGLEFDp0rTjZI2J FQUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=XlvBHuCB/UkbQuM/X/3lYLpBHvhubJ+mYdA+xWcARug=; b=Sed0xsGEbYECPws+nu1xzxDyBuG9vPSxh+060DoiUjQihwVI3n/bXMiiyRAFbHKCpB n/JGe8mLx2Njux3sVjsRC+s9ujwtgD9RQYhBXfTbCd42wYVNzVswGkbEo1mwBh8CmSDM 9LcImr5cJhgBw4uBOSnE+m/3KgdQC2rvBuNjd2dJVXS6UH4Z+BmePP0aBsHBN6xeS10g I2NzIoXgW/cyZsvBuO3bWcnH+mFWthwMw2vfAzEeNYp3e+FoZCEtcrKQ1g1HLZtEpU/q jkNgsg062uNmCgn8puMwQYu6AmgtsYebpwUl50poX0m7vqAvCF75Zx8u8A537R8BVWCC cKVQ==
X-Gm-Message-State: AOPr4FXC1h8+W3AM3PybjYN0JhMMnzpDZCwbayyXX1l5/l62rlwVSJ4d2X7moC6rfOSwN9VcYvnZkXawq8jiig==
MIME-Version: 1.0
X-Received: by 10.50.59.211 with SMTP id b19mr14433395igr.58.1462838394209; Mon, 09 May 2016 16:59:54 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 16:59:54 -0700 (PDT)
In-Reply-To: <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com>
Date: Tue, 10 May 2016 09:59:54 +1000
Message-ID: <CABkgnnXutVVzTJ-FQcPD7iMZ5NQkLgFr4Aite_rKWVwKvV01=A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/JDE0GkeXfPCH00JiDKc9QWJHAK0>
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2016 23:59:56 -0000

On 10 May 2016 at 05:13, Roman Shpount <roman@telurix.com> wrote:
> This is not just my use case. This also affects Cullen's use case where it
> is not known in advance which server will generate the media, so you provide
> fingerprints for multiple unrelated servers. Each of those servers can
> implement different hashes. Removing these use cases will be inconvenient
> (multiple servers will have to be updated at the same time), but it is
> workable since all those servers are typically under a single party control.


But this is easy, isn't it?  You know the certificate for each of
those servers and you either support SHA-foo or not.  That those
servers can only validate MD5 (and will be vulnerable) doesn't matter
as much as the fact that you aren't making any material impact on
security.


From nobody Mon May  9 17:16:08 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A3E12D561 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKU6HPw-S9_b for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:16:05 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0A9912B05D for <mmusic@ietf.org>; Mon,  9 May 2016 17:16:05 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id f89so188698971ioi.0 for <mmusic@ietf.org>; Mon, 09 May 2016 17:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=4EMH/2EPJ8zH6Fps3DBo1eSBx2bwlddqJZkJyAKEPXk=; b=eDtMMagef6/VkwXEvZ+xItlh5nGPw/aEEAJwnPSYN0o1uW+6GCTabL+FfR2nR2MP4R C2sv6AfP2iXELb3oItukk4TGARO1h6KtMn6wCuEzgPCElLBacXQ4RLNR3/IZrI23IB8j rmpmNa3xDmakrBtq+6L96dHuW+1FQ+GkD9aMGAl+tq+u0vNaUlgKe0iKbYrm0sSjDpKV VYaqIhQ6Exu0yUAHxLb90Jn2rkx+iW+eSR8bpQVfXPrEhZjUnqF4NfzzX4gNSUlB0DBc aVeteIXT27IfrCvqvd68OG65V4Rc49hO8kIDYmMDr3HRSLEhAOtw5L8YN3A47jh7t9QE qavg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=4EMH/2EPJ8zH6Fps3DBo1eSBx2bwlddqJZkJyAKEPXk=; b=GhldMfvI7dWyC01j5D2s+9xSmo4lmMxYpH8KaRKYGZPZuMz3KBJ5PctGKKMd0fw4U2 Rv9UzcsocaxkzFtnOnm/WwuxLcaIc+03HGtPHoTeQeJUXINCthelIt+FVRWFt1dS34Em Ukm6273e8wbZrXLVwamwbzqxVOguta4LoxPYcqT3cvxCry8qrorOlNoCkizFyLJ1BOwu w+0xZ9gqa1h3UWwlcN05y843Wlj53860bgMq12tywY+Ip+/Xg2mrtHUHE2ChiKE0JYLA mMRvKjDLV3/QxD1vhQj6FjP97d7OAx4IFCORvRhzTJfqVt7VuDLTfqZUg59/yT6PLVpU qEQQ==
X-Gm-Message-State: AOPr4FVTDz5yniL5YSKqga41bH9DYUNHtXDVZkiXBzPN6q7MGtoI2vEnAwAD7UV6OibowA==
X-Received: by 10.107.11.18 with SMTP id v18mr43611394ioi.184.1462839365038; Mon, 09 May 2016 17:16:05 -0700 (PDT)
Received: from mail-ig0-f174.google.com (mail-ig0-f174.google.com. [209.85.213.174]) by smtp.gmail.com with ESMTPSA id de3sm12562193igb.13.2016.05.09.17.16.04 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 17:16:04 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id m9so105642182ige.1 for <mmusic@ietf.org>; Mon, 09 May 2016 17:16:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.119.2 with SMTP id kq2mr14315811igb.95.1462839364009; Mon, 09 May 2016 17:16:04 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 17:16:03 -0700 (PDT)
In-Reply-To: <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com>
Date: Mon, 9 May 2016 20:16:03 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com>
Message-ID: <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=089e011829a6a7de81053271d4f3
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/a6PZB5JzGUMB80KagCcy-S85arY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 00:16:07 -0000

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

On Mon, May 9, 2016 at 7:52 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> > What are existing implementations doing? Are there any that support
> > multiple certificates?
>
> Firefox has done for a while (though it didn't for even longer due to
> a bug).  I'm sure that's not much help though :)
>
>
Does current Firefox implementation matches any one fingerprint or one
fingerprint per each hash algorithm?

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 7:52 PM, Martin Thomson <span dir=3D"ltr">&lt;<=
a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson=
@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><span class=3D"">&gt; What are existing implementations do=
ing? Are there any that support<br>
&gt; multiple certificates?<br>
<br>
</span>Firefox has done for a while (though it didn&#39;t for even longer d=
ue to<br>
a bug).=C2=A0 I&#39;m sure that&#39;s not much help though :)<br>
<div class=3D""><div class=3D"h5"><br></div></div></blockquote><div><br></d=
iv><div>Does current Firefox implementation matches any one fingerprint or =
one fingerprint per each hash algorithm?</div><div><br></div><div>Regards,<=
/div><div><div class=3D"gmail_signature">_____________<br>Roman Shpount</di=
v></div><div>=C2=A0</div></div></div></div>

--089e011829a6a7de81053271d4f3--


From nobody Mon May  9 17:17:39 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD62A12D185 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aM31TL4WuXGt for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:17:36 -0700 (PDT)
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 0DD4C12B05D for <mmusic@ietf.org>; Mon,  9 May 2016 17:17:36 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id f89so188724257ioi.0 for <mmusic@ietf.org>; Mon, 09 May 2016 17:17:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YaJFLQAzPOZgdD0nP+btNuJt18dOqvNnorWEDETf+QM=; b=gzXTK9P+ShK6m5AMZ2gGNCyXm2UPQs4gCTznkG+I+44QLpN9P2vnLGPzQ/9Lyhtppq KQnAHOTSLyWJh4ktW3x+okABPsfk4V2DdxQ/YUKnrJ5uCOY74cSck4Mtpy8va0gyAYRd fUZttFUC2vV6OFhhT11KDS6SY9pk4KgoySTBiSY5/zyTnPjphwrblbwXev4HvtW2ELP2 /AEyMMS/GxdfVd0A/15k8l2z73kAV0Tjcjkmiu4IqdDajrZNU7gdEbioDjGBCk5K9IuF +Iapw2hMlZc8MGHDuD3WcyxoPVs3PnDKbCYBVKJuXmGZ96DXKMi7pcBP48iC9xqaMV4a 1Z1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YaJFLQAzPOZgdD0nP+btNuJt18dOqvNnorWEDETf+QM=; b=JaVTNEigB2OSF9teyuSRSfgMAE7Hm9x/Jpsl/rK6CoCfDgQVomNaxg4GZRE09udaLE RX/7+wXLdjXo1qfp2pJoiEtuxMBoy/ls76VnJsh8oHqwc9P92HUmrDDRrehNkNCgyZA6 zZENHWywz7UlQMVnw4bNHt/OWXVmEqOOw0tgwVL90l3roWrxfvQ3qIwRvpm+BK61+dTU jiteRwRRbEaH62Q0Ul+Rx76Xq9kX52frdTO1fdt8uGfsRBJ9tYxamG26eDekzvp9RpBx tMg1mO51GuuszUHK93oQuqKVJper60+hLC7BT6Y3cM3dY+aVqa9uAy8dcq+SifvZ+rCv Ls/A==
X-Gm-Message-State: AOPr4FVUsbljoadp+2sgzom7lPbhI+fuyVnHfOYOaFazCnSP8uUoCT9/+I5r/sC+ma3SzepgNc47UYAwHldboA==
MIME-Version: 1.0
X-Received: by 10.107.136.76 with SMTP id k73mr41578723iod.100.1462839455466;  Mon, 09 May 2016 17:17:35 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 17:17:35 -0700 (PDT)
In-Reply-To: <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com>
Date: Tue, 10 May 2016 10:17:35 +1000
Message-ID: <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/32qq_Itc8CyfMJCk9GCauAylYOM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 00:17:38 -0000

On 10 May 2016 at 10:16, Roman Shpount <roman@telurix.com> wrote:
> Does current Firefox implementation matches any one fingerprint or one
> fingerprint per each hash algorithm?

Just one.


From nobody Mon May  9 17:35:48 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7F512D0D8 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:35:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id reL_WKGbJbZK for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:35:44 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6BF312D0BF for <mmusic@ietf.org>; Mon,  9 May 2016 17:35:44 -0700 (PDT)
Received: by mail-ob0-x22e.google.com with SMTP id x1so91579037obt.0 for <mmusic@ietf.org>; Mon, 09 May 2016 17:35:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=5MRfn09ABbIPuVrzxKNNU2PdzNXyoRgQA7OPDTu9kN8=; b=PxcPA6ftum/XVMrDB9DZ6kPZBRZ5ZrA0rsxEJ6wquf2CcVPWKtguCGEJr226L7lbU9 5NAlbsf7yv+VaKYWw8gHLBwyYioeM+oklKl/F2VdR0981GwnUWNaPHm4zkDuuDccpAHR a5LskS/HRsxp4c8J9FjkUSXkVrBHQx3S0NJlBnrEzp01gZyOMPbYYDkpx4ixGv1qtIgb 1iGbDtyUnARRr2HeRiQZxvcflC2KFQGZ8jbe8HYCN1dsVtqRudf7ycg/ApSK5nVCBkqW ddmSkAYthOCc8omSWgiF+IiQGbGh4uJ+15JjpT+moCo+xBUfsqv5Ld+H4ZI9NWttGwt7 36NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=5MRfn09ABbIPuVrzxKNNU2PdzNXyoRgQA7OPDTu9kN8=; b=h3tIVXfRG3vqXQOJZXILMNn+nc9GLNeIon59mEXiexZ/E/JG526EMA8moV2nbDej87 SNpDA5M5wjWdZTktwdHquKSmcWLoukTQ2UeY5ZWh0tVkns9/nVj8Q9HfFrxRbnt3J7WI O7UB38xv4W8mKceuvPELaC34Y3xKYj7/+VKVoIF4oDdojVUz8EqnBcEvuC4o05mZIsa+ TFMaUxjKgs7xtGdNEJaPucn6Kz7kO0z4jLvz7/oYly64ZjLo5lE4XICSRY68IFyi80uo 0DclOuV42ck3+dsQZuocdr2olFK3njQYpEWmJBlghhRddT9mcyQ5R6O150/jynx7Mkja 9jfQ==
X-Gm-Message-State: AOPr4FUjkbTRFoszuZFQoeBS+5gT7HkxDbPx1OVY3V1okIgl8K4zfP3bW31uxwTT4kmTIw==
X-Received: by 10.182.122.41 with SMTP id lp9mr16379175obb.16.1462840543826; Mon, 09 May 2016 17:35:43 -0700 (PDT)
Received: from mail-io0-f173.google.com (mail-io0-f173.google.com. [209.85.223.173]) by smtp.gmail.com with ESMTPSA id u8sm9906009obf.5.2016.05.09.17.35.43 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 17:35:43 -0700 (PDT)
Received: by mail-io0-f173.google.com with SMTP id d62so189305914iof.2 for <mmusic@ietf.org>; Mon, 09 May 2016 17:35:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.160.76 with SMTP id j73mr39554237ioe.66.1462840542894; Mon, 09 May 2016 17:35:42 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 17:35:42 -0700 (PDT)
In-Reply-To: <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com>
Date: Mon, 9 May 2016 20:35:42 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com>
Message-ID: <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a114027b8ec2e110532721a5a
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/UlF7_xTJpYZBdubXgRb71GvIk0I>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 00:35:47 -0000

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

On Mon, May 9, 2016 at 8:17 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 10 May 2016 at 10:16, Roman Shpount <roman@telurix.com> wrote:
> > Does current Firefox implementation matches any one fingerprint or one
> > fingerprint per each hash algorithm?
>
> Just one.
>

This is what I thought, but I was afraid I was missing something. I think
Chrome, Asterisk, and Freeswitch do the same.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 8:17 PM, Martin Thomson <span dir=3D"ltr">&lt;<=
a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson=
@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><span class=3D"">On 10 May 2016 at 10:16, Roman Shpount &l=
t;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br>
&gt; Does current Firefox implementation matches any one fingerprint or one=
<br>
&gt; fingerprint per each hash algorithm?<br>
<br>
</span>Just one.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">This is what I thou=
ght, but I was afraid I was missing something. I think Chrome, Asterisk, an=
d Freeswitch do the same.</div><div class=3D"gmail_extra"><div><div class=
=3D"gmail_signature">_____________<br>Roman Shpount</div></div><div><br></d=
iv></div></div>

--001a114027b8ec2e110532721a5a--


From nobody Mon May  9 17:50:50 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 599B112D56D for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcDM3KHbP16V for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 17:50:46 -0700 (PDT)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2202312D566 for <mmusic@ietf.org>; Mon,  9 May 2016 17:50:46 -0700 (PDT)
Received: by mail-ig0-x233.google.com with SMTP id u10so120050557igr.1 for <mmusic@ietf.org>; Mon, 09 May 2016 17:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=T1q3YB1QXUDvpMHVlnzLYPU4yyEN9olnASHwAiKROFQ=; b=OJw6HsdTrGtkwPgiMA9JenJBGyHxv4H3SEZPAjBDwbYB12HV7rNFoSMrKUgZj+ZrlE PvG2idOpkrEXymEkPweOSpFenSSXKW0y7yYGdBiBdFOUDQnEiRIsKb4KdyWoYw7wj4WG u/ARCwaK0Tn+tp2m7eScMA4I3WxrHXk2lR/ehGbItD8Xbm8e5k6EKGKVLuk/y5nY31hG OtS9EHhOb7lt7pDbqbb8M8jnbHp0BCqobt4vJANSPCR7Owc9adotu2IQegDBdpJ0NyKi 8b3KR9Z+lx/TpegoBh0K+ULHvl3OwdWGEMSqUZ+yRQQ/cDhRpQ/F4JwMUZfKswARsA69 /RsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=T1q3YB1QXUDvpMHVlnzLYPU4yyEN9olnASHwAiKROFQ=; b=dLEgUD+LJxst45CMVNNWf4F+QiwmGcw4AtVsrfv+uAq8p8QQ4e1FGXaaonAMWiC7J6 D2ueGuLkh67UMXuTut2EWx3GqN4A1qMBbmkMdsbIIHPUTSynOqlIf1Z25X01Xgu20WXx 9Ps9qZeB+Rq2m9vl0JMOZV+/bynxh3QJ5C6IyHNg8+vXB+uLtKhUZ+p6v5UOZx3QtSzw GknD9y3HJmXWzQqE6XTiQVXKUZW89MBwDF+W15dhju8P/3j7JX7bngqmja/fIJ4M2Mmi rgpochryJFFKhFagD5TCf2r02Z8qgPSdfWhJB04reYGQsUfzscv6sfI6xRX8LVxNTjBr AivA==
X-Gm-Message-State: AOPr4FUbHfgzpKPQ3VBG7npD53qzL3wHgxHxsA8tmJzO6gGC3o2mIQ+DNwqXq7cSeRAR7A==
X-Received: by 10.50.155.6 with SMTP id vs6mr13873551igb.79.1462841445474; Mon, 09 May 2016 17:50:45 -0700 (PDT)
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com. [209.85.223.174]) by smtp.gmail.com with ESMTPSA id o201sm5127ioe.15.2016.05.09.17.50.44 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 17:50:44 -0700 (PDT)
Received: by mail-io0-f174.google.com with SMTP id f89so179372ioi.0; Mon, 09 May 2016 17:50:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.160.76 with SMTP id j73mr39592739ioe.66.1462841444526; Mon, 09 May 2016 17:50:44 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 17:50:44 -0700 (PDT)
In-Reply-To: <CABkgnnXutVVzTJ-FQcPD7iMZ5NQkLgFr4Aite_rKWVwKvV01=A@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com> <CABkgnnXutVVzTJ-FQcPD7iMZ5NQkLgFr4Aite_rKWVwKvV01=A@mail.gmail.com>
Date: Mon, 9 May 2016 20:50:44 -0400
X-Gmail-Original-Message-ID: <CAD5OKxs0QHSf=7meHOHoDS7MWdkYTXb4HacpH66D9yERMLWC5A@mail.gmail.com>
Message-ID: <CAD5OKxs0QHSf=7meHOHoDS7MWdkYTXb4HacpH66D9yERMLWC5A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a114027b8a9f1d30532725051
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/l4V2VT1IXlw1I3iF8cl8B8LJ6I4>
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 00:50:48 -0000

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

On Mon, May 9, 2016 at 7:59 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 10 May 2016 at 05:13, Roman Shpount <roman@telurix.com> wrote:
> > This is not just my use case. This also affects Cullen's use case where
> it
> > is not known in advance which server will generate the media, so you
> provide
> > fingerprints for multiple unrelated servers. Each of those servers can
> > implement different hashes. Removing these use cases will be inconvenient
> > (multiple servers will have to be updated at the same time), but it is
> > workable since all those servers are typically under a single party
> control.
>
>
> But this is easy, isn't it?  You know the certificate for each of
> those servers and you either support SHA-foo or not.  That those
> servers can only validate MD5 (and will be vulnerable) doesn't matter
> as much as the fact that you aren't making any material impact on
> security.
>

Signaling agent that generates an offer on behalf of several media servers
might not know the actual certificates for each of the servers and only
have access to fingerprints. This of cause can be fixed to force the media
servers to provide the complete certificates, since communication protocol
between media server and signaling agent is something that should be under
control of the same developer. Fixing this might be inconvenient, but
definitely doable.

More important question is, if end point considers SHA-1 secure enough and
will accept offers with SHA-1, why forcing it to check SHA-1 and SHA-256
if SHA-256 is present would make connections more secure? If something
wants to attack such connection and SHA-1 is compromised, attacker can
simply cause the bid down to SHA-1 by removing SHA-256 fingerprint from the
offer.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, May 9, 2016 at 7:59 PM, Martin Thomson <span dir=3D"ltr">&lt;<a href=3D=
"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-le=
ft-color:rgb(204,204,204);padding-left:1ex"><span class=3D"">On 10 May 2016=
 at 05:13, Roman Shpount &lt;<a href=3D"mailto:roman@telurix.com">roman@tel=
urix.com</a>&gt; wrote:<br>
&gt; This is not just my use case. This also affects Cullen&#39;s use case =
where it<br>
&gt; is not known in advance which server will generate the media, so you p=
rovide<br>
&gt; fingerprints for multiple unrelated servers. Each of those servers can=
<br>
&gt; implement different hashes. Removing these use cases will be inconveni=
ent<br>
&gt; (multiple servers will have to be updated at the same time), but it is=
<br>
&gt; workable since all those servers are typically under a single party co=
ntrol.<br>
<br>
<br>
</span>But this is easy, isn&#39;t it?=C2=A0 You know the certificate for e=
ach of<br>
those servers and you either support SHA-foo or not.=C2=A0 That those<br>
servers can only validate MD5 (and will be vulnerable) doesn&#39;t matter<b=
r>
as much as the fact that you aren&#39;t making any material impact on<br>
security.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Signaling agent tha=
t generates an offer on behalf of several media servers might not know the =
actual certificates for each of the servers and only have access to fingerp=
rints. This of cause can be fixed to force the media servers to provide the=
 complete certificates, since communication protocol between media server a=
nd signaling agent is something that should be under control of the same de=
veloper. Fixing this might be inconvenient, but definitely doable.</div><di=
v class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">More important=
 question is, if end point considers SHA-1 secure enough and will accept of=
fers with SHA-1, why forcing it to check SHA-1 and SHA-256 if=C2=A0SHA-256=
=C2=A0is present would make connections more secure? If something wants to =
attack such connection and SHA-1 is compromised, attacker can simply cause =
the bid down to SHA-1 by removing SHA-256 fingerprint from the offer.</div>=
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Regards,</d=
iv><div class=3D"gmail_extra"><div><div class=3D"gmail_signature">_________=
____<br>Roman Shpount</div></div><div><br></div></div></div>

--001a114027b8a9f1d30532725051--


From nobody Mon May  9 18:03:33 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595EB12D0F6 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 18:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oi-w6MCAgdwv for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 18:03:30 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACBA512D0D8 for <mmusic@ietf.org>; Mon,  9 May 2016 18:03:30 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id d62so334095iof.2 for <mmusic@ietf.org>; Mon, 09 May 2016 18:03:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=fen4KBwsSlkckmMWGCWbHZvBb76yzlZRWVgIuj9u9NA=; b=Hdy14tB3kFrl5aq78zgp9sS6XRZ53ft4+odbVsY3S3oM0QsWm6uGrhXni43MiuAO7j dHPmg/yoptb1sh0Fv+87XbCAejZG1Fr3Ijgavcw5rt+orRPonkREjMCkNGyglzHdjAou T/3PTuyl9pYRRvUys87gHncIaKu1KOJQ+A41RR7CS7gR1BZ7VoFj6ee9kgAHZeEqspOK zfprckLgswf7E58Th/jVSfWKKkInUW9Kp01EvM5xUgaqsxZU2eVhbGb0n8BMsAJiNcHn 1Wq3qhz9A9g6ld1cANaDHDWpGxlYR8Yim+RaQqoeDj25fWDsoFEAj21buHHwMQ2zQRQO KH8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=fen4KBwsSlkckmMWGCWbHZvBb76yzlZRWVgIuj9u9NA=; b=GcH5D8C08cc176St/5iSg09bkQurMrMoEvZQvBOTv6+xXVKzCtIQE71kGj52zBjcWe 2SNR3xxv+9ZUylXip4rbcZGjBUBh2T6Y6j5G+1FZe43eTu5PGki065wcanQf71PV3601 a+mc91+IyqtEwLf2ovcNF8HYTVMBBedHnrftMmkHnrV4uBcCSB1+YSoeVcGArKV8wCRF qwaTdjRJWzJe+m8ZsfXZkaMmc3AZb0cM4eeY4vx84Pl1dHp6qG919Net48vjoLynIDtQ 6rpSJ0n24FP97Le4G3dyC6UTWup3g8WnECQSr9tisGiHxEinA5CU0PVXxxhZqoYSguhb QWag==
X-Gm-Message-State: AOPr4FVDD7WUNEtADgEA9aZeID6ORC1NugfxJjSuglztpJLBqmC+hrX/WLEkWej9RQ9HVjTDWkkHCdHXWhpmtg==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr42580604ioe.190.1462842209978;  Mon, 09 May 2016 18:03:29 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 18:03:29 -0700 (PDT)
In-Reply-To: <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com> <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com>
Date: Tue, 10 May 2016 11:03:29 +1000
Message-ID: <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/PBcp0sVeJhFv_DSOCy5iWBGNDv8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 01:03:32 -0000

On 10 May 2016 at 10:35, Roman Shpount <roman@telurix.com> wrote:
> This is what I thought, but I was afraid I was missing something. I think
> Chrome, Asterisk, and Freeswitch do the same.

I think that this is OK.  My point with the multiple hashes thing is
that we have the opportunity to fix this without breaking backward
compatibility.

OLD:

implementations generate exactly one hash per certificate
implementations validate at most one hash

NEW:

implementations generate one hash per hash function per certificate
implementations validate one hash per hash function (if that function
is present)

If you draw up the possible combinations, everything works.


From nobody Mon May  9 18:07:39 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 855FA12D0F6; Mon,  9 May 2016 18:07:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VB0dR82tri0x; Mon,  9 May 2016 18:07:35 -0700 (PDT)
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 D08EC12D0D8; Mon,  9 May 2016 18:07:35 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id u185so443508iod.3; Mon, 09 May 2016 18:07:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=KImdtcYl6oXviFQtxDea92AhmGZnIOIExGO73VMm4hU=; b=P5cRvpshHCTwYCFCH7bA5yORNPhtZDwgAAYrfLlTwEogEUzTdrzf2KXnCaq/e3p1jB g2XUOyYAu/bIT2x2gEImq4tkuP/YkJUhp45cMY2GaTrHfxWIS+gw4PHonXrmkrzTOcC1 HnYWT54p7pO64Btn6OE3Y7hjdYsC71CQIzjeUp2WtbgbMmxbggDyT1xjPsYRWD+JWIEc VrQZGWh4FHgfQsu0a8t2RB7TNUFgCbBxYmmbYEsDsxGy0UuKy6nIfwBzooIP/oaOcrtM oZVZvcSAx53qrk7DWDaaBK+z37WupBPKPdO5Oo1gAtV/1AjZRedxA5oJBHN1q+Y8K1Bx Po8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=KImdtcYl6oXviFQtxDea92AhmGZnIOIExGO73VMm4hU=; b=ZzczAACywDw/L0LJyXdRxv+nFYifQ5GltId3N1/WUPJ6Hje8SbNZ6sapXezIz60Mdu eV409Xw5lVtqIoGJxvn/RvHY5UREhZUa5jboChuKbBffAEm1UNJkqt/zYhP10NPojQ3W wLcEoUepI78rPEgqOcDtd4I1DbFG44pKphjNueZp5l6VhFEBV/mf1Tf8cqdnHtbYz5kU EbM48AjT5jYVXIBPNeIc6PjpbdEXawF+ClpzFgTRstYWhpmkbWECLHFZwKbFlyxKQ8yD WPKVibrSfP/8B3A89dD91ppi1GABv9JWwW62Pv/7SyRr8uoD5j68PQh0sDAtPfqLFmKG c/8Q==
X-Gm-Message-State: AOPr4FWd1MaMwAnqZu5n1nr/xMtyWjNISy+akmWvI0xqBmO3jgdDBomptAutkohCmjaCSqKwnnJlJlEcpcnAxg==
MIME-Version: 1.0
X-Received: by 10.107.136.76 with SMTP id k73mr41729388iod.100.1462842455008;  Mon, 09 May 2016 18:07:35 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 18:07:34 -0700 (PDT)
In-Reply-To: <CAD5OKxs0QHSf=7meHOHoDS7MWdkYTXb4HacpH66D9yERMLWC5A@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com> <CABkgnnXutVVzTJ-FQcPD7iMZ5NQkLgFr4Aite_rKWVwKvV01=A@mail.gmail.com> <CAD5OKxs0QHSf=7meHOHoDS7MWdkYTXb4HacpH66D9yERMLWC5A@mail.gmail.com>
Date: Tue, 10 May 2016 11:07:34 +1000
Message-ID: <CABkgnnW_6uX=cPYfMAYGPA8e6+vxz_1rB9hRjE04kB53dMpQfQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/3zItRL4_RBSeht7pSrIaACEIM6o>
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 01:07:37 -0000

On 10 May 2016 at 10:50, Roman Shpount <roman@telurix.com> wrote:
> More important question is, if end point considers SHA-1 secure enough and
> will accept offers with SHA-1, why forcing it to check SHA-1 and SHA-256 if
> SHA-256 is present would make connections more secure?


That is fine.  That endpoint is vulnerable, but what you are
advocating makes its peer vulnerable too.

In general, the idea when designing security mechanisms is to ensure
that the *strongest* common primitive has to be broken to mount an
attack.  That's really hard, and we've failed at it in the past for
other protocols, but when the solution is so simple in this case, it
seems like a no-brainer to me.

> If something wants to attack such connection and SHA-1 is compromised, attacker can simply cause the bid down to SHA-1 by removing SHA-256 fingerprint from the offer.

The requirement (as is always the case with DTLS-SRTP) is that
signaling has integrity.  After all, if they can change signaling,
they can just insert their own certificate hash.


From nobody Mon May  9 19:24:07 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A77A912D589 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 19:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fcwfp0hSDe7y for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 19:24:03 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D08412D0DB for <mmusic@ietf.org>; Mon,  9 May 2016 19:24:03 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id v145so231953145oie.0 for <mmusic@ietf.org>; Mon, 09 May 2016 19:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=4MY0bV5xGdgjumMlAER0CC+AjNre3c1le0MSIfJwNvM=; b=c9g2kSEJTdasZoI3hc1rGQnjyWUPEmgVpecMOWbZdyyoGajRegyuCGxz/3AN7DnUyD OmMrp5+EyBrZHwkHt3iQqkacLn9Kii1WnmuYARTfJIlYQhrxpQrb48Envin8SRY3/nxx nRDFEe9aQR7wHtBAL3+v1hL1la/wf6fnl5zoh9mS4sZ7t+cMae2nrc7bbirO0mEqfAom aRU06huuiK4UDE33K6ULEKgdjOdngHOOdoxeJAorHFDZ/+9jPDRK/WM5z0QWyLmFucv2 OqgegVZjctReE5OIKN9OQyD78VE8qrwq+8974oNJqxxAL/DS9N9vL0rMotVBB4tstWtV 2PWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=4MY0bV5xGdgjumMlAER0CC+AjNre3c1le0MSIfJwNvM=; b=BM3FFglPnWn+tpW2M/krD+unlVbPXcIHAUrDxOl5DW4fqh37CN5jf5n06qQk4vq/SM NVSZLxECKwvW7zGP+9D3hZhSdsBYsF8nvfhjztRo4vegukIr2i1h9oET1enI+fSE41Xf XAd6zMb+/qpoMUpTySxnELjzDG/0eUeA91yGmJypW7cz9GlCbw51kUFZpzBBM/w9txCl hsRPPD8EMv6ViuQhc6ckSTSISlrpeDVXBeG5uxhhZLyZ1uIA6i/IKwf+I5vtF8qETqPO 2k0sn72OXLQqstXvP+HQoMLEp/jZDY9UHlViUxEaXa40GG9C1j/lABC+0BWk+Q5LgdXR pnRQ==
X-Gm-Message-State: AOPr4FWxopi56jsZeQ2mxkY1LVmpqMTva6Ny5Ng4un+vuj2tCaEF/Os31sMJ8W1q9GyZbA==
X-Received: by 10.202.203.147 with SMTP id b141mr3304353oig.159.1462847042874;  Mon, 09 May 2016 19:24:02 -0700 (PDT)
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com. [209.85.213.169]) by smtp.gmail.com with ESMTPSA id p203sm9862140oif.16.2016.05.09.19.24.02 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 19:24:02 -0700 (PDT)
Received: by mail-ig0-f169.google.com with SMTP id m9so1302085ige.1; Mon, 09 May 2016 19:24:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.150.42 with SMTP id uf10mr14715267igb.95.1462847041849; Mon, 09 May 2016 19:24:01 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 19:24:01 -0700 (PDT)
In-Reply-To: <CABkgnnW_6uX=cPYfMAYGPA8e6+vxz_1rB9hRjE04kB53dMpQfQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com> <CABkgnnXutVVzTJ-FQcPD7iMZ5NQkLgFr4Aite_rKWVwKvV01=A@mail.gmail.com> <CAD5OKxs0QHSf=7meHOHoDS7MWdkYTXb4HacpH66D9yERMLWC5A@mail.gmail.com> <CABkgnnW_6uX=cPYfMAYGPA8e6+vxz_1rB9hRjE04kB53dMpQfQ@mail.gmail.com>
Date: Mon, 9 May 2016 22:24:01 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtmxdx5OLRZh7V8WPAv2sK89c5OSjMHhmhH-YgRNw+H6w@mail.gmail.com>
Message-ID: <CAD5OKxtmxdx5OLRZh7V8WPAv2sK89c5OSjMHhmhH-YgRNw+H6w@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134cff24a6a170532739ed9
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/XLuYBrFHi7vCDUaccHxmxeVJv8k>
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 02:24:06 -0000

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

On Mon, May 9, 2016 at 9:07 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 10 May 2016 at 10:50, Roman Shpount <roman@telurix.com> wrote:
> > More important question is, if end point considers SHA-1 secure enough
> and
> > will accept offers with SHA-1, why forcing it to check SHA-1 and SHA-256
> if
> > SHA-256 is present would make connections more secure?
>
>
> That is fine.  That endpoint is vulnerable, but what you are
> advocating makes its peer vulnerable too.
>
>
I think you are missing my point. If end point considers a single
fingerprint with SHA-1 has secure enough for some connections, why would it
not be secure enough for others even if other, more secure hashes, are
present there? A hash algorithm is either secure enough or not secure
enough. If hash is secure enough, why something else must be checked? If it
is not secure enough, why does it have to be checked at all?

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 9:07 PM, Martin Thomson <span dir=3D"ltr">&lt;<=
a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson=
@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><span class=3D"">On 10 May 2016 at 10:50, Roman Shpount &l=
t;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br>
&gt; More important question is, if end point considers SHA-1 secure enough=
 and<br>
&gt; will accept offers with SHA-1, why forcing it to check SHA-1 and SHA-2=
56 if<br>
&gt; SHA-256 is present would make connections more secure?<br>
<br>
<br>
</span>That is fine.=C2=A0 That endpoint is vulnerable, but what you are<br=
>
advocating makes its peer vulnerable too.<br>
<br></blockquote><div><br></div><div>I think you are missing my point. If e=
nd point considers a single fingerprint with SHA-1 has secure enough for so=
me connections, why would it not be secure enough for others even if other,=
 more secure hashes, are present there? A hash algorithm is either secure e=
nough or not secure enough. If hash is secure enough, why something else mu=
st be checked? If it is not secure enough, why does it have to be checked a=
t all?</div><div><br></div><div>Regards,</div><div><div class=3D"gmail_sign=
ature">_____________<br>Roman Shpount</div></div><div>=C2=A0</div></div></d=
iv></div>

--001a1134cff24a6a170532739ed9--


From nobody Mon May  9 19:25:57 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3A3112D0FE for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 19:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rmybnkx_bZB5 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 19:25:54 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E550912D0DB for <mmusic@ietf.org>; Mon,  9 May 2016 19:25:53 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id u185so1946197iod.3 for <mmusic@ietf.org>; Mon, 09 May 2016 19:25:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ogJqzZic/zkgGvGeoe2IDmJsMptYHMrHEbq4jAoLyXU=; b=ULT8ShTWISCxH7JP68idZ4ssybZlk6InkdIE8+lKPlUL1z34Yu5+TnQSq7uThGVW9K s177aLGm1w4PlqUHTIS0x71X4apRjZXHmZmpzdevMO8gL1sEKarbLQnanDzRVD6O2Vpg tbPa72NDo5k3zOOfh0bzff9/40SKmDIYgOZJBLHu6OmQzJjjIvc4GGXkqcu/cx3gniTo jboFWQMz7N5JlPwLDd+RqBVwQwyFpCDiaKIiOyZ3S07jIWyXnYFXNVAwG2SXhRRFMkQF 0UOf1xokjZ3nU4akyy7erHK6Dbv1wJotRHNE4exwTcEitEQjOdD1vte7ALBl2dM89MiY lgSQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ogJqzZic/zkgGvGeoe2IDmJsMptYHMrHEbq4jAoLyXU=; b=Kuakk14jvULfK2WeaULNNIY5IrUSio+hBGbEIygPZgDQ15iWRnWcgRN7rlHp/81Cr0 oQ5KZCq42NAHn6mxkHTDY6ptaKTnlfcPOi42AUC2W6+RqAJy7pNN+a2WtJWs79/jy9/j pep+oSyoLcNv6kyvaZIBTg8w6gk8sYrC+l59XkLdwwG5R2cjX9HqBxa4V3kAUk502ka+ 9pBE4gS7yEe/OMQflH/QjjS2aWwJkPRwZKPwikUEl408PWCLaLuHHQkcvoM+N6dKUTRF VE0tLvIFvNv59t2RYD053+74dDFnAOCNVfvOt1ZMGmE0idy55FwH5QQ0EGQtRwfwN8Kp dtHg==
X-Gm-Message-State: AOPr4FUXwO2ityRlxQ4l4xOJ4eHmA/GAil2pMr5OMLciJA08fOur4zvVJ921HgqrN1vyeQ==
X-Received: by 10.107.133.81 with SMTP id h78mr45659411iod.44.1462847153340; Mon, 09 May 2016 19:25:53 -0700 (PDT)
Received: from mail-io0-f181.google.com (mail-io0-f181.google.com. [209.85.223.181]) by smtp.gmail.com with ESMTPSA id vh5sm158095igb.21.2016.05.09.19.25.52 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 19:25:52 -0700 (PDT)
Received: by mail-io0-f181.google.com with SMTP id f89so1771670ioi.0 for <mmusic@ietf.org>; Mon, 09 May 2016 19:25:52 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.147.7 with SMTP id v7mr40597816iod.3.1462847152556; Mon, 09 May 2016 19:25:52 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 19:25:52 -0700 (PDT)
In-Reply-To: <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com> <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com> <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com>
Date: Mon, 9 May 2016 22:25:52 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt_EbEZS2XLw-mv1C+B6W59qsFwPwsPRty+efvqcVQHbw@mail.gmail.com>
Message-ID: <CAD5OKxt_EbEZS2XLw-mv1C+B6W59qsFwPwsPRty+efvqcVQHbw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c055f68e3a774053273a4e6
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/PBHWIc8KIYJKoEsW_UGw0I04j8o>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 02:25:55 -0000

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

On Mon, May 9, 2016 at 9:03 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 10 May 2016 at 10:35, Roman Shpount <roman@telurix.com> wrote:
> > This is what I thought, but I was afraid I was missing something. I think
> > Chrome, Asterisk, and Freeswitch do the same.
>
> I think that this is OK.  My point with the multiple hashes thing is
> that we have the opportunity to fix this without breaking backward
> compatibility.
>
>
I understand you are trying to fix something but you never explained what
was broken with the old way.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 9:03 PM, Martin Thomson <span dir=3D"ltr">&lt;<=
a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson=
@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><span class=3D"">On 10 May 2016 at 10:35, Roman Shpount &l=
t;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br>
&gt; This is what I thought, but I was afraid I was missing something. I th=
ink<br>
&gt; Chrome, Asterisk, and Freeswitch do the same.<br>
<br>
</span>I think that this is OK.=C2=A0 My point with the multiple hashes thi=
ng is<br>
that we have the opportunity to fix this without breaking backward<br>
compatibility.<br>
<br></blockquote><div>=C2=A0</div><div>I understand you are trying to fix s=
omething but you never explained what was broken with the old way.</div><di=
v><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div>=
<div>=C2=A0</div></div></div></div>

--94eb2c055f68e3a774053273a4e6--


From nobody Mon May  9 19:44:04 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6FCF12D16A; Mon,  9 May 2016 19:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MEJRiwFkq5li; Mon,  9 May 2016 19:44:01 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09CB212B052; Mon,  9 May 2016 19:44:01 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id d62so2004226iof.2; Mon, 09 May 2016 19:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=MYQHsTAAEDLeNVCl+/eovR84KD4Sp1gctJb7oYrKfTY=; b=NzGbDcgpe/dVVQenoFhHkjLteAMbGU+LKVVcJEMOZWsKrPIOVTXtDM6jMDr3Z6opyM dQcuUIPamqSY/FJPCWYc1gAmqZLCHtd3Xq4SFUEcWmCFSQy92DdIUoSzVfikJQ3h1XwA jrUCl6w2xfifBxh0rKqwpZdhYSxlq6GYFcv05kbm36oluRBwFO4yG8QlOctqYSCX0W4n Dnk2oiJZmI2UyUK3W75BP6qzzLFRt/DFftQ/kmTvPD/6Nvl4Pktba+Z+cgxSnIdNAbBg EjBnNAH+A4FPvlVve3UqzGv50OBh2y4RugELwzW+QmD68uKGfGBHicJ8L2SMQ6cetCNg edXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=MYQHsTAAEDLeNVCl+/eovR84KD4Sp1gctJb7oYrKfTY=; b=IRTtx6b+XjqqDoiyMTbDI0ELhawEHwXCzO2LjV1tXVm09ZgNyxHkXFxx6rILv2sBR4 Q0LdWv1eS5ihL8Zc6gI8QFipUqmOJJjoIMETU5hgU1fVx7WWxRaN5ztg/JjgZ5tKJ0x2 LK7axAH/1CPOZ2VNn+tUxec+6zUIoCMeRU+3OvgI/hR0AAMeiQICnr8UtMKy24A4Hk9o k1dwq6QfZdwY1c3dPJlRZZCQDizHyiHWOlkyLJWMHSIGSiZQf6rnc9Zua5NwvgEuZUJD UN5fHCPF3f/mzyGf90oNKxpkJvtyAYh6pl+2MhcD+9WnPXH8puWg45JE/nceNwspVFPC 7PDg==
X-Gm-Message-State: AOPr4FWSjZYgfpUtTeADHP/jQLdZEWMP5uc0NQimWGRkDrgGhW97HlULs+FJpWUKU7zi2B8nLF418xl0SEr1rg==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr42903790ioe.190.1462848240418;  Mon, 09 May 2016 19:44:00 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 19:44:00 -0700 (PDT)
In-Reply-To: <CAD5OKxtmxdx5OLRZh7V8WPAv2sK89c5OSjMHhmhH-YgRNw+H6w@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F98E9F@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37F98ECC@ESESSMB209.ericsson.se> <52EA71BC-0679-4634-A393-83B4B691593C@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37F99114@ESESSMB209.ericsson.se> <CAD5OKxsQ_G7pnzWrbEuS2rwf6tk8hKeWaGoCtY0dHEAJziNpyQ@mail.gmail.com> <CABkgnnXutVVzTJ-FQcPD7iMZ5NQkLgFr4Aite_rKWVwKvV01=A@mail.gmail.com> <CAD5OKxs0QHSf=7meHOHoDS7MWdkYTXb4HacpH66D9yERMLWC5A@mail.gmail.com> <CABkgnnW_6uX=cPYfMAYGPA8e6+vxz_1rB9hRjE04kB53dMpQfQ@mail.gmail.com> <CAD5OKxtmxdx5OLRZh7V8WPAv2sK89c5OSjMHhmhH-YgRNw+H6w@mail.gmail.com>
Date: Tue, 10 May 2016 12:44:00 +1000
Message-ID: <CABkgnnXYZ=kZknBconby+iCJm2_SPJ_t35eX8xPLD7QPkqAe3w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Om6l-tDv0VxkmOzWVlfrqH7adYk>
Cc: Jonathan Lennox <jonathan@vidyo.com>, "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Martin's technical comment
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 02:44:03 -0000

On 10 May 2016 at 12:24, Roman Shpount <roman@telurix.com> wrote:
> I think you are missing my point. If end point considers a single
> fingerprint with SHA-1 has secure enough for some connections, why would it
> not be secure enough for others even if other, more secure hashes, are
> present there? A hash algorithm is either secure enough or not secure
> enough. If hash is secure enough, why something else must be checked? If it
> is not secure enough, why does it have to be checked at all?

Let's be clear, if someone thinks that SHA-1 is all they need to
implement (which is insane based on recent progress in cryptanalysis),
then we aren't making them implement others.

The reason that you want to implement two hash algorithms is so that
you can talk to multiple people: the ones with the good one (SHA-256)
and the one that you tolerate because you have to talk to people with
old software that can't be easily updated (SHA-1).  However, once you
support both, you create the potential for a bid-down from the good
one to the bad one unless you do as I have suggested.

Of course, what would be ideal is that every DTLS-SRTP implementation
would use SHA-256.  Right away.  That seems unlikely.


From nobody Mon May  9 19:44:54 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A510D12D16A for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 19:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Lfgp-Ur39rnY for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 19:44:51 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9842212D5B8 for <mmusic@ietf.org>; Mon,  9 May 2016 19:44:50 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id u185so2288968iod.3 for <mmusic@ietf.org>; Mon, 09 May 2016 19:44:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=OkOea3Uygbrplqfg0YazQ+CgY1O+PUma7AoMuI0sNro=; b=zTknX/pJfgGMWpeesqnMxLA1oUFJ0gP8hxB6pqr/iIfNRQkg1uh0OUz2dUXk95JvqI 871YrZzdklndGFc5bdxRh+bCSgm3R6UylFWSdZh5nky50XrxeJ+09OuogW1N4yrHq3A6 mIbUaCl4C1qMh0DCMKiAn4rashX3UZ0dMWsBo9Zg6tsJHnacnQZY/Y7WKnH1nZ2H08jt yBs7/q1QzaR7fybilBuEIymuXsDsrBtoQxA4DsSxCcOCDp/ogjQqodAhn3v9a8OCDbxd bU2/P10Rv0pq+GG+oW597+ZasUG1y8bBMQLal9Xq6eTZWQKEjoKcuD4YXE/XdMLxn6FF YX6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=OkOea3Uygbrplqfg0YazQ+CgY1O+PUma7AoMuI0sNro=; b=CMprWHOJcGFFytfXkOFb+NU9go98NO8jxpfRuFzzMvHeH3RCx4ZLEA0VSsKyH2SRMq NwgPrmKy1oEU4hXdOKU36slN6yH0r6Kg5rdBSRaIXbj2+RnM4deaNhENgvbzA5pNGwu9 7uD+ZoQYSCjo9wSEanRTjhZdRnK6SksyuU4Mi4+nAZ0EGbajXz3IC5aIOyxXptsE6U3T a4mHOZ6fMTN7TlxFDE8WPh+wu5eUBCPbKGG0u28DnxPCHafHsS0JnsvpPnw4bVR4CBYW eN8cyF0RgkWc6DouNAI3FrA0BFPuBYYExfymUBLGuQuiUVfYpmg7VVXuvAkzEIU6gk9C +eww==
X-Gm-Message-State: AOPr4FUDQ4pBrmrrO6vSA5z4HuVtyvtywTXXDc246AuFIsqtsiZQ2M02RAHWIdUtOgGQB6F0un+wIpfRaZ7K2Q==
MIME-Version: 1.0
X-Received: by 10.36.9.15 with SMTP id 15mr538134itm.68.1462848290036; Mon, 09 May 2016 19:44:50 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 19:44:49 -0700 (PDT)
In-Reply-To: <CAD5OKxt_EbEZS2XLw-mv1C+B6W59qsFwPwsPRty+efvqcVQHbw@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com> <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com> <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com> <CAD5OKxt_EbEZS2XLw-mv1C+B6W59qsFwPwsPRty+efvqcVQHbw@mail.gmail.com>
Date: Tue, 10 May 2016 12:44:49 +1000
Message-ID: <CABkgnnV-LJrLsVo+xmh5nRt9dJOcxxJ6BdEZYFMkMnYmee6RDA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/XGHjQzM9TQIP-7yuenalGJPKI6E>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 02:44:52 -0000

On 10 May 2016 at 12:25, Roman Shpount <roman@telurix.com> wrote:
> I understand you are trying to fix something but you never explained what
> was broken with the old way.

See upthread, where I said "my concern is that this design ends up
relying on the weakest mutually supported hash function".


From nobody Mon May  9 20:24:59 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3EB12D10B for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 20:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8dGITatywBn for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 20:24:56 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8105812B052 for <mmusic@ietf.org>; Mon,  9 May 2016 20:24:56 -0700 (PDT)
Received: by mail-ig0-x229.google.com with SMTP id lr7so177788igb.1 for <mmusic@ietf.org>; Mon, 09 May 2016 20:24:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=SUlBPjDXOPfRpyd/a07ICcap/GHFtyOsV+QFVEUtN/s=; b=WOVd665hd0uFKyA5lxJd1FHclxq/QxSAjyaf+YPHFDQ2Ngy+fCX04rHp/QS+H8BMld eQRAgCGILggkim7EXyIOqWTJ7ZJ0I/aAA0uK5sQd/Z3h4FVFOJEfprxXayJtqecuSILA St7FabENeoGY3aNMXfOij1GZJoerKwlGP76z/mtGM+zRVB1Qz7gtgqjjOIzXtVWQfLd7 Va8BAwjfqsDagaCoIu7RKJap55HG78Bce4P91oRpfH6NhbslwmA/0kAkJCUrHf8ToxHP X7/h5HEVYyjlAowTn/nd5rsWzhZPD6Xz9Ow5oicHlz2yJyNl7C4I+dpQ+SvBlwrGF9CK wc1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=SUlBPjDXOPfRpyd/a07ICcap/GHFtyOsV+QFVEUtN/s=; b=W2iREtR1drybIJW3UUpZMbjAuBuD10mHzuqWc+uhmY2PnEDtwihOxn10lWq8yscFTw pq6zOrHoxSfG5VRpZOrBXPPpSIYY1DEeH9EiVNF4g1tv050XUSWeZWZzyfFlZSvJKnDO G3PkQqk5qvOGx3iS/13IAjkdUvc7IYwGKc0SwmSz6JtHj/gJMJ5AHzfbmnGC7jVCKc59 5kWWPZvoVZ8Rp3yFmwWZ+xVUbFmCMfI+5U0D9tOuZ2YL9oUXYt04N/sE8dXX3BI+CbQz sWR27Ug9GcpuMuGpuKDP98/+kYKGGKSUWBNBqcc5RF3Pkm6RV6bm2rjZmexnKSHL0AC3 hIHA==
X-Gm-Message-State: AOPr4FVHZkDQS7UKmS1Rz+aeghE06B5wS57fX8rOB2YH34a468FqPEwlyafR1/hvk8awGA==
X-Received: by 10.50.20.10 with SMTP id j10mr4205276ige.30.1462850695856; Mon, 09 May 2016 20:24:55 -0700 (PDT)
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com. [209.85.223.175]) by smtp.gmail.com with ESMTPSA id a94sm264119ioj.11.2016.05.09.20.24.54 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 09 May 2016 20:24:55 -0700 (PDT)
Received: by mail-io0-f175.google.com with SMTP id f89so2682050ioi.0 for <mmusic@ietf.org>; Mon, 09 May 2016 20:24:54 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.147.7 with SMTP id v7mr40754319iod.3.1462850694758; Mon, 09 May 2016 20:24:54 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 9 May 2016 20:24:54 -0700 (PDT)
In-Reply-To: <CABkgnnV-LJrLsVo+xmh5nRt9dJOcxxJ6BdEZYFMkMnYmee6RDA@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com> <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com> <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com> <CAD5OKxt_EbEZS2XLw-mv1C+B6W59qsFwPwsPRty+efvqcVQHbw@mail.gmail.com> <CABkgnnV-LJrLsVo+xmh5nRt9dJOcxxJ6BdEZYFMkMnYmee6RDA@mail.gmail.com>
Date: Mon, 9 May 2016 23:24:54 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsG9t9Eurdzyv9W2wtRREH6Y+A9m-e1wAjKRxHMUEgvug@mail.gmail.com>
Message-ID: <CAD5OKxsG9t9Eurdzyv9W2wtRREH6Y+A9m-e1wAjKRxHMUEgvug@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c055f68054efb0532747867
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/LaZ9OOMS_sVvuwWou2dTKkCYwZg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 03:24:58 -0000

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

On Mon, May 9, 2016 at 10:44 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 10 May 2016 at 12:25, Roman Shpount <roman@telurix.com> wrote:
> > I understand you are trying to fix something but you never explained what
> > was broken with the old way.
>
> See upthread, where I said "my concern is that this design ends up
> relying on the weakest mutually supported hash function".
>

I read this, but if SHA-1 is bad it should not be used (or trusted). You
make a PSA that your network will no longer accept SHA-1 past certain date
and ignore SHA-1 fingerprints from that date forward. Based on your
suggestion, you would still need to check SHA-1 past the date it was phased
out. So, my question is why SHA-1 + SHA-256 is better then SHA-256? Also,
if I trust SHA-256, why do I need to test SHA-512?

>From my experience it is better to always accept hash if you accept it
sometimes, or never accept it, if you don't.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 9, 2016 at 10:44 PM, Martin Thomson <span dir=3D"ltr">&lt;=
<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomso=
n@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);=
padding-left:1ex"><span class=3D"">On 10 May 2016 at 12:25, Roman Shpount &=
lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br=
>
&gt; I understand you are trying to fix something but you never explained w=
hat<br>
&gt; was broken with the old way.<br>
<br>
</span>See upthread, where I said &quot;my concern is that this design ends=
 up<br>
<div class=3D""><div class=3D"h5">relying on the weakest mutually supported=
 hash function&quot;.<br>
</div></div></blockquote></div><br></div><div class=3D"gmail_extra">I read =
this, but if SHA-1 is bad it should not be used (or trusted). You make a PS=
A that your network will no longer accept SHA-1 past certain date and ignor=
e SHA-1 fingerprints from that date forward. Based on your suggestion, you =
would still need to check SHA-1 past the date it was phased out. So, my que=
stion is why SHA-1 + SHA-256 is better then SHA-256? Also, if I trust SHA-2=
56, why do I need to test SHA-512?</div><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra">From my experience it is better to always acce=
pt hash if you accept it sometimes, or never accept it, if you don&#39;t.=
=C2=A0</div><div class=3D"gmail_extra"><div><div class=3D"gmail_signature">=
_____________<br>Roman Shpount</div></div><div><br></div></div></div>

--94eb2c055f68054efb0532747867--


From nobody Mon May  9 20:28:18 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD2C12D195 for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 20:28:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TqHMO407wxHw for <mmusic@ietfa.amsl.com>; Mon,  9 May 2016 20:28:15 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92F2A12D184 for <mmusic@ietf.org>; Mon,  9 May 2016 20:28:15 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id f89so2731403ioi.0 for <mmusic@ietf.org>; Mon, 09 May 2016 20:28:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=touIIqZZ0zVhb78Hwk+Z9k+N+2hV3yttVAuuGdQ0tqU=; b=0eA9vdTCAC/t8uEwLa0goJBnLCW2AOddTbH3bUXuQNm9Nx3ISW8zOHuFlTNjIa03EE el4JOshTc3lacbuYfFHL9q5bO+L0s2ifWfqMuwDB2zwHYDQ6FoeFiSz3X4kDvEJfaL1C pxY01E0IADNJyGsQdGb7DfqzDd3tMVtonlfWwLbTg0/C28jeWCyvp/uTEqvEhuiyIr0V lNqNqNGJecsKdKwX4RdM0sqIvwhKFST53tg9H+vLHFrjGnX6CiQkIRZf4v0alfemda5u Mi6PIiXOaJrWL0wOgjZmItj4ZvjTmcvORL+s5y5mThxRo9zPLP5vTR1/0ajt18XkJvfn YJSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=touIIqZZ0zVhb78Hwk+Z9k+N+2hV3yttVAuuGdQ0tqU=; b=HA9TOFEF5Qj6Vs+blR/06vVkp6e6NrPX/HZ1cjhHJMVC6b1TPr11Rsp+fjcUfDRMha JhsSTXPJ0a5ZZpZ+1M8MXJIJL0VSWk51eTP4qbSGDgCtT9VSpsmxdIymw1CK88YhyomF RhHtQ6KSD+ZT5QG2xIoqe1eaqBnnoIj6Y40yE0sakd0cooVhjvAekUfk4j0ZvsSDAgfK jkwJoosgaTXyqEqoi7qLoQ/f3vbTYOXYb6TmrhQLLrmx/UrkLIBDkOGmLeOmsOibkzW8 aKNvj6c228OkbsV2GmE75QNsM05s9SnF8sawo3fiWCkik9GrPGT8RzCb7taYQ7ApWIzt 5WnA==
X-Gm-Message-State: AOPr4FWnqM9LiLCmYmTksgTP92Jz6bBtIhWxKqhVpQlehtnbzBETAT5lk2kPDvk7bVKCLzBrWefrfOGeaktIdA==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr43033991ioe.190.1462850895002;  Mon, 09 May 2016 20:28:15 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Mon, 9 May 2016 20:28:14 -0700 (PDT)
In-Reply-To: <CAD5OKxsG9t9Eurdzyv9W2wtRREH6Y+A9m-e1wAjKRxHMUEgvug@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com> <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com> <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com> <CAD5OKxt_EbEZS2XLw-mv1C+B6W59qsFwPwsPRty+efvqcVQHbw@mail.gmail.com> <CABkgnnV-LJrLsVo+xmh5nRt9dJOcxxJ6BdEZYFMkMnYmee6RDA@mail.gmail.com> <CAD5OKxsG9t9Eurdzyv9W2wtRREH6Y+A9m-e1wAjKRxHMUEgvug@mail.gmail.com>
Date: Tue, 10 May 2016 13:28:14 +1000
Message-ID: <CABkgnnVH2MxarH2y1gk6r=NNeKscyut+LA4v2B1fdkYGouzcSQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/i9IvGsMymCDNMCqg-GpaqH3ckIo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 03:28:17 -0000

On 10 May 2016 at 13:24, Roman Shpount <roman@telurix.com> wrote:
> I read this, but if SHA-1 is bad it should not be used (or trusted). You
> make a PSA that your network will no longer accept SHA-1 past certain date
> and ignore SHA-1 fingerprints from that date forward. Based on your
> suggestion, you would still need to check SHA-1 past the date it was phased
> out. So, my question is why SHA-1 + SHA-256 is better then SHA-256? Also, if
> I trust SHA-256, why do I need to test SHA-512?

Flag days on the Internet don't work.  Unless you have complete
autocratic control over everyone you are talking to.  See how well
that worked for us when we disabled SHA-1 in certificates.  And we
concurrently supported SHA-256 there for ages.


From nobody Tue May 10 00:23:57 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8DD12D188 for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 00:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v4UIbnqkNXbr for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 00:23:55 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCFB812D1BE for <mmusic@ietf.org>; Tue, 10 May 2016 00:23:54 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-e9-57318c8880d6
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 9D.5C.12516.88C81375; Tue, 10 May 2016 09:23:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0248.002; Tue, 10 May 2016 09:23:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAAzoiAAAANtYAAAKH6AAAA+GeAABOinAA=
Date: Tue, 10 May 2016 07:23:52 +0000
Message-ID: <D357670A.826A%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <CAD5OKxvVrEhT_TvjukDjcQuNm=GtQvBQnfhCj-qjw3VaVLLvzA@mail.gmail.com> <CABkgnnU4NW0cOx9TKV=uY4oBP0HGfFmsr9x2Kz2xWRFEMUJ1kQ@mail.gmail.com> <CAD5OKxvj_K5yaRkY8BQZyMjtYvDp93qz_qDGnzq8e2VuHnZNHQ@mail.gmail.com> <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com>
In-Reply-To: <CABkgnnWTyJ5vquKJB52ZqwQ4uVP_Dq6Og-rHjz_NS=va=AwBMA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FE917AA6CCB4C94AA93A34BB2CC54D63@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLIsWRmVeSWpSXmKPExsUyM2K7qG5nj2G4wbWr7BbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsEroxnP46x FPxkrbg6bzJrA+MTli5GTg4JAROJd+/nsUHYYhIX7q0Hsrk4hASOMEqsWnmFFcJZwihxbMlp IIeDg03AQqL7nzZIg4hAkMTDh4/BBjEL+Eq8/zmdHcQWFvCU2PhoHytEjZfEhakL2CHsJIkZ Ew8zgdgsAqoSH3dfZgaxeQWsJJpen2eE2LWWReLhrJNsILs4BQIldp/JA6lhBDru+6k1TBC7 xCVuPZnPBHG0gMSSPeeZIWxRiZeP/4HtFRXQk9j3AmQmSFxJ4seGS1B36kgs2P0JbDyzgLXE 5w3GEGFtiWULX0OdIyhxcuYTlgmMErOQbJuFpHsWQvcsJN2zkHQvYGRdxShanFpcnJtuZKyX WpSZXFycn6eXl1qyiREYqQe3/Nbdwbj6teMhRgEORiUe3gUOhuFCrIllxZW5hxglOJiVRHhd OoBCvCmJlVWpRfnxRaU5qcWHGKU5WJTEef1fKoYLCaQnlqRmp6YWpBbBZJk4OKUaGCXOy9/v nbz4XvWdPd3quy8J1bOI+2hN/8S7nktNdZdut9P5jdwrCiaI+VVuqmssNHL7l5Wp+e7mtjmG K/VT/ySGBJkeiDA//HVj/ZRHag2lc73OtQSV1+/5eGxpS/Ccvw+M5z6yFOFKup4VnDz/55Gb +u4iR96+jTzd/vUjp4XrDc4sgYZQYyWW4oxEQy3mouJEAESl/7jQAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RG5rJ_UNy6JlQl8zTValB3g500M>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 07:23:56 -0000

Hi,

>OLD:
>
>implementations generate exactly one hash per certificate
>implementations validate at most one hash
>
>NEW:
>
>implementations generate one hash per hash function per certificate
>implementations validate one hash per hash function (if that function
>is present)
>
>If you draw up the possible combinations, everything works.

Again, if you provide hashes for multiple certificates, this assumes you
generate the same set of hashes for each certificate.

Assume you generate SHA-1 for cert1 and SHA-1 and SHA-256 for cert2.
During the DTLS handshake, cert1 is chosen. Now, the endpoint will try to
match the SHA-256 hash, and it will fail (as there is no reference to the
cert in the fingerprint).

Regards,

Christer


From nobody Tue May 10 06:32:09 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3400512D09C for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 06:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mSCHwj9rTtjx for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 06:32:07 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB52912B077 for <mmusic@ietf.org>; Tue, 10 May 2016 06:32:06 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by comcast with SMTP id 07ktbYJ9zfr8T07lebsxB1; Tue, 10 May 2016 13:32:06 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1462887126; bh=FKLgXBQfvno9rb6i7G5iD29B1ZcexSzv6G8eeoZe5KQ=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=BKwUtmuYr61rprcOGGOAbO/tk8KfT7aGNdH7urWwZPL0zIaf9Uu7CJb9vvsVkwl2i WT8dFcMUkxDzQ4SaNqliBEpYuqgpURL4RuhRwi7+Nf9o8aMZnqiMQbEpCE1/H3FhJS TUvCagxsY/94a0gQVsoyCnuF8Hzs0fGTv3epVa4j90DAeo++g6sXJ6rIts+Q//Y2Jb VjxM+CUTtNane+9M2LNoW50dn6/B5dS/6wJLns2xlXV3H1cEhkBa9EmIuZlKwgHnC7 2YpoAZVhAc6y3YenVmzKu4r244b+BgrxLXd7KJmzCQ8MJeQ1rgpoftOGWh2hRZWh5k qPzPk2Ddqp8iQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-08v.sys.comcast.net with comcast id sdY51s00D3KdFy101dY5EN; Tue, 10 May 2016 13:32:06 +0000
To: Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu>
Date: Tue, 10 May 2016 09:32:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/GULFEz_gE6E0PYEOraHJ1l0fXRw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 13:32:08 -0000

On 5/9/16 7:52 PM, Martin Thomson wrote:
> On 10 May 2016 at 02:14, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> IIUC you want it to work so that if there are only SHA-1 fingerprints then
>> matching one of them is ok, but if there are any SHA-256 fingerprints, and
>> the receiver supports those, then there should be failure if none of the
>> SHA-256 fingerprints match even if an SHA-1 fingerprint does match.
>>
>> I'm not sure how to write a matching rule that works that way, especially
>> one that is clear.
>
> How about this:
>
> anyMatched := false
> for (hashName : supportedHashes) {
>   found := false
>   match := false
>   for (fingerprint : fingerprintAttributes) {
>     if (fingerprint.hashName == hashName) {
>       found = true
>       match = fingerprint.value == hash(hashName, certificate)
>     }
>   }
>   if (match) {
>     anyMatched = true
>   } else if (found) {
>     throw 'no matches for ' + hashName
>   }
> }
> if (!anyMatched) {
>   throw 'no matches at all'
> }

I wasn't looking for code. (I understood how to do that.) My concern was 
for clear yet unambiguous text.

> Or you can go with the more succinct version:
>
> For every hash function that is both supported AND present, check that
> there is at least one matching value.  If there are no matching
> values, abort.

That is clear though incomplete. It at least needs to be qualified that 
it must be applied to each certificate.

But it does require that all supported hashes be tested against every 
certificate. While that isn't particularly expensive, it may be more 
than some want to do.

It could be adjusted, so that fingerprints were tested in descending 
order of strength, stopping when one succeeds. I wouldn't want to 
express doing that as a mandatory requirement, but it would be good if 
the requirements allowed such an approach to be conforming.

	Thanks,
	Paul

>> What are existing implementations doing? Are there any that support
>> multiple certificates?
>
> Firefox has done for a while (though it didn't for even longer due to
> a bug).  I'm sure that's not much help though :)
>


From nobody Tue May 10 06:51:00 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA7012D09C for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 06:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEnbxetDrSQV for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 06:50:53 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A03C12D099 for <mmusic@ietf.org>; Tue, 10 May 2016 06:50:52 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-4b-5731e73a9e27
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 48.B8.18043.A37E1375; Tue, 10 May 2016 15:50:50 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0248.002; Tue, 10 May 2016 15:50:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAAASTuqA=
Date: Tue, 10 May 2016 13:50:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37F9B0DA@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu>
In-Reply-To: <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyM2K7k67Vc8Nwg+dfjSyunfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgynh1pYmx4JRAxa/lKg2M C3m7GDk5JARMJJbtbmeHsMUkLtxbz9bFyMUhJHCEUeLM68MsEM4SRokHfxcwdTFycLAJWEh0 /9MGaRARCJXYfewxWJhZQF3i6uIgkLCwgKfE9dOf2SBKvCQuTF3ADmH7SaxZPJMRxGYRUJV4 fH4zWA2vgK/EtgfnWSFWHWeS+PZwKVgDp4CDxLPnU5lBbEag476fWsMEYjMLiEvcejKfCeJo AYkle84zQ9iiEi8f/2OFsJUkFt3+DFWvI7Fg9yc2CFtbYtnC18wQiwUlTs58wjKBUWwWkrGz kLTMQtIyC0nLAkaWVYyixanFxbnpRkZ6qUWZycXF+Xl6eaklmxiBEXVwy2+rHYwHnzseYhTg YFTi4V3gYBguxJpYVlyZe4hRgoNZSYS3+CFQiDclsbIqtSg/vqg0J7X4EKM0B4uSOK//S8Vw IYH0xJLU7NTUgtQimCwTB6dUA2PXktLwfdtfze6J3H1D5YnFd+bAoE+uU7sYJtuZRUQlt6nr dTj9OSK9sOy75M2wanOfxOn7Eg0VD8fvP9N4f5LUFTfpWWc3lz1+cYFVf4Uef7d1627d1fYT PqeeD+NKWPDWapnB1CAJoWLf+H3THjTZxPfK3lqa0HP3TN6jmOlCcYvcLwn801ViKc5INNRi LipOBADFbgg2pAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/kAsKvbcCJORZP4jB5E-T_cVMcgY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 13:50:55 -0000

Hi,

...

>> Or you can go with the more succinct version:
>>
>> For every hash function that is both supported AND present, check that=20
>> there is at least one matching value.  If there are no matching=20
>> values, abort.
>
>That is clear though incomplete. It at least needs to be qualified that it=
 must be applied to each certificate.
>
>But it does require that all supported hashes be tested against every cert=
ificate. While that isn't particularly expensive, it may be more than some =
want to do.

Question 1: How often will we end up using multiple certificates to begin w=
ith? We have the RTP-and-RTCP-on-different-servers use-case, which I assume=
 will never be used on TLS/DTLS connections between two user endpoints, and=
 not on all endpoint-to-server connections either.

Question 2: How many fingerprints, per certificate, will endpoints provide?=
 My guess is 1-2 (one for backward compatibility, and one new 'n fancy).

So, in reality it may  not be so expensive.=20

Whether it provides more security by matching all hashes is a separate issu=
e.

>It could be adjusted, so that fingerprints were tested in descending order=
 of strength, stopping when one succeeds.=20
>I wouldn't want to express doing that as a mandatory requirement, but it w=
ould be good if the requirements allowed=20
>such an approach to be conforming.

Currently the draft says that an endpoint shall test a "secure enough" hash=
. That doesn't mean it shall be the strongest, but it doesn't forbid using =
the strongest.

But, if we want to say something regarding order of strength, I guess that =
order would have to be an implementation issue?=20

Regards,

Christer






	Thanks,
	Paul

>> What are existing implementations doing? Are there any that support=20
>> multiple certificates?
>
> Firefox has done for a while (though it didn't for even longer due to=20
> a bug).  I'm sure that's not much help though :)
>

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


From nobody Tue May 10 08:23:49 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0083F12D736; Tue, 10 May 2016 08:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level: 
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996] 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 8Dhb_fCuNFf6; Tue, 10 May 2016 08:23:46 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F7612D707; Tue, 10 May 2016 08:23:20 -0700 (PDT)
Received: from [10.10.1.2] ([162.216.46.177]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id u4AFNIWe076833 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 10 May 2016 10:23:19 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [162.216.46.177] claimed to be [10.10.1.2]
From: "Ben Campbell" <ben@nostrum.com>
To: draft-ietf-mmusic-msid.all@ietf.org, "mmusic WG" <mmusic@ietf.org>
Date: Tue, 10 May 2016 11:23:18 -0400
Message-ID: <972D269C-639E-4EC5-B836-BF42DAFD3785@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KejxusGmZxF6IcEyKmlftpQqosw>
Subject: [MMUSIC] AD Evaluation of draft-ietf-mmusic-msid-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 15:23:48 -0000

Hi,

This is my AD evaluation of draft-ietf-mmusic-msid-13. None of my 
comments need block the IETF last call; we can resolve things in 
parallel. I will start the last call shortly.


Thanks!

Ben.

----------

- General: There are a number of terms that are used without (or before) 
definition. A terminology section might be helpful. (Most of these 
should be known to a student of the art, but I think some definitions 
would make this more accessible to those new to the subject.) Examples: 
Binding, group, the various WebRTC API objects...

- 1.2, 2nd paragraph:

"SDP gives a description based on media descriptions."

That's sort of a circular definition. A one sentence definition of 
"media description" would be helpful.

s/mulitple/multiple

- 1.3, first paragraph: "This complication is ignored below."

Ignored by the draft in general? Or just the section below?

- 2, last paragraph
"mux category" needs a citation. (There is a reference, which is cited 
in 4.1, but a citation on first mention would be helpful.

- 3, 2nd paragraph:
Is the "Javascript API" mentioned here the same as the WebRTC API 
mentioned previously? If so, consistent naming would be helpful.

-- 3rd and 4th paragraphs:
The antecedent for "its" is ambiguous (occurs twice)

-- 5th paragraph: "specific "msid-id"
Should that be specific "msid-id" value?

-- 2nd bullet in list: "When a session description is updated to have 
media descriptions
       with an msid "identifier" value, with one or more different
       "appdata" values,"

Does that mean with the _same_ identifier value?


From nobody Tue May 10 12:00:00 2016
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 560BE12D5AD; Tue, 10 May 2016 11:59:56 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
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.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20160510185956.551.7848.idtracker@ietfa.amsl.com>
Date: Tue, 10 May 2016 11:59:56 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-WqeYUE-y47AK8GaU5XNdnJpGxM>
Cc: fandreas@cisco.com, ben@nostrum.com, draft-ietf-mmusic-msid@ietf.org, mmusic@ietf.org, mmusic-chairs@ietf.org
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-msid-13.txt> (WebRTC MediaStream Identification in the Session Description Protocol) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 18:59:56 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document:
- 'WebRTC MediaStream Identification in the Session Description Protocol'
  <draft-ietf-mmusic-msid-13.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 2016-05-24. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document specifies a Session Description Protocol (SDP) Grouping
   mechanism for RTP media streams that can be used to specify relations
   between media streams.

   This mechanism is used to signal the association between the SDP
   concept of "media description" and the WebRTC concept of
   "MediaStream" / "MediaStreamTrack" using SDP signaling.

   This document is a work item of the MMUSIC WG, whose discussion list
   is mmusic@ietf.org.





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

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


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



From nobody Tue May 10 17:02:21 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6D212B02B for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 17:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KAB5Wl57LqxY for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 17:02:17 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E36512B027 for <mmusic@ietf.org>; Tue, 10 May 2016 17:02:17 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id d62so35542813iof.2 for <mmusic@ietf.org>; Tue, 10 May 2016 17:02:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=+sLp+LhCbbyW1NZN8caYuKmzuNPQqCosNJxMdRYbCSY=; b=ByU0a5i43S2Nb2iSMnfu5nzaFKa7q7kzlS+MXepFHqSHOIJHmnrOzm9t6ZteBGmqqi nji2rLx2/uTa8HWZ/MNjhQ3R9HHMES4PDaoQmwTiIHMlbegmBmtpZOpHCKahxMgZWl3K +2+Vr3+cEj+rmmi3jWUAt4QhvnwqFNiO5CnnTMjRzOX+woHnTjkJ9UItiYgdG6oEOwXC U6D/EMvbL/OQ9+Oc7aTjZwhDJ8hoVdUF+/Vr+UktbfspaOLjYyI1RvO+LeQpMsJooKDS ng53ggEmC/EccleSgF8Zoc088rzJSaPTuFurHDcQdhSP+RRLdJnKXpnSuEWYnKXuPFf2 MyyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=+sLp+LhCbbyW1NZN8caYuKmzuNPQqCosNJxMdRYbCSY=; b=OVGnl+ynMMm/hgelHQyQrB8OeKLZitt/JqiRXsL7RqOqI6+29ZABgAs2J/20VtVH7r YSr3ne6pPgRKvp06vKSYi048eVwKM7mb5jsmgRtfWcvtoyHdKOtZceuUuQ035EFtPJKK ZucYXP2tUpfNnZolKndfQVKXDbqMsmC8xjq0v20TgkXGWwwIoRYXXbh2N9GAJPR5J0bk tlG0vi9gv2Zbp+/FaqyPigNCWQN09sHSmXYM9k0Hf94XLXWdw0blbl2BOF/dnNK2vDRw vncVBHGJauqHfMdljmVEE2jWDRi9Gz4NRC205/+z0UGZhzKsd/hdvSk+ue8YcyvVXGI1 ixig==
X-Gm-Message-State: AOPr4FUmO80LOnscSo79Nkz+8KvrdZ8hJQ2Ts6lflhnz/vZ4VCBmZEjfB6mjT1HSqDtUGjkz/ngJLOF8Echn3w==
MIME-Version: 1.0
X-Received: by 10.36.196.11 with SMTP id v11mr2701137itf.49.1462924936593; Tue, 10 May 2016 17:02:16 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 10 May 2016 17:02:16 -0700 (PDT)
In-Reply-To: <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu>
Date: Wed, 11 May 2016 10:02:16 +1000
Message-ID: <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/8cnA7fZ0H3bOsKhkhNULi8DY4AY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 00:02:19 -0000

On 10 May 2016 at 23:32, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> For every hash function that is both supported AND present, check that
>> there is at least one matching value.  If there are no matching
>> values, abort.
>
>
> That is clear though incomplete. It at least needs to be qualified that it
> must be applied to each certificate.

There is only one certificate that you need to test [1].  The one that
your peer offered.

[1].  ... per media section.


From nobody Tue May 10 17:04:26 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4AC12B02B for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 17:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0EtJG4jT_IRE for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 17:04:24 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 017AF12B027 for <mmusic@ietf.org>; Tue, 10 May 2016 17:04:23 -0700 (PDT)
Received: by mail-ig0-x22f.google.com with SMTP id bi2so145497756igb.0 for <mmusic@ietf.org>; Tue, 10 May 2016 17:04:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=xReQb0GZFb+YCavbmTIznipWgqlSR8eGMJEHVJUttf0=; b=0XW5lYbgmaUkt8iIGVjlSzuna4B3Olg5Kssnrf11KCXGxq29vLkYnvRhJvB1fnGiSy oOuGibs77dhkvQoxK9MkiaCOGKTbVe1mmkopmC9wPw6mDb4UvwHfUlcP2WKx8lIGIX3R +LAVO/Umf2A5crDkDyl9GpFiUL26hQs9AxDLXGbZodgsjfcZsbrKQCvodeia4Pjg6xoD qEF1KtGcU67E8sDNpWRKClL7e+43ZEcj9shm8Zf3sWyJT9FrfXNKDgkF6R8aRybm3gmr c93kl3lQTLWi8SQsov8wB+OEgg5DFdsmIqdmoBRUOukGTkPo1Vy/UPThpvwVEvHnqJU4 5m9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=xReQb0GZFb+YCavbmTIznipWgqlSR8eGMJEHVJUttf0=; b=QV/IieroA3pTgvkc4giqNQKHWAkG3jM7+bJCvmHXW+Beq1JD7IUiV5hMIRz/HZ3S+6 kk778O8xCYvUl05x4uDYkuVwf77+lZDKrBuCRMRyrzHiqr3yxwR0IAmoZLpH5Imehm+1 /DE3b2sxixB1RPmld08Zgj1FxCLf6FfO6ZDUKX3RUdhA+c26R3yPeKg6jDE1IsijjfHP CpyR5W57a5czQBrKDAB191qkb/Pk3E3OXWwjZMQcziDIauHwp7EGSuhTdWJK6ZZSvptj CCqOlhXRkvTUjQmNDC+EyyVWv+af8t4Sk4Ku06Dk75mYBEA1MaC/SFl1XKtmuF1TYZ57 N1GQ==
X-Gm-Message-State: AOPr4FWpmyRwD3uRiy6GRLOx7elT9xSYPh/8GtW8zc0kixc+G/EobilXBLAzIesAFIoD5z2ZxdnBshL9tJw0lg==
MIME-Version: 1.0
X-Received: by 10.50.30.73 with SMTP id q9mr20650845igh.77.1462925063339; Tue, 10 May 2016 17:04:23 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 10 May 2016 17:04:23 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37F9B0DA@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37F9B0DA@ESESSMB209.ericsson.se>
Date: Wed, 11 May 2016 10:04:23 +1000
Message-ID: <CABkgnnXNazG_a-msZd5i-Rcp69JNo1bfiFq0qVyoAspzuOuRsQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/oBmdQ3ilk2_iWzONAcw_oWxfVqE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 00:04:25 -0000

On 10 May 2016 at 23:50, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
>>It could be adjusted, so that fingerprints were tested in descending order of strength, stopping when one succeeds.
>>I wouldn't want to express doing that as a mandatory requirement, but it would be good if the requirements allowed
>>such an approach to be conforming.
>
> Currently the draft says that an endpoint shall test a "secure enough" hash. That doesn't mean it shall be the strongest, but it doesn't forbid using the strongest.
>
> But, if we want to say something regarding order of strength, I guess that order would have to be an implementation issue?

That would only work if you required that if the strongest is present,
then it has to match.


From nobody Tue May 10 19:14:27 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8913712D566 for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 19:14:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8knCssBAe0q for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 19:14:24 -0700 (PDT)
Received: from resqmta-po-12v.sys.comcast.net (resqmta-po-12v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6991112B041 for <mmusic@ietf.org>; Tue, 10 May 2016 19:14:24 -0700 (PDT)
Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by comcast with SMTP id 0JfHbzjvGsK9m0JfLb3tUM; Wed, 11 May 2016 02:14:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1462932863; bh=HK1j0adB3OyUWWewpMACjDOiEqkMazBriopuK0Yr7cw=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=HVldHS7gFgu5ADhjvwvLZZkIBrA4tJb3RLkcRTV37i6hJ8npL5FMN7a8DWfPRlRUF 8+ugWVrXGV3v1sG9LoMePnUSf2RS22TKaIyil3eH1149jIM6JSjB8U1xTTjoOvgyY8 2AQHhryol0HiXvREE5gpFWE5tGxidsbNyu++tP3glFQ+hDK7AsAq3LCQm9iBg3B6Fu DGTn2gn8g3hP5Mkzl5R0OF6BMih5q3WGptec1rwAIonAPkJDz2JxlAbOc19BV5wK60 rm6ZVCcVwZpTeyTxX5SEBsIY0KvOS8/OhshOTQXWMNHQAMJbGlYx+Ut20JqKMRtdEK r52y2YLb4fhyQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-po-12v.sys.comcast.net with comcast id sqEP1s0053KdFy101qEPj6; Wed, 11 May 2016 02:14:23 +0000
To: Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu>
Date: Tue, 10 May 2016 22:14:22 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/_pU1d6sDscD-_gPfvDsddbHcAZc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 02:14:25 -0000

On 5/10/16 8:02 PM, Martin Thomson wrote:
> On 10 May 2016 at 23:32, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>> For every hash function that is both supported AND present, check that
>>> there is at least one matching value.  If there are no matching
>>> values, abort.
>>
>>
>> That is clear though incomplete. It at least needs to be qualified that it
>> must be applied to each certificate.
>
> There is only one certificate that you need to test [1].  The one that
> your peer offered.
>
> [1].  ... per media section.

For RTP and SRTP on separate ports there will be two certificates.

	Thanks,
	Paul


From nobody Tue May 10 20:58:31 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A963812D13A for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 20:58:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c9f1vFSikr33 for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 20:58:29 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30D3312D165 for <mmusic@ietf.org>; Tue, 10 May 2016 20:58:25 -0700 (PDT)
Received: by mail-ig0-x236.google.com with SMTP id lr7so26187645igb.1 for <mmusic@ietf.org>; Tue, 10 May 2016 20:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YIbRgVV0obY7jc0eUBFjHQmcVqC+jDkZq3PNYbPgMd0=; b=B0khUFpsX7mVRyGXgWDpyaN8xOTKlAnXccea8fY7zsM2dQ+mMHDJ7o8bRx0Z0M9ZCK tM3bmseKjbPDeGf3aIyn9N8z3hCUYhsur9zh8GWg0DlulekFsX2NmrhprFA1xoULV/jC 8cVWUqdu8px1VVTMEjBb8AHc5MMg5chgjXGJ5PR8IczdaLS2A4jpPg26FHSJMxQtl7I2 6LLQ+zgQJ9BQdaWhGtU1nbfhHxvDA0lphr+XcyfL4YZxLdl+zbM1K+/uspvExnkAKFOx NJzgLjuWVKfPG0vi2KkiZiu4p/E9PqCKSjhOx+XoNjxhqvhUfR6OyQhdzoNunoJroPFK +wEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YIbRgVV0obY7jc0eUBFjHQmcVqC+jDkZq3PNYbPgMd0=; b=G6c+PjFBvuj+is7hLrO/6zeb3BoxxkhzKlj2HyPl8reR9zRHehWcS5IhFNK7OqdeKV cFxCJvOjD37MpiF1RvZ2XJUpxMF1bsLlgx5k/3tXw9FgWCPhE5MMEjFQdw3VxdOif2TG 73RPuJo8BxpHaJ2QMh7qNs1dIJyylDzS+4fRwur7erOjka80NhokzE1GIj/WqC/+VFLe e7CjiOqIyEsNP96DzGmPjh4YtLfi/l7VgGLNBN8pVwZ3YxnsZkgYgwX992Y6YGYdafHA t8dadOl28uN0aTyZpeSWW5nRZl8on23ms4EF5XNwsVvX71x4EHc+5EbgixZA7J3A3fIY 0QuQ==
X-Gm-Message-State: AOPr4FUTkpw3yqgUC9OhMAydjKkMuXJPdMJepjYqYWEh4nltPw0Bs/GxjxWQcfX6HTmgtF2VqIqfCpF5DiMqXQ==
MIME-Version: 1.0
X-Received: by 10.50.183.7 with SMTP id ei7mr1480209igc.77.1462939104647; Tue, 10 May 2016 20:58:24 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 10 May 2016 20:58:24 -0700 (PDT)
In-Reply-To: <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu>
Date: Wed, 11 May 2016 13:58:24 +1000
Message-ID: <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/z1kEVgeUbZXVXql3sNMsf87GJYg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 03:58:31 -0000

On 11 May 2016 at 12:14, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 5/10/16 8:02 PM, Martin Thomson wrote:
>>
>> On 10 May 2016 at 23:32, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>>>
>>>> For every hash function that is both supported AND present, check that
>>>> there is at least one matching value.  If there are no matching
>>>> values, abort.
>>>
>>>
>>>
>>> That is clear though incomplete. It at least needs to be qualified that
>>> it
>>> must be applied to each certificate.
>>
>>
>> There is only one certificate that you need to test [1].  The one that
>> your peer offered.
>>
>> [1].  ... per media section.
>
>
> For RTP and SRTP on separate ports there will be two certificates.

You mean RTP and RTCP, yes. that too.  A reasonable implementation
will use the same certificate most times, so the checking can use a
shortcut.


From nobody Tue May 10 23:32:51 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D7E812D145 for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 23:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UtRrrLKyE6d for <mmusic@ietfa.amsl.com>; Tue, 10 May 2016 23:32:49 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC97312D0C2 for <mmusic@ietf.org>; Tue, 10 May 2016 23:32:48 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-6a-5732d20edda9
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 51.2F.27088.E02D2375; Wed, 11 May 2016 08:32:46 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0248.002; Wed, 11 May 2016 08:32:45 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4A=
Date: Wed, 11 May 2016 06:32:45 +0000
Message-ID: <D358ABDC.8392%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com>
In-Reply-To: <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <01FACDE7A3AD4548BBA7E3914ED30C48@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIIsWRmVeSWpSXmKPExsUyM2K7qy7fJaNwg51HlCyunfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgyljYXF0wmaWi7dFnpgbG ucxdjBwcEgImEn9epHUxcgKZYhIX7q1n62Lk4hASOMIosejNJ2aQhJDAEkaJjodxIPVsAhYS 3f+0QcIiAqESbRf3MYKEmQXUJa4uDgIJCwt4Smx8tI8VosRL4sLUBewQdpLEhiO7wCayCKhK NO7oBqvhFbCSmLilmQliUzeLRNsNNRCbUyBQounxVrBeRqDTvp9aA1bDLCAucevJfCaIkwUk luw5zwxhi0q8fPwPbKaogJ7EvhfnGSE+VJKYtjUNolVHYsHuT2wQtrXEhyWXoWxtiWULXzND nCMocXLmE5YJjBKzkGybhaR9FpL2WUjaZyFpX8DIuopRtDi1OCk33chIL7UoM7m4OD9PLy+1 ZBMjMCIPbvltsIPx5XPHQ4wCHIxKPLwKk4zChVgTy4orcw8xSnAwK4nwzr0IFOJNSaysSi3K jy8qzUktPsQozcGiJM7r/1IxXEggPbEkNTs1tSC1CCbLxMEp1cCou//edZNCl3mq++ScixmO +qzOteNnl6pzm8i0Y+XPO96WaS/+Pv+pe2Flz+Zpl9VZOs75LHYovt90pvhz35Uv9tYrvkxa f77JYhf/LLZLj7ddcjSzyizQ2hhzxbtPUiR0xTSGs/3uBl3vozjnVBttiS78vbM6/TCnZf2x //kHpUKZ+bU5NGKVWIozEg21mIuKEwFpJZf1xAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/v4LoDCWBZu4TaGnpL8_kLkjrFrI>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 06:32:50 -0000

Hi,

...

>>For RTP and SRTP on separate ports there will be two certificates.
>
> You mean RTP and RTCP, yes. that too.  A reasonable implementation
> will use the same certificate most times, so the checking can use a
> shortcut.

But, if we still want to allow multiple certificates, the procedures need
to support that.

So, do we require the same set of hash functions to be provide for each
certificate? If not, we cannot mandate that each hash function must match
each certificate.

Regards,

Christer


From nobody Wed May 11 02:20:15 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E81E12D0B3 for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 02:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKM4O49ZSFLB for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 02:20:12 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EEB1128B44 for <mmusic@ietf.org>; Wed, 11 May 2016 02:20:12 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id d62so46692867iof.2 for <mmusic@ietf.org>; Wed, 11 May 2016 02:20:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YUEhlforpFm1iTfPuutlPCVa+WSMRBtGS0wQ54eAt80=; b=os2sZV+MzAphz5KVNFvi3R8VMd7kHkXRjbSuLI36lhJp3sSukZH/UaTXl+f7DOt8Ly IOSOAl/wBko9QLp0Y7SMPQDpEPxOZZA+2zP1iKVNvpOc2x0xBNuimPh5RgNT3xu+aSok EGqPH4gX7QSUoEPRmUQxdxb1U4un1eGo1kQgNI2/OP/9Kw8/Uv0H7lp1FLSsczB1A9wh cV7CdZrIvWEQNMGufTRP5e8f2QUHBzIqKzEx0DD69v/JrQsHOcwfzv0a/i88tvm1U9xh sN9EpuSw5z8JszLSGuY6o+1nsTY28fnmm3I08ujrPxxVANUaEBDvIEBFqU6M5xWHxpsM ABmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YUEhlforpFm1iTfPuutlPCVa+WSMRBtGS0wQ54eAt80=; b=NTojs4VYdQL/Ll6ABrVa49wTTXYW8lMiK3mrMGNhK3cWo67e9r98GN/G2cxBBNn3AJ mYIU0AeZJjx6M3dAN+sabKOW4Sqace4dBm1ljI+NlkzElDIIHgWEJwbBh0KiPdvYKz4B NUjgzK+JRafeUQz3AUSR0mOIDPdviR0nR7AMqZamSYutIv/2dKpvx+b9lheGZiGVh6zz ljpgPiWkUQGJTGWQxySD4g+c14Gm8oqARBNIkTab9NLds0R3cXSjiEH5OuZ0vTc9ZyeL 2ECPzJ6NJ6zOmyxldLcsjuoO+U7m0EwxyJDTiy8gljFiaWUKxEEqZ2mTW7kpwP/IKiTj RJSg==
X-Gm-Message-State: AOPr4FWis9zGZSKkFSHjrkLqo3OyLkOVg3JB3+xoJps+NbcxSB/hycn7HA7iUSKcpq6GpQAm0a62wrzLPKS4AQ==
MIME-Version: 1.0
X-Received: by 10.36.9.15 with SMTP id 15mr3608124itm.68.1462958411703; Wed, 11 May 2016 02:20:11 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Wed, 11 May 2016 02:20:11 -0700 (PDT)
In-Reply-To: <D358ABDC.8392%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com>
Date: Wed, 11 May 2016 19:20:11 +1000
Message-ID: <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/LgWGcLdgT2zLbPxT9NxFDSpF-cA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 09:20:14 -0000

On 11 May 2016 at 16:32, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> But, if we still want to allow multiple certificates, the procedures need
> to support that.
>
> So, do we require the same set of hash functions to be provide for each
> certificate? If not, we cannot mandate that each hash function must match
> each certificate.


Without a way to identify which fingerprint goes with which (and that
fails if a=fingerprint is at the session level), we are reduced to the
same rules for every certificate: either match just one, or (as I have
been advocating) match one for every hash function you care about.

Note that you could decide that you don't care about a weaker hash
function if a strong one matches.  That reduces the number of checks.


From nobody Wed May 11 03:00:18 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A6A12D63E for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 03:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A3Q4daDMQ6bU for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 03:00:15 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AA4112D60E for <mmusic@ietf.org>; Wed, 11 May 2016 03:00:14 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-e8-573302ab3670
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id ED.8E.12516.BA203375; Wed, 11 May 2016 12:00:11 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Wed, 11 May 2016 12:00:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4A
Date: Wed, 11 May 2016 10:00:10 +0000
Message-ID: <D358DAF1.83DD%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com>
In-Reply-To: <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2DB6CDC7FA3DFE4FB706FD6042DAFEFD@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGIsWRmVeSWpSXmKPExsUyM2K7n+5qJuNwg10T1C2unfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgymi58ZytYBJnxcxVO5kb GHvYuxg5OSQETCS2TVjCDGGLSVy4t56ti5GLQ0jgCKPEvrNPmCCcJYwSzQtnA3VwcLAJWEh0 /9MGaRAR0JVYdPYB2CBmAV+Jlwu+gA0SFvCU2PhoHytEjZfEhakLwFpFBPIk1j9KBwmzCKhK LL30mRHE5hWwkvi0fyMrxKpmVoknj98wgSQ4BQIlHm+dygZiMwId9/3UGiaIXeISt57MZ4I4 WkBiyZ7zUA+ISrx8/A9sr6iAnsS+F+cZIeKKEjvPtjND9OpJ3Jg6hQ3CtpaY+WYKK4StLbFs 4WtmiIMEJU7OfMIygVFiFpJ1s5C0z0LSPgtJ+ywk7QsYWVcxihanFhfnphsZ66UWZSYXF+fn 6eWllmxiBMbmwS2/dXcwrn7teIhRgINRiYdXYZJRuBBrYllxZe4hRgkOZiUR3leMxuFCvCmJ lVWpRfnxRaU5qcWHGKU5WJTEef1fKoYLCaQnlqRmp6YWpBbBZJk4OKUaGAX5tjW90ltYPoFV 3Ny5qCpgn9CLTfqKrw/yz+YM/v5/h5tZnontIgam83djqo94bpktnTx7rfKPQ0aCyzYVt7bc mDoxZYH3ie1zolN/b85dtmIb39QZF5Tj4nN+Tp+0hOsP/9QQi5wEZ9/PH0IUmINOL7g7efeq Vw8+su24xqbx//hTWYnXSnOVWIozEg21mIuKEwG/6C9MyQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Be-upGXyjZwy3E2R7FvWbmHKU9E>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 10:00:16 -0000

Hi,

>>But, if we still want to allow multiple certificates, the procedures need
>> to support that.
>>
>> So, do we require the same set of hash functions to be provide for each
>> certificate? If not, we cannot mandate that each hash function must
>>match
>> each certificate.
>
>
>Without a way to identify which fingerprint goes with which (and that
>fails if a=3Dfingerprint is at the session level),

Even if it=B9s on the media level, as RTP and RTCP use the same m- line.

>we are reduced to the
>same rules for every certificate: either match just one, or (as I have
>been advocating) match one for every hash function you care about.
>
>Note that you could decide that you don't care about a weaker hash
>function if a strong one matches.  That reduces the number of checks.

Isn=B9t that what the current text more or less says:

"An endpoint MUST be able to match at least one of the received
     fingerprints, calculated using a hash algorithm that the endpoint
     considers secure enough,=B2

I could change =B3at least one=B2 to =B3one or more=B2 if you think that wo=
uld be
more clear.

Regards,

Christer





From nobody Wed May 11 03:53:05 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2874512D978 for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 03:53:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wsf38nTb99n5 for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 03:53:02 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DF3F12D968 for <mmusic@ietf.org>; Wed, 11 May 2016 03:53:02 -0700 (PDT)
Received: by mail-ig0-x231.google.com with SMTP id s8so31144975ign.0 for <mmusic@ietf.org>; Wed, 11 May 2016 03:53:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=3fXo4kvMz/nWiA0gZXm/adKYOu6Kkwqsui/9bybH6Q8=; b=As4kO+mjcHvqAstgfFd0ORnjTqpy+bC9oSkesN4aRC0KFMEHSFx9NBTiMQ2XJ8Cl4q LhMAuLOpM2l1roJsjhpPghDbAdm83r1F+lRM0yC25yM8DETgdUlLvWNyBAJPBsA7+dfq ubFquN5DQJ4/yPpHyHLZ4aLzgpml7+OZrEyhwouyW3nyne8lkhtRVbpOByf7wTQw4DOW 1eLet/yKF6zJnyRtJGyLw+srMaH86xh0C1mxYJtkVCwyWYcmidW3xTZNhsBoZ0CVvSXk R+YUfbox9VTXvGmhyttAVgTrTgiGmtrCmVI4FJvcHccM7omkrt3UFgaPmvr+NhY+M6/T pBEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=3fXo4kvMz/nWiA0gZXm/adKYOu6Kkwqsui/9bybH6Q8=; b=Q+5EARay/XatX5L3lf44B1fHuJXfnJnlEcapEPC3rbw+UAVe7kwrlTWYkqG87HFaVD 1A1Nql9nJTDeUL8ou3aV5So0Ze0jZw5ZRoO0k+5Qy1CIgWuvKT8M+9NKMmkDi7CXVpql zrjGtRS0YtP9SPljACvGBtH6w7qMXtvEV5e+hf/AooW25IA8MJNuUc+2HN5OvaRGlBEg nZ6Ngisar3ttbAO/LMtTMvsQxkMzzOT+RtnX3h2SYm2kIKGDJvmtIzujdnRUrETY1Gpl 1d5Xkg578NCNN8xUbERkwj3dPPlnxdkhi/g1KII07Z0yhJEr+I5U+iqyuo3Dz90y5IT9 UL+g==
X-Gm-Message-State: AOPr4FW+wHrLi4Sxcq1ILEK7EU4l8fwZk9DbAYc2M0eZV8NJu2JssCGlmEnBZYxDMcFBzD73UK2oABFa1UIW2g==
MIME-Version: 1.0
X-Received: by 10.50.33.81 with SMTP id p17mr22289635igi.58.1462963981986; Wed, 11 May 2016 03:53:01 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Wed, 11 May 2016 03:53:01 -0700 (PDT)
In-Reply-To: <D358DAF1.83DD%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com>
Date: Wed, 11 May 2016 20:53:01 +1000
Message-ID: <CABkgnnV4f6+mmqxvtRvLiq7Ji5WSVeQYXC=oO-7+aajmw6zb5A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/3RsCO31CqV0LNMRCw3mjo-RLxpk>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 10:53:04 -0000

On 11 May 2016 at 20:00, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> >Note that you could decide that you don't care about a weaker hash
> >function if a strong one matches.  That reduces the number of checks.
>
> Isn=C2=B9t that what the current text more or less says:
>
> "An endpoint MUST be able to match at least one of the received
>      fingerprints, calculated using a hash algorithm that the endpoint
>      considers secure enough,=C2=B2
>
> I could change =C2=B3at least one=C2=B2 to =C2=B3one or more=C2=B2 if you=
 think that would be
> more clear.

No, that implies that if it considers SHA-1 is good enough to talk to
Paul, then it should be OK with using that with Christer, even if
Christer has SHA-256.

I would not put text to the effect of what I said above in the draft.
Simply say that all hashes that it supports need to match.  It's too
hard to explain that you can give up after hash A, but not after hash
B.

I'm wondering if all this is worry about the cost of hashing the
certificate a few times.  That's so little work that we no longer
worry about it in the crypto world.  Take a look at the current TLS
1.3 handshake and work out how many times we run a hash function.
It's well into double digits.


From nobody Wed May 11 04:18:18 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A737412D9D7 for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 04:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9SnQDnHyBU1 for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 04:18:15 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAA8712D9D6 for <mmusic@ietf.org>; Wed, 11 May 2016 04:18:14 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-53-573314f49553
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A0.BB.18043.4F413375; Wed, 11 May 2016 13:18:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0248.002; Wed, 11 May 2016 13:17:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4A///b8oCAADnHgA==
Date: Wed, 11 May 2016 11:17:55 +0000
Message-ID: <D358EF24.840A%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <CABkgnnV4f6+mmqxvtRvLiq7Ji5WSVeQYXC=oO-7+aajmw6zb5A@mail.gmail.com>
In-Reply-To: <CABkgnnV4f6+mmqxvtRvLiq7Ji5WSVeQYXC=oO-7+aajmw6zb5A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <769E8A4E270D6C4391A578E457FBE9C3@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2J7iO4XEeNwg4fbTSyunfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgyljfq1VwTbBi/oXTbA2M cwS7GDk5JARMJA42H2OCsMUkLtxbz9bFyMUhJHCEUWLN3jXMEM4SRolps5eydjFycLAJWEh0 /9MGaRAR0JVYdPYBO4jNLOAr8XLBF2YQW1jAU2Ljo32sEDVeEhemLmCHsOsklj7eAFbDIqAq sefHTxaQkbwCVhIn1sRDrPrNKvHo2nQWkBpOgUCJCde2gNUzAh33/dQaJohd4hK3nsyHOlpA Ysme88wQtqjEy8f/wPaKCuhJ7HtxnhEiriTxY8MlFoheLYkvP/axQdjWEtPfNELdrygxpfsh mM0rIChxcuYTlgmMErOQrJuFpH0WkvZZSNpnIWlfwMi6ilG0OLW4ODfdyEgvtSgzubg4P08v L7VkEyMwMg9u+W21g/Hgc8dDjAIcjEo8vAqTjMKFWBPLiitzDzFKcDArifD+ETYOF+JNSays Si3Kjy8qzUktPsQozcGiJM7r/1IxXEggPbEkNTs1tSC1CCbLxMEp1cAotoHVsS1C11dHYKXj wkPWFX8EpNdoSafNvPPRrf9c71/rGffNQqZEax65OqX95sxn+3Js929wevh/j1ZNWKX2ivUl 7/0uekZf2f5NI+PWU4fKy64nnr1dH5cZWfrTWZDteVHFxhUbPaVY163XEazwcHlypc7KRUK0 SPfc2Q+bdv3i/OH7i5dJiaU4I9FQi7moOBEAmrBVPMgCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/AKY7IbOPIO1yxcE3xWI0gpHSY9s>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 11:18:17 -0000

SGksDQoNCj4+Pk5vdGUgdGhhdCB5b3UgY291bGQgZGVjaWRlIHRoYXQgeW91IGRvbid0IGNhcmUg
YWJvdXQgYSB3ZWFrZXIgaGFzaA0KPj4gPmZ1bmN0aW9uIGlmIGEgc3Ryb25nIG9uZSBtYXRjaGVz
LiAgVGhhdCByZWR1Y2VzIHRoZSBudW1iZXIgb2YgY2hlY2tzLg0KPj4NCj4+IElzbqn2dCB0aGF0
IHdoYXQgdGhlIGN1cnJlbnQgdGV4dCBtb3JlIG9yIGxlc3Mgc2F5czoNCj4+DQo+PiAiQW4gZW5k
cG9pbnQgTVVTVCBiZSBhYmxlIHRvIG1hdGNoIGF0IGxlYXN0IG9uZSBvZiB0aGUgcmVjZWl2ZWQN
Cj4+ICAgICAgZmluZ2VycHJpbnRzLCBjYWxjdWxhdGVkIHVzaW5nIGEgaGFzaCBhbGdvcml0aG0g
dGhhdCB0aGUgZW5kcG9pbnQNCj4+ICAgICAgY29uc2lkZXJzIHNlY3VyZSBlbm91Z2gsqfcNCj4+
DQo+PiBJIGNvdWxkIGNoYW5nZSCp+GF0IGxlYXN0IG9uZan3IHRvIKn4b25lIG9yIG1vcmWp9yBp
ZiB5b3UgdGhpbmsgdGhhdCB3b3VsZA0KPj5iZQ0KPj4gbW9yZSBjbGVhci4NCj4NCj5ObywgdGhh
dCBpbXBsaWVzIHRoYXQgaWYgaXQgY29uc2lkZXJzIFNIQS0xIGlzIGdvb2QgZW5vdWdoIHRvIHRh
bGsgdG8NCj5QYXVsLCB0aGVuIGl0IHNob3VsZCBiZSBPSyB3aXRoIHVzaW5nIHRoYXQgd2l0aCBD
aHJpc3RlciwgZXZlbiBpZg0KPkNocmlzdGVyIGhhcyBTSEEtMjU2Lg0KPg0KPkkgd291bGQgbm90
IHB1dCB0ZXh0IHRvIHRoZSBlZmZlY3Qgb2Ygd2hhdCBJIHNhaWQgYWJvdmUgaW4gdGhlIGRyYWZ0
Lg0KPlNpbXBseSBzYXkgdGhhdCBhbGwgaGFzaGVzIHRoYXQgaXQgc3VwcG9ydHMgbmVlZCB0byBt
YXRjaC4gIEl0J3MgdG9vDQo+aGFyZCB0byBleHBsYWluIHRoYXQgeW91IGNhbiBnaXZlIHVwIGFm
dGVyIGhhc2ggQSwgYnV0IG5vdCBhZnRlciBoYXNoDQo+Qi4NCg0KQWdhaW4sIGlmIHlvdSByZWNl
aXZlIGhhc2ggZnVuY3Rpb24gU0hBLVhYWCBvbmx5IGZvciB0aGUgUlRQIGNlcnRpZmljYXRlLA0K
YnV0IG5vdCBmb3IgdGhlIFJUQ1AgY2VydGlmaWNhdGUsIGl0IHdpbGwgZmFpbCwgYmVjYXVzZSB0
aGUgcmVjZWl2ZXIgd2lsbA0Kbm90IGJlIGFibGUgdG8gbWF0Y2ggYW55IFNIQS1YWFggaGFzaCB3
aXRoIHRoZSBSVENQIGNlcnRpZmljYXRlLg0KDQpUaGUgb25seSB3YXkgdG8gcHJldmVudCB0aGF0
IGlzIGJ5IG1hbmRhdGluZyB0aGUgc2FtZSBzZXQgb2YgaGFzaA0KZnVuY3Rpb25zIGZvciBlYWNo
IGNlcnRpZmljYXRlIC0gd2hpY2ggcGVvcGxlIGhhdmUgY2xhaW1lZCBtYXkgbm90IGJlDQpwb3Nz
aWJsZSBpZiBSVFAgYW5kIFJUQ1AgYXJlIHByb3ZpZGUgYnkgZGlmZmVyZW50IGVudGl0aWVzLg0K
DQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg0KPg0KPkknbSB3b25kZXJpbmcgaWYgYWxsIHRo
aXMgaXMgd29ycnkgYWJvdXQgdGhlIGNvc3Qgb2YgaGFzaGluZyB0aGUNCj5jZXJ0aWZpY2F0ZSBh
IGZldyB0aW1lcy4gIFRoYXQncyBzbyBsaXR0bGUgd29yayB0aGF0IHdlIG5vIGxvbmdlcg0KPndv
cnJ5IGFib3V0IGl0IGluIHRoZSBjcnlwdG8gd29ybGQuICBUYWtlIGEgbG9vayBhdCB0aGUgY3Vy
cmVudCBUTFMNCj4xLjMgaGFuZHNoYWtlIGFuZCB3b3JrIG91dCBob3cgbWFueSB0aW1lcyB3ZSBy
dW4gYSBoYXNoIGZ1bmN0aW9uLg0KPkl0J3Mgd2VsbCBpbnRvIGRvdWJsZSBkaWdpdHMuDQoNCg==


From nobody Wed May 11 06:51:19 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C359E12D6C1 for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 06:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJ6fWgssaI8R for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 06:51:16 -0700 (PDT)
Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F90912D6C4 for <mmusic@ietf.org>; Wed, 11 May 2016 06:51:16 -0700 (PDT)
Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by comcast with SMTP id 0UXXbA168LCmU0UXjb2MxR; Wed, 11 May 2016 13:51:15 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1462974675; bh=K84gyHItrxTbHNwN9XZ4w2AxvejXxQ1L4LKlXUwC+9U=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=d3V3aywtLRpyYb2zLN8RM36lpTNYEKXA5uS5a3cscEyD0ZDGbGUad89qP5unZUXir c3NIRNvO+d6/tk0vGuaCeENQEtmN/M9vlhlUq5u5KGoa6OjULM83yUZI8+5wAzGUI/ w7NPQjzgHf/jc5GdCbqQhBPBGVDLNj2lwCpETjHL2QNYfRgIvGEmrfWOHvmw8Oc0y0 mvbv4OyVC5AhW0e1Bnq/V2FGART2qj5De8vRLp9raMnEdaPBnn0xyjpJ1k2rhB9DvF qszWIn83HZnhZNKC+cFK56JygYyr6pIWwKtYlYLJ2g8ShP3c8nyAvG9G4F7LADJCFu wYkENWLzsTcgA==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-16v.sys.comcast.net with comcast id t1rF1s0033KdFy1011rFRz; Wed, 11 May 2016 13:51:15 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu>
Date: Wed, 11 May 2016 09:51:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <D358DAF1.83DD%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/B5V-HXOSXA3TCIEOa_NcV35lKIA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 13:51:18 -0000

On 5/11/16 6:00 AM, Christer Holmberg wrote:
> Hi,
>
>>> But, if we still want to allow multiple certificates, the procedures need
>>> to support that.
>>>
>>> So, do we require the same set of hash functions to be provide for each
>>> certificate? If not, we cannot mandate that each hash function must
>>> match
>>> each certificate.
>>
>>
>> Without a way to identify which fingerprint goes with which (and that
>> fails if a=fingerprint is at the session level),
>
> Even if it¹s on the media level, as RTP and RTCP use the same m- line.
>
>> we are reduced to the
>> same rules for every certificate: either match just one, or (as I have
>> been advocating) match one for every hash function you care about.
>>
>> Note that you could decide that you don't care about a weaker hash
>> function if a strong one matches.  That reduces the number of checks.
>
> Isn¹t that what the current text more or less says:
>
> "An endpoint MUST be able to match at least one of the received
>      fingerprints, calculated using a hash algorithm that the endpoint
>      considers secure enough,²

The part we are not talking about here is what the sender must do. With 
the sort of algorithm Martin is talking about, if the intent is to cover 
multiple certificates then every hash function used must be used for 
every certificate. Whether that is a burden is debatable. If the 
matching algorithm requires that, then it must be a stated requirement 
on the sender.

	Thanks,
	Paul


From nobody Wed May 11 07:06:28 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D246612DADF for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 07:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id akJrJfVw8riE for <mmusic@ietfa.amsl.com>; Wed, 11 May 2016 07:06:26 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DA7D12DAD2 for <mmusic@ietf.org>; Wed, 11 May 2016 07:06:12 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-a5-57333c511e7b
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 44.B6.27088.15C33375; Wed, 11 May 2016 16:06:09 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0248.002; Wed, 11 May 2016 16:06:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AA==
Date: Wed, 11 May 2016 14:06:08 +0000
Message-ID: <D35916D7.84B4%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu>
In-Reply-To: <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <32A8DE4F326F4644803178D143B5DA58@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2J7uG6gjXG4wYz9chbXzvxjtJi6/DGL xYoNB1gdmD3+vv/A5LFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZczbe5q54BJHReeniawN jFs4uhg5OSQETCT2H/zDBGGLSVy4t56ti5GLQ0jgCKPEo3UvmCCcJYwSf1qms3YxcnCwCVhI dP/TBmkQEQiV2H3sMRNImFlAXeLq4iCQsLCAp8TGR/tYIUq8JC5MXcAOUiIiUCdxr0UcJMwi oCrx6fYRFhCbV8BKovHwB3aITa9YJa5tvQ/WyyngIPGtbQXYbYxAt30/tQbMZhYQl7j1ZD7U zQISS/acZ4awRSVePv4H1isqoCex78V5Roi4osTV6cuherUkvvzYxwZhW0tMuT0VylaUmNL9 kB3iIEGJkzOfsExglJiFZN0sJO2zkLTPQtI+C0n7AkbWVYyixanFSbnpRkZ6qUWZycXF+Xl6 eaklmxiBkXlwy2+DHYwvnzseYhTgYFTi4VWYZBQuxJpYVlyZe4hRgoNZSYRXydo4XIg3JbGy KrUoP76oNCe1+BCjNAeLkjiv/0vFcCGB9MSS1OzU1ILUIpgsEwenVAOjHtfjVGcGXeY/ew7+ u1WXXrhI5f0R6UVnpwTyRarKcLxtUPd7GqP07/D62nfL9hSxF63c7F3YpauopNzcejXSfdPT 39L9GVcaQkvEXwjlWczjqZ94yeN6d0IX62X9hb6nXKPmtyZpdUwyv5vOeDf31QmWm4ennf/S rBOy99neaRUPyrudWuKVWIozEg21mIuKEwGNb7IRyAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/bOONVR8EpmYgyqOibFciycg8cpo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 May 2016 14:06:28 -0000

SGksDQoNCi4uLg0KPj4NCj4+IElzbqn2dCB0aGF0IHdoYXQgdGhlIGN1cnJlbnQgdGV4dCBtb3Jl
IG9yIGxlc3Mgc2F5czoNCj4+DQo+PiAiQW4gZW5kcG9pbnQgTVVTVCBiZSBhYmxlIHRvIG1hdGNo
IGF0IGxlYXN0IG9uZSBvZiB0aGUgcmVjZWl2ZWQNCj4+ICAgICAgZmluZ2VycHJpbnRzLCBjYWxj
dWxhdGVkIHVzaW5nIGEgaGFzaCBhbGdvcml0aG0gdGhhdCB0aGUgZW5kcG9pbnQNCj4+ICAgICAg
Y29uc2lkZXJzIHNlY3VyZSBlbm91Z2gsqfcNCj4NCj5UaGUgcGFydCB3ZSBhcmUgbm90IHRhbGtp
bmcgYWJvdXQgaGVyZSBpcyB3aGF0IHRoZSBzZW5kZXIgbXVzdCBkby4gV2l0aA0KPnRoZSBzb3J0
IG9mIGFsZ29yaXRobSBNYXJ0aW4gaXMgdGFsa2luZyBhYm91dCwgaWYgdGhlIGludGVudCBpcyB0
byBjb3Zlcg0KPm11bHRpcGxlIGNlcnRpZmljYXRlcyB0aGVuIGV2ZXJ5IGhhc2ggZnVuY3Rpb24g
dXNlZCBtdXN0IGJlIHVzZWQgZm9yDQo+ZXZlcnkgY2VydGlmaWNhdGUuDQoNCkNvcnJlY3QuDQoN
Cj5XaGV0aGVyIHRoYXQgaXMgYSBidXJkZW4gaXMgZGViYXRhYmxlLiBJZiB0aGUNCj5tYXRjaGlu
ZyBhbGdvcml0aG0gcmVxdWlyZXMgdGhhdCwgdGhlbiBpdCBtdXN0IGJlIGEgc3RhdGVkIHJlcXVp
cmVtZW50DQo+b24gdGhlIHNlbmRlci4NCg0KQ29ycmVjdC4NCg0KVGhlIHF1ZXN0aW9uIGlzIHdo
ZXRoZXIgc3VjaCByZXF1aXJlbWVudCB3b3VsZCBiZSBoYXJtZnVsIHRvIHRoZQ0KUlRQLWFuZC1S
VENQLW9uLWRpZmZlcmVudC1zZXJ2ZXJzIHVzZS1jYXNlLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rl
cg0KDQoNCg==


From nobody Thu May 12 01:11:16 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CEEC12B068 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 01:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJS4KiYZx1X3 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 01:11:14 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A154212D112 for <mmusic@ietf.org>; Thu, 12 May 2016 01:11:13 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-2e-57343a9f35e4
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id FA.6C.12516.F9A34375; Thu, 12 May 2016 10:11:11 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0248.002; Thu, 12 May 2016 10:11:10 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - WHERE WE ARE
Thread-Index: AQHRrCXXFNgvwocFVkWNrBE31b/zcA==
Date: Thu, 12 May 2016 08:11:10 +0000
Message-ID: <D35A123E.8508%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <BB83ACBFD8A9ED4595888C90F67180E9@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM2K7k+58K5Nwgw1vLSyunfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgytg19ztTwTqOio1XZzM3 MF5l62Lk4JAQMJH4c86li5ETyBSTuHBvPVCYi0NI4AijxOHvD8FqhASWMEq8YwIx2QQsJLr/ aYOUiwgkS5x5sZAZxGYW8JV4/3M6O4gtLBAlsXj9ZhaImmiJ13MvMkPYehL9G/eygdgsAqoS M87OArN5Bawkfv84AtbLCHTC91NrmCBmikvcejKfCeI0AYkle84zQ9iiEi8f/2MFsUWBZu57 cZ4RIq4o8fHVPkaIXj2JG1OnsEHY1hLzFj1jgbC1JZYtfM0MsVdQ4uTMJywTGMVmIVk3C0n7 LCTts5C0z0LSvoCRdRWjaHFqcXFuupGxXmpRZnJxcX6eXl5qySZGYJQd3PJbdwfj6teOhxgF OBiVeHgXPDYOF2JNLCuuzD3EKMHBrCTCy2NuEi7Em5JYWZValB9fVJqTWnyIUZqDRUmc1/+l YriQQHpiSWp2ampBahFMlomDU6qB0XHSzNgdVTIVHGwT5H5GqTubqTHFr8zcO2P15LCDD/dk /JksdMOTOXhW6f+Jx36o/3t50f/nR7nOvu6wQNPN/H8OSb4LetAU9EHfMdVEQlTN+/rNbUWC wn1Oy3j+vReoNDoU8InpVl6jUYH28RYZZZmKDUsWbZ3AEFwe8WJhLntHpMTBkkXflFiKMxIN tZiLihMB81GU464CAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/t_gd5Ycbk6mAPqkY9eE7yS6y6BE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - WHERE WE ARE
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 08:11:15 -0000

Hi,

Based on the discussions, it seems (please correct me if I=B9m wrong) that
we have to alternatives:


ALTERNATIVE 1 (Martin=B9s):

The SENDER MUST provide one or more hash functions for each offered
certificate. The set of hash functions MUST be identical for each offered
certificate.

The RECEIVER MUST match each selected* certificate with each hash function
provided by the sender (and supported by the receiver).



ALTERNATIVE 2 (Roman=B9s):

The SENDER MUST provide one or more hash functions for each offered
certificate. The set of hash functions can be different for each offered
certificate.

The RECEIVER MUST match each selected* certificate with one hash function
supported by the receiver and provided by the sender. That hash function
may be different for each used certificate, as long as it is considered
secure by the receiver.


Regards,

Christer


* In most cases a single certificate is selected (as part of the DTLS
handshake), but there are use-cases where RTP and RTCP will use separate
certificates


From nobody Thu May 12 01:19:24 2016
Return-Path: <kevindempsey70@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 16FFC12D169 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 01:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EsSe9t1eFQt6 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 01:19:19 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E00B12B029 for <mmusic@ietf.org>; Thu, 12 May 2016 01:19:15 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id m188so88457207vka.1 for <mmusic@ietf.org>; Thu, 12 May 2016 01:19:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=kRPUwI4TvTApairR1swldGqfTuwbkMKH3oJkUU2KkQ8=; b=gbjXy775idB39dltmBRabzZxywq3YwsVBmh1/vvqVVAeW2VNzlZpzvsnh1I5QZHsfQ FcS58NSDY7iK9GIehharz6GeUCuP1VJsI1REsXZI49PJiiv7l8aou7YybqyNhvz4qb7C x0JVzq/2CRkS56eR0N3u5QDBiTts6ghS+WELhNXDczBmwGLw2A5OTKuCrNUz4VXJVaua yyFUptLrbwBs7ODWQsj5ZkYUbR4sKvJj+PklxnxyrtjgrASc+c0rRvWeqdXuaM4auCoq uvf79mvTyKqcEsrPg1OhuBSSiGH/YzL79LSAB73RTHxhW7srJkMRBzPgRpnlwRC0Et3m fKhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=kRPUwI4TvTApairR1swldGqfTuwbkMKH3oJkUU2KkQ8=; b=SZAI9Id5vLL4w9ylpLwKPfslViOS6wKtPj7+8iPOnXD/AThvTzW4fUg2M4sv7tnhfx Hn+5z729HyiH3CiClhd27D4hK8nrlU/81qnnKABYCf/iCT6vBE+8fQ8IfsKngkyYenMB CKsEaZI4Hgf2n7UZI4gNMok+EbbErHi6bL2gCl+WxRuT7mcUnJjSeRN1P95x1mp5yRFf PJmJGoDNmdf44OVQHKc3RkZqYCx7ZhsTV/8J4DVyfcPLWh9Bi7fPGeWqut3Hvvupoces j+0DXNTSSvUbJozuvgRotzJZkPvmiUQd45amHtqKFAC4PYHUsXH/FDtfBcmbPSvYU4Xg 2E0g==
X-Gm-Message-State: AOPr4FUfxVzj7lOm5QJPfr3uE6ltWn6NmPHNWteZX8ZiHI70E4IVjasHzwc+7AlgzmlGg/8iJ5Dp+1OuTtA8ag==
MIME-Version: 1.0
X-Received: by 10.176.6.161 with SMTP id g30mr4212484uag.142.1463041154541; Thu, 12 May 2016 01:19:14 -0700 (PDT)
Received: by 10.159.32.132 with HTTP; Thu, 12 May 2016 01:19:14 -0700 (PDT)
In-Reply-To: <D35916D7.84B4%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com>
Date: Thu, 12 May 2016 09:19:14 +0100
Message-ID: <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com>
From: Kevin Dempsey <kevindempsey70@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c047ca04ef1c10532a0d0cf
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/QVJy7eRk6YN7P_vW5-Api-2gsNU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 08:19:22 -0000

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

An alternative would be to provide some way to associate the fingerprints
of each certificate with each other. For example, replace multiple
a=3Dfingerprint attributes with something like:
a=3Dfingerprints: hash1 AAAA, hash2 BBBBBBBB, hash3 CCCCCCCCCCCC
Then the requirement on the receiving side would be that the certificate
must match at least one 'fingerprints' line. Which, and how many, of the
hashes that are checked would depend on the receivers preferences.

On 11 May 2016 at 15:06, Christer Holmberg <christer.holmberg@ericsson.com>
wrote:

> Hi,
>
> ...
> >>
> >> Isn=C2=B9t that what the current text more or less says:
> >>
> >> "An endpoint MUST be able to match at least one of the received
> >>      fingerprints, calculated using a hash algorithm that the endpoint
> >>      considers secure enough,=C2=B2
> >
> >The part we are not talking about here is what the sender must do. With
> >the sort of algorithm Martin is talking about, if the intent is to cover
> >multiple certificates then every hash function used must be used for
> >every certificate.
>
> Correct.
>
> >Whether that is a burden is debatable. If the
> >matching algorithm requires that, then it must be a stated requirement
> >on the sender.
>
> Correct.
>
> The question is whether such requirement would be harmful to the
> RTP-and-RTCP-on-different-servers use-case.
>
> Regards,
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">An alternative would be to provide some way to associate t=
he fingerprints of each certificate with each other. For example, replace m=
ultiple a=3Dfingerprint attributes with something like:<div>a=3Dfingerprint=
s: hash1 AAAA, hash2 BBBBBBBB, hash3 CCCCCCCCCCCC</div><div>Then the requir=
ement on the receiving side would be that the certificate must match at lea=
st one &#39;fingerprints&#39; line. Which, and how many, of the hashes that=
 are checked would depend on the receivers preferences.</div></div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On 11 May 2016 at 15:06, =
Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg=
@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
...<br>
<span class=3D"">&gt;&gt;<br>
&gt;&gt; Isn=C2=B9t that what the current text more or less says:<br>
&gt;&gt;<br>
&gt;&gt; &quot;An endpoint MUST be able to match at least one of the receiv=
ed<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 fingerprints, calculated using a hash algorith=
m that the endpoint<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 considers secure enough,=C2=B2<br>
&gt;<br>
&gt;The part we are not talking about here is what the sender must do. With=
<br>
&gt;the sort of algorithm Martin is talking about, if the intent is to cove=
r<br>
&gt;multiple certificates then every hash function used must be used for<br=
>
&gt;every certificate.<br>
<br>
</span>Correct.<br>
<span class=3D""><br>
&gt;Whether that is a burden is debatable. If the<br>
&gt;matching algorithm requires that, then it must be a stated requirement<=
br>
&gt;on the sender.<br>
<br>
</span>Correct.<br>
<br>
The question is whether such requirement would be harmful to the<br>
RTP-and-RTCP-on-different-servers use-case.<br>
<br>
Regards,<br>
<br>
Christer<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div>

--94eb2c047ca04ef1c10532a0d0cf--


From nobody Thu May 12 01:57:59 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFE2912D145 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 01:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J56sPhkRoNyh for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 01:57:55 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C237C12D096 for <mmusic@ietf.org>; Thu, 12 May 2016 01:57:54 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-a5-5734458fd22a
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id CA.07.12516.F8544375; Thu, 12 May 2016 10:57:52 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0248.002; Thu, 12 May 2016 10:57:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAA=
Date: Thu, 12 May 2016 08:57:51 +0000
Message-ID: <D35A1FAC.8533%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com>
In-Reply-To: <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.146]
Content-Type: multipart/alternative; boundary="_000_D35A1FAC8533christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKIsWRmVeSWpSXmKPExsUyM2K7ve4EV5Nwg5NXuCxuzn/LYnHtzD9G i6nLH7NYrNhwgNWBxePv+w9MHjtn3WX3WLLkJ1MAcxSXTUpqTmZZapG+XQJXxvufnUwFd60q Psw/w9bA2GLZxcjJISFgIjHjzEdGCFtM4sK99WxdjFwcQgJHGCU+LH7OAuEsYZSY+PQNcxcj BwebgIVE9z9tkAYRAR2Jg/cns4PYzAJVEp3HX4DZwgKeEhsf7WOFqPGSuDB1ATvIHBGBLkaJ A8uPM4EkWARUJZY1n2ADsXkFrCRu/r0KFhcSeMQmMWe2FojNKRAoMWnPRBYQmxHouu+n1jBB LBOXuPVkPhPE1QISS/acZ4awRSVePv4HtlhUQE9i34vzUJ8pSfzYcIkF5H5mgXiJY6vEINYK Spyc+YRlAqPYLCRTZyFUzUJSBVGiJfHlxz42CFtRYkr3Q3aIck2JNw9rIcLWEp3vFrIgK1nA yLGKUbQ4tbg4N93IWC+1KDO5uDg/Ty8vtWQTIzByD275rbuDcfVrx0OMAhyMSjy8Cx4bhwux JpYVV+YeYpTgYFYS4eUxNwkX4k1JrKxKLcqPLyrNSS0+xCjNwaIkzuv/UjFcSCA9sSQ1OzW1 ILUIJsvEwSnVwGj9d1FUhFhYCpP77sr8L9OXl3w1fT/HafccNfOT/zm4WaVfdBoUhzvOebJC /aXWeobuaQddBYREli+OY6xP+z1Bm+dRwIdeqxe6NswsO5+lreWtsb9Xs8c/3jpr6e/tF7Xy xSymPJmkcD/A3Y4nyYBpfZyGzQPn0GtxZbOeZz88qjXhVYiCrBJLcUaioRZzUXEiAFrnlPPY AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/afNwpUyP1LYYxO62u7orGykOhiw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 08:57:58 -0000

--_000_D35A1FAC8533christerholmbergericssoncom_
Content-Type: text/plain; charset="euc-kr"
Content-Transfer-Encoding: base64

SGksDQoNCj5BbiBhbHRlcm5hdGl2ZSB3b3VsZCBiZSB0byBwcm92aWRlIHNvbWUgd2F5IHRvIGFz
c29jaWF0ZSB0aGUgZmluZ2VycHJpbnRzIG9mIGVhY2ggY2VydGlmaWNhdGUgd2l0aCBlYWNoIG90
aGVyLiBGb3IgZXhhbXBsZSwgcmVwbGFjZSBtdWx0aXBsZSBhPWZpbmdlcnByaW50IGF0dHJpYnV0
ZXMgd2l0aCBzb21ldGhpbmcgbGlrZToNCj5hPWZpbmdlcnByaW50czogaGFzaDEgQUFBQSwgaGFz
aDIgQkJCQkJCQkIsIGhhc2gzIENDQ0NDQ0NDQ0NDQw0KPlRoZW4gdGhlIHJlcXVpcmVtZW50IG9u
IHRoZSByZWNlaXZpbmcgc2lkZSB3b3VsZCBiZSB0aGF0IHRoZSBjZXJ0aWZpY2F0ZSBtdXN0IG1h
dGNoIGF0IGxlYXN0IG9uZSAnZmluZ2VycHJpbnRzJyBsaW5lLiBXaGljaCwgYW5kIGhvdyBtYW55
LCBvZiB0aGUgaGFzaGVzIHRoYXQgYXJlIGNoZWNrZWQgd291bGQgZGVwZW5kIG9uIHRoZSByZWNl
aXZlcnMgcHJlZmVyZW5jZXMuDQoNCkNvcnJlY3QuDQoNCkhvd2V2ZXIsIGFzIHRoYXQgc29sdXRp
b24gd291bGQgbm90IGJlIGJhY2t3YXJkIGNvbXBhdGlibGUsIHRoZSBxdWVzdGlvbiBpcyB3aGV0
aGVyIGV4aXN0aW5nIGRlcGxveW1lbnRzIHRvZGF5IHN1cHBvcnQgbXVsdGlwbGUgY2VydGlmaWNh
dGVzLiBJZiBub3QsIHRoZW4gdGhpcyBjb3VsZCBiZSBhbiBvcHRpb24uDQoNCkluIGNhc2VzIHdo
ZXJlIG9ubHkgYSBzaW5nbGUgY2VydGlmaWNhdGUgaXMgb2ZmZXJlZCwgd2UgY291bGQgY29udGlu
dWUgdXNpbmcgdGhlIGV4aXN0aW5nIGZpbmdlcnByaW50IGF0dHJpYnV0ZS4NCg0KUmVnYXJkcywN
Cg0KQ2hyaXN0ZXINCg0KDQoNCg0KT24gMTEgTWF5IDIwMTYgYXQgMTU6MDYsIENocmlzdGVyIEhv
bG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208bWFpbHRvOmNocmlzdGVyLmhv
bG1iZXJnQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KSGksDQoNCi4uLg0KPj4NCj4+IElzbqn2dCB0
aGF0IHdoYXQgdGhlIGN1cnJlbnQgdGV4dCBtb3JlIG9yIGxlc3Mgc2F5czoNCj4+DQo+PiAiQW4g
ZW5kcG9pbnQgTVVTVCBiZSBhYmxlIHRvIG1hdGNoIGF0IGxlYXN0IG9uZSBvZiB0aGUgcmVjZWl2
ZWQNCj4+ICAgICAgZmluZ2VycHJpbnRzLCBjYWxjdWxhdGVkIHVzaW5nIGEgaGFzaCBhbGdvcml0
aG0gdGhhdCB0aGUgZW5kcG9pbnQNCj4+ICAgICAgY29uc2lkZXJzIHNlY3VyZSBlbm91Z2gsqfcN
Cj4NCj5UaGUgcGFydCB3ZSBhcmUgbm90IHRhbGtpbmcgYWJvdXQgaGVyZSBpcyB3aGF0IHRoZSBz
ZW5kZXIgbXVzdCBkby4gV2l0aA0KPnRoZSBzb3J0IG9mIGFsZ29yaXRobSBNYXJ0aW4gaXMgdGFs
a2luZyBhYm91dCwgaWYgdGhlIGludGVudCBpcyB0byBjb3Zlcg0KPm11bHRpcGxlIGNlcnRpZmlj
YXRlcyB0aGVuIGV2ZXJ5IGhhc2ggZnVuY3Rpb24gdXNlZCBtdXN0IGJlIHVzZWQgZm9yDQo+ZXZl
cnkgY2VydGlmaWNhdGUuDQoNCkNvcnJlY3QuDQoNCj5XaGV0aGVyIHRoYXQgaXMgYSBidXJkZW4g
aXMgZGViYXRhYmxlLiBJZiB0aGUNCj5tYXRjaGluZyBhbGdvcml0aG0gcmVxdWlyZXMgdGhhdCwg
dGhlbiBpdCBtdXN0IGJlIGEgc3RhdGVkIHJlcXVpcmVtZW50DQo+b24gdGhlIHNlbmRlci4NCg0K
Q29ycmVjdC4NCg0KVGhlIHF1ZXN0aW9uIGlzIHdoZXRoZXIgc3VjaCByZXF1aXJlbWVudCB3b3Vs
ZCBiZSBoYXJtZnVsIHRvIHRoZQ0KUlRQLWFuZC1SVENQLW9uLWRpZmZlcmVudC1zZXJ2ZXJzIHVz
ZS1jYXNlLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQptbXVzaWNA
aWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbW11c2ljDQoNCg==

--_000_D35A1FAC8533christerholmbergericssoncom_
Content-Type: text/html; charset="euc-kr"
Content-ID: <594E1F7EA4953F4FA145DECA5967C27A@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PWV1Yy1rciI+DQo8L2hlYWQ+DQo8Ym9keSBzdHlsZT0id29yZC13
cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1i
cmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTog
MTRweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NCjxkaXY+SGksPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+Jmd0O0FuIGFsdGVybmF0aXZlIHdvdWxkIGJlIHRv
IHByb3ZpZGUgc29tZSB3YXkgdG8gYXNzb2NpYXRlIHRoZSBmaW5nZXJwcmludHMgb2YgZWFjaCBj
ZXJ0aWZpY2F0ZSB3aXRoIGVhY2ggb3RoZXIuIEZvciBleGFtcGxlLCByZXBsYWNlIG11bHRpcGxl
IGE9ZmluZ2VycHJpbnQgYXR0cmlidXRlcyB3aXRoIHNvbWV0aGluZyBsaWtlOg0KPGRpdj4mZ3Q7
YT1maW5nZXJwcmludHM6IGhhc2gxIEFBQUEsIGhhc2gyIEJCQkJCQkJCLCBoYXNoMyBDQ0NDQ0ND
Q0NDQ0M8L2Rpdj4NCjxkaXY+Jmd0O1RoZW4gdGhlIHJlcXVpcmVtZW50IG9uIHRoZSByZWNlaXZp
bmcgc2lkZSB3b3VsZCBiZSB0aGF0IHRoZSBjZXJ0aWZpY2F0ZSBtdXN0IG1hdGNoIGF0IGxlYXN0
IG9uZSAnZmluZ2VycHJpbnRzJyBsaW5lLiBXaGljaCwgYW5kIGhvdyBtYW55LCBvZiB0aGUgaGFz
aGVzIHRoYXQgYXJlIGNoZWNrZWQgd291bGQgZGVwZW5kIG9uIHRoZSByZWNlaXZlcnMgcHJlZmVy
ZW5jZXMuPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPGRpdj5Db3JyZWN0LjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+SG93
ZXZlciwgYXMgdGhhdCBzb2x1dGlvbiB3b3VsZCBub3QgYmUgYmFja3dhcmQgY29tcGF0aWJsZSwg
dGhlIHF1ZXN0aW9uIGlzIHdoZXRoZXIgZXhpc3RpbmcgZGVwbG95bWVudHMgdG9kYXkgc3VwcG9y
dCBtdWx0aXBsZSBjZXJ0aWZpY2F0ZXMuIElmIG5vdCwgdGhlbiB0aGlzIGNvdWxkIGJlIGFuIG9w
dGlvbi48L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkluIGNhc2VzIHdoZXJlIG9ubHkg
YSBzaW5nbGUgY2VydGlmaWNhdGUgaXMgb2ZmZXJlZCwgd2UgY291bGQgY29udGludWUgdXNpbmcg
dGhlIGV4aXN0aW5nIGZpbmdlcnByaW50IGF0dHJpYnV0ZS48L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8ZGl2PlJlZ2FyZHMsPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5DaHJpc3Rl
cjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4N
CjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5P
biAxMSBNYXkgMjAxNiBhdCAxNTowNiwgQ2hyaXN0ZXIgSG9sbWJlcmcgPHNwYW4gZGlyPSJsdHIi
Pg0KJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20iIHRh
cmdldD0iX2JsYW5rIj5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208L2E+Jmd0Ozwvc3Bh
bj4gd3JvdGU6PGJyPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0ibWFy
Z2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFl
eCI+DQpIaSw8YnI+DQo8YnI+DQouLi48YnI+DQo8c3BhbiBjbGFzcz0iIj4mZ3Q7Jmd0Ozxicj4N
CiZndDsmZ3Q7IElzbqn2dCB0aGF0IHdoYXQgdGhlIGN1cnJlbnQgdGV4dCBtb3JlIG9yIGxlc3Mg
c2F5czo8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7ICZxdW90O0FuIGVuZHBvaW50IE1VU1Qg
YmUgYWJsZSB0byBtYXRjaCBhdCBsZWFzdCBvbmUgb2YgdGhlIHJlY2VpdmVkPGJyPg0KJmd0OyZn
dDsmbmJzcDsgJm5ic3A7ICZuYnNwOyBmaW5nZXJwcmludHMsIGNhbGN1bGF0ZWQgdXNpbmcgYSBo
YXNoIGFsZ29yaXRobSB0aGF0IHRoZSBlbmRwb2ludDxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgY29uc2lkZXJzIHNlY3VyZSBlbm91Z2gsqfc8YnI+DQomZ3Q7PGJyPg0KJmd0O1Ro
ZSBwYXJ0IHdlIGFyZSBub3QgdGFsa2luZyBhYm91dCBoZXJlIGlzIHdoYXQgdGhlIHNlbmRlciBt
dXN0IGRvLiBXaXRoPGJyPg0KJmd0O3RoZSBzb3J0IG9mIGFsZ29yaXRobSBNYXJ0aW4gaXMgdGFs
a2luZyBhYm91dCwgaWYgdGhlIGludGVudCBpcyB0byBjb3Zlcjxicj4NCiZndDttdWx0aXBsZSBj
ZXJ0aWZpY2F0ZXMgdGhlbiBldmVyeSBoYXNoIGZ1bmN0aW9uIHVzZWQgbXVzdCBiZSB1c2VkIGZv
cjxicj4NCiZndDtldmVyeSBjZXJ0aWZpY2F0ZS48YnI+DQo8YnI+DQo8L3NwYW4+Q29ycmVjdC48
YnI+DQo8c3BhbiBjbGFzcz0iIj48YnI+DQomZ3Q7V2hldGhlciB0aGF0IGlzIGEgYnVyZGVuIGlz
IGRlYmF0YWJsZS4gSWYgdGhlPGJyPg0KJmd0O21hdGNoaW5nIGFsZ29yaXRobSByZXF1aXJlcyB0
aGF0LCB0aGVuIGl0IG11c3QgYmUgYSBzdGF0ZWQgcmVxdWlyZW1lbnQ8YnI+DQomZ3Q7b24gdGhl
IHNlbmRlci48YnI+DQo8YnI+DQo8L3NwYW4+Q29ycmVjdC48YnI+DQo8YnI+DQpUaGUgcXVlc3Rp
b24gaXMgd2hldGhlciBzdWNoIHJlcXVpcmVtZW50IHdvdWxkIGJlIGhhcm1mdWwgdG8gdGhlPGJy
Pg0KUlRQLWFuZC1SVENQLW9uLWRpZmZlcmVudC1zZXJ2ZXJzIHVzZS1jYXNlLjxicj4NCjxicj4N
ClJlZ2FyZHMsPGJyPg0KPGJyPg0KQ2hyaXN0ZXI8YnI+DQo8ZGl2IGNsYXNzPSJIT0VuWmIiPg0K
PGRpdiBjbGFzcz0iaDUiPjxicj4NCjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fPGJyPg0KbW11c2ljIG1haWxpbmcgbGlzdDxicj4NCjxhIGhyZWY9
Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciPm1tdXNpY0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVm
PSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYyIgcmVsPSJub3Jl
ZmVycmVyIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9tbXVzaWM8L2E+PGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2
Pg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPg0KPC9ib2R5Pg0KPC9odG1s
Pg0K

--_000_D35A1FAC8533christerholmbergericssoncom_--


From nobody Thu May 12 02:18:42 2016
Return-Path: <kevindempsey70@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 7274E12D139 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 02:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HfGI4zm7J9_j for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 02:18:39 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2773C12D096 for <mmusic@ietf.org>; Thu, 12 May 2016 02:18:39 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id f66so89958803vkh.2 for <mmusic@ietf.org>; Thu, 12 May 2016 02:18:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=cNlDapSQGzKGllHbq+wXlAG10Qh6Fmwx0dPitLa4RS8=; b=gmbrOT4Fj+sYXCRZVAGoAifKYrqMXRQL/DuKCsKNKWACr2vWvDZNnW4bJg6Dp+z0dx 71jZ+THJ6mCuInzaA5G5uEYMS4GFZCWKFU4T1AC9FGKpPo2ILZdROYkQKN+Qc0SLsbEC fpvqDka4o+SLXKTD4yq+zNJOWFCDO6edvMswWwKmVCsp6G7R4iIcj4oNidFEvRvw/B0Z 80nt8p5DYkCv8QX0ru/4YWAhBrRet+5UCafAcI39G2fDQl0rjp9XGiphGzRHD4BQqwVy MIK8pRzO903VBGf0TdIs2mVNHvNtcJcLhGyx9F8YQMavEZMJBcd36rL3FhDdiL8fAVMq iA1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=cNlDapSQGzKGllHbq+wXlAG10Qh6Fmwx0dPitLa4RS8=; b=QxHeejo+aPaFu9aPL6nihYltDXlQVJA9vspgdrKt5SGnnIEW43CjYqkjFJ4+nKtcA4 iC98BzrW9DoldlhPWTmr/KUJ37XBKyb27vBD/cE24Y+vpxYNVySHyhX11lWnc/ySK4aV d+WH2DnQ9AX/dch5U627kuYNoKSS5KCQE3F5bA0xr8ueU13p2FPJNdx+6kQREN6cNRl7 HJczDipyptPYH8ySvEtckPyEFE3YMN9Bk2DSRfh6wtlHqGuaKd6yz/jk6QUkgRkRNaeJ NMES669JYGdgRH90yvqGYk6PTJ7sJr3fjhBEEUiqJlor5wS1A0lwtdHeogNKvvs1oBPl whbQ==
X-Gm-Message-State: AOPr4FUpTkJ3s1ND47DzdNwicg9wlsM2WVt70adbJY1mhpLWBIllZBIGQcpggrqPhvZjxteK9BfAjuj/icVlbw==
MIME-Version: 1.0
X-Received: by 10.176.2.50 with SMTP id 47mr4187825uas.45.1463044718154; Thu, 12 May 2016 02:18:38 -0700 (PDT)
Received: by 10.159.32.132 with HTTP; Thu, 12 May 2016 02:18:37 -0700 (PDT)
In-Reply-To: <D35A1FAC.8533%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com>
Date: Thu, 12 May 2016 10:18:37 +0100
Message-ID: <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com>
From: Kevin Dempsey <kevindempsey70@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11372416b75bb30532a1a4a5
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/JKx1I3-3sAiesqn6e5YS_xWcpGg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 09:18:41 -0000

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

For backwards compatibility you could still use the a=3Dfingerprint attribu=
te
as well. If there are a=3Dfingerprints and you understand them, then you'd
ignore a=3Dfingerprint lines.

On 12 May 2016 at 09:57, Christer Holmberg <christer.holmberg@ericsson.com>
wrote:

> Hi,
>
> >An alternative would be to provide some way to associate the fingerprint=
s
> of each certificate with each other. For example, replace multiple
> a=3Dfingerprint attributes with something like:
> >a=3Dfingerprints: hash1 AAAA, hash2 BBBBBBBB, hash3 CCCCCCCCCCCC
> >Then the requirement on the receiving side would be that the certificate
> must match at least one 'fingerprints' line. Which, and how many, of the
> hashes that are checked would depend on the receivers preferences.
>
> Correct.
>
> However, as that solution would not be backward compatible, the question
> is whether existing deployments today support multiple certificates. If
> not, then this could be an option.
>
> In cases where only a single certificate is offered, we could continue
> using the existing fingerprint attribute.
>
> Regards,
>
> Christer
>
>
>
>
> On 11 May 2016 at 15:06, Christer Holmberg <christer.holmberg@ericsson.co=
m
> > wrote:
>
>> Hi,
>>
>> ...
>> >>
>> >> Isn=C2=B9t that what the current text more or less says:
>> >>
>> >> "An endpoint MUST be able to match at least one of the received
>> >>      fingerprints, calculated using a hash algorithm that the endpoin=
t
>> >>      considers secure enough,=C2=B2
>> >
>> >The part we are not talking about here is what the sender must do. With
>> >the sort of algorithm Martin is talking about, if the intent is to cove=
r
>> >multiple certificates then every hash function used must be used for
>> >every certificate.
>>
>> Correct.
>>
>> >Whether that is a burden is debatable. If the
>> >matching algorithm requires that, then it must be a stated requirement
>> >on the sender.
>>
>> Correct.
>>
>> The question is whether such requirement would be harmful to the
>> RTP-and-RTCP-on-different-servers use-case.
>>
>> Regards,
>>
>> Christer
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
>

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

<div dir=3D"ltr">For backwards compatibility you could still use the a=3Dfi=
ngerprint attribute as well. If there are a=3Dfingerprints and you understa=
nd them, then you&#39;d ignore a=3Dfingerprint lines.</div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On 12 May 2016 at 09:57, Christer=
 Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsso=
n.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi,</div><span class=3D"">
<div><br>
</div>
<span>
<div>
<div>
<div dir=3D"ltr">&gt;An alternative would be to provide some way to associa=
te the fingerprints of each certificate with each other. For example, repla=
ce multiple a=3Dfingerprint attributes with something like:
<div>&gt;a=3Dfingerprints: hash1 AAAA, hash2 BBBBBBBB, hash3 CCCCCCCCCCCC</=
div>
<div>&gt;Then the requirement on the receiving side would be that the certi=
ficate must match at least one &#39;fingerprints&#39; line. Which, and how =
many, of the hashes that are checked would depend on the receivers preferen=
ces.</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>Correct.</div>
<div><br>
</div>
<div>However, as that solution would not be backward compatible, the questi=
on is whether existing deployments today support multiple certificates. If =
not, then this could be an option.</div>
<div><br>
</div>
<div>In cases where only a single certificate is offered, we could continue=
 using the existing fingerprint attribute.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div><span class=3D"">
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div>
<div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 11 May 2016 at 15:06, Christer Holmberg <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<br>
...<br>
<span>&gt;&gt;<br>
&gt;&gt; Isn=C2=B9t that what the current text more or less says:<br>
&gt;&gt;<br>
&gt;&gt; &quot;An endpoint MUST be able to match at least one of the receiv=
ed<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 fingerprints, calculated using a hash algorith=
m that the endpoint<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 considers secure enough,=C2=B2<br>
&gt;<br>
&gt;The part we are not talking about here is what the sender must do. With=
<br>
&gt;the sort of algorithm Martin is talking about, if the intent is to cove=
r<br>
&gt;multiple certificates then every hash function used must be used for<br=
>
&gt;every certificate.<br>
<br>
</span>Correct.<br>
<span><br>
&gt;Whether that is a burden is debatable. If the<br>
&gt;matching algorithm requires that, then it must be a stated requirement<=
br>
&gt;on the sender.<br>
<br>
</span>Correct.<br>
<br>
The question is whether such requirement would be harmful to the<br>
RTP-and-RTCP-on-different-servers use-case.<br>
<br>
Regards,<br>
<br>
Christer<br>
<div>
<div><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</span></div>

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

--001a11372416b75bb30532a1a4a5--


From nobody Thu May 12 02:21:21 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D3612D15B for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 02:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5_xrij-8---L for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 02:21:17 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB22112D145 for <mmusic@ietf.org>; Thu, 12 May 2016 02:21:16 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-ef-57344b0ad7b6
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 7F.CB.18043.A0B44375; Thu, 12 May 2016 11:21:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0248.002; Thu, 12 May 2016 11:21:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA
Date: Thu, 12 May 2016 09:21:13 +0000
Message-ID: <D35A25F7.8546%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com>
In-Reply-To: <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D35A25F78546christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrCIsWRmVeSWpSXmKPExsUyM2J7iC63t0m4wfwbnBY3579lsbh25h+j xdTlj1ksVmw4wOrA4vH3/Qcmj52z7rJ7LFnykymAOYrLJiU1J7MstUjfLoEr4+PZ80wFm30q Dl37xdbAuMCri5GTQ0LARGLKgyeMELaYxIV769m6GLk4hASOMEo0vXvNCOEsYZSYvuQBkMPB wSZgIdH9TxukQURAR+Lg/cnsIDazQJVE5/EXYLawgKfExkf7WCFqvCQuTF3ADmFPY5RoXyoM MoZFQFXi0ANHkDCvgJVE38cl7BCrbrFLPNmxnxkkwSkQKLFq1nGw4xiBjvt+ag0TxC5xiVtP 5jNBHC0gsWTPeWYIW1Ti5eN/YHtFBfQk9r04D3ayhICixPJ+OYjWeInWP5cYIfYKSpyc+YRl AqPYLCRTZyEpm4WkDCKuJfHlxz42CFtRYkr3Q/ZZQBuYBTQl3jyshTCtJW7Nc0ZWsYCRYxWj aHFqcXFuupGRXmpRZnJxcX6eXl5qySZGYNwe3PLbagfjweeOhxgFOBiVeHgXPDYOF2JNLCuu zD3EKMHBrCTCm+1iEi7Em5JYWZValB9fVJqTWnyIUZqDRUmc1/+lYriQQHpiSWp2ampBahFM lomDU6qB0dk8ryL4VmRdNPMZvYPTvXZuKz/7O5WvKuSbo4Oo8DG5i7c+P1f0+a04W2Dr5ljl 0w7aDYwSgbH/GG7ZL5p1j/OmzIr9xwQOVipK/awxq41aONOeNXrn5Wlu6aEvNavuN8qo5726 33crUFfbo+FH8xXtzXfMX7Zxxczb/+21YGPCwgx/4/2eSizFGYmGWsxFxYkApMxa8NcCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/yCxcgdAY4Ge8BFMQdfzbx0JoP9c>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 09:21:19 -0000

--_000_D35A25F78546christerholmbergericssoncom_
Content-Type: text/plain; charset="euc-kr"
Content-Transfer-Encoding: base64

SGksDQoNCj5Gb3IgYmFja3dhcmRzIGNvbXBhdGliaWxpdHkgeW91IGNvdWxkIHN0aWxsIHVzZSB0
aGUgYT1maW5nZXJwcmludCBhdHRyaWJ1dGUgYXMgd2VsbC4gSWYgdGhlcmUgYXJlIGE9ZmluZ2Vy
cHJpbnRzIGFuZCB5b3UgdW5kZXJzdGFuZCB0aGVtLCB0aGVuIHlvdSdkIGlnbm9yZSBhPWZpbmdl
cnByaW50IGxpbmVzLg0KDQpTdXJlLiBCdXQsIGFzIHRoZSBzZW5kZXIgZG9lc26hr3Qga25vdyB3
aGV0aGVyIHRoZSByZWNlaXZlciB3aWxsIHN1cHBvcnQgdGhlIG5ldyBhdHRyaWJ1dGUsIHdloa9k
IHN0aWxsIG5lZWQgcnVsZXMgYXNzb2NpYXRlZCB3aXRoIHRoZSB1c2FnZSBvZiB0aGUgZXhpc3Rp
bmcgZmluZ2VycHJpbnQuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg0KT24gMTIgTWF5IDIw
MTYgYXQgMDk6NTcsIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nv
bi5jb208bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KSGks
DQoNCj5BbiBhbHRlcm5hdGl2ZSB3b3VsZCBiZSB0byBwcm92aWRlIHNvbWUgd2F5IHRvIGFzc29j
aWF0ZSB0aGUgZmluZ2VycHJpbnRzIG9mIGVhY2ggY2VydGlmaWNhdGUgd2l0aCBlYWNoIG90aGVy
LiBGb3IgZXhhbXBsZSwgcmVwbGFjZSBtdWx0aXBsZSBhPWZpbmdlcnByaW50IGF0dHJpYnV0ZXMg
d2l0aCBzb21ldGhpbmcgbGlrZToNCj5hPWZpbmdlcnByaW50czogaGFzaDEgQUFBQSwgaGFzaDIg
QkJCQkJCQkIsIGhhc2gzIENDQ0NDQ0NDQ0NDQw0KPlRoZW4gdGhlIHJlcXVpcmVtZW50IG9uIHRo
ZSByZWNlaXZpbmcgc2lkZSB3b3VsZCBiZSB0aGF0IHRoZSBjZXJ0aWZpY2F0ZSBtdXN0IG1hdGNo
IGF0IGxlYXN0IG9uZSAnZmluZ2VycHJpbnRzJyBsaW5lLiBXaGljaCwgYW5kIGhvdyBtYW55LCBv
ZiB0aGUgaGFzaGVzIHRoYXQgYXJlIGNoZWNrZWQgd291bGQgZGVwZW5kIG9uIHRoZSByZWNlaXZl
cnMgcHJlZmVyZW5jZXMuDQoNCkNvcnJlY3QuDQoNCkhvd2V2ZXIsIGFzIHRoYXQgc29sdXRpb24g
d291bGQgbm90IGJlIGJhY2t3YXJkIGNvbXBhdGlibGUsIHRoZSBxdWVzdGlvbiBpcyB3aGV0aGVy
IGV4aXN0aW5nIGRlcGxveW1lbnRzIHRvZGF5IHN1cHBvcnQgbXVsdGlwbGUgY2VydGlmaWNhdGVz
LiBJZiBub3QsIHRoZW4gdGhpcyBjb3VsZCBiZSBhbiBvcHRpb24uDQoNCkluIGNhc2VzIHdoZXJl
IG9ubHkgYSBzaW5nbGUgY2VydGlmaWNhdGUgaXMgb2ZmZXJlZCwgd2UgY291bGQgY29udGludWUg
dXNpbmcgdGhlIGV4aXN0aW5nIGZpbmdlcnByaW50IGF0dHJpYnV0ZS4NCg0KUmVnYXJkcywNCg0K
Q2hyaXN0ZXINCg0KDQoNCg0KT24gMTEgTWF5IDIwMTYgYXQgMTU6MDYsIENocmlzdGVyIEhvbG1i
ZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208bWFpbHRvOmNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KSGksDQoNCi4uLg0KPj4NCj4+IElzbqn2dCB0aGF0
IHdoYXQgdGhlIGN1cnJlbnQgdGV4dCBtb3JlIG9yIGxlc3Mgc2F5czoNCj4+DQo+PiAiQW4gZW5k
cG9pbnQgTVVTVCBiZSBhYmxlIHRvIG1hdGNoIGF0IGxlYXN0IG9uZSBvZiB0aGUgcmVjZWl2ZWQN
Cj4+ICAgICAgZmluZ2VycHJpbnRzLCBjYWxjdWxhdGVkIHVzaW5nIGEgaGFzaCBhbGdvcml0aG0g
dGhhdCB0aGUgZW5kcG9pbnQNCj4+ICAgICAgY29uc2lkZXJzIHNlY3VyZSBlbm91Z2gsqfcNCj4N
Cj5UaGUgcGFydCB3ZSBhcmUgbm90IHRhbGtpbmcgYWJvdXQgaGVyZSBpcyB3aGF0IHRoZSBzZW5k
ZXIgbXVzdCBkby4gV2l0aA0KPnRoZSBzb3J0IG9mIGFsZ29yaXRobSBNYXJ0aW4gaXMgdGFsa2lu
ZyBhYm91dCwgaWYgdGhlIGludGVudCBpcyB0byBjb3Zlcg0KPm11bHRpcGxlIGNlcnRpZmljYXRl
cyB0aGVuIGV2ZXJ5IGhhc2ggZnVuY3Rpb24gdXNlZCBtdXN0IGJlIHVzZWQgZm9yDQo+ZXZlcnkg
Y2VydGlmaWNhdGUuDQoNCkNvcnJlY3QuDQoNCj5XaGV0aGVyIHRoYXQgaXMgYSBidXJkZW4gaXMg
ZGViYXRhYmxlLiBJZiB0aGUNCj5tYXRjaGluZyBhbGdvcml0aG0gcmVxdWlyZXMgdGhhdCwgdGhl
biBpdCBtdXN0IGJlIGEgc3RhdGVkIHJlcXVpcmVtZW50DQo+b24gdGhlIHNlbmRlci4NCg0KQ29y
cmVjdC4NCg0KVGhlIHF1ZXN0aW9uIGlzIHdoZXRoZXIgc3VjaCByZXF1aXJlbWVudCB3b3VsZCBi
ZSBoYXJtZnVsIHRvIHRoZQ0KUlRQLWFuZC1SVENQLW9uLWRpZmZlcmVudC1zZXJ2ZXJzIHVzZS1j
YXNlLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQptbXVzaWMgbWFpbGluZyBsaXN0DQptbXVzaWNAaWV0
Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vbW11c2ljDQoNCg0K

--_000_D35A25F78546christerholmbergericssoncom_
Content-Type: text/html; charset="euc-kr"
Content-ID: <8109D53032550D44AFDA854A250A8BE7@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PWV1Yy1rciI+DQo8L2hlYWQ+DQo8Ym9keSBzdHlsZT0id29yZC13
cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1i
cmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTog
MTRweDsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7Ij4NCjxkaXY+SGksPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxk
aXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+Jmd0O0ZvciBiYWNrd2FyZHMgY29tcGF0aWJpbGl0
eSB5b3UgY291bGQgc3RpbGwgdXNlIHRoZSBhPWZpbmdlcnByaW50IGF0dHJpYnV0ZSBhcyB3ZWxs
LiBJZiB0aGVyZSBhcmUgYT1maW5nZXJwcmludHMgYW5kIHlvdSB1bmRlcnN0YW5kIHRoZW0sIHRo
ZW4geW91J2QgaWdub3JlIGE9ZmluZ2VycHJpbnQgbGluZXMuPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+U3VyZS4gQnV0LCBhcyB0aGUgc2Vu
ZGVyIGRvZXNuoa90IGtub3cgd2hldGhlciB0aGUgcmVjZWl2ZXIgd2lsbCBzdXBwb3J0IHRoZSBu
ZXcgYXR0cmlidXRlLCB3ZaGvZCBzdGlsbCBuZWVkIHJ1bGVzIGFzc29jaWF0ZWQgd2l0aCB0aGUg
dXNhZ2Ugb2YgdGhlIGV4aXN0aW5nIGZpbmdlcnByaW50LjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxkaXY+UmVnYXJkcyw8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkNocmlzdGVy
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9O
Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxicj4NCjxkaXYgY2xh
c3M9ImdtYWlsX3F1b3RlIj5PbiAxMiBNYXkgMjAxNiBhdCAwOTo1NywgQ2hyaXN0ZXIgSG9sbWJl
cmcgPHNwYW4gZGlyPSJsdHIiPg0KJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVy
Z0Blcmljc3Nvbi5jb20iIHRhcmdldD0iX2JsYW5rIj5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nv
bi5jb208L2E+Jmd0Ozwvc3Bhbj4gd3JvdGU6PGJyPg0KPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWls
X3F1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29s
aWQ7cGFkZGluZy1sZWZ0OjFleCI+DQo8ZGl2IHN0eWxlPSJ3b3JkLXdyYXA6YnJlYWstd29yZDtj
b2xvcjpyZ2IoMCwwLDApO2ZvbnQtc2l6ZToxNHB4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1z
ZXJpZiI+DQo8ZGl2PkhpLDwvZGl2Pg0KPHNwYW4gY2xhc3M9IiI+DQo8ZGl2Pjxicj4NCjwvZGl2
Pg0KPHNwYW4+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgZGlyPSJsdHIiPiZndDtBbiBhbHRlcm5hdGl2
ZSB3b3VsZCBiZSB0byBwcm92aWRlIHNvbWUgd2F5IHRvIGFzc29jaWF0ZSB0aGUgZmluZ2VycHJp
bnRzIG9mIGVhY2ggY2VydGlmaWNhdGUgd2l0aCBlYWNoIG90aGVyLiBGb3IgZXhhbXBsZSwgcmVw
bGFjZSBtdWx0aXBsZSBhPWZpbmdlcnByaW50IGF0dHJpYnV0ZXMgd2l0aCBzb21ldGhpbmcgbGlr
ZToNCjxkaXY+Jmd0O2E9ZmluZ2VycHJpbnRzOiBoYXNoMSBBQUFBLCBoYXNoMiBCQkJCQkJCQiwg
aGFzaDMgQ0NDQ0NDQ0NDQ0NDPC9kaXY+DQo8ZGl2PiZndDtUaGVuIHRoZSByZXF1aXJlbWVudCBv
biB0aGUgcmVjZWl2aW5nIHNpZGUgd291bGQgYmUgdGhhdCB0aGUgY2VydGlmaWNhdGUgbXVzdCBt
YXRjaCBhdCBsZWFzdCBvbmUgJ2ZpbmdlcnByaW50cycgbGluZS4gV2hpY2gsIGFuZCBob3cgbWFu
eSwgb2YgdGhlIGhhc2hlcyB0aGF0IGFyZSBjaGVja2VkIHdvdWxkIGRlcGVuZCBvbiB0aGUgcmVj
ZWl2ZXJzIHByZWZlcmVuY2VzLjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFu
Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+Q29ycmVjdC48L2Rpdj4NCjxkaXY+
PGJyPg0KPC9kaXY+DQo8ZGl2Pkhvd2V2ZXIsIGFzIHRoYXQgc29sdXRpb24gd291bGQgbm90IGJl
IGJhY2t3YXJkIGNvbXBhdGlibGUsIHRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIGV4aXN0aW5nIGRl
cGxveW1lbnRzIHRvZGF5IHN1cHBvcnQgbXVsdGlwbGUgY2VydGlmaWNhdGVzLiBJZiBub3QsIHRo
ZW4gdGhpcyBjb3VsZCBiZSBhbiBvcHRpb24uPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRp
dj5JbiBjYXNlcyB3aGVyZSBvbmx5IGEgc2luZ2xlIGNlcnRpZmljYXRlIGlzIG9mZmVyZWQsIHdl
IGNvdWxkIGNvbnRpbnVlIHVzaW5nIHRoZSBleGlzdGluZyBmaW5nZXJwcmludCBhdHRyaWJ1dGUu
PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5SZWdhcmRzLDwvZGl2Pg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxkaXY+Q2hyaXN0ZXI8L2Rpdj4NCjxzcGFuIGNsYXNzPSIiPg0KPGRpdj48YnI+
DQo8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX2V4dHJhIj48YnI+DQo8ZGl2IGNsYXNzPSJn
bWFpbF9xdW90ZSI+T24gMTEgTWF5IDIwMTYgYXQgMTU6MDYsIENocmlzdGVyIEhvbG1iZXJnIDxz
cGFuIGRpcj0ibHRyIj4NCiZsdDs8YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJp
Y3Nzb24uY29tIiB0YXJnZXQ9Il9ibGFuayI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29t
PC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90
ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4O2JvcmRlci1sZWZ0OjFweCAjY2NjIHNvbGlkO3Bh
ZGRpbmctbGVmdDoxZXgiPg0KSGksPGJyPg0KPGJyPg0KLi4uPGJyPg0KPHNwYW4+Jmd0OyZndDs8
YnI+DQomZ3Q7Jmd0OyBJc26p9nQgdGhhdCB3aGF0IHRoZSBjdXJyZW50IHRleHQgbW9yZSBvciBs
ZXNzIHNheXM6PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyAmcXVvdDtBbiBlbmRwb2ludCBN
VVNUIGJlIGFibGUgdG8gbWF0Y2ggYXQgbGVhc3Qgb25lIG9mIHRoZSByZWNlaXZlZDxicj4NCiZn
dDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgZmluZ2VycHJpbnRzLCBjYWxjdWxhdGVkIHVzaW5n
IGEgaGFzaCBhbGdvcml0aG0gdGhhdCB0aGUgZW5kcG9pbnQ8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAm
bmJzcDsgJm5ic3A7IGNvbnNpZGVycyBzZWN1cmUgZW5vdWdoLKn3PGJyPg0KJmd0Ozxicj4NCiZn
dDtUaGUgcGFydCB3ZSBhcmUgbm90IHRhbGtpbmcgYWJvdXQgaGVyZSBpcyB3aGF0IHRoZSBzZW5k
ZXIgbXVzdCBkby4gV2l0aDxicj4NCiZndDt0aGUgc29ydCBvZiBhbGdvcml0aG0gTWFydGluIGlz
IHRhbGtpbmcgYWJvdXQsIGlmIHRoZSBpbnRlbnQgaXMgdG8gY292ZXI8YnI+DQomZ3Q7bXVsdGlw
bGUgY2VydGlmaWNhdGVzIHRoZW4gZXZlcnkgaGFzaCBmdW5jdGlvbiB1c2VkIG11c3QgYmUgdXNl
ZCBmb3I8YnI+DQomZ3Q7ZXZlcnkgY2VydGlmaWNhdGUuPGJyPg0KPGJyPg0KPC9zcGFuPkNvcnJl
Y3QuPGJyPg0KPHNwYW4+PGJyPg0KJmd0O1doZXRoZXIgdGhhdCBpcyBhIGJ1cmRlbiBpcyBkZWJh
dGFibGUuIElmIHRoZTxicj4NCiZndDttYXRjaGluZyBhbGdvcml0aG0gcmVxdWlyZXMgdGhhdCwg
dGhlbiBpdCBtdXN0IGJlIGEgc3RhdGVkIHJlcXVpcmVtZW50PGJyPg0KJmd0O29uIHRoZSBzZW5k
ZXIuPGJyPg0KPGJyPg0KPC9zcGFuPkNvcnJlY3QuPGJyPg0KPGJyPg0KVGhlIHF1ZXN0aW9uIGlz
IHdoZXRoZXIgc3VjaCByZXF1aXJlbWVudCB3b3VsZCBiZSBoYXJtZnVsIHRvIHRoZTxicj4NClJU
UC1hbmQtUlRDUC1vbi1kaWZmZXJlbnQtc2VydmVycyB1c2UtY2FzZS48YnI+DQo8YnI+DQpSZWdh
cmRzLDxicj4NCjxicj4NCkNocmlzdGVyPGJyPg0KPGRpdj4NCjxkaXY+PGJyPg0KPGJyPg0KX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQptbXVzaWMg
bWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPm1tdXNpY0BpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYyIgcmVsPSJub3JlZmVycmVyIiB0YXJnZXQ9
Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWM8L2E+
PGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPjwvc3Bhbj48L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwv
ZGl2Pg0KPGJyPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_D35A25F78546christerholmbergericssoncom_--


From nobody Thu May 12 02:44:36 2016
Return-Path: <kevindempsey70@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 7629712D87F for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 02:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-yrUVwrr8YP for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 02:44:32 -0700 (PDT)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB0A512D87B for <mmusic@ietf.org>; Thu, 12 May 2016 02:44:31 -0700 (PDT)
Received: by mail-vk0-x232.google.com with SMTP id o133so90649404vka.0 for <mmusic@ietf.org>; Thu, 12 May 2016 02:44:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=wyaWAlCr9ibLGycFC+0hY5nXtF9D/SZsu8/0l6Iej0w=; b=nNpQ3pnW/JI7PGyBXVuMaFkcR82zFoW73q66+4u40Zu3K8hylLtO353er/EJdIT69d Ap8+aI/50XYQYGbRm45xr/lTRXk8zCuCI7745+Icm86JuXABm4qceXbH5WUEKXcZDGf8 ZmFfLisbzrudPJjSHqg2MX7l9liHbE/OLKHq0P796l1njGpgfx44ju+hz+P0JYYXpxKr jo5lbS8PYpMTgT+zqBtnFLQuYGA08e0Remf4+UwOBLxZIwt5dogZXlWvc0I+K2kn10xu JkRUC3QTiz2l5foX6NEVHJUDOVrP+VLDLqRjd76eMfaaSnPuZhWRMazcWLzlxbaDFxHs FkRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=wyaWAlCr9ibLGycFC+0hY5nXtF9D/SZsu8/0l6Iej0w=; b=XsoD8KOWAxxubEPGp8QCbaOMaVZjqOxTG7njzPgV6xadmJ9GCKji/MEOQA9wiU+X7H nMOHEWuO19gYE5DDqGCPAlU1239FrhkIfm9/4f6PQYYyGUTIUZhu4nYyNljkQa9TywVw Cy2vq75dJrpApQMl+xG8mgXl/dEnvlIue/rH4Qr9jnkaRY8su3d8ezhuR6K0ioC2PW4P Wt2gUMq/djflCC2dfmPKIVrmyRnjPEpWzt1A/jJMJFNmsIdM7YqgfPAB0icB98yboTos 6o/8GnlUc2kadcP5M1MNpuhzbsMKkv2pRMU8UZDRm3qBeq64Ul0cE/AyodtaBp6yKrE5 yz4w==
X-Gm-Message-State: AOPr4FUVuYTO7AUlh58yAfyrcQ2z9J8qXZXE4mxihCcqMYtpwfbAA2S9Sm6RVV9S6Mxv23YlrDV9WNP9aJduyg==
MIME-Version: 1.0
X-Received: by 10.176.2.50 with SMTP id 47mr4236372uas.45.1463046270951; Thu, 12 May 2016 02:44:30 -0700 (PDT)
Received: by 10.159.32.132 with HTTP; Thu, 12 May 2016 02:44:30 -0700 (PDT)
In-Reply-To: <D35A25F7.8546%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com>
Date: Thu, 12 May 2016 10:44:30 +0100
Message-ID: <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com>
From: Kevin Dempsey <kevindempsey70@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11372416452a450532a2016b
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/s4ETQdVu29gMJ9C8fxCd6Lck_Ek>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 09:44:34 -0000

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

The existing fingerprint attribute would keep the original requirement of
using the same hash as the certificate. So there would be only one
fingerprint line per certificate.

For hash agility, you'd use the new attribute. I think that makes it much
simpler.

On 12 May 2016 at 10:21, Christer Holmberg <christer.holmberg@ericsson.com>
wrote:

> Hi,
>
> >For backwards compatibility you could still use the a=3Dfingerprint
> attribute as well. If there are a=3Dfingerprints and you understand them,
> then you'd ignore a=3Dfingerprint lines.
>
> Sure. But, as the sender doesn=E2=80=99t know whether the receiver will s=
upport
> the new attribute, we=E2=80=99d still need rules associated with the usag=
e of the
> existing fingerprint.
>
> Regards,
>
> Christer
>
>
> On 12 May 2016 at 09:57, Christer Holmberg <christer.holmberg@ericsson.co=
m
> > wrote:
>
>> Hi,
>>
>> >An alternative would be to provide some way to associate the
>> fingerprints of each certificate with each other. For example, replace
>> multiple a=3Dfingerprint attributes with something like:
>> >a=3Dfingerprints: hash1 AAAA, hash2 BBBBBBBB, hash3 CCCCCCCCCCCC
>> >Then the requirement on the receiving side would be that the certificat=
e
>> must match at least one 'fingerprints' line. Which, and how many, of the
>> hashes that are checked would depend on the receivers preferences.
>>
>> Correct.
>>
>> However, as that solution would not be backward compatible, the question
>> is whether existing deployments today support multiple certificates. If
>> not, then this could be an option.
>>
>> In cases where only a single certificate is offered, we could continue
>> using the existing fingerprint attribute.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>>
>> On 11 May 2016 at 15:06, Christer Holmberg <
>> christer.holmberg@ericsson.com> wrote:
>>
>>> Hi,
>>>
>>> ...
>>> >>
>>> >> Isn=C2=B9t that what the current text more or less says:
>>> >>
>>> >> "An endpoint MUST be able to match at least one of the received
>>> >>      fingerprints, calculated using a hash algorithm that the endpoi=
nt
>>> >>      considers secure enough,=C2=B2
>>> >
>>> >The part we are not talking about here is what the sender must do. Wit=
h
>>> >the sort of algorithm Martin is talking about, if the intent is to cov=
er
>>> >multiple certificates then every hash function used must be used for
>>> >every certificate.
>>>
>>> Correct.
>>>
>>> >Whether that is a burden is debatable. If the
>>> >matching algorithm requires that, then it must be a stated requirement
>>> >on the sender.
>>>
>>> Correct.
>>>
>>> The question is whether such requirement would be harmful to the
>>> RTP-and-RTCP-on-different-servers use-case.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>>
>>
>

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

<div dir=3D"ltr">The existing fingerprint attribute would keep the original=
 requirement of using the same hash as the certificate. So there would be o=
nly one fingerprint line per certificate.<div><br></div><div>For hash agili=
ty, you&#39;d use the new attribute. I think that makes it much simpler.</d=
iv></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 12 Ma=
y 2016 at 10:21, Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:=
christer.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsso=
n.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi,</div><span class=3D"">
<div><br>
</div>
<span>
<div>
<div>
<div dir=3D"ltr">&gt;For backwards compatibility you could still use the a=
=3Dfingerprint attribute as well. If there are a=3Dfingerprints and you und=
erstand them, then you&#39;d ignore a=3Dfingerprint lines.</div>
</div>
</div>
</span>
<div><br>
</div>
</span><div>Sure. But, as the sender doesn=E2=80=99t know whether the recei=
ver will support the new attribute, we=E2=80=99d still need rules associate=
d with the usage of the existing fingerprint.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div><div><div class=3D"h5">
<div><br>
</div>
<span>
<div>
<div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 12 May 2016 at 09:57, Christer Holmberg <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>Hi,</div>
<span>
<div><br>
</div>
<span>
<div>
<div>
<div dir=3D"ltr">&gt;An alternative would be to provide some way to associa=
te the fingerprints of each certificate with each other. For example, repla=
ce multiple a=3Dfingerprint attributes with something like:
<div>&gt;a=3Dfingerprints: hash1 AAAA, hash2 BBBBBBBB, hash3 CCCCCCCCCCCC</=
div>
<div>&gt;Then the requirement on the receiving side would be that the certi=
ficate must match at least one &#39;fingerprints&#39; line. Which, and how =
many, of the hashes that are checked would depend on the receivers preferen=
ces.</div>
</div>
</div>
</div>
</span>
<div><br>
</div>
</span>
<div>Correct.</div>
<div><br>
</div>
<div>However, as that solution would not be backward compatible, the questi=
on is whether existing deployments today support multiple certificates. If =
not, then this could be an option.</div>
<div><br>
</div>
<div>In cases where only a single certificate is offered, we could continue=
 using the existing fingerprint attribute.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<span>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div>
<div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 11 May 2016 at 15:06, Christer Holmberg <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<br>
...<br>
<span>&gt;&gt;<br>
&gt;&gt; Isn=C2=B9t that what the current text more or less says:<br>
&gt;&gt;<br>
&gt;&gt; &quot;An endpoint MUST be able to match at least one of the receiv=
ed<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 fingerprints, calculated using a hash algorith=
m that the endpoint<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 considers secure enough,=C2=B2<br>
&gt;<br>
&gt;The part we are not talking about here is what the sender must do. With=
<br>
&gt;the sort of algorithm Martin is talking about, if the intent is to cove=
r<br>
&gt;multiple certificates then every hash function used must be used for<br=
>
&gt;every certificate.<br>
<br>
</span>Correct.<br>
<span><br>
&gt;Whether that is a burden is debatable. If the<br>
&gt;matching algorithm requires that, then it must be a stated requirement<=
br>
&gt;on the sender.<br>
<br>
</span>Correct.<br>
<br>
The question is whether such requirement would be harmful to the<br>
RTP-and-RTCP-on-different-servers use-case.<br>
<br>
Regards,<br>
<br>
Christer<br>
<div>
<div><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</div></div></div>

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

--001a11372416452a450532a2016b--


From nobody Thu May 12 03:27:43 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB6C12DA14 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 03:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPyKd1u31pSc for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 03:27:36 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C88F12D55F for <mmusic@ietf.org>; Thu, 12 May 2016 03:25:16 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id 190so88979173iow.1 for <mmusic@ietf.org>; Thu, 12 May 2016 03:25:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=985xtLF0jJzvwGJpQUN3EfiuxDHylIzlS2JXUadtgP8=; b=DddOeZ/SPwfpVh3TUx00nfpRRx8rNCq5rYEIaPVWhk/mPqm6ObHnA0YcN6GrqxL8h+ naY59CMLD+42Z/RykN11Sg6m3ztrJaoeiFrSsUB2qW0f97Yd87R7Qu5Nj23crfRu2Cnx AEmWDByriBq6HifAbc+aOEhv87DyACihIMzDOS9hQLJVxlHKlpItuyrNQsip+IpKIwv2 DFUt93Iezi9RNpt/V08sEQ5VxyhF7YzAOLcutNPeBPhh0G9vxdZ/h72UiytBSKbbykWN RuTNzKKny55HMZg5GPEievu7rAJjbkBeqcN/Eo7iUnBvDfK6QMth0VEAoTuZS5it5ddL 7rzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=985xtLF0jJzvwGJpQUN3EfiuxDHylIzlS2JXUadtgP8=; b=AXHs77H6T9YJXhpRC2UQZHt5CNgT8W+qAsU6GwxcozhV4OYZhEhg/ODPiDroCTV9iJ GEiVQt4xhhLoXrcQtrlbkVm5M/mOdeaP5FtDnt1ERUJV+/qZsTQauPL+erFF28Xv+qoJ 3rfiMWXYO63rb5z2RoaNPdGlM9N9eFH1AMr2RhcpgNfmLrM8hFhTFj9fbsFXmrrFClqH jtQ71vsmnuEjKNGaqSko+KRv8VgMVeXNP8nUSw/of1QNwgOwHUXWZBDPFJioq6NA9YDZ ll/DBU2w0asgTcYwLa0aymEojYiErN+yoz/weCsNThO37pnWq1qOQvrcyFLCnf0MqzgG Ppag==
X-Gm-Message-State: AOPr4FXTaYdS6Wafy5PCcpppedk+gHCc2Bp1YmnI7UbbRn3TSXXoKclF7Wd0kM8u02PHJUOFDQ3Z8SedB2OHPQ==
MIME-Version: 1.0
X-Received: by 10.107.161.140 with SMTP id k134mr7204530ioe.190.1463048715439;  Thu, 12 May 2016 03:25:15 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Thu, 12 May 2016 03:25:15 -0700 (PDT)
In-Reply-To: <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com>
Date: Thu, 12 May 2016 20:25:15 +1000
Message-ID: <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1mWtGJgwo21QiPZ6uwG3S1vOVcc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 10:27:42 -0000

On 12 May 2016 at 19:44, Kevin Dempsey <kevindempsey70@gmail.com> wrote:
> For hash agility, you'd use the new attribute. I think that makes it much
> simpler.


We could fix the stupid syntax at the same time.  Backwards
compatibility is for the weak:

a=fp:<name>=<base64url-value>;<name>=<base64>

Each line is a single certificate with as many hash functions as you please.


From nobody Thu May 12 03:50:17 2016
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704B712D195; Thu, 12 May 2016 03:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOwUeM2gdp3C; Thu, 12 May 2016 03:50:14 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [46.235.227.24]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96B9712D5E5; Thu, 12 May 2016 03:50:14 -0700 (PDT)
Received: from [130.209.254.9] (port=58915 helo=vpn9.dcs.gla.ac.uk) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1b0oC4-0006X8-05; Thu, 12 May 2016 11:50:12 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <90408933-ab1d-8636-9dfb-1b75443a04b8@cisco.com>
Date: Thu, 12 May 2016 10:02:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A630CB4-778A-4E39-B4E5-59B7E39DF351@csperkins.org>
References: <90408933-ab1d-8636-9dfb-1b75443a04b8@cisco.com>
To: Flemming Andreasen <fandreas@cisco.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/c_a5rfHEM14QyFrFfzmdMc-7Kfk>
Cc: mmusic <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 10:50:16 -0000

Flemming,

> On 29 Apr 2016, at 19:32, Flemming Andreasen <fandreas@cisco.com> =
wrote:
>=20
> This is to announce a 2 week Working Last Call for
>=20
>    draft-ietf-mmusic-sdp-bundle-negotiation-29
>=20
> as Proposed Standard. Please note that we previously issued a WGLC on =
the -22 version (in June 2015), however, since there has been various =
updates since then, we want to give people a chance to properly review =
the current version one last time (hopefully).
>=20
> Please review and provide any comments you may have on the document by =
Friday, May 13, 2016. Comments should be sent to the document authors =
and the MMUSIC WG list. If you review the document but do not have any =
comments, please send a note to that effect as well.

One minor comment:

- Section 10.1.1: the last paragraph of this section notes that =E2=80=9Co=
nce an SSRC has left the RTP session (by sending an RTCP BYE packet), =
that SSRC value can later be reused=E2=80=9D. I agree, but this needs to =
also specify the time period for =E2=80=9Clater=E2=80=9D, so that the =
SSRC has timed out if the RTCP BYE was lost. I suggest this sentence is =
changed to =E2=80=9Conce an SSRC has left the RTP session (by sending an =
RTCP BYE packet), that SSRC can be reused after a delay of 5 RTCP =
reporting intervals (the delay is to ensure the SSRC has timed out, in =
case the RTCP BYE packet was lost, see [RFC3550] section 6.3.5)=E2=80=9D.

Cheers,
Colin



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





From nobody Thu May 12 04:21:34 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 771EA12D659; Thu, 12 May 2016 04:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tcc5uHrcQb9J; Thu, 12 May 2016 04:21:30 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8831912D65C; Thu, 12 May 2016 04:21:29 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-63-573467377e54
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E4.81.12926.73764375; Thu, 12 May 2016 13:21:27 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0248.002; Thu, 12 May 2016 13:21:23 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>, Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29
Thread-Index: AQHRokV1UogGos41jEypb/mBLiYWPp+08+EAgABZtoA=
Date: Thu, 12 May 2016 11:21:22 +0000
Message-ID: <D35A41D7.8579%christer.holmberg@ericsson.com>
References: <90408933-ab1d-8636-9dfb-1b75443a04b8@cisco.com> <1A630CB4-778A-4E39-B4E5-59B7E39DF351@csperkins.org>
In-Reply-To: <1A630CB4-778A-4E39-B4E5-59B7E39DF351@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4F1B4C78689F074AAFD0D5E759E00AB0@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBIsWRmVeSWpSXmKPExsUyM2K7k655ukm4webtahbLX55gtJg+6x2b xfsLuhZTlz9mcWDxmPJ7I6vHtPv32TyWLPnJFMAcxWWTkpqTWZZapG+XwJVx4dQR5oKv3BVH 711gamDcy9nFyMkhIWAicfp0MxOELSZx4d56ti5GLg4hgSOMEo8mn2aGcJYwSrxeNZ+9i5GD g03AQqL7nzZIg4iAn0R7ywawBmaBTkaJTZcnMoIkhAW8JA7vOc0CUeQt8fnfRCjbSuJH9wVm EJtFQFXic+tDdhCbFyj+9OMrVhBbSKBY4t+Zg2A2p4CjxJXTS8B6GYGu+35qDdilzALiEree zIe6WkBiyZ7zzBC2qMTLx//AekUF9CT2vTjPCHKzhICixPJ+OYhWPYkbU6ewgYSZBawlpv6I hAhrSyxb+JoZ4hpBiZMzn7BMYJSYhWTZLCTdsxC6ZyHpnoWkewEj6ypG0eLU4qTcdCNjvdSi zOTi4vw8vbzUkk2MwPg8uOW36g7Gy28cDzEKcDAq8fAueGwcLsSaWFZcmXuIUYKDWUmE93Wq SbgQb0piZVVqUX58UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGxrDJO/MD m703H2R/1Dpr8kzFjQ7fPKZpPdYNfPf5iKVltNp5QzHhHjmH4yeNWdiOsXW9fLFtN691w8I7 N+Y8buG8zhK+JIQ3ifthrZRnZN+tmYJfdnUfyNHgnmeU9equ5akzRxSyn913bdJam8dXE+Zc YTFlW77Yxrlc55bx32ho9/Kcl5e0XomlOCPRUIu5qDgRAE4Cus/LAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/O7JwTWPoBmMbWeRyGCBQusYmsy8>
Cc: mmusic <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 11:21:33 -0000

Hi Colin,


>> On 29 Apr 2016, at 19:32, Flemming Andreasen <fandreas@cisco.com> wrote:
>>=20
>> This is to announce a 2 week Working Last Call for
>>=20
>>    draft-ietf-mmusic-sdp-bundle-negotiation-29
>>=20
>> as Proposed Standard. Please note that we previously issued a WGLC on
>>the -22 version (in June 2015), however, since there has been various
>>updates since then, we want to give people a chance to properly review
>>the current version one last time (hopefully).
>>=20
>> Please review and provide any comments you may have on the document by
>>Friday, May 13, 2016. Comments should be sent to the document authors
>>and the MMUSIC WG list. If you review the document but do not have any
>>comments, please send a note to that effect as well.
>
>One minor comment:
>
>- Section 10.1.1: the last paragraph of this section notes that =B3once an
>SSRC has left the RTP session (by sending an RTCP BYE packet), that SSRC
>value can later be reused=B2. I agree, but this needs to also specify the
>time period for =B3later=B2, so that the SSRC has timed out if the RTCP BY=
E
>was lost. I suggest this sentence is changed to =B3once an SSRC has left
>the RTP session (by sending an RTCP BYE packet), that SSRC can be reused
>after a delay of 5 RTCP reporting intervals (the delay is to ensure the
>SSRC has timed out, in case the RTCP BYE packet was lost, see [RFC3550]
>section 6.3.5)=B2.


I am ok with your suggestion. Anyone has any issues?

Thanks!

Regards,

Christer


From nobody Thu May 12 04:24:29 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF5912D950 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 04:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibFZlhzQxsOM for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 04:24:25 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AFC412D952 for <mmusic@ietf.org>; Thu, 12 May 2016 04:24:25 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-28-573467e7d35b
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 2F.05.27088.7E764375; Thu, 12 May 2016 13:24:23 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0248.002; Thu, 12 May 2016 13:24:18 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAAQ1QA
Date: Thu, 12 May 2016 11:24:17 +0000
Message-ID: <D35A4276.857F%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
In-Reply-To: <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <909190D476C4654480B8B60DCA12D28F@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLIsWRmVeSWpSXmKPExsUyM2K7tO7zdJNwg0XtVhY3579lsbh25h+j xdTlj1ksVmw4wOrA4vH3/Qcmj52z7rJ7LFnykymAOYrLJiU1J7MstUjfLoEro2/aH6aCaywV 1/71szYwPmLuYuTkkBAwkdgzuZ8FwhaTuHBvPVsXIxeHkMARRonDDy9DOUsYJa5vfQDkcHCw CVhIdP/TBmkQEYiUOPj+NiuIzSzgK/FywRewocICnhIbH+1jhajxkrgwdQE7yBwRgVWMEo/O X2ICSbAIqErceHgczOYVsJL4PmkeC8SymZwSb/60s4MkOAUCJV4f/wh2HiPQed9PrWGC2CYu cevJfCaIswUkluw5D/WOqMTLx//ANosK6Ense3GeESKuKHF1+nKoXh2JBbs/sUHY1hJ3ni9j hLC1JZYtfM0McZCgxMmZT1gmMErMQrJuFpL2WUjaZyFpn4WkfQEj6ypG0eLU4qTcdCMjvdSi zOTi4vw8vbzUkk2MwEg9uOW3wQ7Gl88dDzEKcDAq8fAueGwcLsSaWFZcmXuIUYKDWUmE91ea SbgQb0piZVVqUX58UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGxsjzEsvn /Hr6QKIkZe6XdWImzIXperXTjLMXx1ScfaA1/Z6vq4rcAoF+by/VE/bBbK/KvwrtjmYwX3Lp U8Kp9BKxfsHKVy6HZTx/aW7U81Qpi7VbW1VueP2A+eLEedIOc0s9v58sy3VMVWfeOOlJygPR t/PU27XfPf7sPfH1ZNe8xXFSK0OrlFiKMxINtZiLihMBF2a6V9ACAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/06uw_kjyO-TscE74lRxZnZJVnbY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 11:24:28 -0000

Hi,

Within the attribute, what value would you use to reference the
certificate?

Regards,

Christer

On 12/05/16 13:25, "Martin Thomson" <martin.thomson@gmail.com> wrote:

>On 12 May 2016 at 19:44, Kevin Dempsey <kevindempsey70@gmail.com> wrote:
>> For hash agility, you'd use the new attribute. I think that makes it
>>much
>> simpler.
>
>
>We could fix the stupid syntax at the same time.  Backwards
>compatibility is for the weak:
>
>a=3Dfp:<name>=3D<base64url-value>;<name>=3D<base64>
>
>Each line is a single certificate with as many hash functions as you
>please.


From nobody Thu May 12 08:02:06 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747EC12D6A7 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 08:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ez7ROytuguX9 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 08:01:57 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9088812D6C8 for <mmusic@ietf.org>; Thu, 12 May 2016 08:01:06 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-a9-57349ab0da9d
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id FF.66.18043.0BA94375; Thu, 12 May 2016 17:01:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0248.002; Thu, 12 May 2016 17:01:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgP//kdyA
Date: Thu, 12 May 2016 15:01:02 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FA140B@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
In-Reply-To: <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2K7ou6GWSbhBlebtC1uzn/LYnHtzD9G i6nLH7NYrNhwgNWBxePv+w9MHjtn3WX3WLLkJ1MAcxSXTUpqTmZZapG+XQJXxtOvv5gLJvBU HL3wlqmB8QV3FyMnh4SAicSczVeZIWwxiQv31rN1MXJxCAkcYZRYPOsIO4SzhFFixq+/rF2M HBxsAhYS3f+0QRpEBCIlDr6/zQpiMwv4Srxc8AVskLCAp8T105/ZIGq8JC5MXQA2R0RgFaPE kr27mUASLAKqEmum7ABr4AVqfrv1IzPEspmcEnsuXAWbyikQKPH6+EcWEJsR6Lzvp9YwQWwT l7j1ZD4TxNkCEkv2nId6QVTi5eN/rBC2kkTjkidgRzMLaEqs36UP0aooMaX7ITvEXkGJkzOf sExgFJuFZOoshI5ZSDpmIelYwMiyilG0OLW4ODfdyEgvtSgzubg4P08vL7VkEyMwug5u+W21 g/Hgc8dDjAIcjEo8vAseG4cLsSaWFVfmHmKU4GBWEuF1m2oSLsSbklhZlVqUH19UmpNafIhR moNFSZzX/6ViuJBAemJJanZqakFqEUyWiYNTqoHR+R1r5K7SDIU/rV5Mdu9ObpjuskIt/8ED pitL14szHfczYvq/8ag1x9bMwx+qJ1peqS3feMam13lV0sNCmSUXSg/f91vzx8ty9aMykYNJ R3uf7bvTqPN4xd1aHWPmv1NmCuufrGncsf1g9kxtJ+3uvOkWa1a8WmIaJ11acT3/5IrIkp1u c6UXKbEUZyQaajEXFScCAEe1m3SqAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/nPH62dV9SAfsrJlnIvLOnV5rXUg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 15:02:05 -0000

SGksDQoNCk9uZSB0aGluZyB0byByZW1lbWJlciwgaWYgd2UgZGVmaW5lIGEgbmV3IGF0dHJpYnV0
ZSwgYW5kIGNsYXJpZnkgdGhhdCBvbmx5IG9uZSBpbnN0YW5jZSBvZiB0aGUgZXhpc3RpbmcgZmlu
Z2VycHJpbnQgYXR0cmlidXRlIGlzIGFsbG93ZWQsIGlzIHRoYXQgaXQgbWF5IGhhdmUgaW1wYWN0
IG9uIG90aGVyIHNwZWNpZmljYXRpb25zLg0KDQpBdCBsZWFzdCBydGN3ZWItc2VjdXJpdHktb3Zl
cnZpZXcgdGFsa3MgYWJvdXQgdXNhZ2Ugb2YgbXVsdGlwbGUgZmluZ2VycHJpbnQgYXR0cmlidXRl
cy4gU28sIHRoYXQgdGV4dCBzaG91bGQgYmUgbW9kaWZpZWQgYW5kIHRhbGsgYWJvdXQgbXVsdGlw
bGUgbmV3LWZpbmdlcnByaW50IGF0dHJpYnV0ZXMuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBNYXJ0aW4gVGhvbXNvbiBbbWFpbHRv
Om1hcnRpbi50aG9tc29uQGdtYWlsLmNvbV0gDQpTZW50OiAxMiBNYXkgMjAxNiAxMzoyNQ0KVG86
IEtldmluIERlbXBzZXkgPGtldmluZGVtcHNleTcwQGdtYWlsLmNvbT4NCkNjOiBDaHJpc3RlciBI
b2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPjsgUGF1bCBLeXppdmF0IDxw
a3l6aXZhdEBhbHVtLm1pdC5lZHU+OyBtbXVzaWNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbTU1V
U0lDXSBEcmFmdCBuZXcgdmVyc2lvbjogZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUtMDEN
Cg0KT24gMTIgTWF5IDIwMTYgYXQgMTk6NDQsIEtldmluIERlbXBzZXkgPGtldmluZGVtcHNleTcw
QGdtYWlsLmNvbT4gd3JvdGU6DQo+IEZvciBoYXNoIGFnaWxpdHksIHlvdSdkIHVzZSB0aGUgbmV3
IGF0dHJpYnV0ZS4gSSB0aGluayB0aGF0IG1ha2VzIGl0IA0KPiBtdWNoIHNpbXBsZXIuDQoNCg0K
V2UgY291bGQgZml4IHRoZSBzdHVwaWQgc3ludGF4IGF0IHRoZSBzYW1lIHRpbWUuICBCYWNrd2Fy
ZHMgY29tcGF0aWJpbGl0eSBpcyBmb3IgdGhlIHdlYWs6DQoNCmE9ZnA6PG5hbWU+PTxiYXNlNjR1
cmwtdmFsdWU+OzxuYW1lPj08YmFzZTY0Pg0KDQpFYWNoIGxpbmUgaXMgYSBzaW5nbGUgY2VydGlm
aWNhdGUgd2l0aCBhcyBtYW55IGhhc2ggZnVuY3Rpb25zIGFzIHlvdSBwbGVhc2UuDQo=


From nobody Thu May 12 10:01:50 2016
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A57412D606 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 10:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 dhCj7Wwu5RQD for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 10:01:47 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13A7712B04D for <mmusic@ietf.org>; Thu, 12 May 2016 10:01:47 -0700 (PDT)
Received: from [193.43.158.229] (port=60763 helo=[10.242.220.33]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1b0tzc-0007aY-94; Thu, 12 May 2016 18:01:45 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7732AC53-DCF8-4FD1-9EA2-0CB27FA3A6A2@nostrum.com>
Date: Thu, 12 May 2016 19:01:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B7BDC47B-D091-402C-9148-7F83CD0227B2@csperkins.org>
References: <BBE9739C2C302046BD34B42713A1E2A22E874B3B@ESESSMB105.ericsson.se> <7732AC53-DCF8-4FD1-9EA2-0CB27FA3A6A2@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/yj9UnOVqdqM-D8037JnWvx3E65k>
Cc: mmusic <mmusic@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: [MMUSIC] 3GPP liaison statement to IETF MMUSIC
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 17:01:49 -0000

Bo, Ben,

I=E2=80=99ve revised this liaison statement, and the attached 3GPP TR =
26.924 V13.0.0, at the chair=E2=80=99s request. I do not follow the work =
in 3GPP closely, but I understand that SDP attribute-based approaches, =
such as solutions D and F in the TR, are being considered for further =
development.=20

Of the alternatives proposed, I believe that use of an SDP attribute =
(i.e., an =E2=80=9Ca=3D=E2=80=9D line) is to be preferred over use of =
further extensions to SDP =E2=80=9Cb=3D=E2=80=9C lines. Attributes are =
the natural extension point for SDP, and offer flexibility that is not =
present in =E2=80=9Cb=3D=E2=80=9C lines. This is compatible with the =
solutions proposed by 3GPP.

Whether any new attribute is signalled per RTP payload type, as in =
solution D, or per m=3D line, as in solution F, is a more complex issue. =
Neither seems unreasonable on the surface, and a QoS attribute per =
=E2=80=9Cm=3D=E2=80=9C line is natural if each =E2=80=9Cm=3D=E2=80=9C =
line represents a single media sent on a single port, with the =
offer/answer exchange being used only to select what encoding is used =
for that media.=20

However, with the definition and widespread adoption of the SDP BUNDLE =
extension, the assumption that a single =E2=80=9Cm=3D=E2=80=9C line =
represents a single type of media being sent on a single UDP port is =
becoming less tenable. I would urge 3GPP to consider the impact of the =
BUNDLE extension on their choice, and to further coordinate with IETF to =
ensure that whatever is developed is compatible with SDP sessions where =
multiple =E2=80=9Cm=3D=E2=80=9C lines, representing several different =
types of media, are sent on a single UDP port.=20

Colin



> On 1 Dec 2015, at 21:25, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Does anyone have thoughts on this?
>=20
> Thanks!
>=20
> Ben.
>=20
> On 16 Nov 2015, at 4:26, Bo Burman wrote:
>=20
>> MMUSIC members,
>>=20
>> We have received a liaison statement from the 3GPP TSG SA WG4 group.
>>=20
>> Briefly summarizing the attached document, they have been studying =
resource allocation at session setup and have found lack of bandwidth =
information elements and lack of end-to-end alignment that can result in =
inconsistent setting of QoS parameters in 3GPP networks. They have also =
documented the problem analysis and potential solutions in a (publicly =
accessible) technical report.
>>=20
>> They would like MMUSIC to consider their work and want us to provide =
feedback on whether we would like to be involved in the coordination of =
future work on this topic.
>>=20
>> For details, please see the attached liaison document.
>>=20
>> Cheers,
>> /Bo
>>=20
>> ________________________________
>>=20
>> Title:                      LS on Improved end-to-end QoS =
Enhancements for MTSI
>>=20
>> Release:               Release 13
>>=20
>> Work Item:         QOSE2EMTSI
>>=20
>> Source:                 3GPP TSG SA WG4
>>=20
>> To:                          IETF MMUSIC
>>=20
>> Cc:                          3GPP TSG CT WG1, 3GPP TSG CT WG3, 3GPP =
TSG CT WG4
>>=20
>>=20
>>=20
>> -------------------------------------------------------------
>>=20
>> Susanna Kooistra, ETSI MCC
>>=20
>> 3GPP liaison co-ordinator
>>=20
>> E-mail: 3GPPLiaison@etsi.org<mailto:3GPPLiaison@etsi.org> =
<mailto:3GPPLiaison@etsi.org>
>>=20
>> Please consider the environmental impact before printing this e-mail
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Thu May 12 16:56:23 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C360D12D0CD for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 16:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7O_U0zfId16 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 16:56:19 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81C0912D0C9 for <mmusic@ietf.org>; Thu, 12 May 2016 16:56:19 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id 190so113946633iow.1 for <mmusic@ietf.org>; Thu, 12 May 2016 16:56:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=P47ARot2eBgfdfpf7XO4wvoKXhUxsJx8cLX7Ayii+sw=; b=Tuhg6OGlhwdf5UVx2VOL48cIuCNyjHzUHTZvKF7QzJ+Q1qYAahj201ZBMq25fSGbJK b9jOuS61c7Jcjd+BzVHFY5ZEUkcuTdwzDcvit1X22Jw5EHIY+1WsG+IFDETgCgC1hhgj dmpRxxRnWugiTmnWT6em7HKux8CCFt1yhUrCo59LypNHKjBA40JfZYG/harFjjG6BAVm OTo+jvCv702Xk/4ALf/kgiwVTbX4kltjjN0ajMc8ij57gUrzjVt/LqmVtmZLWrwd5cat 0/SNdegt2eZX6uXrtH3hWw3ZtVII6ZUt6VBeif5sk1KoH1HNZhkUuv842CZmfl5Doyi1 RG+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=P47ARot2eBgfdfpf7XO4wvoKXhUxsJx8cLX7Ayii+sw=; b=hbAiy3cvI0q55hXU1DyBKjZAk66hSOZwclvv/rCtxe66Pyu5vW2IztJZjvxff5jnvR A+drg7CULoiUJ/MrwEuOItk0Od0XK3eYauFZWdyjRYd9Em9Kc+LiPa1qz5iYCEpHgx5l /n2aROhE5TR3oIPtZG2L4wba5CmCuFbCRNQon5uNmqnjMw7sTYEQhIhVHMvWgxTQoIy+ PoibguIBWnbbZFOmQYCsuoBumqsdzeXGb3G0mvfHvuBsrrk6uaWpKRvBBtVM/NBtO9b/ vfTvydNlL6/wpp7TZ6fBScbjl33lY940FCaNjM4dCpNqMhUfX/SuCcy2MJ6lgIkrz6vC Nq6Q==
X-Gm-Message-State: AOPr4FWA7rrng7Xr1RFQH0eUtAHi/+KLArSKP2KlNOXyZdFmArJ5DduNno4g8w67Dpj3gw==
X-Received: by 10.36.144.131 with SMTP id x125mr9197itd.62.1463097378824; Thu, 12 May 2016 16:56:18 -0700 (PDT)
Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com. [209.85.213.180]) by smtp.gmail.com with ESMTPSA id g13sm5331678ioi.19.2016.05.12.16.56.17 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 May 2016 16:56:17 -0700 (PDT)
Received: by mail-ig0-f180.google.com with SMTP id lr7so2209185igb.1 for <mmusic@ietf.org>; Thu, 12 May 2016 16:56:17 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.62.13 with SMTP id u13mr387686igr.42.1463097377354; Thu, 12 May 2016 16:56:17 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Thu, 12 May 2016 16:56:17 -0700 (PDT)
In-Reply-To: <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com>
Date: Thu, 12 May 2016 19:56:17 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com>
Message-ID: <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc07a872ff660532ade7b9
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/rdvoAdpYFvGiR6aVR_EamSMt_kw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 May 2016 23:56:22 -0000

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

Hi All,

Well, we can define new attribute as set of name value pairs, and define
specific names for currently supported hashes, such as "a=fp:
sha1=base64val;sha256=base64val". New names can be added in the future to
extend the attribute and add new hash function support or other extensions.

Single attribute will refer to the single certificate, so all hashes in an
attribute must match the currently used certificate for the new attribute
to match.

New attribute can be used in parallel with old fingerprint attribute for
backwards compatibility. Matching fingerprint attribute will follow
existing rules (any one match of currently used certificate is sufficient).
New implementations MUST provide a new style attributes for each
certificate used and MAY provide old style fingerprint attributes for
backwards compatibility. If new attribute is present, new implementations
MUST only match new attributes and ignore the old fingerprint attribute.
They MAY match old fingerprint attributes if new attributes are not present.

I think this will give us the best of both worlds, backwards compatibility
and security. Since only things that I know off that currently implement
fingerprint attribute are WebRTC implementations, we can expect old
fingerprint attributes to be retired within a reasonable time.

One unrelated editor note would be that I would prefer the new draft to
overwrite RFC 4572 instead of updating a portion of it. I would also like
to rename it since the new draft covers not only connection oriented media
(TLS) but also DTLS.

Regards,

_____________
Roman Shpount

On Thu, May 12, 2016 at 6:25 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 12 May 2016 at 19:44, Kevin Dempsey <kevindempsey70@gmail.com> wrote:
> > For hash agility, you'd use the new attribute. I think that makes it much
> > simpler.
>
>
> We could fix the stupid syntax at the same time.  Backwards
> compatibility is for the weak:
>
> a=fp:<name>=<base64url-value>;<name>=<base64>
>
> Each line is a single certificate with as many hash functions as you
> please.
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr"><div>Hi All,</div><div><br></div>Well, we can define new a=
ttribute as set of name value pairs, and define specific names for currentl=
y supported hashes, such as &quot;a=3Dfp: sha1=3Dbase64val;sha256=3Dbase64v=
al&quot;. New names can be added in the future to extend the attribute and =
add new hash function support or other extensions.<div><br></div><div>Singl=
e attribute will refer to the single certificate, so all hashes in an attri=
bute must match the currently used certificate for the new attribute to mat=
ch.</div><div><br></div><div>New attribute can be used in parallel with old=
 fingerprint attribute for backwards compatibility. Matching fingerprint at=
tribute will follow existing rules (any one match of currently used certifi=
cate is sufficient). New implementations MUST provide a new style attribute=
s for each certificate used and MAY provide old style fingerprint attribute=
s for backwards compatibility. If new attribute is present, new implementat=
ions MUST only match new attributes and ignore the old fingerprint attribut=
e. They MAY match old fingerprint attributes if new attributes are not pres=
ent.</div><div><br></div><div>I think this will give us the best of both wo=
rlds, backwards compatibility and security. Since only things that I know o=
ff that currently implement fingerprint attribute are WebRTC implementation=
s, we can expect old fingerprint attributes to be retired within a reasonab=
le time.</div><div><br></div><div>One unrelated editor note would be that I=
 would prefer the new draft to overwrite RFC=C2=A0<span style=3D"color:rgb(=
0,0,0);font-size:13.3333px">4572 instead of updating a portion of it. I wou=
ld also like to rename it since the new draft covers not only connection or=
iented media (TLS) but also DTLS. =C2=A0 =C2=A0 =C2=A0</span></div><div><br=
></div><div>Regards,</div></div><div class=3D"gmail_extra"><br clear=3D"all=
"><div><div class=3D"gmail_signature">_____________<br>Roman Shpount</div><=
/div>
<br><div class=3D"gmail_quote">On Thu, May 12, 2016 at 6:25 AM, Martin Thom=
son <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.com" targe=
t=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><span class=3D"">On 12 May 2016 at 19:44, Kevin Dempsey =
&lt;<a href=3D"mailto:kevindempsey70@gmail.com">kevindempsey70@gmail.com</a=
>&gt; wrote:<br>
&gt; For hash agility, you&#39;d use the new attribute. I think that makes =
it much<br>
&gt; simpler.<br>
<br>
<br>
</span>We could fix the stupid syntax at the same time.=C2=A0 Backwards<br>
compatibility is for the weak:<br>
<br>
a=3Dfp:&lt;name&gt;=3D&lt;base64url-value&gt;;&lt;name&gt;=3D&lt;base64&gt;=
<br>
<br>
Each line is a single certificate with as many hash functions as you please=
.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div>

--047d7bdc07a872ff660532ade7b9--


From nobody Thu May 12 17:00:35 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E706412D0C9 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 17:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70zzQMt985Qn for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 17:00:32 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5210212D0A3 for <mmusic@ietf.org>; Thu, 12 May 2016 17:00:32 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id 190so114033881iow.1 for <mmusic@ietf.org>; Thu, 12 May 2016 17:00:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NVNgNfL2LLrb95vkBc/JOVRpMqEKkz7u4PLrmjZcy4k=; b=JdDjH99a0jNQNJRay7zOOyyXIjCHXRd5ayT2EPAzSbQ/id9E7B9+77B32ndgHAMA3s r4B8jZTMBgh0CyvuEjcwMX/9FZojtn2RFbL5pdzxA0V7Iob9PCbTDUnvdicKXaZbICA2 g15rNlMDodWd/0XeszH3itcpovPzROcg2tM2R/o9L74fftLh+aesgUmZQb63bmxYtRyo yQ8tol193cJxyJ1xXJe1FnNjaH/rrWhgNCBPofkJRPxsN0fMSIfwgrQQlEM+C7iY0/0M pboqmt4YLOj1ahMnXwLAGhM6IE3uh2/As84FSwyt1hiRTSaaCGSfn0xNf0oalZfHfIWD v4Bw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=NVNgNfL2LLrb95vkBc/JOVRpMqEKkz7u4PLrmjZcy4k=; b=NwfsAl/47CUc45hyWFBhmv6o+uOeviLV2Iz1Q409E3dz7x+FMQi0wFsTyOgdiiqVpN MDnbrf5D42aVZb1QNxTkxR8vdqjCPkOZ2kS+8NmYeI82UnH60Jj62bFHBMhGckIwsp+c DTuyTP14FGfPeoJqFyMPbyF2DDO7L6cT8XlJ0kuCXr9bS1NTvN/NfjtcdGKbviGOGgvd AyHpupDBg3eaZ81ke077XI3YG/3L/gTAc++LoSP7L4Ue8zjQxb0+WrANwDJlFlXkdJrY /iKQrSeCX5yE5cleD/SPyN6x0P7nl/ODDSw8gkoMB3mnhc55ZGHKzZNCwqbu/V1wwDq0 bW4A==
X-Gm-Message-State: AOPr4FXFBMvDVDIBcd7UXDjmNhJTmo4qVikOQRGzGca7pLnrHqBc1Msauq+/rYk7RZ57mw==
X-Received: by 10.36.74.74 with SMTP id k71mr17610itb.68.1463097631466; Thu, 12 May 2016 17:00:31 -0700 (PDT)
Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com. [209.85.213.170]) by smtp.gmail.com with ESMTPSA id w64sm175316ith.5.2016.05.12.17.00.30 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 May 2016 17:00:30 -0700 (PDT)
Received: by mail-ig0-f170.google.com with SMTP id lr7so2255109igb.1 for <mmusic@ietf.org>; Thu, 12 May 2016 17:00:30 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.124.39 with SMTP id mf7mr374154igb.95.1463097630635; Thu, 12 May 2016 17:00:30 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Thu, 12 May 2016 17:00:30 -0700 (PDT)
In-Reply-To: <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com>
Date: Thu, 12 May 2016 20:00:30 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsd9FVKqHK5uhd2UWtPkk0KtKd+nLTdr_KBXAiBZe0pMA@mail.gmail.com>
Message-ID: <CAD5OKxsd9FVKqHK5uhd2UWtPkk0KtKd+nLTdr_KBXAiBZe0pMA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Content-Type: multipart/alternative; boundary=089e0111bc568bdcee0532adf69a
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/7vzkJQyy2OYce6-uN4iETC0TeA4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 00:00:34 -0000

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

On Thu, May 12, 2016 at 5:44 AM, Kevin Dempsey <kevindempsey70@gmail.com>
wrote:

> The existing fingerprint attribute would keep the original requirement of
> using the same hash as the certificate. So there would be only one
> fingerprint line per certificate.
>
> I do not think any implementation is actually following the original
requirement of using the same hash as the certificate. This particular
requirement was simply misguided since there is not a single reason why
self signing hash algorithm should have any impact on the SDP fingerprint
attribute. The procedure to sign the certificate is completely different
from calculating certificate hash.
______________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Thu, May 12, 2016 at 5:44 AM, Kevin Dempsey <span dir=3D"ltr">&lt;<=
a href=3D"mailto:kevindempsey70@gmail.com" target=3D"_blank">kevindempsey70=
@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote">=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr">The existing fingerprint attribute would =
keep the original requirement of using the same hash as the certificate. So=
 there would be only one fingerprint line per certificate.<div><br></div></=
div></blockquote><div>I do not think any implementation is actually followi=
ng the original requirement of using the same hash as the certificate. This=
 particular requirement was simply misguided since there is not a single re=
ason why self signing hash algorithm should have any impact on the SDP fing=
erprint attribute. The procedure to sign the certificate is completely diff=
erent from calculating certificate hash.</div><div><span style=3D"color:rgb=
(0,0,0);font-size:13.3333px">______________</span></div><div><span style=3D=
"color:rgb(0,0,0);font-size:13.3333px">Roman Shpount =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0</span>=C2=A0</div></div></div></div>

--089e0111bc568bdcee0532adf69a--


From nobody Thu May 12 17:49:19 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 679A412B011 for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 17:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCMhPd-iu4sR for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 17:49:15 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F26512B009 for <mmusic@ietf.org>; Thu, 12 May 2016 17:49:15 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id i75so109630907ioa.3 for <mmusic@ietf.org>; Thu, 12 May 2016 17:49:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=3L4uhUP2nNyLxcvvUwjr/c22hjcJr/dH6Y5BCfye248=; b=zO5RfN6h31fxZ2Yg6B6s47LWvFeSs397TUVOErEhrM8dBtcXClYu1E5rS2IAHervsS a7VBxdHkFAAeFMBeuN1ExDAF0MLHBPRriAKAoPdXC/UH1Xd+IPORg6qgiHIjGX8lZgKT DdeHZZLgBLdfbqDWj2SwgKtAq7ucVEEkIVrH865Wnjibu3yaee6FYPIbzE8QJUjqG+2E zuc/9Fd7RJrGWrbBeMXstA/R91F4lfth2eNqYgA2mlA+EvXhaF8bOSQABfPE2Jbl6ba8 9wwR2oyppowug4lHtIZkL/oexHHuRBc1r5xuB8FQ73YQq0l/tJBkx5C6gbS+TfKgrKhh nBXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=3L4uhUP2nNyLxcvvUwjr/c22hjcJr/dH6Y5BCfye248=; b=MfiJKzNRNnoEGWvzSxpkH9KLuikf8oi074galDGrpYIDZAjCDHkwfUknlLbHSxcPuq ThU6Ax05Puj7oK/f4W9wTzYmOJUmwR0K1a1sESGj/fqkDRV3Pr7jrmkoy4rS0rNf4Be0 TC6jRZXvw2dQ737SKSqT/zRLu1NwGUn713FYZRYfcSpfPdEt2WHmlttn5Sg2t0C5CHdu 2N87nRObqZ8oVsNTwxIIm4kNrChRVz+rpo+TONwPrqbKUhMgAy2LSVFQnX3hS6T+VzKm eq5gvIDQdrfxoJrbLt9ATSGMzkxg6ox6pnzL6vh7MljJtUs4Vt8dp4Fzn8SAp26QSynC LS9A==
X-Gm-Message-State: AOPr4FX2SJDKmesft7YG9yGqTDJ3Oojx2pInhYRQi+N2kQ9p8pw5ZN8e7OXjjRlPXYJISQ==
X-Received: by 10.36.158.69 with SMTP id p66mr99822itd.97.1463100554634; Thu, 12 May 2016 17:49:14 -0700 (PDT)
Received: from mail-io0-f169.google.com (mail-io0-f169.google.com. [209.85.223.169]) by smtp.gmail.com with ESMTPSA id d80sm5361272iod.24.2016.05.12.17.49.13 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 May 2016 17:49:13 -0700 (PDT)
Received: by mail-io0-f169.google.com with SMTP id d62so114946240iof.2 for <mmusic@ietf.org>; Thu, 12 May 2016 17:49:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.71.8 with SMTP id t8mr113239itb.47.1463100553386; Thu, 12 May 2016 17:49:13 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Thu, 12 May 2016 17:49:13 -0700 (PDT)
In-Reply-To: <D35A123E.8508%christer.holmberg@ericsson.com>
References: <D35A123E.8508%christer.holmberg@ericsson.com>
Date: Thu, 12 May 2016 20:49:13 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsgmPxsjoQQWKxw5_epcNcaLsYPDAqksLbgFDAU0GZC8Q@mail.gmail.com>
Message-ID: <CAD5OKxsgmPxsjoQQWKxw5_epcNcaLsYPDAqksLbgFDAU0GZC8Q@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113f609cc1918a0532aea471
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/phImu3pTIGEmWIsM_rVBmXSv7DQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - WHERE WE ARE
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 00:49:18 -0000

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

Now we have the third alternative:

Define the new attribute where all hash values must match. Provide both old
fingerprint and new attribute for backwards compatibility.

_____________
Roman Shpount

On Thu, May 12, 2016 at 4:11 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> Based on the discussions, it seems (please correct me if I=C2=B9m wrong) =
that
> we have to alternatives:
>
>
> ALTERNATIVE 1 (Martin=C2=B9s):
>
> The SENDER MUST provide one or more hash functions for each offered
> certificate. The set of hash functions MUST be identical for each offered
> certificate.
>
> The RECEIVER MUST match each selected* certificate with each hash functio=
n
> provided by the sender (and supported by the receiver).
>
>
>
> ALTERNATIVE 2 (Roman=C2=B9s):
>
> The SENDER MUST provide one or more hash functions for each offered
> certificate. The set of hash functions can be different for each offered
> certificate.
>
> The RECEIVER MUST match each selected* certificate with one hash function
> supported by the receiver and provided by the sender. That hash function
> may be different for each used certificate, as long as it is considered
> secure by the receiver.
>
>
> Regards,
>
> Christer
>
>
> * In most cases a single certificate is selected (as part of the DTLS
> handshake), but there are use-cases where RTP and RTCP will use separate
> certificates
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Now we have the third alternative:<div><br></div><div>Defi=
ne the new attribute where all hash values must match. Provide both old fin=
gerprint and new attribute for backwards compatibility.</div></div><div cla=
ss=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signature">__=
___________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Thu, May 12, 2016 at 4:11 AM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
Based on the discussions, it seems (please correct me if I=C2=B9m wrong) th=
at<br>
we have to alternatives:<br>
<br>
<br>
ALTERNATIVE 1 (Martin=C2=B9s):<br>
<br>
The SENDER MUST provide one or more hash functions for each offered<br>
certificate. The set of hash functions MUST be identical for each offered<b=
r>
certificate.<br>
<br>
The RECEIVER MUST match each selected* certificate with each hash function<=
br>
provided by the sender (and supported by the receiver).<br>
<br>
<br>
<br>
ALTERNATIVE 2 (Roman=C2=B9s):<br>
<br>
The SENDER MUST provide one or more hash functions for each offered<br>
certificate. The set of hash functions can be different for each offered<br=
>
certificate.<br>
<br>
The RECEIVER MUST match each selected* certificate with one hash function<b=
r>
supported by the receiver and provided by the sender. That hash function<br=
>
may be different for each used certificate, as long as it is considered<br>
secure by the receiver.<br>
<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
* In most cases a single certificate is selected (as part of the DTLS<br>
handshake), but there are use-cases where RTP and RTCP will use separate<br=
>
certificates<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div><br></div>

--001a113f609cc1918a0532aea471--


From nobody Thu May 12 18:28:58 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1004E12B02F for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 18:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HeWbdbFNG8uN for <mmusic@ietfa.amsl.com>; Thu, 12 May 2016 18:28:54 -0700 (PDT)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17C5212B00F for <mmusic@ietf.org>; Thu, 12 May 2016 18:28:53 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by comcast with SMTP id 11tLbeZCGBE6O11uPbXPQ9; Fri, 13 May 2016 01:28:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463102933; bh=9/TT0ZfQCs7MXnlcvHJEWu7VxA6eCFnfevzXWM8KwwU=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Sl03chJ7+nCMh5qL+JlYQUOcuhAMD8vc6DvO5XbA1cC8kPTBHWAKD822qrHEpDakG iEtCTSCqhaZ75JGJAdZGjWvaL9cpaCj2YCCeVe+vjjuyjPfuqCEDl6r3u5rFA4nOHk ONLsoJ6SYRoj0b3oUhAPLUkhSm4cgFVrCxArYyXly3JZ7JKG61iAx6pchc0hPKJCIO qPTmfo/mwoV6We87g+AdhMtznvhaX7R9v3usvJbl5r0gZ7bouyGBnnPIveXQPuYtJS NeVJzSPXp9qNUn3Dvm4Ocb5rsgFkmWrk71H1TmVp3+0I5PO4VpUIJ33F+u/z5S71ep WGY980AvbtOvQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-17v.sys.comcast.net with comcast id tdUs1s00n3KdFy101dUsEa; Fri, 13 May 2016 01:28:53 +0000
To: Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <8a205f3a-a9cf-9c57-70f3-87923d7c07d1@alum.mit.edu>
Date: Thu, 12 May 2016 21:28:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/N0Pu2yxwhXsLb6zbTfem7q1pi6g>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 01:28:56 -0000

On 5/12/16 7:56 PM, Roman Shpount wrote:
> Hi All,
>
> Well, we can define new attribute as set of name value pairs, and define
> specific names for currently supported hashes, such as "a=fp:
> sha1=base64val;sha256=base64val". New names can be added in the future
> to extend the attribute and add new hash function support or other
> extensions.
>
> Single attribute will refer to the single certificate, so all hashes in
> an attribute must match the currently used certificate for the new
> attribute to match.
>
> New attribute can be used in parallel with old fingerprint attribute for
> backwards compatibility. Matching fingerprint attribute will follow
> existing rules (any one match of currently used certificate is
> sufficient). New implementations MUST provide a new style attributes for
> each certificate used and MAY provide old style fingerprint attributes
> for backwards compatibility. If new attribute is present, new
> implementations MUST only match new attributes and ignore the old
> fingerprint attribute. They MAY match old fingerprint attributes if new
> attributes are not present.
>
> I think this will give us the best of both worlds, backwards
> compatibility and security. Since only things that I know off that
> currently implement fingerprint attribute are WebRTC implementations, we
> can expect old fingerprint attributes to be retired within a reasonable
> time.

Make sure to define O/A rules so that the offerer *knows* if the new 
attribute was understood.

Also, should the fingerprint in a=fingerprint be repeated in the new 
attribute? Or should the new attribute just be used for additional 
fingerprints?

	Thanks,
	Paul

> One unrelated editor note would be that I would prefer the new draft to
> overwrite RFC 4572 instead of updating a portion of it. I would also
> like to rename it since the new draft covers not only connection
> oriented media (TLS) but also DTLS.
>
> Regards,
>
> _____________
> Roman Shpount
>
> On Thu, May 12, 2016 at 6:25 AM, Martin Thomson
> <martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>> wrote:
>
>     On 12 May 2016 at 19:44, Kevin Dempsey <kevindempsey70@gmail.com
>     <mailto:kevindempsey70@gmail.com>> wrote:
>     > For hash agility, you'd use the new attribute. I think that makes it much
>     > simpler.
>
>
>     We could fix the stupid syntax at the same time.  Backwards
>     compatibility is for the weak:
>
>     a=fp:<name>=<base64url-value>;<name>=<base64>
>
>     Each line is a single certificate with as many hash functions as you
>     please.
>
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
>
>


From nobody Fri May 13 06:36:02 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F8B012B03A for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 06:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KXq-WKk6Fdek for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 06:35:59 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D90312B014 for <mmusic@ietf.org>; Fri, 13 May 2016 06:35:58 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-e6-5735d83c4652
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 15.59.27088.C38D5375; Fri, 13 May 2016 15:35:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0248.002; Fri, 13 May 2016 15:35:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEA=
Date: Fri, 13 May 2016 13:35:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com>
In-Reply-To: <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FA224DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGIsWRmVeSWpSXmKPExsUyM2K7oq7NDdNwg/tfzSxuzn/LYnHtzD9G i6nLH7NYrNhwgNVixoWpzA6sHn/ff2Dy2DnrLrvHkiU/mTxuTSkIYInisklJzcksSy3St0vg ytj/4wFjwZ26il+fJrI2MK6o7mLk4JAQMJHYtl6pi5ETyBSTuHBvPRuILSRwhFHi1kSOLkYu IHsJo8SCSTfYQerZBCwkuv9pg9SICARJPJ8+nwnEZhaolPizaRZYr7CAp8T105/ZIGq8JC5M XcAOYW9ilNj/yQXEZhFQlTjz8ggjiM0r4CvxeMlUdohdDzglvi3bCJbgFAiU6HjyA6yZEei4 76fWQC0Tl7j1BGKxhICAxJI955khbFGJl4//sULYShKLbn+Gqs+X+Hl9OzPEMkGJkzOfsExg FJ2FZNQsJGWzkJTNAnqZWUBTYv0ufYgSRYkp3Q/ZIWwNidY5c9mRxRcwsq9iFC1OLU7KTTcy 0kstykwuLs7P08tLLdnECIzNg1t+G+xgfPnc8RCjAAejEg+vgqlpuBBrYllxZe4hRgkOZiUR 3sQzQCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8/i8Vw4UE0hNLUrNTUwtSi2CyTBycUg2MDX3z NrrHnonc+dt+XWKebbjW3cggtoy+8BnNQnoujw3m5xYrHvtnwHx8pWie4dX+nq9+U49Wrvxh H3bgwIqTQROuHviYqZQ+M/n1zwNO9o0eHzuz1jgzGrtyvv/QNKsuTGb6p6cn/0ub+5hvr30v U7hAT+CLcFLj0cazO7/dP2wTcIZJe/4fJZbijERDLeai4kQAnwi/SckCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/mnMkIvCArIyDnd4R_YkQetaj3mY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 13:36:01 -0000

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

SGksDQoNCj5XZWxsLCB3ZSBjYW4gZGVmaW5lIG5ldyBhdHRyaWJ1dGUgYXMgc2V0IG9mIG5hbWUg
dmFsdWUgcGFpcnMsIGFuZCBkZWZpbmUgc3BlY2lmaWMgbmFtZXMgZm9yIGN1cnJlbnRseSBzdXBw
b3J0ZWQNCj5oYXNoZXMsIHN1Y2ggYXMgImE9ZnA6IHNoYTE9YmFzZTY0dmFsO3NoYTI1Nj1iYXNl
NjR2YWwiLiBOZXcgbmFtZXMgY2FuIGJlIGFkZGVkIGluIHRoZSBmdXR1cmUgdG8gZXh0ZW5kIHRo
ZQ0KPmF0dHJpYnV0ZSBhbmQgYWRkIG5ldyBoYXNoIGZ1bmN0aW9uIHN1cHBvcnQgb3Igb3RoZXIg
ZXh0ZW5zaW9ucy4NCg0KSSB0aGluayB3ZSBjYW4gdXNlIHRoZSBzYW1lIHZhbHVlcyB0aGF0IGFy
ZSB1c2VkIGZvciB0aGUgY3VycmVudCBmaW5nZXJwcmludCBhdHRyaWJ1dGUuDQoNCmhhc2gtZnVu
YyAgICAgICAgICAgICAgPSAgInNoYS0xIiAvICJzaGEtMjI0IiAvICJzaGEtMjU2IiAvDQogICAg
ICAgICAgICAgICAgICAgICAgICAgICJzaGEtMzg0IiAvICJzaGEtNTEyIiAvDQogICAgICAgICAg
ICAgICAgICAgICAgICAgICJtZDUiIC8gIm1kMiIgLyB0b2tlbg0KICAgICAgICAgICAgICAgICAg
ICAgICAgICA7IEFkZGl0aW9uYWwgaGFzaCBmdW5jdGlvbnMgY2FuIG9ubHkgY29tZQ0KICAgICAg
ICAgICAgICAgICAgICAgICAgICA7IGZyb20gdXBkYXRlcyB0byBSRkMgMzI3OQ0KDQo+U2luZ2xl
IGF0dHJpYnV0ZSB3aWxsIHJlZmVyIHRvIHRoZSBzaW5nbGUgY2VydGlmaWNhdGUsIHNvIGFsbCBo
YXNoZXMgaW4gYW4gYXR0cmlidXRlIG11c3QgbWF0Y2ggdGhlIGN1cnJlbnRseSB1c2VkIGNlcnRp
ZmljYXRlIGZvciB0aGUgbmV3IGF0dHJpYnV0ZSB0byBtYXRjaC4NCg0KSG93IGRvIHdlIGFzc29j
aWF0ZSBhbiBhdHRyaWJ1dGUgd2l0aCBhIGNlcnRpZmljYXRlLCBzbyB0aGF0IHRoZSByZWNlaXZl
ciBjYW4gbWF0Y2ggdGhlIGF0dHJpYnV0ZSAoYW5kIHRoZSBoYXNoZXMpIHdpdGggdGhlIGFzc29j
aWF0ZWQgY2VydGlmaWNhdGU/DQoNCj5OZXcgYXR0cmlidXRlIGNhbiBiZSB1c2VkIGluIHBhcmFs
bGVsIHdpdGggb2xkIGZpbmdlcnByaW50IGF0dHJpYnV0ZSBmb3IgYmFja3dhcmRzIGNvbXBhdGli
aWxpdHkuIE1hdGNoaW5nIGZpbmdlcnByaW50IGF0dHJpYnV0ZSB3aWxsIGZvbGxvdyBleGlzdGlu
ZyBydWxlcyAoYW55IG9uZSBtYXRjaCBvZiBjdXJyZW50bHkgdXNlZCA+Y2VydGlmaWNhdGUgaXMg
c3VmZmljaWVudCkuIE5ldyBpbXBsZW1lbnRhdGlvbnMgTVVTVCBwcm92aWRlIGEgbmV3IHN0eWxl
IGF0dHJpYnV0ZXMgZm9yIGVhY2ggY2VydGlmaWNhdGUgdXNlZCBhbmQgTUFZIHByb3ZpZGUgb2xk
IHN0eWxlIGZpbmdlcnByaW50IGF0dHJpYnV0ZXMgZm9yIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5
LiA+SWYgbmV3IGF0dHJpYnV0ZSBpcyBwcmVzZW50LCBuZXcgaW1wbGVtZW50YXRpb25zIE1VU1Qg
b25seSBtYXRjaCBuZXcgYXR0cmlidXRlcyBhbmQgaWdub3JlIHRoZSBvbGQgZmluZ2VycHJpbnQg
YXR0cmlidXRlLiBUaGV5IE1BWSBtYXRjaCBvbGQgZmluZ2VycHJpbnQgYXR0cmlidXRlcyBpZiBu
ZXcgYXR0cmlidXRlcyBhcmUgPm5vdCBwcmVzZW50Lg0KDQpJIHRoaW5rIHRoZXJlIGFyZSBzdGls
bCBkaWZmZXJlbnQgb3BpbmlvbnMgb24gd2hldGhlciBvbmUgbWF0Y2ggaXMgZW5vdWdoLCBvciB3
aGV0aGVyIGFsbCBzdXBwb3J0ZWQgaGFzaGVzIHNob3VsZCBiZSB0ZXN0ZWQuDQoNCkkgdGhpbmsg
dGhpcyB3aWxsIGdpdmUgdXMgdGhlIGJlc3Qgb2YgYm90aCB3b3JsZHMsIGJhY2t3YXJkcyBjb21w
YXRpYmlsaXR5IGFuZCBzZWN1cml0eS4gU2luY2Ugb25seSB0aGluZ3MgdGhhdCBJIGtub3cgb2Zm
IHRoYXQgY3VycmVudGx5IGltcGxlbWVudCBmaW5nZXJwcmludCBhdHRyaWJ1dGUgYXJlIFdlYlJU
QyBpbXBsZW1lbnRhdGlvbnMsIHdlIGNhbiBleHBlY3Qgb2xkIGZpbmdlcnByaW50IGF0dHJpYnV0
ZXMgdG8gYmUgcmV0aXJlZCB3aXRoaW4gYSByZWFzb25hYmxlIHRpbWUuDQoNCj5PbmUgdW5yZWxh
dGVkIGVkaXRvciBub3RlIHdvdWxkIGJlIHRoYXQgSSB3b3VsZCBwcmVmZXIgdGhlIG5ldyBkcmFm
dCB0byBvdmVyd3JpdGUgUkZDIDQ1NzIgaW5zdGVhZCBvZiB1cGRhdGluZyBhIHBvcnRpb24gb2Yg
aXQuIEkgd291bGQgYWxzbw0KPmxpa2UgdG8gcmVuYW1lIGl0IHNpbmNlIHRoZSBuZXcgZHJhZnQg
Y292ZXJzIG5vdCBvbmx5IGNvbm5lY3Rpb24gb3JpZW50ZWQgbWVkaWEgKFRMUykgYnV0IGFsc28g
RFRMUy4NCg0KTm90ZSB0aGF0IHZlcnkgbGl0dGxlIG9mIHRoZSBleGlzdGluZyA0NTcyIHRleHQg
d291bGQgYmUgbW9kaWZpZWQuIFdlIHdvdWxkIG9ubHkgY2xhcmlmeSB0aGUgcmVzdHJpY3Rpb25z
IGFzc29jaWF0ZWQgd2l0aCB0aGUgZmluZ2VycHJpbnQgYXR0cmlidXRlLg0KDQpBbnl3YXksIG15
IHN1Z2dlc3Rpb24gaXMgdG8gZ2V0IHRoZSBtZWNoYW5pc20gY29ycmVjdCBmaXJzdCwgYW5kIHRo
ZW4gd2Ugc2VlIHdoYXTigJlzIHRoZSBiZXN0IHdheSBvZiBkb2N1bWVudGluZyBldmVyeXRoaW5n
Lg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCglt
YXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0
eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJ
Y29sb3I6IzFGNDk3RDt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJz
b25hbC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9y
OndpbmRvd3RleHQ7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFt
ZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3IjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1HQjt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcy
LjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5
bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0
IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDld
Pjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRp
dCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVh
ZD4NCjxib2R5IGxhbmc9IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYg
Y2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGksPG86cD48L286
cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0O1dlbGwsIHdl
IGNhbiBkZWZpbmUgbmV3IGF0dHJpYnV0ZSBhcyBzZXQgb2YgbmFtZSB2YWx1ZSBwYWlycywgYW5k
IGRlZmluZSBzcGVjaWZpYyBuYW1lcyBmb3IgY3VycmVudGx5IHN1cHBvcnRlZA0KPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZndDs8L3NwYW4+
aGFzaGVzLCBzdWNoIGFzICZxdW90O2E9ZnA6IHNoYTE9YmFzZTY0dmFsO3NoYTI1Nj1iYXNlNjR2
YWwmcXVvdDsuIE5ldyBuYW1lcyBjYW4gYmUgYWRkZWQgaW4gdGhlIGZ1dHVyZSB0byBleHRlbmQg
dGhlDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+Jmd0Ozwvc3Bhbj5hdHRyaWJ1dGUgYW5kIGFkZCBuZXcgaGFzaCBmdW5jdGlvbiBzdXBwb3J0
IG9yIG90aGVyIGV4dGVuc2lvbnMuPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkkgdGhpbmsgd2UgY2FuIHVzZSB0
aGUgc2FtZSB2YWx1ZXMgdGhhdCBhcmUgdXNlZCBmb3IgdGhlIGN1cnJlbnQgZmluZ2VycHJpbnQg
YXR0cmlidXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDsiPmhhc2gtZnVuYyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA9Jm5ic3A7
ICZxdW90O3NoYS0xJnF1b3Q7IC8gJnF1b3Q7c2hhLTIyNCZxdW90OyAvICZxdW90O3NoYS0yNTYm
cXVvdDsgLzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJnF1b3Q7c2hhLTM4NCZx
dW90OyAvICZxdW90O3NoYS01MTImcXVvdDsgLzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgJnF1b3Q7bWQ1JnF1b3Q7IC8gJnF1b3Q7bWQyJnF1b3Q7IC8gdG9rZW48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IDsgQWRkaXRpb25hbCBoYXNoIGZ1bmN0aW9ucyBjYW4g
b25seSBjb21lPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA7IGZyb20gdXBkYXRl
cyB0byBSRkMgMzI3OTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0O1NpbmdsZSBhdHRyaWJ1dGUgd2lsbCByZWZl
ciB0byB0aGUgc2luZ2xlIGNlcnRpZmljYXRlLCBzbyBhbGwgaGFzaGVzIGluIGFuIGF0dHJpYnV0
ZSBtdXN0IG1hdGNoIHRoZSBjdXJyZW50bHkgdXNlZCBjZXJ0aWZpY2F0ZSBmb3IgdGhlIG5ldyBh
dHRyaWJ1dGUgdG8gbWF0Y2guPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+SG93IGRvIHdlIGFzc29jaWF0ZSBhbiBhdHRyaWJ1dGUgd2l0aCBh
IGNlcnRpZmljYXRlLCBzbyB0aGF0IHRoZSByZWNlaXZlciBjYW4gbWF0Y2ggdGhlIGF0dHJpYnV0
ZSAoYW5kIHRoZSBoYXNoZXMpIHdpdGggdGhlIGFzc29jaWF0ZWQgY2VydGlmaWNhdGU/PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj4mZ3Q7TmV3IGF0dHJpYnV0ZSBjYW4gYmUgdXNlZCBpbiBwYXJhbGxlbCB3aXRoIG9s
ZCBmaW5nZXJwcmludCBhdHRyaWJ1dGUgZm9yIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5LiBNYXRj
aGluZyBmaW5nZXJwcmludCBhdHRyaWJ1dGUgd2lsbCBmb2xsb3cgZXhpc3RpbmcgcnVsZXMgKGFu
eSBvbmUgbWF0Y2ggb2YgY3VycmVudGx5IHVzZWQgJmd0O2NlcnRpZmljYXRlIGlzIHN1ZmZpY2ll
bnQpLiBOZXcgaW1wbGVtZW50YXRpb25zDQogTVVTVCBwcm92aWRlIGEgbmV3IHN0eWxlIGF0dHJp
YnV0ZXMgZm9yIGVhY2ggY2VydGlmaWNhdGUgdXNlZCBhbmQgTUFZIHByb3ZpZGUgb2xkIHN0eWxl
IGZpbmdlcnByaW50IGF0dHJpYnV0ZXMgZm9yIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5LiAmZ3Q7
SWYgbmV3IGF0dHJpYnV0ZSBpcyBwcmVzZW50LCBuZXcgaW1wbGVtZW50YXRpb25zIE1VU1Qgb25s
eSBtYXRjaCBuZXcgYXR0cmlidXRlcyBhbmQgaWdub3JlIHRoZSBvbGQgZmluZ2VycHJpbnQgYXR0
cmlidXRlLg0KIFRoZXkgTUFZIG1hdGNoIG9sZCBmaW5nZXJwcmludCBhdHRyaWJ1dGVzIGlmIG5l
dyBhdHRyaWJ1dGVzIGFyZSAmZ3Q7bm90IHByZXNlbnQuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+SSB0aGluayB0aGVyZSBhcmUgc3RpbGwg
ZGlmZmVyZW50IG9waW5pb25zIG9uIHdoZXRoZXIgb25lIG1hdGNoIGlzIGVub3VnaCwgb3Igd2hl
dGhlciBhbGwgc3VwcG9ydGVkIGhhc2hlcyBzaG91bGQgYmUgdGVzdGVkLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SSB0aGluayB0aGlzIHdpbGwgZ2l2ZSB1cyB0aGUgYmVzdCBvZiBib3RoIHdvcmxkcywgYmFja3dh
cmRzIGNvbXBhdGliaWxpdHkgYW5kIHNlY3VyaXR5LiBTaW5jZSBvbmx5IHRoaW5ncyB0aGF0IEkg
a25vdyBvZmYgdGhhdCBjdXJyZW50bHkgaW1wbGVtZW50IGZpbmdlcnByaW50IGF0dHJpYnV0ZSBh
cmUgV2ViUlRDIGltcGxlbWVudGF0aW9ucywgd2UgY2FuIGV4cGVjdCBvbGQgZmluZ2VycHJpbnQg
YXR0cmlidXRlcw0KIHRvIGJlIHJldGlyZWQgd2l0aGluIGEgcmVhc29uYWJsZSB0aW1lLjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7T25l
IHVucmVsYXRlZCBlZGl0b3Igbm90ZSB3b3VsZCBiZSB0aGF0IEkgd291bGQgcHJlZmVyIHRoZSBu
ZXcgZHJhZnQgdG8gb3ZlcndyaXRlIFJGQyZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2NvbG9yOmJsYWNrIj40NTcyIGluc3RlYWQgb2YgdXBkYXRpbmcgYSBwb3J0aW9uIG9mIGl0
LiBJIHdvdWxkIGFsc28NCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij4mZ3Q7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2NvbG9yOmJsYWNrIj5s
aWtlIHRvIHJlbmFtZSBpdCBzaW5jZSB0aGUgbmV3IGRyYWZ0IGNvdmVycyBub3Qgb25seSBjb25u
ZWN0aW9uIG9yaWVudGVkIG1lZGlhIChUTFMpIGJ1dCBhbHNvIERUTFMuICZuYnNwOyAmbmJzcDsg
Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPk5vdGUgdGhhdCB2ZXJ5IGxpdHRs
ZSBvZiB0aGUgZXhpc3RpbmcgNDU3MiB0ZXh0IHdvdWxkIGJlIG1vZGlmaWVkLiBXZSB3b3VsZCBv
bmx5IGNsYXJpZnkgdGhlIHJlc3RyaWN0aW9ucyBhc3NvY2lhdGVkIHdpdGggdGhlIGZpbmdlcnBy
aW50IGF0dHJpYnV0ZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+QW55d2F5LCBteSBzdWdnZXN0aW9uIGlzIHRv
IGdldCB0aGUgbWVjaGFuaXNtIGNvcnJlY3QgZmlyc3QsIGFuZCB0aGVuIHdlIHNlZSB3aGF04oCZ
cyB0aGUgYmVzdCB3YXkgb2YgZG9jdW1lbnRpbmcgZXZlcnl0aGluZy48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlJl
Z2FyZHMsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B37FA224DESESSMB209erics_--


From nobody Fri May 13 07:33:18 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A999A12D0C7 for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 07:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhzCpSwcIbbC for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 07:33:15 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EFF112B00C for <mmusic@ietf.org>; Fri, 13 May 2016 07:33:14 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-83-5735e5a8d56e
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 3E.83.27088.8A5E5375; Fri, 13 May 2016 16:33:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.117]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0248.002; Fri, 13 May 2016 16:33:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmAgAAZ3AD//xHE4A==
Date: Fri, 13 May 2016 14:33:11 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FA2314@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <8a205f3a-a9cf-9c57-70f3-87923d7c07d1@alum.mit.edu>
In-Reply-To: <8a205f3a-a9cf-9c57-70f3-87923d7c07d1@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM2K7ve6Kp6bhBnNPaFvcnP+WxeLamX+M FlOXP2axWLHhAKvFjAtTmR1YPf6+/8DksXPWXXaPJUt+MnncmlIQwBLFZZOSmpNZllqkb5fA lfFvl1nBO+GKnun7WRsY1wh3MXJySAiYSDy5+YQFwhaTuHBvPVsXIxeHkMARRolHEzpZIZwl jBKHru8Bcjg42AQsJLr/aYM0iAhUSFzae48dJMwsECxx41QISFhYwFPi+unPbBAlXhIXpi5g BxkjIrCLUeLyyZeMIAkWAVWJQxs+gvXyCvhKXHxrDbFqDofEmtd7wJo5BRwkju88ywRiMwId 9/3UGjCbWUBc4taT+UwQRwtILNlznhnCFpV4+fgfK4StJNG45AkrxG2aEut36UO0KkpM6X7I DmLzCghKnJz5hGUCo9gsJFNnIXTMQtIxC0nHAkaWVYyixanFSbnpRkZ6qUWZycXF+Xl6eakl mxiBkXZwy2+DHYwvnzseYhTgYFTi4X1w1zRciDWxrLgy9xCjBAezkggv1xOgEG9KYmVValF+ fFFpTmrxIUZpDhYlcV7/l4rhQgLpiSWp2ampBalFMFkmDk6pBkaWilJOrY7C3qNLhHRTGdtC InXjG6w/CCSWTzWo4+HdnvT1TqPOqnvml7MWHeCvrdx42DHE9TSXo4uT6xSRImmnU/Y+Jj1X OwxefQ9q2ujTrVd6Z5nBaTHJtds01Ms8elu3zo5/HHvu5PVHfPkVylmFX383cKkfq/8QZxc7 W/pItaxQ0rZ2JZbijERDLeai4kQAhOSpCrACAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/tnT-c69RRqrxX_M2bpOLRm1jr20>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 14:33:17 -0000

SGksDQoNCj4+IFdlbGwsIHdlIGNhbiBkZWZpbmUgbmV3IGF0dHJpYnV0ZSBhcyBzZXQgb2YgbmFt
ZSB2YWx1ZSBwYWlycywgYW5kIA0KPj4gZGVmaW5lIHNwZWNpZmljIG5hbWVzIGZvciBjdXJyZW50
bHkgc3VwcG9ydGVkIGhhc2hlcywgc3VjaCBhcyAiYT1mcDoNCj4+IHNoYTE9YmFzZTY0dmFsO3No
YTI1Nj1iYXNlNjR2YWwiLiBOZXcgbmFtZXMgY2FuIGJlIGFkZGVkIGluIHRoZSBmdXR1cmUgDQo+
PiB0byBleHRlbmQgdGhlIGF0dHJpYnV0ZSBhbmQgYWRkIG5ldyBoYXNoIGZ1bmN0aW9uIHN1cHBv
cnQgb3Igb3RoZXIgDQo+PiBleHRlbnNpb25zLg0KPj4NCj4+IFNpbmdsZSBhdHRyaWJ1dGUgd2ls
bCByZWZlciB0byB0aGUgc2luZ2xlIGNlcnRpZmljYXRlLCBzbyBhbGwgaGFzaGVzIA0KPj4gaW4g
YW4gYXR0cmlidXRlIG11c3QgbWF0Y2ggdGhlIGN1cnJlbnRseSB1c2VkIGNlcnRpZmljYXRlIGZv
ciB0aGUgbmV3IA0KPj4gYXR0cmlidXRlIHRvIG1hdGNoLg0KPj4NCj4+IE5ldyBhdHRyaWJ1dGUg
Y2FuIGJlIHVzZWQgaW4gcGFyYWxsZWwgd2l0aCBvbGQgZmluZ2VycHJpbnQgYXR0cmlidXRlIA0K
Pj4gZm9yIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5LiBNYXRjaGluZyBmaW5nZXJwcmludCBhdHRy
aWJ1dGUgd2lsbCANCj4+IGZvbGxvdyBleGlzdGluZyBydWxlcyAoYW55IG9uZSBtYXRjaCBvZiBj
dXJyZW50bHkgdXNlZCBjZXJ0aWZpY2F0ZSBpcyANCj4+IHN1ZmZpY2llbnQpLiBOZXcgaW1wbGVt
ZW50YXRpb25zIE1VU1QgcHJvdmlkZSBhIG5ldyBzdHlsZSBhdHRyaWJ1dGVzIA0KPj4gZm9yIGVh
Y2ggY2VydGlmaWNhdGUgdXNlZCBhbmQgTUFZIHByb3ZpZGUgb2xkIHN0eWxlIGZpbmdlcnByaW50
IA0KPj4gYXR0cmlidXRlcyBmb3IgYmFja3dhcmRzIGNvbXBhdGliaWxpdHkuIElmIG5ldyBhdHRy
aWJ1dGUgaXMgcHJlc2VudCwgDQo+PiBuZXcgaW1wbGVtZW50YXRpb25zIE1VU1Qgb25seSBtYXRj
aCBuZXcgYXR0cmlidXRlcyBhbmQgaWdub3JlIHRoZSBvbGQgDQo+PiBmaW5nZXJwcmludCBhdHRy
aWJ1dGUuIFRoZXkgTUFZIG1hdGNoIG9sZCBmaW5nZXJwcmludCBhdHRyaWJ1dGVzIGlmIA0KPj4g
bmV3IGF0dHJpYnV0ZXMgYXJlIG5vdCBwcmVzZW50Lg0KPj4NCj4+IEkgdGhpbmsgdGhpcyB3aWxs
IGdpdmUgdXMgdGhlIGJlc3Qgb2YgYm90aCB3b3JsZHMsIGJhY2t3YXJkcyANCj4+IGNvbXBhdGli
aWxpdHkgYW5kIHNlY3VyaXR5LiBTaW5jZSBvbmx5IHRoaW5ncyB0aGF0IEkga25vdyBvZmYgdGhh
dCANCj4+IGN1cnJlbnRseSBpbXBsZW1lbnQgZmluZ2VycHJpbnQgYXR0cmlidXRlIGFyZSBXZWJS
VEMgaW1wbGVtZW50YXRpb25zLCANCj4+IHdlIGNhbiBleHBlY3Qgb2xkIGZpbmdlcnByaW50IGF0
dHJpYnV0ZXMgdG8gYmUgcmV0aXJlZCB3aXRoaW4gYSANCj4+IHJlYXNvbmFibGUgdGltZS4NCj4N
Cj4gTWFrZSBzdXJlIHRvIGRlZmluZSBPL0EgcnVsZXMgc28gdGhhdCB0aGUgb2ZmZXJlciAqa25v
d3MqIGlmIHRoZSBuZXcgYXR0cmlidXRlIHdhcyB1bmRlcnN0b29kLg0KDQpJZiB0aGUgYW5zd2Vy
ZXIgc3VwcG9ydHMgdGhlIGF0dHJpYnV0ZSwgaXQgTVVTVCBpbmNsdWRlIGl0IGluIHRoZSBhbnN3
ZXIuDQoNCj5BbHNvLCBzaG91bGQgdGhlIGZpbmdlcnByaW50IGluIGE9ZmluZ2VycHJpbnQgYmUg
cmVwZWF0ZWQgaW4gdGhlIG5ldyBhdHRyaWJ1dGU/IE9yIHNob3VsZCB0aGUgbmV3IGF0dHJpYnV0
ZSBqdXN0IGJlIHVzZWQgZm9yIGFkZGl0aW9uYWwgZmluZ2VycHJpbnRzPw0KDQpJIHNlZSBubyBy
ZWFzb24gdG8gbm90IGFsbG93IGEgaGFzaCB0byBiZSBpbmNsdWRlZCBpbiBib3RoIGF0dHJpYnV0
ZXMuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Fri May 13 07:55:45 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABA9C127058 for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 07:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bxV2MNap6Qio for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 07:55:43 -0700 (PDT)
Received: from resqmta-po-02v.sys.comcast.net (resqmta-po-02v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 689ED12B00C for <mmusic@ietf.org>; Fri, 13 May 2016 07:55:43 -0700 (PDT)
Received: from resomta-po-16v.sys.comcast.net ([96.114.154.240]) by comcast with SMTP id 1EVCbrxXPGhQ01EVCb7DNm; Fri, 13 May 2016 14:55:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463151342; bh=L1vf3pRjt6DDYu9pIU8HUZRvQYdYVUhetsFoos+P/k8=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=SvEVQyGKMGCwsD3Ue0VJdBEiO8b/W++gaSSRLxG7u5cnUIa6oLC+hMOtX41QukOFg ACaGeajPOSwYvOvrRPI77MhfDFo25pcUTx+Ud913WwKeteo3JChF8l3L3y/7n8RgYx GZfBNoA/CUU6zVIvdEDXalqmHCL/Lti2r1KL9/uFFsgFADwY8lOCiRNo+HYJMnnJCw Z4MwgwaqonSeUXvj3JwOJ65FWZK+ZXNZO3MHNIa+r9rY+FQRvkP/pQhGM43wqZCgQh +6j0iIPq4iDKdOSUEYidAF4M7QMuLJ1g/MFs0cecxS7NLnBcDXRY27vL9mH8eYEKTl KL3iB2hpwElQg==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-po-16v.sys.comcast.net with comcast id tqvh1s00J3KdFy101qvi08; Fri, 13 May 2016 14:55:42 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <8a205f3a-a9cf-9c57-70f3-87923d7c07d1@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FA2314@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <a834657e-ab8e-e33d-ceee-3e5727130363@alum.mit.edu>
Date: Fri, 13 May 2016 10:55:40 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FA2314@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/na5v-mODzDm8pZMdkALW08R77Wc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 14:55:44 -0000

On 5/13/16 10:33 AM, Christer Holmberg wrote:
> Hi,
>
>>> Well, we can define new attribute as set of name value pairs, and
>>> define specific names for currently supported hashes, such as "a=fp:
>>> sha1=base64val;sha256=base64val". New names can be added in the future
>>> to extend the attribute and add new hash function support or other
>>> extensions.
>>>
>>> Single attribute will refer to the single certificate, so all hashes
>>> in an attribute must match the currently used certificate for the new
>>> attribute to match.
>>>
>>> New attribute can be used in parallel with old fingerprint attribute
>>> for backwards compatibility. Matching fingerprint attribute will
>>> follow existing rules (any one match of currently used certificate is
>>> sufficient). New implementations MUST provide a new style attributes
>>> for each certificate used and MAY provide old style fingerprint
>>> attributes for backwards compatibility. If new attribute is present,
>>> new implementations MUST only match new attributes and ignore the old
>>> fingerprint attribute. They MAY match old fingerprint attributes if
>>> new attributes are not present.
>>>
>>> I think this will give us the best of both worlds, backwards
>>> compatibility and security. Since only things that I know off that
>>> currently implement fingerprint attribute are WebRTC implementations,
>>> we can expect old fingerprint attributes to be retired within a
>>> reasonable time.
>>
>> Make sure to define O/A rules so that the offerer *knows* if the new attribute was understood.
>
> If the answerer supports the attribute, it MUST include it in the answer.

That is what I was thinking.

What about the case where the answerer is the one that will be sending 
the certificate, and hence needs to send the fingerprints? That might 
not be common, but it might be possible.

>> Also, should the fingerprint in a=fingerprint be repeated in the new attribute? Or should the new attribute just be used for additional fingerprints?
>
> I see no reason to not allow a hash to be included in both attributes.

Nor do I. But it is worth considering how best to migrate. If you need 
to include a=fingerprint anyway, for backward compatibility, then it 
might make sense to simply use the new attribute for *additional* 
fingerprints.

I don't feel strongly about this. But it is good to be clear what the 
expectation is. If both attributes are present, and the fingerprint in 
a=fingerprint is *not* present in the new attribute, must it still match 
to *some* certificate?

	Thanks,
	Paul

	Thanks,
	Paul

> Regards,
>
> Christer
>


From nobody Fri May 13 11:04:49 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 209F812D651 for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 11:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vebIm2qn2muP for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 11:04:46 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E501712D64D for <mmusic@ietf.org>; Fri, 13 May 2016 11:04:45 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id k142so182895713oib.1 for <mmusic@ietf.org>; Fri, 13 May 2016 11:04:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=3mE3D4AWmHzirxTIheAplux7FGWSMVJlbT3TFFsh6EM=; b=kenNqP5dyH0iUPsANxlLdEUhJ3/S8UdkV8npHcjYOhsWYRb0F5m13FxFsr+XQUL21y 0M3kzcrexSLUV6MsEn+J5LqFlotNbVc+1w5Wtm5uP2PkEdoLIWhQ/miPkkl1hY8Y7uUC pVHKH/a9XAh2SvUJUjeTFWnx5foCpwwM+1aK/MedNis1iKdZZzivwh4v3xBDJnPxqL/W poSrBMhm/onW/rGdQjW1fxqbB1sPfAM84nXRB8Xh1l83zLbQ/5hfkH7aMPs+AOGW0eIJ MwssIrH/eRlo0c5cuWOimg3fjcbC8WJCssY+NN+Wi3IUbP2/m9uWPUguz7IeYB7+zlFM /EUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=3mE3D4AWmHzirxTIheAplux7FGWSMVJlbT3TFFsh6EM=; b=mbAo+k3Bl1gbIFHuE+jWBw+h8Ct6EZq9qet8gM7i9YJrZCJC08lOMnr3G+ow+BNpqK x2RqzMz7aFHz+e7C6pU1gr+wwfPYMoDgyJRx6rypRAiuZcjo0c0mwAIHFAuHvVhnWiI9 ySCz8ad+cYS3kARIBY5vR+7mjCYP8kNeqk1AeNzNSRku4kh4uy05+qjR1diZkvw0Am+B oqPWASyB/CiQH7K60/x7v77prYUBCZGXIe7UTDTwlqLZ6G98AgUQrw1fymEwK0YuX760 0V2pztRauhc/YGTaR9JmDmpU62YE66BVdj+TGMPXd74/+VOEd/VQ6ekot5KVvv/+pbR+ 4tkw==
X-Gm-Message-State: AOPr4FUvvEkWIJRg2X2JWIZGs4ozGZXgbxrfCznSLvGovC0DeIu0dnWlMrWXKfGTNnZlog==
X-Received: by 10.157.29.201 with SMTP id w9mr10281425otw.196.1463162685259; Fri, 13 May 2016 11:04:45 -0700 (PDT)
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com. [209.85.223.175]) by smtp.gmail.com with ESMTPSA id 5sm5682839otg.27.2016.05.13.11.04.44 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 11:04:44 -0700 (PDT)
Received: by mail-io0-f175.google.com with SMTP id f89so142097630ioi.0 for <mmusic@ietf.org>; Fri, 13 May 2016 11:04:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.155.3 with SMTP id o3mr2840909itd.95.1463162684232; Fri, 13 May 2016 11:04:44 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Fri, 13 May 2016 11:04:44 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se>
Date: Fri, 13 May 2016 14:04:44 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com>
Message-ID: <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c05fb4e0ae15f0532bd1c4f
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KnnVKmcxh4gZ3_vZN8xbc9srEP4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 18:04:48 -0000

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

On Fri, May 13, 2016 at 9:35 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >Well, we can define new attribute as set of name value pairs, and define
> specific names for currently supported
>
> >hashes, such as "a=fp: sha1=base64val;sha256=base64val". New names can
> be added in the future to extend the
>
> >attribute and add new hash function support or other extensions.
>
>
>
> I think we can use the same values that are used for the current
> fingerprint attribute.
>
>
>
> hash-func              =  "sha-1" / "sha-224" / "sha-256" /
>
>                           "sha-384" / "sha-512" /
>
>                           "md5" / "md2" / token
>
>                           ; Additional hash functions can only come
>
>                           ; from updates to RFC 3279
>

The difference that current fingerprint attribute contains one hash value.
New attribute would be able to contain multiple hash values for a single
certificate. It can also be extended to provide other attributes for the
certificate, such as certificate common name, for which we can define new
matching rules. For instance in order to match the new attribute,
certificate must match all the hash values and the specified common name.

>Single attribute will refer to the single certificate, so all hashes in an
> attribute must match the currently used certificate for the new attribute
> to match.
>
>
>
> How do we associate an attribute with a certificate, so that the receiver
> can match the attribute (and the hashes) with the associated certificate?
>

We do not associate the new attribute with the certificate. All new
attribute does is specifies that all hashes within the single attribute
refer to the single certificate and should match at the same for the
specific certificate to match this attribute.

>New attribute can be used in parallel with old fingerprint attribute for
> backwards compatibility. Matching fingerprint attribute will follow
> existing rules (any one match of currently used >certificate is
> sufficient). New implementations MUST provide a new style attributes for
> each certificate used and MAY provide old style fingerprint attributes for
> backwards compatibility. >If new attribute is present, new implementations
> MUST only match new attributes and ignore the old fingerprint attribute.
> They MAY match old fingerprint attributes if new attributes are >not
> present.
>
>
>
> I think there are still different opinions on whether one match is enough,
> or whether all supported hashes should be tested.
>

If you want more secure match, you would need to use the new attribute. If
you use existing attribute you will use the match algorithm in existing
implementations, which currently allow a single fingerprint match. I have
mentioned earlier that Chrome, Firefox, Asterisk and Freeswitch currently
are looking for a single match. The algorithm that Martin proposed has, as
far as I know, no existing implementations.

I think this will give us the best of both worlds, backwards compatibility
> and security. Since only things that I know off that currently implement
> fingerprint attribute are WebRTC implementations, we can expect old
> fingerprint attributes to be retired within a reasonable time.
>
>
>
> >One unrelated editor note would be that I would prefer the new draft to
> overwrite RFC 4572 instead of updating a portion of it. I would also
>
> >like to rename it since the new draft covers not only connection
> oriented media (TLS) but also DTLS.
>
>
>
> Note that very little of the existing 4572 text would be modified. We
> would only clarify the restrictions associated with the fingerprint
> attribute.
>
>
>
4572 is a very small document. It mostly talks about fingerprints.

If we define the new attribute then it should definitely be a new document.

_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Fri, May 13, 2016 at 9:35 AM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">&gt;Well, we can define new attribute as set of name=
 value pairs, and define specific names for currently supported<br></p><div=
><span class=3D""><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span>hashes, such as &quot;a=3Dfp: sha1=3Dbase64val;sha256=
=3Dbase64val&quot;. New names can be added in the future to extend the
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span>attribute and add new hash function support or other e=
xtensions.<span style=3D"font-size:11pt;font-family:Calibri,sans-serif"><u>=
</u><u></u></span></p>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">I think we can use the same values that are used for the current =
fingerprint attribute.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">hash-func=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D=C2=A0 &quot;sha-1&quot; / &quot;sha-224&quo=
t; / &quot;sha-256&quot; /<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &quot;sha-384&quot; / &quot;sha-512&quot; /<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &quot;md5&quot; / &quot;md2&quot; / token<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 ; Additional hash functions can only come<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 ; from updates to RFC 3279</span></p></div></div></div></di=
v></blockquote><div><br></div><div>The difference that current fingerprint =
attribute contains one hash value. New attribute would be able to contain m=
ultiple hash values for a single certificate. It can also be extended to pr=
ovide other attributes for the certificate, such as certificate common name=
, for which we can define new matching rules. For instance in order to matc=
h the new attribute, certificate must match all the hash values and the spe=
cified common name.</div><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB=
" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D=
"font-size:10pt;font-family:&quot;Courier New&quot;"><u></u><u></u></span><=
/p>
<p class=3D"MsoNormal">&gt;Single attribute will refer to the single certif=
icate, so all hashes in an attribute must match the currently used certific=
ate for the new attribute to match.<br></p></div><span class=3D""><div><p c=
lass=3D"MsoNormal"><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">How do we associate an attribute with a certificate, so that the =
receiver can match the attribute (and the hashes) with the associated certi=
ficate?</span></p></div></div></blockquote><div>=C2=A0</div><div>We do not =
associate the new attribute with the certificate. All new attribute does is=
 specifies that all hashes within the single attribute refer to the single =
certificate and should match at the same for the specific certificate to ma=
tch this attribute.</div><div><br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:so=
lid;border-left-color:rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB=
" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D=
"font-size:11pt;font-family:Calibri,sans-serif"><u></u><u></u></span></p>
<p class=3D"MsoNormal">&gt;New attribute can be used in parallel with old f=
ingerprint attribute for backwards compatibility. Matching fingerprint attr=
ibute will follow existing rules (any one match of currently used &gt;certi=
ficate is sufficient). New implementations
 MUST provide a new style attributes for each certificate used and MAY prov=
ide old style fingerprint attributes for backwards compatibility. &gt;If ne=
w attribute is present, new implementations MUST only match new attributes =
and ignore the old fingerprint attribute.
 They MAY match old fingerprint attributes if new attributes are &gt;not pr=
esent.<br></p></div><span class=3D""><div><p class=3D"MsoNormal"><u></u></p=
>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">I think there are still different opinions on whether one match i=
s enough, or whether all supported hashes should be tested.</span></p></div=
></div></blockquote><div>=C2=A0</div><div>If you want more secure match, yo=
u would need to use the new attribute. If you use existing attribute you wi=
ll use the match algorithm in existing implementations, which currently all=
ow a single fingerprint match. I have mentioned earlier that Chrome, Firefo=
x, Asterisk and Freeswitch currently are looking for a single match. The al=
gorithm that Martin proposed has, as far as I know, no existing implementat=
ions.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-lef=
t-color:rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue=
" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D"font-size:11p=
t;font-family:Calibri,sans-serif"><u></u><u></u></span></p>
<p class=3D"MsoNormal">I think this will give us the best of both worlds, b=
ackwards compatibility and security. Since only things that I know off that=
 currently implement fingerprint attribute are WebRTC implementations, we c=
an expect old fingerprint attributes
 to be retired within a reasonable time.<br></p></div><span class=3D""><div=
><p class=3D"MsoNormal"><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&gt;One unrelated editor note would be that I would =
prefer the new draft to overwrite RFC=C2=A0<span style=3D"font-size:10pt;co=
lor:black">4572 instead of updating a portion of it. I would also
</span><span style=3D"font-size:10pt"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span><span style=3D"font-size:10pt;color:black">like to ren=
ame it since the new draft covers not only connection oriented media (TLS) =
but also DTLS. =C2=A0 =C2=A0 =C2=A0</span><span style=3D"font-size:11pt;fon=
t-family:Calibri,sans-serif"><u></u><u></u></span></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">Note that very little of the existing 4572 text would be modified=
. We would only clarify the restrictions associated with the fingerprint at=
tribute.</span><span style=3D"font-family:Calibri,sans-serif;font-size:11pt=
">=C2=A0</span></p>
<p class=3D"MsoNormal"><br></p></div></div></blockquote><div><br></div><div=
>4572 is a very small document. It mostly talks about fingerprints.=C2=A0</=
div><div><br></div><div>If we define the new attribute then it should defin=
itely be a new document.</div><div><br></div><div><div class=3D"gmail_signa=
ture">_____________<br>Roman Shpount</div></div><div>=C2=A0</div></div></di=
v></div>

--94eb2c05fb4e0ae15f0532bd1c4f--


From nobody Fri May 13 11:12:15 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE55F12D1B7 for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 11:12:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwFDfQXRPQ6O for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 11:12:08 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10E0312D0EF for <mmusic@ietf.org>; Fri, 13 May 2016 11:12:07 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id f89so142345717ioi.0 for <mmusic@ietf.org>; Fri, 13 May 2016 11:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=KwYWnklOZMwgIGh57lKLIm8nEWrIctDp4nuoy01UFbU=; b=2GuDmY29LKMfayl8PZUPIZMTige2wXTmbNKKejgrlN5djJiAcOO43hUdcNJ+G0VSi/ sb5318G1+4pzzArfG/BAlbZGWZiADEhzma/6jZ2qvijpczgCuiejFrBtaek5nPLH9NeJ pkaPMnVEAV0oeORzBgGyDLUgLuonR+d12oeO46nUfCqfGL8xJ16UeQ/9j8W7zIcyMAoE w2pPuWRLt1ogC8Vz6dj3VjsV9ebKffTAzfSGeBqV0w6FLFBa2AIKxM/jjJ50dU72nBId 7wgQyYeDyXejbslYN/OAc8r+dlpkye4clsw4H/n63umeTEwQ1f03YZxqIC5U8fmkFYK6 Uf4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=KwYWnklOZMwgIGh57lKLIm8nEWrIctDp4nuoy01UFbU=; b=Snv5ph2I8rHsbwHmvkAVPXDOt02DvObBPwe2blegJ9vAwc3+3ZW7pYKsCBhh8yOEts d5CmQ+E106HM0y7q7ZfVQewGNzpnMcKuEFuGMpzM5mrA2Y1tAXzw+jZZ3/OPSHPEInfl kBL9Ve5sOgv5Mmn/ScfZhp74xAxyldWzZPfHIMzJpSv+sLoUtcN3i2PiymQxORnra8UO POHrpxZaAaM6C4U4QO4nyklSYD6QuhHpVq6VI8yzbMIDT/JytBX24Os3lN0AFLORlWDi tt8VqwCSvIh7uBvzFIpnBJyChm/evfCNm9vrrfJf0c5cDGkVJz2cy2ftkKhQUv2gw1YW aZYA==
X-Gm-Message-State: AOPr4FXXF01t/heIZ9ce3dT4hCsIgFvAcHW+QZqlxavsbUYjIxgf4Mr3gUpU+cJGdsjrFQ==
X-Received: by 10.36.14.18 with SMTP id 18mr2658349ite.70.1463163127305; Fri, 13 May 2016 11:12:07 -0700 (PDT)
Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com. [209.85.213.181]) by smtp.gmail.com with ESMTPSA id h6sm1314842ita.17.2016.05.13.11.12.06 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 May 2016 11:12:06 -0700 (PDT)
Received: by mail-ig0-f181.google.com with SMTP id qe5so13010694igc.1 for <mmusic@ietf.org>; Fri, 13 May 2016 11:12:06 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.150.42 with SMTP id uf10mr1689395igb.95.1463163126024; Fri, 13 May 2016 11:12:06 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Fri, 13 May 2016 11:12:05 -0700 (PDT)
In-Reply-To: <a834657e-ab8e-e33d-ceee-3e5727130363@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <8a205f3a-a9cf-9c57-70f3-87923d7c07d1@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FA2314@ESESSMB209.ericsson.se> <a834657e-ab8e-e33d-ceee-3e5727130363@alum.mit.edu>
Date: Fri, 13 May 2016 14:12:05 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtiywzHNV20=FWaVoN3BbykX0Hr7NdXzLsVR__UQOj15Q@mail.gmail.com>
Message-ID: <CAD5OKxtiywzHNV20=FWaVoN3BbykX0Hr7NdXzLsVR__UQOj15Q@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=001a1134cff260285e0532bd36a4
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/jBOowK6AXkpKby6KxCGHEEuCho8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 18:12:10 -0000

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

On Fri, May 13, 2016 at 10:55 AM, Paul Kyzivat <pkyzivat@alum.mit.edu>
wrote:

> If the answerer supports the attribute, it MUST include it in the answer.
>>
>
> That is what I was thinking.
>

Agreed. This is what I was thinking as well.


> What about the case where the answerer is the one that will be sending the
> certificate, and hence needs to send the fingerprints? That might not be
> common, but it might be possible.
>

I am not sure what you mean. Both sides send their certificate when
connection is established, so both sides must send fingerprints.


>
> Also, should the fingerprint in a=fingerprint be repeated in the new
>>> attribute? Or should the new attribute just be used for additional
>>> fingerprints?
>>>
>>
>> I see no reason to not allow a hash to be included in both attributes.
>>
>
> Nor do I. But it is worth considering how best to migrate. If you need to
> include a=fingerprint anyway, for backward compatibility, then it might
> make sense to simply use the new attribute for *additional* fingerprints.
>

If we use new attribute for additional fingerprints we will need to figure
out which a=fingerprint attribute contains the "primary". If everything is
in one attribute, a=fingerprint attributes can be simply ignored if new
attributes are present.

I don't feel strongly about this. But it is good to be clear what the
> expectation is. If both attributes are present, and the fingerprint in
> a=fingerprint is *not* present in the new attribute, must it still match to
> *some* certificate?


What I proposed was that if new attributes are present in the offer and
implementation supports new attribute, one new attribute must match the
certificate and a=fingerprint attributes must be ignored. Answer must
contain only new attributes. If new attributes are not present in the
offer, this will mean that the offer came from the legacy implementation,
or if new attribute is not supported, one a=fingerprint attribute must
match the certificate. New attributes must not be present in the answer and
answer should contain a=fingerprint attributes.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Fri, May 13, 2016 at 10:55 AM, Paul Kyzivat <span dir=3D"ltr">&lt;<=
a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit=
.edu</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding=
-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204=
,204,204);padding-left:1ex">If the answerer supports the attribute, it MUST=
 include it in the answer.<br>
</blockquote>
<br>
That is what I was thinking.<br></blockquote><div><br></div><div>Agreed. Th=
is is what I was thinking as well.</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo=
rder-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">=
What about the case where the answerer is the one that will be sending the =
certificate, and hence needs to send the fingerprints? That might not be co=
mmon, but it might be possible.<br></blockquote><div><br></div><div>I am no=
t sure what you mean. Both sides send their certificate when connection is =
established, so both sides must send fingerprints.</div><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pad=
ding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">
Also, should the fingerprint in a=3Dfingerprint be repeated in the new attr=
ibute? Or should the new attribute just be used for additional fingerprints=
?<br>
</blockquote>
<br>
I see no reason to not allow a hash to be included in both attributes.<br>
</blockquote>
<br>
Nor do I. But it is worth considering how best to migrate. If you need to i=
nclude a=3Dfingerprint anyway, for backward compatibility, then it might ma=
ke sense to simply use the new attribute for *additional* fingerprints.<br>=
</blockquote><div><br></div><div>If we use new attribute for additional fin=
gerprints we will need to figure out which a=3Dfingerprint attribute contai=
ns the &quot;primary&quot;. If everything is in one attribute, a=3Dfingerpr=
int attributes can be simply ignored if new attributes are present.</div><d=
iv><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(2=
04,204,204);padding-left:1ex">I don&#39;t feel strongly about this. But it =
is good to be clear what the expectation is. If both attributes are present=
, and the fingerprint in a=3Dfingerprint is *not* present in the new attrib=
ute, must it still match to *some* certificate?</blockquote><div><br></div>=
<div>What I proposed was that if new attributes are present in the offer an=
d implementation supports new attribute, one new attribute must match the c=
ertificate and a=3Dfingerprint attributes must be ignored. Answer must cont=
ain only new attributes. If new attributes are not present in the offer, th=
is will mean that the offer came from the legacy implementation, or if new =
attribute is not supported, one a=3Dfingerprint attribute must match the ce=
rtificate. New attributes must not be present in the answer and answer shou=
ld contain a=3Dfingerprint attributes.</div><div><br></div><div>Regards,</d=
iv><div>_____________</div><div>Roman Shpount=C2=A0</div></div></div></div>

--001a1134cff260285e0532bd36a4--


From nobody Fri May 13 13:43:58 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B12812D17E for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 13:43:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkHXTgR0hMi7 for <mmusic@ietfa.amsl.com>; Fri, 13 May 2016 13:43:55 -0700 (PDT)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95FAF12B005 for <mmusic@ietf.org>; Fri, 13 May 2016 13:43:53 -0700 (PDT)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by comcast with SMTP id 1Jorbf5MdbFYY1Jw8bxnIc; Fri, 13 May 2016 20:43:52 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463172232; bh=Cw5S40wP7ZpGjZHr6wP7qmZhfeGNOr2zz4Z4PBmBO5Q=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=I3e/2nSMc8p5ZOnJEhxq1sZorVFwWjsjWo3cj3bsGx3Dl7u5+z8GIErzLEYAnLxXX gUmDRGazJJq8ONvmid8Q9P+FzcyHwmCztYNLd1Ep3P54D3aqdMRMjg1e7Efcvz5TT+ a1/PR+IzzTLO7chjOmTfs0OYy1mBhZnhy5kQJAKF9HoCueK9Orp2M1AnOjB5tJGKNb FCBLqltNNgRj1v4Idg0peYfwkyKp0HrwZbty50SSjYAwKpbYDfvoKdJxGl9UGmgfJ6 CI9a2OvAxU0cwGz0PwBSRlvUb2vVDoUQB40T3Hdd1K9tKJuDXCrSf6TXmyl203Xwu7 ak8dTtgKayC+Q==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-14v.sys.comcast.net with comcast id twjs1s00C3KdFy101wjsrt; Fri, 13 May 2016 20:43:52 +0000
To: Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <8a205f3a-a9cf-9c57-70f3-87923d7c07d1@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FA2314@ESESSMB209.ericsson.se> <a834657e-ab8e-e33d-ceee-3e5727130363@alum.mit.edu> <CAD5OKxtiywzHNV20=FWaVoN3BbykX0Hr7NdXzLsVR__UQOj15Q@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <9e8216d1-28f7-3e5f-e0fa-59540f465d06@alum.mit.edu>
Date: Fri, 13 May 2016 16:43:51 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxtiywzHNV20=FWaVoN3BbykX0Hr7NdXzLsVR__UQOj15Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/_nmhtaSjqsB1C3MVUnZm0q8kIwM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2016 20:43:57 -0000

On 5/13/16 2:12 PM, Roman Shpount wrote:
> On Fri, May 13, 2016 at 10:55 AM, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>
>         If the answerer supports the attribute, it MUST include it in
>         the answer.
>
>
>     That is what I was thinking.
>
>
> Agreed. This is what I was thinking as well.
>
>
>     What about the case where the answerer is the one that will be
>     sending the certificate, and hence needs to send the fingerprints?
>     That might not be common, but it might be possible.
>
>
> I am not sure what you mean. Both sides send their certificate when
> connection is established, so both sides must send fingerprints.

Oh, ok.

>             Also, should the fingerprint in a=fingerprint be repeated in
>             the new attribute? Or should the new attribute just be used
>             for additional fingerprints?
>
>
>         I see no reason to not allow a hash to be included in both
>         attributes.
>
>
>     Nor do I. But it is worth considering how best to migrate. If you
>     need to include a=fingerprint anyway, for backward compatibility,
>     then it might make sense to simply use the new attribute for
>     *additional* fingerprints.
>
>
> If we use new attribute for additional fingerprints we will need to
> figure out which a=fingerprint attribute contains the "primary". If
> everything is in one attribute, a=fingerprint attributes can be simply
> ignored if new attributes are present.

That can work. We just need to be clear about it.

>     I don't feel strongly about this. But it is good to be clear what
>     the expectation is. If both attributes are present, and the
>     fingerprint in a=fingerprint is *not* present in the new attribute,
>     must it still match to *some* certificate?
>
>
> What I proposed was that if new attributes are present in the offer and
> implementation supports new attribute, one new attribute must match the
> certificate and a=fingerprint attributes must be ignored. Answer must
> contain only new attributes. If new attributes are not present in the
> offer, this will mean that the offer came from the legacy
> implementation, or if new attribute is not supported, one a=fingerprint
> attribute must match the certificate. New attributes must not be present
> in the answer and answer should contain a=fingerprint attributes.

That language seems to work.

	Thanks,
	Paul


From nobody Sat May 14 00:38:46 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91DA12D148 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 00:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LPPDRXlS1u_l for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 00:38:42 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEB0412B077 for <mmusic@ietf.org>; Sat, 14 May 2016 00:38:41 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-ad-5736d5ff4ac9
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id CC.C6.12516.FF5D6375; Sat, 14 May 2016 09:38:39 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0248.002; Sat, 14 May 2016 09:38:31 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw
Date: Sat, 14 May 2016 07:38:31 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com>
In-Reply-To: <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM2K7q+7/q2bhBocOqljcnP+WxeLamX+M FlOXP2axWLHhAKvFjAtTmR1YPf6+/8DksXPWXXaPJUt+MnncmlIQwBLFZZOSmpNZllqkb5fA lTFr/hamgn9aFftepzQwftDsYuTkkBAwkZj/chIzhC0mceHeejYQW0jgCKPE+hPJEPYSRomu ebldjBwcbAIWEt3/tEHCIgKqEn+/T2YCsZkFljFK7HzHA2ILC3hKXD/9mQ2ixkviwtQF7F2M XED2PkaJBe3NzCBzWICa+zp0QGp4BXwlTt64xQJSIyTwmkuiYc4SJpAaToFAiaP7xEBqGIFO +35qDdQucYlbT+YzQZwsILFkz3mo80UlXj7+xwphK0k0LnnCCjKGWUBTYv0ufYhWRYkp3Q/Z IdYKSpyc+YRlAqPYLCRTZyF0zELSMQtJxwJGllWMosWpxcW56UbGeqlFmcnFxfl5enmpJZsY gVF2cMtv3R2Mq187HmIU4GBU4uF9sM8sXIg1say4MvcQowQHs5IIb/t5oBBvSmJlVWpRfnxR aU5q8SFGaQ4WJXFe/5eK4UIC6YklqdmpqQWpRTBZJg5OqQbG0G8fRN4Gt/wN1p7cnnx6f+7c F86nfsx7dm7H8slHgv7JivybL275RECTW3H/RPuz9oevXCi03Nf0uHHuepP8f+qTfmiuexg9 N+3TzCl8Gwp4v8w+xZKSEj2Di+V2T/j8Z7vsvbk8ypaL3s/dzWCyQen9kbf12T/eqWnGa21Q MM6Orq/bb1LnpMRSnJFoqMVcVJwIAG/rYyiuAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/V6Q883VcTiHLZg3zS-w9qROKeEc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 07:38:44 -0000

SGksDQoNCj4+PldlbGwsIHdlIGNhbiBkZWZpbmUgbmV3IGF0dHJpYnV0ZSBhcyBzZXQgb2YgbmFt
ZSB2YWx1ZSBwYWlycywgYW5kIGRlZmluZSBzcGVjaWZpYyBuYW1lcyBmb3IgY3VycmVudGx5IHN1
cHBvcnRlZA0KPj4+aGFzaGVzLCBzdWNoIGFzICJhPWZwOiBzaGExPWJhc2U2NHZhbDtzaGEyNTY9
YmFzZTY0dmFsIi4gTmV3IG5hbWVzIGNhbiBiZSBhZGRlZCBpbiB0aGUgZnV0dXJlIHRvIGV4dGVu
ZCB0aGUNCj4+PmF0dHJpYnV0ZSBhbmQgYWRkIG5ldyBoYXNoIGZ1bmN0aW9uIHN1cHBvcnQgb3Ig
b3RoZXIgZXh0ZW5zaW9ucy4NCj4+DQo+PkkgdGhpbmsgd2UgY2FuIHVzZSB0aGUgc2FtZSB2YWx1
ZXMgdGhhdCBhcmUgdXNlZCBmb3IgdGhlIGN1cnJlbnQgZmluZ2VycHJpbnQgYXR0cmlidXRlLg0K
Pj7CoA0KPj5oYXNoLWZ1bmPCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA9wqAgInNoYS0xIiAv
ICJzaGEtMjI0IiAvICJzaGEtMjU2IiAvDQo+PsKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgICJzaGEtMzg0IiAvICJzaGEtNTEyIiAvDQo+PsKgwqDCoMKg
wqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgICJtZDUiIC8gIm1kMiIg
LyB0b2tlbg0KPj7CoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKg
wqDCoCA7IEFkZGl0aW9uYWwgaGFzaCBmdW5jdGlvbnMgY2FuIG9ubHkgY29tZQ0KPj7CoMKgwqDC
oMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoMKgwqDCoCA7IGZyb20gdXBkYXRl
cyB0byBSRkMgMzI3OQ0KPg0KPlRoZSBkaWZmZXJlbmNlIHRoYXQgY3VycmVudCBmaW5nZXJwcmlu
dCBhdHRyaWJ1dGUgY29udGFpbnMgb25lIGhhc2ggdmFsdWUuIE5ldyBhdHRyaWJ1dGUgd291bGQg
YmUgYWJsZSB0byBjb250YWluIG11bHRpcGxlIGhhc2ggdmFsdWVzIGZvciBhIHNpbmdsZSBjZXJ0
aWZpY2F0ZS4NCg0KWWVzLCBidXQgSSB3YXMgb25seSB0YWxraW5nIGFib3V0IHRoZSB2YWx1ZSBv
ZiB0aGUgaGFzaCBmdW5jdGlvbi4gDQoNCj5JdCBjYW4gYWxzbyBiZSBleHRlbmRlZCB0byBwcm92
aWRlIG90aGVyIGF0dHJpYnV0ZXMgZm9yIHRoZSBjZXJ0aWZpY2F0ZSwgc3VjaCBhcyBjZXJ0aWZp
Y2F0ZSBjb21tb24gbmFtZSwgZm9yIHdoaWNoIHdlDQo+Y2FuIGRlZmluZSBuZXcgbWF0Y2hpbmcg
cnVsZXMuIEZvciBpbnN0YW5jZSBpbiBvcmRlciB0byBtYXRjaCB0aGUgbmV3IGF0dHJpYnV0ZSwg
Y2VydGlmaWNhdGUgbXVzdCBtYXRjaCBhbGwgdGhlIGhhc2ggdmFsdWVzIA0KPmFuZCB0aGUgc3Bl
Y2lmaWVkIGNvbW1vbiBuYW1lLg0KDQpXZSBjYW4gZm9yIHN1cmUgYWxsb3cgZm9yIGV4dGVuZGli
aWxpdHksIGJ1dCBzdWNoIGV4dGVuc2lvbnMgYXJlIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoZSBj
dXJyZW50IHdvcmsgSU1PLg0KDQo+Pj4gU2luZ2xlIGF0dHJpYnV0ZSB3aWxsIHJlZmVyIHRvIHRo
ZSBzaW5nbGUgY2VydGlmaWNhdGUsIHNvIGFsbCBoYXNoZXMgaW4gYW4gYXR0cmlidXRlIG11c3Qg
bWF0Y2ggdGhlIGN1cnJlbnRseSB1c2VkIGNlcnRpZmljYXRlIGZvciB0aGUgbmV3IGF0dHJpYnV0
ZSB0byBtYXRjaC4NCj4+DQo+PiBIb3cgZG8gd2UgYXNzb2NpYXRlIGFuIGF0dHJpYnV0ZSB3aXRo
IGEgY2VydGlmaWNhdGUsIHNvIHRoYXQgdGhlIHJlY2VpdmVyIGNhbiBtYXRjaCB0aGUgYXR0cmli
dXRlIChhbmQgdGhlIGhhc2hlcykgd2l0aCB0aGUgYXNzb2NpYXRlZCBjZXJ0aWZpY2F0ZT8NCj7C
oA0KPiBXZSBkbyBub3QgYXNzb2NpYXRlIHRoZSBuZXcgYXR0cmlidXRlIHdpdGggdGhlIGNlcnRp
ZmljYXRlLiBBbGwgbmV3IGF0dHJpYnV0ZSBkb2VzIGlzIHNwZWNpZmllcyB0aGF0IGFsbCBoYXNo
ZXMgd2l0aGluIHRoZSANCj4gc2luZ2xlIGF0dHJpYnV0ZSByZWZlciB0byB0aGUgc2luZ2xlIGNl
cnRpZmljYXRlIGFuZCBzaG91bGQgbWF0Y2ggYXQgdGhlIHNhbWUgZm9yIHRoZSBzcGVjaWZpYyBj
ZXJ0aWZpY2F0ZSB0byBtYXRjaCB0aGlzIGF0dHJpYnV0ZS4NCg0KWWVzLiBCdXQsIG15IGlkZWEg
d2FzIHRvIGluZGljYXRlIGluIHRoZSBhdHRyaWJ1dGUgd2l0aCB3aGljaCBjZXJ0aWZpY2F0ZSB0
aGUgYXR0cmlidXRlIGhhc2goZXMpIGFyZSBhc3NvY2lhdGVkIHdpdGgsIHNvIHRoYXQgdGhlIHJl
Y2VpdmVyIGRvZXMgbm90IG5lZWQgdG8gY2hlY2sgdGhlIGhhc2hlcyB3aXRoaW4gYWxsIGF0dHJp
YnV0ZXMuDQoNCkV4YW1wbGU6DQoNCmE9ZnA6Y2VydFg7c2hhLTE6PGhhc2g+O3NoYS0yNTY6PGhh
c2g+DQphPWZwOmNlcnRZOnNoYS0xOjxoYXNoPjtzaGEtMjU2OjxoYXNoPg0KDQpJbiB0aGlzIGNh
c2UsIGlmIGNlcnRYIGVuZHMgdXAgYmVpbmcgc2VsZWN0ZWQsIHRoZSBlbmRwb2ludCBrbm93cyB3
aGljaCBoYXNoZXMgaXQgc2hvdWxkIGNoZWNrLCBhbmQgZG9lcyBub3QgbmVlZCB0byB0cnkgdGhl
IG90aGVycyBpbiBvcmRlciB0byBmaW5kIHRoZSBtYXRjaC4NCg0KPj4+IE5ldyBhdHRyaWJ1dGUg
Y2FuIGJlIHVzZWQgaW4gcGFyYWxsZWwgd2l0aCBvbGQgZmluZ2VycHJpbnQgYXR0cmlidXRlIGZv
ciBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eS4gTWF0Y2hpbmcgZmluZ2VycHJpbnQgYXR0cmlidXRl
IHdpbGwgZm9sbG93IA0KPj4+IGV4aXN0aW5nIHJ1bGVzIChhbnkgb25lIG1hdGNoIG9mIGN1cnJl
bnRseSB1c2VkIGNlcnRpZmljYXRlIGlzIHN1ZmZpY2llbnQpLiBOZXcgaW1wbGVtZW50YXRpb25z
IE1VU1QgcHJvdmlkZSBhIG5ldyBzdHlsZSBhdHRyaWJ1dGVzIGZvciANCj4+PiBlYWNoIGNlcnRp
ZmljYXRlIHVzZWQgYW5kIE1BWSBwcm92aWRlIG9sZCBzdHlsZSBmaW5nZXJwcmludCBhdHRyaWJ1
dGVzIGZvciBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eS4gSWYgbmV3IGF0dHJpYnV0ZSBpcyBwcmVz
ZW50LCBuZXcgDQo+Pj4gaW1wbGVtZW50YXRpb25zIE1VU1Qgb25seSBtYXRjaCBuZXcgYXR0cmli
dXRlcyBhbmQgaWdub3JlIHRoZSBvbGQgZmluZ2VycHJpbnQgYXR0cmlidXRlLiBUaGV5IE1BWSBt
YXRjaCBvbGQgZmluZ2VycHJpbnQgYXR0cmlidXRlcyBpZiANCj4+PiBuZXcgYXR0cmlidXRlcyBh
cmUgbm90IHByZXNlbnQuDQo+PsKgDQo+PiBJIHRoaW5rIHRoZXJlIGFyZSBzdGlsbCBkaWZmZXJl
bnQgb3BpbmlvbnMgb24gd2hldGhlciBvbmUgbWF0Y2ggaXMgZW5vdWdoLCBvciB3aGV0aGVyIGFs
bCBzdXBwb3J0ZWQgaGFzaGVzIHNob3VsZCBiZSB0ZXN0ZWQuDQo+DQo+IElmIHlvdSB3YW50IG1v
cmUgc2VjdXJlIG1hdGNoLCB5b3Ugd291bGQgbmVlZCB0byB1c2UgdGhlIG5ldyBhdHRyaWJ1dGUu
IElmIHlvdSB1c2UgZXhpc3RpbmcgYXR0cmlidXRlIHlvdSB3aWxsIHVzZSB0aGUgbWF0Y2ggDQo+
IGFsZ29yaXRobSBpbiBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnMsIHdoaWNoIGN1cnJlbnRseSBh
bGxvdyBhIHNpbmdsZSBmaW5nZXJwcmludCBtYXRjaC4gSSBoYXZlIG1lbnRpb25lZCBlYXJsaWVy
IHRoYXQgDQo+IENocm9tZSwgRmlyZWZveCwgQXN0ZXJpc2sgYW5kIEZyZWVzd2l0Y2ggY3VycmVu
dGx5IGFyZSBsb29raW5nIGZvciBhIHNpbmdsZSBtYXRjaC4gVGhlIGFsZ29yaXRobSB0aGF0IE1h
cnRpbiBwcm9wb3NlZCANCj4gaGFzLCBhcyBmYXIgYXMgSSBrbm93LCBubyBleGlzdGluZyBpbXBs
ZW1lbnRhdGlvbnMuDQoNCk15IHBvaW50IHdhczogaWYgdGhlIG5ldyBhdHRyaWJ1dGUgaXMgdXNl
ZCwgZG8gd2UgcmVxdWlyZSBhbGwgaGFzaGVzIHdpdGhpbiB0aGUgYXR0cmlidXRlIHRvIG1hdGNo
LCBvciBpcyBpdCBlbm91Z2ggaWYgdGhlIHJlY2VpdmVyIGNoZWNrcyBvbmUgb2YgdGhlIGhhc2hl
cyB3aXRoaW4gdGhlIGF0dHJpYnV0ZS4NCg0KRXhhbXBsZToNCg0KYT1mcDpjZXJ0WDtzaGEtMTo8
aGFzaD47c2hhLTI1Njo8aGFzaD4NCg0KSWYgY2VydFggaXMgc2VsZWN0ZWQsIGlzIHRoZSByZWNl
aXZlciByZXF1aXJlZCB0byBjaGVjayBib3RoIHRoZSBzaGEtMSBhbmQgc2hhLTI1NiBoYXNoZXM/
DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQrCoA0K


From nobody Sat May 14 01:24:01 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F81812D153 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 01:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0_6hoxzOtQUq for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 01:23:56 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A547F12B069 for <mmusic@ietf.org>; Sat, 14 May 2016 01:23:56 -0700 (PDT)
Received: by mail-ig0-x22a.google.com with SMTP id s8so21086844ign.0 for <mmusic@ietf.org>; Sat, 14 May 2016 01:23:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=M8xbEmA/nhh5sldeysPn5yrjTiE3SZY1JuyW1HNpSfA=; b=dP7zI+Q1i8Nu7PAQdeIbNhxooAzw3Bs/0WPMIoq1v8WZlZKw56qUY8gE3HuCYInp2g mu2iy/J/1YLJn6VYmF8gm7DUKQaCrhnag8/KL5egUIoJfPTo57o8B1HQQEyitpexotvJ oNije2y3qIGiTgLSvA6mHFBN3DcwKDBtDTX1oCYClax958F9XU4uiz9r/shl7ifOST5h e3D4CoskTzFkt3uS+ciYmcfZ0QhDRhLLYWM/jIXkT0D6yD5WwU5h8VSMhiWDb+uey+Ye m0pLZsq+q5GQu6erjdhtdtcU3JjRepcGLGy6nzCg7cI1QMAHCXsz85AbEpZf08y2QrE1 ynqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=M8xbEmA/nhh5sldeysPn5yrjTiE3SZY1JuyW1HNpSfA=; b=eYXjDuEG7LeP7wQ5aqY/sfDEHGoBNYUi7Zr+ZBX73on3uLqmy4Jg150gygiAMQpNzG sx4uWF4Apgk45tyNpsDHC2gavNnx6Y0Qg/4iSawbvZtZyOtrHHSsinK4TvzmHkfbAG/m njyp2hzpAZ2dExLzI5PFixVs2mZjhHX61sAWRcXmB6OQAlfXAo+UphJ4FIgE0IYN4fQo XKNP9H9JyT/D+QynzZuCN9gFkALy/Z2qIwkbG9gi/DW4QsaIoyVa/GO+dXTgHPWNRBRS dAGkQeh3oNkgBtJL/aMpSZtG6UMd6lSHVNTqDAKPRVI5TOLZD8++TzBT74ZBj8L8HH0O hh/A==
X-Gm-Message-State: AOPr4FWlKF0Uj/6URssezg3CPiHmgi1FYvZdFq53B7UdPb85gSfLDMUqxOyjSOYyOTZF5A==
X-Received: by 10.50.101.131 with SMTP id fg3mr2942490igb.75.1463214235869; Sat, 14 May 2016 01:23:55 -0700 (PDT)
Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com. [209.85.213.178]) by smtp.gmail.com with ESMTPSA id p194sm2256485itc.16.2016.05.14.01.23.54 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 14 May 2016 01:23:54 -0700 (PDT)
Received: by mail-ig0-f178.google.com with SMTP id bi2so26019392igb.0 for <mmusic@ietf.org>; Sat, 14 May 2016 01:23:54 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.37.147 with SMTP id y19mr4702091igj.42.1463214234475; Sat, 14 May 2016 01:23:54 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Sat, 14 May 2016 01:23:54 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se>
Date: Sat, 14 May 2016 04:23:54 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuTvkNyMkyWXMWEL60T6zpbmi6cXve557bL9x8SkOsu2A@mail.gmail.com>
Message-ID: <CAD5OKxuTvkNyMkyWXMWEL60T6zpbmi6cXve557bL9x8SkOsu2A@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=f46d0444006ead29150532c91c7b
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/FppICemvSkG0GnOyEcDldP4PC7Q>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 08:23:59 -0000

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

On Sat, May 14, 2016 at 3:38 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >It can also be extended to provide other attributes for the certificate,
> such as certificate common name, for which we
> >can define new matching rules. For instance in order to match the new
> attribute, certificate must match all the hash values
> >and the specified common name.
>
> We can for sure allow for extendibility, but such extensions are outside
> the scope of the current work IMO.
>

Agreed. All I am saying we have a framework to extend in the future if
needed.


> >>> Single attribute will refer to the single certificate, so all hashes
> in an attribute must match the currently used certificate for the new
> attribute to match.
> >>
> >> How do we associate an attribute with a certificate, so that the
> receiver can match the attribute (and the hashes) with the associated
> certificate?
> >
> > We do not associate the new attribute with the certificate. All new
> attribute does is specifies that all hashes within the
> > single attribute refer to the single certificate and should match at the
> same for the specific certificate to match this attribute.
>
> Yes. But, my idea was to indicate in the attribute with which certificate
> the attribute hash(es) are associated with, so that the receiver does not
> need to check the hashes within all attributes.
>
> Example:
>
> a=fp:certX;sha-1:<hash>;sha-256:<hash>
> a=fp:certY:sha-1:<hash>;sha-256:<hash>
>
> In this case, if certX ends up being selected, the endpoint knows which
> hashes it should check, and does not need to try the others in order to
> find the match.
>

What are certX and certY values? What do you use to identify the
certificate? Common Name? Something else? Whatever it is, it can be just
one more named parameter.

What I expected was that hash value itself is the certificate identifier.
There are various ways to optimize the match process, if you cash the
calculated hash values for the certificate, so I do not think it will use a
lot of resources.

Also, I would prefer if we keep the format
"a=fp:sha-1=<base64hash>;sha-256=<base64hash>". This is the standard URL
parameter format so it would require one less parser to support.

>>> New attribute can be used in parallel with old fingerprint attribute
> for backwards compatibility. Matching fingerprint attribute will follow
> >>> existing rules (any one match of currently used certificate is
> sufficient). New implementations MUST provide a new style attributes for
> >>> each certificate used and MAY provide old style fingerprint attributes
> for backwards compatibility. If new attribute is present, new
> >>> implementations MUST only match new attributes and ignore the old
> fingerprint attribute. They MAY match old fingerprint attributes if
> >>> new attributes are not present.
> >>
> >> I think there are still different opinions on whether one match is
> enough, or whether all supported hashes should be tested.
> >
> > If you want more secure match, you would need to use the new attribute.
> If you use existing attribute you will use the match
> > algorithm in existing implementations, which currently allow a single
> fingerprint match. I have mentioned earlier that
> > Chrome, Firefox, Asterisk and Freeswitch currently are looking for a
> single match. The algorithm that Martin proposed
> > has, as far as I know, no existing implementations.
>
> My point was: if the new attribute is used, do we require all hashes
> within the attribute to match, or is it enough if the receiver checks one
> of the hashes within the attribute.
>
> Example:
>
> a=fp:certX;sha-1:<hash>;sha-256:<hash>
>
> If certX is selected, is the receiver required to check both the sha-1 and
> sha-256 hashes?


Checking all hashes would be more secure, so I would make it a "SHOULD".
Implementations can decide to check the subset of all the hashes if they
decided it provides sufficient security, as in checking the most secure
hash only.

Regards,
______________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Sat, May 14, 2016 at 3:38 AM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"><span class=3D"">&gt;It can also be exten=
ded to provide other attributes for the certificate, such as certificate co=
mmon name, for which we<br>
&gt;can define new matching rules. For instance in order to match the new a=
ttribute, certificate must match all the hash values<br>
&gt;and the specified common name.<br>
<br>
</span>We can for sure allow for extendibility, but such extensions are out=
side the scope of the current work IMO.<br></blockquote><div><br></div><div=
>Agreed. All I am saying we have a framework to extend in the future if nee=
ded.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-le=
ft-color:rgb(204,204,204);padding-left:1ex"><span class=3D"">&gt;&gt;&gt; S=
ingle attribute will refer to the single certificate, so all hashes in an a=
ttribute must match the currently used certificate for the new attribute to=
 match.<br>
&gt;&gt;<br>
&gt;&gt; How do we associate an attribute with a certificate, so that the r=
eceiver can match the attribute (and the hashes) with the associated certif=
icate?<br>
&gt;=C2=A0<br>
&gt; We do not associate the new attribute with the certificate. All new at=
tribute does is specifies that all hashes within the<br>
&gt; single attribute refer to the single certificate and should match at t=
he same for the specific certificate to match this attribute.<br>
<br>
</span>Yes. But, my idea was to indicate in the attribute with which certif=
icate the attribute hash(es) are associated with, so that the receiver does=
 not need to check the hashes within all attributes.<br>
<br>
Example:<br>
<br>
a=3Dfp:certX;sha-1:&lt;hash&gt;;sha-256:&lt;hash&gt;<br>
a=3Dfp:certY:sha-1:&lt;hash&gt;;sha-256:&lt;hash&gt;<br>
<br>
In this case, if certX ends up being selected, the endpoint knows which has=
hes it should check, and does not need to try the others in order to find t=
he match.<br></blockquote><div><br></div><div>What are certX and certY valu=
es? What do you use to identify the certificate? Common Name? Something els=
e? Whatever it is, it can be just one more named parameter.</div><div><br><=
/div><div>What I expected was that hash value itself is the certificate ide=
ntifier. There are various ways to optimize the match process, if you cash =
the calculated hash values for the certificate, so I do not think it will u=
se a lot of resources.</div><div><br></div><div>Also, I would prefer if we =
keep the format &quot;a=3Dfp:sha-1=3D&lt;base64hash&gt;;sha-256=3D&lt;base6=
4hash&gt;&quot;. This is the standard URL parameter format so it would requ=
ire one less parser to support.</div><div><br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-l=
eft-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span =
class=3D"">&gt;&gt;&gt; New attribute can be used in parallel with old fing=
erprint attribute for backwards compatibility. Matching fingerprint attribu=
te will follow<br>
&gt;&gt;&gt; existing rules (any one match of currently used certificate is=
 sufficient). New implementations MUST provide a new style attributes for<b=
r>
&gt;&gt;&gt; each certificate used and MAY provide old style fingerprint at=
tributes for backwards compatibility. If new attribute is present, new<br>
&gt;&gt;&gt; implementations MUST only match new attributes and ignore the =
old fingerprint attribute. They MAY match old fingerprint attributes if<br>
&gt;&gt;&gt; new attributes are not present.<br>
&gt;&gt;=C2=A0<br>
&gt;&gt; I think there are still different opinions on whether one match is=
 enough, or whether all supported hashes should be tested.<br>
&gt;<br>
&gt; If you want more secure match, you would need to use the new attribute=
. If you use existing attribute you will use the match<br>
&gt; algorithm in existing implementations, which currently allow a single =
fingerprint match. I have mentioned earlier that<br>
&gt; Chrome, Firefox, Asterisk and Freeswitch currently are looking for a s=
ingle match. The algorithm that Martin proposed<br>
&gt; has, as far as I know, no existing implementations.<br>
<br>
</span>My point was: if the new attribute is used, do we require all hashes=
 within the attribute to match, or is it enough if the receiver checks one =
of the hashes within the attribute.<br>
<br>
Example:<br>
<br>
a=3Dfp:certX;sha-1:&lt;hash&gt;;sha-256:&lt;hash&gt;<br>
<br>
If certX is selected, is the receiver required to check both the sha-1 and =
sha-256 hashes?</blockquote><div><br></div><div>Checking all hashes would b=
e more secure, so I would make it a &quot;SHOULD&quot;. Implementations can=
 decide to check the subset of all the hashes if they decided it provides s=
ufficient security, as in checking the most secure hash only.</div><div><br=
></div><div>Regards,</div><div>______________</div><div>Roman Shpount=C2=A0=
</div></div></div></div>

--f46d0444006ead29150532c91c7b--


From nobody Sat May 14 02:00:57 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB3F12D6E8 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 02:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kxr7Btse2FNj for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 02:00:54 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E0FB12D6E7 for <mmusic@ietf.org>; Sat, 14 May 2016 02:00:53 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-5d-5736e943d557
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 81.6E.12516.349E6375; Sat, 14 May 2016 11:00:51 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0248.002; Sat, 14 May 2016 11:00:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//4OqgD/+/MocA==
Date: Sat, 14 May 2016 09:00:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FAF41C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <CAD5OKxuTvkNyMkyWXMWEL60T6zpbmi6cXve557bL9x8SkOsu2A@mail.gmail.com>
In-Reply-To: <CAD5OKxuTvkNyMkyWXMWEL60T6zpbmi6cXve557bL9x8SkOsu2A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPIsWRmVeSWpSXmKPExsUyM2K7oq7zS7Nwg2mz5C1uzn/LYnHtzD9G i6nLH7NYrNhwgNVixoWpzA6sHn/ff2Dy2DnrLrvHkiU/mTxuTSkIYInisklJzcksSy3St0vg ytj3YglLQYNExY+Ti5kaGDeIdzFyckgImEhcvnCcBcIWk7hwbz1bFyMXh5DAEUaJ1dt3MUM4 Sxglji18DpTh4GATsJDo/qcN0iAioCrx9/tkJhCbWWAZo8TOdzwgtrCAp8T105/ZIGq8JC5M XcAOMkdE4ByjxJLGBWBzWICa1952AKnhFfCVeDX7PAvErm/cEgfvdrCDJDgFAiXe324HsxmB rvt+ag3UMnGJW0/mM0FcLSCxZM95ZghbVOLl43+sELaSROOSJ6wgu5gFNCXW79KHaFWUmNL9 kB1ir6DEyZlPWCYwis1CMnUWQscsJB2zkHQsYGRZxShanFpcnJtuZKyXWpSZXFycn6eXl1qy iREYbQe3/Nbdwbj6teMhRgEORiUe3gf7zMKFWBPLiitzDzFKcDArifCW3QUK8aYkVlalFuXH F5XmpBYfYpTmYFES5/V/qRguJJCeWJKanZpakFoEk2Xi4JRqYGw+sFWGX0lDR/wYy+0jzPlv 3QXZag0+9rL9WJK/zTLpa83zma01k4+33Nyx6vTkmKTuq5qxuRtjjSLMg9vNX4Q/K5TRXv/7 UmjM+ReP3/esv6PZ3aJacr0mwI1F4OC8Fev26ezvLJ5099n5+zpdu8ompeyMl2Gpbz05Pz79 BJtuxy9Brwf7pZVYijMSDbWYi4oTAR5AVNmyAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/5s5mBKgsaG9YNmiIuAiJzC_lwdg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 09:00:56 -0000

SGksDQoNCuKApg0KDQo+Pj4gV2UgZG8gbm90IGFzc29jaWF0ZSB0aGUgbmV3IGF0dHJpYnV0ZSB3
aXRoIHRoZSBjZXJ0aWZpY2F0ZS4gQWxsIG5ldyBhdHRyaWJ1dGUgZG9lcyBpcyBzcGVjaWZpZXMg
dGhhdCBhbGwgaGFzaGVzIHdpdGhpbiB0aGUNCj4+PiBzaW5nbGUgYXR0cmlidXRlIHJlZmVyIHRv
IHRoZSBzaW5nbGUgY2VydGlmaWNhdGUgYW5kIHNob3VsZCBtYXRjaCBhdCB0aGUgc2FtZSBmb3Ig
dGhlIHNwZWNpZmljIGNlcnRpZmljYXRlIHRvIG1hdGNoIHRoaXMgYXR0cmlidXRlLg0KPj4NCj4+
IFllcy4gQnV0LCBteSBpZGVhIHdhcyB0byBpbmRpY2F0ZSBpbiB0aGUgYXR0cmlidXRlIHdpdGgg
d2hpY2ggY2VydGlmaWNhdGUgdGhlIGF0dHJpYnV0ZSBoYXNoKGVzKSBhcmUgYXNzb2NpYXRlZCB3
aXRoLCBzbyB0aGF0IHRoZSByZWNlaXZlciBkb2VzIG5vdCBuZWVkIHRvIGNoZWNrIHRoZSBoYXNo
ZXMgd2l0aGluIGFsbCBhdHRyaWJ1dGVzLg0KPj4NCj4+IEV4YW1wbGU6DQo+Pg0KPj4gYT1mcDpj
ZXJ0WDtzaGEtMTo8aGFzaD47c2hhLTI1Njo8aGFzaD4NCj4+IGE9ZnA6Y2VydFk6c2hhLTE6PGhh
c2g+O3NoYS0yNTY6PGhhc2g+DQo+Pg0KPj4gSW4gdGhpcyBjYXNlLCBpZiBjZXJ0WCBlbmRzIHVw
IGJlaW5nIHNlbGVjdGVkLCB0aGUgZW5kcG9pbnQga25vd3Mgd2hpY2ggaGFzaGVzIGl0IHNob3Vs
ZCBjaGVjaywgYW5kIGRvZXMgbm90IG5lZWQgdG8gdHJ5IHRoZSBvdGhlcnMgaW4gb3JkZXIgdG8g
ZmluZCB0aGUgbWF0Y2guDQo+DQo+IFdoYXQgYXJlIGNlcnRYIGFuZCBjZXJ0WSB2YWx1ZXM/IFdo
YXQgZG8geW91IHVzZSB0byBpZGVudGlmeSB0aGUgY2VydGlmaWNhdGU/IENvbW1vbiBOYW1lPyBT
b21ldGhpbmcgZWxzZT8NCg0KVGhhdCBpcyBleGFjdGx5IHRoZSBxdWVzdGlvbiBJIGhhdmUgYmVl
biBhc2tpbmcgOikNCg0KV2hlbiBwZW9wbGUgaGF2ZSBiZWVuIHRhbGtpbmcgYWJvdXQgdGhpcyBu
ZXcgYXR0cmlidXRlLCBJIGhhdmUgYmVlbiBhc2tpbmcgd2hldGhlciB0aGUgYXR0cmlidXRlIHNo
b3VsZCBjb250YWluICpBKiByZWZlcmVuY2UgdG8gdGhlIGFzc29jaWF0ZWQgY2VydGlmaWNhdGUs
IGFuZCBpZiBzbywgd2hhdCBzaG91bGQgdGhhdCB2YWx1ZSBiZSAoQ29tbW9uIE5hbWUgZXRjKT8N
Cg0KPiBBbHNvLCBJIHdvdWxkIHByZWZlciBpZiB3ZSBrZWVwIHRoZSBmb3JtYXQgImE9ZnA6c2hh
LTE9PGJhc2U2NGhhc2g+O3NoYS0yNTY9PGJhc2U2NGhhc2g+Ii4gVGhpcyBpcyB0aGUgc3RhbmRh
cmQgVVJMIHBhcmFtZXRlciBmb3JtYXQgc28gaXQgd291bGQgcmVxdWlyZSBvbmUgbGVzcyBwYXJz
ZXIgdG8gc3VwcG9ydC4NCg0KTm90ZSB0aGF0IFJGQyA0NTcyIGRvZXMgbm90IHVzZSAiPSIgYmV0
d2VlbiB0aGUgaGFzaCBmdW5jdGlvbiBuYW1lIGFuZCB0aGUgdmFsdWUsIGlzIHVzZXMgc3BhY2Ug
KFNQKS4gTm93LCB0aGF0IGRvZXNuJ3QgbWVhbiB3ZSBjYW4ndCB1c2UgIj0iIGZvciB0aGUgbmV3
IGF0dHJpYnV0ZSwgYnV0IGp1c3QgdG8ga2VlcCBpbiBtaW5kIDopDQoNCglhPWZpbmdlcnByaW50
OlNIQS0xIDRBOkFEOkI5OkIxOjNGOjgyOjE4OjNCOjU0OjAyOjEyOkRGOjNFOjVEOjQ5OjZCOjE5
OkU1OjdDOkFCDQoNCi4uLg0KDQo+PiBNeSBwb2ludCB3YXM6IGlmIHRoZSBuZXcgYXR0cmlidXRl
IGlzIHVzZWQsIGRvIHdlIHJlcXVpcmUgYWxsIGhhc2hlcyB3aXRoaW4gdGhlIGF0dHJpYnV0ZSB0
byBtYXRjaCwgb3IgaXMgaXQgZW5vdWdoIGlmIHRoZSByZWNlaXZlciBjaGVja3Mgb25lIG9mIHRo
ZSBoYXNoZXMgd2l0aGluIHRoZSBhdHRyaWJ1dGUuDQo+Pg0KPj4gRXhhbXBsZToNCj4+DQo+PiBh
PWZwOmNlcnRYO3NoYS0xOjxoYXNoPjtzaGEtMjU2OjxoYXNoPg0KPj4NCj4+IElmIGNlcnRYIGlz
IHNlbGVjdGVkLCBpcyB0aGUgcmVjZWl2ZXIgcmVxdWlyZWQgdG8gY2hlY2sgYm90aCB0aGUgc2hh
LTEgYW5kIHNoYS0yNTYgaGFzaGVzPw0KPg0KPiBDaGVja2luZyBhbGwgaGFzaGVzIHdvdWxkIGJl
IG1vcmUgc2VjdXJlLCBzbyBJIHdvdWxkIG1ha2UgaXQgYSAiU0hPVUxEIi4gSW1wbGVtZW50YXRp
b25zIGNhbiBkZWNpZGUgdG8gY2hlY2sgdGhlIHN1YnNldCBvZiBhbGwgdGhlIGhhc2hlcyBpZiB0
aGV5IGRlY2lkZWQgDQo+IGl0IHByb3ZpZGVzIHN1ZmZpY2llbnQgc2VjdXJpdHksIGFzIGluIGNo
ZWNraW5nIHRoZSBtb3N0IHNlY3VyZSBoYXNoIG9ubHkuDQoNCldvcmtzIGZvciBtZS4NCg0KUmVn
YXJkcywNCg0KQ2hyaXN0ZXINCg==


From nobody Sat May 14 02:07:47 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1527A12D6F3 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 02:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CrB8FW6dPFSG for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 02:07:44 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB63112D6ED for <mmusic@ietf.org>; Sat, 14 May 2016 02:07:43 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-44-5736eade4a88
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E6.63.27088.EDAE6375; Sat, 14 May 2016 11:07:42 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Sat, 14 May 2016 11:07:41 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: draft-4572-update: New attribute [was: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01]
Thread-Index: AdGtvzRUT4Od/vD5TACmu5icBDjBUQ==
Date: Sat, 14 May 2016 09:07:40 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FAF469ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPIsWRmVeSWpSXmKPExsUyM2K7n+69V2bhBvMPCFjcnP+WxeLamX+M FlOXP2axWLHhAKvFjAtTmR1YPf6+/8DksXPWXXaPJUt+MnncmlIQwBLFZZOSmpNZllqkb5fA lXH/5T22givFFZcmXWBuYDxS0MXIySEhYCKx59o7JghbTOLCvfVsXYxcHEICRxgl9n5czgjh LGGU2Nf9kbmLkYODTcBCovufNkiDiICqxN/vk8GamQWWMUrsfMcDYgsL5Et0XDrGClFTIrHv SB8jhK0n8bt9Blg9C1DvwWOvmUFsXgFfie7uxWwgNiPQEd9PrYGaKS5x68l8qOMEJJbsOc8M YYtKvHz8jxXCVpJoXPKEFaI+X+L/6UlQMwUlTs58wjKBUXgWklGzkJTNQlI2C+gzZgFNifW7 9CFKFCWmdD9kh7A1JFrnzGVHFl/AyL6KUbQ4tTgpN93ISC+1KDO5uDg/Ty8vtWQTIzDaDm75 bbCD8eVzx0OMAhyMSjy8C9rMwoVYE8uKK3MPMUpwMCuJ8JbdBQrxpiRWVqUW5ccXleakFh9i lOZgURLn9X+pGC4kkJ5YkpqdmlqQWgSTZeLglGpgtBAMK/5w5NbpgJyg1J2S22UD+T7r/dfl Pshp+uaftn/NovKLT82fbDr2ce1thfvdM7aqPzzbELbuuOwtA8OwxojtWcoltyR28HK5JrwP f/tI2vPPrtDuH096cjlsn0bsiRZnuWbRwXI7b268ssTtY/MNjuwVa/aq63u4YDWDh9Wh2KYb AZ+eK7EUZyQaajEXFScCANk5a5yyAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/xDkgJvXFTi1gJs7hTQ9Q0JJQN7w>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 09:07:46 -0000

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

SGksDQoNCknigJl2ZSBwdXQgdG9nZXRoZXIgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQsIHdo
aWNoIGRlZmluZXMgYSBuZXcgYXR0cmlidXRlLCDigJxmcGzigJ0gKHdlIGNhbiBkaXNjdXNzIHRo
ZSBuYW1lIGxhdGVyKS4NCg0KSSBoYXZlIG5vdCBzdWJtaXR0ZWQgaXQgdG8gSUVURiB5ZXQsIGJl
Y2F1c2UgSSBmaXJzdCB3YW50IHRvIG1ha2Ugc3VyZSB3ZSBhZ3JlZSBvbiBtb3ZpbmcgZm9yd2Fy
ZCB3aXRoIGEgbmV3IGF0dHJpYnV0ZS4gSG93ZXZlciwgaXTigJlzIGF2YWlsYWJsZSBvbiBHaXRI
dWIuDQoNCmh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC00NTcyLXVwZGF0ZSAgIChOT1RF
OiBJbmRpdmlkdWFsIHJlcG8pDQoNCk5PVEUgdGhlIGZvbGxvd2luZzoNCg0KDQotICAgICAgICAg
IFRoZSBuZXcgYXR0cmlidXRlIGlzIG5vdCBkZWZpbmVkIGFzIGFuIHVwZGF0ZSB0byA0NTcyLg0K
DQotICAgICAgICAgIDQ1NzIgaXMgdXBkYXRlZCB0byBjbGFyaWZ5IHRoYXQgbXVsdGlwbGUgU0RQ
IOKAmGZpbmdlcnByaW50c+KAmSBhdHRyaWJ1dGVzIGFyZSBhbGxvd2VkLCBidXQgZWFjaCBtdXN0
IGJlIGFzc29jaWF0ZWQgd2l0aCBhIGRpZmZlcmVudCBjZXJ0aWZpY2F0ZS4gSWYgeW91IHdhbnQg
bXVsdGlwbGUgaGFzaGVzIGZvciBhIHNpbmdsZSBjZXJ0aWZpY2F0ZSwgeW91IG5lZWQgdGhlIG5l
dyBhdHRyaWJ1dGUNCg0KLSAgICAgICAgICBQYXVsLCBJIGtub3cgSSB1c2UgdGhlIG9sZCBzeW50
YXggZm9ybWF0IOKAkyB3aWxsIGJlIGZpeGVkIGxhdGVyIDopDQoNClllcywgdGhlcmUgYXJlIHRo
aW5ncyBtaXNzaW5nLCBidXQgYXQgdGhpcyBwb2ludCBJIHdhbnQgY29tbWVudHMgb24gd2hldGhl
ciBwZW9wbGUgdGhpbmsgdGhpcyBpcyB0aGUgY29ycmVjdCBhcHByb2FjaC4gSWYgc28sIEnigJls
bCBzdWJtaXQgdGhlIGRyYWZ0IHRvIElFVEYuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNv
TGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGNtOw0KCW1hcmdpbi1yaWdo
dDowY207DQoJbWFyZ2luLWJvdHRvbTowY207DQoJbWFyZ2luLWxlZnQ6MzYuMHB0Ow0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1l
cyBOZXcgUm9tYW4iLHNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMx
RjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29t
cG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0
ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEy
LjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2
LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25z
ICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDo3NzkzNzE0NTU7DQoJbXNvLWxpc3QtdHlwZTpo
eWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOi04NDE5OTA2ODIgLTgxMzU1MTQ3NiAxMzQ4
MDc1NTUgMTM0ODA3NTU3IDEzNDgwNzU1MyAxMzQ4MDc1NTUgMTM0ODA3NTU3IDEzNDgwNzU1MyAx
MzQ4MDc1NTUgMTM0ODA3NTU3O30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQt
YXQ6NDU3MjsNCgltc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjsNCgltc28tZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJpOw0KCW1zby1iaWRp
LWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28t
bGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGww
OmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5n
czt9DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglmb250LWZh
bWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZl
bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVs
LXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQt
aW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVs
Nw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3
Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
bGVmdDsNCgl0ZXh0LWluZGVudDotMTguMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlz
dCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZl
bC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0xOC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJp
ZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDsNCglm
b250LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowY207fQ0KdWwNCgl7
bWFyZ2luLWJvdHRvbTowY207fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48
IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0
PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5
b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tR0IiIGxpbms9
ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPknigJl2ZSBwdXQgdG9nZXRoZXIgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQsIHdoaWNo
IGRlZmluZXMgYSBuZXcgYXR0cmlidXRlLCDigJxmcGzigJ0gKHdlIGNhbiBkaXNjdXNzIHRoZSBu
YW1lIGxhdGVyKS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkkgaGF2
ZSBub3Qgc3VibWl0dGVkIGl0IHRvIElFVEYgeWV0LCBiZWNhdXNlIEkgZmlyc3Qgd2FudCB0byBt
YWtlIHN1cmUgd2UgYWdyZWUgb24gbW92aW5nIGZvcndhcmQgd2l0aCBhIG5ldyBhdHRyaWJ1dGUu
IEhvd2V2ZXIsIGl04oCZcw0KIGF2YWlsYWJsZSBvbiBHaXRIdWIuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vY2RoNHUv
ZHJhZnQtNDU3Mi11cGRhdGUiPmh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC00NTcyLXVw
ZGF0ZTwvYT48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVT
Ij4mbmJzcDsmbmJzcDsNCiAoTk9URTogSW5kaXZpZHVhbCByZXBvKTxzcGFuIHN0eWxlPSJjb2xv
cjojMUY0OTdEIj48bzpwPjwvbzpwPjwvc3Bhbj48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVT
Ij5OT1RFIHRoZSBmb2xsb3dpbmc6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29MaXN0
UGFyYWdyYXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEg
bGZvMSI+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUi
Pi08c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9z
cGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5UaGUgbmV3IGF0dHJpYnV0ZSBpcyBub3QgZGVm
aW5lZCBhcyBhbiB1cGRhdGUgdG8gNDU3Mi4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0idGV4dC1pbmRlbnQ6LTE4LjBwdDttc28tbGlz
dDpsMCBsZXZlbDEgbGZvMSI+PCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxzcGFuIHN0eWxlPSJtc28t
bGlzdDpJZ25vcmUiPi08c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9t
YW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtj
b2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj40NTcyIGlzIHVwZGF0ZWQg
dG8gY2xhcmlmeSB0aGF0IG11bHRpcGxlIFNEUCDigJhmaW5nZXJwcmludHPigJkgYXR0cmlidXRl
cyBhcmUgYWxsb3dlZCwgYnV0IGVhY2ggbXVzdCBiZSBhc3NvY2lhdGVkIHdpdGggYSBkaWZmZXJl
bnQNCiBjZXJ0aWZpY2F0ZS4gSWYgeW91IHdhbnQgbXVsdGlwbGUgaGFzaGVzIGZvciBhIHNpbmds
ZSBjZXJ0aWZpY2F0ZSwgeW91IG5lZWQgdGhlIG5ldyBhdHRyaWJ1dGU8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9InRleHQtaW5kZW50Oi0x
OC4wcHQ7bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48c3Bh
biBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj4tPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7
VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+UGF1
bCwgSSBrbm93IEkgdXNlIHRoZSBvbGQgc3ludGF4IGZvcm1hdCDigJMgd2lsbCBiZSBmaXhlZCBs
YXRlciA6KTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+WWVzLCB0aGVy
ZSBhcmUgdGhpbmdzIG1pc3NpbmcsIGJ1dCBhdCB0aGlzIHBvaW50IEkgd2FudCBjb21tZW50cyBv
biB3aGV0aGVyIHBlb3BsZSB0aGluayB0aGlzIGlzIHRoZSBjb3JyZWN0IGFwcHJvYWNoLiBJZiBz
bywgSeKAmWxsDQogc3VibWl0IHRoZSBkcmFmdCB0byBJRVRGLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFz
dC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPkNocmlzdGVyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_7594FB04B1934943A5C02806D1A2204B37FAF469ESESSMB209erics_--


From nobody Sat May 14 02:39:12 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F2112D0BF for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 02:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNtwl_uDbgT7 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 02:39:08 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92D5312D149 for <mmusic@ietf.org>; Sat, 14 May 2016 02:39:08 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id 190so160179657iow.1 for <mmusic@ietf.org>; Sat, 14 May 2016 02:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=UNQMp6fFLuXhJuHu8VIlJQCs35RYZsLO5/Y+APEM2Pw=; b=X/GrLdw4th7YNkhvHlTz+dyDJ1GE6a86RGQ+Cu8KbeoONXzlBjlywTTkldv2/kZovL S+I3wJxpNwTzv8sLSERUqFgxdIaHCZ7tJTTpGWbK23amYI2PZEIFiEv0CwS5j6wbUXxp LWzJr7+H+45tJrrB5N1uIRjDc7AJamtLoR2RO07r6Hz3D8Ovy/Dtli6ghIGKM/E2nn/n ez363Ip7iwbbIexMMyR/JiEDNdS6EN1ztlx2+ea7wo/uyyVmBchHQGY5EraB3IAu/6hS QsV1aYFDJLw5ya2Xh5/BZnR0Uz8vv4UW3i9K6rCYKMxTFohF3xqkfD/dr+6phLJs9XvS pYOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=UNQMp6fFLuXhJuHu8VIlJQCs35RYZsLO5/Y+APEM2Pw=; b=MM+ayrN9PJ3IJmCDTRV6O3lxl0t8ZgmbCKtYjPRGf8OtTAHL5jxxjpf+mpVGMoIDVI w8ovk8Jtf3wQbE2s1dj79Ohb+gZvfDwFxpVgxov7DX/GhgIpWGBZASWx2fD2YQxYOxSz 0tgX+iHNl3FbT7DOiGpzJGxtQIa8q+/SOy7sHHYMP0OIJdCVfpQ/fsYQLZUU72ni6+lL XOwe6OXCiUA8eaqxVggnMbDx8m0YEXWwhITkeIqce2P1lOtJ8yb11UGM3PbaTE1DFsTy 11k7gtIFNzpIpzENu3aTbV1AGevY6UbPISMONNL1phhT6e95EP4ujR/Bemqg+Uls4w9x STYw==
X-Gm-Message-State: AOPr4FVlcgKXfHu2POpkmCXAsSd1NZsLc4Ye4IG3LBopRLEwf9bj9mMiBAwWgrMlUBFiyg==
X-Received: by 10.36.127.148 with SMTP id r142mr3459849itc.45.1463218747751; Sat, 14 May 2016 02:39:07 -0700 (PDT)
Received: from mail-io0-f173.google.com (mail-io0-f173.google.com. [209.85.223.173]) by smtp.gmail.com with ESMTPSA id as2sm2301890igc.9.2016.05.14.02.39.06 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 14 May 2016 02:39:06 -0700 (PDT)
Received: by mail-io0-f173.google.com with SMTP id 190so160179247iow.1 for <mmusic@ietf.org>; Sat, 14 May 2016 02:39:06 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.155.132 with SMTP id o126mr3302439itd.95.1463218746113; Sat, 14 May 2016 02:39:06 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Sat, 14 May 2016 02:39:05 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FAF41C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <CAD5OKxuTvkNyMkyWXMWEL60T6zpbmi6cXve557bL9x8SkOsu2A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAF41C@ESESSMB209.ericsson.se>
Date: Sat, 14 May 2016 05:39:05 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsQ_mmMPA32tW9whF_VemG7RMRqWm3Q72w7HigeNQ_0Qw@mail.gmail.com>
Message-ID: <CAD5OKxsQ_mmMPA32tW9whF_VemG7RMRqWm3Q72w7HigeNQ_0Qw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c05d158974c4c0532ca29f7
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/vov5Qvn5eKghz6BlTLZnd4SexYs>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 09:39:10 -0000

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

On Sat, May 14, 2016 at 5:00 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> > What are certX and certY values? What do you use to identify the
> certificate? Common Name? Something else?
>
> That is exactly the question I have been asking :)
>
> When people have been talking about this new attribute, I have been asking
> whether the attribute should contain *A* reference to the associated
> certificate, and if so, what should that value be (Common Name etc)?
>

If anybody wants to add some new way to identify the certificate in
addition to hash, they can propose a new name value pair for this purpose.
The proposed format can already accommodate this.

This being said, I do not think it is necessary to provide certificate ID
in the new attribute. Right now there is no requirement for the common name
to be unique for the certificates. Most implementations simply put server
IP in common name for self signed certificates, so common name is not
unique. I do not think we need to invent a new unique certificate ID when
hash value is already sufficiently unique for this purpose. I think the
problem with the old fingerprint attribute was that it was unclear which
fingerprints referred to the same certificate.  It is solved with the new
attribute by putting all the related fingerprints in the same attribute.
Unless someone thinks of the problem which is needed to be solved by the
certificate id, hash values alone should be enough.

> Also, I would prefer if we keep the format
> "a=fp:sha-1=<base64hash>;sha-256=<base64hash>". This is the standard URL
> parameter format so it would require one less parser to support.
>
> Note that RFC 4572 does not use "=" between the hash function name and the
> value, is uses space (SP). Now, that doesn't mean we can't use "=" for the
> new attribute, but just to keep in mind :)
>
>         a=fingerprint:SHA-1
> 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
>

I am also suggesting to use base64 encoding for hash value instead of hex.
Makes the whole thing a bit shorter.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Sat, May 14, 2016 at 5:00 AM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"><span class=3D"">&gt; What are certX and =
certY values? What do you use to identify the certificate? Common Name? Som=
ething else?<br>
<br>
</span>That is exactly the question I have been asking :)<br>
<br>
When people have been talking about this new attribute, I have been asking =
whether the attribute should contain *A* reference to the associated certif=
icate, and if so, what should that value be (Common Name etc)?<br></blockqu=
ote><div>=C2=A0</div><div>If anybody wants to add some new way to identify =
the certificate in addition to hash, they can propose a new name value pair=
 for this purpose. The proposed format can already accommodate this.</div><=
div><br></div><div>This being said, I do not think it is necessary to provi=
de certificate ID in the new attribute.=C2=A0Right now there is no requirem=
ent for the common name to be unique for the certificates. Most implementat=
ions simply put server IP in common name for self signed certificates, so c=
ommon name is not unique. I do not think we need to invent a new unique cer=
tificate=C2=A0ID=C2=A0when hash value is already sufficiently unique for th=
is purpose. I think the problem with the old fingerprint attribute was that=
 it was unclear which fingerprints referred to the same certificate.=C2=A0 =
It is solved with the new attribute by putting all the related fingerprints=
 in the same attribute. Unless someone thinks of the problem which is neede=
d to be solved by the certificate id, hash values alone should be enough.</=
div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color=
:rgb(204,204,204);padding-left:1ex"><span class=3D"">&gt; Also, I would pre=
fer if we keep the format &quot;a=3Dfp:sha-1=3D&lt;base64hash&gt;;sha-256=
=3D&lt;base64hash&gt;&quot;. This is the standard URL parameter format so i=
t would require one less parser to support.<br>
<br>
</span>Note that RFC 4572 does not use &quot;=3D&quot; between the hash fun=
ction name and the value, is uses space (SP). Now, that doesn&#39;t mean we=
 can&#39;t use &quot;=3D&quot; for the new attribute, but just to keep in m=
ind :)<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a=3Dfingerprint:SHA-1 4A:AD:B9:B1:3F:82:18:3B:5=
4:02:12:DF:3E:5D:49:6B:19:E5:7C:AB<br></blockquote><div><br></div><div>I am=
 also suggesting to use base64 encoding for hash value instead of hex. Make=
s the whole thing a bit shorter.</div><div><br></div><div>Regards,</div><di=
v><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div>=
<div>=C2=A0</div></div></div></div>

--94eb2c05d158974c4c0532ca29f7--


From nobody Sat May 14 04:44:24 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB7A12D71F for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 04:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3j5kHQs5EQIL for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 04:44:21 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C264F12B05E for <mmusic@ietf.org>; Sat, 14 May 2016 04:44:20 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-f6-57370f9230d2
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 54.A4.18043.29F07375; Sat, 14 May 2016 13:44:18 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0248.002; Sat, 14 May 2016 13:43:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//4OqgD/+/MocP/3+3uA/++1YoA=
Date: Sat, 14 May 2016 11:43:35 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FB0668@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <CABkgnnUeQAmRrmRgBazPO=6RX0WzeQ6T9H-x3modd=n07kDLKg@mail.gmail.com> <d8aa50d1-e5f6-1033-3b22-54b540d1beda@alum.mit.edu> <CABkgnnV-wF-7G4oTjdPr_+Xbamn1WpfuycF4NgsE4sqc9CshVw@mail.gmail.com> <30ad9612-84e1-6402-32a6-58afbf90adde@alum.mit.edu> <CABkgnnWf8AOudjH5e-UYTwe8=h5=6r=NzOYuLW+LsAB7W8cRjQ@mail.gmail.com> <6d67ed8b-f01f-7647-47fe-43e0814b18b6@alum.mit.edu> <CABkgnnVv3Xwbic6qNTYnDdQpi61G7boAbopXBUAKg49-HRzgGA@mail.gmail.com> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <CAD5OKxuTvkNyMkyWXMWEL60T6zpbmi6cXve557bL9x8SkOsu2A@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAF41C@ESESSMB209.ericsson.se> <CAD5OKxsQ_mmMPA32tW9whF_VemG7RMRqWm3Q72w7HigeNQ_0Qw@mail.gmail.com>
In-Reply-To: <CAD5OKxsQ_mmMPA32tW9whF_VemG7RMRqWm3Q72w7HigeNQ_0Qw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2J7oO4kfvNwg8UXpCxuzn/LYnHtzD9G i6nLH7NYrNhwgNVixoWpzA6sHn/ff2Dy2DnrLrvHkiU/mTxuTSkIYInisklJzcksSy3St0vg ymjd/pWp4BdfRcvEMywNjCf4uhg5OSQETCQO/HrLBGGLSVy4t56ti5GLQ0jgCKPEl4uf2CGc JYwSX+c+Z+xi5OBgE7CQ6P6nDdIgIqAq8ff7ZLBmZoFljBI73/GA2MICnhLXT39mg6jxkrgw dQHYHBGBW4wSLf/vMIIkWICa19zfzgJi8wr4SnR8+8oIsayRV2L1vL9gRZwCgRJz5j8B28AI dN73U2ugtolL3HoyH+psAYkle84zQ9iiEi8f/2OFsJUkVmy/BHY0s4CmxPpd+hCtihJTuh+y Q+wVlDg58wnLBEaxWUimzkLomIWkYxaSjgWMLKsYRYtTi4tz042M9FKLMpOLi/Pz9PJSSzYx AuPt4JbfVjsYDz53PMQowMGoxMOr8N0sXIg1say4MvcQowQHs5IIbwuPebgQb0piZVVqUX58 UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGxomXFh3enxzsIFIyadudHye6 giQv+5V9jGORCFPdxVe9aWJ3noGVyyeV+odXOo2r7E5abXW/2+Qs8H5pp1Fso6F/38Q0K4ZT 96SWznLe88nQSI79lMnKEOENd/r2tmk+WVmd8Hzzjd2Np9zmbp9RM2umXh1f4Wo1k+B283cX nzFu3nb9UPmjCiWW4oxEQy3mouJEAE9hKCOzAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/t_CKuq_TiIwq30ia6okSBg-MGVo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 11:44:23 -0000

SGksDQoNCj4+PiBXaGF0IGFyZSBjZXJ0WCBhbmQgY2VydFkgdmFsdWVzPyBXaGF0IGRvIHlvdSB1
c2UgdG8gaWRlbnRpZnkgdGhlIGNlcnRpZmljYXRlPyBDb21tb24gTmFtZT8gU29tZXRoaW5nIGVs
c2U/DQo+Pg0KPj4gVGhhdCBpcyBleGFjdGx5IHRoZSBxdWVzdGlvbiBJIGhhdmUgYmVlbiBhc2tp
bmcgOikNCj4+DQo+PiBXaGVuIHBlb3BsZSBoYXZlIGJlZW4gdGFsa2luZyBhYm91dCB0aGlzIG5l
dyBhdHRyaWJ1dGUsIEkgaGF2ZSBiZWVuIGFza2luZyB3aGV0aGVyIHRoZSBhdHRyaWJ1dGUgc2hv
dWxkIA0KPj4gY29udGFpbiAqQSogcmVmZXJlbmNlIHRvIHRoZSBhc3NvY2lhdGVkIGNlcnRpZmlj
YXRlLCBhbmQgaWYgc28sIHdoYXQgc2hvdWxkIHRoYXQgdmFsdWUgYmUgKENvbW1vbiBOYW1lIGV0
Yyk/DQo+DQo+IElmIGFueWJvZHkgd2FudHMgdG8gYWRkIHNvbWUgbmV3IHdheSB0byBpZGVudGlm
eSB0aGUgY2VydGlmaWNhdGUgaW4gYWRkaXRpb24gdG8gaGFzaCwgdGhleSBjYW4gcHJvcG9zZSBh
IG5ldyBuYW1lIHZhbHVlIHBhaXIgZm9yIHRoaXMgcHVycG9zZS4gVGhlIHByb3Bvc2VkIGZvcm1h
dCBjYW4gYWxyZWFkeSBhY2NvbW1vZGF0ZSB0aGlzLg0KDQpJZiBwZW9wbGUgZG9uJ3QgdGhpbmsg
aXQncyBuZWVkZWQgbm93LCBmaW5lIC0gSSBtZXJlbHkgd2FudGVkIHRvIGNsYXJpZnkgd2hldGhl
ciBwZW9wbGUgd2VyZSBhc3N1bWluZyB3ZSdkIGhhdmUgc29tZSBraW5kIG9mIHJlZmVyZW5jZS4N
Cg0KLi4uDQoNCj4+PiBBbHNvLCBJIHdvdWxkIHByZWZlciBpZiB3ZSBrZWVwIHRoZSBmb3JtYXQg
ImE9ZnA6c2hhLTE9PGJhc2U2NGhhc2g+O3NoYS0yNTY9PGJhc2U2NGhhc2g+Ii4gVGhpcyBpcyB0
aGUgc3RhbmRhcmQgVVJMIHBhcmFtZXRlciBmb3JtYXQgc28gaXQgd291bGQgcmVxdWlyZSBvbmUg
bGVzcyBwYXJzZXIgdG8gc3VwcG9ydC4NCj4+DQo+PiBOb3RlIHRoYXQgUkZDIDQ1NzIgZG9lcyBu
b3QgdXNlICI9IiBiZXR3ZWVuIHRoZSBoYXNoIGZ1bmN0aW9uIG5hbWUgYW5kIHRoZSB2YWx1ZSwg
aXMgdXNlcyBzcGFjZSAoU1ApLiBOb3csIHRoYXQgZG9lc24ndCBtZWFuIHdlIGNhbid0IHVzZSAi
PSIgZm9yIHRoZSBuZXcgYXR0cmlidXRlLCBidXQganVzdCB0byBrZWVwIGluIG1pbmQgOikNCj4+
DQo+PsKgIMKgIMKgIMKgIGE9ZmluZ2VycHJpbnQ6U0hBLTEgNEE6QUQ6Qjk6QjE6M0Y6ODI6MTg6
M0I6NTQ6MDI6MTI6REY6M0U6NUQ6NDk6NkI6MTk6RTU6N0M6QUINCj4NCj4gSSBhbSBhbHNvIHN1
Z2dlc3RpbmcgdG8gdXNlIGJhc2U2NCBlbmNvZGluZyBmb3IgaGFzaCB2YWx1ZSBpbnN0ZWFkIG9m
IGhleC4gTWFrZXMgdGhlIHdob2xlIHRoaW5nIGEgYml0IHNob3J0ZXIuDQoNCldvcmtzIGZvciBt
ZS4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0K


From nobody Sat May 14 07:42:13 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E67D012B021 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 07:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ichFk4XSTBWm for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 07:42:10 -0700 (PDT)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89B1B12B066 for <mmusic@ietf.org>; Sat, 14 May 2016 07:42:08 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by comcast with SMTP id 1akMbsL352R4w1albbhdiR; Sat, 14 May 2016 14:42:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463236927; bh=CN8QWKwyPaRsqIklZUtS+6C+JogArs8t/0YNQD8XrxQ=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=fIna+q2bFy+kzjMUGwFJsUwXeCBAWDsYByt21DWK2lhbhG4mJExYXoW1ske3BV1Qq lpXA59G+FqEyxpj+QFBllHEByheCtskxncVZZS2HoyMj8DjHH26xPVwDGtHXQh8Agg hVoVbWzDDa9p32ZnD0KKpUVvbAtzZRnZ4QudAhe3bHYXd1NzfOwMtdLeKfDfoygZlB 5TxnMkJPRB4SE+79NU2d3hQ7oDhprJ2BbDGwXPHEq+M8YjOWchx/IJqFmHx2vbcYa+ uP2MLMRpex/IJm75/+lIkug8VIPWkn/aOpBN43VMfkZTU5SSycMluBcCPdIZD86FG5 FdYY2syQfaGgw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-18v.sys.comcast.net with comcast id uEi61s00f3KdFy101Ei6RA; Sat, 14 May 2016 14:42:07 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu>
Date: Sat, 14 May 2016 10:42:05 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ayKH84YpIgCF2CzDzhngIkIt9GQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 14:42:12 -0000

On 5/14/16 3:38 AM, Christer Holmberg wrote:

> My point was: if the new attribute is used, do we require all hashes within the attribute to match, or is it enough if the receiver checks one of the hashes within the attribute.

ISTM that this should be entirely up to the receiver. It should be 
allowed to check them all, and fail if they don't all match. That means 
the sender must ensure that all those sent are valid. But the receiver 
MAY only check one or a few that it trusts. Probably a receiver SHOULD 
check at least the strongest one it understands.

In the extreme, a very trusting receiver might not check any, thought 
that certainly should not be recommended.

	Thanks,
	Paul


From nobody Sat May 14 08:33:32 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC5512D0DA for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_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 Q4ig_w0_L6R8 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:33:29 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63055127058 for <mmusic@ietf.org>; Sat, 14 May 2016 08:33:29 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id i75so160478679ioa.3 for <mmusic@ietf.org>; Sat, 14 May 2016 08:33:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=7DfMoJpIWsk8uk5hQxTlyJwKXRfUg7WAzle0U4AZC8I=; b=hzGM5Ymlqay8ohoq1PnIRB0kzPLaGwFyhe3WsQeF3TF42290jOcPcSKNlPl1FU1sYl dYES7Oe3w0GzcZPZMoW5lOH5lkniwFN5eiIEYKkI7ipmVUsEU2IEnRauOguA4xC7bxmP 9nUDUxXMAbBZHf24xi69l0OhGKAV6i96oVBwtOWZvD9dCP6G123Hm29qIYZAu3lPvHZX bmqLJPTP4i380LvAGtetRquw4bTtlUizLA09hC+/+lM1fmuN8Uz93HBa+B7xSEgNprQt g3M4xBgSPGHYy/Wogz7ovBrSCkXA/hLSAkJ4eO9hXaVP/w1K3xc2HPaDQp/yWHPw3chE Nl9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=7DfMoJpIWsk8uk5hQxTlyJwKXRfUg7WAzle0U4AZC8I=; b=WTSoUqY6IpPuH6c/vmt694z4Z83k//ebxswnnTxoF+hoc1VZFOj0PW8Ide1mo8HxDY +j1Z8OYzedvGPxkP6PzmbT9eeVGHVeygsVqMFSPhxEhooBRyx1pFW9sOv+fbjrBEBS4o gZzYj31kzocy2ycPj954iV2MCR02LYWtm+ws8d3ueP7NS6md9mPAfq5RoxIWz/Bhr7xh NgFLm4ukoHmJoRaczuyntlZRjzNN0XGKEb2yFPrhwS30a5akXNThe+zF4cDugqQa7ldc kb96cTcVWMzNayXrF/hGtpU945f//AdN1dgQ19sVdCXgHbXYdvW6YRcKKI3JLJIz5LSX vQ+A==
X-Gm-Message-State: AOPr4FXPQRXllkGvUvXMC3bUm4CBKWFiyyoVsmzheN9+nDH47tEEPpQUOXIhGTR06OF8ufmGzAziuttqVYUMMw==
MIME-Version: 1.0
X-Received: by 10.107.136.76 with SMTP id k73mr15354726iod.100.1463240008750;  Sat, 14 May 2016 08:33:28 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sat, 14 May 2016 08:33:28 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se>
Date: Sun, 15 May 2016 01:33:28 +1000
Message-ID: <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/SMBWoNgKqLPJdX2fGMPtwBepu_g>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 15:33:31 -0000

On 14 May 2016 at 19:07, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> https://github.com/cdh4u/draft-4572-update   (NOTE: Individual repo)

Where are the matching rules for the new attribute?  Maybe it's my
jetlag, but I couldn't see them.  They are the most important part.

After seeing this, I think that this is worse than what I've been
proposing.  At least what I proposed was backward compatible, but now
you have no way of specifying multiple hash algorithms for
compatibility with a wide range of peers...unless they support this
spec, which they won't for ages.

The restriction to one a=fingerprint per certificate is an unnecessary
stipulation.  You have to be able to a) ignore fingerprints for
certificates that aren't used, and b) ignore certificates for hashes
that you don't know or support.

I offered this option without really thinking through the
consequences, but having now seen it manifest, I don't like it very
much.


From nobody Sat May 14 08:43:09 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5DAE12D0D3 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.272
X-Spam-Level: 
X-Spam-Status: No, score=0.272 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.972] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJGvcBNM8liv for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:43:06 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 962D1127058 for <mmusic@ietf.org>; Sat, 14 May 2016 08:43:06 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by comcast with SMTP id 1biXb4UGDpUrh1bibbMBkJ; Sat, 14 May 2016 15:43:05 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463240585; bh=7j4lxalpfMfoWmPcnD6aW4LuAS6LaqoFyHWvlpJ+dWY=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=fXIlUA5Sdrcc+IW1pQsw3DryYG2vZdN6OqHyyARuIzDABJbZ1hX+M225OJgNbiyWj 1HcMY1n6SeYCQzwiIwPL1rUj61rht8CXJ/JXv6c+YzWtxEmENYC+Wg+kU9i52QOcY8 PDQyGlULNlXB9CIjjGZsmB2ElSS7Tcn9yRk2m4BZpq2iPIOQhkoJWL5xfhJvfeMOSa DGOTaqvHgMX7+sBPN9LopE9Brhjp6ljAgtQuMlcLkB1mM/RtNRj9R6kRAzMWKAzQty vtljxGBAm9v/Yb00gAhq7lQhSmg9dKBVRChT7/KiXQiodoFmQn+KAGRkieBdMtT0dJ 4s5jHULekW6cw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-08v.sys.comcast.net with comcast id uFj41s00d3KdFy101Fj597; Sat, 14 May 2016 15:43:05 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <7e3d8424-b5f8-8b11-7db1-f5d10ae65091@alum.mit.edu>
Date: Sat, 14 May 2016 11:43:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ChQD7zyqOl5ygB-wXsNFZzonW_4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 15:43:08 -0000

Some comments on the new draft:

The listed syntax for the new attribute:

   fingerprint-list =  "fpl" ":" hash-func SP fingerprint
                       *(":" hash-func SP fingerprint)

This isn't consistent with the example. I think you meant:

   fingerprint-list =  "fpl" ":" hash-func SP fingerprint
                       *(":" hash-func SP fingerprint)

Even then, I think I like Roman's proposed syntax better.

Later, in 4.2, is:

    If the offerer associates both 'fpl' attributes and 'fingerprint'
    attributes with the "m=" line in the offer, the fingerprint value
    included in any 'fingerprint' attribute MUST also be included in the
    'fpl' attribute associated with the same certificate.

Why is this MUST? Certainly it should be allowed. But it may be that the 
sender doesn't trust that hash. If not, why include it.

I think the key thing to note is that if that hash is to be considered 
when processing this attribute then it needs to be included. If it isn't 
included then it will only be used by recipients that don't support fpl.

Section 4.3:

    If the offer does not contain any 'fpl' attribute, the answerer
    SHOULD NOT associate any 'fpl' attribute with the corresponding "m="
    line in the answer.

Why not MUST NOT?

Then:

    If the offer contains one or more SDP 'fingerprint' attributes, the
    answerer follows the procedures in [RFC4572] for generating the
    answer.

I think this needs to be further qualified - this applies if 
'fingerprint' *is* present and 'fpl' *is not* present.

Then:

    If the answerer associates both 'fpl' attributes and 'fingerprint'
    attributes with the "m=" line in the answer, the fingerprint value
    included in any 'fingerprint' attribute MUST also be included in the
    'fpl' attribute associated with the same certificate.

I think if both are present in the offer, then 'fingerprint' should be 
ignored, and not included in the answer.

Update to 4572:

Why is the text change made? I thought this is now for backward 
compatibility only, so the restriction on the hash function used should 
remain. I think it should be dropped, keeping only the new text on 
multiple fingerprints.

	Thanks,
	Paul

On 5/14/16 5:07 AM, Christer Holmberg wrote:
> Hi,
>
>
>
> Iâ€™ve put together a new version of the draft, which defines a new
> attribute, â€œfplâ€� (we can discuss the name later).
>
>
>
> I have not submitted it to IETF yet, because I first want to make sure
> we agree on moving forward with a new attribute. However, itâ€™s available
> on GitHub.
>
>
>
> https://github.com/cdh4u/draft-4572-update   (NOTE: Individual repo)
>
>
>
> NOTE the following:
>
>
>
> -          The new attribute is not defined as an update to 4572.
>
> -          4572 is updated to clarify that multiple SDP â€˜fingerprintsâ€™
> attributes are allowed, but each must be associated with a different
> certificate. If you want multiple hashes for a single certificate, you
> need the new attribute
>
> -          Paul, I know I use the old syntax format â€“ will be fixed later :)
>
>
>
> Yes, there are things missing, but at this point I want comments on
> whether people think this is the correct approach. If so, Iâ€™ll submit
> the draft to IETF.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>


From nobody Sat May 14 08:43:40 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E93ED12D131 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[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 r0blBU5krmsT for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:43:37 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B4CF127058 for <mmusic@ietf.org>; Sat, 14 May 2016 08:43:37 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-89-573747a71a27
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 33.D7.12926.7A747375; Sat, 14 May 2016 17:43:35 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0248.002; Sat, 14 May 2016 17:43:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: draft-4572-update: New attribute [was: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01]
Thread-Index: AdGtvzRUT4Od/vD5TACmu5icBDjBUQAJf5cAAARUvhA=
Date: Sat, 14 May 2016 15:43:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com>
In-Reply-To: <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2K7je5yd/Nwg+ubpC1uzn/LYnHtzD9G i6nLH7NYrNhwgNVixoWpzA6sHn/ff2Dy2DnrLrvHkiU/mTxuTSkIYInisklJzcksSy3St0vg yjjw+DZ7wTqBiuUzulgaGH/wdzFyckgImEj09TSyQthiEhfurWfrYuTiEBI4wiix+NJXJghn CZBz5iZQFQcHm4CFRPc/bZAGEQFdiUVnH7CD1DALzGOUWLrrCDNIQligWOLw0YNMEEUlEvuO 9DFC2FYSK3ceZgexWQRUJX5M/8sGYvMK+Eqs/QIyH2TZFEaJl4+Ogp3EKRAocXHJCzCbEei8 76fWgA1lFhCXuPVkPhPE2QISS/acZ4awRSVePv4H9Y6SxIrtlxhBjmYW0JRYv0sfolVRYkr3 Q3aIvYISJ2c+YZnAKDYLydRZCB2zkHTMQtKxgJFlFaNocWpxUm66kbFealFmcnFxfp5eXmrJ JkZgvB3c8lt1B+PlN46HGAU4GJV4eBW+m4ULsSaWFVfmHmKU4GBWEuHVcTUPF+JNSaysSi3K jy8qzUktPsQozcGiJM7r/1IxXEggPbEkNTs1tSC1CCbLxMEp1cCYcVRwx3qJoHVzr/a8M2lh rm4W5VfImjQl/H9abYZTsa7x5p+lmZkPA9Tbtz/LnF0v7Rdo6rvZ5m7C3PuHJ554FHDr3qzo vuT9Kdn7tScq8n+pu+62bL2scLYQq8IBhoUmq1RuCLXEbH1Q6P7jjZBX5ovVdRYTHy27VbBC a5HnUb5rKuc99b4rsRRnJBpqMRcVJwIACvuDDLMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/MQOnvLOc0d1_Yh5VW_nGq1J_RpI>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 15:43:39 -0000

SGksDQoNCj4+IGh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC00NTcyLXVwZGF0ZSAgIChO
T1RFOiBJbmRpdmlkdWFsIHJlcG8pDQo+DQo+IFdoZXJlIGFyZSB0aGUgbWF0Y2hpbmcgcnVsZXMg
Zm9yIHRoZSBuZXcgYXR0cmlidXRlPyAgTWF5YmUgaXQncyBteSBqZXRsYWcsIGJ1dCBJIGNvdWxk
bid0IHNlZSB0aGVtLiAgDQo+IFRoZXkgYXJlIHRoZSBtb3N0IGltcG9ydGFudCBwYXJ0Lg0KDQpJ
IGFtIHdvcmtpbmcgb24gdGV4dCwgYnV0IHRoZSBzdWdnZXN0aW9ucyBzbyBmYXIgKHVubGVzcyBJ
J3ZlIG1pc3NlZC9taXN1bmRlcnN0b29kIHNvbWV0aGluZykgaGFzIGJlZW4gdGhhdCBhdCBsZWFz
dCBvbmUgKGJ1dCBub3QgYWxsKSBvZiB0aGUgcHJvdmlkZWQgZmluZ2VycHJpbnRzIG11c3QgbWF0
Y2ggY2VydGlmaWNhdGUuDQoNCj5BZnRlciBzZWVpbmcgdGhpcywgSSB0aGluayB0aGF0IHRoaXMg
aXMgd29yc2UgdGhhbiB3aGF0IEkndmUgYmVlbiBwcm9wb3NpbmcuICBBdCBsZWFzdCB3aGF0IEkg
cHJvcG9zZWQgPndhcyBiYWNrd2FyZCBjb21wYXRpYmxlLCBidXQgbm93IHlvdSBoYXZlIG5vIHdh
eSBvZiBzcGVjaWZ5aW5nIG11bHRpcGxlIGhhc2ggYWxnb3JpdGhtcyBmb3IgPmNvbXBhdGliaWxp
dHkgd2l0aCBhIHdpZGUgcmFuZ2Ugb2YgcGVlcnMuLi51bmxlc3MgdGhleSBzdXBwb3J0IHRoaXMg
c3BlYywgd2hpY2ggdGhleSB3b24ndCBmb3IgYWdlcy4NCj4NCj5UaGUgcmVzdHJpY3Rpb24gdG8g
b25lIGE9ZmluZ2VycHJpbnQgcGVyIGNlcnRpZmljYXRlIGlzIGFuIHVubmVjZXNzYXJ5IHN0aXB1
bGF0aW9uLiAgWW91IGhhdmUgdG8gYmUgYWJsZSA+dG8gYSkgaWdub3JlIGZpbmdlcnByaW50cyBm
b3IgY2VydGlmaWNhdGVzIHRoYXQgYXJlbid0IHVzZWQsIGFuZCBiKSBpZ25vcmUgY2VydGlmaWNh
dGVzIGZvciBoYXNoZXMgdGhhdCB5b3UgPmRvbid0IGtub3cgb3Igc3VwcG9ydC4NCj4NCj5JIG9m
ZmVyZWQgdGhpcyBvcHRpb24gd2l0aG91dCByZWFsbHkgdGhpbmtpbmcgdGhyb3VnaCB0aGUgY29u
c2VxdWVuY2VzLCBidXQgaGF2aW5nIG5vdyBzZWVuIGl0ID5tYW5pZmVzdCwgSSBkb24ndCBsaWtl
IGl0IHZlcnkgbXVjaC4NCg0KU28sIHlvdSBkb24ndCBsaWtlIHRoZSBuZXcgYXR0cmlidXRlLCB5
b3UgZG9uJ3QgbGlrZSB0aGUgb25lLWZpbmdlcnByaW50LXBlci1jZXJ0aWZpY2F0ZSByZXN0cmlj
dGlvbiBvbiB0aGUgZXhpc3RpbmcgJ2ZpbmdlcnByaW50JyBhdHRyaWJ1dGUgb3IgeW91IGRvbid0
IGxpa2UgYW55IG9mIGl0Pw0KDQpXZSBjb3VsZCBvZiBjb3Vyc2UgcmVtb3ZlIHRoZSByZXN0cmlj
dGlvbiwgYnV0IHRoZW4gSSB3b25kZXIgaG93IG11Y2ggc2Vuc2UgdGhlIG5ldyBhdHRyaWJ1dGUg
d291bGQgbWFrZS4gU3VyZSwgaXQgd291bGQgYWxsb3cgZW5kcG9pbnRzIHRvIGdyb3VwIHRoZSBm
aW5nZXJwcmludHMgd2l0aCB0aGUgYXNzb2NpYXRlZCBmaW5nZXJwcmludCwgYnV0IGlzIHRoYXQg
d29ydGggdGhlIGVmZm9ydD8gDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Sat May 14 08:48:49 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 644CD12D0D3 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_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 JbcQo8buLvEx for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:48:47 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50382127058 for <mmusic@ietf.org>; Sat, 14 May 2016 08:48:47 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id 190so166133665iow.1 for <mmusic@ietf.org>; Sat, 14 May 2016 08:48:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ayybWNAWWunHJI4X7Czf29rxhMt9FzjudRQ+Jp4f0tY=; b=UhPqq/lRi/WCzUYcr3iRXJqXm/3Y7tBFB+zxY0V5DY3FSqzLBr/79vtRPilnQ83c0J 3qrjmx+r/nMu6hBkivthw0nWmetg/yEVlCsvoNzQV7MC39zzD3P2xCUB4Ql1Mh1cSUUj 4YDoVVT10853TKla5aWA/3TW2nxM0tEoxpn75P0cCGH9mBg/zEfOJ8KRvzYzwF/JuQQo 7yMOIkqIBQOXOEWyrB8xvXgGJaz+rtS4NInTIYhlU9wB6hnSo++wuM2CI9xNSmbpn+u1 yjVuuMCvurpGOhYZWuG1N2a9esxy4WMXcragzHADQfjaJauVdjNpKlNQxUgt2BatiI0U iRCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ayybWNAWWunHJI4X7Czf29rxhMt9FzjudRQ+Jp4f0tY=; b=jL/gN2QIJNwkeLtbL2rysTN4O7wrR1KYURkLqIDgxscB+CxNivytuYA4j5PVSurQoe xAyCxrMhMJmv59UlFmfbojxj+nxrVBfVcbQG1n51Q+jrbR+wGHA3nmafDgaSzDQlD8Cj g9OcSbHRuEAfvrbzKju8NmjohzgC+vc3GKI49ZazZnvtYb3oCGuorn5nQJJXueUyQar+ wnLTNYWtpsWE1YpA1VvbFDxqwtUQoxjCWt9Gt6jNZ1UdmzxRJBcVclnSiHQXqUgOhQan UfKJTsb0j9O2JgWn4eXgIU8bHmc28VuDW6z1YDEKp/8Iv54dinxRs1pfhrsxKe6ja/ee MfVQ==
X-Gm-Message-State: AOPr4FVt72IL5Ve2z3lS6D4R2YmI59ZNL/ztGA7AC628LAMX1V0WVzVl6kuntX2rrTFWy0MvFYCMzkfRLJPSFw==
MIME-Version: 1.0
X-Received: by 10.36.74.74 with SMTP id k71mr5240997itb.68.1463240926705; Sat, 14 May 2016 08:48:46 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sat, 14 May 2016 08:48:46 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se>
Date: Sun, 15 May 2016 01:48:46 +1000
Message-ID: <CABkgnnVS+akLQ9ssvMnU35VRRrBJYMzsBHJRMotQpvDM8Lrc7Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/WEJ38HSjTGwrBHS7UJ1DVihpDrs>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 15:48:48 -0000

What do you think the matching rule should be.  That's the crux of all
of this, all the shiny new syntax in the world won't help unless you
are sure what you want.

On 15 May 2016 at 01:43, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> We could of course remove the restriction, but then I wonder how much sense the new attribute would make. Sure, it would allow endpoints to group the fingerprints with the associated fingerprint, but is that worth the effort?

Yes, now you are getting to the core of the issue.  The restriction
doesn't make sense because it's a restriction you can't enforce in any
meaningful way.  And once you accept that, the only problems we really
have to solve are:

 - whether we care about saying that a particular set of hashes belong
to the same certificate (me, I don't care)

 - whether we care about the weakest-link algorithm (me, I do care: we
are still shipping code with SHA-1)


From nobody Sat May 14 08:51:20 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE6A12B00C for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[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 V7zG7S7i7-Qj for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:51:16 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57689127058 for <mmusic@ietf.org>; Sat, 14 May 2016 08:51:16 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-dd-57374972c1fd
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 2B.E0.12516.27947375; Sat, 14 May 2016 17:51:14 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Sat, 14 May 2016 17:51:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>
Thread-Topic: draft-4572-update: New attribute [was: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01]
Thread-Index: AdGtvzRUT4Od/vD5TACmu5icBDjBUQAJ1WsAAAQ7/iA=
Date: Sat, 14 May 2016 15:51:13 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FB289D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <7e3d8424-b5f8-8b11-7db1-f5d10ae65091@alum.mit.edu>
In-Reply-To: <7e3d8424-b5f8-8b11-7db1-f5d10ae65091@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM2K7n26Rp3m4wcNFehY3579lsbh25h+j xdTlj1ksVmw4wGox48JUZgdWj7/vPzB57Jx1l91jyZKfTB63phQEsERx2aSk5mSWpRbp2yVw ZWz4wVuwQ7Pi1qe/bA2MGzS6GDk5JARMJFZ8/MoKYYtJXLi3nq2LkYtDSOAIo8T0/U+YIJwl jBJLz31g7mLk4GATsJDo/qcN0iAi4C0xYf5qNhCbWaBO4t2kYywgtrBAscThoweZIGpKJPYd 6WOEsK0kuo8dBLNZBFQlpjw5BLaYV8BX4tCJyewQu5oZJc7cuMwIsotTwEHi8KcskBpGoOO+ n1rDBLFLXOLWk/lMEEcLSCzZc54ZwhaVePn4H9QzShIrtl8CG8MsoCmxfpc+RKuixJTuh+wQ awUlTs58wjKBUWwWkqmzEDpmIemYhaRjASPLKkbR4tTi4tx0I2O91KLM5OLi/Dy9vNSSTYzA SDu45bfuDsbVrx0PMQpwMCrx8D7YZxYuxJpYVlyZe4hRgoNZSYRXx9U8XIg3JbGyKrUoP76o NCe1+BCjNAeLkjiv/0vFcCGB9MSS1OzU1ILUIpgsEwenVAOje4vn4Y9HZ0t2eDhVr5nKuylO 9+P/iWefzmp95H4pneUE75kPUj2T/vGZFFs+2BOg/TZa5pOm3o73bz73S0df11A+8HK2s2R0 9dTObXqmzzimXt37uCuk7cCenUrJUWcnBrGyPmC2W5c3v+qkjr3HXYG+QNcF1QuUXsz7diVm scdWyfbJczT/K7EUZyQaajEXFScCAP43mKSwAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/gCi9potNfe74b-o3_qDuXqUTaS0>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 15:51:18 -0000

SGksDQoNCj5Tb21lIGNvbW1lbnRzIG9uIHRoZSBuZXcgZHJhZnQ6DQo+DQo+VGhlIGxpc3RlZCBz
eW50YXggZm9yIHRoZSBuZXcgYXR0cmlidXRlOg0KPg0KPiAgIGZpbmdlcnByaW50LWxpc3QgPSAg
ImZwbCIgIjoiIGhhc2gtZnVuYyBTUCBmaW5nZXJwcmludA0KPiAgICAgICAgICAgICAgICAgICAg
ICAgKigiOiIgaGFzaC1mdW5jIFNQIGZpbmdlcnByaW50KQ0KPg0KPiBUaGlzIGlzbid0IGNvbnNp
c3RlbnQgd2l0aCB0aGUgZXhhbXBsZS4gSSB0aGluayB5b3UgbWVhbnQ6DQo+DQo+ICAgZmluZ2Vy
cHJpbnQtbGlzdCA9ICAiZnBsIiAiOiIgaGFzaC1mdW5jIFNQIGZpbmdlcnByaW50DQo+ICAgICAg
ICAgICAgICAgICAgICAgICAqKCI6IiBoYXNoLWZ1bmMgU1AgZmluZ2VycHJpbnQpDQoNCkkgc2Vl
IG5vIGRpZmZlcmVuY2UgOikNCg0KQnV0LCBJIGFncmVlIHRoZSBleGFtcGxlIGlzIG5vdCBhbGln
bmVkIHdpdGggdGhlIHN5bnRheC4NCg0KPkxhdGVyLCBpbiA0LjIsIGlzOg0KPg0KPiAgICBJZiB0
aGUgb2ZmZXJlciBhc3NvY2lhdGVzIGJvdGggJ2ZwbCcgYXR0cmlidXRlcyBhbmQgJ2ZpbmdlcnBy
aW50Jw0KPiAgICBhdHRyaWJ1dGVzIHdpdGggdGhlICJtPSIgbGluZSBpbiB0aGUgb2ZmZXIsIHRo
ZSBmaW5nZXJwcmludCB2YWx1ZQ0KPiAgICBpbmNsdWRlZCBpbiBhbnkgJ2ZpbmdlcnByaW50JyBh
dHRyaWJ1dGUgTVVTVCBhbHNvIGJlIGluY2x1ZGVkIGluIHRoZQ0KPiAgICAnZnBsJyBhdHRyaWJ1
dGUgYXNzb2NpYXRlZCB3aXRoIHRoZSBzYW1lIGNlcnRpZmljYXRlLg0KPg0KPiBXaHkgaXMgdGhp
cyBNVVNUPyBDZXJ0YWlubHkgaXQgc2hvdWxkIGJlIGFsbG93ZWQuIEJ1dCBpdCBtYXkgYmUgdGhh
dCB0aGUgc2VuZGVyIGRvZXNuJ3QgdHJ1c3QgdGhhdCBoYXNoLiBJZiBub3QsIHdoeSBpbmNsdWRl
IGl0Lg0KDQpZb3Ugd2FudCBhIE1BWT8NCg0KPlNlY3Rpb24gNC4zOg0KPg0KPiAgICBJZiB0aGUg
b2ZmZXIgZG9lcyBub3QgY29udGFpbiBhbnkgJ2ZwbCcgYXR0cmlidXRlLCB0aGUgYW5zd2VyZXIN
Cj4gICAgU0hPVUxEIE5PVCBhc3NvY2lhdGUgYW55ICdmcGwnIGF0dHJpYnV0ZSB3aXRoIHRoZSBj
b3JyZXNwb25kaW5nICJtPSINCj4gICAgbGluZSBpbiB0aGUgYW5zd2VyLg0KPg0KPiBXaHkgbm90
IE1VU1QgTk9UPw0KDQpJIGNhbiBkbyB0aGF0Lg0KDQoNCj5UaGVuOg0KPg0KPiAgICBJZiB0aGUg
b2ZmZXIgY29udGFpbnMgb25lIG9yIG1vcmUgU0RQICdmaW5nZXJwcmludCcgYXR0cmlidXRlcywg
dGhlDQo+ICAgIGFuc3dlcmVyIGZvbGxvd3MgdGhlIHByb2NlZHVyZXMgaW4gW1JGQzQ1NzJdIGZv
ciBnZW5lcmF0aW5nIHRoZQ0KPiAgICBhbnN3ZXIuDQo+DQo+IEkgdGhpbmsgdGhpcyBuZWVkcyB0
byBiZSBmdXJ0aGVyIHF1YWxpZmllZCAtIHRoaXMgYXBwbGllcyBpZiAnZmluZ2VycHJpbnQnICpp
cyogcHJlc2VudCBhbmQgJ2ZwbCcgKmlzIG5vdCogcHJlc2VudC4NCg0KV2VsbCwgSSB3YXMgdGhp
bmtpbmcgdGhhdCBpdCBzaG91bGQgYmUgYWxsb3dlZCB0byBpbmNsdWRlIGJvdGggYXR0cmlidXRl
cyBhbHNvIGluIHRoZSBhbnN3ZXIuIEJ1dCwgaWYgd2UgZG9uJ3Qgd2FudCB0aGF0LCBJIGFncmVl
IHdpdGggeW91Lg0KDQo+VGhlbjoNCj4NCj4gICAgSWYgdGhlIGFuc3dlcmVyIGFzc29jaWF0ZXMg
Ym90aCAnZnBsJyBhdHRyaWJ1dGVzIGFuZCAnZmluZ2VycHJpbnQnDQo+ICAgIGF0dHJpYnV0ZXMg
d2l0aCB0aGUgIm09IiBsaW5lIGluIHRoZSBhbnN3ZXIsIHRoZSBmaW5nZXJwcmludCB2YWx1ZQ0K
PiAgICBpbmNsdWRlZCBpbiBhbnkgJ2ZpbmdlcnByaW50JyBhdHRyaWJ1dGUgTVVTVCBhbHNvIGJl
IGluY2x1ZGVkIGluIHRoZQ0KPiAgICAnZnBsJyBhdHRyaWJ1dGUgYXNzb2NpYXRlZCB3aXRoIHRo
ZSBzYW1lIGNlcnRpZmljYXRlLg0KPg0KPiBJIHRoaW5rIGlmIGJvdGggYXJlIHByZXNlbnQgaW4g
dGhlIG9mZmVyLCB0aGVuICdmaW5nZXJwcmludCcgc2hvdWxkIGJlIGlnbm9yZWQsIGFuZCBub3Qg
aW5jbHVkZWQgaW4gdGhlIGFuc3dlci4NCg0KU2VlIGFib3ZlLg0KDQo+IFVwZGF0ZSB0byA0NTcy
Og0KPg0KPiBXaHkgaXMgdGhlIHRleHQgY2hhbmdlIG1hZGU/IEkgdGhvdWdodCB0aGlzIGlzIG5v
dyBmb3IgYmFja3dhcmQgY29tcGF0aWJpbGl0eSBvbmx5LCBzbyB0aGUgcmVzdHJpY3Rpb24gb24g
dGhlIGhhc2ggZnVuY3Rpb24gDQo+IHVzZWQgc2hvdWxkIHJlbWFpbi4gSSB0aGluayBpdCBzaG91
bGQgYmUgZHJvcHBlZCwga2VlcGluZyBvbmx5IHRoZSBuZXcgdGV4dCBvbiBtdWx0aXBsZSBmaW5n
ZXJwcmludHMuDQoNCkFyZSB5b3UgdGFsa2luZyBhYm91dCB0aGUgcmVzdHJpY3Rpb24gb2YgdXNp
bmcgdGhlIHNhbWUgaGFzaCBmdW5jdGlvbiBmb3IgdGhlIGZpbmdlcnByaW50IGFuZCB0aGUgY2Vy
dGlmaWNhdGUgc2lnbmF0dXJlPw0KDQpFdmVuIGlmIHdlJ2QgcmVtb3ZlIHRoYXQgcGFydCwgdGhl
IHRleHQgY2hhbmdlIHN0aWxsIHVwZGF0ZXMgdGhlIHByZWZlcnJlZCBoYXNoIGZ1bmN0aW9uLCBh
bmQgY2xhcmlmaWVzIHRoZSBzZW1hbnRpY3Mgb2YgbXVsdGlwbGUgJ2ZpbmdlcnByaW50JyBhdHRy
aWJ1dGVzLg0KDQooV2hlbiBpdCBjb21lcyB0byB0aGUgcHJlZmVycmVkIGhhc2ggZnVuY3Rpb24g
ZXRjLCBJJ2QgbGlrZSB0aGUgbmV3IGRyYWZ0IHRvIHJlZmVyZW5jZSA0NTcyLCBzbyB3ZSBkb24n
dCBoYXZlIHRvIHJlLXdyaXRlIGV2ZXJ5dGhpbmcuKQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0K
DQoNCg0KDQpPbiA1LzE0LzE2IDU6MDcgQU0sIENocmlzdGVyIEhvbG1iZXJnIHdyb3RlOg0KPiBI
aSwNCj4NCj4NCj4NCj4gSeKAmXZlIHB1dCB0b2dldGhlciBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBk
cmFmdCwgd2hpY2ggZGVmaW5lcyBhIG5ldyANCj4gYXR0cmlidXRlLCDigJxmcGzigJ0gKHdlIGNh
biBkaXNjdXNzIHRoZSBuYW1lIGxhdGVyKS4NCj4NCj4NCj4NCj4gSSBoYXZlIG5vdCBzdWJtaXR0
ZWQgaXQgdG8gSUVURiB5ZXQsIGJlY2F1c2UgSSBmaXJzdCB3YW50IHRvIG1ha2Ugc3VyZSANCj4g
d2UgYWdyZWUgb24gbW92aW5nIGZvcndhcmQgd2l0aCBhIG5ldyBhdHRyaWJ1dGUuIEhvd2V2ZXIs
IGl04oCZcyANCj4gYXZhaWxhYmxlIG9uIEdpdEh1Yi4NCj4NCj4NCj4NCj4gaHR0cHM6Ly9naXRo
dWIuY29tL2NkaDR1L2RyYWZ0LTQ1NzItdXBkYXRlICAgKE5PVEU6IEluZGl2aWR1YWwgcmVwbykN
Cj4NCj4NCj4NCj4gTk9URSB0aGUgZm9sbG93aW5nOg0KPg0KPg0KPg0KPiAtICAgICAgICAgIFRo
ZSBuZXcgYXR0cmlidXRlIGlzIG5vdCBkZWZpbmVkIGFzIGFuIHVwZGF0ZSB0byA0NTcyLg0KPg0K
PiAtICAgICAgICAgIDQ1NzIgaXMgdXBkYXRlZCB0byBjbGFyaWZ5IHRoYXQgbXVsdGlwbGUgU0RQ
IOKAmGZpbmdlcnByaW50c+KAmQ0KPiBhdHRyaWJ1dGVzIGFyZSBhbGxvd2VkLCBidXQgZWFjaCBt
dXN0IGJlIGFzc29jaWF0ZWQgd2l0aCBhIGRpZmZlcmVudCANCj4gY2VydGlmaWNhdGUuIElmIHlv
dSB3YW50IG11bHRpcGxlIGhhc2hlcyBmb3IgYSBzaW5nbGUgY2VydGlmaWNhdGUsIHlvdSANCj4g
bmVlZCB0aGUgbmV3IGF0dHJpYnV0ZQ0KPg0KPiAtICAgICAgICAgIFBhdWwsIEkga25vdyBJIHVz
ZSB0aGUgb2xkIHN5bnRheCBmb3JtYXQg4oCTIHdpbGwgYmUgZml4ZWQgbGF0ZXIgOikNCj4NCj4N
Cj4NCj4gWWVzLCB0aGVyZSBhcmUgdGhpbmdzIG1pc3NpbmcsIGJ1dCBhdCB0aGlzIHBvaW50IEkg
d2FudCBjb21tZW50cyBvbiANCj4gd2hldGhlciBwZW9wbGUgdGhpbmsgdGhpcyBpcyB0aGUgY29y
cmVjdCBhcHByb2FjaC4gSWYgc28sIEnigJlsbCBzdWJtaXQgDQo+IHRoZSBkcmFmdCB0byBJRVRG
Lg0KPg0KPg0KPg0KPiBSZWdhcmRzLA0KPg0KPg0KPg0KPiBDaHJpc3Rlcg0KPg0KPg0KPg0KDQo=


From nobody Sat May 14 08:51:36 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0949312D11A for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:51:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_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 CJGvqy-bFBTT for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 08:51:33 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5837D12D0D3 for <mmusic@ietf.org>; Sat, 14 May 2016 08:51:32 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id 190so166178431iow.1 for <mmusic@ietf.org>; Sat, 14 May 2016 08:51:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=WC/JIWwBItpJvLOcFTB9lbxyoIfL8be1ac8g158Swbw=; b=ZPw+pzNlr1ktz9a120cHE8MI5443E2i4jR6u+UU+bI8W+rZ9COXA/OZ3rZrDqHIKqf ADdAjj9ftrn2TcyRFBL0kjRKoCQgIEojQ1b+JOoEdXkHD7DWwrHZ4qR7NYLpntpivxes hlm4hOL3tQXLobYJqvR5H2gXzpqwtmVmTWcgvFHVk8sMIa6zrlDIuvz6rrwmk+72EjOz iVXosKz6i7xok7wbAilpWFrGbdGjoDBb810Z/UHsG2Mzn9/aN9VIysWoKSbL+wiMDlia aoysXu2HnaPfxkdcz0crmFuUDHrrIEAx8fIlzM4uwz/EjMlF/JT1gy/bVkZjruDNg0Yu m8cA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=WC/JIWwBItpJvLOcFTB9lbxyoIfL8be1ac8g158Swbw=; b=R0vC6NmigaT+9/7tE+j7SVnu4u0BlFUoIY/0/nBSJ51dyGvTf3l67GNuqYI1XH/57J iocnwidKtKYxXVpXguQdUCOWNvxIt025pIuJxPrYBEUyLikfaIknV2+1272RxU5CUorq pbDR9DQx0uPawts5RW+ee1/gWbtVSCrTcxGcZtrWmCNA0msBxsUEPuLIWxMOpA+6jkvx DhuQoRu62bwbG7EK+X7qJazO5rQFrqGX7al+eaSThjJdHZ05w5Adyxe6QxW+hT0sSSis kCOZ1Dh6PWUY4cQiELw4LqPA/o054TZtXfwpXvJw3KCHrvu6BioPjVQFvfw9xvX1le2r 3QWg==
X-Gm-Message-State: AOPr4FUUHU61KU8acHHH8Waz8euQAc3eRog+nv55rJfHUGpAGzRd7zGGcNd6g8UueVzyu+dMt1ps0srzZZOqcA==
MIME-Version: 1.0
X-Received: by 10.107.161.195 with SMTP id k186mr1580840ioe.190.1463241091759;  Sat, 14 May 2016 08:51:31 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sat, 14 May 2016 08:51:31 -0700 (PDT)
In-Reply-To: <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358ABDC.8392%christer.holmberg@ericsson.com> <CABkgnnX=e8c6W1YzTdNiJvxQJPP+rJBF2_RZju68cbZHc4JaXg@mail.gmail.com> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu>
Date: Sat, 14 May 2016 08:51:31 -0700
Message-ID: <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Rd60zjE66hK5R0N0eBFZvdZkShU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 15:51:36 -0000

On 14 May 2016 at 07:42, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> ISTM that this should be entirely up to the receiver. It should be allowed
> to check them all, and fail if they don't all match. That means the sender
> must ensure that all those sent are valid. But the receiver MAY only check
> one or a few that it trusts. Probably a receiver SHOULD check at least the
> strongest one it understands.


This is right, though I would add that if that strongest one is
present in any way, but NOT matched, then it MUST fail the match.


From nobody Sat May 14 09:03:24 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72E912D0DA for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 09:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[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 dMZ4kn62AL6W for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 09:03:22 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7709012B012 for <mmusic@ietf.org>; Sat, 14 May 2016 09:03:22 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-bd-57374c48a2a5
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 4F.66.27088.84C47375; Sat, 14 May 2016 18:03:20 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0248.002; Sat, 14 May 2016 18:03:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: draft-4572-update: New attribute [was: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01]
Thread-Index: AdGtvzRUT4Od/vD5TACmu5icBDjBUQAJf5cAAARUvhD//+GgAP//3bsQ
Date: Sat, 14 May 2016 16:03:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FB28E5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se> <CABkgnnVS+akLQ9ssvMnU35VRRrBJYMzsBHJRMotQpvDM8Lrc7Q@mail.gmail.com>
In-Reply-To: <CABkgnnVS+akLQ9ssvMnU35VRRrBJYMzsBHJRMotQpvDM8Lrc7Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7rq6Hj3m4wZVZRhY3579lsbh25h+j xdTlj1ksVmw4wGox48JUZgdWj7/vPzB57Jx1l91jyZKfTB63phQEsERx2aSk5mSWpRbp2yVw ZRzbJ1hwhq/i047NTA2Mc/i6GDk5JARMJD4+mskOYYtJXLi3nq2LkYtDSOAIo8S5hxfZIZwl jBLPtq1n7mLk4GATsJDo/qcN0iAioCux6OwDsBpmgXmMEkt3HWEGSQgLFEscPnqQCaKoRGLf kT5GCNtN4vufO2DbWARUJbY3HAer5xXwlWjfuYgFYtl8Jokp3zvZQZZxCgRKXLzgB1LDCHTd 91NrwGYyC4hL3HoynwniagGJJXvOM0PYohIvH/9jhbCVJFZsv8QIMoZZQFNi/S59iFZFiSnd D9kh1gpKnJz5hGUCo9gsJFNnIXTMQtIxC0nHAkaWVYyixanFSbnpRkZ6qUWZycXF+Xl6eakl mxiBsXZwy2+DHYwvnzseYhTgYFTi4VX4bhYuxJpYVlyZe4hRgoNZSYT3nqd5uBBvSmJlVWpR fnxRaU5q8SFGaQ4WJXFe/5eK4UIC6YklqdmpqQWpRTBZJg5OqQbGNXuj07VV+Of+fMD36nau yFI/n0VONo9ep930faf/dINa+u0Xt6dzpMreloiOV4hVeip9Nj+q95fqiQ+Cbke1SzNmMkde 0VoQ+cia7cHSKQtvmc4OblpbtTDecsW/JTOvKF1hMWH4/an1GleCP/uW4y5blZL2FdokdfmH zHrF91awMHSJ0EQ9JZbijERDLeai4kQAVc2x0LECAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Ka3G7aAqOJeK3WAuqHgfiM457_A>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 16:03:24 -0000

SGksDQoNCj5XaGF0IGRvIHlvdSB0aGluayB0aGUgbWF0Y2hpbmcgcnVsZSBzaG91bGQgYmUuICBU
aGF0J3MgdGhlIGNydXggb2YgYWxsIG9mIHRoaXMsIGFsbCB0aGUgc2hpbnkgbmV3IHN5bnRheCBp
biB0aGUgd29ybGQgd29uJ3QgaGVscCB1bmxlc3MgeW91IGFyZSBzdXJlIHdoYXQgeW91IHdhbnQu
DQoNClBlcnNvbmFsbHksIGZvciBhIGdpdmVuIGNlcnRpZmljYXRlLCBJIHRoaW5rIGl0J3MgZW5v
dWdoIGlmIG9uZSBvZiB0aGUgcHJvdmlkZWQgZmluZ2VycHJpbnQgbWF0Y2hlcyB0aGUgY2VydGlm
aWNhdGUuIEJ1dCwgaWYgcGVvcGxlIHRoaW5rIGFsbCBmaW5nZXJwcmludHMgKHRoYXQgdGhlIHJl
Y2VpdmVyIHN1cHBvcnQpIG11c3QgbWF0Y2ggdGhlIGNlcnRpZmljYXRlIEkgd2lsbCBub3QgYXJn
dWUgYWdhaW5zdCB0aGF0Lg0KDQo+PiBXZSBjb3VsZCBvZiBjb3Vyc2UgcmVtb3ZlIHRoZSByZXN0
cmljdGlvbiwgYnV0IHRoZW4gSSB3b25kZXIgaG93IG11Y2ggc2Vuc2UgdGhlIG5ldyBhdHRyaWJ1
dGUgd291bGQgbWFrZS4gU3VyZSwgDQo+PiBpdCB3b3VsZCBhbGxvdyBlbmRwb2ludHMgdG8gZ3Jv
dXAgdGhlIGZpbmdlcnByaW50cyB3aXRoIHRoZSBhc3NvY2lhdGVkIGZpbmdlcnByaW50LCBidXQg
aXMgdGhhdCB3b3J0aCB0aGUgZWZmb3J0Pw0KPg0KPiBZZXMsIG5vdyB5b3UgYXJlIGdldHRpbmcg
dG8gdGhlIGNvcmUgb2YgdGhlIGlzc3VlLiAgVGhlIHJlc3RyaWN0aW9uIGRvZXNuJ3QgbWFrZSBz
ZW5zZSBiZWNhdXNlIGl0J3MgYSByZXN0cmljdGlvbiB5b3UgY2FuJ3QgZW5mb3JjZSANCj4gaW4g
YW55IG1lYW5pbmdmdWwgd2F5LiAgQW5kIG9uY2UgeW91IGFjY2VwdCB0aGF0LCB0aGUgb25seSBw
cm9ibGVtcyB3ZSByZWFsbHkgaGF2ZSB0byBzb2x2ZSBhcmU6DQo+DQo+IC0gd2hldGhlciB3ZSBj
YXJlIGFib3V0IHNheWluZyB0aGF0IGEgcGFydGljdWxhciBzZXQgb2YgaGFzaGVzIGJlbG9uZyB0
byB0aGUgc2FtZSBjZXJ0aWZpY2F0ZSAobWUsIEkgZG9uJ3QgY2FyZSkNCj4NCj4gLSB3aGV0aGVy
IHdlIGNhcmUgYWJvdXQgdGhlIHdlYWtlc3QtbGluayBhbGdvcml0aG0gKG1lLCBJIGRvIGNhcmU6
IHdlIGFyZSBzdGlsbCBzaGlwcGluZyBjb2RlIHdpdGggU0hBLTEpDQoNClNvLCBldmVudGhvdWdo
IHlvdSBoYXZlIHByb2JhYmx5IHNhaWQgaXQgbWFueSB0aW1lcyBhbHJlYWR5OiB3aGF0IGRvIHlv
dSB0aGluayB0aGUgbWF0Y2hpbmcgYWxnb3JpdGhtIHNob3VsZCBiZT8gV2hlbiBhbnN3ZXJpbmcs
IHBsZWFzZSBjb25zaWRlciB0aGUgUlRQL1JUQ1AgdXNlLWNhc2Ugd2hlcmUgbXVsdGlwbGUgY2Vy
dGlmaWNhdGVzIG1heSBiZSB1c2VkLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg==


From nobody Sat May 14 09:05:40 2016
Return-Path: <kevindempsey70@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 9F9C912B012 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 09:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.549
X-Spam-Level: 
X-Spam-Status: No, score=-0.549 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BW6kFFCEz52A for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 09:05:37 -0700 (PDT)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D09A127058 for <mmusic@ietf.org>; Sat, 14 May 2016 09:05:37 -0700 (PDT)
Received: by mail-vk0-x22f.google.com with SMTP id z184so16653066vkg.0 for <mmusic@ietf.org>; Sat, 14 May 2016 09:05:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Zt9GSns8RKB5oGdCF1VWQ32qS9G+TTRX9E9mt2S7uic=; b=f4/WxXOf63yGyuqG2nznVs8VpwGjU2Tvs0bvLCxKtRppUMZfVIjOmoC2v16FNs9KIo QWo3LYFUCxzV9N1NwasVJjGGs1/3uaXKz3vEk4B6p+sN/gXSvGa/8O6MPxRKGnOFq3b3 EvuD9RuZlL6Mq+DQAGFAtDD1+CuN5gkINcd0feBZRNHavU+8r5Vjw9GMsBVGuqXG3ojN bZt68cJgsJ8zvvytLHlshTDsvzG132T0uLYPm5AWX3zsJ6mP3CwTCNJe42L47f6OBnC/ W3o6yJbOQGZCXBnnVj3M9HOi8gYfqg1xsHsPkZb4RsHd+q3QxAo7wlctUdDKVuCMeJMS AOQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Zt9GSns8RKB5oGdCF1VWQ32qS9G+TTRX9E9mt2S7uic=; b=SXJcdGAYq867yLvQOamXGLLfUrEN0fMaZUhV26T6/AVTpM1O0FycDclL4IR5zfIIyF qFmeFl/vJQWNOeUcMNTqi55E1FkqongY7nk6xrDn54+BYCsRSjSk6UwSWBRlv7Ig5El4 7yBeUL73GWbHLSD0B652WP4N2uJ/resPAgqwzz9NpLknrFiCC3A3cT1D8UP30Gl4loAl WvsCCw5f9hCUa1EWkmuTUvgaJI1rLZEfy2AHn598QT3Un9lMT+IzdOb0nPrB75/t2i/b Nd6KFrKv1LfLkRI/gtDk5EageK58JUIc/UPREmxH/Uemy/CMQ48eU5Wq1cgFvj/+OJVW jlgA==
X-Gm-Message-State: AOPr4FXlJt5vsqbAq9qXtFjBi09oGSH9n0LXSURYCNDE+9c1mAsQQMbkTumxTOj2g+JxPC5YoG/viRexwy05Bg==
MIME-Version: 1.0
X-Received: by 10.31.81.199 with SMTP id f190mr9302843vkb.139.1463241936644; Sat, 14 May 2016 09:05:36 -0700 (PDT)
Received: by 10.159.32.132 with HTTP; Sat, 14 May 2016 09:05:36 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FB289D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <7e3d8424-b5f8-8b11-7db1-f5d10ae65091@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FB289D@ESESSMB209.ericsson.se>
Date: Sat, 14 May 2016 17:05:36 +0100
Message-ID: <CAMvTgcd=UWdv19BA=bnkmpT-ECpkD=jxG-_D7AC+_8Hf6Nh2kA@mail.gmail.com>
From: Kevin Dempsey <kevindempsey70@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114e231cdab8d50532cf8fae
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/wXOjx0Mx5d1Xw6pIptgOJ9SJJ3o>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 16:05:38 -0000

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

If an offer has two a=fingerprint lines with different hashes for a single
certificate, by only requiring one a=fingerprint line to match, an attacker
would only need to produce a certificate that matches the weakest hash to
be accepted.

The problem is that there is no way of knowing if two a=fingerprint lines
with different hashes are for the same certificate or different ones. The
new attribute makes it clear which fingerprints are derived from the same
certificate.

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

<div dir=3D"ltr">If an offer has two a=3Dfingerprint lines with different h=
ashes for a single certificate, by only requiring one a=3Dfingerprint line =
to match, an attacker would only need to produce a certificate that matches=
 the weakest hash to be accepted.<div><br></div><div>The problem is that th=
ere is no way of knowing if two a=3Dfingerprint lines with different hashes=
 are for the same certificate or different ones. The new attribute makes it=
 clear which fingerprints are derived from the same certificate.</div></div=
>

--001a114e231cdab8d50532cf8fae--


From nobody Sat May 14 09:09:34 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C31412B035 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 09:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QgmXs93Rrl5y for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 09:09:32 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D5312B012 for <mmusic@ietf.org>; Sat, 14 May 2016 09:09:32 -0700 (PDT)
Received: by mail-ig0-x229.google.com with SMTP id qe5so25813553igc.1 for <mmusic@ietf.org>; Sat, 14 May 2016 09:09:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=sIKtCr9VkJGodIrk4U+TVD7CRITUJfWfJ7DjIRGkGD4=; b=m9VO1YokYXZaszAz+uJrlMFIXYBScq3o1TkqtJQBEyR6KCgKjYmQfBMfkkoE+KBBfu 6epNHKtwZKehTyTnAhQGSxAa1eOYYnq57q7rgRHoQcbSZlyq7EQm0qALEXVog+mOjpAt sBLiVCZYtZDPqrbZHAHjfvk6NGrZn6+F0Re0HKonCXral6O5edF7AMirv8MA+urXK30N XY8juxKV/M4LBzsIVIDHJPNme0UxBKQNSw7A75KxdBS2DKRhlWdD33WeqgjKZ/i7tbDu OT52co46sghC/cTwLXKXxtcr/G6maGu4CsGKwhVeIyXiF84X1xsksjhWV0Q+4hg+TViw Rw9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=sIKtCr9VkJGodIrk4U+TVD7CRITUJfWfJ7DjIRGkGD4=; b=AzCnph5c/p5lsWC4Lv7RTd3rVkQacBfB2BeRQQeJtXc1XqPhpdn/XqEbm3lCOFlLDp L8ggpSO0RWqk3GrR7j/EDUMyrNve2ZgmzBEcuq1z0OK3vz1YjMkq2wmmwHzBB2hYvnSO AfHeHXLb3z31vWzcnsqCFLtnvgWzFdkI4ZrPgTkYxv9b/9qZ6xl+sA4TWpDwOSHUwapk mKkUo84moDsqfAm5k4V/3EoYQ6ngcYVgd28RGuCHxiMVM4sxeu7W3NONPwMQI6xDVHBI nYbsCK5yKyASbYWPYYDcj37iKNaR+6vn2OOkoFDnYSnHOS/3TzcMltHQnodUw8JyfTw+ bhKA==
X-Gm-Message-State: AOPr4FXvLB+o/h+0omblt1x7uW571/HzOg4xKFSXkCK6Fe+J4JE5Wcfy0HNsRk3qP7Le0ewfkixmcaNrrR1t6w==
MIME-Version: 1.0
X-Received: by 10.50.33.81 with SMTP id p17mr4313212igi.58.1463242171465; Sat, 14 May 2016 09:09:31 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sat, 14 May 2016 09:09:31 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FB28E5@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se> <CABkgnnVS+akLQ9ssvMnU35VRRrBJYMzsBHJRMotQpvDM8Lrc7Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB28E5@ESESSMB209.ericsson.se>
Date: Sat, 14 May 2016 09:09:31 -0700
Message-ID: <CABkgnnUSDphbBo-m+SyH3j_n39nHre36v_nWcEPPjt191Z6EXg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-mbKuIQNtEQIUoeSDMradHQHAlU>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 16:09:33 -0000

On 14 May 2016 at 09:03, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> So, eventhough you have probably said it many times already: what do you think the matching algorithm should be? When answering, please consider the RTP/RTCP use-case where multiple certificates may be used.


For each certificate:
 For each hash you support, there are three options:
   A fingerprint is present and matches: count these
   A fingerprint is present but there are no matches: ABORT AND FAIL
   No fingerprint is present
  If the count for a certificate is zero: ABORT AND FAIL

It's not difficult, but it allows for multiple certificates, multiple
hash algorithms, and it avoids the case where an attack can exploit
the presence of weak hashes.


From nobody Sat May 14 12:05:24 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5886312D138 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 12:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level: 
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id je5si67WI_gb for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 12:05:22 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DFDD12D0C3 for <mmusic@ietf.org>; Sat, 14 May 2016 12:05:22 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id 190so169311975iow.1 for <mmusic@ietf.org>; Sat, 14 May 2016 12:05:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=0VR5z5E9P7mzbw2WK81wTjlhw5L6wHVbVjY5pSEDCbw=; b=pcbsRQPZJAnt1MomOxFB8RVK1tKiz9L7QweRqKVCLsbkRUF5v+TKVsy40nkbWZ0K+v mCL2CSih7DiM89XDt+SdiwZpUyzU762ZxwRpeqcsCrQcyqhccRx7W0ERrr4mttT6blPB kJv0otzAkGJoCH8RnFo+zGemsnl1JBZ6BayfWZ/TsyCH+BnRlifNafdnTf7DVt8t59WS 67XVu1mLRMtIn6etJF/jwMcKKOGk3atV1qDc4apHO0r/31KsB0YOqoxK6ARTmqsBAeo0 6T1gB59sWeFohSp637FrLcgrxWzdZdg0PHvFb6kYVSwHzzLDbYI4ULgkY8fUeUjQ73o4 yuNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=0VR5z5E9P7mzbw2WK81wTjlhw5L6wHVbVjY5pSEDCbw=; b=KAlnyTWBsnox1NlUMCrixX/4d1cY8lVyS/FF6hMCR9Rv2G6RB5zuhhZuvx+lSMLp+q klSOxOEBSPtGD0O3oep2y9ia7w9yJwWWMjgytKHhc2deCClwKIfeDVcS0nKlCgPGGnG4 K3tR92EYBk5u8yZtmBGEQMW5rc/U8nTkH+kqEqZ3PPice0jAt8349fvaTZqXOardEWTD xAih0ToLimqq4yfumDkwCUiNPeB41HOqr8k6UETJd0zNPCTCN5tRXM9qL6FnyVBDxg19 YQCKOSSYcMNHqOSW/kL2lym9f/NJ/2RMxs48+HnPXxt9r9b+PvD0BPdCKkH5eFTe7iBZ m5xg==
X-Gm-Message-State: AOPr4FV0oI0xV6L/jz4gVsrF4f2r2EZNnkrDkU8MZCOyPNB1aMYE7YxxWohgY2MeIWRYJg==
X-Received: by 10.36.87.67 with SMTP id u64mr5286608ita.26.1463252721465; Sat, 14 May 2016 12:05:21 -0700 (PDT)
Received: from mail-ig0-f175.google.com (mail-ig0-f175.google.com. [209.85.213.175]) by smtp.gmail.com with ESMTPSA id qn2sm2889755igc.20.2016.05.14.12.05.20 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Sat, 14 May 2016 12:05:20 -0700 (PDT)
Received: by mail-ig0-f175.google.com with SMTP id s8so25003736ign.0 for <mmusic@ietf.org>; Sat, 14 May 2016 12:05:20 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.37.147 with SMTP id y19mr5971806igj.42.1463252720284; Sat, 14 May 2016 12:05:20 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Sat, 14 May 2016 12:05:20 -0700 (PDT)
In-Reply-To: <CABkgnnUSDphbBo-m+SyH3j_n39nHre36v_nWcEPPjt191Z6EXg@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se> <CABkgnnVS+akLQ9ssvMnU35VRRrBJYMzsBHJRMotQpvDM8Lrc7Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB28E5@ESESSMB209.ericsson.se> <CABkgnnUSDphbBo-m+SyH3j_n39nHre36v_nWcEPPjt191Z6EXg@mail.gmail.com>
Date: Sat, 14 May 2016 15:05:20 -0400
X-Gmail-Original-Message-ID: <CAD5OKxs7g75fk6funVL2ZU-Q=T6odiY_FwzFZ5wdYnEfKsQpCg@mail.gmail.com>
Message-ID: <CAD5OKxs7g75fk6funVL2ZU-Q=T6odiY_FwzFZ5wdYnEfKsQpCg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0444006e9bfff70532d212c7
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/AJUinhmCpMS23tScojqO7kUhDaE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 19:05:23 -0000

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

On Sat, May 14, 2016 at 12:09 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 14 May 2016 at 09:03, Christer Holmberg
> <christer.holmberg@ericsson.com> wrote:
> > So, eventhough you have probably said it many times already: what do you
> think the matching algorithm should be? When answering, please consider the
> RTP/RTCP use-case where multiple certificates may be used.
>
>
> For each certificate:
>  For each hash you support, there are three options:
>    A fingerprint is present and matches: count these
>    A fingerprint is present but there are no matches: ABORT AND FAIL
>    No fingerprint is present
>   If the count for a certificate is zero: ABORT AND FAIL
>
> It's not difficult, but it allows for multiple certificates, multiple
> hash algorithms, and it avoids the case where an attack can exploit
> the presence of weak hashes.
>

This match algorithm is also something that none of the current
implementation do right now and has a potential to fail in interesting and
hard to detect ways if different sets of hashes are present for different
certificates.

The main problem I have with your proposal is that a lot of current
implementations match one of multiple fingerprints right now. With the
matching algorithm that you propose, things which are working with current
implementations might stop working.

Also, as far as I know, most of the fingerprint matching implementations
are part of DTLS-SRTP and in some way related to WebRTC. They tend to be
updated quickly as can be shown by the change in required cipher suits
which recently occurred in Firefox and Chrome. So, I think, it would be
better to fix the current fingerprint attribute problems (matching multiple
hashes against the selected certificate, hex encoding for hash value,
non-extensibility of the attribute) at the same time and provide the
backwards compatible way to migrate. Old fingerprint attribute can then be
killed when new attribute is widely adopted.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Sat, May 14, 2016 at 12:09 PM, Martin Thomson <span dir=3D"ltr">&lt=
;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thoms=
on@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204)=
;padding-left:1ex">On 14 May 2016 at 09:03, Christer Holmberg<br>
<span class=3D"">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com">chri=
ster.holmberg@ericsson.com</a>&gt; wrote:<br>
&gt; So, eventhough you have probably said it many times already: what do y=
ou think the matching algorithm should be? When answering, please consider =
the RTP/RTCP use-case where multiple certificates may be used.<br>
<br>
<br>
</span>For each certificate:<br>
=C2=A0For each hash you support, there are three options:<br>
=C2=A0 =C2=A0A fingerprint is present and matches: count these<br>
=C2=A0 =C2=A0A fingerprint is present but there are no matches: ABORT AND F=
AIL<br>
=C2=A0 =C2=A0No fingerprint is present<br>
=C2=A0 If the count for a certificate is zero: ABORT AND FAIL<br>
<br>
It&#39;s not difficult, but it allows for multiple certificates, multiple<b=
r>
hash algorithms, and it avoids the case where an attack can exploit<br>
the presence of weak hashes.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">This match algorith=
m is also something that none of the current implementation do right now an=
d has a potential to fail in interesting and hard to detect ways if differe=
nt sets of hashes are present for different certificates.</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The main problem I ha=
ve with your proposal is that a lot of current implementations match one of=
 multiple fingerprints right now. With the matching algorithm that you prop=
ose, things which are working with current implementations might stop worki=
ng.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Al=
so, as far as I know, most of the fingerprint matching implementations are =
part of DTLS-SRTP and in some way related to WebRTC. They tend to be update=
d quickly as can be shown by the change in required cipher suits which rece=
ntly occurred in Firefox and Chrome. So, I think, it would be better to fix=
 the current fingerprint attribute problems (matching multiple hashes again=
st the selected certificate, hex encoding for hash value, non-extensibility=
 of the attribute) at the same time and provide the backwards compatible wa=
y to migrate. Old fingerprint attribute can then be killed when new attribu=
te is widely adopted.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">Regards,</div><div class=3D"gmail_extra"><div><div class=
=3D"gmail_signature">_____________<br>Roman Shpount</div></div><div><br></d=
iv></div></div>

--f46d0444006e9bfff70532d212c7--


From nobody Sat May 14 12:59:16 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2296012D093 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 12:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.272
X-Spam-Level: 
X-Spam-Status: No, score=0.272 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.972] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ui2HkNrX1EuC for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 12:59:13 -0700 (PDT)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A449A12B046 for <mmusic@ietf.org>; Sat, 14 May 2016 12:59:13 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by comcast with SMTP id 1fiSbhE0nBE6O1fiSbcnmC; Sat, 14 May 2016 19:59:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463255952; bh=Lh11Qot51X1vX0F7dmtbiZRluIsYX63QF5YqxeRFpxE=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=JfBhQLEZ81AnzPNa0sIblkLaUv2Pz2P9BhhoCFgl7/CtDIZqHgXaMH49CxjFp/4ZV 6G522OxiGwDJGvXdw4WShczg+/hLolajZXYXdW5PnPeOzyJdHl5txJ3h4FIMId130E f53YqrK6WyLRd0NNNzeHzmKuH8ZfRPCozCVrbrg1H8XOFLdjcbQdKddSdQ6XKvs7n/ siLylVQTnTqSMCdTJbb5OcPE2tyB5icQSlFt0oIJhSfJquRXD2b4jQLYSc9yEmfkEg B2/ymX+z8/mpvs81y6rhiiLFXXpiC4zCMdEs4+I6zyIvyV1qKzyPBYozMlXFPI0yDz AuRqVOIVCgpLQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-08v.sys.comcast.net with comcast id uKzC1s0033KdFy101KzCrf; Sat, 14 May 2016 19:59:12 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <7e3d8424-b5f8-8b11-7db1-f5d10ae65091@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FB289D@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ba8de5fc-96b1-95ec-c3cd-b3d773504c2b@alum.mit.edu>
Date: Sat, 14 May 2016 15:59:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FB289D@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/cKH5M8zA57gLAC5Mo5xphtcZhts>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 19:59:15 -0000

On 5/14/16 11:51 AM, Christer Holmberg wrote:
> Hi,
>
>> Some comments on the new draft:
>>
>> The listed syntax for the new attribute:
>>
>>   fingerprint-list =  "fpl" ":" hash-func SP fingerprint
>>                       *(":" hash-func SP fingerprint)
>>
>> This isn't consistent with the example. I think you meant:
>>
>>   fingerprint-list =  "fpl" ":" hash-func SP fingerprint
>>                       *(":" hash-func SP fingerprint)
>
> I see no difference :)
>
> But, I agree the example is not aligned with the syntax.

Oops. s/":"/SP/

>> Later, in 4.2, is:
>>
>>    If the offerer associates both 'fpl' attributes and 'fingerprint'
>>    attributes with the "m=" line in the offer, the fingerprint value
>>    included in any 'fingerprint' attribute MUST also be included in the
>>    'fpl' attribute associated with the same certificate.
>>
>> Why is this MUST? Certainly it should be allowed. But it may be that the sender doesn't trust that hash. If not, why include it.
>
> You want a MAY?

That seems right.

>> Section 4.3:
>>
>>    If the offer does not contain any 'fpl' attribute, the answerer
>>    SHOULD NOT associate any 'fpl' attribute with the corresponding "m="
>>    line in the answer.
>>
>> Why not MUST NOT?
>
> I can do that.
>
>
>> Then:
>>
>>    If the offer contains one or more SDP 'fingerprint' attributes, the
>>    answerer follows the procedures in [RFC4572] for generating the
>>    answer.
>>
>> I think this needs to be further qualified - this applies if 'fingerprint' *is* present and 'fpl' *is not* present.
>
> Well, I was thinking that it should be allowed to include both attributes also in the answer. But, if we don't want that, I agree with you.
>
>> Then:
>>
>>    If the answerer associates both 'fpl' attributes and 'fingerprint'
>>    attributes with the "m=" line in the answer, the fingerprint value
>>    included in any 'fingerprint' attribute MUST also be included in the
>>    'fpl' attribute associated with the same certificate.
>>
>> I think if both are present in the offer, then 'fingerprint' should be ignored, and not included in the answer.
>
> See above.
>
>> Update to 4572:
>>
>> Why is the text change made? I thought this is now for backward compatibility only, so the restriction on the hash function
>> used should remain. I think it should be dropped, keeping only the new text on multiple fingerprints.
>
> Are you talking about the restriction of using the same hash function for the fingerprint and the certificate signature?

Sorry, there were more changes in there than I realized. The part I was 
objecting to removing is the first part about using the same hash 
function as the certificate. That is fixed by the new attribute, but 
ought to remain for the old one for backward compatibility purposes.

Given that restriction, I don't understand the preferred part. (In 
either the old or updated text.) ISTM the only place this would apply is 
with self signed certificates. It would make more sense to put the 
recommendation in the last sentence on self signed certificates, which 
you removed.

	Thanks,
	Paul

> Even if we'd remove that part, the text change still updates the preferred hash function, and clarifies the semantics of multiple 'fingerprint' attributes.
>
> (When it comes to the preferred hash function etc, I'd like the new draft to reference 4572, so we don't have to re-write everything.)
>
> Regards,
>
> Christer
>
>
>
>
> On 5/14/16 5:07 AM, Christer Holmberg wrote:
>> Hi,
>>
>>
>>
>> Iâ€™ve put together a new version of the draft, which defines a new
>> attribute, â€œfplâ€� (we can discuss the name later).
>>
>>
>>
>> I have not submitted it to IETF yet, because I first want to make sure
>> we agree on moving forward with a new attribute. However, itâ€™s
>> available on GitHub.
>>
>>
>>
>> https://github.com/cdh4u/draft-4572-update   (NOTE: Individual repo)
>>
>>
>>
>> NOTE the following:
>>
>>
>>
>> -          The new attribute is not defined as an update to 4572.
>>
>> -          4572 is updated to clarify that multiple SDP â€˜fingerprintsâ€™
>> attributes are allowed, but each must be associated with a different
>> certificate. If you want multiple hashes for a single certificate, you
>> need the new attribute
>>
>> -          Paul, I know I use the old syntax format â€“ will be fixed later :)
>>
>>
>>
>> Yes, there are things missing, but at this point I want comments on
>> whether people think this is the correct approach. If so, Iâ€™ll submit
>> the draft to IETF.
>>
>>
>>
>> Regards,
>>
>>
>>
>> Christer
>>
>>
>>
>


From nobody Sat May 14 13:18:53 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E19A112D0F4 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 13:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.272
X-Spam-Level: 
X-Spam-Status: No, score=0.272 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.972] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KpAeITc6Amgu for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 13:18:51 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06D8112B036 for <mmusic@ietf.org>; Sat, 14 May 2016 13:18:50 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by comcast with SMTP id 1g0sbxUOYgEHv1g1Sb3tct; Sat, 14 May 2016 20:18:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463257130; bh=Rv63g8TWkWHkbsxfVpmzs61mXDRmsxIPcbdnY/8Dab4=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=arY8VbRxy2Fca4p9boKej68T8/uVCE0Cq28I/AsHHyoXWMdUgj75k2PwnZzkNhB6d 0MBFc+Ne2aHcez5eB++eyTOmg3oxQWvstFAwB70pENbDgaJ+hsbAumtiegvrZiYLnQ tlRd7cc+cKAcyLzy1jwIDnI3l+NstsdRIiF6Fp1R+D2Urcx52t5yVnRjSzKXphTi99 opMzBCoGqE02RZRCcPE8Zixhy7cAvRGXdm6R4aiHJt2Q+DlmEWqokb47KRd+lN/Sx8 2tUR36c6/WxvEBOWW8C8iqjEB7H5hoXcwaspmkDup4kaUIgmJCGUilO9C9YKES4VIP B75/P8VyeO+Mw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-12v.sys.comcast.net with comcast id uLJp1s0073KdFy101LJpAc; Sat, 14 May 2016 20:18:50 +0000
To: Martin Thomson <martin.thomson@gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu>
Date: Sat, 14 May 2016 16:18:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/al_QDfO_Hir7Quq86F2hQAP9wQ8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 May 2016 20:18:52 -0000

On 5/14/16 11:51 AM, Martin Thomson wrote:
> On 14 May 2016 at 07:42, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> ISTM that this should be entirely up to the receiver. It should be allowed
>> to check them all, and fail if they don't all match. That means the sender
>> must ensure that all those sent are valid. But the receiver MAY only check
>> one or a few that it trusts. Probably a receiver SHOULD check at least the
>> strongest one it understands.
>
>
> This is right, though I would add that if that strongest one is
> present in any way, but NOT matched, then it MUST fail the match.
>

The failure of *any* checked fingerprint to match must cause the 
connection to fail.

If you don't check them all, you are implicitly assuming that the 
unchecked ones match.

When a cert is received on a potential connection the general matching 
algorithm could be:

1) first, discover which fpl attribute applies to this certificate:

For each fpl attribute, pick one of the hashes and test it against the 
certificate. If it matches, then this is the right fpl attribute.

2) Do further verification:

Optionally check other hashes from this fpl attribute against the 
certificate.

The connection must fail if (1) finds no matching fpl, or if any check 
from (2) fails.

One could save a bit of work in step 1 by choosing a hash function that 
is common across all the fpl attributes. Then it only needs to be 
computed once.

Or one could, for each fpl attribute, choose the strongest hash you 
support for step 1. Then you could skip step 2.

But these are implementation strategies, and shouldn't be normative.

	Thanks,
	Paul


From nobody Sat May 14 19:52:36 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3D412D117 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 19:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 5hVCzsKHXCjW for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 19:52:34 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 495F012B011 for <mmusic@ietf.org>; Sat, 14 May 2016 19:52:34 -0700 (PDT)
Received: by mail-ig0-x231.google.com with SMTP id m9so26737232ige.1 for <mmusic@ietf.org>; Sat, 14 May 2016 19:52:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=wE3aB8tx52sQ00k2j36YUrE3wRgX2+P3Q4VdYpn+tKY=; b=KGv/oqjAWYB6DH/h8/40/aV5N79uN9QsT/ghNIinh3Mko3CCTsxOGJzQ45acleCTMa OgcQDRNzY1YPRiSEOkmt8u2tGqSzWtq1vE+G+jiAwJk1DsrmR+bYMDGqVkCPt2+F8elr w/Bwm40Nb8Xafd0ekS97TAJSMxbhEd9BlOy01z2d2BRXWpU2aW0aG55XYTqcKwlXQ9/u fNOyTNfWXvA11aI1pm3dSDfddZXMTDf+zxTooqYLIPA3v59hgl5w5gE90O0AENFDsT1r SYIhsJcliWuLa7Qgy4Frb3vTLqWWWLpLTgYXC1P5yMqgUnEBNUwudchAcAxbXWbQxdDp FJ7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=wE3aB8tx52sQ00k2j36YUrE3wRgX2+P3Q4VdYpn+tKY=; b=fK92QzntVujNx+qbYTSRWOW93nIAEzPIP3qctibYYD2jwMW3PhH4oLGRZiCpoAEbCa AzdUfPzV+dO1yk6JDfawQtmlkFpfBBQlPBAFno4rJJHWSxvUTCiFFvcwysM+7aMyT8VG /memJnjtWUpawNANOpC9Xpj5MfnDiq2X+5poRSe53wkWfIBDfPFWGrnnsevGyBfnLIMM HNuz4hLkbMEXP44/G/S3Q+0E24d8ZzE5dXL/jEWMB1Ph3YW7eYTEu4giqRnor8jET2XA /aSRgp6gm0CvNBhGp3Sg3m/y1XDudzF6apMCtxFvNGHAczLFX6TND+sk0TdysuIyZR4j Gl3w==
X-Gm-Message-State: AOPr4FX/Bb+mdIcVT2Fu7V1APU+eT5Ywfzv9bWD4rypw0Qs88tKBfpq6av5OzgbN4+fujWhWLLnO7sP6FSdUSA==
MIME-Version: 1.0
X-Received: by 10.50.58.71 with SMTP id o7mr3701415igq.77.1463280753705; Sat, 14 May 2016 19:52:33 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sat, 14 May 2016 19:52:33 -0700 (PDT)
In-Reply-To: <CAD5OKxs7g75fk6funVL2ZU-Q=T6odiY_FwzFZ5wdYnEfKsQpCg@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37FAF469@ESESSMB209.ericsson.se> <CABkgnnUQ5d86D5==zf1nz6Jqv3Xrj1R52vkLxWfYVNcdd+XP7w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB1853@ESESSMB209.ericsson.se> <CABkgnnVS+akLQ9ssvMnU35VRRrBJYMzsBHJRMotQpvDM8Lrc7Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FB28E5@ESESSMB209.ericsson.se> <CABkgnnUSDphbBo-m+SyH3j_n39nHre36v_nWcEPPjt191Z6EXg@mail.gmail.com> <CAD5OKxs7g75fk6funVL2ZU-Q=T6odiY_FwzFZ5wdYnEfKsQpCg@mail.gmail.com>
Date: Sat, 14 May 2016 19:52:33 -0700
Message-ID: <CABkgnnXioFmsF2uugjwxkRfxwdLKYgdjNwc1GMuJ-DGGvnXw0A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-Wry-iHUQgEtthE7T2u8Pyen_cY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] draft-4572-update: New attribute [was: Draft new version: draft-ietf-mmusic-4572-update-01]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2016 02:52:35 -0000

On 14 May 2016 at 12:05, Roman Shpount <roman@telurix.com> wrote:
> The main problem I have with your proposal is that a lot of current
> implementations match one of multiple fingerprints right now. With the
> matching algorithm that you propose, things which are working with current
> implementations might stop working.

No, that's not a problem at all.  The existing implementations will
match on one fingerprint.  They might match on a weak hash, but that's
not a problem we can fix without pixie dust.

The advantage of this is that it is completely compatible with
existing implementations.  Unless you have an implementation that has
two different certificates for RTP and RTCP AND those have different
hash algorithms for their fingerprint.  Then a new implementation will
fail one or other component.  I consider that a very low risk failure
mode.


From nobody Sat May 14 19:55:33 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B632112D121 for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 19:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 q_S_3pa_1EcE for <mmusic@ietfa.amsl.com>; Sat, 14 May 2016 19:55:30 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A992B12B011 for <mmusic@ietf.org>; Sat, 14 May 2016 19:55:30 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id i75so169898635ioa.3 for <mmusic@ietf.org>; Sat, 14 May 2016 19:55:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=5eemd1kY4fdUmeacbHLmwY0Kflly+YBsvl+FMHV5vT4=; b=0Sk17ssd7mr/McA8ydaJ/L039hfBO73qXUGGN+yE3nAWSKYL+hiNFDRgNdxqmJu4oX 7/MRcv6KYOhrGr1+K1nPk9W7uELZZqZKGKxju8FeEP9Y4qUXODgIJimDzWNnt1Fs+6lX hI+qD+A9IlHggIHl4Vg4aNxLOAzN6e4rkK9GpZqFrgFv8lkbJObbfpJ0Tjs4Hxeopcg1 iZo5Rse1z8bU/vMz/AUWyFOrBJe+JUmRr9fUUICZzAM5cZTji+dK0BoxNGJw8ARhYKOX lIy6BSOXAvKuqDx2eBXxiehKKKh1BhdXshjTSDZh8U2014jOsjAriLUP8rn8Xft2MKqU ooLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=5eemd1kY4fdUmeacbHLmwY0Kflly+YBsvl+FMHV5vT4=; b=gTp2XuJe10BUmRDzV4ruxPUrusAEp/39xdzkjjNHvyv+Q8Y4ysF85UvTjXvDRnvto+ IY1OdcDmLMQw1CqGkwZhgPMNXpm6jzhPH4wAXu1GeMJx3l0+XQD6waPOjDEK3PAadq09 TNfknmV0X6RnPVCuzWLtykA4dkHOwcGVQ8uf1+sNSAJnnC4Lr5aTyyhC9eJrU6jDdiBY rYDqhNm5KeQnXbz1o0CLXXTWkgcfroxqPtf/eofPGQHnzq8wL7IShND9WDlvQNBDzNL3 byWLJoGmp24qUytheWiYU6NHYqwv+a0u9KKkqPGcYZ7+3RG7eqg5n6Pwr+xIJuHdIE+n XBqA==
X-Gm-Message-State: AOPr4FV8cISOyJNq4KT+DozpK66TLYgQPeybGeaWvKgElIp2yfsanAmHmKtzHUZwz25vkKdslmopdYuXywq3tw==
MIME-Version: 1.0
X-Received: by 10.107.136.76 with SMTP id k73mr16380953iod.100.1463280930136;  Sat, 14 May 2016 19:55:30 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Sat, 14 May 2016 19:55:29 -0700 (PDT)
In-Reply-To: <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu>
Date: Sat, 14 May 2016 19:55:29 -0700
Message-ID: <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/yMtifFHkhIZL3adpZmd4PuMrBu4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2016 02:55:32 -0000

On 14 May 2016 at 13:18, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> The failure of *any* checked fingerprint to match must cause the connection
> to fail.

OK, yes, unless you find another line that matches on every hash, sure.

I agree with the rest, though a=fpl doesn't really address the
backwards compatibility concerns that well.


From nobody Sun May 15 12:27:32 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06ECD12D1C9 for <mmusic@ietfa.amsl.com>; Sun, 15 May 2016 12:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-01ogR-uQqM for <mmusic@ietfa.amsl.com>; Sun, 15 May 2016 12:27:29 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A02E912D1C8 for <mmusic@ietf.org>; Sun, 15 May 2016 12:27:28 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-bf-5738cd9ec791
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 10.93.12926.E9DC8375; Sun, 15 May 2016 21:27:26 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0248.002; Sun, 15 May 2016 21:27:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIA==
Date: Sun, 15 May 2016 19:27:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com>
In-Reply-To: <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM2K7k+68sxbhBjOXWlncnP+WxeLamX+M FlOXP2axWLHhAKvFjAtTmR1YPf6+/8DksXPWXXaPJUt+MnncmlIQwBLFZZOSmpNZllqkb5fA lfHxaT9LwQ+2immX2hgbGB+wdTFycEgImEj8OO3SxcgJZIpJXLi3HijMxSEkcIRRYs2d64wQ zhJGiVPzvzOCNLAJWEh0/9MGaRARCJVou7gPLMwsUCbR3B0CEhYW8JS4fvozG0SJl8SFqQvY QcaICDxilJh2rpUFJMEioCrx5PUlMJtXwFfiwvZ/zCC2kMBnDol1BzJBbE6BQIl3126BxRmB jvt+ag0TiM0sIC5x68l8JoijBSSW7DnPDGGLSrx8/I8VwlaSWHt4OwvEbZoS63fpQ7QqSkzp fsgOsVZQ4uTMJywTGMVmIZk6C6FjFpKOWUg6FjCyrGIULU4tTspNNzLWSy3KTC4uzs/Ty0st 2cQIjLSDW36r7mC8/MbxEKMAB6MSD6/CDfNwIdbEsuLK3EOMEhzMSiK8uactwoV4UxIrq1KL 8uOLSnNSiw8xSnOwKInz+r9UDBcSSE8sSc1OTS1ILYLJMnFwSjUwMr0JyhWI8/i/LeedV4YK 49K97Dp3ag7xx1w8OMn5z7NNN32Z6jmeHNq8NGveoQd5XlaVQRVsj0yXz31m8Jn7X/6pJ7fL kr8eelRdcjVnfmGu83bzlW+vMYTI16w31Ga9YZ/w4cgy7u+X09fqic5p8LAskb054cupf0s/ nLrxpt7MWlCcdX4bpxJLcUaioRZzUXEiAE0E7RGwAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/w4BwDXKP2Oqh2pGdn8opQVx722g>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2016 19:27:30 -0000

SGksDQoNCj4+IFRoZSBmYWlsdXJlIG9mICphbnkqIGNoZWNrZWQgZmluZ2VycHJpbnQgdG8gbWF0
Y2ggbXVzdCBjYXVzZSB0aGUgDQo+PiBjb25uZWN0aW9uIHRvIGZhaWwuDQo+DQo+IE9LLCB5ZXMs
IHVubGVzcyB5b3UgZmluZCBhbm90aGVyIGxpbmUgdGhhdCBtYXRjaGVzIG9uIGV2ZXJ5IGhhc2gs
IHN1cmUuDQo+DQo+IEkgYWdyZWUgd2l0aCB0aGUgcmVzdCwgdGhvdWdoIGE9ZnBsIGRvZXNuJ3Qg
cmVhbGx5IGFkZHJlc3MgdGhlIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5IGNvbmNlcm5zIHRoYXQg
d2VsbC4NCg0KTXkgaW50ZW50aW9uIHdhcyBub3QgdG8gYnJlYWsgYmFja3dhcmRzIGNvbXBhdGli
aWxpdHkuDQoNCkFub3RoZXIgd2F5IHdvdWxkIGJlIHRvIHNheSB0aGF0IGV2ZXJ5ICdmaW5nZXJw
cmludCcgYXR0cmlidXRlIGNhcnJpZXMgYSBmaW5nZXJwcmludCBmb3IgdGhlIFNBTUUgY2VydGlm
aWNhdGUuIEJ1dCwgdGhhdCB3b3VsZCBvZiBjb3Vyc2Ugbm90IHdvcmsgd2l0aCBleGlzdGluZyg/
KSBpbXBsZW1lbnRhdGlvbnMgdGhhdCB1c2UgJ2ZpbmdlcnByaW50JyB0byBwcm92aWRlIGZpbmdl
cnByaW50cyBhc3NvY2lhdGVkIHdpdGggZGlmZmVyZW50IGNlcnRpZmljYXRlcy4uLg0KDQpSZWdh
cmRzLA0KDQpDaHJpc3RlciANCg==


From nobody Mon May 16 03:18:35 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A1912D0FF; Mon, 16 May 2016 03:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPV7UeZ4estn; Mon, 16 May 2016 03:18:31 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D2BC12D0DD; Mon, 16 May 2016 03:18:31 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-8b-57399e743740
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id FF.E1.12926.47E99375; Mon, 16 May 2016 12:18:29 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0248.002; Mon, 16 May 2016 12:18:28 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: mmusic <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29 - WGLC comments addressed
Thread-Index: AQHRr1xJ8y6d1DVC9Ee0qEmbCimSQQ==
Date: Mon, 16 May 2016 10:18:27 +0000
Message-ID: <D35F7933.871E%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E02278C156D15E49954B303E726DAE36@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrEIsWRmVeSWpSXmKPExsUyM2K7lm7pPMtwg2MntCymn/nLaLH85QlG i+mz3rFZTF3+mMWBxePLk5dMHtPu32fzWLLkJ1MAcxSXTUpqTmZZapG+XQJXxp0XbewFK5kq 5mxJamB8ydjFyMkhIWAisXvjbRYIW0ziwr31bF2MXBxCAkcYJVo7b7FAOEsYJSa//MjUxcjB wSZgIdH9TxskLiLQySjx5clbdpBuZgE/iatz7oNNFRZIk5iyZDOYLSKQLvHzxhQWCFtP4uLB V8wgc1gEVCUObLUACfMKWEmc+N4INoYR6Ijvp9YwQYwUl7j1ZD4TxHECEkv2nGeGsEUlXj7+ xwpiiwKN3PfiPNQzShI/NlxigejVkViw+xMbhG0t8WjibKgztSWWLXzNDLFXUOLkzCcsExjF ZiFZNwtJ+ywk7bOQtM9C0r6AkXUVo2hxanFSbrqRsV5qUWZycXF+nl5easkmRmDMHdzyW3UH 4+U3jocYBTgYlXh4F2hahguxJpYVV+YeYpTgYFYS4WWaAxTiTUmsrEotyo8vKs1JLT7EKM3B oiTO6/9SMVxIID2xJDU7NbUgtQgmy8TBKdXAGP1QbZLUg/m/LXNe77z77sDm5wKlbtlfP1es PORso3gk8Y25T27oi1sfpe/P8P57zqqf74B2N+NNsZ9m/y/M1nBfIrGyhftR20VnP2fxco7u Xw/Yvie7V5atnzLDWcKLpY2tt5bLO8OpoDww7MApWXOlsAKlmu7kbTENHsmxDgHN9jdP7v2p xFKckWioxVxUnAgAMA62tLUCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/EIBfObsXKsLx6S_Urq145fG7o6Y>
Cc: Colin Perkins <csp@csperkins.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29 - WGLC comments addressed
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 10:18:33 -0000

Hi,

You can find a version with the WGLC comments addressed in GitHub:

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


Colin/Alissa, please take a look to see whether your comments have been
properly addressed.

I have not yet submitted the new version to IETF.

Regards,

Christer


From nobody Mon May 16 04:27:19 2016
Return-Path: <csp@csperkins.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06B6912D157; Mon, 16 May 2016 04:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.865
X-Spam-Level: 
X-Spam-Status: No, score=-0.865 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SBL_CSS=3.335] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXVlQ37y0jwZ; Mon, 16 May 2016 04:27:16 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [46.235.227.24]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE57812D154; Mon, 16 May 2016 04:27:16 -0700 (PDT)
Received: from [91.118.110.181] (port=21504 helo=[10.5.29.14]) by balrog.mythic-beasts.com with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <csp@csperkins.org>) id 1b2Gg6-0005lC-Dh; Mon, 16 May 2016 12:27:14 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <D35F7933.871E%christer.holmberg@ericsson.com>
Date: Mon, 16 May 2016 13:27:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <89B2DBB9-316C-4F69-ACAD-6E87D677E99B@csperkins.org>
References: <D35F7933.871E%christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/6dMLqQ83YoPXEeZyl-7j331gsiw>
Cc: mmusic <mmusic@ietf.org>, "draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org" <draft-ietf-mmusic-sdp-bundle-negotiation@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-sdp-bundle-negotiation-29 - WGLC comments addressed
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 11:27:18 -0000

> On 16 May 2016, at 12:18, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> You can find a version with the WGLC comments addressed in GitHub:
>=20
> https://github.com/cdh4u/draft-sdp-bundle
>=20
>=20
> Colin/Alissa, please take a look to see whether your comments have =
been
> properly addressed.

Looks good to me.


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





From nobody Mon May 16 09:48:10 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89C312D73F for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 09:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HI57wZgUIpiL for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 09:48:07 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E414012D747 for <mmusic@ietf.org>; Mon, 16 May 2016 09:48:06 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-7a-5739f9c44d60
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 1F.82.18043.4C9F9375; Mon, 16 May 2016 18:48:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0248.002; Mon, 16 May 2016 18:48:04 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIP+rhurA
Date: Mon, 16 May 2016 16:48:04 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7je6Rn5bhBi1fzCyunfnHaDF1+WMW ixUbDrA6MHv8ff+ByWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgypi0YCJzwR/uik+Nb5ga GH9xdjFyckgImEi8ebSBDcIWk7hwbz2QzcUhJHCEUWLehlvMEM4SRolTt04wdjFycLAJWEh0 /9MGiYsIdDJK7Nz0mRUkziygLnF1cRDIIGEBT4nrpz+DDRUR8JK4MHUBO0T9M0aJg6tngCVY BFQl3nZuYQbp5RXwldi1MQdi13ZOiXmN18BqOAX8JCZ29LGC2IxA130/tYYJxGYWEJe49WQ+ E8TVAhJL9pxnhrBFJV4+/scKYStJrNh+iRGiXkdiwe5PbBC2tsSyha/B6nkFBCVOznzCMoFR bBaSsbOQtMxC0jILScsCRpZVjKLFqcXFuelGRnqpRZnJxcX5eXp5qSWbGIFRdXDLb6sdjAef Ox5iFOBgVOLhXaBpGS7EmlhWXJl7iFGCg1lJhHf2D6AQb0piZVVqUX58UWlOavEhRmkOFiVx Xv+XiuFCAumJJanZqakFqUUwWSYOTqkGxsTdEUmJQvmWJ1aGNneU2G17uuGc0GSVtBN9fZIm MTEtp/R4FL+tmj1ptvrJxlr7qXXCF/NuFJq7BSvPfrKr/9zuJVJBE4W2/ZWdOmuXm+MS9jMV H7fFPTlwy6Lwq1O60LlFZz395lVvPreo3ab3XtdTlzemN9bunXXyyoaZzpfXKhj0bFxhZaTE UpyRaKjFXFScCABRv+jmpgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Srj2PZxZonEXTjbDVtECcMZbddY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 16:48:08 -0000

Hi,

I put a new version on GitHub:

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

The main difference is that it now updates 4572 by saying that multiple fin=
gerprint attributes are associated with the SAME certificate, and in order =
to provide fingerprints for multiple certificates the new attribute is need=
ed. I think that should solve Martin's backwards compatibility issue.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: 15 May 2016 22:27
To: Martin Thomson <martin.thomson@gmail.com>; Paul Kyzivat <pkyzivat@alum.=
mit.edu>
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01

Hi,

>> The failure of *any* checked fingerprint to match must cause the=20
>> connection to fail.
>
> OK, yes, unless you find another line that matches on every hash, sure.
>
> I agree with the rest, though a=3Dfpl doesn't really address the backward=
s compatibility concerns that well.

My intention was not to break backwards compatibility.

Another way would be to say that every 'fingerprint' attribute carries a fi=
ngerprint for the SAME certificate. But, that would of course not work with=
 existing(?) implementations that use 'fingerprint' to provide fingerprints=
 associated with different certificates...

Regards,

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


From nobody Mon May 16 09:59:31 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67A0B12D7A0 for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 09:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JSFK0IYuXY6E for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 09:59:27 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E5C412D79D for <mmusic@ietf.org>; Mon, 16 May 2016 09:59:26 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id 190so217448778iow.1 for <mmusic@ietf.org>; Mon, 16 May 2016 09:59:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=VCuvinPtNLX8u7qYFQppJ3a8GtQCpNKqdof+/s/BvLM=; b=VUyGvoYYpwgxqTHznRJPztrElJHUBGGIpLof5SeqbvCe3cBF0BmP9uWhiR6Im+BEbM Ulkg4Ui+uD5JsiUu9p1wcgYSsPglHGRV00U6hVU4cEA0KUGOTlSq0rIcyo/3FgGo4rbh 5X6X4aT/5RDWajOYiJx8tuflUnTKP6StLZKq/1iuhDX04JK0ChPRexDcLk67fKIW2BvY Mn3PpvQduGXlsnchIOYJGVXsjJ2B/ca/cQkkIbcaAcV73yy7LfEPFE/YkLU/vV2VZSUL MNucsQLzEa/+lU9Go5v9HqD/8uNLzbauGwxOjFXJbEWZa4f0nkHGVmPV+ejpiBUgIXtQ KsTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=VCuvinPtNLX8u7qYFQppJ3a8GtQCpNKqdof+/s/BvLM=; b=KntHx9DV8F6/tVLCdP9fU6WPaFOU41VgBGSbn/lopDG+mGCRRBENb0ro33dlT6B3ZY TqbCpCg/tS6vCEeV42RIZCW4aoOueMHchjOymiwIWDeb6v1mkm5pzPGd6KAwTRblYpGh uJsjBGzwT3S7G/xQPMtFqG5p5Ol5FWzRQh1zuiM2+en6H8HH6TT2e6AG1O7v/QbuA38A DFxP6H4kvS7S0aNbcmZaiwWOPE732JFJqyJ2j8fBYNBxK9BMkRheoqh2kRUYZo1U+vaZ k2s60A0JW8hRvc48CnnGAi2jqQRLKP3RNA5+U7FfGid1nxeamG6LuGvuNqemFzrjE10D Qe5Q==
X-Gm-Message-State: AOPr4FV3RYZRoBFCf/wMfLSDGvWwZCVeNoDmBXQgC7r7lwufSsMJU+H0qdP8t0nxwGSUhQ==
X-Received: by 10.107.59.70 with SMTP id i67mr9823376ioa.33.1463417965712; Mon, 16 May 2016 09:59:25 -0700 (PDT)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id n19sm5718178itg.7.2016.05.16.09.59.24 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 09:59:24 -0700 (PDT)
Received: by mail-io0-f172.google.com with SMTP id i75so212071140ioa.3 for <mmusic@ietf.org>; Mon, 16 May 2016 09:59:24 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.156.131 with SMTP id b125mr5070054ite.95.1463417964601; Mon, 16 May 2016 09:59:24 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 16 May 2016 09:59:24 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se>
Date: Mon, 16 May 2016 12:59:24 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com>
Message-ID: <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c089e7cf02a610532f88bbc
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/7Mu3atIlDlhPZD9dHOjjwMF_nZk>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 16:59:29 -0000

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

Hi,

First of all, I would prefer for hash function values to be encoded using
base64 instead of hex.

Second, it would be better that the separator between the name-value pairs
would be semicolon instead of comma. This keeps it within the normal
name-value pair parser for URL parameters.

Finally, I still have a major problem with Martin's proposal. This is a
change comparatively to every current implementation of fingerprint
matching which I have seen. Furthermore, this is a potentially breaking
change with no indication to the remote party that a different matching
algorithm is used. I would strongly prefer that any updates to anything SDP
fingerprint related would be a clarification of how multiple fingerprints
are handled when received by the end point. This is a clarification of RFC
4572, not a new authentication framework. It should not impose any new
restrictions on fingerprint generation for RFC 4572, such as that only
single certificate is used with connection or that same sets of hash
functions must be used for each certificate, since this will not be
backwards compatible with RFC 4572, which had no such restrictions.

Regards,

_____________
Roman Shpount

On Mon, May 16, 2016 at 12:48 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> I put a new version on GitHub:
>
> https://github.com/cdh4u/draft-4572-update
>
> The main difference is that it now updates 4572 by saying that multiple
> fingerprint attributes are associated with the SAME certificate, and in
> order to provide fingerprints for multiple certificates the new attribute
> is needed. I think that should solve Martin's backwards compatibility issue.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer
> Holmberg
> Sent: 15 May 2016 22:27
> To: Martin Thomson <martin.thomson@gmail.com>; Paul Kyzivat <
> pkyzivat@alum.mit.edu>
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
>
> Hi,
>
> >> The failure of *any* checked fingerprint to match must cause the
> >> connection to fail.
> >
> > OK, yes, unless you find another line that matches on every hash, sure.
> >
> > I agree with the rest, though a=fpl doesn't really address the backwards
> compatibility concerns that well.
>
> My intention was not to break backwards compatibility.
>
> Another way would be to say that every 'fingerprint' attribute carries a
> fingerprint for the SAME certificate. But, that would of course not work
> with existing(?) implementations that use 'fingerprint' to provide
> fingerprints associated with different certificates...
>
> 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
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>First of all, I would prefer for ha=
sh function values to be encoded using base64 instead of hex.</div><div><br=
></div><div>Second, it would be better that the separator between the name-=
value pairs would be semicolon instead of comma. This keeps it within the n=
ormal name-value pair parser for URL parameters.</div><div><br></div><div>F=
inally, I still have a major problem with Martin&#39;s proposal. This is a =
change comparatively to every current implementation of fingerprint matchin=
g which I have seen. Furthermore, this is a potentially breaking change wit=
h no indication to the remote party that a different matching algorithm is =
used. I would strongly prefer that any updates to anything SDP fingerprint =
related would be a clarification of how multiple fingerprints are handled w=
hen received by the end point. This is a clarification of RFC 4572, not a n=
ew authentication framework. It should not impose any new restrictions on f=
ingerprint generation for RFC 4572, such as that only single certificate is=
 used with connection or that same sets of hash functions must be used for =
each certificate, since this will not be backwards compatible with RFC 4572=
, which had no such restrictions.</div><div><br></div><div>Regards,</div></=
div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_s=
ignature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Mon, May 16, 2016 at 12:48 PM, Christer H=
olmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.=
com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I put a new version on GitHub:<br>
<br>
<a href=3D"https://github.com/cdh4u/draft-4572-update" rel=3D"noreferrer" t=
arget=3D"_blank">https://github.com/cdh4u/draft-4572-update</a><br>
<br>
The main difference is that it now updates 4572 by saying that multiple fin=
gerprint attributes are associated with the SAME certificate, and in order =
to provide fingerprints for multiple certificates the new attribute is need=
ed. I think that should solve Martin&#39;s backwards compatibility issue.<b=
r>
<br>
Regards,<br>
<br>
Christer<br>
<span class=3D"im HOEnZb"><br>
-----Original Message-----<br>
From: mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-boun=
ces@ietf.org</a>] On Behalf Of Christer Holmberg<br>
</span><span class=3D"im HOEnZb">Sent: 15 May 2016 22:27<br>
To: Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.t=
homson@gmail.com</a>&gt;; Paul Kyzivat &lt;<a href=3D"mailto:pkyzivat@alum.=
mit.edu">pkyzivat@alum.mit.edu</a>&gt;<br>
Cc: <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01<b=
r>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">Hi,<br>
<br>
&gt;&gt; The failure of *any* checked fingerprint to match must cause the<b=
r>
&gt;&gt; connection to fail.<br>
&gt;<br>
&gt; OK, yes, unless you find another line that matches on every hash, sure=
.<br>
&gt;<br>
&gt; I agree with the rest, though a=3Dfpl doesn&#39;t really address the b=
ackwards compatibility concerns that well.<br>
<br>
My intention was not to break backwards compatibility.<br>
<br>
Another way would be to say that every &#39;fingerprint&#39; attribute carr=
ies a fingerprint for the SAME certificate. But, that would of course not w=
ork with existing(?) implementations that use &#39;fingerprint&#39; to prov=
ide fingerprints associated with different certificates...<br>
<br>
Regards,<br>
<br>
Christer<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">_______________________=
________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div>

--94eb2c089e7cf02a610532f88bbc--


From nobody Mon May 16 10:34:49 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 596EE12D783 for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 10:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FMX4mo7VsciY for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 10:34:46 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B042112D186 for <mmusic@ietf.org>; Mon, 16 May 2016 10:34:45 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-2a-573a04b365ce
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 21.38.18043.3B40A375; Mon, 16 May 2016 19:34:43 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0248.002; Mon, 16 May 2016 19:34:24 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIP+rhurA/1crnwD+ri1OoA==
Date: Mon, 16 May 2016 17:34:24 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCB29F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com>
In-Reply-To: <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FCB29FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIIsWRmVeSWpSXmKPExsUyM2J7oO5mFqtwg9Z7ahbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsErozVHZPY Cu41MlZ03elga2BcUNfFyMEhIWAisbgxoYuRE8gUk7hwbz0biC0kcIRR4sDXagh7CaNE27lI kHI2AQuJ7n/aIGERAVWJv98nM4HYzAJVEk86NjCD2MICnhLXT39mg6jxkrgwdQF7FyMXkP2N UeJdawMLyBwWoOb7E1VBangFfCVun94OViMkcIhLYtvpr2BDOQUCJdbs6GcBsRmBbvt+ag3U MnGJW0/mM0HcLCCxZM95ZghbVOLl43+sELaSxIrtlxgh6vMlXv/+wASxTFDi5MwnLBMYRWch GTULSdksJGWzgE5lFtCUWL9LH6JEUWJK90N2CFtDonXOXHZk8QWM7KsYRYtTi4tz042M9FKL MpOLi/Pz9PJSSzYxAiPy4JbfVjsYDz53PMQowMGoxMO7QNMyXIg1say4MvcQowQHs5IIr/9f oBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFe/5eK4UIC6YklqdmpqQWpRTBZJg5OqQZG3V/prPVH SruiGJc7mKYHegQmaF49vMbz0kcOCwOjEz8m3rodsnHJN4kHu4Wn7D/cKN69XGnftTPTqv// 4Xo6b0nKunUMM30s1Hff3t8R9dEmtdx/zsGSMyeDz098dWum4YmGP3wH2TZu+S3+WPQbB8Ny s2MLPv9R2OBS+qt57ZzPxQ2h7LM3nldiKc5INNRiLipOBABLZGu+xAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/JgnxCp8Lc-Ek_PTOoHqxK7Opi1M>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 17:34:48 -0000

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

SGksDQoNCj5GaXJzdCBvZiBhbGwsIEkgd291bGQgcHJlZmVyIGZvciBoYXNoIGZ1bmN0aW9uIHZh
bHVlcyB0byBiZSBlbmNvZGVkIHVzaW5nIGJhc2U2NCBpbnN0ZWFkIG9mIGhleC4NCj4NCj5TZWNv
bmQsIGl0IHdvdWxkIGJlIGJldHRlciB0aGF0IHRoZSBzZXBhcmF0b3IgYmV0d2VlbiB0aGUgbmFt
ZS12YWx1ZSBwYWlycyB3b3VsZCBiZSBzZW1pY29sb24gaW5zdGVhZCBvZiBjb21tYS4gVGhpcyBr
ZWVwcyBpdCB3aXRoaW4gdGhlIG5vcm1hbCBuYW1lLXZhbHVlIHBhaXIgcGFyc2VyIGZvciBVUkwg
PnBhcmFtZXRlcnMuDQoNClN1cmUsIGJ1dCB0aGVuIHlvdSBuZWVkIGFub3RoZXIgc2VwYXJhdG9y
IGJldHdlZW4gdGhlIGhhc2ggZnVuY3Rpb24gbmFtZS12YWx1ZSBwYWlycyBhbmQgdGhlIGV4dGVu
c2lvbnMuDQoNCkFueXdheSwgSSBkb27igJl0IHRoaW5rIHdlIG5lZWQgdG8gZm9jdXMgb24gdGhh
dCBhdCB0aGlzIHBvaW50LiBXZSBuZWVkIHRvIGZpbmQgYSB3YXkgdG8gbW92ZSBmb3J3YXJkIHdp
dGggdGhpcyB3aG9sZSBpc3N1ZS4NCg0KPkZpbmFsbHksIEkgc3RpbGwgaGF2ZSBhIG1ham9yIHBy
b2JsZW0gd2l0aCBNYXJ0aW4ncyBwcm9wb3NhbC4gVGhpcyBpcyBhIGNoYW5nZSBjb21wYXJhdGl2
ZWx5IHRvIGV2ZXJ5IGN1cnJlbnQgaW1wbGVtZW50YXRpb24gb2YgZmluZ2VycHJpbnQgbWF0Y2hp
bmcgd2hpY2ggSSBoYXZlIHNlZW4uIEZ1cnRoZXJtb3JlLCB0aGlzIGlzID5hIHBvdGVudGlhbGx5
IGJyZWFraW5nIGNoYW5nZSB3aXRoIG5vIGluZGljYXRpb24gdG8gdGhlIHJlbW90ZSBwYXJ0eSB0
aGF0IGEgZGlmZmVyZW50IG1hdGNoaW5nIGFsZ29yaXRobSBpcyB1c2VkLiBJIHdvdWxkIHN0cm9u
Z2x5IHByZWZlciB0aGF0IGFueSB1cGRhdGVzIHRvIGFueXRoaW5nIFNEUCBmaW5nZXJwcmludCBy
ZWxhdGVkID53b3VsZCBiZSBhIGNsYXJpZmljYXRpb24gb2YgaG93IG11bHRpcGxlIGZpbmdlcnBy
aW50cyBhcmUgaGFuZGxlZCB3aGVuIHJlY2VpdmVkIGJ5IHRoZSBlbmQgcG9pbnQuIFRoaXMgaXMg
YSBjbGFyaWZpY2F0aW9uIG9mIFJGQyA0NTcyLCBub3QgYSBuZXcgYXV0aGVudGljYXRpb24gZnJh
bWV3b3JrLiBJdCBzaG91bGQgbm90ID5pbXBvc2UgYW55IG5ldyByZXN0cmljdGlvbnMgb24gZmlu
Z2VycHJpbnQgZ2VuZXJhdGlvbiBmb3IgUkZDIDQ1NzIsIHN1Y2ggYXMgdGhhdCBvbmx5IHNpbmds
ZSBjZXJ0aWZpY2F0ZSBpcyB1c2VkIHdpdGggY29ubmVjdGlvbiBvciB0aGF0IHNhbWUgc2V0cyBv
ZiBoYXNoIGZ1bmN0aW9ucyBtdXN0IGJlIHVzZWQgZm9yIGVhY2ggPmNlcnRpZmljYXRlLCBzaW5j
ZSB0aGlzIHdpbGwgbm90IGJlIGJhY2t3YXJkcyBjb21wYXRpYmxlIHdpdGggUkZDIDQ1NzIsIHdo
aWNoIGhhZCBubyBzdWNoIHJlc3RyaWN0aW9ucy4NCg0KVG8gYmUgZmFpciwgdGhlcmUgaXMgbm90
IGEgc2luZ2xlIHdvcmQgYWJvdXQgbXVsdGlwbGUgZmluZ2VycHJpbnRzIGluIDQ1NzIgOikNCg0K
UmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KDQoNCg0KT24gTW9uLCBNYXkgMTYsIDIwMTYgYXQgMTI6
NDggUE0sIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208
bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KSGksDQoNCkkg
cHV0IGEgbmV3IHZlcnNpb24gb24gR2l0SHViOg0KDQpodHRwczovL2dpdGh1Yi5jb20vY2RoNHUv
ZHJhZnQtNDU3Mi11cGRhdGUNCg0KVGhlIG1haW4gZGlmZmVyZW5jZSBpcyB0aGF0IGl0IG5vdyB1
cGRhdGVzIDQ1NzIgYnkgc2F5aW5nIHRoYXQgbXVsdGlwbGUgZmluZ2VycHJpbnQgYXR0cmlidXRl
cyBhcmUgYXNzb2NpYXRlZCB3aXRoIHRoZSBTQU1FIGNlcnRpZmljYXRlLCBhbmQgaW4gb3JkZXIg
dG8gcHJvdmlkZSBmaW5nZXJwcmludHMgZm9yIG11bHRpcGxlIGNlcnRpZmljYXRlcyB0aGUgbmV3
IGF0dHJpYnV0ZSBpcyBuZWVkZWQuIEkgdGhpbmsgdGhhdCBzaG91bGQgc29sdmUgTWFydGluJ3Mg
YmFja3dhcmRzIGNvbXBhdGliaWxpdHkgaXNzdWUuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBtbXVzaWMgW21haWx0bzptbXVzaWMt
Ym91bmNlc0BpZXRmLm9yZzxtYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc+XSBPbiBCZWhh
bGYgT2YgQ2hyaXN0ZXIgSG9sbWJlcmcNClNlbnQ6IDE1IE1heSAyMDE2IDIyOjI3DQpUbzogTWFy
dGluIFRob21zb24gPG1hcnRpbi50aG9tc29uQGdtYWlsLmNvbTxtYWlsdG86bWFydGluLnRob21z
b25AZ21haWwuY29tPj47IFBhdWwgS3l6aXZhdCA8cGt5eml2YXRAYWx1bS5taXQuZWR1PG1haWx0
bzpwa3l6aXZhdEBhbHVtLm1pdC5lZHU+Pg0KQ2M6IG1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11
c2ljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFtNTVVTSUNdIERyYWZ0IG5ldyB2ZXJzaW9uOiBk
cmFmdC1pZXRmLW1tdXNpYy00NTcyLXVwZGF0ZS0wMQ0KSGksDQoNCj4+IFRoZSBmYWlsdXJlIG9m
ICphbnkqIGNoZWNrZWQgZmluZ2VycHJpbnQgdG8gbWF0Y2ggbXVzdCBjYXVzZSB0aGUNCj4+IGNv
bm5lY3Rpb24gdG8gZmFpbC4NCj4NCj4gT0ssIHllcywgdW5sZXNzIHlvdSBmaW5kIGFub3RoZXIg
bGluZSB0aGF0IG1hdGNoZXMgb24gZXZlcnkgaGFzaCwgc3VyZS4NCj4NCj4gSSBhZ3JlZSB3aXRo
IHRoZSByZXN0LCB0aG91Z2ggYT1mcGwgZG9lc24ndCByZWFsbHkgYWRkcmVzcyB0aGUgYmFja3dh
cmRzIGNvbXBhdGliaWxpdHkgY29uY2VybnMgdGhhdCB3ZWxsLg0KDQpNeSBpbnRlbnRpb24gd2Fz
IG5vdCB0byBicmVhayBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eS4NCg0KQW5vdGhlciB3YXkgd291
bGQgYmUgdG8gc2F5IHRoYXQgZXZlcnkgJ2ZpbmdlcnByaW50JyBhdHRyaWJ1dGUgY2FycmllcyBh
IGZpbmdlcnByaW50IGZvciB0aGUgU0FNRSBjZXJ0aWZpY2F0ZS4gQnV0LCB0aGF0IHdvdWxkIG9m
IGNvdXJzZSBub3Qgd29yayB3aXRoIGV4aXN0aW5nKD8pIGltcGxlbWVudGF0aW9ucyB0aGF0IHVz
ZSAnZmluZ2VycHJpbnQnIHRvIHByb3ZpZGUgZmluZ2VycHJpbnRzIGFzc29jaWF0ZWQgd2l0aCBk
aWZmZXJlbnQgY2VydGlmaWNhdGVzLi4uDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQpfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbW11c2ljIG1haWxpbmcg
bGlzdA0KbW11c2ljQGlldGYub3JnPG1haWx0bzptbXVzaWNAaWV0Zi5vcmc+DQpodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KDQpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbW11c2ljIG1haWxpbmcgbGlzdA0KbW11c2lj
QGlldGYub3JnPG1haWx0bzptbXVzaWNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLmltDQoJe21zby1zdHls
ZS1uYW1lOmltO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0K
c3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5N
c29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBw
YWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0
IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVm
YXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48
IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxv
OmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwh
W2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUiIHZsaW5r
PSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LVVTIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+Jmd0O0ZpcnN0IG9mIGFsbCwgSSB3b3VsZCBwcmVmZXIgZm9yIGhhc2ggZnVu
Y3Rpb24gdmFsdWVzIHRvIGJlIGVuY29kZWQgdXNpbmcgYmFzZTY0IGluc3RlYWQgb2YgaGV4Ljxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0Ozxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Jmd0O1NlY29uZCwgaXQgd291bGQgYmUgYmV0dGVyIHRoYXQgdGhlIHNlcGFyYXRvciBiZXR3ZWVu
IHRoZSBuYW1lLXZhbHVlIHBhaXJzIHdvdWxkIGJlIHNlbWljb2xvbiBpbnN0ZWFkIG9mIGNvbW1h
LiBUaGlzIGtlZXBzIGl0IHdpdGhpbiB0aGUgbm9ybWFsIG5hbWUtdmFsdWUgcGFpciBwYXJzZXIg
Zm9yIFVSTCAmZ3Q7cGFyYW1ldGVycy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj5TdXJlLCBidXQgdGhlbiB5b3UgbmVlZCBhbm90aGVyIHNl
cGFyYXRvciBiZXR3ZWVuIHRoZSBoYXNoIGZ1bmN0aW9uIG5hbWUtdmFsdWUgcGFpcnMgYW5kIHRo
ZSBleHRlbnNpb25zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Bbnl3YXksIEkgZG9u4oCZdCB0aGluayB3ZSBu
ZWVkIHRvIGZvY3VzIG9uIHRoYXQgYXQgdGhpcyBwb2ludC4gV2UgbmVlZCB0byBmaW5kIGEgd2F5
IHRvIG1vdmUgZm9yd2FyZCB3aXRoIHRoaXMgd2hvbGUgaXNzdWUuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7
RmluYWxseSwgSSBzdGlsbCBoYXZlIGEgbWFqb3IgcHJvYmxlbSB3aXRoIE1hcnRpbidzIHByb3Bv
c2FsLiBUaGlzIGlzIGEgY2hhbmdlIGNvbXBhcmF0aXZlbHkgdG8gZXZlcnkgY3VycmVudCBpbXBs
ZW1lbnRhdGlvbiBvZiBmaW5nZXJwcmludCBtYXRjaGluZyB3aGljaCBJIGhhdmUgc2Vlbi4gRnVy
dGhlcm1vcmUsIHRoaXMgaXMgJmd0O2EgcG90ZW50aWFsbHkgYnJlYWtpbmcgY2hhbmdlIHdpdGgg
bm8gaW5kaWNhdGlvbg0KIHRvIHRoZSByZW1vdGUgcGFydHkgdGhhdCBhIGRpZmZlcmVudCBtYXRj
aGluZyBhbGdvcml0aG0gaXMgdXNlZC4gSSB3b3VsZCBzdHJvbmdseSBwcmVmZXIgdGhhdCBhbnkg
dXBkYXRlcyB0byBhbnl0aGluZyBTRFAgZmluZ2VycHJpbnQgcmVsYXRlZCAmZ3Q7d291bGQgYmUg
YSBjbGFyaWZpY2F0aW9uIG9mIGhvdyBtdWx0aXBsZSBmaW5nZXJwcmludHMgYXJlIGhhbmRsZWQg
d2hlbiByZWNlaXZlZCBieSB0aGUgZW5kIHBvaW50LiBUaGlzIGlzIGEgY2xhcmlmaWNhdGlvbg0K
IG9mIFJGQyA0NTcyLCBub3QgYSBuZXcgYXV0aGVudGljYXRpb24gZnJhbWV3b3JrLiBJdCBzaG91
bGQgbm90ICZndDtpbXBvc2UgYW55IG5ldyByZXN0cmljdGlvbnMgb24gZmluZ2VycHJpbnQgZ2Vu
ZXJhdGlvbiBmb3IgUkZDIDQ1NzIsIHN1Y2ggYXMgdGhhdCBvbmx5IHNpbmdsZSBjZXJ0aWZpY2F0
ZSBpcyB1c2VkIHdpdGggY29ubmVjdGlvbiBvciB0aGF0IHNhbWUgc2V0cyBvZiBoYXNoIGZ1bmN0
aW9ucyBtdXN0IGJlIHVzZWQgZm9yIGVhY2ggJmd0O2NlcnRpZmljYXRlLA0KIHNpbmNlIHRoaXMg
d2lsbCBub3QgYmUgYmFja3dhcmRzIGNvbXBhdGlibGUgd2l0aCBSRkMgNDU3Miwgd2hpY2ggaGFk
IG5vIHN1Y2ggcmVzdHJpY3Rpb25zLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPlRvIGJlIGZhaXIsIHRoZXJlIGlzIG5vdCBhIHNpbmdsZSB3
b3JkIGFib3V0IG11bHRpcGxlIGZpbmdlcnByaW50cyBpbiA0NTcyIDopPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYi
PlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkNocmlzdGVyPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5PbiBNb24sIE1heSAxNiwgMjAxNiBhdCAxMjo0OCBQTSwgQ2hyaXN0ZXIg
SG9sbWJlcmcgJmx0OzxhIGhyZWY9Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5j
b20iIHRhcmdldD0iX2JsYW5rIj5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208L2E+Jmd0
OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7
bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkhpLDxicj4NCjxicj4NCkkgcHV0IGEgbmV3
IHZlcnNpb24gb24gR2l0SHViOjxicj4NCjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNv
bS9jZGg0dS9kcmFmdC00NTcyLXVwZGF0ZSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vZ2l0aHVi
LmNvbS9jZGg0dS9kcmFmdC00NTcyLXVwZGF0ZTwvYT48YnI+DQo8YnI+DQpUaGUgbWFpbiBkaWZm
ZXJlbmNlIGlzIHRoYXQgaXQgbm93IHVwZGF0ZXMgNDU3MiBieSBzYXlpbmcgdGhhdCBtdWx0aXBs
ZSBmaW5nZXJwcmludCBhdHRyaWJ1dGVzIGFyZSBhc3NvY2lhdGVkIHdpdGggdGhlIFNBTUUgY2Vy
dGlmaWNhdGUsIGFuZCBpbiBvcmRlciB0byBwcm92aWRlIGZpbmdlcnByaW50cyBmb3IgbXVsdGlw
bGUgY2VydGlmaWNhdGVzIHRoZSBuZXcgYXR0cmlidXRlIGlzIG5lZWRlZC4gSSB0aGluayB0aGF0
IHNob3VsZCBzb2x2ZSBNYXJ0aW4ncw0KIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5IGlzc3VlLjxi
cj4NCjxicj4NClJlZ2FyZHMsPGJyPg0KPGJyPg0KQ2hyaXN0ZXI8YnI+DQo8YnI+DQo8c3BhbiBj
bGFzcz0iaW0iPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPC9zcGFuPjxicj4NCjxzcGFuIGNs
YXNzPSJpbSI+RnJvbTogbW11c2ljIFttYWlsdG86PGEgaHJlZj0ibWFpbHRvOm1tdXNpYy1ib3Vu
Y2VzQGlldGYub3JnIj5tbXVzaWMtYm91bmNlc0BpZXRmLm9yZzwvYT5dIE9uIEJlaGFsZiBPZiBD
aHJpc3RlciBIb2xtYmVyZzwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iaW0iPlNlbnQ6IDE1IE1h
eSAyMDE2IDIyOjI3PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJpbSI+VG86IE1hcnRpbiBUaG9t
c29uICZsdDs8YSBocmVmPSJtYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tIj5tYXJ0aW4u
dGhvbXNvbkBnbWFpbC5jb208L2E+Jmd0OzsgUGF1bCBLeXppdmF0ICZsdDs8YSBocmVmPSJtYWls
dG86cGt5eml2YXRAYWx1bS5taXQuZWR1Ij5wa3l6aXZhdEBhbHVtLm1pdC5lZHU8L2E+Jmd0Ozwv
c3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iaW0iPkNjOiA8YSBocmVmPSJtYWlsdG86bW11c2ljQGll
dGYub3JnIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJpbSI+
U3ViamVjdDogUmU6IFtNTVVTSUNdIERyYWZ0IG5ldyB2ZXJzaW9uOiBkcmFmdC1pZXRmLW1tdXNp
Yy00NTcyLXVwZGF0ZS0wMTwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+SGksPGJyPg0KPGJyPg0KJmd0OyZndDsgVGhlIGZhaWx1cmUgb2Yg
KmFueSogY2hlY2tlZCBmaW5nZXJwcmludCB0byBtYXRjaCBtdXN0IGNhdXNlIHRoZTxicj4NCiZn
dDsmZ3Q7IGNvbm5lY3Rpb24gdG8gZmFpbC48YnI+DQomZ3Q7PGJyPg0KJmd0OyBPSywgeWVzLCB1
bmxlc3MgeW91IGZpbmQgYW5vdGhlciBsaW5lIHRoYXQgbWF0Y2hlcyBvbiBldmVyeSBoYXNoLCBz
dXJlLjxicj4NCiZndDs8YnI+DQomZ3Q7IEkgYWdyZWUgd2l0aCB0aGUgcmVzdCwgdGhvdWdoIGE9
ZnBsIGRvZXNuJ3QgcmVhbGx5IGFkZHJlc3MgdGhlIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5IGNv
bmNlcm5zIHRoYXQgd2VsbC48YnI+DQo8YnI+DQpNeSBpbnRlbnRpb24gd2FzIG5vdCB0byBicmVh
ayBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eS48YnI+DQo8YnI+DQpBbm90aGVyIHdheSB3b3VsZCBi
ZSB0byBzYXkgdGhhdCBldmVyeSAnZmluZ2VycHJpbnQnIGF0dHJpYnV0ZSBjYXJyaWVzIGEgZmlu
Z2VycHJpbnQgZm9yIHRoZSBTQU1FIGNlcnRpZmljYXRlLiBCdXQsIHRoYXQgd291bGQgb2YgY291
cnNlIG5vdCB3b3JrIHdpdGggZXhpc3RpbmcoPykgaW1wbGVtZW50YXRpb25zIHRoYXQgdXNlICdm
aW5nZXJwcmludCcgdG8gcHJvdmlkZSBmaW5nZXJwcmludHMgYXNzb2NpYXRlZCB3aXRoIGRpZmZl
cmVudCBjZXJ0aWZpY2F0ZXMuLi48YnI+DQo8YnI+DQpSZWdhcmRzLDxicj4NCjxicj4NCkNocmlz
dGVyPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXzxicj4NCm1tdXNpYyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86bW11c2lj
QGlldGYub3JnIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMiIHRhcmdldD0iX2JsYW5rIj5odHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYzwvYT48YnI+DQo8YnI+DQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCm1tdXNpYyBt
YWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3JnIj5tbXVzaWNA
aWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9tbXVzaWMiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL21tdXNpYzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B37FCB29FESESSMB209erics_--


From nobody Mon May 16 10:49:07 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8AFF12D892 for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 10:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjby53WzkrWU for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 10:49:05 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B87D12D893 for <mmusic@ietf.org>; Mon, 16 May 2016 10:49:05 -0700 (PDT)
Received: by mail-ig0-x22c.google.com with SMTP id bi2so58594843igb.0 for <mmusic@ietf.org>; Mon, 16 May 2016 10:49:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=PNw1eI25R8ahawQADSlsQMt7nXnFwJZT39GC2/vOLAA=; b=XWOEGT21BUCwmLz9hR6VRCO6EKbG67rsb/islAR1lzuPEFxpGP01iFKU++FGT5tm5t 2dssxLCPUbd9Yb61GZ+YaH+fOXtBiqeZ4+kfeAMWIrzGdE0fsIFz+WFveLEr4BwWAvUk AWhZE9QpVokmwRHTSBegiu+kgIb5HuZH8trmrvalpeldxybfPmf3LS5295sOW8rVGCok 4gfx90v30vEIRhVZdCXkBOZ1iDPB9jxyHjjV3RLPMkK0gsnb0v1uWYhPP2UcsSeJTS57 FqAb6MAR2WbqkpuQ1C4F/dNb0wG6BlwuKntXxp1U0+FDW3B+z3nB3wTAXX2P4WeeSld5 X8/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=PNw1eI25R8ahawQADSlsQMt7nXnFwJZT39GC2/vOLAA=; b=aInn8fDx3meqDrN/lVqln7R7VYVikk3hqjvDYMJJ6KsnoaCqT/XUV4CunupEYeFkuk yi6MKesRmgaRdEaB6hVgyTlleL8o8b7VyTALv679qEgDetZVLkEEbhbzhD8hBDSBFGwC 5XmAp6oMsfLgVNAAyzNu3K2rHpGAmM9OFUoUQk6WIR3WZGmqXub/PT+z8Ervj3q+hxRZ aS0jpwgCPY1VDL0lUd4JNmAtBzctN5mjYowtbnduhPaxFROFmr/RzV9nn7en+18vfqdL ydJff8qeFvfuaFJp7v2izxN9jhq0+6oZAeMMvD476V56jmcvetGrKe5JR4EJM2xrO0fm 3ZEQ==
X-Gm-Message-State: AOPr4FXGef9SNx+Y8ZkC9vcFf+7CSRw7w5RnKuq1A7X+fBV3vycAcW5qKbPzhMgJ7iHtVQ==
X-Received: by 10.50.72.237 with SMTP id g13mr11914564igv.4.1463420944392; Mon, 16 May 2016 10:49:04 -0700 (PDT)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id u66sm5873115itc.21.2016.05.16.10.49.03 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 10:49:03 -0700 (PDT)
Received: by mail-io0-f172.google.com with SMTP id i75so213885762ioa.3 for <mmusic@ietf.org>; Mon, 16 May 2016 10:49:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.156.131 with SMTP id b125mr5244602ite.95.1463420943102; Mon, 16 May 2016 10:49:03 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 16 May 2016 10:49:02 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCB29F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCB29F@ESESSMB209.ericsson.se>
Date: Mon, 16 May 2016 13:49:02 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuU8VDcHt1_vBAYiLe5KG-tCSKhQ0a5V__dv-vX42XwwA@mail.gmail.com>
Message-ID: <CAD5OKxuU8VDcHt1_vBAYiLe5KG-tCSKhQ0a5V__dv-vX42XwwA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c089e7c78a0310532f93d49
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/UgYr-NsJkehsTnzPbmI4wHjMgew>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 17:49:07 -0000

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

On Mon, May 16, 2016 at 1:34 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >Finally, I still have a major problem with Martin's proposal. This is a
> change comparatively to every current implementation of fingerprint
> matching which I have seen. Furthermore, this is >a potentially breaking
> change with no indication to the remote party that a different matching
> algorithm is used. I would strongly prefer that any updates to anything SDP
> fingerprint related >would be a clarification of how multiple fingerprints
> are handled when received by the end point. This is a clarification of RFC
> 4572, not a new authentication framework. It should not >impose any new
> restrictions on fingerprint generation for RFC 4572, such as that only
> single certificate is used with connection or that same sets of hash
> functions must be used for each >certificate, since this will not be
> backwards compatible with RFC 4572, which had no such restrictions.
>
>
>
> To be fair, there is not a single word about multiple fingerprints in 4572
> :)
>
>
>
To be fair there is not a single word about how many fingerprints are
allowed in 4572. It can be interpreted either way. If anything, it can be
interpreted that it supports multiple certificates with one fingerprint per
certificate. This is why we wanted to update the document :)

In any case, there are multiple existing implementations out there which
support multiple fingerprints. None of them implement what Martin proposes.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 16, 2016 at 1:34 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal">&gt;Finally, I still have a major problem with Marti=
n&#39;s proposal. This is a change comparatively to every current implement=
ation of fingerprint matching which I have seen. Furthermore, this is &gt;a=
 potentially breaking change with no indication
 to the remote party that a different matching algorithm is used. I would s=
trongly prefer that any updates to anything SDP fingerprint related &gt;wou=
ld be a clarification of how multiple fingerprints are handled when receive=
d by the end point. This is a clarification
 of RFC 4572, not a new authentication framework. It should not &gt;impose =
any new restrictions on fingerprint generation for RFC 4572, such as that o=
nly single certificate is used with connection or that same sets of hash fu=
nctions must be used for each &gt;certificate,
 since this will not be backwards compatible with RFC 4572, which had no su=
ch restrictions.<br></p><div><span class=3D""><div><p class=3D"MsoNormal"><=
u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">To be fair, there is not a single word about multiple fingerprint=
s in 4572 :)<u></u><u></u></span></p>
<p class=3D"MsoNormal"><br></p></div></div></div></div></blockquote><div><b=
r></div><div>To be fair there is not a single word about how many fingerpri=
nts are allowed in 4572. It can be interpreted either way. If anything, it =
can be interpreted that it supports multiple certificates with one fingerpr=
int per certificate. This is why we wanted to update the document :)</div><=
div><br></div><div>In any case, there are multiple existing implementations=
 out there which support multiple fingerprints. None of them implement what=
 Martin proposes.</div><div><div class=3D"gmail_signature">_____________<br=
>Roman Shpount</div></div><div>=C2=A0</div></div></div></div>

--94eb2c089e7c78a0310532f93d49--


From nobody Mon May 16 10:55:26 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 736AB12D8A0 for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 10:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gbpIPi4OfZ9f for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 10:55:24 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEEDC12D898 for <mmusic@ietf.org>; Mon, 16 May 2016 10:55:23 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-12-573a098aa6f6
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id A2.F8.27088.A890A375; Mon, 16 May 2016 19:55:22 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Mon, 16 May 2016 19:55:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIP+rhurA/1crnwD+ri1OoP1cdq4A+rjKwQA=
Date: Mon, 16 May 2016 17:55:20 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCB3BB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCB29F@ESESSMB209.ericsson.se> <CAD5OKxuU8VDcHt1_vBAYiLe5KG-tCSKhQ0a5V__dv-vX42XwwA@mail.gmail.com>
In-Reply-To: <CAD5OKxuU8VDcHt1_vBAYiLe5KG-tCSKhQ0a5V__dv-vX42XwwA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM2K7n24Xp1W4wfmbfBbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsErozvC7Yz FiwSrFi88z9bA+MLgS5GTg4JAROJ1Se3MkHYYhIX7q1n62Lk4hASOMIocXLVTEYIZwmjxOfW I0AOBwebgIVE9z9tkAYRAVWJv98ngzUzC1RJPOnYwAxiCwt4Slw//ZkNosZL4sLUBewgc0QE mpgkJq5uYQFJsAA1H9j5FayBV8BX4t3NVewQy85yS0xfOQtsKqdAoMThnwvAGhiBzvt+ag3U NnGJW0/mQ50tILFkz3lmCFtU4uXjf6wQtpLEiu2XwI5mFtCUWL9LH6JVUWJK90N2iL2CEidn PmGZwCg2C8nUWQgds5B0zELSsYCRZRWjaHFqcVJuupGRXmpRZnJxcX6eXl5qySZGYJQd3PLb YAfjy+eOhxgFOBiVeHgXaFqGC7EmlhVX5h5ilOBgVhLhXcthFS7Em5JYWZValB9fVJqTWnyI UZqDRUmc1/+lYriQQHpiSWp2ampBahFMlomDU6qBsdu10196ecB+3/bfFoFcjBE9UZGLmNW/ nW8pinNREHPgr525VGXZ51ilr3//CjwJ9j31zeOZ8fvlL31Wfz7zOcWs9ny/Q8HtA0HvD9/v bzJx/KGn0Xtx2pNH5np67MvdeSR2t+Rx2AlLubY5rTjkcPrw5WaPL8auacsTSsr0flYdfP+n OTpCiaU4I9FQi7moOBEAgRmVM64CAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/xDq_Gah6PcoSCkMi80xODEwfm-k>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 17:55:25 -0000

SGksDQoNCj4+PiBGaW5hbGx5LCBJIHN0aWxsIGhhdmUgYSBtYWpvciBwcm9ibGVtIHdpdGggTWFy
dGluJ3MgcHJvcG9zYWwuIFRoaXMgaXMgYSBjaGFuZ2UgY29tcGFyYXRpdmVseSB0byBldmVyeSBj
dXJyZW50IGltcGxlbWVudGF0aW9uIA0KPj4+IG9mIGZpbmdlcnByaW50IG1hdGNoaW5nIHdoaWNo
IEkgaGF2ZSBzZWVuLiBGdXJ0aGVybW9yZSwgdGhpcyBpcyBhIHBvdGVudGlhbGx5IGJyZWFraW5n
IGNoYW5nZSB3aXRoIG5vIGluZGljYXRpb24gdG8gdGhlIA0KPj4+IHJlbW90ZSBwYXJ0eSB0aGF0
IGEgZGlmZmVyZW50IG1hdGNoaW5nIGFsZ29yaXRobSBpcyB1c2VkLiBJIHdvdWxkIHN0cm9uZ2x5
IHByZWZlciB0aGF0IGFueSB1cGRhdGVzIHRvIGFueXRoaW5nIFNEUCBmaW5nZXJwcmludCANCj4+
PiByZWxhdGVkIHdvdWxkIGJlIGEgY2xhcmlmaWNhdGlvbiBvZiBob3cgbXVsdGlwbGUgZmluZ2Vy
cHJpbnRzIGFyZSBoYW5kbGVkIHdoZW4gcmVjZWl2ZWQgYnkgdGhlIGVuZCBwb2ludC4gVGhpcyBp
cyBhIGNsYXJpZmljYXRpb24gDQo+Pj4gb2YgUkZDIDQ1NzIsIG5vdCBhIG5ldyBhdXRoZW50aWNh
dGlvbiBmcmFtZXdvcmsuIEl0IHNob3VsZCBub3QgaW1wb3NlIGFueSBuZXcgcmVzdHJpY3Rpb25z
IG9uIGZpbmdlcnByaW50IGdlbmVyYXRpb24NCj4+PiBmb3IgUkZDIDQ1NzIsIHN1Y2ggYXMgdGhh
dCBvbmx5IHNpbmdsZSBjZXJ0aWZpY2F0ZSBpcyB1c2VkIHdpdGggY29ubmVjdGlvbiBvciB0aGF0
IHNhbWUgc2V0cyBvZiBoYXNoIGZ1bmN0aW9ucyBtdXN0IGJlIHVzZWQgDQo+Pj4gZm9yIGVhY2gg
Y2VydGlmaWNhdGUsIHNpbmNlIHRoaXMgd2lsbCBub3QgYmUgYmFja3dhcmRzIGNvbXBhdGlibGUg
d2l0aCBSRkMgNDU3Miwgd2hpY2ggaGFkIG5vIHN1Y2ggcmVzdHJpY3Rpb25zLg0KPj4NCj4+IFRv
IGJlIGZhaXIsIHRoZXJlIGlzIG5vdCBhIHNpbmdsZSB3b3JkIGFib3V0IG11bHRpcGxlIGZpbmdl
cnByaW50cyBpbiA0NTcyIDopDQo+DQo+IFRvIGJlIGZhaXIgdGhlcmUgaXMgbm90IGEgc2luZ2xl
IHdvcmQgYWJvdXQgaG93IG1hbnkgZmluZ2VycHJpbnRzIGFyZSBhbGxvd2VkIGluIDQ1NzIuIEl0
IGNhbiBiZSBpbnRlcnByZXRlZCBlaXRoZXIgd2F5LiANCj4gSWYgYW55dGhpbmcsIGl0IGNhbiBi
ZSBpbnRlcnByZXRlZCB0aGF0IGl0IHN1cHBvcnRzIG11bHRpcGxlIGNlcnRpZmljYXRlcyB3aXRo
IG9uZSBmaW5nZXJwcmludCBwZXIgY2VydGlmaWNhdGUuIFRoaXMgaXMgd2h5IHdlIHdhbnRlZCB0
byB1cGRhdGUgdGhlIGRvY3VtZW50IDopDQo+DQo+IEluIGFueSBjYXNlLCB0aGVyZSBhcmUgbXVs
dGlwbGUgZXhpc3RpbmcgaW1wbGVtZW50YXRpb25zIG91dCB0aGVyZSB3aGljaCBzdXBwb3J0IG11
bHRpcGxlIGZpbmdlcnByaW50cy4gTm9uZSBvZiB0aGVtIGltcGxlbWVudCB3aGF0IE1hcnRpbiBw
cm9wb3Nlcy4NCg0KU28sIGluIHlvdXIgZXhwZXJpZW5jZSwgd2hlbiBleGlzdGluZyBpbXBsZW1l
bnRhdGlvbnMgcHJvdmlkZSBtdWx0aXBsZSBmaW5nZXJwcmludHMgdGhlbiBlYWNoIGZpbmdlcnBy
aW50IGlzIGFzc29jaWF0ZWQgd2l0aCBhIGRpZmZlcmVudCBjZXJ0aWZpY2F0ZT8NCg0KUmVnYXJk
cywNCg0KQ2hyaXN0ZXINCg==


From nobody Mon May 16 11:21:42 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7929C12D50C for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 11:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGES-N-uN82w for <mmusic@ietfa.amsl.com>; Mon, 16 May 2016 11:21:40 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCFFF12D50D for <mmusic@ietf.org>; Mon, 16 May 2016 11:21:39 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id d62so220383322iof.2 for <mmusic@ietf.org>; Mon, 16 May 2016 11:21:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=BXI0xL2z71s4NKdD8jno9+8Y7Eqt8sqNQlZN8IH2QxM=; b=vVdbdHGkupXr3nT2E7JeMIkdvzi5ioB/2uoDjf/qNEurGhvKLTq5q2vmrS0Z+X0f8U i57YEjQIN0MuXAEtgqh1M3kP71FrTtm/Hw8UnP7m8W9HnripYo04e366F9xZoFu5vjym 7Oxv5i7klvTMzpPCZLGGSrQjx1LGg4j4jFrmXAZslM9XrB0fVnI6VHzcrxid/Y/+faZF YhWFd1SV71K4Gp4mnm5yG3UXE78bQsAEqsRK2s/qTIsQZG5/SXNecMOquKhVo7L5Xd34 gs1CY6h3YMKD0/VIoy+Ur3ar7FkKJqR7z1EJTXmzJ5D6gumoS59PHQ9BR95gC+z8Cm1g awjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=BXI0xL2z71s4NKdD8jno9+8Y7Eqt8sqNQlZN8IH2QxM=; b=O7qkvKr7DQfueqwtLMwcl2GBPnMVnl4CX4DYM7zKmmGyq9wnWiYRnBTdFj+zsVlRsD tdHV5BuP6bxZMSKulr+sxWZ9mE8tVdWOp6an/mW64w7xSHv6lHFqEvv0/TXO9C9PascQ WJPfBG/LnK/HZ+8C7M5pRW4Fls+5m4g8RdjaK0FRC3LFWyXn/zMIWwOtZ8oWRSc3HTsp 8WAkP7F/5oYH4Zehed029T8LlI0xkTDZWhooYpmiiMxL/N4d5E/QvrgU1WNKxiezagjW qWsR4Q8CKFYrbDWIYoZysJrowZIWOIqbiqL6L12ijJruvM0+SziO7drxI6vJxiao1Ud/ Y72w==
X-Gm-Message-State: AOPr4FXaAv109JJLLjRzZHBSouXPtLaOkLugetE3NUCbJ76MRyECN/C8z2owqFY7qQW4Fg==
X-Received: by 10.107.22.67 with SMTP id 64mr20106911iow.128.1463422899088; Mon, 16 May 2016 11:21:39 -0700 (PDT)
Received: from mail-ig0-f175.google.com (mail-ig0-f175.google.com. [209.85.213.175]) by smtp.gmail.com with ESMTPSA id 70sm11044341ioz.16.2016.05.16.11.21.38 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 11:21:38 -0700 (PDT)
Received: by mail-ig0-f175.google.com with SMTP id bi2so59187485igb.0 for <mmusic@ietf.org>; Mon, 16 May 2016 11:21:38 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.124.39 with SMTP id mf7mr11993294igb.95.1463422898041; Mon, 16 May 2016 11:21:38 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 16 May 2016 11:21:37 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCB3BB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCB29F@ESESSMB209.ericsson.se> <CAD5OKxuU8VDcHt1_vBAYiLe5KG-tCSKhQ0a5V__dv-vX42XwwA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCB3BB@ESESSMB209.ericsson.se>
Date: Mon, 16 May 2016 14:21:37 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv3Chj29g3NGn1o_OBQCuhPk76CjDjeDqrhTjy0un0hiQ@mail.gmail.com>
Message-ID: <CAD5OKxv3Chj29g3NGn1o_OBQCuhPk76CjDjeDqrhTjy0un0hiQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=089e0111bc56fe8d5d0532f9b1dc
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/jx9ZVHJj83kqClh2wZUtpP0sXzM>
Cc: Cullen Jennings <fluffy@cisco.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2016 18:21:41 -0000

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

On Mon, May 16, 2016 at 1:55 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >>> Finally, I still have a major problem with Martin's proposal. This is
> a change comparatively to every current implementation
> >>> of fingerprint matching which I have seen. Furthermore, this is a
> potentially breaking change with no indication to the
> >>> remote party that a different matching algorithm is used. I would
> strongly prefer that any updates to anything SDP fingerprint
> >>> related would be a clarification of how multiple fingerprints are
> handled when received by the end point. This is a clarification
> >>> of RFC 4572, not a new authentication framework. It should not impose
> any new restrictions on fingerprint generation
> >>> for RFC 4572, such as that only single certificate is used with
> connection or that same sets of hash functions must be used
> >>> for each certificate, since this will not be backwards compatible with
> RFC 4572, which had no such restrictions.
> >>
> >> To be fair, there is not a single word about multiple fingerprints in
> 4572 :)
> >
> > To be fair there is not a single word about how many fingerprints are
> allowed in 4572. It can be interpreted either way.
> > If anything, it can be interpreted that it supports multiple
> certificates with one fingerprint per certificate. This is why we wanted to
> update the document :)
> >
> > In any case, there are multiple existing implementations out there which
> support multiple fingerprints. None of them implement what Martin proposes.
>
> So, in your experience, when existing implementations provide multiple
> fingerprints then each fingerprint is associated with a different
> certificate?
>

Current open source implementations that I've seen provide a single
certificate, but accept the connection on any single fingerprint match.
Implementations that would provide more then one certificate would be
unusual and would typically be associated with service provider
deployments, such as conference providers. These implementations are often
not based on open source and I cannot easily examine them. This being said,
such implementations can potentially rely on current certificate match
rules in the browsers, so changing such rules can potentially break these
implementations.

Cullen was another person who advocated single fingerprint match and he has
access to one of the larger conferencing implementations. It would be
interesting to see his opinion on this topic.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Mon, May 16, 2016 at 1:55 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"><span class=3D"">&gt;&gt;&gt; Finally, I =
still have a major problem with Martin&#39;s proposal. This is a change com=
paratively to every current implementation<br>
&gt;&gt;&gt; of fingerprint matching which I have seen. Furthermore, this i=
s a potentially breaking change with no indication to the<br>
&gt;&gt;&gt; remote party that a different matching algorithm is used. I wo=
uld strongly prefer that any updates to anything SDP fingerprint<br>
&gt;&gt;&gt; related would be a clarification of how multiple fingerprints =
are handled when received by the end point. This is a clarification<br>
&gt;&gt;&gt; of RFC 4572, not a new authentication framework. It should not=
 impose any new restrictions on fingerprint generation<br>
&gt;&gt;&gt; for RFC 4572, such as that only single certificate is used wit=
h connection or that same sets of hash functions must be used<br>
&gt;&gt;&gt; for each certificate, since this will not be backwards compati=
ble with RFC 4572, which had no such restrictions.<br>
&gt;&gt;<br>
&gt;&gt; To be fair, there is not a single word about multiple fingerprints=
 in 4572 :)<br>
&gt;<br>
&gt; To be fair there is not a single word about how many fingerprints are =
allowed in 4572. It can be interpreted either way.<br>
&gt; If anything, it can be interpreted that it supports multiple certifica=
tes with one fingerprint per certificate. This is why we wanted to update t=
he document :)<br>
&gt;<br>
&gt; In any case, there are multiple existing implementations out there whi=
ch support multiple fingerprints. None of them implement what Martin propos=
es.<br>
<br>
</span>So, in your experience, when existing implementations provide multip=
le fingerprints then each fingerprint is associated with a different certif=
icate?<br></blockquote><div><br></div><div>Current open source implementati=
ons that I&#39;ve seen provide a single certificate, but accept the connect=
ion on any single fingerprint match. Implementations that would provide mor=
e then one certificate would be unusual and would typically be associated w=
ith service provider deployments, such as conference providers. These imple=
mentations are often not based on open source and I cannot easily examine t=
hem. This being said, such implementations can potentially rely on current =
certificate match rules in the browsers, so changing such rules can potenti=
ally break these implementations.</div><div><br></div><div>Cullen was anoth=
er person who advocated single fingerprint match and he has access to one o=
f the larger conferencing implementations. It would be interesting to see h=
is opinion on this topic.</div><div><div class=3D"gmail_signature">________=
_____<br>Roman Shpount</div></div><div>=C2=A0</div></div></div></div>

--089e0111bc56fe8d5d0532f9b1dc--


From nobody Tue May 17 03:44:52 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31C712D75C for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 03:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o4uTy_NMomeh for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 03:44:49 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92E612D758 for <mmusic@ietf.org>; Tue, 17 May 2016 03:44:49 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id f89so17773223ioi.0 for <mmusic@ietf.org>; Tue, 17 May 2016 03:44:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=PPqY5jADKmI+OZwOYOKM5965dT0xTo4g0wAO9+An+Ts=; b=KXrDR+FzbkWS0QnR7k3DCZNUPtcShUl0m5tKhzqbKwyx1FdE2zLHutFi5vM3FSHiR+ G9cMIdQreIz+94ALZbNLm0bCj+pqh5ott1SJlynWsEHDt6cyPrHCGaWlsaWup0J8qUFz uRFocrBA4V8W/jhv5Jyf/m7edoKWWxsbAVai1KVa2h3XLpWuT1WO2n+mhm7T/caSSNgp Vv5GPsX+px2Dhwsr9gXT9grfWU+zWQuHYmqcZFRGoCT7BrXxvOH2tfHHRPFxOxUA8cCo ZjMHmUukTu19YJkpnMrn+YmWuoCGFwOcvnDAKOEEYrKuCNqXPTzlL2iFZz+TYUTEkyoM a+zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=PPqY5jADKmI+OZwOYOKM5965dT0xTo4g0wAO9+An+Ts=; b=TMLqB4s94+UziM2kwF64XNATxSWS5w/+SXKFBlkCyfwexn9SbQdO7SeJsdfzGYIELT PKxGzLvcDULdnPuX+WoJxIVVmrDZp7sVCiXHqLN/Ezac5OqSLd41RTYKDyCOYsqs0Zoa 9P2tl5wRUOdDFpQ0nAbMmWHLP8yySD6blYFipZKd5yde8ubD4/e4MzBDgab4Kxh3DSMd wNSvUMkYWTaCxtvowuFdAHCUsZrY08nBg3Y7d9UuJKY7ryHPNKzFds6IddhxdjC7cVHu Fw3hO3Xnotzh6lqvpAQUVlw6XypGQqmvp0dBcSk102Hxro/Gj/Q5XTpTII4oRzKJauL+ ffXg==
X-Gm-Message-State: AOPr4FXmCS2XenEuURlSY7XpM/CTyygjH1rU4cGgBoatUYG2FD73qi2p1G3GBILRuYsYoJSNThh7wVKmIR7VyQ==
MIME-Version: 1.0
X-Received: by 10.107.161.195 with SMTP id k186mr359425ioe.190.1463481889159;  Tue, 17 May 2016 03:44:49 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 03:44:48 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se>
Date: Tue, 17 May 2016 06:44:48 -0400
Message-ID: <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/tgXPfxiDrSYZS9NSOkHc9EQxUSY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 10:44:51 -0000

On 16 May 2016 at 12:48, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> The main difference is that it now updates 4572 by saying that multiple f=
ingerprint attributes are associated with the SAME certificate, and in orde=
r to provide fingerprints for multiple certificates the new attribute is ne=
eded. I think that should solve Martin's backwards compatibility issue.

That wasn't the issue at all, so I think that the change is a regression.


From nobody Tue May 17 03:47:31 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8694512D766 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 03:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 801yt6Vh7NVm for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 03:47:29 -0700 (PDT)
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 D04BB12D758 for <mmusic@ietf.org>; Tue, 17 May 2016 03:47:28 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id i75so17719401ioa.3 for <mmusic@ietf.org>; Tue, 17 May 2016 03:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=EDeUSeWyniF9t8o8HjG1fPAUCvmi1W1Xx3svHm2EWUM=; b=pT5gINyjJz+tS35hs+zvSjI2z8+5kE7PddUT2YGA1lTWev50k9oKP5ZxasBqDVr554 BFrQ4Cb4XyLSajYIAttFSDzy39GkkilfiD8qdCMQoqjNBkUOE4t8wA3EEsPWEVzcM0ry ml8s4uIjAV1eXAoWTSwal/w2tfvaBadrKErWCUzwIYU5SgRoLr+gZFiBPy52W166qopD URs4RvtJDfk1MKJRecHbyxLZo9Qza+YBF3e4rbCqOhT+tMgQA7jroC55zKXPhaJkLA7T hF0EEe4EOqlorNNgUFGlfGWCHdg1cobuTTa0X+PgWCi+hi+0CUxE3860oSmJSeUCTP3W QBZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=EDeUSeWyniF9t8o8HjG1fPAUCvmi1W1Xx3svHm2EWUM=; b=FjWmpu7ZCIduyXUhIHcmUMrqKHXUBv8UoEl/67pcHIja6sR/IB63wSGex24NsG4Zj9 ONZcqg6mZKteL9N/lNgKXpFl03rPiilyPBLajd3gYorofOBnEkTHiL5GG/LpTyKzT8a1 DWP874ewMiJzbMgwMHnDc2QRGeL++AaSWYzUnIPR6Jxwyy4uOsRARLVAwlZaz8xubBSa TwvDPZAFCdL7Iu/vBeRojnsTdIe66ENrYBs0E8Vd5GzGyQ+TEXcSVXaAabDIQUQ0amuC tU3ICBoWh9X2uL0ToeGItxwWSjHNPLjCRMaQoMW4wPaSV5SRkmd+4h0m8+DmKBaZ2L20 HOwQ==
X-Gm-Message-State: AOPr4FVnoxC5YhCeTvPaYOdhVnw2PYo8oyBDKp619MNhzaI8wn2xdG5zs+gP33leK0UQ5MyOz4etenJTfyXpHQ==
MIME-Version: 1.0
X-Received: by 10.36.74.74 with SMTP id k71mr364769itb.68.1463482048199; Tue, 17 May 2016 03:47:28 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 03:47:27 -0700 (PDT)
In-Reply-To: <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CAD5OKxtiJRi4r2FystQfi3T1e3TGws7OF-5jNd1ep9OFFd=Crg@mail.gmail.com>
Date: Tue, 17 May 2016 06:47:27 -0400
Message-ID: <CABkgnnVeD6k3XCXd-2DFBcwwRHT=xC4M4=nQE-0vEu_yA-3Tsw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ntMWuRdBp-jbAnqMWKDjYqTtXiw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 10:47:30 -0000

This is the issue I think we need to address...

On 16 May 2016 at 12:59, Roman Shpount <roman@telurix.com> wrote:
> Finally, I still have a major problem with Martin's proposal. This is a
> change comparatively to every current implementation of fingerprint matching
> which I have seen.

I'm not proposing that we change existing implementations.  On the
contrary, this relies on them doing exactly what they do today.

> Furthermore, this is a potentially breaking change with
> no indication to the remote party that a different matching algorithm is
> used. I would strongly prefer that any updates to anything SDP fingerprint
> related would be a clarification of how multiple fingerprints are handled
> when received by the end point. This is a clarification of RFC 4572, not a
> new authentication framework. It should not impose any new restrictions on
> fingerprint generation for RFC 4572, such as that only single certificate is
> used with connection

I agree with this.

> or that same sets of hash functions must be used for
> each certificate, since this will not be backwards compatible with RFC 4572,

But disagree with this.  How is providing a different hash going to be
incompatible with existing implementations of 4572?


From nobody Tue May 17 05:45:49 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144F812D570 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 05:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kTUBUsHLg-BG for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 05:45:47 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 728A612D555 for <mmusic@ietf.org>; Tue, 17 May 2016 05:45:46 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-5f-573b1277cd35
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.183.57]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id E0.64.12516.7721B375; Tue, 17 May 2016 14:45:43 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.03.0248.002; Tue, 17 May 2016 14:44:40 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIP+rhurA/1YB9AD+q6+DgA==
Date: Tue, 17 May 2016 12:44:40 +0000
Message-ID: <D360ECF9.883D%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com>
In-Reply-To: <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1E81CFDA333A93449E53DF6D8DFFDBED@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBIsWRmVeSWpSXmKPExsUyM2K7pW65kHW4Qc81NYtrZ/4xWkxd/pjF YsWGA6wOzB5/339g8tg56y67x5IlP5kCmKO4bFJSczLLUov07RK4Mjq2HmMreMtSceN5N0sD 4y/mLkZODgkBE4mepavZIWwxiQv31rN1MXJxCAkcYZTY1zUJylnCKNF2ZSNLFyMHB5uAhUT3 P22QBhEBXYlFZx+ANTML+Eq8XPAFbKiwgKfExkf7WCFqvCQuTF3ADjJHROAbo8T9z89YQBIs AqoSa/6tBWvmFbCS+L6hgQVi2SEuiVvXl4F1cwoESkzYfYwRxGYEOu/7qTVMENvEJW49mc8E cbaAxJI956HeEZV4+fgfWK+ogJ7EvhfnGSHiihJXpy+H6tWRWLD7ExuEbS1x785OFghbW2LZ wtfMEAcJSpyc+YRlAqPELCTrZiFpn4WkfRaS9llI2hcwsq5iFC1OLS7OTTcy1kstykwuLs7P 08tLLdnECIzPg1t+6+5gXP3a8RCjAAejEg/vAyercCHWxLLiytxDjBIczEoivI8ErcOFeFMS K6tSi/Lji0pzUosPMUpzsCiJ8/q/VAwXEkhPLEnNTk0tSC2CyTJxcEo1ME7MfWD71MXo14yz S/JEK1uyZVLuv2f9UM15nsHn8dl0/tCvnLY+6qHXVh3LU78ukTD3s940o+0zWbbeia3cbmrv UVZZa7rAyKlw3RHVXJGpab7yLbE/Dh5cubr+9rE804aZSxRa3+8pEmJ9tfOvll7r/pWBVp1Z Uf9NjD8pn2s0l7Go9HGZpsRSnJFoqMVcVJwIAKFRr8zLAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RI7jxCoqJqdiF0iVB0krrDhppYQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 12:45:48 -0000

>>The main difference is that it now updates 4572 by saying that multiple
>>fingerprint attributes are associated with the SAME
>>certificate, and in order to provide fingerprints for multiple
>>certificates the new attribute is needed. I think that should solve
>>Martin's backwards compatibility issue.
>
>That wasn't the issue at all, so I think that the change is a regression.

Ok, so you think that it should be allowed to use fingerprint attributes
BOTH for multiple hashes (for a single certificate) AND multiple
certificates, and the issue is the matching on receiving side?

Regards,

Christer


From nobody Tue May 17 06:29:32 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2673B12D5BF for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 06:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 IDcX65jxegk5 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 06:29:29 -0700 (PDT)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9364212D51F for <mmusic@ietf.org>; Tue, 17 May 2016 06:29:29 -0700 (PDT)
Received: by mail-ig0-x22f.google.com with SMTP id qe5so69462607igc.1 for <mmusic@ietf.org>; Tue, 17 May 2016 06:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NGy2uYQi9cP5i0iV15a33QREt2l5z12OSUj5YIc+eo0=; b=Fe0+2hr4OmjOQ/fBMlDSyVsOPmITIiRftUddeqaJo2QGnjCyyFumswvU01PhXV3q+7 sSRZmvWQMClDvCtBuqhYjznksRj7dwFqmf9Gr8HksB0uJyOEINtg7Ezrm+GZSiqMZpou cow1jf/INT3NPaT7eZxSg5aQRLTGaYaxqTnK5Iq0Cl4w7Pk5vMiGw63fPHY0JWbjqTOS Hz83e1+/JJI32CFH6v2rump1kXqIyGrJz8mZR3JJ0Xd6CJXCf4MTBLgMftgDwZU+NWRC R/VfYD0F2SBSoi+iOj5U84pRb6OVnT9cJ3/JYk5bF//MNkSA/znL0/PCUxEmxoKrupzH 1cbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=NGy2uYQi9cP5i0iV15a33QREt2l5z12OSUj5YIc+eo0=; b=T4PcYTGQjGBAKTrKRbRvSVsO5XDRvlIYJpwzCsYg6UtOr/6i49PlWoABjFu7YR2seP NRMxwUQxuL337o83jWQl+D8+MwlTHyLRV3PfikaoRS1E2ExAUQiXAtjvQLQUBfU3Hsxl RiNMw82djTpFTli288pBK9fAziaDF6u8TxDcSZDnzO59QQjQ+lfPpiX42fWy/RmLlCAy 7IPOOZ0Ti9LMUIUVaZUiar/q4zxC4z/ACJ9Cu23W7k0c85cbzy4Y96nKGoW0HCpKbDfU HxWctDNjOWijsP8hTcD9gXIOno4O1U2iePp/+rVBHCh6fuyhi323nTBFFXmEZ/M/B+tD 8uAw==
X-Gm-Message-State: AOPr4FXlJMqvk+Hlu2xO8bkjKUU8qD6hhMFsH3Jym/dZsAAJJ12eU3qNGMutKsBOUpNymnwkLoO7oUcY+y3LkA==
MIME-Version: 1.0
X-Received: by 10.50.33.81 with SMTP id p17mr14003633igi.58.1463491768900; Tue, 17 May 2016 06:29:28 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 06:29:28 -0700 (PDT)
In-Reply-To: <D360ECF9.883D%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com>
Date: Tue, 17 May 2016 09:29:28 -0400
Message-ID: <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ex_WJsUDrlt23FA9ddGHPkXlxak>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 13:29:31 -0000

On 17 May 2016 at 08:44, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Ok, so you think that it should be allowed to use fingerprint attributes
> BOTH for multiple hashes (for a single certificate) AND multiple
> certificates, and the issue is the matching on receiving side?


Yes, and it appears that Roman has an issue with what I had proposed,
but I'm sure that I don't understand it.


From nobody Tue May 17 06:50:20 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A9512D5F5; Tue, 17 May 2016 06:50:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160517135019.22271.92180.idtracker@ietfa.amsl.com>
Date: Tue, 17 May 2016 06:50:19 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/SWMQRNHhe69GAY22JYUzuDV_IoQ>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 13:50:19 -0000

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

        Title           : A Session Initiation Protocol (SIP) usage for Trickle ICE 
        Authors         : Emil Ivov
                          Thomas Stach
                          Enrico Marocco
                          Christer Holmberg
	Filename        : draft-ietf-mmusic-trickle-ice-sip-04.txt
	Pages           : 36
	Date            : 2016-05-17

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

   This document defines usage semantics for Trickle ICE with the
   Session Initiation Protocol (SIP).


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-04

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


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

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


From nobody Tue May 17 07:00:42 2016
Return-Path: <thomass.stach@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE4A12D5E3 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 76qhvD9WV-un for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:00:34 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::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 BC93112D5E1 for <mmusic@ietf.org>; Tue, 17 May 2016 07:00:33 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id u64so7250869lff.3 for <mmusic@ietf.org>; Tue, 17 May 2016 07:00:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=OJWANhpQ23K/0Iq6VRwsbd7EgDmrp/NO2+0n8OZ9U6U=; b=o3v6KMvsIMgrQd3Unn3WBHtFP2muYx+z42+p4MBmuteMCGdraHQPb8pL/WfHfYFVZQ y87MTh17zef8ZOcmed9+XWD44QNO/Ru9qmID5Nr/wxEl3R0aihXVqbIHUo1DjsMq4Xs6 M78pg3sMOtvwjcrfgk2cK9yUkLLyfElAtpfsgg3B5vGjTk/+Rkb9fahYt3T/fAQnp8rp qiFcoFlDLUbLTl5eWlIg0MkW2bC8X4LmpsLYBE380BC28IsLoayB4WO/xthzav9Dfqj3 F5gHJG7QXcJ1vJhMKvW9OlG9DyBVzTYEwR3XkK3LPDALGCUn4lT+j0v6pgIsw+XCDWe1 Hbqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=OJWANhpQ23K/0Iq6VRwsbd7EgDmrp/NO2+0n8OZ9U6U=; b=L7nvrxG8ccKJ49VV5Er/Z2HCSKbv/gQS1CF3qEg0Lou1aSwi/gvu9RaJ6eQ6my0fjO 4KqbFWKdEIUnZ6XMwFVfnoVylCYD7Ki+d+Qv/CWnigHsPQbFR3Zz2XIg23UZ9Qo5/jMr ENdhm2F/hT0nlvsj9NtDVVp+mJCtt+XRZTpRWZBcGraAQmBF3/KcbkJlVEcErohf1vAM L4Dy2Xuj76ZmgzZZwPiHwGNrY4rd31I9a9nuvuin9pey6JPCVELSU5voIaYve37MXorm 6tzvFrDUW78+xniFbEvJ2ib28PC0/jFWWMVc2Ipdr60MPqggvz9Mw83Q5qR5F2Vo0ATY sx5g==
X-Gm-Message-State: AOPr4FXIVUyiHUh6T/etByCyCtPu4fGEfyw1qSOwP//sTUVijD9gkDLrmcvrao1195kK7Q==
X-Received: by 10.25.83.82 with SMTP id h79mr604654lfb.138.1463493631887; Tue, 17 May 2016 07:00:31 -0700 (PDT)
Received: from [192.168.2.106] (d91-130-21-47.cust.tele2.at. [91.130.21.47]) by smtp.googlemail.com with ESMTPSA id f62sm533067lff.34.2016.05.17.07.00.30 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 07:00:31 -0700 (PDT)
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com>
To: MMUSIC <mmusic@ietf.org>
From: Thomas Stach <thomass.stach@gmail.com>
X-Forwarded-Message-Id: <20160517135019.22271.65158.idtracker@ietfa.amsl.com>
Message-ID: <573B23FD.3070903@gmail.com>
Date: Tue, 17 May 2016 16:00:29 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <20160517135019.22271.65158.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/d5r7NnDg2YYbfN5FIMJmpj888Yg>
Subject: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:00:40 -0000

All,

the changes from draft-ietf-mmusic-trickle-ice-sip-03 include

- replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and 
draft-ietf-mmusic-ice-sip-sdp
- corrected Figure 10, credits to Ayush Jain for finding the bug
- referencing a=rtcp and a=rtcp-mux handling from 
draft-ietf-mmusic-ice-sip-sdp
- referencing a=rtcp-mux-exclusive handling from 
draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support 
a=rtcp-mux-exclusive
- clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the 
application/trickle-ice-sdpfrag body

Currently there are no open issues in this draft. However, it could 
probably benefit from a thorough review.
So, comments welcome.

With respect to progressing this work, I think that it should go forward 
alongside with draft-ietf-ice-trickle since any updates of that document 
might influence the content of this draft.

Regards
Thomas



-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-ietf-mmusic-trickle-ice-sip-04.txt
Date: 	Tue, 17 May 2016 06:50:19 -0700
From: 	internet-drafts@ietf.org
To: 	Thomas Stach <thomass.stach@gmail.com>, Emil Ivov 
<emcho@jitsi.org>, Enrico Marocco <enrico.marocco@telecomitalia.it>, 
Christer Holmberg <christer.holmberg@ericsson.com>



A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
has been successfully submitted by Thomas Stach and posted to the
IETF repository.

Name:		draft-ietf-mmusic-trickle-ice-sip
Revision:	04
Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
Document date:	2016-05-17
Group:		mmusic
Pages:		36
URL:            https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice-sip-04.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-04
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-04

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

    This document defines usage semantics for Trickle ICE with the
    Session Initiation Protocol (SIP).

                                                                                   


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

The IETF Secretariat




From nobody Tue May 17 07:10:12 2016
Return-Path: <kevindempsey70@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 DA57812D620 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:10:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GeyYvh9UBP22 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:10:08 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6842512D61C for <mmusic@ietf.org>; Tue, 17 May 2016 07:10:08 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id f66so21201087vkh.2 for <mmusic@ietf.org>; Tue, 17 May 2016 07:10:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=YWrdCT3HA8I/WNv961fUyY4uYsSVqdZuBZZ9QXUiT90=; b=Bp1xspT9FwzkHP+GhNgZT4Of8S2QFR2QPRRHPKuK2rMh2Xt5sdb5QfXSSKpOEWQh4Z FGp4VqSD91LRDsIUlpdASoJIIvMlxFDXuMhTTD9WlwP0Hu6d1UdZBUxQaJA8SoKDLVQe ORj/A7nT3X3j6oTX2EvNM+14EbzlqEz3JLXxU2iVMAhY9t9a6TxHUJMitjf14Ve8HbXl a6SOu4l4HJRjJ7b6WkvK23p/1Lu+8ruNxVbV55MJ+wIfxwF3tXi25PCzQCyETRMIz7dK +8UkkWk7TUW4llmhlT7XYC/b0BT1xJbmj+k5lNw5MsG3z2JKoBH/bYjQtIPLoNuLCmyb gh9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=YWrdCT3HA8I/WNv961fUyY4uYsSVqdZuBZZ9QXUiT90=; b=BUz6Ij8DzKkhP4GcxTJMr++vFSbRlbCY9ah+TZLWGJu5WRld0m93iSIusnksUalvCA Hfp9+r4MwOr1zy8kOcHjkAs46tu2pIAY2tcJP1nD8SmeSltLAxsk+CTa8BJuqq1tMxvl AFCSjNzMUULrzE7WpAGhUVJ2N6sKHsbMAPewz5mZsfvRcPuMrT5p3WbV3wc68kzllhoV qp+5gJC7aAxSJ3DeT0XiUUhwF0Pm5c1ukY9QIwH9cpD+k1aKR80E9frPqtXEcHM0RG83 zCK2HhtGMvwrWm51mFB29UZE75ECTmmL/rQZVrQgKvHHJi2SmOO4voofojIWDTHp53gj h88A==
X-Gm-Message-State: AOPr4FVQgkqlp3K6tBjv11UszH4SR9j7HpmVW9NQ8zWzECsf5+DrD9+OJozW0OGGnj009VtzyAGCH3HB3fuUOg==
MIME-Version: 1.0
X-Received: by 10.176.3.97 with SMTP id 88mr780845uat.82.1463494207544; Tue, 17 May 2016 07:10:07 -0700 (PDT)
Received: by 10.159.32.132 with HTTP; Tue, 17 May 2016 07:10:07 -0700 (PDT)
In-Reply-To: <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com>
Date: Tue, 17 May 2016 15:10:07 +0100
Message-ID: <CAMvTgcdPsuMRKk1OS7ua6T6gqgQ6qQd9BXYGEeMUaGBg_C82fQ@mail.gmail.com>
From: Kevin Dempsey <kevindempsey70@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=001a11373e925f2cd205330a4cb9
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/SwGnls72knKEGVkZeuXSCtP33aU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:10:11 -0000

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

If I understand correctly, your proposal requires senders to include the
same set of hashes for each certificate.

The propose new attribute does not make that a requirement and is also
makes it clear which set of hashes belong to the same certificate.

On 17 May 2016 at 14:29, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 17 May 2016 at 08:44, Christer Holmberg
> <christer.holmberg@ericsson.com> wrote:
> > Ok, so you think that it should be allowed to use fingerprint attributes
> > BOTH for multiple hashes (for a single certificate) AND multiple
> > certificates, and the issue is the matching on receiving side?
>
>
> Yes, and it appears that Roman has an issue with what I had proposed,
> but I'm sure that I don't understand it.
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">If I understand correctly, your proposal requires senders =
to include the same set of hashes for each certificate.<div><br></div><div>=
The propose new attribute does not make that a requirement and is also make=
s it clear which set of hashes belong to the same certificate.</div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 17 May 2016 at =
14:29, Martin Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomso=
n@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">On 17 May 2016 at 08:44, Christer Holm=
berg<br>
<span class=3D"">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com">chri=
ster.holmberg@ericsson.com</a>&gt; wrote:<br>
&gt; Ok, so you think that it should be allowed to use fingerprint attribut=
es<br>
&gt; BOTH for multiple hashes (for a single certificate) AND multiple<br>
&gt; certificates, and the issue is the matching on receiving side?<br>
<br>
<br>
</span>Yes, and it appears that Roman has an issue with what I had proposed=
,<br>
but I&#39;m sure that I don&#39;t understand it.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div>

--001a11373e925f2cd205330a4cb9--


From nobody Tue May 17 07:19:34 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DCA912D63E for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nnfnNV7z4dHQ for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:19:29 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9BDE12D63F for <mmusic@ietf.org>; Tue, 17 May 2016 07:19:28 -0700 (PDT)
Received: by mail-ig0-x22d.google.com with SMTP id m9so10497932ige.1 for <mmusic@ietf.org>; Tue, 17 May 2016 07:19:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=wHHKw3dPr9mwEUpcLwBGEVccr745WcXqzVwLP0wwxJ8=; b=GhXLdnSid8LOq+cKMO6Bl2OkmcWmQDS13K2cjC9oAOlceiAn4M8t7pS1IlCN54x6Xe CykiDBHLltaqtjtSN2xO62dWhPmcB+IuoJa+dGf2iRCLBAZYUePV7S5inoKBIhfLc4So AWvu/TBy2MlDTp40WMEI2R4jPZBS4Tm90aClxOLPeia/TxGzfdMlqem5HqGfEGhptQHX /1eZ7+w7rsirqYwfnPSo3T54RB1//oDaWgmXme/cEln/6hRk0K6GquwS7y5IqUPZMWqY JlVnipB/8JymvgatmD3Jq6NRFMmjXWuOW5/OxkXAR23e2IAp6nNB1pyQvIUoPeL7E33w /UVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=wHHKw3dPr9mwEUpcLwBGEVccr745WcXqzVwLP0wwxJ8=; b=HluQk2aPnrHXMJrjyptPhSJUHufh5twFLfVWz6W7Pi4ZvJM2I1V4bLhnmjcNPVI+sE fKsy/VfjL6DbJRXxgSTjmWXWYH8a9zZLb4cfiah8067zMzO5nK1dBvVYDo/nzmoxxGHc 4ZDTesDsoiJTvzpGkOMSKDTKdhY30HAFVC737R6NBiblBqIgpOv7hWCvXNlTcM3FUjRR IuSWlge6nays3mIolhpTQIoX7SzXancLpuvuBVlNl2oGZZ+hLgEHFcXStV6eO5WpxrvF 9beXRBIRvWgpMZRKk7rqqdbS902II0uD+FyzQkl5FDFhgKUfnqKSGZAymHsljTKTMpxY 8x5A==
X-Gm-Message-State: AOPr4FXT5jV+fcEZJHV4UrurVdP4ZYsTDHV7DlQUU5fiPRPCVyvNkFCWQHOyuTAwaABB97zOuPgm4czfmcUVSA==
MIME-Version: 1.0
X-Received: by 10.50.58.71 with SMTP id o7mr12688103igq.77.1463494768307; Tue, 17 May 2016 07:19:28 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 07:19:28 -0700 (PDT)
In-Reply-To: <CAMvTgcdPsuMRKk1OS7ua6T6gqgQ6qQd9BXYGEeMUaGBg_C82fQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAMvTgcdPsuMRKk1OS7ua6T6gqgQ6qQd9BXYGEeMUaGBg_C82fQ@mail.gmail.com>
Date: Tue, 17 May 2016 10:19:28 -0400
Message-ID: <CABkgnnVjysSRftJWOHNf4nLBGikft3yK+sxH3S5hVjCzksZd9Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Kevin Dempsey <kevindempsey70@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/L3pV6Mf2OwDrwL3jzj2sPzcPTX8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:19:33 -0000

On 17 May 2016 at 10:10, Kevin Dempsey <kevindempsey70@gmail.com> wrote:
> If I understand correctly, your proposal requires senders to include the
> same set of hashes for each certificate.

Yes.

> The propose new attribute does not make that a requirement and is also makes
> it clear which set of hashes belong to the same certificate.

I haven't seen any evidence that the either is necessary.  The latter
especially.  Happy to change my mind if someone has real problems with
the former other than the purely academic.


From nobody Tue May 17 07:41:41 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B2712D69A for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:41:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvhWc9jbKqg0 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:41:38 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D173212D16E for <mmusic@ietf.org>; Tue, 17 May 2016 07:41:37 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-89-573b2da060fd
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 8F.4A.18043.0AD2B375; Tue, 17 May 2016 16:41:36 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0248.002; Tue, 17 May 2016 16:41:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Kevin Dempsey <kevindempsey70@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIP+rhurA/1YB9AD+q6+DgP1XhWkA+q7/doD1XfxQAOq70OvY
Date: Tue, 17 May 2016 14:41:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCF3F9@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAMvTgcdPsuMRKk1OS7ua6T6gqgQ6qQd9BXYGEeMUaGBg_C82fQ@mail.gmail.com>, <CABkgnnVjysSRftJWOHNf4nLBGikft3yK+sxH3S5hVjCzksZd9Q@mail.gmail.com>
In-Reply-To: <CABkgnnVjysSRftJWOHNf4nLBGikft3yK+sxH3S5hVjCzksZd9Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FCF3F9ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKIsWRmVeSWpSXmKPExsUyM2K7ge4CXetwg3ez+S1uzn/LYnHtzD9G i6nLH7NYrNhwgNWBxePv+w9MHjtn3WX3WLLkJ1MAcxSXTUpqTmZZapG+XQJXRuPjbcwFR1Qq Zl56zNLAeFe+i5GTQ0LAROJBRwM7hC0mceHeerYuRi4OIYEjjBJ7FvexQjhLGCVefN0J5HBw sAlYSHT/0wZpEBGIlDj4/jYriM0s4Cvx/ud0sEHCAp4S109/ZoOo8ZK4MHUBO8gcEYE+JokH c1aDNbAIqEqsXPsIzOYFar44Zzs7xLJjPBIrnk9gAUlwCgRKfPzVBzaVEei876fWMEFsE5do +rKSFeJsAYkle84zQ9iiEi8f/4O6KF/i0LHdLBALBCVOznzCMoFRZBaS9llIymYhKYOIG0h8 eX8bytaWWLbwNTOErS/R/f40E7L4Akb2VYyixanFxbnpRkZ6qUWZycXF+Xl6eaklmxiBkXdw y2+rHYwHnzseYhTgYFTi4X3gZBUuxJpYVlyZe4hRgoNZSYR3vo51uBBvSmJlVWpRfnxRaU5q 8SFGaQ4WJXFe/5eK4UIC6YklqdmpqQWpRTBZJg5OqQZGZs9dey1W6/mdLb/u4XW15pl1xL+/ naVSMyO+9jpM0hHiOSwg5LCuftLi3+uuuCqvOSbONV2tmSOoi2WjbtXfgvDzmzz4NU2XZj4M 63qgJqi30tbSK29ragX7gleJhgbJKqe6dF6efsxyJrtKqsefX7S4Z7nPquKFGVwzH3BOykxa vXNp9V4lluKMREMt5qLiRAD63kDKuAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/kIhkVU_aJ854zx_0G7H8RrpwcI0>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:41:39 -0000

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

Hi,

The problem people seem to have is mandating the same set of hashes, in cas=
e they are calculated by different entities.

I think the question is whether we could mandate the operators of such enti=
ties to make sure that the same hashes are used. After all, the different-e=
ntity use-case will be relatively uncommon, in my opinion.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Martin Thomson<mailto:martin.thomson@gmail.com>
Sent: =FD17/=FD05/=FD2016 17:19
To: Kevin Dempsey<mailto:kevindempsey70@gmail.com>
Cc: Christer Holmberg<mailto:christer.holmberg@ericsson.com>; mmusic@ietf.o=
rg<mailto:mmusic@ietf.org>; Paul Kyzivat<mailto:pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01

On 17 May 2016 at 10:10, Kevin Dempsey <kevindempsey70@gmail.com> wrote:
> If I understand correctly, your proposal requires senders to include the
> same set of hashes for each certificate.

Yes.

> The propose new attribute does not make that a requirement and is also ma=
kes
> it clear which set of hashes belong to the same certificate.

I haven't seen any evidence that the either is necessary.  The latter
especially.  Happy to change my mind if someone has real problems with
the former other than the purely academic.

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
The problem people seem to have is mandating the same set of hashes, in cas=
e they are calculated by different entities.<br>
<br>
I think the question is whether we could mandate the operators of such enti=
ties to make sure that the same hashes are used. After all, the different-e=
ntity use-case will be relatively uncommon, in my opinion.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:martin.thomson@gmail.com">Martin Thomson</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD17=
/=FD05/=FD2016 17:19</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:kevindempsey70@gmail.com">Kevin Dempsey</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a>;
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a href=3D"mailto:p=
kyzivat@alum.mit.edu">
Paul Kyzivat</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01</span><br>
<br>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">On 17 May 2016 at 10:10, Kevin Dempsey &lt;kevinde=
mpsey70@gmail.com&gt; wrote:<br>
&gt; If I understand correctly, your proposal requires senders to include t=
he<br>
&gt; same set of hashes for each certificate.<br>
<br>
Yes.<br>
<br>
&gt; The propose new attribute does not make that a requirement and is also=
 makes<br>
&gt; it clear which set of hashes belong to the same certificate.<br>
<br>
I haven't seen any evidence that the either is necessary.&nbsp; The latter<=
br>
especially.&nbsp; Happy to change my mind if someone has real problems with=
<br>
the former other than the purely academic.<br>
</div>
</span></font>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B37FCF3F9ESESSMB209erics_--


From nobody Tue May 17 07:45:52 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5040112D65A for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOWGo2JXg8_X for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:45:48 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA36112D8DA for <mmusic@ietf.org>; Tue, 17 May 2016 07:45:46 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id 190so26095925iow.1 for <mmusic@ietf.org>; Tue, 17 May 2016 07:45:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=nfY6YEMfF+KXSwk4Fu6QYUaNlJM7ByRBtrTzygYDH58=; b=uaFBpacXuHTXk6UZOMkxjY5HxcGQLboZsO/H1hU+TV5okQe4klSbBAcTQSh6ChYsMy Iy48CTvDu1dt+i3nshN6h6SgTF9uxG+x8RwU8RsrLbxaPFa/y7YakCaiDFY8MQf1u8aj FK9/qygYTMgsIOg3KaaZQyQNNGXTaNUtlgsyf3IxStK84d5nQNXbGnV+pXUK0w1UNsXi SagtXiUtfOQIOO0RCzIS5v5T83AnzdefNjay/HT88Rt5/uM2DLeI+P5I9yxpLnhG8D3C Eud9bcQLF8Tdb1wS1nqxLoAY/WoVAHv/hMxT+COkvjuSYdSNQXtgw3g4D/M/G3Fc6n+s neNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=nfY6YEMfF+KXSwk4Fu6QYUaNlJM7ByRBtrTzygYDH58=; b=hGpJpdRHsA/gLN6GDuQ+i+M8pZVc2J2sN6YbvW6ukiwx4Hm63B8s29p79hI9L8A5+/ nepaKhi/rBsMBtjibpL9cFGxBqzEPdLJ7g83O6gPBVZPxiOKLk8g+rCZEqonVTI+acUC b9XcnwpLiqg4V65R2JgJYJYHq0nE9kKkBI7LIkOxd9gblvw9MsFxI8ONUpwTHd8mxZUn beA5H7JpLaGlOzO469P9HRUULXBw0pg+qG1dQTweMxycrRk62aHBGd5BiP18Qi+IuIMg S03xnaf4lFK5GKuutVCaTLDSFS283uaAocLp/hgAGbck4mz0RdzWRSwjmzSOZ6Zg3cUm 8jxw==
X-Gm-Message-State: AOPr4FVWYNiE6M9Tz/1eX6HdzoXQz4g35rRV0ifhT6wbCn+rC1LAvc4H8k4DMehPdRXN3g==
X-Received: by 10.36.107.17 with SMTP id v17mr1330166itc.51.1463496345859; Tue, 17 May 2016 07:45:45 -0700 (PDT)
Received: from mail-io0-f173.google.com (mail-io0-f173.google.com. [209.85.223.173]) by smtp.gmail.com with ESMTPSA id gn3sm1137138igb.16.2016.05.17.07.45.44 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 07:45:44 -0700 (PDT)
Received: by mail-io0-f173.google.com with SMTP id 190so26094654iow.1 for <mmusic@ietf.org>; Tue, 17 May 2016 07:45:44 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.156.131 with SMTP id b125mr1413640ite.95.1463496344193; Tue, 17 May 2016 07:45:44 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 17 May 2016 07:45:43 -0700 (PDT)
In-Reply-To: <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com>
Date: Tue, 17 May 2016 10:45:43 -0400
X-Gmail-Original-Message-ID: <CAD5OKxup32aeFn-GNF9h1MjK-EQashv-PhsjrutsTxMZ5_b5bQ@mail.gmail.com>
Message-ID: <CAD5OKxup32aeFn-GNF9h1MjK-EQashv-PhsjrutsTxMZ5_b5bQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c089e7cb9e13b05330acbbc
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/2w-8AWgJu9qV3_Vefc26g0307jA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:45:50 -0000

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

On Tue, May 17, 2016 at 9:29 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 17 May 2016 at 08:44, Christer Holmberg
> <christer.holmberg@ericsson.com> wrote:
> > Ok, so you think that it should be allowed to use fingerprint attributes
> > BOTH for multiple hashes (for a single certificate) AND multiple
> > certificates, and the issue is the matching on receiving side?
>
>
> Yes, and it appears that Roman has an issue with what I had proposed,
> but I'm sure that I don't understand it.
>
>
Martin,

I understand that you perceive this issue as academic. I see this as bad
design.

Let me try to explain this again:

1. There are multiple deployed current implementations that match multiple
fingerprints (Firefox and Chrome come to mind)
2. Your proposed a matching algorithm which is different and considerably
stricter then existing implementations
3. You proposed solution provides no indication if your new matching
algorithm is used or a clear migration path. If someone implements it,
connections which worked yesterday will stop working tomorrow with no
indication of the reason.

Your proposed solution should work with offers generated by Firefox and
Chrome, but there are quite a few other implementations which are currently
designed to work with WebRTC end points. Without substantial testing it is
impossible to say if any of them will be affected. They can be affected if
they support multiple certificates or if they insert incorrectly calculated
sha-512 fingerprint together with sha-256.

Considering that a=fingerprint has other design issues (non-extensible,
uses HEX encoding), I am in favor of documenting what current
implementations already do in regard to a=fingerprint and addressing your
security concerns using a new attribute. Since most, if not all DTLS
related implementations are WebRTC related, it should be possible to
migrate to a new attribute within a reasonable time period, provided we
have a migration path. New attribute provides such a path by including both
old and new style fingerprints.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Tue, May 17, 2016 at 9:29 AM, Martin Thomson <span dir=3D"ltr">&lt;=
<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomso=
n@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);=
padding-left:1ex">On 17 May 2016 at 08:44, Christer Holmberg<br>
<span class=3D"">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com">chri=
ster.holmberg@ericsson.com</a>&gt; wrote:<br>
&gt; Ok, so you think that it should be allowed to use fingerprint attribut=
es<br>
&gt; BOTH for multiple hashes (for a single certificate) AND multiple<br>
&gt; certificates, and the issue is the matching on receiving side?<br>
<br>
<br>
</span>Yes, and it appears that Roman has an issue with what I had proposed=
,<br>
but I&#39;m sure that I don&#39;t understand it.<br>
<div class=3D""><div class=3D"h5"><br></div></div></blockquote><div><br></d=
iv><div>Martin,</div><div><br></div><div>I understand that you perceive thi=
s issue as academic. I see this as bad design.</div><div><br></div><div>Let=
 me try to explain this again:</div><div><br></div><div>1. There are multip=
le deployed current implementations that match multiple fingerprints (Firef=
ox and Chrome come to mind)</div><div>2. Your proposed a matching algorithm=
 which is different and considerably stricter then existing implementations=
</div><div>3. You proposed solution provides no indication if your new matc=
hing algorithm is used or a clear migration path. If someone implements it,=
 connections which worked yesterday will stop working tomorrow with no indi=
cation of the reason.</div><div><br></div><div>Your proposed solution shoul=
d work with offers generated by Firefox and Chrome, but there are quite a f=
ew other implementations which are currently designed to work with WebRTC e=
nd points. Without substantial testing it is impossible to say if any of th=
em will be affected. They can be affected if they support multiple certific=
ates or if they insert incorrectly calculated sha-512 fingerprint together =
with sha-256.</div><div><br></div><div>Considering that a=3Dfingerprint has=
 other design issues (non-extensible, uses HEX encoding), I am in favor of =
documenting what current implementations already do in regard to a=3Dfinger=
print and addressing your security concerns using a new attribute. Since mo=
st, if not all DTLS related implementations are WebRTC related, it should b=
e possible to migrate to a new attribute within a reasonable time period, p=
rovided we have a migration path. New attribute provides such a path by inc=
luding both old and new style fingerprints.</div><div><br></div><div>Regard=
s,</div><div><div class=3D"gmail_signature">_____________<br>Roman Shpount<=
/div></div><div>=C2=A0</div></div></div></div>

--94eb2c089e7cb9e13b05330acbbc--


From nobody Tue May 17 07:48:37 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C06B12D90C for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlJ31vaTUifL for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:48:35 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04BD012D909 for <mmusic@ietf.org>; Tue, 17 May 2016 07:48:35 -0700 (PDT)
Received: by mail-ig0-x229.google.com with SMTP id s8so11000940ign.0 for <mmusic@ietf.org>; Tue, 17 May 2016 07:48:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=2xMK9rob8+PFIurk2ooq4ar0+1u1NMFL6u9Y/LjOpQI=; b=TaJIy6cJOA05Dud5r1s9WzUk8whtdfFCIiQ2CtLl6S9h3BJvI7NaZEeQSwilTZT6eG FKjISfwmlUak0iGLhFgH/mRO+99kB1zA92N6okjaPop+FUSoDax2zmt5TweEsaMcM0Qz /Wnka/6Lr/xMmX5i07HtYjiXtATq3gVTM9tGHRuY5LKaIrzK/eH4EgELTV0EFoWILdmI VxJM2JP9NUeFKYC1+quRMFkh2u8npAF8Ke+RpXS8bL6LnuxLs+ezkZOOrmaOr+/VfDDG BKx8KwK9fWfB12BngNHEVpPaWX54RrxjI5xeuFzPlzZlsd/C8ExtPuUTWkMr36JoxGQG x5xQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=2xMK9rob8+PFIurk2ooq4ar0+1u1NMFL6u9Y/LjOpQI=; b=gpTT0rpSCthRoXes+rVXmkbRDHIfIYbkDH1nvBCOvCok0hGp6qqRZjQjrrxwekVRfM uhACDWKT9/lWIYhpOZs12zdUzas3N3LFlZZ4YyplDCAeFpEvSX1uX4i+7syRqI28gApN tUQJeXEQ/wt17/4oKEbeYUYFPuB/IxRtpHcHU85oXLKRPMLu/ppKSmVdRc4EhTFQuNNR wlEe3bxN6n8gqP56QWoisK0nS2k+Ujl0FoNUzSDRfhLQpSokLcPgL0VEaIMXiUcsy8Uv ZtiFAibGP14vcnC505A4c2+nlnUZFlzqvfBzyukvCeTjMCxFNZVMdHp+StituQHA31CQ NRlg==
X-Gm-Message-State: AOPr4FUIgAtjLdWHluXotwjQoLFHMHmqEFXhq+/J7S9yEX/rL73KkW3n9HUjSHrK22u/6w==
X-Received: by 10.50.100.2 with SMTP id eu2mr1417106igb.89.1463496514295; Tue, 17 May 2016 07:48:34 -0700 (PDT)
Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com. [209.85.213.181]) by smtp.gmail.com with ESMTPSA id v136sm7210009ita.3.2016.05.17.07.48.33 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 07:48:33 -0700 (PDT)
Received: by mail-ig0-f181.google.com with SMTP id m9so11018265ige.1 for <mmusic@ietf.org>; Tue, 17 May 2016 07:48:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.124.39 with SMTP id mf7mr1421708igb.95.1463496512862; Tue, 17 May 2016 07:48:32 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 17 May 2016 07:48:32 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCF3F9@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAMvTgcdPsuMRKk1OS7ua6T6gqgQ6qQd9BXYGEeMUaGBg_C82fQ@mail.gmail.com> <CABkgnnVjysSRftJWOHNf4nLBGikft3yK+sxH3S5hVjCzksZd9Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCF3F9@ESESSMB209.ericsson.se>
Date: Tue, 17 May 2016 10:48:32 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtM59u8qzF7fS4ws34crkRGbM5v6WjFvQJ4K_0R67Dh-Q@mail.gmail.com>
Message-ID: <CAD5OKxtM59u8qzF7fS4ws34crkRGbM5v6WjFvQJ4K_0R67Dh-Q@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=089e0111bc56c7aa1205330ad597
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KBgnvzHXQ3Wj-VPFRSsvVcK6MMc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:48:36 -0000

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

On Tue, May 17, 2016 at 10:41 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> The problem people seem to have is mandating the same set of hashes, in
> case they are calculated by different entities.
>
> I think the question is whether we could mandate the operators of such
> entities to make sure that the same hashes are used. After all, the
> different-entity use-case will be relatively uncommon, in my opinion.
>


The problem that I see is that there are already wide spread
implementations of multiple fingerprint matching. I have an issue with
proposing substantialy different and stricter fingerprint matching
algorithm which can break connections that are working with current
implementation without providing a safe migration path.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure"><br></div></div><div class=3D"gmail_quote">On Tue, May 17, 2016 at 10:=
41 AM, Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.h=
olmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-col=
or:rgb(204,204,204);padding-left:1ex">





<div>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">The problem pe=
ople seem to have is mandating the same set of hashes, in case they are cal=
culated by different entities.<br>
<br>
I think the question is whether we could mandate the operators of such enti=
ties to make sure that the same hashes are used. After all, the different-e=
ntity use-case will be relatively uncommon, in my opinion.<br></div></div><=
/div></div></blockquote><div><br></div><div><br></div><div>The problem that=
 I see is that there are already wide spread implementations of multiple fi=
ngerprint matching. I have an issue with proposing substantialy different a=
nd stricter fingerprint matching algorithm which can break connections that=
 are working with current implementation without providing a safe migration=
 path.</div><div><br></div><div>Regards,</div><div><div class=3D"gmail_sign=
ature">_____________<br>Roman Shpount</div></div><div>=C2=A0</div></div></d=
iv></div>

--089e0111bc56c7aa1205330ad597--


From nobody Tue May 17 07:57:20 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D54F12D17D for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qumA00YNxt-Q for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 07:57:17 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55BF912D113 for <mmusic@ietf.org>; Tue, 17 May 2016 07:57:17 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-18-573b314b73c7
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 79.22.12516.B413B375; Tue, 17 May 2016 16:57:15 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0248.002; Tue, 17 May 2016 16:57:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
Thread-Index: AdGnZCVIPuCmi8SsThq6Wzb8nWVtrgCECuuAACIuHAAAEAcJgAAcm3kAABYCbgAABJ0RAAADoiEAAAu+T4D///v1gIAAPf4AgAANvICAADb9AIAA/pYAgAA9oAD//9L4gIAAM4qA///TsQCAAAtjgIAA4pmA//79aEAARlaVAP/+/rfw//2lAID/+zaagP/2IoYA/+vWN4D/1nZlIP+rhurA/1YB9AD+q6+DgP1XhWkA+q7/doD1XfxQAOq70OvY1XfBbACq717iZg==
Date: Tue, 17 May 2016 14:57:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCF506@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAMvTgcdPsuMRKk1OS7ua6T6gqgQ6qQd9BXYGEeMUaGBg_C82fQ@mail.gmail.com> <CABkgnnVjysSRftJWOHNf4nLBGikft3yK+sxH3S5hVjCzksZd9Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCF3F9@ESESSMB209.ericsson.se>, <CAD5OKxtM59u8qzF7fS4ws34crkRGbM5v6WjFvQJ4K_0R67Dh-Q@mail.gmail.com>
In-Reply-To: <CAD5OKxtM59u8qzF7fS4ws34crkRGbM5v6WjFvQJ4K_0R67Dh-Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FCF506ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLIsWRmVeSWpSXmKPExsUyM2K7sa63oXW4wbSn0hY3579lsbh25h+j xdTlj1ksVmw4wGox48JUZgdWj7/vPzB57Jx1l91jyZKfTB63phQEsERx2aSk5mSWpRbp2yVw ZbybPI+54K92xeLGFpYGxpVqXYycHBICJhL7Xk1jgrDFJC7cW8/WxcjFISRwhFFi6tG7jBDO EkaJjQvuAVVxcLAJWEh0/9MGaRARUJX4+30yWDOzwDJGiZ3veEBsYQFPieunP7NB1HhJXJi6 gB1kjojAPCaJg/M/soAkWICadyybxwxi8wr4SqyeM5kVYtlFXommD9NZQJZxCgRKbFzmC1LD CHTd91NroJaJSzR9WckKcbWAxJI955khbFGJl4//sULU5Eus+riaEWK+oMTJmU9YJjCKzELS PgtJ2SwkZRBxA4kv729D2doSyxa+Zoaw9SW6359mQhZfwMi+ilG0OLW4ODfdyFgvtSgzubg4 P08vL7VkEyMwEg9u+a27g3H1a8dDjAIcjEo8vA+crMKFWBPLiitzDzFKcDArifBW61uHC/Gm JFZWpRblxxeV5qQWH2KU5mBREuf1f6kYLiSQnliSmp2aWpBaBJNl4uCUamBkvcgybYdk3N47 4a/yljw+Z1i+q7X5GMfSlPlnmBQ2/D/GcP8W+67nT91Tm86s22sSWsyW1FlzpLVzD/vq4iZO 0bCb31f0n1lz+aejkuVVn9cVs65//bfgyxVzp4uN/2LMV6oFLt5y87jgmrWcO+Ri4tptMnjr 2huctDkPXZZ/ZneFPfCxss9fJZbijERDLeai4kQAQ8bCM8ACAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/U9wKb7U3pdQ5zuXRv0WsYEJnJv0>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 14:57:19 -0000

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

Hi,

How would making stricter rules make existing implementations to fail? They=
 would match whatever they match, and things should work :)

And, we can never mandate the receiver to match all hashes, because there m=
ay be hash functions that the receiver doesn't support to begin with.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Roman Shpount<mailto:roman@telurix.com>
Sent: =FD17/=FD05/=FD2016 17:48
To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>
Cc: Martin Thomson<mailto:martin.thomson@gmail.com>; Kevin Dempsey<mailto:k=
evindempsey70@gmail.com>; mmusic@ietf.org<mailto:mmusic@ietf.org>; Paul Kyz=
ivat<mailto:pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01


On Tue, May 17, 2016 at 10:41 AM, Christer Holmberg <christer.holmberg@eric=
sson.com<mailto:christer.holmberg@ericsson.com>> wrote:
The problem people seem to have is mandating the same set of hashes, in cas=
e they are calculated by different entities.

I think the question is whether we could mandate the operators of such enti=
ties to make sure that the same hashes are used. After all, the different-e=
ntity use-case will be relatively uncommon, in my opinion.


The problem that I see is that there are already wide spread implementation=
s of multiple fingerprint matching. I have an issue with proposing substant=
ialy different and stricter fingerprint matching algorithm which can break =
connections that are working with current implementation without providing =
a safe migration path.

Regards,
_____________
Roman Shpount


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
</head>
<body>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
How would making stricter rules make existing implementations to fail? They=
 would match whatever they match, and things should work :)<br>
<br>
And, we can never mandate the receiver to match all hashes, because there m=
ay be hash functions that the receiver doesn't support to begin with.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:roman@telurix.com">Roman Shpount</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD17=
/=FD05/=FD2016 17:48</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a></span><b=
r>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:martin.thomson@gmail.com">Martin Thomson</a>;
<a href=3D"mailto:kevindempsey70@gmail.com">Kevin Dempsey</a>; <a href=3D"m=
ailto:mmusic@ietf.org">
mmusic@ietf.org</a>; <a href=3D"mailto:pkyzivat@alum.mit.edu">Paul Kyzivat<=
/a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01</span><br>
<br>
</div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div>
<div class=3D"gmail_signature"><br>
</div>
</div>
<div class=3D"gmail_quote">On Tue, May 17, 2016 at 10:41 AM, Christer Holmb=
erg <span dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; border=
-left-width:1px; border-left-style:solid; border-left-color:rgb(204,204,204=
); padding-left:1ex">
<div>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">The problem p=
eople seem to have is mandating the same set of hashes, in case they are ca=
lculated by different entities.<br>
<br>
I think the question is whether we could mandate the operators of such enti=
ties to make sure that the same hashes are used. After all, the different-e=
ntity use-case will be relatively uncommon, in my opinion.<br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>The problem that I see is that there are already wide spread implement=
ations of multiple fingerprint matching. I have an issue with proposing sub=
stantialy different and stricter fingerprint matching algorithm which can b=
reak connections that are working
 with current implementation without providing a safe migration path.</div>
<div><br>
</div>
<div>Regards,</div>
<div>
<div class=3D"gmail_signature">_____________<br>
Roman Shpount</div>
</div>
<div>&nbsp;</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B37FCF506ESESSMB209erics_--


From nobody Tue May 17 08:24:23 2016
Return-Path: <bo.burman@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 334CB12D9A0 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 08:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxt3mjX77qEw for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 08:24:18 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C389B12D99F for <mmusic@ietf.org>; Tue, 17 May 2016 08:24:17 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-9d-573b379f309b
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 74.B8.27088.F973B375; Tue, 17 May 2016 17:24:15 +0200 (CEST)
Received: from ESESSMB105.ericsson.se ([169.254.5.102]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0248.002; Tue, 17 May 2016 17:24:15 +0200
From: Bo Burman <bo.burman@ericsson.com>
To: Colin Perkins <csp@csperkins.org>, Ben Campbell <ben@nostrum.com>
Thread-Topic: [MMUSIC] 3GPP liaison statement to IETF MMUSIC
Thread-Index: AdEgVjTQP0ysnwK+SH+nGn5PSW/tHgMF9TSAH/xJVAAA+5R+oA==
Date: Tue, 17 May 2016 15:24:15 +0000
Message-ID: <BBE9739C2C302046BD34B42713A1E2A22EB40A2D@ESESSMB105.ericsson.se>
References: <BBE9739C2C302046BD34B42713A1E2A22E874B3B@ESESSMB105.ericsson.se> <7732AC53-DCF8-4FD1-9EA2-0CB27FA3A6A2@nostrum.com> <B7BDC47B-D091-402C-9148-7F83CD0227B2@csperkins.org>
In-Reply-To: <B7BDC47B-D091-402C-9148-7F83CD0227B2@csperkins.org>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprEIsWRmVeSWpSXmKPExsUyM2K7iu58c+twg2dLbCzmd55mt1j+8gSj xdTlj1kcmD2m3b/P5rFkyU8mj1k7n7AEMEdx2aSk5mSWpRbp2yVwZSz+/46p4Jt2xep5G5ga GJ9odTFyckgImEjcvfKfCcIWk7hwbz1bFyMXh5DAEUaJxy/+QDlLGCVW/2hkBKliE9CQmL/j LpgtIuAq8XziMWYQm1kgSOJox0xWEFtYwFrizuEDbBA1NhLtV9azQ9hOEj27X4P1sgioSpzb vxWshlfAV+LF+oVQy3YySry/cAOsiFPAUeL97tdgRYwCshL3v99jgVgmLnHryXyoswUkluw5 zwxhi0q8fPyPFcJWkvix4RJQPQdQvabE+l36EK2KElO6H7JD7BWUODnzCcsERrFZSKbOQuiY haRjFpKOBYwsqxhFi1OLk3LTjYz0Uosyk4uL8/P08lJLNjECY+rglt8GOxhfPnc8xCjAwajE w/vAySpciDWxrLgy9xCjBAezkghvpZl1uBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFe/5eK4UIC 6YklqdmpqQWpRTBZJg5OqQbGycfnOtVsn+o6xan3hM3TOTJXp3e4C5/n6d5prvC7kv/WKrNX a+VuMbw79mxm9P0b8zcZ/9o1fZK/e9rORRV5n/JknGKTHqxPkmzomeu/c8+nvteZMZvl9s2M nODLKTH5pOzGbPcn3+5/+1myuJiz2D/aY+PS54s9hO+7HBUMOf//8FMuvbPbziixFGckGmox FxUnAgCWfp0NpQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/yoyrAID34__exwoo6wrbjiRLPig>
Cc: mmusic <mmusic@ietf.org>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: Re: [MMUSIC] 3GPP liaison statement to IETF MMUSIC
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 15:24:22 -0000

VGhhbmsgeW91IGZvciB0aGUgcmV2aWV3IENvbGluIQ0KDQpJIHRoaW5rIHRoaXMgaXMgc3VmZmlj
aWVudCBpbmZvcm1hdGlvbiBmb3IgYSBsaWFpc29uIHJlc3BvbnNlLg0KDQpNTVVTSUMsIEkgd291
bGQgbGlrZSB0byBwcm92aWRlIDNHUFAgVFNHIFNBIFdHNCB3aXRoIGEgcmVzcG9uc2UgbGlhaXNv
biB3ZWxsIGluIHRpbWUgZm9yIHRoZWlyIG5leHQgbWVldGluZyBpbiBKdW5lLCBzbyBwbGVhc2Ug
cHJvdmlkZSBhbnkgZnVydGhlciBjb21tZW50cyBpbiB0d28gd2Vla3MsIGJlZm9yZSBDT0IgVVRD
IE1heSAzMS4NCg0KQm8NCk1NVVNJQyBjby1jaGFpcg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+IEZyb206IENvbGluIFBlcmtpbnMgW21haWx0bzpjc3BAY3NwZXJraW5zLm9yZ10N
Cj4gU2VudDogZGVuIDEyIG1haiAyMDE2IDE5OjAyDQo+IFRvOiBCZW4gQ2FtcGJlbGwNCj4gQ2M6
IEJvIEJ1cm1hbjsgbW11c2ljOyBHb256YWxvIENhbWFyaWxsbw0KPiBTdWJqZWN0OiBSZTogW01N
VVNJQ10gM0dQUCBsaWFpc29uIHN0YXRlbWVudCB0byBJRVRGIE1NVVNJQw0KPiANCj4gQm8sIEJl
biwNCj4gDQo+IEnigJl2ZSByZXZpc2VkIHRoaXMgbGlhaXNvbiBzdGF0ZW1lbnQsIGFuZCB0aGUg
YXR0YWNoZWQgM0dQUCBUUiAyNi45MjQgVjEzLjAuMCwgYXQgdGhlIGNoYWly4oCZcyByZXF1ZXN0
LiBJIGRvIG5vdCBmb2xsb3cgdGhlDQo+IHdvcmsgaW4gM0dQUCBjbG9zZWx5LCBidXQgSSB1bmRl
cnN0YW5kIHRoYXQgU0RQIGF0dHJpYnV0ZS1iYXNlZCBhcHByb2FjaGVzLCBzdWNoIGFzIHNvbHV0
aW9ucyBEIGFuZCBGIGluIHRoZSBUUiwgYXJlDQo+IGJlaW5nIGNvbnNpZGVyZWQgZm9yIGZ1cnRo
ZXIgZGV2ZWxvcG1lbnQuDQo+IA0KPiBPZiB0aGUgYWx0ZXJuYXRpdmVzIHByb3Bvc2VkLCBJIGJl
bGlldmUgdGhhdCB1c2Ugb2YgYW4gU0RQIGF0dHJpYnV0ZSAoaS5lLiwgYW4g4oCcYT3igJ0gbGlu
ZSkgaXMgdG8gYmUgcHJlZmVycmVkIG92ZXIgdXNlIG9mDQo+IGZ1cnRoZXIgZXh0ZW5zaW9ucyB0
byBTRFAg4oCcYj3igJwgbGluZXMuIEF0dHJpYnV0ZXMgYXJlIHRoZSBuYXR1cmFsIGV4dGVuc2lv
biBwb2ludCBmb3IgU0RQLCBhbmQgb2ZmZXIgZmxleGliaWxpdHkgdGhhdCBpcyBub3QNCj4gcHJl
c2VudCBpbiDigJxiPeKAnCBsaW5lcy4gVGhpcyBpcyBjb21wYXRpYmxlIHdpdGggdGhlIHNvbHV0
aW9ucyBwcm9wb3NlZCBieSAzR1BQLg0KPiANCj4gV2hldGhlciBhbnkgbmV3IGF0dHJpYnV0ZSBp
cyBzaWduYWxsZWQgcGVyIFJUUCBwYXlsb2FkIHR5cGUsIGFzIGluIHNvbHV0aW9uIEQsIG9yIHBl
ciBtPSBsaW5lLCBhcyBpbiBzb2x1dGlvbiBGLCBpcyBhIG1vcmUNCj4gY29tcGxleCBpc3N1ZS4g
TmVpdGhlciBzZWVtcyB1bnJlYXNvbmFibGUgb24gdGhlIHN1cmZhY2UsIGFuZCBhIFFvUyBhdHRy
aWJ1dGUgcGVyIOKAnG094oCcIGxpbmUgaXMgbmF0dXJhbCBpZiBlYWNoIOKAnG094oCcIGxpbmUN
Cj4gcmVwcmVzZW50cyBhIHNpbmdsZSBtZWRpYSBzZW50IG9uIGEgc2luZ2xlIHBvcnQsIHdpdGgg
dGhlIG9mZmVyL2Fuc3dlciBleGNoYW5nZSBiZWluZyB1c2VkIG9ubHkgdG8gc2VsZWN0IHdoYXQg
ZW5jb2RpbmcNCj4gaXMgdXNlZCBmb3IgdGhhdCBtZWRpYS4NCj4gDQo+IEhvd2V2ZXIsIHdpdGgg
dGhlIGRlZmluaXRpb24gYW5kIHdpZGVzcHJlYWQgYWRvcHRpb24gb2YgdGhlIFNEUCBCVU5ETEUg
ZXh0ZW5zaW9uLCB0aGUgYXNzdW1wdGlvbiB0aGF0IGEgc2luZ2xlIOKAnG094oCcDQo+IGxpbmUg
cmVwcmVzZW50cyBhIHNpbmdsZSB0eXBlIG9mIG1lZGlhIGJlaW5nIHNlbnQgb24gYSBzaW5nbGUg
VURQIHBvcnQgaXMgYmVjb21pbmcgbGVzcyB0ZW5hYmxlLiBJIHdvdWxkIHVyZ2UgM0dQUCB0bw0K
PiBjb25zaWRlciB0aGUgaW1wYWN0IG9mIHRoZSBCVU5ETEUgZXh0ZW5zaW9uIG9uIHRoZWlyIGNo
b2ljZSwgYW5kIHRvIGZ1cnRoZXIgY29vcmRpbmF0ZSB3aXRoIElFVEYgdG8gZW5zdXJlIHRoYXQN
Cj4gd2hhdGV2ZXIgaXMgZGV2ZWxvcGVkIGlzIGNvbXBhdGlibGUgd2l0aCBTRFAgc2Vzc2lvbnMg
d2hlcmUgbXVsdGlwbGUg4oCcbT3igJwgbGluZXMsIHJlcHJlc2VudGluZyBzZXZlcmFsIGRpZmZl
cmVudCB0eXBlcw0KPiBvZiBtZWRpYSwgYXJlIHNlbnQgb24gYSBzaW5nbGUgVURQIHBvcnQuDQo+
IA0KPiBDb2xpbg0KPiANCj4gDQo+IA0KPiA+IE9uIDEgRGVjIDIwMTUsIGF0IDIxOjI1LCBCZW4g
Q2FtcGJlbGwgPGJlbkBub3N0cnVtLmNvbT4gd3JvdGU6DQo+ID4NCj4gPiBEb2VzIGFueW9uZSBo
YXZlIHRob3VnaHRzIG9uIHRoaXM/DQo+ID4NCj4gPiBUaGFua3MhDQo+ID4NCj4gPiBCZW4uDQo+
ID4NCj4gPiBPbiAxNiBOb3YgMjAxNSwgYXQgNDoyNiwgQm8gQnVybWFuIHdyb3RlOg0KPiA+DQo+
ID4+IE1NVVNJQyBtZW1iZXJzLA0KPiA+Pg0KPiA+PiBXZSBoYXZlIHJlY2VpdmVkIGEgbGlhaXNv
biBzdGF0ZW1lbnQgZnJvbSB0aGUgM0dQUCBUU0cgU0EgV0c0IGdyb3VwLg0KPiA+Pg0KPiA+PiBC
cmllZmx5IHN1bW1hcml6aW5nIHRoZSBhdHRhY2hlZCBkb2N1bWVudCwgdGhleSBoYXZlIGJlZW4g
c3R1ZHlpbmcgcmVzb3VyY2UgYWxsb2NhdGlvbiBhdCBzZXNzaW9uIHNldHVwIGFuZCBoYXZlDQo+
IGZvdW5kIGxhY2sgb2YgYmFuZHdpZHRoIGluZm9ybWF0aW9uIGVsZW1lbnRzIGFuZCBsYWNrIG9m
IGVuZC10by1lbmQgYWxpZ25tZW50IHRoYXQgY2FuIHJlc3VsdCBpbiBpbmNvbnNpc3RlbnQgc2V0
dGluZyBvZg0KPiBRb1MgcGFyYW1ldGVycyBpbiAzR1BQIG5ldHdvcmtzLiBUaGV5IGhhdmUgYWxz
byBkb2N1bWVudGVkIHRoZSBwcm9ibGVtIGFuYWx5c2lzIGFuZCBwb3RlbnRpYWwgc29sdXRpb25z
IGluIGENCj4gKHB1YmxpY2x5IGFjY2Vzc2libGUpIHRlY2huaWNhbCByZXBvcnQuDQo+ID4+DQo+
ID4+IFRoZXkgd291bGQgbGlrZSBNTVVTSUMgdG8gY29uc2lkZXIgdGhlaXIgd29yayBhbmQgd2Fu
dCB1cyB0byBwcm92aWRlIGZlZWRiYWNrIG9uIHdoZXRoZXIgd2Ugd291bGQgbGlrZSB0byBiZQ0K
PiBpbnZvbHZlZCBpbiB0aGUgY29vcmRpbmF0aW9uIG9mIGZ1dHVyZSB3b3JrIG9uIHRoaXMgdG9w
aWMuDQo+ID4+DQo+ID4+IEZvciBkZXRhaWxzLCBwbGVhc2Ugc2VlIHRoZSBhdHRhY2hlZCBsaWFp
c29uIGRvY3VtZW50Lg0KPiA+Pg0KPiA+PiBDaGVlcnMsDQo+ID4+IC9Cbw0KPiA+Pg0KPiA+PiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+Pg0KPiA+PiBUaXRsZTogICAgICAg
ICAgICAgICAgICAgICAgTFMgb24gSW1wcm92ZWQgZW5kLXRvLWVuZCBRb1MgRW5oYW5jZW1lbnRz
IGZvciBNVFNJDQo+ID4+DQo+ID4+IFJlbGVhc2U6ICAgICAgICAgICAgICAgUmVsZWFzZSAxMw0K
PiA+Pg0KPiA+PiBXb3JrIEl0ZW06ICAgICAgICAgUU9TRTJFTVRTSQ0KPiA+Pg0KPiA+PiBTb3Vy
Y2U6ICAgICAgICAgICAgICAgICAzR1BQIFRTRyBTQSBXRzQNCj4gPj4NCj4gPj4gVG86ICAgICAg
ICAgICAgICAgICAgICAgICAgICBJRVRGIE1NVVNJQw0KPiA+Pg0KPiA+PiBDYzogICAgICAgICAg
ICAgICAgICAgICAgICAgIDNHUFAgVFNHIENUIFdHMSwgM0dQUCBUU0cgQ1QgV0czLCAzR1BQIFRT
RyBDVCBXRzQNCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+Pg0KPiA+PiBTdXNhbm5h
IEtvb2lzdHJhLCBFVFNJIE1DQw0KPiA+Pg0KPiA+PiAzR1BQIGxpYWlzb24gY28tb3JkaW5hdG9y
DQo+ID4+DQo+ID4+IEUtbWFpbDogM0dQUExpYWlzb25AZXRzaS5vcmc8bWFpbHRvOjNHUFBMaWFp
c29uQGV0c2kub3JnPiA8bWFpbHRvOjNHUFBMaWFpc29uQGV0c2kub3JnPg0KPiA+Pg0KPiA+PiBQ
bGVhc2UgY29uc2lkZXIgdGhlIGVudmlyb25tZW50YWwgaW1wYWN0IGJlZm9yZSBwcmludGluZyB0
aGlzIGUtbWFpbA0KPiA+Pg0KPiA+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KPiA+PiBtbXVzaWMgbWFpbGluZyBsaXN0DQo+ID4+IG1tdXNpY0BpZXRm
Lm9yZw0KPiA+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0K
DQo=


From nobody Tue May 17 08:26:33 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCE412B04E for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 08:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 T5u3h8mn43cd for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 08:26:30 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BBA512D172 for <mmusic@ietf.org>; Tue, 17 May 2016 08:26:30 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id f89so27870717ioi.0 for <mmusic@ietf.org>; Tue, 17 May 2016 08:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=xCRwIfjgLLlQzGy4paxGNGMHhzEWox4hlMbGRQJ2QK0=; b=c0xj8kPjpuQlcCLWU48XjHgw2vzgDfKKoa8ZtknJbjrjByVaD0gFoFUOZi/6B1/sST US42NPcMTQWxwG0iU6gnljk56X/Erj1QAxa01gkjIJ236hbt96YA+nYYoK1AdxwLIZ/4 zVla9fF4Swuk2f/qBicdlnwlCXXOxkRLSig08xbXteqy/H9Q24aa2nB8BZvLXdU6CNVF z2WXKBE7qi21ahNIFP85gQkB/V0uNwPgWNlI6Ds1o0P3YzoYklc54WbYNnr59Jx2hY8L guKF9PePXv1EcOcHUyMUSGt2IZBFMhoCwVovHnh5a87FbnnHylKAZw0SK8ucBucJjvRD 90hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=xCRwIfjgLLlQzGy4paxGNGMHhzEWox4hlMbGRQJ2QK0=; b=bM1yXSo7ykr1gfL0S7HMMRMQZ+zxAoFGYHV6j9TNf8EeSnknuGIexjrmJC+YXCUccY VJNsgeBGPI+8iu6u/wAKMZGjYncxE5HcyNamv5fQ4ZzkGF0o6VGYiXEnJAxURrxMjkrn NWbCtsY3W5Zaevvv75IotoiW6N+b1JM5xlb6QciV3RuxnGcz7GrVGr7EGbg642zy2eDN RmtKYAc8ZNa0ppobaNcMkpJ+lgkOjYdsAX5hmQHT9ApgZMW9D3PeNGF4sj+hB7+R4j0y wBawSABNHXatKH0Gj347BAJLjNBWpDRRudvTh4cB+LtkkYTZbe/m5RvTbKP/y93IIyxG WnSQ==
X-Gm-Message-State: AOPr4FXr7XxniQxY77DTRUojm0edAgD96WhK7ffqdY8uIgZPAeoGZp0TUbvN03YREGzkOYsB2V93BRMPHD4cDw==
MIME-Version: 1.0
X-Received: by 10.107.161.195 with SMTP id k186mr1618197ioe.190.1463498789451;  Tue, 17 May 2016 08:26:29 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 08:26:29 -0700 (PDT)
In-Reply-To: <CAD5OKxup32aeFn-GNF9h1MjK-EQashv-PhsjrutsTxMZ5_b5bQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAD5OKxup32aeFn-GNF9h1MjK-EQashv-PhsjrutsTxMZ5_b5bQ@mail.gmail.com>
Date: Tue, 17 May 2016 11:26:29 -0400
Message-ID: <CABkgnnU8Z-VsV4anAxcKBASG_WMqTYv-bEOHE+2pe_b1L6_Qnw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/NCtau7NjYhjcyY-tqwg7CiN1b0A>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 15:26:32 -0000

On 17 May 2016 at 10:45, Roman Shpount <roman@telurix.com> wrote:
> Let me try to explain this again:

It's not working.

> 1. There are multiple deployed current implementations that match multiple
> fingerprints (Firefox and Chrome come to mind)

No, we each only match one.

> 2. Your proposed a matching algorithm which is different and considerably
> stricter then existing implementations

Stricter and different aren't a problem unless you can say "in the
following legitimate scenario, things break"

> 3. You proposed solution provides no indication if your new matching
> algorithm is used or a clear migration path. If someone implements it,
> connections which worked yesterday will stop working tomorrow with no
> indication of the reason.

Again, I'm not seeing a situation where this is a problem.  Can you
give me a specific example?


From nobody Tue May 17 09:19:01 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33CCD12DA86 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 09:19:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XiFGNw1sRsP for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 09:18:58 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4AB412DA8D for <mmusic@ietf.org>; Tue, 17 May 2016 09:18:57 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id 190so29961164iow.1 for <mmusic@ietf.org>; Tue, 17 May 2016 09:18:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=dI8uOIPhiw3uTNxDT63lufvE61Jmyd0eof7Nx4fOQNY=; b=tZIAdKtIZTkIqDUxO1VEe6rfz3dxMDp9AUo9z4ENVhZMDhFDMiJdbDcx5mr+8rpKa/ byO/d5XnSH8/b1RrICNviP2PwY92HZz2agJ3mUpciEDTIS56L/2tokSbwIFb5XcoFNHp zOuxljCYcAtC/B3apdyuqCyz+74d6cKC5G1YoGAdVaWOARvbkbMBHWBKpBV7Jj5mXJU5 pRT70vAdeH6tnbwUKT5pD6QqDcq1QMafBGEklsIoWt3Rgnmp4fBArqtCCkJOCyDmSkmX ZbPX/v0snYckOAFhMYxvFAB5A42681lTzjFjItYy2Ss6flkco51alKS2xpGr+E/PM3Gn lCBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=dI8uOIPhiw3uTNxDT63lufvE61Jmyd0eof7Nx4fOQNY=; b=kmzZDCTle4AKCKzmY9aGkJfwOOwGUnomM+Gw7GZ+dKoEXGuFWiIKC8orTYWrPSIMT8 7E7PU+UdlppjZAZM4RFqgPXMX6MNrHZL0B3XtIZ6E5HriGcQVvvzz1Oqn2vbQg6AYcjX f2ft/CxijW4CT5MlmmUK+IZMDcfLYjywqIV8VNgiwf8405h9O7SHvd9W/6jAdHT52oxt g+fwesYZoQLN3bJgW/DIV578Si8QIon3TQfODiKcpqOeQCZQaf8L4+NnRTZOfi5a+pOM 7JEeHVj02gO7n77vybSjYTVqWClVh7B4HVsDMu/gHp8iPtXS6wmCkqhK3u/Rh7Ls9FKK evLw==
X-Gm-Message-State: AOPr4FVvBc37ngO9JPZ37Cm2jQMPn/IU80FfeNRXInSQMUKJXXOrowuXOc29/ShRRic7kw==
X-Received: by 10.36.68.82 with SMTP id o79mr14035046ita.75.1463501937183; Tue, 17 May 2016 09:18:57 -0700 (PDT)
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com. [209.85.213.182]) by smtp.gmail.com with ESMTPSA id m69sm1249918itg.22.2016.05.17.09.18.56 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 09:18:56 -0700 (PDT)
Received: by mail-ig0-f182.google.com with SMTP id bi2so77206470igb.0 for <mmusic@ietf.org>; Tue, 17 May 2016 09:18:56 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.136.228 with SMTP id qd4mr4015100igb.42.1463501935680; Tue, 17 May 2016 09:18:55 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 17 May 2016 09:18:55 -0700 (PDT)
In-Reply-To: <CABkgnnU8Z-VsV4anAxcKBASG_WMqTYv-bEOHE+2pe_b1L6_Qnw@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAD5OKxup32aeFn-GNF9h1MjK-EQashv-PhsjrutsTxMZ5_b5bQ@mail.gmail.com> <CABkgnnU8Z-VsV4anAxcKBASG_WMqTYv-bEOHE+2pe_b1L6_Qnw@mail.gmail.com>
Date: Tue, 17 May 2016 12:18:55 -0400
X-Gmail-Original-Message-ID: <CAD5OKxsDgOGHn401m5v-QVw4ykX8zb1h=18UZqroh7SdVt_7fQ@mail.gmail.com>
Message-ID: <CAD5OKxsDgOGHn401m5v-QVw4ykX8zb1h=18UZqroh7SdVt_7fQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122aa5601335605330c19e2
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/DRtMFEyZuFyNlH0QZbp929IdJQA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 16:19:01 -0000

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

I have double checked the code in Chromium and Firefox.

Chromium code is hard coded to only allow one fingerprint.

Firefox is going through the motions of supporting multiple fingerprints
but it does not look completely implemented.

At this point, since WebRTC browsers do not have a working multiple
fingerprint implementation, we can define whatever we want.

You have me convinced. Let's define that each certificate must provide the
same set of hash functions.

Do we still want to define the new attribute to address HEX encoding and
extensibility issues of a=fingerprint?

Regards,
_____________
Roman Shpount

On Tue, May 17, 2016 at 11:26 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 17 May 2016 at 10:45, Roman Shpount <roman@telurix.com> wrote:
> > Let me try to explain this again:
>
> It's not working.
>
> > 1. There are multiple deployed current implementations that match
> multiple
> > fingerprints (Firefox and Chrome come to mind)
>
> No, we each only match one.
>
> > 2. Your proposed a matching algorithm which is different and considerably
> > stricter then existing implementations
>
> Stricter and different aren't a problem unless you can say "in the
> following legitimate scenario, things break"
>
> > 3. You proposed solution provides no indication if your new matching
> > algorithm is used or a clear migration path. If someone implements it,
> > connections which worked yesterday will stop working tomorrow with no
> > indication of the reason.
>
> Again, I'm not seeing a situation where this is a problem.  Can you
> give me a specific example?
>

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

<div dir=3D"ltr">I have double checked the code in Chromium and Firefox.<di=
v><br></div><div>Chromium code is hard coded to only allow one fingerprint.=
</div><div><br></div><div>Firefox is going through the motions of supportin=
g multiple fingerprints but it does not look completely implemented.</div><=
div><br></div><div>At this point, since WebRTC browsers do not have a worki=
ng multiple fingerprint implementation, we can define whatever we want.</di=
v><div><br></div><div>You have me convinced. Let&#39;s define that each cer=
tificate must provide the same set of hash functions.</div><div><br></div><=
div>Do we still want to define the new attribute to address HEX encoding an=
d extensibility=C2=A0issues of a=3Dfingerprint?<br><div class=3D"gmail_extr=
a"><br></div><div class=3D"gmail_extra">Regards,<br clear=3D"all"><div><div=
 class=3D"gmail_signature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Tue, May 17, 2016 at 11:26 AM, Martin Tho=
mson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.com" targ=
et=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:=
1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left=
:1ex"><span class=3D"">On 17 May 2016 at 10:45, Roman Shpount &lt;<a href=
=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br>
&gt; Let me try to explain this again:<br>
<br>
</span>It&#39;s not working.<br>
<span class=3D""><br>
&gt; 1. There are multiple deployed current implementations that match mult=
iple<br>
&gt; fingerprints (Firefox and Chrome come to mind)<br>
<br>
</span>No, we each only match one.<br>
<span class=3D""><br>
&gt; 2. Your proposed a matching algorithm which is different and considera=
bly<br>
&gt; stricter then existing implementations<br>
<br>
</span>Stricter and different aren&#39;t a problem unless you can say &quot=
;in the<br>
following legitimate scenario, things break&quot;<br>
<span class=3D""><br>
&gt; 3. You proposed solution provides no indication if your new matching<b=
r>
&gt; algorithm is used or a clear migration path. If someone implements it,=
<br>
&gt; connections which worked yesterday will stop working tomorrow with no<=
br>
&gt; indication of the reason.<br>
<br>
</span>Again, I&#39;m not seeing a situation where this is a problem.=C2=A0=
 Can you<br>
give me a specific example?<br>
</blockquote></div><br></div></div></div>

--089e0122aa5601335605330c19e2--


From nobody Tue May 17 10:45:51 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3860012D7E3 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 10:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bmEbaaQ6aWNB for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 10:45:49 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1B8712D5BE for <mmusic@ietf.org>; Tue, 17 May 2016 10:45:48 -0700 (PDT)
Received: by mail-ig0-x234.google.com with SMTP id s8so13980147ign.0 for <mmusic@ietf.org>; Tue, 17 May 2016 10:45:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=+g/W0JOaLl0yGTWUZybT1crSGAkdCc38oBqykGRWWtM=; b=Or0dok9AUCTvm0G4oo3ZQ/KQmiGXhKzsCQfnzf8MUuA8WnyFO6e+76hVFIzQLDiVqd voNg6G5XOyF4gRqlRClcCS1cpyoUSxc0tAdrl+oWHV15I0441ChAhiOLhgb8HtA+d2pO fJup8tJz3bRWn++qBxUDEUSFw0uAylRmq4PvQaAymx9H4kGdaCoFew1TUU7WEb+UOjEy UUouGMJL9ZCNCC9F9DuQqou6/VwkSm+CvtsJruIzy0heEu479bq/GmH6xnQSxkuJkpXI nZI7pHwlxaXEBbenLIjUnRcUhFhCHgaS942zBqnLy3fsmjfmuN/Cg2tkjrYAzR6Lp8XN gJiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=+g/W0JOaLl0yGTWUZybT1crSGAkdCc38oBqykGRWWtM=; b=EkU2T4+uBA3AwkrF90cQO8K09jL6tZUcZOmDBhnL2Bydz5rOLkrPZvzSl8N515vaVM /w6sFuUax53D6rqCQtO+rJcRCdeDanLJfIwHkJHaCl+WPYcOM3cmqCoS0BJu5Z5cK79X fYI8rmzToTExsIJ6DZr5x9OYwN5UNCm7+OI0qZJYB2H+IKvsGNl+F5h5RJLPB1g08yf2 IHJ1afhXHBSVKEVy3QIb6P0qU92nNuQ3NaeIMXWlqKpHyfuTiM7eH2hx5UARxIhw+Jro rn4pBc2p2XX4N9ntkeChKsWGKFy1h74SofPNY3sb64NC0MH5VIlJv7MvjcGpGGLZmZAB bZew==
X-Gm-Message-State: AOPr4FUwfeCMFlEFc3svouseSz3JEMeYgie7mXRdaBMHjOFLGtlFZ5+KKiYs41OhMFJmc5z3RVYb5AsBct85YQ==
MIME-Version: 1.0
X-Received: by 10.50.33.81 with SMTP id p17mr15077420igi.58.1463507148335; Tue, 17 May 2016 10:45:48 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 10:45:48 -0700 (PDT)
In-Reply-To: <CAD5OKxsDgOGHn401m5v-QVw4ykX8zb1h=18UZqroh7SdVt_7fQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37F95326@ESESSMB209.ericsson.se> <D358DAF1.83DD%christer.holmberg@ericsson.com> <4bd46a05-5fee-3407-65b0-1587ae39ec5f@alum.mit.edu> <D35916D7.84B4%christer.holmberg@ericsson.com> <CAMvTgcd+yPcHier7wimeo-zpKk-vREpcuuwBGJe3M2suMUb2kw@mail.gmail.com> <D35A1FAC.8533%christer.holmberg@ericsson.com> <CAMvTgccUwkbrxJmQGp5wNCK1rnNeZdbGq2HuyjNcUyKUAZ0=xQ@mail.gmail.com> <D35A25F7.8546%christer.holmberg@ericsson.com> <CAMvTgcdUOuUodNwghyzyBK7C6HjjSjSCfuDASwkChphTiuW3rg@mail.gmail.com> <CABkgnnVs-YJFaTjU4YLAQhiBgurRZT_Bxei2n_SjCTM8sF9X1A@mail.gmail.com> <CAD5OKxsQaegyM=1SEh9TX8+7vB_Ho2L5TWOGXDAzNpkhLoF6ZA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FA224D@ESESSMB209.ericsson.se> <CAD5OKxsrNVab3jHcP1+2B+RXqgAVa1h4zBMgrWKbqw27_h-ScA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FAD061@ESESSMB209.ericsson.se> <7c2bc70a-3139-a703-a402-6e92a5c9b493@alum.mit.edu> <CABkgnnVAqweOhn3cGNCD6a9bxviiV3sQiUyTtHoq1VHB8NCVoQ@mail.gmail.com> <37c4b00f-c04e-212e-babb-599de13df3d0@alum.mit.edu> <CABkgnnXKoTrV2hw_j13_QRzxCkrkzkvUVKW13ZwXaDtCJ10RXw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FBF8A0@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B37FCB0FB@ESESSMB209.ericsson.se> <CABkgnnUCQYf6MROG4vc4hTn-f57B6nd73wXuVGD-yZGH-TK1Sg@mail.gmail.com> <D360ECF9.883D%christer.holmberg@ericsson.com> <CABkgnnUyY1BuRdme1hJ-T5b-j=PJkyB41vq=fgf8aXUU8SWFhA@mail.gmail.com> <CAD5OKxup32aeFn-GNF9h1MjK-EQashv-PhsjrutsTxMZ5_b5bQ@mail.gmail.com> <CABkgnnU8Z-VsV4anAxcKBASG_WMqTYv-bEOHE+2pe_b1L6_Qnw@mail.gmail.com> <CAD5OKxsDgOGHn401m5v-QVw4ykX8zb1h=18UZqroh7SdVt_7fQ@mail.gmail.com>
Date: Tue, 17 May 2016 13:45:48 -0400
Message-ID: <CABkgnnUAQ7=xqzZ5b3RF=EaoitG5rMJP6k0aNcod3EtKBr36OQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/oiMAlBeHZRy4TuSvcI8Eaa3PFeA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 17:45:50 -0000

On 17 May 2016 at 12:18, Roman Shpount <roman@telurix.com> wrote:
> Do we still want to define the new attribute to address HEX encoding and
> extensibility issues of a=fingerprint?


I've basically given up on those as not having high enough return on
investment.  Since you have to duplicate them in a=fingerprint for old
stuff, you don't save space half the time, and extensibility is a
feature you don't need until you have a concrete need.


From nobody Tue May 17 11:33:29 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD4E712DD1B for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 11:33:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jfNCnwgndU9W for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 11:33:27 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D31DA12DD2A for <mmusic@ietf.org>; Tue, 17 May 2016 11:32:52 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-ee-573b63d3168b
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 0E.E1.12926.3D36B375; Tue, 17 May 2016 20:32:51 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0248.002; Tue, 17 May 2016 20:32:50 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xQ==
Date: Tue, 17 May 2016 18:32:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHLMWRmVeSWpSXmKPExsUyM2K7qO7lZOtwgy8LhCyunfnHaDF1+WMW ixUbDrBazLgwldmBxePv+w9MHjtn3WX3WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBnfps9n KzghUPH+5FymBsYJAl2MHBwSAiYSk1bldTFyApliEhfurWcDsYUEjjBKvLvF3cXIBWQvYZS4 s+ccG0g9m4CFRPc/bZAaEYEgiefT5zOB2MwCvhLvf05nBykRFsiV2LbRF6IkT+LCnKfMELae RPejg2A2i4CqxMLZzxhBbF6g1vPtvWA2I9AJ30+tgRopLnHrCcR4CQEBiSV7zjND2KISLx// Y4WwlSRWbL/ECLKWWUBTYv0ufYhWRYkp3Q/ZIcYLSpyc+YRlAqPILCRTZyF0zELSMQtJxwJG llWMosWpxUm56UbGeqlFmcnFxfl5enmpJZsYgbFycMtv1R2Ml984HmIU4GBU4uF94GQVLsSa WFZcmXuIUYKDWUmEN8jTOlyINyWxsiq1KD++qDQntfgQozQHi5I4r/9LxXAhgfTEktTs1NSC 1CKYLBMHp1QDY4hTcs/Sg83ThbIzFx15l+dbn/T4a2rptKJjfxVYm3Z/WvrmrhXbvtakzA3u BhlyPV4/nbZsd7nya27mbav3xwRdF3yQXN56OkrlXNjnpo86NhUF+QxZi/jfRqs27qme+CDL 2Kjg7IEjPE3+y7reXQpbvuZB1Ksd8g+uTl/2oWV+xZ6w8n2z3ZVYijMSDbWYi4oTAWkrgweR AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/fy3LIKFFoiym3Q8Ohw62TBD_DMM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 18:33:29 -0000

SGksDQoNCi4uLg0KDQo+WW91IGhhdmUgbWUgY29udmluY2VkLiBMZXQncyBkZWZpbmUgdGhhdCBl
YWNoIGNlcnRpZmljYXRlIG11c3QgcHJvdmlkZSB0aGUgc2FtZSBzZXQgb2YgaGFzaCBmdW5jdGlv
bnMuDQoNCkF3ZXNvbWUhDQoNClNvLCBmb3IgdGhlIFNFTkRFUiwgd2Ugd291bGQgc2F5IHRoYXQg
aXQgTVVTVCBwcm92aWRlIHRoZSBzYW1lIHNldCBvZiBoYXNoIGZ1bmN0aW9ucyBmb3IgZWFjaCBj
ZXJ0aWZpY2F0ZS4NCg0KTm93LCB3aGF0IGRvIHdlIHNheSBmb3IgdGhlIFJFQ0VJVkVSIGFuZCB0
aGUgbWF0Y2hpbmc/IA0KDQo+RG8gd2Ugc3RpbGwgd2FudCB0byBkZWZpbmUgdGhlIG5ldyBhdHRy
aWJ1dGUgdG8gYWRkcmVzcyBIRVggZW5jb2RpbmcgYW5kIGV4dGVuc2liaWxpdHnCoGlzc3VlcyBv
ZiBhPWZpbmdlcnByaW50Pw0KDQpNeSBzdWdnZXN0aW9uIHdvdWxkIGJlIHRvIGxlYXZlIGl0IGZv
ciBub3csIGlmIHdlIGNhbiBhZ3JlZSBvbiBhIHNvbHV0aW9uIHdpdGhvdXQgaXQuIElmIG5lZWRl
ZCwgd2UgY2FuIGRvIGl0IGxhdGVyLCBpbiBhIHNlcGFyYXRlIGRyYWZ0Lg0KDQpSZWdhcmRzLA0K
DQpDaHJpc3Rlcg0KDQoNCg0KT24gVHVlLCBNYXkgMTcsIDIwMTYgYXQgMTE6MjYgQU0sIE1hcnRp
biBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+IHdyb3RlOg0KT24gMTcgTWF5IDIw
MTYgYXQgMTA6NDUsIFJvbWFuIFNocG91bnQgPHJvbWFuQHRlbHVyaXguY29tPiB3cm90ZToNCj4g
TGV0IG1lIHRyeSB0byBleHBsYWluIHRoaXMgYWdhaW46DQoNCkl0J3Mgbm90IHdvcmtpbmcuDQoN
Cj4gMS4gVGhlcmUgYXJlIG11bHRpcGxlIGRlcGxveWVkIGN1cnJlbnQgaW1wbGVtZW50YXRpb25z
IHRoYXQgbWF0Y2ggbXVsdGlwbGUNCj4gZmluZ2VycHJpbnRzIChGaXJlZm94IGFuZCBDaHJvbWUg
Y29tZSB0byBtaW5kKQ0KDQpObywgd2UgZWFjaCBvbmx5IG1hdGNoIG9uZS4NCg0KPiAyLiBZb3Vy
IHByb3Bvc2VkIGEgbWF0Y2hpbmcgYWxnb3JpdGhtIHdoaWNoIGlzIGRpZmZlcmVudCBhbmQgY29u
c2lkZXJhYmx5DQo+IHN0cmljdGVyIHRoZW4gZXhpc3RpbmcgaW1wbGVtZW50YXRpb25zDQoNClN0
cmljdGVyIGFuZCBkaWZmZXJlbnQgYXJlbid0IGEgcHJvYmxlbSB1bmxlc3MgeW91IGNhbiBzYXkg
ImluIHRoZQ0KZm9sbG93aW5nIGxlZ2l0aW1hdGUgc2NlbmFyaW8sIHRoaW5ncyBicmVhayINCg0K
PiAzLiBZb3UgcHJvcG9zZWQgc29sdXRpb24gcHJvdmlkZXMgbm8gaW5kaWNhdGlvbiBpZiB5b3Vy
IG5ldyBtYXRjaGluZw0KPiBhbGdvcml0aG0gaXMgdXNlZCBvciBhIGNsZWFyIG1pZ3JhdGlvbiBw
YXRoLiBJZiBzb21lb25lIGltcGxlbWVudHMgaXQsDQo+IGNvbm5lY3Rpb25zIHdoaWNoIHdvcmtl
ZCB5ZXN0ZXJkYXkgd2lsbCBzdG9wIHdvcmtpbmcgdG9tb3Jyb3cgd2l0aCBubw0KPiBpbmRpY2F0
aW9uIG9mIHRoZSByZWFzb24uDQoNCkFnYWluLCBJJ20gbm90IHNlZWluZyBhIHNpdHVhdGlvbiB3
aGVyZSB0aGlzIGlzIGEgcHJvYmxlbS7CoCBDYW4geW91DQpnaXZlIG1lIGEgc3BlY2lmaWMgZXhh
bXBsZT8NCg0K


From nobody Tue May 17 11:47:14 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B52112D8AA for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 11:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ik0Wz4D-ccZ for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 11:47:12 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BD2812D69F for <mmusic@ietf.org>; Tue, 17 May 2016 11:47:12 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id x201so39839553oif.3 for <mmusic@ietf.org>; Tue, 17 May 2016 11:47:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=qOdO6RVGAkbgwsfGRlCY/2zGxzfr1U8WRJ55BMZ7+Ts=; b=uMtqjpAklLyXb86qUuN8NS69akWTR9Q3qbPhtu2GeGeDMr+UWj8rJY017Tbwlj9hBS 0heOKLZiZzqDvQKQt88cFJ1GpF8J6jG+PRlIBY+2mQo4HaepN5lPlGR7Iy+Qk9PnJIGu 8tIoIazM/AVhPYPor+K53XYTf297o8iOiwu7VllOk34P8p+YS23eyyyj2vnpMBb1mmYu 9EDISUCvGjOk0JKqdUOYhQcvkHgy+sWNl8Fr7fCyrXsMecvghxl6TUT50mFXD/ICRNgD LmdO86Yr0ULzpr4oY3JC7uC/SRxDKrPgl7+tMFLqIDCqcs8/wqKM6BcV7AS0uiATrED3 aD1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=qOdO6RVGAkbgwsfGRlCY/2zGxzfr1U8WRJ55BMZ7+Ts=; b=bP+FLwE8AtF0aZzaygGt1yXYAdQsQhqked3MisMvkGKSSPPjTEOvIR2xqXcb6GbnLf Qux9GCSfWwPik0tPI1av/LFQiwqP/BBOoCu7d59EdV8gQ0nTxC7HPxow+K/kclyaRtQS bQZJwodakWMOT9BfTIwuqoCwwseTKxmRB7Eo4/dNasnOzKO1jnHojvmNnOVX2sl0oztg i8dzKeQn7rFIKmDKLZQIiJaEAIgPdb1wgNXl077RrT4Caxd3ZAXB531tY3mD8c9jd8sM zN5VtFi+NxM13/QZHnhoNOlp+u6xt5mc3JBxToRlXaXzT36oLt03FQutzfwf0EkiI18+ boHw==
X-Gm-Message-State: AOPr4FWpEoMeLErBURg/Oe3pCVPH4/uklo9Vgw0TgR+lgvXhRUFYrXRH7t1krJ/jh1PsKw==
X-Received: by 10.157.35.225 with SMTP id t88mr1759714otb.18.1463510831669; Tue, 17 May 2016 11:47:11 -0700 (PDT)
Received: from mail-io0-f170.google.com (mail-io0-f170.google.com. [209.85.223.170]) by smtp.gmail.com with ESMTPSA id 95sm1121695oth.10.2016.05.17.11.47.10 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 11:47:11 -0700 (PDT)
Received: by mail-io0-f170.google.com with SMTP id 190so35451921iow.1 for <mmusic@ietf.org>; Tue, 17 May 2016 11:47:10 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.147.7 with SMTP id v7mr2269392iod.3.1463510830688; Tue, 17 May 2016 11:47:10 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 17 May 2016 11:47:10 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se>
Date: Tue, 17 May 2016 14:47:10 -0400
X-Gmail-Original-Message-ID: <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com>
Message-ID: <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c055f683030e705330e2bc6
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/O6cqeE9RtJfnOJ2m9UJI5EUu_qY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 18:47:13 -0000

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

On Tue, May 17, 2016 at 2:32 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >You have me convinced. Let's define that each certificate must provide
> the same set of hash functions.
>
> Awesome!
>
> So, for the SENDER, we would say that it MUST provide the same set of hash
> functions for each certificate.
>
> Now, what do we say for the RECEIVER and the matching?
>
>
Should match either all fingerprints or the most secure hash function
present and in SDP and supported by the end point.
_____________
Roman Shpount

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br clear=3D"all"><div><div=
 class=3D"gmail_signature"><br></div></div><div class=3D"gmail_quote">On Tu=
e, May 17, 2016 at 2:32 PM, Christer Holmberg <span dir=3D"ltr">&lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:=
solid;border-left-color:rgb(204,204,204);padding-left:1ex">&gt;You have me =
convinced. Let&#39;s define that each certificate must provide the same set=
 of hash functions.<br>
<br>
Awesome!<br>
<br>
So, for the SENDER, we would say that it MUST provide the same set of hash =
functions for each certificate.<br>
<br>
Now, what do we say for the RECEIVER and the matching?<br><br></blockquote>=
<div><br></div><div>Should match either all fingerprints or the most secure=
 hash function present and in SDP and supported by the end point.</div><div=
><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><=
div>=C2=A0</div></div></div></div>

--94eb2c055f683030e705330e2bc6--


From nobody Tue May 17 12:44:01 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB9D12DD7E for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24h9qL9U4k69 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:43:58 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5BE112DD7D for <mmusic@ietf.org>; Tue, 17 May 2016 12:43:57 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id f89so37537129ioi.0 for <mmusic@ietf.org>; Tue, 17 May 2016 12:43:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=ZDrmTLpidVTw1ebakIwSIx+U6nwxnbbl71SMpfhF9pE=; b=sXhcfbCtDCLxYmB3nWOr9X0z7U6n0BL4WI8AxyJ9FlvW9I0rmM+LMhLWJPJ9uN1UNx o69Y7PKt9KrLLU7OzqWH0W6xEw9rjYqADPnvpZjHJ7cXdf/RjDI/uV8de2Z6/VLDUAMa k3OOgAlSJSWnSTB4KwxnOs3mdIkrkLwLhGPSSUazpw5lWHxqL0eSb/ShQRQ/FOdVzTDx oipuhn8qWJcXxFWQ8KDFK1noCMauDgOxnR/S2J9YoujSEy1gNv8GMHAuTGELG6M4sLxS oVntncnEiE+IfL1dYMzzTYxu5W1goWjxC62sWah/NxoJkHXcfx6Bb8uVjs8M654tKYht GYOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=ZDrmTLpidVTw1ebakIwSIx+U6nwxnbbl71SMpfhF9pE=; b=WIMFCodzIyvc+PB4hhs2UZULt3ySPzryyuXelE+/6TgG3i3USw4E9ZqOgnihlVI/jD +DWN/dOVPZympvtkds5Xsomhx5wPhyWirWr3PXimxDPFLaMg+Tum9fuxzh5Y/2uOBCtZ 4LzbZszzAjBPas0872OPPd05wa9vNtWLT/2RfrG96t1fKNvyGiE4XNb2O0SRHd6Akttn jGqc6UstEkF6Onb6xwlxoBjNe+KEDRk3O9Ioi4uV2FnaNny/iXjA0ZupZiD8NdWXLjyN TLDQBcW9tk1weoet7qfi/5/jVEGKHMWrVkvDWk7Rt0iidOrEjSF+ArZsng71lDcDXC77 S0kg==
X-Gm-Message-State: AOPr4FVEzr1yPnmCv7w10qHDd2A8U0BMGhI28bRh6Z94RrGZjV3LAfDZSCOMxRVuaqDJPe8zJpzGDM3r38L5UA==
MIME-Version: 1.0
X-Received: by 10.107.161.195 with SMTP id k186mr2583252ioe.190.1463514237317;  Tue, 17 May 2016 12:43:57 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 12:43:57 -0700 (PDT)
In-Reply-To: <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com>
Date: Tue, 17 May 2016 15:43:57 -0400
Message-ID: <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/TmS3dkJg2ljd4BIUb8IlGcHrPsU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 19:43:59 -0000

On 17 May 2016 at 14:47, Roman Shpount <roman@telurix.com> wrote:
> Should match either all fingerprints or the most secure hash function
> present and in SDP and supported by the end point.

WFM, we might add "MAY additionally check other hash functions", but
one match is the ideal


From nobody Tue May 17 12:52:43 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 594C312D969 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sKNNY6rUG3vn for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:52:40 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66C9C12DD7F for <mmusic@ietf.org>; Tue, 17 May 2016 12:52:40 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-ae-573b76862bb5
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 40.CF.18043.6867B375; Tue, 17 May 2016 21:52:38 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0248.002; Tue, 17 May 2016 21:52:15 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwA==
Date: Tue, 17 May 2016 19:52:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com>
In-Reply-To: <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsUyM2J7oG5bmXW4wcS5JhbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsEroxTL2sL drBU7J86hb2BcQVLFyMnh4SAicSvaRsYIWwxiQv31rOB2EICRxglJq7P72LkArKXMEq8uXcR KMHBwSZgIdH9TxukRkQgSOLhw8dgc5gFfCXe/5zODlIiLJArsW2jL0RJnsSFOU+ZIWwniUuN j1hBbBYBVYl/zfdYQMp5gVr/dThBbLrNKHH/axPYSE6BQImuzqdgpzECnfb91BomiFXiEree zGeCOFlAYsme88wQtqjEy8f/WCFsJYkV2y8xgsxnFtCUWL9LH6JVUWJK90N2EJtXQFDi5Mwn LBMYxWYhmToLoWMWko5ZSDoWMLKsYhQtTi0uzk03MtJLLcpMLi7Oz9PLSy3ZxAiMrYNbflvt YDz43PEQowAHoxIP7wMnq3Ah1sSy4srcQ4wSHMxKIrxV6dbhQrwpiZVVqUX58UWlOanFhxil OViUxHn9XyqGCwmkJ5akZqemFqQWwWSZODilGhizA1/PlZ5of9L4QHI9t/cdR651nSm79Rv5 D1xo+n/1lv4bYf4/PdNF/yyx5U/KrChbLjBt86tUeevGt468f4sOOgv2J/K/P9I/Nfly5tNI 3YUOOSy3ONdPXrvpw4YzjcceKlu+O9/jnHtrnhTfOn7Jzr4C18szw1p8wnrDX+1zlM3/JNT+ jlmJpTgj0VCLuag4EQBBscccqQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/HXNfL2RXd8OjbKP-E_0v8Lnuu5I>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 19:52:42 -0000

SGksDQoNCj4+IFNob3VsZCBtYXRjaCBlaXRoZXIgYWxsIGZpbmdlcnByaW50cyBvciB0aGUgbW9z
dCBzZWN1cmUgaGFzaCBmdW5jdGlvbiANCj4+IHByZXNlbnQgYW5kIGluIFNEUCBhbmQgc3VwcG9y
dGVkIGJ5IHRoZSBlbmQgcG9pbnQuDQo+DQo+IFdGTSwgd2UgbWlnaHQgYWRkICJNQVkgYWRkaXRp
b25hbGx5IGNoZWNrIG90aGVyIGhhc2ggZnVuY3Rpb25zIiwgYnV0IG9uZSBtYXRjaCBpcyB0aGUg
aWRlYWwNCg0KSSBndWVzcyB3ZSB3b3VsZCBzYXkgImNvbnNpZGVyZWQgbW9zdCBzZWN1cmUgYnkg
dGhlIGVuZHBvaW50IiwgYmVjYXVzZSBJIGRvbid0IHRoaW5rIHdlIHdhbnQgdG8gZGVmaW5lIHdo
YXQgaGFzaCBmdW5jdGlvbnMgYXJlIG1vcmUgc2VjdXJlIHRoYW4gb3RoZXJzPw0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0K


From nobody Tue May 17 12:54:03 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72EB212DD92 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PmLY3wW91Lam for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:54:01 -0700 (PDT)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E92612DD91 for <mmusic@ietf.org>; Tue, 17 May 2016 12:54:01 -0700 (PDT)
Received: by mail-ig0-x22d.google.com with SMTP id bi2so81076355igb.0 for <mmusic@ietf.org>; Tue, 17 May 2016 12:54:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=92cuohw2Bny+fQxSif9166Cl7sZDDWrs7oIhdLnov7Y=; b=WVUFJFchxM8K7NgohQUuRgyzQB6/+SwiCYQ9FZsRlBkqKXnkwBTZ1O5eD/V4OxNX8j kWT+0/KC0DcUQH2X39Nlzwq32dksmd2d17IeT8ruvwYjI4xpWgKTVLOeibhDVM7qS0ia w8+8t6wn+JgqAx+Nhs4q+GrhL05F6xqQ72i68jrjMDHwnaczsXzLslfW8Fm1Jv3vhQmE wS3ESs2Mxt3NGKsaJ1U9oteJ0KQAI//Yinl88CBh95ZZMnNyhgq4bsxJc983xFnxnJkl xKWx8kmb2g4KdaKub4irQXvX+sQSBXxegLQIVDmubhxxlsDSw3W4tPegbT7HLeIA9Z3s AVCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=92cuohw2Bny+fQxSif9166Cl7sZDDWrs7oIhdLnov7Y=; b=U6g6ATlfk8j/x4t7QXHjZyBcu7CYtF9tJ+FX2R9xOVB23NdTFbOnRgpGDKNViZj+pJ NzIEwX6gbl+foX/PeTK6LgKfdFnCNpkKVUQeHuxwY/abKgPyYz3hDasFrwQ0yH4K08HI aibao5cuRCYeJsMdpv93ijzTJZypGH1IxsxMwXF/5z96imXmiUP7AeIiaaM8kkJxE71k IH1dYTPN30S0lYTm2/m/xqDvT5zCizUjMT3+tRURSkzk9gvJ0YSSjzc4wgpcWSAIosaJ VeTSnYpKtioo/Khc8xy9hz7iCq3eazuXYx1VLUi5pL7rh1tv2Bd2WvzcUizgRfgjiosc ktqw==
X-Gm-Message-State: AOPr4FXBTDMX/hxqIfZJEyH1jTcfPD+5W27zEQlUJKCmkp+mxDC1rz+39IH/ehcNlWHlHgoTddiLhicLL8DLTg==
MIME-Version: 1.0
X-Received: by 10.50.59.211 with SMTP id b19mr2625963igr.58.1463514840724; Tue, 17 May 2016 12:54:00 -0700 (PDT)
Received: by 10.36.43.82 with HTTP; Tue, 17 May 2016 12:54:00 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se>
Date: Tue, 17 May 2016 15:54:00 -0400
Message-ID: <CABkgnnVfb1NxsYe3t9JwE4F5hjCyW4xFeSz_b3fvKCkprz8ALw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/O3V-PLu10FdPwPou1HJ7KN55Kys>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 19:54:02 -0000

On 17 May 2016 at 15:52, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> I guess we would say "considered most secure by the endpoint", because I don't think we want to define what hash functions are more secure than others?

Sure.


From nobody Tue May 17 12:58:01 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1806B12DD90 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFxBqEdVdq2h for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 12:57:57 -0700 (PDT)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD23512DDA3 for <mmusic@ietf.org>; Tue, 17 May 2016 12:57:56 -0700 (PDT)
Received: by mail-io0-x22a.google.com with SMTP id 190so37972242iow.1 for <mmusic@ietf.org>; Tue, 17 May 2016 12:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NKPQbg12UV/UeOXtYFSclYsmK2LNGZJAVyUGYy4RBE8=; b=Veg3Wr+BgVFr32/C0Lwog6zq78tg5kfe6Adth1ZJcY0rNw56VUnRahOUCFi4zXA6k3 JtVRsrePUz84GuHKLr9B7E7gDxTLnhxqi9weBXVLrYBWqgsK/XG0hwYxEfyTJ4DdE/hx Zlc8sh9Xs/kMufcAvryTBZlvGVVJD+SIKXZVK2s036whrhgZz3kHntX2D2ft6ihACLPf 5FWRJSx+LL3ZcMhtND2mb0Ks/pjm+HfBM7/RbTkchCAh4M5To4tClF6E5CAKOdLRaQ9F wCCgchzCRxkrHjMJ6+pBQW0Xo7GBFFZ7XNCz+yuMCKnv709SUPMSJYi7YpdHK3G0q4jG 2x4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=NKPQbg12UV/UeOXtYFSclYsmK2LNGZJAVyUGYy4RBE8=; b=GI3GCoYcCETb+irwr+rAbfzy532BUpGBjlpi5w42f7fpXg8GKExDYmqiqScd868C97 dA1QC0vJzumRoSw74pMf5NAwn1ILfmsj/NNkrHez0p1hl0KpQrj0u3hpBhgjqWiUD+f3 WC4V3rTLse8M6h+HWJnlVEWUg51XTwY3DVAoQzOYKyNZ2h6EQjPlba6JA1ELxxzxxeu5 9iKZPtSBow0slVmhuvndsL/EAmiKBete9Qcowi1n4mNUwfFLD4tWc0MkrBdjUj5AVnQ9 xe4FoPJsI5i+zTSTCabpYIc3FH4p0T9KlKhj1ZqxrEvfauhDYS6f2CxXAsXDkqE9kWRN 3XIA==
X-Gm-Message-State: AOPr4FWZK75A25uuppyI9lkqwLhyHhyETyDtM7ggJ2Zv7U88GAWcZxSly1xcnz76rzRa4A==
X-Received: by 10.36.64.8 with SMTP id n8mr2463498ita.21.1463515076204; Tue, 17 May 2016 12:57:56 -0700 (PDT)
Received: from mail-io0-f169.google.com (mail-io0-f169.google.com. [209.85.223.169]) by smtp.gmail.com with ESMTPSA id oy1sm1546814igb.8.2016.05.17.12.57.55 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 12:57:55 -0700 (PDT)
Received: by mail-io0-f169.google.com with SMTP id d62so37997302iof.2 for <mmusic@ietf.org>; Tue, 17 May 2016 12:57:55 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.160.76 with SMTP id j73mr2445127ioe.66.1463515075303; Tue, 17 May 2016 12:57:55 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 17 May 2016 12:57:55 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se>
Date: Tue, 17 May 2016 15:57:55 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com>
Message-ID: <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114027b8300a7405330f28d9
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/R9nN0oRjCkbvucorofEL1cCQ8kU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 19:57:59 -0000

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

On Tue, May 17, 2016 at 3:52 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >> Should match either all fingerprints or the most secure hash function
> >> present and in SDP and supported by the end point.
> >
> > WFM, we might add "MAY additionally check other hash functions", but one
> match is the ideal
>
> I guess we would say "considered most secure by the endpoint", because I
> don't think we want to define what hash functions are more secure than
> others?
>
>
I gust wanted to suggest the same thing since we do not want another
academic discussion.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Tue, May 17, 2016 at 3:52 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex"><span class=3D"">&gt;&gt; Should match ei=
ther all fingerprints or the most secure hash function<br>
&gt;&gt; present and in SDP and supported by the end point.<br>
&gt;<br>
&gt; WFM, we might add &quot;MAY additionally check other hash functions&qu=
ot;, but one match is the ideal<br>
<br>
</span>I guess we would say &quot;considered most secure by the endpoint&qu=
ot;, because I don&#39;t think we want to define what hash functions are mo=
re secure than others?<br>
<br></blockquote><div><br></div><div>I gust wanted to suggest the same thin=
g since we do not want another academic discussion.</div><div><div class=3D=
"gmail_signature">_____________<br>Roman Shpount</div></div><div>=C2=A0</di=
v></div></div></div>

--001a114027b8300a7405330f28d9--


From nobody Tue May 17 13:05:31 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F08312D98A for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 13:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmKWbTtCm0Pz for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 13:05:29 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67A4312DD9C for <mmusic@ietf.org>; Tue, 17 May 2016 13:05:29 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-53-573b79872e19
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id D3.E4.27088.7897B375; Tue, 17 May 2016 22:05:27 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0248.002; Tue, 17 May 2016 22:05:27 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///cocA=
Date: Tue, 17 May 2016 20:05:26 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCFC37@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com>
In-Reply-To: <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUyM2K7t257pXW4wbsFRhbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsEroyffzax Fpxjq5ix9xpbA+MOti5GDg4JAROJU9Mluxg5gUwxiQv31gOFuTiEBI4wSmx/s4wdwlnCKHG7 fxUTSAObgIVE9z9tkAYRAVWJv98nM4HYzAJVEq//97CAlAgL5Eps2+gLUZIncWHOU2YI209i zr9PYDYLUOvJtRvYQGxeAV+JZ02bGCFWPWOSONywGyzBKRAosejPRVYQmxHouO+n1kDtEpe4 9WQ+E8TRAhJL9pxnhrBFJV4+/scKYStJrNh+iRHkHmYBTYn1u/QhWhUlpnQ/ZIfYKyhxcuYT lgmMYrOQTJ2F0DELSccsJB0LGFlWMYoWpxYn5aYbGemlFmUmFxfn5+nlpZZsYgTG18Etvw12 ML587niIUYCDUYmH94GTVbgQa2JZcWXuIUYJDmYlEV7XMutwId6UxMqq1KL8+KLSnNTiQ4zS HCxK4rz+LxXDhQTSE0tSs1NTC1KLYLJMHJxSDYyxkboTHiwvf1FX231lJvNsxtV/nOt/PykN EH339/qasNLUy6tqtv5qF8jpMv0X7tLoJfDA15H/c/Dm85yFd6/ekL159tGpmMtrt9tMKPp9 /Tjv8ctnrmu73torsKL/RWtjRNY3CV0uDras7DK+k93PXFSFdLdsmN3/0GVjEuf2f6nNky/5 nF+kxFKckWioxVxUnAgArpi6OKsCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/q9jDkZuS0DvgOqi522FMyOm3GA8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 20:05:30 -0000

SGksDQoNCj4+Pj4gU2hvdWxkIG1hdGNoIGVpdGhlciBhbGwgZmluZ2VycHJpbnRzIG9yIHRoZSBt
b3N0IHNlY3VyZSBoYXNoIGZ1bmN0aW9uDQo+Pj4+IHByZXNlbnQgYW5kIGluIFNEUCBhbmQgc3Vw
cG9ydGVkIGJ5IHRoZSBlbmQgcG9pbnQuDQo+Pj4NCj4+PiBXRk0sIHdlIG1pZ2h0IGFkZCAiTUFZ
IGFkZGl0aW9uYWxseSBjaGVjayBvdGhlciBoYXNoIGZ1bmN0aW9ucyIsIGJ1dCBvbmUgbWF0Y2gg
aXMgdGhlIGlkZWFsDQo+Pg0KPj4gSSBndWVzcyB3ZSB3b3VsZCBzYXkgImNvbnNpZGVyZWQgbW9z
dCBzZWN1cmUgYnkgdGhlIGVuZHBvaW50IiwgYmVjYXVzZSBJIGRvbid0IHRoaW5rIHdlIHdhbnQg
dG8gZGVmaW5lIHdoYXQgaGFzaCBmdW5jdGlvbnMgYXJlIG1vcmUgc2VjdXJlIHRoYW4gb3RoZXJz
Pw0KPg0KPiBJIGd1c3Qgd2FudGVkIHRvIHN1Z2dlc3QgdGhlIHNhbWUgdGhpbmcgc2luY2Ugd2Ug
ZG8gbm90IHdhbnQgYW5vdGhlciBhY2FkZW1pYyBkaXNjdXNzaW9uLg0KDQpUaGUgc2VjdXJpdHkg
Zm9sa3MgbWF5IHdhbnQgdG8gaGF2ZSBzdWNoIGRpc2N1c3Npb24sIGJ1dCB3ZSdsbCBzZWUgd2hl
biB3ZSBnZXQgdGhlcmUgOikNCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCsKgDQo=


From nobody Tue May 17 13:47:12 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3FC512D1B7 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 13:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f1T0p6Rf9WFs for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 13:47:10 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5866312D11C for <mmusic@ietf.org>; Tue, 17 May 2016 13:47:08 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-f8-573b834b0b38
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 29.AD.12926.B438B375; Tue, 17 May 2016 22:47:07 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0248.002; Tue, 17 May 2016 22:47:06 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITA=
Date: Tue, 17 May 2016 20:47:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com>
In-Reply-To: <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FCFD04ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrEIsWRmVeSWpSXmKPExsUyM2K7va53s3W4wZu1UhbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsEroyWBseC f0sZK76vWsXUwHhiIWMXIyeHhICJxLsTj5ggbDGJC/fWs3UxcnEICRxhlLj45AgThLOEUWLS p51ADgcHm4CFRPc/bZAGEQFVib/fJ4M1MwtUSbz+38MCUiIskCuxbaMvREmexIU5T5khbD+J k4tnsoOUsAC1dn4zAwnzCvhKXJx9iR1i0zMmicMNu9lAEpwCgRKL/lxkBbEZgW77fmoN1Cpx iVtP5kPdLCCxZM95ZghbVOLl43+sELaSxIrtlxgh6vMl/qw9wA6xTFDi5MwnLBMYRWchGTUL SdksJGWzgE5lFtCUWL9LH6JEUWJK90N2CFtDonXOXHZk8QWM7KsYRYtTi5Ny042M9VKLMpOL i/Pz9PJSSzYxAmPy4JbfqjsYL79xPMQowMGoxMP7wMkqXIg1say4MvcQowQHs5IIr0aDdbgQ b0piZVVqUX58UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGRiYtCwO219o+ h2WCQoLc2XfYxuyYOU3e/dh6p0ev1pm1epbf4raRdGepuRN+8K/PpUMVZdrtmpMWBWTLiC3M nRfdUlW8ctFRCe88R/2mO1WBK/e8sTjLIPfc71rsCfvCLha1UgZZ77jLm0JMV9itvhe1YaNC Ekup7xX+oO+1HyZFX0gurZ2oxFKckWioxVxUnAgA/YriG8UCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/IDaI40NTCufs5eOUZhs__ayXhe0>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 20:47:12 -0000

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

SGksDQoNCkJhc2VkIG9uIHRoZSBkaXNjdXNzaW9ucywgYmVsb3cgaXMgYSBzdWdnZXN0aW9uIGZv
ciB0aGUgbmV3IHRleHQ6DQoNCi0tLS0tLS0tLS0tLS0tDQoNCk5FVyBURVhUOg0KDQogICAgTXVs
dGlwbGUgU0RQIGZpbmdlcnByaW50IGF0dHJpYnV0ZXMgY2FuIGJlIGFzc29jaWF0ZWQgd2l0aCBh
biBtLQ0KICAgIGxpbmUuIFRoaXMgY2FuIG9jY3VyIGlmIG11bHRpcGxlIGZpbmdlcnByaW50cyBo
YXZlIGJlZW4gY2FsY3VsYXRlZA0KICAgIGZvciBhIGNlcnRpZmljYXRlLCB1c2luZyBkaWZmZXJl
bnQgaGFzaCBmdW5jdGlvbnMuIEl0IGNhbiBhbHNvDQogICAgb2NjdXIgaWYgb25lIG9yIG1vcmUg
ZmluZ2VycHJpbnRzIGFzc29jaWF0ZWQgd2l0aCBtdWx0aXBsZQ0KICAgIGNlcnRpZmljYXRlcyBo
YXZlIGJlZW4gY2FsY3VsYXRlZCwgZS5nLiBmb3IgY2FzZXMgd2hlcmUgbXVsdGlwbGUNCiAgICBj
ZXJ0aWZpY2F0ZXMgd2lsbCBiZSB1c2VkIGZvciBtZWRpYSBhc3NvY2lhdGVkIHdpdGggYW4gbS0g
bGluZQ0KICAgIChlLmcuIHNlcGFyYXRlIGNlcnRpZmljYXRlcyBmb3IgUlRQIGFuZCBSVENQKSwg
b3Igd2hlcmUgaXQgaXMgbm90DQogICAga25vd24gd2hpY2ggY2VydGlmaWNhdGUgd2lsbCBiZSB1
c2VkIHdoZW4gdGhlIGZpbmdlcnByaW50cyBhcmUNCiAgICBleGNoYW5nZWQuIEluIHN1Y2ggY2Fz
ZXMsIG9uZSBvciBtb3JlIGZpbmdlcnByaW50cyBNVVNUIGJlDQogICAgY2FsY3VsYXRlZCBmb3Ig
ZWFjaCBwb3NzaWJsZSBjZXJ0aWZpY2F0ZS4NCg0KICAgIElmIGZpbmdlcnByaW50cyBhc3NvY2lh
dGVkIHdpdGggbXVsdGlwbGUgY2VydGlmaWNhdGVzIGFyZQ0KICAgIGNhbGN1bGF0ZWQsIHRoZSBz
YW1lIHNldCBvZiBmaW5nZXJwcmludHMgKHVzaW5nIHRoZSBzYW1lIGhhc2gNCiAgICBmdW5jdGlv
bnMpIE1VU1QgYmUgY2FsY3VsYXRlZCBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSBhc3NvY2lhdGVkDQog
ICAgd2l0aCB0aGUgbS0gbGluZS4NCg0KICAgIEFuIGVuZHBvaW50IE1VU1QgYmUgYWJsZSB0byBt
YXRjaCBhdCBsZWFzdCBvbmUgZmluZ2VycHJpbnQsDQogICAgY2FsY3VsYXRlZCB1c2luZyB0aGUg
aGFzaCBmdW5jdGlvbiB0aGF0IHRoZSBlbmRwb2ludCBzdXBwb3J0cyBhbmQNCiAgICBjb25zaWRl
cnMgbW9zdCBzZWN1cmUsIHdpdGggdGhlIHVzZWQgY2VydGlmaWNhdGUuIElmIHRoZXJlIGlzIG5v
DQogICAgbWF0Y2gsIHRoZSBlbmRwb2ludCBNVVNUIE5PVCBlc3RhYmxpc2ggdGhlIFRMUyBjb25u
ZWN0aW9uLiBJbg0KICAgIGFkZGl0aW9uLCB0aGUgZW5kcG9pbnQgTUFZIGFsc28gdGVzdCBvdGhl
ciBmaW5nZXJwcmludHMgZm9yIGEgbWF0Y2gNCiAgICAsIGluIHdoaWNoIGNhc2UgZWFjaCB0ZXN0
ZWQgZmluZ2VycHJpbnRzIE1VU1QgbWF0Y2ggdGhlIHVzZWQNCiAgICBjZXJ0aWZpY2F0ZS4NCg0K
ICAgIE5PVEU6IFRoZSBTRFAgZmluZ2VycHJpbnQgYXR0cmlidXRlIGRvZXMgbm90IGNvbnRhaW4g
YSByZWZlcmVuY2UgdG8NCiAgICBhIHNwZWNpZmljIGNlcnRpZmljYXRlLiBFbmRwb2ludHMgbmVl
ZCB0byBjb21wYXJlIHRoZSBmaW5nZXJwcmludA0KICAgIHdpdGggYSBjZXJ0aWZpY2F0ZSBoYXNo
IGluIG9yZGVyIHRvIGxvb2sgZm9yIGEgbWF0Y2guDQoNCi0tLS0tLS0tLS0tLS0tDQoNClJlZ2Fy
ZHMsDQoNCkNocmlzdGVyDQoNCkZyb206IFJvbWFuIFNocG91bnQgW21haWx0bzpyb21hbkB0ZWx1
cml4LmNvbV0NClNlbnQ6IDE3IE1heSAyMDE2IDIyOjU4DQpUbzogQ2hyaXN0ZXIgSG9sbWJlcmcg
PGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4NCkNjOiBNYXJ0aW4gVGhvbXNvbiA8bWFy
dGluLnRob21zb25AZ21haWwuY29tPjsgbW11c2ljQGlldGYub3JnOyBQYXVsIEt5eml2YXQgPHBr
eXppdmF0QGFsdW0ubWl0LmVkdT4NClN1YmplY3Q6IFJlOiBbTU1VU0lDXSBEcmFmdCBuZXcgdmVy
c2lvbjogZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUtMDEgLSBMaWdodCBhdCB0aGUgZW5k
IG9mIHRoZSB0dW5uZWw/DQoNCk9uIFR1ZSwgTWF5IDE3LCAyMDE2IGF0IDM6NTIgUE0sIENocmlz
dGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208bWFpbHRvOmNocmlz
dGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KPj4gU2hvdWxkIG1hdGNoIGVpdGhl
ciBhbGwgZmluZ2VycHJpbnRzIG9yIHRoZSBtb3N0IHNlY3VyZSBoYXNoIGZ1bmN0aW9uDQo+PiBw
cmVzZW50IGFuZCBpbiBTRFAgYW5kIHN1cHBvcnRlZCBieSB0aGUgZW5kIHBvaW50Lg0KPg0KPiBX
Rk0sIHdlIG1pZ2h0IGFkZCAiTUFZIGFkZGl0aW9uYWxseSBjaGVjayBvdGhlciBoYXNoIGZ1bmN0
aW9ucyIsIGJ1dCBvbmUgbWF0Y2ggaXMgdGhlIGlkZWFsDQoNCkkgZ3Vlc3Mgd2Ugd291bGQgc2F5
ICJjb25zaWRlcmVkIG1vc3Qgc2VjdXJlIGJ5IHRoZSBlbmRwb2ludCIsIGJlY2F1c2UgSSBkb24n
dCB0aGluayB3ZSB3YW50IHRvIGRlZmluZSB3aGF0IGhhc2ggZnVuY3Rpb25zIGFyZSBtb3JlIHNl
Y3VyZSB0aGFuIG90aGVycz8NCg0KSSBndXN0IHdhbnRlZCB0byBzdWdnZXN0IHRoZSBzYW1lIHRo
aW5nIHNpbmNlIHdlIGRvIG5vdCB3YW50IGFub3RoZXIgYWNhZGVtaWMgZGlzY3Vzc2lvbi4NCl9f
X19fX19fX19fX18NClJvbWFuIFNocG91bnQNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl
eHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0
IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29y
ZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9
IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0
aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj5CYXNlZCBvbiB0aGUgZGlzY3Vzc2lvbnMsIGJlbG93IGlzIGEgc3Vn
Z2VzdGlvbiBmb3IgdGhlIG5ldyB0ZXh0OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+LS0tLS0tLS0tLS0tLS08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPk5FVyBURVhUOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7IE11bHRpcGxlIFNEUCBmaW5nZXJwcmludCBhdHRyaWJ1dGVzIGNh
biBiZSBhc3NvY2lhdGVkIHdpdGggYW4gbS0NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtsaW5lLiBUaGlzIGNhbiBv
Y2N1ciBpZiBtdWx0aXBsZSBmaW5nZXJwcmludHMgaGF2ZSBiZWVuIGNhbGN1bGF0ZWQ8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
IGZvciBhIGNlcnRpZmljYXRlLCB1c2luZyBkaWZmZXJlbnQgaGFzaCBmdW5jdGlvbnMuIEl0IGNh
biBhbHNvPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNw
OyZuYnNwOyZuYnNwOyBvY2N1ciBpZiBvbmUgb3IgbW9yZSBmaW5nZXJwcmludHMgYXNzb2NpYXRl
ZCB3aXRoIG11bHRpcGxlDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Y2VydGlmaWNhdGVzIGhhdmUgYmVlbiBjYWxj
dWxhdGVkLCBlLmcuIGZvciBjYXNlcyB3aGVyZSBtdWx0aXBsZQ0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2NlcnRp
ZmljYXRlcyB3aWxsIGJlIHVzZWQgZm9yIG1lZGlhIGFzc29jaWF0ZWQgd2l0aCBhbiBtLSBsaW5l
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNw
OyZuYnNwOyAoZS5nLiBzZXBhcmF0ZSBjZXJ0aWZpY2F0ZXMgZm9yIFJUUCBhbmQgUlRDUCksIG9y
IHdoZXJlIGl0IGlzIG5vdDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsga25vd24gd2hpY2ggY2VydGlmaWNhdGUgd2lsbCBiZSB1
c2VkIHdoZW4gdGhlIGZpbmdlcnByaW50cyBhcmU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFz
dC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGV4Y2hhbmdlZC4gSW4gc3VjaCBj
YXNlcywgb25lIG9yIG1vcmUgZmluZ2VycHJpbnRzIE1VU1QgYmUNCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdE
O21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtjYWxj
dWxhdGVkIGZvciBlYWNoIHBvc3NpYmxlIGNlcnRpZmljYXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsNCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
MUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDtJZiBmaW5nZXJwcmludHMgYXNzb2NpYXRlZCB3aXRoIG11bHRpcGxlIGNlcnRpZmljYXRlcyBh
cmUNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDtjYWxjdWxhdGVkLCB0aGUgc2FtZSBzZXQgb2YgZmluZ2VycHJpbnRz
ICh1c2luZyB0aGUgc2FtZSBoYXNoPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOyBmdW5jdGlvbnMpIE1VU1QgYmUgY2FsY3VsYXRl
ZCBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSBhc3NvY2lhdGVkPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOyB3aXRoIHRoZSBtLSBsaW5l
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtBbiBlbmRwb2lu
dCBNVVNUIGJlIGFibGUgdG8gbWF0Y2ggYXQgbGVhc3Qgb25lIGZpbmdlcnByaW50LA0KPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwO2NhbGN1bGF0ZWQgdXNpbmcgdGhlIGhhc2ggZnVuY3Rpb24gdGhhdCB0aGUgZW5kcG9p
bnQgc3VwcG9ydHMgYW5kPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPiZuYnNwOyZuYnNwOyZuYnNwOyBjb25zaWRlcnMgbW9zdCBzZWN1cmUsIHdpdGggdGhlIHVz
ZWQgY2VydGlmaWNhdGUuIElmIHRoZXJlIGlzIG5vPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOyBtYXRjaCwgdGhlIGVuZHBvaW50
IE1VU1QgTk9UIGVzdGFibGlzaCB0aGUgVExTIGNvbm5lY3Rpb24uIEluDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFG
NDk3RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
YWRkaXRpb24sIHRoZSBlbmRwb2ludCBNQVkgYWxzbyB0ZXN0IG90aGVyIGZpbmdlcnByaW50cyBm
b3IgYSBtYXRjaDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4m
bmJzcDsmbmJzcDsmbmJzcDsgLCBpbiB3aGljaCBjYXNlIGVhY2ggdGVzdGVkIGZpbmdlcnByaW50
cyBNVVNUIG1hdGNoIHRoZSB1c2VkDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Y2VydGlmaWNhdGUuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOw0K
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwO05PVEU6IFRoZSBTRFAgZmluZ2VycHJpbnQgYXR0cmlidXRlIGRvZXMgbm90
IGNvbnRhaW4gYSByZWZlcmVuY2UgdG88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGEgc3BlY2lmaWMgY2VydGlmaWNhdGUuIEVu
ZHBvaW50cyBuZWVkIHRvIGNvbXBhcmUgdGhlIGZpbmdlcnByaW50PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOyZuYnNwOyZuYnNwOyB3aXRoIGEgY2Vy
dGlmaWNhdGUgaGFzaCBpbiBvcmRlciB0byBsb29rIGZvciBhIG1hdGNoLjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDtt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+LS0tLS0tLS0tLS0tLS08bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWlsRW5kQ29tcG9zZSI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiMxRjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvYT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+IFJvbWFuIFNocG91bnQgW21haWx0bzpyb21hbkB0ZWx1cml4LmNvbV0NCjxicj4NCjxiPlNl
bnQ6PC9iPiAxNyBNYXkgMjAxNiAyMjo1ODxicj4NCjxiPlRvOjwvYj4gQ2hyaXN0ZXIgSG9sbWJl
cmcgJmx0O2NocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+
IE1hcnRpbiBUaG9tc29uICZsdDttYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20mZ3Q7OyBtbXVzaWNA
aWV0Zi5vcmc7IFBhdWwgS3l6aXZhdCAmbHQ7cGt5eml2YXRAYWx1bS5taXQuZWR1Jmd0Ozxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogW01NVVNJQ10gRHJhZnQgbmV3IHZlcnNpb246IGRyYWZ0LWll
dGYtbW11c2ljLTQ1NzItdXBkYXRlLTAxIC0gTGlnaHQgYXQgdGhlIGVuZCBvZiB0aGUgdHVubmVs
PzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPk9uIFR1ZSwgTWF5IDE3LCAyMDE2IGF0IDM6NTIgUE0sIENocmlzdGVyIEhvbG1iZXJnICZs
dDs8YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tIiB0YXJnZXQ9
Il9ibGFuayI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPiZndDsmZ3Q7IFNob3Vs
ZCBtYXRjaCBlaXRoZXIgYWxsIGZpbmdlcnByaW50cyBvciB0aGUgbW9zdCBzZWN1cmUgaGFzaCBm
dW5jdGlvbjxicj4NCiZndDsmZ3Q7IHByZXNlbnQgYW5kIGluIFNEUCBhbmQgc3VwcG9ydGVkIGJ5
IHRoZSBlbmQgcG9pbnQuPGJyPg0KJmd0Ozxicj4NCiZndDsgV0ZNLCB3ZSBtaWdodCBhZGQgJnF1
b3Q7TUFZIGFkZGl0aW9uYWxseSBjaGVjayBvdGhlciBoYXNoIGZ1bmN0aW9ucyZxdW90OywgYnV0
IG9uZSBtYXRjaCBpcyB0aGUgaWRlYWw8YnI+DQo8YnI+DQpJIGd1ZXNzIHdlIHdvdWxkIHNheSAm
cXVvdDtjb25zaWRlcmVkIG1vc3Qgc2VjdXJlIGJ5IHRoZSBlbmRwb2ludCZxdW90OywgYmVjYXVz
ZSBJIGRvbid0IHRoaW5rIHdlIHdhbnQgdG8gZGVmaW5lIHdoYXQgaGFzaCBmdW5jdGlvbnMgYXJl
IG1vcmUgc2VjdXJlIHRoYW4gb3RoZXJzPzxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBndXN0IHdhbnRlZCB0byBzdWdnZXN0IHRo
ZSBzYW1lIHRoaW5nIHNpbmNlIHdlIGRvIG5vdCB3YW50IGFub3RoZXIgYWNhZGVtaWMgZGlzY3Vz
c2lvbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5fX19fX19fX19fX19fPGJyPg0KUm9tYW4gU2hwb3VudDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B37FCFD04ESESSMB209erics_--


From nobody Tue May 17 13:49:09 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F3312D1CC for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 13:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KlelW6jWCRo for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 13:49:05 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BAB912D1B7 for <mmusic@ietf.org>; Tue, 17 May 2016 13:49:05 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id i75so39750796ioa.3 for <mmusic@ietf.org>; Tue, 17 May 2016 13:49:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=0PBECXog4g4TxG+zOzzvYGqo4j6YE3jiE3GPIIEgZVU=; b=ada+I5qCjYuVoHj35J+Eylza4JlfKC3BGncKAdPe5583RJaQIhjl94jJoE2B2i+dY3 L4xqF/Tz7SqLJrVqcKrMa4Sbrz/rS0OUOAQUN7wzURRVeE+VJG7EOJL1a+msrDG2MUV9 GGUwlNJVR9NO8kUE7jC9nWKw9D/K8dy001TGcXWuvJHUbFC2hgELrEnRtAdB51dhP/fG IJLtS0q6JdCRiXt+/M8YrBLdElKegaOyzYmzYqIL1NmG88sxO3Q9uFBNTsMnKX87p5n0 1bPYdSVlOtCLzu5c7lzGGAiXwH2IL7akOSN//qdHycJ34QDWW4YdDWKtdoZKJZQRT3Eo CMTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=0PBECXog4g4TxG+zOzzvYGqo4j6YE3jiE3GPIIEgZVU=; b=eDsylPpohx+yMV044Fkpfpm/4BEGJcznqWpZmjuONTX2ae44CFpgekSgh/R7bqyJvO 3EoaVHe+s4WFxSaWGk0GPCHDGM4FPHv2DGeM4THSi/3hiy8V4DRKlW4TIGiuFleiqCDC mGbD/k5YBGWgSZFsyaANEIBKc9jOCofIFNNuo5z+SEbJkrOVMNiWOLjzWrnlzkOTdrwz cDAJVtOPxLmOep3+36gEuLk/gPT2FO4EJgeQ/T4v3nzJmqDT0Z8qR1VDXTsO69gbnuy1 HWtgo37UymBV4FwI+2WUyyPq0l0c+ykXICFlNdLqbG8XcaBZasa37O94jNtk3mbWFFZ2 oufw==
X-Gm-Message-State: AOPr4FXlLlIsRrY4E/dlzHYeT0bMoFcm7SjRXH+7R+c5GFVcS3NX4vRkO3c3CsR29c6nUQ==
X-Received: by 10.36.34.145 with SMTP id o139mr114326ito.39.1463518144427; Tue, 17 May 2016 13:49:04 -0700 (PDT)
Received: from mail-io0-f172.google.com (mail-io0-f172.google.com. [209.85.223.172]) by smtp.gmail.com with ESMTPSA id o201sm1604962ioe.15.2016.05.17.13.49.03 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 17 May 2016 13:49:03 -0700 (PDT)
Received: by mail-io0-f172.google.com with SMTP id 190so39730382iow.1 for <mmusic@ietf.org>; Tue, 17 May 2016 13:49:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.156.131 with SMTP id b125mr2753876ite.95.1463518143524; Tue, 17 May 2016 13:49:03 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 17 May 2016 13:49:03 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
Date: Tue, 17 May 2016 16:49:03 -0400
X-Gmail-Original-Message-ID: <CAD5OKxubaDAm41A_z=0-CiBqWpawjJs4qqEV8y_t1gHu+0ECyw@mail.gmail.com>
Message-ID: <CAD5OKxubaDAm41A_z=0-CiBqWpawjJs4qqEV8y_t1gHu+0ECyw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c089e7c11606a05330fdfac
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/xEPBOsvEd6dPw51LbcvXBeYcHEg>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 20:49:07 -0000

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

LGTM

_____________
Roman Shpount

On Tue, May 17, 2016 at 4:47 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
>
>
> Based on the discussions, below is a suggestion for the new text:
>
>
>
> --------------
>
>
>
> NEW TEXT:
>
>
>
>     Multiple SDP fingerprint attributes can be associated with an m-
>
>     line. This can occur if multiple fingerprints have been calculated
>
>     for a certificate, using different hash functions. It can also
>
>     occur if one or more fingerprints associated with multiple
>
>     certificates have been calculated, e.g. for cases where multiple
>
>     certificates will be used for media associated with an m- line
>
>     (e.g. separate certificates for RTP and RTCP), or where it is not
>
>     known which certificate will be used when the fingerprints are
>
>     exchanged. In such cases, one or more fingerprints MUST be
>
>     calculated for each possible certificate.
>
>
>
>     If fingerprints associated with multiple certificates are
>
>     calculated, the same set of fingerprints (using the same hash
>
>     functions) MUST be calculated for each certificate associated
>
>     with the m- line.
>
>
>
>     An endpoint MUST be able to match at least one fingerprint,
>
>     calculated using the hash function that the endpoint supports and
>
>     considers most secure, with the used certificate. If there is no
>
>     match, the endpoint MUST NOT establish the TLS connection. In
>
>     addition, the endpoint MAY also test other fingerprints for a match
>
>     , in which case each tested fingerprints MUST match the used
>
>     certificate.
>
>
>
>     NOTE: The SDP fingerprint attribute does not contain a reference to
>
>     a specific certificate. Endpoints need to compare the fingerprint
>
>     with a certificate hash in order to look for a match.
>
>
>
> --------------
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> *From:* Roman Shpount [mailto:roman@telurix.com]
> *Sent:* 17 May 2016 22:58
> *To:* Christer Holmberg <christer.holmberg@ericsson.com>
> *Cc:* Martin Thomson <martin.thomson@gmail.com>; mmusic@ietf.org; Paul
> Kyzivat <pkyzivat@alum.mit.edu>
> *Subject:* Re: [MMUSIC] Draft new version:
> draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
>
>
>
> On Tue, May 17, 2016 at 3:52 PM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
> >> Should match either all fingerprints or the most secure hash function
> >> present and in SDP and supported by the end point.
> >
> > WFM, we might add "MAY additionally check other hash functions", but one
> match is the ideal
>
> I guess we would say "considered most secure by the endpoint", because I
> don't think we want to define what hash functions are more secure than
> others?
>
>
>
> I gust wanted to suggest the same thing since we do not want another
> academic discussion.
>
> _____________
> Roman Shpount
>
>
>

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

<div dir=3D"ltr">LGTM</div><div class=3D"gmail_extra"><br clear=3D"all"><di=
v><div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Tue, May 17, 2016 at 4:47 PM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Based on the discussions, below is a =
suggestion for the new text:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">--------------<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">NEW TEXT:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 Multiple SDP finge=
rprint attributes can be associated with an m-
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0line. This ca=
n occur if multiple fingerprints have been calculated<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 for a certificate,=
 using different hash functions. It can also<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 occur if one or mo=
re fingerprints associated with multiple
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0certificates =
have been calculated, e.g. for cases where multiple
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0certificates =
will be used for media associated with an m- line<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 (e.g. separate cer=
tificates for RTP and RTCP), or where it is not<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 known which certif=
icate will be used when the fingerprints are<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 exchanged. In such=
 cases, one or more fingerprints MUST be
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0calculated fo=
r each possible certificate.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0If fingerprin=
ts associated with multiple certificates are
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0calculated, t=
he same set of fingerprints (using the same hash<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 functions) MUST be=
 calculated for each certificate associated<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 with the m- line.<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0An endpoint M=
UST be able to match at least one fingerprint,
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0calculated us=
ing the hash function that the endpoint supports and<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 considers most sec=
ure, with the used certificate. If there is no<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 match, the endpoin=
t MUST NOT establish the TLS connection. In
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0addition, the=
 endpoint MAY also test other fingerprints for a match<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 , in which case ea=
ch tested fingerprints MUST match the used
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0certificate.<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0NOTE: The SDP=
 fingerprint attribute does not contain a reference to<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 a specific certifi=
cate. Endpoints need to compare the fingerprint<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">=C2=A0=C2=A0=C2=A0 with a certificate=
 hash in order to look for a match.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">--------------<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Regards,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1f497d">Christer<u></u><u></u></span></p>
<p class=3D"MsoNormal"><a name=3D"m_7174032477681901561__MailEndCompose"><s=
pan style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif;co=
lor:#1f497d"><u></u>=C2=A0<u></u></span></a></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,sans-serif">From:</span></b><span lang=3D"EN-=
US" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-serif"> =
Roman Shpount [mailto:<a href=3D"mailto:roman@telurix.com" target=3D"_blank=
">roman@telurix.com</a>]
<br>
<b>Sent:</b> 17 May 2016 22:58<br>
<b>To:</b> Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericss=
on.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;<br>
<b>Cc:</b> Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" t=
arget=3D"_blank">martin.thomson@gmail.com</a>&gt;; <a href=3D"mailto:mmusic=
@ietf.org" target=3D"_blank">mmusic@ietf.org</a>; Paul Kyzivat &lt;<a href=
=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</=
a>&gt;<br>
<b>Subject:</b> Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-upda=
te-01 - Light at the end of the tunnel?<u></u><u></u></span></p><div><div c=
lass=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal">On Tue, May 17, 2016 at 3:52 PM, Christer Holmberg &=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt; wrote:<u></u><u></u></p>
</div>
</div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&gt;&gt; Should match=
 either all fingerprints or the most secure hash function<br>
&gt;&gt; present and in SDP and supported by the end point.<br>
&gt;<br>
&gt; WFM, we might add &quot;MAY additionally check other hash functions&qu=
ot;, but one match is the ideal<br>
<br>
I guess we would say &quot;considered most secure by the endpoint&quot;, be=
cause I don&#39;t think we want to define what hash functions are more secu=
re than others?<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I gust wanted to suggest the same thing since we do =
not want another academic discussion.<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">_____________<br>
Roman Shpount<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>

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

--94eb2c089e7c11606a05330fdfac--


From nobody Tue May 17 14:08:00 2016
Return-Path: <prvs=39456b8b1f=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 7566B12D1F0 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 14:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.627
X-Spam-Level: 
X-Spam-Status: No, score=-5.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, 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 qY9vIZpNTJIM for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 14:07:58 -0700 (PDT)
Received: from alum-mailsec-scanner-7.mit.edu (alum-mailsec-scanner-7.mit.edu [18.7.68.19]) by ietfa.amsl.com (Postfix) with ESMTP id 0FFCC12D1DF for <mmusic@ietf.org>; Tue, 17 May 2016 14:07:57 -0700 (PDT)
X-AuditID: 12074413-473ff700000008c7-1d-573b882d4086
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by  (Symantec Messaging Gateway) with SMTP id 4F.BE.02247.D288B375; Tue, 17 May 2016 17:07:57 -0400 (EDT)
Received: from Paul-Kyzivats-MacBook-Pro.local (c-73-218-51-154.hsd1.ma.comcast.net [73.218.51.154]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id u4HL7tXX030201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 17 May 2016 17:07:56 -0400
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu>
Date: Tue, 17 May 2016 17:07:53 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42IRYndR1NXtsA43ODdb2uLCzMOMFtfO/GO0 mLr8MYvFjAtTmR1YPH59vcrmsXPWXXaPJUt+MnncmlIQwBLFbZOUWFIWnJmep2+XwJ3RM6eN veAuf8XjY3wNjO+4uxg5OSQETCSW9W9i7WLk4hAS2MoosehCKzuE85RJ4vOLq2wgVcICuRLL H10DSnBwiAgkSRzrLoGoWcUsMWfHZkaQGmaBaImfqzYzg9hsAloScw79ZwGp5xWwl3jS6g0S ZhFQlei+dYEJxBYVSJM4e+0EWDmvgKDEyZlPWEBsTgE/idfTf0ONNJOYt/khM4QtL7H97Rzm CYz8s5C0zEJSNgtJ2QJG5lWMcok5pbm6uYmZOcWpybrFyYl5ealFuuZ6uZkleqkppZsYIWEr vINx10m5Q4wCHIxKPLwVRlbhQqyJZcWVuYcYJTmYlER5L5hYhwvxJeWnVGYkFmfEF5XmpBYf YpTgYFYS4f3ZBJTjTUmsrEotyodJSXOwKInzqi1R9xMSSE8sSc1OTS1ILYLJynBwKEnwlrQD NQoWpaanVqRl5pQgpJk4OEGGc0mJFKfmpaQWJZaWZMSD4jG+GBiRICkeoL21IO28xQWJuUBR iNZTjIpS4rwJbUAJAZBERmke3FhYMnrFKA70pTAvP0g7DzCRwXW/AhrMBDR4gpkFyOCSRISU VAPjwqkGqbcLONeG3EoPs/bjmX6oektml2BI4t32tb1yE1vEfp45Im+Zcfouy9vopEO8s9d+ eFrz2Wpt/8U3tZbLtTfduzsl+ZGf9PNNk3lYC7oD8jU5n08/f/7Bus+96mvkFeY5qSkrJjbZ zwhtXRf4Xm6px+sKm2hV/1mH/kTdjz7e7/eaqfiHEktxRqKhFnNRcSIA7/lQKiEDAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1cq9FWltFn0UUfllrEZXdrJoF4k>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 21:07:59 -0000

On 5/17/16 4:47 PM, Christer Holmberg wrote:
> Hi,
>
>
>
> Based on the discussions, below is a suggestion for the new text:

This looks good except for a couple of points below.

> NEW TEXT:
>
>
>
>     Multiple SDP fingerprint attributes can be associated with an m-
>
>     line. This can occur if multiple fingerprints have been calculated
>
>     for a certificate, using different hash functions. It can also
>
>     occur if one or more fingerprints associated with multiple
>
>     certificates have been calculated, e.g. for cases where multiple
>
>     certificates will be used for media associated with an m- line
>
>     (e.g. separate certificates for RTP and RTCP), or where it is not
>
>     known which certificate will be used when the fingerprints are
>
>     exchanged. In such cases, one or more fingerprints MUST be
>
>     calculated for each possible certificate.
>
>
>
>     If fingerprints associated with multiple certificates are
>
>     calculated, the same set of fingerprints (using the same hash
>
>     functions) MUST be calculated for each certificate associated
>
>     with the m- line.
>
>
>
>     An endpoint MUST be able to match at least one fingerprint,

Prefix the above with "For each received certificate".

>     calculated using the hash function that the endpoint supports and
>
>     considers most secure, with the used certificate. If there is no
>
>     match, the endpoint MUST NOT establish the TLS connection. In

>     addition, the endpoint MAY also test other fingerprints for a match
>
>     , in which case each tested fingerprints MUST match the used
>
>     certificate.

That sentence isn't true when there are fingerprints for multiple 
certificates. How about:

"In addition, the endpoint may check other hash functions present in the 
fingerprints against the certificate. For each hash function checked, 
one of the fingerprints MUST match the certificate."

	Thanks,
	Paul


From nobody Tue May 17 14:23:00 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E71212D1D6 for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 14:22:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOPphrZnMtng for <mmusic@ietfa.amsl.com>; Tue, 17 May 2016 14:22:55 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07C9212D0BE for <mmusic@ietf.org>; Tue, 17 May 2016 14:22:54 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-37-573b8bac7925
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id AE.BA.27088.CAB8B375; Tue, 17 May 2016 23:22:53 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0248.002; Tue, 17 May 2016 23:22:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, MMUSIC <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
Thread-Index: AQHRsEMOIliX14uf2EKWpAtozqzJo5+9BuOAgACWdbA=
Date: Tue, 17 May 2016 21:22:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com>
In-Reply-To: <573B23FD.3070903@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyM2K7qO7abutwg6s7WSymLn/MYvHpxFYm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugSvj8HG9gpW6FS1PnrM3MM5R6WLk5JAQMJG4 /PYuE4QtJnHh3nq2LkYuDiGBI4wS6+Z2sYMkhASWMErcnB/axcjBwSZgIdH9TxskLCLgIvHo xQywEmGBJIm9Sw4zQcSTJW4dfcYCYVtJTNvwCMxmEVCV+NzbyQoyhlfAV+L3Gz+I6QkSvfOv M4OEOQU0JR7/SgEJMwJd8/3UGrCJzALiEreezIe6UkBiyZ7zzBC2qMTLx/9YIWwliRXbLzFC 1OtILNj9iQ3C1pZYtvA1WD2vgKDEyZlPWCYwis5CMnYWkpZZSFpmIWlZwMiyilG0OLU4KTfd yEgvtSgzubg4P08vL7VkEyMwPg5u+W2wg/Hlc8dDjAIcjEo8vA+crMKFWBPLiitzDzFKcDAr ifA6dFmHC/GmJFZWpRblxxeV5qQWH2KU5mBREuf1f6kYLiSQnliSmp2aWpBaBJNl4uCUamDc 6Mc5o+XCvKDzL4L/pvkYr0mVvLyzktWfr/TN7bm35NtSlOf4r2ZW2ecUde3d842r7oQK+8i7 F+s+OrDXvzTldJxzu3T7heeRVY8Zuu+fmm1hcizfnPn07JDA+yFBK3+tiHyxd6XWuqfP7tsd Z7+4Im2/fMvb7exry8Ieu83gv90Ws3bu+s9ZSizFGYmGWsxFxYkA9IxkDIsCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/MDZnh1lL4doMzhXcfiWu2dhwhm4>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 May 2016 21:22:57 -0000

Hi,

I think there is some editorial work that needs to be done, but I'll skip t=
hat for now. Some technical comments, to kick off the discussions:

Q1:

The text in 3.3 says:

	"Such INFO requests do not impact the state of Offer/Answer, nor do they h=
ave an impact on the version number in the "o=3D" line."

I think we'll need more text than this, in order to avoid confusion. For ex=
ample, if INFOs don't impact the state of Offer/Answer, does it mean that t=
he candidates will NOT be included in subsequent offer/answer transactions?=
=20

However, I assume that they WILL be impacted by an ICE re-start.


Q2:

Section 4.2 says:

	"INFO requests containing "a=3Dice-pwd:" and "a=3Dice-ufrag:" attributes t=
hat do not match those of the current ICE processing
   	session MUST be discarded."

This obviously applies if the INFO contains *OLD* pwd/ufrag values. But, I =
also assume that it is not allowed to provide *NEW* values in an INFO. If s=
o, it needs to be clarified.


Q3:

Section 4.2 says:

	"Such "a=3Dmid:" attributes MUST immediately precede the list of candidate=
s for that specific "m=3D" line."

I don't think we need to say that. It is enough that the mid attribute is a=
ssociated with the same m=3D line as the candidates. I.e. normal SDP proced=
ures apply.

Alternatively, we could actually remove the m=3D line, and replace it with =
the mid attribute (in which case the attribute obviously need to precede th=
e list of candidates).

Q4:

Section 4.2 says:

	"In every INFO request agents MUST include all local candidates they have =
previously signaled."

First, I don't think you want to include candidates that are no longer used=
, do you?=20

Second, it is also unclear whether this includes candidates that have been =
signalled using Offer/Answer (I guess Q5 answers that).

Third, do we really want to include all candidates? If we want to regard IN=
FOs as peer reflexive candidates, why not only include the new ones?


Q5:

Section 4.2 says:

  	"When receiving INFO requests carrying any candidates, agents will
   	therefore first identify and discard the SDP lines containing
   	candidates they have already received in previous INFO requests or in
   	the Offer/Answer exchange preceding them."

Where does the text says that INFOs shall carry candidates that have been s=
ignalled in Offer/Answer? The text in Q4?


Regards,

Christer





-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Thomas Stach
Sent: 17 May 2016 17:00
To: MMUSIC <mmusic@ietf.org>
Subject: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trick=
le-ice-sip-04.txt

All,

the changes from draft-ietf-mmusic-trickle-ice-sip-03 include

- replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and draft=
-ietf-mmusic-ice-sip-sdp
- corrected Figure 10, credits to Ayush Jain for finding the bug
- referencing a=3Drtcp and a=3Drtcp-mux handling from draft-ietf-mmusic-ice=
-sip-sdp
- referencing a=3Drtcp-mux-exclusive handling from draft-ietf-mmusic-mux-ex=
clusive, enhanced ABNF to support a=3Drtcp-mux-exclusive
- clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the appl=
ication/trickle-ice-sdpfrag body

Currently there are no open issues in this draft. However, it could probabl=
y benefit from a thorough review.
So, comments welcome.

With respect to progressing this work, I think that it should go forward al=
ongside with draft-ietf-ice-trickle since any updates of that document migh=
t influence the content of this draft.

Regards
Thomas



-------- Forwarded Message --------
Subject: 	New Version Notification for=20
draft-ietf-mmusic-trickle-ice-sip-04.txt
Date: 	Tue, 17 May 2016 06:50:19 -0700
From: 	internet-drafts@ietf.org
To: 	Thomas Stach <thomass.stach@gmail.com>, Emil Ivov=20
<emcho@jitsi.org>, Enrico Marocco <enrico.marocco@telecomitalia.it>,
Christer Holmberg <christer.holmberg@ericsson.com>



A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
has been successfully submitted by Thomas Stach and posted to the
IETF repository.

Name:		draft-ietf-mmusic-trickle-ice-sip
Revision:	04
Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
Document date:	2016-05-17
Group:		mmusic
Pages:		36
URL:            https://www.ietf.org/internet-drafts/draft-ietf-mmusic-tric=
kle-ice-sip-04.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-=
ice-sip/
Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-s=
ip-04
Diff:           https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-trick=
le-ice-sip-04

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

                                                                           =
       =20


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

The IETF Secretariat



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


From nobody Wed May 18 00:02:51 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7AC812D132 for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 00:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFdb6oaDEeYU for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 00:02:45 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85FDD12D12E for <mmusic@ietf.org>; Wed, 18 May 2016 00:02:45 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-f7-573c1393927f
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D6.8B.18043.3931C375; Wed, 18 May 2016 09:02:43 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0248.002; Wed, 18 May 2016 09:02:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITCAAEJsgP//O41A
Date: Wed, 18 May 2016 07:02:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu>
In-Reply-To: <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnkeLIzCtJLcpLzFFi42KZGbHdW3eysE24wY1mE4upyx+zWKzYcIDV YsaFqcwOzB5/339g8liy5CeTx60pBQHMUVw2Kak5mWWpRfp2CVwZL292MRZM5ajouveRuYFx M1sXIyeHhICJxJZN59ghbDGJC/fWA8W5OIQEjjBKLHkzAaxISGAJo8SxgwldjBwcbAIWEt3/ tEHCIgLeEhPmr2YDCTMLqEtcXRwEYgoL5Eps2+gLUZEncWHOU2YIO0qiYcEbVhCbRUBVovFz K9hwXgFfid+vHzFDbH3ALLH9/nywIk4BB4mdW8+DFTECnfb91BomEJtZQFzi1pP5TBAnC0gs 2XOeGcIWlXj5+B8rhK0k0bjkCStEvY7Egt2f2CBsbYllC18zQywWlDg58wnLBEaxWUjGzkLS MgtJyywkLQsYWVYxihanFhfnphsZ6aUWZSYXF+fn6eWllmxiBEbTwS2/rXYwHnzueIhRgINR iYc3YYp1uBBrYllxZe4hRgkOZiUR3vvMNuFCvCmJlVWpRfnxRaU5qcWHGKU5WJTEef1fKoYL CaQnlqRmp6YWpBbBZJk4OKUaGNtYRQ1O5y4UZs/lm2b9Jb7LZfOpu6oyz5iXXt9f5R167CVH Z55Id8Ocl/2en9o3vXA3O7JhL8d7nWWf7qlzFc3Y8nD1rZ0/umQ3Jgm4dOcUq5yzeapkxH4l dep74Tt6MlJKc82UX6itkivdcPHVdjkP6c4jH8pe9R3apbrifQubgyu7uPExWSWW4oxEQy3m ouJEAEKSdBKiAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/A4Zf3EEtA6pOMHyXwEwUEnNCsCs>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 07:02:50 -0000

Hi Paul,

...

>>   An endpoint MUST be able to match at least one fingerprint,
>
> Prefix the above with "For each received certificate".

What about "For each used certificate"?=20

I used "used" elsewhere, so...

> In addition, the endpoint MAY also test other fingerprints for a=20
> match, in which case each tested fingerprints MUST match the used
> certificate.
>
> That sentence isn't true when there are fingerprints for multiple certifi=
cates. How about:
>
> "In addition, the endpoint may check other hash functions present in the =
fingerprints against the=20
> certificate. For each hash function checked, one of the fingerprints MUST=
 match the certificate."

In order to align the text with the other terminology/writing style, what a=
bout:

	"In addition, the endpoint MAY also test=20
    	fingerprints calculated using other hash functions for a match.
    	For each hash function checked, one of the fingerprints MUST match=20
    	the used certificate."

Thanks!

Regards,

Christer


From nobody Wed May 18 00:18:07 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8347B12D0DB for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 00:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4k3NykAwK67f for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 00:18:05 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63C0212B02B for <mmusic@ietf.org>; Wed, 18 May 2016 00:18:03 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-82-573c172a572b
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 62.2C.27088.A271C375; Wed, 18 May 2016 09:18:02 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0248.002; Wed, 18 May 2016 09:18:02 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITCAAEJsgP//O41A//5v8GA=
Date: Wed, 18 May 2016 07:18:01 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD141C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprIIsWRmVeSWpSXmKPExsUyM2K7lq6WuE24wZw+eYupyx+zWKzYcIDV YsaFqcwOzB5/339g8liy5CeTx60pBQHMUVw2Kak5mWWpRfp2CVwZk3dfYS2Yw1Qx/dhjxgbG 54xdjJwcEgImEvd372KFsMUkLtxbz9bFyMUhJHCEUeLP9rfsEM4SRoltC5cydzFycLAJWEh0 /9MGiYsINDJKPNv+lQ0kziygLnF1cRCIKSyQK7Ftoy/ITBGBPIkLc54yQ9hJEj+OvGUBsVkE VCV6Hr8C28sr4CvRPu07M9QqFon3c1vBjuMU8JNou7QCrIgR6Ljvp9YwgdjMAuISt57MZ4I4 WkBiyZ7zzBC2qMTLx/+gnlGSaFzyhBWiXkdiwe5PbBC2tsSyha+ZIRYLSpyc+YRlAqPYLCRj ZyFpmYWkZRaSlgWMLKsYRYtTi5Ny042M9FKLMpOLi/Pz9PJSSzYxAiPq4JbfBjsYXz53PMQo wMGoxMObMMU6XIg1say4MvcQowQHs5II731mm3Ah3pTEyqrUovz4otKc1OJDjNIcLErivP4v FcOFBNITS1KzU1MLUotgskwcnFINjOHfU30ybrOtmcbTdkSdZ0bm9UO7Sjh7ulcG/ry+unzW 2YO8Oh7136+EOkjb+kf+d5NSfiSuVzwj4vvf/tzApYoKmjd0ZaatiDCqVMzbLJ9w4E+s+NSe SH5lNz93hi+OT64pf/Hdt+XXkjtrHY6KdBZ9srR+yjht9vcFx3+wTPDdr8yZEhX7V4mlOCPR UIu5qDgRAAv9MuekAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/L_Mbm23ePl63qhGKZYwq04KZM5M>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 07:18:06 -0000

Hi,

New version on github, based on latest discussions, and without a new attri=
bute:

https://github.com/cdh4u/draft-4572-update/blob/master/draft-ietf-mmusic-45=
72-update.txt

If people are ok with the text I'll submit the new version to IETF.

Regards,

Christer


From nobody Wed May 18 07:02:12 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2F7712D1E3 for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 07:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpgqc6U72pMC for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 07:02:11 -0700 (PDT)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB2D312D167 for <mmusic@ietf.org>; Wed, 18 May 2016 07:02:09 -0700 (PDT)
Received: from resomta-po-10v.sys.comcast.net ([96.114.154.234]) by comcast with SMTP id 320TbjpHXd8263236bmsT1; Wed, 18 May 2016 14:02:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463580128; bh=bLCyjuAOcQLBXG0KEu1KUSENmPfMSZoweL+vS4JbmoQ=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=q+7QXmP3A3d74MSn7KqU+DGd3HXwcqQY0hiwpIrSWuJDk3P+39IZvfDcaZBr7FSZQ PRb4y8LLTPssgzlv/iihxOklkyd+qbPGz7U7LpIEPD2JDITAPb1tskHVRVTID02ogj x9vDPnXsKD5guBlz+3b4yqYR9fMONmmDLpvy9i9nETqcc/XXIpua1fly6smDtVPTKd ZNemfYNVLUCzBpA8dEnqw+gPBkUsqceqsLD6kdddBan1Fr/NmlM8LEj5ekbsyTAK6s 5c1pA7hDuwoaXXeBhtCFcH2rfSZSLw8tJZS6lCgv4eHjrpBrkNfdYMdRmGbt07LFEs McXFBtRx1SsHw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-po-10v.sys.comcast.net with comcast id vq271s00N3KdFy101q27Ev; Wed, 18 May 2016 14:02:08 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c86f0085-e7d4-7743-8580-ace063fe61fd@alum.mit.edu>
Date: Wed, 18 May 2016 10:02:03 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/8nPW5-5NYODAQlpaV1HhzwtV-DM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 14:02:12 -0000

On 5/18/16 3:02 AM, Christer Holmberg wrote:
> Hi Paul,
>
> ...
>
>>>   An endpoint MUST be able to match at least one fingerprint,
>>
>> Prefix the above with "For each received certificate".
>
> What about "For each used certificate"?
>
> I used "used" elsewhere, so...

Fine.

>> In addition, the endpoint MAY also test other fingerprints for a
>> match, in which case each tested fingerprints MUST match the used
>> certificate.
>>
>> That sentence isn't true when there are fingerprints for multiple certificates. How about:
>>
>> "In addition, the endpoint may check other hash functions present in the fingerprints against the
>> certificate. For each hash function checked, one of the fingerprints MUST match the certificate."
>
> In order to align the text with the other terminology/writing style, what about:
>
> 	"In addition, the endpoint MAY also test
>     	fingerprints calculated using other hash functions for a match.
>     	For each hash function checked, one of the fingerprints MUST match
>     	the used certificate."

The nuance I was trying to capture is that one should not decide to test 
a hash function that isn't present in the received fingerprints. If one 
did that then of course you would find no matching fingerprint. You 
wouldn't want to reject based on that.

(Well, I guess you might, if none of the fingerprints offered are 
sufficiently trustworthy for you. But that case would be caught earlier, 
not during this "In addition" phase of checking.)

I don't think your text covers that.

	Thanks,
	Paul


From nobody Wed May 18 08:09:22 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBC2212D597 for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 08:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X4Vx3Mk7GfNQ for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 08:09:20 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89A6512D593 for <mmusic@ietf.org>; Wed, 18 May 2016 08:09:19 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-fd-573c859d4917
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 61.C6.18043.D958C375; Wed, 18 May 2016 17:09:17 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0248.002; Wed, 18 May 2016 17:09:17 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITCAAEJsgP//O41AADv5wYD//83NAA==
Date: Wed, 18 May 2016 15:09:16 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD5C6E@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se> <c86f0085-e7d4-7743-8580-ace063fe61fd@alum.mit.edu>
In-Reply-To: <c86f0085-e7d4-7743-8580-ace063fe61fd@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZGbHdSXduq024wevPhhZTlz9msVix4QCr xYwLU5kdmD3+vv/A5LFkyU8mj1tTCgKYo7hsUlJzMstSi/TtErgyFs58zV5wirfizJXzzA2M T7m6GDk4JARMJJbOFOxi5AQyxSQu3FvP1sXIxSEkcIRR4uzPi6wQzhJGiUNXP7KANLAJWEh0 /9MGaRAR8JaYMH81G0iYWUBd4uriIBBTWCBXYttGX4iKPIkLc54yQ9hZEoc3PAGzWQRUJaZO WcUKUs4r4Cuxca0OxKJbLBKrTu9nB6nhFHCQaD89HayeEei076fWMIHYzALiEreezGeCOFlA Ysme88wQtqjEy8f/WCFsJYlFtz9D1etILNj9iQ3C1pZYtvA1WD2vgKDEyZlPWCYwis1CMnYW kpZZSFpmIWlZwMiyilG0OLW4ODfdyEgvtSgzubg4P08vL7VkEyMwlg5u+W21g/Hgc8dDjAIc jEo8vAlTrMOFWBPLiitzDzFKcDArifD619qEC/GmJFZWpRblxxeV5qQWH2KU5mBREuf1f6kY LiSQnliSmp2aWpBaBJNl4uCUamCUbOeyCCrYtH3vi6Bz+8sO/z914Jyek4V05OGeiQU7d62y UnM7d8NEt1ZRrO/1lUb5w/KX7poXNE+qEzDMKnh7vfP0oX2vmupX3TD4+9/IcHHf75rmMoU4 tlMXXI+F2NUWX2NzPrl+xbuLZjnhthZqK+5+sbjv9FB7y8agDzb1JlE/X7Y6b1mjxFKckWio xVxUnAgAwAL7oKECAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KW_Je2Eu55gVcJtBJvjqbV02vZE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 15:09:21 -0000

Hi,

...

>>> In addition, the endpoint MAY also test other fingerprints for a=20
>>> match, in which case each tested fingerprints MUST match the used=20
>>> certificate.
>>>
>>> That sentence isn't true when there are fingerprints for multiple certi=
ficates. How about:
>>>
>>> "In addition, the endpoint may check other hash functions present in=20
>>> the fingerprints against the certificate. For each hash function checke=
d, one of the fingerprints MUST match the certificate."
>>
>> In order to align the text with the other terminology/writing style, wha=
t about:
>>
>> 	"In addition, the endpoint MAY also test
>>     	fingerprints calculated using other hash functions for a match.
>>     	For each hash function checked, one of the fingerprints MUST match
>>     	the used certificate."
>
> The nuance I was trying to capture is that one should not decide to test =
a hash function that isn't present
> in the received fingerprints. If one did that then of course you would fi=
nd no matching fingerprint. You wouldn't
> want to reject based on that.
>
> (Well, I guess you might, if none of the fingerprints offered are suffici=
ently trustworthy for you. But that case would be caught earlier, not durin=
g this "In addition" phase of checking.)
>
> I don't think your text covers that.

I assumed that people will test using the hash functions that have been use=
d to calculate the associated fingerprints.

Perhaps:

"In addition, the endpoint MAY also other fingerprints (calculated using ot=
her hash functions) that it has received for a match.
For each hash function checked, one of the received fingerprints MUST match=
 the used certificate."

Regards,

Christer


From nobody Wed May 18 10:08:40 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F0E12D5E3 for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 10:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6iJn8h1kGVpR for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 10:08:34 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ED4012D5DB for <mmusic@ietf.org>; Wed, 18 May 2016 10:08:34 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by comcast with SMTP id 34s6bd3WeO4QF34xVb9Y82; Wed, 18 May 2016 17:08:33 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463591313; bh=T+t4LLNTM96yXfeYL6WHH2O725F0UfGiD7MlCmf2J+U=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=bVy6YNMTiNrFy45dp/C4vcMQ4ze2ofHmpQ5kgXZs3ZMsFQeTH9jPGZ9M/d55q3hNL 6zzxvPyLvn2Fxv3K69vMVKGKP93y99O+sQUm1QxeeBUuEkzPi29fwdn8qRh0FUTtHi SWw+8AP83F3imw2tBs4aQ4VxZjJlBjZY5y3kax4fDJoSgt9aSH9S6cackrksbghsNr JVShUSK63WfRBdIgzm/E8+oQKnBIAN3NfcznkzGWElJ4fUb+FAacJ0xp5cgIYT5KOu lC+8qJ9lLYfUJcoz+BK+rryvlVm2af14gd+QILDzd40NYFB+h8vkIFkfUeVSBXznW6 2lemSeorxno1A==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-09v.sys.comcast.net with comcast id vt8Y1s0163KdFy101t8Zpw; Wed, 18 May 2016 17:08:33 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se> <c86f0085-e7d4-7743-8580-ace063fe61fd@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD5C6E@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <9d9320ee-d379-e938-0919-3531f4f15d09@alum.mit.edu>
Date: Wed, 18 May 2016 13:08:27 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FD5C6E@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/9myrRubycXVosrZHzAWG1wqsYjA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 17:08:36 -0000

On 5/18/16 11:09 AM, Christer Holmberg wrote:
> Hi,
>
> ...
>
>>>> In addition, the endpoint MAY also test other fingerprints for a
>>>> match, in which case each tested fingerprints MUST match the used
>>>> certificate.
>>>>
>>>> That sentence isn't true when there are fingerprints for multiple certificates. How about:
>>>>
>>>> "In addition, the endpoint may check other hash functions present in
>>>> the fingerprints against the certificate. For each hash function checked, one of the fingerprints MUST match the certificate."
>>>
>>> In order to align the text with the other terminology/writing style, what about:
>>>
>>> 	"In addition, the endpoint MAY also test
>>>     	fingerprints calculated using other hash functions for a match.
>>>     	For each hash function checked, one of the fingerprints MUST match
>>>     	the used certificate."
>>
>> The nuance I was trying to capture is that one should not decide to test a hash function that isn't present
>> in the received fingerprints. If one did that then of course you would find no matching fingerprint. You wouldn't
>> want to reject based on that.
>>
>> (Well, I guess you might, if none of the fingerprints offered are sufficiently trustworthy for you. But that case would be caught earlier, not during this "In addition" phase of checking.)
>>
>> I don't think your text covers that.
>
> I assumed that people will test using the hash functions that have been used to calculate the associated fingerprints.

Safest never to assume.

> Perhaps:
>
> "In addition, the endpoint MAY also other fingerprints (calculated using other hash functions) that it has received for a match.
> For each hash function checked, one of the received fingerprints MUST match the used certificate."

Missing word above. s/also/also check/

Otherwise this seems good.

	Thanks,
	Paul


From nobody Wed May 18 10:24:45 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2C012D5FF for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 10:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AK9waB-GVQDN for <mmusic@ietfa.amsl.com>; Wed, 18 May 2016 10:24:42 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0459512D5F8 for <mmusic@ietf.org>; Wed, 18 May 2016 10:24:41 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-de-573ca557a8fd
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F3.3B.12516.755AC375; Wed, 18 May 2016 19:24:40 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0248.002; Wed, 18 May 2016 19:24:36 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITCAAEJsgP//O41AADv5wYD//83NAP//mbiA//8ObaA=
Date: Wed, 18 May 2016 17:24:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD5DCF@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <e4f91889-0202-6eda-0e44-94bfa7d1e6ca@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD13CD@ESESSMB209.ericsson.se> <c86f0085-e7d4-7743-8580-ace063fe61fd@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FD5C6E@ESESSMB209.ericsson.se> <9d9320ee-d379-e938-0919-3531f4f15d09@alum.mit.edu>
In-Reply-To: <9d9320ee-d379-e938-0919-3531f4f15d09@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjkeLIzCtJLcpLzFFi42KZGbHdTzdiqU24waP5HBZTlz9msVix4QCr xYwLU5kdmD3+vv/A5LFkyU8mj1tTCgKYo7hsUlJzMstSi/TtErgyun7yFBzlr1jU9Y2lgXEb TxcjJ4eEgInEjQe/GSFsMYkL99azdTFycQgJHGGU2HjgHhNIQkhgCaPEzg96XYwcHGwCFhLd /7RBwiIC3hIT5q9mAwkzC6hLXF0cBGIKC+RKbNvoC1GRJ3FhzlNmCLtM4viTGewgNouAqkTn 5zlgNq+Ar8StKy9ZIbZeYZU4Pf8qG0iCU8BBYkPnCbDTGIFO+35qDdg1zALiEreezGeCOFlA Ysme88wQtqjEy8f/WCFsJYkV2y8xQtTrSCzY/YkNwtaWWLbwNTPEYkGJkzOfsExgFJuFZOws JC2zkLTMQtKygJFlFaNocWpxcW66kbFealFmcnFxfp5eXmrJJkZgLB3c8lt3B+Pq146HGAU4 GJV4eBOmWIcLsSaWFVfmHmKU4GBWEuGNWGITLsSbklhZlVqUH19UmpNafIhRmoNFSZzX/6Vi uJBAemJJanZqakFqEUyWiYNTqoFxqcB1lX91Ftrx0b2fZTsjP1r4vm5e47+7iP38hdWfvxpy ij394lvruL1wpUGMueAFvmlGvDP05rJyFhl+dp2yJIOHc1WS4A3/012VC5NM5VcwzZltpyr3 Ze4D17A5Yeqn7ly7WFbVbWYhvL5/2cvexXmrT9zWCkre8vD2SQaZXUIqguGe8VVKLMUZiYZa zEXFiQAC/TbPoQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/KdxdWpzov1oYLlVkoW0CvpzYT-c>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 17:24:43 -0000

Hi,

>>>>> In addition, the endpoint MAY also test other fingerprints for a=20
>>>>> match, in which case each tested fingerprints MUST match the used=20
>>>>> certificate.
>>>>>
>>>>> That sentence isn't true when there are fingerprints for multiple cer=
tificates. How about:
>>>>>
>>>>> "In addition, the endpoint may check other hash functions present=20
>>>>> in the fingerprints against the certificate. For each hash function c=
hecked, one of the fingerprints MUST match the certificate."
>>>>
>>>> In order to align the text with the other terminology/writing style, w=
hat about:
>>>>
>>>> 	"In addition, the endpoint MAY also test
>>>>     	fingerprints calculated using other hash functions for a match.
>>>>     	For each hash function checked, one of the fingerprints MUST matc=
h
>>>>     	the used certificate."
>>>
>>> The nuance I was trying to capture is that one should not decide to=20
>>> test a hash function that isn't present in the received fingerprints.=20
>>> If one did that then of course you would find no matching fingerprint. =
You wouldn't want to reject based on that.
>>>
>>> (Well, I guess you might, if none of the fingerprints offered are=20
>>> sufficiently trustworthy for you. But that case would be caught=20
>>> earlier, not during this "In addition" phase of checking.)
>>>
>>> I don't think your text covers that.
>>
>> I assumed that people will test using the hash functions that have been =
used to calculate the associated fingerprints.
>
> Safest never to assume.
>
>> Perhaps:
>>
>> "In addition, the endpoint MAY also other fingerprints (calculated using=
 other hash functions) that it has received for a match.
>> For each hash function checked, one of the received fingerprints MUST ma=
tch the used certificate."
>
> Missing word above. s/also/also check/

Correct.

> Otherwise this seems good.

Thanks! I'll update the text and submit the -02 version.

Regards,

Christer


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

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

        Title           : Updates to RFC 4572
        Author          : Christer Holmberg
	Filename        : draft-ietf-mmusic-4572-update-02.txt
	Pages           : 7
	Date            : 2016-05-18

Abstract:
   This document updates RFC 4572 by clarifying the usage of multiple
   SDP 'fingerprint' attributes with a single TLS connection.  The
   document also updates the preferred cipher suite to be used, and
   removes the requirement to use the same hash function for calculating
   a certificate fingerprint that is used to calculate the certificate
   signature.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-02

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


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 May 18 10:51:35 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314E912D616; Wed, 18 May 2016 10:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gPlLRBJiP88s; Wed, 18 May 2016 10:51:33 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5801712D617; Wed, 18 May 2016 10:51:32 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-93-573caba2dddb
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id D8.3E.12516.2ABAC375; Wed, 18 May 2016 19:51:30 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0248.002; Wed, 18 May 2016 19:51:29 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-4572-update-02
Thread-Index: AdGxLPtOKSB54+JJR1WeU6ADzSMFvQ==
Date: Wed, 18 May 2016 17:51:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD5E99@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FD5E99ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGbE9SnfRaptwg0l9Qhbnd65nspi6/DGL A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyWvdNYS6Ya1DR2PiGtYFxklYXIyeHhICJxPYt/9kg bDGJC/fWA9lcHEICRxglLi45zwrhLGGUmPZxA2MXIwcHm4CFRPc/bZAGEQF1ia97e5hBbGYB U4mHr9YwgtjCAjYSd3+cZ4KocZTYs3YSI4StJ7Hv52RWEJtFQFXiWEM/O4jNK+Arse/CAbA4 I9AR30+tYYKYKS5x68l8JojjBCSW7DnPDGGLSrx8/I8VwlaSWLH9EiNEfb5E77seFoiZghIn Zz5hmcAoPAvJqFlIymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGEWLU4uLc9ON jPVSizKTi4vz8/TyUks2MQKj5uCW37o7GFe/djzEKMDBqMTDmzDFOlyINbGsuDL3EKMEB7OS CG/SKptwId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rz+LxXDhQTSE0tSs1NTC1KLYLJMHJxSDYzT PrzkXyrvuSxi4Vuz96y/rk34v2bZ79XfVEvnimxts1w26dOKhytzr9U/DL9217pBdVJB1Yps 34LPQSqpD5slIgOSij8/Xv3lrDrv1aREll6N+YWRjn1pUmvFTHZ2TTtY+LiRNcby9aXX/o/9 T1lzrT7kWJag/3H5w2nycWezbG84fjy2Xi1OiaU4I9FQi7moOBEAQjfP1ZYCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Q-iFQiMMPaSsc1JXNcoQU64qhgs>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-02
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 17:51:34 -0000

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

Hi,

Based on the e-mail discussions, I've submitted a new version (-02) of draf=
t-ietf-mmusic-4572-update.

Note that the draft does NOT define a new attribute. If people want to do t=
hat, we'll discuss it as a separate issue.

There are currently no open issues, and personally I see the draft more or =
less done, so in my opinion we can start thinking about WGLC. There I encou=
rage people to take a look, if there are still any issues we need to addres=
s before WGLC.

Thanks to everyone who participated in the discussions!

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37FD5E99ESESSMB209erics_
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
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;}
/* List Definitions */
@list l0
	{mso-list-id:1170826868;
	mso-list-type:hybrid;
	mso-list-template-ids:323405814 953060964 134807555 134807557 134807553 13=
4807555 134807557 134807553 134807555 134807557;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#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">Based on the e-mail discussions, I&#8217;ve submitte=
d a new version (-02) of draft-ietf-mmusic-4572-update.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Note that the draft does NOT define a new attribute.=
 If people want to do that, we&#8217;ll discuss it as a separate issue.<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are currently no open issues, and personally I=
 see the draft more or less done, so in my opinion we can start thinking ab=
out WGLC. There I encourage people to take a look, if there are still any i=
ssues we need to address before WGLC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks to everyone who participated in the discussio=
ns! <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_7594FB04B1934943A5C02806D1A2204B37FD5E99ESESSMB209erics_--


From nobody Thu May 19 06:46:26 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9989112B058 for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 06:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgXj1QsP612A for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 06:46:24 -0700 (PDT)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AEC512D13D for <mmusic@ietf.org>; Thu, 19 May 2016 06:46:23 -0700 (PDT)
Received: by mail-ig0-x22c.google.com with SMTP id bi2so115830703igb.0 for <mmusic@ietf.org>; Thu, 19 May 2016 06:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=oHYbgAsxwd3vf2Lwitdic1boIjYbyAzw8ZBcb+mNs9k=; b=V58IwKHNHsuF7RKl2vrsFPZYHqHMh01sieEIQg8CcOy5+zGc89x09Fb7mritWhIoCv N+NryhQ8iNdqh/OsebkhmxIaJBCBArGNZVQiTfDXAQjcKwMZaOWrGRcMm4JgxuF8wwsf ZBLpkiIB21fjo2mh728UFeB+Z7UuLBXf+v6cwDvnWNAhoeaABGxfczAwuGGtOfLuS2Ic nY4yUkp1qEG2hqDcA2HXmf3hwu9qJl2CbAtHtXULoBhRLnwDyZeBfiq/pRJrdoI2rrCz fu97uPY7YiwLOEV+wyfpf27P3YHUS/tM8KSM7jrEm+hVJp4dB0JkAYX3LqjqlgRX20uh Av2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=oHYbgAsxwd3vf2Lwitdic1boIjYbyAzw8ZBcb+mNs9k=; b=CAqB9+iNbD+3EJLzSDdq+3BDWkjR+mQA5vROKQjAP3a7SUkbQk2tDfXtzRJ9PKdrQj TWFDMQt5aX574uaMTFhQ83Gli+btY0we70F0b01D4h3YF4TjyBKNwL+xmpQfrCrtCdl/ foePPVZsTeHqOVM+por47/RskGiGkmQnmiHEwkRfPjMuBRQnkpZz80qBfWr6Y3X6mVo9 i9xs8EsIj1kEkeZWXPUgq49nHuU4jKGfhT6eWSEHlVt3n6jrLmF3YlICUKKujhOQaAIZ 3GJZ+5/72CjM8aH43s7KMCx0aHpmU3aiL9iPOxaaoEYV6Or+PFeBnwC0/+2hrhd4JoOT AVyg==
X-Gm-Message-State: AOPr4FXJeEX5woD/bVu9kEQN/77xUJaccWO5b3lhPIRxIosm0w8qkvmO8v/PDRQxfBbQTYFO+jKSUnev9y2L+g==
MIME-Version: 1.0
X-Received: by 10.50.58.71 with SMTP id o7mr3117931igq.77.1463665582575; Thu, 19 May 2016 06:46:22 -0700 (PDT)
Received: by 10.36.142.4 with HTTP; Thu, 19 May 2016 06:46:22 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se>
Date: Thu, 19 May 2016 09:46:22 -0400
Message-ID: <CABkgnnXc_c_Wu8V0HX9Kt4+GEuSSK8noyKkTS+gNEbNBs_0GQQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/qapLsfn75U-8iKgicMTvMbdrwbo>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 13:46:25 -0000

https://avatars3.githubusercontent.com/u/67641?v=3&s=460

On 17 May 2016 at 16:47, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> In
>
>     addition, the endpoint MAY also test other fingerprints for a match
>     , in which case each tested fingerprints MUST match the used
>     certificate.

This could be a little clearer; because it could be interpreted as
meaning that all fingerprints have to match.  How about.  ... in which
case, matching MUST fail unless a match is found for every hash
function that is tested.


From nobody Thu May 19 06:47:21 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3276112D137 for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 06:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0_8Wb7VpzQ3 for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 06:47:19 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DF712D12F for <mmusic@ietf.org>; Thu, 19 May 2016 06:47:18 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id i75so107493980ioa.3 for <mmusic@ietf.org>; Thu, 19 May 2016 06:47:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Uova7oL9KSNSV6H6Cznmpp2ihUXnJFGFbyS7m0ECZdM=; b=YT7cg42ABh0trlyJizeg3bEbrUgqXqqzQW/N1L/5gmmOB61yZblmO+aYmEIJQaLFHW NQclQZxSVjQwItm+Pj+ecZXnv1sLIrCWQt5LxYAj0ZDXUQzxco2f7dLnW+99GdwZW9dm wez1XCHEonvkzN1Z/7a3dUgW0YhDKoy6NSGZNbWIoHynexnLhau27iEjssNYFs8JCIPX Rr4hPOVDtpzydjevaahDGMsiWdp/FEYR/3Je5wn9FwIFhOA4wvtpus+RnLxKD9H4Pr6i /bprmkfOz8nOOQ/C0saiSSPWSJDQdLC0KaSqdYM287KWpKgoHPjOcCoKskPk4gpYF9r0 avaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Uova7oL9KSNSV6H6Cznmpp2ihUXnJFGFbyS7m0ECZdM=; b=kj7MyQjXpuVgJxfD988t/t4Yx2XWKnGO4yLe9JLX3FvMCW2E1Ob9bDaTIXzGyTFFA+ /WohhKpgUbYNg7ge/CKkED5TcJ0++j4yFBK0LkY2Mm2Ssi/iLSPe+kUcrmhAVSew+83j G0Peqw2QmygvvGEsqZgg6z+8l7IZn3ht8z0BfH+dX9wBvO2kJ9m0JH/sBFuaeIjeZPla k0cwUeY/OiYiM/QfpKSDShc9RIzaQDYz7uTDv96ZBwPaL8NmivmkNtevb/gL/9apg/2r ubB11tHkQJmKGYWKoMG78z5Sd/mpygpH/bRwCQNRmId22XaqUxPFZgNG3cG7sDrPF5tP c2KQ==
X-Gm-Message-State: AOPr4FXGPXfdDLOn7g3O/T8qN7mK2qkmWu/VdL8M8rX7wmN+OysmMgExzR/W09HqpAdZiCHYgbBA7iF0As2FNA==
MIME-Version: 1.0
X-Received: by 10.107.136.76 with SMTP id k73mr10199095iod.100.1463665638385;  Thu, 19 May 2016 06:47:18 -0700 (PDT)
Received: by 10.36.142.4 with HTTP; Thu, 19 May 2016 06:47:18 -0700 (PDT)
In-Reply-To: <CABkgnnXc_c_Wu8V0HX9Kt4+GEuSSK8noyKkTS+gNEbNBs_0GQQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <CABkgnnXc_c_Wu8V0HX9Kt4+GEuSSK8noyKkTS+gNEbNBs_0GQQ@mail.gmail.com>
Date: Thu, 19 May 2016 09:47:18 -0400
Message-ID: <CABkgnnXjoY4urEcmGBiZMJ3vMxqkqjRkUNS_ezHg1_1uWVfysA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/YY7XJXL9GL1rt-icV6ujOO1FcG0>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 13:47:20 -0000

On 19 May 2016 at 09:46, Martin Thomson <martin.thomson@gmail.com> wrote:
> This could be a little clearer; because it could be interpreted as
> meaning that all fingerprints have to match.  How about.  ... in which
> case, matching MUST fail unless a match is found for every hash
> function that is tested.


I should read the thread before replying.  Paul caught this too and
his text is probably better than mine.


From nobody Thu May 19 11:40:14 2016
Return-Path: <thomass.stach@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E7FD12DBCD for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 11:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R7C60OQ7ZaFk for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 11:40:09 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCDDC12DBE0 for <mmusic@ietf.org>; Thu, 19 May 2016 11:34:49 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id n129so48728761wmn.1 for <mmusic@ietf.org>; Thu, 19 May 2016 11:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=owvqNvJthbCr77EP3e4HYDqYl4Z4bqraJnkOHwBM6jc=; b=kaUWP0VBchqtE2gfGyEb3reIVweg1kC7II+rGFSC9iOWLWF8IfHHAl8OhM4baezcbi 8gyi6pg+QL56n5DTanPxPbt4Q4fHnjJNnN4eG1/GZLlB+xEaW6pG+iNz8eAnOPXUe3aw tcKDzovPqsCg4j6CFgw1uUhUTgP+swlVq8XRZU+rxPQlzr1joHkU439hZwUUd52E6lDP +SSwRUu8BOxh7p9ncRvSlBCZCgZT1QOCTRmwGt/NUwTgjWLLqIxcvY0e1fBxNA3x3jxV u4iZyBrYUq6gGxgOoCtHN7Xsxcs/tnyxA3SwXHfZWBHZBsTbuI4Ifv9LpCPgmH0efBm8 j1vw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=owvqNvJthbCr77EP3e4HYDqYl4Z4bqraJnkOHwBM6jc=; b=NO+BtfOrEWIrH4Qh77jQ4TRCxqenNPfW287dPfEPw9wotzkQCrgGaaYWPWOEIMxZ63 jugC/IU1O+5nxfEIXVdERxsP/nh5TjdrH+p5i2fdbQ2lrDC4ttKYHQjo0ud47zmn54QJ YwtzZAObyXmSiMuybnmFP3NEe+c0pbsbBSx6/E3dPTH/YL2Nb0lRJtrV0OdWuIP7FNnQ 0r4hxPAezNa/v8bmtTYxF4PFHUMDggUuuUY/lzpE6x9r/nJ1wxttQHJjsOeQcIZl28Bc 96EuTBlzQcUpe41o++tpqtVNZCnw7tv1GTvwea/OGFxQkg6JLnBMeCODkEdSsx5iyehs yh3A==
X-Gm-Message-State: AOPr4FV0zvUtxXfZFpy4Ms5iNLO0t+OCiW+zxNUdYxxHHayo1wRikOGgZYHG2to7nl7SkA==
X-Received: by 10.28.128.138 with SMTP id b132mr5506989wmd.53.1463682888031; Thu, 19 May 2016 11:34:48 -0700 (PDT)
Received: from [192.168.2.109] (d91-130-21-47.cust.tele2.at. [91.130.21.47]) by smtp.googlemail.com with ESMTPSA id yr1sm15736007wjc.9.2016.05.19.11.34.46 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 May 2016 11:34:46 -0700 (PDT)
From: Thomas Stach <thomass.stach@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, MMUSIC <mmusic@ietf.org>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se>
Message-ID: <573E0745.3010606@gmail.com>
Date: Thu, 19 May 2016 20:34:45 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RbHd3ZAnMAsXQsv_JnYuHY8wiv4>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 18:40:12 -0000

Christer,

thanks for reviewing.
more inline

On 2016-05-17 23:22, Christer Holmberg wrote:
> Hi,
>
> I think there is some editorial work that needs to be done, but I'll skip that for now. Some technical comments, to kick off the discussions:
>
> Q1:
>
> The text in 3.3 says:
>
> 	"Such INFO requests do not impact the state of Offer/Answer, nor do they have an impact on the version number in the "o=" line."
>
> I think we'll need more text than this, in order to avoid confusion. For example, if INFOs don't impact the state of Offer/Answer, does it mean that the candidates will NOT be included in subsequent offer/answer transactions?
No, in a subsequent offer/answer transaction you would include the 
actual set of candidates, i.e.  in case you use 100rel and do a second 
O/A before the 200OK to the INVITE, you would include in the offer the 
candidates present in the initial offer and all candidates there were 
trickled in the meantime.
>
> However, I assume that they WILL be impacted by an ICE re-start.
In case of a restart everything starts from scratch.
>
>
> Q2:
>
> Section 4.2 says:
>
> 	"INFO requests containing "a=ice-pwd:" and "a=ice-ufrag:" attributes that do not match those of the current ICE processing
>     	session MUST be discarded."
>
> This obviously applies if the INFO contains *OLD* pwd/ufrag values. But, I also assume that it is not allowed to provide *NEW* values in an INFO. If so, it needs to be clarified.
Correct, the current text does not allow this. I can clarify.
>
>
> Q3:
>
> Section 4.2 says:
>
> 	"Such "a=mid:" attributes MUST immediately precede the list of candidates for that specific "m=" line."
>
> I don't think we need to say that. It is enough that the mid attribute is associated with the same m= line as the candidates. I.e. normal SDP procedures apply.
You're right, it is not strictly needed. However, the current text was 
the outcome of a longer discussion with Paul Kyzivat. I would have to 
look up the details that lead to this format.
Additonally, as the grammar for the info-package is written in a way 
that prescribes the order of the attributes, I'd prefer to keep it as 
is, unless there is a real need for more flexibility.
Others?
> Alternatively, we could actually remove the m= line, and replace it with the mid attribute (in which case the attribute obviously need to precede the list of candidates).
> Q4:
>
> Section 4.2 says:
>
> 	"In every INFO request agents MUST include all local candidates they have previously signaled."
>
> First, I don't think you want to include candidates that are no longer used, do you?
What do you mean by no longer used?
>
> Second, it is also unclear whether this includes candidates that have been signalled using Offer/Answer
> (I guess Q5 answers that).
>
> Third, do we really want to include all candidates? If we want to regard INFOs as peer reflexive candidates, why not only include the new ones?
Always including the complete set of candidates (i.e. those from the 
initial offeror answer plus the ones that were trickled afterwards) is 
motivated by the infamous support for UDP transport in SIP. In order to 
have things simple we decided already in the early days of this draft to 
always have the complete set in the INFO. Then, you don't need to care 
about lost INFOs and can just drop any late arrivals.
>
>
> Q5:
>
> Section 4.2 says:
>
>    	"When receiving INFO requests carrying any candidates, agents will
>     	therefore first identify and discard the SDP lines containing
>     	candidates they have already received in previous INFO requests or in
>     	the Offer/Answer exchange preceding them."
>
> Where does the text says that INFOs shall carry candidates that have been signalled in Offer/Answer? The text in Q4?
Yes

Regards
Thomas
>
>
> Regards,
>
> Christer
>
>
>
>
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Thomas Stach
> Sent: 17 May 2016 17:00
> To: MMUSIC<mmusic@ietf.org>
> Subject: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
>
> All,
>
> the changes from draft-ietf-mmusic-trickle-ice-sip-03 include
>
> - replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and draft-ietf-mmusic-ice-sip-sdp
> - corrected Figure 10, credits to Ayush Jain for finding the bug
> - referencing a=rtcp and a=rtcp-mux handling from draft-ietf-mmusic-ice-sip-sdp
> - referencing a=rtcp-mux-exclusive handling from draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support a=rtcp-mux-exclusive
> - clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the application/trickle-ice-sdpfrag body
>
> Currently there are no open issues in this draft. However, it could probably benefit from a thorough review.
> So, comments welcome.
>
> With respect to progressing this work, I think that it should go forward alongside with draft-ietf-ice-trickle since any updates of that document might influence the content of this draft.
>
> Regards
> Thomas
>
>
>
> -------- Forwarded Message --------
> Subject: 	New Version Notification for
> draft-ietf-mmusic-trickle-ice-sip-04.txt
> Date: 	Tue, 17 May 2016 06:50:19 -0700
> From: 	internet-drafts@ietf.org
> To: 	Thomas Stach<thomass.stach@gmail.com>, Emil Ivov
> <emcho@jitsi.org>, Enrico Marocco<enrico.marocco@telecomitalia.it>,
> Christer Holmberg<christer.holmberg@ericsson.com>
>
>
>
> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
> has been successfully submitted by Thomas Stach and posted to the
> IETF repository.
>
> Name:		draft-ietf-mmusic-trickle-ice-sip
> Revision:	04
> Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
> Document date:	2016-05-17
> Group:		mmusic
> Pages:		36
> URL:https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice-sip-04.txt
> Status:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
> Htmlized:https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-04
> Diff:https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-04
>
> Abstract:
>      The Interactive Connectivity Establishment (ICE) protocol describes a
>      Network Address Translator (NAT) traversal mechanism for UDP-based
>      multimedia sessions established with the Offer/Answer model.  The ICE
>      extension for Incremental Provisioning of Candidates (Trickle ICE)
>      defines a mechanism that allows ICE agents to shorten session
>      establishment delays by making the candidate gathering and
>      connectivity checking phases of ICE non-blocking and by executing
>      them in parallel.
>
>      This document defines usage semantics for Trickle ICE with the
>      Session Initiation Protocol (SIP).
>
>                                                                                     
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu May 19 12:33:33 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F6912DAFC for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 12:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YsIN_8XODB1T for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 12:33:29 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1227212D5AB for <mmusic@ietf.org>; Thu, 19 May 2016 12:33:28 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-1e-573e15069ad5
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 2F.2A.12516.6051E375; Thu, 19 May 2016 21:33:27 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0248.002; Thu, 19 May 2016 21:32:04 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, MMUSIC <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
Thread-Index: AQHRsEMOIliX14uf2EKWpAtozqzJo5+9BuOAgACWdbCAAtrVgIAALipg
Date: Thu, 19 May 2016 19:32:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD9934@ESESSMB209.ericsson.se>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se> <573E0745.3010606@gmail.com>
In-Reply-To: <573E0745.3010606@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2J7iC67qF24wWdTi6nLH7NYfDqxlcmB yWPnrLvsHkuW/GQKYIrisklJzcksSy3St0vgyji6qoOx4JBDxcVbc9gaGFcadzFyckgImEjc vPGcFcIWk7hwbz1bFyMXh5DAEUaJixt3sUA4Sxgl+uc8Zepi5OBgE7CQ6P6nDdIgIuAi8ejF DHYQW1ggSWLvksNMEPFkiVtHn7FA2G4SG++sB4uzCKhKrHi1hhHE5hXwlZi35zrU/MOMEg93 rgYr4hTQlDizdi+YzQh00fdTa8BsZgFxiVtP5jNBXCogsWTPeWYIW1Ti5eN/UB8oSaw9vJ0F ol5HYsHuT2wQtrbEsoWvmSEWC0qcnPmEZQKj6CwkY2chaZmFpGUWkpYFjCyrGEWLU4uLc9ON jPVSizKTi4vz8/TyUks2MQLj5OCW37o7GFe/djzEKMDBqMTDqyBnGy7EmlhWXJl7iFGCg1lJ hNdQxC5ciDclsbIqtSg/vqg0J7X4EKM0B4uSOK//S8VwIYH0xJLU7NTUgtQimCwTB6dUA2Mu /0X+64fS9hxT+LXMWajT0c252qt9zw9J76VbN4uIGwWkxmh/enNi++oMm3PPeF1XB7uxuR0/ mpDzW2CigmXrcXfjCY1OUe+MFa99zbZKlFDpWdK26dIsjeo29wv/1D4HmnjZhUTKzb6tFud/ eLlVaemjX3PqoqbKrGjNKKi+6swmf99BTomlOCPRUIu5qDgRADiS5H2PAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/3jP0qyJy7SGSQOPz7ihzpEdn4No>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 19:33:32 -0000

Hi,

See inline.

Q1:

>> The text in 3.3 says:
>>
>> 	"Such INFO requests do not impact the state of Offer/Answer, nor do the=
y have an impact on the version number in the "o=3D" line."
>>
>> I think we'll need more text than this, in order to avoid confusion. For=
 example, if INFOs don't impact the=20
>> state of Offer/Answer, does it mean that the candidates will NOT be incl=
uded in subsequent offer/answer transactions?
>
> No, in a subsequent offer/answer transaction you would include the actual=
 set of candidates, i.e.  in case you use 100rel=20
> and do a second O/A before the 200OK to the INVITE, you would include in =
the offer the candidates present in the initial=20
> offer and all candidates there were trickled in the meantime.

Well, then the INFO *does* impact the Offer/Answer state, doesn't it - assu=
ming the set of candidates is part of the O/A state?

Also, assume candidates A, B and C are included in the offer/answer transac=
tion, and then the INFO contains (for whatever reason) candidates A and B. =
What is the state of C? Can INFO be used to *remove* previously negotiated =
candidates`?


>> However, I assume that they WILL be impacted by an ICE re-start.
> In case of a restart everything starts from scratch.

Needs to be explicitly indicated.


Q2:

>> Section 4.2 says:
>>
>> 	"INFO requests containing "a=3Dice-pwd:" and "a=3Dice-ufrag:" attribute=
s that do not match those of the current ICE processing
>>     	session MUST be discarded."
>>
> This obviously applies if the INFO contains *OLD* pwd/ufrag values. But, =
I also assume that it is not allowed to provide *NEW* values in an INFO. If=
 so, it needs to be clarified.
> Correct, the current text does not allow this. I can clarify.

Ok.



Q3:

>> Section 4.2 says:
>>
>> 	"Such "a=3Dmid:" attributes MUST immediately precede the list of candid=
ates for that specific "m=3D" line."
>>
>> I don't think we need to say that. It is enough that the mid attribute i=
s associated with the same m=3D line as the candidates. I.e. normal SDP pro=
cedures apply.
> You're right, it is not strictly needed. However, the current text was th=
e outcome of a longer discussion with Paul Kyzivat. I would have to look up=
 the details that lead to this format.
> Additionally, as the grammar for the info-package is written in a way tha=
t prescribes the order of the attributes, I'd prefer to keep it as is, unle=
ss there is a real need for more flexibility.

So, what happens if the mid attribute is NOT where it is supposed to be? Sh=
all the receiver reject the trickled candidates(s)?

That brings up another question: how does a receiver reject received candid=
ates? Remember that the receiver will always send 200 OK to the INFO reques=
t.


>> Alternatively, we could actually remove the m=3D line, and replace it wi=
th the mid attribute (in which case the attribute obviously need to precede=
 the list of candidates).
>> Q4:
>>
>> Section 4.2 says:
>>
>> 	"In every INFO request agents MUST include all local candidates they ha=
ve previously signaled."
>>
>> First, I don't think you want to include candidates that are no longer u=
sed, do you?
> What do you mean by no longer used?

Candidates that were used before a re-start, or have been removed/disabled =
using some other means.


>> Second, it is also unclear whether this includes candidates that have=20
>> been signalled using Offer/Answer (I guess Q5 answers that).
>>
>> Third, do we really want to include all candidates? If we want to regard=
 INFOs as peer reflexive candidates, why not only include the new ones?
> Always including the complete set of candidates (i.e. those from the init=
ial offeror answer plus the ones that were trickled afterwards) is motivate=
d by the infamous support for UDP transport in SIP.

Infamous? Also keep in mind that STUN is transported over UDP, so peer refl=
exive candidates are in no better position.

> In order to have things simple we decided already in the early days of th=
is draft to always have the complete set in the INFO.
> Then, you don't need to care about lost INFOs and can just drop any late =
arrivals.

Well, late arrivals should be dropped anyway.


Q5:

>> Section 4.2 says:
>>
>>    	"When receiving INFO requests carrying any candidates, agents will
>>     	therefore first identify and discard the SDP lines containing
>>     	candidates they have already received in previous INFO requests or =
in
>>     	the Offer/Answer exchange preceding them."
>>
>> Where does the text says that INFOs shall carry candidates that have bee=
n signalled in Offer/Answer? The text in Q4?
> Yes

Ok.

Regards,

Christer

>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Thomas=20
> Stach
> Sent: 17 May 2016 17:00
> To: MMUSIC<mmusic@ietf.org>
> Subject: [MMUSIC] Fwd: New Version Notification for=20
> draft-ietf-mmusic-trickle-ice-sip-04.txt
>
> All,
>
> the changes from draft-ietf-mmusic-trickle-ice-sip-03 include
>
> - replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and=20
> draft-ietf-mmusic-ice-sip-sdp
> - corrected Figure 10, credits to Ayush Jain for finding the bug
> - referencing a=3Drtcp and a=3Drtcp-mux handling from=20
> draft-ietf-mmusic-ice-sip-sdp
> - referencing a=3Drtcp-mux-exclusive handling from=20
> draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support=20
> a=3Drtcp-mux-exclusive
> - clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the=20
> application/trickle-ice-sdpfrag body
>
> Currently there are no open issues in this draft. However, it could proba=
bly benefit from a thorough review.
> So, comments welcome.
>
> With respect to progressing this work, I think that it should go forward =
alongside with draft-ietf-ice-trickle since any updates of that document mi=
ght influence the content of this draft.
>
> Regards
> Thomas
>
>
>
> -------- Forwarded Message --------
> Subject: 	New Version Notification for
> draft-ietf-mmusic-trickle-ice-sip-04.txt
> Date: 	Tue, 17 May 2016 06:50:19 -0700
> From: 	internet-drafts@ietf.org
> To: 	Thomas Stach<thomass.stach@gmail.com>, Emil Ivov
> <emcho@jitsi.org>, Enrico Marocco<enrico.marocco@telecomitalia.it>,
> Christer Holmberg<christer.holmberg@ericsson.com>
>
>
>
> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
> has been successfully submitted by Thomas Stach and posted to the IETF=20
> repository.
>
> Name:		draft-ietf-mmusic-trickle-ice-sip
> Revision:	04
> Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
> Document date:	2016-05-17
> Group:		mmusic
> Pages:		36
> URL:https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice
> -sip-04.txt=20
> Status:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-
> sip/
> Htmlized:https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip
> -04
> Diff:https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-trickle-ice-s
> ip-04
>
> 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 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.
>
>      This document defines usage semantics for Trickle ICE with the
>      Session Initiation Protocol (SIP).
>
>                                                                          =
          =20
>
>
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu May 19 12:33:55 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1E5C12D182 for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 12:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cM7tcQn_ZChM for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 12:33:49 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9662012DC0A for <mmusic@ietf.org>; Thu, 19 May 2016 12:33:48 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-0e-573e151ab807
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 86.B4.12926.A151E375; Thu, 19 May 2016 21:33:47 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0248.002; Thu, 19 May 2016 21:32:58 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITCAAuu6AIAAAEIA//9+FNA=
Date: Thu, 19 May 2016 19:32:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FD995A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <CABkgnnXc_c_Wu8V0HX9Kt4+GEuSSK8noyKkTS+gNEbNBs_0GQQ@mail.gmail.com> <CABkgnnXjoY4urEcmGBiZMJ3vMxqkqjRkUNS_ezHg1_1uWVfysA@mail.gmail.com>
In-Reply-To: <CABkgnnXjoY4urEcmGBiZMJ3vMxqkqjRkUNS_ezHg1_1uWVfysA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKIsWRmVeSWpSXmKPExsUyM2K7t660qF24weKbjBbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsEroxFzRkF T1gqFjffZmxgvMLSxcjJISFgItHy/wk7hC0mceHeerYuRi4OIYEjjBK7l35iBkkICSxhlJiz PrSLkYODTcBCovufNkhYREBXYtHZB2C9zAJFEk0LNrOAlAgL5Eps2+gLUZIncWHOU2aQsIhA ksS03/ogJouAqsSCa5EgFbwCvhJnn+1jhli6g0Wib8tuNpAEp0CgxOytt8CmMwJd9v3UGiaI TeISt57MZ4K4WEBiyZ7zzBC2qMTLx/9YIWwlibWHt4NdwyygKbF+lz5Eq6LElO6H7BB7BSVO znzCMoFRbBaSqbMQOmYh6ZiFpGMBI8sqRtHi1OKk3HQjY73Uoszk4uL8PL281JJNjMDIOrjl t+oOxstvHA8xCnAwKvHwKsjZhguxJpYVV+YeYpTgYFYS4TUUsQsX4k1JrKxKLcqPLyrNSS0+ xCjNwaIkzuv/UjFcSCA9sSQ1OzW1ILUIJsvEwSnVwJhfqpCyTGre5svndmxwO1ykuXp7/pO2 8llXpC7sOPgy5eHpbaYsr6TnBG49O3d6fx1nyp852yYyLtkWZmekGe3D//n+XaPyd3MlG6OZ ZhSIicvND3wmsnLGd2u7+5N3/TXp3a/3cwObxaZJXOvLP36aNFW6mXPvpFjXzke7uR3Wcakf fX9tnX+sEktxRqKhFnNRcSIARkeHcagCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Dv6Mi1d1OyQvzUTOF5Q0ZfkdBfU>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 19:33:55 -0000

Pj4gVGhpcyBjb3VsZCBiZSBhIGxpdHRsZSBjbGVhcmVyOyBiZWNhdXNlIGl0IGNvdWxkIGJlIGlu
dGVycHJldGVkIGFzIA0KPj4gbWVhbmluZyB0aGF0IGFsbCBmaW5nZXJwcmludHMgaGF2ZSB0byBt
YXRjaC4gIEhvdyBhYm91dC4gIC4uLiBpbiB3aGljaCANCj4+IGNhc2UsIG1hdGNoaW5nIE1VU1Qg
ZmFpbCB1bmxlc3MgYSBtYXRjaCBpcyBmb3VuZCBmb3IgZXZlcnkgaGFzaCANCj4+IGZ1bmN0aW9u
IHRoYXQgaXMgdGVzdGVkLg0KPg0KPiBJIHNob3VsZCByZWFkIHRoZSB0aHJlYWQgYmVmb3JlIHJl
cGx5aW5nLiAgUGF1bCBjYXVnaHQgdGhpcyB0b28gDQo+IGFuZCBoaXMgdGV4dCBpcyBwcm9iYWJs
eSBiZXR0ZXIgdGhhbiBtaW5lLg0KDQpQbGVhc2UgYWxzbyBjaGVjayB0aGUgdGV4dCB0aGF0IGVu
ZGVkIHVwIGluIHRoZSBkcmFmdCA6KQ0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0K


From nobody Thu May 19 12:38:38 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D6012D65F for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 12:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwfZReiZxCdR for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 12:38:35 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19FE512D63C for <mmusic@ietf.org>; Thu, 19 May 2016 12:38:34 -0700 (PDT)
Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by comcast with SMTP id 3TlNbQ0Omp1Be3TmEb235O; Thu, 19 May 2016 19:38:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1463686714; bh=Q2IduhCuLD8YijA5nv2hwd4tId3d5LkVYixVPC/t/1k=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=S2wdTXcJYp3BncerkXrpKqyL6g76+0rP4l4Fgv2dUjObkKfqKRVefCMJV4QV2dK51 5pXAhfjZhhpcGjRclUWg2fTt/S7l6nX/gBdDeEu5GknTioJTZluLkxQ7I3hQ/wJr5Y P3GGJ2I7mQ8Xv/jyoNABQMk1dB8lf3JqU1ntkiHEWbO9ESWf0MRhHNWq0rcF8bggW8 kTuiknwaqbKWAS7zhOGshQ4ZOPCQdNCUXGLahR345IR4p7ofGq+EEvkSbfE8ENDmBc 4y8/f3jOgdHqF2jKnavGfrN2gbZHRb+hUTNSE8Hyp7d5xgh65eVIFJENGQhJStcOx9 i5MH41PltR8iQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-18v.sys.comcast.net with comcast id wKeZ1s00X3KdFy101KeavW; Thu, 19 May 2016 19:38:34 +0000
To: mmusic@ietf.org
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se> <573E0745.3010606@gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <a1f248c5-c707-8eb1-1ebc-256392ed7362@alum.mit.edu>
Date: Thu, 19 May 2016 15:38:27 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <573E0745.3010606@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1U_jdbotEzH9ElovVgIs-uWX2w8>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 19:38:36 -0000

On 5/19/16 2:34 PM, Thomas Stach wrote:

>> Section 4.2 says:
>>
>>     "Such "a=mid:" attributes MUST immediately precede the list of
>> candidates for that specific "m=" line."
>>
>> I don't think we need to say that. It is enough that the mid attribute
>> is associated with the same m= line as the candidates. I.e. normal SDP
>> procedures apply.
> You're right, it is not strictly needed. However, the current text was
> the outcome of a longer discussion with Paul Kyzivat. I would have to
> look up the details that lead to this format.
> Additonally, as the grammar for the info-package is written in a way
> that prescribes the order of the attributes, I'd prefer to keep it as
> is, unless there is a real need for more flexibility.
> Others?
>> Alternatively, we could actually remove the m= line, and replace it
>> with the mid attribute (in which case the attribute obviously need to
>> precede the list of candidates).

I just looked back to refresh my mind what that discussion was. It was 
about sdpfrag. At the time it was just application/sdpfrag. My concern 
was a generic sdpfrag isn't useful, because arbitrary subsets of sdp 
lines are ambiguous. To make it unambiguous you need to include certain 
key features that make it so. I was arguing that what was needed was a 
application/trickle-ice-sdpfrag that specified the particular subset 
that is unambiguous.

That has now been done. And it always has the ice attributes preceded by 
as m=line and single a=mid. So the a=mid always does immediately precede 
the candidates.

Since the m=line is there, Christer's language should also work. I don't 
have a strong opinion either way. But I haven't read the draft recently, 
so I might be missing something.

	Thanks,
	Paul


From nobody Thu May 19 23:45:09 2016
Return-Path: <thomass.stach@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ADA512D6B8 for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 23:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 kaHO8UCKRHxN for <mmusic@ietfa.amsl.com>; Thu, 19 May 2016 23:45:06 -0700 (PDT)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8910012D6A6 for <mmusic@ietf.org>; Thu, 19 May 2016 23:45:05 -0700 (PDT)
Received: by mail-wm0-x233.google.com with SMTP id v200so2855339wmv.1 for <mmusic@ietf.org>; Thu, 19 May 2016 23:45:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=VKBdPir98gJNJAtnNAh9ZqtnSU3vcNCkFGH+JUX8pHE=; b=VaLel89RkInYf2+qcQthLTOSypx5x1FMUKRhTj7BbUaO1XeN96OfxCEG2YKfdPe3Iv wmfh0Mf3ScYeMg1c01TMCJpwOInZi3HuqPuFfEffO7Vo4VDHd7TEnu2ZjwMNZJ0Dw616 diUwBDQNyuBXTznrAhECMYskTSjVNa7c5Hbm14QbD6Jt7tylvCEmyo+5QOuyHy+b8Fit 4uDXDU7Pp0sD1U1BOA6T4Nmpaf1QOYKhopzXq4C3RpzrTgO1Drb/OT5pbzE8ObJt8DBp 7/vE1xI2IeShDh46ZsAH4Ufd8xzAOjKFpPPyJvTpg31XPSfajkovJhfeQssmHUq7x3eA OQnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=VKBdPir98gJNJAtnNAh9ZqtnSU3vcNCkFGH+JUX8pHE=; b=K8GBeWF/oHDV2/qckfhCOI6SsQaDhksCkTguMJsn2/Sx0tWJsT1HwXGI06+ZPfizqQ dB5qEqp+elzGVC2HO0SJlS/+lGUVyS+veZouAo+Ta81dvSIQRx/JoUBTHbbHdeeKB3JT wtjBbDybdaW4ZkTc3dEbrGqtxj+7Ol6pieLyReBEIsD8L8rmUEC0AFeXiDHTvC9O+pkC U4Bo7J6XdxUau/L9YX3tGfs1LYGtr5whnZqRrEX/ozWkM6pOcqJpkP7N5+n8WK6Gs02u IosNvLDW2pEYIGD/9VqytvlTuhuX4MysPuJAI7Do/pgnvVsR5pS9xeQCleP7y1puEmqF 7COQ==
X-Gm-Message-State: AOPr4FWzjDUDV7IWfbDa9/u1ytlhj8qHhWMJC+4fndJbBUHDevpjuI85bg0GimeOydbm0g==
X-Received: by 10.194.158.226 with SMTP id wx2mr1394121wjb.91.1463726703908; Thu, 19 May 2016 23:45:03 -0700 (PDT)
Received: from [192.168.2.109] (d91-130-21-47.cust.tele2.at. [91.130.21.47]) by smtp.googlemail.com with ESMTPSA id l74sm2981059wmb.15.2016.05.19.23.45.02 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 May 2016 23:45:03 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, MMUSIC <mmusic@ietf.org>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se> <573E0745.3010606@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FD9934@ESESSMB209.ericsson.se>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <573EB26E.7010509@gmail.com>
Date: Fri, 20 May 2016 08:45:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FD9934@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1aOli35vwfZGrR3J8M6hJbIxFcc>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 06:45:08 -0000

Christer,

On 2016-05-19 21:32, Christer Holmberg wrote:
> Hi,
>
> See inline.
>
> Q1:
>
>>> The text in 3.3 says:
>>>
>>> 	"Such INFO requests do not impact the state of Offer/Answer, nor do they have an impact on the version number in the "o=" line."
>>>
>>> I think we'll need more text than this, in order to avoid confusion. For example, if INFOs don't impact the
>>> state of Offer/Answer, does it mean that the candidates will NOT be included in subsequent offer/answer transactions?
>> No, in a subsequent offer/answer transaction you would include the actual set of candidates, i.e.  in case you use 100rel
>> and do a second O/A before the 200OK to the INVITE, you would include in the offer the candidates present in the initial
>> offer and all candidates there were trickled in the meantime.
> Well, then the INFO *does* impact the Offer/Answer state, doesn't it - assuming the set of candidates is part of the O/A state?
Well, this definition is probably the source of this discussion. The 
draft does not assume that the candidates are part of the O/A state.
Figure 2 tries to clarify that by using the  logical entities "O/A 
module" and "ICE agent".
The candidates just affect the state of the the latter.
This is also the reason for the comparison of trickled candidates with 
peer reflexive candidates.
Both are learned by the ICE agent without the need for an additional O/A 
exchange.

>
> Also, assume candidates A, B and C are included in the offer/answer transaction, and then the INFO contains (for whatever reason) candidates A and B.
This is an error
>   What is the state of C? Can INFO be used to *remove* previously negotiated candidates`?
No, this would need an ICE restart.
>
>
>>> However, I assume that they WILL be impacted by an ICE re-start.
>> In case of a restart everything starts from scratch.
> Needs to be explicitly indicated.
Agreed
>
>
> Q2:
>
>>> Section 4.2 says:
>>>
>>> 	"INFO requests containing "a=ice-pwd:" and "a=ice-ufrag:" attributes that do not match those of the current ICE processing
>>>      	session MUST be discarded."
>>>
>> This obviously applies if the INFO contains *OLD* pwd/ufrag values. But, I also assume that it is not allowed to provide *NEW* values in an INFO. If so, it needs to be clarified.
>> Correct, the current text does not allow this. I can clarify.
> Ok.
>
>
>
> Q3:
>
>>> Section 4.2 says:
>>>
>>> 	"Such "a=mid:" attributes MUST immediately precede the list of candidates for that specific "m=" line."
>>>
>>> I don't think we need to say that. It is enough that the mid attribute is associated with the same m= line as the candidates. I.e. normal SDP procedures apply.
>> You're right, it is not strictly needed. However, the current text was the outcome of a longer discussion with Paul Kyzivat. I would have to look up the details that lead to this format.
>> Additionally, as the grammar for the info-package is written in a way that prescribes the order of the attributes, I'd prefer to keep it as is, unless there is a real need for more flexibility.
> So, what happens if the mid attribute is NOT where it is supposed to be?
This is an error case, which traditionally aren't covered in too much 
detail in RFCs.
You could think about a 488 or 606 or you could be liberal in what you 
receive.
> Shall the receiver reject the trickled candidates(s)?
>
> That brings up another question: how does a receiver reject received candidates?
Why would you need that? That was never a requirement before.

> Remember that the receiver will always send 200 OK to the INFO request.
No, you can also send an error response.


Regards
Thomas

>
>
>>> Alternatively, we could actually remove the m= line, and replace it with the mid attribute (in which case the attribute obviously need to precede the list of candidates).
>>> Q4:
>>>
>>> Section 4.2 says:
>>>
>>> 	"In every INFO request agents MUST include all local candidates they have previously signaled."
>>>
>>> First, I don't think you want to include candidates that are no longer used, do you?
>> What do you mean by no longer used?
> Candidates that were used before a re-start, or have been removed/disabled using some other means.
>
>
>>> Second, it is also unclear whether this includes candidates that have
>>> been signalled using Offer/Answer (I guess Q5 answers that).
>>>
>>> Third, do we really want to include all candidates? If we want to regard INFOs as peer reflexive candidates, why not only include the new ones?
>> Always including the complete set of candidates (i.e. those from the initial offeror answer plus the ones that were trickled afterwards) is motivated by the infamous support for UDP transport in SIP.
> Infamous? Also keep in mind that STUN is transported over UDP, so peer reflexive candidates are in no better position.
>
>> In order to have things simple we decided already in the early days of this draft to always have the complete set in the INFO.
>> Then, you don't need to care about lost INFOs and can just drop any late arrivals.
> Well, late arrivals should be dropped anyway.
>
>
> Q5:
>
>>> Section 4.2 says:
>>>
>>>     	"When receiving INFO requests carrying any candidates, agents will
>>>      	therefore first identify and discard the SDP lines containing
>>>      	candidates they have already received in previous INFO requests or in
>>>      	the Offer/Answer exchange preceding them."
>>>
>>> Where does the text says that INFOs shall carry candidates that have been signalled in Offer/Answer? The text in Q4?
>> Yes
> Ok.
>
> Regards,
>
> Christer
>
>> -----Original Message-----
>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Thomas
>> Stach
>> Sent: 17 May 2016 17:00
>> To: MMUSIC<mmusic@ietf.org>
>> Subject: [MMUSIC] Fwd: New Version Notification for
>> draft-ietf-mmusic-trickle-ice-sip-04.txt
>>
>> All,
>>
>> the changes from draft-ietf-mmusic-trickle-ice-sip-03 include
>>
>> - replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and
>> draft-ietf-mmusic-ice-sip-sdp
>> - corrected Figure 10, credits to Ayush Jain for finding the bug
>> - referencing a=rtcp and a=rtcp-mux handling from
>> draft-ietf-mmusic-ice-sip-sdp
>> - referencing a=rtcp-mux-exclusive handling from
>> draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support
>> a=rtcp-mux-exclusive
>> - clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the
>> application/trickle-ice-sdpfrag body
>>
>> Currently there are no open issues in this draft. However, it could probably benefit from a thorough review.
>> So, comments welcome.
>>
>> With respect to progressing this work, I think that it should go forward alongside with draft-ietf-ice-trickle since any updates of that document might influence the content of this draft.
>>
>> Regards
>> Thomas
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject: 	New Version Notification for
>> draft-ietf-mmusic-trickle-ice-sip-04.txt
>> Date: 	Tue, 17 May 2016 06:50:19 -0700
>> From: 	internet-drafts@ietf.org
>> To: 	Thomas Stach<thomass.stach@gmail.com>, Emil Ivov
>> <emcho@jitsi.org>, Enrico Marocco<enrico.marocco@telecomitalia.it>,
>> Christer Holmberg<christer.holmberg@ericsson.com>
>>
>>
>>
>> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
>> has been successfully submitted by Thomas Stach and posted to the IETF
>> repository.
>>
>> Name:		draft-ietf-mmusic-trickle-ice-sip
>> Revision:	04
>> Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
>> Document date:	2016-05-17
>> Group:		mmusic
>> Pages:		36
>> URL:https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice
>> -sip-04.txt
>> Status:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-
>> sip/
>> Htmlized:https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip
>> -04
>> Diff:https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-s
>> ip-04
>>
>> Abstract:
>>       The Interactive Connectivity Establishment (ICE) protocol describes a
>>       Network Address Translator (NAT) traversal mechanism for UDP-based
>>       multimedia sessions established with the Offer/Answer model.  The ICE
>>       extension for Incremental Provisioning of Candidates (Trickle ICE)
>>       defines a mechanism that allows ICE agents to shorten session
>>       establishment delays by making the candidate gathering and
>>       connectivity checking phases of ICE non-blocking and by executing
>>       them in parallel.
>>
>>       This document defines usage semantics for Trickle ICE with the
>>       Session Initiation Protocol (SIP).
>>
>>                                                                                      
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>


From nobody Fri May 20 02:50:34 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5639312D7B5 for <mmusic@ietfa.amsl.com>; Fri, 20 May 2016 02:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InNWXmMSW9XX for <mmusic@ietfa.amsl.com>; Fri, 20 May 2016 02:50:30 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EF4D12D7B6 for <mmusic@ietf.org>; Fri, 20 May 2016 02:50:12 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-9f-573eddd3a5f6
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id B8.30.27088.3DDDE375; Fri, 20 May 2016 11:50:11 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0248.002; Fri, 20 May 2016 11:49:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, MMUSIC <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
Thread-Index: AQHRsEMOIliX14uf2EKWpAtozqzJo5+9BuOAgACWdbCAAtrVgIAALipggACd4ACAAGZjgA==
Date: Fri, 20 May 2016 09:49:10 +0000
Message-ID: <D364B55A.8B73%christer.holmberg@ericsson.com>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se> <573E0745.3010606@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FD9934@ESESSMB209.ericsson.se> <573EB26E.7010509@gmail.com>
In-Reply-To: <573EB26E.7010509@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8CD497B3CB2CF54CBF17E4E47342AEAB@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM2K7lu7lu3bhBk2H5C2mLn/MYvHpxFYm ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugSvj7feVrAWTAyt+vlzK2sB4yLGLkZNDQsBE 4nPzAkYIW0ziwr31bF2MXBxCAkcYJV4/uc0I4SxhlNjTdRDI4eBgE7CQ6P6nDdIgIuAi8ejF DHYQW1ggSeJHx3pGiHiyxK2jz1gg7DCJt/sesYLYLAKqEp/mHGcCsXkFrCSOnHoKZgsJLGOS mLiuBMTmFNCU+P1sAhuIzQh00PdTa8BqmAXEJW49mc8EcaiAxJI955khbFGJl4//gc0XFdCT 2PfiPNQzShI/NlxigejVk7gxdQobhG0tcXjyBqiZ2hLLFr5mhrhHUOLkzCcsExjFZyFZNwtJ +ywk7bOQtM9C0r6AkXUVo2hxanFSbrqRkV5qUWZycXF+nl5easkmRmC8Hdzy22AH48vnjocY BTgYlXh4F+TbhQuxJpYVV+YeYpTgYFYS4S2/AxTiTUmsrEotyo8vKs1JLT7EKM3BoiTO6/9S MVxIID2xJDU7NbUgtQgmy8TBKdXAaPVvd6uem+K+RXMkWX6+LGy7vaT88/Xe8Ltma868f2/Z /KS27KWKTq6Hnrd35532l0fupt+/UH3m7A/W3eV/fjE5bPM2Pebx3SlZZruwFkPRkYcPFs6J WpHaePawxvnAdl3mRKfV6Qs/blJapqf+z0Pkp4ePnKJrwcb/SYy99/bVRJY6ftX9rMRSnJFo qMVcVJwIAFxklLizAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/vMj4ngNpJvcMPU5R2fVbnZNI87s>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 09:50:34 -0000

Hi,

>> Q1:
>>
>>>> The text in 3.3 says:
>>>>
>>>> 	"Such INFO requests do not impact the state of Offer/Answer, nor do
>>>>they have an impact on the version number in the "o=3D" line."
>>>>
>>>> I think we'll need more text than this, in order to avoid confusion.
>>>>For example, if INFOs don't impact the
>>>> state of Offer/Answer, does it mean that the candidates will NOT be
>>>>included in subsequent offer/answer transactions?
>>> No, in a subsequent offer/answer transaction you would include the
>>>actual set of candidates, i.e.  in case you use 100rel
>>> and do a second O/A before the 200OK to the INVITE, you would include
>>>in the offer the candidates present in the initial
>>> offer and all candidates there were trickled in the meantime.
>> Well, then the INFO *does* impact the Offer/Answer state, doesn't it -
>>assuming the set of candidates is part of the O/A state?
>Well, this definition is probably the source of this discussion. The
>draft does not assume that the candidates are part of the O/A state.
>Figure 2 tries to clarify that by using the  logical entities "O/A
>module" and "ICE agent".
>The candidates just affect the state of the the latter.
>This is also the reason for the comparison of trickled candidates with
>peer reflexive candidates.
>Both are learned by the ICE agent without the need for an additional O/A
>exchange.

O/A state is more than the actual O/A transactions. In my opinion the
current SDP state is also part of the O/A state. Anyway, if that is not
the case, we need further clarification on what we really mean by =B3O/A
state=B2. If you only refer to the O/A transactions, then it should be
clearly stated.


>> Also, assume candidates A, B and C are included in the offer/answer
>>transaction, and then the INFO contains (for whatever reason) candidates
>>A and B.
>This is an error

So, what shall the receiver do if it happens? Discard the candidate(s)?


>>   What is the state of C? Can INFO be used to *remove* previously
>>negotiated candidates`?
>No, this would need an ICE restart.

Needs to be clear. Perhaps there should be a =B3ICE Restrictions=B2 section=
,
or something similar.


>>>> However, I assume that they WILL be impacted by an ICE re-start.
>>> In case of a restart everything starts from scratch.
>> Needs to be explicitly indicated.
>Agreed

Good :)


>> Q2:
>>
>>>> Section 4.2 says:
>>>>
>>>> 	"INFO requests containing "a=3Dice-pwd:" and "a=3Dice-ufrag:" attribu=
tes
>>>>that do not match those of the current ICE processing
>>>>      	session MUST be discarded."
>>>>
>>> This obviously applies if the INFO contains *OLD* pwd/ufrag values.
>>>But, I also assume that it is not allowed to provide *NEW* values in an
>>>INFO. If so, it needs to be clarified.
>>> Correct, the current text does not allow this. I can clarify.
>> Ok.
>>
>>
>>
>> Q3:
>>
>>>> Section 4.2 says:
>>>>
>>>> 	"Such "a=3Dmid:" attributes MUST immediately precede the list of
>>>>candidates for that specific "m=3D" line."
>>>>
>>>> I don't think we need to say that. It is enough that the mid
>>>>attribute is associated with the same m=3D line as the candidates. I.e.
>>>>normal SDP procedures apply.
>>> You're right, it is not strictly needed. However, the current text was
>>>the outcome of a longer discussion with Paul Kyzivat. I would have to
>>>look up the details that lead to this format.
>>> Additionally, as the grammar for the info-package is written in a way
>>>that prescribes the order of the attributes, I'd prefer to keep it as
>>>is, unless there is a real need for more flexibility.
>> So, what happens if the mid attribute is NOT where it is supposed to be?
>This is an error case, which traditionally aren't covered in too much
>detail in RFCs.

Well, I think we need to have some text on error cases. See more below.


>You could think about a 488 or 606 or you could be liberal in what you
>receive.
>> Shall the receiver reject the trickled candidates(s)?
>>
>> That brings up another question: how does a receiver reject received
>>candidates?
>Why would you need that? That was never a requirement before.
>
>> Remember that the receiver will always send 200 OK to the INFO request.
>No, you can also send an error response.


The INFO response is often sent by the SIP stack, before the Info Package
content has been handed to the application, and as long as the SIP stack
supports the Info Package as such, a 200 OK will be sent. If there is some
errors on the application level it needs to be dealt with some other way.
Please see section 4.2.2 of RFC 6086.

Regards,

Christer





>>
>>
>>>> Alternatively, we could actually remove the m=3D line, and replace it
>>>>with the mid attribute (in which case the attribute obviously need to
>>>>precede the list of candidates).
>>>> Q4:
>>>>
>>>> Section 4.2 says:
>>>>
>>>> 	"In every INFO request agents MUST include all local candidates they
>>>>have previously signaled."
>>>>
>>>> First, I don't think you want to include candidates that are no
>>>>longer used, do you?
>>> What do you mean by no longer used?
>> Candidates that were used before a re-start, or have been
>>removed/disabled using some other means.
>>
>>
>>>> Second, it is also unclear whether this includes candidates that have
>>>> been signalled using Offer/Answer (I guess Q5 answers that).
>>>>
>>>> Third, do we really want to include all candidates? If we want to
>>>>regard INFOs as peer reflexive candidates, why not only include the
>>>>new ones?
>>> Always including the complete set of candidates (i.e. those from the
>>>initial offeror answer plus the ones that were trickled afterwards) is
>>>motivated by the infamous support for UDP transport in SIP.
>> Infamous? Also keep in mind that STUN is transported over UDP, so peer
>>reflexive candidates are in no better position.
>>
>>> In order to have things simple we decided already in the early days of
>>>this draft to always have the complete set in the INFO.
>>> Then, you don't need to care about lost INFOs and can just drop any
>>>late arrivals.
>> Well, late arrivals should be dropped anyway.
>>
>>
>> Q5:
>>
>>>> Section 4.2 says:
>>>>
>>>>     	"When receiving INFO requests carrying any candidates, agents
>>>>will
>>>>      	therefore first identify and discard the SDP lines containing
>>>>      	candidates they have already received in previous INFO requests
>>>>or in
>>>>      	the Offer/Answer exchange preceding them."
>>>>
>>>> Where does the text says that INFOs shall carry candidates that have
>>>>been signalled in Offer/Answer? The text in Q4?
>>> Yes
>> Ok.
>>
>> Regards,
>>
>> Christer
>>
>>> -----Original Message-----
>>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Thomas
>>> Stach
>>> Sent: 17 May 2016 17:00
>>> To: MMUSIC<mmusic@ietf.org>
>>> Subject: [MMUSIC] Fwd: New Version Notification for
>>> draft-ietf-mmusic-trickle-ice-sip-04.txt
>>>
>>> All,
>>>
>>> the changes from draft-ietf-mmusic-trickle-ice-sip-03 include
>>>
>>> - replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and
>>> draft-ietf-mmusic-ice-sip-sdp
>>> - corrected Figure 10, credits to Ayush Jain for finding the bug
>>> - referencing a=3Drtcp and a=3Drtcp-mux handling from
>>> draft-ietf-mmusic-ice-sip-sdp
>>> - referencing a=3Drtcp-mux-exclusive handling from
>>> draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support
>>> a=3Drtcp-mux-exclusive
>>> - clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the
>>> application/trickle-ice-sdpfrag body
>>>
>>> Currently there are no open issues in this draft. However, it could
>>>probably benefit from a thorough review.
>>> So, comments welcome.
>>>
>>> With respect to progressing this work, I think that it should go
>>>forward alongside with draft-ietf-ice-trickle since any updates of that
>>>document might influence the content of this draft.
>>>
>>> Regards
>>> Thomas
>>>
>>>
>>>
>>> -------- Forwarded Message --------
>>> Subject: 	New Version Notification for
>>> draft-ietf-mmusic-trickle-ice-sip-04.txt
>>> Date: 	Tue, 17 May 2016 06:50:19 -0700
>>> From: 	internet-drafts@ietf.org
>>> To: 	Thomas Stach<thomass.stach@gmail.com>, Emil Ivov
>>> <emcho@jitsi.org>, Enrico Marocco<enrico.marocco@telecomitalia.it>,
>>> Christer Holmberg<christer.holmberg@ericsson.com>
>>>
>>>
>>>
>>> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
>>> has been successfully submitted by Thomas Stach and posted to the IETF
>>> repository.
>>>
>>> Name:		draft-ietf-mmusic-trickle-ice-sip
>>> Revision:	04
>>> Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
>>> Document date:	2016-05-17
>>> Group:		mmusic
>>> Pages:		36
>>> URL:https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice
>>> -sip-04.txt
>>> Status:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-
>>> sip/
>>> Htmlized:https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip
>>> -04
>>> Diff:https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-trickle-ice-=
s
>>> ip-04
>>>
>>> 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).
>>>
>>>               =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.
>>>
>>> The IETF Secretariat
>>>
>>>
>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>


From nobody Fri May 20 06:34:22 2016
Return-Path: <thomass.stach@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C3712D973 for <mmusic@ietfa.amsl.com>; Fri, 20 May 2016 06:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3osteEYsKa7q for <mmusic@ietfa.amsl.com>; Fri, 20 May 2016 06:34:18 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B272312D96B for <mmusic@ietf.org>; Fri, 20 May 2016 06:34:17 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id a17so173559674wme.0 for <mmusic@ietf.org>; Fri, 20 May 2016 06:34:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=SQSpXcUPNhMnmqeIPjla41+rSTykb5GuwIJZjMh3TGw=; b=j7dLy/lRoIN6DPjVhg4efbP3WsMDKaymX2OiChVqTvYbC/Zt4q2/AcD+Z6JOy7F0r0 EtFjnCWw3Due+fNvpZC3A7ol+p2acW6uO+HtyGGi1FQMH0jXqvm6ucABkvBA8rvkoj2B 15eJs5ATCRz8FPTS3yHPCiZSeM+8udDH/ZQnOSCj2Fw4kKgEwbVbuM8oU3oGFSM5TyIb 3fCv29Rvui9Ps8VZtAclq7NDTac9ICDJocSkQELedlDHjFmcfWrJdnbW/tE1rQHXN4yx e28wAoasWJwLPSfBr/jHKZ6DCnUF3lSGjR4GBK1IKgiLtBIlgNApyNyyH/foqZtqT0tn m9ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=SQSpXcUPNhMnmqeIPjla41+rSTykb5GuwIJZjMh3TGw=; b=Z2xC/Kzo66AQLK4Lz3jaU7UyszRh3/M97b9ZwII4Z5ZkpwNn63HdZwB/cJJCKvQto6 x/cNhT03X6A5cZ4J/PMWV2KYJepwKIr/yFqNuzz0JVJ9MyNyMgmwMPdjfBhAaOFIcoFl 8F+TnPPC3L3Q+JRZ7YThv3KCHKdANaZpXWVlcUL4aWgKd7oEzHI5/f3U8hg3HHAo89J/ 4F3CbXJYod3QqH6BWwVGgb3bhB4yg39/P7rtXyXmQSY6SzoPGcs8gD9W9LrBVXSscD8f QmYQN9rj4zbnPgGYw9rD3gRkIkIRrB64Hz3j2Crn92HVm1vfabSco+cdtoWFWSM68soi iXRw==
X-Gm-Message-State: AOPr4FWe3etzs6OUqcDmJnTjCpFkngQF6625EEXFPEp6lkltbHGo7ebPL97/6WKCnpJJHA==
X-Received: by 10.28.216.208 with SMTP id p199mr3605823wmg.57.1463751255996; Fri, 20 May 2016 06:34:15 -0700 (PDT)
Received: from [192.168.2.109] (d91-130-21-47.cust.tele2.at. [91.130.21.47]) by smtp.googlemail.com with ESMTPSA id u6sm4605649wmd.21.2016.05.20.06.34.10 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 May 2016 06:34:15 -0700 (PDT)
To: Christer Holmberg <christer.holmberg@ericsson.com>, MMUSIC <mmusic@ietf.org>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se> <573E0745.3010606@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FD9934@ESESSMB209.ericsson.se> <573EB26E.7010509@gmail.com> <D364B55A.8B73%christer.holmberg@ericsson.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <573F124D.5010005@gmail.com>
Date: Fri, 20 May 2016 15:34:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <D364B55A.8B73%christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary="------------020905080504070607090305"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/5DDFtaGxOyiRNCMRIURf-G6OSYM>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 13:34:21 -0000

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



On 2016-05-20 11:49, Christer Holmberg wrote:
> Hi,
>
>>> Q1:
>>>
>>>>> The text in 3.3 says:
>>>>>
>>>>> 	"Such INFO requests do not impact the state of Offer/Answer, nor do
>>>>> they have an impact on the version number in the "o=" line."
>>>>>
>>>>> I think we'll need more text than this, in order to avoid confusion.
>>>>> For example, if INFOs don't impact the
>>>>> state of Offer/Answer, does it mean that the candidates will NOT be
>>>>> included in subsequent offer/answer transactions?
>>>> No, in a subsequent offer/answer transaction you would include the
>>>> actual set of candidates, i.e.  in case you use 100rel
>>>> and do a second O/A before the 200OK to the INVITE, you would include
>>>> in the offer the candidates present in the initial
>>>> offer and all candidates there were trickled in the meantime.
>>> Well, then the INFO *does* impact the Offer/Answer state, doesn't it -
>>> assuming the set of candidates is part of the O/A state?
>> Well, this definition is probably the source of this discussion. The
>> draft does not assume that the candidates are part of the O/A state.
>> Figure 2 tries to clarify that by using the  logical entities "O/A
>> module" and "ICE agent".
>> The candidates just affect the state of the the latter.
>> This is also the reason for the comparison of trickled candidates with
>> peer reflexive candidates.
>> Both are learned by the ICE agent without the need for an additional O/A
>> exchange.
> O/A state is more than the actual O/A transactions. In my opinion the
> current SDP state is also part of the O/A state. Anyway, if that is not
> the case, we need further clarification on what we really mean by ³O/A
> state². If you only refer to the O/A transactions, then it should be
> clearly stated.
A proposal for improved text:

old:

Such INFO requests do not
    impact the state of Offer/Answer, nor do they have an impact on the
    version number in the "o=" line.  In that regard they are actually
    comparable to Peer Reflexive candidates that ICE agents can discover
    during ICE processing.

new:

Such INFO requests do not impact the state of Offer/Answer other than providing additional candidates.
Consequently, they do not have an impact on the version number in the "o=" line.
In that regard trickled candidates are actually comparable to Peer Reflexive candidates that
ICE agents can discover during ICE processing without without the need for an additional O/A
exchange.



>
>
>>> Also, assume candidates A, B and C are included in the offer/answer
>>> transaction, and then the INFO contains (for whatever reason) candidates
>>> A and B.
>> This is an error
> So, what shall the receiver do if it happens? Discard the candidate(s)?
Actually this should already be covered at the end of 4.2

When receiving INFO requests carrying any candidates, agents will
    therefore first identify and discard the SDP lines containing
    candidates they have already received in previous INFO requests or in
    the Offer/Answer exchange preceding them.
...  After identifying and discarding known
    candidates, agents will then process the remaining, actually new
    candidates according to the rules described in
    [I-D.ietf-mmusic-trickle-ice 
<https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-04#ref-I-D.ietf-mmusic-trickle-ice>].

In said error case there aren't any remaining candidates, thus nothing 
to do. I can add a clarification at the end of 4.2
>
>
>>>    What is the state of C? Can INFO be used to *remove* previously
>>> negotiated candidates`?
>> No, this would need an ICE restart.
> Needs to be clear. Perhaps there should be a ³ICE Restrictions² section,
> or something similar.
Why? There never was a candidate removal feature in ICE (nor 
Trickle-ICE) and I don't think that this document needs to specify 
anything along that lines.
>
>
>>>>> However, I assume that they WILL be impacted by an ICE re-start.
>>>> In case of a restart everything starts from scratch.
>>> Needs to be explicitly indicated.
>> Agreed
> Good :)
>
>
>>> Q2:
>>>
>>>>> Section 4.2 says:
>>>>>
>>>>> 	"INFO requests containing "a=ice-pwd:" and "a=ice-ufrag:" attributes
>>>>> that do not match those of the current ICE processing
>>>>>       	session MUST be discarded."
>>>>>
>>>> This obviously applies if the INFO contains *OLD* pwd/ufrag values.
>>>> But, I also assume that it is not allowed to provide *NEW* values in an
>>>> INFO. If so, it needs to be clarified.
>>>> Correct, the current text does not allow this. I can clarify.
>>> Ok.
>>>
>>>
>>>
>>> Q3:
>>>
>>>>> Section 4.2 says:
>>>>>
>>>>> 	"Such "a=mid:" attributes MUST immediately precede the list of
>>>>> candidates for that specific "m=" line."
>>>>>
>>>>> I don't think we need to say that. It is enough that the mid
>>>>> attribute is associated with the same m= line as the candidates. I.e.
>>>>> normal SDP procedures apply.
>>>> You're right, it is not strictly needed. However, the current text was
>>>> the outcome of a longer discussion with Paul Kyzivat. I would have to
>>>> look up the details that lead to this format.
>>>> Additionally, as the grammar for the info-package is written in a way
>>>> that prescribes the order of the attributes, I'd prefer to keep it as
>>>> is, unless there is a real need for more flexibility.
>>> So, what happens if the mid attribute is NOT where it is supposed to be?
>> This is an error case, which traditionally aren't covered in too much
>> detail in RFCs.
> Well, I think we need to have some text on error cases. See more below.
>
>
>> You could think about a 488 or 606 or you could be liberal in what you
>> receive.
>>> Shall the receiver reject the trickled candidates(s)?
>>>
>>> That brings up another question: how does a receiver reject received
>>> candidates?
>> Why would you need that? That was never a requirement before.
>>
>>> Remember that the receiver will always send 200 OK to the INFO request.
>> No, you can also send an error response.
>
> The INFO response is often sent by the SIP stack, before the Info Package
> content has been handed to the application, and as long as the SIP stack
> supports the Info Package as such, a 200 OK will be sent. If there is some
> errors on the application level it needs to be dealt with some other way.
> Please see section 4.2.2 of RFC 6086.
My interpretation of that section is that you MAY send an error since 
the INFO request from above  is not syntactically correct. However, 
200OK and dealing with content on application level would also be fine. 
I don't think that this document needs to say anything beyond RFC6086. 
Regards Thomas
>
> Regards,
>
> Christer
>
>
>
>
>
>>>
>>>>> Alternatively, we could actually remove the m= line, and replace it
>>>>> with the mid attribute (in which case the attribute obviously need to
>>>>> precede the list of candidates).
>>>>> Q4:
>>>>>
>>>>> Section 4.2 says:
>>>>>
>>>>> 	"In every INFO request agents MUST include all local candidates they
>>>>> have previously signaled."
>>>>>
>>>>> First, I don't think you want to include candidates that are no
>>>>> longer used, do you?
>>>> What do you mean by no longer used?
>>> Candidates that were used before a re-start, or have been
>>> removed/disabled using some other means.
>>>
>>>
>>>>> Second, it is also unclear whether this includes candidates that have
>>>>> been signalled using Offer/Answer (I guess Q5 answers that).
>>>>>
>>>>> Third, do we really want to include all candidates? If we want to
>>>>> regard INFOs as peer reflexive candidates, why not only include the
>>>>> new ones?
>>>> Always including the complete set of candidates (i.e. those from the
>>>> initial offeror answer plus the ones that were trickled afterwards) is
>>>> motivated by the infamous support for UDP transport in SIP.
>>> Infamous? Also keep in mind that STUN is transported over UDP, so peer
>>> reflexive candidates are in no better position.
>>>
>>>> In order to have things simple we decided already in the early days of
>>>> this draft to always have the complete set in the INFO.
>>>> Then, you don't need to care about lost INFOs and can just drop any
>>>> late arrivals.
>>> Well, late arrivals should be dropped anyway.
>>>
>>>
>>> Q5:
>>>
>>>>> Section 4.2 says:
>>>>>
>>>>>      	"When receiving INFO requests carrying any candidates, agents
>>>>> will
>>>>>       	therefore first identify and discard the SDP lines containing
>>>>>       	candidates they have already received in previous INFO requests
>>>>> or in
>>>>>       	the Offer/Answer exchange preceding them."
>>>>>
>>>>> Where does the text says that INFOs shall carry candidates that have
>>>>> been signalled in Offer/Answer? The text in Q4?
>>>> Yes
>>> Ok.
>>>
>>> Regards,
>>>
>>> Christer
>>>
>>>> -----Original Message-----
>>>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Thomas
>>>> Stach
>>>> Sent: 17 May 2016 17:00
>>>> To: MMUSIC<mmusic@ietf.org>
>>>> Subject: [MMUSIC] Fwd: New Version Notification for
>>>> draft-ietf-mmusic-trickle-ice-sip-04.txt
>>>>
>>>> All,
>>>>
>>>> the changes from draft-ietf-mmusic-trickle-ice-sip-03 include
>>>>
>>>> - replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and
>>>> draft-ietf-mmusic-ice-sip-sdp
>>>> - corrected Figure 10, credits to Ayush Jain for finding the bug
>>>> - referencing a=rtcp and a=rtcp-mux handling from
>>>> draft-ietf-mmusic-ice-sip-sdp
>>>> - referencing a=rtcp-mux-exclusive handling from
>>>> draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support
>>>> a=rtcp-mux-exclusive
>>>> - clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the
>>>> application/trickle-ice-sdpfrag body
>>>>
>>>> Currently there are no open issues in this draft. However, it could
>>>> probably benefit from a thorough review.
>>>> So, comments welcome.
>>>>
>>>> With respect to progressing this work, I think that it should go
>>>> forward alongside with draft-ietf-ice-trickle since any updates of that
>>>> document might influence the content of this draft.
>>>>
>>>> Regards
>>>> Thomas
>>>>
>>>>
>>>>
>>>> -------- Forwarded Message --------
>>>> Subject: 	New Version Notification for
>>>> draft-ietf-mmusic-trickle-ice-sip-04.txt
>>>> Date: 	Tue, 17 May 2016 06:50:19 -0700
>>>> From: 	internet-drafts@ietf.org
>>>> To: 	Thomas Stach<thomass.stach@gmail.com>, Emil Ivov
>>>> <emcho@jitsi.org>, Enrico Marocco<enrico.marocco@telecomitalia.it>,
>>>> Christer Holmberg<christer.holmberg@ericsson.com>
>>>>
>>>>
>>>>
>>>> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
>>>> has been successfully submitted by Thomas Stach and posted to the IETF
>>>> repository.
>>>>
>>>> Name:		draft-ietf-mmusic-trickle-ice-sip
>>>> Revision:	04
>>>> Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
>>>> Document date:	2016-05-17
>>>> Group:		mmusic
>>>> Pages:		36
>>>> URL:https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice
>>>> -sip-04.txt
>>>> Status:https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-
>>>> sip/
>>>> Htmlized:https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip
>>>> -04
>>>> Diff:https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-s
>>>> ip-04
>>>>
>>>> Abstract:
>>>>        The Interactive Connectivity Establishment (ICE) protocol
>>>> describes a
>>>>        Network Address Translator (NAT) traversal mechanism for
>>>> UDP-based
>>>>        multimedia sessions established with the Offer/Answer model.
>>>> The ICE
>>>>        extension for Incremental Provisioning of Candidates (Trickle
>>>> ICE)
>>>>        defines a mechanism that allows ICE agents to shorten session
>>>>        establishment delays by making the candidate gathering and
>>>>        connectivity checking phases of ICE non-blocking and by executing
>>>>        them in parallel.
>>>>
>>>>        This document defines usage semantics for Trickle ICE with the
>>>>        Session Initiation Protocol (SIP).
>>>>
>>>>                 
>>>>               
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of
>>>> submission until the htmlized version and diff are available at
>>>> tools.ietf.org.
>>>>
>>>> The IETF Secretariat
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>
>

--------------020905080504070607090305
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div class="moz-cite-prefix">On 2016-05-20 11:49, Christer Holmberg
      wrote:<br>
    </div>
    <blockquote
      cite="mid:D364B55A.8B73%25christer.holmberg@ericsson.com"
      type="cite">
      <pre wrap="">Hi,

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Q1:

</pre>
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">The text in 3.3 says:

	"Such INFO requests do not impact the state of Offer/Answer, nor do
they have an impact on the version number in the "o=" line."

I think we'll need more text than this, in order to avoid confusion.
For example, if INFOs don't impact the
state of Offer/Answer, does it mean that the candidates will NOT be
included in subsequent offer/answer transactions?
</pre>
            </blockquote>
            <pre wrap="">No, in a subsequent offer/answer transaction you would include the
actual set of candidates, i.e.  in case you use 100rel
and do a second O/A before the 200OK to the INVITE, you would include
in the offer the candidates present in the initial
offer and all candidates there were trickled in the meantime.
</pre>
          </blockquote>
          <pre wrap="">Well, then the INFO *does* impact the Offer/Answer state, doesn't it -
assuming the set of candidates is part of the O/A state?
</pre>
        </blockquote>
        <pre wrap="">Well, this definition is probably the source of this discussion. The
draft does not assume that the candidates are part of the O/A state.
Figure 2 tries to clarify that by using the  logical entities "O/A
module" and "ICE agent".
The candidates just affect the state of the the latter.
This is also the reason for the comparison of trickled candidates with
peer reflexive candidates.
Both are learned by the ICE agent without the need for an additional O/A
exchange.
</pre>
      </blockquote>
      <pre wrap="">
O/A state is more than the actual O/A transactions. In my opinion the
current SDP state is also part of the O/A state. Anyway, if that is not
the case, we need further clarification on what we really mean by ³O/A
state². If you only refer to the O/A transactions, then it should be
clearly stated.</pre>
    </blockquote>
    A proposal for improved text:<br>
    <br>
    old:<br>
    <meta http-equiv="content-type" content="text/html;
      charset=windows-1252">
    <pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Such INFO requests do not
   impact the state of Offer/Answer, nor do they have an impact on the
   version number in the "o=" line.  In that regard they are actually
   comparable to Peer Reflexive candidates that ICE agents can discover
   during ICE processing.

</pre>
    new:<br>
    <meta http-equiv="content-type" content="text/html;
      charset=windows-1252">
    <pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Such INFO requests do not impact the state of Offer/Answer other than providing additional candidates. 
Consequently, they do not have an impact on the version number in the "o=" line.  
In that regard trickled candidates are actually comparable to Peer Reflexive candidates that 
ICE agents can discover during ICE processing without without the need for an additional O/A
exchange.</pre>
    <br>
    <br>
    <blockquote
      cite="mid:D364B55A.8B73%25christer.holmberg@ericsson.com"
      type="cite">
      <pre wrap="">


</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Also, assume candidates A, B and C are included in the offer/answer
transaction, and then the INFO contains (for whatever reason) candidates
A and B.
</pre>
        </blockquote>
        <pre wrap="">This is an error
</pre>
      </blockquote>
      <pre wrap="">
So, what shall the receiver do if it happens? Discard the candidate(s)?</pre>
    </blockquote>
    Actually this should already be covered at the end of 4.2<br>
    <pre wrap=""><meta http-equiv="content-type" content="text/html; charset=windows-1252">When receiving INFO requests carrying any candidates, agents will
   therefore first identify and discard the SDP lines containing
   candidates they have already received in previous INFO requests or in
   the Offer/Answer exchange preceding them.  
...  After identifying and discarding known
   candidates, agents will then process the remaining, actually new
   candidates according to the rules described in
   [<a href="https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-04#ref-I-D.ietf-mmusic-trickle-ice">I-D.ietf-mmusic-trickle-ice</a>].<pre class="newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></pre></pre>In said error case there aren't any remaining candidates, thus nothing to do.  
I can add a clarification at the end of 4.2

<blockquote cite="mid:D364B55A.8B73%25christer.holmberg@ericsson.com" type="cite"><pre wrap="">


</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">  What is the state of C? Can INFO be used to *remove* previously
negotiated candidates`?
</pre></blockquote><pre wrap="">No, this would need an ICE restart.
</pre></blockquote><pre wrap="">
Needs to be clear. Perhaps there should be a ³ICE Restrictions² section,
or something similar.</pre></blockquote>Why? There never was a candidate removal feature in ICE (nor Trickle-ICE) and I don't think that this document needs to specify anything along that lines.
<blockquote cite="mid:D364B55A.8B73%25christer.holmberg@ericsson.com" type="cite"><pre wrap="">


</pre><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><pre wrap="">However, I assume that they WILL be impacted by an ICE re-start.
</pre></blockquote><pre wrap="">In case of a restart everything starts from scratch.
</pre></blockquote><pre wrap="">Needs to be explicitly indicated.
</pre></blockquote><pre wrap="">Agreed
</pre></blockquote><pre wrap="">
Good :)


</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Q2:

</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Section 4.2 says:

	"INFO requests containing "a=ice-pwd:" and "a=ice-ufrag:" attributes
that do not match those of the current ICE processing
     	session MUST be discarded."

</pre></blockquote><pre wrap="">This obviously applies if the INFO contains *OLD* pwd/ufrag values.
But, I also assume that it is not allowed to provide *NEW* values in an
INFO. If so, it needs to be clarified.
Correct, the current text does not allow this. I can clarify.
</pre></blockquote><pre wrap="">Ok.



Q3:

</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Section 4.2 says:

	"Such "a=mid:" attributes MUST immediately precede the list of
candidates for that specific "m=" line."

I don't think we need to say that. It is enough that the mid
attribute is associated with the same m= line as the candidates. I.e.
normal SDP procedures apply.
</pre></blockquote><pre wrap="">You're right, it is not strictly needed. However, the current text was
the outcome of a longer discussion with Paul Kyzivat. I would have to
look up the details that lead to this format.
Additionally, as the grammar for the info-package is written in a way
that prescribes the order of the attributes, I'd prefer to keep it as
is, unless there is a real need for more flexibility.
</pre></blockquote><pre wrap="">So, what happens if the mid attribute is NOT where it is supposed to be?
</pre></blockquote><pre wrap="">This is an error case, which traditionally aren't covered in too much
detail in RFCs.
</pre></blockquote><pre wrap="">
Well, I think we need to have some text on error cases. See more below.</pre></blockquote>
<blockquote cite="mid:D364B55A.8B73%25christer.holmberg@ericsson.com" type="cite"><pre wrap="">


</pre><blockquote type="cite"><pre wrap="">You could think about a 488 or 606 or you could be liberal in what you
receive.
</pre><blockquote type="cite"><pre wrap="">Shall the receiver reject the trickled candidates(s)?

That brings up another question: how does a receiver reject received
candidates?
</pre></blockquote><pre wrap="">Why would you need that? That was never a requirement before.

</pre><blockquote type="cite"><pre wrap="">Remember that the receiver will always send 200 OK to the INFO request.
</pre></blockquote><pre wrap="">No, you can also send an error response.
</pre></blockquote><pre wrap="">

The INFO response is often sent by the SIP stack, before the Info Package
content has been handed to the application, and as long as the SIP stack
supports the Info Package as such, a 200 OK will be sent. If there is some
errors on the application level it needs to be dealt with some other way.
Please see section 4.2.2 of RFC 6086.</pre></blockquote>My interpretation of that section is that you MAY send an error since the INFO request from above  is not syntactically correct.
However, 200OK and dealing with content on application level would also be fine. 
I don't think that this document needs to say anything beyond RFC6086.

Regards
Thomas
<blockquote cite="mid:D364B55A.8B73%25christer.holmberg@ericsson.com" type="cite"><pre wrap="">

Regards,

Christer





</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">

</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Alternatively, we could actually remove the m= line, and replace it
with the mid attribute (in which case the attribute obviously need to
precede the list of candidates).
Q4:

Section 4.2 says:

	"In every INFO request agents MUST include all local candidates they
have previously signaled."

First, I don't think you want to include candidates that are no
longer used, do you?
</pre></blockquote><pre wrap="">What do you mean by no longer used?
</pre></blockquote><pre wrap="">Candidates that were used before a re-start, or have been
removed/disabled using some other means.


</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Second, it is also unclear whether this includes candidates that have
been signalled using Offer/Answer (I guess Q5 answers that).

Third, do we really want to include all candidates? If we want to
regard INFOs as peer reflexive candidates, why not only include the
new ones?
</pre></blockquote><pre wrap="">Always including the complete set of candidates (i.e. those from the
initial offeror answer plus the ones that were trickled afterwards) is
motivated by the infamous support for UDP transport in SIP.
</pre></blockquote><pre wrap="">Infamous? Also keep in mind that STUN is transported over UDP, so peer
reflexive candidates are in no better position.

</pre><blockquote type="cite"><pre wrap="">In order to have things simple we decided already in the early days of
this draft to always have the complete set in the INFO.
Then, you don't need to care about lost INFOs and can just drop any
late arrivals.
</pre></blockquote><pre wrap="">Well, late arrivals should be dropped anyway.


Q5:

</pre><blockquote type="cite"><blockquote type="cite"><pre wrap="">Section 4.2 says:

    	"When receiving INFO requests carrying any candidates, agents
will
     	therefore first identify and discard the SDP lines containing
     	candidates they have already received in previous INFO requests
or in
     	the Offer/Answer exchange preceding them."

Where does the text says that INFOs shall carry candidates that have
been signalled in Offer/Answer? The text in Q4?
</pre></blockquote><pre wrap="">Yes
</pre></blockquote><pre wrap="">Ok.

Regards,

Christer

</pre><blockquote type="cite"><pre wrap="">-----Original Message-----
From: mmusic [<a class="moz-txt-link-freetext" href="mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</a>] On Behalf Of Thomas
Stach
Sent: 17 May 2016 17:00
To: MMUSIC<a class="moz-txt-link-rfc2396E" href="mailto:mmusic@ietf.org">&lt;mmusic@ietf.org&gt;</a>
Subject: [MMUSIC] Fwd: New Version Notification for
draft-ietf-mmusic-trickle-ice-sip-04.txt

All,

the changes from draft-ietf-mmusic-trickle-ice-sip-03 include

- replaced reference to RFC5245 with draft-ietf-mmusic-rfc5245bis and
draft-ietf-mmusic-ice-sip-sdp
- corrected Figure 10, credits to Ayush Jain for finding the bug
- referencing a=rtcp and a=rtcp-mux handling from
draft-ietf-mmusic-ice-sip-sdp
- referencing a=rtcp-mux-exclusive handling from
draft-ietf-mmusic-mux-exclusive, enhanced ABNF to support
a=rtcp-mux-exclusive
- clarifying that draft-ietf-mmusic-sdp-mux-attributes applies for the
application/trickle-ice-sdpfrag body

Currently there are no open issues in this draft. However, it could
probably benefit from a thorough review.
So, comments welcome.

With respect to progressing this work, I think that it should go
forward alongside with draft-ietf-ice-trickle since any updates of that
document might influence the content of this draft.

Regards
Thomas



-------- Forwarded Message --------
Subject: 	New Version Notification for
draft-ietf-mmusic-trickle-ice-sip-04.txt
Date: 	Tue, 17 May 2016 06:50:19 -0700
From: 	<a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>
To: 	Thomas Stach<a class="moz-txt-link-rfc2396E" href="mailto:thomass.stach@gmail.com">&lt;thomass.stach@gmail.com&gt;</a>, Emil Ivov
<a class="moz-txt-link-rfc2396E" href="mailto:emcho@jitsi.org">&lt;emcho@jitsi.org&gt;</a>, Enrico Marocco<a class="moz-txt-link-rfc2396E" href="mailto:enrico.marocco@telecomitalia.it">&lt;enrico.marocco@telecomitalia.it&gt;</a>,
Christer Holmberg<a class="moz-txt-link-rfc2396E" href="mailto:christer.holmberg@ericsson.com">&lt;christer.holmberg@ericsson.com&gt;</a>



A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-04.txt
has been successfully submitted by Thomas Stach and posted to the IETF
repository.

Name:		draft-ietf-mmusic-trickle-ice-sip
Revision:	04
Title:		A Session Initiation Protocol (SIP) usage for Trickle ICE
Document date:	2016-05-17
Group:		mmusic
Pages:		36
URL:<a class="moz-txt-link-freetext" href="https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice">https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice</a>
-sip-04.txt
Status:<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice">https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice</a>-
sip/
Htmlized:<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip">https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip</a>
-04
Diff:<a class="moz-txt-link-freetext" href="https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-s">https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-s</a>
ip-04

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

      This document defines usage semantics for Trickle ICE with the
      Session Initiation Protocol (SIP).

               
             


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

The IETF Secretariat



_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>

</pre></blockquote></blockquote><pre wrap="">
</pre></blockquote><pre wrap="">

</pre>

</blockquote>
</body></html>
--------------020905080504070607090305--


From nobody Fri May 20 11:37:34 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA7FD12D5E5 for <mmusic@ietfa.amsl.com>; Fri, 20 May 2016 11:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7i66nmf-Ivdo for <mmusic@ietfa.amsl.com>; Fri, 20 May 2016 11:37:31 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A603D12DA7E for <mmusic@ietf.org>; Fri, 20 May 2016 11:36:59 -0700 (PDT)
Received: by mail-ig0-x234.google.com with SMTP id bi2so142675227igb.0 for <mmusic@ietf.org>; Fri, 20 May 2016 11:36:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=9p0uF+HfU3LMqS42wdS59pOlqXZfca8YC0oHxoI3D6U=; b=v8+a/YeDQZWKn+8yZugg4KICyZZrCo1Y42O7KPzGqjsyB5s2s0K8CMh2KhyFlNc+5p Kt0RL+Dqtk+rEvlnpe6ewWjTe3AQsf6DYFSauVmQwVyR+Z+mLHoQPBRIspLOdR4Uj0Nf 2QLlTsiPsb0aCpxuPZTH/UuXLuEyYI1j0spTesiH5X6rncLhSc/TS6Z92hMvFocX06v1 D2nfMzxOsYrRD/u4uoPE3KHnOZRS/AL3xdGN+Qs5XMNJIFbVTH5nK02HBqZWT6lJ8x/r RFos14xYvCPqb27xXuq6xDgvF4FdpNXY1Dwh0OO81sNT1XuIIw7uyNLkD8scZ5A31a8j YoMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=9p0uF+HfU3LMqS42wdS59pOlqXZfca8YC0oHxoI3D6U=; b=MwNXw6GvfjeD1q7P3SIRi4ZjMlDYMBQ8KMUPAZzlvwyzbxS1KeATWGB4PbyIhx1IVJ nKljxIsfxiFvYlMmp7R6s4Or7mUv/obERqzjG/7pzV+YQQWCknsLSJyt0hycA7dTRJ7o dJ/aRIs11NpVCcSFmHq0Sb6Ces5BiKnDz7enSm03SkuuL83nc0TAfx1eY7cI1ZOzHMq6 BDiJCgVxzGKqBhcPdZn7oOPmzUpSPkZqyT6kPjnX751qBgnPbw/TJfcKW5C447p53ULG q6Uxj6UoTAHlEKja2HfQYrlQPRTL/AEwAhthWUsGu7C+qeweQLePCv9vpDA6E0fQHKKe MwWg==
X-Gm-Message-State: AOPr4FXt7Vp5sCGU/VKQZWFoF6CrH3BA3f2L7ZZPiCY4nT1e47AUtfO13YfXTEWUFXIQcAibs1iD++1eb4SEUA==
MIME-Version: 1.0
X-Received: by 10.50.33.81 with SMTP id p17mr4350126igi.58.1463769418999; Fri, 20 May 2016 11:36:58 -0700 (PDT)
Received: by 10.36.43.23 with HTTP; Fri, 20 May 2016 11:36:58 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FD995A@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <CABkgnnXc_c_Wu8V0HX9Kt4+GEuSSK8noyKkTS+gNEbNBs_0GQQ@mail.gmail.com> <CABkgnnXjoY4urEcmGBiZMJ3vMxqkqjRkUNS_ezHg1_1uWVfysA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FD995A@ESESSMB209.ericsson.se>
Date: Fri, 20 May 2016 14:36:58 -0400
Message-ID: <CABkgnnV9nouafVaOZjnUah8M+iVqw1T26Mstd9spWnrBTNb7kw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/bTPPTXaxJ7DZ8f0NZOAcIPVA_YE>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 18:37:33 -0000

On 19 May 2016 at 15:32, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Please also check the text that ended up in the draft :)


I think that the text is good.

Nits and grammar suggestions follow:

     Multiple SDP fingerprint attributes can be associated with an m-
     line. This can occur if multiple fingerprints have been calculated
     for a certificate, using different hash functions. It can also

Drop the comma

     occur if one or more fingerprints associated with multiple
     certificates have been calculated, e.g. for cases where multiple
     certificates will be used for media associated with an m- line
     (e.g. separate certificates for RTP and RTCP), or where it is not

You have two nested "e.g." statements.  I would split the first e.g.
into a new sentence starting: This might be needed if multiple
certificates...

     known which certificate will be used when the fingerprints are
     exchanged. In such cases, one or more fingerprints MUST be
     calculated for each possible certificate.

     If fingerprints associated with multiple certificates are
     calculated, the same set of fingerprints (using the same hash
     functions) MUST be calculated for each certificate associated

"the same set of hash functions MUST be used to calculate fingerprints
for every certificate associated"

     with the m- line.

     For each used certificate, an endpoint MUST be able to match at
     least one fingerprint, calculated using the hash function that the
     endpoint supports and considers most secure, with the used
     certificate. If there is no match, the endpoint MUST NOT establish
     the TLS connection. In addition, the endpoint MAY also check other
     fingerprints (calculated using other hash functions) that it has

"MAY also check fingerprints calculated using other hash functions that it has"

     received for a match. For each hash function checked, one of the
     received fingerprints MUST match the used certificate.

     NOTE: The SDP fingerprint attribute does not contain a reference to
     a specific certificate. Endpoints need to compare the fingerprint
     with a certificate hash in order to look for a match.


From nobody Fri May 20 16:07:58 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4959212D672; Fri, 20 May 2016 16:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 o1n3U2fT7YhU; Fri, 20 May 2016 16:07:53 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D83B12D673; Fri, 20 May 2016 16:07:53 -0700 (PDT)
Received: from [10.0.1.18] (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 u4KN7odr009156 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 20 May 2016 18:07:50 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.18]
From: "Ben Campbell" <ben@nostrum.com>
To: "Suhas Nandakumar" <suhasietf@gmail.com>
Date: Fri, 20 May 2016 18:07:49 -0500
Message-ID: <9FFB7971-3556-498B-B267-59089FBD47D7@nostrum.com>
In-Reply-To: <CAMRcRGTq_3_diKAavsf_5dwq1KxmA6R9qygb7YTzQ7wp=dwByw@mail.gmail.com>
References: <C03E65BE-11DF-4AD5-B646-243D28089DC4@nostrum.com> <CAMRcRGTq_3_diKAavsf_5dwq1KxmA6R9qygb7YTzQ7wp=dwByw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/B3DGPSrFmRzHH9HYirkv5y7M6EM>
Cc: mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Subject: Re: [MMUSIC] AD Evaluation of draft-ietf-mmusic-sdp-mux-attributes-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 23:07:56 -0000

Apologies for my slow response. The last month has been a perfect storm =

of productivity killers. I'm digging out of the backlog now. Comments =

inline, with sections that appear resolved removed.

There is one issue (zrtp-hash) where I will start a separate thread =

shortly.

Thanks!

Ben.

On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:

> Hello Ben
>
>  Sorry for the delay in responding. Many thanks for the detailed =

> review.
>
>  Please find my responses inline (marked by [Suhas]).
>
> Cheers
> Suhas
>
> On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell <ben@nostrum.com> wrote:
>
>> Hi,
>>
>> Here is my AD evaluation of draft-ietf-mmusic-sdp-mux-attributes-12. =

>> I
>> would like at least the substantive
>> section to be discussed before going to IETF last call.
>>
>> Thanks!
>>
>> Ben.
>>
>> ----------
>>
>> # Substantive #
>>
>> - This is very long and detailed. Are the authors and chairs =

>> comfortable
>> that all sections have had sufficient review?
>>
>> -4.0: It would be helpful to add a paragraph describing how these =

>> semantic
>> groupings map to the categories.
>>
>
> [Suhas] The semantic groupings were added as a informal reference and =

> they
> don't really interact with the categories as such.

So I have to wonder why we have the groupings. But I guess at this point =

in the process, it's not worth changing that.

>
> Does the following rephrasing work
>
> *"Attributes in an SDP session description can be defined at the
> **session-level
> or  media-level or  source-level. Informally, there are various =

> semantic
> grouping for these attributes. One such grouping could be as noted =

> below:*
>
>
>
>
>
>
>
>
>
>
> *   o  Attributes related to media content such as media type, =

> encoding
>      schemes, payload types.   o  Attributes specifying media =

> transport
> characteristics like RTP/RTP      Control Protocol (RTCP) port =

> numbers,
> network addresses, QOS.   o  Metadata description attributes capturing
> session timing and      origin information.   o  Attributes =

> establishing
> relationships between media descriptions      such as grouping =

> framework
> [RFC5888 <https://tools.ietf.org/html/rfc5888>]The proposed framework
> defines categories for the SDP attributes under multiplexing and =

> assigns
> each SDP attribute to an appropriate multiplexing category.*
>
> *Since the multiplexing categories defined in this specification are
> independent of any informal semantic grouping of the SDP attributes, =

> the
> categorizations assigned against each attribute  MUST be considered as
> normative assignments under multiplexing. "*

All fine, except the last sentence is pretty meta--it uses normative =

language to talk about normative language ("MUST be considered =

normative"). I'm not entirely sure what you intend there, but how about =

something to the effect of "... the categorizations assigned against =

each attribute are normative."

>
>
>
>> -4.2: I recommend choosing a category name that is not a 2119 =

>> keyword.
>>   Maybe something like "not mux-able" or "unsafe"?
>>
>
> [Suhas]
>
> Initially that category was called "BAD" as in
>
> https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux-attrib=
utes/01/
>
> However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D was a=
 bad choice =

> :-)
>
> Either of the following options seems fine to me
>
>    1.
>
>    NOT-RECOMMENDED [ we use hyphen separated multi word format in =

> other
>    category names]
>    2. UNSAFE

I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you intend =

the category name to mean "NOT RECOMMENDED" in the 2119 sense.

>
>
>
>
>>
>> -4.3: Please don't use a 2119 keyword as part of the definition
>> of a category. This creates sort of a circular dependency; that is
>> attributes are in this category because they MUST be identical; but =

>> they
>> MUST be identical because they are in this category. I suggest =

>> describing
>> the category descriptively, and adding a separate sentence to say
>> "Attributes
>> in the IDENTICAL category MUST be identical across all media =

>> descriptions."
>>
>
>
> [Suhas]. I have removed the usage of word identical from the =

> definition as
> below. Please let me know if this works.
>
>
> Category: IDENTICAL
>
> Attributes  and their associated values (if present) in the IDENTICAL
> category MUST be repeated across all the media descriptions under
> multiplexing.
>

Okay.

[...]

>
>
>
>> -5.8 and 5.9:
>>     The last paragraph of 5.8 seems redundant with section 5.9.
>>
>> -5.8, last paragraph:
>>
>>     "Hence multiplexing MUST NOT be performed even in this
>>     alternate scenario." seems to contradict the category selection =

>> of
>>     "NOT RECOMMENDED" (but see previous comment about not using 2119
>>     keywords in a category title.)
>>
>>
> [Suhas] The idea here is to not perform multiplexing and hence the =

> category
> of NOT RECOMMENDED assigned. I can update this once we finalize on the
> right naming for "NOT RECOMMENDED"

This argues for the "UNSAFE" name, since the actual normative guidance =

is stronger than "NOT RECOMMENDED". (Unless you want a "MUST NOT" name =

:-)  )

>
>
>
>> -5.24, last paragraph: "it is recommended to consult the
>>   document defining the attribute."
>>
>>   I assume one should _always_ refer to the specification of
>>   an SDP attribute before trying to mux it. But that doc is
>>   not going to explain muxing issues, is it?
>>
>>
> [Suhas]
>
> Since cparmin/cparmax can define numerical values/ranges
>
> for any of b=3D or a=3D attributes (identified via cpar), there is no e=
asy =

> way
> to assign a multiplexing category unless one knows what cpar is being
>
> used and the assignned numerical values to each of cparmin/cparmax =

> mean.
> Thus the category SPECIAL has been assigned as a recommendation for =

> the
> implementor to consult the spec that defines a particular usage of =

> cpar,
> cparmin and cparmax combination to really see what=E2=80=99s going on.
>
> This is very similar to extmap or RTCP Application feedback message =

> type
>
> How about following rephrasing
>
>
> *"The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and maxim=
um
> numerical values associated with the attributes described in a=3Dcpar. =

> Since
> a cpar attribute can either define*
>
> *=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attribu=
te,  the multiplexing =

> category *
>
> *depends on actual attribute being encapsulated and the implications =

> of the
> numerical values assigned. Hence it is recommended to consult the
> specification defining the the attributes (cparmin/cparmax) to further
> analyze their behavior under multiplexing."*

That works for me.

>
>
>
>> -5.26:
>>   -"Support of this extension is OPTIONAL."
>>   Please don't use 2119 keywords to describe existing requirements
>>   from other docs, unless in direct quotes.
>>
>>
>
> [Suhas] This sentence is taken directly from RFC6714. (
> https://tools.ietf.org/html/rfc6714)

Sure, but it's not attributed as a quote. I suggest something to the =

effect of "This is an optional extension according to [RFC6714]", " =

[RFC6714] states that this extension is 'OPTIONAL'",  or even the exact =

same language as currently in the draft, but without the capitalized =

OPTIONAL.

[...]

>
>
>
>> - 5.39:
>>   I=E2=80=99m not a zrtp expert, but it seems like it might
>>   be more complicated than this. Section 8 of 6189 says
>>   =E2=80=9CThe a=3Dzrtp-hash attribute  can only be included in the
>>   SDP at the media level since Hello messages sent in
>>   different media streams will have unique hashes.=E2=80=9D
>>   I wonder if this shouldn't be =E2=80=9Cidentical=E2=80=9D?
>>
>>
> [Suhas] The category TRANSPORT is the appropriate assignment. This =

> spec
> assigns category for these attributes over the multiplexed transport.
>
> So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.
>
> The zrtp-hash selected must correspond to the m=3Dline that is selected=
 =

> for
> BUNDLE once the O/A negotiation completes. Thus the category =

> TRANSPORT.
>
>

I _think_ you are right, but there may be an interaction here that can =

break things I will think about that more, and respond to this issue is =

a separate thread.

>
>
>
>>
>> -5.45:
>>   6193 is an ISE stream RFC. Does anyone actually use
>>   in a context where muxing matters?
>>
>
> [Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.

That seems reasonable, unless  you know of good reasons otherwise.

>>
>> -15.1:
>>   - Is there no need for a spec for any newly registered categories?
>>   - 2nd to last paragraph: "This seems vague for a MUST. Do you =

>> expect
>>     the registration of a new category to change the categories
>>     already assigned to existing SDP parameters? Is it possible
>>     that a new category only applies to some new SDP parameters?"
>>
>
> [Suhas] The following 2 paragraphs are supposed to mean that new
> multiplexing categories require new registrations via a spec and
> applicability of the new category to new SDP attributes and possibly
> existing SDP attributes ( if the new category makes more sense). What =

> would
> be a better framing to capture the intent ?
>
> "*Further entries can be registered on a first-come first-serve basis. =

> Each
> registration needs to indicate the multiplexing category value to be =

> added
> to the "Multiplexing Categories" subregistry as defined in this =

> section.*
>
> *Such a registration MUST also indicate the applicability of the newly
> defined multiplexing category value to various subregistries defined =

> at
> "Session Description Protocol (SDP) Parameters".*

That works for me.

>
>
>>   - Last paragraph: 4566 procedures apply to what? The text just said
>>     new categories are first-come-first server. I don=E2=80=99t think
>>     4566 set policies for how to change mux categories.
>>
>
> [Suhas] Agreed. I prefer removing this line altogether. Please let me =

> know
>

I agree.

>>
>> -15.2.1:
>>   How do you expect the table to look after adding this RFC to the
>>   references? Will this RFC be added to the entries in the MUX
>>   column?
>>
>
> [Suhas] The plan was to add the reference to this RFC in the =

> "Reference
> Column"

Okay.

[...]


>
>>
>>
>> # Editorial #
>>
>
>> - The abstract is more detailed than needed. The point is to describe =

>> the
>> purpose of the draft. The second paragraph pretty much accomplishes =

>> that.
>>
>>
> [Suhas] How do this rephrase look
>
> =E2=80=9CThe purpose of this specification is to provide a framework fo=
r =

> analyzing
> the multiplexing characteristics of SDP attributes when SDP is used to
> negotiate the usage of single 5-tuple for sending and receiving media
> associated with multiple media descriptions,. This specification also
> categorizes the existing SDP attributes based on the framework =

> described
> herein.=E2=80=9D
>

That works for me.

[...]

>
>
>>
>> -5 and subsections: Is there any method to the ordering? They aren't
>>    in RFC order. It might make sense to group by the nature of the
>>    attributes, but if that is the case here it's not explained.
>>
>>
> [Suhas] These are not ordered as of today. I can order the 5.X =

> subsections
> by RFC order, if needed.

Unordered is also okay. I was just wondering if there was a logic that =

should be mentioned.


[...]

>
>
>>
>> -5.13, table:
>>   "Specific RTP extension document MUST be referred"
>>
>>
> [Suhas] The idea was to mean that , one should refer to the =

> specification
> that defines a specific RTP extension in order to understand the
> multiplexing behavior.
>
> Would the following rephrasing help instead
>
> "Refer to the document defining specific RTP Extension"
>
>

Yes, thanks.

>
>>   I don=E2=80=99t understand what that means. If you mean to
>>    say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=E2=80=
=99t use MUST.
>>
>> -5.22, table: "document needs to be referred" (several repetitions)
>>   I'm not sure what this means. Should it say "Refer to the
>>   specific document"?
>>
>>
> Similarly as above, would this reprhasing help
>
> "Refer to the document defining specific FEC Scheme
>
>

Similarly as above, Yes, thanks. :-)

>
>>
>> -6.3: "not clearly defined offer/answer usage"
>>   I'm not sure what is meant here. (Also, why is this not TBD or NOT
>>   RECOMMENDED?)
>>
>
> [Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind, =

> either the
> BUNDLE spec or this spec cannot define its mux behavior. This is due =

> to
> applicability of these specs under SD{ O/A usages alone.
>
> I can rephrase the above as
> "not defined under SDP Offer/Answer usage"

WFM, thanks.

[...]


From nobody Sat May 21 01:08:33 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4131512D61D for <mmusic@ietfa.amsl.com>; Sat, 21 May 2016 01:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKBuLg6B3Gi7 for <mmusic@ietfa.amsl.com>; Sat, 21 May 2016 01:08:29 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E597712D589 for <mmusic@ietf.org>; Sat, 21 May 2016 01:08:28 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-51-5740177aa767
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E7.28.12926.A7710475; Sat, 21 May 2016 10:08:27 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0294.000; Sat, 21 May 2016 10:08:26 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Thomas Stach <thomass.stach@gmail.com>, MMUSIC <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
Thread-Index: AQHRsEMOIliX14uf2EKWpAtozqzJo5+9BuOAgACWdbCAAtrVgIAALipggACd4ACAAGZjgIAAC+eAgAFTUNA=
Date: Sat, 21 May 2016 08:08:25 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FDDB5B@ESESSMB209.ericsson.se>
References: <20160517135019.22271.65158.idtracker@ietfa.amsl.com> <573B23FD.3070903@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFDF3@ESESSMB209.ericsson.se> <573E0745.3010606@gmail.com> <7594FB04B1934943A5C02806D1A2204B37FD9934@ESESSMB209.ericsson.se> <573EB26E.7010509@gmail.com> <D364B55A.8B73%christer.holmberg@ericsson.com> <573F124D.5010005@gmail.com>
In-Reply-To: <573F124D.5010005@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FDDB5BESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2K7lm61uEO4weoeRoupyx+zWHw6sZXJ gclj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4Mr4NvUPc8Hu5YwVs/d9ZmtgXN3H2MXIySEh YCIxd14fM4QtJnHh3nq2LkYuDiGBI4wSy5c3QjlLGCW2bvoE5HBwsAlYSHT/0wZpEBFwkXj0 YgY7iC0skCSxd8lhJoh4ssSto89YIOwkiXsfD4AtYBFQldj29QnYYl4BX4npv/9Dzf/CJPHm 8AqwQZwCmhIrPxwBG8QIdNH3U2vAbGYBcYlbT+YzQVwqILFkz3moq0UlXj7+xwphK0msPbyd BaI+X2Lp0nZWiGWCEidnPmGZwCgyC8moWUjKZiEpg4jrSdyYOoUNwtaWWLbwNTOErSsx498h FmTxBYzsqxhFi1OLk3LTjYz1Uosyk4uL8/P08lJLNjECo+vglt+qOxgvv3E8xCjAwajEw7sg 3y5ciDWxrLgy9xCjBAezkgivDZ9DuBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFe/5eK4UIC6Ykl qdmpqQWpRTBZJg5OqQZGD0ORIznNUa8mhN3UbDXUbV5ydbHm6VdMS+fHreo21gh9mp7b1sGS IT7nYadJ5dLD0vc6WXg27M6IdCkULa8RZkjYWTBzlkXBkoZC50jDgxKzpHRZVrzxSKhbOOe8 YeXlo0rfq/+/rljRcFQskL+OPZt/hz13y9H+yxulMpuNXy+9ND/lzBklluKMREMt5qLiRACj tH6CqgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Wj_oiCOz2ccb6m2zImxrxIO7Ng4>
Subject: Re: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-trickle-ice-sip-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 08:08:32 -0000

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

Hi,


Q1:



The text in 3.3 says:



 "Such INFO requests do not impact the state of Offer/Answer, nor do

they have an impact on the version number in the "o=3D" line."



I think we'll need more text than this, in order to avoid confusion.

For example, if INFOs don't impact the

state of Offer/Answer, does it mean that the candidates will NOT be

included in subsequent offer/answer transactions?

No, in a subsequent offer/answer transaction you would include the

actual set of candidates, i.e.  in case you use 100rel

and do a second O/A before the 200OK to the INVITE, you would include

in the offer the candidates present in the initial

offer and all candidates there were trickled in the meantime.

Well, then the INFO *does* impact the Offer/Answer state, doesn't it -

assuming the set of candidates is part of the O/A state?

Well, this definition is probably the source of this discussion. The

draft does not assume that the candidates are part of the O/A state.

Figure 2 tries to clarify that by using the  logical entities "O/A

module" and "ICE agent".

The candidates just affect the state of the the latter.

This is also the reason for the comparison of trickled candidates with

peer reflexive candidates.

Both are learned by the ICE agent without the need for an additional O/A

exchange.



O/A state is more than the actual O/A transactions. In my opinion the

current SDP state is also part of the O/A state. Anyway, if that is not

the case, we need further clarification on what we really mean by =B3O/A

state=B2. If you only refer to the O/A transactions, then it should be

clearly stated.
A proposal for improved text:

old:


Such INFO requests do not

   impact the state of Offer/Answer, nor do they have an impact on the

   version number in the "o=3D" line.  In that regard they are actually

   comparable to Peer Reflexive candidates that ICE agents can discover

   during ICE processing.


new:


Such INFO requests do not impact the state of Offer/Answer other than provi=
ding additional candidates.

Consequently, they do not have an impact on the version number in the "o=3D=
" line.

In that regard trickled candidates are actually comparable to Peer Reflexiv=
e candidates that

ICE agents can discover during ICE processing without without the need for =
an additional O/A

exchange.

Is the statement regarding the "o=3D" line really true? For example, assume=
 you send an O/A, with candidates A and B. Then, you use INFO to add candid=
ate C. Then, you send a new O/A, with no other changes than candidate C add=
ed. Are you saying that the "o=3D" line shouldn't be updated, even if the O=
ffer now contains candidate C? I am not sure that is described even if C wa=
s provided as a "real" peer-reflexive candidate, so perhaps it has to be up=
dated in draft-ice-sip-sdp too.

Perhaps the O/A section needs to be re-structured, with a sub-section for e=
ach O/A property, where the impacts/non-impacts are described.




Also, assume candidates A, B and C are included in the offer/answer

transaction, and then the INFO contains (for whatever reason) candidates

A and B.

This is an error



So, what shall the receiver do if it happens? Discard the candidate(s)?
Actually this should already be covered at the end of 4.2


When receiving INFO requests carrying any candidates, agents will

   therefore first identify and discard the SDP lines containing

   candidates they have already received in previous INFO requests or in

   the Offer/Answer exchange preceding them.

...  After identifying and discarding known

   candidates, agents will then process the remaining, actually new

   candidates according to the rules described in

   [I-D.ietf-mmusic-trickle-ice<https://tools.ietf.org/html/draft-ietf-mmus=
ic-trickle-ice-sip-04#ref-I-D.ietf-mmusic-trickle-ice>].
In said error case there aren't any remaining candidates, thus nothing to d=
o.  I can add a clarification at the end of 4.2

It would have to be clear that a previously provided candidate, if missing =
(for whatever reason) in a subsequent INFO, does not mean the candidate has=
 been "disabled" or "removed". The important thing are the NEW candidate(s)=
, i.e. the candidates that the receiver haven't seen before - the rest is t=
here just for information.



  What is the state of C? Can INFO be used to *remove* previously

negotiated candidates`?

No, this would need an ICE restart.



Needs to be clear. Perhaps there should be a =B3ICE Restrictions=B2 section=
,

or something similar.
Why? There never was a candidate removal feature in ICE (nor Trickle-ICE) a=
nd I don't think that this document needs to specify anything along that li=
nes.

My assumption has been that, if you send a new O/A, where are previously pr=
ovided candidate has been removed, it means that it has been removed. But, =
whether that is true or not, perhaps it needs clarification in 5245bid and/=
or draft-ice-sip-sdp.

...



The INFO response is often sent by the SIP stack, before the Info Package

content has been handed to the application, and as long as the SIP stack

supports the Info Package as such, a 200 OK will be sent. If there is some

errors on the application level it needs to be dealt with some other way.

Please see section 4.2.2 of RFC 6086.
My interpretation of that section is that you MAY send an error since the I=
NFO request from above  is not syntactically correct. However, 200OK and de=
aling with content on application level would also be fine. I don't think t=
hat this document needs to say anything beyond RFC6086. Regards Thomas

The SIP stack MAY of course understand the content, but the whole idea of s=
ending application layer data with INFO is that the SIP stack does NOT need=
 to know anything about the semantics and syntax of that application layer =
data (the data could even be encrypted with a key that the SIP stack does n=
ot have access too, or encoded with some algorithm the SIP stack does not u=
nderstand). So, you cannot make an assumption that the SIP stack will detec=
t an error and send a non-200 response. The assumption has to be that, if t=
he usage of the Info Package as such has been negotiated for the session, t=
he sender will receive a 200 OK no matter if the application layer data is =
correct or not.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37FDDB5BESESSMB209erics_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Consolas",serif;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red;mso-fareast-language:EN-US">Hi,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p>&nbsp=
;</o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Q1:<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>The text in 3.3 says:<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre> &quot;Such INFO requests do not impact the state of Offer/Answer, nor=
 do<o:p></o:p></pre>
<pre>they have an impact on the version number in the &quot;o=3D&quot; line=
.&quot;<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>I think we'll need more text than this, in order to avoid confusion.<o=
:p></o:p></pre>
<pre>For example, if INFOs don't impact the<o:p></o:p></pre>
<pre>state of Offer/Answer, does it mean that the candidates will NOT be<o:=
p></o:p></pre>
<pre>included in subsequent offer/answer transactions?<o:p></o:p></pre>
</blockquote>
<pre>No, in a subsequent offer/answer transaction you would include the<o:p=
></o:p></pre>
<pre>actual set of candidates, i.e.&nbsp; in case you use 100rel<o:p></o:p>=
</pre>
<pre>and do a second O/A before the 200OK to the INVITE, you would include<=
o:p></o:p></pre>
<pre>in the offer the candidates present in the initial<o:p></o:p></pre>
<pre>offer and all candidates there were trickled in the meantime.<o:p></o:=
p></pre>
</blockquote>
<pre>Well, then the INFO *does* impact the Offer/Answer state, doesn't it -=
<o:p></o:p></pre>
<pre>assuming the set of candidates is part of the O/A state?<o:p></o:p></p=
re>
</blockquote>
<pre>Well, this definition is probably the source of this discussion. The<o=
:p></o:p></pre>
<pre>draft does not assume that the candidates are part of the O/A state.<o=
:p></o:p></pre>
<pre>Figure 2 tries to clarify that by using the&nbsp; logical entities &qu=
ot;O/A<o:p></o:p></pre>
<pre>module&quot; and &quot;ICE agent&quot;.<o:p></o:p></pre>
<pre>The candidates just affect the state of the the latter.<o:p></o:p></pr=
e>
<pre>This is also the reason for the comparison of trickled candidates with=
<o:p></o:p></pre>
<pre>peer reflexive candidates.<o:p></o:p></pre>
<pre>Both are learned by the ICE agent without the need for an additional O=
/A<o:p></o:p></pre>
<pre>exchange.<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>O/A state is more than the actual O/A transactions. In my opinion the<=
o:p></o:p></pre>
<pre>current SDP state is also part of the O/A state. Anyway, if that is no=
t<o:p></o:p></pre>
<pre>the case, we need further clarification on what we really mean by =B3O=
/A<o:p></o:p></pre>
<pre>state=B2. If you only refer to the O/A transactions, then it should be=
<o:p></o:p></pre>
<pre>clearly stated.<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">A proposal for improved text:<br>
<br>
old:<br>
<br>
<o:p></o:p></p>
<pre>Such INFO requests do not<o:p></o:p></pre>
<pre>&nbsp;&nbsp; impact the state of Offer/Answer, nor do they have an imp=
act on the<o:p></o:p></pre>
<pre>&nbsp;&nbsp; version number in the &quot;o=3D&quot; line.&nbsp; In tha=
t regard they are actually<o:p></o:p></pre>
<pre>&nbsp;&nbsp; comparable to Peer Reflexive candidates that ICE agents c=
an discover<o:p></o:p></pre>
<pre>&nbsp;&nbsp; during ICE processing.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<p class=3D"MsoNormal">new:<br>
<br>
<o:p></o:p></p>
<pre>Such INFO requests do not impact the state of Offer/Answer other than =
providing additional candidates. <o:p></o:p></pre>
<pre>Consequently, they do not have an impact on the version number in the =
&quot;o=3D&quot; line.&nbsp; <o:p></o:p></pre>
<pre>In that regard trickled candidates are actually comparable to Peer Ref=
lexive candidates that <o:p></o:p></pre>
<pre>ICE agents can discover during ICE processing without without the need=
 for an additional O/A<o:p></o:p></pre>
<pre>exchange.<o:p></o:p></pre>
<p class=3D"MsoNormal"><br>
<span style=3D"color:red">Is the statement regarding the &#8220;o=3D&#8221;=
 line really true? For example, assume you send an O/A, with candidates A a=
nd B. Then, you use INFO to add candidate C. Then, you send a new O/A, with=
 no other changes than candidate C added. Are you
 saying that the &#8220;o=3D&#8221; line shouldn&#8217;t be updated, even i=
f the Offer now contains candidate C? I am not sure that is described even =
if C was provided as a &#8220;real&#8221; peer-reflexive candidate, so perh=
aps it has to be updated in
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans=
-serif;color:red">draft-ice-sip-sdp</span><span style=3D"color:red"> too.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:red"><o:p>&nbsp;</o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:red">Perhaps the O/A section ne=
eds to be re-structured, with a sub-section for each O/A property, where th=
e impacts/non-impacts are described.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:windowtext"><o:p>&nbsp;</o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p>&nbsp;</o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>Also, assume candidates A, B and C are included in the offer/answer<o:=
p></o:p></pre>
<pre>transaction, and then the INFO contains (for whatever reason) candidat=
es<o:p></o:p></pre>
<pre>A and B.<o:p></o:p></pre>
</blockquote>
<pre>This is an error<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>So, what shall the receiver do if it happens? Discard the candidate(s)=
?<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">Actually this should already be covered at the end o=
f 4.2<br>
<br>
<o:p></o:p></p>
<pre>When receiving INFO requests carrying any candidates, agents will<o:p>=
</o:p></pre>
<pre>&nbsp;&nbsp; therefore first identify and discard the SDP lines contai=
ning<o:p></o:p></pre>
<pre>&nbsp;&nbsp; candidates they have already received in previous INFO re=
quests or in<o:p></o:p></pre>
<pre>&nbsp;&nbsp; the Offer/Answer exchange preceding them.&nbsp; <o:p></o:=
p></pre>
<pre>...&nbsp; After identifying and discarding known<o:p></o:p></pre>
<pre>&nbsp;&nbsp; candidates, agents will then process the remaining, actua=
lly new<o:p></o:p></pre>
<pre>&nbsp;&nbsp; candidates according to the rules described in<o:p></o:p>=
</pre>
<pre>&nbsp;&nbsp; [<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic=
-trickle-ice-sip-04#ref-I-D.ietf-mmusic-trickle-ice">I-D.ietf-mmusic-trickl=
e-ice</a>].<o:p></o:p></pre>
<p class=3D"MsoNormal">In said error case there aren't any remaining candid=
ates, thus nothing to do.&nbsp; I can add a clarification at the end of 4.2=
<span style=3D"color:windowtext"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:windowtext"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">It would have to be clear that a previous=
ly provided candidate, if missing (for whatever reason) in a subsequent INF=
O, does not mean the candidate has been &#8220;disabled&#8221;
 or &#8220;removed&#8221;. The important thing are the NEW candidate(s), i.=
e. the candidates that the receiver haven&#8217;t seen before &#8211; the r=
est is there just for information.<o:p></o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p>&nbsp;</o:p></pre>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre>&nbsp; What is the state of C? Can INFO be used to *remove* previously=
<o:p></o:p></pre>
<pre>negotiated candidates`?<o:p></o:p></pre>
</blockquote>
<pre>No, this would need an ICE restart.<o:p></o:p></pre>
</blockquote>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Needs to be clear. Perhaps there should be a =B3ICE Restrictions=B2 se=
ction,<o:p></o:p></pre>
<pre>or something similar.<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">Why? There never was a candidate removal feature in =
ICE (nor Trickle-ICE) and I don't think that this document needs to specify=
 anything along that lines.<span style=3D"color:windowtext"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:windowtext"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">My assumption has been that, if you send =
a new O/A, where are previously provided candidate has been removed, it mea=
ns that it has been removed. But, whether that
 is true or not, perhaps it needs clarification in 5245bid and/or draft-ice=
-sip-sdp.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">&#8230;<o:p></o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<pre><o:p>&nbsp;</o:p></pre>
<pre>The INFO response is often sent by the SIP stack, before the Info Pack=
age<o:p></o:p></pre>
<pre>content has been handed to the application, and as long as the SIP sta=
ck<o:p></o:p></pre>
<pre>supports the Info Package as such, a 200 OK will be sent. If there is =
some<o:p></o:p></pre>
<pre>errors on the application level it needs to be dealt with some other w=
ay.<o:p></o:p></pre>
<pre>Please see section 4.2.2 of RFC 6086.<o:p></o:p></pre>
</blockquote>
<p class=3D"MsoNormal">My interpretation of that section is that you MAY se=
nd an error since the INFO request from above&nbsp; is not syntactically co=
rrect. However, 200OK and dealing with content on application level would a=
lso be fine. I don't think that this document
 needs to say anything beyond RFC6086. Regards Thomas <span style=3D"color:=
windowtext">
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:windowtext"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">The SIP stack MAY of course understand th=
e content, but the whole idea of sending application layer data with INFO i=
s that the SIP stack does NOT need to know anything
 about the semantics and syntax of that application layer data (the data co=
uld even be encrypted with a key that the SIP stack does not have access to=
o, or encoded with some algorithm the SIP stack does not understand). So, y=
ou cannot make an assumption that
 the SIP stack will detect an error and send a non-200 response. The assump=
tion has to be that, if the usage of the Info Package as such has been nego=
tiated for the session, the sender will receive a 200 OK no matter if the a=
pplication layer data is correct
 or not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,sans-serif;color:red">Christer<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B37FDDB5BESESSMB209erics_--


From nobody Sat May 21 01:38:04 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5516E12D09F for <mmusic@ietfa.amsl.com>; Sat, 21 May 2016 01:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXpQj5-2_GMZ for <mmusic@ietfa.amsl.com>; Sat, 21 May 2016 01:38:02 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41F7B12B074 for <mmusic@ietf.org>; Sat, 21 May 2016 01:38:01 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-e2-57401e664c7b
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.183.30]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 51.FF.18043.66E10475; Sat, 21 May 2016 10:37:59 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0294.000; Sat, 21 May 2016 10:37:06 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
Thread-Index: AdGwabgBtqwcvvDHTH642HSrSfG9xf//5BIAgAAP3YD//9yZwIAAJ06A///RITCAAuu6AIAAAEIA//9+FNAATKYIAP/+9Rig
Date: Sat, 21 May 2016 08:37:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FDDC67@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FCFA84@ESESSMB209.ericsson.se> <CAD5OKxutPPqUjXFLJnERj1xxx0H_hVwP86u_mLiUN0NYVN5GPg@mail.gmail.com> <CABkgnnW4Wo9gQKjr4qXpoTGNun9G7t2ez_4K3j4OEiEpNG7CQA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFBA0@ESESSMB209.ericsson.se> <CAD5OKxuq_14xcX2559sgig50HJ-5sF87dM6_YRd7=KFU-htNLg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FCFD04@ESESSMB209.ericsson.se> <CABkgnnXc_c_Wu8V0HX9Kt4+GEuSSK8noyKkTS+gNEbNBs_0GQQ@mail.gmail.com> <CABkgnnXjoY4urEcmGBiZMJ3vMxqkqjRkUNS_ezHg1_1uWVfysA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FD995A@ESESSMB209.ericsson.se> <CABkgnnV9nouafVaOZjnUah8M+iVqw1T26Mstd9spWnrBTNb7kw@mail.gmail.com>
In-Reply-To: <CABkgnnV9nouafVaOZjnUah8M+iVqw1T26Mstd9spWnrBTNb7kw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUyM2K7nG66nEO4Qe82DotrZ/4xWkxd/pjF YsWGA6wWMy5MZXZg8fj7/gOTx85Zd9k9liz5yeRxa0pBAEsUl01Kak5mWWqRvl0CV8akE/+Z CxokKr6t+8bawLhBvIuRg0NCwERi3a2iLkZOIFNM4sK99WxdjFwcQgJHGCW2zXrFCOEsYZRo anzJDtLAJmAh0f1PG6RBREBXYtHZB+wgNrNAkUTTgs0sICXCArkS2zb6QpTkSVyY85QZxl54 cDEriM0ioCpx/sU8RhCbV8BXYs2BbewQqw6zSqw7eRKsgVMgUGLL53tgDYxAx30/tYYJYpe4 xK0n85kgjhaQWLLnPDOELSrx8vE/VghbSWLt4e1g9zALaEqs36UP0aooMaX7ITvEXkGJkzOf sExgFJuFZOoshI5ZSDpmIelYwMiyilG0OLW4ODfdyEgvtSgzubg4P08vL7VkEyMwvg5u+W21 g/Hgc8dDjAIcjEo8vAvy7cKFWBPLiitzDzFKcDArifDa8DmEC/GmJFZWpRblxxeV5qQWH2KU 5mBREuf1f6kYLiSQnliSmp2aWpBaBJNl4uCUamBMd/fO6+E0eTBL4r6QwB2BL5qvrvxNjp64 sjs1fVrND04Xd9mZk1Yu3n3js9Z972cOV76kzFyYvXDfBknOGxZ71suGs0z6+nLb3DPnC25G 9q/4/SZEl6fMgbE+WHc3e/aa9M9zvGX0VyRH/tB9aNsT7slwWmXGvpIvh2v7i7aorPSzvuh1 as0CJZbijERDLeai4kQA4SkgEKsCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-KTFsNG61djaHSRSMMKKvfa__V4>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-01 - Light at the end of the tunnel?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 08:38:03 -0000

SGkgTWFydGluLA0KDQpUaGFua3MgZm9yIHlvdXIgY29tbWVudHMhIEknbGwgbW9kaWZ5IHRoZSB0
ZXh0IGFzICBzdWdnZXN0ZWQsIHdpdGggYSBjb3VwbGUgb2YgcmVhbGx5IG1pbm9yIG1vZGlmaWNh
dGlvbnMgKHNlZSBiZWxvdykuDQoNCj5OaXRzIGFuZCBncmFtbWFyIHN1Z2dlc3Rpb25zIGZvbGxv
dzoNCj4NCj4gICAgIE11bHRpcGxlIFNEUCBmaW5nZXJwcmludCBhdHRyaWJ1dGVzIGNhbiBiZSBh
c3NvY2lhdGVkIHdpdGggYW4gbS0NCj4gICAgIGxpbmUuIFRoaXMgY2FuIG9jY3VyIGlmIG11bHRp
cGxlIGZpbmdlcnByaW50cyBoYXZlIGJlZW4gY2FsY3VsYXRlZA0KPiAgICAgZm9yIGEgY2VydGlm
aWNhdGUsIHVzaW5nIGRpZmZlcmVudCBoYXNoIGZ1bmN0aW9ucy4gSXQgY2FuIGFsc28NCj4NCj4g
RHJvcCB0aGUgY29tbWENCj4NCj4gICAgIG9jY3VyIGlmIG9uZSBvciBtb3JlIGZpbmdlcnByaW50
cyBhc3NvY2lhdGVkIHdpdGggbXVsdGlwbGUNCj4gICAgIGNlcnRpZmljYXRlcyBoYXZlIGJlZW4g
Y2FsY3VsYXRlZCwgZS5nLiBmb3IgY2FzZXMgd2hlcmUgbXVsdGlwbGUNCj4gICAgIGNlcnRpZmlj
YXRlcyB3aWxsIGJlIHVzZWQgZm9yIG1lZGlhIGFzc29jaWF0ZWQgd2l0aCBhbiBtLSBsaW5lDQo+
ICAgICAoZS5nLiBzZXBhcmF0ZSBjZXJ0aWZpY2F0ZXMgZm9yIFJUUCBhbmQgUlRDUCksIG9yIHdo
ZXJlIGl0IGlzIG5vdA0KPg0KPiBZb3UgaGF2ZSB0d28gbmVzdGVkICJlLmcuIiBzdGF0ZW1lbnRz
LiAgSSB3b3VsZCBzcGxpdCB0aGUgZmlyc3QgZS5nLg0KPiBpbnRvIGEgbmV3IHNlbnRlbmNlIHN0
YXJ0aW5nOiBUaGlzIG1pZ2h0IGJlIG5lZWRlZCBpZiBtdWx0aXBsZSBjZXJ0aWZpY2F0ZXMuLi4N
Cg0KRml4ZWQgYXMgc3VnZ2VzdGVkLCBhbmQgSSBtb2RpZmllZCB0aGUgcmVtYWluaW5nICJlLmcu
IiBzdGF0ZW1lbnQgdG86DQoNCgkiKGUuZy4gaWYgc2VwYXJhdGUgY2VydGlmaWNhdGVzIGFyZSB1
c2VkIGZvciBSVFAgYW5kIFJUQ1ApIg0KDQoNCj4gICAgIGtub3duIHdoaWNoIGNlcnRpZmljYXRl
IHdpbGwgYmUgdXNlZCB3aGVuIHRoZSBmaW5nZXJwcmludHMgYXJlDQo+ICAgICBleGNoYW5nZWQu
IEluIHN1Y2ggY2FzZXMsIG9uZSBvciBtb3JlIGZpbmdlcnByaW50cyBNVVNUIGJlDQo+ICAgICBj
YWxjdWxhdGVkIGZvciBlYWNoIHBvc3NpYmxlIGNlcnRpZmljYXRlLg0KPg0KPiAgICAgSWYgZmlu
Z2VycHJpbnRzIGFzc29jaWF0ZWQgd2l0aCBtdWx0aXBsZSBjZXJ0aWZpY2F0ZXMgYXJlDQo+ICAg
ICBjYWxjdWxhdGVkLCB0aGUgc2FtZSBzZXQgb2YgZmluZ2VycHJpbnRzICh1c2luZyB0aGUgc2Ft
ZSBoYXNoDQo+ICAgICBmdW5jdGlvbnMpIE1VU1QgYmUgY2FsY3VsYXRlZCBmb3IgZWFjaCBjZXJ0
aWZpY2F0ZSBhc3NvY2lhdGVkDQo+DQo+ICJ0aGUgc2FtZSBzZXQgb2YgaGFzaCBmdW5jdGlvbnMg
TVVTVCBiZSB1c2VkIHRvIGNhbGN1bGF0ZSBmaW5nZXJwcmludHMgZm9yIGV2ZXJ5IGNlcnRpZmlj
YXRlIGFzc29jaWF0ZWQiDQoNCkZpeGVkIGFzIHN1Z2dlc3RlZCwgYnV0IEkgdXNlZCAiZWFjaCBj
ZXJ0aWZpY2F0ZSIgaW5zdGVhZCBvZiAiZXZlcnkgY2VydGlmaWNhdGUiLCBpbiBvcmRlciB0byBi
ZSBjb25zaXN0ZW50IHdpdGggdGhlIHJlc3Qgb2YgdGhlIHRleHQuDQoNCj4gICAgIHdpdGggdGhl
IG0tIGxpbmUuDQo+DQo+ICAgICBGb3IgZWFjaCB1c2VkIGNlcnRpZmljYXRlLCBhbiBlbmRwb2lu
dCBNVVNUIGJlIGFibGUgdG8gbWF0Y2ggYXQNCj4gICAgIGxlYXN0IG9uZSBmaW5nZXJwcmludCwg
Y2FsY3VsYXRlZCB1c2luZyB0aGUgaGFzaCBmdW5jdGlvbiB0aGF0IHRoZQ0KPiAgICAgZW5kcG9p
bnQgc3VwcG9ydHMgYW5kIGNvbnNpZGVycyBtb3N0IHNlY3VyZSwgd2l0aCB0aGUgdXNlZA0KPiAg
ICAgY2VydGlmaWNhdGUuIElmIHRoZXJlIGlzIG5vIG1hdGNoLCB0aGUgZW5kcG9pbnQgTVVTVCBO
T1QgZXN0YWJsaXNoDQo+ICAgICB0aGUgVExTIGNvbm5lY3Rpb24uIEluIGFkZGl0aW9uLCB0aGUg
ZW5kcG9pbnQgTUFZIGFsc28gY2hlY2sgb3RoZXINCj4gICAgIGZpbmdlcnByaW50cyAoY2FsY3Vs
YXRlZCB1c2luZyBvdGhlciBoYXNoIGZ1bmN0aW9ucykgdGhhdCBpdCBoYXMNCj4NCj4gIk1BWSBh
bHNvIGNoZWNrIGZpbmdlcnByaW50cyBjYWxjdWxhdGVkIHVzaW5nIG90aGVyIGhhc2ggZnVuY3Rp
b25zIHRoYXQgaXQgaGFzIg0KDQpGaXhlZCBhcyBzdWdnZXN0ZWQuDQoNClRoYW5rcyENCg0KUmVn
YXJkcywNCg0KQ2hyaXN0ZXINCg==


From nobody Sat May 21 01:48:54 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C62512B074; Sat, 21 May 2016 01:48:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160521084851.18733.97855.idtracker@ietfa.amsl.com>
Date: Sat, 21 May 2016 01:48:51 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/84fcppgZloc_nhZTxZL0ktCmH2g>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-4572-update-03.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 08:48:51 -0000

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

        Title           : Updates to RFC 4572
        Author          : Christer Holmberg
	Filename        : draft-ietf-mmusic-4572-update-03.txt
	Pages           : 7
	Date            : 2016-05-21

Abstract:
   This document updates RFC 4572 by clarifying the usage of multiple
   SDP 'fingerprint' attributes with a single TLS connection.  The
   document also updates the preferred cipher suite to be used, and
   removes the requirement to use the same hash function for calculating
   a certificate fingerprint that is used to calculate the certificate
   signature.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-mmusic-4572-update-03

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


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

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


From nobody Sat May 21 01:52:57 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 507A212B022; Sat, 21 May 2016 01:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 hiSfeS-fm2l5; Sat, 21 May 2016 01:52:54 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97A7C12B00F; Sat, 21 May 2016 01:52:53 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-90-574021e395db
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 57.21.18043.3E120475; Sat, 21 May 2016 10:52:51 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0294.000; Sat, 21 May 2016 10:52:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-4572-update-03
Thread-Index: AdGzPdL2/31UCUDlSbGj3bAwQwSjQQ==
Date: Sat, 21 May 2016 08:52:50 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FDDD0A@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FDDD0AESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZGbHdWPexokO4wbT5ehbnd65nspi6/DGL A5PHkiU/mQIYo7hsUlJzMstSi/TtErgyev98YyzYK15xfNJl9gbGPyJdjJwcEgImEnsmNTND 2GISF+6tZ+ti5OIQEjjCKNExZRsbSEJIYAmjRNuF6C5GDg42AQuJ7n/aIGERAXWJr3t7wHqZ BUwlHr5awwhiCwvYSEw5084GUeMosWziV1YIW0/i9N6Z7CA2i4CqxM2uNywgNq+Ar8TlO8/A 5jAC3fD91BomiJniEreezGeCuE1AYsme81B3ikq8fPyPFcJWklh7eDsLRH2+xORr51khZgpK nJz5hGUCo/AsJKNmISmbhaQMIq4jsWD3JzYIW1ti2cLXzDD2mQOPmZDFFzCyr2IULU4tLs5N NzLSSy3KTC4uzs/Ty0st2cQIjJmDW35b7WA8+NzxEKMAB6MSD++CfLtwIdbEsuLK3EOMEhzM SiK8NnwO4UK8KYmVValF+fFFpTmpxYcYpTlYlMR5/V8qhgsJpCeWpGanphakFsFkmTg4pRoY c/uvzNeWDGdVm7hn34x/d31OqBh5Tup+/eqt/w5mlQip+Lv7/u82+rgqTSj+suSnLROPOnCk MK9slOg1OPr3kqaY8ZpyvlxG3nVCIufOqTi9Sxc2WhxT9U1SXTe53K9fbU/1/PTyjKefVtoH aiTIe/QerSn4yWqpuan0oJz/Ko5HXR9m/z6vxFKckWioxVxUnAgAU7g0/pUCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/6-nCJyEqt93tTUKNddjLoa9WvzU>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 08:52:55 -0000

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

Hi,

Based on Martin's editorial comments, I've submitted a new version (-03) of=
 draft-ietf-mmusic-4572-update.

Also on GitHub: https://github.com/cdh4u/draft-4572-update (personal repo)

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37FDDD0AESESSMB209erics_
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">Based on Martin&#8217;s editorial comments, I&#8217;=
ve submitted a new version (-03) of draft-ietf-mmusic-4572-update.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Also on GitHub: <a href=3D"https://github.com/cdh4u/=
draft-4572-update">
https://github.com/cdh4u/draft-4572-update</a> (personal repo)<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_7594FB04B1934943A5C02806D1A2204B37FDDD0AESESSMB209erics_--


From nobody Sat May 21 08:58:11 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD5B912B059; Sat, 21 May 2016 08:58:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160521155810.18756.1332.idtracker@ietfa.amsl.com>
Date: Sat, 21 May 2016 08:58:10 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/qxa93eIlgH9UC1283x0Qwy4oPBM>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-dtls-sdp-12.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 15:58:11 -0000

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

        Title           : Using the SDP Offer/Answer Mechanism for DTLS
        Authors         : Christer Holmberg
                          Roman Shpount
	Filename        : draft-ietf-mmusic-dtls-sdp-12.txt
	Pages           : 24
	Date            : 2016-05-21

Abstract:
   This draft defines the SDP offer/answer procedures for negotiating
   and establishing a DTLS association.  The draft also defines the
   criteria for when a new DTLS association must be established.

   This draft defines a new SDP media-level attribute, 'dtls-id'.


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

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

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


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

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


From nobody Sat May 21 09:03:52 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B9B12B018; Sat, 21 May 2016 09:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ogv99g1fpq2e; Sat, 21 May 2016 09:03:50 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 577B2128E19; Sat, 21 May 2016 09:03:49 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-77-574086c8b001
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 13.34.18043.8C680475; Sat, 21 May 2016 18:03:20 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0248.002; Sat, 21 May 2016 18:02:52 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-dtls-sdp-12
Thread-Index: AdGzeadT9Biiw5sKQwmLHX/vhwcvDQ==
Date: Sat, 21 May 2016 16:02:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FDE36BESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpikeLIzCtJLcpLzFFi42KZGbHdW/dEm0O4QeMmA4vzO9czWUxd/pjF gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZDb2PWQuuSldsutvO3MB4VqKLkZNDQsBEYt3848wQ tpjEhXvr2boYuTiEBI4wSjy7/R4sISSwhFHi1QSTLkYODjYBC4nuf9ogYREBdYmve3vASpgF TCUevlrDCGILC1hKfPqzjQ2ixk7i8+mJTBC2nsTP6VtYQWwWAVWJYy8PgNm8Ar4SM+4+AZvD CHTD91NrmCBmikvcejKfCeI2AYkle85D3Skq8fLxP1YIW0li7eHtLBD1+RJ7511kh5gpKHFy 5hOWCYzCs5CMmoWkbBaSMoi4jsSC3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KUbQ4tbg4N93I SC+1KDO5uDg/Ty8vtWQTIzBmDm75bbWD8eBzx0OMAhyMSjy8DzMdwoVYE8uKK3MPMUpwMCuJ 8OrUA4V4UxIrq1KL8uOLSnNSiw8xSnOwKInz+r9UDBcSSE8sSc1OTS1ILYLJMnFwSjUwKjes cHh/3vbFs63bBI/NY39YdF9E9pe9n5lQzjUdbV29Gp711d1fMjby+Qmx7do/T5Kf97J2CNfx 8K9+XFu/zFRcp57+P/yf4Zn/DiKOWoI6aXk7e1Yt43LOD/y6pdRB+XRw4YPZF1+ezeAtssvc 83dt7dEN8TeOdy1YF1G867jYRZWFoVs5lViKMxINtZiLihMBAxA4dpUCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/82Pb2Ty_VyPwMBH9OlPl5Kc7Fdw>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 May 2016 16:03:51 -0000

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

Hi,

I've submitted a new version (-12) of draft-ietf-mmusic-dtls-sdp.

The new version contains some additional restrictions regarding the establi=
shment of a new DTLS association.

Also, as message size again seems to matter, I've changed the name of the a=
ttribute from 'dtls-association-id' to 'dtls-id'.

GitHub: https://github.com/cdh4u/draft-dtls-sdp (individual repo)

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37FDE36BESESSMB209erics_
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">I&#8217;ve submitted a new version (-12) of draft-ie=
tf-mmusic-dtls-sdp.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The new version contains some additional restriction=
s regarding the establishment of a new DTLS association.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Also, as message size again seems to matter, I&#8217=
;ve changed the name of the attribute from &#8216;dtls-association-id&#8217=
; to &#8216;dtls-id&#8217;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">GitHub: <a href=3D"https://github.com/cdh4u/draft-dt=
ls-sdp">https://github.com/cdh4u/draft-dtls-sdp</a> (individual repo)<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_7594FB04B1934943A5C02806D1A2204B37FDE36BESESSMB209erics_--


From nobody Mon May 23 12:46:16 2016
Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE0412D526; Mon, 23 May 2016 12:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eaof0vQBbv4U; Mon, 23 May 2016 12:46:13 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A2BF12D14E; Mon, 23 May 2016 12:46:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=432; q=dns/txt; s=iport; t=1464032773; x=1465242373; h=to:cc:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=BWAY0oy1q71viH1E1wcmrfQS2KDehevxh+n+wQvDvUw=; b=Wal+r1rXqmmM4kWHI4aGJFFCI2ZrSmqt/RfpICdrxoQj94H6YRKh49Iv FfQEI239hyopddblTyrqTl8ikTwFUJ8sktm+A+7MRYdrTmc7iSQ/zCpH5 zkvSY08i7QfOQjXT3I1e7PmpRLMqWF9M/kcFAYl4n5ZpkdGGohPdm4L4v E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D1AwChXENX/5xdJa1cgzeBAbM4hDpSg?= =?us-ascii?q?g8BDYF3hhGBODgUAQEBAQEBAWUnhGwVQTUCJgJfDQgBAYgrslmRSAEBAQEBAQQ?= =?us-ascii?q?BAQEBASKBAYUmgXaKF4JZAQSYN4p4gyiBUwEVhE+DCYRAgRuGM4kZHgEBQoQJI?= =?us-ascii?q?IoDAQEB?=
X-IronPort-AV: E=Sophos;i="5.26,357,1459814400"; d="scan'208";a="110966009"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 May 2016 19:46:12 +0000
Received: from [10.98.149.203] (bxb-fandreas-88110.cisco.com [10.98.149.203]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u4NJkCZF001622; Mon, 23 May 2016 19:46:12 GMT
To: mmusic <mmusic@ietf.org>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com>
Date: Mon, 23 May 2016 15:46:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/tCBHXWSNEc5esnpCs_KPS-wd7is>
Cc: draft-ietf-mmusic-4572-update@ietf.org
Subject: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 19:46:14 -0000

Greetings

This is to announce a 2 week WGLC for

     draft-ietf-mmusic-4572-update-03

as Proposed Standard. Please review and provide any comments you may 
have on the document by Monday, June 6, 2016. Comments should be sent to 
the document authors and the MMUSIC WG list. If you review the document 
but do not have any comments, please send a note to that effect as well.

Thanks

-- Flemming (MMUSIC co-chair)


From nobody Mon May 23 13:25:00 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A84D12DB5C; Mon, 23 May 2016 13:24:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Atyo6KaoPs4b; Mon, 23 May 2016 13:24:57 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CCD912DB7C; Mon, 23 May 2016 13:24:56 -0700 (PDT)
Received: by mail-ig0-x231.google.com with SMTP id bi2so40574856igb.0; Mon, 23 May 2016 13:24:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=1fEDPxeLuxarZtmctH+2gNHUem++Tqg9PAgkqP6HzWo=; b=ueGMciVlPTKr/7iOYjvYkFB2vCeZg6JQ2RSN7f5zzzrt9tVmx7qbNIDoyiYmsY+00Q v/GDu3f0LsZriJ2qXVisEVTQzbEECtztzerYBKa0l0MlXcq96eKfjs2QbDVPGnmA/UBV E6dUYgEQ7qrYiKsdU9i9JCWSQDO/F7TrKfbQBPUK2UEh/bE6vgWueoSO5IKwiGANYl2Q H+GLso/cwpCj3LvsZ8fUoDDwxcwav4hXZuDVPqr0fuPKO3tOQP7D+0pNOoYh060s71Vi 6cL40bRmqXxf+xYIGPYngT5qzZLvMjWUq3NTfAh6PhCfRLYzyTMFyH+rYyf60wVQNeZE hUVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=1fEDPxeLuxarZtmctH+2gNHUem++Tqg9PAgkqP6HzWo=; b=cM8hTntIiMLxeeR1W2vyLW8Cmc7HtR1d5ZDBHsbQBhKRX7XEbQ2SRpLXiZtT+H+4oV LSeSkvxcEE8tnsLNWfqaAsADUU+Z8RFPxWICWds2jbmHKiK6vv5rnNjW7fjzuCqE5Ke8 y6BKOA0+8AVZyH2haRHIp31uK30eYfS4yfJZjx1sadsw8oEmzL5j3TTanc758sZxRVLB hJrTLBmYzwE8dxkAcIujAlpFSHwM2nUiVxXfdXPm2aFu6sxJbYUprdCCO4v6zBcgReJ4 0w1r147m6PqD/X5zlMRnwlMgtJdDOxofHdHZnAB8kRdQ6t137jrAF1JECucTivZKakbc ngpQ==
X-Gm-Message-State: AOPr4FUBXgEEtU/J/kQJ/aMxuwv+eNVCmc5qIkV6ze0XXOf6wqBaaK277j4WlB1qP+fELTaPs6bZIqO+ZaNA3Q==
MIME-Version: 1.0
X-Received: by 10.50.33.81 with SMTP id p17mr14715472igi.58.1464035095987; Mon, 23 May 2016 13:24:55 -0700 (PDT)
Received: by 10.36.43.23 with HTTP; Mon, 23 May 2016 13:24:55 -0700 (PDT)
In-Reply-To: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com>
Date: Mon, 23 May 2016 16:24:55 -0400
Message-ID: <CABkgnnVzmKWyB-wEuRGO1RFscUtu3UL8dh+16FH0UsF6tT=5ZQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Flemming Andreasen <fandreas@cisco.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/mZgXWKLgF5SReMa8FRWkC4-YmPM>
Cc: draft-ietf-mmusic-4572-update@ietf.org, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 20:24:58 -0000

On 23 May 2016 at 15:46, Flemming Andreasen <fandreas@cisco.com> wrote:
> This is to announce a 2 week WGLC for
>
>     draft-ietf-mmusic-4572-update-03

LGTM


From nobody Mon May 23 13:35:26 2016
Return-Path: <prvs=99519686b6=jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B5112D16D; Mon, 23 May 2016 13:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.831
X-Spam-Level: 
X-Spam-Status: No, score=-1.831 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=0.77, 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 T7wPyo0qPnZd; Mon, 23 May 2016 13:35:23 -0700 (PDT)
Received: from mx0a-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.202]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7495D12D572; Mon, 23 May 2016 13:35:21 -0700 (PDT)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u4NKP4Ne026387; Mon, 23 May 2016 16:35:20 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 232hrg19eb-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 23 May 2016 16:35:20 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Mon, 23 May 2016 15:35:19 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtTIaQis2k/N4/0eW1holrCy8CJ/HTqoA
Date: Mon, 23 May 2016 20:35:19 +0000
Message-ID: <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com>
In-Reply-To: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <142B7ACF0B21A442AABCC7078A50A207@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-05-23_08:2016-05-23,2016-05-23,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1605230244
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/PTSbH6qwMtLmideJQ5wq9DsXf38>
Cc: "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 20:35:25 -0000

DQo+IE9uIE1heSAyMywgMjAxNiwgYXQgMzo0NiBQTSwgRmxlbW1pbmcgQW5kcmVhc2VuIDxmYW5k
cmVhc0BjaXNjby5jb20+IHdyb3RlOg0KPiANCj4gR3JlZXRpbmdzDQo+IA0KPiBUaGlzIGlzIHRv
IGFubm91bmNlIGEgMiB3ZWVrIFdHTEMgZm9yDQo+IA0KPiAgICBkcmFmdC1pZXRmLW1tdXNpYy00
NTcyLXVwZGF0ZS0wMw0KPiANCj4gYXMgUHJvcG9zZWQgU3RhbmRhcmQuIFBsZWFzZSByZXZpZXcg
YW5kIHByb3ZpZGUgYW55IGNvbW1lbnRzIHlvdSBtYXkgaGF2ZSBvbiB0aGUgZG9jdW1lbnQgYnkg
TW9uZGF5LCBKdW5lIDYsIDIwMTYuIENvbW1lbnRzIHNob3VsZCBiZSBzZW50IHRvIHRoZSBkb2N1
bWVudCBhdXRob3JzIGFuZCB0aGUgTU1VU0lDIFdHIGxpc3QuIElmIHlvdSByZXZpZXcgdGhlIGRv
Y3VtZW50IGJ1dCBkbyBub3QgaGF2ZSBhbnkgY29tbWVudHMsIHBsZWFzZSBzZW5kIGEgbm90ZSB0
byB0aGF0IGVmZmVjdCBhcyB3ZWxsLg0KPiANCj4gVGhhbmtzDQo+IA0KPiAtLSBGbGVtbWluZyAo
TU1VU0lDIGNvLWNoYWlyKQ0KDQo0NTcyIGZvcmJpZCB0aGUgdXNlIG9mIE1ENSBhbmQgTUQyIGlu
IGFsbW9zdCBhbGwgY2lyY3Vtc3RhbmNlcywgYnkgZm9yYmlkZGluZyB0aGVpciB1c2UgaW4gc2Vs
Zi1zaWduZWQgY2VydHMuICBCeSByZW1vdmluZyB0aGUgdGllIGJldHdlZW4gdGhlIGNlcnRpZmlj
YXRlIGhhc2ggYWxnb3JpdGhtIGFuZCB0aGUgZmluZ2VycHJpbnQgYWxnb3JpdGhtLCB3ZeKAmXZl
IGxvc3QgdGhpcyByZXF1aXJlbWVudC4gIFNob3VsZCB3ZSByZS1hZGQgaXQ/DQoNClNIQS0yNTYg
aXMgb25seSDigJxwcmVmZXJyZWTigJ0uICBEbyB3ZSB3YW50IHRvIG1ha2UgaXRzIGluY2x1c2lv
biBtYW5kYXRvcnksIG5vdyB0aGF0IHdlIHN1cHBvcnQgbXVsdGlwbGUgYWxnb3JpdGhtcz8=


From nobody Mon May 23 15:34:18 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62C9F12D5D0; Mon, 23 May 2016 15:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 aE-ZQj8DdFcc; Mon, 23 May 2016 15:34:14 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2F8912B008; Mon, 23 May 2016 15:34:13 -0700 (PDT)
Received: from [10.0.1.18] (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 u4NMYBF9029449 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 23 May 2016 17:34:11 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.18]
From: "Ben Campbell" <ben@nostrum.com>
To: "Suhas Nandakumar" <suhasietf@gmail.com>
Date: Mon, 23 May 2016 17:34:12 -0500
Message-ID: <ED0991AE-DF16-4D42-9130-A2B42C4677A1@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/cqp1AR-QlC4HxPbyWEDUXEsymW0>
Cc: mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Subject: [MMUSIC] zrtp-hash (was Re: AD Evaluation of draft-ietf-mmusic-sdp-mux-attributes-12)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 22:34:16 -0000

Hi,

As promised, here's more on my concern about zrtp-hash in =

draft-ietf-mmusic-sdp-mux-attributes:

I think you need to describe the assumptions about what it means to =

multiplex zrtp. Am I correct to assume that the draft assumes that there =

is only one zrtp session in a transport flow, with a single zrtp =

handshake? And that all of the bundled m=3Dlines represent media that is =

part of that zrtp association? (That is, you never mux distinct zrtp =

associations, or zrtp and dtls-srtp?)

If the answer is yes, then "transport" seems to make sense.

But is zrtp demuxing really well defined enough to keep this out of the =

"NOT RECOMMENDED" category? I'm not sure it meets the bundle requirement =

for a public spec on how to demux it. One might infer that from two =

public specs (zrtp and 5764), but IIUC, the guidance proposed in =

draft-ietf-avtcore-rfc5764-mux-fixes would cause a zrtp messages to be =

dropped, since its first byte would not match any of the demux rules. =

Or, if zrtp-hash is allowed, does mux-fixes need to change?

What am I missing?

Thanks!

Ben.


On 20 May 2016, at 18:07, Ben Campbell wrote:

> Apologies for my slow response. The last month has been a perfect =

> storm of productivity killers. I'm digging out of the backlog now. =

> Comments inline, with sections that appear resolved removed.
>
> There is one issue (zrtp-hash) where I will start a separate thread =

> shortly.
>
> Thanks!
>
> Ben.
>
> On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:
>
>> Hello Ben
>>
>>  Sorry for the delay in responding. Many thanks for the detailed =

>> review.
>>
>>  Please find my responses inline (marked by [Suhas]).
>>
>> Cheers
>> Suhas
>>
>> On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell <ben@nostrum.com> =

>> wrote:
>>
>>> Hi,
>>>
>>> Here is my AD evaluation of draft-ietf-mmusic-sdp-mux-attributes-12. =

>>> I
>>> would like at least the substantive
>>> section to be discussed before going to IETF last call.
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>> ----------
>>>
>>> # Substantive #
>>>
>>> - This is very long and detailed. Are the authors and chairs =

>>> comfortable
>>> that all sections have had sufficient review?
>>>
>>> -4.0: It would be helpful to add a paragraph describing how these =

>>> semantic
>>> groupings map to the categories.
>>>
>>
>> [Suhas] The semantic groupings were added as a informal reference and =

>> they
>> don't really interact with the categories as such.
>
> So I have to wonder why we have the groupings. But I guess at this =

> point in the process, it's not worth changing that.
>
>>
>> Does the following rephrasing work
>>
>> *"Attributes in an SDP session description can be defined at the
>> **session-level
>> or  media-level or  source-level. Informally, there are various =

>> semantic
>> grouping for these attributes. One such grouping could be as noted =

>> below:*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *   o  Attributes related to media content such as media type, =

>> encoding
>>      schemes, payload types.   o  Attributes specifying media =

>> transport
>> characteristics like RTP/RTP      Control Protocol (RTCP) port =

>> numbers,
>> network addresses, QOS.   o  Metadata description attributes =

>> capturing
>> session timing and      origin information.   o  Attributes =

>> establishing
>> relationships between media descriptions      such as grouping =

>> framework
>> [RFC5888 <https://tools.ietf.org/html/rfc5888>]The proposed framework
>> defines categories for the SDP attributes under multiplexing and =

>> assigns
>> each SDP attribute to an appropriate multiplexing category.*
>>
>> *Since the multiplexing categories defined in this specification are
>> independent of any informal semantic grouping of the SDP attributes, =

>> the
>> categorizations assigned against each attribute  MUST be considered =

>> as
>> normative assignments under multiplexing. "*
>
> All fine, except the last sentence is pretty meta--it uses normative =

> language to talk about normative language ("MUST be considered =

> normative"). I'm not entirely sure what you intend there, but how =

> about something to the effect of "... the categorizations assigned =

> against each attribute are normative."
>
>>
>>
>>
>>> -4.2: I recommend choosing a category name that is not a 2119 =

>>> keyword.
>>>   Maybe something like "not mux-able" or "unsafe"?
>>>
>>
>> [Suhas]
>>
>> Initially that category was called "BAD" as in
>>
>> https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux-attri=
butes/01/
>>
>> However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D was =
a bad =

>> choice :-)
>>
>> Either of the following options seems fine to me
>>
>>    1.
>>
>>    NOT-RECOMMENDED [ we use hyphen separated multi word format in =

>> other
>>    category names]
>>    2. UNSAFE
>
> I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you intend =

> the category name to mean "NOT RECOMMENDED" in the 2119 sense.
>
>>
>>
>>
>>
>>>
>>> -4.3: Please don't use a 2119 keyword as part of the definition
>>> of a category. This creates sort of a circular dependency; that is
>>> attributes are in this category because they MUST be identical; but =

>>> they
>>> MUST be identical because they are in this category. I suggest =

>>> describing
>>> the category descriptively, and adding a separate sentence to say
>>> "Attributes
>>> in the IDENTICAL category MUST be identical across all media =

>>> descriptions."
>>>
>>
>>
>> [Suhas]. I have removed the usage of word identical from the =

>> definition as
>> below. Please let me know if this works.
>>
>>
>> Category: IDENTICAL
>>
>> Attributes  and their associated values (if present) in the IDENTICAL
>> category MUST be repeated across all the media descriptions under
>> multiplexing.
>>
>
> Okay.
>
> [...]
>
>>
>>
>>
>>> -5.8 and 5.9:
>>>     The last paragraph of 5.8 seems redundant with section 5.9.
>>>
>>> -5.8, last paragraph:
>>>
>>>     "Hence multiplexing MUST NOT be performed even in this
>>>     alternate scenario." seems to contradict the category selection =

>>> of
>>>     "NOT RECOMMENDED" (but see previous comment about not using 2119
>>>     keywords in a category title.)
>>>
>>>
>> [Suhas] The idea here is to not perform multiplexing and hence the =

>> category
>> of NOT RECOMMENDED assigned. I can update this once we finalize on =

>> the
>> right naming for "NOT RECOMMENDED"
>
> This argues for the "UNSAFE" name, since the actual normative guidance =

> is stronger than "NOT RECOMMENDED". (Unless you want a "MUST NOT" name =

> :-)  )
>
>>
>>
>>
>>> -5.24, last paragraph: "it is recommended to consult the
>>>   document defining the attribute."
>>>
>>>   I assume one should _always_ refer to the specification of
>>>   an SDP attribute before trying to mux it. But that doc is
>>>   not going to explain muxing issues, is it?
>>>
>>>
>> [Suhas]
>>
>> Since cparmin/cparmax can define numerical values/ranges
>>
>> for any of b=3D or a=3D attributes (identified via cpar), there is no =

>> easy way
>> to assign a multiplexing category unless one knows what cpar is being
>>
>> used and the assignned numerical values to each of cparmin/cparmax =

>> mean.
>> Thus the category SPECIAL has been assigned as a recommendation for =

>> the
>> implementor to consult the spec that defines a particular usage of =

>> cpar,
>> cparmin and cparmax combination to really see what=E2=80=99s going on.=

>>
>> This is very similar to extmap or RTCP Application feedback message =

>> type
>>
>> How about following rephrasing
>>
>>
>> *"The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and maxi=
mum
>> numerical values associated with the attributes described in a=3Dcpar.=
 =

>> Since
>> a cpar attribute can either define*
>>
>> *=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attrib=
ute,  the multiplexing =

>> category *
>>
>> *depends on actual attribute being encapsulated and the implications =

>> of the
>> numerical values assigned. Hence it is recommended to consult the
>> specification defining the the attributes (cparmin/cparmax) to =

>> further
>> analyze their behavior under multiplexing."*
>
> That works for me.
>
>>
>>
>>
>>> -5.26:
>>>   -"Support of this extension is OPTIONAL."
>>>   Please don't use 2119 keywords to describe existing requirements
>>>   from other docs, unless in direct quotes.
>>>
>>>
>>
>> [Suhas] This sentence is taken directly from RFC6714. (
>> https://tools.ietf.org/html/rfc6714)
>
> Sure, but it's not attributed as a quote. I suggest something to the =

> effect of "This is an optional extension according to [RFC6714]", " =

> [RFC6714] states that this extension is 'OPTIONAL'",  or even the =

> exact same language as currently in the draft, but without the =

> capitalized OPTIONAL.
>
> [...]
>
>>
>>
>>
>>> - 5.39:
>>>   I=E2=80=99m not a zrtp expert, but it seems like it might
>>>   be more complicated than this. Section 8 of 6189 says
>>>   =E2=80=9CThe a=3Dzrtp-hash attribute  can only be included in the
>>>   SDP at the media level since Hello messages sent in
>>>   different media streams will have unique hashes.=E2=80=9D
>>>   I wonder if this shouldn't be =E2=80=9Cidentical=E2=80=9D?
>>>
>>>
>> [Suhas] The category TRANSPORT is the appropriate assignment. This =

>> spec
>> assigns category for these attributes over the multiplexed transport.
>>
>> So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.
>>
>> The zrtp-hash selected must correspond to the m=3Dline that is selecte=
d =

>> for
>> BUNDLE once the O/A negotiation completes. Thus the category =

>> TRANSPORT.
>>
>>
>
> I _think_ you are right, but there may be an interaction here that can =

> break things I will think about that more, and respond to this issue =

> is a separate thread.
>
>>
>>
>>
>>>
>>> -5.45:
>>>   6193 is an ISE stream RFC. Does anyone actually use
>>>   in a context where muxing matters?
>>>
>>
>> [Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.
>
> That seems reasonable, unless  you know of good reasons otherwise.
>
>>>
>>> -15.1:
>>>   - Is there no need for a spec for any newly registered categories?
>>>   - 2nd to last paragraph: "This seems vague for a MUST. Do you =

>>> expect
>>>     the registration of a new category to change the categories
>>>     already assigned to existing SDP parameters? Is it possible
>>>     that a new category only applies to some new SDP parameters?"
>>>
>>
>> [Suhas] The following 2 paragraphs are supposed to mean that new
>> multiplexing categories require new registrations via a spec and
>> applicability of the new category to new SDP attributes and possibly
>> existing SDP attributes ( if the new category makes more sense). What =

>> would
>> be a better framing to capture the intent ?
>>
>> "*Further entries can be registered on a first-come first-serve =

>> basis. Each
>> registration needs to indicate the multiplexing category value to be =

>> added
>> to the "Multiplexing Categories" subregistry as defined in this =

>> section.*
>>
>> *Such a registration MUST also indicate the applicability of the =

>> newly
>> defined multiplexing category value to various subregistries defined =

>> at
>> "Session Description Protocol (SDP) Parameters".*
>
> That works for me.
>
>>
>>
>>>   - Last paragraph: 4566 procedures apply to what? The text just =

>>> said
>>>     new categories are first-come-first server. I don=E2=80=99t think=

>>>     4566 set policies for how to change mux categories.
>>>
>>
>> [Suhas] Agreed. I prefer removing this line altogether. Please let me =

>> know
>>
>
> I agree.
>
>>>
>>> -15.2.1:
>>>   How do you expect the table to look after adding this RFC to the
>>>   references? Will this RFC be added to the entries in the MUX
>>>   column?
>>>
>>
>> [Suhas] The plan was to add the reference to this RFC in the =

>> "Reference
>> Column"
>
> Okay.
>
> [...]
>
>
>>
>>>
>>>
>>> # Editorial #
>>>
>>
>>> - The abstract is more detailed than needed. The point is to =

>>> describe the
>>> purpose of the draft. The second paragraph pretty much accomplishes =

>>> that.
>>>
>>>
>> [Suhas] How do this rephrase look
>>
>> =E2=80=9CThe purpose of this specification is to provide a framework f=
or =

>> analyzing
>> the multiplexing characteristics of SDP attributes when SDP is used =

>> to
>> negotiate the usage of single 5-tuple for sending and receiving media
>> associated with multiple media descriptions,. This specification also
>> categorizes the existing SDP attributes based on the framework =

>> described
>> herein.=E2=80=9D
>>
>
> That works for me.
>
> [...]
>
>>
>>
>>>
>>> -5 and subsections: Is there any method to the ordering? They aren't
>>>    in RFC order. It might make sense to group by the nature of the
>>>    attributes, but if that is the case here it's not explained.
>>>
>>>
>> [Suhas] These are not ordered as of today. I can order the 5.X =

>> subsections
>> by RFC order, if needed.
>
> Unordered is also okay. I was just wondering if there was a logic that =

> should be mentioned.
>
>
> [...]
>
>>
>>
>>>
>>> -5.13, table:
>>>   "Specific RTP extension document MUST be referred"
>>>
>>>
>> [Suhas] The idea was to mean that , one should refer to the =

>> specification
>> that defines a specific RTP extension in order to understand the
>> multiplexing behavior.
>>
>> Would the following rephrasing help instead
>>
>> "Refer to the document defining specific RTP Extension"
>>
>>
>
> Yes, thanks.
>
>>
>>>   I don=E2=80=99t understand what that means. If you mean to
>>>    say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=E2=80=
=99t use MUST.
>>>
>>> -5.22, table: "document needs to be referred" (several repetitions)
>>>   I'm not sure what this means. Should it say "Refer to the
>>>   specific document"?
>>>
>>>
>> Similarly as above, would this reprhasing help
>>
>> "Refer to the document defining specific FEC Scheme
>>
>>
>
> Similarly as above, Yes, thanks. :-)
>
>>
>>>
>>> -6.3: "not clearly defined offer/answer usage"
>>>   I'm not sure what is meant here. (Also, why is this not TBD or NOT
>>>   RECOMMENDED?)
>>>
>>
>> [Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind, =

>> either the
>> BUNDLE spec or this spec cannot define its mux behavior. This is due =

>> to
>> applicability of these specs under SD{ O/A usages alone.
>>
>> I can rephrase the above as
>> "not defined under SDP Offer/Answer usage"
>
> WFM, thanks.
>
> [...]


From nobody Mon May 23 15:48:10 2016
Return-Path: <alan.b.johnston@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 37CBB12DBFC; Mon, 23 May 2016 15:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPP5i0lwBSRQ; Mon, 23 May 2016 15:48:08 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A204512DBF2; Mon, 23 May 2016 15:48:07 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id t145so27987993qke.2; Mon, 23 May 2016 15:48:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=anExuh2VOy470EdE/dhufHILJrRIwzzD50Y8DNx2onY=; b=U/gs0G+OXkvGCmSphyhkBOZykb5VGKVAeOAgleH1lPi8eshwQgLAMfHJS154ivLD/Z 6h44zewXIL+DjfTlzVw52krQZtFMmmMDwNC+CcRWbOq6gmljPDOwzOe9bCq8wOOyowZs 9TX0LO5gj92qKBn2HuzspynPHzcPnOD6+Exjl9afPolGE0EYq/ul0svSGj7IWhADPDki O4hxG35C+706AmgGtgjCW+51Resh6Pm25jIJB1sbAzZ/3pxRxfET11oRc8v1GMGLaDks o8f7etcc0i/nDAJM4ejYnnMF4eZlKKwm9MlCGG65bAg0Gp6UwwJGmAh8h+YKaSAl+HpI dKPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=anExuh2VOy470EdE/dhufHILJrRIwzzD50Y8DNx2onY=; b=VPy73CjZc4EW+Z6/0853b6zgBXF0ZkGbVwre13m4Nc0RjZ1AjqCRp5ooeX2SBS+EUG v07UJKiPrN2dD377xASF2q90/9yb/5ZDXKLoVcrKTT0VrrOP5qSDLpCTIWah7LyuLJfH Fw2NsBGSEKs4Z+ifshwIg6FwN7fmF5YDTVhVfVPqbfbRvxryPPZSIIJTTnqMi7KW2Yfw ZV7+fMEvs8gKUPAUoCY6qya4yi+tO+W2Dx9SuzWaKeXwMvLuiW1Fv7tcwGI7LMFbazkL IwGcMTa0p/SxtWuTIW9gI/Va54QYsYW0WdPAy78nCL2aB/nihKHztYg69s1TwdhjV8ww K6BQ==
X-Gm-Message-State: ALyK8tKZfaskeS4oXvtPQMozKQSVBEDaIcTNuj+8KG2vasayPr0jk1N6RHusJHTs2gjOkZUz/PhOp/Xi+tBVLg==
MIME-Version: 1.0
X-Received: by 10.55.161.1 with SMTP id k1mr555363qke.193.1464043686675; Mon, 23 May 2016 15:48:06 -0700 (PDT)
Received: by 10.55.185.70 with HTTP; Mon, 23 May 2016 15:48:06 -0700 (PDT)
In-Reply-To: <ED0991AE-DF16-4D42-9130-A2B42C4677A1@nostrum.com>
References: <ED0991AE-DF16-4D42-9130-A2B42C4677A1@nostrum.com>
Date: Mon, 23 May 2016 15:48:06 -0700
Message-ID: <CAKhHsXFybXGPjF-pQuJ7ctyq5qc8JYdgi9ctpTghpFbuOS4B2w@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=94eb2c05fa18e14e0505338a3b5f
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/X46z9izV0umjNIxPSrsLLCCKoZg>
Cc: mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Subject: Re: [MMUSIC] zrtp-hash (was Re: AD Evaluation of draft-ietf-mmusic-sdp-mux-attributes-12)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 22:48:10 -0000

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

Hi Ben,

The a=3Dzrtp-hash attribute is a hash of the ZRTP Hello message that is goi=
ng
to be sent over the transport.  There is one ZRTP Hello sent per transport,
and one handshake per transport.

The ZRTP message format was carefully crafted in association with
DTLS-SRTP, so if draft-ietf-avtcore-rfc5764-mux-fixes breaks this, then it
probably should be fixed.

- Alan -

On Mon, May 23, 2016 at 3:34 PM, Ben Campbell <ben@nostrum.com> wrote:

> Hi,
>
> As promised, here's more on my concern about zrtp-hash in
> draft-ietf-mmusic-sdp-mux-attributes:
>
> I think you need to describe the assumptions about what it means to
> multiplex zrtp. Am I correct to assume that the draft assumes that there =
is
> only one zrtp session in a transport flow, with a single zrtp handshake?
> And that all of the bundled m=3Dlines represent media that is part of tha=
t
> zrtp association? (That is, you never mux distinct zrtp associations, or
> zrtp and dtls-srtp?)
>
> If the answer is yes, then "transport" seems to make sense.
>
> But is zrtp demuxing really well defined enough to keep this out of the
> "NOT RECOMMENDED" category? I'm not sure it meets the bundle requirement
> for a public spec on how to demux it. One might infer that from two publi=
c
> specs (zrtp and 5764), but IIUC, the guidance proposed in
> draft-ietf-avtcore-rfc5764-mux-fixes would cause a zrtp messages to be
> dropped, since its first byte would not match any of the demux rules. Or,
> if zrtp-hash is allowed, does mux-fixes need to change?
>
> What am I missing?
>
> Thanks!
>
> Ben.
>
>
> On 20 May 2016, at 18:07, Ben Campbell wrote:
>
> Apologies for my slow response. The last month has been a perfect storm o=
f
>> productivity killers. I'm digging out of the backlog now. Comments inlin=
e,
>> with sections that appear resolved removed.
>>
>> There is one issue (zrtp-hash) where I will start a separate thread
>> shortly.
>>
>> Thanks!
>>
>> Ben.
>>
>> On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:
>>
>> Hello Ben
>>>
>>>  Sorry for the delay in responding. Many thanks for the detailed review=
.
>>>
>>>  Please find my responses inline (marked by [Suhas]).
>>>
>>> Cheers
>>> Suhas
>>>
>>> On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell <ben@nostrum.com> wrote:
>>>
>>> Hi,
>>>>
>>>> Here is my AD evaluation of draft-ietf-mmusic-sdp-mux-attributes-12. I
>>>> would like at least the substantive
>>>> section to be discussed before going to IETF last call.
>>>>
>>>> Thanks!
>>>>
>>>> Ben.
>>>>
>>>> ----------
>>>>
>>>> # Substantive #
>>>>
>>>> - This is very long and detailed. Are the authors and chairs comfortab=
le
>>>> that all sections have had sufficient review?
>>>>
>>>> -4.0: It would be helpful to add a paragraph describing how these
>>>> semantic
>>>> groupings map to the categories.
>>>>
>>>>
>>> [Suhas] The semantic groupings were added as a informal reference and
>>> they
>>> don't really interact with the categories as such.
>>>
>>
>> So I have to wonder why we have the groupings. But I guess at this point
>> in the process, it's not worth changing that.
>>
>>
>>> Does the following rephrasing work
>>>
>>> *"Attributes in an SDP session description can be defined at the
>>> **session-level
>>> or  media-level or  source-level. Informally, there are various semanti=
c
>>> grouping for these attributes. One such grouping could be as noted
>>> below:*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *   o  Attributes related to media content such as media type, encoding
>>>      schemes, payload types.   o  Attributes specifying media transport
>>> characteristics like RTP/RTP      Control Protocol (RTCP) port numbers,
>>> network addresses, QOS.   o  Metadata description attributes capturing
>>> session timing and      origin information.   o  Attributes establishin=
g
>>> relationships between media descriptions      such as grouping framewor=
k
>>> [RFC5888 <https://tools.ietf.org/html/rfc5888>]The proposed framework
>>> defines categories for the SDP attributes under multiplexing and assign=
s
>>> each SDP attribute to an appropriate multiplexing category.*
>>>
>>> *Since the multiplexing categories defined in this specification are
>>> independent of any informal semantic grouping of the SDP attributes, th=
e
>>> categorizations assigned against each attribute  MUST be considered as
>>> normative assignments under multiplexing. "*
>>>
>>
>> All fine, except the last sentence is pretty meta--it uses normative
>> language to talk about normative language ("MUST be considered normative=
").
>> I'm not entirely sure what you intend there, but how about something to =
the
>> effect of "... the categorizations assigned against each attribute are
>> normative."
>>
>>
>>>
>>>
>>> -4.2: I recommend choosing a category name that is not a 2119 keyword.
>>>>   Maybe something like "not mux-able" or "unsafe"?
>>>>
>>>>
>>> [Suhas]
>>>
>>> Initially that category was called "BAD" as in
>>>
>>>
>>> https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux-attrib=
utes/01/
>>>
>>> However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D was a=
 bad choice :-)
>>>
>>> Either of the following options seems fine to me
>>>
>>>    1.
>>>
>>>    NOT-RECOMMENDED [ we use hyphen separated multi word format in other
>>>    category names]
>>>    2. UNSAFE
>>>
>>
>> I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you intend
>> the category name to mean "NOT RECOMMENDED" in the 2119 sense.
>>
>>
>>>
>>>
>>>
>>>
>>>> -4.3: Please don't use a 2119 keyword as part of the definition
>>>> of a category. This creates sort of a circular dependency; that is
>>>> attributes are in this category because they MUST be identical; but th=
ey
>>>> MUST be identical because they are in this category. I suggest
>>>> describing
>>>> the category descriptively, and adding a separate sentence to say
>>>> "Attributes
>>>> in the IDENTICAL category MUST be identical across all media
>>>> descriptions."
>>>>
>>>>
>>>
>>> [Suhas]. I have removed the usage of word identical from the definition
>>> as
>>> below. Please let me know if this works.
>>>
>>>
>>> Category: IDENTICAL
>>>
>>> Attributes  and their associated values (if present) in the IDENTICAL
>>> category MUST be repeated across all the media descriptions under
>>> multiplexing.
>>>
>>>
>> Okay.
>>
>> [...]
>>
>>
>>>
>>>
>>> -5.8 and 5.9:
>>>>     The last paragraph of 5.8 seems redundant with section 5.9.
>>>>
>>>> -5.8, last paragraph:
>>>>
>>>>     "Hence multiplexing MUST NOT be performed even in this
>>>>     alternate scenario." seems to contradict the category selection of
>>>>     "NOT RECOMMENDED" (but see previous comment about not using 2119
>>>>     keywords in a category title.)
>>>>
>>>>
>>>> [Suhas] The idea here is to not perform multiplexing and hence the
>>> category
>>> of NOT RECOMMENDED assigned. I can update this once we finalize on the
>>> right naming for "NOT RECOMMENDED"
>>>
>>
>> This argues for the "UNSAFE" name, since the actual normative guidance i=
s
>> stronger than "NOT RECOMMENDED". (Unless you want a "MUST NOT" name :-) =
 )
>>
>>
>>>
>>>
>>> -5.24, last paragraph: "it is recommended to consult the
>>>>   document defining the attribute."
>>>>
>>>>   I assume one should _always_ refer to the specification of
>>>>   an SDP attribute before trying to mux it. But that doc is
>>>>   not going to explain muxing issues, is it?
>>>>
>>>>
>>>> [Suhas]
>>>
>>> Since cparmin/cparmax can define numerical values/ranges
>>>
>>> for any of b=3D or a=3D attributes (identified via cpar), there is no e=
asy
>>> way
>>> to assign a multiplexing category unless one knows what cpar is being
>>>
>>> used and the assignned numerical values to each of cparmin/cparmax mean=
.
>>> Thus the category SPECIAL has been assigned as a recommendation for the
>>> implementor to consult the spec that defines a particular usage of cpar=
,
>>> cparmin and cparmax combination to really see what=E2=80=99s going on.
>>>
>>> This is very similar to extmap or RTCP Application feedback message typ=
e
>>>
>>> How about following rephrasing
>>>
>>>
>>> *"The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and maxim=
um
>>> numerical values associated with the attributes described in a=3Dcpar.
>>> Since
>>> a cpar attribute can either define*
>>>
>>> *=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attribu=
te,  the multiplexing category *
>>>
>>> *depends on actual attribute being encapsulated and the implications of
>>> the
>>> numerical values assigned. Hence it is recommended to consult the
>>> specification defining the the attributes (cparmin/cparmax) to further
>>> analyze their behavior under multiplexing."*
>>>
>>
>> That works for me.
>>
>>
>>>
>>>
>>> -5.26:
>>>>   -"Support of this extension is OPTIONAL."
>>>>   Please don't use 2119 keywords to describe existing requirements
>>>>   from other docs, unless in direct quotes.
>>>>
>>>>
>>>>
>>> [Suhas] This sentence is taken directly from RFC6714. (
>>> https://tools.ietf.org/html/rfc6714)
>>>
>>
>> Sure, but it's not attributed as a quote. I suggest something to the
>> effect of "This is an optional extension according to [RFC6714]", "
>> [RFC6714] states that this extension is 'OPTIONAL'",  or even the exact
>> same language as currently in the draft, but without the capitalized
>> OPTIONAL.
>>
>> [...]
>>
>>
>>>
>>>
>>> - 5.39:
>>>>   I=E2=80=99m not a zrtp expert, but it seems like it might
>>>>   be more complicated than this. Section 8 of 6189 says
>>>>   =E2=80=9CThe a=3Dzrtp-hash attribute  can only be included in the
>>>>   SDP at the media level since Hello messages sent in
>>>>   different media streams will have unique hashes.=E2=80=9D
>>>>   I wonder if this shouldn't be =E2=80=9Cidentical=E2=80=9D?
>>>>
>>>>
>>>> [Suhas] The category TRANSPORT is the appropriate assignment. This spe=
c
>>> assigns category for these attributes over the multiplexed transport.
>>>
>>> So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.
>>>
>>> The zrtp-hash selected must correspond to the m=3Dline that is selected=
 for
>>> BUNDLE once the O/A negotiation completes. Thus the category TRANSPORT.
>>>
>>>
>>>
>> I _think_ you are right, but there may be an interaction here that can
>> break things I will think about that more, and respond to this issue is =
a
>> separate thread.
>>
>>
>>>
>>>
>>>
>>>> -5.45:
>>>>   6193 is an ISE stream RFC. Does anyone actually use
>>>>   in a context where muxing matters?
>>>>
>>>>
>>> [Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.
>>>
>>
>> That seems reasonable, unless  you know of good reasons otherwise.
>>
>>
>>>> -15.1:
>>>>   - Is there no need for a spec for any newly registered categories?
>>>>   - 2nd to last paragraph: "This seems vague for a MUST. Do you expect
>>>>     the registration of a new category to change the categories
>>>>     already assigned to existing SDP parameters? Is it possible
>>>>     that a new category only applies to some new SDP parameters?"
>>>>
>>>>
>>> [Suhas] The following 2 paragraphs are supposed to mean that new
>>> multiplexing categories require new registrations via a spec and
>>> applicability of the new category to new SDP attributes and possibly
>>> existing SDP attributes ( if the new category makes more sense). What
>>> would
>>> be a better framing to capture the intent ?
>>>
>>> "*Further entries can be registered on a first-come first-serve basis.
>>> Each
>>> registration needs to indicate the multiplexing category value to be
>>> added
>>> to the "Multiplexing Categories" subregistry as defined in this section=
.*
>>>
>>> *Such a registration MUST also indicate the applicability of the newly
>>> defined multiplexing category value to various subregistries defined at
>>> "Session Description Protocol (SDP) Parameters".*
>>>
>>
>> That works for me.
>>
>>
>>>
>>>   - Last paragraph: 4566 procedures apply to what? The text just said
>>>>     new categories are first-come-first server. I don=E2=80=99t think
>>>>     4566 set policies for how to change mux categories.
>>>>
>>>>
>>> [Suhas] Agreed. I prefer removing this line altogether. Please let me
>>> know
>>>
>>>
>> I agree.
>>
>>
>>>> -15.2.1:
>>>>   How do you expect the table to look after adding this RFC to the
>>>>   references? Will this RFC be added to the entries in the MUX
>>>>   column?
>>>>
>>>>
>>> [Suhas] The plan was to add the reference to this RFC in the "Reference
>>> Column"
>>>
>>
>> Okay.
>>
>> [...]
>>
>>
>>
>>>
>>>>
>>>> # Editorial #
>>>>
>>>>
>>> - The abstract is more detailed than needed. The point is to describe t=
he
>>>> purpose of the draft. The second paragraph pretty much accomplishes
>>>> that.
>>>>
>>>>
>>>> [Suhas] How do this rephrase look
>>>
>>> =E2=80=9CThe purpose of this specification is to provide a framework fo=
r
>>> analyzing
>>> the multiplexing characteristics of SDP attributes when SDP is used to
>>> negotiate the usage of single 5-tuple for sending and receiving media
>>> associated with multiple media descriptions,. This specification also
>>> categorizes the existing SDP attributes based on the framework describe=
d
>>> herein.=E2=80=9D
>>>
>>>
>> That works for me.
>>
>> [...]
>>
>>
>>>
>>>
>>>> -5 and subsections: Is there any method to the ordering? They aren't
>>>>    in RFC order. It might make sense to group by the nature of the
>>>>    attributes, but if that is the case here it's not explained.
>>>>
>>>>
>>>> [Suhas] These are not ordered as of today. I can order the 5.X
>>> subsections
>>> by RFC order, if needed.
>>>
>>
>> Unordered is also okay. I was just wondering if there was a logic that
>> should be mentioned.
>>
>>
>> [...]
>>
>>
>>>
>>>
>>>> -5.13, table:
>>>>   "Specific RTP extension document MUST be referred"
>>>>
>>>>
>>>> [Suhas] The idea was to mean that , one should refer to the
>>> specification
>>> that defines a specific RTP extension in order to understand the
>>> multiplexing behavior.
>>>
>>> Would the following rephrasing help instead
>>>
>>> "Refer to the document defining specific RTP Extension"
>>>
>>>
>>>
>> Yes, thanks.
>>
>>
>>>   I don=E2=80=99t understand what that means. If you mean to
>>>>    say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=E2=
=80=99t use MUST.
>>>>
>>>> -5.22, table: "document needs to be referred" (several repetitions)
>>>>   I'm not sure what this means. Should it say "Refer to the
>>>>   specific document"?
>>>>
>>>>
>>>> Similarly as above, would this reprhasing help
>>>
>>> "Refer to the document defining specific FEC Scheme
>>>
>>>
>>>
>> Similarly as above, Yes, thanks. :-)
>>
>>
>>>
>>>> -6.3: "not clearly defined offer/answer usage"
>>>>   I'm not sure what is meant here. (Also, why is this not TBD or NOT
>>>>   RECOMMENDED?)
>>>>
>>>>
>>> [Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind, eith=
er
>>> the
>>> BUNDLE spec or this spec cannot define its mux behavior. This is due to
>>> applicability of these specs under SD{ O/A usages alone.
>>>
>>> I can rephrase the above as
>>> "not defined under SDP Offer/Answer usage"
>>>
>>
>> WFM, thanks.
>>
>> [...]
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Hi Ben,<div><br></div><div>The a=3Dzrtp-hash attribute is =
a hash of the ZRTP Hello message that is going to be sent over the transpor=
t.=C2=A0 There is one ZRTP Hello sent per transport, and one handshake per =
transport.</div><div><br></div><div>The ZRTP message format was carefully c=
rafted in association with DTLS-SRTP, so if draft-ietf-avtcore-rfc5764-mux-=
fixes breaks this, then it probably should be fixed.</div><div><br></div><d=
iv>- Alan -</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, May 23, 2016 at 3:34 PM, Ben Campbell <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(20=
4,204,204);padding-left:1ex">Hi,<br>
<br>
As promised, here&#39;s more on my concern about zrtp-hash in draft-ietf-mm=
usic-sdp-mux-attributes:<br>
<br>
I think you need to describe the assumptions about what it means to multipl=
ex zrtp. Am I correct to assume that the draft assumes that there is only o=
ne zrtp session in a transport flow, with a single zrtp handshake? And that=
 all of the bundled m=3Dlines represent media that is part of that zrtp ass=
ociation? (That is, you never mux distinct zrtp associations, or zrtp and d=
tls-srtp?)<br>
<br>
If the answer is yes, then &quot;transport&quot; seems to make sense.<br>
<br>
But is zrtp demuxing really well defined enough to keep this out of the &qu=
ot;NOT RECOMMENDED&quot; category? I&#39;m not sure it meets the bundle req=
uirement for a public spec on how to demux it. One might infer that from tw=
o public specs (zrtp and 5764), but IIUC, the guidance proposed in draft-ie=
tf-avtcore-rfc5764-mux-fixes would cause a zrtp messages to be dropped, sin=
ce its first byte would not match any of the demux rules. Or, if zrtp-hash =
is allowed, does mux-fixes need to change?<br>
<br>
What am I missing?<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
<br>
On 20 May 2016, at 18:07, Ben Campbell wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Apologies for my slow response. The last month has been a perfect storm of =
productivity killers. I&#39;m digging out of the backlog now. Comments inli=
ne, with sections that appear resolved removed.<br>
<br>
There is one issue (zrtp-hash) where I will start a separate thread shortly=
.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Hello Ben<br>
<br>
=C2=A0Sorry for the delay in responding. Many thanks for the detailed revie=
w.<br>
<br>
=C2=A0Please find my responses inline (marked by [Suhas]).<br>
<br>
Cheers<br>
Suhas<br>
<br>
On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell &lt;<a href=3D"mailto:ben@nos=
trum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Hi,<br>
<br>
Here is my AD evaluation of draft-ietf-mmusic-sdp-mux-attributes-12. I<br>
would like at least the substantive<br>
section to be discussed before going to IETF last call.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
----------<br>
<br>
# Substantive #<br>
<br>
- This is very long and detailed. Are the authors and chairs comfortable<br=
>
that all sections have had sufficient review?<br>
<br>
-4.0: It would be helpful to add a paragraph describing how these semantic<=
br>
groupings map to the categories.<br>
<br>
</blockquote>
<br>
[Suhas] The semantic groupings were added as a informal reference and they<=
br>
don&#39;t really interact with the categories as such.<br>
</blockquote>
<br>
So I have to wonder why we have the groupings. But I guess at this point in=
 the process, it&#39;s not worth changing that.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
Does the following rephrasing work<br>
<br>
*&quot;Attributes in an SDP session description can be defined at the<br>
**session-level<br>
or=C2=A0 media-level or=C2=A0 source-level. Informally, there are various s=
emantic<br>
grouping for these attributes. One such grouping could be as noted below:*<=
br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
*=C2=A0 =C2=A0o=C2=A0 Attributes related to media content such as media typ=
e, encoding<br>
=C2=A0 =C2=A0 =C2=A0schemes, payload types.=C2=A0 =C2=A0o=C2=A0 Attributes =
specifying media transport<br>
characteristics like RTP/RTP=C2=A0 =C2=A0 =C2=A0 Control Protocol (RTCP) po=
rt numbers,<br>
network addresses, QOS.=C2=A0 =C2=A0o=C2=A0 Metadata description attributes=
 capturing<br>
session timing and=C2=A0 =C2=A0 =C2=A0 origin information.=C2=A0 =C2=A0o=C2=
=A0 Attributes establishing<br>
relationships between media descriptions=C2=A0 =C2=A0 =C2=A0 such as groupi=
ng framework<br>
[RFC5888 &lt;<a href=3D"https://tools.ietf.org/html/rfc5888" rel=3D"norefer=
rer" target=3D"_blank">https://tools.ietf.org/html/rfc5888</a>&gt;]The prop=
osed framework<br>
defines categories for the SDP attributes under multiplexing and assigns<br=
>
each SDP attribute to an appropriate multiplexing category.*<br>
<br>
*Since the multiplexing categories defined in this specification are<br>
independent of any informal semantic grouping of the SDP attributes, the<br=
>
categorizations assigned against each attribute=C2=A0 MUST be considered as=
<br>
normative assignments under multiplexing. &quot;*<br>
</blockquote>
<br>
All fine, except the last sentence is pretty meta--it uses normative langua=
ge to talk about normative language (&quot;MUST be considered normative&quo=
t;). I&#39;m not entirely sure what you intend there, but how about somethi=
ng to the effect of &quot;... the categorizations assigned against each att=
ribute are normative.&quot;<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-4.2: I recommend choosing a category name that is not a 2119 keyword.<br>
=C2=A0 Maybe something like &quot;not mux-able&quot; or &quot;unsafe&quot;?=
<br>
<br>
</blockquote>
<br>
[Suhas]<br>
<br>
Initially that category was called &quot;BAD&quot; as in<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux=
-attributes/01/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.i=
etf.org/doc/draft-nandakumar-mmusic-sdp-mux-attributes/01/</a><br>
<br>
However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D was a bad=
 choice :-)<br>
<br>
Either of the following options seems fine to me<br>
<br>
=C2=A0 =C2=A01.<br>
<br>
=C2=A0 =C2=A0NOT-RECOMMENDED [ we use hyphen separated multi word format in=
 other<br>
=C2=A0 =C2=A0category names]<br>
=C2=A0 =C2=A02. UNSAFE<br>
</blockquote>
<br>
I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you intend the =
category name to mean &quot;NOT RECOMMENDED&quot; in the 2119 sense.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
-4.3: Please don&#39;t use a 2119 keyword as part of the definition<br>
of a category. This creates sort of a circular dependency; that is<br>
attributes are in this category because they MUST be identical; but they<br=
>
MUST be identical because they are in this category. I suggest describing<b=
r>
the category descriptively, and adding a separate sentence to say<br>
&quot;Attributes<br>
in the IDENTICAL category MUST be identical across all media descriptions.&=
quot;<br>
<br>
</blockquote>
<br>
<br>
[Suhas]. I have removed the usage of word identical from the definition as<=
br>
below. Please let me know if this works.<br>
<br>
<br>
Category: IDENTICAL<br>
<br>
Attributes=C2=A0 and their associated values (if present) in the IDENTICAL<=
br>
category MUST be repeated across all the media descriptions under<br>
multiplexing.<br>
<br>
</blockquote>
<br>
Okay.<br>
<br>
[...]<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-5.8 and 5.9:<br>
=C2=A0 =C2=A0 The last paragraph of 5.8 seems redundant with section 5.9.<b=
r>
<br>
-5.8, last paragraph:<br>
<br>
=C2=A0 =C2=A0 &quot;Hence multiplexing MUST NOT be performed even in this<b=
r>
=C2=A0 =C2=A0 alternate scenario.&quot; seems to contradict the category se=
lection of<br>
=C2=A0 =C2=A0 &quot;NOT RECOMMENDED&quot; (but see previous comment about n=
ot using 2119<br>
=C2=A0 =C2=A0 keywords in a category title.)<br>
<br>
<br>
</blockquote>
[Suhas] The idea here is to not perform multiplexing and hence the category=
<br>
of NOT RECOMMENDED assigned. I can update this once we finalize on the<br>
right naming for &quot;NOT RECOMMENDED&quot;<br>
</blockquote>
<br>
This argues for the &quot;UNSAFE&quot; name, since the actual normative gui=
dance is stronger than &quot;NOT RECOMMENDED&quot;. (Unless you want a &quo=
t;MUST NOT&quot; name :-)=C2=A0 )<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-5.24, last paragraph: &quot;it is recommended to consult the<br>
=C2=A0 document defining the attribute.&quot;<br>
<br>
=C2=A0 I assume one should _always_ refer to the specification of<br>
=C2=A0 an SDP attribute before trying to mux it. But that doc is<br>
=C2=A0 not going to explain muxing issues, is it?<br>
<br>
<br>
</blockquote>
[Suhas]<br>
<br>
Since cparmin/cparmax can define numerical values/ranges<br>
<br>
for any of b=3D or a=3D attributes (identified via cpar), there is no easy =
way<br>
to assign a multiplexing category unless one knows what cpar is being<br>
<br>
used and the assignned numerical values to each of cparmin/cparmax mean.<br=
>
Thus the category SPECIAL has been assigned as a recommendation for the<br>
implementor to consult the spec that defines a particular usage of cpar,<br=
>
cparmin and cparmax combination to really see what=E2=80=99s going on.<br>
<br>
This is very similar to extmap or RTCP Application feedback message type<br=
>
<br>
How about following rephrasing<br>
<br>
<br>
*&quot;The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and maxi=
mum<br>
numerical values associated with the attributes described in a=3Dcpar. Sinc=
e<br>
a cpar attribute can either define*<br>
<br>
*=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attribute,=
=C2=A0 the multiplexing category *<br>
<br>
*depends on actual attribute being encapsulated and the implications of the=
<br>
numerical values assigned. Hence it is recommended to consult the<br>
specification defining the the attributes (cparmin/cparmax) to further<br>
analyze their behavior under multiplexing.&quot;*<br>
</blockquote>
<br>
That works for me.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-5.26:<br>
=C2=A0 -&quot;Support of this extension is OPTIONAL.&quot;<br>
=C2=A0 Please don&#39;t use 2119 keywords to describe existing requirements=
<br>
=C2=A0 from other docs, unless in direct quotes.<br>
<br>
<br>
</blockquote>
<br>
[Suhas] This sentence is taken directly from RFC6714. (<br>
<a href=3D"https://tools.ietf.org/html/rfc6714" rel=3D"noreferrer" target=
=3D"_blank">https://tools.ietf.org/html/rfc6714</a>)<br>
</blockquote>
<br>
Sure, but it&#39;s not attributed as a quote. I suggest something to the ef=
fect of &quot;This is an optional extension according to [RFC6714]&quot;, &=
quot; [RFC6714] states that this extension is &#39;OPTIONAL&#39;&quot;,=C2=
=A0 or even the exact same language as currently in the draft, but without =
the capitalized OPTIONAL.<br>
<br>
[...]<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
- 5.39:<br>
=C2=A0 I=E2=80=99m not a zrtp expert, but it seems like it might<br>
=C2=A0 be more complicated than this. Section 8 of 6189 says<br>
=C2=A0 =E2=80=9CThe a=3Dzrtp-hash attribute=C2=A0 can only be included in t=
he<br>
=C2=A0 SDP at the media level since Hello messages sent in<br>
=C2=A0 different media streams will have unique hashes.=E2=80=9D<br>
=C2=A0 I wonder if this shouldn&#39;t be =E2=80=9Cidentical=E2=80=9D?<br>
<br>
<br>
</blockquote>
[Suhas] The category TRANSPORT is the appropriate assignment. This spec<br>
assigns category for these attributes over the multiplexed transport.<br>
<br>
So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.<br>
<br>
The zrtp-hash selected must correspond to the m=3Dline that is selected for=
<br>
BUNDLE once the O/A negotiation completes. Thus the category TRANSPORT.<br>
<br>
<br>
</blockquote>
<br>
I _think_ you are right, but there may be an interaction here that can brea=
k things I will think about that more, and respond to this issue is a separ=
ate thread.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
-5.45:<br>
=C2=A0 6193 is an ISE stream RFC. Does anyone actually use<br>
=C2=A0 in a context where muxing matters?<br>
<br>
</blockquote>
<br>
[Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.<br>
</blockquote>
<br>
That seems reasonable, unless=C2=A0 you know of good reasons otherwise.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">
<br>
-15.1:<br>
=C2=A0 - Is there no need for a spec for any newly registered categories?<b=
r>
=C2=A0 - 2nd to last paragraph: &quot;This seems vague for a MUST. Do you e=
xpect<br>
=C2=A0 =C2=A0 the registration of a new category to change the categories<b=
r>
=C2=A0 =C2=A0 already assigned to existing SDP parameters? Is it possible<b=
r>
=C2=A0 =C2=A0 that a new category only applies to some new SDP parameters?&=
quot;<br>
<br>
</blockquote>
<br>
[Suhas] The following 2 paragraphs are supposed to mean that new<br>
multiplexing categories require new registrations via a spec and<br>
applicability of the new category to new SDP attributes and possibly<br>
existing SDP attributes ( if the new category makes more sense). What would=
<br>
be a better framing to capture the intent ?<br>
<br>
&quot;*Further entries can be registered on a first-come first-serve basis.=
 Each<br>
registration needs to indicate the multiplexing category value to be added<=
br>
to the &quot;Multiplexing Categories&quot; subregistry as defined in this s=
ection.*<br>
<br>
*Such a registration MUST also indicate the applicability of the newly<br>
defined multiplexing category value to various subregistries defined at<br>
&quot;Session Description Protocol (SDP) Parameters&quot;.*<br>
</blockquote>
<br>
That works for me.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 - Last paragraph: 4566 procedures apply to what? The text just said<=
br>
=C2=A0 =C2=A0 new categories are first-come-first server. I don=E2=80=99t t=
hink<br>
=C2=A0 =C2=A0 4566 set policies for how to change mux categories.<br>
<br>
</blockquote>
<br>
[Suhas] Agreed. I prefer removing this line altogether. Please let me know<=
br>
<br>
</blockquote>
<br>
I agree.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">
<br>
-15.2.1:<br>
=C2=A0 How do you expect the table to look after adding this RFC to the<br>
=C2=A0 references? Will this RFC be added to the entries in the MUX<br>
=C2=A0 column?<br>
<br>
</blockquote>
<br>
[Suhas] The plan was to add the reference to this RFC in the &quot;Referenc=
e<br>
Column&quot;<br>
</blockquote>
<br>
Okay.<br>
<br>
[...]<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
# Editorial #<br>
<br>
</blockquote>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
- The abstract is more detailed than needed. The point is to describe the<b=
r>
purpose of the draft. The second paragraph pretty much accomplishes that.<b=
r>
<br>
<br>
</blockquote>
[Suhas] How do this rephrase look<br>
<br>
=E2=80=9CThe purpose of this specification is to provide a framework for an=
alyzing<br>
the multiplexing characteristics of SDP attributes when SDP is used to<br>
negotiate the usage of single 5-tuple for sending and receiving media<br>
associated with multiple media descriptions,. This specification also<br>
categorizes the existing SDP attributes based on the framework described<br=
>
herein.=E2=80=9D<br>
<br>
</blockquote>
<br>
That works for me.<br>
<br>
[...]<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
-5 and subsections: Is there any method to the ordering? They aren&#39;t<br=
>
=C2=A0 =C2=A0in RFC order. It might make sense to group by the nature of th=
e<br>
=C2=A0 =C2=A0attributes, but if that is the case here it&#39;s not explaine=
d.<br>
<br>
<br>
</blockquote>
[Suhas] These are not ordered as of today. I can order the 5.X subsections<=
br>
by RFC order, if needed.<br>
</blockquote>
<br>
Unordered is also okay. I was just wondering if there was a logic that shou=
ld be mentioned.<br>
<br>
<br>
[...]<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
-5.13, table:<br>
=C2=A0 &quot;Specific RTP extension document MUST be referred&quot;<br>
<br>
<br>
</blockquote>
[Suhas] The idea was to mean that , one should refer to the specification<b=
r>
that defines a specific RTP extension in order to understand the<br>
multiplexing behavior.<br>
<br>
Would the following rephrasing help instead<br>
<br>
&quot;Refer to the document defining specific RTP Extension&quot;<br>
<br>
<br>
</blockquote>
<br>
Yes, thanks.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 I don=E2=80=99t understand what that means. If you mean to<br>
=C2=A0 =C2=A0say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=
=E2=80=99t use MUST.<br>
<br>
-5.22, table: &quot;document needs to be referred&quot; (several repetition=
s)<br>
=C2=A0 I&#39;m not sure what this means. Should it say &quot;Refer to the<b=
r>
=C2=A0 specific document&quot;?<br>
<br>
<br>
</blockquote>
Similarly as above, would this reprhasing help<br>
<br>
&quot;Refer to the document defining specific FEC Scheme<br>
<br>
<br>
</blockquote>
<br>
Similarly as above, Yes, thanks. :-)<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
-6.3: &quot;not clearly defined offer/answer usage&quot;<br>
=C2=A0 I&#39;m not sure what is meant here. (Also, why is this not TBD or N=
OT<br>
=C2=A0 RECOMMENDED?)<br>
<br>
</blockquote>
<br>
[Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind, either t=
he<br>
BUNDLE spec or this spec cannot define its mux behavior. This is due to<br>
applicability of these specs under SD{ O/A usages alone.<br>
<br>
I can rephrase the above as<br>
&quot;not defined under SDP Offer/Answer usage&quot;<br>
</blockquote>
<br>
WFM, thanks.<br>
<br>
[...]<br>
</blockquote>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div><br></div></div>

--94eb2c05fa18e14e0505338a3b5f--


From nobody Mon May 23 16:12:15 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C9512D5D3; Mon, 23 May 2016 16:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 EvR4RjtsIsR5; Mon, 23 May 2016 16:12:10 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4A5212D5DF; Mon, 23 May 2016 16:12:07 -0700 (PDT)
Received: from [10.0.1.18] (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 u4NNC5Kg032637 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 23 May 2016 18:12:05 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.18]
From: "Ben Campbell" <ben@nostrum.com>
To: "Alan Johnston" <alan.b.johnston@gmail.com>
Date: Mon, 23 May 2016 18:12:06 -0500
Message-ID: <66ECA4FB-729F-421B-8CD7-C87E6FD248F0@nostrum.com>
In-Reply-To: <CAKhHsXFybXGPjF-pQuJ7ctyq5qc8JYdgi9ctpTghpFbuOS4B2w@mail.gmail.com>
References: <ED0991AE-DF16-4D42-9130-A2B42C4677A1@nostrum.com> <CAKhHsXFybXGPjF-pQuJ7ctyq5qc8JYdgi9ctpTghpFbuOS4B2w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/etPlkwniOmYgWgJQJsAGmMo8QZY>
Cc: mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Subject: Re: [MMUSIC] zrtp-hash (was Re: AD Evaluation of draft-ietf-mmusic-sdp-mux-attributes-12)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 23:12:13 -0000

Hi Alan,

If I read RFC 6189 correctly, I see that it documents how to distinguish =

zrtp messages from rtp and stun. Further, it distinguishes itself from =

stun by using a different magic cookie value. That's a little more =

complex than the first-byte demuxing in 5764--although it looks like =

first-byte demuxing might work as long as we don't end up with a =

conflicting stun method. (I'm also not certain that the average 5764 =

implementation is going to look at the cookie to make the demux =

decision.)

I don't see anything in 6189 about distinguishing itself from DTLS. =

Again, we can infer that from the first byte, as long as we don't get a =

conflicting tls content-type.

This doesn't quite seem (to me) to meet the following requirement in =

draft-ietf-mmusic-sdp-bundle-negotiation (emphasis mine):

   "If bundled "m=3D" lines use different protocols on top
    of the transport-layer protocol,  there MUST exist a publicly
    available specification which describes a mechanism, for **this
    particular protocol combination**, how to associate received data =

with
    the correct protocol."

As mentioned, one way to fix that could be to add zrtp into the general =

guidance in 5764-mux-fixes.

Thanks,

Ben.


On 23 May 2016, at 17:48, Alan Johnston wrote:

> Hi Ben,
>
> The a=3Dzrtp-hash attribute is a hash of the ZRTP Hello message that is=
 =

> going
> to be sent over the transport.  There is one ZRTP Hello sent per =

> transport,
> and one handshake per transport.
>
> The ZRTP message format was carefully crafted in association with
> DTLS-SRTP, so if draft-ietf-avtcore-rfc5764-mux-fixes breaks this, =

> then it
> probably should be fixed.
>
> - Alan -
>
> On Mon, May 23, 2016 at 3:34 PM, Ben Campbell <ben@nostrum.com> wrote:
>
>> Hi,
>>
>> As promised, here's more on my concern about zrtp-hash in
>> draft-ietf-mmusic-sdp-mux-attributes:
>>
>> I think you need to describe the assumptions about what it means to
>> multiplex zrtp. Am I correct to assume that the draft assumes that =

>> there is
>> only one zrtp session in a transport flow, with a single zrtp =

>> handshake?
>> And that all of the bundled m=3Dlines represent media that is part of =

>> that
>> zrtp association? (That is, you never mux distinct zrtp associations, =

>> or
>> zrtp and dtls-srtp?)
>>
>> If the answer is yes, then "transport" seems to make sense.
>>
>> But is zrtp demuxing really well defined enough to keep this out of =

>> the
>> "NOT RECOMMENDED" category? I'm not sure it meets the bundle =

>> requirement
>> for a public spec on how to demux it. One might infer that from two =

>> public
>> specs (zrtp and 5764), but IIUC, the guidance proposed in
>> draft-ietf-avtcore-rfc5764-mux-fixes would cause a zrtp messages to =

>> be
>> dropped, since its first byte would not match any of the demux rules. =

>> Or,
>> if zrtp-hash is allowed, does mux-fixes need to change?
>>
>> What am I missing?
>>
>> Thanks!
>>
>> Ben.
>>
>>
>> On 20 May 2016, at 18:07, Ben Campbell wrote:
>>
>> Apologies for my slow response. The last month has been a perfect =

>> storm of
>>> productivity killers. I'm digging out of the backlog now. Comments =

>>> inline,
>>> with sections that appear resolved removed.
>>>
>>> There is one issue (zrtp-hash) where I will start a separate thread
>>> shortly.
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>> On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:
>>>
>>> Hello Ben
>>>>
>>>>  Sorry for the delay in responding. Many thanks for the detailed =

>>>> review.
>>>>
>>>>  Please find my responses inline (marked by [Suhas]).
>>>>
>>>> Cheers
>>>> Suhas
>>>>
>>>> On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell <ben@nostrum.com> =

>>>> wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> Here is my AD evaluation of =

>>>>> draft-ietf-mmusic-sdp-mux-attributes-12. I
>>>>> would like at least the substantive
>>>>> section to be discussed before going to IETF last call.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Ben.
>>>>>
>>>>> ----------
>>>>>
>>>>> # Substantive #
>>>>>
>>>>> - This is very long and detailed. Are the authors and chairs =

>>>>> comfortable
>>>>> that all sections have had sufficient review?
>>>>>
>>>>> -4.0: It would be helpful to add a paragraph describing how these
>>>>> semantic
>>>>> groupings map to the categories.
>>>>>
>>>>>
>>>> [Suhas] The semantic groupings were added as a informal reference =

>>>> and
>>>> they
>>>> don't really interact with the categories as such.
>>>>
>>>
>>> So I have to wonder why we have the groupings. But I guess at this =

>>> point
>>> in the process, it's not worth changing that.
>>>
>>>
>>>> Does the following rephrasing work
>>>>
>>>> *"Attributes in an SDP session description can be defined at the
>>>> **session-level
>>>> or  media-level or  source-level. Informally, there are various =

>>>> semantic
>>>> grouping for these attributes. One such grouping could be as noted
>>>> below:*
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *   o  Attributes related to media content such as media type, =

>>>> encoding
>>>>      schemes, payload types.   o  Attributes specifying media =

>>>> transport
>>>> characteristics like RTP/RTP      Control Protocol (RTCP) port =

>>>> numbers,
>>>> network addresses, QOS.   o  Metadata description attributes =

>>>> capturing
>>>> session timing and      origin information.   o  Attributes =

>>>> establishing
>>>> relationships between media descriptions      such as grouping =

>>>> framework
>>>> [RFC5888 <https://tools.ietf.org/html/rfc5888>]The proposed =

>>>> framework
>>>> defines categories for the SDP attributes under multiplexing and =

>>>> assigns
>>>> each SDP attribute to an appropriate multiplexing category.*
>>>>
>>>> *Since the multiplexing categories defined in this specification =

>>>> are
>>>> independent of any informal semantic grouping of the SDP =

>>>> attributes, the
>>>> categorizations assigned against each attribute  MUST be considered =

>>>> as
>>>> normative assignments under multiplexing. "*
>>>>
>>>
>>> All fine, except the last sentence is pretty meta--it uses normative
>>> language to talk about normative language ("MUST be considered =

>>> normative").
>>> I'm not entirely sure what you intend there, but how about something =

>>> to the
>>> effect of "... the categorizations assigned against each attribute =

>>> are
>>> normative."
>>>
>>>
>>>>
>>>>
>>>> -4.2: I recommend choosing a category name that is not a 2119 =

>>>> keyword.
>>>>>   Maybe something like "not mux-able" or "unsafe"?
>>>>>
>>>>>
>>>> [Suhas]
>>>>
>>>> Initially that category was called "BAD" as in
>>>>
>>>>
>>>> https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux-att=
ributes/01/
>>>>
>>>> However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D wa=
s a bad =

>>>> choice :-)
>>>>
>>>> Either of the following options seems fine to me
>>>>
>>>>    1.
>>>>
>>>>    NOT-RECOMMENDED [ we use hyphen separated multi word format in =

>>>> other
>>>>    category names]
>>>>    2. UNSAFE
>>>>
>>>
>>> I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you =

>>> intend
>>> the category name to mean "NOT RECOMMENDED" in the 2119 sense.
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>>> -4.3: Please don't use a 2119 keyword as part of the definition
>>>>> of a category. This creates sort of a circular dependency; that is
>>>>> attributes are in this category because they MUST be identical; =

>>>>> but they
>>>>> MUST be identical because they are in this category. I suggest
>>>>> describing
>>>>> the category descriptively, and adding a separate sentence to say
>>>>> "Attributes
>>>>> in the IDENTICAL category MUST be identical across all media
>>>>> descriptions."
>>>>>
>>>>>
>>>>
>>>> [Suhas]. I have removed the usage of word identical from the =

>>>> definition
>>>> as
>>>> below. Please let me know if this works.
>>>>
>>>>
>>>> Category: IDENTICAL
>>>>
>>>> Attributes  and their associated values (if present) in the =

>>>> IDENTICAL
>>>> category MUST be repeated across all the media descriptions under
>>>> multiplexing.
>>>>
>>>>
>>> Okay.
>>>
>>> [...]
>>>
>>>
>>>>
>>>>
>>>> -5.8 and 5.9:
>>>>>     The last paragraph of 5.8 seems redundant with section 5.9.
>>>>>
>>>>> -5.8, last paragraph:
>>>>>
>>>>>     "Hence multiplexing MUST NOT be performed even in this
>>>>>     alternate scenario." seems to contradict the category =

>>>>> selection of
>>>>>     "NOT RECOMMENDED" (but see previous comment about not using =

>>>>> 2119
>>>>>     keywords in a category title.)
>>>>>
>>>>>
>>>>> [Suhas] The idea here is to not perform multiplexing and hence the
>>>> category
>>>> of NOT RECOMMENDED assigned. I can update this once we finalize on =

>>>> the
>>>> right naming for "NOT RECOMMENDED"
>>>>
>>>
>>> This argues for the "UNSAFE" name, since the actual normative =

>>> guidance is
>>> stronger than "NOT RECOMMENDED". (Unless you want a "MUST NOT" name =

>>> :-)  )
>>>
>>>
>>>>
>>>>
>>>> -5.24, last paragraph: "it is recommended to consult the
>>>>>   document defining the attribute."
>>>>>
>>>>>   I assume one should _always_ refer to the specification of
>>>>>   an SDP attribute before trying to mux it. But that doc is
>>>>>   not going to explain muxing issues, is it?
>>>>>
>>>>>
>>>>> [Suhas]
>>>>
>>>> Since cparmin/cparmax can define numerical values/ranges
>>>>
>>>> for any of b=3D or a=3D attributes (identified via cpar), there is n=
o =

>>>> easy
>>>> way
>>>> to assign a multiplexing category unless one knows what cpar is =

>>>> being
>>>>
>>>> used and the assignned numerical values to each of cparmin/cparmax =

>>>> mean.
>>>> Thus the category SPECIAL has been assigned as a recommendation for =

>>>> the
>>>> implementor to consult the spec that defines a particular usage of =

>>>> cpar,
>>>> cparmin and cparmax combination to really see what=E2=80=99s going o=
n.
>>>>
>>>> This is very similar to extmap or RTCP Application feedback message =

>>>> type
>>>>
>>>> How about following rephrasing
>>>>
>>>>
>>>> *"The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and =

>>>> maximum
>>>> numerical values associated with the attributes described in =

>>>> a=3Dcpar.
>>>> Since
>>>> a cpar attribute can either define*
>>>>
>>>> *=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attr=
ibute,  the multiplexing =

>>>> category *
>>>>
>>>> *depends on actual attribute being encapsulated and the =

>>>> implications of
>>>> the
>>>> numerical values assigned. Hence it is recommended to consult the
>>>> specification defining the the attributes (cparmin/cparmax) to =

>>>> further
>>>> analyze their behavior under multiplexing."*
>>>>
>>>
>>> That works for me.
>>>
>>>
>>>>
>>>>
>>>> -5.26:
>>>>>   -"Support of this extension is OPTIONAL."
>>>>>   Please don't use 2119 keywords to describe existing requirements
>>>>>   from other docs, unless in direct quotes.
>>>>>
>>>>>
>>>>>
>>>> [Suhas] This sentence is taken directly from RFC6714. (
>>>> https://tools.ietf.org/html/rfc6714)
>>>>
>>>
>>> Sure, but it's not attributed as a quote. I suggest something to the
>>> effect of "This is an optional extension according to [RFC6714]", "
>>> [RFC6714] states that this extension is 'OPTIONAL'",  or even the =

>>> exact
>>> same language as currently in the draft, but without the capitalized
>>> OPTIONAL.
>>>
>>> [...]
>>>
>>>
>>>>
>>>>
>>>> - 5.39:
>>>>>   I=E2=80=99m not a zrtp expert, but it seems like it might
>>>>>   be more complicated than this. Section 8 of 6189 says
>>>>>   =E2=80=9CThe a=3Dzrtp-hash attribute  can only be included in the=

>>>>>   SDP at the media level since Hello messages sent in
>>>>>   different media streams will have unique hashes.=E2=80=9D
>>>>>   I wonder if this shouldn't be =E2=80=9Cidentical=E2=80=9D?
>>>>>
>>>>>
>>>>> [Suhas] The category TRANSPORT is the appropriate assignment. This =

>>>>> spec
>>>> assigns category for these attributes over the multiplexed =

>>>> transport.
>>>>
>>>> So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.=

>>>>
>>>> The zrtp-hash selected must correspond to the m=3Dline that is =

>>>> selected for
>>>> BUNDLE once the O/A negotiation completes. Thus the category =

>>>> TRANSPORT.
>>>>
>>>>
>>>>
>>> I _think_ you are right, but there may be an interaction here that =

>>> can
>>> break things I will think about that more, and respond to this issue =

>>> is a
>>> separate thread.
>>>
>>>
>>>>
>>>>
>>>>
>>>>> -5.45:
>>>>>   6193 is an ISE stream RFC. Does anyone actually use
>>>>>   in a context where muxing matters?
>>>>>
>>>>>
>>>> [Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.
>>>>
>>>
>>> That seems reasonable, unless  you know of good reasons otherwise.
>>>
>>>
>>>>> -15.1:
>>>>>   - Is there no need for a spec for any newly registered =

>>>>> categories?
>>>>>   - 2nd to last paragraph: "This seems vague for a MUST. Do you =

>>>>> expect
>>>>>     the registration of a new category to change the categories
>>>>>     already assigned to existing SDP parameters? Is it possible
>>>>>     that a new category only applies to some new SDP parameters?"
>>>>>
>>>>>
>>>> [Suhas] The following 2 paragraphs are supposed to mean that new
>>>> multiplexing categories require new registrations via a spec and
>>>> applicability of the new category to new SDP attributes and =

>>>> possibly
>>>> existing SDP attributes ( if the new category makes more sense). =

>>>> What
>>>> would
>>>> be a better framing to capture the intent ?
>>>>
>>>> "*Further entries can be registered on a first-come first-serve =

>>>> basis.
>>>> Each
>>>> registration needs to indicate the multiplexing category value to =

>>>> be
>>>> added
>>>> to the "Multiplexing Categories" subregistry as defined in this =

>>>> section.*
>>>>
>>>> *Such a registration MUST also indicate the applicability of the =

>>>> newly
>>>> defined multiplexing category value to various subregistries =

>>>> defined at
>>>> "Session Description Protocol (SDP) Parameters".*
>>>>
>>>
>>> That works for me.
>>>
>>>
>>>>
>>>>   - Last paragraph: 4566 procedures apply to what? The text just =

>>>> said
>>>>>     new categories are first-come-first server. I don=E2=80=99t thi=
nk
>>>>>     4566 set policies for how to change mux categories.
>>>>>
>>>>>
>>>> [Suhas] Agreed. I prefer removing this line altogether. Please let =

>>>> me
>>>> know
>>>>
>>>>
>>> I agree.
>>>
>>>
>>>>> -15.2.1:
>>>>>   How do you expect the table to look after adding this RFC to the
>>>>>   references? Will this RFC be added to the entries in the MUX
>>>>>   column?
>>>>>
>>>>>
>>>> [Suhas] The plan was to add the reference to this RFC in the =

>>>> "Reference
>>>> Column"
>>>>
>>>
>>> Okay.
>>>
>>> [...]
>>>
>>>
>>>
>>>>
>>>>>
>>>>> # Editorial #
>>>>>
>>>>>
>>>> - The abstract is more detailed than needed. The point is to =

>>>> describe the
>>>>> purpose of the draft. The second paragraph pretty much =

>>>>> accomplishes
>>>>> that.
>>>>>
>>>>>
>>>>> [Suhas] How do this rephrase look
>>>>
>>>> =E2=80=9CThe purpose of this specification is to provide a framework=
 for
>>>> analyzing
>>>> the multiplexing characteristics of SDP attributes when SDP is used =

>>>> to
>>>> negotiate the usage of single 5-tuple for sending and receiving =

>>>> media
>>>> associated with multiple media descriptions,. This specification =

>>>> also
>>>> categorizes the existing SDP attributes based on the framework =

>>>> described
>>>> herein.=E2=80=9D
>>>>
>>>>
>>> That works for me.
>>>
>>> [...]
>>>
>>>
>>>>
>>>>
>>>>> -5 and subsections: Is there any method to the ordering? They =

>>>>> aren't
>>>>>    in RFC order. It might make sense to group by the nature of the
>>>>>    attributes, but if that is the case here it's not explained.
>>>>>
>>>>>
>>>>> [Suhas] These are not ordered as of today. I can order the 5.X
>>>> subsections
>>>> by RFC order, if needed.
>>>>
>>>
>>> Unordered is also okay. I was just wondering if there was a logic =

>>> that
>>> should be mentioned.
>>>
>>>
>>> [...]
>>>
>>>
>>>>
>>>>
>>>>> -5.13, table:
>>>>>   "Specific RTP extension document MUST be referred"
>>>>>
>>>>>
>>>>> [Suhas] The idea was to mean that , one should refer to the
>>>> specification
>>>> that defines a specific RTP extension in order to understand the
>>>> multiplexing behavior.
>>>>
>>>> Would the following rephrasing help instead
>>>>
>>>> "Refer to the document defining specific RTP Extension"
>>>>
>>>>
>>>>
>>> Yes, thanks.
>>>
>>>
>>>>   I don=E2=80=99t understand what that means. If you mean to
>>>>>    say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=E2=
=80=99t use =

>>>>> MUST.
>>>>>
>>>>> -5.22, table: "document needs to be referred" (several =

>>>>> repetitions)
>>>>>   I'm not sure what this means. Should it say "Refer to the
>>>>>   specific document"?
>>>>>
>>>>>
>>>>> Similarly as above, would this reprhasing help
>>>>
>>>> "Refer to the document defining specific FEC Scheme
>>>>
>>>>
>>>>
>>> Similarly as above, Yes, thanks. :-)
>>>
>>>
>>>>
>>>>> -6.3: "not clearly defined offer/answer usage"
>>>>>   I'm not sure what is meant here. (Also, why is this not TBD or =

>>>>> NOT
>>>>>   RECOMMENDED?)
>>>>>
>>>>>
>>>> [Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind, =

>>>> either
>>>> the
>>>> BUNDLE spec or this spec cannot define its mux behavior. This is =

>>>> due to
>>>> applicability of these specs under SD{ O/A usages alone.
>>>>
>>>> I can rephrase the above as
>>>> "not defined under SDP Offer/Answer usage"
>>>>
>>>
>>> WFM, thanks.
>>>
>>> [...]
>>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>


From nobody Tue May 24 00:11:46 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF3B12DC7C; Tue, 24 May 2016 00:11:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKgbG_q3rClH; Tue, 24 May 2016 00:11:43 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D315D12D52D; Tue, 24 May 2016 00:11:42 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-97-5743feadb973
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 9A.E7.27088.DAEF3475; Tue, 24 May 2016 09:11:41 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0294.000; Tue, 24 May 2016 09:11:39 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>, Flemming Andreasen <fandreas@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4A=
Date: Tue, 24 May 2016 07:11:39 +0000
Message-ID: <D369D4DC.8E8B%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com>
In-Reply-To: <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <17EAE60A7B51944BA1385FFB1C12D519@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2K7se7af87hBj+v8FkcvLiM1eL9BV2L /YvPM1tMXf6YxYHFY8rvjaweS5b8ZPJoe3aHPYA5issmJTUnsyy1SN8ugSuj/c425oIJ7BVr ut6wNzDeZ+1i5OSQEDCRmN50nxHCFpO4cG89G4gtJHCEUeLYSYkuRi4gewmjxJyHfUAJDg42 AQuJ7n/aIKaIQLDEtQYvkHJmgUKJjzvesIDYwgL2ElcvX2YCsUUEHCR2vr3KAmFbSUz99p4R pJVFQFXixqs8kDAvUHjvtQ9QW/MlDk/eCHYZp4CtxMmlU8EuYwS67PupNUwQq8Qlbj2ZzwRx sYDEkj3nmSFsUYmXj/+B9YoK6Ense3Ee6isliR8bLrFA9OpJ3Jg6hQ3CtpY4f30a1ExtiWUL XzND3CMocXLmE5YJjBKzkKybhaR9FpL2WUjaZyFpX8DIuopRtDi1OCk33chIL7UoM7m4OD9P Ly+1ZBMjMDoPbvltsIPx5XPHQ4wCHIxKPLwJtc7hQqyJZcWVuYcYJTiYlUR4Gb8AhXhTEiur Uovy44tKc1KLDzFKc7AoifP6v1QMFxJITyxJzU5NLUgtgskycXBKNTDGek2U4p3Vca/g6UJZ C4cC0ezjJblvBLvWsS+981ao+NY95oL5DNdOzXOIcP7dteEB46YPZ070zenJ+53g8i9i/YdQ sTcJGU9vLTdO9ec5a/broExmhJLRuoyCfw+epM78+Z5Fset2v5dDcJPUi3oHDQ6rO3cO+/ME ewVOubbfuu1sTKvUo+9KLMUZiYZazEXFiQDsrxV0ygIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/RuYKz61MSCZzq1p9i__hM4xFbOI>
Cc: "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 07:11:44 -0000

Hi,

>4572 forbid the use of MD5 and MD2 in almost all circumstances, by
>forbidding their use in self-signed certs.  By removing the tie between
>the certificate hash algorithm and the fingerprint algorithm, we=B9ve lost
>this requirement.  Should we re-add it?

The old text indicated the impacts on the fingerprints based on the rules
for calculating certificate signatures.

But, is it within the scope of 4572 to define the general rules for
calculating certificate signatures? I assume they are defined somewhere
else, and as they no longer impact the fingerprints we don=B9t need to
include them.=20

>
>SHA-256 is only =B3preferred=B2.  Do we want to make its inclusion mandato=
ry,
>now that we support multiple algorithms?

My suggestion would be to NOT make it mandatory, because that would make
existing endpoints that do not include it non-compliant.

Regards,

Christer


From nobody Tue May 24 03:53:26 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1379F12D8E1 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 03:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ct-xm08NUy0p for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 03:53:24 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD41D12D65F for <mmusic@ietf.org>; Tue, 24 May 2016 03:53:22 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-91-574432a00d26
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 99.FD.18043.0A234475; Tue, 24 May 2016 12:53:21 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0294.000; Tue, 24 May 2016 12:53:19 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: raft-ietf-mmusic-ice-sip-sdp-08.txt: Offer/Answer structure  
Thread-Index: AQHRtap7QluJLF7VRU6TMlH/JyrNug==
Date: Tue, 24 May 2016 10:53:19 +0000
Message-ID: <D36A0DE5.8F82%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_D36A0DE58F82christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42KZGbHdW3ehkUu4QediJoupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEr40rrJvaCPbIV02f3MzcwfpTsYuTkkBAwkTi1/jUjhC0mceHe erYuRi4OIYEjjBKXZ86FcpYwSnROuMXexcjBwSZgIdH9TxukQURAXeLr3h5mEFtYwE1i9p9p jBBxb4lFny6zQNh6Ej+nnQOLswioSixatBoszitgJfH81U0mEJsRaPH3U2vAbGYBcYlbT+Yz QRwkILFkz3lmCFtU4uXjf6wgtijQzH0vzjOCnCMhoCQxbWsaRGu8xO7Hs5ghxgtKnJz5hGUC o/AsJFNnISmbhaQMIm4g8f7cfGYIW1ti2cLXULa+xMYvZxkhbGuJu5/uMiKrWcDIsYpRtDi1 uDg33chIL7UoM7m4OD9PLy+1ZBMjMIIObvlttYPx4HPHQ4wCHIxKPLwJtc7hQqyJZcWVuYcY JTiYlUR44wxdwoV4UxIrq1KL8uOLSnNSiw8xSnOwKInz+r9UDBcSSE8sSc1OTS1ILYLJMnFw SjUwii5TdHUqvnFA7CPbPs7CDeG/wxSWTX/vu+3Q/961p3ZtWLjm1P+83cdcX2tIHTf5dib+ HXf4Eh/76/9ig6uNBBiXBnmVWHG8W9j9nVku9qe/USbrr8WTG9pT9/08bvbAzuS4EzMzV6Bb BWPSsg8btAStbtdnC2/nZTS4cZ9d1Oxf6qnVDOmvlFiKMxINtZiLihMB+CFXbZwCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/z7jk1ebFrjbkbkouJwJGEfyXIOY>
Subject: [MMUSIC] raft-ietf-mmusic-ice-sip-sdp-08.txt: Offer/Answer structure
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 10:53:25 -0000

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

Hi,

I had a look at raft-ietf-mmusic-ice-sip-sdp-08.txt.

I think the O/A parts of the document needs to be re-structured.

For example, you have:

10. Subsequent Offer/Answer Exchanges

=85while the procedures for the initial offer aren't described until:

13.1.1.  Offer in INVITE

In my opinion, we should have the =93traditional=94 "Offer/Answer Considera=
tions section", which describes the initial offer, answer, subsequent offer=
 etc.

Then, in the =93SIP Considerations=94 section, we can describe how offers a=
nd answers are carried in SIP etc.

Regards,

Christer


--_000_D36A0DE58F82christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <AED6B53E38E22747B711C502FE3288B0@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&nbsp;raft-ietf-mmusic-ice-sip-sdp-08.txt.</div>
<div><br>
</div>
<div>I think the O/A parts of the document needs to be re-structured.</div>
<div><br>
</div>
<div>For example, you have:</div>
<div>
<pre style=3D"font-variant-ligatures: normal; font-variant-position: normal=
; font-variant-numeric: normal; font-variant-alternates: normal; font-varia=
nt-east-asian: normal; line-height: normal; widows: 1; word-wrap: break-wor=
d; white-space: pre-wrap;">10. Subsequent Offer/Answer Exchanges</pre>
<pre style=3D"font-variant-ligatures: normal; font-variant-position: normal=
; font-variant-numeric: normal; font-variant-alternates: normal; font-varia=
nt-east-asian: normal; line-height: normal; widows: 1; word-wrap: break-wor=
d; white-space: pre-wrap;"><div style=3D"font-family: Calibri, sans-serif; =
white-space: normal; widows: auto;">=85while the procedures for the&nbsp;<s=
pan style=3D"font-weight: bold;">initial</span>&nbsp;offer aren't described=
 until:</div><div style=3D"font-family: Calibri, sans-serif; white-space: n=
ormal; widows: auto;"><pre style=3D"font-variant-ligatures: normal; font-va=
riant-position: normal; font-variant-numeric: normal; font-variant-alternat=
es: normal; font-variant-east-asian: normal; line-height: normal; widows: 1=
; word-wrap: break-word; white-space: pre-wrap;">13.1.1.  Offer in INVITE</=
pre></div><div><div style=3D"font-family: Calibri, sans-serif; white-space:=
 normal; widows: auto;">In my opinion, we should have the =93traditional=94=
 &quot;Offer/Answer Considerations section&quot;, which describes the initi=
al offer, answer, subsequent offer etc.</div></div><div style=3D"font-famil=
y: Calibri, sans-serif; white-space: normal; widows: auto;"><br></div><div =
style=3D"font-family: Calibri, sans-serif; white-space: normal; widows: aut=
o;">Then, in the =93SIP Considerations=94 section, we can describe how offe=
rs and answers are carried in SIP etc.</div><div style=3D"font-family: Cali=
bri, sans-serif; white-space: normal; widows: auto;"><br></div><div style=
=3D"font-family: Calibri, sans-serif; white-space: normal; widows: auto;">R=
egards,</div><div style=3D"font-family: Calibri, sans-serif; white-space: n=
ormal; widows: auto;"><br></div><div style=3D"font-family: Calibri, sans-se=
rif; white-space: normal; widows: auto;">Christer</div><div><br></div></pre=
>
</div>
</body>
</html>

--_000_D36A0DE58F82christerholmbergericssoncom_--


From nobody Tue May 24 04:44:32 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D972812D61C for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 04:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h_Y7c1BZ5QXZ for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 04:44:29 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03FF312D125 for <mmusic@ietf.org>; Tue, 24 May 2016 04:44:26 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-95-57443e993dfa
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 8D.57.27088.99E34475; Tue, 24 May 2016 13:44:25 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0294.000; Tue, 24 May 2016 13:44:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] raft-ietf-mmusic-ice-sip-sdp-08.txt: Offer/Answer structure
Thread-Index: AQHRtbGbKfZ8HAC5iEeTUMAbHOdMrw==
Date: Tue, 24 May 2016 11:44:19 +0000
Message-ID: <D36A19A4.8F8F%christer.holmberg@ericsson.com>
References: <D36A0DE5.8F82%christer.holmberg@ericsson.com>
In-Reply-To: <D36A0DE5.8F82%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D36A19A48F8Fchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7t+5MO5dwg/3XhSymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujGOtW1kLbutW7Hy/jrmBcbJGFyMnh4SAicT5L2fYIWwxiQv3 1rN1MXJxCAkcYZSYf+MCC0hCSGAJo8TfN9VdjBwcbAIWEt3/tEHCIgLqEl/39jCD2MICwRJX zz1mBCkREQiR2H0sFaJET2J/x3RWEJtFQFXi6t4pYKt4BawkOq6egJpuJdH19zBYnFPAWuJ5 70w2EJsR6Jzvp9YwgdjMAuISt57MZ4I4U0BiyZ7zzBC2qMTLx//A5osC7dr34jzYCRICihLL ++UgWuMlplw/wQaxVlDi5MwnLBMYRWchmToLSdksJGUQcQOJ9+fmM0PY2hLLFr6GsvUlNn45 yzgLaBsz0NXHz1ogK1nAyLGKUbQ4tTgpN93ISC+1KDO5uDg/Ty8vtWQTIzDWDm75bbCD8eVz x0OMAhyMSjy8CbXO4UKsiWXFlbmHGCU4mJVEeOfbuIQL8aYkVlalFuXHF5XmpBYfYpTmYFES 5/V/qRguJJCeWJKanZpakFoEk2Xi4JRqYPRN2xwsp1McYd6ne5Bts0JQ9uRDnt9ttmiv+Xcu MjfTeH6dwSIT4eUVK6p27Vp94WHD5Wd8S1lrK7U747afbX/2/tK7vLsNJgycZ8N9OjOqLE0j Q5+VeATvWpp0je/ftn+my6ZduyqxWtmN9e4UpUX3nLb0u/E9c3iw/f4Fw5r57ufO2xq1/VNi Kc5INNRiLipOBACot9z1sQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/yvMMNIt5yXW8PTtxKA-yOc-KfxU>
Subject: Re: [MMUSIC] raft-ietf-mmusic-ice-sip-sdp-08.txt: Offer/Answer structure
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 11:44:31 -0000

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

Ok, so I see that sections 4,5 and 6 describe the initial O/A transaction.

But, never the less, I think it should be within one main section.

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Tuesday 24 May 2016 at 13:53
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] raft-ietf-mmusic-ice-sip-sdp-08.txt: Offer/Answer structu=
re

Hi,

I had a look at raft-ietf-mmusic-ice-sip-sdp-08.txt.

I think the O/A parts of the document needs to be re-structured.

For example, you have:

10. Subsequent Offer/Answer Exchanges

=85while the procedures for the initial offer aren't described until:

13.1.1.  Offer in INVITE

In my opinion, we should have the =93traditional=94 "Offer/Answer Considera=
tions section", which describes the initial offer, answer, subsequent offer=
 etc.

Then, in the =93SIP Considerations=94 section, we can describe how offers a=
nd answers are carried in SIP etc.

Regards,

Christer


--_000_D36A19A48F8Fchristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <99B0CC259BA08C46AA58242081826449@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>Ok, so I see that sections 4,5 and 6 describe the initial O/A transact=
ion.</div>
<div><br>
</div>
<div>But, never the less, I think it should be within one main section.</di=
v>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday 24 May 2016 at 13:53<=
br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] raft-ietf-mmusic-=
ice-sip-sdp-08.txt: Offer/Answer structure<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>I had a look at&nbsp;raft-ietf-mmusic-ice-sip-sdp-08.txt.</div>
<div><br>
</div>
<div>I think the O/A parts of the document needs to be re-structured.</div>
<div><br>
</div>
<div>For example, you have:</div>
<div>
<pre style=3D"font-variant-ligatures: normal; font-variant-position: normal=
; font-variant-numeric: normal; font-variant-alternates: normal; font-varia=
nt-east-asian: normal; line-height: normal; widows: 1; word-wrap: break-wor=
d; white-space: pre-wrap;">10. Subsequent Offer/Answer Exchanges</pre>
<pre style=3D"font-variant-ligatures: normal; font-variant-position: normal=
; font-variant-numeric: normal; font-variant-alternates: normal; font-varia=
nt-east-asian: normal; line-height: normal; widows: 1; word-wrap: break-wor=
d; white-space: pre-wrap;"><div style=3D"font-family: Calibri, sans-serif; =
white-space: normal; widows: auto;">=85while the procedures for the&nbsp;<s=
pan style=3D"font-weight: bold;">initial</span>&nbsp;offer aren't described=
 until:</div><div style=3D"font-family: Calibri, sans-serif; white-space: n=
ormal; widows: auto;"><pre style=3D"font-variant-ligatures: normal; font-va=
riant-position: normal; font-variant-numeric: normal; font-variant-alternat=
es: normal; font-variant-east-asian: normal; line-height: normal; widows: 1=
; word-wrap: break-word; white-space: pre-wrap;">13.1.1.  Offer in INVITE</=
pre></div><div><div style=3D"font-family: Calibri, sans-serif; white-space:=
 normal; widows: auto;">In my opinion, we should have the =93traditional=94=
 &quot;Offer/Answer Considerations section&quot;, which describes the initi=
al offer, answer, subsequent offer etc.</div></div><div style=3D"font-famil=
y: Calibri, sans-serif; white-space: normal; widows: auto;"><br></div><div =
style=3D"font-family: Calibri, sans-serif; white-space: normal; widows: aut=
o;">Then, in the =93SIP Considerations=94 section, we can describe how offe=
rs and answers are carried in SIP etc.</div><div style=3D"font-family: Cali=
bri, sans-serif; white-space: normal; widows: auto;"><br></div><div style=
=3D"font-family: Calibri, sans-serif; white-space: normal; widows: auto;">R=
egards,</div><div style=3D"font-family: Calibri, sans-serif; white-space: n=
ormal; widows: auto;"><br></div><div style=3D"font-family: Calibri, sans-se=
rif; white-space: normal; widows: auto;">Christer</div><div><br></div></pre=
>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D36A19A48F8Fchristerholmbergericssoncom_--


From nobody Tue May 24 05:42:41 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2308A12D6C1 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 05:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GexEoSwo6VmV for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 05:42:37 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71EB112D6B5 for <mmusic@ietf.org>; Tue, 24 May 2016 05:42:14 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-d4-57444c231af1
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id BE.34.27088.32C44475; Tue, 24 May 2016 14:42:11 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0294.000; Tue, 24 May 2016 14:42:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: INFO vs peer reflexive when remote peer is ice-lite?
Thread-Index: AQHRtbmw/rS/ypNB9Eav0vNHWhvTrQ==
Date: Tue, 24 May 2016 12:42:11 +0000
Message-ID: <D36A2767.8FD3%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_D36A27678FD3christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnkeLIzCtJLcpLzFFi42KZGbE9UFfZxyXc4OIxA4upyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEro7v/AmPBN56Kh/d2MjcwTuDuYuTgkBAwkbi7j6uLkRPIFJO4 cG89G4gtJHCEUeL5E/YuRi4gewmjRN/Bf+wg9WwCFhLd/7RBakQE1CW+7u1hBrGFBWwlpk++ yQgRd5I4+fcdC4StJ3Hg8EOwOIuAqsT3wwdZQcbwClhJTJgVCRJmBFr7/dQaJhCbWUBc4taT +UwQ5whILNlznhnCFpV4+fgfK4gtCjRy34vzjBBxRYmdZ9uZIXrjJVomb2cHsXkFBCVOznzC MoFReBaSsbOQlM1CUgYRN5B4f24+M4StLbFs4WsoW19i45ezjBC2tcTrz3tZkNUsYORYxSha nFqclJtuZKSXWpSZXFycn6eXl1qyiREYPQe3/DbYwfjyueMhRgEORiUe3oRa53Ah1sSy4src Q4wSHMxKIry3vFzChXhTEiurUovy44tKc1KLDzFKc7AoifP6v1QMFxJITyxJzU5NLUgtgsky cXBKNTAGXN//8kFzf9nafatSW4OYI7TfaLea3HMuUKz9l7S7KX1NbXKm7dQqG+NwIzMF7jZJ 6Ut7nj138l2z8KGznOzP+Q6Ts3hfpEw86HPhi9eVrry7YuZ5vyVe8DSUBLm4X4qS2vX86snm iy4/eGffsHabvzZh1t8jDyIZ+Rjz1xVsXXD38iy72NNKLMUZiYZazEXFiQC8rT60mgIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/cuwl9po5i1hNpW0H7lUrEMth1R4>
Subject: [MMUSIC] INFO vs peer reflexive when remote peer is ice-lite?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 12:42:38 -0000

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

Hi,

Trickled ICE candidates are =93comparable=94 to peer reflexive candidates.

My question: if the remote peer is ice-lite, what advantage is there to tri=
ckle candidates using INFO? Why not simply send them as =93real=94 peer ref=
lexive candidates?

If there is a good reason, I think it should be documented in draft-ietf-mm=
usic-trickle-ice-sip.

Regards,

Christer

--_000_D36A27678FD3christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <B4723DDCA635F14DBB981F5852CA0E4D@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>Trickled ICE candidates are =93comparable=94 to peer reflexive candida=
tes.</div>
<div><br>
</div>
<div>My question: if the remote peer is ice-lite, what advantage is there t=
o trickle candidates using INFO? Why not simply send them as =93real=94 pee=
r reflexive candidates?</div>
<div><br>
</div>
<div>If there is a good reason, I think it should be documented in&nbsp;dra=
ft-ietf-mmusic-trickle-ice-sip.</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
</body>
</html>

--_000_D36A27678FD3christerholmbergericssoncom_--


From nobody Tue May 24 09:10:59 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B181012D0EC; Tue, 24 May 2016 09:10:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i51LlUfI4ldm; Tue, 24 May 2016 09:10:52 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65DE112D0A2; Tue, 24 May 2016 09:10:52 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id p64so15123636ioi.2; Tue, 24 May 2016 09:10:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=whXXkfHjEmlUu83IP6ZzeQ+yGQ2z7HGHCfODsbfsyhU=; b=cJFLopu1lFE3vB38cZDCMeRCZ2Ts75Ix+NnUXjnMC+FG7SkfFZYHiyfz/zC9L2fB78 /0scOhG6lgZwO2vCQ+O/JeJaI2qtJnqHsyFex9HypmTG3FCYU2WdToINFPG2RGZL5zBD XdPA7ftRQ0N5JqFV3RDohnyi5etCe118M/RIERli+CEFjrNg/Jho1ar+SCSi7djeJf7Z 00zwS4CDOmv+ScBEKO7jUl9/LXJ4fhOfO8c8/i9+rYX2Wuh3vxDJYo5aH57SYvVpQ5Xm Y1gcmUMCqA+t9/cknBBNzGTn5Sw88VU+R7/zdSo5Rd3sdaxwBBC2ppiVqntDUhiqSuR8 ra9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=whXXkfHjEmlUu83IP6ZzeQ+yGQ2z7HGHCfODsbfsyhU=; b=irBydT6Cf3SrHyp1RVzRkEywJOKarqTJxwRfTdpS8lyzLngiZrmxi+aIO3FgCF0fbN vynuxDevUVeX0b5jO1+8aCfnVIbkF92M9u3yibCqUTFX5HVYshVuSL3TGpsYhr+5PRGJ hCgma+Uaw8V8H1ZkTwcLh8ThTXre5+L+VyGG8QdHQPXNqJasi9axZ2tRdR/TP+f4I6Cp 3grfnjSv1vvfn9r9M0ATjO//hkosxjeF6aztJY4lj0E0nYj12SDqQEmHbFHN/qCCjv/c 6v1/wabpC7cktnAeV0l9hf4BcCXOCUpOF3rRLBysbv9h3TExaX2Kvad11uhFcxh6nrCY U5HQ==
X-Gm-Message-State: ALyK8tIXoqtqjknUf4h0C0nSetVI0t8ym937aAogcmA9G94Ky1FdDIiPBdgLnAwyRt6VeAy3w0RwY8qW1lY6yw==
MIME-Version: 1.0
X-Received: by 10.107.136.106 with SMTP id k103mr2800809iod.100.1464106251315;  Tue, 24 May 2016 09:10:51 -0700 (PDT)
Received: by 10.36.43.23 with HTTP; Tue, 24 May 2016 09:10:51 -0700 (PDT)
In-Reply-To: <D369D4DC.8E8B%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com>
Date: Tue, 24 May 2016 09:10:51 -0700
Message-ID: <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/dwlWkWj4D4V9PPoNitio9LBgS9E>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 16:10:58 -0000

On 24 May 2016 at 00:11, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> But, is it within the scope of 4572 to define the general rules for
> calculating certificate signatures? I assume they are defined somewhere
> else, and as they no longer impact the fingerprints we don=C2=B9t need to
> include them.

I don't think that is Jonathan's point.  The point is that we no
longer have text that expressly forbids bad hashes (to which I would -
carefully - add SHA-1).  Something like:

    [...] the
    defined hash functions are 'SHA-1' [11] [19], 'SHA-224' [11],
    'SHA-256' [11], 'SHA-384' [11], 'SHA-512' [11], 'MD5' [12], and
    'MD2' [13].  Implementations MUST provide and validate 'SHA-256'.
    The 'MD5', and 'MD2' functions are considered weak and MUST NOT be
used.  Though 'SHA-1' is also considered weak, it MAY be used to
retain compatibility with existing implementations.

I think that this captures the intent: if you implement this update,
you will use SHA-256.  However, we concede that you will have to
include SHA-1 and verify fingerprints based on it because there is no
other way to talk to implementations that haven't implemented this
update.

I agree that we shouldn't say anything about the signature in the
certificate.  It doesn't help at all.

>>SHA-256 is only =C2=B3preferred=C2=B2.  Do we want to make its inclusion =
mandatory,
>>now that we support multiple algorithms?
>
> My suggestion would be to NOT make it mandatory, because that would make
> existing endpoints that do not include it non-compliant.

MUST and MUST NOT are our best tools here for encouraging people to
fix their software.  Existing implementations will be non-compliant
with that spec, but if that provides them a little incentive to
upgrade, then that is good.  They will, of course, remain compliant
with 4572.


From nobody Tue May 24 09:16:55 2016
Return-Path: <prvs=995237461a=jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2960912D0CB; Tue, 24 May 2016 09:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 wlF9WCQH36Lu; Tue, 24 May 2016 09:16:52 -0700 (PDT)
Received: from mx0a-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.202]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECC3412B030; Tue, 24 May 2016 09:16:51 -0700 (PDT)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.15.0.59/8.15.0.59) with SMTP id u4OGEmUW020411; Tue, 24 May 2016 12:16:47 -0400
Received: from mail.vidyo.com ([162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 232hrg1wgc-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 24 May 2016 12:16:47 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Tue, 24 May 2016 11:16:46 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtTIaQis2k/N4/0eW1holrCy8CJ/HTqoAgACxy4CAAJangIAAAaQA
Date: Tue, 24 May 2016 16:16:45 +0000
Message-ID: <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com>
In-Reply-To: <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.220.24]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6BC929F1C16B5C48BDE5F1C744301E7A@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.15.96, 1.0.3, 0.0.0000 definitions=2016-05-24_07:2016-05-24,2016-05-24,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1603290000 definitions=main-1605240193
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/pRy1xjh7X4TKcl0MME-qNgWTQtA>
Cc: Flemming Andreasen <fandreas@cisco.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 16:16:53 -0000

KzEgdG8gYWxsIHRoaXMg4oCUIE1hcnRpbiBjYXB0dXJlcyAoYW5kIGFkZHJlc3NlcykgbXkgY29t
bWVudHMgcGVyZmVjdGx5Lg0KDQo+IE9uIE1heSAyNCwgMjAxNiwgYXQgMTI6MTAgUE0sIE1hcnRp
biBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+IHdyb3RlOg0KPiANCj4gT24gMjQg
TWF5IDIwMTYgYXQgMDA6MTEsIENocmlzdGVyIEhvbG1iZXJnDQo+IDxjaHJpc3Rlci5ob2xtYmVy
Z0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KPj4gQnV0LCBpcyBpdCB3aXRoaW4gdGhlIHNjb3BlIG9m
IDQ1NzIgdG8gZGVmaW5lIHRoZSBnZW5lcmFsIHJ1bGVzIGZvcg0KPj4gY2FsY3VsYXRpbmcgY2Vy
dGlmaWNhdGUgc2lnbmF0dXJlcz8gSSBhc3N1bWUgdGhleSBhcmUgZGVmaW5lZCBzb21ld2hlcmUN
Cj4+IGVsc2UsIGFuZCBhcyB0aGV5IG5vIGxvbmdlciBpbXBhY3QgdGhlIGZpbmdlcnByaW50cyB3
ZSBkb27CuXQgbmVlZCB0bw0KPj4gaW5jbHVkZSB0aGVtLg0KPiANCj4gSSBkb24ndCB0aGluayB0
aGF0IGlzIEpvbmF0aGFuJ3MgcG9pbnQuICBUaGUgcG9pbnQgaXMgdGhhdCB3ZSBubw0KPiBsb25n
ZXIgaGF2ZSB0ZXh0IHRoYXQgZXhwcmVzc2x5IGZvcmJpZHMgYmFkIGhhc2hlcyAodG8gd2hpY2gg
SSB3b3VsZCAtDQo+IGNhcmVmdWxseSAtIGFkZCBTSEEtMSkuICBTb21ldGhpbmcgbGlrZToNCj4g
DQo+ICAgIFsuLi5dIHRoZQ0KPiAgICBkZWZpbmVkIGhhc2ggZnVuY3Rpb25zIGFyZSAnU0hBLTEn
IFsxMV0gWzE5XSwgJ1NIQS0yMjQnIFsxMV0sDQo+ICAgICdTSEEtMjU2JyBbMTFdLCAnU0hBLTM4
NCcgWzExXSwgJ1NIQS01MTInIFsxMV0sICdNRDUnIFsxMl0sIGFuZA0KPiAgICAnTUQyJyBbMTNd
LiAgSW1wbGVtZW50YXRpb25zIE1VU1QgcHJvdmlkZSBhbmQgdmFsaWRhdGUgJ1NIQS0yNTYnLg0K
PiAgICBUaGUgJ01ENScsIGFuZCAnTUQyJyBmdW5jdGlvbnMgYXJlIGNvbnNpZGVyZWQgd2VhayBh
bmQgTVVTVCBOT1QgYmUNCj4gdXNlZC4gIFRob3VnaCAnU0hBLTEnIGlzIGFsc28gY29uc2lkZXJl
ZCB3ZWFrLCBpdCBNQVkgYmUgdXNlZCB0bw0KPiByZXRhaW4gY29tcGF0aWJpbGl0eSB3aXRoIGV4
aXN0aW5nIGltcGxlbWVudGF0aW9ucy4NCj4gDQo+IEkgdGhpbmsgdGhhdCB0aGlzIGNhcHR1cmVz
IHRoZSBpbnRlbnQ6IGlmIHlvdSBpbXBsZW1lbnQgdGhpcyB1cGRhdGUsDQo+IHlvdSB3aWxsIHVz
ZSBTSEEtMjU2LiAgSG93ZXZlciwgd2UgY29uY2VkZSB0aGF0IHlvdSB3aWxsIGhhdmUgdG8NCj4g
aW5jbHVkZSBTSEEtMSBhbmQgdmVyaWZ5IGZpbmdlcnByaW50cyBiYXNlZCBvbiBpdCBiZWNhdXNl
IHRoZXJlIGlzIG5vDQo+IG90aGVyIHdheSB0byB0YWxrIHRvIGltcGxlbWVudGF0aW9ucyB0aGF0
IGhhdmVuJ3QgaW1wbGVtZW50ZWQgdGhpcw0KPiB1cGRhdGUuDQo+IA0KPiBJIGFncmVlIHRoYXQg
d2Ugc2hvdWxkbid0IHNheSBhbnl0aGluZyBhYm91dCB0aGUgc2lnbmF0dXJlIGluIHRoZQ0KPiBj
ZXJ0aWZpY2F0ZS4gIEl0IGRvZXNuJ3QgaGVscCBhdCBhbGwuDQo+IA0KPj4+IFNIQS0yNTYgaXMg
b25seSDCs3ByZWZlcnJlZMKyLiAgRG8gd2Ugd2FudCB0byBtYWtlIGl0cyBpbmNsdXNpb24gbWFu
ZGF0b3J5LA0KPj4+IG5vdyB0aGF0IHdlIHN1cHBvcnQgbXVsdGlwbGUgYWxnb3JpdGhtcz8NCj4+
IA0KPj4gTXkgc3VnZ2VzdGlvbiB3b3VsZCBiZSB0byBOT1QgbWFrZSBpdCBtYW5kYXRvcnksIGJl
Y2F1c2UgdGhhdCB3b3VsZCBtYWtlDQo+PiBleGlzdGluZyBlbmRwb2ludHMgdGhhdCBkbyBub3Qg
aW5jbHVkZSBpdCBub24tY29tcGxpYW50Lg0KPiANCj4gTVVTVCBhbmQgTVVTVCBOT1QgYXJlIG91
ciBiZXN0IHRvb2xzIGhlcmUgZm9yIGVuY291cmFnaW5nIHBlb3BsZSB0bw0KPiBmaXggdGhlaXIg
c29mdHdhcmUuICBFeGlzdGluZyBpbXBsZW1lbnRhdGlvbnMgd2lsbCBiZSBub24tY29tcGxpYW50
DQo+IHdpdGggdGhhdCBzcGVjLCBidXQgaWYgdGhhdCBwcm92aWRlcyB0aGVtIGEgbGl0dGxlIGlu
Y2VudGl2ZSB0bw0KPiB1cGdyYWRlLCB0aGVuIHRoYXQgaXMgZ29vZC4gIFRoZXkgd2lsbCwgb2Yg
Y291cnNlLCByZW1haW4gY29tcGxpYW50DQo+IHdpdGggNDU3Mi4NCg0K


From nobody Tue May 24 09:53:00 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED6812D8E0 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 09:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMpCKRRySsSx for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 09:52:24 -0700 (PDT)
Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0F8D12D8E7 for <mmusic@ietf.org>; Tue, 24 May 2016 09:51:33 -0700 (PDT)
Received: from resomta-po-09v.sys.comcast.net ([96.114.154.233]) by comcast with SMTP id 5FLbbsgTTd8265FMXb30Gz; Tue, 24 May 2016 16:39:21 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464107961; bh=pbjFNkbrL8qRDBZfV/HE2fTxAzbQHjldz8bLz99SKoc=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=gap1ozBTa6LpQdXtHJih7Ql5yOZ/tB0InXmys8I/GWrg7rkiyQyuCQX+INkcXifaA eHNIudHZjL8LbbcdhMeBoaH/naVCp3ChFJgYN/l6xUvBMCH8Zz1OEq2JsVRrFF1qhE 6kY+Ax1Qn8l6EgcX6FpAwc0vtfJ3u4gLYvgaiEYTz3QIEo6N95cfYBFUP4QETv3IhP JTx4UWUPidDBq+Ueuy8hwD8TZcsWT6SGhwjRC9T5gOzWuoosEAmgoe+GJ+HaA/NeBT vsVcx4dMqhtEsm5+KrwKtDpwdfx7OX17GexB/SkUqeWw2f7hTJqTX3a8Sqk7OYp2dH rjWOLz/2FHQKg==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-po-09v.sys.comcast.net with comcast id yGfL1s01Z3KdFy101GfLgE; Tue, 24 May 2016 16:39:21 +0000
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu>
Date: Tue, 24 May 2016 12:39:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/uhiulAHQCwYZaa4frm5URa0csZE>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 16:52:27 -0000

On 5/21/16 12:02 PM, Christer Holmberg wrote:
> Hi,
>
> I’ve submitted a new version (-12) of draft-ietf-mmusic-dtls-sdp.

This generally seems good.

> The new version contains some additional restrictions regarding the
> establishment of a new DTLS association.

I have a slight issue with how this was done. In section 5.1 is the 
following new text:

    When an answerer needs to establish a new DTLS association, if
    unreliable transport is used, and if the offerer did not allocate a
    new transport, the answerer MUST allocate a new transport for the
    offer in answer a way that it can disambiguate any packets associated
    with new DTLS association from any packets associated with any other
    DTLS association.  This typically means using a local address and or
    port, or a set of ICE candidates (see Section 6), which were not
    recently used for any other DTLS association.

I agree with the point of this, but the qualifier "if unreliable 
transport is used" doesn't seem to be the right one. I don't think the 
issue has anything to do with unreliability. For instance I don't think 
it would apply if using unreliable SCTP streams. I think the real issue 
is that UDP is not a connection-oriented transport.

I'm not sure what language to use here that would cover the *right* 
other non-UDP protocols. (AFAIK there are none that qualify.) If you 
can't come up with something I guess I would make this UDP-specific.

Note there is similar text with the same problem in Section 6.

	Thanks,
	Paul



From nobody Tue May 24 10:03:59 2016
Return-Path: <alan.b.johnston@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 761B412D147; Tue, 24 May 2016 10:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bv_tiyjyYOe6; Tue, 24 May 2016 10:03:53 -0700 (PDT)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C12312D910; Tue, 24 May 2016 10:03:50 -0700 (PDT)
Received: by mail-qg0-x22e.google.com with SMTP id f92so10180292qgf.0; Tue, 24 May 2016 10:03:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=02gqi+r5jdB9mE+2DEB3zVIIf35rZBPgG5CxPgR26CY=; b=khn9C0ZJVRHOofc+LLAkaEik6fPyfa/fBd/cHyPd076DKD5pAy1tL40wBWkjhwR8/w yfM7sRXWrQHLxFKY2W5GngRHtGmeuIKDH+x1ymk82x36qVS6+uFoAOjdPCORuaqpzTpX +psKvQAXG5sYHrdqBQijrHhNntjBgPlxJc1b5bNeMtRHsT016difp1DT93jlHKlYKl/C QaGI7Rglahv8z3ub6pkBtGbKjTafSO04o5ELXDDcXgNtDxb20hbn1HBzwv93S5tyIVw5 8+WBd4P3PeW2Wuo4TcKUABxcAikfu3vUrOpt2CLE3Ack5TmhgwsQBLgnZZWh/M7C34TY xSTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=02gqi+r5jdB9mE+2DEB3zVIIf35rZBPgG5CxPgR26CY=; b=j8bv4srvMYQyDn385kFG9LbtdIoRD72qf4LLTd11pGie7nth14v6ORI/AWP+vEtgd8 OucGM6af5NiKz01PIz7DqWP47QDKNa7reuPM/F3Uor24fE/gdQv27cfIfzg97pXdORA4 rgplvAWUK2OcRFkAHok7/v5LWTK6LXZVz295gHYxlYjV6JPlDzFZJdCNgYvbNfUYYBqP fv+Krk422ddq2DPo/mdCUqvkK8SP2KpYWLG4Me1aXQPN6WA52W9lamYWWrf9Xmb8xnKE CqqSX9LRvHEIgXaaBZznPlmbYe7GKB+x1fNms38oQ4k2np08aVabNHP5qAkKP6vv4CsT Q1Wg==
X-Gm-Message-State: ALyK8tL6JO/zlKGsx2hHkYMAs4soRUEa2K79OeU/Yi/HK3L4AL+/4X1hTTjoh4aKdGb+oiwdv7/HaYuhTO3Ynw==
MIME-Version: 1.0
X-Received: by 10.140.201.143 with SMTP id w137mr4428140qha.66.1464109429143;  Tue, 24 May 2016 10:03:49 -0700 (PDT)
Received: by 10.55.185.70 with HTTP; Tue, 24 May 2016 10:03:49 -0700 (PDT)
In-Reply-To: <66ECA4FB-729F-421B-8CD7-C87E6FD248F0@nostrum.com>
References: <ED0991AE-DF16-4D42-9130-A2B42C4677A1@nostrum.com> <CAKhHsXFybXGPjF-pQuJ7ctyq5qc8JYdgi9ctpTghpFbuOS4B2w@mail.gmail.com> <66ECA4FB-729F-421B-8CD7-C87E6FD248F0@nostrum.com>
Date: Tue, 24 May 2016 10:03:49 -0700
Message-ID: <CAKhHsXHpN=c9K4e2e9hLWDd6xmkwT-243N_8iL_xxkLUqcByMw@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001a114267666fc2c60533998a4d
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/W1bUjZZ70bg5LQ4E3GVsZBa7u3I>
Cc: mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Subject: Re: [MMUSIC] zrtp-hash (was Re: AD Evaluation of draft-ietf-mmusic-sdp-mux-attributes-12)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 17:03:57 -0000

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

Hi Ben,

What you say makes sense to me.  Adding ZRTP guidance to 5764-mux-fixes
seems like a reasonable solution to me.

- Alan -

On Mon, May 23, 2016 at 4:12 PM, Ben Campbell <ben@nostrum.com> wrote:

> Hi Alan,
>
> If I read RFC 6189 correctly, I see that it documents how to distinguish
> zrtp messages from rtp and stun. Further, it distinguishes itself from st=
un
> by using a different magic cookie value. That's a little more complex tha=
n
> the first-byte demuxing in 5764--although it looks like first-byte demuxi=
ng
> might work as long as we don't end up with a conflicting stun method. (I'=
m
> also not certain that the average 5764 implementation is going to look at
> the cookie to make the demux decision.)
>
> I don't see anything in 6189 about distinguishing itself from DTLS. Again=
,
> we can infer that from the first byte, as long as we don't get a
> conflicting tls content-type.
>
> This doesn't quite seem (to me) to meet the following requirement in
> draft-ietf-mmusic-sdp-bundle-negotiation (emphasis mine):
>
>   "If bundled "m=3D" lines use different protocols on top
>    of the transport-layer protocol,  there MUST exist a publicly
>    available specification which describes a mechanism, for **this
>    particular protocol combination**, how to associate received data with
>    the correct protocol."
>
> As mentioned, one way to fix that could be to add zrtp into the general
> guidance in 5764-mux-fixes.
>
> Thanks,
>
> Ben.
>
>
> On 23 May 2016, at 17:48, Alan Johnston wrote:
>
> Hi Ben,
>>
>> The a=3Dzrtp-hash attribute is a hash of the ZRTP Hello message that is
>> going
>> to be sent over the transport.  There is one ZRTP Hello sent per
>> transport,
>> and one handshake per transport.
>>
>> The ZRTP message format was carefully crafted in association with
>> DTLS-SRTP, so if draft-ietf-avtcore-rfc5764-mux-fixes breaks this, then =
it
>> probably should be fixed.
>>
>> - Alan -
>>
>> On Mon, May 23, 2016 at 3:34 PM, Ben Campbell <ben@nostrum.com> wrote:
>>
>> Hi,
>>>
>>> As promised, here's more on my concern about zrtp-hash in
>>> draft-ietf-mmusic-sdp-mux-attributes:
>>>
>>> I think you need to describe the assumptions about what it means to
>>> multiplex zrtp. Am I correct to assume that the draft assumes that ther=
e
>>> is
>>> only one zrtp session in a transport flow, with a single zrtp handshake=
?
>>> And that all of the bundled m=3Dlines represent media that is part of t=
hat
>>> zrtp association? (That is, you never mux distinct zrtp associations, o=
r
>>> zrtp and dtls-srtp?)
>>>
>>> If the answer is yes, then "transport" seems to make sense.
>>>
>>> But is zrtp demuxing really well defined enough to keep this out of the
>>> "NOT RECOMMENDED" category? I'm not sure it meets the bundle requiremen=
t
>>> for a public spec on how to demux it. One might infer that from two
>>> public
>>> specs (zrtp and 5764), but IIUC, the guidance proposed in
>>> draft-ietf-avtcore-rfc5764-mux-fixes would cause a zrtp messages to be
>>> dropped, since its first byte would not match any of the demux rules. O=
r,
>>> if zrtp-hash is allowed, does mux-fixes need to change?
>>>
>>> What am I missing?
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>>
>>> On 20 May 2016, at 18:07, Ben Campbell wrote:
>>>
>>> Apologies for my slow response. The last month has been a perfect storm
>>> of
>>>
>>>> productivity killers. I'm digging out of the backlog now. Comments
>>>> inline,
>>>> with sections that appear resolved removed.
>>>>
>>>> There is one issue (zrtp-hash) where I will start a separate thread
>>>> shortly.
>>>>
>>>> Thanks!
>>>>
>>>> Ben.
>>>>
>>>> On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:
>>>>
>>>> Hello Ben
>>>>
>>>>>
>>>>>  Sorry for the delay in responding. Many thanks for the detailed
>>>>> review.
>>>>>
>>>>>  Please find my responses inline (marked by [Suhas]).
>>>>>
>>>>> Cheers
>>>>> Suhas
>>>>>
>>>>> On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell <ben@nostrum.com> wrote=
:
>>>>>
>>>>> Hi,
>>>>>
>>>>>>
>>>>>> Here is my AD evaluation of draft-ietf-mmusic-sdp-mux-attributes-12.=
 I
>>>>>> would like at least the substantive
>>>>>> section to be discussed before going to IETF last call.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Ben.
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>> # Substantive #
>>>>>>
>>>>>> - This is very long and detailed. Are the authors and chairs
>>>>>> comfortable
>>>>>> that all sections have had sufficient review?
>>>>>>
>>>>>> -4.0: It would be helpful to add a paragraph describing how these
>>>>>> semantic
>>>>>> groupings map to the categories.
>>>>>>
>>>>>>
>>>>>> [Suhas] The semantic groupings were added as a informal reference an=
d
>>>>> they
>>>>> don't really interact with the categories as such.
>>>>>
>>>>>
>>>> So I have to wonder why we have the groupings. But I guess at this poi=
nt
>>>> in the process, it's not worth changing that.
>>>>
>>>>
>>>> Does the following rephrasing work
>>>>>
>>>>> *"Attributes in an SDP session description can be defined at the
>>>>> **session-level
>>>>> or  media-level or  source-level. Informally, there are various
>>>>> semantic
>>>>> grouping for these attributes. One such grouping could be as noted
>>>>> below:*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> *   o  Attributes related to media content such as media type, encodi=
ng
>>>>>      schemes, payload types.   o  Attributes specifying media transpo=
rt
>>>>> characteristics like RTP/RTP      Control Protocol (RTCP) port number=
s,
>>>>> network addresses, QOS.   o  Metadata description attributes capturin=
g
>>>>> session timing and      origin information.   o  Attributes
>>>>> establishing
>>>>> relationships between media descriptions      such as grouping
>>>>> framework
>>>>> [RFC5888 <https://tools.ietf.org/html/rfc5888>]The proposed framework
>>>>> defines categories for the SDP attributes under multiplexing and
>>>>> assigns
>>>>> each SDP attribute to an appropriate multiplexing category.*
>>>>>
>>>>> *Since the multiplexing categories defined in this specification are
>>>>> independent of any informal semantic grouping of the SDP attributes,
>>>>> the
>>>>> categorizations assigned against each attribute  MUST be considered a=
s
>>>>> normative assignments under multiplexing. "*
>>>>>
>>>>>
>>>> All fine, except the last sentence is pretty meta--it uses normative
>>>> language to talk about normative language ("MUST be considered
>>>> normative").
>>>> I'm not entirely sure what you intend there, but how about something t=
o
>>>> the
>>>> effect of "... the categorizations assigned against each attribute are
>>>> normative."
>>>>
>>>>
>>>>
>>>>>
>>>>> -4.2: I recommend choosing a category name that is not a 2119 keyword=
.
>>>>>
>>>>>>   Maybe something like "not mux-able" or "unsafe"?
>>>>>>
>>>>>>
>>>>>> [Suhas]
>>>>>
>>>>> Initially that category was called "BAD" as in
>>>>>
>>>>>
>>>>>
>>>>> https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux-attr=
ibutes/01/
>>>>>
>>>>> However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D was=
 a bad choice :-)
>>>>>
>>>>> Either of the following options seems fine to me
>>>>>
>>>>>    1.
>>>>>
>>>>>    NOT-RECOMMENDED [ we use hyphen separated multi word format in oth=
er
>>>>>    category names]
>>>>>    2. UNSAFE
>>>>>
>>>>>
>>>> I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you intend
>>>> the category name to mean "NOT RECOMMENDED" in the 2119 sense.
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>> -4.3: Please don't use a 2119 keyword as part of the definition
>>>>>> of a category. This creates sort of a circular dependency; that is
>>>>>> attributes are in this category because they MUST be identical; but
>>>>>> they
>>>>>> MUST be identical because they are in this category. I suggest
>>>>>> describing
>>>>>> the category descriptively, and adding a separate sentence to say
>>>>>> "Attributes
>>>>>> in the IDENTICAL category MUST be identical across all media
>>>>>> descriptions."
>>>>>>
>>>>>>
>>>>>>
>>>>> [Suhas]. I have removed the usage of word identical from the definiti=
on
>>>>> as
>>>>> below. Please let me know if this works.
>>>>>
>>>>>
>>>>> Category: IDENTICAL
>>>>>
>>>>> Attributes  and their associated values (if present) in the IDENTICAL
>>>>> category MUST be repeated across all the media descriptions under
>>>>> multiplexing.
>>>>>
>>>>>
>>>>> Okay.
>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>>
>>>>> -5.8 and 5.9:
>>>>>
>>>>>>     The last paragraph of 5.8 seems redundant with section 5.9.
>>>>>>
>>>>>> -5.8, last paragraph:
>>>>>>
>>>>>>     "Hence multiplexing MUST NOT be performed even in this
>>>>>>     alternate scenario." seems to contradict the category selection =
of
>>>>>>     "NOT RECOMMENDED" (but see previous comment about not using 2119
>>>>>>     keywords in a category title.)
>>>>>>
>>>>>>
>>>>>> [Suhas] The idea here is to not perform multiplexing and hence the
>>>>>>
>>>>> category
>>>>> of NOT RECOMMENDED assigned. I can update this once we finalize on th=
e
>>>>> right naming for "NOT RECOMMENDED"
>>>>>
>>>>>
>>>> This argues for the "UNSAFE" name, since the actual normative guidance
>>>> is
>>>> stronger than "NOT RECOMMENDED". (Unless you want a "MUST NOT" name
>>>> :-)  )
>>>>
>>>>
>>>>
>>>>>
>>>>> -5.24, last paragraph: "it is recommended to consult the
>>>>>
>>>>>>   document defining the attribute."
>>>>>>
>>>>>>   I assume one should _always_ refer to the specification of
>>>>>>   an SDP attribute before trying to mux it. But that doc is
>>>>>>   not going to explain muxing issues, is it?
>>>>>>
>>>>>>
>>>>>> [Suhas]
>>>>>>
>>>>>
>>>>> Since cparmin/cparmax can define numerical values/ranges
>>>>>
>>>>> for any of b=3D or a=3D attributes (identified via cpar), there is no=
 easy
>>>>> way
>>>>> to assign a multiplexing category unless one knows what cpar is being
>>>>>
>>>>> used and the assignned numerical values to each of cparmin/cparmax
>>>>> mean.
>>>>> Thus the category SPECIAL has been assigned as a recommendation for t=
he
>>>>> implementor to consult the spec that defines a particular usage of
>>>>> cpar,
>>>>> cparmin and cparmax combination to really see what=E2=80=99s going on=
.
>>>>>
>>>>> This is very similar to extmap or RTCP Application feedback message
>>>>> type
>>>>>
>>>>> How about following rephrasing
>>>>>
>>>>>
>>>>> *"The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and max=
imum
>>>>> numerical values associated with the attributes described in a=3Dcpar=
.
>>>>> Since
>>>>> a cpar attribute can either define*
>>>>>
>>>>> *=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attri=
bute,  the multiplexing category *
>>>>>
>>>>> *depends on actual attribute being encapsulated and the implications =
of
>>>>> the
>>>>> numerical values assigned. Hence it is recommended to consult the
>>>>> specification defining the the attributes (cparmin/cparmax) to furthe=
r
>>>>> analyze their behavior under multiplexing."*
>>>>>
>>>>>
>>>> That works for me.
>>>>
>>>>
>>>>
>>>>>
>>>>> -5.26:
>>>>>
>>>>>>   -"Support of this extension is OPTIONAL."
>>>>>>   Please don't use 2119 keywords to describe existing requirements
>>>>>>   from other docs, unless in direct quotes.
>>>>>>
>>>>>>
>>>>>>
>>>>>> [Suhas] This sentence is taken directly from RFC6714. (
>>>>> https://tools.ietf.org/html/rfc6714)
>>>>>
>>>>>
>>>> Sure, but it's not attributed as a quote. I suggest something to the
>>>> effect of "This is an optional extension according to [RFC6714]", "
>>>> [RFC6714] states that this extension is 'OPTIONAL'",  or even the exac=
t
>>>> same language as currently in the draft, but without the capitalized
>>>> OPTIONAL.
>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>>
>>>>> - 5.39:
>>>>>
>>>>>>   I=E2=80=99m not a zrtp expert, but it seems like it might
>>>>>>   be more complicated than this. Section 8 of 6189 says
>>>>>>   =E2=80=9CThe a=3Dzrtp-hash attribute  can only be included in the
>>>>>>   SDP at the media level since Hello messages sent in
>>>>>>   different media streams will have unique hashes.=E2=80=9D
>>>>>>   I wonder if this shouldn't be =E2=80=9Cidentical=E2=80=9D?
>>>>>>
>>>>>>
>>>>>> [Suhas] The category TRANSPORT is the appropriate assignment. This
>>>>>> spec
>>>>>>
>>>>> assigns category for these attributes over the multiplexed transport.
>>>>>
>>>>> So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.
>>>>>
>>>>> The zrtp-hash selected must correspond to the m=3Dline that is select=
ed
>>>>> for
>>>>> BUNDLE once the O/A negotiation completes. Thus the category TRANSPOR=
T.
>>>>>
>>>>>
>>>>>
>>>>> I _think_ you are right, but there may be an interaction here that ca=
n
>>>> break things I will think about that more, and respond to this issue i=
s
>>>> a
>>>> separate thread.
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>> -5.45:
>>>>>>   6193 is an ISE stream RFC. Does anyone actually use
>>>>>>   in a context where muxing matters?
>>>>>>
>>>>>>
>>>>>> [Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.
>>>>>
>>>>>
>>>> That seems reasonable, unless  you know of good reasons otherwise.
>>>>
>>>>
>>>> -15.1:
>>>>>>   - Is there no need for a spec for any newly registered categories?
>>>>>>   - 2nd to last paragraph: "This seems vague for a MUST. Do you expe=
ct
>>>>>>     the registration of a new category to change the categories
>>>>>>     already assigned to existing SDP parameters? Is it possible
>>>>>>     that a new category only applies to some new SDP parameters?"
>>>>>>
>>>>>>
>>>>>> [Suhas] The following 2 paragraphs are supposed to mean that new
>>>>> multiplexing categories require new registrations via a spec and
>>>>> applicability of the new category to new SDP attributes and possibly
>>>>> existing SDP attributes ( if the new category makes more sense). What
>>>>> would
>>>>> be a better framing to capture the intent ?
>>>>>
>>>>> "*Further entries can be registered on a first-come first-serve basis=
.
>>>>> Each
>>>>> registration needs to indicate the multiplexing category value to be
>>>>> added
>>>>> to the "Multiplexing Categories" subregistry as defined in this
>>>>> section.*
>>>>>
>>>>> *Such a registration MUST also indicate the applicability of the newl=
y
>>>>> defined multiplexing category value to various subregistries defined =
at
>>>>> "Session Description Protocol (SDP) Parameters".*
>>>>>
>>>>>
>>>> That works for me.
>>>>
>>>>
>>>>
>>>>>   - Last paragraph: 4566 procedures apply to what? The text just said
>>>>>
>>>>>>     new categories are first-come-first server. I don=E2=80=99t thin=
k
>>>>>>     4566 set policies for how to change mux categories.
>>>>>>
>>>>>>
>>>>>> [Suhas] Agreed. I prefer removing this line altogether. Please let m=
e
>>>>> know
>>>>>
>>>>>
>>>>> I agree.
>>>>
>>>>
>>>> -15.2.1:
>>>>>>   How do you expect the table to look after adding this RFC to the
>>>>>>   references? Will this RFC be added to the entries in the MUX
>>>>>>   column?
>>>>>>
>>>>>>
>>>>>> [Suhas] The plan was to add the reference to this RFC in the
>>>>> "Reference
>>>>> Column"
>>>>>
>>>>>
>>>> Okay.
>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>> # Editorial #
>>>>>>
>>>>>>
>>>>>> - The abstract is more detailed than needed. The point is to describ=
e
>>>>> the
>>>>>
>>>>>> purpose of the draft. The second paragraph pretty much accomplishes
>>>>>> that.
>>>>>>
>>>>>>
>>>>>> [Suhas] How do this rephrase look
>>>>>>
>>>>>
>>>>> =E2=80=9CThe purpose of this specification is to provide a framework =
for
>>>>> analyzing
>>>>> the multiplexing characteristics of SDP attributes when SDP is used t=
o
>>>>> negotiate the usage of single 5-tuple for sending and receiving media
>>>>> associated with multiple media descriptions,. This specification also
>>>>> categorizes the existing SDP attributes based on the framework
>>>>> described
>>>>> herein.=E2=80=9D
>>>>>
>>>>>
>>>>> That works for me.
>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>>
>>>>> -5 and subsections: Is there any method to the ordering? They aren't
>>>>>>    in RFC order. It might make sense to group by the nature of the
>>>>>>    attributes, but if that is the case here it's not explained.
>>>>>>
>>>>>>
>>>>>> [Suhas] These are not ordered as of today. I can order the 5.X
>>>>>>
>>>>> subsections
>>>>> by RFC order, if needed.
>>>>>
>>>>>
>>>> Unordered is also okay. I was just wondering if there was a logic that
>>>> should be mentioned.
>>>>
>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>>
>>>>> -5.13, table:
>>>>>>   "Specific RTP extension document MUST be referred"
>>>>>>
>>>>>>
>>>>>> [Suhas] The idea was to mean that , one should refer to the
>>>>>>
>>>>> specification
>>>>> that defines a specific RTP extension in order to understand the
>>>>> multiplexing behavior.
>>>>>
>>>>> Would the following rephrasing help instead
>>>>>
>>>>> "Refer to the document defining specific RTP Extension"
>>>>>
>>>>>
>>>>>
>>>>> Yes, thanks.
>>>>
>>>>
>>>>   I don=E2=80=99t understand what that means. If you mean to
>>>>>
>>>>>>    say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=E2=
=80=99t use MUST.
>>>>>>
>>>>>> -5.22, table: "document needs to be referred" (several repetitions)
>>>>>>   I'm not sure what this means. Should it say "Refer to the
>>>>>>   specific document"?
>>>>>>
>>>>>>
>>>>>> Similarly as above, would this reprhasing help
>>>>>>
>>>>>
>>>>> "Refer to the document defining specific FEC Scheme
>>>>>
>>>>>
>>>>>
>>>>> Similarly as above, Yes, thanks. :-)
>>>>
>>>>
>>>>
>>>>> -6.3: "not clearly defined offer/answer usage"
>>>>>>   I'm not sure what is meant here. (Also, why is this not TBD or NOT
>>>>>>   RECOMMENDED?)
>>>>>>
>>>>>>
>>>>>> [Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind,
>>>>> either
>>>>> the
>>>>> BUNDLE spec or this spec cannot define its mux behavior. This is due =
to
>>>>> applicability of these specs under SD{ O/A usages alone.
>>>>>
>>>>> I can rephrase the above as
>>>>> "not defined under SDP Offer/Answer usage"
>>>>>
>>>>>
>>>> WFM, thanks.
>>>>
>>>> [...]
>>>>
>>>>
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>
>>>

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

<div dir=3D"ltr">Hi Ben,<div><br></div><div>What you say makes sense to me.=
=C2=A0 Adding ZRTP guidance to 5764-mux-fixes seems like a reasonable solut=
ion to me.</div><div><br></div><div>- Alan -</div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Mon, May 23, 2016 at 4:12 PM, Ben Campb=
ell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com" target=3D"_bla=
nk">ben@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-sty=
le:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi Alan,<br>
<br>
If I read RFC 6189 correctly, I see that it documents how to distinguish zr=
tp messages from rtp and stun. Further, it distinguishes itself from stun b=
y using a different magic cookie value. That&#39;s a little more complex th=
an the first-byte demuxing in 5764--although it looks like first-byte demux=
ing might work as long as we don&#39;t end up with a conflicting stun metho=
d. (I&#39;m also not certain that the average 5764 implementation is going =
to look at the cookie to make the demux decision.)<br>
<br>
I don&#39;t see anything in 6189 about distinguishing itself from DTLS. Aga=
in, we can infer that from the first byte, as long as we don&#39;t get a co=
nflicting tls content-type.<br>
<br>
This doesn&#39;t quite seem (to me) to meet the following requirement in dr=
aft-ietf-mmusic-sdp-bundle-negotiation (emphasis mine):<br>
<br>
=C2=A0 &quot;If bundled &quot;m=3D&quot; lines use different protocols on t=
op<br>
=C2=A0 =C2=A0of the transport-layer protocol,=C2=A0 there MUST exist a publ=
icly<br>
=C2=A0 =C2=A0available specification which describes a mechanism, for **thi=
s<br>
=C2=A0 =C2=A0particular protocol combination**, how to associate received d=
ata with<br>
=C2=A0 =C2=A0the correct protocol.&quot;<br>
<br>
As mentioned, one way to fix that could be to add zrtp into the general gui=
dance in 5764-mux-fixes.<br>
<br>
Thanks,<br>
<br>
Ben.<br>
<br>
<br>
On 23 May 2016, at 17:48, Alan Johnston wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Hi Ben,<br>
<br>
The a=3Dzrtp-hash attribute is a hash of the ZRTP Hello message that is goi=
ng<br>
to be sent over the transport.=C2=A0 There is one ZRTP Hello sent per trans=
port,<br>
and one handshake per transport.<br>
<br>
The ZRTP message format was carefully crafted in association with<br>
DTLS-SRTP, so if draft-ietf-avtcore-rfc5764-mux-fixes breaks this, then it<=
br>
probably should be fixed.<br>
<br>
- Alan -<br>
<br>
On Mon, May 23, 2016 at 3:34 PM, Ben Campbell &lt;<a href=3D"mailto:ben@nos=
trum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Hi,<br>
<br>
As promised, here&#39;s more on my concern about zrtp-hash in<br>
draft-ietf-mmusic-sdp-mux-attributes:<br>
<br>
I think you need to describe the assumptions about what it means to<br>
multiplex zrtp. Am I correct to assume that the draft assumes that there is=
<br>
only one zrtp session in a transport flow, with a single zrtp handshake?<br=
>
And that all of the bundled m=3Dlines represent media that is part of that<=
br>
zrtp association? (That is, you never mux distinct zrtp associations, or<br=
>
zrtp and dtls-srtp?)<br>
<br>
If the answer is yes, then &quot;transport&quot; seems to make sense.<br>
<br>
But is zrtp demuxing really well defined enough to keep this out of the<br>
&quot;NOT RECOMMENDED&quot; category? I&#39;m not sure it meets the bundle =
requirement<br>
for a public spec on how to demux it. One might infer that from two public<=
br>
specs (zrtp and 5764), but IIUC, the guidance proposed in<br>
draft-ietf-avtcore-rfc5764-mux-fixes would cause a zrtp messages to be<br>
dropped, since its first byte would not match any of the demux rules. Or,<b=
r>
if zrtp-hash is allowed, does mux-fixes need to change?<br>
<br>
What am I missing?<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
<br>
On 20 May 2016, at 18:07, Ben Campbell wrote:<br>
<br>
Apologies for my slow response. The last month has been a perfect storm of<=
br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
productivity killers. I&#39;m digging out of the backlog now. Comments inli=
ne,<br>
with sections that appear resolved removed.<br>
<br>
There is one issue (zrtp-hash) where I will start a separate thread<br>
shortly.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
On 20 Apr 2016, at 1:00, Suhas Nandakumar wrote:<br>
<br>
Hello Ben<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
=C2=A0Sorry for the delay in responding. Many thanks for the detailed revie=
w.<br>
<br>
=C2=A0Please find my responses inline (marked by [Suhas]).<br>
<br>
Cheers<br>
Suhas<br>
<br>
On Fri, Feb 19, 2016 at 2:28 PM, Ben Campbell &lt;<a href=3D"mailto:ben@nos=
trum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
<br>
Hi,<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
Here is my AD evaluation of draft-ietf-mmusic-sdp-mux-attributes-12. I<br>
would like at least the substantive<br>
section to be discussed before going to IETF last call.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
----------<br>
<br>
# Substantive #<br>
<br>
- This is very long and detailed. Are the authors and chairs comfortable<br=
>
that all sections have had sufficient review?<br>
<br>
-4.0: It would be helpful to add a paragraph describing how these<br>
semantic<br>
groupings map to the categories.<br>
<br>
<br>
</blockquote>
[Suhas] The semantic groupings were added as a informal reference and<br>
they<br>
don&#39;t really interact with the categories as such.<br>
<br>
</blockquote>
<br>
So I have to wonder why we have the groupings. But I guess at this point<br=
>
in the process, it&#39;s not worth changing that.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Does the following rephrasing work<br>
<br>
*&quot;Attributes in an SDP session description can be defined at the<br>
**session-level<br>
or=C2=A0 media-level or=C2=A0 source-level. Informally, there are various s=
emantic<br>
grouping for these attributes. One such grouping could be as noted<br>
below:*<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
*=C2=A0 =C2=A0o=C2=A0 Attributes related to media content such as media typ=
e, encoding<br>
=C2=A0 =C2=A0 =C2=A0schemes, payload types.=C2=A0 =C2=A0o=C2=A0 Attributes =
specifying media transport<br>
characteristics like RTP/RTP=C2=A0 =C2=A0 =C2=A0 Control Protocol (RTCP) po=
rt numbers,<br>
network addresses, QOS.=C2=A0 =C2=A0o=C2=A0 Metadata description attributes=
 capturing<br>
session timing and=C2=A0 =C2=A0 =C2=A0 origin information.=C2=A0 =C2=A0o=C2=
=A0 Attributes establishing<br>
relationships between media descriptions=C2=A0 =C2=A0 =C2=A0 such as groupi=
ng framework<br>
[RFC5888 &lt;<a href=3D"https://tools.ietf.org/html/rfc5888" rel=3D"norefer=
rer" target=3D"_blank">https://tools.ietf.org/html/rfc5888</a>&gt;]The prop=
osed framework<br>
defines categories for the SDP attributes under multiplexing and assigns<br=
>
each SDP attribute to an appropriate multiplexing category.*<br>
<br>
*Since the multiplexing categories defined in this specification are<br>
independent of any informal semantic grouping of the SDP attributes, the<br=
>
categorizations assigned against each attribute=C2=A0 MUST be considered as=
<br>
normative assignments under multiplexing. &quot;*<br>
<br>
</blockquote>
<br>
All fine, except the last sentence is pretty meta--it uses normative<br>
language to talk about normative language (&quot;MUST be considered normati=
ve&quot;).<br>
I&#39;m not entirely sure what you intend there, but how about something to=
 the<br>
effect of &quot;... the categorizations assigned against each attribute are=
<br>
normative.&quot;<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
-4.2: I recommend choosing a category name that is not a 2119 keyword.<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 Maybe something like &quot;not mux-able&quot; or &quot;unsafe&quot;?=
<br>
<br>
<br>
</blockquote>
[Suhas]<br>
<br>
Initially that category was called &quot;BAD&quot; as in<br>
<br>
<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-nandakumar-mmusic-sdp-mux=
-attributes/01/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.i=
etf.org/doc/draft-nandakumar-mmusic-sdp-mux-attributes/01/</a><br>
<br>
However we ended upon NOT RECOMMENDED since =E2=80=9CBAD=E2=80=9D was a bad=
 choice :-)<br>
<br>
Either of the following options seems fine to me<br>
<br>
=C2=A0 =C2=A01.<br>
<br>
=C2=A0 =C2=A0NOT-RECOMMENDED [ we use hyphen separated multi word format in=
 other<br>
=C2=A0 =C2=A0category names]<br>
=C2=A0 =C2=A02. UNSAFE<br>
<br>
</blockquote>
<br>
I lean towards unsafe. OTOH, NOT-RECOMMENDED makes sense if you intend<br>
the category name to mean &quot;NOT RECOMMENDED&quot; in the 2119 sense.<br=
>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-4.3: Please don&#39;t use a 2119 keyword as part of the definition<br>
of a category. This creates sort of a circular dependency; that is<br>
attributes are in this category because they MUST be identical; but they<br=
>
MUST be identical because they are in this category. I suggest<br>
describing<br>
the category descriptively, and adding a separate sentence to say<br>
&quot;Attributes<br>
in the IDENTICAL category MUST be identical across all media<br>
descriptions.&quot;<br>
<br>
<br>
</blockquote>
<br>
[Suhas]. I have removed the usage of word identical from the definition<br>
as<br>
below. Please let me know if this works.<br>
<br>
<br>
Category: IDENTICAL<br>
<br>
Attributes=C2=A0 and their associated values (if present) in the IDENTICAL<=
br>
category MUST be repeated across all the media descriptions under<br>
multiplexing.<br>
<br>
<br>
</blockquote>
Okay.<br>
<br>
[...]<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
-5.8 and 5.9:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 =C2=A0 The last paragraph of 5.8 seems redundant with section 5.9.<b=
r>
<br>
-5.8, last paragraph:<br>
<br>
=C2=A0 =C2=A0 &quot;Hence multiplexing MUST NOT be performed even in this<b=
r>
=C2=A0 =C2=A0 alternate scenario.&quot; seems to contradict the category se=
lection of<br>
=C2=A0 =C2=A0 &quot;NOT RECOMMENDED&quot; (but see previous comment about n=
ot using 2119<br>
=C2=A0 =C2=A0 keywords in a category title.)<br>
<br>
<br>
[Suhas] The idea here is to not perform multiplexing and hence the<br>
</blockquote>
category<br>
of NOT RECOMMENDED assigned. I can update this once we finalize on the<br>
right naming for &quot;NOT RECOMMENDED&quot;<br>
<br>
</blockquote>
<br>
This argues for the &quot;UNSAFE&quot; name, since the actual normative gui=
dance is<br>
stronger than &quot;NOT RECOMMENDED&quot;. (Unless you want a &quot;MUST NO=
T&quot; name :-)=C2=A0 )<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
-5.24, last paragraph: &quot;it is recommended to consult the<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 document defining the attribute.&quot;<br>
<br>
=C2=A0 I assume one should _always_ refer to the specification of<br>
=C2=A0 an SDP attribute before trying to mux it. But that doc is<br>
=C2=A0 not going to explain muxing issues, is it?<br>
<br>
<br>
[Suhas]<br>
</blockquote>
<br>
Since cparmin/cparmax can define numerical values/ranges<br>
<br>
for any of b=3D or a=3D attributes (identified via cpar), there is no easy<=
br>
way<br>
to assign a multiplexing category unless one knows what cpar is being<br>
<br>
used and the assignned numerical values to each of cparmin/cparmax mean.<br=
>
Thus the category SPECIAL has been assigned as a recommendation for the<br>
implementor to consult the spec that defines a particular usage of cpar,<br=
>
cparmin and cparmax combination to really see what=E2=80=99s going on.<br>
<br>
This is very similar to extmap or RTCP Application feedback message type<br=
>
<br>
How about following rephrasing<br>
<br>
<br>
*&quot;The attributes (a=3Dcparmin and a=3Dcparmax) define minimum and maxi=
mum<br>
numerical values associated with the attributes described in a=3Dcpar.<br>
Since<br>
a cpar attribute can either define*<br>
<br>
*=E2=80=9Cb=3D=E2=80=9D attribute or any =E2=80=9Ca=3D=E2=80=9D attribute,=
=C2=A0 the multiplexing category *<br>
<br>
*depends on actual attribute being encapsulated and the implications of<br>
the<br>
numerical values assigned. Hence it is recommended to consult the<br>
specification defining the the attributes (cparmin/cparmax) to further<br>
analyze their behavior under multiplexing.&quot;*<br>
<br>
</blockquote>
<br>
That works for me.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
-5.26:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 -&quot;Support of this extension is OPTIONAL.&quot;<br>
=C2=A0 Please don&#39;t use 2119 keywords to describe existing requirements=
<br>
=C2=A0 from other docs, unless in direct quotes.<br>
<br>
<br>
<br>
</blockquote>
[Suhas] This sentence is taken directly from RFC6714. (<br>
<a href=3D"https://tools.ietf.org/html/rfc6714" rel=3D"noreferrer" target=
=3D"_blank">https://tools.ietf.org/html/rfc6714</a>)<br>
<br>
</blockquote>
<br>
Sure, but it&#39;s not attributed as a quote. I suggest something to the<br=
>
effect of &quot;This is an optional extension according to [RFC6714]&quot;,=
 &quot;<br>
[RFC6714] states that this extension is &#39;OPTIONAL&#39;&quot;,=C2=A0 or =
even the exact<br>
same language as currently in the draft, but without the capitalized<br>
OPTIONAL.<br>
<br>
[...]<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
- 5.39:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 I=E2=80=99m not a zrtp expert, but it seems like it might<br>
=C2=A0 be more complicated than this. Section 8 of 6189 says<br>
=C2=A0 =E2=80=9CThe a=3Dzrtp-hash attribute=C2=A0 can only be included in t=
he<br>
=C2=A0 SDP at the media level since Hello messages sent in<br>
=C2=A0 different media streams will have unique hashes.=E2=80=9D<br>
=C2=A0 I wonder if this shouldn&#39;t be =E2=80=9Cidentical=E2=80=9D?<br>
<br>
<br>
[Suhas] The category TRANSPORT is the appropriate assignment. This spec<br>
</blockquote>
assigns category for these attributes over the multiplexed transport.<br>
<br>
So, if we have 3 m=3D lines each with one zrtp-hash and all bundled.<br>
<br>
The zrtp-hash selected must correspond to the m=3Dline that is selected for=
<br>
BUNDLE once the O/A negotiation completes. Thus the category TRANSPORT.<br>
<br>
<br>
<br>
</blockquote>
I _think_ you are right, but there may be an interaction here that can<br>
break things I will think about that more, and respond to this issue is a<b=
r>
separate thread.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-5.45:<br>
=C2=A0 6193 is an ISE stream RFC. Does anyone actually use<br>
=C2=A0 in a context where muxing matters?<br>
<br>
<br>
</blockquote>
[Suhas] . I doubt it. Do you recommend as NOT-RECOMMENDED instead.<br>
<br>
</blockquote>
<br>
That seems reasonable, unless=C2=A0 you know of good reasons otherwise.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">
-15.1:<br>
=C2=A0 - Is there no need for a spec for any newly registered categories?<b=
r>
=C2=A0 - 2nd to last paragraph: &quot;This seems vague for a MUST. Do you e=
xpect<br>
=C2=A0 =C2=A0 the registration of a new category to change the categories<b=
r>
=C2=A0 =C2=A0 already assigned to existing SDP parameters? Is it possible<b=
r>
=C2=A0 =C2=A0 that a new category only applies to some new SDP parameters?&=
quot;<br>
<br>
<br>
</blockquote>
[Suhas] The following 2 paragraphs are supposed to mean that new<br>
multiplexing categories require new registrations via a spec and<br>
applicability of the new category to new SDP attributes and possibly<br>
existing SDP attributes ( if the new category makes more sense). What<br>
would<br>
be a better framing to capture the intent ?<br>
<br>
&quot;*Further entries can be registered on a first-come first-serve basis.=
<br>
Each<br>
registration needs to indicate the multiplexing category value to be<br>
added<br>
to the &quot;Multiplexing Categories&quot; subregistry as defined in this s=
ection.*<br>
<br>
*Such a registration MUST also indicate the applicability of the newly<br>
defined multiplexing category value to various subregistries defined at<br>
&quot;Session Description Protocol (SDP) Parameters&quot;.*<br>
<br>
</blockquote>
<br>
That works for me.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
=C2=A0 - Last paragraph: 4566 procedures apply to what? The text just said<=
br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 =C2=A0 new categories are first-come-first server. I don=E2=80=99t t=
hink<br>
=C2=A0 =C2=A0 4566 set policies for how to change mux categories.<br>
<br>
<br>
</blockquote>
[Suhas] Agreed. I prefer removing this line altogether. Please let me<br>
know<br>
<br>
<br>
</blockquote>
I agree.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">
-15.2.1:<br>
=C2=A0 How do you expect the table to look after adding this RFC to the<br>
=C2=A0 references? Will this RFC be added to the entries in the MUX<br>
=C2=A0 column?<br>
<br>
<br>
</blockquote>
[Suhas] The plan was to add the reference to this RFC in the &quot;Referenc=
e<br>
Column&quot;<br>
<br>
</blockquote>
<br>
Okay.<br>
<br>
[...]<br>
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
# Editorial #<br>
<br>
<br>
</blockquote>
- The abstract is more detailed than needed. The point is to describe the<b=
r>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
purpose of the draft. The second paragraph pretty much accomplishes<br>
that.<br>
<br>
<br>
[Suhas] How do this rephrase look<br>
</blockquote>
<br>
=E2=80=9CThe purpose of this specification is to provide a framework for<br=
>
analyzing<br>
the multiplexing characteristics of SDP attributes when SDP is used to<br>
negotiate the usage of single 5-tuple for sending and receiving media<br>
associated with multiple media descriptions,. This specification also<br>
categorizes the existing SDP attributes based on the framework described<br=
>
herein.=E2=80=9D<br>
<br>
<br>
</blockquote>
That works for me.<br>
<br>
[...]<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-5 and subsections: Is there any method to the ordering? They aren&#39;t<br=
>
=C2=A0 =C2=A0in RFC order. It might make sense to group by the nature of th=
e<br>
=C2=A0 =C2=A0attributes, but if that is the case here it&#39;s not explaine=
d.<br>
<br>
<br>
[Suhas] These are not ordered as of today. I can order the 5.X<br>
</blockquote>
subsections<br>
by RFC order, if needed.<br>
<br>
</blockquote>
<br>
Unordered is also okay. I was just wondering if there was a logic that<br>
should be mentioned.<br>
<br>
<br>
[...]<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-5.13, table:<br>
=C2=A0 &quot;Specific RTP extension document MUST be referred&quot;<br>
<br>
<br>
[Suhas] The idea was to mean that , one should refer to the<br>
</blockquote>
specification<br>
that defines a specific RTP extension in order to understand the<br>
multiplexing behavior.<br>
<br>
Would the following rephrasing help instead<br>
<br>
&quot;Refer to the document defining specific RTP Extension&quot;<br>
<br>
<br>
<br>
</blockquote>
Yes, thanks.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 I don=E2=80=99t understand what that means. If you mean to<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 =C2=A0say =E2=80=9Crefer to specific document=E2=80=9D, that shouldn=
=E2=80=99t use MUST.<br>
<br>
-5.22, table: &quot;document needs to be referred&quot; (several repetition=
s)<br>
=C2=A0 I&#39;m not sure what this means. Should it say &quot;Refer to the<b=
r>
=C2=A0 specific document&quot;?<br>
<br>
<br>
Similarly as above, would this reprhasing help<br>
</blockquote>
<br>
&quot;Refer to the document defining specific FEC Scheme<br>
<br>
<br>
<br>
</blockquote>
Similarly as above, Yes, thanks. :-)<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
-6.3: &quot;not clearly defined offer/answer usage&quot;<br>
=C2=A0 I&#39;m not sure what is meant here. (Also, why is this not TBD or N=
OT<br>
=C2=A0 RECOMMENDED?)<br>
<br>
<br>
</blockquote>
[Suhas] Since RFC3890 b=3DTIAS is not defined keeping O/A in mind, either<b=
r>
the<br>
BUNDLE spec or this spec cannot define its mux behavior. This is due to<br>
applicability of these specs under SD{ O/A usages alone.<br>
<br>
I can rephrase the above as<br>
&quot;not defined under SDP Offer/Answer usage&quot;<br>
<br>
</blockquote>
<br>
WFM, thanks.<br>
<br>
[...]<br>
<br>
</blockquote>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br>
</blockquote></blockquote>
</blockquote></div><br></div></div>

--001a114267666fc2c60533998a4d--


From nobody Tue May 24 10:39:35 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADDE12D94E for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 10:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jOuPILumpHgx for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 10:39:32 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9957812D94C for <mmusic@ietf.org>; Tue, 24 May 2016 10:39:32 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id j1so38423902oih.3 for <mmusic@ietf.org>; Tue, 24 May 2016 10:39:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=O3UF+/QGVXjsmaHbqYpDpephI4HMSdfU4+5+2SlCYXo=; b=RQLQqYTyAQ9mVtEMM+fAGXH7SkMM9dauO+Xe6deUXjO2UnLTBfvB+CVEiIZ7NxQR8u +IUwr6V7kF8Ie/TS5oTPlT5gZP3IY+T5fmuveV3fcZZyHCTHu0JjLpfIxdJuQdt0AgHq kx8k1a72QTQI0Hby/7AX/oPAuimxcBg8geN83zvefWn16eO2bAVKb93pxoiBpF+8XTvK IUHVs5ZvLUNBufgKg70UU6zpBzy8/qrwlDEp2jcvieu8KYwVoGnXFnDH6fP6TdzXxsv0 ZGImGZHPIQp7q5OXulibDBUXKslx2krwPXkKDqqFtfWkCJl/TABiNrlf8ofUhnD8SEu3 BVyg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=O3UF+/QGVXjsmaHbqYpDpephI4HMSdfU4+5+2SlCYXo=; b=NKZ20aVpAP/2eUHufHGtCR0q413CFR0Vt7bSKGJyCz44vfm4OF19SUTZ+bQVVVxreJ K4IOMACcOyriAZTpwrH1RANePzZyUrcFjLvA6hB1eQDOFKIkl7ZE5hAaVSn1cgBDiE28 G6R5pO13ADctksRw9yp3pVgWEQeced8uVL5kpBYbewpt9a2ix+V1seZ/0H1zvAQsZJJu 2lo3PGvAFNHUgy21vkSwoe8V6oEjQOwtXP3NJUbfCToTxwGMfP4R4VzcF26GcSBaA/WJ nA9QGJBRc02NtutahJPQ8oMf8U2ZFj68SORTRQGopMUk0V8l1oe+LvB7N1IFdMhzkBOc 1wwg==
X-Gm-Message-State: ALyK8tLJVeM+za0a4QMlhUGayQk6Ug1Mf5LAF9ofMvo860+z6zi4SbCkgPPUkg2NhyMIgw==
X-Received: by 10.157.41.149 with SMTP id n21mr3276396otb.19.1464111571819; Tue, 24 May 2016 10:39:31 -0700 (PDT)
Received: from mail-it0-f52.google.com (mail-it0-f52.google.com. [209.85.214.52]) by smtp.gmail.com with ESMTPSA id t5sm1862217oie.18.2016.05.24.10.39.31 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 10:39:31 -0700 (PDT)
Received: by mail-it0-f52.google.com with SMTP id z123so14940538itg.0 for <mmusic@ietf.org>; Tue, 24 May 2016 10:39:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.155.132 with SMTP id o126mr18758658itd.95.1464111570651;  Tue, 24 May 2016 10:39:30 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 24 May 2016 10:39:30 -0700 (PDT)
In-Reply-To: <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu>
Date: Tue, 24 May 2016 13:39:30 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com>
Message-ID: <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=94eb2c05d15814974e05339a0af5
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ChYQlgVmsN-itjCvz4s5rWxYlio>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 17:39:34 -0000

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

On Tue, May 24, 2016 at 12:39 PM, Paul Kyzivat <pkyzivat@alum.mit.edu>
wrote:

>
> I have a slight issue with how this was done. In section 5.1 is the
> following new text:
>
>    When an answerer needs to establish a new DTLS association, if
>    unreliable transport is used, and if the offerer did not allocate a
>    new transport, the answerer MUST allocate a new transport for the
>    offer in answer a way that it can disambiguate any packets associated
>    with new DTLS association from any packets associated with any other
>    DTLS association.  This typically means using a local address and or
>    port, or a set of ICE candidates (see Section 6), which were not
>    recently used for any other DTLS association.
>
> I agree with the point of this, but the qualifier "if unreliable transport
> is used" doesn't seem to be the right one. I don't think the issue has
> anything to do with unreliability. For instance I don't think it would
> apply if using unreliable SCTP streams. I think the real issue is that UDP
> is not a connection-oriented transport.
>
> I'm not sure what language to use here that would cover the *right* other
> non-UDP protocols. (AFAIK there are none that qualify.) If you can't come
> up with something I guess I would make this UDP-specific.
>
> Note there is similar text with the same problem in Section 6.
>

This is actually the problem with either unreliable or un-ordered delivery
properties of the protocol. If it is known that all packets for DTLS
association have already been delivered (or failed to deliver) to the
remote party, then this protocol can be reused for the new DTLS
association. If it is known that DTLS packets for new association will be
delivered after packets for old DTLS association, then transport can be
reused for new DTLS association. For UDP, only the first condition can be
satisfied, provided that reasonable time have passed since the last packet
was sent and no packets for existing DTLS association are left in flight
over the network. For SCTP, if receipt confirmation was received for all
the DTLS packets for a given association, the same SCTP connection can be
reused for the new DTLS association. If in-order SCTP channel is used for
DTLS, then SCTP channel can also be reused for the new DTLS association.

Taking a step back, there are three protocols which can be in used in
practice to carry DTLS:

1. UDP

2. TCP with RFC 4571 framing. This protocol should be considered
unreliable, non-connection oriented since it is typically used to bridge
with UDP

3. SCTP. DTLS over SCTP is defined in RFC6083 and most likely broken. It is
also, as far as know, is not used by anybody in conjunction with
offer/answer.

What we are trying to do in this paragraph is carve out DTLS over SCTP
without explicitly naming it. Do you think it would be better if define
this as "if unreliable or un-ordered transport is used"?

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Tue, May 24, 2016 at 12:39 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<=
a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit=
.edu</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding=
-left:1ex"><span class=3D""><br></span>
I have a slight issue with how this was done. In section 5.1 is the followi=
ng new text:<br>
<br>
=C2=A0 =C2=A0When an answerer needs to establish a new DTLS association, if=
<br>
=C2=A0 =C2=A0unreliable transport is used, and if the offerer did not alloc=
ate a<br>
=C2=A0 =C2=A0new transport, the answerer MUST allocate a new transport for =
the<br>
=C2=A0 =C2=A0offer in answer a way that it can disambiguate any packets ass=
ociated<br>
=C2=A0 =C2=A0with new DTLS association from any packets associated with any=
 other<br>
=C2=A0 =C2=A0DTLS association.=C2=A0 This typically means using a local add=
ress and or<br>
=C2=A0 =C2=A0port, or a set of ICE candidates (see Section 6), which were n=
ot<br>
=C2=A0 =C2=A0recently used for any other DTLS association.<br>
<br>
I agree with the point of this, but the qualifier &quot;if unreliable trans=
port is used&quot; doesn&#39;t seem to be the right one. I don&#39;t think =
the issue has anything to do with unreliability. For instance I don&#39;t t=
hink it would apply if using unreliable SCTP streams. I think the real issu=
e is that UDP is not a connection-oriented transport.<br>
<br>
I&#39;m not sure what language to use here that would cover the *right* oth=
er non-UDP protocols. (AFAIK there are none that qualify.) If you can&#39;t=
 come up with something I guess I would make this UDP-specific.<br>
<br>
Note there is similar text with the same problem in Section 6.<br></blockqu=
ote><div><br></div><div>This is actually the problem with either unreliable=
 or un-ordered delivery properties of the protocol. If it is known that all=
 packets for DTLS association have already been delivered (or failed to del=
iver) to the remote party, then this protocol can be reused for the new DTL=
S association. If it is known that DTLS packets for new association will be=
 delivered after packets for old DTLS association, then transport can be re=
used for new DTLS association. For UDP, only the first condition can be sat=
isfied, provided that reasonable time have passed since the last packet was=
 sent and no packets for existing DTLS association are left in flight over =
the network. For SCTP, if receipt confirmation was received for all the DTL=
S packets for a given association, the same SCTP connection can be reused f=
or the new DTLS association. If in-order SCTP channel is used for DTLS, the=
n SCTP channel can also be reused for the new DTLS association.</div><div><=
br></div><div>Taking a step back, there are three protocols which can be in=
 used in practice to carry DTLS:</div><div><br></div><div>1. UDP</div><div>=
<br></div><div>2. TCP with RFC 4571 framing. This protocol should be consid=
ered unreliable, non-connection oriented since it is typically used to brid=
ge with UDP</div><div><br></div><div>3. SCTP. DTLS over SCTP is defined in =
RFC6083 and most likely broken. It is also, as far as know, is not used by =
anybody in conjunction with offer/answer.</div><div><br></div><div>What we =
are trying to do in this paragraph is carve out DTLS over SCTP without expl=
icitly naming it. Do you think it would be better if define this as &quot;i=
f unreliable or un-ordered transport is used&quot;?</div><div><br></div><di=
v>Regards,</div><div><div class=3D"gmail_signature">_____________<br>Roman =
Shpount</div></div><div>=C2=A0</div></div></div></div>

--94eb2c05d15814974e05339a0af5--


From nobody Tue May 24 10:49:55 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA34612D123; Tue, 24 May 2016 10:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lz9QqJQtd6EL; Tue, 24 May 2016 10:49:52 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96F3F12D961; Tue, 24 May 2016 10:49:51 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-53-5744943d819b
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.183.30]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 11.27.12926.D3494475; Tue, 24 May 2016 19:49:49 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0294.000; Tue, 24 May 2016 19:49:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nA=
Date: Tue, 24 May 2016 17:49:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com>
In-Reply-To: <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7nK7tFJdwg5YvJhYHLy5jtXh/Qddi /+LzzBbXzvxjtJi6/DGLA6vHlN8bWT12zrrL7rFkyU8mj7Znd9gDWKK4bFJSczLLUov07RK4 Mrr/v2Ys6JGr6F84ja2BcYVsFyMnh4SAicSOEw/YIGwxiQv31oPZQgJHGCUON7h2MXIB2UsY Jb6dOcbUxcjBwSZgIdH9TxukRkQgVOLNhGmsIDXMAnMYJW69aGEHSQgL2EtsfHKHCaLIQWLn 26ssELafxN13WxhBbBYBVYm/C7vBlvEK+Ers2H6GHWLxLCaJaYcVQGxOAVuJ7UvvMYPYjEDH fT+1Bmwms4C4xK0n85kgjhaQWLLnPDOELSrx8vE/VghbSWLR7c9gNzMLaEqs36UP0aooMaX7 ITvEWkGJkzOfsExgFJuFZOoshI5ZSDpmIelYwMiyilG0OLU4KTfdyFgvtSgzubg4P08vL7Vk EyMw1g5u+a26g/HyG8dDjAIcjEo8vAm1zuFCrIllxZW5hxglOJiVRHhPTHIJF+JNSaysSi3K jy8qzUktPsQozcGiJM7r/1IxXEggPbEkNTs1tSC1CCbLxMEp1cDoVuiV1ztzpSbvLZaziopP Ki+/vtJ1zeKX7aZCp79btZKEN9ZHr5jEeDjL/tmcy33KW4TavmkvbHswe+Oen2H6i5oay1ym 3+PISLm85PyeJ5ccDn65c9mId54yB8PerR9YJCVK/9hyPt6vsz4psOjV4rCwFzss/h44zSH/ 81DZ5bnnrjQLf+N6osRSnJFoqMVcVJwIAPqdl6mxAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/O5tXjGmlE3bZ7Tf0WVyVbny2c7c>
Cc: Flemming Andreasen <fandreas@cisco.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 17:49:54 -0000

SGksDQoNClF1ZXN0aW9ucyBmb3IgY2xhcmlmaWNhdGlvbjoNCg0KRG9lcyAicHJvdmlkZSIgbWVh
biB0aGF0IGVuZHBvaW50cyBNVVNUIGFsd2F5cywgZm9yIGVhY2ggY2VydGlmaWNhdGUsIGluY2x1
ZGUgYSBmaW5nZXJwcmludCBjYWxjdWxhdGVkIHVzaW5nIFNIQS0yNTY/DQoNCkRvZXMgInZhbGlk
YXRlIiBtZWFuIHRoZSBlbmRwb2ludHMgTVVTVCBhbHdheXMgY2hlY2sgdGhlIFNIQS0yNTYtY2Fs
Y3VsYXRlZCBmaW5nZXJwcmludCAoaWYgcHJlc2VudCkgYWdhaW5zdCB0aGUgdXNlZCBjZXJ0aWZp
Y2F0ZT8NCg0KUmVnYXJkcywNCg0KQ2hyaXN0ZXINCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEpvbmF0aGFuIExlbm5veCBbbWFpbHRvOmpvbmF0aGFuQHZpZHlvLmNvbV0gDQpT
ZW50OiAyNCBNYXkgMjAxNiAxOToxNw0KVG86IE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhvbXNv
bkBnbWFpbC5jb20+DQpDYzogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVy
aWNzc29uLmNvbT47IEZsZW1taW5nIEFuZHJlYXNlbiA8ZmFuZHJlYXNAY2lzY28uY29tPjsgZHJh
ZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGVAaWV0Zi5vcmc7IG1tdXNpYyA8bW11c2ljQGlldGYu
b3JnPg0KU3ViamVjdDogUmU6IFtNTVVTSUNdIFdHTEMgZm9yIGRyYWZ0LWlldGYtbW11c2ljLTQ1
NzItdXBkYXRlLTAzDQoNCisxIHRvIGFsbCB0aGlzIOKAlCBNYXJ0aW4gY2FwdHVyZXMgKGFuZCBh
ZGRyZXNzZXMpIG15IGNvbW1lbnRzIHBlcmZlY3RseS4NCg0KPiBPbiBNYXkgMjQsIDIwMTYsIGF0
IDEyOjEwIFBNLCBNYXJ0aW4gVGhvbXNvbiA8bWFydGluLnRob21zb25AZ21haWwuY29tPiB3cm90
ZToNCj4gDQo+IE9uIDI0IE1heSAyMDE2IGF0IDAwOjExLCBDaHJpc3RlciBIb2xtYmVyZyANCj4g
PGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4gd3JvdGU6DQo+PiBCdXQsIGlzIGl0IHdp
dGhpbiB0aGUgc2NvcGUgb2YgNDU3MiB0byBkZWZpbmUgdGhlIGdlbmVyYWwgcnVsZXMgZm9yIA0K
Pj4gY2FsY3VsYXRpbmcgY2VydGlmaWNhdGUgc2lnbmF0dXJlcz8gSSBhc3N1bWUgdGhleSBhcmUg
ZGVmaW5lZCANCj4+IHNvbWV3aGVyZSBlbHNlLCBhbmQgYXMgdGhleSBubyBsb25nZXIgaW1wYWN0
IHRoZSBmaW5nZXJwcmludHMgd2UgDQo+PiBkb27CuXQgbmVlZCB0byBpbmNsdWRlIHRoZW0uDQo+
IA0KPiBJIGRvbid0IHRoaW5rIHRoYXQgaXMgSm9uYXRoYW4ncyBwb2ludC4gIFRoZSBwb2ludCBp
cyB0aGF0IHdlIG5vIA0KPiBsb25nZXIgaGF2ZSB0ZXh0IHRoYXQgZXhwcmVzc2x5IGZvcmJpZHMg
YmFkIGhhc2hlcyAodG8gd2hpY2ggSSB3b3VsZCAtIA0KPiBjYXJlZnVsbHkgLSBhZGQgU0hBLTEp
LiAgU29tZXRoaW5nIGxpa2U6DQo+IA0KPiAgICBbLi4uXSB0aGUNCj4gICAgZGVmaW5lZCBoYXNo
IGZ1bmN0aW9ucyBhcmUgJ1NIQS0xJyBbMTFdIFsxOV0sICdTSEEtMjI0JyBbMTFdLA0KPiAgICAn
U0hBLTI1NicgWzExXSwgJ1NIQS0zODQnIFsxMV0sICdTSEEtNTEyJyBbMTFdLCAnTUQ1JyBbMTJd
LCBhbmQNCj4gICAgJ01EMicgWzEzXS4gIEltcGxlbWVudGF0aW9ucyBNVVNUIHByb3ZpZGUgYW5k
IHZhbGlkYXRlICdTSEEtMjU2Jy4NCj4gICAgVGhlICdNRDUnLCBhbmQgJ01EMicgZnVuY3Rpb25z
IGFyZSBjb25zaWRlcmVkIHdlYWsgYW5kIE1VU1QgTk9UIGJlIA0KPiB1c2VkLiAgVGhvdWdoICdT
SEEtMScgaXMgYWxzbyBjb25zaWRlcmVkIHdlYWssIGl0IE1BWSBiZSB1c2VkIHRvIA0KPiByZXRh
aW4gY29tcGF0aWJpbGl0eSB3aXRoIGV4aXN0aW5nIGltcGxlbWVudGF0aW9ucy4NCj4gDQo+IEkg
dGhpbmsgdGhhdCB0aGlzIGNhcHR1cmVzIHRoZSBpbnRlbnQ6IGlmIHlvdSBpbXBsZW1lbnQgdGhp
cyB1cGRhdGUsIA0KPiB5b3Ugd2lsbCB1c2UgU0hBLTI1Ni4gIEhvd2V2ZXIsIHdlIGNvbmNlZGUg
dGhhdCB5b3Ugd2lsbCBoYXZlIHRvIA0KPiBpbmNsdWRlIFNIQS0xIGFuZCB2ZXJpZnkgZmluZ2Vy
cHJpbnRzIGJhc2VkIG9uIGl0IGJlY2F1c2UgdGhlcmUgaXMgbm8gDQo+IG90aGVyIHdheSB0byB0
YWxrIHRvIGltcGxlbWVudGF0aW9ucyB0aGF0IGhhdmVuJ3QgaW1wbGVtZW50ZWQgdGhpcyANCj4g
dXBkYXRlLg0KPiANCj4gSSBhZ3JlZSB0aGF0IHdlIHNob3VsZG4ndCBzYXkgYW55dGhpbmcgYWJv
dXQgdGhlIHNpZ25hdHVyZSBpbiB0aGUgDQo+IGNlcnRpZmljYXRlLiAgSXQgZG9lc24ndCBoZWxw
IGF0IGFsbC4NCj4gDQo+Pj4gU0hBLTI1NiBpcyBvbmx5IMKzcHJlZmVycmVkwrIuICBEbyB3ZSB3
YW50IHRvIG1ha2UgaXRzIGluY2x1c2lvbiANCj4+PiBtYW5kYXRvcnksIG5vdyB0aGF0IHdlIHN1
cHBvcnQgbXVsdGlwbGUgYWxnb3JpdGhtcz8NCj4+IA0KPj4gTXkgc3VnZ2VzdGlvbiB3b3VsZCBi
ZSB0byBOT1QgbWFrZSBpdCBtYW5kYXRvcnksIGJlY2F1c2UgdGhhdCB3b3VsZCANCj4+IG1ha2Ug
ZXhpc3RpbmcgZW5kcG9pbnRzIHRoYXQgZG8gbm90IGluY2x1ZGUgaXQgbm9uLWNvbXBsaWFudC4N
Cj4gDQo+IE1VU1QgYW5kIE1VU1QgTk9UIGFyZSBvdXIgYmVzdCB0b29scyBoZXJlIGZvciBlbmNv
dXJhZ2luZyBwZW9wbGUgdG8gDQo+IGZpeCB0aGVpciBzb2Z0d2FyZS4gIEV4aXN0aW5nIGltcGxl
bWVudGF0aW9ucyB3aWxsIGJlIG5vbi1jb21wbGlhbnQgDQo+IHdpdGggdGhhdCBzcGVjLCBidXQg
aWYgdGhhdCBwcm92aWRlcyB0aGVtIGEgbGl0dGxlIGluY2VudGl2ZSB0byANCj4gdXBncmFkZSwg
dGhlbiB0aGF0IGlzIGdvb2QuICBUaGV5IHdpbGwsIG9mIGNvdXJzZSwgcmVtYWluIGNvbXBsaWFu
dCANCj4gd2l0aCA0NTcyLg0KDQo=


From nobody Tue May 24 11:08:10 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41DE112D96F for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 11:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOoBe212TOus for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 11:08:08 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6466E12D94B for <mmusic@ietf.org>; Tue, 24 May 2016 11:08:08 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by comcast with SMTP id 5GWVbltBnO4QF5GkRbTMP9; Tue, 24 May 2016 18:08:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464113287; bh=Il7a7W1jXFhMJl0i6g4d89QELC8E1dRnfv+aKaXO3u0=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=HYV9JVsVuiyI5KkWE4TtdKoVAINcXIlQr3QGERO0POT8hm42ZyAqhKLRVqSI+cbUS c2E78CQg2AhBGqdGafuw2mzmvbrbe3YhyTQ1mxu3N3O+QaL/w5yAwwqB9u53TDp2ZB dGSJ9+ZpCJTqiMsp4gYaZzgtdt2G7Jb/kYIdm7HNpYh3XEyIwK7DXwEW9n7XcvxEvD CD1KLYsjIlshlyx9W+RDLmv51HmJMk2pPoVnum8AughXkBAJtGSWALzYu6QhOrnngb X72spqfbGSbeABtcBCFlCcgi1pfTvyYDgCEF1g+v6tqeWzZMhFVdZrd5MA4Y+TD6zM P8j4b9UsOIZVQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-17v.sys.comcast.net with comcast id yJ871s0033KdFy101J87kT; Tue, 24 May 2016 18:08:07 +0000
To: Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu>
Date: Tue, 24 May 2016 14:07:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1BDfJu1cTTgZPdiOBmYIHDVO4ZU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 18:08:09 -0000

On 5/24/16 1:39 PM, Roman Shpount wrote:
> On Tue, May 24, 2016 at 12:39 PM, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>
>
>     I have a slight issue with how this was done. In section 5.1 is the
>     following new text:
>
>        When an answerer needs to establish a new DTLS association, if
>        unreliable transport is used, and if the offerer did not allocate a
>        new transport, the answerer MUST allocate a new transport for the
>        offer in answer a way that it can disambiguate any packets associated
>        with new DTLS association from any packets associated with any other
>        DTLS association.  This typically means using a local address and or
>        port, or a set of ICE candidates (see Section 6), which were not
>        recently used for any other DTLS association.
>
>     I agree with the point of this, but the qualifier "if unreliable
>     transport is used" doesn't seem to be the right one. I don't think
>     the issue has anything to do with unreliability. For instance I
>     don't think it would apply if using unreliable SCTP streams. I think
>     the real issue is that UDP is not a connection-oriented transport.
>
>     I'm not sure what language to use here that would cover the *right*
>     other non-UDP protocols. (AFAIK there are none that qualify.) If you
>     can't come up with something I guess I would make this UDP-specific.
>
>     Note there is similar text with the same problem in Section 6.
>
>
> This is actually the problem with either unreliable or un-ordered
> delivery properties of the protocol. If it is known that all packets for
> DTLS association have already been delivered (or failed to deliver) to
> the remote party, then this protocol can be reused for the new DTLS
> association. If it is known that DTLS packets for new association will
> be delivered after packets for old DTLS association, then transport can
> be reused for new DTLS association. For UDP, only the first condition
> can be satisfied, provided that reasonable time have passed since the
> last packet was sent and no packets for existing DTLS association are
> left in flight over the network. For SCTP, if receipt confirmation was
> received for all the DTLS packets for a given association, the same SCTP
> connection can be reused for the new DTLS association. If in-order SCTP
> channel is used for DTLS, then SCTP channel can also be reused for the
> new DTLS association.
>
> Taking a step back, there are three protocols which can be in used in
> practice to carry DTLS:
>
> 1. UDP
>
> 2. TCP with RFC 4571 framing. This protocol should be considered
> unreliable, non-connection oriented since it is typically used to bridge
> with UDP
>
> 3. SCTP. DTLS over SCTP is defined in RFC6083 and most likely broken. It
> is also, as far as know, is not used by anybody in conjunction with
> offer/answer.
>
> What we are trying to do in this paragraph is carve out DTLS over SCTP
> without explicitly naming it. Do you think it would be better if define
> this as "if unreliable or un-ordered transport is used"?

I'm happy if the words cover the specific relevant conditions. Given 
your explanation, I guess "unreliable or un-ordered" works.

I'm a little unclear about SCTP in this regard. IIUC RFC6083 does the 
DTLS setup over a reliable, ordered-delivery stream. So the concerns 
here wouldn't apply to it. So are you considering some other potential 
DTLS over SCTP mapping?

	Thanks,
	Paul


From nobody Tue May 24 11:41:04 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C06C12D099; Tue, 24 May 2016 11:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cNI7G6XTcrwA; Tue, 24 May 2016 11:40:59 -0700 (PDT)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F5B12D9CE; Tue, 24 May 2016 11:38:22 -0700 (PDT)
Received: by mail-qg0-x22c.google.com with SMTP id f92so11504645qgf.0; Tue, 24 May 2016 11:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Q9Vt4TzGIflytgqMFwL56Y+p7eKhpqKgBHvxWFWBey0=; b=SkTlK3isxqpE7RoRIDWe47UzQTDQDgib2q+J3nUh3ZOaWy0P07jfY3+82EXiJlcz/M NNmC3jaLcCnDebtFdj4qvl/hNDJsO8+4moee7+/o6fqQBKMwV9jf5UE7+q0lECP9fIV6 JeOMyZGBQtoEQlTOKIaa3SBc0OWgZ5YH/tvmUys08tFUsENjlwrDI1JArR87+uqQGzh1 R7BbZSQ58Q9HHkVDQzCC8OnpCS0bS4pIRrePFYCOgkerie9inpwl9ogQVh2oiHG/SpBo kbs3rXMH0KoWk4wcyszvqLKwWbU5qVlbJVsiSjx9e7nAUqpzZyrrceoUPbjIAwG/DNcw 0uwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Q9Vt4TzGIflytgqMFwL56Y+p7eKhpqKgBHvxWFWBey0=; b=OOtbg9s4hFGVrVv3CtHAt7LMj4NFEBjUXMSD/g8vDHhlaAazcMt51H4ffRtS64fRgA 26rZN+BJc1M0yHm8fxqSGuRk4hYXcmteC58jFyrC2C3btT+xuJ7PxqToUAwnulOvFaUv PeaMqYTTfeLKa24IhGPJlrzxJ9ZWFXa/nKT8iJt4RAugH6/qxLTcP2cCR+dkvdyKn/hX xc1wNT9NmPzW1jBb2I9SxAJmstTFkRSLdMbLM+86Rj/1T4oe77Ekb1mZ2dJDB8pT63NK Lb9zR9iJU2tXJAvrzMElDrGg6/JCpafjFLCLx7wXveKkML0dD41TG8/4j8L5/Kcg7os5 PCaA==
X-Gm-Message-State: ALyK8tKHX/LxgOCSUKDzfxKJwgX/1G+9XAYJ6oPB7DRi4eAvpYbTd4+Fyu2Dlrp/jtpi7SYLRXd8yVzIOHZ6Kg==
MIME-Version: 1.0
X-Received: by 10.140.32.198 with SMTP id h64mr4598654qgh.53.1464115101478; Tue, 24 May 2016 11:38:21 -0700 (PDT)
Received: by 10.140.104.70 with HTTP; Tue, 24 May 2016 11:38:21 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se>
Date: Tue, 24 May 2016 11:38:21 -0700
Message-ID: <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/G-tOk54H1GPzJjeHWJz7R6rnIk4>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 18:41:00 -0000

On 24 May 2016 at 10:49, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Does "provide" mean that endpoints MUST always, for each certificate, include a fingerprint calculated using SHA-256?
>
> Does "validate" mean the endpoints MUST always check the SHA-256-calculated fingerprint (if present) against the used certificate?


Yes and Yes.


From nobody Tue May 24 11:52:21 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA5312D906; Tue, 24 May 2016 11:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2mZNinlIg9a; Tue, 24 May 2016 11:51:43 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5995812B062; Tue, 24 May 2016 11:51:10 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-05-5744a29c4a5a
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A2.9D.18043.C92A4475; Tue, 24 May 2016 20:51:08 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0294.000; Tue, 24 May 2016 20:51:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ
Date: Tue, 24 May 2016 18:51:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com>
In-Reply-To: <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsUyM2K7ou6cRS7hBr8+6VscvLiM1eL9BV2L /YvPM1tcO/OP0WLq8scsDqweU35vZPXYOesuu8eSJT+ZPNqe3WEPYInisklJzcksSy3St0vg ypg9SbjgHkfFpytrWBsYD3B0MXJySAiYSBxZuJUNwhaTuHBvPZgtJHCEUWLtlvouRi4gewmj xLGju1i7GDk42AQsJLr/aYPUiAjoSiw6+4AdpIZZ4BCjxO2vCxhBEsIC9hIbn9xhgihykNj5 9ioLhB0lsbx7F1icRUBV4v/E9WA2r4CvxKJF/YwQy5YyS8y6exrsCk6BQIn1z+aBFTECXff9 1Bowm1lAXOLWk/lMEFcLSCzZc54ZwhaVePn4HyuErSSx6PZnJpCjmQU0Jdbv0odoVZSY0v2Q HWKvoMTJmU9YJjCKzUIydRZCxywkHbOQdCxgZFnFKFqcWlycm25kpJdalJlcXJyfp5eXWrKJ ERhrB7f8ttrBePC54yFGAQ5GJR7ehFrncCHWxLLiylxgQHEwK4nwSi50CRfiTUmsrEotyo8v Ks1JLT7EKM3BoiTO6/9SMVxIID2xJDU7NbUgtQgmy8TBKdXAqF+2pLdLeYPBVr8L1yUPKV31 jbyvuPLX3JSZ6x/dmHIub/J7Lvlo9m++SadZjvkarHiRoLLzBIOY+UzBp9sNLe43f98RZvir yHNtyvboUxsTb34+PZ3/c+XybkaPk/Kbp6Z3WWxYwRT31vrHn7K/qkvXlkgqfnrdeDp2rVOC T//PS8oby4TvqCuxFGckGmoxFxUnAgAyYNKEsQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/kK39N31F2W90GKqYqXqBXYBuAdg>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 18:52:04 -0000

U28sIGRvZXMgYW55b25lIG9iamVjdCB0byBNYXJ0aW4ncyBzdWdnZXN0aW9uPw0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWFydGlu
IFRob21zb24gW21haWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb21dIA0KU2VudDogMjQgTWF5
IDIwMTYgMjE6MzgNClRvOiBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJp
Y3Nzb24uY29tPg0KQ2M6IEpvbmF0aGFuIExlbm5veCA8am9uYXRoYW5AdmlkeW8uY29tPjsgRmxl
bW1pbmcgQW5kcmVhc2VuIDxmYW5kcmVhc0BjaXNjby5jb20+OyBkcmFmdC1pZXRmLW1tdXNpYy00
NTcyLXVwZGF0ZUBpZXRmLm9yZzsgbW11c2ljIDxtbXVzaWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBS
ZTogW01NVVNJQ10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUtMDMNCg0K
T24gMjQgTWF5IDIwMTYgYXQgMTA6NDksIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xt
YmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KPiBEb2VzICJwcm92aWRlIiBtZWFuIHRoYXQgZW5k
cG9pbnRzIE1VU1QgYWx3YXlzLCBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSwgaW5jbHVkZSBhIGZpbmdl
cnByaW50IGNhbGN1bGF0ZWQgdXNpbmcgU0hBLTI1Nj8NCj4NCj4gRG9lcyAidmFsaWRhdGUiIG1l
YW4gdGhlIGVuZHBvaW50cyBNVVNUIGFsd2F5cyBjaGVjayB0aGUgU0hBLTI1Ni1jYWxjdWxhdGVk
IGZpbmdlcnByaW50IChpZiBwcmVzZW50KSBhZ2FpbnN0IHRoZSB1c2VkIGNlcnRpZmljYXRlPw0K
DQoNClllcyBhbmQgWWVzLg0K


From nobody Tue May 24 11:54:34 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3C412D874 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 11:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XgNcwwhgJtnF for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 11:54:12 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8C6012D0A3 for <mmusic@ietf.org>; Tue, 24 May 2016 11:54:12 -0700 (PDT)
Received: by mail-ig0-x234.google.com with SMTP id fh2so16077211igd.1 for <mmusic@ietf.org>; Tue, 24 May 2016 11:54:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=BMMU+S9nE2i4glBdmzz3phVgAxSvXveZO4lgl5BnR2k=; b=hpKik2D7wUJuorxayeP5ndYrb6rQSszn8Xqaq2p1O5w5xlLHsaam8+K+VI7k2HQyWX iZrl4d8+EZ2D9n92dVXBQmthTNrvCUwPRJIKwlUFoNYpgCu2LrEZjfzUwRDfo2YZjKmQ TFqaDnbNoAi5Bv3K47OJMjPgswNwNiviFLMGOrZy50KZ7jV47LYPnnlUOIRad3JnK5nk sq5osx5ZlpgebgG5cxo7zZ9EJtJ9q2lyJG4g16QZIrsvWAGRuHp0O43J0EbRtmnMMNQ8 BU3N4lh/lfO1Kv1zOXDdrl/gmr0rbUQgZ16r/QxhSn0dPg9Y37AN10wmmtE2oWcGEVtu Ym9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=BMMU+S9nE2i4glBdmzz3phVgAxSvXveZO4lgl5BnR2k=; b=T7gBlMpfxIgdhVkM24Ou//aFk/17acsAwr+QGnov10Wz+BgCEX8mMP0QRNkbagKLDG shG1EdClU13RlV3e15RbPxvnXHe7azKmcLSOq969hJ4kxBKllwukqqbTrHkPDT/yfen2 rtwwHVBcPAL1V7t9AMSgYmHrVeqxtNWO++AYfUQXpOcamEyKdXWcvUlr97Ga4gYLtjL9 VvZaBYJVNE0vEIvTEsuAAIF307Jvy1K4lXKVxTKfU1vvHtgk2bSTGIWswcpU5OSibrJ4 HjLBNYLM7U3leOgRY0mpVR5WcO4Zcvw361LcSsefRyskSbnBdnu5CX4WsAUjj5I43YWO k3fg==
X-Gm-Message-State: ALyK8tK4RwkyBccB7vg2yuc55ZYOUQIOFDHhCFUWT7fzukcjpLl5Vl8V1wN3lA1Rafk1Fg==
X-Received: by 10.50.136.136 with SMTP id qa8mr14221318igb.62.1464116050455; Tue, 24 May 2016 11:54:10 -0700 (PDT)
Received: from mail-io0-f169.google.com (mail-io0-f169.google.com. [209.85.223.169]) by smtp.gmail.com with ESMTPSA id u66sm1515400itc.21.2016.05.24.11.54.09 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 11:54:09 -0700 (PDT)
Received: by mail-io0-f169.google.com with SMTP id t40so18143991ioi.0; Tue, 24 May 2016 11:54:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.160.76 with SMTP id j73mr309476ioe.66.1464116049223; Tue, 24 May 2016 11:54:09 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 24 May 2016 11:54:09 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se>
Date: Tue, 24 May 2016 14:54:09 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com>
Message-ID: <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114027b806684805339b157b
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/XJFOYwPYFDs9AAofcUxDt2SxBgQ>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 18:54:27 -0000

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

What if I already to include SHA-384 or SHA-512, do I still MUST include
SHA-256?

Regards,
_____________
Roman Shpount

On Tue, May 24, 2016 at 2:51 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> So, does anyone object to Martin's suggestion?
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: Martin Thomson [mailto:martin.thomson@gmail.com]
> Sent: 24 May 2016 21:38
> To: Christer Holmberg <christer.holmberg@ericsson.com>
> Cc: Jonathan Lennox <jonathan@vidyo.com>; Flemming Andreasen <
> fandreas@cisco.com>; draft-ietf-mmusic-4572-update@ietf.org; mmusic <
> mmusic@ietf.org>
> Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
>
> On 24 May 2016 at 10:49, Christer Holmberg <christer.holmberg@ericsson.com>
> wrote:
> > Does "provide" mean that endpoints MUST always, for each certificate,
> include a fingerprint calculated using SHA-256?
> >
> > Does "validate" mean the endpoints MUST always check the
> SHA-256-calculated fingerprint (if present) against the used certificate?
>
>
> Yes and Yes.
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">What if I already to include SHA-384 or SHA-512, do I stil=
l MUST include SHA-256?<div><br></div><div>Regards,<div class=3D"gmail_extr=
a"><div><div class=3D"gmail_signature">_____________<br>Roman Shpount</div>=
</div>
<br><div class=3D"gmail_quote">On Tue, May 24, 2016 at 2:51 PM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">So, does anyone object to Martin&#39;s su=
ggestion?<br>
<br>
Regards,<br>
<br>
Christer<br>
<span class=3D"im HOEnZb"><br>
-----Original Message-----<br>
From: Martin Thomson [mailto:<a href=3D"mailto:martin.thomson@gmail.com">ma=
rtin.thomson@gmail.com</a>]<br>
Sent: 24 May 2016 21:38<br>
To: Christer Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com"=
>christer.holmberg@ericsson.com</a>&gt;<br>
Cc: Jonathan Lennox &lt;<a href=3D"mailto:jonathan@vidyo.com">jonathan@vidy=
o.com</a>&gt;; Flemming Andreasen &lt;<a href=3D"mailto:fandreas@cisco.com"=
>fandreas@cisco.com</a>&gt;; <a href=3D"mailto:draft-ietf-mmusic-4572-updat=
e@ietf.org">draft-ietf-mmusic-4572-update@ietf.org</a>; mmusic &lt;<a href=
=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;<br>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03<br>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">On 24 May 2016 at 10:49, Chr=
ister Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christ=
er.holmberg@ericsson.com</a>&gt; wrote:<br>
&gt; Does &quot;provide&quot; mean that endpoints MUST always, for each cer=
tificate, include a fingerprint calculated using SHA-256?<br>
&gt;<br>
&gt; Does &quot;validate&quot; mean the endpoints MUST always check the SHA=
-256-calculated fingerprint (if present) against the used certificate?<br>
<br>
<br>
Yes and Yes.<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div></div></div>

--001a114027b806684805339b157b--


From nobody Tue May 24 12:05:42 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1DE12D9BA for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 12:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MVnNV0XRJI98 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 12:05:38 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A7E512D9AB for <mmusic@ietf.org>; Tue, 24 May 2016 12:05:38 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id j1so42326992oih.3 for <mmusic@ietf.org>; Tue, 24 May 2016 12:05:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=JkSPSQgeTcyUfe7N1ODDixjW/8BEqlOLVxE1ne+eCzo=; b=MQBTTC7jWLtq8jhT6u4UrTP+FlwdhdJ34xu3D93BckycuHmGjJZTV3FhVirJClxqR7 Yz5w04APkVHTIKU5xBly+f0ubHMzjKjooMIsBzJHD3aCZs6t4yC5woLrMtxzWFnWVzJo 5t8Hq6ABnvHuv84eyBrD4XEo+fhW16QNCm2Hia+q26Olxv7a2kb/EHmvJgAqWspF6Ax+ UdZlSHlAEMqVL0sJxAuraJLIdks/rXoc5UoiVsRZgkWCasDc8pyNUXNrvOanigcX+GGD rhqJYXkFQb2fe3EsB7DIr/p4vpRT8pmB/XeeWOBlXodizk0kRSp0K50VegmQXKD1c4Jt Ww1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=JkSPSQgeTcyUfe7N1ODDixjW/8BEqlOLVxE1ne+eCzo=; b=dXa/D3/aNHj09UxWPxV6dZr4sdGivD1GclY1Ra5eGprJp6f4SRxSuO7PS7uOjRnwWT iXJW57pJQLxfi1G+aQ2glDdFWFfQ+heNmJlEWJX/pp/hm9hp1WW6ERCQ94lw0WWv8YIc 91tNDQva73i++zHfyaljwLBVrk8WclkCjKhrYkaWgGvdSvD3o20edb3iWMlVQ58cUeXf 6S+8SborUGmYY5+5sShawCSB3u12WtcJtWLytJssQYZQud7rz3Yyp3LbJIC+/dPsObE0 FwZpEeWLZybuId+lDepOdMG0GxoEBFsq2qx0bW7g6OW2NvbjYUiuczQmOOM1PdNAHSMs hTjg==
X-Gm-Message-State: ALyK8tKCGPzxPMzLXqncefZ9ShNN169D7GQ0xwu5ZHsK+dP+9wRWE16RucUtTUHExYvJlQ==
X-Received: by 10.202.171.143 with SMTP id u137mr9176476oie.71.1464116737570;  Tue, 24 May 2016 12:05:37 -0700 (PDT)
Received: from mail-ig0-f180.google.com (mail-ig0-f180.google.com. [209.85.213.180]) by smtp.gmail.com with ESMTPSA id l103sm2040067otl.5.2016.05.24.12.05.37 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 12:05:37 -0700 (PDT)
Received: by mail-ig0-f180.google.com with SMTP id ww4so58132268igb.1 for <mmusic@ietf.org>; Tue, 24 May 2016 12:05:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.136.228 with SMTP id qd4mr18519923igb.42.1464116736769; Tue, 24 May 2016 12:05:36 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 24 May 2016 12:05:36 -0700 (PDT)
In-Reply-To: <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu>
Date: Tue, 24 May 2016 15:05:36 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com>
Message-ID: <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=089e0122aa56017aea05339b3eb1
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/z34EXulPLJ0xBPxtMKugCIFjz0I>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 19:05:39 -0000

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

On Tue, May 24, 2016 at 2:07 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> I'm happy if the words cover the specific relevant conditions. Given your
> explanation, I guess "unreliable or un-ordered" works.
>
> I'm a little unclear about SCTP in this regard. IIUC RFC6083 does the DTLS
> setup over a reliable, ordered-delivery stream. So the concerns here
> wouldn't apply to it. So are you considering some other potential DTLS over
> SCTP mapping?
>

This is exactly what I am saying: If DTLS is running over SCTP with
reliable, ordered delivery stream, then DTLS packet disambiguation is not a
problem and new DTLS association can always be established over an existing
transport. In fact RFC6083 says that SCTP should be reused for new DTLS
associations. Because of this, if answerer wants to establish a new DTLS
association and offer contains an SCTP transport, answerer can reuse the
SCTP transport for new DTLS association.

If DTLS is running over UDP (unreliable and un-ordered), transport
disambiguation concerns do apply. This means either offerer or answerer
MUST allocate new address/port or set of candidates when new DTLS
association is established. Furthermore, if ICE is used and offerer did not
initiate an ICE restart, new DTLS association MUST NOT be  established,
since new transport cannot be allocated and packets cannot be disambiguated.

Regards,
______________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, May 24, 2016 at 2:07 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<a href=3D"=
mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-colo=
r:rgb(204,204,204);padding-left:1ex">I&#39;m happy if the words cover the s=
pecific relevant conditions. Given your explanation, I guess &quot;unreliab=
le or un-ordered&quot; works.<br>
<br>
I&#39;m a little unclear about SCTP in this regard. IIUC RFC6083 does the D=
TLS setup over a reliable, ordered-delivery stream. So the concerns here wo=
uldn&#39;t apply to it. So are you considering some other potential DTLS ov=
er SCTP mapping?<br></blockquote><div><br></div><div>This is exactly what I=
 am saying: If DTLS is running over SCTP with reliable, ordered delivery st=
ream, then DTLS packet disambiguation is not a problem and new DTLS associa=
tion can always be established over an existing transport. In fact RFC6083 =
says that SCTP should be reused for new DTLS associations. Because of this,=
 if answerer wants to establish a new DTLS association and offer contains a=
n SCTP transport, answerer can reuse the SCTP transport for new DTLS associ=
ation.</div><div><br></div><div>If DTLS is running over UDP (unreliable and=
 un-ordered), transport disambiguation concerns do apply. This means either=
 offerer or answerer MUST allocate new address/port or set of candidates wh=
en new DTLS association is established. Furthermore, if ICE is used and off=
erer did not initiate an ICE restart, new DTLS association MUST NOT be =C2=
=A0established, since new transport cannot be allocated and packets cannot =
be disambiguated.</div><div><br></div><div>Regards,</div><div>_____________=
_</div><div>Roman Shpount=C2=A0</div></div></div></div>

--089e0122aa56017aea05339b3eb1--


From nobody Tue May 24 12:55:06 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6763412D504; Tue, 24 May 2016 12:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRq0EzN9h-7g; Tue, 24 May 2016 12:54:56 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5BB312D13D; Tue, 24 May 2016 12:54:55 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id x7so19615838qkd.3; Tue, 24 May 2016 12:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=qW/bh3ni6IcVZZKJdgUqH8VJvX4L5MNOus3NYi8WeEY=; b=mWaKJeEK1/wsAqzUE6Kz5MnwEXrZZejbCsjdU0b4w/0tdZDXr95dIz1ElRhSbPzf0d j8Kn2zrtlwTM/ZYDd+eRK2pUk24ge0X02ESHIbCw+1g+RaCUo/jSxeQFN7L+2ECRClKX jHr/JMShof/nMjim6FCjnNl9JxTsOKvloCVK9l1t1tOmOYDwQKu1I7q6Di1IRElYL/Lw iDl18Z5NVMk4HfghDwVanMMMqfm/yqQpwNClnnZUT7q3sIHAeGo51TX7Jlcn/WT/pLOT XouB2LJn68Rvp0o7owuOMdV7wJV3oNjpKUMVzvCzWSzFE4oscfTMvWbqBBXm7BZR1C3f Y3pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=qW/bh3ni6IcVZZKJdgUqH8VJvX4L5MNOus3NYi8WeEY=; b=LFvBApoCA9O4Z7wi4MMQm5QkB/RfV3noEvnp6Rs3dk3gUcltOAF4sYQeBlOK06j619 5uNm6LQZFQbWE31/u989eduj9kEVgfPgJVqxq0ONr9CerBS4+xlL0ESk2uBXCxw62kNu bhytrOo6BrOWQCpsxNSA395h7ov822PCjhiYQ4L8USc5DuTCsJcZr1D6eSTAr53x2nck j/QUxfeUBWMUATgcIhAeIt6nO/E1Ho6V6u2+Kg/iBcxy5dak7G3T9gD7CT4AcdLNjhk7 JqQDVzhR4xGZ+zPLhgqug/bSfaElE+i889twnewmQvYbGu+polgoEgUPb/3Nvbz7kTdc gIjg==
X-Gm-Message-State: ALyK8tJsq2Kwm+JSElRXmqz6B42s8sWfqSMQH2giA9xpFvb9zuPlxm7jo0LOTGifNoRo0B4G9FfXp70/Cumexw==
MIME-Version: 1.0
X-Received: by 10.200.37.124 with SMTP id 57mr6014417qtn.40.1464119695021; Tue, 24 May 2016 12:54:55 -0700 (PDT)
Received: by 10.140.104.70 with HTTP; Tue, 24 May 2016 12:54:54 -0700 (PDT)
In-Reply-To: <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com>
Date: Tue, 24 May 2016 12:54:54 -0700
Message-ID: <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/VqZj0k8EPU-wHjOIta2PjVHaHLQ>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 19:55:04 -0000

On 24 May 2016 at 11:54, Roman Shpount <roman@telurix.com> wrote:
> What if I already to include SHA-384 or SHA-512, do I still MUST include
> SHA-256?

Do you like interoperability?  Then yes.  Otherwise, don't let a mere
RFC tell you what to do.


From nobody Tue May 24 13:06:18 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E301612D0FC for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iyz2oJFxLrAy for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:06:14 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C9BF12D0B8 for <mmusic@ietf.org>; Tue, 24 May 2016 13:06:14 -0700 (PDT)
Received: from resomta-ch2-11v.sys.comcast.net ([69.252.207.107]) by comcast with SMTP id 5IUzbXCkEp1Be5IajbIAxN; Tue, 24 May 2016 20:06:13 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464120373; bh=P/fnij1THCj2L4xO6qkaY87euMbH8gvEdgHXC5bdo5I=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=vwPK9OghABRlqsj/mf1KIUi10Mk7llI1Iqy9W6CFeCCyFABn0pIgIMxPSW6bbwMTV GMLiVwmIiRXTjhzAFTiO0C/o9cjtldzSILHHj6idVj6kJLwYVCY8iGld8jlmK6353V QJUnvQsVGwqXNkpDynzjnMd3OSeGTSNJm2Pru4yz2I2O+qpI8MHo5/owhWy3f1bSdH N6VgOL3RpJHNHesYFP+r89GEWdfsU+m7eO6ZvQqOzvyMKe4xi4AsFNfAmvMZWUO+bF KCJNh7VVTjp1f4oYKtTDwPbltZZv8Qes7sGH+IT8JkE3OEgVsZkZJKTn4cNxSplDGq 3rn8n/S29mgaw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-11v.sys.comcast.net with comcast id yL6D1s00K3KdFy101L6DlP; Tue, 24 May 2016 20:06:13 +0000
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu>
Date: Tue, 24 May 2016 16:05:56 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/54Cjs4R22YkgtQDBSNijMKEHlRY>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:06:16 -0000

On 5/24/16 3:05 PM, Roman Shpount wrote:
> On Tue, May 24, 2016 at 2:07 PM, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
>
>     I'm happy if the words cover the specific relevant conditions. Given
>     your explanation, I guess "unreliable or un-ordered" works.
>
>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>     the DTLS setup over a reliable, ordered-delivery stream. So the
>     concerns here wouldn't apply to it. So are you considering some
>     other potential DTLS over SCTP mapping?
>
>
> This is exactly what I am saying: If DTLS is running over SCTP with
> reliable, ordered delivery stream, then DTLS packet disambiguation is
> not a problem and new DTLS association can always be established over an
> existing transport. In fact RFC6083 says that SCTP should be reused for
> new DTLS associations. Because of this, if answerer wants to establish a
> new DTLS association and offer contains an SCTP transport, answerer can
> reuse the SCTP transport for new DTLS association.
>
> If DTLS is running over UDP (unreliable and un-ordered), transport
> disambiguation concerns do apply. This means either offerer or answerer
> MUST allocate new address/port or set of candidates when new DTLS
> association is established. Furthermore, if ICE is used and offerer did
> not initiate an ICE restart, new DTLS association MUST NOT be
>  established, since new transport cannot be allocated and packets cannot
> be disambiguated.

So there is no known transport, other than UDP, where this concern applies?

	Thanks,
	Paul


From nobody Tue May 24 13:08:12 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 459DD12D16A for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7PpKSLzmyCk8 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:08:05 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B47CE12D1C8 for <mmusic@ietf.org>; Tue, 24 May 2016 13:06:42 -0700 (PDT)
Received: by mail-ig0-x22a.google.com with SMTP id bi2so59248240igb.0 for <mmusic@ietf.org>; Tue, 24 May 2016 13:06:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=KA3dCD5GzYcCmfqvO753pTdSL7AgDFKkSkxY029n6rU=; b=HVzF1IbDEe2FtSJLKavPHID5yU2asaqlJZb660lFn9bSqlIekBB2PZw9wqJrdIbFuH 5t3eth7hAfdhdC7iVAHP/Ox2zNmihcj+8OPYPyKhxtyXB3O9ISUHx3ZQEWuMhtL+VPbM FpQe8UOLEk1VTnjilL0wzOcaboNyFoS8a0PJ4QUiFRN4ItFK8eeXrQWRao4ktoTcnZxp A4Sp1tlYTgDlO8pWJEgUt2Qit5TxOQK046y8KtcTLeKCCevvBQ6aXEx4ZJm6n2QATKbw nMOZKJvGO2aFEhWRkifceHDO47br7LQFKRvtBeV5twONYNqqTFXMtWSDsIY4K63QR/ee NwMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=KA3dCD5GzYcCmfqvO753pTdSL7AgDFKkSkxY029n6rU=; b=D67YMeMHobQw6k+ALPbNGPDiYE/htO4yt0dsky7HeWcjOjqvNSxtZOo/NUXyPQ8So9 PyUrvX1ORlC5OnAeLg8OZMtH47hdQYHl5hxe9x2gxuXQpzBNwMhddD0Ork3Q9ArK8EMM qH+nxKlym0M0mW8VSSIrrgp8yjkL6gIkRa6k9iQB8WQ3eSqq/APkw1KKs/dddIXLPNx+ 7Yz+wWahTIkQ9+NkULLrInGDIy5JAE/V/iGX2B5Hcp5gv6v2rismYNhIj0d8LV6Avsek FvN2Q9Xia/xEC+6Zo87U+Ate7Yi1D7qzAWlkzFXoF15YlAbvAV/0OvhcFQmSoLHDXWcG RTGg==
X-Gm-Message-State: AOPr4FVc8mFelwau9lhyxawHmaGNwwjoQN6m9F/rfvGppQYJU6t2V8DcaK2RPtWO7Q5Dow==
X-Received: by 10.50.187.133 with SMTP id fs5mr18277580igc.61.1464120401873; Tue, 24 May 2016 13:06:41 -0700 (PDT)
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com. [209.85.213.179]) by smtp.gmail.com with ESMTPSA id 70sm1629566ioz.16.2016.05.24.13.06.41 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 13:06:41 -0700 (PDT)
Received: by mail-ig0-f179.google.com with SMTP id bi2so59247916igb.0; Tue, 24 May 2016 13:06:41 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.136.228 with SMTP id qd4mr18726878igb.42.1464120400899; Tue, 24 May 2016 13:06:40 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 24 May 2016 13:06:40 -0700 (PDT)
In-Reply-To: <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com>
Date: Tue, 24 May 2016 16:06:40 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtM_XmP0dWJuWa4Du2_g3sXE0BLzhN-8LWfPU01raRAow@mail.gmail.com>
Message-ID: <CAD5OKxtM_XmP0dWJuWa4Du2_g3sXE0BLzhN-8LWfPU01raRAow@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=089e0122aa5667c48f05339c1810
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ATYZLSGjMHaQgKx3vHKhymgwdQ0>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:08:07 -0000

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

On Tue, May 24, 2016 at 3:54 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 24 May 2016 at 11:54, Roman Shpount <roman@telurix.com> wrote:
> > What if I already to include SHA-384 or SHA-512, do I still MUST include
> > SHA-256?
>
> Do you like interoperability?  Then yes.  Otherwise, don't let a mere
> RFC tell you what to do.
>

So, based on your proposal I should include SHA-1 for backwards interop,
SHA-256 for current and SHA-384 or SHA-512 for future.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Tue, May 24, 2016 at 3:54 PM, Martin Thomson <span dir=3D"ltr">&lt;=
<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomso=
n@gmail.com</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);=
padding-left:1ex"><span class=3D"">On 24 May 2016 at 11:54, Roman Shpount &=
lt;<a href=3D"mailto:roman@telurix.com">roman@telurix.com</a>&gt; wrote:<br=
>
&gt; What if I already to include SHA-384 or SHA-512, do I still MUST inclu=
de<br>
&gt; SHA-256?<br>
<br>
</span>Do you like interoperability?=C2=A0 Then yes.=C2=A0 Otherwise, don&#=
39;t let a mere<br>
RFC tell you what to do.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">So, based on your p=
roposal I should include SHA-1 for backwards interop, SHA-256 for current a=
nd SHA-384 or SHA-512 for future.</div><div class=3D"gmail_extra"><div><div=
 class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><div><=
br></div></div></div>

--089e0122aa5667c48f05339c1810--


From nobody Tue May 24 13:11:15 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5507D12D0FC for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYoAsqObfTM9 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:11:03 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94D9112D817 for <mmusic@ietf.org>; Tue, 24 May 2016 13:10:00 -0700 (PDT)
Received: from resomta-ch2-17v.sys.comcast.net ([69.252.207.113]) by comcast with SMTP id 5IU2buWg3fr8T5Ie1bggPX; Tue, 24 May 2016 20:09:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464120577; bh=AMBWulU8uGNOthTYhtYin8jfGReaoz3VK8t8jUmEj2s=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=ZNFU36QPhr6n5Q6Hz0lMpagRIyHWgmiZ3NaFb07zKgmgbsBtiiMH9CSXfdq/mCBJo GmPO7cMemv7r/5elBIDh1ByVYfR9sHnhh8Nec8Bay+KRrwgeK4tyUX+6Dk7kn3Zum8 ouUam6HKeQ5yg9+Vgcf16ovrBR3x4qU8pWRg8ZNIsqrMgA62jbZtL1EcfFnxSAJB4t c1jM85dFuEdFDjSC45O3eEZbhUZgEhCxXqdr326VweMJSB/76NZOGIwN24gwtvKMgq qoyWP4Ow0D0vNzb7Y2vQVQ80jrbok1qPw20tLcetQuUgCbpfmvOfo1WQ9RGxRO54Cp mDqTwHjdMhRKA==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-17v.sys.comcast.net with comcast id yL9d1s00J3KdFy101L9dNV; Tue, 24 May 2016 20:09:37 +0000
To: mmusic@ietf.org
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu>
Date: Tue, 24 May 2016 16:09:19 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/8b6YYqGiZOB21MS1i7c4B4_eGkk>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:11:04 -0000

On 5/24/16 3:54 PM, Martin Thomson wrote:
> On 24 May 2016 at 11:54, Roman Shpount <roman@telurix.com> wrote:
>> What if I already to include SHA-384 or SHA-512, do I still MUST include
>> SHA-256?
>
> Do you like interoperability?  Then yes.  Otherwise, don't let a mere
> RFC tell you what to do.

So this RFC will need to be revised when SHA-256 is broken and no longer 
safe to use?

ISTM that the general mechanism for multiple fingerprints ought to be 
separate from the (transient) recommendations of particular crypto 
algorithms.

	Thanks,
	Paul


From nobody Tue May 24 13:11:32 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC18212D0FC for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmbraHM4VaMI for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:11:09 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D6012D1C8 for <mmusic@ietf.org>; Tue, 24 May 2016 13:10:01 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-59-5744b50dd885
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 87.7F.12516.D05B4475; Tue, 24 May 2016 22:09:49 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0294.000; Tue, 24 May 2016 22:09:49 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
Thread-Index: AdGzeadT9Biiw5sKQwmLHX/vhwcvDQCUFxUAAAIcngAAAP0FAAACBMYAAAIbbAAABEscMA==
Date: Tue, 24 May 2016 20:09:49 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FE70BB@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com> <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu>
In-Reply-To: <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyM2K7qC7vVpdwg1PvzSymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj2JMDTAWHeCqW7/vJ3MDYytXFyMkhIWAi sWPKVVYIW0ziwr31bCC2kMARRonXO4Qg7CWMEtO2cHcxcnCwCVhIdP/TBgmLCPhKPHt8G6xc WMBNonXTamaIuLvE1TubmEHKRQTCJG49dwEJswioSjxraAMr4QVqbfr+mxFi+l8miSf/OUBs TgEHieYtc8FGMgJd8/3UGiYQm1lAXOLWk/lMEFcKSCzZc54ZwhaVePn4H9T1ShKLbn+GqteR WLD7ExuErS2xbOFrqL2CEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypG0eLU4uLcdCNjvdSi zOTi4vw8vbzUkk2MwAg5uOW37g7G1a8dDzEKcDAq8fAm1DqHC7EmlhVX5h5ilOBgVhLh/b7Z JVyINyWxsiq1KD++qDQntfgQozQHi5I4r/9LxXAhgfTEktTs1NSC1CKYLBMHp1QDo/yuvoJ5 Za8/MGy0a7T1nW10ifPjwYLJEovf7Lmd5FgS8PumpZxISJ4yQ7rtMlaZd2WbbNq5vr/Q2dCn 9MC5Jveqv66JXEIXK7MMY92+qtoN5/76NzWUsRZ1fp+4/fNGiw2LhHWCEkMa4gVVRN989dDd du5lwMqzNnWCWr9d2/37LoWZu+YpsRRnJBpqMRcVJwIAJtHmLYwCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1zrIJ8rt7Xr98yCra5MJ6ASbQ-A>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:11:16 -0000

Hi,

>>     I'm happy if the words cover the specific relevant conditions. Given
>>     your explanation, I guess "unreliable or un-ordered" works.
>>
>>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>>     the DTLS setup over a reliable, ordered-delivery stream. So the
>>     concerns here wouldn't apply to it. So are you considering some
>>     other potential DTLS over SCTP mapping?
>>
>>
>> This is exactly what I am saying: If DTLS is running over SCTP with=20
>> reliable, ordered delivery stream, then DTLS packet disambiguation is=20
>> not a problem and new DTLS association can always be established over=20
>> an existing transport. In fact RFC6083 says that SCTP should be reused=20
>> for new DTLS associations. Because of this, if answerer wants to=20
>> establish a new DTLS association and offer contains an SCTP transport,=20
>> answerer can reuse the SCTP transport for new DTLS association.
>>
>> If DTLS is running over UDP (unreliable and un-ordered), transport=20
>> disambiguation concerns do apply. This means either offerer or=20
>> answerer MUST allocate new address/port or set of candidates when new=20
>> DTLS association is established. Furthermore, if ICE is used and=20
>> offerer did not initiate an ICE restart, new DTLS association MUST NOT=20
>> be  established, since new transport cannot be allocated and packets=20
>> cannot be disambiguated.
>
> So there is no known transport, other than UDP, where this concern applie=
s?

You can have unreliable/unordered SCTP too, can't you?

Regards,

Christer


From nobody Tue May 24 13:12:45 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E7512D1DF; Tue, 24 May 2016 13:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xspp6IvX1PAC; Tue, 24 May 2016 13:12:01 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9898E12D1B4; Tue, 24 May 2016 13:11:23 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id x7so19970019qkd.3; Tue, 24 May 2016 13:11:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=hz0hXv2lPNfqg3o/Y1Ugi3I69Ntjce1Pswcdk0KFup4=; b=y0iyWBjBbXTOejOslR7/2CIyPEElGCGImm0xCWXkgSDcaGHjAiBiM4zbL4PY0QsxJi XqseO0CfJGBw0t1Iv85RJKCHWFVAEtUAVko1i34SAlx4BFzbXeU2x1wONadP0bMLSOJa ww9DK+mv0W76EuxxmuKOcBjeyxkryDlr1u/WbSv69Wi0VU3c4UINrAFJ4jQhCogdfASp 6zrFCRn3FQuPMf6vIUmXzt37AkpUNQ1Cz0QKEUJe4lRY2V9qDZic81tvStnkPpCZGLgf A5ZfvgsnxCytemjsZhp03683Ueqda0/WPhlkR5IZGyE8C++l0+oXeRQ8PeozvDl2yKoU KLpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=hz0hXv2lPNfqg3o/Y1Ugi3I69Ntjce1Pswcdk0KFup4=; b=ik8C8qQIa34EmyKV/vdtBJVyjO297HE7oIzOjDIYDTUlVfogvb2k+MW42RxhB7ErzH 1yvC6EOnh0T/v9hR8Uo8i86WZKChzagnxkz1846ZkX4axLF0AFbcG8HMODhVIJ8CZxTO 9NzvHdcxdlToWgT+4cziBohS0c4v6wlrzFLWQe5AqvA4Uo14Fy1Zx/rnDJft48O6pTlc 85NenX7aQO2xNlnKSHze2NoCd4bFiv2LkspkA/2+wxZFQG8eVYLx8Py3H9LXowzPKJXa 0ZcuZrWzls5dHBM8278Nyfp5vbr/j8mcsCys/4fVpN0ivQgLw4WH2p+59cOP1K69C7eZ +vWw==
X-Gm-Message-State: ALyK8tL0BecQw+l5a/4LePziuD6oRTsQzT+2gpChuVu4cXg36KOq3FhxhoXs6BUMJYwT+Fd15AQbvslqW1sZSw==
MIME-Version: 1.0
X-Received: by 10.55.138.194 with SMTP id m185mr67903qkd.48.1464120682702; Tue, 24 May 2016 13:11:22 -0700 (PDT)
Received: by 10.140.104.70 with HTTP; Tue, 24 May 2016 13:11:22 -0700 (PDT)
In-Reply-To: <CAD5OKxtM_XmP0dWJuWa4Du2_g3sXE0BLzhN-8LWfPU01raRAow@mail.gmail.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <CAD5OKxtM_XmP0dWJuWa4Du2_g3sXE0BLzhN-8LWfPU01raRAow@mail.gmail.com>
Date: Tue, 24 May 2016 13:11:22 -0700
Message-ID: <CABkgnnUWuGjJ_ag4AOioqc87+XkZWt8XcnqKczfzVroFkxq24Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/tLgNco2RJdOQt6Cei3X1MWcj9dg>
Cc: Flemming Andreasen <fandreas@cisco.com>, Jonathan Lennox <jonathan@vidyo.com>, "draft-ietf-mmusic-4572-update@ietf.org" <draft-ietf-mmusic-4572-update@ietf.org>, mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:12:08 -0000

On 24 May 2016 at 13:06, Roman Shpount <roman@telurix.com> wrote:
> So, based on your proposal I should include SHA-1 for backwards interop,
> SHA-256 for current and SHA-384 or SHA-512 for future.

Well, the SHA-384 and SHA-512 is your prediction, but if you believe
that they are (or will be) necessary, sure.

I'd have said firstly that they won't be needed, and that only one of
them is likely to be needed if they are.  But I'm willing to accept
the possibility that I'm wrong, and that is why we have an extension
point here.  I wouldn't start using SHA-512 right away though.


From nobody Tue May 24 13:13:14 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6751312D782 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KVRqMrzp1UXL for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:12:34 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C891112D0FC for <mmusic@ietf.org>; Tue, 24 May 2016 13:11:27 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id j1so45199744oih.3 for <mmusic@ietf.org>; Tue, 24 May 2016 13:11:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=TUI9wclFma+jFqLsWHBclt/l3IJ6EocXEnlMTmTgR0E=; b=0FfcQ/w1IAssF3mIy8WXgkFDMbKdQQbLP2MPi5dTDnt5NWufYWr1M4ZO1IHO/Edyhp OI+cxZyXEbMmzdPXPRlRD16AG1xITqADh/8rBybQQyUMwEPvUwlz+IRWuyFP5vI97sjD 3MSJ319QT/tUFLoI64WyPYOHYkTgUSvRnIMDdlDXqSotN46dFCzBJcCcCOI/ygtdikKG X9eExV9RVDyfpOljPVlIAWGIDKjiahqPuAJOYa2HnJorA7dwyydWV27r1qEKtyqnNG47 zcT/2RtmvGI4du0ehn/9sqhA6eReSDkEfCi7goLsq5sa0rzHeY16K8i2MAvyvkuvV0Hj ZxcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=TUI9wclFma+jFqLsWHBclt/l3IJ6EocXEnlMTmTgR0E=; b=W40e1m11fDaHqnyXh1ayYX00T3ffVjOtdePFAK5sp+8v5NKk/sdWVY6px8ObQRoEdx D3IcsJ7y8Jir9zqivfzj7dNda59PrfZoc/5CrHGZ0ecJAJ0oE6sYhf2m++m7+i/xwD7C saC6hkFNblsPOe/Bo/LxPgRhXcyQ8Wn4uvEqaxn3Lp3U7DVV6Kg9ARrjbtl5QfRCnk8h hT4ROXx35GyCVTdxZb76t2Lqtzylpp8E0Dnyj5yMTXC1eSYYqFgbLFUm1XD4+pmRV+NR CFDEbt22kO99E9n3ZpC7sBbD1QNszQ9o9KvNzaWpbadsFAOoYCco36B955DGh68Tzmjz Q/2w==
X-Gm-Message-State: ALyK8tLkb2RKSufkDD9Dp64nj2yOL6kGzyoi4tNwcf8RM24kQZPDkxl9cuyx4wO86mlRBA==
X-Received: by 10.202.236.135 with SMTP id k129mr7543756oih.161.1464120687075;  Tue, 24 May 2016 13:11:27 -0700 (PDT)
Received: from mail-it0-f45.google.com (mail-it0-f45.google.com. [209.85.214.45]) by smtp.gmail.com with ESMTPSA id s107sm2187079ota.4.2016.05.24.13.11.26 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 13:11:26 -0700 (PDT)
Received: by mail-it0-f45.google.com with SMTP id e62so58759553ita.1 for <mmusic@ietf.org>; Tue, 24 May 2016 13:11:26 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.155.132 with SMTP id o126mr19332136itd.95.1464120686209;  Tue, 24 May 2016 13:11:26 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 24 May 2016 13:11:26 -0700 (PDT)
In-Reply-To: <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com> <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu>
Date: Tue, 24 May 2016 16:11:26 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvQxc+Uh4iJrDvbPwbATtA26SNc429UX3c6k+ktwr=FDg@mail.gmail.com>
Message-ID: <CAD5OKxvQxc+Uh4iJrDvbPwbATtA26SNc429UX3c6k+ktwr=FDg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=94eb2c05d15869142a05339c29b2
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/hiRiQe1JPU69vMLlBOaV9lSwgxI>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:12:50 -0000

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

On Tue, May 24, 2016 at 4:05 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 5/24/16 3:05 PM, Roman Shpount wrote:
>
>> On Tue, May 24, 2016 at 2:07 PM, Paul Kyzivat <pkyzivat@alum.mit.edu
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>
>>     I'm happy if the words cover the specific relevant conditions. Given
>>     your explanation, I guess "unreliable or un-ordered" works.
>>
>>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>>     the DTLS setup over a reliable, ordered-delivery stream. So the
>>     concerns here wouldn't apply to it. So are you considering some
>>     other potential DTLS over SCTP mapping?
>>
>>
>> This is exactly what I am saying: If DTLS is running over SCTP with
>> reliable, ordered delivery stream, then DTLS packet disambiguation is
>> not a problem and new DTLS association can always be established over an
>> existing transport. In fact RFC6083 says that SCTP should be reused for
>> new DTLS associations. Because of this, if answerer wants to establish a
>> new DTLS association and offer contains an SCTP transport, answerer can
>> reuse the SCTP transport for new DTLS association.
>>
>> If DTLS is running over UDP (unreliable and un-ordered), transport
>> disambiguation concerns do apply. This means either offerer or answerer
>> MUST allocate new address/port or set of candidates when new DTLS
>> association is established. Furthermore, if ICE is used and offerer did
>> not initiate an ICE restart, new DTLS association MUST NOT be
>>  established, since new transport cannot be allocated and packets cannot
>> be disambiguated.
>>
>
> So there is no known transport, other than UDP, where this concern applies?
>
> There are other unreliable unordered transports out there, like ATM AAL5.
I am not sure anybody is concerned about using DTLS over AAL5 at this
point, but this can potentially work and have similar issues to DTLS over
UDP.

P.S. I have no practical experience with ATM, so this is all fairly
theoretical to me.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Tue, May 24, 2016 at 4:05 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.=
edu</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wi=
dth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-=
left:1ex"><span class=3D"">On 5/24/16 3:05 PM, Roman Shpount wrote:<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204=
,204);padding-left:1ex"><span class=3D"">
On Tue, May 24, 2016 at 2:07 PM, Paul Kyzivat &lt;<a href=3D"mailto:pkyziva=
t@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a><br></span><span=
 class=3D"">
&lt;mailto:<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzi=
vat@alum.mit.edu</a>&gt;&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 I&#39;m happy if the words cover the specific relevant condit=
ions. Given<br>
=C2=A0 =C2=A0 your explanation, I guess &quot;unreliable or un-ordered&quot=
; works.<br>
<br>
=C2=A0 =C2=A0 I&#39;m a little unclear about SCTP in this regard. IIUC RFC6=
083 does<br>
=C2=A0 =C2=A0 the DTLS setup over a reliable, ordered-delivery stream. So t=
he<br>
=C2=A0 =C2=A0 concerns here wouldn&#39;t apply to it. So are you considerin=
g some<br>
=C2=A0 =C2=A0 other potential DTLS over SCTP mapping?<br>
<br>
<br>
This is exactly what I am saying: If DTLS is running over SCTP with<br>
reliable, ordered delivery stream, then DTLS packet disambiguation is<br>
not a problem and new DTLS association can always be established over an<br=
>
existing transport. In fact RFC6083 says that SCTP should be reused for<br>
new DTLS associations. Because of this, if answerer wants to establish a<br=
>
new DTLS association and offer contains an SCTP transport, answerer can<br>
reuse the SCTP transport for new DTLS association.<br>
<br>
If DTLS is running over UDP (unreliable and un-ordered), transport<br>
disambiguation concerns do apply. This means either offerer or answerer<br>
MUST allocate new address/port or set of candidates when new DTLS<br>
association is established. Furthermore, if ICE is used and offerer did<br>
not initiate an ICE restart, new DTLS association MUST NOT be<br>
=C2=A0established, since new transport cannot be allocated and packets cann=
ot<br>
be disambiguated.<br>
</span></blockquote>
<br>
So there is no known transport, other than UDP, where this concern applies?=
<div class=3D""><div class=3D"h5"><br></div></div></blockquote>There are ot=
her unreliable unordered transports out there, like ATM AAL5. I am not sure=
 anybody is concerned about using DTLS over AAL5 at this point, but this ca=
n potentially work and have similar issues to DTLS over UDP.</div><div clas=
s=3D"gmail_quote"><br></div><div class=3D"gmail_quote">P.S. I have no pract=
ical experience with ATM, so this is all fairly theoretical to me.<br><div>=
<div class=3D"gmail_signature">_____________<br>Roman Shpount</div></div><d=
iv>=C2=A0</div></div></div></div>

--94eb2c05d15869142a05339c29b2--


From nobody Tue May 24 13:15:40 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39F012D11F for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NkwHL_9_1E0V for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:15:27 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::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 9D75612D1C8 for <mmusic@ietf.org>; Tue, 24 May 2016 13:12:36 -0700 (PDT)
Received: by mail-qg0-x22d.google.com with SMTP id f92so12794587qgf.0 for <mmusic@ietf.org>; Tue, 24 May 2016 13:12:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=pSlvFXb6v2n+U94Nftc+TSsh0wVY8FzjpX/xWezXsTA=; b=g6VlAeDf1DIEodgNyAo111kvuj4RVzAqZXECMIgEvJXniRldvGrC+mFZOmM6ojDyQK y6FYGXmetAfJrt+WQSSL/+X8u0/aOhcbtqt2qvwWtjcM2FZ4D3m4yKe7XgI13uoqzPau d3G7mTtotgsSA7wME0fxpGwlTJ0kbyY6GxQQUB9ydZdURlMowBArt/O4kWwtIj2rNKvL Buwu8nAMJ2CD7ptJjqpWwHBOXhjVLdUN5Of5u23jSx369PgMPLxeHO/YfS/bmZpyU8TV qwe29+2ncEWLjAWp0Vx8L8zN9FJ67K9lW7l4PFt3MOojB0Xt8bWNtl+XO5QBXl/H4npx ROlg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=pSlvFXb6v2n+U94Nftc+TSsh0wVY8FzjpX/xWezXsTA=; b=UfK4GGO4sOhiQ4cj9h3LNldE2C/i3xnBlZpUKdtZjuf4cyI6Fr7fH4Q7Mey28FjXxR ftWll74UCChKfzW6HlGD03Lo4qhyUNwWjqZunJJvYLtpeLnXRLqS1pW6BMMDEOnShG4S 5SrYIDzfFZHesb6Ao0kt340BD/4c64oeKjDAgpbtnzqOOcToOTupYwgIswdJJJqMH3UH z3enJ2mm8adFlKFFg00h4h8+ICjZzjzdeNTFDoArdo2Nuy7xoXLFWWrEuAT7sImYR0te +RXPNxwntL1Ht3KlO6FtdPiNG8efrJ1UoLUY7+kEthlSM0R4se7ftDH7n1qim/vBLvW6 21sA==
X-Gm-Message-State: ALyK8tIc8cKmo3FUZdzKevK/EmaEJFYJHFLRk6Z1CFxSHMdbTnRH1Y/Kchs911+YKOtziBLiTPxvbSktU4tBVw==
MIME-Version: 1.0
X-Received: by 10.140.38.145 with SMTP id t17mr74358qgt.10.1464120755661; Tue, 24 May 2016 13:12:35 -0700 (PDT)
Received: by 10.140.104.70 with HTTP; Tue, 24 May 2016 13:12:35 -0700 (PDT)
In-Reply-To: <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu>
Date: Tue, 24 May 2016 13:12:35 -0700
Message-ID: <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/yVKAjI5H2uasCs6WZe77yXP-UDw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:15:30 -0000

On 24 May 2016 at 13:09, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> So this RFC will need to be revised when SHA-256 is broken and no longer
> safe to use?

When that happens, I will volunteer my time to fix the problem.  I'm
sure that fixing the specs will be much easier than fixing all the
things that depend on SHA-256.

I see no value in doing more specs.


From nobody Tue May 24 13:19:11 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC79012D1DE for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSOWnqoAeStF for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:19:03 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C33A12D1CD for <mmusic@ietf.org>; Tue, 24 May 2016 13:17:05 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id n63so20184852qkf.0 for <mmusic@ietf.org>; Tue, 24 May 2016 13:17:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=7UyrFSuKc8oa13czSG8w1w8/Vm5zVuGl8geRV7Ft1DY=; b=rimBh0QpA3S399cuNzWupoKWtwkM3dl0/ryi1Dvg1eg8sF0dywfNYkecPy/E45zSFb BPIqOq9CCdhZN9eFVTo1hdW610dDJBnU30yGf4aRUgHuV5dnWepEpSPmwnVOiJo2MTBS a38wI4dPNNUwJxr9jSy4P9rjZ2pie+Ve+ZMuBMctZSo0uxokvXf47K5jCSeoolg8UTeE dT/G74EzsoUlWHGN2STfaGNFj+7QcaiKF1EGDesGZKea1tsluVuLKNJ9wubIDz1DvIVa BUwE2qhd68Hb6MzqkIw5boChEoBPhS2XIY0X89sG9IVgCx4kePDxvVUoyazGUS6RGwBz vtUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=7UyrFSuKc8oa13czSG8w1w8/Vm5zVuGl8geRV7Ft1DY=; b=Kk7iJ1jlcpwKu1xVXZfoUobnKB6X9Z42cZpEFXwMWKIX/Y8e+UZ5kFqa4U9Mf7x5mU WoZ3aToX0mT+XcBHm9kbasGkED0vmUkA5IFmaRSMSNIeV2KU9EjyWVyg14oYPILMK1CU D6rNesTUkyJOkuG8w3rSswm0rouzp4j0TcMLZeAQskZ8koZxTdeyZBK3lqssime4eJt9 tbGpOrVanXRLqQOz3Xxy+O6guadFSjzNuiP70uzJGvv96n0Bf5UvdG6hXGOXo5VXlARS vdvBxNH7Nm1tRy04KNMcebcgsqZimBIxoSnkby3h1wC3VR8BMnd3zd3vfE8N6L5AvUYm nQKA==
X-Gm-Message-State: ALyK8tIhWERo4CxqIZwbbDJWr0a91PH3DZsY95T2+0fCMvoMFQbX3ZqpsnPxjC8bfEv7aIqk+wqsyMtmrEgYaw==
MIME-Version: 1.0
X-Received: by 10.55.138.194 with SMTP id m185mr95750qkd.48.1464121024683; Tue, 24 May 2016 13:17:04 -0700 (PDT)
Received: by 10.140.104.70 with HTTP; Tue, 24 May 2016 13:17:04 -0700 (PDT)
In-Reply-To: <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com>
Date: Tue, 24 May 2016 13:17:04 -0700
Message-ID: <CABkgnnUGKQJyZi3PpV5-dZfCg1S26eRuVzT-=MvJo+j2db6etQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/TpblClGB2NW2dUAuLtrIGkCjF2k>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:19:05 -0000

On 24 May 2016 at 12:05, Roman Shpount <roman@telurix.com> wrote:
>
> If DTLS is running over UDP (unreliable and un-ordered), transport
> disambiguation concerns do apply.


The concern is the ordered delivery, not reliability.  It's the
possibility that you might get a packet from the last connection after
you start with the new connection.


From nobody Tue May 24 13:21:03 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B4D12D11F for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYYNw0uebD9h for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:21:01 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E155F12D109 for <mmusic@ietf.org>; Tue, 24 May 2016 13:19:54 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by comcast with SMTP id 5IjFbXECDp1Be5InybIF5d; Tue, 24 May 2016 20:19:54 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464121194; bh=O04vuewLoCSsAyhazYPEFUgjqPXFw9/su2I1WZHbhPc=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=aq551JjYYD5SrGtSUZ1vmudgAg1pGAyKVr0x2Isu1cVlHj+VTDEKpkeiEV154KPw2 LqyAVaZRRFJ1xEUK4SCLbP7+c3m3uuAqum2KOCjRF2pSgBvC5A/1hOd8qQPU5hn5dy Mp/VA5oygZi7pgDaXW6zUkkr5glWdy1TxJN8o7No6npTfokzu/8GOZc0i0mZbqiTmt OTKfEpZ96HBsIUAxNRSMlCaBG4NuzzuBshpki4XmaXKvbrAM1r2el5XI73VcEmbney ozJ22wkRlZ1xHt7VNgidFgOB87wl/Nj9ZT1tai8LjqtFpY+BIh3SwK8CbWAFrWwn+c sY9BznT7B9MBQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-09v.sys.comcast.net with comcast id yLKt1s01D3KdFy101LKubV; Tue, 24 May 2016 20:19:54 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com> <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FE70BB@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <0afc73be-edfc-fab2-21ca-e3ba18b233a4@alum.mit.edu>
Date: Tue, 24 May 2016 16:19:35 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FE70BB@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/NVgsPuEId7DWDG1x4u9jSVOk65M>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:21:02 -0000

On 5/24/16 4:09 PM, Christer Holmberg wrote:
> Hi,
>
>>>     I'm happy if the words cover the specific relevant conditions. Given
>>>     your explanation, I guess "unreliable or un-ordered" works.
>>>
>>>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>>>     the DTLS setup over a reliable, ordered-delivery stream. So the
>>>     concerns here wouldn't apply to it. So are you considering some
>>>     other potential DTLS over SCTP mapping?
>>>
>>>
>>> This is exactly what I am saying: If DTLS is running over SCTP with
>>> reliable, ordered delivery stream, then DTLS packet disambiguation is
>>> not a problem and new DTLS association can always be established over
>>> an existing transport. In fact RFC6083 says that SCTP should be reused
>>> for new DTLS associations. Because of this, if answerer wants to
>>> establish a new DTLS association and offer contains an SCTP transport,
>>> answerer can reuse the SCTP transport for new DTLS association.
>>>
>>> If DTLS is running over UDP (unreliable and un-ordered), transport
>>> disambiguation concerns do apply. This means either offerer or
>>> answerer MUST allocate new address/port or set of candidates when new
>>> DTLS association is established. Furthermore, if ICE is used and
>>> offerer did not initiate an ICE restart, new DTLS association MUST NOT
>>> be  established, since new transport cannot be allocated and packets
>>> cannot be disambiguated.
>>
>> So there is no known transport, other than UDP, where this concern applies?
>
> You can have unreliable/unordered SCTP too, can't you?

Yes, but there is no DTLS mapping defined for it. The DTLS mapping in 
6083 says that all the DTLS control messages must go over a reliable, 
ordered, stream 0. (The data can go over other streams with other 
properties.)

So it would take a different DTLS mapping over SCTP to cover this. It is 
hard to imagine why anyone would do this.

I still agree that in principle some new transport could be defined 
where this concern would apply. But no such is currently known or foreseen.

Maybe this doesn't need to change the wording at all. (But adding 
"unordered" does seem worthwhile.)

	Thanks,
	Paul


From nobody Tue May 24 13:27:23 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4424212D1DC for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kyuWVCHJ_loc for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 13:27:21 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8012C12D109 for <mmusic@ietf.org>; Tue, 24 May 2016 13:27:20 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-8a-5744b926c4ae
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id C9.A6.18043.629B4475; Tue, 24 May 2016 22:27:18 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0294.000; Tue, 24 May 2016 22:27:18 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
Thread-Index: AdGzeadT9Biiw5sKQwmLHX/vhwcvDQCUFxUAAAIcngAAAP0FAAACBMYAAAIbbAAABEscMP//4XeA///dXbA=
Date: Tue, 24 May 2016 20:27:17 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FE71CA@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com> <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FE70BB@ESESSMB209.ericsson.se> <0afc73be-edfc-fab2-21ca-e3ba18b233a4@alum.mit.edu>
In-Reply-To: <0afc73be-edfc-fab2-21ca-e3ba18b233a4@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM2K7sa7aTpdwg63HxS2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugStj9r8TLAV3hCqu/WlhaWBs5O9i5OSQEDCR uPVxPTuELSZx4d56ti5GLg4hgSOMEq+WrmSGcJYwSuz6MAHI4eBgE7CQ6P6nDdIgIuAr8ezx bTYQW1jATaJ102pmiLi7xNU7m8DKRQSSJM7MTAcJswioSmy79xpsFy9Q67ejixghxn9nljg6 /TUTSIJTwEGib8tRsJmMQAd9P7UGLM4sIC5x68l8JohDBSSW7DnPDGGLSrx8/I8VwlaSWHT7 M1S9jsSC3Z/YIGxtiWULXzNDLBaUODnzCcsERtFZSMbOQtIyC0nLLCQtCxhZVjGKFqcWF+em GxnppRZlJhcX5+fp5aWWbGIExsnBLb+tdjAefO54iFGAg1GJhzeh1jlciDWxrLgy9xCjBAez kgjv/K0u4UK8KYmVValF+fFFpTmpxYcYpTlYlMR5/V8qhgsJpCeWpGanphakFsFkmTg4pRoY /VW4z84Xm/B3xe3XG9K85Vxeh1hYvu4sOnXjPIdJRFNiYI733XkPZKN+Kr1xMHN+JzshvLR0 dZBFyYaomEaJ+HfWO9vbuh8o3t7xep/6gl8+nd4Psrs1Xv5RFW+0/9kosdAiYUM948rNZ79q WcwSFl2jN2Gf/f65X7tXeu9fFR4jePJK+vNKJZbijERDLeai4kQAeGmaUI8CAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/z55uVDKS347ugi85x2Dyvw6u6_I>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 20:27:22 -0000

Hi,

>>>>     I'm happy if the words cover the specific relevant conditions. Giv=
en
>>>>     your explanation, I guess "unreliable or un-ordered" works.
>>>>
>>>>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>>>>     the DTLS setup over a reliable, ordered-delivery stream. So the
>>>>     concerns here wouldn't apply to it. So are you considering some
>>>>     other potential DTLS over SCTP mapping?
>>>>
>>>>
>>>> This is exactly what I am saying: If DTLS is running over SCTP with=20
>>>> reliable, ordered delivery stream, then DTLS packet disambiguation=20
>>>> is not a problem and new DTLS association can always be established=20
>>>> over an existing transport. In fact RFC6083 says that SCTP should be=20
>>>> reused for new DTLS associations. Because of this, if answerer wants=20
>>>> to establish a new DTLS association and offer contains an SCTP=20
>>>> transport, answerer can reuse the SCTP transport for new DTLS associat=
ion.
>>>>
>>>> If DTLS is running over UDP (unreliable and un-ordered), transport=20
>>>> disambiguation concerns do apply. This means either offerer or=20
>>>> answerer MUST allocate new address/port or set of candidates when=20
>>>> new DTLS association is established. Furthermore, if ICE is used and=20
>>>> offerer did not initiate an ICE restart, new DTLS association MUST=20
>>>> NOT be  established, since new transport cannot be allocated and=20
>>>> packets cannot be disambiguated.
>>>
>>> So there is no known transport, other than UDP, where this concern appl=
ies?
>>
>> You can have unreliable/unordered SCTP too, can't you?
>
> Yes, but there is no DTLS mapping defined for it. The DTLS mapping in
> 6083 says that all the DTLS control messages must go over a reliable, ord=
ered, stream 0. (The data can go over other streams with other
> properties.)

True. Comment withdrawn.

>So it would take a different DTLS mapping over SCTP to cover this. It is h=
ard to imagine why anyone would do this.
>
>I still agree that in principle some new transport could be defined where =
this concern would apply. But no such is currently known or foreseen.
>
>Maybe this doesn't need to change the wording at all. (But adding "unorder=
ed" does seem worthwhile.)

Yes.=20

And, based on Martin's latest comment, perhaps removing "unreliable".

Regards,

Christer


From nobody Tue May 24 16:21:19 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EBA112D16C; Tue, 24 May 2016 16:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 lAgXYzBzGAig; Tue, 24 May 2016 16:21:16 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F80312D167; Tue, 24 May 2016 16:21:13 -0700 (PDT)
Received: from [10.0.1.18] (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 u4ONLC4V069839 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 24 May 2016 18:21:12 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.18]
From: "Ben Campbell" <ben@nostrum.com>
To: "mmusic WG" <mmusic@ietf.org>, "avt@ietf.org WG" <avt@ietf.org>
Date: Tue, 24 May 2016 18:21:10 -0500
Message-ID: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ppEW32x_ggdLK66imBn-bNFbWH0>
Cc: draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Subject: [MMUSIC] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 May 2016 23:21:18 -0000

Hi,

There appears to be a discrepancy between 
draft-ietf-mmusic-sdp-mux-attributes and 
draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be used 
with bundle.

mux-attributes puts the zrtp-hash attribute [RFC6189] in the "transport" 
category, meaning, among other things, that it can be used in a bundle 
group. However, as the demux rules are currently defined 5764-mux-fixes, 
zrtp messages cannot actually be demuxed. (If I read things correctly, 
the first byte of a zrtp message will be 16, which is not in any of the 
"known ranges" described in 5765 or 5764-mux-fixes, and therefore the 
message MUST be dropped.

That seems to leave the choice of adding zrtp messages to the demux 
rules in 5764-mux-fixes, or removing the implication that zrtp can be 
bundled from mux-attributes.

Adding rules for demuxing zrtp to 5765-mux-fixes would probably not be 
hard, but would be non-trivial. RFC 6189 calls for using the magic 
cookie to distinguish zrtp messages from stun messages.

Do people have opinions how to move forward with this? Am I interpreting 
the conflict correctly?Keep in mind that ZRTP is not a standards-track 
spec. But at the same time, I'm not sure we want to exclude it from the 
bundle mechanism.

Thanks!

Ben.



From nobody Tue May 24 23:29:28 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEC912D1E1 for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 23:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j2VzoWmVCFbw for <mmusic@ietfa.amsl.com>; Tue, 24 May 2016 23:29:26 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 879EC12B02B for <mmusic@ietf.org>; Tue, 24 May 2016 23:29:25 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-10-57454643ad53
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C8.24.12926.34645475; Wed, 25 May 2016 08:29:23 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0294.000; Wed, 25 May 2016 08:29:23 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>,  Martin Thomson <martin.thomson@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
Thread-Index: AdGzeadT9Biiw5sKQwmLHX/vhwcvDQCUFxUAAAIcngAAAP0FAAACBMYAAAIbbAAABEscMP//4XeA///dXbCAAQACAA==
Date: Wed, 25 May 2016 06:29:22 +0000
Message-ID: <D36B2086.90B7%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com> <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FE70BB@ESESSMB209.ericsson.se> <0afc73be-edfc-fab2-21ca-e3ba18b233a4@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FE71CA@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FE71CA@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5DF9ECCA5E09E542B2114FAEC7C16F13@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMIsWRmVeSWpSXmKPExsUyM2J7uK6zm2u4wd/lqhbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsErowzSx6z FGwSq1ix0ruBsUuoi5GTQ0LARGLL5t1sELaYxIV764FsLg4hgSOMEp1Hp7JDOEsYJZq6fwJl ODjYBCwkuv9pg8RFBOYySpzfsJEdpFtYwE1icf9MMFtEwF3i6p1NzBB2lkTr3oVgcRYBVYm5 D26A2bwCVhJvt+5mhViwm0XicF8PC0iCU8BP4sjBZ0wgNiPQSd9PrQGzmQXEJW49mc8EcaqA xJI955khbFGJl4//sYLYogJ6EvtenGcEOVRCQEli2tY0iFY9iRtTp7BB2NYSE98fgLK1JZYt fM0McY+gxMmZT1gmMIrPQrJtFpL2WUjaZyFpn4WkfQEj6ypG0eLU4qTcdCNjvdSizOTi4vw8 vbzUkk2MwKg8uOW36g7Gy28cDzEKcDAq8fA+OOcSLsSaWFZcmXuIUYKDWUmE96eFa7gQb0pi ZVVqUX58UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGRg4p7b6XBRmftBln be5pfPqwMfiUjND63/GJtx49f7RYvMNWW1agYuKagzNPPv/BcPpT00xzpxbToCan7sOXon5v 5XipNsXnh/zV4DrlW8JxyVNltktU/bdLnhRrZcNr+XqiRs6FV9kXFgo3yfJOKapavU+q/GCE 0MeztQEnUieem3pD68msS0osxRmJhlrMRcWJAJ9aV5LGAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/PGOo7tZE1gEY0G8HVPqe6yN_lBc>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 06:29:27 -0000

Hi,

Based on the comments on -12, we would replace =B3unreliable=B2 with
=B3unordered=B2 in sections 5.1 and 6.

Ok?

Regards,

Christer








On 24/05/16 23:27, "mmusic on behalf of Christer Holmberg"
<mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
wrote:

>Hi,
>
>>>>>     I'm happy if the words cover the specific relevant conditions.
>>>>>Given
>>>>>     your explanation, I guess "unreliable or un-ordered" works.
>>>>>
>>>>>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>>>>>     the DTLS setup over a reliable, ordered-delivery stream. So the
>>>>>     concerns here wouldn't apply to it. So are you considering some
>>>>>     other potential DTLS over SCTP mapping?
>>>>>
>>>>>
>>>>> This is exactly what I am saying: If DTLS is running over SCTP with
>>>>> reliable, ordered delivery stream, then DTLS packet disambiguation
>>>>> is not a problem and new DTLS association can always be established
>>>>> over an existing transport. In fact RFC6083 says that SCTP should be
>>>>> reused for new DTLS associations. Because of this, if answerer wants
>>>>> to establish a new DTLS association and offer contains an SCTP
>>>>> transport, answerer can reuse the SCTP transport for new DTLS
>>>>>association.
>>>>>
>>>>> If DTLS is running over UDP (unreliable and un-ordered), transport
>>>>> disambiguation concerns do apply. This means either offerer or
>>>>> answerer MUST allocate new address/port or set of candidates when
>>>>> new DTLS association is established. Furthermore, if ICE is used and
>>>>> offerer did not initiate an ICE restart, new DTLS association MUST
>>>>> NOT be  established, since new transport cannot be allocated and
>>>>> packets cannot be disambiguated.
>>>>
>>>> So there is no known transport, other than UDP, where this concern
>>>>applies?
>>>
>>> You can have unreliable/unordered SCTP too, can't you?
>>
>> Yes, but there is no DTLS mapping defined for it. The DTLS mapping in
>> 6083 says that all the DTLS control messages must go over a reliable,
>>ordered, stream 0. (The data can go over other streams with other
>> properties.)
>
>True. Comment withdrawn.
>
>>So it would take a different DTLS mapping over SCTP to cover this. It is
>>hard to imagine why anyone would do this.
>>
>>I still agree that in principle some new transport could be defined
>>where this concern would apply. But no such is currently known or
>>foreseen.
>>
>>Maybe this doesn't need to change the wording at all. (But adding
>>"unordered" does seem worthwhile.)
>
>Yes.=20
>
>And, based on Martin's latest comment, perhaps removing "unreliable".
>
>Regards,
>
>Christer
>
>_______________________________________________
>mmusic mailing list
>mmusic@ietf.org
>https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed May 25 00:12:01 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF3712DA62 for <mmusic@ietfa.amsl.com>; Wed, 25 May 2016 00:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1OkVhC-PhB7l for <mmusic@ietfa.amsl.com>; Wed, 25 May 2016 00:11:59 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBBF912D986 for <mmusic@ietf.org>; Wed, 25 May 2016 00:11:58 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-45-5745503c7835
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id F5.2D.12926.C3055475; Wed, 25 May 2016 09:11:56 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0294.000; Wed, 25 May 2016 09:11:56 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gA==
Date: Wed, 25 May 2016 07:11:56 +0000
Message-ID: <D36B255A.90C8%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com>
In-Reply-To: <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <1AACD70D9E3ADB4CA73D3F9C39242E0B@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2K7h65NgGu4Qcsdc4trZ/4xWkxd/pjF YsWGA6wOzB5/339g8tg56y67x5IlP5kCmKO4bFJSczLLUov07RK4MmZ+PstaMFO44uH7OcwN jI/5uhg5OSQETCTWXJ/GBGGLSVy4t56ti5GLQ0jgCKPEqbnnWSCcJYwSs699A3I4ONgELCS6 /2mDNIgIhEq0XdzHCBJmFlCXuLo4CCQsLGAvcfXyZSaIEgeJnW+vskDYdRLrV/9lBrFZBFQl Ds2cAFbDK2AlsWfSa1aIVV9YJXY/PswEMpNTIFBi18ZEkBpGoNu+n1oDVs8sIC5x68l8qJsF JJbsOc8MYYtKvHz8jxXEFhXQk9j34jwjRFxR4uOrfYwQvQYS78/NZ4awrSWOP9jFAmFrSyxb +JoZ4h5BiZMzn7BMYJSYhWTdLCTts5C0z0LSPgtJ+wJG1lWMosWpxUm56UbGeqlFmcnFxfl5 enmpJZsYgZF5cMtv1R2Ml984HmIU4GBU4uF9cM4lXIg1say4MvcQowQHs5IIb4C3a7gQb0pi ZVVqUX58UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGRrcVrhuZrVbeClOI qXs+pe+/2iJ//w+NopxH74nzvrnJGHciJuhzELMQo7CUsL/X8S+G/me99SyXdX/Yl1RhVZF+ naXbVvl7QJ/ApoOeRanff+4+WfhjVlH3903q4XlB9+aoanya7cEYzjNx3euSQ89TtmxbkNbZ 8HbfsfwzhRrlSt0P35+RUWIpzkg01GIuKk4EAJxakfzIAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Rl6yOLUIB9lPXH5OPkdVxlKudDs>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 07:12:01 -0000

Hi,

In addition to the text change suggested by Martin, I=B9ve also identified
the following changes by mandating SHA-256.

-----

Abstract & Introduction:

OLD:

"The document also updates the preferred cipher suite to be used,..."


NEW:

=B3The document also replaces the preferred cipher suite with a mandate to
support a stronger cipher suite,=8A=B2

-----

Section 5:

The changes to the currently suggested new text between <new> and </new>.


 NEW TEXT:

     Multiple SDP fingerprint attributes can be associated with an m-
     line. This can occur if multiple fingerprints have been calculated
     for a certificate using different hash functions. It can also
     occur if one or more fingerprints associated with multiple
     certificates have been calculated. This might be needed if multiple
     certificates will be used for media associated with an m- line
     (e.g. if separate certificates are used for RTP and RTCP), or where
     it is not known which certificate will be used when the
     fingerprints are exchanged. In such cases, one or more fingerprints
     MUST be calculated for each possible certificate. <new>An endpoint
MUST, as a minimum, calculate a fingerprint using the =8CSHA-256=B9
hash function for each possible certificate.</t>

     If fingerprints associated with multiple certificates are
     calculated, the same set of hash functions MUST be used to
     calculate fingerprints for each certificate associated with the
     m- line.

     For each used certificate, an endpoint MUST be able to match at
     least one fingerprint, calculated using the hash function that the
     endpoint supports and considers most secure, with the used
     certificate. <new> If a fingerprint calculated using the =B9SHA-256=B9
hash
function is present, the endpoint MUST be able to match it </new>. If
there is no match, the
endpoint MUST NOT establish the TLS connection. In addition, the endpoint
MAY also check
     fingerprints calculated using other hash functions that it has
     received for a match. For each hash function checked, one of the
     received fingerprints MUST match the used certificate.

     NOTE: The SDP fingerprint attribute does not contain a reference to
     a specific certificate. Endpoints need to compare the fingerprint
     with a certificate hash in order to look for a match.

-----

Regards,

Christer




From nobody Wed May 25 07:14:45 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1123012D753 for <mmusic@ietfa.amsl.com>; Wed, 25 May 2016 07:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-y59ngR2ONC for <mmusic@ietfa.amsl.com>; Wed, 25 May 2016 07:14:40 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4DC712D724 for <mmusic@ietf.org>; Wed, 25 May 2016 07:14:08 -0700 (PDT)
Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by comcast with SMTP id 5ZXTbVKgn8DPn5ZZYbd1bs; Wed, 25 May 2016 14:14:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464185648; bh=DVgdaJ0mtsZLcjJ4msUN6t+YRXOi/81VURyNMmI68Ro=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=Fz+yLQ98CgheSTXksc5XXd0HYMY4PcHcJPy7hj4T8F+QHyG5KyQhM5reBmi7Vzb0A 1wBikmQRVXPIcoZ5+ZPnXfLigtk4diFWXVmsPFPekUtzUGZOiheSPrdnVmBHTLbwrQ psQ2Vg72PJg3/6vfBna/iPon+uHEXN4v63cEFJuh7TKZNFTyY9iEQAKBYifWrICtEw kuHDXZHx8d3R6ouoUFGqkRATMZP4dFicCRWLcVhTyrMyITN3pg9KgkkPfxjiDjpQtO CQMZgwI6pTSWoyVQ2pA1UStuk5RR1m25pp0KnlCVMnwGKnqIQ9L3EiqzL2OcYFIeXQ +zR/CGIGhvFjg==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-16v.sys.comcast.net with comcast id yeE71s00K3KdFy101eE718; Wed, 25 May 2016 14:14:07 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>, Roman Shpount <roman@telurix.com>
References: <7594FB04B1934943A5C02806D1A2204B37FDE36B@ESESSMB209.ericsson.se> <546e854e-8831-5dbb-6e15-5a3d34285767@alum.mit.edu> <CAD5OKxv2VycT2t8Mq3SoUnaVj8rY20tyoNFTnMG8ZP+qQbCKVQ@mail.gmail.com> <a3981bf1-0ad7-a2ba-c347-bd77acbe1abd@alum.mit.edu> <CAD5OKxtcr2=ARVC=N_CcsE2E_84_VAZ=vfOB59GipOETCek3VQ@mail.gmail.com> <49fb85c0-1794-64b1-7817-573074ec6021@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FE70BB@ESESSMB209.ericsson.se> <0afc73be-edfc-fab2-21ca-e3ba18b233a4@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B37FE71CA@ESESSMB209.ericsson.se> <D36B2086.90B7%christer.holmberg@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ee3fb96c-0ad8-686d-913f-daf6a98c3e2e@alum.mit.edu>
Date: Wed, 25 May 2016 10:13:47 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <D36B2086.90B7%christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/tdkQrUjjgUNs1R2EDUh3ltXuvwk>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 14:14:43 -0000

On 5/25/16 2:29 AM, Christer Holmberg wrote:
> Hi,
>
> Based on the comments on -12, we would replace ³unreliable² with
> ³unordered² in sections 5.1 and 6.
>
> Ok?

WFM

> Regards,
>
> Christer
>
>
>
>
>
>
>
>
> On 24/05/16 23:27, "mmusic on behalf of Christer Holmberg"
> <mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
>
>> Hi,
>>
>>>>>>     I'm happy if the words cover the specific relevant conditions.
>>>>>> Given
>>>>>>     your explanation, I guess "unreliable or un-ordered" works.
>>>>>>
>>>>>>     I'm a little unclear about SCTP in this regard. IIUC RFC6083 does
>>>>>>     the DTLS setup over a reliable, ordered-delivery stream. So the
>>>>>>     concerns here wouldn't apply to it. So are you considering some
>>>>>>     other potential DTLS over SCTP mapping?
>>>>>>
>>>>>>
>>>>>> This is exactly what I am saying: If DTLS is running over SCTP with
>>>>>> reliable, ordered delivery stream, then DTLS packet disambiguation
>>>>>> is not a problem and new DTLS association can always be established
>>>>>> over an existing transport. In fact RFC6083 says that SCTP should be
>>>>>> reused for new DTLS associations. Because of this, if answerer wants
>>>>>> to establish a new DTLS association and offer contains an SCTP
>>>>>> transport, answerer can reuse the SCTP transport for new DTLS
>>>>>> association.
>>>>>>
>>>>>> If DTLS is running over UDP (unreliable and un-ordered), transport
>>>>>> disambiguation concerns do apply. This means either offerer or
>>>>>> answerer MUST allocate new address/port or set of candidates when
>>>>>> new DTLS association is established. Furthermore, if ICE is used and
>>>>>> offerer did not initiate an ICE restart, new DTLS association MUST
>>>>>> NOT be  established, since new transport cannot be allocated and
>>>>>> packets cannot be disambiguated.
>>>>>
>>>>> So there is no known transport, other than UDP, where this concern
>>>>> applies?
>>>>
>>>> You can have unreliable/unordered SCTP too, can't you?
>>>
>>> Yes, but there is no DTLS mapping defined for it. The DTLS mapping in
>>> 6083 says that all the DTLS control messages must go over a reliable,
>>> ordered, stream 0. (The data can go over other streams with other
>>> properties.)
>>
>> True. Comment withdrawn.
>>
>>> So it would take a different DTLS mapping over SCTP to cover this. It is
>>> hard to imagine why anyone would do this.
>>>
>>> I still agree that in principle some new transport could be defined
>>> where this concern would apply. But no such is currently known or
>>> foreseen.
>>>
>>> Maybe this doesn't need to change the wording at all. (But adding
>>> "unordered" does seem worthwhile.)
>>
>> Yes.
>>
>> And, based on Martin's latest comment, perhaps removing "unreliable".
>>
>> Regards,
>>
>> Christer
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
>


From nobody Wed May 25 10:38:12 2016
Return-Path: <marc@petit-huguenin.org>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0CAB12D6B7; Wed, 25 May 2016 10:38:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FUGk9XA-vwEd; Wed, 25 May 2016 10:38:07 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C76F12D5C6; Wed, 25 May 2016 10:38:07 -0700 (PDT)
Received: from [IPv6:2001:0:53aa:64c:184d:5c33:53c7:d9b2] (unknown [IPv6:2001:0:53aa:64c:184d:5c33:53c7:d9b2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id D835720251; Wed, 25 May 2016 19:37:59 +0200 (CEST)
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, "avt@ietf.org WG" <avt@ietf.org>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com>
Message-ID: <5745E2F4.8040206@petit-huguenin.org>
Date: Wed, 25 May 2016 10:37:56 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.2
MIME-Version: 1.0
In-Reply-To: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lpGtInOviD2oT6PUpKOOaq5a4EIQWHF08"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/WgfYbOH72vzE9oORzz4Y8gUPBMg>
Cc: draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org, draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 17:38:10 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--lpGtInOviD2oT6PUpKOOaq5a4EIQWHF08
Content-Type: multipart/mixed; boundary="bLbxPiIf0nGAqOCxbDjWOFRqhpNkTsD8o"
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>,
 "avt@ietf.org WG" <avt@ietf.org>
Cc: draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org,
 draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org
Message-ID: <5745E2F4.8040206@petit-huguenin.org>
Subject: Re: [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs
 draft-ietf-avtcore-rfc5764-mux-fixes
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com>
In-Reply-To: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com>

--bLbxPiIf0nGAqOCxbDjWOFRqhpNkTsD8o
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

As you mention, there are several ways to handle this issue. We leave it =
to the community to decide whether to include zrtp in bundle or not. If w=
e were to update the 5764-mux-fix draft, we felt that the cleanest way to=
 handle it is in two steps.

One thing to note is that there is no clash/overlap with STUN, so using m=
agic cookie to distinguish from STUN is a moot point. The overlap with th=
e DTLS range is what we need to avoid. The right thing to do seems to be =
to work on a rfc6189bis draft that would set bit 4 and 5 of the first byt=
e of the zrtp message to 0. This way zrtp cannot clash with DTLS.

On the rfc5764-mux-fixes draft, we just change the algorithm to:

           +----------------+
           |        [0..3] -+--> forward to STUN
           |                |
           |      [16..19] -+--> forward to ZRTP
           |                |
packet --> |      [20..63] -+--> forward to DTLS
           |                |
           |      [64..79] -+--> forward to TURN Channel
           |                |
           |    [128..191] -+--> forward to RTP/RTCP
           +----------------+


Does this seem like a reasonable approach?


On 05/24/2016 04:21 PM, Ben Campbell wrote:
> Hi,
>=20
> There appears to be a discrepancy between draft-ietf-mmusic-sdp-mux-att=
ributes and draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp =
can be used with bundle.
>=20
> mux-attributes puts the zrtp-hash attribute [RFC6189] in the "transport=
" category, meaning, among other things, that it can be used in a bundle =
group. However, as the demux rules are currently defined 5764-mux-fixes, =
zrtp messages cannot actually be demuxed. (If I read things correctly, th=
e first byte of a zrtp message will be 16, which is not in any of the "kn=
own ranges" described in 5765 or 5764-mux-fixes, and therefore the messag=
e MUST be dropped.
>=20
> That seems to leave the choice of adding zrtp messages to the demux rul=
es in 5764-mux-fixes, or removing the implication that zrtp can be bundle=
d from mux-attributes.
>=20
> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not be =
hard, but would be non-trivial. RFC 6189 calls for using the magic cookie=
 to distinguish zrtp messages from stun messages.
>=20
> Do people have opinions how to move forward with this? Am I interpretin=
g the conflict correctly?Keep in mind that ZRTP is not a standards-track =
spec. But at the same time, I'm not sure we want to exclude it from the b=
undle mechanism.
>=20
> Thanks!
>=20
> Ben.
>=20
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>=20




--bLbxPiIf0nGAqOCxbDjWOFRqhpNkTsD8o--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXReL1AAoJECnERZXWan7EO5kP/3mRBA9hVENe08y26OvL9ArY
CI3y2NHJJ5wGXAbtn9w3jmMuRqt0CDLisGQpew3BlpJTNxPR0LTfvHFMMn7p7Udn
ipw/Fz2EuFqx5+hc4mqSlZrsszSUn31UDzqRDIQ9474+GMQHJRn99kG4hXq1X7uJ
oQENUD6jh4A95297GJa/++u/wkTf0PxBeyMzfzDwGbaKyIUbOQGitH3hLl9AoOd9
xwgykMjUN9yT2Dkl1LU2iKZJG9EEjlZc1b0/hRaRMntFqgyLOBbCZ3zRDZwxT1Sz
Ii3knZ1tBGJo+f1g60BWdpUkxdroHMUAdpbeEIqCT0BT3cgYfa15krNOT02cbBm0
187YGy28BD6n2NRyZuvb22nHru0IG18d+mF20CN9BvL+Dat6/HdENs8CKROxIiGg
7KkvHxUXbKzy3HxFUS9v+ei3VfFO+a5zZA2G0ShrCyghjMcKA0cechOYc4f2y7M/
oymYJ1S7nYTjnFCNsv4HlKVSXLZD5fQjqMUZBVvaVsR/jXdxWIcl5qYzqjLpiPAO
F4t4wf6PzO+bVVjvo79+9D9yMlz8cr5tkdgBIHHsTIxf8HwdsxgNclmLCKRU3qDr
F+4Yy6OoKBtZz5q1NnWxJu8GlxMz27y0uh9OpFf6DZI5gOjUbRCuZHS2lfJfyYrA
ZZEdvhJuqiJpef+zL2rS
=7nvL
-----END PGP SIGNATURE-----

--lpGtInOviD2oT6PUpKOOaq5a4EIQWHF08--


From nobody Wed May 25 10:57:02 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8555E12D104; Wed, 25 May 2016 10:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 vNapXIfRrAGV; Wed, 25 May 2016 10:56:59 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D089312D887; Wed, 25 May 2016 10:56:58 -0700 (PDT)
Received: from [10.0.1.18] (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 u4PHuuxE023225 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 25 May 2016 12:56:57 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.18]
From: "Ben Campbell" <ben@nostrum.com>
To: "Marc Petit-Huguenin" <marc@petit-huguenin.org>
Date: Wed, 25 May 2016 12:56:56 -0500
Message-ID: <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com>
In-Reply-To: <5745E2F4.8040206@petit-huguenin.org>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Zjl6mefnd25xhJWMt0gh_dcnvsU>
Cc: draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org, mmusic WG <mmusic@ietf.org>, draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org, "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 17:57:00 -0000

Hi Marc,

That's along the lines that I expected, if the working group chooses 
this path. What do others think?

Thanks!

Ben.

On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:

> As you mention, there are several ways to handle this issue. We leave 
> it to the community to decide whether to include zrtp in bundle or 
> not. If we were to update the 5764-mux-fix draft, we felt that the 
> cleanest way to handle it is in two steps.
>
> One thing to note is that there is no clash/overlap with STUN, so 
> using magic cookie to distinguish from STUN is a moot point. The 
> overlap with the DTLS range is what we need to avoid. The right thing 
> to do seems to be to work on a rfc6189bis draft that would set bit 4 
> and 5 of the first byte of the zrtp message to 0. This way zrtp cannot 
> clash with DTLS.
>
> On the rfc5764-mux-fixes draft, we just change the algorithm to:
>
>            +----------------+
>            |        [0..3] -+--> forward to STUN
>            |                |
>            |      [16..19] -+--> forward to ZRTP
>            |                |
> packet --> |      [20..63] -+--> forward to DTLS
>            |                |
>            |      [64..79] -+--> forward to TURN Channel
>            |                |
>            |    [128..191] -+--> forward to RTP/RTCP
>            +----------------+
>
>
> Does this seem like a reasonable approach?
>
>
> On 05/24/2016 04:21 PM, Ben Campbell wrote:
>> Hi,
>>
>> There appears to be a discrepancy between 
>> draft-ietf-mmusic-sdp-mux-attributes and 
>> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be 
>> used with bundle.
>>
>> mux-attributes puts the zrtp-hash attribute [RFC6189] in the 
>> "transport" category, meaning, among other things, that it can be 
>> used in a bundle group. However, as the demux rules are currently 
>> defined 5764-mux-fixes, zrtp messages cannot actually be demuxed. (If 
>> I read things correctly, the first byte of a zrtp message will be 16, 
>> which is not in any of the "known ranges" described in 5765 or 
>> 5764-mux-fixes, and therefore the message MUST be dropped.
>>
>> That seems to leave the choice of adding zrtp messages to the demux 
>> rules in 5764-mux-fixes, or removing the implication that zrtp can be 
>> bundled from mux-attributes.
>>
>> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not 
>> be hard, but would be non-trivial. RFC 6189 calls for using the magic 
>> cookie to distinguish zrtp messages from stun messages.
>>
>> Do people have opinions how to move forward with this? Am I 
>> interpreting the conflict correctly?Keep in mind that ZRTP is not a 
>> standards-track spec. But at the same time, I'm not sure we want to 
>> exclude it from the bundle mechanism.
>>
>> Thanks!
>>
>> Ben.
>>
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>


From nobody Wed May 25 12:17:49 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 171FA12D967; Wed, 25 May 2016 12:17:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160525191748.18273.4056.idtracker@ietfa.amsl.com>
Date: Wed, 25 May 2016 12:17:48 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/EwOatKtbhsPsBTeP6BdLPB6Gxx8>
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-dtls-sdp-13.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 19:17:48 -0000

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

        Title           : Using the SDP Offer/Answer Mechanism for DTLS
        Authors         : Christer Holmberg
                          Roman Shpount
	Filename        : draft-ietf-mmusic-dtls-sdp-13.txt
	Pages           : 24
	Date            : 2016-05-25

Abstract:
   This draft defines the SDP offer/answer procedures for negotiating
   and establishing a DTLS association.  The draft also defines the
   criteria for when a new DTLS association must be established.

   This draft defines a new SDP media-level attribute, 'dtls-id'.


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-dtls-sdp-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 Wed May 25 12:20:28 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7A812D8C1; Wed, 25 May 2016 12:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XPDcEKo-i5j; Wed, 25 May 2016 12:20:24 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 473F612D14A; Wed, 25 May 2016 12:20:24 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-29-5745faf6af17
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 9D.85.12516.6FAF5475; Wed, 25 May 2016 21:20:22 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0294.000; Wed, 25 May 2016 21:20:21 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-dtls-sdp-13
Thread-Index: AdG2umECPFoB+vEuSXyS6znw2TfU8A==
Date: Wed, 25 May 2016 19:20:21 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FEAFFA@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FEAFFAESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42KZGbHdWPfbL9dwgy3rJCzO71zPZDF1+WMW ByaPJUt+MgUwRnHZpKTmZJalFunbJXBlTJ2zgbVgr3jFvlUzGRsY34h0MXJySAiYSMxf9okN whaTuHBvPZDNxSEkcIRRYvffJYwQzhJGiV1bG1i6GDk42AQsJLr/aYM0iAioS3zd28MMYjML mEo8fLWGEcQWFrCU2D9jCgtEjZ3EjAM7oGw9iY57R9lBbBYBVYkFC3uZQGxeAV+J+e9fgR3B CHTE91NrmCBmikvcejKfCeI4AYkle84zQ9iiEi8f/2OFsJUkVmy/xAhyGrNAvsSkxx4QIwUl Ts58wjKBUXgWkkmzEKpmIamCKNGRWLD7ExuErS2xbOFrZhj7zIHHTMjiCxjZVzGKFqcWF+em GxnrpRZlJhcX5+fp5aWWbGIERszBLb91dzCufu14iFGAg1GJh/fBOZdwIdbEsuLK3EOMEhzM SiK8yT9dw4V4UxIrq1KL8uOLSnNSiw8xSnOwKInz+r9UDBcSSE8sSc1OTS1ILYLJMnFwSjUw Ll73XLVixfH9/TcurHvkY7zaa2vyp6sT1+lX7hPqPvtKS/5e86qDno+WMURLtTCaZj5RLFbe HtZWPslY7sIFh9vrN+72uBo+fVVUwo6db4vvrblx2EaVj09y1eZW3kYr11n/p81et/gAT8Pr fKFtj9i66+w+rk1h1NH84mB5Ze28+/2L6haaJCixFGckGmoxFxUnAgDQRwAalAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/PaWWDmR4atvDjlfGxJEsvHlz0Fs>
Cc: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 19:20:27 -0000

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

Hi,

I've submitted a new version (-13) of draft-ietf-mmusic-dtls-sdp.

The only change compared to the previous version is the change from "unreli=
able" to "unordered".

Are we done? :)

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B37FEAFFAESESSMB209erics_
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">I&#8217;ve submitted a new version (-13) of draft-ie=
tf-mmusic-dtls-sdp.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The only change compared to the previous version is =
the change from &#8220;unreliable&#8221; to &#8220;unordered&#8221;.<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Are we done? :)<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_7594FB04B1934943A5C02806D1A2204B37FEAFFAESESSMB209erics_--


From nobody Wed May 25 13:18:56 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909EE12DCC7 for <mmusic@ietfa.amsl.com>; Wed, 25 May 2016 13:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNVW-MxxZIyk for <mmusic@ietfa.amsl.com>; Wed, 25 May 2016 13:18:52 -0700 (PDT)
Received: from resqmta-ch2-12v.sys.comcast.net (resqmta-ch2-12v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BA2E12DCCF for <mmusic@ietf.org>; Wed, 25 May 2016 13:18:51 -0700 (PDT)
Received: from resomta-ch2-16v.sys.comcast.net ([69.252.207.112]) by comcast with SMTP id 5fFFbF3HEgEHv5fGUbfHbi; Wed, 25 May 2016 20:18:50 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464207530; bh=WR+cvGiNt0dfGCUtAl/Ho58F0xnC2iT2gzRCYml4dgA=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=b/YiCjMpIJJFIqdl+PR7OuECRWXcDdUBo3UiiNLfJyMIaLg58BplOmP68HC2yldSZ 7xiyyTQpOlQnIF3j38hx1eCDGJ1K9Aie5NI2IrWZz5rjdWlnP5q3tF9HVgkJEg9L1T k7JX4A/MQDvwuVALbAlaX8XtNBSP7/QmkIOjfMeExGBLziMlANZrPKGAFPZ4BDW5Yc rtr/aqSK+piUXq3idB06ICJdKxj0XfNzuSUe48oeR7QC+A1GUUQnPhrVmLRNF17xBy +wJD/hGTgw/LMgljPAnk6uiE/HuNsiifGv9/cFPSql0UJx95QWTDhT0a9EncXYubp9 gKUBIDfN07PUA==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-16v.sys.comcast.net with comcast id ykJq1s00B3KdFy101kJq4A; Wed, 25 May 2016 20:18:50 +0000
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B37FEAFFA@ESESSMB209.ericsson.se>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <652667a6-1853-6162-1e1a-a94603cf4893@alum.mit.edu>
Date: Wed, 25 May 2016 16:19:11 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FEAFFA@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Ma2718QUml6iHgC2CVpMXrfTAjc>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-dtls-sdp-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 20:18:54 -0000

WFM

On 5/25/16 3:20 PM, Christer Holmberg wrote:
> Hi,
>
>
>
> I’ve submitted a new version (-13) of draft-ietf-mmusic-dtls-sdp.
>
>
>
> The only change compared to the previous version is the change from
> “unreliable” to “unordered”.
>
>
>
> Are we done? :)
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Wed May 25 13:36:28 2016
Return-Path: <alan.b.johnston@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 9AA0C12DCFE; Wed, 25 May 2016 13:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnUx_5frUrui; Wed, 25 May 2016 13:36:22 -0700 (PDT)
Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com [209.85.192.47]) (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 D785A12D9C3; Wed, 25 May 2016 13:36:21 -0700 (PDT)
Received: by mail-qg0-f47.google.com with SMTP id q32so28146520qgq.3; Wed, 25 May 2016 13:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=hhPmYwhemrOGY5rBiuEBx0E2NeaL4fCpTZ6QAxhXUoQ=; b=H6YFsSL7tTSrw+TD0Icvpzry1LAFYDGAvbAPXOUh1Dz9GU+mEppeDn6nNcg0G3mtMj EA2GSPVPLzSjATUyyUz4fnaRkTTmNj0vJIfjMYNdnYApRG9elMG/jxaOPmteOkIHDZ0J Bv1CTUbv7h5V7rT2XW8ZnM05XJKu93GOjh5FWr0Z4Q9rbOBB0uqoSvNVZrfus6w+lE7Y upZsbqRqqmKeFpbdJttanjneyvZIPTAYrnv7z+ezRCDRu2T1nd6zMih9IyG6cigvrikS 5t/I/XE79YrME6Q2VpyOe01pebegEnYPYow3UjxfrdxDIYp2sdeRIxKxxr1UoBKuCJsq S/Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=hhPmYwhemrOGY5rBiuEBx0E2NeaL4fCpTZ6QAxhXUoQ=; b=FfrJIGiA/K/vUSrsT/9AthirLgV7KJCG8c/LJbT2V13tl+mODgQBnBfT49Pd1A2tps G3K9QePIU0/vhiopUz13JY3MHqXstNxqbioM3QNBZeW0dTh0EUwdr3c2KMf2JH1GtEMm bEj3nyz75XiembLb1Aj6jx7rWrLhY/ToOK0X+7lMOiw2CUSIGIjD43WRpeNaFKhT+Pb/ 6fdEDilw2R3c1BP6EYWkoxmHeIqbDJe3MxafAJDBdzvXQrxueF0WRe9lyDiESjkf3bhC tVrwntQsyIdWCJyn77J3n6YJpme+oJOhpf+FA2qvln1Efup0NXcaCbTpt+Zo2XEUMAJO wP2g==
X-Gm-Message-State: ALyK8tISo0XCdqkpU046gj12cZ6r0lUpeO/H8k8H7voVvFg08U3gQ7VKcjEtQUk7YtFi65yxeA58h/sG6osPpw==
MIME-Version: 1.0
X-Received: by 10.140.41.200 with SMTP id z66mr5408235qgz.20.1464208506147; Wed, 25 May 2016 13:35:06 -0700 (PDT)
Received: by 10.55.185.70 with HTTP; Wed, 25 May 2016 13:35:06 -0700 (PDT)
In-Reply-To: <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com>
Date: Wed, 25 May 2016 13:35:06 -0700
Message-ID: <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary=001a11c13b84e2dc4d0533b09b1f
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/l9gcZ6ABcgwZTOnq6_1CTDI04zQ>
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org, mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org, "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 20:36:24 -0000

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

Hi Marc,

Changing the packet format for ZRTP is a pretty major change to the
protocol...

I think the only case where this is an issue would be if both ZRTP and
DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
DTLS-SRTP arrives before the answer is received.    During this window of
time, a slightly more complicated algorithm could be used to distinguish
ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
present in every ZRTP message. Otherwise, only one of these protocols will
be used at a time, so it is not the same as distinguishing either from STUN
and RTP, which happens throughout a session.

We could put this guidance in a RFC6189bis draft, and the other documents
could just defer to that guidance if they support ZRTP in addition to
DTLS-SRTP opportunistically.

- Alan -

On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com> wrote:

> Hi Marc,
>
> That's along the lines that I expected, if the working group chooses this
> path. What do others think?
>
> Thanks!
>
> Ben.
>
> On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
>
> As you mention, there are several ways to handle this issue. We leave it
>> to the community to decide whether to include zrtp in bundle or not. If we
>> were to update the 5764-mux-fix draft, we felt that the cleanest way to
>> handle it is in two steps.
>>
>> One thing to note is that there is no clash/overlap with STUN, so using
>> magic cookie to distinguish from STUN is a moot point. The overlap with the
>> DTLS range is what we need to avoid. The right thing to do seems to be to
>> work on a rfc6189bis draft that would set bit 4 and 5 of the first byte of
>> the zrtp message to 0. This way zrtp cannot clash with DTLS.
>>
>> On the rfc5764-mux-fixes draft, we just change the algorithm to:
>>
>>            +----------------+
>>            |        [0..3] -+--> forward to STUN
>>            |                |
>>            |      [16..19] -+--> forward to ZRTP
>>            |                |
>> packet --> |      [20..63] -+--> forward to DTLS
>>            |                |
>>            |      [64..79] -+--> forward to TURN Channel
>>            |                |
>>            |    [128..191] -+--> forward to RTP/RTCP
>>            +----------------+
>>
>>
>> Does this seem like a reasonable approach?
>>
>>
>> On 05/24/2016 04:21 PM, Ben Campbell wrote:
>>
>>> Hi,
>>>
>>> There appears to be a discrepancy between
>>> draft-ietf-mmusic-sdp-mux-attributes and
>>> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be used
>>> with bundle.
>>>
>>> mux-attributes puts the zrtp-hash attribute [RFC6189] in the "transport"
>>> category, meaning, among other things, that it can be used in a bundle
>>> group. However, as the demux rules are currently defined 5764-mux-fixes,
>>> zrtp messages cannot actually be demuxed. (If I read things correctly, the
>>> first byte of a zrtp message will be 16, which is not in any of the "known
>>> ranges" described in 5765 or 5764-mux-fixes, and therefore the message MUST
>>> be dropped.
>>>
>>> That seems to leave the choice of adding zrtp messages to the demux
>>> rules in 5764-mux-fixes, or removing the implication that zrtp can be
>>> bundled from mux-attributes.
>>>
>>> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not be
>>> hard, but would be non-trivial. RFC 6189 calls for using the magic cookie
>>> to distinguish zrtp messages from stun messages.
>>>
>>> Do people have opinions how to move forward with this? Am I interpreting
>>> the conflict correctly?Keep in mind that ZRTP is not a standards-track
>>> spec. But at the same time, I'm not sure we want to exclude it from the
>>> bundle mechanism.
>>>
>>> Thanks!
>>>
>>> Ben.
>>>
>>>
>>> _______________________________________________
>>> Audio/Video Transport Core Maintenance
>>> avt@ietf.org
>>> https://www.ietf.org/mailman/listinfo/avt
>>>
>>>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Hi Marc,<div><br></div><div>Changing the packet format for=
 ZRTP is a pretty major change to the protocol... =C2=A0</div><div><br></di=
v><div>I think the only case where this is an issue would be if both ZRTP a=
nd DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or DTLS=
-SRTP arrives before the answer is received. =C2=A0 =C2=A0During this windo=
w of time, a slightly more complicated algorithm could be used to distingui=
sh ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is pr=
esent in every ZRTP message. Otherwise, only one of these protocols will be=
 used at a time, so it is not the same as distinguishing either from STUN a=
nd RTP, which happens throughout a session.</div><div><br></div><div>We cou=
ld put this guidance in a RFC6189bis draft, and the other documents could j=
ust defer to that guidance if they support ZRTP in addition to DTLS-SRTP op=
portunistically.</div><div><br></div><div>- Alan -</div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Wed, May 25, 2016 at 10:56 AM, Be=
n Campbell <span dir=3D"ltr">&lt;<a href=3D"mailto:ben@nostrum.com" target=
=3D"_blank">ben@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-=
left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi Ma=
rc,<br>
<br>
That&#39;s along the lines that I expected, if the working group chooses th=
is path. What do others think?<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
As you mention, there are several ways to handle this issue. We leave it to=
 the community to decide whether to include zrtp in bundle or not. If we we=
re to update the 5764-mux-fix draft, we felt that the cleanest way to handl=
e it is in two steps.<br>
<br>
One thing to note is that there is no clash/overlap with STUN, so using mag=
ic cookie to distinguish from STUN is a moot point. The overlap with the DT=
LS range is what we need to avoid. The right thing to do seems to be to wor=
k on a rfc6189bis draft that would set bit 4 and 5 of the first byte of the=
 zrtp message to 0. This way zrtp cannot clash with DTLS.<br>
<br>
On the rfc5764-mux-fixes draft, we just change the algorithm to:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+----------------+<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 [0..3=
] -+--&gt; forward to STUN<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 [16..19] -+-=
-&gt; forward to ZRTP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
packet --&gt; |=C2=A0 =C2=A0 =C2=A0 [20..63] -+--&gt; forward to DTLS<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 [64..79] -+-=
-&gt; forward to TURN Channel<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 [128..191] -+--&gt;=
 forward to RTP/RTCP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+----------------+<br>
<br>
<br>
Does this seem like a reasonable approach?<br>
<br>
<br>
On 05/24/2016 04:21 PM, Ben Campbell wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
Hi,<br>
<br>
There appears to be a discrepancy between draft-ietf-mmusic-sdp-mux-attribu=
tes and draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be=
 used with bundle.<br>
<br>
mux-attributes puts the zrtp-hash attribute [RFC6189] in the &quot;transpor=
t&quot; category, meaning, among other things, that it can be used in a bun=
dle group. However, as the demux rules are currently defined 5764-mux-fixes=
, zrtp messages cannot actually be demuxed. (If I read things correctly, th=
e first byte of a zrtp message will be 16, which is not in any of the &quot=
;known ranges&quot; described in 5765 or 5764-mux-fixes, and therefore the =
message MUST be dropped.<br>
<br>
That seems to leave the choice of adding zrtp messages to the demux rules i=
n 5764-mux-fixes, or removing the implication that zrtp can be bundled from=
 mux-attributes.<br>
<br>
Adding rules for demuxing zrtp to 5765-mux-fixes would probably not be hard=
, but would be non-trivial. RFC 6189 calls for using the magic cookie to di=
stinguish zrtp messages from stun messages.<br>
<br>
Do people have opinions how to move forward with this? Am I interpreting th=
e conflict correctly?Keep in mind that ZRTP is not a standards-track spec. =
But at the same time, I&#39;m not sure we want to exclude it from the bundl=
e mechanism.<br>
<br>
Thanks!<br>
<br>
Ben.<br>
<br>
<br>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
<br>
</blockquote></blockquote>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div><br></div></div>

--001a11c13b84e2dc4d0533b09b1f--


From nobody Wed May 25 13:40:52 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEC2912D9C2; Wed, 25 May 2016 13:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 rlIFILSdCHRQ; Wed, 25 May 2016 13:40:48 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D01F12D906; Wed, 25 May 2016 13:40:48 -0700 (PDT)
Received: from [10.0.1.18] (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 u4PKei62038129 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 25 May 2016 15:40:45 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.18]
From: "Ben Campbell" <ben@nostrum.com>
To: "Alan Johnston" <alan.b.johnston@gmail.com>
Date: Wed, 25 May 2016 15:40:44 -0500
Message-ID: <FC37C429-0F9F-4545-BDA1-5CC6D4CDB028@nostrum.com>
In-Reply-To: <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1ORw9BJ5t834L4bv76VRxBqGwNs>
Cc: Marc Petit-Huguenin <marc@petit-huguenin.org>, draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org, mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org, "avt@ietf.org WG" <avt@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 20:40:51 -0000

By the way, when I said "along the lines I expected", I was thinking in 
terms of the updated algorithm in mux-fixes, not an update to ZRTP. As 
an individual, I agree that changing the ZRTP packet format seems 
drastic, and I would be concerned that implementors would ignore such a 
change.

Thanks!

Ben.


On 25 May 2016, at 15:35, Alan Johnston wrote:

> Hi Marc,
>
> Changing the packet format for ZRTP is a pretty major change to the
> protocol...
>
> I think the only case where this is an issue would be if both ZRTP and
> DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
> DTLS-SRTP arrives before the answer is received.    During this window 
> of
> time, a slightly more complicated algorithm could be used to 
> distinguish
> ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
> present in every ZRTP message. Otherwise, only one of these protocols 
> will
> be used at a time, so it is not the same as distinguishing either from 
> STUN
> and RTP, which happens throughout a session.
>
> We could put this guidance in a RFC6189bis draft, and the other 
> documents
> could just defer to that guidance if they support ZRTP in addition to
> DTLS-SRTP opportunistically.
>
> - Alan -
>
> On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com> 
> wrote:
>
>> Hi Marc,
>>
>> That's along the lines that I expected, if the working group chooses 
>> this
>> path. What do others think?
>>
>> Thanks!
>>
>> Ben.
>>
>> On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
>>
>> As you mention, there are several ways to handle this issue. We leave 
>> it
>>> to the community to decide whether to include zrtp in bundle or not. 
>>> If we
>>> were to update the 5764-mux-fix draft, we felt that the cleanest way 
>>> to
>>> handle it is in two steps.
>>>
>>> One thing to note is that there is no clash/overlap with STUN, so 
>>> using
>>> magic cookie to distinguish from STUN is a moot point. The overlap 
>>> with the
>>> DTLS range is what we need to avoid. The right thing to do seems to 
>>> be to
>>> work on a rfc6189bis draft that would set bit 4 and 5 of the first 
>>> byte of
>>> the zrtp message to 0. This way zrtp cannot clash with DTLS.
>>>
>>> On the rfc5764-mux-fixes draft, we just change the algorithm to:
>>>
>>>            +----------------+
>>>            |        [0..3] -+--> forward to STUN
>>>            |                |
>>>            |      [16..19] -+--> forward to ZRTP
>>>            |                |
>>> packet --> |      [20..63] -+--> forward to DTLS
>>>            |                |
>>>            |      [64..79] -+--> forward to TURN Channel
>>>            |                |
>>>            |    [128..191] -+--> forward to RTP/RTCP
>>>            +----------------+
>>>
>>>
>>> Does this seem like a reasonable approach?
>>>
>>>
>>> On 05/24/2016 04:21 PM, Ben Campbell wrote:
>>>
>>>> Hi,
>>>>
>>>> There appears to be a discrepancy between
>>>> draft-ietf-mmusic-sdp-mux-attributes and
>>>> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be 
>>>> used
>>>> with bundle.
>>>>
>>>> mux-attributes puts the zrtp-hash attribute [RFC6189] in the 
>>>> "transport"
>>>> category, meaning, among other things, that it can be used in a 
>>>> bundle
>>>> group. However, as the demux rules are currently defined 
>>>> 5764-mux-fixes,
>>>> zrtp messages cannot actually be demuxed. (If I read things 
>>>> correctly, the
>>>> first byte of a zrtp message will be 16, which is not in any of the 
>>>> "known
>>>> ranges" described in 5765 or 5764-mux-fixes, and therefore the 
>>>> message MUST
>>>> be dropped.
>>>>
>>>> That seems to leave the choice of adding zrtp messages to the demux
>>>> rules in 5764-mux-fixes, or removing the implication that zrtp can 
>>>> be
>>>> bundled from mux-attributes.
>>>>
>>>> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not 
>>>> be
>>>> hard, but would be non-trivial. RFC 6189 calls for using the magic 
>>>> cookie
>>>> to distinguish zrtp messages from stun messages.
>>>>
>>>> Do people have opinions how to move forward with this? Am I 
>>>> interpreting
>>>> the conflict correctly?Keep in mind that ZRTP is not a 
>>>> standards-track
>>>> spec. But at the same time, I'm not sure we want to exclude it from 
>>>> the
>>>> bundle mechanism.
>>>>
>>>> Thanks!
>>>>
>>>> Ben.
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Core Maintenance
>>>> avt@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>
>>>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>


From nobody Wed May 25 13:57:03 2016
Return-Path: <gsalguei@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 7A73D12DAA4; Wed, 25 May 2016 13:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jDfWF79wBVRH; Wed, 25 May 2016 13:57:00 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4418F12DD5B; Wed, 25 May 2016 13:57:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8294; q=dns/txt; s=iport; t=1464209820; x=1465419420; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2Wg3mFiDPXTtNmqd2YKWrG4oOrFZYFsO13Dk92l0HdM=; b=k/No6srD7Epa9eu29HgQU35mjAQ+DBA4okyHkaJd8bk6w3eZ3qm4DdKh jDRcVafY9nqVtj2utFXNI1PMDLtImws907yzIGz8IpL90JMv3iJekHfHL 3wykm6xyVzUS38YceQPYnd8wVo+j22bKyW1FKnMsah+xVKmRbHehadx8y o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AYAgD2EEZX/5xdJa1cgzdWfQauBItvA?= =?us-ascii?q?Q2BeBcLhSVKAhyBKDgUAQEBAQEBAWUnhEMBAQEDAQEBASAEDToLBQsCAQgYAgI?= =?us-ascii?q?fBwICAh8GCxUQAgQOBRSIAQMPCA6xQI0SDYQpAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBFwWBAYUmgXaCVoJDgXwXgmorgi4FiASQADMBjCaBeYFph3uFOIYzgTGHZwE?= =?us-ascii?q?eAQFCggUBHBaBNW4BiQd/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,365,1459814400"; d="scan'208";a="108364072"
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; 25 May 2016 20:56:59 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u4PKuxr5013935 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 25 May 2016 20:56:59 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 25 May 2016 15:56:58 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1104.009; Wed, 25 May 2016 15:56:58 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Alan Johnston <alan.b.johnston@gmail.com>
Thread-Topic: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
Thread-Index: AQHRthL8VuJ5x/fyEE6AYexF7eizHZ/KQAMAgAAFTwCAACwxAIAABhuA
Date: Wed, 25 May 2016 20:56:58 +0000
Message-ID: <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com>
In-Reply-To: <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.114.3]
Content-Type: text/plain; charset="utf-8"
Content-ID: <296B7AE262BBA642B2EC0C0B2D903D2B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/MVar5ibRNxPTKJpfBfV5mwsbwTg>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 20:57:02 -0000

SGkgQWxhbiAtIA0KDQpPbmUgb2YgdGhlIHJlYXNvbnMgd2UgbWFkZSB0aGUgc3VnZ2VzdGlvbiB3
YXMgYmVjYXVzZSAoaW4gb3VyIGVzdGltYXRpb24pIGl0IGRpZCBub3QgaGF2ZSBhIG1ham9yIGlt
cGFjdCB0byB0aGUgWlJUUCBwYWNrZXQgZm9ybWF0LiBDdXJyZW50bHkgdGhlIHBhY2tldCBmb3Jt
YXQgaXM6DQoNCg0KICAgIDAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAy
ICAgICAgICAgICAgICAgICAgIDMNCiAgICAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1
IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDENCiAgICstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICB8MCAwIDAg
MXxOb3QgVXNlZCAoc2V0IHRvIHplcm8pIHwgICAgICAgICBTZXF1ZW5jZSBOdW1iZXIgICAgICAg
fA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSsNCiAgIHwgICAgICAgICAgICAgICAgIE1hZ2ljIENvb2tpZSAnWlJUUCcg
KDB4NWE1MjU0NTApICAgICAgICAgICAgICB8DQogICArLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgfCAgICAgICAgICAg
ICAgICAgICAgICAgIFNvdXJjZSBJZGVudGlmaWVyICAgICAgICAgICAgICAgICAgICAgIHwNCiAg
ICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rDQogICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfA0KICAgfCAgICAgICAgICAgWlJUUCBNZXNzYWdlIChsZW5n
dGggZGVwZW5kcyBvbiBNZXNzYWdlIFR5cGUpICAgICAgIHwNCiAgIHwgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgLiAuIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICB8ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgfA0KICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSsNCiAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgIENSQyAoMSB3
b3JkKSAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICArLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KDQoNCk91ciBwcm9w
b3NhbCB3YXMgdG8gc2V0IGJpdHMgNCBhbmQgNSB0byB6ZXJvLCB3aGljaCBpcyBjdXJyZW50bHkg
d2hhdCB0aGUgcHJvdG9jb2wgY2FsbHMgZm9yIGFuZCBzaG91bGQgaW1wbGljaXRseSBtYWtlIGFs
bCBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnMgY29tcGxpYW50LiAgQWxsIHdlIGFyZSBwcm9wb3Np
bmcgaXMgaXMgdG8gdGFrZSBiaXRzIDQgYW5kIDUgb3V0IG9mIHRoZSDigJxOb3QgVXNlZOKAnSBy
YW5nZSBhbmQgbGVhdmUgdGhlbSBmaXhlZCB0byB0aGUgdmFsdWUgdGhhdCBjdXJyZW50IGltcGxl
bWVudGF0aW9ucyB1c2UuICBEb2VzIHRoaXMgbWFrZSBzZW5zZT8NCg0KSW4gYW55IGNhc2UsIEni
gJlkIGxpa2UgdG8gdHJ5IGFuZCB1bmRlcnN0YW5kIHdoYXQgaW1wYWN0IHRoaXMgaGFzIHRvIHRo
ZSBjdXJyZW50IHJmYzU3NjQtbXV4LWZpeCB0ZXh0LiAgSXMgaXQgYXMgc2ltcGxlIGFzIGV4cGxp
Y2l0bHkgcmVzZXJ2aW5nIHZhbHVlcyAxNiAtIDE5IGZvciBaUlRQPyBPciBkaWQgeW91IGhhdmUg
c29tZXRoaW5nIGVsc2UgaW4gbWluZD8gIElmIHlvdSBjYW4gbWFrZSBzcGVjaWZpYyB0ZXh0IHN1
Z2dlc3Rpb25zIHRoYXQgd2lsbCBzaW1wbGlmeSB0aGluZ3MuDQoNClRoYW5rcywNCg0KR29uemFs
bw0KDQoNCiANCg0KDQo+IE9uIE1heSAyNSwgMjAxNiwgYXQgMTozNSBQTSwgQWxhbiBKb2huc3Rv
biA8YWxhbi5iLmpvaG5zdG9uQGdtYWlsLmNvbT4gd3JvdGU6DQo+IA0KPiBIaSBNYXJjLA0KPiAN
Cj4gQ2hhbmdpbmcgdGhlIHBhY2tldCBmb3JtYXQgZm9yIFpSVFAgaXMgYSBwcmV0dHkgbWFqb3Ig
Y2hhbmdlIHRvIHRoZSBwcm90b2NvbC4uLiAgDQo+IA0KPiBJIHRoaW5rIHRoZSBvbmx5IGNhc2Ug
d2hlcmUgdGhpcyBpcyBhbiBpc3N1ZSB3b3VsZCBiZSBpZiBib3RoIFpSVFAgYW5kIERUTFMtU1JU
UCBhcmUgb2ZmZXJlZCBvcHBvcnR1bmlzdGljYWxseSAoT1NSVFApLCBhbmQgZWl0aGVyIFpSVFAg
b3IgRFRMUy1TUlRQIGFycml2ZXMgYmVmb3JlIHRoZSBhbnN3ZXIgaXMgcmVjZWl2ZWQuICAgIER1
cmluZyB0aGlzIHdpbmRvdyBvZiB0aW1lLCBhIHNsaWdodGx5IG1vcmUgY29tcGxpY2F0ZWQgYWxn
b3JpdGhtIGNvdWxkIGJlIHVzZWQgdG8gZGlzdGluZ3Vpc2ggWlJUUCBmcm9tIERUTFMtU1JUUCwg
c3VjaCBhcyBjaGVja2luZyB0aGUgMzItYml0IG1hZ2ljIGNvb2tpZSB0aGF0IGlzIHByZXNlbnQg
aW4gZXZlcnkgWlJUUCBtZXNzYWdlLiBPdGhlcndpc2UsIG9ubHkgb25lIG9mIHRoZXNlIHByb3Rv
Y29scyB3aWxsIGJlIHVzZWQgYXQgYSB0aW1lLCBzbyBpdCBpcyBub3QgdGhlIHNhbWUgYXMgZGlz
dGluZ3Vpc2hpbmcgZWl0aGVyIGZyb20gU1RVTiBhbmQgUlRQLCB3aGljaCBoYXBwZW5zIHRocm91
Z2hvdXQgYSBzZXNzaW9uLg0KPiANCj4gV2UgY291bGQgcHV0IHRoaXMgZ3VpZGFuY2UgaW4gYSBS
RkM2MTg5YmlzIGRyYWZ0LCBhbmQgdGhlIG90aGVyIGRvY3VtZW50cyBjb3VsZCBqdXN0IGRlZmVy
IHRvIHRoYXQgZ3VpZGFuY2UgaWYgdGhleSBzdXBwb3J0IFpSVFAgaW4gYWRkaXRpb24gdG8gRFRM
Uy1TUlRQIG9wcG9ydHVuaXN0aWNhbGx5Lg0KPiANCj4gLSBBbGFuIC0NCj4gDQo+IE9uIFdlZCwg
TWF5IDI1LCAyMDE2IGF0IDEwOjU2IEFNLCBCZW4gQ2FtcGJlbGwgPGJlbkBub3N0cnVtLmNvbT4g
d3JvdGU6DQo+IEhpIE1hcmMsDQo+IA0KPiBUaGF0J3MgYWxvbmcgdGhlIGxpbmVzIHRoYXQgSSBl
eHBlY3RlZCwgaWYgdGhlIHdvcmtpbmcgZ3JvdXAgY2hvb3NlcyB0aGlzIHBhdGguIFdoYXQgZG8g
b3RoZXJzIHRoaW5rPw0KPiANCj4gVGhhbmtzIQ0KPiANCj4gQmVuLg0KPiANCj4gT24gMjUgTWF5
IDIwMTYsIGF0IDEyOjM3LCBNYXJjIFBldGl0LUh1Z3VlbmluIHdyb3RlOg0KPiANCj4gQXMgeW91
IG1lbnRpb24sIHRoZXJlIGFyZSBzZXZlcmFsIHdheXMgdG8gaGFuZGxlIHRoaXMgaXNzdWUuIFdl
IGxlYXZlIGl0IHRvIHRoZSBjb21tdW5pdHkgdG8gZGVjaWRlIHdoZXRoZXIgdG8gaW5jbHVkZSB6
cnRwIGluIGJ1bmRsZSBvciBub3QuIElmIHdlIHdlcmUgdG8gdXBkYXRlIHRoZSA1NzY0LW11eC1m
aXggZHJhZnQsIHdlIGZlbHQgdGhhdCB0aGUgY2xlYW5lc3Qgd2F5IHRvIGhhbmRsZSBpdCBpcyBp
biB0d28gc3RlcHMuDQo+IA0KPiBPbmUgdGhpbmcgdG8gbm90ZSBpcyB0aGF0IHRoZXJlIGlzIG5v
IGNsYXNoL292ZXJsYXAgd2l0aCBTVFVOLCBzbyB1c2luZyBtYWdpYyBjb29raWUgdG8gZGlzdGlu
Z3Vpc2ggZnJvbSBTVFVOIGlzIGEgbW9vdCBwb2ludC4gVGhlIG92ZXJsYXAgd2l0aCB0aGUgRFRM
UyByYW5nZSBpcyB3aGF0IHdlIG5lZWQgdG8gYXZvaWQuIFRoZSByaWdodCB0aGluZyB0byBkbyBz
ZWVtcyB0byBiZSB0byB3b3JrIG9uIGEgcmZjNjE4OWJpcyBkcmFmdCB0aGF0IHdvdWxkIHNldCBi
aXQgNCBhbmQgNSBvZiB0aGUgZmlyc3QgYnl0ZSBvZiB0aGUgenJ0cCBtZXNzYWdlIHRvIDAuIFRo
aXMgd2F5IHpydHAgY2Fubm90IGNsYXNoIHdpdGggRFRMUy4NCj4gDQo+IE9uIHRoZSByZmM1NzY0
LW11eC1maXhlcyBkcmFmdCwgd2UganVzdCBjaGFuZ2UgdGhlIGFsZ29yaXRobSB0bzoNCj4gDQo+
ICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0rDQo+ICAgICAgICAgICAgfCAgICAgICAgWzAu
LjNdIC0rLS0+IGZvcndhcmQgdG8gU1RVTg0KPiAgICAgICAgICAgIHwgICAgICAgICAgICAgICAg
fA0KPiAgICAgICAgICAgIHwgICAgICBbMTYuLjE5XSAtKy0tPiBmb3J3YXJkIHRvIFpSVFANCj4g
ICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwNCj4gcGFja2V0IC0tPiB8ICAgICAgWzIwLi42
M10gLSstLT4gZm9yd2FyZCB0byBEVExTDQo+ICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8
DQo+ICAgICAgICAgICAgfCAgICAgIFs2NC4uNzldIC0rLS0+IGZvcndhcmQgdG8gVFVSTiBDaGFu
bmVsDQo+ICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8DQo+ICAgICAgICAgICAgfCAgICBb
MTI4Li4xOTFdIC0rLS0+IGZvcndhcmQgdG8gUlRQL1JUQ1ANCj4gICAgICAgICAgICArLS0tLS0t
LS0tLS0tLS0tLSsNCj4gDQo+IA0KPiBEb2VzIHRoaXMgc2VlbSBsaWtlIGEgcmVhc29uYWJsZSBh
cHByb2FjaD8NCj4gDQo+IA0KPiBPbiAwNS8yNC8yMDE2IDA0OjIxIFBNLCBCZW4gQ2FtcGJlbGwg
d3JvdGU6DQo+IEhpLA0KPiANCj4gVGhlcmUgYXBwZWFycyB0byBiZSBhIGRpc2NyZXBhbmN5IGJl
dHdlZW4gZHJhZnQtaWV0Zi1tbXVzaWMtc2RwLW11eC1hdHRyaWJ1dGVzIGFuZCBkcmFmdC1pZXRm
LWF2dGNvcmUtcmZjNTc2NC1tdXgtZml4ZXMgY29uY2VybmluZyB3aGV0aGVyIHpydHAgY2FuIGJl
IHVzZWQgd2l0aCBidW5kbGUuDQo+IA0KPiBtdXgtYXR0cmlidXRlcyBwdXRzIHRoZSB6cnRwLWhh
c2ggYXR0cmlidXRlIFtSRkM2MTg5XSBpbiB0aGUgInRyYW5zcG9ydCIgY2F0ZWdvcnksIG1lYW5p
bmcsIGFtb25nIG90aGVyIHRoaW5ncywgdGhhdCBpdCBjYW4gYmUgdXNlZCBpbiBhIGJ1bmRsZSBn
cm91cC4gSG93ZXZlciwgYXMgdGhlIGRlbXV4IHJ1bGVzIGFyZSBjdXJyZW50bHkgZGVmaW5lZCA1
NzY0LW11eC1maXhlcywgenJ0cCBtZXNzYWdlcyBjYW5ub3QgYWN0dWFsbHkgYmUgZGVtdXhlZC4g
KElmIEkgcmVhZCB0aGluZ3MgY29ycmVjdGx5LCB0aGUgZmlyc3QgYnl0ZSBvZiBhIHpydHAgbWVz
c2FnZSB3aWxsIGJlIDE2LCB3aGljaCBpcyBub3QgaW4gYW55IG9mIHRoZSAia25vd24gcmFuZ2Vz
IiBkZXNjcmliZWQgaW4gNTc2NSBvciA1NzY0LW11eC1maXhlcywgYW5kIHRoZXJlZm9yZSB0aGUg
bWVzc2FnZSBNVVNUIGJlIGRyb3BwZWQuDQo+IA0KPiBUaGF0IHNlZW1zIHRvIGxlYXZlIHRoZSBj
aG9pY2Ugb2YgYWRkaW5nIHpydHAgbWVzc2FnZXMgdG8gdGhlIGRlbXV4IHJ1bGVzIGluIDU3NjQt
bXV4LWZpeGVzLCBvciByZW1vdmluZyB0aGUgaW1wbGljYXRpb24gdGhhdCB6cnRwIGNhbiBiZSBi
dW5kbGVkIGZyb20gbXV4LWF0dHJpYnV0ZXMuDQo+IA0KPiBBZGRpbmcgcnVsZXMgZm9yIGRlbXV4
aW5nIHpydHAgdG8gNTc2NS1tdXgtZml4ZXMgd291bGQgcHJvYmFibHkgbm90IGJlIGhhcmQsIGJ1
dCB3b3VsZCBiZSBub24tdHJpdmlhbC4gUkZDIDYxODkgY2FsbHMgZm9yIHVzaW5nIHRoZSBtYWdp
YyBjb29raWUgdG8gZGlzdGluZ3Vpc2ggenJ0cCBtZXNzYWdlcyBmcm9tIHN0dW4gbWVzc2FnZXMu
DQo+IA0KPiBEbyBwZW9wbGUgaGF2ZSBvcGluaW9ucyBob3cgdG8gbW92ZSBmb3J3YXJkIHdpdGgg
dGhpcz8gQW0gSSBpbnRlcnByZXRpbmcgdGhlIGNvbmZsaWN0IGNvcnJlY3RseT9LZWVwIGluIG1p
bmQgdGhhdCBaUlRQIGlzIG5vdCBhIHN0YW5kYXJkcy10cmFjayBzcGVjLiBCdXQgYXQgdGhlIHNh
bWUgdGltZSwgSSdtIG5vdCBzdXJlIHdlIHdhbnQgdG8gZXhjbHVkZSBpdCBmcm9tIHRoZSBidW5k
bGUgbWVjaGFuaXNtLg0KPiANCj4gVGhhbmtzIQ0KPiANCj4gQmVuLg0KPiANCj4gDQo+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEF1ZGlvL1ZpZGVv
IFRyYW5zcG9ydCBDb3JlIE1haW50ZW5hbmNlDQo+IGF2dEBpZXRmLm9yZw0KPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dA0KPiANCj4gDQo+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1tdXNpYyBtYWlsaW5nIGxpc3QN
Cj4gbW11c2ljQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vbW11c2ljDQo+IA0KDQo=


From nobody Wed May 25 20:01:36 2016
Return-Path: <alan.b.johnston@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 6DE8412D524; Wed, 25 May 2016 20:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6hpz5Lm7OF6w; Wed, 25 May 2016 20:01:29 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B80D112D50C; Wed, 25 May 2016 20:01:28 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id y126so49897554qke.1; Wed, 25 May 2016 20:01:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=FCiSbClJRkzPw6NtmvKri17jlBazlX7MJaUIUcbwuY8=; b=mLXZMv+alNlJ4gxJA3HzEoQnJsEoh1uE/sgoOviTlhJzpIgsm5ZpIUMnG8TwpNizvT 9L+j5kEbWnwgTDHzRQbOPKkSIIV86Mu92gJ03tfte5u9D7i1i/ZnEJs9dAAnyR/39/qg +9kl5jfBYJQ22fHSypg0zEXp4tLRjZtjvJJk/qYbU+qGLbqTSQGSg+wxBitIWr8DRYBZ +fbERs5v5EGTlFDd77qK+KZG1uv3KyleGJWN8WtZYI5Ba46mHJNVtGtD3wFElXSoHLs+ AAfUN8DKzeXU6/1J/b65gXiktnFous3WJySmAT+N62QrrLwK/eZHN268tzln9O5ERVCY BSwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=FCiSbClJRkzPw6NtmvKri17jlBazlX7MJaUIUcbwuY8=; b=Bh0zcg8CQ+HwQtZlDHL5aG6V6jC23dmNy10VZlGvgle+V/TAS2vONs05wtSwLpXqOZ 6fjMwWCmwNaUxkoBZfRW7XssLhiyYBRh6hB3h/sSr0rld2dK81LvyRfCoUFxO+sIV/cb m2LfPjZ1X2L+fYmzYdMjExMxVZlwkwKfaJvRpsz96OON2cV8E2e48fsu1/6jLSB+Y2eA WzTUftSoQAqE6a13m/U/4CvpUvIV0zbOwdzcqoISPGsV4LqJWZClthRkB6hllSoRqkYr xLy4/YVnpiqBYjJpWdy6Xim744HtMSN0pTOSdjfcY5PpblXJtQTGIwuX+LiFhCaGXcpn FM3Q==
X-Gm-Message-State: ALyK8tKMEsr3nvlTVpMMf25kAqY3KHO5Fut4XSL4wtAt7XrtHJiDLgwbXs7iDnKhs63HWJLX7pPK5DNW7RxqTw==
MIME-Version: 1.0
X-Received: by 10.200.47.6 with SMTP id j6mr6956582qta.85.1464231687737; Wed, 25 May 2016 20:01:27 -0700 (PDT)
Received: by 10.55.185.70 with HTTP; Wed, 25 May 2016 20:01:27 -0700 (PDT)
In-Reply-To: <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com> <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com>
Date: Wed, 25 May 2016 20:01:27 -0700
Message-ID: <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Content-Type: multipart/alternative; boundary=001a1136f16c9de10d0533b60178
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/jwl0tUQ9jMmd8wA9wpHJiBTLg6k>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 03:01:32 -0000

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

Hi Gonzalo,

Thanks for the clarification - I had it backwards in my head.   Existing
ZRTP implementations will be compliant to the proposal, and we can
constrain those bits to 0 in the 6189bis draft to lock it down.

So I am OK with this proposal.

- Alan -

On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gsalguei) <
gsalguei@cisco.com> wrote:

> Hi Alan -
>
> One of the reasons we made the suggestion was because (in our estimation)
> it did not have a major impact to the ZRTP packet format. Currently the
> packet format is:
>
>
>     0                   1                   2                   3
>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |0 0 0 1|Not Used (set to zero) |         Sequence Number       |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                 Magic Cookie 'ZRTP' (0x5a525450)              |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                        Source Identifier                      |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                                                               |
>    |           ZRTP Message (length depends on Message Type)       |
>    |                            . . .                              |
>    |                                                               |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>    |                          CRC (1 word)                         |
>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> Our proposal was to set bits 4 and 5 to zero, which is currently what the
> protocol calls for and should implicitly make all existing implementation=
s
> compliant.  All we are proposing is is to take bits 4 and 5 out of the =
=E2=80=9CNot
> Used=E2=80=9D range and leave them fixed to the value that current implem=
entations
> use.  Does this make sense?
>
> In any case, I=E2=80=99d like to try and understand what impact this has =
to the
> current rfc5764-mux-fix text.  Is it as simple as explicitly reserving
> values 16 - 19 for ZRTP? Or did you have something else in mind?  If you
> can make specific text suggestions that will simplify things.
>
> Thanks,
>
> Gonzalo
>
>
>
>
>
> > On May 25, 2016, at 1:35 PM, Alan Johnston <alan.b.johnston@gmail.com>
> wrote:
> >
> > Hi Marc,
> >
> > Changing the packet format for ZRTP is a pretty major change to the
> protocol...
> >
> > I think the only case where this is an issue would be if both ZRTP and
> DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
> DTLS-SRTP arrives before the answer is received.    During this window of
> time, a slightly more complicated algorithm could be used to distinguish
> ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
> present in every ZRTP message. Otherwise, only one of these protocols wil=
l
> be used at a time, so it is not the same as distinguishing either from ST=
UN
> and RTP, which happens throughout a session.
> >
> > We could put this guidance in a RFC6189bis draft, and the other
> documents could just defer to that guidance if they support ZRTP in
> addition to DTLS-SRTP opportunistically.
> >
> > - Alan -
> >
> > On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com> wrote:
> > Hi Marc,
> >
> > That's along the lines that I expected, if the working group chooses
> this path. What do others think?
> >
> > Thanks!
> >
> > Ben.
> >
> > On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
> >
> > As you mention, there are several ways to handle this issue. We leave i=
t
> to the community to decide whether to include zrtp in bundle or not. If w=
e
> were to update the 5764-mux-fix draft, we felt that the cleanest way to
> handle it is in two steps.
> >
> > One thing to note is that there is no clash/overlap with STUN, so using
> magic cookie to distinguish from STUN is a moot point. The overlap with t=
he
> DTLS range is what we need to avoid. The right thing to do seems to be to
> work on a rfc6189bis draft that would set bit 4 and 5 of the first byte o=
f
> the zrtp message to 0. This way zrtp cannot clash with DTLS.
> >
> > On the rfc5764-mux-fixes draft, we just change the algorithm to:
> >
> >            +----------------+
> >            |        [0..3] -+--> forward to STUN
> >            |                |
> >            |      [16..19] -+--> forward to ZRTP
> >            |                |
> > packet --> |      [20..63] -+--> forward to DTLS
> >            |                |
> >            |      [64..79] -+--> forward to TURN Channel
> >            |                |
> >            |    [128..191] -+--> forward to RTP/RTCP
> >            +----------------+
> >
> >
> > Does this seem like a reasonable approach?
> >
> >
> > On 05/24/2016 04:21 PM, Ben Campbell wrote:
> > Hi,
> >
> > There appears to be a discrepancy between
> draft-ietf-mmusic-sdp-mux-attributes and
> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be used
> with bundle.
> >
> > mux-attributes puts the zrtp-hash attribute [RFC6189] in the "transport=
"
> category, meaning, among other things, that it can be used in a bundle
> group. However, as the demux rules are currently defined 5764-mux-fixes,
> zrtp messages cannot actually be demuxed. (If I read things correctly, th=
e
> first byte of a zrtp message will be 16, which is not in any of the "know=
n
> ranges" described in 5765 or 5764-mux-fixes, and therefore the message MU=
ST
> be dropped.
> >
> > That seems to leave the choice of adding zrtp messages to the demux
> rules in 5764-mux-fixes, or removing the implication that zrtp can be
> bundled from mux-attributes.
> >
> > Adding rules for demuxing zrtp to 5765-mux-fixes would probably not be
> hard, but would be non-trivial. RFC 6189 calls for using the magic cookie
> to distinguish zrtp messages from stun messages.
> >
> > Do people have opinions how to move forward with this? Am I interpretin=
g
> the conflict correctly?Keep in mind that ZRTP is not a standards-track
> spec. But at the same time, I'm not sure we want to exclude it from the
> bundle mechanism.
> >
> > Thanks!
> >
> > Ben.
> >
> >
> > _______________________________________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
> >
>
>

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

<div dir=3D"ltr">Hi Gonzalo,<div><br></div><div>Thanks for the clarificatio=
n - I had it backwards in my head. =C2=A0 Existing ZRTP implementations wil=
l be compliant to the proposal, and we can constrain those bits to 0 in the=
 6189bis draft to lock it down.</div><div><br></div><div>So I am OK with th=
is proposal.</div><div><br></div><div>- Alan -</div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Wed, May 25, 2016 at 1:56 PM, Gonzalo=
 Salgueiro (gsalguei) <span dir=3D"ltr">&lt;<a href=3D"mailto:gsalguei@cisc=
o.com" target=3D"_blank">gsalguei@cisco.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">Hi Alan -<br>
<br>
One of the reasons we made the suggestion was because (in our estimation) i=
t did not have a major impact to the ZRTP packet format. Currently the pack=
et format is:<br>
<br>
<br>
=C2=A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A03<br>
=C2=A0 =C2=A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0=
 1<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
=C2=A0 =C2=A0|0 0 0 1|Not Used (set to zero) |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0Sequence Number=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0Magic Cookie &#39;ZRTP&#39; (0x5a525450)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Source Identifier=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ZRTP Message (length=
 depends on Message Type)=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 . . .=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=
<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 CRC (1 word)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<br>
<br>
<br>
Our proposal was to set bits 4 and 5 to zero, which is currently what the p=
rotocol calls for and should implicitly make all existing implementations c=
ompliant.=C2=A0 All we are proposing is is to take bits 4 and 5 out of the =
=E2=80=9CNot Used=E2=80=9D range and leave them fixed to the value that cur=
rent implementations use.=C2=A0 Does this make sense?<br>
<br>
In any case, I=E2=80=99d like to try and understand what impact this has to=
 the current rfc5764-mux-fix text.=C2=A0 Is it as simple as explicitly rese=
rving values 16 - 19 for ZRTP? Or did you have something else in mind?=C2=
=A0 If you can make specific text suggestions that will simplify things.<br=
>
<br>
Thanks,<br>
<br>
Gonzalo<br>
<br>
<br>
<br>
<br>
<br>
&gt; On May 25, 2016, at 1:35 PM, Alan Johnston &lt;<a href=3D"mailto:alan.=
b.johnston@gmail.com">alan.b.johnston@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Marc,<br>
&gt;<br>
&gt; Changing the packet format for ZRTP is a pretty major change to the pr=
otocol...<br>
&gt;<br>
&gt; I think the only case where this is an issue would be if both ZRTP and=
 DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or DTLS-S=
RTP arrives before the answer is received.=C2=A0 =C2=A0 During this window =
of time, a slightly more complicated algorithm could be used to distinguish=
 ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is pres=
ent in every ZRTP message. Otherwise, only one of these protocols will be u=
sed at a time, so it is not the same as distinguishing either from STUN and=
 RTP, which happens throughout a session.<br>
&gt;<br>
&gt; We could put this guidance in a RFC6189bis draft, and the other docume=
nts could just defer to that guidance if they support ZRTP in addition to D=
TLS-SRTP opportunistically.<br>
&gt;<br>
&gt; - Alan -<br>
&gt;<br>
&gt; On Wed, May 25, 2016 at 10:56 AM, Ben Campbell &lt;<a href=3D"mailto:b=
en@nostrum.com">ben@nostrum.com</a>&gt; wrote:<br>
&gt; Hi Marc,<br>
&gt;<br>
&gt; That&#39;s along the lines that I expected, if the working group choos=
es this path. What do others think?<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Ben.<br>
&gt;<br>
&gt; On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:<br>
&gt;<br>
&gt; As you mention, there are several ways to handle this issue. We leave =
it to the community to decide whether to include zrtp in bundle or not. If =
we were to update the 5764-mux-fix draft, we felt that the cleanest way to =
handle it is in two steps.<br>
&gt;<br>
&gt; One thing to note is that there is no clash/overlap with STUN, so usin=
g magic cookie to distinguish from STUN is a moot point. The overlap with t=
he DTLS range is what we need to avoid. The right thing to do seems to be t=
o work on a rfc6189bis draft that would set bit 4 and 5 of the first byte o=
f the zrtp message to 0. This way zrtp cannot clash with DTLS.<br>
&gt;<br>
&gt; On the rfc5764-mux-fixes draft, we just change the algorithm to:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +----------------+<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
[0..3] -+--&gt; forward to STUN<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 [16..19=
] -+--&gt; forward to ZRTP<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; packet --&gt; |=C2=A0 =C2=A0 =C2=A0 [20..63] -+--&gt; forward to DTLS<=
br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 [64..79=
] -+--&gt; forward to TURN Channel<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 [128..191] -+-=
-&gt; forward to RTP/RTCP<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +----------------+<br>
&gt;<br>
&gt;<br>
&gt; Does this seem like a reasonable approach?<br>
&gt;<br>
&gt;<br>
&gt; On 05/24/2016 04:21 PM, Ben Campbell wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; There appears to be a discrepancy between draft-ietf-mmusic-sdp-mux-at=
tributes and draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp c=
an be used with bundle.<br>
&gt;<br>
&gt; mux-attributes puts the zrtp-hash attribute [RFC6189] in the &quot;tra=
nsport&quot; category, meaning, among other things, that it can be used in =
a bundle group. However, as the demux rules are currently defined 5764-mux-=
fixes, zrtp messages cannot actually be demuxed. (If I read things correctl=
y, the first byte of a zrtp message will be 16, which is not in any of the =
&quot;known ranges&quot; described in 5765 or 5764-mux-fixes, and therefore=
 the message MUST be dropped.<br>
&gt;<br>
&gt; That seems to leave the choice of adding zrtp messages to the demux ru=
les in 5764-mux-fixes, or removing the implication that zrtp can be bundled=
 from mux-attributes.<br>
&gt;<br>
&gt; Adding rules for demuxing zrtp to 5765-mux-fixes would probably not be=
 hard, but would be non-trivial. RFC 6189 calls for using the magic cookie =
to distinguish zrtp messages from stun messages.<br>
&gt;<br>
&gt; Do people have opinions how to move forward with this? Am I interpreti=
ng the conflict correctly?Keep in mind that ZRTP is not a standards-track s=
pec. But at the same time, I&#39;m not sure we want to exclude it from the =
bundle mechanism.<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Ben.<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Audio/Video Transport Core Maintenance<br>
&gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferre=
r" target=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; mmusic mailing list<br>
&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefe=
rrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br=
>
&gt;<br>
<br>
</blockquote></div><br></div></div>

--001a1136f16c9de10d0533b60178--


From nobody Wed May 25 20:05:48 2016
Return-Path: <gsalguei@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 2B80312D539; Wed, 25 May 2016 20:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8471qAHFEjC; Wed, 25 May 2016 20:05:45 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17BB112D50C; Wed, 25 May 2016 20:05:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9444; q=dns/txt; s=iport; t=1464231945; x=1465441545; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=IeIRA+eICLOssRJyWk0B94yxVqYWanfdZVNGNNa6ep0=; b=Dk/wu8asL1ttZTtIAL/oYjRt/sJiVlo2PJ2VzBmvYwdqgI3WCI3f2RvH 3NyHY7tiqPPI30UehDsGzISxg+8BPlWQ2UBnqUOtBGJ8mEfNon8RqF4PF dK64nlvLHiZs0vtH1HpNTjRE+YCSURdkzWZkORtHD91i/ZD4T1pGfPjx8 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D4AQD2ZkZX/5FdJa1cgzlWfQauBotvA?= =?us-ascii?q?Q2BeBcLhSVKAhyBGTgUAQEBAQEBAWUnhEMBAQEDAQEBASAEDToLBQsCAQgYAgI?= =?us-ascii?q?fBwICAh8GCxUQAgQOBRSIAQMPCA6xM40QDYQtAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBFwWBAYUmgXaCVoJDghOCaiuCLgWIBJAAMwGMJoF5gWmHe4U4hjOBMYdnAR4?= =?us-ascii?q?BAUKCBQEcFoE1bgGJFX8BAQE?=
X-IronPort-AV: E=Sophos;i="5.26,366,1459814400"; d="scan'208";a="277858087"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2016 03:05:44 +0000
Received: from XCH-ALN-007.cisco.com (xch-aln-007.cisco.com [173.36.7.17]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id u4Q35iSf022141 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 26 May 2016 03:05:44 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-ALN-007.cisco.com (173.36.7.17) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 25 May 2016 22:05:43 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1104.009; Wed, 25 May 2016 22:05:43 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Alan Johnston <alan.b.johnston@gmail.com>
Thread-Topic: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
Thread-Index: AQHRthL8VuJ5x/fyEE6AYexF7eizHZ/KQAMAgAAFTwCAACwxAIAABhuAgABl14CAAAEuAA==
Date: Thu, 26 May 2016 03:05:43 +0000
Message-ID: <CCF13C88-3C10-4E73-88A5-B70BA1C15A20@cisco.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com> <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com> <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com>
In-Reply-To: <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.114.3]
Content-Type: text/plain; charset="utf-8"
Content-ID: <0816D2BDF5AAD8449F9A55AD8CF1752F@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/p02iBpdY9exsWLdrenyNRetY8PY>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 03:05:47 -0000

T0ssIGNvb2wgIFRoYW5rcywgQWxhbi4gIE9uY2Ugd2UgZ2V0IGNvbnNlbnN1cyBmcm9tIHRoZSBX
RyhzKSB0aGF0IHRoaXMgaXMgdGhlIGJlc3Qgd2F5IGZvcndhcmQgd2Ugd2lsbCBtYWtlIHRoaXMg
Y2hhbmdlIHRvIGRyYWZ0LWlldGYtYXZ0Y29yZS1yZmM1NzY0LW11eC1maXhlcy4NCg0KQ2hlZXJz
LA0KDQpHb256YWxvDQoNCj4gT24gTWF5IDI1LCAyMDE2LCBhdCA4OjAxIFBNLCBBbGFuIEpvaG5z
dG9uIDxhbGFuLmIuam9obnN0b25AZ21haWwuY29tPiB3cm90ZToNCj4gDQo+IEhpIEdvbnphbG8s
DQo+IA0KPiBUaGFua3MgZm9yIHRoZSBjbGFyaWZpY2F0aW9uIC0gSSBoYWQgaXQgYmFja3dhcmRz
IGluIG15IGhlYWQuICAgRXhpc3RpbmcgWlJUUCBpbXBsZW1lbnRhdGlvbnMgd2lsbCBiZSBjb21w
bGlhbnQgdG8gdGhlIHByb3Bvc2FsLCBhbmQgd2UgY2FuIGNvbnN0cmFpbiB0aG9zZSBiaXRzIHRv
IDAgaW4gdGhlIDYxODliaXMgZHJhZnQgdG8gbG9jayBpdCBkb3duLg0KPiANCj4gU28gSSBhbSBP
SyB3aXRoIHRoaXMgcHJvcG9zYWwuDQo+IA0KPiAtIEFsYW4gLQ0KPiANCj4gT24gV2VkLCBNYXkg
MjUsIDIwMTYgYXQgMTo1NiBQTSwgR29uemFsbyBTYWxndWVpcm8gKGdzYWxndWVpKSA8Z3NhbGd1
ZWlAY2lzY28uY29tPiB3cm90ZToNCj4gSGkgQWxhbiAtDQo+IA0KPiBPbmUgb2YgdGhlIHJlYXNv
bnMgd2UgbWFkZSB0aGUgc3VnZ2VzdGlvbiB3YXMgYmVjYXVzZSAoaW4gb3VyIGVzdGltYXRpb24p
IGl0IGRpZCBub3QgaGF2ZSBhIG1ham9yIGltcGFjdCB0byB0aGUgWlJUUCBwYWNrZXQgZm9ybWF0
LiBDdXJyZW50bHkgdGhlIHBhY2tldCBmb3JtYXQgaXM6DQo+IA0KPiANCj4gICAgIDAgICAgICAg
ICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMNCj4g
ICAgIDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2
IDcgOCA5IDAgMQ0KPiAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KPiAgICB8MCAwIDAgMXxOb3QgVXNlZCAoc2V0IHRv
IHplcm8pIHwgICAgICAgICBTZXF1ZW5jZSBOdW1iZXIgICAgICAgfA0KPiAgICArLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0K
PiAgICB8ICAgICAgICAgICAgICAgICBNYWdpYyBDb29raWUgJ1pSVFAnICgweDVhNTI1NDUwKSAg
ICAgICAgICAgICAgfA0KPiAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KPiAgICB8ICAgICAgICAgICAgICAgICAgICAg
ICAgU291cmNlIElkZW50aWZpZXIgICAgICAgICAgICAgICAgICAgICAgfA0KPiAgICArLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Kw0KPiAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgfA0KPiAgICB8ICAgICAgICAgICBaUlRQIE1lc3NhZ2UgKGxlbmd0aCBk
ZXBlbmRzIG9uIE1lc3NhZ2UgVHlwZSkgICAgICAgfA0KPiAgICB8ICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIC4gLiAuICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KPiAgICB8ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgfA0KPiAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKw0KPiAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICBDUkMg
KDEgd29yZCkgICAgICAgICAgICAgICAgICAgICAgICAgfA0KPiAgICArLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KPiANCj4g
DQo+IE91ciBwcm9wb3NhbCB3YXMgdG8gc2V0IGJpdHMgNCBhbmQgNSB0byB6ZXJvLCB3aGljaCBp
cyBjdXJyZW50bHkgd2hhdCB0aGUgcHJvdG9jb2wgY2FsbHMgZm9yIGFuZCBzaG91bGQgaW1wbGlj
aXRseSBtYWtlIGFsbCBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnMgY29tcGxpYW50LiAgQWxsIHdl
IGFyZSBwcm9wb3NpbmcgaXMgaXMgdG8gdGFrZSBiaXRzIDQgYW5kIDUgb3V0IG9mIHRoZSDigJxO
b3QgVXNlZOKAnSByYW5nZSBhbmQgbGVhdmUgdGhlbSBmaXhlZCB0byB0aGUgdmFsdWUgdGhhdCBj
dXJyZW50IGltcGxlbWVudGF0aW9ucyB1c2UuICBEb2VzIHRoaXMgbWFrZSBzZW5zZT8NCj4gDQo+
IEluIGFueSBjYXNlLCBJ4oCZZCBsaWtlIHRvIHRyeSBhbmQgdW5kZXJzdGFuZCB3aGF0IGltcGFj
dCB0aGlzIGhhcyB0byB0aGUgY3VycmVudCByZmM1NzY0LW11eC1maXggdGV4dC4gIElzIGl0IGFz
IHNpbXBsZSBhcyBleHBsaWNpdGx5IHJlc2VydmluZyB2YWx1ZXMgMTYgLSAxOSBmb3IgWlJUUD8g
T3IgZGlkIHlvdSBoYXZlIHNvbWV0aGluZyBlbHNlIGluIG1pbmQ/ICBJZiB5b3UgY2FuIG1ha2Ug
c3BlY2lmaWMgdGV4dCBzdWdnZXN0aW9ucyB0aGF0IHdpbGwgc2ltcGxpZnkgdGhpbmdzLg0KPiAN
Cj4gVGhhbmtzLA0KPiANCj4gR29uemFsbw0KPiANCj4gDQo+IA0KPiANCj4gDQo+ID4gT24gTWF5
IDI1LCAyMDE2LCBhdCAxOjM1IFBNLCBBbGFuIEpvaG5zdG9uIDxhbGFuLmIuam9obnN0b25AZ21h
aWwuY29tPiB3cm90ZToNCj4gPg0KPiA+IEhpIE1hcmMsDQo+ID4NCj4gPiBDaGFuZ2luZyB0aGUg
cGFja2V0IGZvcm1hdCBmb3IgWlJUUCBpcyBhIHByZXR0eSBtYWpvciBjaGFuZ2UgdG8gdGhlIHBy
b3RvY29sLi4uDQo+ID4NCj4gPiBJIHRoaW5rIHRoZSBvbmx5IGNhc2Ugd2hlcmUgdGhpcyBpcyBh
biBpc3N1ZSB3b3VsZCBiZSBpZiBib3RoIFpSVFAgYW5kIERUTFMtU1JUUCBhcmUgb2ZmZXJlZCBv
cHBvcnR1bmlzdGljYWxseSAoT1NSVFApLCBhbmQgZWl0aGVyIFpSVFAgb3IgRFRMUy1TUlRQIGFy
cml2ZXMgYmVmb3JlIHRoZSBhbnN3ZXIgaXMgcmVjZWl2ZWQuICAgIER1cmluZyB0aGlzIHdpbmRv
dyBvZiB0aW1lLCBhIHNsaWdodGx5IG1vcmUgY29tcGxpY2F0ZWQgYWxnb3JpdGhtIGNvdWxkIGJl
IHVzZWQgdG8gZGlzdGluZ3Vpc2ggWlJUUCBmcm9tIERUTFMtU1JUUCwgc3VjaCBhcyBjaGVja2lu
ZyB0aGUgMzItYml0IG1hZ2ljIGNvb2tpZSB0aGF0IGlzIHByZXNlbnQgaW4gZXZlcnkgWlJUUCBt
ZXNzYWdlLiBPdGhlcndpc2UsIG9ubHkgb25lIG9mIHRoZXNlIHByb3RvY29scyB3aWxsIGJlIHVz
ZWQgYXQgYSB0aW1lLCBzbyBpdCBpcyBub3QgdGhlIHNhbWUgYXMgZGlzdGluZ3Vpc2hpbmcgZWl0
aGVyIGZyb20gU1RVTiBhbmQgUlRQLCB3aGljaCBoYXBwZW5zIHRocm91Z2hvdXQgYSBzZXNzaW9u
Lg0KPiA+DQo+ID4gV2UgY291bGQgcHV0IHRoaXMgZ3VpZGFuY2UgaW4gYSBSRkM2MTg5YmlzIGRy
YWZ0LCBhbmQgdGhlIG90aGVyIGRvY3VtZW50cyBjb3VsZCBqdXN0IGRlZmVyIHRvIHRoYXQgZ3Vp
ZGFuY2UgaWYgdGhleSBzdXBwb3J0IFpSVFAgaW4gYWRkaXRpb24gdG8gRFRMUy1TUlRQIG9wcG9y
dHVuaXN0aWNhbGx5Lg0KPiA+DQo+ID4gLSBBbGFuIC0NCj4gPg0KPiA+IE9uIFdlZCwgTWF5IDI1
LCAyMDE2IGF0IDEwOjU2IEFNLCBCZW4gQ2FtcGJlbGwgPGJlbkBub3N0cnVtLmNvbT4gd3JvdGU6
DQo+ID4gSGkgTWFyYywNCj4gPg0KPiA+IFRoYXQncyBhbG9uZyB0aGUgbGluZXMgdGhhdCBJIGV4
cGVjdGVkLCBpZiB0aGUgd29ya2luZyBncm91cCBjaG9vc2VzIHRoaXMgcGF0aC4gV2hhdCBkbyBv
dGhlcnMgdGhpbms/DQo+ID4NCj4gPiBUaGFua3MhDQo+ID4NCj4gPiBCZW4uDQo+ID4NCj4gPiBP
biAyNSBNYXkgMjAxNiwgYXQgMTI6MzcsIE1hcmMgUGV0aXQtSHVndWVuaW4gd3JvdGU6DQo+ID4N
Cj4gPiBBcyB5b3UgbWVudGlvbiwgdGhlcmUgYXJlIHNldmVyYWwgd2F5cyB0byBoYW5kbGUgdGhp
cyBpc3N1ZS4gV2UgbGVhdmUgaXQgdG8gdGhlIGNvbW11bml0eSB0byBkZWNpZGUgd2hldGhlciB0
byBpbmNsdWRlIHpydHAgaW4gYnVuZGxlIG9yIG5vdC4gSWYgd2Ugd2VyZSB0byB1cGRhdGUgdGhl
IDU3NjQtbXV4LWZpeCBkcmFmdCwgd2UgZmVsdCB0aGF0IHRoZSBjbGVhbmVzdCB3YXkgdG8gaGFu
ZGxlIGl0IGlzIGluIHR3byBzdGVwcy4NCj4gPg0KPiA+IE9uZSB0aGluZyB0byBub3RlIGlzIHRo
YXQgdGhlcmUgaXMgbm8gY2xhc2gvb3ZlcmxhcCB3aXRoIFNUVU4sIHNvIHVzaW5nIG1hZ2ljIGNv
b2tpZSB0byBkaXN0aW5ndWlzaCBmcm9tIFNUVU4gaXMgYSBtb290IHBvaW50LiBUaGUgb3Zlcmxh
cCB3aXRoIHRoZSBEVExTIHJhbmdlIGlzIHdoYXQgd2UgbmVlZCB0byBhdm9pZC4gVGhlIHJpZ2h0
IHRoaW5nIHRvIGRvIHNlZW1zIHRvIGJlIHRvIHdvcmsgb24gYSByZmM2MTg5YmlzIGRyYWZ0IHRo
YXQgd291bGQgc2V0IGJpdCA0IGFuZCA1IG9mIHRoZSBmaXJzdCBieXRlIG9mIHRoZSB6cnRwIG1l
c3NhZ2UgdG8gMC4gVGhpcyB3YXkgenJ0cCBjYW5ub3QgY2xhc2ggd2l0aCBEVExTLg0KPiA+DQo+
ID4gT24gdGhlIHJmYzU3NjQtbXV4LWZpeGVzIGRyYWZ0LCB3ZSBqdXN0IGNoYW5nZSB0aGUgYWxn
b3JpdGhtIHRvOg0KPiA+DQo+ID4gICAgICAgICAgICArLS0tLS0tLS0tLS0tLS0tLSsNCj4gPiAg
ICAgICAgICAgIHwgICAgICAgIFswLi4zXSAtKy0tPiBmb3J3YXJkIHRvIFNUVU4NCj4gPiAgICAg
ICAgICAgIHwgICAgICAgICAgICAgICAgfA0KPiA+ICAgICAgICAgICAgfCAgICAgIFsxNi4uMTld
IC0rLS0+IGZvcndhcmQgdG8gWlJUUA0KPiA+ICAgICAgICAgICAgfCAgICAgICAgICAgICAgICB8
DQo+ID4gcGFja2V0IC0tPiB8ICAgICAgWzIwLi42M10gLSstLT4gZm9yd2FyZCB0byBEVExTDQo+
ID4gICAgICAgICAgICB8ICAgICAgICAgICAgICAgIHwNCj4gPiAgICAgICAgICAgIHwgICAgICBb
NjQuLjc5XSAtKy0tPiBmb3J3YXJkIHRvIFRVUk4gQ2hhbm5lbA0KPiA+ICAgICAgICAgICAgfCAg
ICAgICAgICAgICAgICB8DQo+ID4gICAgICAgICAgICB8ICAgIFsxMjguLjE5MV0gLSstLT4gZm9y
d2FyZCB0byBSVFAvUlRDUA0KPiA+ICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0rDQo+ID4N
Cj4gPg0KPiA+IERvZXMgdGhpcyBzZWVtIGxpa2UgYSByZWFzb25hYmxlIGFwcHJvYWNoPw0KPiA+
DQo+ID4NCj4gPiBPbiAwNS8yNC8yMDE2IDA0OjIxIFBNLCBCZW4gQ2FtcGJlbGwgd3JvdGU6DQo+
ID4gSGksDQo+ID4NCj4gPiBUaGVyZSBhcHBlYXJzIHRvIGJlIGEgZGlzY3JlcGFuY3kgYmV0d2Vl
biBkcmFmdC1pZXRmLW1tdXNpYy1zZHAtbXV4LWF0dHJpYnV0ZXMgYW5kIGRyYWZ0LWlldGYtYXZ0
Y29yZS1yZmM1NzY0LW11eC1maXhlcyBjb25jZXJuaW5nIHdoZXRoZXIgenJ0cCBjYW4gYmUgdXNl
ZCB3aXRoIGJ1bmRsZS4NCj4gPg0KPiA+IG11eC1hdHRyaWJ1dGVzIHB1dHMgdGhlIHpydHAtaGFz
aCBhdHRyaWJ1dGUgW1JGQzYxODldIGluIHRoZSAidHJhbnNwb3J0IiBjYXRlZ29yeSwgbWVhbmlu
ZywgYW1vbmcgb3RoZXIgdGhpbmdzLCB0aGF0IGl0IGNhbiBiZSB1c2VkIGluIGEgYnVuZGxlIGdy
b3VwLiBIb3dldmVyLCBhcyB0aGUgZGVtdXggcnVsZXMgYXJlIGN1cnJlbnRseSBkZWZpbmVkIDU3
NjQtbXV4LWZpeGVzLCB6cnRwIG1lc3NhZ2VzIGNhbm5vdCBhY3R1YWxseSBiZSBkZW11eGVkLiAo
SWYgSSByZWFkIHRoaW5ncyBjb3JyZWN0bHksIHRoZSBmaXJzdCBieXRlIG9mIGEgenJ0cCBtZXNz
YWdlIHdpbGwgYmUgMTYsIHdoaWNoIGlzIG5vdCBpbiBhbnkgb2YgdGhlICJrbm93biByYW5nZXMi
IGRlc2NyaWJlZCBpbiA1NzY1IG9yIDU3NjQtbXV4LWZpeGVzLCBhbmQgdGhlcmVmb3JlIHRoZSBt
ZXNzYWdlIE1VU1QgYmUgZHJvcHBlZC4NCj4gPg0KPiA+IFRoYXQgc2VlbXMgdG8gbGVhdmUgdGhl
IGNob2ljZSBvZiBhZGRpbmcgenJ0cCBtZXNzYWdlcyB0byB0aGUgZGVtdXggcnVsZXMgaW4gNTc2
NC1tdXgtZml4ZXMsIG9yIHJlbW92aW5nIHRoZSBpbXBsaWNhdGlvbiB0aGF0IHpydHAgY2FuIGJl
IGJ1bmRsZWQgZnJvbSBtdXgtYXR0cmlidXRlcy4NCj4gPg0KPiA+IEFkZGluZyBydWxlcyBmb3Ig
ZGVtdXhpbmcgenJ0cCB0byA1NzY1LW11eC1maXhlcyB3b3VsZCBwcm9iYWJseSBub3QgYmUgaGFy
ZCwgYnV0IHdvdWxkIGJlIG5vbi10cml2aWFsLiBSRkMgNjE4OSBjYWxscyBmb3IgdXNpbmcgdGhl
IG1hZ2ljIGNvb2tpZSB0byBkaXN0aW5ndWlzaCB6cnRwIG1lc3NhZ2VzIGZyb20gc3R1biBtZXNz
YWdlcy4NCj4gPg0KPiA+IERvIHBlb3BsZSBoYXZlIG9waW5pb25zIGhvdyB0byBtb3ZlIGZvcndh
cmQgd2l0aCB0aGlzPyBBbSBJIGludGVycHJldGluZyB0aGUgY29uZmxpY3QgY29ycmVjdGx5P0tl
ZXAgaW4gbWluZCB0aGF0IFpSVFAgaXMgbm90IGEgc3RhbmRhcmRzLXRyYWNrIHNwZWMuIEJ1dCBh
dCB0aGUgc2FtZSB0aW1lLCBJJ20gbm90IHN1cmUgd2Ugd2FudCB0byBleGNsdWRlIGl0IGZyb20g
dGhlIGJ1bmRsZSBtZWNoYW5pc20uDQo+ID4NCj4gPiBUaGFua3MhDQo+ID4NCj4gPiBCZW4uDQo+
ID4NCj4gPg0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+ID4gQXVkaW8vVmlkZW8gVHJhbnNwb3J0IENvcmUgTWFpbnRlbmFuY2UNCj4gPiBhdnRA
aWV0Zi5vcmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dA0K
PiA+DQo+ID4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KPiA+IG1tdXNpYyBtYWlsaW5nIGxpc3QNCj4gPiBtbXVzaWNAaWV0Zi5vcmcNCj4gPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0KPiA+DQo+IA0KPiAN
Cg0K


From nobody Wed May 25 20:09:51 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 831A712D0F2; Wed, 25 May 2016 20:09:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0gg1kP7UtvU; Wed, 25 May 2016 20:09:46 -0700 (PDT)
Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9960C12D539; Wed, 25 May 2016 20:09:45 -0700 (PDT)
Received: by mail-yw0-x232.google.com with SMTP id x189so65007276ywe.3; Wed, 25 May 2016 20:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=tMAMBxMEP3BPhkFwAe9r6LAZCA+2eEJ6qvtUt8lQSVg=; b=YfNGeZroQKQSODzPC7HzL1U7x2g3l/6yw5GHdEHP4k/h1YQBmGCPlb3ciovQgEuEp8 05gBOniNciHli9Hej6Q+ZdMgXr82/zpG29KnzeKILvnRx+amvhrgigi7GaXJLg4v7eFD WHy1VHeMDYORStfqtZqT3JCMYLeF6rsqOYtplnJFXPudEbNG7bRW6TKnUFc8vPA7MweF iUK5L7/nGLKp+958CQ6B3BpSGAKqtNvEgczvzb0Ow475gbmLPw03k1exLKLVfGzdYNFI 4dfEv72vWHymC0Rsd9Hsil0OIi4nncml8cqfRf/tMa9o3ICpHgBclJmpwXn7V3wLyw5H mPbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=tMAMBxMEP3BPhkFwAe9r6LAZCA+2eEJ6qvtUt8lQSVg=; b=PUG8Bz8hta8h8XAeEGt9YiVmgDabeuXKDrdJp3jZEGTyBX/UthqmHwp2aW0lU+ZXJ0 D7iIMHNtkKlAafw83MYID+CJlJ6NZIIUkxtmbj6g80G+QZU8W8NC6n2nZmA+X1Z/Dqfp VYoQpDIw91cQWLcABlwVEdSar8wre/mpHrh/A8Y2TwI0XM5ud8jayJPisXNDXvkoiFAU CtklcQfxz5HnvjkYQ4jf4mp+XUPh0wzgWo3wJAvT4H+1Unh1kLFYuXCLh8iApDhnHoWx O0hxB4ygbe9uBbTlIoUfzzYt1Sp8s6U2ccCYfdDqIfNvg8GlW4+N+4clq2pMvCDK/UJb IGzA==
X-Gm-Message-State: ALyK8tIst19MXvHzY/Yub7n/IXOBUAPricfI+RXOD5CBuYY/1w3eu7qcJB4NOqc9/Iiyn8Hxn8t0pXGr9fKzVg==
MIME-Version: 1.0
X-Received: by 10.129.90.135 with SMTP id o129mr4927421ywb.20.1464232184753; Wed, 25 May 2016 20:09:44 -0700 (PDT)
Received: by 10.129.54.15 with HTTP; Wed, 25 May 2016 20:09:44 -0700 (PDT)
In-Reply-To: <CCF13C88-3C10-4E73-88A5-B70BA1C15A20@cisco.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com> <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com> <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com> <CCF13C88-3C10-4E73-88A5-B70BA1C15A20@cisco.com>
Date: Wed, 25 May 2016 20:09:44 -0700
Message-ID: <CAMRcRGTRkM8wksX8jHBwa1+kT_JSN9x=HtpV81+LcwdvsdcWNg@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Content-Type: multipart/alternative; boundary=001a114914f03db6920533b61f4f
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/eSSqDpeVrLavU_aAInxhDwcvfvU>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, Alan Johnston <alan.b.johnston@gmail.com>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 03:09:49 -0000

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

Thanks Ben, Alan , Gonzalo & Marc for driving these discussions.


Just getting back to the original question that Ben had on the mux-cateory
for ZRTP - Do we all agree that with the changes to rfc5764-mux-fixes the
category TRANSPORT makes sense ? Since that helps clarify demuxing ...

Thanks
Suhas

On Wed, May 25, 2016 at 8:05 PM, Gonzalo Salgueiro (gsalguei) <
gsalguei@cisco.com> wrote:

> OK, cool  Thanks, Alan.  Once we get consensus from the WG(s) that this i=
s
> the best way forward we will make this change to
> draft-ietf-avtcore-rfc5764-mux-fixes.
>
> Cheers,
>
> Gonzalo
>
> > On May 25, 2016, at 8:01 PM, Alan Johnston <alan.b.johnston@gmail.com>
> wrote:
> >
> > Hi Gonzalo,
> >
> > Thanks for the clarification - I had it backwards in my head.   Existin=
g
> ZRTP implementations will be compliant to the proposal, and we can
> constrain those bits to 0 in the 6189bis draft to lock it down.
> >
> > So I am OK with this proposal.
> >
> > - Alan -
> >
> > On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gsalguei) <
> gsalguei@cisco.com> wrote:
> > Hi Alan -
> >
> > One of the reasons we made the suggestion was because (in our
> estimation) it did not have a major impact to the ZRTP packet format.
> Currently the packet format is:
> >
> >
> >     0                   1                   2                   3
> >     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |0 0 0 1|Not Used (set to zero) |         Sequence Number       |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                 Magic Cookie 'ZRTP' (0x5a525450)              |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                        Source Identifier                      |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                                                               |
> >    |           ZRTP Message (length depends on Message Type)       |
> >    |                            . . .                              |
> >    |                                                               |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >    |                          CRC (1 word)                         |
> >    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >
> >
> > Our proposal was to set bits 4 and 5 to zero, which is currently what
> the protocol calls for and should implicitly make all existing
> implementations compliant.  All we are proposing is is to take bits 4 and=
 5
> out of the =E2=80=9CNot Used=E2=80=9D range and leave them fixed to the v=
alue that current
> implementations use.  Does this make sense?
> >
> > In any case, I=E2=80=99d like to try and understand what impact this ha=
s to the
> current rfc5764-mux-fix text.  Is it as simple as explicitly reserving
> values 16 - 19 for ZRTP? Or did you have something else in mind?  If you
> can make specific text suggestions that will simplify things.
> >
> > Thanks,
> >
> > Gonzalo
> >
> >
> >
> >
> >
> > > On May 25, 2016, at 1:35 PM, Alan Johnston <alan.b.johnston@gmail.com=
>
> wrote:
> > >
> > > Hi Marc,
> > >
> > > Changing the packet format for ZRTP is a pretty major change to the
> protocol...
> > >
> > > I think the only case where this is an issue would be if both ZRTP an=
d
> DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
> DTLS-SRTP arrives before the answer is received.    During this window of
> time, a slightly more complicated algorithm could be used to distinguish
> ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
> present in every ZRTP message. Otherwise, only one of these protocols wil=
l
> be used at a time, so it is not the same as distinguishing either from ST=
UN
> and RTP, which happens throughout a session.
> > >
> > > We could put this guidance in a RFC6189bis draft, and the other
> documents could just defer to that guidance if they support ZRTP in
> addition to DTLS-SRTP opportunistically.
> > >
> > > - Alan -
> > >
> > > On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com>
> wrote:
> > > Hi Marc,
> > >
> > > That's along the lines that I expected, if the working group chooses
> this path. What do others think?
> > >
> > > Thanks!
> > >
> > > Ben.
> > >
> > > On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
> > >
> > > As you mention, there are several ways to handle this issue. We leave
> it to the community to decide whether to include zrtp in bundle or not. I=
f
> we were to update the 5764-mux-fix draft, we felt that the cleanest way t=
o
> handle it is in two steps.
> > >
> > > One thing to note is that there is no clash/overlap with STUN, so
> using magic cookie to distinguish from STUN is a moot point. The overlap
> with the DTLS range is what we need to avoid. The right thing to do seems
> to be to work on a rfc6189bis draft that would set bit 4 and 5 of the fir=
st
> byte of the zrtp message to 0. This way zrtp cannot clash with DTLS.
> > >
> > > On the rfc5764-mux-fixes draft, we just change the algorithm to:
> > >
> > >            +----------------+
> > >            |        [0..3] -+--> forward to STUN
> > >            |                |
> > >            |      [16..19] -+--> forward to ZRTP
> > >            |                |
> > > packet --> |      [20..63] -+--> forward to DTLS
> > >            |                |
> > >            |      [64..79] -+--> forward to TURN Channel
> > >            |                |
> > >            |    [128..191] -+--> forward to RTP/RTCP
> > >            +----------------+
> > >
> > >
> > > Does this seem like a reasonable approach?
> > >
> > >
> > > On 05/24/2016 04:21 PM, Ben Campbell wrote:
> > > Hi,
> > >
> > > There appears to be a discrepancy between
> draft-ietf-mmusic-sdp-mux-attributes and
> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be used
> with bundle.
> > >
> > > mux-attributes puts the zrtp-hash attribute [RFC6189] in the
> "transport" category, meaning, among other things, that it can be used in=
 a
> bundle group. However, as the demux rules are currently defined
> 5764-mux-fixes, zrtp messages cannot actually be demuxed. (If I read thin=
gs
> correctly, the first byte of a zrtp message will be 16, which is not in a=
ny
> of the "known ranges" described in 5765 or 5764-mux-fixes, and therefore
> the message MUST be dropped.
> > >
> > > That seems to leave the choice of adding zrtp messages to the demux
> rules in 5764-mux-fixes, or removing the implication that zrtp can be
> bundled from mux-attributes.
> > >
> > > Adding rules for demuxing zrtp to 5765-mux-fixes would probably not b=
e
> hard, but would be non-trivial. RFC 6189 calls for using the magic cookie
> to distinguish zrtp messages from stun messages.
> > >
> > > Do people have opinions how to move forward with this? Am I
> interpreting the conflict correctly?Keep in mind that ZRTP is not a
> standards-track spec. But at the same time, I'm not sure we want to exclu=
de
> it from the bundle mechanism.
> > >
> > > Thanks!
> > >
> > > Ben.
> > >
> > >
> > > _______________________________________________
> > > Audio/Video Transport Core Maintenance
> > > avt@ietf.org
> > > https://www.ietf.org/mailman/listinfo/avt
> > >
> > >
> > > _______________________________________________
> > > 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
>

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

<div dir=3D"ltr"><div>Thanks Ben, Alan , Gonzalo &amp; Marc for driving the=
se discussions.</div><div><br></div><div><br></div>Just getting back to the=
 original question that Ben had on the mux-cateory for ZRTP - Do we all agr=
ee that with the changes to rfc5764-mux-fixes the category TRANSPORT makes =
sense ? Since that helps clarify demuxing ...<div><br></div><div>Thanks</di=
v><div>Suhas</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Wed, May 25, 2016 at 8:05 PM, Gonzalo Salgueiro (gsalguei) <span =
dir=3D"ltr">&lt;<a href=3D"mailto:gsalguei@cisco.com" target=3D"_blank">gsa=
lguei@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">OK,=
 cool=C2=A0 Thanks, Alan.=C2=A0 Once we get consensus from the WG(s) that t=
his is the best way forward we will make this change to draft-ietf-avtcore-=
rfc5764-mux-fixes.<br>
<br>
Cheers,<br>
<br>
Gonzalo<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On May 25, 2016, at 8:01 PM, Alan Johnston &lt;<a href=3D"mailto:alan.=
b.johnston@gmail.com">alan.b.johnston@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Gonzalo,<br>
&gt;<br>
&gt; Thanks for the clarification - I had it backwards in my head.=C2=A0 =
=C2=A0Existing ZRTP implementations will be compliant to the proposal, and =
we can constrain those bits to 0 in the 6189bis draft to lock it down.<br>
&gt;<br>
&gt; So I am OK with this proposal.<br>
&gt;<br>
&gt; - Alan -<br>
&gt;<br>
&gt; On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gsalguei) &lt;<a h=
ref=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; wrote:<br>
&gt; Hi Alan -<br>
&gt;<br>
&gt; One of the reasons we made the suggestion was because (in our estimati=
on) it did not have a major impact to the ZRTP packet format. Currently the=
 packet format is:<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A00=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A03<br>
&gt;=C2=A0 =C2=A0 =C2=A00 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5=
 6 7 8 9 0 1<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<br>
&gt;=C2=A0 =C2=A0 |0 0 0 1|Not Used (set to zero) |=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0Sequence Number=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0Magic Cookie &#39;ZRTP&#39; (0x5a525450)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Source Identifier=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ZRTP Message (l=
ength depends on Message Type)=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 . . .=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 |<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<br>
&gt;=C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 CRC (1 word)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;=C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<br>
&gt;<br>
&gt;<br>
&gt; Our proposal was to set bits 4 and 5 to zero, which is currently what =
the protocol calls for and should implicitly make all existing implementati=
ons compliant.=C2=A0 All we are proposing is is to take bits 4 and 5 out of=
 the =E2=80=9CNot Used=E2=80=9D range and leave them fixed to the value tha=
t current implementations use.=C2=A0 Does this make sense?<br>
&gt;<br>
&gt; In any case, I=E2=80=99d like to try and understand what impact this h=
as to the current rfc5764-mux-fix text.=C2=A0 Is it as simple as explicitly=
 reserving values 16 - 19 for ZRTP? Or did you have something else in mind?=
=C2=A0 If you can make specific text suggestions that will simplify things.=
<br>
&gt;<br>
&gt; Thanks,<br>
&gt;<br>
&gt; Gonzalo<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; On May 25, 2016, at 1:35 PM, Alan Johnston &lt;<a href=3D"mailto:=
alan.b.johnston@gmail.com">alan.b.johnston@gmail.com</a>&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; Hi Marc,<br>
&gt; &gt;<br>
&gt; &gt; Changing the packet format for ZRTP is a pretty major change to t=
he protocol...<br>
&gt; &gt;<br>
&gt; &gt; I think the only case where this is an issue would be if both ZRT=
P and DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or D=
TLS-SRTP arrives before the answer is received.=C2=A0 =C2=A0 During this wi=
ndow of time, a slightly more complicated algorithm could be used to distin=
guish ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is=
 present in every ZRTP message. Otherwise, only one of these protocols will=
 be used at a time, so it is not the same as distinguishing either from STU=
N and RTP, which happens throughout a session.<br>
&gt; &gt;<br>
&gt; &gt; We could put this guidance in a RFC6189bis draft, and the other d=
ocuments could just defer to that guidance if they support ZRTP in addition=
 to DTLS-SRTP opportunistically.<br>
&gt; &gt;<br>
&gt; &gt; - Alan -<br>
&gt; &gt;<br>
&gt; &gt; On Wed, May 25, 2016 at 10:56 AM, Ben Campbell &lt;<a href=3D"mai=
lto:ben@nostrum.com">ben@nostrum.com</a>&gt; wrote:<br>
&gt; &gt; Hi Marc,<br>
&gt; &gt;<br>
&gt; &gt; That&#39;s along the lines that I expected, if the working group =
chooses this path. What do others think?<br>
&gt; &gt;<br>
&gt; &gt; Thanks!<br>
&gt; &gt;<br>
&gt; &gt; Ben.<br>
&gt; &gt;<br>
&gt; &gt; On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:<br>
&gt; &gt;<br>
&gt; &gt; As you mention, there are several ways to handle this issue. We l=
eave it to the community to decide whether to include zrtp in bundle or not=
. If we were to update the 5764-mux-fix draft, we felt that the cleanest wa=
y to handle it is in two steps.<br>
&gt; &gt;<br>
&gt; &gt; One thing to note is that there is no clash/overlap with STUN, so=
 using magic cookie to distinguish from STUN is a moot point. The overlap w=
ith the DTLS range is what we need to avoid. The right thing to do seems to=
 be to work on a rfc6189bis draft that would set bit 4 and 5 of the first b=
yte of the zrtp message to 0. This way zrtp cannot clash with DTLS.<br>
&gt; &gt;<br>
&gt; &gt; On the rfc5764-mux-fixes draft, we just change the algorithm to:<=
br>
&gt; &gt;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +----------------+<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 [0..3] -+--&gt; forward to STUN<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 [1=
6..19] -+--&gt; forward to ZRTP<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; &gt; packet --&gt; |=C2=A0 =C2=A0 =C2=A0 [20..63] -+--&gt; forward to =
DTLS<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 [6=
4..79] -+--&gt; forward to TURN Channel<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 [128..191=
] -+--&gt; forward to RTP/RTCP<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 +----------------+<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Does this seem like a reasonable approach?<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 05/24/2016 04:21 PM, Ben Campbell wrote:<br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; There appears to be a discrepancy between draft-ietf-mmusic-sdp-m=
ux-attributes and draft-ietf-avtcore-rfc5764-mux-fixes concerning whether z=
rtp can be used with bundle.<br>
&gt; &gt;<br>
&gt; &gt; mux-attributes puts the zrtp-hash attribute [RFC6189] in the &quo=
t;transport&quot; category, meaning, among other things, that it can be use=
d in a bundle group. However, as the demux rules are currently defined 5764=
-mux-fixes, zrtp messages cannot actually be demuxed. (If I read things cor=
rectly, the first byte of a zrtp message will be 16, which is not in any of=
 the &quot;known ranges&quot; described in 5765 or 5764-mux-fixes, and ther=
efore the message MUST be dropped.<br>
&gt; &gt;<br>
&gt; &gt; That seems to leave the choice of adding zrtp messages to the dem=
ux rules in 5764-mux-fixes, or removing the implication that zrtp can be bu=
ndled from mux-attributes.<br>
&gt; &gt;<br>
&gt; &gt; Adding rules for demuxing zrtp to 5765-mux-fixes would probably n=
ot be hard, but would be non-trivial. RFC 6189 calls for using the magic co=
okie to distinguish zrtp messages from stun messages.<br>
&gt; &gt;<br>
&gt; &gt; Do people have opinions how to move forward with this? Am I inter=
preting the conflict correctly?Keep in mind that ZRTP is not a standards-tr=
ack spec. But at the same time, I&#39;m not sure we want to exclude it from=
 the bundle mechanism.<br>
&gt; &gt;<br>
&gt; &gt; Thanks!<br>
&gt; &gt;<br>
&gt; &gt; Ben.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; Audio/Video Transport Core Maintenance<br>
&gt; &gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"nore=
ferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; mmusic mailing list<br>
&gt; &gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"n=
oreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</=
a><br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</div></div></blockquote></div><br></div>

--001a114914f03db6920533b61f4f--


From nobody Wed May 25 20:50:25 2016
Return-Path: <ben@nostrum.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A33A212D093; Wed, 25 May 2016 20:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.326
X-Spam-Level: 
X-Spam-Status: No, score=-3.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426] 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 3AKUnRPkGXwh; Wed, 25 May 2016 20:50:22 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC2AE12D50B; Wed, 25 May 2016 20:50:21 -0700 (PDT)
Received: from [10.0.1.24] (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 u4Q3oFBt081452 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 25 May 2016 22:50:16 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.24]
From: "Ben Campbell" <ben@nostrum.com>
To: "Suhas Nandakumar" <suhasietf@gmail.com>
Date: Wed, 25 May 2016 22:50:15 -0500
Message-ID: <19E42A64-2DFD-4DAD-AD8D-C971EBD88C19@nostrum.com>
In-Reply-To: <CAMRcRGTRkM8wksX8jHBwa1+kT_JSN9x=HtpV81+LcwdvsdcWNg@mail.gmail.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com> <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com> <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com> <CCF13C88-3C10-4E73-88A5-B70BA1C15A20@cisco.com> <CAMRcRGTRkM8wksX8jHBwa1+kT_JSN9x=HtpV81+LcwdvsdcWNg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/LDcvLsg_aHLTa6UWvZtwzPiX4Mo>
Cc: mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, Alan Johnston <alan.b.johnston@gmail.com>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 03:50:24 -0000

Since I'm the one who originally complained about TRANSPORT I should 
probably respond :-)

I agree TRANSPORT makes sense if people agree to the changes in 
mux-fixes. Ben.

On 25 May 2016, at 22:09, Suhas Nandakumar wrote:

> Thanks Ben, Alan , Gonzalo & Marc for driving these discussions.
>
>
> Just getting back to the original question that Ben had on the 
> mux-cateory
> for ZRTP - Do we all agree that with the changes to rfc5764-mux-fixes 
> the
> category TRANSPORT makes sense ? Since that helps clarify demuxing ...
>
> Thanks
> Suhas
>
> On Wed, May 25, 2016 at 8:05 PM, Gonzalo Salgueiro (gsalguei) <
> gsalguei@cisco.com> wrote:
>
>> OK, cool  Thanks, Alan.  Once we get consensus from the WG(s) that 
>> this is
>> the best way forward we will make this change to
>> draft-ietf-avtcore-rfc5764-mux-fixes.
>>
>> Cheers,
>>
>> Gonzalo
>>
>>> On May 25, 2016, at 8:01 PM, Alan Johnston 
>>> <alan.b.johnston@gmail.com>
>> wrote:
>>>
>>> Hi Gonzalo,
>>>
>>> Thanks for the clarification - I had it backwards in my head.   
>>> Existing
>> ZRTP implementations will be compliant to the proposal, and we can
>> constrain those bits to 0 in the 6189bis draft to lock it down.
>>>
>>> So I am OK with this proposal.
>>>
>>> - Alan -
>>>
>>> On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gsalguei) <
>> gsalguei@cisco.com> wrote:
>>> Hi Alan -
>>>
>>> One of the reasons we made the suggestion was because (in our
>> estimation) it did not have a major impact to the ZRTP packet format.
>> Currently the packet format is:
>>>
>>>
>>>     0                   1                   2                   3
>>>     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>    |0 0 0 1|Not Used (set to zero) |         Sequence Number       |
>>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>    |                 Magic Cookie 'ZRTP' (0x5a525450)              |
>>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>    |                        Source Identifier                      |
>>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>    |                                                               |
>>>    |           ZRTP Message (length depends on Message Type)       |
>>>    |                            . . .                              |
>>>    |                                                               |
>>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>    |                          CRC (1 word)                         |
>>>    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>
>>>
>>> Our proposal was to set bits 4 and 5 to zero, which is currently 
>>> what
>> the protocol calls for and should implicitly make all existing
>> implementations compliant.  All we are proposing is is to take bits 4 
>> and 5
>> out of the â€œNot Usedâ€� range and leave them fixed to the value 
>> that current
>> implementations use.  Does this make sense?
>>>
>>> In any case, Iâ€™d like to try and understand what impact this has 
>>> to the
>> current rfc5764-mux-fix text.  Is it as simple as explicitly 
>> reserving
>> values 16 - 19 for ZRTP? Or did you have something else in mind?  If 
>> you
>> can make specific text suggestions that will simplify things.
>>>
>>> Thanks,
>>>
>>> Gonzalo
>>>
>>>
>>>
>>>
>>>
>>>> On May 25, 2016, at 1:35 PM, Alan Johnston 
>>>> <alan.b.johnston@gmail.com>
>> wrote:
>>>>
>>>> Hi Marc,
>>>>
>>>> Changing the packet format for ZRTP is a pretty major change to the
>> protocol...
>>>>
>>>> I think the only case where this is an issue would be if both ZRTP 
>>>> and
>> DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
>> DTLS-SRTP arrives before the answer is received.    During this 
>> window of
>> time, a slightly more complicated algorithm could be used to 
>> distinguish
>> ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
>> present in every ZRTP message. Otherwise, only one of these protocols 
>> will
>> be used at a time, so it is not the same as distinguishing either 
>> from STUN
>> and RTP, which happens throughout a session.
>>>>
>>>> We could put this guidance in a RFC6189bis draft, and the other
>> documents could just defer to that guidance if they support ZRTP in
>> addition to DTLS-SRTP opportunistically.
>>>>
>>>> - Alan -
>>>>
>>>> On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com>
>> wrote:
>>>> Hi Marc,
>>>>
>>>> That's along the lines that I expected, if the working group 
>>>> chooses
>> this path. What do others think?
>>>>
>>>> Thanks!
>>>>
>>>> Ben.
>>>>
>>>> On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
>>>>
>>>> As you mention, there are several ways to handle this issue. We 
>>>> leave
>> it to the community to decide whether to include zrtp in bundle or 
>> not. If
>> we were to update the 5764-mux-fix draft, we felt that the cleanest 
>> way to
>> handle it is in two steps.
>>>>
>>>> One thing to note is that there is no clash/overlap with STUN, so
>> using magic cookie to distinguish from STUN is a moot point. The 
>> overlap
>> with the DTLS range is what we need to avoid. The right thing to do 
>> seems
>> to be to work on a rfc6189bis draft that would set bit 4 and 5 of the 
>> first
>> byte of the zrtp message to 0. This way zrtp cannot clash with DTLS.
>>>>
>>>> On the rfc5764-mux-fixes draft, we just change the algorithm to:
>>>>
>>>>            +----------------+
>>>>            |        [0..3] -+--> forward to STUN
>>>>            |                |
>>>>            |      [16..19] -+--> forward to ZRTP
>>>>            |                |
>>>> packet --> |      [20..63] -+--> forward to DTLS
>>>>            |                |
>>>>            |      [64..79] -+--> forward to TURN Channel
>>>>            |                |
>>>>            |    [128..191] -+--> forward to RTP/RTCP
>>>>            +----------------+
>>>>
>>>>
>>>> Does this seem like a reasonable approach?
>>>>
>>>>
>>>> On 05/24/2016 04:21 PM, Ben Campbell wrote:
>>>> Hi,
>>>>
>>>> There appears to be a discrepancy between
>> draft-ietf-mmusic-sdp-mux-attributes and
>> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be 
>> used
>> with bundle.
>>>>
>>>> mux-attributes puts the zrtp-hash attribute [RFC6189] in the
>> "transport" category, meaning, among other things, that it can be 
>> used in a
>> bundle group. However, as the demux rules are currently defined
>> 5764-mux-fixes, zrtp messages cannot actually be demuxed. (If I read 
>> things
>> correctly, the first byte of a zrtp message will be 16, which is not 
>> in any
>> of the "known ranges" described in 5765 or 5764-mux-fixes, and 
>> therefore
>> the message MUST be dropped.
>>>>
>>>> That seems to leave the choice of adding zrtp messages to the demux
>> rules in 5764-mux-fixes, or removing the implication that zrtp can be
>> bundled from mux-attributes.
>>>>
>>>> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not 
>>>> be
>> hard, but would be non-trivial. RFC 6189 calls for using the magic 
>> cookie
>> to distinguish zrtp messages from stun messages.
>>>>
>>>> Do people have opinions how to move forward with this? Am I
>> interpreting the conflict correctly?Keep in mind that ZRTP is not a
>> standards-track spec. But at the same time, I'm not sure we want to 
>> exclude
>> it from the bundle mechanism.
>>>>
>>>> Thanks!
>>>>
>>>> Ben.
>>>>
>>>>
>>>> _______________________________________________
>>>> Audio/Video Transport Core Maintenance
>>>> avt@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>
>>>
>>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>


From nobody Wed May 25 20:59:37 2016
Return-Path: <gsalguei@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 56DDA12D0B6; Wed, 25 May 2016 20:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elc_xM8lYmbU; Wed, 25 May 2016 20:59:33 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0087B12D5D9; Wed, 25 May 2016 20:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8710; q=dns/txt; s=iport; t=1464235171; x=1465444771; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=jdPn8l4PeQSJW2D17BC0JDQ9CIMonzSXnfWwrrdxYKw=; b=Ln1DU+riy/l8JmBSPkLSSjs/8LN0WkLmUUbuVyTqeBuXeVoQo00J8nex Nl6HQvNbXsUV06jIoMbV7Loip1voZOb0fNHxh4+DxDbXbnJrKLSPm3KO8 T7M82VyVNj0TO9de+o3eKvrTYfxpmDSf5ql/dyCumGGwUv4rhOloebvDS M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ABAgBmc0ZX/5xdJa1cgzlWfa4Mi28BD?= =?us-ascii?q?YF4FwuFJUoCgTU4FAEBAQEBAQFlJ4RDAQEBAwEBAQEkRwsFCwIBCBgdBgshBgs?= =?us-ascii?q?lAgQOBRSIAQMPCA6+UA2ELQEBAQEBAQEBAQEBAQEBAQEBAQEBARcFhieBdgiCT?= =?us-ascii?q?oJDgU4RARyDLIIuBYgEkAAzAYwmgXmBaYd7hTiGM4Exh2cBHgEBQoIFARwWgTV?= =?us-ascii?q?uAYhfgTUBAQE?=
X-IronPort-AV: E=Sophos;i="5.26,366,1459814400"; d="scan'208";a="108311096"
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; 26 May 2016 03:59:29 +0000
Received: from XCH-RCD-006.cisco.com (xch-rcd-006.cisco.com [173.37.102.16]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u4Q3xTb0002231 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 26 May 2016 03:59:29 GMT
Received: from xch-aln-009.cisco.com (173.36.7.19) by XCH-RCD-006.cisco.com (173.37.102.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 25 May 2016 22:59:29 -0500
Received: from xch-aln-009.cisco.com ([173.36.7.19]) by XCH-ALN-009.cisco.com ([173.36.7.19]) with mapi id 15.00.1104.009; Wed, 25 May 2016 22:59:29 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Ben Campbell <ben@nostrum.com>
Thread-Topic: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
Thread-Index: AQHRthL8VuJ5x/fyEE6AYexF7eizHZ/KQAMAgAAFTwCAACwxAIAABhuAgABl14CAAAEuAIAAASMAgAALUoD//67CtA==
Date: Thu, 26 May 2016 03:59:29 +0000
Message-ID: <D760EEE0-2241-428A-89B7-1D8F985E2BBE@cisco.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com> <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com> <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com> <CCF13C88-3C10-4E73-88A5-B70BA1C15A20@cisco.com> <CAMRcRGTRkM8wksX8jHBwa1+kT_JSN9x=HtpV81+LcwdvsdcWNg@mail.gmail.com>, <19E42A64-2DFD-4DAD-AD8D-C971EBD88C19@nostrum.com>
In-Reply-To: <19E42A64-2DFD-4DAD-AD8D-C971EBD88C19@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/h5tyLv_MNNbEOyflfclBsnnJitg>
Cc: mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, Alan Johnston <alan.b.johnston@gmail.com>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 03:59:35 -0000

> On May 25, 2016, at 8:50 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Since I'm the one who originally complained about TRANSPORT I should prob=
ably respond :-)
>=20
> I agree TRANSPORT makes sense if people agree to the changes in mux-fixes=
.

Well, as mentioned in my earlier email, changes to both mux-fixes and 6189 =
are needed.=20

Gonzalo


> Ben.
>=20
>> On 25 May 2016, at 22:09, Suhas Nandakumar wrote:
>>=20
>> Thanks Ben, Alan , Gonzalo & Marc for driving these discussions.
>>=20
>>=20
>> Just getting back to the original question that Ben had on the mux-cateo=
ry
>> for ZRTP - Do we all agree that with the changes to rfc5764-mux-fixes th=
e
>> category TRANSPORT makes sense ? Since that helps clarify demuxing ...
>>=20
>> Thanks
>> Suhas
>>=20
>> On Wed, May 25, 2016 at 8:05 PM, Gonzalo Salgueiro (gsalguei) <
>> gsalguei@cisco.com> wrote:
>>=20
>>> OK, cool  Thanks, Alan.  Once we get consensus from the WG(s) that this=
 is
>>> the best way forward we will make this change to
>>> draft-ietf-avtcore-rfc5764-mux-fixes.
>>>=20
>>> Cheers,
>>>=20
>>> Gonzalo
>>>=20
>>>>> On May 25, 2016, at 8:01 PM, Alan Johnston <alan.b.johnston@gmail.com=
>
>>>> wrote:
>>>>=20
>>>> Hi Gonzalo,
>>>>=20
>>>> Thanks for the clarification - I had it backwards in my head.   Existi=
ng
>>> ZRTP implementations will be compliant to the proposal, and we can
>>> constrain those bits to 0 in the 6189bis draft to lock it down.
>>>>=20
>>>> So I am OK with this proposal.
>>>>=20
>>>> - Alan -
>>>>=20
>>>>> On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gsalguei) <
>>>> gsalguei@cisco.com> wrote:
>>>> Hi Alan -
>>>>=20
>>>> One of the reasons we made the suggestion was because (in our
>>> estimation) it did not have a major impact to the ZRTP packet format.
>>> Currently the packet format is:
>>>>=20
>>>>=20
>>>>    0                   1                   2                   3
>>>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>   |0 0 0 1|Not Used (set to zero) |         Sequence Number       |
>>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>   |                 Magic Cookie 'ZRTP' (0x5a525450)              |
>>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>   |                        Source Identifier                      |
>>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>   |                                                               |
>>>>   |           ZRTP Message (length depends on Message Type)       |
>>>>   |                            . . .                              |
>>>>   |                                                               |
>>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>   |                          CRC (1 word)                         |
>>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>>=20
>>>>=20
>>>> Our proposal was to set bits 4 and 5 to zero, which is currently what
>>> the protocol calls for and should implicitly make all existing
>>> implementations compliant.  All we are proposing is is to take bits 4 a=
nd 5
>>> out of the =93Not Used=94 range and leave them fixed to the value that =
current
>>> implementations use.  Does this make sense?
>>>>=20
>>>> In any case, I=92d like to try and understand what impact this has to =
the
>>> current rfc5764-mux-fix text.  Is it as simple as explicitly reserving
>>> values 16 - 19 for ZRTP? Or did you have something else in mind?  If yo=
u
>>> can make specific text suggestions that will simplify things.
>>>>=20
>>>> Thanks,
>>>>=20
>>>> Gonzalo
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>> On May 25, 2016, at 1:35 PM, Alan Johnston <alan.b.johnston@gmail.com=
>
>>> wrote:
>>>>>=20
>>>>> Hi Marc,
>>>>>=20
>>>>> Changing the packet format for ZRTP is a pretty major change to the
>>> protocol...
>>>>>=20
>>>>> I think the only case where this is an issue would be if both ZRTP an=
d
>>> DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
>>> DTLS-SRTP arrives before the answer is received.    During this window =
of
>>> time, a slightly more complicated algorithm could be used to distinguis=
h
>>> ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
>>> present in every ZRTP message. Otherwise, only one of these protocols w=
ill
>>> be used at a time, so it is not the same as distinguishing either from =
STUN
>>> and RTP, which happens throughout a session.
>>>>>=20
>>>>> We could put this guidance in a RFC6189bis draft, and the other
>>> documents could just defer to that guidance if they support ZRTP in
>>> addition to DTLS-SRTP opportunistically.
>>>>>=20
>>>>> - Alan -
>>>>>=20
>>>>> On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com>
>>> wrote:
>>>>> Hi Marc,
>>>>>=20
>>>>> That's along the lines that I expected, if the working group chooses
>>> this path. What do others think?
>>>>>=20
>>>>> Thanks!
>>>>>=20
>>>>> Ben.
>>>>>=20
>>>>> On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
>>>>>=20
>>>>> As you mention, there are several ways to handle this issue. We leave
>>> it to the community to decide whether to include zrtp in bundle or not.=
 If
>>> we were to update the 5764-mux-fix draft, we felt that the cleanest way=
 to
>>> handle it is in two steps.
>>>>>=20
>>>>> One thing to note is that there is no clash/overlap with STUN, so
>>> using magic cookie to distinguish from STUN is a moot point. The overla=
p
>>> with the DTLS range is what we need to avoid. The right thing to do see=
ms
>>> to be to work on a rfc6189bis draft that would set bit 4 and 5 of the f=
irst
>>> byte of the zrtp message to 0. This way zrtp cannot clash with DTLS.
>>>>>=20
>>>>> On the rfc5764-mux-fixes draft, we just change the algorithm to:
>>>>>=20
>>>>>           +----------------+
>>>>>           |        [0..3] -+--> forward to STUN
>>>>>           |                |
>>>>>           |      [16..19] -+--> forward to ZRTP
>>>>>           |                |
>>>>> packet --> |      [20..63] -+--> forward to DTLS
>>>>>           |                |
>>>>>           |      [64..79] -+--> forward to TURN Channel
>>>>>           |                |
>>>>>           |    [128..191] -+--> forward to RTP/RTCP
>>>>>           +----------------+
>>>>>=20
>>>>>=20
>>>>> Does this seem like a reasonable approach?
>>>>>=20
>>>>>=20
>>>>> On 05/24/2016 04:21 PM, Ben Campbell wrote:
>>>>> Hi,
>>>>>=20
>>>>> There appears to be a discrepancy between
>>> draft-ietf-mmusic-sdp-mux-attributes and
>>> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be use=
d
>>> with bundle.
>>>>>=20
>>>>> mux-attributes puts the zrtp-hash attribute [RFC6189] in the
>>> "transport" category, meaning, among other things, that it can be used =
in a
>>> bundle group. However, as the demux rules are currently defined
>>> 5764-mux-fixes, zrtp messages cannot actually be demuxed. (If I read th=
ings
>>> correctly, the first byte of a zrtp message will be 16, which is not in=
 any
>>> of the "known ranges" described in 5765 or 5764-mux-fixes, and therefor=
e
>>> the message MUST be dropped.
>>>>>=20
>>>>> That seems to leave the choice of adding zrtp messages to the demux
>>> rules in 5764-mux-fixes, or removing the implication that zrtp can be
>>> bundled from mux-attributes.
>>>>>=20
>>>>> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not b=
e
>>> hard, but would be non-trivial. RFC 6189 calls for using the magic cook=
ie
>>> to distinguish zrtp messages from stun messages.
>>>>>=20
>>>>> Do people have opinions how to move forward with this? Am I
>>> interpreting the conflict correctly?Keep in mind that ZRTP is not a
>>> standards-track spec. But at the same time, I'm not sure we want to exc=
lude
>>> it from the bundle mechanism.
>>>>>=20
>>>>> Thanks!
>>>>>=20
>>>>> Ben.
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> Audio/Video Transport Core Maintenance
>>>>> avt@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/avt
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> mmusic mailing list
>>>>> mmusic@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>=20


From nobody Wed May 25 21:02:08 2016
Return-Path: <alan.b.johnston@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 BCEF912D15C; Wed, 25 May 2016 21:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bu1HIbUo-qBf; Wed, 25 May 2016 21:02:02 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEC7612D0B6; Wed, 25 May 2016 21:02:01 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id h185so20653479qke.2; Wed, 25 May 2016 21:02:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=bDG5/UA4EqVabfIfGeb4LqVjWkBcOhNWRaBfs70hSxI=; b=l8JvcAxfCsAi7BwmPw2pGQmdnFI8EVMoFINn2ruAQoTvGcHSCyVVjxLjDiSvGM09S5 ZjFDXVQWkc/3TNmit/r0ELVFL921thd+1g62KNmnxX6UxFpdU90EV5aUAupHhEOHNdN2 lizmPwBdMYvm0g6JuyrLztP0UKDvdUV+xvMku49dgBnOzHKH6Hy+3G24YBbq8E/uYkt1 7EYBlmbtPcW+dBJr2pK1zmZ/3+2S8aO0yOE/FSBBAlsb9e7S5UiGgExJKOxiRbdY15Ed FOsscxMCD43ZEai+HBQUj+L3xOZFmI0Fnd7yxLxbBNOPgB5Y+LP57EfA4a//1gLu2Qo8 SPJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=bDG5/UA4EqVabfIfGeb4LqVjWkBcOhNWRaBfs70hSxI=; b=NzTHmMO4M8YgVYeGJPjSdUSXdiBRowtTpnwuraGUxllym1HwcF409Q8W+qR2edH9S+ 4yTXgIfnLSXxgQgOVryhJjAqZGZhBCOm+F+K/lFtZiAZiHxKGRZfrlYcPwnO0rRPEtPZ II1WuIkhoDOCjfxghWb2Dep7QEx7K5wVOVtlanVyavSp0yy7zourh7nyf2phVRBerPNP JceVpMvsBXA0vt956f1rShR0Iwrs5n6yyAJgx0PpAsTWuxZrV9Dh8hvY/Axv9kvWGujx 9cGlTQQNM6BYeZKhiS9oowLuWIouwKFFVnhA9tnpbXrxVepbNtZRGk/M4+C1coBKfKTw sElw==
X-Gm-Message-State: ALyK8tKv1fw71Vo1wVEuL+m2hjwpvJs192fUCHe612Z6cGuQQDwOurvLCyksvy9PxUSGaxWbBQ1V3AnfGX1hEg==
MIME-Version: 1.0
X-Received: by 10.55.161.1 with SMTP id k1mr7321073qke.193.1464235320557; Wed, 25 May 2016 21:02:00 -0700 (PDT)
Received: by 10.55.185.70 with HTTP; Wed, 25 May 2016 21:02:00 -0700 (PDT)
In-Reply-To: <D760EEE0-2241-428A-89B7-1D8F985E2BBE@cisco.com>
References: <CD90C355-FAFD-44F9-8CB0-E40045E31046@nostrum.com> <5745E2F4.8040206@petit-huguenin.org> <9759123A-B014-41AC-95B8-720C50BC9E57@nostrum.com> <CAKhHsXG96C141ujTNtKP8D1QEHB2seYnCR67mRYzSqac5fijJg@mail.gmail.com> <80563BED-ADDE-4C2B-8B4E-DF1C8F3E3FA5@cisco.com> <CAKhHsXGDneqTTaZ0tkw3WxsCPStLuMWGBSDHnarc+4YA-t-tyA@mail.gmail.com> <CCF13C88-3C10-4E73-88A5-B70BA1C15A20@cisco.com> <CAMRcRGTRkM8wksX8jHBwa1+kT_JSN9x=HtpV81+LcwdvsdcWNg@mail.gmail.com> <19E42A64-2DFD-4DAD-AD8D-C971EBD88C19@nostrum.com> <D760EEE0-2241-428A-89B7-1D8F985E2BBE@cisco.com>
Date: Wed, 25 May 2016 21:02:00 -0700
Message-ID: <CAKhHsXEy=QAJb_hvsy5mkxwiH+ph5ryJNVwenLZ0VMf54SyRyg@mail.gmail.com>
From: Alan Johnston <alan.b.johnston@gmail.com>
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Content-Type: multipart/alternative; boundary=94eb2c05fa182648a40533b6da05
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/hOGHfnbqsRItkLF359gRld9WnjU>
Cc: Ben Campbell <ben@nostrum.com>, mmusic WG <mmusic@ietf.org>, Marc Petit-Huguenin <marc@petit-huguenin.org>, "avt@ietf.org WG" <avt@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes.all@ietf.org>, "draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org" <draft-ietf-avtcore-rfc5764-mux-fixes.all@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] zrtp: draft-ietf-mmusic-sdp-mux-attributes vs draft-ietf-avtcore-rfc5764-mux-fixes
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 04:02:05 -0000

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

On Wed, May 25, 2016 at 8:59 PM, Gonzalo Salgueiro (gsalguei) <
gsalguei@cisco.com> wrote:

>
>
> > On May 25, 2016, at 8:50 PM, Ben Campbell <ben@nostrum.com> wrote:
> >
> > Since I'm the one who originally complained about TRANSPORT I should
> probably respond :-)
> >
> > I agree TRANSPORT makes sense if people agree to the changes in
> mux-fixes.
>
> Well, as mentioned in my earlier email, changes to both mux-fixes and 618=
9
> are needed.
>

Agreed.  I will make the changes to RFC 6189.

- Alan -


>
> Gonzalo
>
>
> > Ben.
> >
> >> On 25 May 2016, at 22:09, Suhas Nandakumar wrote:
> >>
> >> Thanks Ben, Alan , Gonzalo & Marc for driving these discussions.
> >>
> >>
> >> Just getting back to the original question that Ben had on the
> mux-cateory
> >> for ZRTP - Do we all agree that with the changes to rfc5764-mux-fixes
> the
> >> category TRANSPORT makes sense ? Since that helps clarify demuxing ...
> >>
> >> Thanks
> >> Suhas
> >>
> >> On Wed, May 25, 2016 at 8:05 PM, Gonzalo Salgueiro (gsalguei) <
> >> gsalguei@cisco.com> wrote:
> >>
> >>> OK, cool  Thanks, Alan.  Once we get consensus from the WG(s) that
> this is
> >>> the best way forward we will make this change to
> >>> draft-ietf-avtcore-rfc5764-mux-fixes.
> >>>
> >>> Cheers,
> >>>
> >>> Gonzalo
> >>>
> >>>>> On May 25, 2016, at 8:01 PM, Alan Johnston <
> alan.b.johnston@gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi Gonzalo,
> >>>>
> >>>> Thanks for the clarification - I had it backwards in my head.
>  Existing
> >>> ZRTP implementations will be compliant to the proposal, and we can
> >>> constrain those bits to 0 in the 6189bis draft to lock it down.
> >>>>
> >>>> So I am OK with this proposal.
> >>>>
> >>>> - Alan -
> >>>>
> >>>>> On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gsalguei) <
> >>>> gsalguei@cisco.com> wrote:
> >>>> Hi Alan -
> >>>>
> >>>> One of the reasons we made the suggestion was because (in our
> >>> estimation) it did not have a major impact to the ZRTP packet format.
> >>> Currently the packet format is:
> >>>>
> >>>>
> >>>>    0                   1                   2                   3
> >>>>    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
> >>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>   |0 0 0 1|Not Used (set to zero) |         Sequence Number       |
> >>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>   |                 Magic Cookie 'ZRTP' (0x5a525450)              |
> >>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>   |                        Source Identifier                      |
> >>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>   |                                                               |
> >>>>   |           ZRTP Message (length depends on Message Type)       |
> >>>>   |                            . . .                              |
> >>>>   |                                                               |
> >>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>   |                          CRC (1 word)                         |
> >>>>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> >>>>
> >>>>
> >>>> Our proposal was to set bits 4 and 5 to zero, which is currently wha=
t
> >>> the protocol calls for and should implicitly make all existing
> >>> implementations compliant.  All we are proposing is is to take bits 4
> and 5
> >>> out of the =E2=80=9CNot Used=E2=80=9D range and leave them fixed to t=
he value that
> current
> >>> implementations use.  Does this make sense?
> >>>>
> >>>> In any case, I=E2=80=99d like to try and understand what impact this=
 has to
> the
> >>> current rfc5764-mux-fix text.  Is it as simple as explicitly reservin=
g
> >>> values 16 - 19 for ZRTP? Or did you have something else in mind?  If
> you
> >>> can make specific text suggestions that will simplify things.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Gonzalo
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>> On May 25, 2016, at 1:35 PM, Alan Johnston <
> alan.b.johnston@gmail.com>
> >>> wrote:
> >>>>>
> >>>>> Hi Marc,
> >>>>>
> >>>>> Changing the packet format for ZRTP is a pretty major change to the
> >>> protocol...
> >>>>>
> >>>>> I think the only case where this is an issue would be if both ZRTP
> and
> >>> DTLS-SRTP are offered opportunistically (OSRTP), and either ZRTP or
> >>> DTLS-SRTP arrives before the answer is received.    During this windo=
w
> of
> >>> time, a slightly more complicated algorithm could be used to
> distinguish
> >>> ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie that is
> >>> present in every ZRTP message. Otherwise, only one of these protocols
> will
> >>> be used at a time, so it is not the same as distinguishing either fro=
m
> STUN
> >>> and RTP, which happens throughout a session.
> >>>>>
> >>>>> We could put this guidance in a RFC6189bis draft, and the other
> >>> documents could just defer to that guidance if they support ZRTP in
> >>> addition to DTLS-SRTP opportunistically.
> >>>>>
> >>>>> - Alan -
> >>>>>
> >>>>> On Wed, May 25, 2016 at 10:56 AM, Ben Campbell <ben@nostrum.com>
> >>> wrote:
> >>>>> Hi Marc,
> >>>>>
> >>>>> That's along the lines that I expected, if the working group choose=
s
> >>> this path. What do others think?
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> Ben.
> >>>>>
> >>>>> On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:
> >>>>>
> >>>>> As you mention, there are several ways to handle this issue. We lea=
ve
> >>> it to the community to decide whether to include zrtp in bundle or
> not. If
> >>> we were to update the 5764-mux-fix draft, we felt that the cleanest
> way to
> >>> handle it is in two steps.
> >>>>>
> >>>>> One thing to note is that there is no clash/overlap with STUN, so
> >>> using magic cookie to distinguish from STUN is a moot point. The
> overlap
> >>> with the DTLS range is what we need to avoid. The right thing to do
> seems
> >>> to be to work on a rfc6189bis draft that would set bit 4 and 5 of the
> first
> >>> byte of the zrtp message to 0. This way zrtp cannot clash with DTLS.
> >>>>>
> >>>>> On the rfc5764-mux-fixes draft, we just change the algorithm to:
> >>>>>
> >>>>>           +----------------+
> >>>>>           |        [0..3] -+--> forward to STUN
> >>>>>           |                |
> >>>>>           |      [16..19] -+--> forward to ZRTP
> >>>>>           |                |
> >>>>> packet --> |      [20..63] -+--> forward to DTLS
> >>>>>           |                |
> >>>>>           |      [64..79] -+--> forward to TURN Channel
> >>>>>           |                |
> >>>>>           |    [128..191] -+--> forward to RTP/RTCP
> >>>>>           +----------------+
> >>>>>
> >>>>>
> >>>>> Does this seem like a reasonable approach?
> >>>>>
> >>>>>
> >>>>> On 05/24/2016 04:21 PM, Ben Campbell wrote:
> >>>>> Hi,
> >>>>>
> >>>>> There appears to be a discrepancy between
> >>> draft-ietf-mmusic-sdp-mux-attributes and
> >>> draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp can be
> used
> >>> with bundle.
> >>>>>
> >>>>> mux-attributes puts the zrtp-hash attribute [RFC6189] in the
> >>> "transport" category, meaning, among other things, that it can be use=
d
> in a
> >>> bundle group. However, as the demux rules are currently defined
> >>> 5764-mux-fixes, zrtp messages cannot actually be demuxed. (If I read
> things
> >>> correctly, the first byte of a zrtp message will be 16, which is not
> in any
> >>> of the "known ranges" described in 5765 or 5764-mux-fixes, and
> therefore
> >>> the message MUST be dropped.
> >>>>>
> >>>>> That seems to leave the choice of adding zrtp messages to the demux
> >>> rules in 5764-mux-fixes, or removing the implication that zrtp can be
> >>> bundled from mux-attributes.
> >>>>>
> >>>>> Adding rules for demuxing zrtp to 5765-mux-fixes would probably not
> be
> >>> hard, but would be non-trivial. RFC 6189 calls for using the magic
> cookie
> >>> to distinguish zrtp messages from stun messages.
> >>>>>
> >>>>> Do people have opinions how to move forward with this? Am I
> >>> interpreting the conflict correctly?Keep in mind that ZRTP is not a
> >>> standards-track spec. But at the same time, I'm not sure we want to
> exclude
> >>> it from the bundle mechanism.
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> Ben.
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Audio/Video Transport Core Maintenance
> >>>>> avt@ietf.org
> >>>>> https://www.ietf.org/mailman/listinfo/avt
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> 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
> >>>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, May 25, 2016 at 8:59 PM, Gonzalo Salgueiro (gsalguei) <span dir=
=3D"ltr">&lt;<a href=3D"mailto:gsalguei@cisco.com" target=3D"_blank">gsalgu=
ei@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
&gt; On May 25, 2016, at 8:50 PM, Ben Campbell &lt;<a href=3D"mailto:ben@no=
strum.com">ben@nostrum.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Since I&#39;m the one who originally complained about TRANSPORT I shou=
ld probably respond :-)<br>
&gt;<br>
&gt; I agree TRANSPORT makes sense if people agree to the changes in mux-fi=
xes.<br>
<br>
Well, as mentioned in my earlier email, changes to both mux-fixes and 6189 =
are needed.<br></blockquote><div><br></div><div>Agreed.=C2=A0 I will make t=
he changes to RFC 6189.</div><div><br></div><div>- Alan -</div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
<br>
Gonzalo<br>
<br>
<br>
&gt; Ben.<br>
&gt;<br>
&gt;&gt; On 25 May 2016, at 22:09, Suhas Nandakumar wrote:<br>
&gt;&gt;<br>
&gt;&gt; Thanks Ben, Alan , Gonzalo &amp; Marc for driving these discussion=
s.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Just getting back to the original question that Ben had on the mux=
-cateory<br>
&gt;&gt; for ZRTP - Do we all agree that with the changes to rfc5764-mux-fi=
xes the<br>
&gt;&gt; category TRANSPORT makes sense ? Since that helps clarify demuxing=
 ...<br>
&gt;&gt;<br>
&gt;&gt; Thanks<br>
&gt;&gt; Suhas<br>
&gt;&gt;<br>
&gt;&gt; On Wed, May 25, 2016 at 8:05 PM, Gonzalo Salgueiro (gsalguei) &lt;=
<br>
&gt;&gt; <a href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</a>&gt; w=
rote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; OK, cool=C2=A0 Thanks, Alan.=C2=A0 Once we get consensus from =
the WG(s) that this is<br>
&gt;&gt;&gt; the best way forward we will make this change to<br>
&gt;&gt;&gt; draft-ietf-avtcore-rfc5764-mux-fixes.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Cheers,<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Gonzalo<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On May 25, 2016, at 8:01 PM, Alan Johnston &lt;<a href=
=3D"mailto:alan.b.johnston@gmail.com">alan.b.johnston@gmail.com</a>&gt;<br>
&gt;&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Hi Gonzalo,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks for the clarification - I had it backwards in my he=
ad.=C2=A0 =C2=A0Existing<br>
&gt;&gt;&gt; ZRTP implementations will be compliant to the proposal, and we=
 can<br>
&gt;&gt;&gt; constrain those bits to 0 in the 6189bis draft to lock it down=
.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; So I am OK with this proposal.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - Alan -<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On Wed, May 25, 2016 at 1:56 PM, Gonzalo Salgueiro (gs=
alguei) &lt;<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:gsalguei@cisco.com">gsalguei@cisco.com</=
a>&gt; wrote:<br>
&gt;&gt;&gt;&gt; Hi Alan -<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; One of the reasons we made the suggestion was because (in =
our<br>
&gt;&gt;&gt; estimation) it did not have a major impact to the ZRTP packet =
format.<br>
&gt;&gt;&gt; Currently the packet format is:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A03<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2=
 3 4 5 6 7 8 9 0 1<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|0 0 0 1|Not Used (set to zero) |=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0Sequence Number=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0Magic Cookie &#39;ZRTP&#39; (0x5a525450)=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Source Identifier=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ZRTP=
 Message (length depends on Message Type)=C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 . . .=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 CRC (1 word)=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|<=
br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+-+-+-+-+-+-+<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Our proposal was to set bits 4 and 5 to zero, which is cur=
rently what<br>
&gt;&gt;&gt; the protocol calls for and should implicitly make all existing=
<br>
&gt;&gt;&gt; implementations compliant.=C2=A0 All we are proposing is is to=
 take bits 4 and 5<br>
&gt;&gt;&gt; out of the =E2=80=9CNot Used=E2=80=9D range and leave them fix=
ed to the value that current<br>
&gt;&gt;&gt; implementations use.=C2=A0 Does this make sense?<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In any case, I=E2=80=99d like to try and understand what i=
mpact this has to the<br>
&gt;&gt;&gt; current rfc5764-mux-fix text.=C2=A0 Is it as simple as explici=
tly reserving<br>
&gt;&gt;&gt; values 16 - 19 for ZRTP? Or did you have something else in min=
d?=C2=A0 If you<br>
&gt;&gt;&gt; can make specific text suggestions that will simplify things.<=
br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Gonzalo<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On May 25, 2016, at 1:35 PM, Alan Johnston &lt;<a href=
=3D"mailto:alan.b.johnston@gmail.com">alan.b.johnston@gmail.com</a>&gt;<br>
&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Hi Marc,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Changing the packet format for ZRTP is a pretty major =
change to the<br>
&gt;&gt;&gt; protocol...<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I think the only case where this is an issue would be =
if both ZRTP and<br>
&gt;&gt;&gt; DTLS-SRTP are offered opportunistically (OSRTP), and either ZR=
TP or<br>
&gt;&gt;&gt; DTLS-SRTP arrives before the answer is received.=C2=A0 =C2=A0 =
During this window of<br>
&gt;&gt;&gt; time, a slightly more complicated algorithm could be used to d=
istinguish<br>
&gt;&gt;&gt; ZRTP from DTLS-SRTP, such as checking the 32-bit magic cookie =
that is<br>
&gt;&gt;&gt; present in every ZRTP message. Otherwise, only one of these pr=
otocols will<br>
&gt;&gt;&gt; be used at a time, so it is not the same as distinguishing eit=
her from STUN<br>
&gt;&gt;&gt; and RTP, which happens throughout a session.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; We could put this guidance in a RFC6189bis draft, and =
the other<br>
&gt;&gt;&gt; documents could just defer to that guidance if they support ZR=
TP in<br>
&gt;&gt;&gt; addition to DTLS-SRTP opportunistically.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; - Alan -<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On Wed, May 25, 2016 at 10:56 AM, Ben Campbell &lt;<a =
href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt;<br>
&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt; Hi Marc,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; That&#39;s along the lines that I expected, if the wor=
king group chooses<br>
&gt;&gt;&gt; this path. What do others think?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Thanks!<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Ben.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 25 May 2016, at 12:37, Marc Petit-Huguenin wrote:<b=
r>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; As you mention, there are several ways to handle this =
issue. We leave<br>
&gt;&gt;&gt; it to the community to decide whether to include zrtp in bundl=
e or not. If<br>
&gt;&gt;&gt; we were to update the 5764-mux-fix draft, we felt that the cle=
anest way to<br>
&gt;&gt;&gt; handle it is in two steps.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; One thing to note is that there is no clash/overlap wi=
th STUN, so<br>
&gt;&gt;&gt; using magic cookie to distinguish from STUN is a moot point. T=
he overlap<br>
&gt;&gt;&gt; with the DTLS range is what we need to avoid. The right thing =
to do seems<br>
&gt;&gt;&gt; to be to work on a rfc6189bis draft that would set bit 4 and 5=
 of the first<br>
&gt;&gt;&gt; byte of the zrtp message to 0. This way zrtp cannot clash with=
 DTLS.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On the rfc5764-mux-fixes draft, we just change the alg=
orithm to:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+-------------=
---+<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 [0..3] -+--&gt; forward to STUN<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 [16..19] -+--&gt; forward to ZRTP<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;&gt; packet --&gt; |=C2=A0 =C2=A0 =C2=A0 [20..63] -+--&gt; =
forward to DTLS<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 [64..79] -+--&gt; forward to TURN Channel<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0=
 [128..191] -+--&gt; forward to RTP/RTCP<br>
&gt;&gt;&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+-------------=
---+<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Does this seem like a reasonable approach?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On 05/24/2016 04:21 PM, Ben Campbell wrote:<br>
&gt;&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; There appears to be a discrepancy between<br>
&gt;&gt;&gt; draft-ietf-mmusic-sdp-mux-attributes and<br>
&gt;&gt;&gt; draft-ietf-avtcore-rfc5764-mux-fixes concerning whether zrtp c=
an be used<br>
&gt;&gt;&gt; with bundle.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; mux-attributes puts the zrtp-hash attribute [RFC6189] =
in the<br>
&gt;&gt;&gt; &quot;transport&quot; category, meaning, among other things, t=
hat it can be used in a<br>
&gt;&gt;&gt; bundle group. However, as the demux rules are currently define=
d<br>
&gt;&gt;&gt; 5764-mux-fixes, zrtp messages cannot actually be demuxed. (If =
I read things<br>
&gt;&gt;&gt; correctly, the first byte of a zrtp message will be 16, which =
is not in any<br>
&gt;&gt;&gt; of the &quot;known ranges&quot; described in 5765 or 5764-mux-=
fixes, and therefore<br>
&gt;&gt;&gt; the message MUST be dropped.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; That seems to leave the choice of adding zrtp messages=
 to the demux<br>
&gt;&gt;&gt; rules in 5764-mux-fixes, or removing the implication that zrtp=
 can be<br>
&gt;&gt;&gt; bundled from mux-attributes.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Adding rules for demuxing zrtp to 5765-mux-fixes would=
 probably not be<br>
&gt;&gt;&gt; hard, but would be non-trivial. RFC 6189 calls for using the m=
agic cookie<br>
&gt;&gt;&gt; to distinguish zrtp messages from stun messages.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Do people have opinions how to move forward with this?=
 Am I<br>
&gt;&gt;&gt; interpreting the conflict correctly?Keep in mind that ZRTP is =
not a<br>
&gt;&gt;&gt; standards-track spec. But at the same time, I&#39;m not sure w=
e want to exclude<br>
&gt;&gt;&gt; it from the bundle mechanism.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Thanks!<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Ben.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt;&gt; Audio/Video Transport Core Maintenance<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/avt" =
rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/=
avt</a><br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>=
<br>
&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusi=
c" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listin=
fo/mmusic</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; mmusic mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmu=
sic</a><br>
&gt;&gt;&gt;<br>
</blockquote></div><br></div></div>

--94eb2c05fa182648a40533b6da05--


From nobody Thu May 26 02:42:01 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A880D12D527 for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 02:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CU7tBYVxebV for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 02:41:58 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C4EF12D151 for <mmusic@ietf.org>; Thu, 26 May 2016 02:41:57 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-e2-5746c4e3622f
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 56.B6.12926.3E4C6475; Thu, 26 May 2016 11:41:55 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0294.000; Thu, 26 May 2016 11:41:55 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "Roman Shpount" <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKA
Date: Thu, 26 May 2016 09:41:54 +0000
Message-ID: <D36CA01E.93ED%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com>
In-Reply-To: <D36B255A.90C8%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C845A0615EEC0B4B90D2A1E4AA425E3D@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHIsWRmVeSWpSXmKPExsUyM2K7ge7jI27hBmfnWlpcO/OP0WLq8scs Fis2HGC1mHFhKrMDi8ff9x+YPHbOusvusWTJTyaPW1MKAliiuGxSUnMyy1KL9O0SuDKOTXnN WHBIruLS613MDYx3ZLsYOTkkBEwkVr/fxQJhi0lcuLeerYuRi0NI4AijRO//z8wQzhJGiV+L PgNlODjYBCwkuv9pg8RFBDYwSlxouc8MEmcWUJe4ujgIZJCwgL3E1cuXmUBsEQEHiZ1vr7JA 1DcxSnw+3wqWYBFQlbiy8DUriM0rYCVx7PolVohlS9kkGt90s4MkOAWsJSauaGQGsRmBzvt+ ag1YM7OAuMStJ/OZIM4WkFiy5zwzhC0q8fLxP7ChogJ6EvtenGcEOU5CQEli2tY0iDs1Jdbv 0oeYYi1xZf9SFghbUWJK90N2iHMEJU7OfMIygVFiFpJlsxC6ZyHpnoWkexaS7gWMrKsYRYtT i5Ny042M9VKLMpOLi/Pz9PJSSzYxAmP14JbfqjsYL79xPMQowMGoxMOboOAWLsSaWFZcmXuI UYKDWUmEt+IQUIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv/0vFcCGB9MSS1OzU1ILUIpgsEwen VANj3LrGy4E//+UYC7wTVgxR1Y6KyPXTeP3sfmllbfIa2Txfi9Ils58fOWvzp2H3wi3RNYz8 jR2Ne9szJqrE/NPj57L4eLBb+3hWrtk15t9FXDMkFOoXqfCZ9hZvmRk9r2WRTNqH/4Y9DYqt TpklylURdee3RRxh5eXvN1dlzXqktu7E86MME5VYijMSDbWYi4oTAcgAyGjRAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/6XB_kFy6S7jm1dHBU-1ElIZFEBE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 09:42:00 -0000

QXJlIHBlb3BsZSBvayB3aXRoIHRoaXM/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCk9uIDI1
LzA1LzE2IDEwOjExLCAibW11c2ljIG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyINCjxt
bXVzaWMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgY2hyaXN0ZXIuaG9sbWJlcmdAZXJp
Y3Nzb24uY29tPg0Kd3JvdGU6DQoNCj5IaSwNCj4NCj5JbiBhZGRpdGlvbiB0byB0aGUgdGV4dCBj
aGFuZ2Ugc3VnZ2VzdGVkIGJ5IE1hcnRpbiwgScK5dmUgYWxzbyBpZGVudGlmaWVkDQo+dGhlIGZv
bGxvd2luZyBjaGFuZ2VzIGJ5IG1hbmRhdGluZyBTSEEtMjU2Lg0KPg0KPi0tLS0tDQo+DQo+QWJz
dHJhY3QgJiBJbnRyb2R1Y3Rpb246DQo+DQo+T0xEOg0KPg0KPiJUaGUgZG9jdW1lbnQgYWxzbyB1
cGRhdGVzIHRoZSBwcmVmZXJyZWQgY2lwaGVyIHN1aXRlIHRvIGJlIHVzZWQsLi4uIg0KPg0KPg0K
Pk5FVzoNCj4NCj7Cs1RoZSBkb2N1bWVudCBhbHNvIHJlcGxhY2VzIHRoZSBwcmVmZXJyZWQgY2lw
aGVyIHN1aXRlIHdpdGggYSBtYW5kYXRlIHRvDQo+c3VwcG9ydCBhIHN0cm9uZ2VyIGNpcGhlciBz
dWl0ZSzFoMKyDQo+DQo+LS0tLS0NCj4NCj5TZWN0aW9uIDU6DQo+DQo+VGhlIGNoYW5nZXMgdG8g
dGhlIGN1cnJlbnRseSBzdWdnZXN0ZWQgbmV3IHRleHQgYmV0d2VlbiA8bmV3PiBhbmQgPC9uZXc+
Lg0KPg0KPg0KPiBORVcgVEVYVDoNCj4NCj4gICAgIE11bHRpcGxlIFNEUCBmaW5nZXJwcmludCBh
dHRyaWJ1dGVzIGNhbiBiZSBhc3NvY2lhdGVkIHdpdGggYW4gbS0NCj4gICAgIGxpbmUuIFRoaXMg
Y2FuIG9jY3VyIGlmIG11bHRpcGxlIGZpbmdlcnByaW50cyBoYXZlIGJlZW4gY2FsY3VsYXRlZA0K
PiAgICAgZm9yIGEgY2VydGlmaWNhdGUgdXNpbmcgZGlmZmVyZW50IGhhc2ggZnVuY3Rpb25zLiBJ
dCBjYW4gYWxzbw0KPiAgICAgb2NjdXIgaWYgb25lIG9yIG1vcmUgZmluZ2VycHJpbnRzIGFzc29j
aWF0ZWQgd2l0aCBtdWx0aXBsZQ0KPiAgICAgY2VydGlmaWNhdGVzIGhhdmUgYmVlbiBjYWxjdWxh
dGVkLiBUaGlzIG1pZ2h0IGJlIG5lZWRlZCBpZiBtdWx0aXBsZQ0KPiAgICAgY2VydGlmaWNhdGVz
IHdpbGwgYmUgdXNlZCBmb3IgbWVkaWEgYXNzb2NpYXRlZCB3aXRoIGFuIG0tIGxpbmUNCj4gICAg
IChlLmcuIGlmIHNlcGFyYXRlIGNlcnRpZmljYXRlcyBhcmUgdXNlZCBmb3IgUlRQIGFuZCBSVENQ
KSwgb3Igd2hlcmUNCj4gICAgIGl0IGlzIG5vdCBrbm93biB3aGljaCBjZXJ0aWZpY2F0ZSB3aWxs
IGJlIHVzZWQgd2hlbiB0aGUNCj4gICAgIGZpbmdlcnByaW50cyBhcmUgZXhjaGFuZ2VkLiBJbiBz
dWNoIGNhc2VzLCBvbmUgb3IgbW9yZSBmaW5nZXJwcmludHMNCj4gICAgIE1VU1QgYmUgY2FsY3Vs
YXRlZCBmb3IgZWFjaCBwb3NzaWJsZSBjZXJ0aWZpY2F0ZS4gPG5ldz5BbiBlbmRwb2ludA0KPk1V
U1QsIGFzIGEgbWluaW11bSwgY2FsY3VsYXRlIGEgZmluZ2VycHJpbnQgdXNpbmcgdGhlIMWSU0hB
LTI1NsK5DQo+aGFzaCBmdW5jdGlvbiBmb3IgZWFjaCBwb3NzaWJsZSBjZXJ0aWZpY2F0ZS48L3Q+
DQo+DQo+ICAgICBJZiBmaW5nZXJwcmludHMgYXNzb2NpYXRlZCB3aXRoIG11bHRpcGxlIGNlcnRp
ZmljYXRlcyBhcmUNCj4gICAgIGNhbGN1bGF0ZWQsIHRoZSBzYW1lIHNldCBvZiBoYXNoIGZ1bmN0
aW9ucyBNVVNUIGJlIHVzZWQgdG8NCj4gICAgIGNhbGN1bGF0ZSBmaW5nZXJwcmludHMgZm9yIGVh
Y2ggY2VydGlmaWNhdGUgYXNzb2NpYXRlZCB3aXRoIHRoZQ0KPiAgICAgbS0gbGluZS4NCj4NCj4g
ICAgIEZvciBlYWNoIHVzZWQgY2VydGlmaWNhdGUsIGFuIGVuZHBvaW50IE1VU1QgYmUgYWJsZSB0
byBtYXRjaCBhdA0KPiAgICAgbGVhc3Qgb25lIGZpbmdlcnByaW50LCBjYWxjdWxhdGVkIHVzaW5n
IHRoZSBoYXNoIGZ1bmN0aW9uIHRoYXQgdGhlDQo+ICAgICBlbmRwb2ludCBzdXBwb3J0cyBhbmQg
Y29uc2lkZXJzIG1vc3Qgc2VjdXJlLCB3aXRoIHRoZSB1c2VkDQo+ICAgICBjZXJ0aWZpY2F0ZS4g
PG5ldz4gSWYgYSBmaW5nZXJwcmludCBjYWxjdWxhdGVkIHVzaW5nIHRoZSDCuVNIQS0yNTbCuQ0K
Pmhhc2gNCj5mdW5jdGlvbiBpcyBwcmVzZW50LCB0aGUgZW5kcG9pbnQgTVVTVCBiZSBhYmxlIHRv
IG1hdGNoIGl0IDwvbmV3Pi4gSWYNCj50aGVyZSBpcyBubyBtYXRjaCwgdGhlDQo+ZW5kcG9pbnQg
TVVTVCBOT1QgZXN0YWJsaXNoIHRoZSBUTFMgY29ubmVjdGlvbi4gSW4gYWRkaXRpb24sIHRoZSBl
bmRwb2ludA0KPk1BWSBhbHNvIGNoZWNrDQo+ICAgICBmaW5nZXJwcmludHMgY2FsY3VsYXRlZCB1
c2luZyBvdGhlciBoYXNoIGZ1bmN0aW9ucyB0aGF0IGl0IGhhcw0KPiAgICAgcmVjZWl2ZWQgZm9y
IGEgbWF0Y2guIEZvciBlYWNoIGhhc2ggZnVuY3Rpb24gY2hlY2tlZCwgb25lIG9mIHRoZQ0KPiAg
ICAgcmVjZWl2ZWQgZmluZ2VycHJpbnRzIE1VU1QgbWF0Y2ggdGhlIHVzZWQgY2VydGlmaWNhdGUu
DQo+DQo+ICAgICBOT1RFOiBUaGUgU0RQIGZpbmdlcnByaW50IGF0dHJpYnV0ZSBkb2VzIG5vdCBj
b250YWluIGEgcmVmZXJlbmNlIHRvDQo+ICAgICBhIHNwZWNpZmljIGNlcnRpZmljYXRlLiBFbmRw
b2ludHMgbmVlZCB0byBjb21wYXJlIHRoZSBmaW5nZXJwcmludA0KPiAgICAgd2l0aCBhIGNlcnRp
ZmljYXRlIGhhc2ggaW4gb3JkZXIgdG8gbG9vayBmb3IgYSBtYXRjaC4NCj4NCj4tLS0tLQ0KPg0K
PlJlZ2FyZHMsDQo+DQo+Q2hyaXN0ZXINCj4NCj4NCj4NCj5fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KPm1tdXNpYyBtYWlsaW5nIGxpc3QNCj5tbXVzaWNA
aWV0Zi5vcmcNCj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNpYw0K
DQo=


From nobody Thu May 26 04:32:09 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B3D12DA71 for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 04:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7yU7E_gVDUR for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 04:32:05 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1509012DDA1 for <mmusic@ietf.org>; Thu, 26 May 2016 04:31:56 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-04-5746deaa7612
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.183.30]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 3A.73.12516.AAED6475; Thu, 26 May 2016 13:31:55 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0294.000; Thu, 26 May 2016 13:31:54 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Martin Thomson <martin.thomson@gmail.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "Roman Shpount" <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAeuwA=
Date: Thu, 26 May 2016 11:31:54 +0000
Message-ID: <D36CB9E1.941C%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com>
In-Reply-To: <D36CA01E.93ED%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C582A6621F9E8F4EBAFD3CBFBA1CCF1C@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrLIsWRmVeSWpSXmKPExsUyM2K7nO7qe27hBtu+sVlcO/OP0WLq8scs Fis2HGC1mHFhKrMDi8ff9x+YPHbOusvusWTJTyaPW1MKAliiuGxSUnMyy1KL9O0SuDL+Tooo +KFY8WbeK5YGxg7FLkZODgkBE4n5k46xQNhiEhfurWfrYuTiEBI4wijxsuUAE4SzhFHiyNcn QA4HB5uAhUT3P22QuIjABkaJCy33mUHizALqElcXB4EMEhawl7h6+TITiC0i4CCx8+1VFoj6 LkaJLa93s4HUswioSnz7FA5SwytgJdF08iczxK5rbBJLlr4Du4hTwFriY/tUMJsR6Lrvp9aA DWUWEJe49WQ+E8TVAhJL9pxnhrBFJV4+/scKYosK6Ense3GeESKuKLHzbDvUnZoS63fpQ4yx llh8aSE7hK0oMaX7ITvEPYISJ2c+YZnAKDELybZZCN2zkHTPQtI9C0n3AkbWVYyixanFxbnp RsZ6qUWZycXF+Xl6eaklmxiBkXpwy2/dHYyrXzseYhTgYFTi4U1QcAsXYk0sK67MPcQowcGs JMIrdAsoxJuSWFmVWpQfX1Sak1p8iFGag0VJnNf/pWK4kEB6YklqdmpqQWoRTJaJg1OqgXEu 85xjbvuPzdvBnzaFx/dW1H/7CUfM8soZXxds6QsLV02tTBfcp9i5+vmhH7HZthoT/njqlp8/ ezfq/JaG1RkKX3duDrh3uKW+0O9gY9S+n9LTZyVJbf35hGNFX83m5ra1C2Y5e3v3y1Y7eZ3P 9gj2DPmmXfymL7mjomzyr4Xqco8KxOeLBymxFGckGmoxFxUnAgDw4SPb0AIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/O3h1gwBKVIl_zswe7vG43I1pJzs>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 11:32:07 -0000

WW91IGNhbiBhbHNvIHNlZSB0aGUgc3VnZ2VzdGVkIGNoYW5nZXMgaW4gdGhpcyBwdWxsIHJlcXVl
c3Q6DQoNCmh0dHBzOi8vZ2l0aHViLmNvbS9jZGg0dS9kcmFmdC00NTcyLXVwZGF0ZS9wdWxsLzEv
ZmlsZXMNCg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpPbiAyNi8wNS8xNiAxMjo0MSwgIkNo
cmlzdGVyIEhvbG1iZXJnIiA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPg0Kd3JvdGU6
DQoNCj5BcmUgcGVvcGxlIG9rIHdpdGggdGhpcz8NCj4NCj5SZWdhcmRzLA0KPg0KPkNocmlzdGVy
DQo+DQo+T24gMjUvMDUvMTYgMTA6MTEsICJtbXVzaWMgb24gYmVoYWxmIG9mIENocmlzdGVyIEhv
bG1iZXJnIg0KPjxtbXVzaWMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgY2hyaXN0ZXIu
aG9sbWJlcmdAZXJpY3Nzb24uY29tPg0KPndyb3RlOg0KPg0KPj5IaSwNCj4+DQo+PkluIGFkZGl0
aW9uIHRvIHRoZSB0ZXh0IGNoYW5nZSBzdWdnZXN0ZWQgYnkgTWFydGluLCBJwrl2ZSBhbHNvIGlk
ZW50aWZpZWQNCj4+dGhlIGZvbGxvd2luZyBjaGFuZ2VzIGJ5IG1hbmRhdGluZyBTSEEtMjU2Lg0K
Pj4NCj4+LS0tLS0NCj4+DQo+PkFic3RyYWN0ICYgSW50cm9kdWN0aW9uOg0KPj4NCj4+T0xEOg0K
Pj4NCj4+IlRoZSBkb2N1bWVudCBhbHNvIHVwZGF0ZXMgdGhlIHByZWZlcnJlZCBjaXBoZXIgc3Vp
dGUgdG8gYmUgdXNlZCwuLi4iDQo+Pg0KPj4NCj4+TkVXOg0KPj4NCj4+wrNUaGUgZG9jdW1lbnQg
YWxzbyByZXBsYWNlcyB0aGUgcHJlZmVycmVkIGNpcGhlciBzdWl0ZSB3aXRoIGEgbWFuZGF0ZSB0
bw0KPj5zdXBwb3J0IGEgc3Ryb25nZXIgY2lwaGVyIHN1aXRlLMWgwrINCj4+DQo+Pi0tLS0tDQo+
Pg0KPj5TZWN0aW9uIDU6DQo+Pg0KPj5UaGUgY2hhbmdlcyB0byB0aGUgY3VycmVudGx5IHN1Z2dl
c3RlZCBuZXcgdGV4dCBiZXR3ZWVuIDxuZXc+IGFuZCA8L25ldz4uDQo+Pg0KPj4NCj4+IE5FVyBU
RVhUOg0KPj4NCj4+ICAgICBNdWx0aXBsZSBTRFAgZmluZ2VycHJpbnQgYXR0cmlidXRlcyBjYW4g
YmUgYXNzb2NpYXRlZCB3aXRoIGFuIG0tDQo+PiAgICAgbGluZS4gVGhpcyBjYW4gb2NjdXIgaWYg
bXVsdGlwbGUgZmluZ2VycHJpbnRzIGhhdmUgYmVlbiBjYWxjdWxhdGVkDQo+PiAgICAgZm9yIGEg
Y2VydGlmaWNhdGUgdXNpbmcgZGlmZmVyZW50IGhhc2ggZnVuY3Rpb25zLiBJdCBjYW4gYWxzbw0K
Pj4gICAgIG9jY3VyIGlmIG9uZSBvciBtb3JlIGZpbmdlcnByaW50cyBhc3NvY2lhdGVkIHdpdGgg
bXVsdGlwbGUNCj4+ICAgICBjZXJ0aWZpY2F0ZXMgaGF2ZSBiZWVuIGNhbGN1bGF0ZWQuIFRoaXMg
bWlnaHQgYmUgbmVlZGVkIGlmIG11bHRpcGxlDQo+PiAgICAgY2VydGlmaWNhdGVzIHdpbGwgYmUg
dXNlZCBmb3IgbWVkaWEgYXNzb2NpYXRlZCB3aXRoIGFuIG0tIGxpbmUNCj4+ICAgICAoZS5nLiBp
ZiBzZXBhcmF0ZSBjZXJ0aWZpY2F0ZXMgYXJlIHVzZWQgZm9yIFJUUCBhbmQgUlRDUCksIG9yIHdo
ZXJlDQo+PiAgICAgaXQgaXMgbm90IGtub3duIHdoaWNoIGNlcnRpZmljYXRlIHdpbGwgYmUgdXNl
ZCB3aGVuIHRoZQ0KPj4gICAgIGZpbmdlcnByaW50cyBhcmUgZXhjaGFuZ2VkLiBJbiBzdWNoIGNh
c2VzLCBvbmUgb3IgbW9yZSBmaW5nZXJwcmludHMNCj4+ICAgICBNVVNUIGJlIGNhbGN1bGF0ZWQg
Zm9yIGVhY2ggcG9zc2libGUgY2VydGlmaWNhdGUuIDxuZXc+QW4gZW5kcG9pbnQNCj4+TVVTVCwg
YXMgYSBtaW5pbXVtLCBjYWxjdWxhdGUgYSBmaW5nZXJwcmludCB1c2luZyB0aGUgxZJTSEEtMjU2
wrkNCj4+aGFzaCBmdW5jdGlvbiBmb3IgZWFjaCBwb3NzaWJsZSBjZXJ0aWZpY2F0ZS48L3Q+DQo+
Pg0KPj4gICAgIElmIGZpbmdlcnByaW50cyBhc3NvY2lhdGVkIHdpdGggbXVsdGlwbGUgY2VydGlm
aWNhdGVzIGFyZQ0KPj4gICAgIGNhbGN1bGF0ZWQsIHRoZSBzYW1lIHNldCBvZiBoYXNoIGZ1bmN0
aW9ucyBNVVNUIGJlIHVzZWQgdG8NCj4+ICAgICBjYWxjdWxhdGUgZmluZ2VycHJpbnRzIGZvciBl
YWNoIGNlcnRpZmljYXRlIGFzc29jaWF0ZWQgd2l0aCB0aGUNCj4+ICAgICBtLSBsaW5lLg0KPj4N
Cj4+ICAgICBGb3IgZWFjaCB1c2VkIGNlcnRpZmljYXRlLCBhbiBlbmRwb2ludCBNVVNUIGJlIGFi
bGUgdG8gbWF0Y2ggYXQNCj4+ICAgICBsZWFzdCBvbmUgZmluZ2VycHJpbnQsIGNhbGN1bGF0ZWQg
dXNpbmcgdGhlIGhhc2ggZnVuY3Rpb24gdGhhdCB0aGUNCj4+ICAgICBlbmRwb2ludCBzdXBwb3J0
cyBhbmQgY29uc2lkZXJzIG1vc3Qgc2VjdXJlLCB3aXRoIHRoZSB1c2VkDQo+PiAgICAgY2VydGlm
aWNhdGUuIDxuZXc+IElmIGEgZmluZ2VycHJpbnQgY2FsY3VsYXRlZCB1c2luZyB0aGUgwrlTSEEt
MjU2wrkNCj4+aGFzaA0KPj5mdW5jdGlvbiBpcyBwcmVzZW50LCB0aGUgZW5kcG9pbnQgTVVTVCBi
ZSBhYmxlIHRvIG1hdGNoIGl0IDwvbmV3Pi4gSWYNCj4+dGhlcmUgaXMgbm8gbWF0Y2gsIHRoZQ0K
Pj5lbmRwb2ludCBNVVNUIE5PVCBlc3RhYmxpc2ggdGhlIFRMUyBjb25uZWN0aW9uLiBJbiBhZGRp
dGlvbiwgdGhlIGVuZHBvaW50DQo+Pk1BWSBhbHNvIGNoZWNrDQo+PiAgICAgZmluZ2VycHJpbnRz
IGNhbGN1bGF0ZWQgdXNpbmcgb3RoZXIgaGFzaCBmdW5jdGlvbnMgdGhhdCBpdCBoYXMNCj4+ICAg
ICByZWNlaXZlZCBmb3IgYSBtYXRjaC4gRm9yIGVhY2ggaGFzaCBmdW5jdGlvbiBjaGVja2VkLCBv
bmUgb2YgdGhlDQo+PiAgICAgcmVjZWl2ZWQgZmluZ2VycHJpbnRzIE1VU1QgbWF0Y2ggdGhlIHVz
ZWQgY2VydGlmaWNhdGUuDQo+Pg0KPj4gICAgIE5PVEU6IFRoZSBTRFAgZmluZ2VycHJpbnQgYXR0
cmlidXRlIGRvZXMgbm90IGNvbnRhaW4gYSByZWZlcmVuY2UgdG8NCj4+ICAgICBhIHNwZWNpZmlj
IGNlcnRpZmljYXRlLiBFbmRwb2ludHMgbmVlZCB0byBjb21wYXJlIHRoZSBmaW5nZXJwcmludA0K
Pj4gICAgIHdpdGggYSBjZXJ0aWZpY2F0ZSBoYXNoIGluIG9yZGVyIHRvIGxvb2sgZm9yIGEgbWF0
Y2guDQo+Pg0KPj4tLS0tLQ0KPj4NCj4+UmVnYXJkcywNCj4+DQo+PkNocmlzdGVyDQo+Pg0KPj4N
Cj4+DQo+Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
Pm1tdXNpYyBtYWlsaW5nIGxpc3QNCj4+bW11c2ljQGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQo+DQoNCg==


From nobody Thu May 26 07:48:05 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB0612D6AA for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 07:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C_ohfavKChUm for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 07:48:02 -0700 (PDT)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECCCA12B04F for <mmusic@ietf.org>; Thu, 26 May 2016 07:48:01 -0700 (PDT)
Received: by mail-oi0-x230.google.com with SMTP id w184so120894662oiw.2 for <mmusic@ietf.org>; Thu, 26 May 2016 07:48:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=NE1gBA9NPpfRGS/uAmzTjbdo2x/oP426OQrFJcDus3w=; b=p81tIWRn6JjpY6DcTHSbpaWjHoyaAUSggX/vwRIxG0qgSPpHSmcVCI0SqEdFiAEo3T E/ot6oCn5Sb4/dMxss+LpY4IAtseChTXusAA7nwT/SmSF7S3gNFysc4HtX7cR4FCNPT2 MhGzhwH9i5/kArh6Uj4ClDlrWRrlz8TvFCXR1kTRJzVkYt1TIpQbsykFor6FH/sLMMEw zKwYKNUhPiHX02s+HygVYXwhe2B5QEOKTCHhnmzixKI2Vxj6PshQys52xSwgDT6SP1In vyA3YiZ7VRD385aMIar6mpsoeGLtrw0Q8pC3HMGnRmldvf0YeydZYDsfxFMv/vKY7Rk4 lDeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=NE1gBA9NPpfRGS/uAmzTjbdo2x/oP426OQrFJcDus3w=; b=Ef2rt1cpB3Q8YOEbn+Nmgzg7NRd+BPbqzrTzI54N/Tqux+NSfk0XSPVdbzD+f1Z50/ 1rGgUWEoonVo4DymomxD5Vbt5jk2Vs9WfW3+gATpfWeP0JkCzLS2gkFwBP5mcTxnKdrx +eFhf2t24muI3NTdQDGbOkPHdt6REpAYrwH8hJpf0WRwubOHzf9a2iGZCxY9c/EYqEFL f1HFI99MKUjchy6bHF+po0flAO6cwGhqtmCPxRoVUj3sK8ZiWqfzvPfh5G3K/1l8uUHq gVg2770bwloYS2UOm3bcsZYJaL2BnhgatFR3/2IfWNVLEIF3au/Jl3pGlIu83kioJ+7T Gi5g==
X-Gm-Message-State: ALyK8tJnjdq3375wiSrWCDKF3J0rq/5M1/0xGt3TLsAW5y4fbnWtM8yPM3ZjLWIvrDUtBw==
X-Received: by 10.157.1.116 with SMTP id 107mr5917288otu.145.1464274081214; Thu, 26 May 2016 07:48:01 -0700 (PDT)
Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com. [209.85.213.178]) by smtp.gmail.com with ESMTPSA id l103sm6662871otl.5.2016.05.26.07.48.00 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Thu, 26 May 2016 07:48:00 -0700 (PDT)
Received: by mail-ig0-f178.google.com with SMTP id fh2so48581878igd.1 for <mmusic@ietf.org>; Thu, 26 May 2016 07:48:00 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.37.147 with SMTP id y19mr3517478igj.42.1464274079884; Thu, 26 May 2016 07:47:59 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Thu, 26 May 2016 07:47:59 -0700 (PDT)
In-Reply-To: <D36CA01E.93ED%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com>
Date: Thu, 26 May 2016 10:47:59 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com>
Message-ID: <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=f46d0444006e62b68e0533bfe02e
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/gzRA1JQEM3Qs-MQ-zfWpXRUXgdA>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 14:48:04 -0000

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

I still think SHA-256 requirement should be a SHOULD not a MUST.

_____________
Roman Shpount

On Thu, May 26, 2016 at 5:41 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Are people ok with this?
>
> Regards,
>
> Christer
>
> On 25/05/16 10:11, "mmusic on behalf of Christer Holmberg"
> <mmusic-bounces@ietf.org on behalf of christer.holmberg@ericsson.com>
> wrote:
>
> >Hi,
> >
> >In addition to the text change suggested by Martin, I=C2=B9ve also ident=
ified
> >the following changes by mandating SHA-256.
> >
> >-----
> >
> >Abstract & Introduction:
> >
> >OLD:
> >
> >"The document also updates the preferred cipher suite to be used,..."
> >
> >
> >NEW:
> >
> >=C2=B3The document also replaces the preferred cipher suite with a manda=
te to
> >support a stronger cipher suite,=C5=A0=C2=B2
> >
> >-----
> >
> >Section 5:
> >
> >The changes to the currently suggested new text between <new> and </new>=
.
> >
> >
> > NEW TEXT:
> >
> >     Multiple SDP fingerprint attributes can be associated with an m-
> >     line. This can occur if multiple fingerprints have been calculated
> >     for a certificate using different hash functions. It can also
> >     occur if one or more fingerprints associated with multiple
> >     certificates have been calculated. This might be needed if multiple
> >     certificates will be used for media associated with an m- line
> >     (e.g. if separate certificates are used for RTP and RTCP), or where
> >     it is not known which certificate will be used when the
> >     fingerprints are exchanged. In such cases, one or more fingerprints
> >     MUST be calculated for each possible certificate. <new>An endpoint
> >MUST, as a minimum, calculate a fingerprint using the =C5=92SHA-256=C2=
=B9
> >hash function for each possible certificate.</t>
> >
> >     If fingerprints associated with multiple certificates are
> >     calculated, the same set of hash functions MUST be used to
> >     calculate fingerprints for each certificate associated with the
> >     m- line.
> >
> >     For each used certificate, an endpoint MUST be able to match at
> >     least one fingerprint, calculated using the hash function that the
> >     endpoint supports and considers most secure, with the used
> >     certificate. <new> If a fingerprint calculated using the =C2=B9SHA-=
256=C2=B9
> >hash
> >function is present, the endpoint MUST be able to match it </new>. If
> >there is no match, the
> >endpoint MUST NOT establish the TLS connection. In addition, the endpoin=
t
> >MAY also check
> >     fingerprints calculated using other hash functions that it has
> >     received for a match. For each hash function checked, one of the
> >     received fingerprints MUST match the used certificate.
> >
> >     NOTE: The SDP fingerprint attribute does not contain a reference to
> >     a specific certificate. Endpoints need to compare the fingerprint
> >     with a certificate hash in order to look for a match.
> >
> >-----
> >
> >Regards,
> >
> >Christer
> >
> >
> >
> >_______________________________________________
> >mmusic mailing list
> >mmusic@ietf.org
> >https://www.ietf.org/mailman/listinfo/mmusic
>
>

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

<div dir=3D"ltr">I still think SHA-256 requirement should be a SHOULD not a=
 MUST.</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D=
"gmail_signature">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Thu, May 26, 2016 at 5:41 AM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Are people ok with this?<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
On 25/05/16 10:11, &quot;mmusic on behalf of Christer Holmberg&quot;<br>
&lt;<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a> =
on behalf of <a href=3D"mailto:christer.holmberg@ericsson.com">christer.hol=
mberg@ericsson.com</a>&gt;<br>
wrote:<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;Hi,<br>
&gt;<br>
&gt;In addition to the text change suggested by Martin, I=C2=B9ve also iden=
tified<br>
&gt;the following changes by mandating SHA-256.<br>
&gt;<br>
&gt;-----<br>
&gt;<br>
&gt;Abstract &amp; Introduction:<br>
&gt;<br>
&gt;OLD:<br>
&gt;<br>
&gt;&quot;The document also updates the preferred cipher suite to be used,.=
..&quot;<br>
&gt;<br>
&gt;<br>
&gt;NEW:<br>
&gt;<br>
&gt;=C2=B3The document also replaces the preferred cipher suite with a mand=
ate to<br>
&gt;support a stronger cipher suite,=C5=A0=C2=B2<br>
&gt;<br>
&gt;-----<br>
&gt;<br>
&gt;Section 5:<br>
&gt;<br>
&gt;The changes to the currently suggested new text between &lt;new&gt; and=
 &lt;/new&gt;.<br>
&gt;<br>
&gt;<br>
&gt; NEW TEXT:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Multiple SDP fingerprint attributes can be associat=
ed with an m-<br>
&gt;=C2=A0 =C2=A0 =C2=A0line. This can occur if multiple fingerprints have =
been calculated<br>
&gt;=C2=A0 =C2=A0 =C2=A0for a certificate using different hash functions. I=
t can also<br>
&gt;=C2=A0 =C2=A0 =C2=A0occur if one or more fingerprints associated with m=
ultiple<br>
&gt;=C2=A0 =C2=A0 =C2=A0certificates have been calculated. This might be ne=
eded if multiple<br>
&gt;=C2=A0 =C2=A0 =C2=A0certificates will be used for media associated with=
 an m- line<br>
&gt;=C2=A0 =C2=A0 =C2=A0(e.g. if separate certificates are used for RTP and=
 RTCP), or where<br>
&gt;=C2=A0 =C2=A0 =C2=A0it is not known which certificate will be used when=
 the<br>
&gt;=C2=A0 =C2=A0 =C2=A0fingerprints are exchanged. In such cases, one or m=
ore fingerprints<br>
&gt;=C2=A0 =C2=A0 =C2=A0MUST be calculated for each possible certificate. &=
lt;new&gt;An endpoint<br>
&gt;MUST, as a minimum, calculate a fingerprint using the =C5=92SHA-256=C2=
=B9<br>
&gt;hash function for each possible certificate.&lt;/t&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0If fingerprints associated with multiple certificat=
es are<br>
&gt;=C2=A0 =C2=A0 =C2=A0calculated, the same set of hash functions MUST be =
used to<br>
&gt;=C2=A0 =C2=A0 =C2=A0calculate fingerprints for each certificate associa=
ted with the<br>
&gt;=C2=A0 =C2=A0 =C2=A0m- line.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0For each used certificate, an endpoint MUST be able=
 to match at<br>
&gt;=C2=A0 =C2=A0 =C2=A0least one fingerprint, calculated using the hash fu=
nction that the<br>
&gt;=C2=A0 =C2=A0 =C2=A0endpoint supports and considers most secure, with t=
he used<br>
&gt;=C2=A0 =C2=A0 =C2=A0certificate. &lt;new&gt; If a fingerprint calculate=
d using the =C2=B9SHA-256=C2=B9<br>
&gt;hash<br>
&gt;function is present, the endpoint MUST be able to match it &lt;/new&gt;=
. If<br>
&gt;there is no match, the<br>
&gt;endpoint MUST NOT establish the TLS connection. In addition, the endpoi=
nt<br>
&gt;MAY also check<br>
&gt;=C2=A0 =C2=A0 =C2=A0fingerprints calculated using other hash functions =
that it has<br>
&gt;=C2=A0 =C2=A0 =C2=A0received for a match. For each hash function checke=
d, one of the<br>
&gt;=C2=A0 =C2=A0 =C2=A0received fingerprints MUST match the used certifica=
te.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0NOTE: The SDP fingerprint attribute does not contai=
n a reference to<br>
&gt;=C2=A0 =C2=A0 =C2=A0a specific certificate. Endpoints need to compare t=
he fingerprint<br>
&gt;=C2=A0 =C2=A0 =C2=A0with a certificate hash in order to look for a matc=
h.<br>
&gt;<br>
&gt;-----<br>
&gt;<br>
&gt;Regards,<br>
&gt;<br>
&gt;Christer<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;_______________________________________________<br>
&gt;mmusic mailing list<br>
&gt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt;<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br>
</div></div></blockquote></div><br></div>

--f46d0444006e62b68e0533bfe02e--


From nobody Thu May 26 07:50:25 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D72E12D158 for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 07:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzQCeqXyVG3z for <mmusic@ietfa.amsl.com>; Thu, 26 May 2016 07:50:22 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CA2612D17C for <mmusic@ietf.org>; Thu, 26 May 2016 07:50:20 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-f8-57470d2ab3dc
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 01.F6.12926.A2D07475; Thu, 26 May 2016 16:50:18 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0294.000; Thu, 26 May 2016 16:50:18 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/g==
Date: Thu, 26 May 2016 14:50:17 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com>, <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com>
In-Reply-To: <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FF0C94ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGIsWRmVeSWpSXmKPExsUyM2K7tK4Wr3u4wf1nahbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsErowZD86x FTzIrnh14zZTA+OLjC5GDg4JAROJ9lPxXYycQKaYxIV769lAbCGBI4wSCw6JdzFyAdlLGCU+ bNjIClLPJmAh0f1PG6RGREBV4u/3yUwgNrNAlcSTjg3MILawgL3Exid3mCBqHCR2vr3KAjJH RGASo8Siqz9YQRIsQM13uteygNi8Ar4Sj6+sZ4JYNptdYsrErewgCU6BQImzt++BXcQIdN33 U2ugtolLNH1ZyQpxtYDEkj3nmSFsUYmXj/+xQtTkS3x7dJANYoGgxMmZT1gmMIrMQtI+C0nZ LCRls4D+ZBbQlFi/Sx+iRFFiSvdDdghbQ6J1zlx2ZPEFjOyrGEWLU4uTctONjPVSizKTi4vz 8/TyUks2MQJj7+CW36o7GC+/cTzEKMDBqMTDm6DgFi7EmlhWXJl7iFGCg1lJhFfoFlCINyWx siq1KD++qDQntfgQozQHi5I4r/9LxXAhgfTEktTs1NSC1CKYLBMHp1QDY8m71qevjUNS9zGo PbXYftHqeWDm1qMnmZmVLzaf1Hm5WcFN2ylFMJhzc0Ty2cp/r+N/7y4rft197HZK3G3nuxMS n32bdOHFG9HpO1XWH9HQk5LUVvW1/pZ4wubIQo2NAUtq9x4sf3BnabfP1EddR1aKZvCEym3c nlK3UlyQ2356gHXYz8uSHEosxRmJhlrMRcWJAImq+qm5AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/He37ur_PbsmtkIo-M-TdOiEEbI8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 14:50:24 -0000

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

V0ZNDQoNClNlbnQgZnJvbSBteSBXaW5kb3dzIFBob25lDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KRnJvbTogUm9tYW4gU2hwb3VudDxtYWlsdG86cm9tYW5AdGVsdXJpeC5jb20+
DQpTZW50OiDigI4yNi/igI4wNS/igI4yMDE2IDE3OjQ4DQpUbzogQ2hyaXN0ZXIgSG9sbWJlcmc8
bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4NCkNjOiBNYXJ0aW4gVGhvbXNv
bjxtYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tPjsgUGF1bCBLeXppdmF0PG1haWx0bzpw
a3l6aXZhdEBhbHVtLm1pdC5lZHU+OyBtbXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRm
Lm9yZz4NClN1YmplY3Q6IFJlOiBbTU1VU0lDXSBXR0xDIGZvciBkcmFmdC1pZXRmLW1tdXNpYy00
NTcyLXVwZGF0ZS0wMw0KDQpJIHN0aWxsIHRoaW5rIFNIQS0yNTYgcmVxdWlyZW1lbnQgc2hvdWxk
IGJlIGEgU0hPVUxEIG5vdCBhIE1VU1QuDQoNCl9fX19fX19fX19fX18NClJvbWFuIFNocG91bnQN
Cg0KT24gVGh1LCBNYXkgMjYsIDIwMTYgYXQgNTo0MSBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNo
cmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJp
Y3Nzb24uY29tPj4gd3JvdGU6DQpBcmUgcGVvcGxlIG9rIHdpdGggdGhpcz8NCg0KUmVnYXJkcywN
Cg0KQ2hyaXN0ZXINCg0KT24gMjUvMDUvMTYgMTA6MTEsICJtbXVzaWMgb24gYmVoYWxmIG9mIENo
cmlzdGVyIEhvbG1iZXJnIg0KPG1tdXNpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMt
Ym91bmNlc0BpZXRmLm9yZz4gb24gYmVoYWxmIG9mIGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29u
LmNvbTxtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4NCndyb3RlOg0KDQo+
SGksDQo+DQo+SW4gYWRkaXRpb24gdG8gdGhlIHRleHQgY2hhbmdlIHN1Z2dlc3RlZCBieSBNYXJ0
aW4sIEnCuXZlIGFsc28gaWRlbnRpZmllZA0KPnRoZSBmb2xsb3dpbmcgY2hhbmdlcyBieSBtYW5k
YXRpbmcgU0hBLTI1Ni4NCj4NCj4tLS0tLQ0KPg0KPkFic3RyYWN0ICYgSW50cm9kdWN0aW9uOg0K
Pg0KPk9MRDoNCj4NCj4iVGhlIGRvY3VtZW50IGFsc28gdXBkYXRlcyB0aGUgcHJlZmVycmVkIGNp
cGhlciBzdWl0ZSB0byBiZSB1c2VkLC4uLiINCj4NCj4NCj5ORVc6DQo+DQo+wrNUaGUgZG9jdW1l
bnQgYWxzbyByZXBsYWNlcyB0aGUgcHJlZmVycmVkIGNpcGhlciBzdWl0ZSB3aXRoIGEgbWFuZGF0
ZSB0bw0KPnN1cHBvcnQgYSBzdHJvbmdlciBjaXBoZXIgc3VpdGUsxaDCsg0KPg0KPi0tLS0tDQo+
DQo+U2VjdGlvbiA1Og0KPg0KPlRoZSBjaGFuZ2VzIHRvIHRoZSBjdXJyZW50bHkgc3VnZ2VzdGVk
IG5ldyB0ZXh0IGJldHdlZW4gPG5ldz4gYW5kIDwvbmV3Pi4NCj4NCj4NCj4gTkVXIFRFWFQ6DQo+
DQo+ICAgICBNdWx0aXBsZSBTRFAgZmluZ2VycHJpbnQgYXR0cmlidXRlcyBjYW4gYmUgYXNzb2Np
YXRlZCB3aXRoIGFuIG0tDQo+ICAgICBsaW5lLiBUaGlzIGNhbiBvY2N1ciBpZiBtdWx0aXBsZSBm
aW5nZXJwcmludHMgaGF2ZSBiZWVuIGNhbGN1bGF0ZWQNCj4gICAgIGZvciBhIGNlcnRpZmljYXRl
IHVzaW5nIGRpZmZlcmVudCBoYXNoIGZ1bmN0aW9ucy4gSXQgY2FuIGFsc28NCj4gICAgIG9jY3Vy
IGlmIG9uZSBvciBtb3JlIGZpbmdlcnByaW50cyBhc3NvY2lhdGVkIHdpdGggbXVsdGlwbGUNCj4g
ICAgIGNlcnRpZmljYXRlcyBoYXZlIGJlZW4gY2FsY3VsYXRlZC4gVGhpcyBtaWdodCBiZSBuZWVk
ZWQgaWYgbXVsdGlwbGUNCj4gICAgIGNlcnRpZmljYXRlcyB3aWxsIGJlIHVzZWQgZm9yIG1lZGlh
IGFzc29jaWF0ZWQgd2l0aCBhbiBtLSBsaW5lDQo+ICAgICAoZS5nLiBpZiBzZXBhcmF0ZSBjZXJ0
aWZpY2F0ZXMgYXJlIHVzZWQgZm9yIFJUUCBhbmQgUlRDUCksIG9yIHdoZXJlDQo+ICAgICBpdCBp
cyBub3Qga25vd24gd2hpY2ggY2VydGlmaWNhdGUgd2lsbCBiZSB1c2VkIHdoZW4gdGhlDQo+ICAg
ICBmaW5nZXJwcmludHMgYXJlIGV4Y2hhbmdlZC4gSW4gc3VjaCBjYXNlcywgb25lIG9yIG1vcmUg
ZmluZ2VycHJpbnRzDQo+ICAgICBNVVNUIGJlIGNhbGN1bGF0ZWQgZm9yIGVhY2ggcG9zc2libGUg
Y2VydGlmaWNhdGUuIDxuZXc+QW4gZW5kcG9pbnQNCj5NVVNULCBhcyBhIG1pbmltdW0sIGNhbGN1
bGF0ZSBhIGZpbmdlcnByaW50IHVzaW5nIHRoZSDFklNIQS0yNTbCuQ0KPmhhc2ggZnVuY3Rpb24g
Zm9yIGVhY2ggcG9zc2libGUgY2VydGlmaWNhdGUuPC90Pg0KPg0KPiAgICAgSWYgZmluZ2VycHJp
bnRzIGFzc29jaWF0ZWQgd2l0aCBtdWx0aXBsZSBjZXJ0aWZpY2F0ZXMgYXJlDQo+ICAgICBjYWxj
dWxhdGVkLCB0aGUgc2FtZSBzZXQgb2YgaGFzaCBmdW5jdGlvbnMgTVVTVCBiZSB1c2VkIHRvDQo+
ICAgICBjYWxjdWxhdGUgZmluZ2VycHJpbnRzIGZvciBlYWNoIGNlcnRpZmljYXRlIGFzc29jaWF0
ZWQgd2l0aCB0aGUNCj4gICAgIG0tIGxpbmUuDQo+DQo+ICAgICBGb3IgZWFjaCB1c2VkIGNlcnRp
ZmljYXRlLCBhbiBlbmRwb2ludCBNVVNUIGJlIGFibGUgdG8gbWF0Y2ggYXQNCj4gICAgIGxlYXN0
IG9uZSBmaW5nZXJwcmludCwgY2FsY3VsYXRlZCB1c2luZyB0aGUgaGFzaCBmdW5jdGlvbiB0aGF0
IHRoZQ0KPiAgICAgZW5kcG9pbnQgc3VwcG9ydHMgYW5kIGNvbnNpZGVycyBtb3N0IHNlY3VyZSwg
d2l0aCB0aGUgdXNlZA0KPiAgICAgY2VydGlmaWNhdGUuIDxuZXc+IElmIGEgZmluZ2VycHJpbnQg
Y2FsY3VsYXRlZCB1c2luZyB0aGUgwrlTSEEtMjU2wrkNCj5oYXNoDQo+ZnVuY3Rpb24gaXMgcHJl
c2VudCwgdGhlIGVuZHBvaW50IE1VU1QgYmUgYWJsZSB0byBtYXRjaCBpdCA8L25ldz4uIElmDQo+
dGhlcmUgaXMgbm8gbWF0Y2gsIHRoZQ0KPmVuZHBvaW50IE1VU1QgTk9UIGVzdGFibGlzaCB0aGUg
VExTIGNvbm5lY3Rpb24uIEluIGFkZGl0aW9uLCB0aGUgZW5kcG9pbnQNCj5NQVkgYWxzbyBjaGVj
aw0KPiAgICAgZmluZ2VycHJpbnRzIGNhbGN1bGF0ZWQgdXNpbmcgb3RoZXIgaGFzaCBmdW5jdGlv
bnMgdGhhdCBpdCBoYXMNCj4gICAgIHJlY2VpdmVkIGZvciBhIG1hdGNoLiBGb3IgZWFjaCBoYXNo
IGZ1bmN0aW9uIGNoZWNrZWQsIG9uZSBvZiB0aGUNCj4gICAgIHJlY2VpdmVkIGZpbmdlcnByaW50
cyBNVVNUIG1hdGNoIHRoZSB1c2VkIGNlcnRpZmljYXRlLg0KPg0KPiAgICAgTk9URTogVGhlIFNE
UCBmaW5nZXJwcmludCBhdHRyaWJ1dGUgZG9lcyBub3QgY29udGFpbiBhIHJlZmVyZW5jZSB0bw0K
PiAgICAgYSBzcGVjaWZpYyBjZXJ0aWZpY2F0ZS4gRW5kcG9pbnRzIG5lZWQgdG8gY29tcGFyZSB0
aGUgZmluZ2VycHJpbnQNCj4gICAgIHdpdGggYSBjZXJ0aWZpY2F0ZSBoYXNoIGluIG9yZGVyIHRv
IGxvb2sgZm9yIGEgbWF0Y2guDQo+DQo+LS0tLS0NCj4NCj5SZWdhcmRzLA0KPg0KPkNocmlzdGVy
DQo+DQo+DQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj5tbXVzaWMgbWFpbGluZyBsaXN0DQo+bW11c2ljQGlldGYub3JnPG1haWx0bzptbXVzaWNA
aWV0Zi5vcmc+DQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMN
Cg0KDQo=

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPGRpdj4NCjxkaXYg
c3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQiPldG
TTxicj4NCjxicj4NClNlbnQgZnJvbSBteSBXaW5kb3dzIFBob25lPC9kaXY+DQo8L2Rpdj4NCjxk
aXYgZGlyPSJsdHIiPg0KPGhyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fu
cy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQiPkZyb206DQo8L3NwYW4+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjEx
cHQiPjxhIGhyZWY9Im1haWx0bzpyb21hbkB0ZWx1cml4LmNvbSI+Um9tYW4gU2hwb3VudDwvYT48
L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsg
Zm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQiPlNlbnQ6DQo8L3NwYW4+PHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQiPuKAjjI2
L+KAjjA1L+KAjjIwMTYgMTc6NDg8L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQiPlRv
Og0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZv
bnQtc2l6ZToxMXB0Ij48YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24u
Y29tIj5DaHJpc3RlciBIb2xtYmVyZzwvYT48L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJv
bGQiPkNjOg0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2Vy
aWY7IGZvbnQtc2l6ZToxMXB0Ij48YSBocmVmPSJtYWlsdG86bWFydGluLnRob21zb25AZ21haWwu
Y29tIj5NYXJ0aW4gVGhvbXNvbjwvYT47DQo8YSBocmVmPSJtYWlsdG86cGt5eml2YXRAYWx1bS5t
aXQuZWR1Ij5QYXVsIEt5eml2YXQ8L2E+OyA8YSBocmVmPSJtYWlsdG86bW11c2ljQGlldGYub3Jn
Ij4NCm1tdXNpY0BpZXRmLm9yZzwvYT48L3NwYW4+PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OkNhbGlicmksc2Fucy1zZXJpZjsgZm9udC1zaXplOjExcHQ7IGZvbnQtd2VpZ2h0OmJvbGQi
PlN1YmplY3Q6DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1z
ZXJpZjsgZm9udC1zaXplOjExcHQiPlJlOiBbTU1VU0lDXSBXR0xDIGZvciBkcmFmdC1pZXRmLW1t
dXNpYy00NTcyLXVwZGF0ZS0wMzwvc3Bhbj48YnI+DQo8YnI+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2
IGRpcj0ibHRyIj5JIHN0aWxsIHRoaW5rIFNIQS0yNTYgcmVxdWlyZW1lbnQgc2hvdWxkIGJlIGEg
U0hPVUxEIG5vdCBhIE1VU1QuPC9kaXY+DQo8ZGl2IGNsYXNzPSJnbWFpbF9leHRyYSI+PGJyIGNs
ZWFyPSJhbGwiPg0KPGRpdj4NCjxkaXYgY2xhc3M9ImdtYWlsX3NpZ25hdHVyZSI+X19fX19fX19f
X19fXzxicj4NClJvbWFuIFNocG91bnQ8L2Rpdj4NCjwvZGl2Pg0KPGJyPg0KPGRpdiBjbGFzcz0i
Z21haWxfcXVvdGUiPk9uIFRodSwgTWF5IDI2LCAyMDE2IGF0IDU6NDEgQU0sIENocmlzdGVyIEhv
bG1iZXJnIDxzcGFuIGRpcj0ibHRyIj4NCiZsdDs8YSBocmVmPSJtYWlsdG86Y2hyaXN0ZXIuaG9s
bWJlcmdAZXJpY3Nzb24uY29tIiB0YXJnZXQ9Il9ibGFuayI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJp
Y3Nzb24uY29tPC9hPiZndDs8L3NwYW4+IHdyb3RlOjxicj4NCjxibG9ja3F1b3RlIGNsYXNzPSJn
bWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjowIDAgMCAuOGV4OyBib3JkZXItbGVmdDoxcHggI2Nj
YyBzb2xpZDsgcGFkZGluZy1sZWZ0OjFleCI+DQpBcmUgcGVvcGxlIG9rIHdpdGggdGhpcz88YnI+
DQo8YnI+DQpSZWdhcmRzLDxicj4NCjxicj4NCkNocmlzdGVyPGJyPg0KPGJyPg0KT24gMjUvMDUv
MTYgMTA6MTEsICZxdW90O21tdXNpYyBvbiBiZWhhbGYgb2YgQ2hyaXN0ZXIgSG9sbWJlcmcmcXVv
dDs8YnI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOm1tdXNpYy1ib3VuY2VzQGlldGYub3JnIj5tbXVz
aWMtYm91bmNlc0BpZXRmLm9yZzwvYT4gb24gYmVoYWxmIG9mDQo8YSBocmVmPSJtYWlsdG86Y2hy
aXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tIj5jaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5j
b208L2E+Jmd0Ozxicj4NCndyb3RlOjxicj4NCjxkaXYgY2xhc3M9IkhPRW5aYiI+DQo8ZGl2IGNs
YXNzPSJoNSI+PGJyPg0KJmd0O0hpLDxicj4NCiZndDs8YnI+DQomZ3Q7SW4gYWRkaXRpb24gdG8g
dGhlIHRleHQgY2hhbmdlIHN1Z2dlc3RlZCBieSBNYXJ0aW4sIEnCuXZlIGFsc28gaWRlbnRpZmll
ZDxicj4NCiZndDt0aGUgZm9sbG93aW5nIGNoYW5nZXMgYnkgbWFuZGF0aW5nIFNIQS0yNTYuPGJy
Pg0KJmd0Ozxicj4NCiZndDstLS0tLTxicj4NCiZndDs8YnI+DQomZ3Q7QWJzdHJhY3QgJmFtcDsg
SW50cm9kdWN0aW9uOjxicj4NCiZndDs8YnI+DQomZ3Q7T0xEOjxicj4NCiZndDs8YnI+DQomZ3Q7
JnF1b3Q7VGhlIGRvY3VtZW50IGFsc28gdXBkYXRlcyB0aGUgcHJlZmVycmVkIGNpcGhlciBzdWl0
ZSB0byBiZSB1c2VkLC4uLiZxdW90Ozxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0O05FVzo8
YnI+DQomZ3Q7PGJyPg0KJmd0O8KzVGhlIGRvY3VtZW50IGFsc28gcmVwbGFjZXMgdGhlIHByZWZl
cnJlZCBjaXBoZXIgc3VpdGUgd2l0aCBhIG1hbmRhdGUgdG88YnI+DQomZ3Q7c3VwcG9ydCBhIHN0
cm9uZ2VyIGNpcGhlciBzdWl0ZSzFoMKyPGJyPg0KJmd0Ozxicj4NCiZndDstLS0tLTxicj4NCiZn
dDs8YnI+DQomZ3Q7U2VjdGlvbiA1Ojxicj4NCiZndDs8YnI+DQomZ3Q7VGhlIGNoYW5nZXMgdG8g
dGhlIGN1cnJlbnRseSBzdWdnZXN0ZWQgbmV3IHRleHQgYmV0d2VlbiAmbHQ7bmV3Jmd0OyBhbmQg
Jmx0Oy9uZXcmZ3Q7Ljxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyBORVcgVEVYVDo8YnI+
DQomZ3Q7PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7TXVsdGlwbGUgU0RQIGZpbmdlcnBy
aW50IGF0dHJpYnV0ZXMgY2FuIGJlIGFzc29jaWF0ZWQgd2l0aCBhbiBtLTxicj4NCiZndDsmbmJz
cDsgJm5ic3A7ICZuYnNwO2xpbmUuIFRoaXMgY2FuIG9jY3VyIGlmIG11bHRpcGxlIGZpbmdlcnBy
aW50cyBoYXZlIGJlZW4gY2FsY3VsYXRlZDxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO2Zv
ciBhIGNlcnRpZmljYXRlIHVzaW5nIGRpZmZlcmVudCBoYXNoIGZ1bmN0aW9ucy4gSXQgY2FuIGFs
c288YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtvY2N1ciBpZiBvbmUgb3IgbW9yZSBmaW5n
ZXJwcmludHMgYXNzb2NpYXRlZCB3aXRoIG11bHRpcGxlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsg
Jm5ic3A7Y2VydGlmaWNhdGVzIGhhdmUgYmVlbiBjYWxjdWxhdGVkLiBUaGlzIG1pZ2h0IGJlIG5l
ZWRlZCBpZiBtdWx0aXBsZTxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO2NlcnRpZmljYXRl
cyB3aWxsIGJlIHVzZWQgZm9yIG1lZGlhIGFzc29jaWF0ZWQgd2l0aCBhbiBtLSBsaW5lPGJyPg0K
Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7KGUuZy4gaWYgc2VwYXJhdGUgY2VydGlmaWNhdGVzIGFy
ZSB1c2VkIGZvciBSVFAgYW5kIFJUQ1ApLCBvciB3aGVyZTxicj4NCiZndDsmbmJzcDsgJm5ic3A7
ICZuYnNwO2l0IGlzIG5vdCBrbm93biB3aGljaCBjZXJ0aWZpY2F0ZSB3aWxsIGJlIHVzZWQgd2hl
biB0aGU8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtmaW5nZXJwcmludHMgYXJlIGV4Y2hh
bmdlZC4gSW4gc3VjaCBjYXNlcywgb25lIG9yIG1vcmUgZmluZ2VycHJpbnRzPGJyPg0KJmd0OyZu
YnNwOyAmbmJzcDsgJm5ic3A7TVVTVCBiZSBjYWxjdWxhdGVkIGZvciBlYWNoIHBvc3NpYmxlIGNl
cnRpZmljYXRlLiAmbHQ7bmV3Jmd0O0FuIGVuZHBvaW50PGJyPg0KJmd0O01VU1QsIGFzIGEgbWlu
aW11bSwgY2FsY3VsYXRlIGEgZmluZ2VycHJpbnQgdXNpbmcgdGhlIMWSU0hBLTI1NsK5PGJyPg0K
Jmd0O2hhc2ggZnVuY3Rpb24gZm9yIGVhY2ggcG9zc2libGUgY2VydGlmaWNhdGUuJmx0Oy90Jmd0
Ozxicj4NCiZndDs8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtJZiBmaW5nZXJwcmludHMg
YXNzb2NpYXRlZCB3aXRoIG11bHRpcGxlIGNlcnRpZmljYXRlcyBhcmU8YnI+DQomZ3Q7Jm5ic3A7
ICZuYnNwOyAmbmJzcDtjYWxjdWxhdGVkLCB0aGUgc2FtZSBzZXQgb2YgaGFzaCBmdW5jdGlvbnMg
TVVTVCBiZSB1c2VkIHRvPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7Y2FsY3VsYXRlIGZp
bmdlcnByaW50cyBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSBhc3NvY2lhdGVkIHdpdGggdGhlPGJyPg0K
Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7bS0gbGluZS48YnI+DQomZ3Q7PGJyPg0KJmd0OyZuYnNw
OyAmbmJzcDsgJm5ic3A7Rm9yIGVhY2ggdXNlZCBjZXJ0aWZpY2F0ZSwgYW4gZW5kcG9pbnQgTVVT
VCBiZSBhYmxlIHRvIG1hdGNoIGF0PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7bGVhc3Qg
b25lIGZpbmdlcnByaW50LCBjYWxjdWxhdGVkIHVzaW5nIHRoZSBoYXNoIGZ1bmN0aW9uIHRoYXQg
dGhlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ZW5kcG9pbnQgc3VwcG9ydHMgYW5kIGNv
bnNpZGVycyBtb3N0IHNlY3VyZSwgd2l0aCB0aGUgdXNlZDxicj4NCiZndDsmbmJzcDsgJm5ic3A7
ICZuYnNwO2NlcnRpZmljYXRlLiAmbHQ7bmV3Jmd0OyBJZiBhIGZpbmdlcnByaW50IGNhbGN1bGF0
ZWQgdXNpbmcgdGhlIMK5U0hBLTI1NsK5PGJyPg0KJmd0O2hhc2g8YnI+DQomZ3Q7ZnVuY3Rpb24g
aXMgcHJlc2VudCwgdGhlIGVuZHBvaW50IE1VU1QgYmUgYWJsZSB0byBtYXRjaCBpdCAmbHQ7L25l
dyZndDsuIElmPGJyPg0KJmd0O3RoZXJlIGlzIG5vIG1hdGNoLCB0aGU8YnI+DQomZ3Q7ZW5kcG9p
bnQgTVVTVCBOT1QgZXN0YWJsaXNoIHRoZSBUTFMgY29ubmVjdGlvbi4gSW4gYWRkaXRpb24sIHRo
ZSBlbmRwb2ludDxicj4NCiZndDtNQVkgYWxzbyBjaGVjazxicj4NCiZndDsmbmJzcDsgJm5ic3A7
ICZuYnNwO2ZpbmdlcnByaW50cyBjYWxjdWxhdGVkIHVzaW5nIG90aGVyIGhhc2ggZnVuY3Rpb25z
IHRoYXQgaXQgaGFzPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7cmVjZWl2ZWQgZm9yIGEg
bWF0Y2guIEZvciBlYWNoIGhhc2ggZnVuY3Rpb24gY2hlY2tlZCwgb25lIG9mIHRoZTxicj4NCiZn
dDsmbmJzcDsgJm5ic3A7ICZuYnNwO3JlY2VpdmVkIGZpbmdlcnByaW50cyBNVVNUIG1hdGNoIHRo
ZSB1c2VkIGNlcnRpZmljYXRlLjxicj4NCiZndDs8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJz
cDtOT1RFOiBUaGUgU0RQIGZpbmdlcnByaW50IGF0dHJpYnV0ZSBkb2VzIG5vdCBjb250YWluIGEg
cmVmZXJlbmNlIHRvPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7YSBzcGVjaWZpYyBjZXJ0
aWZpY2F0ZS4gRW5kcG9pbnRzIG5lZWQgdG8gY29tcGFyZSB0aGUgZmluZ2VycHJpbnQ8YnI+DQom
Z3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDt3aXRoIGEgY2VydGlmaWNhdGUgaGFzaCBpbiBvcmRlciB0
byBsb29rIGZvciBhIG1hdGNoLjxicj4NCiZndDs8YnI+DQomZ3Q7LS0tLS08YnI+DQomZ3Q7PGJy
Pg0KJmd0O1JlZ2FyZHMsPGJyPg0KJmd0Ozxicj4NCiZndDtDaHJpc3Rlcjxicj4NCiZndDs8YnI+
DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDtfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXzxicj4NCiZndDttbXVzaWMgbWFpbGluZyBsaXN0PGJyPg0KJmd0Ozxh
IGhyZWY9Im1haWx0bzptbXVzaWNAaWV0Zi5vcmciPm1tdXNpY0BpZXRmLm9yZzwvYT48YnI+DQom
Z3Q7PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMi
IHJlbD0ibm9yZWZlcnJlciIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbW11c2ljPC9hPjxicj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjxicj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_7594FB04B1934943A5C02806D1A2204B37FF0C94ESESSMB209erics_--


From nobody Thu May 26 13:01:56 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60A0012D996; Thu, 26 May 2016 13:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wGv0GwIjDk3; Thu, 26 May 2016 13:01:43 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD58012D970; Thu, 26 May 2016 13:01:40 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-a7-574756226731
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id F0.1A.12926.22657475; Thu, 26 May 2016 22:01:38 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0294.000; Thu, 26 May 2016 22:01:38 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AdG3iWsAcXNHXXrjTfakEZTp6P/ejw==
Date: Thu, 26 May 2016 20:01:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FF17DEESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGIsWRmVeSWpSXmKPExsUyM2K7n65SmHu4wdd9NhYve1ayWyx/eYLR YuryxywWKzYcYHVg8fj7/gOTx7T799k8liz5yRTAHMVlk5Kak1mWWqRvl8CVcfP+TraC61kV 31s3sDUwHo/rYuTkkBAwkfi+ehkrhC0mceHeerYuRi4OIYEjjBIvG44wgSSEBJYwSmy5kNfF yMHBJmAh0f1PGyQsIuAm0dDZwwRSzwxScvXlHHaQGmEBF4klq70gajwljv6dzghh60nsffsI zGYRUJU4feoOO4jNK+ArMeP9LTYQmxHohu+n1oCtZRYQl7j1ZD4TxG0CEkv2nGeGsEUlXj7+ B3WzkkTjkiesEPX5Et0PPrBAzBSUODnzCcsERuFZSEbNQlI2C0kZRFxHYsHuT2wQtrbEsoWv mWHsMwceMyGLL2BkX8UoWpxanJSbbmSsl1qUmVxcnJ+nl5dasokRGFsHt/xW3cF4+Y3jIUYB DkYlHt4EBbdwIdbEsuLK3EOMEhzMSiK8U0Lcw4V4UxIrq1KL8uOLSnNSiw8xSnOwKInz+r9U DBcSSE8sSc1OTS1ILYLJMnFwSjUwZlelbHzRPJOVVeJ3u7hHT8/uIp6lD3JNvPcHejLa/GK0 OVFtv45z7ePzT24F9PZkitx7O+m4xfxs5aqAfbm150o+uMm3/dmkmvTZr+ZRk29Jiy630Xat HJ638466LbCRt9j+bk/crotTYgsubOWpq3t79FX86RCHzJ1zdgb8DDh5dEeZo9B9JZbijERD Leai4kQACDIrcakCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ezG_dJHq_Uma6kpDAHe5sbIi84U>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Colin Perkins \(csp@csperkins.org\)" <csp@csperkins.org>, "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>
Subject: [MMUSIC] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2016 20:01:52 -0000

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

(Sorry for the cross-posting)

Hi,

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       v=3D0
       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       s=3D-
       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=3D1153134164 1153137764
       m=3Daudio 49170 RTP/AVP 97
       a=3Drtpmap:97 iLBC/8000
       a=3Drtcp-mux

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=3Drtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=3Drtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=3Drtcp-mux"
   attribute.

Q: The question is whether it is allowed to include a=3Drtcp-mux in an answ=
er if the associated offer did NOT contain a=3Drtcp-mux.

The second last paragraph in the text above does say that, if the answer wi=
shes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=3D=
rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even i=
f it's not included in the offer? If so, how will the offerer then indicate=
 whether mux is used or not.

Regards,

Christer


--_000_7594FB04B1934943A5C02806D1A2204B37FF17DEESESSMB209erics_
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:EN-GB;}
.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">(Sorry for the cross-posting)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There has been a discussion in 3GPP regarding RFC 57=
61 (RTP/RTCP-mux).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1.1 says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">5.1.1.&nbsp; SDP Signalling<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; When the Session D=
escription Protocol (SDP) [8] is used to negotiate<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTP sessions follo=
wing the offer/answer model [9], the &quot;a=3Drtcp-mux&quot;<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute (see Sec=
tion 8) indicates the desire to multiplex RTP and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTCP onto a single=
 port.&nbsp; The initial SDP offer MUST include this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute at the m=
edia level to request multiplexing of RTP and RTCP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; on a single port.&=
nbsp; For example:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; v=3D0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; s=3D-<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; t=3D1153134164 1153137764<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; m=3Daudio 49170 RTP/AVP 97<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtpmap:97 iLBC/8000<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtcp-mux<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; This offer denotes=
 a unicast voice-over-IP session using the RTP/AVP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; profile with iLBC =
coding.&nbsp; The answerer is requested to send both RTP<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; and RTCP to port 4=
9170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answerer wi=
shes to multiplex RTP and RTCP onto a single port,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it MUST include a =
media-level &quot;a=3Drtcp-mux&quot; attribute in the answer.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; The RTP payload ty=
pes used in the answer MUST conform to the rules in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; Section 4.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answer does=
 not contain an &quot;a=3Drtcp-mux&quot; attribute, the offerer<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; MUST NOT multiplex=
 RTP and RTCP packets on a single port.&nbsp; Instead,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it should send and=
 receive RTCP on a port allocated according to the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; usual port-selecti=
on rules (either the port pair, or a signalled port<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; if the &quot;a=3Dr=
tcp:&quot; attribute [10] is also included).&nbsp; This will occur<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; when talking to a =
peer that does not understand the &quot;a=3Drtcp-mux&quot;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain a=3Drtcp-=
mux.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The second last paragraph in the text above does say=
 that, if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in=
 the answer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">BUT, in my view that is it based on the first paragr=
aph, which assumes a=3Drtcp-mux is also included in the offer.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Or, am I wrong? Is it allowed to include a=3Drtcp-mu=
x in the answer, even if it&#8217;s not included in the offer? If so, how w=
ill the offerer then indicate whether mux is used or not.<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>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B37FF17DEESESSMB209erics_--


From nobody Thu May 26 18:25:48 2016
Return-Path: <suhasietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0430B12D17D; Thu, 26 May 2016 18:25:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dq3yTZEviGH9; Thu, 26 May 2016 18:25:44 -0700 (PDT)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8104512B062; Thu, 26 May 2016 18:25:44 -0700 (PDT)
Received: by mail-yw0-x22a.google.com with SMTP id h19so93353454ywc.0; Thu, 26 May 2016 18:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=WX7i0AJ5WERbWO496YH0UZ3LLP0jydSLO7A/R2SyPZA=; b=b+iB+5DeQLdngaE/iQLYvjbN8Lm/3bUNUI25iNRBTi3WBCoKyvxP+gvZQ5ct2j6jx2 KzS//Zz/zIH5OcHzAiStwSzghGUlNsL+gKJGVazLGGx7LjumjxybeVicYkUzSE/gVFhw tGiXvBtd4QaH1bucibNQMdqUHJ44IqSC1dRIZwcHuaCbIDoFxaGX/f+H+ZAt+1zzSDXz ud1MY1lESVLEztrYSlAVRXGI+rsq1UBQfCpsdZwYbzXQxYO57qzsI9WM3LMuaKkiMxyU iVMBKy6Xpd5qYxESr7fk5DCsTsqQfpH2OsEgcRW5wX3vAazn21vVNUIK87RHzONgcOR/ aOsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=WX7i0AJ5WERbWO496YH0UZ3LLP0jydSLO7A/R2SyPZA=; b=k0106QQEAJCvZPPV1pc9aMzDbAoa1y2jk5/LlJrIRjerT4akegAuBcvQyOCYPe9+ZR LBiBPmbuZit0xtWWg8ZA6RwDHjNcfpmD4DS8a0u7nzZO/TpkaSrnMIOYcqEYK7nk5JDL OC+6t6ISC2oI8jyVrHfyrbnE2fJH57YfWc1CQvoYB8ZTwlUVbP9NZ1ja1nHk0kj1O+RL GLH5XgON+P75cV2fLDrx4F4oONCxvNQE+rLPcjLtUVw3DfP5U5ZoCc6lkBTs8vkLw1pd 03RyQ2/SA3tTuP3r66ohq7o8lg4q5TwVOjrsRP+qnrNB+QFG4LR9QSsF3+hSFsuwN1Ux GW8A==
X-Gm-Message-State: ALyK8tJHaaahrgenD+HvEAfaqycgRxY7I12ZbK+sasShrI1bGdO6d1DljA/dTLRdnXNmxRdOju/oai4OVLp6Lg==
MIME-Version: 1.0
X-Received: by 10.37.15.215 with SMTP id 206mr6826554ybp.171.1464312343636; Thu, 26 May 2016 18:25:43 -0700 (PDT)
Received: by 10.129.54.15 with HTTP; Thu, 26 May 2016 18:25:43 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se>
Date: Thu, 26 May 2016 18:25:43 -0700
Message-ID: <CAMRcRGRK2s1MrgxsoHir6cF1n6WU1FTEFEAeTJ+VPzcmS9HSHw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113f58e415328b0533c8c91f
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/ura-6H2skYl9wYKDFD7jb_ksiGM>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Colin Perkins \(csp@csperkins.org\)" <csp@csperkins.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 01:25:47 -0000

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

Going along O/A negotiation procedures, i would lean towards your former
conclusion that the offer needs to include the rtcp-mux ability.
If the offer doesn't include a=3Drtcp-mux and the answerer wants to mux ,
then it needs a new O/A from the answerer's perspectives.


If we make a=3Drtcp-mux a declarative SDP it might solve the other use-case=
 ..

thanks
Suhas

On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> (Sorry for the cross-posting)
>
>
>
> Hi,
>
>
>
> There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).
>
>
>
> Section 5.1.1 says:
>
>
>
> 5.1.1.  SDP Signalling
>
>
>
>    When the Session Description Protocol (SDP) [8] is used to negotiate
>
>    RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
>
>    attribute (see Section 8) indicates the desire to multiplex RTP and
>
>    RTCP onto a single port.  The initial SDP offer MUST include this
>
>    attribute at the media level to request multiplexing of RTP and RTCP
>
>    on a single port.  For example:
>
>
>
>        v=3D0
>
>        o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
>
>        s=3D-
>
>        c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
>
>        t=3D1153134164 1153137764
>
>        m=3Daudio 49170 RTP/AVP 97
>
>        a=3Drtpmap:97 iLBC/8000
>
>        a=3Drtcp-mux
>
>
>
>    This offer denotes a unicast voice-over-IP session using the RTP/AVP
>
>    profile with iLBC coding.  The answerer is requested to send both RTP
>
>    and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.
>
>
>
>    If the answerer wishes to multiplex RTP and RTCP onto a single port,
>
>    it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
>
>    The RTP payload types used in the answer MUST conform to the rules in
>
>    Section 4.
>
>
>
>    If the answer does not contain an "a=3Drtcp-mux" attribute, the offere=
r
>
>    MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
>
>    it should send and receive RTCP on a port allocated according to the
>
>    usual port-selection rules (either the port pair, or a signalled port
>
>    if the "a=3Drtcp:" attribute [10] is also included).  This will occur
>
>    when talking to a peer that does not understand the "a=3Drtcp-mux"
>
>    attribute.
>
>
>
> Q: The question is whether it is allowed to include a=3Drtcp-mux in an
> answer if the associated offer did NOT contain a=3Drtcp-mux.
>
>
>
> The second last paragraph in the text above does say that, if the answer
> wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.
>
>
>
> BUT, in my view that is it based on the first paragraph, which assumes
> a=3Drtcp-mux is also included in the offer.
>
>
>
> Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even=
 if
> it=E2=80=99s not included in the offer? If so, how will the offerer then =
indicate
> whether mux is used or not.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>

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

<div dir=3D"ltr">Going along O/A negotiation procedures, i would lean towar=
ds your former conclusion that the offer needs to include the rtcp-mux abil=
ity.<div>If the offer doesn&#39;t include a=3Drtcp-mux and the answerer wan=
ts to mux , then it needs a new O/A from the answerer&#39;s perspectives.<b=
r></div><div><br></div><div><br></div><div>If we make a=3Drtcp-mux a declar=
ative SDP it might solve the other use-case ..</div><div><br></div><div>tha=
nks</div><div>Suhas</div></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg <span dir=
=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_b=
lank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">





<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div>
<p class=3D"MsoNormal">(Sorry for the cross-posting)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Hi,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">There has been a discussion in 3GPP regarding RFC 57=
61 (RTP/RTCP-mux).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Section 5.1.1 says:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">5.1.1.=C2=A0 SDP Signalling<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 When the Session Description Protocol (SDP) [=
8] is used to negotiate<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 RTP sessions following the offer/answer model=
 [9], the &quot;a=3Drtcp-mux&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 attribute (see Section 8) indicates the desir=
e to multiplex RTP and<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 RTCP onto a single port.=C2=A0 The initial SD=
P offer MUST include this<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 attribute at the media level to request multi=
plexing of RTP and RTCP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 on a single port.=C2=A0 For example:<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 v=3D0<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 o=3Dcsp 1153134164 11=
53134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 s=3D-<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 c=3DIN IP6 2001:DB8::=
211:24ff:fea3:7a2e<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 t=3D1153134164 115313=
7764<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 m=3Daudio 49170 RTP/A=
VP 97<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a=3Drtpmap:97 iLBC/80=
00<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a=3Drtcp-mux<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 This offer denotes a unicast voice-over-IP se=
ssion using the RTP/AVP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 profile with iLBC coding.=C2=A0 The answerer =
is requested to send both RTP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 and RTCP to port 49170 on IPv6 address 2001:D=
B8::211:24ff:fea3:7a2e.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 If the answerer wishes to multiplex RTP and R=
TCP onto a single port,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 it MUST include a media-level &quot;a=3Drtcp-=
mux&quot; attribute in the answer.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 The RTP payload types used in the answer MUST=
 conform to the rules in<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 Section 4.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 If the answer does not contain an &quot;a=3Dr=
tcp-mux&quot; attribute, the offerer<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 MUST NOT multiplex RTP and RTCP packets on a =
single port.=C2=A0 Instead,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 it should send and receive RTCP on a port all=
ocated according to the<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 usual port-selection rules (either the port p=
air, or a signalled port<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 if the &quot;a=3Drtcp:&quot; attribute [10] i=
s also included).=C2=A0 This will occur<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 when talking to a peer that does not understa=
nd the &quot;a=3Drtcp-mux&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">=C2=A0=C2=A0 attribute.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain a=3Drtcp-=
mux.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The second last paragraph in the text above does say=
 that, if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in=
 the answer.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">BUT, in my view that is it based on the first paragr=
aph, which assumes a=3Drtcp-mux is also included in the offer.<u></u><u></u=
></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Or, am I wrong? Is it allowed to include a=3Drtcp-mu=
x in the answer, even if it=E2=80=99s not included in the offer? If so, how=
 will the offerer then indicate whether mux is used or not.<u></u><u></u></=
p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Regards,<span class=3D"HOEnZb"><font color=3D"#88888=
8"><u></u><u></u></font></span></p><span class=3D"HOEnZb"><font color=3D"#8=
88888">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Christer<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</font></span></div>
</div>

<br>_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
<br></blockquote></div><br></div>

--001a113f58e415328b0533c8c91f--


From nobody Fri May 27 00:15:55 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA0312D5D1 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 00:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWh2cCBVyXRF for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 00:15:52 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7451B12D1F0 for <mmusic@ietf.org>; Fri, 27 May 2016 00:15:51 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-61-5747f4223add
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 4B.95.27088.524F7475; Fri, 27 May 2016 09:15:49 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.03.0294.000; Fri, 27 May 2016 09:15:46 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA
Date: Fri, 27 May 2016 07:15:45 +0000
Message-ID: <D36DCF44.950D%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_D36DCF44950Dchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsUyM2K7lq7qF/dwgy2XTS2mLn/MYrFiwwFW ixkXpjI7MHv8ff+ByWPJkp9MHremFAQwR3HZpKTmZJalFunbJXBl7P2/kLXgbAtjxesPjg2M TY2MXYycHBICJhL31q1khrDFJC7cW8/WxcjFISRwhFHi1qVTjBDOEkaJ3WuuAVVxcLAJWEh0 /9MGaRARiJb48GEBE4jNLOAr8f7ndHYQW1jAXuLq5ctMEDUOEjvfXmUBmSMiMI1R4l3LCzaQ BIuAqsSNw6vBingFrCTeTDvOBLHsIbvEsQW7wBKcAn4SO3ZvArMZgc77fmoN1DZxiVtP5jNB nC0gsWTPeagXRCVePv7HCmKLCuhJ7HtxHupNRYmdZ9uZIXrjJTYdW8EMsVhQ4uTMJywTGMVm IRk7C0nZLCRls4D+ZxbQlFi/Sx+iRFFiSvdDdghbQ6J1zlwo21riUssPdmQ1Cxg5VjGKFqcW J+WmGxnppRZlJhcX5+fp5aWWbGIERu3BLb8NdjC+fO54iFGAg1GJh/dBoXu4EGtiWXFl7iFG CQ5mJRHe05+AQrwpiZVVqUX58UWlOanFhxilOViUxHn9XyqGCwmkJ5akZqemFqQWwWSZODil GhjrZ22eddJWcL3TblGe1HiHP+ueaqtXvv/aqLrpzSeG26a7lvleuOzy88pK7/1J155ypk5y bDoQtbM8p7j56aJ5ylNmZcreT7N4vNdZbnMcx8Q+OZu+pI7gb943d/66mvPh+O8V0gvZqnY/ mOn2KJ1pyoWyqP3f/XXlj3wI/7X0zxW9ln871lgvUmIpzkg01GIuKk4EAB4aXQbWAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/4aAIV00DcXyVoRSpR3zzkLSw8OE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 07:15:54 -0000

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

SGksDQoNCkRvZXMgYW55b25lIG9iamVjdCB0byDigJxTSE9VTEQgcHJvdmlkZSBhbmQgdmFsaWRh
dGUgU0hBLTI1NuKAnSwgaW5zdGVhZCBvZiBNVVNUPw0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0K
DQpGcm9tOiBtbXVzaWMgPG1tdXNpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzptbXVzaWMtYm91
bmNlc0BpZXRmLm9yZz4+IG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyA8Y2hyaXN0ZXIu
aG9sbWJlcmdAZXJpY3Nzb24uY29tPG1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5j
b20+Pg0KRGF0ZTogVGh1cnNkYXkgMjYgTWF5IDIwMTYgYXQgMTc6NTANClRvOiBSb21hbiBTaHBv
dW50IDxyb21hbkB0ZWx1cml4LmNvbTxtYWlsdG86cm9tYW5AdGVsdXJpeC5jb20+Pg0KQ2M6ICJt
bXVzaWNAaWV0Zi5vcmc8bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4iIDxtbXVzaWNAaWV0Zi5vcmc8
bWFpbHRvOm1tdXNpY0BpZXRmLm9yZz4+LCAicGt5eml2YXRAYWx1bS5taXQuZWR1PG1haWx0bzpw
a3l6aXZhdEBhbHVtLm1pdC5lZHU+IiA8cGt5eml2YXRAYWx1bS5taXQuZWR1PG1haWx0bzpwa3l6
aXZhdEBhbHVtLm1pdC5lZHU+Pg0KU3ViamVjdDogUmU6IFtNTVVTSUNdIFdHTEMgZm9yIGRyYWZ0
LWlldGYtbW11c2ljLTQ1NzItdXBkYXRlLTAzDQoNCldGTQ0KDQpTZW50IGZyb20gbXkgV2luZG93
cyBQaG9uZQ0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IFJvbWFuIFNo
cG91bnQ8bWFpbHRvOnJvbWFuQHRlbHVyaXguY29tPg0KU2VudDog4oCOMjYv4oCOMDUv4oCOMjAx
NiAxNzo0OA0KVG86IENocmlzdGVyIEhvbG1iZXJnPG1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Bl
cmljc3Nvbi5jb20+DQpDYzogTWFydGluIFRob21zb248bWFpbHRvOm1hcnRpbi50aG9tc29uQGdt
YWlsLmNvbT47IFBhdWwgS3l6aXZhdDxtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1PjsgbW11
c2ljQGlldGYub3JnPG1haWx0bzptbXVzaWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW01NVVNJ
Q10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUtMDMNCg0KSSBzdGlsbCB0
aGluayBTSEEtMjU2IHJlcXVpcmVtZW50IHNob3VsZCBiZSBhIFNIT1VMRCBub3QgYSBNVVNULg0K
DQpfX19fX19fX19fX19fDQpSb21hbiBTaHBvdW50DQoNCk9uIFRodSwgTWF5IDI2LCAyMDE2IGF0
IDU6NDEgQU0sIENocmlzdGVyIEhvbG1iZXJnIDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5j
b208bWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KQXJlIHBl
b3BsZSBvayB3aXRoIHRoaXM/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCk9uIDI1LzA1LzE2
IDEwOjExLCAibW11c2ljIG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyINCjxtbXVzaWMt
Ym91bmNlc0BpZXRmLm9yZzxtYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFs
ZiBvZiBjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb208bWFpbHRvOmNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbT4+DQp3cm90ZToNCg0KPkhpLA0KPg0KPkluIGFkZGl0aW9uIHRvIHRo
ZSB0ZXh0IGNoYW5nZSBzdWdnZXN0ZWQgYnkgTWFydGluLCBJwrl2ZSBhbHNvIGlkZW50aWZpZWQN
Cj50aGUgZm9sbG93aW5nIGNoYW5nZXMgYnkgbWFuZGF0aW5nIFNIQS0yNTYuDQo+DQo+LS0tLS0N
Cj4NCj5BYnN0cmFjdCAmIEludHJvZHVjdGlvbjoNCj4NCj5PTEQ6DQo+DQo+IlRoZSBkb2N1bWVu
dCBhbHNvIHVwZGF0ZXMgdGhlIHByZWZlcnJlZCBjaXBoZXIgc3VpdGUgdG8gYmUgdXNlZCwuLi4i
DQo+DQo+DQo+TkVXOg0KPg0KPsKzVGhlIGRvY3VtZW50IGFsc28gcmVwbGFjZXMgdGhlIHByZWZl
cnJlZCBjaXBoZXIgc3VpdGUgd2l0aCBhIG1hbmRhdGUgdG8NCj5zdXBwb3J0IGEgc3Ryb25nZXIg
Y2lwaGVyIHN1aXRlLMWgwrINCj4NCj4tLS0tLQ0KPg0KPlNlY3Rpb24gNToNCj4NCj5UaGUgY2hh
bmdlcyB0byB0aGUgY3VycmVudGx5IHN1Z2dlc3RlZCBuZXcgdGV4dCBiZXR3ZWVuIDxuZXc+IGFu
ZCA8L25ldz4uDQo+DQo+DQo+IE5FVyBURVhUOg0KPg0KPiAgICAgTXVsdGlwbGUgU0RQIGZpbmdl
cnByaW50IGF0dHJpYnV0ZXMgY2FuIGJlIGFzc29jaWF0ZWQgd2l0aCBhbiBtLQ0KPiAgICAgbGlu
ZS4gVGhpcyBjYW4gb2NjdXIgaWYgbXVsdGlwbGUgZmluZ2VycHJpbnRzIGhhdmUgYmVlbiBjYWxj
dWxhdGVkDQo+ICAgICBmb3IgYSBjZXJ0aWZpY2F0ZSB1c2luZyBkaWZmZXJlbnQgaGFzaCBmdW5j
dGlvbnMuIEl0IGNhbiBhbHNvDQo+ICAgICBvY2N1ciBpZiBvbmUgb3IgbW9yZSBmaW5nZXJwcmlu
dHMgYXNzb2NpYXRlZCB3aXRoIG11bHRpcGxlDQo+ICAgICBjZXJ0aWZpY2F0ZXMgaGF2ZSBiZWVu
IGNhbGN1bGF0ZWQuIFRoaXMgbWlnaHQgYmUgbmVlZGVkIGlmIG11bHRpcGxlDQo+ICAgICBjZXJ0
aWZpY2F0ZXMgd2lsbCBiZSB1c2VkIGZvciBtZWRpYSBhc3NvY2lhdGVkIHdpdGggYW4gbS0gbGlu
ZQ0KPiAgICAgKGUuZy4gaWYgc2VwYXJhdGUgY2VydGlmaWNhdGVzIGFyZSB1c2VkIGZvciBSVFAg
YW5kIFJUQ1ApLCBvciB3aGVyZQ0KPiAgICAgaXQgaXMgbm90IGtub3duIHdoaWNoIGNlcnRpZmlj
YXRlIHdpbGwgYmUgdXNlZCB3aGVuIHRoZQ0KPiAgICAgZmluZ2VycHJpbnRzIGFyZSBleGNoYW5n
ZWQuIEluIHN1Y2ggY2FzZXMsIG9uZSBvciBtb3JlIGZpbmdlcnByaW50cw0KPiAgICAgTVVTVCBi
ZSBjYWxjdWxhdGVkIGZvciBlYWNoIHBvc3NpYmxlIGNlcnRpZmljYXRlLiA8bmV3PkFuIGVuZHBv
aW50DQo+TVVTVCwgYXMgYSBtaW5pbXVtLCBjYWxjdWxhdGUgYSBmaW5nZXJwcmludCB1c2luZyB0
aGUgxZJTSEEtMjU2wrkNCj5oYXNoIGZ1bmN0aW9uIGZvciBlYWNoIHBvc3NpYmxlIGNlcnRpZmlj
YXRlLjwvdD4NCj4NCj4gICAgIElmIGZpbmdlcnByaW50cyBhc3NvY2lhdGVkIHdpdGggbXVsdGlw
bGUgY2VydGlmaWNhdGVzIGFyZQ0KPiAgICAgY2FsY3VsYXRlZCwgdGhlIHNhbWUgc2V0IG9mIGhh
c2ggZnVuY3Rpb25zIE1VU1QgYmUgdXNlZCB0bw0KPiAgICAgY2FsY3VsYXRlIGZpbmdlcnByaW50
cyBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSBhc3NvY2lhdGVkIHdpdGggdGhlDQo+ICAgICBtLSBsaW5l
Lg0KPg0KPiAgICAgRm9yIGVhY2ggdXNlZCBjZXJ0aWZpY2F0ZSwgYW4gZW5kcG9pbnQgTVVTVCBi
ZSBhYmxlIHRvIG1hdGNoIGF0DQo+ICAgICBsZWFzdCBvbmUgZmluZ2VycHJpbnQsIGNhbGN1bGF0
ZWQgdXNpbmcgdGhlIGhhc2ggZnVuY3Rpb24gdGhhdCB0aGUNCj4gICAgIGVuZHBvaW50IHN1cHBv
cnRzIGFuZCBjb25zaWRlcnMgbW9zdCBzZWN1cmUsIHdpdGggdGhlIHVzZWQNCj4gICAgIGNlcnRp
ZmljYXRlLiA8bmV3PiBJZiBhIGZpbmdlcnByaW50IGNhbGN1bGF0ZWQgdXNpbmcgdGhlIMK5U0hB
LTI1NsK5DQo+aGFzaA0KPmZ1bmN0aW9uIGlzIHByZXNlbnQsIHRoZSBlbmRwb2ludCBNVVNUIGJl
IGFibGUgdG8gbWF0Y2ggaXQgPC9uZXc+LiBJZg0KPnRoZXJlIGlzIG5vIG1hdGNoLCB0aGUNCj5l
bmRwb2ludCBNVVNUIE5PVCBlc3RhYmxpc2ggdGhlIFRMUyBjb25uZWN0aW9uLiBJbiBhZGRpdGlv
biwgdGhlIGVuZHBvaW50DQo+TUFZIGFsc28gY2hlY2sNCj4gICAgIGZpbmdlcnByaW50cyBjYWxj
dWxhdGVkIHVzaW5nIG90aGVyIGhhc2ggZnVuY3Rpb25zIHRoYXQgaXQgaGFzDQo+ICAgICByZWNl
aXZlZCBmb3IgYSBtYXRjaC4gRm9yIGVhY2ggaGFzaCBmdW5jdGlvbiBjaGVja2VkLCBvbmUgb2Yg
dGhlDQo+ICAgICByZWNlaXZlZCBmaW5nZXJwcmludHMgTVVTVCBtYXRjaCB0aGUgdXNlZCBjZXJ0
aWZpY2F0ZS4NCj4NCj4gICAgIE5PVEU6IFRoZSBTRFAgZmluZ2VycHJpbnQgYXR0cmlidXRlIGRv
ZXMgbm90IGNvbnRhaW4gYSByZWZlcmVuY2UgdG8NCj4gICAgIGEgc3BlY2lmaWMgY2VydGlmaWNh
dGUuIEVuZHBvaW50cyBuZWVkIHRvIGNvbXBhcmUgdGhlIGZpbmdlcnByaW50DQo+ICAgICB3aXRo
IGEgY2VydGlmaWNhdGUgaGFzaCBpbiBvcmRlciB0byBsb29rIGZvciBhIG1hdGNoLg0KPg0KPi0t
LS0tDQo+DQo+UmVnYXJkcywNCj4NCj5DaHJpc3Rlcg0KPg0KPg0KPg0KPl9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+bW11c2ljIG1haWxpbmcgbGlzdA0K
Pm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQoNCg0K

--_000_D36DCF44950Dchristerholmbergericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <5484EC45A382894687EB040D581759F0@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5IaSw8L2Rpdj4N
CjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkRvZXMgYW55b25lIG9iamVjdCB0byDigJxTSE9VTEQg
cHJvdmlkZSBhbmQgdmFsaWRhdGUgU0hBLTI1NuKAnSwgaW5zdGVhZCBvZiBNVVNUPzwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+UmVnYXJkcyw8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8ZGl2PkNocmlzdGVyPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19T
UkNfQk9EWV9TRUNUSU9OIj4NCjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7IGZvbnQt
c2l6ZToxMXB0OyB0ZXh0LWFsaWduOmxlZnQ7IGNvbG9yOmJsYWNrOyBCT1JERVItQk9UVE9NOiBt
ZWRpdW0gbm9uZTsgQk9SREVSLUxFRlQ6IG1lZGl1bSBub25lOyBQQURESU5HLUJPVFRPTTogMGlu
OyBQQURESU5HLUxFRlQ6IDBpbjsgUEFERElORy1SSUdIVDogMGluOyBCT1JERVItVE9QOiAjYjVj
NGRmIDFwdCBzb2xpZDsgQk9SREVSLVJJR0hUOiBtZWRpdW0gbm9uZTsgUEFERElORy1UT1A6IDNw
dCI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+RnJvbTogPC9zcGFuPm1tdXNpYyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOm1tdXNpYy1ib3VuY2VzQGlldGYub3JnIj5tbXVzaWMtYm91bmNl
c0BpZXRmLm9yZzwvYT4mZ3Q7IG9uIGJlaGFsZiBvZiBDaHJpc3RlciBIb2xtYmVyZyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+Y2hyaXN0ZXIuaG9s
bWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6
Ym9sZCI+RGF0ZTogPC9zcGFuPlRodXJzZGF5IDI2IE1heSAyMDE2IGF0IDE3OjUwPGJyPg0KPHNw
YW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlRvOiA8L3NwYW4+Um9tYW4gU2hwb3VudCAmbHQ7
PGEgaHJlZj0ibWFpbHRvOnJvbWFuQHRlbHVyaXguY29tIj5yb21hbkB0ZWx1cml4LmNvbTwvYT4m
Z3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPkNjOiA8L3NwYW4+JnF1b3Q7
PGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRmLm9yZyI+bW11c2ljQGlldGYub3JnPC9hPiZxdW90
OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRmLm9yZyI+bW11c2ljQGlldGYub3JnPC9h
PiZndDssICZxdW90OzxhIGhyZWY9Im1haWx0bzpwa3l6aXZhdEBhbHVtLm1pdC5lZHUiPnBreXpp
dmF0QGFsdW0ubWl0LmVkdTwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpwa3l6aXZhdEBh
bHVtLm1pdC5lZHUiPnBreXppdmF0QGFsdW0ubWl0LmVkdTwvYT4mZ3Q7PGJyPg0KPHNwYW4gc3R5
bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlN1YmplY3Q6IDwvc3Bhbj5SZTogW01NVVNJQ10gV0dMQyBm
b3IgZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUtMDM8YnI+DQo8L2Rpdj4NCjxkaXY+PGJy
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJmb250LWZhbWlseTpD
YWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0Ij5XRk08YnI+DQo8YnI+DQpTZW50IGZy
b20gbXkgV2luZG93cyBQaG9uZTwvZGl2Pg0KPC9kaXY+DQo8ZGl2IGRpcj0ibHRyIj4NCjxocj4N
CjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTox
MXB0OyBmb250LXdlaWdodDpib2xkIj5Gcm9tOg0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZh
bWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0Ij48YSBocmVmPSJtYWlsdG86
cm9tYW5AdGVsdXJpeC5jb20iPlJvbWFuIFNocG91bnQ8L2E+PC9zcGFuPjxicj4NCjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0OyBmb250
LXdlaWdodDpib2xkIj5TZW50Og0KPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxp
YnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0Ij7igI4yNi/igI4wNS/igI4yMDE2IDE3OjQ4
PC9zcGFuPjxicj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7
IGZvbnQtc2l6ZToxMXB0OyBmb250LXdlaWdodDpib2xkIj5UbzoNCjwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6MTFwdCI+PGEgaHJl
Zj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSI+Q2hyaXN0ZXIgSG9sbWJl
cmc8L2E+PC9zcGFuPjxicj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMt
c2VyaWY7IGZvbnQtc2l6ZToxMXB0OyBmb250LXdlaWdodDpib2xkIj5DYzoNCjwvc3Bhbj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyBmb250LXNpemU6MTFwdCI+
PGEgaHJlZj0ibWFpbHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbSI+TWFydGluIFRob21zb248
L2E+Ow0KPGEgaHJlZj0ibWFpbHRvOnBreXppdmF0QGFsdW0ubWl0LmVkdSI+UGF1bCBLeXppdmF0
PC9hPjsgPGEgaHJlZj0ibWFpbHRvOm1tdXNpY0BpZXRmLm9yZyI+DQptbXVzaWNAaWV0Zi5vcmc8
L2E+PC9zcGFuPjxicj4NCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2Vy
aWY7IGZvbnQtc2l6ZToxMXB0OyBmb250LXdlaWdodDpib2xkIj5TdWJqZWN0Og0KPC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7IGZvbnQtc2l6ZToxMXB0
Ij5SZTogW01NVVNJQ10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1tbXVzaWMtNDU3Mi11cGRhdGUtMDM8
L3NwYW4+PGJyPg0KPGJyPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdiBkaXI9Imx0ciI+SSBzdGlsbCB0
aGluayBTSEEtMjU2IHJlcXVpcmVtZW50IHNob3VsZCBiZSBhIFNIT1VMRCBub3QgYSBNVVNULjwv
ZGl2Pg0KPGRpdiBjbGFzcz0iZ21haWxfZXh0cmEiPjxiciBjbGVhcj0iYWxsIj4NCjxkaXY+DQo8
ZGl2IGNsYXNzPSJnbWFpbF9zaWduYXR1cmUiPl9fX19fX19fX19fX188YnI+DQpSb21hbiBTaHBv
dW50PC9kaXY+DQo8L2Rpdj4NCjxicj4NCjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj5PbiBUaHUs
IE1heSAyNiwgMjAxNiBhdCA1OjQxIEFNLCBDaHJpc3RlciBIb2xtYmVyZyA8c3BhbiBkaXI9Imx0
ciI+DQombHQ7PGEgaHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSIg
dGFyZ2V0PSJfYmxhbmsiPmNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTwvYT4mZ3Q7PC9z
cGFuPiB3cm90ZTo8YnI+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJt
YXJnaW46MCAwIDAgLjhleDsgYm9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7IHBhZGRpbmctbGVm
dDoxZXgiPg0KQXJlIHBlb3BsZSBvayB3aXRoIHRoaXM/PGJyPg0KPGJyPg0KUmVnYXJkcyw8YnI+
DQo8YnI+DQpDaHJpc3Rlcjxicj4NCjxicj4NCk9uIDI1LzA1LzE2IDEwOjExLCAmcXVvdDttbXVz
aWMgb24gYmVoYWxmIG9mIENocmlzdGVyIEhvbG1iZXJnJnF1b3Q7PGJyPg0KJmx0OzxhIGhyZWY9
Im1haWx0bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZyI+bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmc8
L2E+IG9uIGJlaGFsZiBvZg0KPGEgaHJlZj0ibWFpbHRvOmNocmlzdGVyLmhvbG1iZXJnQGVyaWNz
c29uLmNvbSI+Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPC9hPiZndDs8YnI+DQp3cm90
ZTo8YnI+DQo8ZGl2IGNsYXNzPSJIT0VuWmIiPg0KPGRpdiBjbGFzcz0iaDUiPjxicj4NCiZndDtI
aSw8YnI+DQomZ3Q7PGJyPg0KJmd0O0luIGFkZGl0aW9uIHRvIHRoZSB0ZXh0IGNoYW5nZSBzdWdn
ZXN0ZWQgYnkgTWFydGluLCBJwrl2ZSBhbHNvIGlkZW50aWZpZWQ8YnI+DQomZ3Q7dGhlIGZvbGxv
d2luZyBjaGFuZ2VzIGJ5IG1hbmRhdGluZyBTSEEtMjU2Ljxicj4NCiZndDs8YnI+DQomZ3Q7LS0t
LS08YnI+DQomZ3Q7PGJyPg0KJmd0O0Fic3RyYWN0ICZhbXA7IEludHJvZHVjdGlvbjo8YnI+DQom
Z3Q7PGJyPg0KJmd0O09MRDo8YnI+DQomZ3Q7PGJyPg0KJmd0OyZxdW90O1RoZSBkb2N1bWVudCBh
bHNvIHVwZGF0ZXMgdGhlIHByZWZlcnJlZCBjaXBoZXIgc3VpdGUgdG8gYmUgdXNlZCwuLi4mcXVv
dDs8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDtORVc6PGJyPg0KJmd0Ozxicj4NCiZndDvC
s1RoZSBkb2N1bWVudCBhbHNvIHJlcGxhY2VzIHRoZSBwcmVmZXJyZWQgY2lwaGVyIHN1aXRlIHdp
dGggYSBtYW5kYXRlIHRvPGJyPg0KJmd0O3N1cHBvcnQgYSBzdHJvbmdlciBjaXBoZXIgc3VpdGUs
xaDCsjxicj4NCiZndDs8YnI+DQomZ3Q7LS0tLS08YnI+DQomZ3Q7PGJyPg0KJmd0O1NlY3Rpb24g
NTo8YnI+DQomZ3Q7PGJyPg0KJmd0O1RoZSBjaGFuZ2VzIHRvIHRoZSBjdXJyZW50bHkgc3VnZ2Vz
dGVkIG5ldyB0ZXh0IGJldHdlZW4gJmx0O25ldyZndDsgYW5kICZsdDsvbmV3Jmd0Oy48YnI+DQom
Z3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgTkVXIFRFWFQ6PGJyPg0KJmd0Ozxicj4NCiZndDsmbmJz
cDsgJm5ic3A7ICZuYnNwO011bHRpcGxlIFNEUCBmaW5nZXJwcmludCBhdHRyaWJ1dGVzIGNhbiBi
ZSBhc3NvY2lhdGVkIHdpdGggYW4gbS08YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtsaW5l
LiBUaGlzIGNhbiBvY2N1ciBpZiBtdWx0aXBsZSBmaW5nZXJwcmludHMgaGF2ZSBiZWVuIGNhbGN1
bGF0ZWQ8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtmb3IgYSBjZXJ0aWZpY2F0ZSB1c2lu
ZyBkaWZmZXJlbnQgaGFzaCBmdW5jdGlvbnMuIEl0IGNhbiBhbHNvPGJyPg0KJmd0OyZuYnNwOyAm
bmJzcDsgJm5ic3A7b2NjdXIgaWYgb25lIG9yIG1vcmUgZmluZ2VycHJpbnRzIGFzc29jaWF0ZWQg
d2l0aCBtdWx0aXBsZTxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO2NlcnRpZmljYXRlcyBo
YXZlIGJlZW4gY2FsY3VsYXRlZC4gVGhpcyBtaWdodCBiZSBuZWVkZWQgaWYgbXVsdGlwbGU8YnI+
DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtjZXJ0aWZpY2F0ZXMgd2lsbCBiZSB1c2VkIGZvciBt
ZWRpYSBhc3NvY2lhdGVkIHdpdGggYW4gbS0gbGluZTxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZu
YnNwOyhlLmcuIGlmIHNlcGFyYXRlIGNlcnRpZmljYXRlcyBhcmUgdXNlZCBmb3IgUlRQIGFuZCBS
VENQKSwgb3Igd2hlcmU8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtpdCBpcyBub3Qga25v
d24gd2hpY2ggY2VydGlmaWNhdGUgd2lsbCBiZSB1c2VkIHdoZW4gdGhlPGJyPg0KJmd0OyZuYnNw
OyAmbmJzcDsgJm5ic3A7ZmluZ2VycHJpbnRzIGFyZSBleGNoYW5nZWQuIEluIHN1Y2ggY2FzZXMs
IG9uZSBvciBtb3JlIGZpbmdlcnByaW50czxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO01V
U1QgYmUgY2FsY3VsYXRlZCBmb3IgZWFjaCBwb3NzaWJsZSBjZXJ0aWZpY2F0ZS4gJmx0O25ldyZn
dDtBbiBlbmRwb2ludDxicj4NCiZndDtNVVNULCBhcyBhIG1pbmltdW0sIGNhbGN1bGF0ZSBhIGZp
bmdlcnByaW50IHVzaW5nIHRoZSDFklNIQS0yNTbCuTxicj4NCiZndDtoYXNoIGZ1bmN0aW9uIGZv
ciBlYWNoIHBvc3NpYmxlIGNlcnRpZmljYXRlLiZsdDsvdCZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0
OyZuYnNwOyAmbmJzcDsgJm5ic3A7SWYgZmluZ2VycHJpbnRzIGFzc29jaWF0ZWQgd2l0aCBtdWx0
aXBsZSBjZXJ0aWZpY2F0ZXMgYXJlPGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7Y2FsY3Vs
YXRlZCwgdGhlIHNhbWUgc2V0IG9mIGhhc2ggZnVuY3Rpb25zIE1VU1QgYmUgdXNlZCB0bzxicj4N
CiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO2NhbGN1bGF0ZSBmaW5nZXJwcmludHMgZm9yIGVhY2gg
Y2VydGlmaWNhdGUgYXNzb2NpYXRlZCB3aXRoIHRoZTxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZu
YnNwO20tIGxpbmUuPGJyPg0KJmd0Ozxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO0ZvciBl
YWNoIHVzZWQgY2VydGlmaWNhdGUsIGFuIGVuZHBvaW50IE1VU1QgYmUgYWJsZSB0byBtYXRjaCBh
dDxicj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwO2xlYXN0IG9uZSBmaW5nZXJwcmludCwgY2Fs
Y3VsYXRlZCB1c2luZyB0aGUgaGFzaCBmdW5jdGlvbiB0aGF0IHRoZTxicj4NCiZndDsmbmJzcDsg
Jm5ic3A7ICZuYnNwO2VuZHBvaW50IHN1cHBvcnRzIGFuZCBjb25zaWRlcnMgbW9zdCBzZWN1cmUs
IHdpdGggdGhlIHVzZWQ8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtjZXJ0aWZpY2F0ZS4g
Jmx0O25ldyZndDsgSWYgYSBmaW5nZXJwcmludCBjYWxjdWxhdGVkIHVzaW5nIHRoZSDCuVNIQS0y
NTbCuTxicj4NCiZndDtoYXNoPGJyPg0KJmd0O2Z1bmN0aW9uIGlzIHByZXNlbnQsIHRoZSBlbmRw
b2ludCBNVVNUIGJlIGFibGUgdG8gbWF0Y2ggaXQgJmx0Oy9uZXcmZ3Q7LiBJZjxicj4NCiZndDt0
aGVyZSBpcyBubyBtYXRjaCwgdGhlPGJyPg0KJmd0O2VuZHBvaW50IE1VU1QgTk9UIGVzdGFibGlz
aCB0aGUgVExTIGNvbm5lY3Rpb24uIEluIGFkZGl0aW9uLCB0aGUgZW5kcG9pbnQ8YnI+DQomZ3Q7
TUFZIGFsc28gY2hlY2s8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtmaW5nZXJwcmludHMg
Y2FsY3VsYXRlZCB1c2luZyBvdGhlciBoYXNoIGZ1bmN0aW9ucyB0aGF0IGl0IGhhczxicj4NCiZn
dDsmbmJzcDsgJm5ic3A7ICZuYnNwO3JlY2VpdmVkIGZvciBhIG1hdGNoLiBGb3IgZWFjaCBoYXNo
IGZ1bmN0aW9uIGNoZWNrZWQsIG9uZSBvZiB0aGU8YnI+DQomZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJz
cDtyZWNlaXZlZCBmaW5nZXJwcmludHMgTVVTVCBtYXRjaCB0aGUgdXNlZCBjZXJ0aWZpY2F0ZS48
YnI+DQomZ3Q7PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7Tk9URTogVGhlIFNEUCBmaW5n
ZXJwcmludCBhdHRyaWJ1dGUgZG9lcyBub3QgY29udGFpbiBhIHJlZmVyZW5jZSB0bzxicj4NCiZn
dDsmbmJzcDsgJm5ic3A7ICZuYnNwO2Egc3BlY2lmaWMgY2VydGlmaWNhdGUuIEVuZHBvaW50cyBu
ZWVkIHRvIGNvbXBhcmUgdGhlIGZpbmdlcnByaW50PGJyPg0KJmd0OyZuYnNwOyAmbmJzcDsgJm5i
c3A7d2l0aCBhIGNlcnRpZmljYXRlIGhhc2ggaW4gb3JkZXIgdG8gbG9vayBmb3IgYSBtYXRjaC48
YnI+DQomZ3Q7PGJyPg0KJmd0Oy0tLS0tPGJyPg0KJmd0Ozxicj4NCiZndDtSZWdhcmRzLDxicj4N
CiZndDs8YnI+DQomZ3Q7Q2hyaXN0ZXI8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+
DQomZ3Q7X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+
DQomZ3Q7bW11c2ljIG1haWxpbmcgbGlzdDxicj4NCiZndDs8YSBocmVmPSJtYWlsdG86bW11c2lj
QGlldGYub3JnIj5tbXVzaWNAaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OzxhIGhyZWY9Imh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljIiByZWw9Im5vcmVmZXJyZXIiIHRh
cmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21tdXNp
YzwvYT48YnI+DQo8YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
YnI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvc3Bhbj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_D36DCF44950Dchristerholmbergericssoncom_--


From nobody Fri May 27 02:10:09 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA73C12D4FF for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 02:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7n8nJpvIJRuF for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 02:10:07 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CF9512D0ED for <mmusic@ietf.org>; Fri, 27 May 2016 02:10:06 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-cc-57480eec2d6c
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 70.CE.12926.CEE08475; Fri, 27 May 2016 11:10:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0294.000; Fri, 27 May 2016 11:10:04 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AdG3iWsAcXNHXXrjTfakEZTp6P/ejwAduMUA
Date: Fri, 27 May 2016 09:10:03 +0000
Message-ID: <D36DEA2E.952D%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.19]
Content-Type: multipart/mixed; boundary="_004_D36DEA2E952Dchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKIsWRmVeSWpSXmKPExsUyM2K7se4bPo9wg10rtSymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAc79jAWLCqumH/4L1sD49q0LkZODgkBE4nfB9exQdhiEhfu rQezhQSOMEpMvS3WxcgFZC9hlFjy8QVLFyMHB5uAhUT3P22QGhEBdYmve3uYQWxhgRCJG7u3 sIKUiAiEStx+Jg1RYiTRfK6ZEcRmEVCVWPm4GaycV8BK4ve0KUwQq3wl/i7YDFbDKeAn8Whr MzuIzQh0zvdTa8BqmAXEJW49mc8EcaaIxMOLp6FOFpV4+fgfK4gtKqAnse/FeUaIuKJE+9MG RojeSIlVt++xQewVlDg58wnLBEbRWUjGzkJSNgtJGUQ8XuLByResELaBxPtz85khbG2JZQtf Q9n6Ehu/nGWEsK0lTt77hUWNrsSR88fYIWxFibbtzUC7uIDsFYwS3/9fYYNr3nMDrmhK90P2 BYx8qxhFi1OLk3LTjYz1Uosyk4uL8/P08lJLNjECE8DBLb9VdzBefuN4iFGAg1GJh/dBoXu4 EGtiWXFl7iFGFaA5jzasvsAoxZKXn5eqJMLby+QRLsSbklhZlVqUH19UmpNafIhRmoNFSZzX /6ViuJBAemJJanZqakFqEUyWiYNTqoGxNXhmfoiPzYmEupU1E1x97i7lZ14kFbB6peojx618 KtuyL08SzGrb+fcG/0vz4oxiPt0fW/86dOYEKrwpjXieIGM7/e/UybvXP1T53ZYpc3hRlYnm yz11pgvdLLdZvNMq2V0fFztzJt9Uwf/X22/e3xi77VXDdpE/EzPmfbvx/1hr4m2fKL8rSizF GYmGWsxFxYkA6qgvzAgDAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-hPeSW3i310jybR_IgqeHyK4GrM>
Subject: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 09:10:09 -0000

--_004_D36DEA2E952Dchristerholmbergericssoncom_
Content-Type: multipart/alternative;
	boundary="_000_D36DEA2E952Dchristerholmbergericssoncom_"

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


(Sorry for the cross-posting)

Hi,

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       v=3D0
       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       s=3D-
       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=3D1153134164 1153137764
       m=3Daudio 49170 RTP/AVP 97
       a=3Drtpmap:97 iLBC/8000
       a=3Drtcp-mux

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=3Drtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=3Drtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=3Drtcp-mux"
   attribute.

Q: The question is whether it is allowed to include a=3Drtcp-mux in an answ=
er if the associated offer did NOT contain a=3Drtcp-mux.

The second last paragraph in the text above does say that, if the answer wi=
shes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=3D=
rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even i=
f it=92s not included in the offer? If so, how will the offerer then indica=
te whether mux is used or not.

Regards,

Christer


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:EN-GB;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">(Sorry for the cross-posting)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There has been a discussion in 3GPP regarding RFC 57=
61 (RTP/RTCP-mux).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1.1 says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">5.1.1.&nbsp; SDP Signalling<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; When the Session D=
escription Protocol (SDP) [8] is used to negotiate<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTP sessions follo=
wing the offer/answer model [9], the &quot;a=3Drtcp-mux&quot;<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute (see Sec=
tion 8) indicates the desire to multiplex RTP and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTCP onto a single=
 port.&nbsp; The initial SDP offer MUST include this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute at the m=
edia level to request multiplexing of RTP and RTCP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; on a single port.&=
nbsp; For example:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; v=3D0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; s=3D-<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; t=3D1153134164 1153137764<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; m=3Daudio 49170 RTP/AVP 97<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtpmap:97 iLBC/8000<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtcp-mux<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; This offer denotes=
 a unicast voice-over-IP session using the RTP/AVP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; profile with iLBC =
coding.&nbsp; The answerer is requested to send both RTP<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; and RTCP to port 4=
9170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answerer wi=
shes to multiplex RTP and RTCP onto a single port,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it MUST include a =
media-level &quot;a=3Drtcp-mux&quot; attribute in the answer.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; The RTP payload ty=
pes used in the answer MUST conform to the rules in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; Section 4.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answer does=
 not contain an &quot;a=3Drtcp-mux&quot; attribute, the offerer<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; MUST NOT multiplex=
 RTP and RTCP packets on a single port.&nbsp; Instead,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it should send and=
 receive RTCP on a port allocated according to the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; usual port-selecti=
on rules (either the port pair, or a signalled port<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; if the &quot;a=3Dr=
tcp:&quot; attribute [10] is also included).&nbsp; This will occur<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; when talking to a =
peer that does not understand the &quot;a=3Drtcp-mux&quot;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain a=3Drtcp-=
mux.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The second last paragraph in the text above does say=
 that, if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in=
 the answer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">BUT, in my view that is it based on the first paragr=
aph, which assumes a=3Drtcp-mux is also included in the offer.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Or, am I wrong? Is it allowed to include a=3Drtcp-mu=
x in the answer, even if it=92s not included in the offer? If so, how will =
the offerer then indicate whether mux is used or not.<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>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D36DEA2E952Dchristerholmbergericssoncom_--

--_004_D36DEA2E952Dchristerholmbergericssoncom_
Content-Type: text/plain; name="ATT00001.txt"
Content-Description: ATT00001.txt
Content-Disposition: attachment; filename="ATT00001.txt"; size=146;
	creation-date="Fri, 27 May 2016 09:10:03 GMT";
	modification-date="Fri, 27 May 2016 09:10:03 GMT"
Content-ID: <B4A30DA5079F5B4A87EF0DD21C57CB24@ericsson.com>
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkF1ZGlvL1Zp
ZGVvIFRyYW5zcG9ydCBDb3JlIE1haW50ZW5hbmNlDQphdnRAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQo=

--_004_D36DEA2E952Dchristerholmbergericssoncom_--


From nobody Fri May 27 02:53:54 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D951812D61B for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 02:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 QyhjYEVdTYls for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 02:53:51 -0700 (PDT)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9173812D1D7 for <mmusic@ietf.org>; Fri, 27 May 2016 02:53:51 -0700 (PDT)
Received: by mail-qk0-x230.google.com with SMTP id x7so75730299qkd.3 for <mmusic@ietf.org>; Fri, 27 May 2016 02:53:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=abXCB2voo6PF0vXzy/rQFaHWu96VZCuPrsYejD7QsAI=; b=NLn6LqlVt8nTMNudlL5w908uW6bCbJ88TrTEDajxNBt6olqkbDA83t94NscEkr+TZG RoYnyAcyXAn/JfG5macPGXlJDt5lACqPWgjgOAA/+VvT+ZRiaEdfHgsW6UgGLGAbcj9k nn7Fw7X2yK47ZdG64JJ+UGtHR3i64ikDNk9/z8tTZDJW/ljlwlGuonW3XpwpvCBo5p+q B0DRNWDyQP2eFyntmT3pGHl72sTn0QBDYWM5qOGOvKJ2MSfGU5iiZfNZzzGbe+0hTuao g+PsTglRNctR4nL1qhZFew+r0zQyBFzTPapMEUgRsAdbt13S/InKE08OuYFLYhGLEPRJ MGKQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=abXCB2voo6PF0vXzy/rQFaHWu96VZCuPrsYejD7QsAI=; b=d+GZdkKUyXSRL2cAUwPkGvXT01oE8Mk+qbmxOEloK2zn9ZClCM0bzSby2XC2RO9gjh bGj8wMI/UZaANCZnw3bB9t8cPSN/IxXo57B9mkSOQtPLeNdGqkJSCKCE0K49R8qKorl/ xR2cFcZeNyg1FjuDi8T9pBey3noXD9Z2FK8G/hlp1jvOFv5d2Bs5ybDhkk1EREskT2n8 EULX/0wwUg+UdawQh70tGdkbqOo/QAFlbybKpJH2/r70pXUz045vE1wzhcRPs4k7thct 0+KRKEvoFs/BrslspBD6ILmCZZEdhpQE+hJ1w2Ti062IjRbBnG25ciJwRTxUFVPnYu6B DamQ==
X-Gm-Message-State: ALyK8tJZP5FA5yGj9MJbzNYeH/IhSn5az6LnrhFZSmNdCimQsVvrL7RcZVjnfmnbqEPlcjIOVp6RkuDc2zz0cw==
MIME-Version: 1.0
X-Received: by 10.237.42.194 with SMTP id t60mr4762013qtd.40.1464342830759; Fri, 27 May 2016 02:53:50 -0700 (PDT)
Received: by 10.140.104.110 with HTTP; Fri, 27 May 2016 02:53:50 -0700 (PDT)
In-Reply-To: <D36DCF44.950D%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com>
Date: Fri, 27 May 2016 19:53:50 +1000
Message-ID: <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/kqs9SqCQKQ0S4VzcHGyh3yIFAHM>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 09:53:53 -0000

On 27 May 2016 at 17:15, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Does anyone object to =E2=80=9CSHOULD provide and validate SHA-256=E2=80=
=9D, instead of
> MUST?


What would we say about the reasons for not following this advice?


From nobody Fri May 27 03:13:40 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F3F12D5C0 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 03:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yc3IlCRPbMjX for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 03:13:38 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CEEF12B010 for <mmusic@ietf.org>; Fri, 27 May 2016 03:13:37 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-2e-57481dcfe78e
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E9.EB.12926.FCD18475; Fri, 27 May 2016 12:13:35 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC006.ericsson.se ([153.88.183.36]) with mapi id 14.03.0294.000; Fri, 27 May 2016 12:13:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4Lw==
Date: Fri, 27 May 2016 10:13:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com>, <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com>
In-Reply-To: <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FF3B58ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBIsWRmVeSWpSXmKPExsUyM2K7iu55WY9wg6n/dC2unfnHaDF1+WMW ixUbDrBazLgwldmBxePv+w9MHjtn3WX3WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBkrW04y FtySqthy/ix7A+NT8S5GDg4JAROJn8fruhg5gUwxiQv31rN1MXJxCAkcYZToOPcaylnCKPH2 5CU2kAY2AQuJ7n/aIA0iAroSi84+YAexmQWKJJoWbGYBsYUF7CU2PrnDBFHjILHz7VUWkDki AssYJTZfmQqWYBFQlej7PwGsmVfAV+LQtVcsEMuuc0g8O9/BCpLgFAiUWN76AayBEei876fW MEFsE5do+rKSFeJsAYkle84zQ9iiEi8f/2OFqMmX2PRmHzPEAkGJkzOfsExgFJmFpH0WkrJZ SMog4gYSX97fhrK1JZYtfM0MYetLdL8/zYQsvoCRfRWjaHFqcVJuupGxXmpRZnJxcX6eXl5q ySZGYPwd3PJbdQfj5TeOhxgFOBiVeHgfFLqHC7EmlhVX5h5ilOBgVhLhvSfjES7Em5JYWZVa lB9fVJqTWnyIUZqDRUmc1/+lYriQQHpiSWp2ampBahFMlomDU6qBUYdzh+xk4ZWxMpeYbS1W yzDbRuyTPapt2VAu+yWg0yY54W721PBNPL4qm3Vu3bp4Kz13R/3npY2pDziOxQuG3ujgXjeD q1vivczE+OadFV2WKnPKYnJYF333ZIo01AnLLNkwR3jtbuml8bEbmfb22mzelVmnoHnomi9/ 0MroVW/9LGXsI5OUWIozEg21mIuKEwF/7/nouwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/-3CQdvkyOIsooBsC2_qQoALNqqI>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 10:13:40 -0000

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

We say what we normally say when we use SHOULD: nothing.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Martin Thomson<mailto:martin.thomson@gmail.com>
Sent: =FD27/=FD05/=FD2016 12:53
To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>
Cc: Roman Shpount<mailto:roman@telurix.com>; mmusic@ietf.org<mailto:mmusic@=
ietf.org>; Paul Kyzivat<mailto:pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03

On 27 May 2016 at 17:15, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> Does anyone object to =93SHOULD provide and validate SHA-256=94, instead =
of
> MUST?


What would we say about the reasons for not following this advice?

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">We say what w=
e normally say when we use SHOULD: nothing.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:martin.thomson@gmail.com">Martin Thomson</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD27=
/=FD05/=FD2016 12:53</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a></span><b=
r>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:roman@telurix.com">Roman Shpount</a>;
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>; <a href=3D"mailto:p=
kyzivat@alum.mit.edu">
Paul Kyzivat</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03</span><br>
<br>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">On 27 May 2016 at 17:15, Christer Holmberg<br>
&lt;christer.holmberg@ericsson.com&gt; wrote:<br>
&gt; Does anyone object to =93SHOULD provide and validate SHA-256=94, inste=
ad of<br>
&gt; MUST?<br>
<br>
<br>
What would we say about the reasons for not following this advice?<br>
</div>
</span></font>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B37FF3B58ESESSMB209erics_--


From nobody Fri May 27 03:55:25 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF8012D8E7 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 03:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMpD-DNpiS4G for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 03:55:22 -0700 (PDT)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2FB112D820 for <mmusic@ietf.org>; Fri, 27 May 2016 03:55:21 -0700 (PDT)
Received: by mail-qg0-x236.google.com with SMTP id e93so48958118qgf.2 for <mmusic@ietf.org>; Fri, 27 May 2016 03:55:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=lswFrrqyRXvFcFSr4ocVwdhDUxoQnrcPUeURju8G7cg=; b=B6oTe/Y/My+WTaBGPAeR6w9Xj5/VzIKzwO1eqhgVHGCc5H+8dWETcXZPZsq5CbY3gP +vHMLsElX1M+athwukAvXv4E02eTkN2y5f3j0ORLt+ZShryQh7SGs1Skjjk1y5B8jveO MvFrnbEXaqsaMSpRJuPLPzsBGLrmqSj8V6Drp3J6BqosjK2AFpBcON42qHOCsVhuerqb WpzBpRQZZiBRCCQhMH+jjmFUb2hPcUX8LM2vf0D1dY+jSKXLJaRJj4o+y048hEWLgiUR qwPe96DXCHQucZESo2NtabzUMqA+JkzLvnZ+gHuFuFLotKJqQ93TdnlXSFPcxaLn4k7B BEzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=lswFrrqyRXvFcFSr4ocVwdhDUxoQnrcPUeURju8G7cg=; b=M2F2UPm52+oIxFz51ZjchGpDhteWwzG4PAQTnSHA0rwg8ZJ4MFvLnVz+jLJnRJ2BWF 0esZwpPUwAqQF4ntE2HUtfgND3chXXiVR5h3OOOLvVJ0T36lTblFMZwZ7BekSsHJYs/B sFJ5tUDUoHlaL3DDGWs1WUhV8xPCC7EFnPgXpugr7mw3vveBlWkqNzcS1JlZxYIgVPBR 7277qrZDuYK16EEOIvJdCreD1IADmHD9U/I6Go6e7L2yBsqrmshV5M8v8LsKtThNmrjg YTNnYBB71APnUqCCm4Pt2A1wzkFs/gG73zBLr/bpF8rDpU2aUnf5oesZH04BXU0yYlBs j2Uw==
X-Gm-Message-State: ALyK8tIbfNEyIGk0XLiOpoGXE2POlPd9eM0AyxHueeqVN2NHoRmrTrXWwz76WxiOp8SsvygHIv1vovavrmBCBw==
MIME-Version: 1.0
X-Received: by 10.140.38.145 with SMTP id t17mr12609145qgt.10.1464346521017; Fri, 27 May 2016 03:55:21 -0700 (PDT)
Received: by 10.140.104.110 with HTTP; Fri, 27 May 2016 03:55:20 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se>
Date: Fri, 27 May 2016 20:55:20 +1000
Message-ID: <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/CRpnvoIwOQ-lFkElPGSA_xzvhhw>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 10:55:24 -0000

On 27 May 2016 at 20:13, Christer Holmberg
<christer.holmberg@ericsson.com> wrote:
> We say what we normally say when we use SHOULD: nothing.

That's singularly unhelpful.  Presumably when we decided that a SHOULD
was necessary, we established at least one valid reason that a MUST
wouldn't do.  You see, though Roman is saying that he doesn't want a
MUST, I'm not seeing an actual reason for it not to be.


From nobody Fri May 27 04:09:57 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB3012D17F for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 04:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyqPo2FgDrfs for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 04:09:54 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCDB912B006 for <mmusic@ietf.org>; Fri, 27 May 2016 04:09:53 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-d7-57482aff7c98
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.183.54]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 09.B0.18043.FFA28475; Fri, 27 May 2016 13:09:52 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.03.0294.000; Fri, 27 May 2016 13:09:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYA=
Date: Fri, 27 May 2016 11:09:50 +0000
Message-ID: <D36E05CF.9553%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com>
In-Reply-To: <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.3.160329
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <131E48F2207F284CA80673FBDED53D6D@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAIsWRmVeSWpSXmKPExsUyM2K7mS6Dtke4wfeHvBbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsErowvDevY C/6xVRzf/Zi1gfEkaxcjJ4eEgInE0/d/mSFsMYkL99azdTFycQgJHGGU+NLxiBnCWcIocfrG GaAODg42AQuJ7n/aIA0iAroSi84+YAexmQWKJJoWbGYBsYUF7CWuXr7MBFHjILHz7VUWkDki ApsYJW62n2YESbAIqEo8/fwJrIFXwErifvcxRohlTzglFq1ZxQ6yjFMgUOJNN9iljEDXfT+1 hglimbjErSfzmSCuFpBYsuc81AeiEi8f/wOrFxXQk9j34jwjRFxR4uOrfYwQvQYS78/NZ4aw rSWuPbsIZWtLLFv4mhniHkGJkzOfsExglJiFZN0sJO2zkLTPQtI+C0n7AkbWVYyixanFxbnp RkZ6qUWZycXF+Xl6eaklmxiB8Xpwy2+rHYwHnzseYhTgYFTi4X1Q6B4uxJpYVlyZe4hRgoNZ SYS3TdMjXIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv/0vFcCGB9MSS1OzU1ILUIpgsEwenVANj 7o/oc13TuaScWGacmf91Rdm5wqQ9/7MvB2fUZV1O5v8//XjSryt8XRJNG1nyDHZOXJV0v+JL w9Vbgv9rOg8K+Pp06xwt7Zf5HzDhosxe1r8Gwl0eHAayIZ0f+Bh23WtTYrq8JytEROL/y3x7 3ZA93z+0bkuvyM7/+ebjhBlda2Iuzpzr+OauEktxRqKhFnNRcSIAs80rZdMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/bA7JAnlVTzPlAtnfnB-FlzUCjJU>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 11:09:55 -0000

Hi,

I agree that, when one uses SHOULD, there needs to be text clarifying when
it doesn=B9t apply.

But, that doesn=B9t always happen, and sometimes it=B9s because people don=
=B9t
know when it doesn=B9t apply - they just feel that there may be a case (now
or later) where it doesn=B9t apply=8A

Having said that, asking Roman for justification is fair.

Regards,

Christer



On 27/05/16 13:55, "Martin Thomson" <martin.thomson@gmail.com> wrote:

>On 27 May 2016 at 20:13, Christer Holmberg
><christer.holmberg@ericsson.com> wrote:
>> We say what we normally say when we use SHOULD: nothing.
>
>That's singularly unhelpful.  Presumably when we decided that a SHOULD
>was necessary, we established at least one valid reason that a MUST
>wouldn't do.  You see, though Roman is saying that he doesn't want a
>MUST, I'm not seeing an actual reason for it not to be.


From nobody Fri May 27 07:35:57 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76C7312DB0E for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 07:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g-e75T-vbbe9 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 07:35:51 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C01112D6BC for <mmusic@ietf.org>; Fri, 27 May 2016 07:35:45 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id e62so115249980ita.1 for <mmusic@ietf.org>; Fri, 27 May 2016 07:35:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=nP7laqWFDTISA9rrPUynue961dZd52V1GkpJ27QTbY8=; b=MCNlIlDflyQuhc7FDIfKVVON+IwRe9FN3hgq8XxcsNBu+53i+vO2vkin2khv6iqT3r 4f31iE/t/1m/M2LOiOT7HjKY/JxSYzAgD0qFsbyIqK0kmkChieyuUDMy7gV3+FzNrbRf 2XDvI7Qo6epDb4NoPBNEoSfkwPz4B2QzUXwrT3D/umcwsIVo0pr/UpE+n+tlSiaU9M9a IslhYZWhVB9FhuMcbcAkBb08ub4O3bxPcHBWAjcg4EMEMXfQqrnZ8tm3T+4D8EDVh1GU SLWmO5KoCgTUuhVDHtKB+GftjqJjkLRDkf6jD+dDoy3DGqSrDyySKRubWvFM+ecpuvdU 6clQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=nP7laqWFDTISA9rrPUynue961dZd52V1GkpJ27QTbY8=; b=RCOWCcvQqB0NqYoymX4qrYr/6IF1MsuW2aGkJnzgk1VhofkNNuGdnmoC1MIit4cLM2 NE87txYUBnwiO36hI0qsgXhKbkFWEciAeOKoKGdFEif9ZSw1I72lMbSc3T5/UEQ5Rw/F atEbJIftp9ysLhOFH7hgMTm30wiBVUi9w04pxCPXPd2sfTicVsUUl0gahHO7teeXRTp+ GKinAxeUwjfsly6JVSI+VLv0dx8AaBx9m4rofmsDdK6nU2QI7Scqo12GDzGWTBwB5mBS FxwV2WNV+xkug55v1kjHxxN+ycj05aXhSRh8YSkqW6TsSt2zSbWpaXyqgXVwhQDcolTV AEkQ==
X-Gm-Message-State: ALyK8tIYekXlVK8WV6chHt9PaHdoqnld9GXVAtDwdjBtE5BtEyn/Txho39EN8ss+4zYq9g==
X-Received: by 10.36.50.82 with SMTP id j79mr9002970ita.27.1464359744488; Fri, 27 May 2016 07:35:44 -0700 (PDT)
Received: from mail-ig0-f181.google.com (mail-ig0-f181.google.com. [209.85.213.181]) by smtp.gmail.com with ESMTPSA id gv9sm2746551igb.4.2016.05.27.07.35.43 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 May 2016 07:35:43 -0700 (PDT)
Received: by mail-ig0-f181.google.com with SMTP id z9so1943425igu.0 for <mmusic@ietf.org>; Fri, 27 May 2016 07:35:43 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.112.166 with SMTP id ir6mr2065452igb.95.1464359743333; Fri, 27 May 2016 07:35:43 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Fri, 27 May 2016 07:35:43 -0700 (PDT)
In-Reply-To: <D36E05CF.9553%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <A6AE7698-FF73-4829-BD55-3F3DA78101D0@vidyo.com> <D369D4DC.8E8B%christer.holmberg@ericsson.com> <CABkgnnXXSxYC46TajGigAyMwNvEo2sevFcAoP14Oh2jYBZEs4A@mail.gmail.com> <5C000C3B-C697-469B-93B8-C70B9E85CC24@vidyo.com> <7594FB04B1934943A5C02806D1A2204B37FE6A24@ESESSMB209.ericsson.se> <CABkgnnV30-2E9MEyeqUdb5p8mPww6e4ud3+R5dBBnYzNGc9GgQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com>
Date: Fri, 27 May 2016 10:35:43 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com>
Message-ID: <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=089e013c6cfa5336210533d3d22c
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/OhbRGP5JrHdKycWlnlTZ_r7wFfs>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 14:35:55 -0000

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

Hi Christer,

In general, requirement to always insert SHA-256 is to insure
interoperability. If the network is limited to devices only supporting more
secure hash algorithms, it would be safe not include SHA-256 if higher
security is desired.

For example, when an end point communicates with another end point for
which it is known in advance what fingerprint hash algorithms are
supported, only a single desired fingerprint can be inserted. In other
words, if an end point communicates, let's say, with Firefox version X,
which is known to support SHA-512, and end point desires higher security,
it can include only SHA-512 fingerprint.  There is no need for SHA-256.

Another example, if I design a "higher security" communication service
where I control all the end points, I can only support SHA-512 certificates
within this service and not include SHA-256.

I believe it important to have a solution which works in the described
situations and still claims standard compliance.

This is no different then requirement to support PCMU by all devices
implementing audio/video profile to insure interop (
https://tools.ietf.org/html/rfc3551#section-6), which us a SHOULD.

Regards,
_____________
Roman Shpount

On Fri, May 27, 2016 at 7:09 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> I agree that, when one uses SHOULD, there needs to be text clarifying whe=
n
> it doesn=C2=B9t apply.
>
> But, that doesn=C2=B9t always happen, and sometimes it=C2=B9s because peo=
ple don=C2=B9t
> know when it doesn=C2=B9t apply - they just feel that there may be a case=
 (now
> or later) where it doesn=C2=B9t apply=C5=A0
>
> Having said that, asking Roman for justification is fair.
>
> Regards,
>
> Christer
>
>
>
> On 27/05/16 13:55, "Martin Thomson" <martin.thomson@gmail.com> wrote:
>
> >On 27 May 2016 at 20:13, Christer Holmberg
> ><christer.holmberg@ericsson.com> wrote:
> >> We say what we normally say when we use SHOULD: nothing.
> >
> >That's singularly unhelpful.  Presumably when we decided that a SHOULD
> >was necessary, we established at least one valid reason that a MUST
> >wouldn't do.  You see, though Roman is saying that he doesn't want a
> >MUST, I'm not seeing an actual reason for it not to be.
>
>

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

<div dir=3D"ltr">Hi Christer,<div><br></div><div>In general, requirement to=
 always insert SHA-256 is to insure interoperability. If the network is lim=
ited to devices only supporting more secure hash algorithms, it would be sa=
fe not include SHA-256 if higher security is desired.<br></div><div><br></d=
iv><div>For example, when an end point communicates with another end point =
for which it is known in advance what fingerprint hash algorithms are suppo=
rted, only a single desired fingerprint can be inserted. In other words, if=
 an end point communicates, let&#39;s say, with Firefox version X, which is=
 known to support SHA-512, and end point desires higher security, it can in=
clude only SHA-512 fingerprint.=C2=A0 There is no need for SHA-256.=C2=A0</=
div><div><br></div><div>Another example, if I design a &quot;higher securit=
y&quot; communication service where I control all the end points, I can onl=
y support SHA-512 certificates within this service and not include SHA-256.=
</div><div><br></div><div>I believe it important to have a solution which w=
orks in the described situations and still claims standard compliance.=C2=
=A0</div><div><br></div><div>This is no different then requirement to suppo=
rt PCMU by all devices implementing audio/video profile to insure interop (=
<a href=3D"https://tools.ietf.org/html/rfc3551#section-6">https://tools.iet=
f.org/html/rfc3551#section-6</a>), which us a SHOULD.</div><div><br></div><=
div>Regards,</div><div class=3D"gmail_extra"><div><div class=3D"gmail_signa=
ture">_____________<br>Roman Shpount</div></div>
<br><div class=3D"gmail_quote">On Fri, May 27, 2016 at 7:09 AM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I agree that, when one uses SHOULD, there needs to be text clarifying when<=
br>
it doesn=C2=B9t apply.<br>
<br>
But, that doesn=C2=B9t always happen, and sometimes it=C2=B9s because peopl=
e don=C2=B9t<br>
know when it doesn=C2=B9t apply - they just feel that there may be a case (=
now<br>
or later) where it doesn=C2=B9t apply=C5=A0<br>
<br>
Having said that, asking Roman for justification is fair.<br>
<br>
Regards,<br>
<br>
Christer<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On 27/05/16 13:55, &quot;Martin Thomson&quot; &lt;<a href=3D"mailto:martin.=
thomson@gmail.com">martin.thomson@gmail.com</a>&gt; wrote:<br>
<br>
&gt;On 27 May 2016 at 20:13, Christer Holmberg<br>
&gt;&lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg=
@ericsson.com</a>&gt; wrote:<br>
&gt;&gt; We say what we normally say when we use SHOULD: nothing.<br>
&gt;<br>
&gt;That&#39;s singularly unhelpful.=C2=A0 Presumably when we decided that =
a SHOULD<br>
&gt;was necessary, we established at least one valid reason that a MUST<br>
&gt;wouldn&#39;t do.=C2=A0 You see, though Roman is saying that he doesn&#3=
9;t want a<br>
&gt;MUST, I&#39;m not seeing an actual reason for it not to be.<br>
<br>
</div></div></blockquote></div><br></div></div>

--089e013c6cfa5336210533d3d22c--


From nobody Fri May 27 10:00:15 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 253F112D707 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 10:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A_PyKVO8izYO for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 10:00:11 -0700 (PDT)
Received: from resqmta-ch2-10v.sys.comcast.net (resqmta-ch2-10v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFD3C12D70A for <mmusic@ietf.org>; Fri, 27 May 2016 10:00:07 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by comcast with SMTP id 6L5lbOowvpUrh6L7Hb4ucM; Fri, 27 May 2016 17:00:07 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464368407; bh=/rHAVqEjbEhyxpE0Y8agS2QUKiKotLFwvHzGVXqp9gY=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=evNqx3ss/jughMDvxW9RrgCROcTHt241hIwHw0koKW1KbW3Rzn1dv9NGSxRc/qtRl vf7FvZTv03fF/muQAQylR3rwGuyexxL7b1UH8d4kj9qdgPjQxQ776fQA9u/stDlvik w0YgQMM/u2mRlMa6DQ2YHpzhI+8Li4HPxb1EBzi4WgnRoELt+Ao+X47Ll42qhv9P69 7FlHFqO5WXXRsfAmCfmaUpRNyk2ijMGYKSmYRJL05VNXlwXSxyySvKW4MuarvcVF65 +ZXI9zjwvM6cls392AaynrgfoyUQUIj7H9sDENk8PUaF00bkpoXVfWkuE9Dq032FYP jhc/Z8dVhKKMw==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-08v.sys.comcast.net with comcast id zV061s0093KdFy101V068m; Fri, 27 May 2016 17:00:07 +0000
To: Roman Shpount <roman@telurix.com>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu>
Date: Fri, 27 May 2016 13:00:22 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/nWJGMuRdWh8Mj4B-68-Pq_zDvx8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 17:00:14 -0000

On 5/27/16 10:35 AM, Roman Shpount wrote:
> Hi Christer,
>
> In general, requirement to always insert SHA-256 is to insure
> interoperability. If the network is limited to devices only supporting
> more secure hash algorithms, it would be safe not include SHA-256 if
> higher security is desired.
>
> For example, when an end point communicates with another end point for
> which it is known in advance what fingerprint hash algorithms are
> supported, only a single desired fingerprint can be inserted. In other
> words, if an end point communicates, let's say, with Firefox version X,
> which is known to support SHA-512, and end point desires higher
> security, it can include only SHA-512 fingerprint.  There is no need for
> SHA-256.
>
> Another example, if I design a "higher security" communication service
> where I control all the end points, I can only support SHA-512
> certificates within this service and not include SHA-256.

So any valid exception will include a hash that the sender thinks is 
*stronger* than SHA-256?

This could be stated as:

"A fingerprint using the SHA-256 hash MUST/SHOULD be included except in 
cases where a fingerprint is included that uses a hash known to be 
stronger than SHA-256."

There could be additional text stating that even in that case SHA-256 
should still be included except in cases where it is known that the 
recipient will support the stronger hash.

	Thanks,
	Paul

> I believe it important to have a solution which works in the described
> situations and still claims standard compliance.
>
> This is no different then requirement to support PCMU by all devices
> implementing audio/video profile to insure interop
> (https://tools.ietf.org/html/rfc3551#section-6), which us a SHOULD.
>
> Regards,
> _____________
> Roman Shpount
>
> On Fri, May 27, 2016 at 7:09 AM, Christer Holmberg
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> wrote:
>
>     Hi,
>
>     I agree that, when one uses SHOULD, there needs to be text
>     clarifying when
>     it doesnÂ¹t apply.
>
>     But, that doesnÂ¹t always happen, and sometimes itÂ¹s because people donÂ¹t
>     know when it doesnÂ¹t apply - they just feel that there may be a case
>     (now
>     or later) where it doesnÂ¹t applyÅ 
>
>     Having said that, asking Roman for justification is fair.
>
>     Regards,
>
>     Christer
>
>
>
>     On 27/05/16 13:55, "Martin Thomson" <martin.thomson@gmail.com
>     <mailto:martin.thomson@gmail.com>> wrote:
>
>     >On 27 May 2016 at 20:13, Christer Holmberg
>     ><christer.holmberg@ericsson.com
>     <mailto:christer.holmberg@ericsson.com>> wrote:
>     >> We say what we normally say when we use SHOULD: nothing.
>     >
>     >That's singularly unhelpful.  Presumably when we decided that a SHOULD
>     >was necessary, we established at least one valid reason that a MUST
>     >wouldn't do.  You see, though Roman is saying that he doesn't want a
>     >MUST, I'm not seeing an actual reason for it not to be.
>
>


From nobody Fri May 27 10:16:11 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D13712D759 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 10:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4C5xdQgb0OD for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 10:16:08 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8585512D74F for <mmusic@ietf.org>; Fri, 27 May 2016 10:16:07 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-8a-574880d5a6e4
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 4B.3D.18043.5D088475; Fri, 27 May 2016 19:16:05 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0294.000; Fri, 27 May 2016 19:16:04 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoA///bDzA=
Date: Fri, 27 May 2016 17:16:04 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FF4A7F@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu>
In-Reply-To: <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFIsWRmVeSWpSXmKPExsUyM2J7lO7VBo9wg+8PlS2unfnHaDF1+WMW ixUbDrBazLgwldmBxePv+w9MHjtn3WX3WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBkP7z9n L+jRrFj9qo2lgbFFo4uRk0NCwERizr6NLBC2mMSFe+vZuhi5OIQEjjBKrOvvZYdwljBKLF87 lbmLkYODTcBCovufNkiDiIC3xIT5q9lAwswCIRIXjoSChIUF7CU2PrnDBFHiILHz7VUWkDEi AscYJQ5PPwGWYBFQlfix6zIziM0r4Ctx/vAsFohdKzkk2ibfZgNJcAJ1L5rwAew6RqDrvp9a A9bMLCAucevJfCaIqwUkluw5zwxhi0q8fPyPFcJWklh0+zMTxHGaEut36UO0KkpM6X7IDrFX UOLkzCcsExjFZiGZOguhYxaSjllIOhYwsqxiFC1OLS7OTTcy0kstykwuLs7P08tLLdnECIyx g1t+W+1gPPjc8RCjAAejEg/vg0L3cCHWxLLiytxDjBIczEoivC31HuFCvCmJlVWpRfnxRaU5 qcWHGKU5WJTEef1fKoYLCaQnlqRmp6YWpBbBZJk4OKUaGBfsbZ2ln526tUnujGTNBN7fshI1 Gf5nljht1Dt//ovS3Ar2w1eK139d8fZ5wKsVN8Nv1n1Y/iA9oEdjm+qbyccl06ffmqR86WTV JPuNURv1U4OOM0xflPvvqPa6vBo7gaLApk93pliV+p/KrPv+Uba3fuK3g5Fvd/Dl63Az2byb P/uvPIt8YJ8SS3FGoqEWc1FxIgB/egjPrQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/UXNE6MY0USRJUnB_ACRfAnmoW3Q>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 17:16:10 -0000

SGksDQoNClRoZXJlIGFyZSB0d28gcXVlc3Rpb25zOiB3aGF0IE1VU1QvU0hPVUxEIGJlIHNlbnQs
IGFuZCB3aGF0IE1VU1QvU0hPVUxEIGJlIHZhbGlkYXRlZC4NCg0KQXMgZmFyIGFzIHZhbGlkYXRp
b24gaXMgY29uY2VybmVkLCBJIGFtIG5vdCBzdXJlIHdoZXRoZXIgd2UgbmVlZCB0byBtYW5kYXRl
IHRoZSByZWNlaXZlciB0byB2YWxpZGF0ZSBTSEEtMjU2LiBUaGUgc3VnZ2VzdGlvbiBoYXMgYmVl
biB0aGF0IHRoZSByZWNlaXZlciBtYXRjaGVzIGEgZmluZ2VycHJpbnQgdGhhdCBpdCBjb25zaWRl
cnMgc3Ryb25nIGVub3VnaC4gDQoNCldoZXRoZXIgdGhlIHNlbmRlciBNVVNUL1NIT1VMRCBwcm92
aWRlIFNIQS0yNTYgSSBoYXZlIG5vIHN0cm9uZyBvcGluaW9uIGFib3V0Lg0KDQpSZWdhcmRzLA0K
DQpDaHJpc3Rlcg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogUGF1bCBLeXpp
dmF0IFttYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1XSANClNlbnQ6IDI3IE1heSAyMDE2IDIw
OjAwDQpUbzogUm9tYW4gU2hwb3VudCA8cm9tYW5AdGVsdXJpeC5jb20+OyBDaHJpc3RlciBIb2xt
YmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPg0KQ2M6IE1hcnRpbiBUaG9tc29u
IDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+OyBtbXVzaWNAaWV0Zi5vcmcNClN1YmplY3Q6IFJl
OiBbTU1VU0lDXSBXR0xDIGZvciBkcmFmdC1pZXRmLW1tdXNpYy00NTcyLXVwZGF0ZS0wMw0KDQpP
biA1LzI3LzE2IDEwOjM1IEFNLCBSb21hbiBTaHBvdW50IHdyb3RlOg0KPiBIaSBDaHJpc3RlciwN
Cj4NCj4gSW4gZ2VuZXJhbCwgcmVxdWlyZW1lbnQgdG8gYWx3YXlzIGluc2VydCBTSEEtMjU2IGlz
IHRvIGluc3VyZSANCj4gaW50ZXJvcGVyYWJpbGl0eS4gSWYgdGhlIG5ldHdvcmsgaXMgbGltaXRl
ZCB0byBkZXZpY2VzIG9ubHkgc3VwcG9ydGluZyANCj4gbW9yZSBzZWN1cmUgaGFzaCBhbGdvcml0
aG1zLCBpdCB3b3VsZCBiZSBzYWZlIG5vdCBpbmNsdWRlIFNIQS0yNTYgaWYgDQo+IGhpZ2hlciBz
ZWN1cml0eSBpcyBkZXNpcmVkLg0KPg0KPiBGb3IgZXhhbXBsZSwgd2hlbiBhbiBlbmQgcG9pbnQg
Y29tbXVuaWNhdGVzIHdpdGggYW5vdGhlciBlbmQgcG9pbnQgZm9yIA0KPiB3aGljaCBpdCBpcyBr
bm93biBpbiBhZHZhbmNlIHdoYXQgZmluZ2VycHJpbnQgaGFzaCBhbGdvcml0aG1zIGFyZSANCj4g
c3VwcG9ydGVkLCBvbmx5IGEgc2luZ2xlIGRlc2lyZWQgZmluZ2VycHJpbnQgY2FuIGJlIGluc2Vy
dGVkLiBJbiBvdGhlciANCj4gd29yZHMsIGlmIGFuIGVuZCBwb2ludCBjb21tdW5pY2F0ZXMsIGxl
dCdzIHNheSwgd2l0aCBGaXJlZm94IHZlcnNpb24gDQo+IFgsIHdoaWNoIGlzIGtub3duIHRvIHN1
cHBvcnQgU0hBLTUxMiwgYW5kIGVuZCBwb2ludCBkZXNpcmVzIGhpZ2hlciANCj4gc2VjdXJpdHks
IGl0IGNhbiBpbmNsdWRlIG9ubHkgU0hBLTUxMiBmaW5nZXJwcmludC4gIFRoZXJlIGlzIG5vIG5l
ZWQgDQo+IGZvciBTSEEtMjU2Lg0KPg0KPiBBbm90aGVyIGV4YW1wbGUsIGlmIEkgZGVzaWduIGEg
ImhpZ2hlciBzZWN1cml0eSIgY29tbXVuaWNhdGlvbiBzZXJ2aWNlIA0KPiB3aGVyZSBJIGNvbnRy
b2wgYWxsIHRoZSBlbmQgcG9pbnRzLCBJIGNhbiBvbmx5IHN1cHBvcnQgU0hBLTUxMiANCj4gY2Vy
dGlmaWNhdGVzIHdpdGhpbiB0aGlzIHNlcnZpY2UgYW5kIG5vdCBpbmNsdWRlIFNIQS0yNTYuDQoN
ClNvIGFueSB2YWxpZCBleGNlcHRpb24gd2lsbCBpbmNsdWRlIGEgaGFzaCB0aGF0IHRoZSBzZW5k
ZXIgdGhpbmtzIGlzDQoqc3Ryb25nZXIqIHRoYW4gU0hBLTI1Nj8NCg0KVGhpcyBjb3VsZCBiZSBz
dGF0ZWQgYXM6DQoNCiJBIGZpbmdlcnByaW50IHVzaW5nIHRoZSBTSEEtMjU2IGhhc2ggTVVTVC9T
SE9VTEQgYmUgaW5jbHVkZWQgZXhjZXB0IGluIGNhc2VzIHdoZXJlIGEgZmluZ2VycHJpbnQgaXMg
aW5jbHVkZWQgdGhhdCB1c2VzIGEgaGFzaCBrbm93biB0byBiZSBzdHJvbmdlciB0aGFuIFNIQS0y
NTYuIg0KDQpUaGVyZSBjb3VsZCBiZSBhZGRpdGlvbmFsIHRleHQgc3RhdGluZyB0aGF0IGV2ZW4g
aW4gdGhhdCBjYXNlIFNIQS0yNTYgc2hvdWxkIHN0aWxsIGJlIGluY2x1ZGVkIGV4Y2VwdCBpbiBj
YXNlcyB3aGVyZSBpdCBpcyBrbm93biB0aGF0IHRoZSByZWNpcGllbnQgd2lsbCBzdXBwb3J0IHRo
ZSBzdHJvbmdlciBoYXNoLg0KDQoJVGhhbmtzLA0KCVBhdWwNCg0KPiBJIGJlbGlldmUgaXQgaW1w
b3J0YW50IHRvIGhhdmUgYSBzb2x1dGlvbiB3aGljaCB3b3JrcyBpbiB0aGUgZGVzY3JpYmVkIA0K
PiBzaXR1YXRpb25zIGFuZCBzdGlsbCBjbGFpbXMgc3RhbmRhcmQgY29tcGxpYW5jZS4NCj4NCj4g
VGhpcyBpcyBubyBkaWZmZXJlbnQgdGhlbiByZXF1aXJlbWVudCB0byBzdXBwb3J0IFBDTVUgYnkg
YWxsIGRldmljZXMgDQo+IGltcGxlbWVudGluZyBhdWRpby92aWRlbyBwcm9maWxlIHRvIGluc3Vy
ZSBpbnRlcm9wIA0KPiAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzM1NTEjc2VjdGlv
bi02KSwgd2hpY2ggdXMgYSBTSE9VTEQuDQo+DQo+IFJlZ2FyZHMsDQo+IF9fX19fX19fX19fX18N
Cj4gUm9tYW4gU2hwb3VudA0KPg0KPiBPbiBGcmksIE1heSAyNywgMjAxNiBhdCA3OjA5IEFNLCBD
aHJpc3RlciBIb2xtYmVyZyANCj4gPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSANCj4g
PG1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+Pg0KPiB3cm90ZToNCj4NCj4g
ICAgIEhpLA0KPg0KPiAgICAgSSBhZ3JlZSB0aGF0LCB3aGVuIG9uZSB1c2VzIFNIT1VMRCwgdGhl
cmUgbmVlZHMgdG8gYmUgdGV4dA0KPiAgICAgY2xhcmlmeWluZyB3aGVuDQo+ICAgICBpdCBkb2Vz
bsK5dCBhcHBseS4NCj4NCj4gICAgIEJ1dCwgdGhhdCBkb2VzbsK5dCBhbHdheXMgaGFwcGVuLCBh
bmQgc29tZXRpbWVzIGl0wrlzIGJlY2F1c2UgcGVvcGxlIGRvbsK5dA0KPiAgICAga25vdyB3aGVu
IGl0IGRvZXNuwrl0IGFwcGx5IC0gdGhleSBqdXN0IGZlZWwgdGhhdCB0aGVyZSBtYXkgYmUgYSBj
YXNlDQo+ICAgICAobm93DQo+ICAgICBvciBsYXRlcikgd2hlcmUgaXQgZG9lc27CuXQgYXBwbHnF
oA0KPg0KPiAgICAgSGF2aW5nIHNhaWQgdGhhdCwgYXNraW5nIFJvbWFuIGZvciBqdXN0aWZpY2F0
aW9uIGlzIGZhaXIuDQo+DQo+ICAgICBSZWdhcmRzLA0KPg0KPiAgICAgQ2hyaXN0ZXINCj4NCj4N
Cj4NCj4gICAgIE9uIDI3LzA1LzE2IDEzOjU1LCAiTWFydGluIFRob21zb24iIDxtYXJ0aW4udGhv
bXNvbkBnbWFpbC5jb20NCj4gICAgIDxtYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tPj4g
d3JvdGU6DQo+DQo+ICAgICA+T24gMjcgTWF5IDIwMTYgYXQgMjA6MTMsIENocmlzdGVyIEhvbG1i
ZXJnDQo+ICAgICA+PGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbQ0KPiAgICAgPG1haWx0
bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+PiB3cm90ZToNCj4gICAgID4+IFdlIHNh
eSB3aGF0IHdlIG5vcm1hbGx5IHNheSB3aGVuIHdlIHVzZSBTSE9VTEQ6IG5vdGhpbmcuDQo+ICAg
ICA+DQo+ICAgICA+VGhhdCdzIHNpbmd1bGFybHkgdW5oZWxwZnVsLiAgUHJlc3VtYWJseSB3aGVu
IHdlIGRlY2lkZWQgdGhhdCBhIFNIT1VMRA0KPiAgICAgPndhcyBuZWNlc3NhcnksIHdlIGVzdGFi
bGlzaGVkIGF0IGxlYXN0IG9uZSB2YWxpZCByZWFzb24gdGhhdCBhIE1VU1QNCj4gICAgID53b3Vs
ZG4ndCBkby4gIFlvdSBzZWUsIHRob3VnaCBSb21hbiBpcyBzYXlpbmcgdGhhdCBoZSBkb2Vzbid0
IHdhbnQgYQ0KPiAgICAgPk1VU1QsIEknbSBub3Qgc2VlaW5nIGFuIGFjdHVhbCByZWFzb24gZm9y
IGl0IG5vdCB0byBiZS4NCj4NCj4NCg0K


From nobody Fri May 27 10:16:25 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E94512D753 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 10:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9pVNVrojida for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 10:16:16 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12F7D12D792 for <mmusic@ietf.org>; Fri, 27 May 2016 10:16:14 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id z123so429844itg.0 for <mmusic@ietf.org>; Fri, 27 May 2016 10:16:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=d0WkfJlrK/jfB7ELtmq1xeT6HucfF9NFbpyt1/kambM=; b=mEhyxFpOiBu9O2aGL4dS6a3iaGJCcVWaOSlYSAD+MVCKLcx02h6giyZmAHd98ENjXw +ceFRuhNZQlKanWCW+NrRiOeZ9GroM0gihJyLrAu20js7ki+beX6ty7QH8aHYcB58xjB 3A1qiEDQYG1IfjEFwbYnt8rp/701QCIi1KFXHXBKfWIcrYsyrsVHqx+mdeKA3xRTeOhJ hnHdw7+a/iet57gwrZ15mg+wpC7sVZHsgBK9T+rtkK2jDDB1oOhvVsAzI+/zilzKZZuH BKnD9wzYHIxUb5qp7G0IaBxybZOQIFXWzY4/nFZ5g5B1WATeURnqYVGkoIIeeDxXStWK +Zng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=d0WkfJlrK/jfB7ELtmq1xeT6HucfF9NFbpyt1/kambM=; b=LkQUQmKwTYd9qpw5wwFInDnS2u+rnW/MWQhJ45LfIOJlBfiyfIrvzOpSR+qOFechsq W7OernSb0s27O6hsYw0XpK+zH8WlQb5TDQzxFF3r50sTDTwiFFWrZOnkXqQgp+zz2k2D sAGeSlAQc8p5+zr7mL69bj4sjebo/lXb/qacAiMYYhN6MSJcmbv+zXdBEtPEdZ+ImEUL PD1Yx14gUM4cS6tx5kvDXB7qZRlOIBguC3HmH1REdF6mZG4SNV/FmcCkJE4MMIwaIoDa xEp1LmZ4dvzAXlxVDhPXXE1uVqyQV1x6FeOYIJaEAI2xF2AgiOE2hB0BLJeCBHh6AuHh 8F1Q==
X-Gm-Message-State: ALyK8tLgkshI2Il7Z8jPMFtypBXxBvUOXplHr2erxQueXdn05GfzQyYM3oanIBvpQu3ELA==
X-Received: by 10.36.130.130 with SMTP id t124mr9373103itd.42.1464369373401; Fri, 27 May 2016 10:16:13 -0700 (PDT)
Received: from mail-io0-f175.google.com (mail-io0-f175.google.com. [209.85.223.175]) by smtp.gmail.com with ESMTPSA id l123sm2928733ita.1.2016.05.27.10.16.12 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 May 2016 10:16:12 -0700 (PDT)
Received: by mail-io0-f175.google.com with SMTP id 190so76102704iow.1 for <mmusic@ietf.org>; Fri, 27 May 2016 10:16:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.160.76 with SMTP id j73mr14171300ioe.66.1464369372167; Fri, 27 May 2016 10:16:12 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Fri, 27 May 2016 10:16:12 -0700 (PDT)
In-Reply-To: <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu>
Date: Fri, 27 May 2016 13:16:12 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com>
Message-ID: <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=001a114027b83fd5af0533d61067
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/qNopBsAsiPVJdZoqUkHmyUizqb4>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 17:16:24 -0000

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

On Fri, May 27, 2016 at 1:00 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> On 5/27/16 10:35 AM, Roman Shpount wrote:
>
>> In general, requirement to always insert SHA-256 is to insure
>> interoperability. If the network is limited to devices only supporting
>> more secure hash algorithms, it would be safe not include SHA-256 if
>> higher security is desired.
>>
>> For example, when an end point communicates with another end point for
>> which it is known in advance what fingerprint hash algorithms are
>> supported, only a single desired fingerprint can be inserted. In other
>> words, if an end point communicates, let's say, with Firefox version X,
>> which is known to support SHA-512, and end point desires higher
>> security, it can include only SHA-512 fingerprint.  There is no need for
>> SHA-256.
>>
>> Another example, if I design a "higher security" communication service
>> where I control all the end points, I can only support SHA-512
>> certificates within this service and not include SHA-256.
>>
>
> So any valid exception will include a hash that the sender thinks is
> *stronger* than SHA-256?
>

If an application thinks that another hash is more appropriate and is
supported by remote application, it should be allowed to include just that
hash.

For instance, one can argue if end point knows in advance that it
communicates with a legacy end point that only supports SHA-1, there is no
reason to include SHA-256. It is also likely that this legacy end point
will only support a single fingerprint per m= line, so including both
SHA-256 and SHA-1 can prevent the connection from being setup.


> This could be stated as:
>
> "A fingerprint using the SHA-256 hash MUST/SHOULD be included except in
> cases where a fingerprint is included that uses a hash known to be stronger
> than SHA-256."
>
> There could be additional text stating that even in that case SHA-256
> should still be included except in cases where it is known that the
> recipient will support the stronger hash.
>

I think what we are trying to document here is:

1. SHA-256 or better hash SHOULD be verified for each certificate to insure
adequate security, except when communicating with legacy end points that
only provide lower quality hashes in fingerprints such as SHA-1 or MD5.

2. SHA-256 SHOULD be included to for each certificate used to insure
interoperability, unless it is known in advance that remote end point is
either legacy end point that does not support SHA-256 or remote end point
supports a better hash which needs to be forced for some reason, such as
better security.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Fri, May 27, 2016 at 1:00 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.=
edu</a>&gt;</span> wrote:<br></div></div><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wi=
dth:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-=
left:1ex"><span class=3D"">On 5/27/16 10:35 AM, Roman Shpount wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">In general, requirement to always insert SHA-256 is to ins=
ure<br>
interoperability. If the network is limited to devices only supporting<br>
more secure hash algorithms, it would be safe not include SHA-256 if<br>
higher security is desired.<br>
<br>
For example, when an end point communicates with another end point for<br>
which it is known in advance what fingerprint hash algorithms are<br>
supported, only a single desired fingerprint can be inserted. In other<br>
words, if an end point communicates, let&#39;s say, with Firefox version X,=
<br>
which is known to support SHA-512, and end point desires higher<br>
security, it can include only SHA-512 fingerprint.=C2=A0 There is no need f=
or<br>
SHA-256.<br>
<br>
Another example, if I design a &quot;higher security&quot; communication se=
rvice<br>
where I control all the end points, I can only support SHA-512<br>
certificates within this service and not include SHA-256.<br>
</blockquote>
<br></span>
So any valid exception will include a hash that the sender thinks is *stron=
ger* than SHA-256?<br></blockquote><div><br></div><div>If an application th=
inks that another hash is more appropriate and is supported by remote appli=
cation, it should be allowed to include just that hash.</div><div><br></div=
><div>For instance, one can argue if end point knows in advance that it com=
municates with a legacy end point that only supports SHA-1, there is no rea=
son to include SHA-256. It is also likely that this legacy end point will o=
nly support a single fingerprint per m=3D line, so including both SHA-256 a=
nd SHA-1 can prevent the connection from being setup.</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);=
padding-left:1ex">This could be stated as:<br>
<br>
&quot;A fingerprint using the SHA-256 hash MUST/SHOULD be included except i=
n cases where a fingerprint is included that uses a hash known to be strong=
er than SHA-256.&quot;<br>
<br>
There could be additional text stating that even in that case SHA-256 shoul=
d still be included except in cases where it is known that the recipient wi=
ll support the stronger hash.<br></blockquote><div><br></div><div>I think w=
hat we are trying to document here is:</div><div><br></div><div>1. SHA-256 =
or better hash SHOULD be verified for each certificate to insure adequate s=
ecurity, except when communicating with legacy end points that only provide=
 lower quality hashes in fingerprints such as SHA-1 or MD5.</div><div><br><=
/div><div>2. SHA-256 SHOULD be included to for each certificate used to ins=
ure interoperability, unless it is known in advance that remote end point i=
s either legacy end point that does not support SHA-256 or remote end point=
 supports a better hash which needs to be forced for some reason, such as b=
etter security.=C2=A0</div><div><div class=3D"gmail_signature">____________=
_<br>Roman Shpount</div></div><div>=C2=A0</div></div></div></div>

--001a114027b83fd5af0533d61067--


From nobody Fri May 27 12:05:10 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E357E12DC95 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 12:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ROYeu_krbjAl for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 12:05:07 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C41CB12D841 for <mmusic@ietf.org>; Fri, 27 May 2016 12:05:05 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-27-57489a5f61c5
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 3F.1E.12926.F5A98475; Fri, 27 May 2016 21:05:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.152]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0294.000; Fri, 27 May 2016 21:05:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoAgAAEbAD//8AqMA==
Date: Fri, 27 May 2016 19:05:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com>
In-Reply-To: <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B37FF4E53ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrEIsWRmVeSWpSXmKPExsUyM2K7jW7CLI9wg9VPGC2unfnHaDF1+WMW ixUbDrBazLgwldmBxePv+w9MHjtn3WX3WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBm32g6x Ffwrq2h5sIC9gfFJcRcjJ4eEgInE7VnX2SFsMYkL99azdTFycQgJHGGUeH7nKguEs4RR4mD/ X6YuRg4ONgELie5/2iANIgLeEn19HewgYWaBEIkLR0JBwsIC9hIbn9xhgihxkNj5FmKMiMA5 RonDbetZQBIsAqoSb//cZwPp5RXwlfi+Lgli1QcOic0Pr7KC1HAKBEq8/n8T7DhGoOO+n1oD NpRZQFzi1pP5TBBHC0gs2XOeGcIWlXj5+B8rhK0ksej2Z6j6fImpMw8xgti8AoISJ2c+YZnA KDoLyahZSMpmISmbBfaapsT6XfoQJYoSU7ofskPYGhKtc+ayI4svYGRfxShanFqclJtuZKyX WpSZXFycn6eXl1qyiREYkwe3/FbdwXj5jeMhRgEORiUe3geF7uFCrIllxZW5hxglOJiVRHiF ZnqEC/GmJFZWpRblxxeV5qQWH2KU5mBREuf1f6kYLiSQnliSmp2aWpBaBJNl4uCUamDsFBZM Nbyjd5NR7qwju62u3cGnL4J0/YpbbjjuX3SpLr7g4f/Y9MNV+Rm7ef8venHquYfk6tOcPppJ kznOilxfuYjf7I7cz/fSeeqZU/fmLZ1Szbms0dZtxb7VD6VO3RTf9+LW+y9d4udynZbxPo+P Mrd/mVAm/SlRiMsu7nqpAo8k19fYhSeVWIozEg21mIuKEwFbMFxaxQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/v9lX5X1ZJIp7f3gXRLBzvB8QYIQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 19:05:09 -0000

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

SGksDQoNCldlIHRyeSB0byBhdm9pZCB1bmxlc3MtaXQtaXMta25vd24taW4tYWR2YW5jZSB0eXBl
IG9mIHByb2NlZHVyZXMuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCkZyb206IFJvbWFuIFNo
cG91bnQgW21haWx0bzpyb21hbkB0ZWx1cml4LmNvbV0NClNlbnQ6IDI3IE1heSAyMDE2IDIwOjE2
DQpUbzogUGF1bCBLeXppdmF0IDxwa3l6aXZhdEBhbHVtLm1pdC5lZHU+DQpDYzogQ2hyaXN0ZXIg
SG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbT47IE1hcnRpbiBUaG9tc29u
IDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+OyBtbXVzaWNAaWV0Zi5vcmcNClN1YmplY3Q6IFJl
OiBbTU1VU0lDXSBXR0xDIGZvciBkcmFmdC1pZXRmLW1tdXNpYy00NTcyLXVwZGF0ZS0wMw0KDQpP
biBGcmksIE1heSAyNywgMjAxNiBhdCAxOjAwIFBNLCBQYXVsIEt5eml2YXQgPHBreXppdmF0QGFs
dW0ubWl0LmVkdTxtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1Pj4gd3JvdGU6DQpPbiA1LzI3
LzE2IDEwOjM1IEFNLCBSb21hbiBTaHBvdW50IHdyb3RlOg0KSW4gZ2VuZXJhbCwgcmVxdWlyZW1l
bnQgdG8gYWx3YXlzIGluc2VydCBTSEEtMjU2IGlzIHRvIGluc3VyZQ0KaW50ZXJvcGVyYWJpbGl0
eS4gSWYgdGhlIG5ldHdvcmsgaXMgbGltaXRlZCB0byBkZXZpY2VzIG9ubHkgc3VwcG9ydGluZw0K
bW9yZSBzZWN1cmUgaGFzaCBhbGdvcml0aG1zLCBpdCB3b3VsZCBiZSBzYWZlIG5vdCBpbmNsdWRl
IFNIQS0yNTYgaWYNCmhpZ2hlciBzZWN1cml0eSBpcyBkZXNpcmVkLg0KDQpGb3IgZXhhbXBsZSwg
d2hlbiBhbiBlbmQgcG9pbnQgY29tbXVuaWNhdGVzIHdpdGggYW5vdGhlciBlbmQgcG9pbnQgZm9y
DQp3aGljaCBpdCBpcyBrbm93biBpbiBhZHZhbmNlIHdoYXQgZmluZ2VycHJpbnQgaGFzaCBhbGdv
cml0aG1zIGFyZQ0Kc3VwcG9ydGVkLCBvbmx5IGEgc2luZ2xlIGRlc2lyZWQgZmluZ2VycHJpbnQg
Y2FuIGJlIGluc2VydGVkLiBJbiBvdGhlcg0Kd29yZHMsIGlmIGFuIGVuZCBwb2ludCBjb21tdW5p
Y2F0ZXMsIGxldCdzIHNheSwgd2l0aCBGaXJlZm94IHZlcnNpb24gWCwNCndoaWNoIGlzIGtub3du
IHRvIHN1cHBvcnQgU0hBLTUxMiwgYW5kIGVuZCBwb2ludCBkZXNpcmVzIGhpZ2hlcg0Kc2VjdXJp
dHksIGl0IGNhbiBpbmNsdWRlIG9ubHkgU0hBLTUxMiBmaW5nZXJwcmludC4gIFRoZXJlIGlzIG5v
IG5lZWQgZm9yDQpTSEEtMjU2Lg0KDQpBbm90aGVyIGV4YW1wbGUsIGlmIEkgZGVzaWduIGEgImhp
Z2hlciBzZWN1cml0eSIgY29tbXVuaWNhdGlvbiBzZXJ2aWNlDQp3aGVyZSBJIGNvbnRyb2wgYWxs
IHRoZSBlbmQgcG9pbnRzLCBJIGNhbiBvbmx5IHN1cHBvcnQgU0hBLTUxMg0KY2VydGlmaWNhdGVz
IHdpdGhpbiB0aGlzIHNlcnZpY2UgYW5kIG5vdCBpbmNsdWRlIFNIQS0yNTYuDQoNClNvIGFueSB2
YWxpZCBleGNlcHRpb24gd2lsbCBpbmNsdWRlIGEgaGFzaCB0aGF0IHRoZSBzZW5kZXIgdGhpbmtz
IGlzICpzdHJvbmdlciogdGhhbiBTSEEtMjU2Pw0KDQpJZiBhbiBhcHBsaWNhdGlvbiB0aGlua3Mg
dGhhdCBhbm90aGVyIGhhc2ggaXMgbW9yZSBhcHByb3ByaWF0ZSBhbmQgaXMgc3VwcG9ydGVkIGJ5
IHJlbW90ZSBhcHBsaWNhdGlvbiwgaXQgc2hvdWxkIGJlIGFsbG93ZWQgdG8gaW5jbHVkZSBqdXN0
IHRoYXQgaGFzaC4NCg0KRm9yIGluc3RhbmNlLCBvbmUgY2FuIGFyZ3VlIGlmIGVuZCBwb2ludCBr
bm93cyBpbiBhZHZhbmNlIHRoYXQgaXQgY29tbXVuaWNhdGVzIHdpdGggYSBsZWdhY3kgZW5kIHBv
aW50IHRoYXQgb25seSBzdXBwb3J0cyBTSEEtMSwgdGhlcmUgaXMgbm8gcmVhc29uIHRvIGluY2x1
ZGUgU0hBLTI1Ni4gSXQgaXMgYWxzbyBsaWtlbHkgdGhhdCB0aGlzIGxlZ2FjeSBlbmQgcG9pbnQg
d2lsbCBvbmx5IHN1cHBvcnQgYSBzaW5nbGUgZmluZ2VycHJpbnQgcGVyIG09IGxpbmUsIHNvIGlu
Y2x1ZGluZyBib3RoIFNIQS0yNTYgYW5kIFNIQS0xIGNhbiBwcmV2ZW50IHRoZSBjb25uZWN0aW9u
IGZyb20gYmVpbmcgc2V0dXAuDQoNClRoaXMgY291bGQgYmUgc3RhdGVkIGFzOg0KDQoiQSBmaW5n
ZXJwcmludCB1c2luZyB0aGUgU0hBLTI1NiBoYXNoIE1VU1QvU0hPVUxEIGJlIGluY2x1ZGVkIGV4
Y2VwdCBpbiBjYXNlcyB3aGVyZSBhIGZpbmdlcnByaW50IGlzIGluY2x1ZGVkIHRoYXQgdXNlcyBh
IGhhc2gga25vd24gdG8gYmUgc3Ryb25nZXIgdGhhbiBTSEEtMjU2LiINCg0KVGhlcmUgY291bGQg
YmUgYWRkaXRpb25hbCB0ZXh0IHN0YXRpbmcgdGhhdCBldmVuIGluIHRoYXQgY2FzZSBTSEEtMjU2
IHNob3VsZCBzdGlsbCBiZSBpbmNsdWRlZCBleGNlcHQgaW4gY2FzZXMgd2hlcmUgaXQgaXMga25v
d24gdGhhdCB0aGUgcmVjaXBpZW50IHdpbGwgc3VwcG9ydCB0aGUgc3Ryb25nZXIgaGFzaC4NCg0K
SSB0aGluayB3aGF0IHdlIGFyZSB0cnlpbmcgdG8gZG9jdW1lbnQgaGVyZSBpczoNCg0KMS4gU0hB
LTI1NiBvciBiZXR0ZXIgaGFzaCBTSE9VTEQgYmUgdmVyaWZpZWQgZm9yIGVhY2ggY2VydGlmaWNh
dGUgdG8gaW5zdXJlIGFkZXF1YXRlIHNlY3VyaXR5LCBleGNlcHQgd2hlbiBjb21tdW5pY2F0aW5n
IHdpdGggbGVnYWN5IGVuZCBwb2ludHMgdGhhdCBvbmx5IHByb3ZpZGUgbG93ZXIgcXVhbGl0eSBo
YXNoZXMgaW4gZmluZ2VycHJpbnRzIHN1Y2ggYXMgU0hBLTEgb3IgTUQ1Lg0KDQoyLiBTSEEtMjU2
IFNIT1VMRCBiZSBpbmNsdWRlZCB0byBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSB1c2VkIHRvIGluc3Vy
ZSBpbnRlcm9wZXJhYmlsaXR5LCB1bmxlc3MgaXQgaXMga25vd24gaW4gYWR2YW5jZSB0aGF0IHJl
bW90ZSBlbmQgcG9pbnQgaXMgZWl0aGVyIGxlZ2FjeSBlbmQgcG9pbnQgdGhhdCBkb2VzIG5vdCBz
dXBwb3J0IFNIQS0yNTYgb3IgcmVtb3RlIGVuZCBwb2ludCBzdXBwb3J0cyBhIGJldHRlciBoYXNo
IHdoaWNoIG5lZWRzIHRvIGJlIGZvcmNlZCBmb3Igc29tZSByZWFzb24sIHN1Y2ggYXMgYmV0dGVy
IHNlY3VyaXR5Lg0KX19fX19fX19fX19fXw0KUm9tYW4gU2hwb3VudA0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHls
ZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0K
CW1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXpl
OjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgbGFuZz0iRU4tR0IiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojMUY0OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5IaSw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPldlIHRyeSB0byBhdm9pZCB1bmxlc3MtaXQtaXMta25v
d24taW4tYWR2YW5jZSB0eXBlIG9mIHByb2NlZHVyZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RDttc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48YSBuYW1lPSJfTWFpbEVuZENvbXBvc2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0
OTdEO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L2E+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBSb21h
biBTaHBvdW50IFttYWlsdG86cm9tYW5AdGVsdXJpeC5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4g
MjcgTWF5IDIwMTYgMjA6MTY8YnI+DQo8Yj5Ubzo8L2I+IFBhdWwgS3l6aXZhdCAmbHQ7cGt5eml2
YXRAYWx1bS5taXQuZWR1Jmd0Ozxicj4NCjxiPkNjOjwvYj4gQ2hyaXN0ZXIgSG9sbWJlcmcgJmx0
O2NocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbSZndDs7IE1hcnRpbiBUaG9tc29uICZsdDtt
YXJ0aW4udGhvbXNvbkBnbWFpbC5jb20mZ3Q7OyBtbXVzaWNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJq
ZWN0OjwvYj4gUmU6IFtNTVVTSUNdIFdHTEMgZm9yIGRyYWZ0LWlldGYtbW11c2ljLTQ1NzItdXBk
YXRlLTAzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+T24gRnJpLCBNYXkgMjcsIDIwMTYgYXQgMTowMCBQTSwgUGF1bCBLeXppdmF0ICZs
dDs8YSBocmVmPSJtYWlsdG86cGt5eml2YXRAYWx1bS5taXQuZWR1IiB0YXJnZXQ9Il9ibGFuayI+
cGt5eml2YXRAYWx1bS5taXQuZWR1PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2lu
LWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiA1
LzI3LzE2IDEwOjM1IEFNLCBSb21hbiBTaHBvdW50IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4w
cHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmln
aHQ6MGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkluIGdlbmVyYWwsIHJlcXVpcmVtZW50IHRv
IGFsd2F5cyBpbnNlcnQgU0hBLTI1NiBpcyB0byBpbnN1cmU8YnI+DQppbnRlcm9wZXJhYmlsaXR5
LiBJZiB0aGUgbmV0d29yayBpcyBsaW1pdGVkIHRvIGRldmljZXMgb25seSBzdXBwb3J0aW5nPGJy
Pg0KbW9yZSBzZWN1cmUgaGFzaCBhbGdvcml0aG1zLCBpdCB3b3VsZCBiZSBzYWZlIG5vdCBpbmNs
dWRlIFNIQS0yNTYgaWY8YnI+DQpoaWdoZXIgc2VjdXJpdHkgaXMgZGVzaXJlZC48YnI+DQo8YnI+
DQpGb3IgZXhhbXBsZSwgd2hlbiBhbiBlbmQgcG9pbnQgY29tbXVuaWNhdGVzIHdpdGggYW5vdGhl
ciBlbmQgcG9pbnQgZm9yPGJyPg0Kd2hpY2ggaXQgaXMga25vd24gaW4gYWR2YW5jZSB3aGF0IGZp
bmdlcnByaW50IGhhc2ggYWxnb3JpdGhtcyBhcmU8YnI+DQpzdXBwb3J0ZWQsIG9ubHkgYSBzaW5n
bGUgZGVzaXJlZCBmaW5nZXJwcmludCBjYW4gYmUgaW5zZXJ0ZWQuIEluIG90aGVyPGJyPg0Kd29y
ZHMsIGlmIGFuIGVuZCBwb2ludCBjb21tdW5pY2F0ZXMsIGxldCdzIHNheSwgd2l0aCBGaXJlZm94
IHZlcnNpb24gWCw8YnI+DQp3aGljaCBpcyBrbm93biB0byBzdXBwb3J0IFNIQS01MTIsIGFuZCBl
bmQgcG9pbnQgZGVzaXJlcyBoaWdoZXI8YnI+DQpzZWN1cml0eSwgaXQgY2FuIGluY2x1ZGUgb25s
eSBTSEEtNTEyIGZpbmdlcnByaW50LiZuYnNwOyBUaGVyZSBpcyBubyBuZWVkIGZvcjxicj4NClNI
QS0yNTYuPGJyPg0KPGJyPg0KQW5vdGhlciBleGFtcGxlLCBpZiBJIGRlc2lnbiBhICZxdW90O2hp
Z2hlciBzZWN1cml0eSZxdW90OyBjb21tdW5pY2F0aW9uIHNlcnZpY2U8YnI+DQp3aGVyZSBJIGNv
bnRyb2wgYWxsIHRoZSBlbmQgcG9pbnRzLCBJIGNhbiBvbmx5IHN1cHBvcnQgU0hBLTUxMjxicj4N
CmNlcnRpZmljYXRlcyB3aXRoaW4gdGhpcyBzZXJ2aWNlIGFuZCBub3QgaW5jbHVkZSBTSEEtMjU2
LjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJy
Pg0KU28gYW55IHZhbGlkIGV4Y2VwdGlvbiB3aWxsIGluY2x1ZGUgYSBoYXNoIHRoYXQgdGhlIHNl
bmRlciB0aGlua3MgaXMgKnN0cm9uZ2VyKiB0aGFuIFNIQS0yNTY/PG86cD48L286cD48L3A+DQo8
L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JZiBhbiBhcHBsaWNh
dGlvbiB0aGlua3MgdGhhdCBhbm90aGVyIGhhc2ggaXMgbW9yZSBhcHByb3ByaWF0ZSBhbmQgaXMg
c3VwcG9ydGVkIGJ5IHJlbW90ZSBhcHBsaWNhdGlvbiwgaXQgc2hvdWxkIGJlIGFsbG93ZWQgdG8g
aW5jbHVkZSBqdXN0IHRoYXQgaGFzaC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Rm9yIGluc3RhbmNlLCBvbmUgY2FuIGFyZ3VlIGlmIGVuZCBw
b2ludCBrbm93cyBpbiBhZHZhbmNlIHRoYXQgaXQgY29tbXVuaWNhdGVzIHdpdGggYSBsZWdhY3kg
ZW5kIHBvaW50IHRoYXQgb25seSBzdXBwb3J0cyBTSEEtMSwgdGhlcmUgaXMgbm8gcmVhc29uIHRv
IGluY2x1ZGUgU0hBLTI1Ni4gSXQgaXMgYWxzbyBsaWtlbHkgdGhhdCB0aGlzIGxlZ2FjeSBlbmQg
cG9pbnQgd2lsbCBvbmx5IHN1cHBvcnQgYSBzaW5nbGUNCiBmaW5nZXJwcmludCBwZXIgbT0gbGlu
ZSwgc28gaW5jbHVkaW5nIGJvdGggU0hBLTI1NiBhbmQgU0hBLTEgY2FuIHByZXZlbnQgdGhlIGNv
bm5lY3Rpb24gZnJvbSBiZWluZyBzZXR1cC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdo
dDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBjb3VsZCBiZSBzdGF0ZWQgYXM6PGJy
Pg0KPGJyPg0KJnF1b3Q7QSBmaW5nZXJwcmludCB1c2luZyB0aGUgU0hBLTI1NiBoYXNoIE1VU1Qv
U0hPVUxEIGJlIGluY2x1ZGVkIGV4Y2VwdCBpbiBjYXNlcyB3aGVyZSBhIGZpbmdlcnByaW50IGlz
IGluY2x1ZGVkIHRoYXQgdXNlcyBhIGhhc2gga25vd24gdG8gYmUgc3Ryb25nZXIgdGhhbiBTSEEt
MjU2LiZxdW90Ozxicj4NCjxicj4NClRoZXJlIGNvdWxkIGJlIGFkZGl0aW9uYWwgdGV4dCBzdGF0
aW5nIHRoYXQgZXZlbiBpbiB0aGF0IGNhc2UgU0hBLTI1NiBzaG91bGQgc3RpbGwgYmUgaW5jbHVk
ZWQgZXhjZXB0IGluIGNhc2VzIHdoZXJlIGl0IGlzIGtub3duIHRoYXQgdGhlIHJlY2lwaWVudCB3
aWxsIHN1cHBvcnQgdGhlIHN0cm9uZ2VyIGhhc2guPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVv
dGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHRoaW5rIHdoYXQgd2UgYXJlIHRy
eWluZyB0byBkb2N1bWVudCBoZXJlIGlzOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4xLiBTSEEtMjU2IG9yIGJldHRlciBoYXNoIFNIT1VMRCBi
ZSB2ZXJpZmllZCBmb3IgZWFjaCBjZXJ0aWZpY2F0ZSB0byBpbnN1cmUgYWRlcXVhdGUgc2VjdXJp
dHksIGV4Y2VwdCB3aGVuIGNvbW11bmljYXRpbmcgd2l0aCBsZWdhY3kgZW5kIHBvaW50cyB0aGF0
IG9ubHkgcHJvdmlkZSBsb3dlciBxdWFsaXR5IGhhc2hlcyBpbiBmaW5nZXJwcmludHMgc3VjaCBh
cyBTSEEtMSBvciBNRDUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjIuIFNIQS0yNTYgU0hPVUxEIGJlIGluY2x1ZGVkIHRvIGZvciBlYWNoIGNl
cnRpZmljYXRlIHVzZWQgdG8gaW5zdXJlIGludGVyb3BlcmFiaWxpdHksIHVubGVzcyBpdCBpcyBr
bm93biBpbiBhZHZhbmNlIHRoYXQgcmVtb3RlIGVuZCBwb2ludCBpcyBlaXRoZXIgbGVnYWN5IGVu
ZCBwb2ludCB0aGF0IGRvZXMgbm90IHN1cHBvcnQgU0hBLTI1NiBvciByZW1vdGUgZW5kIHBvaW50
IHN1cHBvcnRzIGEgYmV0dGVyIGhhc2gNCiB3aGljaCBuZWVkcyB0byBiZSBmb3JjZWQgZm9yIHNv
bWUgcmVhc29uLCBzdWNoIGFzIGJldHRlciBzZWN1cml0eS4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5fX19fX19fX19fX19f
PGJyPg0KUm9tYW4gU2hwb3VudDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B37FF4E53ESESSMB209erics_--


From nobody Fri May 27 12:34:27 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEDA312DC64 for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 12:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4y6XHdu3dD8i for <mmusic@ietfa.amsl.com>; Fri, 27 May 2016 12:34:25 -0700 (PDT)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F19712DBBE for <mmusic@ietf.org>; Fri, 27 May 2016 12:34:25 -0700 (PDT)
Received: by mail-io0-x232.google.com with SMTP id 190so78160886iow.1 for <mmusic@ietf.org>; Fri, 27 May 2016 12:34:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=fonXKfvByyw2/JNjYER0j1gxaOdVKGv5AhsjV+5QS2w=; b=wkB6bJZoU0a46ggpkuZ6cd8ZXzFbUmN/euWMYzNqqL+xONp6vFuvBnBxBmwDXDhnRw dk2G/qvwWYzDJzpM+5lt1xt9xxIQt08QnsdDnwqgZ0Bx720RF/jD8ICacsaJdhtZnJEs m0I5uElsnWmCNdEhUfTro0/nvRN2n0qJClpkJ2QZvWFPL/3J4aGnAfLmJl0Kv5j9WSKR Ct8cIjds194sZ2JxJW2IXQZpyC/NYYWpoioVx1UJuPRuwszpw8WCQwilsg4zKGvlOBfD VJ/grIKnRr641DPjgYsxysaG5lEOnj2MnuYHjQv8e67H7VGPI6dlpffJddBiX7Z08mDw 0HZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=fonXKfvByyw2/JNjYER0j1gxaOdVKGv5AhsjV+5QS2w=; b=ImVq8Y1HHDhv+AAHmdxuWBIUzLJ2xUnQWHn6b4DiIM6LM6czOGOZh6lz4oKrfmHhGt VPUpkJ9InnC3Zasuw/saJYhVaQeQqfhaHa3gXwNAXuDgIApSpiEGz6VNF0wzPbs6/7xc 9BKNxIQpdXNZUwIxFSLHj/blEo49NCxZelFqgXLpGF62+r/BWTpa8i5Wl+xdwPJ7dPFX WUm8zVpUGZI8Dr5wVPCJwl7Zb4Crpu8pu2EFfXejxSxSd4rLHQtJqzk37HwBVD00QWFx k8mmnsq3vnuBCHeuH+w5aGUOoHGzd8V5xE6OPtDLZDmK/Tt7NN+ftMQSEID1ld0N/xzi bqvQ==
X-Gm-Message-State: ALyK8tLXJv0aRnksJjwL9WMXXFkTkOBVsIuHG29FesIvrIVA0hBUyzonVyV9eWbjbd1SXQ==
X-Received: by 10.107.7.165 with SMTP id g37mr14277685ioi.64.1464377664713; Fri, 27 May 2016 12:34:24 -0700 (PDT)
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com. [209.85.223.174]) by smtp.gmail.com with ESMTPSA id i128sm3111301ith.6.2016.05.27.12.34.23 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 May 2016 12:34:23 -0700 (PDT)
Received: by mail-io0-f174.google.com with SMTP id p64so37165451ioi.2 for <mmusic@ietf.org>; Fri, 27 May 2016 12:34:23 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.147.6 with SMTP id v6mr13729973iod.3.1464377663541; Fri, 27 May 2016 12:34:23 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Fri, 27 May 2016 12:34:23 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se>
Date: Fri, 27 May 2016 15:34:23 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com>
Message-ID: <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c05be5673e3700533d7fe42
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/T317KGOLH-9JQCdbFo2gYb8EfDw>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2016 19:34:26 -0000

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

On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> We try to avoid unless-it-is-known-in-advance type of procedures.
>
>
>
What does this means, exactly?

When I am communicating with a WebRTC browser, I know which browser it is,
and what hash algorithms it supports. Most of the communication networks
require some sort of interop, so it is known in advance what codecs,
encryption algorithm, fingerprint hashes are supported.

It is, actually, it-is-unknown-in-advance procedures that are uncommon in
practice.

In any case, with current proposal, end point can either be complaint to
the new draft or be able to communicate with legacy that supports a single
SHA-1 per m= line. I think this should be enough reason to make inclusion
of SHA-256 a SHOULD instead of MUST.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure">On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br></div></div><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:Cali=
bri,sans-serif;font-size:11pt">We try to avoid unless-it-is-known-in-advanc=
e type of procedures.</span><br></p>
<p class=3D"MsoNormal"><br></p></div></div></blockquote><div><br></div><div=
>What does this means, exactly?</div><div><br></div><div>When I am communic=
ating with a WebRTC browser, I know which browser it is, and what hash algo=
rithms it supports. Most of the communication networks require some sort of=
 interop, so it is known in advance what codecs, encryption algorithm, fing=
erprint hashes are supported.</div><div><br></div><div>It is, actually, it-=
is-unknown-in-advance procedures that are uncommon in practice.</div><div><=
br></div><div>In any case, with current proposal, end point can either be c=
omplaint to the new draft or be able to communicate with legacy that suppor=
ts a single SHA-1 per m=3D line. I think this should be enough reason to ma=
ke inclusion of SHA-256 a SHOULD instead of MUST.</div><div><div class=3D"g=
mail_signature">_____________<br>Roman Shpount</div></div><div>=C2=A0</div>=
</div></div></div>

--94eb2c05be5673e3700533d7fe42--


From nobody Mon May 30 01:05:09 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1BE12D0C6 for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 01:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 D_wZNB7Pu5hZ for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 01:05:06 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4636D12D16B for <mmusic@ietf.org>; Mon, 30 May 2016 01:05:06 -0700 (PDT)
X-AuditID: c1b4fb2d-f79936d0000030e4-e7-574bf42fbe03
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 71.EB.12516.F24FB475; Mon, 30 May 2016 10:05:04 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0294.000; Mon, 30 May 2016 10:05:03 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoAgAAEbAD//8AqMIAAZnKAgAQpdQA=
Date: Mon, 30 May 2016 08:05:03 +0000
Message-ID: <D371CF1B.966A%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com>
In-Reply-To: <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_D371CF1B966Achristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFIsWRmVeSWpSXmKPExsUyM2K7t67BF+9wgxXnOCyunfnHaDF1+WMW ixUbDrBazLgwldmBxePv+w9MHjtn3WX3WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBmrzzYx FzzQq1iwcRpTA+MNjS5GDg4JAROJ9a8Suxg5gUwxiQv31rN1MXJxCAkcYZQ4vWYDK4SzhFFi 94a9LCANbAIWEt3/tEEaRARUJf5+n8wEYjMLVEl0Hn/BDmILC9hLXL18mQmixkFi59urLBD2 LUaJaW8VQWwWoN6bc08yg9i8AlYSZ/f/h9r1m1Pi6OLTYA2cAoESt/4sZQOxGYGu+35qDdQy cYlbT+YzQVwtILFkz3lmCFtU4uXjf6wgtqiAnsSXe/MYIZ5UlFjeLwfRGi+xfOd9Voi9ghIn Zz5hmcAoNgvJ1FlIymYhKYOIG0i8PzefGcLWlli28DWUrS+x8ctZRgjbWuL8jU8oahYwcqxi FC1OLS7OTTcy1kstykwuLs7P08tLLdnECIzhg1t+6+5gXP3a8RCjAAejEg+vgp53uBBrYllx Ze4hRgkOZiUR3rePgUK8KYmVValF+fFFpTmpxYcYpTlYlMR5/V8qhgsJpCeWpGanphakFsFk mTg4pRoY+77e+HhGeebxjpWZDmk9zhELrFs15k425Qz/EFu86Ob2EtttxvO3O/M6cS1ODmLe 82XJlHeNzzYlvQnpurNMO3PG8piE7d/bAzyPatpaMnQej6u0/9S3a9reeY67TqQsOtcdLN/Y cTfsu8P7srwW3uIHWz9YnrvwW+xBQWxK/yVev97JSUFPlFiKMxINtZiLihMBYGMELd0CAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/OW90krPcElsmYLYaORe6wfAiiaE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 08:05:08 -0000

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

So, what about something like this:

=93SHOULD, unless the endpoint knows that the peer supports a stronger hash=
 algorithm, or unless the endpoint is used for a service, or within an envi=
ronment, that mandates usage of strong hash algorithms=94.

?

Regards,

Christer

From: Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Date: Friday 27 May 2016 at 22:34
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>
Cc: "pkyzivat@alum.mit.edu<mailto:pkyzivat@alum.mit.edu>" <pkyzivat@alum.mi=
t.edu<mailto:pkyzivat@alum.mit.edu>>, Martin Thomson <martin.thomson@gmail.=
com<mailto:martin.thomson@gmail.com>>, "mmusic@ietf.org<mailto:mmusic@ietf.=
org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03

On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <christer.holmberg@erics=
son.com<mailto:christer.holmberg@ericsson.com>> wrote:
We try to avoid unless-it-is-known-in-advance type of procedures.


What does this means, exactly?

When I am communicating with a WebRTC browser, I know which browser it is, =
and what hash algorithms it supports. Most of the communication networks re=
quire some sort of interop, so it is known in advance what codecs, encrypti=
on algorithm, fingerprint hashes are supported.

It is, actually, it-is-unknown-in-advance procedures that are uncommon in p=
ractice.

In any case, with current proposal, end point can either be complaint to th=
e new draft or be able to communicate with legacy that supports a single SH=
A-1 per m=3D line. I think this should be enough reason to make inclusion o=
f SHA-256 a SHOULD instead of MUST.
_____________
Roman Shpount


--_000_D371CF1B966Achristerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <66B27A3074D9A44D9AA83FB97AA5AB41@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>So, what about something like this:</div>
<div><br>
</div>
<div>=93SHOULD, unless the endpoint knows that the peer supports a stronger=
 hash algorithm, or unless the endpoint is used for a service, or within an=
 environment, that mandates usage of strong hash algorithms=94.</div>
<div><br>
</div>
<div>?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Roman Shpount &lt;<a href=3D"=
mailto:roman@telurix.com">roman@telurix.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 27 May 2016 at 22:34<b=
r>
<span style=3D"font-weight:bold">To: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com</=
a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:pkyziva=
t@alum.mit.edu">pkyzivat@alum.mit.edu</a>&quot; &lt;<a href=3D"mailto:pkyzi=
vat@alum.mit.edu">pkyzivat@alum.mit.edu</a>&gt;, Martin Thomson &lt;<a href=
=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;,
 &quot;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] WGLC for draf=
t-ietf-mmusic-4572-update-03<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div>
<div class=3D"gmail_signature">On Fri, May 27, 2016 at 3:05 PM, Christer Ho=
lmberg <span dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
</div>
</div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:Cali=
bri,sans-serif;font-size:11pt">We try to avoid unless-it-is-known-in-advanc=
e type of procedures.</span><br>
</p>
<p class=3D"MsoNormal"><br>
</p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>What does this means, exactly?</div>
<div><br>
</div>
<div>When I am communicating with a WebRTC browser, I know which browser it=
 is, and what hash algorithms it supports. Most of the communication networ=
ks require some sort of interop, so it is known in advance what codecs, enc=
ryption algorithm, fingerprint hashes
 are supported.</div>
<div><br>
</div>
<div>It is, actually, it-is-unknown-in-advance procedures that are uncommon=
 in practice.</div>
<div><br>
</div>
<div>In any case, with current proposal, end point can either be complaint =
to the new draft or be able to communicate with legacy that supports a sing=
le SHA-1 per m=3D line. I think this should be enough reason to make inclus=
ion of SHA-256 a SHOULD instead of
 MUST.</div>
<div>
<div class=3D"gmail_signature">_____________<br>
Roman Shpount</div>
</div>
<div>&nbsp;</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D371CF1B966Achristerholmbergericssoncom_--


From nobody Mon May 30 01:08:23 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34EB12D180; Mon, 30 May 2016 01:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id twus6elaeC60; Mon, 30 May 2016 01:08:16 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C78CD12D16B; Mon, 30 May 2016 01:08:14 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-72-574bf4ec26ac
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 65.8C.12926.CE4FB475; Mon, 30 May 2016 10:08:12 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0294.000; Mon, 30 May 2016 10:08:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AdG3iWsAcXNHXXrjTfakEZTp6P/ejwAHIEqAAKtQNIA=
Date: Mon, 30 May 2016 08:08:12 +0000
Message-ID: <D371CFE9.9672%christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se> <CAMRcRGRK2s1MrgxsoHir6cF1n6WU1FTEFEAeTJ+VPzcmS9HSHw@mail.gmail.com>
In-Reply-To: <CAMRcRGRK2s1MrgxsoHir6cF1n6WU1FTEFEAeTJ+VPzcmS9HSHw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D371CFE99672christerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMIsWRmVeSWpSXmKPExsUyM2K7h+6bL97hBtdn6Vi87FnJbrH85QlG i6nLH7NY7JzbwezA4jHt/n02j52z7rJ7LFnykymAOYrLJiU1J7MstUjfLoEro3c+Z8G82oo9 v4QaGBvzuhg5OCQETCRWvFbuYuQEMsUkLtxbz9bFyMUhJHCEUWL1nlnMEM4SRokJU+8ygjSw CVhIdP/TBmkQEdCSWL14LhNIDbPATkaJhm1/2UFqhAVCJDYsyAIxRQRCJW4/k4Yot5J4NWEz G4jNIqAqsWv7TCYQmxcovm9CH9TeKYwSex9OYQVJcAoESjw9uA3MZgQ67vupNWANzALiEree zGeCOFpAYsme88wQtqjEy8f/wOpFBfQkvtybxwgRV5T4+GofI0RvvETvmtlsEIsFJU7OfMIy gVFsFpKxs5CUzUJSBhE3kHh/bj4zhK0tsWzhayhbX2Ljl7OMs4BeZhawlpix0hJZyQJGjlWM osWpxUm56UbGeqlFmcnFxfl5enmpJZsYgVF7cMtv1R2Ml984HmIU4GBU4uFV0PMOF2JNLCuu zD3EKMHBrCTC+/YxUIg3JbGyKrUoP76oNCe1+BCjNAeLkjiv/0vFcCGB9MSS1OzU1ILUIpgs EwenVAOj4BUJLe0Y7wmrnfyynukXNPiyLtfRO5Iaf6v+6/Oe7FVG7PohM7Wee0XZPkjT67il ++BlgQS7s8CMC1yhly9M+7F913fGqBcT0v7/t+dUnFi67QXrgwPMOZutS54oJuxRt54o+vDK a76w6hSxvuN921kfF/7VU1x/5opsLP/BBatrrna+9QlQYinOSDTUYi4qTgQAPFSijdYCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/EY8X-ILfSzkN39pb00R1HUGpGlg>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Colin Perkins \(csp@csperkins.org\)" <csp@csperkins.org>, "mmusic@ietf.org" <mmusic@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 08:08:20 -0000

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

Hi Suhas,

I have the same understanding as you: the offerer indicates support of RTP/=
RTCP-mux, and the answerer decides whether to use it or not. And, if used, =
it will be used in BOTH directions =96 i.e. the usage of RTP/RTCP is not pe=
r direction.

Colin? Magnus?

Regards,

Christer

From: Suhas Nandakumar <suhasietf@gmail.com<mailto:suhasietf@gmail.com>>
Date: Friday 27 May 2016 at 04:25
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>
Cc: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>, "avt@ietf.org<mailto:avt@ietf.org>" <avt@ietf.org<mailto:avt@=
ietf.org>>, Magnus Westerlund <magnus.westerlund@ericsson.com<mailto:magnus=
.westerlund@ericsson.com>>, Colin Perkins <csp@csperkins.org<mailto:csp@csp=
erkins.org>>
Subject: Re: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in=
 offer?

Going along O/A negotiation procedures, i would lean towards your former co=
nclusion that the offer needs to include the rtcp-mux ability.
If the offer doesn't include a=3Drtcp-mux and the answerer wants to mux , t=
hen it needs a new O/A from the answerer's perspectives.


If we make a=3Drtcp-mux a declarative SDP it might solve the other use-case=
 ..

thanks
Suhas

On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg <christer.holmberg@erics=
son.com<mailto:christer.holmberg@ericsson.com>> wrote:
(Sorry for the cross-posting)

Hi,

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       v=3D0
       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       s=3D-
       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=3D1153134164 1153137764
       m=3Daudio 49170 RTP/AVP 97
       a=3Drtpmap:97 iLBC/8000
       a=3Drtcp-mux

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=3Drtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=3Drtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=3Drtcp-mux"
   attribute.

Q: The question is whether it is allowed to include a=3Drtcp-mux in an answ=
er if the associated offer did NOT contain a=3Drtcp-mux.

The second last paragraph in the text above does say that, if the answer wi=
shes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=3D=
rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even i=
f it=92s not included in the offer? If so, how will the offerer then indica=
te whether mux is used or not.

Regards,

Christer


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org<mailto:avt@ietf.org>
https://www.ietf.org/mailman/listinfo/avt



--_000_D371CFE99672christerholmbergericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <1527A23550FE7E488B4B8188C3964A69@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 Suhas,</div>
<div><br>
</div>
<div>I have the same understanding as you: the offerer indicates support of=
 RTP/RTCP-mux, and the answerer decides whether to use it or not. And, if u=
sed, it will be used in BOTH directions =96 i.e. the usage of RTP/RTCP is n=
ot per direction.</div>
<div><br>
</div>
<div>Colin? Magnus?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Suhas Nandakumar &lt;<a href=
=3D"mailto:suhasietf@gmail.com">suhasietf@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 27 May 2016 at 04:25<b=
r>
<span style=3D"font-weight:bold">To: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com</=
a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;, &quot;<a href=3D"mailto:avt@ietf.org">avt@ietf.org=
</a>&quot; &lt;<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a>&gt;, Magnus
 Westerlund &lt;<a href=3D"mailto:magnus.westerlund@ericsson.com">magnus.we=
sterlund@ericsson.com</a>&gt;, Colin Perkins &lt;<a href=3D"mailto:csp@cspe=
rkins.org">csp@csperkins.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [AVTCORE] RTP/RTCP-mux=
: Attribute in answer if not included in offer?<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">Going along O/A negotiation procedures, i would lean towar=
ds your former conclusion that the offer needs to include the rtcp-mux abil=
ity.
<div>If the offer doesn't include a=3Drtcp-mux and the answerer wants to mu=
x , then it needs a new O/A from the answerer's perspectives.<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>If we make a=3Drtcp-mux a declarative SDP it might solve the other use=
-case ..</div>
<div><br>
</div>
<div>thanks</div>
<div>Suhas</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Thu, May 26, 2016 at 1:01 PM, Christer Holmbe=
rg <span dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div>
<p class=3D"MsoNormal">(Sorry for the cross-posting)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Hi,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">There has been a discussion in 3GPP regarding RFC 57=
61 (RTP/RTCP-mux).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Section 5.1.1 says:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">5.1.1.&nbsp; SDP Signalling<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; When the Session Description Protocol (SDP) [=
8] is used to negotiate<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; RTP sessions following the offer/answer model=
 [9], the &quot;a=3Drtcp-mux&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; attribute (see Section 8) indicates the desir=
e to multiplex RTP and<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; RTCP onto a single port.&nbsp; The initial SD=
P offer MUST include this<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; attribute at the media level to request multi=
plexing of RTP and RTCP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; on a single port.&nbsp; For example:<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; v=3D0<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o=3Dcsp 1153134164 11=
53134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; s=3D-<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c=3DIN IP6 2001:DB8::=
211:24ff:fea3:7a2e<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; t=3D1153134164 115313=
7764<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Daudio 49170 RTP/A=
VP 97<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Drtpmap:97 iLBC/80=
00<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Drtcp-mux<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; This offer denotes a unicast voice-over-IP se=
ssion using the RTP/AVP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; profile with iLBC coding.&nbsp; The answerer =
is requested to send both RTP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; and RTCP to port 49170 on IPv6 address 2001:D=
B8::211:24ff:fea3:7a2e.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; If the answerer wishes to multiplex RTP and R=
TCP onto a single port,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; it MUST include a media-level &quot;a=3Drtcp-=
mux&quot; attribute in the answer.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; The RTP payload types used in the answer MUST=
 conform to the rules in<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; Section 4.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; If the answer does not contain an &quot;a=3Dr=
tcp-mux&quot; attribute, the offerer<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; MUST NOT multiplex RTP and RTCP packets on a =
single port.&nbsp; Instead,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; it should send and receive RTCP on a port all=
ocated according to the<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; usual port-selection rules (either the port p=
air, or a signalled port<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; if the &quot;a=3Drtcp:&quot; attribute [10] i=
s also included).&nbsp; This will occur<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; when talking to a peer that does not understa=
nd the &quot;a=3Drtcp-mux&quot;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;">&nbsp;&nbsp; attribute.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain a=3Drtcp-=
mux.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">The second last paragraph in the text above does say=
 that, if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in=
 the answer.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">BUT, in my view that is it based on the first paragr=
aph, which assumes a=3Drtcp-mux is also included in the offer.<u></u><u></u=
></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Or, am I wrong? Is it allowed to include a=3Drtcp-mu=
x in the answer, even if it=92s not included in the offer? If so, how will =
the offerer then indicate whether mux is used or not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Regards,<span class=3D"HOEnZb"><font color=3D"#88888=
8"><u></u><u></u></font></span></p>
<span class=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Christer<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</font></span></div>
</div>
<br>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_D371CFE99672christerholmbergericssoncom_--


From nobody Mon May 30 01:12:52 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF7012D16B for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 01:12:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MgmRtYPkqx4 for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 01:12:49 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AA1512B027 for <mmusic@ietf.org>; Mon, 30 May 2016 01:12:48 -0700 (PDT)
X-AuditID: c1b4fb3a-f79386d00000467b-6b-574bf5fe0142
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id BC.65.18043.EF5FB475; Mon, 30 May 2016 10:12:46 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.03.0294.000; Mon, 30 May 2016 10:12:44 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AQHRuksKjftEj52ycEuRAM04XLGXwg==
Date: Mon, 30 May 2016 08:12:43 +0000
Message-ID: <D371D129.967D%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_D371D129967Dchristerholmbergericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZGbFdVPffV+9wgzm7dCymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujKdHcgoaqysezXrL3MD4N6eLkZNDQsBEovXmRXYIW0ziwr31 bF2MXBxCAkcYJWbNAEmAOEsYJT6vm8/cxcjBwSZgIdH9TxukQUQgVuLruvdMILawQKLEtknf mSDiSRLPV7aAlYsI6El8WwBWziKgKnH+/gawXbwCVhIbJywDsxmB9n4/tQaslVlAXOLWk/lM EPcISCzZc54ZwhaVePn4HyuILQo08su9eYwQcUWJj6/2MYKsYhaIl9i5NR9ivKDEyZlPWCYw Cs9CMnUWQtUsJFUQJQYS78/NZ4awtSWWLXwNZetLbPxylhGi1Vri4IIyZCULGDlWMYoWpxYX 56YbGemlFmUmFxfn5+nlpZZsYgRGzsEtv612MB587niIUYCDUYmHV0HPO1yINbGsuDL3EKME B7OSCO/bx0Ah3pTEyqrUovz4otKc1OJDjNIcLErivP4vFcOFBNITS1KzU1MLUotgskwcnFIN jNKzigPM0jrXT/65uu5AgNHeZbzCrVN23pSXsNlju/7Lluq9vpw+H7kSszbdiOxYp/JG88iP Of0nTnvmu/vx/3i05VpTH7t8+IPgmu6sqfePX6z5IxgzIfjp8p07ApNfBRuYbns0u5/H44HH 9pYiT4cd8Voun8o3v46d8eb8l9pPOv73xSo331ZiKc5INNRiLipOBACAKzRZmAIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/6KaYg1bOonC9t-0V44M93U8OUm0>
Subject: Re: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 08:12:51 -0000

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

Anyone?

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Friday 27 May 2016 at 12:10
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not in=
cluded in offer?


(Sorry for the cross-posting)

Hi,

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       v=3D0
       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       s=3D-
       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=3D1153134164 1153137764
       m=3Daudio 49170 RTP/AVP 97
       a=3Drtpmap:97 iLBC/8000
       a=3Drtcp-mux

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=3Drtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=3Drtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=3Drtcp-mux"
   attribute.

Q: The question is whether it is allowed to include a=3Drtcp-mux in an answ=
er if the associated offer did NOT contain a=3Drtcp-mux.

The second last paragraph in the text above does say that, if the answer wi=
shes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=3D=
rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even i=
f it=92s not included in the offer? If so, how will the offerer then indica=
te whether mux is used or not.

Regards,

Christer


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Anyone?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 27 May 2016 at 12:10<b=
r>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] FW: [AVTCORE] RTP=
/RTCP-mux: Attribute in answer if not included in offer?<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:EN-GB;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">(Sorry for the cross-posting)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There has been a discussion in 3GPP regarding RFC 57=
61 (RTP/RTCP-mux).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1.1 says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">5.1.1.&nbsp; SDP Signalling<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; When the Session D=
escription Protocol (SDP) [8] is used to negotiate<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTP sessions follo=
wing the offer/answer model [9], the &quot;a=3Drtcp-mux&quot;<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute (see Sec=
tion 8) indicates the desire to multiplex RTP and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTCP onto a single=
 port.&nbsp; The initial SDP offer MUST include this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute at the m=
edia level to request multiplexing of RTP and RTCP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; on a single port.&=
nbsp; For example:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; v=3D0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; s=3D-<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; t=3D1153134164 1153137764<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; m=3Daudio 49170 RTP/AVP 97<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtpmap:97 iLBC/8000<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtcp-mux<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; This offer denotes=
 a unicast voice-over-IP session using the RTP/AVP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; profile with iLBC =
coding.&nbsp; The answerer is requested to send both RTP<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; and RTCP to port 4=
9170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answerer wi=
shes to multiplex RTP and RTCP onto a single port,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it MUST include a =
media-level &quot;a=3Drtcp-mux&quot; attribute in the answer.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; The RTP payload ty=
pes used in the answer MUST conform to the rules in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; Section 4.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answer does=
 not contain an &quot;a=3Drtcp-mux&quot; attribute, the offerer<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; MUST NOT multiplex=
 RTP and RTCP packets on a single port.&nbsp; Instead,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it should send and=
 receive RTCP on a port allocated according to the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; usual port-selecti=
on rules (either the port pair, or a signalled port<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; if the &quot;a=3Dr=
tcp:&quot; attribute [10] is also included).&nbsp; This will occur<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; when talking to a =
peer that does not understand the &quot;a=3Drtcp-mux&quot;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain a=3Drtcp-=
mux.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The second last paragraph in the text above does say=
 that, if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in=
 the answer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">BUT, in my view that is it based on the first paragr=
aph, which assumes a=3Drtcp-mux is also included in the offer.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Or, am I wrong? Is it allowed to include a=3Drtcp-mu=
x in the answer, even if it=92s not included in the offer? If so, how will =
the offerer then indicate whether mux is used or not.<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>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>

--_000_D371D129967Dchristerholmbergericssoncom_--


From nobody Mon May 30 07:19:13 2016
Return-Path: <ron.even.tlv@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 A018C12D5E6; Mon, 30 May 2016 07:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJsvUD-mL-JN; Mon, 30 May 2016 07:19:10 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93A6A12D5E3; Mon, 30 May 2016 07:19:09 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id n129so73194079wmn.1; Mon, 30 May 2016 07:19:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=KUxdjzWqZ12ybSY1BE1ceYJ1JBpSEBTExcPFok5wDY0=; b=TTRNcneNYC9FsvkgSmmDw19vb5E1VLutoPvyCgZi3PDjz7lRFB2GoACXZVSeqnwKkv moODTOVAEubyMpcmsgdyuMSWmn1xt1FYk/ryHDqSXhG4P40OYs+wqO+gZzz+qQok8Mjv u+XWm0h/QaBm8r27VheuMh2w0y6nCP1E1iOo0h2yU3CNG0aaqOonNPrV+B+G4cwyeLT7 qjMmatDvz385g3OqewemJ0JWoA42AApPoHXM+JnypA4iyGotMfBjzYYX4XtDuTsTlNdO D3hHsDZZmwBwSC73ik0zpBxvk2Eo1WqEutMKwUNXm5yG1ynyhsx9IXZ1GNTe1mL0wGKH 16NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=KUxdjzWqZ12ybSY1BE1ceYJ1JBpSEBTExcPFok5wDY0=; b=BGGpu7Rtdnq6aMYi+2bnRBfaygpg6zsqw915mQeMDmGWzRU8PFF9iVxglGgQ6Kqx96 JpZlOTmddCrmaOoqa1bzyewdjg2CoJ4ca4X0QcPfVQUI8HQ0WP0s5kh7csTKpmj2O0hs E9goowDkXTcVqri42giml2kQHxISfcocuBeJ7xqFupV/oQv2xj3hXoy5f7eJsJzDvfF5 QGiPKhosPbPwA7Rd0P1g+NPdsuf6OE2IQzy4H29FPkDd4r4UEyTnrUVueBWjKXjNn0NV uf+viO2P+Hd3ARW/e6A7eUPKPnvl10PAhrd+N1AsbG55CjaSY9WcB//QNUdw6vq+quXh Drcw==
X-Gm-Message-State: ALyK8tICvKHfoEVRSMVw+fanJ8rDjJ/GoHPqkphr9l4rcOmwBUXKnwYMW6zRNPGrixWZpQ==
X-Received: by 10.194.123.67 with SMTP id ly3mr26748457wjb.135.1464617948021;  Mon, 30 May 2016 07:19:08 -0700 (PDT)
Received: from RoniPC (bzq-79-178-104-140.red.bezeqint.net. [79.178.104.140]) by smtp.gmail.com with ESMTPSA id jp2sm34716330wjc.16.2016.05.30.07.19.05 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 May 2016 07:19:06 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Suhas Nandakumar'" <suhasietf@gmail.com>, "'Christer Holmberg'" <christer.holmberg@ericsson.com>
References: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se> <CAMRcRGRK2s1MrgxsoHir6cF1n6WU1FTEFEAeTJ+VPzcmS9HSHw@mail.gmail.com>
In-Reply-To: <CAMRcRGRK2s1MrgxsoHir6cF1n6WU1FTEFEAeTJ+VPzcmS9HSHw@mail.gmail.com>
Date: Mon, 30 May 2016 17:18:09 +0300
Message-ID: <04d601d1ba7e$189ec900$49dc5b00$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04D7_01D1BA97.3DEDFCD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIVDnqmqgE4v4cr5iz6Tekgwmz3YwI2aa3Tnzkp6SA=
Content-Language: he
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/W7nphwnp2EZEP4Y2-H-eBC9ZYVw>
Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, 'Colin Perkins' <csp@csperkins.org>, avt@ietf.org, mmusic@ietf.org
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 14:19:12 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04D7_01D1BA97.3DEDFCD0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Agree with Suhas but have a question

What if the offer has an a=3Drtcp with a port different from the RTP =
one, and the response include a=3Drtcp using the same port as the RTP =
port? Is it allowed, at least in RFC3605 did not see any discussion =
about this

=20

Roni

=20

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Suhas =
Nandakumar
Sent: Friday, May 27, 2016 4:26 AM
To: Christer Holmberg
Cc: Magnus Westerlund; Colin Perkins (csp@csperkins.org); =
mmusic@ietf.org; avt@ietf.org
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not =
included in offer?

=20

Going along O/A negotiation procedures, i would lean towards your former =
conclusion that the offer needs to include the rtcp-mux ability.

If the offer doesn't include a=3Drtcp-mux and the answerer wants to mux =
, then it needs a new O/A from the answerer's perspectives.

=20

=20

If we make a=3Drtcp-mux a declarative SDP it might solve the other =
use-case ..

=20

thanks

Suhas

=20

On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

(Sorry for the cross-posting)

=20

Hi,

=20

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

=20

Section 5.1.1 says:

=20

5.1.1.  SDP Signalling

=20

   When the Session Description Protocol (SDP) [8] is used to negotiate

   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"

   attribute (see Section 8) indicates the desire to multiplex RTP and

   RTCP onto a single port.  The initial SDP offer MUST include this

   attribute at the media level to request multiplexing of RTP and RTCP

   on a single port.  For example:

=20

       v=3D0

       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e

       s=3D-

       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e

       t=3D1153134164 1153137764

       m=3Daudio 49170 RTP/AVP 97

       a=3Drtpmap:97 iLBC/8000

       a=3Drtcp-mux

=20

   This offer denotes a unicast voice-over-IP session using the RTP/AVP

   profile with iLBC coding.  The answerer is requested to send both RTP

   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

=20

   If the answerer wishes to multiplex RTP and RTCP onto a single port,

   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.

   The RTP payload types used in the answer MUST conform to the rules in

   Section 4.

=20

   If the answer does not contain an "a=3Drtcp-mux" attribute, the =
offerer

   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,

   it should send and receive RTCP on a port allocated according to the

   usual port-selection rules (either the port pair, or a signalled port

   if the "a=3Drtcp:" attribute [10] is also included).  This will occur

   when talking to a peer that does not understand the "a=3Drtcp-mux"

   attribute.

=20

Q: The question is whether it is allowed to include a=3Drtcp-mux in an =
answer if the associated offer did NOT contain a=3Drtcp-mux.

=20

The second last paragraph in the text above does say that, if the answer =
wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

=20

BUT, in my view that is it based on the first paragraph, which assumes =
a=3Drtcp-mux is also included in the offer.

=20

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, =
even if it=E2=80=99s not included in the offer? If so, how will the =
offerer then indicate whether mux is used or not.

=20

Regards,

=20

Christer

=20


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

=20


------=_NextPart_000_04D7_01D1BA97.3DEDFCD0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 14 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Agree with Suhas but have a question<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>What if the offer has an a=3Drtcp with a port different from the RTP =
one, and the response include a=3Drtcp using the same port as the RTP =
port? Is it allowed, at least in RFC3605 did not see any discussion =
about this<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
mmusic [mailto:mmusic-bounces@ietf.org] <b>On Behalf Of </b>Suhas =
Nandakumar<br><b>Sent:</b> Friday, May 27, 2016 4:26 AM<br><b>To:</b> =
Christer Holmberg<br><b>Cc:</b> Magnus Westerlund; Colin Perkins =
(csp@csperkins.org); mmusic@ietf.org; avt@ietf.org<br><b>Subject:</b> =
Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included =
in offer?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Going =
along O/A negotiation procedures, i would lean towards your former =
conclusion that the offer needs to include the rtcp-mux =
ability.<o:p></o:p></p><div><p class=3DMsoNormal>If the offer doesn't =
include a=3Drtcp-mux and the answerer wants to mux , then it needs a new =
O/A from the answerer's perspectives.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>If we make a=3Drtcp-mux a declarative SDP it might =
solve the other use-case ..<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>thanks<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Suhas<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Thu, =
May 26, 2016 at 1:01 PM, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" =
target=3D"_blank">christer.holmberg@ericsson.com</a>&gt; =
wrote:<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>(Sorry for the cross-posting)<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Hi,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>There has been a discussion in 3GPP regarding RFC 5761 =
(RTP/RTCP-mux).<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Section 5.1.1 says:<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>5.1.1.&nbsp; SDP Signalling</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; When the Session Description Protocol (SDP) [8] is =
used to negotiate</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; RTP sessions following the offer/answer model [9], =
the &quot;a=3Drtcp-mux&quot;</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; attribute (see Section 8) indicates the desire to =
multiplex RTP and</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; RTCP onto a single port.&nbsp; The initial SDP offer =
MUST include this</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; attribute at the media level to request multiplexing =
of RTP and RTCP</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; on a single port.&nbsp; For example:</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; v=3D0</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; o=3Dcsp 1153134164 1153134164 =
IN IP6 2001:DB8::211:24ff:fea3:7a2e</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; s=3D-</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; c=3DIN IP6 =
2001:DB8::211:24ff:fea3:7a2e</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; t=3D1153134164 =
1153137764</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; m=3Daudio 49170 RTP/AVP =
97</span><span lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Drtpmap:97 =
iLBC/8000</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=3Drtcp-mux</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; This offer denotes a unicast voice-over-IP session =
using the RTP/AVP</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; profile with iLBC coding.&nbsp; The answerer is =
requested to send both RTP</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; and RTCP to port 49170 on IPv6 address =
2001:DB8::211:24ff:fea3:7a2e.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; If the answerer wishes to multiplex RTP and RTCP onto =
a single port,</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; it MUST include a media-level =
&quot;a=3Drtcp-mux&quot; attribute in the answer.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; The RTP payload types used in the answer MUST conform =
to the rules in</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; Section 4.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; If the answer does not contain an =
&quot;a=3Drtcp-mux&quot; attribute, the offerer</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; MUST NOT multiplex RTP and RTCP packets on a single =
port.&nbsp; Instead,</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; it should send and receive RTCP on a port allocated =
according to the</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; usual port-selection rules (either the port pair, or =
a signalled port</span><span lang=3DEN-GB><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; if the &quot;a=3Drtcp:&quot; attribute [10] is also =
included).&nbsp; This will occur</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; when talking to a peer that does not understand the =
&quot;a=3Drtcp-mux&quot;</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; attribute.</span><span =
lang=3DEN-GB><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain =
a=3Drtcp-mux.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>The second last paragraph in the text above does say that, =
if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the =
answer.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>BUT, in my view that is it based on the first paragraph, =
which assumes a=3Drtcp-mux is also included in the =
offer.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Or, am I wrong? Is it allowed to include a=3Drtcp-mux in =
the answer, even if it=E2=80=99s not included in the offer? If so, how =
will the offerer then indicate whether mux is used or =
not.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB>Regards,<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB style=3D'color:#888888'>Christer<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-GB =
style=3D'color:#888888'>&nbsp;<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>______________________________________=
_________<br>Audio/Video Transport Core Maintenance<br><a =
href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/avt" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><o:p></o:p=
></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_04D7_01D1BA97.3DEDFCD0--


From nobody Mon May 30 07:25:38 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9A812D5D4; Mon, 30 May 2016 07:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j7r8g9iqNLEf; Mon, 30 May 2016 07:25:34 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4450312D5EF; Mon, 30 May 2016 07:25:33 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-dd-574c4d5bde70
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 61.5A.27088.B5D4C475; Mon, 30 May 2016 16:25:31 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0294.000; Mon, 30 May 2016 16:25:31 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, 'Suhas Nandakumar' <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AdG3iWsAcXNHXXrjTfakEZTp6P/ejwAHIEqAALHZ5oAABHKs+g==
Date: Mon, 30 May 2016 14:25:30 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B3801E9C6@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B37FF17DE@ESESSMB209.ericsson.se> <CAMRcRGRK2s1MrgxsoHir6cF1n6WU1FTEFEAeTJ+VPzcmS9HSHw@mail.gmail.com>, <04d601d1ba7e$189ec900$49dc5b00$@gmail.com>
In-Reply-To: <04d601d1ba7e$189ec900$49dc5b00$@gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B3801E9C6ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGIsWRmVeSWpSXmKPExsUyM2K7k260r0+4wacedYuXPSvZLZa/PMFo MXX5YxaLv+3MFjvndjA7sHpMu3+fzWPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgypjw4D5T wYXFjBWn51Y0MDZMYOxi5OSQEDCRONrSDmWLSVy4t56ti5GLQ0jgCKPE6yPdzBDOEkaJp0uW s3QxcnCwCVhIdP/TBjFFBIIk9jUIgPQyCyxmlPj5zQgkLCwQK7HzgTFIWEQgTuLU7jcsELaT xKINe5hBbBYBVYlVM56zgZTzCvhKzDujCrHoAKPEncalTCA1nECLTrX3g/UyAp32/dQaJohV 4hJNX1ayQpwsILFkz3lmCFtU4uXjf6wQNfkSa9YtYgexeQUEJU7OfMIygVFkFpL2WUjKZiEp g4gbSHx5fxvK1pZYtvA1M4StL9H9/jQTsvgCRvZVjKLFqcVJuelGRnqpRZnJxcX5eXp5qSWb GIGxd3DLb4MdjC+fOx5iFOBgVOLhVdDzDhdiTSwrrsw9xCjBwawkwqvg4xMuxJuSWFmVWpQf X1Sak1p8iFGag0VJnNf/pWK4kEB6YklqdmpqQWoRTJaJg1OqgTF1f/Xpra++PntR4v/oYON6 vr91yrM4jX48fGpnrvv588yJDhOtU5hVfkyZJ2srZKb/m9lxxgP2dxrvppiq/qgo49u65FxK +m6OHU9Lvpzqe3g8prLOJ9ouOW/Oj1vHFl6+Ft56QD9PM0/zrMyRK8LWhca62T/UH386FGl0 X+Mg99d1C71jgyYrsRRnJBpqMRcVJwIAYP3W4rkCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/tEEYUy1Z1kfulFSUmRNwvMAFofw>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, 'Colin Perkins' <csp@csperkins.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 14:25:36 -0000

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

Hi,

In an offer a=3Drtcp is used to provide a fallback port, in case the answer=
er does not support RTP/RTCP-mux (but does support a=3Drtcp).

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Roni Even<mailto:ron.even.tlv@gmail.com>
Sent: =FD30/=FD05/=FD2016 17:19
To: 'Suhas Nandakumar'<mailto:suhasietf@gmail.com>; Christer Holmberg<mailt=
o:christer.holmberg@ericsson.com>
Cc: Magnus Westerlund<mailto:magnus.westerlund@ericsson.com>; 'Colin Perkin=
s'<mailto:csp@csperkins.org>; avt@ietf.org<mailto:avt@ietf.org>; mmusic@iet=
f.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not in=
cluded in offer?

Hi,
Agree with Suhas but have a question
What if the offer has an a=3Drtcp with a port different from the RTP one, a=
nd the response include a=3Drtcp using the same port as the RTP port? Is it=
 allowed, at least in RFC3605 did not see any discussion about this

Roni

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Suhas Nandakumar
Sent: Friday, May 27, 2016 4:26 AM
To: Christer Holmberg
Cc: Magnus Westerlund; Colin Perkins (csp@csperkins.org); mmusic@ietf.org; =
avt@ietf.org
Subject: Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not in=
cluded in offer?

Going along O/A negotiation procedures, i would lean towards your former co=
nclusion that the offer needs to include the rtcp-mux ability.
If the offer doesn't include a=3Drtcp-mux and the answerer wants to mux , t=
hen it needs a new O/A from the answerer's perspectives.


If we make a=3Drtcp-mux a declarative SDP it might solve the other use-case=
 ..

thanks
Suhas

On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg <christer.holmberg@erics=
son.com<mailto:christer.holmberg@ericsson.com>> wrote:
(Sorry for the cross-posting)

Hi,

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       v=3D0
       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       s=3D-
       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=3D1153134164 1153137764
       m=3Daudio 49170 RTP/AVP 97
       a=3Drtpmap:97 iLBC/8000
       a=3Drtcp-mux

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=3Drtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=3Drtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=3Drtcp-mux"
   attribute.

Q: The question is whether it is allowed to include a=3Drtcp-mux in an answ=
er if the associated offer did NOT contain a=3Drtcp-mux.

The second last paragraph in the text above does say that, if the answer wi=
shes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=3D=
rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even i=
f it=92s not included in the offer? If so, how will the offerer then indica=
te whether mux is used or not.

Regards,

Christer


_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org<mailto:avt@ietf.org>
https://www.ietf.org/mailman/listinfo/avt


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
<style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
span.hoenzb
	{}
span.EmailStyle18
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-family:"Calibri","sans-serif"}
@page WordSection1
	{margin:72.0pt 90.0pt 72.0pt 90.0pt}
div.WordSection1
	{}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
In an offer a=3Drtcp is used to provide a fallback port, in case the answer=
er does not support RTP/RTCP-mux (but does support a=3Drtcp).<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:ron.even.tlv@gmail.com">Roni Even</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD30=
/=FD05/=FD2016 17:19</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:suhasietf@gmail.com">'Suhas Nandakumar'</a>;
<a href=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a></sp=
an><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:magnus.westerlund@ericsson.com">Magnus Westerlund</a>;
<a href=3D"mailto:csp@csperkins.org">'Colin Perkins'</a>; <a href=3D"mailto=
:avt@ietf.org">
avt@ietf.org</a>; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a></s=
pan><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offe=
r?</span><br>
<br>
</div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Hi,</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Agree with Suhas but ha=
ve a question</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">What if the offer has a=
n a=3Drtcp with a port different from the RTP one, and the response include=
 a=3Drtcp using the same port as the RTP port? Is it allowed,
 at least in RFC3605 did not see any discussion about this</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Roni</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0c=
m 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> mmusic=
 [mailto:mmusic-bounces@ietf.org]
<b>On Behalf Of </b>Suhas Nandakumar<br>
<b>Sent:</b> Friday, May 27, 2016 4:26 AM<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> Magnus Westerlund; Colin Perkins (csp@csperkins.org); mmusic@iet=
f.org; avt@ietf.org<br>
<b>Subject:</b> Re: [MMUSIC] [AVTCORE] RTP/RTCP-mux: Attribute in answer if=
 not included in offer?</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<p class=3D"MsoNormal">Going along O/A negotiation procedures, i would lean=
 towards your former conclusion that the offer needs to include the rtcp-mu=
x ability.</p>
<div>
<p class=3D"MsoNormal">If the offer doesn't include a=3Drtcp-mux and the an=
swerer wants to mux , then it needs a new O/A from the answerer's perspecti=
ves.</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal">If we make a=3Drtcp-mux a declarative SDP it might s=
olve the other use-case ..</p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<div>
<p class=3D"MsoNormal">thanks</p>
</div>
<div>
<p class=3D"MsoNormal">Suhas</p>
</div>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<p class=3D"MsoNormal">On Thu, May 26, 2016 at 1:01 PM, Christer Holmberg &=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt; wrote:</p>
<div>
<div>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">(Sorry for the cross=
-posting)</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">Hi,</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">There has been a dis=
cussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">Section 5.1.1 says:<=
/span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">5.1.1.&nbsp; SDP Signalling</sp=
an><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; When the Session D=
escription Protocol (SDP) [8] is used to negotiate</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; RTP sessions follo=
wing the offer/answer model [9], the &quot;a=3Drtcp-mux&quot;</span><span l=
ang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; attribute (see Sec=
tion 8) indicates the desire to multiplex RTP and</span><span lang=3D"EN-GB=
"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; RTCP onto a single=
 port.&nbsp; The initial SDP offer MUST include this</span><span lang=3D"EN=
-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; attribute at the m=
edia level to request multiplexing of RTP and RTCP</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; on a single port.&=
nbsp; For example:</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; v=3D0</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e</sp=
an><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; s=3D-</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e</span><span lang=3D"EN-GB"></=
span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; t=3D1153134164 1153137764</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; m=3Daudio 49170 RTP/AVP 97</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtpmap:97 iLBC/8000</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtcp-mux</span><span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; This offer denotes=
 a unicast voice-over-IP session using the RTP/AVP</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; profile with iLBC =
coding.&nbsp; The answerer is requested to send both RTP</span><span lang=
=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; and RTCP to port 4=
9170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; If the answerer wi=
shes to multiplex RTP and RTCP onto a single port,</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; it MUST include a =
media-level &quot;a=3Drtcp-mux&quot; attribute in the answer.</span><span l=
ang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; The RTP payload ty=
pes used in the answer MUST conform to the rules in</span><span lang=3D"EN-=
GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; Section 4.</span><=
span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; If the answer does=
 not contain an &quot;a=3Drtcp-mux&quot; attribute, the offerer</span><span=
 lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; MUST NOT multiplex=
 RTP and RTCP packets on a single port.&nbsp; Instead,</span><span lang=3D"=
EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; it should send and=
 receive RTCP on a port allocated according to the</span><span lang=3D"EN-G=
B"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; usual port-selecti=
on rules (either the port pair, or a signalled port</span><span lang=3D"EN-=
GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; if the &quot;a=3Dr=
tcp:&quot; attribute [10] is also included).&nbsp; This will occur</span><s=
pan lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; when talking to a =
peer that does not understand the &quot;a=3Drtcp-mux&quot;</span><span lang=
=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"font-size:1=
0.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; attribute.</span><=
span lang=3D"EN-GB"></span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">Q: The question is w=
hether it is allowed to include a=3Drtcp-mux in an answer if the associated=
 offer did NOT contain a=3Drtcp-mux.</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">The second last para=
graph in the text above does say that, if the answer wishes to do RTP/RTCP-=
mux, it includes a=3Drtcp-mux in the answer.</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">BUT, in my view that=
 is it based on the first paragraph, which assumes a=3Drtcp-mux is also inc=
luded in the offer.</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">Or, am I wrong? Is i=
t allowed to include a=3Drtcp-mux in the answer, even if it=92s not include=
d in the offer? If so, how will the offerer then indicate whether mux is us=
ed or not.</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB">Regards,</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"color:#8888=
88">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"color:#8888=
88">Christer</span></p>
<p class=3D"MsoNormal" style=3D""><span lang=3D"EN-GB" style=3D"color:#8888=
88">&nbsp;</span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a></p>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B3801E9C6ESESSMB209erics_--


From nobody Mon May 30 07:30:51 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 013E112D5EA for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 07:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PTFEFqhXRm1 for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 07:30:48 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8D7712D5D7 for <mmusic@ietf.org>; Mon, 30 May 2016 07:30:47 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id p64so67004730ioi.2 for <mmusic@ietf.org>; Mon, 30 May 2016 07:30:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=N5eBTnnNt8e2A0b0HDRtb47IJ422/iaNJr2vij3DJEk=; b=FUd/4dfvhuPgxBCj2codhVwTnRGWlc3FZqnxfOpMQw7lxztjpqV4h10YN/U8OpcS/B CX/oNSWGpDeLebybM5R/L0AssOkhtSFCjNmNDq+S638VW1yEdXSzrB4shZMXZR5jJ335 VXSkAlwFazQX02yLKJ3xGP7cuoTYRCdniAPMAhE+yuTdEtkjOgm3fezgClMpKDSX/ITj 6YZC8jTE/rgNr6fEONtuLsEN55em9qdgZf5kGGVWisbRX5LxjFAFGD+BXHQOWKOzCvBV jIqjI/Fqgq4X7vQss4QMmUC6AbXZ1APg5j8RqplKjwCZRMVerGIiydycdnC2U054LW/E pTUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=N5eBTnnNt8e2A0b0HDRtb47IJ422/iaNJr2vij3DJEk=; b=ewqrKwwdDwEi8sUA7js49JmC28v0+YlQ9Dxq9V7InR0yHWtyNvCcNTkjLj3rdWoWV1 I4ULxu7VLKQeYU6xRFKjutRL2CBa1y50Qo6pfo6e433XGdJLlj1ebBqKgTSsFRQJTEZh YdgNnpnbsRVQgZhQuKqNZ9rI/fYEK3KFWz6hX/ymHrmRGPCZxV2+OaIPU9n8IHslJqsn ElJ57/db1iOCN+1aO13A3D0LHji8+G5secUGjB6/M+aa5KQkelDoDcvd0muf+dkaVBib qWR57ssP7E7kQRtf8hyp0+rZ9kqC0kLfeKqHYWcqNzk95iHdRZXfcvfBew2WN/QkSzMI 5ixw==
X-Gm-Message-State: ALyK8tL3ug0a4wgfT/Y1L+1Ufuc9UWLzX5FHEPVh/5Hj155aveSmSWnusHH/aXS5v/GvCQ==
X-Received: by 10.107.7.165 with SMTP id g37mr21418459ioi.64.1464618647202; Mon, 30 May 2016 07:30:47 -0700 (PDT)
Received: from mail-it0-f53.google.com (mail-it0-f53.google.com. [209.85.214.53]) by smtp.gmail.com with ESMTPSA id g73sm7405191iog.6.2016.05.30.07.30.46 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 May 2016 07:30:46 -0700 (PDT)
Received: by mail-it0-f53.google.com with SMTP id z123so32820558itg.0 for <mmusic@ietf.org>; Mon, 30 May 2016 07:30:46 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.155.132 with SMTP id o126mr8464658itd.95.1464618646099; Mon, 30 May 2016 07:30:46 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 30 May 2016 07:30:45 -0700 (PDT)
In-Reply-To: <D371CF1B.966A%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com>
Date: Mon, 30 May 2016 10:30:45 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com>
Message-ID: <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c05d15821f3b00534101a64
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/GAonI_P-d8uSSm8eBuaix5H-ixY>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 14:30:50 -0000

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

What about legacy interop? Do we allow sending a single non SHA-256
fingerprint when working with legacy end points, or do we assume this is
covered under original RFC 4572?

Regards,
_____________
Roman Shpount

On Mon, May 30, 2016 at 4:05 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> So, what about something like this:
>
> =E2=80=9CSHOULD, unless the endpoint knows that the peer supports a stron=
ger hash
> algorithm, or unless the endpoint is used for a service, or within an
> environment, that mandates usage of strong hash algorithms=E2=80=9D.
>
> ?
>
> Regards,
>
> Christer
>
> From: Roman Shpount <roman@telurix.com>
> Date: Friday 27 May 2016 at 22:34
> To: Christer Holmberg <christer.holmberg@ericsson.com>
> Cc: "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>, Martin Thomson <
> martin.thomson@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
> Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
>
> On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>> We try to avoid unless-it-is-known-in-advance type of procedures.
>>
>>
>>
> What does this means, exactly?
>
> When I am communicating with a WebRTC browser, I know which browser it is=
,
> and what hash algorithms it supports. Most of the communication networks
> require some sort of interop, so it is known in advance what codecs,
> encryption algorithm, fingerprint hashes are supported.
>
> It is, actually, it-is-unknown-in-advance procedures that are uncommon in
> practice.
>
> In any case, with current proposal, end point can either be complaint to
> the new draft or be able to communicate with legacy that supports a singl=
e
> SHA-1 per m=3D line. I think this should be enough reason to make inclusi=
on
> of SHA-256 a SHOULD instead of MUST.
> _____________
> Roman Shpount
>
>

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

<div dir=3D"ltr">What about legacy interop? Do we allow sending a single no=
n SHA-256 fingerprint when working with legacy end points, or do we assume =
this is covered under original RFC 4572?<br><div class=3D"gmail_extra"><br>=
</div><div class=3D"gmail_extra">Regards,<br clear=3D"all"><div><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">_____________<br>Ro=
man Shpount</div></div>
<br><div class=3D"gmail_quote">On Mon, May 30, 2016 at 4:05 AM, Christer Ho=
lmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.c=
om" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-fam=
ily:Calibri,sans-serif">
<div>So, what about something like this:</div>
<div><br>
</div>
<div>=E2=80=9CSHOULD, unless the endpoint knows that the peer supports a st=
ronger hash algorithm, or unless the endpoint is used for a service, or wit=
hin an environment, that mandates usage of strong hash algorithms=E2=80=9D.=
</div>
<div><br>
</div>
<div>?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span>
<div style=3D"font-family:Calibri;font-size:11pt;text-align:left;color:blac=
k;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADD=
ING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:me=
dium none;PADDING-TOP:3pt">
<span style=3D"font-weight:bold">From: </span>Roman Shpount &lt;<a href=3D"=
mailto:roman@telurix.com" target=3D"_blank">roman@telurix.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 27 May 2016 at 22:34<b=
r>
<span style=3D"font-weight:bold">To: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:pkyziva=
t@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a>&quot; &lt;<a hr=
ef=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu=
</a>&gt;, Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" ta=
rget=3D"_blank">martin.thomson@gmail.com</a>&gt;,
 &quot;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org=
</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@=
ietf.org</a>&gt;<span class=3D""><br>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] WGLC for draf=
t-ietf-mmusic-4572-update-03<br>
</span></div><div><div class=3D"h5">
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div>
<div>On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <span dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
</div>
</div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);p=
adding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125);font-family:Cali=
bri,sans-serif;font-size:11pt">We try to avoid unless-it-is-known-in-advanc=
e type of procedures.</span><br>
</p>
<p class=3D"MsoNormal"><br>
</p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>What does this means, exactly?</div>
<div><br>
</div>
<div>When I am communicating with a WebRTC browser, I know which browser it=
 is, and what hash algorithms it supports. Most of the communication networ=
ks require some sort of interop, so it is known in advance what codecs, enc=
ryption algorithm, fingerprint hashes
 are supported.</div>
<div><br>
</div>
<div>It is, actually, it-is-unknown-in-advance procedures that are uncommon=
 in practice.</div>
<div><br>
</div>
<div>In any case, with current proposal, end point can either be complaint =
to the new draft or be able to communicate with legacy that supports a sing=
le SHA-1 per m=3D line. I think this should be enough reason to make inclus=
ion of SHA-256 a SHOULD instead of
 MUST.</div>
<div>
<div>_____________<br>
Roman Shpount</div>
</div>
<div>=C2=A0</div>
</div>
</div>
</div>
</div>
</div>
</div></div></span>
</div>

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

--94eb2c05d15821f3b00534101a64--


From nobody Mon May 30 10:08:40 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8BF12D17A for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 10:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iONKQEucxZtn for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 10:08:37 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C592312B05D for <mmusic@ietf.org>; Mon, 30 May 2016 10:08:36 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-fe-574c7392a366
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.183.51]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 9E.0F.27088.2937C475; Mon, 30 May 2016 19:08:34 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.03.0294.000; Mon, 30 May 2016 19:08:34 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoAgAAEbAD//8AqMIAAZnKAgAQpdQCAADi0gIAATZ/d
Date: Mon, 30 May 2016 17:08:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com>, <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com>
In-Reply-To: <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B3801FBC2ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrJIsWRmVeSWpSXmKPExsUyM2K7se6kYp9wgwW3jS2unfnHaDF1+WMW ixUbDrBazLgwldmBxePv+w9MHjtn3WX3WLLkJ5PHrSkFASxRXDYpqTmZZalF+nYJXBl/vt5g LFjgUfF/6lfmBsb59l2MnBwSAiYSJ96dY4GwxSQu3FvP1sXIxSEkcIRR4uO+BhYIZwmjRHfX XMYuRg4ONgELie5/2iANIgKqEn+/T2YCsZkFqiQ6j79gB7GFBewlNj65wwRR4yCx8+1VsDki As8YJfYtucsIkmABaj707S1YA6+Ar8S8+S+hNn/kkjh/7RtYEadAoMSfC3/AzmMEOu/7qTVQ 28Qlmr6sZIU4W0BiyZ7zzBC2qMTLx/9YIWryJR6taWOGWCAocXLmE5YJjCKzkLTPQlI2C0kZ RNxA4sv721C2tsSyha+ZIWx9ie73p5mQxRcwsq9iFC1OLU7KTTcy0kstykwuLs7P08tLLdnE CIzAg1t+G+xgfPnc8RCjAAejEg+vgp53uBBrYllxZe4hRgkOZiUR3jnpPuFCvCmJlVWpRfnx RaU5qcWHGKU5WJTEef1fKoYLCaQnlqRmp6YWpBbBZJk4OKUaGNdopUxTat6T3+2d17bxK9+b NE+nHoZJYfvniPAf0XYSsTC70W55fe3CIP7Ew6/f7J0x8cWLprZN5zT+mu9Xa3N8semxR0WR ufzmvx37q5bb6L1n2jT/4Tbl1TwTQqT7nQx4y/h8Lf+V3j+8fz1Hfcqf9dX/Sg/WHzTs3fXz vpYzn9ra+w+7hJVYijMSDbWYi4oTATgjAZ68AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/zzTphFaeOVwlt60JnDIHRIviueQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 17:08:39 -0000

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

Hi,

In my opinion that is covered by not mandating SHA-256 on the receiving sid=
e.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Roman Shpount<mailto:roman@telurix.com>
Sent: =FD30/=FD05/=FD2016 17:30
To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>
Cc: Paul Kyzivat<mailto:pkyzivat@alum.mit.edu>; Martin Thomson<mailto:marti=
n.thomson@gmail.com>; mmusic@ietf.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03

What about legacy interop? Do we allow sending a single non SHA-256 fingerp=
rint when working with legacy end points, or do we assume this is covered u=
nder original RFC 4572?

Regards,
_____________
Roman Shpount

On Mon, May 30, 2016 at 4:05 AM, Christer Holmberg <christer.holmberg@erics=
son.com<mailto:christer.holmberg@ericsson.com>> wrote:
So, what about something like this:

=93SHOULD, unless the endpoint knows that the peer supports a stronger hash=
 algorithm, or unless the endpoint is used for a service, or within an envi=
ronment, that mandates usage of strong hash algorithms=94.

?

Regards,

Christer

From: Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>>
Date: Friday 27 May 2016 at 22:34
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>
Cc: "pkyzivat@alum.mit.edu<mailto:pkyzivat@alum.mit.edu>" <pkyzivat@alum.mi=
t.edu<mailto:pkyzivat@alum.mit.edu>>, Martin Thomson <martin.thomson@gmail.=
com<mailto:martin.thomson@gmail.com>>, "mmusic@ietf.org<mailto:mmusic@ietf.=
org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03

On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <christer.holmberg@erics=
son.com<mailto:christer.holmberg@ericsson.com>> wrote:
We try to avoid unless-it-is-known-in-advance type of procedures.


What does this means, exactly?

When I am communicating with a WebRTC browser, I know which browser it is, =
and what hash algorithms it supports. Most of the communication networks re=
quire some sort of interop, so it is known in advance what codecs, encrypti=
on algorithm, fingerprint hashes are supported.

It is, actually, it-is-unknown-in-advance procedures that are uncommon in p=
ractice.

In any case, with current proposal, end point can either be complaint to th=
e new draft or be able to communicate with legacy that supports a single SH=
A-1 per m=3D line. I think this should be enough reason to make inclusion o=
f SHA-256 a SHOULD instead of MUST.
_____________
Roman Shpount



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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
</head>
<body>
<div>
<div style=3D"font-family:Calibri,sans-serif; font-size:11pt">Hi,<br>
<br>
In my opinion that is covered by not mandating SHA-256 on the receiving sid=
e.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
Sent from my Windows Phone</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">From:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:roman@telurix.com">Roman Shpount</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Sent:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">=FD30=
/=FD05/=FD2016 17:30</span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">To:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">Christer Holmberg</a></span><b=
r>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Cc:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt"><a hr=
ef=3D"mailto:pkyzivat@alum.mit.edu">Paul Kyzivat</a>;
<a href=3D"mailto:martin.thomson@gmail.com">Martin Thomson</a>; <a href=3D"=
mailto:mmusic@ietf.org">
mmusic@ietf.org</a></span><br>
<span style=3D"font-family:Calibri,sans-serif; font-size:11pt; font-weight:=
bold">Subject:
</span><span style=3D"font-family:Calibri,sans-serif; font-size:11pt">Re: [=
MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03</span><br>
<br>
</div>
<div>
<div dir=3D"ltr">What about legacy interop? Do we allow sending a single no=
n SHA-256 fingerprint when working with legacy end points, or do we assume =
this is covered under original RFC 4572?<br>
<div class=3D"gmail_extra"><br>
</div>
<div class=3D"gmail_extra">Regards,<br clear=3D"all">
<div>
<div class=3D"gmail_signature">_____________<br>
Roman Shpount</div>
</div>
<br>
<div class=3D"gmail_quote">On Mon, May 30, 2016 at 4:05 AM, Christer Holmbe=
rg <span dir=3D"ltr">
&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chr=
ister.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div style=3D"word-wrap:break-word; color:rgb(0,0,0); font-size:14px; font-=
family:Calibri,sans-serif">
<div>So, what about something like this:</div>
<div><br>
</div>
<div>=93SHOULD, unless the endpoint knows that the peer supports a stronger=
 hash algorithm, or unless the endpoint is used for a service, or within an=
 environment, that mandates usage of strong hash algorithms=94.</div>
<div><br>
</div>
<div>?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span>
<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:0i=
n; padding-left:0in; padding-right:0in; border-top:#b5c4df 1pt solid; borde=
r-right:medium none; padding-top:3pt">
<span style=3D"font-weight:bold">From: </span>Roman Shpount &lt;<a href=3D"=
mailto:roman@telurix.com" target=3D"_blank">roman@telurix.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 27 May 2016 at 22:34<b=
r>
<span style=3D"font-weight:bold">To: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmb=
erg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:pkyziva=
t@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a>&quot; &lt;<a hr=
ef=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu=
</a>&gt;, Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" ta=
rget=3D"_blank">martin.thomson@gmail.com</a>&gt;,
 &quot;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org=
</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@=
ietf.org</a>&gt;<span class=3D""><br>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] WGLC for draf=
t-ietf-mmusic-4572-update-03<br>
</span></div>
<div>
<div class=3D"h5">
<div><br>
</div>
<div>
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div>
<div>On Fri, May 27, 2016 at 3:05 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
</div>
</div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex; border=
-left-width:1px; border-left-style:solid; border-left-color:rgb(204,204,204=
); padding-left:1ex">
<div lang=3D"EN-GB">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125); font-family:Cal=
ibri,sans-serif; font-size:11pt">We try to avoid unless-it-is-known-in-adva=
nce type of procedures.</span><br>
</p>
<p class=3D"MsoNormal"><br>
</p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>What does this means, exactly?</div>
<div><br>
</div>
<div>When I am communicating with a WebRTC browser, I know which browser it=
 is, and what hash algorithms it supports. Most of the communication networ=
ks require some sort of interop, so it is known in advance what codecs, enc=
ryption algorithm, fingerprint hashes
 are supported.</div>
<div><br>
</div>
<div>It is, actually, it-is-unknown-in-advance procedures that are uncommon=
 in practice.</div>
<div><br>
</div>
<div>In any case, with current proposal, end point can either be complaint =
to the new draft or be able to communicate with legacy that supports a sing=
le SHA-1 per m=3D line. I think this should be enough reason to make inclus=
ion of SHA-256 a SHOULD instead of
 MUST.</div>
<div>
<div>_____________<br>
Roman Shpount</div>
</div>
<div>&nbsp;</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B3801FBC2ESESSMB209erics_--


From nobody Mon May 30 10:16:41 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E788E12D122 for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 10:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRUjZLg8cXNS for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 10:16:38 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A39E12D0C2 for <mmusic@ietf.org>; Mon, 30 May 2016 10:16:38 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id k23so275859386oih.0 for <mmusic@ietf.org>; Mon, 30 May 2016 10:16:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=CwUWgcuLn0i3miXns8qJXiA4DK6wN7bIp4JV9g1FZeo=; b=XTQk2LtMBwRqMHF7+146DZUq15OvG/cbxkGnMo4jozJPg0Fv85HxEzEMN4gUJU6x6H okzEiuNmzuipFM/Sx+TxL6YB1sfpcEGcM9n+oY3YCr/vGN6lDEQSMEBERdgCgwmXlFWx aiDGpiq7vH6lLq5NV37tbhA+zX4kvkfaMdqNURhWUkusOZfdDZjpltqFv4RdKU+av9Je LpLAUv1ElePFukGV23/vl+i7Yx7kc+8PbJrcizhvoJH+ZTKbHCAfa98Y0E1LgJ0I5GdB QlQ23omg0cynZfDtdThRL7cWO9cHR3knXygUTIq5xOVqLWW10UhNoj2CcD9rBzJxw0vh S/yA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=CwUWgcuLn0i3miXns8qJXiA4DK6wN7bIp4JV9g1FZeo=; b=YVgCCziXTA9OwQ9Kg6FvcuAuDjMv/At0u97eoXh2+UvC7Ua96e6yBvrphz6/IzMhv4 YX5Q2oQT1/P9Ce1nOYWML9ysrqIXntZdCkZSf6LLlgfLzNUIkjt6jk/8GNon2r3Etdwz GinP2BWzZFvi8KPU13xT5JMoxYGmYx6FW9BfAuCLa64sdbyQxcRp+eUQQa4VLylRNuWw FhIArGxTfO5wnaHK6GboM2QRGF2PtPV+0QLE05fIpWseac9LJhvGyd9jWoxOw7lX2gUu UkSopKWw72iLEm5dUFVAfszpXSUEDppEmgc8T5A2wCBz8LkzgrnXNFJMfqDip1tzmYop TjaQ==
X-Gm-Message-State: ALyK8tLx3wvDfRS4p4ZeO5zDBM36w4RV2WdvRj89xgDSI3mt/BH2TMyMdBT91i7qbtQAfg==
X-Received: by 10.157.41.173 with SMTP id n42mr19869456otb.65.1464628597821; Mon, 30 May 2016 10:16:37 -0700 (PDT)
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com. [209.85.223.174]) by smtp.gmail.com with ESMTPSA id 78sm16558222otc.24.2016.05.30.10.16.36 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Mon, 30 May 2016 10:16:36 -0700 (PDT)
Received: by mail-io0-f174.google.com with SMTP id f8so110868596ioe.3 for <mmusic@ietf.org>; Mon, 30 May 2016 10:16:36 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.147.6 with SMTP id v6mr22061177iod.3.1464628596457; Mon, 30 May 2016 10:16:36 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Mon, 30 May 2016 10:16:36 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se>
Date: Mon, 30 May 2016 13:16:36 -0400
X-Gmail-Original-Message-ID: <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com>
Message-ID: <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c05be5638626c0534126b96
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/UTb33UGz6tx98wVhEPNvsKzuUc8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 17:16:40 -0000

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

On Mon, May 30, 2016 at 1:08 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> In my opinion that is covered by not mandating SHA-256 on the receiving
> side.
>

End points should also be able to generate session descriptions with a
single SHA-1 fingerprint per m= line on the sending side, when
communicating with legacy end points. Legacy end points might not be able
to handle multiple fingerprints and might not support SHA-256.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure" data-smartmail=3D"gmail_signature">On Mon, May 30, 2016 at 1:08 PM, Ch=
rister Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@e=
ricsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span=
> wrote:<br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">



<div>
<div>
<div style=3D"font-family:Calibri,sans-serif;font-size:11pt">In my opinion =
that is covered by not mandating SHA-256 on the receiving side.</div></div>=
</div></blockquote><div><br></div><div>End points should also be able to ge=
nerate session descriptions with a single SHA-1 fingerprint per m=3D line o=
n the sending side, when communicating with legacy end points. Legacy end p=
oints might not be able to handle multiple fingerprints and might not suppo=
rt SHA-256.</div><div><br></div><div>Regards,</div><div><div class=3D"gmail=
_signature" data-smartmail=3D"gmail_signature">_____________<br>Roman Shpou=
nt</div></div><div>=C2=A0</div></div></div></div>

--94eb2c05be5638626c0534126b96--


From nobody Mon May 30 10:50:11 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C59F12D0B3 for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 10:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uoNoZiQQp_Ry for <mmusic@ietfa.amsl.com>; Mon, 30 May 2016 10:50:09 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5FEE12B011 for <mmusic@ietf.org>; Mon, 30 May 2016 10:50:08 -0700 (PDT)
X-AuditID: c1b4fb25-f79f26d00000327e-ed-574c7d4f7b74
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E9.25.12926.F4D7C475; Mon, 30 May 2016 19:50:07 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.03.0294.000; Mon, 30 May 2016 19:50:06 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoAgAAEbAD//8AqMIAAZnKAgAQpdQCAADi0gIAATZ/d///gtwD//9XcMA==
Date: Mon, 30 May 2016 17:50:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com>
In-Reply-To: <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNIsWRmVeSWpSXmKPExsUyM2K7va5/rU+4wcmjvBbXzvxjtJi6/DGL xYoNB1gtZlyYyuzA4vH3/Qcmj52z7rJ7LFnyk8nj1pSCAJYoLpuU1JzMstQifbsEroxF026w FOxjq1h0cg9zA+MKti5GTg4JAROJ19/OMkHYYhIX7q0HinNxCAkcYZTYdfMmC4SzhFFi97Xp jF2MHBxsAhYS3f+0QRpEBFQl/n6fDNbMLFAl0Xn8BTuILSxgL7HxyR0miBoHiZ1vr4LNERH4 xihx8uIVVpAEC1Dz3gU3wWxeAV+Jyz1NzBDL/nFLfDoxAWwSp0CgxMKfHxlBbEag876fWgO1 TVzi1pP5UGcLSCzZc54ZwhaVePn4HyuErSSx9vB2FpCjmQU0Jdbv0odoVZSY0v2QHWKvoMTJ mU9YJjCKzUIydRZCxywkHbOQdCxgZFnFKFqcWpyUm25krJdalJlcXJyfp5eXWrKJERhlB7f8 Vt3BePmN4yFGAQ5GJR5eBT3vcCHWxLLiytxDjBIczEoivHPSfcKFeFMSK6tSi/Lji0pzUosP MUpzsCiJ8/q/VAwXEkhPLEnNTk0tSC2CyTJxcEo1MGYya6w34eE1e6PZes+s9oLNPrEA5wcz 3/98fF9155TMjjjR/Q9Z/UK5wjQqGr6VqPx8XpF9U9mhL6qi9ryFoIfcSefrkzTSb4rWHFd7 dcC4+1L44zoJBsGi+Pdmq9jOVDr7GadUb3TmWx51bUuC/jY12Rb1yz5V6Utvfnr7/euK5I9L d/jPUGIpzkg01GIuKk4EADOYIlGuAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/AYViBwGrLmzNhAZxWppTCLGf8rM>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 May 2016 17:50:10 -0000

SGksDQoNCj4+IEluIG15IG9waW5pb24gdGhhdCBpcyBjb3ZlcmVkIGJ5IG5vdCBtYW5kYXRpbmcg
U0hBLTI1NiBvbiB0aGUgcmVjZWl2aW5nIHNpZGUuDQo+DQo+IEVuZCBwb2ludHMgc2hvdWxkIGFs
c28gYmUgYWJsZSB0byBnZW5lcmF0ZSBzZXNzaW9uIGRlc2NyaXB0aW9ucyB3aXRoIGEgc2luZ2xl
IFNIQS0xIGZpbmdlcnByaW50IHBlciBtPSBsaW5lIG9uIHRoZQ0KPiBzZW5kaW5nIHNpZGUsIHdo
ZW4gY29tbXVuaWNhdGluZyB3aXRoIGxlZ2FjeSBlbmQgcG9pbnRzLiBMZWdhY3kgZW5kIHBvaW50
cyBtaWdodCBub3QgYmUgYWJsZSB0byBoYW5kbGUgbXVsdGlwbGUgZmluZ2VycHJpbnRzIGFuZCBt
aWdodCBub3Qgc3VwcG9ydCBTSEEtMjU2Lg0KDQpJIGhlYXIgd2hhdCB5b3UgYXJlIHNheWluZywg
YnV0IHRoZSBxdWVzdGlvbiBpcyB3aGV0aGVyIHdlIHdhbnQgdG8gY292ZXIgdGhhdCwgb3Igd2hl
dGhlciB3ZSBhc3N1bWUgdGhhdCB0aGUgZW5kcG9pbnQgaW4gc3VjaCBjYXNlcyBzaW1wbHkgaGF2
ZSB0byBvcGVyYXRlIGluICJsZWdhY3kgbW9kZSIsIGkuZS4gYWNjb3JkaW5nIHRvIHRoZSBvbGQg
UkZDLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KwqANCg==


From nobody Tue May 31 07:15:17 2016
Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA7B312D5D0 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 07:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level: 
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LdBBg5rAKH9K for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 07:15:14 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73F6112D5B6 for <mmusic@ietf.org>; Tue, 31 May 2016 07:15:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=463; q=dns/txt; s=iport; t=1464704114; x=1465913714; h=from:subject:to:message-id:date:mime-version: content-transfer-encoding; bh=dlrk083HmYgzlXeWjyGKTUMiSJNzTJMzTZMQk3mr6f8=; b=ilWr9gMeagSjMAH3JvTw4afydMoMlIPKWMPTmbJ7J4O48FIbZRV5hSnf WkLPfrKreyigXt/rt22L2o/8Rf7cClXbb92qIVrxp94VaArdNjgb2XGND oojZqJX+V4NYgi0Z8jjE6GGBlLToKM1PZjVfI0M52sF/R4ZEY8eOCC/aP s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AbAgBQm01X/4cNJK1bgzyBAYQVtDeCD?= =?us-ascii?q?wENgXqGBwGBSTgUAQEBAQEBAWUnhG8VdgImAl8NCAEBiCudB49ikH4BAQEHAiW?= =?us-ascii?q?BAYUmgXcIiheCWQEEmDeBL4xxgVMBFYRPgwmFW49MHgEBQoQJIIpqAQEB?=
X-IronPort-AV: E=Sophos;i="5.26,395,1459814400"; d="scan'208";a="278390599"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 May 2016 14:15:13 +0000
Received: from [10.98.149.203] (bxb-fandreas-88110.cisco.com [10.98.149.203]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u4VEFCen002590 for <mmusic@ietf.org>; Tue, 31 May 2016 14:15:13 GMT
From: Flemming Andreasen <fandreas@cisco.com>
To: mmusic <mmusic@ietf.org>
Message-ID: <73a4d9c3-ee07-6134-7f28-a0c53d530627@cisco.com>
Date: Tue, 31 May 2016 10:15:12 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/B0tEixFE5qRQg1qIZt33xgg1zyo>
Subject: [MMUSIC] Preparing for MMUSIC meeting at IETF 96 (Berlin)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 14:15:16 -0000

Greetings MMUSIC

IETF 96 will be held in Berlin July 17-26. WG scheduling requests need 
to be submitted by Friday this week, however before we ask for meeting 
time, we would like to get an indication of what  topics people would 
like to discuss in Berlin. Thus, if you believe you (or somebody else) 
have a draft that would benefit from discussion in Berlin, please let us 
know at this time so we can plan accordingly.

Thanks

-- Flemming & Bo



From nobody Tue May 31 09:24:37 2016
Return-Path: <eckelcu@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79FD612D623 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 09:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level: 
X-Spam-Status: No, score=-15.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JGZj3IhsjCKj for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 09:24:33 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED4A112D626 for <mmusic@ietf.org>; Tue, 31 May 2016 09:24:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18140; q=dns/txt; s=iport; t=1464711872; x=1465921472; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=hCoHMM+GZXojwKwBw6ig3D6SVO7uO3gyQGCMsHNtpN8=; b=XawYjYt572nbBN1i6deivzrkZSoZd7PZjW4ci6dl1VT0Q9yhqfVYfiob W4MkS7FH1TDfNr/A/kizM90YSKhhpepE9vJJNPmpiuTfb1pQ3/O1+q3/H 2OoylMdXMdb7y63H3ZNww67Gq7pexg3vea7oNB/9M7SYYu0BVGzNwmcJ4 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAgAkuk1X/4gNJK1bgm9NVn0Gt3WCD?= =?us-ascii?q?wENgXqGEQKBPjgUAQEBAQEBAWUnhEUBAQEELVwCAQgRAwECKAcyFAgBCAIEARK?= =?us-ascii?q?IL743AQEBAQEBAQEBAQEBAQEBAQEBAQEBHIp0hGCFQgWOHYUahQABjh+PHI9LA?= =?us-ascii?q?R4BAUKCBhwWgTVuiTl/AQEB?=
X-IronPort-AV: E=Sophos;i="5.26,396,1459814400";  d="scan'208,217";a="112847602"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 31 May 2016 16:24:31 +0000
Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u4VGOVTQ012919 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 31 May 2016 16:24:31 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 31 May 2016 11:24:31 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1104.009; Tue, 31 May 2016 11:24:30 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
Thread-Index: AQHRuksKjftEj52ycEuRAM04XLGXwp/TG7KA
Date: Tue, 31 May 2016 16:24:30 +0000
Message-ID: <D3730864.710F0%eckelcu@cisco.com>
References: <D371D129.967D%christer.holmberg@ericsson.com>
In-Reply-To: <D371D129.967D%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.32.140]
Content-Type: multipart/alternative; boundary="_000_D3730864710F0eckelcuciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Icy_D2sJjm7ZQtnslGN8Plo4SW4>
Subject: Re: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 16:24:35 -0000

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

Hi Christer,

My understanding is the same as yours, if rtcp-mux was not included in the =
offer, it cannot be included in the answer.

Cheers,
Charles

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, May 30, 2016 at 1:12 AM
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmb=
erg@ericsson.com>>, "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.=
org<mailto:mmusic@ietf.org>>
Subject: Re: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if no=
t included in offer?

Anyone?

Regards,

Christer

From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on b=
ehalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.=
holmberg@ericsson.com>>
Date: Friday 27 May 2016 at 12:10
To: "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusi=
c@ietf.org>>
Subject: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not in=
cluded in offer?


(Sorry for the cross-posting)

Hi,

There has been a discussion in 3GPP regarding RFC 5761 (RTP/RTCP-mux).

Section 5.1.1 says:

5.1.1.  SDP Signalling

   When the Session Description Protocol (SDP) [8] is used to negotiate
   RTP sessions following the offer/answer model [9], the "a=3Drtcp-mux"
   attribute (see Section 8) indicates the desire to multiplex RTP and
   RTCP onto a single port.  The initial SDP offer MUST include this
   attribute at the media level to request multiplexing of RTP and RTCP
   on a single port.  For example:

       v=3D0
       o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e
       s=3D-
       c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e
       t=3D1153134164 1153137764
       m=3Daudio 49170 RTP/AVP 97
       a=3Drtpmap:97 iLBC/8000
       a=3Drtcp-mux

   This offer denotes a unicast voice-over-IP session using the RTP/AVP
   profile with iLBC coding.  The answerer is requested to send both RTP
   and RTCP to port 49170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.

   If the answerer wishes to multiplex RTP and RTCP onto a single port,
   it MUST include a media-level "a=3Drtcp-mux" attribute in the answer.
   The RTP payload types used in the answer MUST conform to the rules in
   Section 4.

   If the answer does not contain an "a=3Drtcp-mux" attribute, the offerer
   MUST NOT multiplex RTP and RTCP packets on a single port.  Instead,
   it should send and receive RTCP on a port allocated according to the
   usual port-selection rules (either the port pair, or a signalled port
   if the "a=3Drtcp:" attribute [10] is also included).  This will occur
   when talking to a peer that does not understand the "a=3Drtcp-mux"
   attribute.

Q: The question is whether it is allowed to include a=3Drtcp-mux in an answ=
er if the associated offer did NOT contain a=3Drtcp-mux.

The second last paragraph in the text above does say that, if the answer wi=
shes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in the answer.

BUT, in my view that is it based on the first paragraph, which assumes a=3D=
rtcp-mux is also included in the offer.

Or, am I wrong? Is it allowed to include a=3Drtcp-mux in the answer, even i=
f it's not included in the offer? If so, how will the offerer then indicate=
 whether mux is used or not.

Regards,

Christer


--_000_D3730864710F0eckelcuciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <A05CF80055E4F241ADDA8553D7D0D174@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</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: 16px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi Christer,</div>
<div><br>
</div>
<div>My understanding is the same as yours, if rtcp-mux was not included in=
 the offer, it cannot be included in the answer.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Charles</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, May 30, 2016 at 1:12 =
AM<br>
<span style=3D"font-weight:bold">To: </span>Christer Holmberg &lt;<a href=
=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com</=
a>&gt;, &quot;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [MMUSIC] FW: [AVTCORE]=
 RTP/RTCP-mux: Attribute in answer if not included in offer?<br>
</div>
<div><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div>Anyone?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>mmusic &lt;<a href=3D"mailto:=
mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>&gt; on behalf of Chris=
ter Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com">christer=
.holmberg@ericsson.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday 27 May 2016 at 12:10<b=
r>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mmusic@=
ietf.org">mmusic@ietf.org</a>&quot; &lt;<a href=3D"mailto:mmusic@ietf.org">=
mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] FW: [AVTCORE] RTP=
/RTCP-mux: Attribute in answer if not included in offer?<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif;">
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:EN-GB;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">(Sorry for the cross-posting)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There has been a discussion in 3GPP regarding RFC 57=
61 (RTP/RTCP-mux).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1.1 says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">5.1.1.&nbsp; SDP Signalling<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; When the Session D=
escription Protocol (SDP) [8] is used to negotiate<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTP sessions follo=
wing the offer/answer model [9], the &quot;a=3Drtcp-mux&quot;<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute (see Sec=
tion 8) indicates the desire to multiplex RTP and<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; RTCP onto a single=
 port.&nbsp; The initial SDP offer MUST include this<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute at the m=
edia level to request multiplexing of RTP and RTCP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; on a single port.&=
nbsp; For example:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; v=3D0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; o=3Dcsp 1153134164 1153134164 IN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; s=3D-<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; c=3DIN IP6 2001:DB8::211:24ff:fea3:7a2e<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; t=3D1153134164 1153137764<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; m=3Daudio 49170 RTP/AVP 97<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtpmap:97 iLBC/8000<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; a=3Drtcp-mux<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; This offer denotes=
 a unicast voice-over-IP session using the RTP/AVP<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; profile with iLBC =
coding.&nbsp; The answerer is requested to send both RTP<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; and RTCP to port 4=
9170 on IPv6 address 2001:DB8::211:24ff:fea3:7a2e.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answerer wi=
shes to multiplex RTP and RTCP onto a single port,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it MUST include a =
media-level &quot;a=3Drtcp-mux&quot; attribute in the answer.<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; The RTP payload ty=
pes used in the answer MUST conform to the rules in<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; Section 4.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; If the answer does=
 not contain an &quot;a=3Drtcp-mux&quot; attribute, the offerer<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; MUST NOT multiplex=
 RTP and RTCP packets on a single port.&nbsp; Instead,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; it should send and=
 receive RTCP on a port allocated according to the<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; usual port-selecti=
on rules (either the port pair, or a signalled port<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; if the &quot;a=3Dr=
tcp:&quot; attribute [10] is also included).&nbsp; This will occur<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; when talking to a =
peer that does not understand the &quot;a=3Drtcp-mux&quot;<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:EN-GB">&nbsp;&nbsp; attribute.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Q: The question is whether it is allowed to include =
a=3Drtcp-mux in an answer if the associated offer did NOT contain a=3Drtcp-=
mux.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The second last paragraph in the text above does say=
 that, if the answer wishes to do RTP/RTCP-mux, it includes a=3Drtcp-mux in=
 the answer.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">BUT, in my view that is it based on the first paragr=
aph, which assumes a=3Drtcp-mux is also included in the offer.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Or, am I wrong? Is it allowed to include a=3Drtcp-mu=
x in the answer, even if it&#8217;s not included in the offer? If so, how w=
ill the offerer then indicate whether mux is used or not.<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>
</div>
</div>
</div>
</span></div>
</div>
</span></div>
</div>
</blockquote>
</span>
</body>
</html>

--_000_D3730864710F0eckelcuciscocom_--


From nobody Tue May 31 09:45:07 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 483BD12D749 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 09:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6mWzh-fz3xA8 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 09:45:03 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D08A12D629 for <mmusic@ietf.org>; Tue, 31 May 2016 09:45:03 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id f8so139244611ioe.3 for <mmusic@ietf.org>; Tue, 31 May 2016 09:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=oK/UUq5hBwIppHLFzdlB/wNforXbqtqovGbZogXcURI=; b=a4KvunGncQatvxTwQpBtCEbP/cPT8yz8amvt+X2VrpJn5IWiJmljvEuLdp+X+OTnZP bFgHJDvXKltCKMqHIMPGcKIwSNBusaGW4VY6/OqniR9MhOD+brYeXWeKSlaUFFttWwhE 0EgVtRQ/I15qeolj/QED2EI6a0xUnPRELUsANWRTUO0Zef9J1izwW8ErT/mJXbMKEBQx i9HshVJo4LR67uiSfIw1IqPuqD6IXA6kN/zv2ifAVjMQEsprH4ga5p68nHFkzK+OCLa4 vpU4Lj7W8VrjRsMc+MV+bvsUwaL/cK+LL7DqtgWJR0X7GY2Gyjv9QFcjTKcJG7ckCpIb aQkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=oK/UUq5hBwIppHLFzdlB/wNforXbqtqovGbZogXcURI=; b=eVPymS62nb5lAyU2QESAJAq++y28nuzRjvfXdUJ7qTSkwXULGOKvsGerloZwvpcf1i 5uLFsmTZPHcEV9xjblDVyrDzDoRF9wIVTgedGeIZtbJjXskcMRAgsFpICN8ZvUyptkvc GKAYuPF9rVoonjARYq6yHWmYBnbiL15X4bM7E3bWRYfU4r9McwvsYhjCTFNPpbR0WPiC 7vhPjN6D9+zWoxufLLEKF1fG98hsLTq9XPBgC5guUC7gVmnLIYz/sXMnoMJoXX56FGsM L8mIrPq7IPOuekKH6xHDb6kTZpHLzU2nPvZbN8GkVoBm9VPSHYKYw5xDTSZEOKOAhk79 SlHg==
X-Gm-Message-State: ALyK8tJQIXJ+muOAtMRoxYmAYoLAB9B4HSC7fhZPx3SDHnHskhx9ZPbiW+11f1wYUP2OIw==
X-Received: by 10.107.17.165 with SMTP id 37mr28081299ior.101.1464713102616; Tue, 31 May 2016 09:45:02 -0700 (PDT)
Received: from mail-it0-f47.google.com (mail-it0-f47.google.com. [209.85.214.47]) by smtp.gmail.com with ESMTPSA id n10sm13430207iod.39.2016.05.31.09.45.02 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 31 May 2016 09:45:02 -0700 (PDT)
Received: by mail-it0-f47.google.com with SMTP id i127so33099208ita.1 for <mmusic@ietf.org>; Tue, 31 May 2016 09:45:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.110.214 with SMTP id w205mr15514423itc.47.1464713101842;  Tue, 31 May 2016 09:45:01 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 31 May 2016 09:45:01 -0700 (PDT)
In-Reply-To: <D3730864.710F0%eckelcu@cisco.com>
References: <D371D129.967D%christer.holmberg@ericsson.com> <D3730864.710F0%eckelcu@cisco.com>
Date: Tue, 31 May 2016 12:45:01 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv8iPX06Xy4Cb0cA1V=PE1oHePZh0-W8tbriMc4iFyP1g@mail.gmail.com>
Message-ID: <CAD5OKxv8iPX06Xy4Cb0cA1V=PE1oHePZh0-W8tbriMc4iFyP1g@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a114a97762269f4053426185e
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/LPo3Zg13-zlpvXELiC-nkFZSpWo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] FW: [AVTCORE] RTP/RTCP-mux: Attribute in answer if not included in offer?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 16:45:05 -0000

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

Christer,

Technically speaking RFC5761 does not prohibit including rtcp-mux in the
answer if it was not present in the offer. This being said, if offerer
supports rtcp-mux, according to RFC5761 it must include rtcp-mux in the
offer. This means including rtcp-mux in the answer will imply sending this
attribute to the end point which does not support it. I would also say,
that since offerer did not send rtcp-mux attribute it should pretend not to
support rtcp-mux and ignore rtcp-mux in the answer to be compliant with
RFC5761.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra">Christer,</div><div class=3D"gm=
ail_extra"><br></div><div class=3D"gmail_extra">Technically speaking RFC576=
1 does not prohibit including rtcp-mux in the answer if it was not present =
in the offer. This being said, if offerer supports rtcp-mux, according to=
=C2=A0RFC5761 it must include=C2=A0rtcp-mux in the offer. This means includ=
ing=C2=A0rtcp-mux in the answer will imply sending this attribute to the en=
d point which does not support it. I would also say, that since offerer did=
 not send rtcp-mux attribute it should pretend not to support rtcp-mux and =
ignore rtcp-mux in the answer to be compliant with RFC5761.</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Regards,</div><div cl=
ass=3D"gmail_extra"><div><div class=3D"gmail_signature" data-smartmail=3D"g=
mail_signature">_____________<br>Roman Shpount</div></div></div></div>

--001a114a97762269f4053426185e--


From nobody Tue May 31 10:54:45 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 348C712D553 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 10:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ufA_wgKwdh_Q for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 10:54:42 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50FAD12B05E for <mmusic@ietf.org>; Tue, 31 May 2016 10:54:42 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id f8so141213744ioe.3 for <mmusic@ietf.org>; Tue, 31 May 2016 10:54:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=dtA16Xd4fHiC7vJFnIOH2bU3q2g8HXVsgKEqxk+qTbk=; b=Yr8Db2SVpYgRbRrR1yFzFbqmwGM26Jyj3nRYLIocSKLNTnTazaP4MZp7F4A1olj5R0 5SYgHTCUOuWSIiV4W8vCHvssZA59DIWLsVTX1sFoGB0DZB+5ACwwwLIvFWQu/UsNHOLx YrE//82Pqeye7f7Sne5Tj/9qEYc4q0g3qoTfuGz1SP9DIu2eE9HPH5PfMZ0FHkQAYkUc pJYmO6vpzr1k+UmcwsZ2+G0H7u1MXrNMl5BqYLctu2koitBl0YxP7rRDXNTNGMN78/Ay EkBqGgVqIdtM5BTqXdN2UEIS8q83P453BSFnUcjdVBPz0I8jVPGKMAQUCvD5NdaFAFz8 BlPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=dtA16Xd4fHiC7vJFnIOH2bU3q2g8HXVsgKEqxk+qTbk=; b=a5T8ltziydCbfipHYpC41mg+jDi3D/Yt3mt6XCpALNxGYl6zxQgSiyDvQqmwAB6I9U nvNfLnlAjAmJGMDEN00gTYbvDtdvcvSa8wLg2l63GJdhtukObvHczGr7OhOTXncolXJv nB4ljWKjShehEBkspt7AJIDNPGfy+ArY44sQPlt5MXaxn6lJX1nhi9WGsulECyAklXZV EOxZATd29dDGAi+fNyhV+tPvPztf4GK5tigCElZrBYsyUk297zVOPcfPbwOs1Tmk39lz K4dJhm6wLDRH8lALovC1DfugWVA1r8w1w45OSEBm23F3xvWdUv3fSCa2txp7sl3XGAdF 97EA==
X-Gm-Message-State: ALyK8tLGmlnj7QqmXdel4J3kAAOM4nDZ2GSvzXP2kvoEwCov6L2hHYuDY/dqYahPBmmRDA==
X-Received: by 10.107.159.84 with SMTP id i81mr27490424ioe.29.1464717276671; Tue, 31 May 2016 10:54:36 -0700 (PDT)
Received: from mail-it0-f53.google.com (mail-it0-f53.google.com. [209.85.214.53]) by smtp.gmail.com with ESMTPSA id j137sm6156613ioe.18.2016.05.31.10.54.35 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 31 May 2016 10:54:35 -0700 (PDT)
Received: by mail-it0-f53.google.com with SMTP id e62so66762159ita.1 for <mmusic@ietf.org>; Tue, 31 May 2016 10:54:35 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.155.132 with SMTP id o126mr15317679itd.95.1464717270460;  Tue, 31 May 2016 10:54:30 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 31 May 2016 10:54:30 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se>
Date: Tue, 31 May 2016 13:54:30 -0400
X-Gmail-Original-Message-ID: <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com>
Message-ID: <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c05d1589a495005342710f9
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/fnbkFBR9lYUisG_-za8tkdX8M8w>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 17:54:44 -0000

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

On Mon, May 30, 2016 at 1:50 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >> In my opinion that is covered by not mandating SHA-256 on the receiving
> side.
> >
> > End points should also be able to generate session descriptions with a
> single SHA-1 fingerprint per m= line on the
> > sending side, when communicating with legacy end points. Legacy end
> points might not be able to handle multiple fingerprints and might not
> support SHA-256.
>
> I hear what you are saying, but the question is whether we want to cover
> that, or whether we assume that the endpoint in such cases simply have to
> operate in "legacy mode", i.e. according to the old RFC.
>

Whether we want to cover this was exactly the question that what I was
asking. Since we make provisions in the new document to accept descriptions
with a single legacy fingerprint, should we also allow description
generation with a single legacy fingerprint? Otherwise we can simply say
that handling session descriptions with legacy hashes is not allowed and
end points should switch to "legacy mode" described by old RFC if they wish
to support it.

Also, does it ever makes sense to include hashes in the answer which were
not present in the offer? What are the chances for the end point to support
verification of some hash but not generation?

If we introduce the restriction that answer MUST only include hash
algorithms from the offer, and if legacy hashes are acceptable, offers from
legacy end point will automatically generate the legacy compatible answer.

Regards,
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure" data-smartmail=3D"gmail_signature">On Mon, May 30, 2016 at 1:50 PM, Ch=
rister Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@e=
ricsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span=
> wrote:<br></div></div><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span c=
lass=3D"">&gt;&gt; In my opinion that is covered by not mandating SHA-256 o=
n the receiving side.<br>
&gt;<br>
&gt; End points should also be able to generate session descriptions with a=
 single SHA-1 fingerprint per m=3D line on the<br>
&gt; sending side, when communicating with legacy end points. Legacy end po=
ints might not be able to handle multiple fingerprints and might not suppor=
t SHA-256.<br>
<br>
</span>I hear what you are saying, but the question is whether we want to c=
over that, or whether we assume that the endpoint in such cases simply have=
 to operate in &quot;legacy mode&quot;, i.e. according to the old RFC.<br><=
/blockquote><div><br></div><div>Whether we want to cover this was exactly t=
he question that what I was asking. Since we make provisions in the new doc=
ument to accept descriptions with a single legacy fingerprint, should we al=
so allow description generation with a single legacy fingerprint? Otherwise=
 we can simply say that handling session descriptions with legacy hashes is=
 not allowed and end points should switch to &quot;legacy mode&quot; descri=
bed by old RFC if they wish to support it.</div><div><br></div><div>Also, d=
oes it ever makes sense to include hashes in the answer which were not pres=
ent in the offer? What are the chances for the end point to support verific=
ation of some hash but not generation?</div><div><br></div><div>If we intro=
duce the restriction that answer MUST only include hash algorithms from the=
 offer, and if legacy hashes are acceptable, offers from legacy end point w=
ill automatically generate the legacy compatible answer.</div><div><br></di=
v><div>Regards,</div><div><div class=3D"gmail_signature" data-smartmail=3D"=
gmail_signature">_____________<br>Roman Shpount</div></div><div>=C2=A0</div=
></div></div></div>

--94eb2c05d1589a495005342710f9--


From nobody Tue May 31 11:34:53 2016
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A81212D556 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 11:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k9yUR8j0LudE for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 11:34:50 -0700 (PDT)
Received: from resqmta-ch2-02v.sys.comcast.net (resqmta-ch2-02v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C103912D14B for <mmusic@ietf.org>; Tue, 31 May 2016 11:34:50 -0700 (PDT)
Received: from resomta-ch2-12v.sys.comcast.net ([69.252.207.108]) by comcast with SMTP id 7oRrbeYFL8DPn7oV7bwCkc; Tue, 31 May 2016 18:34:49 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1464719689; bh=THjXUZJUcReNgLXpITiAlr9SnSzqOTEiGBp/23kH2lA=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=BU7DTQ1Rh8FW42N4I3wZB6kvvyICmRPDw4/KJUqjp62sRP6ToAy3l4CiReW106fs8 Zpb5VkEVVIYl/oSp5+/AUuKcL2Sa9BjGcnma8UfS1SJV8WwRD8zyYJF0w7AH1yxh2J +RH8Px7NH7NNsZQjBDGOx+/2zKgju95zRIjqZSwJDOayW4KbpcUdvctc98s49NuoLR 5ODLu1eMLA0Xga5AgBNeTXPqB180yLrTcW7JsLeVmvIXj+4jdJpAJDKD4lROBZwFPg GyAbLHpj9SFOKc20NqyW0wPQpeLetMKJSkNcq2kQFvFMR9j8WMYS8BKTRMgmheam1r vXabtfP+lEAzQ==
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-12v.sys.comcast.net with comcast id 16ap1t0043KdFy1016apLv; Tue, 31 May 2016 18:34:49 +0000
To: Roman Shpount <roman@telurix.com>, Christer Holmberg <christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se> <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <2a5ebdc5-20c6-8a55-c6fd-f18957f2c4e4@alum.mit.edu>
Date: Tue, 31 May 2016 14:34:48 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.1.0
MIME-Version: 1.0
In-Reply-To: <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/Of2XhWRm5RtbS29_bZF8dXM4grU>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 18:34:52 -0000

On 5/31/16 1:54 PM, Roman Shpount wrote:
> On Mon, May 30, 2016 at 1:50 PM, Christer Holmberg
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> wrote:
>
>     >> In my opinion that is covered by not mandating SHA-256 on the receiving side.
>     >
>     > End points should also be able to generate session descriptions with a single SHA-1 fingerprint per m= line on the
>     > sending side, when communicating with legacy end points. Legacy end points might not be able to handle multiple fingerprints and might not support SHA-256.
>
>     I hear what you are saying, but the question is whether we want to
>     cover that, or whether we assume that the endpoint in such cases
>     simply have to operate in "legacy mode", i.e. according to the old RFC.
>
>
> Whether we want to cover this was exactly the question that what I was
> asking. Since we make provisions in the new document to accept
> descriptions with a single legacy fingerprint, should we also allow
> description generation with a single legacy fingerprint? Otherwise we
> can simply say that handling session descriptions with legacy hashes is
> not allowed and end points should switch to "legacy mode" described by
> old RFC if they wish to support it.
>
> Also, does it ever makes sense to include hashes in the answer which
> were not present in the offer? What are the chances for the end point to
> support verification of some hash but not generation?
>
> If we introduce the restriction that answer MUST only include hash
> algorithms from the offer, and if legacy hashes are acceptable, offers
> from legacy end point will automatically generate the legacy compatible
> answer.

According to the old scheme the hash would always match that of the 
cert. If the certs in the two directions used different hashs, then so 
would the fingerprints.

The rule you are suggesting would break that.

	Thanks,
	Paul


From nobody Tue May 31 11:45:08 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 240E212D14B for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 11:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqMLrL2pfyqt for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 11:45:05 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3080A12D5FA for <mmusic@ietf.org>; Tue, 31 May 2016 11:45:02 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-67-574ddbac6f8f
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id A4.30.27088.CABDD475; Tue, 31 May 2016 20:45:00 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0294.000; Tue, 31 May 2016 20:44:14 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoAgAAEbAD//8AqMIAAZnKAgAQpdQCAADi0gIAATZ/d///gtwD//9XcMAA44hMA///SSxA=
Date: Tue, 31 May 2016 18:44:13 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B38025D6F@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se> <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com>
In-Reply-To: <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B38025D6FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrEIsWRmVeSWpSXmKPExsUyM2K7tO6a277hBv/nC1tcO/OP0WLq8scs Fis2HGC1mHFhKrMDi8ff9x+YPHbOusvusWTJTyaPW1MKAliiuGxSUnMyy1KL9O0SuDJ2T/nH WrDIueLBvCb2BsYNjl2MHBwSAiYS/bf5uxg5gUwxiQv31rN1MXJxCAkcYZT4+PYVK4SzhFHi z9LZ7CANbAIWEt3/tEEaRARUJf5+n8wEYjMLVEl0Hn/BDmILC9hLbHxyhwmixkFi59urLCBz RASamCT2vD7KCpJgAWo+9P4FE8hMXgFfiWuvXCB2dfJKXF84gRmkhlMgUOLAjINgQxmBrvt+ ag3UMnGJW0/mM0FcLSCxZM95ZghbVOLl43+sELaSxIrtlxgh6vMlti5vZAGxeQUEJU7OfMIy gVF0FpJRs5CUzUJSNgvoPGYBTYn1u/QhShQlpnQ/ZIewNSRa58xlRxZfwMi+ilG0OLU4KTfd yEgvtSgzubg4P08vL7VkEyMwJg9u+W2wg/Hlc8dDjAIcjEo8vA+2+4QLsSaWFVfmHmKU4GBW EuEVueUbLsSbklhZlVqUH19UmpNafIhRmoNFSZzX/6ViuJBAemJJanZqakFqEUyWiYNTqoEx 9YPR/dbOgqmZ18PLdnGlC72x2aGxKf/Yzj8Mdy6F3XlVGPmu43I+s7VH+5YNEawnTO6dmZEh J/3N6MKJyYt55toznVjDNan6LndY8/S1dxdvDd/qkfrW+ITjWcVZX5fPfL9e/aH//5sv3NU2 vOVnOrTa7uK36uI1Fl3Xunr/FdnJyO2Z9213lxJLcUaioRZzUXEiAOtLdqrFAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/EUkyonwcXTep8lBm3fYASB3sm-8>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 18:45:07 -0000

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

SGksDQoNCj5XaGV0aGVyIHdlIHdhbnQgdG8gY292ZXIgdGhpcyB3YXMgZXhhY3RseSB0aGUgcXVl
c3Rpb24gdGhhdCB3aGF0IEkgd2FzIGFza2luZy4gU2luY2Ugd2UgbWFrZQ0KPmluIHRoZSBuZXcg
ZG9jdW1lbnQgdG8gYWNjZXB0IGRlc2NyaXB0aW9ucyB3aXRoIGEgc2luZ2xlIGxlZ2FjeSBmaW5n
ZXJwcmludCwgc2hvdWxkIHdlIGFsc28gYWxsb3cNCj5kZXNjcmlwdGlvbiBnZW5lcmF0aW9uIHdp
dGggYSBzaW5nbGUgbGVnYWN5IGZpbmdlcnByaW50PyBPdGhlcndpc2Ugd2UgY2FuIHNpbXBseSBz
YXkgdGhhdA0KPmhhbmRsaW5nIHNlc3Npb24gZGVzY3JpcHRpb25zIHdpdGggbGVnYWN5IGhhc2hl
cyBpcyBub3QgYWxsb3dlZCBhbmQgZW5kIHBvaW50cyBzaG91bGQgc3dpdGNoDQo+dG8gImxlZ2Fj
eSBtb2RlIiBkZXNjcmliZWQgYnkgb2xkIFJGQyBpZiB0aGV5IHdpc2ggdG8gc3VwcG9ydCBpdC4N
Cg0KSSBkb27igJl0IHRoaW5rIHdlIGNhbiByZWZlciB0byB0ZXh0IHRoYXQgZG9lc27igJl0IGV4
aXN0IGFueW1vcmUgKHNpbmNlIHRoZSBkcmFmdCB1cGRhdGVzIGl0KS4NCg0KQnV0LCBpZiB5b3Ug
d2FudCB0byBjb3ZlciBpdCwgd2hhdCBhYm91dDoNCg0KU0hPVUxELCB1bmxlc3MgdGhlIGVuZHBv
aW50IGtub3dzIHRoYXQgdGhlIHBlZXIgc3VwcG9ydHMgYSBzdHJvbmdlciBoYXNoIGFsZ29yaXRo
bSwgb3IgdW5sZXNzIHRoZSBlbmRwb2ludCBrbm93cyB0aGF0IHRoZSBwZWVyIGhhcyBub3QgYmVl
biB1cGdyYWRlZCB0byBzdXBwb3J0IHRoZSBTSEEtMjU2IGFsZ29yaXRobSwgb3IgdW5sZXNzIHRo
ZSBlbmRwb2ludCBpcyB1c2VkIGZvciBhIHNlcnZpY2UsIG9yIHdpdGhpbiBhbiBlbnZpcm9ubWVu
dCwgdGhhdCBtYW5kYXRlcyB1c2FnZSBvZiBzdHJvbmcgaGFzaCBhbGdvcml0aG1zDQoNClJlZ2Fy
ZHMsDQoNCkNocmlzdGVyDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpl
eHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgltc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0
IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29y
ZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9
IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0
aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3
RDttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Q7bXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPiZndDs8L3NwYW4+V2hldGhlciB3ZSB3YW50IHRvIGNvdmVyIHRoaXMgd2FzIGV4YWN0bHkg
dGhlIHF1ZXN0aW9uIHRoYXQgd2hhdCBJIHdhcyBhc2tpbmcuIFNpbmNlIHdlIG1ha2UNCjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7PC9z
cGFuPmluIHRoZSBuZXcgZG9jdW1lbnQgdG8gYWNjZXB0IGRlc2NyaXB0aW9ucyB3aXRoIGEgc2lu
Z2xlIGxlZ2FjeSBmaW5nZXJwcmludCwgc2hvdWxkIHdlIGFsc28gYWxsb3cNCjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj4mZ3Q7PC9zcGFuPmRl
c2NyaXB0aW9uIGdlbmVyYXRpb24gd2l0aCBhIHNpbmdsZSBsZWdhY3kgZmluZ2VycHJpbnQ/IE90
aGVyd2lzZSB3ZSBjYW4gc2ltcGx5IHNheSB0aGF0DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jmd0Ozwvc3Bhbj5oYW5kbGluZyBzZXNzaW9u
IGRlc2NyaXB0aW9ucyB3aXRoIGxlZ2FjeSBoYXNoZXMgaXMgbm90IGFsbG93ZWQgYW5kIGVuZCBw
b2ludHMgc2hvdWxkIHN3aXRjaA0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWYiPiZndDs8L3NwYW4+dG8gJnF1b3Q7bGVnYWN5IG1vZGUmcXVvdDsg
ZGVzY3JpYmVkIGJ5IG9sZCBSRkMgaWYgdGhleSB3aXNoIHRvIHN1cHBvcnQgaXQuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
SSBkb27igJl0IHRoaW5rIHdlIGNhbiByZWZlciB0byB0ZXh0IHRoYXQgZG9lc27igJl0IGV4aXN0
IGFueW1vcmUgKHNpbmNlIHRoZSBkcmFmdCB1cGRhdGVzIGl0KS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+QnV0
LCBpZiB5b3Ugd2FudCB0byBjb3ZlciBpdCwgd2hhdCBhYm91dDo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjpibGFjayI+U0hPVUxELCB1bmxlc3MgdGhlIGVuZHBvaW50IGtub3dzIHRoYXQgdGhlIHBlZXIg
c3VwcG9ydHMgYSBzdHJvbmdlciBoYXNoIGFsZ29yaXRobSwgb3IgdW5sZXNzIHRoZSBlbmRwb2lu
dCBrbm93cyB0aGF0IHRoZSBwZWVyIGhhcyBub3QgYmVlbiB1cGdyYWRlZCB0byBzdXBwb3J0DQog
dGhlIFNIQS0yNTYgYWxnb3JpdGhtLCBvciB1bmxlc3MgdGhlIGVuZHBvaW50IGlzIHVzZWQgZm9y
IGEgc2VydmljZSwgb3Igd2l0aGluIGFuIGVudmlyb25tZW50LCB0aGF0IG1hbmRhdGVzIHVzYWdl
IG9mIHN0cm9uZyBoYXNoIGFsZ29yaXRobXM8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Q2hyaXN0ZXI8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_7594FB04B1934943A5C02806D1A2204B38025D6FESESSMB209erics_--


From nobody Tue May 31 13:09:24 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6507E12D64E for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 13:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TrdHt3BH5QqT for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 13:09:21 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B5FD12D640 for <mmusic@ietf.org>; Tue, 31 May 2016 13:09:21 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id p64so1897017ioi.2 for <mmusic@ietf.org>; Tue, 31 May 2016 13:09:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=4be9MWPxmsHTDbGOmgrHTsreX8Mf/8ToyvJRICwNI1s=; b=CQvqRd9lhQBxqR0dZJsCO/SnNhcb261d65Q3FSzVcopfb3+RvyNX/l5aNj64HlPlwk lBsmbALQOE9U8hij2sNBh9lVov5kdMNamWe1S39OfDcbFhu/Tj8hmK/rfAdsHV6CDJUc n9wlrKNEAIuRWAT/PT0+83XdTKnM3t3JR/kI9qt8uftUBuiMCScbEOvlsS0jw6UzOdHh 6qHQxeWGZCvwzu78K01g1f9TdZ64HhtayDEPUOuToE0wmebpKRgy3FnHcqr/COcAWzni fMUOABL2EsIalKFjQo5rarQslLBbUarN+h7IBQ7OBgfAVNypdgbfLwTNK2E+cY7cuGt1 RjbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=4be9MWPxmsHTDbGOmgrHTsreX8Mf/8ToyvJRICwNI1s=; b=Y+ZLvUbAIV6MZL0jNdGa2E6g7IMOyg5w0yqqbtUnSFqrw6Hv5jkjcGi7pT5noLQeU5 HoTq57BOdVznQnB15C2IOQlOyGHUaegB2S8Hiv6F1xvJrEUYBnS0+4zb88VjuETMP3L2 mBWQp5mdWz+rJcUk1aMLhTlL0+RfENbfnIAPvFthBoipPFAxyTei6anDNxg32ssKkmJT rWRiPddokdyy5hsIssuA8Jq9QTEjvObXjxpFGruZvHp8vJIT33z80rwXyBCYmw/gYTL4 QEjhjvxjWolTFFHtJtx1OnLfR+YD78/kBj1mPocc7qSdkHnD1+D50OJeXS/YsXkSpblA aW9Q==
X-Gm-Message-State: ALyK8tLY1IHtrb/yoQOGYjZ8TEg1ns7BDbghEDPzLENymquZ7ZUlWMvl7BtUWi03PdxmVg==
X-Received: by 10.107.131.105 with SMTP id f102mr451580iod.136.1464725360856;  Tue, 31 May 2016 13:09:20 -0700 (PDT)
Received: from mail-it0-f51.google.com (mail-it0-f51.google.com. [209.85.214.51]) by smtp.gmail.com with ESMTPSA id w207sm10318580itc.20.2016.05.31.13.09.19 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 31 May 2016 13:09:19 -0700 (PDT)
Received: by mail-it0-f51.google.com with SMTP id e62so70479515ita.1 for <mmusic@ietf.org>; Tue, 31 May 2016 13:09:19 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.54.85 with SMTP id l82mr16353733itl.18.1464725359659; Tue, 31 May 2016 13:09:19 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 31 May 2016 13:09:19 -0700 (PDT)
In-Reply-To: <2a5ebdc5-20c6-8a55-c6fd-f18957f2c4e4@alum.mit.edu>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se> <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com> <2a5ebdc5-20c6-8a55-c6fd-f18957f2c4e4@alum.mit.edu>
Date: Tue, 31 May 2016 16:09:19 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuJX5c6HG3+YjwB5sARPw_NaQk-o+=BK=voRZ5Hjw2=Sg@mail.gmail.com>
Message-ID: <CAD5OKxuJX5c6HG3+YjwB5sARPw_NaQk-o+=BK=voRZ5Hjw2=Sg@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: multipart/alternative; boundary=001a1144e04ac1db62053428f241
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/bIrC36BLZJFAAh684LwEqplhQfo>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 20:09:23 -0000

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

On Tue, May 31, 2016 at 2:34 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:

> According to the old scheme the hash would always match that of the cert.
> If the certs in the two directions used different hashs, then so would the
> fingerprints.
>
> The rule you are suggesting would break that.
>

I do not think there is a single implementation that actually looks at the
hash function that is used to sign the certificate when checking the
fingerprint, so in reality this will not break anything. For RFC4572
implementations there is rarely a reason to look at certificate signature,
since it will only verify who signed the certificate and certificates used
by RFC4572 are normally self signed. This entire requirement was in RFC4572
by mistake.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure" data-smartmail=3D"gmail_signature">On Tue, May 31, 2016 at 2:34 PM, Pa=
ul Kyzivat <span dir=3D"ltr">&lt;<a href=3D"mailto:pkyzivat@alum.mit.edu" t=
arget=3D"_blank">pkyzivat@alum.mit.edu</a>&gt;</span> wrote:<br></div></div=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-l=
eft-color:rgb(204,204,204);padding-left:1ex">According to the old scheme th=
e hash would always match that of the cert. If the certs in the two directi=
ons used different hashs, then so would the fingerprints.<br>
<br>
The rule you are suggesting would break that.<br></blockquote><div><br></di=
v><div>I do not think there is a single implementation that actually looks =
at the hash function that is used to sign the certificate when checking the=
 fingerprint, so in reality this will not break anything. For RFC4572 imple=
mentations there is rarely a reason to look at certificate signature, since=
 it will only verify who signed the certificate and certificates used by RF=
C4572 are normally self signed. This entire requirement was in RFC4572 by m=
istake.</div><div><div class=3D"gmail_signature" data-smartmail=3D"gmail_si=
gnature">_____________<br>Roman Shpount</div></div><div>=C2=A0</div></div><=
/div></div>

--001a1144e04ac1db62053428f241--


From nobody Tue May 31 13:10:33 2016
Return-Path: <roman@telurix.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B5512D651 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 13:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNV1TVOewURT for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 13:10:29 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4809212D659 for <mmusic@ietf.org>; Tue, 31 May 2016 13:10:29 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id f8so1864046ioe.3 for <mmusic@ietf.org>; Tue, 31 May 2016 13:10:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=n9W/uckb0+sdwT/fEbVAzVOpKuAmEGnmt5dUKlNUx6o=; b=JRyk2sA+F2S0qEdMHVy6cEhc7sEb/1L+hTKO8yyiIzLgKnGCY5Cb921YjzVK16IDBW tB7RCqRrgA4WzZWXmbKJi+LTyXWuEC3hI3cJ3FDZPuLlXYyxL5cdUzvrEhKRoYcnfMN2 +ya4uFCoySTB8aaAPMRou9gX/8HrpAcvYfhqBregAG6AHtr2BvgzPZObIbBMEl8osTfv 9pZi4AcpJI9x14RY0M4klEmZk082USA6046hRM5LRjWU4Xbs1DRNSGdf2Xzp3HJ/aWlv aEqIRYY4BXecIgKF89hOwwhqJYykTeVSkRCXTqse2AIoOcp5WPMtasyiSlIb7D/usurT ASEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=n9W/uckb0+sdwT/fEbVAzVOpKuAmEGnmt5dUKlNUx6o=; b=D6qOPNMPw6q5b0cckSp9KLu72qPBS+s01erFzzN9bPo3ej6soZac3mYJIHpoJqYYXw A97Pwvr0oRFWW9De8S5SFB7ya8/p4JKRBPTrQfYGJO36trStA5gn3Ox5hDN0uLJwNu1C 9w7VEIw+SqeaFhnoBf/L7Vr1fM6DeY7hdhPgAq/F+xS6fyPiTcES323GN72X/f0aN6HZ nheFE321ZASVHUqPA5CRZ35vMAkKlsjw1bGQMHAdSVCos6c/fgtqjwSUI7EoocNY0G2L HNRD5/BQL0lpNu5cSKFBloisgy2S5DINUJJjyEGPJxg+wFfS6j4MRrxFJUvHEdEyuehg 4ukA==
X-Gm-Message-State: ALyK8tKJBss1dyXqns1eecwfJ/Z7SsQEq2SJTqOR3um+RVkxo3aUMVY2h+jhAbkKQF6CuA==
X-Received: by 10.107.15.39 with SMTP id x39mr401523ioi.125.1464725428671; Tue, 31 May 2016 13:10:28 -0700 (PDT)
Received: from mail-it0-f42.google.com (mail-it0-f42.google.com. [209.85.214.42]) by smtp.gmail.com with ESMTPSA id p132sm11930533iod.29.2016.05.31.13.10.27 for <mmusic@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Tue, 31 May 2016 13:10:27 -0700 (PDT)
Received: by mail-it0-f42.google.com with SMTP id i127so1860816ita.1 for <mmusic@ietf.org>; Tue, 31 May 2016 13:10:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.36.227.131 with SMTP id d125mr519941ith.18.1464725427584; Tue, 31 May 2016 13:10:27 -0700 (PDT)
Received: by 10.36.144.69 with HTTP; Tue, 31 May 2016 13:10:27 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B38025D6F@ESESSMB209.ericsson.se>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se> <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B38025D6F@ESESSMB209.ericsson.se>
Date: Tue, 31 May 2016 16:10:27 -0400
X-Gmail-Original-Message-ID: <CAD5OKxuFuvbi-RFvWTcZTaBNij3k+RV+SFNf9Fh3DnEpShzNng@mail.gmail.com>
Message-ID: <CAD5OKxuFuvbi-RFvWTcZTaBNij3k+RV+SFNf9Fh3DnEpShzNng@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=94eb2c111620ce2cb2053428f6a4
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/kAivOT0oYUnWuJqFG5koSOyDweQ>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2016 20:10:31 -0000

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

On Tue, May 31, 2016 at 2:44 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> >Whether we want to cover this was exactly the question that what I was
> asking. Since we make
>
> >in the new document to accept descriptions with a single legacy
> fingerprint, should we also allow
>
> >description generation with a single legacy fingerprint? Otherwise we
> can simply say that
>
> >handling session descriptions with legacy hashes is not allowed and end
> points should switch
>
> >to "legacy mode" described by old RFC if they wish to support it.
>
>
>
> I don=E2=80=99t think we can refer to text that doesn=E2=80=99t exist any=
more (since the
> draft updates it).
>
>
>
> But, if you want to cover it, what about:
>
>
>
> SHOULD, unless the endpoint knows that the peer supports a stronger hash
> algorithm, or unless the endpoint knows that the peer has not been upgrad=
ed
> to support the SHA-256 algorithm, or unless the endpoint is used for a
> service, or within an environment, that mandates usage of strong hash
> algorithms
>
>
>
This covers all my examples, so I would be fine with this language.
_____________
Roman Shpount

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"gmail_signat=
ure" data-smartmail=3D"gmail_signature"><br></div></div><div class=3D"gmail=
_quote">On Tue, May 31, 2016 at 2:44 PM, Christer Holmberg <span dir=3D"ltr=
">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">c=
hrister.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span>Whether we want to cover this was exactly the question=
 that what I was asking. Since we make<br></p><div><div><div><div><span cla=
ss=3D""><p class=3D"MsoNormal"><u></u></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Cal=
ibri,sans-serif">&gt;</span>in the new document to accept descriptions with=
 a single legacy fingerprint, should we also allow
<u></u><u></u></p><span class=3D"">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span>description generation with a single legacy fingerprin=
t? Otherwise we can simply say that
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span>handling session descriptions with legacy hashes is no=
t allowed and end points should switch
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">&gt;</span>to &quot;legacy mode&quot; described by old RFC if the=
y wish to support it.<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Cal=
ibri,sans-serif">I don=E2=80=99t think we can refer to text that doesn=E2=
=80=99t exist anymore (since the draft updates it).<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif">But, if you want to cover it, what about:<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;font-family:Calibri,=
sans-serif;color:black">SHOULD, unless the endpoint knows that the peer sup=
ports a stronger hash algorithm, or unless the endpoint knows that the peer=
 has not been upgraded to support
 the SHA-256 algorithm, or unless the endpoint is used for a service, or wi=
thin an environment, that mandates usage of strong hash algorithms</span><s=
pan style=3D"font-size:11pt;font-family:Calibri,sans-serif"><u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><br></p></div></div></div></div></div></div></blockq=
uote><div><br></div><div>This covers all my examples, so I would be fine wi=
th this language.</div><div><div class=3D"gmail_signature" data-smartmail=
=3D"gmail_signature">_____________<br>Roman Shpount</div></div><div>=C2=A0<=
/div></div></div></div>

--94eb2c111620ce2cb2053428f6a4--


From nobody Tue May 31 19:52:11 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E86E12D0B0 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 19:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ur7B6wme5B_D for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 19:52:09 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE1612B02B for <mmusic@ietf.org>; Tue, 31 May 2016 19:52:09 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id y126so5184900qke.1 for <mmusic@ietf.org>; Tue, 31 May 2016 19:52:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Is58L9ZP1eu3uRqaW3tJk0DS3M3FVoEytdt3OG6Rr5s=; b=LxfxjAm3iR1LYuncfJEVCnOhxajbGuqCJxZlqTjjmNDwGGUHpObIsgb1B0mzVbXmUD BCX8iOTji7xHPbYR5c5S5x0Wt9SPY9g0yIHgMx0rTCgNBawUepAHF14qUCy9di5K7Bvu LCpLzRwYBvZSP3xlWtC4YM9lLoxhoYGWrYqKaMg7KAICK/dsOn2ik4VFMMogUFgJ7nCC Kifz7bQ+RaV1ZU6GFHu8IrQXF83lwVKdZXJFBSFeq3T+t5/cqtVX/vRUkcosrhM4V+Ww DhCWE076qoliri3oA3et6AGz3eEvDTNkTpEDzWNnAcq88jCYmXESexpAb0fuZOR0Xb0p +a+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Is58L9ZP1eu3uRqaW3tJk0DS3M3FVoEytdt3OG6Rr5s=; b=dnVKbjoogZDf3Ia8HqOrYuaBUib85NHB7SpKhMJsEVBW0k7zJfy6J6kzRfYvSaavGa UrmFqKOZdXkc+1tXZE5lugNcVGbW0Ho/cg6RwZJcQTbZ+OlOQZnpFnvkMwcEPEplC+oW epqZLBygoSnrhoNCbsXhHPzyTsll1OCqJz/9wouBS+TiU0n8U/SBrn7QjXOlFUoehW4r UiMlkqN+A75jDLrNWCNNZ7fcRmd+XuKo30brwH9+4H1kaORY08NafFY5cJ6hUhsQCr6u syfY+fqFuwyNnVzmlFb87yo4Zy+tGYLQEhGrlsv6ejRPi8OKIU5ennN1CXX2yIWX+IhK UyIQ==
X-Gm-Message-State: ALyK8tJ4PO3otFktcpATOuwl7H+aiLpnR1VBmFezoNKoZOM8/H2ltyD0q+3UxICLeU/b0hJdI3v3kXBRnpmHcQ==
MIME-Version: 1.0
X-Received: by 10.200.54.108 with SMTP id n41mr1350710qtb.18.1464749528132; Tue, 31 May 2016 19:52:08 -0700 (PDT)
Received: by 10.140.104.110 with HTTP; Tue, 31 May 2016 19:52:07 -0700 (PDT)
In-Reply-To: <CAD5OKxuFuvbi-RFvWTcZTaBNij3k+RV+SFNf9Fh3DnEpShzNng@mail.gmail.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se> <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B38025D6F@ESESSMB209.ericsson.se> <CAD5OKxuFuvbi-RFvWTcZTaBNij3k+RV+SFNf9Fh3DnEpShzNng@mail.gmail.com>
Date: Wed, 1 Jun 2016 12:52:07 +1000
Message-ID: <CABkgnnX4CJJwfQnED6TA_Sq2HOHA2tnNKjsGnXpQXr_P+OLisA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/1c3evVei7xD8f4bog3Hg4ij8DTc>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 02:52:10 -0000

On 1 June 2016 at 06:10, Roman Shpount <roman@telurix.com> wrote:
>> SHOULD, unless the endpoint knows that the peer supports a stronger hash
>> algorithm, or unless the endpoint knows that the peer has not been upgraded
>> to support the SHA-256 algorithm, or unless the endpoint is used for a
>> service, or within an environment, that mandates usage of strong hash
>> algorithms
>>
>>
>
> This covers all my examples, so I would be fine with this language.

Might as well be a MUST given the extensive list of caveats.

Editorial: The last comma can be removed, or you could turn this into
a bullet list of exemptions.


From nobody Tue May 31 23:28:15 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2C612D148 for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 23:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OCCtzc3LfKQg for <mmusic@ietfa.amsl.com>; Tue, 31 May 2016 23:28:12 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E32912D12A for <mmusic@ietf.org>; Tue, 31 May 2016 23:28:12 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-d9-574e80799be1
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.183.48]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 63.17.27088.9708E475; Wed,  1 Jun 2016 08:28:09 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0294.000; Wed, 1 Jun 2016 08:28:08 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
Thread-Index: AQHRtSvFlj02GsdUjEqN/h66uVwldJ/G2V+AgADkx4CAAGOpgIAAAaaAgAA66nD//+ymgIAAJPaQ///fdYCAABD5AIAABAeAgAAA6oCAAOs3gIABvEKAgAAif4CAACIs/oABJNaA///5JAAABOE4L///6iUAgAA3FYCAAAZ+gIAAKGoAgAAEbAD//8AqMIAAZnKAgAQpdQCAADi0gIAATZ/d///gtwD//9XcMAA44hMA///SSxD//6xPgP/+6GSA//1hVgA=
Date: Wed, 1 Jun 2016 06:28:08 +0000
Message-ID: <D3745B43.97DC%christer.holmberg@ericsson.com>
References: <e1d3b783-efeb-c52b-9e15-98cd66997690@cisco.com> <7594FB04B1934943A5C02806D1A2204B37FE6BB6@ESESSMB209.ericsson.se> <CAD5OKxv9=tCQ3ZP6RKTZwKw_GiNTc4h_FBgKxOReHUkwZgfQ4Q@mail.gmail.com> <CABkgnnWZtBheFTbaWT58ptx9BuG+WO9emeditNcsF4WDq6JhxQ@mail.gmail.com> <ecac3518-6c23-6e5c-6df1-854a48bd4ebd@alum.mit.edu> <CABkgnnVDSkxmymheeK=qyMxnD2-AiVHJU5Cf3GrHmGwcaS530Q@mail.gmail.com> <D36B255A.90C8%christer.holmberg@ericsson.com> <D36CA01E.93ED%christer.holmberg@ericsson.com> <CAD5OKxt+TTzvE9fZmkRstoaji5pRcs+w7Z=o8puds=hQ_ZSxjA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF0C94@ESESSMB209.ericsson.se> <D36DCF44.950D%christer.holmberg@ericsson.com> <CABkgnnVk1cu6SmGztw9KULimy=C4WVGG8MWuHafSwir8XKtamg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF3B58@ESESSMB209.ericsson.se> <CABkgnnU_r+Va52+2eP49MXj-dX5QQXBq7EjOzk+n+FuneO728Q@mail.gmail.com> <D36E05CF.9553%christer.holmberg@ericsson.com> <CAD5OKxvqPpmF6pJzQ_F==wjZnsE+YdqCHnn-DxrPs5uHM47sTQ@mail.gmail.com> <2a554789-0668-74f0-4bb4-e2908daa5e91@alum.mit.edu> <CAD5OKxuuc30VpkC0O0Jf321RzwYHXXbAXo034v0n3kfvxSuauQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B37FF4E53@ESESSMB209.ericsson.se> <CAD5OKxv769ETv6mvkJLGm6f9MMCe4hxZ6uh6Yt=4gcWEBYVqUw@mail.gmail.com> <D371CF1B.966A%christer.holmberg@ericsson.com> <CAD5OKxt8Sx-VYkyMXGz6XYTqBDkeTvowAg+SSu1AtTbvh_DWQg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FBC2@ESESSMB209.ericsson.se> <CAD5OKxtwkPC6qCR4qKWuMb=K6pDj45PeVV93JvUE1Xm97WL_tQ@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B3801FC74@ESESSMB209.ericsson.se> <CAD5OKxt1vbKBQtAwC2DcMiEX1BvErtrO1k2XaKCo+e0t=QAZRA@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B38025D6F@ESESSMB209.ericsson.se> <CAD5OKxuFuvbi-RFvWTcZTaBNij3k+RV+SFNf9Fh3DnEpShzNng@mail.gmail.com> <CABkgnnX4CJJwfQnED6TA_Sq2HOHA2tnNKjsGnXpQXr_P+OLisA@mail.gmail.com>
In-Reply-To: <CABkgnnX4CJJwfQnED6TA_Sq2HOHA2tnNKjsGnXpQXr_P+OLisA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EC70527FA522EB47B4BE77C4230591D6@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrIIsWRmVeSWpSXmKPExsUyM2K7gW5lg1+4QcMDVYtrZ/4xWkxd/pjF YsWGA6wWMy5MZXZg8fj7/gOTx85Zd9k9liz5yeRxa0pBAEsUl01Kak5mWWqRvl0CV8aiEztZ CppZK9buW8PSwPiFuYuRk0NCwETizb/9TBC2mMSFe+vZuhi5OIQEjjBK9O35xgjhLGaUmDvz AUsXIwcHm4CFRPc/bZAGEYEgiYcPH7OA2MwCvhIvF0AMFRawl7h6+TITRI2DxM63V1lA5ogI TGOSWL3uE1gRi4CKxMf5u1lBbF4BK4nJJ84zQSy7zSex68xWsASnQKDErZ9XGUFsRqDzvp9a wwSxTVzi1pP5UGcLSCzZcx7qHVGJl4//gfWKCuhJfLk3jxEirijx8dU+RoheHYkFuz+xQdjW EtNXHmaFsLUlli18zQxxkKDEyZlPWCYwSsxCsm4WkvZZSNpnIWmfhaR9ASPrKkbR4tTipNx0 IyO91KLM5OLi/Dy9vNSSTYzAiD245bfBDsaXzx0PMQpwMCrx8CZw+oULsSaWFVfmHmKU4GBW EuEtLQYK8aYkVlalFuXHF5XmpBYfYpTmYFES5/V/qRguJJCeWJKanZpakFoEk2Xi4JRqYCyc 4s6+al7xfuamr3IXK+t25LP4Fzivm19TEN8VJn43e97CE11J17NO5jAJ7Fx8aadqc+C9Jcyu XiUtZx7LZvd97lx346Qu9wvnphmme7ie3XI1uieyQILB8fnbR5c+Hz4sbBXbJ1tUbGB+Y5E2 f1ZFmuez2v9rulcceqyVrMVQXtIcKWn8UImlOCPRUIu5qDgRAGou0svUAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/mmusic/oV0V9yqSUrQrrnbWOXa5O55FbvE>
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-4572-update-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jun 2016 06:28:14 -0000

Hi,

>>> SHOULD, unless the endpoint knows that the peer supports a stronger
>>>hash
>>> algorithm, or unless the endpoint knows that the peer has not been
>>>upgraded
>>> to support the SHA-256 algorithm, or unless the endpoint is used for a
>>> service, or within an environment, that mandates usage of strong hash
>>> algorithms
>>
>> This covers all my examples, so I would be fine with this language.
>
> Might as well be a MUST given the extensive list of caveats.

WFM.

> Editorial: The last comma can be removed, or you could turn this into
> a bullet list of exemptions.

Will be fixed.

Regards,

Christer

