(RADIATOR) DIAMETER dying?

Wed Mar 2 07:35:56 CST 2005

Hi
We are using an Ericsson GGSN for mobile GPRS. The real time charging
interfaces are developed using RADIUS and now DIAMETER.  We had to
develop a radius to diameter server as well for some initial billing
issues.

The new nodes now are fully diameter compliant with some Ericsson
specific modifications.

Surajh Surjoo
Systems Engineer - Data
Mobile: 0832129829

If A equals success, then the formula is: 

A = X + Y + Z, 

X is work. Y is play. Z is keep your mouth shut. 
--Albert Einstein 

NOTE: This e-mail message is subject to the MTN Group disclaimer see
http://www.mtn.co.za/email_disclaimer.asp

-----Original Message-----

NOTE: This e-mail message is subject to the MTN Group disclaimer see http://www.mtn.co.za/default.aspx?pid=34411
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
Behalf Of Hugh Irvine
Sent: Wednesday, 02 March 2005 01:21 PM
To: Mike McCauley; Dave Kitabjian
Cc: Radiator MailingList
Subject: Re: (RADIATOR) DIAMETER dying?

Hi Dave -

As always there is a healthy dose of "if it isn't broken, don't fix it" 
associated with the RADIUS protocol - it really is quite remarkable how 
simple and useful a protocol it is. That said there are a number of 
serious shortcomings with the RADIUS protocol that DIAMETER seeks to 
address, including greatly expanded header fields and attribute fields 
and much stricter control over attribute use. DIAMETER is also designed 
to use reliable, encrypted transport and this is important for some 
people. I also personally feel that the EAP extensions to RADIUS are an 
ugly kludge at best.

In my recent travels I have seen increasing interest in Diameter and I 
also saw my first equipment that implements a DIAMETER client (an 
Ericsson service gateway device). My expectation is that all the 
equipment vendors are working on DIAMETER clients and we will start to 
see code appearing during the course of this year.

I imagine that we will see RADIUS/DIAMETER translation gateways as the 
first products to be introduced, as this sort of operation will allow 
existing RADIUS implementations to be used unchanged, with DIAMETER 
being used for the "core network" within a providers infrastructure 
(somewhat analogous to IPv6 deployment).

I also imagine that many current RADIUS users will continue to use 
RADIUS quite happily, as it meets their needs perfectly well. I expect 
to see DIAMETER being used in new, large projects where its features 
provide the solutions to problems like secure, reliable transport, 
"automatic" service location discovery, expanded accounting 
capabilities, and enhanced attribute use. The projects that fit into 
this category that I have seen are mainly large-scale roaming 
initiatives in academia and/or government. There is also some interest 
in large-scale corporate intranets too.

So, no I don't think that DIAMETER is dying, but I also don't think it 
is going to replace every single existing RADIUS installation any time 
soon either.

As you already know, we are actively working on raDiameter currently 
and we have a number of beta-testers who have expressed interest in 
testing the early code with a view to deploying experimental DIAMETER 
servers sometime later this year.

If you have any further questions or comments please feel free to post 
them.

I have copied this mail to Mike for his comments, and I would be 
interested in everyone else's views as well.

regards

Hugh

On 1 Mar 2005, at 23:18, Dave Kitabjian wrote:

> Hey folks,
>
> I was chatting with the good folks at O'Reilly (http://www.ora.com) as

> to whether they had any plans to produce a book on DIAMETER. Their 
> impression was that DIAMETER was dying, if not dead.
>
> I have also noticed that www.diameter.org has been offline for some 
> time. Still, I know you guys are producing raDiameter, and I pointed 
> them to your website.
>
>  Does anyone want to comment on where that technology stands and what 
> might be the issues affecting its success and adoption?
>
> Thanks,
>
> Dave
>

NB: I am travelling this week, so there may be delays in our 
correspondence.

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.