Re: [Pce] draft-ietf-pce-stateful-pce : clarifying the End Of Synchronization marker

[<[e-mail]>]

Hi,

Do you take this assumption from  :
"   Where:
      <path>::= <intended_path><attribute-list>[<actual_path>]

   Where:
      <intended_path> is represented by the ERO object defined in
      section 7.9 of [RFC5440]." ?


What should be the content of the ERO ? empty ? current ERO ?

Section 6.2. is more clear on the presence of ERO in PCUpd :
" There are three mandatory objects that MUST be included within each
   LSP Update Request in the PCUpd message ... If the ERO object
   is missing, the receiving PCC MUST send a PCErr message with Error-
   type=6 (Mandatory Object missing) and Error-value=9 (ERO object
   missing)."


If you consider that ERO is mandatory for PCRpt, would be good to have similar text, stating the "mandatory" stuff, the content expected (or telling that we do not care) and the behavior is case it is missing.

Thoughts ?


Best regards,

Stephane


-----Original Message-----
From: Robert Varga [mailto:[e-mail]] 
Sent: Monday, June 27, 2016 13:46
To: LITKOWSKI Stephane OBS/OINIS; [e-mail]
Subject: Re: [Pce] draft-ietf-pce-stateful-pce : clarifying the End Of Synchronization marker

On 06/23/2016 03:54 PM, [e-mail] wrote:
> Hi again,
> 
> We also found an issue when a PCC removes a LSP. It would be good to precise the objects that are mandatory, optional in this case also. 
> Some PCE implementations are waiting for an ERO in the PCRpt that removes an LSP, while some PCC does not send an ERO. 
> Would be good to clarify the procedure of LSP removal.

Hello,

I think section 6.1 on PCRpt message format covers this: ERO is mandatory in all cases. I could not find any text which would imply this should not be the case for R=1.

Bye,
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.