Re: [MMUSIC] draft-gellens-mmusic-negotiating-human-language-01.txt - more use cases

Randall Gellens <> Thu, 18 July 2013 16:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 476F021E8128 for <>; Thu, 18 Jul 2013 09:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -105.87
X-Spam-Status: No, score=-105.87 tagged_above=-999 required=5 tests=[AWL=-0.729, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id smQTLCzkbldw for <>; Thu, 18 Jul 2013 09:25:22 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 61D1A11E819B for <>; Thu, 18 Jul 2013 09:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;;; q=dns/txt; s=qcdkim; t=1374164705; x=1405700705; h=message-id:in-reply-to:references:date:to:from:subject: mime-version:content-transfer-encoding; bh=jDToOhBe46Y+Za8vFPBDr4QzCtml9cDT6EWSLIMUq3I=; b=w6pXdAhHbkwewVGeH5YsMZIJ3X0LYVtRfMFw+xVgvCzZG78qo3XZo7pv oT5T3koICSaESbGIdptLEG3YR42TWUzg25+NTs5x+JF6PNUI6Y61OUlf/ XW1+pCtxczsPjvS93HokGgpn6UY2QC/+sJLeHOKityjXNmBxu4Q8K+x/W I=;
X-IronPort-AV: E=Sophos; i="4.89,694,1367996400"; d="scan'208,217"; a="63494352"
Received: from ([]) by with ESMTP; 18 Jul 2013 09:25:04 -0700
X-IronPort-AV: E=Sophos; i="4.89,694,1367996400"; d="scan'208,217"; a="481677102"
Received: from ([]) by with ESMTP/TLS/RC4-SHA; 18 Jul 2013 09:25:04 -0700
Received: from [] ( by ( with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 18 Jul 2013 09:25:03 -0700
Message-ID: <p06240604ce0dc6237036@[]>
In-Reply-To: <>
References: <> <> <> <> <> <> <p06240615cdfea836f364@[]> <> <p0624060ece02360a322d@[]> <> <> <p06240603ce06ba958db4@[]> <> <> <>
X-Mailer: Eudora for Mac OS X
Date: Thu, 18 Jul 2013 09:21:33 -0700
To: Gunnar Hellstrom <>,
From: Randall Gellens <>
MIME-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: []
Subject: Re: [MMUSIC] draft-gellens-mmusic-negotiating-human-language-01.txt - more use cases
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 18 Jul 2013 16:25:26 -0000

Re: [MMUSIC] draft-gellens-mmusic-negotiating-human-langua
Hi Gunnar,

I am concerned that getting into person-to-person usage will overly complicate the draft with no real-world benefit, since person-to-person communication has context and implied language/media, as stated in the draft.  The draft is trying to solve a more focused real-world problem where there is no context.

At 8:40 AM +0200 7/15/13, Gunnar Hellstrom wrote:

I suggest to add a couple of use cases.
4.x.  Deaf French sign language user calling another deaf French sign language user.

Someone who mainly uses French sign language (FSL) places a call. 
The call offers a video stream listing FSL in both directions with highest preference and also
real-time text stream on low preference level for French in both directions.
Audio is also included but without language indications.
The call destination turns out to be another user of FSL with the same media and language settings.
The called client can find that the language preferences match, so the same language indications are
sent in the SDP answer, and the call can be connected without connection of any relay service.
The users can sign directly with each other in the video streams, and occasionally use the real-time
text streams for data that need exact spelling or noted.

4.y.  Spoken Japanese user calling a Spanish speaking person.

Someone who speaks Japanese and is subscriber of an on-line interpreting service places a call. 
The call offers audio streams using Japanese in both directions on high preference level, video
with spoken Japanese with no specific preference and both message-wise and real-time text in
Japanese in both directions.
This user is customer of an on-line interpreting service. The service adds its interpreting
language capabilities to the SDP on lower level than the originator, and conveys the call to the destination.
The destination is a Spanish speaking person. The called terminal detects that Spanish is among the possible
languages even if not highest preference, so that call is answered with indication of spoken Spanish at high
priority level and Spanish text messaging in both directions at low priority level.
The on-line interpreting service detects that their translation between Japanese and Spanish is needed to
make the call work, so they allocate an interpreter to the call, and answers the call with an indication
of Japanese towards the caller.
Information that the call will be soon supported by a Japanese/Spanish interpreter is provided in the
appropriate languages in the text message connections.
The users can communicate in their own languages supported by the interpreter.

More might be needed to clarify some more of the endless possible variations and benefit.

Gunnar Hellstršm
On 2013-07-15 04:11, Christian Groves wrote:
Hello Randall and Gunnar,

I think Randall's clarification would be good to have in the draft. I think that when a caller support the language it is sent for every call. Whether the language is used by a receiver depends on the receiver's local capability.

Regards, Christian

On 14/07/2013 4:04 AM, Gunnar Hellstrom wrote:
On 2013-07-13 10:07, Randall Gellens wrote:
At 2:49 PM +1000 7/10/13, Christian Groves wrote:
 I wouldn't have thought that it would be use case specific... i.e. i'd only include my language when I called an emergency service. I would think an endpoint would be configured with the information and then provide it whenever I made a call. Is that the intent?

I expect so, but then, I also didn't expect it to be used much in the person-to-person case since usually language is implied by context when calling an individual.  I expect it to be used when a person is calling an call center (corporate or emergency).  To put it another way, I expect a personal client to always set language on outbound calls, but in most cases to ignore it on inbound calls.  I'd expect a corporate call center, as well as emergency call handling facilities, to pay attention.  I should make this more clear in the draft.

I expect the setting to be retrieved from a personal profile (likely but not necessarily stored in connection with other user information and account information) and used in every call.

mmusic mailing list" rel="nofollow">

mmusic mailing list" rel="nofollow">

mmusic mailing list

Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If you make people think they're thinking, they'll love you; but if you
really make them think they'll hate you.