Re: [AVTCORE] [Editorial Errata Reported] RFC3711 (4514)

"Ben Campbell" <ben@nostrum.com> Fri, 30 October 2015 01:49 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFE981B33FC for <avt@ietfa.amsl.com>; Thu, 29 Oct 2015 18:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eRAEQlCdk8Bo for <avt@ietfa.amsl.com>; Thu, 29 Oct 2015 18:49:09 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C5811B33E5 for <avt@ietf.org>; Thu, 29 Oct 2015 18:49:09 -0700 (PDT)
Received: from [10.71.15.21] ([101.110.53.38]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t9U1mv8d046621 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 29 Oct 2015 20:48:58 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [101.110.53.38] claimed to be [10.71.15.21]
From: "Ben Campbell" <ben@nostrum.com>
To: "Karl Norrman" <karl.norrman@ericsson.com>
Date: Fri, 30 Oct 2015 10:48:51 +0900
Message-ID: <CFC30752-5373-4F1F-B1B1-5E673592454C@nostrum.com>
In-Reply-To: <33E51946CDE71249AF9D86CE4D8966B428AA4AE3@ESESSMB203.ericsson.se>
References: <20151029114025.CAB65180092@rfc-editor.org> <33E51946CDE71249AF9D86CE4D8966B428AA4AE3@ESESSMB203.ericsson.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/avt/DE6l4nXRbYtVsc3LiYOXcqpuvn8>
Cc: "mcgrew@cisco.com" <mcgrew@cisco.com>, "bernhard.kirchen@lancom.de" <bernhard.kirchen@lancom.de>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] [Editorial Errata Reported] RFC3711 (4514)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 30 Oct 2015 01:49:10 -0000

Agreed on both points. Since it does not appear to impact 
interoperability, I marked it as "held for update".

Thanks!

Ben.

On 29 Oct 2015, at 21:10, Karl Norrman wrote:

> Hello!
>
> I agree that the figure would look better if the proposed correction 
> is made.
> On the other hand, I can't really see that the current figure could be 
> misinterpreted by an implementer, so I consider this to be an 
> editorial correction.
>
> BR
> Karl
>
>> -----Original Message-----
>> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
>> Sent: den 29 oktober 2015 12:40
>> To: mbaugher@cisco.com; elisabetta.carrara@ericsson.com;
>> mcgrew@cisco.com; Mats Näslund; Karl Norrman; ben@nostrum.com;
>> alissa@cooperw.in; keith.drage@alcatel-lucent.com;
>> roni.even@mail01.huawei.com
>> Cc: bernhard.kirchen@lancom.de; avt@ietf.org; 
>> rfc-editor@rfc-editor.org
>> Subject: [Editorial Errata Reported] RFC3711 (4514)
>>
>> 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=4514
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: Bernhard Kirchen <bernhard.kirchen@lancom.de>
>>
>> Section: 3.1
>>
>> Original Text
>> -------------
>> The format of an SRTP packet is illustrated in Figure 1.
>>
>> 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
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<+
>>
>> Corrected Text
>> --------------
>> The format of an SRTP packet is illustrated in Figure 1.
>>
>> 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
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<+
>>
>> Notes
>> -----
>> The bit index second decimal digit is shifted by two characters. 
>> These digits
>> should align with the zeros in the second 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.
>>
>> --------------------------------------
>> 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