IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST
draft-ietf-extra-imap-list-myrights-07

[Ballot comment]
Please consider using the boilerplate from RFC 8174 instead of 2119. The draft includes at least one lower case "may". That boilerplate also enables things like lower-case "should" rather than the more awkward "ought to", which has connotations of criticism or moral judgement in much of the US.

[Ballot comment]
Comment to the AD: All IMAP shepherd write-ups say "7. There have been no IPR disclosures for this spec.", however, questions 7 is about confirming that the authors are not aware of any IPR (that might not have been disclosed yet). Was that checked with the authors?

Also sec 3: "This document extends the LIST command with a new return option
  [RFC5258], "MYRIGHTS", which allows the client to request all of the
  desired information in a single command. "
The "which" clause is confusing to me...  or should this also be attribute and "LIST-MYRIGHTS" here?

[Ballot comment]
Please consider using the RFC 8174 boilerplate (instead of the RFC 2119 one) -- there is
a lowercased "may" in the document.

Per the secdir review, please incorporate the security
considerations of RFC 4314 (e.g., by reference).

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-ietf-extra-imap-list-myrights-04. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there are two actions which we must complete.

First, in the IMAP Capabilities registry located at:

https://www.iana.org/assignments/imap-capabilities/

a single, new registration will be made as follows:

Capability Name: LIST-MYRIGHTS
Reference: [ RFC-to-be ]

Second, in the LIST-EXTENDED options registry on the Internet Message Access Protocol (IMAP) LIST EXTENDED Registry page located at:

https://www.iana.org/assignments/imap-list-extended/

a single, new registration will be made as follows:

LIST-EXTENDED option name: MYRIGHTS
LIST-EXTENDED option type: RETURN
Implied return option(s):
Published specification: [ RFC-to-be ], Section 3
Security considerations: [ RFC-to-be ], Section 6
Intended usage: COMMON
Person and email address to contact for further information: Kenneth Murchison
Change controller: IESG

The IANA Services Operator understands 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.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2018-05-14):

From: The IESG
To: IETF-Announce
CC: Jiankang Yao , extra@ietf.org, yaojk@cnnic.cn, draft-ietf-extra-imap-list-myrights@ietf.org, extra-chairs@ietf.org, alexey.melnikov@isode.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST) to Proposed Standard


The IESG has received a request from the Email mailstore and eXtensions To
Revise or Amend WG (extra) to consider the following document: - 'IMAP4
Extension for Returning MYRIGHTS Information in Extended LIST'
  as Proposed Standard

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
ietf@ietf.org mailing lists by 2018-05-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 an extension to the IMAP LIST command that
  allows the client to request the set of rights that the logged-in
  user has been granted on mailboxes, along with other information
  typically returned by the LIST command.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-extra-imap-list-myrights/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-extra-imap-list-myrights/ballot/


No IPR declarations have been submitted directly on this I-D.

Document Shepherd Write-Up for draft-ietf-extra-imap-list-myrights

1. This document is being requested as a Proposed Standard because it
extends an existing PROPOSED STANDARD (RFC5258).
The request type is indicated in the title page header.

2.

Technical Summary

This document defines an extension  to IMAP LIST command that
  allows the client to request the set of rights that the logged-in
  user has been granted on mailboxes, along with other information
  typically returned by the LIST command.

Working Group Summary

  The EXTRA WG meeting in IETF 101 identified two items, which have been to be fixed.
  During working group last call, a couple of minor issues were identified and fixed in the new version.
  The WG has looked throught this document in detail.

Document Quality

  The document is in very good shape and is ready to be published.
  Some vendors have stated their intention to implement it. Some have stated that
  they have no objection to advancement although they do not plan to implement it right now.

Personnel

  Document Shepherd - Jiankang Yao (EXTRA co-chair)
  Responsible Area Director - Alexey Melnikov


3. The Document Shepherd has read the document through in detail and
think that it is ready to go.

4. For such a short document it has had many reviews and been discussed
in two meetings. Two experts have reviewed this draft in detail and agree that this draft is in good shape.

5. There is no review required for the document by other areas, it's
very self-contained.

6. There are no concerns with this document that IESG should be aware of.

7. There have been no IPR disclosures for this spec.

8. There have been no IPR disclosures for this spec.

9. The WG consensus is very solid, while not everybody spoke, it was
clear that the entire group understood and agreed with the idea and
the method chosen.

10. There has been no discontent.

11. The ID nits tool shows the following:

  == Unused Reference: 'RFC3501' is defined on line 215, but no explicit
    reference was found in the text
Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 0 comments (--).


12. This document doesn't define anything which needs formal review
outside the working group.

13. All references have been identified as either normative or
informative.

14. All normative references are published standards.

15. There are no downward normative references references.

16. This RFC does not change the status of any other RFCs.

17. The IANA considerations ask for the following two items to be added to the registry:
Registration of IMAP capability LIST-MYRIGHTS
Registration of LIST-EXTENDED option MYRIGHTS

18. None of the IANA registries mentioned require Expert Review.

19. The formal sections are simple enough that eyeball reading
was sufficient to validate them.

The EXTRA WG meeting in IETF 101 identified two items to be fixed:
https://github.com/ietfextra/tracking/issues/17
https://github.com/ietfextra/tracking/issues/18

The authors have fixed both of these  and uploaded a new version:
https://tools.ietf.org/html/draft-ietf-extra-imap-list-myrights-02