[tcpm] tcp-auth-opt issue: support for NATs

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

Adam Langley raised the issue of support for NATs.

The TSAD is indexed by the socket pair of the incoming/outgoing packet
(addr/port pair). There is no provision for a separate key identifier
that would be unique across all connections.

As a result, the KMS must populate the TSAD with the appropriate
connection information - it must know the source/dest used at both
endpoints, even if they differ.

<individual contributor hat on>
(I should have indicated this in some parts of other posts, FWIW)

Suppose they do differ; the KMS could then put both sides' views of the
src/dst info on each side's TSAD:
	src/dst addr/port as sent
	src/dst addr/port as rec'd

The TSAD would be indexed by the "as sent" info, but the MAC would be
calculated using the "as rec'd" info.

<hat off>

Should the document:

a) require the socket pair info always be included in the MAC, i.e., be
protected

b) allow a TSAD entry to indicate that the socket pair is excluded from
the MAC?

Finally, does (b) help, given the current keying requirements?

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

iEYEARECAAYFAkiQ9L4ACgkQE5f5cImnZruvmwCglVgXBbN9hSgiuoa1p/r+1FGP
0lQAn0FBL8te0c5UD6eK+q/BwDtcQbAG
=kusE
-----END PGP SIGNATURE-----
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www.ietf.org/mailman/listinfo/tcpm