IETF Logo Mail Archive

Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02

Nico Williams <nico@cryptonector.com> Mon, 07 July 2014 05:35 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8173D1A0AEF for <json@ietfa.amsl.com>; Sun, 6 Jul 2014 22:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 kZDLPNV3p1nq for <json@ietfa.amsl.com>; Sun, 6 Jul 2014 22:35:08 -0700 (PDT)
Received: from homiemail-a87.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id E548E1A0640 for <json@ietf.org>; Sun, 6 Jul 2014 22:35:08 -0700 (PDT)
Received: from homiemail-a87.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a87.g.dreamhost.com (Postfix) with ESMTP id 9432E26C069 for <json@ietf.org>; Sun, 6 Jul 2014 22:35:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=U/fApWBeAOcVuEQ0YXTP 3gNhH/Y=; b=Wy0OoTfSS5mp9qPZYUQxu9hOxC/Go/W9rgnyvJF/ZvY6+hBRuS4x LK28kHxGBogebESkfzh9LV+SD0W3kzPkRQBdg+vZ9Jc2Ae4r+PYV8fRNYrqvSQEP 7zA3BUUNuExyiEaRribM9hnTqA5h9i+6c2c91XwpmRFJW0ANUflABR4=
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a87.g.dreamhost.com (Postfix) with ESMTPSA id 4584F26C063 for <json@ietf.org>; Sun, 6 Jul 2014 22:35:08 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id n15so6040568wiw.11 for <json@ietf.org>; Sun, 06 Jul 2014 22:35:06 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.84.7 with SMTP id u7mr73296921wiy.1.1404711306910; Sun, 06 Jul 2014 22:35:06 -0700 (PDT)
Received: by 10.216.29.201 with HTTP; Sun, 6 Jul 2014 22:35:06 -0700 (PDT)
In-Reply-To: <CFDCB00F.52A7B%jhildebr@cisco.com>
References: <CALcoZionwZ1gn0hkhq4sKcDKg3LK13+d-XvBzXUA4iHjS6PHNA@mail.gmail.com> <CAMm+LwgU5veinaNJ6ptLJ509QD3R5=LEbpfmNjZSy5C+8jfPXg@mail.gmail.com> <CAHBU6iuc2j4a5VYnrboMEMnAPxhs5i+iZxfpbfnN1oa3740TfQ@mail.gmail.com> <CALcoZioTakxzkuvrt1EgNAKS==NNskWJ1TLUjxtZ1TBGPD+EXw@mail.gmail.com> <CFDCB00F.52A7B%jhildebr@cisco.com>
Date: Mon, 07 Jul 2014 00:35:06 -0500
Message-ID: <CAK3OfOhH=38=aR=xYUGGDT0a9B+vdoiNgF6GjJTRyk_EAnwqGw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/06EIvJbKkbSxH-rcveTDbVg305s
Cc: Mark Baker <distobj@acm.org>, Phillip Hallam-Baker <ietf@hallambaker.com>, Tim Bray <tbray@textuality.com>, JSON WG <json@ietf.org>
Subject: Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 05:35:09 -0000

On Fri, Jul 4, 2014 at 8:30 PM, Joe Hildebrand (jhildebr)
<jhildebr@cisco.com> wrote:
> There are times when, in the documentation for a service that is producing
> JSON, I would like to say:
>
> "If you receive a message from me that is not strictly I-JSON, I would
> prefer you treat it as an error on my part, and therefore treat my message
> as invalid, because if something went wrong enough that what I sent you
> wasn't valid I-JSON my server room is likely on fire."

Shades of "secure bit".  This is not appropriate for a protocol, IMO.

Nico
--

v2.37.1 | Report a Bug | By Email | System Status