Re: [Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 15 January 2021 02:18 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 B7EBF3A0813 for <teas@ietfa.amsl.com>; Thu, 14 Jan 2021 18:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level:
X-Spam-Status: No, score=-2.362 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.262, 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 o4Eg1o7H79Kb for <teas@ietfa.amsl.com>; Thu, 14 Jan 2021 18:18:25 -0800 (PST)
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 12E833A0812 for <teas@ietf.org>; Thu, 14 Jan 2021 18:18:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4DH4bh65Xjz6GBGZ; Thu, 14 Jan 2021 18:18:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1610677104; bh=XeMRBgUB3aMSxAhVp9InjmqJV7laF/xnA/HQbsrHUzo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=dLRJQHDJ3gLxxqcDN699gfL5gJqepMPP3AXiTR139mjibapaoMz6IGdO+7F1bepE1 iqA5dJrIuA49uput/UBq1Kyl2pz70ActqbCXEF6Q5GRzPUPPx1WH8f1R69Bptgky8a 3NgxQVzw29NXl9vglqcbwC9coRfCKtlxWTeJADfk=
X-Quarantine-ID: <nBNem66idEIF>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (unknown [50.225.209.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4DH4bh0Phwz6G8qs; Thu, 14 Jan 2021 18:18:23 -0800 (PST)
To: peng.shaofu@zte.com.cn
Cc: teas@ietf.org
References: <202101151008295415129@zte.com.cn>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <342ca5e0-7374-9ed3-762f-385628806fb6@joelhalpern.com>
Date: Thu, 14 Jan 2021 21:18:21 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <202101151008295415129@zte.com.cn>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/IlwNfyEgyCE2ejgj9oDiKyGX9dI>
Subject: Re: [Teas] WG adoption - draft-nsdt-teas-ietf-network-slice-definition
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, 15 Jan 2021 02:18:27 -0000

Given that station in the case below is making a request, isn't it 
reasonable to assume that the request makes its way to the control 
systems, which then handle the itneraction with the underlay network 
through the mechanisms proposed in the definitions and framework drafts?

Yours,
Joel

On 1/14/2021 9:08 PM, peng.shaofu@zte.com.cn wrote:
> 
> A little comment:
> 
> 
> It seems that the definition document only support that the realization 
> of IETF network slice is triggered by the consumer through the interface 
> to NSC with specific SLO. I think it is not enough. Please see if it is 
> needed to support the case for a network device (the headend) to 
> explicitly request a slice on demand, and request a connection path 
> within the specific slice on demand.
> 
> 
> Regards,
> 
> PSF
> 
> 
> 原始邮件
> *发件人:*VishnuPavanBeeram
> *收件人:*TEAS WG;
> *抄送人:*TEAS WG Chairs;
> *日 期 :*2021年01月04日 22:02
> *主 题 :**[Teas] WG adoption - 
> draft-nsdt-teas-ietf-network-slice-definition*
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
> 
> All,
> 
> This is start of a two week poll on making
> draft-nsdt-teas-ietf-network-slice-definition-02 a TEAS working group 
> document.
> Please send email to the list indicating "yes/support" or "no/do not
> support". If indicating no, please state your reservations with the
> document. If yes, please also feel free to provide comments you'd
> like to see addressed once the document is a WG document.
> 
> The poll ends January 18th.
> 
> Thanks,
> Pavan and Lou
> 
> 
> 
> _______________________________________________
> Teas mailing list
> Teas@ietf.org
> https://www.ietf.org/mailman/listinfo/teas
>