Re: [Idr] FW: New Version Notification for draft-kumari-deprecate-as-set-confed-set-00.txt

Hi, folks:

Is there really a need for another doc on deprecating AS_SET / 
AS_CONFED_SET?  Regardless the code in the software can not be removed.

-- Enke

On 7/9/12 9:21 AM, Sriram, Kotikalapudi wrote:
> Recall that RFC6472/BCP172 is a *recommendation* for not using AS_SET and AS_CONFED_SET in BGP.
> It was intended that eventually there would be a document to *proscribe*
> the use of the AS_SET and AS_CONFED_SET types of the AS_PATH in BGP.
> So this document ( http://tools.ietf.org/html/draft-kumari-deprecate-as-set-confed-set-00 )
> is being submitted for consideration by the WG to start work on a standards-track RFC
> for deprecation of AS_SET and AS_CONFED _SET in BGPv4.
> Any comments and suggestions would be welcome and much appreciated.
>
> Sriram / Warren
>
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Sent: Friday, July 06, 2012 7:40 PM
> To: sriram.ietf@gmail.com
> Cc: warren@kumari.net; Sriram, Kotikalapudi
> Subject: New Version Notification for draft-kumari-deprecate-as-set-confed-set-00.txt
>
> A new version of I-D, draft-kumari-deprecate-as-set-confed-set-00.txt
> has been successfully submitted by Kotikalapudi Sriram and posted to the IETF repository.
>
> Filename:	 draft-kumari-deprecate-as-set-confed-set
> Revision:	 00
> Title:		 Deprecation of AS_SET and AS_CONFED_SET in BGP
> Creation date:	 2012-07-07
> WG ID:		 Individual Submission
> Number of pages: 6
> URL:             http://www.ietf.org/internet-drafts/draft-kumari-deprecate-as-set-confed-set-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-kumari-deprecate-as-set-confed-set
> Htmlized:        http://tools.ietf.org/html/draft-kumari-deprecate-as-set-confed-set-00
>
> Abstract:
>     RFC 6472 (i.e., BCP 172) recommends not using AS_SET and
>     AS_CONFED_SET in BGP.  This document updates RFC 4271 and proscribes
>     the use of the AS_SET and AS_CONFED_SET types of the AS_PATH in
>     BGPv4.  This is done to simplify the design and implementation of BGP
>     and to make the semantics of the originator of a route more clear.
>     This will also simplify the design, implementation, and deployment of
>     ongoing work in the Secure Inter-Domain Routing Working Group.
>
> The IETF Secretariat
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr