[mpls] [Technical Errata Reported] RFC8577 (5743)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 30 May 2019 04:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FC212007A for <mpls@ietfa.amsl.com>; Wed, 29 May 2019 21:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 fQ1rAlkB9o0k for <mpls@ietfa.amsl.com>; Wed, 29 May 2019 21:51:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9F7A12004F for <mpls@ietf.org>; Wed, 29 May 2019 21:51:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0476BB8211C; Wed, 29 May 2019 21:51:33 -0700 (PDT)
To: harish.ietf@gmail.com, vbeeram@juniper.net, tejal.parikh@verizon.com, tsaad.net@gmail.com, db3546@att.com, aretana.ietf@gmail.com, martin.vigoureux@nokia.com, loa@pi.nu, n.leymann@telekom.de, tsaad.net@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: vishnupavan@gmail.com, mpls@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190530045133.0476BB8211C@rfc-editor.org>
Date: Wed, 29 May 2019 21:51:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/JinNkPDpKII5LBTwZR1raBwN4ag>
Subject: [mpls] [Technical Errata Reported] RFC8577 (5743)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2019 04:51:38 -0000
The following errata report has been submitted for RFC8577, "Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5743 -------------------------------------- Type: Technical Reported by: Vishnu Pavan Beeram <vishnupavan@gmail.com> Section: 11.3 Original Text ------------- IANA manages the "Record Route Object Sub-object Flags" registry as part of the "Resource Reservation Protocol-Traffic Engineering (RSVP- TE) Parameters" registry located at <http://www.iana.org/assignments/ rsvp-te-parameters>. Prior to this document, this registry did not include Label Sub-object Flags. This document creates the addition of a new subregistry for Label Sub-object Flags as shown below. Flag Name Reference 0x1 Global Label [RFC3209] 0x02 TE Link Label [RFC8577], Section 9.3 0x04 Delegation Label [RFC8577], Section 9.5 Corrected Text -------------- IANA manages the "Record Route Object Sub-object Flags" registry as part of the "Resource Reservation Protocol-Traffic Engineering (RSVP- TE) Parameters" registry located at <http://www.iana.org/assignments/ rsvp-te-parameters>. Prior to this document, this registry did not include Label Sub-object Flags. This document creates the addition of a new subregistry for Label Sub-object Flags as shown below. Flag Name Reference 0x1 Global Label [RFC3209] 0x02 TE Link Label [RFC8577], Section 9.3 0x04 Delegation Label [RFC8577], Section 9.5 All assignments in this sub-registry are to be performed via Standards Action. Notes ----- This errata is being reported as a response to the following email from IANA. ** Authors/WG Chairs/ADs for RFC 8577, During the publication process, the registration procedures were unintentionally removed from the document. Is this something that an errata should be submitted for? In version 9 of the document, it says: All assignments in this sub-registry are to be performed via Standards Action. In the published RFC this sentence does not appear to be there. Please advise. Thank you, Michelle Cotton Protocol Parameters Engagement Sr. Manager 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. -------------------------------------- RFC8577 (draft-ietf-mpls-rsvp-shared-labels-09) -------------------------------------- Title : Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane Publication Date : April 2019 Author(s) : H. Sitaraman, V. Beeram, T. Parikh, T. Saad Category : PROPOSED STANDARD Source : Multiprotocol Label Switching Area : Routing Stream : IETF Verifying Party : IESG
- [mpls] [Technical Errata Reported] RFC8577 (5743) RFC Errata System
- Re: [mpls] [Technical Errata Reported] RFC8577 (5… Loa Andersson
- Re: [mpls] [Technical Errata Reported] RFC8577 (5… BRUNGARD, DEBORAH A