Status, Requirements and Proposal

1
SIP Routing Operations, Policy, and Request-URI
Discussion

• Status, Requirements and Proposal

Sean Olson Robert Sparks seancolson_at_yahoo.com
rsparks_at_dynamicsoft.com
2
Problem Statement

• How do we modify Route processing to allow for
  loose routing to a SIP element

3
Requirements

• Loose routing
• Allow flexible Request-URI rewriting policy
• Handle inbound and outbound proxies
• Handle visited and home proxies
• Allow for routes not strictly constructed with
  Record-Route (pre-loaded routes)
• Should be backwards compatible
• Should work for SIP ALG devices
• See also draft-bjorkner-sip-serviceroute-00 and
  draft-garcia-sipping-3gpp-reqs-02

4
Proposal

• Relax Route processing rules to allow loose
  routing in a backwards compatible way
• Request-URI rewriting and topmost Route removal
  become local policy decisions
• Route header value is removed when reached
• Request-URI and topmost route value will differ
  in some way

5
Proposal

• Solves Outbound/Inbound proxy issues
• Leaves Record-Route as is
• Discussion of meaning of port/transport in R/RR
  will be a separate thread.

6
GOAL

• Reach consensus by 12/28 (2 weeks)