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) <
marcel.reuter.exter...@telefonica.com> 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
>
> :-)
>
>
> VG
> Marcel Reuter
>
> --
> Marcel Reuter
> Im Auftrag der Telefónica Germany GmbH & Co. OHG
> Überseering 33a
> 22297 Hamburg
>
> marcel.reuter.exter...@telefonica.com
>
> ________________________________
>
> 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
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

Reply via email to