idnits 2.17.1 draft-wilde-sms-uri-09.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 656. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 633. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 640. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 646. ** 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 (Feb 22, 2005) is 7002 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 26, 2005 Technology 5 A. Vaha-Sipila 6 Nokia 7 Feb 22, 2005 9 URI scheme for GSM Short Message Service 10 draft-wilde-sms-uri-09 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 26, 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 -08 to -09 . . . . . . . . . . . . . . . . . . . . . 11 70 5.2 From -07 to -08 . . . . . . . . . . . . . . . . . . . . . 11 71 5.3 From -06 to -07 . . . . . . . . . . . . . . . . . . . . . 11 72 5.4 From -05 to -06 . . . . . . . . . . . . . . . . . . . . . 11 73 5.5 From -04 to -05 . . . . . . . . . . . . . . . . . . . . . 11 74 5.6 From -03 to -04 . . . . . . . . . . . . . . . . . . . . . 11 75 5.7 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . 11 76 5.8 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . 12 77 5.9 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . 12 78 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 79 6.1 Normative References . . . . . . . . . . . . . . . . . . . 12 80 6.2 Non-Normative References . . . . . . . . . . . . . . . . . 13 81 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 14 82 A. Where to send Comments . . . . . . . . . . . . . . . . . . . . 14 83 B. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 84 Intellectual Property and Copyright Statements . . . . . . . . 15 86 1. Introduction 88 Compliant software MUST follow this specification. The capitalized 89 key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in RFC 2119 [RFC2119]. 93 1.1 The Short Message Service 95 The Short Message Service (SMS) [SMS] is a rather simple service for 96 sending messages between SMS clients or, using so-called "Telematic 97 Interworking", from an SMS client through a gateway to a receiver 98 using a different service, such as fax or email. The SMS service is 99 described in more detail in the SMS service registration memo 100 [draft-wilde-sms-service-09]. 102 1.2 Universal Resource Identifiers 104 One of the core specifications for identifying resources on the 105 Internet is RFC 3986 [RFC3986], specifying the syntax and semantics 106 of a Universal Resource Identifier (URI). The most important notion 107 of URIs are "schemes", which define a framework within which 108 resources can be identified (and possibly accessed). URIs enable 109 users to identify resources, and are used for very diverse schemes 110 such as access protocols (HTTP, FTP), broadcast media (TV channels 111 [RFC2838]), messaging (email [RFC2368]), or even telephone numbers 112 (voice [RFC2806]). 114 URIs often are mentioned together with Universal Resource Names 115 (URNs) and/or Uniform Resource Locators (URLs), and it often is 116 unclear how to separate these concepts. For the purpose of this 117 memo, only the term URI will be used, referring to the most 118 fundamental concept. The World Wide Web Consortium (W3C) has issued 119 a note [uri-clarification] discussing the topic of URIs, URNs, and 120 URLs in detail. 122 1.3 SMS Messages and the Internet 124 One of the important reasons for the universal access of the Web is 125 the ability to access all information through a unique interface. 126 This kind of integration makes it easy to provide information as well 127 as to consume it. One aspect of this integration is the support of 128 user agents (in the case of the Web, commonly referred to as 129 browsers) for multiple content formats (such as HTML, GIF, JPEG) and 130 access schemes (such as HTTP, HTTP-S, FTP). 132 The "mailto" scheme has proven to be very useful and popular, because 133 most user agents support it by providing an email composition 134 facility when the user activates (eg, clicks on) the URI. 135 Accordingly, the "sms" scheme could be supported by user agents by 136 providing an SMS message composition facility when the user activates 137 the URI. Alternatively, in cases where the user agent does not 138 provide a built-in SMS message composition facility, the scheme could 139 still be supported by opening a Web page which provides such a 140 service. The specific Web page to be used could be configured by the 141 user, so that each user could use the SMS message composition service 142 of his choice. 144 The goal of this memo is to specify the "sms" URI scheme, so that 145 user agents (such as Web browsers and email clients) could start to 146 support it. The "sms" URI scheme identifies SMS message endpoints as 147 resources. When "sms" URIs are dereferenced, implementations MAY 148 create a message and present it to be edited before being sent, or 149 they MAY use additional services to provide the functionality 150 necessary for composing a message and sending it to the SMS message 151 endpoint. 153 1.3.1 SMS Messages and the Web 155 SMS messages can provide an alternative to a "mailto" URIs [RFC2368], 156 or "tel" or "fax" URIs [RFC2806]. When a "sms" URI is activated, the 157 user agent MAY start a program for sending an SMS message, just as 158 "mailto" may open a mail client. Unfortunately, most browsers do not 159 support the external handling of internally unsupported URI schemes 160 in the same generalized way as most of them support external handling 161 of additional MIME type content for types which they do not support 162 internally. Ideally, user agents should implement generic URI 163 parsers and provide a way to associate unsupported schemes with 164 external applications (or Web services). 166 The recipient of an SMS message need not be a mobile phone. It can 167 be a server that can process SMS messages, either by gatewaying them 168 to another messaging system (such as regular electronic mail), or by 169 parsing them for supplementary services. 171 SMS messages can be used to transport almost any kind of data (even 172 though there is a very tight size limit), but the only standardized 173 data formats are character-based messages in different character 174 encodings. SMS messages have a maximum length of 160 characters 175 (when using 7-bit characters from the SMS character set), or 140 176 octets. However, SMS messages can be concatenated to form longer 177 messages. It is up to the user agent to decide whether to limit the 178 length of the message, and how to indicate this limit in its user 179 interface, if necessary. There is one exception to this, see 180 Section 2.5. 182 1.3.2 SMS Messages and Forms 184 The Hypertext Markup Language (HTML) [HTML401] provides a way to 185 collect information from a user and pass it to a server for 186 processing. This functionality is known as "HTML forms". A 187 filled-in form is usually sent to the destination using the Hypertext 188 Transfer Protocol (HTTP) or email. However, SMS messages can also be 189 used as the transport mechanism for these forms. As SMS transport is 190 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this 191 provides a way to fill in forms offline, and send the data without 192 making a TCP connection to the server, as the set-up time, cost, and 193 overhead for a TCP connection are large compared to an SMS message. 194 Also, depending on the network configuration, the sender's telephone 195 number may be included in the SMS message, thus providing a weak form 196 of authentication. 198 2. The "sms" URI Scheme 200 Syntax definitions are given using the Augmented BNF for Syntax 201 Specifications [RFC2234]. 203 2.1 Applicability 205 This URI scheme is intended for sending an SMS message to a certain 206 recipient(s). The functionality is quite similar to that of the 207 "mailto" URL, which (as per RFC 2368 [RFC2368]) can also be used with 208 a comma-separated list of email addresses. 210 In some situations, it may be necessary to guide the sender to send 211 the SMS message via a certain SMSC. For this purpose, the URI may 212 specify the number of the SMSC. 214 SMS messages may be sent through gateways to other services. These 215 gateways are operated inside SMS centers. An "SMS" URI may specify 216 that a certain gateway should be used. 218 The notation for phone numbers is taken from [RFC3601]. Refer to 219 this document for information on why this particular format was 220 chosen. 222 How the SMS message is sent to the SMSC is outside the scope of this 223 specification. SMS messages can be sent over the GSM air interface, 224 by using a modem and a suitable protocol, or by accessing services 225 over other protocols, such as a Web service for sending SMS messages. 226 Also, SMS message service options like deferred delivery and delivery 227 notification requests are not in the scope of this document. Such 228 services MAY be requested from the network by the user agent if 229 necessary. 231 SMS messages sent as a result of this URI MUST be sent as class 1 SMS 232 messages, if the user agent is able to specify the message class. 234 2.2 Formal Definition 236 The URI scheme's keywords specified in the following syntax 237 description are case-insensitive. The syntax of an "sms" URI is 238 formally described as follows, where the base syntax is taken from 239 RFC 3986 [RFC3986]: 241 sms-uri = scheme ":" hier-part [ "?" sms-body ] 242 scheme = "sms" 243 hier-part = sms-recipient *( "," sms-recipient ) 244 sms-recipient = gstn-phone sms-qualifier 245 sms-qualifier = *( smsc-qualifier / pid-qualifier ) 246 smsc-qualifier = ";smsc=" SMSC-sub-addr 247 pid-qualifier = ";pid=" PID-sub-addr 248 sms-body = "body=" query 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-09], 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 268 sms-body that are not supported by the SMS character set they are 269 using 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 only to aid readability. 288 They MUST NOT have 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 302 "pid-qualifier" is set to "pid=SMTP:...", then the user agents 303 must make sure that the email address is correctly set (as 304 defined by the SMS specification [SMS]) in the message being 305 composed. 307 6. After message composition, a user agent SHOULD try to send the 308 message first using the SMSC set in the "smsc-qualifier" (if 309 present). If that fails, the user agent MAY try another SMSC. 311 7. If the URI consists of a comma-separated list of recipients (ie, 312 contains multiple "sms-recipient" parts), all of them are 313 processed in this manner. Exactly the same message SHOULD be 314 sent to all of the listed recipients. 316 2.4 Examples of Use 318 sms:+41796431851 320 This indicates an SMS message capable recipient at the given 321 telephone number. The message is sent using the user agent's default 322 SMSC. 324 sms:+41796431851;smsc=+41794999000 326 This indicates that the SMS message should be sent using the SMSC at 327 the given number. 329 sms:+41796431851,+4116321035;pid=fax 331 This URI should result in two SMS messages being sent, one to the 332 recipient number as shown in the example above, the other one being 333 sent as a fax to the second number (the fax is sent by the SMSC 334 performing the gatewaying, not by the user agent). 336 sms:+41796431851;pid=smtp:erik.wilde@dret.net?body=hello%20there 338 In this case, a message (initially being set to "hello there", which 339 may have been modified by the user before sending) will be sent via 340 SMS using the SMS to email functionality in the SMSC, so that it will 341 eventually result in an email being sent to the specified email 342 address. In this case, the phone number will not be interpreted. 344 2.5 Using "sms" URIs in HTML Forms 346 When using a "sms" type URI as an action URI for HTML form submission 347 [HTML401], the form contents MUST be packaged in the SMS message just 348 as they are packaged when using a "mailto" URL [RFC2368], using the 349 "application/x-www-form-urlencoded" MIME type, effectively packaging 350 all form data into URI compliant syntax [RFC3986]. The SMS message 351 MUST NOT contain any HTTP headers, only the form data. The MIME type 352 is implicit. It MUST NOT be transferred in the SMS message. 354 The character encoding used for form submissions MUST be UTF-8 355 [RFC2279]. It should be noted, however, that user agents MUST 356 percent-encode form submissions before sending them. 358 The user agent SHOULD inform the user about the possible security 359 hazards involved when submitting the form (it is probably being sent 360 as plain text over an air interface). 362 If the form submission is longer than the maximum SMS message size, 363 the user agent MAY either concatenate SMS messages, if it is able to 364 do so, or it MAY refuse to send the message. The user agent MUST NOT 365 send out partial form submissions. 367 Form submission via an "sms" URI can be combined with Telematic 368 Interworking to result in form submissions being submitted via an SMS 369 message and finally being sent to an email account. In this case, 370 all provisions for using the email "pid-qualifier" and using "sms" 371 URIs with HTML forms must be followed. 373 3. "sms" URIs and SMS Web Services 375 In many cases, user agents will not be able to directly compose and 376 send SMS messages (because this requires that such a service is 377 accessible to the system the user agent is running on). However, it 378 is likely that the user has access to a Web service that provides an 379 SMS service, such as a Web site offering form-based SMS composition. 380 Ideally, the user agent should access this Web service when 381 activating an "sms" URI, thus enabling the user to use the Web 382 service. 384 One problem with this approach is that the Web service should somehow 385 get the "sms" URI, in order to interpret it and set the required 386 parameters (such as the receiver's phone number). The easiest way to 387 implement this is for the user agent to add the "sms" URI as query 388 string to the Web service's URI. Consequently, user agents 389 supporting SMS Web services identified by URIs SHOULD append the 390 "sms" URI as query string to the Web services URI when accessing the 391 Web service. Web services providing SMS composition facilities 392 SHOULD expect to receive an "sms" URI as query string and should 393 process it as described by this memo. This method only can be 394 applied for Web service URIs which permit query strings (such as 395 "http" and "https" URIs). For other Web service URIs (such as "ftp" 396 and "mailto"), user agents as well as Web services MUST NOT use the 397 query string. 399 It should be noted that RFC 3986 [RFC3986] defines that within query 400 strings, the "gen-delims" characters ":", "/", "?", "#", "[", "]", 401 and "@" are reserved. It is therefore necessary to encode the "sms" 402 URI accordingly before appending it as query string. 404 3.1 Example 406 A document contains this fragment of (X)HTML: 408 Send me an SMS! 410 The user agent interpreting this document does not internally support 411 SMS message composition or sending, but has been configured to access 412 a Web service for handling "sms" URIs. This Web service has the 413 following URI: 415 http://sms.example.com/sms-form 417 When the user activates the "sms" URI (eg, by clicking on the text 418 "Send me an SMS!"), the user agents sends a request to the SMS Web 419 service and acts as if the activated URI had been: 421 http://sms.example.com/sms-form?sms%3A+41796431851 423 The SMS Web service is then responsible for parsing the query string 424 and providing an approriate interface, for example by already filling 425 in the recipient address with the number provided by the "sms" URI. 426 This way, the non-SMS capable user agent and the SMS Web service can 427 interact to provide the best integration of Web browsing and SMS 428 sending to the user. 430 4. Security Considerations 432 The "Security Considerations" section of the SMS service registration 433 memo [draft-wilde-sms-service-09] MUST be consulted. 435 A user agent SHOULD NOT send out SMS messages without the knowledge 436 of the user, because of associated risks, which include sending 437 masses of SMS messages to a subscriber without his consent, and the 438 costs involved in sending an SMS message. 440 The user agent SHOULD have some mechanism that the user can use to 441 filter out unwanted destinations for SMS messages. The user agent 442 SHOULD also have some means of restricting the number of SMS messages 443 being sent as the result of activating one "sms" URI. 445 If an "sms" URI contains a pid-qualifier and the user agent supports 446 the qualifier and its value, then the user agent MUST set the SMS 447 message's PID as specified by the qualifier. User agents MAY inform 448 users about the value and the functional consequences of PID 449 qualifiers (eg, by notifying users that sending the SMS effectively 450 will result in a fax message being delivered, rather than an SMS 451 message). 453 The method described in section Section 3 adds another level of 454 indirection to the handling of "sms" URIs. If this method is 455 combined with the pid-qualifier gateway functionality, SMS 456 composition and reception will probably be distributed over three 457 different protocols (the Web service, SMS transport itself, and the 458 service selected by the pid-qualifier). User agents SHOULD make this 459 clear to users (either when the Web service is being configured, or 460 when it is accessed). 462 The Telematic Interworking functionality of the SMSC addressed by the 463 pid-qualifier is not necessarily implemented by the SMSC being used, 464 and SMSC providers are known for not or not correctly supporting some 465 or all pid-qualifier values. User agents SHOULD take into account 466 that the success rate of SMS messages being sent using pid-qualifiers 467 is lower than that of "plain" SMS messages. 469 5. Change Log 471 This section will not be part of the final RFC text, it serves as a 472 container to collect the history of the individual draft versions. 474 5.1 From -08 to -09 476 o Fixed syntax error in hier-part and sms-recipient non-terminals, 477 which allowed sms-recipients to be concatenated without comma 478 separation. 480 5.2 From -07 to -08 482 o URIs are now defined by RFC 3986 [RFC3986], so the text (including 483 the syntax definitions) and the references have been updated. 485 5.3 From -06 to -07 487 o Changed IPR clause from RFC 2026 to RFC 3667 (updated version of 488 RFC 2026) 490 5.4 From -05 to -06 492 o Updated reference from draft-allocchio-gstn to RFC 3601. 494 5.5 From -04 to -05 496 o Updated reference to SMS spec to the version referenced in the SMS 497 service draft. 499 5.6 From -03 to -04 501 o Updated reference to draft-allocchio-gstn (to revision -05). 503 5.7 From -02 to -03 505 o Changed ordering of "change Log" section (descending to 506 ascending). 508 o Clarified the wording at the beginning of Section Section 2.2 509 about only the keywords of the scheme being case-insensitive. 511 o Changed "sms-body" to be a URI query string. 513 o Added some text describing "sms" URIs as addressing resources. 515 5.8 From -01 to -02 517 o Changed the sms-body field to percent-encoded UTF-8 characters. 519 5.9 From -00 to -01 521 o Added the "sms-body" field and its processing rules. 523 o Added Section Section 3 about using "sms" URIs as query strings 524 for SMS Web services. 526 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone"). 528 o Added some explanatory text about form submissions using email 529 Telematic Interworking. 531 o Added some text about character encoding in form submissions. 533 6. References 535 6.1 Normative References 537 [HTML401] Raggett, D., Le Hors, A. and I. Jacobs, "HTML 4.01 538 Specification", W3C REC-html401, December 1999, 539 . 541 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 542 Requirement Levels", RFC 2119, March 1997. 544 [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 545 Specifications: ABNF", RFC 2234, November 1997. 547 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 548 10646", RFC 2279, January 1998. 550 [RFC3601] Allocchio, C., "Text string notation for Dial Sequences 551 and GSTN / E.164 addresses", RFC 3601, September 2003. 553 [RFC3986] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 554 Resource Identifier (URI): Generic Syntax", RFC 3986, 555 January 2005. 557 [SMS] European Telecommunications Standards Institute, "ETSI TS 558 100 901 (GSM 03.40 version 7.3.0 Release 1998): Digital 559 Cellular Telecommunications System (Phase 2+); Technical 560 realization of the Short Message Service (SMS); 561 Point-to-Point (PP)", November 1999, 562 . 564 [SMS-CHAR] 565 European Telecommunications Standards Institute, "ETSI TS 566 100 901 (GSM 03.38 version 7.2.0 Release 1998): Digital 567 Cellular Telecommunications System (Phase 2+); Alphabets 568 and language-specific information", July 1999, 569 . 571 [draft-wilde-sms-service-09] 572 Wilde, E., "Registration of GSTN SMS Service Qualifier", 573 Internet-Draft draft-wilde-sms-service-09, Feb 2005. 575 6.2 Non-Normative References 577 [RFC2368] Hoffmann, P., Masinter, L. and J. Zawinski, "The mailto 578 URL scheme", RFC 2368, June 1998. 580 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 581 June 1999. 583 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, 584 April 2000. 586 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers 587 for Television Broadcasts", RFC 2838, May 2000. 589 [uri-clarification] 590 World Wide Web Consortium, "URIs, URLs, and URNs: 591 Clarifications and Recommendations 1.0", 592 W3C uri-clarification , September 2001, 593 . 595 Authors' Addresses 597 Erik Wilde 598 Swiss Federal Institute of Technology 599 ETH-Zentrum 600 8092 Zurich 601 Switzerland 603 Phone: +41-1-6325132 604 Email: erik.wilde@dret.net 605 URI: http://dret.net/netdret/ 607 Antti Vaha-Sipila 608 Nokia 610 Email: antti.vaha-sipila@nokia.com 612 Appendix A. Where to send Comments 614 Please send all comments and questions concerning this document to 615 Erik Wilde. 617 Appendix B. Acknowledgements 619 This document has been prepared using the IETF document DTD described 620 in RFC 2629 [RFC2629]. 622 Thanks to Claudio Allocchio for his comments. 624 Intellectual Property Statement 626 The IETF takes no position regarding the validity or scope of any 627 Intellectual Property Rights or other rights that might be claimed to 628 pertain to the implementation or use of the technology described in 629 this document or the extent to which any license under such rights 630 might or might not be available; nor does it represent that it has 631 made any independent effort to identify any such rights. Information 632 on the procedures with respect to rights in RFC documents can be 633 found in BCP 78 and BCP 79. 635 Copies of IPR disclosures made to the IETF Secretariat and any 636 assurances of licenses to be made available, or the result of an 637 attempt made to obtain a general license or permission for the use of 638 such proprietary rights by implementers or users of this 639 specification can be obtained from the IETF on-line IPR repository at 640 http://www.ietf.org/ipr. 642 The IETF invites any interested party to bring to its attention any 643 copyrights, patents or patent applications, or other proprietary 644 rights that may cover technology that may be required to implement 645 this standard. Please address the information to the IETF at 646 ietf-ipr@ietf.org. 648 Disclaimer of Validity 650 This document and the information contained herein are provided on an 651 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 652 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 653 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 654 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 655 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 656 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 658 Copyright Statement 660 Copyright (C) The Internet Society (2005). This document is subject 661 to the rights, licenses and restrictions contained in BCP 78, and 662 except as set forth therein, the authors retain all their rights. 664 Acknowledgment 666 Funding for the RFC Editor function is currently provided by the 667 Internet Society.