In this paper, we provide a detailed and comprehensive survey of the AC mechanisms in NDN. To date, considerable efforts have been made to develop various AC mechanisms in NDN. This phenomenon leads to the loss of control over the content causing different challenges for the realization of efficient AC mechanisms. In contrast, ICN-based networks use content names to drive communication and decouple the content from its original location. In TCP/IP-based AC systems, due to the client-server communication model, the servers control which client can access a particular content. Among other security aspects, Access Control (AC) rules specify the privileges for the entities that can access the content. NDN provides intrinsic content security where security is directly provided to the content instead of communication channel. Named Data Networking (NDN) is one of the most recent and active ICN architectures that provides a clean slate approach for Internet communication. Information-Centric Networking (ICN) has recently emerged as a prominent candidate for the Future Internet Architecture (FIA) that addresses existing issues with the host-centric communication model of the current TCP/IP-based Internet.
We have implemented the RoundSync protocol, conducted preliminary evaluation through simulations, as well as performed comparative study of the RoundSync design with other NDN dataset synchronization solutions that have been developed so far.
CHRONOSYNC SLOW WHEN LOCKED UPDATE
RoundSync splits data publications into “rounds” and uses two separate Interest types for state inconsistency detection and update retrieval. In this report, we first use a simple case study to analyze the behavior of ChronoSync under simultaneous data publications, and then introduce RoundSync, a revision to ChronoSync to fix the overloading problem. This problem is caused by a semantic overloading on Sync Interests: a Sync Interest is used both to detect state inconsistency (by embedding the dataset state digest in the Interest name) and to retrieve update (resulting in the update being named under a specific digest). However, when multiple nodes in the same sync group publish new data simultaneously, ChronoSync needs to either use exclude mechanism to fetch the simultaneously produced data, or fall back to a recovery mechanism.
Distributed dataset synchronization (Sync in short) implemented by ChronoSync allows a group of nodes to operate on a shared dataset with eventual consistency.
0 kommentar(er)
