draft-ietf-pce-pcep-domain-sequence-11.txt   draft-ietf-pce-pcep-domain-sequence-12.txt 
PCE Working Group D. Dhody PCE Working Group D. Dhody
Internet-Draft U. Palle Internet-Draft U. Palle
Intended status: Experimental Huawei Technologies Intended status: Experimental Huawei Technologies
Expires: May 22, 2016 R. Casellas Expires: June 9, 2016 R. Casellas
CTTC CTTC
November 19, 2015 December 7, 2015
Domain Subobjects for Path Computation Element (PCE) Communication Domain Subobjects for Path Computation Element (PCE) Communication
Protocol (PCEP). Protocol (PCEP).
draft-ietf-pce-pcep-domain-sequence-11 draft-ietf-pce-pcep-domain-sequence-12
Abstract Abstract
The ability to compute shortest constrained Traffic Engineering Label The ability to compute shortest constrained Traffic Engineering Label
Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and Switched Paths (TE LSPs) in Multiprotocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) networks across multiple domains has been Generalized MPLS (GMPLS) networks across multiple domains has been
identified as a key requirement. In this context, a domain is a identified as a key requirement. In this context, a domain is a
collection of network elements within a common sphere of address collection of network elements within a common sphere of address
management or path computational responsibility such as an Interior management or path computational responsibility such as an Interior
Gateway Protocol (IGP) area or an Autonomous System (AS). This Gateway Protocol (IGP) area or an Autonomous System (AS). This
skipping to change at page 1, line 46 skipping to change at page 1, line 46
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 May 22, 2016. This Internet-Draft will expire on June 9, 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 25, line 40 skipping to change at page 25, line 40
+-L-------------W+ +------P---------+ +-----------T----+ +-L-------------W+ +------P---------+ +-----------T----+
| | | | | | | | | | | |
| | | Q | | U | | | | Q | | U |
| M O | | S | | | | M O | | S | | |
| | | | | V | | | | | | V |
| N | | R | | | | N | | R | | |
+----------------+ +----------------+ +----------------+ +----------------+ +----------------+ +----------------+
The domain tree can be represented as a series of domain-sequence - The domain tree can be represented as a series of domain-sequence -
o Domian D1, Domian D3, Domian D6 o Domain D1, Domain D3, Domain D6
o Domian D1, Domian D3, Domian D5 o Domain D1, Domain D3, Domain D5
o Domian D1, Domian D2, Domian D4 o Domain D1, Domain D2, Domain D4
The domain sequence handling described in this document could be The domain sequence handling described in this document could be
applied to P2MP path domain tree. applied to P2MP path domain tree.
4.6. Hierarchical PCE 4.6. Hierarchical PCE
In case of H-PCE [RFC6805], the parent PCE can be requested to In case of H-PCE [RFC6805], the parent PCE can be requested to
determine the Domain-Sequence and return it in the path computation determine the Domain-Sequence and return it in the path computation
reply, using the ERO. . For the example in section 4.6 of [RFC6805], reply, using the ERO. . For the example in section 4.6 of [RFC6805],
the Domain-Sequence can possibly appear as: the Domain-Sequence can possibly appear as:
skipping to change at page 31, line 38 skipping to change at page 31, line 38
[IRO-UPDATE] [IRO-UPDATE]
Dhody, D., "Update to Include Route Object (IRO) Dhody, D., "Update to Include Route Object (IRO)
specification in Path Computation Element communication specification in Path Computation Element communication
Protocol (PCEP. (draft-ietf-pce-iro-update-02)", May 2015. Protocol (PCEP. (draft-ietf-pce-iro-update-02)", May 2015.
[DOMAIN-SUBOBJ] [DOMAIN-SUBOBJ]
Dhody, D., Palle, U., Kondreddy, V., and R. Casellas, Dhody, D., Palle, U., Kondreddy, V., and R. Casellas,
"Domain Subobjects for Resource ReserVation Protocol - "Domain Subobjects for Resource ReserVation Protocol -
Traffic Engineering (RSVP-TE). (draft-ietf-teas-rsvp-te- Traffic Engineering (RSVP-TE). (draft-ietf-teas-rsvp-te-
domain-subobjects-04)", November 2015. domain-subobjects-05)", November 2015.
10.2. Informative References 10.2. Informative References
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, Element (PCE)-Based Architecture", RFC 4655,
DOI 10.17487/RFC4655, August 2006, DOI 10.17487/RFC4655, August 2006,
<http://www.rfc-editor.org/info/rfc4655>. <http://www.rfc-editor.org/info/rfc4655>.
[RFC4726] Farrel, A., Vasseur, J., and A. Ayyangar, "A Framework for [RFC4726] Farrel, A., Vasseur, J., and A. Ayyangar, "A Framework for
Inter-Domain Multiprotocol Label Switching Traffic Inter-Domain Multiprotocol Label Switching Traffic
skipping to change at page 33, line 12 skipping to change at page 33, line 12
DOI 10.17487/RFC7334, August 2014, DOI 10.17487/RFC7334, August 2014,
<http://www.rfc-editor.org/info/rfc7334>. <http://www.rfc-editor.org/info/rfc7334>.
[RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J. [RFC7420] Koushik, A., Stephan, E., Zhao, Q., King, D., and J.
Hardwick, "Path Computation Element Communication Protocol Hardwick, "Path Computation Element Communication Protocol
(PCEP) Management Information Base (MIB) Module", (PCEP) Management Information Base (MIB) Module",
RFC 7420, DOI 10.17487/RFC7420, December 2014, RFC 7420, DOI 10.17487/RFC7420, December 2014,
<http://www.rfc-editor.org/info/rfc7420>. <http://www.rfc-editor.org/info/rfc7420>.
[PCEPS] Lopez, D., Dios, O., Wu, W., and D. Dhody, "Secure [PCEPS] Lopez, D., Dios, O., Wu, W., and D. Dhody, "Secure
Transport for PCEP", draft-ietf-pce-pceps-05 (work in Transport for PCEP", draft-ietf-pce-pceps-06 (work in
progress), November 2015. progress), November 2015.
Authors' Addresses Authors' Addresses
Dhruv Dhody Dhruv Dhody
Huawei Technologies Huawei Technologies
Divyashree Techno Park, Whitefield Divyashree Techno Park, Whitefield
Bangalore, Karnataka 560037 Bangalore, Karnataka 560037
India India
 End of changes. 9 change blocks. 
9 lines changed or deleted 9 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/