Subject: [core] Token or source port

From: Cullen Jennings <[email-masked]>
Date: Tue, 10 May 2011 07:56:37 -0700

When a client has multiple outstanding transactions, one approach would be to include a token in each one, a different approach would be to do each transaction from a different source port. WHen using DTLS, the token is probably preferable but for UDP deployments, what should implementors do? Creating a new flow for every transaction has the potential to create a huge amount of state on the NATs as, unlike TCP, there is no FIN to clean up the state on the middle boxes. 

Thoughts on what advice the draft should offer implementors?

Cullen <in my individual contributor role>