RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 5464, "The IMAP METADATA Extension", February 2009

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: app

Errata ID: 3160
Status: Rejected
Type: Technical
Publication Format(s) : TEXT

Reported By: Adrien de Croy
Date Reported: 2012-03-22
Rejected by: Pete Resnick
Date Rejected: 2012-04-28

Section 4.4.2 says:

   The response consists of a list of entries, each of which have
   changed on the server or mailbox.

   Example:
           C: a NOOP
           S: * METADATA "" /shared/comment
           S: a OK NOOP complete

      In the above example, the server indicates that the "/shared/
      comment" server entry has been changed.

   Example:

           C: a NOOP
           S: * METADATA "INBOX" /shared/comment /private/comment
           S: a OK NOOP complete

      In the above example, the server indicates a change to two mailbox
      entries.

It should say:

needs design input

Notes:

unsolicited METADATA responses not clear as to scope / state

need some prose about what to do depending on client state.

if a client has a mailbox selected should it receive unsolicited metadata responses relating ONLY to that mailbox, or any mailbox? The response has a mailbox field, so it's feasible a client not in a selected state could want responses for any metadata change on any mailbox.
--VERIFIER NOTES--
A desire for more explanatory prose is not appropriate for an erratum.

Report New Errata