| < draft-ietf-nvo3-mcast-framework-00.txt | draft-ietf-nvo3-mcast-framework-01.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 10, 2015 Huawei | Expires: May 9, 2016 M. McBride | |||
| M. McBride | Huawei | |||
| Ericsson | ||||
| V. Bannai | V. Bannai | |||
| R. Krishnan | R. Krishnan | |||
| Dell | Dell | |||
| May 10, 2015 | November 9, 2015 | |||
| A Framework for Multicast in NVO3 | A Framework for Multicast in NVO3 | |||
| draft-ietf-nvo3-mcast-framework-00 | draft-ietf-nvo3-mcast-framework-01 | |||
| 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 1, line 44 ¶ | skipping to change at page 1, line 43 ¶ | |||
| months and may be updated, replaced, or obsoleted by other documents | months and may be updated, replaced, or obsoleted by other documents | |||
| at any time. It is inappropriate to use Internet-Drafts as | at any time. It is inappropriate to use Internet-Drafts as | |||
| reference material or to cite them other than as "work in progress." | reference material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | http://www.ietf.org/ietf/1id-abstracts.txt | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html | http://www.ietf.org/shadow.html | |||
| This Internet-Draft will expire on November 10, 2015. | This Internet-Draft will expire on May 9, 2016. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2015 IETF Trust and the persons identified as the | Copyright (c) 2015 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 | |||
| carefully, as they describe your rights and restrictions with | carefully, as they describe your rights and restrictions with | |||
| respect to this document. Code Components extracted from this | respect to this document. Code Components extracted from this | |||
| document must include Simplified BSD License text as described in | document must include Simplified BSD License text as described in | |||
| Section 4.e of the Trust Legal Provisions and are provided without | Section 4.e of the Trust Legal Provisions and are provided without | |||
| warranty as described in the Simplified BSD License. | warranty as described in the Simplified BSD License. | |||
| Abstract | Abstract | |||
| This document discusses a framework for supporting multicast traffic | This document discusses a framework of supporting multicast traffic | |||
| in a network that uses Network Virtualization using Overlays over | in a network that uses Network Virtualization Overlays over Layer 3 | |||
| Layer 3 (NVO3). Both infrastructure multicast and application- | (NVO3). Both infrastructure multicast and application-specific | |||
| specific multicast are discussed. It describes the various | multicast are discussed. It describes the various mechanisms that | |||
| mechanisms and considerations that can be used for delivering such | can be used for delivering such traffic as well as the data plane | |||
| traffic as well as the data plane and control plane considerations | and control plane considerations for each of the mechanisms. | |||
| for each of the mechanisms. | ||||
| Table of Contents | Table of Contents | |||
| 1. Introduction...................................................3 | 1. Introduction...................................................3 | |||
| 1.1. Infrastructure multicast..................................3 | ||||
| 1.2. Application-specific multicast............................3 | ||||
| 2. Acronyms.......................................................4 | 2. Acronyms.......................................................4 | |||
| 3. Multicast mechanisms in networks that use NVO3.................4 | 3. Multicast mechanisms in networks that use NVO3.................4 | |||
| 3.1. No multicast support......................................5 | 3.1. No multicast support......................................5 | |||
| 3.2. Replication at the source NVE.............................6 | 3.2. Replication at the source NVE.............................6 | |||
| 3.3. Replication at a multicast service node...................8 | 3.3. Replication at a multicast service node...................8 | |||
| 3.4. IP multicast in the underlay..............................9 | 3.4. IP multicast in the underlay..............................9 | |||
| 3.5. Other schemes............................................10 | 3.5. Other schemes............................................10 | |||
| 4. Simultaneous use of more than one mechanism...................11 | 4. Simultaneous use of more than one mechanism...................10 | |||
| 5. Other issues..................................................11 | 5. Other issues..................................................11 | |||
| 5.1. Multicast-agnostic NVEs..................................11 | 5.1. Multicast-agnostic NVEs..................................11 | |||
| 5.2. Multicast membership management for DC with VMs..........12 | 5.2. Multicast membership management for DC with VMs..........12 | |||
| 6. Summary.......................................................12 | 6. Summary.......................................................12 | |||
| 7. Security Considerations.......................................12 | 7. Security Considerations.......................................12 | |||
| 8. IANA Considerations...........................................12 | 8. IANA Considerations...........................................12 | |||
| 9. References....................................................12 | 9. References....................................................12 | |||
| 9.1. Normative References.....................................12 | 9.1. Normative References.....................................12 | |||
| 9.2. Informative References...................................13 | 9.2. Informative References...................................13 | |||
| 10. Acknowledgments..............................................14 | 10. Acknowledgments..............................................14 | |||
| 1. Introduction | 1. Introduction | |||
| Network virtualization using Overlays over Layer 3 (NVO3) is a | Network virtualization using Overlays over Layer 3 (NVO3) is a | |||
| technology that is used to address issues that arise in building | technology that is used to address issues that arise in building | |||
| large, multitenant data centers that make extensive use of server | large, multitenant data centers that make extensive use of server | |||
| virtualization [RFC7364]. | virtualization [RFC7364]. | |||
| This document provides a framework for supporting multicast traffic, | This document provides a framework for supporting multicast traffic, | |||
| skipping to change at page 3, line 47 ¶ | skipping to change at page 3, line 45 ¶ | |||
| Of course it is possible to support all of these infrastructure | Of course it is possible to support all of these infrastructure | |||
| multicast protocols natively if the underlay provides multicast | multicast protocols natively if the underlay provides multicast | |||
| transport. However, even in the presence of multicast transport, it | transport. However, even in the presence of multicast transport, it | |||
| may be beneficial to use the optimizations mentioned above to reduce | may be beneficial to use the optimizations mentioned above to reduce | |||
| the amount of such traffic in the network. | the amount of such traffic in the network. | |||
| 1.2. Application-specific multicast | 1.2. Application-specific multicast | |||
| Application-specific multicast traffic, which may be either Source- | Application-specific multicast traffic, which may be either Source- | |||
| Specific Multicast (SSM) or Any-Source Multicast (ASM)[RFC3569], | Specific Multicast (SSM) or Any-Source Multicast (ASM)[RFC 3569], | |||
| has the following characteristics: | has the following characteristics: | |||
| 1. Receiver hosts are expected to subscribe to multicast content | 1. Receiver hosts are expected to subscribe to multicast content | |||
| using protocols such as IGMP [RFC3376] (IPv4) or MLD (IPv6). | using protocols such as IGMP [RFC3376] (IPv4) or MLD (IPv6). | |||
| Multicast sources and listeners participant in these protocols | Multicast sources and listeners participant in these protocols | |||
| using addresses that are in the Tenant System address domain. | using addresses that are in the Tenant System address domain. | |||
| 2. The list of multicast listeners for each multicast group is not | 2. The list of multicast listeners for each multicast group is not | |||
| known in advance. Therefore, it may not be possible for an NVA | known in advance. Therefore, it may not be possible for an NVA | |||
| to get the list of participants for each multicast group ahead | to get the list of participants for each multicast group ahead | |||
| of time. | of time. | |||
| 2. Acronyms | 2. Acronyms | |||
| skipping to change at page 4, line 43 ¶ | skipping to change at page 4, line 41 ¶ | |||
| 3. Multicast mechanisms in networks that use NVO3 | 3. Multicast mechanisms in networks that use NVO3 | |||
| In NVO3 environments, traffic between NVEs is transported using an | In NVO3 environments, traffic between NVEs is transported using an | |||
| encapsulation such as VXLAN [VXLAN], NVGRE [NVGRE], STT [STT], etc. | encapsulation such as VXLAN [VXLAN], NVGRE [NVGRE], STT [STT], etc. | |||
| Besides the need to support the Address Resolution Protocol (ARP) | Besides the need to support the Address Resolution Protocol (ARP) | |||
| and Neighbor Discovery (ND), there are several applications that | and Neighbor Discovery (ND), there are several applications that | |||
| require the support of multicast and/or broadcast in data centers | require the support of multicast and/or broadcast in data centers | |||
| [DC-MC]. With NVO3, there are many possible ways that multicast may | [DC-MC]. With NVO3, there are many possible ways that multicast may | |||
| be handled in such networks. We discuss some of the attributes of | be handled in such networks. We discuss some of the attributes of | |||
| the following four methods: 1. No multicast support. | the following four methods: | |||
| 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 mechanisms are briefly mentioned in the NVO3 Framework [FW] | These mechanisms are briefly mentioned in the NVO3 Framework [FW] | |||
| and NVO3 architecture [NVO3-ARCH] document. This document attempts | and NVO3 architecture [NVO3-ARCH] document. This document attempts | |||
| to provide more details about the basic mechanisms underlying each | to provide more details about the basic mechanisms underlying each | |||
| skipping to change at page 6, line 49 ¶ | skipping to change at page 6, line 49 ¶ | |||
| In the absence of IGMP/MLD snooping, the traffic would be delivered | In the absence of IGMP/MLD snooping, the traffic would be delivered | |||
| to all hosts that are part of the VNI. | to all hosts that are part of the VNI. | |||
| This method requires multiple copies of the same packet to all NVEs | This method requires multiple copies of the same packet to all NVEs | |||
| that participate in the VN. If, for example, a tenant subnet is | that participate in the VN. If, for example, a tenant subnet is | |||
| spread across 50 NVEs, the packet would have to be replicated 50 | spread across 50 NVEs, the packet would have to be replicated 50 | |||
| times at the source NVE. This also creates an issue with the | times at the source NVE. This also creates an issue with the | |||
| forwarding performance of the NVE. | forwarding performance of the NVE. | |||
| Note that this method is similar to what was used in VPLS [RFC4762] | Note that this method is similar to what was used in VPLS [VPLS] | |||
| prior to support of MPLS multicast [MPLS-MC]. While there are some | prior to support of MPLS multicast [MPLS-MC]. While there are some | |||
| similarities between MPLS VPN and the NVO3 overlay, there are some | similarities between MPLS VPN and the NVO3 overlay, there are some | |||
| key differences: | key differences: | |||
| - The CE-to-PE attachment in VPNs is somewhat static, whereas in a | - The CE-to-PE attachment in VPNs is somewhat static, whereas in a | |||
| DC that allows VMs to migrate anywhere, the TS attachment to NVE | DC that allows VMs to migrate anywhere, the TS attachment to NVE | |||
| is much more dynamic. | is much more dynamic. | |||
| - The number of PEs to which a single VPN customer is attached in | - The number of PEs to which a single VPN customer is attached in | |||
| an MPLS VPN environment is normally far less than the number of | an MPLS VPN environment is normally far less than the number of | |||
| skipping to change at page 13, line 22 ¶ | skipping to change at page 13, line 19 ¶ | |||
| (NVO3)", work in progress, February 2014. | (NVO3)", work in progress, February 2014. | |||
| [RFC3376] B. Cain, et al, "Internet Group Management Protocol, | [RFC3376] B. Cain, et al, "Internet Group Management Protocol, | |||
| Version 3", October 2002. | Version 3", October 2002. | |||
| [RFC6513] Rosen, E. et al., "Multicast in MPLS/BGP IP VPNs", | [RFC6513] Rosen, E. et al., "Multicast in MPLS/BGP IP VPNs", | |||
| February 2012. | February 2012. | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [RFC7348] Mahalingam, M. et al., "Virtual eXtensible Local Area | [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. | |||
| [NVGRE] Sridharan, M. et al., "NVGRE: Network virtualization using | [NVGRE] Sridharan, M. et al., "NVGRE: Network virtualization using | |||
| Generic Routing Encapsulation", work in progress. | Generic Routing Encapsulation", work in progress. | |||
| [STT] Davie, B. and Gross J., "A stateless transport tunneling | [STT] Davie, B. and Gross J., "A stateless transport tunneling | |||
| protocol for network virtualization", work in progress. | protocol for network virtualization," work in progress. | |||
| [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", work in progress. | overview," work in progress. | |||
| [ISIS-Multicast] | [ISIS-Multicast] | |||
| L. Yong, et al, "ISIS Protocol Extension For Building | ||||
| Distribution Trees", work in progress. Oct 2013. | ||||
| [RFC4762] Lasserre, M., and Kompella, V. (Eds), "Virtual Private LAN | L. Yong, et al, "ISIS Protocol Extension For Building | |||
| Service (VPLS) using Label Distribution Protocol (LDP) | Distribution Trees", work in progress. Oct 2013. | |||
| signaling", January 2007. | ||||
| [VPLS] Lasserre, M., and Kompella, V. (Eds), "Virtual Private LAN | ||||
| Service (VPLS) using Label Distribution Protocol (LDP) | ||||
| signaling," RFC 4762, January 2007. | ||||
| [MPLS-MC] Aggarwal, R. et al., "Multicast in VPLS," work in | [MPLS-MC] Aggarwal, R. et al., "Multicast in VPLS," work in | |||
| progress. | progress. | |||
| [LANE] "LAN emulation over ATM," The ATM Forum, af-lane-0021.000, | [LANE] "LAN emulation over ATM," The ATM Forum, af-lane-0021.000, | |||
| January 1995. | January 1995. | |||
| [EDGE-REP] | [EDGE-REP] | |||
| Marques P. et al., "Edge multicast replication for BGP IP | Marques P. et al., "Edge multicast replication for BGP IP | |||
| VPNs," work in progress, June 2012. | VPNs," work in progress, June 2012. | |||
| [RFC3569] S. Bhattacharyya, Ed., "An Overview of Source-Specific | [RFC 3569] | |||
| Multicast (SSM)", July 2003. | ||||
| S. Bhattacharyya, Ed., "An Overview of Source-Specific | ||||
| Multicast (SSM)", July 2003. | ||||
| [LISP-Signal-Free] | [LISP-Signal-Free] | |||
| V. Moreno & D. Farinacci, "Signal-Free LISP Multicast", | ||||
| work in progress. Dec 2014. | V. Moreno & D. Farinacci, "Signal-Free LISP Multicast", | |||
| work in progress. Dec 2014. | ||||
| 10. Acknowledgments | 10. Acknowledgments | |||
| Thanks are due to Dino Farinacci and Erik Nordmark for their | Thanks are due to Dino Farinacci and Erik Nordmark for their | |||
| comments and suggestions on this work. | 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 | |||
| Anoop Ghanwani | Anoop Ghanwani | |||
| Dell | Dell | |||
| Email: anoop@alumni.duke.edu | Email: anoop@alumni.duke.edu | |||
| Linda Dunbar | Linda Dunbar | |||
| Huawei Technologies | Huawei Technologies | |||
| 5340 Legacy Drive, Suite 1750 | 5340 Legacy Drive, Suite 1750 | |||
| Plano, TX 75024, USA | Plano, TX 75024, USA | |||
| Phone: (469) 277 5840 | Phone: (469) 277 5840 | |||
| Email: ldunbar@huawei.com | Email: ldunbar@huawei.com | |||
| Mike McBride | Mike McBride | |||
| Ericsson | Huawei Technologies | |||
| mike.mcbride@ericsson.com | mmcbride7@gmail.com | |||
| Vinay Bannai | Vinay Bannai | |||
| Email: vbannai@gmail.com | Email: vbannai@gmail.com | |||
| Ram Krishnan | Ram Krishnan | |||
| Dell | Dell | |||
| Email: Ramki_Krishnan@dell.com | Email: Ramki_Krishnan@dell.com | |||
| End of changes. 25 change blocks. | ||||
| 45 lines changed or deleted | 49 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/ | ||||