1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<pre>Internet Engineering Task Force (IETF) Y. Shafranovich
Request for Comments: 6922 BioFortis, Inc.
Category: Informational April 2013
ISSN: 2070-1721
<span class="h1">The application/sql Media Type</span>
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6922">http://www.rfc-editor.org/info/rfc6922</a>.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Shafranovich Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6922">RFC 6922</a> The application/sql Media Type April 2013</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. Conventions Used in This Document . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-3">3</a>. Media Type Registration Application . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-7">7</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] 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.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Media Type Registration Application</span>
This section provides the media type registration application for
this media type (see <a href="./rfc6838#section-5.6">[RFC6838], Section 5.6</a>)
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
<span class="grey">Shafranovich Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6922">RFC 6922</a> The application/sql Media Type April 2013</span>
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 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 ([<a href="#ref-ISO.9075.2011" title=""ISO/IEC 9075:2011, Information Technology - Database Languages - Structured Query Language (SQL)"">ISO.9075.2011</a>]), 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
[<a href="#ref-ISO.9075.2011" title=""ISO/IEC 9075:2011, Information Technology - Database Languages - Structured Query Language (SQL)"">ISO.9075.2011</a>].
Applications that use this media type:
Databases and related tools
<span class="grey">Shafranovich Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6922">RFC 6922</a> The application/sql Media Type April 2013</span>
Fragment identifier considerations: N/A
Additional information:
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): sql
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
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
IANA has registered "application/sql" in the standards tree of the
"Application Media Types" registry, using the application provided in
<a href="#section-3">Section 3</a> of this document.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
See the Security Considerations item in the registration template in
<a href="#section-3">Section 3</a>, above.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgments</span>
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 who provided feedback on this
document.
<span class="grey">Shafranovich Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6922">RFC 6922</a> The application/sql Media Type April 2013</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Normative References</span>
[<a id="ref-ISO.9075.2011">ISO.9075.2011</a>] International Organization for Standardization,
"ISO/IEC 9075:2011, Information Technology -
Database Languages - Structured Query Language
(SQL)", 2011.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC6838">RFC6838</a>] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>,
<a href="./rfc6838">RFC 6838</a>, January 2013.
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 Informational [Page 5]
</pre>
|
