1 / 16

Detecting Network Attachment Router Reachability Detection draft-narayanan-dna-rrd-00.txt

Detecting Network Attachment Router Reachability Detection draft-narayanan-dna-rrd-00.txt. Sathya Narayanan Panasonic. Outline. Design principles Router Reachability Detection Rate limiting Modifications Comparison of proposed solutions. Design principles.

vmorris
Download Presentation

Detecting Network Attachment Router Reachability Detection draft-narayanan-dna-rrd-00.txt

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. Detecting Network Attachment Router Reachability Detectiondraft-narayanan-dna-rrd-00.txt Sathya Narayanan Panasonic IETF 61 – Washington D.C.

  2. Outline • Design principles • Router Reachability Detection • Rate limiting • Modifications • Comparison of proposed solutions IETF 61 – Washington D.C.

  3. Design principles • The link-identifier used by different IP nodes on the same link need not be the same (<Current active prefix, current default router>) • Pro-active detection mechanism to quickly learn about link-change. • Layer-2 trigger to initiate such pro-active detection. IETF 61 – Washington D.C.

  4. Router reachability detection • Verify availability and reachability of current default router. • If not-available, learn about other available routers. IETF 61 – Washington D.C.

  5. RS Router reachability detection IP Link Current default router = AR1 Current prefix = P1 L2 Trigger IETF 61 – Washington D.C.

  6. RS Quick RA from AR1 Router reachability detection IP Link AR1 Current default router = AR1 Current prefix = P1 IETF 61 – Washington D.C.

  7. RS Router reachability detection IP Link Current default router = AR1 Current prefix = P1 L2 Trigger IETF 61 – Washington D.C.

  8. RS Quick RA from AR1 Router reachability detection IP Link AR2 AR1 AR3 Current default router = AR1 Current prefix = P1 IETF 61 – Washington D.C.

  9. RS Router reachability detection IP Link Current default router = AR1 Current prefix = P1 L2 Trigger IETF 61 – Washington D.C.

  10. RS Quick RA from AR2/AR3/AR4 Router reachability detection IP Link AR3 AR2 AR4 Current default router = AR1 Current prefix = P1 IETF 61 – Washington D.C.

  11. RS Router reachability detection IP Link Current default router = AR1 Current prefix = P1 L2 Trigger IETF 61 – Washington D.C.

  12. RS Match RA with corresponding RS(s) that triggered the response Router reachability detection IP Link Current default router = AR1 Current prefix = P1 IETF 61 – Washington D.C.

  13. Proposed changes • Current Access Router option in RS message • Higher priority for current access router in responding to the RS message • Two new variables: MinDelayForOtherRouters <= MaxDelayForCurrRouter • If MinDelayForOtherRouters = MaxDelayForCurrrouter, current access router will always (with prob. 1) respond first. • Use target link layer address option(s) in RA message to identify RS messages received. IETF 61 – Washington D.C.

  14. One last change !!! • Token bucket based rate-limiting for RA messages to reduce likelihood of MIN_DELAY_BETWEEN_RAS delay before RA response. IETF 61 – Washington D.C.

  15. Issues • When current access router is not available, how to make one other router to respond quick (daley-dna-det-fastra) IETF 61 – Washington D.C.

  16. Questions? Comments? IETF 61 – Washington D.C.

More Related