user requirements for sip in support of deaf, hard of hearing and speech-impaired individuals
DESCRIPTION
User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals. Arnoud Van Wijk Ericsson Guido Gybels, Nathan Charlton The Royal National Institute for Deaf People. What has happened over the last three months?. draft-vanwijk-sipping-deaf-req-00.txt - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/1.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals
• Arnoud Van WijkEricsson
• Guido Gybels, Nathan CharltonThe Royal National Institute for Deaf People
![Page 2: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/2.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
What has happened over the last three months?
• draft-vanwijk-sipping-deaf-req-00.txt• 51st Meeting in London: decision to focus on the requirements• New draft with requirements only was submitted: draft-charlton-deaf-req-00.txt• SIPPING Charter: now includes under Nr 2, “Messaging-like applications under SIP”: support for hearing-, speech impaired calling• Milestone: Feb ’02: submission to IESG• Design team
![Page 3: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/3.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Motivation
• Ensure SIP-based applications will fully
support services for hearing/speech impaired
users
• Allow improved/new services where possible
We can’t degrade the existing situation
Avoid building solutions before req. are
defined
SIP already has the potential for
new/improved services
![Page 4: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/4.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#1
Now that it is on the charter, can we rename
the current draft to:
draft-sipping-deaf-req-00.txt
![Page 5: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/5.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2
Req. #5: “User Agents SHOULD be able to identify the content of a media stream in order to obtain such information as the cost of the media stream, if a transcoding service can support it, etc. User Agents SHOULD be able to choose among transcoding services and similar services based on their capabilities (e.g., whether a transcoding service carries a particular media stream), and any policy constraints they impose (e.g., charging for use). It SHOULD be possible for User Agents to discover the availability of alternative media streams and to choose from them.”
Some confusion about the meaningWe need ideas on how to do this!
![Page 6: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/6.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
Do we just define this requirement and leave it to the implementers to come up with a solution?
We suggest: NOWe have to define a model for doing this and incorporate that into the requirements.
![Page 7: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/7.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
What are the options?
a) SDP-based mechanism?
b) New SIP header?
c) Make assumptions based on the
nature/origin of the call?
d) Don’t define a solution, let the operators
take a decision?
![Page 8: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/8.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
Option a) Use SDP:
• Elegant solution• BUT: currently no fields available?• So: do we need to define a new field type?
![Page 9: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/9.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
Option b) New SIP header:
• Backwards compatible• Is SIP the right place to look for content?
![Page 10: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/10.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
Option c) Make assumptions based on the nature/origin of the call
• Can be implemented today• BUT: Low granularity, relevance• High maintenance
![Page 11: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/11.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
Option d) Let the operator make a decision
• How?• Currently possible by having human operators drop/accept the call: depends on human judgement• But: what about (semi) automated systems?• UGLY!
![Page 12: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/12.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#2 (Continued)
Any other options??
Suggestions, please!!
![Page 13: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/13.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
Open issues#3
Very little feedback from the mailing list:
Did we capture all the business-cases???
• Is this a robust set of requirements?
• Advocacy groups need to look at this
• We need further thinking/input from the WG:
testing the assumptions!
![Page 14: User Requirements for SIP in support of deaf, hard of hearing and speech-impaired individuals](https://reader035.vdocuments.us/reader035/viewer/2022072013/56812c5f550346895d90ed3e/html5/thumbnails/14.jpg)
December 2001 draft-charlton-deaf-req-00.txt IETF 52nd Meeting
What’s next?
• Let’s look at the open issues and come up
with answers;
• Updated draft somewhere end of January
2002
• Last call
• Submission to IESG as planned