idnits 2.17.1 draft-wilde-sms-uri-08.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.a on line 19. -- Found old boilerplate from RFC 3978, Section 5.5 on line 648. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 625. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 632. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 638. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** 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. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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 (Jan 29, 2005) is 7020 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: 8 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: August 2, 2005 Technology 5 A. Vaha-Sipila 6 Nokia 7 Jan 29, 2005 9 URI scheme for GSM Short Message Service 10 draft-wilde-sms-uri-08 12 Status of this Memo 14 This document is an Internet-Draft and is subject to all provisions 15 of Section 3 of RFC 3667. By submitting this Internet-Draft, each 16 author represents that any applicable patent or other IPR claims of 17 which he or she is aware have been or will be disclosed, and any of 18 which he or she become aware will be disclosed, in accordance with 19 RFC 3668. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as 24 Internet-Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 This Internet-Draft will expire on August 2, 2005. 39 Copyright Notice 41 Copyright (C) The Internet Society (2005). 43 Abstract 45 This memo specifies a URI (Universal Resource Identifier) scheme 46 "sms" for specifying a recipient (and optionally a gateway) for an 47 SMS message. SMS messages are two-way paging messages that can be 48 sent from and received by a mobile phone or a suitably equipped 49 computer. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1 The Short Message Service . . . . . . . . . . . . . . . . 3 55 1.2 Universal Resource Identifiers . . . . . . . . . . . . . . 3 56 1.3 SMS Messages and the Internet . . . . . . . . . . . . . . 3 57 1.3.1 SMS Messages and the Web . . . . . . . . . . . . . . . 4 58 1.3.2 SMS Messages and Forms . . . . . . . . . . . . . . . . 5 59 2. The "sms" URI Scheme . . . . . . . . . . . . . . . . . . . . . 5 60 2.1 Applicability . . . . . . . . . . . . . . . . . . . . . . 5 61 2.2 Formal Definition . . . . . . . . . . . . . . . . . . . . 6 62 2.3 Parsing an "sms" URI . . . . . . . . . . . . . . . . . . . 7 63 2.4 Examples of Use . . . . . . . . . . . . . . . . . . . . . 7 64 2.5 Using "sms" URIs in HTML Forms . . . . . . . . . . . . . . 8 65 3. "sms" URIs and SMS Web Services . . . . . . . . . . . . . . . 9 66 3.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . 9 67 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 68 5. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 11 69 5.1 From -07 to -08 . . . . . . . . . . . . . . . . . . . . . 11 70 5.2 From -06 to -07 . . . . . . . . . . . . . . . . . . . . . 11 71 5.3 From -05 to -06 . . . . . . . . . . . . . . . . . . . . . 11 72 5.4 From -04 to -05 . . . . . . . . . . . . . . . . . . . . . 11 73 5.5 From -03 to -04 . . . . . . . . . . . . . . . . . . . . . 11 74 5.6 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . 11 75 5.7 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . 12 76 5.8 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . 12 77 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 78 6.1 Normative References . . . . . . . . . . . . . . . . . . . 12 79 6.2 Non-Normative References . . . . . . . . . . . . . . . . . 13 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 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-08]. 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 = 1*( sms-recipient ) 243 sms-recipient = gstn-phone sms-qualifier [ "," sms-recipient ] 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-08], 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 267 sms-body that are not supported by the SMS character set they are 268 using 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 301 "pid-qualifier" is set to "pid=SMTP:...", then the user agents 302 must make sure that the email address is correctly set (as 303 defined by the SMS specification [SMS]) in the message being 304 composed. 306 6. After message composition, a user agent SHOULD try to send the 307 message first using the SMSC set in the "smsc-qualifier" (if 308 present). If that fails, the user agent MAY try another SMSC. 310 7. If the URI consists of a comma-separated list of recipients (ie, 311 contains multiple "sms-recipient" parts), all of them are 312 processed in this manner. Exactly the same message SHOULD be 313 sent to all of the listed recipients. 315 2.4 Examples of Use 317 sms:+41796431851 319 This indicates an SMS message capable recipient at the given 320 telephone number. The message is sent using the user agent's default 321 SMSC. 323 sms:+41796431851;smsc=+41794999000 325 This indicates that the SMS message should be sent using the SMSC at 326 the given number. 328 sms:+41796431851,+4116321035;pid=fax 330 This URI should result in two SMS messages being sent, one to the 331 recipient number as shown in the example above, the other one being 332 sent as a fax to the second number (the fax is sent by the SMSC 333 performing the gatewaying, not by the user agent). 335 sms:+41796431851;pid=smtp:erik.wilde@dret.net?body=hello%20there 337 In this case, a message (initially being set to "hello there", which 338 may have been modified by the user before sending) will be sent via 339 SMS using the SMS to email functionality in the SMSC, so that it will 340 eventually result in an email being sent to the specified email 341 address. In this case, the phone number will not be interpreted. 343 2.5 Using "sms" URIs in HTML Forms 345 When using a "sms" type URI as an action URI for HTML form submission 346 [HTML401], the form contents MUST be packaged in the SMS message just 347 as they are packaged when using a "mailto" URL [RFC2368], using the 348 "application/x-www-form-urlencoded" MIME type, effectively packaging 349 all form data into URI compliant syntax [RFC3986]. The SMS message 350 MUST NOT contain any HTTP headers, only the form data. The MIME type 351 is implicit. It MUST NOT be transferred in the SMS message. 353 The character encoding used for form submissions MUST be UTF-8 354 [RFC2279]. It should be noted, however, that user agents MUST 355 percent-encode form submissions before sending them. 357 The user agent SHOULD inform the user about the possible security 358 hazards involved when submitting the form (it is probably being sent 359 as plain text over an air interface). 361 If the form submission is longer than the maximum SMS message size, 362 the user agent MAY either concatenate SMS messages, if it is able to 363 do so, or it MAY refuse to send the message. The user agent MUST NOT 364 send out partial form submissions. 366 Form submission via an "sms" URI can be combined with Telematic 367 Interworking to result in form submissions being submitted via an SMS 368 message and finally being sent to an email account. In this case, 369 all provisions for using the email "pid-qualifier" and using "sms" 370 URIs with HTML forms must be followed. 372 3. "sms" URIs and SMS Web Services 374 In many cases, user agents will not be able to directly compose and 375 send SMS messages (because this requires that such a service is 376 accessible to the system the user agent is running on). However, it 377 is likely that the user has access to a Web service that provides an 378 SMS service, such as a Web site offering form-based SMS composition. 379 Ideally, the user agent should access this Web service when 380 activating an "sms" URI, thus enabling the user to use the Web 381 service. 383 One problem with this approach is that the Web service should somehow 384 get the "sms" URI, in order to interpret it and set the required 385 parameters (such as the receiver's phone number). The easiest way to 386 implement this is for the user agent to add the "sms" URI as query 387 string to the Web service's URI. Consequently, user agents 388 supporting SMS Web services identified by URIs SHOULD append the 389 "sms" URI as query string to the Web services URI when accessing the 390 Web service. Web services providing SMS composition facilities 391 SHOULD expect to receive an "sms" URI as query string and should 392 process it as described by this memo. This method only can be 393 applied for Web service URIs which permit query strings (such as 394 "http" and "https" URIs). For other Web service URIs (such as "ftp" 395 and "mailto"), user agents as well as Web services MUST NOT use the 396 query string. 398 It should be noted that RFC 3986 [RFC3986] defines that within query 399 strings, the "gen-delims" characters ":", "/", "?", "#", "[", "]", 400 and "@" are reserved. It is therefore necessary to encode the "sms" 401 URI accordingly before appending it as query string. 403 3.1 Example 405 A document contains this fragment of (X)HTML: 407 Send me an SMS! 409 The user agent interpreting this document does not internally support 410 SMS message composition or sending, but has been configured to access 411 a Web service for handling "sms" URIs. This Web service has the 412 following URI: 414 http://sms.example.com/sms-form 416 When the user activates the "sms" URI (eg, by clicking on the text 417 "Send me an SMS!"), the user agents sends a request to the SMS Web 418 service and acts as if the activated URI had been: 420 http://sms.example.com/sms-form?sms%3A+41796431851 422 The SMS Web service is then responsible for parsing the query string 423 and providing an approriate interface, for example by already filling 424 in the recipient address with the number provided by the "sms" URI. 425 This way, the non-SMS capable user agent and the SMS Web service can 426 interact to provide the best integration of Web browsing and SMS 427 sending to the user. 429 4. Security Considerations 431 The "Security Considerations" section of the SMS service registration 432 memo [draft-wilde-sms-service-08] MUST be consulted. 434 A user agent SHOULD NOT send out SMS messages without the knowledge 435 of the user, because of associated risks, which include sending 436 masses of SMS messages to a subscriber without his consent, and the 437 costs involved in sending an SMS message. 439 The user agent SHOULD have some mechanism that the user can use to 440 filter out unwanted destinations for SMS messages. The user agent 441 SHOULD also have some means of restricting the number of SMS messages 442 being sent as the result of activating one "sms" URI. 444 If an "sms" URI contains a pid-qualifier and the user agent supports 445 the qualifier and its value, then the user agent MUST set the SMS 446 message's PID as specified by the qualifier. User agents MAY inform 447 users about the value and the functional consequences of PID 448 qualifiers (eg, by notifying users that sending the SMS effectively 449 will result in a fax message being delivered, rather than an SMS 450 message). 452 The method described in section Section 3 adds another level of 453 indirection to the handling of "sms" URIs. If this method is 454 combined with the pid-qualifier gateway functionality, SMS 455 composition and reception will probably be distributed over three 456 different protocols (the Web service, SMS transport itself, and the 457 service selected by the pid-qualifier). User agents SHOULD make this 458 clear to users (either when the Web service is being configured, or 459 when it is accessed). 461 The Telematic Interworking functionality of the SMSC addressed by the 462 pid-qualifier is not necessarily implemented by the SMSC being used, 463 and SMSC providers are known for not or not correctly supporting some 464 or all pid-qualifier values. User agents SHOULD take into account 465 that the success rate of SMS messages being sent using pid-qualifiers 466 is lower than that of "plain" SMS messages. 468 5. Change Log 470 This section will not be part of the final RFC text, it serves as a 471 container to collect the history of the individual draft versions. 473 5.1 From -07 to -08 475 o URIs are now defined by RFC 3986 [RFC3986], so the text (including 476 the syntax definitions) and the references have been updated. 478 5.2 From -06 to -07 480 o Changed IPR clause from RFC 2026 to RFC 3667 (updated version of 481 RFC 2026) 483 5.3 From -05 to -06 485 o Updated reference from draft-allocchio-gstn to RFC 3601. 487 5.4 From -04 to -05 489 o Updated reference to SMS spec to the version referenced in the SMS 490 service draft. 492 5.5 From -03 to -04 494 o Updated reference to draft-allocchio-gstn (to revision -05). 496 5.6 From -02 to -03 498 o Changed ordering of "change Log" section (descending to 499 ascending). 501 o Clarified the wording at the beginning of Section Section 2.2 502 about only the keywords of the scheme being case-insensitive. 504 o Changed "sms-body" to be a URI query string. 506 o Added some text describing "sms" URIs as addressing resources. 508 5.7 From -01 to -02 510 o Changed the sms-body field to percent-encoded UTF-8 characters. 512 5.8 From -00 to -01 514 o Added the "sms-body" field and its processing rules. 516 o Added Section Section 3 about using "sms" URIs as query strings 517 for SMS Web services. 519 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone"). 521 o Added some explanatory text about form submissions using email 522 Telematic Interworking. 524 o Added some text about character encoding in form submissions. 526 6. References 528 6.1 Normative References 530 [HTML401] Raggett, D., Le Hors, A. and I. Jacobs, "HTML 4.01 531 Specification", W3C REC-html401, December 1999, 532 . 534 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 535 Requirement Levels", RFC 2119, March 1997. 537 [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 538 Specifications: ABNF", RFC 2234, November 1997. 540 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 541 10646", RFC 2279, January 1998. 543 [RFC3601] Allocchio, C., "Text string notation for Dial Sequences 544 and GSTN / E.164 addresses", RFC 3601, September 2003. 546 [RFC3986] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 547 Resource Identifier (URI): Generic Syntax", RFC 3986, 548 January 2005. 550 [SMS] European Telecommunications Standards Institute, "ETSI TS 551 100 901 (GSM 03.40 version 7.3.0 Release 1998): Digital 552 Cellular Telecommunications System (Phase 2+); Technical 553 realization of the Short Message Service (SMS); 554 Point-to-Point (PP)", November 1999, 555 . 557 [SMS-CHAR] 558 European Telecommunications Standards Institute, "ETSI TS 559 100 901 (GSM 03.38 version 7.2.0 Release 1998): Digital 560 Cellular Telecommunications System (Phase 2+); Alphabets 561 and language-specific information", July 1999, 562 . 564 [draft-wilde-sms-service-08] 565 Wilde, E., "Registration of GSTN SMS Service Qualifier", 566 Internet-Draft draft-wilde-sms-service-08, Jan 2005. 568 6.2 Non-Normative References 570 [RFC2368] Hoffmann, P., Masinter, L. and J. Zawinski, "The mailto 571 URL scheme", RFC 2368, June 1998. 573 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 574 June 1999. 576 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, 577 April 2000. 579 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers 580 for Television Broadcasts", RFC 2838, May 2000. 582 [uri-clarification] 583 World Wide Web Consortium, "URIs, URLs, and URNs: 584 Clarifications and Recommendations 1.0", 585 W3C uri-clarification , September 2001, 586 . 588 Authors' Addresses 590 Erik Wilde 591 Swiss Federal Institute of Technology 592 ETH-Zentrum 593 8092 Zurich 594 Switzerland 596 Phone: +41-1-6325132 597 Email: erik.wilde@dret.net 598 URI: http://dret.net/netdret/ 599 Antti Vaha-Sipila 600 Nokia 602 Email: antti.vaha-sipila@nokia.com 604 Appendix A. Where to send Comments 606 Please send all comments and questions concerning this document to 607 Erik Wilde. 609 Appendix B. Acknowledgements 611 This document has been prepared using the IETF document DTD described 612 in RFC 2629 [RFC2629]. 614 Thanks to Claudio Allocchio for his comments. 616 Intellectual Property Statement 618 The IETF takes no position regarding the validity or scope of any 619 Intellectual Property Rights or other rights that might be claimed to 620 pertain to the implementation or use of the technology described in 621 this document or the extent to which any license under such rights 622 might or might not be available; nor does it represent that it has 623 made any independent effort to identify any such rights. Information 624 on the procedures with respect to rights in RFC documents can be 625 found in BCP 78 and BCP 79. 627 Copies of IPR disclosures made to the IETF Secretariat and any 628 assurances of licenses to be made available, or the result of an 629 attempt made to obtain a general license or permission for the use of 630 such proprietary rights by implementers or users of this 631 specification can be obtained from the IETF on-line IPR repository at 632 http://www.ietf.org/ipr. 634 The IETF invites any interested party to bring to its attention any 635 copyrights, patents or patent applications, or other proprietary 636 rights that may cover technology that may be required to implement 637 this standard. Please address the information to the IETF at 638 ietf-ipr@ietf.org. 640 Disclaimer of Validity 642 This document and the information contained herein are provided on an 643 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 644 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 645 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 646 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 647 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 648 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 650 Copyright Statement 652 Copyright (C) The Internet Society (2005). This document is subject 653 to the rights, licenses and restrictions contained in BCP 78, and 654 except as set forth therein, the authors retain all their rights. 656 Acknowledgment 658 Funding for the RFC Editor function is currently provided by the 659 Internet Society.