draft-ietf-mboned-dc-deploy-00.txt		draft-ietf-mboned-dc-deploy-01.txt
	Internet Engineering Task Force M. McBride		Internet Engineering Task Force M. McBride
	Internet-Draft Huawei Technologies		Internet-Draft Huawei Technologies
	Intended status: Informational February 18, 2013		Intended status: Informational August 23, 2013
	Expires: August 22, 2013		Expires: February 24, 2014
	Multicast in the Data Center Overview		Multicast in the Data Center Overview
	draft-ietf-mboned-dc-deploy-00		draft-ietf-mboned-dc-deploy-01
	Abstract		Abstract
	There has been much interest in issues surrounding massive amounts of		There has been much interest in issues surrounding massive amounts of
	hosts in the data center. These issues include the prevalent use of		hosts in the data center. These issues include the prevalent use of
	IP Multicast within the Data Center. Its important to understand how		IP Multicast within the Data Center. Its important to understand how
	IP Multicast is being deployed in the Data Center to be able to		IP Multicast is being deployed in the Data Center to be able to
	understand the surrounding issues with doing so. This document		understand the surrounding issues with doing so. This document
	provides a quick survey of uses of multicast in the data center and		provides a quick survey of uses of multicast in the data center and
	should serve as an aid to further discussion of issues related to		should serve as an aid to further discussion of issues related to
	skipping to change at page 1, line 36		skipping to change at page 1, line 36
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	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."
	This Internet-Draft will expire on August 22, 2013.		This Internet-Draft will expire on February 24, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 29		skipping to change at page 3, line 29
	survey of multicast in the data center and should serve as an aid to		survey of multicast in the data center and should serve as an aid to
	further discussion of issues related to multicast in the data center.		further discussion of issues related to multicast in the data center.
	ARP/ND issues are not addressed in this document except to explain		ARP/ND issues are not addressed in this document except to explain
	how address resolution occurs with multicast.		how address resolution occurs with multicast.
	2. Multicast Applications in the Data Center		2. Multicast Applications in the Data Center
	There are many data center operators who do not deploy Multicast in		There are many data center operators who do not deploy Multicast in
	their networks for scalability and stability reasons. There are also		their networks for scalability and stability reasons. There are also
	many operators for whom multicast is critical and is enabled on their		many operators for whom multicast is a critical protocol within their
	data center switches and routers. For this latter group, there are		network and is enabled on their data center switches and routers.
	several uses of multicast in their data centers. An understanding of		For this latter group, there are several uses of multicast in their
	the uses of that multicast is important in order to properly support		data centers. An understanding of the uses of that multicast is
	these applications in the ever evolving data centers. If, for		important in order to properly support these applications in the ever
	instance, the majority of the applications are discovering/signaling		evolving data centers. If, for instance, the majority of the
	each other, using multicast, there may be better ways to support them		applications are discovering/signaling each other, using multicast,
	then using multicast. If, however, the multicasting of data is		there may be better ways to support them then using multicast. If,
	occurring in large volumes, there is a need for good data center		however, the multicasting of data is occurring in large volumes,
	overlay multicast support. The applications either fall into the		there is a need for good data center overlay multicast support. The
	category of those that leverage L2 multicast for discovery or of		applications either fall into the category of those that leverage L2
	those that require L3 support and likely span multiple subnets.		multicast for discovery or of those that require L3 support and
			likely span multiple subnets.
	2.1. Client-Server Applications		2.1. Client-Server Applications
	IPTV servers use multicast to deliver content from the data center to		IPTV servers use multicast to deliver content from the data center to
	end users. IPTV is typically a one to many application where the		end users. IPTV is typically a one to many application where the
	hosts are configured for IGMPv3, the switches are configured with		hosts are configured for IGMPv3, the switches are configured with
	IGMP snooping, and the routers are running PIM-SSM mode. Often		IGMP snooping, and the routers are running PIM-SSM mode. Often
	redundant servers are sending multicast streams into the network and		redundant servers are sending multicast streams into the network and
	the network is forwarding the data across diverse paths.		the network is forwarding the data across diverse paths.
	skipping to change at page 10, line 33		skipping to change at page 10, line 34
	Anoop Ghanwani, Peter Ashwoodsmith, David Allan, Aldrin Isaac, Igor		Anoop Ghanwani, Peter Ashwoodsmith, David Allan, Aldrin Isaac, Igor
	Gashinsky, Michael Smith, Patrick Frejborg, Joel Jaeggli and Thomas		Gashinsky, Michael Smith, Patrick Frejborg, Joel Jaeggli and Thomas
	Narten.		Narten.
	9. IANA Considerations		9. IANA Considerations
	This memo includes no request to IANA.		This memo includes no request to IANA.
	10. Security Considerations		10. Security Considerations
	No security considerations at this time.		No new security considerations result from this document
	11. Informative References		11. Informative References
	[I-D.armd-problem-statement]		[I-D.armd-problem-statement]
	Narten, T., Karir, M., and I. Foo,		Narten, T., Karir, M., and I. Foo,
	"draft-ietf-armd-problem-statement", February 2012.		"draft-ietf-armd-problem-statement", February 2012.
	[I-D.pim-umf-problem-statement]		[I-D.pim-umf-problem-statement]
	Zhou, D., Deng, H., Shi, Y., Liu, H., and I. Bhattacharya,		Zhou, D., Deng, H., Shi, Y., Liu, H., and I. Bhattacharya,
	"draft-dizhou-pim-umf-problem-statement", October 2010.		"draft-dizhou-pim-umf-problem-statement", October 2010.
End of changes. 5 change blocks.
	17 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/