Content for TR 29.819 Word version: 13.0.0
2 References
3 Definitions, symbols and abbreviations
4 General
5 Changes from IETF RFC 3588
6 Conclusions and recommendations
$ Change History
2 References p. 6
3 Definitions, symbols and abbreviations p. 7
3.1 Definitions p. 7
3.2 Abbreviations p. 7
4 General p. 7
4.1 Introduction p. 7
4.2 Objectives p. 7
5 Changes from IETF RFC 3588 p. 8
5.1 Introduction p. 8
5.2 Major Changes p. 8
5.2.1 Change in the Security Model p. 8
5.2.1.1 Description of the change p. 8
5.2.1.1.1 TLS/DTLS as mandatory to support p. 8
5.2.1.1.2 Deprecating the use of the Inband-Security AVP p. 8
5.2.1.1.3 Deprecating the E2E security framework p. 9
5.2.1.2 Backward compatibility with IETF RFC 3588 p. 9
5.2.1.3 Impacts on 3GPP specifications p. 9
5.2.1.4 Conclusion p. 10
5.2.2 Use of the Vendor-Specific-Application-ID p. 11
5.2.2.1 Description of the change p. 11
5.2.2.2 Backward compatibility with IETF RFC 3588 p. 11
5.2.2.3 Impacts on 3GPP specifications p. 12
5.2.2.4 Conclusion p. 12
5.2.3 Deprecated the exchange of CER/CEA messages in the "Open" state p. 13
5.3 Other Changes p. 14
5.3.1 Changes and Clarifications of the rules for Diameter Extensibility p. 14
5.3.1.1 Description of the change p. 14
5.3.1.1.1 New Policies for IANA's Command Code Assignment p. 14
5.3.1.1.2 Clarifications the Diameter extensibility rules p. 15
5.3.1.2 Backward compatibility with IETF RFC 3588 p. 16
5.3.1.3 Impacts on 3GPP specifications p. 16
5.3.1.4 Conclusion p. 16
5.3.2 Simplified Diameter peer discovery p. 16
5.3.2.1 Description of the change p. 16
5.3.2.2 Backward compatibility with IETF RFC 3588 p. 17
5.3.2.3 Impacts on 3GPP specifications p. 17
5.3.2.4 Conclusion p. 17
5.3.3 Changes in the Command's CCF specifications p. 17
6 Conclusions and recommendations p. 19
6.1 Conclusions p. 19
6.2 Recommendations p. 21
$ Change History p. 22
