Re: [Pce] NULL PCUpdate message

2014-10-29 Thread Dhruv Dhody
...@ietf.org] On Behalf Of Dhruv Dhody Sent: 10 October 2014 10:17 To: Cyril Margaria; Ramana Yarlagadda Cc: pce@ietf.org Subject: Re: [Pce] NULL PCUpdate message Hi Cyril, Ramana, I agree with this, during returning delegation – On the receiving side, we ignore the content. On the sending side, we put

Re: [Pce] NULL PCUpdate message

2014-10-09 Thread Dhruv Dhody
send an empty ERO object with no sub-objects in PCUpd message. What does the WG think about this? Regards, Dhruv From: Pce [mailto:pce-boun...@ietf.org] On Behalf Of Cyril Margaria Sent: 10 October 2014 00:34 To: Ramana Yarlagadda Cc: pce@ietf.org Subject: Re: [Pce] NULL PCUpdate message Hi

Re: [Pce] NULL PCUpdate message

2014-10-09 Thread Cyril Margaria
Hi, >From the definition, an empty PCUpd must contain an ERO, I think the question boils down to having an empty ERO or an ERO that mirrors the last ERO received. This is the only required parameter. I would propose the following text to clarify: Section 5.5.3: Add: Upon reception of a PCUpd wit

[Pce] NULL PCUpdate message

2014-10-09 Thread Ramana Yarlagadda
Hi All, I have a questions on sending the PCUpdate message to delegate an LSP from PCE to PCC. Can somebody please help me here to understand the PCUpdate message For delegating an LSP back to PCC. Re-delegation section talks about empty message but the PCUpdate request message definition Says t