Diameter Mobile IPv6: Support for Network Access Server to Diameter Server Interaction
RFC 5447
Yes
No Objection
Note: This ballot was opened for revision 12 and is now closed.
(Dan Romascanu; former steering group member) Yes
(Chris Newman; former steering group member) No Objection
I support the other ADs discuss positions.
(Cullen Jennings; former steering group member) No Objection
(David Ward; former steering group member) No Objection
(Jari Arkko; former steering group member) (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.
(Lisa Dusseault; former steering group member) No Objection
(Magnus Westerlund; former steering group member) (was Discuss) No Objection
(Pasi Eronen; former steering group member) (was Discuss) No Objection
(Ron Bonica; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Tim Polk; former steering group member) No Objection
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).