Re: [Pce] Review of draft-ietf-pce-stateful-pce-18

Julien Meuric <julien.meuric@orange.com> Thu, 13 April 2017 15:50 UTC

Return-Path: <julien.meuric@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 990FA1294B3; Thu, 13 Apr 2017 08:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level:
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=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 TU4-frcTDRmu; Thu, 13 Apr 2017 08:50:10 -0700 (PDT)
Received: from r-mail1.rd.orange.com (r-mail1.rd.orange.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id B67E3129455; Thu, 13 Apr 2017 08:50:09 -0700 (PDT)
Received: from r-mail1.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id CCDF6A4414A; Thu, 13 Apr 2017 17:50:08 +0200 (CEST)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by r-mail1.rd.orange.com (Postfix) with ESMTP id AB51CA44115; Thu, 13 Apr 2017 17:50:08 +0200 (CEST)
Received: from [10.193.71.173] (10.193.71.173) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.319.2; Thu, 13 Apr 2017 17:50:08 +0200
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: lionel.morand@orange.com
References: <148965756308.14230.13426886469262710918@ietfa.amsl.com> <BY2PR0201MB1910B9060DF50A938DC05D6984000@BY2PR0201MB1910.namprd02.prod.outlook.com> <2ff156bc-c198-80fe-eccf-b45b6db978df@orange.com> <BY2PR0201MB19101ABC5D53474ED6DB96B484000@BY2PR0201MB1910.namprd02.prod.outlook.com> <26612_1492014535_58EE55C7_26612_8402_1_d18aea96-35a8-419a-b7fe-9f6231f2aaaf@OPEXCLILM21.corporate.adroot.infra.ftgroup>
CC: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
From: Julien Meuric <julien.meuric@orange.com>
Organization: Orange
Message-ID: <a9e752e5-64df-3dc1-c1b9-74908b477c10@orange.com>
Date: Thu, 13 Apr 2017 17:50:08 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <26612_1492014535_58EE55C7_26612_8402_1_d18aea96-35a8-419a-b7fe-9f6231f2aaaf@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rw169rjw5neoNRNfDVArCw564-s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 15:50:12 -0000

Hi Lionel,

Thank you for following up. I think we're almost done. My answers below
as [JM2].

Julien


Apr. 12, 2017 - <lionel.morand@orange.com:

[snip]

>>> =====
>> [JM] NACK! ;-) Actually, the passive mode is advertised using the 
>> Stateful-capability-object TLV with the U bit unset, the active 
>> mode by setting the U bit.
>> 
> [LM2] "il faut être sorti de Saint-Cyr pour comprendre" as we say in
>  french :)

[JM2] Let me check with my colleague next door... ;-)

> Could be good to add something like "(as indicated by the U-bit clear
> in Stateful-capability-object)"

[JM2] ACK!

> 
>>> =====
>>> 
>>> Note that even if the update capability has not been advertised,
>>>  a PCE can still accept LSP Status Reports from a PCC and build 
>>> and maintain an up to date view of the state of the PCC's LSPs.
>>> 
>>> [LM] I don't undersand. Is it not in contradiction with
>>> 
>>> "If the PCEP Speaker on the PCE supports the extensions of this 
>>> draft but did not advertise this capability, then upon receipt of
>>> a PCRpt message from the PCC, it MUST generate a PCErr with 
>>> error- type 19 (Invalid Operation), error-value 5 (Attempted LSP
>>>  State Report if active stateful PCE capability was not 
>>> advertised) (see Section 8.5) and it SHOULD terminate the PCEP 
>>> session."
>>> 
>>> Or does it mean that there is another way than PCRpt message for
>>>  the PCC to send LSP status reports to the PCE?
>>> 
>>> Jon> ACK.  I think that the statement in the draft is bogus and
>>> I propose to delete this sentence from it.
>>> 
>>> =====
>> [JM] I do not think that the text is bogus: - case 1: no advertised
>> capability on update but advertised on report (i.e. passive
>> stateful) => no error message; - case 2: no advertised capability
>> on update nor report (i.e. stateless) => error.
> [LM2] After multiple readings and thanks to your explanation, I think
> I have understood. Am I correct saying that the PCE will accept LSP
> Status Reports from a PCC ONLY if the stateful PCE capability has
> been advertised (i.e. Stateful Capability TLV with the 'LSP Update'
> Flag cleared)? 

[JM2] Almost... but not fully! Your main sentence is true, your
parenthesis is not. The latter should be rephrased as "i.e. inclusion of
the Stateful Capability TLV". Indeed, passive (report, no update) and
active (report + update) are two possible modes within stateful, i.e. we
do not care about the 'LSP Update' flag when talking about
Report/"stateful at large".

If it is the case, is it really required to keep this
> text, as in the previous paragraph we find the conditions to
> accept/reject reports from the PCC?

[JM2] AFAIU, the sentence clarifies the fact that an error on an update
attempt does not lead to an error on the report feature.

[JM2] Side note to the (RFC?) editor, on page 11: s/this draft/this
document/