naec2007 - NR2

tansysoapweedRéseaux et Communications

16 févr. 2014 (il y a 3 années et 1 mois)

70 vue(s)

Emerging
Architectures for

Post
-
IP Networking*


Daniel F. Macedo
1
,
Aldri

L. dos Santos
2
,Guy Pujolle
1



1
Université

Pierre et Marie Curie
-
Paris VI, France

2
Federal University of Paraná, Brazil

*This work has been partially financed by CNPq, a funding
organization from the science and technology ministry, Brazil.

Outline


Why should we replace IP?


Post
-
IP Architectures


Research Challenges and Directions in
Post
-
IP

The Internet Nowadays


IP was very well
-
designed, being used for
more than 30 years now



IP is a victim of its own success: new
scenarios with significant challenges:


Node mobility


The Internet of things: small, restricted
devices

Why should we replace IP
networks?


IP is used for identification and routing


It changes when stations roam from one
network to another to allow proper routing


Packets addressed to the ancient IP of a
station are routed to the old network, breaking
connections

Need to decouple routing and addressing!

Why should we replace IP
networks?


The End
-
to
-
End (E2E) principle is
frequently violated


Smart middle
-
boxes, e.g. NAT and proxies
that break other E2E applications


Proxies do not work with SSL connections


NATs are not compatible with P2P


Context
-
aware networks

Why should we replace IP
networks?


Too difficult to be managed by humans


Too many nodes


Changes are frequent due to mobility



Shift from operator
-
based management to
autonomic
-
based management


Scalable self
-
organizing solutions, where
local decisions lead to near optimal global
behavior

An Overview of

Post
-
IP Architectures

AdaptNet


Goals


Support mobile users roaming among BSs


Deliver multimedia content over wireless links


IP
-
compatible



Solution: heavy use of cross
-
layering


Proactively opens TCP connections before
handover to allow seamless operation


Automatically changes the codec in the app.
Layer

Ambient Networks, Plutarch


Post
-
IP networks will be a concatenation of
autonomic heterogeneous networks



Architecture


An autonomic management plane


Ambient Control Space (Ambient Networks)


Interstitial Functions

(Plutarch)


Several layers of names to cope with mobility


Bearers
,
End Points

and
Sessions
(Ambient Networks)


Contexts
(Plutarch)

Ambient Networks

NewArch


Goals


Redesign the Internet from scratch


Rethink the layering model


Provide solutions adapted to wireless links


NewArch


The RBA architecture


Role
-
based forwarding


Improvement of active networks, where roles
define the code to be executed in routers


Resembles the stratum paradigm



Addressing mobility


Three levels of naming, allowing node and agent
mobility

Challenges and
Directions

Challenges and Directions


An urgent need to rethink layering


IP is hard to kill: Post
-
IP must support old
equipment


Autonomic management of post
-
IP networks


No attention has been given to


Emergent networks (ad hoc, WSNs, home networks)


QoS


Security



Challenges and Directions


Security and Dependability


Standards (benchmarks, tools, etc…) to validate
the dependability and security of networks


Large scale test
-
beds


Fast, low
-
cost testing of new protocols of
planetary
-
scale networks


Several initiatives:
PlanetLab
, VINI, GENI



Virtualization



Questions?


Daniel.Macedo@rp.lip6.fr