[Idr] Fwd: New Version Notification for draft-scudder-idr-rfc3392-bis-00

"John G. Scudder" <jgs@bgp.nu> Tue, 29 April 2008 18:52 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from core3.amsl.com (localhost []) by core3.amsl.com (Postfix) with ESMTP id 786943A6D0B; Tue, 29 Apr 2008 11:52:05 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 164DB3A6D0B for <idr@core3.amsl.com>; Tue, 29 Apr 2008 11:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id 5W83XFvQ-LFn for <idr@core3.amsl.com>; Tue, 29 Apr 2008 11:52:04 -0700 (PDT)
Received: from bgp.nu (bgp.nu []) by core3.amsl.com (Postfix) with ESMTP id C858C3A6DD6 for <idr@ietf.org>; Tue, 29 Apr 2008 11:51:33 -0700 (PDT)
Received: from localhost (bgp.nu []) by bgp.nu (Postfix) with ESMTP id 9BCB453E1B5 for <idr@ietf.org>; Tue, 29 Apr 2008 14:51:36 -0400 (EDT)
X-Virus-Scanned: amavisd-new at bgp.nu
Received: from bgp.nu ([]) by localhost (bgp.nu []) (amavisd-new, port 10024) with LMTP id 7AKowXBtDHgi for <idr@ietf.org>; Tue, 29 Apr 2008 14:51:19 -0400 (EDT)
Received: from [] (dsl093-003-111.det1.dsl.speakeasy.net []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by bgp.nu (Postfix) with ESMTP id E653F53E0FC for <idr@ietf.org>; Tue, 29 Apr 2008 14:51:18 -0400 (EDT)
Message-Id: <818DEA85-D9F0-4899-A057-D621C5DA31D0@bgp.nu>
From: "John G. Scudder" <jgs@bgp.nu>
To: idr <idr@ietf.org>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Tue, 29 Apr 2008 14:51:16 -0400
References: <20080429184121.CDDEA3A6CA9@core3.amsl.com>
X-Mailer: Apple Mail (2.919.2)
Subject: [Idr] Fwd: New Version Notification for draft-scudder-idr-rfc3392-bis-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org


I've done some minor updates to the Capabilities Advertisement  
specification to address confusion about the "Unsupported Capability"  

	Appendix B.  Comparison with RFC 3392
	   In addition to minor editorial changes, this document also clarifies
	   the use of the Unsupported Optional Parameter NOTIFICATION message,
	   and updates references to the base BGP-4 specification [RFC4271] and
	   security analysis [RFC4272].

The draft is at http://www.ietf.org/internet-drafts/draft-scudder-idr-rfc3392-bis-00.txt 

Comments welcome.  One thing that occurred to me was to rename  
"Unsupported Capability" to "Required Capability Missing", however  
that might do more harm than good by renaming an existing code point,  
so I didn't.

I'd like to propose this as a WG item (if indeed such a request is  
even required for an update to an existing WG document?).



Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: April 29, 2008 2:41:21 PM GMT-04:00
> To: jgs@juniper.net
> Cc: rchandra@sonoasystems.com
> Subject: New Version Notification for draft-scudder-idr-rfc3392-bis-00
> A new version of I-D, draft-scudder-idr-rfc3392-bis-00.txt has been  
> successfuly submitted by John Scudder and posted to the IETF  
> repository.
> Filename:	 draft-scudder-idr-rfc3392-bis
> Revision:	 00
> Title:		 Capabilities Advertisement with BGP-4
> Creation_date:	 2008-04-29
> WG ID:		 Independent Submission
> Number_of_pages: 7
> Abstract:
> 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.
> The IETF Secretariat.

Idr mailing list