Hello Nigel,
NR> > Hmmm.. I think that would be a bit too much. Systems that fly the PING
NR> flag can be considered to have an open invitation to test it ...
And there really is not that much wrong with it ...
NR> So some not flying a PING
NR> flag may consider it mildly annoying if their logs are contaminated by
NR> unsollicited PING attempts...
The argument of disc-overflows is not valid anymore with the capacities now
available ... and the spec mentions that onsollicited PINGs to a system which
does not fly that flag should end in the bit-bucket.
There are more important things in life to get upset about ...
NR> BTW, why are you sending an unsolicited ping to my BBS if I don't have
NR> the PING flag? :)
Look at what I'm getting ...
****************************************************************************
Date: 11 Feb 21 11:19:54
From: Michiel van der Vlist on 2:280/5555 Nieuw Schnoord in Driebergen
To: Ping on 2:292/854 Many-Glacier (043) in Mortsel
Date: 13 Feb 21 11:03:18
From: Michiel van der Vlist on 2:280/5555 Nieuw Schnoord in Driebergen
To: Ping on 2:2/0 Eur (043) in B
Date: 13 Feb 21 11:03:48
From: Michiel van der Vlist on 2:280/5555 Nieuw Schnoord in Driebergen
To: Ping on 2:2/1000 International Coordinator in Belgium
****************************************************************************
Nothing to be upset about has happened.
\%/@rd
--- DB4 - Dec.21 2020
* Origin: Hou het veilig, hou vol. Het komt allemaal weer goed (2:292/854)
|