RTT in IETF standards
IETF accessibility specific documents
| Standard | Full Name of Standard | Explanation | Type | Status |
|---|---|---|---|---|
| IETF RFC 4102 | Registration of text/red |
MIME registration of text with redundancy. References RFC4103. |
MIME registration | Approved |
| IETF RFC 4103 | RTP Payload for Text Conversation. | RTP Payload for T.140 text conversation. MIME Registered as "text/t140", used in H.323 and SIP and 3GPP | Transport |
Approved replaces RFC 2793 |
| IETF RFC 5194 | Framework of requirements for real-time text conversation using SIP |
Requirements and implementation guidelines for real-time text in the SIP environment. References RFC4103. |
Requirements |
Approved
june 2008 |
| IETF RFC 3351 | User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired Individuals | Handles transcoding and other value added services invoked through SIP. | Requirements | Approved |
| IETF RFC 4351 | RTP Payload for Text Conversation interleaved in an audio stream |
RTP Payload for text, intended for transit gateways where number of ports may be an issue. (historic RFC)
References RFC4103 normatively. |
Transport | Approved. |
| draft-hellstrom-textpreview | Presentation of Text Conversation in realtime and en-bloc form | Presentation of real-time text conversations | Presentation procedures | Draft |
| draft-hellstrom-textgwy | Real-time text interworking between PSTN and IP networks | Interworking procedures between PSTN textphones and SIP with real-time text | Call control and media handling | Draft (to be updated) |
| draft-hellstrom-text-turntaking | Registration of the Real-time-text Media Feature Tag | Registration of a capability for real-time text. | SIP Session level capability | Draft (to be updated) |
| draft-hellstrom-text-conference | Text media handling in RTP based real-time and message conferences | Procedures for multi-party sessions with RTP based real-time text | RTP session details | Draft |
IETF General documents of specific interest for accessibility
| Specification | Title | Explanation | Type | Status |
|---|---|---|---|---|
| IETF RFC 2833 | RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals | Encoding and transport of tones over IP | Transport |
Approved,
obsoleted by RFC 4733 |
| IETF RFC 4566 | Session Description Protocol | Contains "text" as an allowable media type in multimedia calls. | Call control | Approved |
| IETF RFC 2198 | Redundancy for RTP payloads | Used in RFC4103 for reliability of text traffic | Transport | Approved |
| IETF RFC 2805 | Media Gateway Control Protocol Architecture and Requirements | Contains text gateway requirements | Procedure requirements | Approved |
| IETF RFC 3840 | Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) | Can be useful for preference and capability indication for service invocation | Call control | Approved |
| IETF RFC 3841 | Caller Preferences for the Session Initiation Protocol | Can be useful for preference and capability indication for service invocation | Call control | Approved |
| IETF RFC 4733 | Definition of events for telephony tones | References RFC4103. | Transport | Approved, obsoletes RFC 2833 |
| IETF RFC 4734 | Definition of Events For Modem, FAX, and Text Telephony Signals |
Text telephone signals expanded.
References RFC4103. |
Transport | Approved |
| IETF RFC 4504 | SIP Telephony Device Requirements and Configuration |
Text requirements included.
References RFC4103. |
Device requirements | Approved |
| IETF RFC 4117 | Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc) | Most examples valid for text relay service and text gateway invocation | Call Control procedures | Approved |
| IETF RFC 4597 | Conference scenarios |
Real-time text included.
References RFC4103. |
Service description | Approved |
| IETF RFC 5370 | The session Initiation Protocol Conference bridge transcoding model | This RFC describes call connection methods that may be of interest for connecting a relay service or a gateway service to a call. | Procedure specification | Approved |
| IETF RFC 5012 | Requirements for Emergency Context Resolution with Internet Technologies |
Requirements for emergency services in IP, including real time text.
References RFC4104. |
Service requirements | Approved |
| IETF RFC 6881 | Best Current Practices for Communications Services in support of Emergency Calling |
Refers to real-time text for emergency calls.
References RFC 4103 |
Service and terminal requirements | Approved RFC |
| IETF RFC 6443 | Framework for Emergency Calling in Internet Multimedia |
Structure for emergency services in IP.
References RFC4103 normatively. |
Service requirements | Approved RFC |
| IETF RFC 6263 | Application Mechanism for maintaining alive the Network Address Translator (NAT) mappings associated to RTP flows. |
Methods for keep-alive through NAT-router References RFC 4103 |
Transport mechanism | Approved RFC |