IETF Logo Mail Archive

Re: [arch-d] ETSI launches new group on Non-IP Networking addressing 5G new services

Victor Reijs <victor.reijs@sidn.nl> Fri, 17 April 2020 10:45 UTC

Return-Path: <victor.reijs@sidn.nl>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759293A088C for <architecture-discuss@ietfa.amsl.com>; Fri, 17 Apr 2020 03:45:56 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, 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=sidn.nl
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 FhYuq7I-ijSl for <architecture-discuss@ietfa.amsl.com>; Fri, 17 Apr 2020 03:45:54 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2067.outbound.protection.outlook.com [40.107.20.67]) (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 289983A088A for <architecture-discuss@ietf.org>; Fri, 17 Apr 2020 03:45:53 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=T4IlDOI4xNNoCSUQ8IW53N6mb+wjeYW5a7LTx8GD/kUREpgV/njoUrlrW6C5c3WOnL3rvZjAX/U/GM/heLXkRN+Ih0urzyK7QSvOftvp3JHYDUN2ij1UCEy14jlsTzph9RCbb/31/M8Ofk2Q1yzwbMKRrPWQXw5VdNPFKzx8TsIPTZoBYZ49YmgXzE1MHy/pUpc+VBISANfmwc1nHJWiF9S6uj1oJ6XMYvLCe0ASExqcvxkXZTNWHeNBvMlB5iFZAlcwI6NamQ3AFPOuhHHhkaeRI99Hj4/v4Ym28ATDoOXrOcVkfXT+w7uRrXe3ug/c+9OWhMIIuFXrPJV/+tqr/A==
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=kDYWWDIAriyDybvuaUiqpBY2odpDwbWxjJL+72OAofY=; b=WL1l+1e2sIJMS9SHfl8N5IV/299me+K5eMUDIC7mg2abBSordLoX+mVT5mjoboe61V7hEVx1I91IAQLlBjJ+PeOeYSYO2ryphBSGdCvfxIErmMF/d1PN0Ir414Qqgb7IzLfG1B22TCTmesrpkIt8chwEQvnw7+AjUVZUqUm76EnsQScflgo/Pezrx1GBENJ2Y8YDwwrjcx44buNOGdsRnkYjTOssQLE6USDo2pK0zIAxQ2oxkm9OzWfi+3rM/TR/N8yssJroJ+JBPEsyjuYoLJhWCT1J5EcJ44uG6jULtszweBfVLhxWys8l5BdM78glMcrWl+XBdH2o1XGriKItAA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sidn.nl; dmarc=pass action=none header.from=sidn.nl; dkim=pass header.d=sidn.nl; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sidn.nl; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=kDYWWDIAriyDybvuaUiqpBY2odpDwbWxjJL+72OAofY=; b=bwAVo1UPFqhB6fqiFGzKaQK+t5z0eANt1UD2/vXVjQGTKFC5q+HLX4HZJs5ex7wX13gJDOlGhM1AfZyeWWCgamyatoFztvWMCQd5ouGnJgi16BPxSwZrYuNuoBMn/p2SIzOLlbJskn3rJ234XuPkyA5d4mAg9LpGpmQuzBqSEJo=
Received: from PR3P194MB0602.EURP194.PROD.OUTLOOK.COM (2603:10a6:102:38::12) by PR3P194MB0764.EURP194.PROD.OUTLOOK.COM (2603:10a6:102:29::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.29; Fri, 17 Apr 2020 10:45:50 +0000
Received: from PR3P194MB0602.EURP194.PROD.OUTLOOK.COM ([fe80::b575:a338:3cd4:1ee1]) by PR3P194MB0602.EURP194.PROD.OUTLOOK.COM ([fe80::b575:a338:3cd4:1ee1%5]) with mapi id 15.20.2921.027; Fri, 17 Apr 2020 10:45:50 +0000
From: Victor Reijs <victor.reijs@sidn.nl>
To: S Moonesamy <sm+ietf@elandsys.com>, Toerless Eckert <tte@cs.fau.de>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Thread-Topic: [arch-d] ETSI launches new group on Non-IP Networking addressing 5G new services
Thread-Index: AQHWDWJyhUWBPnI3wkiq6mi66DMYhahuqlAAgAALyACAAN4dAIAADIkAgADi6gCAADPdgIAAGZYAgABD94CAADYPAIAByMIAgARb1ACABKQKAIABAP0AgAAXdVA=
Date: Fri, 17 Apr 2020 10:45:50 +0000
Message-ID: <PR3P194MB06020637CFA84A4C249835419AD90@PR3P194MB0602.EURP194.PROD.OUTLOOK.COM>
References: <20200408054204.GA6005@nic.fr> <6C2A3533-7F75-45B1-9B51-19938597174B@tzi.org> <20200408194154.GJ28965@faui48f.informatik.uni-erlangen.de> <4200C5F8-9F56-4FFF-90F4-7AD76A9F4FC8@eggert.org> <20200409121941.GZ28965@faui48f.informatik.uni-erlangen.de> <C758BDF2-8CD6-4C22-90CA-6ED98DACD740@eggert.org> <20200409175431.GF28965@faui48f.informatik.uni-erlangen.de> <1e89795e-6bd9-2318-aa81-27f8327e1226@gmail.com> <4ac9e9fc-41a3-f458-566e-f0a68d26d9ea@huitema.net> <E029AEC023B1A60E3E956641@PSB> <20200416174840.GL41264@faui48f.informatik.uni-erlangen.de> <6.2.5.6.2.20200417010529.0c28ab50@elandnews.com>
In-Reply-To: <6.2.5.6.2.20200417010529.0c28ab50@elandnews.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=victor.reijs@sidn.nl;
x-originating-ip: [213.127.1.166]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 17e7993c-fad6-4701-6eb1-08d7e2bc7f05
x-ms-traffictypediagnostic: PR3P194MB0764:
x-microsoft-antispam-prvs: <PR3P194MB07648D7B650794A7EDFC63089AD90@PR3P194MB0764.EURP194.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0376ECF4DD
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PR3P194MB0602.EURP194.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFTY:; SFS:(10009020)(4636009)(396003)(376002)(39840400004)(136003)(366004)(346002)(2906002)(33656002)(7696005)(6506007)(53546011)(26005)(110136005)(316002)(86362001)(66574012)(52536014)(186003)(44832011)(5660300002)(9686003)(478600001)(8676002)(66556008)(64756008)(66446008)(71200400001)(55016002)(81156014)(8936002)(76116006)(66946007)(66476007)(15974865002)(83080400001)(18886075002); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: sidn.nl does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: yT1cwtREYKgklbcFE4jQEFRZ2Xt4gpmXEtGib9raf6U+BN3bpnZo19UP7ZPsMJYCxkhjj/jF1kgIxZX20J2GN55GtWKW6vf7dGySW3itL9bTG+/HVu3+jHQmZJpIEmDZDwMrlPcOOBxPU1qS/amer27h5CpPL96c2NtKrQANZh7eyv9f+jipaU7NIn0toCLBDDRxu/H1LdmxkX2p1oK9CN4aGkMra1Sq8pAI2V6J5ypESK/CxSMjdQvTCOMos/X/lxUPGPRlVYoNp5YxMDHsCFfRYzEXeMR4nkAy3n3bSWmwZr5YeK1oaeL9OkZbYWlC8l2EbxEwEmu3OW9yvPtD76jV2qwyGAgc1PaElghkHgwwMYhAcLHD3ONj31SpMBpJ4u063MhVFwA/5k8X9iIGc4ZourJwYz+5X7lsgih0+97ObGsDysdMZqmMXgGhZHrQGAbHTiiLOzg+c+OMF9J2FRbSjJKPrSkVGQlc1GAI3fNhzr2f0OLdF1oY42izzSACu6YQMYmanNEu0puQamVvOR4hvG1mBtIuKOITOL9ECWzd6TZKseQfegNxTU30pXw9TEj6Az2IpvHVJqdaAqK2Lw==
x-ms-exchange-antispam-messagedata: 9sAaPbf8uJHZNlnE+K4BiXufpcaKzhQsbIpapP/LsSKOBy1f0IBIk4krp44x9MLXenvK1xhuu/hDG5q3nsvtCrVhe2CcA0sSdVBcHlppqA5uhQd7821S7ihAxNUmL/EQstM3UvWhKUZ/WZ8dRt2hgQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: sidn.nl
X-MS-Exchange-CrossTenant-Network-Message-Id: 17e7993c-fad6-4701-6eb1-08d7e2bc7f05
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2020 10:45:50.8249 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ab4d3626-c1c5-4a75-ab85-427f1a644a7d
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 3v8c7CBzqnP1IfS9oPP30yJxgbysES+fvR2leiOrWWSUATtDCz9a28Y3PiKL6g+Cd5EkgExRWDGcEhq67Xy/yA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR3P194MB0764
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/0FDK1fWODXI1ARXhjMoQSIbZ7gI>
Subject: Re: [arch-d] ETSI launches new group on Non-IP Networking addressing 5G new services
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Apr 2020 10:45:57 -0000

Hello all of you,

> -----Original Message-----
> From: Architecture-discuss <architecture-discuss-bounces@ietf.org> On Behalf Of
> S Moonesamy
> Sent: Friday, 17 April 2020 11:08
> To: Toerless Eckert <tte@cs.fau.de>; architecture-discuss@ietf.org
> Subject: Re: [arch-d] ETSI launches new group on Non-IP Networking addressing
> 5G new services
> 
> IPv6 was promoted as "secure by default" as IPsec was part of it.  

[Victor Reijs] 
I can remember that when we together had a fully operational TUBA/CLNS service in Europe and US (really 90s). The missing of IPSec was one of the reason not to choose for TUBA/CLNS (beside that it was an ITU standard). TUBA/CLNS was only providing longer (flexible length) addresses. While IPv6 should do indeed secure stuff. Not much has materialise in all these years during which IPv6 needed to be developed/deployed...
But ok that is in the past.

I now read in the ETSI ISG-NIN group that the major issues not to use IP inside B5G is de additional cost of spectrum (which is quite limited) due to the large headers in IPv4/v6 and many encapsulations happening. Furthermore congestion control and QoS are really not supported and that might cause problems for real-time or time critical applications. The ICANN report (5G Technology) says that IP can all do that, but why are the ICANN arguments not (yet) convincing the mobile operators?
I think the specifications are quite clear defined by ETSI NGP's KPI (https://www.etsi.org/deliver/etsi_gs/NGP/001_099/012/01.01.01_60/gs_NGP012v010101p.pdf ) so it must be 'easy' to determine if IP can or cannot do it.


All the best and stay healthy,

Victor Reijs
Research engineer: future internet

Attendance (CEST): Mon 8.15-16.45 | Tue 8.15-16.45 | Fri 9.00-17.30



SIDN | Meander 501 | 6825 MD | Postbus 5022 | 6802 EA | ARNHEM | The Netherlands
T +31 (0)26 352 55 00 | M +31 (0)6 12 45 00 11
victor.reijs@sidn.nl | www.sidn.nl

v2.23.0 | Report a Bug | By Email