Update to the Include Route Object (IRO) Specification in the Path Computation Element Communication Protocol (PCEP)
RFC 7896

Document Type RFC - Proposed Standard (June 2016; No errata)
Updates RFC 5440
Last updated 2019-03-11
Replaces draft-dhody-pce-iro-update
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jonathan Hardwick
Shepherd write-up Show (last changed 2016-02-03)
IESG IESG state RFC 7896 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to "Jonathan Hardwick" <jonathan.hardwick@metaswitch.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions
Internet Engineering Task Force (IETF)                          D. Dhody
Request for Comments: 7896                           Huawei Technologies
Updates: 5440                                                  June 2016
Category: Standards Track
ISSN: 2070-1721

         Update to the Include Route Object (IRO) Specification
     in the Path Computation Element Communication Protocol (PCEP)

Abstract

   The Path Computation Element Communication Protocol (PCEP) enables
   communications between a Path Computation Client (PCC) and a PCE, or
   between two PCEs.  RFC 5440 defines the Include Route Object (IRO) to
   specify network elements to be traversed in the computed path.  The
   specification does not specify if the IRO contains an ordered or
   unordered list of subobjects.  During recent discussions, it was
   determined that there was a need to define a standard representation
   to ensure interoperability.  It was also noted that there is a
   benefit in the handling of an attribute of the IRO's subobject, the L
   bit.

   This document updates RFC 5440 regarding the IRO specification.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7896.

Dhody                        Standards Track                    [Page 1]
RFC 7896                IRO Specification Update               June 2016

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Update in the IRO Specification . . . . . . . . . . . . . . .   3
     2.1.  Update to RFC 5440  . . . . . . . . . . . . . . . . . . .   3
   3.  Operational Considerations  . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     5.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

Dhody                        Standards Track                    [Page 2]
RFC 7896                IRO Specification Update               June 2016

1.  Introduction

   The Path Computation Element Communication Protocol (PCEP) enables
   communications between a Path Computation Client (PCC) and a PCE, or
   between two PCEs.  [RFC5440] defines the Include Route Object (IRO)
   to specify network elements to be traversed in the computed path.
   The specification does not specify if the IRO is an ordered or
   unordered list of subobjects.  In addition, it defines the L bit as
   having no meaning within an IRO.

   [RFC5441] describes the use of an IRO to indicate the sequence of
   domains to be traversed during inter-domain path computation.

   During recent discussions, it was determined that there was a need to
   define a standard representation to ensure interoperability.

   This document updates the IRO specifications in Section 7.12 of
Show full document text