1. draft-ietf-sipping-toip-01.txt draft-ietf-sipping-toip-01 Title: Framework of requirements for real-time text conversation using SIP Authors –Willem Dijkstra –Barry Dingle –Guido Gybels –Gunnar Hellstrom –Henry Sinnreich –Gregg C Vanderheiden –Arnoud van Wijk

2. draft-ietf-sipping-toip-01.txt Reasons for doing this Explain how to support text over IP using standard SIP and RTP Stimulate deployment of ToIP in VoIP networks Stimulate use of one real time text protocol for SIP telephony: RFC4103 –Avoid PSTN text telephone incompatibility nightmare: V.21, EDT, Baudot, DTMF, Minitel, Bell 103, etc

3. draft-ietf-sipping-toip-01.txt Changes since last draft Clarified scope –Define a framework for the implementation of ToIP, stand- alone or as part of a total conversation –Description of ToIP using SIP and RTP; –Requirements of Real-time, interactive text; –Requirements for ToIP interworking with gateways (e.g. PSTN ) Stressed that ToIP is similar to VoIP for SIP Call flows moved to planned separate draft Clarified requirements –removed most overlaps –access to emergency services similar to VoIP

4. draft-ietf-sipping-toip-01.txt Next steps Submit –02 in 2 weeks –Number requirements, remove last overlaps –Incorporate feedback from sipping group and authors –WGLC Start call flows draft

5. draft-ietf-sipping-toip-01.txt Questions? Hosted by Mike Spanner & Willem Dijkstra

6. draft-ietf-sipping-toip-01.txt ToIP example Why do you need character by character transmission? Because then you get a live conversation suitable for a real time call.Yes, I see, I can read your thoughts at the moment you express them. No waiting. Good! User A User B ToIP is real-time character by character streaming text as described in RFC4103

7. draft-ietf-sipping-toip-01.txt Total Conversation