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

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