[Json] Publishing draft-ucarion-json-type-definition as an RFC
"RFC ISE (Adrian Farrel)" <rfc-ise@rfc-editor.org> Mon, 20 April 2020 11:03 UTC
Return-Path: <rfc-ise@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id DF9093A0B65;
Mon, 20 Apr 2020 04:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5
tests=[SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=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 qNmJI7JWLi8v; Mon, 20 Apr 2020 04:03:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id B03663A0B53;
Mon, 20 Apr 2020 04:03:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
by rfc-editor.org (Postfix) with ESMTP id E5D62F406CD;
Mon, 20 Apr 2020 04:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1])
by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id C7oTYvdYNXmU; Mon, 20 Apr 2020 04:03:49 -0700 (PDT)
Received: from www.rfc-editor.org (localhost [127.0.0.1])
by rfc-editor.org (Postfix) with ESMTP id E0774F406CB;
Mon, 20 Apr 2020 04:03:49 -0700 (PDT)
Received: from 81.174.202.163 (SquirrelMail authenticated user rfcpise)
by www.rfc-editor.org with HTTP; Mon, 20 Apr 2020 04:03:49 -0700
Message-ID: <e097e37931c61c3a6349957a07f27017.squirrel@www.rfc-editor.org>
Date: Mon, 20 Apr 2020 04:03:49 -0700
From: "RFC ISE (Adrian Farrel)" <rfc-ise@rfc-editor.org>
To: json@ietf.org
Cc: "Adrian Farrel" <rfc-ise@rfc-editor.org>,
draft-ucarion-json-type-definition@ietf.org
Reply-To: rfc-ise@rfc-editor.org
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/uVg3A5A8O9lItmHvU7eF8SIYBYM>
Subject: [Json] Publishing draft-ucarion-json-type-definition as an RFC
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 20 Apr 2020 11:03:58 -0000
Hi JSON list, draft-ucarion-json-type-definition has been presented to the Independent Submissions Editor for publication as an RFC. Obviously, this document has received a fair amount of discussion on the JSON list, and the author informs me that the current revision owes a lot to the suggestions made on the list. However, JSON is not currently an active working group and so there is no obvious home for the work within the IETF. I have flagged the draft on the Dispatch mailing list in case there is interest in adopting the work in some way, and it was pointed out that I should raise a similar flag here. The default position will be that the draft is progressed on the Independent Stream, but should anyone believe that it would be better worked on within the IETF, I'd be happy to hear that and we can discuss with the ADs how best to progress it. Thanks, Adrian -- Adrian Farrel (ISE), rfc-ise@rfc-editor.org
- [Json] Publishing draft-ucarion-json-type-definit… RFC ISE (Adrian Farrel)