Skip to main content

Negotiating Human Language in Real-Time Communications

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Randall Gellens
Last updated 2015-11-01
Replaces draft-gellens-mmusic-negotiating-human-language, draft-gellens-negotiating-human-language
Replaced by draft-ietf-slim-negotiating-human-language, RFC 8373
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-slim-negotiating-human-language, draft-ietf-slim-negotiating-human-language
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Users have various human (natural) language needs, abilities, and preferences regarding spoken, written, and signed languages. When establishing interactive communication ("calls") there needs to be a way to negotiate (communicate and match) the caller's language and media needs with the capabilities of the called party. This is especially important with emergency calls, where a call can be handled by a call taker capable of communicating with the user, or a translator or relay operator can be bridged into the call during setup, but this applies to non-emergency calls as well (as an example, when calling a company call center). This document describes the need and a solution using new SDP stream attributes.


Randall Gellens

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)