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

Mary Barnes <mary.ietf.barnes@gmail.com> Mon, 20 April 2020 19:49 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 D418C3A0E13; Mon, 20 Apr 2020 12:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 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, URIBL_BLOCKED=0.001] autolearn=ham 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 ERxxxdpi9J24; Mon, 20 Apr 2020 12:49:31 -0700 (PDT)
Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) (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 5EA5E3A0E0B; Mon, 20 Apr 2020 12:49:31 -0700 (PDT)
Received: by mail-pf1-x433.google.com with SMTP id d184so1066151pfd.4; Mon, 20 Apr 2020 12:49:31 -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=ppwTtvJoxW0AHt/VcIWvLhix9YN17QCVkk48uTPvPeU=; b=a85GzQYp+aQoi571cF9cPU+dQFndYyJIiNBTcsEdrheqtQU304hUdtVZprjD4lgjqM AWAY6QSDsntjtsYF9CDat5cul1lPrbWFl7LmtsRmvWgCYM3nGb5b66F64Sw1fF0Vb5kR AZsoNDq7VLYWX9Gw8SJN08yI7S+kgWUw6rbP5kKgiLY01HPPxGaT89N9hhaRlB1tLozW Tn8YqSR5Udvo6kg5JQFm9RH5/YrTolvi6VrFUiU4uK3eQlyOKbVdslD++2IHrZN3i8Qp 0nQMx9ovXYP+EbItKeXCVJDoKAmd4US6yQ/JeVhD9C/Fj2U0ALJQ7m23PyN9f+Pe0Z4Z OOvw==
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=ppwTtvJoxW0AHt/VcIWvLhix9YN17QCVkk48uTPvPeU=; b=Vs8mhOOFVRTpoOdt00tu43xhPKtqZ2tv+qkrhbU+wzqAoE69X41mklTJze7bTzBnoH 5B+Qwv3141NtnHMpGnZ6CtKTHbtYiP6xX5KB77WLxU8po0/cAP9CyTsSnGK+dslFwdm2 zLuvHZVHFFThb/FRjoDhB/vQ9ahDTOnqFiWA9g+xYDQlO9G9M8knmHjgzBEh1+79jxCG QClAPPneRqm7FiZbdE/BGL4A6ncIG7dx5b5vEyk2fevk/G63gw1QE6XmBoqdlrVxvd4n L3pQXFRKfMi8NhGCaPTEGRLBO8iDRMKHsbr1v84rBHe9UOLknS2tAA3xG3a9WmVdPDCb smqg==
X-Gm-Message-State: AGi0PubOfMqLnagTz0pE35Gpei6s9kcWQIFl/Y/TrAsVSeujLyZV7lOn u96uir6n/kGzx1EBl//e9iWwu9DI6AKbtIG5vLU=
X-Google-Smtp-Source: APiQypIb9Rzlf0zOGkhoPPfujyW0mRjqXUAp8Uhw6Lo9p+a+1CSg2Mo/3zdcFDEG2QmtcP6Z9yIsb3LrsZYT/Ex8+Ik=
X-Received: by 2002:a62:cdc9:: with SMTP id o192mr18833152pfg.310.1587412170924; Mon, 20 Apr 2020 12:49:30 -0700 (PDT)
MIME-Version: 1.0
References: <20200420184456.GG5351@faui48f.informatik.uni-erlangen.de> <c8c9947a-9fa5-e208-6560-01f31067a590@gmail.com>
In-Reply-To: <c8c9947a-9fa5-e208-6560-01f31067a590@gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Mon, 20 Apr 2020 14:49:19 -0500
Message-ID: <CAHBDyN6b_GFDaxRj1v4n==NjZJMXt11sBSsRcik7R1b0kN4yUA@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="0000000000008f67c005a3be32a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/koXvuk5JTcaNJwWxO5QYrIqDOvE>
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 19:49:33 -0000

If the intent is that the list is specific to IAB activities (as I said in
my response, that wasn't the intent in the past), then you all should
update the description.  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.

On Mon, Apr 20, 2020 at 2:43 PM Melinda Shore <melinda.shore@gmail.com>
wrote:

> On 4/20/20 10:44 AM, Toerless Eckert wrote:
> >    1. It is called architecture-discuss@ietf.org, not @iab.org
>
> Note that ietf.org hosts a number of mailing lists that are not
> "official" IETF activities.  You can find a list of all IETF
> mailing lists at https://www.ietf.org/mailman/listinfo.  The
> main reason we have so many mailing lists is to group things which
> are like and separate things which are not like, to keep discussions
> manageable.  architecture-discuss exists to support the activities of
> the IAB.  Presumably a discussion of homenet architecture would
> not be welcome on architecture-discuss.
>
> It seems to me that it makes more sense to request a new list for the
> discussions that you'd like to have than to repurpose an existing list
> over the objections of the list owners/managers/SAAs.
>
> Melinda
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>