scion architecture overview
play

SCION: Architecture Overview Adrian Perrig Network Security Group, - PowerPoint PPT Presentation

SCION: Architecture Overview Adrian Perrig Network Security Group, ETH Zrich SCION Project Team SCION: S calability, C ontrol, and I solation O n N ext-generation networks Core team: Daniele Asoni, Chen Chen, Laurent Chuat, Sergiu


  1. SCION: Architecture Overview Adrian Perrig Network Security Group, ETH Zürich

  2. SCION Project Team ▪ SCION: S calability, C ontrol, and I solation O n N ext-generation networks ▪ Core team: Daniele Asoni, Chen Chen, Laurent Chuat, Sergiu Costea, Sam Hitz, Tobias Klausmann, Tae-Ho Lee, Chris Pappas, Adrian Perrig, Benjamin Rotenberger, Stephen Shirley, Jean-Pierre Smith, Pawel Szalachowski, Brian Trammell, Ercan Ucan 2

  3. Some Terminology ▪ Autonomous System (AS): network under a single administrative control ▪ Examples: Internet Service Provider (ISP), university, corporation ▪ Control plane: network functions to explore and disseminate reachability information ▪ Data plane: network functions to forward a packet 3

  4. SCION Architectural Design Goals ▪ High availability, even for networks with malicious parties • Adversary: access to management plane of router • Communication should be available if adversary-free path exists ▪ Secure entity authentication 
 that scales to global heterogeneous (dis)trusted environment ▪ Flexible trust: operate in heterogeneous trust environment ▪ Transparent operation: clear what is happening to packets and whom needs to be relied upon for operation ▪ Balanced control among ISPs, senders, and receivers ▪ Scalability, efficiency, flexibility 4

  5. SCION Overview ▪ Control plane: How to find and disseminate paths 
 [Chapter 2.1] ▪ Path exploration ▪ Path registration ▪ Data plane: How to send packets [Chapter 2.2] ▪ Path lookup ▪ Path combination 5

  6. Approach for Scalability: Isolation Domain (ISD) ▪ Isolation Domain (ISD): grouping of ASes ▪ ISD core: ASes that manage the ISD ▪ Core AS: AS that is part of ISD core ▪ Control plane is organized hierarchically ▪ Inter-ISD control plane TRC ▪ Intra-ISD control plane TRC TRC TRC TRC 6

  7. Intra-ISD Path Exploration: Beaconing ▪ Core ASes K, L, M initiate Path-segment Construction Beacons (PCBs), or K M L “beacons” ▪ PCBs traverse ISD as a flood N P O to reach downstream ASes ▪ Each AS receives multiple S Q PCBs representing path R segments to a core AS 7

  8. Up-Path and Down-Path Segments ▪ Intra-ISD beaconing process sends PCBs to ASes ▪ PCBs contain path segments that K M can be used as communication paths L to communicate with the core AS that initiated it N P ▪ Up-path segment: PCB is used from O AS to core AS ▪ Example: R → K S Q ▪ Down-path segment: PCB is used R from core AS to AS ▪ Example: M → S 8

  9. Inter-ISD Path Exploration: 
 Sample Core-Path Segments from AS T I J T U A B V K M Y Z W L X C E C’ N P D B’ O A’ F H E’ D’ S Q G R 9

  10. Path Server Infrastructure ▪ Each AS operates path server(s) ▪ Path servers offer lookup service: ▪ ISD, AS → down-path segments, core- K M path segments L ▪ Local up-path segment request → up- path segments to core ASes N P ▪ Core ASes operate core path server O infrastructure ▪ Each non-core AS runs local path servers S Q ▪ Serves up-path segments to local clients R ▪ Resolves and caches response of remote AS lookups Path server 10

  11. Up-Path Segment Registration ▪ AS selects path segments to announce K M as up-path segments L for local hosts ▪ Up-path segments are N P O registered at local path Path server servers S Q R 11

  12. Down-Path Segment Registration ▪ AS selects path Core segments to announce path server K M as down-path L segments for others to use to communicate N P with AS O ▪ Down-path segments S Q are uploaded to core R path server in core AS 12

  13. SCION Overview ▪ Control plane: How to find end-to-end paths? ▪ Path exploration ▪ Path registration ▪ Data plane: How to send packets ▪ Path lookup ▪ Path combination 13

  14. Path Lookup ▪ Steps of a host to obtain path segments ▪ Host contacts RAINS server with a name 
 H → RAINS: www.scion-architecture.net 
 RAINS → H: ISD X, AS Y, local address Z ▪ Host contacts local path server to query path segments 
 H → PS: ISD X, AS Y 
 PS → H: up-path, core-path, down-path segments ▪ Host combines path segments to obtain end-to-end paths, which are added to packets 14

  15. Path Lookup: Local ISD ▪ Client requests path segments to <ISD, AS> from local path server ▪ If down-path segments are not locally K M cached, local path server send request L to core path server ▪ Local path server replies N P ▪ Up-path segments to local ISD core O ASes S Q ▪ Down-path segments to <ISD, AS> ▪ Core-path segments as needed to R connect up-path and down-path segments 15

  16. Path Lookup: Remote ISD ▪ Host contacts local path server requesting <ISD, T U AS> ▪ If path segments are not cached, local path V K M server will contact core Z Y W path server L X ▪ If core path server does C’ not have path segments N P B’ cached, it will contact O A’ remote core path server E’ ▪ Finally, host receives D’ S Q up-, core-, and down- segments R 16

  17. Path Combination Example (1) ▪ Core-segment combination: 
 Up-path segment + 
 core-path segment + 
 K M down-path segment L N P O S Q R 17

  18. Path Combination Example (2) ▪ Peering shortcut: up-path segment and down-path M K segment offer same L peering link N P O S Q R 18

  19. Path Combination Example (3) ▪ Peering shortcut: up-path segment T U and down-path segment offer K M V same peering Y Z W L link X C’ N P B’ O A’ E’ D’ S Q R 19

  20. Path Combination Example (4) ▪ AS shortcut path through common AS on up-path and K M down-path segment L N P O S Q R 20

  21. SCION Summary ▪ Complete re-design of network architecture 
 resolves numerous fundamental problems • BGP protocol convergence issues • Separation of control and data planes • Isolation of mutually untrusted control planes • Path control by senders and receivers • Simpler routers (no forwarding tables) • Root of trust selectable by each ISD ▪ An isolation architecture for the control plane, 
 but a transparency architecture for the data plane. 21

  22. For More Information … ▪ … please see our web page: 
 www.scion-architecture.net ▪ Chapter 2 of our book “SCION: A secure Internet Architecture” ▪ Available from Springer this Summer 2017 ▪ PDF available on our web site ▪ More details on beaconing, PCB message formats, security: “Control Plane Overview” video ▪ More details on path lookup, path combination, SCION packet header, in-packet encoding of paths, security: “Data Plane Overview” video 22

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend