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

Re: RADIUS and complex attributes

To: Greg Weber <gdweber@cisco.com>
Subject: Re: RADIUS and complex attributes
From: Bernard Aboba <aboba@internaut.com>
Date: Mon, 16 Feb 2004 11:42:26 -0800 (PST)
Cc: "Joel M. Halpern" <joel@stevecrocker.com>, radiusext@ops.ietf.org
In-reply-to: <200402161722.MAA18993@cisco.com>
References: <200402161722.MAA18993@cisco.com>

> I think it would be very helpful to produce some more modern
> recommendations on how to format/tag/concatenate/encrypt/etc VSAs
> and when to pursue IETF space use vs. vendor (SDO) specific.
> Perhaps this is worthy of charter work-item inclusion.

I think it is.  There has been some discussion about one of the following
types of documents:

a. RADIUS Implementation Issues and Fixes
b. RADIUS attribute design guidelines



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

References:
- Re: RADIUS and complex attributes
  - From: Greg Weber <gdweber@cisco.com>

Prev by Date: Re: RADIUS and complex attributes
Next by Date: RE: subtypes (was: HTTP digest and RADIUS; new version of the St ermandraft)
Previous by thread: Re: RADIUS and complex attributes
Next by thread: RE: subtypes (was: HTTP digest and RADIUS; new version of the Stermandraft)
Index(es):
- Date
- Thread