| < draft-ietf-pce-lsp-setup-type-00.txt | draft-ietf-pce-lsp-setup-type-01.txt > | |||
|---|---|---|---|---|
| PCE Working Group S. Sivabalan | PCE Working Group S. Sivabalan | |||
| Internet-Draft J. Medved | Internet-Draft J. Medved | |||
| Intended status: Standards Track Cisco Systems, Inc. | Intended status: Standards Track Cisco Systems, Inc. | |||
| Expires: April 28, 2015 I. Minei | Expires: September 10, 2015 I. Minei | |||
| E. Crabbe | ||||
| Google, Inc. | Google, Inc. | |||
| E. Crabbe | ||||
| R. Varga | R. Varga | |||
| Pantheon Technologies SRO | Pantheon Technologies SRO | |||
| October 25, 2014 | J. Tantsura | |||
| Ericsson | ||||
| March 9, 2015 | ||||
| Conveying path setup type in PCEP messages | Conveying path setup type in PCEP messages | |||
| draft-ietf-pce-lsp-setup-type-00.txt | draft-ietf-pce-lsp-setup-type-01.txt | |||
| Abstract | Abstract | |||
| A Path Computation Element can compute traffic engineering paths (TE | A Path Computation Element can compute traffic engineering paths (TE | |||
| paths) through a network that are subject to various constraints. | paths) through a network that are subject to various constraints. | |||
| Currently, TE paths are label switched paths (LSPs) which are set up | Currently, TE paths are label switched paths (LSPs) which are set up | |||
| using the RSVP-TE signaling protocol. However, other TE path setup | using the RSVP-TE signaling protocol. However, other TE path setup | |||
| methods are possible within the PCE architecture. This document | methods are possible within the PCE architecture. This document | |||
| proposes an extension to PCEP to allow support for different path | proposes an extension to PCEP to allow support for different path | |||
| setup methods over a given PCEP session. | setup methods over a given PCEP session. | |||
| skipping to change at page 1, line 46 ¶ | skipping to change at page 2, line 4 ¶ | |||
| 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 10, 2015. | ||||
| This Internet-Draft will expire on April 28, 2015. | ||||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2015 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 6, line 14 ¶ | skipping to change at page 6, line 14 ¶ | |||
| 7. Acknowledgements | 7. Acknowledgements | |||
| We like to thank Marek Zavodsky for valuable comments. | We like to thank Marek Zavodsky for valuable comments. | |||
| 8. Normative References | 8. Normative References | |||
| [I-D.ietf-pce-pce-initiated-lsp] | [I-D.ietf-pce-pce-initiated-lsp] | |||
| Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP | Crabbe, E., Minei, I., Sivabalan, S., and R. Varga, "PCEP | |||
| Extensions for PCE-initiated LSP Setup in a Stateful PCE | Extensions for PCE-initiated LSP Setup in a Stateful PCE | |||
| Model", draft-ietf-pce-pce-initiated-lsp-01 (work in | Model", draft-ietf-pce-pce-initiated-lsp-03 (work in | |||
| progress), June 2014. | progress), March 2015. | |||
| [I-D.ietf-pce-stateful-pce] | [I-D.ietf-pce-stateful-pce] | |||
| Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP | Crabbe, E., Minei, I., Medved, J., and R. Varga, "PCEP | |||
| Extensions for Stateful PCE", draft-ietf-pce-stateful- | Extensions for Stateful PCE", draft-ietf-pce-stateful- | |||
| pce-09 (work in progress), June 2014. | pce-10 (work in progress), October 2014. | |||
| [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, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element | [RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element | |||
| (PCE) Communication Protocol (PCEP)", RFC 5440, March | (PCE) Communication Protocol (PCEP)", RFC 5440, March | |||
| 2009. | 2009. | |||
| Authors' Addresses | Authors' Addresses | |||
| skipping to change at page 7, line 13 ¶ | skipping to change at page 7, line 13 ¶ | |||
| Email: jmedved@cisco.com | Email: jmedved@cisco.com | |||
| Ina Minei | Ina Minei | |||
| Google, Inc. | Google, Inc. | |||
| 1600 Amphitheatre Parkway | 1600 Amphitheatre Parkway | |||
| Mountain View, CA 94043 | Mountain View, CA 94043 | |||
| USA | USA | |||
| Email: inaminei@google.com | Email: inaminei@google.com | |||
| Edward Crabbe | Edward Crabbe | |||
| Google, Inc. | ||||
| 1600 Amphitheatre Parkway | ||||
| Mountain View, CA 94043 | ||||
| USA | ||||
| Email: edc@google.com | ||||
| Robert Varga | Robert Varga | |||
| Pantheon Technologies SRO | Pantheon Technologies SRO | |||
| Mlynske Nivy 56 | Mlynske Nivy 56 | |||
| Bratislava, 821 05 | Bratislava, 821 05 | |||
| Slovakia | Slovakia | |||
| Email: robert.vargad@pantheon.sk | Email: robert.vargad@pantheon.sk | |||
| Jeff Tantsura | ||||
| Ericsson | ||||
| 300 Holger Way | ||||
| San Jose, CA 95134 | ||||
| USA | ||||
| Email: jeff.tantsura@ericsson.com | ||||
| End of changes. 10 change blocks. | ||||
| 16 lines changed or deleted | 12 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/ | ||||