Browse Prior Art Database

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

IP.com Disclosure Number: IPCOM000246762D
Original Publication Date: 2016-Jun-01
Included in the Prior Art Database: 2016-Jun-29
Document File: 10 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Dhody: AUTHOR

Abstract

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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 27% of the total text.

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...