Re: Request for review

Mark Nottingham <mnot@mnot.net> Wed, 04 August 2021 00:52 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: wellknown-uri-review@ietfa.amsl.com
Delivered-To: wellknown-uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296F63A397F for <wellknown-uri-review@ietfa.amsl.com>; Tue, 3 Aug 2021 17:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=afC/nDTg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ap0BkmlE
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 Z_yNnHIVBxZK for <wellknown-uri-review@ietfa.amsl.com>; Tue, 3 Aug 2021 17:51:57 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D80A3A3982 for <wellknown-uri-review@ietf.org>; Tue, 3 Aug 2021 17:51:57 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id DB9593200973; Tue, 3 Aug 2021 20:51:55 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 03 Aug 2021 20:51:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm3; bh=r 63Bky6FrDGc5u4BfGW7SzSUdbpJ5RG8C4yVKQjL2wU=; b=afC/nDTg9HkkUQuf0 BJ4I+zFvgB/jMRGf3NliAU2sMg4jRMtuKr/jMI1/k7L8D7Hcm1yUvUme9TXQwGEe thBVLFtLQUcwkFsCTudNFBBOGNj9QXUdfoP8tyR24o4MKhHESvCK8VXmKtgqdzt5 HKs+gdfat2abhvJDkqpCsAoSaCOoSAIyE+QI9fqxkJOzBvcSGQE86OdeUcK30WHK J5ZQBQtXBK+J4RTDuqoKO+k+VtgP0U4r/dv24Vtsd+2Cyv0lxSRuLKd8fNZnYdXy r88p3swiT71N5NgA0xNzkFCYqXgIHRk+O/0JAaK/y8CI0NQoNqhnY2S1dgt4J4+n +RXeg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=r63Bky6FrDGc5u4BfGW7SzSUdbpJ5RG8C4yVKQjL2 wU=; b=ap0BkmlETzNlE8wRhON1fZUp36yTIq+Wl8g8Di36C1nw3CyTHlB8ukCte BGUAKXDZzesaTxi1zbp7rlx1jQIFezESwnWfF7OpT/vEwmlvBwZmpjCH/QKBYcu3 waz7EyvYw2XdU9xCIKbpWFd9Q6DHX46KO90RMEefhX1CYBh2XEpo5hmX/awIgO96 EYIVNOXv74E867bt1rC8oViMJRo/+lwhC0kQh1772Xu+zWlBz/i8+SSb9TBsAN6I 2VazVOq833GKWc0cCHQxULOu0jKd1NT50Qfztf6mhYLQb/jD8IJFBG1Yjp51V+v3 dTetKZjv/858rKyDFRMoP3FtUGUSg==
X-ME-Sender: <xms:quQJYQs95rFfaTg0GZULxSmh26WephrxRxEt2UMYOp6wm5uf1VoqfA> <xme:quQJYdf7-bGaJK5bpU5amXZ9PqAEa2qk2OiGZ8CaKZ3huMtGXZjpO3RXC_4M3bZsK xn0GY8a9PBz2KijmQ>
X-ME-Received: <xmr:quQJYby8R_OnJ_CmW2xHxk5vTwcyJY_gKKEqbKDK0uWePfXunSlYGnWb23mWqzrMXgD1cCI1oM4TcLgPSMNzrvaQ9KMCn3KWH5OlSlUSDcCxzqTFj0YT7fGQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrieehgdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcu pfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeduvdeljeegtefhveekhfdtveekleevkeefgeeludeihfdugedvieeuffdttdfh necuffhomhgrihhnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgv th
X-ME-Proxy: <xmx:quQJYTOwT1O6Nu3z6Y6MEtSFPIVGN0T6pBIs36Km1avGwVXhepQZPA> <xmx:quQJYQ-cg_Y0Sw4jsJJB4BeOEIBkHVKWcgZCTn-teEt8VdAViEjkog> <xmx:quQJYbWI-ZQCF13d_sNnAOWdzaAIaj3ZPTRYcp6ge0yz0Izx1jK_Ag> <xmx:q-QJYUZPNhssfcHsbsaltrQVy-rwnc4OZ54ia3eNbzdlZfkOfVTVgw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 3 Aug 2021 20:51:53 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Subject: Re: Request for review
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <267a860e-d5c8-66ac-f1b3-e29d7ca11de5@uniovi.es>
Date: Wed, 04 Aug 2021 10:51:49 +1000
Cc: wellknown-uri-review@ietf.org, Rafa Marin-Lopez <rafa@um.es>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7673C783-3010-40D9-8D17-6DB7DE8E5BD2@mnot.net>
References: <267a860e-d5c8-66ac-f1b3-e29d7ca11de5@uniovi.es>
To: Dan Garcia Carrillo <garciadan@uniovi.es>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wellknown-uri-review/qGNYYWbV1iliVB8X94tU9D4xl5Y>
X-BeenThere: wellknown-uri-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Well-Known URI review list <wellknown-uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wellknown-uri-review/>
List-Post: <mailto:wellknown-uri-review@ietf.org>
List-Help: <mailto:wellknown-uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wellknown-uri-review>, <mailto:wellknown-uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Aug 2021 00:52:02 -0000

Hi Dan,

Since this mechanism appears to be COAP-specific, would 'coap-eap' be workable?

Cheers,


> On 3 Aug 2021, at 9:45 pm, Dan Garcia Carrillo <garciadan@uniovi.es> wrote:
> 
> Dear wellknown-uri experts,
> 
> I'd like to request a review of registration request for the URI .well-known/eap, which after the last IETF meeting of the ACE working group seems to be the best fit for the work found in  -- https://datatracker.ietf.org/doc/draft-ietf-ace-wg-coap-eap
> 
> Summary: CoAP-EAP defines an EAP lower layer for CoAP, as a CoAP service. This entails communication between to CoAP endpoints to perform an EAP exchange to authenticate both CoAP endpoints so the newcommer can join the security domain and do so securely.
> 
> Thank you for your consideration.
> Best Regards,
> 
> Dan.
> 
> _______________________________________________
> wellknown-uri-review mailing list
> wellknown-uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/wellknown-uri-review

--
Mark Nottingham   https://www.mnot.net/