Re: [IPFIX] [Editorial Errata Reported] RFC6728 (4370)

Gerhard Muenz <muenz@net.in.tum.de> Fri, 22 May 2015 18:55 UTC

Return-Path: <muenz@net.in.tum.de>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59B941A00BE for <ipfix@ietfa.amsl.com>; Fri, 22 May 2015 11:55:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level:
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3] 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 CbFXbSbTcYgh for <ipfix@ietfa.amsl.com>; Fri, 22 May 2015 11:55:28 -0700 (PDT)
Received: from mail-out1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 735621A000E for <ipfix@ietf.org>; Fri, 22 May 2015 11:55:25 -0700 (PDT)
Received: from [192.168.2.26] (x5ce59976.dyn.telefonica.de [92.229.153.118]) by mail.net.in.tum.de (Postfix) with ESMTPSA id E0268188DCBF; Fri, 22 May 2015 20:55:21 +0200 (CEST)
Message-ID: <555F7B9E.6080901@net.in.tum.de>
Date: Fri, 22 May 2015 20:55:26 +0200
From: Gerhard Muenz <muenz@net.in.tum.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, Paul Aitken <paitken@brocade.com>, "stbryant@cisco.com" <stbryant@cisco.com>, RFC Errata System <rfc-editor@rfc-editor.org>, "paitken@cisco.com" <paitken@cisco.com>, "joelja@bogus.com" <joelja@bogus.com>, "n.brownlee@auckland.ac.nz" <n.brownlee@auckland.ac.nz>, "quittek@neclab.eu" <quittek@neclab.eu>
References: <20150521161640.89DF3180452@rfc-editor.org> <555E069E.50707@brocade.com> <555E0B50.4000000@cisco.com> <555E0C6B.4070506@brocade.com> <555E19C4.4010704@cisco.com>
In-Reply-To: <555E19C4.4010704@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipfix/W9cLIbc9-oA0uMqvfkJ9ANps4UI>
Cc: "ipfix@ietf.org" <ipfix@ietf.org>, "mwd@cert.org" <mwd@cert.org>
Subject: Re: [IPFIX] [Editorial Errata Reported] RFC6728 (4370)
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix/>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 May 2015 18:55:30 -0000

Hi,

Thanks for reporting this error.
Luckily, it does not repeat in the yang module specification nor in any 
example or diagram. So, I do not think that this error has mislead any 
reader of the RFC. "Editorial" seems right for me.

Regards,
Gerhard

On 21.05.2015 19:45, Benoit Claise wrote:
> On 21/05/2015 18:48, Paul Aitken wrote:
>> cut-n-paste typo; editorial.
>>
>> The meaning is clear from the immediately preceding diagram (Figure 29).
> That was my rational in accepting this as editorial.
> And I checked http://www.rfc-editor.org/status_type_desc.html
> Granted, this one is on the boundary.
>
> Regards, Benoit
>>
>> P.
>>
>>
>> On 21/05/15 17:44, Stewart Bryant wrote:
>>> Surely it is technical rather than editorial.
>>>
>>> Stewart
>>>
>>> On 21/05/2015 17:23, Paul Aitken wrote:
>>>> Good catch, Michael!
>>>>
>>>> P.
>>>>
>>>>
>>>> On 21/05/15 17:16, RFC Errata System wrote:
>>>>> The following errata report has been submitted for RFC6728,
>>>>> "Configuration Data Model for the IP Flow Information Export (IPFIX)
>>>>> and Packet Sampling (PSAMP) Protocols".
>>>>>
>>>>> --------------------------------------
>>>>> You may review the report below and at:
>>>>> http://www.rfc-editor.org/errata_search.php?rfc=6728&eid=4370
>>>>>
>>>>> --------------------------------------
>>>>> Type: Editorial
>>>>> Reported by: Michael Duggan <mwd@cert.org>
>>>>>
>>>>> Section: 4.8
>>>>>
>>>>> Original Text
>>>>> -------------
>>>>>      isFlowKey:  If this state parameter is present, this is a 
>>>>> Flow Key
>>>>>         field.
>>>>>         This parameter is only available for non-Options Templates 
>>>>> (i.e.,
>>>>>         if setId is 2).
>>>>>
>>>>>      isFlowKey:  If this state parameter is present, this is a scope
>>>>>         field.
>>>>>         This parameter is only available for Options Templates 
>>>>> (i.e., if
>>>>>         setId is 3).
>>>>>
>>>>> Corrected Text
>>>>> --------------
>>>>>      isFlowKey:  If this state parameter is present, this is a 
>>>>> Flow Key
>>>>>         field.
>>>>>         This parameter is only available for non-Options Templates 
>>>>> (i.e.,
>>>>>         if setId is 2).
>>>>>
>>>>>      isScope:    If this state parameter is present, this is a scope
>>>>>         field.
>>>>>         This parameter is only available for Options Templates 
>>>>> (i.e., if
>>>>>         setId is 3).
>>>>>
>>>>> Notes
>>>>> -----
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>> --------------------------------------
>>>>> RFC6728 (draft-ietf-ipfix-configuration-model-11)
>>>>> --------------------------------------
>>>>> Title               : Configuration Data Model for the IP Flow
>>>>> Information Export (IPFIX) and Packet Sampling (PSAMP) Protocols
>>>>> Publication Date    : October 2012
>>>>> Author(s)           : G. Muenz, B. Claise, P. Aitken
>>>>> Category            : PROPOSED STANDARD
>>>>> Source              : IP Flow Information Export
>>>>> Area                : Operations and Management
>>>>> Stream              : IETF
>>>>> Verifying Party     : IESG
>>>>>
>>>>> _______________________________________________
>>>>> IPFIX mailing list
>>>>> IPFIX@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/ipfix
>>>> _______________________________________________
>>>> IPFIX mailing list
>>>> IPFIX@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ipfix
>>>> .
>>>>
>>>
>>
>> .
>>
>