Last Call: <draft-ietf-idr-bgp-prefix-sid-09.txt> (Segment Routing Prefix SID extensions for BGP) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document: - 'Segment Routing Prefix SID extensions for
BGP'
  <draft-ietf-idr-bgp-prefix-sid-09.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-01-26. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   Segment Routing (SR) architecture allows a node to steer a packet
   flow through any topological path and service chain by leveraging
   source routing.  The ingress node prepends an SR header to a packet
   containing a set of segment identifiers (SID).  Each SID represents a
   topological or a service-based instruction.  Per-flow state is
   maintained only on the ingress node of the SR domain.

   This document defines an optional, transitive BGP attribute for
   announcing BGP Prefix Segment Identifiers (BGP Prefix-SID)
   information.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-prefix-sid/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-prefix-sid/ballot/


No IPR declarations have been submitted directly on this I-D.







[Index of Archives]     [IETF]     [IETF Discussion]     [Linux Kernel]

  Powered by Linux