Yes, there is always some poor soul who will haplessly manage to
trip over cables, even if they are under a raised floor. So,
there is that--connections can drop.
That wasn't quite what I was getting at. What I meant was
generating an error condition which maybe ought not be there had
the closure been done 'the right way'. Right now, because I just
punt the connection as soon as I get the configuration goodies, I
see a premature EOF in my log files. Not the end of the world,
but I was wondering about not having it be there.
So I was thinking about sending an access complete message after
the configuration exchange, but that doesn't seem to be what it
was designed for in this case.
The last part of section 5.1 seems to imply that a disconnect after a configuration exchange should be rare as errors will be rare due to the "canned" responses. So maybe I'm thinking about this the wrong way.
Another approach would just be to not log a premature-EOF error
on a disconnect after a configuration exchange. I'll look into
that.
On 6/1/23 2:55 PM, Paul Koning wrote: Rude or not, it's clearly possible: in any distributed protocol the connection can end at any time.
On Jun 1, 2023, at 2:39 PM, Thomas DeBellis <tommytimesharing@gmail.com> wrote: First, what do you do after you get the foreign configuration message in NFT? Send an access complete and close or just close? I punt the connection, and was wondering whether that might be considered a rude thing to do.