| draft-ietf-idr-performance-routing-02.txt | draft-ietf-idr-performance-routing-03.txt | |||
|---|---|---|---|---|
| Network Working Group X. Xu | Network Working Group X. Xu | |||
| Internet-Draft Alibaba, Inc | Internet-Draft Alibaba, Inc | |||
| Intended status: Standards Track S. Hegde | Intended status: Standards Track S. Hegde | |||
| Expires: April 12, 2020 Juniper | Expires: June 24, 2021 Juniper | |||
| K. Talaulikar | K. Talaulikar | |||
| Cisco | Cisco | |||
| M. Boucadair | M. Boucadair | |||
| C. Jacquenet | C. Jacquenet | |||
| France Telecom | France Telecom | |||
| October 10, 2019 | December 21, 2020 | |||
| Performance-based BGP Routing Mechanism | Performance-based BGP Routing Mechanism | |||
| draft-ietf-idr-performance-routing-02 | draft-ietf-idr-performance-routing-03 | |||
| Abstract | Abstract | |||
| The current BGP specification doesn't use network performance metrics | The current BGP specification doesn't use network performance metrics | |||
| (e.g., network latency) in the route selection decision process. | (e.g., network latency) in the route selection decision process. | |||
| This document describes a performance-based BGP routing mechanism in | This document describes a performance-based BGP routing mechanism in | |||
| which network latency metric is taken as one of the route selection | which network latency metric is taken as one of the route selection | |||
| criteria. This routing mechanism is useful for those server | criteria. This routing mechanism is useful for those server | |||
| providers with global reach to deliver low-latency network | providers with global reach to deliver low-latency network | |||
| connectivity services to their customers. | connectivity services to their customers. | |||
| skipping to change at page 1, line 48 ¶ | skipping to change at page 1, line 48 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on April 12, 2020. | This Internet-Draft will expire on June 24, 2021. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2020 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 9, line 24 ¶ | skipping to change at page 9, line 24 ¶ | |||
| [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement | [RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement | |||
| with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February | with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February | |||
| 2009, <https://www.rfc-editor.org/info/rfc5492>. | 2009, <https://www.rfc-editor.org/info/rfc5492>. | |||
| 11.2. Informative References | 11.2. Informative References | |||
| [I-D.ietf-idr-bgp-optimal-route-reflection] | [I-D.ietf-idr-bgp-optimal-route-reflection] | |||
| Raszuk, R., Cassar, C., Aman, E., Decraene, B., and K. | Raszuk, R., Cassar, C., Aman, E., Decraene, B., and K. | |||
| Wang, "BGP Optimal Route Reflection (BGP-ORR)", draft- | Wang, "BGP Optimal Route Reflection (BGP-ORR)", draft- | |||
| ietf-idr-bgp-optimal-route-reflection-19 (work in | ietf-idr-bgp-optimal-route-reflection-21 (work in | |||
| progress), July 2019. | progress), June 2020. | |||
| [I-D.ietf-spring-segment-routing-policy] | [I-D.ietf-spring-segment-routing-policy] | |||
| Filsfils, C., Sivabalan, S., daniel.voyer@bell.ca, d., | Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and | |||
| bogdanov@google.com, b., and P. Mattes, "Segment Routing | P. Mattes, "Segment Routing Policy Architecture", draft- | |||
| Policy Architecture", draft-ietf-spring-segment-routing- | ietf-spring-segment-routing-policy-09 (work in progress), | |||
| policy-03 (work in progress), May 2019. | November 2020. | |||
| [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way | [RFC2679] Almes, G., Kalidindi, S., and M. Zekauskas, "A One-way | |||
| Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679, | Delay Metric for IPPM", RFC 2679, DOI 10.17487/RFC2679, | |||
| September 1999, <https://www.rfc-editor.org/info/rfc2679>. | September 1999, <https://www.rfc-editor.org/info/rfc2679>. | |||
| [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering | [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering | |||
| (TE) Extensions to OSPF Version 2", RFC 3630, | (TE) Extensions to OSPF Version 2", RFC 3630, | |||
| DOI 10.17487/RFC3630, September 2003, | DOI 10.17487/RFC3630, September 2003, | |||
| <https://www.rfc-editor.org/info/rfc3630>. | <https://www.rfc-editor.org/info/rfc3630>. | |||
| skipping to change at page 10, line 25 ¶ | skipping to change at page 10, line 25 ¶ | |||
| [RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder, | [RFC7911] Walton, D., Retana, A., Chen, E., and J. Scudder, | |||
| "Advertisement of Multiple Paths in BGP", RFC 7911, | "Advertisement of Multiple Paths in BGP", RFC 7911, | |||
| DOI 10.17487/RFC7911, July 2016, | DOI 10.17487/RFC7911, July 2016, | |||
| <https://www.rfc-editor.org/info/rfc7911>. | <https://www.rfc-editor.org/info/rfc7911>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Xiaohu Xu | Xiaohu Xu | |||
| Alibaba, Inc | Alibaba, Inc | |||
| Email: xiaohu.xxh@alibaba-inc.com | Email: 13910161692@qq.com | |||
| Shraddha Hegde | Shraddha Hegde | |||
| Juniper | Juniper | |||
| Email: shraddha@juniper.net | Email: shraddha@juniper.net | |||
| Ketan Talaulikar | Ketan Talaulikar | |||
| Cisco | Cisco | |||
| Email: ketant@cisco.com | Email: ketant@cisco.com | |||
| End of changes. 8 change blocks. | ||||
| 12 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||