Update to Include Route Object (IRO) specification in Path Computation Element communication Protocol (PCEP)
draft-ietf-pce-iro-update-05

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Last updated 2016-02-17 (latest revision 2016-01-27)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state Submitted to IESG for Publication
Document shepherd Jonathan Hardwick
Shepherd write-up Show (last changed 2016-02-03)
IESG IESG state AD Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to "Jonathan Hardwick" <jonathan.hardwick@metaswitch.com>
PCE Working Group                                               D. Dhody
Internet-Draft                                       Huawei Technologies
Updates: 5440 (if approved)                             January 27, 2016
Intended status: Standards Track
Expires: July 30, 2016

 Update to Include Route Object (IRO) specification in Path Computation
                 Element communication Protocol (PCEP)
                      draft-ietf-pce-iro-update-05

Abstract

   During discussions of a document to provide a standard representation
   and encoding of Domain-Sequence within the Path Computation Element
   (PCE) communication Protocol (PCEP) for communications between a Path
   Computation Client (PCC) and a PCE, or between two PCEs, it was
   determined that there was a need for clarification with respect to
   the ordered nature of the Include Route Object (IRO).

   An informal survey was conducted to determine the state of current
   and planned implementation with respect to IRO ordering and handling
   of Loose bit (L bit).

   This document updates RFC 5440 regarding the IRO specification, based
   on the survey conclusion and recommendation.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 30, 2016.

Dhody                     Expires July 30, 2016                 [Page 1]
Internet-Draft                 IRO-UPDATE                   January 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Update in IRO specification . . . . . . . . . . . . . . . . .   3
     2.1.  Update to RFC 5440  . . . . . . . . . . . . . . . . . . .   4
   3.  Other Considerations  . . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Path Computation Element Communication Protocol (PCEP) provides
   mechanisms for Path Computation Elements (PCEs) to perform path
   computations in response to Path Computation Clients (PCCs) requests.

Dhody                     Expires July 30, 2016                 [Page 2]
Internet-Draft                 IRO-UPDATE                   January 2016

   [RFC5440] defines the Include Route Object (IRO) to specify network
   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.
   It mentioned that the Loose bit (L bit) has no meaning within an IRO.
Show full document text