Internet Printing Protocol/1.1: Encoding and Transport
draft-sweet-rfc2910bis-08
The information below is for an old version of the document | |||
---|---|---|---|
Document | Type | Active Internet-Draft (individual in art area) | |
Authors | Michael Sweet , Ira McDonald | ||
Last updated | 2016-08-04 (latest revision 2016-06-13) | ||
Stream | IETF | ||
Intended RFC status | Proposed Standard | ||
Formats | pdf htmlized (tools) htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Barry Leiba | ||
Shepherd write-up | Show (last changed 2016-06-21) | ||
IESG | IESG state | IESG Evaluation::Revised I-D Needed | |
Consensus Boilerplate | Yes | ||
Telechat date |
Needs a YES. Needs 7 more YES or NO OBJECTION positions to pass. |
||
Responsible AD | Alexey Melnikov | ||
Send notices to | "Barry Leiba" <barryleiba@computer.org> | ||
IANA | IANA review state | IANA OK - Actions Needed |
IPP WG M. Sweet Internet-Draft Apple Inc. Obsoletes: 2910,3382 (if approved) I. McDonald Intended status: Standards Track High North, Inc. Expires: December 15, 2016 June 13, 2016 Internet Printing Protocol/1.1: Encoding and Transport draft-sweet-rfc2910bis-08 Abstract This document is one of a set of documents, which together describe all aspects of a new Internet Printing Protocol (IPP). IPP is an application level protocol that can be used for distributed printing using Internet tools and technologies. This document defines the rules for encoding IPP operations and IPP attributes into the Internet MIME media type called "application/ipp". This document also defines the rules for transporting a message body whose Content- Type is "application/ipp" over HTTP. Editor's Note This draft is being submitted as an AD-sponsored replacement of RFCs 2910 and 3382, with drafts being reviewed and edited by the IEEE- ISTO's Printer Working Group IPP WG. The initial goal is to have an clean version of IPP/1.1 as an IETF Proposed Standard. The long-term goal is to advance IPP/1.1 to IETF Internet Standard. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 15, 2016. Sweet & McDonald Expires December 15, 2016 [Page 1] Internet-Draft IPP/1.1: Encoding and Transport June 2016 Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 4 2.1. Requirements Language . . . . . . . . . . . . . . . . . . . 4 2.2. Printing Terminology . . . . . . . . . . . . . . . . . . . 4 2.3. Abbreviations . . . . . . . . . . . . . . . . . . . . . . . 5 3. Encoding of the Operation Layer . . . . . . . . . . . . . . . 6 3.1. Picture of the Encoding . . . . . . . . . . . . . . . . . . 7 3.1.1. Request and Response . . . . . . . . . . . . . . . . . . 7 3.1.2. Attribute Group . . . . . . . . . . . . . . . . . . . . . 8 3.1.3. Attribute . . . . . . . . . . . . . . . . . . . . . . . . 8 3.1.4. Attribute-with-one-value . . . . . . . . . . . . . . . . 8 3.1.5. Additional-value . . . . . . . . . . . . . . . . . . . . 9 3.1.6. Collection Attribute . . . . . . . . . . . . . . . . . . 10 3.1.7. Member Attributes . . . . . . . . . . . . . . . . . . . . 11 3.1.8. Alternative Picture of the Encoding of a Request Or a Response . . . . . . . . . . . . . . . . . . . . . . . . 12 3.2. Syntax of Encoding . . . . . . . . . . . . . . . . . . . . 13 3.3. Attribute-group . . . . . . . . . . . . . . . . . . . . . . 15 3.4. Required Parameters . . . . . . . . . . . . . . . . . . . . 17 3.4.1. Version-number . . . . . . . . . . . . . . . . . . . . . 17 3.4.2. Operation-id . . . . . . . . . . . . . . . . . . . . . . 17 3.4.3. Status-code . . . . . . . . . . . . . . . . . . . . . . . 17 3.4.4. Request-id . . . . . . . . . . . . . . . . . . . . . . . 18 3.5. Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3.5.1. Delimiter Tags . . . . . . . . . . . . . . . . . . . . . 18 3.5.2. Value Tags . . . . . . . . . . . . . . . . . . . . . . . 19 3.6. Name-Length . . . . . . . . . . . . . . . . . . . . . . . . 21 3.7. (Attribute) Name . . . . . . . . . . . . . . . . . . . . . 22Show full document text