[Editorial Errata Reported] RFC6016 (2554)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 12 October 2010 17:44 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF7F03A69F7 for <tsvwg@core3.amsl.com>; Tue, 12 Oct 2010 10:44:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.278
X-Spam-Level:
X-Spam-Status: No, score=-102.278 tagged_above=-999 required=5 tests=[AWL=0.322, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 jFQvrEQM0FAG for <tsvwg@core3.amsl.com>; Tue, 12 Oct 2010 10:44:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id BC6763A69D3 for <tsvwg@ietf.org>; Tue, 12 Oct 2010 10:44:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C1BCFE06EE; Tue, 12 Oct 2010 10:45:48 -0700 (PDT)
To: bsd@cisco.com, flefauch@cisco.com, ashokn@cisco.com, ietfdbh@comcast.net, lars.eggert@nokia.com, jmpolk@cisco.com, gorry@erg.abdn.ac.uk
Subject: [Editorial Errata Reported] RFC6016 (2554)
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20101012174548.C1BCFE06EE@rfc-editor.org>
Date: Tue, 12 Oct 2010 10:45:48 -0700
Cc: ah@TR-Sys.de, tsvwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 17:44:40 -0000
The following errata report has been submitted for RFC6016, "Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6016&eid=2554 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes <ah@TR-Sys.de> Section: Abstract Original Text ------------- RFC 4364 and RFC 4659 define an approach to building provider- provisioned Layer 3 VPNs (L3VPNs) for IPv4 and IPv6. It may be | desirable to use Resource Reservation Protocol (RSVP) to perform admission control on the links between Customer Edge (CE) routers and Provider Edge (PE) routers. [...] Corrected Text -------------- RFC 4364 and RFC 4659 define an approach to building provider- provisioned Layer 3 VPNs (L3VPNs) for IPv4 and IPv6. It may be | desirable to use the Resource Reservation Protocol (RSVP) to perform admission control on the links between Customer Edge (CE) routers and Provider Edge (PE) routers. [...] Notes ----- Rationale: Missing article 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. -------------------------------------- RFC6016 (draft-ietf-tsvwg-rsvp-l3vpn-07) -------------------------------------- Title : Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNs Publication Date : October 2010 Author(s) : B. Davie, F. Le Faucheur, A. Narayanan Category : PROPOSED STANDARD Source : Transport Area Working Group Area : Transport Stream : IETF Verifying Party : IESG
- [Editorial Errata Reported] RFC6016 (2554) RFC Errata System