Re: [TLS] heads-up: ALPN ID allocation for NTP security with "Recommended" as "Y"
Ben Schwartz <bemasc@google.com> Wed, 11 March 2020 01:25 UTC
Return-Path: <bemasc@google.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 3E3D13A0D96 for <tls@ietfa.amsl.com>; Tue, 10 Mar 2020 18:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.588
X-Spam-Level:
X-Spam-Status: No, score=-9.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 nda-2cBsMofi for <tls@ietfa.amsl.com>; Tue, 10 Mar 2020 18:25:27 -0700 (PDT)
Received: from mail-wm1-x330.google.com (mail-wm1-x330.google.com [IPv6:2a00:1450:4864:20::330]) (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 431763A0D94 for <tls@ietf.org>; Tue, 10 Mar 2020 18:25:26 -0700 (PDT)
Received: by mail-wm1-x330.google.com with SMTP id r7so2027618wmg.0 for <tls@ietf.org>; Tue, 10 Mar 2020 18:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KQxAsG2lwj1v0TAgHJNjK7/IJ/VZ1lphp2O/hXxqDmU=; b=moRb7qGEnptiWOQNIw/cuTVJwtqH8f9YqKT4QSKnfZrryPRp8Vn8qYzZug8ibe6BfW DYFgbW2N1ocEsq8rcVQohYk8pGTpa8dzrTcwUY3eDFw2/PXdjg6l+eWBi79WUwlRcTQx gV7Xd1OBmXyOJ6zexFYjNw6JOC18ZjvKY/B1Ewf0Wq8ib61KQxvF3j3vLBg2p5WtsW/r dU4au9KtiZIFrBjXQ1LhsOiqQPG0uI7WWpE4mjVjNdrL1o9RQ/Yzvgmu/TvW5sFgSnaL 6yTCGZEvmY7LYRQgcvNNGlm5uAULHusHchrXNMEnx2SY25pEryOz/X0qpM6OxYDujakl 0hjA==
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=KQxAsG2lwj1v0TAgHJNjK7/IJ/VZ1lphp2O/hXxqDmU=; b=CTn5cPVK5EJV7QTPSatSLcWN3DDfgiBZeDmWjcOqEs8rgagE2uWhUq07mZ8ikgSQ0f G5/WRF0hHKqQHWViTK4TS4G5uSlNZ1V5nVb48Zlzaj7J5vm+DXASIgb9STQq5PtKGeTk Q4x06W7o0V9w6GyydFwM6rkr7X+wrGMjvWFIfT1dXuHy0psUGzFKIBdQEOBo2Jp0V47E eseRUMjTgp9+N4+QuALR11gUQn5Yr0HBX6Q2+kKEdGH8GYqvJwM033FDehqYxv9K1IpO QVM4RoNssbUwP4XUs8V5TzEiY/jS9MJTGYEe73KL1EWQKDBHQxtarsqV/hKGYoxKMbOo RuAQ==
X-Gm-Message-State: ANhLgQ1mzrZynnxdFmY35jBzDdMiWvKXFhtmpS65zfI6RN/SIfv0CnAX l+ZY5GgFYC541QuNr8dPwZRJG5RZqZ21DDCLZDPXlLDf
X-Google-Smtp-Source: ADFU+vu58eacBXCzwY5Eck2pyGfJEJEiZZHh5HQHEt3Ax0O6EBP32BtZMCVEJqTegCEk9kz5dA0PuzYJ1bjHLcqI8A0=
X-Received: by 2002:a1c:9646:: with SMTP id y67mr449487wmd.42.1583889924888; Tue, 10 Mar 2020 18:25:24 -0700 (PDT)
MIME-Version: 1.0
References: <20200310234524.GH3439@akamai.com> <21fbb472-6aa8-4bdc-bf34-70fa95c5681c@www.fastmail.com> <6E43F2D3-1027-434C-B911-78C47CE81611@akamai.com>
In-Reply-To: <6E43F2D3-1027-434C-B911-78C47CE81611@akamai.com>
From: Ben Schwartz <bemasc@google.com>
Date: Tue, 10 Mar 2020 21:25:12 -0400
Message-ID: <CAHbrMsC4ZDfAabOF1SvfFUT=J+fB_5w0tdY14qQeHD+v+VaFdw@mail.gmail.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, "tls@ietf.org" <tls@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="00000000000061729e05a08a1c5a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/jXjE5KXqLEmDqDl2axq-zTU_DlI>
Subject: Re: [TLS] heads-up: ALPN ID allocation for NTP security with "Recommended" as "Y"
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 11 Mar 2020 01:25:32 -0000
I note that the exporter has "DTLS-OK: Y", but DTLS is not otherwise mentioned in the draft. Is there an anticipated need for NTS-KE to use DTLS? On Tue, Mar 10, 2020 at 8:17 PM Salz, Rich <rsalz= 40akamai.com@dmarc.ietf.org> wrote: > > (Is TLS the de-facto owner of ALPN? There are some issues being > discussed elsewhere that might affect future registrations.) > > I believe the TLS designated experts think so :) > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
- [TLS] heads-up: ALPN ID allocation for NTP securi… Benjamin Kaduk
- Re: [TLS] heads-up: ALPN ID allocation for NTP se… Martin Thomson
- Re: [TLS] heads-up: ALPN ID allocation for NTP se… Salz, Rich
- Re: [TLS] heads-up: ALPN ID allocation for NTP se… Ben Schwartz