1 / 14

Three Points to Remember

Three Points to Remember. Active Networks Are Cool Active Networks Can Be At Least As Secure As Legacy Networks ;) Data and Algorithm Are Mutable Active Networks. Introduction. http://www.darpa.mil/ato/programs/activenetworks/actnet.htm Email List: activenets_wire@ittc.ukans.edu.

fpaul
Download Presentation

Three Points to Remember

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. Three Points to Remember • Active Networks Are Cool • Active Networks Can Be At Least As Secure As Legacy Networks ;) • Data and Algorithm Are Mutable Active Networks Introduction

  2. http://www.darpa.mil/ato/programs/activenetworks/actnet.htm • Email List: activenets_wire@ittc.ukans.edu Motivation for Active Networking • Faster Hardware Not Fully Utilized • Enables More Flexible Network • De-couples Protocol From Transport • Minimizes Requirements for Global Agreement • Enables On-the-fly Experimentation • Enables Faster Deployment of New Services Introduction

  3. Active Networking: A Natural Evolution Traditional Packet Network Header Data Adaptive Monitoring, And Predictive Control Devices Become Network-aware and Smart Network-Aware Devices Active Network Header Code Data Custom Code Injected By Applications/devices Makes Network Intelligent Reduces Protocol Deployment Time From Years to Months Introduction

  4. Change Is Inevitable Internet Protocol Active and Programmable Networks • Fossilized: Resistant to Change • Layers of Complexity O(4000) RFCs • Inability to Customize Quickly or Efficiently • Lack of Security Paradigm • Downward Side of the Innovation Curve • Built for Change • Reduced Complexity • Rapid, Efficient Customization • Security Paradigm Built-in • Upward Innovation Path Introduction

  5. Discrete Approach Programs (P) Injected Into Active Nodes Separately From Passive Data (D) Integrated Approach Programs Integrated Into Every Packet Along With Passive Data Integrated Versus Discrete Approaches P D P D D P D P Active Network Node Introduction

  6. Section 1 Active Network Framework

  7. Legacy Co-Existence Host Active Router Legacy Router Active Router Host ip_active ip_active Cut-through Cut-through Sect. I: Framework

  8. Active Network Framework • Active Application (AA) • The active network application • Execution Environment (EE) • Analogous to a Unix shell in which to execute a packet • Node Operating System (NodeOS) • Operating System support for Execution Environments AA AA AA AA EE 1 EE 2 NodeOS Hardware Sect. I: Framework

  9. Active Network Framework • Primary Focus Is Communication and Not Computation • Packet Is Unit of Multiplexing • No Assumptions About Underlying Forwarding Technologies Sect. I: Framework

  10. Active Network Framework Execution Environment ... Management EE EE 1 EE 2 IPv6 Security Enforcement Engine NodeOS ... ... Policy db Channels Store Active Network Working Group Version 1.0, Ken Calvert ed. Active Network Framework. http://www.cc.gatech.edu/projects/canes/arch/arch-0-9.ps, August 31 1998. Version 0.9.", citeseer.nj.nec.com/group98architectural.html. Sect. I: Framework

  11. Framework Considerations (I) • End Systems (ES) and Intermediate Systems (IS) • No Architectural Differences Between EEs and ISs. • Execution Environment (EE) and Active Application (AA) • AA Implements an End-to-end Service Executed Within an EE Sect. I: Framework

  12. Framework Considerations (III) • Node Operating System (NodeOS) • Primary Role Is Mediator of Node Resources to the EEs • Security • All Requests to the NodeOS Are Verified Based Upon Credentials Sufficient to Verify Authorized Access • EEs Must Trust NodeOS and Can Add Stricter Policies • NodeOS May Trust Some EEs More Than Others Sect. I: Framework

  13. Active Network Framework IP|UDP|ANEP EE 1 UDP|IP sched IP|UDP|ANEP ANEP|IP IP|UDP UDP|IP EE 2 IP sched classify IP IP IP|ANEP ANEP|UDP|IP IPv4 sched (Cut-through) EE 3 IP IP Packet Classification Input Channel Processing EE Processing Output Channel Processing Scheduling and Transmission Active Network Working Group Version 1.0, Ken Calvert ed. Active Network Framework. http://www.cc.gatech.edu/projects/canes/arch/arch-0-9.ps, August 31 1998. Version 0.9.", citeseer.nj.nec.com/group98architectural.html. Sect. I: Framework

  14. Hardware Reference Model output ports input ports Switch Fabric Passive EE EE EE input ports output ports Switch Fabric Active Active Network Working Group Version 1.0, Ken Calvert ed. Active Network Framework. http://www.cc.gatech.edu/projects/canes/arch/arch-0-9.ps, August 31 1998. Version 0.9.", citeseer.nj.nec.com/group98architectural.html. Sect. I: Framework

More Related