Triggered RIP IETF/RIP/TRIGGER 1.0 
IETF Dallas December 1995 
  
========
   
  1. Triggered Extensions to RIP to Support Demand Circuits 

  
  draft-ietf-rip-trigger-rip-00.txt:
 
    o  Triggered Extensions to RIP to Support Demand Circuits.
 
  draft-ietf-rip-trigger-analysis-00.txt:
 
    o  Protocol Analysis for Triggered RIP.

 
  Like "Extensions to RIP to Support Demand Circuits", RFC 1582 
  (Feb 1994), enhances:
 
    o  IP RIP V1 (RFC 1058).
 
    o  IP RIP V2 (RFC 1723).
 
    o  Netware RIP (IPX Router Specification).
 
    o  Netware SAP (IPX router Specification).
 
  to eliminate periodic 'broadcasting' on the WAN
  
========
 
  2. Triggered RIP 
  
    o  WAN Demand links (SVCs).
 
    o  WAN Point-to-Point links.
 
    o  LANs (unmodified).

 
  Always reduces WAN routing traffic:
 
    o  Eliminates periodic updates.
 
    o  Still sends 'infrequent' updates for topology changes.
 
========  
 
  3. Key Differences from Demand RIP 
  
    o  Updates are sent incrementally.
 
    o  Peer updates database as each updates arrive.
 
  These differences save memory and bandwidth.


  Not backward compatible with Demand RIP:
 
    o  Packet Command/Operation types are different.
 
    o  Updates are not 'fragmented'.  Each packet is a 'complete' update.
 
  Triggered RIP and Demand RIP can however co-exist.