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

S Moonesamy <sm+ietf@elandsys.com> Wed, 08 April 2020 22:51 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 AC3433A18EB for <architecture-discuss@ietfa.amsl.com>; Wed, 8 Apr 2020 15:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level:
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, 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 6yyo8BFmdhMU for <architecture-discuss@ietfa.amsl.com>; Wed, 8 Apr 2020 15:50:56 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 694C53A193C for <architecture-discuss@ietf.org>; Wed, 8 Apr 2020 15:50:56 -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 038MoRoI027849 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Apr 2020 15:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1586386240; x=1586472640; i=@elandsys.com; bh=5ApZZGb1ueISlxURmZMC6rfyulnSkt1vPRTz8g8DJoI=; h=Date:To:From:Subject:In-Reply-To:References; b=liopvVER1ydRrwriPwyWu6aog3qjyoxgPaOZQ0aKkBrTzYZXALcwMYJV7+Nz7lwG2 8/AaauHwd70IMsRIWVBuUwXr3rDpVKJC97TkBOzVEE5NoGIa772uVF7rrOnZFbYWEp am3R19jUHXH3ZQkS2G2kH1YpS9Yk1jc9hqajnhG8=
Message-Id: <6.2.5.6.2.20200408142709.0b957348@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 08 Apr 2020 15:40:09 -0700
To: Toerless Eckert <tte@cs.fau.de>, architecture-discuss@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20200408195622.GK28965@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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/LWIH2AlzH0YAejPJhH3srjZCslA>
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: Wed, 08 Apr 2020 22:51:01 -0000

Hi Toerless,
At 12:56 PM 08-04-2020, Toerless Eckert wrote:
>Alas, there is really no good investigative journalism
>in our field that would expose how this is e.g.: a fight
>for votes in next ITU-T round of decision making.

It is a cyclic event.

>The key word of my criticism is "only". None of
>what done in liaison is per-se bad, its just too
>isolated from the communities. But i am of course
>repeating just my core ask to have a more open
>architecture evolution forum in the IAB/IETF to
>be able to more effectiely pull in possible
>contributors from other SDOs.

My guess is that another SDO would have its own culture.

>Heck, think of a track where you start to inviting
>3GPP, ETSI, ITU-T and other SDO presenters, ask
>them to present what they do and their thoughts how
>it should impact the future of IETF work. And make
>sure the time planning allows double the amount of
>time for IETF participants to discuss. And hopefully
>help them to understand where/how that integration could
>be suggested/done via specific contributions to IETF.

Have you watched a presentation of IETF work in a non-IETF 
forum?  Sometimes, it is not an accurate reflection of the IETF discussions.

I'd say that the above suggestion is worth a try instead of viewing 
it through pessimistic lenses.

>(and be careful in selecting whom to invite so you do
>  not end up with administrative slide deck readers).

Yes.

>Indeed. The problem though is to figure out how to get to
>more effective forms of actual architecture/engineering
>process and not to better marketing mechanisms. Then again,
>given how ossified our industry is, there is unfortunately
>something to be said about scaring people to wake up, even
>though i do not like it.

I don't think that businesses would remain idle if there was an 
effective way to change things over the short term.

Regards,
S. Moonesamy