RFC 8118 on The application/pdf Media Type

rfc-editor@rfc-editor.org Fri, 17 March 2017 23:11 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EBF712968A for <ietf-announce@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wF1wu8ppQCpm for <ietf-announce@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62AE5129695 for <ietf-announce@ietf.org>; Fri, 17 Mar 2017 16:11:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 981F6B80DBC; Fri, 17 Mar 2017 16:11:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8118 on The application/pdf Media Type
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170317231101.981F6B80DBC@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:11:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/JrtNLCwUbGpnJ4sLkm7iBYrWc7U>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 23:11:56 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8118

        Title:      The application/pdf Media Type 
        Author:     M. Hardy,
                    L. Masinter,
                    D. Markovic, 
                    D. Johnson,
                    M. Bailey
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mahardy@adobe.com, 
                    masinter@adobe.com, 
                    dmarkovi@adobe.com, 
                    duff.johnson@pdfa.org, 
                    martin.bailey@globalgraphics.com
        Pages:      12
        Characters: 24463
        Obsoletes:  RFC 3778

        I-D Tag:    draft-hardy-pdf-mime-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8118

        DOI:        10.17487/RFC8118

The Portable Document Format (PDF) is an ISO standard (ISO
32000-1:2008) defining a final-form document representation language
in use for document exchange, including on the Internet, since 1993.
This document provides an overview of the PDF format and updates the
media type registration of "application/pdf".  It obsoletes RFC 3778.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC