Inclusive Language Initiative

One Gigamon, Trust, Employees First, and Collaboration: these Gigamon values require an inclusive and welcoming environment – for ourselves, our customers, our partners, and all the stakeholders with whom we interact. Our choice of language every day creates and reinforces our values, expectations, and conventions. For these reasons, Gigamon is adopting inclusive language standards and is in the process of updating all of our content to remove exclusionary language wherever it exists, whether that be in Gigamon products and documentation, public-facing marketing materials, or internal communications.

For details, see Replaced Terms in this Release. Additional changes are forthcoming to change the same terms in our product interfaces, support materials, and previously released content. Stay tuned. As we make these changes, we will announce updates to our terminology in our release notes and product documentation.

Replaced Terms in this Release

As part of the Inclusive Language Initiative, the following new terms are being adopted by Gigamon. This list is organized by the functionality they describe:

Note: Some terms may be subject to further change at a future date based on the IEEE.

Decryption	What to call the lists defining whether to decrypt or not to decrypt: ● decrypt list need to decrypt (formerly blacklist), meaning need to decrypt (formerly “blacklist”) ● no-decrypt list no need to decrypt (formerly whitelist), meaning no need to decrypt (formerly “whitelist”)
Selective Forwarding	What to call the list that gets forwarded to the network: ● forwardlist (formerly “whitelist”)
PTP (Precision Time Protocol)	What to call PTP (precision time protocol) clock nodes: These terms are used to describe the relationship of node clocks with regard to how they communicate time data to ensure clocks are synchronized throughout a network: ● Primary source leader in a bidirectional clock relationship (formerly master) = root timing reference; transmits sync info to clocks in its network segment (formerly "grandmaster") ● Source/leader leader in clustering node relationship (formerly master) = leader in a bidirectional clock relationship (formerly "master") ● Receiver/destination/follower= follower in a bidirectional clock relationship (formerly "slave")
PKI (Public Key Infrastructure)	How to describe Public Key Infrastructure: ● Root = Primary, root certificate, trust anchors (formerly “master") ● CA or Subordinate CA, depending on context = sub-node, subordinate certificate, certificate authority (formerly “master”) ● Leaf Node = leaf nodes, clients, users   See Illustration of PKI Structure for a visual representation of the inverted tree structure. Refer to the x.509 standard for additional technical details about the structure.

Illustration of PKI Structure

root (root certificate)
| sub-node  (subordinate CA)	| sub-node  (subordinate CA)	| | | leaf nodes
| | | leaf nodes (users)	| sub-node (subordinate CA)
	| | | leaf nodes (clients)