Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added reference to Sandoche paper; but not sure where to reference it #70

Merged
merged 2 commits into from
Jan 22, 2025
Merged

added reference to Sandoche paper; but not sure where to reference it #70

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
179f02e
added reference to Sandoche paper; but not sure where to reference it
mcr Sep 16, 2024
7ea6059
Merge branch 'main' into cite-afnic-paper
hardaker Jan 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions draft-ietf-dance-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,8 @@ author:
normative:

informative:
pkiiot: DOI.10.1109/PKIA56009.2022.9952253

slowloris:
target: "https://en.wikipedia.org/wiki/Slowloris_(computer_security)"
title: "Slowloris Attack"
Expand Down Expand Up @@ -96,8 +98,7 @@ A first-class identity is an application-independent identity.

**How to DANCE with ENTITY:** This architecture document delegates many details of how DANCE can be used with some specific protocol to a document with the name "How to DANCE with _entity_".

**Identity provisioning:** This refers to the set of tasks required to securely provision an asymmetric key pair for the device, sign the certificate (if the public credential is not simply a raw public key), and publish the public key or certificate in DNS.
These steps may not be performed by the same party or organization. Examples:
**Identity provisioning:** This refers to the set of tasks required to securely provision an asymmetric key pair for the device, sign the certificate (if the public credential is not simply a raw public key), and publish the public key or certificate in DNS. These steps may not be performed by the same party or organization. Examples:

- A device manufacturer may instantiate the key pair, and a systems integrator may be
responsible for issuing (and publishing) the device certificate in DNS.
Expand Down
Loading