RE: QoS and IEEE 802

["Congdon, Paul T (ProCurve)" <paul.congdon@hp.com>]

Yes, I was talking about 2.4.

If there is to be a separate draft-ietf-radext-vlan-priority-00.txt
draft.  I would suggest it contain the following attributes from the
following current sections:

	2.1.      Egress-VLANID 
      2.2.      Ingress-Filters 
      2.3.      Egress-VLAN-Name 
      2.4.      User-Priority-Table

Paul
 
> -----Original Message-----
> From: Tschofenig, Hannes [mailto:hannes.tschofenig@siemens.com] 
> Sent: Tuesday, February 21, 2006 9:34 AM
> To: Congdon, Paul T (ProCurve); radiusext@ops.ietf.org
> Subject: AW: QoS and IEEE 802
> 
> Hi Paul, 
> 
> thanks for your quick response. 
> 
> > > Is the first document about QoS (is priority QoS for you)? 
> > 
> > The 802 priority attributes define a standard mechanism to 
> configure 
> > the standard 802.1 priority regeneration table.  They do 
> not deal with 
> > bandwidth allocations, reservations, schedulers, markers, meters...
> > They simply make a mapping of the incoming priority of a 
> frame to one 
> > of the eight 802 classes of service.  This is fairly simple and in 
> > support of an existing standard, so I would argue they do 
> not need to 
> > become part of a larger common QoS approach.  There are no current 
> > open issues related to this attribute.
> > 
> 
> Do you refer to the Section 2.4. User-Priority-Table ?
> 
> I will take a look at the referenced document ([IEEE802.1D]). 
> a few references are missing, btw.
> 
> Is the content of this attribute going to be dumped into 
> > draft-ietf-radext-vlan-priority-00.txt
> What else will go into this draft? 
> 
> Ciao
> Hannes
> 
> > Paul
> > 
> 

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