Updated Rules for Processing Stateful PCE Request Parameters Flags
draft-farrel-pce-stateful-flags-03

Document Type Replaced Internet-Draft (pce WG)
Last updated 2019-11-06 (latest revision 2019-10-31)
Replaced by draft-ietf-pce-stateful-flags
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
pdf htmlized bibtex
Reviews
Stream WG state Candidate for WG Adoption
Revised I-D Needed - Issue raised by AD
Document shepherd Hariharan Ananthakrishnan
Shepherd write-up Show (last changed 2019-09-23)
IESG IESG state Replaced by draft-ietf-pce-stateful-flags
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Hariharan Ananthakrishnan <hari@netflix.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-farrel-pce-stateful-flags-03.txt

Abstract

Extensions to the Path Computation Element Communication Protocol (PCEP) to support stateful Path Computation Elements (PCEs) are defined in RFC 8231. One of the extensions is the Stateful PCE Request Parameters (SRP) object. That object includes a Flags field that is a set of 32 bit flags, and RFC 8281 defines an IANA registry for tracking assigned flags. However, RFC 8231 does not explain how an implementation should set unassigned flags in transmitted messages, nor how an implementation should process unassigned, unknown, or unsupported flags in received messages. This document updates RFC 8231 by defining the correct behaviors.

Authors

Adrian Farrel (adrian@olddog.co.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)