Re: [arch-d] iesg: Re: Updates on IAB mailing lists

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 20 April 2020 21:54 UTC

Return-Path: <jmh@joelhalpern.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 B15843A110B; Mon, 20 Apr 2020 14:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.198
X-Spam-Level:
X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 S_i5rrA5Lj0p; Mon, 20 Apr 2020 14:54:17 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D243A110C; Mon, 20 Apr 2020 14:54:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 495gT46QDNz1p3YZ; Mon, 20 Apr 2020 14:54:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1587419656; bh=4FSIWOXKqvU4BYBzNlu6Jmi3XWKQ0EfOQ8Yg2junXk4=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=rPpPa75zdkBRIT0uzJRb92aUJ4QEyTY0iGuap+DGzOipLW+VVs/aqiUR9/6Qhao1r AHebnZwTYWIAorzUEoNhgA7S6tsKz+htVhHIkdLmmLLzhuBQihayId28B9VMDCHjR3 0F72pK9ikhzLH7ndO60pc21LMCgzdz7h8LRociZ4=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 495gT42LVbz1nsfH; Mon, 20 Apr 2020 14:54:16 -0700 (PDT)
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Cc: "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>, IETF-Discussion list <ietf@ietf.org>
References: <20200420184456.GG5351@faui48f.informatik.uni-erlangen.de> <c8c9947a-9fa5-e208-6560-01f31067a590@gmail.com> <CAHBDyN6b_GFDaxRj1v4n==NjZJMXt11sBSsRcik7R1b0kN4yUA@mail.gmail.com> <93a7ae7f-c2bc-a009-baa9-8671de5ee384@gmail.com> <CAHBDyN5Jf1amBHFXwWVtG1De74M7bvTZaxiX9L1x6TtzNG-nmw@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <1b3a6b47-a4b4-1527-0adc-77d4421d8947@joelhalpern.com>
Date: Mon, 20 Apr 2020 17:54:12 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0
MIME-Version: 1.0
In-Reply-To: <CAHBDyN5Jf1amBHFXwWVtG1De74M7bvTZaxiX9L1x6TtzNG-nmw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/jw_RgG7mQdcnramNdyiL71zlVpg>
Subject: Re: [arch-d] iesg: Re: Updates on IAB mailing lists
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: Mon, 20 Apr 2020 21:54:19 -0000

My read has been that architecture-discuss was for Internet Architecture 
topics of relevance to the IAB or IETF.

That does not, in my book, include random musing about research projects 
that may or may not lead to something in some ill-defined time in the 
future.

And even if you disagree with the specific example, it does mean that 
there are clearly things which are off-topic for architecture-discuss. 
Which means that someone needs to be authorized to deal with such things 
when they become problematic.

Yours,
Joel

On 4/20/2020 4:13 PM, Mary Barnes wrote:
> Thanks - I hadn't followed Toeless' thread where he encountered the 
> problem that triggered his email.
> 
> Just to make sure I understand - the architecture-discuss list is 
> intended only for topics that the IAB deems of interest specifically to 
> the IAB and NOT a general community list to discuss things related to 
> the Internet architecture.  Is that correct?   If so, then it does seem 
> we need a list where folks can have discussion of technical topics that 
> aren't necessarily related to work IAB is doing.   I know we've 
> discussed in the past that the IETF discussion list is most suitable for 
> those discussions but I think most would agree that the list has a whole 
> lot more discussion of how we do non-technical things than technical (I 
> would guess 90/10 for the most part).   I think many don't pay near the 
> attention to the list that they might if it were technical discussions - 
> for example, I subscribe to that list using my general email that I use 
> for not real work.
> 
> So, one question I would have then, is whether it's thus only 
> appropriate for someone in the community to post to architecture-discuss 
> if they are asking specific questions on current IAB activities and 
> documents?
> 
> Regards,
> Mary.
> 
> On Mon, Apr 20, 2020 at 2:52 PM Melinda Shore <melinda.shore@gmail.com 
> <mailto:melinda.shore@gmail.com>> wrote:
> 
>     On 4/20/20 11:49 AM, Mary Barnes wrote:
>      > Personally, I think it's a handy list to have
>      > for purely technical discussions as opposed to all the non-technical
>      > discussions on the main IETF discussion list.
> 
>     Right, but I think it's clear that it's not every technical
>     discussion, which circles back around to Toerless's argument.
> 
>     Melinda
> 
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>