AW: QoS and IEEE 802

["Tschofenig, Hannes" <hannes.tschofenig@siemens.com>]

Hi David, 

it is interesting to hear that you think that the generic RADIUS QoS will also be done in Dime. 
Fine for me. 

Ciao
Hannes


> -----Ursprüngliche Nachricht-----
> Von: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] Im Auftrag von Nelson, David
> Gesendet: Dienstag, 21. Februar 2006 18:07
> An: radiusext@ops.ietf.org
> Cc: dime@ietf.org
> Betreff: RE: QoS and IEEE 802
> 
> Hannes Tschofenig writes...
> 
> > > draft-ietf-radext-vlan-priority-00.txt
> > > draft-ietf-radext-filter-rules-00.txt
> > > draft-ietf-radext-redirection-00.txt
> > 
> > Is the first document about QoS (is priority QoS for you)?
> 
> No.  The draft includes IEEE 802.1 priority queues.  It does 
> not extend
> to anything like RSVP or DiffServ.  We agreed that the "full" QoS work
> would take place in the DIME WG, with coordination with RADEXT as
> needed.
> 
> > What are your thoughts about a common QoS approach? 
> Different IEEE 802
> > standards specify different QoS parameters and require RADIUS
> > interaction. There is work in 3GPP2 and ongoing work in Wimax.
> Recently
> > someone posted a draft about the DSL proposal in this area. 
> I ask this
> > question because I noticed that you seem to like a unified approach.
> 
> Yes, a unified approach would be highly desirable.  As indicated, DIME
> has the lead on this.
> 
> 
> --
> 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/>
> 

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