Re: WG Review: General Area Dispatch (gendispatch)

S Moonesamy <sm+ietf@elandsys.com> Fri, 25 October 2019 23:45 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 5088A12009E for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2019 16:45:55 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 Kc8Aw1ERZvP9 for <ietf@ietfa.amsl.com>; Fri, 25 Oct 2019 16:45:54 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 5CC50120073 for <ietf@ietf.org>; Fri, 25 Oct 2019 16:45:54 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.185.148]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id x9PNjdOE012495 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Oct 2019 16:45:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1572047152; x=1572133552; i=@elandsys.com; bh=HaZDqmxrqZBcIPxSQoiTdTbekSRs4emSvWCpfeWMDyc=; h=Date:To:From:Subject:In-Reply-To:References; b=GOOOXXLZpIixQbyq0fqpzR5S0e3HnSWSps7EgIL2m1/gAQPJCMtDQPXtNtnT7wsLT OwNF4DubdZNH4gxNkVGi7U7ALlkJh69EX6EmLJze7YVnoG2oRW/NPFDb4ZdHLDJ/lo BdL9M1qTYt8JutKw2Id4ewaWxXOtQ1KoK1i80iAk=
Message-Id: <6.2.5.6.2.20191025150414.1316a9e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 25 Oct 2019 16:41:39 -0700
To: Benjamin Kaduk <kaduk@mit.edu>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: WG Review: General Area Dispatch (gendispatch)
In-Reply-To: <20191025215031.GL69013@kduck.mit.edu>
References: <6.2.5.6.2.20191025000022.0d4d5570@elandsys.com> <20191025215031.GL69013@kduck.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bPqV1ZNKi4QwOhKfQpi3elgoxRo>
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: Fri, 25 Oct 2019 23:45:55 -0000

Hi Ben,
At 02:50 PM 25-10-2019, Benjamin Kaduk wrote:
>You give plain-text quotations from another message (or messages?), but
>with no Reply-To header or full quoted passages inline, it's hard to provide

There should have been an "In-Reply-To:" header in my message.  I 
probably did something wrong as it was included in the message which 
was submitted.

Please see the following messages for context:

   https://mailarchive.ietf.org/arch/msg/ietf/KdVwXK9LZ70rj53wol1tpi48k0Q#
   https://mailarchive.ietf.org/arch/msg/ietf/m7jd1XYr6VkB4ErELHlIspovZEo#

>an answer in the proper context, but I will try.  My interpretation (at
>least to the extent I recall) of John's classification of two types of
>process proposals is that it was mostly descriptive, of an "either X or not
>X" sense, and thus uncontroversial.

Ok.

>The role of the IESG in the standards process is described in BCP 9; I
>would characterize what's described there as having the IESG be the primary
>authority for standards decisions, but given the possibility of appeals,
>not the final authority.  There is some degree of terminology definition
>involved, so I could see others providing a different answer.

The point was that the IESG was given the authority to make those 
decisions.  In simple terms, IESG members have the power to make 
those decisions. I doubt that you read that as meaning that you can 
do anything you like or else you would not have mentioned the 
possibility of appeals.

>You did not ask me specifically for my opinion on "members of the
>community" but since I'm replying to the rest of your note I'll make an
>attempt at that as well: to me, taking an action to have an interaction
>with the activities of the IETF is enough to make one a member of the
>community.  That could be as much as reading email on our mailing lists,
>through authoring drafts and RFCs, holding leadership positions, and more.
>Different individuals will of course have different levels of involvement
>in the community, and I acknowledge that there will be situations in which
>the level of involvement will matter for one reason or another, but the
>core idea remains that we are an open community and taking action to be a
>part of it ought to suffice.

Part of being in open community is that you and I can have this 
exchange.  I don't use the word "member" as that can entail having 
some obligations.  Anyway, the important part is what you communicated above.

Regards,
S. Moonesamy