RFC 4889, "Network Mobility Route Optimization Solution Space Analysis", July 2007Source of RFC: nemo (int)
Errata ID: 1038
Status: Held for Document Update
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-09-12
Held for Document Update by: Brian Haberman
Section 5.1.2 says:
Traditionally, it has been generally avoided having state information in the routers to increase proportionally with the number of pairs of communicating peers.
It should say:
This is not true for the vast majority of IPv4 routers deployed
today, the typical NAT/NAPT 'SOHO' access routers, which all need to
keep *per flow* state -- increasing even more, proportionally with
the number of transport 'sessions' between communicating peers!