| < draft-xu-idr-neighbor-autodiscovery-06.txt | draft-xu-idr-neighbor-autodiscovery-07.txt > | |||
|---|---|---|---|---|
| Network Working Group X. Xu | Network Working Group X. Xu | |||
| Internet-Draft Alibaba Inc | Internet-Draft Alibaba Inc | |||
| Intended status: Standards Track K. Bi | Intended status: Standards Track K. Bi | |||
| Expires: October 24, 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 | |||
| April 22, 2018 | May 15, 2018 | |||
| BGP Neighbor Autodiscovery | BGP Neighbor Autodiscovery | |||
| draft-xu-idr-neighbor-autodiscovery-06 | draft-xu-idr-neighbor-autodiscovery-07 | |||
| 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 1, line 47 ¶ | skipping to change at page 1, line 47 ¶ | |||
| 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 October 24, 2018. | This Internet-Draft will expire on November 16, 2018. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | |||
| skipping to change at page 2, line 32 ¶ | skipping to change at page 2, line 32 ¶ | |||
| 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 . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 7.1. BGP Hello Message . . . . . . . . . . . . . . . . . . . . 11 | 7.1. BGP Hello Message . . . . . . . . . . . . . . . . . . . . 11 | |||
| 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 . . . . . . . . . . . . . . . . . . . . . . . . . 12 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 9.1. Normative References . . . . . . . . . . . . . . . . . . 12 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 | |||
| 9.2. Informative References . . . . . . . . . . . . . . . . . 13 | 9.2. Informative References . . . . . . . . . . . . . . . . . 13 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 | |||
| 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 | |||
| skipping to change at page 11, line 28 ¶ | skipping to change at page 11, line 28 ¶ | |||
| 5. Contributors | 5. Contributors | |||
| Satya Mohanty | Satya Mohanty | |||
| Cisco | Cisco | |||
| Email: satyamoh@cisco.com | Email: satyamoh@cisco.com | |||
| Shunwan Zhuang | Shunwan Zhuang | |||
| Huawei | Huawei | |||
| Email: zhuangshunwan@huawei.com | Email: zhuangshunwan@huawei.com | |||
| Chao Huang | ||||
| Alibaba Inc | ||||
| Email: jingtan.hc@alibaba-inc.com | ||||
| Guixin Bao | ||||
| Alibaba Inc | ||||
| Email: guixin.bgx@alibaba-inc.com | ||||
| Jinghui Liu | ||||
| Ruijie Networks | ||||
| Email: liujh@ruijie.com.cn | ||||
| 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. 6 change blocks. | ||||
| 6 lines changed or deleted | 18 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/ | ||||