draft-ietf-extra-specialuse-important-03.txt   draft-ietf-extra-specialuse-important-04.txt 
Network Working Group B. Leiba, Ed. Network Working Group B. Leiba, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track May 01, 2018 Intended status: Standards Track June 07, 2018
Expires: October 31, 2018 Expires: December 07, 2018
IMAP $Important Keyword and \Important Special-Use Attribute IMAP $Important Keyword and \Important Special-Use Attribute
draft-ietf-extra-specialuse-important-03 draft-ietf-extra-specialuse-important-04
Abstract Abstract
RFC 6154 created an IMAP Special-Use LIST extension and defined an RFC 6154 created an IMAP Special-Use LIST extension and defined an
initial set of attributes. This document defines a new attribute, initial set of attributes. This document defines a new attribute,
"\Important", and establishes a new IANA registry for IMAP folder "\Important", and establishes a new IANA registry for IMAP folder
attributes, registering the attributes defined in RFCs 3348, 3501, attributes, registering the attributes defined in RFCs 5258, 3501,
and 6154. This document also defines a new IMAP keyword, and 6154. This document also defines a new IMAP keyword,
"$Important", and registers it in the registry defined in RFC 5788. "$Important", and registers it in the registry defined in RFC 5788.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 31, 2018. This Internet-Draft will expire on December 07, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (http://trustee.ietf.org/ Provisions Relating to IETF Documents (http://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 2, line 46 skipping to change at page 2, line 46
that are considered important for the user, by some externally that are considered important for the user, by some externally
defined criteria. defined criteria.
o Registers the "$Important" keyword in the IMAP Keywords registry. o Registers the "$Important" keyword in the IMAP Keywords registry.
o Defines a new special-use attribute, "\Important", to designate a o Defines a new special-use attribute, "\Important", to designate a
mailbox that will hold messages that are considered important for mailbox that will hold messages that are considered important for
the user, by some externally defined criteria. the user, by some externally defined criteria.
o Creates a registry for IMAP mailbox attributes and registers the o Creates a registry for IMAP mailbox attributes and registers the
new attribute and those defined in [RFC3348], [RFC3501], and new attribute and those defined in [RFC5258], [RFC3501], and
[RFC6154]. [RFC6154].
1.1. Conventions used in this document 1.1. Conventions used in this document
In examples, "C:" indicates lines sent by a client that is connected In examples, "C:" indicates lines sent by a client that is connected
to a server. "S:" indicates lines sent by the server to the client. to a server. "S:" indicates lines sent by the server to the client.
2. Definition of the '$Important' Message Keyword 2. Definition of the '$Important' Message Keyword
The "$Important" keyword is a signal that a message is likely The "$Important" keyword is a signal that a message is likely
important to the user. The keyword is generally expected to be set important to the user. The keyword is generally expected to be set
skipping to change at page 4, line 24 skipping to change at page 4, line 24
created with the "\Important" attribute on a server that advertises created with the "\Important" attribute on a server that advertises
the "CREATE-SPECIAL-USE" capability string. the "CREATE-SPECIAL-USE" capability string.
C: t1 CREATE "Important Messages" (USE (\Important)) C: t1 CREATE "Important Messages" (USE (\Important))
S: t1 OK Mailbox created S: t1 OK Mailbox created
The following example is similar to the previous one, but the server The following example is similar to the previous one, but the server
is not able to assign the \Important attribute to the new mailbox. is not able to assign the \Important attribute to the new mailbox.
C: t1 CREATE "Important Messages" (USE (\Important)) C: t1 CREATE "Important Messages" (USE (\Important))
S: t1 NO [USEATTR] Mailbox not created; an \Important mailbox already exists S: t1 NO [USEATTR] Not created; an \Important mailbox already exists
The following example is similar to the previous one, but the server The following example is similar to the previous one, but the server
does not support this extension. does not support this extension.
C: t1 CREATE "Important Messages" (USE (\Important)) C: t1 CREATE "Important Messages" (USE (\Important))
S: t1 NO [USEATTR] Mailbox not created; unsupported use \Important S: t1 NO [USEATTR] Mailbox not created; unsupported use \Important
In both of the failure-mode examples, the "USEATTR" response code In both of the failure-mode examples, the "USEATTR" response code
lets the client know that the problem is in the "USE" parameters. lets the client know that the problem is in the "USE" parameters.
Note that the same response code is given in both cases, and the Note that the same response code is given in both cases, and the
skipping to change at page 7, line 23 skipping to change at page 7, line 23
accepted in one of two ways: accepted in one of two ways:
1. For registrations requested in an IETF consensus document, the 1. For registrations requested in an IETF consensus document, the
registration policy will be IETF Review, and the request will be registration policy will be IETF Review, and the request will be
made in the IANA Considerations section of the document, giving made in the IANA Considerations section of the document, giving
the requested values for each of the fields. the requested values for each of the fields.
2. For other registrations, the policy will be Expert Review policy 2. For other registrations, the policy will be Expert Review policy
(see Section 6.2.1), and the request will be made by sending (see Section 6.2.1), and the request will be made by sending
email to IANA asking for a new IMAP Mailbox Name Attribute and email to IANA asking for a new IMAP Mailbox Name Attribute and
giving the requested values for each of the fields. giving the requested values for each of the fields. While a
formal specification is not required, the reference document
should provide a description of the proposed attribute sufficient
for building interoperable implementations. An Informational RFC
(submitted through the IETF or Independent stream) is a fine way
to publish a reference document (see also Section 6.2.1).
6.2.1. Instructions to the Designated Expert 6.2.1. Instructions to the Designated Expert
The expert reviewer, who will be designated by the IESG, is expected The expert reviewer, who will be designated by the IESG, is expected
to provide only a general review of the requested registration, to provide only a general review of the requested registration,
checking that the reference and description are adequate for checking that the reference and description are adequate for
understanding the intent of the registered attribute. Efforts should understanding the intent of the registered attribute. Efforts should
also be made to generalize the intent of an attribute so that also be made to generalize the intent of an attribute so that
multiple implementations with the same requirements may reuse multiple implementations with the same requirements may reuse
existing attributes. Except for this check, this is intended to be existing attributes. Except for this check, this is intended to be
skipping to change at page 9, line 39 skipping to change at page 9, line 39
Changes in draft-iceman-imap-specialuse-important-02 Changes in draft-iceman-imap-specialuse-important-02
o Added the definition and registration of $Important. o Added the definition and registration of $Important.
o Noted that \Important might be implemented as a virtual collection o Noted that \Important might be implemented as a virtual collection
of $Important messages. of $Important messages.
Changes in draft-iceman-imap-specialuse-important-01 Changes in draft-iceman-imap-specialuse-important-01
o Expanded the new registry to all mailbox name attributes, and o Expanded the new registry to all mailbox name attributes, and
added the attributes from 3501 and 3348 (suggested by Alexey). added the attributes from 3501 and 5258 (suggested by Alexey).
This also adds those two documents to the "updates" list. This also adds those two documents to the "updates" list.
o Recorded Cyrus's suggestion to define $Important. o Recorded Cyrus's suggestion to define $Important.
8. Contributors 8. Contributors
The following author was an original contributor to this document in The following author was an original contributor to this document in
addition to the editor. addition to the editor.
Eric "Iceman" Eric "Iceman"
skipping to change at page 10, line 25 skipping to change at page 10, line 25
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, <https://www RFC 8126, DOI 10.17487/RFC8126, June 2017, <https://www
.rfc-editor.org/info/rfc8126>. .rfc-editor.org/info/rfc8126>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-jmap-mail] [I-D.ietf-jmap-mail]
Jenkins, N., "JMAP for Mail", Internet-Draft draft-ietf- Jenkins, N., "JMAP for Mail", Internet-Draft draft-ietf-
jmap-mail-04, March 2018. jmap-mail-04, March 2018.
[RFC3348] Gahrns, M. and R. Cheng, "The Internet Message Action [RFC5258] Leiba, B. and A. Melnikov, "Internet Message Access
Protocol (IMAP4) Child Mailbox Extension", RFC 3348, July Protocol version 4 - LIST Command Extensions", RFC 5258,
2002. DOI 10.17487/RFC5258, June 2008, <https://www.rfc-
editor.org/info/rfc5258>.
[RFC5788] Melnikov, A. and D. Cridland, "IMAP4 Keyword Registry", [RFC5788] Melnikov, A. and D. Cridland, "IMAP4 Keyword Registry",
RFC 5788, March 2010. RFC 5788, March 2010.
Author's Address Author's Address
Barry Leiba, editor Barry Leiba, editor
Huawei Technologies Huawei Technologies
Phone: +1 646 827 0648 Phone: +1 646 827 0648
 End of changes. 9 change blocks. 
12 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/