< draft-ietf-msdp-spec-07.txt   draft-ietf-msdp-spec-08.txt >
Network Working Group David Meyer (Editor) Network Working Group David Meyer (Editor)
INTERNET DRAFT INTERNET DRAFT
Category Standards Track Category Standards Track
March, 2001 April, 2001
Multicast Source Discovery Protocol (MSDP) Multicast Source Discovery Protocol (MSDP)
<draft-ietf-msdp-spec-07.txt> <draft-ietf-msdp-spec-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 8, line 22 skipping to change at page 8, line 22
14.1. Peer-RPF Forwarding Rules 14.1. Peer-RPF Forwarding Rules
An SA message originated by R and received by X An SA message originated by R and received by X
from N is accepted if N is the peer-RPF neighbor for R, and is from N is accepted if N is the peer-RPF neighbor for R, and is
discarded otherwise. discarded otherwise.
MP(R,N) MP(N,X) MP(R,N) MP(N,X)
R ---------....-------> N ------------------> X R ---------....-------> N ------------------> X
SA(S,G,R) SA(S,G,R) SA(S,G,R) SA(S,G,R)
Where MP(A,B) is an MSDP peering path (one or more Where MP(R,N) is an MSDP peering path (one or more
MSDP peers) between A and B, and SA(S,G,R) is an MSDP peers) between R and N, and SA(S,G,R) is an
SA message for source S on group G orignated by SA message for source S on group G orignated by
an RP R. an RP R.
The peer-RPF neighbor is chosen deterministically, The peer-RPF neighbor is chosen deterministically,
using the first of the following rules that matches. using the first of the following rules that matches.
X accepts the SA from R forwarded by N if : X accepts the SA from R forwarded by N if :
(i). R is the RPF neighbor if we have an MSDP peering (i). R is the RPF neighbor of X if we have an MSDP peering
with R (e.g. N == R). with R (e.g. N == R).
(ii). N is the RPF neighbor of X if N is a MSDP peer of (ii). N is the RPF neighbor of X if N is a MSDP peer of
X and N is the next hop toward R. X and N is the next hop toward R.
(iii). N is the RPF neighbor of X if X has an MSDP (iii) N is the RPF neighbor of X if N resides in the first AS
peering(s) with the neighboring AS (the AS towards R and N has a higher IP address than any other
with that AS, then the MSDP neighbor with the MSDP peer of X that resides in first AS towards R.
highest IP address in the first AS toward R is
the RPF peer.
(iv). N is the RPF neighbor of X if (intra-domain case): (iv). N is the RPF neighbor of X if (intra-domain case):
(a). N == R (i.e. N originated the SA), or (a). N == R (i.e. N originated the SA), or
(b). X and N are part of a MSDP Mesh Group. Note that in (b). X and N are part of a MSDP Mesh Group. Note that in
this case every member of mesh group is an peer-RPF this case every member of mesh group is an peer-RPF
neighbor of X. neighbor of X.
(v). If none of the above match, and we have an (v). If none of the above match, and we have an
skipping to change at page 25, line 15 skipping to change at page 25, line 15
21. Acknowledgments 21. Acknowledgments
The editor would like to thank the original authors, Dino Farinacci, The editor would like to thank the original authors, Dino Farinacci,
Yakov Rehkter, Peter Lothberg, Hank Kilmer, and Jermey Hall for their Yakov Rehkter, Peter Lothberg, Hank Kilmer, and Jermey Hall for their
orginal contribution to the MSDP specification. In addition, Bill orginal contribution to the MSDP specification. In addition, Bill
Nickless, John Meylor, Liming Wei, Manoj Leelanivas, Mark Turner, Nickless, John Meylor, Liming Wei, Manoj Leelanivas, Mark Turner,
John Zwiebel, Cristina Radulescu-Banu and IJsbrand Wijnands provided John Zwiebel, Cristina Radulescu-Banu and IJsbrand Wijnands provided
useful and productive design feedback and comments. In addition to useful and productive design feedback and comments. In addition to
many other contributions, Tom Pusateri helped to clarify the many other contributions, Tom Pusateri helped to clarify the
connection state machine, Dave Thaler helped to clarify the connection state machine, Dave Thaler helped to clarify the
Notification message types, and Bill Fenner helped to clarify the Notification message types, and countless others helped to clarify
Peer-RPF rules. the Peer-RPF rules.
22. Editor's Address: 22. Editor's Address:
David Meyer David Meyer
Cisco Systems, Inc. Cisco Systems, Inc.
170 Tasman Drive 170 Tasman Drive
San Jose, CA, 95134 San Jose, CA, 95134
Email: dmm@cisco.com Email: dmm@cisco.com
23. REFERENCES 23. REFERENCES
[IANA] ftp://www.iana.org [IANA] www.iana.org
[RFC1700] J. Reynolds and J. Postel, "Assigned Numbers", RFC 1700, [RFC1700] J. Reynolds and J. Postel, "Assigned Numbers", RFC 1700,
October, 1994. October, 1994.
[RFC2784] Farinacci, D., et al., "Generic Routing Encapsulation [RFC2784] Farinacci, D., et al., "Generic Routing Encapsulation
(GRE)", RFC 2784, March 2000. (GRE)", RFC 2784, March 2000.
[RFC768] Postel, J. "User Datagram Protocol", RFC 768, August, [RFC768] Postel, J. "User Datagram Protocol", RFC 768, August,
1980. 1980.
skipping to change at line 1019 skipping to change at page 28, line 4
[RFC2283] Bates, T., Chandra, R., Katz, D., and Y. Rekhter., [RFC2283] Bates, T., Chandra, R., Katz, D., and Y. Rekhter.,
"Multiprotocol Extensions for BGP-4", RFC 2283, "Multiprotocol Extensions for BGP-4", RFC 2283,
February 1998. February 1998.
[RFC2362] Estrin D., et al., "Protocol Independent Multicast - [RFC2362] Estrin D., et al., "Protocol Independent Multicast -
Sparse Mode (PIM-SM): Protocol Specification", RFC Sparse Mode (PIM-SM): Protocol Specification", RFC
2362, June 1998. 2362, June 1998.
[RFC2365] Meyer, D. "Administratively Scoped IP Multicast", RFC [RFC2365] Meyer, D. "Administratively Scoped IP Multicast", RFC
2365, July, 1998. 2365, July, 1998.
24. Full Copyright Statement
Copyright (C) The Internet Society (2001). 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
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.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 9 change blocks. 
14 lines changed or deleted 11 lines changed or added

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