Re: [tcpm] tcp-auth-opt issue: replay protection

[Joe Touch <[e-mail]>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Regarding the ESN,

<individual hat on>
My goal was to allow TCP-AO code to be isolated to handling packets just
before exit/entrance to IP. That suggests that all TCP-AO state should
be kept to the TSAD, and not extend the core TCP code unless absolutely
necessary.

Let's assume we compute the ESN

	compute the ESN for each packet as Adam described,
	using the 'nearby' algorithm

The question becomes when to actually increment the ESN?

Eric Rescorla wrote:
| I'm sorry, but I don't understand the issue. The ESN dosn't have to
| move monotonically forward, any more than the packet sequence numbers
| do. You assign bytes sequence numbers in a 64-bit rather than 32-bit
| space and only transmit the low-order 32 bits in the packet.

This would require modifying the core of TCP to use 64-bit sequence
numbers throughout.
<individual hat off>

Does the WG want to keep mods out of the core of TCP, or can we assume a
64-bit sequence number space?

- ------

A separate question is whether ESN rollover should use the keyID
mechanism or not. This is related to Eric's points:

| So, two salient points:
| 1. When the sequence number is in the region of 0 (more precisely
|    while there are unacked segments on both sides of the region),
|    then the sides must maintain two keys and arrange to use
|    the appropriate one.

Eric - can you explain "arrange to use the appropriate one"?

| 2. The same key-id is used in the packet regardless of the which
|    key is being used to protect the traffic. It refers to the
|    static key from which the traffic keys were diversified.

Eric - can you explain where the multiple keys per keyID are determined?
i.e., are they recomputed per-packet or kept somewhere?

<individual hat on>
FWIW, I agree with Eric's example on the wire; the issue is the state
required at the endpoints required to make it happen.
<individual hat off>

Comments?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiRdb0ACgkQE5f5cImnZrtD0ACgh2FOEbxxfkDJhNnZLDtCima6
Y1AAoKu5WJqoFtYH2eBLJdF5aDEHvk+R
=fNzA
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/tcpm