
From nobody Thu Aug  4 20:45:08 2016
Return-Path: <paulej@packetizer.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05DCE12B05D for <avt@ietfa.amsl.com>; Thu,  4 Aug 2016 20:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.982
X-Spam-Level: 
X-Spam-Status: No, score=-1.982 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_NONE=-0.0001, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, TRACKER_ID=1.306] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZHLDYR6JZvS for <avt@ietfa.amsl.com>; Thu,  4 Aug 2016 20:45:03 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98A0812D14F for <avt@ietf.org>; Thu,  4 Aug 2016 20:45:03 -0700 (PDT)
Received: from [192.168.1.20] (cpe-098-122-181-215.nc.res.rr.com [98.122.181.215] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.15.2/8.15.2) with ESMTPSA id u753j1Ds005840 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <avt@ietf.org>; Thu, 4 Aug 2016 23:45:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1470368702; bh=ilS4CQXwR3gknaeVFtu3Tes2y6Z1qwYhNw3erIOYgBc=; h=From:To:Subject:Date:Reply-To; b=AKFpYj9KHfdV1ervAmnLvaDnbLhO8zmyBlsd0zzT82CQ9qCbdVGgUs/qyKjIe4NXK oXuElqczHF7eedjTEYQE+LiPy94cuPE1qb2lOEn4gEMCG7B7fa6fhO+/61W3E84rKB 4PBj+GcVzr/iKwLcDaUSrvJpbHM5Junl+zY9WH2g=
From: "Paul E. Jones" <paulej@packetizer.com>
To: avt@ietf.org
Date: Fri, 05 Aug 2016 03:45:08 +0000
Message-Id: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney>
User-Agent: eM_Client/7.0.26482.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MBF048CA5D-3C17-4BAB-9521-14EC418F637E"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6 (dublin.packetizer.com [10.137.60.122]); Thu, 04 Aug 2016 23:45:02 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/IRfLuNKglD3qhqwSz3v3t0CG6fA>
Subject: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 03:45:06 -0000

--------=_MBF048CA5D-3C17-4BAB-9521-14EC418F637E
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable

AVT,

There are now at least two implementation of RFC 7714 and at least two=20
interpretations of how to treat the master salt value when used with in=20
KDF.  So that we can ensure consistent implementation, it was suggested=20
that I bring this issue to the WG.

The issue has to do with the salt length and the KDF.  As you know, RFC=20
3711 uses AES-CM for the KDF and assumes an initial SRTP master salt=20
that is 14 octets in length (see section 5.3/RFC3711).  AES-GCM, though,=
=20
utilizes a 12 octet salt value.

We have this when AES-CM is used (example taken from RFC 3711) with a 14=
=20
octet salt:

index DIV kdr: 000000000000 label: 02 master salt:=20
0EC675AD498AFEEBB6960B3AABE6=20
----------------------------------------------- xor:=20
0EC675AD498AFEE9B6960B3AABE6 (x, PRF input)

This value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad zeros=
=20
on the right) to produce a 16-octet salt value that is then used in the=20
AES-CM KDF logic.

When the 12 octet salt used in AES-GCM is provided, libsrtp=20
(https://github.com/cisco/libsrtp) will assume that zeros are padded on=20
the right to produce a 14-octet salt value (to get the default master=20
salt length needed per section 5.3).  Thus, assuming a salt value of=20
0EC675AD498AFEEBB6960B3A, these steps are performed:

index DIV kdr: 000000000000 label: 02 master salt:=20
0EC675AD498AFEEBB6960B3A0000 (two padding octets on the right)=20
----------------------------------------------- xor:=20
0EC675AD498AFEE9B6960B3A0000 (x, PRF input)

Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e.,=20
pad zeros on the right) to produce a 16-octet salt value that is then=20
used in the AES-CM KDF logic.

However, there is a statement in 4.3.1/RFC3711 that says "Let x =3D key_id=
=20
XOR master_salt, where key_id and master_salt are aligned so that their=20
least significant bits agree (right-alignment)."  That might suggest=20
that the XOR should have been performed without padding as shown above=20
and as implemented in libsrtp.

If padding on the right was the wrong thing to do, that would mean that=20
the XOR step using the initial 12 octet AES-GCM salt should have been=20
this:

index DIV kdr: 000000000000 label: 02 master salt:=20
0EC675AD498AFEEBB6960B3A -------------------------------------------=20
xor: 0EC675AD4988FEEBB6960B3A (x, PRF input)

Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would=20
result in:
0EC675AD4988FEEBB6960B3A0000

However, this is only a 14 octet value and we need 16 octets for the=20
AES-CM KDF (which was the reason the step in 4.3.3 exists for the=20
default 14 octet salt).  Thus, we are short two octets.

We either need to pad the initial 12 octet AES-GCM input salt at the=20
start in some way to form the expected 14 octet salt value expected per=20
section 5.3 (the approach taken by libsrtp), or we need additional=20
padding after the above x*2^16 step (e.g., introduce a second x*2^16=20
step).

Given that at least two implementers interpreted the specs differently,=20
I think it would be of benefit to discuss this in the WG and document=20
the proper behavior.

Paul
--------=_MBF048CA5D-3C17-4BAB-9521-14EC418F637E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head>

<style>#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f82=
8 blockquote.cite,#x44f08514173e4c178815cefa8ed99e10 blockquote.cite{
	margin-left:5px;
	margin-right:0px;
	padding-left:10px;
	padding-right:0px;
	border-left-width:1px;
	border-left-style:solid;
	border-left-color:#CCC;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 block=
quote.cite2,#x44f08514173e4c178815cefa8ed99e10 blockquote.cite2{
	margin-left:5px;
	margin-right:0px;
	padding-left:10px;
	padding-right:0px;
	border-left-width:1px;
	border-left-style:solid;
	border-left-color:#CCC;
	margin-top:3px;
	padding-top:0px;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 a =
img,#x44f08514173e4c178815cefa8ed99e10 a img{
	border:0px;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n pre,#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828=
 .plain tt{
	font-family:monospace;
	font-size:100%;
	font-weight:normal;
	font-style:normal;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n div{
	white-space:pre-wrap;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828{
	font-family:'Courier New';
	font-size:10pt;
	color:#000;
	margin-left:0px;
	margin-right:8px;
	background-color:#FFF;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n pre,#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828=
 .plain tt{
	font-family:'Courier New';
	font-size:10pt;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 block=
quote{
	display:none;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 block=
quote.cite{
	padding-left:10px;
	margin-left:5px;
	border-left-color:#CCC;
	border-left-width:1px;
	border-left-style:solid;
	padding-right:0px;
	margin-right:0px;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 block=
quote.cite2{
	margin-top:3px;
	padding-top:0px;
	padding-left:10px;
	margin-left:5px;
	border-left-color:#CCC;
	border-left-width:1px;
	border-left-style:solid;
	padding-right:0px;
	margin-right:0px;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n pre,#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828=
 .plain tt{
	font-size:100%;
	font-family:monospace;
	font-weight:normal;
	font-style:normal;
}
#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb4304492ead054c8c2539f828 #x496=
c9607052d430f8a776ee24adff4ae,#x44f08514173e4c178815cefa8ed99e10 #xda4c2fbb=
4304492ead054c8c2539f828 .plain pre,#x44f08514173e4c178815cefa8ed99e10 #xda=
4c2fbb4304492ead054c8c2539f828 .plain tt,#x44f08514173e4c178815cefa8ed99e10=
 #xda4c2fbb4304492ead054c8c2539f828{
	font-size:11pt;
	font-family:Calibri;
}
#x44f08514173e4c178815cefa8ed99e10{
	font-family:Calibri;
	font-size:11pt;
}#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 bloc=
kquote.cite,#x32b9284632b64626b878f71eefaea4b4 blockquote.cite{
	margin-left:5px;
	margin-right:0px;
	padding-left:10px;
	padding-right:0px;
	border-left-width:1px;
	border-left-style:solid;
	border-left-color:#CCC;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 block=
quote.cite2,#x32b9284632b64626b878f71eefaea4b4 blockquote.cite2{
	margin-left:5px;
	margin-right:0px;
	padding-left:10px;
	padding-right:0px;
	border-left-width:1px;
	border-left-style:solid;
	border-left-color:#CCC;
	margin-top:3px;
	padding-top:0px;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 a =
img,#x32b9284632b64626b878f71eefaea4b4 a img{
	border:0px;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n pre,#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828=
 .plain tt{
	font-family:monospace;
	font-size:100%;
	font-weight:normal;
	font-style:normal;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n div{
	white-space:pre-wrap;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828{
	font-family:'Courier New';
	font-size:10pt;
	color:#000;
	margin-left:0px;
	margin-right:8px;
	background-color:#FFF;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n pre,#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828=
 .plain tt{
	font-family:'Courier New';
	font-size:10pt;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 block=
quote{
	display:none;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 block=
quote.cite{
	padding-left:10px;
	margin-left:5px;
	border-left-color:#CCC;
	border-left-width:1px;
	border-left-style:solid;
	padding-right:0px;
	margin-right:0px;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 block=
quote.cite2{
	margin-top:3px;
	padding-top:0px;
	padding-left:10px;
	margin-left:5px;
	border-left-color:#CCC;
	border-left-width:1px;
	border-left-style:solid;
	padding-right:0px;
	margin-right:0px;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 .plai=
n pre,#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828=
 .plain tt{
	font-size:100%;
	font-family:monospace;
	font-weight:normal;
	font-style:normal;
}
#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb4304492ead054c8c2539f828 #x496=
c9607052d430f8a776ee24adff4ae,#x32b9284632b64626b878f71eefaea4b4 #xda4c2fbb=
4304492ead054c8c2539f828 .plain pre,#x32b9284632b64626b878f71eefaea4b4 #xda=
4c2fbb4304492ead054c8c2539f828 .plain tt,#x32b9284632b64626b878f71eefaea4b4=
 #xda4c2fbb4304492ead054c8c2539f828{
	font-size:11pt;
	font-family:Calibri;
}
#x32b9284632b64626b878f71eefaea4b4{
	font-family:Calibri;
	font-size:11pt;
}#xda4c2fbb4304492ead054c8c2539f828 blockquote.cite{
	margin-left:5px;
	margin-right:0px;
	padding-left:10px;
	padding-right:0px;
	border-left-width:1px;
	border-left-style:solid;
	border-left-color:#CCC;
}
#xda4c2fbb4304492ead054c8c2539f828 blockquote.cite2{
	margin-left:5px;
	margin-right:0px;
	padding-left:10px;
	padding-right:0px;
	border-left-width:1px;
	border-left-style:solid;
	border-left-color:#CCC;
	margin-top:3px;
	padding-top:0px;
}
#xda4c2fbb4304492ead054c8c2539f828 a img{
	border:0px;
}
#xda4c2fbb4304492ead054c8c2539f828 .plain pre,#xda4c2fbb4304492ead054c8c253=
9f828 .plain tt{
	font-family:monospace;
	font-size:100%;
	font-weight:normal;
	font-style:normal;
}
#xda4c2fbb4304492ead054c8c2539f828 .plain div{
	white-space:pre-wrap;
}
#xda4c2fbb4304492ead054c8c2539f828{
	font-family:'Courier New';
	font-size:10pt;
	color:#000;
	margin-left:0px;
	margin-right:8px;
	background-color:#FFF;
}
#xda4c2fbb4304492ead054c8c2539f828 .plain pre,#xda4c2fbb4304492ead054c8c253=
9f828 .plain tt{
	font-family:'Courier New';
	font-size:10pt;
}
#xda4c2fbb4304492ead054c8c2539f828 blockquote{
	display:none;
}
#xda4c2fbb4304492ead054c8c2539f828 blockquote.cite{
	padding-left:10px;
	margin-left:5px;
	border-left-color:#CCC;
	border-left-width:1px;
	border-left-style:solid;
	padding-right:0px;
	margin-right:0px;
}
#xda4c2fbb4304492ead054c8c2539f828 blockquote.cite2{
	margin-top:3px;
	padding-top:0px;
	padding-left:10px;
	margin-left:5px;
	border-left-color:#CCC;
	border-left-width:1px;
	border-left-style:solid;
	padding-right:0px;
	margin-right:0px;
}
#xda4c2fbb4304492ead054c8c2539f828 .plain pre,#xda4c2fbb4304492ead054c8c253=
9f828 .plain tt{
	font-size:100%;
	font-family:monospace;
	font-weight:normal;
	font-style:normal;
}
#xda4c2fbb4304492ead054c8c2539f828 a img{
	border:0px;
}
#xda4c2fbb4304492ead054c8c2539f828 #x496c9607052d430f8a776ee24adff4ae,#xda4=
c2fbb4304492ead054c8c2539f828 .plain pre,#xda4c2fbb4304492ead054c8c2539f828=
 .plain tt,#xda4c2fbb4304492ead054c8c2539f828{
	font-size:11pt;
	font-family:Calibri;
}blockquote.cite
{margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:=
 0px; border-left-width: 1px; border-left-style: solid; border-left-color:=
 rgb(204, 204, 204);}
blockquote.cite2
{margin-left: 5px; margin-right: 0px; padding-left: 10px; padding-right:=
 0px; border-left-width: 1px; border-left-style: solid; border-left-color:=
 rgb(204, 204, 204); margin-top: 3px; padding-top: 0px;}
a img
{border: 0px;}
body
{font-family: Calibri; font-size: 11pt;}
</style>
</head>
<body background=3D"">AVT,<div><br></div><div><span>There are now at least=
 two implementation of RFC 7714 and at least two interpretations of how =
to treat the master salt value when used with in KDF. &nbsp;So that we can=
 ensure consistent implementation, it was suggested that I bring this issue=
 to the WG.</span></div><div><span id=3D"xda4c2fbb4304492ead054c8c2539f828"=
><div style=3D"zoom: 1; overflow: auto;"><div><br></div><div>The issue has=
 to do with the salt length and the KDF. &nbsp;As you know, RFC 3711 uses=
 AES-CM for the KDF and assumes an initial SRTP master salt that is 14 octe=
ts in length (see section 5.3/RFC3711). &nbsp;AES-GCM, though, utilizes =
a 12 octet salt value.</div><div><br></div>
<div><span>We have this when AES-CM is used (example taken from RFC 3711)=
 with a 14 octet salt:</span></div>
<div>&nbsp;</div>
<div><pre class=3D"newpage" style=3D"font-size: 13px; margin-bottom: 0px;=
 margin-top: 0px;">      index DIV kdr:                 000000000000
      label:                       02
      master salt:   0EC675AD498AFEEBB6960B3AABE6
      -----------------------------------------------
      xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF input)</pre><=
/div>
<div>&nbsp;</div>
<div><div style=3D"font-size: 14.6667px;"><span>This value is then multipli=
ed by 2^16 per&nbsp;</span><span>4.3.3/RFC3711 (i.e., pad zeros on the righ=
t) to produce a 16-octet salt value that is then used in the AES-CM KDF =
logic.</span></div><div style=3D"font-size: 14.6667px;"><span><br></span></=
div><div style=3D"font-size: 14.6667px;"><span>When the 12 octet salt used=
 in AES-GCM is provided, libsrtp (</span><a href=3D"https://github.com/cisc=
o/libsrtp" style=3D"font-size: 14.6667px;">https://github.com/cisco/libsrtp=
</a><span>)</span><span>&nbsp;will assume that zeros are padded on the righ=
t to produce a 14-octet salt value (to get the default master salt length=
 needed per section 5.3). &nbsp;Thus,&nbsp;</span>assuming a salt value =
of 0EC675AD498AFEEBB6960B3A, these steps are performed:</div></div>
<div>&nbsp;</div>
<div><span id=3D"x496c9607052d430f8a776ee24adff4ae"><pre class=3D"newpage"=
 style=3D"font-size: 13px; margin-bottom: 0px; margin-top: 0px;">      inde=
x DIV kdr:                 000000000000
      label:                       02
      master salt:   0EC675AD498AFEEBB6960B3A<font color=3D"#ea161e" style=
=3D"font-weight: bold;">00</font><font color=3D"#ea161e" style=3D"font-weig=
ht: bold;">00</font>     (two padding octets on the right)
      -----------------------------------------------
      xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF input)</pre><=
/span></div>
<div>&nbsp;</div>
<div>Again, t<span>his value is then multiplied by 2^16 per&nbsp;</span><sp=
an>4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet salt=
 value that is then used in the AES-CM KDF logic.</span></div><div><br></di=
v><div>However, there is a statement in 4.3.1/RFC3711 that says "Let x =3D=
 key_id XOR master_salt, where key_id and master_salt are aligned so that=
 their least significant bits agree (right-alignment)." &nbsp;That might=
 suggest that the XOR should have been performed without padding as shown=
 above and as implemented in libsrtp.</div>
<div>&nbsp;</div>
<div>If padding on the right was the&nbsp;wrong thing to do,&nbsp;that woul=
d mean that the XOR step using the initial 12 octet AES-GCM salt should =
have been this:</div>
<div>&nbsp;</div>
<div><span id=3D"x21252b3ad05d454da31a16ae9ed87349"><pre class=3D"newpage"=
 style=3D"font-size: 13px; margin-bottom: 0px; margin-top: 0px;">      inde=
x DIV kdr:             000000000000
      label:                   02
      master salt:   0EC675AD498AFEEBB6960B3A
      -------------------------------------------
      xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)</pre></spa=
n></div>
<div>&nbsp;</div>
<div>Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would=
 result in:</div>
<div>0EC675AD4988FEEBB6960B3A0000</div>
<div>&nbsp;</div>
<div>However, this is only a 14 octet value and we need 16 octets for the=
 AES-CM KDF (which was the reason the step in 4.3.3 exists for the default=
 14 octet salt). &nbsp;Thus, we are short two octets.</div><div><br></div><=
div>We either need to pad the initial 12 octet AES-GCM input salt at the=
 start in some way to form the expected 14 octet salt value expected per=
 section 5.3 (the approach taken by libsrtp), or we need additional padding=
 after the above x*2^16 step (e.g., introduce a second x*2^16 step).</div><=
div><br></div><div>Given that at least two implementers interpreted the =
specs differently, I think it would be of benefit to discuss this in the=
 WG and document the proper behavior.</div><div><br></div>
<div>Paul</div></div></span></div></body></html>
--------=_MBF048CA5D-3C17-4BAB-9521-14EC418F637E--


From nobody Mon Aug  8 09:00:41 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1903A12B01B; Mon,  8 Aug 2016 09:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level: 
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFsMKkzLseIK; Mon,  8 Aug 2016 09:00:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4ECE12D0AC; Mon,  8 Aug 2016 09:00:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9FEA4B80E1B; Mon,  8 Aug 2016 09:00:38 -0700 (PDT)
To: arkamar@atlas.cz, schulzrinne@cs.columbia.edu, casner@acm.org, ronf@bluecoat.com, van@packetdesign.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160808160038.9FEA4B80E1B@rfc-editor.org>
Date: Mon,  8 Aug 2016 09:00:38 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/Rxe-HctqSEbb9kIR7vWT0Sorgv4>
Cc: rfc-editor@rfc-editor.org, iesg@ietf.org, avt@ietf.org
Subject: [AVTCORE] [Errata Held for Document Update] RFC3550 (4770)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 16:00:40 -0000

The following errata report has been held for document update 
for RFC3550, "RTP: A Transport Protocol for Real-Time Applications". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3550&eid=4770

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Petr Van?k <arkamar@atlas.cz>
Date Reported: 2016-08-08
Held by: Ben Campbell (IESG)

Section: 3.

Original Text
-------------
   RTP session: An association among a set of participants
      communicating with RTP.  A participant may be involved in multiple
      RTP sessions at the same time.  In a multimedia session, each
      medium is typically carried in a separate RTP session with its own
      RTCP packets unless the the encoding itself multiplexes multiple
      media into a single data stream.  A participant distinguishes
      multiple RTP sessions by reception of different sessions using
      different pairs of destination transport addresses, where a pair
      of transport addresses comprises one network address plus a pair
      of ports for RTP and RTCP.  All participants in an RTP session may
      share a common destination transport address pair, as in the case
      of IP multicast, or the pairs may be different for each
      participant, as in the case of individual unicast network
      addresses and port pairs.  In the unicast case, a participant may
      receive from all other participants in the session using the same
      pair of ports, or may use a distinct pair of ports for each.

Corrected Text
--------------
   RTP session: An association among a set of participants
      communicating with RTP.  A participant may be involved in multiple
      RTP sessions at the same time.  In a multimedia session, each
      medium is typically carried in a separate RTP session with its own
      RTCP packets unless the encoding itself multiplexes multiple
      media into a single data stream.  A participant distinguishes
      multiple RTP sessions by reception of different sessions using
      different pairs of destination transport addresses, where a pair
      of transport addresses comprises one network address plus a pair
      of ports for RTP and RTCP.  All participants in an RTP session may
      share a common destination transport address pair, as in the case
      of IP multicast, or the pairs may be different for each
      participant, as in the case of individual unicast network
      addresses and port pairs.  In the unicast case, a participant may
      receive from all other participants in the session using the same
      pair of ports, or may use a distinct pair of ports for each.

Notes
-----
typo: double the in 5th line.

--------------------------------------
RFC3550 (draft-ietf-avt-rtp-new-12)
--------------------------------------
Title               : RTP: A Transport Protocol for Real-Time Applications
Publication Date    : July 2003
Author(s)           : H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson
Category            : DRAFT STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG


From nobody Mon Aug  8 13:47:43 2016
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7639912D0B5 for <avt@ietfa.amsl.com>; Mon,  8 Aug 2016 13:47:42 -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 BdFRICNl1SuU for <avt@ietfa.amsl.com>; Mon,  8 Aug 2016 13:47:40 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c: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 D67CA12B004 for <avt@ietf.org>; Mon,  8 Aug 2016 13:47:39 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id f65so138650354wmi.0 for <avt@ietf.org>; Mon, 08 Aug 2016 13:47:39 -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=I929R2CSeuEpRqVSzl7fblIqeBZrYQpsXedIva7Zk4A=; b=Ev4yQVV/BVPfRTLDapgeSxqSWArOPjLuyMBTXsV8pgXnO4noe4MlEGXh/ZBJbu4ut0 2aD8BZC+Xq/3aXcDnhQcsh4JF/cBJpKZkfwmYgeTwZUqWsl+rcVPifGKOr2jO2ZbOKlq WycRtOmrFG/jYS43ByFE/Z+VzZw/3fRuGbwafBa0kF1yRmPM/R5jI7gaVDqYBPQXL1xO d91wHj08Uq6brThVG58gQL2pOr1QunqkQdonZLB2iIuRF75KeEpL/qjqNh1ZirYtcU+l sSvOUVw2RDcH4KhklC3jp3VAnZhI2IPqfzcVd8j2HwgxxThp59tP4jy5Lai58y1bfwC/ Q79A==
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=I929R2CSeuEpRqVSzl7fblIqeBZrYQpsXedIva7Zk4A=; b=US2WH7QkMRvSlIe6rrAyQs/uA+TxBFNhx5vJyRIGUxLnmOv+1HcJ1wgNMvp2mzHODZ S5bVyyDIkW2oipyBXYs0h+Jj+72sjw47k7dXXX1REDFEuIOfXGxtGGJN8xRhI1kuZiIT s9bQSCCxYWzSt0MGqtVdCDL2x8Vx/pLnPysvN0huyazjO/lfSY+f4W3yAjv9P1F1GoJR iPgeIRop3FbFjyYWy8af7Z/CGN7NYFcglAJFg7YDydNM4KEHDWno/xUu34W9J/mv+CNy eMDydHmYMkKAk9t1xDB9FiQWEIO2Pf7VBZBkoe7mZ7/cecXhUAAY4RNyY/XhdC1sStLh N39Q==
X-Gm-Message-State: AEkoouv6DfyVLdiWt8hJ4Bw/r+FfBaE5nku/3iJLrPxPHY+lFs1go2macfN+EmNYiGLz3A==
X-Received: by 10.194.110.42 with SMTP id hx10mr85149234wjb.116.1470689258315;  Mon, 08 Aug 2016 13:47:38 -0700 (PDT)
Received: from RoniPC (bzq-79-176-39-238.red.bezeqint.net. [79.176.39.238]) by smtp.gmail.com with ESMTPSA id cw7sm751331wjb.38.2016.08.08.13.47.36 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 08 Aug 2016 13:47:37 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <avt@ietf.org>
References: 
In-Reply-To: 
Date: Mon, 8 Aug 2016 23:47:24 +0300
Message-ID: <011401d1f1b6$11d61640$358242c0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0115_01D1F1CF.372438A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdHnBtcWHcNW/BSpSGmgfXSGXHlRQgKrojzQ
Content-Language: he
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/dnxWeM1xrRxZkXUHEFTGMbViFQU>
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-5761-update-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 20:47:42 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0115_01D1F1CF.372438A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

I reviewed the document and have two editorial comments:

 

1.       In section 3.1 new text ""the answerer MUST NOT include an
attribute in the answer" I assume you wanted to say "MUST NOT include this
attribute" or "a=rtc-mux attribute"

2.       You can remove section 7 and  if no acknowledgments remove section
6

 

Roni Even 

 

From: Roni Even [mailto:ron.even.tlv@gmail.com] 
Sent: Tuesday, July 26, 2016 9:29 AM
To: avt@ietf.org
Cc: 'Christer Holmberg'
Subject: WGLC on draft-ietf-avtcore-5761-update-00

 

Hi,

I would like to start a WGLC on
https://tools.ietf.org/html/draft-ietf-avtcore-5761-update-00  , Update to
RFC5761
 
 

The WGLC will end on August 9th , 2016

 

Please review the draft and send comments to the list.

 

For the draft authors;  Are you aware of any IPR that applies to
draft-ietf-avtcore-5761-update-00?

 

If so, has this IPR been disclosed in compliance with IETF IPR rules?

The above question is needed for the document write-up when sent to
publication.
 
 

Thanks

 

Roni Even

AVTCore co-chair

 


------=_NextPart_000_0115_01D1F1CF.372438A0
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-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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><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;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:24.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Times New Roman","serif";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:360474213;
	mso-list-type:hybrid;
	mso-list-template-ids:714868150 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I reviewed the document =
and have two editorial comments:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:#1F497D'>In section 3.1 new text &#8220;&#8221;the =
answerer MUST NOT include an attribute in the answer&#8221; I assume you =
wanted to say &#8220;MUST NOT include this attribute&#8221; or =
&#8220;a=3Drtc-mux attribute&#8221;<o:p></o:p></span></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'color:#1F497D'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:#1F497D'>You can remove section 7 and&nbsp; if no =
acknowledgments remove section 6<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Roni Even =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'><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"'> =
Roni Even [mailto:ron.even.tlv@gmail.com] <br><b>Sent:</b> Tuesday, July =
26, 2016 9:29 AM<br><b>To:</b> avt@ietf.org<br><b>Cc:</b> 'Christer =
Holmberg'<br><b>Subject:</b> WGLC on =
draft-ietf-avtcore-5761-update-00<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I would =
like to start a WGLC on &nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-ietf-avtcore-5761-update-00">ht=
tps://tools.ietf.org/html/draft-ietf-avtcore-5761-update-00</a> &nbsp;, =
Update to RFC5761<span =
style=3D'color:black'><o:p></o:p></span></span></pre><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></pre><pre><span lang=3DEN =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></pre><p class=3DMsoNormal><span lang=3DEN>The WGLC will =
end on August 9<sup>th</sup> , 2016<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Please =
review the draft and send comments to the list.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>For the =
draft authors; &nbsp;Are you aware of any IPR that applies to <span =
style=3D'color:black'>draft-ietf-avtcore-5761-update-00?</span><o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>If so, has =
this IPR been disclosed in compliance with IETF IPR =
rules?<o:p></o:p></span></p><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The above =
question is needed for the document write-up when sent to =
publication.<o:p></o:p></span></pre><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></pre><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></pre><p class=3DMsoNormal>Thanks<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Roni =
Even<o:p></o:p></p><p =
class=3DMsoNormal>AVTCore&nbsp;co-chair<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_0115_01D1F1CF.372438A0--


From nobody Tue Aug  9 05:05:58 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB85A12D7E4 for <avt@ietfa.amsl.com>; Tue,  9 Aug 2016 05:05: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 5hHBF9o6FH64 for <avt@ietfa.amsl.com>; Tue,  9 Aug 2016 05:05:55 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EFC112D09A for <avt@ietf.org>; Tue,  9 Aug 2016 05:05:54 -0700 (PDT)
X-AuditID: c1b4fb30-ea88e980000009f9-33-57a9c7212cf1
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by  (Symantec Mail Security) with SMTP id 46.CB.02553.127C9A75; Tue,  9 Aug 2016 14:05:53 +0200 (CEST)
Received: from ESESSMB208.ericsson.se ([169.254.8.233]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0301.000; Tue, 9 Aug 2016 14:05:51 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, "avt@ietf.org" <avt@ietf.org>
Thread-Topic: WGLC on draft-ietf-avtcore-5761-update-00
Thread-Index: AdHnBtcWHcNW/BSpSGmgfXSGXHlRQgKrojzQACAgnkA=
Date: Tue, 9 Aug 2016 12:05:51 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BBCC463@ESESSMB208.ericsson.se>
References: <011401d1f1b6$11d61640$358242c0$@gmail.com>
In-Reply-To: <011401d1f1b6$11d61640$358242c0$@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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrDLMWRmVeSWpSXmKPExsUyM2K7q67i8ZXhBp+OSFm87FnJbvG3ndmB yWPnrLvsHkuW/GQKYIrisklJzcksSy3St0vgyji/bBpLwTvOitYjWxgbGJ+wdzFyckgImEj0 /JnC3MXIxSEksJ5R4uDPG2wQzmJGiYZ9x4EyHBxsAhYS3f+0QUwRAVeJ+zv9QXqFBcwkfi7/ yAJiiwiYS0w8f5MVwraSeLNqHth8FgEVifndJ8BsXgFfid2PFrKDjBECqv8y1RfE5AQavupn LEgFo4CYxPdTa5hAbGYBcYlbT+YzQVwpILFkz3lmCFtU4uXjf6wQtpLEiu2XGCHq9SRuTJ3C BmFrSyxb+JoZYqugxMmZT1gmMIrMQjJ2FpKWWUhaZiFpWcDIsopRtDi1OCk33chIL7UoM7m4 OD9PLy+1ZBMjMA4ObvltsIPx5XPHQ4wCHIxKPLwLTqwIF2JNLCuuzD3EKMHBrCTCq7VnZbgQ b0piZVVqUX58UWlOavEhRmkOFiVxXv+XiuFCAumJJanZqakFqUUwWSYOTqkGRlNvnVbNqREW 8vfT4k8nmh1ZVLeE1aUpJvrgyd7HuQZzuZ5Uv9OPWubptPRnR4b7Wfki3pniCesuzDOJkPCy ieNlntMpLZcZHlIaGztlA9eRHAXjgxm8Un9LMla7mjcLaYaLv3rEKVJiHXxJ+tbNzWY6h2PK FP7+bFM7wrPtlsH8SQEOi0KUWIozEg21mIuKEwHTIkBNfwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/q7HYvqjTvjU_mOfyoodFGD47nGw>
Subject: Re: [AVTCORE] WGLC on draft-ietf-avtcore-5761-update-00
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 12:05:57 -0000

Hi Roni,

> 1. In section 3.1 new text ""the answerer MUST NOT include an attribute i=
n the answer" I assume you wanted
> to say "MUST NOT include this attribute" or "a=3Drtc-mux attribute"

Correct.

I'll change the text to: "MUST NOT include an "a=3Drtcp-mux" attribute in t=
he answer"

> 2. You can remove section 7 and=A0 if no acknowledgments remove section 6

There will be some text in section 7 in the next version of the draft.

I will also add some names to section 6 :)

Regards,

Christer




From: Roni Even [mailto:ron.even.tlv@gmail.com]=20
Sent: Tuesday, July 26, 2016 9:29 AM
To: avt@ietf.org
Cc: 'Christer Holmberg'
Subject: WGLC on draft-ietf-avtcore-5761-update-00

Hi,
I would like to start a WGLC on =A0https://tools.ietf.org/html/draft-ietf-a=
vtcore-5761-update-00 =A0, Update to RFC5761


The WGLC will end on August 9th , 2016

Please review the draft and send comments to the list.

For the draft authors; =A0Are you aware of any IPR that applies to draft-ie=
tf-avtcore-5761-update-00?

If so, has this IPR been disclosed in compliance with IETF IPR rules?
The above question is needed for the document write-up when sent to publica=
tion.


Thanks

Roni Even
AVTCore=A0co-chair


From nobody Wed Aug 10 13:10:15 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9D48126FDC; Wed, 10 Aug 2016 13:10:14 -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.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147085981469.13509.17986341716477297044.idtracker@ietfa.amsl.com>
Date: Wed, 10 Aug 2016 13:10:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/VgozC8gq45FVU0hi11iU8Ob-P0A>
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-5761-update-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 20:10:14 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Core Maintenance of the IETF.

        Title           : Updates to RFC 5761
        Author          : Christer Holmberg
	Filename        : draft-ietf-avtcore-5761-update-01.txt
	Pages           : 5
	Date            : 2016-08-10

Abstract:
   This document updates RFC 5761 by clarifying the SDP offer/answer
   negotiation of RTP and RTCP multiplexing.  It makes it clear that an
   answerer can only include an "a=rtcp-mux" attribute in an SDP answer
   if the associated SDP offer contained the attribute.


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-5761-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 Wed Aug 10 13:11:43 2016
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D365812D16F for <avt@ietfa.amsl.com>; Wed, 10 Aug 2016 13:11:42 -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 joe_Yq6a2PBk for <avt@ietfa.amsl.com>; Wed, 10 Aug 2016 13:11:41 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3D7612D739 for <avt@ietf.org>; Wed, 10 Aug 2016 13:11:40 -0700 (PDT)
X-AuditID: c1b4fb3a-c7bff700000009bd-b9-57ab8a79230c
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by  (Symantec Mail Security) with SMTP id 17.47.02493.97A8BA75; Wed, 10 Aug 2016 22:11:39 +0200 (CEST)
Received: from ESESSMB208.ericsson.se ([169.254.8.233]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.03.0301.000; Wed, 10 Aug 2016 22:11:37 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "avt@ietf.org" <avt@ietf.org>
Thread-Topic: Draft new version: draft-ietf-avtcore-5761-update-01
Thread-Index: AdHzQ1RrVs7Smyf4QqKQMwS11uHzUw==
Date: Wed, 10 Aug 2016 20:11:37 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BBD6946@ESESSMB208.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_7594FB04B1934943A5C02806D1A2204B4BBD6946ESESSMB208erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM2K7h2511+pwgyWbuSxe9qxkd2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxqWDrgUfRSoOrHjO3MB4XqiLkZNDQsBEYv3FftYuRi4OIYH1 jBLvbjWyQzhLGCVOznrB1sXIwcEmYCHR/U8bpEFEQFGi9dpnRhBbWMBWYtnGi+wQcSeJUzea mCFsPYltp/6xgdgsAqoSq74vBbN5BXwlFt95AGYzCohJfD+1hgnEZhYQl7j1ZD4TxEECEkv2 nGeGsEUlXj7+xwphK0ms2H6JEeQcZoF8ia1H3SFGCkqcnPmEZQKj4Cwkk2YhVM1CUgVRoiOx YPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYhQtTi0uzk03MtJLLcpMLi7Oz9PLSy3ZxAgM+oNb flvtYDz43PEQowAHoxIPr4LUqnAh1sSy4srcQ4wSHMxKIryr2leHC/GmJFZWpRblxxeV5qQW H2KU5mBREuf1f6kYLiSQnliSmp2aWpBaBJNl4uCUamDUed6XvfZtsMq6FE7x+q4wO2s7xScl y01lf9i4R7CeP2u0TvV3/nGH6yL74rLPRtfI9l+VmzohQGJpxMNEs1+TrNonpCt96P76RnKh o3VTUWnaS1PffL6Ta792HAhcmXGN/fpzZRsNx1mWqUqTNSw2bL31R2ln8Opv4n6/Nt+a5WYu truw+KISS3FGoqEWc1FxIgDzVaLfdgIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/98GCjuPZPItfhptzO1JV1-Kfg-U>
Subject: [AVTCORE] Draft new version: draft-ietf-avtcore-5761-update-01
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Aug 2016 20:11:43 -0000

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

Hi,

Based on Roni's comments I've submitted a new version (-01) of draft-ietf-a=
vtcore-5761-update.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B4BBD6946ESESSMB208erics_
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 Roni&#8217;s comments I&#8217;ve submitted =
a new version (-01) of draft-ietf-avtcore-5761-update.<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_7594FB04B1934943A5C02806D1A2204B4BBD6946ESESSMB208erics_--


From nobody Fri Aug 12 08:28:50 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E951412D08C for <avt@ietfa.amsl.com>; Mon,  8 Aug 2016 08:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level: 
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.247, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yaey0_4yw7ym for <avt@ietfa.amsl.com>; Mon,  8 Aug 2016 08:37:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83D0512B044 for <avt@ietf.org>; Mon,  8 Aug 2016 08:37:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 66498B80B5E; Mon,  8 Aug 2016 08:37:25 -0700 (PDT)
To: schulzrinne@cs.columbia.edu, casner@acm.org, ronf@bluecoat.com, van@packetdesign.com, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, keith.drage@alcatel-lucent.com, roni.even@mail01.huawei.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160808153725.66498B80B5E@rfc-editor.org>
Date: Mon,  8 Aug 2016 08:37:25 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/Y01y8OT01PH_naSrzyT_dxrAMtM>
X-Mailman-Approved-At: Fri, 12 Aug 2016 08:28:48 -0700
Cc: rfc-editor@rfc-editor.org, avt@ietf.org, arkamar@atlas.cz
Subject: [AVTCORE] [Editorial Errata Reported] RFC3550 (4770)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Aug 2016 15:37:27 -0000

The following errata report has been submitted for RFC3550,
"RTP: A Transport Protocol for Real-Time Applications".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3550&eid=4770

--------------------------------------
Type: Editorial
Reported by: Petr Vaněk <arkamar@atlas.cz>

Section: 3.

Original Text
-------------
   RTP session: An association among a set of participants
      communicating with RTP.  A participant may be involved in multiple
      RTP sessions at the same time.  In a multimedia session, each
      medium is typically carried in a separate RTP session with its own
      RTCP packets unless the the encoding itself multiplexes multiple
      media into a single data stream.  A participant distinguishes
      multiple RTP sessions by reception of different sessions using
      different pairs of destination transport addresses, where a pair
      of transport addresses comprises one network address plus a pair
      of ports for RTP and RTCP.  All participants in an RTP session may
      share a common destination transport address pair, as in the case
      of IP multicast, or the pairs may be different for each
      participant, as in the case of individual unicast network
      addresses and port pairs.  In the unicast case, a participant may
      receive from all other participants in the session using the same
      pair of ports, or may use a distinct pair of ports for each.

Corrected Text
--------------
   RTP session: An association among a set of participants
      communicating with RTP.  A participant may be involved in multiple
      RTP sessions at the same time.  In a multimedia session, each
      medium is typically carried in a separate RTP session with its own
      RTCP packets unless the encoding itself multiplexes multiple
      media into a single data stream.  A participant distinguishes
      multiple RTP sessions by reception of different sessions using
      different pairs of destination transport addresses, where a pair
      of transport addresses comprises one network address plus a pair
      of ports for RTP and RTCP.  All participants in an RTP session may
      share a common destination transport address pair, as in the case
      of IP multicast, or the pairs may be different for each
      participant, as in the case of individual unicast network
      addresses and port pairs.  In the unicast case, a participant may
      receive from all other participants in the session using the same
      pair of ports, or may use a distinct pair of ports for each.

Notes
-----
typo: double the in 5th line.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC3550 (draft-ietf-avt-rtp-new-12)
--------------------------------------
Title               : RTP: A Transport Protocol for Real-Time Applications
Publication Date    : July 2003
Author(s)           : H. Schulzrinne, S. Casner, R. Frederick, V. Jacobson
Category            : DRAFT STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG


From nobody Sun Aug 14 23:52:45 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A95112D0D8; Sun, 14 Aug 2016 23:52:43 -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.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147124396323.13828.12305435543398952185.idtracker@ietfa.amsl.com>
Date: Sun, 14 Aug 2016 23:52:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/-hD1VKwK_b8ozh-Ik6L2ANmQDqk>
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rfc5285-bis-03.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2016 06:52:43 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Core Maintenance of the IETF.

        Title           : A General Mechanism for RTP Header Extensions
        Authors         : Roni Even
                          David Singer
                          Harikishan Desineni
	Filename        : draft-ietf-avtcore-rfc5285-bis-03.txt
	Pages           : 20
	Date            : 2016-08-12

Abstract:
   This document provides a general mechanism to use the header
   extension feature of RTP (the Real-Time Transport Protocol).  It
   provides the option to use a small number of small extensions in each
   RTP packet, where the universe of possible extensions is large and
   registration is de-centralized.  The actual extensions in use in a
   session are signaled in the setup information for that session.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5285-bis/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-avtcore-rfc5285-bis-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rfc5285-bis-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 Thu Aug 18 10:21:10 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E33912DA71; Thu, 18 Aug 2016 10:21:06 -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.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147154086624.27840.13399354322098770056.idtracker@ietfa.amsl.com>
Date: Thu, 18 Aug 2016 10:21:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/UnHz15MVZ27YLxISgG5SwB10nYs>
Cc: avt@ietf.org
Subject: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-18.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 17:21:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Audio/Video Transport Core Maintenance of the IETF.

        Title           : Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
        Authors         : Colin Perkins
                          Varun Singh
	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-18.txt
	Pages           : 25
	Date            : 2016-08-18

Abstract:
   The Real-time Transport Protocol (RTP) is widely used in telephony,
   video conferencing, and telepresence applications.  Such applications
   are often run on best-effort UDP/IP networks.  If congestion control
   is not implemented in these applications, then network congestion can
   lead to uncontrolled packet loss, and a resulting deterioration of
   the user's multimedia experience.  The congestion control algorithm
   acts as a safety measure, stopping RTP flows from using excessive
   resources, and protecting the network from overload.  At the time of
   this writing, however, while there are several proprietary solutions,
   there is no standard algorithm for congestion control of interactive
   RTP flows.

   This document does not propose a congestion control algorithm.  It
   instead defines a minimal set of RTP circuit breakers: conditions
   under which an RTP sender needs to stop transmitting media data, to
   protect the network from excessive congestion.  It is expected that,
   in the absence of long-lived excessive congestion, RTP applications
   running on best-effort IP networks will be able to operate without
   triggering these circuit breakers.  To avoid triggering the RTP
   circuit breaker, any standards-track congestion control algorithms
   defined for RTP will need to operate within the envelope set by these
   RTP circuit breaker algorithms.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-18

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-avtcore-rtp-circuit-breakers-18


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

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


From nobody Thu Aug 18 10:28:56 2016
Return-Path: <csp@csperkins.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBAE112D85F for <avt@ietfa.amsl.com>; Thu, 18 Aug 2016 10:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6sAEbNJiTY0Y for <avt@ietfa.amsl.com>; Thu, 18 Aug 2016 10:28:46 -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 2E0C512DA07 for <avt@ietf.org>; Thu, 18 Aug 2016 10:28:45 -0700 (PDT)
Received: from [81.187.2.149] (port=35444 helo=[192.168.0.91]) 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 1baR7P-0000Su-Js for avt@ietf.org; Thu, 18 Aug 2016 18:28:43 +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: <147154086624.27840.13399354322098770056.idtracker@ietfa.amsl.com>
Date: Thu, 18 Aug 2016 18:28:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <155AFB36-0048-429B-BD08-7E26AB2C4C6C@csperkins.org>
References: <147154086624.27840.13399354322098770056.idtracker@ietfa.amsl.com>
To: IETF AVTCore WG <avt@ietf.org>
X-Mailer: Apple Mail (2.3124)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/zB1hcLCiRSDbM6KcRehekCSjjsw>
Subject: Re: [AVTCORE] I-D Action: draft-ietf-avtcore-rtp-circuit-breakers-18.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 17:28:52 -0000

This version includes the change Varun suggested on the list on 26 July =
(=E2=80=9CIn section 4.5, I would propose reshuffling the statements a =
bit to make the guidance more appropriate=E2=80=9D):

OLD:
   What it means to cease transmission depends on the application. The
   intention is that the application will stop sending RTP data packets
   on a particular 5-tuple (transport protocol, source and destination
   ports, source and destination IP addresses), until whatever network
   problem that triggered the RTP circuit breaker has dissipated.  This
   could mean stopping a single RTP flow, or it could mean that multiple
   bundled RTP flows are stopped.=20

NEW:

   What it means to cease transmission depends on the application. This
   could mean stopping a single RTP flow, or it could mean that multiple
   bundled RTP flows are stopped. The intention is that the application =
will=20
   stop sending RTP data packets on a particular 5-tuple (transport =
protocol,=20
   source and destination ports, source and destination IP addresses), =
until=20
   whatever network problem that triggered the RTP circuit breaker has=20=

   dissipated. =20

There are no other changes.

Colin



> On 18 Aug 2016, at 18:21, Internet-Drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Audio/Video Transport Core =
Maintenance of the IETF.
>=20
>        Title           : Multimedia Congestion Control: Circuit =
Breakers for Unicast RTP Sessions
>        Authors         : Colin Perkins
>                          Varun Singh
> 	Filename        : draft-ietf-avtcore-rtp-circuit-breakers-18.txt
> 	Pages           : 25
> 	Date            : 2016-08-18
>=20
> Abstract:
>   The Real-time Transport Protocol (RTP) is widely used in telephony,
>   video conferencing, and telepresence applications.  Such =
applications
>   are often run on best-effort UDP/IP networks.  If congestion control
>   is not implemented in these applications, then network congestion =
can
>   lead to uncontrolled packet loss, and a resulting deterioration of
>   the user's multimedia experience.  The congestion control algorithm
>   acts as a safety measure, stopping RTP flows from using excessive
>   resources, and protecting the network from overload.  At the time of
>   this writing, however, while there are several proprietary =
solutions,
>   there is no standard algorithm for congestion control of interactive
>   RTP flows.
>=20
>   This document does not propose a congestion control algorithm.  It
>   instead defines a minimal set of RTP circuit breakers: conditions
>   under which an RTP sender needs to stop transmitting media data, to
>   protect the network from excessive congestion.  It is expected that,
>   in the absence of long-lived excessive congestion, RTP applications
>   running on best-effort IP networks will be able to operate without
>   triggering these circuit breakers.  To avoid triggering the RTP
>   circuit breaker, any standards-track congestion control algorithms
>   defined for RTP will need to operate within the envelope set by =
these
>   RTP circuit breaker algorithms.
>=20
>=20
> The IETF datatracker status page for this draft is:
> =
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/
>=20
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-avtcore-rtp-circuit-breakers-18
>=20
> A diff from the previous version is available at:
> =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtcore-rtp-circuit-breaker=
s-18
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt



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





From nobody Thu Aug 18 15:48:31 2016
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5442B12D79D; Thu, 18 Aug 2016 15:48:29 -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.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147156050933.27811.17057090027159590137.idtracker@ietfa.amsl.com>
Date: Thu, 18 Aug 2016 15:48:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/wpMJjZ9BxNPD_cB4Kpv_H_TrhVc>
Cc: avtcore-chairs@ietf.org, magnus.westerlund@ericsson.com, draft-ietf-avtcore-rtp-circuit-breakers@ietf.org, avt@ietf.org, The IESG <iesg@ietf.org>, rfc-editor@rfc-editor.org
Subject: [AVTCORE] Protocol Action: 'Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions' to Proposed Standard (draft-ietf-avtcore-rtp-circuit-breakers-18.txt)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Aug 2016 22:48:29 -0000

The IESG has approved the following document:
- 'Multimedia Congestion Control: Circuit Breakers for Unicast RTP
   Sessions'
  (draft-ietf-avtcore-rtp-circuit-breakers-18.txt) as Proposed Standard

This document is the product of the Audio/Video Transport Core
Maintenance Working Group.

The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa
Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-circuit-breakers/





Technical Summary

   The Real-time Transport Protocol (RTP) is widely used in telephony,
   video conferencing, and telepresence applications.  Such applications
   are often run on best-effort UDP/IP networks.  If congestion control
   is not implemented in the applications, then network congestion will
   deteriorate the user's multimedia experience.  This acts as a safety
   measure to prevent starvation of network resources denying other
   flows from access to the Internet, such measures are essential for an
   Internet that is heterogeneous and for traffic that is hard to
   predict in advance.  This document does not propose a congestion
   control algorithm; instead, it defines a minimal set of RTP circuit-
   breakers.  Circuit-breakers are conditions under which an RTP sender
   needs to stop transmitting media data in order to protect the network
   from excessive congestion.  It is expected that, in the absence of
   severe congestion, all RTP applications running on best-effort IP
   networks will be able to run without triggering these circuit
   breakers.  Any future RTP congestion control specification will be
   expected to operate within the constraints defined by these circuit
   breakers.

Working Group Summary

The WG has been quite diligent in working on this. There has been 
discussion if the specification addresses the right issue, and if the 
perimeter behavior it establish is the appropriate one. That consensus 
is definitely a rough consensus. A very good number of people have 
commented on the specification. 

Document Quality

There has been significant input, including simulations both for wired 
and wireless networks, the result of these simulations are referenced 
by the specification. Simon Perreault at JIVE did a trial deployment in 
their service. All of this has helped improving the solution and its 
definition significantly and helped verifying the behavior of the 
circuit breakers. 

Personnel

Magnus Westerlund is the document shepherd. 
Responsible AD is Ben Campbell


From nobody Sat Aug 20 06:29:21 2016
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53BE812D0A5 for <avt@ietfa.amsl.com>; Sat, 20 Aug 2016 06:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.768
X-Spam-Level: 
X-Spam-Status: No, score=-115.768 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.247, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 caIxZwh5VyTS for <avt@ietfa.amsl.com>; Sat, 20 Aug 2016 06:29:18 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3732E12D0A3 for <avt@ietf.org>; Sat, 20 Aug 2016 06:29:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3863; q=dns/txt; s=iport; t=1471699758; x=1472909358; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=lzEOg/dOVWJ2tMkBKBKGSrEoZGZJxxkl9AZXHgx5B4Y=; b=OGcOnrjgkjvT382RgI63iinA1akfuxnxUXYHFOPEAoC6dzC5Zs7XHu+r otsN2KBqNIEGqzGxuQKGRDpxMDQj3wn1vbF092BTfV5GCQ0p+7iTmN/Gv 2DJCJsh12+QiIDDIyWkHPONt2s/g0oGzIceWGJ5l33G/YyB5IpPuY2DMs 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AIAgA+WrhX/5JdJa1eg0RWfAe3bYF9J?= =?us-ascii?q?IV5AoFYOBQCAQEBAQEBAV4nhF4BAQQBAQE4PwULAgEIGB4QJwslAgQBDQWIKQg?= =?us-ascii?q?OuxkBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYgjCIJNgTmDB4Msgi8FiCuRHQGGH?= =?us-ascii?q?4h/j1CMP4N3AR42gh+BW3CGL38BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,549,1464652800"; d="scan'208";a="138012277"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Aug 2016 13:29:17 +0000
Received: from XCH-RTP-004.cisco.com (xch-rtp-004.cisco.com [64.101.220.144]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u7KDTG7L026403 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 20 Aug 2016 13:29:17 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-004.cisco.com (64.101.220.144) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 20 Aug 2016 09:29:16 -0400
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1210.000; Sat, 20 Aug 2016 09:29:16 -0400
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Paul Jones <paulej@packetizer.com>, Eric Rescorla <ekr@rtfm.com>, "Martin Thomson" <martin.thomson@gmail.com>
Thread-Topic: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
Thread-Index: AQHR+ubZ9mh23xIC9EenVde5Kf8BAw==
Date: Sat, 20 Aug 2016 13:29:16 +0000
Message-ID: <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney>
In-Reply-To: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney>
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.20.249.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3E9BC3536CEF1F489041D94868B8D672@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/9lPzX-FXpETE1sUM5mxFbZdRAJ8>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 13:29:20 -0000

Ekr, Martin,=20

Any thoughts on this ?

Thanks


> On Aug 4, 2016, at 9:45 PM, Paul E. Jones <paulej@packetizer.com> wrote:
>=20
> AVT,
>=20
> There are now at least two implementation of RFC 7714 and at least two in=
terpretations of how to treat the master salt value when used with in KDF. =
 So that we can ensure consistent implementation, it was suggested that I b=
ring this issue to the WG.
>=20
> The issue has to do with the salt length and the KDF.  As you know, RFC 3=
711 uses AES-CM for the KDF and assumes an initial SRTP master salt that is=
 14 octets in length (see section 5.3/RFC3711).  AES-GCM, though, utilizes =
a 12 octet salt value.
>=20
> We have this when AES-CM is used (example taken from RFC 3711) with a 14 =
octet salt:
> =20
>       index DIV kdr:                 000000000000
>       label:                       02
>       master salt:   0EC675AD498AFEEBB6960B3AABE6
>       -----------------------------------------------
>       xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF input)
>=20
> =20
> This value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad zeros =
on the right) to produce a 16-octet salt value that is then used in the AES=
-CM KDF logic.
>=20
> When the 12 octet salt used in AES-GCM is provided, libsrtp (https://gith=
ub.com/cisco/libsrtp) will assume that zeros are padded on the right to pro=
duce a 14-octet salt value (to get the default master salt length needed pe=
r section 5.3).  Thus, assuming a salt value of 0EC675AD498AFEEBB6960B3A, t=
hese steps are performed:
> =20
>       index DIV kdr:                 000000000000
>       label:                       02
>       master salt:   0EC675AD498AFEEBB6960B3A
> 0000
>      (two padding octets on the right)
>       -----------------------------------------------
>       xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF input)
>=20
> =20
> Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad=
 zeros on the right) to produce a 16-octet salt value that is then used in =
the AES-CM KDF logic.
>=20
> However, there is a statement in 4.3.1/RFC3711 that says "Let x =3D key_i=
d XOR master_salt, where key_id and master_salt are aligned so that their l=
east significant bits agree (right-alignment)."  That might suggest that th=
e XOR should have been performed without padding as shown above and as impl=
emented in libsrtp.
> =20
> If padding on the right was the wrong thing to do, that would mean that t=
he XOR step using the initial 12 octet AES-GCM salt should have been this:
> =20
>       index DIV kdr:             000000000000
>       label:                   02
>       master salt:   0EC675AD498AFEEBB6960B3A
>       -------------------------------------------
>       xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)
>=20
> =20
> Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would re=
sult in:
> 0EC675AD4988FEEBB6960B3A0000
> =20
> However, this is only a 14 octet value and we need 16 octets for the AES-=
CM KDF (which was the reason the step in 4.3.3 exists for the default 14 oc=
tet salt).  Thus, we are short two octets.
>=20
> We either need to pad the initial 12 octet AES-GCM input salt at the star=
t in some way to form the expected 14 octet salt value expected per section=
 5.3 (the approach taken by libsrtp), or we need additional padding after t=
he above x*2^16 step (e.g., introduce a second x*2^16 step).
>=20
> Given that at least two implementers interpreted the specs differently, I=
 think it would be of benefit to discuss this in the WG and document the pr=
oper behavior.
>=20
> Paul
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From nobody Sat Aug 20 13:53:56 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ADC4412D590; Sat, 20 Aug 2016 13:53:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.29.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147172643467.2722.10922545707934856868.idtracker@ietfa.amsl.com>
Date: Sat, 20 Aug 2016 13:53:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/A15UN50vLd6TVoFF-3SK2F3oAGs>
Cc: avtcore-chairs@ietf.org, avt@ietf.org
Subject: [AVTCORE] avtcore - New Meeting Session Request for IETF 97
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Aug 2016 20:53:55 -0000

A new meeting session request has just been submitted by Roni Even, a Chair of the avtcore working group.


---------------------------------------------------------
Working Group Name: Audio/Video Transport Core Maintenance
Area Name: Applications and Real-Time Area
Session Requester: Roni Even

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: tsvwg rmcat xrblock rtcweb payload mmusic dispatch avtext netvc perc
 Second Priority: tram sipcore lmap stir
 Third Priority: tls


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


From nobody Sun Aug 21 23:54:31 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8104212B00B for <avt@ietfa.amsl.com>; Sun, 21 Aug 2016 23:54: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 IobyvAPfIpsV for <avt@ietfa.amsl.com>; Sun, 21 Aug 2016 23:54:28 -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 9260312B042 for <avt@ietf.org>; Sun, 21 Aug 2016 23:54:28 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id t7so78875523qkh.1 for <avt@ietf.org>; Sun, 21 Aug 2016 23:54: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:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=pKltxxQogc5N29XeurfRUjE+lm+NIt5sHPJB/Pe61ms=; b=jvHcroCRqHRwJACLjuyZl6S/MXUv4+21Ng1M4X6+JoF0s51NVIldjyOKcpv9eVjvQ4 zUtRiVbg3zz4qL9oY4D48NDDsukjm+91TS0LJDRwENojJDniM/Xjf3+BNFzCEsW5+ZwM M0FfCuyrlM/+AzuA9PW1Z9AfQ+w+0tTRrrQq7VmrNP6gYuRvUy6XRSSKZLpWa3j/qCva yEFmXWJq09F7yfAPwtFZRTGJugERXLXfWmQvI8hM33t00hqtN8hPKUfwnnD3/zH/GiiZ TQksJt7cOwIBQjX9UYBMsr5VteodSvBvhCWohtRdioxZv/RoHRt/SvYDcZHlkcvPZsZC 499g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=pKltxxQogc5N29XeurfRUjE+lm+NIt5sHPJB/Pe61ms=; b=P/bYZNExNFyBXFGHFrl6F1ydDBnJuqHo64xASjtDSxvhDwz75YjikeeMNN8IYMxc6n fpXFIW2tX/S3PuEuq3FquF+UA2fheIKWwG5MzxP/YQigRK/b1DpR5ZPdSGpSiwN20t9Z BEHW5VpA5mcegJyu3IS9Y0rnTgB8x4QgD8Ou//s3rD/Jzm1S/iod8uB6oqfNmq8jeQsd U+vo9c1o4vC38S/B5AkwTjeHoclW7aOEFFbnVyEF982Fn9EY0AdgixPmGr904Ez6tPBN vujZ2H0kTJofAnIt717Uzc33WdkqA9MU1CttISHI4S2iEmXz/+JP3pNukHzcqMd+rrOr 8zww==
X-Gm-Message-State: AE9vXwMx6Uzw8/mmQvWtnGOAk+5GfUmxn3rRajlnsCfzr9ofvZ6LoyVLU7j+RgwCRcPdNZZqG01ZdTecSMOyLA==
X-Received: by 10.55.184.2 with SMTP id i2mr21296231qkf.261.1471848867638; Sun, 21 Aug 2016 23:54:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Sun, 21 Aug 2016 23:54:27 -0700 (PDT)
In-Reply-To: <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 22 Aug 2016 16:54:27 +1000
Message-ID: <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/DxJxHzkXXriCOMtA9_F7UkS-HpQ>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 06:54:30 -0000

I've just concluded that I don't understand RFC 7714.  That is either
because I'm too frazzled to think today, or because it's awful.  I
think that there's a good slice of tired, but I'm also fairly certain
that 7714 is horrendous.  It doesn't even use the same terminology as
RFC 3711.  It doesn't even use the AES-GCM (the thing defined in RFC
5116).

How did you even conclude that AES-GCM needed a 14 octet salt?  I
think that I would have concluded that it has a 12 octet salt.

On 20 August 2016 at 23:29, Cullen Jennings (fluffy) <fluffy@cisco.com> wro=
te:
>
> Ekr, Martin,
>
> Any thoughts on this ?
>
> Thanks
>
>
>> On Aug 4, 2016, at 9:45 PM, Paul E. Jones <paulej@packetizer.com> wrote:
>>
>> AVT,
>>
>> There are now at least two implementation of RFC 7714 and at least two i=
nterpretations of how to treat the master salt value when used with in KDF.=
  So that we can ensure consistent implementation, it was suggested that I =
bring this issue to the WG.
>>
>> The issue has to do with the salt length and the KDF.  As you know, RFC =
3711 uses AES-CM for the KDF and assumes an initial SRTP master salt that i=
s 14 octets in length (see section 5.3/RFC3711).  AES-GCM, though, utilizes=
 a 12 octet salt value.
>>
>> We have this when AES-CM is used (example taken from RFC 3711) with a 14=
 octet salt:
>>
>>       index DIV kdr:                 000000000000
>>       label:                       02
>>       master salt:   0EC675AD498AFEEBB6960B3AABE6
>>       -----------------------------------------------
>>       xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF input)
>>
>>
>> This value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad zeros=
 on the right) to produce a 16-octet salt value that is then used in the AE=
S-CM KDF logic.
>>
>> When the 12 octet salt used in AES-GCM is provided, libsrtp (https://git=
hub.com/cisco/libsrtp) will assume that zeros are padded on the right to pr=
oduce a 14-octet salt value (to get the default master salt length needed p=
er section 5.3).  Thus, assuming a salt value of 0EC675AD498AFEEBB6960B3A, =
these steps are performed:
>>
>>       index DIV kdr:                 000000000000
>>       label:                       02
>>       master salt:   0EC675AD498AFEEBB6960B3A
>> 0000
>>      (two padding octets on the right)
>>       -----------------------------------------------
>>       xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF input)
>>
>>
>> Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pa=
d zeros on the right) to produce a 16-octet salt value that is then used in=
 the AES-CM KDF logic.
>>
>> However, there is a statement in 4.3.1/RFC3711 that says "Let x =3D key_=
id XOR master_salt, where key_id and master_salt are aligned so that their =
least significant bits agree (right-alignment)."  That might suggest that t=
he XOR should have been performed without padding as shown above and as imp=
lemented in libsrtp.
>>
>> If padding on the right was the wrong thing to do, that would mean that =
the XOR step using the initial 12 octet AES-GCM salt should have been this:
>>
>>       index DIV kdr:             000000000000
>>       label:                   02
>>       master salt:   0EC675AD498AFEEBB6960B3A
>>       -------------------------------------------
>>       xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)
>>
>>
>> Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would r=
esult in:
>> 0EC675AD4988FEEBB6960B3A0000
>>
>> However, this is only a 14 octet value and we need 16 octets for the AES=
-CM KDF (which was the reason the step in 4.3.3 exists for the default 14 o=
ctet salt).  Thus, we are short two octets.
>>
>> We either need to pad the initial 12 octet AES-GCM input salt at the sta=
rt in some way to form the expected 14 octet salt value expected per sectio=
n 5.3 (the approach taken by libsrtp), or we need additional padding after =
the above x*2^16 step (e.g., introduce a second x*2^16 step).
>>
>> Given that at least two implementers interpreted the specs differently, =
I think it would be of benefit to discuss this in the WG and document the p=
roper behavior.
>>
>> Paul
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>


From nobody Mon Aug 22 05:38:31 2016
Return-Path: <paulej@packetizer.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6F9D12D126 for <avt@ietfa.amsl.com>; Mon, 22 Aug 2016 05:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.539
X-Spam-Level: 
X-Spam-Status: No, score=-1.539 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=packetizer.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8r4bTn6zS3q for <avt@ietfa.amsl.com>; Mon, 22 Aug 2016 05:38:27 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E1A812D146 for <avt@ietf.org>; Mon, 22 Aug 2016 05:38:27 -0700 (PDT)
Received: from dyn-229.arid.us (cpe-098-122-181-220.nc.res.rr.com [98.122.181.220] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.15.2/8.15.2) with ESMTPSA id u7MCcObI012732 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2016 08:38:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1471869504; bh=1o1/PEWlAXf/GERGlixrhaxmDvhxg0ktdSD7OyDZDl8=; h=In-Reply-To:References:Subject:From:Date:To:CC; b=ksLcjlhTYcCd5Lv8nR5O8GlVzmmhDqrrbYksKpHCg4Iddk/EwxruC3DnKXx/qo21G f1TW+K4e7QP4uS8aUqNY3NRapsOG9P79CQY0IFiTWTwluq6oMqzrX6IT4j8FiGQ7Fv nyqic5bmByzRqsvvwJTJw7Vuqy/QekDSDS8jSLYU=
User-Agent: K-9 Mail for Android
In-Reply-To: <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----P4BK8WA1QWFQ1QSSU0IP9RX2U4WVCF"
Content-Transfer-Encoding: 8bit
From: "Paul E. Jones" <paulej@packetizer.com>
Date: Mon, 22 Aug 2016 08:38:21 -0400
To: Martin Thomson <martin.thomson@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Message-ID: <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6 (dublin.packetizer.com [10.137.60.122]); Mon, 22 Aug 2016 08:38:24 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/z6mTnd22v3Wb4AnBAH65M3asUXM>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Aug 2016 12:38:29 -0000

------P4BK8WA1QWFQ1QSSU0IP9RX2U4WVCF
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8

Martin,

RFC 7714 uses a 12 octet salt, but this same same salt must be used in AES-CM as part of the KDF.  RFC 3711 assumes the input master salt for AES-CM is a 14 octet salt that is then transformed into a 16 octet salt used by the KDF.

Somehow, that 12 octet salt in RFC 7714 needs to be transformed into a 16 octet value, too, for use in the AES-CM based KDF.  What's missing are those steps, so different implementers made different assumptions to ultimately arrive at the needed 16 octets.

I think some guidance is needed in RFC 7714, since it defines a 12 octet salt and RFC 3711 assumes an input salt of 14 octets in length.

Paul


-------- Original Message --------
From: Martin Thomson <martin.thomson@gmail.com>
Sent: August 22, 2016 2:54:27 AM EDT
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: Paul Jones <paulej@packetizer.com>, Eric Rescorla <ekr@rtfm.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation

I've just concluded that I don't understand RFC 7714.  That is either
because I'm too frazzled to think today, or because it's awful.  I
think that there's a good slice of tired, but I'm also fairly certain
that 7714 is horrendous.  It doesn't even use the same terminology as
RFC 3711.  It doesn't even use the AES-GCM (the thing defined in RFC
5116).

How did you even conclude that AES-GCM needed a 14 octet salt?  I
think that I would have concluded that it has a 12 octet salt.

On 20 August 2016 at 23:29, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>
> Ekr, Martin,
>
> Any thoughts on this ?
>
> Thanks
>
>
>> On Aug 4, 2016, at 9:45 PM, Paul E. Jones <paulej@packetizer.com> wrote:
>>
>> AVT,
>>
>> There are now at least two implementation of RFC 7714 and at least two interpretations of how to treat the master salt value when used with in KDF.  So that we can ensure consistent implementation, it was suggested that I bring this issue to the WG.
>>
>> The issue has to do with the salt length and the KDF.  As you know, RFC 3711 uses AES-CM for the KDF and assumes an initial SRTP master salt that is 14 octets in length (see section 5.3/RFC3711).  AES-GCM, though, utilizes a 12 octet salt value.
>>
>> We have this when AES-CM is used (example taken from RFC 3711) with a 14 octet salt:
>>
>>       index DIV kdr:                 000000000000
>>       label:                       02
>>       master salt:   0EC675AD498AFEEBB6960B3AABE6
>>       -----------------------------------------------
>>       xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF input)
>>
>>
>> This value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet salt value that is then used in the AES-CM KDF logic.
>>
>> When the 12 octet salt used in AES-GCM is provided, libsrtp (https://github.com/cisco/libsrtp) will assume that zeros are padded on the right to produce a 14-octet salt value (to get the default master salt length needed per section 5.3).  Thus, assuming a salt value of 0EC675AD498AFEEBB6960B3A, these steps are performed:
>>
>>       index DIV kdr:                 000000000000
>>       label:                       02
>>       master salt:   0EC675AD498AFEEBB6960B3A
>> 0000
>>      (two padding octets on the right)
>>       -----------------------------------------------
>>       xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF input)
>>
>>
>> Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet salt value that is then used in the AES-CM KDF logic.
>>
>> However, there is a statement in 4.3.1/RFC3711 that says "Let x = key_id XOR master_salt, where key_id and master_salt are aligned so that their least significant bits agree (right-alignment)."  That might suggest that the XOR should have been performed without padding as shown above and as implemented in libsrtp.
>>
>> If padding on the right was the wrong thing to do, that would mean that the XOR step using the initial 12 octet AES-GCM salt should have been this:
>>
>>       index DIV kdr:             000000000000
>>       label:                   02
>>       master salt:   0EC675AD498AFEEBB6960B3A
>>       -------------------------------------------
>>       xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)
>>
>>
>> Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would result in:
>> 0EC675AD4988FEEBB6960B3A0000
>>
>> However, this is only a 14 octet value and we need 16 octets for the AES-CM KDF (which was the reason the step in 4.3.3 exists for the default 14 octet salt).  Thus, we are short two octets.
>>
>> We either need to pad the initial 12 octet AES-GCM input salt at the start in some way to form the expected 14 octet salt value expected per section 5.3 (the approach taken by libsrtp), or we need additional padding after the above x*2^16 step (e.g., introduce a second x*2^16 step).
>>
>> Given that at least two implementers interpreted the specs differently, I think it would be of benefit to discuss this in the WG and document the proper behavior.
>>
>> Paul
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>

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

<html><head></head><body>Martin,<br>
<br>
RFC 7714 uses a 12 octet salt, but this same same salt must be used in AES-CM as part of the KDF.  RFC 3711 assumes the input master salt for AES-CM is a 14 octet salt that is then transformed into a 16 octet salt used by the KDF.<br>
<br>
Somehow, that 12 octet salt in RFC 7714 needs to be transformed into a 16 octet value, too, for use in the AES-CM based KDF.  What&#39;s missing are those steps, so different implementers made different assumptions to ultimately arrive at the needed 16 octets.<br>
<br>
I think some guidance is needed in RFC 7714, since it defines a 12 octet salt and RFC 3711 assumes an input salt of 14 octets in length.<br>
<br>
Paul<br><br><div style='font-size:10.0pt;font-family:"Tahoma","sans-serif";padding:3.0pt 0in 0in 0in'>
<hr style='border:none;border-top:solid #E1E1E1 1.0pt'>
<b>From:</b> Martin Thomson &lt;martin.thomson@gmail.com&gt;<br>
<b>Sent:</b> August 22, 2016 2:54:27 AM EDT<br>
<b>To:</b> &quot;Cullen Jennings (fluffy)&quot; &lt;fluffy@cisco.com&gt;<br>
<b>Cc:</b> Paul Jones &lt;paulej@packetizer.com&gt;, Eric Rescorla &lt;ekr@rtfm.com&gt;, &quot;avt@ietf.org&quot; &lt;avt@ietf.org&gt;<br>
<b>Subject:</b> Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation<br>
</div>
<br>
<pre class="k9mail">I've just concluded that I don't understand RFC 7714.  That is either<br />because I'm too frazzled to think today, or because it's awful.  I<br />think that there's a good slice of tired, but I'm also fairly certain<br />that 7714 is horrendous.  It doesn't even use the same terminology as<br />RFC 3711.  It doesn't even use the AES-GCM (the thing defined in RFC<br />5116).<br /><br />How did you even conclude that AES-GCM needed a 14 octet salt?  I<br />think that I would have concluded that it has a 12 octet salt.<br /><br />On 20 August 2016 at 23:29, Cullen Jennings (fluffy) &lt;fluffy@cisco.com&gt; wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><br /> Ekr, Martin,<br /><br /> Any thoughts on this ?<br /><br /> Thanks<br /><br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> On Aug 4, 2016, a!
 t 9:45
PM, Paul E. Jones &lt;paulej@packetizer.com&gt; wrote:<br /><br /> AVT,<br /><br /> There are now at least two implementation of RFC 7714 and at least two interpretations of how to treat the master salt value when used with in KDF.  So that we can ensure consistent implementation, it was suggested that I bring this issue to the WG.<br /><br /> The issue has to do with the salt length and the KDF.  As you know, RFC 3711 uses AES-CM for the KDF and assumes an initial SRTP master salt that is 14 octets in length (see section 5.3/RFC3711).  AES-GCM, though, utilizes a 12 octet salt value.<br /><br /> We have this when AES-CM is used (example taken from RFC 3711) with a 14 octet salt:<br /><br />       index DIV kdr:                 000000000000<br />       label:                       02<br />       master salt:   0EC675AD498AFEEBB6960B3AABE6<br /><hr /><br />       xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF input)<br /><br /><br /> This value is then multiplied by !
 2^16 per
4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet salt value that is then used in the AES-CM KDF logic.<br /><br /> When the 12 octet salt used in AES-GCM is provided, libsrtp (<a href="https://github.com/cisco/libsrtp">https://github.com/cisco/libsrtp</a>) will assume that zeros are padded on the right to produce a 14-octet salt value (to get the default master salt length needed per section 5.3).  Thus, assuming a salt value of 0EC675AD498AFEEBB6960B3A, these steps are performed:<br /><br />       index DIV kdr:                 000000000000<br />       label:                       02<br />       master salt:   0EC675AD498AFEEBB6960B3A<br /> 0000<br />      (two padding octets on the right)<br /><hr /><br />       xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF input)<br /><br /><br /> Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet salt value that is then used in the AES-CM KDF log!
 ic.<br
/><br /> However, there is a statement in 4.3.1/RFC3711 that says "Let x = key_id XOR master_salt, where key_id and master_salt are aligned so that their least significant bits agree (right-alignment)."  That might suggest that the XOR should have been performed without padding as shown above and as implemented in libsrtp.<br /><br /> If padding on the right was the wrong thing to do, that would mean that the XOR step using the initial 12 octet AES-GCM salt should have been this:<br /><br />       index DIV kdr:             000000000000<br />       label:                   02<br />       master salt:   0EC675AD498AFEEBB6960B3A<br /><hr /><br />       xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)<br /><br /><br /> Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would result in:<br /> 0EC675AD4988FEEBB6960B3A0000<br /><br /> However, this is only a 14 octet value and we need 16 octets for the AES-CM KDF (which was the reason the step in 4.3.3 exis!
 ts for
the default 14 octet salt).  Thus, we are short two octets.<br /><br /> We either need to pad the initial 12 octet AES-GCM input salt at the start in some way to form the expected 14 octet salt value expected per section 5.3 (the approach taken by libsrtp), or we need additional padding after the above x*2^16 step (e.g., introduce a second x*2^16 step).<br /><br /> Given that at least two implementers interpreted the specs differently, I think it would be of benefit to discuss this in the WG and document the proper behavior.<br /><br /> Paul<br /><hr /><br /> Audio/Video Transport Core Maintenance<br /> avt@ietf.org<br /> <a href="https://www.ietf.org/mailman/listinfo/avt">https://www.ietf.org/mailman/listinfo/avt</a><br /></blockquote><br /></blockquote></pre></body></html>
------P4BK8WA1QWFQ1QSSU0IP9RX2U4WVCF--


From nobody Tue Aug 23 17:44:01 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B889012D0FA for <avt@ietfa.amsl.com>; Tue, 23 Aug 2016 17: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 sX161P8H4yQj for <avt@ietfa.amsl.com>; Tue, 23 Aug 2016 17:43:57 -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 7418C12D53B for <avt@ietf.org>; Tue, 23 Aug 2016 17:43:57 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id z190so1383569qkc.0 for <avt@ietf.org>; Tue, 23 Aug 2016 17: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:from:date:message-id:subject:to :cc; bh=Ie1agamOoJ4SDO7gsqB2MauQwCkgeD7v6ftXM9W2FV4=; b=wErbmRQfTbpm3A1c8UFnTbQHdxyKiRSlEmm31aTahNGAFLcmDnx6WqtaQuQGpLWvvs mXErrWh74GeBHY78TB8uj9PxGjoZAcfDXvMA2vRO+cjFLFVUggueppMIGQEGz1hI3vxk NfzQULNqLQS1Sg7zr9BK0IOBMsCjApbtoZZOkvUsHNpNCor7inO3IxFcco4zoHvVDEod o7EDuGUzQLuGhBc29w6dgDqLMqujBYDJDABECErK4ONGVd+z5JnS3CmVOMFcSxCTpAbs CaplVi+4vvLR5uygLc+pSFixXUMEEKpr0o34qmoPVHWPRTDzhLIkh906slwh8PT14Fvu if5w==
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=Ie1agamOoJ4SDO7gsqB2MauQwCkgeD7v6ftXM9W2FV4=; b=lDzsraBcmffjQQNf7U3sBdQPDSfLRUgq0BsVE+yIJIEdJVrDV73ga+nb4yk0Q9LgZu 7aaIdj0wnQzTEiSodEqSZ31SnNzxz2feSsIhrxAQxUzFW/9TQKsTgfKPrKpjWS9glMtt 7Wnh6RVZo9klNlmNBFCnVEX33gM0DOZphDpwPCqCxJOVZukVDbnOLK4jeJYcxQtG1SAT SMIj9hYT56IGeHE34z+ud/OGFVnZyfHKpq2RyAmqGo/ffDsCthGU6QB83DqoOJloJ7i4 KVaXBHZkv8Ja9/gjdYN4nEC7lrAG4mfbMNV1vkcUAyt+TkYGDYMHdKREkRSaGqnvjF1t 2vMQ==
X-Gm-Message-State: AE9vXwO7svWJINmKpHzHIEJt3sksDdxhdk3pJkzbie7XJ0IeWrvDkzG2wnQ5uFyXW9iOs9PJVLUmygDuPnJnSw==
X-Received: by 10.55.184.2 with SMTP id i2mr224124qkf.261.1471999436553; Tue, 23 Aug 2016 17:43:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Tue, 23 Aug 2016 17:43:56 -0700 (PDT)
In-Reply-To: <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com> <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 24 Aug 2016 10:43:56 +1000
Message-ID: <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/NG4Yd9O8r9e9jtVyAoWXVznYiKI>
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 00:44:00 -0000

Why is the same value being used as input to two different ciphers.
That sounds like it could be a very bad idea.

On 22 August 2016 at 22:38, Paul E. Jones <paulej@packetizer.com> wrote:
> Martin,
>
> RFC 7714 uses a 12 octet salt, but this same same salt must be used in
> AES-CM as part of the KDF. RFC 3711 assumes the input master salt for AES-CM
> is a 14 octet salt that is then transformed into a 16 octet salt used by the
> KDF.
>
> Somehow, that 12 octet salt in RFC 7714 needs to be transformed into a 16
> octet value, too, for use in the AES-CM based KDF. What's missing are those
> steps, so different implementers made different assumptions to ultimately
> arrive at the needed 16 octets.
>
> I think some guidance is needed in RFC 7714, since it defines a 12 octet
> salt and RFC 3711 assumes an input salt of 14 octets in length.
>
> Paul
>
> ________________________________
> From: Martin Thomson <martin.thomson@gmail.com>
> Sent: August 22, 2016 2:54:27 AM EDT
> To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
> Cc: Paul Jones <paulej@packetizer.com>, Eric Rescorla <ekr@rtfm.com>,
> "avt@ietf.org" <avt@ietf.org>
> Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
>
> I've just concluded that I don't understand RFC 7714.  That is either
> because I'm too frazzled to think today, or because it's awful.  I
> think that there's a good slice of tired, but I'm also fairly certain
> that 7714 is horrendous.  It doesn't even use the same terminology as
> RFC 3711.  It doesn't even use the AES-GCM (the thing defined in RFC
> 5116).
>
> How did you even conclude that AES-GCM needed a 14 octet salt?  I
> think that I would have concluded that it has a 12 octet salt.
>
> On 20 August 2016 at 23:29, Cullen Jennings (fluffy) <fluffy@cisco.com>
> wrote:
>>
>>
>>  Ekr, Martin,
>>
>>  Any thoughts on this ?
>>
>>  Thanks
>>
>>
>>>  On Aug 4, 2016, a!
>>>  t 9:45
>>> PM, Paul E. Jones <paulej@packetizer.com> wrote:
>>>
>>>  AVT,
>>>
>>>  There are now at least two implementation of RFC 7714 and at least two
>>> interpretations of how to treat the master salt value when used with in KDF.
>>> So that we can ensure consistent implementation, it was suggested that I
>>> bring this issue to the WG.
>>>
>>>  The issue has to do with the salt length and the KDF.  As you know, RFC
>>> 3711 uses AES-CM for the KDF and assumes an initial SRTP master salt that is
>>> 14 octets in length (see section 5.3/RFC3711).  AES-GCM, though, utilizes a
>>> 12 octet salt value.
>>>
>>>  We have this when AES-CM is used (example taken from RFC 3711) with a 14
>>> octet salt:
>>>
>>>        index DIV kdr:                 000000000000
>>>        label:                       02
>>>        master salt:   0EC675AD498AFEEBB6960B3AABE6
>>> ________________________________
>>>
>>>        xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF input)
>>>
>>>
>>>  This value is then multiplied by !
>>>  2^16 per
>>> 4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet salt
>>> value that is then used in the AES-CM KDF logic.
>>>
>>>  When the 12 octet salt used in AES-GCM is provided, libsrtp
>>> (https://github.com/cisco/libsrtp) will assume that zeros are padded on the
>>> right to produce a 14-octet salt value (to get the default master salt
>>> length needed per section 5.3).  Thus, assuming a salt value of
>>> 0EC675AD498AFEEBB6960B3A, these steps are performed:
>>>
>>>        index DIV kdr:                 000000000000
>>>        label:                       02
>>>        master salt:   0EC675AD498AFEEBB6960B3A
>>>  0000
>>>       (two padding octets on the right)
>>> ________________________________
>>>
>>>        xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF input)
>>>
>>>
>>>  Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711 (i.e.,
>>> pad zeros on the right) to produce a 16-octet salt value that is then used
>>> in the AES-CM KDF log!
>>>  ic.
>>>
>>>  However, there is a statement in 4.3.1/RFC3711 that says "Let x = key_id
>>> XOR master_salt, where key_id and master_salt are aligned so that their
>>> least significant bits agree (right-alignment)."  That might suggest that
>>> the XOR should have been performed without padding as shown above and as
>>> implemented in libsrtp.
>>>
>>>  If padding on the right was the wrong thing to do, that would mean that
>>> the XOR step using the initial 12 octet AES-GCM salt should have been this:
>>>
>>>        index DIV kdr:             000000000000
>>>        label:                   02
>>>        master salt:   0EC675AD498AFEEBB6960B3A
>>> ________________________________
>>>
>>>        xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)
>>>
>>>
>>>  Then the x*2^16 operation that then follows as per 4.3.3/RFC3711 would
>>> result in:
>>>  0EC675AD4988FEEBB6960B3A0000
>>>
>>>  However, this is only a 14 octet value and we need 16 octets for the
>>> AES-CM KDF (which was the reason the step in 4.3.3 exis!
>>>  ts for
>>> the default 14 octet salt).  Thus, we are short two octets.
>>>
>>>  We either need to pad the initial 12 octet AES-GCM input salt at the
>>> start in some way to form the expected 14 octet salt value expected per
>>> section 5.3 (the approach taken by libsrtp), or we need additional padding
>>> after the above x*2^16 step (e.g., introduce a second x*2^16 step).
>>>
>>>  Given that at least two implementers interpreted the specs differently,
>>> I think it would be of benefit to discuss this in the WG and document the
>>> proper behavior.
>>>
>>>  Paul
>>> ________________________________
>>>
>>>  Audio/Video Transport Core Maintenance
>>>  avt@ietf.org
>>>  https://www.ietf.org/mailman/listinfo/avt
>>
>>
>


From nobody Tue Aug 23 18:53:56 2016
Return-Path: <paulej@packetizer.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25AA012D5C5 for <avt@ietfa.amsl.com>; Tue, 23 Aug 2016 18:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91chAnY1ksCD for <avt@ietfa.amsl.com>; Tue, 23 Aug 2016 18:53:53 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3680A12D59A for <avt@ietf.org>; Tue, 23 Aug 2016 18:53:53 -0700 (PDT)
Received: from [192.168.1.20] (cpe-098-122-181-220.nc.res.rr.com [98.122.181.220] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.15.2/8.15.2) with ESMTPSA id u7O1roLn004990 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 23 Aug 2016 21:53:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1472003630; bh=b9xUgWCe89VfHVk2aAw95BJcaIc6MNvug/rOY3xt730=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=CGLPLMGP3TWwpIor/ZWL2DDMzFo4uo771mUqLy7uNjHOo2X6w0A+3F7rdunolSjj9 Kb7xaDWMBy77Vb8Q2Zoi8eWiZmsiDg8EmMW+2vfJu55ajBJma6WCN24MUCl6Z1vwSM bnT6NZZNpGDZghdK7FomEMXQSdH2KiMY0lDOqLlU=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Martin Thomson" <martin.thomson@gmail.com>
Date: Wed, 24 Aug 2016 01:53:50 +0000
Message-Id: <em1ea28ee4-249a-4d22-93fc-4d0eea9ac537@sydney>
In-Reply-To: <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com> <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com> <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com>
User-Agent: eM_Client/7.0.26482.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6 (dublin.packetizer.com [10.137.60.122]); Tue, 23 Aug 2016 21:53:50 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/qnhssFxREJfVW3HnkK21Lh33gXQ>
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 01:53:55 -0000

Martin,

The same value is not used.  SRTP takes as input a master key and master=
=20
salt.  Those values are given to a Key Derivation Function (KDF) that=20
produces session encryption and salting keys.

The KDF is defined to be AES-CM.  To use AES-CM, we need the encryption=20
key and a salt that is 16 octets in length.  This is where the issue=20
arises and is the subject of this email thread.

RFC 3711 assumes a default salt length of 14 octets.  It specifies how=20
to manipulate the salt so that it is unique for each type of key and=20
salt we wish to create via the KDF.  Specifically, the master salt is=20
XORed with a unique "key_id".  The salt is then padded with 2 zero=20
octets on the right, forming a 16-octet value that is unique for each=20
key type.

RFC 7714 specified a salt length of 12 octets.  And that's where the=20
problem comes in.

One implementer padded that 12 octet salt with two zero octets on the=20
right to form a 14 octet value.  Then the usual RFC 3711 procedures were=
=20
followed.

The other implementer took the salt value given, performed the XOR step,=
=20
then padded two zero octets on the right or left.  I don't recall which=20
was done, but it's immaterial.  Both will work, but neither are=20
specified.

Then both implementers padded two zero octets on the right per Section=20
4.3.3 of RFC 3711 to get the required 16 octets.

So, the only issue we have is the fact that the salt length specified in=
=20
RFC 7714 is two octets short of what we need to use the salt properly=20
with the procedures defined in RFC 3711.  Two additional octets are=20
needed and we need to decide where and when to add them.   We have=20
several ways to fix it.  Starting with the 12 octet salt:
   1. Pad with two zero octets on the left before XORing the salt with=20
the key_id
   2. Pad with two zero octets on the right before XORing the salt with=20
the key_id (libsrtp behavior)
   3. Pad with two zero octets on the left after XORing the salt with the=
=20
key_id
   4. Pad with two zero octets on the right after XORing the salt with=20
the key_id
   5. Pad with any other values before or after or in between to get to=20
14 octets.

Paul

------ Original Message ------
From: "Martin Thomson" <martin.thomson@gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>; "Eric Rescorla"=20
<ekr@rtfm.com>; "avt@ietf.org" <avt@ietf.org>
Sent: 8/23/2016 8:43:56 PM
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation

>Why is the same value being used as input to two different ciphers.
>That sounds like it could be a very bad idea.
>
>On 22 August 2016 at 22:38, Paul E. Jones <paulej@packetizer.com>=20
>wrote:
>>  Martin,
>>
>>  RFC 7714 uses a 12 octet salt, but this same same salt must be used=20
>>in
>>  AES-CM as part of the KDF. RFC 3711 assumes the input master salt for=
=20
>>AES-CM
>>  is a 14 octet salt that is then transformed into a 16 octet salt used=
=20
>>by the
>>  KDF.
>>
>>  Somehow, that 12 octet salt in RFC 7714 needs to be transformed into=
=20
>>a 16
>>  octet value, too, for use in the AES-CM based KDF. What's missing are=
=20
>>those
>>  steps, so different implementers made different assumptions to=20
>>ultimately
>>  arrive at the needed 16 octets.
>>
>>  I think some guidance is needed in RFC 7714, since it defines a 12=20
>>octet
>>  salt and RFC 3711 assumes an input salt of 14 octets in length.
>>
>>  Paul
>>
>>  ________________________________
>>  From: Martin Thomson <martin.thomson@gmail.com>
>>  Sent: August 22, 2016 2:54:27 AM EDT
>>  To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
>>  Cc: Paul Jones <paulej@packetizer.com>, Eric Rescorla <ekr@rtfm.com>,
>>  "avt@ietf.org" <avt@ietf.org>
>>  Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
>>
>>  I've just concluded that I don't understand RFC 7714.  That is either
>>  because I'm too frazzled to think today, or because it's awful.  I
>>  think that there's a good slice of tired, but I'm also fairly certain
>>  that 7714 is horrendous.  It doesn't even use the same terminology as
>>  RFC 3711.  It doesn't even use the AES-GCM (the thing defined in RFC
>>  5116).
>>
>>  How did you even conclude that AES-GCM needed a 14 octet salt?  I
>>  think that I would have concluded that it has a 12 octet salt.
>>
>>  On 20 August 2016 at 23:29, Cullen Jennings (fluffy)=20
>><fluffy@cisco.com>
>>  wrote:
>>>
>>>
>>>   Ekr, Martin,
>>>
>>>   Any thoughts on this ?
>>>
>>>   Thanks
>>>
>>>
>>>>   On Aug 4, 2016, a!
>>>>   t 9:45
>>>>  PM, Paul E. Jones <paulej@packetizer.com> wrote:
>>>>
>>>>   AVT,
>>>>
>>>>   There are now at least two implementation of RFC 7714 and at least=
=20
>>>>two
>>>>  interpretations of how to treat the master salt value when used=20
>>>>with in KDF.
>>>>  So that we can ensure consistent implementation, it was suggested=20
>>>>that I
>>>>  bring this issue to the WG.
>>>>
>>>>   The issue has to do with the salt length and the KDF.  As you=20
>>>>know, RFC
>>>>  3711 uses AES-CM for the KDF and assumes an initial SRTP master=20
>>>>salt that is
>>>>  14 octets in length (see section 5.3/RFC3711).  AES-GCM, though,=20
>>>>utilizes a
>>>>  12 octet salt value.
>>>>
>>>>   We have this when AES-CM is used (example taken from RFC 3711)=20
>>>>with a 14
>>>>  octet salt:
>>>>
>>>>         index DIV kdr:                 000000000000
>>>>         label:                       02
>>>>         master salt:   0EC675AD498AFEEBB6960B3AABE6
>>>>  ________________________________
>>>>
>>>>         xor:           0EC675AD498AFEE9B6960B3AABE6     (x, PRF=20
>>>>input)
>>>>
>>>>
>>>>   This value is then multiplied by !
>>>>   2^16 per
>>>>  4.3.3/RFC3711 (i.e., pad zeros on the right) to produce a 16-octet=
=20
>>>>salt
>>>>  value that is then used in the AES-CM KDF logic.
>>>>
>>>>   When the 12 octet salt used in AES-GCM is provided, libsrtp
>>>>  (https://github.com/cisco/libsrtp) will assume that zeros are=20
>>>>padded on the
>>>>  right to produce a 14-octet salt value (to get the default master=20
>>>>salt
>>>>  length needed per section 5.3).  Thus, assuming a salt value of
>>>>  0EC675AD498AFEEBB6960B3A, these steps are performed:
>>>>
>>>>         index DIV kdr:                 000000000000
>>>>         label:                       02
>>>>         master salt:   0EC675AD498AFEEBB6960B3A
>>>>   0000
>>>>        (two padding octets on the right)
>>>>  ________________________________
>>>>
>>>>         xor:           0EC675AD498AFEE9B6960B3A0000     (x, PRF=20
>>>>input)
>>>>
>>>>
>>>>   Again, this value is then multiplied by 2^16 per 4.3.3/RFC3711=20
>>>>(i.e.,
>>>>  pad zeros on the right) to produce a 16-octet salt value that is=20
>>>>then used
>>>>  in the AES-CM KDF log!
>>>>   ic.
>>>>
>>>>   However, there is a statement in 4.3.1/RFC3711 that says "Let x =3D=
=20
>>>>key_id
>>>>  XOR master_salt, where key_id and master_salt are aligned so that=20
>>>>their
>>>>  least significant bits agree (right-alignment)."  That might=20
>>>>suggest that
>>>>  the XOR should have been performed without padding as shown above=20
>>>>and as
>>>>  implemented in libsrtp.
>>>>
>>>>   If padding on the right was the wrong thing to do, that would mean=
=20
>>>>that
>>>>  the XOR step using the initial 12 octet AES-GCM salt should have=20
>>>>been this:
>>>>
>>>>         index DIV kdr:             000000000000
>>>>         label:                   02
>>>>         master salt:   0EC675AD498AFEEBB6960B3A
>>>>  ________________________________
>>>>
>>>>         xor:           0EC675AD4988FEEBB6960B3A     (x, PRF input)
>>>>
>>>>
>>>>   Then the x*2^16 operation that then follows as per 4.3.3/RFC3711=20
>>>>would
>>>>  result in:
>>>>   0EC675AD4988FEEBB6960B3A0000
>>>>
>>>>   However, this is only a 14 octet value and we need 16 octets for=20
>>>>the
>>>>  AES-CM KDF (which was the reason the step in 4.3.3 exis!
>>>>   ts for
>>>>  the default 14 octet salt).  Thus, we are short two octets.
>>>>
>>>>   We either need to pad the initial 12 octet AES-GCM input salt at=20
>>>>the
>>>>  start in some way to form the expected 14 octet salt value expected=
=20
>>>>per
>>>>  section 5.3 (the approach taken by libsrtp), or we need additional=
=20
>>>>padding
>>>>  after the above x*2^16 step (e.g., introduce a second x*2^16 step).
>>>>
>>>>   Given that at least two implementers interpreted the specs=20
>>>>differently,
>>>>  I think it would be of benefit to discuss this in the WG and=20
>>>>document the
>>>>  proper behavior.
>>>>
>>>>   Paul
>>>>  ________________________________
>>>>
>>>>   Audio/Video Transport Core Maintenance
>>>>   avt@ietf.org
>>>>   https://www.ietf.org/mailman/listinfo/avt
>>>
>>>
>>


From nobody Wed Aug 24 00:21:40 2016
Return-Path: <martin.thomson@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD07612D7F9 for <avt@ietfa.amsl.com>; Wed, 24 Aug 2016 00:21:38 -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 MBnZodrOTsVl for <avt@ietfa.amsl.com>; Wed, 24 Aug 2016 00:21:37 -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 6FECB12D7E3 for <avt@ietf.org>; Wed, 24 Aug 2016 00:21:37 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id z190so7180556qkc.0 for <avt@ietf.org>; Wed, 24 Aug 2016 00:21: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:from:date:message-id:subject:to :cc; bh=Nno7f44g5MqJWUCPECvmqvI1Ug/UNOAn8yNVwYGFClo=; b=lmnkzd+tA8ZD11/MMS9iNalaDT9KIBOcMWZ3JvH2A39edtnrvvXIZyjslSpnNKylPJ QJa/8+ZV5B67wqqncTHR0gqZznugGLQ5b+kzMwQ12A5zouDzSHJ6veNhZhbRZ2KeIjSu 34/799QBl05vBXoucA3i2tHWiLoO6t/Ta9qr8NkB1iz0B362mfW7q5LvJi+LNmH71DOP u4eiyw1EpC2Kp6mygls6OzQXeMCqsXPWagMlddM24IZoYPYbfGfQdprshq5IfyMfEgEq QsyzL3modcIG0fSozmzfHqqo/RN4/2v3lEijKPkW0lW4a48zZe+S9mBsSqrZlAWiF9Ma OMJA==
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=Nno7f44g5MqJWUCPECvmqvI1Ug/UNOAn8yNVwYGFClo=; b=R90cAsjkiemKl5AuhpGPIhSrEjQFKwpPrkVGAhIC1OZRgMKGH3VH4lpV6roOAObEGo xeZIql8UHI7U6z7tC2L9zoa4qBVxrfK6mNnka6QfhzNcxPXmKiteTHuPGmT3PKWP8KqE h1oYmLBvLCHXtGCQp/pk1kHnEgbVNPEYIxxMcV2kx/03BW3ClBByH2x3MeuUDqWBKaxl gT45r4J+2vh84KYhuSurB68TUl28uP9axgHZ6/pUgrXGScgsToTSCmhg1UlFWsZHk4Pc fFSuRgi3bvs5KIMj9xNkcH5ewS6g/9Oow1YOFgkOfRwzMqFIDtCzBU5S+/Bq4MyjP0dE rDoQ==
X-Gm-Message-State: AE9vXwOSl+NCkoqo395At7ZKYwEncBjlk8yJ2KhLP9Two3D9VyPJ7MsJf1aAhRnXLerocYxblh57xkqfdaZoZA==
X-Received: by 10.55.6.19 with SMTP id 19mr1651533qkg.156.1472023296601; Wed, 24 Aug 2016 00:21:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Wed, 24 Aug 2016 00:21:36 -0700 (PDT)
In-Reply-To: <em1ea28ee4-249a-4d22-93fc-4d0eea9ac537@sydney>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com> <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com> <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com> <em1ea28ee4-249a-4d22-93fc-4d0eea9ac537@sydney>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 24 Aug 2016 17:21:36 +1000
Message-ID: <CABkgnnUojv-82cnUPerPvOAZHD90vRSOKQ_S6cU8LNyVh5stJA@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/rf7uDggshmQXUUwq5LTBLAOH0Fo>
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 07:21:39 -0000

On 24 August 2016 at 11:53, Paul E. Jones <paulej@packetizer.com> wrote:
> RFC 7714 specified a salt length of 12 octets.  And that's where the problem
> comes in.

If you (and 7714) were to use "master salt" consistently, the
confusion would have been easily avoided.

Either way, I agree that clarification is helpful.  My inclination is
to take option 1 here.  That matches S4.1.1 of 3711 where it defines
using right-alignment and it matches my understanding of the
mathematics used in 3711 (x is multiplied by 2^16, so presumably these
are big-endian numbers we are talking about rather than octet
sequences).

Option 2 seems like an error (assuming 7714 really does define
master_salt as being 12 octets), driven by examples rather than
normative language.  Options 3 and 4 (pad after XOR) don't fit with
the interpretation.

My guess is that 3711 doesn't define how big x is (that is, the output
of the XOR) because it assumes this to be a mere number.  It seems
like an oversight though.

So I guess that my conclusion is that no one is right.


From nobody Wed Aug 24 15:08:31 2016
Return-Path: <paulej@packetizer.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527A112B043 for <avt@ietfa.amsl.com>; Wed, 24 Aug 2016 15:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84gwAoqpHQjC for <avt@ietfa.amsl.com>; Wed, 24 Aug 2016 15:08:30 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB1EE12B026 for <avt@ietf.org>; Wed, 24 Aug 2016 15:08:29 -0700 (PDT)
Received: from [192.168.1.20] (cpe-098-122-181-220.nc.res.rr.com [98.122.181.220] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.15.2/8.15.2) with ESMTPSA id u7OM8PQK014337 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 24 Aug 2016 18:08:26 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1472076506; bh=JjTVTYr0BCrxFHhDduwwUYTjsLb0Le4tQVR5OYZXOyM=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=aS0632xMYuEDjMAtu8CVEPKqMbx1FShxTTTlBLJWWGjQ1d9dHKOVp5vLGvQL3UvAC 1ojID5Pf9FI2GTAujUAE783IdzgwBI4MLCGCsluq5htIC6cqTscyEfYlH2hDTIeNoj QzhaPVdme9rpM+RihCmB2gs/WKIWPzKihQqdkG/k=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Martin Thomson" <martin.thomson@gmail.com>
Date: Wed, 24 Aug 2016 22:08:26 +0000
Message-Id: <em4d4ae0b9-9526-4f03-83e7-87154cf0befd@sydney>
In-Reply-To: <CABkgnnUojv-82cnUPerPvOAZHD90vRSOKQ_S6cU8LNyVh5stJA@mail.gmail.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com> <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com> <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com> <em1ea28ee4-249a-4d22-93fc-4d0eea9ac537@sydney> <CABkgnnUojv-82cnUPerPvOAZHD90vRSOKQ_S6cU8LNyVh5stJA@mail.gmail.com>
User-Agent: eM_Client/7.0.26482.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6 (dublin.packetizer.com [10.137.60.122]); Wed, 24 Aug 2016 18:08:26 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/y212m_JisYGj0FhDWubCYYyWwZc>
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2016 22:08:31 -0000

Martin,

I think you were referring to section 4.3.1 of RFC 3711, right?  That's=20
where it talks about right-alignment.  They key_id is generally shorter=20
than the salt (and is in all defined uses of RFC 3711), so the=20
right-alignment statement was to ensure that the key_id aligned with the=
=20
master salt at a particular place.

If we followed RFC 3711, we would take whatever salt we have (12 octets=20
in this case), align it with the key_id and XOR.  We would then multiply=
=20
that by 2*16 (to effectively pad two octets on the right). =20
Unfortunately, we'd be two octets short of what we need.

If we take option (1), the right-alignment will result in the same=20
numeric value as if no padding is introduced.  Thus the output would be=20
precisely the same as option (3), since the salt is longer than the=20
key_id.  Those options work, though I'll note that nowhere does RFC 3711=
=20
ever pad on the left.

Option (2) does padding in a way that is consistent with RFC 3711 and,=20
as with option (1), padding at the outset addresses any issues had the=20
salt been shorter than the key_id.

Option (4) is actually a logical choice to make given the way RFC 3711=20
is defined.  What could have been stated in section 4.3.3 is that the IV=
=20
is equal to ((x*2^8n), where n is 16 - length of x in octets).  That=20
might be confusing language and perhaps better worded.  It also would=20
not consider the case where the salt length is less than the key_id=20
length.  (In reality, it's not likely anyone would ever specify such a=20
short salt, but I like to be complete.)

So as to avoid complicating what is in RFC 3711, my though was to modify=
=20
the text in  Section 11 of RFC 7714 where it refers to using KDFs=20
defined in RFC 3711 and RFC 6188.  RFC 6188 states "both AES_192_CM and=20
AES_256_CM use a 112-bit salt as an input, as does AES_CM."  So I think=20
the simplest thing is to explain in this section that the salt value=20
used in the KDF for RFC 3711 and RFC 6188 assume a 112 bit value and=20
suggest to either add two zero octets to the front or the end. =20
Consistent with language in RFC 3711, we would say:

"Since the KDF functions in those RFCs assume as input a 112-bit master=20
salt, the 96-bit master salt specified in this document must be=20
multiplied by 2^16 to form the 112-bit salt used as the master salt for=20
those key derivation functions."

In effect, that language results in the use of option 2 in my previous=20
email.  It's fairly concise language and then resolves how to use the=20
shorter salt with the existing text that assumes a longer salt.

Paul

------ Original Message ------
From: "Martin Thomson" <martin.thomson@gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Cc: "Cullen Jennings (fluffy)" <fluffy@cisco.com>; "Eric Rescorla"=20
<ekr@rtfm.com>; "avt@ietf.org" <avt@ietf.org>
Sent: 8/24/2016 3:21:36 AM
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation

>On 24 August 2016 at 11:53, Paul E. Jones <paulej@packetizer.com>=20
>wrote:
>>  RFC 7714 specified a salt length of 12 octets.  And that's where the=
=20
>>problem
>>  comes in.
>
>If you (and 7714) were to use "master salt" consistently, the
>confusion would have been easily avoided.
>
>Either way, I agree that clarification is helpful.  My inclination is
>to take option 1 here.  That matches S4.1.1 of 3711 where it defines
>using right-alignment and it matches my understanding of the
>mathematics used in 3711 (x is multiplied by 2^16, so presumably these
>are big-endian numbers we are talking about rather than octet
>sequences).
>
>Option 2 seems like an error (assuming 7714 really does define
>master_salt as being 12 octets), driven by examples rather than
>normative language.  Options 3 and 4 (pad after XOR) don't fit with
>the interpretation.
>
>My guess is that 3711 doesn't define how big x is (that is, the output
>of the XOR) because it assumes this to be a mere number.  It seems
>like an oversight though.
>
>So I guess that my conclusion is that no one is right.


From nobody Thu Aug 25 07:38:31 2016
Return-Path: <fluffy@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC4712D0DC for <avt@ietfa.amsl.com>; Thu, 25 Aug 2016 07:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.069
X-Spam-Level: 
X-Spam-Status: No, score=-115.069 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 YkExta4isFTN for <avt@ietfa.amsl.com>; Thu, 25 Aug 2016 07:38:29 -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 E5A0312B058 for <avt@ietf.org>; Thu, 25 Aug 2016 07:38:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1643; q=dns/txt; s=iport; t=1472135908; x=1473345508; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=NPTULP2DxgmqWO/OjKQG9vIIyAJtr1k7ddwSPwhC4NI=; b=LVlElPScblhAri0jRhWjKbuRBXARzDXXl5zzzPPwKWzdVsjiUtjnhKfV 9CTcQLSsCfITjOwA+6j9sxGpebnJS+FWJhxySk9F+m4pfg9BVC7ANuLfz n9/mgtTdBc1ymefZrlZcoXQtYBGnd6/gA8AGTHWUL3kv4emRTJ+i1Lg0X A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AxAgBcAr9X/5hdJa1dgykBAQEBAR5Wf?= =?us-ascii?q?AerYIwugXwkhXkCgVo4FAIBAQEBAQEBXieEYQEBBAEBATg/BQsCAQgYHhAhBgs?= =?us-ascii?q?lAgQOBYgYAw8IDrwkDYNsAQEBAQEBAQEBAQEBAQEBAQEBAQEBFwWIJoJVgTmBC?= =?us-ascii?q?oF9gy2CLwWZFjQBjFqCS49RiDiECYN4AR42giKBW3CGAn8BAQE?=
X-IronPort-AV: E=Sophos;i="5.28,576,1464652800"; d="scan'208";a="144454799"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Aug 2016 14:38:28 +0000
Received: from XCH-RTP-002.cisco.com (xch-rtp-002.cisco.com [64.101.220.142]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u7PEcR04006136 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 25 Aug 2016 14:38:27 GMT
Received: from xch-rtp-004.cisco.com (64.101.220.144) by XCH-RTP-002.cisco.com (64.101.220.142) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 25 Aug 2016 10:38:26 -0400
Received: from xch-rtp-004.cisco.com ([64.101.220.144]) by XCH-RTP-004.cisco.com ([64.101.220.144]) with mapi id 15.00.1210.000; Thu, 25 Aug 2016 10:38:26 -0400
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
Thread-Index: AQHR/EIIWeVoiD0MkEWgupGjXxA9P6BVLquAgAJdDwCAABOIAIAAW5MAgAIMYYA=
Date: Thu, 25 Aug 2016 14:38:26 +0000
Message-ID: <4E7A1063-0FCF-4F15-B563-A70AD696C97F@cisco.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com> <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com> <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com> <em1ea28ee4-249a-4d22-93fc-4d0eea9ac537@sydney> <CABkgnnUojv-82cnUPerPvOAZHD90vRSOKQ_S6cU8LNyVh5stJA@mail.gmail.com>
In-Reply-To: <CABkgnnUojv-82cnUPerPvOAZHD90vRSOKQ_S6cU8LNyVh5stJA@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.20.249.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CDCCD9D5B4A59E47A21CD73F26DFFE8E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/GbVvZt8uyc9O8oLEe-4D7qMZ9DQ>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 14:38:30 -0000

So to be pragmatic about this ... how much running code will either choice =
A or B break? Do we need to make a new version this somehow if we are break=
ing deployed code so that running code knows which version it is dealing wi=
th and what to do?


> On Aug 24, 2016, at 1:21 AM, Martin Thomson <martin.thomson@gmail.com> wr=
ote:
>=20
> On 24 August 2016 at 11:53, Paul E. Jones <paulej@packetizer.com> wrote:
>> RFC 7714 specified a salt length of 12 octets.  And that's where the pro=
blem
>> comes in.
>=20
> If you (and 7714) were to use "master salt" consistently, the
> confusion would have been easily avoided.
>=20
> Either way, I agree that clarification is helpful.  My inclination is
> to take option 1 here.  That matches S4.1.1 of 3711 where it defines
> using right-alignment and it matches my understanding of the
> mathematics used in 3711 (x is multiplied by 2^16, so presumably these
> are big-endian numbers we are talking about rather than octet
> sequences).
>=20
> Option 2 seems like an error (assuming 7714 really does define
> master_salt as being 12 octets), driven by examples rather than
> normative language.  Options 3 and 4 (pad after XOR) don't fit with
> the interpretation.
>=20
> My guess is that 3711 doesn't define how big x is (that is, the output
> of the XOR) because it assumes this to be a mere number.  It seems
> like an oversight though.
>=20
> So I guess that my conclusion is that no one is right.
>=20
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt


From nobody Fri Aug 26 12:32:00 2016
Return-Path: <paulej@packetizer.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B8212D814 for <avt@ietfa.amsl.com>; Fri, 26 Aug 2016 12:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-1l6CAMz18g for <avt@ietfa.amsl.com>; Fri, 26 Aug 2016 12:31:56 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B548612D7F3 for <avt@ietf.org>; Fri, 26 Aug 2016 12:31:44 -0700 (PDT)
Received: from [192.168.1.20] (cpe-098-122-181-220.nc.res.rr.com [98.122.181.220] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.15.2/8.15.2) with ESMTPSA id u7QJVfLg016972 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 26 Aug 2016 15:31:42 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1472239902; bh=bTmBL5W/hIkwA/ZRCMC4HjABSPO1WR6EKGTYb7DXcTg=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=D3u/AaN5K17eeNikaYZe6iy4uq6iEOLNf115JwlF+eC2FmkCAHWlaLphc+w+oWMhg a3RIBPzepGKwH9MIIBzLJlVRlQUWcnTSr4PSspGbC+yt0I/PikUrm9rulWtuA4pp3N imlCHTt6zgiyXnTKPsJMBZw4mQzjqvz9NL7f5q0I=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "Martin Thomson" <martin.thomson@gmail.com>
Date: Fri, 26 Aug 2016 19:31:41 +0000
Message-Id: <embbb75de5-539b-4e56-a972-5da370e9f857@sydney>
In-Reply-To: <4E7A1063-0FCF-4F15-B563-A70AD696C97F@cisco.com>
References: <em43c05a1d-4be9-4d0b-96f9-0ea529996685@sydney> <D5E3E4C0-9873-451F-BB6A-973BB03E4D32@cisco.com> <CABkgnnVH30pEVqnEnRfm==vjPfeZcnKjPSOet+HowVn_+yqAMQ@mail.gmail.com> <AF1F75B7-7A01-43C3-81BA-A133D46A4CCD@packetizer.com> <CABkgnnUdnPF1g+YpCycbU0q+8ObdNSFwM_NN3eOjAcRLxWCs4Q@mail.gmail.com> <em1ea28ee4-249a-4d22-93fc-4d0eea9ac537@sydney> <CABkgnnUojv-82cnUPerPvOAZHD90vRSOKQ_S6cU8LNyVh5stJA@mail.gmail.com> <4E7A1063-0FCF-4F15-B563-A70AD696C97F@cisco.com>
User-Agent: eM_Client/7.0.26482.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6 (dublin.packetizer.com [10.137.60.122]); Fri, 26 Aug 2016 15:31:42 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/SRGKKswX4amJi5MqUZjUae1wXjQ>
Cc: "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2016 19:31:59 -0000

Cullen,

Cisco has a fairly large number of IP phones and videoconferencing=20
endpoints using the logic currently implemented in libSRTP (which is #2=20
in my list of options).

Paul

------ Original Message ------
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Martin Thomson" <martin.thomson@gmail.com>
Cc: "Paul Jones" <paulej@packetizer.com>; "avt@ietf.org" <avt@ietf.org>
Sent: 8/25/2016 10:38:26 AM
Subject: Re: [AVTCORE] AES-GCM SRTP (RFC 7714) KDF implementation

>So to be pragmatic about this ... how much running code will either=20
>choice A or B break? Do we need to make a new version this somehow if=20
>we are breaking deployed code so that running code knows which version=20
>it is dealing with and what to do?
>
>
>>  On Aug 24, 2016, at 1:21 AM, Martin Thomson=20
>><martin.thomson@gmail.com> wrote:
>>
>>  On 24 August 2016 at 11:53, Paul E. Jones <paulej@packetizer.com>=20
>>wrote:
>>>  RFC 7714 specified a salt length of 12 octets.  And that's where the=
=20
>>>problem
>>>  comes in.
>>
>>  If you (and 7714) were to use "master salt" consistently, the
>>  confusion would have been easily avoided.
>>
>>  Either way, I agree that clarification is helpful.  My inclination is
>>  to take option 1 here.  That matches S4.1.1 of 3711 where it defines
>>  using right-alignment and it matches my understanding of the
>>  mathematics used in 3711 (x is multiplied by 2^16, so presumably=20
>>these
>>  are big-endian numbers we are talking about rather than octet
>>  sequences).
>>
>>  Option 2 seems like an error (assuming 7714 really does define
>>  master_salt as being 12 octets), driven by examples rather than
>>  normative language.  Options 3 and 4 (pad after XOR) don't fit with
>>  the interpretation.
>>
>>  My guess is that 3711 doesn't define how big x is (that is, the=20
>>output
>>  of the XOR) because it assumes this to be a mere number.  It seems
>>  like an oversight though.
>>
>>  So I guess that my conclusion is that no one is right.
>>
>>  _______________________________________________
>>  Audio/Video Transport Core Maintenance
>>  avt@ietf.org
>>  https://www.ietf.org/mailman/listinfo/avt
>


From nobody Mon Aug 29 13:22:47 2016
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: avt@ietf.org
Delivered-To: avt@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8747212D0B2; Mon, 29 Aug 2016 13:22:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.31.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <147250216554.19077.2789579335319205739.idtracker@ietfa.amsl.com>
Date: Mon, 29 Aug 2016 13:22:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/vBlqnAZuMArKPZDY1H341cebBfs>
Cc: avtcore-chairs@ietf.org, magnus.westerlund@ericsson.com, draft-ietf-avtcore-rfc5764-mux-fixes@ietf.org, avt@ietf.org
Subject: [AVTCORE] Spencer Dawkins' Yes on draft-ietf-avtcore-rfc5764-mux-fixes-10: (with COMMENT)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Aug 2016 20:22:46 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-avtcore-rfc5764-mux-fixes-10: Yes

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


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


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rfc5764-mux-fixes/



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

Thank you for doing this update. You're helping avoid problems later.

This specification was pretty dense and difficult for me to understand
(there's quite a bit going on), until I got to the OLD TEXT/NEW TEXT in
Section 7, which made everything much clearer. You might consider moving
Section 7 forward, so that the organization of the document becomes "here
is the new multiplexing scheme", followed by "here's why the changes are
needed".

In these list entries:

   1.  It implicitly allocated codepoints for new STUN methods without
       an IANA registry reflecting these new allocations.
       
and

   3.  It implicitly allocated codepoints for new Transport Layer
       Security (TLS) ContentTypes without an IANA registry reflecting
       these new allocations.
       
is it correct to say "without entries in an IANA registry reflecting
these new allocations"? I was reading the text as saying there were no
registries for STUN methods or TLS ContentTypes, but that's not what you
meant, is it?



From nobody Wed Aug 31 04:24:09 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C80F12D5CC for <avt@ietfa.amsl.com>; Tue, 30 Aug 2016 06:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level: 
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5p9ytyJacSai for <avt@ietfa.amsl.com>; Tue, 30 Aug 2016 06:25:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF82512D14F for <avt@ietf.org>; Tue, 30 Aug 2016 06:25:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B863DB80D13; Tue, 30 Aug 2016 06:25:57 -0700 (PDT)
To: mcgrew@cisco.com, ekr@rtfm.com, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, keith.drage@alcatel-lucent.com, roni.even@mail01.huawei.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160830132557.B863DB80D13@rfc-editor.org>
Date: Tue, 30 Aug 2016 06:25:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/oxzw376NA8rh4efUnf0lhB-utBA>
X-Mailman-Approved-At: Wed, 31 Aug 2016 04:24:08 -0700
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] [Technical Errata Reported] RFC5764 (4788)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2016 13:26:03 -0000

The following errata report has been submitted for RFC5764,
"Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5764&eid=4788

--------------------------------------
Type: Technical
Reported by: Eric Rescorla <ekr@rtfm.com>

Section: 5.3

Original Text
-------------
Section 4.2 says:
   which are assigned as shown below.  The per-association context value
   is empty.

Corrected Text
--------------
   which are assigned as shown below.  No per-association context value
   is used.

Notes
-----
This code is somewhat ambiguous, though the better interpretation is probably that you should use a zero-length context (arm 2 of https://tools.ietf.org/html/rfc5705#section-4). However, real implementations do not seem to use the exporter value, so we need to resolve this in that direction.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5764 (draft-ietf-avt-dtls-srtp-07)
--------------------------------------
Title               : Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP)
Publication Date    : May 2010
Author(s)           : D. McGrew, E. Rescorla
Category            : PROPOSED STANDARD
Source              : Audio/Video Transport
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

