[Pce] [Editorial Errata Reported] RFC5623 (1897)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 30 September 2009 11:42 UTC

Return-Path: <web-usrn@ISI.EDU>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5EDD3A6838 for <pce@core3.amsl.com>; Wed, 30 Sep 2009 04:42:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.904
X-Spam-Level:
X-Spam-Status: No, score=-16.904 tagged_above=-999 required=5 tests=[AWL=0.695, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQ9jgvkkemXv for <pce@core3.amsl.com>; Wed, 30 Sep 2009 04:42:51 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 607A73A67E3 for <pce@ietf.org>; Wed, 30 Sep 2009 04:42:51 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n8UBgug1023131; Wed, 30 Sep 2009 04:42:57 -0700 (PDT)
Received: (from web-usrn@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id n8UBgs2a023105; Wed, 30 Sep 2009 04:42:54 -0700 (PDT)
Date: Wed, 30 Sep 2009 04:42:54 -0700
Message-Id: <200909301142.n8UBgs2a023105@boreas.isi.edu>
To: oki@ice.uec.ac.jp, takeda.tomonori@lab.ntt.co.jp, jeanlouis.leroux@orange-ftgroup.com, adrian@olddog.co.uk, rcallon@juniper.net, adrian.farrel@huawei.com, jpv@cisco.com, julien.meuric@orange-ftgroup.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: web-usrn@boreas.isi.edu
X-Mailman-Approved-At: Wed, 30 Sep 2009 09:51:43 -0700
Cc: ah@TR-Sys.de, pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] [Editorial Errata Reported] RFC5623 (1897)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Sep 2009 11:42:52 -0000

The following errata report has been submitted for RFC5623,
"Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering".

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

--------------------------------------
Type: Editorial
Reported by: Alfred Hoenes <ah@TR-Sys.de>

Section: 4.1,

Original Text
-------------
a) Section 4.1, 2nd paragraph (bottom of page 10):

   A VNT Manager (VNTM) is defined as a functional element that manages
   and controls the VNT.  The PCE and VNT Manager are distinct
|  functional elements that may or may not be collocated.
                                                ^^

b) Section 4.2.4, trailing Note below Table 1 (on page 22):

   * Note that, in case of NSM-VNTM cooperation (separate flavor) and
     single PCE inter-layer path computation, the PCE function used by
|    NMS and VNTM may be collocated, but it will operate on separate
     TEDs.
                           ^^

Corrected Text
--------------
a)

   A VNT Manager (VNTM) is defined as a functional element that manages
   and controls the VNT.  The PCE and VNT Manager are distinct
|  functional elements that may or may not be co-located.

b)

   * Note that, in case of NSM-VNTM cooperation (separate flavor) and
     single PCE inter-layer path computation, the PCE function used by
|    NMS and VNTM may be co-located, but it will operate on separate
     TEDs.
 

Notes
-----
Rationale:
  "collocated" and "co-located" (or "colocated") have very different
  semantics!  The latter seems to be the appropriate choice: two
  logical entites (or subsystems) are located within the same system.
  The former means "arranged/placed/sorted *somehow*, in the proper
  way", without emphasis on neighborship or common enclosement.

Instructions:
-------------
This errata 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. 

--------------------------------------
RFC5623 (draft-ietf-pce-inter-layer-frwk-10)
--------------------------------------
Title               : Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering
Publication Date    : September 2009
Author(s)           : E. Oki, T. Takeda, JL. Le Roux, A. Farrel
Category            : INFORMATIONAL
Source              : Path Computation Element
Area                : Routing
Stream              : IETF
Verifying Party     : IESG