RE: request to recharter

["Glen Zorn" <glenzorn@comcast.net>]

Stefan Winter <> scribbled on Monday, February 11, 2008 5:26 PM:

> Hello,
> 
> the topic of re-chartering radiusext to accomodate the RadSec work
> has been a continuous topic in the last two meetings, the mailing
> list and in several offline discussions.  

Yes, there has been a popular upswell of support for abandoning our work
in favor of yours -- oh, wait, that would be you alone...

> The last meeting in Vancouver suggested to move the three most
> promising crypto-agility suggestions (keywrap, dtls, radsec) to EXP
> status within radext.  
> RadSec is being implemented in various independent codebases and is
> in production use today. 
> 
> 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.  

Yes, there has been a popular upswell of support for abandoning our work
in favor of yours -- oh, wait, that would be you again...

> 
> The DTLS draft led to consensus that TLS-style payload encryption is
> not considered being a new security mechanism for protecting RADIUS
> (which would be excluded by the charter as-is). Then, the same holds
> true for the TLS part of the radsec draft, which in turn means this
> part of the charter does not need changing.    
> 
> 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.

No, no, NO!  "radsec" is not RADIUS, period.  Not an extension, not even
a perversion, not RADIUS.  I would support a radsec BOF & WG, but I will
not support this.

> 
> After being included in the radext WG scope, the radsec draft would
> certainly be rewritten for more normative wording. Because up to now,
> it was meant as an FYI description of existing implementations, not
> in any way a standard.   
> When EXP is a target, language should change accordingly. I volunteer
> to do this to the best of my knowledge - it is my first I-D at all. 
> 
> Greetings,
> 
> Stefan Winter


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