draft-ietf-mboned-anycast-rp-07.txt | draft-ietf-mboned-anycast-rp-08.txt | |||
---|---|---|---|---|
MBONED Working Group Dorian Kim | MBONED Working Group Dorian Kim | |||
Internet Draft Verio | Internet Draft Verio | |||
David Meyer | David Meyer | |||
Cisco Systems | ||||
Henry Kilmer | Henry Kilmer | |||
Dino Farinacci | Dino Farinacci | |||
Procket Networks | Procket Networks | |||
Category Experimental | Category Experimental | |||
July, 2001 | May, 2001 | |||
Anycast RP mechanism using PIM and MSDP | Anycast RP mechanism using PIM and MSDP | |||
<draft-ietf-mboned-anycast-rp-07.txt> | <draft-ietf-mboned-anycast-rp-08.txt> | |||
1. Status of this Memo | 1. Status of this Memo | |||
This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
all provisions of Section 10 of RFC 2026. | all provisions of Section 10 of RFC 2026. | |||
Internet Drafts are working documents of the Internet Engineering | Internet Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that other | Task Force (IETF), its areas, and its working groups. Note that other | |||
groups may also distribute working documents as Internet-Drafts. | groups may also distribute working documents as Internet-Drafts. | |||
skipping to change at page 2, line 17 | skipping to change at page 2, line 17 | |||
This document describes a mechanism to allow for an arbitrary number | This document describes a mechanism to allow for an arbitrary number | |||
of RPs per group in a single shared-tree PIM-SM domain. | of RPs per group in a single shared-tree PIM-SM domain. | |||
This memo is a product of the MBONE Deployment Working Group (MBONED) | This memo is a product of the MBONE Deployment Working Group (MBONED) | |||
in the Operations and Management Area of the Internet Engineering | in the Operations and Management Area of the Internet Engineering | |||
Task Force. Submit comments to <mboned@ns.uoregon.edu> or the | Task Force. Submit comments to <mboned@ns.uoregon.edu> or the | |||
authors. | authors. | |||
3. Copyright Notice | 3. Copyright Notice | |||
Copyright (C) The Internet Society (2000). All Rights Reserved. | Copyright (C) The Internet Society (2001). All Rights Reserved. | |||
4. Introduction | 4. Introduction | |||
PIM-SM as defined in RFC 2362 allows for only a single active RP per | PIM-SM as defined in RFC 2362 allows for only a single active RP per | |||
group, and as such the decision of optimal RP placement can become | group, and as such the decision of optimal RP placement can become | |||
problematic for a multi-regional network deploying PIM-SM. | problematic for a multi-regional network deploying PIM-SM. | |||
Anycast RP relaxes an important constraint in PIM-SM, namely, that | Anycast RP relaxes an important constraint in PIM-SM, namely, that | |||
there can be only one group to RP mapping can be active at any time. | there can be only one group to RP mapping can be active at any time. | |||
The single mapping property has several implications, including | The single mapping property has several implications, including | |||
skipping to change at page 7, line 10 | skipping to change at page 7, line 10 | |||
7.3. MSDP Peer Integrity | 7.3. MSDP Peer Integrity | |||
As is the the case for BGP, MSDP peers can be protected using keyed | As is the the case for BGP, MSDP peers can be protected using keyed | |||
MD5 [RFC1828]. | MD5 [RFC1828]. | |||
8. Acknowledgments | 8. Acknowledgments | |||
John Meylor, Bill Fenner, Dave Thaler and Tom Pusateri provided | John Meylor, Bill Fenner, Dave Thaler and Tom Pusateri provided | |||
insightful comments on earlier versions for this idea. | insightful comments on earlier versions for this idea. | |||
9. References | 9. Author's Address | |||
[MSDP] D. Farinacci, et. al., "Multicast Source Discovery | Dorian Kim | |||
Protocol (MSDP)", draft-ietf-msdp-spec-02.txt, | Verio, Inc. | |||
January, 2000. Work in Progress. | 2361 Lancashire Dr. #2A | |||
Ann Arbor, MI 48015 | ||||
Email: dorian@blackrose.org | ||||
Hank Kilmer | ||||
Email: hank@rem.com | ||||
Dino Farinacci | ||||
Procket Networks | ||||
Email: dino@procket.com | ||||
David Meyer | ||||
Email: dmm@maoz.com | ||||
10. References | ||||
[MSDP] D. Meyer and B. Fenner, Editors, "Multicast Source Discovery | ||||
Protocol (MSDP)", draft-ietf-msdp-spec-10.txt, | ||||
May, 2001. Work in Progress. | ||||
[RFC1825] Atkinson, R., "IP Security Architecture", August 1995. | [RFC1825] Atkinson, R., "IP Security Architecture", August 1995. | |||
[RFC1828] P. Metzger and W. Simpson, "IP Authentication using Keyed | [RFC1828] P. Metzger and W. Simpson, "IP Authentication using Keyed | |||
MD5", RFC 1828, August, 1995. | MD5", RFC 1828, August, 1995. | |||
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate | [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate | |||
Requirement Levels", RFC 2119, March, 1997. | Requirement Levels", RFC 2119, March, 1997. | |||
[RFC2362] D. Estrin, et. al., "Protocol Independent Multicast- | [RFC2362] D. Estrin, et. al., "Protocol Independent Multicast- | |||
skipping to change at page 7, line 36 | skipping to change at page 9, line 5 | |||
2362, June, 1998. | 2362, June, 1998. | |||
[RFC2382] Moy, J., "OSPF Version 2", RFC 2382, April 1998. | [RFC2382] Moy, J., "OSPF Version 2", RFC 2382, April 1998. | |||
[RFC2385] Herrernan, A., "Protection of BGP Sessions via the TCP | [RFC2385] Herrernan, A., "Protection of BGP Sessions via the TCP | |||
MD5 Signature Option", RFC 2385, August, 1998. | MD5 Signature Option", RFC 2385, August, 1998. | |||
[RFC2403] C. Madson and R. Glenn, "The Use of HMAC-MD5-96 within | [RFC2403] C. Madson and R. Glenn, "The Use of HMAC-MD5-96 within | |||
ESP and AH", RFC 2403, November, 1998. | ESP and AH", RFC 2403, November, 1998. | |||
10. Author's Address | 11. Full Copyright Statement | |||
Dorian Kim | Copyright (C) The Internet Society (2001). All Rights Reserved. | |||
Verio, Inc. | ||||
2361 Lancashire Dr. #2A | ||||
Ann Arbor, MI 48015 | ||||
Email: dorian@blackrose.org | ||||
Hank Kilmer | This document and translations of it may be copied and furnished to | |||
Email: hank@rem.com | 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 | ||||
developing Internet standards in which case the procedures for | ||||
copyrights defined in the Internet Standards process must be | ||||
followed, or as required to translate it into languages other than | ||||
English. | ||||
Dino Farinacci | The limited permissions granted above are perpetual and will not be | |||
Procket Networks | revoked by the Internet Society or its successors or assigns. | |||
Email: dino@procket.com | ||||
David Meyer | This document and the information contained herein is provided on an | |||
Cisco Systems, Inc. | "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING | |||
170 Tasman Drive | TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING | |||
San Jose, CA, 95134 | BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION | |||
Email: dmm@cisco.com | HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF | |||
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | ||||
End of changes. | ||||
This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |