[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Charter questions
- To: "Weiss, Walter" <wweiss@Ellacoya.com>
- Subject: RE: Charter questions
- From: Bernard Aboba <firstname.lastname@example.org>
- Date: Wed, 23 Jan 2002 08:14:44 -0800 (PST)
- Cc: "'Harrington, David'" <email@example.com>, "'Wijnen, Bert (Bert)'" <firstname.lastname@example.org>, "Durham, David" <email@example.com>, "'firstname.lastname@example.org'" <email@example.com>, "'Randy Bush'" <firstname.lastname@example.org>, "'David Mitton'" <email@example.com>
- In-reply-to: <D9B4A3B5A9FCD5118BFE00D0B760121C4121DF@bor.ellacoya.com>
> > How many of the other RFC 2989 requirements does the COPS/AAA
> > functionality satisfy? Souds like you've essentially got functionality
> > equivalent to Diameter NASREQ, and Accounting. Can it do Mobile IP
> > too? Protection of AVPs end-to-end a la CMS-Sec?
> To be honest, I stopped tracking DIAMETER issues at 150, and we never went
> back to see how well the various requirements are supported by this work. I
> suppose someone may be interested in investigating it though. As to the
> security question, the COPS protocol supports both CMS and TLS, which
> provides protection both at the protocol and the object levels.
Well, it certainly sounds like you believe that you have developed a
completely RFC 2989 compliant AAA protocol. At the least, I'd suggest that
this compliance be documented for all the AAA applications that you've
chosen to support.