< draft-ietf-msdp-spec-17.txt		draft-ietf-msdp-spec-18.txt >
	INTERNET-DRAFT Bill Fenner (Editor)		INTERNET-DRAFT Bill Fenner (Editor)
	draft-ietf-msdp-spec-17.txt David Meyer (Editor)		draft-ietf-msdp-spec-18.txt David Meyer (Editor)
	Category Informational		Category Experimental
	Expires: November 2003 May 2003		Expires: November 2003 May 2003
	Multicast Source Discovery Protocol (MSDP)		Multicast Source Discovery Protocol (MSDP)
	<draft-ietf-msdp-spec-17.txt>		<draft-ietf-msdp-spec-18.txt>
	Status of this Document		Status of this Document
	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		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 23, line 19 ¶		skipping to change at page 23, line 19 ¶
	that do not support it. However, if one side of the connection is		that do not support it. However, if one side of the connection is
	configured with Keyed MD5 and the other side is not, the connection		configured with Keyed MD5 and the other side is not, the connection
	SHOULD NOT be established.		SHOULD NOT be established.
	In addition, to mitigate state explosion during denial of service and		In addition, to mitigate state explosion during denial of service and
	other attacks, SA filters and limits SHOULD be used with MSDP to		other attacks, SA filters and limits SHOULD be used with MSDP to
	limit the sources and groups that will be passed between RPs.		limit the sources and groups that will be passed between RPs.
	19. IANA Considerations		19. IANA Considerations
	This document defines the seven MSDP TLV values specificed in Section		This document creates a new namespace called "MSDP TLV Values" that
	12.2.		the IANA should manage. The intial seven MSDP TLV values are
			specified in Section 12.2. The following two sections describe the
			rules for allocating new MSDP TLV values.
	19.1. IANA Allocated TLV Range		19.1. IANA Allocated TLV Range
	MSDP TLV values in the range [8,200] (inclusive) are to be allocated		MSDP TLV values in the range [8,200] (inclusive) are to be allocated
	using an IESG Approval or Standards Action process.		using an IESG Approval or Standards Action process [RFC2434].
	19.2. Experimental TLV Range		19.2. Experimental TLV Range
	TLV values in the range [201,255] (inclusive) are allocated for		TLV values in the range [201,255] (inclusive) are allocated for
	experimental use.		experimental use.
	20. References		20. References
	20.1. Normative References		20.1. Normative References
	skipping to change at page 24, line 28 ¶		skipping to change at page 24, line 28 ¶
	[RFC2362] Estrin D., et al., "Protocol Independent		[RFC2362] Estrin D., et al., "Protocol Independent
	Multicast - Sparse Mode (PIM-SM): Protocol		Multicast - Sparse Mode (PIM-SM): Protocol
	Specification", RFC 2362, June 1998.		Specification", RFC 2362, June 1998.
	[RFC2365] Meyer, D. "Administratively Scoped IP Multicast",		[RFC2365] Meyer, D. "Administratively Scoped IP Multicast",
	RFC 2365, July, 1998.		RFC 2365, July, 1998.
	[RFC2385] Heffernan. A, "Protection of BGP Sessions via the		[RFC2385] Heffernan. A, "Protection of BGP Sessions via the
	TCP MD5 Signature Option", August, 1998.		TCP MD5 Signature Option", August, 1998.
			[RFC2434] Narten, T., and H. Alvestrand, "Guidelines for
			Writing an IANA Considerations Section in
			RFCs", RFC2434/BCP0026, October, 1998.
	[RFC3446] Kim, D., et al., "Anycast Rendezvous Point (RP)		[RFC3446] Kim, D., et al., "Anycast Rendezvous Point (RP)
	Mechanism using Protocol Independent Multicast		Mechanism using Protocol Independent Multicast
	(PIM) and Multicast Source Discovery Protocol		(PIM) and Multicast Source Discovery Protocol
	(MSDP)", RFC 3446, January, 2003.		(MSDP)", RFC 3446, January, 2003.
	20.2. Informative References		20.2. Informative References
	[RFC2119] S. Bradner, "Key words for use in RFCs to		[RFC2119] S. Bradner, "Key words for use in RFCs to
	Indicate Requirement Levels", RFC 2119, March,		Indicate Requirement Levels", RFC 2119, March,
	1997.		1997.
End of changes. 6 change blocks.
	6 lines changed or deleted		13 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/