icnrg / draft-irtf-icnrg-terminology

ICNRG terminology draft
https://icnrg.github.io/draft-irtf-icnrg-terminology/
0 stars 1 forks source link

Comments from Brian Trammel on draft version -06 #9

Closed daveoran closed 4 years ago

daveoran commented 4 years ago

A terminology document, as a potential landing place of someone trying to get their head around a new area, should at least have security considerations by redirection. In particular, the definition of "trust" refers to the context of a trust model but makes no reference to trust models typically used within ICN deployments; I looked to the security considerations section for this and was disappointed. In the interest of being general, we don’t point to particular trust models or schemes to support them. However, there is a lot of good work here and that seems to be the common direction for both CCNx and NDN, so it’s probably appropriate to add a sentence on this and a reference to the Trust Schema paper for NDN. Would that alleviate your concern? The use of Packet, Segment, and Frame is a little weird for people with a traditional TCP/IP background. Differences in applicability between segmentation and fragmentation an an ICN are not really clear to me after reading this document. Additional discussion would be useful. Could you elaborate a bit on this? Packet is an L3 object understood by forwarders. Segment is a piece of a content object that had been fragmented to place in a Packet. Frame is the L2 thing you stuff packets in. Is this different from your understanding of either what the terminology doc says, or what the usage in for TCP/IP?

daveoran commented 4 years ago

This was fixed in the -07 version