idnits 2.17.1 draft-wilde-sms-uri-11.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 686. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 663. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 670. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 676. ** 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 (Feb 08, 2006) is 6651 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 2279 (Obsoleted by RFC 3629) ** Obsolete normative reference: RFC 4234 (Obsoleted by RFC 5234) -- 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: August 12, 2006 Technology 5 A. Vaha-Sipila 6 Nokia 7 Feb 08, 2006 9 URI Scheme for GSM Short Message Service 10 draft-wilde-sms-uri-11 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 August 12, 2006. 37 Copyright Notice 39 Copyright (C) The Internet Society (2006). 41 Abstract 43 This memo specifies the Universal Resource Identifier (URI) 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 2. The "sms" URI Scheme . . . . . . . . . . . . . . . . . . . . . 5 56 2.1. Applicability . . . . . . . . . . . . . . . . . . . . . . 5 57 2.2. Formal Definition . . . . . . . . . . . . . . . . . . . . 6 58 2.3. Parsing an "sms" URI . . . . . . . . . . . . . . . . . . . 7 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 11 65 5.1. From -10 to -11 . . . . . . . . . . . . . . . . . . . . . 11 66 5.2. From -09 to -10 . . . . . . . . . . . . . . . . . . . . . 11 67 5.3. From -08 to -09 . . . . . . . . . . . . . . . . . . . . . 11 68 5.4. From -07 to -08 . . . . . . . . . . . . . . . . . . . . . 12 69 5.5. From -06 to -07 . . . . . . . . . . . . . . . . . . . . . 12 70 5.6. From -05 to -06 . . . . . . . . . . . . . . . . . . . . . 12 71 5.7. From -04 to -05 . . . . . . . . . . . . . . . . . . . . . 12 72 5.8. From -03 to -04 . . . . . . . . . . . . . . . . . . . . . 12 73 5.9. From -02 to -03 . . . . . . . . . . . . . . . . . . . . . 12 74 5.10. From -01 to -02 . . . . . . . . . . . . . . . . . . . . . 12 75 5.11. From -00 to -01 . . . . . . . . . . . . . . . . . . . . . 12 76 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 77 6.1. Normative References . . . . . . . . . . . . . . . . . . . 13 78 6.2. Non-Normative References . . . . . . . . . . . . . . . . . 14 79 Appendix A. Where to send Comments . . . . . . . . . . . . . . . 14 80 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 14 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 82 Intellectual Property and Copyright Statements . . . . . . . . . . 16 84 1. Introduction 86 Compliant software MUST follow this specification. The capitalized 87 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in RFC 2119 [RFC2119]. 91 1.1. The Short Message Service 93 The Short Message Service (SMS) [SMS] is a rather simple service for 94 sending messages between SMS clients or, using the so-called 95 "Telematic Interworking", from an SMS client through a gateway to a 96 receiver using a different service, such as fax or email. The SMS 97 service is described in more detail in the SMS service registration 98 memo [draft-wilde-sms-service-11]. 100 1.2. Universal Resource Identifiers 102 One of the core specifications for identifying resources on the 103 Internet is RFC 3986 [RFC3986], specifying the syntax and semantics 104 of a Universal Resource Identifier (URI). The most important notion 105 of URIs are "schemes", which define a framework within which 106 resources can be uniquely identified and addressed. URIs enable 107 users to access resources, and are used for very diverse schemes such 108 as access protocols (HTTP, FTP), broadcast media (TV channels 109 [RFC2838]), messaging (email [RFC2368]), and even telephone numbers 110 (voice [RFC2806]). 112 URIs often are mentioned together with Universal Resource Names 113 (URNs) and/or Uniform Resource Locators (URLs), and it often is 114 unclear how to separate these concepts. For the purpose of this 115 memo, only the term URI will be used, referring to the most 116 fundamental concept. The World Wide Web Consortium (W3C) has issued 117 a note [uri-clarification] discussing the topic of URIs, URNs, and 118 URLs in detail. 120 1.3. SMS Messages and the Internet 122 One of the important reasons for the universal access of the Web is 123 the ability to access all information through a unique interface. 124 This kind of integration makes it easy to provide information as well 125 as to consume it. One aspect of this integration is the support of 126 user agents (in the case of the Web, commonly referred to as 127 browsers) for multiple content formats (such as HTML, GIF, JPEG) and 128 access schemes (such as HTTP, HTTP-S, FTP). 130 The "mailto" scheme has proven to be very useful and popular, because 131 most user agents support it by providing an email composition 132 facility when the user activates (e.g., clicks on) the URI. 133 Similarly, the "sms" scheme could be supported by user agents by 134 providing an SMS message composition facility when the user activates 135 the URI. In cases where the user agent does not provide a built-in 136 SMS message composition facility, the scheme could still be supported 137 by opening a Web page which provides such a service. The specific 138 Web page to be used could be configured by the user, so that each 139 user could use the SMS message composition service of his choice. 141 The goal of this memo is to specify the "sms" URI scheme, so that 142 user agents (such as Web browsers and email clients) could start to 143 support it. The "sms" URI scheme identifies SMS message endpoints as 144 resources. When "sms" URIs are dereferenced, implementations MAY 145 create a message and present it to be edited before being sent, or 146 they MAY use additional services to provide the functionality 147 necessary for composing a message and sending it to the SMS message 148 endpoint. 150 1.3.1. SMS Messages and the Web 152 SMS messages can provide an alternative to "mailto" URIs [RFC2368], 153 or "tel" or "fax" URIs [RFC2806]. When a "sms" URI is activated, the 154 user agent MAY start a program for sending an SMS message, just as 155 "mailto" may open a mail client. Unfortunately, most browsers do not 156 support the external handling of internally unsupported URI schemes 157 in the same generalized way as most of them support external handling 158 of additional MIME type content for types which they do not support 159 internally. Ideally, user agents should implement generic URI 160 parsers and provide a way to associate unsupported schemes with 161 external applications (or Web services). 163 The recipient of an SMS message need not be a mobile phone. It can 164 be a server that can process SMS messages, either by gatewaying them 165 to another messaging system (such as regular electronic mail), or by 166 parsing them for supplementary services. 168 SMS messages can be used to transport almost any kind of data (even 169 though there is a very tight size limit), but the only standardized 170 data formats are character-based messages in different character 171 encodings. SMS messages have a maximum length of 160 characters 172 (when using 7-bit characters from the SMS character set), or 140 173 octets. However, SMS messages can be concatenated to form longer 174 messages. It is up to the user agent to decide whether to limit the 175 length of the message, and how to indicate this limit in its user 176 interface, if necessary. There is one exception to this, see 177 Section 2.5. 179 1.3.2. SMS Messages and Forms 181 The Hypertext Markup Language (HTML) [HTML401] provides a way to 182 collect information from a user and pass it to a server for 183 processing. This functionality is known as "HTML forms". A 184 filled-in form is usually sent to the destination using the Hypertext 185 Transfer Protocol (HTTP) or email. However, SMS messages can also be 186 used as the transport mechanism for these forms. As SMS transport is 187 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this 188 provides a way to fill in forms offline, and send the data without 189 making a TCP connection to the server, as the set-up time, cost, and 190 overhead for a TCP connection are large compared to an SMS message. 191 Also, depending on the network configuration, the sender's telephone 192 number may be included in the SMS message, thus providing a weak form 193 of authentication. 195 2. The "sms" URI Scheme 197 Syntax definitions are given using the Augmented BNF for Syntax 198 Specifications [RFC4234]. 200 2.1. Applicability 202 This URI scheme is intended for sending an SMS message to a certain 203 recipient(s). The functionality is quite similar to that of the 204 "mailto" URI, which (as per RFC 2368 [RFC2368]) can also be used with 205 a comma-separated list of email addresses. 207 In some situations, it may be necessary to guide the sender to send 208 the SMS message via a certain SMS Center (SMSC). For this purpose, 209 the URI may specify the number of the SMSC. 211 SMS messages may be sent through gateways to other services. These 212 gateways are operated inside SMS centers. An "sms" URI may specify 213 that a certain gateway should be used. 215 The notation for phone numbers is taken from [RFC3601]. Refer to 216 this document for information on why this particular format was 217 chosen. 219 How the SMS message is sent to the SMSC is outside the scope of this 220 specification. SMS messages can be sent over the GSM air interface, 221 by using a modem and a suitable protocol, or by accessing services 222 over other protocols, such as a Web service for sending SMS messages. 223 Also, SMS message service options like deferred delivery and delivery 224 notification requests are not in the scope of this document. Such 225 services MAY be requested from the network by the user agent if 226 necessary. 228 SMS messages sent as a result of this URI MUST be sent as class 1 SMS 229 messages, if the user agent is able to specify the message class. 231 2.2. Formal Definition 233 The URI scheme's keywords specified in the following syntax 234 description are case-insensitive. The syntax of an "sms" URI is 235 formally described as follows, where the base syntax is taken from 236 RFC 3986 [RFC3986]: 238 sms-uri = scheme ":" hier-part [ "?" sms-body ] 239 scheme = "sms" 240 hier-part = sms-recipient *( "," sms-recipient ) 241 sms-recipient = gstn-phone sms-qualifier 242 sms-qualifier = *( smsc-qualifier / pid-qualifier ) 243 smsc-qualifier = ";smsc=" SMSC-sub-addr 244 pid-qualifier = ";pid=" PID-sub-addr 245 sms-body = "body=" query 247 Some illustrative examples using this syntax are given in 248 Section 2.4. 250 The syntax definition for "gstn-phone" is taken from RFC 3601 251 [RFC3601], allowing global as well as local telephone numbers. 253 The syntax definition for "query" is taken from RFC 3986 [RFC3986], 254 please refer to that document. 256 The syntax definition for "SMSC-sub-addr" and "PID-sub-addr" is 257 derived from [draft-wilde-sms-service-11], please refer to that 258 document for the syntax of the qualifier values. 260 The "sms-body" is used to define the body of the SMS message to be 261 composed. It consists of percent-encoded UTF-8 characters. 262 Implementations MUST make sure that the sms-body characters are 263 converted to a suitable character encoding before sending, the most 264 popular being the 7-bit SMS character encoding, another variant 265 (though not as universally supported as 7-bit SMS) is the UCS-2 266 character encoding (both specified in [SMS-CHAR]). Implementations 267 MAY choose to silently discard (or convert) characters in the sms- 268 body that are not supported by the SMS character set they are using 269 to send the SMS message. 271 It should be noted that both the SMSC as well as the PID qualifier 272 may appear only once per sms-recipient. If multiple SMSC or PID 273 qualifiers are present, conforming software MUST interpret the first 274 occurrence and ignore all other occurrences. 276 2.3. Parsing an "sms" URI 278 The following list describes the steps for processing an "sms" URI: 280 1. The "gstn-phone" of the first "sms-recipient" is extracted. It 281 is the phone number of the final recipient and it MUST be written 282 in international form with country code, unless the number only 283 works from inside a certain geographical area or a network. Note 284 that some numbers may work from several networks but not from the 285 whole world - these SHOULD be written in international form. 286 According to [RFC3601], all international numbers MUST begin with 287 a "+" character. Hyphens and dots are used only to improve 288 readability and MUST NOT convey any other meaning. 290 2. The "smsc-qualifier" of the first "sms-recipient" is extracted, 291 if present. 293 3. The "pid-qualifier" of the first "sms-recipient" is extracted, if 294 present. 296 4. The "sms-body" is extracted, if present. 298 5. The user agent should provide some means for message composition, 299 either by implementing this itself, or by accessing a service 300 providing it. Message composition SHOULD start with the body 301 extracted from the "sms-body", if present. If the "pid- 302 qualifier" is set to "pid=SMTP:...", then the user agents must 303 make sure that the email address is correctly set (as defined by 304 the SMS specification [SMS]) in the message being 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 311 (i.e., 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, interpretation of the phone number is left to 342 the SMSC, and is typically not used if the delivery of the email is 343 done with SMTP or some other email delivery mechanism. 345 2.5. Using "sms" URIs in HTML Forms 347 When using a "sms" type URI as an action URI for HTML form submission 348 [HTML401], the form contents MUST be packaged in the SMS message just 349 as they are packaged when using a "mailto" URI [RFC2368], using the 350 "application/x-www-form-urlencoded" MIME type, effectively packaging 351 all form data into URI compliant syntax [RFC3986]. The SMS message 352 MUST NOT contain any HTTP headers, only the form data. The MIME type 353 is implicit. It MUST NOT be transferred in the SMS message. 355 The character encoding used for form submissions MUST be UTF-8 356 [RFC2279]. It should be noted, however, that user agents MUST 357 percent-encode form submissions before sending them. 359 The user agent SHOULD inform the user about the possible security 360 hazards involved when submitting the form (it is probably being sent 361 as plain text over an air interface). 363 If the form submission is longer than the maximum SMS message size, 364 the user agent MAY either concatenate SMS messages, if it is able to 365 do so, or it MAY refuse to send the message. The user agent MUST NOT 366 send out partial form submissions. 368 Form submission via an "sms" URI can be combined with Telematic 369 Interworking to result in form submissions being submitted via an SMS 370 message and finally being sent to an email account. In this case, 371 all provisions for using the email "pid-qualifier" and using "sms" 372 URIs with HTML forms must be followed. 374 3. "sms" URIs and SMS Web Services 376 In many cases, user agents will not be able to directly compose and 377 send SMS messages (because this requires that such a service is 378 accessible to the system the user agent is running on). However, it 379 is likely that the user has access to a Web service that provides an 380 SMS service, such as a Web site offering form-based SMS composition. 381 Ideally, the user agent should access this Web service when 382 activating an "sms" URI, thus enabling the user to use the Web 383 service. 385 One problem with this approach is that the Web service should somehow 386 get the "sms" URI, in order to interpret it and set the required 387 parameters (such as the receiver's phone number). The easiest way to 388 implement this is for the user agent to add the "sms" URI as query 389 string to the Web service's URI. Consequently, user agents 390 supporting SMS Web services identified by URIs SHOULD append the 391 "sms" URI as query string to the Web services URI when accessing the 392 Web service. Web services providing SMS composition facilities 393 SHOULD expect to receive an "sms" URI as query string and should 394 process it as described by this memo. This method only can be 395 applied for Web service URIs which permit query strings (such as 396 "http" and "https" URIs). For other Web service URIs (such as "ftp" 397 and "mailto"), user agents as well as Web services MUST NOT use the 398 query string. 400 It should be noted that RFC 3986 [RFC3986] defines that within query 401 strings, the "gen-delims" characters ":", "/", "?", "#", "[", "]", 402 and "@" are reserved. It is therefore necessary to encode the "sms" 403 URI accordingly before appending it as query string. 405 3.1. Example 407 A document contains this fragment of (X)HTML: 409 Send me an SMS! 411 The user agent interpreting this document does not internally support 412 SMS message composition or sending, but has been configured to access 413 a Web service for handling "sms" URIs. This Web service has the 414 following URI: 416 http://sms.example.com/sms-form 418 When the user activates the "sms" URI (e.g., by clicking on the text 419 "Send me an SMS!"), the user agents sends a request to the SMS Web 420 service and acts as if the activated URI had been: 422 http://sms.example.com/sms-form?sms%3A+41796431851 424 The SMS Web service is then responsible for parsing the query string 425 and providing an approriate interface, for example by already filling 426 in the recipient address with the number provided by the "sms" URI. 427 This way, the non-SMS capable user agent and the SMS Web service can 428 interact to provide the best integration of Web browsing and SMS 429 sending to the user. 431 4. Security Considerations 433 The "Security Considerations" section of the SMS service registration 434 memo [draft-wilde-sms-service-11] MUST be consulted. 436 A user agent SHOULD NOT send out SMS messages without the knowledge 437 of the user, because of associated risks, which include sending 438 masses of SMS messages to a subscriber without his consent, and the 439 costs involved in sending an SMS message. 441 The user agent SHOULD have some mechanism that the user can use to 442 filter out unwanted destinations for SMS messages. The user agent 443 SHOULD also have some means of restricting the number of SMS messages 444 being sent as the result of activating one "sms" URI. 446 If an "sms" URI contains a pid-qualifier and the user agent supports 447 the qualifier and its value, then the user agent MUST set the SMS 448 message's PID as specified by the qualifier. User agents MAY inform 449 users about the value and the functional consequences of PID 450 qualifiers (e.g., by notifying users that sending the SMS effectively 451 will result in a fax message being delivered, rather than an SMS 452 message). 454 The method described in section Section 3 adds another level of 455 indirection to the handling of "sms" URIs. If this method is 456 combined with the pid-qualifier gateway functionality, SMS 457 composition and reception will probably be distributed over three 458 different protocols (the Web service, SMS transport itself, and the 459 service selected by the pid-qualifier). User agents SHOULD make this 460 clear to users (either when the Web service is being configured, or 461 when it is accessed). 463 The Telematic Interworking functionality of the SMSC addressed by the 464 pid-qualifier is not necessarily implemented by the SMSC being used, 465 and SMSC providers are known for not or not correctly supporting some 466 or all pid-qualifier values. User agents SHOULD take into account 467 that the success rate of SMS messages being sent using pid-qualifiers 468 is lower than that of "plain" SMS messages. 470 As suggested functionality, the user agent MAY offer a possibility 471 for the user to filter out those gstn-phone numbers that are 472 expressed in local format, as most premium-rate numbers are expressed 473 in local format, and because determining the correct local context 474 (and hence the validity of the number to this specific user) may be 475 very difficult. 477 When using SMS URIs as targets of forms (as described in 478 Section 2.5), the user agent SHOULD inform the user about the 479 possible security hazards involved when submitting the form (it is 480 probably being sent as plain text over an air interface). 482 5. Change Log 484 This section will not be part of the final RFC text, it serves as a 485 container to collect the history of the individual draft versions. 487 5.1. From -10 to -11 489 o RFC 2234 (ABNF) has been obsoleted by [RFC4234]. 491 o Updated reference information for [SMS] and [SMS-CHAR]. 493 o Minor textual changes. 495 5.2. From -09 to -10 497 o Added security consideration about filtering local format phone 498 numbers. 500 o Changed IPR clause from RFC 3667 to RFC 3978 (updated version of 501 RFC 3667). 503 5.3. From -08 to -09 505 o Fixed syntax error in hier-part and sms-recipient non-terminals, 506 which allowed sms-recipients to be concatenated without comma 507 separation. 509 5.4. From -07 to -08 511 o URIs are now defined by RFC 3986 [RFC3986], so the text (including 512 the syntax definitions) and the references have been updated. 514 5.5. From -06 to -07 516 o Changed IPR clause from RFC 2026 to RFC 3667 (updated version of 517 RFC 2026). 519 5.6. From -05 to -06 521 o Updated reference from draft-allocchio-gstn to RFC 3601. 523 5.7. From -04 to -05 525 o Updated reference to SMS spec to the version referenced in the SMS 526 service draft. 528 5.8. From -03 to -04 530 o Updated reference to draft-allocchio-gstn (to revision -05). 532 5.9. From -02 to -03 534 o Changed ordering of "change Log" section (descending to 535 ascending). 537 o Clarified the wording at the beginning of Section Section 2.2 538 about only the keywords of the scheme being case-insensitive. 540 o Changed "sms-body" to be a URI query string. 542 o Added some text describing "sms" URIs as addressing resources. 544 5.10. From -01 to -02 546 o Changed the sms-body field to percent-encoded UTF-8 characters. 548 5.11. From -00 to -01 550 o Added the "sms-body" field and its processing rules. 552 o Added Section Section 3 about using "sms" URIs as query strings 553 for SMS Web services. 555 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone"). 557 o Added some explanatory text about form submissions using email 558 Telematic Interworking. 560 o Added some text about character encoding in form submissions. 562 6. References 564 6.1. Normative References 566 [HTML401] Raggett, D., Le Hors, A., and I. Jacobs, "HTML 4.01 567 Specification", W3C REC-html401, December 1999, 568 . 570 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 571 Requirement Levels", RFC 2119, March 1997. 573 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 574 10646", RFC 2279, January 1998. 576 [RFC3601] Allocchio, C., "Text string notation for Dial Sequences 577 and GSTN / E.164 addresses", RFC 3601, September 2003. 579 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 580 Resource Identifier (URI): Generic Syntax", RFC 3986, 581 January 2005. 583 [RFC4234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 584 Specifications: ABNF", RFC 4234, October 2005. 586 [SMS] European Telecommunications Standards Institute, "3GPP TS 587 03.40 (Version 7.5.0 Release 1998): 3rd Generation 588 Partnership Project; Technical Specification Group 589 Terminals; Technical realization of the Short Message 590 Service (SMS)", December 2001, . 593 [SMS-CHAR] 594 European Telecommunications Standards Institute, "TS 100 595 900 (GSM 03.38 version 7.2.0 Release 1998): Digital 596 Cellular Telecommunications System (Phase 2+); Alphabets 597 and language-specific information", July 1999, . 601 [draft-wilde-sms-service-11] 602 Wilde, E., "Registration of GSTN SMS Service Qualifier", 603 draft-wilde-sms-service-11 (work in progress), Aug 2005. 605 6.2. Non-Normative References 607 [RFC2368] Hoffmann, P., Masinter, L., and J. Zawinski, "The mailto 608 URL scheme", RFC 2368, June 1998. 610 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 611 June 1999. 613 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, 614 April 2000. 616 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers 617 for Television Broadcasts", RFC 2838, May 2000. 619 [uri-clarification] 620 World Wide Web Consortium, "URIs, URLs, and URNs: 621 Clarifications and Recommendations 1.0", W3C uri- 622 clarification , September 2001, 623 . 625 Appendix A. Where to send Comments 627 Please send all comments and questions concerning this document to 628 Erik Wilde. 630 Appendix B. Acknowledgements 632 This document has been prepared using the IETF document DTD described 633 in RFC 2629 [RFC2629]. 635 Thanks to Claudio Allocchio for his comments. 637 Authors' Addresses 639 Erik Wilde 640 Swiss Federal Institute of Technology 641 ETH-Zentrum 642 8092 Zurich 643 Switzerland 645 Phone: +41-44-6325132 646 Email: erik.wilde@dret.net 647 URI: http://dret.net/netdret/ 649 Antti Vaha-Sipila 650 Nokia 652 Email: antti.vaha-sipila@nokia.com 654 Intellectual Property Statement 656 The IETF takes no position regarding the validity or scope of any 657 Intellectual Property Rights or other rights that might be claimed to 658 pertain to the implementation or use of the technology described in 659 this document or the extent to which any license under such rights 660 might or might not be available; nor does it represent that it has 661 made any independent effort to identify any such rights. Information 662 on the procedures with respect to rights in RFC documents can be 663 found in BCP 78 and BCP 79. 665 Copies of IPR disclosures made to the IETF Secretariat and any 666 assurances of licenses to be made available, or the result of an 667 attempt made to obtain a general license or permission for the use of 668 such proprietary rights by implementers or users of this 669 specification can be obtained from the IETF on-line IPR repository at 670 http://www.ietf.org/ipr. 672 The IETF invites any interested party to bring to its attention any 673 copyrights, patents or patent applications, or other proprietary 674 rights that may cover technology that may be required to implement 675 this standard. Please address the information to the IETF at 676 ietf-ipr@ietf.org. 678 Disclaimer of Validity 680 This document and the information contained herein are provided on an 681 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 682 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 683 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 684 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 685 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 686 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 688 Copyright Statement 690 Copyright (C) The Internet Society (2006). This document is subject 691 to the rights, licenses and restrictions contained in BCP 78, and 692 except as set forth therein, the authors retain all their rights. 694 Acknowledgment 696 Funding for the RFC Editor function is currently provided by the 697 Internet Society.