Upstream label assignment for the resource reservation protocol with traffic engineering

• US 8,767,741 B1
• Filed: 12/17/2010
• Issued: 07/01/2014
• Est. Priority Date: 06/30/2006
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Aggarwal, Rahul
• Primary Examiner(s): SMARTH, GERALD A
• Application Number:
  US12/972,197
• Time in Patent Office: 1,292 Days
• Field of Search: 370/390, 370/395.3
• US Class Current: 370/395.3
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/50 using label swapping, e.g. multi-protocol label switch [MPLS]
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/724 at intermediate nodes, e.g. resource reservation protocol [RSVP]
• CPC Class Codes: H04L 47/825 Involving tunnels, e.g. MPLS

Abstract

The invention is directed toward techniques for Multi-Protocol Label Switching (MPLS) upstream label assignment for the Resource Reservation Protocol with Traffic Engineering (RSVP-TE). The techniques include extensions to the RSVP-TE that enable distribution of upstream assigned labels in Path messages from an upstream router to two or more downstream routers of tunnel established over a network. The tunnel may comprise a RSVP-TE P2MP Label Switched Path (LSP) or an Internet Protocol (IP) multicast tunnel. The techniques also include extensions to the RSVP-TE that enable a router to advertise upstream label assignment capability to neighboring routers in the network. The MPLS upstream label assignment using RSVP-TE described herein enables a branch router to avoid traffic replication on a Local Area Network (LAN) for RSVP-TE P2MP LSPs.

Claims

1. A method of establishing a point-to-multipoint (P2MP) tunnel across a network between an upstream router and two or more downstream routers using a label distribution protocol, the method comprising:

outputting, to the upstream router, advertisements that include upstream label assignment capability indications from one or more of the downstream routers of the tunnel, wherein the upstream assignment capability indications from the downstream routers indicate whether the respective downstream router is capable of supporting upstream assigned labels, and wherein the advertisements from the downstream routers that are capable of supporting upstream assigned labels comprise label distribution protocol Hello messages including a Capability object with a set flag;

receiving a message having a label object with the at least one of the downstream routers, wherein the message requests a P2MP tunnel and the label object specifies an upstream assigned label allocated to the downstream routers of the P2MP tunnel that output the advertisements carrying the upstream label assignment capability indications;

outputting, from the at least one of the downstream routers to the upstream router, a message to establish the P2MP tunnel without including any downstream assigned labels when the downstream router supports the type of label object included in the message and is able to process the upstream assigned label;

outputting, from the at least one of the downstream routers to the upstream router, a message specifying an error when the downstream router does not support the type of label object included in the message from the upstream router requesting the P2MP tunnel.

2. The method of claim 1, wherein the advertisements comprise Resource Reservation Protocol with Traffic Engineering (RSVP-TE) Hello messages including a Capability object with a set U flag.

3. The method of claim 1, further comprising receiving a tunnel identifier with the at least one of the downstream routers that identifies the tunnel as carrying upstream assigned labels from the upstream router.

4. The method of claim 1, further comprising receiving, with the at least one of the downstream routers, a packet on the tunnel from the upstream router to the capable downstream routers with the upstream assigned label.

5. The method of claim 1, wherein the label distribution protocol comprises the Resource Reservation Protocol with Traffic Engineering (RSVP-TE).

6. A method of establishing a point-to-multipoint (P2MP) tunnel across a network between an upstream router and two or more downstream routers using a label distribution protocol, the method comprising:

outputting, to the upstream router, advertisements that include upstream label assignment capability indications from one or more of the downstream routers of the tunnel, wherein the upstream assignment capability indications from the downstream routers indicate whether the respective downstream router is capable of supporting upstream assigned labels;

receiving a message having a label object with the at least one of the downstream routers, wherein the message requests a P2MP tunnel and the label object specifies an upstream assigned label allocated to the downstream routers of the P2MP tunnel that output the advertisements carrying the upstream label assignment capability indications, and wherein the message requesting the P2MP tunnel includes a Type-Length-Value of a label distribution protocol object that signals either a P2MP LSP or an IP Multicast Tunnel;

outputting, from the at least one of the downstream routers to the upstream router, a message to establish the P2MP tunnel without including any downstream assigned labels when the downstream router supports the type of label object included in the message and is able to process the upstream assigned label;

outputting, from the at least one of the downstream routers to the upstream router, a message specifying an error when the downstream router does not support the type of label object included in the message from the upstream router requesting the P2MP tunnel.

7. A router comprising:

a control unit comprising a processor; and

a label distribution protocol executing on the control unit to establish a point-to-multipoint (P2MP) tunnel across a network,

wherein the signaling protocol outputs an advertisement having an upstream label assignment capability indication that indicates whether the router is capable of supporting upstream assigned labels from an upstream router of the P2MP tunnel, wherein, when the router is capable of supporting upstream assigned labels, the advertisement comprises a label distribution protocol Hello message including a Capability object with a set flag,

wherein the router receives from the upstream router a request for the P2MP tunnel, the request having a label object specifying the upstream assigned label,

wherein, in response to the message requesting the P2MP tunnel, the label distribution protocol outputs to the upstream router a message to establish the P2MP tunnel without including any downstream assigned labels when the router supports the type of label object included in the request and is able to process the upstream assigned label, and

wherein the label distribution protocol outputs to the upstream router a message specifying an error when the router does not support the type of label object included in the request.

8. The router of claim 7, wherein the tunnel comprises one of a Resource Reservation Protocol with Traffic Engineering (RSVP-TE) Point to Multipoint (P2MP) Label Switched Path (LSP) or an Internet Protocol (IP) Multicast Tunnel.

9. The router of claim 7, wherein the advertisement comprises a Resource Reservation Protocol with Traffic Engineering (RSVP-TE) Hello message including a Capability object with a set U flag.

10. The router of claim 7, wherein the label distribution protocol comprises the Resource Reservation Protocol with Traffic Engineering (RSVP-TE).