Protocol Action: 'Capabilities Advertisement with BGP-4' to Draft Standard
The IESG <iesg-secretary@ietf.org> Wed, 14 January 2009 14:54 UTC
Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 797C23A6B3B; Wed, 14 Jan 2009 06:54:51 -0800 (PST)
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 7ED523A69F5; Wed, 14 Jan 2009 06:54:50 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Capabilities Advertisement with BGP-4' to Draft Standard
Message-Id: <20090114145450.7ED523A69F5@core3.amsl.com>
Date: Wed, 14 Jan 2009 06:54:50 -0800
Cc: idr mailing list <idr@ietf.org>, idr chair <idr-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
The IESG has approved the following document: - 'Capabilities Advertisement with BGP-4 ' <draft-ietf-idr-rfc3392bis-05.txt> as a Draft Standard This document is the product of the Inter-Domain Routing Working Group. The IESG contact persons are David Ward and Ross Callon. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idr-rfc3392bis-05.txt Technical Summary This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated. This document obsoletes RFC 3392. Working Group Summary There were no objections to this document within the IDR WG during the IDR WG Last Call. Document Quality There are multiple, interoperable implementations of this technology. Personnel Dave Ward RFC-Editor Note Please add this to the IANA Considerations section: IANA is requested to create and maintain a registry for OPEN message optional parameters called "BGP OPEN Optional Parameter Types". Optional parameters are identified by the Parameter Type, which is a one-octet unsigned integer. Values (0 reserved, 1-255) are to be allocated according to the "IETF Review" policy as defined in [RFC5226]. The registry should be populated with the two Parameter Type codes that are currently defined: o Parameter Type 1: Authentication (deprecated). o Parameter Type 2: Capabilities ([RFC3392bis]) IANA Note See RFC-Editor note for instructions on the new registry. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce