Re: [Teas-ns-dt] Definitions draft text improvement on NBI/SBI.

Kiran Makhijani <kiranm@futurewei.com> Tue, 17 March 2020 00:13 UTC

Return-Path: <kiranm@futurewei.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 1D0B83A1402 for <teas-ns-dt@ietfa.amsl.com>; Mon, 16 Mar 2020 17:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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=futurewei.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_paCyZm80BO for <teas-ns-dt@ietfa.amsl.com>; Mon, 16 Mar 2020 17:13:28 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2110.outbound.protection.outlook.com [40.107.243.110]) (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 452263A12F0 for <teas-ns-dt@ietf.org>; Mon, 16 Mar 2020 17:13:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JdQsrSXI9bM2JyiOWGXyYEuWq9yLfqTE85owQgYZHVqanJH1spCF/y4mBn0w6nbfqNO2liUt+3WvLWkEUPZv73ZUI+r4wkWlez4kNLPs5JrIbUJCRIgEHlAcItpKZcScXfGyYj0y7acDiPNa/IvFhf5KP/WeUI4ror+knkiIzVqfFwg8yEXoiewUHOjhT/2QkZoBP6yivkdyymmkxnZCpfVTOelbGFflVgX8sV094ZiJkTOxO90qBaiB4dtTWmh2T2qE4k5iHL+CByadh8TU21GTD7V2Ka6cl3vHGJys+bLhHvgAo+8pHYBnZoAMsorbW8+MvjCpDgE3hAuYXzW50g==
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=tHLI903BdexLZCs6YzSGhQst/3U8iUiYAWMVI4dK8OQ=; b=Ry+YaKTESlel+8KhYX1u+RaWD0dc3aOuPCmF9mkrXEzDHAIuXC+S1gvXazP80yZ5YR8W8TU/rhLY9+J4w64y8pCEDpN5vVfqjTLYLi/8JPABkTYtVSzB6q/p9U4C4TvlzgkbNLxID2b2PRnub2dWK1UHxxcMjlPd7WDWRZ6yTEIpmMQox0E+usSZ98sKN++2j41E6k48UwXF+zOEVpFmDu9FrhYGu+FdXp4F/WkX2mfmq0n55NWGqOmmaZtdfSGVUp26qBAeWH4vtY7JzRz7YrtF/i5Sl+AeTNsHT98vVGRqlFaSompjguNOZDlVMdddInzQOf1t4E1/sJYk0o9VXg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tHLI903BdexLZCs6YzSGhQst/3U8iUiYAWMVI4dK8OQ=; b=EOsrJBB4iulwvzy2oWm3FUn2XlqROv2hh3ZaWEYOJFK39TWg5l3IvoR4Wi2swnC26dz0N6wgvKAw0hFsqvn/BmvrnGOQEEXMCD1Pv8ch8fMHggddSnMCWv+0hoykdOSlqspJ0yHP0xnJzLzcZIrBTJeYHZGV8NtmJ+/vl3f4jqQ=
Received: from BYAPR13MB2437.namprd13.prod.outlook.com (2603:10b6:a02:cb::23) by BYAPR13MB2664.namprd13.prod.outlook.com (2603:10b6:a03:fe::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2835.12; Tue, 17 Mar 2020 00:13:25 +0000
Received: from BYAPR13MB2437.namprd13.prod.outlook.com ([fe80::d01b:c684:d858:fd26]) by BYAPR13MB2437.namprd13.prod.outlook.com ([fe80::d01b:c684:d858:fd26%3]) with mapi id 15.20.2835.012; Tue, 17 Mar 2020 00:13:24 +0000
From: Kiran Makhijani <kiranm@futurewei.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: [Teas-ns-dt] Definitions draft text improvement on NBI/SBI.
Thread-Index: AdX7v23bNeESlSQcSAOyb+WVfZ2OsAAIsV8AAAHg/2A=
Date: Tue, 17 Mar 2020 00:13:24 +0000
Message-ID: <BYAPR13MB243766D9CD25DBC6DCB1079AD9F60@BYAPR13MB2437.namprd13.prod.outlook.com>
References: <BYAPR13MB24371C43649A2740D690D9E7D9F90@BYAPR13MB2437.namprd13.prod.outlook.com> <b8ec8447-5a60-47e0-8888-aabb221ebd82@Spark>
In-Reply-To: <b8ec8447-5a60-47e0-8888-aabb221ebd82@Spark>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kiranm@futurewei.com;
x-originating-ip: [73.63.186.221]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 349894c6-2e76-4966-ebbe-08d7ca080287
x-ms-traffictypediagnostic: BYAPR13MB2664:
x-microsoft-antispam-prvs: <BYAPR13MB2664EE3135978E38146CAB16D9F60@BYAPR13MB2664.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0345CFD558
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(396003)(39850400004)(346002)(136003)(376002)(366004)(199004)(71200400001)(110136005)(186003)(53546011)(6506007)(7696005)(26005)(2906002)(66476007)(966005)(52536014)(66946007)(8936002)(66446008)(64756008)(66556008)(33656002)(478600001)(81156014)(81166006)(8676002)(66616009)(86362001)(55016002)(76116006)(5660300002)(9686003)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR13MB2664; H:BYAPR13MB2437.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: axUbuhFBIc+1IWk+6V3lpEO6EWiTo1XSeMg7/n904HKR9H14zyPAZ1C9rCY08yCWyf8tOUXEn4v7gMPo06owvHK6J7fwe9WQGjObCt6HZVGd1ktwXtvfkdXq9Gb8msRq7Nc0Cv96I4wNQx+2Y+odZYjjimjQsaynqV5W4C1X5sOrMsNq1JUoICeSk2pEgvw6l3VW7XQDfUhHEARJxHHALMTMtMttcPURo675U0GuhsW43DvO14KiiazAm3qvdq0pXw3cV4iml7SXNLMed7Bk7qKW9kMz22RW7yYaRzdLv5/D258n8IDDSxOmgxKFiqmdX8/uzZLRiE5rYvkW+cj4tDtFYP2T67S8ZAQBeyT1xb2CWCE14ABCaFTlVNDqJ+FH2YV1OzZtr+1ecwuvcUPlUSnxBz9/gLDC7WGv5VpAI74EC/xibh7qjTn7zrlIZSMo50ldHN7F2Xw+mD8gz3nm9VbnwgH1bpUcFiGUJaPFyoUUFyY7ejIekceup4dzmiJTBW3urA4jUTTKSrzkegEJBw==
x-ms-exchange-antispam-messagedata: fyJzdpAMaa4uh125Qi9EoT0HHt3RfTW6D5d08VbJuN0X5Kd+xif8dS0BWDsmV3UWtEv+YRWCXFct4EuJik8m6u7bOJj7zUiawrjJcW1VFAaIrZ4tOAW67sjzM9NM2WDm0s7u0HFd9sVhkv/ZvxQdJw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/related; boundary="_004_BYAPR13MB243766D9CD25DBC6DCB1079AD9F60BYAPR13MB2437namp_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 349894c6-2e76-4966-ebbe-08d7ca080287
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Mar 2020 00:13:24.4757 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Dwx0SpM8cSyOfY6zDpTAR2Ly5PCdgjwBr2RapK0FnyL6l0zJhQz7GD0XtP1GGoxoLyHm2amsZG3fxp+rDuM3nw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR13MB2664
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/5RVmq5oRmWunn5qSv_UwgBb68R0>
Subject: Re: [Teas-ns-dt] Definitions draft text improvement on NBI/SBI.
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: Tue, 17 Mar 2020 00:13:30 -0000

I am ok with either text. But since the comment was raised, it made me think that when we say asynchronous and/or  bidirectional, it is a particular means of telling implementation or low level design detail. There was also a question on what should go in framework vs definitions document.

At this point we are focusing on high-level description and the interface for me corresponds to a logical channel. I have tried to take care of these 2 keywords by using “on-demand”, “retrieval”, “informed”.

Does this explanation work for you? Or any other suggestion?
Kiran

From: Jeff Tantsura <jefftant.ietf@gmail.com>
Sent: Monday, March 16, 2020 3:28 PM
To: teas-ns-dt@ietf.org; Kiran Makhijani <kiranm@futurewei.com>
Subject: Re: [Teas-ns-dt] Definitions draft text improvement on NBI/SBI.

Kiran,

I don’t think the objection is valid, “bidirectional and asynchronous” defines basic characteristics and is not implementation specific.  If someone thinks otherwise please instantiate your objections.
Thanks!

Cheers,
Jeff
On Mar 16, 2020, 11:26 AM -0700, Kiran Makhijani <kiranm@futurewei.com<mailto:kiranm@futurewei.com>>, wrote:

[cid:image001.gif@01D5FBB0.10181FD0]
Hi,
In response to text objections about “bidirectional and asynchronous” terms being implementation specific.  Please see
https://github.com/teas-wg/teas-ns-dt/issues/14<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fteas-wg%2Fteas-ns-dt%2Fissues%2F14&data=02%7C01%7Ckiranm%40futurewei.com%7C11c4e1de3a1b4e6d8a0e08d7c9f97a08%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637199945645428557&sdata=lKNqkRKgUVvbwd%2Ffnf3OXLpkxggka2cQweX5fwdODcA%3D&reserved=0>

In nutshell new text could be revised as below:

- TSC Northbound Interface (NBI): is an interface between a higher level
system, e.g. 'E2E network slice orchestrator' and the 'Transport
slice controller'. It is a technology agnostic interface. Over this NBI, slice characteristics and other requirements can be informed to TSC and current state of a transport slice can be retrieved.

- TSC Southbound Interface (SBI): is an interface between 'Transport
slice controller' and network controller(s). These interfaces are
technology-specific and can utilize many of the existing data
models such as L2SM, L3SM, VPN, etc. TSC may request network resources or retrieval of their current state.

Thanks
Kiran
--
Teas-ns-dt mailing list
Teas-ns-dt@ietf.org<mailto:Teas-ns-dt@ietf.org>
https://www.ietf.org/mailman/listinfo/teas-ns-dt