making internet work for us all

8/10/2019 Making Internet Work for Us All

1/38

1 2002, Cisco Systems, Inc. All rights reserved.JGN Conference 2002Research Directions

Research Directions: Makingthe Internet work for everyone

Fred Baker

Cisco Systems

Internet Society


2/38

222 2002, Cisco Systems, Inc. All rights reserved.Research Directions

The ubiquitous Internet

Who is everyone?

The theory

If you are a person, you are included

The reality

Limited by geography, connectivity, culture,

and cultural taboos

Many find little need for the Internet, because ithas not been made useful to them


3/38


Issue: QoS in Access Networks

What is the single biggest impediment tofilling up backbone networks?

Getting data out of the access network

onto the backbone!


4/38


Home network diagram

The Internet

As seen through Cox Cable

Hitachi Cable modem

Required/Supplied by Cox

Cisco 2600IOS CBAC Firewall+NAT

Cisco 2924

Family equipment

Includes private servers

VPN 3002ECS VPN Pilot

Currently unused

Cisco 806Stealth software/configuration

Office Equipment

NetGear AP


5/38


Big picture network diagram

Stepdown to ~128 KBPS(actually ~160 KBPS)upstream and downstream

QoS Requirements

Priority Queuing (EF) for VoIP

traffic shaping to control rate atmodem to avoid long FIFO eitherdirection

Cox Cable

Network

AT&T IP Network

(ip.att.net)

Stealth

Network

Stealth

Network


6/38


Worst case round trip delays on pings


7/38


8/38


Delays within a VPN


9/38


Resolving QoS issues

Just add bandwidth is not reality inaccess networks (but it sure helps)

It costs too much money for SOHO

Voice need priority

Video needs bandwidth allocation


10/38


Making the Internet available

More generally:

Most Internet users have no need to know itsinternals

Having to understand these issues is irksometo them

The complexity causes lack of robustness intheir ability to use the network


11/38


Kinds of technologies to exploit formere mortals

Technologies that deliver high speed

inexpensively

Technologies that are relatively simple todeploy and maintain by non-experts

Technologies that make power of theInternet accessible to non-technical users


12/38


13/38


User interface issues

English is not necessarily suitable

Language independence

Illiterate or unsophisticated users

Emphasize

Graphics

Intuitive options and messages

Speech as input or output

Responsiveness


14/38


Responsiveness as an issue

Human response to delay tends to beanger

Youre not listening to me

This isnt worth the time or effort

Examples:

Voice/Video coding of interactive exchanges

Database applications


15/38


16/38


Example: Database applications

Expense Reports, calendars, LDAPapplications

Important thing is user satisfaction,

getting something done


17/38


ISPEnterprise Service Models

Issue:

How can we provide connectivity for peer-to-

peer applications spanning multiple privatenetworks?

Pick one:

Application issues resulting from NetworkAddress Translation

Give us more addresses


18/38


19/38


20/38


21/38


Peer-peer access control model

Let everyone talk

Distributed computing

Peer computers to performfunction, not server

Central Authentication/Authorization

Access control

Accountability


22/38


23/38


24/38


25/38


0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

1980 1985 1990 1995 2000 2005 2010

Address allocations

Today: 60% allocated

CERNET

could use 72 /8's ifthey were available

Population is > 320M,

ARIN

Today manages 75 /8's

population ~ 300M

Five years for sure;

But effectively out today Source: RFCs, Scott Marcus, IANA

Analysis done by Tony Hain


26/38


27/38


28/38


29/38


30/38


31/38


32/38


Intrusion/attack detection/avoidance

A service that a service provider offers

Requirements:

Detect attacks in real time

Isolate legitimate traffic from attack traffic

Potential Solutions:

Application layer identifies golden streams?

Lower layer detects onset of loss?


33/38


34/38


Fast routing convergence

Algorithms to promote convergence

DUAL, Sequence-numbered announcements

To routes that deliver performance, notjust connectivity

Best Exit, not Nearest Exit

Global algorithm improvements

Map-based architectures

Explicit routing of traffic

Multi-provider SLAs


35/38


36/38


37/38


38/38

making internet work for us all

Documents