IETF Logo Mail Archive

Re: [saag] Discuss at SAAG? was Re: nation state crypto profiles - draft-jenkins-cnsa-cmc-profile-00

Sean Turner <sean@sn3rd.com> Thu, 04 October 2018 15:59 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 282C9130EF2 for <saag@ietfa.amsl.com>; Thu, 4 Oct 2018 08:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] 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 0ajyW1HQp54v for <saag@ietfa.amsl.com>; Thu, 4 Oct 2018 08:59:03 -0700 (PDT)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 D59A5130EE8 for <saag@ietf.org>; Thu, 4 Oct 2018 08:59:02 -0700 (PDT)
Received: by mail-qt1-x829.google.com with SMTP id v19-v6so10459136qtg.2 for <saag@ietf.org>; Thu, 04 Oct 2018 08:59:02 -0700 (PDT)
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=wgjicPRMQRgKVUBMzddumVX/cRO/AGsasOa4aOOI8i0=; b=nSdbephbVfA/54005Z5nMQNp3y1CbpJXAyWHdip2ZRbEKo2FkUUXtd/d6xDB2uzFk8 TO+0iXVLsI2Am4Db18ASu4v12+e7Lf3fKGlgU7Gq0pLY2hN+VdYWiQMS+WkiNE4IZHIz GIuG7iPH2jNmpHBQBlSrPafSDuCXowdMibToc=
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=wgjicPRMQRgKVUBMzddumVX/cRO/AGsasOa4aOOI8i0=; b=QSDJrKRTPKL4LxCxmURBUQh+u4tTu2u7mNSl2Y+TqT6IiQXzgQCImEe4V2NmlHTvdh sZLJbFk1PUAU2LSc7hkWuUUzIpCRPmNSA+/oIU5dTOfzqXPX3KmD+WjQm2piRnbOx7MM Ob45e60ab0zJksrVgPzgeLe6CHa5pV2hTmd9FQqgEeJ0zk45okWf5KrfUe+tT3+sWFL1 BSzzhuAXHGmuY1V8ffzKwAR2Queqa7YF8g5cmYY5IJJLTQBa1HbToN/u4c5AG0NXrudJ c3At4wPEH4DAJXSKPBw19+6Zqwpo92fCv2ushvEPe2Hqz7S4omliFBdwoaDaG5Vg3qAr q9tg==
X-Gm-Message-State: ABuFfoiDP3+vqtaLRY5WFVF9Sq9mtcnBVE4xhjjN5RVjkaCY8p+tjF4z N2jxMMdS8OMmn8f41AuO8i+IAQ==
X-Google-Smtp-Source: ACcGV63u9W6mqMUfjOOzgxSmvPO5II/AhAZJyVeXCGcjNzYcZgEWtu6L/kyHw1hY4ObvITFRSKWoPw==
X-Received: by 2002:aed:3445:: with SMTP id w63-v6mr6039917qtd.339.1538668742075; Thu, 04 Oct 2018 08:59:02 -0700 (PDT)
Received: from [172.16.0.18] ([96.231.224.191]) by smtp.gmail.com with ESMTPSA id x12-v6sm2699488qtk.6.2018.10.04.08.59.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Oct 2018 08:59:01 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <20181004155028.GK2164@localhost>
Date: Thu, 04 Oct 2018 11:58:59 -0400
Cc: Rich Salz <rsalz@akamai.com>, Paul Wouters <paul@nohats.ca>, "saag@ietf.org" <saag@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0568644D-0598-4FF7-B250-985EBEEEA025@sn3rd.com>
References: <7CB10AE4-09C1-4AC5-B255-6489EF1FAE78@akamai.com> <alpine.LRH.2.21.1810021734350.12702@bofh.nohats.ca> <BEC2489D-FE1E-4E55-A88C-05E0143F8415@gmail.com> <20181002220720.GD56675@kduck.kaduk.org> <CABcZeBPJjfjdxbHCWFQFLJcnMKZSCpVb0oEZPhpymVgu-=bspQ@mail.gmail.com> <4DCAFB4A-9CDB-4692-9382-FBD04DC8FA16@akamai.com> <DBAF8917-3E3B-41DA-851B-5A925423ED7C@sn3rd.com> <20181004155028.GK2164@localhost>
To: Nico Williams <nico@cryptonector.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/c6JcXoEBjr5U5r0bkjeF6a_ykY0>
Subject: Re: [saag] Discuss at SAAG? was Re: nation state crypto profiles - draft-jenkins-cnsa-cmc-profile-00
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2018 15:59:12 -0000


> On Oct 4, 2018, at 11:50, Nico Williams <nico@cryptonector.com> wrote:
> 
> On Thu, Oct 04, 2018 at 10:53:20AM -0400, Sean Turner wrote:
>>> On Oct 4, 2018, at 10:49, Salz, Rich <rsalz@akamai.com> wrote:
>>> 	• The reasoning here was that having code points marked Not
>>> 	Recommended was better than having people squatting.
>>> 
>>> They’re actually “no comment” as opposed to Not Recommended.  The
>>> only way something gets to be recommended is if it’s a WG document.
>>> This is, admittedly, a fine point and could well be lost on many,
>>> but it’s important.
>> 
>> Agreed that it will be lost on most, but I think it kind of makes
>> sense.  The interesting flip side here is that there are going to be
>> some perfectly good algorithms are not marked as Recommended.
> 
> That is just fine.  There's no reason we should want all "perfectly good
> algorithms" to be, or even any other than those we already have as,
> Recommended.
> 
> To go from "no comment" to Recommended, a "perfectly good algorithm"
> would have to be more than perfectly good: the IETF would have to need
> additional Recommended algorithms due to obsolescence of existing ones.

Exactly!

spt

v2.23.0 | Report a Bug | By Email