Re: "Management team"

S Moonesamy <sm+ietf@elandsys.com> Wed, 22 April 2020 16:41 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 F386A3A0FFC; Wed, 22 Apr 2020 09:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 meqM8_pHGSDp; Wed, 22 Apr 2020 09:41:02 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 5F09D3A0FFB; Wed, 22 Apr 2020 09:41:00 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.150.115]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 03MGelX9009376 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Apr 2020 09:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1587573659; x=1587660059; i=@elandsys.com; bh=momN6KeYKCfBC14ft1pSIuV6rFyoefHSJqgVVBNWg8c=; h=Date:To:From:Subject:In-Reply-To:References; b=U/MQz8ZAGHksBX5te0wB85Ziio6w+jeOvReI1QaRU6XstjVIUSDgC5i6hnljN0kK6 qGNG8U950BYSLV2wIeTXScNj1HadMA+6TWLKoxIae5t6a/kHHLcFP21GBGMrQB2ENg wb5u6U95UhWTT2d2YL2kxYRtVnmLCZULe6TceexE=
Message-Id: <6.2.5.6.2.20200422083137.0c226b08@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 22 Apr 2020 09:33:18 -0700
To: Jay Daley <jay@ietf.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: "Management team"
In-Reply-To: <64A28988-B8DC-4DA3-90FF-FBE658AE620E@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> <BD7D0BDB-C8EB-4113-B379-5B2095C7F9FA@episteme.net> <64A28988-B8DC-4DA3-90FF-FBE658AE620E@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1R1BErulP6yO6gg9PoVBhe9YIQA>
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: Wed, 22 Apr 2020 16:41:07 -0000

Dear Mr Daley,
At 04:21 PM 21-04-2020, Jay Daley wrote:
>Yes fair point - this could not be called a "delegated 
>authority".  Since the IESG asserts responsibility for 
>"administering the meeting event" and with this being all that is 
>documented (and nothing documented to the contrary) I think you can 
>see why I follow that and so coordinate with them in the planning of meetings.

Last year, I read a blog article [1]:   The following text caught my 
attention: "served on the Internet Engineering Steering Group (the 
board of the IETF)".  I was a bit puzzled by the description of that 
group given that it does not match a description which I read several 
months or more before that.  A few days ago, I read the thread about 
"Management team".  In simple terms, the board of an entity is not 
part of the Management team.

Last year, I submitted an Internet-Draft [2].  I provided my view 
about some parts of the Internet Standards Process in that document, 
together with the logical basis for that view.  One of the arguments 
made against the proposal was that it would be risky to adopt given 
that there are bad people on the Internet and they may misuse the 
"right of redress".  It is ironic that the Internet Engineering 
Steering Group gave its approval for IETF attendees to "sign the blue 
sheets" by typing in their names in a web-based collaborative 
real-time editor which does not provide verification process.

Regards,
S. Moonesamy

1. http://r.elandsys.com/r/69647
2. https://tools.ietf.org/html/draft-moonesamy-recall-rev-03