draft-ietf-lemonade-architecture-01.txt   draft-ietf-lemonade-architecture-02.txt 
LEMONADE Working Group E. Burger LEMONADE Working Group E. Burger
Internet-Draft BEA Systems, Inc. Internet-Draft
Intended status: Informational G. Parsons Intended status: Informational G. Parsons
Expires: July 1, 2008 Nortel Networks Expires: November 17, 2008 Nortel Networks
December 29, 2007 May 16, 2008
LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet LEMONADE Architecture - Supporting OMA Mobile Email (MEM) using Internet
Mail Mail
draft-ietf-lemonade-architecture-01.txt draft-ietf-lemonade-architecture-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 36 skipping to change at page 1, line 36
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 July 1, 2008. This Internet-Draft will expire on November 17, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document specifies the architecture for mobile email, as This document specifies the architecture for mobile email, as
described by the OMA, using Internet Mail protocols. This described by the OMA, using Internet Mail protocols. This
architecture is the basis of the work of the LEMONADE WG and is a architecture is the basis of the work of the LEMONADE WG and is a
guideline for the LEMONADE Profile. guideline for the LEMONADE Profile.
Table of Contents Table of Contents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE 3.2.1. LEMONADE realization of OMA MEM with non-LEMONADE
IMAP servers . . . . . . . . . . . . . . . . . . . . . 9 IMAP servers . . . . . . . . . . . . . . . . . . . . . 9
3.2.2. LEMONADE realization of OMA MEM with non-IMAP 3.2.2. LEMONADE realization of OMA MEM with non-IMAP
servers . . . . . . . . . . . . . . . . . . . . . . . 10 servers . . . . . . . . . . . . . . . . . . . . . . . 10
4. Filters and server to client notifications and LEMONADE . . . 10 4. Filters and server to client notifications and LEMONADE . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
8. Informative References . . . . . . . . . . . . . . . . . . . . 12 8. Informative References . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . . . 14 Intellectual Property and Copyright Statements . . . . . . . . . . 15
1. Introduction 1. Introduction
This document describes the architecture of OMA mobile email (MEM) This document describes the architecture of OMA mobile email (MEM)
using Internet Mail protocols defined by the IETF. The LEMONADE work using Internet Mail protocols defined by the IETF. The LEMONADE work
group has enhanced many of these protocols for use in the mobile group has enhanced many of these protocols for use in the mobile
environment and are summarized in the LEMONADE profile [4] and its environment and are summarized in the LEMONADE profile [PROFILE] and
revision LEMONADE profile bis [5]. This document shows how the OMA its revision LEMONADE profile bis [PROFILE-bis]. This document shows
MEM Requirement document [2], OMA MEM Architecture [1], and OMA MEM how the OMA MEM Requirement document [MEM-req], OMA MEM Architecture
Technical Specification [3] relate to the work of LEMONADE. [MEM-arch], and OMA MEM Technical Specification [MEM-ts] relate to
the work of LEMONADE.
2. OMA Mobile Email (MEM) 2. OMA Mobile Email (MEM)
The OMA Mobile Email (MEM) sub-working group has spent some time The OMA Mobile Email (MEM) sub-working group has spent some time
studying the requirements and architecture of mobile email. IETF studying the requirements and architecture of mobile email. IETF
LEMONADE has been liaising with them and has based much of our LEMONADE has been liaising with them and has based much of our
Internet Mail enhancements based on their input. This section Internet Mail enhancements based on their input. This section
summarizes the output of the OMA. summarizes the output of the OMA.
2.1. OMA MEM Requirements 2.1. OMA MEM Requirements
The OMA MEM activity collected a set of use cases and derived The OMA MEM activity collected a set of use cases and derived
requirements for a mobile email enabler (MEM). The OMA MEM requirements for a mobile email enabler (MEM). The OMA MEM
Requirements [2] summarizes this work. Some requirements relates to Requirements [MEM-req] summarizes this work. Some requirements
email protocols, some involve other OMA technologies outside the relates to email protocols, some involve other OMA technologies
scope of IETF and some relate to implementations and normative outside the scope of IETF and some relate to implementations and
interoperability statements for clients and servers. normative interoperability statements for clients and servers.
2.2. OMA MEM Architecture 2.2. OMA MEM Architecture
This section introduces the OMA MEM Architecture. This section introduces the OMA MEM Architecture.
2.2.1. OMA MEM logical Architecture 2.2.1. OMA MEM logical Architecture
The OMA MEM activity has derived a logical architecture from the The OMA MEM activity has derived a logical architecture from the
requirements and use cases described in [2]. A simplification for requirements and use cases described in [MEM-req]. A simplification
illustrative purposes is shown in Figure 1, where arrows indicate for illustrative purposes is shown in Figure 1, where arrows indicate
content flows. content flows.
__________ __________
| Other | | Other |
+---| Mobile |<--+ +---| Mobile |<--+
| | Enablers | | | | Enablers | |
| |__________| | | |__________| |
|ME-4 |ME-3 |ME-4 |ME-3
_v____ ___v____ ________ _v____ ___v____ ________
| |ME-1 | | | | | |ME-1 | | | |
skipping to change at page 5, line 22 skipping to change at page 5, line 22
it) the MEM server or be a separate component. In such cases, it) the MEM server or be a separate component. In such cases,
interfaces to the email server are out of scope of the OMA MEM interfaces to the email server are out of scope of the OMA MEM
specifications. In the present document, we focus on the case where specifications. In the present document, we focus on the case where
the backend consists of IETF IMAP and Submit servers. However, we the backend consists of IETF IMAP and Submit servers. However, we
also discuss the relationship to other cases. The I2 interface is an also discuss the relationship to other cases. The I2 interface is an
OMA notation to designate protocol / interfaces that are not OMA notation to designate protocol / interfaces that are not
specified by the MEM enabler but may be standardized elsewhere. specified by the MEM enabler but may be standardized elsewhere.
2.2.2. OMA MEM Deployment Issues 2.2.2. OMA MEM Deployment Issues
The OMA MEM Architecture document [1] further identifies deployment The OMA MEM Architecture document [MEM-arch] further identifies
models. deployment models.
2.2.2.1. OMA MEM proxy 2.2.2.1. OMA MEM proxy
The OMA MEM Architecture document [1] identifies OMA MEM server The OMA MEM Architecture document [MEM-arch] identifies OMA MEM
proxies as server components that may be deployed ahead of firewalls server proxies as server components that may be deployed ahead of
to facilitate firewall traversal. firewalls to facilitate firewall traversal.
2.2.2.2. OMA MEM deployment cases 2.2.2.2. OMA MEM deployment cases
OMA MEM identifies that each component (MEM client, MEM servers, OMA MEM identifies that each component (MEM client, MEM servers,
other enablers, and the email server) may be deployed in different other enablers, and the email server) may be deployed in different
domains, possibly separated by firewalls and other network domains, possibly separated by firewalls and other network
intermediaries. MEM proxies may be involved in front of firewall intermediaries. MEM proxies may be involved in front of firewall
that protects the MEM server domain. that protects the MEM server domain.
OMA MEM targets support of configurations where: OMA MEM targets support of configurations where:
skipping to change at page 6, line 19 skipping to change at page 6, line 19
email server is in the domain of the email service provider email server is in the domain of the email service provider
The e-mail service provider can be either a third-party service The e-mail service provider can be either a third-party service
provider, a network service provider, or an enterprise e-mail provider, a network service provider, or an enterprise e-mail
service. service.
2.3. OMA MEM Technical Specification 2.3. OMA MEM Technical Specification
The OMA MEM activity will conclude with a specification for a mobile The OMA MEM activity will conclude with a specification for a mobile
email enabler (MEM). The ongoing work is in OMA MEM Technical email enabler (MEM). The ongoing work is in OMA MEM Technical
Specification [3]. LEMONADE is a basis for the mechanism. However, Specification [MEM-ts]. LEMONADE is a basis for the mechanism.
some additional details that are outside the scope of IETF will also However, some additional details that are outside the scope of IETF
be included. will also be included.
OMA provides ways to perform provisioning via OMA client provisioning OMA provides ways to perform provisioning via OMA client provisioning
and device management. Other provisioning specifications are and device management. Other provisioning specifications are
available (e.g., SMS based). available (e.g., SMS based).
OMA provides enablers to support out-of-band notification mechanisms, OMA provides enablers to support out-of-band notification mechanisms,
as well as filter specifications (such as XDM), remote device as well as filter specifications (such as XDM), remote device
deactivation, and other, non-Internet activities. deactivation, and other, non-Internet activities.
3. IETF LEMONADE Architecture 3. IETF LEMONADE Architecture
This section introduces the LEMONADE Architecture. This section introduces the LEMONADE Architecture.
The IETF LEMONADE activity has derived a LEMONADE profile [4] with The IETF LEMONADE activity has derived a LEMONADE profile
the logical architecture represented in Figure 2, where arrows [PROFILE-bis] with the logical architecture represented in Figure 2,
indicate content flows. where arrows indicate content flows.
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol | |Protocol |
| ___|______ | ___|______
| | | _____ | | | _____
skipping to change at page 7, line 30 skipping to change at page 7, line 30
\SUBMIT | \SUBMIT |
\ ____v_____ \ ____v_____
\ | | _____ \ | | _____
\ | LEMONADE | ESMTP | | \ | LEMONADE | ESMTP | |
---->| Submit |--------------->| MTA | ---->| Submit |--------------->| MTA |
| Server | |_____| | Server | |_____|
|__________| |__________|
Figure 2: LEMONADE logical architecture Figure 2: LEMONADE logical architecture
The LEMONADE profile [4] assumes: The LEMONADE profile [PROFILE] assumes:
o IMAP protocol [6] including LEMONADE profile extensions [4] o IMAP protocol [RFC3501] including LEMONADE profile extensions
o SUBMIT protocol [8], including LEMONADE profile extensions [PROFILE]
o SUBMIT protocol [RFC4409], including LEMONADE profile extensions
o LEMONADE profile compliant IMAP store connected to MTA (Mail o LEMONADE profile compliant IMAP store connected to MTA (Mail
Transfer Agent) via ESMTP [7] Transfer Agent) via ESMTP [RFC1861]
o LEMONADE profile compliant Submit server connected to MTA via o LEMONADE profile compliant Submit server connected to MTA via
ESMTP ESMTP
o Lemonade profile message store / submit server protocols (URLAUTH, o Lemonade profile message store / submit server protocols (URLAUTH,
BURL, CATENATE) (see lemonade Profile [4]). BURL, CATENATE) (see lemonade Profile [PROFILE]).
o Out-of-band server to client notifications relying on external o Out-of-band server to client notifications relying on external
notification mechanisms (and notification protocols) that may be notification mechanisms (and notification protocols) that may be
out of scope of the LEMONADE profile. out of scope of the LEMONADE profile.
o A LEMONADE aware MUA (Mail User Agent). While use of out-of-band o A LEMONADE aware MUA (Mail User Agent). While use of out-of-band
notification is described in the LEMONADE profile, support for the notification is described in the LEMONADE profile, support for the
underlying notifications mechanisms/protocols is out of scope of underlying notifications mechanisms/protocols is out of scope of
the LEMONADE specifications. the LEMONADE specifications.
Further details on the IETF email protocol stack and architecture can Further details on the IETF email protocol stack and architecture can
be found in [10] be found in [MAIL]
3.1. Relationship between the OMA MEM and LEMONADE logical 3.1. Relationship between the OMA MEM and LEMONADE logical
architectures architectures
Figure 3 illustrates the mapping of the IETF LEMONADE logical Figure 3 illustrates the mapping of the IETF LEMONADE logical
architecture on the OMA MEM logical architecture. architecture on the OMA MEM logical architecture.
_____________________ _____________________
| Other_Mob. Enablers | | Other_Mob. Enablers |
| |--------------| | | |--------------| |
_________| Notification | | _________| Notification | |
skipping to change at page 10, line 42 skipping to change at page 10, line 42
ME-2b | Server | | | |_____| ME-2b | Server | | | |_____|
|__________| |_____________| |__________| |_____________|
Figure 5: Architecture to support non-IMAP servers with a LEMONADE Figure 5: Architecture to support non-IMAP servers with a LEMONADE
realization of OMA MEM enabler. realization of OMA MEM enabler.
I2 designates proprietary adapters to the back-ends. I2 designates proprietary adapters to the back-ends.
4. Filters and server to client notifications and LEMONADE 4. Filters and server to client notifications and LEMONADE
OMA MEM RD [2] and AD [1] emphasize the need to provide mechanisms OMA MEM RD [MEM-req] and AD [MEM-arch] emphasize the need to provide
for server to client notifications of email events and filtering. mechanisms for server to client notifications of email events and
Figure 6 illustrates how notification and filtering works in the filtering. Figure 6 illustrates how notification and filtering works
LEMONADE profile [4]. in the LEMONADE profile [PROFILE].
______________ ______________
| | | |
_________| Notification | _________| Notification |
| | Mechanism | | | Mechanism |
| |______________| | |______________|
|Notif. ^ |Notif. ^
|Protocol -------\ _|__ |Protocol -------\ _|__
| ______| ___\>|NF|____ | ______| ___\>|NF|____
| | | ---- | _____ | | | ---- | _____
skipping to change at page 11, line 36 skipping to change at page 11, line 36
|__________| |__________|
Figure 6: Filtering mechanism defined in LEMONADE architecture Figure 6: Filtering mechanism defined in LEMONADE architecture
In Figure 6, we define four categories of filters: In Figure 6, we define four categories of filters:
o AF: Administrative Filters - The e-mail service provider usually o AF: Administrative Filters - The e-mail service provider usually
sets administrative filters. The user typically does not sets administrative filters. The user typically does not
configure AF. AF applies policies covering content filtering, configure AF. AF applies policies covering content filtering,
virus protection, spam filtering, etc. virus protection, spam filtering, etc.
o DF: Deposit Filters - Filters that are executed on deposit of new o DF: Deposit Filters - Filters that are executed on deposit of new
emails. They can be defined as SIEVE filters [9]. They can emails. They can be defined as SIEVE filters [SIEVE]. They can
include vacation notices. include vacation notices.
o VF: View Filters - Filters that define which emails are visible to o VF: View Filters - Filters that define which emails are visible to
the MUA. View filters can be performed via IMAP using the the MUA. View filters can be performed via IMAP using the
facilities described in [5]. facilities described in [NOTIFICATIONS].
o NF: Notification Filters - Filters that define for what email o NF: Notification Filters - Filters that define for what email
server event an out-of-band notification is sent to the client, as server event an out-of-band notification is sent to the client, as
described in [5]. described in [NOTIFICATIONS].
The MUA can manage the NF and DF filters using the SIEVE management The MUA can manage the NF and DF filters using the SIEVE management
protocol. protocol.
5. Security Considerations 5. Security Considerations
We note there are security risks associated with: We note there are security risks associated with:
o Out-of-band notifications o Out-of-band notifications
o Server configuration by client o Server configuration by client
skipping to change at page 12, line 24 skipping to change at page 12, line 24
6. IANA considerations 6. IANA considerations
None. None.
7. Acknowledgements 7. Acknowledgements
The authors acknowledge and appreciate the work and comments of the The authors acknowledge and appreciate the work and comments of the
IETF LEMONADE working group and the OMA MEM working group. We IETF LEMONADE working group and the OMA MEM working group. We
extracted the contents of this document from sections of extracted the contents of this document from sections of
draft-ietf-lemonade-profile-bis-05.txt and draft-ietf-lemonade-profile-bis-05.txt by Stephane Maes, Alexey
draft-ietf-lemonade-notifications-04.txt. Melnikov and Dave Cridland, as well as sections of
draft-ietf-lemonade-notifications-04.txt by Stephane Maes and Ray
Cromwell.
8. Informative References 8. Informative References
[1] Open Mobile Alliance, "Mobile Email Architecture Document", [MEM-arch]
June 2007, <http://member.openmobilealliance.org/ftp/ Open Mobile Alliance, "Mobile Email Architecture
public_documents/mwg/MEM/Permanent_documents/ Document", June 2007, <http://
member.openmobilealliance.org/ftp/public_documents/mwg/
MEM/Permanent_documents/
OMA-AD-Mobile_Email-V1_0_0-20070614-D.zip>. OMA-AD-Mobile_Email-V1_0_0-20070614-D.zip>.
[2] Open Mobile Alliance, "Mobile Email RequirementS Document", [MEM-req] Open Mobile Alliance, "Mobile Email Requirements
OMA http://www.openmobilealliance.org/, Oct 2005. Document", OMA http://www.openmobilealliance.org/,
Oct 2005.
[3] Open Mobile Alliance, "Mobile Email Technical Specification", [MEM-ts] Open Mobile Alliance, "Mobile Email Technical
OMA (Work in Progress), http://www.openmobilealliance.org/, Specification", OMA (Work in Progress),
Oct 2007. http://www.openmobilealliance.org/, Oct 2007.
[4] Maes, S. and A. Melnikov, "Internet Email to Support Diverse [PROFILE] Maes, S. and A. Melnikov, "Internet Email to Support
Service Environments (Lemonade) Profile", RFC 4550, June 2006. Diverse Service Environments (Lemonade) Profile",
RFC 4550, June 2006.
[5] Cridland, D., Melnikov, A., and S. Maes, "The Lemonade [PROFILE-bis]
Profile", draft-ietf-lemonade-profile-bis-07 (work in Cridland, D., Melnikov, A., and S. Maes, "The Lemonade
progress), November 2007. Profile", draft-ietf-lemonade-profile-bis-08 (work in
progress), February 2008.
[6] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION [RFC3501] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION
4rev1", RFC 3501, March 2003. 4rev1", RFC 3501, March 2003.
[7] Gwinn, R., "Simple Network Paging Protocol - Version 3 -Two-Way [RFC1861] Gwinn, R., "Simple Network Paging Protocol - Version 3
Enhanced", RFC 1861, October 1995. -Two-Way Enhanced", RFC 1861, October 1995.
[8] Gellens, R. and J. Klensin, "Message Submission for Mail", [RFC4409] Gellens, R. and J. Klensin, "Message Submission for Mail",
RFC 4409, April 2006. RFC 4409, April 2006.
[9] Guenther, P. and T. Showalter, "Seive: An Email Filtering [SIEVE] Guenther, P. and T. Showalter, "Seive: An Email Filtering
Language", October 2007, <http://www.ietf.org/internet-drafts/ Language", RFC 5528, January 2008,
draft-ietf-sieve-3028bis-13.txt>. <ftp://ftp.isi.edu/in-notes/rfc5528.txt>.
[10] Crocker, D., "Internet Mail Architecture", [NOTIFICATIONS]
draft-crocker-email-arch-09 (work in progress), May 2007. Gellens, R. and S. Maes, "Lemonade Notifications
Architecture", draft-ietf-lemonade-notifications-08 (work
in progress), April 2008.
[MAIL] Crocker, D., "Internet Mail Architecture",
draft-crocker-email-arch-10 (work in progress),
February 2008.
Authors' Addresses Authors' Addresses
Eric W. Burger Eric W. Burger
BEA Systems, Inc. New Hampshire
4 Van de Graaf Dr.
Burlington, MA 01803
USA USA
Phone: +1 781 993 7437 Phone:
Fax: Fax:
Email: eric.burger@bea.com Email: eburger@standardstrack.com
URI: http://www.standardstrack.com URI: http://www.standardstrack.com
Glenn Parsons Glenn Parsons
Nortel Networks Nortel Networks
3500 Carling Avenue 3500 Carling Avenue
Ottawa, ON K2H 8E9 Ottawa, ON K2H 8E9
Canada Canada
Phone: +1 613 763 7582 Phone: +1 613 763 7582
Email: gparsons@nortel.com Email: gparsons@nortel.com
Full Copyright Statement Full Copyright Statement
skipping to change at page 14, line 7 skipping to change at page 15, line 7
Nortel Networks Nortel Networks
3500 Carling Avenue 3500 Carling Avenue
Ottawa, ON K2H 8E9 Ottawa, ON K2H 8E9
Canada Canada
Phone: +1 613 763 7582 Phone: +1 613 763 7582
Email: gparsons@nortel.com Email: gparsons@nortel.com
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. 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, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
skipping to change at page 14, line 44 skipping to change at line 598
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. 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 that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 37 change blocks. 
75 lines changed or deleted 83 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/