1 / 9

draft-koivusalo-sip-outbound-discovery

draft-koivusalo-sip-outbound-discovery. Miguel Garcia on behalf of Erkki Koivusalo erkki.koivusalo@nokia.com SIP WG @ IETF#66 Montreal. draft-koivusalo-sip-outbound-discovery. Scope of the document (version -02) Define the problems for SIP Outbound autodiscovery

rhoda-villarreal
Download Presentation

draft-koivusalo-sip-outbound-discovery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-koivusalo-sip-outbound-discovery Miguel Garcia on behalf of Erkki Koivusaloerkki.koivusalo@nokia.comSIP WG @ IETF#66 Montreal

  2. draft-koivusalo-sip-outbound-discovery • Scope of the document (version -02) • Define the problems for SIP Outbound autodiscovery • Which proxies in the domain support SIP Outbound ? • Should the UA set up a single or multiple flows ? • Which proxy in the domain should the UA use for its primary flow and which one for its secondary flow ? • Define requirements for the solution • Evaluate solutions and choose one of them • Specify the UA mechanisms • All that in one single document since the problem space is small enough

  3. Which proxies support Outbound ? • Agreed mechanism • New DNS NAPTR RR “SIP-O” service types • Benefits: • satisfies all requirements • uses a well specified mechanism (RFC 2915) • Cost: five more NAPTR service types

  4. Known Open Issues • Synchronize the draft with Outbound I-D • Will the next version of Outbound I-D have support for requirement REQ-PROXY-FARM-03 ? • “Must support the domain to have a separate farm of idle proxies dedicated for secondary backup connections” • Is the number of flows to be set up in scope of this draft or outbound draft ? • Proposed that the DNS server would be able to indicate the preferred number of flows for the domain: the question is how ?

  5. Which proxies should UA connect ? DNSSRV RRPriority 0 Proxy1 Weight=3 Proxy3 Weight=1 Proxy2 Weight=2 Primaryflow Secondaryflow UA UA finds two separate proxies by applying DNS SRV query after “SIP-O” NAPTR query

  6. 1:N redundancy with q-value ? SRV RRPriority 0 1 Proxy1 Weight=3 Proxy3 Weight=1 Proxy2 Weight=2 Proxy4 Weight=1 Primaryflow; q=0.9 Secondarybackup flow; q=0.1 UA UA uses primary flow whenever it works (the UA just keeps backup flow alive)Highest Contact ‘q’ value is assigned for the primary flow

  7. Or treat all flows always equally ? SRV RRPriority 0 1 Proxy1 Weight=3 Proxy3 Weight=1 Proxy2 Weight=2 Proxy4 Weight=1 Primaryflow Secondaryflow UA UA just ignores the SRV RRs which do not have the lowest number as SRV RR Priority (as far as there are multiple proxies within the topmost priority level)

  8. Proposals • The I-D to be adopted as WG item

  9. Thank you

More Related