Documente Academic
Documente Profesional
Documente Cultură
Virendra S Shekhawat
Department of Computer Science and Information Systems
BITS Pilani
Pilani Campus
Agenda
Tussle in Cyber space
[CH-3]
Compulsory Reading
Tussle in Cyberspace: Defining Tomorrows Internet *Clark
2003]
3
First Sem 2015-16
Tussle in Cyberspace
Interests of different stakeholders can adverse of
each other called as tussle
End user, Commercial ISPs, Govt., Private sector
providers, IP Right Holders, Content Providers
Requirements in Todays
Communication
Users communicate but dont trust
User desire anonymity
7
First Sem 2015-16
Examples
Provider lock-in from IP addressing
Incorporate mechanisms that make it easy for a
host to change address
Like you can change cell phone carrier without
changing your cell phone number
Value pricing
Divide customers based on their willingness to pay
Pay higher rate to run a server at home
10
First Sem 2015-16
New Principles?
Design for variation in outcome
Challenges
Flexible designs will be complex
Applications should be written to deal with this complexity
Innovations will be slow
13
BITS Pilani, Pilani Campus
Examples
Isolate tussles
QoS designs uses separate ToS bits instead of overloading
other parts of packet like port number
Separate QoS decisions from application/protocol design
14
First Sem 2015-16
Enough Patchwork ?
Original simplicity is changing
Hourglass approach
Why?
New class of applications
Real time, multimedia, content distribution, 3D immersive,
cloud services etc.
Next
Future Internet Design Project: Named Data
Networking
[CH-4]
Compulsory Readings
Named Data Networking (NDN) Project [L Zhang 2010]
16
First Sem 2015-16
Mobility
Identity and location in one (IP Address) makes mobility
complex
Energy
Assumes live and awake end systems
Communication can happen only when both ends are awake
Symmetric protocols
No difference between a PDA and a big server
Stateless
QoS is difficult
Some applications guarantees about the delay and
throughput of their flows
Security
In Original Internet it works as an Overlay not an
integral part of it
Technical aspects encryption, authentication,
authorization
Non-Technical aspects to provide trustworthy
interface among the participants
First Sem 2015-16
21
22
First Sem 2015-16
European Union
7th Framework program
24
NDN Architecture
NDN Architecture -1
Communication is driven by the receiver
Sends interest packet
/pilani/computerscience/courses/acn.htm
31
First Sem 2015-16
NDN Architecture -2
NDN routers keep both Interests and Data for some
period of time.
To serve consumers with same interests
NDN Architecture -3
NDN Supports following inherently
Content Distribution (many users are requesting
the same data at different times)
Multicast (Many users are requesting same data at
same time)
Mobility (users requesting data from different
locations)
Delay Tolerant Networking (Users having
intermittent connectivity)
33
First Sem 2015-16
Question?
How to achieve content access control and Infrastructure
security..?
34
First Sem 2015-16
Routing
IP Prefixes Name Prefixes
Existing routing protocols can be used to construct FIB
table
Question..?
How to keep routing table sizes scalable for unbounded
data names
NDN names are longer than IP addresses, but the hierarchical
structure helps the efficiency of lookup and global accessibility
of the data.
35
First Sem 2015-16
Privacy Protection
No information about Who requested what data
36
First Sem 2015-16
Thank You!
37
First Sem 2015-16