XcmGlobalUniqueID
A management station or management agent specifies an object of type 'GlobalUniqueID' to uniquely label a client job request, a system administration request, or ANY other managed object (or set of managed objects) which are required to be unambiguously identified in a distributed network environment. An object of type 'GlobalUniqueID' SHALL be a textual string representation in standard 'dotted decimal' form of an OID. An object of type 'GlobalUniqueID' SHALL be composed of three mandatory sections (plus zero or more optional sections), as follows: nodeID.userID.seqID[[.subID1]...[.subIDn]] Each of the sections SHALL be separated by a dot ('.'). The three mandatory sections and any specified optional sections (in left to right order) SHALL be: 1) A globally unambiguous (within at least the network domain of the Requestor and Responder host systems) dotted decimal 'nodeID' of the Requestor host system which explicitly or implicitly labelled this managed object, either: a) A domain specific network layer address (eg, IETF IP address for 'nodeIDTypeIP'); OR b) A domain specific datalink MAC sublayer address (eg, ISO 8802-5 MAC address for 'nodeIDType88025'). 2) A locally unambiguous (within at least the Requestor and/or Responder host systems) dotted decimal 'userID' (ie, user identifier) of the user who explicitly or implicitly labelled this managed object. 3) A locally unambiguous (within at least the Requestor and/or Responder host systems) dotted decimal 'seqID' (ie, sequence identifier) assigned by the host system or user who explicitly or implicitly labelled this managed object. 4) A locally unambiguous (within at least the Requestor and/or Responder host systems) dotted decimal 'subID' (ie, sequence sub-identifier) assigned by the host system or user who explicitly or implicitly labelled this managed object. Usage: Conforming implementations MAY use one or more optional sections in an 'XcmGlobalUniqueID', for example to assign a sub-job identifier for job distribution services (e.g., fax to multiple destinations specified in the PDL of an input 'print' job - using an original 'xcmJobClientId' which is augmented by the server that splits up the destinations into separate jobs). Usage: Conforming implementations SHALL NOT specify BOTH the first ('nodeID') and second ('userID') sections as 'empty', but one OR the other section MAY take on an 'empty' value (see below). The third ('seqID') section SHALL NOT be 'empty'. Each of the three mandatory sections and any optional sections SHALL be composed of one mandatory and two optional subsections, as follows: sectionLength.sectionType.sectionValue Each of the subsections SHALL be separated by a dot ('.'). The three subsections (in left to right order) SHALL be: 1) A mandatory 'sectionLength', which specifies the decimal count of dotted decimal 'components' in the associated 'sectionValue' - this 'sectionLength' SHALL NOT be self-inclusive and SHALL NOT include the single 'component' of the 'sectionType' - a 'sectionLength' of decimal zero ('0') SHALL indicate an 'empty' section, and the associated two subsections ('sectionType' and 'sectionValue') SHALL be omitted. 2) An optional 'sectionType', selected from the standard 'sectionType' choices applicable to this section (below). 3) An optional 'sectionValue', specified as a dotted decimal string of 'components', each 'component' separated by a dot ('.'). The standard 'sectionType' choices (one set for each section) SHALL be as follows: 1) 'nodeIDType' -- for mandatory 'nodeID' section 1 : nodeIDTypeOther -- Other 2 : nodeIDTypeUnknown -- Unknown 11 : nodeIDTypeIP -- Internet IP 12 : nodeIDTypeCLNS -- OSI CLNS 13 : nodeIDTypeCONS -- OSI CONS 14 : nodeIDTypeDDP -- AppleTalk DDP 15 : nodeIDTypeIPX -- NetWare IPX 16 : nodeIDTypeNetBIOS -- IBM NetBIOS 31 : nodeIDType88023 -- ISO 8802-3 (Ethernet LAN) 32 : nodeIDType88024 -- ISO 8802-4 (TokenBus LAN) 33 : nodeIDType88025 -- ISO 8802-5 (TokenRing LAN) 34 : nodeIDType88026 -- ISO 8802-6 (SlottedRing MAN) 2) 'userIDType' -- for mandatory 'userID' section 1 : userIDTypeOther -- Other 2 : userIDTypeUnknown -- Unknown 11 : userIDTypeSystem -- System scope 12 : userIDTypeSubnet -- Subnet scope 13 : userIDTypeNetwork -- Network scope 14 : userIDTypeGlobal -- Global scope 3) 'seqIDType' -- for mandatory 'seqID' section 1 : seqIDTypeOther -- Other 2 : seqIDTypeUnknown -- Unknown 11 : seqIDTypeSystem -- System generated 12 : seqIDTypeProcess -- Process generated 13 : seqIDTypeThread -- Thread generated 4) 'subIDType' -- for optional 'subID' sections 1 : subIDTypeOther -- Other 2 : subIDTypeUnknown -- Unknown 11 : subIDTypeSystem -- System generated 12 : subIDTypeProcess -- Process generated 13 : subIDTypeThread -- Thread generated Usage: A 'seqID' of any type SHALL be system-unique. Usage: A 'seqID' of type 'seqIDTypeProcess' SHALL be prefixed (if necessary) by a system-unique dotted decimal 'processID'. Usage: A 'seqID' of type 'seqIDTypeThread' SHALL be prefixed (if necessary) by a system-unique dotted decimal 'threadID' (possibly itself prefixed by a system-unique 'processID'). Example: A request submitted from a client end system running the IETF Internet Protocol Suite (IPS), with an IP address of '13.240.128.21', without a specified dotted decimal 'userID', might include an 'xcmJobClientId' of the following form: '4.11.13.240.128.21.0.1.11.3045.1.11.23' [GlobalUniqueID] |---------1--------|2|----3----|---4---| [Sections] 1) The mandatory first section ('nodeID') consists of: a) 'sectionLength' of '4'; b) 'sectionType' of '11' ('nodeIDTypeIP'); and c) 'sectionValue' of '13.240.128.21' (4 components). 2) The mandatory second section ('userID') consists of: a) 'sectionLength' of '0' (ie, 'empty' section). 3) The mandatory third section ('seqID') consists of: a) 'sectionLength' of '1'; b) 'sectionType' of '11' ('seqIDTypeSystem'); and c) 'sectionValue' of '3045' (one component). 4) The optional fourth section ('subID') consists of: a) 'sectionLength' of '1'; b) 'sectionType' of '11' ('subIDTypeSystem'); and c) 'sectionValue' of '23' (one component).