IETF Logo Mail Archive

Re: [Pce] WGLC for draft-ietf-pce-segment-routing-policy-cp-12

Boris Khasanov <bhassanov@yandex-team.ru> Tue, 23 January 2024 10:17 UTC

Return-Path: <bhassanov@yandex-team.ru>
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 34908C14F703; Tue, 23 Jan 2024 02:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.628
X-Spam-Level:
X-Spam-Status: No, score=-1.628 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, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yandex-team.ru
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 mIJJ-H6A3Jc2; Tue, 23 Jan 2024 02:17:11 -0800 (PST)
Received: from forwardcorp1c.mail.yandex.net (forwardcorp1c.mail.yandex.net [178.154.239.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 C9714C151062; Tue, 23 Jan 2024 02:17:08 -0800 (PST)
Received: from mail-nwsmtp-mxback-corp-main-58.myt.yp-c.yandex.net (mail-nwsmtp-mxback-corp-main-58.myt.yp-c.yandex.net [IPv6:2a02:6b8:c12:62a5:0:640:ee1b:0]) by forwardcorp1c.mail.yandex.net (Yandex) with ESMTPS id 4ACEE608D2; Tue, 23 Jan 2024 13:17:06 +0300 (MSK)
Received: from mail.yandex-team.ru (2a02:6b8:c12:6299:0:640:b0ce:0 [2a02:6b8:c12:6299:0:640:b0ce:0]) by mail-nwsmtp-mxback-corp-main-58.myt.yp-c.yandex.net (mxbackcorp/Yandex) with HTTP id PGPt4S0Io8c0-P9PBRUdV; Tue, 23 Jan 2024 13:17:06 +0300
X-Yandex-Fwd: 2
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex-team.ru; s=default; t=1706005026; bh=iR9K//tAETNRm2vlgkECKm/b8Tm3QsCwGUWSlDyKhn4=; h=Message-Id:In-Reply-To:Cc:References:To:Date:Subject:From; b=pEP0FXWkj5+WBlSXUmX+n1r9PGSGSXgcsyD9x/dlTta47oFiL5UsVDHTpqbNhGCxL sbLMKSOpQvgTCajeGORUCG39LOpP6rvojwVSQBFOJmmouDjXhusKZn2u6+rapfRiT2 lZUa2xwcQ70EoSAtdWlGgKXUJmjOcx5121glRefc=
Authentication-Results: mail-nwsmtp-mxback-corp-main-58.myt.yp-c.yandex.net; dkim=pass header.i=@yandex-team.ru
Received: from mejgq6zk2vrbiq2h.sas.yp-c.yandex.net (mejgq6zk2vrbiq2h.sas.yp-c.yandex.net [2a02:6b8:c08:570b:0:640:5c12:0]) by mail-nwsmtp-mxback-corp-main-62.sas.yp-c.yandex.net (mxbackcorp/Yandex) with HTTP id EEP0KP0IpKo0-gH4dBvZK for <bhassanov@yandex-team.ru>; Tue, 23 Jan 2024 13:16:56 +0300
Received: by mejgq6zk2vrbiq2h.sas.yp-c.yandex.net with HTTP; Tue, 23 Jan 2024 13:16:56 +0300
From: Boris Khasanov <bhassanov@yandex-team.ru>
To: Dhruv Dhody <dd@dhruvdhody.com>, "pce@ietf.org" <pce@ietf.org>
Cc: pce-chairs <pce-chairs@ietf.org>, "draft-ietf-pce-segment-routing-policy-cp@ietf.org" <draft-ietf-pce-segment-routing-policy-cp@ietf.org>
In-Reply-To: <CAP7zK5a82T3itOURWipyO0YaC4XgmkRwxDeyE4edZHmMCmX0Bg@mail.gmail.com>
References: <CAP7zK5a82T3itOURWipyO0YaC4XgmkRwxDeyE4edZHmMCmX0Bg@mail.gmail.com>
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Tue, 23 Jan 2024 13:17:06 +0300
Message-Id: <230141706003864@mail.yandex-team.ru>
Content-Transfer-Encoding: base64
Content-Type: text/html; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8VP9vYlvnDoVguFYpOckcuNU0i0>
Subject: Re: [Pce] WGLC for draft-ietf-pce-segment-routing-policy-cp-12
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: Tue, 23 Jan 2024 10:17:16 -0000

Hi all,
Sorry for being late, I fully support the adoption too.
 
Some small comments for the better understanding:
1) Section 4.1 Association parameters
1.1) Association ID which should be set to 1, will it never be used and should be kept as '1" ?
 
1.2) This sentence sounds confusing, IMO:
"If the PCC receives a PCInit message with the Association Source set not to the headend IP but to some globally unique IP address that the headend owns, then the PCC SHOULD accept the PCInit message and create the SRPA with the Association Source that was sent in the PCInit message."
 
Why do we need such dualism here? I mean this other IP-address which should be  delivered to PCE in advance etc. Complicates an implementation IMO.
 
1.3) Also not exactly clear how these parameters can  help to escape "a race condition when multiple PCEP speakers want to create the same SR Policy at the same time." Can you please clarify?
2) Can you please add into  section 7 (Implementation status)  some info/plans about  the Invalidation TLV. It is very important mechanism in practice.
 
Thank you.
 
SY,
Boris
 
 
 
 
 
08.01.2024, 13:29, "Dhruv Dhody" <dd@dhruvdhody.com>:
Hi WG,

This email starts a 2-weeks working group last call for draft-ietf-pce-segment-routing-policy-cp-12.
 
https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-policy-cp/" rel="noopener noreferrer nofollow">https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-policy-cp/  

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 Monday 22nd January 2024.

A general reminder to the WG to be more vocal during the last-call/adoption.

Thanks,
Dhruv & Julien

 
 
 
,

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce" rel="noopener noreferrer nofollow">https://www.ietf.org/mailman/listinfo/pce

v2.23.0 | Report a Bug | By Email