tech-invite   World Map
3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search     Home

RFC 8011

 
 
 

Internet Printing Protocol/1.1: Model and Semantics

Part 11 of 12, p. 188 to 200
Prev Section       Next Section

 


prevText      Top      ToC       Page 188 
11.  References

11.1.  Normative References

   [ASME-Y14.1M]
              ASME Y14.1M-2012, "Metric Drawing Sheet Size and Format",
              March 2013.

   [ISO10175] ISO/IEC 10175, "Information technology -- Text and office
              systems -- Document Printing Application (DPA) -- Part 1:
              Abstract service definition and procedures",
              September 1996.

   [ISO10646] ISO/IEC 10646:2014, JTC1/SC2, "Information technology --
              Universal Coded Character Set (UCS)", September 2014.

   [ISO8859-1]
              ISO/IEC 8859-1:1998, "Information technology -- 8-bit
              single-byte coded graphic character sets -- Part 1: Latin
              alphabet No. 1", April 1998.

   [PWG5100.1]
              Sweet, M., "IPP Finishings 2.0 (FIN)", December 2014,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippfinishings20-20141219-5100.1.pdf>.

Top      Up      ToC       Page 189 
   [PWG5100.11]
              Hastings, T. and D. Fullman, "Internet Printing Protocol
              (IPP): Job and Printer Extensions -- Set 2 (JPS2)",
              October 2010, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippjobprinterext10-20101030-5100.11.pdf>.

   [PWG5100.12]
              Sweet, M. and I. McDonald, "IPP Version 2.0, 2.1, and
              2.2", October 2015, <http://ftp.pwg.org/pub/pwg/standards/
              std-ipp20-20151030-5100.12.pdf>.

   [PWG5100.13]
              Sweet, M., McDonald, I., and P. Zehler, "IPP: Job and
              Printer Extensions -- Set 3 (JPS3)", July 2012,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippjobprinterext3v10-20120727-5100.13.pdf>.

   [PWG5100.14]
              Sweet, M., McDonald, I., Mitchell, A., and J. Hutchings,
              "IPP Everywhere", January 2013,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippeve10-20130128-5100.14.pdf>.

   [PWG5100.15]
              Sweet, M., "IPP FaxOut Service", June 2014,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippfaxout10-20140618-5100.15.pdf>.

   [PWG5100.16]
              Sweet, M., "IPP Transaction-Based Printing Extensions",
              November 2013, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ipptrans10-20131108-5100.16.pdf>.

   [PWG5100.17]
              Zehler, P. and M. Sweet, "IPP Scan Service (SCAN)",
              September 2014, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippscan10-20140918-5100.17.pdf>.

   [PWG5100.18]
              Sweet, M. and I. McDonald, "IPP Shared Infrastructure
              Extensions (INFRA)", June 2015,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippinfra10-20150619-5100.18.pdf>.

   [PWG5100.19]
              Kennedy, S., "IPP Implementor's Guide v2.0 (IG)",
              August 2015, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippig20-20150821-5100.19.pdf>.

Top      Up      ToC       Page 190 
   [PWG5100.2]
              Hastings, T. and R. Bergman, "Internet Printing Protocol
              (IPP): "output-bin" attribute extension", February 2001,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippoutputbin10-20010207-5100.2.pdf>.

   [PWG5100.3]
              Ocke, K. and T. Hastings, "Internet Printing Protocol
              (IPP): Production Printing Attributes -- Set1",
              February 2001, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippprodprint10-20010212-5100.3.pdf>.

   [PWG5100.5]
              Carney, D., Hastings, T., and P. Zehler, "Standard for The
              Internet Printing Protocol (IPP): Document Object",
              October 2003, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippdocobject10-20031031-5100.5.pdf>.

   [PWG5100.6]
              Zehler, P., Herriot, R., and K. Ocke, "Standard for The
              Internet Printing Protocol (IPP): Page Overrides",
              October 2003, <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ipppageoverride10-20031031-5100.6.pdf>.

   [PWG5100.7]
              Hastings, T. and P. Zehler, "Standard for The Internet
              Printing Protocol (IPP): Job Extensions", October 2003,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippjobext10-20031031-5100.7.pdf>.

   [PWG5100.8]
              Carney, D. and H. Lewis, "Standard for Internet Printing
              Protocol (IPP): "-actual" attributes", March 2003,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippactuals10-20030313-5100.8.pdf>.

   [PWG5100.9]
              McDonald, I. and C. Whittle, "Internet Printing Protocol
              (IPP): Printer State Extensions v1.0", July 2009,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-ippstate10-20090731-5100.9.pdf>.

   [PWG5101.1]
              Sweet, M., Bergman, R., and T. Hastings, "PWG Media
              Standardized Names 2.0 (MSN2)", March 2013,
              <http://ftp.pwg.org/pub/pwg/candidates/
              cs-pwgmsn20-20130328-5101.1.pdf>.

Top      Up      ToC       Page 191 
   [RFC20]    Cerf, V., "ASCII format for network interchange", STD 80,
              RFC 20, DOI 10.17487/RFC0020, October 1969,
              <http://www.rfc-editor.org/info/rfc20>.

   [RFC793]   Postel, J., "Transmission Control Protocol", STD 7,
              RFC 793, DOI 10.17487/RFC0793, September 1981,
              <http://www.rfc-editor.org/info/rfc793>.

   [RFC1035]  Mockapetris, P., "Domain names - implementation and
              specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
              November 1987, <http://www.rfc-editor.org/info/rfc1035>.

   [RFC1951]  Deutsch, P., "DEFLATE Compressed Data Format Specification
              version 1.3", RFC 1951, DOI 10.17487/RFC1951, May 1996,
              <http://www.rfc-editor.org/info/rfc1951>.

   [RFC1952]  Deutsch, P., "GZIP file format specification version 4.3",
              RFC 1952, DOI 10.17487/RFC1952, May 1996,
              <http://www.rfc-editor.org/info/rfc1952>.

   [RFC1977]  Schryver, V., "PPP BSD Compression Protocol", RFC 1977,
              DOI 10.17487/RFC1977, August 1996,
              <http://www.rfc-editor.org/info/rfc1977>.

   [RFC2046]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part Two: Media Types", RFC 2046,
              DOI 10.17487/RFC2046, November 1996,
              <http://www.rfc-editor.org/info/rfc2046>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC2818]  Rescorla, E., "HTTP Over TLS", RFC 2818,
              DOI 10.17487/RFC2818, May 2000,
              <http://www.rfc-editor.org/info/rfc2818>.

   [RFC3196]  Hastings, T., Manros, C., Zehler, P., Kugler, C., and H.
              Holst, "Internet Printing Protocol/1.1: Implementor's
              Guide", RFC 3196, DOI 10.17487/RFC3196, November 2001,
              <http://www.rfc-editor.org/info/rfc3196>.

   [RFC3380]  Hastings, T., Herriot, R., Kugler, C., and H. Lewis,
              "Internet Printing Protocol (IPP): Job and Printer Set
              Operations", RFC 3380, DOI 10.17487/RFC3380,
              September 2002, <http://www.rfc-editor.org/info/rfc3380>.

Top      Up      ToC       Page 192 
   [RFC3510]  Herriot, R. and I. McDonald, "Internet Printing
              Protocol/1.1: IPP URL Scheme", RFC 3510,
              DOI 10.17487/RFC3510, April 2003,
              <http://www.rfc-editor.org/info/rfc3510>.

   [RFC3629]  Yergeau, F., "UTF-8, a transformation format of
              ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629,
              November 2003, <http://www.rfc-editor.org/info/rfc3629>.

   [RFC3805]  Bergman, R., Lewis, H., and I. McDonald, "Printer MIB v2",
              RFC 3805, DOI 10.17487/RFC3805, June 2004,
              <http://www.rfc-editor.org/info/rfc3805>.

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, DOI 10.17487/RFC3986, January 2005,
              <http://www.rfc-editor.org/info/rfc3986>.

   [RFC3995]  Herriot, R. and T. Hastings, "Internet Printing Protocol
              (IPP): Event Notifications and Subscriptions", RFC 3995,
              DOI 10.17487/RFC3995, March 2005,
              <http://www.rfc-editor.org/info/rfc3995>.

   [RFC3996]  Herriot, R., Hastings, T., and H. Lewis, "Internet
              Printing Protocol (IPP): The 'ippget' Delivery Method for
              Event Notifications", RFC 3996, DOI 10.17487/RFC3996,
              March 2005, <http://www.rfc-editor.org/info/rfc3996>.

   [RFC3998]  Kugler, C., Lewis, H., and T. Hastings, Ed., "Internet
              Printing Protocol (IPP): Job and Printer Administrative
              Operations", RFC 3998, DOI 10.17487/RFC3998, March 2005,
              <http://www.rfc-editor.org/info/rfc3998>.

   [RFC5051]  Crispin, M., "i;unicode-casemap - Simple Unicode Collation
              Algorithm", RFC 5051, DOI 10.17487/RFC5051, October 2007,
              <http://www.rfc-editor.org/info/rfc5051>.

   [RFC5234]  Crocker, D., Ed., and P. Overell, "Augmented BNF for
              Syntax Specifications: ABNF", STD 68, RFC 5234,
              DOI 10.17487/RFC5234, January 2008,
              <http://www.rfc-editor.org/info/rfc5234>.

   [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer Security
              (TLS) Protocol Version 1.2", RFC 5246,
              DOI 10.17487/RFC5246, August 2008,
              <http://www.rfc-editor.org/info/rfc5246>.

Top      Up      ToC       Page 193 
   [RFC5646]  Phillips, A., Ed., and M. Davis, Ed., "Tags for
              Identifying Languages", BCP 47, RFC 5646,
              DOI 10.17487/RFC5646, September 2009,
              <http://www.rfc-editor.org/info/rfc5646>.

   [RFC6838]  Freed, N., Klensin, J., and T. Hansen, "Media Type
              Specifications and Registration Procedures", BCP 13,
              RFC 6838, DOI 10.17487/RFC6838, January 2013,
              <http://www.rfc-editor.org/info/rfc6838>.

   [RFC7230]  Fielding, R., Ed., and J. Reschke, Ed., "Hypertext
              Transfer Protocol (HTTP/1.1): Message Syntax and Routing",
              RFC 7230, DOI 10.17487/RFC7230, June 2014,
              <http://www.rfc-editor.org/info/rfc7230>.

   [RFC7472]  McDonald, I. and M. Sweet, "Internet Printing Protocol
              (IPP) over HTTPS Transport Binding and the 'ipps' URI
              Scheme", RFC 7472, DOI 10.17487/RFC7472, March 2015,
              <http://www.rfc-editor.org/info/rfc7472>.

   [RFC7612]  Fleming, P. and I. McDonald, "Lightweight Directory Access
              Protocol (LDAP): Schema for Printer Services", RFC 7612,
              DOI 10.17487/RFC7612, June 2015,
              <http://www.rfc-editor.org/info/rfc7612>.

   [RFC7616]  Shekh-Yusef, R., Ed., Ahrens, D., and S. Bremer, "HTTP
              Digest Access Authentication", RFC 7616,
              DOI 10.17487/RFC7616, September 2015,
              <http://www.rfc-editor.org/info/rfc7616>.

   [RFC7617]  Reschke, J., "The 'Basic' HTTP Authentication Scheme",
              RFC 7617, DOI 10.17487/RFC7617, September 2015,
              <http://www.rfc-editor.org/info/rfc7617>.

   [RFC8010]  Sweet, M. and I. McDonald, "Internet Printing
              Protocol/1.1: Encoding and Transport", RFC 8010,
              DOI 10.17487/RFC8010, January 2017,
              <http://www.rfc-editor.org/info/rfc8010>.

Top      Up      ToC       Page 194 
11.2.  Informative References

   [HTPP]     Barnett, J., Carter, K., and R. deBry, "Internet Print
              Protocol Proposal: HTPP -- Hypertext Print Protocol
              (HTPP/1.0 Initial Draft)", October 1996,
              <ftp://ftp.pwg.org/pub/pwg/ipp/historic/htpp/
              overview.ps.gz>.

   [IANA-CS]  IANA, "Registry of Coded Character Sets",
              <http://www.iana.org/assignments/character-sets/>.

   [IANA-MT]  IANA, "Media Types",
              <http://www.iana.org/assignments/media-types/>.

   [IANA-PEN]
              IANA, "Private Enterprise Numbers",
              <http://www.iana.org/assignments/enterprise-numbers/>.

   [ISO32000] "Document management -- Portable document format --
              Part 1: PDF 1.7", July 2008, <http://www.adobe.com/
              devnet/acrobat/pdfs/PDF32000_2008.pdf>.

   [LDPA]     Isaacson, S., Taylor, D., MacKay, M., Zehler, P.,
              Hastings, T., and C. Manros, "LDPA - Lightweight Document
              Printing Application", Proposed Internet-Draft,
              October 1996, <ftp://ftp.pwg.org/pub/pwg/ipp/
              historic/ldpa/ldpa8.pdf.gz>.

   [P1387.4]  Kirk, M., "POSIX Systems Administration - Part 4: Printing
              Interfaces, POSIX 1387.4 D8", 1998.

   [PSIS]     Herriot, R., Ed., "X/Open: A Printing System
              Interoperability Specification (PSIS)", August 1995.

   [PWG-IPP-WG]
              IEEE-ISTO Printer Working Group, "Internet Printing
              Protocol Workgroup", <http://www.pwg.org/ipp>.

   [RFC959]   Postel, J. and J. Reynolds, "File Transfer Protocol",
              STD 9, RFC 959, DOI 10.17487/RFC0959, October 1985,
              <http://www.rfc-editor.org/info/rfc959>.

   [RFC1179]  McLaughlin, L., "Line printer daemon protocol", RFC 1179,
              DOI 10.17487/RFC1179, August 1990,
              <http://www.rfc-editor.org/info/rfc1179>.

Top      Up      ToC       Page 195 
   [RFC1738]  Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
              Resource Locators (URL)", RFC 1738, DOI 10.17487/RFC1738,
              December 1994, <http://www.rfc-editor.org/info/rfc1738>.

   [RFC2565]  Herriot, R., Ed., Butler, S., Moore, P., and R. Turner,
              "Internet Printing Protocol/1.0: Encoding and Transport",
              RFC 2565, DOI 10.17487/RFC2565, April 1999,
              <http://www.rfc-editor.org/info/rfc2565>.

   [RFC2566]  deBry, R., Hastings, T., Herriot, R., Isaacson, S., and P.
              Powell, "Internet Printing Protocol/1.0: Model and
              Semantics", RFC 2566, DOI 10.17487/RFC2566, April 1999,
              <http://www.rfc-editor.org/info/rfc2566>.

   [RFC2567]  Wright, F., "Design Goals for an Internet Printing
              Protocol", RFC 2567, DOI 10.17487/RFC2567, April 1999,
              <http://www.rfc-editor.org/info/rfc2567>.

   [RFC2568]  Zilles, S., "Rationale for the Structure of the Model and
              Protocol for the Internet Printing Protocol", RFC 2568,
              DOI 10.17487/RFC2568, April 1999,
              <http://www.rfc-editor.org/info/rfc2568>.

   [RFC2569]  Herriot, R., Ed., Hastings, T., Jacobs, N., and J. Martin,
              "Mapping between LPD and IPP Protocols", RFC 2569,
              DOI 10.17487/RFC2569, April 1999,
              <http://www.rfc-editor.org/info/rfc2569>.

   [RFC2579]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Textual Conventions for SMIv2",
              STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
              <http://www.rfc-editor.org/info/rfc2579>.

   [RFC2978]  Freed, N. and J. Postel, "IANA Charset Registration
              Procedures", BCP 19, RFC 2978, DOI 10.17487/RFC2978,
              October 2000, <http://www.rfc-editor.org/info/rfc2978>.

   [RFC3239]  Kugler, C., Lewis, H., and T. Hastings, "Internet Printing
              Protocol (IPP): Requirements for Job, Printer, and Device
              Administrative Operations", RFC 3239,
              DOI 10.17487/RFC3239, February 2002,
              <http://www.rfc-editor.org/info/rfc3239>.

   [RFC3997]  Hastings, T., Ed., deBry, R., and H. Lewis, "Internet
              Printing Protocol (IPP): Requirements for IPP
              Notifications", RFC 3997, DOI 10.17487/RFC3997,
              March 2005, <http://www.rfc-editor.org/info/rfc3997>.

Top      Up      ToC       Page 196 
   [RFC4122]  Leach, P., Mealling, M., and R. Salz, "A Universally
              Unique IDentifier (UUID) URN Namespace", RFC 4122,
              DOI 10.17487/RFC4122, July 2005,
              <http://www.rfc-editor.org/info/rfc4122>.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              DOI 10.17487/RFC5226, May 2008,
              <http://www.rfc-editor.org/info/rfc5226>.

   [RFC6068]  Duerst, M., Masinter, L., and J. Zawinski, "The 'mailto'
              URI Scheme", RFC 6068, DOI 10.17487/RFC6068, October 2010,
              <http://www.rfc-editor.org/info/rfc6068>.

   [RFC7525]  Sheffer, Y., Holz, R., and P. Saint-Andre,
              "Recommendations for Secure Use of Transport Layer
              Security (TLS) and Datagram Transport Layer Security
              (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525,
              May 2015, <http://www.rfc-editor.org/info/rfc7525>.

   [SWP]      Moore, P. and S. Butler, "Simple Web Printing (SWP/1.0)",
              May 1997, <ftp://ftp.pwg.org/pub/pwg/ipp/new_PRO/
              swp9705.pdf>.

Top      Up      ToC       Page 197 
Appendix A.  Formats for IPP Registration Proposals

   In order to propose an IPP extension for registration, the proposer
   must submit an application to IANA by email to "iana@iana.org" or by
   filling out the appropriate form on the IANA web pages
   (http://www.iana.org).  This section specifies the required
   information and the formats for proposing registrations of extensions
   to IPP as provided in Section 7 for:

   1.  attributes

   2.  type2 'keyword' attribute values

   3.  type2 'enum' attribute values

   4.  operations

   5.  status-code values

A.1.  Attribute Registration

   Type of registration: attribute

   Proposed keyword name of this attribute:

   Types of attributes (Document Description, Document Status, Document
   Template, Event Notifications, Job Description, Job Status, Job
   Template, Operation, Printer Description, Printer Status,
   Subscription Description, Subscription Status, Subscription
   Template):

   Operations to be used if the attribute is an operation attribute:

   Object (Document, Job, Printer, Subscription, etc. if bound to an
   object):

   Attribute syntax(es) (include '1setOf' and range; see Section 5.2):

   If attribute syntax is 'keyword' or 'enum', is it type1 or type2?

   If this is a Printer attribute, MAY the value returned depend on
   "document-format"?  (See Section 7.2.)

   If this is a Job Template attribute, how does its specification
   depend on the value of the "multiple-document-handling" attribute?

Top      Up      ToC       Page 198 
   Specification of this attribute (follow the style of Section 5.2):

   Name of proposer:

   Email address of proposer:

   Note: For attributes, the IPP Designated Expert will be the point of
   contact and change controller for the approved registration
   specification, if any maintenance of the registration specification
   is needed.

A.2.  type2 'keyword' Attribute Value Registration

   Type of registration: type2 keyword attribute value

   Name of attribute to which this keyword specification is to be added:

   Proposed keyword name of this 'keyword' value:

   Specification of this 'keyword' value (follow the style of
   Section 5.1.4):

   Name of proposer:

   Email address of proposer:

   Note: For type2 keywords, the Designated Expert will be the point of
   contact and change controller for the approved registration
   specification, if any maintenance of the registration specification
   is needed.

A.3.  type2 'enum' Attribute Value Registration

   Type of registration: type2 enum attribute value

   Name of attribute to which this enum specification is to be added:

   Keyword symbolic name of this enum value:

   Numeric value (to be assigned by the IPP Designated Expert in
   consultation with IANA):

   Specification of this enum value (follow the style of Section 5.1.5):

   Name of proposer:

   Email address of proposer:

Top      Up      ToC       Page 199 
   Note: For type2 enums, the Designated Expert will be the point of
   contact and change controller for the approved registration
   specification, if any maintenance of the registration specification
   is needed.

A.4.  Operation Registration

   Type of registration: operation

   Proposed name of this operation:

   Numeric "operation-id" value according to Section 5.4.15 (to be
   assigned by the IPP Designated Expert in consultation with IANA):

   Object Target (Document, Job, Printer, Subscription, etc. that
   operation is upon):

   Specification of this operation (follow the style of Section 4):

   Name of proposer:

   Email address of proposer:

   Note: For operations, the IPP Designated Expert will be the point of
   contact and change controller for the approved registration
   specification, if any maintenance of the registration specification
   is needed.

A.5.  Status-Code Registration

   Type of registration: status-code

   Keyword symbolic name of this status-code value:

   Numeric value (to be assigned by the IPP Designated Expert in
   consultation with IANA):

   Operations that this status-code can be used with:

   Specification of this status-code (follow the style of Appendix B):

   Name of proposer:

   Email address of proposer:

Top      Up      ToC       Page 200 
   Note: For status-code values, the Designated Expert will be the point
   of contact and change controller for the approved registration
   specification, if any maintenance of the registration specification
   is needed.



(page 200 continued on part 12)

Next Section