1 / 11

PIM over Reliable Transport draft-farinacci-pim-port-00.txt

PIM over Reliable Transport draft-farinacci-pim-port-00.txt. Dino Farinacci, Ijsbrand Wijnands, Apoorva Karan, Arjen Boers, Maria Napierala IETF 71 - Philadelphia - March 2008. Agenda. Problem Statement Solution Statement Send PIM JP messages over TCP/SCTP Summary Working Group Status

doctor
Download Presentation

PIM over Reliable Transport draft-farinacci-pim-port-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. PIM over Reliable Transportdraft-farinacci-pim-port-00.txt Dino Farinacci, Ijsbrand Wijnands, Apoorva Karan, Arjen Boers, Maria Napierala IETF 71 - Philadelphia - March 2008

  2. Agenda • Problem Statement • Solution Statement • Send PIM JP messages over TCP/SCTP • Summary • Working Group Status • Next Steps • Acknowledgments IETF 71 - Philly

  3. Problem Statement • Periodic sending of JP messages • Could take more CPU than desirable • Could use more bandwidth than desirable • More profound when there is a PIM instance per VPN • Other periodic messages not as critical • Hello messages can be backed off IETF 71 - Philly

  4. Solution Statement • Make simple and isolated changes to PIMv2 • No need to rev the protocol version • Make optional on a per logical or physical interface basis • Use existing transport layers • So we don’t have to reinvent congestion control, in order delivery, and retransmission logic • TCP and SCTP • Only for JP messages • Avoid the complexities of mix-mode LANs IETF 71 - Philly

  5. New Hello Options IETF 71 - Philly

  6. Muxing for Efficiency IETF 71 - Philly

  7. Connection Establishment • Use address from PIM Hello for transport connection addresses • Use address comparison for call collision • O(n2) connections not necessary • Reliability is between you and your RPF neighbor • Even over LANs or NBMA configured MDTs • Sending JPs over TCP/SCTP is called • “transport-mode” • When connection not established • Use “datagram-mode” IETF 71 - Philly

  8. Receiving JPs in Transport-Mode • Don’t need to maintain oif-timers • State is not refreshed but now incremental • So Join adds to oif-list and Prune removes • When transitioning between transport-mode and datagram-mode • Use oif-timers • Send full set of JPs since transmitter doesn’t know what was received IETF 71 - Philly

  9. TCP API Interface Topology Table Neighbor Table Triggered JP Cancel oif-timer Periodic sending Set oif-timer IP API Interface JP Thread Send JP Receive JP Send JP Receive JP Sub-layer Hello Thread A Possible Implementation Connection Setup Legend: green - new red - existing blue - tables black - code IETF 71 - Philly

  10. Summary • Working Group Status • Should we make this a WG draft? • Next Steps • Prototype draft • IOS-XR, NX-OS, IOS • Report on prototype at summer IETF IETF 71 - Philly

  11. Acknowledgments IETF 71 - Philly

More Related