ISO/IEC TR 29181-2:2014

TECHNICAL ISO/IEC TR
REPORT 29181-2
First edition
2014-12-15
Information technology — Future
Network — Problem statement and
requirements —
Part 2:
Naming and addressing
Technologies de l’information — Réseaux du futur — Énoncé du
problème et exigences —
Partie 2: Dénomination et adressage
Reference number
©
ISO/IEC 2014
© ISO/IEC 2014
All rights reserved. Unless otherwise 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 below or ISO’s 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2014 – All rights reserved

Contents Page
Foreword .v
Introduction .vi
1 Scope . 1
2 Terms 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 Addressing 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 Performance . 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 Translation . 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
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.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 technology .21
© ISO/IEC 2014 – All rights reserved iii

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

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 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, in 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, 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 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 declarations 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 about ISO’s 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 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 composition
© ISO/IEC 2014 – All rights reserved v

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 provides 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 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 capabilities. 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 for 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 challenges 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, 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 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 planning, 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

TECHNICAL REPORT ISO/IEC TR 29181-2:2014(E)
Information technology — Future Network — Problem
statement and 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 characteristics 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 characteristics 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 future 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 Network 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 depending on its network usage and its characteristics.
2 Terms and 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
Note 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 from the network
© ISO/IEC 2014 – All rights reserved 1

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 mechanisms, 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
routing 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 point identification
EID
address used in the source 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 host’s “local” IP address.
[SOURCE: IETF RFC 6830 (LISP)]
2.7
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 lookup.
[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 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

2.9
EID-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
network 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 endpoint 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 interface.
[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
identifier
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) providing services/applications, or other entities
(e.g. physical or logical objects)
[SOURCE: ITU-T Y.2091 (2011)]
2.15
name
identifier of any entity (e.g. subscriber, network element) that may be resolved/translated into an address
[SOURCE: ITU-T Y.2091 (2011)]
3 Abbreviations
DNS Domain Name Service
EID Endpoint ID
© ISO/IEC 2014 – All rights reserved 3

ENUM E.164 NUmber Mapping
ID Identifier
LER Locator Edge Router
LOC Locator
NAPTR Naming Authority Pointer
NAS Naming and Addressing Scheme
NID Node ID
RLOR Routing Locator
4 Problem statements
4.1 Naming and Addressing in Network Operation
Naming and addressing are an engineering approach to computer networking, and are two closely
related core schemes in any network designs. Both names and addresses uniquely identify a host (or an
interface on the host) Naming is a scheme which gives identity to every computer or object connected
with the network or the party who is going to send or receive information from the network. -.
Addressing is a scheme which provides information on the point where receiver node is located in the
networks. It contains two mechanisms in a single address field; one is to define the location and another
is to specify how to find the addresses
At present, due the explosive growth of devices (especially mobile devices) and sites, scalability and
mobility become hot issues to the future network.
Communication networks (composed of telecom networks and computer networks) are designed to
deliver information from one point to another remote point or from one person to another person. In
order to conduct the delivery, the sender must know the other party’s name and where the other party
is located. Therefore, a network system must contain the naming and addressing schemes as the most
fundamental protocols so that the telecommunication networks and information systems know whom
and where to send the information effectively and efficiently.
4.2 NAS Types
4.2.1 Telecom Network Naming and Addressing Schemes — addressing mode
The first generation of network is the traditional telecom network which is typically known for telephone
system sending analogue signals through circuit switches and copper lines (or modernized fiber optical
lines). The phone network connects people at two ends of the communication line. Typically, E.164
numbering system has been being used. The phone numbers have two different characteristics. One is a
pure object identifier (a name), the other is function as an address.
For fixed line communication in first generation telecom networks, the fixed line telephone number is a
simply address mode. A phone number actually contains information about the location and path. Fixed
line telephone number is a system that mostly relies on addressing schemes. Furthermore, the E.164 is
regarded as an easy-to-remember well organized addressing scheme.
Note: For example, when people dial number 861088888888,the telecom switch instantly know the
identification of the party been called, but also knows which country (86) which city (10) and which
location (88888888) the party is located. The telephone address is fixed, but the person who was called
is unsure or not a requirement for communication.
4 © ISO/IEC 2014 – All rights reserved

Figure 1 — Addressing Mode NAS (Telecom network)
4.2.2 Telecom Network Naming and Addressing Schemes — naming mode
Other than the fixed line telecom networks, there is another type of network which sends communication
signals not through wire but through the air, mobile telecom network, in which E.164 numbering system
is also being used. In these kinds of networks, the same E.164 addressing does not provide the location
(or device name) and path at the same time. The address is just a device name only, while mobile telecom
network provides the path to the point where the device name is located using location management.
Name : 1088888888 (cell number)
Communication
Requester
Location Management
Figure 2 — Naming Mode NAS (Mobile Telecom network)
4.2.3 Computer Network Naming and Addressing Schemes — dual mode
Another generation of network is represented by Internet which mostly sending digital signals through
routers and fibre optical backbones to connect computer hosts. In computer networks (Internet), there
is also an address only communication mode. Internet address is composed of subnet prefix and host
Identification, where host identification is to locate the host, while subnet prefix is advertised to the
routers for routing path.
Since the internet address itself identifies a host or subnet, it faces some serious problems: (1) it does not
scale well due to the finite address size limitation, (2) due to the renumbering, occurring whenever the
network topologies change, more addresses are required, (3) the increased size of address field comes
to be heavy especially in the short data payload packet, and (4) the size-increased address is worse
human understandable.
Since even though the size of IPv4 address is 32 bits (relatively shorter than that of IPv6), it is not still
human friendly, the name is used and translated via DNS server. It means two or more names can be
assigned to the same host or site.
There is a dual mode NAS in telecommunication and information networks, in which both name and
address are required for information exchange. IP based computer networks are typical dual mode NAS.
IP network communication relies on domain name and IP addresses which are two different structures.
Most of the computer communication involves a process inputting a domain name, finding matches
involving a DNS server and converting into registered IP address.
© ISO/IEC 2014 – All rights reserved 5

Figure 3 — Dual Mode NAS (IP network)
4.2.4 .Computer Network Naming and Addressing Schemes — naming mode
While the current internet address identifies a subnet and a host in a same address field, the other
alternative is to separate host identification and subnet routing path. A same address format is separated
into two new numbering spaces: an host identifier (or name) and routing locator. Each host has a globally
unique ID(or EID) or name. Packet with EID is sent to the default locator router( Routing Locator, or ITR)
which then map EID to destination RLOC using EID-to-RLOC database. The packet will be traversed
from sending ITR to destination ETR using conventional routing mechanism. Finally the destination
ETR will deliver the packet to the destination host.
While Tunnel Routers manage and maintain the routing path among them using the conventional
routing mechanisms, the user only keeps the unique EID’s for communication. From user’s perspective,
the internet access network behaves like telecom network, while the internet core itself performs in a
conventional way.
Name: EID
(DNS Server)
Name : EID
Information
(ITR)
Requester
IP address: RLOC
Figure 4 — Naming Mode NAS (IP network)
4.2.5 Hybrid Network Naming and Addressing Schemes — Addressing mode
Even though internet is widely deployed network and popular to users, (mobile) telecom network is
another powerful and popular network as well. As long as two types of networks exist, it is natural to
combine them. There are two ways to implement combined networks: Access network can be either
telecom network or internet.
Since E.164 numbering is more user friendly and telecom network is more widely deployed up to date, a
telephone number can be used to identify a host, while the telephone number is translated to the IP address,
Note that the use of any/multicasting changes the one-to-one association of an address with a
physical endpoint
6 © ISO/IEC 2014 – All rights reserved

Name : ENUM
(DNS Server)
NAPTR
Name:(phone number)
Information
(PABX)
Requester
Name : (DNS Server)
Figure 5 — Addressing Mode NAS (Telecom network + IP network)
4.3 Problems in Network Integration
The brief reviews of network naming and addressing schemes indicate some problems for any attempt
to integrate existing networks.
— Telecom networks and computer networks have different addressing formats.
— Telecom networks and computer networks have different naming formats and different method in
addressing searching, transporting and forwarding.
— Many forms of naming and addressing in old networks make the network integration very complicated,
if not impossible. Even though technicians can find technologies to allow information shared among
the networks, it would be a huge effort to overhaul the existing network infrastructures.
— In order to avoid duplicating construction, sharing network resources, providing more and better
services, there is a tendency to integrate various kinds of networks into one system to allow information
seamlessly transmitted among networks. This is one of the objectives for Future Network.
— Considering the fact that IP networks have the potential to be a platform for future network
integration, its own problems should be fundamentally resolved. Otherwise, if they are spread into
other networks, it would bring more broad and severe problems.
4.4 NAS and Network Performance
In network designs, naming and addressing are not only essential and indispensable, but should also
occupy top priority in design schedules. Reasons are:
— Only after naming and addressing schemes are set, the whole architecture and other subsystems
such as router designs and application services can have a base to start work on.
— NAS structures may affect network performances
— NAS format influences network security
— NAS format influences accuracy for information delivery, etc.
© ISO/IEC 2014 – All rights reserved 7

4.5 Technical Limitations of Existing Naming and Addressing System
4.5.1 Central Registration Authority
The existing schemes require the Central registration authority, which maintains the control of
the key facilities of the Internet. This causes widely concerns of information security among the
international community.
4.5.2 Address Space exhaustion
IPv4 addressing space would be in danger of exhaustion due to the increased numbers of wireless devices,
always-on connections, or higher Internet adoption rates. The development and planned deployment of
IPv6 was regarded to be a long-term solution to this problem. However, its deployment is being delayed.
4.5.3 Name and Address Costs
The centralized domain name registration schemes create economic burdens for heavy IP address
users or nations.
4.5.4 Identifier-Locator Separation
IP address identifies an attachment point of an IP node for data delivery. Also It is used as a transport
layer session identifier, or even by some applications as node identifier. When host changes its IP address,
transport layer session breaks downs, and so does application on top of it.
4.5.5 Routing Table
Routing tables are becoming more and more bulky. It causes problems for management and maintenance
and increases router work load due to the increased number of sites, or possibly due to the increased
address size.
4.5.6 Vertical Addressing Structure
Centralized domain name system forms a vertical addressing structure with multiple redundancy or
bottlenecks which generate or increase heavy network congestion.
4.5.7 DNS Translation
The separation of domain names and IP addresses requires a Domain name to IP Address translation
process. Failure of DNS system may cause degradation of overall network performance.
4.5.8 Data Encryption
1)
IPv4 can only utilize data encryption (IPv6-IPSec ), but its addresses cannot be encrypted. It cannot
provide address confidentiality.
4.5.9 Address Category
IPv4 addresses can only provide “type” addresses, but do not provide “leveled” addresses which are
essential for high quality communication applications such as multi-media and real time information
transmissions.
1) Internet Protocol security (IPsec) uses cryptographic security services to protect communications over Internet
Protocol (IP) networks. IPsec supports network-level peer authentication, data origin authentication, data integrity,
and data confidentiality (encryption), and replay protection. The Microsoft implementation of IPsec is based on
Internet Engineering Task Force (IETF) standards.
8 © ISO/IEC 2014 – All rights reserved

4.5.10 Policy
Existing naming and addressing schemes lacks consideration or respect for geographical or national
boundary considerations. It creates problems for national government in network management and
information security. With additional information like geographical location, it may solve the current
problems like scalability, mobility, security, etc.
4.5.11 No Address in Native Language
IP domain names and addresses schemes do not provide language (such as Chinese, Korean, Japanese,
Russian, French, German, etc.) direct routing function, and have to rely on domain name conversion schemes.
However, current domain name conversion systems do not provide multiple language supports other
than English. It does not convert domain names based on other languages such as Chinese, Korean,
Japanese, Russian, French, German, Arabian, etc.
4.5.12 No Decimal Naming System
Current domain name conversion system does not provide all decimal name systems such as telephone
number, OID coding, mobile phone number, merchandise code, etc. Those numbers have to be inserted
into English domain names for conversion. It makes the process complicated, reduces data security, and
wastes network resources.
4.5.13 IPv6 Limitations
The major improvements of IPv6 are that it increases the length of IP addresses and expands address
resources. However, IPv6 does not make significant changes to other aspects of the IPv4 domain naming
and addressing structure. IPv6 still carries most of IPv4 problems in naming and addressing without
additional properties considering management, security and economic efficiency.
4.6 FN-NAS Development Challenges
4.6.1 Scalability
The rigid structure of centralized domain registration and hierarchical routing systems in IPv4-IPv6
prevent scalable networks from emerging. Scalability issues have mobility, multi-homing, renumbering,
provider independence routing, IPv6 impact, etc. on the today’s Internet architecture.
4.6.2 Security
The centralized domain name conversion and exposed IP addresses cause wide security concerns.
4.6.3 Mobility:
Current domain names and address protocols does not fit well into the future network environment
which will have more and more new communication devices or services such as mobile phones, RFID,
sensors, etc.
4.6.4 Quality of Service
The future network should support quality of service (QoS) from user and/or application perspectives.
The current IP-based network naming and addressing schemes needs to give more freedom to users and
more rooms of expansion for applications.
Even though it seems that QoS may not be directly related to NAS, QoS is mentioned here since it is
closely related the routing which is based on the addressing scheme.
© ISO/IEC 2014 – All rights reserved 9

4.6.5 Heterogeneity
Current domain names and address is incapable of providing name and address structural support for
accommodating the integrated networks.
4.6.6 Robustness:
The centralized domain name conversion and hierarchical network routing structures in current IP-
based networks is one of the causes for network congestion.
4.6.7 Customizability
Current naming and addressing schemes has too rigid policies and does not provide flexibility for
customized network communications.
4.6.8 Economic incentives
Current IP, especially IP domain names and addresses fee systems are too expensive for users. Better
designed naming and addressing structures also may produce economic incentives resulting from more
security and network efficiency.
5 Requirements
5.1 Content Description
This section describes technical requirements for FN-NAS design, including the following aspects:
— System Requirements: Including design concepts, system architecture, etc.;
— Special NAS requirements: including address format, network space, network communication
structure, routing, DNS, communication protocols, security, etc.
— Foreseeing mechanism: consider how the Future Network will change and benefit the human society
in the future.
— Compatibility Requirement: considering the emergence of FN-NAS will largely influence Future
Network’s basic technological designs including network space, network resources, communication
protocols, network architectural modes, security, QoS, routing protocols, upper layer protocols,
interoperability, it is desirable to have considerations and design to allow compatibility and
interoperability with existing networks.
— Others: Future network forward compatibility, future continuous development and testing and
compliance requirements.
Reasons for specifying these technical requirements are:
— From the perspective of network performance, demonstrative Future Network’s main characteristics
and capabilities, and to show a more clear future outlook for the development of Future Network.
— To point out objectives and directions for global research on new generation networks.
— To produce clear criteria for technical assessment in the next stage (proposal evaluation)
— To provide reference criteria for other research projects in Future Network program.
10 © ISO/IEC 2014 – All rights reserved

5.2 System Technical Requirements
5.2.1 System Integrity Requirement
From the perspective of system requirements, a complete NAS system should include at least the following
elements: naming, network space, network resources, addresses, network architecture, predictive
mathematic model, application, experiment, testing, etc. FN-NAS plan must have these elements. (From
historical experiences, some communication system may requirement single mode, such as naming only
or address only. If a proposal specifies only one mode, reasons must be given.
5.2.2 Intersystem Coherence Requirement
Besides having many sub-systems inside FN-NAS, it is also a part of a larger Future Network system. FN-
NAS should not only study and seek coherence among its sub-systems, but also should seek compatibility
and mutual support with the larger system. FN-NAS should consider how to be consistent, supportive,
benefit and interoperate with other systems in Future Network. FN-NAS should not produce conflict
with other systems and should avoid lowering the Future Network performance to meet the lower
requirements caused by deficient NAS design.
5.2.3 Structural Requirement
5.2.3.1 Addressing Structure
Future Network should have a complete new addressing structure with the following requirements:
— Good human-machine interface.
— Support conventional computing, future quantum computing, biological computing and other
computing language and various human languages based computing, and their compatibility and
interoperability.
— Protocol, addressing format and addressing solution schemes that would form a secure network
structure supporting and satisfying the concept of authentication before communication.
— A communication method mixing virtual layer-three circuit switching and Layer-four packet switching.
— Direct routing network architecture that will reduce carbon emission and produce greener networks.
— Fast and large capacity network services.
— Been able to interoperate with existing networks, allowing lower cost and seamlessly upgrade of
old networks, ability to maintain forward compatibility and potential for continuous development.
5.2.3.2 Reference Architecture
Existing networks mainly use two types of switching. In telecom networks (mainly telephone network)
circuit switching is the primary form. In computer networks (mainly Internet), the dominant protocol
is TCP/IP (simply referred as IP protocol) uses mainly packet switching. Future Network faces the task
of offering both data communication and video/voice communication in one network. To solve this
problem, Future Network should employ a transmission architecture model constructing a mixed layer
structure, using the layer three for virtual circuit switching to transmit video broadcasting and voice
communication while using the layer four structures for IP dada transmission.
5.2.3.3 A Network Structure mixing Virtual Circuit Switching and Packet Switching
Future network should be flexible so that it can be perceived as either packet switching network or
virtual network, as needed. It may provide both services by implementing two separate switching
mechanisms in the same intermediate node, or by implementing a new hybrid mechanism in a node.
© ISO/IEC 2014 – All rights reserved 11

Figure 6 — Network Model for the future (Note: M = mixed protocol)
5.2.3.4 Separation of Control Layer and Data Layer
Current internet has been using the layer such as control layer and data layer. However, in this
circumstance, delivery problem of control packet can occur in a situation of a flood of data packet by
DDOS attack or mobility of node. As a result, control layer and data layer must be separated.
5.2.4 Specific Technical Requirements
5.2.4.1 Addressing Technical Requirements
5.2.4.1.1 Address Format
Future Network NAS should consider having a new address system which will create a totally new
network space for the Future Network to exist, operate and expand.
A new address format is the foundation of a new address system. FN-NAS should have a new format of
addresses that is different from all existing NAS, but it should have the potential to allow compatibility
with existing address formats.
FN-NAS address format should go beyond of serving computer, but also make it more human friendly, to
allow users easier operate the addressing scheme while maintaining the efficiency for computing.
Digital Coding: The ten digits Arabian numerals are globally used language. Pure decimal encoding
is one of the most commonly used ways of expressing. Future Network should consider the need for
pure decimal coding from real applications such as commercial good coding, sensor coding, cell phone
number, geographic location, Space object location coding, molecule order coding for living bodies, etc.
12 © ISO/IEC 2014 – All rights reserved

Character coding: the FN-NAS address format could be in characters, such as Arabian numerals
...