1 / 5

Protocol Independent Multicast (PIM) MIB Draft Updates

This draft outlines changes in managed objects for managing PIM Sparse Mode and Dense Mode, introducing new objects, bits, and mappings. It discusses updates for MIB compilation and object order, and future IPv6 compatibility. Participate in discussions by joining the PIM MIB mailing list.

jjulian
Download Presentation

Protocol Independent Multicast (PIM) MIB Draft Updates

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. IETF PIM MIB Draft pim-mib@mountain2sea.com

  2. This draft describes managed objects used for managing the Protocol Independent Multicast (PIM) protocol. It defines objects for PIM Sparse Mode as well as for Dense Mode. “draft-ietf-pim-mib-v2-01.txt” authored by J. Nicholas, has expired in May'2004. PIM MIB

  3. Changes dicsussed and freezed: Removal of warnings during MIB compilation with smilint. Changes to make MIB objects in proper order in the document. Introduce a new object "pimInterfaceBSRBorder" in pimInterfaceEntry table. This object shows the status of a BSR border on the interface. Status of PIM MIB

  4. Changes which are being discussed: In pimIpMRouteFlag of pimIpMRouteEntry table, we need two registration bits (registrationInProgress and registrationSucceeded). These bits will help in identifying the state of registration for the given MRoute Entry. In pimIpMRouteFlag of pimIpMRouteEntry table, we need a bit to represent data flow. It will tell user if data is flowing through SPT or RPT. MIB object for Static Group-RP mapping. We have introdcued a new table which can represent static Group-RP mapping entries. Add a new object "pimIpMRouteRP" in pimIpMRouteEntry table to identify the RP being used for this Mroute. Add a new bit "ssm" in pimIpMRouteFlags in pimIpMRouteEntry table, this bit will idntify this MRoute entry as an SSM entry. Status of PIM MIB

  5. IPv6 compatibility for PIM MIB. Comments/Suggestions provided by community after the review. A new version of this draft will be released in August'2004 NOTE: To participate in PIM MIB discussions, Please join the PIM MIB mailing list at: http://www.mountain2sea.com/mailman/listinfo/pim-mib Future Road Map

More Related