Usage and Applicability of Link State Vector Routing in Data Centers
draft-keyupate-lsvr-applicability-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-03-05
Replaced by draft-ietf-lsvr-applicability
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
LSVR                                                            K. Patel
Internet-Draft                                              Arrcus, Inc.
Intended status: Informational                                 A. Lindem
Expires: September 6, 2018                                 Cisco Systems
                                                                S. Zandi
                                                                G. Dawra
                                                                Linkedin
                                                           March 5, 2018

  Usage and Applicability of Link State Vector Routing in Data Centers
                draft-keyupate-lsvr-applicability-00.txt

Abstract

   This document discusses the usage and applicability of Link State
   Vector Routing (LSVR) extensions in the CLOS architecture of Data
   Center Networks.  The document is intended to provide a simplified
   guide for the deployment of LSVR extensions.

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 http://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 September 6, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (http://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

Patel, et al.           Expires September 6, 2018               [Page 1]
Internet-Draft                                                March 2018

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Recommended Reading . . . . . . . . . . . . . . . . . . . . .   2
   4.  Common Deployment Scenario  . . . . . . . . . . . . . . . . .   3
   5.  Justification for BGP modifications . . . . . . . . . . . . .   3
   6.  LSVR Applicability to CLOS Networks . . . . . . . . . . . . .   4
     6.1.  Usage of LSVR SAFI  . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document complements [I-D.keyupate-lsvr-bgp-spf] by discussing
   the applicability of the technology in a simple and fairly common
   deployment scenario, which is described in Section 4.

   After describing the deployment scenario, Section 5 will describe the
   reasons for BGP modifications for such deployments.

   Once the control plane routing protocol requirements are described,
   Section 6 will cover the LSVR protocol enhancements to BGP to meet
   these requirements and their applicability to Data Center CLOS
   networks.

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].  This document also assumes
   knowledge of data center routing protocols like BGP [RFC4271], BGP-

Patel, et al.           Expires September 6, 2018               [Page 2]
Internet-Draft                                                March 2018

   SPF [I-D.keyupate-lsvr-bgp-spf], OSPF [RFC2328], as well as, data
   center OAM protocols like LLDP [RFC4957] and BFD [RFC5580].
Show full document text