60 likes | 69 Views
This proposal by Jonathan Rosenberg from Cisco Systems aims to add cookies to URIs for seamless routing. By including cookies in the URI, routing can be improved, maintaining original information during requests. The mechanism is explained using INV and REFER methods, along with a proposed REGISTER approach to achieve efficient routing without rewriting the Request-URI.
E N D
UA Loose Routing Jonathan Rosenberg Cisco Systems
UA wants to add a cookie to its URI AOR or GRUU Hand out that URI with the cookie When it is dereferenced, incoming request conveys cookie Problem Statement INV 200 K:gruu+cookie REFER Gruu+cookie
Basic Idea: home proxy doesn’t rewrite Request-URI, instead pushes Route with registered contact Preserves the original URI and any parameters Proposed Mechanism REGISTER To: sip:joe@example.com K: sip:1.2.3.4 INV sip:joe@example.com; Cookie=asdasd INV sip:joe@example.com; Cookie=asdasd Route: sip:1.2.3.4 UAS proxy
Determining the Alias by which a UA is reached P-Called-Party-ID Limited Use Addresses Sub-Addressing Service Interaction RFC 3087, IVR SIP, Voicemail URI Emergency Services Marking Freephone numbers Additional Problems Solved
Issues • Backwards compatibility • Draft proposes Supported/Require in REGISTER • Should work fine, but what about proxies? • Redirection • Need to differentiate three cases • Recurse by R-URI modification • Recurse by replacing top Route • Recurse by appending top Route • Propose Via param to indicate capability and ;lr flag to differentiate cases • Other routing services?
Questions • Adopt as WG item?