1. SIP INFO Cast of Thousands Fall Guy: Eric Burger 29 July 20081SIP INFO - IETF 72 Dublin Ireland

2. What is Your View of INFO? 29 July 2008SIP INFO - IETF 72 Dublin Ireland2

3. What is Your View of INFO? 29 July 2008SIP INFO - IETF 72 Dublin Ireland3 Photobucket duduwalkerPhotobucket kiyokouchiha A Zombie that will not go away? An Angel you cannot live without?

4. Drafts draft-kaplan-sip-info-events draft-kaplan-sip-info-use-cases draft-rosenberg-sip-info-litmus draft-rosenberg-sip-tote draft-burger-sip-info draft-burger-sip-user 29 July 20084SIP INFO - IETF 72 Dublin Ireland

5. Issues Is there a problem at all? – We all see the potential for trouble – Do we see trouble in the wild? – Is there trouble other than for DTMF? Assuming there is a problem... What should we do? 29 July 20085SIP INFO - IETF 72 Dublin Ireland

6. User-User Information Exchange Clearly a need for UUI related to the SIP dialog – Done way too much in the wild to ignore – Just saying “no” does not work Issue 1: Do we need some UUI mechanism related to the SIP dialog? 29 July 20086SIP INFO - IETF 72 Dublin Ireland

7. INFO in the Wild Registry / Catalog of extant INFO usage – Capture what is out there – Analyze trends – Avoid collisions – Already done in reality (draft-burger-sip-info, draft- kaplan-sip-info-use-cases) Issue 2: Worth spending more effort on cataloging extant INFO usage? Issue 3: If so, worth establishing IANA registry, document in an Informational RFC, other? 29 July 20087SIP INFO - IETF 72 Dublin Ireland

8. INFO as a Method Any “repair” of INFO will NOT be backwards compatible Issue 4: do we care? – Just ignore old usages? – Means “Good INFO” UAS will, by design, barf on “Bad INFO” usage – Since “Good INFO” UAS will be new, and they probably want to interoperate with old, will not barf on “Bad INFO.” ∴ “Bad INFO” with us forever and cast in stone; might as well give up and stick with “Bad INFO” 29 July 20088SIP INFO - IETF 72 Dublin Ireland

9. New Mechanisms Lots of options New INFO that looks like SUBSCRIBE New method that – Is negotiable – Is unambiguous – Carries arbitrary payloads Issue 5: Do we need a new mechanism? 29 July 20089SIP INFO - IETF 72 Dublin Ireland

10. Issue 6: Pick a Mechanism #1: Method, or mechanism to open pipe, a’la speechsc, mediactrl, tote? #2: Option tags and Requre? #3: Something else? 29 July 200810SIP INFO - IETF 72 Dublin Ireland

11. Anything Else? 29 July 2008SIP INFO - IETF 72 Dublin Ireland11