Re: [Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt

Xiaohu,

few comments:

RFC7311 is very specific about containing routes with AIGP attribute within AIGP administrative domain, while not well defined in RFC7311, perhaps worth saying something?
The value field of the AIGP TLV in RFC7311 is 8 octets long - draft defines 4 octet value, I assume you are following RFC8570 and RFC7471 encoding?
Rather that making AIGP TLV and NETWORK_LATENCY TLV  mutually exclusive, perhaps defining how they interact, if both are present would be a better choice?
Capability Advertisement - 3rd para doesn’t parse, be clear if it applies to labelled routes only (RFC7311 is vague here - "tunneling of some sort”)
Manipulation of the Unidirectional Link delay sub-TLV in IGP’s could natively be done by using  Unidirectional Link Delay TLV in RFC8571.

3107 has been obsoleted by 8277

Cheers,
Jeff
On Oct 15, 2019, 11:57 AM +0200, 徐小虎(义先) <xiaohu.xxh@alibaba-inc.com>, wrote:
>
> Hi all,
>
> I just recently realized that the performance routing mechanism as described in this draft could facilitate the deployment of segment routing across multiple ASes of an administrative entity where low-latency SR paths across ASes are needed for carrying latency-sensitive and high-priority traffic. In this way, there is no need to resort to centralized TE controllers for calculating low-latency paths across ASes.
>
> Any comments and suggestions are welcome.
>
> Best regards,
> Xiaohu
>
>
>
>
>
> > ------------------------------------------------------------------
> > From:internet-drafts <internet-drafts@ietf.org>
> > Send Time:2019年10月14日(星期一) 13:09
> > To:i-d-announce <i-d-announce@ietf.org>
> > Cc:idr <idr@ietf.org>
> > Subject:[Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt
> >
> >
> > 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           : Performance-based BGP Routing Mechanism
> >         Authors         : Xiaohu Xu
> >                           Shraddha Hegde
> >                           Ketan Talaulikar
> >                           Mohamed Boucadair
> >                           Christian Jacquenet
> >  Filename        : draft-ietf-idr-performance-routing-02.txt
> >  Pages           : 10
> >  Date            : 2019-10-13
> >
> > Abstract:
> >    The current BGP specification doesn't use network performance metrics
> >    (e.g., network latency) in the route selection decision process.
> >    This document describes a performance-based BGP routing mechanism in
> >    which network latency metric is taken as one of the route selection
> >    criteria.  This routing mechanism is useful for those server
> >    providers with global reach to deliver low-latency network
> >    connectivity services to their customers.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-idr-performance-routing/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-idr-performance-routing-02
> > https://datatracker.ietf.org/doc/html/draft-ietf-idr-performance-routing-02
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-performance-routing-02
> >
> >
> > 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
> > Idr@ietf.org
> > https://www.ietf.org/mailman/listinfo/idr
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr