Scalable edge node protection using IPv6 segment routing extension header

Patent metadata

Field	Value
Publication number	US-9444677-B2
Application number	US-201414155409-A
Country	US
Kind code	B2
Filing date	Jan 15, 2014
Priority date	Oct 18, 2013
Publication date	Sep 13, 2016
Grant date	Sep 13, 2016

Abstract

In one embodiment, a method comprises selecting, by an ingress provider edge router, one of first or second provider edge routers as a primary router for reaching a destination via a core network, and selecting the other of the first or second provider edge routers as a backup router for reaching the destination via the core network; and inserting, into an IPv6 data packet destined for the destination, a primary label assigned by the primary router and a repair label assigned by backup router, and an IPv6 extension header specifying first and second segment identifiers associated with the respective first and second provider edge routers and a protected flag that enables fast rerouting of the IPv6 data packet to the backup router if the primary router is unavailable.

First claim

What is claimed is:

1. A method comprising:
generating, by a first provider edge router associated with a first segment identifier, a primary label identifying the first provider edge router as a primary egress router for reaching a destination, and a repair label identifying the first provider edge router as a backup egress router for reaching the destination if a second provider edge router associated with a second segment identifier is unavailable to reach the destination;
advertising in a core network, by the first provider edge router, the first segment identifier for reaching the first provider edge router in the core network; and
sending via the core network, by the first provider edge router, an advertisement specifying the primary and repair labels, enabling an ingress provider edge router to insert, into an IPv6 data packet, selected primary and repair labels from the first and second provider edge routers and a segment routing-typed IPv6 extension header specifying the first and second segment identifiers and a protected flag, for fast rerouting by a core router in the core network to the destination via one of the first or second provider edge router if the other is unavailable, wherein the first and second segment identifiers enable segment routing of the IPv6 data packet by the ingress provider edge router and the core router in the core network without hop-by-hop signaling.

2. The method of claim 1 , further comprising the first provider edge router allocating a first protected next-hop address associated with the first segment identifier for protected reachability to the destination, the advertising of the first segment identifier including sending a link state advertisement associating the first protected next-hop address with the first segment identifier.

3. The method of claim 1 , wherein the advertising of the first segment identifier and the advertisement further enables the ingress provider edge router to insert, into the IPv6 data packet, the corresponding repair label of the one provider edge router and the primary label for the other provider edge router.

4. The method of claim 1 , wherein the protected flag enables any core router in the core network to detect the corresponding segment identifier of the one provider edge router in the extension header for fast rerouting if the other provider edge router is unavailable.

5. The method of claim 1 , further comprising:
the first provider edge router receiving the IPv6 data packet from the ingress provider edge router via the core network;
the first provider edge router accessing one of the primary label or the repair label based on whether a rerouted flag in the IPv6 data packet has been set in the core network indicating fast rerouting has been performed; and
forwarding a data packet contained in the IPv6 data packet, without the primary repair labels or the IPv6 extension header, to the destination based on the accessed one label.

6. A method comprising:
selecting, by an ingress provider edge router, one of first or second provider edge routers as a primary router for reaching a destination via a core network, and selecting the other of the first or second provider edge routers as a backup router for reaching the destination via the core network; and
inserting, into an IPv6 data packet destined for the destination, a primary label assigned by the primary router and a repair label assigned by the backup router, and an IPv6 extension header specifying first and second segment identifiers associated with the respective first and second provider edge routers and a protected flag that enables fast rerouting, by a core router in the core network, of the IPv6 data packet to the backup router if the primary router is unavailable;
wherein the protected flag is associated with the corresponding segment identifier of the primary router, the inserting further including inserting a null rerouted flag that enables any router to specify that the IPv6 data packet is being rerouted to the backup router.

7. The method of claim 6 , wherein the inserting includes inserting a sequence of segment identifiers for reaching the primary router via the core network, the protected flag associated with the corresponding segment identifier of the primary router to identify the corresponding segment identifier of the backup router if the primary router is unavailable.

8. The method of claim 6 , wherein the protected flag enables any core router in the core network to detect the corresponding segment identifier of the backup router if the primary router is unavailable.

9. Logic encoded in one or more non-transitory tangible media for execution by a machine and when executed by the machine operable for:
generating, by a first provider edge router associated with a first segment identifier, a primary label identifying the first provider edge router as a primary egress router for reaching a destination, and a repair label identifying the first provider edge router as a backup egress router for reaching the destination if a second provider edge router associated with a second segment identifier is unavailable to reach the destination;
advertising in a core network, by the first provider edge router, the first segment identifier for reaching the first provider edge router in the core network; and
sending via the core network, by the first provider edge router, an advertisement specifying the primary and repair labels, enabling an ingress provider edge router to insert, into an IPv6 data packet, selected primary and repair labels from the first and second provider edge routers and a segment routing-typed IPv6 extension header specifying the first and second segment identifiers and a protected flag, for fast rerouting by a core router in the core network to the destination via one of the first or second provider edge router if the other is unavailable, wherein the first and second segment identifiers enable segment routing of the IPv6 data packet by the ingress provider edge router and the core router in the core network without hop-by-hop signaling.

10. The logic of claim 9 , further operable for the first provider edge router allocating a first protected next-hop address associated with the first segment identifier for protected reachability to the destination, the advertising of the first segment identifier including sending a link state advertisement associating the first protected next-hop address with the first segment identifier.

11. The logic of claim 9 , wherein the advertising of the first segment identifier and the advertisement further enables the ingress provider edge router to insert, into the IPv6 data packet, the corresponding repair label of the one provider edge router and the primary label for the other provider edge router.

12. The logic of claim 9 , wherein the protected flag enables any router in the core network to detect the corresponding segment identifier of the one provider edge router in the extension header for fast rerouting if the other provider edge router is unavailable.

13. The logic of claim 9 , further operable for:
the first provider edge router receiving the IPv6 data packet from the ingress provider edge router via the core network;
the first provider edge router accessing one of the primary label or the repair label based on whether a rerouted flag in the IPv6 data packet has been set in the core network indicating fast rerouting has been performed; and
forwarding a data packet contained in the IPv6 data packet, without the primary repair labels or the IPv6 extension header, to the destination based on the accessed one label.

14. Logic encoded in one or more no

Assignees

• Cisco Tech Inc

Inventors

• Kumar Nagendra
• Pignataro Carlos M
• Filsfils Clarence
• Francois Pierre Jean Rene

Classifications

• H04L45/22

  Alternate routing · CPC title

• H04L45/50

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

• H04L45/34

  Source routing · CPC title

• H04L41/0659

  by isolating or reconfiguring faulty entities · CPC title

• H04L41/0668 Primary

  by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure · CPC title