Registration of further IMAP/JMAP keywords and mailbox name attributes
draft-ietf-mailmaint-messageflag-mailboxattribute-14
Revision differences
Document history
| Date | Rev. | By | Action |
|---|---|---|---|
|
2026-05-29
|
14 | (System) | Updated while publishing rfc9979 (changed state to RFC, created became rfc relationship between draft-ietf-mailmaint-messageflag-mailboxattribute and RFC 9979, changed IESG state to RFC Published) |
|
2026-05-28
|
14 | (System) | RPC status changed to publisher from Awaiting Editor Assignment |
|
2026-05-26
|
14 | (System) | RPC status changed to Awaiting Editor Assignment from final_review_editor |
|
2026-05-20
|
14 | (System) | RPC status changed to final_review_editor |
|
2026-05-20
|
14 | (System) | RFC Editor state changed to In Progress from AUTH48-DONE |
|
2026-05-13
|
14 | (System) | RFC Editor state changed to AUTH48-DONE from AUTH48 |
|
2026-05-07
|
14 | (System) | RFC Editor state changed to AUTH48 |
|
2026-05-06
|
14 | (System) | RFC Editor state changed to RFC-EDITOR from EDIT |
|
2026-01-07
|
14 | (System) | RFC Editor state changed to EDIT from AUTH |
|
2026-01-05
|
14 | (System) | IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor |
|
2026-01-05
|
14 | (System) | IANA Action state changed to Waiting on RFC Editor from In Progress |
|
2026-01-05
|
14 | (System) | IANA Action state changed to In Progress from Waiting on Authors |
|
2026-01-05
|
14 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-14.txt |
|
2026-01-05
|
14 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2026-01-05
|
14 | Daniel Eggert | Uploaded new revision |
|
2025-12-22
|
13 | (System) | IANA Action state changed to Waiting on Authors from In Progress |
|
2025-12-18
|
13 | (System) | RFC Editor state changed to AUTH from EDIT |
|
2025-12-18
|
13 | (System) | RFC Editor state changed to EDIT |
|
2025-12-18
|
13 | (System) | IESG state changed to RFC Ed Queue from Approved-announcement sent |
|
2025-12-18
|
13 | (System) | Announcement was received by RFC Editor |
|
2025-12-18
|
13 | (System) | IANA Action state changed to In Progress |
|
2025-12-18
|
13 | Morgan Condie | IESG state changed to Approved-announcement sent from Approved-announcement to be sent |
|
2025-12-18
|
13 | Morgan Condie | IESG has approved the document |
|
2025-12-18
|
13 | Morgan Condie | Closed "Approve" ballot |
|
2025-12-18
|
13 | Morgan Condie | Ballot approval text was generated |
|
2025-12-18
|
13 | (System) | Removed all action holders (IESG state changed) |
|
2025-12-18
|
13 | Andy Newton | IESG state changed to Approved-announcement to be sent from IESG Evaluation::AD Followup |
|
2025-12-17
|
13 | Sabrina Tanamal | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
|
2025-12-16
|
13 | Andy Newton | Email sent to IANA to confirm status is no longer "Review Needed". |
|
2025-12-04
|
13 | Roman Danyliw | [Ballot comment] (revised ballot for -13) Thank you to Meral Shirazipour for the GENART review. Thank you for addressing my DISCUSS feedback. ** For the … [Ballot comment] (revised ballot for -13) Thank you to Meral Shirazipour for the GENART review. Thank you for addressing my DISCUSS feedback. ** For the responsible AD and MAILMAINT WG Chairs, the charter text says “milestones will be used to track all approved work, including during chartering and rechartering.” However, this document and none of the adopted document have milestones. |
|
2025-12-04
|
13 | Roman Danyliw | [Ballot Position Update] Position for Roman Danyliw has been changed to No Objection from Discuss |
|
2025-11-30
|
13 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
|
2025-11-30
|
13 | Neil Jenkins | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-13.txt |
|
2025-11-30
|
13 | (System) | New version approved |
|
2025-11-30
|
13 | (System) | Request for posting confirmation emailed to previous authors: Daniel Eggert , Neil Jenkins |
|
2025-11-30
|
13 | Neil Jenkins | Uploaded new revision |
|
2025-11-24
|
12 | Amanda Baber | IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed |
|
2025-11-23
|
12 | Paul Wouters | [Ballot comment] Thanks for addressing my concerns. I have updated my ballot to No Objection. |
|
2025-11-23
|
12 | Paul Wouters | [Ballot Position Update] Position for Paul Wouters has been changed to No Objection from Discuss |
|
2025-11-23
|
12 | (System) | Changed action holders to Andy Newton (IESG state changed) |
|
2025-11-23
|
12 | (System) | Sub state has been changed to AD Followup from Revised I-D Needed |
|
2025-11-23
|
12 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA - Not OK |
|
2025-11-23
|
12 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-12.txt |
|
2025-11-23
|
12 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-11-23
|
12 | Daniel Eggert | Uploaded new revision |
|
2025-11-20
|
11 | (System) | Changed action holders to Neil Jenkins, Daniel Eggert (IESG state changed) |
|
2025-11-20
|
11 | Morgan Condie | IESG state changed to IESG Evaluation::Revised I-D Needed from IESG Evaluation |
|
2025-11-20
|
11 | Roman Danyliw | [Ballot discuss] (updated ballot) ** "IANA NOT OK" status, "What should the scope be set to for the keywords: $MailFlagBit0. $MailFlagBit1, and $MailFlagBit2"? Please document … [Ballot discuss] (updated ballot) ** "IANA NOT OK" status, "What should the scope be set to for the keywords: $MailFlagBit0. $MailFlagBit1, and $MailFlagBit2"? Please document the intended scope for these registry entries. |
|
2025-11-20
|
11 | Roman Danyliw | [Ballot Position Update] Position for Roman Danyliw has been changed to Discuss from No Objection |
|
2025-11-20
|
11 | Éric Vyncke | [Ballot Position Update] New position, No Objection, has been recorded for Éric Vyncke |
|
2025-11-19
|
11 | Mike Bishop | [Ballot comment] Thanks for this document -- it's useful to document conventions that have emerged across vendors. The title and text imply that these keywords … [Ballot comment] Thanks for this document -- it's useful to document conventions that have emerged across vendors. The title and text imply that these keywords apply equally to IMAP and JMAP, but the Introduction never mentions JMAP. Please consider updating the registry reference to the actual registry names (with "IMAP/JMAP") and adding an explicit statement that IMAP and JMAP both use these registries. In general, "SHOULD consider" isn't a useful phrase to find in an RFC, and Section 3.2 is no exception. If we think a certain behavior is generally useful but optional, this is simply "SHOULD." In Section 3, the keywords aren't defined in Section 9.1.[9-11], they're merely registered there. The definitions of them are here in Section 3. In Section 7.6, I'm slightly more concerned about this threat than the text suggests. While there are certainly all manners of harm one can do with a compromised e-mail account, this seems like one of the few where the effects would continue to happen even after control of the account is recovered. I support Paul's DISCUSS. |
|
2025-11-19
|
11 | Mike Bishop | [Ballot Position Update] New position, No Objection, has been recorded for Mike Bishop |
|
2025-11-18
|
11 | Paul Wouters | [Ballot discuss] While most of my questions are comments, I find one issue raises to a DISCUSS level: for $istrusted: It … [Ballot discuss] While most of my questions are comments, I find one issue raises to a DISCUSS level: for $istrusted: It SHOULD NOT be used for messages that have only passed standard authentication mechanisms like SPF, DKIM, or DMARC. I feel this should really be a MUST NOT. Why is this set at SHOULD NOT level? What would be an acceptable exception for using $istrusted? |
|
2025-11-18
|
11 | Paul Wouters | [Ballot comment] Servers MAY clear these flag color keywords when a client clears the \Flagged system flag. Why is this a … [Ballot comment] Servers MAY clear these flag color keywords when a client clears the \Flagged system flag. Why is this a MAY and not a SHOULD ? The $hasattachment and $hasnoattachment keywords are mutually exclusive. A message SHOULD NOT have both keywords set simultaneously. Why is this not a MUST NOT ? Same for the $memo and $hasmemo keywords ? |
|
2025-11-18
|
11 | Paul Wouters | [Ballot Position Update] New position, Discuss, has been recorded for Paul Wouters |
|
2025-11-18
|
11 | (System) | IANA Review state changed to IANA - Not OK from Version Changed - Review Needed |
|
2025-11-18
|
11 | Andy Newton | Changed consensus to Yes from Unknown |
|
2025-11-18
|
11 | Ketan Talaulikar | [Ballot Position Update] New position, No Objection, has been recorded for Ketan Talaulikar |
|
2025-11-17
|
11 | Deb Cooley | [Ballot comment] Thanks to Rich Salz for their secdir review Why not MUST/MUST NOT? In many places in Section 3-8 there are instances of SHOULD/SHOULD … [Ballot comment] Thanks to Rich Salz for their secdir review Why not MUST/MUST NOT? In many places in Section 3-8 there are instances of SHOULD/SHOULD NOT where it isn't clear under what circumstances one might ignore the SHOULD or SHOULD NOT. Either provide an example of why one might choose to ignore the statement, or perhaps it should be a MUST or MUST NOT. For example in Section 4, last sentence, it seems like MUST NOT would be a reasonable choice. Where in Section 5.2, para 3, the 'SHOULD present these messages differently' might depend on the UI of the client. Section 10: I recognize the updates that have been made wrt the secdir review, and I agree that it makes the specification clearer. Just one more tweak: It would be better to have the security caution for '$muted' be in the section where it is specified, Section 7.6. While I agree it is repetitive to have this in both 7.6 and 9.14, one might argue that an implementer/integrator is more likely to read Section 7.6, where the rest of the requirements are listed. |
|
2025-11-17
|
11 | Deb Cooley | [Ballot Position Update] New position, No Objection, has been recorded for Deb Cooley |
|
2025-11-17
|
11 | Jim Guichard | [Ballot Position Update] New position, No Objection, has been recorded for Jim Guichard |
|
2025-11-16
|
11 | Roman Danyliw | [Ballot comment] Thank you to Meral Shirazipour for the GENART review. ** For the responsible AD and MAILMAINT WG Chairs, the charter text says “milestones … [Ballot comment] Thank you to Meral Shirazipour for the GENART review. ** For the responsible AD and MAILMAINT WG Chairs, the charter text says “milestones will be used to track all approved work, including during chartering and rechartering.” However, this document and none of the adopted document have milestones. ** Section 9.2. Editorial. The following 3 IMAP/JMAP mailbox name attributes are registered in the IMAP/JMAP Mailbox Name Attributes Registry, as established in [RFC8457]. The name of the registry is “IMAP Mailbox Name Attributes” |
|
2025-11-16
|
11 | Roman Danyliw | [Ballot Position Update] New position, No Objection, has been recorded for Roman Danyliw |
|
2025-11-16
|
11 | Gorry Fairhurst | [Ballot Position Update] New position, No Objection, has been recorded for Gorry Fairhurst |
|
2025-11-13
|
11 | Mohamed Boucadair | [Ballot comment] Hi Neil and Daniel, Thank you for the effort put into this specification. The description of the keywords/attributes is clear and well articulated. … [Ballot comment] Hi Neil and Daniel, Thank you for the effort put into this specification. The description of the keywords/attributes is clear and well articulated. I found the use of the normative language a bit concerning in some places, mainly the use of SHOULDs. I suspect this is to accommodate existing implementations. No? Cheers, Med |
|
2025-11-13
|
11 | Mohamed Boucadair | [Ballot Position Update] New position, No Objection, has been recorded for Mohamed Boucadair |
|
2025-11-12
|
11 | Gunter Van de Velde | [Ballot Position Update] New position, No Objection, has been recorded for Gunter Van de Velde |
|
2025-10-23
|
11 | Erik Kline | [Ballot Position Update] New position, No Objection, has been recorded for Erik Kline |
|
2025-10-21
|
11 | Morgan Condie | Placed on agenda for telechat - 2025-11-20 |
|
2025-10-21
|
11 | Andy Newton | Ballot has been issued |
|
2025-10-21
|
11 | Andy Newton | [Ballot Position Update] New position, Yes, has been recorded for Andy Newton |
|
2025-10-21
|
11 | Andy Newton | Created "Approve" ballot |
|
2025-10-21
|
11 | Andy Newton | IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead |
|
2025-10-21
|
11 | Andy Newton | Ballot writeup was changed |
|
2025-10-20
|
11 | (System) | IANA Review state changed to Version Changed - Review Needed from IANA OK - Actions Needed |
|
2025-10-20
|
11 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-11.txt |
|
2025-10-20
|
11 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-10-20
|
11 | Daniel Eggert | Uploaded new revision |
|
2025-10-17
|
10 | David Dong | IANA Review state changed to IANA OK - Actions Needed from IANA - Not OK |
|
2025-10-17
|
10 | David Dong | Registrations have been approved. |
|
2025-10-17
|
10 | David Dong | IANA Experts State changed to Expert Reviews OK from Reviews assigned |
|
2025-10-16
|
10 | David Dong | IMAP and JMAP Keywords registration has been approved. |
|
2025-10-15
|
10 | David Dong | IANA Experts State changed to Reviews assigned |
|
2025-10-14
|
10 | (System) | IESG state changed to Waiting for AD Go-Ahead from In Last Call |
|
2025-10-13
|
10 | David Dong | IESG/Authors/WG Chairs: IANA has completed its review of draft-ietf-mailmaint-messageflag-mailboxattribute-10. If any part of this review is inaccurate, please let us know. IANA understands that, upon … IESG/Authors/WG Chairs: IANA has completed its review of draft-ietf-mailmaint-messageflag-mailboxattribute-10. If any part of this review is inaccurate, please let us know. IANA understands that, upon approval of this document, there are two actions which we must complete. First, in the IMAP and JMAP Keywords registry located at: https://www.iana.org/assignments/imap-jmap-keywords/ seventeen new keywords are to be registered as follows: Keyword: $notify Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that a notification should be presented for this message. Reference: [ RFC-to-be ] Keyword: $muted Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the server that the user is not interested in future replies to a particular thread Reference: [ RFC-to-be ] Keyword: $followed Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the server that the user is particularly interested in future replies to a particular thread. Reference: [ RFC-to-be ] Keyword: $memo Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that a message is a note-to-self from the user regarding another message in the same thread. Reference: [ RFC-to-be ] Keyword: $hasmemo Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that a message has an associated memo with the $memo keyword. Reference: [ RFC-to-be ] Keyword: $hasattachment Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that a message has an attachment. Reference: [ RFC-to-be ] Keyword: $hasnoattachment Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that a message does not have an attachment. Reference: [ RFC-to-be ] Keyword: $autosent Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that a message was sent automatically as a response due to a user rule or setting. Reference: [ RFC-to-be ] Keyword: $unsubscribed Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that it has unsubscribed from the thread this message is on. Reference: [ RFC-to-be ] Keyword: $canunsubscribe Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that this message has an [RFC8058]-compliant List-Unsubscribe header. Reference: [ RFC-to-be ] Keyword: $imported Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that this message was imported from another mailbox. Reference: [ RFC-to-be ] Keyword: $istrusted Type: SHARED Usage: COMMON Scope: BOTH Comments: Indicate to the client that the authenticity of the from name and email address have been verified by the server. Reference: [ RFC-to-be ] Keyword: $maskedemail Type: SHARED Usage: LIMITED Scope: BOTH Comments: Indicate to the client that the message was received via an alias created for an individual sender. Reference: [ RFC-to-be ] Keyword: $new Type: SHARED Usage: LIMITED Scope: BOTH Comments: Indicate to the client that a message should be made more prominent to the user due to a recent action. Reference: [ RFC-to-be ] Keyword: $MailFlagBit0 Type: SHARED Usage: COMMON Scope: Comments: Bit 0 part of a 3-bit bitmask that defines the color of the flag when the message has the system flag \Flagged set. See [ RFC-to-be; Section 3 ] for details. Reference: [ RFC-to-be ] Keyword: $MailFlagBit1 Type: SHARED Usage: COMMON Scope: Comments: Bit 1 part of a 3-bit bitmask that defines the color of the flag when the message has the system flag \Flagged set. See [ RFC-to-be; Section 3 ] for details. Reference: [ RFC-to-be ] Keyword: $MailFlagBit2 Type: SHARED Usage: COMMON Scope: Comments: Bit 2 part of a 3-bit bitmask that defines the color of the flag when the message has the system flag \Flagged set. See [ RFC-to-be; Section 3 ] for details. Reference: [ RFC-to-be ] IANA Question --> What should the scope be set to for the keywords: $MailFlagBit0. $MailFlagBit1, and $MailFlagBit2? As this document requests registrations in an Expert Review or Specification Required (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. This review must be completed before the document's IANA state can be changed to "IANA OK." Second, in the IMAP Mailbox Name Attributes registry located at: https://www.iana.org/assignments/imap-mailbox-name-attributes/ three new attributes are to be registered as follows: Attribute Name: Snoozed Description: Identifies the mailbox where temporarily snoozed messages are stored. Reference: [ RFC-to-be ] Usage Notes: Attribute Name: Scheduled Description: Identifies the mailbox where messages scheduled to be sent at a later time are stored. Reference: [ RFC-to-be ] Usage Notes: Attribute Name: Memos Description: Identifies the mailbox where user-created memo messages are stored. Reference: [ RFC-to-be ] Usage Notes: As this also requests registrations in an Expert Review or Specification Required (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. This review must be completed before the document's IANA state can be changed to "IANA OK." We understand that these are the only actions required to be completed upon approval of this document. NOTE: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed. For definitions of IANA review states, please see: https://datatracker.ietf.org/help/state/draft/iana-review Thank you, David Dong IANA Services Sr. Specialist |
|
2025-10-13
|
10 | (System) | IANA Review state changed to IANA - Not OK from IANA - Review Needed |
|
2025-10-11
|
10 | Meral Shirazipour | Request for IETF Last Call review by GENART Completed: Ready. Reviewer: Meral Shirazipour. Sent review to list. Submission of review completed at an earlier date. |
|
2025-10-11
|
10 | Meral Shirazipour | Request for IETF Last Call review by GENART Completed: Ready. Reviewer: Meral Shirazipour. |
|
2025-10-09
|
10 | Jiankang Yao | Request for IETF Last Call review by ARTART Completed: Ready with Nits. Reviewer: Jiankang Yao. Sent review to list. |
|
2025-10-06
|
10 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-10.txt |
|
2025-10-06
|
10 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-10-06
|
10 | Daniel Eggert | Uploaded new revision |
|
2025-10-06
|
09 | Barry Leiba | Request for IETF Last Call review by ARTART is assigned to Jiankang Yao |
|
2025-10-06
|
09 | Rich Salz | Request for IETF Last Call review by SECDIR Completed: Has Nits. Reviewer: Rich Salz. Sent review to list. |
|
2025-10-05
|
09 | Tero Kivinen | Request for IETF Last Call review by SECDIR is assigned to Rich Salz |
|
2025-10-01
|
09 | Jean Mahoney | Request for IETF Last Call review by GENART is assigned to Meral Shirazipour |
|
2025-09-30
|
09 | Morgan Condie | IANA Review state changed to IANA - Review Needed |
|
2025-09-30
|
09 | Morgan Condie | The following Last Call announcement was sent out (ends 2025-10-14): From: The IESG To: IETF-Announce CC: andy@hxr.us, draft-ietf-mailmaint-messageflag-mailboxattribute@ietf.org, fenton@bluepopcorn.net, mailmaint-chairs@ietf.org, mailmaint@ietf.org … The following Last Call announcement was sent out (ends 2025-10-14): From: The IESG To: IETF-Announce CC: andy@hxr.us, draft-ietf-mailmaint-messageflag-mailboxattribute@ietf.org, fenton@bluepopcorn.net, mailmaint-chairs@ietf.org, mailmaint@ietf.org Reply-To: last-call@ietf.org Sender: Subject: Last Call: (Registration of further IMAP/JMAP keywords and mailbox name attributes) to Informational RFC The IESG has received a request from the Mail Maintenance WG (mailmaint) to consider the following document: - 'Registration of further IMAP/JMAP keywords and mailbox name attributes' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2025-10-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document defines a number of keywords and mailbox name attributes that have been in use across different server and client implementations. It defines the intended use of these keywords and mailbox name attributes. This document registers all of these with IANA to avoid name collisions. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-mailmaint-messageflag-mailboxattribute/ No IPR declarations have been submitted directly on this I-D. |
|
2025-09-30
|
09 | Morgan Condie | IESG state changed to In Last Call from Last Call Requested |
|
2025-09-30
|
09 | Andy Newton | Last call was requested |
|
2025-09-30
|
09 | Andy Newton | Last call announcement was generated |
|
2025-09-30
|
09 | Andy Newton | Ballot approval text was generated |
|
2025-09-30
|
09 | Andy Newton | Ballot writeup was generated |
|
2025-09-30
|
09 | Andy Newton | IESG state changed to Last Call Requested from AD Evaluation |
|
2025-09-28
|
09 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-09.txt |
|
2025-09-28
|
09 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-09-28
|
09 | Daniel Eggert | Uploaded new revision |
|
2025-09-24
|
08 | Andy Newton | IESG state changed to AD Evaluation from Publication Requested |
|
2025-09-13
|
08 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-08.txt |
|
2025-09-13
|
08 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-09-13
|
08 | Daniel Eggert | Uploaded new revision |
|
2025-08-28
|
07 | Ken Murchison | Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach … Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? This document describes existing practice in order to add new IMAP/JMAP keywords and mailbox attributes to the appropriate IANA registries. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? There was a moderate amoount of discussion, primarily as a result of WG last call and a second last call issued as a result of document changes. None of the consensus was particularly rough. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) Much the opposite; as noted above, there has been very little comment. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as RFC 7942 recommends) or elsewhere (where)? The document is informational. It has been written to document existing usage by some implementations, but doesnÕt cite those implementations. Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The document addresses keywords and attributes that are internal to IMAP and JMAP. No external reviews are thought to be needed. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. No formal expert review criteria are applicable. 7. If the document contains a YANG module, has the final version of the module been checked with any of the recommended validation tools for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC 8342? N/A Ð no YANG involvement. 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. None of the document is written in a formal language. Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? At the beginning of the shepherding process, the shepherd did a review of the document, which resulted in significant revisions. The document appears ready, although the shepherd suspects that some clarification of the IANA requests will still be required, which can happen at a later stage in the publication process. 10. Several IETF Areas have assembled lists of common issues that their reviewers encounter. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent reviews? The ART topics are the most relevant. The working group from which this originates would be the appropriate place for IMAP concerns to be raised, and none have been. There is enough overlap with the JMAP WG that any concerns there would have surfaced. 11. What type of RFC publication is being requested on the IETF stream (Best Current Practice, Proposed Standard, Internet Standard, Informational, Experimental or Historic)? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? Informational status is being requested. This seems appropriate for describing and documenting existing practice. Datatracker reflects this intent. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in BCP 79? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. Shepherd has polled authors and they are not aware of any relevant IPR. 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. Authors are willing to be listed. There are 2 authors. 14. Document any remaining I-D nits in this document. Simply running the idnits tool is not enough; please review the "Content Guidelines" on authors.ietf.org. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) Idnits identifies only an instance of non-ASCII characters in the document, which can be corrected in the editorial process. 15. Should any informative references be normative or vice-versa? See the IESG Statement on Normative and Informative References. References are all normative and seem correct. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? All normative references are freely available. 17. Are there any normative downward references (see RFC 3967 and BCP 97) that are not already listed in the DOWNREF registry? If so, list them. No downrefs have been seen. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? N/A 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. No existing RFC status is changed. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see RFC 8126). The shepherd has some concern about the IANA considerations, specifically that the template shown in the IANA considerations does not align with the form of the registries being added to. It was noted that RFC 5788, which was the source of other entries in the registry, also doesnÕt align. Hopefully this can be resolved in interactions with IANA during the publication process. 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. There are no new IANA registries. |
|
2025-08-28
|
07 | Ken Murchison | IETF WG state changed to Submitted to IESG for Publication from In WG Last Call |
|
2025-08-28
|
07 | Ken Murchison | IESG state changed to Publication Requested from I-D Exists |
|
2025-08-28
|
07 | (System) | Changed action holders to Andy Newton (IESG state changed) |
|
2025-08-28
|
07 | Ken Murchison | Responsible AD changed to Andy Newton |
|
2025-08-28
|
07 | Ken Murchison | Document is now in IESG state Publication Requested |
|
2025-08-11
|
07 | Jim Fenton | Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach … Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? This document describes existing practice in order to add new IMAP/JMAP keywords and mailbox attributes to the appropriate IANA registries. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? There was a moderate amoount of discussion, primarily as a result of WG last call and a second last call issued as a result of document changes. None of the consensus was particularly rough. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) Much the opposite; as noted above, there has been very little comment. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as RFC 7942 recommends) or elsewhere (where)? The document is informational. It has been written to document existing usage by some implementations, but doesnÕt cite those implementations. Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The document addresses keywords and attributes that are internal to IMAP and JMAP. No external reviews are thought to be needed. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. No formal expert review criteria are applicable. 7. If the document contains a YANG module, has the final version of the module been checked with any of the recommended validation tools for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC 8342? N/A Ð no YANG involvement. 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. None of the document is written in a formal language. Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? At the beginning of the shepherding process, the shepherd did a review of the document, which resulted in significant revisions. The document appears ready, although the shepherd suspects that some clarification of the IANA requests will still be required, which can happen at a later stage in the publication process. 10. Several IETF Areas have assembled lists of common issues that their reviewers encounter. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent reviews? The ART topics are the most relevant. The working group from which this originates would be the appropriate place for IMAP concerns to be raised, and none have been. There is enough overlap with the JMAP WG that any concerns there would have surfaced. 11. What type of RFC publication is being requested on the IETF stream (Best Current Practice, Proposed Standard, Internet Standard, Informational, Experimental or Historic)? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? Informational status is being requested. This seems appropriate for describing and documenting existing practice. Datatracker reflects this intent. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in BCP 79? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. Shepherd has polled authors and they are not aware of any relevant IPR. 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. Authors are willing to be listed. There are 2 authors. 14. Document any remaining I-D nits in this document. Simply running the idnits tool is not enough; please review the "Content Guidelines" on authors.ietf.org. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) Idnits identifies only an instance of non-ASCII characters in the document, which can be corrected in the editorial process. 15. Should any informative references be normative or vice-versa? See the IESG Statement on Normative and Informative References. References are all normative and seem correct. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? All normative references are freely available. 17. Are there any normative downward references (see RFC 3967 and BCP 97) that are not already listed in the DOWNREF registry? If so, list them. No downrefs have been seen. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? N/A 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. No existing RFC status is changed. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see RFC 8126). The shepherd has some concern about the IANA considerations, specifically that the template shown in the IANA considerations does not align with the form of the registries being added to. It was noted that RFC 5788, which was the source of other entries in the registry, also doesnÕt align. Hopefully this can be resolved in interactions with IANA during the publication process. 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. There are no new IANA registries. |
|
2025-08-09
|
07 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-07.txt |
|
2025-08-09
|
07 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-08-09
|
07 | Daniel Eggert | Uploaded new revision |
|
2025-07-30
|
06 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-06.txt |
|
2025-07-30
|
06 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-07-30
|
06 | Daniel Eggert | Uploaded new revision |
|
2025-07-24
|
05 | Ken Murchison | IETF WG state changed to In WG Last Call from WG Consensus: Waiting for Write-Up |
|
2025-07-24
|
05 | Ken Murchison | Notification list changed to fenton@bluepopcorn.net from fenton@bluepopcorn.net |
|
2025-07-21
|
05 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-05.txt |
|
2025-07-21
|
05 | Daniel Eggert | New version approved |
|
2025-07-21
|
05 | (System) | Request for posting confirmation emailed to previous authors: Daniel Eggert , Neil Jenkins |
|
2025-07-21
|
05 | Daniel Eggert | Uploaded new revision |
|
2025-06-10
|
04 | Jim Fenton | Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach … Document History 1. Does the working group (WG) consensus represent the strong concurrence of a few individuals, with others being silent, or did it reach broad agreement? This document describes existing practice in order to add new IMAP/JMAP keywords and mailbox attributes to the appropriate IANA registries. 2. Was there controversy about particular points, or were there decisions where the consensus was particularly rough? There was very little discussion about this draft other than a WG last-call comment and review comments from the Document Shepherd. Nothing was controversial. 3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarize the areas of conflict in separate email messages to the responsible Area Director. (It should be in a separate email because this questionnaire is publicly available.) Much the opposite; as noted above, there has been very little comment. 4. For protocol documents, are there existing implementations of the contents of the document? Have a significant number of potential implementers indicated plans to implement? Are any existing implementations reported somewhere, either in the document itself (as RFC 7942 recommends) or elsewhere (where)? The document is informational. It has been written to document existing usage by some implementations, but doesnÕt cite those implementations. Additional Reviews 5. Do the contents of this document closely interact with technologies in other IETF working groups or external organizations, and would it therefore benefit from their review? Have those reviews occurred? If yes, describe which reviews took place. The document addresses keywords and attributes that are internal to IMAP and JMAP. No external reviews are thought to be needed. 6. Describe how the document meets any required formal expert review criteria, such as the MIB Doctor, YANG Doctor, media type, and URI type reviews. No formal expert review criteria are applicable. 7. If the document contains a YANG module, has the final version of the module been checked with any of the recommended validation tools for syntax and formatting validation? If there are any resulting errors or warnings, what is the justification for not fixing them at this time? Does the YANG module comply with the Network Management Datastore Architecture (NMDA) as specified in RFC 8342? N/A Ð no YANG involvement. 8. Describe reviews and automated checks performed to validate sections of the final version of the document written in a formal language, such as XML code, BNF rules, MIB definitions, CBOR's CDDL, etc. None of the document is written in a formal language. Document Shepherd Checks 9. Based on the shepherd's review of the document, is it their opinion that this document is needed, clearly written, complete, correctly designed, and ready to be handed off to the responsible Area Director? At the beginning of the shepherding process, the shepherd did a review of the document, which resulted in significant revisions. The document appears ready, although the shepherd suspects that some clarification of the IANA requests will still be required, which can happen at a later stage in the publication process. 10. Several IETF Areas have assembled lists of common issues that their reviewers encounter. For which areas have such issues been identified and addressed? For which does this still need to happen in subsequent reviews? The ART topics are the most relevant. The working group from which this originates would be the appropriate place for IMAP concerns to be raised, and none have been. There is enough overlap with the JMAP WG that any concerns there would have surfaced. 11. What type of RFC publication is being requested on the IETF stream (Best Current Practice, Proposed Standard, Internet Standard, Informational, Experimental or Historic)? Why is this the proper type of RFC? Do all Datatracker state attributes correctly reflect this intent? Informational status is being requested. This seems appropriate for describing and documenting existing practice. Datatracker reflects this intent. 12. Have reasonable efforts been made to remind all authors of the intellectual property rights (IPR) disclosure obligations described in BCP 79? To the best of your knowledge, have all required disclosures been filed? If not, explain why. If yes, summarize any relevant discussion, including links to publicly-available messages when applicable. Shepherd has polled authors and they are not aware of any relevant IPR. 13. Has each author, editor, and contributor shown their willingness to be listed as such? If the total number of authors and editors on the front page is greater than five, please provide a justification. Authors are willing to be listed. There are 2 authors. 14. Document any remaining I-D nits in this document. Simply running the idnits tool is not enough; please review the "Content Guidelines" on authors.ietf.org. (Also note that the current idnits tool generates some incorrect warnings; a rewrite is underway.) Idnits identifies only an instance of non-ASCII characters in the document, which can be corrected in the editorial process. 15. Should any informative references be normative or vice-versa? See the IESG Statement on Normative and Informative References. References are all normative and seem correct. 16. List any normative references that are not freely available to anyone. Did the community have sufficient access to review any such normative references? All normative references are freely available. 17. Are there any normative downward references (see RFC 3967 and BCP 97) that are not already listed in the DOWNREF registry? If so, list them. No downrefs have been seen. 18. Are there normative references to documents that are not ready to be submitted to the IESG for publication or are otherwise in an unclear state? If so, what is the plan for their completion? N/A 19. Will publication of this document change the status of any existing RFCs? If so, does the Datatracker metadata correctly reflect this and are those RFCs listed on the title page, in the abstract, and discussed in the introduction? If not, explain why and point to the part of the document where the relationship of this document to these other RFCs is discussed. No existing RFC status is changed. 20. Describe the document shepherd's review of the IANA considerations section, especially with regard to its consistency with the body of the document. Confirm that all aspects of the document requiring IANA assignments are associated with the appropriate reservations in IANA registries. Confirm that any referenced IANA registries have been clearly identified. Confirm that each newly created IANA registry specifies its initial contents, allocations procedures, and a reasonable name (see RFC 8126). The shepherd has some concern about the IANA considerations, specifically that the template shown in the IANA considerations does not align with the form of the registries being added to. It was noted that RFC 5788, which was the source of other entries in the registry, also doesnÕt align. Hopefully this can be resolved in interactions with IANA during the publication process. 21. List any new IANA registries that require Designated Expert Review for future allocations. Are the instructions to the Designated Expert clear? Please include suggestions of designated experts, if appropriate. There are no new IANA registries. |
|
2025-06-08
|
04 | Murray Kucherawy | Intended Status changed to Informational from None |
|
2025-06-07
|
04 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-04.txt |
|
2025-06-07
|
04 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-06-07
|
04 | Daniel Eggert | Uploaded new revision |
|
2025-06-05
|
03 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-03.txt |
|
2025-06-05
|
03 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-06-05
|
03 | Daniel Eggert | Uploaded new revision |
|
2025-03-19
|
02 | Murray Kucherawy | Notification list changed to fenton@bluepopcorn.net because the document shepherd was set |
|
2025-03-19
|
02 | Murray Kucherawy | Document shepherd changed to Jim Fenton |
|
2025-03-19
|
02 | Ken Murchison | IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call |
|
2025-03-16
|
02 | Ken Murchison | Added to session: IETF-122: mailmaint Thu-0230 |
|
2025-02-17
|
02 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-02.txt |
|
2025-02-17
|
02 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2025-02-17
|
02 | Daniel Eggert | Uploaded new revision |
|
2025-02-07
|
01 | Ken Murchison | IETF WG state changed to In WG Last Call from WG Document |
|
2025-02-07
|
01 | Ken Murchison | Notification list changed to none |
|
2024-12-10
|
01 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-01.txt |
|
2024-12-10
|
01 | Daniel Eggert | New version accepted (logged-in submitter: Daniel Eggert) |
|
2024-12-10
|
01 | Daniel Eggert | Uploaded new revision |
|
2024-11-26
|
00 | Ken Murchison | This document now replaces draft-eggert-mailflagcolors, draft-eggert-messageflag-mailboxattribute, draft-jenkins-mail-keywords instead of None |
|
2024-11-25
|
00 | Daniel Eggert | New version available: draft-ietf-mailmaint-messageflag-mailboxattribute-00.txt |
|
2024-11-25
|
00 | Ken Murchison | WG -00 approved |
|
2024-11-25
|
00 | Daniel Eggert | Set submitter to "Daniel Eggert ", replaces to (none) and sent approval email to group chairs: mailmaint-chairs@ietf.org |
|
2024-11-25
|
00 | Daniel Eggert | Uploaded new revision |