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

scion architecture overview
SMART_READER_LITE
LIVE PREVIEW

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


slide-1
SLIDE 1

SCION: Architecture Overview

Adrian Perrig Network Security Group, ETH Zürich

slide-2
SLIDE 2

SCION Project Team

▪ SCION: Scalability, Control, and Isolation On Next-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

slide-3
SLIDE 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

slide-4
SLIDE 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

slide-5
SLIDE 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

slide-6
SLIDE 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 ▪ Intra-ISD control plane

6

TRC TRC TRC TRC TRC

slide-7
SLIDE 7

Intra-ISD Path Exploration: Beaconing

▪ Core ASes K, L, M initiate Path-segment Construction Beacons (PCBs), or “beacons” ▪ PCBs traverse ISD as a flood to reach downstream ASes ▪ Each AS receives multiple PCBs representing path segments to a core AS

7

Q R N L S K P O M

slide-8
SLIDE 8

Up-Path and Down-Path Segments

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

8

Q R N L S K P O M

slide-9
SLIDE 9

Inter-ISD Path Exploration:
 Sample Core-Path Segments from AS T

9

Q R V C D F G E H N L S W A B I J Z Y X K P O M T U D’ C’ E’ A’ B’

slide-10
SLIDE 10

Path Server Infrastructure

▪ Each AS operates path server(s) ▪ Path servers offer lookup service: ▪ ISD, AS → down-path segments, core- path segments ▪ Local up-path segment request → up- path segments to core ASes ▪ Core ASes operate core path server infrastructure ▪ Each non-core AS runs local path servers ▪ Serves up-path segments to local clients ▪ Resolves and caches response of remote AS lookups

10

Path server

Q R N L S K P O M

slide-11
SLIDE 11

Up-Path Segment Registration

▪ AS selects path segments to announce as up-path segments for local hosts ▪ Up-path segments are registered at local path servers

11

Q R N L S K P O M

Path server

slide-12
SLIDE 12

Down-Path Segment Registration

▪ AS selects path segments to announce as down-path segments for others to use to communicate with AS ▪ Down-path segments are uploaded to core path server in core AS

12

Q R N L S K P O M

Core path server

slide-13
SLIDE 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

slide-14
SLIDE 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

slide-15
SLIDE 15

Path Lookup: Local ISD

▪ Client requests path segments to <ISD, AS> from local path server ▪ If down-path segments are not locally cached, local path server send request to core path server ▪ Local path server replies ▪ Up-path segments to local ISD core ASes ▪ Down-path segments to <ISD, AS> ▪ Core-path segments as needed to connect up-path and down-path segments

15

Q R N L S K P O M

slide-16
SLIDE 16

Path Lookup: Remote ISD

▪ Host contacts local path server requesting <ISD, AS> ▪ If path segments are not cached, local path server will contact core path server ▪ If core path server does not have path segments cached, it will contact remote core path server ▪ Finally, host receives up-, core-, and down- segments

16

Q R V N L S W Z Y X K P O M T U D’ C’ E’ A’ B’

slide-17
SLIDE 17

Path Combination Example (1)

▪ Core-segment combination:
 Up-path segment + 
 core-path segment + 
 down-path segment

17

Q R N L S K P O M

slide-18
SLIDE 18

Path Combination Example (2)

▪ Peering shortcut: up-path segment and down-path segment offer same peering link

18

Q R N L S K P O M

slide-19
SLIDE 19

Path Combination Example (3)

▪ Peering shortcut: up-path segment and down-path segment offer same peering link

19

Q R V N L S W Z Y X K P O M T U D’ C’ E’ A’ B’

slide-20
SLIDE 20

Path Combination Example (4)

▪ AS shortcut path through common AS on up-path and down-path segment

20

Q R N L S K P O M

slide-21
SLIDE 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

slide-22
SLIDE 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