| 1 |
<pre>Internet Engineering Task Force (IETF) M. Hardy |
| 2 |
Request for Comments: 8118 L. Masinter |
| 3 |
Obsoletes: <a href="./rfc3778">3778</a> D. Markovic |
| 4 |
Category: Informational Adobe Systems Incorporated |
| 5 |
ISSN: 2070-1721 D. Johnson |
| 6 |
PDF Association |
| 7 |
M. Bailey |
| 8 |
Global Graphics |
| 9 |
March 2017 |
| 10 |
|
| 11 |
|
| 12 |
<span class="h1">The application/pdf Media Type</span> |
| 13 |
|
| 14 |
Abstract |
| 15 |
|
| 16 |
The Portable Document Format (PDF) is an ISO standard (ISO |
| 17 |
32000-1:2008) defining a final-form document representation language |
| 18 |
in use for document exchange, including on the Internet, since 1993. |
| 19 |
This document provides an overview of the PDF format and updates the |
| 20 |
media type registration of "application/pdf". It obsoletes <a href="./rfc3778">RFC 3778</a>. |
| 21 |
|
| 22 |
Status of This Memo |
| 23 |
|
| 24 |
This document is not an Internet Standards Track specification; it is |
| 25 |
published for informational purposes. |
| 26 |
|
| 27 |
This document is a product of the Internet Engineering Task Force |
| 28 |
(IETF). It represents the consensus of the IETF community. It has |
| 29 |
received public review and has been approved for publication by the |
| 30 |
Internet Engineering Steering Group (IESG). Not all documents |
| 31 |
approved by the IESG are a candidate for any level of Internet |
| 32 |
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 33 |
|
| 34 |
Information about the current status of this document, any errata, |
| 35 |
and how to provide feedback on it may be obtained at |
| 36 |
<a href="http://www.rfc-editor.org/info/rfc8118">http://www.rfc-editor.org/info/rfc8118</a>. |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Hardy, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2017 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
Table of Contents |
| 73 |
|
| 74 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 75 |
<a href="#section-2">2</a>. History .........................................................<a href="#page-3">3</a> |
| 76 |
<a href="#section-3">3</a>. Fragment Identifiers ............................................<a href="#page-3">3</a> |
| 77 |
<a href="#section-4">4</a>. Subset Standards ................................................<a href="#page-5">5</a> |
| 78 |
<a href="#section-5">5</a>. PDF Versions ....................................................<a href="#page-6">6</a> |
| 79 |
<a href="#section-6">6</a>. PDF Implementations .............................................<a href="#page-7">7</a> |
| 80 |
<a href="#section-7">7</a>. Security Considerations .........................................<a href="#page-7">7</a> |
| 81 |
<a href="#section-8">8</a>. IANA Considerations .............................................<a href="#page-8">8</a> |
| 82 |
<a href="#section-9">9</a>. References ......................................................<a href="#page-9">9</a> |
| 83 |
<a href="#section-9.1">9.1</a>. Normative References .......................................<a href="#page-9">9</a> |
| 84 |
<a href="#section-9.2">9.2</a>. Informative References .....................................<a href="#page-9">9</a> |
| 85 |
<a href="#appendix-A">Appendix A</a>. Changes since <a href="./rfc3778">RFC 3778</a> ................................<a href="#page-11">11</a> |
| 86 |
Authors' Addresses ................................................<a href="#page-12">12</a> |
| 87 |
|
| 88 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 89 |
|
| 90 |
This document is intended to provide updated information on the |
| 91 |
registration of the MIME Media Type "application/pdf" for documents |
| 92 |
in the PDF (Portable Document Format) syntax. It obsoletes |
| 93 |
[<a href="./rfc3778" title=""The application/pdf Media Type"">RFC3778</a>]. |
| 94 |
|
| 95 |
PDF was originally envisioned as a way to reliably communicate and |
| 96 |
view printed information electronically across a wide variety of |
| 97 |
machine configurations, operating systems, and communication |
| 98 |
networks. |
| 99 |
|
| 100 |
PDF is used to represent "final form" formatted documents. PDF pages |
| 101 |
may include text, images, graphics, and multimedia content such as |
| 102 |
video and audio. PDF is also capable of containing auxiliary |
| 103 |
structures, including annotations, bookmarks, file attachments, |
| 104 |
hyperlinks, logical structures, and metadata. These features are |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Hardy, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 111 |
|
| 112 |
|
| 113 |
useful for navigation and building collections of related documents, |
| 114 |
as well as for reviewing and commenting on documents. A rich |
| 115 |
JavaScript model has been defined for interacting with PDF documents. |
| 116 |
|
| 117 |
The imaging model for PDF was originally based on the PostScript [<a href="#ref-PS" title=""PostScript Language Reference, third edition"">PS</a>] |
| 118 |
page description language, used to render complex text, images, and |
| 119 |
graphics in a device-independent and resolution-independent manner. |
| 120 |
|
| 121 |
PDF supports encryption and digital signatures. The encryption |
| 122 |
capability is combined with access control information to facilitate |
| 123 |
management of the functionality available to the recipient. PDF |
| 124 |
supports the inclusion of document and object-level metadata through |
| 125 |
the eXtensible Metadata Platform [<a href="#ref-XMP" title=""Graphic technology -- Extensible metadata platform (XMP) specification -- Part 1: Data model, serialization and core properties"">XMP</a>]. |
| 126 |
|
| 127 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. History</span> |
| 128 |
|
| 129 |
PDF is used widely in the Internet community. The first version of |
| 130 |
PDF, 1.0, was published in 1993 by Adobe Systems Incorporated. Since |
| 131 |
then, PDF has grown to be a widely used format for capturing and |
| 132 |
exchanging formatted documents electronically across the Web, via |
| 133 |
email and virtually every other document-exchange mechanism. In |
| 134 |
2008, PDF 1.7 was adopted as an ISO standard (ISO 32000-1:2008 |
| 135 |
[<a href="#ref-ISOPDF" title=""Document management -- Portable document format -- Part 1: PDF 1.7"">ISOPDF</a>]) using the ISO "Fast-Track" process. That specification is |
| 136 |
technically identical to Adobe Portable Document Format version 1.7 |
| 137 |
[<a href="#ref-AdobePDF" title=""PDF Reference, sixth edition"">AdobePDF</a>]. |
| 138 |
|
| 139 |
The ISO TC-171 committee developed a "refresh" of PDF, known as |
| 140 |
ISO 32000-2; the version is PDF 2.0 [<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>]. |
| 141 |
|
| 142 |
In addition to ISO 32000-1:2008 and ISO 32000-2, several subset |
| 143 |
standards have been defined to address specific use cases and |
| 144 |
standardized by the ISO. These standards include PDF for Archival |
| 145 |
(PDF/A) [<a href="#ref-ISOPDFA" title=""Document management -- Electronic document file format for long-term preservation -- Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)"">ISOPDFA</a>], PDF for Engineering (PDF/E) [<a href="#ref-ISOPDFE" title=""Document management -- Engineering document format using PDF -- Part 1: Use of PDF 1.6 (PDF/E-1)"">ISOPDFE</a>], PDF for |
| 146 |
Universal Accessibility (PDF/UA) [<a href="#ref-ISOPDFUA" title=""Document management applications -- Electronic document file format enhancement for accessibility -- Part 1: Use of ISO 32000-1 (PDF/UA-1)"">ISOPDFUA</a>], PDF for Variable Data |
| 147 |
and Transactional Printing (PDF/VT) [<a href="#ref-ISOPDFVT" title=""Graphic technology -- Variable data exchange -- Part 2: Using PDF/X-4 and PDF/X-5 (PDF/VT-1 and PDF/VT-2)"">ISOPDFVT</a>], and PDF for Prepress |
| 148 |
Digital Data Exchange (PDF/X) [<a href="#ref-ISOPDFX" title=""Graphic technology -- Prepress digital data exchange using PDF -- Part 8: Partial exchange of printing data using PDF 1.6 (PDF/X-5)"">ISOPDFX</a>]. The subset standards are |
| 149 |
fully compliant PDF files capable of being displayed in a general PDF |
| 150 |
viewer. |
| 151 |
|
| 152 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Fragment Identifiers</span> |
| 153 |
|
| 154 |
Fragment identifiers appear at the end of a URI and provide a way to |
| 155 |
reference an anchor to subordinate content within the target of the |
| 156 |
URI, or additional parameters to the process of opening the |
| 157 |
identified content. The syntax and semantics of fragment identifiers |
| 158 |
are referenced in the media type definition. |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Hardy, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 167 |
|
| 168 |
|
| 169 |
The specification of fragment identifiers for PDF appeared originally |
| 170 |
in [<a href="./rfc3778" title=""The application/pdf Media Type"">RFC3778</a>] and is now included in ISO 32000-2 [<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>]. This |
| 171 |
section is a summary of that material. Any disagreements between |
| 172 |
[<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] and this document should be resolved in favor of the |
| 173 |
ISO 32000-2 definition. |
| 174 |
|
| 175 |
A fragment identifier for PDF has one or more parameters, separated |
| 176 |
by the ampersand (&) or pound (#) character. Each parameter consists |
| 177 |
of the parameter name, "=" (equal), and the parameter value; lists of |
| 178 |
values are comma-separated, and parameter value strings may be |
| 179 |
URI-encoded [<a href="./rfc3986" title=""Uniform Resource Identifier (URI): Generic Syntax"">RFC3986</a>]. Parameters are processed left to right. |
| 180 |
|
| 181 |
Coordinate values (such as <left>, <right>, and <width>) are |
| 182 |
expressed in the default user space coordinate system of the |
| 183 |
document: 1/72 of an inch measured down and to the right from the |
| 184 |
upper left corner of the (current) page ([<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] 8.3.2.3 |
| 185 |
"User Space"). |
| 186 |
|
| 187 |
The following parameters identify subordinate content of a PDF file |
| 188 |
but also may be used to set the document view to make the (start of) |
| 189 |
the identified content visible: |
| 190 |
|
| 191 |
page=<pageNum> |
| 192 |
Identifies a specified (physical) page; the first page in the |
| 193 |
document has a pageNum value of 1. |
| 194 |
|
| 195 |
nameddest=<name> |
| 196 |
Identifies a named destination ([<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] 12.3.2.4 "Named |
| 197 |
destinations"). |
| 198 |
|
| 199 |
structelem=<structID> |
| 200 |
A byte string with URI encoding; identifies the structure element |
| 201 |
with the ID key within a StructElem dictionary of the document. |
| 202 |
|
| 203 |
comment=<commentID> |
| 204 |
The value of an annotation name, which is defined by the NM key in |
| 205 |
the corresponding annotation dictionary of the selected page |
| 206 |
([<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] 12.5.2 "Annotation dictionaries"). |
| 207 |
|
| 208 |
ef=<name> |
| 209 |
Identifies the embedded file where the parameter string <name> |
| 210 |
matches a file specification dictionary in the EmbeddedFiles name |
| 211 |
tree. If the "ef" parameter is not at the end of the fragment |
| 212 |
identifier, then the rest of the fragment identifier (after the |
| 213 |
ampersand or hash delimiter) is applied to the embedded file |
| 214 |
according to its own media type. This allows identification of |
| 215 |
content within the embedded file (which itself might be a |
| 216 |
PDF file). |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Hardy, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 223 |
|
| 224 |
|
| 225 |
NOTE: When attempting to open a PDF file that is not from a |
| 226 |
trusted source, the processor may choose to prompt the user or |
| 227 |
even prevent the file from being opened. |
| 228 |
|
| 229 |
These parameters operate on the view of the PDF document when it is |
| 230 |
opened: |
| 231 |
|
| 232 |
zoom=<scale>,<left>,<top> |
| 233 |
<scale> is the percentage to which the document should be zoomed, |
| 234 |
where a value of 100 corresponds to a zoom of 100%. <left> and |
| 235 |
<top> are optional, but both must be specified if either is |
| 236 |
included. |
| 237 |
|
| 238 |
view=<keyword>,<position> |
| 239 |
The arguments correspond to those found in [<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] 12.3.2.2 |
| 240 |
"Explicit destinations". <keyword> is one of the keywords defined |
| 241 |
in [<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] "Table 149: Destination syntax" with appropriate |
| 242 |
position values. |
| 243 |
|
| 244 |
viewrect=<left>,<top>,<width>,<height> |
| 245 |
Set the view rectangle. |
| 246 |
|
| 247 |
highlight=<left>,<right>,<top>,<bottom> |
| 248 |
Highlight the specified rectangle. |
| 249 |
|
| 250 |
search=<wordList> |
| 251 |
Open the document and search for one or more words, selecting the |
| 252 |
first matching word in the document. <wordList> is a string |
| 253 |
enclosed in quotation marks, where individual words are separated |
| 254 |
by the space character (or %20). |
| 255 |
|
| 256 |
fdf=<URI> |
| 257 |
This parameter imports data into PDF form fields. The URI is |
| 258 |
either a relative or absolute URI to a Forms Data Format (FDF) or |
| 259 |
XML FDF (XFDF) file. The fdf parameter should be specified as the |
| 260 |
last parameter to a given URI. |
| 261 |
|
| 262 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Subset Standards</span> |
| 263 |
|
| 264 |
Several subsets of PDF have been published as distinct ISO standards: |
| 265 |
|
| 266 |
o PDF/X [<a href="#ref-ISOPDFX" title=""Graphic technology -- Prepress digital data exchange using PDF -- Part 8: Partial exchange of printing data using PDF 1.6 (PDF/X-5)"">ISOPDFX</a>], initially released in 2001 as PDF/X-1a, specifies |
| 267 |
how to use PDF for graphics exchange, with the aim to facilitate |
| 268 |
correct and predictable printing by print service providers. The |
| 269 |
standard has gone through multiple revisions over the years and |
| 270 |
has several published parts, the most recently released being |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Hardy, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 279 |
|
| 280 |
|
| 281 |
part 8, specifying different levels of conformance: PDF/X-1a:2001, |
| 282 |
PDF/X-3:2002, PDF/X-1a:2003, PDF/X-3:2003, PDF/X-4, PDF/X-4p, |
| 283 |
PDF/X-5g, PDF/X-5pg, and PDF/X-5n. |
| 284 |
|
| 285 |
o PDF/A [<a href="#ref-ISOPDFA" title=""Document management -- Electronic document file format for long-term preservation -- Part 3: Use of ISO 32000-1 with support for embedded files (PDF/A-3)"">ISOPDFA</a>], initially released in 2005, specifies how to use |
| 286 |
PDF for long-term preservation (archiving) of electronic |
| 287 |
documents. It prohibits PDF features that are not well suited to |
| 288 |
long-term archiving of documents, including JavaScript or |
| 289 |
executable file launches. Its requirements for PDF/A viewers |
| 290 |
include color management guidelines and support for embedded |
| 291 |
fonts. There are three parts of this standard and a total of |
| 292 |
eight conformance levels: PDF/A-1a, PDF/A-1b, PDF/A-2a, PDF/A-2b, |
| 293 |
PDF/A-2u, PDF/A-3a, PDF/A-3b, and PDF/A-3u. |
| 294 |
|
| 295 |
o PDF/E, initially released in 2008 as PDF/E-1 [<a href="#ref-ISOPDFE" title=""Document management -- Engineering document format using PDF -- Part 1: Use of PDF 1.6 (PDF/E-1)"">ISOPDFE</a>], specifies |
| 296 |
how to use PDF in engineering workflows, such as manufacturing, |
| 297 |
construction, and geospatial analysis. Future revisions of PDF/E |
| 298 |
are supposed to include support for 3D PDF workflows. |
| 299 |
|
| 300 |
o PDF/VT, initially released in 2010, specifies how to use PDF in |
| 301 |
variable and transactional printing. It is based on PDF/X and |
| 302 |
places additional restrictions on PDF content elements and |
| 303 |
supporting metadata. It specifies three conformance levels: |
| 304 |
PDF/VT-1, PDF/VT-2, and PDF/VT-2s [<a href="#ref-ISOPDFVT" title=""Graphic technology -- Variable data exchange -- Part 2: Using PDF/X-4 and PDF/X-5 (PDF/VT-1 and PDF/VT-2)"">ISOPDFVT</a>]. |
| 305 |
|
| 306 |
o PDF/UA [<a href="#ref-ISOPDFUA" title=""Document management applications -- Electronic document file format enhancement for accessibility -- Part 1: Use of ISO 32000-1 (PDF/UA-1)"">ISOPDFUA</a>], initially released in 2012 as PDF/UA-1, |
| 307 |
specifies how to create accessible electronic documents. It |
| 308 |
requires the use of ISO 32000's Tagged PDF feature and adds many |
| 309 |
requirements regarding semantic correctness in applying logical |
| 310 |
structures to content in PDF documents. |
| 311 |
|
| 312 |
All of these subset standards use the "application/pdf" media type. |
| 313 |
The subset standards are generally not exclusive, so it is possible |
| 314 |
to construct a PDF file that conforms to, for example, both PDF/A-2b |
| 315 |
and PDF/X-4 subset standards. |
| 316 |
|
| 317 |
PDF documents claiming conformance to one or more of the subset |
| 318 |
standards use XMP metadata to identify levels of conformance. PDF |
| 319 |
processors should examine document metadata streams for such subset |
| 320 |
standards identifiers and, if appropriate, label documents as such |
| 321 |
when presenting them to the user. |
| 322 |
|
| 323 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. PDF Versions</span> |
| 324 |
|
| 325 |
The PDF format has gone through several revisions, primarily for the |
| 326 |
addition of features. PDF features have generally been added in a |
| 327 |
way that older viewers "fail gracefully", because they can just |
| 328 |
ignore features they do not recognize. Even so, the older the PDF |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Hardy, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 335 |
|
| 336 |
|
| 337 |
version produced, the more legacy viewers will support that version, |
| 338 |
but the fewer features will be enabled. The "application/pdf" media |
| 339 |
type is used for all versions. See [<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] Annex I, "PDF Versions |
| 340 |
and Compatibility". |
| 341 |
|
| 342 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. PDF Implementations</span> |
| 343 |
|
| 344 |
PDF files are experienced through a reader or viewer of PDF files. |
| 345 |
For most of the common platforms in use (iOS, OS X, Windows, Android, |
| 346 |
ChromeOS, Kindle) and for most browsers (Edge, Safari, Chrome, |
| 347 |
Firefox), PDF viewing is built in. In addition, there are many PDF |
| 348 |
viewers available for download and installation. The PDF |
| 349 |
specification was published and freely available since the format was |
| 350 |
introduced in 1993, so hundreds of companies and organizations make |
| 351 |
tools for PDF creation, viewing, and manipulation. |
| 352 |
|
| 353 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span> |
| 354 |
|
| 355 |
PDF is certainly a complex media type as per <a href="./rfc6838#section-4.6">Section 4.6 of |
| 356 |
[RFC6838]</a>, which sets requirements for security analysis of media |
| 357 |
type registrations. [<a href="./rfc3778" title=""The application/pdf Media Type"">RFC3778</a>] (which this document obsoletes) |
| 358 |
contained a detailed analysis of some of the security issues for PDF |
| 359 |
implementations known at the time. While the analysis isn't |
| 360 |
necessarily wrong, the threat analysis is much too limited, and the |
| 361 |
mitigations are somewhat out of date. There is now extensive |
| 362 |
literature on security threats involving PDF implementations and how |
| 363 |
to avoid them, consistent with broad implementation over decades. We |
| 364 |
are not registering a new media type but rather are making a |
| 365 |
primarily administrative update. With those caveats: |
| 366 |
|
| 367 |
The PDF file format allows several constructs that may compromise |
| 368 |
security if handled inadequately by PDF processors. For example: |
| 369 |
|
| 370 |
o PDF may contain scripts to customize the displaying and processing |
| 371 |
of PDF files. These scripts are expressed in a version of |
| 372 |
JavaScript and are intended for execution by the PDF processor. |
| 373 |
|
| 374 |
o A PDF file may refer to other PDF files for portions of content. |
| 375 |
PDF processors may be expected to find and use these external |
| 376 |
files when processing the document. |
| 377 |
|
| 378 |
o PDF may act as a container for various files embedded in it (for |
| 379 |
example, as attached files). PDF processors may offer |
| 380 |
functionality to open and display such files or store them on the |
| 381 |
system, such as with the "ef" open action. The PDF specification |
| 382 |
places no restrictions on types of files that may be embedded, so |
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Hardy, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 391 |
|
| 392 |
|
| 393 |
PDF processors should be extremely careful to prevent unwanted |
| 394 |
execution of attached executables or decompression of attached |
| 395 |
archives that may store dangerous files in the host file system. |
| 396 |
|
| 397 |
o PDF files may contain links to content on the Internet. PDF |
| 398 |
processors may offer functionality to show such content upon |
| 399 |
following the link. |
| 400 |
|
| 401 |
o The fragment identifier syntax (<a href="#section-3">Section 3</a>) contains directives for |
| 402 |
opening ("ef") or including ("fdf") additional material. |
| 403 |
|
| 404 |
PDF interpreters executing any scripts or programs related to these |
| 405 |
constructs must be extremely careful to ensure that untrusted |
| 406 |
software is executed in a protected environment. |
| 407 |
|
| 408 |
In addition, the PDF processor itself, as well as its plugins, |
| 409 |
scripts, etc., may be a source of insecurity, by either obvious or |
| 410 |
subtle means. |
| 411 |
|
| 412 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span> |
| 413 |
|
| 414 |
This document updates the registration of "application/pdf", a media |
| 415 |
type registration previously defined in [<a href="./rfc3778" title=""The application/pdf Media Type"">RFC3778</a>], using the |
| 416 |
registration template defined in [<a href="./rfc6838" title=""Media Type Specifications and Registration Procedures"">RFC6838</a>]: |
| 417 |
|
| 418 |
Type name: application |
| 419 |
|
| 420 |
Subtype name: pdf |
| 421 |
|
| 422 |
Required parameters: none |
| 423 |
|
| 424 |
Optional parameter: none |
| 425 |
|
| 426 |
Encoding considerations: binary |
| 427 |
|
| 428 |
Security considerations: See <a href="#section-7">Section 7</a> of this document. |
| 429 |
|
| 430 |
Interoperability considerations: See <a href="#section-5">Section 5</a> of this document. |
| 431 |
|
| 432 |
Published specification: ISO 32000-2 (PDF 2.0) [<a href="#ref-ISOPDF2" title=""Document management -- Portable document format -- Part 2: PDF 2.0"">ISOPDF2</a>] is the |
| 433 |
most recent. |
| 434 |
|
| 435 |
Applications that use this media type: See <a href="#section-6">Section 6</a> of this |
| 436 |
document. |
| 437 |
|
| 438 |
Fragment identifier considerations: See <a href="#section-3">Section 3</a> of this document. |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Hardy, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 447 |
|
| 448 |
|
| 449 |
Additional information: |
| 450 |
|
| 451 |
Deprecated alias names for this type: none |
| 452 |
|
| 453 |
Magic number(s): All PDF files start with the characters "%PDF-" |
| 454 |
followed by the PDF version number, e.g., "%PDF-1.7" or |
| 455 |
"%PDF-2.0". These characters are in US-ASCII encoding. |
| 456 |
|
| 457 |
File extension(s): .pdf |
| 458 |
|
| 459 |
Macintosh file type code(s): "PDF " |
| 460 |
|
| 461 |
Person & email address to contact for further information: |
| 462 |
Duff Johnson <[email protected]>, Peter Wyatt |
| 463 |
<[email protected]>, ISO 32000 Project Leaders. |
| 464 |
|
| 465 |
Intended usage: COMMON |
| 466 |
|
| 467 |
Restrictions on usage: none |
| 468 |
|
| 469 |
Author: Authors of this document |
| 470 |
|
| 471 |
Change controller: ISO; in particular, ISO 32000 is by |
| 472 |
ISO TC 171/SC 02/WG 08, "PDF specification". Duff Johnson |
| 473 |
<[email protected]> and Peter Wyatt |
| 474 |
<[email protected]> are current ISO 32000 Project |
| 475 |
Leaders. |
| 476 |
|
| 477 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span> |
| 478 |
|
| 479 |
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span> |
| 480 |
|
| 481 |
[<a id="ref-ISOPDF">ISOPDF</a>] ISO, "Document management -- Portable document format -- |
| 482 |
Part 1: PDF 1.7", ISO 32000-1:2008, 2008. |
| 483 |
|
| 484 |
[<a id="ref-ISOPDF2">ISOPDF2</a>] ISO, "Document management -- Portable document format -- |
| 485 |
Part 2: PDF 2.0", ISO 32000-2:2017, 2017. |
| 486 |
|
| 487 |
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span> |
| 488 |
|
| 489 |
[<a id="ref-ISOPDFX">ISOPDFX</a>] ISO, "Graphic technology -- Prepress digital data exchange |
| 490 |
using PDF -- Part 8: Partial exchange of printing data |
| 491 |
using PDF 1.6 (PDF/X-5)", ISO 15930-8:2008, 2008. |
| 492 |
|
| 493 |
[<a id="ref-ISOPDFA">ISOPDFA</a>] ISO, "Document management -- Electronic document file |
| 494 |
format for long-term preservation -- Part 3: Use of |
| 495 |
ISO 32000-1 with support for embedded files (PDF/A-3)", |
| 496 |
ISO 19005-3:2012, 2012. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Hardy, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 503 |
|
| 504 |
|
| 505 |
[<a id="ref-ISOPDFE">ISOPDFE</a>] ISO, "Document management -- Engineering document format |
| 506 |
using PDF -- Part 1: Use of PDF 1.6 (PDF/E-1)", |
| 507 |
ISO 24517-1:2008, 2008. |
| 508 |
|
| 509 |
[<a id="ref-ISOPDFVT">ISOPDFVT</a>] ISO, "Graphic technology -- Variable data exchange -- |
| 510 |
Part 2: Using PDF/X-4 and PDF/X-5 (PDF/VT-1 and |
| 511 |
PDF/VT-2)", ISO 16612-2:2010, 2010. |
| 512 |
|
| 513 |
[<a id="ref-ISOPDFUA">ISOPDFUA</a>] ISO, "Document management applications -- Electronic |
| 514 |
document file format enhancement for accessibility -- |
| 515 |
Part 1: Use of ISO 32000-1 (PDF/UA-1)", ISO 14289-1:2014, |
| 516 |
2014. |
| 517 |
|
| 518 |
[<a id="ref-XMP">XMP</a>] ISO, "Graphic technology -- Extensible metadata platform |
| 519 |
(XMP) specification -- Part 1: Data model, serialization |
| 520 |
and core properties", ISO 16684-1, 2012. |
| 521 |
|
| 522 |
[<a id="ref-PS">PS</a>] Adobe Systems Incorporated, "PostScript Language |
| 523 |
Reference, third edition", 1999, |
| 524 |
<<a href="https://www.adobe.com/products/postscript/pdfs/PLRM.pdf">https://www.adobe.com/products/postscript/pdfs/PLRM.pdf</a>>. |
| 525 |
|
| 526 |
[<a id="ref-AdobePDF">AdobePDF</a>] Adobe Systems Incorporated, "PDF Reference, |
| 527 |
sixth edition", 2006, |
| 528 |
<<a href="http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf">http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/</a> |
| 529 |
<a href="http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/pdf_reference_1-7.pdf">pdfs/pdf_reference_1-7.pdf</a>>. |
| 530 |
|
| 531 |
[<a id="ref-RFC6838">RFC6838</a>] Freed, N., Klensin, J., and T. Hansen, "Media Type |
| 532 |
Specifications and Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>, |
| 533 |
<a href="./rfc6838">RFC 6838</a>, DOI 10.17487/RFC6838, January 2013, |
| 534 |
<<a href="http://www.rfc-editor.org/info/rfc6838">http://www.rfc-editor.org/info/rfc6838</a>>. |
| 535 |
|
| 536 |
[<a id="ref-RFC3986">RFC3986</a>] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform |
| 537 |
Resource Identifier (URI): Generic Syntax", STD 66, |
| 538 |
<a href="./rfc3986">RFC 3986</a>, DOI 10.17487/RFC3986, January 2005, |
| 539 |
<<a href="http://www.rfc-editor.org/info/rfc3986">http://www.rfc-editor.org/info/rfc3986</a>>. |
| 540 |
|
| 541 |
[<a id="ref-RFC3778">RFC3778</a>] Taft, E., Pravetz, J., Zilles, S., and L. Masinter, "The |
| 542 |
application/pdf Media Type", <a href="./rfc3778">RFC 3778</a>, |
| 543 |
DOI 10.17487/RFC3778, May 2004, |
| 544 |
<<a href="http://www.rfc-editor.org/info/rfc3778">http://www.rfc-editor.org/info/rfc3778</a>>. |
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Hardy, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Changes since <a href="./rfc3778">RFC 3778</a></span> |
| 562 |
|
| 563 |
This specification replaces <a href="./rfc3778">RFC 3778</a>, which previously defined the |
| 564 |
"application/pdf" Media Type. Differences include the following: |
| 565 |
|
| 566 |
o To reflect the transition from a proprietary specification by |
| 567 |
Adobe to an open ISO standard, the Change Controller has changed |
| 568 |
from Adobe to ISO, and references have been updated. |
| 569 |
|
| 570 |
o The overview of PDF capabilities, the history of PDF, and the |
| 571 |
descriptions of PDF subsets were updated to reflect more recent |
| 572 |
relevant history. |
| 573 |
|
| 574 |
o The section on fragment identifiers was updated to closely reflect |
| 575 |
the material that has been added to ISO-32000-2. |
| 576 |
|
| 577 |
o The status of popular PDF implementations was updated. |
| 578 |
|
| 579 |
o The Security Considerations section was updated to match the |
| 580 |
current understanding of PDF vulnerabilities. |
| 581 |
|
| 582 |
o The registration template was updated to match <a href="./rfc6838">RFC 6838</a>. |
| 583 |
|
| 584 |
|
| 585 |
|
| 586 |
|
| 587 |
|
| 588 |
|
| 589 |
|
| 590 |
|
| 591 |
|
| 592 |
|
| 593 |
|
| 594 |
|
| 595 |
|
| 596 |
|
| 597 |
|
| 598 |
|
| 599 |
|
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Hardy, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc8118">RFC 8118</a> application/pdf March 2017</span> |
| 615 |
|
| 616 |
|
| 617 |
Authors' Addresses |
| 618 |
|
| 619 |
Matthew Hardy |
| 620 |
Adobe Systems Incorporated |
| 621 |
345 Park Ave. |
| 622 |
San Jose, CA 95110 |
| 623 |
United States of America |
| 624 |
|
| 625 |
Email: [email protected] |
| 626 |
|
| 627 |
|
| 628 |
Larry Masinter |
| 629 |
Adobe Systems Incorporated |
| 630 |
345 Park Ave. |
| 631 |
San Jose, CA 95110 |
| 632 |
United States of America |
| 633 |
|
| 634 |
Email: [email protected] |
| 635 |
URI: <a href="http://LarryMasinter.net">http://LarryMasinter.net</a> |
| 636 |
|
| 637 |
|
| 638 |
Dejan Markovic |
| 639 |
Adobe Systems Incorporated |
| 640 |
345 Park Ave. |
| 641 |
San Jose, CA 95110 |
| 642 |
United States of America |
| 643 |
|
| 644 |
Email: [email protected] |
| 645 |
|
| 646 |
|
| 647 |
Duff Johnson |
| 648 |
PDF Association |
| 649 |
Neue Kantstrasse 14 |
| 650 |
Berlin 14057 |
| 651 |
Germany |
| 652 |
|
| 653 |
Email: [email protected] |
| 654 |
|
| 655 |
|
| 656 |
Martin Bailey |
| 657 |
Global Graphics |
| 658 |
2030 Cambourne Business Park |
| 659 |
Cambridge CB23 6DW |
| 660 |
United Kingdom |
| 661 |
|
| 662 |
Email: [email protected] |
| 663 |
URI: <a href="http://www.globalgraphics.com">http://www.globalgraphics.com</a> |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
Hardy, et al. Informational [Page 12] |
| 669 |
</pre> |