idnits 2.17.1 draft-wilde-sms-uri-registration-00.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 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 219. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 196. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 203. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 209. ** 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 Introduction section. ** 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 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 (Mar 13, 2006) is 6609 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) == Unused Reference: 'RFC4395' is defined on line 146, but no explicit reference was found in the text ** Obsolete normative reference: RFC 4395 (Obsoleted by RFC 7595) -- Obsolete informational reference (is this intentional?): RFC 2368 (Obsoleted by RFC 6068) -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 6 errors (**), 0 flaws (~~), 3 warnings (==), 9 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: September 14, 2006 Technology 5 Mar 13, 2006 7 Registration Request for SMS URI Scheme 8 draft-wilde-sms-uri-registration-00 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on September 14, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2006). 39 Abstract 41 This memo requests the registration of the Universal Resource 42 Identifier (URI) scheme "sms" for specifying a recipient (and 43 optionally a gateway) for an SMS message. SMS messages are two-way 44 paging messages that can be sent from and received by a mobile phone 45 or a suitably equipped computer. 47 Table of Contents 49 1. URI Scheme Name . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 3. URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. URI Scheme Semantics . . . . . . . . . . . . . . . . . . . . . 3 53 5. Encoding Considerations . . . . . . . . . . . . . . . . . . . . 3 54 6. Applications/Protocols that use this URI Scheme Name . . . . . 3 55 7. Interoperability Considerations . . . . . . . . . . . . . . . . 3 56 8. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 57 9. Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 10. Author/Change Controller . . . . . . . . . . . . . . . . . . . 4 59 11. Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 12.1. Normative References . . . . . . . . . . . . . . . . . . . 4 62 12.2. Non-Normative References . . . . . . . . . . . . . . . . . 5 63 Appendix A. Where to send Comments . . . . . . . . . . . . . . . . 5 64 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . . 5 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 Intellectual Property and Copyright Statements . . . . . . . . . . 7 68 1. URI Scheme Name 70 sms 72 2. Status 74 Provisional 76 3. URI Scheme Syntax 78 See [draft-wilde-sms-uri-12]. 80 4. URI Scheme Semantics 82 The "sms" URI scheme defines a URI scheme which does not directly 83 address a resource. Thus, the usual operations that may be performed 84 on resources do not apply. Instead, the "sms" defines a way how a 85 message may be composed which is then transmitted using the SMS 86 message transmission method. This scheme can thus be compared to be 87 "mailto" URI scheme [RFC2368]. See [draft-wilde-sms-uri-12] for the 88 details of operation. 90 5. Encoding Considerations 92 The optional body field of "sms" URIs may contain a message text, but 93 this text uses percent-encoded UTF-8 characters and thus can always 94 be represented using URI characters. See [draft-wilde-sms-uri-12] 95 for the details of encoding. 97 6. Applications/Protocols that use this URI Scheme Name 99 The "sms" URI scheme is intended to be used in a similar way as the 100 "mailto" URI scheme [RFC2368]. By using "sms" URIs, authors can 101 embed information into documents which can be used as a starting 102 point for initiating message composition. Whether the client is 103 sending the message itself (for example over a GSM air interface) or 104 redirecting the user to a third party for message composition (such 105 as a Web service for sending SMS messages) is outside of the scope of 106 the URI scheme definition. 108 7. Interoperability Considerations 109 No interoperability issues have been identified. 111 8. Security Considerations 113 See [draft-wilde-sms-uri-12]. 115 9. Contact 117 Erik Wilde 118 Swiss Federal Institute of Technology 119 ETH-Zentrum 120 8092 Zurich 121 Switzerland 122 tel:+41-44-6325132 123 fax:+41-44-6321035 124 mailto:erik.wilde@dret.net 126 10. Author/Change Controller 128 Erik Wilde 129 Swiss Federal Institute of Technology 130 ETH-Zentrum 131 8092 Zurich 132 Switzerland 133 tel:+41-44-6325132 134 fax:+41-44-6321035 135 mailto:erik.wilde@dret.net 137 11. Change Log 139 This section will not be part of the final RFC text, it serves as a 140 container to collect the history of the individual draft versions. 142 12. References 144 12.1. Normative References 146 [RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and 147 Registration Procedures for New URI Schemes", RFC 4395, 148 February 2006. 150 [draft-wilde-sms-uri-12] 151 Wilde, E. and A. Vaha-Sipila, "URI Scheme for GSM Short 152 Message Service", draft-wilde-sms-service-12 (work in 153 progress), March 2006. 155 12.2. Non-Normative References 157 [RFC2368] Hoffmann, P., Masinter, L., and J. Zawinski, "The mailto 158 URL scheme", RFC 2368, June 1998. 160 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 161 June 1999. 163 Appendix A. Where to send Comments 165 Please send all comments and questions concerning this document to 166 Erik Wilde. 168 Appendix B. Acknowledgements 170 This document has been prepared using the IETF document DTD described 171 in RFC 2629 [RFC2629]. 173 Thanks to Bennett Marks for his help and comments. 175 Author's Address 177 Erik Wilde 178 Swiss Federal Institute of Technology 179 ETH-Zentrum 180 8092 Zurich 181 Switzerland 183 Phone: +41-44-6325132 184 Email: erik.wilde@dret.net 185 URI: http://dret.net/netdret/ 187 Intellectual Property Statement 189 The IETF takes no position regarding the validity or scope of any 190 Intellectual Property Rights or other rights that might be claimed to 191 pertain to the implementation or use of the technology described in 192 this document or the extent to which any license under such rights 193 might or might not be available; nor does it represent that it has 194 made any independent effort to identify any such rights. Information 195 on the procedures with respect to rights in RFC documents can be 196 found in BCP 78 and BCP 79. 198 Copies of IPR disclosures made to the IETF Secretariat and any 199 assurances of licenses to be made available, or the result of an 200 attempt made to obtain a general license or permission for the use of 201 such proprietary rights by implementers or users of this 202 specification can be obtained from the IETF on-line IPR repository at 203 http://www.ietf.org/ipr. 205 The IETF invites any interested party to bring to its attention any 206 copyrights, patents or patent applications, or other proprietary 207 rights that may cover technology that may be required to implement 208 this standard. Please address the information to the IETF at 209 ietf-ipr@ietf.org. 211 Disclaimer of Validity 213 This document and the information contained herein are provided on an 214 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 215 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 216 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 217 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 218 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 219 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 221 Copyright Statement 223 Copyright (C) The Internet Society (2006). This document is subject 224 to the rights, licenses and restrictions contained in BCP 78, and 225 except as set forth therein, the authors retain all their rights. 227 Acknowledgment 229 Funding for the RFC Editor function is currently provided by the 230 Internet Society.