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

Vishnu Pavan Beeram <vishnupavan@gmail.com> Wed, 02 August 2023 13:38 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6EAAC1522CD for <pce@ietfa.amsl.com>; Wed, 2 Aug 2023 06:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXvAlhHZy9pm for <pce@ietfa.amsl.com>; Wed, 2 Aug 2023 06:38:36 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA8EC1522D3 for <pce@ietf.org>; Wed, 2 Aug 2023 06:38:35 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id 4fb4d7f45d1cf-51cff235226so2145394a12.0 for <pce@ietf.org>; Wed, 02 Aug 2023 06:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690983514; x=1691588314; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iybyAbMhIR1FfUve8Vd5h3KsDgfuOawQRPiRFPHtcSM=; b=doUuDoOZXpCB7mSytZQFjHlN69yBLUSOLCZVEDmyn6tV0afDmMPWLpjTOqHzK4mOti H/op9yxHKhagFx1s5A2eEwxRH377RuvUfevzq2pfhORunVNCu0CMmI9VNaSk9nYyT8oN 5HV/jbO/eaWQYCHuZESK/7ygM/AkWNMtH5HUsg8z0IQMwhmNdLiGd+z7vI/XmHoBr2lv vv435qi+8lSNRR/laf7hP5NxNOikEnCtCocnvdj0TLB6Xod1bln9QdqWGM4zrArN3x5D 5QAL8Iw7ciPX9KIN5ZjKPTbG4qOuZJARHo8p30o6Fx61TGCNJniG4FlrNWv2S+bAZJnj H+/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690983514; x=1691588314; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iybyAbMhIR1FfUve8Vd5h3KsDgfuOawQRPiRFPHtcSM=; b=JYL8C4ewtbwR+6v9z8grBgwBb5kOr1LTogLSNdtzJIqiZbtds3PbhErKh/08DvAo9k cY9pq3r+0k3QNPhpILiWu/e1QmVpU5Zg02vPcYJl1lnXjIkcw2wgAbE9k+FMLPuQR3uT 1LLzUKe8d1Mqf9KQNw03iNe8IHpRUG5rJgUQxP36J8ZesveJAvrSTqRB5A6nfH/dVdmw RtfwqKscY+deGcuvMcqCicGPabfeUdexlsyjJxDH2M6C6mLbqflZGdRz3GzJmshBxaL2 jfMFzdA2fe943sKU5aSKkISqYl5YdY1FyUv6KcYbCcYnDci787BkdQhAnKb+DQNAee+T jGWA==
X-Gm-Message-State: ABy/qLZYSlE5V3EpS26ARbrNaS2Z0T1Qfu7clOMK+rWNaWSKTiWS3PEQ tOBbtpx1YNiiZ69tXWTOoKWBYJXGN7Yjb++RWYI=
X-Google-Smtp-Source: APBJJlGbqOohQwXcTzlXSOqlUfPXMt4kfBbqUWm2Z9TjWTbkG/EceQrnFIHAl8eixEXM2686HF0xfw59JH1eVEyHaSk=
X-Received: by 2002:a05:6402:50c8:b0:51e:5206:d69e with SMTP id h8-20020a05640250c800b0051e5206d69emr6060395edb.10.1690983513822; Wed, 02 Aug 2023 06:38:33 -0700 (PDT)
MIME-Version: 1.0
References: <AM9PR06MB720494D6C48BED6FB3667F06A90BA@AM9PR06MB7204.eurprd06.prod.outlook.com> <CAB75xn5S6rCkiAARym9ZLJCwTDzzr9HvmdrQj=v2zuZtVhwf=g@mail.gmail.com>
In-Reply-To: <CAB75xn5S6rCkiAARym9ZLJCwTDzzr9HvmdrQj=v2zuZtVhwf=g@mail.gmail.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Wed, 02 Aug 2023 19:08:22 +0530
Message-ID: <CA+YzgTtxmLQ_5twdzoHyuAuMEWOtfRr7+qc4RF8c1bECgirv9A@mail.gmail.com>
To: Dhruv Dhody <dhruv.ietf@gmail.com>
Cc: "Marcel Reuter (External)" <marcel.reuter.external@telefonica.com>, "pce@ietf.org" <pce@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a999860601f0c7a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/wBH2k7FJGtPa8hUcnlu3mR06PnM>
Subject: Re: [Pce] Mail regarding draft-ietf-pce-pcep
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Aug 2023 13:38:39 -0000

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.

Regards,
-Pavan

On Wed, Aug 2, 2023 at 6:51 PM Dhruv Dhody <dhruv.ietf@gmail.com> 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) <
> marcel.reuter.external@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.external@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
>