...
| Question | Outcome |
|---|---|
| Default setting for Unencrypted SRTP? This is a boolean value that enable/disables receiving unencrypted SRTP packet payloads. | Thoughts are if a system has security features enabled to not allow non-secure calls. This settings are a nice to have. |
| Default setting for Unencrypted SRTCP? This is a boolean value that enable/disables receiving unencrypted SRTCP packet payloads. | |
| How are keys updated during a fax session. HMP selected a default Lifetime value to attempt to not update the key during a session. It does not prevent the remote sending from updating their keys. Do we want this to be configurable or do we just use a key per session with the large default setting? | The lifetime value should be set to the max and the parameter is a nice to have. |
There is a NULL invite and 3rd PCC use cases with the XMS. Are these use cases required for SR140? | This is not required. |
| Do we need to support multiple crypto keys? HMP has the ability to support multiple key rotation (up to 20) for a single session. Multiple crypto key rotation per session using Master Key Identifier (MKI) | No. Only a single key will be used. |
| Are we expecting the remote to updated their transmit key during a fax session (Lifetime expired)? | No. Expecting fax sessions to complete before lifetime expires. |
What about the enabling or disabling of SRTP authentication? | |
| Support switching between RTP to SRTP or SRTP to RTP in mid-session? | Again by default if SRTP is enabled then it should force SRTP encryption. No changing mid-session.
|
| Support setting the advance notification time (100 ms units) that the current encryption key is about to expire? | We should not need to switch keys during a session with the max lifetime setting. |
Support the setting of the thresholds for the SRTP alarms (authentication failure, packet replay detection and Master Key Identifier (MKI) mismatches)? | Will not be available in initial release. |
| Support enabling or disabling the advance notification time for key expiry and the SRTP alarms? | We should not need to switch keys during a session with the max lifetime setting. |
| Support changing the key derivation rate? | |
| Support different lifetimes for SRTP and SRTCP? Depending on whichever expires first, the key would then need to be changed. | We should not need to switch keys during a session with the max lifetime setting. |
| Support for F8_128_HMAC_SHA1_80? | This is a future requirement. |
Not Doing
Exploring Tasks
Due to time constraints, it was desided to not create a HLD but perform prototype work and document the exploration. The notes as part of the investagate are attacked to the appropiate JIRA tasks.
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|