[Technical Errata Reported] RFC6368 (4309)

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 20 March 2015 15:08 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27D281AC43A for <l3vpn@ietfa.amsl.com>; Fri, 20 Mar 2015 08:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 DIcgsFUSYNRm for <l3vpn@ietfa.amsl.com>; Fri, 20 Mar 2015 08:08:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id BEAF41AC434 for <l3vpn@ietf.org>; Fri, 20 Mar 2015 08:08:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 036EF180208; Fri, 20 Mar 2015 08:07:06 -0700 (PDT)
To: pedro.r.marques@gmail.com, robert@raszuk.net, keyupate@cisco.com, ke-kumaki@kddi.com, to-yamagata@kddi.com, akatlas@gmail.com, adrian@olddog.co.uk, martin.vigoureux@alcatel-lucent.com, thomas.morin@orange.com
Subject: [Technical Errata Reported] RFC6368 (4309)
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20150320150706.036EF180208@rfc-editor.org>
Date: Fri, 20 Mar 2015 08:07:06 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/l3vpn/1ScUBZGT6P4RkhoMbpbIV6iiSmM>
Cc: guillaume.gaulon@orange.com, l3vpn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn/>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Mar 2015 15:08:23 -0000

The following errata report has been submitted for RFC6368,
"Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)".

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

--------------------------------------
Type: Technical
Reported by: Guillaume Gaulon <guillaume.gaulon@orange.com>;

Section: 7

Original Text
-------------
   In the traditional model, where External BGP sessions are used
   between the BGP/MPLS VPN PE and CE, the PE router identifies itself
   as belonging to the customer network autonomous system.

Corrected Text
--------------
   In the traditional model, where External BGP sessions are used
   between the BGP/MPLS VPN PE and CE, the PE router identifies itself
   as belonging to the provider network autonomous system.

Notes
-----


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 (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6368 (draft-ietf-l3vpn-ibgp-08)
--------------------------------------
Title               : Internal BGP as the Provider/Customer Edge Protocol for BGP/MPLS IP Virtual Private Networks (VPNs)
Publication Date    : September 2011
Author(s)           : P. Marques, R. Raszuk, K. Patel, K. Kumaki, T. Yamagata
Category            : PROPOSED STANDARD
Source              : Layer 3 Virtual Private Networks
Area                : Routing
Stream              : IETF
Verifying Party     : IESG