Routable Prefix Queries for Privacy in Content Centric Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Content Centric Networks (CCNs), consumers face challenges in determining the minimum number of cleartext name components required to route interests to content producers while maintaining privacy, as existing CCN routing protocols do not effectively address this issue.
Innovation Solution
A system that generates queries for indices to determine the minimum routable prefix within a hierarchically structured variable length identifier, allowing consumers to encrypt sufficient name components for secure communication, and facilitates the transmission of interests with a cleartext routable prefix and encrypted suffix to content producers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Object-affected harmful factors
If a consumer encrypts the interest name to protect privacy, then privacy protection is improved, but routing capability deteriorates because sufficient name components must remain unencrypted
Solution Approach 1:
The interest name is segmented into two distinct parts: a routable prefix that remains unencrypted for routing purposes, and a suffix that is encrypted for privacy protection. This segmentation allows the system to simultaneously achieve both routing capability and privacy protection by treating different parts of the name differently.
Solution Approach 2:
Different parts of the interest name are assigned different security properties: the prefix is kept in cleartext with high accessibility for routing, while the suffix is encrypted with restricted accessibility for privacy protection. This local differentiation of quality allows simultaneous optimization of routing efficiency and privacy protection.
2Reliability
If existing CCN routing protocols are used, then routing functionality is maintained, but the ability to determine minimum routable prefix deteriorates
Solution Approach 1:
The system performs preliminary actions by establishing a query mechanism that allows consumers to determine the minimum routable prefix before constructing and sending encrypted interests. This preliminary determination of the required prefix length simplifies the subsequent encryption process and ensures routing capability is maintained.
Solution Approach 2:
A query mechanism acts as an intermediary between the consumer and the routing system, allowing the consumer to obtain information about the minimum routable prefix without having full visibility into the routing protocol internals. This intermediary simplifies the consumer's task while maintaining routing functionality.
Data Source
AI summary
One embodiment provides a system that facilitates routable prefix queries in a CCN. During operation, the system generates, by a client computing device, a query for one or more indices based on a name for an interest, wherein a name is a hierarchically structured variable length identifier that includes contiguous name components ordered from a most general level to a most specific level. An index indicates a number of the contiguous name components beginning from the most general level that represent a routable prefix needed to route the interest to a content producing device that can satisfy the interest. In response to the query, the system receives the one or more indices, which allows the client computing device to determine a remaining number of name components of the interest name which can be encrypted, thereby facilitating protection of private communication in a content centric network.