Skip to content

Commit 8e7dc37

Browse files
committed
Document term mapping
1 parent e68205d commit 8e7dc37

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

docs/protocol-guide.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,6 +164,20 @@ These lines are not intended to represent single-hop point-to-point physical con
164164
Instead they represent potentially multi-hop IP connectivity between the network nodes; each link
165165
may contain multiple switch or router hops.
166166

167+
### DSKE vs ETSI terminology
168+
169+
The DSKE IETF draft and arXiv papers use different terminology than the European Telecommunications
170+
Standardization Institute (ETSI).
171+
The following table shows how the different terminologies map to each other:
172+
173+
| DSKE term | ETSI term |
174+
|---|---|
175+
| Client <br> DSKE Client <br> DSKE Client Node | Key Management Entity (KME) |
176+
| Hub <br> Security Hub <br> DSKE Security Hub | Trusted Relay Node (TRN) [1] |
177+
| Encryptor | Secure Application Entity (SAE) |
178+
179+
[1] Note that ETSI does not have the concept of a Trusted Relay Node splitting a key into shares.
180+
167181
## High-level overview
168182

169183
We start with a high-level overview of how the protocol works.

0 commit comments

Comments
 (0)