[Jmap] RFC 9007 on Handling Message Disposition Notification with the JSON Meta Application Protocol (JMAP)

rfc-editor@rfc-editor.org Tue, 23 March 2021 04:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 730AF3A1DA0; Mon, 22 Mar 2021 21:56:08 -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 B_wc0Z8rnh25; Mon, 22 Mar 2021 21:56:03 -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 80F213A1D98; Mon, 22 Mar 2021 21:56:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CB03DF40755; Mon, 22 Mar 2021 21:55:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20210323045559.CB03DF40755@rfc-editor.org>
Date: Mon, 22 Mar 2021 21:55:59 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/keOR_9StpZSMIwMB21s8ZYOqOo0>
Subject: [Jmap] =?utf-8?q?RFC_9007_on_Handling_Message_Disposition_Notifi?= =?utf-8?q?cation_with_the_JSON_Meta_Application_Protocol_=28JMAP=29?=
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Mar 2021 04:56:09 -0000

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

        
        RFC 9007

        Title:      Handling Message Disposition Notification with 
                    the JSON Meta Application Protocol (JMAP) 
        Author:     R. Ouazana, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2021
        Mailbox:    rouazana@linagora.com
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-jmap-mdn-17.txt

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

        DOI:        10.17487/RFC9007

This document specifies a data model for handling Message Disposition
Notifications (MDNs) (see RFC 8098) in the JSON Meta Application
Protocol (JMAP) (see RFCs 8620 and 8621).

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