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

rfc-editor@rfc-editor.org Wed, 15 June 2016 22:22 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E330612D881; Wed, 15 Jun 2016 15:22:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.628
X-Spam-Status: No, score=-105.628 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id PxjEvhCv-TSj; Wed, 15 Jun 2016 15:22:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 201BD12DC29; Wed, 15 Jun 2016 15:22:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0B87BB812C1; Wed, 15 Jun 2016 15:22:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160615222204.0B87BB812C1@rfc-editor.org>
Date: Wed, 15 Jun 2016 15:22:04 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/sbHuABgKrUGPV4sVzJyHsm5W0tY>
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 7896 on Update to the Include Route Object (IRO) Specification in the Path Computation Element Communication Protocol (PCEP)
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
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: Wed, 15 Jun 2016 22:22:18 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7896

        Title:      Update to the Include Route 
                    Object (IRO) Specification in the Path 
                    Computation Element Communication Protocol (PCEP) 
        Author:     D. Dhody
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2016
        Mailbox:    dhruv.ietf@gmail.com
        Pages:      5
        Characters: 9966
        Updates:    RFC 5440

        I-D Tag:    draft-ietf-pce-iro-update-07.txt

        URL:        https://www.rfc-editor.org/info/rfc7896

        DOI:        http://dx.doi.org/10.17487/RFC7896

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

This document updates RFC 5440 regarding the IRO specification.

This document is a product of the Path Computation Element Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC