RFC 2911:Internet Printing Protocol/1.1: Model and...
RFC-Ref

encoding


Click on the red underlined text to get to the source

... Semantics (this document) Internet Printing Protocol/1.1: Encoding and Transport [RFC2910] ...


... - the attributes that are REQUIRED for that type of response. The "Encoding and Transport" document [RFC2910] defines special rules ...
... Transport" document [RFC2910] defines special rules for the encoding of these parameters. All other operation elements are represented using the more generic encoding rules ...
... encoding of these parameters. All other operation elements are represented using the more generic encoding rules for attributes and groups of attributes. ...
... charset (coded character set and encoding method) used by any 'text' and 'name' attributes that the client ...
... Note: The IPP "Encoding and Transport document [RFC2910] shows a ...
... 'unsupported'. This value's syntax type is "out-of-band" and its encoding is defined by special rules for "out-of-band" values in the "Encoding ...
... encoding is defined by special rules for "out-of-band" values in the "Encoding and Transport" document [RFC2910]. Its value indicates no ...
... Semantics document (this document) or a new version of the "Encoding and Transport" document [RFC2910 ...
... any changes to the Model and Semantics document (this document) or the "Encoding and Transport" document [RFC2910] itself, such as: ...
... version number include any changes to the model objects and attributes but not the encoding and transport rules [RFC2910] (except adding attribute ...
... - adding OPTIONAL attribute syntaxes to an existing attribute. The encoding of the "version-number" MUST NOT change over any version number (either major or minor). This rule guarantees that all future ...


... request) MAY be one of the "out-of-band" values whose special encoding rules are defined in the "Encoding and Transport" document ...
... out-of-band" values whose special encoding rules are defined in the "Encoding and Transport" document [RFC2910 ...
... 'Rapport Mensuel': the job name in French See the "Encoding and Transport" document [RFC2910] section 3.9 for ...
... Transport" document [RFC2910] section 3.9 for the encoding of the two parts and Appendix A for a detailed example of the 'textWithLanguage' attribute syntax. ...
... 'Farbdrucker': the Printer name in German See the "Encoding and Transport" document [RFC2910] section 3.9 for ...
... Transport" document [RFC2910] section 3.9 for the encoding of the two parts and Appendix A for a detailed example of the 'nameWithLanguage' attribute syntax. ...
... charset. A charset is a coded character set and encoding scheme. Charsets are used for labeling certain document contents and 'text' ...
... UCS) represented as the UTF-8 [RFC2279] transfer encoding scheme in which US-ASCII is a subset charset ...
... identifies the charset (coded character set and encoding method) used by any Job attributes with attribute syntax 'text' and 'name' that ...
... IPP/1.1 "Transport and Encoding" document [RFC2910] for the actual URI schemes to be used in ...
... IPP "Model and Semantics" document or the IPP "Encoding and Transport" document following the rules, if any, when the ...
... Semantics" document or the IPP Encoding and Transport document following the rules, if any, when the "version ...
... Compression only applies to the document data; compression does not apply to the encoding of the IPP operation itself. The supported values are used to validate ...


... channel, a Printer MAY print all or part of the received portion of the document. See the "Encoding and Transport" document [RFC2910] ...
... Client Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910]. A client ...
... Server Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910]. See also section 8 of ...
... IPP Printer implementation SHOULD contain support for Client Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910 ...
... Privacy and Server Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910 ...


... extension rules described in Section 6.1. The initial set of value codes that identify each of the attribute syntaxes have been assigned in the "Encoding and Transport" document [RFC2910], including a ...
... group tags have been assigned in the "Encoding and Transport" document [RFC2910], including a ...
... type2 procedures described in Section 6.1. The initial set of out- of-band attribute value tags have been assigned in the "Encoding and Transport" document [RFC2910 ...


... Herriot, R., Butler, S., Moore, P. and R. Turner, "Internet Printing Protocol/1.0: Encoding and Transport", RFC 2565(-> 2910prop), April 1999. ...
... Hastings, T. and C. Manros, "Internet Printing Protocol/1.0: Encoding and Transport", RFC 2639(-> 3196), July 1999. ...
... Herriot, R., Butler, S., Moore, P., Turner, R. and J. Wenn, "Internet Printing Protocol/1.1: Encoding and Transport", RFC 2910prop, September 2000. ...


... Each attribute is defined using an explicit syntax type. In this document, each syntax type is defined as a keyword with specific meaning. The "Encoding and Transport" document [RFC2910] indicates ...
... Transport" document [RFC2910] indicates the actual "on-the-wire" encoding rules for each syntax type. Attribute syntax types are defined in section 4.1. ...


... print jobs and it receives a print job that exceeds that limit or when the attributes are so many that their encoding causes the request entity to exceed IPP ...


... returning attributes that were in the request. Moved the text from section 3.2.1.2 Unsupported Attributes to this section. 11. Sections 3.1.7 and 4.1 - clarified the encoding of the "out- of-band" 'unsupported' and 'unknown' values. 12. Section 3.1.8 - clarified that only the version number ...
... Print-URI or Send-URI). 27. Section 4.1 - clarified that the encoding of the out-of-band values are specified in the Encoding ...
... encoding of the out-of-band values are specified in the Encoding and Transport" document. 28. Section 4.1 - Clarified that the requirement ...
... RECOMMENDED non-standards track SSL3 to MUST support Client Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910 ...
... Server Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910]. ...
... Client Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910]. A Printer ...
... Server Authentication as defined in the IPP/1.1 Encoding and Transport document [RFC2910 ...
... See also the "IPP/1.1 Encoding and Transport" [RFC2910] document for ...



Google
Web
RFC-Ref