Re: [Teas-ns-dt] Traffic (address?) type information
"to-niwa@kddi.com" <to-niwa@kddi.com> Tue, 02 June 2020 01:30 UTC
Return-Path: <to-niwa@kddi.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 6AC593A07CB
for <teas-ns-dt@ietfa.amsl.com>; Mon, 1 Jun 2020 18:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
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=o365kddi.onmicrosoft.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 US7Fc0JjVWCE for <teas-ns-dt@ietfa.amsl.com>;
Mon, 1 Jun 2020 18:30:35 -0700 (PDT)
Received: from kddi.com (athena2.kddi.com [27.90.165.195])
by ietfa.amsl.com (Postfix) with ESMTP id 804CB3A07CE
for <teas-ns-dt@ietf.org>; Mon, 1 Jun 2020 18:30:35 -0700 (PDT)
Received: from LTMC2122.kddi.com (post-send [10.206.2.120])
by kddi.com (KDDI Mail) with ESMTP id 32901E0175;
Tue, 2 Jun 2020 10:30:34 +0900 (JST)
Received: from LTMC2145.kddi.com ([10.206.0.236] [10.206.0.236]) by
LTMC2122.kddi.com with ESMTP; Tue, 2 Jun 2020 10:30:34 +0900
Received: from LTMC2145.kddi.com (localhost [127.0.0.1])
by localhost.kddi.com (Postfix) with ESMTP id 1284D3A0065;
Tue, 2 Jun 2020 10:30:34 +0900 (JST)
Received: from LTMC2154.kddi.com (post-incheck [10.206.0.239])
by LTMC2145.kddi.com (Postfix) with ESMTP id 0752D3A006B;
Tue, 2 Jun 2020 10:30:34 +0900 (JST)
Received: from LTMC2154.kddi.com (localhost.localdomain [127.0.0.1])
by LTMC2154.kddi.com with ESMTP id 0521UXt9045917;
Tue, 2 Jun 2020 10:30:33 +0900
Received: from LTMC2154.kddi.com.mid_83694385 (localhost.localdomain
[127.0.0.1]) by LTMC2154.kddi.com with ESMTP id 0521KXvt031429;
Tue, 2 Jun 2020 10:20:33 +0900
X-SA-MID: 83694385
Received: from APC01-SG2-obe.outbound.protection.outlook.com
(mail-sg2apc01lp2058.outbound.protection.outlook.com [104.47.125.58])
by post-gate.kddi.com (KDDI Mail) with ESMTPS id 8ABFC80004;
Tue, 2 Jun 2020 10:20:32 +0900 (JST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=fv7WJtf+X0r+OD8gzxRJz62zLadXeWXMGxVqe3aKHDbnr/a9lDnjYHUQMfvDfImBvW61rEM79wz+W8WjfaAkuIxzdoFGSrKPyyBy2NR71My+g3yJmbReGDO1MR9mofswpf56pvWg5lkWgmeXE2pfYnCxh7clG1ddB2OEDJSBJHykvuK6ZyaVptaNImnGO3EhAflO6IYrFZN5JNrri27xRaJIYbuHmLiUC1cTHoWcEx14iOFgjaNzWy5wZfXgYp/KgsZ8/+YM9n+G3lc11WOmdUH0cJuscP2pHGEbCYUXWar0FPIw59kX0MEb1xowER8HSbZK9C0drdsiMO7lFLuKiw==
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=Fdz2e3BJyfTq7WAJ2aNYwwHT/8BjuctA4WG5wh34T8g=;
b=dKWdbjCs+I/5mxoCXEmfjtdr27+OlO2VWsIwV3JTZiiM80zCBRsOgbUrklVnmzG16F91wNh+IhxOTRSfw4ts18sbJQiJ3Noo1yMFu7c5NjHtGdD7CsxeCLu2eHPdmxiEXjNdEaYQKeMMh5I6FfA6dc029XEwiCpWiFD92o5aSFRRQGE2aYSkLzpA5LnDl/HdoWl5Jd60ZE0SfGEQQGTtYjK3OVFEn9DCiUdcouIWGrLAiJvFoN4L0b3sXDraXfSSFl2q+7NslCLddpLREmppfvs8iSQ60GOIjLZGngQrGPhywZQnauhgvFZYU4KHqcum9gpoq9C+f8HvpdOYTQJ+9g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=kddi.com; dmarc=pass action=none header.from=kddi.com;
dkim=pass header.d=kddi.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=o365kddi.onmicrosoft.com; s=selector2-o365kddi-onmicrosoft-com;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=Fdz2e3BJyfTq7WAJ2aNYwwHT/8BjuctA4WG5wh34T8g=;
b=l5SXr081AxO8MYhce0QxEeMiqT7fuQAuesFNAoE7M5ZVfRidGusHC7XRlZO6VcOo+RfOmevaVwiRJ2K+COh3sNpQZXPmYvnMX4tSyzFYH3ksk4Jz6VIoYdqgtOAoE7L410zLlVoYJkltEXkr+c+FEN0ZV7bBcPHrESCgY3hvQYI=
Received: from TY2PR01MB4377.jpnprd01.prod.outlook.com (2603:1096:404:10c::20)
by TY2PR01MB4569.jpnprd01.prod.outlook.com (2603:1096:404:110::12)
with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.19; Tue, 2 Jun
2020 01:20:31 +0000
Received: from TY2PR01MB4377.jpnprd01.prod.outlook.com
([fe80::2d02:425a:d816:dfdc]) by TY2PR01MB4377.jpnprd01.prod.outlook.com
([fe80::2d02:425a:d816:dfdc%6]) with mapi id 15.20.3045.024; Tue, 2 Jun 2020
01:20:31 +0000
From: "to-niwa@kddi.com" <to-niwa@kddi.com>
To: Eric Gray <eric.gray=40ericsson.com@dmarc.ietf.org>
CC: "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: Traffic (address?) type information
Thread-Index: AdY4Itf2+xIcVqVwS66BzsQ4SbMm3QAUEL+w
Date: Tue, 2 Jun 2020 01:20:31 +0000
Message-ID: <TY2PR01MB4377DBD4CF174EFF98546A57908B0@TY2PR01MB4377.jpnprd01.prod.outlook.com>
References: <MN2PR15MB310373DBA713D310A79824E8978A0@MN2PR15MB3103.namprd15.prod.outlook.com>
In-Reply-To: <MN2PR15MB310373DBA713D310A79824E8978A0@MN2PR15MB3103.namprd15.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dmarc.ietf.org; dkim=none (message not signed)
header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=kddi.com;
x-originating-ip: [27.85.176.7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a3ca9c2a-344c-4e61-6f5e-08d80693246f
x-ms-traffictypediagnostic: TY2PR01MB4569:
x-microsoft-antispam-prvs: <TY2PR01MB456904467D39AF9403F3568A908B0@TY2PR01MB4569.jpnprd01.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0422860ED4
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 0EyskrG8NJDm7xAmccObj7ZGQYVnyQUj91dVLVFp+Gi2RqIjbAxOVPJ6gj8cTwuEh2IN6Llo8Ax1N11WYd9BVd04KXKh5mwn+7vW/FnjcrH59hS5HbPoT27NFVEBPQQtAzXIBiF4v3Uhe9w0G6FQN8QxWxuNWTszTtsjewWCwOyUNI+BnD4UC/PxKryNOOn1wtE1oBTsap+Tmx24uJhnWvL3DKZrywSk3rD44GuLMYAwb8Oh8DlOhX94sGVohvMIEBJwLoCelLddWQ311nnS6eO8HVRwjxKn/8Tl+EtvW/g0kY/RbZ/MP8Zm3Fr1RuEqSXq+b0yFA474qhXTMQP3wA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;
IPV:NLI; SFV:NSPM;
H:TY2PR01MB4377.jpnprd01.prod.outlook.com; PTR:; CAT:NONE;
SFTY:;
SFS:(4636009)(346002)(366004)(376002)(396003)(136003)(39860400002)(6506007)(53546011)(186003)(26005)(316002)(55016002)(8936002)(52536014)(8676002)(7696005)(478600001)(85182001)(9686003)(83380400001)(71200400001)(4326008)(2906002)(5660300002)(33656002)(76116006)(66946007)(66556008)(66446008)(66476007)(64756008)(86362001);
DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: ftGuRoLMIj1qqSaCzr2GNtftui4jeD5gnouReG0sx1mNlNcJaeTAGgLy89gbFV+rEluzyUdG57NOachdvILqjNC62VxYe00wVI/oyBn+wUsuQCGsQiYwKwFzLBNlUPTM7SFy3WTNV4hSORHJiZ067l1B9OvDbQetO2QjnaZIYoIJiTuyUBE1UUT7aPL7VdsCN7cmnBJV5JVJb/TXFtwLpJzC/07s2006QNSoqn5SfbMuSReS8wj/68BqA2Iy0Xnb/A/eMaudD5Dbrx6C1S6I0nYNVwTLMovlVCNjM9fJPgMVSnkgllcEcGd7rRSJ0YZc9g9JxPywJbQcSIDatF9orvmHDMoXB9yodbUrDm2xW0MuTUdzWQPJ92qZ6amrY2yqh58gxk2IM26nsTU5V+/UZsqCx/bxmif6gYUebLcORBteWEs+WbMJm/j1bT4qnHu/TfJCm3EuRhOjnMA1yVhmRVnbqmNu0AxMkviNxWDiTZA=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: kddi.com
X-MS-Exchange-CrossTenant-Network-Message-Id: a3ca9c2a-344c-4e61-6f5e-08d80693246f
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jun 2020 01:20:31.3497 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 040b5c43-0c27-49b3-b8e6-cdec886abcee
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Vd/7KZJqL1GBShuvNgaoqbf+SBhurH7fBv4ilez0G9qbTxftZaQOJVP94w5M8AcWRWYa7kkJMqGWIGeSuC+NAA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY2PR01MB4569
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/vXoJCdxPbUxjuwtVH9q9I1J39gM>
Subject: Re: [Teas-ns-dt] Traffic (address?) type information
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, 02 Jun 2020 01:30:37 -0000
I agree with Eric. TSC NBI and then service request for TS need to include ingress attributes to TS. The purpose of TSC NBI is to allow outside of transport network(e.g, 3GPP system, customer) to control TS. Traffic comes from the outside actually, and therefore TSC NBI should include such ingress information. If not, TSC needs other interaction methods to understand it in addition to TSC NBI. It would lack usability of NBI...I think. Tomo --- ************************************************************ Tomonobu Niwa KDDI Corporation TEL: +81-80-5074-9346 E-Mail: to-niwa@kddi.com ************************************************************ -----Original Message----- From: Teas-ns-dt <teas-ns-dt-bounces@ietf.org> On Behalf Of Eric Gray Sent: Tuesday, June 2, 2020 12:54 AM To: teas-ns-dt@ietf.org Subject: [Teas-ns-dt] Traffic (address?) type information On the question of possibly including the traffic types (IPv4, IPv6, Ethernet, unstructured) as an additional parameter of a Transport Slice service: I guess I really need to ask this question, first: Under what circumstances would this information not be explicitly known in advance by whatever higher-level entity it is that is making the request (via the TSC NBI) for a transport slice service? If the higher-level entity does not know what the available capabilities are for making transport slice service requests (i.e. – what connection points are available, how those connection points are to be reached, what PDU format they are capable of handling, etc.), it is likely that this higher-level will need to make arbitrarily many requests before arriving at a combination that works (i.e. – the NBI interaction results in success), as it goes through an iterative “guessing” process. It may be that there are multiple ways of doing this, but I believe it is likely to be the common case that traffic is expected to arrive at a transport slice service ingress with a specifically defined format and encapsulation that allows that ingress logical device to determine to which transport slice that traffic applies. Further, I also believe it very likely that the payload (at least) of the received traffic is expected to be delivered via the transport slice service (exactly as is) to the transport slice service egress. Are these assumption incorrect?
- [Teas-ns-dt] Traffic (address?) type information Eric Gray
- Re: [Teas-ns-dt] Traffic (address?) type informat… to-niwa@kddi.com
- Re: [Teas-ns-dt] Traffic (address?) type informat… Jeff Tantsura