IPsec Delivery Delay Detection

Document Type Expired Internet-Draft (individual)
Last updated 2018-09-06 (latest revision 2018-03-05)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This memo describes a one-way measurement of an IPsec packet edge-to- edge delay. Delay detection is enabled by a sender of an IPsec packet that includes a timestamp declaring the time at which it was sent. The receiver of the datagram can then judge how recently it was sent and choose a policy action, which could include discarding packets deemed to be 'too old' (having a timestamp too far into the past) or 'too new' (having a timestamp that is too far into the future). This provides a freshness policy check, which can be valuable irrespective of whether the IPsec policy also includes replay protection.


Brian Weis (bew@cisco.com)
Umesh Mangla (umangla@juniper.net)
Thomas Karl (thomas.karl@telekom.de)
Nilesh Maheshwari (nileshm@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)