1 - 3 - 7 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - Q - R - S - T - U - V - W
requirement
Click on the red underlined text to get to the source
... - Section 4 defines the attributes (and their syntaxes) that are
used in the model.
- Sections 5 - 6 summarizes the implementation conformance
requirements for objects that support the protocol and IANA
considerations, respectively.
...
... context of the Printer object to which the create request was
originally submitted. This requirement to support both Job URIs and
Job IDs allows all types of clients ...
... integer (possibly unique depending on
client requirements) in the range from 1 to 2**31 - 1 (inclusive).
This "request-id" allows clients ...
... client can check that the client and
Printer object security requirements can be met before performing a
Print-Job operation.
...
... Printer object supports that natural language or not. These
requirements are independent of the value of the "ipp-attribute-
fidelity" operation attribute that the client ...
... b. the Associated Natural-Language parts match if the
shorter of the two meets the syntactic requirements of RFC
1766(-> 3282draft | 3066(-> 4647 | 4646)) [RFC1766 ...
... integer).
Some attribute descriptions MAY place additional requirements on
charset values that may be used, such as REQUIRED values that MUST be
...
...
This section describes conformance issues and requirements. This
document introduces model entities such as objects, operations,
attributes, attribute syntaxes, and attribute values. These
...
... document introduces model entities such as objects, operations,
attributes, attribute syntaxes, and attribute values. These
conformance sections describe the conformance requirements which
apply to these model entities.
...
... Client Conformance Requirements ...
... request, a conforming client MUST supply a value whose type and value
syntax conforms to the requirements of the Model document as
specified in Sections 3 and 4. A conforming client MAY supply any
...
... client MAY supply any
registered extensions and/or private extensions in an operation
request, as long as they meet the requirements in Section 6.
Otherwise, there are no conformance requirements ...
... requirements in Section 6.
Otherwise, there are no conformance requirements placed on the user
interfaces provided by IPP clients ...
... IPP Object Conformance Requirements ...
...
This section specifies the conformance requirements for conforming
implementations with respect to objects, operations, and attributes.
...
... A conforming IPP object MAY support registered extensions and private
extensions, as long as they meet the requirements specified in
Section 6.
...
... IPP object MUST return a value whose type and value syntax conforms
to the requirement of the Model document as specified in Sections 3
and 4.
...
... Security Conformance Requirements ...
... IPP clients SHOULD support SSL3 access and non-SSL3
access. Note: This client requirement to support both means that
conforming IPP clients will be able to inter-operate with any IPP
Printer ...
... Socket
Layer" requirement as documented in the SSL3 specification [SSL].
For interoperability ...
... Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. ...