RE: Deployment Review for Bandwidth Attributes Document

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

Paul,

I believe that it would be a useful thing to discuss this in 802.1. I
would rather see the issues of how we standardize definition of
bandwidth, what limiting means, and how to do it discussed first in
802.1. It can be taken over by radext later, but I do not believe that
it is a RADIUS extension problem, other management protocols may apply.
This is the reason for which I did not support the work in radext,
although the problem of bandwidth limitation is interesting for me as
well. 

Thanks and Regards,

Dan


 
 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Congdon, 
> Paul T (ProCurve)
> Sent: Friday, September 16, 2005 7:23 PM
> To: Bernard Aboba
> Cc: radiusext@ops.ietf.org; Mick Seaman; Tony Jeffree
> Subject: RE: Deployment Review for Bandwidth Attributes Document
> 
> 
> I believe the proposal Avi and I have discussed would 
> interest the 802.1 folks and I can certainly present this 
> briefly to them next week at the Interim.
> 
> Paul 
> 
> > -----Original Message-----
> > From: Bernard Aboba [mailto:aboba@internaut.com]
> > Sent: Friday, September 16, 2005 9:21 AM
> > To: Congdon, Paul T (ProCurve)
> > Cc: radiusext@ops.ietf.org
> > Subject: RE: Deployment Review for Bandwidth Attributes Document
> > 
> > One way to move forward would be to revise the document in order to 
> > increase buyin from the individuals who responded to the survey.
> > In particular, wider buyin from IEEE 802.1 participants would be 
> > desirable.
> > 
> > With IETF 64 and the  November IEEE 802 plenary occurring 
> in the same 
> > city (Vancouver, CA) one week apart, this might be a good 
> opportunity 
> > for cooperation.
> > 
> > 
> > On Fri, 16 Sep 2005, Congdon, Paul T (ProCurve) wrote:
> > 
> > > 
> > > Sounds to me like there is support, especially if we added
> > a scheme to
> > > support the 802 traffic classes.  Avi and I have talked
> > about a simple
> > > and optional way to do this without crossing the complexity
> > line.  It
> > > would be good to know if this would satisfy Pat's needs.
> > > 
> > > 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/>
> 

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