Hi Glenn,
> No, it's not -- see below.
>
> > Several people have, at various times,
> > mentioned that we need a document on how to generally interoperate
> > and interwork Diameter and RADIUS.
>
> John, have you read the NASREQ draft? It _is_, AFAICT, that
> document; in fact, others are using it as a template (or worse,
> incorporating it by reference (i.e., "just do what NASREQ does")
> already.
Yes, I have read the document, though I usually need a pot of coffee
to get through it ...
The abstract says:
This document describes the Diameter protocol application used for
Authentication, Authorization and Accounting (AAA) services in the
Network Access Server (NAS) environment. This application
specification, when combined with the Diameter Base protocol,
Transport Profile, and Extensible Authentication Protocol
specifications, satisfies typical network access services
requirements.
Initial deployments of the Diameter protocol are expected to include
legacy systems. Therefore, this application was carefully designed to
ease the burden of protocol conversion between RADIUS and Diameter.
This is achieved by including the RADIUS attribute space, and
eliminating the need to perform many attribute translations.
So, I'd say that we still need BCP or something that talks more generally about
how and when to translate, how to handle translation vs. pass the attribute unmolested.
Additionally, as you have noted, RADext work continues, how should Diameter
handle new RADIUS extensions. I agree that the ongoing RADext work should
have more text on how to handle Diameter interaction; but I maintain that
we still don't have a good understanding how RADIUS and Diameter should
co-exist, and your points are just underscoring that point, IMO.
John
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.