IETF Logo Mail Archive

[Tls-reg-review] [IANA #1270741] Re: Re: Request to register value in TLS ExtensionType registry

Amanda Baber via RT <iana-prot-param@iana.org> Wed, 12 April 2023 18:15 UTC

Return-Path: <iana-shared@icann.org>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A3ACC15270B for <tls-reg-review@ietfa.amsl.com>; Wed, 12 Apr 2023 11:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.647
X-Spam-Level:
X-Spam-Status: No, score=-6.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WE2S5zlwBiVn for <tls-reg-review@ietfa.amsl.com>; Wed, 12 Apr 2023 11:15:42 -0700 (PDT)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [192.0.33.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 963CDC1524DD for <tls-reg-review@ietf.org>; Wed, 12 Apr 2023 11:15:42 -0700 (PDT)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 59943E3C5A; Wed, 12 Apr 2023 18:15:42 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id 54884552CE; Wed, 12 Apr 2023 18:15:42 +0000 (UTC)
RT-Owner: amanda.baber
From: Amanda Baber via RT <iana-prot-param@iana.org>
Reply-To: iana-prot-param@iana.org
In-Reply-To: <A29AA1DB-1308-4B14-A607-AD4AA111445B@akamai.com>
References: <RT-Ticket-1270741@icann.org> <RT-Ticket-1270702@icann.org> <CAKJMo+tT8M356=VkD3iXyu24TajfZ6U5cnbT=cswngW4Vx3=1A@mail.gmail.com> <224C05D7-31A5-40DF-A422-31DB738CD1C2@akamai.com> <rt-5.0.3-3704678-1681254905-391.1270702-37-0@icann.org> <A29AA1DB-1308-4B14-A607-AD4AA111445B@akamai.com>
Message-ID: <rt-5.0.3-3788492-1681323342-291.1270741-37-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1270741
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
To: rsalz@akamai.com
CC: nicholas.sullivan+ietf@gmail.com, ynir.ietf@gmail.com, tls-reg-review@ietf.org, borispismenny@gmail.com
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 12 Apr 2023 18:15:42 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/DUHufmTFMNQDQzrcpuqRnBAWlc4>
Subject: [Tls-reg-review] [IANA #1270741] Re: Re: Request to register value in TLS ExtensionType registry
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.39
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2023 18:15:46 -0000

Hi Yoav, Nick,

Can one of you approve this request as well? I jumped the gun in assigning it w/one approval only and have temporarily removed it from the registry.

thanks,
Amanda

On Tue Apr 11 17:08:01 2023, rsalz@akamai.com wrote:
> This seems fine, and I propose using 60 (the first unassigned number).
> 
> 
> From: Boris Pismenny <borispismenny@gmail.com>
> Date: Tuesday, April 11, 2023 at 10:13 AM
> To: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
> Subject: [Tls-reg-review] Request to register value in TLS
> ExtensionType registry
> 
> Dear expert reviewers,
> 
> Following the discussion at IETF116, it was decided to assign a custom
> code point for https://www.ietf.org/archive/id/draft-pismenny-tls-
> dtls-plaintext-sequence-number-
> 01.txt<https://urldefense.com/v3/__https:/www.ietf.org/archive/id/draft-
> pismenny-tls-dtls-plaintext-sequence-number-
> 01.txt__;!!GjvTz_vk!SWfLlCKryKXJi_3pyEmw82ih3yOk-
> cRQCwGlDgrNL46Dr6XmZirqCduGlnSPOs8WnWeEcjBs52jJ0EEbGZsb$>
> To the best of my understanding, it implies registering the proposed
> TLS extension type, as specified in the draft above:
> * The Extension Name should be sequence_number_encryption_algorithms
> * The TLS 1.3 value should be CH,HRR,SH
> * The DTLS-Only value should be Y
> * The Recommended value should be N
> * The Reference document should be
> https://www.ietf.org/archive/id/draft-pismenny-tls-dtls-plaintext-
> sequence-number-
> 01.txt<https://urldefense.com/v3/__https:/www.ietf.org/archive/id/draft-
> pismenny-tls-dtls-plaintext-sequence-number-
> 01.txt__;!!GjvTz_vk!SWfLlCKryKXJi_3pyEmw82ih3yOk-
> cRQCwGlDgrNL46Dr6XmZirqCduGlnSPOs8WnWeEcjBs52jJ0EEbGZsb$>
> 
> Thanks,
> Boris

v2.23.0 | Report a Bug | By Email