idnits 2.17.1
draft-wilde-sms-uri-04.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 (May 14, 2003) is 7652 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: November 12, 2003 Technology
5 A. Vaha-Sipila
6 Nokia
7 May 14, 2003
9 URI scheme for GSM Short Message Service
10 draft-wilde-sms-uri-04
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 other
19 groups may also distribute working documents as Internet-Drafts.
21 Internet-Drafts are draft documents valid for a maximum of six months
22 and may be updated, replaced, or obsoleted by other documents at any
23 time. It is inappropriate to use Internet-Drafts as reference
24 material or to cite them other than as "work in progress."
26 The list of current Internet-Drafts can be accessed at http://
27 www.ietf.org/ietf/1id-abstracts.txt.
29 The list of Internet-Draft Shadow Directories can be accessed at
30 http://www.ietf.org/shadow.html.
32 This Internet-Draft will expire on November 12, 2003.
34 Copyright Notice
36 Copyright (C) The Internet Society (2003). All Rights Reserved.
38 Abstract
40 This memo specifies a URI (Universal Resource Identifier) scheme
41 "sms" for specifying a recipient (and optionally a gateway) for an
42 SMS message. SMS messages are two-way paging messages that can be
43 sent from and received by a mobile phone or a suitably equipped
44 computer.
46 Table of Contents
48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
49 1.1 The Short Message Service . . . . . . . . . . . . . . . . . 3
50 1.2 Universal Resource Identifiers . . . . . . . . . . . . . . . 3
51 1.3 SMS Messages and the Internet . . . . . . . . . . . . . . . 3
52 1.3.1 SMS Messages and the Web . . . . . . . . . . . . . . . . . . 4
53 1.3.2 SMS Messages and Forms . . . . . . . . . . . . . . . . . . . 5
54 2. The "sms" URI Scheme . . . . . . . . . . . . . . . . . . . . 5
55 2.1 Applicability . . . . . . . . . . . . . . . . . . . . . . . 5
56 2.2 Formal Definition . . . . . . . . . . . . . . . . . . . . . 6
57 2.3 Parsing an "sms" URI . . . . . . . . . . . . . . . . . . . . 6
58 2.4 Examples of Use . . . . . . . . . . . . . . . . . . . . . . 7
59 2.5 Using "sms" URIs in HTML Forms . . . . . . . . . . . . . . . 8
60 3. "sms" URIs and SMS Web Services . . . . . . . . . . . . . . 8
61 3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . 9
62 4. Security Considerations . . . . . . . . . . . . . . . . . . 10
63 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . 10
64 5.1 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . . 10
65 5.2 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . . 11
66 5.3 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . . 11
67 5.4 From -03 to -04 . . . . . . . . . . . . . . . . . . . . . . 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 Intellectual Property and Copyright Statements . . . . . . . 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
89 [draft-wilde-sms-service-04].
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 memo,
106 only the term URI will be used, referring to the most fundamental
107 concept. The World Wide Web Consortium (W3C) has issued a note
108 [uri-clarification] discussing the topic of URIs, URNs, and URLs in
109 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 parsers
152 and provide a way to associate unsupported schemes with external
153 applications (or Web services).
155 The recipient of an SMS message need not be a mobile phone. It can be
156 a server that can process SMS messages, either by gatewaying them to
157 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 (when
164 using 7-bit characters from the SMS character set), or 140 octets.
165 However, SMS messages can be concatenated to form longer messages. It
166 is up to the user agent to decide whether to limit the length of the
167 message, and how to indicate this limit in its user interface, if
168 necessary. There is one exception to this, see Section 2.5.
170 1.3.2 SMS Messages and Forms
172 The Hypertext Markup Language (HTML) [HTML401] provides a way to
173 collect information from a user and pass it to a server for
174 processing. This functionality is known as "HTML forms". A filled-in
175 form is usually sent to the destination using the Hypertext Transfer
176 Protocol (HTTP) or email. However, SMS messages can also be used as
177 the transport mechanism for these forms. As SMS transport is
178 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this
179 provides a way to fill in forms offline, and send the data without
180 making a TCP connection to the server, as the set-up time, cost, and
181 overhead for a TCP connection are large compared to an SMS message.
182 Also, depending on the network configuration, the sender's telephone
183 number may be included in the SMS message, thus providing a weak form
184 of authentication.
186 2. The "sms" URI Scheme
188 Syntax definitions are given using the Augmented BNF for Syntax
189 Specifications [RFC2234].
191 2.1 Applicability
193 This URI scheme is intended for sending an SMS message to a certain
194 recipient(s). The functionality is quite similar to that of the
195 "mailto" URL, which (as per RFC 2368 [RFC2368]) can also be used with
196 a comma-separated list of email addresses.
198 In some situations, it may be necessary to guide the sender to send
199 the SMS message via a certain SMSC. For this purpose, the URI may
200 specify the number of the SMSC.
202 SMS messages may be sent through gateways to other services. These
203 gateways are operated inside SMS centers. An "SMS" URI may specify
204 that a certain gateway should be used.
206 The notation for phone numbers is taken from
207 [draft-allocchio-gstn-05]. Refer to this document for information on
208 why this particular format was chosen.
210 How the SMS message is sent to the SMSC is outside the scope of this
211 specification. SMS messages can be sent over the GSM air interface,
212 by using a modem and a suitable protocol, or by accessing services
213 over other protocols, such as a Web service for sending SMS messages.
214 Also, SMS message service options like deferred delivery and delivery
215 notification requests are not in the scope of this document. Such
216 services MAY be requested from the network by the user agent if
217 necessary.
219 SMS messages sent as a result of this URI MUST be sent as class 1 SMS
220 messages, if the user agent is able to specify the message class.
222 2.2 Formal Definition
224 The URI scheme's keywords specified in the following syntax
225 description are case-insensitive. The syntax of an "sms" URI is
226 formally described as follows, where the base syntax is taken from
227 RFC 2396 [RFC2396]:
229 sms-uri = scheme ":" scheme-specific-part
230 scheme = "sms"
231 scheme-specific-part = 1*( sms-recipient ) [ sms-body ]
232 sms-recipient = gstn-phone sms-qualifier
233 [ "," sms-recipient ]
234 sms-qualifier = *( smsc-qualifier / pid-qualifier )
235 smsc-qualifier = ";smsc=" SMSC-sub-addr
236 pid-qualifier = ";pid=" PID-sub-addr
237 sms-body = "?body=" *urlc
239 The syntax definition for "gstn-phone" is taken from
240 [draft-allocchio-gstn-05], allowing global as well as local telephone
241 numbers.
243 The syntax definition for "SMSC-sub-addr" and "PID-sub-addr" is
244 derived from [draft-wilde-sms-service-04], please refer to that
245 document for the syntax of the qualifier values.
247 The "sms-body" is used to define the body of the SMS message to be
248 composed. It consists of URL-encoded UTF-8 characters.
249 Implementations MUST make sure that the sms-body characters are
250 converted to a suitable character encoding before sending, the most
251 popular being the 7-bit SMS character encoding, another variant
252 (though not as universally supported as 7-bit SMS) is the UCS-2
253 character encoding (both specified in [SMS-CHAR]). Implementations
254 MAY choose to silently discard (or convert) characters in the
255 sms-body that are not supported by the SMS character set they are
256 using to send the SMS message.
258 It should be noted that both the SMSC as well as the PID qualifier
259 may appear only once per sms-recipient. If multiple qualifiers are
260 present, conforming software MUST interpret the first occurrence and
261 ignore all other occurrences.
263 2.3 Parsing an "sms" URI
265 The following list describes the steps for processing an "sms" URI:
267 1. The "gstn-phone" of the first "sms-recipient" is extracted. It is
268 the phone number of the final recipient and it MUST be written in
269 international form with country code, unless the number only
270 works from inside a certain geographical area or a network. Note
271 that some numbers may work from several networks but not from the
272 whole world - these SHOULD be written in international form.
273 According to [draft-allocchio-gstn-05], all international numbers
274 MUST begin with a "+" character. Hyphens and dots are only to aid
275 readability. They MUST NOT have any other meaning.
277 2. The "smsc-qualifier" of the first "sms-recipient" is extracted,
278 if present.
280 3. The "pid-qualifier" of the first "sms-recipient" is extracted, if
281 present.
283 4. The "sms-body" is extracted, if present.
285 5. The user agent should provide some means for message composition,
286 either by implementing this itself, or by accessing a service
287 providing it. Message composition SHOULD start with the body
288 extracted from the "sms-body", if present. If the "pid-qualifier"
289 is set to "pid=SMTP:...", then the user agents must make sure
290 that the email address is correctly set (as defined by the SMS
291 specification [SMS]) in the message being composed.
293 6. After message composition, a user agent SHOULD try to send the
294 message first using the SMSC set in the "smsc-qualifier" (if
295 present). If that fails, the user agent MAY try another SMSC.
297 7. If the URI consists of a comma-separated list of recipients (ie,
298 contains multiple "sms-recipient" parts), all of them are
299 processed in this manner. Exactly the same message SHOULD be sent
300 to all of the listed recipients.
302 2.4 Examples of Use
304 sms:+41796431851
306 This indicates an SMS message capable recipient at the given
307 telephone number. The message is sent using the user agent's default
308 SMSC.
310 sms:+41796431851;smsc=+41794999000
312 This indicates that the SMS message should be sent using the SMSC at
313 the given number.
315 sms:+41796431851,+4116321035;pid=fax
317 This URI should result in two SMS messages being sent, one to the
318 recipient number as shown in the example above, the other one being
319 sent as a fax to the second number (the fax is sent by the SMSC
320 performing the gatewaying, not by the user agent).
322 sms:+41796431851;pid=smtp:ietf@dret.net?body=hello%20there
324 In this case, a message (initially being set to "hello there", which
325 may have been modified by the user before sending) will be sent via
326 SMS using the SMS to email functionality in the SMSC, so that it will
327 eventually result in an email being sent to the specified email
328 address. In this case, the phone number will not be interpreted.
330 2.5 Using "sms" URIs in HTML Forms
332 When using a "sms" type URI as an action URI for HTML form submission
333 [HTML401], the form contents MUST be packaged in the SMS message just
334 as they are packaged when using a "mailto" URL [RFC2368], using the
335 "application/x-www-form-urlencoded" MIME type, effectively packaging
336 all form data into URI compliant syntax [RFC2396]. The SMS message
337 MUST NOT contain any HTTP headers, only the form data. The MIME type
338 is implicit. It MUST NOT be transferred in the SMS message.
340 The character encoding used for form submissions MUST be UTF-8
341 [RFC2279]. It should be noted, however, that user agents MUST
342 URL-encode form submissions before sending them.
344 The user agent SHOULD inform the user about the possible security
345 hazards involved when submitting the form (it is probably being sent
346 as plain text over an air interface).
348 If the form submission is longer than the maximum SMS message size,
349 the user agent MAY either concatenate SMS messages, if it is able to
350 do so, or it MAY refuse to send the message. The user agent MUST NOT
351 send out partial form submissions.
353 Form submission via an "sms" URI can be combined with Telematic
354 Interworking to result in form submissions being submitted via an SMS
355 message and finally being sent to an email account. In this case, all
356 provisions for using the email "pid-qualifier" and using "sms" URIs
357 with HTML forms must be followed.
359 3. "sms" URIs and SMS Web Services
361 In many cases, user agents will not be able to directly compose and
362 send SMS messages (because this requires that such a service is
363 accessible to the system the user agent is running on). However, it
364 is likely that the user has access to a Web service that provides an
365 SMS service, such as a Web site offering form-based SMS composition.
366 Ideally, the user agent should access this Web service when
367 activating an "sms" URI, thus enabling the user to use the Web
368 service.
370 One problem with this approach is that the Web service should somehow
371 get the "sms" URI, in order interpret it and set the required
372 parameters (such as the receiver's phone number). The easiest way to
373 implement this is for the user agent to add the "sms" URI as query
374 string to the Web service's URI. Consequently, user agents supporting
375 SMS Web services identified by URIs SHOULD append the "sms" URI as
376 query string to the Web services URI when accessing the Web service.
377 Web services providing SMS composition facilities SHOULD expect to
378 receive an "sms" URI as query string and should process it as
379 described by this memo. This method only can be applied for Web
380 service URIs which permit query strings (such as "http" and "https"
381 URIs). For other Web service URIs (such as "ftp" and "mailto"), user
382 agents as well as Web services MUST NOT use the query string.
384 It should be noted that RFC 2396 [RFC2396] defines that within query
385 strings, the characters ";", "/", "?", ":", "@", "&", "=", "+", ",",
386 and "$" are reserved. It is therefore necessary to encode the "sms"
387 URI accordingly before appending it as query string.
389 3.1 Example
391 A document contains this piece of (X)HTML:
393 Send me an SMS!
395 The user agent interpreting this document does not internally support
396 SMS message composition, but been has been configured to access a Web
397 service for handling "sms" URIs. This Web service has the following
398 URI:
400 http://sms.example.com/sms-form
402 When the user activates the "sms" URI (eg, by clicking on the text
403 "Send me an SMS!"), the user agents acts as if the activated URI had
404 been:
406 http://sms.example.com/sms-form?sms%3A%2B41796431851
408 The Web service is then responsible for parsing the query string and
409 providing an approriate interface, for example by already filling in
410 the recipient address with the number provided in the "sms" URI.
412 4. Security Considerations
414 The "Security Considerations" section of the SMS service registration
415 memo [draft-wilde-sms-service-04] MUST be consulted.
417 A user agent SHOULD NOT send out SMS messages without the knowledge
418 of the user, because of associated risks, which include sending
419 masses of SMS messages to a subscriber without his consent, and the
420 costs involved in sending an SMS message.
422 The user agent SHOULD have some mechanism that the user can use to
423 filter out unwanted destinations for SMS messages. The user agent
424 SHOULD also have some means of restricting the number of SMS messages
425 being sent as the result of activating one "sms" URI.
427 If an "sms" URI contains a pid-qualifier and the user agent supports
428 the qualifier and its value, then the user agent MUST set the SMS
429 message's PID as specified by the qualifier. User agents MAY inform
430 users about the value and the functional consequences of PID
431 qualifiers (eg, by notifying users that sending the SMS effectively
432 will result in a fax message being delivered, rather than an SMS
433 message).
435 The method described in section Section 3 adds another level of
436 indirection to the handling of "sms" URIs. If this method is combined
437 with the pid-qualifier gateway functionality, SMS composition and
438 reception will probably be distributed over three different protocols
439 (the Web service, SMS transport itself, and the service selected by
440 the pid-qualifier). User agent SHOULD make this clear to users
441 (either when the Web service is being configured, or when it is
442 accessed).
444 The Telematic Interworking functionality of the SMSC addressed by the
445 pid-qualifier is not necessarily implemented by the SMSC being used,
446 and SMSC providers are known for not or not correctly supporting some
447 or all pid-qualifier values. User agents SHOULD take into account
448 that the success rate of SMS messages being sent using pid-qualifiers
449 is lower than that of "plain" SMS messages.
451 5. Change Log
453 5.1 From -00 to -01
455 o Added the "sms-body" field and its processing rules.
457 o Added Section Section 3 about using "sms" URIs as query strings
458 for SMS Web services.
460 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone").
462 o Added some explanatory text about form submissions using email
463 Telematic Interworking.
465 o Added some text about character encoding in form submissions.
467 5.2 From -01 to -02
469 o Changed the sms-body field to URL encoded UTF-8 characters.
471 5.3 From -02 to -03
473 o Changed ordering of "change Log" section (descending to
474 ascending).
476 o Clarified the wording at the beginning of Section Section 2.2
477 about only the keywords of the scheme being case-insensitive.
479 o Changed "sms-body" to be a URI query string.
481 o Added some text describing "sms" URIs as addressing resources.
483 5.4 From -03 to -04
485 o Updated reference to draft-allocchio-gstn (to revision -05).
487 Normative References
489 [HTML401] Raggett, D., Le Hors, A. and I. Jacobs, "HTML 4.01
490 Specification", W3C REC-html401, December 1999, .
493 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
494 Requirement Levels", RFC 2119, March 1997.
496 [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
497 Specifications: ABNF", RFC 2234, November 1997.
499 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO
500 10646", RFC 2279, January 1998.
502 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
503 Resource Identifiers (URI): Generic Syntax", RFC 2396,
504 August 1998.
506 [SMS] European Telecommunications Standards Institute, "Digital
507 Cellular Telecommunications System (Phase 2+); Technical
508 realization of the Short Message Service (SMS);
509 Point-to-Point (PP)", December 1998, .
512 [SMS-CHAR]
513 European Telecommunications Standards Institute, "ETSI TS
514 100 901 (GSM 03.38 version 7.2.0 Release 1998): Digital
515 Cellular Telecommunications System (Phase 2+); Alphabets
516 and language-specific information", July 1999, .
519 [draft-allocchio-gstn-05]
520 Allocchio, C., "Text string notation for Dial Sequences
521 and GSTN / E.164 addresses", draft-allocchio-gstn-05 (work
522 in progress), April 2003.
524 [draft-wilde-sms-service-04]
525 Wilde, E., "Registration of GSTN SMS Service Qualifier",
526 draft-wilde-sms-service-04 (work in progress), May 2003.
528 Non-Normative References
530 [RFC2368] Hoffmann, P., Masinter, L. and J. Zawinski, "The mailto
531 URL scheme", RFC 2368, June 1998.
533 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
534 June 1999.
536 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806,
537 April 2000.
539 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers
540 for Television Broadcasts", RFC 2838, May 2000.
542 [uri-clarification]
543 World Wide Web Consortium, "URIs, URLs, and URNs:
544 Clarifications and Recommendations 1.0", W3C
545 uri-clarification , September 2001, .
548 Authors' Addresses
550 Erik Wilde
551 Swiss Federal Institute of Technology
552 ETH-Zentrum
553 8092 Zurich
554 Switzerland
556 Phone: +41-1-6325132
557 EMail: ietf@dret.net
558 URI: http://dret.net/netdret/
560 Antti Vaha-Sipila
561 Nokia
563 EMail: antti.vaha-sipila@nokia.com
565 Appendix A. Where to send Comments
567 Please send all comments and questions concerning this document to
568 Erik Wilde.
570 Appendix B. Acknowledgements
572 This document has been prepared using the IETF document DTD described
573 in RFC 2629 [RFC2629].
575 Thanks to Claudio Allocchio for his comments.
577 Intellectual Property Statement
579 The IETF takes no position regarding the validity or scope of any
580 intellectual property or other rights that might be claimed to
581 pertain to the implementation or use of the technology described in
582 this document or the extent to which any license under such rights
583 might or might not be available; neither does it represent that it
584 has made any effort to identify any such rights. Information on the
585 IETF's procedures with respect to rights in standards-track and
586 standards-related documentation can be found in BCP-11. Copies of
587 claims of rights made available for publication and any assurances of
588 licenses to be made available, or the result of an attempt made to
589 obtain a general license or permission for the use of such
590 proprietary rights by implementors or users of this specification can
591 be obtained from the IETF Secretariat.
593 The IETF invites any interested party to bring to its attention any
594 copyrights, patents or patent applications, or other proprietary
595 rights which may cover technology that may be required to practice
596 this standard. Please address the information to the IETF Executive
597 Director.
599 Full Copyright Statement
601 Copyright (C) The Internet Society (2003). All Rights Reserved.
603 This document and translations of it may be copied and furnished to
604 others, and derivative works that comment on or otherwise explain it
605 or assist in its implementation may be prepared, copied, published
606 and distributed, in whole or in part, without restriction of any
607 kind, provided that the above copyright notice and this paragraph are
608 included on all such copies and derivative works. However, this
609 document itself may not be modified in any way, such as by removing
610 the copyright notice or references to the Internet Society or other
611 Internet organizations, except as needed for the purpose of
612 developing Internet standards in which case the procedures for
613 copyrights defined in the Internet Standards process must be
614 followed, or as required to translate it into languages other than
615 English.
617 The limited permissions granted above are perpetual and will not be
618 revoked by the Internet Society or its successors or assignees.
620 This document and the information contained herein is provided on an
621 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
622 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
623 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
624 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
625 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
627 Acknowledgement
629 Funding for the RFC Editor function is currently provided by the
630 Internet Society.