IETF Logo Mail Archive

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

Carsten Bormann <cabo@tzi.org> Wed, 26 April 2017 18:20 UTC

Return-Path: <cabo@tzi.org>
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 2EE9C13156A; Wed, 26 Apr 2017 11:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 4yTDYMOUd1-9; Wed, 26 Apr 2017 11:20:55 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 40982131565; Wed, 26 Apr 2017 11:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3QIKnc6028132; Wed, 26 Apr 2017 20:20:49 +0200 (CEST)
Received: from [192.168.217.124] (p5DC7F3A7.dip0.t-ipconnect.de [93.199.243.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3wCpKs0RWgzDH41; Wed, 26 Apr 2017 20:20:49 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Genart last call review of draft-ietf-core-links-json-07
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
Date: Wed, 26 Apr 2017 20:20:47 +0200
Cc: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514923647.182059-f87b135b40f402b437f2bb96c0d3467d
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6D9E89E-2D94-401C-9B00-84CE7E36657C@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com> <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vueh-BPnVqylBQkYYv8nAQZ6Cpw>
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 18:20:58 -0000

On Apr 26, 2017, at 19:12, Adam Roach <adam@nostrum.com> wrote:
> 
> This has the reciprocal problem that using quotes with (e.g.) sz and hreflang is a violation of the ABNF in RFC6690.

Yes.  Using ABNF for the serialization of an item that should be described at the data model level (as in 5988bis) is now generally considered a mistake.  To stay compatible with the letter of RFC 6690 (which probably continues to be a good idea), the reference implementation in Appendix A of links-json uses the quote-less form whenever the value is a ptoken, i.e. a sequence of one or more ptokenchar characters(*).  Should we require this, and if yes, should this be a SHOULD or a MUST?

Grüße, Carsten

(*)
    ptoken         = 1*ptokenchar
    ptokenchar     = "!" / "#" / "$" / "%" / "&" / "'" / "("
                   / ")" / "*" / "+" / "-" / "." / "/" / DIGIT
                   / ":" / "<" / "=" / ">" / "?" / "@" / ALPHA
                   / "[" / "]" / "^" / "_" / "`" / "{" / "|"
                   / "}" / "~"

v2.23.0 | Report a Bug | By Email