draft-ietf-acap-email-03.txt   draft-ietf-acap-email-04.txt 
Internet Draft R. Gellens Internet Draft R. Gellens
Document: draft-ietf-acap-email-03.txt QUALCOMM Document: draft-ietf-acap-email-04.txt QUALCOMM
Expires: 28 August 2000 28 February 2000
ACAP Email Account Dataset Class ACAP Email Account Dataset Class
Status of this Memo: Status of this Memo:
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as other groups may also distribute working documents as
skipping to change at page 12, line ? skipping to change at page 12, line ?
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>.
A version of this draft document is intended for submission to the A version of this draft document is intended for submission to the
RFC editor as a Proposed Standard for the Internet Community. RFC editor as a Proposed Standard for the Internet Community.
Discussion and suggestions for improvement are requested. Discussion and suggestions for improvement are requested.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society 2000. All Rights Reserved. Copyright (C) The Internet Society 2001. All Rights Reserved.
Gellens Expires August 2000 [Page 1] Internet Draft ACAP Email Account Dataset Class February 2000
Table of Contents Table of Contents
1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in this Document . . . . . . . . . . . . . 2 2. Conventions Used in this Document . . . . . . . . . . . . . 2
3. Changes Since the Previous Version . . . . . . . . . . . . . 2 3. Changes Since the Previous Version . . . . . . . . . . . . . 2
4. Comments . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Comments . . . . . . . . . . . . . . . . . . . . . . . . . 2
5. ACAP Standard Options . . . . . . . . . . . . . . . . . . . 3 5. ACAP Standard Options . . . . . . . . . . . . . . . . . . . 3
6. ACAP Email Account Dataset Class . . . . . . . . . . . . . 3 6. ACAP Email Account Dataset Class . . . . . . . . . . . . . 3
6.1. ACAP Email Account Dataset Class Prefix . . . . . . . . 3 6.1. ACAP Email Account Dataset Class Prefix . . . . . . . . 3
6.2. ACAP Email Account Dataset Hierarchy . . . . . . . . . 3 6.2. ACAP Email Account Dataset Hierarchy . . . . . . . . . 3
7. ACAP Email Account Dataset Attributes . . . . . . . . . . . 4 7. ACAP Email Account Dataset Attributes . . . . . . . . . . . 3
7.1. Basic Attributes . . . . . . . . . . . . . . . . . . . 4 7.1. Basic Attributes . . . . . . . . . . . . . . . . . . . 4
7.2. Specific Attributes . . . . . . . . . . . . . . . . . . 4 7.2. Specific Attributes . . . . . . . . . . . . . . . . . . 4
8. Dataset Class Capabilities . . . . . . . . . . . . . . . . 9 8. Dataset Class Capabilities . . . . . . . . . . . . . . . . 9
9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 9
10. References . . . . . . . . . . . . . . . . . . . . . . . . 10 10. References . . . . . . . . . . . . . . . . . . . . . . . . 10
11. Security Considerations . . . . . . . . . . . . . . . . . . 11 11. Security Considerations . . . . . . . . . . . . . . . . . . 11
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 11 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 11
13. Author's Address . . . . . . . . . . . . . . . . . . . . . . 11 13. Author's Address . . . . . . . . . . . . . . . . . . . . . . 11
14. Full Copyright Statement . . . . . . . . . . . . . . . . . 11 14. Full Copyright Statement . . . . . . . . . . . . . . . . . 11
skipping to change at page 12, line ? skipping to change at page 12, line ?
account. account.
2. Conventions Used in this Document 2. Conventions Used in this Document
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 RFC 2119 [KEYWORDS]. document are to be interpreted as described in RFC 2119 [KEYWORDS].
3. Changes Since the Previous Version 3. Changes Since the Previous Version
- Added attributes: - Cleaned up examples.
email.mailbox-prefix, - Minor text clarifications.
email.sieve.capability,
email.sieve.runtime.errors,
email.sieve.runtime.warnings,
Gellens Expires August 2000 [Page 2] Internet Draft ACAP Email Account Dataset Class February 2000
email.sieve.runtime.errtxt,
email.sieve.runtime.warntxt,
email.trash-folder.
- Fixed ABNF for email-sieve-errtxt.
- Added text for email.maximum.download-size regarding use with
IMAP [IMAP4].
- Added mention of multiple Sieve scripts.
- Clarified email vs. personalities datasets.
- Updated Sieve script examples.
- Added section on items in the "capabilities" dataset.
4. Comments 4. Comments
Public comments can be sent to the IETF ACAP mailing list, Public comments can be sent to the IETF ACAP mailing list,
<ietf-acap+@andrew.cmu.edu>. To subscribe, send a message to <ietf-acap+@andrew.cmu.edu>. To subscribe, send a message to
<ietf-acap-request+@andrew.cmu.edu> with the word SUBSCRIBE as the <ietf-acap-request+@andrew.cmu.edu> with the word SUBSCRIBE as the
body. Private comments should be sent to the author. body. Private comments should be sent to the author.
5. ACAP Standard Options 5. ACAP Standard Options
skipping to change at page 12, line ? skipping to change at page 12, line ?
Configuration information related to composing and sending mail is Configuration information related to composing and sending mail is
stored in the ACAP Email Personality Dataset Class stored in the ACAP Email Personality Dataset Class
[ACAP-PERSONALITY]. [ACAP-PERSONALITY].
6.1. ACAP Email Account Dataset Class Prefix 6.1. ACAP Email Account Dataset Class Prefix
Datasets whose names begin with "/email" are assumed to contain Datasets whose names begin with "/email" are assumed to contain
email account entries as defined in this specification. email account entries as defined in this specification.
Gellens Expires August 2000 [Page 3] Internet Draft ACAP Email Account Dataset Class February 2000
6.2. ACAP Email Account Dataset Hierarchy 6.2. ACAP Email Account Dataset Hierarchy
Each user may have a set of named email accounts. The default is Each user may have a set of named email accounts. The default is
pointed at by the "mua.default.account" standard option. (See pointed at by the "mua.default.account" standard option. (See
section 5, ACAP Standard Options, for more information.) section 5, ACAP Standard Options, for more information.)
Inheritance is likely to be useful both for inheriting site or group Inheritance is likely to be useful both for inheriting site or group
defaults (for example, POP or IMAP servers, and initial client defaults (for example, POP or IMAP servers, and initial client
configuration in general) as well as for inheriting user-specific configuration in general) as well as for inheriting user-specific
configuration when using different machines. configuration when using different machines.
skipping to change at page 12, line ? skipping to change at page 12, line ?
subdataset subdataset
The "subdataset" attribute indicates that there is a subdataset The "subdataset" attribute indicates that there is a subdataset
of this entry. The value of this attribute specifies the actual of this entry. The value of this attribute specifies the actual
location of the subdataset, per [ACAP] section 3.1.1. location of the subdataset, per [ACAP] section 3.1.1.
7.2. Specific Attributes 7.2. Specific Attributes
These attributes are specific to the Email Account dataset class. These attributes are specific to the Email Account dataset class.
Gellens Expires August 2000 [Page 4] Internet Draft ACAP Email Account Dataset Class February 2000
email.boring-headers email.boring-headers
This multi-valued attribute is a list of header prefixes. If This multi-valued attribute is a list of header prefixes. If
the client has a mode where it suppresses display of certain the client has a mode where it suppresses display of certain
headers and/or properties of messages, headers which start with headers and/or properties of messages, headers which start with
a prefix included in this attribute are candidates for a prefix included in this attribute are candidates for
suppression. Prefix strings are case-insensitive. suppression. Prefix strings are case-insensitive.
email-boring = 1*VCHAR email-boring = 1*VCHAR
email.check-interval email.check-interval
skipping to change at page 12, line ? skipping to change at page 12, line ?
email.leave-on-server.days email.leave-on-server.days
When email.leave-on-server.flag is set (value is "1"), this When email.leave-on-server.flag is set (value is "1"), this
attribute specifies the number of days messages should remain on attribute specifies the number of days messages should remain on
the server before being deleted by the client. This is the server before being deleted by the client. This is
generally useful only with POP servers [POP3] which support generally useful only with POP servers [POP3] which support
leaving mail on the server. Note that a value of "0" indicates leaving mail on the server. Note that a value of "0" indicates
that clients SHOULD never automatically delete mail from the that clients SHOULD never automatically delete mail from the
server. server.
Gellens Expires August 2000 [Page 5] Internet Draft ACAP Email Account Dataset Class February 2000
email-lmos-days = 1*DIGIT email-lmos-days = 1*DIGIT
email.maximum.download-size email.maximum.download-size
This contains the maximum size (in octets) of messages to be This contains the maximum size (in octets) of messages to be
downloaded. This is most useful when accessing messages via POP downloaded. This is most useful when accessing messages via POP
[POP3], although it might also be used with IMAP [IMAP4] to [POP3], although it might also be used with IMAP [IMAP4] to
specify a limit on the size of attachments to be downloaded. A specify a limit on the size of attachments to be downloaded. A
value of "0" indicates no limit. value of "0" indicates no limit.
email-max-dsize = 1*DIGIT email-max-dsize = 1*DIGIT
skipping to change at page 12, line ? skipping to change at page 12, line ?
email-pop = url ;defined in [URL-BASIC] email-pop = url ;defined in [URL-BASIC]
email.server.Local email.server.Local
This indicates that this email account refers to a mailstore on This indicates that this email account refers to a mailstore on
the local client. When set to "1", the "email.server.IMAP" and the local client. When set to "1", the "email.server.IMAP" and
"email.server.POP" attributes are ignored. "email.server.POP" attributes are ignored.
email-local = "0"/"1" email-local = "0"/"1"
email.sieve.capability email.sieve.capability
This multivalued attribute contains a list of Sieve capability This multivalued attribute contains a list of [SIEVE] capability
strings for extensions supported by the Sieve execution engine strings. These strings represent extensions supported by the
which processes the Sieve script contained in Sieve execution engine which processes the Sieve script
"email.sieve.script". contained in "email.sieve.script".
Gellens Expires August 2000 [Page 6] Internet Draft ACAP Email Account Dataset Class February 2000
Note that this attribute SHOULD NOT be modified except by the Note that this attribute SHOULD NOT be modified except by the
Sieve execution engine or its agent. Normally, this attribute Sieve execution engine or its agent. Normally, this attribute
is inherited from a site-specific dataset. is inherited from a site-specific dataset.
email-sieve-cap = 1*CHAR email-sieve-cap = 1*CHAR
email.sieve.script email.sieve.script
This specifies the text of a Sieve script which will be applied This specifies the text of a Sieve script which will be applied
by the delivery agent (if supported) to mail arriving at this by the delivery agent (if supported) to mail arriving at this
email account. Sieve is specified in [SIEVE]. email account. Sieve is specified in [SIEVE].
Note that multiple Sieve scripts may be stored. The active Note that multiple Sieve scripts may be stored. The active
script is always called "email.sieve.script", while additional script is always called "email.sieve.script", while additional
scripts may be stored in names of the form scripts may be stored in names of the form "email.sieve.foo",
"email.account.sieve.foo", where "foo" is the name of a where "foo" is the name of a non-active script.
non-active script.
email-sieve = 1*UTF8-CHAR email-sieve = 1*UTF8-CHAR
email.sieve.runtime.errors email.sieve.runtime.errors
If supported by the Sieve implementation (see section 8), this If supported by the Sieve implementation (see section 8), this
attribute contains the count of runtime errors detected in the attribute contains the count of runtime errors detected in the
currently active Sieve script. This count SHOULD be cleared currently active Sieve script. This count SHOULD be cleared
when a new script is stored. It MAY be reset at other times, at when a new script is stored. It MAY be reset at other times, at
the discretion of the server. Sieve is specified in [SIEVE]. the discretion of the server. Sieve is specified in [SIEVE].
skipping to change at page 12, line ? skipping to change at page 12, line ?
named attributes of the error, in a MIME-header-like format. named attributes of the error, in a MIME-header-like format.
The currently specified attributes are: line, offset, length, The currently specified attributes are: line, offset, length,
and text. Text MUST always be the last attribute. This and text. Text MUST always be the last attribute. This
attribute SHOULD be cleared when a new script is stored. It MAY attribute SHOULD be cleared when a new script is stored. It MAY
be reset at other times, at the discretion of the server. Sieve be reset at other times, at the discretion of the server. Sieve
is specified in [SIEVE]. is specified in [SIEVE].
The format is intended to be easy for a Sieve execution agent to The format is intended to be easy for a Sieve execution agent to
generate, and easy for a Sieve user agent to parse. The Sieve generate, and easy for a Sieve user agent to parse. The Sieve
user agent could use the information to highlight the indicated user agent could use the information to highlight the indicated
Gellens Expires August 2000 [Page 7] Internet Draft ACAP Email Account Dataset Class February 2000
section of the Sieve script text, as specified by the line, section of the Sieve script text, as specified by the line,
offset, and length. offset, and length.
email-sieve-errtxt = *(non-text-sieve-att ";" SP) email-sieve-errtxt = *(non-text-sieve-att ";" SP)
text-sieve-att CRLF text-sieve-att CRLF
non-text-sieve-att = sieve-att-line / sieve-att-off / non-text-sieve-att = sieve-att-line / sieve-att-off /
sieve-att-len / sieve-att-ext sieve-att-len / sieve-att-ext
text-sieve-att = "text" ":" SP 1*UTF8-CHAR text-sieve-att = "text" ":" SP 1*UTF8-CHAR
;MAY use ":" or ";" ;MAY use ":" or ";"
;MUST NOT use CRLF ;MUST NOT use CRLF
skipping to change at page 12, line ? skipping to change at page 12, line ?
email-sieve-synwarn = 1*DIGIT email-sieve-synwarn = 1*DIGIT
email.sieve.syntax.errtxt email.sieve.syntax.errtxt
If supported by the Sieve implementation (see section 8), this If supported by the Sieve implementation (see section 8), this
attribute contains the text of syntax errors detected in the attribute contains the text of syntax errors detected in the
most recently stored Sieve script. The error text is formated most recently stored Sieve script. The error text is formated
into CRLF-separated lines, one line per error, as specified for into CRLF-separated lines, one line per error, as specified for
"email.sieve.runtime.errtxt". Sieve is specified in [SIEVE]. "email.sieve.runtime.errtxt". Sieve is specified in [SIEVE].
Gellens Expires August 2000 [Page 8] Internet Draft ACAP Email Account Dataset Class February 2000
email-sieve-synerrtxt = email-sieve-errtxt email-sieve-synerrtxt = email-sieve-errtxt
email.sieve.syntax.warntxt email.sieve.syntax.warntxt
If supported by the Sieve implementation (see section 8), this If supported by the Sieve implementation (see section 8), this
attribute contains the text of syntax warnings detected in the attribute contains the text of syntax warnings detected in the
most recently stored Sieve script. The warning text is formated most recently stored Sieve script. The warning text is formated
into CRLF-separated lines, one line per warning, as specified into CRLF-separated lines, one line per warning, as specified
for "email.sieve.runtime.errtxt". Sieve is specified in for "email.sieve.runtime.errtxt". Sieve is specified in
[SIEVE]. [SIEVE].
skipping to change at page 12, line ? skipping to change at page 12, line ?
capability.email.sieve.syntax.errtxt capability.email.sieve.syntax.errtxt
capability.email.sieve.syntax.warntxt capability.email.sieve.syntax.warntxt
Note that these attributes SHOULD NOT be modified except by the Note that these attributes SHOULD NOT be modified except by the
server or an active client responsible for supporting the underlying server or an active client responsible for supporting the underlying
capability. These attributes are normally inherited from a capability. These attributes are normally inherited from a
site-specific dataset. site-specific dataset.
9. Examples 9. Examples
entry = "home" entry home
email.connection-type = "phone-modem" email.connection-type phone-modem
email.personality = "home" email.personality home
email.server.pop POP://jru;AUTH=APOP@pop.isp.com
Gellens Expires August 2000 [Page 9] Internet Draft ACAP Email Account Dataset Class February 2000 email.sieve.capability ("vacation" "mark")
email.sieve.script if header :matches "subject"
email.server.pop = "POP://jru;AUTH=APOP@pop.isp.com"
email.sieve.capability = ("vacation" "mark")
email.sieve.script = "if header :matches "subject"
[ "*make*money*fast*", [ "*make*money*fast*",
"*university*dipl*mas*" ] "*university*dipl*mas*" ]
{ {
discard; discard;
} }
email.boring-headers = ("received" "message" "x400") email.boring-headers ("received" "message" "x400")
entry = "work entry work
email.connection-type = "direct email.connection-type direct
email.personality = "work email.personality work
email.server.imap = "IMAP://jru@mail.bigcorp.com email.server.imap IMAP://jru@mail.bigcorp.com
email.sieve.capability = ("fileinto" "vacation" "envelope") email.sieve.capability ("fileinto" "vacation" "envelope")
email.sieve.script = {47} email.sieve.script if header :is "Sender"
if header :is "Sender"
"BigCheese@example.com" "BigCheese@example.com"
{ {
fileinto "Blatherings"; fileinto "Blatherings";
} }
email.trash-folder = "Trash" email.trash-folder Trash
10. References 10. References
[ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications: [ABNF] Crocker, Overell, "Augmented BNF for Syntax Specifications:
ABNF", RFC 2234, Internet Mail Consortium, Demon Internet Ltd., ABNF", RFC 2234, Internet Mail Consortium, Demon Internet Ltd.,
November 1997. <ftp://ftp.isi.edu/in-notes/rfc2234.txt> November 1997. <ftp://ftp.isi.edu/in-notes/rfc2234.txt>
[ACAP] Newman, Myers, "ACAP -- Application Configuration Access [ACAP] Newman, Myers, "ACAP -- Application Configuration Access
Protocol", RFC 2244, Innosoft, Netscape, November 1997. Protocol", RFC 2244, Innosoft, Netscape, November 1997.
<ftp://ftp.isi.edu/in-notes/rfc2244.txt> <ftp://ftp.isi.edu/in-notes/rfc2244.txt>
[ACAP-OPTIONS] Hole, "ACAP Application Options Dataset Class", The [ACAP-OPTIONS] Hole, "ACAP Application Options Dataset Class", The
Esys Corporation, Work in Progress, February 1998. Esys Corporation, work in Progress,
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-options-xx.txt> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-options-xx.txt>
[ACAP-PERSONALITY] Gellens, "ACAP Email Personality Dataset Class", [ACAP-PERSONALITY] Gellens, "ACAP Email Personality Dataset Class",
QUALCOMM Incorporated, Work in Progress. QUALCOMM Incorporated, work in Progress,
<ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-pers-xx.txt> <ftp://ftp.ietf.org/internet-drafts/draft-ietf-acap-pers-xx.txt>
[IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1", [IMAP4] Crispin, "Internet Message Access Protocol - Version 4rev1",
RFC 2060, University of Washington, December 1996. RFC 2060, University of Washington, December 1996.
[KEYWORDS] Bradner, "Key words for use in RFCs to Indicate [KEYWORDS] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March 1997. Requirement Levels", RFC 2119, Harvard University, March 1997.
<ftp://ftp.isi.edu/in-notes/rfc2119.txt> <ftp://ftp.isi.edu/in-notes/rfc2119.txt>
Gellens Expires August 2000 [Page 10] Internet Draft ACAP Email Account Dataset Class February 2000
[POP3] Myers, Rose, "Post Office Protocol -- Version 3", RFC 1939, [POP3] Myers, Rose, "Post Office Protocol -- Version 3", RFC 1939,
Carnegie Mellon, Dover Beach Consulting, Inc., May 1996. Carnegie Mellon, Dover Beach Consulting, Inc., May 1996.
<ftp://ftp.isi.edu/in-notes/rfc1939.txt> <ftp://ftp.isi.edu/in-notes/rfc1939.txt>
[SIEVE] Showalter, "Sieve -- a Mail Filtering Language", Carnegie [SIEVE] Showalter, "Sieve: A Mail Filtering Language", RFC 3028,
Mellon, Work in Progress. Mirapoint, Inc, January 2001.
<ftp://ftp.ietf.org/internet-drafts/draft-showalter-sieve-xx.txt>\ <ftp://ftp.isi.edu/in-notes/rfc3028.txt>
[URL-BASIC] Berners-Lee, Masinter, McCahill, "Uniform Resource [URL-BASIC] Berners-Lee, Masinter, McCahill, "Uniform Resource
Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of Locators (URL)", RFC 1738, CERN, Xerox Corporation, University of
Minnesota, December 1994. <ftp://ftp.isi.edu/in-notes/rfc1738.txt> Minnesota, December 1994. <ftp://ftp.isi.edu/in-notes/rfc1738.txt>
[URL-IMAP] Newman, "IMAP URL Scheme", RFC 2192, Innosoft, September [URL-IMAP] Newman, "IMAP URL Scheme", RFC 2192, Innosoft, September
1997. <ftp://ftp.isi.edu/in-notes/rfc2192.txt> 1997. <ftp://ftp.isi.edu/in-notes/rfc2192.txt>
[URL-POP] Gellens, "POP URL Scheme", RFC 2384, QUALCOMM [URL-POP] Gellens, "POP URL Scheme", RFC 2384, QUALCOMM
Incorporated, August 1998. <ftp://ftp.isi.edu/in-notes/rfc2384.txt> Incorporated, August 1998. <ftp://ftp.isi.edu/in-notes/rfc2384.txt>
[UTF8] Yergeau, F. "UTF-8, a transformation format of ISO 10646", [UTF8] Yergeau, F. "UTF-8, a transformation format of ISO 10646",
RFC 2279, Alis Technologies, January 1998. RFC 2279, Alis Technologies, January 1998.
<ftp://ftp.isi.edu/in-notes/rfc2279.txt> <ftp://ftp.isi.edu/in-notes/rfc2279.txt>
11. Security Considerations 11. Security Considerations
As with ACAP datasets in general, it is important that access As with ACAP datasets in general, it is important that access
skipping to change at page 12, line ? skipping to change at page 12, line ?
13. Author's Address 13. Author's Address
Randall Gellens +1 858 651 5115 Randall Gellens +1 858 651 5115
QUALCOMM Incorporated randy@qualcomm.com QUALCOMM Incorporated randy@qualcomm.com
5775 Morehouse Drive 5775 Morehouse Drive
San Diego, CA 92121-2779 San Diego, CA 92121-2779
U.S.A. U.S.A.
14. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society 2000. All Rights Reserved. Copyright (C) The Internet Society 2001. All Rights Reserved.
Gellens Expires August 2000 [Page 11] Internet Draft ACAP Email Account Dataset Class February 2000
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 22 change blocks. 
75 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/