[Nfd-dev] Signed Interest processing: alternate to stop-and-wait

Marc.Mosko at parc.com Marc.Mosko at parc.com
Mon Feb 23 09:54:46 PST 2015

I think if a protocol needs serialized commands, it should have its own serial number and not confound protocols by using a field from a different area of concern.  For example, if you change signing algorithms that use a different mechanism, will that break your protocol?

I think the signing algorithm and verification should use its own mechanism.  Other protocols should not peek in to there for their properties. For example, some system might ditch the existing signature and put a new signature on there.  That should not change your protocol’s behavior.


On Feb 23, 2015, at 9:50 AM, Mark Stapp <mjs at cisco.com<mailto:mjs at cisco.com>> wrote:


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150223/755df666/attachment.html>

More information about the Nfd-dev mailing list