4. Standards Compliance

4 Standards Compliance

Known points of questionable or non-compliance.

There is no support for DTLS over SCTP.
There is no explicit support for peer discovery (section 5.2). It can possibly be implemented on top of diameter as is but this is probably something that diameter should do.
The peer state machine's election process (section 5.6.4) isn't implemented as specified since it assumes knowledge of a peer's Origin-Host before sending it a CER. (The identity becoming known upon reception of CEA.) The possibility of configuring the peer's Origin-Host could be added, along with handling of the case that it sends something else, but for many applications this will just be unnecessary configuration of a value that it has no control over.

A more detailed commentary on RFC 6733 follows. Its purpose is to (hopefully) clarify not only