Re: I-D Action: draft-ietf-idr-deprecate-as-set-confed-set-01.txt

Alejandro Acosta <[email protected]> Tue, 29 Oct 2019 22:45:56 -0500
Newsgroups	gmane.ietf.idr
Message-ID	<[email protected]>
Hello,

  As a comment, we did a small research and these are our findings (hope
the table shows ok):

*
*

*

 

	

IPv4

	

IPv6

  RIPE ASs doing AS_SET

	

52

	

9

  RIPE Prefixes behind AS_SET 

	

111

	

9

  ARIN ASs*doing AS_SET*

	

50

	

5

  ARIN *Prefixes behind AS_SET*

	

127

	

10

  APNIC ASs *doing AS_SET*

	

11

	

4

  APNIC *Prefixes behind AS_SET*

	

46

	

8

  AFRINIC ASs*doing AS_SET*

	

1

	

0

  AFRINIC *Prefixes behind AS_SET*

	

7

	

0

  LACNIC ASs*doing AS_SET*

	

14

	

2

  LACNIC *Prefixes behind AS_SET*

	

96

	

7

*
**


Thanks,


Alejandro,



On 10/29/19 8:50 AM, Sriram, Kotikalapudi (Fed) wrote:
> We have incorporated all WG comments/suggestions ...
> from the WG adoption call discussions:
> https://mailarchive.ietf.org/arch/browse/idr/?gbt=1&index=PB8YtGMBvVLeAu6dot072VaDJNc 
> and also from a related thread (feedback requested):
> https://mailarchive.ietf.org/arch/browse/idr/?gbt=1&index=rqY4ipWnrz2TdYWkKIeZCby9HlY 
>
> The authors feel that the draft is now ready for WGLC.
> Do the Chairs and WG think that it is ready?  
> Chairs: Please advise if you think it needs to be presented (in Singapore). 
>
> Thank you.
> Sriram
>    
> --------------------------------------------------
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Inter-Domain Routing WG of the IETF.
>
>         Title           : Deprecation of AS_SET and AS_CONFED_SET in BGP
>         Authors         : Warren Kumari
>                           Kotikalapudi Sriram
>                           Lilia Hannachi
> 	Filename        : draft-ietf-idr-deprecate-as-set-confed-set-01.txt
> 	Pages           : 7
> 	Date            : 2019-10-29
>
> Abstract:
>    BCP 172 (i.e., RFC 6472) recommends not using AS_SET and
>    AS_CONFED_SET in the Border Gateway Protocol.  This document advances
>    this recommendation to a standards requirement in BGP; it proscribes
>    the use of the AS_SET and AS_CONFED_SET types of path segments in the
>    AS_PATH.  This is done to simplify the design and implementation of
>    BGP and to make the semantics of the originator of a route clearer.
>    This will also simplify the design, implementation, and deployment of
>    various BGP security mechanisms.  This document (if approved) updates
>    RFC 4271 and RFC 5065 by eliminating AS_SET and AS_CONFED_SET types,
>    and obsoletes RFC 6472.
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/ 
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-idr-deprecate-as-set-confed-set-01 
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-deprecate-as-set-confed-set-01  
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-deprecate-as-set-confed-set-01  
>
> _______________________________________________
> Idr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/idr

_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr
pEpkey.asc (application/pgp-keys, 1.7 KB)