On Mon, Oct 27, 2014 at 9:22 PM, Tom Taylor <[email protected]> wrote:
> Leaving aside the notification question for research, the discussion below > suggests that the boundary between port exhaustion and address exhaustion > is somewhat indeterminate. The MIB currently has two counters (showing up > in various tables, another issue), OutOfPortErrors and ResourceErrors, with > the latter supposedly picking up address exhaustion. I'd suggest we make > the first one OutOfAddressPortErrors and thereby eliminate the ambiguity. > I'd also call these Drops rather than Errors to make the consequences > clearer. Works for me! Thanks, Simon
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
