1 / 7

Update on RSVP Diagnostics

Update on RSVP Diagnostics. No major changes New version of spec Changed order of steps in processing of DREQ messages (first increase hop_count then send back in case of error) Added Security Considerations paragraph Graphical Diagnosis client Java Applet as a front-end

licia
Download Presentation

Update on RSVP Diagnostics

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. Update on RSVP Diagnostics • No major changes • New version of spec • Changed order of steps in processing of DREQ messages (first increase hop_count then send back in case of error) • Added Security Considerations paragraph • Graphical Diagnosis client • Java Applet as a front-end • Back-end written in C Andreas Terzis UCLA IRL

  2. RSVP Diagnostics (cont.) • Getting around “black holes” • Send multiple requests, timeout • Do a traceroute or mtrace to find the path from LAST_HOP to sender • Use HOP_COUNT to incrementally get results • Once “black hole” found use LAST_HOP to continue DREQ from next hop towards source • Status: Working out some details, code will be available at http://irl.cs.ucla.edu Andreas Terzis UCLA IRL

  3. RSVP Tunnels-New draft version • Major cleanup and reorganization • Definitions of different tunnel types have changed. • Type 1: At least one of the endpoints does not support RSVP-Tunnels • Type 2: Configured Tunnels • Type 3: Dynamic Tunnels Andreas Terzis UCLA IRL

  4. New draft version (cont.) • SESSION_ASSOC object now carried by E2E PATH msgs • used to be carried by tunnel PATH msgs • Two cases for refreshing tunnel reservations, configured vs. dynamic sessions • Dynamic are refreshed by end-to-end RESV messages. • Configured Tunnels, state does not expire Andreas Terzis UCLA IRL

  5. Multicast Tunnels • Multicast Tunnels • Used for VPNs • What is it: One entry point multiple exit points • How do we use it: To send signaling messages and do the resource reservation • Data traffic does not go through the multicast tunnel, but through unicast tunnels • SE reservations (destination address in packet filter should be wildcard) Andreas Terzis UCLA IRL

  6. Interface Discovery • How does RSVP learn about tunnel interfaces • Ask kernel • Ask RSRR • Should we do both or one is enough??? Andreas Terzis UCLA IRL

  7. RSVP Tunnels Implementation • Completed implementation based on ISI’s RSVP • Contains tunnel management interface for creation of “configured pipes” • Available at http://irl.cs.ucla.edu • TBD: • Implement changes proposed in latest draft (SESSION_ASSOC object) • Sync up with latest RSVP release from ISI Andreas Terzis UCLA IRL

More Related