mirror of
				https://git.proxmox.com/git/mirror_frr
				synced 2025-10-31 09:04:27 +00:00 
			
		
		
		
	 95d962bf1d
			
		
	
	
		95d962bf1d
		
	
	
	
	
		
			
			The TODO file had become a dumping ground of changes made to the protocol. That when we modified the underlying code we would need to update the TODO file again due to it's nature. There is no point in keeping the list of items that we've done as that commit messages will indicate the new features. So pull out all the Finished work and rework the Todo numbers used. Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
		
			
				
	
	
		
			71 lines
		
	
	
		
			2.6 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			71 lines
		
	
	
		
			2.6 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
| T1  Consider reliable pim solution (refresh reduction)
 | |
|     A Reliable Transport Mechanism for PIM
 | |
|     http://tools.ietf.org/wg/pim/draft-ietf-pim-port/
 | |
|     PORT=PIM-Over-Reliable-Transport
 | |
| 
 | |
| T2  If an interface changes one of its secondary IP addresses, a Hello
 | |
|     message with an updated Address_List option and a non-zero
 | |
|     HoldTime should be sent immediately.
 | |
|     See also detect_secondary_address_change
 | |
|     See also CAVEAT C15.
 | |
|     See also RFC 4601: 4.3.1.  Sending Hello Messages
 | |
| 
 | |
| T3  Lightweight MLDv2
 | |
|     http://tools.ietf.org/html/draft-ietf-mboned-lightweight-igmpv3-mldv2-05
 | |
|     http://www.ietf.org/internet-drafts/draft-ietf-mboned-lightweight-igmpv3-mldv2-05.txt
 | |
|     http://www.ietf.org/html.charters/mboned-charter.html
 | |
| 
 | |
| T4  Static igmp join fails when loading config at boot time
 | |
| 
 | |
|     ! Wrong behavior seen at boot time:
 | |
|     !
 | |
|     2010/02/22 08:59:00 PIM: igmp_source_forward_start: ignoring request for
 | |
|     looped MFC entry (S,G)=(3.3.3.3,239.3.3.3): igmp_sock=12 oif=eth0 vif_index=2
 | |
| 
 | |
|     ! Correct behavior seen later:
 | |
|     !
 | |
|     2010/02/22 09:03:16 PIM: igmp_source_forward_start: ignoring request for
 | |
|     looped MFC entry (S,G)=(2.2.2.2,239.2.2.2): igmp_sock=17 oif=lo vif_index=1
 | |
| 
 | |
|     ! To see the wrong message at boot:    
 | |
|     !
 | |
|     debug igmp trace
 | |
|     !
 | |
|     interface lo
 | |
|      ip igmp
 | |
|      ip igmp join 239.2.2.2 2.2.2.2
 | |
|      ip igmp join 239.3.3.3 3.3.3.3
 | |
|     !
 | |
| 
 | |
|     ! Interfaces indexes:
 | |
|     Interface Address         ifi Vif  PktsIn PktsOut    BytesIn   BytesOut
 | |
|     eth0      200.202.112.3     2   2       0       0          0          0
 | |
|     lo        127.0.0.1         1   1       0       0          0          0
 | |
| 
 | |
| T5  PIM Neighbor Reduction
 | |
|     https://datatracker.ietf.org/doc/draft-wijnands-pim-neighbor-reduction/
 | |
|     
 | |
|     "In a transit LAN (no directly connected source or receiver), many
 | |
|     of the PIM procedures don't apply. (...) This proposal describes
 | |
|     a procedure to reduce the amount of neighbors established over a
 | |
|     transit LAN."
 | |
| 
 | |
| T6  Single Stream Multicast Fast Reroute (SMFR) Method
 | |
|     https://datatracker.ietf.org/doc/draft-liu-pim-single-stream-multicast-frr/
 | |
| 
 | |
|     "This document proposes an IP multicast fast convergence method
 | |
|     based on differentiating primary and backup PIM join."
 | |
| 
 | |
| T7  RFC5384 - The Join Attribute Format
 | |
|     "This document describes a modification of the Join message that
 | |
|     allows a node to associate attributes with a particular tree."
 | |
| 
 | |
| T8  PIM Multi-Topology ID (MT-ID) Join-Attribute
 | |
|     http://tools.ietf.org/html/draft-cai-pim-mtid-00
 | |
|     Depends on T7.
 | |
| 
 | |
|     "This draft introduces a new type of PIM Join Attribute used to
 | |
|     encode the identity of the topology PIM uses for RPF."
 | |
|     
 | |
| -x-
 |