< draft-shen-pim-nnhop-nodes-00.txt		draft-shen-pim-nnhop-nodes-01.txt >
	Network Working Group Naiming Shen		Network Working Group Naiming Shen
	Internet Draft Liming Wei		Internet Draft Liming Wei
	Redback Networks		Redback Networks
	Expiration Date: June 2004 Dino Farinacci		Expiration Date: January 2005 Dino Farinacci
	Procket Networks		Procket Networks
	December 2003		July 2004
	Discovering PIM-SM Next-Nexthop Downstream Nodes		Discovering PIM-SM Next-Nexthop Downstream Nodes
	<draft-shen-pim-nnhop-nodes-00.txt>		<draft-shen-pim-nnhop-nodes-01.txt>
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		By submitting this Internet-Draft, I certify that any applicable
	all provisions of Section 10 of RFC2026.		patent or other IPR claims of which I am aware have been disclosed,
			or will be disclosed, and any of which I become aware will be
			disclosed, in accordance with RFC 3668.
	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.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as ``work in progress.''		material or to cite them other than as ``work in progress.''
	skipping to change at page 6, line 43 ¶		skipping to change at page 6, line 43 ¶
	The Router-ID and Next-Nexthop Node Request option types		The Router-ID and Next-Nexthop Node Request option types
	in Hello messages, the Next-Nexthop Join/Prune Mesage type and		in Hello messages, the Next-Nexthop Join/Prune Mesage type and
	the Next-Nexthop Node Address are proposed in this document.		the Next-Nexthop Node Address are proposed in this document.
	This PIM-SM extension requires that IANA allocate those numbers.		This PIM-SM extension requires that IANA allocate those numbers.
	6. Acknowledgments		6. Acknowledgments
	The authors would like to thank Yiqun Cai for the discussion and		The authors would like to thank Yiqun Cai for the discussion and
	comments to this document.		comments to this document.
	7. Intellectual Property Considerations		7. References
	Redback Networks may have intellectual property rights claimed in
	regard to some of the specification contained in this document.
	8. Full Copyright Statement
	Copyright (C) The Internet Society (2002). All Rights Reserved.
	This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of
	developing Internet standards in which case the procedures for
	copyrights defined in the Internet Standards process must be
	followed, or as required to translate it into languages other than
	English.
	The limited permissions granted above are perpetual and will not be
	revoked by the Internet Society or its successors or assigns.
	This document and the information contained herein is provided on an
	"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
	TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
	BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
	HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
	MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	9. References
	[1] Estrin, et al., "Protocol Independent Multicast-Sparse Mode		[1] Estrin, et al., "Protocol Independent Multicast-Sparse Mode
	(PIM- SM): Protocol Specification", RFC 2362, June 1998.		(PIM- SM): Protocol Specification", RFC 2362, June 1998.
	[2] Shen, N., Pan, P., "Nexthop Fast ReRoute for IP and MPLS",		[2] Shen, N., Pan, P., "Nexthop Fast ReRoute for IP and MPLS",
	Internet draft, draft-shen-nhop-fastreroute-00.txt, work in		Internet draft, draft-shen-nhop-fastreroute-01.txt, work in
	progress.		progress.
	[3] Bradner, S., "Key words for use in RFCs to Indicate		[3] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	10. Author's Addresses		8. Author's Addresses
	Naiming Shen		Naiming Shen
	Redback Networks		Redback Networks
	300 Holger Way		300 Holger Way
	San Jose, CA 95134		San Jose, CA 95134
	Email: naiming@redback.com		Email: naiming@redback.com
	Liming Wei		Liming Wei
	Redback Networks		Redback Networks
	300 Holger Way		300 Holger Way
	San Jose, CA 95134		San Jose, CA 95134
	Email: lwei@redback.com		Email: lwei@redback.com
	Dino Farinacci		Dino Farinacci
	Procket Networks		Procket Networks
	dino@procket.com		dino@procket.com
			7. Intellectual Property Considerations
			The IETF takes no position regarding the validity or scope of any
			intellectual property or other rights that might be claimed to
			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 might not be available; neither does it represent that it
			has made any effort to identify any such rights. Information on the
			IETF's procedures with respect to rights in standards-track and
			standards-related documentation can be found in BCP-11. Copies of
			claims of rights made available for publication and any assurances of
			licenses to be made available, or the result of an attempt made to
			obtain a general license or permission for the use of such
			proprietary rights by implementors or users of this specification can
			be obtained from the IETF Secretariat.
			The IETF invites any interested party to bring to its attention any
			copyrights, patents or patent applications, or other proprietary
			rights which may cover technology that may be required to practice
			this standard. Please address the information to the IETF Executive
			Director.
			8. Full Copyright Notice
			Copyright (C) The Internet Society (2004). 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 is provided on an
			"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
			TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
			BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
			HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
			MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
End of changes. 8 change blocks.
	40 lines changed or deleted		10 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/