pimd/TODO

   1 T1  Consider reliable pim solution (refresh reduction)
   2     A Reliable Transport Mechanism for PIM
   3     http://tools.ietf.org/wg/pim/draft-ietf-pim-port/
   4     PORT=PIM-Over-Reliable-Transport
   5
   6 T2  If an interface changes one of its secondary IP addresses, a Hello
   7     message with an updated Address_List option and a non-zero
   8     HoldTime should be sent immediately.
   9     See also detect_secondary_address_change
  10     See also CAVEAT C15.
  11     See also RFC 4601: 4.3.1.  Sending Hello Messages
  12
  13 T3  Lightweight MLDv2
  14     http://tools.ietf.org/html/draft-ietf-mboned-lightweight-igmpv3-mldv2-05
  15     http://www.ietf.org/internet-drafts/draft-ietf-mboned-lightweight-igmpv3-mldv2-05.txt
  16     http://www.ietf.org/html.charters/mboned-charter.html
  17
  18 T4  Static igmp join fails when loading config at boot time
  19
  20     ! Wrong behavior seen at boot time:
  21     !
  22     2010/02/22 08:59:00 PIM: igmp_source_forward_start: ignoring request for
  23     looped MFC entry (S,G)=(3.3.3.3,239.3.3.3): igmp_sock=12 oif=eth0 vif_index=2
  24
  25     ! Correct behavior seen later:
  26     !
  27     2010/02/22 09:03:16 PIM: igmp_source_forward_start: ignoring request for
  28     looped MFC entry (S,G)=(2.2.2.2,239.2.2.2): igmp_sock=17 oif=lo vif_index=1
  29
  30     ! To see the wrong message at boot:
  31     !
  32     debug igmp trace
  33     !
  34     interface lo
  35      ip igmp
  36      ip igmp join 239.2.2.2 2.2.2.2
  37      ip igmp join 239.3.3.3 3.3.3.3
  38     !
  39
  40     ! Interfaces indexes:
  41     Interface Address         ifi Vif  PktsIn PktsOut    BytesIn   BytesOut
  42     eth0      200.202.112.3     2   2       0       0          0          0
  43     lo        127.0.0.1         1   1       0       0          0          0
  44
  45 T5  PIM Neighbor Reduction
  46     https://datatracker.ietf.org/doc/draft-wijnands-pim-neighbor-reduction/
  47
  48     "In a transit LAN (no directly connected source or receiver), many
  49     of the PIM procedures don't apply. (...) This proposal describes
  50     a procedure to reduce the amount of neighbors established over a
  51     transit LAN."
  52
  53 T6  Single Stream Multicast Fast Reroute (SMFR) Method
  54     https://datatracker.ietf.org/doc/draft-liu-pim-single-stream-multicast-frr/
  55
  56     "This document proposes an IP multicast fast convergence method
  57     based on differentiating primary and backup PIM join."
  58
  59 T7  RFC5384 - The Join Attribute Format
  60     "This document describes a modification of the Join message that
  61     allows a node to associate attributes with a particular tree."
  62
  63 T8  PIM Multi-Topology ID (MT-ID) Join-Attribute
  64     http://tools.ietf.org/html/draft-cai-pim-mtid-00
  65     Depends on T7.
  66
  67     "This draft introduces a new type of PIM Join Attribute used to
  68     encode the identity of the topology PIM uses for RPF."
  69
  70 -x-