IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP), December 2015
- File formats:
- PROPOSED STANDARD
- RFC 4656, RFC 5357
- K. Pentikousis, Ed.
- ippm (tsv)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
The One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP) security mechanisms require that both the client and server endpoints possess a shared secret. This document describes the use of keys derived from an IKEv2 security association (SA) as the shared key in OWAMP or TWAMP. If the shared key can be derived from the IKEv2 SA, OWAMP or TWAMP can support certificate-based key exchange; this would allow for more operational flexibility and efficiency. The key derivation presented in this document can also facilitate automatic key management.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.