Re: [Emu] John Scudder's No Objection on draft-ietf-emu-tls-eap-types-11: (with COMMENT)
Alan DeKok <aland@freeradius.org> Tue, 14 February 2023 22:53 UTC
Return-Path: <aland@freeradius.org>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDABC1FB5E7; Tue, 14 Feb 2023 14:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 4tQgG_xZ8kis; Tue, 14 Feb 2023 14:53:30 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 495CFC14CF15; Tue, 14 Feb 2023 14:53:28 -0800 (PST)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id C660652D; Tue, 14 Feb 2023 22:53:25 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=fail (p=reject dis=none) header.from=freeradius.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Alan DeKok <aland@freeradius.org>
In-Reply-To: <E5A5EC55-07E4-4246-B72C-843B6DC9C0A9@juniper.net>
Date: Tue, 14 Feb 2023 17:53:24 -0500
Cc: The IESG <iesg@ietf.org>, "draft-ietf-emu-tls-eap-types@ietf.org" <draft-ietf-emu-tls-eap-types@ietf.org>, "emu-chairs@ietf.org" <emu-chairs@ietf.org>, EMU WG <emu@ietf.org>, "jsalowey@gmail.com" <jsalowey@gmail.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <93CD2A38-F2E3-4F11-A2B6-28225DAA0881@freeradius.org>
References: <167640985268.60504.14345761192561097879@ietfa.amsl.com> <B70BF937-1E48-4033-9AAE-7C8948DD8C1B@freeradius.org> <E5A5EC55-07E4-4246-B72C-843B6DC9C0A9@juniper.net>
To: John Scudder <jgs@juniper.net>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/-EX21h0ROh3CN5InDgcpV4_0vWc>
Subject: Re: [Emu] John Scudder's No Objection on draft-ietf-emu-tls-eap-types-11: (with COMMENT)
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2023 22:53:31 -0000
On Feb 14, 2023, at 5:51 PM, John Scudder <jgs@juniper.net> wrote: > The RFC 2119-style MAY seems a little out of place, it seems like it’s expressing an expectation rather than giving permission to an implementation that the inner protocol is allowed to do certain things (which seems beyond the scope of this spec to regulate?). Consider “may”, “might”, “could”, or similar? Sure. I'll just lowercase it.
- [Emu] John Scudder's No Objection on draft-ietf-e… John Scudder via Datatracker
- Re: [Emu] John Scudder's No Objection on draft-ie… Alan DeKok
- Re: [Emu] John Scudder's No Objection on draft-ie… John Scudder
- Re: [Emu] John Scudder's No Objection on draft-ie… Alan DeKok