[Json] A word from the Chairs

"Matt Miller (mamille2)" <mamille2@cisco.com> Fri, 31 May 2013 17:28 UTC

Return-Path: <mamille2@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C9C5421F85BF for <json@ietfa.amsl.com>; Fri, 31 May 2013 10:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 2x91-azTUaFz for <json@ietfa.amsl.com>; Fri, 31 May 2013 10:28:18 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 1B26221F8517 for <json@ietf.org>; Fri, 31 May 2013 10:28:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8922; q=dns/txt; s=iport; t=1370021298; x=1371230898; h=from:to:cc:subject:date:message-id:mime-version; bh=jrerX5Tlfqa9twkTLwXjMQXdhcunEbW/K36UQTlj0OQ=; b=GBvtkF20WMY6Z92bfAaxWWwDM+/9tSG7oJeSEg+zwe8m7biZo+dNZvfD sPaBEDFdOWhhkmMEBZhI0ctPK4Zi7VJYPzj5zrY8uZ2RrfRQ7nGd2LEJj LgyhMvvKu/R00DtJPB5giTVZEZofwtAzib4V7JIGP2B/8dsxQkwYF1UDr 4=;
X-Files: smime.p7s : 4136
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFACTdqFGtJV2c/2dsb2JhbABagwm/HoECFnSCJQEEHUgJCxIBKiYwJwQODQaHf7pLjnAxgn1hA5AAgSyCQZURgw+CJw
X-IronPort-AV: E=Sophos; i="4.87,780,1363132800"; d="p7s'?scan'208"; a="214342846"
Received: from rcdn-core-5.cisco.com ([]) by rcdn-iport-9.cisco.com with ESMTP; 31 May 2013 17:28:17 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com []) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4VHSHqG000497 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 May 2013 17:28:17 GMT
Received: from xmb-aln-x11.cisco.com ([]) by xhc-aln-x13.cisco.com ([]) with mapi id 14.02.0318.004; Fri, 31 May 2013 12:28:17 -0500
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: "<json@ietf.org>" <json@ietf.org>
Thread-Topic: A word from the Chairs
Thread-Index: AQHOXiQ8uEkLdb4RPkqxttzVzX5OLQ==
Date: Fri, 31 May 2013 17:28:16 +0000
Message-ID: <BF7E36B9C495A6468E8EC573603ED94115268A5D@xmb-aln-x11.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
Content-Type: multipart/signed; boundary="Apple-Mail=_D30298F3-26D2-4B10-99C4-023F8883A5F3"; protocol="application/pkcs7-signature"; micalg="sha1"
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: [Json] A word from the Chairs
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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, 31 May 2013 17:28:23 -0000

Welcome everyone!

The JSON WG currently has just one task in its charter: the minor revision of RFC 4627 to bring it onto the Standards Track. This is essentially a reclassification in place, with minimal changes. The WG will correct significant errors and inconsistencies, but will keep changes to a minimum.

From the earlier discussion in the BoF and on the mailing list, there is likely to be differences of opinion of what “keep changes to a minimum” means for various proposed changes. The WG chairs want to have a process that facilitates open discussion without judgement of whether or not a particular proposal meets the charter requirement too early in the process. This needs to be balanced against having the WG get bogged down in discussions of changes that few people support.

WG members can say during the discussion or during the consensus calls if they think a proposed change is outside the charter’s mandate to “keep changes to a minimum” as well as whether they think a proposed change is technically sound.

Our intention is to conduct the discussion as follows:

- WG members bring up proposed changes on the mailing list. These proposals need to include specific intended wording changes to the current-at-that-time draft, but the wording can change during the discussion. It is expected that many topics will be being discussed simultaneously.

- When the discussion of a topic has died down, the WG chairs will nudge the list for any remaining discussion.

- When that discussion has died down, the WG chairs will issue a formal call for consensus on the specific wording. The call will always have at least two choices: “leave the document as-is” and one or more sets of wording changes. The intention is that there is no discussion during the consensus call, just people stating their own opinions. There may be more than one consensus call on different topics running at the same time.

- After a consensus call that results in changes to the draft is complete, the WG chairs will ask the authors to issue a new draft quickly. This will facilitate the WG knowing what the state of the document is at any time.

- If any consensus call has fewer than five responses, the WG chairs will not consider the proposal to have consensus, and no changes to the document will be made.  WG members are free to raise the proposal again later, following the same guidelines as above.

If a WG member has proposed a change with specific wording and the WG chairs have not acted as stated above, that person should nudge the WG chairs in order to keep the discussion fresh and to have the consensus calls come close in time to the main discussion.

Thank you,

Matt Miller and Paul Hoffman