Re: draft-ietf-l3vpn-mpls-vpn-mib drop counter

[Ross Callon <rcallon at juniper.net>]

TOM:    Understood, but I am still struggling with what you would do with that information once you have it.
                It seems that in either case, you have to sit down and re-tune the VRF size. >From my customer
                experience, I have seen that most of the deployments have 2 or at most 3 VRF sizes. The typical customer
                purchases the lower limit and moves up only if and when they exceed this limit (based on the
                existing notification information) or through other detection means. Given this, it seems that
                whether you are over by 3000 or 3, you would have to decide on raising the limit or
                decide that there was a configuration error on the CE.  The fact that you can tell your customer
                that you are seeing "something like 3000 routes" or just "more than the limit" doesn't seem to
                necessarily help.

If you are expecting less than 100 routes, and are over by 3 routes, then
I 
would expect that the limit probably has to be increased. 

If you are expecting 100 routes, and are over by 3000 routes, hasn't
someone 
made some significant error, and you probably need to debug the error
rather 
than just increase the limit? 

Ross (as individual contributor)