Re: [6tisch] [Ace] Optimizing EAP-over-CoAP payload

Dear Alexander:

Thanks for your comments 

> El 8 oct 2015, a las 10:53, Alexander Pelov <a@ackl.io> escribió:
> 
> Dear Rafa,
> 
> I've been reading the latest version of your draft ( draft-marin-ace-wg-coap-eap-01.txt ), and I have a couple of questions regarding some of the payload options, which could be optimized even further:
> 
> 1) Use shorter name for the /auth resource
> 2) Mandate the use of zero-length CoAP token
> 
> The first, and the more simple one, is - would it be possible to change the name of the authentication resource from /auth to a shorter one (like /a)? Maybe it could be an option to change the name of this resource, based on the underlaying architecture, e.g. an RFC could mandate that in a specific network the resource could be named /a, whereas the default value could remain /auth?

[Rafa] I do not see any problem to shorten the resource name.

> 
> The second, which is a little bit more subtle. Tokens are used to match responses to requests, but during the authentication/authorization phase a single peer (endpoint) would communicate with a single authenticator. Moreover, the communication happens in a serial fashion, and responses are piggybacked. This falls in the case when zero-length token is also advised by RFC7252. Do you think that it would be appropriate to make the use of zero-length token mandatory for EAP-over-CoAP?

[Rafa] I guess you are referring to this text:  

"An empty token value is appropriate e.g., when
   no other tokens are in use to a destination, "or when requests are
   made serially per destination and receive piggybacked responses.”

I would say that using zero-length token is possible. What I am not sure is whether make it mandatory or not. I mean we could say that if the client sends a zero-length token the server can consider it OK as per the text above. If there is a non-zero length token value should be also fine.

What do you think?

Best Regards.

> 
> Best,
> Alexander
> 
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace

-------------------------------------------------------
Rafael Marin Lopez, PhD
Dept. Information and Communications Engineering (DIIC)
Faculty of Computer Science-University of Murcia
30100 Murcia - Spain
Telf: +34868888501 Fax: +34868884151 e-mail: rafa@um.es
-------------------------------------------------------