Question Regarding RFC2616-14.1 Accept Header

Alex Crawford <alex.crawford@coreos.com> Fri, 01 April 2016 15:01 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 205C712D63A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 1 Apr 2016 08:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.931
X-Spam-Level:
X-Spam-Status: No, score=-6.931 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 JP-jPXaR7Yju for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 1 Apr 2016 08:01:02 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 306A912D64D for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 1 Apr 2016 08:01:01 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1am0UZ-0006ec-HZ for ietf-http-wg-dist@listhub.w3.org; Fri, 01 Apr 2016 14:56:07 +0000
Resent-Message-Id: <E1am0UZ-0006ec-HZ@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1am0UV-0006dp-IK for ietf-http-wg@listhub.w3.org; Fri, 01 Apr 2016 14:56:03 +0000
Received: from raoul.w3.org ([128.30.52.128]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1am0UU-0001Sc-CW for ietf-http-wg@w3.org; Fri, 01 Apr 2016 14:56:03 +0000
Received: from platy.fdn.fr ([80.67.176.7] helo=[192.168.1.40]) by raoul.w3.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1am0UT-000DrE-OM for ietf-http-wg@w3.org; Fri, 01 Apr 2016 14:56:01 +0000
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset="us-ascii"
From: Alex Crawford <alex.crawford@coreos.com>
Resent-From: Yves Lafon <ylafon@w3.org>
Date: Thu, 31 Mar 2016 18:33:29 +0000
Content-Transfer-Encoding: quoted-printable
Resent-Date: Fri, 01 Apr 2016 16:55:59 +0200
Resent-To: ietf-http-wg@w3.org
X-Name-Md5: efe3dad792d606410c9cc49cedaffc94
Message-Id: <20160331183255.GA32099@68-f7-28-d0-dd-36.libcore.so>
To: ietf-http-wg@w3.org
X-Mailer: Apple Mail (2.3124)
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.996, W3C_NW=0.5
X-W3C-Scan-Sig: lisa.w3.org 1am0UU-0001Sc-CW deb1094cabd89d9923827442b2bd59e2
X-Original-To: ietf-http-wg@w3.org
Subject: Question Regarding RFC2616-14.1 Accept Header
Archived-At: <http://www.w3.org/mid/20160331183255.GA32099@68-f7-28-d0-dd-36.libcore.so>
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/31375
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hello,

First off, my apologies if this is the wrong list for this question, but I've
had a heck of a time trying to find someone knowledgeable on this topic.

I'm working on a utility that fetches its config via HTTP from a remote system.
The configuration language for this utility will evolve over time, so I need a
way for the utility to convey which configuration versions are valid. I'd like
to use the HTTP Accept header for this task and I think it would look something
like the following (broken across lines for readability):

   application/vnd.coreos.ignition+json; version=2,
   application/vnd.coreos.ignition+json; version=1; q=0.5

My intent is to convey to the remote system that this particular version of the
utility can accept version 1 or 2 of application/vnd.coreos.ignition+json, with
a preference for version 2. I believe this is syntactically correct, but I'm
wondering if it's semantically correct as well - am I abusing this
functionality?

Any insight you might have would be greatly appreciated. Thanks!

-Alex