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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 13 February 2019 00:49 UTC

Return-Path: <brian.e.carpenter@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 D1B34130E11 for <iasa20@ietfa.amsl.com>; Tue, 12 Feb 2019 16:49:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 tFJT1POY6Lv3 for <iasa20@ietfa.amsl.com>; Tue, 12 Feb 2019 16:49:38 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 5B0A1130EAF for <iasa20@ietf.org>; Tue, 12 Feb 2019 16:49:38 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id s22so300775pfh.4 for <iasa20@ietf.org>; Tue, 12 Feb 2019 16:49:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=qDD1K0vqcw474EpoWHiKtMWkGH8rDpPf6U1o5HL2GBI=; b=HQUzH+YtN4CZwM9SKebKSaIyK2trMLhC5YeMlTxkLqtCVgaCAUsXUD2VTcUSpBwrj/ md7bqfum17JhN0Qy61Y2wlJAito7hXIY84RBk7ZIG3Fky1TeOcQhhLg2aDmkvYHhmANG y7aSz2Y9fHgGUflA9Q8dVVZtr2gxZ5BbiLhJGhulYKwKu6qpUrVjQgpal0v5QryUNvQY TbYMnZSt6b2zWfJKGyEex86/bq8e6Q4NhuX3YA9+T4Hd8SU0nRBvxeJdyL9byOFVfn0i q0opaJ3bw1lt9N+t0rCfTC5bSwozq4GgzQ0fAokZNcjhOciCJTEfo2xXivhbRQzVawx+ jF0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=qDD1K0vqcw474EpoWHiKtMWkGH8rDpPf6U1o5HL2GBI=; b=iGVSkFC4K/acwQG1PE78SFQNSf8g/C8HcqubiwF9AK68ps/Rm5acwghuDzKHU1PLlW g6xOHSAMBgMrD85wrmqGyg3PE9SvxUtFESS0v17GTGfN0jzMnHNOBZxpjK14vSFEYntY QRjXWplQ/wqelWlI/JEPSkJ861qDJVakQnyDZjF025WxvgK7Y0D1e06IRYPyeB84m5V7 w3ZdQ2MmaYX41fN3Dj8veGubIGCWJZNFKIU/iyGiHOGu819c5aS65Sz+Hpgk7Nw2t2jw Hhm/bGjgsOsa1x+FVjhgp5YXAYMh4FmLRD9if37aRLET9y+CVDVH6SEPNlL+cjWmrsT7 8Hdw==
X-Gm-Message-State: AHQUAuapfTI41Li8HN4cGBtZo15AKesL+FrIIbOiCqoEgG+AVqSnG3EQ xMfZYn7faPoEPiMLDNeeEI7KZK/b
X-Google-Smtp-Source: AHgI3IbEpxEu80tS5gYz6PaEfqBLDbo4DpkpkXeJL0uvT+Lk5DURz8oMIk4Z09f31lK4XgV6Ls2ElA==
X-Received: by 2002:a62:1981:: with SMTP id 123mr2905242pfz.69.1550018977527; Tue, 12 Feb 2019 16:49:37 -0800 (PST)
Received: from [192.168.88.29] ([103.29.31.113]) by smtp.gmail.com with ESMTPSA id u87sm39595263pfi.2.2019.02.12.16.49.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Feb 2019 16:49:36 -0800 (PST)
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Robert Sparks <rjsparks@nostrum.com>, IASA 2 WG <iasa20@ietf.org>
References: <1b58312a-ab8e-ccba-2f9b-884091e1c603@nostrum.com> <27724fb0-25ee-0226-b2ee-2b861a34cbf2@gmail.com> <CA+9kkMAQZaxw+Zv5SQ0fvCcfgD1W13V8X8HbVaN4a__hkyBSqQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <42c4d5bc-db36-dcb2-6813-719e0f1e5d24@gmail.com>
Date: Wed, 13 Feb 2019 13:49:31 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <CA+9kkMAQZaxw+Zv5SQ0fvCcfgD1W13V8X8HbVaN4a__hkyBSqQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/_1DKPZHKj5wziCPwxSd1p1jYEj8>
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: Wed, 13 Feb 2019 00:49:40 -0000

On 2019-02-13 10:30, Ted Hardie wrote:
> On Tue, Feb 12, 2019 at 1:15 PM Brian E Carpenter <brian.e.carpenter@gmail.com <mailto: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?  

I agree entirely - please re-read my sentence, whose syntax could be improved ;-).

> 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).

Yes. But if we (the IETF, not this WG) want that threat to continue, surely "experimental" is the wrong status?
  
> 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.

That's a perfectly defensible position, which is why I suggested calling this out explicitly in IETF Last Call. 
 
> I may, of course, have a slight bias here.

Regardless of that, I think we're agreeing that it isn't this WG's job to decide, but it probably *is* our job to point out the obsolete terminology.

Regards,
    Brian
 
> Ted