ISO/IEC TR 29181-1:2012

Information technology - Future Network - Problem statement and requirements - Part 1: Overall aspects

ISO/IEC TR 29181-1:2012 describes the definition, general concept, problems and requirements for Future Network (FN). It also discusses a milestone for standardization on FN. The scope of ISO/IEC TR 29181-1:2012 includes: motivation of FN; definition, general concept, and terminologies of FN; services and applications in FN; problems with current networks; design goals and high-level requirements for FN; milestones for standardization on FN.

Technologies de l'information — Réseaux du futur — Énoncé du problème et exigences — Partie 1: Aspects généraux

General Information

• Status: Published
• Publication Date: 06-Sep-2012
• ICS: 35.100.30 - Network layer
• Technical Committee: ISO/IEC JTC 1/SC 6 - Telecommunications and information exchange between systems
• Drafting Committee: ISO/IEC JTC 1/SC 6/WG 7 - Network, transport and future network
• Current Stage: 6060 - International Standard published
• Start Date: 07-Sep-2012
• Due Date: 06-Oct-2013
• Completion Date: 06-Oct-2013

Overview

ISO/IEC TR 29181-1:2012 - Information technology - Future Network (FN) - Part 1: Overall aspects is a Technical Report from ISO/IEC JTC 1 that defines the motivation, concepts, problems and high-level requirements for Future Network (FN) architectures. The report frames a clean‑slate and incremental approach to designing networks that go beyond current Internet limits and outlines a milestone-driven roadmap for future standardization work.

What this standard covers

• Definition and general concept of Future Network (FN) and associated terminology.
• Motivation and vision for FN: why current networks need evolution (scalability, ubiquity, security, mobility, heterogeneity, QoS, manageability, economics).
• Services and applications that FN should support.
• Problem statement detailing shortcomings of current networks (routing scalability, insecurity, mobility handling, congestive collapse, heterogeneous media, inefficient media distribution, etc.).
• High-level requirements and design goals such as scalability, naming/addressing schemes, security, mobility support, customizable QoS, network virtualization, service awareness, media transport, management, energy efficiency and economic incentives.
• Milestone and standardization roadmap for FN, including planned work on naming/addressing, switching/routing, mobility, security, media distribution and service composition.

Key technical topics and requirements

• Scalability: architectures and naming/addressing models to handle massively increased endpoints and services.
• Naming and addressing: rethinking identifiers to support mobility, multi-homing and service-centric models.
• Security and privacy: comprehensive requirements covering peer, resource, mobility and heterogeneity threats.
• Mobility: context-aware mobility, seamless multi‑homing and flow switching across heterogeneous access networks.
• Quality of Service / Experience (QoS/QoE): support for customizable service-level behavior.
• Heterogeneity & virtualization: enabling coexistence of multiple virtual networks over shared physical infrastructures and diverse devices/media.
• Service awareness: discovery, composition, self-organizing services and context-aware operation.
• Management and resilience: robust, autonomous management models to prevent failures and congestive collapse.
• Energy and economics: efficiency and incentive mechanisms to make future deployments sustainable and operable.

Practical applications - who uses this standard

• Network architects and designers planning next‑generation architectures.
• Standards bodies and working groups (e.g., JTC 1 / SC 6) aligning FN work items.
• Researchers and academic projects studying clean‑slate and incremental evolution of the Internet.
• Telecom vendors, cloud and CDN providers designing products for mobility, virtualization and service composition.
• Network operators and integrators evaluating long‑term migration strategies.
• Policy makers and regulators assessing economic and operational implications of future networks.
• IoT, vehicular networks and multimedia system designers needing scalable, secure, context‑aware networking models.

Related standards and roadmap

ISO/IEC TR 29181 is a multi‑part technical report series. Part 1 sets the overall aspects; Parts under preparation address detailed topics:

• Part 2: Naming and addressing
• Part 3: Switching and routing
• Part 4: Mobility
• Part 5: Security
• Part 6: Media distribution
• Part 7: Service composition

ISO/IEC TR 29181-1:2012 is a foundational guidance document for FN standardization, useful as a roadmap for subsequent technical specifications and protocol work.

Standards Content (Sample)

TECHNICAL ISO/IEC
REPORT TR
29181-1
First edition
2012-09-15
Information technology — Future
Network — Problem statement and
requirements —
Part 1:
Overall aspects
Technologies de l'information — Réseaux du futur — Énoncé du
problème et exigences —
Partie 1: Aspects généraux
Reference number
©
ISO/IEC 2012
©  ISO/IEC 2012
All rights reserved. Unless otherwise specified, no 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 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 [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2012 – All rights reserved

Contents Page
Foreword . v
Introduction . vi
1  Scope . 1
2  Normative references . 1
3  Terms and definitions . 1
4  Abbreviations . 3
5  Overview . 4
5.1  Needs to research and standardize FN . 4
5.2  Value and vision of FN . 4
6  Services and applications in FN . 5
7  Problem statement . 6
7.1  Basic problems . 6
7.1.1  Routing failures and scalability . 6
7.1.2  Insecurity . 7
7.1.3  Mobility . 7
7.1.4  Quality of service . 7
7.1.5  Heterogeneous physical layers, applications and architecture . 7
7.1.6  Network management . 7
7.1.7  Congestive collapse . 7
7.1.8  Opportunistic communications . 7
7.1.9  Fast long-distance communications . 7
7.1.10  Lack of efficient media distribution . 7
7.1.11  Customizability . 8
7.1.12  Economy and policy . 8
7.2  Problems with fundamental design principles of current Internet . 8
7.2.1  Packet switching . 8
7.2.2  Models of the end-to-end principle . 8
7.2.3  Layering . 8
7.2.4  Naming and addressing . 9
8  General requirements for FN . 9
8.1  Scalability . 9
8.2  Naming and addressing scheme . 9
8.3  Security . 9
8.3.1  Privacy . 9
8.3.2  Mobility . 10
8.3.3  Peer . 10
8.3.4  Resource . 10
8.3.5  Heterogeneity . 10
8.3.6  Attack . 10
8.4  Mobility . 10
8.4.1  Context-awareness . 11
8.4.2  Multi-homing and seamless flow switching . 11
8.4.3  Heterogeneity . 11
8.5  Customizable quality of service . 11
8.6  Heterogeneity and network virtualization . 12
8.6.1  Application/service heterogeneity . 12
8.6.2  Device heterogeneity . 12
8.6.3  Physical media heterogeneity . 12
© ISO/IEC 2012 – All rights reserved iii

8.6.4  Network virtualization .12
8.7  Service awareness .12
8.7.1  Service discovery .13
8.7.2  Service composition .13
8.7.3  Self-organizing service .13
8.7.4  Context-awareness .14
8.7.5  Service QoE .14
8.8  Media transport .14
8.9  New layered architecture .14
8.10  Management .15
8.10.1  Robustness .15
8.10.2  Autonomy .15
8.11  Energy efficiency .15
8.12  Economic incentives .15
8.12.1  Quality of service/experience .15
8.12.2  Manageability .15
8.12.3  Customizability .15
8.12.4  AAA and security .15
8.12.5  Operational aspect.15
9  Milestone for standardization on FN.16
9.1  Overall work plan .16
9.2  Architectures of FN .16
9.2.1  FN architecture: services/network model and functional architecture .17
9.2.2  FN architecture: naming and addressing .18
9.2.3  FN architecture : switching and routing .18
9.2.4  FN architecture: mobility .18
9.2.5  FN architecture: security .18
9.2.6  FN architecture : media transport .19
9.2.7  FN architecture : service composition .19
9.2.8  FN architecture : federation .19
9.2.9  Protocols for FN .19
Annex A (informative) General concept of FN .20
Annex B (informative) Gap analysis .22
Bibliography .25

iv © ISO/IEC 2012 – 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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
In exceptional circumstances, when the joint technical committee has collected data of a different kind from
that which is normally published as an International Standard (“state of the art”, for example), it may decide to
publish a Technical Report. A Technical Report is entirely informative in nature and shall be subject to review
every five years in the same manner as an International Standard.
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.
ISO/IEC TR 29181-1 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 6, Telecommunications 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
The following parts are under preparation:
 Part 2: Naming and addressing
 Part 3: Switching and routing
 Part 4: Mobility
 Part 5: Security
 Part 6: Media distribution
 Part 7: Service composition
© ISO/IEC 2012 – All rights reserved v

Introduction
The current Internet has become an essential communication infrastructure, not only for data transfer but also
for social applications such as e-government, energy/traffic controls, finance, learning, health, etc.
Even though the current Internet is such an essential infrastructure, we see that there are many concerns
about the following technical aspects of the current Internet, including IP based networks: scalability, ubiquity,
security, robustness, mobility, heterogeneity, Quality of Service (QoS), re-configurability, context-awareness,
manageability, economics, etc. Also, the advancement of mass storage units, high speed computing devices,
and ultra broadband transport technologies (e.g., peta/exa/zeta bps) enables many emerging devices such as
sensors, tiny devices, vehicles, etc. The resultant new shape of ICT architecture and huge number of new
services cannot be well supported with current network technologies.
The Future Network (FN), which is anticipated to provide functionalities and services beyond the limitations of
current networking technology, has been studied by researchers in the field of communication network and
services worldwide. FN technologies have now been widely and deeply studied in many research
organizations and standardization bodies.
This part of ISO/IEC TR 29181 describes overall aspects for FN including definition, general concept,
problems and requirements. Also, it discusses a milestone for standardization on FN.

vi © ISO/IEC 2012 – All rights reserved

TECHNICAL REPORT ISO/IEC TR 29181-1:2012(E)

Information technology — Future Network — Problem
statement and requirements —
Part 1:
Overall aspects
1 Scope
This part of ISO/IEC TR 29181 describes the definition, general concept, problems and requirements for
Future Network (FN). It also discusses a milestone for standardization on FN. The scope of this part of
ISO/IEC TR 29181 includes:
 motivation of FN;
 definition, general concept, and terminologies of FN;
 services and applications in FN;
 problems with current networks;
 design goals and high-level requirements for FN;
 milestones for standardization on FN.
2 Normative references
There are no normative references.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
Future Network
FN
network of the future which is made on clean-slate design approach as well as incremental design approach; it
should provide futuristic capabilities and services beyond the limitations of the current network, including the
Internet
3.2
clean-slate design approach
approach where a system and network are designed from scratch, based on a long-term, revolutionary
approach
NOTE In clean-slate design approach, the backward compatibility may not be required [1],[2].
© ISO/IEC 2012 – All rights reserved 1

3.3
network virtualization
technology that enables the creation of logically isolated network partitions over shared physical network
infrastructures so that multiple heterogeneous virtual networks can simultaneously coexist over the shared
infrastructures
NOTE Network virtualization allows the aggregation of multiple resources and makes the aggregated resources
appear as a single resource [3],[4].
3.4
cross-layer communication
technology that enables to create new interfaces between layers, redefine the layer boundaries, design
protocol at a layer based on the details of how another layer is designed, joint tuning of parameters across
layers, or create complete new abstraction
3.5
autonomous service
service that enables users or services in motion to configure autonomously and to mange networks
3.6
context-awareness service
service that enables applications or services to adapt their behaviour based on their physical environment
3.7
content-centric networking
technology that enables to support routing based on contents rather than physical location
3.8
service composition
technology that supports the composition of those activities required to combine and link existing services
(atomic and, even composite services) to create new processes; i.e., the customizability of the services
provided to the end users
3.9
customizable QoS/QoE
technology that enables to support preference setting and service composition/re-composition accordingly
3.10
economic incentives
encouragement, rewards and compensation which motivates the parties (components/participants)
economically to contribute for networking and/or services and/or to provide their resources
3.11
Building Blocks (BB) approach
technique for development of a set of standards by creating some basic modules or elements that may be
added together so as to obtain an overall architecture or entire operations
NOTE This approach may be used to develop a new challenging technology, such as Future Network, in which many
of the basic associated elements have not been identified at the current stage.
[Note] The definitions of Internet and NGN:
 Internet: A collection of interconnected networks using the Internet Protocol which allows them to
function as a single, large virtual network [5].The Internet: a global system of interconnected
computer networks that interchange data by packet switching using the standardized Internet
Protocol Suite (TCP/IP). It is a "network of networks" that consists of millions of private and public,
academic, business, and government networks of local to global scope that are linked by copper
wires, fiber-optic cables, wireless connections, and other technologies [5].
2 © ISO/IEC 2012 – All rights reserved

 Next Generation Network (NGN): A packet-based network able to provide telecommunication
services and able to make use of multiple broadband, QoS-enabled transport technologies and in
which service-related functions are independent from underlying transport-related technologies. It
enables unfettered access for users to networks and to competing service providers and/or services
of their choice. It supports generalized mobility which will allow consistent and ubiquitous provision
of services to users [6].
4 Abbreviations
AAA Authentication, Authorization, and Accounting
BB Building Blocks
DNS Domain Name System
FA Functional Architecture
FI Future Internet
FIRE Future Internet Research and Experiments
FN Future Network
FP7 Framework Program 7
GENI Global Environment for Network Innovations
ICT Information Communication Technology
IoT Internet of Things
IP Internet Protocol
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISP Internet Service Provider
NAT Network Address Translation
NGN Next Generation Networks
NwGN New Generation Network
P2P Peer-to-Peer
PI Provider Independent
QoE Quality of Experience
QoS Quality of Service
SOA Service Oriented Architecture
© ISO/IEC 2012 – All rights reserved 3

5 Overview
5.1 Needs to research and standardize FN
The current IP-based technology has significant deficiencies that need to be solved before it can be become a
unified global communication infrastructure. Particularly, there are problems with a large number of hosts,
such as sensors, the various wireless and mobile nodes, multiple interface and multi-homed nodes, the
support of the flow mobility, support of fast mobile hosts, safe e-transactions, quality of service guarantees,
business aspects, etc., on current IP-based networks, so various researches have been conducted to solve
these problems. Further, there are now significant concerns that shortcomings would not be completely
resolved by the conventional incremental and 'backward-compatible' style of current research and
standardization efforts. That is the reason why the FN research effort is called a “clean-slate design for anew
network’s architecture”. It is assumed that FN design must be discussed based on a clean-slate approach as
well as an incremental design approach.
In this regard, we need to study and standardize the FN which overcomes the limitations of current networks,
and enable new plentiful services.
5.2 Value and vision of FN
The business model of FN aims for profit sharing among infrastructure providers, service providers,
application providers and end users by building cooperative eco-systems between them. It can be
accomplished by openness and accommodating various requirements of each party.
Also, FN will be able to provide millions/billions of services, therefore flexible service composition is required
to achieve the FN of context-aware services. Context-aware service composition is a key functionality required
to provide dynamically adapted services, and a key feature to guarantee a seamless provisioning of media
services, which will allow to generate enriched and novel services for end-users.
Figure 1 illustrates vision and roadmap of FN.
미래
미래
Future
서비스
서비스
Services
Clean-slate
Future Internet
Design
Today’s Future
Service
Federation
migration
Internet Network
Incremental Design
(IPv4)
(IPv6, NGN)
2015 ~ 2020
Figure 1 — Vision and Roadmap of FN
Today’s networks are mainly based on the IPv4 Internet. To enhance the Internet, there are two design
approaches – clean-slate design and incremental design. Future Internet will be designed based on clean-
slate approach and roughly prototyped and deployed between 2015 and 2020. At the same time, today’s
networks will be evolved continuously. Thus, there will be two different network technologies and federation
and service migration are required to support seamless integration. Federation is to be defined as an
interconnection of multiple, heterogeneous networks (e.g, IPv4, IPv6, Future Internet, or non-IP based
networks). In federation, networks would be normally be geographically dispersed and managed by different
organizations/ISPs. They would however be considered as being part of single network, in so far as they are
operated in a common management framework under a common management authority. So, multiple,
4 © ISO/IEC 2012 – All rights reserved

heterogeneous networks would be eventually seen as a single federated network – FN. The FN covers all the
disruptive networks as well as existing networks. FN has a broader view than the Future Internet, and includes
other non-IP networks (e.g., sensors, vehicular networks, satellite, etc.).
6 Services and applications in FN
In the clause, the following future services are envisioned and considered as benchmark services to achieve
to build the FN.
Though the listed services are shown as examples (not normative), they imply essential, societal and
infrastructural services, and require considerable network resources that current Internet technology cannot
support.
Research projects Envisioned future services
- Ubiquitous health care
GENI [7]
- Participatory urban sensing
(Global Environment for
Network Innovations)
- Dealing with personal data
- Tele-presence
NwGN [8] - Essential services: medical care,
transportation, emergency services
(New Generation Network
Architecture)
EU FP-7 [9] - Personal service creation
- Future home
(European Union Framework
Program-7)
- Future of traffic
- Virtual reality
- Productivity tools
Korean Future Internet - Smart Network services
Development and
- Cloud Network services
Deployment Strategies
- Internet of Things services
[10]
-
Distinguished from the traditional CT (communication technology) or IT (information technology) services, the
services of the future should be reconsidered with broader concept since the FN will encompass wide range of
heterogeneous networks [11]:
 The problem of scope, functionality, capability, granularity, time, scale, intelligence, roles, people
and their stuff, and “at your service”
FN (or future) services can be stated as:
 the services which emerge by the year 2020
 the services which are provided and inter-work on top of both clean slate based new networks
and/or existing networks
: Since services are inherently transport /access network independent, it may span across the
exiting and clean slate based infrastructures.
 the services whose features are both user centric (I-Centric) and network centric (Net-Centric)
: The purpose of future services is to satisfy and provide best convenience for end users with
optimal usage of network resources.
© ISO/IEC 2012 – All rights reserved 5

*
*
*
*
*
*
*
And it would cover the IT, telecom, media and cloud computing areas, which can be provided on any layers of
network (Figure 2): for example, future ICT resource services may be provided directly on transport and
resource layers, or may be provided on transport/resource control layer in case with quality controls. Likewise,
immersive communication services may be provided on application/service support layer, or service control
layer according to provider’s own service policy and capabilities. Capabilities of each network layer may be
accessed with open standardized interfaces.
Enhanced media
Enhanced media
communications
communications
IPTV, health, 3D game,
Machine to machine
IPTV, health, 3D game,
Machine to machine
media networking,
media networking,
Adaptive VPN, Virtual community, Cross media platform,
Location measurement,
Cross media platform,
Location measurement, Adaptive VPN, Virtual community,
mobile broadcast,…
Open LBS Real-time collaboration,
Real-time collaboration, mobile broadcast,…
Open LBS
Rich media communication,
Rich media communication,
Immersive communication,
Immersive communication,
Network services
Network services Ultra immersive tele-presence,
Ultra immersive tele-presence,
IT services
Integrated virtual world and web service, IT services
Integrated virtual world and web service,
Service aware managed
Service aware managed Connected virtual and real world,
Connected virtual and real world,
EaaS, Green IT,
network,
EaaS, Green IT,
network, Virtual world on any devices,.
Virtual world on any devices,. context aware computing,
Service mobility,
context aware computing,
Service mobility,
Future cloud computing,
Simple access,
Future cloud computing,
Simple access,
Future ICT resource service,
QoS assured connection,
Application/service support Future ICT resource service,
QoS assured connection,
Future IDC
Managed P2P
Future IDC
Managed P2P
Service control
Sensor net/Access control Transport/Resource control
Transport/Resource (communication/computing/storage,.)
* API/Open Interface
Figure 2 — Services Concept of FN
The key features the FN services should support include:
 Context awareness
 Dynamic adaptiveness
 Self organization and self-configuration
 Self-detection and self-healing
 Distributed control
 Mass data control
7 Problem statement
The problems for the FN could be classified into i) basic problems and ii) problems with fundamental design
principles of current Internet. Most of them are also studied and researched in many organizations and
research projects such as IETF/IRTF[12, 13], ITU-T [14], EU FIA Arch group [15].
7.1 Basic problems
7.1.1 Routing failures and scalability
The today’s Internet is facing challenges in scalability issues on routing and addressing architecture. The
problems have been examined as being caused by mobility, multi-homing, renumbering, provider
independence (PI routing), IPv6 impact, etc. on the today’s Internet architecture. The problem is known to be
caused by current Identifier-Locator integration architecture within IP address scheme. As the Internet
continues to evolve, the challenges in providing a scalable and robust global routing system will also change
over time.
6 © ISO/IEC 2012 – All rights reserved

7.1.2 Insecurity
One of the main problems on the today’s Internet is that it does not providesecure communication. As current
communication is not trusted, problems are self-evident, such as the plague of security breaches, spread of
worms, and denial of service attacks. Even without attacks, service is often not available due to failures in
equipment of fragile IP routing protocols.
7.1.3 Mobility
Current IP technologies are designed for hosts in fixed locations, and ill-suited to support mobile hosts. Mobile
IP was designed to support host mobility, but Mobile IP has problems on update latency, signaling overhead,
location privacy. Also the current Mobile IP architecture is facing challenges in fast and vertical handover.
Moreover, multiple interfaces are recently available to user devices for the accessing of heterogeneous
multiple access networks. In this case, flow level traffic control is needed in addition to host level mobility
management.
7.1.4 Quality of service
Current Internet architecture is not enough to support quality of service from user or application perspective. It
is still unclear how and where to integrate different levels of quality of service in the architecture.
7.1.5 Heterogeneous physical layers, applications and architecture
Current Internet architecture was known as “a narrow waist” of today’s Internet hourglass. Today’s IP enables
a broad range of physical layers and applications. But, this physical layers and applications heterogeneity
poses tremendous challenges for network architecture, resource allocation, reliable transport, context-
awareness, re-configurability, and security.
7.1.6 Network management
The original Internet lacks in management plane. Instant and easy management for users is highly required,
as the Future Internet can be composed of new emerging heterogeneous wireless, mobile and ad-hoc
architectures. For example, the following autonomic management should be provided to future mobile
networks: self-protecting, self-healing, self-configuring, self-optimizing, etc.
7.1.7 Congestive collapse
Current TCP is showing its limits in insufficient dynamic range to handle high-speed wide-area networks, poor
performance over links with unpredictable characteristics, such as some forms of wireless link, poor latency
characteristics for competing real-time flows, etc.
7.1.8 Opportunistic communications
Current Internet was designed to support always-on connectivity, short delay, symmetric data rate and low
error rate communications, but many evolving and challenged networks (e.g., intermittent connectivity, long or
variable delay, asymmetric data rates, high error rates, etc.) do not confirm to this design philosophy.
7.1.9 Fast long-distance communications
Current Internet is based on the philosophy of ‘end-to-end’ packet forwarding scheme i.e., best-effort network,
so that a point of bottleneck causes a delay. When the distance becomes longer, the probability of bottleneck-
appearance becomes higher.
7.1.10 Lack of efficient media distribution
Related to the media, the current problems are the lack of true interaction between the people and the media,
the lack of efficient search and retrieval mechanisms, the lack of truly collaborative environments, the
© ISO/IEC 2012 – All rights reserved 7

disembodied and non-multimodal access to the content, the gap between content (media) and senses and the
lack of emotional communication among users and communities. The current network problems are its
reliability aspects, its complex management, its asymmetric nature (more download than upload), relatively
limited capacity of access lines, the limitation to always achieve ubiquity of access, the lack of integration of
QoS and security within mobility, the lack of security mechanisms (intrusion detection, attack mitigation, quick
reaction to attacks, etc.) and the difficulties for monitoring the network performance.
7.1.11 Customizability
The Internet has evolved to reflect changes in the way it is used. Originally, it was primarily used by scientists
for networking research and for exchanging static information. However, it is now also used to carry digital
media such as audio and video, which have very different requirements from the original traffic. Moreover, in
the near future, this heterogeneous and dynamic context is going to rise exponentially. Additionally, it is
expected that the Future Media Internet will allow to share and distribute high quality and rich (including 3D)
multimedia content and services in a flexible, efficient and personalized way. This will directly impact on the
improvement of quality of life, working conditions, edutainment and safety.
Broader speaking, the user will consume services that will be a composition of simple or already composited
services, and these will not be limited only to media services, but also to network services and any other kind
of required services.
In addition, FN will require to deal with transparent network-imposed blackboxes if they want to add
intelligence to the network (opposite to end-to-end principle used for current internet design). Middleboxes or
blackboxes should be natively supported by networks as they are key in order to provide future value added
services and capabilities.
7.1.12 Economy and policy
There is also a question of how infrastructure providers, service providers, and end users continue to make
profit. Some of the economic travails of the today’s Internet can be traced to a failure of engineering. The
today’s Internet lacks explicit economic primitives.
7.2 Problems with fundamental design principles of current Internet
7.2.1 Packet switching
Today’s Internet technologies use connectionless packet switching making it hard to provide guaranteed QoS
or to take advantage of improvements in optical switching. Packet switching is also known to be inappropriate
for the core of high capacity (e.g., Terabit) networks. Instead, we may need to re-design dynamic circuit
switching or hybrid (packet–circuit) switching for the core of networks.
7.2.2 Models of the end-to-end principle
The models of the end-to-end principle has been progressively eroded, most notably by the use of NATs,
which modify addresses, and firewalls and other middle boxes, which expect to understand the semantics
behind any given port number (for instance to block or differentially handle a flow). As a result, end hosts are
often not able to connect even when security policies would otherwise allow such connections. This problem
will only be exacerbated with the emerging need for IPv4-IPv6 translation. Beyond this, other changes in the
way the Internet is used has stressed the original unique-address:port model of transport connections.
7.2.3 Layering
Layering was one of important characteristics of today’s Internet technologies, but at this phase, it has
inevitable inefficiencies. One of challenging issues is how to support fast mobility in heterogeneous layered
architecture. We should explore where interfaces belong, and what services each layer must provide.
8 © ISO/IEC 2012 – All rights reserved

7.2.4 Naming and addressing
Naming and addressing schemes are two essential and key elements in a network structure and service
provisioning. How the naming and addressing are designed has a critical impact on the characteristic and
performance of the networks. The fundamental structure of naming and addressing scheme in current
networks especially the IP networks are mostly designed over 40 year’s ago and is a major root of the
problems facing existing networks. For example, the DNS to IP address search and translation process, the
centralized domain name registration, the hierarchical structure etc. limits the potential of existing networks.
We should explore new naming and addressing design principles to help achieve FN objectives.
8 General requirements for FN
In this clause, new design goals and high-level requirements for the FN are described.
8.1 Scalability
The FN should support scalable routing architecture. Scalability issue is emerging as the cultural demands for
networking toward the future is growing continuously. During the next 10-15 years, it is envisioned that the
telecommunication networks including internet will undergo several major transitions with respect to
technologies, services, size, and so on. For example, machine-to-machine communication might be pervasive
in addition to the current way of communication that human-beings are involved. Scalability consideration
should include following aspects:
 Routing and addressing architecture
 Multi-homing and provider independence (PI routing)
8.2 Naming and addressing scheme
The FN may need new naming and addressing schemes which would require:
 The new naming and addressing schemes should take the advantage of the principle of clean slate
design to explore, identify, experiment complete new architecture.
 The new architecture does not have to abide by the old network naming and addressing rules, but on
the other hand, the issue of compatibility and interoperability should also be considered when
technical proposals are evaluated.
 An architecture which would help FN to achieve objectives such as scalability, security, mobility,
robustness, heterogeneity, quality of service, customizability and economic incentive.
Ability to integrate various networks, to support new protocols, to provide bases for new applications and
services, and to give support to new networking technologies
8.3 Security
The FN should be built on the premise that security must be protected from the plague of security breaches,
spread of worms and spam, and denial of service attacks, and so on. Especially, as for authentication, the
following requirements are carefully investigated.
8.3.1 Privacy
Because of the practical considerations to prevent attacks such as spoofing, we would like to bind each user
or device to a single identity. However, users value their privacy and are unlikely to adopt systems that require
them to abandon their anonymity. For example, most users would resent a system such as a Mobile IP
Network that allows others to know their locations. Balancing privacy concerns with authentication needs in
FN will require codifying legal, societal and practical considerations.
© ISO/IEC 2012 – All rights reserved 9

8.3.2 Mobility
Traditional authentication mechanisms for networks frequently base on a relatively static or fixed network, and
even ad hoc networks typically assume limited mobility, often focusing on handheld PDAs and laptops carried
by users. The design of authentication mechanism for FN should consider the case of highly mobility in a
network. For example, in vehicular networks, since two vehicles may only be within communication range for a
matter of seconds and many of whom it has never interacted with before and is unlikely to interact with again,
we cannot rely on protocols that require significant interaction to process authentication between the sender
and receiver.
8.3.3 Peer
Why the authentication and trust of ends become a challenge in current networks? One of important reasons
is that many authentication mechanisms cannot provide a real mutual authentication procedure. For example,
we currently focus on how to identify a spoof station by the server, while a station usually does not have an
effective scheme to check the identity of a server in a network. Hence, the authentication mechanisms of peer
and multi-security should be designed for FN.
8.3.4 Resource
With the increasing ubiquity of networks, it can be seen that size and cost constraints on nodes result in
corresponding constraints on resources such as energy, memory and computational speed, resulting in the
challenge of authentication
...