[Jmap] RFC 9425 on JSON Meta Application Protocol (JMAP) for Quotas

rfc-editor@rfc-editor.org Wed, 21 June 2023 05:58 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 345B6C14CE30; Tue, 20 Jun 2023 22:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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 QNZvuyBdA2Hy; Tue, 20 Jun 2023 22:57:58 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 EC658C151087; Tue, 20 Jun 2023 22:57:58 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id BD2F96AB14; Tue, 20 Jun 2023 22:57:58 -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, jmap@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230621055758.BD2F96AB14@rfcpa.amsl.com>
Date: Tue, 20 Jun 2023 22:57:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/2Ur7u5fwN385daXg7oAP-5XMlIA>
Subject: [Jmap] RFC 9425 on JSON Meta Application Protocol (JMAP) for Quotas
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jun 2023 05:58:03 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9425

        Title:      JSON Meta Application Protocol (JMAP) 
                    for Quotas 
        Author:     R. Cordier, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2023
        Mailbox:    rcordier@linagora.com
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-jmap-quotas-12.txt

        URL:        https://www.rfc-editor.org/info/rfc9425

        DOI:        10.17487/RFC9425

This document specifies a data model for handling quotas on accounts
with a server using the JSON Meta Application Protocol (JMAP).

This document is a product of the JSON Mail Access Protocol 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