[Teas-ns-dt] Traffic (address?) type information

Eric Gray <eric.gray@ericsson.com> Mon, 01 June 2020 15:59 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 4E4503A1189 for <teas-ns-dt@ietfa.amsl.com>; Mon, 1 Jun 2020 08:59:28 -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 Yu-zPq9ghoYs for <teas-ns-dt@ietfa.amsl.com>; Mon, 1 Jun 2020 08:59:27 -0700 (PDT)
Received: from NAM10-BN7-obe.outbound.protection.outlook.com (mail-bn7nam10on2088.outbound.protection.outlook.com [40.107.92.88]) (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 C90FE3A10EF for <teas-ns-dt@ietf.org>; Mon, 1 Jun 2020 08:53:50 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iznB7VjHgJzxlx53VMCE745a3TXhZC11VvUorFx+2mc27YIecqLKhDo1DfJiXqn4PpHKLwc/FF59kaSuGiWa0llLi6nt74dGE/c5ePmiNU03pxA75CvsINmunrBsKOLoGs2Hj/cr6FxlddwKoOTTCJkDPza308WhJO90CgvXc8DpkApNU3P2ePxSq74/dliybtTxMhh+G4Z+dHw10CnLcDyXJOz5c1RsUvBFDbvDpDAUs39VY0O8g9VnnqNSH2WskNvxQjkxIu5cUxntWW8WsOM30J4OOUq7rSALT0EilAHvW63TpTq4yxaNLyhBur1SD9Ty5kZ3DPjr+4eP6zeWyA==
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=5vbmojI+ylBLXsX4g0AoJGsalkL3NTbgbneLqTgDPhs=; b=Ma1/tRXIpEds8I5374HjH8PnRrlsZegs36d8u4NikELNIQ/jCT4FN3vSzv1pxqKZpTuJEJaq8CFDV7IL+L3kLWKFSIWifn9qq+x/orpP/7QZ10RxxKCaHpS/IcAWGflAitaqmLzQqqrAIeEu5/hLnVy8YIxBiyX+2bfEJAIqGQuIk15gQY0JEdx3B+gcSHYE8q24a1aC5l1RRVQyQd1wVU8hHWbeFto+SfIpRXmnOurH5wh7i75VDK2QV4YOoSmXsdHHgt8+OXMdonYEskoHUY1klqJ1YZu0UGEhB/aZ9dPsW1FHKJTxvPk8kK8eJrrnwwJCRl/nBAgFC3X8ke/glA==
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=5vbmojI+ylBLXsX4g0AoJGsalkL3NTbgbneLqTgDPhs=; b=goSATvOm4KhjSpRrGD6R4pR9ghO5rgNIdsnq03qU37Q3xFK+GnEEKNS4kSMn5NweIMPW1s24u5B9U6D0j5hcNqt6zPWyHGqZqToaHW4u+Lfza2AgecwBbY+Hz0N2/JkfOM6hwz9StngqFvO18iFJj7C98YkRvDboXzOrNrb7YrM=
Received: from MN2PR15MB3103.namprd15.prod.outlook.com (2603:10b6:208:f9::10) by MN2PR15MB2976.namprd15.prod.outlook.com (2603:10b6:208:f6::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.17; Mon, 1 Jun 2020 15:53:48 +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.3045.024; Mon, 1 Jun 2020 15:53:48 +0000
From: Eric Gray <eric.gray@ericsson.com>
To: "teas-ns-dt@ietf.org" <teas-ns-dt@ietf.org>
Thread-Topic: Traffic (address?) type information
Thread-Index: AdY4Itf2+xIcVqVwS66BzsQ4SbMm3Q==
Date: Mon, 1 Jun 2020 15:53:48 +0000
Message-ID: <MN2PR15MB310373DBA713D310A79824E8978A0@MN2PR15MB3103.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2601:85:4680:3329:b458:376:4362:6ee6]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 74895b35-1852-487b-eaa8-08d80643f911
x-ms-traffictypediagnostic: MN2PR15MB2976:
x-microsoft-antispam-prvs: <MN2PR15MB29763E542B8AA7411B11E005978A0@MN2PR15MB2976.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0421BF7135
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: aX81lo9SLUGJHAOYVlTvr5vm0vBNtaCPJhCfAysuA/OvwxaNh0cL9vM4yt8PYAfIsZqvAdner0A3eV7CuE4x6RvpJPPRhSt+LLN3Xqyg4ffkPQRLwCjomNbU0vaL7y7tC4ceRq7d3C9DlJI4C/bO8B8XdSPwlnZ9xmOF7g+I5yIYJJpE4uorrpKKBirslkS6F88O+OofPnFbQ9YCoOqluT4jdClIjKstwURJ+oqZMgqr1sLyPnLeomQqGxIVfFwyb3El4zETCT09DeAWzR07bHbHuPJiAIDMkbT07WG/wUhFE2m7ULHy6Tgs+rL9ZrvvQFqJ+6TfBee+l7xkXac8WA==
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)(376002)(366004)(396003)(346002)(39860400002)(136003)(5660300002)(6506007)(8676002)(478600001)(66556008)(44832011)(76116006)(86362001)(55016002)(66446008)(64756008)(66476007)(66946007)(71200400001)(9686003)(33656002)(83380400001)(316002)(2906002)(6916009)(8936002)(186003)(7696005)(52536014); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: KD4ViUfodtEB6k7J7sByg0jBFPu8bmrVO1vXMEWGJX+qC1AXnGMilAG4qzZqNnUptu2YkimvogscHGO9tW7XVYZNi+bEyIeA9/WLZg8dOwVha/aOxljiZmjRyDvGCF6b9q7vTo2MsGnV/v+cENgCLG+GEcPmPmOOlLCCSASnwiwUzlLmOB9FvdkHdIAdaZMhsv1TdDlsodn+fWxoFnfMSaFZHZxxTu4qKTyf2dA3IphMegjgUtxszB7QJF3VNm/5pYKEpx4aq93gdG1JkvNSbR7KgUIeZVYSz+wM8DOvvLajQxmYSjq6kys32A9u6N+IjTDlLdA+2jveL1c17Shnb6Yx3F6FHO5nJ7CGE/Y/eiZMd56dt9Nd+0P9h5w2E754LvsunHvJdgZWpNX+J7m/JWPe2maYV2c9x4utMBB6UkeiOnGb64Hgv2Knpvhf3NgksWWH23mOGPsG+waexOpRArg+x2iqyCI5OSKuvDI94O6ktVm7eTf/9/lNxvcaMrc5Tn5ofP30tU5qCnjE4ArOkikiWABpw9yKWpsFwBYmqvQ=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR15MB310373DBA713D310A79824E8978A0MN2PR15MB3103namp_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 74895b35-1852-487b-eaa8-08d80643f911
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Jun 2020 15:53:48.2292 (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: 6nsUN0c2j6ehYfFlHViJMeXctvbz01Tn7z0zcOPn0X0SL1Q/MRe1CIhL1jn0BCl+4eN+neB4AMFS+e7k7xGC2w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR15MB2976
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas-ns-dt/WcCEQUXqMeyRgywTFUyNF3om5PQ>
Subject: [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: Mon, 01 Jun 2020 15:59:28 -0000

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?