Re: [Ace] call for adoption for draft-marin-ace-wg-coap-eap

Daniel Migault <mglt.ietf@gmail.com> Fri, 19 February 2021 19:15 UTC

Return-Path: <mglt.ietf@gmail.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D78973A138F for <ace@ietfa.amsl.com>; Fri, 19 Feb 2021 11:15:45 -0800 (PST)
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=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 4btRmCFfm8Mt for <ace@ietfa.amsl.com>; Fri, 19 Feb 2021 11:15:44 -0800 (PST)
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 D028A3A1395 for <ace@ietf.org>; Fri, 19 Feb 2021 11:15:43 -0800 (PST)
Received: by mail-ua1-x92a.google.com with SMTP id a31so2181944uae.11 for <ace@ietf.org>; Fri, 19 Feb 2021 11:15:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yZ6ZJDuK27VCWdzVnF/4rFS9JLUTQRMzJldsua63220=; b=N+zuj0eNklMrUOx2cVNtsV4Sq2v34WTsWFmxWbnPfA7e01s8f1xJYDtit7eexwt4BS UPkI5ps+dli+Evllfb8x9tIeTluj+jyTMNcBog+IFGR3HiEonOxDEujKFuY99c5ytgLj KplRl8qmWghE9gMtO9ckgy59BoW0bVtcNvsu/csv1aQ8TTrP5a7DfI5UF1l4mtciGijb RWceIjN0beMb/Qsk8lYm84iuYxDOluqOMeAAIzEfgGtwADUPcPm5b7w/UTM9nV8MIyIH EqS7GRVMgjHVAvKNsIhCM78Cg9tBr8L1IZD+P4QN91Qk4V7n89u4vsJmqdQ7RmZv8QDh 1EAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yZ6ZJDuK27VCWdzVnF/4rFS9JLUTQRMzJldsua63220=; b=quq4gmpFUEuYpjfq4NREJEEY5JF372WnHz9obucZluvTif+cynjVIZ+fC6QxExBH2t IrWEtmQ/7HpZDZ/STd9itwayWlIRZva2GVi2eeFeR12xcsBGzTl42ZDuPhVxM4gCvh2D jxzXrGPPXPEu3xZrXFlOrWp9RToygXMtSD302Uv0CVzAXonBmZDbmBZODmP9Z/1+BhAb 5JYUrq+Zx7ZqdjUxx5C6yBshUHr23RtpzcRpTksAYD07zZ9OsYW89GEabArMD3hv+xZY SfXItqJ+wQO9+Ytsw5AfNL9XM69R8iHdq0gH66zV9NOiDB8nhQT8GCshVK691GBP0Rp6 WDxw==
X-Gm-Message-State: AOAM531CjYfDHPvF+LimFrM5FOCdWrmCQ8Rfqy5TGiu37yf7gZBCFgGk fqQCVCXEo7U1LHLDn3HUbf3PUcoPaRXvntCTGMY=
X-Google-Smtp-Source: ABdhPJwRocC7bwlgoVJ3j82Il8E25KUdF2Frbuq9yHiQNxCQnck6J8iw6BXEy9Ip27gUZYTTt1No1OjPLWk7w/5eQhE=
X-Received: by 2002:ab0:6614:: with SMTP id r20mr8891569uam.68.1613762141988; Fri, 19 Feb 2021 11:15:41 -0800 (PST)
MIME-Version: 1.0
References: <CADZyTkkiqC=x_oAYsc_jHHeiNWhjvXHHvOKEeF=9W3si8Dp3pw@mail.gmail.com> <4ced3414-dbff-0ca3-5345-7e524207d722@imt-atlantique.fr> <14711.1612646999@localhost> <CADZyTkkjj8CiH+frg6gYDXHYW4PM+dSMEuBvdb-WzYi2=W1tcA@mail.gmail.com>
In-Reply-To: <CADZyTkkjj8CiH+frg6gYDXHYW4PM+dSMEuBvdb-WzYi2=W1tcA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
Date: Fri, 19 Feb 2021 14:15:30 -0500
Message-ID: <CADZyTk=cdUSTQWszWv6aO_BOe2Ocg=2yjZikUQC_e65d8780zw@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: =?UTF-8?B?RWR1YXJkbyBJbmdsw6lzIChJTVQp?= <eduardo.ingles-sanchez@imt-atlantique.fr>, Ace Wg <ace@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000039aa8505bbb54780"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/cnR4Wt5p7wnO8Z2TUTyZqG1Zv5k>
Subject: Re: [Ace] call for adoption for draft-marin-ace-wg-coap-eap
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2021 19:15:46 -0000

The ACE charter has been approved. Please move the draft to WG document
that is rename it to draft-ietf-ace-wg-coap-eap and publish it.

Our current milestone is : Aug 2021 - Submission to the IESG of "EAP-based
Authentication Service for CoAP"

The document will be discussed during interim and IETF meetings. Note that
discussions are expected to happen on the mailing list, so please keep the
WG informed about the progress as well as concerns to be resolved.

Yours,
Logan and Daniel

On Tue, Feb 16, 2021 at 9:40 AM Daniel Migault <mglt.ietf@gmail.com> wrote:

> Hi,
>
> I would like to close the call for adoption. As far as I can see, 5 strong
> support for adoption in addition to the coauthors and one objection.
> The objection for the draft adoption was a lake of a use case or a
> description of a specific use case - that requires EAP over CoAP. On the
> other hand it has been acknowledged the draft is expected to ease
> interconnecting the CoAP and EAP (for lower layers) communities. I propose
> we consider the draft as adopted - once the charter will be approved with
> this item mentioned in the charter.
>
> When the adoption becomes official I will ask the co-author to publish an
> update of the document that addresses the comment received during the call
> for adoption as well as provide a careful analysis and description on the
> position of this work.
>
> Yours,
> Daniel
>
> On Sat, Feb 6, 2021 at 4:30 PM Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
>
>>
>> Eduardo Inglés (IMT) wrote:
>>     > Regarding the writing of the draft, I agree with Michael Richardson
>>     > that it can be improved to facilitate the understanding of some
>>     > concepts. For example, I would rewrite this sentence to understand
>> it
>>     > on a first reading: "EAP requests go always from the EAP
>> authenticator
>>     > and the EAP peer and the EAP responses from the EAP peer to the EAP
>>     > authenticator."  And perhaps it is convenient to clarify in the
>>     > abstract that this draft is a lower layer EAP to avoid confusion
>> with
>>     > the EAP methods. However, I do agree with the authors on the
>> usefulness
>>     > of the protocol.
>>
>> Could you please explain to me a use case?
>> Did you use an EAP method to key OSCORE?
>>
>> Did you do this without a TLS method within the EAP?
>> If you did use a TLS method within EAP, then did you compare:
>>
>> (1)  IP/UDP/CoAP/EAP/TLS
>> to:
>> (2)  IP/UDP/DTLS/CoAP
>>
>> What was your EAP peer to AAA server communication transported?
>> Was it EAP over RADIUS?  If so, how did you setup the RADIUS key?
>> Or did you use DTLS or TLS for the RADIUS?
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting
>> )
>>            Sandelman Software Works Inc, Ottawa and Worldwide
>>
>>
>>
>>
>> _______________________________________________
>> Ace mailing list
>> Ace@ietf.org
>> https://www.ietf.org/mailman/listinfo/ace
>>
>
>
> --
> Daniel Migault
> Ericsson
>


-- 
Daniel Migault
Ericsson