IETF Logo Mail Archive

Re: [Teas] A draft on the framework for end-to-end IETF network slicing

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 13 May 2021 04:48 UTC

Return-Path: <jmh@joelhalpern.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 5BC883A25BC for <teas@ietfa.amsl.com>; Wed, 12 May 2021 21:48:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Level:
X-Spam-Status: No, score=-2.801 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 sKdFdqRR6TrC for <teas@ietfa.amsl.com>; Wed, 12 May 2021 21:48:33 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E5F13A25BB for <teas@ietf.org>; Wed, 12 May 2021 21:48:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4FgfLT0s5bz6G9tM; Wed, 12 May 2021 21:48:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1620881313; bh=4ZDELLGO1MldOY4pJ+IWyh5xdsA7aEf7R9s9HMtXcwk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=QhehBNmvXnVOZmIm8rLKWde+gwT3FhVtxVnH1u9UVGLyjzVbZqcySPIZBWU2TPKMZ lCGx1sSAqSQCNOmGLv2AmIaQu0XazU5uKD1V0WQNoL1OXh5OIhgaibII34bODRzZm6 CMUELr9o8rKVoaELqwyACHzk2yLCldGczHJBmn8M=
X-Quarantine-ID: <mESAzIQaQt4K>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4FgfLS1svGz6G7yZ; Wed, 12 May 2021 21:48:31 -0700 (PDT)
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, "teas@ietf.org" <teas@ietf.org>
References: <c7bb7462db8f4149912d644adbd4760b@huawei.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <e8e5e968-f6af-a910-d2ec-510fc98ff1d6@joelhalpern.com>
Date: Thu, 13 May 2021 00:48:31 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <c7bb7462db8f4149912d644adbd4760b@huawei.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/NIUmdiLd0on4g9LawP3MKQLnxL8>
Subject: Re: [Teas] A draft on the framework for end-to-end IETF network slicing
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, 13 May 2021 04:48:37 -0000

It is not at all clear that any identifiers are needed inside the 
various networks, and specifically it is not clear that an internal 
identifier for the end-to-end network slice is needed at the level of 
the IETF network slice as is being defined by teas.  Since path 
selection, QoS parameter handling, and resource allocation needs to be 
handled in aggregate, it seems likely that no such identifier is needed.

Yours,
Joel

On 5/12/2021 10:53 PM, Dongjie (Jimmy) wrote:
> Hi WG,
> 
> Recently we published a draft on the framework for end-to-end IETF 
> network slicing: 
> https://datatracker.ietf.org/doc/html/draft-li-teas-e2e-ietf-network-slicing 
> <https://datatracker.ietf.org/doc/html/draft-li-teas-e2e-ietf-network-slicing>
> 
> This document describes the scenarios of end-to-end network slicing, and 
> the framework of network slice mapping between different network 
> segments and network domains. Multiple network slice related identifiers 
> are defined to covers different network scopes.
> 
> The network slice related identifiers of different network scopes can be 
> instantiated with MPLS or IPv6 data plane, which are further described 
> in the following drafts:
> 
> https://datatracker.ietf.org/doc/draft-li-mpls-e2e-ietf-network-slicing/ 
> <https://datatracker.ietf.org/doc/draft-li-mpls-e2e-ietf-network-slicing/>
> 
> https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-slicing 
> <https://datatracker.ietf.org/doc/html/draft-li-6man-e2e-ietf-network-slicing>
> 
> https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing 
> <https://datatracker.ietf.org/doc/html/draft-li-spring-sr-e2e-ietf-network-slicing>
> 
> Your review and comments are welcome. (Comments on the specific data 
> plane draft can go to the corresponding WG mail list).
> 
> Best regards,
> 
> Jie
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>

v2.23.0 | Report a Bug | By Email