Content Manifest Renaming for CCN Authentication Binding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content-centric networks face challenges in efficiently redistributing digital content while maintaining authentication information, as renaming content objects breaks the binding security association between the unique name and authentication information, leading to computational overhead and authentication issues.
Innovation Solution
The method involves creating an original manifest with authentication information, encapsulating it under a new name, and creating a new manifest that includes the original authentication information, allowing content objects to be renamed without re-computing the authentication information, and enabling verification of the original producer through self-certifying names.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If content objects are renamed for redistribution, then content can be moved to different locations, but the binding security association between the unique name and authentication information is broken
Solution Approach 1:
The manifest is segmented into multiple components: original authentication information (signature, producer identity), original content name, and new content name. This segmentation allows the authentication information to be separated from the content name binding, enabling renaming while preserving security verification capability.
Solution Approach 2:
The manifest acts as an intermediary that bridges the original content name and new content name. It contains the original authentication information and enables verification by providing a mapping relationship between the old and new names, allowing security verification without direct binding to the new name.
2Adaptability or versatility
If routing information is updated to move content, then content can be redistributed, but computational overhead increases due to modifying routing tables
Solution Approach 1:
The authentication and verification logic is extracted from the routing table modification process. Instead of updating routing tables to track content movement, the system extracts the essential verification information (original authentication data and name mapping) into a manifest that travels with the content, eliminating the need for complex routing table updates.
3Ease of operation
If content is renamed without preserving authentication information, then redistribution is simplified, but the original producer cannot be authenticated
Solution Approach 1:
The manifest is created in advance with all necessary authentication information and name mapping data before the renaming operation. This preliminary preparation ensures that when content is renamed and redistributed, the verification information is already available, making the process both simple and secure without requiring post-renaming authentication setup.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
One embodiment provides a system that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information. During operation, the system determines, by a content producing device, an original manifest which indicates at least an original name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level. The system renames the content object with a new name. The system also creates a new manifest which indicates the new name, wherein the new manifest includes original authentication information associated with the original manifest.