1 / 6

IMAPEXT IETF 64

IMAPEXT IETF 64. Good day, eh?. Agenda. LISTEXT - Barry Leiba CONDSTORE update Annotate Collator and Comparator ABNF. Annotate Draft. Draft expired - needs update. Cyrus’ list of changes:. Changed 'string' formal syntax to 'list-mail' and 'astring' for entry/attribute names.

gomeza
Download Presentation

IMAPEXT IETF 64

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMAPEXT IETF 64 Good day, eh?

  2. Agenda • LISTEXT - Barry Leiba • CONDSTORE update • Annotate • Collator and Comparator • ABNF

  3. Annotate Draft • Draft expired - needs update

  4. Cyrus’ list of changes: • Changed 'string' formal syntax to 'list-mail' and 'astring' for entry/attribute names. • Updated examples to match new astring syntax. • Now requires explicit use of .priv or .shared in SORT. • Removed requirement that 'n' right only be present if 'r' right is also present. • Changed ANNOTATESIZE response to ANNOTATIONS response. • Allow servers to indicate that they do not support private annotations. • Added example for extended SELECT including ANNOTATIONS response code.

  5. Ease of Implementation Issues arising since Paris in part. • Hard-code content-type? Yes • Remove content-language? No… • Remove display-name? Yes • Limit searching to value only? Yes • Remove % and * in SEARCH attributes? Yes • In FETCH? No • Remove flags as annotations?

  6. Other issues • Remove vendor.* attributes - list consensus • Need to define what happens if the same annotation is written twice in the same STORE command. • Need to return empty ANNOTATIONS() response when none exist when doing a FETCH. • What is proper server response if client asks to fetch annotations on non-existent body-part? • Re-word section 3.2.1 as per Arnt's suggestion to clarify use of vendor namespace.

More Related