Re: [Teas] WG adoption poll: draft-bestbar-teas-ns-packet-08

Vishnu Pavan Beeram <vishnupavan@gmail.com> Thu, 24 February 2022 15:03 UTC

Return-Path: <vishnupavan@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE163A0896; Thu, 24 Feb 2022 07:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-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=gmail.com
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 JyF3dObL5Y0F; Thu, 24 Feb 2022 07:03:47 -0800 (PST)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 161EA3A08AB; Thu, 24 Feb 2022 07:03:47 -0800 (PST)
Received: by mail-io1-xd29.google.com with SMTP id f14so3026805ioz.1; Thu, 24 Feb 2022 07:03:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=L2c6Wtfl7O0CJzm4IiNS60l+x7O3F/WgtdmQm+xWf3o=; b=IL8d5hPPG3SVrNzHfvHCI0B545IbiI95DGbqUhxAsmD+/lI6qyLs0hczUI2oAuCqS9 lhMTD3OlGOKU8XbG3OicI+tgPk6Z4qkpjbgxUQcRPrxyZRNlCZOi0euhD+UELouHi6cQ nZTYemkji1kaEiAjD1Hxrgn5f7mwXK8wNYP0dSeQrNcq/Ow4n59cJcU5TJIoCcRp0WPM c+0eRu1hxlgK+NhVV7MTqgq8xmDYNud8XhoPlCZdpLryZdnznm4UFwHPtFwB68tC9q4g 228v7A4hWCBRh07OPZDx+JbXkwmoilF5W4/vfNgxXFfTBCkvse2lufTsUWr9YCJBXgce gS0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=L2c6Wtfl7O0CJzm4IiNS60l+x7O3F/WgtdmQm+xWf3o=; b=X948/mxnE8F737zENUjUUthiu1LAOW4QNzvX3b01EqKbwQriXL/vd85IYmHxidhs1c FirUjCLB+szqyCn21NCFjh+O+DJmRNyuGkAuWN0upY6zMwAEO5NG4FiaAkCqMNrGJAmZ KeZsjLkk+WQBFEZmnJPbMAHVJ9mLN/3phmmphWUTqPWGB44wm6saimh5ACAArM+wvy++ D72/0YMKj+qYhe45KgEHjzvRQPYY0hgsK0UZqR8VPhLbSfz6OGQFz+oslJG0uCTuT+pl WsDnGcC5rxiORCxBzE7KeBRmHV0AyDPQ8lPAhKssngNVl0UETLtUGK83Vu3TK9oHCVo5 E/lg==
X-Gm-Message-State: AOAM532+7sAMHFcGUxUtBDTpDMKLMGzCV8yNxsV8Hg/SWo1mXpMMq81P DD4CL67gj12SknC2UuETAI4pg160/hcpOUi2+uw=
X-Google-Smtp-Source: ABdhPJz6mSEDHKa9VejJ7Bdr7vh4YjXH7i0Rf4o7wWnDXEGjYY1MqK/ZUR1nOualQ5iiIZtiSqLIn9ea1u430rv/slY=
X-Received: by 2002:a05:6638:8c:b0:314:418e:d739 with SMTP id v12-20020a056638008c00b00314418ed739mr2391703jao.98.1645715025696; Thu, 24 Feb 2022 07:03:45 -0800 (PST)
MIME-Version: 1.0
References: <54263b17-4c97-8fcc-672c-146bed709b01@labn.net> <TY2PR01MB3562D0221712D45F1D6AB949903D9@TY2PR01MB3562.jpnprd01.prod.outlook.com>
In-Reply-To: <TY2PR01MB3562D0221712D45F1D6AB949903D9@TY2PR01MB3562.jpnprd01.prod.outlook.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Thu, 24 Feb 2022 09:03:34 -0600
Message-ID: <CA+YzgTsmpyewHD0K8DdnVYmnyeoE4jB_F1_yTgMo+wQBe1T0WQ@mail.gmail.com>
To: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
Cc: Lou Berger <lberger@labn.net>, TEAS WG <teas@ietf.org>, TEAS WG Chairs <teas-chairs@ietf.org>, "draft-bestbar-teas-ns-packet@ietf.org" <draft-bestbar-teas-ns-packet@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000821df805d8c4e32d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/eoBzZQTG5WH344NlLPXhKgrIiLk>
Subject: Re: [Teas] WG adoption poll: draft-bestbar-teas-ns-packet-08
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2022 15:03:53 -0000

Kenichi, Hi!



Thanks for the review! This draft discusses the use of Network Resource
Partition (NRP) to support a Slice-Flow Aggregate. The NRP identifier is
unique within an NRP domain and is meant for use in the control/management
plane to identify the resources associated with the NRP (this should be the
identifier used in any relevant control-plane protocol extensions).



The NRP-ID is not the same as Flow-Aggregate Selector (FAS). The FAS is
quite simply the marking in the data plane packet that identifies a
Slice-Flow Aggregate. The same Slice-Flow Aggregate may be identified by
multiple Flow-Aggregate Selectors (see the example in Section 5.1.1 where a
range of VPN service labels – each acting as a FAS – select the same
Slice-Flow Aggregate). The solution architecture leaves room for an
implementation to overload the NRP-ID and use it as a FAS – but that is
strictly an implementation choice.



And yes, we do expect all other related work to eventually align and adhere
to what is specified in this document.



Regards,

-Pavan (as co-author)

On Thu, Feb 24, 2022 at 3:14 AM Ogaki, Kenichi <ke-oogaki@kddi.com> wrote:

> Hi Authors,
>
> I'd just like to clarify.
> Comparing Fig. 5 in draft-ietf-teas-ietf-network-slices-05 with Fig. 1 in
> this draft, I understand that this draft also describes one of solutions
> realizing Network Resource Partition(NRP).
> If my understanding is correct, NRP-ID is essentially same as FASL and
> "Slice Aggregate ID" described at Fig.5 in
> draft-bestbar-lsr-slice-aware-te-00.
> From an operational perspective, it's burden to manage many slice related
> components and the mappings of these components, e.g. connectivity matrix
> <-> IETF network slice <-> Slice-flow Aggregate <-> FAS <-> NRP.
> Do authors have any thought to at least unify these identifiers in a
> series of bestbar drafts. Or, is there any reason not able to unify these?
>
> Thanks,
> Kenichi
> -----Original Message-----
> From: Teas <teas-bounces@ietf.org> On Behalf Of Lou Berger
> Sent: Friday, February 18, 2022 10:28 PM
> To: TEAS WG <teas@ietf.org>
> Cc: TEAS WG Chairs <teas-chairs@ietf.org>;
> draft-bestbar-teas-ns-packet@ietf.org
> Subject: [Teas] WG adoption poll: draft-bestbar-teas-ns-packet-08
>
> Hello,
>
> This email begins a 2-week adoption poll for:
> https://datatracker.ietf.org/doc/draft-bestbar-teas-ns-packet/
>
> Please note that IPR has been disclosed on this document:
>
> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-bestbar-teas-ns-packet
>
> Please voice your support or objections to adoption on the list by the end
> of the day (any time zone) March 4.
>
> Thank you,
> Lou (as Co-chair)
>
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>