draft-ietf-lisp-multicast-09.txt   draft-ietf-lisp-multicast-10.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft D. Meyer Internet-Draft D. Meyer
Intended status: Experimental J. Zwiebel Intended status: Experimental J. Zwiebel
Expires: April 7, 2012 S. Venaas Expires: April 19, 2012 S. Venaas
cisco Systems cisco Systems
October 5, 2011 October 17, 2011
LISP for Multicast Environments LISP for Multicast Environments
draft-ietf-lisp-multicast-09 draft-ietf-lisp-multicast-10
Abstract Abstract
This draft describes how inter-domain multicast routing will function This draft describes how inter-domain multicast routing will function
in an environment where Locator/ID Separation is deployed using the in an environment where Locator/ID Separation is deployed using the
LISP architecture. LISP architecture.
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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 April 7, 2012. This Internet-Draft will expire on April 19, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 2, line 40 skipping to change at page 2, line 40
Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 28
11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 29 11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 29
12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 30 12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 30
13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 13. Security Considerations . . . . . . . . . . . . . . . . . . . 31
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34
16.1. Normative References . . . . . . . . . . . . . . . . . . . 34 16.1. Normative References . . . . . . . . . . . . . . . . . . . 34
16.2. Informative References . . . . . . . . . . . . . . . . . . 35 16.2. Informative References . . . . . . . . . . . . . . . . . . 35
Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 36 Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 36
A.1. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 36 A.1. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 36
A.2. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 36 A.2. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 36
A.3. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 36 A.3. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 36
A.4. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 36 A.4. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 36
A.5. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 36 A.5. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 36
A.6. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 36 A.6. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 36
A.7. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 36 A.7. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 36
A.8. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 37 A.8. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 37
A.9. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 37 A.9. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 37
A.10. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 37 A.10. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 37
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 38 A.11. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39
1. Requirements Notation 1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Introduction 2. Introduction
The Locator/ID Separation Architecture [LISP] provides a mechanism to The Locator/ID Separation Architecture [LISP] provides a mechanism to
skipping to change at page 5, line 17 skipping to change at page 5, line 17
enabled sites. enabled sites.
D. How multicast packets from a source host in a non-LISP site D. How multicast packets from a source host in a non-LISP site
are sent to receivers in both LISP-enabled sites and non-LISP are sent to receivers in both LISP-enabled sites and non-LISP
sites. sites.
This specification focuses on what changes are needed to the This specification focuses on what changes are needed to the
multicast routing protocols to support LISP-Multicast as well as multicast routing protocols to support LISP-Multicast as well as
other protocols used for inter-domain multicast, such as Multi- other protocols used for inter-domain multicast, such as Multi-
protocol BGP (MBGP) [RFC4760]. The approach proposed in this protocol BGP (MBGP) [RFC4760]. The approach proposed in this
specification requires no packet format changes to the protocol and specification requires no packet format changes to the protocols and
no operational procedural changes to the multicast infrastructure no operational procedural changes to the multicast infrastructure
inside of a site when all sources and receivers reside in that site, inside of a site when all sources and receivers reside in that site,
even when the site is LISP enabled. That is, internal operation of even when the site is LISP enabled. That is, internal operation of
multicast is unchanged regardless of whether or not the site is LISP multicast is unchanged regardless of whether or not the site is LISP
enabled or whether or not receivers exist in other sites which are enabled or whether or not receivers exist in other sites which are
LISP-enabled. LISP-enabled.
Therefore, we see changes only to PIM-ASM [RFC4601], MSDP [RFC3618], Therefore, we see changes only to PIM-ASM [RFC4601], MSDP [RFC3618],
and PIM-SSM [RFC4607]. Bidir-PIM [RFC5015], which typically does not and PIM-SSM [RFC4607]. Bidir-PIM [RFC5015], which typically does not
run in an inter-domain environment is not addressed in depth in this run in an inter-domain environment is not addressed in depth in this
skipping to change at page 9, line 5 skipping to change at page 8, line 46
Join/Prune message (encapsulated in a LISP Encapsulated Control Join/Prune message (encapsulated in a LISP Encapsulated Control
Message with destination UDP port 4342) which is sent by ETRs at Message with destination UDP port 4342) which is sent by ETRs at
multicast receiver sites to an ITR at a multicast source site. multicast receiver sites to an ITR at a multicast source site.
This message is sent periodically as long as there are interfaces This message is sent periodically as long as there are interfaces
in the OIF-list for the (S-EID,G) entry the ETR is joining for. in the OIF-list for the (S-EID,G) entry the ETR is joining for.
OIF-list: this is notation to describe the outgoing interface list OIF-list: this is notation to describe the outgoing interface list
a multicast router stores per multicast routing table entry so it a multicast router stores per multicast routing table entry so it
knows what interfaces to replicate multicast packets on. knows what interfaces to replicate multicast packets on.
RPF: Reverse Path Forwarding is a procedure used by multicast
routers. A router will accept a multicast packet for forwarding
if the packet was received on the path that the router would use
to forward unicast packets to the multicast packet's source.
4. Basic Overview 4. Basic Overview
LISP, when used for unicast routing, increases the site's ability to LISP, when used for unicast routing, increases the site's ability to
control ingress traffic flows. Egress traffic flows are controlled control ingress traffic flows. Egress traffic flows are controlled
by the IGP in the source site. For multicast, the IGP coupled with by the IGP in the source site. For multicast, the IGP coupled with
PIM can decide which path multicast packets ingress. By using the PIM can decide which path multicast packets ingress. By using the
traffic engineering features of LISP, a multicast source site can traffic engineering features of LISP, a multicast source site can
control the egress of its multicast traffic. By controlling the control the egress of its multicast traffic. By controlling the
priorities of locators from a mapping database entry, a source priorities of locators from a mapping database entry, a source
multicast site can control which way multicast receiver sites join to multicast site can control which way multicast receiver sites join to
skipping to change at page 28, line 13 skipping to change at page 28, line 13
avoid head-end data replication at ITRs. avoid head-end data replication at ITRs.
10. Considerations when RP Addresses are Embedded in Group Addresses 10. Considerations when RP Addresses are Embedded in Group Addresses
When ASM and PIM-Bidir is used in an IPv6 inter-domain environment, a When ASM and PIM-Bidir is used in an IPv6 inter-domain environment, a
technique exists to embed the unicast address of an RP in a IPv6 technique exists to embed the unicast address of an RP in a IPv6
group address [RFC3956]. When routers in end sites process a PIM group address [RFC3956]. When routers in end sites process a PIM
Join/Prune message which contain an embedded-RP group address, they Join/Prune message which contain an embedded-RP group address, they
extract the RP address from the group address and treat it from the extract the RP address from the group address and treat it from the
EID namespace. However, core routers do not have state for the EID EID namespace. However, core routers do not have state for the EID
namespace, need to extract an RP address from the RLOC namespace. namespace, and need to extract an RP address from the RLOC namespace.
Therefore, it is the responsibility of ETRs in multicast receiver Therefore, it is the responsibility of ETRs in multicast receiver
sites to map the group address into a group address where the sites to map the group address into a group address where the
embedded-RP address is from the RLOC namespace. The mapped RP- embedded-RP address is from the RLOC namespace. The mapped RP-
address is obtained from a EID-to-RLOC mapping database lookup. The address is obtained from a EID-to-RLOC mapping database lookup. The
ETR will also send a unicast (*,G) Join/Prune message to the ITR so ETR will also send a unicast (*,G) Join/Prune message to the ITR so
the branch of the distribution tree from the source site resident RP the branch of the distribution tree from the source site resident RP
to the ITR is created. to the ITR is created.
This technique is no different than the techniques described in this This technique is no different than the techniques described in this
skipping to change at page 36, line 7 skipping to change at page 36, line 7
[MLISP] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, [MLISP] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas,
"LISP for Multicast Environments", "LISP for Multicast Environments",
draft-farinacci-lisp-multicast-01.txt (work in progress). draft-farinacci-lisp-multicast-01.txt (work in progress).
[MTRACE] Asaeda, H., Jinmei, T., Fenner, W., and S. Casner, "Mtrace [MTRACE] Asaeda, H., Jinmei, T., Fenner, W., and S. Casner, "Mtrace
Version 2: Traceroute Facility for IP Multicast", Version 2: Traceroute Facility for IP Multicast",
draft-ietf-mboned-mtrace-v2-08.txt (work in progress). draft-ietf-mboned-mtrace-v2-08.txt (work in progress).
Appendix A. Document Change Log Appendix A. Document Change Log
A.1. Changes to draft-ietf-lisp-multicast-09.txt A.1. Changes to draft-ietf-lisp-multicast-10.txt
o Posted second half of October 2011. Changes to reflect IESG
review comments from Stephen Farrell.
A.2. Changes to draft-ietf-lisp-multicast-09.txt
o Posted October 2011. Changes to reflect IESG review comments from o Posted October 2011. Changes to reflect IESG review comments from
Ralph Droms and Kathleen Moriarty. Ralph Droms and Kathleen Moriarty.
A.2. Changes to draft-ietf-lisp-multicast-08.txt A.3. Changes to draft-ietf-lisp-multicast-08.txt
o Posted September 2011. Minor editorial changes from Jari's o Posted September 2011. Minor editorial changes from Jari's
commentary. commentary.
A.3. Changes to draft-ietf-lisp-multicast-07.txt A.4. Changes to draft-ietf-lisp-multicast-07.txt
o Posted July 2011. Fixing IDnits errors. o Posted July 2011. Fixing IDnits errors.
A.4. Changes to draft-ietf-lisp-multicast-06.txt A.5. Changes to draft-ietf-lisp-multicast-06.txt
o Posted June 2011 to complete working group last call. o Posted June 2011 to complete working group last call.
o Added paragraph to section 8.1.2 based on Jesus comment about o Added paragraph to section 8.1.2 based on Jesus comment about
making it more clear what happens when two (S-EID,G) trees use the making it more clear what happens when two (S-EID,G) trees use the
same (RLOC,G) tree. same (RLOC,G) tree.
o Make more references to [INTWORK] when mentioning uPITRs and o Make more references to [INTWORK] when mentioning uPITRs and
uPETRs. uPETRs.
o Made many changes based on editorial and wordsmithing comments o Made many changes based on editorial and wordsmithing comments
from Alia. from Alia.
A.5. Changes to draft-ietf-lisp-multicast-05.txt A.6. Changes to draft-ietf-lisp-multicast-05.txt
o Posted April 2011 to reset expiration timer. o Posted April 2011 to reset expiration timer.
o Updated references. o Updated references.
A.6. Changes to draft-ietf-lisp-multicast-04.txt A.7. Changes to draft-ietf-lisp-multicast-04.txt
o Posted October 2010 to reset expiration timer. o Posted October 2010 to reset expiration timer.
o Updated references. o Updated references.
A.7. Changes to draft-ietf-lisp-multicast-03.txt A.8. Changes to draft-ietf-lisp-multicast-03.txt
o Posted April 2010. o Posted April 2010.
o Added section 8.1.2 to address Joel Halpern's comment about o Added section 8.1.2 to address Joel Halpern's comment about
receiver sites joining the same source site via 2 different RLOCs, receiver sites joining the same source site via 2 different RLOCs,
each being a separate ITR. each being a separate ITR.
o Change all occurences of "mPTR" to "mPETR" to become more o Change all occurences of "mPTR" to "mPETR" to become more
consistent with uPITRs and uPETRs described in [INTWORK]. That consistent with uPITRs and uPETRs described in [INTWORK]. That
is, an mPETR is a LISP multicast router that decapsulates is, an mPETR is a LISP multicast router that decapsulates
skipping to change at page 37, line 20 skipping to change at page 37, line 27
source sites. source sites.
o Add clarifications in section 9 about how homogeneous multicast o Add clarifications in section 9 about how homogeneous multicast
encapsulation should occur. As well as describing in this encapsulation should occur. As well as describing in this
section, how to deal with mixed-locator sets to avoid section, how to deal with mixed-locator sets to avoid
heterogeneous encapsulation. heterogeneous encapsulation.
o Introduce concept of mPITRs to help reduce (S-EID,G) to the edges o Introduce concept of mPITRs to help reduce (S-EID,G) to the edges
of LISP global multicast network. of LISP global multicast network.
A.8. Changes to draft-ietf-lisp-multicast-02.txt A.9. Changes to draft-ietf-lisp-multicast-02.txt
o Posted September 2009. o Posted September 2009.
o Added Document Change Log appendix. o Added Document Change Log appendix.
o Specify that the LISP Encapsulated Control Message be used for o Specify that the LISP Encapsulated Control Message be used for
unicasting PIM Join/Prune messages from ETRs to ITRs. unicasting PIM Join/Prune messages from ETRs to ITRs.
A.9. Changes to draft-ietf-lisp-multicast-01.txt A.10. Changes to draft-ietf-lisp-multicast-01.txt
o Posted November 2008. o Posted November 2008.
o Specified that PIM Join/Prune unicast messages that get sent from o Specified that PIM Join/Prune unicast messages that get sent from
ETRs to ITRs of a source multicast site get LISP encapsulated in ETRs to ITRs of a source multicast site get LISP encapsulated in
destination UDP port 4342. destination UDP port 4342.
o Add multiple RLOCs per ITR per Yiqun's comments. o Add multiple RLOCs per ITR per Yiqun's comments.
o Indicate how static RPs can be used when LISP is run using Bidir- o Indicate how static RPs can be used when LISP is run using Bidir-
PIM in the core. PIM in the core.
o Editorial changes per Liming comments. o Editorial changes per Liming comments.
o Add Mttrace Considersations section. o Add Mttrace Considersations section.
A.10. Changes to draft-ietf-lisp-multicast-00.txt A.11. Changes to draft-ietf-lisp-multicast-00.txt
o Posted April 2008. o Posted April 2008.
o Renamed from draft-farinacci-lisp-multicast-01.txt. o Renamed from draft-farinacci-lisp-multicast-01.txt.
Authors' Addresses Authors' Addresses
Dino Farinacci Dino Farinacci
cisco Systems cisco Systems
Tasman Drive Tasman Drive
 End of changes. 18 change blocks. 
27 lines changed or deleted 38 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/