Release v1.2.0 - 5GMS Application Function

Release v1.2.0

Major changes in this release:

• Implementation of the interfaces at reference point M1 for:
  • Provisioning Session (TS 26.512 clauses 4.3.2 & 7.2)
  • Content Protocols Discovery (TS 26.512 clauses 4.3.4 & 7.5)
  • Server Certificates (TS 26.512 clauses 4.3.6 & 7.3)
  • Content Hosting Configuration (TS 26.512 clauses 4.3.3 & 7.6)
• Removal of stream configuration from the msaf.yaml configuration file.
• Improvement of server headers for all API interfaces:
  • Addition of an ETag header to identify data instances.
  • Addition of a Last-Modified header to indicate the change date of the data.
  • Addition of a Cache-Control header with max-age field to indicate cache time.
  • Server header now indicates the 5GMSd AF name and major API version used with the individual API interface details held in a comment field in the same header.
• Introduction of an m1-session tool for managing stream configuration at runtime.
  • Management of Provisioning Sessions, Certificates and Content Hosting.
  • Querying of available downlink/uplink protocols.
  • Pluggable certificate signing class to allow easy enhancement with custom signing.

Testing of the new M1 API interfaces is described in the "Testing the M1 Interface" wiki page. Other testing wiki pages have been updated to use the new m1-session tool for configuration. The information on "Testing as a Local User" has also been updated in the wiki to include extra instruction needed to use the new m1-session tool when testing in a temporary development deployment.

What's Changed

• Feature: M1 provisioning by @davidjwbbc in #53
• Various fixes for issues found while writing up the testing by @davidjwbbc in #54
• Bug fixes and final improvements before v1.2.0 Release Candidate by @davidjwbbc in #56

Full Changelog: rt-5gms-application-function-v1.1.0...rt-5gms-application-function-v1.2.0