Re: [Idr] WG adoption call for draft-xu-idr-performance-routing-01

Hello Xu,

Few questions before I make my mind on "support" or "no support" :) ...

* How often intermediate nodes are supposed to re-test the latency and
readvertised the new value ?

* What is the permitted hysteresis when change will not trigger the
readvertisement ?

* How do you account for transit delay via network nodes which set
next hop self (example EBGP peers) ?

* In the case of SR being used which allows effectively per prefix
path selection how does test to per next hop helps in anything ?

* Do you intend to allow AIGP type 1 and new type to co-exist ?

- - -

How about talking or at least discussing in this draft a completely
different approach of just marking by regular community ingress to the
domain (or set of domains) an originator address which would not
change across BGP hops?

That would enable quick testing of end to end real path delay by those
BGP speakers which are interested in doing so. The advantages are
flexibility to enable it only for say small subset of very important
prefixes on a perhaps few BGP speakers and no requirement for any new
capability or BGP upgrades domain/set of domains wide.

Last but not least your proposal may perhaps work when you have BGP
control plane present on actual data plane devices. Now think how your
proposal brings any value when your control plane is 100% decoupled
from data plane devices and operates on few x86 blades not co-located
with data plane ?  Or worse how your draft is useful when BGP is moved
to the "cloud".

Cheers,
R.

On Thu, Dec 25, 2014 at 2:58 AM, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> Support as a co-author.
>
>
>
> Best regards,
>
> Xiaohu
>
>
>
> From: Susan Hares [mailto:shares@ndzh.com]
> Sent: Tuesday, December 23, 2014 10:37 PM
> To: idr wg
> Cc: Xuxiaohu; John G. Scudder
> Subject: WG adoption call for draft-xu-idr-performance-routing-01
>
>
>
> This is to begin a 2 Week WG adoption call for
> draft-xu-idr-performance-routing-01  (12/23/2014 to 01/6/2014).  The draft
> can be accessed at:
>
>
>
>  http://datatracker.ietf.org/doc/draft-xu-idr-performance-routing/.
>
>
>
> In your response, please discuss the pros/cons of this approach and indicate
> “support” or “no support”.
>
>
>
> Thank you,
>
>
>
> Sue Hares
>
>
>
>
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>