[Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
Matt Miller <mamille2@cisco.com> Fri, 14 March 2014 23:22 UTC
Return-Path: <mamille2@cisco.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 99C141A0214 for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 16:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level:
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 rRDso1DeQI2o for <json@ietfa.amsl.com>; Fri, 14 Mar 2014 16:22:18 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id EE2BA1A0213 for <json@ietf.org>; Fri, 14 Mar 2014 16:22:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=593; q=dns/txt; s=iport; t=1394839331; x=1396048931; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=pVcDiwlYRN1wJIjYQqpE/D5xR4MC+oWvuxiLWbUFjQA=; b=Sx/Z/gEsDEaptkSah4fE2Yecqc1Ja8QvsFjiK+eHvZKxlmO/peSZf/JH lX9wdnJqqiX/4GC47AnJRL7fwRPO9d4r8gw0geGGZFwQ/Rk9tYOyqL+nS 1+eqtdXpYjQI9Qd9MnXz9+6WJnkC3JVf4JEa53egHPdampHtPC3jWOaJM I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsUJAKqOI1OtJV2d/2dsb2JhbABZgwY7V6h4BJoRFnSCSVs9FhgDAgECAUsNCAEBh3UNojGxfReOE4UTBIkZOI50gTKQfINMggw
X-IronPort-AV: E=Sophos;i="4.97,657,1389744000"; d="scan'208";a="27635953"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-2.cisco.com with ESMTP; 14 Mar 2014 23:22:10 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s2ENMAuX002933 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <json@ietf.org>; Fri, 14 Mar 2014 23:22:10 GMT
Received: from MAMILLE2-M-T03K.local (64.101.72.33) by xhc-rcd-x05.cisco.com (173.37.183.79) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 14 Mar 2014 18:22:10 -0500
Message-ID: <53238F21.2030508@cisco.com>
Date: Fri, 14 Mar 2014 17:22:09 -0600
From: Matt Miller <mamille2@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: IETF JSON WG <json@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [64.101.72.33]
Archived-At: http://mailarchive.ietf.org/arch/msg/json/80btI1DWbAwDX7-yqeK4xiEAzI8
Subject: [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: Fri, 14 Mar 2014 23:22:19 -0000
The chairs are seeking comment on whether we should adopt I-JSON (http://tools.ietf.org/html/draft-bray-i-json-01) as a WG item in our charter. Remember that adopting this draft does not mean it is done; changes can happen based on the consensus of the WG. Note that the current draft does *not* have the new MIME type nor the reserved field name that was heavily debated in London; that could be added later if there is WG consensus to do so. Please speak up whether or not you believe our charter should be amended to include this work item. --Paul Hoffman and Matt Miller
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nico Williams
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tony Hansen
- [Json] Call for WG Consensus to Adopt I-JSON as a… Matt Miller
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tim Bray
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nat Sakimura
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Dave Cottlehuber
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Levine
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Martin J. Dürst
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Stefan Drees
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tim Bray
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Larry Masinter
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nico Williams
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker