A Reliable Transport Mechanism for PIM
RFC 6559
Document | Type |
RFC - Experimental
(March 2012; No errata)
Was draft-ietf-pim-port (pim WG)
|
|
---|---|---|---|
Authors | Dino Farinacci , IJsbrand Wijnands , Stig Venaas , Maria Napierala | ||
Last updated | 2015-10-14 | ||
Replaces | draft-farinacci-pim-port | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 6559 (Experimental) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Adrian Farrel | ||
IESG note | Mike McBride (mmcbride7@gmail.com) is the document shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) D. Farinacci Request for Comments: 6559 IJ. Wijnands Category: Experimental S. Venaas ISSN: 2070-1721 Cisco Systems M. Napierala AT&T Labs March 2012 A Reliable Transport Mechanism for PIM Abstract This document defines a reliable transport mechanism for the PIM protocol for transmission of Join/Prune messages. This eliminates the need for periodic Join/Prune message transmission and processing. The reliable transport mechanism can use either TCP or SCTP as the transport protocol. Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation. This document defines an Experimental Protocol for the Internet community. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6559. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must Farinacci, et al. Experimental [Page 1] RFC 6559 A Reliable Transport Mechanism for PIM March 2012 include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Notation . . . . . . . . . . . . . . . . . . 4 1.2. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 5 3. PIM Hello Options . . . . . . . . . . . . . . . . . . . . . . 6 3.1. PIM over the TCP Transport Protocol . . . . . . . . . . . 6 3.2. PIM over the SCTP Transport Protocol . . . . . . . . . . . 7 3.3. Interface ID . . . . . . . . . . . . . . . . . . . . . . . 8 4. Establishing Transport Connections . . . . . . . . . . . . . . 9 4.1. Connection Security . . . . . . . . . . . . . . . . . . . 11 4.2. Connection Maintenance . . . . . . . . . . . . . . . . . . 11 4.3. Actions When a Connection Goes Down . . . . . . . . . . . 13 4.4. Moving from PORT to Datagram Mode . . . . . . . . . . . . 14 4.5. On-Demand versus Pre-Configured Connections . . . . . . . 14 4.6. Possible Hello Suppression Considerations . . . . . . . . 15 4.7. Avoiding a Pair of TCP Connections between Neighbors . . . 15 5. PORT Message Definitions . . . . . . . . . . . . . . . . . . . 16 5.1. PORT Join/Prune Message . . . . . . . . . . . . . . . . . 18 5.2. PORT Keep-Alive Message . . . . . . . . . . . . . . . . . 19 5.3. PORT Options . . . . . . . . . . . . . . . . . . . . . . . 20 5.3.1. PIM IPv4 Join/Prune Option . . . . . . . . . . . . . . 21 5.3.2. PIM IPv6 Join/Prune Option . . . . . . . . . . . . . . 21 6. Explicit Tracking . . . . . . . . . . . . . . . . . . . . . . 22 7. Support of Multiple Address Families . . . . . . . . . . . . . 23 8. Miscellany . . . . . . . . . . . . . . . . . . . . . . . . . . 23 9. Transport Considerations . . . . . . . . . . . . . . . . . . . 23 10. Manageability Considerations . . . . . . . . . . . . . . . . . 24 11. Security Considerations . . . . . . . . . . . . . . . . . . . 25 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 12.1. PORT Port Number . . . . . . . . . . . . . . . . . . . . . 25 12.2. PORT Hello Options . . . . . . . . . . . . . . . . . . . . 25 12.3. PORT Message Type Registry . . . . . . . . . . . . . . . . 26 12.4. PORT Option Type Registry . . . . . . . . . . . . . . . . 26 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 26Show full document text