IETF Logo Mail Archive

Re: [Jsonpath] Milestones changed for jsonpath WG

Carsten Bormann <cabo@tzi.org> Mon, 02 October 2023 04:48 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: jsonpath@ietfa.amsl.com
Delivered-To: jsonpath@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9041EC15199A for <jsonpath@ietfa.amsl.com>; Sun, 1 Oct 2023 21:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofxAbW_uWFWB for <jsonpath@ietfa.amsl.com>; Sun, 1 Oct 2023 21:48:00 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [134.102.50.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 406F4C14CE2E for <jsonpath@ietf.org>; Sun, 1 Oct 2023 21:47:58 -0700 (PDT)
Received: from smtpclient.apple (eduroam-pool10-475.wlan.uni-bremen.de [134.102.91.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4RzT3H2TPMzDCbK; Mon, 2 Oct 2023 06:47:55 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <726403323.4690547.1696220785359@mail.yahoo.com>
Date: Mon, 02 Oct 2023 06:47:44 +0200
Cc: Tim Bray <tbray@textuality.com>, jsonpath@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <16A8A6F3-8ADA-440D-9DB4-3B30E5BDFCFD@tzi.org>
References: <169591192550.2448.18153131197735976579@ietfa.amsl.com> <1454096005.4050280.1696206693908@mail.yahoo.com> <CAHBU6itHdwcJ_7H7_vpbwzGhrzxySvOrDCgyzynyNogU5S7u6w@mail.gmail.com> <726403323.4690547.1696220785359@mail.yahoo.com>
To: Greg Dennis <gregsdennis@yahoo.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/73iXv6cWMU9sjLQBK5NvMSKp2nA>
Subject: Re: [Jsonpath] Milestones changed for jsonpath WG
X-BeenThere: jsonpath@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A summary description of the list to be included in the table on this page <jsonpath.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jsonpath/>
List-Post: <mailto:jsonpath@ietf.org>
List-Help: <mailto:jsonpath-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jsonpath>, <mailto:jsonpath-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Oct 2023 04:48:04 -0000

On 2. Oct 2023, at 06:26, Greg Dennis <gregsdennis=40yahoo.com@dmarc.ietf.org> wrote:
> 
> So does that mean we have an official spec? 

Both jsonpath-base and iregexp are approved documents.

(The milestone updates this is replying to are about events that already have happened earlier: submission of the documents to IESG, i.e., after the Working Group Last Call procedure completed.)

> I don't see an RFC number or anything.

You can see the status here:

https://datatracker.ietf.org/doc/search?name=jsonpath&sort=&rfcs=on&activedrafts=on

iregexp is in AUTH48, i.e., the RFC editor has completed their work and has had feedback with the authors with respect to the edits they have applied.  (Actually, it should be in AUTH48-DONE now; we are waiting for Murray’s final go ahead only.)  We already know the RFC number, but the RFC is not published yet; I’d expect this to happen approximately this week.

Jsonpath-base is in EDIT, i.e., the RFC editor is editing it.  This will probably take a couple of months; I’d expect it to reach AUTH48 by December, and it probably will be published this year.

The RFC editor page for the “cluster” of documents is at:

https://www.rfc-editor.org/auth48/C490
And yes, that cluster includes the first RFC-to-be that is relying on JSONPath, too!

If you want to see the status of all documents currently being processed by the RFC editor in their various states, please look here:
https://www.rfc-editor.org/current_queue.php#draft-ietf-jsonpath-base

Grüße, Carsten

v2.23.0 | Report a Bug | By Email