Diff: draft-ietf-pim-sm-bsr-09.txt - draft-ietf-pim-sm-bsr-10.txt

	< draft-ietf-pim-sm-bsr-09.txt	draft-ietf-pim-sm-bsr-10.txt >
	Internet Engineering Task Force PIM WG	Internet Engineering Task Force PIM WG
	INTERNET-DRAFT Nidhi Bhaskar/Cisco	INTERNET-DRAFT Nidhi Bhaskar/Cisco

	draft-ietf-pim-sm-bsr-09.txt Alexander Gall/SWITCH	draft-ietf-pim-sm-bsr-10.txt Alexander Gall/SWITCH
	James Lingard/Arastra	James Lingard/Arastra
	Stig Venaas/UNINETT	Stig Venaas/UNINETT

	23 June 2006	9 February 2007
	Expires: December 2006	Expires: August 2007

	Bootstrap Router (BSR) Mechanism for PIM	Bootstrap Router (BSR) Mechanism for PIM

	Status of this Document	Status of this Document

	By submitting this Internet-Draft, each author represents that any	By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware have	applicable patent or other IPR claims of which he or she is aware have
	been or will be disclosed, and any of which he or she becomes aware will	been or will be disclosed, and any of which he or she becomes aware will
	be disclosed, in accordance with Section 6 of BCP 79.	be disclosed, in accordance with Section 6 of BCP 79.


	skipping to change at page 1, line 39 ¶	skipping to change at page 1, line 39 ¶
	http://www.ietf.org/1id-abstracts.html	http://www.ietf.org/1id-abstracts.html

	The list of Internet-Draft Shadow Directories can be accessed at	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html	http://www.ietf.org/shadow.html

	This document is a product of the IETF PIM WG. Comments should be	This document is a product of the IETF PIM WG. Comments should be
	addressed to the authors, or the WG's mailing list at pim@ietf.org.	addressed to the authors, or the WG's mailing list at pim@ietf.org.

	Copyright Notice	Copyright Notice


	Copyright (C) The Internet Society (2006).	Copyright (C) The IETF Trust (2007).

	Abstract	Abstract

	This document specifies the Bootstrap Router (BSR) mechanism	This document specifies the Bootstrap Router (BSR) mechanism
	for the class of multicast routing protocols in the PIM	for the class of multicast routing protocols in the PIM
	(Protocol Independent Multicast) family that use the concept	(Protocol Independent Multicast) family that use the concept
	of a Rendezvous Point as a means for receivers to discover the	of a Rendezvous Point as a means for receivers to discover the
	sources that send to a particular multicast group. BSR is one	sources that send to a particular multicast group. BSR is one
	way that a multicast router can learn the set of group-to-RP	way that a multicast router can learn the set of group-to-RP
	mappings required in order to function. The mechanism is	mappings required in order to function. The mechanism is
	dynamic, largely self-configuring, and robust to router	dynamic, largely self-configuring, and robust to router
	failure.	failure.

	Table of Contents	Table of Contents


	1. Introduction. . . . . . . . . . . . . . . . . . . . . . 4	1. Introduction. . . . . . . . . . . . . . . . . . . . . . 5
	1.1. Background . . . . . . . . . . . . . . . . . . . . . 4	1.1. Background . . . . . . . . . . . . . . . . . . . . . 5
	1.2. Protocol Overview. . . . . . . . . . . . . . . . . . 6	1.2. Protocol Overview. . . . . . . . . . . . . . . . . . 7
	1.3. Administrative Scoping and BSR . . . . . . . . . . . 7	1.3. Administrative Scoping and BSR . . . . . . . . . . . 8
	2. BSR State and Timers. . . . . . . . . . . . . . . . . . 8	2. BSR State and Timers. . . . . . . . . . . . . . . . . . 9
	3. Bootstrap Router Election and RP-Set	3.1. Bootstrap Router Election and RP-Set
	Distribution. . . . . . . . . . . . . . . . . . . . . . 9	Distribution . . . . . . . . . . . . . . . . . . . . 11
	3.1. Bootstrap Router Election. . . . . . . . . . . . . . 9	3.1. Bootstrap Router Election. . . . . . . . . . . . . . 11
	3.1.1. Per-Scope-Zone Candidate-BSR State	3.1.1. Per-Scope-Zone Candidate-BSR State

	Machine . . . . . . . . . . . . . . . . . . . . . 10	Machine . . . . . . . . . . . . . . . . . . . . . 11
	3.1.2. Per-Scope-Zone State Machine for Non-	3.1.2. Per-Scope-Zone State Machine for Non-

	Candidate-BSR Routers . . . . . . . . . . . . . . 12	Candidate-BSR Routers . . . . . . . . . . . . . . 13
	3.1.3. Bootstrap Message Processing Checks . . . . . . . 14	3.1.3. Bootstrap Message Processing Checks . . . . . . . 15
	3.1.4. State Machine Transition Events . . . . . . . . . 15	3.1.4. State Machine Transition Events . . . . . . . . . 16
	3.1.5. State Machine Actions . . . . . . . . . . . . . . 16	3.1.5. State Machine Actions . . . . . . . . . . . . . . 17
	3.2. Sending Candidate-RP-Advertisement Messages. . . . . 17	3.2. Sending Candidate-RP-Advertisement Messages. . . . . 18
	3.3. Creating the RP-Set at the BSR . . . . . . . . . . . 19	3.3. Creating the RP-Set at the BSR . . . . . . . . . . . 20
	3.4. Forwarding Bootstrap Messages. . . . . . . . . . . . 21	3.4. Forwarding Bootstrap Messages. . . . . . . . . . . . 22
	3.5. Bootstrap Messages to New and Rebooting	3.5. Bootstrap Messages to New and Rebooting

	Routers. . . . . . . . . . . . . . . . . . . . . . . 22	Routers. . . . . . . . . . . . . . . . . . . . . . . 23
	3.5.1. No-Forward Bootstrap Messages . . . . . . . . . . 22	3.5.1. No-Forward Bootstrap Messages . . . . . . . . . . 24
	3.5.2. Unicasting Bootstrap Messages . . . . . . . . . . 23	3.5.2. Unicasting Bootstrap Messages . . . . . . . . . . 24
	3.6. Receiving and Using the RP-Set . . . . . . . . . . . 23	3.6. Receiving and Using the RP-Set . . . . . . . . . . . 24
	4. Message Formats . . . . . . . . . . . . . . . . . . . . 23	4. Message Formats . . . . . . . . . . . . . . . . . . . . 24
	4.1. Bootstrap Message Format . . . . . . . . . . . . . . 25	4.1. Bootstrap Message Format . . . . . . . . . . . . . . 27
	4.1.1. Semantic Fragmentation of BSMs. . . . . . . . . . 29	4.1.1. Semantic Fragmentation of BSMs. . . . . . . . . . 31
	4.2. Candidate-RP-Advertisement Message Format. . . . . . 30	4.2. Candidate-RP-Advertisement Message Format. . . . . . 32
	5. Timers and Timer Values . . . . . . . . . . . . . . . . 32	5. Timers and Timer Values . . . . . . . . . . . . . . . . 34
	6. Security Considerations . . . . . . . . . . . . . . . . 36	6. Security Considerations . . . . . . . . . . . . . . . . 37
	6.1. Possible Threats . . . . . . . . . . . . . . . . . . 36	6.1. Possible Threats . . . . . . . . . . . . . . . . . . 37
	6.2. Limiting Third-Party DoS Attacks . . . . . . . . . . 37	6.2. Limiting Third-Party DoS Attacks . . . . . . . . . . 38
	6.3. Bootstrap Message Security . . . . . . . . . . . . . 37	6.3. Bootstrap Message Security . . . . . . . . . . . . . 38
	6.3.1. Rejecting Bootstrap Messages from Invalid	6.3.1. Rejecting Bootstrap Messages from Invalid

	Neighbors . . . . . . . . . . . . . . . . . . . . 38	Neighbors . . . . . . . . . . . . . . . . . . . . 39
	6.4. Candidate-RP-Advertisement Message Security. . . . . 38	6.4. Candidate-RP-Advertisement Message Security. . . . . 39
	6.4.1. Non-Cryptographic Security of C-RP-Adv	6.4.1. Non-Cryptographic Security of C-RP-Adv

	Messages. . . . . . . . . . . . . . . . . . . . . 38
	6.4.2. Cryptographic Security of C-RP-Adv
	Messages. . . . . . . . . . . . . . . . . . . . . 39	Messages. . . . . . . . . . . . . . . . . . . . . 39

	6.5. Denial of Service using IPsec. . . . . . . . . . . . 39	6.4.2. Cryptographic Security of C-RP-Adv
	7. Contributors. . . . . . . . . . . . . . . . . . . . . . 40	Messages. . . . . . . . . . . . . . . . . . . . . 40
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . 40	6.5. Denial of Service using IPsec. . . . . . . . . . . . 40
	9. IANA Considerations . . . . . . . . . . . . . . . . . . 40	7. Contributors. . . . . . . . . . . . . . . . . . . . . . 41
	10. Normative References . . . . . . . . . . . . . . . . . 40	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . 41
	11. Informative References . . . . . . . . . . . . . . . . 41	9. IANA Considerations . . . . . . . . . . . . . . . . . . 41
		10. Normative References . . . . . . . . . . . . . . . . . 41
		11. Informative References . . . . . . . . . . . . . . . . 42

	1. Introduction	1. Introduction

	This document assumes some familiarity with the concepts of Protocol	This document assumes some familiarity with the concepts of Protocol
	Independent Multicast - Sparse Mode (PIM-SM), as defined in [1], and Bi-	Independent Multicast - Sparse Mode (PIM-SM), as defined in [1], and Bi-
	directional Protocol Independent Multicast (BIDIR-PIM), as defined in	directional Protocol Independent Multicast (BIDIR-PIM), as defined in
	[2], as well as with Administratively Scoped IP Multicast, as described	[2], as well as with Administratively Scoped IP Multicast, as described
	in [3], and the IPv6 Scoped Address Architecture, described in [4].	in [3], and the IPv6 Scoped Address Architecture, described in [4].

	For correct operation, every multicast router within a PIM domain must	For correct operation, every multicast router within a PIM domain must

	skipping to change at page 21, line 10 ¶	skipping to change at page 22, line 14 ¶

	A scoped BSM MUST have at least one group range, and the first group	A scoped BSM MUST have at least one group range, and the first group
	range in a scoped BSM MUST have the "Admin Scope Zone" bit set. This	range in a scoped BSM MUST have the "Admin Scope Zone" bit set. This
	group range identifies the scope of the BSM. In a scoped IPv4 BSM, the	group range identifies the scope of the BSM. In a scoped IPv4 BSM, the
	first group range is the range corresponding to the scope of the BSM.	first group range is the range corresponding to the scope of the BSM.
	In a scoped IPv6 BSM, the first group range may be any group range	In a scoped IPv6 BSM, the first group range may be any group range
	subject to the general condition that all the group ranges in such a BSM	subject to the general condition that all the group ranges in such a BSM
	MUST have a mask length of at least 16 and MUST have the same scope ID	MUST have a mask length of at least 16 and MUST have the same scope ID
	as the scope of the BSM.	as the scope of the BSM.


	RP mappings may be included in the first group range of a BSM, just as	Apart from identifying the scope, the first group range in a scoped BSM
	for any other group range. After this group range, other group ranges	is treated like any other range with respect to RP mappings. I.e., all
	for which there are RP mappings appear in any order.	mappings in the RP-set for this group range, if any, must be included in
		this first group range in the BSM. After this group range, other group
		ranges in this scope for which there are RP mappings appear in any
		order.

	The "Admin Scope Zone" bit of all group ranges other than the first	The "Admin Scope Zone" bit of all group ranges other than the first
	SHOULD be set to 0 on origination, and MUST be ignored on receipt.	SHOULD be set to 0 on origination, and MUST be ignored on receipt.

	When an elected BSR is being shut down, it should immediately originate	When an elected BSR is being shut down, it should immediately originate
	a Bootstrap message listing its current RP-Set, but with the BSR	a Bootstrap message listing its current RP-Set, but with the BSR
	Priority field set to the lowest priority value possible. This will	Priority field set to the lowest priority value possible. This will
	cause the election of a new BSR to happen more quickly.	cause the election of a new BSR to happen more quickly.

	3.4. Forwarding Bootstrap Messages	3.4. Forwarding Bootstrap Messages

	skipping to change at page 23, line 35 ¶	skipping to change at page 24, line 44 ¶
	routing protocol is also not part of the present specification.	routing protocol is also not part of the present specification.

	Some group-to-RP mappings in the RP-Set indicate group ranges for which	Some group-to-RP mappings in the RP-Set indicate group ranges for which
	PIM-SM should be used; others indicate group ranges for use with BIDIR-	PIM-SM should be used; others indicate group ranges for use with BIDIR-
	PIM. Routers that only support one of these protocols MUST NOT ignore	PIM. Routers that only support one of these protocols MUST NOT ignore
	ranges indicated as being for the other protocol. They MUST NOT treat	ranges indicated as being for the other protocol. They MUST NOT treat
	them as being for the protocol they support.	them as being for the protocol they support.

	4. Message Formats	4. Message Formats


	BSR messages are PIM messages, as defined in [1]. The values of the PIM	BSR messages are PIM messages, as defined in [1].
	Message Type field for BSR messages are:	The values of the PIM Message Type field for BSR messages are:

	4 Bootstrap	4 Bootstrap

	8 Candidate-RP-Advertisement	8 Candidate-RP-Advertisement

	As with all other PIM control messages, BSR messages have IP protocol	As with all other PIM control messages, BSR messages have IP protocol
	number 103.	number 103.

	Candidate-RP-Advertisement messages are unicast to a BSR. Usually,	Candidate-RP-Advertisement messages are unicast to a BSR. Usually,
	Bootstrap messages are multicast with TTL 1 to the ALL-PIM-ROUTERS	Bootstrap messages are multicast with TTL 1 to the ALL-PIM-ROUTERS

	skipping to change at page 40, line 34 ¶	skipping to change at page 41, line 34 ¶
	Rishabh Parekh and Katta Sambasivarao.	Rishabh Parekh and Katta Sambasivarao.

	9. IANA Considerations	9. IANA Considerations

	This document has no actions for IANA.	This document has no actions for IANA.

	10. Normative References	10. Normative References

	[1] W. Fenner, M. Handley, H. Holbrook, I. Kouvelas, "Protocol	[1] W. Fenner, M. Handley, H. Holbrook, I. Kouvelas, "Protocol
	Independent Multicast - Sparse Mode (PIM-SM): Protocol	Independent Multicast - Sparse Mode (PIM-SM): Protocol

	Specification (Revised)", Internet Draft draft-ietf-pim-sm-	Specification (Revised)", RFC 4601, August 2006.
	v2-new-11.txt

	[2] M. Handley, I. Kouvelas, T. Speakman, L. Vicisano, "Bi-directional	[2] M. Handley, I. Kouvelas, T. Speakman, L. Vicisano, "Bi-directional
	Protocol Independent Multicast (BIDIR-PIM)", Internet Draft draft-	Protocol Independent Multicast (BIDIR-PIM)", Internet Draft draft-
	ietf-pim-bidir-08.txt	ietf-pim-bidir-08.txt

	[3] D. Meyer, "Administratively Scoped IP Multicast", RFC 2365, Jul	[3] D. Meyer, "Administratively Scoped IP Multicast", RFC 2365, Jul
	1998.	1998.

	[4] S. Deering, B. Haberman, T. Jinmei, E. Nordmark, B. Zill, "IPv6	[4] S. Deering, B. Haberman, T. Jinmei, E. Nordmark, B. Zill, "IPv6
	Scoped Address Architecture", RFC 4007, Mar 2005.	Scoped Address Architecture", RFC 4007, Mar 2005.

	skipping to change at page 42, line 12 ¶	skipping to change at page 43, line 12 ¶
	USA	USA
	jchl@arastra.com	jchl@arastra.com
	Stig Venaas	Stig Venaas
	UNINETT	UNINETT
	NO-7465 Trondheim	NO-7465 Trondheim
	Norway	Norway
	venaas@uninett.no	venaas@uninett.no

	Copyright Statement	Copyright Statement


	Copyright (C) The Internet Society (2006). This document is subject to	Copyright (C) The IETF Trust (2007).
	the rights, licenses and restrictions contained in BCP 78, and except as
	set forth therein, the authors retain all their rights.	This document is subject to the rights, licenses and restrictions
		contained in BCP 78, and except as set forth therein, the authors retain
		all their rights.

	This document and the information contained herein are provided on an	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR

	IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET	IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,	INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE	IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

	Intellectual Property	Intellectual Property

	The IETF takes no position regarding the validity or scope of any	The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to	Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in this	pertain to the implementation or use of the technology described in this
	document or the extent to which any license under such rights might or	document or the extent to which any license under such rights might or
	might not be available; nor does it represent that it has made any	might not be available; nor does it represent that it has made any

End of changes. 15 change blocks.
	56 lines changed or deleted	60 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/