draft-ietf-pce-stateful-sync-optimizations-02.txt | draft-ietf-pce-stateful-sync-optimizations-03.txt | |||
---|---|---|---|---|
PCE Working Group E. Crabbe | PCE Working Group E. Crabbe | |||
Internet-Draft | Internet-Draft | |||
Intended status: Standards Track I. Minei | Intended status: Standards Track I. Minei | |||
Expires: July 16, 2015 Google, Inc. | Expires: April 8, 2016 Google, Inc. | |||
J. Medved | J. Medved | |||
Cisco Systems, Inc. | Cisco Systems, Inc. | |||
R. Varga | R. Varga | |||
Pantheon Technologies SRO | Pantheon Technologies SRO | |||
X. Zhang | X. Zhang | |||
D. Dhody | D. Dhody | |||
Huawei Technologies | Huawei Technologies | |||
January 12, 2015 | October 6, 2015 | |||
Optimizations of Label Switched Path State Synchronization Procedures | Optimizations of Label Switched Path State Synchronization Procedures | |||
for a Stateful PCE | for a Stateful PCE | |||
draft-ietf-pce-stateful-sync-optimizations-02 | draft-ietf-pce-stateful-sync-optimizations-03 | |||
Abstract | Abstract | |||
A stateful Path Computation Element (PCE) has access to not only the | A stateful Path Computation Element (PCE) has access to not only the | |||
information disseminated by the network's Interior Gateway Protocol | information disseminated by the network's Interior Gateway Protocol | |||
(IGP), but also the set of active paths and their reserved resources | (IGP), but also the set of active paths and their reserved resources | |||
for its computation. The additional Label Switched Path (LSP) state | for its computation. The additional Label Switched Path (LSP) state | |||
information allows the PCE to compute constrained paths while | information allows the PCE to compute constrained paths while | |||
considering individual LSPs and their interactions. This requires a | considering individual LSPs and their interactions. This requires a | |||
reliable state synchronization mechanism between the PCE and the | reliable state synchronization mechanism between the PCE and the | |||
skipping to change at page 2, line 12 | skipping to change at page 2, line 12 | |||
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 July 16, 2015. | This Internet-Draft will expire on April 8, 2016. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2015 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 | |||
skipping to change at page 21, line 31 | skipping to change at page 21, line 31 | |||
P.R. China | P.R. China | |||
Email: xiegang09@huawei.com | Email: xiegang09@huawei.com | |||
13. References | 13. References | |||
13.1. Normative References | 13.1. Normative References | |||
[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-10 (work in progress), October 2014. | pce-11 (work in progress), April 2015. | |||
[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, | |||
DOI 10.17487/RFC2119, March 1997, | ||||
<http://www.rfc-editor.org/info/rfc2119>. | ||||
[RFC5440] Vasseur, JP. and JL. Le Roux, "Path Computation Element | [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation | |||
(PCE) Communication Protocol (PCEP)", RFC 5440, March | Element (PCE) Communication Protocol (PCEP)", RFC 5440, | |||
2009. | DOI 10.17487/RFC5440, March 2009, | |||
<http://www.rfc-editor.org/info/rfc5440>. | ||||
13.2. Informative References | 13.2. Informative 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-02 (work in | Model", draft-ietf-pce-pce-initiated-lsp-04 (work in | |||
progress), October 2014. | progress), April 2015. | |||
Authors' Addresses | Authors' Addresses | |||
Edward Crabbe | Edward Crabbe | |||
Email: edward.crabbe@gmail.com | Email: edward.crabbe@gmail.com | |||
Ina Minei | Ina Minei | |||
Google, Inc. | Google, Inc. | |||
1600 Amphitheatre Parkway | 1600 Amphitheatre Parkway | |||
skipping to change at page 23, line 6 | skipping to change at page 23, line 6 | |||
Xian Zhang | Xian Zhang | |||
Huawei Technologies | Huawei Technologies | |||
F3-5-B R&D Center, Huawei Industrial Base, Bantian, Longgang District | F3-5-B R&D Center, Huawei Industrial Base, Bantian, Longgang District | |||
Shenzhen, Guangdong 518129 | Shenzhen, Guangdong 518129 | |||
P.R.China | P.R.China | |||
Email: zhang.xian@huawei.com | Email: zhang.xian@huawei.com | |||
Dhruv Dhody | Dhruv Dhody | |||
Huawei Technologies | Huawei Technologies | |||
Leela Palace | Divyashree Techno Park, Whitefield | |||
Bangalore, Karnataka 560008 | Bangalore, Karnataka 560037 | |||
India | India | |||
Email: dhruv.ietf@gmail.com | Email: dhruv.ietf@gmail.com | |||
End of changes. 9 change blocks. | ||||
13 lines changed or deleted | 16 lines changed or added | |||
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |