Re: [TLS] Opsdir last call review of draft-ietf-tls-iana-registry-updates-04

Sean Turner <sean@sn3rd.com> Tue, 27 February 2018 21:01 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5BB12D94C for <tls@ietfa.amsl.com>; Tue, 27 Feb 2018 13:01: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 aKZhgbNVPFtT for <tls@ietfa.amsl.com>; Tue, 27 Feb 2018 13:01:37 -0800 (PST)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 8A6C41242EA for <tls@ietf.org>; Tue, 27 Feb 2018 13:01:37 -0800 (PST)
Received: by mail-qt0-x22c.google.com with SMTP id n12so304573qtl.5 for <tls@ietf.org>; Tue, 27 Feb 2018 13:01:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DlVcPr0c5m3mtLjdqQ3ccuv7/29V7iaJkq57JswjQ3k=; b=SaWJofV31XIpHmkKqtTUwam5/0r0p+V5pnWHGCfg0DBsK8cttgWS87qKn/agixmN6E 6uftbRPO891VAjzyDy8qpoLg6yWBsri3bGVjOzgPrrBQnumE07tUNtzHq9yj02O++lcN N89etotlubQTdEb4TK3lEM+Z+cuveEfK8bltQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DlVcPr0c5m3mtLjdqQ3ccuv7/29V7iaJkq57JswjQ3k=; b=KsjHzzL8pvanj1FdVHFeV4vhdrTZ5N6zK1yOUMi970g6y+Ap/+49dlIqiWcUTlACGi FsxGhT6j5LGd3un+5k7TjdoSEHeyQn3qLik0TRiqT6757fAQIc0J0SJj/AEE8uDzJBh/ 9iXhCjCzPVxD+AHL3+M20GLnrc/XthU/fAiqzJmJmQ4XW1ceO/bLm9/uUEc3kxoqouv/ RbP9KILOPUD89cxQaNg4SdjGfTCNWHXb6RMfVF1LNvaDDvwmywX5bT8WwhlwwVs/3af8 lYYrXaMJOx1W2diTQ1/fYpuMnV3R7PZ8w/8CKH3cHGFEtvk2Bod+gCXuxXPLjiyj5SxX SvHQ==
X-Gm-Message-State: APf1xPC23vqLxw/f7+1Q68jmZ94+Y9g+nUPQ7XAKR3i7m+HyVfYTAdZU R3q+t7o0E2qUfdaKaD2Mi1TvPA==
X-Google-Smtp-Source: AG47ELtSHm6YouWn2sHtFiJH/YGFta/+2V/81NEdBsOF5jFw43wSJapSBaX3dzP3qlitIg0UMzDc+Q==
X-Received: by 10.200.24.46 with SMTP id q43mr26341321qtj.309.1519765296742; Tue, 27 Feb 2018 13:01:36 -0800 (PST)
Received: from [172.16.0.18] ([96.231.218.194]) by smtp.gmail.com with ESMTPSA id u4sm45091qtg.28.2018.02.27.13.01.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Feb 2018 13:01:36 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <20180227165308.GZ50954@kduck.kaduk.org>
Date: Tue, 27 Feb 2018 16:01:34 -0500
Cc: Russ Housley <housley@vigilsec.com>, Dan Romascanu <dromasca@gmail.com>, ops-dir@ietf.org, IETF TLS <tls@ietf.org>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <29391D2F-B263-4EEE-81CF-1C32AC627B44@sn3rd.com>
References: <151912347695.29703.11473433478669184845@ietfa.amsl.com> <D27C238D-C8F1-4FBC-A546-4555898CAE99@sn3rd.com> <57ECF9E5-80AC-4353-9E46-73A19BD085E3@vigilsec.com> <20180227165308.GZ50954@kduck.kaduk.org>
To: Benjamin Kaduk <kaduk@MIT.EDU>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/fWKDxcturiq4UvY82Ybmg3PLXvc>
Subject: Re: [TLS] Opsdir last call review of draft-ietf-tls-iana-registry-updates-04
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Feb 2018 21:01:39 -0000


> On Feb 27, 2018, at 11:53, Benjamin Kaduk <kaduk@MIT.EDU> wrote:
> 
> On Tue, Feb 27, 2018 at 11:25:29AM -0500, Russ Housley wrote:
>> 
>> 
>> Wouldn't it be sufficient to add a note a the bottom of the registry that says:
>> 
>>   If an item is marked as not recommended it does not necessarily mean
>>   that it is flawed, rather, it indicates that either the item has not
>>   been through the IETF consensus process, has limited applicability,
>>   or is intended only for specific use cases.
> 
> Basically.  But, "not marked as recommended", please.

Check out the PR:
https://github.com/tlswg/draft-ietf-tls-iana-registry-updates/pull/62