RFC 3351: User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals
In plain English — editorial summary, not part of the RFC
This document aims to present a set of SIP user requirements that support communications for deaf, hard of hearing and speech-impaired individuals. These user requirements address the current difficulties of deaf, hard of hearing and speech-impaired individuals in using communications facilities, while acknowledging the multi-functional potential of SIP-based communications. A number of issues related to these user requirements are further raised in this document. Also included are some real world scenarios and some technical requirements to show the robustness of these requirements on a concept-level.
Document record
- Document ID
- RFC3351
- Published
- August 2002
- Authors
- N. Charlton; M. Gasson; G. Gybels; M. Spanner; A. van Wijk
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 5370The Session Initiation Protocol (SIP) Conference Bridge Transcoding ModelCurrent
October 2008
- RFC 3361Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session Initiation Protocol (SIP) ServersCurrent
August 2002
- RFC 3332Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)Obsoleted
September 2002
- RFC 3331Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation LayerCurrent
September 2002
- RFC 3372Session Initiation Protocol for Telephones (SIP-T): Context and ArchitecturesCurrent
September 2002
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 2003
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?