< draft-ietf-nvo3-mcast-framework-07.txt   draft-ietf-nvo3-mcast-framework-08.txt >
NVO3 working group A. Ghanwani NVO3 working group A. Ghanwani
Internet Draft Dell Internet Draft Dell
Intended status: Informational L. Dunbar Intended status: Informational L. Dunbar
Expires: November 8, 2017 M. McBride Expires: November 8, 2017 M. McBride
Huawei Huawei
V. Bannai V. Bannai
Google Google
R. Krishnan R. Krishnan
Dell Dell
February 16, 2017 May 12, 2017
A Framework for Multicast in Network Virtualization Overlays A Framework for Multicast in Network Virtualization Overlays
draft-ietf-nvo3-mcast-framework-07 draft-ietf-nvo3-mcast-framework-08
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified, provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, except to publish it and derivative works of it may not be created, except to publish it
as an RFC and to translate it into languages other than English. as an RFC and to translate it into languages other than English.
skipping to change at page 3, line 25 skipping to change at page 3, line 25
This document provides a framework for supporting multicast traffic, This document provides a framework for supporting multicast traffic,
in a network that uses Network Virtualization using Overlays over in a network that uses Network Virtualization using Overlays over
Layer 3 (NVO3). Both infrastructure multicast and application- Layer 3 (NVO3). Both infrastructure multicast and application-
specific multicast are considered. It describes the various specific multicast are considered. It describes the various
mechanisms and considerations that can be used for delivering such mechanisms and considerations that can be used for delivering such
traffic in networks that use NVO3. traffic in networks that use NVO3.
The reader is assumed to be familiar with the terminology as defined The reader is assumed to be familiar with the terminology as defined
in the NVO3 Framework document [RFC7365] and NVO3 Architecture in the NVO3 Framework document [RFC7365] and NVO3 Architecture
document [NVO3-ARCH]. document [RFC8014].
1.1. Infrastructure multicast 1.1. Infrastructure multicast
Infrastructure multicast is a capability needed by networking Infrastructure multicast is a capability needed by networking
services, such as Address Resolution Protocol (ARP), Neighbor services, such as Address Resolution Protocol (ARP), Neighbor
Discovery (ND), Dynamic Host Configuration Protocol (DHCP), Discovery (ND), Dynamic Host Configuration Protocol (DHCP),
multicast Domain Name Server (mDNS), etc.. RFC3819 Section 5 and 6 multicast Domain Name Server (mDNS), etc.. RFC3819 Section 5 and 6
have detailed description for some of the infrastructure multicast have detailed description for some of the infrastructure multicast
[RFC 3819]. It is possible to provide solutions for these that do [RFC 3819]. It is possible to provide solutions for these that do
not involve multicast in the underlay network. In the case of not involve multicast in the underlay network. In the case of
skipping to change at page 6, line 6 skipping to change at page 6, line 6
1. No multicast support. 1. No multicast support.
2. Replication at the source NVE. 2. Replication at the source NVE.
3. Replication at a multicast service node. 3. Replication at a multicast service node.
4. IP multicast in the underlay. 4. IP multicast in the underlay.
These methods are briefly mentioned in the NVO3 Framework [FW] and These methods are briefly mentioned in the NVO3 Framework [FW] and
NVO3 architecture [NVO3-ARCH] document. This document provides more NVO3 architecture [RFC8014] document. This document provides more
details about the basic mechanisms underlying each of these methods details about the basic mechanisms underlying each of these methods
and discusses the issues and tradeoffs of each. and discusses the issues and tradeoffs of each.
We note that other methods are also possible, such as [EDGE-REP], We note that other methods are also possible, such as [EDGE-REP],
but we focus on the above four because they are the most common. but we focus on the above four because they are the most common.
3.1. No multicast support 3.1. No multicast support
In this scenario, there is no support whatsoever for multicast In this scenario, there is no support whatsoever for multicast
traffic when using the overlay. This method can only work if the traffic when using the overlay. This method can only work if the
skipping to change at page 9, line 25 skipping to change at page 9, line 25
Mode (ATM) Forum's LAN Emulation (LANE)LANE specification [LANE]. Mode (ATM) Forum's LAN Emulation (LANE)LANE specification [LANE].
The MSN is similar to the RP in PIM SM, but different in that the The MSN is similar to the RP in PIM SM, but different in that the
user data traffic are carried by the NVO3 tunnels. user data traffic are carried by the NVO3 tunnels.
The following are the possible ways for the MSN to get the The following are the possible ways for the MSN to get the
membership information for each multicast group: membership information for each multicast group:
- The MSN can obtain this membership information from the IGMP/MLD - The MSN can obtain this membership information from the IGMP/MLD
report messages sent by TSs in response to IGMP/MLD query messages report messages sent by TSs in response to IGMP/MLD query messages
from the MSN. The IGMP/MLD query messages are sent from the MSN to from the MSN. The IGMP/MLD query messages are sent from the MSN to
the NVEs, which then multicast the query messages to TSs attached the NVEs, which then forward the query messages to TSs attached to
to them. An IGMP/MLD query messages sent out by the MSN to an NVE them. An IGMP/MLD query messages sent out by the MSN to an NVE is
is encapsulated with the MSN address in the outer source address encapsulated with the MSN address in the outer source address
field and the address of the NVE in the outer destination address field and the address of the NVE in the outer destination address
field. The encapsulated IGMP/MLD query messages also has a VNID field. The encapsulated IGMP/MLD query messages also has a VNID
for a virtual network (VN) that TSs belong in the outer header and for a virtual network (VN) that TSs belong in the outer header and
a multicast address in the inner destination address field. Upon a multicast address in the inner destination address field. Upon
receiving the encapsulated IGMP/MLD query message, the NVE receiving the encapsulated IGMP/MLD query message, the NVE
establishes a mapping "MSN address" <-> "multicast address", establishes a mapping "MSN address" <-> "multicast address",
decapsulates the received encapsulated IGMP/MLD message, and decapsulates the received encapsulated IGMP/MLD message, and
multicast the decapsulated IGMP/MLD query message to TSs that multicast the decapsulated query message to TSs that belong to the
belong to the VN under the NVE. A IGMP/MLD report message sent by VN under the NVE. A IGMP/MLD report message sent by a TS includes
a TS includes the multicast address and the address of the TS. the multicast address and the address of the TS. With the proper
With the proper "MSN Address" <-> "Multicast-Address" mapping, the "MSN Address" <-> "Multicast-Address" mapping, the NVEs can
NVEs can encapsulate all multicast data frames sent by TSs to the encapsulate all multicast data frames to the "Multicast-Address"
"Multicast-Address" with the address of the MSN in the outer with the address of the MSN in the outer destination address
destination address field. field.
- The MSN can obtain the membership information from the NVEs that - The MSN can obtain the membership information from the NVEs that
have the capability to establish multicast groups by snooping have the capability to establish multicast groups by snooping
native IGMP/MLD messages (p.s. the communication must be specific native IGMP/MLD messages (p.s. the communication must be specific
to the multicast addresses), or by having the NVA obtain the to the multicast addresses), or by having the NVA obtain the
information from the NVEs, and in turn have MSN communicate with information from the NVEs, and in turn have MSN communicate with
the NVA. This approach requires additional protocol between MSN the NVA. This approach requires additional protocol between MSN
and NVEs. and NVEs.
Unlike the method described in Section 3.2, there is no performance Unlike the method described in Section 3.2, there is no performance
skipping to change at page 14, line 18 skipping to change at page 14, line 18
application specific multicast in networks that use NVO3. It application specific multicast in networks that use NVO3. It
highlights the basics of each mechanism and some of the issues with highlights the basics of each mechanism and some of the issues with
them. As solutions are developed, the protocols would need to them. As solutions are developed, the protocols would need to
consider the use of these mechanisms and co-existence may be a consider the use of these mechanisms and co-existence may be a
consideration. It also highlights some of the requirements for consideration. It also highlights some of the requirements for
supporting multicast applications in an NVO3 network. supporting multicast applications in an NVO3 network.
7. Security Considerations 7. Security Considerations
This draft does not introduce any new security considerations beyond This draft does not introduce any new security considerations beyond
what may be present in proposed solutions. what is described n NVO3 Architecture (RFC8014).
8. IANA Considerations 8. IANA Considerations
This document requires no IANA actions. RFC Editor: Please remove This document requires no IANA actions. RFC Editor: Please remove
this section before publication. this section before publication.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC7365] Lasserre, M. et al., "Framework for data center (DC) [RFC3376] Cain B. et al., "Internet Group Management Protocol,
Version 3", October 2002.
[RFC6513] Rosen, E. et al., "Multicast in MPLS/BGP IP VPNs",
February 2012.
[RFC7364] Narten, T. et al., "Problem statement: Overlays for
network virtualization", October 2014. network virtualization", October 2014.
[RFC7364] Narten, T. et al., "Problem statement: Overlays for [RFC7365] Lasserre, M. et al., "Framework for data center (DC)
network virtualization", October 2014. network virtualization", October 2014.
[NVO3-ARCH] Narten, T. et al.," An Architecture for Overlay Networks [RFC8014] Narten, T. et al.," An Architecture for Overlay Networks
(NVO3)", RFC8014, Dec. 2016. (NVO3)", RFC8014, Dec. 2016.
[RFC3376] Cain B. et al., "Internet Group Management Protocol, 9.2. Informative References
Version 3", October 2002.
[RFC6513] Rosen, E. et al., "Multicast in MPLS/BGP IP VPNs", [RFC3569] S. Bhattacharyya, Ed., "An Overview of Source-Specific
February 2012. Multicast (SSM)", July 2003.
9.2. Informative References [RFC3819] P. Harn et al., "Advice for Internet Subnetwork
Designers", July 2004.
[RFC7348] Mahalingam, M. et al., " Virtual eXtensible Local Area [RFC4762] Lasserre, M., and Kompella, V. (Eds.), "Virtual Private
LAN Service (VPLS) using Label Distribution Protocol (LDP)
signaling," January 2007.
[RFC6831] Farinacci, D. et al., "The Locator/ID Seperation Protocol
(LISP) for Multicast Environments", Jan, 2013.
[RFC7117] Aggarwal, R. et al., "Multicast in VPLS," February 2014.
[RFC7348] Mahalingam, M. et al., " Virtual eXtensible Local Area
Network (VXLAN): A Framework for Overlaying Virtualized Network (VXLAN): A Framework for Overlaying Virtualized
Layer 2 Networks over Layer 3 Networks", August 2014. Layer 2 Networks over Layer 3 Networks", August 2014.
[RFC7637] Garg P. and Wang, Y. (Eds.), "NVGRE: Network [RFC7637] Garg P. and Wang, Y. (Eds.), "NVGRE: Network
Vvirtualization using Generic Routing Encapsulation", Vvirtualization using Generic Routing Encapsulation",
September 2015. September 2015.
[BIER-ARCH]
Wijnands, IJ. (Ed.) et al., "Multicast using Bit Index
Explicit Replication," <draft-ietf-bier-architecture-03>,
January 2016.
[DC-MC] McBride, M. and Lui, H., "Multicast in the data center [DC-MC] McBride, M. and Lui, H., "Multicast in the data center
overview," <draft-mcbride-armd-mcast-overview-02>, work in overview," <draft-mcbride-armd-mcast-overview-02>, work in
progress, July 2012. progress, July 2012.
[ISIS-Multicast] [EDGE-REP]
Yong, L. et al., "ISIS Protocol Extension for Building
Distribution Trees", <draft-yong-isis-ext-4-distribution-
tree-03>, work in progress, October 2014.
[RFC4762] Lasserre, M., and Kompella, V. (Eds.), "Virtual Private
LAN Service (VPLS) using Label Distribution Protocol (LDP)
signaling," January 2007.
[RFC7117] Aggarwal, R. et al., "Multicast in VPLS," February 2014.
[LANE] "LAN emulation over ATM," The ATM Forum, af-lane-0021.000,
January 1995.
[EDGE-REP]
Marques P. et al., "Edge multicast replication for BGP IP Marques P. et al., "Edge multicast replication for BGP IP
VPNs," <draft-marques-l3vpn-mcast-edge-01>, work in VPNs," <draft-marques-l3vpn-mcast-edge-01>, work in
progress, June 2012. progress, June 2012.
[RFC 3569]
S. Bhattacharyya, Ed., "An Overview of Source-Specific
Multicast (SSM)", July 2003.
[LISP-Signal-Free]
Moreno, V. and Farinacci, D., "Signal-Free LISP
Multicast", <draft-ietf-lisp-signal-free-multicast-01>,
work in progress, April 2016.
[VXLAN-GPE]
Kreeger, L. and Elzur, U. (Eds.), "Generic Protocol
Extension for VXLAN", <draft-ietf-nvo3-vxlan-gpe-02>, work
in progress, April 2016.
[Geneve] [Geneve]
Gross, J. and Ganga, I. (Eds.), "Geneve: Generic Network Gross, J. and Ganga, I. (Eds.), "Geneve: Generic Network
Virtualization Encapsulation", <draft-ietf-nvo3-geneve- Virtualization Encapsulation", <draft-ietf-nvo3-geneve-
01>, work in progress, January 2016. 01>, work in progress, January 2016.
[GUE] [GUE]
Herbert, T. et al., "Generic UDP Encapsulation", <draft- Herbert, T. et al., "Generic UDP Encapsulation", <draft-
ietf-nvo3-gue-02>, work in progress, December 2015. ietf-nvo3-gue-02>, work in progress, December 2015.
[BIER-ARCH] [ISIS-Multicast]
Yong, L. et al., "ISIS Protocol Extension for Building
Distribution Trees", <draft-yong-isis-ext-4-distribution-
tree-03>, work in progress, October 2014.
Wijnands, IJ. (Ed.) et al., "Multicast using Bit Index [LANE] "LAN emulation over ATM," The ATM Forum, af-lane-0021.000,
Explicit Replication," <draft-ietf-bier-architecture-03>, January 1995.
January 2016.
[RFC 3819] [LISP-Signal-Free]
P. Harn et al., "Advice for Internet Subnetwork Designers", Moreno, V. and Farinacci, D., "Signal-Free LISP
July 2004. Multicast", <draft-ietf-lisp-signal-free-multicast-01>,
work in progress, April 2016.
[RFC6831] Farinacci, D. et al., "The Locator/ID Seperation Protocol [VXLAN-GPE]
(LISP) for Multicast Environments", Jan, 2013.
Kreeger, L. and Elzur, U. (Eds.), "Generic Protocol
Extension for VXLAN", <draft-ietf-nvo3-vxlan-gpe-02>, work
in progress, April 2016.
10. Acknowledgments 10. Acknowledgments
Many thanks are due to Dino Farinacci, Erik Nordmark, Lucy Yong, Many thanks are due to Dino Farinacci, Erik Nordmark, Lucy Yong,
Nicolas Bouliane, Saumya Dikshit, Joe Touch, Olufemi Komolafe, and Nicolas Bouliane, Saumya Dikshit, Joe Touch, Olufemi Komolafe, and
Matthew Bocci, for their valuable comments and suggestions. Matthew Bocci, for their valuable comments and suggestions.
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
Authors' Addresses Authors' Addresses
 End of changes. 25 change blocks. 
69 lines changed or deleted 61 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/