[Pce] RFC 8786 on Updated Rules for Processing Stateful PCE Request Parameters Flags

rfc-editor@rfc-editor.org Sun, 31 May 2020 18:59 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 59F703A0BB1; Sun, 31 May 2020 11:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id eXOoaKiIl_3n; Sun, 31 May 2020 11:59:34 -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 2E68D3A0BAE; Sun, 31 May 2020 11:59:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5564FF406D8; Sun, 31 May 2020 11:59:18 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pce@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200531185918.5564FF406D8@rfc-editor.org>
Date: Sun, 31 May 2020 11:59:18 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/DI8uaWlaLWx-wbYmW9BUE2kOjbA>
Subject: [Pce] =?utf-8?q?RFC_8786_on_Updated_Rules_for_Processing_Statefu?= =?utf-8?q?l_PCE_Request_Parameters_Flags?=
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 31 May 2020 18:59:35 -0000

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

        RFC 8786

        Title:      Updated Rules for Processing Stateful 
                    PCE Request Parameters Flags 
        Author:     A. Farrel
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2020
        Mailbox:    adrian@olddog.co.uk
        Pages:      6
        Updates:    RFC 8231

        I-D Tag:    draft-ietf-pce-stateful-flags-01.txt

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

        DOI:        10.17487/RFC8786

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.

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