IETF Logo Mail Archive

[IPsec] rfc 8750 question

Robert Moskowitz <rgm-sec@htt-consult.com> Tue, 10 May 2022 03:08 UTC

Return-Path: <rgm-sec@htt-consult.com>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0385C15E6C6 for <ipsec@ietfa.amsl.com>; Mon, 9 May 2022 20:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SQyFjzGQNAZg for <ipsec@ietfa.amsl.com>; Mon, 9 May 2022 20:08:57 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2001C15E6C4 for <ipsec@ietf.org>; Mon, 9 May 2022 20:08:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id DDCC16247F for <ipsec@ietf.org>; Mon, 9 May 2022 23:08:09 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KwDvf0d+4iB4 for <ipsec@ietf.org>; Mon, 9 May 2022 23:08:06 -0400 (EDT)
Received: from [192.168.160.11] (unknown [192.168.160.11]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 6501962434 for <ipsec@ietf.org>; Mon, 9 May 2022 23:08:06 -0400 (EDT)
Message-ID: <432fd973-212c-00b3-48a1-9de81129d6eb@htt-consult.com>
Date: Mon, 09 May 2022 23:08:49 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
To: ipsec@ietf.org
Content-Language: en-US
From: Robert Moskowitz <rgm-sec@htt-consult.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipsec/Cr1Vb6wVtjsHcRmB-oEa608CHg0>
Subject: [IPsec] rfc 8750 question
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipsec/>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2022 03:08:59 -0000

I just noticed that 8750 defines one algorithm number for aes-gcm:

  30     | ENCR_AES_GCM_16_IIV        | RFC 8750

But rfc 4106 defined 3:

       18 for AES-GCM with an 8 octet ICV;
       19 for AES-GCM with a 12 octet ICV; and
       20 for AES-GCM with a 16 octet ICV.


so for 8750, what is the ICV length?

Trying to figure out the packet size with diet-esp...

thanks

v2.23.0 | Report a Bug | By Email