draft-ietf-mboned-ssm232-03.txt   draft-ietf-mboned-ssm232-04.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 14
INTERNET DRAFT Sprint INTERNET DRAFT Sprint
Rob Rockell Rob Rockell
Sprint Sprint
Greg Shepherd Greg Shepherd
Procket Procket
Category Best Current Practices Category Best Current Practices
January, 2003 January, 2003
Source-Specific Protocol Independent Multicast in 232/8 Source-Specific Protocol Independent Multicast in 232/8
<draft-ietf-mboned-ssm232-03.txt> <draft-ietf-mboned-ssm232-04.txt>
1. Status of this Memo 1. Status of this Memo
This document specifies an Internet Best Current Practices for the This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited. improvements. Distribution of this memo is unlimited.
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.
skipping to change at page 3, line 20 skipping to change at page 3, line 20
Eliminating the use of shared trees for groups in 232/8, while Eliminating the use of shared trees for groups in 232/8, while
maintaining coexistence with PIM-SM, behavior of the RP and/or the DR maintaining coexistence with PIM-SM, behavior of the RP and/or the DR
needs to be modified. This can be accomplished by needs to be modified. This can be accomplished by
- preventing data for 232/8 groups from being sent encapsulated to - preventing data for 232/8 groups from being sent encapsulated to
the RP by the DR the RP by the DR
- preventing the RP from accepting registers for 232/8 groups from - preventing the RP from accepting registers for 232/8 groups from
the DR the DR
- preventing the RP from forwarding accepted data down (*,G) tree - preventing the RP from forwarding accepted data down (*,G)
tree for 232/8 groups
5.2. Preventing remote sources from being learned/joined via MSDP 5.2. Preventing remote sources from being learned/joined via MSDP
PIM-SS does not require active source announcements via MSDP. All PIM-SS does not require active source announcements via MSDP. All
source announcements are received out of band, the the last hop source announcements are received out of band, the the last hop
router is responsible for sending (S,G) joins directly to the source. router is responsible for sending (S,G) joins directly to the source.
To prevent propagation of SAs in the 232/8 range, an RP SHOULD To prevent propagation of SAs in the 232/8 range, an RP SHOULD
- never originate an SA for any 232/8 groups - never originate an SA for any 232/8 groups
- never accept or forward an SA for any 232/8 groups. - never accept or forward an SA for any 232/8 groups.
5.3. Preventing receivers from joining the shared tree 5.3. Preventing receivers from joining the shared tree
Local PIM domain practices need to be enforced to prevent local Local PIM domain practices need to be enforced to prevent local
receivers from joining the shared tree for 232/8 groups. This can be receivers from joining the shared tree for 232/8 groups. This can be
accomplished by accomplished by
- preventing DR from sending (*,G) joins - preventing DR from sending (*,G) joins for 232/8 groups
- preventing RP from accepting (*,G) join - preventing RP from accepting (*,G) join for 232/8 groups
Within a local PIM domain, any last-hop router NOT preventing (*,G) However, within a local PIM domain, any last-hop router NOT
joins MAY trigger (*,G) state toward the RP which intersects an preventing (*,G) joins may trigger unwanted (*,G) state toward
existing (S,G) tree, allowing the receiver on the shared tree to the RP which intersects an existing (S,G) tree, allowing the
receive the data. So if the last-hop routers are not preventing (*,G) receiver on the shared tree to receive the data, breaking the
joins, then all routers in the domain must also prevent (*,G) joins. source-specific [SSM] service model. It is therefore recommended
that ALL routers in the domain MUST reject AND never originate
(*,G) joins for 232/8 groups.
5.4. Preventing RP's as candidates for 232/8 5.4. Preventing RP's as candidates for 232/8
Because PIM-SS does not require an RP, all RPs SHOULD NOT offer themí Because PIM-SS does not require an RP, all RPs SHOULD NOT offer themí
selves as candidates in the 232/8 range. This can be accomplished by selves as candidates in the 232/8 range. This can be accomplished by
- preventing RP/BSR from announcing in the 232/8 range - preventing RP/BSR from announcing in the 232/8 range
- preventing DRs from accepting delegations in this range - preventing ALL routers from accepting RP delegations in the
232/8 range
- precluding RP functionality on RP for the 232/8 range - precluding RP functionality on RP for the 232/8 range
6. References 6. Informative References
[IANA] http://www.iana.org [IANA] http://www.iana.org
[SSM] Holbrook, H., Cain, B., "Source-Specific Multicast",
draft-ietf-ssm-arch-01.txt, November, 2002.
[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.
7. Normative References
[MSDP] D. Meyer and Bill Fenner (Editors), "The Multicast
Source Discovery Protocol (MSDP)",
draft-ietf-msdp-spec-14.txt, November 2002.
[SSM] Holbrook, H., Cain, B., "Source-Specific Multicast",
draft-ietf-ssm-arch-01.txt, November, 2002.
[RFC2362] D. Estrin, et. al., "Protocol Independent Multicast-Sparse [RFC2362] D. Estrin, et. al., "Protocol Independent Multicast-Sparse
Mode (PIM-SM): Protocol Specification", RFC 2362, June, Mode (PIM-SM): Protocol Specification", RFC 2362, June,
1998. 1998.
[MSDP] D. Meyer and Bill Fenner (Editors), "The Multicast 8. Author's Addresses
Source Discovery Protocol (MSDP)", draft-ietf-msdp-spec-14.txt,
November 2002.
7. Author's Addresses
Greg Shepherd David Meyer
Procket Sprint
Email: shep@procket.net Email: dmm@sprint.net
Robert Rockell Robert Rockell
Sprint Sprint
Email: rrockell@sprint.net Email: rrockell@sprint.net
David Meyer Greg Shepherd
Sprint Procket
Email: dmm@sprint.net Email: shep@procket.com
8. Full Copyright Statement 9. Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docí included on all such copies and derivative works. However, this docí
ument itself may not be modified in any way, such as by removing the ument itself may not be modified in any way, such as by removing the
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/