I suspect the idea is the following: 1) First, you would decrypt the packet and validate the mac (assuming that it is an AEAD cipher) 2) You execute the operation to meet the latency requirements. 3) Then, you can take time to verify the digital signature (outside the latency requirements)
Is that the idea? -----Original Message----- From: Beck, Stefan [mailto:s.b...@osram.com] Sent: 19 October 2017 15:21 To: Hannes Tschofenig; ace@ietf.org Subject: RE: multicast Yes, correct. Stevie > -----Original Message----- > From: Hannes Tschofenig [mailto:hannes.tschofe...@arm.com] > Sent: Thursday, October 19, 2017 2:52 PM > To: Beck, Stefan <s.b...@osram.com>; ace@ietf.org > Subject: RE: multicast > > Hi Stefan, > > I am trying to understand your ideas. > > ~snip ~ > > > For multicast, my focus is on using asymmetric encryption for > authentication & integrity, and using symmetric encryption for confidentiality. > > In your view, you are sending a multicast message that will contain a digital > signature and is also encrypted using symmetric key crypto? > > Is this correct? > > Ciao > Hannes > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended recipient, > please notify the sender immediately and do not disclose the contents to any > other person, use it for any purpose, or store or copy the information in any > medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
