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

Danny McPherson <danny@tcb.net> Wed, 30 April 2008 14:02 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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 805AA3A6B46; Wed, 30 Apr 2008 07:02:53 -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 8D7273A6A71 for <idr@core3.amsl.com>; Wed, 30 Apr 2008 07:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599]
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 nVi4zrqQ8Ym3 for <idr@core3.amsl.com>; Wed, 30 Apr 2008 07:02:50 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id B15B83A6BE4 for <idr@ietf.org>; Wed, 30 Apr 2008 07:02:49 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id AD182268494; Wed, 30 Apr 2008 08:02:52 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET [151.118.146.11]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Wed, 30 Apr 2008 08:02:52 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11; client-port=55539; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S; data-bytes=0
Message-Id: <0B82A4F5-4D76-427B-8CB3-386C0F6A64F2@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: Yakov Rekhter <yakov@juniper.net>
In-Reply-To: <200804301333.m3UDX4x97759@magenta.juniper.net>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 30 Apr 2008 08:02:37 -0600
References: <200804301333.m3UDX4x97759@magenta.juniper.net>
X-Mailer: Apple Mail (2.919.2)
Cc: idr@ietf.org
Subject: Re: [Idr] Fwd: New Version Notification for draft-scudder-idr-rfc3392-bis-
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

On Apr 30, 2008, at 7:33 AM, Yakov Rekhter wrote:

> Folks,
>
> There is a request (see attached) to accept draft-scudder-idr- 
> rfc3392-bis
> as an IDR WG item. Please send your comments to the list. The deadline
> for comments is May 14.

I support this as an IDR WG item.

One minor comment..   I think we should rename "Unsupported Capability"
to "Required Capability Missing", and given that the codepoint itself  
isn't
changing, just the descriptor, there should be no issues here.

-danny


>
>
> Yakov.
> ------- Forwarded Message
>
> Date:    Tue, 29 Apr 2008 14:51:16 -0400
> From:    "John G. Scudder" <jgs@bgp.nu>
> To:      idr <idr@ietf.org>
> Subject: [Idr] Fwd: New Version Notification for draft-scudder-idr- 
> rfc3392-bis-
> 	  00
>
> 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-b
> is-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?).
>
> Thanks,
>
> - --John
>
> 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
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>
> ------- End of Forwarded Message
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

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