1 / 7

The Marketing Story

The Marketing Story. A single protocol Exploration = confirmation of reachability = quick check Works the same way for the current or other pairs Efficient No packets sent if payload traffic is idle No packets sent if bidirectional payload traffic

geoff
Download Presentation

The Marketing Story

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Marketing Story • A single protocol • Exploration = confirmation of reachability = quick check • Works the same way for the current or other pairs • Efficient • No packets sent if payload traffic is idle • No packets sent if bidirectional payload traffic • Packets sent only if (a) there’s a failure or (b) there’s unidirectional traffic • Minimization of overhead for case b is unimportant • Simple, no unnecessary negotiation or messages • Handles unidirectional failures • Built to be extensible for handling NATs

  2. The Design • Same messages have four complementary functions: • Show direct reachability, i.e., that the message can get to the receiver • Show indirect reachability, i.e., that earlier messages or payload packets from the receiver have gotten to the sender • Request the receiver to send responses over different return paths • Perform a return routability test in anticipation of moving a traffic stream to an address • Timeout is a protocol constant • 10s ; extensible later to other values for real-time re-homing

  3. B A REAP (1/4) - Idle If you are not sending or receiving payload packets, assume path is OK

  4. B A REAP (2/4) - Bidirectional Traffic If you send and receive payload packets, assume path is OK Payload packet Payload packet

  5. B A Payload packet REAP (3/4) - Unidirectional Traffic If you are receiving payload packets but not sending within t, assume path is OK but send an event message Event (no=10, seen={a payload}, iamok=yes)

  6. B A Payload packet Payload packet REAP (4/4) - Failure If you are sending payload packets but not receiving anything, request peer to explore other return paths. Return path failure: Payload packet Event (no=10, seen={}, iamok=no) Event (no=20, seen={10,a payload}, iamok=yes, nonce1) Event (no=21, seen={10,a payload}, iamok=yes, nonce2) Event (no=11, seen={21:nonce2}, iamok=yes)

  7. State Machine • State OK • I am receiving something • State Not OK • I am not receiving anything, hence something needs to change

More Related