On 5/21/22 07:13, Michael Richardson wrote:
Robert Moskowitz wrote:
> This is an item that goes back to the beginning of ESP work:
> Minimally, how does the higher level 'learn' that it is secure:
Are you asking how *TCP* learns of this, or how an application with an open
socket(2)
Thanks Chris.
Helps a bit.
On 5/20/22 20:27, Christian Hopps wrote:
Robert Moskowitz writes:
This is an item that goes back to the beginning of ESP work:
Minimally, how does the higher level 'learn' that it is secure:
E2E or TE2TE?
Encrypted/Authenticated/CrCed... ?
And as ESP has a
Robert Moskowitz wrote:
> This is an item that goes back to the beginning of ESP work:
> Minimally, how does the higher level 'learn' that it is secure:
Are you asking how *TCP* learns of this, or how an application with an open
socket(2) learns of this?
>
Robert Moskowitz writes:
This is an item that goes back to the beginning of ESP work:
Minimally, how does the higher level 'learn' that it is secure:
E2E or TE2TE?
Encrypted/Authenticated/CrCed... ?
And as ESP has a seq#, how might it be convied to the higher layer?
Case in point:
This is an item that goes back to the beginning of ESP work:
Minimally, how does the higher level 'learn' that it is secure:
E2E or TE2TE?
Encrypted/Authenticated/CrCed... ?
And as ESP has a seq#, how might it be convied to the higher layer?
Case in point: MAVlink has a 1-byte seq# in its
