| commit | 7ed6204f927d5a26c1c12010028c755cbd8edb24 | [log] [tgz] |
|---|---|---|
| author | Ashlesh Gawande <agawande@memphis.edu> | Sun May 28 13:42:34 2017 +0000 |
| committer | Junxiao Shi <sunnylandh@gmail.com> | Thu Jun 01 17:28:44 2017 -0700 |
| tree | e438159d7b03d0bed1580424bbfcdbcc19b8a03a | |
| parent | 7c06803d0b2f7ef7a9de0825b267f4e22dbcbbf5 [diff] |
ci: recompile ndn-cxx after Boost upgrade on macOS refs #3321 Change-Id: Ibac137688a5720b7a7a8b51f1ac756b892e2f68a
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.