Re: Question on applicable procedure
Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 11 October 2026 20:05 UTC
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 0FB8846 for <ietf@ietf.org>; Sun, 11 Oct 2026 20:05:07 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=rwELZCqB; spf=pass (mx.ietf.org: domain of brian.e.carpenter@gmail.com designates 2607:f8b0:4864:20::62f as permitted sender) smtp.mailfrom=brian.e.carpenter@gmail.com; dmarc=pass (policy=none) header.from=gmail.com
Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-2d560775ca2so4867425ad.1 for <ietf@ietf.org>; Sun, 11 Oct 2026 13:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1791749100; x=1792353900; darn=ietf.org; h=content-transfer-encoding:content-type:in-reply-to:from:references :to:content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to:content-type; bh=a+6aHzdOmToHzBLFhuYQhBWtEv+XY59+Q45cOs7MKjU=; b=rwELZCqBHbFw8zimA6Dd/AGHYhj93G2CSL/GU9RQXZZkCErL4HV72sKvDnPyq29mrt u5EcF+/KyCSoQVrDyqesq0d0UNUKf5CaCrZFBbLHKutOTyPzIZe+rUJRpRLaDXfv3Axp WMAdDTVLFnlE5U0I5N8Vd4jkIPXAkBfTcWkIkWp5ukCC4Sdezw/EllcUj/3RkspnuWIt EqK+wgiCPJzLeDZy9GaZGu691zgb2AqSoqWrUECgoMYK6hL7dK9niGZE+2vdLIpat2hd 43SG57NlNEe0EpMkXXbaqsXfgWT7cNSnwIV/MwyZ1dRl96xWE2drZ2x4gKArZpb9fxQ8 B6BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1791749100; x=1792353900; h=content-transfer-encoding:content-type:in-reply-to:from:references :to:content-language:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to:content-type; bh=a+6aHzdOmToHzBLFhuYQhBWtEv+XY59+Q45cOs7MKjU=; b=s9lQfstSctLKQPO/exLW2U4KEueGSUCRx9TKCOoYitXKTkUe2GZ5+xzeH+f02tqZ2f 0Crw3G07rmOw2IZFj6eEUCrjwcPymWo2PkV5Ane+tdsVYA/0+7A8JrQ2kZdKFMkO6LWM LtrD4EdspHX3ypVqfvQ5fsujjK1PsJhtwcyhjZRrcaVA1nK8M5ocIqYKMURV0TFfHOq8 7CUEtLW3+I8n1pZm8QlEU9J6baK7LCTYH+cEmRq7CEdBS6mjIg5KJb6/vZeljvnUkHkK fGfrr4bVPPCSC6UeGw/a6kHyDEIk+dXfVNIrlecFD9yMQ7JIh1qVsy9O2ZEA2bBErgoa U+TA==
X-Gm-Message-State: AFq9FYIWxvlgCy+6UUCrQm/A0N5H97V0Opx0k8R92OpAL8wccGIQly0U HsRYI9KskUPs6mrPnifbcGzwpQNs+DJYBZneOsMiapSe6bZArAt10gX7TyVnxfux
X-Gm-Gg: AYBFou0+A9dDn94y3ueYh0c+q/ZiyQtqMhHPK1E72z3n6Ho3BzHqG5oLYY1cmq6VR+o HPVTVYmi7bZZ25Q4WH2OehKJoEOt7xfHSzRP4Ugi2Gogen4wMI7ZQxNNXltbHJQUs3HdRKMF395 WkOEf5O6vrfn8RrgS6z9sQWhAsipz8qYRqht3XkHmtCfpTipEvZ8T43D922yRGqlcaD69xN0EKf hO2wI0FTDxQMcb1XRYnnX7Mx15P6haqGttHEtVXLlgvxbIF+vSC4C8kEbXxyEtlVuayYProJ8q+ v+a0DE5RrEbiTBrIHCA7IPtOI4HiqrD4kozPTR0hQgiNS/3pRm95OxysmMWjyrn1Zf5cnf0+Y3l r2qwbG656qN/5+mDxcfTwvbgc1DbisKGn+bFg6enSSTbP4Nc0lUvH0/rFC73K7QOKYNVLlxK026 Er69mLz2Qx9mvjdPAZjmMQv0rW3bjwwt1scNlh+GkRQyy+4fC4ispxgQCmfruqe66QHEHr1nhFq fEtBALRnIjAcIv1GKqNs9/i27A1/BG8xAOmWFkzGrSfnlQXOEDCEdgoxWkcElZALBOup/G3A4Q=
X-Received: by 2002:a17:903:1967:b0:2d6:f6ba:263d with SMTP id d9443c01a7336-2e8427f0392mr68050105ad.7.1791749099762; Sun, 11 Oct 2026 13:04:59 -0700 (PDT)
Received: from ?IPV6:2404:4400:a100:1829:5956:ca53:df83:6568? ([2404:4400:a100:1829:5956:ca53:df83:6568]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2e8421af45fsm34254545ad.32.2026.10.11.13.04.55 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 11 Oct 2026 13:04:56 -0700 (PDT)
Message-ID: <e1477358-7794-40a5-9d36-ac8745061a16@gmail.com>
Date: Mon, 12 Oct 2026 09:04:53 +1300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Question on applicable procedure
Content-Language: en-US
To: ietf@ietf.org
References: <202610110802.69B81vYT002390@mx.elandsys.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <202610110802.69B81vYT002390@mx.elandsys.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spamd-Bar: -----------
Message-ID-Hash: 66ZQ2UQ6FFZOZ7CYYGZKW7WODERZ4PD7
X-Message-ID-Hash: 66ZQ2UQ6FFZOZ7CYYGZKW7WODERZ4PD7
X-MailFrom: brian.e.carpenter@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ietf.ietf.org-0; header-match-ietf.ietf.org-1; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uSdiCSPmFjJYHz1J_w47zcf8P40>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>
On 11-Oct-26 21:00, S Moonesamy wrote: > Dear Operations and Management Area Directors, > > [Cc ietf@ietf.org] > > There was a response to an appeal on draft-ietf-opsawg-rfc5706bis in > January 2026. An > Operations and Management Area Director stated the following in the > conclusion: "The OPSAWG delegate, acting on behalf of the chairs, ..." > > RFC 2418 discussed working group procedures and staff roles. That > RFC stated that: > > 1. the (working group) Chair "has the responsibility and the authority to > make decisions, on behalf of the working group, regarding all matters of > working group process and staffing". IETF process wonk here: There's the answer right there. The Chair has made a decision to delegate some responsiblity regarding a matter of WG process. The previous sentence in RFC 2418 includes "either directly or by others assigned to the tasks" so the Chair has explicit authority to delegate. Brian > > 2. "As a general practice, the Working Group Chair and Document > Editor positions > are filled by different individuals to help ensure that the > resulting documents > accurately reflect the consensus of the working group and that > all processes are > followed." > > 3. "The WG Chair MUST send email to the relevant Area Director." > > 4. "In most cases the determination that a WG feels that a document > is ready for > publication is done by the WG Chair issuing a working group Last-Call." > > My reading of the four points is that the working group Chair is the > person who make decisions on behalf of a working group. Which > section of RFC 2418 was relied on for the delegation? Which section > of RFC 2418 explained to whom the delegate reports to? > > Regards, > S. Moonesamy > > _______________________________________________ > ietf mailing list -- ietf@ietf.org > To unsubscribe send an email to ietf-leave@ietf.org
- Question on applicable procedure S Moonesamy
- Re: Question on applicable procedure Brian E Carpenter