Hi, after reading the RFC 5627 I don't understand why the registrar can create a new temp-gruu URI for each registration refresh. If it does so, the registrar would end with a database full of temp-gruu URI's.
From the point of view of a registrar implementing GRUU, is it posible to mantain an unique temp-gruu for each registration instance (as it occurs for the public-gruu? It would make the implementation easier (by adding two columns "temp_gruu" and "public_gruu" in the location database table). Do I miss something? Also, the example in section 9 of RFC 5627 shows the same temp-gruu for two different registration from same UA instance (as it crashed and generates a new registration with different Call-ID after rebooting). Thanks for any explanation. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
