Re: [Pce] WGLC for draft-ietf-pce-vn-association-05
Ramon Casellas <ramon.casellas@cttc.es> Mon, 14 March 2022 09:01 UTC
Return-Path: <ramon.casellas@cttc.es>
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 E9A3D3A0820;
Mon, 14 Mar 2022 02:01:52 -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, HTML_MESSAGE=0.001,
RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001,
SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001,
URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=cttc.es
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 1oORFe3-EPcP; Mon, 14 Mar 2022 02:01:45 -0700 (PDT)
Received: from mx01.puc.rediris.es (outbound5mad.lav.puc.rediris.es
[130.206.19.148])
(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 8BD6F3A082D;
Mon, 14 Mar 2022 02:01:43 -0700 (PDT)
Received: from leo.cttc.es (leo.cttc.es [84.88.62.208])
by mx01.puc.rediris.es with ESMTP id 22E91YvB021668-22E91YvD021668
(version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK);
Mon, 14 Mar 2022 10:01:35 +0100
Received: from localhost (localhost [127.0.0.1])
From: "Ramon Casellas" <ramon.casellas@cttc.es>
To: "'Dhruv Dhody'" <dd@dhruvdhody.com>,
<pce@ietf.org>
Cc: <draft-ietf-pce-vn-association@ietf.org>,
"'pce-chairs'" <pce-chairs@ietf.org>
References: <CAP7zK5YwLt8OY_tM9S5LPYTAcz1spgyg3TgvdzcjKBcR=CyE4A@mail.gmail.com>
<CAP7zK5Za=_5x1N3TEEEy_qCWGhPovjvxd7nRdHoG298puP1TAw@mail.gmail.com>
<CAP7zK5YwnsmadV9tZ5gaRH1Saz-JeaD37NRk_00_Q6WuveSvaA@mail.gmail.com>
In-Reply-To: <CAP7zK5YwnsmadV9tZ5gaRH1Saz-JeaD37NRk_00_Q6WuveSvaA@mail.gmail.com>
Date: Mon, 14 Mar 2022 10:01:32 +0100
Organization: CTTC
Message-ID: <00a101d83782$1a29c1d0$4e7d4570$@cttc.es>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_00A2_01D8378A.7BEEED20"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKkB1CO7W2OASCimIBQKCchm3ny/AF/b+NtAp+0PDGrBfgpcA==
Content-Language: es
X-FE-Policy-ID: 23:6:0:SYSTEM
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=cttc.es; s=DKIM;
c=relaxed/relaxed;
h=from:to:cc:references:subject:date:message-id:mime-version:content-type;
bh=ngGRUBNtw30qykbBAf9q8DEsK9ILHGBwRZ9h6P1K/SI=;
b=g3UZ+kuo4wCFqHQZsxfL0IzLmb1yvJbxGBJk8RFlJHtVaFehZR+2dWIzeyL75ys1BJVr3ybZgdz9
m00rsvAQMz1LUUOwyFGkC3WRzmzmhAFRGK9vRoz3R9Y717i4HT2cG9hD5xsQUEDHfaGZxpubgsvS
GaRbBaTeL4Ws7mjjgQHURuPHNP7mHk+teg7CQMxrmXMTTDhEcKTWTZsj3kJEDlZ5v360FCtCBqoc
wrzDPKZN5sedbvW59v7wK3BpNOx4nk6xHHWmUZpo8ax2agLsB8tlxLdDclBkXrBoImEAYVOyB9N1
lUMC7TZnffNiZYMex+vsTDxpJRdPw1IqoZ02Ig==
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/SflbeNP5WipTCN9aodsegNilBAo>
Subject: Re: [Pce] WGLC for draft-ietf-pce-vn-association-05
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, 14 Mar 2022 09:01:53 -0000
Dear all, I read the draft and I think it’s ready for publication. My only minor comment is that I was confused by the sentence “This document defines one mandatory TLV "VIRTUAL-NETWORK-TLV" and one new optional TLV "VENDOR-INFORMATION-TLV”. Later on , the reference to RFC7470 is provided. I believe the intent is to state that the latter can be used (optional) but no further guidelines are given in this regard. It is slightly redundant but it does not hurt I guess. Alternatively, it would be beneficial to state what other information can be provided in the VENDOR-INFORMATION-TLV (my personal opinion is to try to avoid those) Regards Ramon From: Pce <pce-bounces@ietf.org> On Behalf Of Dhruv Dhody Sent: lunes, 14 de marzo de 2022 9:40 To: pce@ietf.org Cc: draft-ietf-pce-vn-association@ietf.org; pce-chairs <pce-chairs@ietf.org> Subject: Re: [Pce] WGLC for draft-ietf-pce-vn-association-05 Hi WG, The WGLC ends on Wednesday 16th March. The I-D is NOT long, please review/respond to the list. Thanks! Dhruv On Tue, Feb 22, 2022 at 6:02 PM Dhruv Dhody <dd@dhruvdhody.com <mailto:dd@dhruvdhody.com> > wrote: Looks like the chairs had a "collision" in sending out the WGLC notice! Apologies! :) The only parameter that was different was when the WGLC ends, and let's pick the larger of the two dates i.e. WGLC will end on March 16, 2022. Thanks! Dhruv On Tue, Feb 22, 2022 at 5:48 PM Dhruv Dhody <dd@dhruvdhody.com <mailto:dd@dhruvdhody.com> > wrote: Hi WG, This email starts a 3-weeks working group last call for draft-ietf-pce-vn-association-05 [ <https://datatracker.ietf.org/doc/draft-ietf-pce-vn-association/> 1] to accommodate the upcoming draft submission deadline. Please indicate your support or concern for this draft. If you are opposed to the progression of the draft to RFC, please articulate your concern. If you support it, please indicate that you have read the latest version and it is ready for publication in your opinion. As always, review comments and nits are most welcome. The WG LC will end on Tuesday 15th March 2022. A general reminder to the WG to be more vocal during the last-call/adoption and help us unclog our queues :) Thanks, Dhruv & Julien [1] <https://datatracker.ietf.org/doc/draft-ietf-pce-vn-association/> https://datatracker.ietf.org/doc/draft-ietf-pce-vn-association/
- [Pce] WGLC for draft-ietf-pce-vn-association-05 Dhruv Dhody
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Dhruv Dhody
- [Pce] 答复: WGLC for draft-ietf-pce-vn-association-… Zhenghaomian
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Adrian Farrel
- [Pce] 答复: WGLC for draft-ietf-pce-vn-association-… Chengli (Cheng Li)
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Aijun Wang
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Dhruv Dhody
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Ramon Casellas
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Aihua Guo
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Ricard Vilalta
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Gyan Mishra
- [Pce] ASCII in PCEP (WAS - Re: WGLC for draft-iet… Dhruv Dhody
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Dhruv Dhody
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Dhruv Dhody
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Ramon Casellas
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Dhruv Dhody
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… chen.ran
- Re: [Pce] ASCII in PCEP (WAS - Re: WGLC for draft… Adrian Farrel
- Re: [Pce] ASCII in PCEP (WAS - Re: WGLC for draft… Dhruv Dhody
- Re: [Pce] ASCII in PCEP (WAS - Re: WGLC for draft… Ketan Talaulikar
- Re: [Pce] ASCII in PCEP (WAS - Re: WGLC for draft… Ketan Talaulikar
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… julien.meuric
- Re: [Pce] WGLC for draft-ietf-pce-vn-association-… Gyan Mishra