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

S Moonesamy <sm+ietf@elandsys.com> Thu, 09 April 2020 06:11 UTC

Return-Path: <sm@elandsys.com>
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 6AA693A0BFB for <architecture-discuss@ietfa.amsl.com>; Wed, 8 Apr 2020 23:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 OPaPPEXqtgN6 for <architecture-discuss@ietfa.amsl.com>; Wed, 8 Apr 2020 23:11:20 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id CAB2E3A0BFA for <architecture-discuss@ietf.org>; Wed, 8 Apr 2020 23:11:20 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.117.21]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0396AriY013631 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Apr 2020 23:11:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1586412665; x=1586499065; i=@elandsys.com; bh=dQ5qoTstV1H3cHTprRwRUWKFYTHkbCQx3ExkL4t3u38=; h=Date:To:From:Subject:In-Reply-To:References; b=0enHaBhtgq04TmoCmBGcCihO9CPD4+Gg1eItXfmeU8phWBcYZn02Pz1zMArgOgtqm KQMPTublXaC080Amyb+lJYikTz9IkWo67oHHu6ezxuvGBCALtxwn8fopqm7sonjRfb 69D7K1rF2hnZ2fx1DWDmrdpjOm7AmU969UfPJJSQ=
Message-Id: <6.2.5.6.2.20200408222422.0ae60b50@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 08 Apr 2020 23:10:38 -0700
To: Toerless Eckert <tte@cs.fau.de>, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20200408230852.GS28965@faui48f.informatik.uni-erlangen.de>
References: <60a10451-5fbd-fcec-5389-7a72870dcc84@gmail.com> <6A3A4410-A889-46C7-8FD5-7C5AA85486A1@tzi.org> <20200408055530.GC28965@faui48f.informatik.uni-erlangen.de> <6.2.5.6.2.20200408102605.0ba41040@elandnews.com> <20200408195622.GK28965@faui48f.informatik.uni-erlangen.de> <6.2.5.6.2.20200408142709.0b957348@elandnews.com> <20200408230852.GS28965@faui48f.informatik.uni-erlangen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/AOEq-ROa7OQVvSRSUv7jwg7U3q8>
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: Thu, 09 Apr 2020 06:11:24 -0000

Hi Toerless,
At 04:08 PM 08-04-2020, Toerless Eckert wrote:
>If all you have is a liaison statement you will
>always wander on thin ice attempting to extrapolate
>the meaning between the lines / discussion.  Goes both ways.

There are liaisons who are expected to get the message across.  In 
theory, that should prevent the two sides from misunderstanding the 
(formal) statements.

>? Sorry, to much thread cutting... which suggestion ?

It was the one where you mentioned several SDOs and having them 
presenting what they do [1].

>As said in the othre thread, i don't think in an industry as
>mature as ours and as capital intensive, that there is
>a lot you can change short term and from a single player.
>Hence the need IMHO for IETF to have to rethink to promote
>and support more poactive longer term architiecture discussions.
>(and if you don't like the word architecture, use design, strategy,...)

I'll have to review past discussions (unrelated to this thread) to 
provide a good answer.  It may be possible [2] to make some short 
steps, e.g. have a venue for a discussion.  Someone will have to 
convince the IAB members to include that in their list of pet projects. :-)

Regards,
S. Moonesamy
1. 
https://mailarchive.ietf.org/arch/msg/architecture-discuss/D8Mxm3e4BPSf15JDXzfITNlwjbo/
2. I would rate the probability of success as very low.