> 802.15.4 then it will be fairly widely used in the IoT sector. I am sure the
> authors of the Thread specifications (and the members of the Thread
> consortium) expect their stuff to be widely used (in IoT -- not on the Web).
They can get a code-point but not a Y since there is no IETF consensus/WG
agreement.
Is this a problem? How and why? Will a non-approval from IETF really hamper
the acceptance and deployment since it's already on-track to be widely used? I
can't see why that would be true.
The only possible practical impact I can see is that someone like OpenSSL might
not provide it. But a Y doesn't guarantee we will, either.
/r$
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
