Re: [Teas-ns-dt] Isolation text in appendix of definition draft
Eric Gray <eric.gray@ericsson.com> Mon, 29 June 2020 13:01 UTC
Return-Path: <eric.gray@ericsson.com>
X-Original-To: teas-ns-dt@ietfa.amsl.com
Delivered-To: teas-ns-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 78E6D3A0ECA
for <teas-ns-dt@ietfa.amsl.com>; Mon, 29 Jun 2020 06:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=ericsson.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 OoR64pzWapyC for <teas-ns-dt@ietfa.amsl.com>;
Mon, 29 Jun 2020 06:01:33 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com
(mail-mw2nam10on2046.outbound.protection.outlook.com [40.107.94.46])
(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 691143A0EDB
for <teas-ns-dt@ietf.org>; Mon, 29 Jun 2020 06:01:33 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=TSVkjbx9dL28s0O5qYuLRrKZSV3GBnFpUwV0/cjozJFQJbU7kxnmmssl6ADbDD+tnf8yahio94fKamXM+NiBKeAJi55oa2wpIOjPVLhL8gr4CkaB/06czwFdVfzwJvwisa6JNo6yKNnk4Rlk5CYopBS5jgH3DaJsByq+bpaRssr8AvDqXNtgZFUWJsQvoouSON+yGyS4TuTCACsoyx7rJIH56WreFvfrUggQI62/8Ii4O0Gg+RAzMR32pY2bOICRVI5HIjxhWxrGtD5gEGWpLpSWQxYEuXa0YnSmarXhKNrD0Pt7kHjrzogBA0Fauh57GLTEDLm9gDNK8tZ4Tj0dOA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=5ign09fvcGU/zMoxK91/F9jvHQaJ5xAioYGMQCJ0Vjk=;
b=JuB5HDXE5oaSzDugllS5LevLMSqdmoJDplTP3en0kNMMZ0RPl9J1LrGXb8LyTk3XggL+p0n5TwPYb9M/Th7SI+TI6Jp+tDLKbT4Y/wHlfD+5RXA+jgg/UJhTiCb2I+wJRUdoiqJ5f1PsKoMCrDhClm3CxE7xLRHGo2nRiAVShIFAESbns/iWxa27+fKBdbfWaUOjXYyBvusn+Y+UA/SArFd5BfpegnVCf7uZEroWVnNlYIGrlACWc+NIf9FWm4rwIrn4DTqbelQgrMAJckczUBtBZhbAhq25y5Ne5MMvpNrYMxaWKwvrA7bbtU4zIXWlWXiyOqTmjo8+Hxdszaqakw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com;
dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=5ign09fvcGU/zMoxK91/F9jvHQaJ5xAioYGMQCJ0Vjk=;
b=ac5Ek4Cv4yA5Ghp7EGB+NB8Q/cnyJFQSdyNqX5inMcHgY7fPz9173lJvFhKcB4l9fnIWgHShzLBDtScgriUwUn4lwosiXNOsUnyjV7KWmzp1oCUG68rKgwCW0xc1XdpGJ4CbC76/5zkPu5IHH/z+KwJyKqWDQq9Old6ArhTsFZY=
Received: from MN2PR15MB3103.namprd15.prod.outlook.com (2603:10b6:208:f9::10)
by MN2PR15MB3280.namprd15.prod.outlook.com (2603:10b6:208:38::21)
with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3131.21; Mon, 29 Jun
2020 13:01:29 +0000
Received: from MN2PR15MB3103.namprd15.prod.outlook.com
([fe80::6dab:2470:4c23:1471]) by MN2PR15MB3103.namprd15.prod.outlook.com
([fe80::6dab:2470:4c23:1471%5]) with mapi id 15.20.3131.026; Mon, 29 Jun 2020
13:01:29 +0000
From: Eric Gray <eric.gray@ericsson.com>
To: "Dongjie (Jimmy)" <jie.dong@huawei.com>, Kiran Makhijani
<kiranm@futurewei.com>, Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org>,
"teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: Isolation text in appendix of definition draft
Thread-Index: AdZLCj3qcrgUgSfpTpKLZjbA0ZA1mQAAoquUAHm3V3AASCdDQA==
Date: Mon, 29 Jun 2020 13:01:28 +0000
Message-ID: <MN2PR15MB31034CC55C353186175E90DE976E0@MN2PR15MB3103.namprd15.prod.outlook.com>
References: <MN2PR15MB3103F7A1F511EEB6FAEB959697920@MN2PR15MB3103.namprd15.prod.outlook.com>
<BYAPR13MB24377096DD01A10056EE3213D9920@BYAPR13MB2437.namprd13.prod.outlook.com>
<82f0946859024453b9b56bfc04a59aad@huawei.com>
In-Reply-To: <82f0946859024453b9b56bfc04a59aad@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed)
header.d=none;huawei.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [73.248.143.71]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ffa535fc-6f94-4f9e-1dfd-08d81c2c89e2
x-ms-traffictypediagnostic: MN2PR15MB3280:
x-microsoft-antispam-prvs: <MN2PR15MB32807B3E8F89891013840360976E0@MN2PR15MB3280.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 044968D9E1
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jeN6aWp0XqpkiGKcoKfmDS+Fb2bKBqk5nWEM0Z3quTlo3Ynht44AHpDdyK8JhSoFTp0NvR+7088OJaREIFNFr/fGd9XvMW5stBI0sAzilq17FZkYse+dDhEpFQ97fkeWp9VyYMTS8JNiUZiVxRYTZqn0YvoUf8FNHys04U6OiVSkay4Y6HDLENTxx9KtkICMesDjlCv0HpEbm+Qk83Gjx6FUoUvccktK18yMH0EuwoZQaGA8sODGLjzfLpzYs1JCdaYdnwaBzFavt8LM/gIuuzfQB93S83AEgfhimIBypJcxhsBPcIeEK7gZRcJ0h44uSpfW3QDEDHcKKlio7GMNig==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;
IPV:NLI; SFV:NSPM;
H:MN2PR15MB3103.namprd15.prod.outlook.com; PTR:; CAT:NONE;
SFTY:;
SFS:(4636009)(136003)(376002)(396003)(39850400004)(366004)(346002)(66946007)(8936002)(33656002)(7696005)(2906002)(8676002)(86362001)(110136005)(44832011)(316002)(478600001)(53546011)(66446008)(64756008)(66556008)(6506007)(66476007)(71200400001)(83380400001)(76116006)(5660300002)(9686003)(55016002)(186003)(52536014)(26005);
DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: JuEIVO5UTOMAWfjJnEOYT2Rdx3nC5i1kRPavZHvla1Hjhknkd3rYsgHEbsZMi0eMdlvLEr5ZmuAcEPWmJndTbbl3f8Ix2em2sLMiwQLet9ecquFEfMeWuv6WN13UiQoQ/DsJ5DGsZMoQ6+L967wu/im3QDuBQdDs09oI8fU4p2uZEcnDR22yqdU5mGdtKdBlX2XiW8jBsWGYGpKCrnctmChGRjxYQ2kBZjwxIOBukPvSwuaS3i2ua+fR43ZayQg1G43Y7PIPVSeCJ4t1Qh2cPUIOBjY5vmJhuhqFb9dmFndzu3/m55IClMpsSMIRoqoeqWoIrrtTI2OD8TcdWML8Ot2bJ6+yaHVRK6CgSwEBqsXhjtshG1cjfcpSxR5b8MAzwDK7n3rwIBu7FIWmIDwbp/f6owxNWOZeC82NVxG3yswgfE6aeKGngp3tnNb+zJB8ybbBr7rGZNQiSRoqj3JRolOonirOLgRqtdsPoTWrLIA=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative;
boundary="_000_MN2PR15MB31034CC55C353186175E90DE976E0MN2PR15MB3103namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR15MB3103.namprd15.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ffa535fc-6f94-4f9e-1dfd-08d81c2c89e2
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2020 13:01:28.9032 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: RT5IG6wXHYB+AhTSPz9JdZ69kXhdKXDL+K/LKurHyaedSlKSQI5oMFuMlCDs2294hLO7afRghcmSpohprdDbsw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR15MB3280
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/aoq4jq4okXlHJvkB1Pv0S2mcvRw>
Subject: Re: [Teas-ns-dt] Isolation text in appendix of definition draft
X-BeenThere: teas-ns-dt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TEAS Network Slicing Design Team <teas-ns-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas-ns-dt>,
<mailto:teas-ns-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas-ns-dt/>
List-Post: <mailto:teas-ns-dt@ietf.org>
List-Help: <mailto:teas-ns-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas-ns-dt>,
<mailto:teas-ns-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2020 13:01:48 -0000
Jie,
Clearly this represents a strong potential misunderstanding of what was being discussed.
Nobody was discussing moving the text in the definitions appendix to section 4.1.2. For a number of us, that would be a step backwards and away from convergence on the content for the draft.
What is being discussed is whether or not to move the text in the definitions draft appendix to the Framework draft (specifically to section 2, in a new subsection 2.1).
Where the confusion may have come up is that we (Kiran and I) discussed - whether or not we move the text in the appendix - we should add a _reference_ to it (where ever it ends up) in section 4.1.2 ("Other Objectives").
Hope that clears things up...
--
Eric
From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org> On Behalf Of Dongjie (Jimmy)
Sent: Saturday, June 27, 2020 11:28 PM
To: Kiran Makhijani <kiranm@futurewei.com>om>; Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org>rg>; teas-ns-dt@ietf.org
Subject: Re: [Teas-ns-dt] Isolation text in appendix of definition draft
Hi Eric, Kiran and all,
For the definition draft I tend to agree to move the isolation text from appendix to the subsection "other objectives". Depending on whether "other objectives" can be considered as part of the SLO characteristics, the "other objectives" subsection may also be listed as a subsection in parallel with section 4.1 "SLO characteristics", e.g. make it subsection 4.2?
As for the framework draft, I'm willing to work on the description about this. Also note that section 2 of framework draft refers to the requirement section of the enhanced VPN framework, in which isolation is further described.
Best regards,
Jie
From: Teas-ns-dt [mailto:teas-ns-dt-bounces@ietf.org] On Behalf Of Kiran Makhijani
Sent: Friday, June 26, 2020 12:24 AM
To: Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org<mailto:eric.gray=40ericsson.com@dmarc.ietf.org>>; teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>
Subject: Re: [Teas-ns-dt] Isolation text in appendix of definition draft
Hi Eric,
If you don't mind I can work with you to bringing it in framework and I anyway intended to glue the orphaned Appendix to Realization section but 4.1.2 is also a good place.
Regards
Kiran
________________________________
From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org<mailto:teas-ns-dt-bounces@ietf.org>> on behalf of Eric Gray <eric.gray=40ericsson..com@dmarc.ietf.org<mailto:eric.gray=40ericsson..com@dmarc.ietf.org>>
Sent: Thursday, June 25, 2020 9:19:31 AM
To: teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org> <teas-ns-dt@ietf.org<mailto:teas-ns-dt@ietf.org>>
Subject: [Teas-ns-dt] Isolation text in appendix of definition draft
Folks,
I had a plan to suggest for this text, but I think there was not overwhelming interest in moving this to the Framework draft. Plus we ran out of time.
If we were going to move it, my suggestion was to add a new subsection in the Framework draft under the current section 2 (Transport Slice Objectives) - probably with the heading "2.1 Isolation" that includes the agreed text from the current appendix in the definition draft. In the definition draft, we would then remove the appendix entirely, and add a new paragraph to current section 4.1.2 (Other Objectives) that says "Also, isolation objectives (see [I-D.nsdt-teas-ns-framework] for more information) may also be necessary to meet some Transport Slice requests."
I have a very slight issue with leaving an appendix in the definitions draft, because it may leave some readers with the impression that this is an open issue. But I am essentially okay if we decide to leave it as is. I would suggest - if we do that - that we add a similar new paragraph to section 4.1.2 that points to the appendix.
--
Eric
- [Teas-ns-dt] Isolation text in appendix of defini… Eric Gray
- Re: [Teas-ns-dt] Isolation text in appendix of de… Kiran Makhijani
- Re: [Teas-ns-dt] Isolation text in appendix of de… Dongjie (Jimmy)
- Re: [Teas-ns-dt] Isolation text in appendix of de… Eric Gray