1 / 6

RSVP Transport Issues

This document discusses the challenges of reliable delivery and soft-state management in the RSVP and NSIS protocols, focusing on techniques like staged refresh timers and message bundling (RFC2961). It emphasizes the issues faced with message size and CPU load, particularly in real-time applications. The comparison between RSVP-TE and NSIS illustrates the lessons learned, such as the need for flexible transport layers and simplified communication methods. Recommendations include enabling RFC2961 and adopting a TCP-like approach for improved efficiency and scalability in transport layers.

shel
Download Presentation

RSVP Transport Issues

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. RSVP Transport Issues Ping Pan Henning Schulzrinne NSIS WG

  2. Issues • Reliable Messaging: • Reliable delivery & soft-state. • Solution: Staged refresh timers (RFC2961). • … very TCP-like, at per-session level. • Message Packing • One session per RSVP message. • The size does not matter…. It is the message count that kills the CPU. • Solution: Message Bundling (RFC2961) NSIS WG

  3. Issues (cont.) • RSVP MTU • Cannot handle fragments. • Not an issue in RSVP-TE. • In e2e, message size may increase due to security overhead. • RSVP-TE vs. real-time applications • RSVP-TE does not have scaling problems. • Always enable RFC2961 • Controlled triggered messages • Real-time applications may have a problem. NSIS WG

  4. Where do we go? • RSVP-TE: no thanks. • Already deployed RFC2961. • 50,000+ sessions per router. • Other applications: • Transport layer may be a concern. • Recommendation on transport layer: • Make it flexible. • Make it TCP-like, • … and make it simple. NSIS WG

  5. Only if we could have done it again… • Learn from RSVP: • Application-neutral. • Change #1: hop-by-hop messaging • No need of using IP Router Alert for PATH • Change #2: flexible message transport • Support multiple transport protocols: raw mode, TCP, or UDP. • Swap transport-layer protocol per-hop NSIS WG

  6. How does it work … Hello, negotiation Step 1 A B C D TCP Raw mode TCP Step 2 A B C D Bundling User Requests Step 3 A B C D NSIS WG

More Related