Re: request to recharter

[Alan DeKok <aland@nitros9.org>]

Stefan Winter wrote:
> The points above make me think that it is about time to seriously consider 
> that the radext charter is modified to include RadSec into the working group 
> scope.

  I have no objections, presuming that TCP is also accepted as a
transport protocol.

> The only part in the charter that would need to be changed is, obviously, the 
> line
> 
> "- No new RADIUS transports (e.g. TCP, SCTP) will be defined."
> 
> which I request to purge from the charter.

  I'm not sure I understand all of Glen's concerns, but TCP as a
transport protocol is a fairly large change to RADIUS.  The basic
send/receive concepts don't change.  The packet formats don't change,
but there are issues relating to TCP && AAA stability, as discussed in
RFC 3539.

  I have no major objections to this.  If TCP is accepted, I would
suggest a draft focussed on issues relating to TCP as a transport
protocol.  The RadSec document can then reference this draft.

  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/>