Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

6.
Lack of application names (II)
• The IP address is both the identifier of the IP protocol
machine and the identifier used to forward IP packets
• Identifier of protocol machine should be stable and
location-independent
– So that firewall rules, ACLs, etc. don’t need to be updated if
the network is renumbered or the host/router moves
• Identifiers used for forwarding must be location-
dependent and may change
– To minimize elements in forwarding table and routing updates
• But there is only 1 identifier: the IP address
– Can’t have both properties at the same time
Large-scale RINA Experimentation on FIRE+ 6

9.
Naming and addressing, mobility, routing
No need for special protocols
Large-scale RINA Experimentation on FIRE+ 9
Name Indicates Property RINA IP
Applica6on name What Loca6on independent Yes No
Node address Where Loca6on dependent, route
independent
Yes No
Point of
A%achment
How to get
there
Route dependent Yes Yes (twice:
IP, MAC)

16.
Implications
• With a proper naming and addressing structure in
place, life network renumbering can be done
– without impacting existing flows
– without the need of extra protocols or mechanisms
– in a fully automated way (minimize opex and network
downtime)
• Use cases
– Network consolidation (e.g. acquisition of other networks)
– Update network addressing scheme to optimize routing (e.g.
due to changes in network topology)
– Better support for mobility (change address of moving nodes
if they attach to different subnets)
Large-scale RINA Experimentation on FIRE+ 16