IETF Logo Mail Archive

Re: [Uta] Second WGLC for draft-ietf-uta-rfc7525bis-05

Yaron Sheffer <yaronf.ietf@gmail.com> Mon, 14 February 2022 16:30 UTC

Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D377C3A1203; Mon, 14 Feb 2022 08:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-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 2hoJhf0gMGHx; Mon, 14 Feb 2022 08:30:15 -0800 (PST)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 92AB13A11F9; Mon, 14 Feb 2022 08:30:14 -0800 (PST)
Received: by mail-wr1-x435.google.com with SMTP id v12so27829274wrv.2; Mon, 14 Feb 2022 08:30:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=5/9tW3PE1F8PBlI49w/QE0gnbkfeuJ6hPbWB4AdrUBw=; b=EQzEQsrrYgj8n8vrTxR7+GSGxfiHm/CGpVEBaJkTEKZC01dGvJdpvLIOOETZmmssJp ueTjyZq3vqu9dMbJ0oMsip4JmHCezNnXQgAJghuhAvM8EK0B3lUudLvCtMMFMa7gxzPl xABnwzlVT1Cy5VcUQxtlXv9NixRCGgDmlsuisA7NzDDZwQ1oECqIG5Jh0y4/OHUmgb1X U/P0JXgkUHYGBYAOD5IkSZOaLQn8wN2I3j5pLj/JOZaCU0Forbk/fApFQxupwdU6jOmV eR1Xj0dbHUw3H0uY6tILCMm9Iyl4Qoh5XMIRj9JJDuRYlXhFIFVGOCSljCs54qpsflg/ gFdQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=5/9tW3PE1F8PBlI49w/QE0gnbkfeuJ6hPbWB4AdrUBw=; b=fRk5ZOKZwECehlsBXGgVRVwEArx+jy4txFIvR1vRsWpgO1aBEk7ksPgqc8OQf2nM98 ejB2SNkrEBGE6rDZfcyRHosHTEnoz7RXb1kIPY40G300NTDGzpMf1WEyD4aOAV8cX9Wb 6Gjxo4y5EyMf1bTBfjCCUwwigm9Fjm770/KqeLKjUZjcYxfzu5EedHDS5WS+UIPQHBoh tRDqIbIEIIsO5F6xaC4nMnh2pUhnblG+tw0MX2wEyQw/fWS6Sdg5GdKLXI7vlNRJeU8t mNtbhXZCk7hWdRYncNXo5IJ3jmYVJta17oeogiykwsM3ncpV8Xv9sSb3Lp3m7E7hRCGa NKIg==
X-Gm-Message-State: AOAM532GqadLAH/O0PSAO6g1ADIXBREny7KlteEEKQG6WItPbNNovG2q SwTzQyc6oPNSDVP/MT2ZRFo=
X-Google-Smtp-Source: ABdhPJx+3HR1XaA8f2YfHFu7AkcOJM6sN9CeRCEiylcymO5w+LVPXaSeeaWmOWIvwja7RY5Fkaw48A==
X-Received: by 2002:a5d:68cd:: with SMTP id p13mr322712wrw.537.1644856211803; Mon, 14 Feb 2022 08:30:11 -0800 (PST)
Received: from [192.168.68.108] (IGLD-84-229-146-220.inter.net.il. [84.229.146.220]) by smtp.gmail.com with ESMTPSA id u12sm15611115wrw.32.2022.02.14.08.30.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Feb 2022 08:30:09 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.57.22011101
Date: Mon, 14 Feb 2022 18:30:07 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>, "Olle E. Johansson" <oej@edvina.net>, Valery Smyslov <valery@smyslov.net>
CC: "uta@ietf.org" <uta@ietf.org>, Leif Johansson <leifj@mnt.se>, "draft-ietf-uta-rfc7525bis@ietf.org" <draft-ietf-uta-rfc7525bis@ietf.org>, "uta-chairs@ietf.org" <uta-chairs@ietf.org>
Message-ID: <A87001D0-FEAD-4346-93E0-F638725A0E38@gmail.com>
Thread-Topic: [Uta] Second WGLC for draft-ietf-uta-rfc7525bis-05
References: <021b01d82197$6cf5dc60$46e19520$@smyslov.net> <7C66DF11-FA4F-4FBD-A0A0-33B8701B676D@edvina.net> <1124F14E-0CA5-4B6F-B293-083D9F4EAC09@akamai.com>
In-Reply-To: <1124F14E-0CA5-4B6F-B293-083D9F4EAC09@akamai.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/X5edpoFgtyqX6o4FdcFIKWh9uSY>
Subject: Re: [Uta] Second WGLC for draft-ietf-uta-rfc7525bis-05
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Feb 2022 16:30:28 -0000

In fact if you look up the relevant IANA page [1], it refers to Sec. 17 of RFC 8447, which in turn lists the email address that Rich mentions at iana.org.

Arguably email addresses are not stable enough for inclusion in RFCs but in this particular case, it is right there where it needs to be.

Thanks,
	Yaron

[1] https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids


From: "Salz, Rich" <rsalz@akamai.com>
Date: Monday, February 14, 2022 at 17:47
To: "Olle E. Johansson" <oej@edvina.net>, Valery Smyslov <valery@smyslov.net>
Cc: "uta@ietf.org" <uta@ietf.org>, Leif Johansson <leifj@mnt.se>, "draft-ietf-uta-rfc7525bis@ietf.org" <draft-ietf-uta-rfc7525bis@ietf.org>, "uta-chairs@ietf.org" <uta-chairs@ietf.org>
Subject: Re: [Uta] Second WGLC for draft-ietf-uta-rfc7525bis-05
Resent-From: <alias-bounces@ietf.org>
Resent-To: <thomas.fossati@arm.com>, <yaronf.ietf@gmail.com>, <stpeter@mozilla.com>
Resent-Date: Mon, 14 Feb 2022 07:47:00 -0800 (PST)

➢ I’ve tried to register ALPN for SIP/2.0 for a long time now, but fail to get responses and confusing ones.

I don’t recall seeing the request, and I am one of the designated experts for the TLS registries.  I wonder where you asked?  mailto:Tls-reg-review@iana.org is the place to write to.  That address doesn’t seem to be written down anywhere well-known.

➢ It seems unclear whether we need to write new RFCs for SIP in order to get a registration, but that seems wrong to me.

The requirement is that somewhere there be a stable document.  Since they don’t expire, an internet-draft is sufficient.  More likely, if the SIP documents talk about TLS, and ideally mention ALPN, that’s enough, just mention whatever docs in your email.
➢ It must be much easier to get this done. 

Sorry for your frustration.  Perhaps the current draft could add a sentence giving the email address?

v2.23.0 | Report a Bug | By Email