IETF Logo Mail Archive

Re: [arch-d] Rescoping of this mailing list?

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 23 February 2021 23:47 UTC

Return-Path: <brian.e.carpenter@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 1158A3A1127 for <architecture-discuss@ietfa.amsl.com>; Tue, 23 Feb 2021 15:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-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 eETPBvKX76ns for <architecture-discuss@ietfa.amsl.com>; Tue, 23 Feb 2021 15:47:47 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 974453A1126 for <architecture-discuss@ietf.org>; Tue, 23 Feb 2021 15:47:47 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id p5so27913plo.4 for <architecture-discuss@ietf.org>; Tue, 23 Feb 2021 15:47:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=HM1i0T5JWGlKV47UZC5MBBJGgi4xZGXd6DCWKDNTq9M=; b=t2ZOAyKnnPXWT8dEKC/A9sojSHLE4CjY9mQf2YF44nOsrT5En3bie5btd/B74zMwq4 H4xv13SverNvEHnMoKma+av8fRUWNPiTOmuQiY5WfE2F9f47i/2GxBKau1Cn1k7dvJiz QAAEoynWhmMuCvNgw6C4m9Swha19MnRXOT9vBRewc1osmoQeiiIQHom1rjfuCBuY4qjW l2uYSUUFNGgpF69f3siv2MIpMwTvpubE+o30v8AbteGF3RvhtBJV4qgqcHKxmnQ6oaIE QG+icWbqP5EiaxgQuJY5u8e5PmcJiwuOhSBZDKn6/S01LERrTkdMUnDbVVPXc82GxjF5 AweQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HM1i0T5JWGlKV47UZC5MBBJGgi4xZGXd6DCWKDNTq9M=; b=Zv+0wcJuEYJKWHNTUQMCI8vicEhFqv0Timcw9rBhMXI5+62DLbMhPWVP9AWKhHkS2E IfNhJPzSeUfw/Wo5Jem0IM6YluXXJlZS8iqHvgudUec8azIZRL1/S+0hyJKu3JTWIt73 S78YFYJJXOYYqIkuztcsXFm1jJdhdssf84VrlGCyR+DaAycBs2Xb6unqFWVar88A+20X wskZzRt4MeNtN7qHm9rptvMSPWBlmHKlmm0/ZhXKcp3t+84Acu4up9GuUKRjbtBghLQG HJ4ThSnjesRUY0EBzZYzsPgBS9Y4Za0sCb8y0sWmAeO5stFU9j2oPJDsWBS+xGYkiQOE 7xoA==
X-Gm-Message-State: AOAM530HuHAWr1+qwUS0oa7SOv2WlDjraBUF6+3/s76cT4DJJewHP5QZ 1LosHGHCnP2BZr91bVWx+7/tmi+iuiBN9g==
X-Google-Smtp-Source: ABdhPJwI5pbQGmzvgO1O6tX2zAMJ3AJ9nEsvnZkkNnRF7eg45LrO7qwoSWEo/82V3EvNlMiYMxMkzg==
X-Received: by 2002:a17:90a:a585:: with SMTP id b5mr1253580pjq.110.1614124066484; Tue, 23 Feb 2021 15:47:46 -0800 (PST)
Received: from [192.168.178.20] ([151.210.131.28]) by smtp.gmail.com with ESMTPSA id 203sm283573pfy.105.2021.02.23.15.47.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Feb 2021 15:47:45 -0800 (PST)
To: adrian@olddog.co.uk, architecture-discuss@ietf.org
References: <03b601d70a37$3e481770$bad84650$@olddog.co.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <f721e7dc-2685-98ce-568b-30d3eebc3927@gmail.com>
Date: Wed, 24 Feb 2021 12:47:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <03b601d70a37$3e481770$bad84650$@olddog.co.uk>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/h4BFhBe1dciRPlSq6Aze-cVYqGA>
Subject: Re: [arch-d] Rescoping of this mailing list?
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, 23 Feb 2021 23:47:49 -0000

I think we should actually discuss stuff here, and it doesn't just have to be IAB documents IMHO. RFC8799 certainly benefitted from discussion here.

For example, draft-jia-intarea-scenarios-problems-addressing. I haven't had time for a careful read yet, but it seems to have signficantly wider scope than just intarea.

If there was an I-D on the purpose and mechanisms for external liaisons, I'd be happy to discuss it here too. (I've always felt that this was actually a key part of the IAB's architectural role, not just an admin chore.)

Regards
   Brian

On 24-Feb-21 11:57, Adrian Farrel wrote:
> Hi,
> 
> I notice that recently this list has been used to make announcements of IAB
> policy such as repurposing/scrapping IAB programs.
> 
> It is good that the IAB is making those announcements and providing reasons
> (even if I don't agree with them :-)
> 
> However, surely these announcements should be sent to ietf-announce@ietf.org
> so that they can be properly noticed by the community. (You wouldn't want to
> find that there was no interest in a sleepy program due to you not telling
> people about it!)
> 
> This list is described as... 
> The architecture-discuss list serves as a technical discussion forum for all
> members of the IETF community that are interested in larger architectural
> issues. It is meant to be an open discussion forum for all long and/or wide
> range architectural concerns related to the Internet Architecture. In
> particular, it may be used to discuss and bring forth different points of
> view on controversial architectural questions. Discussions that drill down
> and dwell on specifics of individual protocols or technologies are to be
> discouraged, redirected to appropriate other fora, or re-cast to discussions
> of broader implications for Internet architecture. [1]
> 
> Or maybe this list needs to be repurposed?
> 
> Thanks,
> Adrian
> 
> [1] https://www.ietf.org/how/lists/discussion/
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>

v2.23.0 | Report a Bug | By Email