Re: [Slim] I-D Action: draft-ietf-slim-negotiating-human-language-10.txt

Gunnar Hellström <gunnar.hellstrom@omnitor.se> Thu, 01 June 2017 18:35 UTC

Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: slim@ietfa.amsl.com
Delivered-To: slim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76C1412F3D6 for <slim@ietfa.amsl.com>; Thu, 1 Jun 2017 11:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vn0_y49ykoi3 for <slim@ietfa.amsl.com>; Thu, 1 Jun 2017 11:35:07 -0700 (PDT)
Received: from bin-vsp-out-01.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E93C112EA7F for <slim@ietf.org>; Thu, 1 Jun 2017 11:35:06 -0700 (PDT)
X-Halon-ID: 06a9b3ca-46f9-11e7-b757-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [77.53.231.21]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA for <slim@ietf.org>; Thu, 1 Jun 2017 20:35:02 +0200 (CEST)
To: slim@ietf.org
References: <149609884905.14640.4714137651572553743@ietfa.amsl.com> <54839aba-7ac8-79e4-74f8-927eb455d8af@omnitor.se> <p06240605d553b4cd71e6@[99.111.97.136]> <db378c1e-aecb-f312-fefe-bc7a6eacfebc@omnitor.se> <p06240600d5547791845c@[99.111.97.136]> <e25a2790-0feb-9377-a3c3-f4e984e2cdd8@omnitor.se> <029e25ca-fbf7-b6b1-9432-497f2dfb5a0a@omnitor.se> <p06240607d5560c19be82@[99.111.97.136]>
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
Message-ID: <5e4385da-3d6f-d268-d1a7-e97f860c57cc@omnitor.se>
Date: Thu, 01 Jun 2017 20:35:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <p06240607d5560c19be82@[99.111.97.136]>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/RP0MK6Tdap7Uf2tur9JLX8wZA3g>
Subject: Re: [Slim] I-D Action: draft-ietf-slim-negotiating-human-language-10.txt
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, 01 Jun 2017 18:35:09 -0000

Den 2017-06-01 kl. 20:28, skrev Randall Gellens:
> Edited down for clarity.
>
> At 8:16 PM +0200 6/1/17, Gunnar Hellström wrote:
>
>>>>>
>>>>>  ---Change 2.5-----
>>>>>  Requiring exactly one language per direction in the answer 
>>>>> requires a tight coupling between the device and the user that we 
>>>>> have avoided to specify. It would require either that the device 
>>>>> takes the negotiation decision and dictates to the user e.g. 
>>>>> "SPEAK GERMAN NOW !, or that there is a user interface interaction 
>>>>> to decide which language to answer in, e.g. "The calling part may 
>>>>> accept French or German, indicate here which one you will answer 
>>>>> with".
>>>>>
>>>>>  We do not want to dictate that kind of tight coupling, and 
>>>>> therefore must allow a number of alternative languages in various 
>>>>> media to appear in the answer.
>>>>>
>>>>>  ---Old text 2.5---
>>>>>  In an answer, 'hlang-send' is the language the answerer will send
>>>>>  when using the media (which in most cases is one of the languages in
>>>>>  the offer's 'hlang-recv'), and 'hlang-recv' is the language the
>>>>>  answerer expects to receive in the media (which in most cases is one
>>>>>  of the languages in the offer's 'hlang-send').
>>>>>  ---New text 2.5---
>>>>>  In an answer, 'hlang-send' may be one or a list of alternative 
>>>>> languages the
>>>>>  answerer will select from for sending if using the media for 
>>>>> language
>>>>>  (which in most cases is one of the languages in the offer's 
>>>>> 'hlang-recv'),
>>>>>  and 'hlang-recv' may be one or a list of alternative languages 
>>>>> the answerer
>>>>>  can accept to receive if the media is used for language (which in 
>>>>> most cases is one
>>>>>  of the languages in the offer's 'hlang-send').
>>>>>
>>>>
>>>>  Having one language per media in the answer has been part of the 
>>>> draft all along. I don't recall seeing an objection to this before. 
>>>> Further, Section 3 has said all along that attempting to negotiate 
>>>> multiple languages per media is out of scope:
>>>>
>>>>  (Negotiating multiple simultaneous languages within a media stream is
>>>>  out of scope of this document.)
>>>>
>>>  <GH>Yes, the user will only use one language. But have you thought 
>>> about the consequences for how to accomplish a negotiation result of 
>>> just one language in a media, and just that language will also be 
>>> used by the answering human?
>>>
>>>  It will require tight coupling in the user interface of a kind that 
>>> you do not want to discuss. If the UA decides that the answering 
>>> part will send spoken german, then that needs to be conveyed to the 
>>> user. If the UA instead lets the user decide, then there must be a 
>>> question-answer exchange between the UA and the user to enable the 
>>> UA to have just one language for the media in the answer.
>>>
>>>  We have agreed that some kind of such coupling is needed, and we do 
>>> not specify how. But the requirements on the operation will be much 
>>> less strict if we allow a list of languages per media to be the 
>>> result of the negotiation.
>>>
>>>  The paranthesis " (Negotiating multiple simultaneous languages 
>>> within a media stream is
>>>  out of scope of this document.) " will then apply to the user.
>>>
>>>
>>>  This is a quite new finding from when trying to think through a 
>>> real negotiation, so I am prepared to discuss how strict we should be.
>>>
>>  <GH>After the exercise with the negotiation today, I see that I can 
>> relax this requirement.
>>  But it needs to be clear that the negotiated language in a media 
>> just maybe used for language.
>>  So that it is clear that no simultaneous use is normally required.
>>
>>  That leads to
>>  --New text 2.5 ---
>>  In an answer, 'hlang-send' is the language the answerer will send
>>  if using the media for language (which in most cases is one of the 
>> languages in
>>  the offer's 'hlang-recv'), and 'hlang-recv' is the language the
>>  answerer expects to receive in the media (which in most cases is one
>>  of the languages in the offer's 'hlang-send').
>>
>>  ---end of 2.5 -------------------------
>
> Your request is to change "when using the media" to "if using the 
> media for language".  I can live with this.
>
<GH>Good, accepted.

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288