datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

The application/sql Media Type
RFC 6922

Document type: RFC - Informational (April 2013)
Was draft-shafranovich-mime-sql (individual in app area)
Document stream: IETF
Last updated: 2013-04-10
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 6922 (Informational)
Responsible AD: Barry Leiba
Send notices to: ietf@shaftek.org, draft-shafranovich-mime-sql@tools.ietf.org

Internet Engineering Task Force (IETF)                   Y. Shafranovich
Request for Comments: 6922                               BioFortis, Inc.
Category: Informational                                       April 2013
ISSN: 2070-1721

                     The application/sql Media Type

Abstract

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

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6922.

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                  Informational                     [Page 1]
RFC 6922             The application/sql Media Type           April 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  Conventions Used in This Document . . . . . . . . . . . . . . . 2
   3.  Media Type Registration Application . . . . . . . . . . . . . . 2
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5

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
   lowercase as English prose, absent of the normative meanings
   mentioned above.

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.

      Implementors 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

Shafranovich                  Informational                     [Page 2]
RFC 6922             The application/sql Media Type           April 2013

      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.

   Security considerations:

      Being that SQL is a full-fledged programming language and may

[include full document text]