1 / 34

Service-enabled Networks From The Network to My Network

Explore the evolution of network technology, from traditional networks to service-enabled networks that bring more capacity, quality, and faster cycle times. Discover the opportunities for intelligent edge adaptation, the need for software reuse, and the impact of hardware innovations. Learn about the future of network services and the potential for entrepreneurs to create high-value services within a programmable network infrastructure.

emmittk
Download Presentation

Service-enabled Networks From The Network to My Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service-enabled NetworksFrom The Network to My Network

  2. Four wheels traction CAGR to 2001 Internet Telephony Bring more quality Optical Internet Bring more capacity eBusiness Bring faster cycle times Wireless Internet Extend reach

  3. What’s the scoop—the techies’ view Very high-value traffic coexists with low value, low pay off traffic, all within the same commodity infrastructure TTM and product cycles make software reuse a must—enough stovepipes, layers are back with a vengeance! Increasingly, “impedance mismatches” in the network generate opportunities for intelligent edge adaptation Network wires are now much faster than I/O busses—it’s time to bring the optical revolution into servers/storage Standardization lags behind the mighty innovation curve— the IETF process hardly matches a trillion dollar business

  4. What’s the scoop—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 Hardware innovations are fueling a steep innovation curve— what a great time for disruptive technologies to snowball! 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

  5. Inflection points we left behind (1) Voice & Data Capacity in Mbps Source: Mutooni & Tennenhouse, MIT, Jan 1998

  6. Inflection points we left behind (2) 10,000 OC 192 10 Gbit/s 1,000 Ethernet 1 Gbit/s Aggregate Bandwidth (MB/s) 100 I/O Buses Internet Backbone T3 10 1 1986 1988 1990 1992 1994 1996 1998 2000 2002

  7. Global Internet Hosts (000s) 1989-2006 Inflection points ahead of us (1) 360 Million users Source: Vint Cerf, MCI Worldcom, Jan 2000

  8. Inflection points ahead of us (2) Incomplete transformation; the inflection point is quickly approaching … Network & Mgmt services ? Embedded OS System ASICs 3Com Cisco Juniper Nortel Horizontal Network Industry ‘00 Vertical Network Industry

  9. 2001’sThin Client Thick Server 1996-2000Thick Client Thick Server 1986-1995Thick Client Thin Server 1970-1985Dumb Terminal Mainframe Inflection points ahead of us (3) 2001’sThin ClientSmart NetworkServer FarmsData Farms 2000’sThin Client Thick Server

  10. 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. Much like … 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

  12. Analogy terminals in airports, railways, roads fleet, personnel parcels APIs and resources in telephones, routers, switches Ubiquitous, shrink-wrapped software PDUs (meeting the various SLAs)

  13. Service 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. 2) ABS detect lockups and will pump brakes 1) Brake! Why inside the network and not e2e? ABS brakes are a Turing machine exploiting locality

  15. Why inside the network and not e2e? (2) • Fan-in/fan-out • Centralization/De-centralization • Visibility • Affinity with data that only lives in the network • Localization

  16. Location, 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. 7 7 Application Application 7 7 Application Application 6 6 Presentation Presentation Presentation Presentation 6 6 Session Session Session Session 5 5 5 5 Transport Transport Transport Transport 4 4 4 4 Network Network Network Network 3 3 3 3 Link Link Link Link 2 2 2 2 Physical Physical 1 1 Physical Physical 1 1 7 6 proxies 5 4 new world 3.5 2.5 2.5 2 2 2 1 1 1 routing switch (many) edge router (few) routing switch (many) Where have you gone, network layer? 3 old world 2 1 routers

  18. Proprietary Apps Proprietary NOS ASICs/Processors Emancipation of arouter It all started from old-world, vertically-integrated code

  19. N 1 Routing N k Protocol r o M 1 w e O m N Management a r F System Interface s Agents C O Manager e c 1 i N v r e 1 N S Routing m Table Forwarding Engine e t s Manager y M S C M Forwarding Engine Interface ASICs/Processors FC FM 1st Degree of emancipation Introverted APIs emerge Modular code is native, local, and trusted. WAT port required

  20. N 1 Routing N k Protocol r o M 1 w e m O N a Management r F System Interface s Agents e C O Manager c 1 i v N r e S 1 N Routing m e Table t s Manager y S M C M Forwarding Engine Interface FC FM 2nd Degree of emancipation ISV’s Software Extroverted APIs Extroverted APIs expose object capabilities to ISV code ISV code is a local, native, and trusted .DLL; loaded WAT APIs Introverted APIs Forwarding Engine ASICs/Processors

  21. N 1 Routing k N Protocol r o M 1 w e m O N a Management r F System Interface s e Agents C O Manager c 1 i v N r e S 1 N Routing m e Table t s Manager y S M C M Forwarding Engine Interface FC FM 3th Degree of emancipation ISV’s Software Extroverted APIs extend a commodity Java runtime ISV code is local/non-local, non native, non trusted, and is loaded on demand JAPIs Extroverted APIs JVM APIs Introverted APIs Forwarding Engine ASICs/Processors

  22. ISV’s Software ISV’s Software N 1 Routing k N Protocol r o M 1 w e m O N a Management r F System Interface s e Agents C O Manager c 1 i v N r e S 1 N Routing m e Table t s Manager y S M C M Forwarding Engine Interface FC FM 4th Degree of emancipation ISV’s Software ISV code is local/non-local, non native, non trusted, loaded on demand, and can teleport itself JAPIs Extroverted APIs JVM APIs Introverted APIs Forwarding Engine ASICs/Processors

  23. Top 5 Challenges to Service-enablement 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? Programmable Nodes community Active Networks community Akamai-like infrastructures Jain Intel’s Phoenix platform Lucent’s softswitch Nortel’ s openet.lab platform

  25. Programmable 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 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 overlap Active Networks Programmable Nodes Manufacturers extend routers Users extend routers ISP extend routers

  28. Nortel’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. Stockwatch Client Presentation Objects Stockwatch Server Biz logic Objects Intranet Stock-history DB Data Objects Real-time Database Object Directory Internet Service-enabled Network Flashcards (1) • Object Ref. Caching • Obj. Load-balancing • Connection Pooling • Preferential QoS • Access Policy • Push for DB Sync. Client Client Client Client Client Client Client

  30. P S T N Internet Internet Service-enabled Network Flashcards (2) Service Provider: - Directory - Bank - Etailer - ASP Content Provider

  31. Service-enabled Network Flashcards (3) Planning higher goodput Surveillance Auditing higher goodput Census Billing AccountingApplications Network Nodes Accounting Server • Activated edge nodes are taught to prep accounting data and peer ad-hoc accounting protocols

  32. 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! Conclusion

  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

  34. Q&A

More Related