[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: TCP transport draft
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
some small glitches:
2.2. TCP Ports
~ IANA has already assigned TCP ports for RADIUS transport, as outlined
~ below:
~ * radius 1812/udp
~ * radius-acct 1813/tcp
~ * radius-dynauth 3799/tcp
1812/tcp.
2.6.3
~ * Packet from an unknown client (using the key as defined above)
~ * Packet with an invalid code field
~ * Packet that is less than the minimim RADIUS packet length
~ * Packet that is more than the minimim RADIUS packet length
more than the maximum.
Should there be some more TCP usage profile guidelines in it, like
recommending TCP PSH when a RADIUS message is complete, 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.
Greetings,
Stefan Winter
- --
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - Réseau Téléinformatique de l'Education Nationale et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg
Tel: +352 424409 1
Fax: +352 422473
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iEYEARECAAYFAkhswk4ACgkQ+jm90f8eFWY7bgCeI497U6BcTdsGT/iOy9CSIbbQ
TTwAoIXYaIVDfXQJpfOR/OjmH4d2sLHU
=M56L
-----END PGP SIGNATURE-----
--
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/>