Re: RE : : Support for Geopriv RADIUS attributes in Diameter
Jari Arkko <[email protected]>
| Newsgroups | gmane.ietf.aaa |
|---|---|
| Message-ID | <[email protected]> |
[email protected] wrote: >Hi Lionel, > > > >>The following statement is not enough? >> >>8. Diameter RADIUS Interoperability >> >> In deployments where RADIUS clients talk with DIAMETER servers or >> DIAMETER clients talk with RADIUS servers then a translation agent >> will be deployed and operate in accordance to the NASREQ >> specification [14]. >> >> > >That was what I was wondering. Some of the people who queried me about this >thought it wasn't enough; that's why I am checking with the rest of the >WG. > > s/operate/operated/ Translation happens presumably through a mindless, standard NASREQ mapping. That's sooo much better than hand-coding everything. But there are also other Diameter issues. Can you use these attributes in commands not associated with NASREQ (or anything that inherits the NASREQ rules). Say, some of the Diameter SIP operations that don't exist in RADIUS? I guess that was also what Jouni is saying. Suggestion: the document should provide guidance in which Diameter commands (of the existing applications) you can use them. --Jari