--- 1/draft-ietf-mboned-msdp-deploy-04.txt 2006-02-05 00:20:31.000000000 +0100 +++ 2/draft-ietf-mboned-msdp-deploy-05.txt 2006-02-05 00:20:31.000000000 +0100 @@ -1,23 +1,23 @@ INTERNET-DRAFT M. McBride -draft-ietf-msdp-deploy-04.txt J. Meylor +draft-ietf-msdp-deploy-05.txt J. Meylor D. Meyer Category Best Current Practice -Expires: April 2004 October 2003 +Expires: July 2004 January 2004 Multicast Source Discovery Protocol (MSDP) Deployment Scenarios - + Copyright Notice - Copyright (C) The Internet Society (2003). All Rights Reserved. + Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document describes best current practices for intra-domain and inter-domain deployment of the Multicast Source Discovery Protocol (MSDP) in conjunction with Protocol Independent Multicast Sparse Mode (PIM-SM). Status of this Document @@ -69,21 +69,21 @@ 6. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 14 7. Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 8.1. Normative References. . . . . . . . . . . . . . . . . . . . 16 8.2. Informative References. . . . . . . . . . . . . . . . . . . 17 9. Author's Addresses . . . . . . . . . . . . . . . . . . . . . . 17 10. Full Copyright Statement. . . . . . . . . . . . . . . . . . . 17 1. Introduction - MSDP [MSDP] is used primarily in two deployment scenarios: + MSDP [RFC3618] is used primarily in two deployment scenarios: o Between PIM Domains MSDP can be used between Protocol Independent Multicast Sparse Mode (PIM-SM) [RFC2362] domains to convey information about active sources available in other domains. MSDP peering used in such cases is generally one to one peering, and utilizes the deterministic peer-RPF (Reverse Path Forwarding) rules described in the MSDP specification (i.e., does not use mesh-groups). Peerings can be aggregated on a single MSDP @@ -513,21 +513,21 @@ Typically there is a fair amount of (S,G) state in a PIM-SM domain that is local to the domain. However, without proper filtering, sa- messages containing these local (S,G) announcements may be advertised to the global MSDP infrastructure. Examples of this includes domain local applications that use global IP multicast addresses and sources that use RFC 1918 addresses [RFC1918]. To improve on the scalability of MSDP and to avoid global visibility of domain local (S,G) information, an external SA filter list is recommended to help prevent unnecessary creation, forwarding, and caching of well-known - domain local sources [UNUSABLE]. + domain local sources. 5.2. SA message state limits Proper filtering on SA message origination, receipt, and forwarding will significantly reduce the likelihood of unintended and unexpected spikes in MSDP state However, a sa-cache state limit SHOULD BE configured as a final safeguard to state spikes. When an MSDP peering has reached a stable state (i.e., when the peering has been established and the initial SA state has been transferred), it may also be desirable to configure a rate limiter for the creation of new @@ -541,28 +541,20 @@ 7. Acknowledgments The authors would like to thank Pekka Savola, John Zwiebel, Swapna Yelamanchi, Greg Shepherd, and Jay Ford for their feedback on earlier versions of this document. 8. References 8.1. Normative References - [MSDP] Meyer, D. and W. Fenner (Editors), "The Multicast - Source Discovery Protocol (MSDP)", draft-ietf-msdp-spec-20.txt, - May 2003. Work in Progress. - - [SSM] Holbrook, H., and B. Cain, "Source-Specific - Multicast for IP", draft-ietf-ssm-arch-03.txt, - May, 2003. Work in Progress. - [RFC1771] Rekhter, Y., and T. Li, "A Border Gateway Protocol 4 (BGP-4)", RFC 1771, March 1995. [RFC1918] Y. Rekhter, R. Moskowitz, D. Karrenberg, G. de Groot, E. Lear, "Address Allocation for Private Internets", RFC 1918, Feburary, 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels" RFC 2119/BCP 14, March 1997. @@ -583,53 +575,53 @@ June 2000. [RFC3330] IANA, "Special-User IPv4 Addresses", RFC 3330, September 2002. [RFC3446] Kim, D., et. al., "Anycast Rendezvous Point (RP) Mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP)", RFC 3446, January, 2003. - [UNUSABLE] Nickless, B., "IPv4 Multicast Unusable Group And - Source Addresses", draft-nickless-ipv4-mcast-unusable-02.txt, - June, 2003. Work in Progress. + [RFC3618] Meyer, D. and W. Fenner (Editors), "The Multicast + Source Discovery Protocol (MSDP)", RFC 3618, + October, 2003. 8.2. Informative References [AUTORP] Fenner, W., et. al., " Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol - Specification (Revised)", draft-ietf-pim-sm-v2-new-07.txt, - March, 2003. Work in Progress. + Specification (Revised)", draft-ietf-pim-sm-v2-new-08.txt, + April, 2004. Work in progress. [BSR] Fenner, W., et. al., "Bootstrap Router (BSR) Mechanism for PIM Sparse Mode", draft-ietf-pim-sm-bsr-03.txt, - February, 2003. Work in Progress. + February, 2003. Work in progress. [IANA] http://www.iana.org 9. Author's Addresses Mike McBride Cisco Systems Email: mcbride@cisco.com John Meylor Cisco Systems Email: jmeylor@cisco.com David Meyer Email: dmm@1-4-5.net 10. Full Copyright Statement - Copyright (C) The Internet Society (2003). All Rights Reserved. + Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of