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

Yakov Rekhter <yakov@juniper.net> Thu, 22 May 2008 12:09 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 [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 251C628C16B; Thu, 22 May 2008 05:09:57 -0700 (PDT)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 177233A69E5 for <idr@core3.amsl.com>; Thu, 22 May 2008 05:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QTX4mE7NcMZB for <idr@core3.amsl.com>; Thu, 22 May 2008 05:09:53 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id 9186D28C16B for <idr@ietf.org>; Thu, 22 May 2008 05:09:49 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP; Thu, 22 May 2008 05:09:46 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 May 2008 05:09:28 -0700
Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m4MC9Sx77651; Thu, 22 May 2008 05:09:28 -0700 (PDT) (envelope-from yakov@juniper.net)
Message-Id: <200805221209.m4MC9Sx77651@magenta.juniper.net>
To: "John G. Scudder" <jgs@bgp.nu>
In-Reply-To: Your message of "Tue, 29 Apr 2008 14:51:16 EDT." <818DEA85-D9F0-4899-A057-D621C5DA31D0@bgp.nu>
MIME-Version: 1.0
Content-ID: <14289.1211458168.1@juniper.net>
Date: Thu, 22 May 2008 05:09:28 -0700
From: Yakov Rekhter <yakov@juniper.net>
X-OriginalArrivalTime: 22 May 2008 12:09:28.0881 (UTC) FILETIME=[AF687A10:01C8BC04]
Cc: idr <idr@ietf.org>
Subject: Re: [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

John,

> Folks,
> 
> I've done some minor updates to the Capabilities Advertisement  
> specification to address confusion about the "Unsupported Capability"  
> NOTIFICATION message:
> 
> 	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?).

Based on the received responses your document is accepted as an IDR
WG item. Please resubmit it as draft-ietf-idr-rfc3392bis-00.txt

Yakov.
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr