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

Magnus Westerlund <magnus.westerlund@ericsson.com> Mon, 04 April 2016 17:28 UTC

Return-Path: <magnus.westerlund@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 70C8612D115 for <avt@ietfa.amsl.com>; Mon, 4 Apr 2016 10:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2q4H5OlT-v_V for <avt@ietfa.amsl.com>; Mon, 4 Apr 2016 10:28:01 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FB3812D7E5 for <avt@ietf.org>; Mon, 4 Apr 2016 10:27:06 -0700 (PDT)
X-AuditID: c1b4fb3a-f79d86d000005b69-dd-5702a3e89d14
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 4D.40.23401.8E3A2075; Mon, 4 Apr 2016 19:27:04 +0200 (CEST)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.3.248.2; Mon, 4 Apr 2016 19:27:03 +0200
To: ben@nostrum.com, alissa@cooperw.in
References: <20150722191648.2D97918020A@rfc-editor.org> <55B0A8A7.7060005@ericsson.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <5702A3E2.2050106@ericsson.com>
Date: Mon, 04 Apr 2016 14:26:58 -0300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <55B0A8A7.7060005@ericsson.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUyM2K7lu6LxUzhBjMPalpMP/OX0eJlz0p2 i/mdp9ktpjb+Z3Vg8fjy5CWTx5IlP5k8Vi/5w+oxa+cTlgCWKC6blNSczLLUIn27BK6M/tlv mAva5StmTc9qYGwT72Lk5JAQMJGY/GcZE4QtJnHh3nq2LkYuDiGBI4wSi+duZ4FwljFK7Ly9 h72LkYNDWMBR4tNiaZAGEQEtiWmXfoCFhQQiJSb+kgQJMwtoS1yecQlsJpuAhcTNH41sIDYv UPxhxwxWEJtFQEViwYGZzCC2qECMxPF35xghagQlTs58wgJicwroSOy+d48NZDyzgL3Eg61l EOPlJZq3zgZrFQIa2dDUwTqBUXAWku5ZCB2zkHQsYGRexShanFpcnJtuZKSXWpSZXFycn6eX l1qyiREYzge3/LbawXjwueMhRgEORiUe3gWnGMOFWBPLiitzDzFKcDArifBKLWAKF+JNSays Si3Kjy8qzUktPsQozcGiJM6bE/kvTEggPbEkNTs1tSC1CCbLxMEp1cCoMZ1tkqPP7Ef1XtmO Z85K8Rm2/Le7sbbzacvVO7c8rPyzJmp2XN7W6qCc/fLb5GcKty3ib//oNd16WHJpBcekpK// ee68uxbOuON5xO1DMi3TtSa9sxX98fhB3ZkbYntfsVqGmfKLMHQx9HyYNq9JRmLBYrMTx7wu vA6J5QvYe6X/QsM/9Z0FSizFGYmGWsxFxYkA733uOmMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/P9ZNZiYAzDzl0Px7HSX-u16tacY>
Cc: finlayson@live555.com, avt@ietf.org
Subject: Re: [AVTCORE] [Technical Errata Reported] RFC3711 (4425)
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, 04 Apr 2016 17:28:03 -0000

Ben,

Can you please put this Errata into Held for Document update. I think 
you can change it to Editorial rather than Technical.

Cheers

Magnus


Den 2015-07-23 kl. 05:41, skrev Magnus Westerlund:
> Hi,
>
> I think this errata is editorial rather than technical. This as the
> error is in the part not specified by this RFC, rather as you say
> RFC3550. I don't think it is likely to cause any interoperability issue,
> but it should be retain. Thus I propose that it is put into the
>
> HOLD for Document update
>
> Category. Please provide an further comments on this.
>
> Cheers
>
> Magnus Westerlund
> (Chair)
>
>
> Den 2015-07-22 kl. 21:16, skrev RFC Errata System:
>> 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=4425
>>
>> --------------------------------------
>> Type: Technical
b>> Reported by: Ross Finlayson <finlayson@live555.com>
>>
>> Section: 3.4
>>
>> Original Text
>> -------------
>>        0                   1                   2                   3
>>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<+
>>       |V=2|P|    RC   |   PT=SR or RR   |             length          | |
>>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
>>
>>
>> Corrected Text
>> --------------
>>        0                   1                   2                   3
>>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<+
>>       |V=2|P|    RC   |   PT=SR or RR |             length          | |
>>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
>>
>>
>> Notes
>> -----
>> The boundary between the "PT=SR or RR" and the "length" fields is
>> wrong: The boundary is shown as being between bits 16 and 17; it
>> should be between bits 15 and 16.  I.e., the "PT=SR or RR" field
>> should be 8 bits long, not 9.
>>
>> This is just a minor bug, because the equivalent diagram in RFC 3550
>> (the normative reference for RTCP) is correct.  Nonetheless, this bug
>> should probably be added to the errata for RFC 3711
>>
>> 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.
>>
>> --------------------------------------
>> 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
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
>
>


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------