idnits 2.17.1
draft-wilde-sms-uri-06.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 (Jul 14, 2004) is 7219 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: January 12, 2005 Technology
5 A. Vaha-Sipila
6 Nokia
7 Jul 14, 2004
9 URI scheme for GSM Short Message Service
10 draft-wilde-sms-uri-06
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
20 Internet-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 January 12, 2005.
35 Copyright Notice
37 Copyright (C) The Internet Society (2004). 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 . . . . . . . . . . . . . . . 9
62 3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . 9
63 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
64 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 10
65 5.1 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . 11
66 5.2 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . 11
67 5.3 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . 11
68 5.4 From -03 to -04 . . . . . . . . . . . . . . . . . . . . . 11
69 5.5 From -04 to -05 . . . . . . . . . . . . . . . . . . . . . 11
70 5.6 From -05 to -06 . . . . . . . . . . . . . . . . . . . . . 11
71 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
72 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 12
73 6.2 Non-Normative References . . . . . . . . . . . . . . . . . . 12
74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13
75 A. Where to send Comments . . . . . . . . . . . . . . . . . . . . 13
76 B. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
77 Intellectual Property and Copyright Statements . . . . . . . . 14
79 1. Introduction
81 Compliant software MUST follow this specification. The capitalized
82 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
84 document are to be interpreted as described in RFC 2119 [RFC2119].
86 1.1 The Short Message Service
88 The Short Message Service (SMS) [SMS] is a rather simple service for
89 sending messages between SMS clients or, using so-called "Telematic
90 Interworking", from an SMS client through a gateway to a receiver
91 using a different service, such as fax or email. The SMS service is
92 described in more detail in the SMS service registration memo
93 [draft-wilde-sms-service-06].
95 1.2 Universal Resource Identifiers
97 One of the core specifications for identifying resources on the
98 Internet is RFC 2396 [RFC2396], specifying the syntax and semantics
99 of a Universal Resource Identifier (URI). The most important notion
100 of URIs are "schemes", which define a framework within which
101 resources can be identified (and possibly accessed). URIs enable
102 users to identify resources, and are used for very diverse schemes
103 such as access protocols (HTTP, FTP), broadcast media (TV channels
104 [RFC2838]), messaging (email [RFC2368]), or even telephone numbers
105 (voice [RFC2806]).
107 URIs often are mentioned together with Universal Resource Names
108 (URNs) and/or Uniform Resource Locators (URLs), and it often is
109 unclear how to separate these concepts. For the purpose of this
110 memo, only the term URI will be used, referring to the most
111 fundamental concept. The World Wide Web Consortium (W3C) has issued
112 a note [uri-clarification] discussing the topic of URIs, URNs, and
113 URLs in detail.
115 1.3 SMS Messages and the Internet
117 One of the important reasons for the universal access of the Web is
118 the ability to access all information through a unique interface.
119 This kind of integration makes it easy to provide information as well
120 as to consume it. One aspect of this integration is the support of
121 user agents (in the case of the Web, commonly referred to as
122 browsers) for multiple content formats (such as HTML, GIF, JPEG) and
123 access schemes (such as HTTP, HTTP-S, FTP).
125 The "mailto" scheme has proven to be very useful and popular, because
126 most user agents support it by providing an email composition
127 facility when the user activates (eg, clicks on) the URI.
128 Accordingly, the "sms" scheme could be supported by user agents by
129 providing an SMS message composition facility when the user activates
130 the URI. Alternatively, in cases where the user agent does not
131 provide a built-in SMS message composition facility, the scheme could
132 still be supported by opening a Web page which provides such a
133 service. The specific Web page to be used could be configured by the
134 user, so that each user could use the SMS message composition service
135 of his choice.
137 The goal of this memo is to specify the "sms" URI scheme, so that
138 user agents (such as Web browsers and email clients) could start to
139 support it. The "sms" URI scheme identifies SMS message endpoints as
140 resources. When "sms" URIs are dereferenced, implementations MAY
141 create a message and present it to be edited before being sent, or
142 they MAY use additional services to provide the functionality
143 necessary for composing a message and sending it to the SMS message
144 endpoint.
146 1.3.1 SMS Messages and the Web
148 SMS messages can provide an alternative to a "mailto" URIs [RFC2368],
149 or "tel" or "fax" URIs [RFC2806]. When a "sms" URI is activated, the
150 user agent MAY start a program for sending an SMS message, just as
151 "mailto" may open a mail client. Unfortunately, most browsers do not
152 support the external handling of internally unsupported URI schemes
153 in the same generalized way as most of them support external handling
154 of additional MIME type content for types which they do not support
155 internally. Ideally, user agents should implement generic URI
156 parsers and provide a way to associate unsupported schemes with
157 external applications (or Web services).
159 The recipient of an SMS message need not be a mobile phone. It can
160 be a server that can process SMS messages, either by gatewaying them
161 to another messaging system (such as regular electronic mail), or by
162 parsing them for supplementary services.
164 SMS messages can be used to transport almost any kind of data (even
165 though there is a very tight size limit), but the only standardized
166 data formats are character-based messages in different character
167 encodings. SMS messages have a maximum length of 160 characters
168 (when using 7-bit characters from the SMS character set), or 140
169 octets. However, SMS messages can be concatenated to form longer
170 messages. It is up to the user agent to decide whether to limit the
171 length of the message, and how to indicate this limit in its user
172 interface, if necessary. There is one exception to this, see Section
173 2.5.
175 1.3.2 SMS Messages and Forms
177 The Hypertext Markup Language (HTML) [HTML401] provides a way to
178 collect information from a user and pass it to a server for
179 processing. This functionality is known as "HTML forms". A
180 filled-in form is usually sent to the destination using the Hypertext
181 Transfer Protocol (HTTP) or email. However, SMS messages can also be
182 used as the transport mechanism for these forms. As SMS transport is
183 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this
184 provides a way to fill in forms offline, and send the data without
185 making a TCP connection to the server, as the set-up time, cost, and
186 overhead for a TCP connection are large compared to an SMS message.
187 Also, depending on the network configuration, the sender's telephone
188 number may be included in the SMS message, thus providing a weak form
189 of authentication.
191 2. The "sms" URI Scheme
193 Syntax definitions are given using the Augmented BNF for Syntax
194 Specifications [RFC2234].
196 2.1 Applicability
198 This URI scheme is intended for sending an SMS message to a certain
199 recipient(s). The functionality is quite similar to that of the
200 "mailto" URL, which (as per RFC 2368 [RFC2368]) can also be used with
201 a comma-separated list of email addresses.
203 In some situations, it may be necessary to guide the sender to send
204 the SMS message via a certain SMSC. For this purpose, the URI may
205 specify the number of the SMSC.
207 SMS messages may be sent through gateways to other services. These
208 gateways are operated inside SMS centers. An "SMS" URI may specify
209 that a certain gateway should be used.
211 The notation for phone numbers is taken from [RFC3601]. Refer to
212 this document for information on why this particular format was
213 chosen.
215 How the SMS message is sent to the SMSC is outside the scope of this
216 specification. SMS messages can be sent over the GSM air interface,
217 by using a modem and a suitable protocol, or by accessing services
218 over other protocols, such as a Web service for sending SMS messages.
219 Also, SMS message service options like deferred delivery and delivery
220 notification requests are not in the scope of this document. Such
221 services MAY be requested from the network by the user agent if
222 necessary.
224 SMS messages sent as a result of this URI MUST be sent as class 1 SMS
225 messages, if the user agent is able to specify the message class.
227 2.2 Formal Definition
229 The URI scheme's keywords specified in the following syntax
230 description are case-insensitive. The syntax of an "sms" URI is
231 formally described as follows, where the base syntax is taken from
232 RFC 2396 [RFC2396]:
234 sms-uri = scheme ":" scheme-specific-part
235 scheme = "sms"
236 scheme-specific-part = 1*( sms-recipient ) [ sms-body ]
237 sms-recipient = gstn-phone sms-qualifier
238 [ "," sms-recipient ]
239 sms-qualifier = *( smsc-qualifier / pid-qualifier )
240 smsc-qualifier = ";smsc=" SMSC-sub-addr
241 pid-qualifier = ";pid=" PID-sub-addr
242 sms-body = "?body=" *urlc
244 The syntax definition for "gstn-phone" is taken from [RFC3601],
245 allowing global as well as local telephone numbers.
247 The syntax definition for "SMSC-sub-addr" and "PID-sub-addr" is
248 derived from [draft-wilde-sms-service-06], please refer to that
249 document for the syntax of the qualifier values.
251 The "sms-body" is used to define the body of the SMS message to be
252 composed. It consists of URL-encoded UTF-8 characters.
253 Implementations MUST make sure that the sms-body characters are
254 converted to a suitable character encoding before sending, the most
255 popular being the 7-bit SMS character encoding, another variant
256 (though not as universally supported as 7-bit SMS) is the UCS-2
257 character encoding (both specified in [SMS-CHAR]). Implementations
258 MAY choose to silently discard (or convert) characters in the
259 sms-body that are not supported by the SMS character set they are
260 using to send the SMS message.
262 It should be noted that both the SMSC as well as the PID qualifier
263 may appear only once per sms-recipient. If multiple qualifiers are
264 present, conforming software MUST interpret the first occurrence and
265 ignore all other occurrences.
267 2.3 Parsing an "sms" URI
269 The following list describes the steps for processing an "sms" URI:
271 1. The "gstn-phone" of the first "sms-recipient" is extracted. It
272 is the phone number of the final recipient and it MUST be written
273 in international form with country code, unless the number only
274 works from inside a certain geographical area or a network. Note
275 that some numbers may work from several networks but not from the
276 whole world - these SHOULD be written in international form.
277 According to [RFC3601], all international numbers MUST begin with
278 a "+" character. Hyphens and dots are only to aid readability.
279 They MUST NOT have any other meaning.
281 2. The "smsc-qualifier" of the first "sms-recipient" is extracted,
282 if present.
284 3. The "pid-qualifier" of the first "sms-recipient" is extracted, if
285 present.
287 4. The "sms-body" is extracted, if present.
289 5. The user agent should provide some means for message composition,
290 either by implementing this itself, or by accessing a service
291 providing it. Message composition SHOULD start with the body
292 extracted from the "sms-body", if present. If the
293 "pid-qualifier" is set to "pid=SMTP:...", then the user agents
294 must make sure that the email address is correctly set (as
295 defined by the SMS specification [SMS]) in the message being
296 composed.
298 6. After message composition, a user agent SHOULD try to send the
299 message first using the SMSC set in the "smsc-qualifier" (if
300 present). If that fails, the user agent MAY try another SMSC.
302 7. If the URI consists of a comma-separated list of recipients (ie,
303 contains multiple "sms-recipient" parts), all of them are
304 processed in this manner. Exactly the same message SHOULD be
305 sent to all of the listed recipients.
307 2.4 Examples of Use
309 sms:+41796431851
311 This indicates an SMS message capable recipient at the given
312 telephone number. The message is sent using the user agent's default
313 SMSC.
315 sms:+41796431851;smsc=+41794999000
317 This indicates that the SMS message should be sent using the SMSC at
318 the given number.
320 sms:+41796431851,+4116321035;pid=fax
322 This URI should result in two SMS messages being sent, one to the
323 recipient number as shown in the example above, the other one being
324 sent as a fax to the second number (the fax is sent by the SMSC
325 performing the gatewaying, not by the user agent).
327 sms:+41796431851;pid=smtp:erik.wilde@dret.net?body=hello%20there
329 In this case, a message (initially being set to "hello there", which
330 may have been modified by the user before sending) will be sent via
331 SMS using the SMS to email functionality in the SMSC, so that it will
332 eventually result in an email being sent to the specified email
333 address. In this case, the phone number will not be interpreted.
335 2.5 Using "sms" URIs in HTML Forms
337 When using a "sms" type URI as an action URI for HTML form submission
338 [HTML401], the form contents MUST be packaged in the SMS message just
339 as they are packaged when using a "mailto" URL [RFC2368], using the
340 "application/x-www-form-urlencoded" MIME type, effectively packaging
341 all form data into URI compliant syntax [RFC2396]. The SMS message
342 MUST NOT contain any HTTP headers, only the form data. The MIME type
343 is implicit. It MUST NOT be transferred in the SMS message.
345 The character encoding used for form submissions MUST be UTF-8
346 [RFC2279]. It should be noted, however, that user agents MUST
347 URL-encode form submissions before sending them.
349 The user agent SHOULD inform the user about the possible security
350 hazards involved when submitting the form (it is probably being sent
351 as plain text over an air interface).
353 If the form submission is longer than the maximum SMS message size,
354 the user agent MAY either concatenate SMS messages, if it is able to
355 do so, or it MAY refuse to send the message. The user agent MUST NOT
356 send out partial form submissions.
358 Form submission via an "sms" URI can be combined with Telematic
359 Interworking to result in form submissions being submitted via an SMS
360 message and finally being sent to an email account. In this case,
361 all provisions for using the email "pid-qualifier" and using "sms"
362 URIs with HTML forms must be followed.
364 3. "sms" URIs and SMS Web Services
366 In many cases, user agents will not be able to directly compose and
367 send SMS messages (because this requires that such a service is
368 accessible to the system the user agent is running on). However, it
369 is likely that the user has access to a Web service that provides an
370 SMS service, such as a Web site offering form-based SMS composition.
371 Ideally, the user agent should access this Web service when
372 activating an "sms" URI, thus enabling the user to use the Web
373 service.
375 One problem with this approach is that the Web service should somehow
376 get the "sms" URI, in order interpret it and set the required
377 parameters (such as the receiver's phone number). The easiest way to
378 implement this is for the user agent to add the "sms" URI as query
379 string to the Web service's URI. Consequently, user agents
380 supporting SMS Web services identified by URIs SHOULD append the
381 "sms" URI as query string to the Web services URI when accessing the
382 Web service. Web services providing SMS composition facilities
383 SHOULD expect to receive an "sms" URI as query string and should
384 process it as described by this memo. This method only can be
385 applied for Web service URIs which permit query strings (such as
386 "http" and "https" URIs). For other Web service URIs (such as "ftp"
387 and "mailto"), user agents as well as Web services MUST NOT use the
388 query string.
390 It should be noted that RFC 2396 [RFC2396] defines that within query
391 strings, the characters ";", "/", "?", ":", "@", "&", "=", "+", ",",
392 and "$" are reserved. It is therefore necessary to encode the "sms"
393 URI accordingly before appending it as query string.
395 3.1 Example
397 A document contains this piece of (X)HTML:
399 Send me an SMS!
401 The user agent interpreting this document does not internally support
402 SMS message composition, but has been configured to access a Web
403 service for handling "sms" URIs. This Web service has the following
404 URI:
406 http://sms.example.com/sms-form
408 When the user activates the "sms" URI (eg, by clicking on the text
409 "Send me an SMS!"), the user agents acts as if the activated URI had
410 been:
412 http://sms.example.com/sms-form?sms%3A%2B41796431851
414 The Web service is then responsible for parsing the query string and
415 providing an approriate interface, for example by already filling in
416 the recipient address with the number provided in the "sms" URI.
418 4. Security Considerations
420 The "Security Considerations" section of the SMS service registration
421 memo [draft-wilde-sms-service-06] MUST be consulted.
423 A user agent SHOULD NOT send out SMS messages without the knowledge
424 of the user, because of associated risks, which include sending
425 masses of SMS messages to a subscriber without his consent, and the
426 costs involved in sending an SMS message.
428 The user agent SHOULD have some mechanism that the user can use to
429 filter out unwanted destinations for SMS messages. The user agent
430 SHOULD also have some means of restricting the number of SMS messages
431 being sent as the result of activating one "sms" URI.
433 If an "sms" URI contains a pid-qualifier and the user agent supports
434 the qualifier and its value, then the user agent MUST set the SMS
435 message's PID as specified by the qualifier. User agents MAY inform
436 users about the value and the functional consequences of PID
437 qualifiers (eg, by notifying users that sending the SMS effectively
438 will result in a fax message being delivered, rather than an SMS
439 message).
441 The method described in section Section 3 adds another level of
442 indirection to the handling of "sms" URIs. If this method is
443 combined with the pid-qualifier gateway functionality, SMS
444 composition and reception will probably be distributed over three
445 different protocols (the Web service, SMS transport itself, and the
446 service selected by the pid-qualifier). User agent SHOULD make this
447 clear to users (either when the Web service is being configured, or
448 when it is accessed).
450 The Telematic Interworking functionality of the SMSC addressed by the
451 pid-qualifier is not necessarily implemented by the SMSC being used,
452 and SMSC providers are known for not or not correctly supporting some
453 or all pid-qualifier values. User agents SHOULD take into account
454 that the success rate of SMS messages being sent using pid-qualifiers
455 is lower than that of "plain" SMS messages.
457 5. Change Log
458 5.1 From -00 to -01
460 o Added the "sms-body" field and its processing rules.
462 o Added Section Section 3 about using "sms" URIs as query strings
463 for SMS Web services.
465 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone").
467 o Added some explanatory text about form submissions using email
468 Telematic Interworking.
470 o Added some text about character encoding in form submissions.
472 5.2 From -01 to -02
474 o Changed the sms-body field to URL encoded UTF-8 characters.
476 5.3 From -02 to -03
478 o Changed ordering of "change Log" section (descending to
479 ascending).
481 o Clarified the wording at the beginning of Section Section 2.2
482 about only the keywords of the scheme being case-insensitive.
484 o Changed "sms-body" to be a URI query string.
486 o Added some text describing "sms" URIs as addressing resources.
488 5.4 From -03 to -04
490 o Updated reference to draft-allocchio-gstn (to revision -05).
492 5.5 From -04 to -05
494 o Updated reference to SMS spec to the version referenced in the SMS
495 service draft.
497 5.6 From -05 to -06
499 o Updated reference from draft-allocchio-gstn to RFC 3601.
501 6. References
503 6.1 Normative References
505 [HTML401] Raggett, D., Le Hors, A. and I. Jacobs, "HTML 4.01
506 Specification", W3C REC-html401, December 1999, .
509 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
510 Requirement Levels", RFC 2119, March 1997.
512 [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
513 Specifications: ABNF", RFC 2234, November 1997.
515 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO
516 10646", RFC 2279, January 1998.
518 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
519 Resource Identifiers (URI): Generic Syntax", RFC 2396,
520 August 1998.
522 [RFC3601] Allocchio, C., "Text string notation for Dial Sequences
523 and GSTN / E.164 addresses", RFC 3601, September 2003.
525 [SMS] European Telecommunications Standards Institute, "ETSI TS
526 100 901 (GSM 03.40 version 7.3.0 Release 1998): Digital
527 Cellular Telecommunications System (Phase 2+); Technical
528 realization of the Short Message Service (SMS);
529 Point-to-Point (PP)", November 1999, .
532 [SMS-CHAR]
533 European Telecommunications Standards Institute, "ETSI TS
534 100 901 (GSM 03.38 version 7.2.0 Release 1998): Digital
535 Cellular Telecommunications System (Phase 2+); Alphabets
536 and language-specific information", July 1999, .
539 [draft-wilde-sms-service-06]
540 Wilde, E., "Registration of GSTN SMS Service Qualifier",
541 draft-wilde-sms-service-06 (work in progress), Jul 2004.
543 6.2 Non-Normative References
545 [RFC2368] Hoffmann, P., Masinter, L. and J. Zawinski, "The mailto
546 URL scheme", RFC 2368, June 1998.
548 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
549 June 1999.
551 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806,
552 April 2000.
554 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers
555 for Television Broadcasts", RFC 2838, May 2000.
557 [uri-clarification]
558 World Wide Web Consortium, "URIs, URLs, and URNs:
559 Clarifications and Recommendations 1.0", W3C
560 uri-clarification , September 2001, .
563 Authors' Addresses
565 Erik Wilde
566 Swiss Federal Institute of Technology
567 ETH-Zentrum
568 8092 Zurich
569 Switzerland
571 Phone: +41-1-6325132
572 EMail: erik.wilde@dret.net
573 URI: http://dret.net/netdret/
575 Antti Vaha-Sipila
576 Nokia
578 EMail: antti.vaha-sipila@nokia.com
580 Appendix A. Where to send Comments
582 Please send all comments and questions concerning this document to
583 Erik Wilde.
585 Appendix B. Acknowledgements
587 This document has been prepared using the IETF document DTD described
588 in RFC 2629 [RFC2629].
590 Thanks to Claudio Allocchio for his comments.
592 Intellectual Property Statement
594 The IETF takes no position regarding the validity or scope of any
595 intellectual property or other rights that might be claimed to
596 pertain to the implementation or use of the technology described in
597 this document or the extent to which any license under such rights
598 might or might not be available; neither does it represent that it
599 has made any effort to identify any such rights. Information on the
600 IETF's procedures with respect to rights in standards-track and
601 standards-related documentation can be found in BCP-11. Copies of
602 claims of rights made available for publication and any assurances of
603 licenses to be made available, or the result of an attempt made to
604 obtain a general license or permission for the use of such
605 proprietary rights by implementors or users of this specification can
606 be obtained from the IETF Secretariat.
608 The IETF invites any interested party to bring to its attention any
609 copyrights, patents or patent applications, or other proprietary
610 rights which may cover technology that may be required to practice
611 this standard. Please address the information to the IETF Executive
612 Director.
614 Full Copyright Statement
616 Copyright (C) The Internet Society (2004). All Rights Reserved.
618 This document and translations of it may be copied and furnished to
619 others, and derivative works that comment on or otherwise explain it
620 or assist in its implementation may be prepared, copied, published
621 and distributed, in whole or in part, without restriction of any
622 kind, provided that the above copyright notice and this paragraph are
623 included on all such copies and derivative works. However, this
624 document itself may not be modified in any way, such as by removing
625 the copyright notice or references to the Internet Society or other
626 Internet organizations, except as needed for the purpose of
627 developing Internet standards in which case the procedures for
628 copyrights defined in the Internet Standards process must be
629 followed, or as required to translate it into languages other than
630 English.
632 The limited permissions granted above are perpetual and will not be
633 revoked by the Internet Society or its successors or assignees.
635 This document and the information contained herein is provided on an
636 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
637 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
638 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
639 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
640 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
642 Acknowledgment
644 Funding for the RFC Editor function is currently provided by the
645 Internet Society.