Arguments for an information-centric internetworking architecture

Nature, 2010

IJCSMC, 2021

The original internet design principle was guided by the end-to-end principle in the early 1980s and formed the foundation for the existing internet architectural model. The priorities of the original internet designers do not match the needs of today actual users; rise in new players, demanding applications, erosion of trust and rights and responsibilities is pushing the internet to a new dimension. This paper presents the goals and principles behind the design of the original internet architecture, the resulting issues and limitations of the existing network architecture and the approaches that is driving the future internet architecture.

Multidisciplinary Perspectives on Telecommunications, Wireless Systems, and Mobile Computing, 2014

We all take the ubiquity of the Internet for granted: anyone, anywhere, anytime, any device, any connection, any app…but for how long? Is the future of the Internet really at stake? Discussions about control of the Internet, its architecture and of the applications running on it started more than a decade ago (Blumenthal & Clark, 2001). This topic is becoming more and more important for citizens, businesses, and governments across the world. In its original setup , the architecture of the Internet did not favor one application over another and was based on the net neutrality principle (Wu, 2003). However, architectures should be understood an "alternative way of influencing economic systems" (Van Schewick, 2010), but they should not be a substitute for politics (Agre, 2003). The architecture is laid down in standards and therefore discussions about the future of the Internet should also address the role of standards. This is what this chapter aims to do.

2010

In most cases, current Internet architecture treats content and services simply as bits of data transported between end-systems. While this relatively simple model of operation had clear benefits when users interacted with wellknown servers, the recent evolution of the way the Internet is used makes it necessary to create a new model of interaction between entities representing content. In this paper we study the limitations of current Internet and propose a new model, where the smallest addressable unit is a content object, regardless of its location.

Communications Policy in …, 2001

residing on several hosts the network is therefore "transparent" in that it has no effect on the application other than facilitating the delivery of information between the

Lecture Notes in Computer Science, 2012

Design principles play a central role in the architecture of the Internet as driving most engineering decisions at conception level and operational level. This paper is based on the EC Future Internet Architecture (FIArch) Group results and identifies some of the design principles that we expect to govern the future architecture of the Internet. We believe that it may serve as a starting point and comparison for most research and development projects that target the so-called Future Internet Architecture. 2 Definition and Background 2.1 Definitions We define architecture the set of functions, states, and objects/information together with their behavior, structure, composition, relationships and spatio-temporal distribution. The specification of the associated functional, object/informational and state models leads to an architectural model comprising a set of components (i.e., procedures, data structures, state machines) and the characterization of their interactions (i.e., messages, calls, events, etc.). Design principles refer to agreed structural and behavioral rules on how a designer/an architect can best structure the various architectural components and describe the fundamental and time invariant laws underlying an engineered artefact (i.e., an object formed/produced by engineering). By "structural and behavioral rules" we refer to the set of commonly accepted and agreed rules serving to guide, control, or regulate a proper and acceptable structure of a system at design time and a proper and acceptable behavior of a system at running time. Time invariance refers to a system whose output does not depend explicitly on time (this time invariance is to be seen as within a given set of initial conditions due to the technological change and paradigms shifts, the economical constraints, etc.). We use the term data to refer to any organized group of bits, e.g., packets, traffic, information, etc. and service to refer to any action or set of actions performed by a provider in fulfillment of a request, which occurs through the Internet (i.e., by exploiting data communication, as defined below) with the aim of creating and/or providing added value or benefits to the requester(s). "Resource" is any fundamental element (i.e., physical, logical or abstract) that can be identified. This paper refers to communication as the exchange of data (including both control messages and data) between a physical or logical source and sink referred to as communication end-points; when end-points sit at the same physical or logical functional level, communication is qualified as "end-to-end". Security is a process of taking into account all major constraints that encompasses robustness, confidentiality and integrity. Robustness is the degree to which a system operates correctly in the presence of exceptional inputs or stressful environmental conditions. Confidentiality is the property that ensures that information is accessible only to those authorized to have access and integrity includes both "data integrity" and "system integrity". The term complexity refers to the architectural complexity (i.e., proportional to the needed number of components and interactions among components), and communication complexity (i.e., proportional to the needed number of messages for proper operation). Finally, scalability refers to the ability of a computational system to continue to function without making changes to the system

2010 IEEE Global Telecommunications Conference GLOBECOM 2010, 2010

We present a new Internet architecture based on de-conflated identities (ADI) that explicitly establishes the separation of ownership of hosts from the underlying infrastructure connectivity. A direct impact of this de-conflated Internet architecture is the ability to express organizational policies separately and thus more naturally, from the underlying infrastructure routing policies. Host or organizational accountability is separated from the infrastructure accountability, laying the foundations of a cleaner security and policy enforcement framework. Also, it addresses the present Internet routing problems of mobility, multihoming, and traffic engineering more naturally by making a clear distinction of host and infrastructure responsibilities and thus defining these functions as a set of primitives governed by individual policies. In this paper, we instantiate the primitive mechanisms related to the issues of end-to-end policy enforcements, mobility, multihoming, traffic engineering, etc., within the context of our architecture to emphasize the relevance of a de-conflated Internet architecture on these functions.

2008 4th Workshop on Secure Network Protocols, 2008

This paper proposes a future Internet architecture whose security foundations prevent today's major threats -IP spoofing, distributed denial-of-service attacks, distributed scanning and intrusions, and wide-spread worm infections.

IEEE Internet Computing, 2000

It has been argued by many that the Future Internet should address information at the core of its operation. Prototypes have emerged to embody this new paradigm. Applications for such networks, however, are noted primarily by their absence. In spite of an appetite for Information-Centric Networking (ICN) applications, relatively little has come to fruition. We suggest that this is due to an unfavorable development environment, requiring applications to interface with the ICN substrate directly. This paper aims to answer this shortcoming by providing a middleware layer that aids the development of more advanced applications. We also present an application that leverages the middleware and answers a real-world problem concerning personalised media delivery. We argue that the development of this, and potentially other, application(s) is aided by the presence of such an application environment.