RFC 8011 on Internet Printing Protocol/1.1: Model and Semantics

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 []) by ietfa.amsl.com (Postfix) with ESMTP id E18BD1295D9 for <ietf-announce@ietfa.amsl.com>; Tue, 17 Jan 2017 13:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 0ES_E1otA_Uc for <ietf-announce@ietfa.amsl.com>; Tue, 17 Jan 2017 13:59:45 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 546121295D1 for <ietf-announce@ietf.org>; Tue, 17 Jan 2017 13:59:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2FF23B8015F; Tue, 17 Jan 2017 13:59:39 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8011 on Internet Printing Protocol/1.1: Model and Semantics
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170117215939.2FF23B8015F@rfc-editor.org>
Date: Tue, 17 Jan 2017 13:59:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lWLpGimpYdkTD9e2574VNwqjeOY>
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:48 -0000

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

        RFC 8011

        Title:      Internet Printing Protocol/1.1: Model and 
        Author:     M. Sweet, I. McDonald
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2017
        Mailbox:    msweet@apple.com, 
        Pages:      221
        Characters: 535490
        Obsoletes:  RFC 2911, RFC 3381, RFC 3382

        I-D Tag:    draft-sweet-rfc2911bis-11.txt

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

        DOI:        10.17487/RFC8011

The Internet Printing Protocol (IPP) is an application-level protocol
for distributed printing using Internet tools and technologies.  This
document describes a simplified model consisting of abstract objects,
attributes, and operations that is independent of encoding and
transport.  The model consists of several objects, including Printers
and Jobs.  Jobs optionally support multiple Documents.

IPP semantics allow End Users and Operators to query Printer
capabilities; submit Print Jobs; inquire about the status of Print
Jobs and Printers; and cancel, hold, and release Print Jobs.  IPP
semantics also allow Operators to pause and resume Jobs and Printers.

Security, internationalization, and directory issues are also
addressed by the model and semantics.  The IPP message encoding and
transport are described in "Internet Printing Protocol/1.1: Encoding
and Transport" (RFC 8010).

This document obsoletes RFCs 2911, 3381, and 3382.

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

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