RFC 8010 on Internet Printing Protocol/1.1: Encoding and Transport
rfc-editor@rfc-editor.org Tue, 17 January 2017 21:59 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 BAB421295CE for <ietf-announce@ietfa.amsl.com>; Tue, 17 Jan 2017 13:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-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 KKP_XH6GVqji for <ietf-announce@ietfa.amsl.com>; Tue, 17 Jan 2017 13:59:23 -0800 (PST)
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 8174B1295C7 for <ietf-announce@ietf.org>; Tue, 17 Jan 2017 13:59:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7289EB80150; Tue, 17 Jan 2017 13:59:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8010 on Internet Printing Protocol/1.1: Encoding and Transport
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170117215923.7289EB80150@rfc-editor.org>
Date: Tue, 17 Jan 2017 13:59:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/sumv7p7JnB1WlW_WKU3uUum2k5c>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Tue, 17 Jan 2017 21:59:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8010
Title: Internet Printing Protocol/1.1:
Encoding and Transport
Author: M. Sweet, I. McDonald
Status: Standards Track
Stream: IETF
Date: January 2017
Mailbox: msweet@apple.com,
blueroofmusic@gmail.com
Pages: 51
Characters: 115605
Obsoletes: RFC 2910, RFC 3382
I-D Tag: draft-sweet-rfc2910bis-10.txt
URL: https://www.rfc-editor.org/info/rfc8010
DOI: 10.17487/RFC8010
The Internet Printing Protocol (IPP) is an application-level protocol
for distributed printing using Internet tools and technologies. This
document defines the rules for encoding IPP operations, attributes,
and values into the Internet MIME media type called "application/ipp". It
also defines the rules for transporting a message body
whose Content-Type is "application/ipp" over HTTP and/or HTTPS. The
IPP data model and operation semantics are described in "Internet
Printing Protocol/1.1: Model and Semantics" (RFC 8011).
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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