⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc941.txt

📁 RFC 相关的技术文档
💻 TXT
📖 第 1 页 / 共 5 页
字号:
    If the original binary field contained an odd number of octets,  the    final  octet  is  converted  to  a  number  in  the  range 0-255 and    represented as three decimal digits (000-255);   e)  when the IDI format is "Local", representing an  ISO  646       character syntax DSP using the technique described in Clause       8.3.1 (e); and   f)  when  the  IDI  format is "Local", representing a National       Character syntax DSP using the technique described in Clause       8.3.1 (f).8.4  Maximum Network Address Length The maximum length of the NSAP address for each of the combinations of IDI abstract syntax is given in Table 8-5 both the decimal concrete syntax and the binary concrete syntax.ISO/TC-97/SC-6                                                 [Page 26]RFC 941                                                       April 1985Network Layer Addressing                                                    Table 8-5:  Maximum NSAP Address Lengths    ________________________________________________________________    |             | DSP Abstract  |  Binary DSP     | Decimal DSP  |    |  IDI Format |   syntax      | concrete syntax concrete syntax|    |_____________|_______________|_________________|______________|    |             |   Decimal     |   20 octets     |  40 digits   |    |   X.121     |   Binary      |   17 octets     |  39 digits   |    |             |               |                 |              |    |             |   Decimal     |   20 octets     |  40 digits   |    |  ISO DCC    |   Binary      |   17 octets     |  40 digits   |    |             |               |                 |              |    |             |   Decimal     |   20 octets     |  40 digits   |    |    F.69     |   Binary      |   17 octets     |  40 digits   |    |             |               |                 |              |    |             |   Decimal     |   20 octets     |  40 digits   |    |    E.163    |   Binary      |   17 octets     |  39 digits   |    |             |               |                 |              |    |             |   Decimal     |   20 octets     |  40 digits   |    |    E.164    |    Binary     |   18 octets     |  40 digits   |    |             |               |                 |              |    |             |   Decimal     |   20 octets     |  40 digits   |    | ISO 6523-ICD|   Binary      |   16 octets     |  39 digits   |    |             |               |                 |              |    |             |   Decimal     |   20 octets     |  40 digits   |    |   LOCAL     |   Binary      |   16 octets     |  40 digits   |    |             | Character     |   20 octets     |  40 digits   |    |             |National Char. |   15 octets     |  37 digits   |    |_____________|_______________|_________________|______________|                                      Note:  These values assume a National Character representation of one  character as two binary octets (see clause 8.2.3). From this table it is clear that: a)  the maximum length of an NSAP address in its binary concrete syntax     is 20 octets; and b)  the maximum length of an NSAP address in its decimal concrete     syntax is 40 digits. A Network Layer protocol which is capable of conveying a string of variable length with a maximum length of either 20 binary octets or 40 decimal digits is capable of encoding the full semantic content of any Network Address.ISO/TC-97/SC-6                                                 [Page 27]RFC 941                                                       April 1985Network Layer Addressing9  CHARACTER BASED DSP ALLOCATIONAn authority may choose to allocate NSAP addresses with the DSP in aNational Character syntax. In such cases, the allocating authority mustdefine and publish the mapping of the National Character syntax toeither a binary abstract syntax or a decimal abstract syntax. Note:  It is recommended that this mapping be done by reference to the ISO Register of Character Sets, which is maintained by the European Computer Manufacturers Association (ECMA) acting as a registration authority according to ISO 2375, "Procedure for the Registration of Escape Sequences".In the case where the authority defines and publishes the mapping of theNational Character set to a binary abstract syntax, the result must berepresentable in either one or two octets per National Character.  Inthis case, the resulting DSP is considered to be based on the Binaryabstract syntax. AFI values from Table 8-2 and the mapping to binary anddecimal concrete syntaxes are based on the binary abstract syntax.In the case where the authority defines and publishes the mapping of theNational Character set to a decimal abstract syntax, the result must berepresentable in up to five decimal digits per National Character.  Inthis case, the resulting DSP is considered to be based on the decimalabstract syntax. AFI values from Table 8-2 and the mapping to binary anddecimal concrete syntaxes are based on the decimal abstract syntax. Note:  The ability to base DSP allocation on National Character sets allows DSP allocation based on international character sets. This may simplify address assignment in some cases, and may facilitate representation of NSAP address in humanly-readable form.  Nevertheless, NSAP addresses should not be confused with Application Layer entity titles.  NSAP addresses are not intended to provide the same degree of human-readable,  user-friendly  naming  and  addressing capabilities as may be expected in Application Layer entity titles.ISO/TC-97/SC-6                                                 [Page 28]RFC 941                                                       April 1985Network Layer Addressing10  REFERENCE PUBLICATION FORMATSReference publication formats are defined  to  allow  unambiguousrepresentation of NSAP addresses in both written and oral communication.10.1  Decimal Reference Publication Format The Decimal reference publication form (DRPF) consists of a string of up to 40 decimal digits.  The DRPF is the written inscription of the decimal concrete syntax defined in clause 8.3.2.10.2  Hexadecimal Reference Publication Format The Hexadecimal reference publication format (HRPF) consists of the symbol "/" (solidus) followed by a string of up to 40 hexadecimal digits. The HRPF is the written inscription of the binary concrete syntax defined in clause 8.3.1, using two hexadecimal digits ranging from 00 through FF to represent each binary octet.ISO/TC-97/SC-6                                                 [Page 29]RFC 941                                                       April 1985Network Layer AddressingANNEX A - NETWORK ENTITY TITLESThis Annex is an integral part of the Addendum.In order to perform routing functions and to distribute Network Layermanagement information concerning routing among Network entities, it isnecessary to be able to unambiguously identify Network entities in endsystems and intermediate systems.  The Reference Model (ISO 7498)provides a definition of the concept of an (N)-entity title, which maybe used to permanently and unambiguously identify a Network entity in anend system or intermediate system.Any authority responsible for allocating addresses to NSAPs may choosealso to allocate Network entity titles. One of the ways in which thiscan be done is to use the principles and mechanisms defined in thisAddendum for allocating Network addresses. When this approach is taken,a Network entity title has the same abstract syntax as an NSAP address.A value may be allocated as a Network entity tile only if it has notbeen allocated as an NSAP address.ISO/TC-97/SC-6                                                 [Page 30]RFC 941                                                       April 1985Network Layer AddressingANNEX B - NSAP ADDRESS ALLOCATIONThis Annex is not an integral part of the Addendum.The division of the global Network addressing domain according to theIDI formats described in clause 8.2.1.2 may be illustrated by thefollowing figure.  The numbers adjacent to each line in the figure areAFI values, as defined in Table 8-2 of clause 8.2.1.2.         Figure B-1 - NSAP Address Allocation on attached page. 00-09          Reserved - will not be allocated 10-35          Reserved for future allocation by joint agreement of ISO                and CCITT 36-37          X.121 38-39          ISO DCC 40-41          F.69 42-43          E.163 44-45          E.164 46-47          ISO ICD 48-51          Local 52-59          Reserved for future allocation by joint agreement of ISO                and CCITT 60-69          Allocated for assignment by ISO 70-79          Allocated for assignment by CCITT 80-99          Reserved for future allocation by joint agreement of ISO                and CCITT ISO/TC-97/SC-6                                                 [Page 31]RFC 941                                                       April 1985Network Layer AddressingANNEX C - RATIONALESThis annex contains tutorial and explanatory material, and is not anintegral part of the Addendum.C.1  IDI FORMATS (Clause 8.2.1.2) The rationale for the use of the specific IDI formats identified in Clause 8.2.1.2 is to allow the allocation and assignment of NSAP addresses to be based on existing, well-established network numbering plans and organization-identification standards. The CCITT numbering plans are included so as to allow for the designation of the organization to which a number is assigned as an authority for the assignment of NSAP addresses. If the organization identified by a particular number from one of these plans chooses not to define any further sub-addressing beyond that number, then the number itself constitutes an NSAP address when it is used in the OSI environment. This flexibility allows number allocated from the four CCITT numbering plans identified in Clause 8.2.1.2 to be used directly as NSAP addresses, with the addition of nothing more than the initial AFI digits that identify the plan. The ISO DCC format is included so as to allow for the designation, where permitted by national regulations, of the organization that represents a country in ISO (or an appropriately sponsored organization) as an authority for the assignment of geographically-based NSAP addresses. The way in which addresses are allocated and assigned in the ISO DCC format is determined by the designated organization, which might, for example, be the national standards body that represents a country in ISO. The ISO 6523-ICD format is included so as to allow for the designation, where permitted by national regulations, of an organization that may or may not be tied to a particular country as an authority for the assignment of NSAP addresses according to the hierarchy appropriate for that organization (which may not be based on geographical or national boundaries).  The way which addresses are allocated and assigned in the ISO 6523-ICD format is determined by the designated organization, which might, for example, be the United Nations World Health Organization. The Local format is included so as to allow for proprietary or other non-standard network addressing schemes to coexist with the standard OSI network addressing scheme.  Use of the Local format for  these non-standard address ensures that they cannot be confused with standard OSI network addresses. This capability will be useful in the evolution of existing networks to OSI, and for the accommodation of non-OSI addressing schemes that may be used in 

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -