Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction
Note: This ballot was opened for revision 12 and is now closed.
(Dan Romascanu) Yes
(Jari Arkko) (was Discuss, No Objection, Discuss) No Objection
The small detail that I complained about in my Discuss has been fixed. However, I still support Pasi in his Discuss. From an initial look it was not clear how it was addressed in the new version.
(Ron Bonica) No Objection
(Ross Callon) No Objection
(Lisa Dusseault) No Objection
(Pasi Eronen) (was Discuss) No Objection
(Russ Housley) No Objection
(Cullen Jennings) No Objection
(Chris Newman) No Objection
Comment (2008-10-23 for -** No value found for 'p.get_dochistory.rev' **)
I support the other ADs discuss positions.
(Tim Polk) No Objection
Comment (2008-10-22 for -** No value found for 'p.get_dochistory.rev' **)
In email Sept. 9, Jouni indicated his intention to add the following text to the security considerations, but it does not appear in the current RFC Editor note. The Diameter messages may be transported between the HA and the Diameter server via one or more AAA brokers or Diameter agents. In this case the HA to the Diameter server AAA communication rely on the security properties of the intermediate AAA brokers and Diameter agents (such as proxies).