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

Toerless Eckert <tte@cs.fau.de> Thu, 09 April 2020 12:34 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 057963A08EE for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 05:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level:
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, 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 llAzEQ2VoSxw for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Apr 2020 05:34:07 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff: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 1281C3A0926 for <architecture-discuss@ietf.org>; Thu, 9 Apr 2020 05:34:06 -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 7161D548048; Thu, 9 Apr 2020 14:34:02 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 67D3F440040; Thu, 9 Apr 2020 14:34:02 +0200 (CEST)
Date: Thu, 09 Apr 2020 14:34:02 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Carsten Bormann <cabo@tzi.org>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, architecture-discuss@ietf.org
Message-ID: <20200409123402.GB28965@faui48f.informatik.uni-erlangen.de>
References: <60a10451-5fbd-fcec-5389-7a72870dcc84@gmail.com> <6A3A4410-A889-46C7-8FD5-7C5AA85486A1@tzi.org> <20200408054204.GA6005@nic.fr> <6C2A3533-7F75-45B1-9B51-19938597174B@tzi.org> <20200408194154.GJ28965@faui48f.informatik.uni-erlangen.de> <C6378454-EE7A-4CBB-A109-C0D969A81715@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <C6378454-EE7A-4CBB-A109-C0D969A81715@tzi.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/mVLB54M3c40ewsIpVoR4o0a1_HM>
Subject: Re: [arch-d] Other SDOs (Re: 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 12:34:09 -0000

On Thu, Apr 09, 2020 at 02:26:50PM +0200, Carsten Bormann wrote:
> On 2020-04-08, at 21:41, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > When would have
> > IETF leadership ever have tried to explain/help IETF attendants to
> > do better work in another SDO ?
> 
> I???m not sure WG chairs qualify as ???leadership??? in your view (they do, in my view), but that has been a constant theme for us in IoT-land.

Ok. great. I did mention i can imagine this to happen better in APP/ART,
if it also happens in IoT land, all the better. I was just
coming from not seeing it for ITU-T.

Cheers
    Toerless

> > Which meeting did i miss about this ?
> 
> Well, we didn???t quite start by saying ???this is the way we, the IETF, will work with other SDOs, now eat it???.  We started by working with other SDOs and tried to find out what they actually need.
> Interestingly, one of the homes of that work is the T2TRG, as it turns out that IETF and other-SDO work isn???t already perfectly aligned, so you need a wider view (and a longer outlook) to really be useful.
> 
> I???m sure we are not yet nearly doing enough of this, but you can???t say we (as an organization) ignore working with other SDOs.
> 
> > Maybe with the small exception of RTCweb and W3C (or maybe even more
> > in APP, i am not that much involved there).
> 
> It may help that some of the IoT work is in ART (which encompasses what previously was APP).
> 
> Grüße, Carsten