IETF Logo Mail Archive

Re: [TLS] Consultation About Assignment of ExtensionTypes

Rob Sayre <sayrer@gmail.com> Fri, 19 June 2020 05:27 UTC

Return-Path: <sayrer@gmail.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 0AF913A10DB for <tls@ietfa.amsl.com>; Thu, 18 Jun 2020 22:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 PzuTUqDTzLF4 for <tls@ietfa.amsl.com>; Thu, 18 Jun 2020 22:27:09 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 7E7D53A10D0 for <tls@ietf.org>; Thu, 18 Jun 2020 22:27:09 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id r2so9936897ioo.4 for <tls@ietf.org>; Thu, 18 Jun 2020 22:27:09 -0700 (PDT)
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=udWcV4TbRlWcVJjdp0KDWPbl8GmTqKJ0tqFss4ipQog=; b=XvIwP15NpoJ1eWUNfOt9arDhS+I0WlvSLas7/xV0ypIlkdG/HlWwJRs5jU4yUclQqo 74kkDFDJjHBcGgMkSdZI6BMQ9hV53EQk53WVutPlYOGej+RXvea3NIvSQIigUfnySV7O rgpOV3QsEym993khqtyZGonVp/WFBECf3Y/lABkXa1zvA9BzavSyZemgKRyjogZCdD2b HFL5ruB0t/mUmGnlhRvEEskHv16Fwvts0XAx+ZHsTKHARXHSg/lgqHgOtG/kcwl0i5Hm DHsrtrxKpOrFYSrF51kMCC7hCTyfDfhHj+8+Bcr2RVIK1lHKnOyqj5reDXoMAfSlefg1 bxdw==
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=udWcV4TbRlWcVJjdp0KDWPbl8GmTqKJ0tqFss4ipQog=; b=jDnAWMoLebtEcFERp2tSpr/7hqJpdmD5Kx1TI5AIrZyS9Ue5EoIItk5WsEwdFsIM2Q jEx2ZbcuLOPc/Yc+Fsqj+VE48Ogw7DBhVAb0L008ss0CNplmmG4qsT5PPXlKy3h9YS+4 c9FeTU5PoBvy0gzbUSRVxlgMhh12Pip7cut45P+kR/Wu7GJSxLTJvBvzhp0Y2Whh+eAE zuHTpG1wBKYsxIJA3Nd56UyrYS+rkG6klQhz2vcrTEg5D/BEzi0sCo2frvkc3OROyrVZ S3n0TKFFnBrmmIyixCOXf8IeEDx/uYIoqxzF6S6B0Kkpsgd2qyL58PTVTLfyZ/25xecF kxIQ==
X-Gm-Message-State: AOAM531ftEcvjsPpzstEEMaomi5L11XNhCidpwhIT0EZUuAC871im+Am +4E//sEkYswC1d6gTk9/NEljBpQJVUWZAgsc/nE=
X-Google-Smtp-Source: ABdhPJzxkg6/bRTib48ku8flgbmHW1SDqdMz0t0eV+A9Yc8UGGjHLsldDt4sz+hc7O4ZNL/TwZSMTlAbBKh3hnp96Lk=
X-Received: by 2002:a02:1784:: with SMTP id 126mr2201097jah.53.1592544428668; Thu, 18 Jun 2020 22:27:08 -0700 (PDT)
MIME-Version: 1.0
References: <2F7403F6-C28A-4F5A-8128-A4B4609CA7C5@gmail.com>
In-Reply-To: <2F7403F6-C28A-4F5A-8128-A4B4609CA7C5@gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Thu, 18 Jun 2020 22:26:57 -0700
Message-ID: <CAChr6Szk7J6cvG80Om9PKRcOv=cd-MfpUxryrKg14zvBfWcCAg@mail.gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f5bd0e05a86924f9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/tN2_r8CD1ftRlgnA4a8ZppVg2j8>
Subject: Re: [TLS] Consultation About Assignment of ExtensionTypes
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: Fri, 19 Jun 2020 05:27:11 -0000

On Sat, Jun 13, 2020 at 10:20 AM Yoav Nir <ynir.ietf@gmail.com> wrote:

>
> To re-iterate, the policy for the registry is “Specification Required” and
> a specification is available. Unless we hear convincing arguments to the
> contrary, we will approve this allocation. We just prefer to have the
> kerfuffle before the assignment rather than afterwards.
>

If the IANA experts feel the 99 page PDF is "sufficiently clear and
technically sound" [1], then it should appear in the registry. [2]

It seems like it should appear with a "Recommended" value of "No", and no
value in the TLS 1.3 column, since the document says "The Middlebox
Security Protocol builds on TLS 1.2". [3]

Is that what's being proposed?

thanks,
Rob

[1] https://tools.ietf.org/html/rfc8126#section-4.6
[2]
https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#tls-extensiontype-values-1
[3]
https://docbox.etsi.org/CYBER/CYBER/Open/Latest_Drafts/CYBER-0027-2v020-TLMSP-Transport-Layer-Middlebox-Security-Protocol.pdf
(Section 1, scope)

v2.23.0 | Report a Bug | By Email