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

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 02 August 2023 13:21 UTC

Return-Path: <dhruv.ietf@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 6B501C15107E for <pce@ietfa.amsl.com>; Wed, 2 Aug 2023 06:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 1nJ1c4s7PI_D for <pce@ietfa.amsl.com>; Wed, 2 Aug 2023 06:21:33 -0700 (PDT)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (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 2A3AFC14CF13 for <pce@ietf.org>; Wed, 2 Aug 2023 06:21:33 -0700 (PDT)
Received: by mail-ua1-x92a.google.com with SMTP id a1e0cc1a2514c-794c5f60479so2015065241.3 for <pce@ietf.org>; Wed, 02 Aug 2023 06:21:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690982492; x=1691587292; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5B9dqoaENxYJQpcLE5sGvHDonckGOWAXd5YZgewRZXc=; b=r4wFBQGn0vG43B2NVNHrBOsB03QHqt8nr2uNfLgfpRL26imjcgzeOPdWDlgcwmeIdG 3Ebh3YzqVU92s7NRpGl0oR4uhMXceWRM99tNd3/WCh4f2CogHI1zaQRW7iTL8+pKdScf 4btz+dpDqI9OY9Smatm+7i00nGuEJ8nMrcfxHGQnjM/YcJYQwcd8nV1AVpm0SC0kTQgw Up++QNRhy+9ztDoND7ZHFq7ap95PUrdbpLEL+/DexggBRWf6T0mCo0rV2MPL9GwykmwE j9OJBgbdCKyB3UAkWYNYuOdcU9ryAoAxRpWqPG6+ysfjTTiHAgS8iYN2WjZySqx30GRv 0Lzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690982492; x=1691587292; 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=5B9dqoaENxYJQpcLE5sGvHDonckGOWAXd5YZgewRZXc=; b=hrMoY60H+PniaekS+X0rp8HK63bTRBFWI9BrMmQqeTtmz5aaGaYayKW9V/iP9HgHP4 zT/mx454zbzFksnxLsS4lnawjJqtku3wkUPLB1LTjNukTRH5/y8z+C6dqsf58M5sEUjC f5Fhtk6R/1KDAs4NVoh83vLSQs16IE91P8KTfSYp/GTgx4m/1lbim39aosya2eb1gZzs 4izroiEo9aWH5dlm234cUif2eOaJSln36BqUaWR1RPk/pwI8a5OWGxNlFNUDCw9XwJcM e3SdNhSrJNdOVys7cD3IklKD0QxvFBOpO53UDzfhw2IMtD4wipN2m/zunmhYwheNLFAP DGpw==
X-Gm-Message-State: ABy/qLZjUR1YLtuA6LnImz2KcNrhexQ9CeLAJytRawWrnnxJptKSvR6J ORb4hxll/pAK9SZnCzxoK2f99l+K9MU1d50KhPcOdID1
X-Google-Smtp-Source: APBJJlGvrUca8+DzphkceTPGnQYIbksUenl4uADOP8Wfxrlx2BZtzPEYebyxEE5EQ/QpwdJnUtE7NejTSPSJBju63oc=
X-Received: by 2002:a05:6102:1352:b0:445:942:5c81 with SMTP id j18-20020a056102135200b0044509425c81mr3057713vsl.20.1690982491574; Wed, 02 Aug 2023 06:21:31 -0700 (PDT)
MIME-Version: 1.0
References: <AM9PR06MB720494D6C48BED6FB3667F06A90BA@AM9PR06MB7204.eurprd06.prod.outlook.com>
In-Reply-To: <AM9PR06MB720494D6C48BED6FB3667F06A90BA@AM9PR06MB7204.eurprd06.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 02 Aug 2023 08:20:55 -0500
Message-ID: <CAB75xn5S6rCkiAARym9ZLJCwTDzzr9HvmdrQj=v2zuZtVhwf=g@mail.gmail.com>
To: "Marcel Reuter (External)" <marcel.reuter.external@telefonica.com>
Cc: "pce@ietf.org" <pce@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bb56570601f08aea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/4APd9gvIopm3aZnUNlvgTuKagzg>
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:21:37 -0000

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
>