Flexible algorithm aware border gateway protocol (BGP) prefix segment routing identifiers (SIDs)

Patent metadata

Field	Value
Publication number	US-11438259-B2
Application number	US-202016794190-A
Country	US
Kind code	B2
Filing date	Feb 18, 2020
Priority date	Feb 18, 2020
Publication date	Sep 6, 2022
Grant date	Sep 6, 2022

Abstract

Support is provided for flexible algorithms, used by the border gateway protocol (BGP) route selection process, in the context of segment routing (SR) Prefix segment identifiers (SIDS) advertised using BGP.

First claim

What is claimed is:

1. A computer-implemented method comprising:
a) receiving, by a border gateway protocol (BGP) peer node, a segment routing (SR) prefix segment identifier (SID) associated with a prefix;
b) receiving, by the BGP peer node, a flexible algorithm definition (FAD);
c) determining, by the BGP peer node and using the FAD received, a next hop in a route towards a destination identified by the prefix;
d) allocating a local label for the prefix;
e) associating the local label with the determined next hop for the prefix; and
f) storing, in a forwarding information base (FIB) of the BGP peer node, the next hop determined, wherein the act of storing, in a forwarding information base (FIB) of the BGP peer node, the next hop determined includes associating with the next hop, in the FIB, (1) the prefix and (2) the local label allocated.

2. The computer-implemented method of claim 1 wherein both the SR prefix SID and the prefix are carried as network layer reachability information (NLRI) of a BGP update message.

3. The computer-implemented method of claim 2 wherein the border gateway protocol (BGP) peer node receives the FAD as a part of the BGP NLRI carrying the SR prefix SID and the prefix.

4. The computer-implemented method of claim 3 wherein the BGP SR prefix SID is encoded in a type length value (TLV) of the NLRI, and wherein the FAD is encoded as a sub-TLV of the SR prefix SID TLV.

5. The computer-implemented method of claim 1 , further comprising:
g) determining, by the BGP peer node, whether or not it has a feasible path to the node identified by the prefix; and
h) responsive to a determination that the BGP peer node has a feasible route to the node identified by the prefix carried in the SR prefix SID,
propagating reachability information for the prefix to an upstream BGP peer, and

otherwise, responsive to a determination that the BGP node does not have a feasible route to the node identified by the prefix,
not propagating reachability information for the prefix to the upstream BGP peer.

6. The computer-implemented method of claim 1 wherein the BGP peer node receives the FAD and a FAD identifier in a BGP link state (LS) node network layer reachability information (NLRI) field of a BGP update message, and wherein SR prefix SID includes the FAD identifier, the computer-implemented method further comprising:
g) storing, by the BGP peer node, the FAD and the FAD identifier in its link state database; and
h) responsive to receiving the SR prefix SID, finding the FAD stored in its link state database using the FAD identifier included in the SR prefix SID.

7. The computer-implemented method of claim 6 wherein the SR prefix SID is encoded in a type length value (TLV) of a BGP network layer reachability information (NLRI) field of a BGP update message.

8. The computer-implemented method of claim 6 wherein the FAD identifier has a value between 0 and 255.

9. The computer-implemented method of claim 1 wherein BGP is used to select feasible path(s) towards a peer node of a data center.

10. The computer-implemented method of claim 1 wherein the BGP peer node does not run an interior gateway protocol (IGP).

11. The computer-implemented method of claim 1 wherein the FAD includes at least one path computation constraint.

12. The computer-implemented method of claim 1 wherein the BGP peer node receives at least two FADs, and wherein the BGP peer node determines at least two different paths to the prefix carried in the SR prefix SID using the at least two FADs.

13. The computer-implemented method of claim 1 wherein the node identified by the prefix is a provider edge device (PE) for accessing a transport network.

14. A non-transitory computer-readable medium storing processor executable instructions which, when executed by at least one processor, cause the at least one processor to perform a method comprising:
a) receiving, by a border gateway protocol (BGP) peer node, a segment routing (SR) prefix segment identifier (SID) associated with a prefix;
b) receiving, by the BGP peer node, a flexible algorithm definition (FAD);
c) determining, by the BGP peer node and using the FAD received, a next hop in a route towards a destination identified by the prefix;
d) allocating a local label for the prefix;
e) associating the local label with the determined next hop for the prefix; and
f) storing, in a forwarding information base (FIB) of the BGP peer node, the next hop determined, wherein the act of storing, in a forwarding information base (FIB) of the BGP peer node, the next hop determined includes associating with the next hop, in the FIB, (1) the prefix and (2) the local label allocated.

15. The non-transitory computer-readable medium of claim 14 wherein both the SR prefix SID and the prefix are carried as network layer reachability information (NLRI) of a BGP update message.

16. The non-transitory computer-readable medium of claim 14 wherein the BGP peer node receives the FAD and a FAD identifier in a BGP link state (LS) node network layer reachability information (NLRI) field of a BGP update message, and wherein SR prefix SID includes the FAD identifier, the method further comprising:
g) storing, by the BGP peer node, the FAD and the FAD identifier in its link state database; and
h) responsive to receiving the SR prefix SID, finding the FAD stored in its link state database using the FAD identifier included in the SR prefix SID.

17. A border gateway protocol (BGP) peer node comprising:
a) at least one processor;
b) a storage device storing processor executable instructions which, when executed by the at least one processor, cause the at least one processor to perform a method comprising
1) receiving, by a border gateway protocol (BGP) peer node, a segment routing (SR) prefix segment identifier (SID) associated with a prefix,
2) receiving, by the BGP peer node, a flexible algorithm definition (FAD),
3) determining, by the BGP peer node and using the FAD received, a next hop in a route towards a destination identified by the prefix,
4) allocating a local label for the prefix,
5) associating the local label with the determined next hop for the prefix, and
6) storing, in a forwarding information base (FIB) of the BGP peer node, the next hop determined, wherein the act of storing, in a forwarding information base (FIB) of the BGP peer node, the next hop determined includes associating with the next hop, in the FIB, (1) the prefix and (2) the local label allocated.

18. The border gateway protocol (BGP) peer node of claim 17 wherein both the SR prefix SID and the prefix are carried as network layer reachability information (NLRI) of a BGP update message.

19. The border gateway protocol (BGP) peer node of claim 17 wherein the BGP peer node receives the FAD and a FAD identifier in a BGP link state (LS) node network layer reachability information (NLRI) field of a BGP update message, and wherein SR prefix SID includes the FAD identifier, the method further comprising
7) storing, by the BGP peer node, the FAD and the FAD identifier in its link state database, and
8) responsive to receiving the SR prefix SID, finding the FAD stored in its link state database using the FAD identifier included in the SR prefix SID.

Assignees

• Juniper Networks Inc

Inventors

• Torvi Raveendra
• Saad Tarek
• Barth Jonathan C
• Drake John E
• Beeram Vishnu Pavan

Classifications

• H04L45/50

  using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title

• H04L45/04 Primary

  Interdomain routing, e.g. hierarchical routing · CPC title

• H04L45/34 Primary

  Source routing · CPC title

• H04L45/566

  Routing instructions carried by the data packet, e.g. active networks · CPC title