1 / 8

Francois Le Faucheur, Dan Wing C isco Systems

draft-lefaucheur-tsvwg-rsvp-proxy-00.txt RSVP Proxy Approaches Francois Le Faucheur - flefauch@cisco.com. Francois Le Faucheur, Dan Wing C isco Systems. Jukka Manner University of Helsinki. RSVP Proxy Background. RSVP deployments happening: eg for Voice/Video CAC on WAN in Enterprise

luka
Download Presentation

Francois Le Faucheur, Dan Wing C isco Systems

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. draft-lefaucheur-tsvwg-rsvp-proxy-00.txtRSVP Proxy ApproachesFrancois Le Faucheur - flefauch@cisco.com Francois Le Faucheur, Dan Wing Cisco Systems Jukka Manner University of Helsinki

  2. RSVP Proxy Background • RSVP deployments happening: • eg for Voice/Video CAC on WAN in Enterprise • eg for VoD CAC on Aggregation in Triple-Play SP • RSVP also considered: • eg for Mobile Voice CAC on Radio • Many deployment scenarios involve RSVP only on a subset of end-to-end path • non-RSVP-capable Sender, or non-RSVP-capable Receiver • RSVP CAC only needed on (radio) access • Current RSVP spec assumes end-to-end signaling • Need to : • document (resurrect) non end-to-end deployment approaches • standardize corresponding extensions (where needed) • NSIS included this in base specs

  3. VoD RSVP Path Video Stream RSVP Resv Use Case: VoD CAC on Aggregation in Triple Play RSVP aware RSVP Receiver Proxy RSVP aware Residential L3 IP/MPLS Core Ethernet/IP/MPLS Aggregation Business RSVP Unaware Corporate 802.1Q

  4. Use Case: Voice/Video CAC on WAN in Enterprise SIP Server SIP HQ SIP RSVP Proxy RSVP Proxy WAN RSVP RSVP aware Location B Location A RSVP Unaware

  5. VoD Example of required RSVP Extension RSVP Receiver Proxy • Regular RSVP sends CAC reject notification towards Receiver • RSVP Receiver Proxy can not do much with it • Extension to notify Sender of CAC reject RSVP Unaware RSVP aware Path Resv CAC reject ResvErr (CAC reject) ??? PathErr (CAC reject)

  6. I-Ds Roadmap • As announced on mailing list after Montreal • draft-lefaucheur-tsvwg-rsvp-proxy: • Provides Framework for RSVP Proxy concept • Taxonomy of (useful) Proxy Approaches • Minor RSVP extensions for simple Proxy approaches • Use Cases (in Appendix) • draft-manner-tsvwg-rsvp-proxy-sig ("Localized RSVP for Controlling RSVP Proxies”) : • Specifies RSVP signaling extensions for more complex Proxy approaches (RSVP-Signaling-Triggered Proxy)

  7. Taxonomy of Proxy Approaches: • Path-Triggered Receiver Proxy • Path-Triggered Sender Proxy for Reverse Direction • Inspection-Triggered Proxy • STUN-Triggered Proxy • Application-Signaling-Triggered On-Path Proxy • Application-Signaling-Triggered Off-Path Source Proxy • RSVP-Signaling-Triggered Proxy

  8. Next Steps • Progress RSVP Proxy under TSVWG • Address comments received • Should rsvp-proxy target Informational Track or Standards Track? • If Informational, need to move minor “extensions” out of rsvp-proxy I-D. • Should all extensions go to rsvp-proxy-sig or to separate I-Ds for different Proxy approaches?

More Related