[Teas] draft-ietf-teas-ietf-network-slice-definition-00

Uma Chunduri <umac.ietf@gmail.com> Fri, 12 February 2021 00:26 UTC

Return-Path: <umac.ietf@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 04D993A0EC9; Thu, 11 Feb 2021 16:26:50 -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 q_06hl0rGPL3; Thu, 11 Feb 2021 16:26:48 -0800 (PST)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 409963A0EC4; Thu, 11 Feb 2021 16:26:48 -0800 (PST)
Received: by mail-yb1-xb31.google.com with SMTP id d184so7478684ybf.1; Thu, 11 Feb 2021 16:26:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=W4YWtqoxX7kWA5GUTy67ARTYW1OOv6ZCH7DDnBqJUWc=; b=TpK0gJJrlBhk0BP92ERnLubeSDqDU+Foa/OMqGSFIQpsx9FZlAXQcyVSeqUM9LwI4M Hsqmt7vbsSKSp8CJdvj0V77ioGc9MumcQH+HQejmaHZjGnX4TvDXK4/pQkXGecSI/5R+ X4gL/61Si2tPcLVajt+/bbdiEyFJpAfwSee9ks0wFdFhuQXOgk0QtwLAUqXFxzAfyLtX CqzbMz1QVkrR3QWZ4b+4LDQoKt8bYh8MIiFm+M+sJPGIVc/rm3LFt6kAqC19uW1ENVZy EFchlXIsLoFnnqxjUKJJ4ySB7R/WIePZIK+sDzgCR+tv0mka7mClKKd+Ok8S/25/LpHR YBZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=W4YWtqoxX7kWA5GUTy67ARTYW1OOv6ZCH7DDnBqJUWc=; b=tltarJRyzjnTqDgRzU35f0XYwTnzFbWHIiXWBFAlZOyU5gvcBoBEZ3XCNlOj0JJNnR ok8UogyIIAyGPAaj/OlaELmdJ+kF6ssPfh0i7aJsZIYzsyZFvDLk6pdz7Da8Tvsapq1w Cl3p2UG+9GzyY/ZYewnvz8WE4emYVEslvnKQ7FkzSdtMMkFMwVHqlrxDgpwuV90m1Ix7 oag96pRuTj3kFRhFV668NGVncwj+ZRUq9Nk68FzEyAqgXZBLxkOOOXZF76BitlFmVmvb 8eIK85VYCI9vuUvxhTl1/7hBTGQfVSdB0DNqyynUlLKTuLPbr4o40sLl61TNdEsA3zMA 0Kgw==
X-Gm-Message-State: AOAM531jJ5+bBsLUn6QCOf54LyOiJdGOYL438NiZlhxH78rdSmgck9Rz hOwtOASeq2oQLGSxYLuPZnZRThummYS1JVpfaqEpPouaI+w=
X-Google-Smtp-Source: ABdhPJzFYe9YkZ46JQnWKFTtYX7utgNW2Dm8O//bz/cwJUf/gVLVU3kkSrzB88VwzuN5S5btlj9lRm2XK6nI+17Whug=
X-Received: by 2002:a25:538a:: with SMTP id h132mr608047ybb.247.1613089606579; Thu, 11 Feb 2021 16:26:46 -0800 (PST)
MIME-Version: 1.0
From: Uma Chunduri <umac.ietf@gmail.com>
Date: Thu, 11 Feb 2021 16:26:36 -0800
Message-ID: <CAF18ct7PNaA6G1U1ZszQt0JA72ehspH7H3vdew1JVHkQkA9Vug@mail.gmail.com>
To: TEAS WG <teas@ietf.org>
Cc: dmm <dmm@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fdba5505bb18b049"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/e226kzQ-01BHQUi4_tHFO3kO8jo>
Subject: [Teas] draft-ietf-teas-ietf-network-slice-definition-00
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: Fri, 12 Feb 2021 00:26:50 -0000

Dear All,

2 questions on this draft:

1.
Section 4.2 defines 'IETF Network Slice endpoints'

It Says -

" o They are conceptual points of connection of a consumer network,

      network function, device, or application to the IETF network
      slice.  This might include routers, switches, firewalls, WAN,
      4G/5G RAN nodes, 4G/5G Core nodes, application acceleration, Deep
      Packet Inspection (DPI), server load balancers, NAT44 [RFC3022
<https://tools.ietf.org/html/rfc3022>],
      NAT64 [RFC6146 <https://tools.ietf.org/html/rfc6146>], HTTP
header enrichment functions, and TCP
      optimizers."



I presume 4G/5G RAN nodes, you meant eNB, gNB-DU, gNB-CU-UP etc. If yes,

there was a question from one of the 3GPP delegates on how this can be
called as

'IETF Network Slice Endpoint'?


I guess, we ought to be cognizant when we tag 'IETF' for some of

these definitions.


The above also mentions 4G/5G Core nodes aka SGW/PGW/all-variants-of-UPFs and

these are again not typically 'IETF Network Slice Endpoints'.


Could you please give your thoughts here?


2.


Section 1 says


"IETF network slices are created and managed within the scope of one

   or more network technologies (e.g., IP, MPLS, optical). :



Obviously, optical is a bigger topic and if we talk about optical
solutions like

OTN (Layer 1)  and SPN (Layer 1.5) are more controlled by other SDOs. SPN has

a complete slicing solution with not much bearing to IETF.


So, could you please expand 'optical' in the list above? Is it the
various optical control plane

specifications done here, you were referring to?


--

Uma C.