Re: [Pce] Adoption of draft-xiong-pce-lsp-flag-03

xiong.quan@zte.com.cn Mon, 22 February 2021 01:36 UTC

Return-Path: <xiong.quan@zte.com.cn>
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 0FB343A0B60 for <pce@ietfa.amsl.com>; Sun, 21 Feb 2021 17:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.885
X-Spam-Level:
X-Spam-Status: No, score=-6.885 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hmE5x8oUlOg for <pce@ietfa.amsl.com>; Sun, 21 Feb 2021 17:36:01 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE2453A0B5F for <pce@ietf.org>; Sun, 21 Feb 2021 17:35:58 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.215]) by Forcepoint Email with ESMTPS id 3BBC19EB46D0D2DC92DE for <pce@ietf.org>; Mon, 22 Feb 2021 09:35:56 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id 26B8E1F8E375E12C8BFE; Mon, 22 Feb 2021 09:35:56 +0800 (CST)
Received: from njxapp02.zte.com.cn ([10.41.132.201]) by mse-fl2.zte.com.cn with SMTP id 11M1ZrKi038142; Mon, 22 Feb 2021 09:35:53 +0800 (GMT-8) (envelope-from xiong.quan@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Mon, 22 Feb 2021 09:35:53 +0800 (CST)
Date: Mon, 22 Feb 2021 09:35:53 +0800
X-Zmail-TransId: 2afb60330a79e82d03bc
X-Mailer: Zmail v1.0
Message-ID: <202102220935531496698@zte.com.cn>
Mime-Version: 1.0
From: xiong.quan@zte.com.cn
To: adrian@olddog.co.uk, julien.meuric@orange.com
Cc: pce@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 11M1ZrKi038142
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/ornjzNDvWqdSKZIasRhxFUf-Qv8>
Subject: Re: [Pce] Adoption of draft-xiong-pce-lsp-flag-03
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 22 Feb 2021 01:36:03 -0000

Hi  Adrian and Julien,




Many thanks for your suggestions!

I fully agree with you. The two wg drafts could be viewed as two implementations to use the flag carried in LSP-EXTENDED-FLAG TLV.

I will add informative references to those two drafts if necessary.  And I also suggest those two drafts could add references to the draft-xiong-pce-lsp-flag.




Regards,

Quan






>Re: [Pce] Adoption of draft-xiong-pce-lsp-flag-03
Adrian Farrel <adrian@olddog.co.uk> Fri, 19 February 2021 16:05 UTCShow header


>Ah, that's useful. Thanks Julien.

>Makes this work more pressing.

>Informative references to those two drafts would help focus the reviewer's mind and might be handy when this draft overtakes those other two documents and goes to the IESG.

>Cheers,
>Adrian

-----Original Message-----
From: julien.meuric@orange.com <julien.meuric@orange.com> Sent: 19 February 2021 14:38
To: adrian@olddog.co.ukCc: pce@ietf.orgSubject: Re: [Pce] Adoption of draft-xiong-pce-lsp-flag-03

>Hi Adrian,

>Thank you for your feedback.

>If evidence is needed, how about binding label?https://tools.ietf.org/html/draft-ietf-pce-binding-label-sid-06#section-11.2Note it's also reused inhttps://tools.ietf.org/html/draft-ietf-pce-sr-path-segment-03#section-4.2Have a nice week-end,

>Julien


On 18/02/2021 16:57, Adrian Farrel wrote:
> Thanks to the authors for cleaning this up a lot since last time.
>
> I don't object to adoption. Would be nice to have evidence of someone
> needing a bit now, but by the time this becomes an RFC it is reasonably
> possible.
>
> Adrian
>
> -----Original Message-----
> From: Pce <pce-bounces@ietf.org> On Behalf Of Dhruv Dhody
> Sent: 01 February 2021 17:48
>
> Hi WG,
>
> This email begins the WG adoption poll for draft-xiong-pce-lsp-flag-03.
>
> https://datatracker.ietf.org/doc/html/draft-xiong-pce-lsp-flag-03>
> This is a small draft that extends the flags in the LSP Objects by
> defining a new LSP-EXTENDED-FLAG TLV. Note that the existing
> sub-registry "LSP Object Flag Field" is almost fully assigned.
>
> https://www.iana.org/assignments/pcep/pcep.xhtml#lsp-object-flag-field>
> Should this draft be adopted by the PCE WG? Please state your reasons
> - Why / Why not? What needs to be fixed before or after adoption? Are
> you willing to work on this draft? Review comments should be posted to
> the list.
>
> Please respond by Monday 15th Feb.
>
> Thanks!
> Dhruv & Julien
>
> _______________________________________________
> 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>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.