ISO IEC 9834-2-1993 Information technology Open Systems Interconnection procedures for the operation of OSI registration authorities part 2 registration procedu.pdf

《ISO IEC 9834-2-1993 Information technology Open Systems Interconnection procedures for the operation of OSI registration authorities part 2 registration procedu.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 9834-2-1993 Information technology Open Systems Interconnection procedures for the operation of OSI registration authorities part 2 registration procedu.pdf（13页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL STANDARD ISO/IEC 9834-2 First edition 1993-l I-01 Information technology - Open Systems Interconnection - Procedures for the operation of OSI Registration Authorities - Part 2: Registration procedures for OSI document types Technologies de /information - lnterconnexion de systkmes ouve

2、rts (0.9) - Pro and b) the abstract syntactic structure of the OSI docu- ment types(s) specified; and c) a full specification of how to transfer OSI docu- ment types specified by the register entry, using any carrier-standard; and d) operations and support requirements which are specific to particul

3、ar OSI protocols concerned with the transfer of OSI documents (specific carrier- standards). 7 Requirements on carrier standards Any IS0 Standard or CCITT Recommendation which refer- ences OSI Document Type Registration for the purpose of OSI document transfer shall provide a) a field in its protoco

4、l capable of carrying any value of the ASN.l type object identifier (identifying an entry in a register), together with a field capable lSO/lEC 98342: 1993(E) of carrying any value of any ASN.l type (repre- senting parameters qualifying the register entry), and of indicating the absence of parameter

5、s; for those carrier-standards using ASN.l to define their protocol, an example of suitable fields would be: SEQUENCE (osidocument-typeregister-entry 0 IMPLICIT OBJECT IDENTIFIER, til)+X%llet.S l ANY OPTIONAL - to be filled by the - Am.1 type defined - for “PARAMETERS - in the register entry -) othe

6、r carrier-standards referencing OSI Document Type Registration shall define the way they carry these values; and b) for the transfer, using the OS1 Presentation Ser- vice defined in IS0 8822, of a series of presenta- tion data values carrying the document semantics, clearly identifying the delimitat

7、ion of the series, in- dependently of the contents of the presentation data value or its associated abstract syntax name (see IS0 8822); and c) optionally, the means of invoking certain oper- ations (specific to the carrier-standards) whose de- tailed definition is contained in the register entry. N

8、OTES 1 The register entry specifies the series of presentation data values to be transferred, the name of the associated abstract syntax (or syntaxes), and one or more transfer syntaxes. 2 The carrier-standard determines the placement of presentation data values on P-service primitives, and any use

9、which is made of synchronisation-points for checkpointing the transfer. Where the ASN.l field “ANY is used for “entry-parameters” in a) above, the register entry shall be referenced as the source of conformance requirements for the field “ANY”. 8 The form of OSI documents in transfer All register en

10、tries include specifications for the transfer of OSI documents as a series of presentation data values (see IS0 8822). The register entry defines: a) the possible contents of each presentation data value; and b) one or more abstract syntax names for the set(s) of presentation data values; and c) for

11、 each abstract syntax name, one or more as- sociated transfer syntax names (one of which is “mandatory” for claims of support for the OSI docu- ment type) with a definition of the associated encod- ings, each capable of transferring the semantics; and d) the series of such presentation data values n

12、eeded to transfer the document semantics. NOTES 1 It is not required that register entries define a series of presen- tation data values which are sufficient to identify the OSI document type. Such identification is performed by the OSI document type name and any associated parameters, which are car

13、ried separately. 2 It is not required that OSI document type definitions provide the means of recognising the last presentation data value in the OSI document. Such termination is provided by the carrier standard. 9 Contents of the register The register entries shall contain the information specifie

14、d in annex A. With the exception of the entry number, all infor- mation in the International Register shall be specified either explicitly in the register entry or by reference to an Intema- tional Standard, CCITT Recommendation, or other Intema- tional Registration. The entry number shall be specified explicitly. Annex A contains the clause number and headings of a register entry. The body of each clause specifies the con- tents of the corresponding clause in the register entry. NOTE - IS0 8571 (FTAM). IS0 8832 (JTM), and IS0 9069 (SDIF) contain examples of register entries. 3