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

Toerless Eckert <tte@cs.fau.de> Thu, 09 April 2020 11:30 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 DEBD63A088E for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 04:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.651
X-Spam-Level:
X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 tLc9DJuoRY-q for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 04:30:24 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F00663A088D for <architecture-discuss@ietf.org>; Thu, 9 Apr 2020 04:30:23 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id D4D5A548042; Thu, 9 Apr 2020 13:30:17 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id CA88B440040; Thu, 9 Apr 2020 13:30:17 +0200 (CEST)
Date: Thu, 09 Apr 2020 13:30:17 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: architecture-discuss@ietf.org
Message-ID: <20200409113017.GX28965@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> <6.2.5.6.2.20200408222422.0ae60b50@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20200408222422.0ae60b50@elandnews.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/WG-kAf2bt3uPf5xdZflhrGF0ikw>
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 11:30:26 -0000

On Wed, Apr 08, 2020 at 11:10:38PM -0700, S Moonesamy wrote:
> 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.

Sure, and lets assume everybody does an excellent job in that:
Where on the IETF schedule is the open meeting with those liaisons
to discuss with them ? (same thing other side of course too).

> > ? Sorry, to much thread cutting... which suggestion ?
> 
> It was the one where you mentioned several SDOs and having them presenting
> what they do [1].

Ack.

> > 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. :-)

Its crazy that in research (IRTF) and protocol development (IEF),
 the groups are started by pet topics of the community, and leadership
provides process management and adult supervision.

And in architecture its the opposite: Work has to be pet topics
of IAB and the community has to provide adult supervision.

WHich model works better ?
Why is architecture not using the model of research and protocol
development ?

Cheers
    Toerless

> Regards,
> S. Moonesamy
> 1. https://mailarchive.ietf.org/arch/msg/architecture-discuss/D8Mxm3e4BPSf15JDXzfITNlwjbo/
> 2. I would rate the probability of success as very low.
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss

-- 
---
tte@cs.fau.de