BGP-LS Extensions for Inter-AS TE using EPE based mechanisms
draft-hegde-idr-bgp-ls-epe-inter-as-02

Document Type Active Internet-Draft (individual)
Last updated 2019-11-02
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda spring at IETF-106
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
SPRING                                                          S. Hegde
Internet-Draft                                                 S. Sangli
Intended status: Standards Track                           M. Srivastava
Expires: May 4, 2020                               Juniper Networks Inc.
                                                                   X. Xu
                                                            Alibaba Inc.
                                                        November 1, 2019

      BGP-LS Extensions for Inter-AS TE using EPE based mechanisms
                 draft-hegde-idr-bgp-ls-epe-inter-as-02

Abstract

   In certain network deployments, a single operator has multiple
   Autonomous Systems(AS) to facilitate ease of management.  A multiple
   AS network design could also be a result of network mergers and
   acquisitions.  In such scenarios, a centralized Inter-domain TE
   approach could provide most optimal allocation of resources and the
   most controlled path placement.  BGP-LS-EPE
   [I-D.ietf-idr-bgpls-segment-routing-epe] describes an extension to
   BGP Link State (BGP-LS) for the advertisement of BGP Peering Segments
   along with their BGP peering node and inter-AS link information, so
   that efficient BGP Egress Peer Engineering (EPE) policies and
   strategies can be computed based on Segment Routing.  This document
   describes extensions to the BGP-LS EPE to enable it to be used for
   inter-AS Traffic-Engineering (TE) purposes.

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 RFC 2119 [RFC2119].

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."

Hegde, et al.              Expires May 4, 2020                  [Page 1]
Internet-Draft BGP-LS extensions for Inter-AS TE using EPE November 2019

   This Internet-Draft will expire on May 4, 2020.

Copyright Notice

   Copyright (c) 2019 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Reference Topology  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Fast Reroute Label  . . . . . . . . . . . . . . . . . . . . .   4
   4.  TE Link attributes of PeerNode SID  . . . . . . . . . . . . .   5
   5.  TE Link attributes of PeerAdj SID . . . . . . . . . . . . . .   5
   6.  Link address TLV  . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Example Advertisements  . . . . . . . . . . . . . . . . . . .   7
   8.  Backward Compatibility  . . . . . . . . . . . . . . . . . . .   9
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     12.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Segment Routing (SR) leverages source routing.  A node steers a
   packet through a controlled set of instructions, called segments, by
   prepending the packet with an SR header with segment identifiers
   (SID).  A SID can represent any instruction, topological or service-
   based.  SR segments allows to enforce a flow through any topological
   path or service function while maintaining per-flow state only at the
   ingress node of the SR domain.

   As there is no per-path state in the network, the bandwidth
   management for the paths is expected to be handled by a centralized
Show full document text