Re: [Slim] New wording for the use of the asterisk in draft-ietf-slim-negotiating-human-language

Brian Rosen <br@brianrosen.net> Fri, 09 June 2017 18:48 UTC

Return-Path: <br@brianrosen.net>
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 7058B129405 for <slim@ietfa.amsl.com>; Fri, 9 Jun 2017 11:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.20150623.gappssmtp.com
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 svaTPIDFIr9E for <slim@ietfa.amsl.com>; Fri, 9 Jun 2017 11:48:56 -0700 (PDT)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE4841200C5 for <slim@ietf.org>; Fri, 9 Jun 2017 11:48:55 -0700 (PDT)
Received: by mail-pf0-x244.google.com with SMTP id f27so9397398pfe.0 for <slim@ietf.org>; Fri, 09 Jun 2017 11:48:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=SPVIdEHlIWhCd9QHdZ0EJjMJNvQ7gddtf0RrHFOyxfY=; b=uOqST3uGSBaOKGnrN0Zd7bCsoOSMGhzGRz8Wk+brQERUcQVmncQPDXICR5FQQg84hq voyDn2Pv0LEeza92qL/0wkmvI74ZtExriygRqrNepKk560ufYLBiniFEpOxc+uFBawpo +aQTcGgQLb8iwgF031etbeA2SlVWQOVJXANNg0ytpKOrsyZeI77SID9xRVQ//n/sIsCH 0OrQaVCE9XReOMMpzdpAwDgYkM+tCLO1ioh+GgSGXFVztiiDSVSM9h6t0yIe3fDMoBJ0 iviIGH6e8BfLZ5RIQDGTbyg9dAHWCLG43dNowLeiaWGRKXmXwRkaw3Ph0m4u188Kl+zI pclw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=SPVIdEHlIWhCd9QHdZ0EJjMJNvQ7gddtf0RrHFOyxfY=; b=ft06eCme2Itpntfl7vYvVxMOnfDFM0SZ3j+ktLeRqOjIYTYTJi1W4uQhvPfCtDUueP kiXlqI1QANqJ4PXWdE5yVg2FWU8NDmjiwLBh3bHiDPL3J4s+MarYED+3nbpI3VDDNDdD XVlOHVc4Fy3PCT1arUR3vIrTKXuJTqa+xDiVsM3Hvnwy3UyjsgJhOvDXP9sc3eDJfyro spbZfamJFltS4Kq2zH9E93SxQSvmDoTAz4gOa+4fD5AeFEKjP4nbGgLm3ebUALCfhljJ P4uwZZcF9wKayM0oJ0fFvNKtsjNBqXsYC9JGx+bmZYUbSD4ZFCMAkYxKXztNyaH30FOL /x1A==
X-Gm-Message-State: AODbwcCAGnqVkTAQ32PtReARSXwQSYcoQroFO9hF93drPq4fm6UfDmxv l/5RpPIXiwlvzLBy7MtboQ==
X-Received: by 10.84.224.74 with SMTP id a10mr43307138plt.173.1497034135351; Fri, 09 Jun 2017 11:48:55 -0700 (PDT)
Received: from [10.96.43.74] (neustar-sthide-nat1.neustar.biz. [156.154.81.54]) by smtp.gmail.com with ESMTPSA id y2sm5039169pfk.1.2017.06.09.11.48.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jun 2017 11:48:54 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <7669593F-0B97-4AFA-8294-A69684436AD6@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6B3E5FDF-05C0-4B16-BB1D-37D156A62BD0"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 09 Jun 2017 14:48:52 -0400
In-Reply-To: <p06240604d56098a6a37f@[99.111.97.136]>
Cc: Gunnar Hellström <gunnar.hellstrom@omnitor.se>, "slim@ietf.org" <slim@ietf.org>
To: Randall Gellens <rg+ietf@randy.pensive.org>
References: <149609884905.14640.4714137651572553743@ietfa.amsl.com> <54839aba-7ac8-79e4-74f8-927eb455d8af@omnitor.se> <p06240605d553b4cd71e6@[99.111.97.136]> <b4d3e366-1250-283c-9a02-1d6b0d7c822d@omnitor.se> <p06240601d5547c6aa715@[99.111.97.136]> <8ca64f00-b1d1-e4da-05cf-0e4663178d85@omnitor.se> <ed04b0e4-c1c8-8b5d-d275-a575f0747a81@omnitor.se> <p06240601d55a2f62df54@[99.111.97.136]> <a254823b-05fc-d780-3da9-a4518c3fc2fb@omnitor.se> <p06240615d55bae9c6bc3@[99.111.97.136]> <11fef8a5-8ed3-5e70-4ccd-66e7613b22fc@omnitor.se> <p06240604d56098a6a37f@[99.111.97.136]>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/3Plc-q7rdJfWfisjESKciH4tgNQ>
Subject: Re: [Slim] New wording for the use of the asterisk in draft-ietf-slim-negotiating-human-language
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: Fri, 09 Jun 2017 18:48:58 -0000

Generally, I like the wording here.  I’d make a minor suggestion to change "extends the use of the asterisk with a media level indication” to “extends the use of the asterisk convey additional information”  or even "extends the use of the asterisk convey additional information about languages preferences among multiple media sessions”

Brian

> On Jun 9, 2017, at 2:28 PM, Randall Gellens <rg+ietf@randy.pensive.org> wrote:
> 
> At 8:20 PM +0200 6/7/17, Gunnar Hellström wrote:
> 
>> Den 2017-06-06 kl. 03:00, skrev Randall Gellens:
>> 
>>> At 10:21 PM +0200 6/5/17, Gunnar Hellström wrote:
>>> 
>>>> Den 2017-06-04 kl. 23:51, skrev Randall Gellens:
>>>> 
>>>>> Hi Gunnar,
>>>>> 
>>>>> What I'd suggest is that we include an informational reference to the draft, although that requires that at least an initial version of the draft be published pretty quickly. So, my suggestion is that you publish at least a skeleton draft right away (which you can revise and extend quickly), and we add text along the lines of the following, perhaps after the second paragraph of Section 5.3:
>>>>> 
>>>>> Note that separate work [draft-xxx] proposes to use the asterisk (or
>>>>> lack thereof) to convey information between endpoints.
>>>>> 
>>>>> This alerts implementers to the other draft.
>>>>> 
>>>> This might be a possible way ahead, if others also think it is feasible.
>>>> 
>>> 
>>> Gunnar, please upload at least a skeleton version of the draft right away, and let me know the title. If you need help with that, I can create one.
>>> 
>>>> The wording and placement of the text requires more tuning. E.g. it should not say "proposes", but rather "specifies".
>>>> 
>>> 
>>> I was reluctant to say "specifies" until we have a more solid draft (we don't yet have anything). How about if the text says "uses" rather than "proposes to use"? I think that covers it.
>>> 
>> Yes, the drafts for the two functionality extensions are uploaded.
>> 
>> I would think that it would be more logical to insert the note about the added meaning of the asterisk in section 5.2, because 5.3 is for the current interpretation case only.
>> 
>> I propose a change to this current text in 5.2
>> 
>> ------old text----
>> 
>> 
>>    In an offer, each value MAY have an asterisk appended as the final
>>    value.  An asterisk appended to either value in an offer indicates a
>>    request by the caller to the callee to not fail the call if there is
>>    no language in common.  See Section 5.3 for more information and
>>    discussion.
>> 
>>  -----new text could be----
>>    In an offer or answer, each value MAY have an asterisk appended as the final
>>    token.  An asterisk appended to either value in an offer indicates a
>>    request by the caller to the callee to not fail the call if there is
>>    no language in common.  See Section 5.3 for more information and
>>    discussion.
>> 
>>    Note that separate work [draft-hellstrom-slim-modalitypref] extends the use of the
>>    asterisk with a media level indication.
>> 
>> 
>> ---end of change-----------------
> 
> I moved the note from 5.3 to 5.2 and reworded to say "extends the use of the asterisk to convey information between endpoints":
> 
>   In an offer, each list of language tags MAY have an asterisk appended
>   at the end.  An asterisk appended to any value in any media in an
>   offer indicates a request by the caller to the callee to not fail the
>   call if there is no language in common.  See Section 5.3 for more
>   information and discussion.  Note that separate work
>   [I-D.hellstrom-slim-modalitypref] extends the use of the asterisk to
>   convey information between endpoints.
> 
>> The other draft, about simultaneous modality may also need to be announced.
>> I suggest this change:
>> 
>> ----old text in 5.2------
>> 
>>  BCP 47 describes mechanisms for
>>    matching language tags.  Note that [RFC5646] Section 4.1 advises to
>>    "tag content wisely" and not include unnecessary subtags.
>> 
>>  ----new text-----
>> 
>>  BCP 47 describes mechanisms for
>>    matching language tags.  Note that [RFC5646] Section 4.1 advises to
>>    "tag content wisely" and not include unnecessary subtags.
>> 
>> 
>>  Note also that separate work in [draft-hellstrom-slim-simultaneous-modality] uses a
>>  notation with a subtag for extended functionality. It is therefore of importance to
>>  use the mechanisms from BCP 47 for matching languages correctly.
>> 
>> ----end of change-----
> 
> I am not sure we need to reference the other draft, since it doesn't directly affect the usage of this draft.
> 
>> 
>>  This all builds on that we can at least get WG draft status soon on the new drafts.
> 
> -- 
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly selected tag: ---------------
> "SFPD Homicide: Our Day Begins when Yours End" --Slogan seen on back of
> San Francisco Police Jacket, as reported by Herb Caen in SF Chronicle
> 
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org <mailto:SLIM@ietf.org>
> https://www.ietf.org/mailman/listinfo/slim <https://www.ietf.org/mailman/listinfo/slim>