Re: [Dime] WG adoption call for draft-zorn-dime-rfc4005bis-01

["Glen Zorn" <[e-mail]>]

Sebastien Decugis [mailto:[e-mail]] writes:

>  Hi again Glen,

Hi, sorry for the slow reply!

...

> >>> In any case, if they decided to migrate to Diameter they could use
> the
> >>> pointless tunneling protocol, retiring their RADIUS server when the
> >>> transition was complete.
> >> You are implying that each domain can retire its RADIUS server only
> when
> >> *all* the domains have moved all their clients to Diameter... This
> >> reasoning may be possible in a single-domain context, but it does not
> >> hold in a multi-domain roaming consortium case.
> > Care to give some sort of rationale for this statement?
> Well, assume domain A is still using RADIUS and domain B has moved all
> its equipment to Diameter.
> Now a user from domain B is accessing the network through a NAS in
> domain A.
> 
> NAS-A -> RADIA agent (in RADIUS)
> RDR -> domain B in Diameter.
> Now, one needs to de-tunnel the RADIUS message from the RDR and then
> have a RADIUS stack to interpret this message, right?

Yes; presumably this would be the RADIUS server that they are retiring.

> Hence my comment that we cannot get rid of RADIUS in domain B until all
> domains in the consortium have moved to Diameter...

OK, but it was the assertion that "This reasoning may be possible in a
single-domain context, but it does not hold in a multi-domain roaming
consortium case" that I was questioning.

> In addition, with RADIA you loose the benefit of Diameter applications
> allowing to route different applications to different servers.

I'm confused: isn't the only Diameter app that deals w/RADIUS stuff NASREQ?


> 
> Best regards,
> Sebastien.
> 
> --
> Sebastien Decugis
> Research fellow
> Network Architecture Group
> NICT (nict.go.jp)
>