Re: Genart last call review of draft-ietf-core-links-json-07

Adam Roach <adam@nostrum.com> Wed, 26 April 2017 17:12 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9432712955D; Wed, 26 Apr 2017 10:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level:
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 CsqE8Dichnhf; Wed, 26 Apr 2017 10:12:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 ACCBB131544; Wed, 26 Apr 2017 10:12:54 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v3QHCgq7059727 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Apr 2017 12:12:43 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
Subject: Re: Genart last call review of draft-ietf-core-links-json-07
To: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
Date: Wed, 26 Apr 2017 12:12:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AW-dD99pPJvtjyZY6Epz0d5gKZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:12:56 -0000

On 4/25/17 17:19, Elwyn Davies wrote:
> >From JSON to RFC 6690: 
> - Remove the double quotes from the JSON string value and do any
> necessary decoding and encoding.  Reapply double quotes.  Note that
> this may result in values that were originally not enclosed in double
> quotes in the RFC 6690 repreentation becoming enclosed in double
> quotes. However, [AFAICS] this does not alter the semantics of any of
> the predefined parameters.  For example the ABNF productions mean that
> ct=40 and ct="40" are equivalent (the second case is needed so that
> one can also have ct="40 41 42").  What IS needed is a statement that
> this must also apply to any application specific parameters.  For
> example the case in examples 4 and 5 of ..;foo="bar";foo=3;...
> transforming to "foo":["bar","3"] and then back to
> ...;foo="bar";foo="3";.. MUST require that the two RFC 6690
> representations are equivalent.


This has the reciprocal problem that using quotes with (e.g.) sz and 
hreflang is a violation of the ABNF in RFC6690.

/a