Skip to main content

Negotiating Human Language in Real-Time Communications
RFC 8373

Revision differences

Document history

Date By Action
2020-01-21
(System) Received changes through RFC Editor sync (added Verified Errata tag)
2018-12-19
(System)
Received changes through RFC Editor sync (changed abstract to 'Users have various human (i.e., natural) language needs, abilities, and preferences regarding spoken, written, and signed …
Received changes through RFC Editor sync (changed abstract to '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.')
2018-05-31
(System) Received changes through RFC Editor sync (added Errata tag)
2018-05-24
(System)
Received changes through RFC Editor sync (created alias RFC 8373, changed abstract to 'Users have various human (i.e., natural) language needs, abilities, and preferences …
Received changes through RFC Editor sync (created alias RFC 8373, changed abstract to '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).', changed pages to 13, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-05-24, changed IESG state to RFC Published)
2018-05-24
(System) RFC published