Re: [tcpm] Test vectors for RFC5925 algorithms?

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Mon, 08 June 2020 07:21 UTC

Return-Path: <Michael.Scharf@hs-esslingen.de>
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 CB3AF3A0912 for <tcpm@ietfa.amsl.com>; Mon, 8 Jun 2020 00:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hs-esslingen.de
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 3rPoL0hzd9Nc for <tcpm@ietfa.amsl.com>; Mon, 8 Jun 2020 00:21:40 -0700 (PDT)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB5FA3A090D for <tcpm@ietf.org>; Mon, 8 Jun 2020 00:21:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id B69B825A1C; Mon, 8 Jun 2020 09:21:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1591600897; bh=htK8E2IwXQ0wukELncf+TtqxKJ9vZG5nM+V+kkT4HIc=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=TDmI3hzWmN75EGF5i0PIBr6Shm7htYQgIYj2epaozIZlnWLe1X8M87YE6W1qGtdxY m6/vXvK6V/SBAt4UzB/LRc2ypWWhqRt8F45sTvLrb5m/tgxsKdORXEmI5X/KamfzR2 4PPpsBbIr20ruLaQ2tXCifpmpxpRMGle+OAqqNTk=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mivtyZu0c_7; Mon, 8 Jun 2020 09:21:35 +0200 (CEST)
Received: from rznt8101.rznt.rzdir.fht-esslingen.de (rznt8101.rznt.rzdir.fht-esslingen.de [134.108.29.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Mon, 8 Jun 2020 09:21:35 +0200 (CEST)
Received: from RZNT8114.rznt.rzdir.fht-esslingen.de ([169.254.3.171]) by rznt8101.rznt.rzdir.fht-esslingen.de ([fe80::bd73:d6a9:24d7:95f1%10]) with mapi id 14.03.0468.000; Mon, 8 Jun 2020 09:21:35 +0200
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: Joseph Touch <touch@strayalpha.com>
CC: "juhamatk@gmail.com" <juhamatk@gmail.com>, "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: [tcpm] Test vectors for RFC5925 algorithms?
Thread-Index: AQHWB0lfUk5cDvT0M0+o4ytgvsbwRKhi6ecAgADUtQCAACc4sIABaoiAgBa48iCAUeGkgIAAz7LA
Date: Mon, 08 Jun 2020 07:21:34 +0000
Message-ID: <6EC6417807D9754DA64F3087E2E2E03E2DC3B40E@rznt8114.rznt.rzdir.fht-esslingen.de>
References: <CACS3ZpCawjTF4YMg+Rm7pOkjO2NQB-BZLBvobZCg2kyRQgaNzw@mail.gmail.com> <AFABEFAB-AA58-4599-94E3-06889E38DC01@strayalpha.com> <CACS3ZpAqdeF6xivndh7EqOqwYebyziyP6AQkKVWZww6nC=Zo0Q@mail.gmail.com> <6EC6417807D9754DA64F3087E2E2E03E2DA4B5C7@rznt8114.rznt.rzdir.fht-esslingen.de> <CACS3ZpAyYahfCfibCKwZkb6u3VAk2UiXViMGbdH3t76iUyY5fw@mail.gmail.com> <6EC6417807D9754DA64F3087E2E2E03E2DA73D5B@rznt8114.rznt.rzdir.fht-esslingen.de> <CE38B4DB-63FB-4C34-A064-EA87E22AA689@strayalpha.com>
In-Reply-To: <CE38B4DB-63FB-4C34-A064-EA87E22AA689@strayalpha.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.108.48.165]
Content-Type: multipart/alternative; boundary="_000_6EC6417807D9754DA64F3087E2E2E03E2DC3B40Erznt8114rzntrzd_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/Lq4OCv4AS6Kj6PTG2iQJ9wqrgFo>
Subject: Re: [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: Mon, 08 Jun 2020 07:21:42 -0000

Hi Joe,

Page 700 of link [1] references RFC 5925 and RFC 5926.

I don’t have access to a Nokia router to actually test the implementation. Yet, as far as I know, listing an RFC in the standard compliance lists of a Nokia product implies that the standard is indeed implemented.

Michael

From: Joseph Touch <touch@strayalpha.com>
Sent: Sunday, June 7, 2020 10:52 PM
To: Scharf, Michael <Michael.Scharf@hs-esslingen.de>
Cc: juhamatk@gmail.com; tcpm@ietf.org
Subject: Re: [tcpm] Test vectors for RFC5925 algorithms?

Hi, Michael,

The link below doesn’t appear to reference TCP-AO. Do you know of a link with a more direct reference?

Joe


On Apr 16, 2020, at 9:31 AM, Scharf, Michael <Michael.Scharf@hs-esslingen.de<mailto:Michael.Scharf@hs-esslingen.de>> wrote:

Have you checked other router vendors? For instance, the public Cisco IOS XE
documentation lists TCP-AO support. And I have also heard that another main
router vendor may implement TCP-AO (well, I am not familiar with Juniper).

I am aware that Cisco has an implementation. It is quite new, and
unfortunately I do have experience of it. If someone has, then that
may well be a very good candidate for test vectors.

Coming back to this, as I have just found another document: According to reference [1], Nokia SROS implements TCP-AO as well.

Michael


[1] Nokia SROS documentation at https://documentation.nokia.com/cgi-bin/dbaccessfilename.cgi/3HE15811AAAATQZZA01_V1_7450%20ESS%207750%20SR%207950%20XRS%20and%20VSR%20Basic%20System%20Configuration%20Guide%2020.2.R1.pdf