60 likes | 71 Views
This draft addresses the lack of clarity in how a UA determines Route header set and handling of 305 responses in network communication. Sources of Route are explored, like Record-Route and DHCP. Specific points of confusion and the goal of the draft are discussed, aiming to define explicit algorithms for Route construction. If you're interested in this work, explore the nuances of Route header usage.
E N D
Route Construction Jonathan Rosenberg Cisco Systems
Problem Definition • Lack of clarity on how a UA determines Route header set for a request • Lack of definition on handling of 305 response
Sources of Route • Record-Route • Configured outbound proxies • DHCP • 3gpp air interface • Config framework • 305 response • Email discussion on usage in populating Route header, not Contact • Service-Route
Specific Points of Confusion • Do I include Route header field in my REGISTER? • Generally, what methods? • Does service-route override default outbound proxy?
Goal of Draft • Define an explicit algorithm for construction of Route at UA for each request, clearly defining how each route source relates • Define an explicit algorithm for construction of service route at proxy, with specific points of variation
Question • Interest in this work?