Update to Include Route Object (IRO) specification in Path Computation Element communication Protocol (PCEP)
draft-dhody-pce-iro-update-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dhruv Dhody | ||
| Last updated | 2015-07-03 (Latest revision 2014-12-30) | ||
| Replaced by | draft-ietf-pce-iro-update | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-pce-iro-update | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 the IRO specification based on the survey conclusion and recommendation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)