Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS and COMMENT)

Barry Leiba <barryleiba@computer.org> Tue, 09 April 2019 17:32 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6147B1207F7 for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 10:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 5yDw5oc_B-Cf for <iasa20@ietfa.amsl.com>; Tue, 9 Apr 2019 10:32:17 -0700 (PDT)
Received: from mail-it1-f172.google.com (mail-it1-f172.google.com [209.85.166.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 060D11200EA for <iasa20@ietf.org>; Tue, 9 Apr 2019 10:32:17 -0700 (PDT)
Received: by mail-it1-f172.google.com with SMTP id 139so6296418ita.4 for <iasa20@ietf.org>; Tue, 09 Apr 2019 10:32:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OFtmM+/TtxWaSe4goCZQDhabqjQbAe1wdJupPKjJkwU=; b=lx9ypSVTK25shbkAMroL/5yG59JlUJQS0kqltJ1VWHMXvkCdQCNUjPT3f13kwU8qBT XQZ6UDMCV04zlR3GTvYmHO9v1yPMW9ksdX2yq1vG2Q1iTx/D6GCX720d8W3eplZmZjYe 6Ip/B18CBIgFLS3DpQRhSpp6pKAF9nOfJAdXGvRbvzW/6Ss7rJBWSPc7Su1EvgJXfYc9 CcO3VTUHEm2DE2AiUi9o2JOSvUHOHimpuSJL3T7TI39jY6uBaAlWBwYvpLCvon8oPkxQ shjutoF/w1cc7qtrnv2in8S5IB9SLlaGlICzSWvYyLr+SWW3FgdXZrL8s8WZL57DIENw NTGw==
X-Gm-Message-State: APjAAAWEQ/VrjMdVbnyIcUPLlhtnGGQXKSfdbz84M8N0bky/hSWZ8NAX d3WZ5NUE+6RYyRHAW7nZt6Dtj0XIIojziChVSToMPA==
X-Google-Smtp-Source: APXvYqxfj5AQpuho2T9tLqujRJL9UC64BNPKuxR30SXwuqUx40WzUyoCRCcPzzMpziqh7jVj1q1sjX6NnLqvh84kQn0=
X-Received: by 2002:a02:9a12:: with SMTP id b18mr27437381jal.45.1554831135986; Tue, 09 Apr 2019 10:32:15 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJKQPNWYF52HAJar53DoZ_RgyN1oFW3JpABbW9KXrjbyWA@mail.gmail.com> <20190409160911.4BF602011C7A02@ary.qy>
In-Reply-To: <20190409160911.4BF602011C7A02@ary.qy>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 9 Apr 2019 13:32:04 -0400
Message-ID: <CALaySJ++KU_6TkKRELY36hHrMydrLzAu0=5sox2xumE+-PGfaA@mail.gmail.com>
To: John Levine <johnl@taugh.com>
Cc: IASA 2 WG <iasa20@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/KDSnMIy9wmDQP-gEbHvfV2HLqoc>
Subject: Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc4071bis-08: (with DISCUSS and COMMENT)
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Tue, 09 Apr 2019 17:32:19 -0000

> Once again we are falling into the chronic IETF trap of obsessing
> about process corner cases.

We're not obsessing, and I don't see them as corner cases.

> This document says that the IESG will
> probably appoint the Chair to the LLC board, but if the chair doesn't
> want to do it they can appoint someone else.

It says neither of those; it certainly makes no statement about what
the IETF Chair does or doesn't want.  It says it's at the IESG's
discretion.  For this year, the IETF Chair made no assumption, and
asked the IESG what we wanted to do.  We decided that for this year,
continuity with the transition board and the fact that there's a bunch
of startup stuff to do, such as hiring an Executive Director, made it
particularly important to appoint the IETF Chair this time.  At least
some of us want to reconsider that next time, when the situation is
different.

So, no, not a corner case.

> I would leave the language alone, and if it turns out there's an
> *actual* problem we haven't anticipated, we can fix it.

We have an opportunity to spend a small amount of time NOW to get the
language clear and make it less likely to need fixing in the future.
I think we would be derelict if we didn't take it.

Barry