Re: [Idr] I-D Action: draft-ietf-idr-as-migration-04.txt

["Susan Hares" <[e-mail]>]

George: 

Let me review the document and query Alvaro to make sure it addresses his concerns.  

On re-doing WG LC, we can do this in parallel with the other reviews I'll need to redo (security directorate, routing directorate, ops-directorate and gen-art). I'll start both sequences at the same time once I've heard from Alvaro.  

Sue 

-----Original Message-----
From: George, Wes [mailto:[e-mail]] 
Sent: Thursday, April 09, 2015 10:13 AM
To: [e-mail]; Alvaro Retana (aretana); Alia Atlas; Susan Hares
Cc: Adrian Farrel
Subject: Re: [Idr] I-D Action: draft-ietf-idr-as-migration-04.txt

Shane and I believe that this revision addresses the majority of concerns raised during IESG evaluation, including Alvaro's review.

I don't know if this has to go back through WGLC or if it can just be put back on IESG schedule, as a good bit of the text was changed to address the concerns about this being too vendor-specific, including some of the normative language, so I'll leave that to the chairs and ADs to decide.

Thanks,

Wes



On 4/9/15, 10:02 AM, "[e-mail]" <[e-mail]>
wrote:

>
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
> This draft is a work item of the Inter-Domain Routing Working Group of 
>the IETF.
>
>        Title           : Autonomous System Migration Mechanisms and
>Their Effects on the BGP AS_PATH Attribute
>        Authors         : Wesley George
>                          Shane Amante
>       Filename        : draft-ietf-idr-as-migration-04.txt
>       Pages           : 16
>       Date            : 2015-04-09
>
>Abstract:
>   This draft discusses some commonly-used BGP mechanisms for ASN
>   migration that are not formally part of the BGP4 protocol
>   specification and may be vendor-specific in exact implementation.  It
>   is necessary to document these de facto standards to ensure that they
>   are properly supported in future BGP protocol work.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-idr-as-migration/
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-idr-as-migration-04
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-idr-as-migration-04
>
>
>Please note that it may take a couple of minutes from the time of 
>submission until the htmlized version and diff are available at 
>tools.ietf.org.
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>Idr mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/idr


This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.