IETF Logo Mail Archive

Re: "Management team"

Pete Resnick <resnick@episteme.net> Tue, 21 April 2020 23:02 UTC

Return-Path: <resnick@episteme.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D70E13A0D6D; Tue, 21 Apr 2020 16:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 W28hyDDXiEhk; Tue, 21 Apr 2020 16:02:05 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F9D43A0D67; Tue, 21 Apr 2020 16:02:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id DFA3DA9C5993; Tue, 21 Apr 2020 18:01:57 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFQ4W8_sNe56; Tue, 21 Apr 2020 18:01:56 -0500 (CDT)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id DE145A9C5986; Tue, 21 Apr 2020 18:01:56 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: Jay Daley <jay@ietf.org>
Cc: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
Subject: Re: "Management team"
Date: Tue, 21 Apr 2020 16:48:26 -0500
X-Mailer: MailMate (1.13.1r5683)
Message-ID: <BD7D0BDB-C8EB-4113-B379-5B2095C7F9FA@episteme.net>
In-Reply-To: <17E08229-CE52-434E-B2FF-22992E95DD30@ietf.org>
References: <47A0EEE1BBB8EF41FD8B07E0@PSB> <26FF91F9-CD44-4045-991E-AF21A7208622@ietf.org> <6.2.5.6.2.20200421022015.0ba531d0@elandnews.com> <17E08229-CE52-434E-B2FF-22992E95DD30@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; markup="markdown"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cT3y4Q31-uFHueYNS16CxKroR-o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Apr 2020 23:02:07 -0000

On 21 Apr 2020, at 16:16, Jay Daley wrote:

> RFC 3710, Section 1.1 sets out role of the IESG as follows:

Fair warning about RFC 3710. See section 1.2:

    This document is published as an Informational RFC, detailing the
    current operations of the IESG.  It does not claim to represent
    consensus of the IETF that this is the right set of instructions to
    the IESG.

The role of the IESG, except for it's role in the standards process (see 
RFC 2026) is highly under-specified, for better or worse. RFC 2028, 
section 3.5 also makes for amusing reading, and if you really want to go 
spelunking, a look at RFC 1602, section 1.2, and RFC 1310, section 1.2, 
are also fun.

Welcome to the amusing part of this crusty old organization. ;-)

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best

v2.23.0 | Report a Bug | By Email