| commit | 00a4a008d4c0ec61d69832a61294010545f3f6bf | [log] [tgz] |
|---|---|---|
| author | Zhiyi Zhang <zhiyi@cs.ucla.edu> | Wed Mar 01 10:17:36 2017 -0800 |
| committer | Zhiyi Zhang <zhiyi@cs.ucla.edu> | Tue Mar 07 09:25:41 2017 -0800 |
| tree | 12f21d6d96afe1ae903b0d34ac53fb7a3445b44f | |
| parent | 0df767e964185d0ed7b10e205f5fc7c233ad9329 [diff] |
Add default constructor in CertificateRequest When fetch CertificateRequest instance from storage, we may want a default constructor to create an empty instance. Change-Id: I3be7517465fc912813282d7b40f9de3d9422cb70
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.