Xu Xiaohu wrote:
I also did some worm-related troubleshooting and my intuition tells me that something will surely explode in such an architecture. Just a feeling, probably because you'll have to keep too much state per packet or because end hosts will get another leverage over the routers in terms of operations per packet...Reasonable, the default mapper will have to maintain a huge per-flow-based status statistics table. What's the estimated amount of statistics for eachdefault-mapper?
Hi Xiaohu, I don't believe the default mapper needs to understandanything about flows. When it gets a packet from an ITR, it simply examines the destination address and replies with a mapping, meanwhile encapping and forwarding the packet to the destination. Once the ITR receives the mapping, it doesn't make use of the default mapper again until it has another cache miss.
The default mapper keeps a small amount of state to ensure that it only responds once (or maybe twice) to a burst of traffic for the same (ITR, destination prefix) pair.
-Michael -- to unsubscribe send a message to rrg-request@psg.com with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg