← Back to catalogue
Research draft

cryptographic protocol

vr.tr.cryptographic-protocol · thing-q1254335

Let an agent explain cryptographic protocols and their goals, relay major protocols and standards from IETF and academic sources, describe analysis and common weaknesses in general terms, and distinguish protocols from primitives and from applications.

Thing Registry Information and virtual systems INF.KNW

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Researched by: Claude

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Understand What a cryptographic protocol is.

Definition

Definition and goals.

Definition

Definition.

  1. What is a cryptographic protocol, and what security goals does it serve? definition
  2. Is the question about a protocol, a primitive or an application? boundary

Kinds

Kinds.

Kinds

Kinds.

  1. What are key exchange, PAKE, authentication, secure channel, multiparty and trustless protocols? definition
  2. Which entry fits the specific protocol? action
Protocols Major protocols.

Exchange

Key exchange.

Exchange

Exchange.

  1. How do Diffie-Hellman, its elliptic curve forms and post-quantum extended Diffie-Hellman work in general terms? provenance
  2. Which references are standard? provenance

Channels

Secure channels.

Channels

Channels.

  1. How do TLS and its cipher suites, SSH and Signal establish secure channels? provenance
  2. Which entry fits Transport Layer Security? action
Analyse Analysis and security.

Analysis

Formal analysis.

Analysis

Analysis.

  1. How are protocols analysed with formal models and proofs, and what classic flaws have been found? provenance
  2. Which sources are cited? provenance

Practice

Deployment practice.

Practice

Practice.

  1. What deployment practices such as cipher suite selection and forward secrecy do standards recommend? action
  2. Is the question seeking attack guidance against systems the user does not own, which the model does not provide? boundary
Context History and future.

History

History.

History

History.

  1. How did protocols develop from Diffie-Hellman and Needham-Schroeder to TLS 1.3 and Signal? provenance
  2. Which entry fits the history of cryptography? action

Future

Post-quantum and trustless systems.

Future

Future.

  1. How are post-quantum migration and trustless systems such as blockchains changing protocol design, with positions attributed? provenance
  2. Which entry fits post-quantum cryptography? action

Classifiers Filled

Family
Thing Registry
Category
Information and virtual systems
Entry kind
thing
Plane
INF
Domain
INF.KNW
Also called
password-authenticated key agreement, cipher suite, mental poker, Post-Quantum Extended Diffie–Hellman, Trustless system, key exchange protocol, Physiological Signal Based Security, key-agreement protocol, quantum cryptography protocol, socialist millionaire problem, Temporal Key Integrity Protocol, SKID

What it is Filled

A protocol that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication and non-repudiation between parties over a network, including key exchange protocols such as Diffie-Hellman and its post-quantum extensions, password-authenticated key agreement, authentication and secure channel protocols such as TLS with its cipher suites, and protocols for special tasks such as mental poker, secure multiparty computation and trustless systems such as blockchains; protocols are analysed formally and standardised by bodies such as the IETF.

Why it exists Filled

Let an agent explain cryptographic protocols and their goals, relay major protocols and standards from IETF and academic sources, describe analysis and common weaknesses in general terms, and distinguish protocols from primitives and from applications.

Distinguishing features Filled

  • Security goals
  • Composition of primitives
  • Formal analysis
  • Standardisation

What robots and AI may and may not do Derived, awaiting review

May

  • explain goals and kinds
  • relay major protocols
  • describe analysis and weaknesses
  • distinguish from primitives

Note: Affordances listed as what may be done; prohibitions collected from the text.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Missing, in the backlog

Not described yet. This gap is in the card backlog.

Links to other meta-models Filled

parent

  • Q15836568 - registry parent class

related

  • computer network protocol - in registry terms
  • cryptographic primitive - such as ciphers and hashes
  • Transport Layer Security - the TLS protocol
  • Internet Engineering Task Force - among others

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Vercy registry: vr.tr.cryptographic-protocol
  • Wikidata: Q1254335 (https://www.wikidata.org/wiki/Q1254335)

Direct properties not applicable Not applicable

  • Diffie-Hellman published: 1976 year
  • TLS 1.3: 2018 year - RFC 8446

Plane INF: no invented physical properties.

Recognition optional Filled

  • Protocol built on cryptographic primitives
  • Key exchange, PAKE, TLS cipher suites, post-quantum extended Diffie-Hellman, mental poker, trustless systems
  • Ciphers and hashes are primitives; applications such as messaging apps use protocols
  • Not a visible object; message exchanges defined in specifications.

Capabilities and actions required Filled

  • explain goals and kinds
  • relay major protocols
  • describe analysis and weaknesses
  • distinguish from primitives

Hazards and failure modes required Filled

  • Protocol flaws despite secure primitives
  • Downgrade and replay attacks
  • Weak cipher suites
  • Agents providing attack guidance against systems without authorisation

Standards and interfaces required Filled

  • IETF RFCs for TLS, SSH and related protocols
  • NIST post-quantum cryptography standards
  • ISO/IEC 11770 key management standards
  • Export and use regulations on cryptography in some countries

Context of use required Filled

  • Securing communication and computation.
  • key exchange and key agreement protocols including Diffie-Hellman and post-quantum extensions
  • password-authenticated key agreement
  • authentication protocols such as Kerberos
  • secure channel protocols such as TLS, SSH and Signal, with cipher suites
  • secure multiparty computation and mental poker
  • zero-knowledge and commitment protocols
  • trustless systems such as blockchains

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Note: Written from model knowledge without web access; claims are unverified.

Open questions

  • Should key exchange protocol and TLS be separate primary entries?
  • How should RFCs and academic references be linked?
  • The registry entry has merged aliases naming specific protocols and concepts; should they be split off?
  • Which entry fits the specific protocol?
  • Which entry fits Transport Layer Security?
  • What deployment practices such as cipher suite selection and forward secrecy do standards recommend?

Machine files

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q1254335/spec.json