idnits 2.17.1 draft-ietf-sipping-deaf-req-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3351 5 Title: User Requirements for the Session Initiation 6 Protocol (SIP) in Support of Deaf, Hard of Hearing 7 and Speech-impaired Individuals 8 Author(s): N. Charlton, M. Gasson, G. Gybels, M. Spanner, 9 A. van Wijk 10 Status: Informational 11 Date: August 2002 12 Mailbox: nathan@millpark.com, 13 michael.gasson@korusolutions.com, 14 Guido.Gybels@rnid.org.uk, 15 mike.spanner@rnid.org.uk, 16 Arnoud.van.Wijk@eln.ericsson.se 17 Pages: 17 18 Characters: 33894 19 Updates/Obsoletes/SeeAlso: None 21 I-D Tag: draft-ietf-sipping-deaf-req-03.txt 23 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3351.txt 25 This document presents a set of Session Initiation Protocol 26 (SIP) user requirements that support communications for deaf, hard of 27 hearing and speech-impaired individuals. These user requirements 28 address the current difficulties of deaf, hard of hearing and 29 speech-impaired individuals in using communications facilities, while 30 acknowledging the multi-functional potential of SIP-based 31 communications. 33 A number of issues related to these user requirements are further 34 raised in this document. 36 Also included are some real world scenarios and some technical 37 requirements to show the robustness of these requirements on a 38 concept-level. 40 This document is a product of the Session Initiation Proposal 41 Investigation Working Group of the IETF. 43 This memo provides information for the Internet community. It does 44 not specify an Internet standard of any kind. Distribution of this 45 memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.