IETF Logo Mail Archive

Re: [Pce] New Version Notification for draft-ietf-pce-segment-routing-policy-cp-13.txt

Mike Koldychev <mkoldych@proton.me> Wed, 17 January 2024 00:57 UTC

Return-Path: <mkoldych@proton.me>
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 8A2F3C14F6B1 for <pce@ietfa.amsl.com>; Tue, 16 Jan 2024 16:57:38 -0800 (PST)
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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=proton.me
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 HysiJsxcJQe3 for <pce@ietfa.amsl.com>; Tue, 16 Jan 2024 16:57:34 -0800 (PST)
Received: from mail-4325.protonmail.ch (mail-4325.protonmail.ch [185.70.43.25]) (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 28B61C14F68F for <pce@ietf.org>; Tue, 16 Jan 2024 16:57:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1705453051; x=1705712251; bh=yddFHnTGWCPNCFO45LNJaAyQ8phWOj/0OuglC2Uhn1g=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=e43kBXUb0/uZ5TcXlngrqYOcxyelkUmFUjEbvTlrmpm2amDwZ9Y8kGkvKTjTgCFgN UgJKIhYtkL8J2+igXpcY2HhrITelwwag0fgYqwdiDDbvZimOCpet500kH9k3zZrj2b TdsJv83L8KWIWhCUXuWMT/d478kCMrTioWMSSdsIXNG1BG/+VGtJJyMJlDwjza36I7 I42Q+LS9AYL2+98FLV50n6W4D6xHsGmeeXr73i4yTYTx4BtmUW52RtDUqzzXqq78P6 93qYPqCiZLCLYMepFdqDm3hrzpKt15C3ftDsl8X75ou8KhSZD+HEpxcKGDGwwwsT6z hArqSI9S2RM6Q==
Date: Wed, 17 Jan 2024 00:57:22 +0000
To: "pce@ietf.org" <pce@ietf.org>
From: Mike Koldychev <mkoldych@proton.me>
Message-ID: <BSdxctqZqshX3SWQgTDO8TfmlQK4ntm6Hfa1xI-CskFYGZcgnVeCcx8aHRW9HuKMoobavQryzgYmZZBkqQy64U5GyWzNqmix4CR0OGJBcPE=@proton.me>
In-Reply-To: <170545250417.45332.14942466113369417174@ietfa.amsl.com>
References: <170545250417.45332.14942466113369417174@ietfa.amsl.com>
Feedback-ID: 98235495:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/o4zgZ81ZxZi52NxK7Ijd2Xgw7Gw>
X-Mailman-Approved-At: Tue, 16 Jan 2024 20:48:40 -0800
Subject: Re: [Pce] New Version Notification for draft-ietf-pce-segment-routing-policy-cp-13.txt
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, 17 Jan 2024 01:00:17 -0000

Hi WG,

I addressed all comments that I received so far (let me know if I missed anything). 

I copied some text from [I-D.ietf-idr-segment-routing-te-policy] into Section 5.3, to avoid making a normative reference to that draft. So we should probably review it again in more detail.

Also, we need to double check Section 6.5 (https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-policy-cp-13#section-6.5), to make sure it's a good idea to create the new registry under Segment Routing instead of under PCEP.

Thanks,
Mike.


Sent with Proton Mail secure email.

On Tuesday, January 16th, 2024 at 7:48 PM, internet-drafts@ietf.org <internet-drafts@ietf.org> wrote:


> A new version of Internet-Draft
> draft-ietf-pce-segment-routing-policy-cp-13.txt has been successfully
> submitted by Mike Koldychev and posted to the
> IETF repository.
> 
> Name: draft-ietf-pce-segment-routing-policy-cp
> Revision: 13
> Title: PCEP Extensions for SR Policy Candidate Paths
> Date: 2024-01-16
> Group: pce
> Pages: 23
> URL: https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-cp-13.txt
> Status: https://datatracker.ietf.org/doc/draft-ietf-pce-segment-routing-policy-cp/
> HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-policy-cp
> Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-segment-routing-policy-cp-13
> 
> Abstract:
> 
> A Segment Routing (SR) Policy is a non-empty set of SR Candidate
> Paths, which share the same <headend, color, endpoint> tuple. SR
> 
> Policy is modeled in PCEP as an Association of one or more SR
> Candidate Paths. PCEP extensions are defined to signal additional
> attributes of an SR Policy. The mechanism is applicable to all SR
> forwarding planes (MPLS, SRv6, etc.).
> 
> 
> 
> The IETF Secretariat

v2.23.0 | Report a Bug | By Email