Hi Carsten, I thought the discussion centered more around the transport stack for the "authentication method" and key management. Hence the discussion about using EAP/PANA, CoAP, etc.
Whether the auth method will be cert based, or PSK based, etc. is indeed very important. But whatever it is determined to be, there'd already be an existing EAP method, or one can define an alternative encapsulation/transport if using a non-EAP solution. I recommend we open another thread just to discuss the type of credentials and the associated auth method to be used. Once we converge on that, we can come back and discuss how to transport that. Alper On Nov 1, 2015, at 12:17 AM, Carsten Bormann wrote: > Alper, > > I have not read the thread, but I'm trying to understand your suggestion. > > PANA and EAP are only carriers for EAP methods. > So the real question is: Which EAP method is going to be used? > > If an existing method fits the bill, that would be interesting to know. > > If a new method has to be designed, I would like to understand what the > effect is of having to phrase that method in EAP terms (e.g., as opposed > to directly using that exchange e.g. via 6top). > > Grüße, Carsten > > _______________________________________________ > 6tisch mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6tisch _______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
