BS PD ISO IEC TR 29181-2-2014 Information technology Future Network Problem statement and requirements Naming and addressing《信息技术 未来网络 问题陈述和需求 命名和寻址》.pdf

《BS PD ISO IEC TR 29181-2-2014 Information technology Future Network Problem statement and requirements Naming and addressing《信息技术 未来网络 问题陈述和需求 命名和寻址》.pdf》由会员分享，可在线阅读，更多相关《BS PD ISO IEC TR 29181-2-2014 Information technology Future Network Problem statement and requirements Naming and addressing《信息技术 未来网络 问题陈述和需求 命名和寻址》.pdf（46页珍藏版）》请在麦多课文档分享上搜索。

1、BSI Standards Publication Information technology Future Network Problem statement and requirements Part 2: Naming and addressing PD ISO/IEC TR 29181-2:2014National foreword This Published Document is the UK implementation of ISO/IEC TR 29181-2:2014. The UK participation in its preparation was entrus

2、ted to Technical Committee IST/6, Data communications. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The Br

3、itish Standards Institution 2014. Published by BSI Standards Limited 2014 ISBN 978 0 580 75288 9 ICS 35.100.30 Compliance with a British Standard cannot confer immunity from legal obligations. This Published Document was published under the authority of the Standards Policy and Strategy Committee on

4、 31 December 2014. Amendments/corrigenda issued since publication Date Text affected PUBLISHED DOCUMENT PD ISO/IEC TR 29181-2:2014Information technology Future Network Problem statement and requirements Part 2: Naming and addressing Technologies de linformation Rseaux du futur nonc du problme et exi

5、gences Partie 2: Dnomination et adressage TECHNICAL REPORT ISO/IEC TR 29181-2 First edition 2014-12-15 Reference number ISO/IEC TR 29181-2:2014(E) ISO/IEC 2014 PD ISO/IEC TR 29181-2:2014 ii ISO/IEC 2014 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2014 All rights reserved. Unless otherwi

6、se specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address bel

7、ow or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/IEC TR 29181-2:2014(E) PD ISO/IEC TR 29181-2:2014 ISO/IEC TR 29181-2:2014(E

8、)Contents Page Foreword v Introduction vi 1 Scope . 1 2 T erms and Definitions 1 3 Abbreviations. 3 4 Problem statements 4 4.1 Naming and Addressing in Network Operation . 4 4.2 NAS Types 4 4.2.1 Telecom Network Naming and Addressing Schemes addressing mode . 4 4.2.2 Telecom Network Naming and Addre

9、ssing Schemes naming mode 5 4.2.3 Computer Network Naming and Addressing Schemes dual mode . 5 4.2.4 .Computer Network Naming and Addressing Schemes naming mode 6 4.2.5 Hybrid Network Naming and Addressing Schemes Addressing mode 6 4.3 Problems in Network Integration . 7 4.4 NAS and Network Performa

10、nce 7 4.5 Technical Limitations of Existing Naming and Addressing System . 8 4.5.1 Central Registration Authority 8 4.5.2 Address Space exhaustion . 8 4.5.3 Name and Address Costs. 8 4.5.4 Identifier-Locator Separation . 8 4.5.5 Routing Table 8 4.5.6 Vertical Addressing Structure . 8 4.5.7 DNS Trans

11、lation 8 4.5.8 Data Encryption 8 4.5.9 Address Category 8 4.5.10 Policy 9 4.5.11 No Address in Native Language 9 4.5.12 No Decimal Naming System . 9 4.5.13 IPv6 Limitations . 9 4.6 FN-NAS Development Challenges . 9 4.6.1 Scalability . 9 4.6.2 Security 9 4.6.3 Mobility: 9 4.6.4 Quality of Service . 9

12、 4.6.5 Heterogeneity 10 4.6.6 Robustness: .10 4.6.7 Customizability 10 4.6.8 Economic incentives 10 5 Requirements .10 5.1 Content Description .10 5.2 System Technical Requirements .11 5.2.1 System Integrity Requirement 11 5.2.2 Intersystem Coherence Requirement .11 5.2.3 Structural Requirement 11 5

13、.2.4 Specific Technical Requirements 12 5.2.5 Complementary Technical Requirements .16 5.2.6 Extension Technical Requirement .16 5.2.7 Evaluation and Test Requirement 17 5.2.8 Infrastructure Requirement 17 Annex A (informative) FN-NAS Standardization Plan 18 Annex B (informative) Current Internet te

14、chnology .21 ISO/IEC 2014 All rights reserved iii PD ISO/IEC TR 29181-2:2014 ISO/IEC TR 29181-2:2014(E)Annex C (informative) Current Internet Views .24 Annex D (informative) Packet Transferring using Geographical addressing scheme .27 Bibliography .33 iv ISO/IEC 2014 All rights reserved PD ISO/IEC T

15、R 29181-2:2014 ISO/IEC TR 29181-2:2014(E) Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development

16、 of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, i

17、n liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives

18、, Part 1. In particular the different approval criteria needed for the different types of document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives). Attention is drawn to the possibility that some of the

19、elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarat

20、ions received (see www.iso.org/patents). Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information abo

21、ut ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 6, Telecommunication and information exchange between systems. ISO/IEC

22、 TR 29181 consists of the following parts, under the general title Information technology Future Network Problem statement and requirements: Part 1: Overall aspects Part 2: Naming and addressing Part 3: Switching and routing Part 4: Mobility Part 5: Security Part 6: Media transport Part 7: Service c

23、omposition ISO/IEC 2014 All rights reserved v PD ISO/IEC TR 29181-2:2014 ISO/IEC TR 29181-2:2014(E) Introduction This part of ISO/IEC TR 29181 is the second part of this Technical Report on Future Network Problem statement and requirements developed by ISO/IEC JTC1 SC6. As ISO/IEC TR 29181-1 provide

24、s an overall perspective of the missions and requirements of the FN project, this part of ISO/IEC TR 29181 focuses on the issue of naming and addressing. The objective of this part of ISO/IEC TR 29181 is to discuss how to develop a clean slate designed new naming and addressing schemes (NAS) to help

25、 FN project achieve its lofty ambitions. Naming and addressing schemes are the cornerstones of telecommunication networks and information systems. NAS designs not only provide fundamental building blocks for network designs, but can also influence network characteristics, performance, and capabiliti

26、es. Therefore, NAS needs to be among the top priorities of network design projects. NAS plays an even more important role in FN. As a project aimed at designing a totally new network with a clean slate design approach, FN has to produce a clean slate designed naming and addressing scheme. The need f

27、or new naming and addressing systems were based from the gaps between the existing NAS systems and the rising future demands of new applications which produces many technical challenges the existing NAS systems cannot provide satisfactory solutions. This Technical Report summarizes some of the chall

28、enges and also offers some new directions for future research on NAS standardization. However, as the new network has to produce a network structure which would allow information to flow more smoothly, fast, and securely among various networks with various kinds of naming and addressing structures,

29、designing a new NAS which would not only function within the new system, but also interoperate with other naming and addressing systems (such as old systems like DNS or telecom networks and new systems such as RFID and sensor networks) is a very challenging task. Considering evolutionary approaches

30、which seek to engage gradual improvement with available technologies while protecting the integrity of overall structure of old networks, a new scheme will produce a totally new naming and addressing scheme. A clean slate design needs thorough analysis, full understanding of the demand, careful plan

31、ning, and collective work. In order to achieve the maximum benefits and find the best solution, a strategic planning document is needed before specific schemes are standardized.vi ISO/IEC 2014 All rights reserved PD ISO/IEC TR 29181-2:2014 Information technology Future Network Problem statement and

32、requirements Part 2: Naming and addressing 1 Scope This part of ISO/IEC TR 29181 describes the general characteristics of Future Network naming and addressing schemes, including problem statements, requirements, design objectives, gap analysis, and development directions. Problem Statements: The cha

33、racteristics and problems of existing NAS in existing network will be discussed. Technical Challenges: A list of major technical challenges to assure that the FN-NAS will be able to provide solid technical support from the base level to meet the objectives of FN. Requirements: The general characteri

34、stics of Future Network are discussed and their impact on NAS design. Gap analysis: Examines the gap between existing network NAS and future network performance expectations. In Annex A, FN-NAS Standardization Plan, design objectives, gap analysis, development guidance, chronological scenarios for f

35、uture network naming, and addressing guidance are described in detail. Though this part of ISO/IEC TR 29181 mainly presents a list of up-to-date surveyed problems, requirements, and plausible techniques for Future Network, it does not mean that all of those would be applied to a single Future Networ

36、k in common, since the naming and addressing scheme can be applied to the various networks, such as global networks, local networks, access networks, mobile networks, etc. If a specific Future Network is designed and implemented, some appropriate parts of ISO/IEC TR 29181 would be considered dependi

37、ng on its network usage and its characteristics. 2 T erms a nd Definitions For the purposes of this document, the following terms and definitions apply. 2.1 Future Network naming and addressing schemes system of mechanisms to provide identify and locate for information exchange in Future Network Not

38、e 1 to entry: The system may design new naming schemes, new addressing schemes or an integrated scheme that combines identification and location. 2.2 naming scheme which gives identity to every computer or object connected with the network or the party who is going to send or receive information fro

39、m the network TECHNICAL REPORT ISO/IEC TR 29181-2:2014(E) ISO/IEC 2014 All rights reserved 1 PD ISO/IEC TR 29181-2:2014 ISO/IEC TR 29181-2:2014(E) 2.3 addressing scheme which provides information on the point, where sender or receiver is located in the networks Note 1 to entry: It contains two mecha

40、nisms, one is to define the location (address format) and another is to specify how to find the addresses. 2.4 naming authority pointer NAPTR type of DNS resource record, used in particular (but not only) which is used for E.164 telephone number to URI resolution SOURCE: IETF RFC 3403(NAPTR) 2.5 rou

41、ting locator RLOC sddress of an ETR Note 1 to entry: Typically, RLOCs are numbered from topologically- aggregatable blocks that are assigned to a site at each point to which it attaches to the global Internet. SOURCE: IETF RFC 6830 (LISP) 2.6 end p oi nt ident i f ic at ion EID address used in the s

42、ource and destination fields of the most inner LISP header of a packet Note 1 to entry: The host obtains a destination EID the same way it obtains a destination address today. The source EID is obtained via existing mechanisms used to set a hosts “local” IP address. SOURCE: IETF RFC 6830 (LISP) 2.7

43、ingress tunnel router ITR router that resides in a LISP site Note 1 to entry: Packets sent by sources inside of the LISP site to destinations outside of the site are candidates for encapsulation by the ITR. The ITR treats the IP destination address as an EID and performs an EID-to-RLOC mapping looku

44、p. SOURCE: IETF RFC 6830 (LISP) 2.8 egress tunnel router ETR router that accepts an IP packet where the destination address in the “outer” IP header is one of its own RLOCs Note 1 to entry: In general, an ETR receives LISP-encapsulated IP packets from the Internet on one side and sends de-capsulated

45、 IP packets to site end-systems on the other side. ETR functionality does not have to be limited to a router device. A server host can be the endpoint of a LISP tunnel as well. SOURCE: IETF RFC 6830 (LISP)2 ISO/IEC 2014 All rights reserved PD ISO/IEC TR 29181-2:2014 ISO/IEC TR 29181-2:2014(E) 2.9 EI

46、D-to-RLOC database global distributed database that contains all known EID-prefix to RLOC mappings Note 1 to entry: Each potential ETR typically contains a small piece of the database: the EID-to-RLOC mappings for the EID prefixes “behind” the router. SOURCE: IETF RFC 6830 (LISP) 2.10 locator LOC ne

47、twork layer topological name for an interface or a set of interfaces Note 1 to entry: LOCs are carried in the IP address fields as packets that traverse the network SOURCE: ITU-T Y.2015 (2011) 2.11 node ID identifier used at the transport and higher layers to identify the node as well as the endpoin

48、t of a communication session Note 1 to entry: A node ID is independent of the node location as well as the network to which the node is attached so that the node ID is not required to change even when the node changes its network connectivity by physically moving or simply activating another interfa

49、ce. SOURCE: ITU-T Y.2015 (2011) 2.12 ID/LOC mapping storage function stores the mapping of NGN identifiers, node IDs, and LOCs SOURCE: ITU-T Y.2015 (2011) 2.13 address identifier for a specific termination point and is used for routing to this termination point SOURCE: ITU-T Y.2091 (2011) 2.14 ident i f ier series of digits, characters, and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), network entity(ies)