| < draft-xu-idr-neighbor-autodiscovery-07.txt | draft-xu-idr-neighbor-autodiscovery-08.txt > | |||
|---|---|---|---|---|
| skipping to change at page 1, line 16 ¶ | skipping to change at page 1, line 16 ¶ | |||
| Expires: November 16, 2018 Huawei | Expires: November 16, 2018 Huawei | |||
| J. Tantsura | J. Tantsura | |||
| Nuage Networks | Nuage Networks | |||
| N. Triantafillis | N. Triantafillis | |||
| K. Talaulikar | K. Talaulikar | |||
| Cisco | Cisco | |||
| May 15, 2018 | May 15, 2018 | |||
| BGP Neighbor Autodiscovery | BGP Neighbor Autodiscovery | |||
| draft-xu-idr-neighbor-autodiscovery-07 | draft-xu-idr-neighbor-autodiscovery-08 | |||
| Abstract | Abstract | |||
| BGP has been used as the underlay routing protocol in many hyper- | BGP has been used as the underlay routing protocol in many hyper- | |||
| scale data centers. This document proposes a BGP neighbor | scale data centers. This document proposes a BGP neighbor | |||
| autodiscovery mechanism that greatly simplifies BGP deployments. | autodiscovery mechanism that greatly simplifies BGP deployments. | |||
| This mechanism is very useful for those hyper-scale data centers | This mechanism is very useful for those hyper-scale data centers | |||
| where BGP is used as the underlay routing protocol. | where BGP is used as the underlay routing protocol. | |||
| Requirements Language | Requirements Language | |||
| skipping to change at page 2, line 28 ¶ | skipping to change at page 2, line 28 ¶ | |||
| described in the Simplified BSD License. | described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. BGP Hello Message Format . . . . . . . . . . . . . . . . . . 3 | 3. BGP Hello Message Format . . . . . . . . . . . . . . . . . . 3 | |||
| 4. Hello Message Procedure . . . . . . . . . . . . . . . . . . . 10 | 4. Hello Message Procedure . . . . . . . . . . . . . . . . . . . 10 | |||
| 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 | 5. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 | 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 | |||
| 7.1. BGP Hello Message . . . . . . . . . . . . . . . . . . . . 11 | 7.1. BGP Hello Message . . . . . . . . . . . . . . . . . . . . 12 | |||
| 7.2. TLVs of BGP Hello Message . . . . . . . . . . . . . . . . 12 | 7.2. TLVs of BGP Hello Message . . . . . . . . . . . . . . . . 12 | |||
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 | |||
| 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 | |||
| 9.2. Informative References . . . . . . . . . . . . . . . . . 13 | 9.2. Informative References . . . . . . . . . . . . . . . . . 13 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 | |||
| 1. Introduction | 1. Introduction | |||
| BGP has been used as the underlay routing protocol instead of IGP in | BGP has been used as the underlay routing protocol instead of IGP in | |||
| many hyper-scale data centers [RFC7938]. Furthermore, there is an | many hyper-scale data centers [RFC7938]. Furthermore, there is an | |||
| ongoing effort to leverage BGP link-state distribution mechanism to | ongoing effort to leverage BGP link-state distribution mechanism to | |||
| achieve BGP-SPF [I-D.keyupate-lsvr-bgp-spf]. However, BGP is not | achieve BGP-SPF [I-D.keyupate-lsvr-bgp-spf]. However, BGP is not | |||
| good as an IGP from the perspective of deployment automation and | good as an IGP from the perspective of deployment automation and | |||
| simplicity. For instance, the IP address and the Autonomous System | simplicity. For instance, the IP address and the Autonomous System | |||
| Number (ASN) of each and every BGP neighbor have to be manually | Number (ASN) of each and every BGP neighbor have to be manually | |||
| skipping to change at page 11, line 40 ¶ | skipping to change at page 11, line 40 ¶ | |||
| Email: jingtan.hc@alibaba-inc.com | Email: jingtan.hc@alibaba-inc.com | |||
| Guixin Bao | Guixin Bao | |||
| Alibaba Inc | Alibaba Inc | |||
| Email: guixin.bgx@alibaba-inc.com | Email: guixin.bgx@alibaba-inc.com | |||
| Jinghui Liu | Jinghui Liu | |||
| Ruijie Networks | Ruijie Networks | |||
| Email: liujh@ruijie.com.cn | Email: liujh@ruijie.com.cn | |||
| Zhichun Jiang | ||||
| Tecent | ||||
| Email: zcjiang@tencent.com | ||||
| 6. Acknowledgements | 6. Acknowledgements | |||
| The authors would like to thank Enke Chen for his valuable comments | The authors would like to thank Enke Chen for his valuable comments | |||
| and suggestions on this document. | and suggestions on this document. | |||
| 7. IANA Considerations | 7. IANA Considerations | |||
| 7.1. BGP Hello Message | 7.1. BGP Hello Message | |||
| This document requests IANA to allocate a new UDP port (179 is the | This document requests IANA to allocate a new UDP port (179 is the | |||
| End of changes. 4 change blocks. | ||||
| 4 lines changed or deleted | 8 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/ | ||||