draft-ietf-pce-hierarchy-fwk-03.txt   draft-ietf-pce-hierarchy-fwk-04.txt 
Network Working Group D. King (Ed.) Network Working Group D. King (Ed.)
Internet-Draft Old Dog Consulting Internet-Draft Old Dog Consulting
Intended Status: Informational A. Farrel (Ed.) Intended Status: Informational A. Farrel (Ed.)
Expires: 27 November 2012 Old Dog Consulting Expires: 28 November 2012 Old Dog Consulting
27 June 2012 28 June 2012
The Application of the Path Computation Element Architecture to the The Application of the Path Computation Element Architecture to the
Determination of a Sequence of Domains in MPLS and GMPLS Determination of a Sequence of Domains in MPLS and GMPLS
draft-ietf-pce-hierarchy-fwk-03.txt draft-ietf-pce-hierarchy-fwk-04.txt
Abstract Abstract
Computing optimum routes for Label Switched Paths (LSPs) across Computing optimum routes for Label Switched Paths (LSPs) across
multiple domains in MPLS Traffic Engineering (MPLS-TE) and GMPLS multiple domains in MPLS Traffic Engineering (MPLS-TE) and GMPLS
networks presents a problem because no single point of path networks presents a problem because no single point of path
computation is aware of all of the links and resources in each computation is aware of all of the links and resources in each
domain. A solution may be achieved using the Path Computation domain. A solution may be achieved using the Path Computation
Element (PCE) architecture. Element (PCE) architecture.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on 27 November 2012. This Internet-Draft will expire on 28 November 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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 19, line 20 skipping to change at page 19, line 20
parent PCE can elect to: parent PCE can elect to:
o Cancel the request and send the relevant response back to the o Cancel the request and send the relevant response back to the
initial child PCE that requested an end-to-end path; initial child PCE that requested an end-to-end path;
o Relax some of the constraints associated with the initial path o Relax some of the constraints associated with the initial path
request; request;
o Select another candidate domain and send the path request to the o Select another candidate domain and send the path request to the
child PCE responsible for the domain. child PCE responsible for the domain.
If the parent PCE does not receive a response from a child PCE within If the parent PCE does not receive a response from a child PCE within
an allotted time period. The parent PCE can either: an allotted time period. The parent PCE can elect to:
o Cancel the request and send the relevant response back to the
initial child PCE that requested an end-to-end path;
o Send the path request to another child PCE in the same domain, if a o Send the path request to another child PCE in the same domain, if a
secondary child PCE exists; secondary child PCE exists;
o Select another candidate domain and send the path request to the o Select another candidate domain and send the path request to the
child PCE responsible for that domain. child PCE responsible for that domain.
The parent PCE may also want to prune any unresponsive child PCE The parent PCE may also want to prune any unresponsive child PCE
domain paths from the candidate set. domain paths from the candidate set.
4.8 Requirements for Hierarchical PCEP Protocol Extensions 4.8 Requirements for Hierarchical PCEP Protocol Extensions
 End of changes. 5 change blocks. 
5 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/