Routing Advice Agreement (RIP)
The Acquisition Advice Protocol, or RIP as it is added frequently called, is one of the best constant of all
routing protocols. RIP was authentic in RFC 1058 and Internet Standard (STD) 56. Later, the IETF (Internet
Engineering Task Force) adapted RIP with the absolution of a revised RFC 1388 in January 1993. RFC 1388 was
then abolished in November 1994 by RFC 1723, which describes RIPv2 (the additional adaptation of RIP). These
RFCs did not attack to accomplish anachronistic the antecedent adaptation of RIP, but proposed extensions and enhancements
to the RIP capabilities. RIPv2 enabled RIP letters to backpack added advice and calibration added with more
features, such as multicast abutment and a next-hop router address. The next-hop router abode is an
authentication mechanism; its best important action is to abutment subnet masks and is accordingly a critical
feature that was not accessible in RIPv1. RIP is a dynamic, distance-vector acquisition agreement that uses UDP as the
transport protocol. RIP packets are transmitted on UDP anchorage 520 for avenue updates.
The Security Appliance supports both RIPv1 and RIPv2 protocols. Application RIP has advantages over application static
routes, because the antecedent agreement for RIP is simple and does not crave afterlight the agreement when
the cartography changes. The downside to RIP (or any added activating protocol) is that there is added arrangement and
processing aerial than with changeless routing.
By default, the Security Appliance sends RIPv1 updates and accepts RIPv1 and RIPv2 updates. Redistribution of
routes from added acquisition processes into the RIP is accurate in Firewall OS Adaptation 7.2 and later. Prior to this,
RIP and OSPF were not accurate on the aforementioned device.