Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 05 April 2023 06:46 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89521C14CE38 for <idr@ietfa.amsl.com>; Tue, 4 Apr 2023 23:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, 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 SH7-1zFQliYf for <idr@ietfa.amsl.com>; Tue, 4 Apr 2023 23:46:28 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 19B27C14CF1B for <idr@ietf.org>; Tue, 4 Apr 2023 23:46:28 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id h15so30616937vsh.0 for <idr@ietf.org>; Tue, 04 Apr 2023 23:46:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680677187; x=1683269187; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mSkOpXFCQbPECdAmrPMuW1kDk4y+L0koWyAtqakOuX4=; b=AQfYS5PmzvcISxJcuGw7LqYNuzgH0qs82EeeK9WZ8CkMbg2ZLLKcp9FfIdKK5TqtBe w0gxkqWHvDxQ8nHTZkbrjxovu/wuHjvtpmz5G/+Qgi8BtjTqIh014zMVwa+ZUHw/nNGc g2mgO7RGQ0+rjAhv7sFWLLG+OV8y4YhkmrBA64LbKxfTdjxMPw280YAjrmgN6SR6dUzc D7/lfZUmDj7AgU6hmaazZW7T4gN503sndGBkqwAIC668PiDLcBcEhV6oY2mHLEhO+Cg+ OHLU9FQtOz6i40GuZtFf7/bkaf/cvAwgmWjsUl9hnkk4VaRKv7DR5431CLl0FojCBtCo CZIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680677187; x=1683269187; 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=mSkOpXFCQbPECdAmrPMuW1kDk4y+L0koWyAtqakOuX4=; b=AOrjz0WpN1X5J9v03FlaycAhUSYDusybUgYVzFOshphHka2E3H3OX0ehksIPzN+gXq ryIOQY2mHaTb8tLAGrQQjgWtitlvPZyz20ywwX2brIjEbjbgaJ2ZoAiMgcN7bpGKjcVr xu5912HRpgyjZ5hD6VrxFhajCPnsARxkUMb2dw560oOv6WR1LyOtiBR3vCRaxqE1Vab6 sCov9s3y+dRR6pFm6gDvx3KRsAHEZ7xqxiNid2JIPdGZmpvJ6gwOsIHJ1A9hk8Tj9xgt Ct7HE9fiCvF0w+Cm43ehCmCkH6SuRHqw8OEh5v5iEZAkJoUHEfqcgmU5WEsNOdOujqXm XWDQ==
X-Gm-Message-State: AAQBX9fmdASxe5K/bu8JScTVlT/mgzA+jvcvUHq+w/mUbD13BRGiGvxE QdDq4AhCixpbsCUVknX9TQZmU5Hncqshd/iZvZuBo+xP
X-Google-Smtp-Source: AKy350amOgZXYMYGt3ZeZpLRNsu56lWUjidlTrNBSldh9ef+JjIqg038BOpgKs7r9dyZSh/htVyxPGlvyp0tEgy2W+o=
X-Received: by 2002:a67:d20f:0:b0:426:392a:92bc with SMTP id y15-20020a67d20f000000b00426392a92bcmr4097469vsi.1.1680677186937; Tue, 04 Apr 2023 23:46:26 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 05 Apr 2023 12:15:50 +0530
Message-ID: <CAB75xn70k8xE3QaNKqHkHn=22gD0NEG65o1uooB6puNx4xWB6A@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b5ae5605f8912645"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/700NcPMHDIAHFQkPw538fWD_ON0>
Subject: Re: [Idr] Adoption call for - draft-dong-idr-sr-policy-nrp-02 (3/1 to 3/14)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2023 06:46:32 -0000

Hi Sue,

Since the WG adoption call is not closed yet, let me slip in my review...

I support WG adoption, but I have some comments...

1) The I-D states that the candidate paths in one SR Policy SHOULD be
associated with the same NRP. The I-D should explicitly state what happens
if it is not! (Also see (4))
2) The security consideration needs to add reference to relevant documents
that describe the security risks of NRP-ID in the dataplane as well as
incorrect association of NRP in the control plane.
3) Please remove the codepoint in the IANA consideration, use TBD!
4) Is NRP a property of SR Policy or the Candidate path? It feels it is
used interchangeably. I suggest being specific and consistent.
5) We could also lay out explicitly, what does it mean to not have an NRP
sub-TLV.
6) NRP ID in section 2, you should also state that it is unsigned
7) Section 3, i am not sure about the SHOULD in para 1, why not MUST?

Thanks!
Dhruv


On Wed, Mar 1, 2023 at 10:19 AM Susan Hares <shares@ndzh.com> wrote:

> This begins a 2 week WG adoption call for
>
> draft-dong-idr-sr-policy-nrp
>
> https://datatracker.ietf.org/doc/draft-dong-idr-sr-policy-nrp/
>
>
>
> Each of the authors should respond to this message with
>
> an email indicating if they know of any IPR regarding this draft.
>
>
>
> The draft specifies an extension to BGP SR policy to
>
> Specify the NRP (network partition resources) that
>
> Than an SR Policy candidate path is associated with.
>
>
>
> In your discussion consider if this is a useful addition to the
>
> SR Policy candidate path.
>
>
>
> Cheerily, Sue
>
>
>
> ===========
>
> Full description from the draft
>
>
>
>   Segment Routing (SR) Policy is a set of candidate paths, each
>
>    consisting of one or more segment lists and the associated
>
>    information.  The header of a packet steered in an SR Policy is
>
>    augmented with an ordered list of segments associated with that SR
>
>    Policy.  A Network Resource Partition (NRP) is a subset of network
>
>    resources allocated in the underlay network which can be used to
>
>    support one or a group of IETF network slice services.
>
>
>
>    In networks where there are multiple NRPs, an SR Policy may be
>
>    associated with a particular NRP.  The association between SR Policy
>
>    and NRP needs to be specified, so that for service traffic which is
>
>    steered into the SR Policy, the header of the packets can be
>
>    augmented with the information associated with the NRP.  An SR Policy
>
>    candidate path can be distributed using BGP SR Policy.  This document
>
>    defines the extensions to BGP SR policy to specify the NRP which the
>
>    SR Policy candidate path is associated with.
>
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>