RFC 8373: Negotiating Human Language in Real-Time Communications
In plain English — editorial summary, not part of the RFC
Users have various human (i.e., natural) language needs, abilities, and preferences regarding spoken, written, and signed languages. This document defines new Session Description Protocol (SDP) media- level attributes so that when establishing interactive communication sessions ("calls"), it is possible to negotiate (i.e., communicate and match) the caller's language and media needs with the capabilities of the called party. This is especially important for emergency calls, because it allows for a call to be handled by a call taker capable of communicating with the user or for a translator or relay operator to be bridged into the call during setup. However, this also applies to non-emergency calls (for example, calls to a company call center). This document describes the need as well as a solution that uses new SDP media attributes.
Document record
- Document ID
- RFC8373
- Published
- May 2018
- Authors
- R. Gellens
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- Also known as
- —
- Updated by:
- RFC 8865
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8840A Session Initiation Protocol (SIP) Usage for Incremental Provisioning of Candidates for the Interactive Connectivity Establishment (Trickle ICE)Updated
January 2021
- RFC 8850Controlling Multiple Streams for Telepresence (CLUE) Protocol Data ChannelCurrent
January 2021
- RFC 7345UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)Updated
August 2014
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 6337Session Initiation Protocol (SIP) Usage of the Offer/Answer ModelCurrent
August 2011
- RFC 3485The Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)Updated
March 2003
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 2003
- RFC 2848The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call ServicesCurrent
June 2000
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?