Scribd
Upload
56 views

RIP Version 1 (RIP-1) Message Format

The document discusses the RIP Version 1 message format. RIP Version 1 was the original RIP protocol standardized in RFC 1058. It defines the basic RIP message format used by RIP Version 1 and later versions, including RIP request and response messages that are transmitted using UDP on port 520. RIP Version 1 also had limitations like a lack of support for classless addresses and authentication that were addressed by later RIP versions.

Uploaded by

manu221089
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
56 views

RIP Version 1 (RIP-1) Message Format

The document discusses the RIP Version 1 message format. RIP Version 1 was the original RIP protocol standardized in RFC 1058. It defines the basic RIP message format used by RIP Version 1 and later versions, including RIP request and response messages that are transmitted using UDP on port 520. RIP Version 1 also had limitations like a lack of support for classless addresses and authentication that were addressed by later RIP versions.

Uploaded by

manu221089
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 5

RIP Version 1 (RIP-1) Message Format

RIP evolved as an industry standard and was popularized by its inclusion in


the Berkeley Standard Distribution of UNIX (BSD UNIX). This first version of
RIP (now sometimes called RIP-1 to differentiate it from later versions), was
eventually standardized in RFC 1058. As part of this standard the original RIP-
1 message format was defined, which of course serves RIP-1 itself, and is also
the basis for the format used in later versions.

RIP-1 Messaging

As explained in the general discussion on RIP operation, route information is


exchanged in RIP through the sending of two different types of RIP messages:
RIP Request and the RIP Response. These are transmitted as regular TCP/IP
messages using the User Datagram Protocol (UDP), using UDP reserved port
number 520. This port number is used as follows:

RIP Request messages are sent to UDP destination port 520. They may have
a source port of 520 or may use an ephemeral port number.

RIP Response messages sent in reply to an RIP Request are sent with a
source port of 520, and a destination port equal to whatever source port the
RIP Request used.

Unsolicited RIP Response messages (sent on a routine basis and not in


response to a request) are sent with both the source and destination ports
set to 520.

RIP-1 Version-Specific Features

Since RIP version 1 was the first version of the protocol, its features formed
the basis for future RIP versions; it doesn't really have any version-specific
features. What RIP-1 has is a number of limitations, such as a lack of support
for specifying classless addresses and no means for authentication. RIP
version 2 was created to address some of RIP-1 shortcomings. As we will see
in the next topic, RIP-2's features put to good use those “Must Be Zero” bytes
in the RIP-1 format.

RIP for IP Version 2

RIP version 2 (v2) as defined in RFC 1723 seeks to address some of the
problems associated with RIP v1. The decision to refine RIP was controversial
in the context of newer, smarter routing protocols such as OSPF. However,
RIP has the following advantages over OSPF:

RIP for IP is easy to implement. In its simplest default configuration, RIP for IP
is as easy as configuring IP addresses and subnet masks for each router
interface and then turning on the router.

RIP for IP has a large installed base consisting of small and medium-sized IP
internetworks that do not wish to bear the design and configuration burden of
OSPF.

Features of RIP v2

To help today's IP internetworks minimize broadcast traffic, use variable


length subnetting to conserve IP addresses, and secure their routing
environment from misconfigured or malicious routers, several key features
were added to RIP v2.

RIP for IP Version 1

RIP version 1 (v1) is defined in RFC 1058 and is widely deployed in small to
medium-sized intranets.

RIP v1 Message Format

RIP messages are encapsulated in a User Datagram Protocol (UDP) datagram


sent from the router interface IP address and UDP port 520 to the subnet
broadcast IP address. The RIP v1 message consists of a 4-byte RIP header
and up to 25 RIP routes. The maximum size of the RIP message is 504 bytes.
With the 8-byte UDP header, the maximum size of the RIP message is a 512-
byte IP payload. Figure 3.8 illustrates the RIP v1 message format.

Command A 1-byte field containing either 0x01 or 0x02. 0x01 indicates a


RIP request for all (a General RIP Request) or part of the routing tables of
neighboring routers. 0x02 indicates a RIP response consisting of all or part of
a neighboring router's routing table. A RIP response can be sent in response
to a RIP request or as the periodic or triggered update message.

Version A 1-byte field set to the value of 0x01 for RIP v1.

Family Identifier A 2-byte field identifying the protocol family. This is set to
the value of 0x00-02 to indicate the IP protocol family.

IP Address A 4-byte field set to the IP network ID which can be a class-


based network ID, a subnetted network ID (advertised only within the
subnetted network), an IP address (for a host route), or 0.0.0.0 (for the
default route). For a General RIP Request, the IP Address is set to 0.0.0.0.

Metric A 4-byte field for the number of hops to the IP network that must be
a value from 1 to 16. The metric is set to 16 in a General RIP Request or to
indicate that the network is unreachable in a RIP response (announcement).

Problems with RIP v1


RIP v1 was designed in 1988 to suit the dynamic routing needs of LAN
technology–based IP internetworks. Shared access LAN technologies like
Ethernet and Token Ring support Media Access Control (MAC)–level
broadcasting where a single packet can be received and processed by
multiple network nodes. However, in modern internetworks, the use of MAC-
level broadcasts is undesirable because all nodes must process all
broadcasts. RIP v1 was also designed in a time when the Internet was still
using network IDs based on the Internet address classes. Today, however,
the use of Classless Inter-Domain Routing (CIDR) and variable length
subnetting is almost required to conserve IP addresses.

EIGRP FEATURES

Enhanced IGRP (EIGRP) is a classless, enhanced distance-vector protocol that


gives us a real edge over another Cisco proprietary protocol, Interior Gateway
Routing Protocol (IGRP). That’s basically why it’s called Enhanced IGRP. Like
IGRP, EIGRP uses the concept of an autonomous system to describe the set of
contiguous routers that run the same routing protocol and share routing
information. But unlike IGRP, EIGRP includes the subnet mask in its route
updates. And as you now know, the advertisement of subnet information
allows us to use VLSM and summarization when designing our networks!

OSPF provides the following features:

*consists of areas and autonomous systems

*Minimizes routing update traffic

*Allows scalability

*Supports VLSM/CIDR

*Has unlimited hop count

*Allows multi-vendor deployment (open standard)

*OSPF is the first link-state routing protocol that most people are introduced
to, so it’s useful to see how it compares to more traditional distance-vector
protocols such as RIPv2 and RIPv1.

Characteristic OSPF RIPv2 RIPv1

Type of protocol Link state Distance vector Distance vector

Classless support Yes Yes No

VLSM support Yes Yes No


Auto-summarization No Yes Yes

Manual summarization Yes No No

Discontiguous support Yes Yes No

Route propagation Multicast on change Periodic multicast Periodic


broadcast

Path metric Bandwidth Hops Hops

Hop count limit None 15 15

Convergence Fast Slow Slow

Peer authentication Yes Yes No

Hierarchical network Yes (using areas) No (flat only) No (flat only)

Updates Event triggered Route table updates Route


table updates

Route computation Dijkstra Bellman-Ford


Bellman-Ford

BGP (Border Gateway Protocol)

BGP (Border Gateway Protocol) is a protocol for exchanging routing


information between gateway hosts (each with its own router) in a network of
autonomous systems. BGP is often the protocol used between gateway hosts
on the Internet. The routing table contains a list of known routers, the
addresses they can reach, and a cost metric associated with the path to each
router so that the best available route is chosen.

Hosts using BGP communicate using the Transmission Control Protocol (TCP)
and send updated router table information only when one host has detected
a change. Only the affected part

Telecom Routing and Switching

Telecom Network Management

Telecom Resources

of the routing table is sent. BGP-4, the latest version, lets adminstrators
configure cost metrics based on policy statements. (BGP-4 is sometimes
called BGP4, without the hyphen.)
BGP communicates with autonomous (local) networks using Internal BGP
(IBGP) since it doesn't work well with IGP. The routers inside the autonomous
network thus maintain two routing tables: one for the interior gateway
protocol and one for IBGP.

BGP-4 makes it easy to use Classless Inter-Domain Routing (CIDR), which is a


way to have more addresses within the network than with the current IP
address assignment scheme.

BGP is a more recent protocol than the Exterior Gateway Protocol (EGP).

Also see the Interior Gateway Protocol (IGP) and the Open Shortest Path First
(OSPF) interior gateway protocol.

What is IS-IS?

The IS-IS (Intermediate System - Intermediate System) protocol is one of a


family of IP Routing protocols, and is an Interior Gateway Protocol (IGP) for
the Internet, used to distribute IP routing information throughout a single
Autonomous System (AS) in an IP network.

You might also like