10
ECE 544 Project3 Team member

ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Embed Size (px)

Citation preview

Page 1: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

ECE 544 Project3

Team member

Page 2: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Assumptions and Address Scheme

Assumptions End hosts can only connect to routers Same content available at multiple end nodes etc…

Naming scheme and eventual address scheme Router End hosts Content

Page 3: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Bootstrapping and Discovery

Algorithm Routers and end hosts boot up (Hello packet?)

Discovery Routers discover other routers Hosts discover their router

Packet Format

Page 4: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Baseline Algorithm

Content routing algorithm How are contents advertised? How to route a content-request packet? How to choose the ‘best’, among multiple hosts

having the same content? How is the content actually delivered?

Packet Format

Page 5: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Data Transfer and Reliability

Message Forward Unicast, Multicast Packet Format of DATA, ACK

ARQ Scheme Hop-by-hop or End-to-end Stop-and-wait, Selective-repeat, sliding

windows or other schemes

Page 6: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Advantages and Disadvantages

Scalability? Latency? etc…

Page 7: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Example Scenarios

Use the example scenarios (from the Appendix) to highlight the key aspects of your proposal

Page 8: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Appendix: Network Architecture

Refer to the following example scenarios for analysis purposes:

H1

H2

H3

C1C1 C2C2

C3C3

R1 R2 R3 R4

R5

Scenario 1: @host_H2: get (content_C3)

Page 9: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Appendix: Network Architecture

H1

H2

H3

C1C1

C2C2

C2C2

C3C3

C3C3

R1 R2 R3 R4

R5

Scenario 2: @host_H1: get (content_C2)

Page 10: ECE 544 Project3 Team member. Assumptions and Address Scheme Assumptions End hosts can only connect to routers Same content available at multiple end

Appendix: Network Architecture

H1

C3C3

Scenario 3: @host_H1: get (content_C1)

H2 H3 H4

C1C1 C1C1C2C2

C1C1