Re: TCP transport draft

[Alan DeKok <aland@deployingradius.com>]

Stefan Winter wrote:
> some small glitches:

  Fixed, thanks.

> Should there be some more TCP usage profile guidelines in it, like
> recommending TCP PSH when a RADIUS message is complete,

  There's no socket API to do that, so far as I know.  The closest thing
is that the kernel *usually* will send the data if it's written by
write() or send(), as one call.

> or should it
> remain at the sentence "We RECOMMEND that implementors of this
> ~   specification familiarize themselves with TCP application programming
> ~   concepts." IMHO, a little more handholding wouldn't hurt.

  I think that this document isn't the place to get into programming
guidelines.  If people want to know about TCP application programming,
there are books && lots of source available.  This document should
concentrate on RADIUS && TCP interaction issues.

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>