draft-ietf-lisp-multicast-11.txt   draft-ietf-lisp-multicast-12.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: May 7, 2012 S. Venaas Expires: July 5, 2012 S. Venaas
cisco Systems cisco Systems
November 4, 2011 January 2, 2012
LISP for Multicast Environments LISP for Multicast Environments
draft-ietf-lisp-multicast-11 draft-ietf-lisp-multicast-12
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 May 7, 2012. This Internet-Draft will expire on July 5, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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 respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 1. Requirements Notation . . . . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 6 3. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 7
4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Basic Overview . . . . . . . . . . . . . . . . . . . . . . . . 10
5. Source Addresses versus Group Addresses . . . . . . . . . . . 12 5. Source Addresses versus Group Addresses . . . . . . . . . . . 13
6. Locator Reachability Implications on LISP-Multicast . . . . . 13 6. Locator Reachability Implications on LISP-Multicast . . . . . 14
7. Multicast Protocol Changes . . . . . . . . . . . . . . . . . . 14 7. Multicast Protocol Changes . . . . . . . . . . . . . . . . . . 15
8. LISP-Multicast Data-Plane Architecture . . . . . . . . . . . . 17 8. LISP-Multicast Data-Plane Architecture . . . . . . . . . . . . 18
8.1. ITR Forwarding Procedure . . . . . . . . . . . . . . . . . 17 8.1. ITR Forwarding Procedure . . . . . . . . . . . . . . . . . 18
8.1.1. Multiple RLOCs for an ITR . . . . . . . . . . . . . . 17 8.1.1. Multiple RLOCs for an ITR . . . . . . . . . . . . . . 18
8.1.2. Multiple ITRs for a LISP Source Site . . . . . . . . . 18 8.1.2. Multiple ITRs for a LISP Source Site . . . . . . . . . 19
8.2. ETR Forwarding Procedure . . . . . . . . . . . . . . . . . 18 8.2. ETR Forwarding Procedure . . . . . . . . . . . . . . . . . 19
8.3. Replication Locations . . . . . . . . . . . . . . . . . . 19 8.3. Replication Locations . . . . . . . . . . . . . . . . . . 20
9. LISP-Multicast Interworking . . . . . . . . . . . . . . . . . 20 9. LISP-Multicast Interworking . . . . . . . . . . . . . . . . . 21
9.1. LISP and non-LISP Mixed Sites . . . . . . . . . . . . . . 20 9.1. LISP and non-LISP Mixed Sites . . . . . . . . . . . . . . 21
9.1.1. LISP Source Site to non-LISP Receiver Sites . . . . . 21 9.1.1. LISP Source Site to non-LISP Receiver Sites . . . . . 22
9.1.2. Non-LISP Source Site to non-LISP Receiver Sites . . . 22 9.1.2. Non-LISP Source Site to non-LISP Receiver Sites . . . 23
9.1.3. Non-LISP Source Site to Any Receiver Site . . . . . . 23 9.1.3. Non-LISP Source Site to Any Receiver Site . . . . . . 24
9.1.4. Unicast LISP Source Site to Any Receiver Sites . . . . 24 9.1.4. Unicast LISP Source Site to Any Receiver Sites . . . . 25
9.1.5. LISP Source Site to Any Receiver Sites . . . . . . . . 24 9.1.5. LISP Source Site to Any Receiver Sites . . . . . . . . 25
9.2. LISP Sites with Mixed Address Families . . . . . . . . . . 25 9.2. LISP Sites with Mixed Address Families . . . . . . . . . . 26
9.3. Making a Multicast Interworking Decision . . . . . . . . . 27 9.3. Making a Multicast Interworking Decision . . . . . . . . . 28
10. Considerations when RP Addresses are Embedded in Group 10. Considerations when RP Addresses are Embedded in Group
Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 29 11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 30
12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 30 12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 31
13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 13. Security Considerations . . . . . . . . . . . . . . . . . . . 32
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
16.1. Normative References . . . . . . . . . . . . . . . . . . . 34 16.1. Normative References . . . . . . . . . . . . . . . . . . . 35
16.2. Informative References . . . . . . . . . . . . . . . . . . 35 16.2. Informative References . . . . . . . . . . . . . . . . . . 36
Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 36 Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 37
A.1. Changes to draft-ietf-lisp-multicast-11.txt . . . . . . . 36 A.1. Changes to draft-ietf-lisp-multicast-12.txt . . . . . . . 37
A.2. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 36 A.2. Changes to draft-ietf-lisp-multicast-11.txt . . . . . . . 37
A.3. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 36 A.3. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 37
A.4. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 36 A.4. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 37
A.5. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 36 A.5. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 37
A.6. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 36 A.6. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 37
A.7. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 37 A.7. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 37
A.8. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 37 A.8. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 38
A.9. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 37 A.9. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 38
A.10. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 37 A.10. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 38
A.11. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 37 A.11. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 38
A.12. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 38 A.12. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 A.13. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40
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 32, line 5 skipping to change at page 32, line 18
the base LISP specification [LISP] and for multicast in general, the base LISP specification [LISP] and for multicast in general,
including PIM-ASM [RFC4601]. including PIM-ASM [RFC4601].
There may be a security concern with respect to unicast PIM messages. There may be a security concern with respect to unicast PIM messages.
When multiple receiver sites are joining a (S-EID1,G) distribution When multiple receiver sites are joining a (S-EID1,G) distribution
tree that maps to a (RLOC1,G) core distribution tree, and a malicious tree that maps to a (RLOC1,G) core distribution tree, and a malicious
receiver site joins a (S-EID2,G) distribution tree that also maps to receiver site joins a (S-EID2,G) distribution tree that also maps to
the (RLOC1,G) core distribution tree, the legitimate sites will the (RLOC1,G) core distribution tree, the legitimate sites will
receive data from S-EID2 when they did not ask for it. receive data from S-EID2 when they did not ask for it.
Other than as noted above there are currently no known security
differences between multicast with LISP and multicast without LISP.
However this has not been a topic that has been investigated deeply
so far therefore additional issues might arise in future.
14. Acknowledgments 14. Acknowledgments
The authors would like to gratefully acknowledge the people who have The authors would like to gratefully acknowledge the people who have
contributed discussion, ideas, and commentary to the making of this contributed discussion, ideas, and commentary to the making of this
proposal and specification. People who provided expert review were proposal and specification. People who provided expert review were
Scott Brim, Greg Shepherd, and Dave Oran. Other commentary from Scott Brim, Greg Shepherd, and Dave Oran. Other commentary from
discussions at Summer 2008 Dublin IETF were Toerless Eckert and discussions at Summer 2008 Dublin IETF were Toerless Eckert and
Ijsbrand Wijnands. Ijsbrand Wijnands.
The authors would also like to thank the MBONED working group for The authors would also like to thank the MBONED working group for
skipping to change at page 36, line 7 skipping to change at page 37, 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-11.txt A.1. Changes to draft-ietf-lisp-multicast-12.txt
o Posted January 2012.
o Added more security disclaimers to the Security Considerations
section.
A.2. Changes to draft-ietf-lisp-multicast-11.txt
o Posted November 2011. o Posted November 2011.
o Added Stig text to Security Considerations section to reflect o Added Stig text to Security Considerations section to reflect
comments from IESG review comment from Stephen Farrell. comments from IESG review comment from Stephen Farrell.
o Changed how an unicast PIM join gets sent. Do not use an ECM or o Changed how an unicast PIM join gets sent. Do not use an ECM or
else an instance-ID cannot be included in the join. So go back to else an instance-ID cannot be included in the join. So go back to
what we had where the unicast PIM join is encapsulated in a 4341 what we had where the unicast PIM join is encapsulated in a 4341
UDP packet. UDP packet.
A.2. Changes to draft-ietf-lisp-multicast-10.txt A.3. Changes to draft-ietf-lisp-multicast-10.txt
o Posted second half of October 2011. Changes to reflect IESG o Posted second half of October 2011. Changes to reflect IESG
review comments from Stephen Farrell. review comments from Stephen Farrell.
A.3. Changes to draft-ietf-lisp-multicast-09.txt A.4. 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.4. Changes to draft-ietf-lisp-multicast-08.txt A.5. 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.5. Changes to draft-ietf-lisp-multicast-07.txt A.6. Changes to draft-ietf-lisp-multicast-07.txt
o Posted July 2011. Fixing IDnits errors. o Posted July 2011. Fixing IDnits errors.
A.6. Changes to draft-ietf-lisp-multicast-06.txt A.7. 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.7. Changes to draft-ietf-lisp-multicast-05.txt A.8. 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.8. Changes to draft-ietf-lisp-multicast-04.txt A.9. 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.9. Changes to draft-ietf-lisp-multicast-03.txt A.10. 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 39 skipping to change at page 38, line 45
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.10. Changes to draft-ietf-lisp-multicast-02.txt A.11. 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.11. Changes to draft-ietf-lisp-multicast-01.txt A.12. 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.12. Changes to draft-ietf-lisp-multicast-00.txt A.13. 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. 20 change blocks. 
62 lines changed or deleted 76 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/