[Slim] RFC 8373 on Negotiating Human Language in Real-Time Communications

rfc-editor@rfc-editor.org Thu, 24 May 2018 23:50 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: slim@ietfa.amsl.com
Delivered-To: slim@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BFA8812E8D7; Thu, 24 May 2018 16:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id irydWEixhsAi; Thu, 24 May 2018 16:50:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2ADC812D80F; Thu, 24 May 2018 16:50:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 715BCB828AE; Thu, 24 May 2018 16:50:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, slim@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180524235004.715BCB828AE@rfc-editor.org>
Date: Thu, 24 May 2018 16:50:04 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/Gh017lYXkIvRXQHlCep0iRJmOr8>
Subject: [Slim] =?utf-8?q?RFC_8373_on_Negotiating_Human_Language_in_Real-T?= =?utf-8?q?ime_Communications?=
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Selection of Language for Internet Media <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 23:50:20 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8373

        Title:      Negotiating Human Language in Real-Time 
        Author:     R. Gellens
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2018
        Mailbox:    rg+ietf@coretechnologyconsulting.com
        Pages:      13
        Characters: 27727
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-slim-negotiating-human-language-24.txt

        URL:        https://www.rfc-editor.org/info/rfc8373

        DOI:        10.17487/RFC8373

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.

This document is a product of the Selection of Language for Internet Media Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC