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

Gyan Mishra <hayabusagsm@gmail.com> Thu, 30 March 2023 04:20 UTC

Return-Path: <hayabusagsm@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 77470C1522DA for <idr@ietfa.amsl.com>; Wed, 29 Mar 2023 21:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.084
X-Spam-Level:
X-Spam-Status: No, score=-7.084 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=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=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 niDoGlpP94hv for <idr@ietfa.amsl.com>; Wed, 29 Mar 2023 21:20:07 -0700 (PDT)
Received: from mail-qv1-xf31.google.com (mail-qv1-xf31.google.com [IPv6:2607:f8b0:4864:20::f31]) (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 3A62EC1522BE for <idr@ietf.org>; Wed, 29 Mar 2023 21:20:07 -0700 (PDT)
Received: by mail-qv1-xf31.google.com with SMTP id jl13so13223994qvb.10 for <idr@ietf.org>; Wed, 29 Mar 2023 21:20:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680150006; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5y4k2A/GOoC6npaKpOSq9pBmQM5VV/Fhd+fLWe/SxpA=; b=n9KfmZLY4MveOvc6R7njWXy6xnPJhHdrdh7Nqh/4iBZpvg+IlqFlRFfInfVSQVq7qe uNeu7u+0g/peLQvH9UCinqlb/qTeUBbNr3GMp/YXQvU1Iz3CxmfVyn3AiW8vMgO9cDqk zVD18CjAWJaDPSGYw/0UeOVRbRVsiTsm6uGJx6eCHPW8PzTKjxnDX+aSGvRAPdGPhcmz n8986fdeAnnRX6EM7tT7K7nigqb/WFvFbyig4DD4ZyiUvVq5Lnprb0wpAo/eQaz7Psik bOmjnojz0bPNF76la5ro/ZSyHtrDR+ZeZiPYsLztFaad/8aEJgF5Q61h9NSpau8nhNFo yCuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680150006; 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=5y4k2A/GOoC6npaKpOSq9pBmQM5VV/Fhd+fLWe/SxpA=; b=c4ssmZSx4RWN9DQuDhwWxBGZiN4kOLelm4EDoVcgjRmsnLKWfzhZlGBGVO/kd6+DDf W8rxeub675b7jKVK2tYCE9OlmRWKcRp8oyrfaOYG4ASKNzgK96ibj479bF5WTfj4Ldct L6gNAZDmD8JeGteSZkYOAxQXpkSry8muWjteYmcPOM2ZAv6uGOo7DBtUukJiWUNqduyG ReK6/1l06halDnJNX1o8qh6X00X3vnf33k/ovT+PK8yjI9T8Voc/mzpHskSIk8pxMeaR +kytYRx6drXKkanLjFooudbCqy5B+hcwr9SSjA0uBrK9dWJpy3ByNn6Z51rYrts7iY4O bW8A==
X-Gm-Message-State: AAQBX9czmVX+/kR72bPxd/4yCPyT7EQZfGIHVzDIvcFLu1Q93tmc56nF JbQmOWcVZRyStwDMyV56wR49iKBO+2DgvrOWCmAdJg1X
X-Google-Smtp-Source: AKy350bub6y9o/UoyiYb87DcjNe7Ioj+S+KK5ux3jRxsFVhy+z/yUkov+WXwvVlEnsizl1tYSbSteAJP6jPbyUxgmMY=
X-Received: by 2002:a05:6214:1863:b0:56e:ace8:866f with SMTP id eh3-20020a056214186300b0056eace8866fmr4247682qvb.3.1680150006123; Wed, 29 Mar 2023 21:20:06 -0700 (PDT)
MIME-Version: 1.0
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Thu, 30 Mar 2023 00:19:55 -0400
Message-ID: <CABNhwV36n-GwyT7niVFkj5jrZYho9ENbrS9ogo3HU79AjFm8-g@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Cc: "idr@ietf.org" <idr@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000048d0a605f81668a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/R6q4-IQGk2SWaxpVBY34uCQV4DU>
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: Thu, 30 Mar 2023 04:20:11 -0000

I support WG adoption.

For operators deploying network slicing, being able to perform network
slicing in the context of an IETF network slice using NRP definition would
be valuable for operators for all use cases such as 5G and Enhanced VPN
network slicing or any other use case.

Since SR stateless intent based steering is the primary operator  tool for
network slicing I believe any TEAS network slicing specification concepts
 that are developed should be funneled back to IDR and Spring to bring
those TEAS developed ideas to fruition so they can be realized by operators.

Dear authors

SR policy per RFC 9256 can be instantiated via local configuration, BGP
using SR-TE SAFI 73 or PCEP.

With the SR policy extension would all three method now support NRP sub
TLV.  Maybe some verbiage surrounding that should be added to the draft.

SR Policy using SR Algo link coloring is one of the key use cases for
network slicing using latency metic constraint.

How would the interaction work between the NRP sub TLV and SR Algo link
coloring and then the RFC 9012 color extended community VPN service route
egress PE signaling coloring  to SR source node intent SR policy color
mapping to instantiate the steered path work.

Thank you

Gyan

On Tue, Feb 28, 2023 at 11:49 PM 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
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*