|
|
Description:
|
ppmPortServiceNameOrURI OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..255))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The service name or URI for this port, specified in UTF-8 (RFC
3629), in the locale specified by 'ppmGeneralNaturalLanguage'.
The service name is typically a queue name.
Compatibility Note: At the time of publication of this MIB,
the Microsoft tools do not support LPR queue names longer than
32 characters. Network administrators SHOULD NOT assign longer
LPR queue names, to prevent interworking problems.
Compatibility Note: At the time of publication of this MIB,
IETF URI Generic Syntax (RFC 3986) requires that all non-ASCII
characters be percent-encoded, while IETF Internationalized
Resource Identifiers (RFC 3987) permits native UTF-8 resource
identifiers and supplies mappings to and from standard URI.
In order to support current use of IRI and possible future
evolution of URI (in a successor to RFC 3986) to allow non-ASCII
characters, this object has been defined with a syntax of UTF-8
(RFC 3629).
Examples of well-formed service URI for print protocols
include:
- 'lpr://foo.example.com/public-printer' (where 'public-
printer' is the LPR queue name portion)
and
- 'ipp://bar.example.com/printer/fox'
If this object is non-empty, then it SHOULD NOT conflict with a
the default (e.g., IANA-registered) or explicit transport target
port specified in 'ppmPortProtocolTargetPort'. In case of
conflict, the URI value in 'ppmPortServiceNameOrURI' is
authoritative (e.g., 'ipp://example.com:631/~smith/printer').
If this object is empty and 'ppmPortProtocolType' is
'chLPDServer(8)', the LPR queue name MUST default to 'LPR'."
REFERENCE
"IETF Line Printer Daemon Protocol (RFC 1179).
'lpr:' URL scheme in IANA-registered SLP Printer Schema at
http://www.iana.org/assignments/svrloc-templates/
printer-uri in LDAP Printer Schema (RFC 3712).
IPP/1.1: IPP URL Scheme (RFC 3510).
printer-uri-supported in IPP/1.1 (RFC 2911)."
DEFVAL { ''H } -- no service name or URI
|
|
|
|
