Routing Information Protocol (RIP) Parameters (last updated 2009-11-10) Registries included below: - RIP Commands - RIP Message Types - RIP Update Headers - RIP Address Family Identifiers - RIP Authentication Type - RIPNG Commands - RIPNG Update Headers Registry Name: RIP Commands Reference: [RFC1723] Registration Procedures: Not defined Registry: Value Description Reference Notes -------- ------------------------------------------------ --------- ------ 0 Invalid 1 Request [RFC1058] 2 Response [RFC1058] 3 TraceOn [RFC1058] 4 TraceOff [RFC1058] 5 Reserved [RFC1058] 6 Triggered Request [RFC1582] There are widely deployed implementations that don't support Triggered UDP that use value 6 = "Poll Entry" (undocumented) 7 Triggered Response [RFC1582] 8 Triggered Acknowledgement [RFC1582] 9 Update Request [RFC2091] 10 Update Response [RFC2091] 11 Update Acknowledge [RFC2091] 12-254 Unassigned Registry Name: RIP Update Headers Reference: [RFC1058] Registration Procedures: Not Defined Registry: Value Description Reference Notes -------- ------------------------------------------------ --------- ------ 0 must be discarded [RFC1058] 1 version 1 [RFC1058] 2 version 2 [RFC2453] 3-254 Unassigned Registry Name: RIP Address Family Identifiers Reference: [RFC1058] Registration Procedures: Not defined Registry: Value Description Reference Notes -------- ------------------------------------------------ --------- ------ 0 assigned but, unspecified. Associated full route [RFC1058] table exchange 1 Unassigned 2 IP [RFC1058] 3-65534 Unassigned 65535 Authentication present [RFC1388] This is represented in hex as 0xFFFF in Section 3.1 Registry Name: RIP Authentication Type Reference: [RFC1388] Registration Procedures: Not defined Registry: Value Description Reference Notes -------- ------------------------------------------------ --------- ------ 0 none 1 Unassigned 2 simple password [RFC1388] 3 md5 [RFC2082] 4-65534 Unassigned Registry Name: RIPNG Commands Reference: [RFC2080] Registration Procedures: Not defined Registry: Value Description Reference Notes -------- ------------------------------------------------ --------- ------ 1 Request [RFC2080] 2 Response [RFC2080] 3-255 Unassigned Registry name: RIPNG Update Headers Reference: [RFC2080] Registration Procedures: Not defined Value Description Reference Notes -------- ------------------------------------------------ --------- ------ 0 Unassigned Must be discarded 1 Version 1 [RFC2080] 2-254 Unassigned References ---------- [RFC1058] Hedrick, C., "Routing Information Protocol", RFC 1058, Rutgers University, June 1988. [RFC1388] G. Malkin, "RIP Version 2 Carrying Additional Information" RFC 1388, January 1993. [RFC1582] G. Meyer, "Extensions to RIP to Support Demand Circuits", RFC 1582, February 1994. [RFC1723] G. Malkin, "RIP Version 2 Carrying Additional Information", RFC 1723, November 1994. [RFC2080] G. Malkin and R. Minnear, "RIPng for IPv6", RFC 2080, January 1997. [RFC2082] F. Baker and R. Atkinson, "RIP-2 MD5 Authentication", RFC 2082, January 1997. [RFC2091] Meyers, G., and S. Sherry, "Triggered Extensions to RIP to Support Demand Circuits", RFc 2091, Shiva, Xyplex, January 1997. [RFC2453] G. Malkin, "RIP Version 2", RFC 2453, November 1998. []