draft-ietf-lisp-multicast-13.txt   draft-ietf-lisp-multicast-14.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: August 10, 2012 S. Venaas Expires: August 11, 2012 S. Venaas
cisco Systems cisco Systems
February 7, 2012 February 8, 2012
LISP for Multicast Environments LISP for Multicast Environments
draft-ietf-lisp-multicast-13 draft-ietf-lisp-multicast-14
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 August 10, 2012. This Internet-Draft will expire on August 11, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 2, line 40 skipping to change at page 2, line 40
Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 29
11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 30 11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 30
12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 31 12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 31
13. Security Considerations . . . . . . . . . . . . . . . . . . . 32 13. Security Considerations . . . . . . . . . . . . . . . . . . . 32
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33
15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 15. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35 16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35
16.1. Normative References . . . . . . . . . . . . . . . . . . . 35 16.1. Normative References . . . . . . . . . . . . . . . . . . . 35
16.2. Informative References . . . . . . . . . . . . . . . . . . 36 16.2. Informative References . . . . . . . . . . . . . . . . . . 36
Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 37 Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 37
A.1. Changes to draft-ietf-lisp-multicast-13.txt . . . . . . . 37 A.1. Changes to draft-ietf-lisp-multicast-14.txt . . . . . . . 37
A.2. Changes to draft-ietf-lisp-multicast-12.txt . . . . . . . 37 A.2. Changes to draft-ietf-lisp-multicast-13.txt . . . . . . . 37
A.3. Changes to draft-ietf-lisp-multicast-11.txt . . . . . . . 37 A.3. Changes to draft-ietf-lisp-multicast-12.txt . . . . . . . 37
A.4. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 37 A.4. Changes to draft-ietf-lisp-multicast-11.txt . . . . . . . 37
A.5. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 37 A.5. Changes to draft-ietf-lisp-multicast-10.txt . . . . . . . 37
A.6. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 37 A.6. Changes to draft-ietf-lisp-multicast-09.txt . . . . . . . 37
A.7. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 37 A.7. Changes to draft-ietf-lisp-multicast-08.txt . . . . . . . 37
A.8. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 38 A.8. Changes to draft-ietf-lisp-multicast-07.txt . . . . . . . 38
A.9. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 38 A.9. Changes to draft-ietf-lisp-multicast-06.txt . . . . . . . 38
A.10. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 38 A.10. Changes to draft-ietf-lisp-multicast-05.txt . . . . . . . 38
A.11. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 38 A.11. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 38
A.12. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 39 A.12. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 38
A.13. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 39 A.13. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 39
A.14. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 39 A.14. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 39
A.15. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 40 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
skipping to change at page 7, line 5 skipping to change at page 6, line 43
Engineering based Ingress Tunnel Router) and TE-ETR (Traffic Engineering based Ingress Tunnel Router) and TE-ETR (Traffic
Engineering based Egress Tunnel Router) descriptions in [LISP]. Engineering based Egress Tunnel Router) descriptions in [LISP].
Futher work is also needed to determine the detailed behavior for Futher work is also needed to determine the detailed behavior for
multicast proxy ITRs (mPITRs) (Section 9.1.3), mtrace (Section 12), multicast proxy ITRs (mPITRs) (Section 9.1.3), mtrace (Section 12),
and locator reachability (Section 6). Finally, further deployment and locator reachability (Section 6). Finally, further deployment
and experimentation would be useful to understand the real-life and experimentation would be useful to understand the real-life
performance of the LISP-Multicast solution. For instance, the design performance of the LISP-Multicast solution. For instance, the design
optimizes for minimal state and control traffic in the core, but can optimizes for minimal state and control traffic in the core, but can
in some cases cause extra multicast traffic to be sent Section 8.1.2. in some cases cause extra multicast traffic to be sent Section 8.1.2.
Issues and concerns about the deployment of LISP for Internet traffic
are discussed in [LISP]. Section 12 provides additional issues and
concerns raised by this document.
3. Definition of Terms 3. Definition of Terms
The terminology in this section is consistent with the definitions in The terminology in this section is consistent with the definitions in
[LISP] but is extended specifically to deal with the application of [LISP] but is extended specifically to deal with the application of
the terminology to multicast routing. the terminology to multicast routing.
LISP-Multicast: a reference to the design in this specification. LISP-Multicast: a reference to the design in this specification.
That is, when any site that is participating in multicast That is, when any site that is participating in multicast
communication has been upgraded to be a LISP site, the operation communication has been upgraded to be a LISP site, the operation
of control-plane and data-plane protocols is considered part of of control-plane and data-plane protocols is considered part of
skipping to change at page 37, 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-13.txt A.1. Changes to draft-ietf-lisp-multicast-14.txt
o Posted February 2012.
o Resolve Adrian Farrel's final DISCUSS comment.
A.2. Changes to draft-ietf-lisp-multicast-13.txt
o Posted February 2012. o Posted February 2012.
o Resolution to Stewart Bryant's and Adrian Farrel's comments. o Resolution to Stewart Bryant's and Adrian Farrel's comments.
A.2. Changes to draft-ietf-lisp-multicast-12.txt A.3. Changes to draft-ietf-lisp-multicast-12.txt
o Posted January 2012. o Posted January 2012.
o Added more security disclaimers to the Security Considerations o Added more security disclaimers to the Security Considerations
section. section.
A.3. Changes to draft-ietf-lisp-multicast-11.txt A.4. 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.4. Changes to draft-ietf-lisp-multicast-10.txt A.5. 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.5. Changes to draft-ietf-lisp-multicast-09.txt A.6. 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.6. Changes to draft-ietf-lisp-multicast-08.txt A.7. 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.7. Changes to draft-ietf-lisp-multicast-07.txt A.8. Changes to draft-ietf-lisp-multicast-07.txt
o Posted July 2011. Fixing IDnits errors. o Posted July 2011. Fixing IDnits errors.
A.8. Changes to draft-ietf-lisp-multicast-06.txt A.9. 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.9. Changes to draft-ietf-lisp-multicast-05.txt A.10. 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.10. Changes to draft-ietf-lisp-multicast-04.txt A.11. 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.11. Changes to draft-ietf-lisp-multicast-03.txt A.12. 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 39, line 5 skipping to change at page 39, line 8
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.12. Changes to draft-ietf-lisp-multicast-02.txt A.13. 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.13. Changes to draft-ietf-lisp-multicast-01.txt A.14. 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.14. Changes to draft-ietf-lisp-multicast-00.txt A.15. 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. 
32 lines changed or deleted 43 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/