Re: "Management team"

S Moonesamy <sm+ietf@elandsys.com> Tue, 21 April 2020 09:46 UTC

Return-Path: <sm@elandsys.com>
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 A885E3A0B04; Tue, 21 Apr 2020 02:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.203
X-Spam-Level:
X-Spam-Status: No, score=0.203 tagged_above=-999 required=5 tests=[DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 xmr1LKkujWdG; Tue, 21 Apr 2020 02:46:26 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1E03A0B03; Tue, 21 Apr 2020 02:46:25 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.37.130]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 03L9kDDa024118 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Apr 2020 02:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1587462385; x=1587548785; i=@elandsys.com; bh=1yDH3a0IKjLnYdPKAlqvGD7vUwGpp/uTFsQun5KhWvk=; h=Date:To:From:Subject:In-Reply-To:References; b=fkxysBYdg9JfwkPw7yhcosBv9C3UIjdaNdHG5z4ij0t7hAF85isUDqJ3fLg/uobkt VOGuq+E/DVxwAXXsHsIosC6xZK1WpNZ/NoRjL/14HXiezQMpU0fINjnZKfEV77zpKH zM+fcPbyVkV/L2KNnUOSLq8aKsfjC7Bp0xPF1yEw=
Message-Id: <6.2.5.6.2.20200421022015.0ba531d0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 21 Apr 2020 02:45:54 -0700
To: Jay Daley <jay@ietf.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: "Management team"
In-Reply-To: <26FF91F9-CD44-4045-991E-AF21A7208622@ietf.org>
References: <47A0EEE1BBB8EF41FD8B07E0@PSB> <26FF91F9-CD44-4045-991E-AF21A7208622@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SmC5FMaOhukTg5Dl_2XwjGDDHjw>
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 09:46:28 -0000

Dear Mr Daley,
At 05:57 PM 19-04-2020, Jay Daley wrote:
>Another way of looking at this is that the IESG have a set of 
>responsibilities (delegated authorities if you prefer) as does the 
>IETF Executive Director and as does the IRTF Chair, and if those get 
>together to coordinate on how they do their work and do not exceed 
>any of their responsibilities then why does that need a label or 
>formal recognition?  Or is it your view that a) the responsibilities 
>have been exceeded; or b) this type coordination across roles needs 
>community consensus approval before it is allowed to happen?  Your 
>note implies b) rather than a) which seems surprising so I suspect 
>I'm just missing a nuance.

There is a policy (BCP) about the meeting stuff.  It sets guidance 
for the IASA.  Are you are referring to that as the delegated 
authority?  There isn't anything in there about delegated authority 
for the IESG.  The IETF LLC gets to decide whether the IESG should be 
part of some management team.  A person operating at Management level 
is deemed to have understood the limits of his/her "authority".

Regards,
S. Moonesamy