RE: [Tsvwg] Re: [tcpm] Revision of draft-larsen-tsvwg-port-randomization

In this context I wanted to bring up a related issue that might also strengthen this sort of a port randomization proposal.

Today the 64k port limitation is starting to become a huge problem and most often admins add ip addresses to increase the scalability. Given that most often the destination port (and sometimes the destination address) is well known, the only scalability left is the source address. Increasing ip addresses to improve scalability seems a fairly round about approach and frankly doesn't scale well. Given that the 64k limit is not fundamental why not provide a scaling factor similar to the receive window to scale the number of usable ports. This also makes randomization much more meaningful because in certain proxy scenarios the number of connections quickly exhausts the available ports and at that point the attacker can simply use any port assuming he can guess the source address.

Murari

-----Original Message-----
From: Lars Eggert [mailto:lars.eggert@nokia.com]
Sent: Wednesday, July 04, 2007 3:35 AM
To: tsvwg WG
Cc: tcpm@ietf.org; DCCP mailing list; ext Fernando Gont; TSV Dir
Subject: Re: [Tsvwg] Re: [tcpm] Revision of draft-larsen-tsvwg-port-randomization

On 2007-5-31, at 17:51, ext Lars Eggert wrote:
> The concepts in this draft are likely relevant to most of our
> transport protocols, and hence would be in scope for TSVWG. The
> TSVWG chairs are interested in comments on whether there is group
> interest in this draft - please comment on tsvwg@ietf.org.

We've received some positive feedback on adopting this draft, but I'd
like to see a stronger show of support, because this draft impacts
several of our transport protocols at the same time.

Please comment on tsvwg@ietf.org - reply-to set accordingly.

Lars

_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm