ENUM R. Brandner Internet-Draft Siemens AG Expires: November 22, 2004 L. Conroy Siemens Roke Manor Research R. Stastny Oefeg May 24, 2004 IANA Registration for ENUMservices email, fax, mms, ems and sms Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on November 22, 2004. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document registers the 'ENUMservices' [6] 'email', 'fax', 'sms', 'ems' and 'mms' using the URI schemes 'tel:', 'mailto:', 'sip:' and 'sips:' as per the IANA registration process defined in the ENUM specification RFC3761 [6]. Brandner, et al. Expires November 22, 2004 [Page 1] Internet-Draft IANA Registration for Message ENUMservices May 2004 Table of Contents 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. E-mail Service Registration . . . . . . . . . . . . . . . . . 6 4. Fax Service Registration . . . . . . . . . . . . . . . . . . . 8 5. MMS, EMS, SMS Service . . . . . . . . . . . . . . . . . . . . 9 5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 9 5.2 SMS Service Registrations . . . . . . . . . . . . . . . . 9 5.2.1 SMS Service Registration with tel: URI . . . . . . . . 9 5.2.2 SMS Service Registration with mailto: URI . . . . . . 10 5.2.3 SMS Service Registration with sip: URI . . . . . . . . 10 5.3 EMS Service Registrations . . . . . . . . . . . . . . . . 11 5.3.1 EMS Service Registration with tel: URI . . . . . . . . 11 5.3.2 SMS Service Registration with mailto: URI . . . . . . 12 5.3.3 EMS Service Registration with sip: URI . . . . . . . . 13 5.4 MMS Service Registrations . . . . . . . . . . . . . . . . 13 5.4.1 MMS Service Registration with tel: URI . . . . . . . . 13 5.4.2 MMS Service Registration with mailto: URI . . . . . . 14 5.4.3 MMS Service Registration with sip: URI . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 8.1 Normative References . . . . . . . . . . . . . . . . . . . 19 8.2 Informative References . . . . . . . . . . . . . . . . . . 20 9. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 20 10. Full Copyright Statements. . . . . . . . . . . . . . . . . . . 22 Brandner, et al. Expires November 22, 2004 [Page 2] Internet-Draft IANA Registration for Message ENUMservices May 2004 1. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC2119 [2]. Brandner, et al. Expires November 22, 2004 [Page 3] Internet-Draft IANA Registration for Message ENUMservices May 2004 2. Introduction ENUM (E.164 Number Mapping, RFC3761 [6]) is a system that transforms E.164 numbers [7] into domain names and then uses DNS (Domain Name Service, RFC1034 [8]) services like delegation through NS records and NAPTR records to look up what services are available for a specific domain name. This document registers 'ENUMservices' according to the guidelines given in RFC3761 to be used for provisioning in the services field of a NAPTR [11] resource record to indicate what class of functionality a given end point offers. The registration is defined within the DDDS (Dynamic Delegation Discovery System [9][10][11][12][13]) hierarchy, for use with the "E2U" DDDS Application defined in RFC3761. The following 'ENUMservices' are registered with this document: 'email', 'fax', 'sms', 'ems' and 'mms'. These share a common feature in that they each indicate that the functionality of the given end points and the associated resources are capable of receiving discrete messages, albeit of different types. According to RFC3761, the 'ENUMservice' registered must be able to function as a selection mechanism when choosing one NAPTR resource record from another. That means that the registration MUST specify what is expected when using that very NAPTR record, and the URI scheme which is the outcome of the use of it. Therefore an 'ENUMservice' acts as a hint, indicating the kind of service with which the URI constructed using the regexp field is associated. There can be more than one 'ENUMservice' included within a single NAPTR; this indicates that there is more than one service that can be achieved using the associated URI scheme. The common thread with this set of definitions is that they reflect the kind of service that the end user will hope to achieve with the communication using the associated URI. The services specified here are intended NOT to specify the protocol or even method of connection that MUST be used to achieve each service. Instead they define the kind of interactive behavior that an end user will expect, leaving the end system to decide (based on policies outside the remit of this specification) how to execute the service. Since the same URI scheme may be used for different services (e.g. 'tel:'), and the same kind of service may use different URI schemes (e.g. for VoIP 'h323:' and 'tel:' may be used), it is necessary in Brandner, et al. Expires November 22, 2004 [Page 4] Internet-Draft IANA Registration for Message ENUMservices May 2004 some cases to specify the service and the URI scheme used. The service parameters defined in RFC3761 allow therefore a 'type' and a 'subtype' to be specified. Within this set of specifications the convention is assumed that the 'type' (being the more generic term) is defining the service and the 'subtype' is defining the URI scheme. Although currently only one URI scheme is associated with a given service, it should be considered that an additional URI scheme to be used with this service may be added later. Thus the subtype is needed to identify the specific 'ENUMservice' intended. Brandner, et al. Expires November 22, 2004 [Page 5] Internet-Draft IANA Registration for Message ENUMservices May 2004 3. E-mail Service Registration Enumservice Name: "email" Enumservice Type: "email" Enumservice Subtype: "mailto" URI Scheme: 'mailto:' Functional Specification: This ENUMservice indicates that the remote resource can be addressed by the associated URI scheme in order to send an email. Security Considerations: An e-mail address is a canonical address by which a user is known. Placing this address in ENUM is comparable to placing a SIP or H.323 address in the DNS. DNS does not make any policy decisions about the records that it shares with an inquirer. All DNS records must be assumed to be available to all inquirers at all times. The information provided within an ENUM NAPTR resource record must therefore be considered to be open to the public, which is a cause for some privacy considerations. Therefore ENUM Subscribers should be made aware of this risk. Since it is within the responsibility of the ENUM Subscriber which data is entered in ENUM, it is within the ENUM Subscribers control if he enters e-mail addresses: 1. allowing inference of private data e.g. his first and last name 2. at all It should also be considered that it is the purpose of public communication identifiers to be publicly known. To reduce spam and other unwanted communication other means should be made available. See also Section 6. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Brandner, et al. Expires November 22, 2004 [Page 6] Internet-Draft IANA Registration for Message ENUMservices May 2004 Any other information the author deems interesting: None Brandner, et al. Expires November 22, 2004 [Page 7] Internet-Draft IANA Registration for Message ENUMservices May 2004 4. Fax Service Registration Enumservice Name: "fax" Enumservice Type: "fax" Enumservice Subtype: "tel" URI Scheme: 'tel:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of being contacted to provide a communication session during which facsimile documents can be sent. A client selecting this NAPTR will have support for generating and sending facsimile documents to the recipient using the PSTN session and transfer protocols specified in [3] and [4] - in short, they will have a fax program with a local or shared PSTN access over which they can send faxes. Security Considerations: An fax number as any other phone number may give not so much privacy away then a name in the format user@host (e.g. an email or sip address), but there is still the risk of unwanted messages. Therefore in principle the same applies as stated in the security consideration for e-mail. See also Section 6. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: None Brandner, et al. Expires November 22, 2004 [Page 8] Internet-Draft IANA Registration for Message ENUMservices May 2004 5. MMS, EMS, SMS Service 5.1 Introduction An ENUM NAPTR indicates ability on the part of the Subscriber to receive specified communication service (or services) provided via the contact address (shown in the generated URI). In the case of MMS, EMS, and SMS services, the capability of these services is a nested superset; thus a service supporting MMS can support also delivery of EMS or SMS messages to a recipient, whilst a service supporting EMS can also deliver SMS messages. Thus, if a client is capable only of generating and sending an SMS message, they MAY choose to consider also NAPTRs indicating support for EMS and MMS services as well as SMS, as these services will be able to deliver an SMS message to the recipient address. Conversely, a client capable of sending MMS messages may choose to consider also NAPTRs indicating support for EMS or SMS messages, "downgrading" their User Interface to allow only generation of messages that conform to SMS or EMS standards. These behaviours on the part of the client are purely optional, and are NOT the subject of any protocol standardization. 5.2 SMS Service Registrations 5.2.1 SMS Service Registration with tel: URI Enumservice Name: "sms" Enumservice Type: "sms" Enumservice Subtypes: "tel" URI Scheme: 'tel:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the Short Message Service (SMS) [16]. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Brandner, et al. Expires November 22, 2004 [Page 9] Internet-Draft IANA Registration for Message ENUMservices May 2004 Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: None 5.2.2 SMS Service Registration with mailto: URI Enumservice Name: "sms" Enumservice Type: "sms" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: None 5.2.3 SMS Service Registration with sip: URI Enumservice Name: "sms" Enumservice Type: "sms" Brandner, et al. Expires November 22, 2004 [Page 10] Internet-Draft IANA Registration for Message ENUMservices May 2004 Enumservice Subtypes: "sip" URI Scheme: 'sip:', 'sips:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the SIP [14] protocol or using SIP with a secure connection (using TLS), respectively. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: In SIP requests various types of URIs can be present. Depending on the purpose one can address a particular SIP user agent or an identity. The first is commonly known as SIP contact address, the latter as Address-of-record (AoR). It is recommended to read RFC3764 [15] for more information on this topic. 5.3 EMS Service Registrations 5.3.1 EMS Service Registration with tel: URI Enumservice Name: "ems" Enumservice Type: "ems" Enumservice Subtype: "tel" URI Scheme: 'tel:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the Enhanced Message Service (EMS) [16]. Brandner, et al. Expires November 22, 2004 [Page 11] Internet-Draft IANA Registration for Message ENUMservices May 2004 Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: Note that an indication of EMS can be taken as implying that the recipient is capable of receiving SMS messages at this address as well. 5.3.2 SMS Service Registration with mailto: URI Enumservice Name: "ems" Enumservice Type: "ems" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: Brandner, et al. Expires November 22, 2004 [Page 12] Internet-Draft IANA Registration for Message ENUMservices May 2004 None 5.3.3 EMS Service Registration with sip: URI Enumservice Name: "ems" Enumservice Type: "ems" Enumservice Subtypes: "sip" URI Scheme: 'sip:', 'sips:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the SIP [14] protocol or using SIP with a secure connection (using TLS), respectively. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: In SIP requests various types of URIs can be present. Depending on the purpose one can address a particular SIP user agent or an identity. The first is commonly known as SIP contact address, the latter as Address-of-record (AoR). It is recommended to read RFC3764 [15] for more information on this topic. 5.4 MMS Service Registrations 5.4.1 MMS Service Registration with tel: URI Enumservice Name: "mms" Enumservice Type: "mms" Enumservice Subtype: "tel" Brandner, et al. Expires November 22, 2004 [Page 13] Internet-Draft IANA Registration for Message ENUMservices May 2004 URI Scheme: 'tel:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the Multimedia Messaging Service (MMS) [17]. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: Note that MMS can be used as an alternative to deliver an SMS RP-DATA RPDU if, for example, the SMS bearer is not supported. If an entry includes this ENUMservice, then in effect this can be taken as implying that the recipient is capable of receiving EMS or SMS messages at this address. Such choices on the end system design do have a small caveat; whilst in practise all terminals supporting MMS today support SMS as well, it might not necessarily be the case in the future. 5.4.2 MMS Service Registration with mailto: URI Enumservice Name: "mms" Enumservice Type: "mms" Enumservice Subtypes: "mailto" URI Scheme: 'mailto:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using an email protocol. Security Considerations: Brandner, et al. Expires November 22, 2004 [Page 14] Internet-Draft IANA Registration for Message ENUMservices May 2004 There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: None 5.4.3 MMS Service Registration with sip: URI Enumservice Name: "mms" Enumservice Type: "mms" Enumservice Subtypes: "sip" URI Scheme: 'sip:', 'sips:' Functional Specification: This ENUMservice indicates that the resource identified by the associated URI scheme is capable of receiving a message using the SIP [14] protocol or using SIP with a secure connection (using TLS), respectively. Security Considerations: There are no specific security issues with this 'ENUMservice'. However, the general considerations of Section 6 apply. Intended Usage: COMMON Author: Rudolf Brandner, Lawrence Conroy, Richard Stastny (for author contact detail see Authors' Addresses section) Any other information the author deems interesting: In SIP requests various types of URIs can be present. Depending on the purpose one can address a particular SIP user agent or an identity. The first is commonly known as SIP contact address, the Brandner, et al. Expires November 22, 2004 [Page 15] Internet-Draft IANA Registration for Message ENUMservices May 2004 latter as Address-of-record (AoR). It is recommended to read RFC3764 [15] for more information on this topic. Brandner, et al. Expires November 22, 2004 [Page 16] Internet-Draft IANA Registration for Message ENUMservices May 2004 6. Security Considerations DNS, as used by ENUM, is a global, distributed database. Thus any information stored there is visible to anyone anonymously. Whilst this is not qualitatively different from publication in a Telephone Directory, it does open the data subject to having "their" information collected automatically without any indication that this has been done or by whom. Such data harvesting by third parties is often used to generate lists of targets for unrequested information; in short, they are used to address "spam". Anyone who uses a Web-archived mailing list is aware that the volume of "spam" email they are sent increases when they post to the mailing list; publication of a telephone number in ENUM is no different, and may be used to send "junk faxes" or "junk SMS" for example. Many mailing list users have more than one email address and use "sacrificial" email accounts when posting to such lists to help filter out unrequested emails sent to them. This is not so easy with published telephone numbers; the PSTN E.164 number assignment process is much more involved and usually a single E.164 number (or a fixed range of numbers) is associated with each PSTN access. Thus providing a "sacrificial" phone number in any publication is not possible. Due to the implications of publishing data on a globally accessible database, as a principle the data subject MUST give their explicit informed consent to data being published in ENUM. In addition, they should be made aware that, due to storage of such data during harvesting by third parties, removal of the data from publication will not remove any copies that have been taken; in effect, any publication may be permanent. However, regulations in many regions will require that the data subject can at any time request that the data is removed from publication, and that their consent for its publication is explicitly confirmed at regular intervals. When placing a fax call via the PSTN or a sending a message via the Public Land Mobile Network, the sender may be charged for this action. In both kinds of network, calling or messaging to some numbers is more expensive than sending to others; both networks have "premium rate" services that can charge considerably more than a "normal" call or message destination. As such, it is important that the end user be asked to confirm sending the message, and that the destination number be presented to them. It is the originating Brandner, et al. Expires November 22, 2004 [Page 17] Internet-Draft IANA Registration for Message ENUMservices May 2004 user's choice on whether or not to send a message to this destination number, but they SHOULD be shown the destination number so that they can make this decision. An analysis of threats specific to the dependence of ENUM on the DNS, and the applicability of DNSSEC [19] to these, is provided in RFC3761 [6]. Brandner, et al. Expires November 22, 2004 [Page 18] Internet-Draft IANA Registration for Message ENUMservices May 2004 7. Acknowledgements Many thanks to Ville Warsta for his close reading of the draft and extracting the right references. 8. References 8.1 Normative References [1] Bradner, S., "The Internet Standards Process -- Revision 3", RFC 2026, BCP 9, October 1996. [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [3] ITU-T, "Standardization of Group 3 facsimile terminals for document transmission", T.4 , April 1999. [4] ITU-T, "Procedures for document facsimile transmission in the general switched telephone network", T.30 , April 1999. [5] Schulzrinne, H., "The tel URI for Telephone Numbers", draft-ietf-iptel-rfc2806bis-07 , April 2004. [6] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004. [7] ITU-T, "The International Public Telecommunication Number Plan", Recommendation E.164 , May 1997. [8] Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES", RFC 1034, November 1987. [9] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS", RFC 3401, October 2002. [10] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm", RFC 3402, October 2002. [11] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403, October 2002. [12] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)", RFC 3404, October 2002. [13] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Five: URI.ARPA Assignment Procedures", RFC 3405, October 2002. Brandner, et al. Expires November 22, 2004 [Page 19] Internet-Draft IANA Registration for Message ENUMservices May 2004 [14] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002. [15] Peterson, J., "enumservice registration for Session Initiation Protocol (SIP) Address-of-Record", RFC 3764, April 2004. [16] 3GPP, "Technical realization of the Short Message Service (SMS); (Release5)", TS 23.040 . [17] 3GPP, "Multimedia Messaging Service (MMS); Functional description; Stage 2 (Release 5)", TS 23.140 . [18] ETSI, "Minimum Requirements for Interoperability of European ENUM Trials", ETSI TS 102 172, February 2004. 8.2 Informative References [19] Arends, R. and et al. , "Protocol Modifications for the DNS Security Extensions", Work in Progress . Authors' Addresses Rudolf Brandner Siemens AG Hofmannstr. 51 81359 Munich Germany Phone: +49-89-722-51003 EMail: rudolf.brandner@siemens.com Lawrence Conroy Siemens Roke Manor Research Roke Manor Romsey United Kingdom Phone: +44-1794-833666 EMail: lwc@roke.co.uk Brandner, et al. Expires November 22, 2004 [Page 20] Internet-Draft IANA Registration for Message ENUMservices May 2004 Richard Stastny Oefeg Postbox 147 1103 Vienna Austria Phone: +43-664-420-4100 EMail: Richard.stastny@oefeg.at Brandner, et al. Expires November 22, 2004 [Page 21] Internet-Draft IANA Registration for Message ENUMservices May 2004 10. Full Copyright Statement Copyright (C) The Internet Society (2004). 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 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this 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 copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society. Brandner, et al. Expires November 22, 2004 [Page 22]