1. We reference RFC3261 when we first say reference SIP. I don't think we need more reference than that.
2. SIP Phones, printers, and Internet Routers are examples of devices that fit into the categoey of IoT devices. They have limited or no user interface, they have limited (control plane/user) processing power, limited memory, and are not desktops. Yes, SIP phones often have screens and buttons, but not that you'd want an end user to toggle in a base64 PEM encoded certificate into. BRSKI-CLOUD addresses application onboarding more than networking onboarding, so the match to wired SIP phones is much better than for other large appliances that might be Wi-Fi, and need network onboarding (as well). One could use another onboarding protocol (DPP, EAP-NOOB, EAP-TEEP, the not-yet-defined BRSKI-TEEP...) to get on the network, and then use BRSKI-CLOUD to connect to do application onboarding. This is what some Thread ecosystems do, with work going back to 2018, for instance. If you have some specific text you want to suggest, please send PR. -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list -- [email protected] To unsubscribe send an email to [email protected]
