draft-ietf-pce-iro-update-02.txt   draft-ietf-pce-iro-update-03.txt 
PCE Working Group D. Dhody PCE Working Group D. Dhody
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Updates: 5440 (if approved) May 20, 2015 Updates: 5440 (if approved) November 16, 2015
Intended status: Standards Track Intended status: Standards Track
Expires: November 21, 2015 Expires: May 19, 2016
Update to Include Route Object (IRO) specification in Path Computation Update to Include Route Object (IRO) specification in Path Computation
Element communication Protocol (PCEP) Element communication Protocol (PCEP)
draft-ietf-pce-iro-update-02 draft-ietf-pce-iro-update-03
Abstract Abstract
During discussions of a document to provide a standard representation During discussions of a document to provide a standard representation
and encoding of Domain-Sequence within the Path Computation Element and encoding of Domain-Sequence within the Path Computation Element
(PCE) communication Protocol (PCEP) for communications between a Path (PCE) communication Protocol (PCEP) for communications between a Path
Computation Client (PCC) and a PCE, or between two PCEs, it was Computation Client (PCC) and a PCE, or between two PCEs, it was
determined that there was a need for clarification with respect to determined that there was a need for clarification with respect to
the ordered nature of the Include Route Object (IRO). the ordered nature of the Include Route Object (IRO).
An informal survey was conducted to determine the state of current An informal survey was conducted to determine the state of current
and planned implementation with respect to IRO ordering and handling and planned implementation with respect to IRO ordering and handling
of Loose bit (L bit). of Loose bit (L bit).
This document updates the IRO specification based on the survey This document updates the IRO specification of RFC 5440 based on the
conclusion and recommendation. survey conclusion and recommendation.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 November 21, 2015. This Internet-Draft will expire on May 19, 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 2, line 32 skipping to change at page 2, line 32
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Update in IRO specification . . . . . . . . . . . . . . . . . 3 2. Update in IRO specification . . . . . . . . . . . . . . . . . 3
3. Other Considerations . . . . . . . . . . . . . . . . . . . . 4 3. Other Considerations . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
7.1. Normative References . . . . . . . . . . . . . . . . . . 4 7.1. Normative References . . . . . . . . . . . . . . . . . . 4
7.2. Informative References . . . . . . . . . . . . . . . . . 5 7.2. Informative References . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
The Path Computation Element Communication Protocol (PCEP) provides The Path Computation Element Communication Protocol (PCEP) provides
mechanisms for Path Computation Elements (PCEs) to perform path mechanisms for Path Computation Elements (PCEs) to perform path
computations in response to Path Computation Clients (PCCs) requests. computations in response to Path Computation Clients (PCCs) requests.
[RFC5440] defines the Include Route Object (IRO) to specify network [RFC5440] defines the Include Route Object (IRO) to specify network
elements to be traversed in the computed path. The specification did elements to be traversed in the computed path. The specification did
not mention if IRO is an ordered or un-ordered list of sub-objects. not mention if IRO is an ordered or un-ordered list of sub-objects.
skipping to change at page 4, line 50 skipping to change at page 5, line 6
Thanks to Francesco Fondelli for his suggestions in clarifying the L Thanks to Francesco Fondelli for his suggestions in clarifying the L
bit usage. bit usage.
Thanks to Adrian Farrel for his review and comments. Thanks to Adrian Farrel for his review and comments.
7. References 7. References
7.1. Normative References 7.1. 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, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001. Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<http://www.rfc-editor.org/info/rfc3209>.
[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>.
7.2. Informative References 7.2. Informative References
[RFC5441] Vasseur, JP., Zhang, R., Bitar, N., and JL. Le Roux, "A [RFC5441] Vasseur, JP., Ed., Zhang, R., Bitar, N., and JL. Le Roux,
Backward-Recursive PCE-Based Computation (BRPC) Procedure "A Backward-Recursive PCE-Based Computation (BRPC)
to Compute Shortest Constrained Inter-Domain Traffic Procedure to Compute Shortest Constrained Inter-Domain
Engineering Label Switched Paths", RFC 5441, April 2009. Traffic Engineering Label Switched Paths", RFC 5441,
DOI 10.17487/RFC5441, April 2009,
<http://www.rfc-editor.org/info/rfc5441>.
[RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of
BGP, LDP, PCEP, and MSDP Issues According to the Keying BGP, LDP, PCEP, and MSDP Issues According to the Keying
and Authentication for Routing Protocols (KARP) Design and Authentication for Routing Protocols (KARP) Design
Guide", RFC 6952, May 2013. Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013,
<http://www.rfc-editor.org/info/rfc6952>.
[I-D.ietf-pce-pcep-domain-sequence] [I-D.ietf-pce-pcep-domain-sequence]
Dhody, D., Palle, U., and R. Casellas, "Standard Dhody, D., Palle, U., and R. Casellas, "Standard
Representation of Domain-Sequence", draft-ietf-pce-pcep- Representation of Domain-Sequence", draft-ietf-pce-pcep-
domain-sequence-08 (work in progress), April 2015. domain-sequence-09 (work in progress), September 2015.
[I-D.ietf-pce-pceps] [I-D.ietf-pce-pceps]
Lopez, D., Dios, O., Wu, W., and D. Dhody, "Secure Lopez, D., Dios, O., Wu, W., and D. Dhody, "Secure
Transport for PCEP", draft-ietf-pce-pceps-04 (work in Transport for PCEP", draft-ietf-pce-pceps-05 (work in
progress), May 2015. progress), November 2015.
[I-D.dhody-pce-iro-survey] [I-D.dhody-pce-iro-survey]
Dhody, D., "Informal Survey into Include Route Object Dhody, D., "Informal Survey into Include Route Object
(IRO) Implementations in Path Computation Element (IRO) Implementations in Path Computation Element
communication Protocol (PCEP)", draft-dhody-pce-iro- communication Protocol (PCEP)", draft-dhody-pce-iro-
survey-02 (work in progress), December 2014. survey-02 (work in progress), December 2014.
Author's Address Author's Address
Dhruv Dhody Dhruv Dhody
 End of changes. 13 change blocks. 
20 lines changed or deleted 27 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/