Talk:Diameter (protocol)
From Wikipedia, the free encyclopedia
The name should be Diameter, not DIAMETER. --Fylke
RFC3588 uses 'Diameter', but both spellings are common in many documents. 'Diameter' might be preferred because it's not an abreviation. -- bluezy
The page for RADIUS says that DIAMETER *IS* backward compatible. What is the truth? could someone knowledgable please get the two entries in a consistent shape? --a reader
It's not directly backwards compatible because it uses a different different protocol layout, and runs on a different transport (TCP or SCTP instead of UDP). But the designers have gone to great pains to ensure that it's easy to build a gateway between RADIUS and Diameter, but using the same AVP codes for example. The NASREQ application (application doesn't mean a product here, but a specific sub-protocol, defined on top of the base protocol from RFC3588) almost a complete copy of the original RADIUS protocol. -- bluezy (currently working on gateways)
Is SIP a Diameter application ? I don't think it is -- a reader
No, but the "Diameter SIP Application" is. See <http://www.ietf.org/internet-drafts/draft-ietf-aaa-diameter-sip-app-10.txt>. Should not be confused with SIP itself.
What is the performance impact of using Diameter v/s RADIUS or a direct LDAP query ? -- a reader
Diameter is not a peer-to-peer protocol, it is a client-server protocol, with exception that server can also have some initiated messages. However the reason and difference is because if it was peer-to-peer, both server and client would have the same set of messages to exchange which is not the case in Diameter. Instead Diameter clients and Diameter servers each have their own sets of "requests" and "answers".
it is possible to route besides to authorize? -- member of <http://www.cidra.com.ar>
On the difference list:
RADIUS can and should also use IPSec
RADIUS is also a client server protocol with server-intiated messages (RFC 3576)
RADIUS can also be extended.. The real point of Diameter applications are *well defined*. If you look realistically at the avaliable diameter applications they need specific server/client codes to support them which is the same when adding a new code to RADIUS.
Who cares about 32-bit boundaries? Remove this and lets get some real-world benefits of the Diameter protocol listed.
RADIUS also supports accounting, user session? This needs to be clarified or removed entirely.
Man get back to reality - Diameter is happening big time Diameter is everywhere - in any Telco RFP today you need Diameter support. and soon also in the web with the SIP Diameter applciation
