| < draft-ietf-mpls-ldp-mrt-02.txt | draft-ietf-mpls-ldp-mrt-03.txt > | |||
|---|---|---|---|---|
| MPLS Working Group A. Atlas | MPLS Working Group A. Atlas | |||
| Internet-Draft K. Tiruveedhula | Internet-Draft K. Tiruveedhula | |||
| Intended status: Standards Track C. Bowers | Intended status: Standards Track C. Bowers | |||
| Expires: April 2, 2016 Juniper Networks | Expires: November 19, 2016 Juniper Networks | |||
| J. Tantsura | J. Tantsura | |||
| Ericsson | Individual | |||
| IJ. Wijnands | IJ. Wijnands | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| September 30, 2015 | May 18, 2016 | |||
| LDP Extensions to Support Maximally Redundant Trees | LDP Extensions to Support Maximally Redundant Trees | |||
| draft-ietf-mpls-ldp-mrt-02 | draft-ietf-mpls-ldp-mrt-03 | |||
| Abstract | Abstract | |||
| This document specifies extensions to the Label Distribution | This document specifies extensions to the Label Distribution | |||
| Protocol(LDP) to support the creation of label-switched paths for | Protocol(LDP) to support the creation of label-switched paths for | |||
| Maximally Redundant Trees (MRT). A prime use of MRTs is for unicast | Maximally Redundant Trees (MRT). A prime use of MRTs is for unicast | |||
| and multicast IP/LDP Fast-Reroute, which we will refer to as MRT-FRR. | and multicast IP/LDP Fast-Reroute, which we will refer to as MRT-FRR. | |||
| The sole protocol extension to LDP is simply the ability to advertise | The sole protocol extension to LDP is simply the ability to advertise | |||
| an MRT Capability. This document describes that extension and the | an MRT Capability. This document describes that extension and the | |||
| skipping to change at page 1, line 47 ¶ | skipping to change at page 1, line 47 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on April 2, 2016. | This Internet-Draft will expire on November 19, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2016 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| carefully, as they describe your rights and restrictions with respect | carefully, as they describe your rights and restrictions with respect | |||
| to this document. Code Components extracted from this document must | to this document. Code Components extracted from this document must | |||
| include Simplified BSD License text as described in Section 4.e of | include Simplified BSD License text as described in Section 4.e of | |||
| the Trust Legal Provisions and are provided without warranty as | the Trust Legal Provisions and are provided without warranty as | |||
| skipping to change at page 13, line 43 ¶ | skipping to change at page 13, line 43 ¶ | |||
| propagate a label mapping for that Rainbow FEC. | propagate a label mapping for that Rainbow FEC. | |||
| 6. Security Considerations | 6. Security Considerations | |||
| The labels distributed by the extensions in this document create | The labels distributed by the extensions in this document create | |||
| additional forwarding paths that do not following shortest path | additional forwarding paths that do not following shortest path | |||
| routes. The transit label swapping operations defining these | routes. The transit label swapping operations defining these | |||
| alternative forwarding paths are created during normal operations | alternative forwarding paths are created during normal operations | |||
| (before a failure occurs). Therefore, a malicious packet with an | (before a failure occurs). Therefore, a malicious packet with an | |||
| appropriate label injected into the network from a compromised | appropriate label injected into the network from a compromised | |||
| location would be forwarded to a destinations along a non-shortest | location would be forwarded to a destination along a non-shortest | |||
| path. When this technology is deployed, a network security design | path. When this technology is deployed, a network security design | |||
| should not rely on assumptions about potentially malicious traffic | should not rely on assumptions about potentially malicious traffic | |||
| only following shortest paths. | only following shortest paths. | |||
| It should be noted that the creation of non-shortest forwarding paths | It should be noted that the creation of non-shortest forwarding paths | |||
| is not unique to MRT. | is not unique to MRT. | |||
| 7. Potential restrictions on MRT-related MT-ID values imposed by | 7. Potential restrictions on MRT-related MT-ID values imposed by | |||
| RFC6420 | RFC6420 | |||
| skipping to change at page 18, line 5 ¶ | skipping to change at page 18, line 5 ¶ | |||
| Email: kishoret@juniper.net | Email: kishoret@juniper.net | |||
| Chris Bowers | Chris Bowers | |||
| Juniper Networks | Juniper Networks | |||
| 1194 N. Mathilda Ave. | 1194 N. Mathilda Ave. | |||
| Sunnyvale, CA 94089 | Sunnyvale, CA 94089 | |||
| USA | USA | |||
| Email: cbowers@juniper.net | Email: cbowers@juniper.net | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Ericsson | Individual | |||
| 300 Holger Way | ||||
| San Jose, CA 95134 | ||||
| USA | USA | |||
| Email: jeff.tantsura@ericsson.com | Email: jefftant.ietf@gmail.com | |||
| IJsbrand Wijnands | IJsbrand Wijnands | |||
| Cisco Systems, Inc. | Cisco Systems, Inc. | |||
| Email: ice@cisco.com | Email: ice@cisco.com | |||
| End of changes. 9 change blocks. | ||||
| 11 lines changed or deleted | 9 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||