[Docs] [txt|pdf] [Tracker] [Email] [Nits]

Versions: 00

Network Working Group                                           E. Wilde
Internet-Draft                                Swiss Federal Institute of
Expires: September 14, 2006                                   Technology
                                                            Mar 13, 2006


                Registration Request for SMS URI Scheme
                  draft-wilde-sms-uri-registration-00

Status of this Memo

   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.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on September 14, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This memo requests the registration of the Universal Resource
   Identifier (URI) scheme "sms" for specifying a recipient (and
   optionally a gateway) for an SMS message.  SMS messages are two-way
   paging messages that can be sent from and received by a mobile phone
   or a suitably equipped computer.






Wilde                  Expires September 14, 2006               [Page 1]

Internet-Draft               SMS URI Scheme                     Mar 2006


Table of Contents

   1.  URI Scheme Name . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Status  . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  URI Scheme Syntax . . . . . . . . . . . . . . . . . . . . . . . 3
   4.  URI Scheme Semantics  . . . . . . . . . . . . . . . . . . . . . 3
   5.  Encoding Considerations . . . . . . . . . . . . . . . . . . . . 3
   6.  Applications/Protocols that use this URI Scheme Name  . . . . . 3
   7.  Interoperability Considerations . . . . . . . . . . . . . . . . 3
   8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   9.  Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   10. Author/Change Controller  . . . . . . . . . . . . . . . . . . . 4
   11. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
     12.1.  Normative References . . . . . . . . . . . . . . . . . . . 4
     12.2.  Non-Normative References . . . . . . . . . . . . . . . . . 5
   Appendix A.  Where to send Comments . . . . . . . . . . . . . . . . 5
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . . . 5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6
   Intellectual Property and Copyright Statements  . . . . . . . . . . 7































Wilde                  Expires September 14, 2006               [Page 2]

Internet-Draft               SMS URI Scheme                     Mar 2006


1.  URI Scheme Name

   sms


2.  Status

   Provisional


3.  URI Scheme Syntax

   See [draft-wilde-sms-uri-12].


4.  URI Scheme Semantics

   The "sms" URI scheme defines a URI scheme which does not directly
   address a resource.  Thus, the usual operations that may be performed
   on resources do not apply.  Instead, the "sms" defines a way how a
   message may be composed which is then transmitted using the SMS
   message transmission method.  This scheme can thus be compared to be
   "mailto" URI scheme [RFC2368].  See [draft-wilde-sms-uri-12] for the
   details of operation.


5.  Encoding Considerations

   The optional body field of "sms" URIs may contain a message text, but
   this text uses percent-encoded UTF-8 characters and thus can always
   be represented using URI characters.  See [draft-wilde-sms-uri-12]
   for the details of encoding.


6.  Applications/Protocols that use this URI Scheme Name

   The "sms" URI scheme is intended to be used in a similar way as the
   "mailto" URI scheme [RFC2368].  By using "sms" URIs, authors can
   embed information into documents which can be used as a starting
   point for initiating message composition.  Whether the client is
   sending the message itself (for example over a GSM air interface) or
   redirecting the user to a third party for message composition (such
   as a Web service for sending SMS messages) is outside of the scope of
   the URI scheme definition.


7.  Interoperability Considerations




Wilde                  Expires September 14, 2006               [Page 3]

Internet-Draft               SMS URI Scheme                     Mar 2006


   No interoperability issues have been identified.


8.  Security Considerations

   See [draft-wilde-sms-uri-12].


9.  Contact

   Erik Wilde
   Swiss Federal Institute of Technology
   ETH-Zentrum
   8092 Zurich
   Switzerland
   tel:+41-44-6325132
   fax:+41-44-6321035
   mailto:erik.wilde@dret.net


10.  Author/Change Controller

   Erik Wilde
   Swiss Federal Institute of Technology
   ETH-Zentrum
   8092 Zurich
   Switzerland
   tel:+41-44-6325132
   fax:+41-44-6321035
   mailto:erik.wilde@dret.net


11.  Change Log

   This section will not be part of the final RFC text, it serves as a
   container to collect the history of the individual draft versions.


12.  References

12.1.  Normative References

   [RFC4395]  Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
              Registration Procedures for New URI Schemes", RFC 4395,
              February 2006.

   [draft-wilde-sms-uri-12]
              Wilde, E. and A. Vaha-Sipila, "URI Scheme for GSM Short



Wilde                  Expires September 14, 2006               [Page 4]

Internet-Draft               SMS URI Scheme                     Mar 2006


              Message Service", draft-wilde-sms-service-12 (work in
              progress), March 2006.

12.2.  Non-Normative References

   [RFC2368]  Hoffmann, P., Masinter, L., and J. Zawinski, "The mailto
              URL scheme", RFC 2368, June 1998.

   [RFC2629]  Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
              June 1999.


Appendix A.  Where to send Comments

   Please send all comments and questions concerning this document to
   Erik Wilde.


Appendix B.  Acknowledgements

   This document has been prepared using the IETF document DTD described
   in RFC 2629 [RFC2629].

   Thanks to Bennett Marks for his help and comments.



























Wilde                  Expires September 14, 2006               [Page 5]

Internet-Draft               SMS URI Scheme                     Mar 2006


Author's Address

   Erik Wilde
   Swiss Federal Institute of Technology
   ETH-Zentrum
   8092 Zurich
   Switzerland

   Phone: +41-44-6325132
   Email: erik.wilde@dret.net
   URI:   http://dret.net/netdret/








































Wilde                  Expires September 14, 2006               [Page 6]

Internet-Draft               SMS URI Scheme                     Mar 2006


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Wilde                  Expires September 14, 2006               [Page 7]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/