BS ISO IEC TR 10730-1993 Information technology - Open systems interconnection - Tutorial on naming and addressing《信息技术 开放式系统互连 命名和定址指导》.pdf

《BS ISO IEC TR 10730-1993 Information technology - Open systems interconnection - Tutorial on naming and addressing《信息技术 开放式系统互连 命名和定址指导》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC TR 10730-1993 Information technology - Open systems interconnection - Tutorial on naming and addressing《信息技术 开放式系统互连 命名和定址指导》.pdf（43页珍藏版）》请在麦多课文档分享上搜索。

1、BSI BS*ISO/IEC TR*10730 73 W 1624669 0364245 846 W BRITISH STANDARD I Implementation of ISO/IEC TR 10730 : 1993 Information technology - Open Systems Interconnection - Tutorial on Naming and Addressing BS ISO/IEC TR 10730 : 1993 BSI BS*ISO/IEC TR*L0730 93 m Lb24bb9 03b424b 782 m BS ISO/IEC TR 10730

2、: 1993 National foreword This British Standard reproduces verbatim 1SO:IEC TR 10730 : 1993 and implements it as the UK national standard. This British Standard is published under the direction of the Information Systems Technology Standards Policy Committee whose Technical Committee IST2 1 has the r

3、esponsibility to: - aid enquirers to understand the text; - present to the responsible international committee any enquiiies on interpretation, or proposals for change, and keep UK interests informed; - monitor related international and European developments and promulgate them in the UK. KTE. Inter

4、national and European Standards, as well as oveneas standards, are available from BSI Sales Department. BSI. Linford Wood. Milton Keynes. MK14 6LE. Compliance with a British Standard does not of itself confer immunity from legal obligations. BSI BSSOIIEC TR*10730 93 m 1624669 0364247 619 m TECHNICAL

5、 REPORT ISO/IEC TR 10730 First edition 1993-04-1 5 Information technology - Open Systems Interconnection - Tutorial on Naming and Addressing Technologies de linforma tion - In terconnexion de systmes ouverts - Tutorial sur la dnomination et ladressage Reference number iSO/IEC TR 10730:1993(E) BSI BS

6、*ISO/IEC TRrL0730 93 Lb24669 0364248 555 W ISO/IEC TR 10730:1993(E) Contents Page Foreword . Introduction 1 scope 2 Normative references . 3 Abbreviations 4 IS0 7468-3 and its relationship with this technical report 5 Basic concepts . 5.1 General aspects of naming 5.2 Naming authorities and naming d

7、omains . 6 Architecture and naming 6.1 Decomposition of names . 6.2 Addressing information in OS1 services . 6.3 Addressing information in OS1 protocols . 6.4 Relatioship between Addressing Information. OSI-services and OSI-protocols 6.5 (N)-directory-functions 6.6 Layer Specific Aspects 7 OS1 envir

8、onment and names . 7.1 Naming related standards 7.2 Registration of names . 7.3 Directory Facilities . 8 Examples . 8.1 Entities and Addresses . 8.2 Application-association establishment 8.3 Examples of specific names forms published in OS1 standards . II IV 1 1 2 3 3 3 5 11 11 11 12 13 14 15 19 19

9、21 21 25 25 28 31 Q ISO/IEC 1993 All rights reserved . Unless otherwise specified. nor part of this publication may be reproduced or utilized in any form or by any means. electronic or mechanical. including photocopying and microfilm. without permission in writing from the publisher . ISO/IEC Copyri

10、ght Office Case postale 506 CH-1211 Genve 20 Switzerland Printed in Switzerland . II BSI BS*ISO/IEC TRrL0730 93 m Lb2Libb9 03bq2i.19 Li91 = ISO/IEC ISO/IEC TR 107301993(E) Foreword IS0 (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form t

11、he specialized system for worldwide standardization. National bodies that are members of IS0 or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. IS0 and IEC tech

12、nical committees collaborate in fields of mutual interest. Other international organizations, governmental and non governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and IEC have established a joint technical committee, ISOAEC JTC1. The

13、 main task of a technical committee is to prepare International Standards, but in exceptional circumstances, a technical committee may propose the publication of a Technical Report of one of the following types : - of an International Standard, despite repeated efforts ; type 1, when the required su

14、pport cannot be obtained for the publication - type 2, when the subject is still under technical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard ; - type 3, when a technical committee has collected data of a dif

15、ferent kind from that which is normally published as an International Standard (state of the art, for example). Technical reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical reports of typ

16、e 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful . ISOIEC TR 10730, which is a Technical Report of type 3, was prepared by Joint Technical Committee ISOIEC JTC 1, Information technology, Sub- Commitee SC 21, Information retrieval t

17、ransfer and management for open systems interconnection (09). BSI BS*ISO/IEC TR*L0730 93 m 1624669 0364250 LO3 = ISO/IEC TR 10730:1993(E) ISO/IEC Introduction This Technical Report has been developed in order to answer JTC1 member comments on IS0 7498-3 requesting to provide tutorial material to giv

18、e readers easy understanding. It has been decided to publish this tutorial as a Technical Report of Type 3 rather than as an annex to IS0 7498-3. In this Technical Report, the basic concepts of naming, including the relationship between (N)-entities, (N)-service-access-points and (N)- addresses are

19、developed in clause 5. A discussion of addressing information in services and protocols is then presented in clause 6, followed by layer- specific examples for the Application and Network layers. Registration authorities and directory facilities are then described in clause 7. Clause 8 presents a se

20、ries of examples covering relationships between layers and the effects of both initiating and recipient mechanisms in Open Systems altogether with examples of specific name forms published in OS1 standards. IV BSI BS*ISO/IEC TR*l7=93 3624669 0364253 O4T = TECHNICAL REPORT ISOAEC ISOAEC TR 10730:1993

21、 (E) Information technology - Open Systems Interconnection - Tutorial on Naming and Addressing 1 Scope This Technical Report introduces the main concepts and mechanisms which are defined in IS0 7498-3 to fulfil the needs for Naming and Addressing (N & A) objects in the Open Systems Interconnection E

22、nvironment (OSIE). It also includes the rationale for some of the important decisions made in the Naming and Addressing architecture. Although IS0 7498-3 does not define any specific forms of names and addresses, this Technical Report concludes with examples of specific name forms that have been def

23、ined in other published OS1 standards thereby showing how the concepts and mechanisms defined in IS0 7498-3 have been applied in the naming of certain objects. 2 References The following standards contain provisions which, through reference in this text, constitute provisions of this Technical Repor

24、t. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Technical Report are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. Members of IEC and IS0 m

25、aintain registers of currently valid International Standards. IS0 3166:1988, Codes for the representation of names of countries. IS0 6523:1984, Data interchange - Structures for the identification of organizations. IS0 7498:1984, Information processing systems - Open Systems Interconnection - Basic

26、Reference Model. IS0 7498-3:1989, Information processing systems - Open Systems Interconnection - Basic Reference Model - Part 3 : Naming and Addressing. IS0 8348 I Add.2:1988, 2 : Network Layer Addressing. ISOIIEC 8824:1990, Information technology - Open Systems Interconnection - Specification of A

27、bstract Syntax Notation One (ASN. 1). Information processing systems - Data communications - Network service definition - Addendum ISO/IEC TR 9577:1990, Information technology - Telecommunications and information exchange between systems - Protocol identification in the Network Layer. ISOIIEC 9594:1

28、990, Information technology - Open Systems Interconnection - The Directory. ISOIIEC 9834-1 :-1993, registration authorities - Part 1 : General procedures. Information technology - Open Systems Interconnection - Procedures for the operation of OS1 ISOIIEC 9834-6:-1993, registration authorities. Part

29、6 : Application-processes and application-entities. Information technology - Open Systems Interconnection - Procedures for the operation of OS1 ISO/IEC 10021 :I 990, Information processing systems - Text communication - Message Oriented Text Interchange Systems (mons). 1 BSI BS*ISO/IEC TRx10730 93 =

30、 Lb24669 0364252 TB6 ISO/IEC TR 10730:1993(E) 3 Abbreviations For the purpose of this Technical Report, the following abbreviations apply. AE AET AM AF I AFNOR ANSI AP ASN ATDF BSI ccm CL 03 Dcc DIS DSP ECMA Ewos FTAM IAF I ATA ICD ID1 IDP IPF JTCl MHS NADF NSAP OIT OS1 OSIE PAI PCI RA RAF m SAP SNP

31、A m 2 Application Entity Application-Entity Title Application-Entity Qualifier Authority and Format Identifier Association Franaise de Normalisation American National Standards Institute Application Process Abstract Syntax Notation Application Title Directory Facility British Standards Institute Com

32、it Consultatif International Tlgraphique et Tlphonique Connectionless (Mode) Connection (Mode) (previously referred to as Connection Oriented Mode) Data Country Code Draft International Standard Domain Specific Part European Computer Manufacturers Association European Workshop on Open Systems File T

33、ransfer, Access and Management Initiator Addressing Function International Airlines Transport Association International Code Designator Initial Domain Identifier Initial Domain Part Initiator PAI Function Joint Technical Committee 1 Message Handling System Network Address Directory Facility Network

34、Service Access Point Object Identifier Tree Open Systems Interconnection Open Systems Interconnection Environnment Protocol-Addressing- Information Protocol-Control-Information Quality of Service Registration Authority Recipient Addressing Function Relative Distinguished Name Service-Access-Point Su

35、b-network Point of Attachment Technical Report ISO/IEC ISOAEC BSI BS*ISO/IEC TR*:L0730 93 m l1624b69 0364253 912 m ISO/IEC TR 10730:1993(E) 4 IS0 7498-3 and its relationship with this Technical Report IS0 7498-3 states principles which are to be followed in any standard involving the need for identi

36、fication and I or location of relevant objects within the OSIE. For the purpose of locating objects, a specific form of name (an address) is used. Naming and addressing rules are essential to the success of OSI. In particular, it is a basic requirement that a real open system, however complex its in

37、ternal structure may be, shows a simple naming and addressing structure to the OSIE, SO that it may be easily accessible by any other real open system. IS0 7498-3 thus develops concepts which allow for the design of open systems which may have a very complex internal structure, while this complexity

38、 is not visible within the OSIE and the addressing scheme appears to be a very simple one from the view of other open systems. Such concepts preserve the principle of implementation independance (which is one of the basic rules of OSI), that is no real open system is required to know anything about

39、the implementation design of any other real open system, nor does any real open system impose such knowledge as a condition for communication using OS1 standards. This Technical Report is intended to explain how IS0 7498-3 achieves this task. It is not intended to replace the base standard. Where an

40、y conflict arise with statements made in this Technical Report and those in the referenced standards, the base standards are the definitive source. The examples shown in this Technical Report are for explanatory purposes only and are not prescriptive. 5 Basic concepts 5.1 General aspects of naming N

41、ames are linguistic constructs expressed in some language - .e. names are composed of a given set of symbols. A name is bound to one or more objects. Within the OS1 context names identify particular communication objects in the OSIE. Naming of the objects considered in the OSIE may have global or lo

42、cal significance. The objects for which naming has global significance include real open systems and the elements of the OSI-layers (e.g. (N)-entity, application-process) .The addresses of these objects also have global significance. The objects for which naming has local significance (.e. significa

43、nce within a given scope in an open system) include selectors, application-process-invocations and (N)-entity-invocations. 5.1.1 Types and properties of names 5.1.1.1 Primitive, descriptive and generic names A name is unambiguous within a given scope when it identifies one and only one object within

44、 that scope. The unambiguity of a name does not preclude the existence of synonymous names for an object - .e. more than one name can unambiguously identify an object. The concept of unambiguity may be extended to the case of the name of a set of objects. Examples - The name of a person (complete na

45、me) is unambiguous (generally ) within the context of the family cell, but may oten become ambiguous if this context is broadened. Other means are then necessary to ensure unambiguity, such as identity cardlpassport number, or social security number. - IATA (International Airlines Transport Associat

46、ion) flight numbers are, generally, an example of unambiguous names. - Within the OS1 context, network-addresses are, by definition, unambiguous, as their purpose is to identify a set of NSAPs at the end system and, as a result, to locate the end system itself, among all possible end systems attache

47、d to any subnetwork. Names can be categorised into primitive names and descriptive names. A primitive name is a name that identifies an object (which may be a set of objects) and which is assigned by a designated authority. The internal structure of the name is not required to be understood or to ha

48、ve significance to users of the name. A descriptive name is a name that identifies a set of one or more objects by means of a set of assertions concerning the properties of the objects of the set. The characteristic that distinguishes a descriptive name from a primitive name is that the structure of

49、 a descriptive name has significance to users of the name. 3 BSI BS*ISO/IEC TR*II0730 93 m II624669 0364254 859 m ISO/IEC TR 10730:1993(E) ISO/IEC A descriptive name may be incomplete, in that many objects satisfy all the assertions or it may be complete in that it serves to identify a single object (e.g. a descriptive name may identify several FTAM-application processes and thus be an incomplete descriptive name. A complete descriptive name would in that case identify just a single FTAM-application-process). A generic name is a primitive name or an incomplete de