Re: [IPFIX] [Editorial Errata Reported] RFC7012 (6564)

Benoit Claise <benoit.claise@huawei.com> Thu, 29 April 2021 07:23 UTC

Return-Path: <benoit.claise@huawei.com>
X-Original-To: ipfix@ietfa.amsl.com
Delivered-To: ipfix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962163A33B7 for <ipfix@ietfa.amsl.com>; Thu, 29 Apr 2021 00:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 xX9x2LQMQpy2 for <ipfix@ietfa.amsl.com>; Thu, 29 Apr 2021 00:23:19 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C6D73A33B6 for <ipfix@ietf.org>; Thu, 29 Apr 2021 00:23:19 -0700 (PDT)
Received: from fraeml745-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4FW6C62mJDz70gQ2 for <ipfix@ietf.org>; Thu, 29 Apr 2021 15:12:34 +0800 (CST)
Received: from fraeml795-chm.china.huawei.com (10.206.15.16) by fraeml745-chm.china.huawei.com (10.206.15.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 29 Apr 2021 09:23:12 +0200
Received: from fraeml795-chm.china.huawei.com (10.206.15.16) by fraeml795-chm.china.huawei.com (10.206.15.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 29 Apr 2021 09:23:12 +0200
Received: from DGGEMS411-HUB.china.huawei.com (10.3.19.211) by fraeml795-chm.china.huawei.com (10.206.15.16) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2176.2 via Frontend Transport; Thu, 29 Apr 2021 09:23:11 +0200
Received: from [10.47.73.169] (10.47.73.169) by DGGEMS411-HUB.china.huawei.com (10.3.19.211) with Microsoft SMTP Server id 14.3.498.0; Thu, 29 Apr 2021 15:22:59 +0800
To: ipfix@ietf.org
References: <20210428201609.5BB3EF4075E@rfc-editor.org> <57c9182181ec49688eacdef45006bb7b@claise.be>
From: Benoit Claise <benoit.claise@huawei.com>
Message-ID: <8470fe7c-9079-69d4-90b3-0e02b53e0f63@huawei.com>
Date: Thu, 29 Apr 2021 09:23:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <57c9182181ec49688eacdef45006bb7b@claise.be>
Content-Type: multipart/alternative; boundary="------------13765614F2ED2EB0C958F635"
Content-Language: en-GB
X-Originating-IP: [10.47.73.169]
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipfix/-bp1KjBj1Ej0iqTXRuxm9OmeKuU>
Subject: Re: [IPFIX] [Editorial Errata Reported] RFC7012 (6564)
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 29 Apr 2021 07:23:25 -0000

Hi Paul,

IIRC, when we wrote:
    "The specification of new MPLS label types MUST be published using a 
well-established and persistent publication medium."
... we carefully crafted this sentence not to mention "publication 
requested" as RFC, with in idea in mind that an IANA registry would fall 
under the "well-established  and persistent publication medium" category.

Regards, Benoit
> ------------------------------------------------------------------------
> *De :* IPFIX <ipfix-bounces@ietf.org> de la part de RFC Errata System 
> <rfc-editor@rfc-editor.org>
> *Envoyé :* mercredi 28 avril 2021 22:16:09
> *À :* bclaise@cisco.com; trammell@tik.ee.ethz.ch; warren@kumari.net; 
> rwilton@cisco.com; n.brownlee@auckland.ac.nz; quittek@neclab.eu
> *Cc :* ipfix@ietf.org; rfc-editor@rfc-editor.org
> *Objet :* [IPFIX] [Editorial Errata Reported] RFC7012 (6564)
> The following errata report has been submitted for RFC7012,
> "Information Model for IP Flow Information Export (IPFIX)".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6564 
> <https://www.rfc-editor.org/errata/eid6564>
>
> --------------------------------------
> Type: Editorial
> Reported by: Paul Aitken <paul.aitken@att.com>
>
> Section: 7.2
>
> Original Text
> -------------
>    The specification
>    of new MPLS label types MUST be published using a well-established
>    and persistent publication medium.
>
> Corrected Text
> --------------
> (Deleted)
>
> Notes
> -----
> This paragraph envisaged that a new RFC be written to specify new 
> label types in the mplsTopLabelType sub-registry.
>
> Since the publication of RFC7012, IANA has added 16 other IPFIX IE 
> sub-registries, none of which have the same requirement. See 
> https://www.iana.org/assignments/ipfix/ipfix.xhtml 
> <https://www.iana.org/assignments/ipfix/ipfix.xhtml>
>
> Publication in IANA's IPFIX registry should provide a clear and 
> persistent definition. New IPFIX MPLS label type specifications should 
> not be singled out to require persistent publication of an additional 
> document.
>
> 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
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC7012 (draft-ietf-ipfix-information-model-rfc5102bis-10)
> --------------------------------------
> Title               : Information Model for IP Flow Information Export 
> (IPFIX)
> Publication Date    : September 2013
> Author(s)           : B. Claise, Ed., B. Trammell, Ed.
> 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 
> <https://www.ietf.org/mailman/listinfo/ipfix>