draft-ietf-pim-source-discovery-bsr-09.txt   draft-ietf-pim-source-discovery-bsr-10.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Network Working Group IJ. Wijnands Network Working Group IJ. Wijnands
Internet-Draft S. Venaas Internet-Draft S. Venaas
Intended status: Experimental Cisco Systems, Inc. Intended status: Experimental Cisco Systems, Inc.
Expires: July 29, 2018 M. Brig Expires: July 29, 2018 M. Brig
Aegis BMD Program Office Aegis BMD Program Office
A. Jonasson A. Jonasson
Swedish Defence Material Administration (FMV) Swedish Defence Material Administration (FMV)
January 25, 2018 January 25, 2018
PIM Flooding Mechanism and Source Discovery PIM Flooding Mechanism and Source Discovery
draft-ietf-pim-source-discovery-bsr-09 draft-ietf-pim-source-discovery-bsr-10
Abstract Abstract
PIM Sparse-Mode (PIM-SM) uses a Rendezvous Point (RP) and shared PIM Sparse-Mode (PIM-SM) uses a Rendezvous Point (RP) and shared
trees to forward multicast packets from new sources. Once last hop trees to forward multicast packets from new sources. Once last hop
routers receive packets from a new source, they may join the Shortest routers receive packets from a new source, they may join the Shortest
Path Tree for the source for optimal forwarding. This draft defines Path Tree for the source for optimal forwarding. This draft defines
a new mechanism that provides a way to support PIM-SM without the a new mechanism that provides a way to support PIM-SM without the
need for PIM registers, RPs or shared trees. Multicast source need for PIM registers, RPs or shared trees. Multicast source
information is flooded throughout the multicast domain using a new information is flooded throughout the multicast domain using a new
skipping to change at page 15, line 36 skipping to change at page 15, line 36
Type Name Reference Type Name Reference
-------------------------------------------------- --------------------------------------------------
0 Reserved [this document] 0 Reserved [this document]
1 Source Group Holdtime [this document] 1 Source Group Holdtime [this document]
2-32767 Unassigned 2-32767 Unassigned
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Arjen Boers for contributing to the The authors would like to thank Arjen Boers for contributing to the
initial idea, and Stewart Bryant, Yiqun Cai, Toerless Eckert, Dino initial idea, and David Black, Stewart Bryant, Yiqun Cai, Toerless
Farinacci, Alvaro Retana and Liang Xia for their very helpful Eckert, Dino Farinacci, Alvaro Retana and Liang Xia for their very
comments on the draft. helpful comments on the draft.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
 End of changes. 2 change blocks. 
4 lines changed or deleted 4 lines changed or added

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