Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05

Ted Hardie <ted.ietf@gmail.com> Tue, 12 February 2019 21:31 UTC

Return-Path: <ted.ietf@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 F3796130DDA for <iasa20@ietfa.amsl.com>; Tue, 12 Feb 2019 13:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0Wn9bEV_9h6u for <iasa20@ietfa.amsl.com>; Tue, 12 Feb 2019 13:31:28 -0800 (PST)
Received: from mail-it1-x135.google.com (mail-it1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) (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 206D3130DD3 for <iasa20@ietf.org>; Tue, 12 Feb 2019 13:31:28 -0800 (PST)
Received: by mail-it1-x135.google.com with SMTP id g85so489818ita.3 for <iasa20@ietf.org>; Tue, 12 Feb 2019 13:31:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8IwnLBCb9tFOLRWmMxGhZA/534sSr8LovDaFAzGUd70=; b=rC1AUyZQlRm/1DydXlnSPzTfZm93diEtmsEHEmxYHJsZzWP0Co2dnFlYnBkpJiwiCi 9nkdcLncv5eHDmeQM+jubmQT1LBVYaAUW6sVLSYIdwc3cweSKW0UTAsPosVCg3F59JCz b9DBkrUdcdkRXYfTdKoTZN7zvMF7C2BsrPOvIU5R6WlSaycKWl6Lz2Bgt5RzLT3YGQgb 0Kw0fWHA8puyw/UhY2gN4bA+bROLLDP3W8lIW2iu5g5GrPeOA/Q8C4XIxxTCPrKbBBmK JmOafCZ8ZcF6JT3494km9u7h3bfLEFKIIbMfNTn9rKY0tUZXdjbzeVuxXlWrJZOGfzow EgwA==
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=8IwnLBCb9tFOLRWmMxGhZA/534sSr8LovDaFAzGUd70=; b=HPAxfZC2EkeLVtCAKylvjmhUoSMEYx098ENqG1xnjrGgrmuD9tOEU26S3eOyhzkjIO SO3I0oxZpJ5Xz3I8hVTF2OwyFDBbVF4PKmfQh4Z6JoIKP0hLvF/aXtuSq7zZ67Ph9H9/ 8OWO+2dufy5AeFkVLomeR6q4pBoWq984Ip5rUmJ/AnBt05N1DOct05q5v7DoDP5YzFeF a2fK86S3LpopQllBHEiJM4Ck6Lx3dHhF+r1NxK0QgL3lcDMowGvKfVy7baKh3JMiJKJg qEPusXZguNAV/G2J4q5gRw+AAvGagIBviWGGDdG4mGHVyakPXukLGC+Y2jpbqCWSd3aK SK3w==
X-Gm-Message-State: AHQUAuZrcTgItR9Z6uqhHPcl2b13bR1LNOXJ1t7m4D5i9CH7r/hTEjrX T5vOQXRoU6a67G1eABF60QZTFdrYYpjYwvYp9+8=
X-Google-Smtp-Source: AHgI3Ia1usE7ulIutwaUT/ma5LWf7x8WXZ6+G1Yy1TnvGVAItXqlg7GmJy3MHvm4ecrC0x5bJKeljcGBhGCAw6HqbTk=
X-Received: by 2002:a6b:d318:: with SMTP id s24mr3287281iob.6.1550007087105; Tue, 12 Feb 2019 13:31:27 -0800 (PST)
MIME-Version: 1.0
References: <1b58312a-ab8e-ccba-2f9b-884091e1c603@nostrum.com> <27724fb0-25ee-0226-b2ee-2b861a34cbf2@gmail.com>
In-Reply-To: <27724fb0-25ee-0226-b2ee-2b861a34cbf2@gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 12 Feb 2019 13:30:59 -0800
Message-ID: <CA+9kkMAQZaxw+Zv5SQ0fvCcfgD1W13V8X8HbVaN4a__hkyBSqQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, IASA 2 WG <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d38bbe0581b92576"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/4WdvfoOzLoCPwJmq0oZIFiPyK8w>
Subject: Re: [Iasa20] Odd deprecations in draft-ietf-iasa2-consolidated-upd-05
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, 12 Feb 2019 21:31:30 -0000

On Tue, Feb 12, 2019 at 1:15 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Hi Robert,
>
> 3929 has no explicit time limit, which these days is considered bad
> practice for procedural experiments. So yes, it isn't this WG's
> job to decide. But the IETF can of course decide. If it's clear
> that this is subject to Last Call comments, is there really a problem?
>
> I don't see how the lack of experimental deadline makes it this WG's job
to decide--can you clarify your thinking?  In this document's case, it is
hard to call the experiment done when it has never been exercised.  We can
say that the threat of it has been useful, but that the actual methods are
"not proven" (in the Scots legal sense).

My take on why they were included was more that they included the phrase
"IETF Executive Director"; the doc says that specific methods require
telling the IETF Executive Director something (e.g. that you volunteer to
serve).  The working group concluded that this didn't mean the new
Executive Director, but meant the Secretariat role that used that term
before.  I personally would fix that with an erratum, rather than
deprecation or obsolescence.

I may, of course, have a slight bias here.

Ted