idnits 2.17.1
draft-wilde-sms-uri-10.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** It looks like you're using RFC 3978 boilerplate. You should update this
to the boilerplate described in the IETF Trust License Policy document
(see https://trustee.ietf.org/license-info), which is required now.
-- Found old boilerplate from RFC 3978, Section 5.1 on line 17.
-- Found old boilerplate from RFC 3978, Section 5.5 on line 668.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 645.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 652.
-- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 658.
** This document has an original RFC 3978 Section 5.4 Copyright Line,
instead of the newer IETF Trust Copyright according to RFC 4748.
** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
of the newer disclaimer which includes the IETF Trust according to 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 (Aug 03, 2005) is 6840 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)
-- 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: 6 errors (**), 0 flaws (~~), 3 warnings (==), 13 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: February 4, 2006 Technology
5 A. Vaha-Sipila
6 Nokia
7 Aug 03, 2005
9 URI Scheme for GSM Short Message Service
10 draft-wilde-sms-uri-10
12 Status of this Memo
14 By submitting this Internet-Draft, each author represents that any
15 applicable patent or other IPR claims of which he or she is aware
16 have been or will be disclosed, and any of which he or she becomes
17 aware will be disclosed, in accordance with Section 6 of BCP 79.
19 Internet-Drafts are working documents of the Internet Engineering
20 Task Force (IETF), its areas, and its working groups. Note that
21 other groups may also distribute working documents as Internet-
22 Drafts.
24 Internet-Drafts are draft documents valid for a maximum of six months
25 and may be updated, replaced, or obsoleted by other documents at any
26 time. It is inappropriate to use Internet-Drafts as reference
27 material or to cite them other than as "work in progress."
29 The list of current Internet-Drafts can be accessed at
30 http://www.ietf.org/ietf/1id-abstracts.txt.
32 The list of Internet-Draft Shadow Directories can be accessed at
33 http://www.ietf.org/shadow.html.
35 This Internet-Draft will expire on February 4, 2006.
37 Copyright Notice
39 Copyright (C) The Internet Society (2005).
41 Abstract
43 This memo specifies a URI (Universal Resource Identifier) scheme
44 "sms" for specifying a recipient (and optionally a gateway) for an
45 SMS message. SMS messages are two-way paging messages that can be
46 sent from and received by a mobile phone or a suitably equipped
47 computer.
49 Table of Contents
51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
52 1.1 The Short Message Service . . . . . . . . . . . . . . . . 3
53 1.2 Universal Resource Identifiers . . . . . . . . . . . . . . 3
54 1.3 SMS Messages and the Internet . . . . . . . . . . . . . . 3
55 1.3.1 SMS Messages and the Web . . . . . . . . . . . . . . . 4
56 1.3.2 SMS Messages and Forms . . . . . . . . . . . . . . . . 5
57 2. The "sms" URI Scheme . . . . . . . . . . . . . . . . . . . . . 5
58 2.1 Applicability . . . . . . . . . . . . . . . . . . . . . . 5
59 2.2 Formal Definition . . . . . . . . . . . . . . . . . . . . 6
60 2.3 Parsing an "sms" URI . . . . . . . . . . . . . . . . . . . 7
61 2.4 Examples of Use . . . . . . . . . . . . . . . . . . . . . 7
62 2.5 Using "sms" URIs in HTML Forms . . . . . . . . . . . . . . 8
63 3. "sms" URIs and SMS Web Services . . . . . . . . . . . . . . . 9
64 3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . 9
65 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
66 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 11
67 5.1 From -09 to -10 . . . . . . . . . . . . . . . . . . . . . 11
68 5.2 From -08 to -09 . . . . . . . . . . . . . . . . . . . . . 11
69 5.3 From -07 to -08 . . . . . . . . . . . . . . . . . . . . . 11
70 5.4 From -06 to -07 . . . . . . . . . . . . . . . . . . . . . 11
71 5.5 From -05 to -06 . . . . . . . . . . . . . . . . . . . . . 12
72 5.6 From -04 to -05 . . . . . . . . . . . . . . . . . . . . . 12
73 5.7 From -03 to -04 . . . . . . . . . . . . . . . . . . . . . 12
74 5.8 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . 12
75 5.9 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . 12
76 5.10 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . 12
77 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
78 6.1 Normative References . . . . . . . . . . . . . . . . . . . 13
79 6.2 Non-Normative References . . . . . . . . . . . . . . . . . 13
80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14
81 A. Where to send Comments . . . . . . . . . . . . . . . . . . . . 14
82 B. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
83 Intellectual Property and Copyright Statements . . . . . . . . 15
85 1. Introduction
87 Compliant software MUST follow this specification. The capitalized
88 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
90 document are to be interpreted as described in RFC 2119 [RFC2119].
92 1.1 The Short Message Service
94 The Short Message Service (SMS) [SMS] is a rather simple service for
95 sending messages between SMS clients or, using so-called "Telematic
96 Interworking", from an SMS client through a gateway to a receiver
97 using a different service, such as fax or email. The SMS service is
98 described in more detail in the SMS service registration memo
99 [draft-wilde-sms-service-10].
101 1.2 Universal Resource Identifiers
103 One of the core specifications for identifying resources on the
104 Internet is RFC 3986 [RFC3986], specifying the syntax and semantics
105 of a Universal Resource Identifier (URI). The most important notion
106 of URIs are "schemes", which define a framework within which
107 resources can be identified (and possibly accessed). URIs enable
108 users to identify resources, and are used for very diverse schemes
109 such as access protocols (HTTP, FTP), broadcast media (TV channels
110 [RFC2838]), messaging (email [RFC2368]), or even telephone numbers
111 (voice [RFC2806]).
113 URIs often are mentioned together with Universal Resource Names
114 (URNs) and/or Uniform Resource Locators (URLs), and it often is
115 unclear how to separate these concepts. For the purpose of this
116 memo, only the term URI will be used, referring to the most
117 fundamental concept. The World Wide Web Consortium (W3C) has issued
118 a note [uri-clarification] discussing the topic of URIs, URNs, and
119 URLs in detail.
121 1.3 SMS Messages and the Internet
123 One of the important reasons for the universal access of the Web is
124 the ability to access all information through a unique interface.
125 This kind of integration makes it easy to provide information as well
126 as to consume it. One aspect of this integration is the support of
127 user agents (in the case of the Web, commonly referred to as
128 browsers) for multiple content formats (such as HTML, GIF, JPEG) and
129 access schemes (such as HTTP, HTTP-S, FTP).
131 The "mailto" scheme has proven to be very useful and popular, because
132 most user agents support it by providing an email composition
133 facility when the user activates (eg, clicks on) the URI.
134 Accordingly, the "sms" scheme could be supported by user agents by
135 providing an SMS message composition facility when the user activates
136 the URI. Alternatively, in cases where the user agent does not
137 provide a built-in SMS message composition facility, the scheme could
138 still be supported by opening a Web page which provides such a
139 service. The specific Web page to be used could be configured by the
140 user, so that each user could use the SMS message composition service
141 of his choice.
143 The goal of this memo is to specify the "sms" URI scheme, so that
144 user agents (such as Web browsers and email clients) could start to
145 support it. The "sms" URI scheme identifies SMS message endpoints as
146 resources. When "sms" URIs are dereferenced, implementations MAY
147 create a message and present it to be edited before being sent, or
148 they MAY use additional services to provide the functionality
149 necessary for composing a message and sending it to the SMS message
150 endpoint.
152 1.3.1 SMS Messages and the Web
154 SMS messages can provide an alternative to a "mailto" URIs [RFC2368],
155 or "tel" or "fax" URIs [RFC2806]. When a "sms" URI is activated, the
156 user agent MAY start a program for sending an SMS message, just as
157 "mailto" may open a mail client. Unfortunately, most browsers do not
158 support the external handling of internally unsupported URI schemes
159 in the same generalized way as most of them support external handling
160 of additional MIME type content for types which they do not support
161 internally. Ideally, user agents should implement generic URI
162 parsers and provide a way to associate unsupported schemes with
163 external applications (or Web services).
165 The recipient of an SMS message need not be a mobile phone. It can
166 be a server that can process SMS messages, either by gatewaying them
167 to another messaging system (such as regular electronic mail), or by
168 parsing them for supplementary services.
170 SMS messages can be used to transport almost any kind of data (even
171 though there is a very tight size limit), but the only standardized
172 data formats are character-based messages in different character
173 encodings. SMS messages have a maximum length of 160 characters
174 (when using 7-bit characters from the SMS character set), or 140
175 octets. However, SMS messages can be concatenated to form longer
176 messages. It is up to the user agent to decide whether to limit the
177 length of the message, and how to indicate this limit in its user
178 interface, if necessary. There is one exception to this, see
179 Section 2.5.
181 1.3.2 SMS Messages and Forms
183 The Hypertext Markup Language (HTML) [HTML401] provides a way to
184 collect information from a user and pass it to a server for
185 processing. This functionality is known as "HTML forms". A
186 filled-in form is usually sent to the destination using the Hypertext
187 Transfer Protocol (HTTP) or email. However, SMS messages can also be
188 used as the transport mechanism for these forms. As SMS transport is
189 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this
190 provides a way to fill in forms offline, and send the data without
191 making a TCP connection to the server, as the set-up time, cost, and
192 overhead for a TCP connection are large compared to an SMS message.
193 Also, depending on the network configuration, the sender's telephone
194 number may be included in the SMS message, thus providing a weak form
195 of authentication.
197 2. The "sms" URI Scheme
199 Syntax definitions are given using the Augmented BNF for Syntax
200 Specifications [RFC2234].
202 2.1 Applicability
204 This URI scheme is intended for sending an SMS message to a certain
205 recipient(s). The functionality is quite similar to that of the
206 "mailto" URL, which (as per RFC 2368 [RFC2368]) can also be used with
207 a comma-separated list of email addresses.
209 In some situations, it may be necessary to guide the sender to send
210 the SMS message via a certain SMSC. For this purpose, the URI may
211 specify the number of the SMSC.
213 SMS messages may be sent through gateways to other services. These
214 gateways are operated inside SMS centers. An "SMS" URI may specify
215 that a certain gateway should be used.
217 The notation for phone numbers is taken from [RFC3601]. Refer to
218 this document for information on why this particular format was
219 chosen.
221 How the SMS message is sent to the SMSC is outside the scope of this
222 specification. SMS messages can be sent over the GSM air interface,
223 by using a modem and a suitable protocol, or by accessing services
224 over other protocols, such as a Web service for sending SMS messages.
225 Also, SMS message service options like deferred delivery and delivery
226 notification requests are not in the scope of this document. Such
227 services MAY be requested from the network by the user agent if
228 necessary.
230 SMS messages sent as a result of this URI MUST be sent as class 1 SMS
231 messages, if the user agent is able to specify the message class.
233 2.2 Formal Definition
235 The URI scheme's keywords specified in the following syntax
236 description are case-insensitive. The syntax of an "sms" URI is
237 formally described as follows, where the base syntax is taken from
238 RFC 3986 [RFC3986]:
240 sms-uri = scheme ":" hier-part [ "?" sms-body ]
241 scheme = "sms"
242 hier-part = sms-recipient *( "," sms-recipient )
243 sms-recipient = gstn-phone sms-qualifier
244 sms-qualifier = *( smsc-qualifier / pid-qualifier )
245 smsc-qualifier = ";smsc=" SMSC-sub-addr
246 pid-qualifier = ";pid=" PID-sub-addr
247 sms-body = "body=" query
249 The syntax definition for "gstn-phone" is taken from RFC 3601
250 [RFC3601], allowing global as well as local telephone numbers.
252 The syntax definition for "query" is taken from RFC 3986 [RFC3986],
253 please refer to that document.
255 The syntax definition for "SMSC-sub-addr" and "PID-sub-addr" is
256 derived from [draft-wilde-sms-service-10], please refer to that
257 document for the syntax of the qualifier values.
259 The "sms-body" is used to define the body of the SMS message to be
260 composed. It consists of percent-encoded UTF-8 characters.
261 Implementations MUST make sure that the sms-body characters are
262 converted to a suitable character encoding before sending, the most
263 popular being the 7-bit SMS character encoding, another variant
264 (though not as universally supported as 7-bit SMS) is the UCS-2
265 character encoding (both specified in [SMS-CHAR]). Implementations
266 MAY choose to silently discard (or convert) characters in the sms-
267 body that are not supported by the SMS character set they are using
268 to send the SMS message.
270 It should be noted that both the SMSC as well as the PID qualifier
271 may appear only once per sms-recipient. If multiple SMSC or PID
272 qualifiers are present, conforming software MUST interpret the first
273 occurrence and ignore all other occurrences.
275 2.3 Parsing an "sms" URI
277 The following list describes the steps for processing an "sms" URI:
279 1. The "gstn-phone" of the first "sms-recipient" is extracted. It
280 is the phone number of the final recipient and it MUST be written
281 in international form with country code, unless the number only
282 works from inside a certain geographical area or a network. Note
283 that some numbers may work from several networks but not from the
284 whole world - these SHOULD be written in international form.
285 According to [RFC3601], all international numbers MUST begin with
286 a "+" character. Hyphens and dots are only to aid readability.
287 They MUST NOT have any other meaning.
289 2. The "smsc-qualifier" of the first "sms-recipient" is extracted,
290 if present.
292 3. The "pid-qualifier" of the first "sms-recipient" is extracted, if
293 present.
295 4. The "sms-body" is extracted, if present.
297 5. The user agent should provide some means for message composition,
298 either by implementing this itself, or by accessing a service
299 providing it. Message composition SHOULD start with the body
300 extracted from the "sms-body", if present. If the "pid-
301 qualifier" is set to "pid=SMTP:...", then the user agents must
302 make sure that the email address is correctly set (as defined by
303 the SMS specification [SMS]) in the message being composed.
305 6. After message composition, a user agent SHOULD try to send the
306 message first using the SMSC set in the "smsc-qualifier" (if
307 present). If that fails, the user agent MAY try another SMSC.
309 7. If the URI consists of a comma-separated list of recipients (ie,
310 contains multiple "sms-recipient" parts), all of them are
311 processed in this manner. Exactly the same message SHOULD be
312 sent to all of the listed recipients.
314 2.4 Examples of Use
316 sms:+41796431851
318 This indicates an SMS message capable recipient at the given
319 telephone number. The message is sent using the user agent's default
320 SMSC.
322 sms:+41796431851;smsc=+41794999000
324 This indicates that the SMS message should be sent using the SMSC at
325 the given number.
327 sms:+41796431851,+4116321035;pid=fax
329 This URI should result in two SMS messages being sent, one to the
330 recipient number as shown in the example above, the other one being
331 sent as a fax to the second number (the fax is sent by the SMSC
332 performing the gatewaying, not by the user agent).
334 sms:+41796431851;pid=smtp:erik.wilde@dret.net?body=hello%20there
336 In this case, a message (initially being set to "hello there", which
337 may have been modified by the user before sending) will be sent via
338 SMS using the SMS to email functionality in the SMSC, so that it will
339 eventually result in an email being sent to the specified email
340 address. In this case, the phone number will not be interpreted.
342 2.5 Using "sms" URIs in HTML Forms
344 When using a "sms" type URI as an action URI for HTML form submission
345 [HTML401], the form contents MUST be packaged in the SMS message just
346 as they are packaged when using a "mailto" URL [RFC2368], using the
347 "application/x-www-form-urlencoded" MIME type, effectively packaging
348 all form data into URI compliant syntax [RFC3986]. The SMS message
349 MUST NOT contain any HTTP headers, only the form data. The MIME type
350 is implicit. It MUST NOT be transferred in the SMS message.
352 The character encoding used for form submissions MUST be UTF-8
353 [RFC2279]. It should be noted, however, that user agents MUST
354 percent-encode form submissions before sending them.
356 The user agent SHOULD inform the user about the possible security
357 hazards involved when submitting the form (it is probably being sent
358 as plain text over an air interface).
360 If the form submission is longer than the maximum SMS message size,
361 the user agent MAY either concatenate SMS messages, if it is able to
362 do so, or it MAY refuse to send the message. The user agent MUST NOT
363 send out partial form submissions.
365 Form submission via an "sms" URI can be combined with Telematic
366 Interworking to result in form submissions being submitted via an SMS
367 message and finally being sent to an email account. In this case,
368 all provisions for using the email "pid-qualifier" and using "sms"
369 URIs with HTML forms must be followed.
371 3. "sms" URIs and SMS Web Services
373 In many cases, user agents will not be able to directly compose and
374 send SMS messages (because this requires that such a service is
375 accessible to the system the user agent is running on). However, it
376 is likely that the user has access to a Web service that provides an
377 SMS service, such as a Web site offering form-based SMS composition.
378 Ideally, the user agent should access this Web service when
379 activating an "sms" URI, thus enabling the user to use the Web
380 service.
382 One problem with this approach is that the Web service should somehow
383 get the "sms" URI, in order to interpret it and set the required
384 parameters (such as the receiver's phone number). The easiest way to
385 implement this is for the user agent to add the "sms" URI as query
386 string to the Web service's URI. Consequently, user agents
387 supporting SMS Web services identified by URIs SHOULD append the
388 "sms" URI as query string to the Web services URI when accessing the
389 Web service. Web services providing SMS composition facilities
390 SHOULD expect to receive an "sms" URI as query string and should
391 process it as described by this memo. This method only can be
392 applied for Web service URIs which permit query strings (such as
393 "http" and "https" URIs). For other Web service URIs (such as "ftp"
394 and "mailto"), user agents as well as Web services MUST NOT use the
395 query string.
397 It should be noted that RFC 3986 [RFC3986] defines that within query
398 strings, the "gen-delims" characters ":", "/", "?", "#", "[", "]",
399 and "@" are reserved. It is therefore necessary to encode the "sms"
400 URI accordingly before appending it as query string.
402 3.1 Example
404 A document contains this fragment of (X)HTML:
406 Send me an SMS!
408 The user agent interpreting this document does not internally support
409 SMS message composition or sending, but has been configured to access
410 a Web service for handling "sms" URIs. This Web service has the
411 following URI:
413 http://sms.example.com/sms-form
414 When the user activates the "sms" URI (eg, by clicking on the text
415 "Send me an SMS!"), the user agents sends a request to the SMS Web
416 service and acts as if the activated URI had been:
418 http://sms.example.com/sms-form?sms%3A+41796431851
420 The SMS Web service is then responsible for parsing the query string
421 and providing an approriate interface, for example by already filling
422 in the recipient address with the number provided by the "sms" URI.
423 This way, the non-SMS capable user agent and the SMS Web service can
424 interact to provide the best integration of Web browsing and SMS
425 sending to the user.
427 4. Security Considerations
429 The "Security Considerations" section of the SMS service registration
430 memo [draft-wilde-sms-service-10] MUST be consulted.
432 A user agent SHOULD NOT send out SMS messages without the knowledge
433 of the user, because of associated risks, which include sending
434 masses of SMS messages to a subscriber without his consent, and the
435 costs involved in sending an SMS message.
437 The user agent SHOULD have some mechanism that the user can use to
438 filter out unwanted destinations for SMS messages. The user agent
439 SHOULD also have some means of restricting the number of SMS messages
440 being sent as the result of activating one "sms" URI.
442 If an "sms" URI contains a pid-qualifier and the user agent supports
443 the qualifier and its value, then the user agent MUST set the SMS
444 message's PID as specified by the qualifier. User agents MAY inform
445 users about the value and the functional consequences of PID
446 qualifiers (eg, by notifying users that sending the SMS effectively
447 will result in a fax message being delivered, rather than an SMS
448 message).
450 The method described in section Section 3 adds another level of
451 indirection to the handling of "sms" URIs. If this method is
452 combined with the pid-qualifier gateway functionality, SMS
453 composition and reception will probably be distributed over three
454 different protocols (the Web service, SMS transport itself, and the
455 service selected by the pid-qualifier). User agents SHOULD make this
456 clear to users (either when the Web service is being configured, or
457 when it is accessed).
459 The Telematic Interworking functionality of the SMSC addressed by the
460 pid-qualifier is not necessarily implemented by the SMSC being used,
461 and SMSC providers are known for not or not correctly supporting some
462 or all pid-qualifier values. User agents SHOULD take into account
463 that the success rate of SMS messages being sent using pid-qualifiers
464 is lower than that of "plain" SMS messages.
466 As suggested functionality, the user agent MAY offer a possibility
467 for the user to filter out those gstn-phone numbers that are
468 expressed in local format, as most premium-rate numbers are expressed
469 in local format, and because determining the correct local context
470 (and hence the validity of the number to this specific user) may be
471 very difficult.
473 5. Change Log
475 This section will not be part of the final RFC text, it serves as a
476 container to collect the history of the individual draft versions.
478 5.1 From -09 to -10
480 o Added security consideration about filtering local format phone
481 numbers.
483 o Changed IPR clause from RFC 3667 to RFC 3978 (updated version of
484 RFC 3667).
486 5.2 From -08 to -09
488 o Fixed syntax error in hier-part and sms-recipient non-terminals,
489 which allowed sms-recipients to be concatenated without comma
490 separation.
492 5.3 From -07 to -08
494 o URIs are now defined by RFC 3986 [RFC3986], so the text (including
495 the syntax definitions) and the references have been updated.
497 5.4 From -06 to -07
499 o Changed IPR clause from RFC 2026 to RFC 3667 (updated version of
500 RFC 2026).
502 5.5 From -05 to -06
504 o Updated reference from draft-allocchio-gstn to RFC 3601.
506 5.6 From -04 to -05
508 o Updated reference to SMS spec to the version referenced in the SMS
509 service draft.
511 5.7 From -03 to -04
513 o Updated reference to draft-allocchio-gstn (to revision -05).
515 5.8 From -02 to -03
517 o Changed ordering of "change Log" section (descending to
518 ascending).
520 o Clarified the wording at the beginning of Section Section 2.2
521 about only the keywords of the scheme being case-insensitive.
523 o Changed "sms-body" to be a URI query string.
525 o Added some text describing "sms" URIs as addressing resources.
527 5.9 From -01 to -02
529 o Changed the sms-body field to percent-encoded UTF-8 characters.
531 5.10 From -00 to -01
533 o Added the "sms-body" field and its processing rules.
535 o Added Section Section 3 about using "sms" URIs as query strings
536 for SMS Web services.
538 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone").
540 o Added some explanatory text about form submissions using email
541 Telematic Interworking.
543 o Added some text about character encoding in form submissions.
545 6. References
547 6.1 Normative References
549 [HTML401] Raggett, D., Le Hors, A., and I. Jacobs, "HTML 4.01
550 Specification", W3C REC-html401, December 1999,
551 .
553 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
554 Requirement Levels", RFC 2119, March 1997.
556 [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
557 Specifications: ABNF", RFC 2234, November 1997.
559 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO
560 10646", RFC 2279, January 1998.
562 [RFC3601] Allocchio, C., "Text string notation for Dial Sequences
563 and GSTN / E.164 addresses", RFC 3601, September 2003.
565 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
566 Resource Identifier (URI): Generic Syntax", RFC 3986,
567 January 2005.
569 [SMS] European Telecommunications Standards Institute, "ETSI TS
570 100 901 (GSM 03.40 version 7.3.0 Release 1998): Digital
571 Cellular Telecommunications System (Phase 2+); Technical
572 realization of the Short Message Service (SMS); Point-to-
573 Point (PP)", November 1999,
574 .
576 [SMS-CHAR]
577 European Telecommunications Standards Institute, "ETSI TS
578 100 901 (GSM 03.38 version 7.2.0 Release 1998): Digital
579 Cellular Telecommunications System (Phase 2+); Alphabets
580 and language-specific information", July 1999,
581 .
583 [draft-wilde-sms-service-10]
584 Wilde, E., "Registration of GSTN SMS Service Qualifier",
585 draft-wilde-sms-service-10 (work in progress), Aug 2005.
587 6.2 Non-Normative References
589 [RFC2368] Hoffmann, P., Masinter, L., and J. Zawinski, "The mailto
590 URL scheme", RFC 2368, June 1998.
592 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
593 June 1999.
595 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806,
596 April 2000.
598 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers
599 for Television Broadcasts", RFC 2838, May 2000.
601 [uri-clarification]
602 World Wide Web Consortium, "URIs, URLs, and URNs:
603 Clarifications and Recommendations 1.0", W3C uri-
604 clarification , September 2001,
605 .
607 Authors' Addresses
609 Erik Wilde
610 Swiss Federal Institute of Technology
611 ETH-Zentrum
612 8092 Zurich
613 Switzerland
615 Phone: +41-1-6325132
616 Email: erik.wilde@dret.net
617 URI: http://dret.net/netdret/
619 Antti Vaha-Sipila
620 Nokia
622 Email: antti.vaha-sipila@nokia.com
624 Appendix A. Where to send Comments
626 Please send all comments and questions concerning this document to
627 Erik Wilde.
629 Appendix B. Acknowledgements
631 This document has been prepared using the IETF document DTD described
632 in RFC 2629 [RFC2629].
634 Thanks to Claudio Allocchio for his comments.
636 Intellectual Property Statement
638 The IETF takes no position regarding the validity or scope of any
639 Intellectual Property Rights or other rights that might be claimed to
640 pertain to the implementation or use of the technology described in
641 this document or the extent to which any license under such rights
642 might or might not be available; nor does it represent that it has
643 made any independent effort to identify any such rights. Information
644 on the procedures with respect to rights in RFC documents can be
645 found in BCP 78 and BCP 79.
647 Copies of IPR disclosures made to the IETF Secretariat and any
648 assurances of licenses to be made available, or the result of an
649 attempt made to obtain a general license or permission for the use of
650 such proprietary rights by implementers or users of this
651 specification can be obtained from the IETF on-line IPR repository at
652 http://www.ietf.org/ipr.
654 The IETF invites any interested party to bring to its attention any
655 copyrights, patents or patent applications, or other proprietary
656 rights that may cover technology that may be required to implement
657 this standard. Please address the information to the IETF at
658 ietf-ipr@ietf.org.
660 Disclaimer of Validity
662 This document and the information contained herein are provided on an
663 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
664 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
665 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
666 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
667 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
668 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
670 Copyright Statement
672 Copyright (C) The Internet Society (2005). This document is subject
673 to the rights, licenses and restrictions contained in BCP 78, and
674 except as set forth therein, the authors retain all their rights.
676 Acknowledgment
678 Funding for the RFC Editor function is currently provided by the
679 Internet Society.