-
Notifications
You must be signed in to change notification settings - Fork 2
Data Naming
Jerry Yuan edited this page May 28, 2022
·
1 revision
- Name:
/<prefix>/KEY/<key-id>/<issuer-info>/<version>
- e.g.
/ndn/siteA/depart/cs/KEY /223/alice/001
- Certificate owner:
/ndn /siteA/depart/cs
- Key ID: 223
- Certificate owner:
Revocation record is a Data packet
- Name:
/<prefix>/REVOKE/<keyid>/<issuer>/<version>/<publisher>
-
<publisher> = <issuer>
, if this record is produced by certificate issuer -
<publisher> = self
, if this record is produced by certificate owner itself
-
- Content Type: BLOB
- Content Payload:
- Revocation Timestamp: The timestamp of this revocation event
- Key Hash: The public key hash of the corresponding certificate
- Revocation Reason
- Signature:
- Signed by the corresponding certificate issuer, or certificate owner
Applications express Interest to query the certificate status
- Name:
/<prefix>/REVOKE/<keyid>/<issuer>/<version>
- CanBePrefix, forwarding hint:
/<ledger prefix>
- Query for specific revocation record:
/<prefix>/REVOKE/<keyid>/<issuer>/<version>/<publisher>
- CanBePrefix, forwarding hint:
If no corresponding record as queried, an application layer NACK is returned
- Name:
/<prefix>/REVOKE/<keyid>/<issuer>/<version>/nack/<timestamp>
- or
/<prefix>/REVOKE/<keyid>/<issuer>/<version>/<publisher>/nack/<timestamp>
, depending on the received interest
- or
- Content Type: NACK
- NO Content Payload
- Signature:
- Signature: signed by ledger instances