[Pce] I-D Action: draft-ietf-pce-iro-update-07.txt

internet-drafts@ietf.org Fri, 22 April 2016 05:52 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFBB012D99E; Thu, 21 Apr 2016 22:52:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160422055254.19518.95172.idtracker@ietfa.amsl.com>
Date: Thu, 21 Apr 2016 22:52:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/pce/DZNwmC_Nzdn5ZjgggKkkeCTbft0>
Cc: pce@ietf.org
Subject: [Pce] I-D Action: draft-ietf-pce-iro-update-07.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Apr 2016 05:52:54 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element of the IETF.

        Title           : Update to Include Route Object (IRO) specification in Path Computation Element communication Protocol (PCEP)
        Author          : Dhruv Dhody
	Filename        : draft-ietf-pce-iro-update-07.txt
	Pages           : 5
	Date            : 2016-04-21

   The Path Computation Element Communication Protocol (PCEP) provides
   for 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 did not specify if the IRO contains an ordered or
   un-ordered list of sub-objects.  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 handling of an attribute of the IRO's sub-object, the
   Loose hop bit (L bit).

   This document updates RFC 5440 regarding the IRO specification.

The IETF datatracker status page for this draft is:

There's also a htmlized version available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at: