[tcpm] Test vectors for RFC5925 algorithms?

juhamatk@gmail.com Tue, 31 March 2020 10:44 UTC

Return-Path: <juhamatk@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3477B3A1FC0 for <tcpm@ietfa.amsl.com>; Tue, 31 Mar 2020 03:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FftWEgQ38hd8 for <tcpm@ietfa.amsl.com>; Tue, 31 Mar 2020 03:44:19 -0700 (PDT)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9DF73A1FC7 for <tcpm@ietf.org>; Tue, 31 Mar 2020 03:44:17 -0700 (PDT)
Received: by mail-wm1-x32f.google.com with SMTP id t128so1916695wma.0 for <tcpm@ietf.org>; Tue, 31 Mar 2020 03:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/j+QNAoC7Y7IoTl0gYAVRux7dMool2EtqMseUj4slIw=; b=Ww3dlqbNmWXqcWw5Cft5GBlYEAAkh/lN1e6oX7g9gM/NIwJjc3hJgsoHCJuRmbwZDL or8kq1SC30nyEBCrr7BtV8tAs8lUy0uI2e1d43A36QCFOyjYDOKLe1j7ZeiZgX6OzvL/ CC/NwljvTkTogDssofMn0OgrspB+IDq6ANoLtOhJIvzbRA3ipalSGzC2d/zPxuRgdWY6 e2LxyHzOALB9jnyXDxXF+Nsa/4klB8m4jH2ZfRkNg7Jm081xRoF9xk91y+R0bDaja+PL oON8eMcWRm4psx+ZFzyEB/g4dtpW0hnFRN10Pm7xUxYa/eR8hWY0+OGSGlQDy0x0Gy+A YklQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/j+QNAoC7Y7IoTl0gYAVRux7dMool2EtqMseUj4slIw=; b=bD3y5M8qNP/+SEgl+mh8vQHz59nMvn+4uUdG+jL4XKFG3n4m8bau4yQM8p3YeZnMEi Q0BBZOt+K039c8PzhNIn+FSy6HY1Fulm5ZzN8pE6PQdzoLlRbYYpY+ZGUPNyOLOb0j8/ BsKNVpApwMqdG1dIQC2Ya5LtvABVE/3MUyjWckSvYkBHT0tepWhN3t6SI7rUZzonaEUt Pss7Nj8dpiDnC91dnbVHgAXi9j2DuzEDaWWbo7p1p9v1W3GX1Cpfh0D3oKgiRUcnpbJu XxcKLGdWg8vdYMODrxUR57P4WZsklZ5bavWYwnORJAhYlEUnbR4KtXUT/bPxKvItJbZx SrQg==
X-Gm-Message-State: ANhLgQ18jYfejBJXs3ZZ0OQcCW0i51eYQmsdADSm9T1Pujmi33+ia44B dOrtV+D7jZmSTSnKRtKdxA9GZC50lRZVCSdivpaaE1dg
X-Google-Smtp-Source: ADFU+vuSf72c3lTtfSQl9/O1innRaHF4YjZTAvV72lRe980B02HP2ChhhjtJqSVsP0hmiuIDCF8AeJjWioJdZf4+dfU=
X-Received: by 2002:a1c:23d6:: with SMTP id j205mr2778136wmj.22.1585651455820; Tue, 31 Mar 2020 03:44:15 -0700 (PDT)
MIME-Version: 1.0
From: juhamatk@gmail.com
Date: Tue, 31 Mar 2020 13:44:04 +0300
Message-ID: <CACS3ZpCawjTF4YMg+Rm7pOkjO2NQB-BZLBvobZCg2kyRQgaNzw@mail.gmail.com>
To: tcpm@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/gmeqGkNXeFT5Vc3rEyqjjmIo8jE>
Subject: [tcpm] Test vectors for RFC5925 algorithms?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2020 10:44:20 -0000

Hello,

I have been searching for test vectors for RFC5925/5926 algorithms for
TCP AO and to my surprise it seems that such do not exist. Am I
correct here?

Even though test vectors for HMAC SHA1 (RFC2202) and AES CMAC
(RFC4493) are available, it would be useful to have example test
vectors for frames using TCP AO - otherwise implementations end up
easily not to match. As RFC5925 is 47 pages, there is a room for error
and only one mismatch is needed for MACs not to match.

I think publishing a new RFC for them would be good, but probably
takes some time. Even unofficial, but verified, test vectors on some
specified example frames (with and without TCP options), e.g. on this
mailing list or otherwise, would be a very good start to get TCP AO
more widely implemented. If such already are available somewhere,
please do let me know.

Thanks,
--
 Juhamatti