draft-ietf-pim-refresh-01.txt   draft-ietf-pim-refresh-02.txt 
Network Working Group Dino Farinacci Network Working Group Dino Farinacci
Internet Draft Procket Networks Internet Draft Procket Networks
Expiration Date: April, 2000 I. Kouvelas Expiration Date: May, 2001 Isidor Kouvelas
cisco Systems cisco Systems
K. Windisch Kurt Windisch
University of Oregon cisco Systems
October 21, 1999 November 22, 2000
State Refresh in PIM-DM State Refresh in PIM-DM
<draft-ietf-pim-refresh-01.txt> <draft-ietf-pim-refresh-02.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 7, line 27 skipping to change at page 7, line 27
O O
The Assert-Override flag. This is set by candidate forward- The Assert-Override flag. This is set by candidate forward-
ers on a LAN if a State-Refresh message has not been heard ers on a LAN if a State-Refresh message has not been heard
by the assert winner over the period of three times the by the assert winner over the period of three times the
[Refresh-Interval]. [Refresh-Interval].
Reserved Reserved
Set to zero and ignored upon receipt. Set to zero and ignored upon receipt.
Interval Interval
Set by the originating router to the interval between con- Set by the originating router to the interval (in seconds)
secutive State-Refresh messages for this source [Refresh- between consecutive State-Refresh messages for this source
Interval]. [Refresh-Interval].
6. Handling Router Failures 6. Handling Router Failures
PIM Hello messages will contain a Generation ID (GenID) in a Hello PIM Hello messages will contain a Generation ID (GenID) in a Hello
option [3]. When a PIM Hello is received from an existing neighbor option [3]. When a PIM Hello is received from an existing neighbor
and the GenID differs from the previous ID, the neighbor has res- and the GenID differs from the previous ID, the neighbor has res-
tarted and may not contain (S,G) state. In order to recreate the tarted and may not contain (S,G) state. In order to recreate the
missing state, for each (S,G), all routers upstream of the failed missing state, for each (S,G), all routers upstream of the failed
router (i.e. those receiving the Hello on a non-iif) can send a new router (i.e. those receiving the Hello on a non-iif) can send a new
(S,G) PIM State-Refresh message on the interface that the Hello mes- (S,G) PIM State-Refresh message on the interface that the Hello mes-
skipping to change at page 10, line 31 skipping to change at page 10, line 31
Dino Farinacci Dino Farinacci
Procket Networks Procket Networks
dino@procket.com dino@procket.com
Isidor Kouvelas Isidor Kouvelas
cisco Systems, Inc. cisco Systems, Inc.
kouvelas@cisco.com kouvelas@cisco.com
Kurt Windisch Kurt Windisch
Advanced Network Technolgy Center cisco Systems, Inc.
University of Oregon kurtw@cisco.com
kurtw@antc.uoregon.edu
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/