[Tls-reg-review] [IANA #1264437] expert review for draft-ietf-emu-tls-eap-types (tls-parameters)

Amanda Baber via RT <drafts-expert-review-comment@iana.org> Wed, 15 February 2023 18:37 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 DE36EC165767; Wed, 15 Feb 2023 10:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level:
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 g5Fa9lpYuyF7; Wed, 15 Feb 2023 10:37:34 -0800 (PST)
Received: from smtp.lax.icann.org (smtp.lax.icann.org [IPv6:2620:0:2d0:201::1: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 9C4C9C14E514; Wed, 15 Feb 2023 10:37:15 -0800 (PST)
Received: from request6.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp.lax.icann.org (Postfix) with ESMTP id 8D70EEF4E2; Wed, 15 Feb 2023 18:37:14 +0000 (UTC)
Received: by request6.lax.icann.org (Postfix, from userid 48) id 791E54B12E; Wed, 15 Feb 2023 18:37:14 +0000 (UTC)
RT-Owner: david.dong
From: Amanda Baber via RT <drafts-expert-review-comment@iana.org>
Reply-To: drafts-expert-review-comment@iana.org
In-Reply-To: <rt-5.0.3-120107-1674145599-860.1264437-9-0@icann.org>
References: <RT-Ticket-1264437@icann.org> <rt-5.0.3-49710-1674071725-1336.1264437-9-0@icann.org> <rt-5.0.3-56953-1674079809-1714.1264437-9-0@icann.org> <349F6743-C4F4-40EC-9FAB-862BA3E01932@akamai.com> <BF3968F6-2341-4513-AF56-E7A16613D037@deployingradius.com> <9E0B3E66-DDB9-4CBF-98A0-7B30A0F5093B@akamai.com> <rt-5.0.3-120107-1674145599-860.1264437-9-0@icann.org>
Message-ID: <rt-5.0.3-4160389-1676486234-1163.1264437-9-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #1264437
X-Managed-BY: RT 5.0.3 (http://www.bestpractical.com/rt/)
X-RT-Originator: amanda.baber@icann.org
CC: emu@ietf.org, tls-reg-review@ietf.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Wed, 15 Feb 2023 18:37:14 +0000
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/0F0xvzFfSGEpO2PsU7VNVWBKnwg>
Subject: [Tls-reg-review] [IANA #1264437] expert review for draft-ietf-emu-tls-eap-types (tls-parameters)
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, 15 Feb 2023 18:37:35 -0000

Hi Rich, Yoav, Noah,

Does version -12 require a new review? This was updated today and is on the telechat tomorrow:

https://datatracker.ietf.org/doc/html/draft-ietf-emu-tls-eap-types-12

thanks,
Amanda

On Thu Jan 19 16:26:39 2023, rsalz@akamai.com wrote:
> > At this point, I don't think so. We have implementations which use
> > these values.
> 
> That's fine, interop over all.
> 
> > Does the space cause a problem? I don't recall seeing guidance on TLS
> > exporter labels which suggest that spaces should be avoided.
> 
> There isn't guidance.  IT's just that I noticed that the internal
> whitespace can lead to confusion, such as mine.
> 
> You've addressed my concerns.  I approve this.  Still need Yoav or
> Nick to agree.
> 
>