BGP segment routing optimization by packing multiple prefixes in an update
Systems and methods for border gateway protocol (BGP) Segment Routing (SR) (BGP-SR) update packing include negotiating with border gateway protocol (BGP) peers for packing BGP-Segment Routing (BGP-SR) updates, receiving a plurality of prefixes for a BGP-SR update message, encoding the plurality of prefixes with associated label information in network layer reachability information (NLRI) of the BGP-SR update message, and transmitting the BGP-SR update message to any of the BGP peers.
1 . A router comprising circuitry configured to:
negotiate with border gateway protocol (BGP) peers for packing BGP-Segment Routing (BGP-SR) updates,
receive a plurality of prefixes for a BGP-SR update message,
encode the plurality of prefixes with associated label information in network layer reachability information (NLRI) of the BGP-SR update message, wherein the associated label information in the NLRI is utilized to derive a Segment Identifier (SID) for a corresponding prefix of the plurality of prefixes, wherein the BGP-SR update message is a single message for all of the plurality of prefixes each of which has a different SID which is derived from a calculation using the associated label information in the NLRI, and
transmit the BGP-SR update message to any of the BGP peers,
wherein the SID is derived for the corresponding prefix by
determining a label index as a label from the associated label information for the corresponding prefix subtracted by a local or peer segment routing global block (SRGB) start, and
determining the SID as the local SRGB start plus the label index,
wherein the circuitry is further configured to encode in a peer SRGB range sub-TLV attribute of a BGP Prefix-SID TLV of the BGP-SR update message, a peer SRGB start label explicitly identifying a peer SRGB range shared uniformly across multiple BGP peers, wherein the peer SRGB start label is distinct from any locally allocated SRGB start labels or ranges and from any flexible algorithm definitions or identifiers and is explicitly used by receiving BGP peers to derive label indexes for Segment Identifiers.
2 . The router of claim 1 , wherein the plurality of prefixes all share same attributes.
3 . The router of claim 1 , wherein the BGP peers all include a same segment routing global block (SRGB).
4 . The router of claim 1 , wherein any of the BGP peers include a different segment routing global block (SRGB), and wherein the circuitry is further configured to
encode the SRGB of a node performing the transmitting in an attribute.
5 . The router of claim 1 , wherein the circuitry is further configured to
responsive to any BGP peers failing to support the packing BGP-SR updates, encode each prefix in a separate BGP-SR update message.
6 . The router of claim 1 , wherein the circuitry is further configured to
receive a second BGP-SR update message from any of the BGP peers and determine an incoming label mapping (ILM) table based thereon.
7 . The router of claim 1 , wherein the associated label information includes the label for a corresponding prefix.
8 . The router of claim 1 , wherein the BGP-SR update message excludes a Label Index type-length-value (TLV).
9 . The router of claim 1 , wherein the plurality of prefixes are any of Internet Protocol version 4 (IPv4) and IP version 6 (IPv6) addresses.
10 . A method comprising steps of:
negotiating with border gateway protocol (BGP) peers for packing BGP-Segment Routing (BGP-SR) updates;
receiving a plurality of prefixes for a BGP-SR update message;
encode the plurality of prefixes with associated label information in network layer reachability information (NLRI) of the BGP-SR update message, wherein the associated label information in the NLRI is utilized to derive a Segment Identifier (SID) for a corresponding prefix of the plurality of prefixes, wherein the BGP-SR update message is a single message for all of the plurality of prefixes each of which has a different SID which is derived from a calculation using the associated label information in the NLRI, and
transmitting the BGP-SR update message to any of the BGP peers,
wherein the SID is derived for the corresponding prefix by
determining a label index as a label from the associated label information for the corresponding prefix subtracted by a local or peer segment routing global block (SRGB) start, and
determining the SID as the local SRGB start plus the label index,
wherein the steps further include encoding, in a peer SRGB range sub-TLV attribute of a BGP Prefix-SID TLV of the BGP-SR update message, a peer SRGB start label explicitly identifying a peer SRGB range shared uniformly across multiple BGP peers wherein the peer SRGB start label is distinct from any locally allocated SRGB start labels or ranges and from any flexible algorithm definitions or identifiers, and is explicitly used by receiving BGP peers to derive label indexes for Segment Identifiers.
11 . The method of claim 10 , wherein the plurality of prefixes all share same attributes.
12 . The method of claim 10 , wherein the BGP peers all include a same segment routing global block (SRGB).
13 . The method of claim 10 , wherein any of the BGP peers include a different segment routing global block (SRGB), and wherein the steps include
encoding the SRGB of a node performing the transmitting in an attribute.
14 . The method of claim 10 , wherein the steps include
responsive to any BGP peers failing to support the packing BGP-SR updates, encoding each prefix in a separate BGP-SR update message.
15 . The method of claim 10 , wherein the steps include
receiving a second BGP-SR update message from any of the BGP peers and determining an incoming label mapping (ILM) table based thereon.
16 . The method of claim 10 , wherein the associated label information includes the label for a corresponding prefix.
17 . The method of claim 10 , wherein the BGP-SR update message excludes a Label Index type-length-value (TLV).
18 . The method of claim 10 , wherein the plurality of prefixes are any of Internet Protocol version 4 (IPv4) and IP version 6 (IPv6) addresses.
19 . A non-transitory computer-readable medium comprising instructions that, when executed, cause a network element to perform steps of:
negotiating with border gateway protocol (BGP) peers for packing BGP-Segment Routing (BGP-SR) updates;
receiving a plurality of prefixes for a BGP-SR update message;
encode the plurality of prefixes with associated label information in network layer reachability information (NLRI) of the BGP-SR update message, wherein the associated label information in the NLRI is utilized to derive a Segment Identifier (SID) for a corresponding prefix of the plurality of prefixes, wherein the BGP-SR update message is a single message for all of the plurality of prefixes each of which has a different SID which is derived from a calculation using the associated label information in the NLRI, and
transmitting the BGP-SR update message to any of the BGP peers,
wherein the SID is derived for the corresponding prefix by
determining a label index as a label from the associated label information for the corresponding prefix subtracted by a local or peer segment routing global block (SRGB) start, and
determining the SID as the local SRGB start plus the label index,
wherein the steps further include encoding, in a peer SRGB range sub-TLV attribute of a BGP Prefix-SID TLV of the BGP-SR update message, a peer SRGB start label explicitly identifying a peer SRGB range shared uniformly across multiple BGP peers, wherein the peer SRGB start label is distinct from any locally allocated SRGB start labels or ranges and from any flexible algorithm definitions or identifiers, and is explicitly used by receiving BGP peers to derive label indexes for Segment Identifiers.
20 . The non-transitory computer-readable medium of claim 19 , wherein the plurality of prefixes all share same attributes.