Abstract
In Named Data Networking (NDN), where every data packet requires a cryptographic signature, the initial "bootstrapping" of security credentials for new entities presents a significant challenge. This paper introduces Trust-domain Entity Bootstrapping (TEB), a systematic model that unifies how new devices and users securely join an NDN environment. By decomposing the complex process of obtaining initial security credentials into four modular steps, the authors provide a framework for analyzing existing protocols and a blueprint for designing robust, interoperable security for future networks.
Introduction
Security in NDN is intrinsic; every piece of data must be signed. However, this creates a "chicken and egg" problem: how does a brand-new device obtain its first certificate and establish trust with the network authority before it possesses any credentials? This process, known as security bootstrapping, is critical for network integrity.
While various solutions have been proposed—ranging from QR codes to physical vibrations—they are often developed in isolation. The lack of a formal, generalized model makes it difficult for developers to compare methods, reuse code, or ensure comprehensive security coverage. The TEB model addresses this gap by providing a universal language for NDN security onboarding.
The TEB Model
The authors define security bootstrapping within a "trust domain"—a group of entities under a single administrative authority, such as a smart home or corporate network. The TEB model decomposes the bootstrapping process into four distinct functional procedures:
- Mutual Authentication: The new entity ($E_{new}$) and the Trust Domain Controller verify each other's identity.
- Establishing Trust Relations: The entity installs the "Trust Anchor" (root of trust) and the "Trust Schema" (the rules governing signing authority).
- Naming: The controller assigns the entity a unique, semantically meaningful NDN name.
- Certification: The controller (or a delegated issuer) provides a digital certificate binding the entity's public key to its new name.
Dataflow and Dependencies
A key contribution of the paper is the TEB Dataflow Graph, which maps the logical dependencies between these steps. It illustrates how "Proof of Authority" (POA) and "Proof of Membership" (POM) are established through authentication and trust relation steps, eventually leading to a "Proof of Possession" (POP) of a name and the final certification.
This decoupling of Naming from Certification is particularly powerful. It allows a network to approve a device's name before the final certificate is generated, enhancing modularity. Furthermore, the model supports the concept of "elemental entities," where a main controller can delegate authentication and naming to a local hub while retaining final certificate issuance authority.
Evaluation and Results
The TEB model's expressiveness and sufficiency were evaluated by "reverse-engineering" five diverse, real-world NDN bootstrapping protocols: SSP (QR-code-based), NDN Testbed (email-based), NDNViber (proximity-based), PION (password-based), and DCT (manual toolkit).
The authors successfully mapped all five protocols onto the TEB framework without losing functional detail. For instance, while NDNViber and PION use different authentication mechanisms (vibrations vs. passwords), both follow the same logical flow to reach certification. This demonstrates that TEB can serve as a universal architectural language.
Conclusion and Future Work
The TEB model provides a much-needed formalization of security bootstrapping in NDN. While it successfully models intra-domain processes, future work is needed to address inter-domain bootstrapping—how separate trust domains establish mutual trust. Additionally, challenges remain regarding the secure storage of credentials and the automated execution of trust policies to hide cryptographic complexity from end-users.
Summary updated