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

Mary Barnes <mary.ietf.barnes@gmail.com> Mon, 20 April 2020 20:14 UTC

Return-Path: <mary.ietf.barnes@gmail.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 29F603A0EDF; Mon, 20 Apr 2020 13:14:11 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 xyKTJji3SxjU; Mon, 20 Apr 2020 13:14:09 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 789A73A0EE4; Mon, 20 Apr 2020 13:14:09 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id q18so2089854pgm.11; Mon, 20 Apr 2020 13:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1ePCTQDy68sKGvcDOAyA0Blfe55I3t8tJJwdLGlslec=; b=bzDEw76RJJo1ka/3MiN9Ks/OrXqiwl6zw+F02NhgIQXoV3w5vVoi5DEwmGGV9Om6wb 6jQT+B0Jx8M5jzDDffQl3rzD8zKnfHu8qIGT8SjaI/+SLMVOx0SpVAgF8nedL6ue/qyY 8ny3ghaCP83HBuesYhQ6CkA2+YhDC6miAD7AZTuI30diyaDq6aOct0lrzweBiogDiD7m oD7I3S5Zeu5oQv/0FndQn2995E1ZqvyQJz7Umu8yeRZSgew/JXmxYwZumF47eKX5TKVp vVoAaDKFPuDT5svp0lwtPsu3oc2gP+0wIxQd1B7brMBwLQlsDsMfv/yf6rLDqNK19VWp rCrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1ePCTQDy68sKGvcDOAyA0Blfe55I3t8tJJwdLGlslec=; b=A/Pml/QJcmQ/rdYvUygi93cB+5y801reUqKAcTY6s0aOEAcC+rF48oxutcu0AU4o7V RNrNXvBZDoPAE+JGXe7BR/+8cwh6B0eOD/5MNjmq0FWZOe0z0zvqeCab86CAuLyRqjlw /Z6q2W3a5nIqmf8XWEkRVbZMFb+2QRKlecx8ae5MiRo4L+lznFkkUgiT4ZqLwahOPHYX Bb9e5adraqTtvlbKwiDjkh/YJsK2P2ZlP2iggXBPrcJK9QaLV2u5UKA5hlgw7DWq9xzE Zl95V4LBv/+usYcuF1Q1z0VNocAlysIYKBOd/hLPKThUQ4zGtAYmrOnt0XBImlnXl3mx zzCQ==
X-Gm-Message-State: AGi0PuY0sgXdKl4UF5IIXoL3TzpNHyWuS6INXTxIsRJKZZUaui+T9w8z SZ3CwvA9OgNt4d4NjZrAlYajxJa0csA0hNzlpSI=
X-Google-Smtp-Source: APiQypLdsZ74CV6egzMSW8su932xjVwE4lD9Aafu449vYZVBQpFzZwznWDt7MNTIl0kcUYeVMBZ+hPRZ/1eiG5yftvs=
X-Received: by 2002:a63:c504:: with SMTP id f4mr18082748pgd.292.1587413648763; Mon, 20 Apr 2020 13:14:08 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <93a7ae7f-c2bc-a009-baa9-8671de5ee384@gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Mon, 20 Apr 2020 15:13:57 -0500
Message-ID: <CAHBDyN5Jf1amBHFXwWVtG1De74M7bvTZaxiX9L1x6TtzNG-nmw@mail.gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Cc: Toerless Eckert <tte@cs.fau.de>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>, The IESG <iesg@ietf.org>, IETF-Discussion list <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a56df205a3be8a25"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/lkkVdMpd1EhZl3DaX0OxYhFXf3Y>
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 20:14:11 -0000

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>
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
>
>