RFC 3488:Cisco Systems Router-port G...
RFC-Ref

router


Click on the red underlined text to get to the source

... multicast traffic to ports where at least one multicast router is connected. It must instead flood multicast traffic to these ports ...
... through IGMP which traffic flows need to be received by router ports to be routed because routers ...
... router ports to be routed because routers do not report these flows via IGMP. ...
... IGMP. In situations where multiple multicast routers are connected to a switched backbone, IGMP ...
... In switched backbone networks or exchange points, where predominantly routers are connected with each other, a large amount of multicast traffic may lead to unexpected congestion. It also leads to more ...
... multicast traffic may lead to unexpected congestion. It also leads to more resource consumption in the routers because they must discard the unwanted multicast traffic. ...
... The RGMP protocol described in this document restricts multicast traffic to router ports. To effectively restrict traffic, it must be ...
... traffic, it must be supported by both the switches and the routers in the network. ...
... address has been assigned by IANA to carry messages from routers to switches [3 ...
... For this reason, RGMP only supports a single RGMP enabled router to be connected directly to a port of an RGMP ...
... switch. Such a topology should be customary when connecting routers to backbone switches ...
... There are four types of RGMP messages of concern to the router-switch interaction. The type codes are defined to be the highest values in an octet to avoid the re-use of already assigned ...
... RGMP messages are sent by routers to switches. The source IPv4 address of an RGMP ...
... interface IPv4 address of the originating router. The destination IPv4 address of an RGMP ...


... RGMP Router side Protocol Description ...
... groups are desired at each of their ports. Multicast routers use RGMP to pass such information to the switches ...
... RGMP to pass such information to the switches. Only routers send RGMP messages. They ignore received RGMP ...
... RGMP messages. A Router enabled for RGMP on an interface periodically [Hello ...
... indicate that it is RGMP enabled. When RGMP is disabled on a routers interface, it will send out an RGMP ...
... When an interface is RGMP enabled, a router sends an RGMP Join message out through this interface ...
... receive traffic for from the interface. The router needs to periodically [Join Interval] re-send an RGMP ...
... multicast traffic. Routers supporting RGMP MUST NOT send RGMP Join ...
... 3]. When a router no longer needs to receive traffic for a particular group ...
... RGMP Leave message for the group. For robustness, the router MAY send more than one such message. If IPv4 ...
... multicast packets for an undesired group are received at a router from a switch, the router MAY send a RGMP ...
... router from a switch, the router MAY send a RGMP Leave message for that group ...
... switch. These messages are called data-triggered RGMP Leave messages and the router SHOULD rate-limit them. The router MAY suppress sending a data triggered RGMP ...
... RGMP Leave messages and the router SHOULD rate-limit them. The router MAY suppress sending a data triggered RGMP Leave message if it has a desired group ...
... deployment of RGMP is one RGMP enabled router directly connected to a port on a switch ...
... By default, connecting two or more RGMP enabled routers to a switch port ...
... IPv4 multicast traffic towards these routers. Black holing occurs when a RGMP Leave is received from one router ...
... routers. Black holing occurs when a RGMP Leave is received from one router while the other router is still joined. ...
... RGMP Leave is received from one router while the other router is still joined. This malfunction is not only easily recognized by the actual users ...
... This malfunction is not only easily recognized by the actual users connected through the routers, but it also adheres to the principle that a failure situation causes less traffic than more. Reverting to ...
... correlated with the cause anymore. Because routers supporting RGMP are not required to send RGMP Join ...
... switch SHOULD recognize a port connected to a router by other appropriate protocol packets or dedicated IPv4 multicast router discovery ...
... router by other appropriate protocol packets or dedicated IPv4 multicast router discovery mechanisms such as MRDISC [11]. The manual configuration ...
... [11]. The manual configuration is required to support routers not supporting PIM or other methods ...


... links within a network if at least one router is connected to each of the switches. ...
... switch on the other end will only recognize the port as a router port via the PIM Hello ...
... links may be required if non-PIM routers are being used, depending on the other capabilities of the switch. ...
... ports to make it look like an RGMP enabled router to a potential switch at the other end of the link ...
... Interoperability with RGMP-incapable routers ...
... traffic restriction is applied there only. RGMP-incapable routers will receive multicast traffic for all multicast groups ...
... a few known restrictions. A router running RGMP on a switched network will not receive traffic ...
... network with RGMP enabled routers. In Bidir-PIM ...
... In Bidir-PIM, a router elected to be the DF must not be enabled for RGMP ...
... traffic received from the network towards the RP. If a router is not the DF for any group ...
... directly connected sources can be supported with RGMP enabled routers. Both in PIM-SM ...
... PIM-SSM, upstream routers forwarding traffic into the switched network ...


... Hello messages sent by an RGMP-enabled router to an RGMP-enabled switch. Default: 60 ...
... Join messages sent by an RGMP-enabled router to an RGMP-enabled switch for a given ...


... ports are dedicatedly connected to one system which acts as an RGMP capable router. This is also the recommended configuration to best leverage the benefits of the RGMP protocol ...
... multicast data towards a non-RGMP enabled router on the same port. This effectively introduces a blackholing DoS attack ...
... affect a port if there officially is only one RGMP enabled router connected to it (i.e., if the port is RGMP ...
... port only if there officially is only one RGMP enabled router connected to it (i.e., if the port is RGMP ...


... Biswas, S., Cain, B. and B. Haberman, "IGMP Multicast Router Discovery", Work In Progress. ...


... RGMP for the purpose of constraining multicast traffic towards router ports. This appendix will explain the motivation not to rely on ...
... GARP/GMRP messages. In RGMP, routers only need to send RGMP messages and switches ...
... IGMP (version 2) and is as such easy to add to router and switch platforms that already support IGMP ...
... o GARP/GMRP supports more than one system (host/router) on a switch port ...
... port which is one reason for its complexity. In RGMP, this configuration is explicitly not supported: More than one router per switched port is not only not a common scenario in today's ...
... IPv4 multicast traffic is to be kept away from routers. o GARP ...
... switches can easily be the aggregate required bandwidth to routers on either sides. For this reason, inter-switch bandwidth ...
... over provisioned. In addition, the likelihood for receiving routers to be only on the sources side of an inter-switch link is in general deployments ...


... PIM-SSM, it does not have explicit messages for the router to selectively join to (S,G) channels individually. ...
... join to (S,G) channels individually. Instead the router must RGMP join to all (Si,G) channels ...
... snooping. o Support for multiple routers per port ...
... As discussed in Appendix B. This is probably one extension that should be avoided. Multiple RGMP router per port are inappropriate for efficient multicast traffic ...
... DVMRP or Bidir-PIM DF routers, additional RGMP messages may be added to allow routers ...
... routers, additional RGMP messages may be added to allow routers to indicate that certain group (ranges ...
... Multicast Exchange Points (MIXes) environments situations exist where different downstream routers for policy reasons need to receive the same traffic flow from different upstream ...
... receive the same traffic flow from different upstream routers. This problem could be solved by actually providing an upstream ...
... then forward traffic from one upstream router only to those downstream routers ...
... router only to those downstream routers who want to have the traffic from exactly this upstream ...
... traffic from exactly this upstream router. This extension would best go in hand with changes to the layer 3 routing protocol ...
... changes to the layer 3 routing protocol run between the routers. As previously mentioned, RGMP ...
... IPv4 routing protocol run between routers in a switched LAN. ...



Google
Web
RFC-Ref