Re: [Pce] Mail regarding draft-ietf-pce-pcep

["Marcel Reuter (External)" <[e-mail]>]

Good morning Dhruv !

Good morning Pavan!

Thanks for taking this point and having an active discussion.

Question inline


From: Dhruv Dhody <[e-mail]>
Date: Wednesday, 2. August 2023 at 16:49
To: Vishnu Pavan Beeram <[e-mail]>
Cc: Dhruv Dhody <[e-mail]>, Marcel Reuter (External) <[e-mail]>, [e-mail] <[e-mail]>
Subject: Re: [Pce] Mail regarding draft-ietf-pce-pcep
Hi Pavan,

On Wed, Aug 2, 2023 at 8:39 AM Vishnu Pavan Beeram <[e-mail]<mailto:[e-mail]>> wrote:
Marcel, Hi!
Thanks for bringing this to the list! I interpret the text in RFC5440 regarding "one OPEN object" to just mean that the Open Message cannot carry more than one "OPEN" object.

Dhruv, Hi!
I would propose updating draft-ietf-pce-stateful-pce-vendor to explicitly allow the use of the "VENDOR-INFORMATION" object in the Open message. For example, implementations may choose to carry "versioning" information in this object during the Open message exchange (this information may or may not have any impact on the establishment of the PCEP session). As you mentioned, carrying the "VENDOR-INFORMATION" TLV in the Open Object is already allowed. I don't see any good reason to preclude the use of the "VENDOR-INFORMATION" object in the Open message.


Hmm, with that reasoning do we need to do that for all PCEP messages?
Also, is there anything that cannot be achieved via the TLV, and you would need the Object in the Open message case? Just wondering...

Thanks!
Dhruv

[MR]:
Would it be maybe more clear, if there could be a separate "VENDOR-INFORMATION" object in the Open message, so the open object stays only with standard options / TLV’s?






Regards,
-Pavan

On Wed, Aug 2, 2023 at 6:51 PM Dhruv Dhody <[e-mail]<mailto:[e-mail]>> wrote:
Hi Marcel,

Welcome, please consider joining the PCE mailing list so that we don't have to manually approve your email to the list - https://www.ietf.org/mailman/listinfo/pce

See inline...

On Wed, Aug 2, 2023 at 8:11 AM Marcel Reuter (External) <[e-mail]<mailto:[e-mail]>> wrote:
Aloha,

dear colleagues!

This is my very first E-mail ever to IETF.
So please forgive me, if I dont follow all rules.

I have a question about the RFC5440
Section 6-2


https://www.rfc-editor.org/rfc/rfc5440.html#section-6.2

The RFC says:

6.2.  Open Message

...
   The format of an Open message is as follows:

   <Open Message>::= <Common Header>
                     <OPEN>
 The Open message MUST contain exactly one OPEN object (see
   Section 7.3).


Unfortunately, Im not very firm in BNF syntax
My question here is to  understand the last sentence.

Is it allowed, just from a pure protocol standpoint,
to send in the open message
1 (one) open object
AND also
1(one)  VENDOR-INFORMATION object with the P-flag not set?


We are an operator and using PCE from one vendor and router from different other vendors and have currently some interesting discussing about that topic

RFC 7470 (https://datatracker.ietf.org/doc/rfc7470/) added a VENDOR-INFORMATION Object for PCReq and PCRep messages!
https://datatracker.ietf.org/doc/draft-ietf-pce-stateful-pce-vendor/ addes the same for PCRpt and PCUpd messages!

We have not specified the use of the Object within the Open message!
If there is a need to carry vendor specific information, then using the VENDOR-INFORMATION-TLV within the Open object is allowed.

In case they have a need for the object within the Open message, please provide a usecase and perhaps it can be added in the draft!

Hope this helps!

Thanks!
Dhruv



Thanks a lot
Marcel



________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição