RFC 7717: IKEv2-Derived Shared Secret Key for the One-Way Active Measurement Protocol (OWAMP) and Two-Way Active Measurement Protocol (TWAMP)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC7717
- Published
- December 2015
- Authors
- K. Pentikousis; E. Zhang; Y. Cui
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7718Registries for the One-Way Active Measurement Protocol (OWAMP)Current
December 2015
- RFC 7719DNS TerminologyObsoleted
December 2015
- RFC 7707Network Reconnaissance in IPv6 NetworksCurrent
March 2016
- RFC 7706Decreasing Access Time to Root Servers by Running One on LoopbackObsoleted
November 2015
- RFC 7690Close Encounters of the ICMP Type 2 Kind (Near Misses with ICMPv6 Packet Too Big (PTB))Current
January 2016
- RFC 7747Basic BGP Convergence Benchmarking Methodology for Data-Plane ConvergenceCurrent
April 2016
- RFC 7686The ".onion" Special-Use Domain NameCurrent
October 2015
- RFC 7750Differentiated Service Code Point and Explicit Congestion Notification Monitoring in the Two-Way Active Measurement Protocol (TWAMP)Current
February 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?