question string | answer string | rating int64 |
|---|---|---|
What is the title of the NDN technical report discussed in the text? | NDN Technical Report NDN-0073. | 9 |
What is the primary purpose of the State Vector Sync (SVS) protocol according to the text? | To synchronize the data names of a shared dataset among a group of participants in Named Data Networking (NDN). | 8 |
What is the limitation of using digests in dataset synchronization? | Digests do not indicate whether the local or remote dataset is newer or exactly which data item caused the difference. | 8 |
How does sequential naming in ChronoSync simplify dataset reconciliation? | It allows inferring all data items' names via participant-specific prefixes and sequence numbers, enabling a simpler recovery mechanism than walking the name tree. | 8 |
What is the main difference between VectorSync and DSSN? | DSSN changed the vector format from a list of sequence numbers to a list of [participant-prefix, seq#]-tuples. | 8 |
What does SVS inherit from DSSN? | SVS inherits DSSN’s State Vector encoding of sync interests. | 8 |
What is the example name structure for data items in the text? | /ucla/alice/111/ucla/bob/129/usc/ted/112/ucla/alice/112/ucla/bob/130/usc/ted/113/ucla/alice/113/ucla/bob/131/usc/ted/114.........Shared Dataset/ucla/alice: 113/ucla/bob: 131/usc/ted: 114]StateVector/<grp-prefix>/<state-vector>/<signature>/<publishing-prefix>/<grp-prefix>/<seq-no>/ucla/cs/irl/chatroom/[/ucla/alice: 10, ...... | 8 |
What are the two conditions under which a member of a sync group sends a sync interest? | i) event driven, i.e., the node identifies a new dataset state change, or receives a sync interest with obsolete dataset state; and ii) time driven, i.e., periodically, in the absence of event-driven sync interest generation. | 8 |
Exact question text | Exact answer text | 8 |
What action does P take if the received sync interest 𝐼𝑟𝑒𝑐𝑣 is identical to its local dataset state? | P resets its periodic sync interest transmission timer to the original full period value. | 9 |
What mechanism is introduced to reduce collisions on wireless broadcast media when multiple participants send Sync Interest simultaneously? | A random collision-avoidance timer (in the range of a few milliseconds) is introduced, as suggested by Wang et al. [9]. | 8 |
Why do SVS sync interests not solicit responses? | SVS sync interests are used as one-way notifications only, not triggering reply data packets, to avoid issues like persistent PIT states, reply conflicts, and dataset state divergence. | 8 |
What are the scalability concerns related to the SVS design? | The state vector design carries the entire dataset state in the sync interest name, leading to a large state vector size when there are many sync participants, which can exceed the network MTU limit. | 8 |
What is the ongoing work evaluating to address SVS scalability? | Approaches that let sync interests carry partial state vectors, leveraging the independence of [producer, sequence number] pairs to avoid the need for the full dataset state in each interest. | 8 |
What is the main advantage of using SVS in terms of state vector encoding? | SVS allows each [producer, sequence number] pair to be independent, enabling sync interests to carry partial state vectors instead of the full dataset state. | 8 |
How does SVS handle data item naming for scalability? | SVS uses sequential data item names that combine the producer's name with a sequence number, reducing the need for complete semantic information and enabling efficient scaling with a compact dataset state representation. | 8 |
README.md exists but content is empty.
- Downloads last month
- 12