Thoughts on how gruu, outbound, etc. should have been documented
Dean Willis <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
In retrospect, our world might be tidier had we used a document structure something like this: 1) Instance identification for SIP user agents, and the use of instance identification in SIP registration. 2) Global aliasing for user-agent-instance/AOR tuples (making/using a GRUU for an instance) 3) Keepalive for SIP message sequences. 4) Persistence and reuse of registration flows (core Outbound). 5) Enhanced availability architecture using the preceding design elements. -- Dean _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip