draft gu alto redistribution n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
draft-gu-alto-redistribution PowerPoint Presentation
Download Presentation
draft-gu-alto-redistribution

Loading in 2 Seconds...

play fullscreen
1 / 14

draft-gu-alto-redistribution - PowerPoint PPT Presentation


  • 81 Views
  • Uploaded on

draft-gu-alto-redistribution. Y.J. Gu Richard Alimi Roni Even. Review on Basic Information. Basic Requirements 1. The ALTO Client should be able to identify the desired redistributed data . 2. The ALTO Client should be able to check the validity of the information .

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'draft-gu-alto-redistribution' - lolita


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
draft gu alto redistribution

draft-gu-alto-redistribution

Y.J. Gu

Richard Alimi

Roni Even

review on basic information
Review on Basic Information
  • Basic Requirements
    • 1. The ALTO Client should be able to identify the desired redistributed data.
    • 2. The ALTO Client should be able to check the validity of the information.
  • Redistributable Information
    • Server Capability
    • Full Network Map
    • Full Path Cost Map among all PIDs
scheme design questions
Scheme Design Questions
  • How could peers decide whether to get ALTO Information from ALTO Server or to get from other clients?
  • How could peers locate redistributed Information?
  • What protocol is used for retrieving redistributed Information?
  • How to update the Redistributed Information on time and who is responsible for updating.
significant changes from ietf77
Significant Changes from IETF77
  • Divide Redistribution Flow into two parts and introduce options for each part
    • Draft should be further updated
  • For each of them, analyze the benefits and the requirements for ALTO system.
redistribution architecture

ALTO Client

P2P/ALTO

Client

P2P/ALTO

Client

Redistribution

Proxy (RProxy)

ALTO Server

Redistribution Architecture

PUSH / PULL

1) Get server list

and Public Key

1) Get Public Key

2) PULL

2) PUSH

Overlay

slide6

Redistribution Proxy (RProxy):

    • ISP deployed
    • App. deployed, e.g. Tracker or Supernode
  • Used to receive and redistribute ALTO Information
communication between alto server and rproxy

ALTO Client

P2P/ALTO

Client

P2P/ALTO

Client

Communication between ALTO Server and RProxy

ALTO Server

PUSH / PULL

1) Get server list

and Public Key

1) Get Public Key

2) PULL

Redistribution

Proxy (RProxy)

2) PUSH

Overlay

communication between alto server and rproxy1
Communication between ALTO Server and RProxy
  • Two options:
    • PULL: RProxy ask for the ALTO Infor. frequently, or when expired.
    • PUSH: ALTO Server send updated Infor. to RProxy as soon as the Infor changed.
  • RProxy runs ALTO Protocol
pull from rproxy

ALTO Client

P2P/ALTO

Client

P2P/ALTO

Client

PULL from RProxy

ALTO Server

PUSH / PULL

1) Get server list

and Public Key

1) Get Public Key

2) PULL

Redistribution

Proxy (RProxy)

2) PUSH

Overlay

pull from rproxy1
PULL from RProxy
  • Step 1: Client requests Server Capability from ALTO Server and server responses with Server List, which includes its Public key and the URL of RProxy. Afterwards client will ask the URL for ALTO infor., without judging it's an ALTO Server or a RProxy. ALTO Protocol is used.
  • Step 2: Client connects with an URL in the list and requests for ALTO Infor. ALTO Protocol is used.
  • Setp 3: If RProxy hasn't this required Infor., it pulls the infor from ALTO Server.
push from rproxy

ALTO Client

P2P/ALTO

Client

P2P/ALTO

Client

PUSH from RProxy

ALTO Server

PUSH / PULL

1) Get server list

and Public Key

1) Get Public Key

2) PULL

Redistribution

Proxy (RProxy)

2) PUSH

Overlay

push from rproxy1
PUSH from RProxy
  • Suitable for P2P Application, e.g. PPLive.
  • Step 1: Client requests Server Capability from ALTO Server and server responses with its Public key. ALTO Protocol is used.
  • Parellel Step 1: RProxy publishes ALTO Infor. into Overlay, using P2P Protocol.
  • Step 2: Client looks up for ALTO Infor. in the Overlay, using P2P Protocol.
  • Setp 3: If fails to find in the Overlay, it follows the steps in PULL Case.
slide13
Make no decision on which scheme wins. Leave it as an implementation design choice based on the concrete situations.
  • Detail mechanism will update align with ALTO Protocol.
slide14

1) Does the WG recognize a need for a document discussing design and implementation considerations for redistribution?2) If yes, what is the suggested way to progress the document?