Re: [MMUSIC] Notes from Orlando human language draft discussion

Christian Groves <> Fri, 19 July 2013 01:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1734711E8208 for <>; Thu, 18 Jul 2013 18:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id scyc7bSzxtC3 for <>; Thu, 18 Jul 2013 18:08:46 -0700 (PDT)
Received: from ( [IPv6:2001:44b8:8060:ff02:300:1:6:6]) by (Postfix) with ESMTP id 3F69711E8186 for <>; Thu, 18 Jul 2013 18:08:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
Received: from (HELO []) ([]) by with ESMTP; 19 Jul 2013 10:38:38 +0930
Message-ID: <>
Date: Fri, 19 Jul 2013 11:08:28 +1000
From: Christian Groves <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Randall Gellens <>
References: <> <> <> <> <> <> <p06240615cdfea836f364@[]> <> <p0624060ece02360a322d@[]> <> <> <p06240603ce06ba958db4@[]> <> <> <p06240602ce0dc4c31dd8@[]>
In-Reply-To: <p06240602ce0dc4c31dd8@[]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [MMUSIC] Notes from Orlando human language draft discussion
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: Fri, 19 Jul 2013 01:08:47 -0000

Hello Randall,

I think you're mixing protocol functionality with application.

 From a protocol perspective I think that all you need to say is 
something like:

Clients that have a language preference related to a media stream/s 
shall set the 'humintlang-send' and/or 'humintlang-recv' attribute on 
the applicable media stream at session establishment. Receivers of the 
'humanintlang-*" attributes may then apply session handling based on the 
received language/s and according to local policy. For example: Call 
centers and PSAPs may route the session to an operator that is capable 
of communicating in the preferred language/s.

I think this describes the protocol behaviour without requiring 
behaviour depending on user type.

Regards, Christian

On 19/07/2013 2:14 AM, Randall Gellens wrote:
> Hi Christian,
> How about this text:
>    Clients acting on behalf of end users are expected to set one or both
>    'humintlang-send' and 'humintlang-recv' attributes on each media
>    stream primarily intended for human communication in an offer when
>    placing an outgoing session, but either ignore or take into
>    consideration the attributes when receiving incoming calls, based on
>    local configuration and capabilities.  Systems acting on behalf of
>    call centers and PSAPs are expected to take into account the values
>    when processing inbound calls.
> At 12:11 PM +1000 7/15/13, 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.
>>>  /Gunnar
>>>  _______________________________________________
>>>  mmusic mailing list
>>  _______________________________________________
>>  mmusic mailing list