Re: [Slim] Open Issues on draft-ietf-slim-negotiating-human-language

Randall Gellens <rg+ietf@randy.pensive.org> Thu, 01 June 2017 17:03 UTC

Return-Path: <rg+ietf@randy.pensive.org>
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 7F66E128D6F for <slim@ietfa.amsl.com>; Thu, 1 Jun 2017 10:03:26 -0700 (PDT)
X-Quarantine-ID: <goaU6U0ugItc>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 goaU6U0ugItc for <slim@ietfa.amsl.com>; Thu, 1 Jun 2017 10:03:24 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 873E912EB07 for <slim@ietf.org>; Thu, 1 Jun 2017 10:03:23 -0700 (PDT)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 1 Jun 2017 10:05:39 -0700
Mime-Version: 1.0
Message-Id: <p06240603d555f797f000@[99.111.97.136]>
In-Reply-To: <2A61C813-6E0C-488C-9A73-972D47D62719@gsma.com>
References: <CAOW+2dtU+sbM=7tYYr0m8t3D6eyKiKo_ShVhoAjaKOBuJYpdNw@mail.gmail.com> <p06240606d550fb76f4a0@[99.111.97.136]> <b05d8e79-104c-f3be-06b6-7df5254f7b48@omnitor.se> <p06240600d5524da4e807@[99.111.97.136]> <DD8DA8BD-65E6-4825-B928-CCC06BAFC8A2@gsma.com> <p06240601d555cbe1b15f@[99.111.97.136]> <2A61C813-6E0C-488C-9A73-972D47D62719@gsma.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 01 Jun 2017 10:03:12 -0700
To: Natasha Rooney <nrooney@gsma.com>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: Gunnar Hellström <gunnar.hellstrom@omnitor.se>, Bernard Aboba <bernard.aboba@gmail.com>, "slim@ietf.org" <slim@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/meclU8MXIoeOAAxUWpBBDqux-4A>
Subject: Re: [Slim] Open Issues on 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: Thu, 01 Jun 2017 17:03:26 -0000

At 2:00 PM +0000 6/1/17, Natasha Rooney wrote:

>>  On 1 Jun 2017, at 14:49, Randall Gellens 
>> <<mailto:rg+ietf@randy.pensive.org>rg+ietf@randy.pensive.org> 
>> wrote:
>>
>>  The syntax does not permit a * only, there has to be at least one 
>> language tag.
>>
>
>  That's fine - but can we just explain that somewhere?

We do.  Section 5.2 says:

    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.

Section 5.3 says:

    The mechanism for indicating this preference is that, in an offer, if
    the last value of any 'hlang-recv' or 'hlang-send' for any media is
    an asterisk, this indicates a request to not fail the call.  The
    called party MAY ignore the indication, e.g., for the emergency
    services use case, regardless of the absence of an asterisk, a PSAP
    will likely not fail the call; some call centers might reject a call
    even if the offer contains an asterisk.

Section 6.1 says:

    Attribute Syntax:

       hlang-value =  Language-Tag *( SP Language-tag ) [ SP asterisk ]

                            ; Language-Tag as defined in BCP 47

       asterisk    =  "*"   ; an asterisk (0x2A) character

       SP          =  1*" " ; one or more space (0x20) characters

So, the text in both 5.2 and 5.3 make clear that an asterisk may be 
appended, but can't appear on its own.  The text also explains what 
an asterisk means.  The syntax in 6.1 also clearly shows that an 
asterisk can only appear after one or more language tags.

(As a separate issue, Gunnar felt that using the word "value" to mean 
the set of language tags as well as each language tag or asterisk is 
confusing, so I'm thinking I will use the word "token" for the second 
use, to refer to each tag or asterisk.)
-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Never look at the trombones, it only encourages them.
                                   --Richard Strauss