Clarifications on the Routing of Diameter Requests Based on the Username and the Realm
RFC 5729
Yes
No Objection
Note: This ballot was opened for revision 04 and is now closed.
Lars Eggert No Objection
(Dan Romascanu; former steering group member) Yes
(Adrian Farrel; former steering group member) (was Discuss) No Objection
(Alexey Melnikov; former steering group member) No Objection
I support Jari's DISCUSS on i18n (issue 6). 4.2. Ensuring Backwards Compatibility Implementations compliant to this specification MUST define a new Diameter application. This requirement is set to guarantee backwards compatibility with existing Diameter implementations, applications and deployments. Diameter agents not compliant with this specification will not advertise support for these new applications that implement the enhanced routing solution based on Decorated NAIs and will therefore be bypassed. Excuse my ignorance, but how can this be achived?
(Cullen Jennings; former steering group member) No Objection
(Jari Arkko; former steering group member) (was Discuss) No Objection
(Lisa Dusseault; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Pasi Eronen; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) 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