< draft-ietf-msdp-spec-19.txt   draft-ietf-msdp-spec-20.txt >
INTERNET-DRAFT Bill Fenner (Editor) INTERNET-DRAFT Bill Fenner (Editor)
draft-ietf-msdp-spec-19.txt David Meyer (Editor) draft-ietf-msdp-spec-20.txt David Meyer (Editor)
Category Experimental Category Experimental
Expires: November 2003 May 2003 Expires: November 2003 May 2003
Multicast Source Discovery Protocol (MSDP) Multicast Source Discovery Protocol (MSDP)
<draft-ietf-msdp-spec-19.txt> <draft-ietf-msdp-spec-20.txt>
Status of this Document Status of this Document
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 RFC2026. all provisions of Section 10 of RFC2026.
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 Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 9, line 40 skipping to change at page 9, line 40
(see section 15, event E2, action A2 ). When the timer expires, the (see section 15, event E2, action A2 ). When the timer expires, the
peer retries the connection and the timer is reset to [ConnectRetry- peer retries the connection and the timer is reset to [ConnectRetry-
Period]. It is deleted if either the connection transitions into Period]. It is deleted if either the connection transitions into
ESTABLISHED state or the peer is de-configured. ESTABLISHED state or the peer is de-configured.
6. Intermediate MSDP Peers 6. Intermediate MSDP Peers
Intermediate MSDP speakers do not originate periodic SA messages on Intermediate MSDP speakers do not originate periodic SA messages on
behalf of sources in other domains. In general, an RP MUST only behalf of sources in other domains. In general, an RP MUST only
originate an SA for a source which would register to it, and ONLY RPs originate an SA for a source which would register to it, and ONLY RPs
may originate SA messages. may originate SA messages. Intermediate MSDP speakers MAY forward SA
messages received from other domains.
7. SA Filtering and Policy 7. SA Filtering and Policy
As the number of (S,G) pairs increases in the Internet, an RP may As the number of (S,G) pairs increases in the Internet, an RP may
want to filter which sources it describes in SA messages. Also, want to filter which sources it describes in SA messages. Also,
filtering may be used as a matter of policy which at the same time filtering may be used as a matter of policy which at the same time
can reduce state. MSDP peers in transit domains should not filter SA can reduce state. MSDP peers in transit domains should not filter SA
messages or the flood-and-join model can not guarantee that sources messages or the flood-and-join model can not guarantee that sources
will be known throughout the Internet (i.e., SA filtering by transit will be known throughout the Internet (i.e., SA filtering by transit
domains may cause undesired lack of connectivity). In general, policy domains may cause undesired lack of connectivity). In general, policy
skipping to change at page 17, line 26 skipping to change at page 17, line 26
register received for a new source): register received for a new source):
-> Send Source-Active TLV -> Send Source-Active TLV
-> Set KeepAlive timer to [KeepAlive-Period] -> Set KeepAlive timer to [KeepAlive-Period]
*) SG-State-Timer expired (one timer per cache entry): *) SG-State-Timer expired (one timer per cache entry):
-> Implementation specific, typically mark the cache entry -> Implementation specific, typically mark the cache entry
for deletion for deletion
12. Packet Formats 12. Packet Formats
MSDP messages are encoded in TLV format. If an implementation MSDP messages are encoded in TLV format. If an implementation
receives a TLV that has length that is longer than expected, the TLV receives a TLV whose length exceeds the maximum TLV length specified
SHOULD be accepted. Any additional data SHOULD be ignored and the below, the TLV SHOULD be accepted. Any additional data, including
possible next TLV's in the same message, SHOULD be ignored, and the
MSDP session should not be reset. MSDP session should not be reset.
12.1. MSDP TLV format 12.1. MSDP TLV format
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value .... | | Type | Length | Value .... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 22, line 30 skipping to change at page 22, line 30
17. Acknowledgments 17. Acknowledgments
The editors would like to thank the original authors, Dino Farinacci, The editors 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
original contribution to the MSDP specification. In addition, Bill original 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, Brian Edwards, Selina John Zwiebel, Cristina Radulescu-Banu, Brian Edwards, Selina
Priestley, IJsbrand Wijnands, Tom Pusateri, Kristofer Warell, Henning Priestley, IJsbrand Wijnands, Tom Pusateri, Kristofer Warell, Henning
Eriksson, Thomas Eriksson, Dave Thaler, and Ravi Shekhar provided Eriksson, Thomas Eriksson, Dave Thaler, and Ravi Shekhar provided
useful and productive design feedback and comments. Mike McBride, useful and productive design feedback and comments. Toerless Eckert,
Leonard Giuliano, Swapna Yelamanchi, Toerless Eckert, John Meylor and Leonard Giuliano, Mike McBride, David Meyer, John Meylor, Pekka
Ishan Wu contributed to the final version of the draft. Savola, Ishan Wu, and Swapna Yelamanchi contributed to the final
version of the draft.
18. Security Considerations 18. Security Considerations
An MSDP implementation MUST implement Keyed MD5 [RFC2385] to secure An MSDP implementation MUST implement Keyed MD5 [RFC2385] to secure
control messages, and MUST be capable of interoperating with peers control messages, and MUST be capable of interoperating with peers
that do not support it. However, if one side of the connection is that do not support it. However, if one side of the connection is
configured with Keyed MD5 and the other side is not, the connection configured with Keyed MD5 and the other side is not, the connection
SHOULD NOT be established. SHOULD NOT be established.
In addition, to mitigate state explosion during denial of service and In addition, to mitigate state explosion during denial of service and
other attacks, SA filters and limits SHOULD be used with MSDP to other attacks, SA filters and limits SHOULD be used with MSDP to
limit the sources and groups that will be passed between RPs. limit the sources and groups that will be passed between RPs
[DEPLOY]. These filtering and limiting functions may include, for
example, access lists of source or group addresses which should not
be propagated to other domains using MSDP, the absolute highest
acceptable number of SA-state entries or a rate-limit of for the
creation of new SA-state entries after the connection has been
established.
19. IANA Considerations 19. IANA Considerations
This document creates a new namespace called "MSDP TLV Values" that This document creates a new namespace called "MSDP TLV Values" that
the IANA should manage. The intial seven MSDP TLV values are the IANA should manage. The intial seven MSDP TLV values are
specified in Section 12.2. The following two sections describe the specified in Section 12.2. The following two sections describe the
rules for allocating new MSDP TLV values. rules for allocating new MSDP TLV values.
19.1. IANA Allocated TLV Range 19.1. IANA Allocated TLV Range
skipping to change at page 24, line 14 skipping to change at page 24, line 14
20. References 20. References
20.1. Normative References 20.1. Normative References
[RFC1142] Oran, D. "OSI IS-IS Intra-domain Routing [RFC1142] Oran, D. "OSI IS-IS Intra-domain Routing
Protocol", RFC 1142, February 1990. Protocol", RFC 1142, February 1990.
[RFC2178] Moy, J., "OSPF Version 2", RFC 2178, April, 1998. [RFC2178] Moy, J., "OSPF Version 2", RFC 2178, April, 1998.
[RFC2283] Bates, T., Chandra, R., Katz, D., and [RFC2283] Bates, T., R. Chandra, and D. Katz, and
Y. Rekhter., "Multiprotocol Extensions for Y. Rekhter., "Multiprotocol Extensions for
BGP-4", RFC 2283, February 1998. BGP-4", RFC 2283, February 1998.
[RFC2362] Estrin D., et al., "Protocol Independent [RFC2362] Estrin D., et al., "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Multicast - Sparse Mode (PIM-SM): Protocol
Specification", RFC 2362, June 1998. Specification", RFC 2362, June 1998.
[RFC2365] Meyer, D. "Administratively Scoped IP Multicast", [RFC2365] Meyer, D. "Administratively Scoped IP Multicast",
RFC 2365, July, 1998. RFC 2365, July, 1998.
skipping to change at page 24, line 39 skipping to change at page 24, line 39
Writing an IANA Considerations Section in Writing an IANA Considerations Section in
RFCs", RFC2434/BCP0026, October, 1998. RFCs", RFC2434/BCP0026, October, 1998.
[RFC3446] Kim, D., et al., "Anycast Rendezvous Point (RP) [RFC3446] Kim, D., et al., "Anycast Rendezvous Point (RP)
Mechanism using Protocol Independent Multicast Mechanism using Protocol Independent Multicast
(PIM) and Multicast Source Discovery Protocol (PIM) and Multicast Source Discovery Protocol
(MSDP)", RFC 3446, January, 2003. (MSDP)", RFC 3446, January, 2003.
20.2. Informative References 20.2. Informative References
[DEPLOY] McBride, M., J. Meylor, and D. Meyer, "Multicast
Source Discovery Protocol (MSDP) Deployment
Scenarios", draft-ietf-mboned-msdp-deploy-02.txt,
Work in Progress.
[RFC2119] S. Bradner, "Key words for use in RFCs to [RFC2119] S. Bradner, "Key words for use in RFCs to
Indicate Requirement Levels", RFC 2119, March, Indicate Requirement Levels", RFC 2119, March,
1997. 1997.
21. Editor's Addresses 21. Editor's Addresses
Bill Fenner Bill Fenner
AT&T Labs -- Research AT&T Labs -- Research
75 Willow Road 75 Willow Road
Menlo Park, CA 94025 Menlo Park, CA 94025
 End of changes. 9 change blocks. 
11 lines changed or deleted 24 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/