ALTO Protocol draft-penno-alto-protocol-03 Presenters R Alimi R Penno

ALTO Protocol draft-penno-alto-protocol-03 Presenters: R. Alimi, R. Penno Current Design Team working on the draft: Richard Alimi, Reinaldo Penno, Stefano Previdi, Albert Tian, Yu-Shun Wang, Y. Richard Yang Grateful to the contributions of a large number of collaborators; Complete list please see draft. 7/28/09 ALTO/IETF 75

Outline Design history Basic concepts Protocol framework Use cases Next step 7/28/09 ALTO/IETF 75 2

Design history IETF-74 Between IETF-74 and IETF-75 Merged P 4 P and Info. Export Merged ATTP Merged Query-Response Merged DNS based Net. Location Service Merged Proxidor IETF-75 7/28/09 Today… ALTO/IETF 75 3

Contributing Proposal: P 4 P • [draft-p 4 p-framework-00, draft-wang-alto-p 4 p-specification 00] – • Key Features – – – 7/28/09 R. Alimi, D. Pasko, L. Popkin, Y. Wang, Y. R. Yang Theoretical foundation based on primal-dual decomposition Network Map and Cost Map PIDs and Grouping Tracker-based selection RESTful URLs and Text encoding Leverage P 2 P caching (extension) ALTO/IETF 75 4

Contributing Proposal : Info. Export • [draft-shalunov-alto-infoexport-00] – • Key Features – – – 7/28/09 S. Shalunov, R. Penno, R. Woundy Cost Map PIDs and Grouping Client-based selection HTTP Transport and Text encoding Leverage P 2 P caching (extension) IP/ASN mapping (extension) ALTO/IETF 75 5

Contributing Proposals: Proxidor • [draft-akonjang-alto-proxidor-00] – – • Key Features – – 7/28/09 O. Akonjang. A. Feldmann, S. Previdi, B. Davie, D. Saucez Drawn from merged proposals • DT Oracle, Cisco Proximity Engine, UCL-Belgium IDIPS Cost types Path ranking • Addresses and groupings Include P 2 P caches in ranked lists (extension) ALTO Info derived from routing protocols/policies ALTO/IETF 75 6

Contributing Proposal : Query/Response • [draft-saumitra-alto-queryresponse-00, draft-saumitra-altomulti-ps-00 ] – • Query/Response – – – 7/28/09 S. Das, V. Narayanan, L. Dondeti XML/Text encoding Cost constraints Service Configuration (now Server Capability) Overlay ID (now type of Endpoint) Multi-homed clients (extension) Client Feedback (extension) ALTO/IETF 75 7

Contributing Proposal : ATTP • [draft-zhang-alto-attp-02] – • Key Features – – – 7/28/09 Y. Zhang, H. Liao, N. Zhou Discovery of tracker (done by Server Capability query) Leverage P 2 P caching (extension) Client feedback (extension) ALTO/IETF 75 8

Contributing Proposal: DNS based Net. Location Service • Presentation at IETF 74 - Syon Ding • Key features – Location – Potential extension to support info through hierarchy aggregation 7/28/09 ALTO/IETF 75 9

Outline Design history - Basic concepts Protocol framework Use cases Next step 7/28/09 ALTO/IETF 75 10

Concept: my-Internet View node 5 node 3 node 1 Defined by ALTO Server Defines set of Network Locations node 2 node 4 node 6 node 7 7/28/09 ALTO/IETF 75 Intradomain External Defines generic costs amongst network locations 11

Concept: Hosting ALTO Server ALTO Client Resource Consumer (1) Alice Join (4) (2) Alice? (3) Request info alto. isp-a. net ALTO Service Discovery 7/28/09 ALTO Server alto. isp-a. net ALTO/IETF 75 Resource Consumer's Hosting ALTO Server determined by Service Discovery my-Internet View from Hosting ALTO Server applied for guidance of Resource Consumer 12

Concept: ALTO Cost Type node 4 Hop-count: 2 Air-miles: 1500 Routing Cost: 684 ALTO Server may define multiple costs between pair of network locations Each cost distinguished by Type node 3 7/28/09 ALTO/IETF 75 13

Concept: Location Grouping ALTO Server ALTO Information Resource Consumers Alice Network Locations may indicate set of locations Coarse-grained proximity Scalability and Privacy Barbara cost=10 cost=15 cost=90 Resource Providers 7/28/09 ALTO/IETF 75 14

Outline Design history Basic concepts - Protocol framework Use cases Next step 7/28/09 ALTO/IETF 75 15

ALTO Protocol Scope ALTO Protocol defines communication between ALTO Client and ALTO Server Routing Protocols ALTO Client ALTO Server ALTO Protocol Dynamic Network Info . . . ALTO Service Discovery 7/28/09 Provisioning Policy ALTO/IETF 75 16

ALTO Service Model ALTO Server provides ALTO Information to ALTO Clients Indicates preferences amongst Resource Consumers and Resource Providers ALTO Client (P 2 P Tracker) ALTO Client (P 2 P Client) Resource Consumers and Providers ALTO Server 7/28/09 ALTO/IETF 75 17

ALTO Query Types Generic and extensible query framework Four types of queries 7/28/09 ALTO capability query Endpoint property lookup service [IP, property] -> value Property can be, e. g. , Location definition, Connectivity type (e. g. , ADSL, 512 Kup/2 Mdown), Usage (e. g. , client usage cap; current usage), Devices (e. g. , caches/Gateway) Network property reverse mapping service E. g. , Location -> list of IP prefixes in a location Path property service E. g. , inter-location path cost/distance ALTO/IETF 75 18

ALTO Protocol Design Focus on Network Map: an endpoint property 7/28/09 Path Rating: a path property to indicate preference of communication patterns ALTO/IETF 75 19

Network Map • Grouping indicated by an endpoint property Set of groupings is called Network Map – • Network-agnostic – – – 7/28/09 Net. Loc: PID 1 PID: identifier for a group – Network Map 128. 36. 0. 0/16 Endpoint: 128. 36. 9. 8 130. 132. 0. 0/16 Subnet, set of subnets, metro area, Po. P, AS, etc Net. Loc: PID 2. . . Net. Loc: PID 3. . . Endpoint: 130. 132. 10. 5 Indicates coarsegrained proximity Scalability and privacy ALTO/IETF 75 ALTO 20

Network Map Queries Endpoint PID Query: Lookup PIDs for set of endpoints Input Set of endpoints Output PID for each endpoint Reverse Network Map Query: Find set of Endpoints within PIDs Input Set of PIDs Output Set of Endpoints within each PID ALTO 7/28/09 ALTO/IETF 75 21

Path Rating Property indicating rating of path between network locations (endpoints or PIDs) Rating is conveyed by Path Costs Type: What the cost represents Air miles, hop count, routing cost, etc Mode: Interpretation of the cost Numerical or ordinal (ranking) 7/28/09 ALTO/IETF 75 22

Path Rating Query: Lookup costs among network locations Input Cost type and mode List of source network locations List of destination network locations Constraints (optional) 7/28/09 Output Cost Map containing costs among each source/destination pair ALTO/IETF 75 23

Protocol Message Encoding Employ HTTP – Wide infrastructure support, implementations – Authentication/encryption in HTTP and SSL REST-ful API – Simple; HTTP caching Currently use XML encoding 7/28/09 ALTO/IETF 75 24

Outline Design history Design requirements and basic concepts Protocol framework - Use cases Next step 7/28/09 ALTO/IETF 75 25

Use Case 1: ALTO Client Embedded in App. Tracker 7/28/09 ALTO/IETF 75 26

ALTO Server (alto. isp. net: 80) Retrieve Server Capability GET /capability ALTO Client @app. Tracker 7/28/09 ALTO/IETF 75 27

ALTO Server (alto. isp. net: 80) Retrieve Network Map GET /prop/pid ALTO Client @app. Tracker 7/28/09 ALTO/IETF 75 28

ALTO Server (alto. isp. net: 80) Retrieve Cost Map GET /cost/map ALTO Client @app. Tracker 7/28/09 ALTO/IETF 75 29

ALTO Info ALTO Server (alto. isp. net: 80) ALTO Client @app. Tracker get peers selected peer list Peer 1 Peer 2 7/28/09 Peer 40 ALTO/IETF 75 … 30

Use Case 2: ALTO Client Embedded in a P 2 P Client 7/28/09 ALTO/IETF 75 31

ALTO Server (alto. isp. net: 80) P 2 P Client (in PID 1) Retrieve Server Capability GET /capability 7/28/09 ALTO/IETF 75 32

ALTO Server (alto. isp. net: 80) P 2 P Client (in PID 1) Retrieve Network Map GET /prop/pid 7/28/09 ALTO/IETF 75 33

ALTO Server (alto. isp. net: 80) P 2 P Client (in PID 1) Retrieve Cost Map GET /cost/row? srcpid=PID 1 7/28/09 ALTO/IETF 75 34

ALTO Info ALTO Server (alto. isp. net: 80) P 2 P Client Peer Exchange DHT 7/28/09 ALTO/IETF 75 P 2 P Client (in PID 1) new peers Tracker 35

Use Case 3: ALTO Client Embedded at a P 2 P Client using Ranking 7/28/09 ALTO/IETF 75 36

ALTO Server (alto. isp. net: 80) P 2 P Client (in PID 1) Retrieve Server Capability GET /capability 7/28/09 ALTO/IETF 75 37

ALTO Server (alto. isp. net: 80) Request Ranking POST /cost/m? mode=ordinal HTTP/1. 1. . . (contains src & dest addresses) P 2 P Client (in PID 1) 7/28/09 ALTO/IETF 75 38

Outline Design history Design requirements and basic concepts Protocol framework Use cases - Next step 7/28/09 ALTO/IETF 75 39

Next Steps Adoption as WG document Discussions on possible extensions 7/28/09 ALTO/IETF 75 40

Extensions ALTO Info Caching / Redistribution Mechanisms ALTO Info served by existing HTTP caches ALTO Clients redistribute amongst themselves Improves scalability Example: millions of viewers beginning to watch the same live streaming event Hierarchical Groupings (PIDs) Allow hierarchy of PIDs (Group IDs) for finer accuracy when desired 7/28/09 ALTO/IETF 75 41

Extensions ALTO Client feedback Allow clients to feed back information to ALTO Service Improve ALTO info Examples: ATTP, Query/Response 7/28/09 ALTO/IETF 75 42

Thank you! 7/28/09 ALTO/IETF 75 43