1 / 5

Improved Register Procedure in PIM-SM draft-wen-pim-improved-register-00.txt

Improved Register Procedure in PIM-SM draft-wen-pim-improved-register-00.txt. Haibo WEN. Register procedure in current PIM-SM. Current procedure The data-plane and control-plane are not clearly separated in PIM-SM

eleanor-parker
Download Presentation

Improved Register Procedure in PIM-SM draft-wen-pim-improved-register-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. Improved Register Procedure in PIM-SMdraft-wen-pim-improved-register-00.txt Haibo WEN

  2. Register procedure in current PIM-SM • Current procedure The data-plane and control-plane are not clearly separated in PIM-SM • The sender sends MC data packets once it wants to do, no control message exchange in control-plane. • At the DR, MC packets from sender trigger Register message (with encapsulation of MC data packets) in control plane. • The Register messages of this kind continue being sent until DR receives Register-Stop message. RP decapsulates the Register message and send the payload along the RP tree in the data plane. • Encapsulation and de-capsulation are relatively expensive operations for routers. • The arriving of native MC data packets in data-plane at RP will trigger Register-Stop message in control-plane. • 2. Security issue • Malicious user will use this feature to attack the network by sending all kinds of MC data

  3. Improved PIM-SM register procedure (1/2) • Basic idea:DR will not forward/encapsulate MC until the delivery path has been established. • Once the MC path from DR to RP has been established, the MC packets from the sender will be forwarded. • Separate control plane and data plane completely • Registering Process in the control-plane • Sender management (logical messages. Two choices: (i) IGMP/MLD can be extended for this purpose; (ii) define new protocol)) • Sender-Request: request for sending MC data. • DR-ACK: positive indication for allowing the sender to send MC data. • DR-NAK: negative indication for not allowing the sender to send MC data. • Sender-Alive: periodically sent by the sender to notify the DR that the sender is alive. • Sender-Leave: the sender notifies the DR that it will not send MC data any more. • DR’s register process (define 3 new messages except Join) • Register-Request: DR sends this message to RP to register. • Join: to join the MC delivery tree • SPT-OK: to notify the downstream routers on the SPT that the sender is alive, update the corresponding status in routers. Periodically sent from the root of SPT, either responded as a newly branch grafting this SPT. • MC-Over: the sender will not send MC data, the SPT will be deleted (the corresponding status will be removed • MC data packets delivery in the data-plane

  4. Improved PIM-SM register procedure (2/2) Advantages: • Simplify the logic of registering procedure. • Clearly separate the control-plane and data-plane is good for speeding up data forwarding. • Authentication for MC sender can easily implemented in this procedure • No encapsulation and de-capsulation for MC data at the routers • SPT-OK along the SPT setting SPTbit removes the mechanism of MC data setting SPTbit, Keepalive timer • It’s good for fast forwarding.

  5. Thank you!

More Related