< draft-ietf-msdp-spec-18.txt		draft-ietf-msdp-spec-19.txt >
	INTERNET-DRAFT Bill Fenner (Editor)		INTERNET-DRAFT Bill Fenner (Editor)
	draft-ietf-msdp-spec-18.txt David Meyer (Editor)		draft-ietf-msdp-spec-19.txt David Meyer (Editor)
	Category Experimental		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-18.txt>		<draft-ietf-msdp-spec-19.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 7 ¶		skipping to change at page 23, line 7 ¶
	Nickless, John Meylor, Liming Wei, Manoj Leelanivas, Mark Turner,		Nickless, John Meylor, Liming Wei, Manoj Leelanivas, Mark Turner,
	John Zwiebel, Cristina Radulescu-Banu, Brian Edwards, Selina		John Zwiebel, Cristina Radulescu-Banu, Brian Edwards, Selina
	Priestley, IJsbrand Wijnands, Tom Pusateri, Kristofer Warell, Henning		Priestley, IJsbrand Wijnands, Tom Pusateri, Kristofer Warell, Henning
	Eriksson, Thomas Eriksson, Dave Thaler, and Ravi Shekhar provided		Eriksson, Thomas Eriksson, Dave Thaler, and Ravi Shekhar provided
	useful and productive design feedback and comments. Mike McBride,		useful and productive design feedback and comments. Mike McBride,
	Leonard Giuliano, Swapna Yelamanchi, Toerless Eckert, John Meylor and		Leonard Giuliano, Swapna Yelamanchi, Toerless Eckert, John Meylor and
	Ishan Wu contributed to the final version of the draft.		Ishan Wu contributed to the final version of the draft.
	18. Security Considerations		18. Security Considerations
	An MSDP implementation SHOULD implement Keyed MD5 [RFC2385] to secure		An MSDP implementation MUST implement Keyed MD5 [RFC2385] to secure
	control messages, and MUST be capable of interoperating with peers		control messages, and MUST be capable of interoperating with peers
	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
End of changes. 3 change blocks.
	3 lines changed or deleted		3 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/