[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FW: Review of draft-nakhjiri-radius-mip4-01.txt
Thanks for the information. There's a charter item
in mip4 that is built for this stuff, and presumably
the group has agreed that they indeed want to do
this.
Wrt aaa key management requirements, I'd like to
find out more about what the problem is. I couldn't
do so yet, because the document was unclear with
its difference to RFCs 3957 and 4004. If this is the
same thing, I don't see an issue. If its a different
thing, I see a lengthy process ahead, similar to what
people went through in RFC 4004. From what I
can see, there's nothing that should cause a
deviation from 3957/4004, but we've seen this
happen in the past where people wanted to
do the RADIUS thing in a very different way
from the Diameter thing.
--Jari
Bernard Aboba wrote:
The Nakhjiri document has not been discussed in RADEXT WG, although it was
brought up in a 3GPP2 liaison request. At that time, the question arose
as to whether this was a legitimate dependency or not -- as I recall,
3GPP2 had already defined VSAs for use of MIPv4 within RADIUS, so it
wasn't clear whether this document, if developed would be deployed.
Also, concerns were raised about whether the document could meet the
AAA Key Management requirements.
On Thu, 13 Oct 2005, Jari Arkko wrote:
I reviewed this draft for the mobility directorate, as
its attempting to become a WG item in the MIP4 WG.
See review below.
Does anyone else want to comment on this? Was there
a history of this draft in RADEXT, or has anyone reviewed
this in the AAA Doctors team?
-------