In addition, the performance routing paradigm could actually be deployed in the
EPE scenario as well where both capacity-aware TE capability and
performance-aware TE capability are desired. More specifically, since there are
two routing tables, one contains vanilla routes which are used for
capacity-aware routing purpose and the other contains performance routes which
are used for performance-aware routing purpose, which are manipulated by the
EPE controller via the BGP-LU and the performance routing SAFIs respectively,
traffic with different QoS class but designated for the same destination could
be forwarded to different ISP peers according to different routing tables.
In this way, it allows cloud providers to provide differentiated Internet
connectivity service to their tenants. For example, high-priority traffic
originated from gold tenants could be forwarded according to the performance
routing table while the remaining traffic would be forwarded according to the
vanilla routing table, as a result, the former is forwarded along a low-latency
path while the latter is forwarded along a high-latency path.
Best regards,
Xiaohu
------------------------------------------------------------------
From:徐小虎(义先) <[email protected]>
Send Time:2019年10月15日(星期二) 17:57
To:SPRING WG List <[email protected]>
Cc:idr <[email protected]>
Subject:Re: [Idr] I-D Action: draft-ietf-idr-performance-routing-02.txt
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 <[email protected]>
Send Time:2019年10月14日(星期一) 13:09
To:i-d-announce <[email protected]>
Cc:idr <[email protected]>
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
[email protected]
https://www.ietf.org/mailman/listinfo/idr_______________________________________________
spring mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/spring
