Browse Prior Art Database

RIPng for IPv6 (RFC2080)

IP.com Disclosure Number: IPCOM000002632D
Original Publication Date: 1997-Jan-01
Included in the Prior Art Database: 2019-Feb-16
Document File: 19 page(s) / 28K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Malkin: AUTHOR [+1]

Related Documents

10.17487/RFC2080: DOI

Abstract

This document specifies a routing protocol for an IPv6 internet. It is based on protocols and algorithms currently in wide use in the IPv4 Internet [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group G. Malkin Request for Comments: 2080 Xylogics Category: Standards Track R. Minnear Ipsilon Networks January 1997

RIPng for IPv6

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.

Abstract

This document specifies a routing protocol for an IPv6 internet. It is based on protocols and algorithms currently in wide use in the IPv4 Internet.

This specification represents the minimum change to the Routing Information Protocol (RIP), as specified in RFC 1058 [1] and RFC 1723 [2], necessary for operation over IPv6 [3].

Acknowledgements

This document is a modified version of RFC 1058, written by Chuck Hedrick [1]. The modifications reflect RIP-2 and IPv6 enhancements, but the original wording is his.

We’d like to thank Dennis Ferguson and Thomas Narten for their input.

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Theoretical Underpinnings . . . . . . . . . . . . . . . . . 3 1.2 Limitations of the Protocol . . . . . . . . . . . . . . . . 3 2. Protocol Specification . . . . . . . . . . . . . . . . . . . . 4 2.1 Message Format . . . . . . . . . . . . . . . . . . . . . . . 5 2.1.1 Next Hop . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.2 Addressing Considerations . . . . . . . . . . . . . . . . . 8 2.3 Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.4 Input Processing . . . . . . . . . . . . . . . . . . . . . . 10 2.4.1 Request Messages . . . . . . . . . . . . . . . . . . . . . 10 2.4.2 Response Messages . . . . . . . . . . . . . . . . . . . . 11

Malkin & Minnear Standards Track [Page 1]

RFC 2080 RIPng for IPv6 January 1997

2.5 Output Processing . . . . . . . . . . . . . . . . . . . . . 14 2.5.1 Triggered Updates . . . . . . . . . . . . . . . . . . . . 14 2.5.2 Generating Response Messages . . . . . . . . . . . . . . . 15 2.6 Split Horizon . . . . . . . . . . . . . . . . . . . . . . . 16 3. Control Functions . . . . . . . . . . . . . . . . . . . . . . 17 4. Security Considerations. . . . . . . . . . . . . . . . . . . . 18 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors’ Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

1. Introduction

This memo describes one protocol in a series of routing protocols based on the Bellman-Ford (or distance vector) algorithm. This algorithm has been used for routing computations in computer networks since the early days of the ARPANET. The particular packet formats and protocol described here are based on the program "routed," which is included with the Berkeley distribution of Unix.

In an international network, such as the Internet, it is very unlikely that a single routing protocol will used for...

Processing...
Loading...