IETF Logo Mail Archive

Re: [admin-discuss] Consultation on IETF Administrative Strategic Plan 2023

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 16 November 2023 19:49 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: admin-discuss@ietfa.amsl.com
Delivered-To: admin-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29630C14CE33; Thu, 16 Nov 2023 11:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 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.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhCrn9vlyVaH; Thu, 16 Nov 2023 11:49:49 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82EB1C14F74A; Thu, 16 Nov 2023 11:49:49 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-6c4cf0aea06so1174758b3a.0; Thu, 16 Nov 2023 11:49:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700164188; x=1700768988; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=IxBDNmoP0GziI1Z8vup+/T5HOAN5qryQwHn9Cm5xfvc=; b=P9qs1PeQT93lLCKFcKQRpTMRQKixw97TU976VExT2XKSMdZ5J6HUmbw1hrCm+wHJep xiaLAJiIeAieKcPKobGCu4h+rJ3sJCmk8q6RWgc6bkB4HOcGZitdIxp6URqtB8LovQLZ dVAo0V5zp7Lfj4tohHP+xcH02/tbs5VQuffNAcOOzOlrcGyNbcAXLXCH8k2QhJQYsSLb CxN1OyQ/26nWUD1ZEdeSzcdck6cH5oEy4eAg+y+7JM+2Va8vQo0rJKmaNovHViAMiDqW JRbDk0L+cGgcfBeJGDxD91X0S1fVQ0vuCD6gr4P69j75J1k82omfjwAISFHqkNuU9CwI a5Dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700164188; x=1700768988; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=IxBDNmoP0GziI1Z8vup+/T5HOAN5qryQwHn9Cm5xfvc=; b=I5qoavVwQd6Ap0pTZzo6XFXf+9zqWoJIOjwCh/Hze1BDXdFPxMSpsx6pLrQpwvwnsK uCvQajo/tQvBYidHknBhiFtUtvzcZzJL03RR+AaIBEPPCNYf8k8pQaWdKnGkV646NLr4 FvfkYAcqQfcGorEpqVP7+ZexUHJ/aREb1YJhbBbqX54GEHdtUqGRxr6gGa/qjGIJEUD9 OeWRI0w0RIgFltLW52w6vBvR8rP8PHn4mHVq+taeH/MYSdxbBCD5OAtOVN/JOm5SETtE lu5nPYNCcf+1Qhs7gRIu5qlHpcpYBZeuNfVN2fR0wpCJpdMV8lc6FWdL59pQQUl5HgQs 3c6Q==
X-Gm-Message-State: AOJu0Yw0wP4gY0AAbnrgfhpJeSRQZeieGkJAE4VOsc1K1n2UaRSFaqnr hMwIcPC2w6xoQOFLY1xV9fLEB1QliMbMjA==
X-Google-Smtp-Source: AGHT+IGjamjkNRN4VT+hQPdQZe32Gm3U0sQs5PxQX1u+WG0lKrP69yeZSaAeyZ34eppq4eAW8ncmSw==
X-Received: by 2002:a05:6a00:1406:b0:6bc:e7f8:821e with SMTP id l6-20020a056a00140600b006bce7f8821emr20832554pfu.10.1700164188437; Thu, 16 Nov 2023 11:49:48 -0800 (PST)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id s2-20020aa78d42000000b006be5af77f06sm115880pfe.2.2023.11.16.11.49.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 16 Nov 2023 11:49:47 -0800 (PST)
Message-ID: <ac02ab49-9ee0-f95a-9e01-99f0d97371dd@gmail.com>
Date: Fri, 17 Nov 2023 08:49:44 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Eric Rescorla <ekr@rtfm.com>, Jay Daley <exec-director@ietf.org>
Cc: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, "admin-discuss@ietf.org" <admin-discuss@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, IAB <iab@iab.org>
References: <309BA4FC-7129-4F7B-894C-E64FADA24DD0@ietf.org> <6DFA5AB6-1C7B-4701-B711-280461B6A956@ericsson.com> <F61C1FCD-55C4-4DCC-8460-F67D62DF4113@ietf.org> <CABcZeBPqSoKe-kYQgjn6Pvx8VqujfDm4wq-GTZ+iJna6Mkyzog@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CABcZeBPqSoKe-kYQgjn6Pvx8VqujfDm4wq-GTZ+iJna6Mkyzog@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/admin-discuss/MRZBDndInycfU1P4s5NVRBrI8Yg>
Subject: Re: [admin-discuss] Consultation on IETF Administrative Strategic Plan 2023
X-BeenThere: admin-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussion list for IETF LLC administrative issues <admin-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/admin-discuss/>
List-Post: <mailto:admin-discuss@ietf.org>
List-Help: <mailto:admin-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/admin-discuss>, <mailto:admin-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2023 19:49:50 -0000

Eric,

On 17-Nov-23 02:48, Eric Rescorla wrote:
> 
> On Thu, Nov 16, 2023 at 5:00 AM Jay Daley <exec-director@ietf.org <mailto:exec-director@ietf.org>> wrote:

<snip>
  
> I agree that the IETF has a number of long-standing and important strategic issues and the LLC has a role to play in addressing them. However, that role is a supporting role, which is to say that the IESG and IAB are responsible for addressing those issues ...

It isn't clear to me that the IAB has a large part of that responsibility (reading RFC 2850 and 9280), but I agree that the IESG has the responsibility for strategic issues in the IETF process and procedures. However, it seems to me that the IESG doesn't have either enough continuity or enough spare time to exercise that responsibility. So if we are worried that the LLC is exceeding its support role, we need to take steps to ensure that the IESG can fullfil its strategic role.

Should there be a strategy WG to crowdsource resources for this?

    Brian

> ... and the LLC is responsible for providing support on those issues as requested by those bodies. As such, actually seeing that those issues are addressed is not an IETF LLC objective; rather, it is an objective for the IESG and IAB. The LLC's strategic objective is to ensure that they have the capacity to support the IESG and IAB in these matters. To be concrete about it, if the IESG/IAB just decided not to work on these issues, we might say that they had failed but not that the LLC had.
> 
> While I think the text you write above in response to Mirja is largely reasonable, the relevant text is actually what is in this document, which in fact does look like the LLC *is* asserting ownership and control over this and other similar items. So I think rather than providing more context in email it would be better to edit the document to make these matters clear.
> 
> -Ekr
>

v2.23.0 | Report a Bug | By Email