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

Gunnar Hellstrom <gunnar.hellstrom@omnitor.se> Thu, 18 July 2013 21:19 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 2E2DD11E8214 for <mmusic@ietfa.amsl.com>; Thu, 18 Jul 2013 14:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 yhW56mmMzDlM for <mmusic@ietfa.amsl.com>; Thu, 18 Jul 2013 14:19:48 -0700 (PDT)
Received: from vsp-authed-02-02.binero.net (vsp-authed02.binero.net [195.74.38.226]) by ietfa.amsl.com (Postfix) with SMTP id 79FF411E8209 for <mmusic@ietf.org>; Thu, 18 Jul 2013 14:19:38 -0700 (PDT)
Received: from smtp01.binero.se (unknown [195.74.38.28]) by vsp-authed-02-02.binero.net (Halon Mail Gateway) with ESMTP for <mmusic@ietf.org>; Thu, 18 Jul 2013 23:19:29 +0200 (CEST)
Received: from [192.168.50.33] (h79n2fls31o933.telia.com [212.181.137.79]) (Authenticated sender: gunnar.hellstrom@omnitor.se) by smtp-03-01.atm.binero.net (Postfix) with ESMTPA id 6C0313A161 for <mmusic@ietf.org>; Thu, 18 Jul 2013 23:19:29 +0200 (CEST)
Message-ID: <51E85BE6.50904@omnitor.se>
Date: Thu, 18 Jul 2013 23:19:34 +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: <p06240602ce081a3d3f8c@[10.121.65.183]> <51E322C9.4040002@omnitor.se> <51E35C7F.7030101@nteczone.com> <p06240603ce0dc4fe2ba5@[99.111.97.136]>
In-Reply-To: <p06240603ce0dc4fe2ba5@[99.111.97.136]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [MMUSIC] draft-gellens-mmusic-negotiating-human-language-01.txt
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, 18 Jul 2013 21:19:55 -0000

On 2013-07-18 18:16, Randall Gellens wrote:
>>>  2. You have also introduced this paragraph in 7.1:
>>>  "
>>>  Clients acting on behalf of end users are expected to set one or both
>>>      'humintlang-send' and 'humintlang-recv' attributes on each media
>>>      stream in an offer when placing an outgoing session but ignore the
>>>      attributes when receiving incoming calls.  Systems acting on 
>>> behalf
>>>      of call centers and PSAPs are expected to take into account the
>>>      values when processing inbound calls.
>>>  "
>>>
>>>  What is the thought behind this?
>>>
>>>  I see the humintlang specification equally valuable in outgoing as 
>>> incoming calls, and for end-users as well as call-centers and PSAPs.
>>>  If a user gets an incoming call, with humintlang specifications, it 
>>> can compare with its own profile and decide to invoke a
>>>  relay service or interpreter servicde to cover some differences in 
>>> language preferences, or just prepare for what media, modalities and
>>>  languages to use in the call..
>>>  I do not see the background for this paragraph, and think it will 
>>> be better to delete it.
>>>
>>>
>>  [CNG] I guess this is a question of scope. I would think that the 
>> draft would just describe the syntax and procedures of this new 
>> language tag in a generic manner. The application level behaviour of 
>> call centres and PSAPs would be defined elsewhere?
>
> [RG] That would be fine with me; my attempt in adding the text using 
> descriptive rather than normative language was to clarify the intended 
> use without imposing mandates on call centers and PSAPs (which, as you 
> say, will be done elsewhere).
But since your assumption of use was far from mine, I hope that you 
accept to delete the paragraph.


Or change it to:

  "
  Clients are expected to set one or both
      'humintlang-send' and 'humintlang-recv' attributes on each media
      stream in an offer and answer for which the users has any 
preferences or capabilities for use in human communication. Systems are 
expected to take into account the
      values when processing inbound calls or when processing the 
answers on outbound calls. The values can also be used for call handling 
decisions by service providers.
  "


Regards

Gunnar