IETF Logo Mail Archive

Re: [Taps] Opsdir telechat review of draft-ietf-taps-transport-security-11

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Thu, 16 April 2020 16:25 UTC

Return-Path: <Michael.Scharf@hs-esslingen.de>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12EDE3A0D86; Thu, 16 Apr 2020 09:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 T_kPsShA9vCW; Thu, 16 Apr 2020 09:25:32 -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 589AB3A0DC8; Thu, 16 Apr 2020 09:18:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 6318525A12; Thu, 16 Apr 2020 18:18:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1587053914; bh=LNCpqJ8w8Qt470tW2PYDJ5RL6iF/57l8c0I4bXFK/rg=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=ufMzuKf9V8vUDjmrRKfOhgKz2ssmIxy4dcocYJZ3zn4t6n/QvhhNjcVWraJNlklZW IGYrpaYELsZjI843f+5Im2WPzBPlJq10fLbvvisvEdNscIEFgd4oa9Fn8r101Vzopd Z6X141VtbRejJeltCRxc6T8/w8KQVbp98Ceb0QZ8=
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 vA-MZ4SPFLM4; Thu, 16 Apr 2020 18:18:32 +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; Thu, 16 Apr 2020 18:18:32 +0200 (CEST)
Received: from RZNT8114.rznt.rzdir.fht-esslingen.de ([169.254.3.209]) by rznt8101.rznt.rzdir.fht-esslingen.de ([fe80::bd73:d6a9:24d7:95f1%10]) with mapi id 14.03.0468.000; Thu, 16 Apr 2020 18:18:32 +0200
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: Joseph Touch <touch@strayalpha.com>, Susan Hares <shares@ndzh.com>
CC: "last-call@ietf.org" <last-call@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-taps-transport-security.all@ietf.org" <draft-ietf-taps-transport-security.all@ietf.org>, "taps@ietf.org" <taps@ietf.org>
Thread-Topic: [Taps] Opsdir telechat review of draft-ietf-taps-transport-security-11
Thread-Index: AQHWFAQoq8z0cso+UkeJRH+eZgOe7Kh76cgQ
Date: Thu, 16 Apr 2020 16:18:32 +0000
Message-ID: <6EC6417807D9754DA64F3087E2E2E03E2DA73BD7@rznt8114.rznt.rzdir.fht-esslingen.de>
References: <158703333468.25896.8984664151253035199@ietfa.amsl.com> <87F84D2D-ED5D-445A-ABA3-416AD0F3F9BD@strayalpha.com>
In-Reply-To: <87F84D2D-ED5D-445A-ABA3-416AD0F3F9BD@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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/4F3SieGlv7QwmuVSn0hpdb_z6OA>
Subject: Re: [Taps] Opsdir telechat review of draft-ietf-taps-transport-security-11
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Apr 2020 16:25:35 -0000

> Hi, Susan,
> 
> > On Apr 16, 2020, at 3:35 AM, Susan Hares via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Reviewer: Susan Hares
> > ...
> > Personal plea:
> > You've clear stated the BGP issue up front.
> > TCP MD5 is bad (due to privacy issues) and TCP-AO
> > is not deployed..
> 
> It is available in Cisco IOS at least. Its biggest drawback appears to be a lack of
> open-source implementations.

According to reference [1], Nokia SROS implements TCP-AO as well. As far as I can see, RFC 5925 and RFC 5926 are explicitly listed as supported in [1].

So, apparently two major router vendors have running code for TCP-AO.

But this seems really off-topic for draft-ietf-taps-transport-security.

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


> >  Has the TAPs given any thought to
> > what might be  a replacement that could utilize some of the modern
> > TCP.
> 
> Given the problem with TCP-AO deployment is that there is no free
> implementation and low implementation by vendors, how exactly would a new
> solution with even less implemented code help?
> 
> Joe
> _______________________________________________
> Taps mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

v2.23.0 | Report a Bug | By Email