[Jmap] RFC 9219 on S/MIME Signature Verification Extension to the JSON Meta Application Protocol (JMAP)

rfc-editor@rfc-editor.org Tue, 05 April 2022 19:02 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 0D1CD3A23D0; Tue, 5 Apr 2022 12:02:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 dqfIM5hXs2HW; Tue, 5 Apr 2022 12:01:57 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12B343A23B2; Tue, 5 Apr 2022 12:01:47 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 7D0873BA9D; Tue, 5 Apr 2022 12:01:46 -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: <20220405190146.7D0873BA9D@rfcpa.amsl.com>
Date: Tue, 05 Apr 2022 12:01:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/YR0IzB2F3tBOwn1tq6vZnlmu3vI>
Subject: [Jmap] RFC 9219 on S/MIME Signature Verification Extension to the JSON Meta Application Protocol (JMAP)
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, 05 Apr 2022 19:02:11 -0000

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

        
        RFC 9219

        Title:      S/MIME Signature Verification Extension to 
                    the JSON Meta Application Protocol (JMAP) 
        Author:     A. Melnikov
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2022
        Mailbox:    Alexey.Melnikov@isode.com
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

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

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

        DOI:        10.17487/RFC9219

This document specifies an extension to "The JSON Meta Application
Protocol (JMAP) for Mail" (RFC 8621) for returning the S/MIME
signature verification status.

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