Hi, Jan, I guess this kind of port exhaustion problem will also exist in dynamic CGN. Assume the average port number consumed by average subscribers are 2000 (around 32 users per public IPv4 address) and this CGN has 32 concurrent users at that time with the only public IPv4 address in the address pool, one can still find port exhaustion when applying for more 2500 concurrent ports.
So, this is a problem about how to define appropriate port set for our customers, or to define maximum concurrent subscribers for a given IPv4 address pool. Otherwise, there would either be a waste of resource, or port exhaustion. Maybe we can even make some more flexible port-set rules for different time-slot or different types of users. But anyway, this is the problem we have to face in the further, and I also suggest that port-consuming applications should upgrade to IPv6 directly. Best regards On Mon, Aug 1, 2011 at 10:45 PM, Simon Perreault < [email protected]> wrote: > Jan Zorz @ go6.si wrote, on 08/01/2011 10:36 AM: > > Well, is short words, whatever number of ports you assign in > port-set/range, end > > user can exhaust them. > > The fact that most ISPs have been successfully operating with 65536 ports > per > subscriber demonstrates that it is possible to statically provision > subscribers > with "enough" ports. > > Simon > -- > DTN made easy, lean, and smart --> http://postellation.viagenie.ca > NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca > STUN/TURN server --> http://numb.viagenie.ca > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
