draft-ietf-lisp-multicast-03.txt   draft-ietf-lisp-multicast-04.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: October 18, 2010 S. Venaas Expires: April 14, 2011 S. Venaas
cisco Systems cisco Systems
April 16, 2010 October 11, 2010
LISP for Multicast Environments LISP for Multicast Environments
draft-ietf-lisp-multicast-03 draft-ietf-lisp-multicast-04
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 to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 18, 2010. This Internet-Draft will expire on April 14, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 45 skipping to change at page 2, line 45
10. Considerations when RP Addresses are Embedded in Group 10. Considerations when RP Addresses are Embedded in Group
Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 28 11. Taking Advantage of Upgrades in the Core . . . . . . . . . . . 28
12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 29 12. Mtrace Considerations . . . . . . . . . . . . . . . . . . . . 29
13. Security Considerations . . . . . . . . . . . . . . . . . . . 30 13. Security Considerations . . . . . . . . . . . . . . . . . . . 30
14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31
15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32 15. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
15.1. Normative References . . . . . . . . . . . . . . . . . . . 32 15.1. Normative References . . . . . . . . . . . . . . . . . . . 32
15.2. Informative References . . . . . . . . . . . . . . . . . . 32 15.2. Informative References . . . . . . . . . . . . . . . . . . 32
Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 34 Appendix A. Document Change Log . . . . . . . . . . . . . . . . . 34
A.1. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 34 A.1. Changes to draft-ietf-lisp-multicast-04.txt . . . . . . . 34
A.2. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 34 A.2. Changes to draft-ietf-lisp-multicast-03.txt . . . . . . . 34
A.3. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 34 A.3. Changes to draft-ietf-lisp-multicast-02.txt . . . . . . . 34
A.4. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 35 A.4. Changes to draft-ietf-lisp-multicast-01.txt . . . . . . . 34
A.5. Changes to draft-ietf-lisp-multicast-00.txt . . . . . . . 35
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 36
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 33, line 5 skipping to change at page 33, line 5
[ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP Alternative [ALT] Farinacci, D., Fuller, V., and D. Meyer, "LISP Alternative
Topology (LISP-ALT)", draft-ietf-lisp-alt-04.txt (work in Topology (LISP-ALT)", draft-ietf-lisp-alt-04.txt (work in
progress), April 2010. progress), April 2010.
[INTWORK] Lewis, D., Meyer, D., and D. Farinacci, "Interworking LISP [INTWORK] Lewis, D., Meyer, D., and D. Farinacci, "Interworking LISP
with IPv4 and IPv6", draft-ietf-lisp-interworking-01.txt with IPv4 and IPv6", draft-ietf-lisp-interworking-01.txt
(work in progress), March 2010. (work in progress), March 2010.
[LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, [LISP] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol (LISP)", "Locator/ID Separation Protocol (LISP)",
draft-ietf-lisp-07.txt (work in progress), April 2010. draft-ietf-lisp-09.txt (work in progress), October 2010.
[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),
November 2008. November 2008.
[MNAT] Wing, D. and T. Eckert, "Multicast Requirements for a [MNAT] Wing, D. and T. Eckert, "Multicast Requirements for a
Network Address (and port) Translator (NAT)", Network Address (and port) Translator (NAT)",
draft-ietf-behave-multicast-07.txt (work in progress), draft-ietf-behave-multicast-07.txt (work in progress),
June 2007. June 2007.
skipping to change at page 34, line 7 skipping to change at page 34, line 7
Version 2: Traceroute Facility for IP Multicast", Version 2: Traceroute Facility for IP Multicast",
draft-ietf-mboned-mtrace-v2-03.txt (work in progress), draft-ietf-mboned-mtrace-v2-03.txt (work in progress),
March 2009. March 2009.
[RPFV] Wijnands, IJ., Boers, A., and E. Rosen, "The RPF Vector [RPFV] Wijnands, IJ., Boers, A., and E. Rosen, "The RPF Vector
TLV", draft-ietf-pim-rpf-vector-06.txt (work in progress), TLV", draft-ietf-pim-rpf-vector-06.txt (work in progress),
February 2008. February 2008.
Appendix A. Document Change Log Appendix A. Document Change Log
A.1. Changes to draft-ietf-lisp-multicast-03.txt A.1. Changes to draft-ietf-lisp-multicast-04.txt
o Posted October 2010 to reset expiration timer.
o Updated references.
A.2. 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 34, line 29 skipping to change at page 34, line 35
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.2. Changes to draft-ietf-lisp-multicast-02.txt A.3. 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.3. Changes to draft-ietf-lisp-multicast-01.txt A.4. 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.4. Changes to draft-ietf-lisp-multicast-00.txt A.5. 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. 10 change blocks. 
13 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/