RE: [RRG] Tunnel fragmentation/reassembly for RRG map-and-encaps architectures

["Templin, Fred L" <Fred.L.Templin@boeing.com>]

Back from the holidays, I guess I'll begin the new year by
answering the only item I was explicitly asked *not* to: 

> -----Original Message-----
> From: Dino Farinacci [mailto:dino@cisco.com] 
> Sent: Friday, December 21, 2007 5:09 PM
> To: Templin, Fred L
> Cc: Routing Research Group list
> Subject: Re: [RRG] Tunnel fragmentation/reassembly for RRG 
> map-and-encaps architectures
... 
> > reduce the memory required for reassembly buffers by
> > actively discarding any reassemblies that appear to
> > have no chance of completion. This assumes that any
> 
> And how does the ETR determine there is no chance of completion?  
> Please don't answer.

Recent Linux 2.6.x kernel versions do exactly this; pull
a recent kernel distribution, edit net/ipv4/ip_fragment.c,
and search for "ip_frag_too_far". (This was pointed out by
Matt Mathis in an off-list discussion.)

Thanks - Fred
fred.l.templin@boeing.com  

> Dino

--
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