[Jsonpath] RFC 9485 on I-Regexp: An Interoperable Regular Expression Format
rfc-editor@rfc-editor.org Fri, 13 October 2023 22:31 UTC
Return-Path: <wwwrun@rfcpa.amsl.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 72162C14CE4B; Fri, 13 Oct 2023 15:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, 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 CGLqBpT5yfIz; Fri, 13 Oct 2023 15:31:49 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (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 31DD2C14F75F; Fri, 13 Oct 2023 15:31:49 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 088FE13BB4C3; Fri, 13 Oct 2023 15:31:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, jsonpath@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231013223149.088FE13BB4C3@rfcpa.amsl.com>
Date: Fri, 13 Oct 2023 15:31:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jsonpath/pD1Nbh1F5aKi7LIlkUBPntIZvEo>
Subject: [Jsonpath] RFC 9485 on I-Regexp: An Interoperable Regular Expression Format
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: Fri, 13 Oct 2023 22:31:53 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9485 Title: I-Regexp: An Interoperable Regular Expression Format Author: C. Bormann, T. Bray Status: Standards Track Stream: IETF Date: October 2023 Mailbox: cabo@tzi.org, tbray@textuality.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-jsonpath-iregexp-08.txt URL: https://www.rfc-editor.org/info/rfc9485 DOI: 10.17487/RFC9485 This document specifies I-Regexp, a flavor of regular expression that is limited in scope with the goal of interoperation across many different regular expression libraries. This document is a product of the JSON Path Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC