By the way, you mean back to Octet String... right?
<!--StartFragment-->
hrPrinterDetectedErrorState OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
<!--EndFragment-->
Harry Lewis
IBM Printing Systems
harryl@us.ibm.com
lpyoung@lexmark.com on 07/21/99 04:17:28 PM
To: pmp@pwg.org
cc:
Subject: PMP> Printer MIB Change Proposals
From: Lloyd Young@LEXMARK on 07/21/99 06:17 PM
To: pmp@pwg.org
cc:
Subject: Printer MIB Change Proposals
Both Printer MIB change proposals were accepted by a consensus of the
Printer MIB Working Group.
My plan is to have a revised Printer MIB available around August 16th
with these two changes incorporated as well as other minor editorial
changes (including the change of hrPrinterDetectedErrorState back to BITS).
1. In the PrtAlertCodeTC Textual Convention, Media Path Device Group, the
following will be added:
--------------------------------------------------
"cannotDuplexMediaSelected(1304)"
--------------------------------------------------
2. In the PrtChannelTypeTC Textual Convention, the following will be added:
--------------------------------------------------
chIPP(44),
-- Internet Printing Protocol (IPP)
-- (IPP/1.0 - see RFC 2565/2566)
-- (also applies to all future versions of IPP)
--
-- IPP Printer URI
-- Keyword: URI
-- Syntax: URI (Unicode UTF-8 per RFC 2396)
-- Status: Mandatory
-- Multiplicity: Single
-- Default: not applicable
-- Description: URI of this IPP Printer within the
-- Internet naming scope. Unicode UTF-8 [RFC-2279]
-- string with hexadecimal escapes for any non-ASCII
-- characters (per RFC 2396).
-- Conformance: An IPP Printer shall list all IPP
-- URI it supports (one per IPP Channel entry).
-- If a URI contains the 'http:' scheme, it MUST
-- have an explicit port.
-- See: [RFC-2279], [RFC-2396], [RFC-2565],
-- [RFC-2566].
--
-- IPP Printer Client Authentication
-- Keyword: Auth
-- Syntax: Keyword
-- Status: Optional
-- Multiplicity: Single
-- Default: 'none'
-- Description: A client authentication mechanism
-- supported for this IPP Printer URI:
-- 'none'
-- no client authentication mechanism
-- 'requesting-user-name'
-- authenticated user in 'requesting-user-name'
-- 'basic'
-- authenticated user via HTTP Basic mechanism
-- 'digest'
-- authenticated user via HTTP Digest mechanism
-- 'certificate'
-- authenticated user via certificate mechanism
-- Conformance: An IPP Printer should list all IPP
-- client authentication mechanisms it supports
-- (one per IPP Channel entry).
-- See: [IPP-MOD-11], [IPP-PRO-11].
--
-- IPP Printer Security
-- Keyword: Security
-- Syntax: Keyword
-- Status: Optional
-- Multiplicity: Single
-- Default: 'none'
-- Description: A security mechanism supported for
-- this IPP Printer URI:
-- 'none'
-- no security mechanism
-- 'ssl3'
-- SSL3 secure communications channel protocol
-- 'tls'
-- TLS secure communications channel protocol
-- Conformance: An IPP Printer should list all IPP
-- security mechanisms it supports (one per IPP
-- Channel entry).
-- See: [RFC-2246], [RFC-2566], [IPP-MOD-11].
--
-- IPP Printer Protocol Version
-- Keyword: Version
-- Syntax: Keyword
-- Status: Optional
-- Multiplicity: Multiple
-- Default: '1.0'
-- Description: All of the IPP protocol versions
-- (major.minor) supported for this IPP Printer URI:
-- '1.0'
-- IPP/1.0 conforming Printer
-- '1.1'
-- IPP/1.1 conforming Printer
-- Conformance: An IPP Printer should list all IPP
-- versions it supports (all listed in each IPP
-- Channel entry).
-- An IPP Client should select the highest numbered
-- version that the client supports for use in all
-- IPP Requests (for optimum interworking).
-- See: [RFC-2566], [IPP-MOD-11].
--
-- References:
-- [RFC-2246] TLS/1.0 Protocol
-- section 9 'Mandatory Cipher Suites'
-- [RFC-2279] UTF-8 Transform of ISO 10646
-- section 2 'UTF-8 Definition'
-- [RFC-2396] Generic URI Syntax
-- section 2.1 'URI and non-ASCII characters'
-- [RFC-2566] IPP/1.0 Model and Semantics
-- section 4.1.5 'uri' (attribute syntax)
-- section 4.4.1 'printer-uri-supported'
-- section 4.4.2 'uri-security-supported'
-- section 4.4.14 'ipp-versions-supported'
-- section 5 'Conformance'
-- [RFC-2565] IPP/1.0 Encoding and Transport
-- section 3.3 'Version-number'
-- section 5.1 'Using IPP with SSL3'
-- section 9 'Appendix A: Protocol Examples'
-- [IPP-MOD-11] IPP/1.1 Model and Semantics
-- <draft-ietf-ipp-model-v11-04.txt>
-- (work-in-progress)
-- section 4.4.2 'uri-authentication-supported'
-- section 4.4.3 'uri-security-supported'
-- [IPP-PRO-11] IPP/1.1 Encoding and Transport
-- <draft-ietf-ipp-protocol-v11-03.txt>
-- (work-in-progress)
-- section 3.3 'Version-number'
-- section 5 'IPP URL Scheme'
-- section 9 'Appendix A: Protocol Examples'
--------------------------------------------------
------------------------------------------------------------
Lloyd Young
Manager, Alliances and Complementary Project Development
Consumer Printer Division Lexmark International, Inc.
Dept. C88M/Bldg. 005-1 740 New Circle Road NW
email: lpyoung@lexmark.com Lexington, KY 40550-0001
Phone: (606) 232-5150 Fax: (630) 982-4032