--- 1/draft-ietf-lisp-multicast-10.txt 2011-11-14 19:14:05.490671304 +0100 +++ 2/draft-ietf-lisp-multicast-11.txt 2011-11-14 19:14:05.558671814 +0100 @@ -1,20 +1,20 @@ Network Working Group D. Farinacci Internet-Draft D. Meyer Intended status: Experimental J. Zwiebel -Expires: April 19, 2012 S. Venaas +Expires: May 7, 2012 S. Venaas cisco Systems - October 17, 2011 + November 4, 2011 LISP for Multicast Environments - draft-ietf-lisp-multicast-10 + draft-ietf-lisp-multicast-11 Abstract This draft describes how inter-domain multicast routing will function in an environment where Locator/ID Separation is deployed using the LISP architecture. Status of this Memo This Internet-Draft is submitted in full conformance with the @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 19, 2012. + This Internet-Draft will expire on May 7, 2012. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -75,31 +75,32 @@ Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 28 11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 29 12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 30 13. Security Considerations . . . . . . . . . . . . . . . . . . . 31 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 32 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 34 16.1. Normative References . . . . . . . . . . . . . . . . . . . 34 16.2. Informative References . . . . . . . . . . . . . . . . . . 35 Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 36 - A.1. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 36 - A.2. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 36 - A.3. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 36 - A.4. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 36 - A.5. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 36 - A.6. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 36 - A.7. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 36 - A.8. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 37 - A.9. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 37 - A.10. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 37 - A.11. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 38 + A.1. Changes to draft-ietf-lisp-multicast-11.txt . . . . . . . 36 + A.2. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 36 + A.3. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 36 + A.4. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 36 + A.5. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 36 + A.6. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 36 + A.7. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 37 + A.8. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 37 + A.9. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 37 + A.10. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 37 + A.11. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 37 + A.12. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 38 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 39 1. Requirements Notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Introduction @@ -306,25 +307,25 @@ ETRs for supporting multicast routing in a LISP infrastructure. It is likely an uPITR [INTWORK] and a mPETR will be co-located since the single device advertises a coarse EID-prefix in the underlying unicast routing system. Mixed Locator-Sets: this is a locator-set for a LISP database mapping entry where the RLOC addresses in the locator-set are in both IPv4 and IPv6 format. Unicast Encapsulated PIM Join/Prune Message: this is a standard PIM - Join/Prune message (encapsulated in a LISP Encapsulated Control - Message with destination UDP port 4342) which is sent by ETRs at - multicast receiver sites to an ITR at a multicast source site. - 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. + Join/Prune message (LISP encapsulated with destination UDP port + 4341) which is sent by ETRs at multicast receiver sites to an ITR + at a multicast source site. 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. OIF-list: this is notation to describe the outgoing interface list a multicast router stores per multicast routing table entry so it 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. @@ -1160,22 +1161,30 @@ Mtrace functionality MUST be consistent with unicast traceroute functionality where all hops from multicast receiver to multicast source are visible. The design for mtrace for use in LISP-Multicast environments is to be determined but should build upon the mtrace version 2 specified in [MTRACE]. 13. Security Considerations - This document introduces no additional security concerns beyond those - specified in the base LISP specification [LISP]. + The security concerns for LISP multicast are mainly the same as for + the base LISP specification [LISP] and for multicast in general, + including PIM-ASM [RFC4601]. + + There may be a security concern with respect to unicast PIM messages. + When multiple receiver sites are joining a (S-EID1,G) distribution + 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 + the (RLOC1,G) core distribution tree, the legitimate sites will + receive data from S-EID2 when they did not ask for it. 14. Acknowledgments The authors would like to gratefully acknowledge the people who have contributed discussion, ideas, and commentary to the making of this proposal and specification. People who provided expert review were Scott Brim, Greg Shepherd, and Dave Oran. Other commentary from discussions at Summer 2008 Dublin IETF were Toerless Eckert and Ijsbrand Wijnands. @@ -1200,21 +1209,21 @@ 16. References 16.1. Normative References [INTWORK] Lewis, D., Meyer, D., and D. Farinacci, "Interworking LISP with IPv4 and IPv6", draft-ietf-lisp-interworking-02.txt (work in progress). [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "Locator/ID Separation Protocol (LISP)", - draft-ietf-lisp-15.txt (work in progress). + draft-ietf-lisp-16.txt (work in progress). [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery Protocol (MSDP)", RFC 3618, October 2003. [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address", RFC 3956, November 2004. @@ -1242,79 +1251,91 @@ [RFC5135] Wing, D. and T. Eckert, "IP Multicast Requirements for a Network Address Translator (NAT) and a Network Address Port Translator (NAPT)", BCP 135, RFC 5135, February 2008. [RFC5496] Wijnands, IJ., Boers, A., and E. Rosen, "The Reverse Path Forwarding (RPF) Vector TLV", RFC 5496, March 2009. 16.2. Informative References [ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP Alternative - Topology (LISP-ALT)", draft-ietf-lisp-alt-08.txt (work in + Topology (LISP-ALT)", draft-ietf-lisp-alt-09.txt (work in progress). [MLISP] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "LISP for Multicast Environments", draft-farinacci-lisp-multicast-01.txt (work in progress). [MTRACE] Asaeda, H., Jinmei, T., Fenner, W., and S. Casner, "Mtrace Version 2: Traceroute Facility for IP Multicast", draft-ietf-mboned-mtrace-v2-08.txt (work in progress). Appendix A. Document Change Log -A.1. Changes to draft-ietf-lisp-multicast-10.txt +A.1. Changes to draft-ietf-lisp-multicast-11.txt + + o Posted November 2011. + + o Added Stig text to Security Considerations section to reflect + comments from IESG review comment from Stephen Farrell. + + 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 + what we had where the unicast PIM join is encapsulated in a 4341 + UDP packet. + +A.2. 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 +A.3. Changes to draft-ietf-lisp-multicast-09.txt o Posted October 2011. Changes to reflect IESG review comments from Ralph Droms and Kathleen Moriarty. -A.3. Changes to draft-ietf-lisp-multicast-08.txt +A.4. Changes to draft-ietf-lisp-multicast-08.txt o Posted September 2011. Minor editorial changes from Jari's commentary. -A.4. Changes to draft-ietf-lisp-multicast-07.txt +A.5. Changes to draft-ietf-lisp-multicast-07.txt o Posted July 2011. Fixing IDnits errors. -A.5. Changes to draft-ietf-lisp-multicast-06.txt +A.6. Changes to draft-ietf-lisp-multicast-06.txt o Posted June 2011 to complete working group last call. 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 same (RLOC,G) tree. o Make more references to [INTWORK] when mentioning uPITRs and uPETRs. o Made many changes based on editorial and wordsmithing comments from Alia. -A.6. Changes to draft-ietf-lisp-multicast-05.txt +A.7. Changes to draft-ietf-lisp-multicast-05.txt o Posted April 2011 to reset expiration timer. o Updated references. -A.7. Changes to draft-ietf-lisp-multicast-04.txt +A.8. Changes to draft-ietf-lisp-multicast-04.txt o Posted October 2010 to reset expiration timer. o Updated references. -A.8. Changes to draft-ietf-lisp-multicast-03.txt +A.9. Changes to draft-ietf-lisp-multicast-03.txt o Posted April 2010. o Added section 8.1.2 to address Joel Halpern's comment about receiver sites joining the same source site via 2 different RLOCs, each being a separate ITR. o Change all occurences of "mPTR" to "mPETR" to become more consistent with uPITRs and uPETRs described in [INTWORK]. That is, an mPETR is a LISP multicast router that decapsulates @@ -1322,47 +1343,47 @@ source sites. o Add clarifications in section 9 about how homogeneous multicast encapsulation should occur. As well as describing in this section, how to deal with mixed-locator sets to avoid heterogeneous encapsulation. o Introduce concept of mPITRs to help reduce (S-EID,G) to the edges of LISP global multicast network. -A.9. Changes to draft-ietf-lisp-multicast-02.txt +A.10. Changes to draft-ietf-lisp-multicast-02.txt o Posted September 2009. o Added Document Change Log appendix. o Specify that the LISP Encapsulated Control Message be used for unicasting PIM Join/Prune messages from ETRs to ITRs. -A.10. Changes to draft-ietf-lisp-multicast-01.txt +A.11. Changes to draft-ietf-lisp-multicast-01.txt o Posted November 2008. o Specified that PIM Join/Prune unicast messages that get sent from ETRs to ITRs of a source multicast site get LISP encapsulated in destination UDP port 4342. o Add multiple RLOCs per ITR per Yiqun's comments. o Indicate how static RPs can be used when LISP is run using Bidir- PIM in the core. o Editorial changes per Liming comments. o Add Mttrace Considersations section. -A.11. Changes to draft-ietf-lisp-multicast-00.txt +A.12. Changes to draft-ietf-lisp-multicast-00.txt o Posted April 2008. o Renamed from draft-farinacci-lisp-multicast-01.txt. Authors' Addresses Dino Farinacci cisco Systems Tasman Drive