Browse Prior Art Database

RIP Version 2 (RFC2453)

IP.com Disclosure Number: IPCOM000003031D
Original Publication Date: 1998-Nov-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 31 page(s) / 92K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Malkin: AUTHOR

Abstract

This document specifies an extension of the Routing Information Protocol (RIP), as defined in [1], to expand the amount of useful information carried in RIP messages and to add a measure of security.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group G. Malkin

Request for Comments: 2453 Bay Networks

Obsoletes: 1723, 1388 November 1998

STD: 56

Category: Standards Track

RIP Version 2

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

This document specifies an extension of the Routing Information

Protocol (RIP), as defined in [1], to expand the amount of useful

information carried in RIP messages and to add a measure of security.

A companion document will define the SNMP MIB objects for RIP-2 [2].

An additional document will define cryptographic security

improvements for RIP-2 [3].

Acknowledgements

I would like to thank the IETF RIP Working Group for their help in

improving the RIP-2 protocol. Much of the text for the background

discussions about distance vector protocols and some of the

descriptions of the operation of RIP were taken from "Routing

Information Protocol" by C. Hedrick [1]. Some of the final editing on

the document was done by Scott Bradner.

Table of Contents

1. Justification . . . . . . . . . . . . . . . . . . . . . . . . 3

2. Current RIP . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. Basic Protocol . . . . . . . . . . . . . . . . . . . . . . . . 3

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 3

3.2 Limitations of the Protocol . . . . . . . . . . . . . . . . 5

3.3. Organization of this document . . . . . . . . . . . . . . . 6

3.4 Distance Vector Algorithms . . . . . . . . . . . . . . . . . 6

3.4.1 Dealing with changes in topology . . . . . . . . . . . . 12

3.4.2 Preventing instability . . . . . . . . . . . . . . . . . 13

3.4.3 Split horizon . . . . . . . . . . . . . . . . . . . . . . 15

3.4.4 Triggered updates . . . . . . . . . . . . . . . . . . . . 17

3.5 Protocol Specification . . . . . . . . . . . . . . . . . . 18

3.6 Message Format . . . . . . . . . . . . . . . . . . . . . . . 20

3.7 Addressing Considerations . . . . . . . . . . . . . . . . . 22

3.8 Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.9 Input Processing . . . . . . . . . . ....