Re: [Teas] //Re: [Lsr] "Packet Network Slicing using Segment Routing"

<chen.ran@zte.com.cn> Tue, 26 March 2019 09:01 UTC

Return-Path: <chen.ran@zte.com.cn>
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 78332120296; Tue, 26 Mar 2019 02:01:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 38nwuB9bPK_D; Tue, 26 Mar 2019 02:01:18 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 1D35E120309; Tue, 26 Mar 2019 02:01:15 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 3D9F349AD8696E7E9EDA; Tue, 26 Mar 2019 17:01:11 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Forcepoint Email with ESMTPS id 025BBE2D2E7AD24E60B0; Tue, 26 Mar 2019 17:01:11 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse01.zte.com.cn with SMTP id x2Q90vFn016605; Tue, 26 Mar 2019 17:00:57 +0800 (GMT-8) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njxapp05[null]) by mapi (Zmail) with MAPI id mid203; Tue, 26 Mar 2019 17:00:58 +0800 (CST)
Date: Tue, 26 Mar 2019 17:00:58 +0800 (CST)
X-Zmail-TransId: 2afd5c99ea4a0ee07aec
X-Mailer: Zmail v1.0
Message-ID: <201903261700586759048@zte.com.cn>
Mime-Version: 1.0
From: <chen.ran@zte.com.cn>
To: <lberger@labn.net>, <acee@cisco.com>
Cc: <teas@ietf.org>, <lsr@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse01.zte.com.cn x2Q90vFn016605
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/H1DSlN5H2a3tc50pTuHD4ifQ2Qg>
Subject: Re: [Teas] =?utf-8?q?//Re=3A_=5BLsr=5D__=22Packet_Network_Slicing_us?= =?utf-8?q?ing_Segment_Routing=22?=
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: Tue, 26 Mar 2019 09:01:30 -0000

Hi chairs,

Thank you very much for your suggestions.

I will change the name of the draft, and continue the draft on the teas wG.

Regards,


Ran

--------------------------------------------------------------------Re: [Lsr] [Teas] "Packet Network Slicing using Segment Routing"
Lou Berger <lberger@labn.net> Mon, 25 March 2019 23:32 UTCShow header


Authors, just resubmit with teas in place of lsr, when you do your 
update based on other feedback you received this week.

Thanks,

Lou

(TEAS co-chair)

On 3/25/2019 2:52 PM, Acee Lindem (acee) wrote:
>
> Hi Authors,
>
> I read this draft on the plane on the way to Prague and I don’t think 
> it belongs in LSR. I believe it belongs in TEAs as it is more about 
> the requirement and framework for TE slicing than it does about adding 
> the Administrative Instance Identifier (AII) to the OSPF and IS-IS TE 
> encodings. We will go forward with the presentation on Thursday with 
> the understanding that LSR will not adopt this work. If it is adopted 
> in TEAS, we can decide whether to proceed with a small LSR draft with 
> just the new AIIs or simply provide review and IANA code points in our 
> registries.
>
> Thanks,
> Acee
>
>