Re: [spring] [Technical Errata Reported] RFC8660 (5891)
<bruno.decraene@orange.com> Mon, 13 January 2020 14:43 UTC
Return-Path: <bruno.decraene@orange.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4B8E12003E for <spring@ietfa.amsl.com>; Mon, 13 Jan 2020 06:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 bp5nDFrIe2ma for <spring@ietfa.amsl.com>; Mon, 13 Jan 2020 06:43:49 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C8FB1200D6 for <spring@ietf.org>; Mon, 13 Jan 2020 06:43:49 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 47xGYb0CYCz2xvQ; Mon, 13 Jan 2020 15:43:47 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 47xGYZ4Kc1z5vNH; Mon, 13 Jan 2020 15:43:46 +0100 (CET)
Received: from OPEXCAUBM43.corporate.adroot.infra.ftgroup ([fe80::b846:2467:1591:5d9d]) by OPEXCAUBM5D.corporate.adroot.infra.ftgroup ([fe80::8899:bbc3:9726:cd5e%21]) with mapi id 14.03.0468.000; Mon, 13 Jan 2020 15:43:41 +0100
From: bruno.decraene@orange.com
To: "arusso@amsl.com" <arusso@amsl.com>, "martin.vigoureux@nokia.com" <martin.vigoureux@nokia.com>
CC: "spring@ietf.org" <spring@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>, "abashandy.ietf@gmail.com" <abashandy.ietf@gmail.com>, "cfilsfil@cisco.com" <cfilsfil@cisco.com>, "stefano@previdi.net" <stefano@previdi.net>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "robjs@google.com" <robjs@google.com>, "db3546@att.com" <db3546@att.com>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "robjs@google.com" <robjs@google.com>
Thread-Topic: [Technical Errata Reported] RFC8660 (5891)
Thread-Index: AQHVyPqtdPQLC8o5JEqKzFpgVohkRqfoq4yQ
Date: Mon, 13 Jan 2020 14:43:41 +0000
Message-ID: <12928_1578926626_5E1C8222_12928_423_5_67587ab9-c013-4388-9956-3ecfdcd8fc68@OPEXCAUBM5D.corporate.adroot.infra.ftgroup>
References: <20200112032326.5F35366423F@devb.amsl.com>
In-Reply-To: <20200112032326.5F35366423F@devb.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/yuiJi2H8nhoQ-_dU1tH13OPTFuA>
Subject: Re: [spring] [Technical Errata Reported] RFC8660 (5891)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2020 14:43:52 -0000
Alice, To the best of my knowledge those two errata (5891 & 5890) are to be ignored. In particular because: - as of today in the errata system both errata refers to different RFCs and no errata refers to RFC 8660 https://www.rfc-editor.org/errata_search.php?eid=5890 https://www.rfc-editor.org/errata/eid5891 https://www.rfc-editor.org/errata_search.php?rfc=8660&rec_status=15&presentation=records - RFC8660 has no section 3.5, no section 3.6, no text matching 'testing'. If this is not correct conclusion, please reply to this email. Thank you, --Bruno -----Original Message----- From: RFC Errata System [mailto:rfc-editor@rfc-editor.org] Sent: Tuesday, January 7, 2020 7:48 PM To: abashandy.ietf@gmail.com; cfilsfil@cisco.com; stefano@previdi.net; DECRAENE Bruno TGI/OLN; stephane.litkowski@orange.com; robjs@google.com; db3546@att.com; aretana.ietf@gmail.com; martin.vigoureux@nokia.com; DECRAENE Bruno TGI/OLN; robjs@google.com Cc: arusso@amsl.com; spring@ietf.org; rfc-editor@rfc-editor.org Subject: [Technical Errata Reported] RFC8660 (5891) The following errata report has been submitted for RFC8660, "Segment Routing with MPLS data plane". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid5891 -------------------------------------- Type: Technical Reported by: Alice Russo <arusso@amsl.com> Section: 3.6 Original Text ------------- testing4 Corrected Text -------------- testing5 Notes ----- testing6 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. -------------------------------------- RFC8660 (draft-ietf-spring-segment-routing-mpls-22) -------------------------------------- Title : Segment Routing with MPLS data plane Publication Date : January 2020 Author(s) : A. Bashandy, Ed., C. Filsfils, Ed., S. Previdi, B. Decraene, S. Litkowski, R. Shakir Category : PROPOSED STANDARD Source : Source Packet Routing in Networking Area : Routing Stream : IETF Verifying Party : IESG _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- Re: [spring] [Technical Errata Reported] RFC8660 … bruno.decraene