From nobody Tue Oct 26 08:26:45 2021 Return-Path: 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 25C6A3A12FF for ; Tue, 26 Oct 2021 08:26:44 -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=unavailable 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 EsZudBmERqNg for ; Tue, 26 Oct 2021 08:26:39 -0700 (PDT) Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (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 741503A1304 for ; Tue, 26 Oct 2021 08:26:39 -0700 (PDT) Received: by mail-ua1-x92a.google.com with SMTP id f24so10726357uav.12 for ; Tue, 26 Oct 2021 08:26:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=N2z7c4ujEVPRXunNn7vgMkoMnU2U7XZ5++eQXZuDVVE=; b=kJKIhoiDiU+ULE1vhanMB+iY5ULRiakuq17BVWw4+MwGQmKygF0ydBBX08Xy88Exec dPmgcWjbcuiSzXF+BkjC6dhlWbxJWw/hER3Ub3/DeQEs9J/0AFbS86k0DK8NNAezpH3n B/MMrPm8FAGJSRRyiZ4IBL3ND4covyMdrYRBjeSQe/912zL3b6vNSuzh8vLzVMGwxuew vs5U1SM10JsvCZJlBk1qNkBhdYY6vz7PQ9EGLiHpb+m4N9ydjNUT3Qkjy1dC8R0N4tzg SK4RsyMcgE5sOW7TjUNMNKW/dEjDb/PuwF2+9xYnbEOVmzw9PiSpQyuUEhjqCSxVvsrd 1qfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=N2z7c4ujEVPRXunNn7vgMkoMnU2U7XZ5++eQXZuDVVE=; b=BcmBtrwvvYkI///7Dflcq6mCJATDER23mpnc4q4HIGfKmEQ/1zFEO5Nbdo9vI0b0uD JesQPCLNWfnTgrc8vtiSZrDcNSB4ySle8eldadBbpxsDBqL+w6SjMoSxQIUOMCGQ1dRA Ja1RACzu4ePZ8nViP9JA0tIqBC7WE2uJ0LtUfftaLslwRftz2Tr7znIyhE8bQnTLubfu oMjs3eqnwVDO81WVdMqjSc8AlidObqMiPZOZqoVegvwIKVAtPL67QIAPNqFpwIVV7gIV su1lLS/wf9d3musdzFZyITW4achlfzYeYbabctzY0OuWE0n2yxr3BBdX3qb7E7rLKbHZ xDdQ== X-Gm-Message-State: AOAM5303YbCaY2NDb1YxkrNqYzevHV274913HR074Ig9axOHjhLhEaWo WnLAmYY8JHCLthMfJKEB/wbEVQ6f1w1sJfTYLcE8d4b5 X-Google-Smtp-Source: ABdhPJxptwkh3bNE6bTF6y5uRNKg1VzubUcwrbZC9zJluiA8Q4UhBMXfXwbuL+hlzZj3RyBtn5ElCkwPKXf/OL1c/Yk= X-Received: by 2002:ab0:6f01:: with SMTP id r1mr13119142uah.52.1635261995206; Tue, 26 Oct 2021 08:26:35 -0700 (PDT) MIME-Version: 1.0 References: <6DC9931F-7CEC-4DD3-87BC-EEA93A7B9646@akamai.com> In-Reply-To: From: Ira McDonald Date: Tue, 26 Oct 2021 11:26:16 -0400 Message-ID: To: Hannes Tschofenig , Ira McDonald Cc: "Salz, Rich" , Ilari Liusvaara , IETF TLS Content-Type: multipart/alternative; boundary="00000000000056ca7805cf431ad1" Archived-At: Subject: Re: [TLS] TLS Flags and IANA registration policy 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2021 15:26:44 -0000 --00000000000056ca7805cf431ad1 Content-Type: text/plain; charset="UTF-8" Hi, I agree that the "Recommended" column in the IANA registry (which is frequently misunderstood) should just be renamed to "IETF Consensus". Obvious and self-explanatory. Cheers, - Ira On Tue, Oct 26, 2021 at 10:45 AM Hannes Tschofenig < Hannes.Tschofenig@arm.com> wrote: > Rich, this makes more sense. Maybe the column should say "IETF Consensus" > (Y/N) instead of Recommended. > > In any case, the draft should say what recommended means for the flags > values. > > -----Original Message----- > From: TLS On Behalf Of Salz, Rich > Sent: Tuesday, October 26, 2021 3:19 PM > To: Ilari Liusvaara ; IETF TLS > Subject: Re: [TLS] TLS Flags and IANA registration policy > > The Recommended column is "was this done via IETF consensus." Some of the > values you think are odd are from pre-1.3, done by consensus, even if the > protocol is now outdated by 1.3 > > If there are some 1.0 and 1.1 extensions that are not defined in 1.2, then > that deprecation draft should suggest IANA changes. > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls > --00000000000056ca7805cf431ad1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I agree that the "R= ecommended" column in the IANA registry (which is frequently misunders= tood)
should just be renamed to "IETF Consensus".=C2=A0= Obvious and self-explanatory.

Cheers,
-= Ira


On Tue, Oct 26, 2021 at 10:45 AM Hannes Tschofenig <Hannes.Tschofenig@arm.com> = wrote:
Rich, thi= s makes more sense. Maybe the column should say "IETF Consensus"= =C2=A0 (Y/N) instead of Recommended.

In any case, the draft should say what recommended means for the flags valu= es.

-----Original Message-----
From: TLS <tls= -bounces@ietf.org> On Behalf Of Salz, Rich
Sent: Tuesday, October 26, 2021 3:19 PM
To: Ilari Liusvaara <ilariliusvaara@welho.com>; IETF TLS <tls@ietf.org>
Subject: Re: [TLS] TLS Flags and IANA registration policy

The Recommended column is "was this done via IETF consensus."=C2= =A0 Some of the values you think are odd are from pre-1.3, done by consensu= s, even if the protocol is now outdated by 1.3

If there are some 1.0 and 1.1 extensions that are not defined in 1.2, then = that deprecation draft should suggest IANA changes.

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in = any medium. Thank you.

_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
--00000000000056ca7805cf431ad1--