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 14:41 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 882723A0CBD for <architecture-discuss@ietfa.amsl.com>; Fri, 17 Apr 2020 07:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, 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 fuSkrclOCP4f for <architecture-discuss@ietfa.amsl.com>; Fri, 17 Apr 2020 07:40:57 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60041.outbound.protection.outlook.com [40.107.6.41]) (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 315F83A0C66 for <architecture-discuss@ietf.org>; Fri, 17 Apr 2020 07:40:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Rcth3hL1ADH/tExG7cy5jlPLIPmJtXGZd1IlPwfSslMuvBGvwZ2v05VZ5OYyXr+c5cV9GecQxp8CNExFYADVKX1mOsVyoqLAd79duOZrbCEiO+LJ7RhgiRpb4u48W7jpN+y2m5xCHceJWDxyM6TP5IUKjTF9Pf/Kb9KB322fHGRiGWqj+7mpDJ4MRgEui6GwUdeafREHdNOqr3zt2ie0uXBfgpu1Jvbg9YduTM+MybXVlGOzTPeqhtk2zwi+Za5J9ZH/kxBIUnShczr2w5S951Ot5qvmII+PFiNv4omp4ICrZMOgkLoh/K/91Py5O+Y5BhBn5rOkEOXZe8IrnF6x7w==
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=0N3fHmg28HD7Q9vCkYw5jeEW7VbyZO7vgU+EONJKz04=; b=LTeRDjMia4l449gjdwUJIwsPOnkAnSO23wTEEAQwJ8y2A6YHhalrNKWxgEfN2Q9fS4D8VYG6zDmRKQxT0sge0XUJS4WRpz1wtMPUkkpGxc9Zy91aCGITx+D1ic64o22Z+vEAarrSHfdidYKaBQz1deQkGDrNe7m36nItojOJ+SlQ8TiTWB7Z9+/87GbtcE7EQi5CBLZIVGbpWEFsdLlW+nWFdwZuuH45T8US7gY7h3vs+UVHgZLbPQIs4bWJQrX1vUJfa1rB2D7TOwUiUBkKeGME3m5Qnfa7Q1g17tPa2duhhr26+kGfaDgxpu0ZPfiEcwzLyQSNDo0dFqqTF+zdfQ==
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=0N3fHmg28HD7Q9vCkYw5jeEW7VbyZO7vgU+EONJKz04=; b=Uw/tGSW2fRNOveNv40lb3yeXENjgWWcZIti9tX13KcVXBTTlzrsJbGPhOpB78qlLJTUNj844MKCBhJ9MmfX5igVH5yzwjs3MCodbyT1nkZpoxp6XwYoOQFDW+hajPziqYr5eA1eqwLZQytLc6f45X94EMbSoU82djq7/ixyprRM=
Received: from PR3P194MB0602.EURP194.PROD.OUTLOOK.COM (2603:10a6:102:38::12) by PR3P194MB0906.EURP194.PROD.OUTLOOK.COM (2603:10a6:102:4a::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2921.27; Fri, 17 Apr 2020 14:40:53 +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 14:40:53 +0000
From: Victor Reijs <victor.reijs@sidn.nl>
To: John Day <jeanjour@comcast.net>
CC: 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: AQHWDWJyhUWBPnI3wkiq6mi66DMYhahuqlAAgAALyACAAN4dAIAADIkAgADi6gCAADPdgIAAGZYAgABD94CAADYPAIAByMIAgARb1ACABKQKAIABAP0AgAAXdVCAAEKiAIAAArMg
Date: Fri, 17 Apr 2020 14:40:53 +0000
Message-ID: <PR3P194MB06021A724D98AC6AAC9A65929AD90@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> <PR3P194MB06020637CFA84A4C249835419AD90@PR3P194MB0602.EURP194.PROD.OUTLOOK.COM> <D63B17E3-F10B-4D19-A229-582BEB0DAC7A@comcast.net>
In-Reply-To: <D63B17E3-F10B-4D19-A229-582BEB0DAC7A@comcast.net>
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: 03546282-0972-4c5c-066c-08d7e2dd54c8
x-ms-traffictypediagnostic: PR3P194MB0906:
x-microsoft-antispam-prvs: <PR3P194MB0906333FCB63E6DCC4A0824A9AD90@PR3P194MB0906.EURP194.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
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)(136003)(346002)(39840400004)(376002)(366004)(396003)(316002)(6506007)(7696005)(15974865002)(66446008)(76116006)(53546011)(9686003)(55016002)(64756008)(66556008)(66946007)(66476007)(26005)(54906003)(478600001)(186003)(44832011)(6916009)(966005)(81156014)(8676002)(8936002)(5660300002)(83080400001)(66574012)(86362001)(71200400001)(4326008)(52536014)(2906002)(33656002); 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: bqYRt0+eE5xL+oJZZg8obovDmeV+BPHk5EYxMIZ/aLd8jYjv75w2J0FL/pytR+rjVQmSNpy7zFikchj3gvsJkbmYS/H/MCXcvRE3CZ+TsQ1zGHXEG/OPhyhFOxnHspwFslCKexy9iKT/vR2kOmYXTRCCRzg9owoOVEUExoWVIca+L01pGiaWUJUxqk0P2CmRgn8oWTVpqGDlCGMqCRpTWlBFrhBHo4VAVMvZWw/Of8YrB/FQJKR4nce1+Ph4PtGHCscDQz1HMnD9YYYeH0+3rWr4c0oANwuyBTSzb+M1isPywbnlVdWTfWzYv8TOrYIN6aORzLwXw1NLulrNbhHzPoji+xT+svJc4dSjeT7Ux+G0JwhRId87Fco5+6lI6ITP2lVUoyMCFUkaO7ITsU90A6vqhbH7RcD98J5HCLdN8GugHT3357NOZzz0n+Hh77SSdiHDinPYl2xlgk3LAcL2iXQbxmqWFusV4+MoQ1+A6FcCSishci6Kn7SbRSELkvuhJUUacY2FF0PH962QFkxfyA==
x-ms-exchange-antispam-messagedata: BXEn53kZdwr9OlCR5ZwQERzp9zwijeLMZEX6lRhjdKQ0AI2A9decG7zhD2mHud0aQTWcAI2L7RxY5pEfb4SuxHlJUPRdzsgEjYoZwQkkYxhdusFK3CaBTkczQW3QmDxNjuRJEzmy5LWIo6H4C2qT1Q==
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: 03546282-0972-4c5c-066c-08d7e2dd54c8
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Apr 2020 14:40:53.3482 (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: nHwiWZqxmPaNoIiSFaU/aARTAC6vBf2fyiG3nmwYaG+BvP2qzsMe8P2ovWQE/tNBlh0ciI3NTkb8sCfsUVwMgA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR3P194MB0906
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/jqmm12UR-vnfM_2CSv9zjKq3yMo>
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 14:41:02 -0000
Indeed I was running the TUBA/CLNBS project worldwide😉 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 > -----Original Message----- > From: John Day <jeanjour@comcast.net> > Sent: Friday, 17 April 2020 16:31 > To: Victor Reijs <victor.reijs@sidn.nl> > Cc: S Moonesamy <sm+ietf@elandsys.com>; 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 > > One minor correction. > > TUBA/CLNS was an ISO effort. It is true that it does have a ITU number but nearly > all OSI standards had both an ISO number and an ITU number. > > The ITU consistently opposed connectionless and CLNP at every opportunity they > had starting with the OSI Reference Model to keep connectionless out of OSI. The > first amendment to the OSI Reference Model was to add connectionless and the > ITU fought that tooth and nail. It was only through the efforts of *computer > companies,* not ITU members, that connectionless and CLNP was there and the > work progressed. > > The ITU never wanted CLNP and the IETF obliged them. > > There was more CLNP deployed and operational in the Internet in 1992 than IPv6 > in 2014. > > The ITU owes the IETF an immense debt of gratitude for keeping this issue > uncertain for the past 28 years. This has greatly facilitated the ITU's great success > in bringing the IETF even closer to the ITU direction. > > Congratulations. > > John > > > > > On Apr 17, 2020, at 06:45, Victor Reijs <victor.reijs=40sidn.nl@dmarc.ietf.org> > wrote: > > > > 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_NGP01 > 2v010101p.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 > > _______________________________________________ > > Architecture-discuss mailing list > > Architecture-discuss@ietf.org > > https://www.ietf.org/mailman/listinfo/architecture-discuss
- [arch-d] ETSI launches new group on Non-IP Networ… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Carsten Bormann
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Stephane Bortzmeyer
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Bob Hinden
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Carsten Bormann
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Tony Li
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Scott Brim
- Re: [arch-d] ETSI launches new group on Non-IP Ne… John C Klensin
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Spencer Dawkins at IETF
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Spencer Dawkins at IETF
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Stewart Bryant
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Stephane Bortzmeyer
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Stephane Bortzmeyer
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Lars Eggert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Lars Eggert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Stewart Bryant
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Alexander Pelov
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Spencer Dawkins at IETF
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- [arch-d] Other SDOs (Re: ETSI launches new group … Carsten Bormann
- Re: [arch-d] Other SDOs (Re: ETSI launches new gr… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Marie-Jose Montpetit
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Lars Eggert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Bob Hinden
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Henning Schulzrinne
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- [arch-d] Beyond Best Effort ?! Re: ETSI launches … Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Cedric Westphal
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Jeff Tantsura
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] Beyond Best Effort ?! Re: ETSI launc… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Tony Li
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… tony.li
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- [arch-d] our troubles [was: ETSI launches new gro… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Randy Bush
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Jeff Tantsura
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] our troubles [was: ETSI launches new… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Uma Chunduri
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Christian Huitema
- Re: [arch-d] ETSI launches new group on Non-IP Ne… John C Klensin
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Vittorio Bertola
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Geoff Huston
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… John C Klensin
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Victor Reijs
- Re: [arch-d] ETSI launches new group on Non-IP Ne… John Day
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Victor Reijs
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Toerless Eckert
- Re: [arch-d] ETSI launches new group on Non-IP Ne… John Day
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Victor Reijs
- Re: [arch-d] ETSI launches new group on Non-IP Ne… John Day
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Brian E Carpenter
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Dino Farinacci
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Tony Li
- Re: [arch-d] ETSI launches new group on Non-IP Ne… S Moonesamy
- Re: [arch-d] ETSI launches new group on Non-IP Ne… Victor Reijs