[Extra] RFC 8457 on IMAP "$Important" Keyword and "\Important" Special-Use Attribute
rfc-editor@rfc-editor.org Fri, 07 September 2018 00:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC00C130F76; Thu, 6 Sep 2018 17:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 eV2sD0EYkDkx; Thu, 6 Sep 2018 17:14:33 -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 C6C45130FBD; Thu, 6 Sep 2018 17:14:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AB894B8152B; Thu, 6 Sep 2018 17:14:32 -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, extra@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180907001432.AB894B8152B@rfc-editor.org>
Date: Thu, 06 Sep 2018 17:14:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/ZlOT9Vx0WeEJ7uftAMLIa2h32Bo>
Subject: [Extra] RFC 8457 on IMAP "$Important" Keyword and "\Important" Special-Use Attribute
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Sep 2018 00:14:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8457
Title: IMAP "$Important" Keyword and "Important"
Special-Use Attribute
Author: B. Leiba, Ed.
Status: Standards Track
Stream: IETF
Date: September 2018
Mailbox: barryleiba@computer.org
Pages: 11
Characters: 22542
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-extra-specialuse-important-04.txt
URL: https://www.rfc-editor.org/info/rfc8457
DOI: 10.17487/RFC8457
RFC 6154 created an IMAP special-use LIST extension and defined an
initial set of attributes. This document defines a new attribute,
"Important", and establishes a new IANA registry for IMAP folder
attributes, which include the attributes defined in RFCs 5258, 3501,
and 6154. This document also defines a new IMAP keyword,
"$Important", and registers it in the registry defined in RFC 5788.
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