1 service-enabled networks service-enabled networks from the network to my network
Post on 26-Dec-2015
213 Views
Preview:
TRANSCRIPT
2
Four wheels tractionFour wheels traction
CAGR to 2001
Internet TelephonyInternet Telephony Bring more quality
Optical InternetOptical InternetBring more capacity
eBusinesseBusinessBring faster cycle times
Wireless InternetWireless InternetExtend reach
3
What’s the scoopWhat’s the scoop—the techies’ —the techies’ viewview
TTM and product cycles make software reuse a must—enough stovepipes, layers are back with a vengeance!
Very high-value traffic coexists with low value, low pay off traffic, all within the same commodity infrastructure
Increasingly, “impedance mismatches” in the network generate opportunities for intelligent edge adaptation
Standardization lags behind the mighty innovation curve— the IETF process hardly matches a trillion dollar business
Network wires are now much faster than I/O busses—it’s time to bring the optical revolution into servers/storage
4
What’s the scoopWhat’s the scoop—the biz view—the biz view
ASPs and eBiz test the market for new services, non stop— many fail, but they’ve thrown a monkey-wrench into the net
Customers demand new soft features in network gear—manufacturers cannot keep up with fast (contrasting) reqs
Personalized customer care stipulations are strategic for customer expansion and customer loyalty
Hardware innovations are fueling a steep innovation curve— what a great time for disruptive technologies to snowball!
5
Inflection points we left behind Inflection points we left behind (1)(1)
Voice & Data Capacity in MbpsVoice & Data Capacity in MbpsSource: Mutooni & Tennenhouse, MIT, Jan 1998Source: Mutooni & Tennenhouse, MIT, Jan 1998
6
Inflection points we left behind Inflection points we left behind (2)(2)
1
10
100
1,000
10,000
1986 1988 1990 1992 1994 1996 1998 2000 2002
Ag
gre
gat
e B
an
dw
idth
(M
B/s
)
Ethernet
Internet Backbone
1 Gbit/s
OC 192
T3
I/O Buses
10 Gbit/s
7
0
200000
400000
600000
800000
1000000
1200000
1400000
1600000
198919901991199219931994199519961997199819992000200120022003200420052006
hosts mobiles
Glo
bal
Inte
rne
t H
ost
s (
000
s)
198
9-2
006
360 Million users
Source: Vint Cerf, MCI Worldcom, Jan 2000Source: Vint Cerf, MCI Worldcom, Jan 2000
Inflection points ahead of us (1)Inflection points ahead of us (1)
8
Incomplete transformation; the inflection point is quickly approaching …
Cisco Nortel Juniper 3Com
Network &Mgmt services
EmbeddedOS
System
ASICs
‘00 Vertical Network Industry Horizontal Network Industry
Inflection points ahead of us (2) Inflection points ahead of us (2)
9
2000’sThin Client Thick Server
2001’sThin Client Thick Server
1996-2000Thick Client Thick Server
1970-1985Dumb Terminal
Mainframe
1986-1995Thick Client Thin Server
2001’sThin Client
Smart Network
Server FarmsData Farms
Inflection points ahead of us (3) Inflection points ahead of us (3)
10
Kiss “The Network” Goodbye!!!Kiss “The Network” Goodbye!!!
How about a “white-sheet” network with nodes exposing programmable control to 3rd party code?
How about passing on to entrepreneurs and service providers the freedom to formulate the high pay-off services for which they have found a market
For this, we will need new levels of abstraction
11
Fred Smith invented the FedEx business in 1973, after recognizing the significance of predictable movement of packages. Smith has always used the same roads, airports, cars, and types of planes as the U.S. Postal Service … but he has programmed his own resources to work in a novel way
Much like …Much like …
12
terminals in airports, railways, roads
fleet, personnel
parcels
AnalogyAnalogy
APIs and resources in telephones, routers, switches
Ubiquitous, shrink-wrapped software
PDUs (meeting the various SLAs)
13
Service samplerService sampler
Entrepreneurs will run code inside the network for:
—Ad-hoc routing or policy definition for VPNs
—New protocol versions or features deployment
—Multicast protocols and support tools instantiation
—Stateful packet capturing; “intrusion detectors with legs”
—Intentional directory services
—Content-sensitive load balancing and caching
—Diagnostic agents (e.g., for loops, SLAs infringements, etc.)
—Customizable IP Accounting (e.g., to support “pay-for-what-u-use”)
14
1) Brake! 2) ABS
detect lockups and will pump
brakes
ABS brakes are a Turing machine exploiting locality
Why inside the network and not Why inside the network and not e2e?e2e?
15
Why inside the network and not Why inside the network and not e2e? (2)e2e? (2)
Fan-in/fan-out
Centralization/De-centralization
Visibility
Affinity with data that only lives in the network
Localization
16
Location, location, locationLocation, location, location
Service-enablement will prove most effective where “impedance mismatches” occur in the network
— Wireline vs. wire-less
— Secure vs. non-secure
— Customer-premises vs. Content-provider-land
— SLA (x) vs. SLA (y)
— Low TCO vs. High TCO
— Resource-constrained vs. unwashed unlimited computing
A service-enabled box can wear multiple hats
17
Where have you gone, network Where have you gone, network layer?layer?
Physical
Link
Network
Transport
Session
Presentation
Application
1
2
3
4
5
6
7
Physical
Link
Network
Transport
Session
Presentation
Application
1
2
3
4
5
6
7
1
2
3
old
wor
ld
routers
Physical
Link
Network
Transport
Session
Presentation
Application
1
2
3
4
5
6
7
Physical
Link
Network
Transport
Session
Presentation
Application
1
2
3
4
5
6
7
new
wor
ld
edgerouter(few)
1
2
2.5
routingswitch(many)
12
2.5
routingswitch(many)
12
3.5
4567
prox
ies
18
Emancipation of aEmancipation of arouterrouter
It all started from old-world, vertically-integrated code
ASICs/Processors
ProprietaryApps
ProprietaryNOS
19
11stst Degree of emancipation Degree of emancipation
Introverted APIs emerge
Modular code is native, local, and trusted. WAT port required
ASICs/Processors
Forwarding Engine
Sy
stem
Se
rvic
es
Fra
mew
ork
RoutingProtocol
1N
RoutingTableManager
Forwarding EngineInterface
SystemManager
ManagementInterfaceAgents
1N
M
M
M
N
O1
ON
C
C
FC
1N
FM
20
2nd Degree of emancipation2nd Degree of emancipation
Extroverted APIs expose object capabilities to ISV code
ISV code is a local, native, and trusted .DLL; loaded WAT
Intr
over
ted
AP
Is
APIs
ASICs/Processors
Forwarding Engine
Syst
em S
ervi
ces F
ram
ewor
k
RoutingProtocol
1N
RoutingTableManager
Forwarding EngineInterface
SystemManager
ManagementInterfaceAgents
1N
M
MM
N
O1
ON
C
C
FC
1N
FM
Ext
rove
rted
A
PIs
ISV’s SoftwareISV’s Software
21
3th Degree of emancipation3th Degree of emancipation
Extroverted APIs extend a commodity Java runtime
ISV code is local/non-local, non native, non trusted, and is loaded on demand
Ext
rove
rted
A
PIs
Intr
over
ted
AP
Is
APIs
ASICs/Processors
Forwarding Engine
Syste
m Se
rvice
s Fram
ewo rk
RoutingProtocol
1N
RoutingTableManager
Forwarding EngineInterface
SystemManager
ManagementInterfaceAgents
1N
M
MM
N
O1
ON
C
C
FC
1N
FM
JVM
JAPIs
ISV’s SoftwareISV’s Software
22
4th Degree of emancipation4th Degree of emancipation
ISV code is local/non-local, non native, non trusted, loaded on demand, and can teleport itself
Ext
rove
rted
A
PIs
Intr
over
ted
AP
Is
APIs
ASICs/Processors
Forwarding Engine
Syste
m Se
rvice
s Fram
ewo rk
RoutingProtocol
1N
RoutingTableManager
Forwarding EngineInterface
SystemManager
ManagementInterfaceAgents
1N
M
MM
N
O1
ON
C
C
FC
1N
FM
JVM
JAPIs
ISV’s SoftwareISV’s Software
ISV’s SoftwareISV’s Software
ISV’s SoftwareISV’s Software
23
Top 5 Challenges to Service-Top 5 Challenges to Service-enablementenablement
What do the APIs look like
Scalability
Service guarantees
Security
“I’ve got a hammer and everything looks like a
nail”
24
Who’s looking into this?Who’s looking into this?
Programmable Nodes community
Active Networks community
Akamai-like infrastructures
Jain
Intel’s Phoenix platform
Lucent’s softswitch
Nortel’ s openet.lab platform
25
Programmable NodesProgrammable Nodes
Current Nodes—Vertically integrated—Primitive scripting
Programmable Nodes—Manufacturers publish extroverted APIs—I can port code and extend such network nodes—Alternately, I can operate the APIs remotely—APIs’ target audience: Manufacturers, ISPs
References—IEEE P1520—Industry alliances
26
Active NetworksActive Networks
Current Networks—Data in the packet, program in the network nodes
—Effective, but inflexible
Active Networks—The program travels with the packet, end-to-end
—Flexible, but ... how about security, interoperability?
—Most ambitious thus far
—Target audience: ISPs, end-users
References—DARPA Active Networks
27
Partial overlapPartial overlap
ActiveNetworks
ProgrammableNodes
Users extend routers
Manufacturers extend routers ISP extend
routers
28
Nortel’s Openet.labNortel’s Openet.lab
It’s an incubator for service-enabled network nodes and sample services
It provides:— JVM-emancipated prototypes of Nortel routers
— Java APIs to MIBs
— Java APIs to Forwarding Planes, packet capturing
— A runtime environment for downloaded code
It’s popular among researchers (DARPA, CSIRO, …)
Free downloads from http://www.openetlab.com
29
Service-enabled Network Flashcards (1)
Stockwatch ClientPresentation Objects
Stockwatch ServerBiz logic Objects
Intranet
Stock-history DBData Objects
Real-timeDatabase
Client
Client
Client
Client
Client
Client
Client
Internet
ObjectDirectory
• Object Ref. Caching• Obj. Load-balancing
• Connection Pooling• Preferential QoS• Access Policy
• Push for DB Sync.
30
Internet
Service Provider:- Directory- Bank- Etailer- ASP
P S T N
Internet
Service-enabled Network Flashcards (2)
Content Provider
31
Billing
Auditing
Planning
Surveillance
Census
Accounting Applications
higher goodput
higher goodput
Accounting ServerNetwork Nodes
Activated edge nodes are taught to prep accounting data and peer ad-hoc accounting
protocols
Service-enabled Network Flashcards (3)
32
ConclusionConclusion
Fast-paced innovations paint an optimal scenario for service-enablement in the network
Service-enablement is an effective way to overcome network “impedance mismatches”
It brings friend-services and friend-content closer; it pushes foes further away
Kiss The Network good bye. It’s My Network now!
33
Closing remark
Back then, thrust wasn’t a problem; control was
Likewise, network bandwidth growth is just fine; control does demand our collective efforts
top related