draft-ietf-pim-sm-v2-new-05.txt   draft-ietf-pim-sm-v2-new-06.txt 
Internet Engineering Task Force PIM WG Internet Engineering Task Force PIM WG
INTERNET-DRAFT Bill Fenner/AT&T INTERNET-DRAFT Bill Fenner/AT&T
draft-ietf-pim-sm-v2-new-05.txt Mark Handley/ICIR draft-ietf-pim-sm-v2-new-06.txt Mark Handley/ICIR
Hugh Holbrook/Cisco Hugh Holbrook/Cisco
Isidor Kouvelas/Cisco Isidor Kouvelas/Cisco
1 March 2002 10 December 2002
Expires: September 2002 Expires: June 2003
Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised) Protocol Specification (Revised)
Status of this Document Status of this Document
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
skipping to change at page 30, line 9 skipping to change at page 30, line 9
random value between 0 and Triggered_Hello_Delay. This prevents random value between 0 and Triggered_Hello_Delay. This prevents
synchronization of Hello messages if multiple routers are powered on synchronization of Hello messages if multiple routers are powered on
simultaneously. After the initial randomized interval, Hello messages simultaneously. After the initial randomized interval, Hello messages
must be sent every Hello_Period seconds. The hello timer should not be must be sent every Hello_Period seconds. The hello timer should not be
reset except when it expires. reset except when it expires.
Note that neighbors will not accept Join/Prune or Assert messages from a Note that neighbors will not accept Join/Prune or Assert messages from a
router unless they have first heard a Hello message from that router. router unless they have first heard a Hello message from that router.
Thus if a router needs to send a Join/Prune or Assert message on an Thus if a router needs to send a Join/Prune or Assert message on an
interface on which it has not yet sent a Hello message, then it MUST interface on which it has not yet sent a Hello message, then it MUST
immediately send the relevant without Hello message without waiting for immediately send the relevant Hello message without waiting for the
the Hello timer to expire, followed by the Join/Prune or Assert message. Hello timer to expire, followed by the Join/Prune or Assert message.
The DR_Election_Priority Option allows a network administrator to give The DR_Election_Priority Option allows a network administrator to give
preference to a particular router in the DR election process by giving preference to a particular router in the DR election process by giving
it a numerically larger DR Election Priority. The DR_Election_Priority it a numerically larger DR Election Priority. The DR_Election_Priority
Option SHOULD be included in every Hello message, even if no DR election Option SHOULD be included in every Hello message, even if no DR election
priority is explicitly configured on that interface. This is necessary priority is explicitly configured on that interface. This is necessary
because priority-based DR election is only enabled when all neighbors on because priority-based DR election is only enabled when all neighbors on
an interface advertise that they are capable of using the DR Election an interface advertise that they are capable of using the DR Election
Priority Option. The default priority is 1. Priority Option. The default priority is 1.
skipping to change at page 87, line 8 skipping to change at page 87, line 8
(*,G,I) -> better than (RP(G)) stops Join(*,G) or (*,G,I) -> better than (RP(G)) stops Join(*,G) or
FALSE Winner's being I Join(*,*,RP(G)) FALSE Winner's being I Join(*,*,RP(G))
metric on Interface I metric on Interface I
------------------------------------------------------------------------- -------------------------------------------------------------------------
-> NI state -> NI state -> NI state -> NI State -> NI state -> NI state -> NI state -> NI State
[Actions A5] [Actions A5] [Actions A5] [Actions A5] [Actions A5] [Actions A5] [Actions A5] [Actions A5]
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
INTERNET-DRAFT | Expires: September 2002 | March 2002| INTERNET-DRAFT | Expires: June 2003 | December 2002|
| | | | | | | | | |
| | | | | | | | | |
+---------------+-----------------+-----------------+-------------------+ +---------------+-----------------+-----------------+-------------------+
The state machine uses the following macros: The state machine uses the following macros:
CouldAssert(*,G,I) = CouldAssert(*,G,I) =
( I in ( joins(*,*,RP(G)) (+) joins(*,G) ( I in ( joins(*,*,RP(G)) (+) joins(*,G)
(+) pim_include(*,G)) ) (+) pim_include(*,G)) )
AND RPF_interface(RP(G)) != I AND RPF_interface(RP(G)) != I
skipping to change at page 130, line 46 skipping to change at page 130, line 46
may be used. Furthermore, a PIM router SHOULD NOT accept protocol may be used. Furthermore, a PIM router SHOULD NOT accept protocol
messages from a router from which it has not yet received a valid Hello messages from a router from which it has not yet received a valid Hello
message. message.
A Designated Router MUST NOT register-encapsulate a packet and send it A Designated Router MUST NOT register-encapsulate a packet and send it
to the RP unless the source address of the packet is a legal address for to the RP unless the source address of the packet is a legal address for
the subnet on which the packet was received. Similarly, a Designated the subnet on which the packet was received. Similarly, a Designated
Router SHOULD NOT accept a RegisterStop packet whose IP source address Router SHOULD NOT accept a RegisterStop packet whose IP source address
is not a valid RP address for the local domain. is not a valid RP address for the local domain.
An implementation SHOULD provide a mechanism to allow a DR to restrict An implementation SHOULD provide a mechanism to allow an RP to restrict
the range of source addresses from which it accepts Register- the range of source addresses from which it accepts Register-
encapsulated packets. encapsulated packets.
All options that restrict the range of addresses from which packets are All options that restrict the range of addresses from which packets are
accepted MUST default to allowing all packets. accepted MUST default to allowing all packets.
6.3. Authentication using IPsec 6.3. Authentication using IPsec
The IPsec [11] transport mode using the Authentication Header (AH) is The IPsec [11] transport mode using the Authentication Header (AH) is
the recommended method to prevent the above attacks PIM. The anti- the recommended method to prevent the above attacks PIM. The anti-
 End of changes. 

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