idnits 2.17.1
draft-wilde-sms-uri-03.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** Looks like you're using RFC 2026 boilerplate. This must be updated to
follow RFC 3978/3979, as updated by RFC 4748.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
== No 'Intended status' indicated for this document; assuming Proposed
Standard
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
match the current year
== The document seems to lack the recommended RFC 2119 boilerplate, even if
it appears to use RFC 2119 keywords.
(The document does seem to have the reference to RFC 2119 which the
ID-Checklist requires).
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (April 16, 2002) is 8045 days in the past. Is this
intentional?
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
-- Possible downref: Non-RFC (?) normative reference: ref. 'HTML401'
** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234)
** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629)
** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986)
-- Possible downref: Non-RFC (?) normative reference: ref. 'SMS'
-- Possible downref: Non-RFC (?) normative reference: ref. 'SMS-CHAR'
-- Obsolete informational reference (is this intentional?): RFC 2368
(Obsoleted by RFC 6068)
-- Obsolete informational reference (is this intentional?): RFC 2629
(Obsoleted by RFC 7749)
-- Obsolete informational reference (is this intentional?): RFC 2806
(Obsoleted by RFC 3966)
Summary: 5 errors (**), 0 flaws (~~), 3 warnings (==), 8 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 Network Working Group E. Wilde
3 Internet-Draft Swiss Federal Institute of
4 Expires: October 15, 2002 Technology
5 A. Vaha-Sipila
6 Nokia
7 April 16, 2002
9 URI scheme for GSM Short Message Service
10 draft-wilde-sms-uri-03
12 Status of this Memo
14 This document is an Internet-Draft and is in full conformance with
15 all provisions of Section 10 of RFC2026.
17 Internet-Drafts are working documents of the Internet Engineering
18 Task Force (IETF), its areas, and its working groups. Note that
19 other groups may also distribute working documents as Internet-
20 Drafts.
22 Internet-Drafts are draft documents valid for a maximum of six months
23 and may be updated, replaced, or obsoleted by other documents at any
24 time. It is inappropriate to use Internet-Drafts as reference
25 material or to cite them other than as "work in progress."
27 The list of current Internet-Drafts can be accessed at http://
28 www.ietf.org/ietf/1id-abstracts.txt.
30 The list of Internet-Draft Shadow Directories can be accessed at
31 http://www.ietf.org/shadow.html.
33 This Internet-Draft will expire on October 15, 2002.
35 Copyright Notice
37 Copyright (C) The Internet Society (2002). All Rights Reserved.
39 Abstract
41 This memo specifies a URI (Universal Resource Identifier) scheme
42 "sms" for specifying a recipient (and optionally a gateway) for an
43 SMS message. SMS messages are two-way paging messages that can be
44 sent from and received by a mobile phone or a suitably equipped
45 computer.
47 Table of Contents
49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
50 1.1 The Short Message Service . . . . . . . . . . . . . . . . . 3
51 1.2 Universal Resource Identifiers . . . . . . . . . . . . . . . 3
52 1.3 SMS Messages and the Internet . . . . . . . . . . . . . . . 3
53 1.3.1 SMS Messages and the Web . . . . . . . . . . . . . . . . . . 4
54 1.3.2 SMS Messages and Forms . . . . . . . . . . . . . . . . . . . 5
55 2. The "sms" URI Scheme . . . . . . . . . . . . . . . . . . . . 5
56 2.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . 5
57 2.2 Formal Definition . . . . . . . . . . . . . . . . . . . . . 6
58 2.3 Parsing an "sms" URI . . . . . . . . . . . . . . . . . . . . 6
59 2.4 Examples of Use . . . . . . . . . . . . . . . . . . . . . . 7
60 2.5 Using "sms" URIs in HTML Forms . . . . . . . . . . . . . . . 8
61 3. "sms" URIs and SMS Web Services . . . . . . . . . . . . . . 8
62 3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . 9
63 4. Security Considerations . . . . . . . . . . . . . . . . . . 10
64 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 10
65 5.1 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . . 10
66 5.2 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . . 11
67 5.3 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . . 11
68 Normative References . . . . . . . . . . . . . . . . . . . . 11
69 Non-Normative References . . . . . . . . . . . . . . . . . . 12
70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 13
71 A. Where to send Comments . . . . . . . . . . . . . . . . . . . 13
72 B. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
73 Full Copyright Statement . . . . . . . . . . . . . . . . . . 14
75 1. Introduction
77 Compliant software MUST follow this specification. The capitalized
78 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
79 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
80 document are to be interpreted as described in RFC 2119 [RFC2119].
82 1.1 The Short Message Service
84 The Short Message Service (SMS) [SMS] is a rather simple service for
85 sending messages between SMS clients or, using so-called "Telematic
86 Interworking", from an SMS client through a gateway to a receiver
87 using a different service, such as fax or email. The SMS service is
88 described in more detail in the SMS service registration memo [draft-
89 wilde-sms-service-03].
91 1.2 Universal Resource Identifiers
93 One of the core specifications for identifying resources on the
94 Internet is RFC 2396 [RFC2396], specifying the syntax and semantics
95 of a Universal Resource Identifier (URI). The most important notion
96 of URIs are "schemes", which define a framework within which
97 resources can be identified (and possibly accessed). URIs enable
98 users to identify resources, and are used for very diverse schemes
99 such as access protocols (HTTP, FTP), broadcast media (TV channels
100 [RFC2838]), messaging (email [RFC2368]), or even telephone numbers
101 (voice [RFC2806]).
103 URIs often are mentioned together with Universal Resource Names
104 (URNs) and/or Uniform Resource Locators (URLs), and it often is
105 unclear how to separate these concepts. For the purpose of this
106 memo, only the term URI will be used, referring to the most
107 fundamental concept. The World Wide Web Consortium (W3C) has issued
108 a note [uri-clarification] discussing the topic of URIs, URNs, and
109 URLs in detail.
111 1.3 SMS Messages and the Internet
113 One of the important reasons for the universal access of the Web is
114 the ability to access all information through a unique interface.
115 This kind of integration makes it easy to provide information as well
116 as to consume it. One aspect of this integration is the support of
117 user agents (in the case of the Web, commonly referred to as
118 browsers) for multiple content formats (such as HTML, GIF, JPEG) and
119 access schemes (such as HTTP, HTTP-S, FTP).
121 The "mailto" scheme has proven to be very useful and popular, because
122 most user agents support it by providing an email composition
123 facility when the user activates (eg, clicks on) the URI.
124 Accordingly, the "sms" scheme could be supported by user agents by
125 providing an SMS message composition facility when the user activates
126 the URI. Alternatively, in cases where the user agent does not
127 provide a built-in SMS message composition facility, the scheme could
128 still be supported by opening a Web page which provides such a
129 service. The specific Web page to be used could be configured by the
130 user, so that each user could use the SMS message composition service
131 of his choice.
133 The goal of this memo is to specify the "sms" URI scheme, so that
134 user agents (such as Web browsers and email clients) could start to
135 support it. The "sms" URI scheme identifies SMS message endpoints as
136 resources. When "sms" URIs are dereferenced, implementations MAY
137 create a message and present it to be edited before being sent, or
138 they MAY use additional services to provide the functionality
139 necessary for composing a message and sending it to the SMS message
140 endpoint.
142 1.3.1 SMS Messages and the Web
144 SMS messages can provide an alternative to a "mailto" URIs [RFC2368],
145 or "tel" or "fax" URIs [RFC2806]. When a "sms" URI is activated, the
146 user agent MAY start a program for sending an SMS message, just as
147 "mailto" may open a mail client. Unfortunately, most browsers do not
148 support the external handling of internally unsupported URI schemes
149 in the same generalized way as most of them support external handling
150 of additional MIME type content for types which they do not support
151 internally. Ideally, user agents should implement generic URI
152 parsers and provide a way to associate unsupported schemes with
153 external applications (or Web services).
155 The recipient of an SMS message need not be a mobile phone. It can
156 be a server that can process SMS messages, either by gatewaying them
157 to another messaging system (such as regular electronic mail), or by
158 parsing them for supplementary services.
160 SMS messages can be used to transport almost any kind of data (even
161 though there is a very tight size limit), but the only standardized
162 data formats are character-based messages in different character
163 encodings. SMS messages have a maximum length of 160 characters
164 (when using 7-bit characters from the SMS character set), or 140
165 octets. However, SMS messages can be concatenated to form longer
166 messages. It is up to the user agent to decide whether to limit the
167 length of the message, and how to indicate this limit in its user
168 interface, if necessary. There is one exception to this, see Section
169 2.5.
171 1.3.2 SMS Messages and Forms
173 The Hypertext Markup Language (HTML) [HTML401] provides a way to
174 collect information from a user and pass it to a server for
175 processing. This functionality is known as "HTML forms". A filled-
176 in form is usually sent to the destination using the Hypertext
177 Transfer Protocol (HTTP) or email. However, SMS messages can also be
178 used as the transport mechanism for these forms. As SMS transport is
179 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this
180 provides a way to fill in forms offline, and send the data without
181 making a TCP connection to the server, as the set-up time, cost, and
182 overhead for a TCP connection are large compared to an SMS message.
183 Also, depending on the network configuration, the sender's telephone
184 number may be included in the SMS message, thus providing a weak form
185 of authentication.
187 2. The "sms" URI Scheme
189 Syntax definitions are given using the Augmented BNF for Syntax
190 Specifications [RFC2234].
192 2.1 Applicability
194 This URI scheme is intended for sending an SMS message to a certain
195 recipient(s). The functionality is quite similar to that of the
196 "mailto" URL, which (as per RFC 2368 [RFC2368]) can also be used with
197 a comma-separated list of email addresses.
199 In some situations, it may be necessary to guide the sender to send
200 the SMS message via a certain SMSC. For this purpose, the URI may
201 specify the number of the SMSC.
203 SMS messages may be sent through gateways to other services. These
204 gateways are operated inside SMS centers. An "SMS" URI may specify
205 that a certain gateway should be used.
207 The notation for phone numbers is taken from [draft-allocchio-gstn-
208 03]. Refer to this document for information on why this particular
209 format was chosen.
211 How the SMS message is sent to the SMSC is outside the scope of this
212 specification. SMS messages can be sent over the GSM air interface,
213 by using a modem and a suitable protocol, or by accessing services
214 over other protocols, such as a Web service for sending SMS messages.
215 Also, SMS message service options like deferred delivery and delivery
216 notification requests are not in the scope of this document. Such
217 services MAY be requested from the network by the user agent if
218 necessary.
220 SMS messages sent as a result of this URI MUST be sent as class 1 SMS
221 messages, if the user agent is able to specify the message class.
223 2.2 Formal Definition
225 The URI scheme's keywords specified in the following syntax
226 description are case-insensitive. The syntax of an "sms" URI is
227 formally described as follows, where the base syntax is taken from
228 RFC 2396 [RFC2396]:
230 sms-uri = scheme ":" scheme-specific-part
231 scheme = "sms"
232 scheme-specific-part = 1*( sms-recipient ) [ sms-body ]
233 sms-recipient = gstn-phone sms-qualifier
234 [ "," sms-recipient ]
235 sms-qualifier = *( smsc-qualifier / pid-qualifier )
236 smsc-qualifier = ";smsc=" SMSC-sub-addr
237 pid-qualifier = ";pid=" PID-sub-addr
238 sms-body = "?body=" *urlc
240 The syntax definition for "gstn-phone" is taken from [draft-
241 allocchio-gstn-03], allowing global as well as local telephone
242 numbers.
244 The syntax definition for "SMSC-sub-addr" and "PID-sub-addr" is
245 derived from [draft-wilde-sms-service-03], please refer to that
246 document for the syntax of the qualifier values.
248 The "sms-body" is used to define the body of the SMS message to be
249 composed. It consists of URL-encoded UTF-8 characters.
250 Implementations MUST make sure that the sms-body characters are
251 converted to a suitable character encoding before sending, the most
252 popular being the 7-bit SMS character encoding, another variant
253 (though not as universally supported as 7-bit SMS) is the UCS-2
254 character encoding (both specified in [SMS-CHAR]). Implementations
255 MAY choose to silently discard (or convert) characters in the sms-
256 body that are not supported by the SMS character set they are using
257 to send the SMS message.
259 It should be noted that both the SMSC as well as the PID qualifier
260 may appear only once per sms-recipient. If multiple qualifiers are
261 present, conforming software MUST interpret the first occurrence and
262 ignore all other occurrences.
264 2.3 Parsing an "sms" URI
266 The following list describes the steps for processing an "sms" URI:
268 1. The "gstn-phone" of the first "sms-recipient" is extracted. It
269 is the phone number of the final recipient and it MUST be written
270 in international form with country code, unless the number only
271 works from inside a certain geographical area or a network. Note
272 that some numbers may work from several networks but not from the
273 whole world - these SHOULD be written in international form.
274 According to [draft-allocchio-gstn-03], all international numbers
275 MUST begin with a "+" character. Hyphens and dots are only to
276 aid readability. They MUST NOT have any other meaning.
278 2. The "smsc-qualifier" of the first "sms-recipient" is extracted,
279 if present.
281 3. The "pid-qualifier" of the first "sms-recipient" is extracted, if
282 present.
284 4. The "sms-body" is extracted, if present.
286 5. The user agent should provide some means for message composition,
287 either by implementing this itself, or by accessing a service
288 providing it. Message composition SHOULD start with the body
289 extracted from the "sms-body", if present. If the "pid-
290 qualifier" is set to "pid=SMTP:...", then the user agents must
291 make sure that the email address is correctly set (as defined by
292 the SMS specification [SMS]) in the message being composed.
294 6. After message composition, a user agent SHOULD try to send the
295 message first using the SMSC set in the "smsc-qualifier" (if
296 present). If that fails, the user agent MAY try another SMSC.
298 7. If the URI consists of a comma-separated list of recipients (ie,
299 contains multiple "sms-recipient" parts), all of them are
300 processed in this manner. Exactly the same message SHOULD be
301 sent to all of the listed recipients.
303 2.4 Examples of Use
305 sms:+41796431851
307 This indicates an SMS message capable recipient at the given
308 telephone number. The message is sent using the user agent's default
309 SMSC.
311 sms:+41796431851;smsc=+41794999000
313 This indicates that the SMS message should be sent using the SMSC at
314 the given number.
316 sms:+41796431851,+4116321035;pid=fax
318 This URI should result in two SMS messages being sent, one to the
319 recipient number as shown in the example above, the other one being
320 sent as a fax to the second number (the fax is sent by the SMSC
321 performing the gatewaying, not by the user agent).
323 sms:+41796431851;pid=smtp:ietf@dret.net?body=hello%20there
325 In this case, a message (initially being set to "hello there", which
326 may have been modified by the user before sending) will be sent via
327 SMS using the SMS to email functionality in the SMSC, so that it will
328 eventually result in an email being sent to the specified email
329 address. In this case, the phone number will not be interpreted.
331 2.5 Using "sms" URIs in HTML Forms
333 When using a "sms" type URI as an action URI for HTML form submission
334 [HTML401], the form contents MUST be packaged in the SMS message just
335 as they are packaged when using a "mailto" URL [RFC2368], using the
336 "application/x-www-form-urlencoded" MIME type, effectively packaging
337 all form data into URI compliant syntax [RFC2396]. The SMS message
338 MUST NOT contain any HTTP headers, only the form data. The MIME type
339 is implicit. It MUST NOT be transferred in the SMS message.
341 The character encoding used for form submissions MUST be UTF-8
342 [RFC2279]. It should be noted, however, that user agents MUST URL-
343 encode form submissions before sending them.
345 The user agent SHOULD inform the user about the possible security
346 hazards involved when submitting the form (it is probably being sent
347 as plain text over an air interface).
349 If the form submission is longer than the maximum SMS message size,
350 the user agent MAY either concatenate SMS messages, if it is able to
351 do so, or it MAY refuse to send the message. The user agent MUST NOT
352 send out partial form submissions.
354 Form submission via an "sms" URI can be combined with Telematic
355 Interworking to result in form submissions being submitted via an SMS
356 message and finally being sent to an email account. In this case,
357 all provisions for using the email "pid-qualifier" and using "sms"
358 URIs with HTML forms must be followed.
360 3. "sms" URIs and SMS Web Services
362 In many cases, user agents will not be able to directly compose and
363 send SMS messages (because this requires that such a service is
364 accessible to the system the user agent is running on). However, it
365 is likely that the user has access to a Web service that provides an
366 SMS service, such as a Web site offering form-based SMS composition.
367 Ideally, the user agent should access this Web service when
368 activating an "sms" URI, thus enabling the user to use the Web
369 service.
371 One problem with this approach is that the Web service should somehow
372 get the "sms" URI, in order interpret it and set the required
373 parameters (such as the receiver's phone number). The easiest way to
374 implement this is for the user agent to add the "sms" URI as query
375 string to the Web service's URI. Consequently, user agents
376 supporting SMS Web services identified by URIs SHOULD append the
377 "sms" URI as query string to the Web services URI when accessing the
378 Web service. Web services providing SMS composition facilities
379 SHOULD expect to receive an "sms" URI as query string and should
380 process it as described by this memo. This method only can be
381 applied for Web service URIs which permit query strings (such as
382 "http" and "https" URIs). For other Web service URIs (such as "ftp"
383 and "mailto"), user agents as well as Web services MUST NOT use the
384 query string.
386 It should be noted that RFC 2396 [RFC2396] defines that within query
387 strings, the characters ";", "/", "?", ":", "@", "&", "=", "+", ",",
388 and "$" are reserved. It is therefore necessary to encode the "sms"
389 URI accordingly before appending it as query string.
391 3.1 Example
393 A document contains this piece of (X)HTML:
395 Send me an SMS!
397 The user agent interpreting this document does not internally support
398 SMS message composition, but has configured to access a Web service
399 for handling "sms" URIs. This Web service has the following URI:
401 http://sms.example.com/sms-form
403 When the user activates the "sms" URI (eg, by clicking on the text
404 "Send me an SMS!"), the user agents acts as if the activated URI had
405 been:
407 http://sms.example.com/sms-form?sms%3A%2B41796431851
409 The Web service is then responsible for parsing the query string and
410 providing an approriate interface, for example by already filling in
411 the recipient address with the number provided in the "sms" URI.
413 4. Security Considerations
415 The "Security Considerations" section of the SMS service registration
416 memo [draft-wilde-sms-service-03] MUST be consulted.
418 A user agent SHOULD NOT send out SMS messages without the knowledge
419 of the user, because of associated risks, which include sending
420 masses of SMS messages to a subscriber without his consent, and the
421 costs involved in sending an SMS message.
423 The user agent SHOULD have some mechanism that the user can use to
424 filter out unwanted destinations for SMS messages. The user agent
425 SHOULD also have some means of restricting the number of SMS messages
426 being sent as the result of activating one "sms" URI.
428 If an "sms" URI contains a pid-qualifier and the user agent supports
429 the qualifier and its value, then the user agent MUST set the SMS
430 message's PID as specified by the qualifier. User agents MAY inform
431 users about the value and the functional consequences of PID
432 qualifiers (eg, by notifying users that sending the SMS effectively
433 will result in a fax message being delivered, rather than an SMS
434 message).
436 The method described in section Section 3 adds another level of
437 indirection to the handling of "sms" URIs. If this method is
438 combined with the pid-qualifier gateway functionality, SMS
439 composition and reception will probably be distributed over three
440 different protocols (the Web service, SMS transport itself, and the
441 service selected by the pid-qualifier). User agent SHOULD make this
442 clear to users (either when the Web service is being configured, or
443 when it is accessed).
445 The Telematic Interworking functionality of the SMSC addressed by the
446 pid-qualifier is not necessarily implemented by the SMSC being used,
447 and SMSC providers are known for not or not correctly supporting some
448 or all pid-qualifier values. User agents SHOULD take into account
449 that the success rate of SMS messages being sent using pid-qualifiers
450 is lower than that of "plain" SMS messages.
452 5. Change Log
454 5.1 From -00 to -01
456 o Added the "sms-body" field and its processing rules.
458 o Added Section Section 3 about using "sms" URIs as query strings
459 for SMS Web services.
461 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone").
463 o Added some explanatory text about form submissions using email
464 Telematic Interworking.
466 o Added some text about character encoding in form submissions.
468 5.2 From -01 to -02
470 o Changed the sms-body field to URL encoded UTF-8 characters.
472 5.3 From -02 to -03
474 o Changed ordering of "change Log" section (descending to
475 ascending).
477 o Clarified the wording at the beginning of Section Section 2.2
478 about only the keywords of the scheme being case-insensitive.
480 o Changed "sms-body" to be a URI query string.
482 o Added some text describing "sms" URIs as addressing resources.
484 Normative References
486 [HTML401] Raggett, D., Le Hors, A. and I. Jacobs,
487 "HTML 4.01 Specification", W3C REC-
488 html401, December 1999, .
491 [RFC2119] Bradner, S., "Key words for use in RFCs
492 to Indicate Requirement Levels", RFC
493 2119, March 1997.
495 [RFC2234] Crocker, D. and P. Overell, "Augmented
496 BNF for Syntax Specifications: ABNF",
497 RFC 2234, November 1997.
499 [RFC2279] Yergeau, F., "UTF-8, a transformation
500 format of ISO 10646", RFC 2279, January
501 1998.
503 [RFC2396] Berners-Lee, T., Fielding, R. and L.
504 Masinter, "Uniform Resource Identifiers
505 (URI): Generic Syntax", RFC 2396,
506 August 1998.
508 [SMS] European Telecommunications Standards
509 Institute, "Digital Cellular
510 Telecommunications System (Phase 2+);
511 Technical realization of the Short
512 Message Service (SMS); Point-to-Point
513 (PP)", December 1998, .
516 [SMS-CHAR] European Telecommunications Standards
517 Institute, "ETSI TS 100 901 (GSM 03.38
518 version 7.2.0 Release 1998): Digital
519 Cellular Telecommunications System
520 (Phase 2+); Alphabets and language-
521 specific information", July 1999,
522 .
525 [draft-allocchio-gstn-03] Allocchio, C., "Text string notation
526 for Dial Sequences and GSTN / E.164
527 addresses", draft-allocchio-gstn-03
528 (work in progress), March 2002.
530 [draft-wilde-sms-service-03] Wilde, E., "Registration of GSTN SMS
531 Service Qualifier", draft-wilde-sms-
532 service-03 (work in progress), January
533 2002.
535 Non-Normative References
537 [RFC2368] Hoffmann, P., Masinter, L. and J. Zawinski, "The
538 mailto URL scheme", RFC 2368, June 1998.
540 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC
541 2629, June 1999.
543 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC
544 2806, April 2000.
546 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource
547 Identifiers for Television Broadcasts", RFC
548 2838, May 2000.
550 [uri-clarification] World Wide Web Consortium, "URIs, URLs, and
551 URNs: Clarifications and Recommendations 1.0",
552 W3C uri-clarification , September 2001, .
555 Authors' Addresses
557 Erik Wilde
558 Swiss Federal Institute of Technology
559 ETH-Zentrum
560 8092 Zurich
561 Switzerland
563 Phone: +41-1-6325132
564 EMail: ietf@dret.net
565 URI: http://dret.net/netdret/
567 Antti Vaha-Sipila
568 Nokia
570 EMail: antti.vaha-sipila@nokia.com
572 Appendix A. Where to send Comments
574 Please send all comments about this document to Erik Wilde.
576 Appendix B. Acknowledgements
578 This document has been written using the IETF document DTD described
579 in RFC 2629 [RFC2629].
581 Thanks to Claudio Allocchio for his comments.
583 Full Copyright Statement
585 Copyright (C) The Internet Society (2002). All Rights Reserved.
587 This document and translations of it may be copied and furnished to
588 others, and derivative works that comment on or otherwise explain it
589 or assist in its implementation may be prepared, copied, published
590 and distributed, in whole or in part, without restriction of any
591 kind, provided that the above copyright notice and this paragraph are
592 included on all such copies and derivative works. However, this
593 document itself may not be modified in any way, such as by removing
594 the copyright notice or references to the Internet Society or other
595 Internet organizations, except as needed for the purpose of
596 developing Internet standards in which case the procedures for
597 copyrights defined in the Internet Standards process must be
598 followed, or as required to translate it into languages other than
599 English.
601 The limited permissions granted above are perpetual and will not be
602 revoked by the Internet Society or its successors or assigns.
604 This document and the information contained herein is provided on an
605 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
606 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
607 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
608 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
609 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
611 Acknowledgement
613 Funding for the RFC Editor function is currently provided by the
614 Internet Society.