Hi, > The only concern/reason is to not silently increase the memory > requirement of Mesh > support with this patch. OK. > So was skeptical on having a higher cache size(like 250 or 500 max). > Hence had a value of 50 and left the configuration part for devices > which needed higher > cache. > But as you mentioned, this is only runtime max memory and not default. > So we should be fine to set some high limit, If above is not a > concern could we stick to > an upper limit of ~150-200 ? Right, I'm fine with that. I was just throwing out 500 as a random number to show that it's not really a huge memory requirement. > Apart from that, though the points you mentioned are quite possible, > the cache > Management logic will ensure to cleanup stale entries and in worst > case will > use regular header generation process if cache is full. So I feel that > should ensure > things work as normal even under attack. Right. johannes
