draft-ietf-sieve-rfc3598bis-03.txt   draft-ietf-sieve-rfc3598bis-04.txt 
Sieve Working Group K. Murchison Sieve Working Group K. Murchison
Internet-Draft Carnegie Mellon University Internet-Draft Carnegie Mellon University
Obsoletes: 3598 (if approved) April 18, 2006 Obsoletes: 3598 (if approved) April 24, 2006
Expires: October 20, 2006 Expires: October 26, 2006
Sieve Email Filtering -- Subaddress Extension Sieve Email Filtering -- Subaddress Extension
draft-ietf-sieve-rfc3598bis-03 draft-ietf-sieve-rfc3598bis-04
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 October 20, 2006. This Internet-Draft will expire on October 26, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). 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.
skipping to change at page 4, line 8 skipping to change at page 4, line 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. Normative References . . . . . . . . . . . . . . . . . . . . . 10 7. 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 the local-part of an Subaddressing is the practice of augmenting the local-part of an
[RFC2822] address with some "detail" information to indicate that the [RFC2822] address with some "detail" information in order to give
message should be delivered to the mailbox specified by the "detail" some extra meaning to that address. One common way of encoding
information. One common way of encoding "detail" information into "detail" information into the local-part is to add a "separator
the local-part is to add a "separator character sequence", such as character sequence", such as "+", to form a boundary between the
"+", to form a boundary between the "user" (original local-part) and "user" (original local-part) and "detail" sub-parts of the address,
"detail" sub-parts of the address, much like the "@" character forms much like the "@" character forms the boundary between the local-part
the boundary between the local-part and domain. and 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.com" is delivered to o A message addressed to "5551212#123@example.com" 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 11, line 8 skipping to change at page 11, line 8
[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
Gellens, Philip Guenther, Jutta Degener, Michael Haardt, and Ned Gellens, Philip Guenther, Jutta Degener, Michael Haardt, Ned Freed,
Freed for their help with this document. and Mark Mallett for their help with this document.
Appendix B. Changes since RFC3598 Appendix B. Changes since RFC3598
o Discussion of how the user and detail information is encoded now o Discussion of how the user and detail information is encoded now
uses generic language. uses generic language.
o Added note detailing that this extension is most useful when used o Added note detailing that this extension is most useful when used
on the envelope "to" address. on the envelope "to" address.
o Added note detailing that this extension isn't very useful on o Added note detailing that this extension isn't very useful on
 End of changes. 5 change blocks. 
13 lines changed or deleted 13 lines changed or added

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