Behcet Sarikaya <[email protected]> wrote: > On Wed, Jul 2, 2025 at 9:38 AM Michael Richardson > <[email protected]> wrote:
>>
>> 1. We reference RFC3261 when we first say reference SIP. I don't
>> think we need more reference than that.
>>
>>
> Really?
> I think the best resolution is this Michael: SIP [RFC3261] Phones.
Please read the document.
Paragraph five says:
For instance, a SIP [RFC3261] phone might have a client certificate to be
used with a SIP proxy.
It's been there for at least a few versions before -15 too.
Probably longer, but 2025-02-28 was the last time that line was touched.
>> 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.
> Yes, please put the above text in some form into the draft. No PR.
No, I'm not going to guess where you think more text belongs. Be specific.
The document already says all of this. If you have specific places you
think the text needs to be tweaked, then tell me. Given the above, I'm not
guessing here.
--
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]
