[icnrg] Review of "Architectural Considerations of ICN using Name Resolution Service"

[Christopher Wood <[e-mail]>]

Document: draft-irtf-icnrg-nrsarch-considerations-05

The summary of the review is: Ready with issues

Comments: 

Given that this is a considerations document for ICNRG, I think the level of detail is probably fine here. My biggest concern is the lack of discussion around NRS mapping management. The document states:

   When an NRS is utilized in an ICN architecture, security threats may
   increase in various aspects...

And then briefly describes "Name Space Management." It states that producer authentication is required, but I would like to see some more discussion there. In particular, is authentication required for only insertion into the NRS? What about updates or removal? (Something like BEAD [1] might help deal with deletion.)

On a related topic, how do clients (resolvers) know if they received the most up-to-date version of an NRS mapping? Should these be stored in cacheable content objects, or in new protocol messages that are not cached? This relates to the discussion around mobility, and I'm not sure how much detail you want to add here. Maybe just mentioning the possibility of stale content as a consideration will suffice.

Lastly, how a NRS impacts client behavior seems a bit unclear at the moment. This document seems to suggest that names can only map to other NDOs, and not, for example, prefixes. Should it be possible to query the NRS with a name prefix, and the NRS performs LPM to return the mapped value? What are the implications for clients if they can query by prefix? Should they always query the NRS before sending an interest for a name?

I hope this helps.

Best,
Chris

[1] https://arxiv.org/pdf/1512.07311.pdf