[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: request to recharter

To: "David B. Nelson" <d.b.nelson@comcast.net>, <radiusext@ops.ietf.org>
Subject: RE: request to recharter
From: Bernard Aboba <bernard_aboba@hotmail.com>
Date: Wed, 13 Feb 2008 15:04:07 -0800
In-reply-to: <078001c86e67$5fec7d00$011716ac@NEWTON603>
References: <200802111126.25340.stefan.winter@restena.lu> <47B3214B.4050407@nitros9.org> <078001c86e67$5fec7d00$011716ac@NEWTON603>

> I think that would be warranted, whether in a separate document or
> integrated.  Someone sent me an off-list reply, expressing concern about
> changes to the RADIUS paradigm for timeouts and retransmissions, when using
> TCP.  Those issues would certainly need to be addressed.

There is already a proposed standard for the transport of AAA protocols over TCP,
"Authentication, Authorization and Accounting (AAA) Transport Profile", RFC 3539. 
--
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/>

Follow-Ups:
- RE: request to recharter
  - From: "David B. Nelson" <d.b.nelson@comcast.net>

References:
- request to recharter
  - From: Stefan Winter <stefan.winter@restena.lu>
- Re: request to recharter
  - From: Alan DeKok <aland@nitros9.org>
- RE: request to recharter
  - From: "David B. Nelson" <d.b.nelson@comcast.net>

Prev by Date: Re: request to recharter
Next by Date: RE: request to recharter
Previous by thread: Re: request to recharter
Next by thread: RE: request to recharter
Index(es):
- Date
- Thread