Using compression in the Internet Key Exchange Protocol Version 2 (IKEv2)
draft-smyslov-ipsecme-ikev2-compression-04
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-09-07
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group V. Smyslov
Internet-Draft ELVIS-PLUS
Intended status: Standards Track September 7, 2017
Expires: March 11, 2018
Using compression in the Internet Key Exchange Protocol Version 2
(IKEv2)
draft-smyslov-ipsecme-ikev2-compression-04
Abstract
This document describes a method for reducing the size of the IKEv2
messages by using lossless compression. Making IKEv2 messages
smaller is desirable for low power consumption battery powered
devices. It also helps to avoid IP fragmentation of IKEv2 messages.
This document describes how compression is negotiated maintaining
backward compatibility and how it is used in IKEv2.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 11, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
Smyslov Expires March 11, 2018 [Page 1]
Internet-Draft Compression in IKEv2 September 2017
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Description . . . . . . . . . . . . . . . . . . . . 3
3.1. Using Compression in the IKE_SA_INIT Exchange . . . . . . 4
3.2. Using Compression in Subsequent Exchanges . . . . . . . . 6
4. Payload Formats . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Compressed Payload . . . . . . . . . . . . . . . . . . . 7
4.2. INVALID_COMPRESSION_ALGORITHM Notification . . . . . . . 8
5. Interaction with other IKEv2 Extensions . . . . . . . . . . . 8
5.1. Interaction with IKEv2 Fragmentation . . . . . . . . . . 9
5.2. Interaction with IKEv2 Resumption . . . . . . . . . . . . 9
5.3. Interaction with IKEv2 Redirect . . . . . . . . . . . . . 9
5.4. Interaction with IKEv2 Puzzles . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
8.1. Normative References . . . . . . . . . . . . . . . . . . 10
8.2. Informative References . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The Internet Key Exchange protocol version 2 (IKEv2) defined in
[RFC7296] is used in the IP Security (IPsec) architecture for the
purposes of Security Association (SA) parameters negotiation and
authenticated key exchange. The protocol uses UDP as a transport for
its messages. The size of the IKEv2 messages varies from hundreds
bytes to several kBytes.
Sending large UDP messages may cause IP fragmentation to take place,
which may interact badly with some Network Address Translators (NAT).
One of the possible solutions to the problem is IKEv2 fragmentation
described in [RFC7383]. However, the IKEv2 fragmentation cannot be
used for unencrypted messages and thus cannot be used in the initial
IKEv2 exchange (IKE_SA_INIT). Usually the messages of the
IKE_SA_INIT exchange are relatively small and this restriction
doesn't cause problems. However with adoption more and more new
algorithms and new IKEv2 extensions there is a tendency for these
Show full document text