Protocol Action: 'The I-JSON Message Format' to Proposed Standard (draft-ietf-json-i-json-06.txt)
The IESG <iesg-secretary@ietf.org> Thu, 12 February 2015 12:52 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA551A87CE; Thu, 12 Feb 2015 04:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 ajP2mZo4-11N; Thu, 12 Feb 2015 04:51:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A7A1A87D7; Thu, 12 Feb 2015 04:51:50 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'The I-JSON Message Format' to Proposed Standard (draft-ietf-json-i-json-06.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150212125150.17727.31698.idtracker@ietfa.amsl.com>
Date: Thu, 12 Feb 2015 04:51:50 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/Tj40hbPapXmI6Ob7IxrkCITYCks>
Cc: json mailing list <json@ietf.org>, json chair <json-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 12:52:00 -0000
The IESG has approved the following document: - 'The I-JSON Message Format' (draft-ietf-json-i-json-06.txt) as Proposed Standard This document is the product of the JavaScript Object Notation Working Group. The IESG contact persons are Pete Resnick and Barry Leiba. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-json-i-json/ Technical Summary This document defines a profile of JSON (RFC 7159). This profile further restricts characters, numbers, object members; it also provides additional recommendations for protocol use. Working Group Summary The WG discussion was not as extensive as for RFC 7159, but still broad. Two major points were brought up in WG Last Call: defining a link relation profile URI, and the use of base64 versus bsae64url. It was suggested that a profile URI be defined as an alternative to defining a media type or media type suffix (which is also not defined in this document). However, the WG could not reach consensus on this change. There was considerable debate over the use of base64 versus base64url. The WG consensus was that binary data be encoded as some form of base64 but could not reach any consensus on which specific variant. The document first specified base64url and without consensus to change it, it remains the recommendation in the document. Document Quality Overall, the consensus on publishing this document is rough. At least one participant still questions its utility. Personnel Matthew Miller (JSON WG co-chair) is the document shepherd Pete Resnick is the responsible AD. IANA Note There are no IANA Considerations.