ETSI GR NGP 003 V1.1.1 (2017-03)

NGP Next Generation Protocol; Packet Routing Technologies

DGR/NGP-003

General Information

• Status: Published
• Publication Date: 29-Mar-2017
• Technical Committee: NGP - Next Generation Protocols
• Current Stage: 12 - Completion
• Due Date: 17-Apr-2017
• Completion Date: 30-Mar-2017

Standards Content (Sample)

ETSI GR NGP 003 V1.1.1 (2017-03)






GROUP REPORT
NGP Next Generation Protocol;
Packet Routing Technologies
Disclaimer
The present document has been produced and approved by the Next Generation Protocols (NGP) ETSI Industry Specification
Group (ISG) and represents the views of those members who participated in this ISG.
It does not necessarily represent the views of the entire ETSI membership.

---------------------- Page: 1 ----------------------
2 ETSI GR NGP 003 V1.1.1 (2017-03)



Reference
DGR/NGP-003
Keywords
flexilink, M2CNP, Next Generation Protocol,
RINA

ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI GR NGP 003 V1.1.1 (2017-03)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
Executive summary . 6
Introduction . 7
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 8
3 Definitions and abbreviations . 10
3.1 Definitions . 10
3.2 Abbreviations . 10
4 RINA (Recursive InterNetwork Architecture) . 12
4.1 Overview . 12
4.1.0 Introduction to RINA . 12
4.1.1 The DIF service definition . 13
4.1.2 The nature of layers (DIFs) . 14
4.1.3 Internals of a DIF: only two protocols required . 14
4.1.4 Naming and addressing . 15
4.1.5 Consistent QoS model across layers . 15
4.1.6 Consistent security model across layers . 16
4.1.7 Network Management . 16
4.2 Data transfer: protocol, functions and procedures . 17
4.2.0 General . 17
4.2.1 DTP PDU Format . 17
4.2.2 DTCP PDU Formats . 18
4.2.3 Overview of data-transfer procedures . 18
4.3 Layer management: protocol, functions and procedures . 19
4.3.1 Common layer management machinery . 19
4.3.2 Layer management functions: enrolment . 20
4.3.3 Layer management functions: namespace management . 20
4.3.4 Layer management functions: flow allocation . 21
4.3.5 Layer management functions: resource allocation . 21
4.3.6 Layer management functions: routing . 22
4.3.7 Layer management functions: security coordination . 22
4.4 Support for mobility . 22
4.5 Support for security . 23
4.6 Addressing and scalability . 24
4.7 Interworking and migration . 24
4.8 Assessment against NGP key issues . 25
5 Flexilink . 26
5.1 Overview . 26
5.1.1 Background . 26
5.1.2 Main differences from IP . 27
5.1.3 Flows, and separation of control and forwarding . 27
5.1.4 Services . 27
5.1.5 Choice of service for data transport . 28
5.2 Packet formats . 29
5.2.1 General . 29
5.2.2 AV packets. 29
5.2.3 IT packets. 29
5.3 Control plane procedures . 30
ETSI

---------------------- Page: 3 ----------------------
4 ETSI GR NGP 003 V1.1.1 (2017-03)
5.3.1 Message format . 30
5.3.2 Identifiers . 30
5.3.2.1 Equipment identifiers . 30
5.3.2.2 Call, route, and flow identifiers . 30
5.3.2.3 Addressing . 30
5.3.3 Setting up routes . 31
5.3.3.1 Procedure for connection-oriented model . 31
5.3.3.2 Connectionless service . 31
5.3.3.3 Additional information in FindRoute messages . 31
5.3.4 Synchronization of AV flows . 31
5.3.4.1 Slots. 31
5.3.4.2 Frame alignment . 32
5.4 Support for mobility . 32
5.5 Support for security . 32
5.5.1 Authentication . 32
5.5.2 Denial of service . 32
5.6 Addressing and scalability . 33
5.7 Interworking and migration . 33
5.7.1 Definitions . 33
5.7.2 Connecting islands via other technologies . 33
5.7.3 Tunnelling other technologies across isla nds . 34
5.7.4 Other gateway functions . 34
5.8 Assessment against NGP key issues . 35
6 Multi-access, Mobility-aware, Context-aware-Networking Protocol (M2CNP) . 37
6.1 Overview . 37
6.2 System Architecture . 37
6.2.1 Introduction. 37
6.2.2 M2CNP Protocol Management Entities . 38
6.2.2.1 Access EndPoint . 38
6.2.2.2 Access Point . 39
6.2.2.3 Packet Processing Entity . 39
6.2.2.4 Cluster Controller Functional Entity . 39
6.2.2.5 Cluster Member Functional Entity . 40
6.2.2.6 Access Agent Functional Entity . 40
6.2.2.7 Network Subscriber Location Database . 40
6.2.2.8 Cluster Content Routing Database . 40
6.3 Protocol Stack . 41
6.4 Access Agent Functionalities and Benefits . 43
6.4.0 Preview . 43
6.4.1 User Plane Functionality . 43
6.4.1.0 General . 43
6.4.1.1 Network Service Request Handling . 43
6.4.1.1.0 Types of service . 43
6.4.1.1.1 HTTP Request Handling . 43
6.4.1.1.2 Voice Request Handling . 44
6.4.1.2 Context-Driven Intelligent Content Management . 44
6.4.2 Control Functionality . 45
6.4.2.1 User Association . 45
6.4.2.2 User Authentication . 45
6.4.2.3 Address Translation . 45
6.4.2.4 Intra-Cluster Mobility . 45
6.4.2.5 Inter-Cluster Mobility . 45
6.5 Protocol Field Structure/Addressing . 45
6.6 Security . 46
6.7 Routing . 47
6.8 Message Sets . 47
6.8.0 General . 47
6.8.1 Network Services . 48
6.9 M2CNP assessment against criteria . 49
Annex A: Assessment against NGP requirements. 52
ETSI

---------------------- Page: 4 ----------------------
5 ETSI GR NGP 003 V1.1.1 (2017-03)
Annex B: Authors & contributors . 54
Annex C: Change History . 55
History . 56


ETSI

---------------------- Page: 5 ----------------------
6 ETSI GR NGP 003 V1.1.1 (2017-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Group Report (GR) has been produced by ETSI Industry Specification Group (ISG) Next Generation Protocols
(NGP).
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
Executive summary
Three technologies are described in the present document.
RINA embodies a theory which is informally known as the Inter-Process Communication (IPC) model. It is structured
around a single type of layer - called Distributed IPC Facility or DIF - that repeats as many times as needed. In RINA,
all layers are distributed applications that provide the same service (communication flows between distributed
applications) and have the same internal structure, divided into data transfer (delimiting, addressing, sequencing,
relaying, multiplexing, lifetime termination, error check, encryption), data transfer control (flow and retransmission
control), and layer management (enrolment, routing, flow allocation, namespace management, resource allocation,
security management).
st
Flexilink is designed for implementation in 21 century digital systems, in which packet forwarding is implemented in
hardware and memory is much more plentiful than when Internet Protocol was developed. The information needed to
route packets is carried separately from the packets themselves; this reduces the size of the packet header by an order of
magnitude, simplifies the forwarding hardware, and allows different addressing mechanisms to be used without
changing the packet format. It supports ultra-low latency live streams; these are needed for some of the new services
that 5G is to support, and also provide a better service for audio and video. They can also be used for file transfer,
eliminating the need for the kind of empirical throughput testing that is a feature of TCP.
M2CNP envisages a packet based routed protocol architecture with the ability to embed protocol control messaging to
provide basic protocol management functions for: security, context-awareness, transmission management, and mobility.
Applications and/or services, running at access network connected devices, communicate using IPC interfaces towards
the M2CNP communications network. Devices may be connected via one or more access technologies at a time and are
capable of mobility from one access point or Temporary Access Points Group (for multiple access) to another. The
M2CNP network consists of M2CNP Packet Processing Entities, which are M2CNP routing entities that are selectively
enabled with various protocol management capabilities of M2CNP and may be deployed in terms of scope in a similar
manner to CE, PE, P scope routers as commonly understood in the legacy IP world.
ETSI

---------------------- Page: 6 ----------------------
7 ETSI GR NGP 003 V1.1.1 (2017-03)
Introduction
ETSI ISG NGP is tasked with reviewing networking technologies, architectures, and protocols for the next generation
of communication systems.
The present document describes some technologies of which ISG NGP is aware, which could be evaluated against the
requirements listed in ETSI GS NGP 001 [i.1] (Scenarios) and 3GPP TR 23.799 [i.3].
Ideally, ISG NGP would issue a Call for Technology and wait for responses before drafting the present document.
However, new radio interfaces are now being developed for 5G, and if something other than TCP/IP is to be used with
them the developers of the radio technology need to have an indication, early in the process, of the kind of shape the
new protocols might have. Therefore, a first version of the present document is being produced covering technologies
that have been researched by the current members of ISP NGP. It is intended that further versions will be produced,
containing additional architectures.

ETSI

---------------------- Page: 7 ----------------------
8 ETSI GR NGP 003 V1.1.1 (2017-03)
1 Scope
The present document describes packet routing technologies that might be used in 5G radio networks and in the core of
future mobile networks, and would also be suitable for use in the Internet. The description of each technology includes:
• overview of routing approach;
• key fields in user plane packets;
• procedures for setting up routes, etc.;
• support for mobility;
• support for security;
• addressing, including scalability issues.
2 References
2.1 Normative references
Normative references are not applicable in the present document.
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] ETSI GS NGP 001 (V1.1.1): "Next Generation Protocol (NGP); Scenario Definitions".
[i.2] ISO/IEC 62379-5-2:2014: "Common control interface for networked digital audio and video
products -- Part 5-2: Transmission over networks -- Signalling".
[i.3] 3GPP TR 23.799: "Study on Architecture for Next Generation System".
[i.4] J. Day: "Patterns in Network Architecture: A return to fundamentals". Prentice Hall, 2008.
[i.5] J. Day, I. Matta, and K. Mattar. 2008: "Networking is IPC: a guiding principle to a better Internet".
In Proceedings of the 2008 ACM CoNEXT Conference (CoNEXT '08).
[i.6] J. Day, E. Grasa: "About layers: more or less".
NOTE: PSOC Tutorial, available online at http://pouzinsociety.org.
[i.7] J. Day: "How naming, addressing and routing are supposed to work".
NOTE: PSOC Tutorial, available online at http://pouzinsociety.org.
[i.8] G. Gursun, I. Matta, and K. Mattar: "On the Performance and Robustness of Managing Reliable
th
Transport Connections". In Proceedings of the 8 International Workshop on Protocols for Future,
Large-Scale and Diverse Network Transports (PFLDNeT), Lancester, PA, November 2010.
ETSI

---------------------- Page: 8 ----------------------
9 ETSI GR NGP 003 V1.1.1 (2017-03)
[i.9] Boddapati, G.; Day, J.; Matta, I.; Chitkushev, L.: "Assessing the security of a clean-slate Internet
th
architecture". Network Protocols (ICNP), 2012 20 IEEE International Conference on.
[i.10] V. Maffione, F. Salvestrini, E. Grasa, L. Bergesio, M. Tarzan: "A Software Development Kit to
exploit RINA programmability". IEEE ICC 2016, Next Generation Networking and Internet
Symposium.
[i.11] J. Day, E. Grasa: "Mobility made simple".
NOTE: PSOC Tutorial, available online at http://pouzinsociety.org.
[i.12] J. Day, E. Trouva, E. Grasa, P. Phelan, M.P. de Leon, S. Bunch, I. Matta, L.T. Chitkushev,
L. Pouzin: "Bounding the router table size in an ISP network using RINA". Network of the Future
(NOF), 2011.
[i.13] V. Ishakian, J. Akinwumi, F. Esposito, and I. Matta: "On supporting mobility and multihoming in
recursive internet architectures". Comput. Commun. 35, 13 (July 2012),
1561-1573.
[i.14] J. Small: "Threat analysis of Recursive InterNetwork Architecture Distributed IPC Facilities".
BU Technical Report, 2011.
[i.15] E. Grasa, O. Rysavy, O. Lichtner, H. Asgari, J. Day, L. Chitkushev: "From protecting protocols to
protecting layers: designing, implementing and experimenting with security policie
...