[Iasa20] Barry Leiba's Yes on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)

Barry Leiba via Datatracker <noreply@ietf.org> Thu, 08 August 2019 04:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: iasa20@ietf.org
Delivered-To: iasa20@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B255E12000E; Wed, 7 Aug 2019 21:50:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-iasa2-rfc2031bis@ietf.org, Jon Peterson <jon.peterson@neustar.biz>, iasa2-chairs@ietf.org, jon.peterson@neustar.biz, iasa20@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <156523980964.8361.17146518946075725241.idtracker@ietfa.amsl.com>
Date: Wed, 07 Aug 2019 21:50:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/hSswOdh46BotHGBLezbqQGVxUOU>
Subject: [Iasa20] Barry Leiba's Yes on draft-ietf-iasa2-rfc2031bis-05: (with COMMENT)
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2019 04:50:10 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-iasa2-rfc2031bis-05: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc2031bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I find the wording in Section 2 to be a bit odd: it sounds like it’s saying
that things have always been the case before, but are perhaps so no longer. 
Can we re-word it a little to make it clear that these aspects have not
changed, though other details of the relationship have?  Maybe something like
this (adjust as you see appropriate):

”ISOC and the IETF have historically been and remain philosophically aligned.
 ISOC's connection with the IETF community has always played an important role
 in its policy work.  ISOC has always been an advocate for multistakeholder
 processes, which include the technical community.  These have not changed, and
 open standards are an explicit part of one of the focus areas in ISOC's
 mission: Advancing the development and application of Internet infrastructure,
 technologies, and open standards.”

Where Section 4 cites RFC 7437, it should cite 7437bis.

While I always find British spellings delightful, ISOC’s own web site uses
“program” (see, for example,
https://www.internetsociety.org/fellowship/ietf-policy-program/).  We should be
consistent with that.

The first sentence of Section 7 leads me to expect the paragraph to continue
talking about funding from ISOC, but it has nothing further to do with that.  I
suggest a paragraph break after the first sentence, and removing ”in
particular” from the second.

   Note that it is possible
   that some of those services are provided by ISOC or involve ISOC
   staff.

I would say “may be provided”.  Does that not feel better?