Re: [arch-d] Invite to webex side meeting 03/25, 8:00 AM on "New IP Architecture and Protocols".

Toerless Eckert <tte@cs.fau.de> Tue, 24 March 2020 01:51 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 9AC7D3A0ECC for <architecture-discuss@ietfa.amsl.com>; Mon, 23 Mar 2020 18:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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 bSC3QJneO4DZ for <architecture-discuss@ietfa.amsl.com>; Mon, 23 Mar 2020 18:51:17 -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 1B8893A0ECB for <architecture-discuss@ietf.org>; Mon, 23 Mar 2020 18:51:16 -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 9914B548049; Tue, 24 Mar 2020 02:51:11 +0100 (CET)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 9235B440040; Tue, 24 Mar 2020 02:51:11 +0100 (CET)
Date: Tue, 24 Mar 2020 02:51:11 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Message-ID: <20200324015111.GB30574@faui48f.informatik.uni-erlangen.de>
References: <20200320223801.GU30574@faui48f.informatik.uni-erlangen.de> <8e49e49b-3e56-ea18-7faf-75623f14f548@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8e49e49b-3e56-ea18-7faf-75623f14f548@cs.tcd.ie>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/GsvgPofqOTmZFIpvCXO196AIjGo>
Subject: Re: [arch-d] Invite to webex side meeting 03/25, 8:00 AM on "New IP Architecture and Protocols".
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: Tue, 24 Mar 2020 01:51:21 -0000

Stephen,

1) Wrt to side-meeting announcement:
In a similar way as you had planned for a side-meeting for Chirp,
we had planned an inofficial side meeting to offer discussing this
drafts topic until corona hit. So we just tried to set up a a virtual
inofficial side meeting as good as possible without any IETF
online collaboration tool support for such inofficial side meetings.

2) Wrt to discussion on a list vs. side meeting:
A lot of new -00 work to the IETF is first brought in front of a fitting
in-person IETF audience before being dicussed at length on lists, especially
when its not incremental work. In our case, this work was predated by
the IETF106 inofficial side meeting, after which we started to write
down the -00 draft and tried to find the best community to discuss this
with. Everybody told us to use architecture-discuss@ief.org.

3) Wrt to architecture-discuss@ietf.org being an IAB activity:
https://www.iab.org/mailman/listinfo/architecture-discuss
""The architecture-discuss list serves as a technical discussion forum for
all members of the IETF community that are interested in larger
architectural issues. ... ""
I do not see IAB being mentioned in the text at all. Maybe you want
to refine that text if the list is assumed to be subject to specific
IAB regulations not described yet. I would hope it is not, because
the current scope definition is IMHO very good.

4) Wrt. ICS invite "cheeky to cast .. sort-of official"
I think its clear now, that this ICS was a tragic accident by a third
party. I specifically DID NOT include an ICS because it clearly would be
too invasive on a list like architecture-discuss!! I can also not remember
(maybe i am wrong) that this list is used for official IAB
announcements / meeting invites either.

5) Wrt. "a bit more style"
Always happy to improve my collaboration style.
Let me know what is missing given above explanations.

Cheers
    Toerless

On Fri, Mar 20, 2020 at 11:03:42PM +0000, Stephen Farrell wrote:
> 
> Hmm,
> 
> On 20/03/2020 22:38, Toerless Eckert wrote:
> > We suggest to direct followup discussions to
> > architcture-discuss@ietf.org if you think it is of interest to the
> > IETF.
> AFAIK this is basically an initiative driven by one or
> a small set of vendors. It is not an IAB activity and
> this list is. ISTM somewhat cheeky to cast this as if
> it were sort-of "official" by sending ICS invites to
> this list and suggesting this list be used for follow
> ups. I'm saying that as an individual and have not
> asked other IAB folks what they think, but again
> speaking personally, I'd be much happier if people
> and organisations had a bit more style.
> 
> S.

pub   RSA 4096/7B172BEA 2017-12-22 Stephen Farrell (2017) <stephen.farrell@cs.tcd.ie>
> sub   RSA 4096/36CB8BB6 2017-12-22
>