[mpls] [Errata Held for Document Update] RFC3209 (4733)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 12 July 2016 22:21 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 5C39D12DA66; Tue, 12 Jul 2016 15:21:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 NS_Stj_PO1Wk; Tue, 12 Jul 2016 15:21:56 -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 B5DC012DA79; Tue, 12 Jul 2016 15:21:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A1ED5B80DF2; Tue, 12 Jul 2016 15:21:47 -0700 (PDT)
To: ramakrishnadtv@infosys.com, awduche@movaz.com, lberger@movaz.com, dhg@juniper.net, tli@procket.com, vsriniva@cosinecom.com, swallow@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160712222147.A1ED5B80DF2@rfc-editor.org>
Date: Tue, 12 Jul 2016 15:21:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/IacXuL2HgQH3qwvolkHYpGoSKr0>
Cc: mpls@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] [Errata Held for Document Update] RFC3209 (4733)
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 12 Jul 2016 22:21:57 -0000

The following errata report has been held for document update 
for RFC3209, "RSVP-TE: Extensions to RSVP for LSP Tunnels". 

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3209&eid=4733

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Ramakrishna DTV <ramakrishnadtv@infosys.com>
Date Reported: 2016-07-06
Held by: Deborah Brungard (IESG)

Section: 4.3.2

Original Text
-------------
   To formalize the discussion, we call each group of nodes an abstract
   node.  Thus, we say that an explicit route is a specification of a
   set of abstract nodes to be traversed.  If an abstract node consists
   of only one node, we refer to it as a simple abstract node.


Corrected Text
--------------
   To formalize the discussion, we call each group of nodes an abstract
   node.  Thus, we say that an explicit route is a specification of a
   sequence of abstract nodes to be traversed.  If an abstract node 
   consists of only one node, we refer to it as a simple abstract node.


Notes
-----
s/set/sequence

A set implies ordering of abstract nodes is NOT important.
A sequence implies ordering of abstract nodes IS important.

In the rest of RFC 3209, this distinction is maintained, but not
in this paragraph.

--------------------------------------
RFC3209 (draft-ietf-mpls-rsvp-lsp-tunnel-09)
--------------------------------------
Title               : RSVP-TE: Extensions to RSVP for LSP Tunnels
Publication Date    : December 2001
Author(s)           : D. Awduche, L. Berger, D. Gan, T. Li, V. Srinivasan, G. Swallow
Category            : PROPOSED STANDARD
Source              : Multiprotocol Label Switching
Area                : Routing
Stream              : IETF
Verifying Party     : IESG