[Pce] New draft draft-farrel-pce-stateful-flags-00.txt

"Adrian Farrel" <adrian@olddog.co.uk> Mon, 24 June 2019 07:04 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE00212011C for <pce@ietfa.amsl.com>; Mon, 24 Jun 2019 00:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNBoU4NT0o1O for <pce@ietfa.amsl.com>; Mon, 24 Jun 2019 00:04:14 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E803F120075 for <pce@ietf.org>; Mon, 24 Jun 2019 00:04:13 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5O74BPs029988 for <pce@ietf.org>; Mon, 24 Jun 2019 08:04:11 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5738B22042 for <pce@ietf.org>; Mon, 24 Jun 2019 08:04:11 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS id 42AEF22048 for <pce@ietf.org>; Mon, 24 Jun 2019 08:04:11 +0100 (BST)
Received: from LAPTOPK7AS653V (25.129.51.84.dyn.plus.net [84.51.129.25] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x5O74Avb024689 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <pce@ietf.org>; Mon, 24 Jun 2019 08:04:10 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
Date: Mon, 24 Jun 2019 08:04:09 +0100
Organization: Old Dog Consulting
Message-ID: <02ff01d52a5b$05b07aa0$11116fe0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdUqWvwcW1vQqGXPQV6jZH3g4hNrdg==
Content-Language: en-gb
X-Originating-IP: 84.51.129.25
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24708.005
X-TM-AS-Result: No--20.634-10.0-31-10
X-imss-scan-details: No--20.634-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24708.005
X-TMASE-Result: 10--20.634200-10.000000
X-TMASE-MatchedRID: IB58ABr55WgZnuop9luYIPvv+Ti5O6dRpQH4ogtVQP3mTInKzpSFSeph 8zS0iA+pSt06DJ1HfO63s6dv1G+jrJCGpyupaGwt2bpX2XJNwqGg8867bIwmUzt7ZjJPAVIiu/q LnMI+6lJKO4TF66UXWli1LK3HkfQMgFbe1R8iu9LM1jffIgQXhsF/N0FEhg33tXl9IxEPXOozy+ CKVy54HoS+dVXELIyz/1NGIs1OdkuFdTXKo0kYsnvf3q4k1K+qPIAXg1uNCQsiXE6jAom+xYNSz GIfkv3cXlhjI2Nz/SO84uIAE1Zlwl3vCNuHp1s1nVTWWiNp+v8FcnqPYTPUh2tEzrC9eANppFWv ufJVGzZhMCLqCj6m1LOnfFOr4f59EfMbQdPm0Fs2oY2TxKHZFwbgyOCF364/WfmMcjcXc0eoB03 wQCIXjuHzznJEWlVzdYo5RMB6BYA3KXWd30Ii3YMbH85DUZXySKrhyjgu6KGw7M6dyuYKg/cUt5 lc1lLgtT4piLWpY7p+3BndfXUhXQ==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/stZ3cV3y7F-mPNbrl9S6brHAinU>
Subject: [Pce] New draft draft-farrel-pce-stateful-flags-00.txt
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: Mon, 24 Jun 2019 07:04:16 -0000

Hi,

While reviewing draft-ietf-pce-lsp-control-request I noticed that RFC 8231 is missing clarity about how to handle the Flags field in the SRP object. RFC 8281 uses one of the Flags, but doesn't add the clarity.

This very short document seeks to add clarity so that future implementations know how set and process unknown/unassigned bits in the Flags field. It updates RFC 8231 (if published as an RFC).

Your thoughts would be helpful.

Dhruv suggests there may be other clarifications to 8231 that are needed. If so, I'd be happy to roll them all together.

Best,
Adrian

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: 24 June 2019 07:53
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: New Version Notification for draft-farrel-pce-stateful-flags-00.txt


A new version of I-D, draft-farrel-pce-stateful-flags-00.txt
has been successfully submitted by Adrian Farrel and posted to the
IETF repository.

Name:		draft-farrel-pce-stateful-flags
Revision:	00
Title:		Updated Rules for Processing Stateful PCE Request Parameters Flags
Document date:	2019-06-24
Group:		Individual Submission
Pages:		5
URL:            https://www.ietf.org/internet-drafts/draft-farrel-pce-stateful-flags-00.txt
Status:         https://datatracker.ietf.org/doc/draft-farrel-pce-stateful-flags/
Htmlized:       https://tools.ietf.org/html/draft-farrel-pce-stateful-flags-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-farrel-pce-stateful-flags


Abstract:
   Extensions to the Path Computation Element communications 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.

                                                                                  


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.

The IETF Secretariat