[PWE3] [Technical Errata Reported] RFC5003 (3411)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 15 November 2012 20:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE71A21F856B for <pwe3@ietfa.amsl.com>; Thu, 15 Nov 2012 12:17:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.127
X-Spam-Level:
X-Spam-Status: No, score=-102.127 tagged_above=-999 required=5 tests=[AWL=0.473, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jnSHFXEyTCOO for <pwe3@ietfa.amsl.com>; Thu, 15 Nov 2012 12:17:00 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5489621F8568 for <pwe3@ietf.org>; Thu, 15 Nov 2012 12:17:00 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D8DF0B1E002; Thu, 15 Nov 2012 12:09:56 -0800 (PST)
To: chmetz@cisco.com, lmartini@cisco.com, florin.balus@alcatel-lucent.com, sugimoto@nortel.com, rdroms.ietf@gmail.com, brian@innovationslab.net, matthew.bocci@alcatel-lucent.com, andrew.g.malis@verizon.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20121115200956.D8DF0B1E002@rfc-editor.org>
Date: Thu, 15 Nov 2012 12:09:56 -0800
Cc: rfc-editor@rfc-editor.org, pwe3@ietf.org
Subject: [PWE3] [Technical Errata Reported] RFC5003 (3411)
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 20:17:00 -0000
The following errata report has been submitted for RFC5003, "Attachment Individual Identifier (AII) Types for Aggregation". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5003&eid=3411 -------------------------------------- Type: Technical Reported by: Rajiv Asati <rajiva@cisco.com> Section: 3.2 Original Text ------------- o Prefix = The 32-bit prefix is a value assigned by the provider or it can be automatically derived from the PE's /32 IPv4 loopback address. Note that, for IP reachability, it is not required that the 32-bit prefix have any association with the IPv4 address space used in the provider's IGP or BGP. Corrected Text -------------- o Prefix = The 32-bit prefix is a value assigned by the provider or it can be automatically derived from the PE's router-id i.e. LSR Id. Note that it is not required that the 32-bit prefix is IP routable or have any association with the IPv4 address space used in the provider's IGP or BGP. Notes ----- The intent of this RFC is to treat the 32bit prefix as a number that provides uniqueness in the network (within the ASN). While it can be derived from the IPv4 /32 Loopback address, it causes confusion when routers are configured with no IPv4. It is better to suggest using router-id used by LDP for calculating the LSR identifier. How is router-id calculated is outside the scope of this document.` 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. -------------------------------------- RFC5003 (draft-ietf-pwe3-aii-aggregate-02) -------------------------------------- Title : Attachment Individual Identifier (AII) Types for Aggregation Publication Date : September 2007 Author(s) : C. Metz, L. Martini, F. Balus, J. Sugimoto Category : PROPOSED STANDARD Source : Pseudo Wire Emulation Edge to Edge INT Area : Internet Stream : IETF Verifying Party : IESG
- [PWE3] [Technical Errata Reported] RFC5003 (3411) RFC Errata System
- Re: [PWE3] [Technical Errata Reported] RFC5003 (3… Luca Martini
- Re: [PWE3] [Technical Errata Reported] RFC5003 (3… Brian Haberman
- Re: [PWE3] [Technical Errata Reported] RFC5003 (3… Rajiv Asati (rajiva)
- Re: [PWE3] [Technical Errata Reported] RFC5003 (3… Yaakov Stein
- Re: [PWE3] [Technical Errata Reported] RFC5003 (3… Carlos Pignataro (cpignata)
- Re: [PWE3] [Technical Errata Reported] RFC5003 (3… Lizhong Jin