AES-GCM with port names

Overview & Cryptographic Context

When modeling real-world security protocols such as SRTP (RFC 7714) or TLS record protection, generic port names like Plaintext and Ciphertext can obscure what protocol structure is actually flowing through each wire. NodeCrypto allows you to rename any fixed or dynamic port directly on the canvas card or in the Properties modal while keeping the underlying permanent port ID intact.

This workflow is functionally identical to AES-GCM encryption, but assigns domain-specific role names to the fixed ports of the AES Encrypt node—renaming plaintext to Packet Payload, ciphertext to Encrypted Payload, and tag to Authentication Tag—and attaches a Markdown memo explaining the SRTP nonce rules.

Pipeline Architecture & Role Port Mapping

• Permanent Port IDs Preserved: Even though the display label on port plaintext is changed to Packet Payload, the edge wiring and the CLI execution engine still reference the immutable ID plaintext. Hovering over a renamed port on the canvas displays its original ID in a tooltip (see Port Order and Renaming).
• Embedded Markdown Memo: The AES node includes a node note documenting RFC 7714 §16.1.1 and reminding reviewers never to reuse a 96-bit GCM nonce under the same key (see Node Properties Window and Memos).

Nodes & Configuration

Node reference → · Port renaming guide →

Inputs, Outputs & Test Vector Verification

Verification Source: RFC 7714 §16.1.1 (AES-128-GCM, SRTP packet)

Inputs

Expected Outputs