RE: new Service-Type

["Avi Lior" <avi@bridgewatersystems.com>]

Victor,

I am wondering about whether or not this is the way you would want to do
this.

In my opinion Service-Type is really broken when it comes to requesting
and authorizing services.

First and foremost only one instance of Service-Type is allowed in a
radius packet.  Therefore a client that is requesting multiple services,
for example IP service, Voice Service, Video Streaming etc., would have
to issue multiple requests....clearly not what you want to do.

However, if this was an authentication that comes from the Video
Streaming subsystem, in which case that is the only thing that it would
be requesting authentication for, then a Service-Type of Video etc would
work.  It would not be the only way to achieve that goal. Usually the
Server would have other attributes to key on, or one could use NAS-IP
and NAS-ID or even NAS-Port-Type.

I am not objecting to the allocation of Service-Type but I am wondering
what the utility of using it for the purpose that you state.


 

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Victor Gamov
Sent: Tuesday, April 10, 2007 4:24 AM
To: Bernard Aboba
Cc: radiusext@ops.ietf.org
Subject: Re: new Service-Type

Hi Bernard!

Some times ago I ask about propose new Service-Type values to carry
information about video services.  Now I have I-D which propose such
values. This document placed at
http://so.comsat.ru/IST/draft-vit-radext-videoservicetype-00.txt

Please tell me what else must I do to approve this values by IANA?

Thanks!

--

CU,
Victor Gamov

--

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