Will Hargrave wrote: > With a 30 minute cull window, there is substantial concern that an > operator will begin to debug the ‘problem’, discover ICMP PING works but > TCP/179 doesn’t work, and get very annoyed at this strange behaviour. I > think we should operate on a principle of least surprise here.
We have found that re-mailing technical contacts with a "Maintenance is about to start in 1 hour" reminder helps quite a lot in this sort of situation. Low tech is sometimes good. Otherwise, 30 minutes for traffic drain is unnecessary - we keep our interface counters on 30 second load average so can see when the majority of traffic is gone; this always happens within a couple of minutes of the 3m bgp dead time drop. Usually this sort of thing happens at omg o'clock in the morning, and we've found that reducing the time load helps quite a bit with both accuracy and staff morale, as all our staff usually work regular office hours. Again, this sort of rationale would be outside the scope of IETF BCPs, but they are real enough concerns that I'd personally be uncomfortable with recommending any delays. Nick _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
