Re: [Pce] Whither Stateless PCE?

[<[e-mail]>]

Yes, exactly.
Depending on the exact level of detail we want from the PCC, we may need possibly three different states :
- intended (configuration => may be partially/totally received from PCE)
- effective (configuration => what has been really taken into account by PCC in term of config) => this one may be necessary in case some configuration option may be sent by the PCE but not taken into account by PCC.
- operational (ops state => what is the current state of the computed path)

-----Original Message-----
From: Robert Varga [mailto:[e-mail]] 
Sent: Monday, May 09, 2016 15:18
To: LITKOWSKI Stephane OBS/OINIS; Zhangxian (Xian); Aissaoui, Mustapha (Nokia - CA); DUGEON Olivier IMT/OLN
Cc: [e-mail]
Subject: Re: [Pce] Whither Stateless PCE?

On 05/09/2016 03:06 PM, [e-mail] wrote:
> Hi Xian,
> 
>  
> 
> Regarding the METRIC object, the issue is not having the Object in the 
> PCRpt (which already works). The issue is that the metric object will 
> reflect the operational state of the LSP rather than it's configuration.
> 
> The best example may be :
> 
> PCC is configured to use IGP metric with a cost bound to 20.
> 
> In the PCRpt, it will send in the METRIC object the operational values 
> of the LSP, so the metric may be anything below 20 (e.g. 14) and B=0 
> and we will not have any information about the cost boundary 
> constraint, so the PCE will not be able to fullfill this constraint 
> when computing the path for the PCC.

Hello,

This looks like the 'ERO/RRO in PCRpt' discussion we have had with Julien. While the ERO/RRO split makes this a non-issue in that case, we seem to lack a general mechanism to discern 'intended' and 'effective'
state, notably in the case when the PCE needs to recover the intended state from the PCC.

Does that sum up the problem?

Thanks,
Robert


_________________________________________________________________________________________________________________________

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.