Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter

Larry Masinter <masinter@adobe.com> Mon, 17 March 2014 00:54 UTC

Return-Path: <masinter@adobe.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 343691A0339 for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 17:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 SgHzDpVDksZE for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 17:54:07 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 29B241A032B for <json@ietf.org>; Sun, 16 Mar 2014 17:54:06 -0700 (PDT)
Received: from BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) by BL2PR02MB305.namprd02.prod.outlook.com (10.141.91.17) with Microsoft SMTP Server (TLS) id 15.0.893.10; Mon, 17 Mar 2014 00:53:57 +0000
Received: from BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) by BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) with mapi id 15.00.0893.001; Mon, 17 Mar 2014 00:53:57 +0000
From: Larry Masinter <masinter@adobe.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>, Matt Miller <mamille2@cisco.com>
Thread-Topic: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
Thread-Index: AQHPQFVChMk0qCQ/h0SHqE0YpXG40prkdUow
Date: Mon, 17 Mar 2014 00:53:56 +0000
Message-ID: <e4ee7f04f1424e7eb884d87d16bd9105@BL2PR02MB307.namprd02.prod.outlook.com>
References: <53238F21.2030508@cisco.com> <nll8i999lis5u0f719iv6bgte71d8uus52@hive.bjoern.hoehrmann.de>
In-Reply-To: <nll8i999lis5u0f719iv6bgte71d8uus52@hive.bjoern.hoehrmann.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.184.24.49]
x-forefront-prvs: 0153A8321A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(51704005)(24454002)(199002)(189002)(85306002)(90146001)(74706001)(31966008)(74502001)(74876001)(74662001)(95666003)(97186001)(95416001)(81816001)(66066001)(74366001)(83072002)(63696002)(47976001)(50986001)(51856001)(54316002)(47446002)(81542001)(54356001)(33646001)(2656002)(15202345003)(4396001)(47736001)(92566001)(15975445006)(87266001)(59766001)(77982001)(93516002)(69226001)(86362001)(74316001)(94316002)(65816001)(81686001)(85852003)(56816005)(97336001)(53806001)(49866001)(46102001)(80976001)(76482001)(81342001)(79102001)(87936001)(76576001)(80022001)(83322001)(19580395003)(93136001)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR02MB305; H:BL2PR02MB307.namprd02.prod.outlook.com; CLIP:50.184.24.49; FPR:DCAFD173.2CBA0FE1.43C32386.D6E6D2C3.200D8; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (: adobe.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/json/T-9QFa8TSp9C0136s_Lcn8APJis
Cc: IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
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, 17 Mar 2014 00:54:11 -0000

> * Matt Miller wrote:
> >.. adopt I-JSON
> >(http://tools.ietf.org/html/draft-bray-i-json-01) 

> No, not without changing the nature of the document considerably. These
> are just best practises and not a separate format with its own name.

+1, no new name. best practices if you want to be a conservative sender.
Possibly validated in spoof-prevention scenarios.