BGP trigger Segment Routing ODN

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-10-02
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
Network Working Group                                        Yuanchao Su
Internet-Draft                                               Cisco Systems, Inc.
Intended status: Standards Track                             October 1,2018 
Expires: January 3, 2019                                    

              BGP trigger Segment Routing ODN


   This document defines an extension to the BGP SR Policy NLRI
   (draft-ietf-idr-segment-routing-te-policy) in order to use BGP to trigger 
   Segment Routing ODN, without using PCEP.
   The goal is to consolidate the SR Policy provision(BGP-TE), collection(BGP-LS)
   and ODN-trigger protocol for device to be BGP only, thus remove the need
   for PCEP and reduce the network complexity and potential bugs cause by
   different protocol interactions.

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

   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 January 3, 2019.

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

1.  Introduction


1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  BGP trigger ODN Encoding


3.  BGP trigger ODN Operations


4.  Contributors

   Yuanchao Su (editor)
   Cisco Systems, Inc. 


5.  Acknowledgments

   The authors of this document would like to thank  for their comments and review of this document.

7.  Implementation Status

   Note to RFC Editor: Please remove this section prior to publication,
   as well as the reference to RFC 7942.

   This section records the status of known implementations of the
   protocol defined by this specification at the time of posting of this
   Internet-Draft, and is based on a proposal described in [RFC7942].
   The description of implementations in this section is intended to
   assist the IETF in its decision processes in progressing drafts to
   RFCs.  Please note that the listing of any individual implementation
   here does not imply endorsement by the IETF.  Furthermore, no effort
   has been spent to verify the information presented here that was
   supplied by IETF contributors.  This is not intended as, and must not
   be construed to be, a catalog of available implementations or their
   features.  Readers are advised to note that other implementations may

   According to [RFC7942], "this will allow reviewers and working groups
   to assign due consideration to documents that have the benefit of
   running code, which may serve as evidence of valuable experimentation
   and feedback that have made the implemented protocols more mature.
   It is up to the individual working groups to use this information as
   they see fit".

   When IANA-assigned values are available, implementations will be
   updated to use them.

8.  IANA Considerations


9.  Security Considerations


10.  References

10.1.  Normative References
              S. Previdi, Ed., C. Filsfils,D. Jain, Ed., P. Mattes,E. Rosen,
              S. Lin,"Advertising Segment Routing Policies in BGP",
              draft-ietf-idr-segment-routing-te-policy-04.txt(work in progress),

              Rosen, E., Patel, K., and G. Velde, "The BGP Tunnel
              Encapsulation Attribute", draft-ietf-idr-tunnel-encaps-09
              (work in progress), February 2018.
Show full document text