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

Re: Suggestions regarding RADIUS encoding for draft-ietf-dime-qos-attributes-07.txt

To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
Subject: Re: Suggestions regarding RADIUS encoding for draft-ietf-dime-qos-attributes-07.txt
From: Alan DeKok <aland@deployingradius.com>
Date: Fri, 19 Sep 2008 16:57:23 +0200
Cc: radiusext@ops.ietf.org
In-reply-to: <48D29BF1.1030806@gmx.net>
References: <48D29BF1.1030806@gmx.net>
User-agent: Thunderbird 2.0.0.16 (X11/20080724)

Hannes Tschofenig wrote:
> In Dime we are currently working on
> draft-ietf-dime-qos-attributes-07.txt and a missing piece is the RADIUS
> Diameter compatibility section.
> 
> How should we encode these AVPs in RADIUS attributes?

  The sheer number of attributes, and use of Diameter functionality
(e.g. grouping && data types) makes it difficult.

  I'm not sure there are any good methods for doing this.

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

References:
- Suggestions regarding RADIUS encoding for draft-ietf-dime-qos-attributes-07.txt
  - From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>

Prev by Date: Re: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
Next by Date: RE: [Emu] EAP, RADIUS, UTF-8, RFC 4282 and SASLPREP: the interop nightmare
Previous by thread: Suggestions regarding RADIUS encoding for draft-ietf-dime-qos-attributes-07.txt
Next by thread: Re: Suggestions regarding RADIUS encoding for draft-ietf-dime-qos-attributes-07.txt
Index(es):
- Date
- Thread