RTGWG J. Tantsura
Internet-Draft Individual
Intended status: Informational D. Afanasiev
Expires: May 3, 2018 YANDEX
K. Patel
P. Lapukhov
P. Przygienda
R. White
Y. Qu
J. Uttaro
October 30, 2017

Requirements for the DataCenter Routing


This document describes list of functional requirments towards a Routing Protocol for Data Center Networks.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on May 3, 2018.

Copyright Notice

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

1. Introduction

It is common to host and build a network of more than tens of thousands of end points inside a data center. Data Center Networks of such size have unique set of requirements with emphasis on scale, convergence, network stability and opertional simplicity. Existing or new set of protocols and routing infrastructure needs to be augmented to support higher scale, faster convergence with increased optional simplicity in order to address the requirements of these networks.

This document describes list of functional requirements that are required towards addressing scale, convergence and operational maintainance of such scaled networks. The requirements described in this document can be used to augment existing solutions or used to design a new set of solutions.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] only when they appear in all upper case. They may also appear in lower or mixed case as English words, without any normative meaning.

3. Recommended Reading

This document assumes knowledge of existing data center networks and data center network topologies [CLOS],[RFC7938]. This document also assumes knowledge of data center routing protocols like BGP [RFC4271], OSPF [RFC2328] and BFD [RFC5880] as well as data center layer 2 link layer protocols like LLDP [RFC4957].

4. Goals and Requirements

Following are general requirements for the Data Center Network Fabric and its Routing Protocols:

5. For further study

Following topics have been identified to be studied at a later time:

6. Network Topologies

7. IANA Considerations

8. Security Considerations

This document describes list of functional requirements towards a routing protocol for Data Center Networks. It does not raise any security concerns or issues in addition to ones common to a routing protocol for Data Center Networks.

9. Acknowledgements

10. Change Log

Initial Version:
October 31 2017

11. References

11.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.

11.2. Informative References

[CLOS] , "A Study of Non-Blocking Switching Networks", The Bell System Technical Journal, Vol. 32(2), DOI 10.1002/j.1538-7305.1953.tb01433.x, March 1953.
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/RFC2328, April 1998.
[RFC4271] Rekhter, Y., Li, T. and S. Hares, "A Border Gateway Protocol 4 (BGP-4)", RFC 4271, DOI 10.17487/RFC4271, January 2006.
[RFC4957] Krishnan, S., Montavont, N., Njedjou, E., Veerepalli, S. and A. Yegin, "Link-Layer Event Notifications for Detecting Network Attachments", RFC 4957, DOI 10.17487/RFC4957, August 2007.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010.
[RFC5882] Katz, D. and D. Ward, "Generic Application of Bidirectional Forwarding Detection (BFD)", RFC 5882, DOI 10.17487/RFC5882, June 2010.
[RFC7938] Lapukhov, P., Premji, A. and J. Mitchell, "Use of BGP for Routing in Large-Scale Data Centers", RFC 7938, DOI 10.17487/RFC7938, August 2016.

Authors' Addresses

Jeff Tantsura Individual USA EMail: jefftant.ietf@gmail.com
Dmitry Afanasiev YANDEX RU EMail: dmitry.afanasiev@gmail.com
Keyur Patel Arccus San Jose, USA EMail: keyur@arrcus.com
Petr Lapukhov Facebook USA EMail: petr@fb.com
Tony Przygienda Juniper 1137 Innovation Way Sunnyvale, CA, USA EMail: prz@juniper.net
Russ White LinkedIn USA EMail: russ@riw.us
Yingzhen Qu Huawei Santa Clara, USA EMail: yingzhen.ietf@gmail.com
Jim Uttaro ATT USA EMail: juttaro@ieee.org