commit | 36706835c62c85ddb010bc38205f890a5b8a746f | [log] [tgz] |
---|---|---|
author | Zhiyi Zhang <zhiyi@cs.ucla.edu> | Thu Jul 04 21:33:03 2019 -0700 |
committer | Zhiyi Zhang <zhiyi@cs.ucla.edu> | Thu Oct 03 12:49:15 2019 -0700 |
tree | c1a88007fdcafdd434b06b280965e5905d606200 | |
parent | 2546462fcdc833c7964a9d71340b71e187207e59 [diff] |
Fixed several ndncert-client bugs and use lower case Challenge ID refs: #4962 Change-Id: Id10dcc15cb718d6a55f4657884b2c6be3f653867
NDN certificate management protocol (NDNCERT) enables automatic certificate management in NDN. In Named Data Networking (NDN), every entity should have corresponding identity (namespace) and the corresponding certificate for this namespace. Moreover, entities need simple mechanisms to manage sub-identities and their certificates. NDNCERT provides flexible mechanisms to request certificate from a certificate authority(CA) and, as soon as certificate is obtained, mechanisms to issue and manage certificates in the designated namespace. Note that NDNCERT does not impose any specific trust model or trust anchors. While the primary use case of the developed protocol is to manage NDN testbed certificates, it can be used with any other set of global and local trust anchors.
This specification provides details and packet formats to request certificates, create certificates after one of the validation mechanism, and how the issued certificate is retrieved by the original requester.
See our GitHub wiki for more details.