IETF Logo Mail Archive

Re: [Jsonpath] Milestones changed for jsonpath WG

Tim Bray <tbray@textuality.com> Mon, 02 October 2023 06:34 UTC

Return-Path: <tbray@textuality.com>
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 1F0C5C1516EA for <jsonpath@ietfa.amsl.com>; Sun, 1 Oct 2023 23:34:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=textuality.com
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 U62AWjb6bw0M for <jsonpath@ietfa.amsl.com>; Sun, 1 Oct 2023 23:33:59 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 20F13C14CE22 for <jsonpath@ietf.org>; Sun, 1 Oct 2023 23:33:58 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-53447d0241eso14849797a12.3 for <jsonpath@ietf.org>; Sun, 01 Oct 2023 23:33:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality.com; s=google; t=1696228437; x=1696833237; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qpUfi0hUohTzV3yRgYgXGiAe6Nt8SXQ1YPFiQVG16gM=; b=YZgegMVWbm4RhLShVZdcvf/M7WSci2D6Tewr7+1NUKOY2fjzusI1NQCJiCy7ty3z1k xmCOchb5jsfg8mDNWtqJ320OWb6ro4gQxN0TnDmW5OBW8uRuVyMxm/C2HyJhy0SqItqM 5qE2ly3BTHQM6/3ZvOjPs1EPOk18FetG9kka4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696228437; x=1696833237; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qpUfi0hUohTzV3yRgYgXGiAe6Nt8SXQ1YPFiQVG16gM=; b=WR5o0W1cMoCiivj56Deo9YSblxZ3YgwqLpPkYVHOkgV7e89kPtDPuwpokZICClVyDE IrjpO5WAZ5VYqaK3wIbcF0Ieqmyyow7vZWWGyqYQeaG9UW5gJe0mJ2yc5DV+uo4m1dFe IFC81YVMPuCrAAkvqpiR4gOhGLaFIodyj2+oEnvJIIgap9ulxk42ef+L8dXsubIhJN6P BLN9PMPTdeF1qgAJvLU0AAcmtY3rZnieKyQzdI0FEYY3Ga2dFmSOUlEh2otKOr5jy/lH tiCYk7FD05MXP5MnbFva6IFewJsHynaMCvh5md3fPNQrPvfASQxQzuWfMdpQLEkH8XUU Q3kQ==
X-Gm-Message-State: AOJu0Yyyc3gLqRxfBS/IGBDXNu18RhjZOSDBH6wuqbuRnyh8x1gJx3pA pJEUJ6e77VllwxA9x5MpeRqRy9vSBQ9HcU16mz4G5Q==
X-Google-Smtp-Source: AGHT+IE4nnLha5CFleQcKwKPmdPUhW6gob0ruKSV/6OBpfZaW7eQSt8HvgPcGKhEmvki2IRvDT67Ag+wbehpXwOAasQ=
X-Received: by 2002:aa7:cd15:0:b0:52b:db31:3c48 with SMTP id b21-20020aa7cd15000000b0052bdb313c48mr9089382edw.0.1696228436752; Sun, 01 Oct 2023 23:33:56 -0700 (PDT)
MIME-Version: 1.0
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> <16A8A6F3-8ADA-440D-9DB4-3B30E5BDFCFD@tzi.org> <CANH0GbKqJSWOxb09jj0DMDh=_eW4vy2zLeHdJs9MfrR_wutWyw@mail.gmail.com>
In-Reply-To: <CANH0GbKqJSWOxb09jj0DMDh=_eW4vy2zLeHdJs9MfrR_wutWyw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Sun, 01 Oct 2023 23:33:45 -0700
Message-ID: <CAHBU6ivXAwGcPjCc5mfC070UuHyDctZSOQ+HA3e_yBbMqnXMnA@mail.gmail.com>
To: Glyn Normington <glyn.normington.work@gmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, Greg Dennis <gregsdennis@yahoo.com>, jsonpath@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006e504c0606b5f5f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/cHnKs-qYYZuZWPvd8N_MDyH5m40>
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 06:34:04 -0000

I'm generally pleased with their work. They provide exhaustive diffs and
highlight any changes of any import. Their job is to add polish and
professionalism. On occasions where I've objected to a change, they've
deferred.

On Sun, Oct 1, 2023, 11:19 p.m. Glyn Normington <
glyn.normington.work@gmail.com> wrote:

> Hi Carsten
>
> Thanks for that excellent summary for us uninitiated! It will be
> fascinating to see what changes the RFC Editor makes (proposes?) with a
> fresh pair of eyes.
>
> Regards,
> Glyn
>
> On Mon, 2 Oct 2023, 06:48 Carsten Bormann, <cabo@tzi.org> wrote:
>
>> 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
>>
>> --
>> JSONpath mailing list
>> JSONpath@ietf.org
>> https://www.ietf.org/mailman/listinfo/jsonpath
>>
>

v2.23.0 | Report a Bug | By Email