Abstract: Techniques are described for prioritized establishment of communication sessions. In one example, a network device parses a configuration file that defines a plurality of communication sessions of a routing protocol and includes priority values assigned to the communication sessions. The network device creates two or more lists of communication sessions for two or more of the priority values based on the configuration file, wherein each list of the two or more lists is created for a particular priority value of the priority values and defines one or more communication sessions of the plurality of communication sessions that are assigned the particular priority value. The network device then establishes the one or more communication sessions included in each list of the two or more lists according to an ordering based on the priority values associated with the two or more lists.

Abstract: Techniques are described for prioritized establishment of communication sessions. In one example, a network device parses a configuration file that defines a plurality of communication sessions of a routing protocol and includes priority values assigned to the communication sessions. The network device creates two or more lists of communication sessions for two or more of the priority values based on the configuration file, wherein each list of the two or more lists is created for a particular priority value of the priority values and defines one or more communication sessions of the plurality of communication sessions that are assigned the particular priority value. The network device then establishes the one or more communication sessions included in each list of the two or more lists according to an ordering based on the priority values associated with the two or more lists.

Abstract: Multiple Register State Machines on a rendezvous point router (“RP”) in a Protocol Independent Multicast-Sparse Mode (“PIM-SM”) domain per (S,G) is supported, thereby increasing the Register state consistency and faster convergence in case of a first hop router (“FHR”) failure. Such example embodiments may advantageously eliminate the limitation of a single Register State Machine on RP for a given (S,G), in the presence of multiple FHRs connected to the same source. At least some such example embodiments provide the capability of maintaining multiple Register State Machines on RP for a given (S,G), in a way, that maps one Register State Machine to each FHR. In this way, the RP can avoid the inconsistent FHR states and traffic losses caused due to FHR failures.

Abstract: The potential problem of traffic loss during a period when a second PIM router is elected DR after a first PIM router (on the same PIM interface) was previously elected DR and is transiting multicast traffic, is solved by (1) configuring a first interval on a PIM interface for at least the first PIM router; (2) responsive to the PIM interface of the first PIM router booting up, (i) starting, by the first PIM router, a timer corresponding to the configured first interval, (ii) determining, by the first PIM router, whether or not it is the DR on the PIM interface, (iii) upon determining that the timer has expired, redetermining, by the first PIM router, whether or not it is the DR on the PIM interface, and (iv) responsive to a redetermination that the first PIM router is the DR on the PIM interface, (A) increasing, by the first PIM router, a DR priority value of the first PIM router to reduce a likelihood that another of the at least two PIM routers will replace the first PIM router as DR, and (B) sending on th

Abstract: Techniques are described for enhancements to Protocol Independent Multicast (PIM) to enable a last hop router (LHR) to perform source discovery and directly build or join a source tree. According to the techniques of this disclosure, an LHR may be configured to receive a request to obtain multicast traffic corresponding to one or more multicast groups. The LHR may be configured to generate a source discovery join message including a request to join one or more multicast groups identified in the source discovery message and one or more source discovery flags. At least one of the one or more source discovery flags may indicate that the last hop router is interested in obtaining source information relating to at least one of the one or more multicast groups. The LHR may be configured to send, to a rendezvous point (RP) router in the network, the source discovery join message.

Abstract: An example method includes receiving, by a first hop router (FHR) and from a source device, multicast stream data associated with a multicast stream, sending, from the FHR and to a rendezvous point (RP) using a Protocol Independent Multicast (PIM) protocol, one or more null register messages that are each associated with the multicast stream. Each of the one or more null register messages includes a source address and a group address that are collectively associated with the multicast stream, and each of the one or more null register messages further includes an indication to request that the RP refrain from sending any register-stop messages associated with the multicast stream to the FHR. The example method further includes, after sending the one or more null register messages that are each associated with the multicast stream, sending, to the RP, the multicast stream data in a non-encapsulated format.

Abstract: Techniques are described for enhancements to Protocol Independent Multicast (PIM) in an Any Source Multicast (ASM) mode in order to effectively implement Multicast only Fast Re-Route (MoFRR). According to the PIM ASM mode, a router operating as a last hop router connected to a receiver may initiate establishment of both a shared tree and a shortest path tree over which to receive multicast traffic for a given multicast group. According to the disclosed techniques, the router may use the shortest path tree as a primary path on which to receive the multicast traffic, and may use the shared tree as a secondary or backup path for MoFRR in case a failure occurs on the primary path. The techniques enable the router to perform MoFRR for PIM ASM mode without pruning the multicast traffic from the shared tree, and without building additional trees as secondary paths for MoFRR.

Abstract: Techniques are described for enhancements to Protocol Independent Multicast (PIM) to enable a last hop router (LHR) to perform source discovery and directly build or join a source tree. According to the techniques of this disclosure, an LHR may be configured to receive a request to obtain multicast traffic corresponding to one or more multicast groups. The LHR may be configured to generate a source discovery join message including a request to join one or more multicast groups identified in the source discovery message and one or more source discovery flags. At least one of the one or more source discovery flags may indicate that the last hop router is interested in obtaining source information relating to at least one of the one or more multicast groups. The LHR may be configured to send, to a rendezvous point (RP) router in the network, the source discovery join message.

Abstract: An example method includes receiving, by a first hop router (FHR) and from a source device, multicast stream data associated with a multicast stream, sending, from the FHR and to a rendezvous point (RP) using a Protocol Independent Multicast (PIM) protocol, one or more null register messages that are each associated with the multicast stream. Each of the one or more null register messages includes a source address and a group address that are collectively associated with the multicast stream, and each of the one or more null register messages further includes an indication to request that the RP refrain from sending any register-stop messages associated with the multicast stream to the FHR. The example method further includes, after sending the one or more null register messages that are each associated with the multicast stream, sending, to the RP, the multicast stream data in a non-encapsulated format.

Abstract: Embodiments of the present disclosure provide systems and methods for automated chargeback processing, including hardware and software for storing, in a database, transaction data associated with one or more transactions in a queue, retrieving transaction data associated with one or more transactions stored in the queue, for each transaction in the queue, applying, using an automated chargeback processor, one or more rules to the transaction data, identifying, using the automated chargeback processor, the transaction data as eligible or ineligible for chargeback processing based on the one or more rules, determining, using the automated chargeback processor, whether additional documentation is required, and sending, via a network, instructions to perform a chargeback operation for an account associated with the transaction data.