--- 1/draft-ietf-mboned-routingarch-07.txt 2007-06-14 17:12:05.000000000 +0200 +++ 2/draft-ietf-mboned-routingarch-08.txt 2007-06-14 17:12:05.000000000 +0200 @@ -1,22 +1,22 @@ Internet Engineering Task Force P. Savola Internet-Draft CSC/FUNET -Obsoletes: November 21, 2006 +Obsoletes: June 14, 2007 3913,2189,2201,1584,1585 (if approved) Intended status: Best Current Practice -Expires: May 25, 2007 +Expires: December 16, 2007 Overview of the Internet Multicast Routing Architecture - draft-ietf-mboned-routingarch-07.txt + draft-ietf-mboned-routingarch-08.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -27,25 +27,25 @@ 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 May 25, 2007. + This Internet-Draft will expire on December 16, 2007. Copyright Notice - Copyright (C) The IETF Trust (2006). + Copyright (C) The IETF Trust (2007). Abstract The lack of up-to-date documentation on IP multicast routing protocols and procedures has caused a great deal of confusion. To clarify the situation, this memo describes the routing protocols and techniques currently (as of this writing) in use. This memo also Obsoletes and reclassifies to Historic a number of older multicast protocols. @@ -89,21 +89,21 @@ 2.6.3. Summary . . . . . . . . . . . . . . . . . . . . . . . 15 2.7. Restricting Multicast Flooding in the Link Layer . . . . . 16 2.7.1. Router-to-Router Flooding Reduction . . . . . . . . . 16 2.7.2. Host/Router Flooding Reduction . . . . . . . . . . . . 16 2.7.3. Summary . . . . . . . . . . . . . . . . . . . . . . . 17 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 5. Security Considerations . . . . . . . . . . . . . . . . . . . 18 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.1. Normative References . . . . . . . . . . . . . . . . . . . 18 - 6.2. Informative References . . . . . . . . . . . . . . . . . . 20 + 6.2. Informative References . . . . . . . . . . . . . . . . . . 19 Appendix A. Multicast Payload Transport Extensions . . . . . . . 22 A.1. Reliable Multicast . . . . . . . . . . . . . . . . . . . . 23 A.2. Multicast Group Security . . . . . . . . . . . . . . . . . 23 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 23 Intellectual Property and Copyright Statements . . . . . . . . . . 24 1. Introduction Good, up-to-date documentation of IP multicast is close to non- existent. This issue is severely felt with multicast routing @@ -342,28 +342,28 @@ reachability information. The topology information is needed to perform efficient distribution of multicast transmissions and to prevent transmission loops by applying it to the Reverse Path Forwarding (RPF) check. This subsection introduces these protocols. 2.2.1. Multi-protocol BGP - Multiprotocol Extensions for BGP-4 [I-D.ietf-idr-rfc2858bis] (often - referred to as "MBGP"; however, it is worth noting that "MBGP" does - *not* stand for "Multicast BGP") specifies a mechanism by which BGP - can be used to distribute different reachability information for - unicast (SAFI=1) and multicast traffic (SAFI=2). Multiprotocol BGP - has been widely deployed for years, and is also needed to route IPv6. - Note that SAFI=3 was originally specified for "both unicast and - multicast" but has since then been deprecated. + Multiprotocol Extensions for BGP-4 [RFC4760] (often referred to as + "MBGP"; however, it is worth noting that "MBGP" does *not* stand for + "Multicast BGP") specifies a mechanism by which BGP can be used to + distribute different reachability information for unicast (SAFI=1) + and multicast traffic (SAFI=2). Multiprotocol BGP has been widely + deployed for years, and is also needed to route IPv6. Note that + SAFI=3 was originally specified for "both unicast and multicast" but + has since then been deprecated. These extensions are in widespread use wherever BGP is used to distribute unicast topology information. Multicast-enabled networks that use BGP should use Multiprotocol BGP to distribute multicast reachability information explicitly even if the topologies are congruent to make an explicit statement about multicast reachability. A number of significant multicast transit providers even require this, by doing the RPF lookups solely based on explicitly advertised multicast address family. @@ -810,72 +810,57 @@ mentioned protocols is out of scope of this memo. However, there has been analysis of the security of multicast routing infrastructures [RFC4609], IGMP/MLD [I-D.daley-magma-smld-prob], and PIM last-hop issues [I-D.ietf-pim-lasthop-threats]. 6. References 6.1. Normative References - [I-D.ietf-idr-rfc2858bis] - Bates, T., "Multiprotocol Extensions for BGP-4", - draft-ietf-idr-rfc2858bis-10 (work in progress), - March 2006. - - [I-D.ietf-isis-wg-multi-topology] - Przygienda, T., "M-ISIS: Multi Topology (MT) Routing in - IS-IS", draft-ietf-isis-wg-multi-topology-11 (work in - progress), October 2005. - - [I-D.ietf-mboned-addrarch] - Savola, P., "Overview of the Internet Multicast Addressing - Architecture", draft-ietf-mboned-addrarch-05 (work in - progress), October 2006. - [I-D.ietf-ospf-mt] Psenak, P., "Multi-Topology (MT) Routing in OSPF", - draft-ietf-ospf-mt-06 (work in progress), February 2006. + draft-ietf-ospf-mt-08 (work in progress), January 2007. [I-D.ietf-pim-bidir] Handley, M., "Bi-directional Protocol Independent - Multicast (BIDIR-PIM)", draft-ietf-pim-bidir-08 (work in - progress), October 2005. + Multicast (BIDIR-PIM)", draft-ietf-pim-bidir-09 (work in + progress), February 2007. [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002. [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery Protocol (MSDP)", RFC 3618, October 2003. [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address", RFC 3956, November 2004. - [RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol - Independent Multicast - Dense Mode (PIM-DM): Protocol - Specification (Revised)", RFC 3973, January 2005. - [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006. [RFC4607] Holbrook, H. and B. Cain, "Source-Specific Multicast for IP", RFC 4607, August 2006. + [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, + "Multiprotocol Extensions for BGP-4", RFC 4760, + January 2007. + 6.2. Informative References [802.1ak] "IEEE 802.1ak - Multiple Registration Protocol", . [CGMP] "Cisco Group Management Protocol", . [GMRP] "GARP Multicast Registration Protocol", . @@ -889,39 +874,50 @@ [I-D.ietf-idmr-dvmrp-v3] Pusateri, T., "Distance Vector Multicast Routing Protocol", draft-ietf-idmr-dvmrp-v3-11 (work in progress), December 2003. [I-D.ietf-idmr-dvmrp-v3-as] Pusateri, T., "Distance Vector Multicast Routing Protocol Applicability Statement", draft-ietf-idmr-dvmrp-v3-as-01 (work in progress), May 2004. + [I-D.ietf-isis-wg-multi-topology] + Przygienda, T., "M-ISIS: Multi Topology (MT) Routing in + IS-IS", draft-ietf-isis-wg-multi-topology-11 (work in + progress), October 2005. + [I-D.ietf-l2vpn-vpls-pim-snooping] Hemige, V., "PIM Snooping over VPLS", - draft-ietf-l2vpn-vpls-pim-snooping-00 (work in progress), - August 2006. + draft-ietf-l2vpn-vpls-pim-snooping-01 (work in progress), + March 2007. + + [I-D.ietf-mboned-addrarch] + Savola, P., "Overview of the Internet Multicast Addressing + Architecture", draft-ietf-mboned-addrarch-05 (work in + progress), October 2006. [I-D.ietf-mboned-ipv6-multicast-issues] Savola, P., "IPv6 Multicast Deployment Issues", draft-ietf-mboned-ipv6-multicast-issues-02 (work in progress), February 2005. [I-D.ietf-pim-lasthop-threats] Savola, P. and J. Lingard, "Last-hop Threats to Protocol Independent Multicast (PIM)", draft-ietf-pim-lasthop-threats-00 (work in progress), October 2006. [I-D.ietf-pim-sm-bsr] Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", - draft-ietf-pim-sm-bsr-09 (work in progress), June 2006. + draft-ietf-pim-sm-bsr-10 (work in progress), + February 2007. [I-D.lehtonen-mboned-dynssm-req] Lehtonen, R., "Requirements for discovery of dynamic SSM sources", draft-lehtonen-mboned-dynssm-req-00 (work in progress), February 2005. [IM-GAPS] Meyer, D. and B. Nickless, "Internet Multicast Gap Analysis from the MBONED Working Group for the IESG [Expired]", draft-ietf-mboned-iesg-gap-analysis-00 (work in progress), July 2002. @@ -972,20 +968,24 @@ [RFC3488] Wu, I. and T. Eckert, "Cisco Systems Router-port Group Management Protocol (RGMP)", RFC 3488, February 2003. [RFC3740] Hardjono, T. and B. Weis, "The Multicast Group Security Architecture", RFC 3740, March 2004. [RFC3913] Thaler, D., "Border Gateway Multicast Protocol (BGMP): Protocol Specification", RFC 3913, September 2004. + [RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol + Independent Multicast - Dense Mode (PIM-DM): Protocol + Specification (Revised)", RFC 3973, January 2005. + [RFC4286] Haberman, B. and J. Martin, "Multicast Router Discovery", RFC 4286, December 2005. [RFC4541] Christensen, M., Kimball, K., and F. Solensky, "Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches", RFC 4541, May 2006. [RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick, "Internet Group Management Protocol (IGMP) / Multicast @@ -1037,21 +1037,21 @@ Pekka Savola CSC - Scientific Computing Ltd. Espoo Finland Email: psavola@funet.fi Full Copyright Statement - Copyright (C) The IETF Trust (2006). + Copyright (C) The IETF Trust (2007). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF