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

Gunnar Hellstrom <gunnar.hellstrom@omnitor.se> Thu, 11 July 2013 05:35 UTC

Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E099021F9DAF for <mmusic@ietfa.amsl.com>; Wed, 10 Jul 2013 22:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMVhHjlOTPGm for <mmusic@ietfa.amsl.com>; Wed, 10 Jul 2013 22:35:00 -0700 (PDT)
Received: from vsp-authed-03-02.binero.net (vsp-authed02.binero.net [195.74.38.226]) by ietfa.amsl.com (Postfix) with SMTP id 53B1421F9D8B for <mmusic@ietf.org>; Wed, 10 Jul 2013 22:34:59 -0700 (PDT)
Received: from smtp01.binero.se (unknown [195.74.38.28]) by vsp-authed-03-02.binero.net (Halon Mail Gateway) with ESMTP for <mmusic@ietf.org>; Thu, 11 Jul 2013 07:34:50 +0200 (CEST)
Received: from [192.168.50.38] (h79n2fls31o933.telia.com [212.181.137.79]) (Authenticated sender: gunnar.hellstrom@omnitor.se) by smtp-09-01.atm.binero.net (Postfix) with ESMTPA id 77C5B3A11F for <mmusic@ietf.org>; Thu, 11 Jul 2013 07:34:50 +0200 (CEST)
Message-ID: <51DE43FC.6080508@omnitor.se>
Date: Thu, 11 Jul 2013 07:34:52 +0200
From: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: mmusic@ietf.org
References: <p0624061acd691d9b38bc@dhcp-42ec.meeting.ietf.org> <B0295A41-BF2B-4520-8495-7A88B4803F30@acmepacket.com> <5144E4E5.4030801@omnitor.se> <03559DEF-E442-4118-A616-8D7E42D1F22A@acmepacket.com> <5145729C.6030905@omnitor.se> <514FE5A9.3060900@nteczone.com> <p06240615cdfea836f364@[99.111.97.136]> <51DBB813.4060607@nteczone.com> <p0624060ece02360a322d@[99.111.97.136]> <51DC9B66.6090302@omnitor.se> <51DCE7CB.7080205@nteczone.com>
In-Reply-To: <51DCE7CB.7080205@nteczone.com>
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-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jul 2013 05:35:06 -0000

On 2013-07-10 06:49, 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?
>
> Christian
Yes, that is the intent.

And for both relay service invocation and any other assisting service 
invocation, it is best for the user to dial the destination, and get the 
assisting service invoked by an indication like this in the call, rather 
than being forced to first call an assisting service and with them 
discuss who is the final destination of the call.

The other party in the call may be another user, a call center, an 
emergency service or a conference bridge.

Gunnar

>
> On 10/07/2013 9:23 AM, Gunnar Hellstrom wrote:
>> On 2013-07-09 23:58, Randall Gellens wrote:
>>> This is a different, and more complex, scenario than what this 
>>> proposal is trying to solve.  This proposal is focused on simpler 
>>> cases where someone places an emergency call or calls a corporate 
>>> call center.  Possibly this can be just a simple case of the more 
>>> complex cases? 
>> My view is that it is intended to also cover user-to-user cases, 
>> where preferences are compared and a relay service (or language 
>> interpreter) can be invoked to bridge language gaps.
>>
>> Gunnar
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic