--- 1/draft-ietf-lisp-multicast-01.txt 2009-09-30 04:12:12.000000000 +0200 +++ 2/draft-ietf-lisp-multicast-02.txt 2009-09-30 04:12:12.000000000 +0200 @@ -1,20 +1,20 @@ Network Working Group D. Farinacci Internet-Draft D. Meyer Intended status: Experimental J. Zwiebel -Expires: November 29, 2009 S. Venaas +Expires: April 2, 2010 S. Venaas cisco Systems - May 28, 2009 + September 29, 2009 LISP for Multicast Environments - draft-ietf-lisp-multicast-01.txt + draft-ietf-lisp-multicast-02.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -23,21 +23,21 @@ 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on November 29, 2009. + This Internet-Draft will expire on April 2, 2010. Copyright Notice Copyright (c) 2009 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 in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights @@ -74,21 +74,25 @@ 9.3. Making a Multicast Interworking Decision . . . . . . . . . 25 10. Considerations when RP Addresses are Embedded in Group Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 26 11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 27 12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 28 13. Security Considerations . . . . . . . . . . . . . . . . . . . 29 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31 15.1. Normative References . . . . . . . . . . . . . . . . . . . 31 15.2. Informative References . . . . . . . . . . . . . . . . . . 31 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33 + Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 33 + A.1. Changes to draft-ietf-lisp-multicsat-02.txt . . . . . . . 33 + A.2. Changes to draft-ietf-lisp-multicsat-01.txt . . . . . . . 33 + A.3. Changes to draft-ietf-lisp-multicsat-00.txt . . . . . . . 33 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34 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 The Locator/ID Separation Architecture [LISP] provides a mechanism to @@ -277,25 +281,25 @@ their (S-EID,G) PIM Join/Prune message to. mPTRs are used so LISP source multicast sites can send multicast packets using source addresses from the EID namespace. mPTRs act as Proxy ETRs for supporting multicast routing in a LISP infrastructure. 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 (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. + 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. 4. Basic Overview LISP, when used for unicast routing, increases the site's ability to control ingress traffic flows. Egress traffic flows are controlled by the IGP in the source site. For multicast, the IGP coupled with PIM can decide which path multicast packets ingress. By using the traffic engineering features of LISP, a multicast source site can control the egress of its multicast traffic. By controlling the priorities of locators from a mapping database entry, a source @@ -1146,41 +1150,75 @@ [ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP Alternative Topology (LISP-ALT)", draft-ietf-lisp-alt-01.txt (work in progress), May 2009. [INTWORK] Lewis, D., Meyer, D., and D. Farinacci, "Interworking LISP with IPv4 and IPv6", draft-ietf-lisp-interworking-00.txt (work in progress), May 2009. [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "Locator/ID Separation Protocol (LISP)", - draft-ietf-lisp-01.txt (work in progress), May 2009. + draft-ietf-lisp-05.txt (work in progress), September 2009. [MLISP] Farinacci, D., Meyer, D., Zwiebel, J., and S. Venaas, "LISP for Multicast Environments", draft-farinacci-lisp-multicast-01.txt (work in progress), November 2008. [MNAT] Wing, D. and T. Eckert, "Multicast Requirements for a Network Address (and port) Translator (NAT)", draft-ietf-behave-multicast-07.txt (work in progress), June 2007. [MTRACE] Asaeda, H., Jinmei, T., Fenner, W., and S. Casner, "Mtrace Version 2: Traceroute Facility for IP Multicast", draft-ietf-mboned-mtrace-v2-03.txt (work in progress), March 2009. [RPFV] Wijnands, IJ., Boers, A., and E. Rosen, "The RPF Vector TLV", draft-ietf-pim-rpf-vector-06.txt (work in progress), February 2008. +Appendix A. Document Change Log + +A.1. Changes to draft-ietf-lisp-multicsat-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.2. Changes to draft-ietf-lisp-multicsat-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.3. Changes to draft-ietf-lisp-multicsat-00.txt + + o Posted April 2008. + + o Renamed from draft-farinacci-lisp-multicast-01.txt. + Authors' Addresses Dino Farinacci cisco Systems Tasman Drive San Jose, CA USA Email: dino@cisco.com