Re: [AVTCORE] [Technical Errata Reported] RFC3711 (3420)

Karl Norrman <karl.norrman@ericsson.com> Fri, 22 March 2013 17:45 UTC

Return-Path: <karl.norrman@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 3097321F8F4A for <avt@ietfa.amsl.com>; Fri, 22 Mar 2013 10:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOECnG5aVCwx for <avt@ietfa.amsl.com>; Fri, 22 Mar 2013 10:45:26 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id AE29921F8F43 for <avt@ietf.org>; Fri, 22 Mar 2013 10:45:25 -0700 (PDT)
X-AuditID: c1b4fb25-b7f366d000004d10-5e-514c98b37b72
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 46.90.19728.3B89C415; Fri, 22 Mar 2013 18:45:24 +0100 (CET)
Received: from ESESSMB203.ericsson.se ([169.254.3.183]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0318.004; Fri, 22 Mar 2013 18:45:23 +0100
From: Karl Norrman <karl.norrman@ericsson.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [Technical Errata Reported] RFC3711 (3420)
Thread-Index: AQHOJxGrsLg0sGohOEGnXhFDB+UzwJix+4Rw
Date: Fri, 22 Mar 2013 17:45:22 +0000
Message-ID: <33E51946CDE71249AF9D86CE4D8966B4121F17BE@ESESSMB203.ericsson.se>
References: <20121128143149.E05F3B1E004@rfc-editor.org> <33E51946CDE71249AF9D86CE4D8966B40213AC@ESESSMB203.ericsson.se> <514C7827.3030503@nostrum.com>
In-Reply-To: <514C7827.3030503@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42KZGfG3RnfLDJ9AgxcvuSxe9qxkt3j1+gqr xdPGs4wW1w7sZ7H4MmU5i8XVVX/YLa7NaWSzmNpn68Dh0fpsL6vHlN8bWT0Wb9rP5tFy5C2r x5IlP5k8Jm+cxeIxa+cTlgD2KC6blNSczLLUIn27BK6MS8v2Mha8l61Y9DSlgfGmeBcjJ4eE gInEy6+HWCFsMYkL99azdTFycQgJHGKU+Pr0ADuEs4RRouvWYnaQKjYBPYlrN5+D2SICGhLX liwBK2IW2Mki8XrSbSaQhLCAucTc04tZIIosJA62PYayjSSmr+tkBrFZBFQlZrWvARvEK+Ar 8Wf5B0aIbbMYJdZPWM8IkuAU0JY4PfEWWBEj0H3fT60BW8AsIC5x68l8Joi7BSSW7DnPDGGL Srx8/A/oHw4gW1Fieb8cRLmexI2pU9ggbG2JZQtfM0PsFZQ4OfMJywRGsVlIps5C0jILScss JC0LGFlWMbLnJmbmpJcbbWIERuTBLb9VdzDeOSdyiFGag0VJnDfc9UKAkEB6YklqdmpqQWpR fFFpTmrxIUYmDk6pBsbtlxz3fcwyv73fYfGO2zemXfuyrJ1h1ewDLyr5RK1epTVsfWEls8fy eMq+3ZPPBszQLNxiNSVi0qsIzw2++gW7GguZNadf6Klflru12fho+RcXz7QZkonLn1+6rNft Nnn+d+eFz0y9vkzYc/HqnRUZVxaGZiVuezLl/a4in/2aQuwLNjfZVb1brMRSnJFoqMVcVJwI AMVD18OWAgAA
X-Mailman-Approved-At: Sun, 24 Mar 2013 08:09:10 -0700
Cc: "even.roni@huawei.com" <even.roni@huawei.com>, "avt@ietf.org" <avt@ietf.org>, "elisabetta.carrara@ericsson.com" <elisabetta.carrara@ericsson.com>, "mbaugher@cisco.com" <mbaugher@cisco.com>, Mats Näslund <mats.naslund@ericsson.com>, "matthias.schertler@gmx.net" <matthias.schertler@gmx.net>
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC3711 (3420)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 22 Mar 2013 17:47:52 -0000

Hello!

OK, putting it on hold for document update is fine with me.

BR
Karl

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: den 22 mars 2013 16:27
> To: Karl Norrman
> Cc: mbaugher@cisco.com; elisabetta.carrara@ericsson.com;
> mcgrew@cisco.com; Mats Näslund; Gonzalo Camarillo; keith.drage@alcatel-
> lucent.com; even.roni@huawei.com; matthias.schertler@gmx.net;
> avt@ietf.org; Gonzalo Camarillo; Richard Barnes
> Subject: Re: [Technical Errata Reported] RFC3711 (3420)
> 
> Using the criteria at
> <http://www.ietf.org/iesg/statement/errata-processing.html> I recommend
> putting this into Hold For Document Update.
> 
> ( I could make an argument for Reject, given the text in 3550 is very clear, but
> a working group can make that decision if 3771 is ever revised).
> 
> On 11/28/12 9:13 AM, Karl Norrman wrote:
> > Hello!
> >
> > I always considered the padding count to be part of the padding itself and
> hence it would be included in the encrypted portion.  However, the
> proposed errata below makes the text more explicit on this point.  So, if it
> can avoid some interoperability problems I'm all for accepting it.
> >
> > BR
> > Karl
> >
> >
> >> -----Original Message-----
> >> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> >> Sent: den 28 november 2012 15:32
> >> To: mbaugher@cisco.com; elisabetta.carrara@ericsson.com;
> >> mcgrew@cisco.com; Mats Näslund; Karl Norrman; Gonzalo Camarillo;
> >> rjsparks@nostrum.com; keith.drage@alcatel-lucent.com;
> >> even.roni@huawei.com
> >> Cc: matthias.schertler@gmx.net; avt@ietf.org;
> >> rfc-editor@rfc-editor.org
> >> Subject: [Technical Errata Reported] RFC3711 (3420)
> >>
> >>
> >> The following errata report has been submitted for RFC3711, "The
> >> Secure Real-time Transport Protocol (SRTP)".
> >>
> >> --------------------------------------
> >> You may review the report below and at:
> >> http://www.rfc-editor.org/errata_search.php?rfc=3711&eid=3420
> >>
> >> --------------------------------------
> >> Type: Technical
> >> Reported by: Matthias Schertler <matthias.schertler@gmx.net>
> >>
> >> Section: 3.1.
> >>
> >> Original Text
> >> -------------
> >>     The "Encrypted Portion" of an SRTP packet consists of the
> >> encryption    of the RTP payload (including RTP padding when
> >> present) of the    equivalent RTP packet.
> >>
> >> Corrected Text
> >> --------------
> >>     The "Encrypted Portion" of an SRTP packet consists of the
> >> encryption    of the RTP payload (including RTP padding and
> >> RTP pad count when present)    of the equivalent RTP packet.
> >>
> >> Notes
> >> -----
> >> In Figure 1 "RTP padding" and "RTP pad count" are different things.
> >> The text should use the same terminology in order to make clear that
> >> the padding count is encrypted.
> >>
> >> Instructions:
> >> -------------
> >> This errata 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.
> >>
> >> --------------------------------------
> >> RFC3711 (draft-ietf-avt-srtp-09)
> >> --------------------------------------
> >> Title               : The Secure Real-time Transport Protocol (SRTP)
> >> Publication Date    : March 2004
> >> Author(s)           : M. Baugher, D. McGrew, M. Naslund, E.
> >> Carrara, K. Norrman
> >> Category            : PROPOSED STANDARD
> >> Source              : Audio/Video Transport
> >> Area                : Real-time Applications and Infrastructure
> >> Stream              : IETF
> >> Verifying Party     : IESG