Abstract: A request for a transaction between a client system and a server system may be processed. The transaction may be associated with transmission of data between the client system and the server system. The data may be encrypted using a transient encryption key to form encrypted data. The transient encryption key may be a synced-clock random number configured to automatically change when a designated time interval elapses. The encrypted data may be transmitted between the client system and the server system.

Abstract: A request for a transaction between a client system and a server system may be processed. The transaction may be associated with transmission of data between the client system and the server system. The data may be encrypted using a transient encryption key to form encrypted data. The transient encryption key may be a synced-clock random number configured to automatically change when a designated time interval elapses. The encrypted data may be transmitted between the client system and the server system.

Abstract: A request for a transaction between a client system and a server system may be processed. The transaction may be associated with transmission of data between the client system and the server system. The data may be encrypted using a transient encryption key to form encrypted data. The transient encryption key may be a synced-clock random number configured to automatically change when a designated time interval elapses. The encrypted data may be transmitted between the client system and the server system.

Abstract: Techniques are disclosed for determining whether to permit distribution of a software package—for example, via an application exchange service of a cloud computer system. The computer system may calculate a risk score for the software package based on various factors, including package metadata that specifies one of a plurality of package types supported by the application exchange service. The specified package type may be indicative of an amount of developer control on the software package after distribution. Based on comparing the calculated risk score to a risk threshold, the computer system may determine whether to permit distribution of the software package via the application exchange service. Scoring software packages based on package metadata may reduce the number of packages requiring manual review, which may advantageously reduce an amount of time between package development and deployment.

Abstract: Techniques are disclosed for determining whether to permit distribution of a software package—for example, via an application exchange service of a cloud computer system. The computer system may calculate a risk score for the software package based on various factors, including package metadata that specifies one of a plurality of package types supported by the application exchange service. The specified package type may be indicative of an amount of developer control on the software package after distribution. Based on comparing the calculated risk score to a risk threshold, the computer system may determine whether to permit distribution of the software package via the application exchange service. Scoring software packages based on package metadata may reduce the number of packages requiring manual review, which may advantageously reduce an amount of time between package development and deployment.

Abstract: A request for a transaction between a client system and a server system may be processed. The transaction may be associated with transmission of data between the client system and the server system. The data may be encrypted using a transient encryption key to form encrypted data. The transient encryption key may be a synced-clock random number configured to automatically change when a designated time interval elapses. The encrypted data may be transmitted between the client system and the server system.

Abstract: A method for multicast routing may include receiving, at a router of a receiving multicast domain, a data packet from a forwarding multicast domain. The method may further include configuring the router to operate as if a multicast forwarding information base entry is directly connected, and configuring the router with a reverse path forwarding override with source discovery such that a path used by multicast traffic is different from a path used for unicast traffic.

Abstract: A method for multicast routing may include receiving, at a router of a receiving multicast domain, a data packet from a forwarding multicast domain. The method may further include configuring the router to operate as if a multicast forwarding information base entry is directly connected, and configuring the router with a reverse path forwarding override with source discovery such that a path used by multicast traffic is different from a path used for unicast traffic.

Abstract: A method for multicast routing may include receiving, at a router of a receiving multicast domain, a data packet from a forwarding multicast domain. The method may further include configuring the router to operate as if a multicast forwarding information base entry is directly connected, and configuring the router with a reverse path forwarding override with source discovery such that a path used by multicast traffic is different from a path used for unicast traffic.

Abstract: A system and method for real-time detection, identification, and reporting of mac-sync failures in distributed trunking (DT) are disclosed. In one example, a mac-sync failure between a pair of communicatively coupled DT switches is detected in real-time. Further, a type of mac-sync failure between the pair of DT switches is dynamically identified upon detecting the mac-sync failure. Furthermore, an information technology (IT) admin is dynamically notified about the type of mac-sync failure between the pair of DT switches.

Abstract: Provided is a method of source discovery for non-flooding multicast using OpenFlow. A data packet is received from a source address on a network device. The data packet is routed from the network device to an OpenFlow controller. The OpenFlow controller identifies a rendezvous point (RP) of the network device, maps a random address to the source address in a port used for connecting with the rendezvous point (RP), generates a flow message containing a rule for handling the data packet, transmits the flow message to the network device and adds a flow entry in the network device based on the rule for handling the data packet.

Abstract: Provided is a method of source discovery for non-flooding multicast using OpenFlow. A data packet is received from a source address on a network device. The data packet is routed from the network device to an OpenFlow controller. The OpenFlow controller identifies a rendezvous point (RP) of the network device, maps a random address to the source address in a port used for connecting with the rendezvous point (RP), generates a flow message containing a rule for handling the data packet, transmits the flow message to the network device and adds a flow entry in the network device based on the rule for handling the data packet.

Abstract: A method for multicast routing may include receiving, at a router of a receiving multicast domain, a data packet from a forwarding multicast domain. The method may further include configuring the router to operate as if a multicast forwarding information base entry is directly connected, and configuring the router with a reverse path forwarding override with source discovery such that a path used by multicast traffic is different from a path used for unicast traffic.