idnits 2.17.1 draft-wilde-sms-uri-07.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 634. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 611. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 618. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 624. ** 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 10, 2005) is 7047 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'HTML401' ** Obsolete normative reference: RFC 2234 (Obsoleted by RFC 4234) ** Obsolete normative reference: RFC 2279 (Obsoleted by RFC 3629) ** Obsolete normative reference: RFC 2396 (Obsoleted by RFC 3986) -- Possible downref: Non-RFC (?) normative reference: ref. 'SMS' -- Possible downref: Non-RFC (?) normative reference: ref. 'SMS-CHAR' -- Obsolete informational reference (is this intentional?): RFC 2368 (Obsoleted by RFC 6068) -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) -- Obsolete informational reference (is this intentional?): RFC 2806 (Obsoleted by RFC 3966) Summary: 9 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: July 11, 2005 Technology 5 A. Vaha-Sipila 6 Nokia 7 Jan 10, 2005 9 URI scheme for GSM Short Message Service 10 draft-wilde-sms-uri-07 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 July 11, 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 . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 10 69 5.1 From -06 to -07 . . . . . . . . . . . . . . . . . . . . . 11 70 5.2 From -05 to -06 . . . . . . . . . . . . . . . . . . . . . 11 71 5.3 From -04 to -05 . . . . . . . . . . . . . . . . . . . . . 11 72 5.4 From -03 to -04 . . . . . . . . . . . . . . . . . . . . . 11 73 5.5 From -02 to -03 . . . . . . . . . . . . . . . . . . . . . 11 74 5.6 From -01 to -02 . . . . . . . . . . . . . . . . . . . . . 11 75 5.7 From -00 to -01 . . . . . . . . . . . . . . . . . . . . . 11 76 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 77 6.1 Normative References . . . . . . . . . . . . . . . . . . . . 12 78 6.2 Non-Normative References . . . . . . . . . . . . . . . . . . 13 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13 80 A. Where to send Comments . . . . . . . . . . . . . . . . . . . . 13 81 B. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 82 Intellectual Property and Copyright Statements . . . . . . . . 15 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 so-called "Telematic 95 Interworking", from an SMS client through a gateway to a receiver 96 using a different service, such as fax or email. The SMS service is 97 described in more detail in the SMS service registration memo 98 [draft-wilde-sms-service-07]. 100 1.2 Universal Resource Identifiers 102 One of the core specifications for identifying resources on the 103 Internet is RFC 2396 [RFC2396], 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 identified (and possibly accessed). URIs enable 107 users to identify resources, and are used for very diverse schemes 108 such as access protocols (HTTP, FTP), broadcast media (TV channels 109 [RFC2838]), messaging (email [RFC2368]), or 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 (eg, clicks on) the URI. 133 Accordingly, the "sms" scheme could be supported by user agents by 134 providing an SMS message composition facility when the user activates 135 the URI. Alternatively, in cases where the user agent does not 136 provide a built-in SMS message composition facility, the scheme could 137 still be supported by opening a Web page which provides such a 138 service. The specific Web page to be used could be configured by the 139 user, so that each user could use the SMS message composition service 140 of his choice. 142 The goal of this memo is to specify the "sms" URI scheme, so that 143 user agents (such as Web browsers and email clients) could start to 144 support it. The "sms" URI scheme identifies SMS message endpoints as 145 resources. When "sms" URIs are dereferenced, implementations MAY 146 create a message and present it to be edited before being sent, or 147 they MAY use additional services to provide the functionality 148 necessary for composing a message and sending it to the SMS message 149 endpoint. 151 1.3.1 SMS Messages and the Web 153 SMS messages can provide an alternative to a "mailto" URIs [RFC2368], 154 or "tel" or "fax" URIs [RFC2806]. When a "sms" URI is activated, the 155 user agent MAY start a program for sending an SMS message, just as 156 "mailto" may open a mail client. Unfortunately, most browsers do not 157 support the external handling of internally unsupported URI schemes 158 in the same generalized way as most of them support external handling 159 of additional MIME type content for types which they do not support 160 internally. Ideally, user agents should implement generic URI 161 parsers and provide a way to associate unsupported schemes with 162 external applications (or Web services). 164 The recipient of an SMS message need not be a mobile phone. It can 165 be a server that can process SMS messages, either by gatewaying them 166 to another messaging system (such as regular electronic mail), or by 167 parsing them for supplementary services. 169 SMS messages can be used to transport almost any kind of data (even 170 though there is a very tight size limit), but the only standardized 171 data formats are character-based messages in different character 172 encodings. SMS messages have a maximum length of 160 characters 173 (when using 7-bit characters from the SMS character set), or 140 174 octets. However, SMS messages can be concatenated to form longer 175 messages. It is up to the user agent to decide whether to limit the 176 length of the message, and how to indicate this limit in its user 177 interface, if necessary. There is one exception to this, see Section 178 2.5. 180 1.3.2 SMS Messages and Forms 182 The Hypertext Markup Language (HTML) [HTML401] provides a way to 183 collect information from a user and pass it to a server for 184 processing. This functionality is known as "HTML forms". A 185 filled-in form is usually sent to the destination using the Hypertext 186 Transfer Protocol (HTTP) or email. However, SMS messages can also be 187 used as the transport mechanism for these forms. As SMS transport is 188 "out-of-band" as far as normal HTTP over TCP/IP is concerned, this 189 provides a way to fill in forms offline, and send the data without 190 making a TCP connection to the server, as the set-up time, cost, and 191 overhead for a TCP connection are large compared to an SMS message. 192 Also, depending on the network configuration, the sender's telephone 193 number may be included in the SMS message, thus providing a weak form 194 of authentication. 196 2. The "sms" URI Scheme 198 Syntax definitions are given using the Augmented BNF for Syntax 199 Specifications [RFC2234]. 201 2.1 Applicability 203 This URI scheme is intended for sending an SMS message to a certain 204 recipient(s). The functionality is quite similar to that of the 205 "mailto" URL, which (as per RFC 2368 [RFC2368]) can also be used with 206 a comma-separated list of email addresses. 208 In some situations, it may be necessary to guide the sender to send 209 the SMS message via a certain SMSC. For this purpose, the URI may 210 specify the number of the SMSC. 212 SMS messages may be sent through gateways to other services. These 213 gateways are operated inside SMS centers. An "SMS" URI may specify 214 that a certain gateway should be used. 216 The notation for phone numbers is taken from [RFC3601]. Refer to 217 this document for information on why this particular format was 218 chosen. 220 How the SMS message is sent to the SMSC is outside the scope of this 221 specification. SMS messages can be sent over the GSM air interface, 222 by using a modem and a suitable protocol, or by accessing services 223 over other protocols, such as a Web service for sending SMS messages. 224 Also, SMS message service options like deferred delivery and delivery 225 notification requests are not in the scope of this document. Such 226 services MAY be requested from the network by the user agent if 227 necessary. 229 SMS messages sent as a result of this URI MUST be sent as class 1 SMS 230 messages, if the user agent is able to specify the message class. 232 2.2 Formal Definition 234 The URI scheme's keywords specified in the following syntax 235 description are case-insensitive. The syntax of an "sms" URI is 236 formally described as follows, where the base syntax is taken from 237 RFC 2396 [RFC2396]: 239 sms-uri = scheme ":" scheme-specific-part 240 scheme = "sms" 241 scheme-specific-part = 1*( sms-recipient ) [ sms-body ] 242 sms-recipient = gstn-phone sms-qualifier 243 [ "," 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=" *urlc 249 The syntax definition for "gstn-phone" is taken from [RFC3601], 250 allowing global as well as local telephone numbers. 252 The syntax definition for "SMSC-sub-addr" and "PID-sub-addr" is 253 derived from [draft-wilde-sms-service-07], please refer to that 254 document for the syntax of the qualifier values. 256 The "sms-body" is used to define the body of the SMS message to be 257 composed. It consists of URL-encoded UTF-8 characters. 258 Implementations MUST make sure that the sms-body characters are 259 converted to a suitable character encoding before sending, the most 260 popular being the 7-bit SMS character encoding, another variant 261 (though not as universally supported as 7-bit SMS) is the UCS-2 262 character encoding (both specified in [SMS-CHAR]). Implementations 263 MAY choose to silently discard (or convert) characters in the 264 sms-body that are not supported by the SMS character set they are 265 using to send the SMS message. 267 It should be noted that both the SMSC as well as the PID qualifier 268 may appear only once per sms-recipient. If multiple qualifiers are 269 present, conforming software MUST interpret the first occurrence and 270 ignore all other occurrences. 272 2.3 Parsing an "sms" URI 274 The following list describes the steps for processing an "sms" URI: 276 1. The "gstn-phone" of the first "sms-recipient" is extracted. It 277 is the phone number of the final recipient and it MUST be written 278 in international form with country code, unless the number only 279 works from inside a certain geographical area or a network. Note 280 that some numbers may work from several networks but not from the 281 whole world - these SHOULD be written in international form. 282 According to [RFC3601], all international numbers MUST begin with 283 a "+" character. Hyphens and dots are only to aid readability. 284 They MUST NOT have any other meaning. 286 2. The "smsc-qualifier" of the first "sms-recipient" is extracted, 287 if present. 289 3. The "pid-qualifier" of the first "sms-recipient" is extracted, if 290 present. 292 4. The "sms-body" is extracted, if present. 294 5. The user agent should provide some means for message composition, 295 either by implementing this itself, or by accessing a service 296 providing it. Message composition SHOULD start with the body 297 extracted from the "sms-body", if present. If the 298 "pid-qualifier" is set to "pid=SMTP:...", then the user agents 299 must make sure that the email address is correctly set (as 300 defined by the SMS specification [SMS]) in the message being 301 composed. 303 6. After message composition, a user agent SHOULD try to send the 304 message first using the SMSC set in the "smsc-qualifier" (if 305 present). If that fails, the user agent MAY try another SMSC. 307 7. If the URI consists of a comma-separated list of recipients (ie, 308 contains multiple "sms-recipient" parts), all of them are 309 processed in this manner. Exactly the same message SHOULD be 310 sent to all of the listed recipients. 312 2.4 Examples of Use 314 sms:+41796431851 316 This indicates an SMS message capable recipient at the given 317 telephone number. The message is sent using the user agent's default 318 SMSC. 320 sms:+41796431851;smsc=+41794999000 322 This indicates that the SMS message should be sent using the SMSC at 323 the given number. 325 sms:+41796431851,+4116321035;pid=fax 327 This URI should result in two SMS messages being sent, one to the 328 recipient number as shown in the example above, the other one being 329 sent as a fax to the second number (the fax is sent by the SMSC 330 performing the gatewaying, not by the user agent). 332 sms:+41796431851;pid=smtp:erik.wilde@dret.net?body=hello%20there 334 In this case, a message (initially being set to "hello there", which 335 may have been modified by the user before sending) will be sent via 336 SMS using the SMS to email functionality in the SMSC, so that it will 337 eventually result in an email being sent to the specified email 338 address. In this case, the phone number will not be interpreted. 340 2.5 Using "sms" URIs in HTML Forms 342 When using a "sms" type URI as an action URI for HTML form submission 343 [HTML401], the form contents MUST be packaged in the SMS message just 344 as they are packaged when using a "mailto" URL [RFC2368], using the 345 "application/x-www-form-urlencoded" MIME type, effectively packaging 346 all form data into URI compliant syntax [RFC2396]. The SMS message 347 MUST NOT contain any HTTP headers, only the form data. The MIME type 348 is implicit. It MUST NOT be transferred in the SMS message. 350 The character encoding used for form submissions MUST be UTF-8 351 [RFC2279]. It should be noted, however, that user agents MUST 352 URL-encode form submissions before sending them. 354 The user agent SHOULD inform the user about the possible security 355 hazards involved when submitting the form (it is probably being sent 356 as plain text over an air interface). 358 If the form submission is longer than the maximum SMS message size, 359 the user agent MAY either concatenate SMS messages, if it is able to 360 do so, or it MAY refuse to send the message. The user agent MUST NOT 361 send out partial form submissions. 363 Form submission via an "sms" URI can be combined with Telematic 364 Interworking to result in form submissions being submitted via an SMS 365 message and finally being sent to an email account. In this case, 366 all provisions for using the email "pid-qualifier" and using "sms" 367 URIs with HTML forms must be followed. 369 3. "sms" URIs and SMS Web Services 371 In many cases, user agents will not be able to directly compose and 372 send SMS messages (because this requires that such a service is 373 accessible to the system the user agent is running on). However, it 374 is likely that the user has access to a Web service that provides an 375 SMS service, such as a Web site offering form-based SMS composition. 376 Ideally, the user agent should access this Web service when 377 activating an "sms" URI, thus enabling the user to use the Web 378 service. 380 One problem with this approach is that the Web service should somehow 381 get the "sms" URI, in order interpret it and set the required 382 parameters (such as the receiver's phone number). The easiest way to 383 implement this is for the user agent to add the "sms" URI as query 384 string to the Web service's URI. Consequently, user agents 385 supporting SMS Web services identified by URIs SHOULD append the 386 "sms" URI as query string to the Web services URI when accessing the 387 Web service. Web services providing SMS composition facilities 388 SHOULD expect to receive an "sms" URI as query string and should 389 process it as described by this memo. This method only can be 390 applied for Web service URIs which permit query strings (such as 391 "http" and "https" URIs). For other Web service URIs (such as "ftp" 392 and "mailto"), user agents as well as Web services MUST NOT use the 393 query string. 395 It should be noted that RFC 2396 [RFC2396] defines that within query 396 strings, the characters ";", "/", "?", ":", "@", "&", "=", "+", ",", 397 and "$" are reserved. It is therefore necessary to encode the "sms" 398 URI accordingly before appending it as query string. 400 3.1 Example 402 A document contains this piece of (X)HTML: 404 Send me an SMS! 406 The user agent interpreting this document does not internally support 407 SMS message composition, but has been configured to access a Web 408 service for handling "sms" URIs. This Web service has the following 409 URI: 411 http://sms.example.com/sms-form 413 When the user activates the "sms" URI (eg, by clicking on the text 414 "Send me an SMS!"), the user agents acts as if the activated URI had 415 been: 417 http://sms.example.com/sms-form?sms%3A%2B41796431851 419 The Web service is then responsible for parsing the query string and 420 providing an approriate interface, for example by already filling in 421 the recipient address with the number provided in the "sms" URI. 423 4. Security Considerations 425 The "Security Considerations" section of the SMS service registration 426 memo [draft-wilde-sms-service-07] MUST be consulted. 428 A user agent SHOULD NOT send out SMS messages without the knowledge 429 of the user, because of associated risks, which include sending 430 masses of SMS messages to a subscriber without his consent, and the 431 costs involved in sending an SMS message. 433 The user agent SHOULD have some mechanism that the user can use to 434 filter out unwanted destinations for SMS messages. The user agent 435 SHOULD also have some means of restricting the number of SMS messages 436 being sent as the result of activating one "sms" URI. 438 If an "sms" URI contains a pid-qualifier and the user agent supports 439 the qualifier and its value, then the user agent MUST set the SMS 440 message's PID as specified by the qualifier. User agents MAY inform 441 users about the value and the functional consequences of PID 442 qualifiers (eg, by notifying users that sending the SMS effectively 443 will result in a fax message being delivered, rather than an SMS 444 message). 446 The method described in section Section 3 adds another level of 447 indirection to the handling of "sms" URIs. If this method is 448 combined with the pid-qualifier gateway functionality, SMS 449 composition and reception will probably be distributed over three 450 different protocols (the Web service, SMS transport itself, and the 451 service selected by the pid-qualifier). User agent SHOULD make this 452 clear to users (either when the Web service is being configured, or 453 when it is accessed). 455 The Telematic Interworking functionality of the SMSC addressed by the 456 pid-qualifier is not necessarily implemented by the SMSC being used, 457 and SMSC providers are known for not or not correctly supporting some 458 or all pid-qualifier values. User agents SHOULD take into account 459 that the success rate of SMS messages being sent using pid-qualifiers 460 is lower than that of "plain" SMS messages. 462 5. Change Log 463 5.1 From -06 to -07 465 o Changed IPR clause from RFC 2026 to RFC 3667 (updated version of 466 RFC 2026) 468 5.2 From -05 to -06 470 o Updated reference from draft-allocchio-gstn to RFC 3601. 472 5.3 From -04 to -05 474 o Updated reference to SMS spec to the version referenced in the SMS 475 service draft. 477 5.4 From -03 to -04 479 o Updated reference to draft-allocchio-gstn (to revision -05). 481 5.5 From -02 to -03 483 o Changed ordering of "change Log" section (descending to 484 ascending). 486 o Clarified the wording at the beginning of Section Section 2.2 487 about only the keywords of the scheme being case-insensitive. 489 o Changed "sms-body" to be a URI query string. 491 o Added some text describing "sms" URIs as addressing resources. 493 5.6 From -01 to -02 495 o Changed the sms-body field to URL encoded UTF-8 characters. 497 5.7 From -00 to -01 499 o Added the "sms-body" field and its processing rules. 501 o Added Section Section 3 about using "sms" URIs as query strings 502 for SMS Web services. 504 o Fixed typo in ABNF (said "global-phone" instead of "gstn-phone"). 506 o Added some explanatory text about form submissions using email 507 Telematic Interworking. 509 o Added some text about character encoding in form submissions. 511 6. References 513 6.1 Normative References 515 [HTML401] Raggett, D., Le Hors, A. and I. Jacobs, "HTML 4.01 516 Specification", W3C REC-html401, December 1999, 517 . 519 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 520 Requirement Levels", RFC 2119, March 1997. 522 [RFC2234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 523 Specifications: ABNF", RFC 2234, November 1997. 525 [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 526 10646", RFC 2279, January 1998. 528 [RFC2396] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform 529 Resource Identifiers (URI): Generic Syntax", RFC 2396, 530 August 1998. 532 [RFC3601] Allocchio, C., "Text string notation for Dial Sequences 533 and GSTN / E.164 addresses", RFC 3601, September 2003. 535 [SMS] European Telecommunications Standards Institute, "ETSI TS 536 100 901 (GSM 03.40 version 7.3.0 Release 1998): Digital 537 Cellular Telecommunications System (Phase 2+); Technical 538 realization of the Short Message Service (SMS); 539 Point-to-Point (PP)", November 1999, 540 . 542 [SMS-CHAR] 543 European Telecommunications Standards Institute, "ETSI TS 544 100 901 (GSM 03.38 version 7.2.0 Release 1998): Digital 545 Cellular Telecommunications System (Phase 2+); Alphabets 546 and language-specific information", July 1999, 547 . 549 [draft-wilde-sms-service-07] 550 Wilde, E., "Registration of GSTN SMS Service Qualifier", 551 draft-wilde-sms-service-07 (work in progress), Jul 2004. 553 6.2 Non-Normative References 555 [RFC2368] Hoffmann, P., Masinter, L. and J. Zawinski, "The mailto 556 URL scheme", RFC 2368, June 1998. 558 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 559 June 1999. 561 [RFC2806] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, 562 April 2000. 564 [RFC2838] Zigmond, D. and M. Vickers, "Uniform Resource Identifiers 565 for Television Broadcasts", RFC 2838, May 2000. 567 [uri-clarification] 568 World Wide Web Consortium, "URIs, URLs, and URNs: 569 Clarifications and Recommendations 1.0", W3C 570 uri-clarification , September 2001, 571 . 573 Authors' Addresses 575 Erik Wilde 576 Swiss Federal Institute of Technology 577 ETH-Zentrum 578 8092 Zurich 579 Switzerland 581 Phone: +41-1-6325132 582 EMail: erik.wilde@dret.net 583 URI: http://dret.net/netdret/ 585 Antti Vaha-Sipila 586 Nokia 588 EMail: antti.vaha-sipila@nokia.com 590 Appendix A. Where to send Comments 592 Please send all comments and questions concerning this document to 593 Erik Wilde. 595 Appendix B. Acknowledgements 597 This document has been prepared using the IETF document DTD described 598 in RFC 2629 [RFC2629]. 600 Thanks to Claudio Allocchio for his comments. 602 Intellectual Property Statement 604 The IETF takes no position regarding the validity or scope of any 605 Intellectual Property Rights or other rights that might be claimed to 606 pertain to the implementation or use of the technology described in 607 this document or the extent to which any license under such rights 608 might or might not be available; nor does it represent that it has 609 made any independent effort to identify any such rights. Information 610 on the procedures with respect to rights in RFC documents can be 611 found in BCP 78 and BCP 79. 613 Copies of IPR disclosures made to the IETF Secretariat and any 614 assurances of licenses to be made available, or the result of an 615 attempt made to obtain a general license or permission for the use of 616 such proprietary rights by implementers or users of this 617 specification can be obtained from the IETF on-line IPR repository at 618 http://www.ietf.org/ipr. 620 The IETF invites any interested party to bring to its attention any 621 copyrights, patents or patent applications, or other proprietary 622 rights that may cover technology that may be required to implement 623 this standard. Please address the information to the IETF at 624 ietf-ipr@ietf.org. 626 Disclaimer of Validity 628 This document and the information contained herein are provided on an 629 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 630 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 631 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 632 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 633 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 634 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 636 Copyright Statement 638 Copyright (C) The Internet Society (2005). This document is subject 639 to the rights, licenses and restrictions contained in BCP 78, and 640 except as set forth therein, the authors retain all their rights. 642 Acknowledgment 644 Funding for the RFC Editor function is currently provided by the 645 Internet Society.