draft-ietf-lemonade-search-within-01.txt   draft-ietf-lemonade-search-within-02.txt 
Lemonade Lemonade
Internet Draft: WITHIN S. H. Maes Internet Draft: WITHIN S. H. Maes
Document: draft-ietf-lemonade-search-within-01 R. Cromwell Document: draft-ietf-lemonade-search-within-02 R. Cromwell
Eds. Eds.
WITHIN Search extension to the IMAP Protocol WITHIN Search extension to the IMAP Protocol
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
skipping to change at page 1, line 28 skipping to change at page 1, line 28
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 30, 2006.
Abstract Abstract
WITHIN is an extension to [RFC3501] SEARCH which returns messages WITHIN is an extension to [RFC3501] SEARCH which returns messages
whose internal date is within or outside a specified interval and whose internal date is within or outside a specified interval and
differs from SINCE in that an interval in days is specified instead differs from SINCE in that an interval in days is specified instead
of a date. WITHIN is expected to be most useful for persistent of a date. WITHIN is expected to be most useful for persistent
searches in combination with mobile devices. searches in combination with mobile devices.
Conventions used in this document Conventions used in this document
In examples, "C:" and "S:" indicate lines sent by the client and In examples, "C:" and "S:" indicate lines sent by the client and
server respectively. server respectively.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
An implementation is not compliant if it fails to satisfy one or more When describing the general syntax, some definitions are omitted as
of the MUST or REQUIRED level requirements for the protocol(s) it they are defined in [RFC3501].
implements. An implementation that satisfies all the MUST or REQUIRED
level and all the SHOULD level requirements for a protocol is said to
be "unconditionally compliant" to that protocol; one that satisfies
all the MUST level requirements but not all the SHOULD level
requirements is said to be "conditionally compliant." When
describing the general syntax, some definitions are omitted as they
are defined in [RFC3501].
Table of Contents Table of Contents
Status of this Memo...............................................1 Status of this Memo...............................................1
Abstract..........................................................1 Abstract..........................................................1
Conventions used in this document.................................1 Conventions used in this document.................................1
Table of Contents.................................................2 Table of Contents.................................................2
1. Introduction................................................2 1. Introduction................................................2
2. Formal Syntax...............................................3 2. Formal Syntax...............................................2
Security Considerations...........................................3 3. Examples....................................................3
References........................................................3 4. Security Considerations.....................................3
Normative References..............................................3
Informative References............................................3
Future Work.......................................................3 Future Work.......................................................3
Version History...................................................4 Version History...................................................3
Acknowledgments...................................................4 Acknowledgments...................................................4
Authors Addresses.................................................4 Authors Addresses.................................................4
Intellectual Property Statement...................................5 Intellectual Property Statement...................................4
Disclaimer of Validity............................................5 Full Copyright Statement..........................................5
Copyright Statement...............................................5
1. Introduction 1. Introduction
The WITHIN extension is present in any IMAP4 implementation which The WITHIN extension is present in any IMAP4 implementation which
returns “WITHIN” as one of the supported capabilities in the returns "WITHIN" as one of the supported capabilities in the
CAPABILITY command. CAPABILITY command.
The extension exposes two new search keys, YOUNGER and OLDER, each of The extension exposes two new search keys, YOUNGER and OLDER, each of
which take a non-zero integer argument corresponding to an interval which take a non-zero integer argument corresponding to an interval
in days. YOUNGER returns messages deposited in the mailbox after the in hours. YOUNGER returns messages deposited in the mailbox after
date calculated by subtracting the interval number of day from the the date calculated by subtracting the interval number of hours from
server’s current date. OLDER returns messages deposited before the the server's current date. OLDER returns messages deposited before
date calculated as described above. the date calculated as described above.
2. Formal Syntax 2. Formal Syntax
The following syntax specification uses the Augmented Backus-Naur The following syntax specification uses the Augmented Backus-Naur
Form (ABNF) notation. Elements not defined here can be found in Form (ABNF) notation. Elements not defined here can be found in
the formal syntax of the [ABNF], [RFC3501], and [ABNFEXTEND]. the formal syntax of the [ABNF], [RFC3501], and [ABNFEXTEND].
The ABNF grammar in [RFC3501] is hereby modified with two new search The ABNF grammar in [RFC3501] is hereby modified with two new search
keys: OLDER <interval days> and YOUNGER <interval days> keys: OLDER <interval hours> and YOUNGER <interval hours>
search-key /= "OLDER" SP nz-number / "YOUNGER" SP nz-number
search-key /= “OLDER” nz-number / “YOUNGER” nz-number
; search-key defined in [RFC3501] ; search-key defined in [RFC3501]
3. Examples 3. Examples
C: a1 SEARCH UNSEEN YOUNGER 3 C: a1 SEARCH UNSEEN YOUNGER 72
S: a1 * SEARCH 4 8 15 16 23 42 S: a1 * SEARCH 4 8 15 16 23 42
Search for all unseen messages within the past 3 days according to Search for all unseen messages within the past 3 days (72 hours)
the server’s current time. according to the server’s current time.
Security Considerations 4. Security Considerations
The WITHIN extension does not raise any security considerations which The WITHIN extension does not raise any security considerations which
are not present in the base protocol. Considerations are the same as are not present in the base protocol. Considerations are the same as
for IMAP [RFC 3501]. for IMAP [RFC 3501].
References Normative References
[ABNF] D. Crocker, et al. "Augmented BNF for Syntax Specifications: [ABNF] D. Crocker, et al. "Augmented BNF for Syntax Specifications:
ABNF, RFC 2234, November 1997. ABNF", RFC 2234, November 1997.
http://www.ietf.org/rfc/rfc2234 http://www.ietf.org/rfc/rfc2234
[ABNFEXTEND] Melnikov, A., and C. Daboo, "Collected extensions to [ABNFEXTEND] Melnikov, A., and C. Daboo, "Collected extensions to
IMAP4 ABNF", work in progress, draft-melnikov-imap-ext-abnf-XX.txt. IMAP4 ABNF", RFC 4466, April 2006.
[RFC3501] Crispin, M. "IMAP4, Internet Message Access Protocol [RFC3501] Crispin, M. "IMAP4, Internet Message Access Protocol
Version 4 rev1", RFC 3501, March 2003. Version 4 rev1", RFC 3501, March 2003.
http://www.ietf.org/rfc/rfc3501 http://www.ietf.org/rfc/rfc3501
Informative References
[P-IMAP] Maes, S.H., Lima R., Kuang, C., Cromwell, R., Ha, V. and
Chiu, E., Day, J., Ahad R., Jeong W-H., Rosell G., Sini, J., Sohn S-
M., Xiaohui F. and Lijun Z., "Push Extensions to the IMAP Protocol
(P-IMAP)", draft-maes-lemonade-p-imap-xx.txt, (work in progress).
Future Work Future Work
[Note to RFC editor: please delete this section before publication]
[1] Decide whether other interval units are necessary. [1] Decide whether other interval units are necessary.
Version History Version History
[Note to RFC editor: please delete this section before publication]
Release 00 Release 00
Initial release, separated from VFOLDER draft Initial release, separated from VFOLDER draft
Release 01 Release 01
Incorporate feedback and suggestions received from Arnt Incorporate feedback and suggestions received from Arnt
Gulbrandsen. Gulbrandsen.
Release 02
Interval now defined as hours instead of days as per interim
meeting consensus.
Acknowledgments Acknowledgments
We want to give a special thanks to A. Melnikov and A. Gulbrandsen The authors want to thank all who have contributed key insight and
for their review and suggestions. This work is reflecting many extensively reviewed and discussed the concepts of LPSEARCH and the
concepts shared with the work done by A. Gulbrandsen. authors of its early introduction P-IMAP [P-IMAP].
The authors also want to thank all who have contributed key insight We also want to give a special thanks to A. Melnikov and A.
and extensively reviewed and discussed the concepts of LPSEARCH and Gulbrandsen for their review and suggestions.
its early introduction P-IMAP [P-IMAP]. In particular, this includes
the authors of the P-IMAP draft: Rafiul Ahad – Oracle Corporation,
Eugene Chiu – Oracle Corporation, Ray Cromwell – Oracle Corporation,
Jia-der Day – Oracle Corporation, Vi Ha – Oracle Corporation, Wook-
Hyun Jeong – Samsung Electronics Co. LTF, Chang Kuang – Oracle
Corporation, Rodrigo Lima – Oracle Corporation, Stephane H. Maes –
Oracle Corporation, Gustaf Rosell - Sony Ericsson, Jean Sini – Symbol
Technologies, Sung-Mu Son – LG Electronics, Fan Xiaohui - CHINA
MOBILE COMMUNICATIONS CORPORATION (CMCC), Zhao Lijun - CHINA MOBILE
COMMUNICATIONS CORPORATION (CMCC).
Authors Addresses Authors Addresses
Stephane H. Maes Stephane H. Maes
Oracle Corporation Oracle Corporation
500 Oracle Parkway 500 Oracle Parkway
M/S 4op634 M/S 4op634
Redwood Shores, CA 94065 Redwood Shores, CA 94065
USA USA
Phone: +1-650-607-6296 Phone: +1-650-607-6296
skipping to change at page 5, line 8 skipping to change at page 4, line 46
Ray Cromwell Ray Cromwell
Oracle Corporation Oracle Corporation
500 Oracle Parkway 500 Oracle Parkway
Redwood Shores, CA 94065 Redwood Shores, CA 94065
USA USA
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; neither does it represent that it
made any independent effort to identify any such rights. Information has made any effort to identify any such rights. Information on the
on the procedures with respect to rights in RFC documents can be IETF's procedures with respect to rights in standards-track and
found in BCP 78 and BCP 79. standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
Copies of IPR disclosures made to the IETF Secretariat and any licenses to be made available, or the result of an attempt made to
assurances of licenses to be made available, or the result of an obtain a general license or permission for the use of such
attempt made to obtain a general license or permission for the use of proprietary rights by implementers or users of this specification can
such proprietary rights by implementers or users of this be obtained from the IETF Secretariat.
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights, which may cover technology that may be required to practice
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF Executive
ipr@ietf.org. Director.
Disclaimer of Validity Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
Copyright (C) The Internet Society (2006). This document is subject or assist in its implementation may be prepared, copied, published
to the rights, licenses and restrictions contained in BCP 78, and and distributed, in whole or in part, without restriction of any
except as set forth therein, the authors retain all their rights. kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
Acknowledgement document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
Funding for the RFC Editor function is currently provided by the The limited permissions granted above are perpetual and will not be
Internet Society. revoked by the Internet Society or its successors or assigns.
 End of changes. 28 change blocks. 
73 lines changed or deleted 81 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/