RFC 8508 on IMAP REPLACE Extension

rfc-editor@rfc-editor.org Fri, 04 January 2019 19:58 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5945D130E85; Fri, 4 Jan 2019 11:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 GiyUurza4Q2r; Fri, 4 Jan 2019 11:58:39 -0800 (PST)
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 7004F130E8E; Fri, 4 Jan 2019 11:58:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7C933B81AAE; Fri, 4 Jan 2019 11:58:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8508 on IMAP REPLACE Extension
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, extra@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190104195830.7C933B81AAE@rfc-editor.org>
Date: Fri, 04 Jan 2019 11:58:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/THA9cTKV8AyKSdEUE_iMCncPO5k>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2019 19:58:42 -0000

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

        
        RFC 8508

        Title:      IMAP REPLACE Extension 
        Author:     S. Brandt
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2019
        Mailbox:    stujenerin@aol.com
        Pages:      11
        Characters: 21984
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-extra-imap-replace-03.txt

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

        DOI:        10.17487/RFC8508

This document defines an IMAP extension that can be used to replace
an existing message in a message store with a new message.  Message
replacement is a common operation for clients that automatically save
drafts or notes as a user composes them.

This document is a product of the Email mailstore and eXtensions To Revise or Amend 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