idnits 2.17.1 draft-shafranovich-mime-sql-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 25, 2013) is 4071 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Y. Shafranovich 3 Internet-Draft BioFortis, Inc. 4 Intended status: Informational February 25, 2013 5 Expires: August 29, 2013 7 The application/sql Media Type 8 draft-shafranovich-mime-sql-06.txt 10 Abstract 12 This document registers the application/sql media type to be used for 13 the Structured Query Language (SQL). 15 Status of this Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on August 29, 2013. 32 Copyright Notice 34 Copyright (c) 2013 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 2. Conventions Used in This Document . . . . . . . . . . . . . . . 3 51 3. Media Type Registration Application . . . . . . . . . . . . . . 3 52 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 54 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5 55 7. Normative References . . . . . . . . . . . . . . . . . . . . . 5 56 Appendix A. Status of This Document [To Be Removed Upon 57 Publication] . . . . . . . . . . . . . . . . . . . . . 6 58 A.1. Discussion Venue . . . . . . . . . . . . . . . . . . . . . 6 59 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 61 1. Introduction 63 The Structured Query Language (SQL) has been in use for over 30 years 64 with various types of database technologies. However, there is no 65 current media type registered for SQL. Therefore, this document 66 seeks to formally register the application/sql media type to be used 67 for SQL with IANA. 69 2. Conventions Used in This Document 71 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 72 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 73 document are to be interpreted as described in [RFC2119] when they 74 appear in ALL CAPS. These words may also appear in this document in 75 lower case as plain English words, absent their normative meanings. 77 3. Media Type Registration Application 79 This section provides the media type registration application for 80 this media type (see [RFC6838], Section 5.6) 82 Type name: application 84 Subtype name: sql 86 Required parameters: N/A 88 Optional parameters: 90 "charset" - indicates the character set to be used. When not 91 specified, a default value MUST NOT be assumed without inspection 92 of the content. 94 Implementators should be aware that SQL may carry character set 95 information in-band. In such cases, the "charset" parameter MUST 96 NOT be used in order to avoid conflict. In cases, where no 97 character set information is supplied in-band, and the character 98 set is known, implementors SHOULD use the "charset" parameter. If 99 no in-band or out-of-band character set information is available, 100 implementors MUST NOT specify the "charset" parameter. 102 Encoding considerations: 104 If the "charset" parameter is used, the corresponding 7-bit, 8-bit 105 or binary encoding may be used. If the "charset" parameter is not 106 used, binary encoding may be required. 108 Security considerations: 110 Being that SQL is a full fledged programming language and may 111 include embedded source code for other programming languages, 112 there is a risk of it being used to transfer malware, viruses and 113 other malicious payloads. Implementors and users are encouraged 114 only to exchange SQL files among trusted parties and utilize all 115 available security measures such as restricted access, virus 116 scanners, etc. to minimize risk. 118 Implementors should be aware that guessing character sets, 119 encodings, and possible conflicts between in-band and out-of-band 120 character set information may lead to the similar security issues 121 as described above. 123 Implementors should also be aware that SQL does not provide or 124 guarantee any sort of confidentiality and integrity checking, and 125 SQL files can expose account information or private information 126 about database structure and contents. It is therefore important 127 for applications to provide confidentiality and protection against 128 modification by malicious third parties while in transit. 130 Interoperability considerations: 132 While a single standard exists ([ISO.9075.2011]), vendor 133 implementations of the standard vary significantly. Implementors 134 and users should make sure that the exchanged SQL files match to 135 the specific database/tool and version that they are using. 137 Published specification: 139 The most recent specification of SQL is available in 140 [ISO.9075.2011]. 142 Applications that use this media type: 144 Databases and related tools 146 Fragment identifier considerations: N/A 148 Additional information: 150 Deprecated alias names for this type: N/A 152 Magic number(s): N/A 154 File extension(s): sql 155 Macintosh File Type Code(s): N/A 157 Person & email address to contact for further information: 159 Yakov Shafranovich 161 Intended usage: COMMON 163 Restrictions on usage: N/A 165 Author: IESG 167 Change controller: IESG 169 Provisional registration? (standards tree only): N/A 171 4. IANA Considerations 173 IANA is asked to register the media type application/sql in the 174 Standards tree using the application provided in Section 3 of this 175 document. 177 5. Security Considerations 179 See the Security Considerations item in the registration template in 180 Section 3, above. 182 6. Acknowledgments 184 To LTS, thanks for everything. 186 The author would also like to thank all of the folks at 187 xml.resource.org for providing many of the tools used for preparing 188 RFCs and Internet drafts. 190 A word of thanks to all IETF members that provided feedback on this 191 document. 193 7. Normative References 195 [ISO.9075.2011] 196 International Organization for Standardization, "ISO/IEC 197 9075:2011, Information Technology - Database Languages - 198 Structured Query Language (SQL)", 2011. 200 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 201 Requirement Levels", BCP 14, RFC 2119, March 1997. 203 [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type 204 Specifications and Registration Procedures", BCP 13, 205 RFC 6838, January 2013. 207 Appendix A. Status of This Document [To Be Removed Upon Publication] 209 A.1. Discussion Venue 211 Discussion about this document should be directed to IANA's media- 212 types mailing list 213 which is also 214 reachable via . Of course, comments directly 215 to the author are always welcome. 217 Author's Address 219 Yakov Shafranovich 220 BioFortis, Inc. 221 10320 Little Patuxent Parkway, Suite 410 222 Columbia, MD 21044 223 US 225 Phone: +1 443 276-2464 226 Email: ietf@shaftek.org