draft-ietf-teas-rsvp-ingress-protection-05.txt | draft-ietf-teas-rsvp-ingress-protection-06.txt | |||
---|---|---|---|---|
Internet Engineering Task Force H. Chen, Ed. | Internet Engineering Task Force H. Chen, Ed. | |||
Internet-Draft Huawei Technologies | Internet-Draft Huawei Technologies | |||
Intended status: Experimental R. Torvi, Ed. | Intended status: Experimental R. Torvi, Ed. | |||
Expires: September 22, 2016 Juniper Networks | Expires: October 17, 2016 Juniper Networks | |||
March 21, 2016 | April 15, 2016 | |||
Extensions to RSVP-TE for LSP Ingress Local Protection | Extensions to RSVP-TE for LSP Ingress Local Protection | |||
draft-ietf-teas-rsvp-ingress-protection-05.txt | draft-ietf-teas-rsvp-ingress-protection-06.txt | |||
Abstract | Abstract | |||
This document describes extensions to Resource Reservation Protocol - | This document describes extensions to Resource Reservation Protocol - | |||
Traffic Engineering (RSVP-TE) for locally protecting the ingress node | Traffic Engineering (RSVP-TE) for locally protecting the ingress node | |||
of a Traffic Engineered (TE) Label Switched Path (LSP), which is a | of a Traffic Engineered (TE) Label Switched Path (LSP), which is a | |||
Point-to-Point (P2P) LSP or a Point-to-Multipoint (P2MP) LSP. | Point-to-Point (P2P) LSP or a Point-to-Multipoint (P2MP) LSP. | |||
Status of this Memo | Status of this Memo | |||
skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
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 September 22, 2016. | This Internet-Draft will expire on October 17, 2016. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2016 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 | |||
skipping to change at page 3, line 7 ¶ | skipping to change at page 3, line 7 ¶ | |||
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 | 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 | |||
8.1. A New Class Number . . . . . . . . . . . . . . . . . . . . 20 | 8.1. A New Class Number . . . . . . . . . . . . . . . . . . . . 20 | |||
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20 | 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 21 | 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
11. Normative References . . . . . . . . . . . . . . . . . . . . . 21 | 11. Normative References . . . . . . . . . . . . . . . . . . . . . 21 | |||
A. Problem Summary . . . . . . . . . . . . . . . . . . . . . . . 22 | A. Problem Summary . . . . . . . . . . . . . . . . . . . . . . . 22 | |||
B. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23 | B. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 23 | |||
1. Co-authors | 1. Co-authors | |||
Ning So, Autumn Liu, Alia Atlas, Yimin Shen, Tarek Saad, Fengman Xu, | Ning So, Autumn Liu, Yimin Shen, Tarek Saad, Fengman Xu, Mehmet Toy, | |||
Mehmet Toy, Lei Liu | Lei Liu | |||
2. Introduction | 2. Introduction | |||
For a MPLS LSP it is important to have a fast-reroute method for | For a MPLS LSP it is important to have a fast-reroute method for | |||
protecting its ingress node and transit nodes. Protecting an ingress | protecting its ingress node and transit nodes. Protecting an ingress | |||
is not covered either in the fast-reroute method defined in [RFC4090] | is not covered either in the fast-reroute method defined in [RFC4090] | |||
or in the P2MP fast-reroute extensions to fast-reroute in [RFC4875]. | or in the P2MP fast-reroute extensions to fast-reroute in [RFC4875]. | |||
An alternate approach to local protection (fast-reroute) is to use | An alternate approach to local protection (fast-reroute) is to use | |||
global protection and set up a secondary backup LSP (whether P2MP or | global protection and set up a secondary backup LSP (whether P2MP or | |||
skipping to change at page 21, line 28 ¶ | skipping to change at page 21, line 28 ¶ | |||
Markus Jork | Markus Jork | |||
Juniper Networks | Juniper Networks | |||
10 Technology Park Drive | 10 Technology Park Drive | |||
Westford, MA 01886 | Westford, MA 01886 | |||
USA | USA | |||
Email: mjork@juniper.net | Email: mjork@juniper.net | |||
10. Acknowledgement | 10. Acknowledgement | |||
The authors would like to thank Nobo Akiya, Rahul Aggarwal, Eric | The authors would like to thank Nobo Akiya, Rahul Aggarwal, Eric | |||
Osborne, Ross Callon, Loa Andersson, Daniel King, Michael Yue, | Osborne, Ross Callon, Loa Andersson, Daniel King, Michael Yue, Alia | |||
Olufemi Komolafe, Rob Rennison, Neil Harrison, Kannan Sampath, | Atlas, Olufemi Komolafe, Rob Rennison, Neil Harrison, Kannan Sampath, | |||
Gregory Mirsky, and Ronhazli Adam for their valuable comments and | Gregory Mirsky, and Ronhazli Adam for their valuable comments and | |||
suggestions on this draft. | suggestions on this draft. | |||
11. Normative References | 11. Normative References | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ | Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ | |||
RFC2119, March 1997, | RFC2119, March 1997, | |||
<http://www.rfc-editor.org/info/rfc2119>. | <http://www.rfc-editor.org/info/rfc2119>. | |||
skipping to change at page 24, line 18 ¶ | skipping to change at page 24, line 18 ¶ | |||
USA | USA | |||
Email: ningso01@gmail.com | Email: ningso01@gmail.com | |||
Autumn Liu | Autumn Liu | |||
Ericsson | Ericsson | |||
300 Holger Way | 300 Holger Way | |||
San Jose, CA 95134 | San Jose, CA 95134 | |||
USA | USA | |||
Email: autumn.liu@ericsson.com | Email: autumn.liu@ericsson.com | |||
Alia Atlas | ||||
Juniper Networks | ||||
10 Technology Park Drive | ||||
Westford, MA 01886 | ||||
USA | ||||
Email: akatlas@juniper.net | ||||
Yimin Shen | Yimin Shen | |||
Juniper Networks | Juniper Networks | |||
10 Technology Park Drive | 10 Technology Park Drive | |||
Westford, MA 01886 | Westford, MA 01886 | |||
USA | USA | |||
Email: yshen@juniper.net | Email: yshen@juniper.net | |||
Tarek Saad | Tarek Saad | |||
Cisco Systems | Cisco Systems | |||
Email: tsaad@cisco.com | Email: tsaad@cisco.com | |||
End of changes. 6 change blocks. | ||||
15 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |