Skip to main content

The application/sql Media Type
draft-shafranovich-mime-sql-06

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 6922.
Author Yakov Shafranovich
Last updated 2015-10-14 (Latest revision 2013-02-26)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Formats
Reviews
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 6922 (Informational)
Action Holders
(None)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Barry Leiba
Send notices to (None)
draft-shafranovich-mime-sql-06
Network Working Group                                    Y. Shafranovich
Internet-Draft                                           BioFortis, Inc.
Intended status: Informational                         February 25, 2013
Expires: August 29, 2013

                     The application/sql Media Type
                   draft-shafranovich-mime-sql-06.txt

Abstract

   This document registers the application/sql media type to be used for
   the Structured Query Language (SQL).

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on August 29, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Shafranovich             Expires August 29, 2013                [Page 1]
Internet-Draft       The application/sql Media Type        February 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions Used in This Document . . . . . . . . . . . . . . . 3
   3.  Media Type Registration Application . . . . . . . . . . . . . . 3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5
   Appendix A.  Status of This Document [To Be Removed Upon
                Publication] . . . . . . . . . . . . . . . . . . . . . 6
     A.1.  Discussion Venue  . . . . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6

Shafranovich             Expires August 29, 2013                [Page 2]
Internet-Draft       The application/sql Media Type        February 2013

1.  Introduction

   The Structured Query Language (SQL) has been in use for over 30 years
   with various types of database technologies.  However, there is no
   current media type registered for SQL.  Therefore, this document
   seeks to formally register the application/sql media type to be used
   for SQL with IANA.

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] when they
   appear in ALL CAPS.  These words may also appear in this document in
   lower case as plain English words, absent their normative meanings.

3.  Media Type Registration Application

   This section provides the media type registration application for
   this media type (see [RFC6838], Section 5.6)

   Type name: application

   Subtype name: sql

   Required parameters: N/A

   Optional parameters:

      "charset" - indicates the character set to be used.  When not
      specified, a default value MUST NOT be assumed without inspection
      of the content.

      Implementators should be aware that SQL may carry character set
      information in-band.  In such cases, the "charset" parameter MUST
      NOT be used in order to avoid conflict.  In cases, where no
      character set information is supplied in-band, and the character
      set is known, implementors SHOULD use the "charset" parameter.  If
      no in-band or out-of-band character set information is available,
      implementors MUST NOT specify the "charset" parameter.

   Encoding considerations:

      If the "charset" parameter is used, the corresponding 7-bit, 8-bit
      or binary encoding may be used.  If the "charset" parameter is not
      used, binary encoding may be required.

Shafranovich             Expires August 29, 2013                [Page 3]
Internet-Draft       The application/sql Media Type        February 2013

   Security considerations:

      Being that SQL is a full fledged programming language and may
      include embedded source code for other programming languages,
      there is a risk of it being used to transfer malware, viruses and
      other malicious payloads.  Implementors and users are encouraged
      only to exchange SQL files among trusted parties and utilize all
      available security measures such as restricted access, virus
      scanners, etc. to minimize risk.

      Implementors should be aware that guessing character sets,
      encodings, and possible conflicts between in-band and out-of-band
      character set information may lead to the similar security issues
      as described above.

      Implementors should also be aware that SQL does not provide or
      guarantee any sort of confidentiality and integrity checking, and
      SQL files can expose account information or private information
      about database structure and contents.  It is therefore important
      for applications to provide confidentiality and protection against
      modification by malicious third parties while in transit.

   Interoperability considerations:

      While a single standard exists ([ISO.9075.2011]), vendor
      implementations of the standard vary significantly.  Implementors
      and users should make sure that the exchanged SQL files match to
      the specific database/tool and version that they are using.

   Published specification:

      The most recent specification of SQL is available in
      [ISO.9075.2011].

   Applications that use this media type:

      Databases and related tools

   Fragment identifier considerations: N/A

   Additional information:

      Deprecated alias names for this type: N/A

      Magic number(s): N/A

      File extension(s): sql

Shafranovich             Expires August 29, 2013                [Page 4]
Internet-Draft       The application/sql Media Type        February 2013

      Macintosh File Type Code(s): N/A

   Person & email address to contact for further information:

      Yakov Shafranovich <ietf@shaftek.org>

   Intended usage: COMMON

   Restrictions on usage: N/A

   Author: IESG

   Change controller: IESG

   Provisional registration? (standards tree only): N/A

4.  IANA Considerations

   IANA is asked to register the media type application/sql in the
   Standards tree using the application provided in Section 3 of this
   document.

5.  Security Considerations

   See the Security Considerations item in the registration template in
   Section 3, above.

6.  Acknowledgments

   To LTS, thanks for everything.

   The author would also like to thank all of the folks at
   xml.resource.org for providing many of the tools used for preparing
   RFCs and Internet drafts.

   A word of thanks to all IETF members that provided feedback on this
   document.

7.  Normative References

   [ISO.9075.2011]
              International Organization for Standardization, "ISO/IEC
              9075:2011, Information Technology - Database Languages -
              Structured Query Language (SQL)", 2011.

Shafranovich             Expires August 29, 2013                [Page 5]
Internet-Draft       The application/sql Media Type        February 2013

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC6838]  Freed, N., Klensin, J., and T. Hansen, "Media Type
              Specifications and Registration Procedures", BCP 13,
              RFC 6838, January 2013.

Appendix A.  Status of This Document [To Be Removed Upon Publication]

A.1.  Discussion Venue

   Discussion about this document should be directed to IANA's media-
   types mailing list
   <https://www.ietf.org/mailman/listinfo/media-types> which is also
   reachable via <media-types@iana.org>.  Of course, comments directly
   to the author are always welcome.

Author's Address

   Yakov Shafranovich
   BioFortis, Inc.
   10320 Little Patuxent Parkway, Suite 410
   Columbia, MD  21044
   US

   Phone: +1 443 276-2464
   Email: ietf@shaftek.org

Shafranovich             Expires August 29, 2013                [Page 6]