IPsec Delivery Delay Detection
draft-weis-delay-detection-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Brian Weis , Umesh Mangla , Thomas Karl , Nilesh Maheshwari | ||
| Last updated | 2018-09-06 (Latest revision 2018-03-05) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
Brian Weis
Umesh Mangla
Thomas Karl
Nilesh Maheshwari
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)