________________________________________
From: sip-implementors-boun...@lists.cs.columbia.edu
[sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Paul Kyzivat
[pkyzi...@cisco.com]
I thought this was discussed in the RFC. (But I'm too lazy to check
right now.)
_______________________________________________
Network Working Group J. Rosenberg
Request for Comments: 5627 Cisco Systems
Category: Standards Track October 2009
Obtaining and Using Globally Routable User Agent URIs (GRUUs)
in the Session Initiation Protocol (SIP)
[...]
Appendix A. Example GRUU Construction Algorithms
The mechanism for constructing a GRUU is not subject to
specification. This appendix provides an example that can be used by
a registrar to construct a public and a temporary GRUU. Of course,
others are permitted, as long as they meet the constraints defined
for a GRUU.
[...]
A.2. Temporary GRUU
This specification requires a registrar to create a new temporary
GRUU on each registration refresh. If a registration is very long
lived, this can quickly result in hundreds or even thousands of
temporary GRUUs being created and allocated to a UA. Consequently,
it is important to have an algorithm for constructing temporary GRUUs
that does not require additional storage that grows in size with the
number of temporary GRUUs. The following algorithm meets this goal.
Dale
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
