Re: [Pce] Shepherd Review of draft-farrel-pce-stateful-flags-01

<> Mon, 23 September 2019 08:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 42D32120128 for <>; Mon, 23 Sep 2019 01:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.29
X-Spam-Status: No, score=-0.29 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kKfa25ImObKj for <>; Mon, 23 Sep 2019 01:20:46 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F006F120121 for <>; Mon, 23 Sep 2019 01:20:45 -0700 (PDT)
Received: from (unknown [xx.xx.xx.11]) by (ESMTP service) with ESMTP id 46cHMJ5kcSz2yGt; Mon, 23 Sep 2019 10:20:44 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.57]) by (ESMTP service) with ESMTP id 46cHMJ4dbCzCqk4; Mon, 23 Sep 2019 10:20:44 +0200 (CEST)
Received: from [] ( by OPEXCAUBM6D.corporate.adroot.infra.ftgroup ( with Microsoft SMTP Server (TLS) id 14.3.468.0; Mon, 23 Sep 2019 10:20:44 +0200
To: <>, 'Hariharan Ananthakrishnan' <>
CC: <>
References: <> <037901d57182$abe9c890$03bd59b0$>
From: <>
Organization: Orange
Message-ID: <>
Date: Mon, 23 Sep 2019 10:20:43 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <037901d57182$abe9c890$03bd59b0$>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Originating-IP: []
Archived-At: <>
Subject: Re: [Pce] Shepherd Review of draft-farrel-pce-stateful-flags-01
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Sep 2019 08:20:47 -0000


IMHO, including the new reference in the registry could be valuable and
makes no harm. And now that the text is written, why leaving it out?

Thanks Hari and Adrian,


On 22/09/2019 22:16, Adrian Farrel wrote:
> Hi,
> I’m willing to be guided here.
> I don’t think the new draft makes any changes to how a code point seen in in the wild should be interpreted.
> And the “updates” relationship will be in place.
> But if people think it is valuable we could have…
> IANA maintains a registry called the “Path Computation Element Protocol (PCEP) Numbers” registry with a subregistry called " SRP Object Flag Field". IANA is requested to update the Reference in that subregistry to include a reference to this document in addition to [RFC8281].
> Best,
> Adrian
>> This document is well written and clear. Thanks for the update. Please find below
>> my comments on draft-farrel-pce-stateful-flags-01.
>> OLD:
>> 8. IANA Considerations
>> This document makes no requests for IANA action
>> NEW:
>> The current IANA for this object has reference to "RFC8281" (
>> assignments/pcep/pcep.xhtml#srp-object-flag-field) Dont we want that refer to this
>> new draft since we have updated the text ?
> _______________________________________________
> Pce mailing list


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.