1 / 9

IETF 72 Dublin Ireland SIPPING WG meeting July 28, 2008

IETF 72 Dublin Ireland SIPPING WG meeting July 28, 2008. draft-schwartz-sipping-nsr-code-00.txt. What am I trying to solve?. URIs containing e.164 numbers different than regular (non e.164) URIs in that the domain ( hostport ) context may not bind the userinfo

brielle-macdonald
Download Presentation

IETF 72 Dublin Ireland SIPPING WG meeting July 28, 2008

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. IETF 72 Dublin IrelandSIPPING WG meetingJuly 28, 2008 draft-schwartz-sipping-nsr-code-00.txt

  2. What am I trying to solve? • URIs containing e.164 numbers different than regular (non e.164) URIs in that the domain (hostport) context may not bind the userinfo • Current “Not-Found” failure handling assumes strong tie between domain context and userinfo • Need to define a response code to address the cases when no such linkage exists xxx - I don’t know - PLEASE TRY ELSEWHERE

  3. SIP “Not Found” Response Codes - do we really need any more? • Definitive (“I know”) • 410 - Gone - used to be here - no longer - go away • Try elsewhere • Implies knowledge that the number is valid • 604 - no such user anywhere • Don’t bother trying anywhere else • Is this appropriate for URIs containing e.164 numbers? • Are these two really the same vis-à-vis “example.com”? • sip:alice@example.com • sip:+12121234567@example.com;user=phone

  4. SIP “Not Found” Response Codes - do we really need any more? • Inconclusive (“I think I know”) • 404 - Not Found • The server has definitive information that the user does not exist (right now?) at the domain (is this relevant for e.164 userinfo?) specified in the RURI • Can this be used by automata? • Not found right now? Ever? • Valid user? Offline? 480 look-alike? • Do I try elsewhere?

  5. Use Cases • LNP CDB wrapping • I only have access to one country's (or less) data • Non A-Z PSTN GW • I only cover Spain and this is a UK #

  6. UAS Constraints • No knowledge if such a resource is even valid • Rules out 410 • No relevance to domain/realm specified in request URI • Rules out 604/404 • Cannot assume any fault for failure • Rules out 5xx • MUST enable automated failover to other routing options • Rules out 404

  7. Going Forward • Additional clarification needed? • Can we proceed?

  8. SIP Failure Response Codes - do we really need any more? • NO SIGNALING ERROR • Feel free to immediately try again - 408, 487 • Wait before retrying - 413, 480, 486, 600, 603 • FIX BEFORE RESENDING • Something is wrong or malformed • 400, 406, 414, 415, 416, 417, 420, 421, 422, 423, • 436, 438, 481, 482, 483, 484, 485, 488, 489, 493, 606 • Something is missing • 401, 407, 428, 429, 433, 437, 470 • DO NOT RESEND THIS REQUEST • 402, 403, 405, 501 • Network - (TRY SOMEWHERE ELSE OR WAIT AND RETRY) • 5xx

More Related