draft-ietf-sieve-rfc3598bis-01.txt   draft-ietf-sieve-rfc3598bis-02.txt 
Sieve Working Group K. Murchison Sieve Working Group K. Murchison
Internet-Draft Oceana Matrix Ltd. Internet-Draft Carnegie Mellon University
Obsoletes: 3598 (if approved) September 12, 2005 Obsoletes: 3598 (if approved) February 15, 2006
Expires: March 16, 2006 Expires: August 19, 2006
Sieve Email Filtering -- Subaddress Extension Sieve Email Filtering -- Subaddress Extension
draft-ietf-sieve-rfc3598bis-01.txt draft-ietf-sieve-rfc3598bis-02.txt
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.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 March 16, 2006. This Internet-Draft will expire on August 19, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
On email systems that allow for "subaddressing" or "detailed On email systems that allow for "subaddressing" or "detailed
addressing" (e.g., "ken+sieve@example.org"), it is sometimes addressing" (e.g., "ken+sieve@example.org"), it is sometimes
desirable to make comparisons against these sub-parts of addresses. desirable to make comparisons against these sub-parts of addresses.
This document defines an extension to the Sieve mail filtering This document defines an extension to the Sieve mail filtering
language that allows users to compare against the user and detail language that allows users to compare against the user and detail
parts of an address. parts of an address.
Meta-information on this document Meta-information on this document
This information is intended to facilitate discussion. It will be This information is intended to facilitate discussion. It will be
removed when this document leaves the Internet-Draft stage. removed when this document leaves the Internet-Draft stage.
This document is intended to be an update to the existing This document is intended to be an update to the existing
"subaddress" extension to the Sieve mail filtering language, "subaddress" extension to the Sieve mail filtering language,
available from the RFC repository as available from the RFC repository as
<ftp://ftp.isi.edu/in-notes/rfc3598.txt> and <ftp://ftp.isi.edu/in-notes/rfc3598.txt> and
<ftp://ftp.isi.edu/internet-drafts/draft-ietf-sieve-3028bis-04.txt> <ftp://ftp.isi.edu/internet-drafts/draft-ietf-sieve-3028bis-05.txt>
respectively. respectively.
This document and the Sieve language itself are being discussed on This document and the Sieve language itself are being discussed on
the MTA Filters mailing list at <mailto:ietf-mta-filters@imc.org>. the MTA Filters mailing list at <mailto:ietf-mta-filters@imc.org>.
Subscription requests can be sent to Subscription requests can be sent to
<mailto:ietf-mta-filters-request@imc.org?body=subscribe> (send an <mailto:ietf-mta-filters-request@imc.org?body=subscribe> (send an
email message with the word "subscribe" in the body). More email message with the word "subscribe" in the body). More
information on the mailing list along with a WWW archive of back information on the mailing list along with an archive of back
messages is available at <http://www.imc.org/ietf-mta-filters/>. messages is available at <http://www.imc.org/ietf-mta-filters/>.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Capability Identifier . . . . . . . . . . . . . . . . . . . . 5 2. Capability Identifier . . . . . . . . . . . . . . . . . . . . 5
3. Subaddress Comparisons . . . . . . . . . . . . . . . . . . . . 6 3. Subaddress Comparisons . . . . . . . . . . . . . . . . . . . . 6
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. Normative References . . . . . . . . . . . . . . . . . . . . . 10 6. Normative References . . . . . . . . . . . . . . . . . . . . . 10
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 11
Appendix B. Changes since RFC3598 . . . . . . . . . . . . . . . . 12 Appendix B. Changes since RFC3598 . . . . . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . . . 14
1. Introduction 1. Introduction
Subaddressing is the practice of augmenting (either by prefix or Subaddressing is the practice of augmenting (usually with a suffix)
suffix) the local-part of an [RFC2822] address with some "detail" the local-part of an [RFC2822] address with some "detail" information
information to indicate that the message should be delivered to the to indicate that the message should be delivered to the mailbox
mailbox specified by the "detail" information. A "separator specified by the "detail" information. A "separator character
character sequence" (typically "+"), forms the boundary between the sequence" (typically "+"), forms the boundary between the "user"
"user" (original local-part) and "detail" sub-parts of the address, (original local-part) and "detail" sub-parts of the address, much
much like the "@" character forms the boundary between the local-part like the "@" character forms the boundary between the local-part and
and domain. domain.
Typical uses of subaddressing might be: Typical uses of subaddressing might be:
o A message addressed to "ken+sieve@example.org" is delivered into a o A message addressed to "ken+sieve@example.org" is delivered into a
mailbox called "sieve" belonging to the user "ken". mailbox called "sieve" belonging to the user "ken".
o A message addressed to "5551212#123@example.org" is delivered to o A message addressed to "5551212#123@example.org" is delivered to
the voice mailbox number "123" at phone number "5551212". the voice mailbox number "123" at phone number "5551212".
This document describes an extension to the Sieve language defined by This document describes an extension to the Sieve language defined by
skipping to change at page 6, line 28 skipping to change at page 6, line 28
be the only source of detail information for the specific be the only source of detail information for the specific
recipient. recipient.
NOTE: Because the construction of detailed addresses can be site NOTE: Because the construction of detailed addresses can be site
and/or implementation specific, using the subaddress extension on and/or implementation specific, using the subaddress extension on
foreign addresses (such as the envelope "from" address or foreign addresses (such as the envelope "from" address or
originator header fields) may lead to inconsistent or incorrect originator header fields) may lead to inconsistent or incorrect
results. results.
The ":user" argument specifies the user sub-part of the local-part of The ":user" argument specifies the user sub-part of the local-part of
an address. Whether the user sub-part lies to the left or right of an address. The positioning of the user sub-part with respect to the
the separator character sequence is dependent on the encompassing separator character sequence is dependent on the encompassing mail
mail system. If no separator character sequence exists, then ":user" system. If no separator character sequence exists, then ":user"
specifies the entire left-side of the address (equivalent to specifies the entire left-side of the address (equivalent to
":localpart"). ":localpart").
The ":detail" argument specifies the detail sub-part of the local- The ":detail" argument specifies the detail sub-part of the local-
part of an address. Whether the detail sub-part lies to the left or part of an address. The positioning of the detail sub-part with
right of the separator character sequence is dependent on the respect to the separator character sequence is dependent on the
encompassing mail system. If no separator character sequence exists, encompassing mail system. If no separator character sequence exists,
the test evaluates to false. If the separator character sequence the test evaluates to false. If the separator character sequence
exists, but not detail information is provided, then ":detail" ":is" exists, but no detail information is provided, then ":detail" ":is"
the empty key (""). Otherwise, the ":detail" sub-part ":contains" the empty key (""). Otherwise, the ":detail" sub-part ":contains"
the empty key. the empty key.
NOTE: If the separator character sequence occurs more than once in NOTE: If the separator character sequence occurs more than once in
the local-part, then the address MUST be split at the left-most the local-part, then the logic used to split the address is
separator when the detail information is a suffix and at the implementation defined, and is usually dependent on the format
right-most separator when the detail information is a prefix. used by the encompassing mail system.
Implementations MUST make sure that the separator character sequence Implementations MUST make sure that the separator character sequence
and the ordering of the user and detail sub-parts match those that and the ordering of the user and detail sub-parts match those that
are used and/or allowed by the encompassing mail system, otherwise are used and/or allowed by the encompassing mail system, otherwise
unexpected results might occur. Implementations SHOULD allow the unexpected results might occur. Implementations SHOULD allow the
separator character sequence and sub-part ordering to be configurable separator character sequence and sub-part ordering to be configurable
so that they may be used with a variety of mail systems. Note that so that they may be used with a variety of mail systems. Note that
the mechanisms used to define and/or query the separator character the mechanisms used to define and/or query the separator character
sequence and sub-part ordering used by the mail system are outside sequence and sub-part ordering used by the mail system are outside
the scope of this document. the scope of this document.
skipping to change at page 10, line 15 skipping to change at page 10, line 15
5. Security Considerations 5. Security Considerations
Security considerations are discussed in [I-D.ietf-sieve-3028bis]. Security considerations are discussed in [I-D.ietf-sieve-3028bis].
It is believed that this extension does not introduce any additional It is believed that this extension does not introduce any additional
security concerns. security concerns.
6. Normative References 6. Normative References
[I-D.ietf-sieve-3028bis] [I-D.ietf-sieve-3028bis]
Showalter, T. and P. Guenther, "Sieve: An Email Filtering Showalter, T. and P. Guenther, "Sieve: An Email Filtering
Language", draft-ietf-sieve-3028bis-04 (work in progress), Language", draft-ietf-sieve-3028bis-05 (work in progress),
July 2005. November 2005.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2822] Resnick, P., "Internet Message Format", RFC 2822, [RFC2822] Resnick, P., "Internet Message Format", RFC 2822,
April 2001. April 2001.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Thanks to Tim Showalter, Alexey Melnikov, Michael Salmon, Randall Thanks to Tim Showalter, Alexey Melnikov, Michael Salmon, Randall
skipping to change at page 13, line 8 skipping to change at page 13, line 8
o Fixed envelope test example to only use "to" address. o Fixed envelope test example to only use "to" address.
o Refer to the zero-length string ("") as "empty" instead of "null" o Refer to the zero-length string ("") as "empty" instead of "null"
(per draft-ietf-sieve-3028bis) (per draft-ietf-sieve-3028bis)
o Miscellaneous editorial changes. o Miscellaneous editorial changes.
Author's Address Author's Address
Kenneth Murchison Kenneth Murchison
Oceana Matrix Ltd. Carnegie Mellon University
2495 Main St. 5000 Forbes Avenue
Suite 401 Cyert Hall 285
Buffalo, NY 14214 Pittsburgh, PA 15213
US US
Phone: +1 716 604 0088 Phone: +1 412 268 2638
Email: ken@oceana.com Email: murch@andrew.cmu.edu
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 Rights 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; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 14, line 41 skipping to change at page 14, line 41
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 Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 15 change blocks. 
34 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.29, available from http://www.levkowetz.com/ietf/tools/rfcdiff/