Re: Last Call: <draft-ietf-iasa2-trust-update-00.txt> (Update to the Selection of Trustees for the IETF Trust) to Best Current Practice

S Moonesamy <sm+ietf@elandsys.com> Tue, 25 September 2018 05:01 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 6867A131220 for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2018 22:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIM_INVALID=0.01] 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=opendkim.org header.b=aazAwNoV; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=BUZVg+Uk
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 HIaGtuqiyjXI for <ietf@ietfa.amsl.com>; Mon, 24 Sep 2018 22:01:55 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6924F13121F for <ietf@ietf.org>; Mon, 24 Sep 2018 22:01:55 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.49.118]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id w8P51eGd029948 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Sep 2018 22:01:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1537851712; x=1537938112; bh=PwAg/ELoHN0e+EqxpnlfkxFHbwF6cp6nQaMZKJgigkU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aazAwNoVh8kP+BBZw/+iHdQN6y+0gzLTtK5OQ4lEHvI6PsTGEnk7eGmtbUALOFpS3 9V0RgZXHgCYHi+xu8XOcshU84/GuzF20pTirBtZrOMh6318URF8L9VphzZ79zAkuhb 0sRKhxsUBBofjKben7sa/swiYJ5UYnUTKzvjb02Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1537851712; x=1537938112; i=@elandsys.com; bh=PwAg/ELoHN0e+EqxpnlfkxFHbwF6cp6nQaMZKJgigkU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BUZVg+UkmhsVCX6PLJscmPQK9BamsruunywnPSldOo8XC7S/TxTFnjb6Nz2/HdMnj ta4f4eeSWk4H0eArLe3D1xqPpV/GC+4gNlnKxUYYMsk8Hu/GS2NR63G7aSFIw6tOzJ AltGshT1bJJ9rM33RxH0h339P6S1s9FFRnX59BJI=
Message-Id: <6.2.5.6.2.20180924193018.0c021310@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Sep 2018 21:59:39 -0700
To: Ted Hardie <ted.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-iasa2-trust-update-00.txt> (Update to the Selection of Trustees for the IETF Trust) to Best Current Practice
In-Reply-To: <CA+9kkMAeB1-8V+DMK2FqD436A4mn5shAUrwYSe2B-1hs6MAUuQ@mail.g mail.com>
References: <153756470188.20283.12048259576780413892.idtracker@ietfa.amsl.com> <6.2.5.6.2.20180924090802.0b3bb098@elandnews.com> <CA+9kkMAeB1-8V+DMK2FqD436A4mn5shAUrwYSe2B-1hs6MAUuQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rNmpbTRBwULVZZeZv7OrqnrleR8>
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, 25 Sep 2018 05:01:57 -0000

Hi Ted,
At 02:08 PM 24-09-2018, Ted Hardie wrote:
>Thanks for the review.  The issue here is that RFC 4071 and RFC 4371 
>will be obsolete at the end of the IASA 2.0 process, and the aim is 
>to make the process listed here complete without needing to read the 
>previous iterations of BCP 101.   If the document didn't reference 
>the previous document at all, do you think it is clear how the 
>Trustees are selected?

Thanks for the prompt reply.  One of the points which I missed in my 
previous comment was that the draft obsoletes RFC 4371.  The draft 
updates instead of obsoleting RFC 4071 by removing a sentence which 
RFC 4371 added to Section 3.2 of RFC 4071.

The appointments as specified in Section 2 are clear.

>I don't think so, as it is the "why", where this document is 
>intended to be narrowly scoped to how.  An informative reference 
>makes sense, and it has already been suggested.

It might be useful to publish the "why" if the RFCs are viewed as 
part of an archival series.

>This document doesn't update BCP 10, so I believe your change has to 
>be directed there, not at this document.

The WG charter states that existing IETF and IAB appointments are out 
of scope.  As the draft specifies new appointments, I presume that 
matters related to appointments are included as part of this Last 
Call.  The IETF rules regarding recalls are specified in this draft 
by reference.  Is it fair that IETF rules with respect to the recall 
of IETF Trustees be unavailable to roughly one third of the 
IETF?  That is the question which the IESG may have to give some thought to.

As a comment about BCP 10, a side effect of removing
the re
quirement that trustees be drawn from the members of the IAOC is that 
BCP 10 would no longer be applicable given that the document does not 
say anything about IETF trustees.  That also removes an ineligibility 
requirement which is currently applicable to an IETF trustee given 
that the that "IETF rules" are ambiguous.

Regards,
S. Moonesamy