Identifier-Locator Network Protocol (ILNP) Architectural Description
01 Nov 2012-Vol. 6740, pp 1-53
TL;DR: This document provides an architectural description and the concept of operations for the Identifier-Locator Network Protocol (ILNP), which is an experimental, evolutionary enhancement to IP.
Abstract: This document provides an architectural description and the concept of
operations for the Identifier-Locator Network Protocol (ILNP), which
is an experimental, evolutionary enhancement to IP. This is a product
of the IRTF Routing Research Group. This document defines an
Experimental Protocol for the Internet community.
Citations
More filters
10 Apr 2016
TL;DR: A clear definition of NDN mobility support is provided, to enable fetching of data produced by mobile users, and then to classify the proposed solutions by their commonalities and to articulate design tradeoffs of different approaches.
Abstract: The initial Named Data Networking (NDN) architecture design provided consumer mobility support automatically, taking advantage of NDN's stateful forwarding plane to return data to mobile consumers; at the same time, the support of data producer mobility was left unspecified. During the past few years, a number of NDN producer mobility support schemes have been proposed. This paper provides a clear definition of NDN mobility support, to enable fetching of data produced by mobile users, and then to classify the proposed solutions by their commonalities and to articulate design tradeoffs of different approaches. We identify remaining challenges and discuss future research directions for effective and efficient data producer mobility support in NDN.
108 citations
Cites methods from "Identifier-Locator Network Protocol..."
...Afterwards, we discuss the design tradeoffs and security challenges (§V), and conclude the paper with our evaluation of the solutions and describe future work (§VI)....
[...]
TL;DR: This paper illustrates the major serious problems of the Internet caused by the overloading of IP address semantics, and classify the existing Loc/ID split network architectures based on their properties, abstract the general principle and framework for each classification, and demonstrate related representative architectures in detail.
Abstract: The Internet has achieved unprecedented success in human history. However, its original design has encountered many challenges in the past decades due to the significant changes of context and requirements. As a result, the design of future networks has received great attention from both academia and industry, and numerous novel architectures have sprung up in recent years. Among them, the locator/identifier (Loc/ID) split networking is widely discussed for its decoupling of the overloaded IP address semantics, which satisfies several urgent needs of the current Internet such as mobility, multi-homing, routing scalability, security, and heterogeneous network convergence. Hence, in this paper, we focus on Loc/ID split network architectures, and provide a related comprehensive survey on their principles, mechanisms, and characteristics. First, we illustrate the major serious problems of the Internet caused by the overloading of IP address semantics. Second, we classify the existing Loc/ID split network architectures based on their properties, abstract the general principle and framework for each classification, and demonstrate related representative architectures in detail. Finally, we summarize the fundamental features of the Loc/ID split networking, compare corresponding investigated architectures, and discuss several open issues and opportunities.
60 citations
Additional excerpts
...3) ILNP: ILNP (Identifier-Locator Network Protocol) [61], [62] aims to support mobility, multi-homing,...
[...]
...3) ILNP: ILNP (Identifier-Locator Network Protocol) [61], [62] aims to support mobility, multi-homing, localised addressing and security for the current Internet through naming....
[...]
29 Sep 2014
TL;DR: This paper argues that IP mobility problems can be addressed based on Software Defined Networks (SDN), and discusses why SDN helps to solve the problems in current IP mobility protocols and gives algorithms to demonstrate how the problems are solved.
Abstract: A large number of solutions have been proposed to support mobility in IP networks including original Mobile IP, its derivatives and several newly proposed protocols. However, these solutions have drawbacks in different aspects including triangle routing, handover inefficiency, heavy signaling overhead, etc. In this paper, we argue that these problems can be addressed based on Software Defined Networks (SDN). We discuss why SDN helps to solve the problems in current IP mobility protocols and give our algorithms to demonstrate how the problems are solved. We also present an Openflow-based protocol design to realize our idea. We show performance benefits of our protocol comparing with existing IP mobility protocols through implementation and experiments on Mininet. Keywords—mobility management; mobile ip; home agent; software defined networks; openflow
54 citations
TL;DR: This critical review provides some valuable guidelines and suggestions for designing and developing mobility architectures, including some practical expedients aimed to cope with the presence of NAT/firewalls and to provide support to legacy systems and several communication protocols working at the application layer.
44 citations
TL;DR: This paper proposes design, implementation and deployment of a software-defined IP mobility architecture and demonstrates evaluations and experiments of the proposal based on both the Mininet platform and a cross-domain SDN testbed, proving the feasibility, scalability and high adaptability of the proposed architecture.
Abstract: Recently many research efforts have been spent on applying Software Defined Networking (SDN) to mobile and wireless networking to make them adapt to the rapid development and popularity of the mobile Internet. SDN offers programmable devices and centralized control which help to realize customizable and adaptive solutions to meet requirements from diversified mobile networks, devices, applications and so forth. This paper focuses on extending SDN paradigm to mobility handling in the Internet which has been little studied, and proposes design, implementation and deployment of a software-defined IP mobility architecture. The paper also demonstrates evaluations and experiments of the proposal based on both the Mininet platform and a cross-domain SDN testbed. Results prove the feasibility, scalability and high adaptability of the proposal.
43 citations
Cites background or methods from "Identifier-Locator Network Protocol..."
...Host Identity Protocol (HIP) [9], IdentifierLocator Network Protocol (ILNP) [10] and LISP Mobile Node [11] are typical solutions that fall into this category....
[...]
...In this evaluation set, we compare our proposal with Proxy Mobile IPv6 (PMIPv6) [26] and ILNP [10], which serve as representatives of existing Internet mobility solutions, in terms of data plane QoS metrics....
[...]
...On the other side, protocols such as HIP [9], ILNP [10] and LISP Mobile Node [11] propose to move the mapping functionality from the network side to the host side....
[...]
References
More filters
01 Mar 1997
TL;DR: This document defines these words as they should be interpreted in IETF documents as well as providing guidelines for authors to incorporate this phrase near the beginning of their document.
Abstract: In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document:
3,501 citations
28 Aug 1980
TL;DR: UDP does not guarantee reliability or ordering in the way that TCP does, but its stateless nature is also useful for servers that answer small queries from huge numbers of clients.
Abstract: UDP does not guarantee reliability or ordering in the way that TCP does. Datagrams may arrive out of order, appear duplicated, or go missing without notice. Avoiding the overhead of checking whether every packet actually arrived makes UDP faster and more efficient, at least for applications that do not need guaranteed delivery. Time-sensitive applications often use UDP because dropped packets are preferable to delayed packets. UDP's stateless nature is also useful for servers that answer small queries from huge numbers of clients. Unlike TCP, UDP supports packet broadcast (sending to all on local network) and multicasting (send to all subscribers).
2,485 citations
Proceedings Article•
01 Jan 1981TL;DR: A design principle is presented that helps guide placement of functions among the modules of a distributed computer system and suggests that functions placed at low levels of a system may be redundant or of little value when compared with the cost of providing them at that low level.
Abstract: This paper presents a design principle that helps guide placement of functions among the modules of a distributed computer system. The principle, called the end-to-end argument, suggests that functions placed at low levels of a system may be redundant or of little value when compared with the cost of providing them at that low level. Examples discussed in the paper include bit error recovery, security using encryption, duplicate message suppression, recovery from system crashes, and delivery acknowledgement. Low level mechanisms to support these functions are justified only as performance enhancements.
2,091 citations
[...]
01 Sep 1981
TL;DR: Along with TCP, IP represents the heart of the Internet protocols and has two primary responsibilities: providing connectionless, best-effort delivery of datagrams through an internetwork; and providing fragmentation and reassembly of data links to support data links with different maximum transmission unit (MTU) sizes.
Abstract: IP is a network layer (Layer 3) protocol that contains addressing information and some control information that enables packets to be routed. IP is documented in RFC 791 and is the primary network layer protocol in the Internet protocol suite. Along with TCP, IP represents the heart of the Internet protocols. IP has two primary responsibilities: providing connectionless, best-effort delivery of datagrams through an internetwork; and providing fragmentation and reassembly of datagrams to support data links with different maximum transmission unit (MTU) sizes.
1,967 citations
01 Oct 1989
TL;DR: This RFC is an official specification for the Internet community that incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts.
Abstract: This RFC is an official specification for the Internet community It
incorporates by reference, amends, corrects, and supplements the
primary protocol standards documents relating to hosts [STANDARDS-
TRACK]
1,675 citations