IETF Logo Mail Archive

Re: [tsvwg] design assumptions - draft-ietf-udp-options

Joe Touch <touch@strayalpha.com> Thu, 18 July 2019 00:09 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEFF1202D3 for <tsvwg@ietfa.amsl.com>; Wed, 17 Jul 2019 17:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.218
X-Spam-Level:
X-Spam-Status: No, score=-1.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 xhxId4em8q7a for <tsvwg@ietfa.amsl.com>; Wed, 17 Jul 2019 17:09:33 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 4B5211201DA for <tsvwg@ietf.org>; Wed, 17 Jul 2019 17:09:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=EI1H4tcJQ081h4L6gfEVitf0wtjCjHddCSRjyLUYNio=; b=l2BA2hzC5OP50x8iPGJBlPq7b kEAzDWSfgR3xwNadwib/3hx+F2YcD4ju4Rwt39k1Calqyr4bv4dMWkvJSNSSEz3ZXfnytL3ZLXQlX auFbKAue3073X1tmU1M7o8lNPRcODLSM6WYN2rJ54sHGVTJMliK/wEE89UiNd46qDEXrpRrFNkTQD QpL67IJ2y5udTI2eMbNM2xoC18W/qrALly7kZ1lcfTIfaWI9PwFptrNYWxpY1XI4ObasCOuKCdWID Za6brhTcVqaD122A6C1ATejYNlIHMwtiV3uAGrSdaaxzFvTxHAl4OSn44iuhejcJEiAQMOv7VtprU SPyEYnlMA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:50290 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hntzD-003BQh-SC; Wed, 17 Jul 2019 20:09:32 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_68B37061-04F1-4622-ACEB-A7EAA1658F1E"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CALx6S345v5AMb4s59S0r7qCU_AzMtLMu2vscU3A2xea9UUVFPQ@mail.gmail.com>
Date: Wed, 17 Jul 2019 17:09:26 -0700
Cc: Derek Fawcus <dfawcus+lists-tsvwg@employees.org>, tsvwg <tsvwg@ietf.org>
Message-Id: <4D01988C-0EC1-4033-9BEA-719AA87B492C@strayalpha.com>
References: <CALx6S37wOkz0436CmevOjSe=VwAxKstSR9Jc66PUmXwUKK4vBw@mail.gmail.com> <075C3166-DF88-4160-8E6C-1C32511F4D46@strayalpha.com> <811C4C35-48D8-4382-A4B4-784FAC1B9F1D@strayalpha.com> <CE03DB3D7B45C245BCA0D2432779493630620745@MX307CL04.corp.emc.com> <80BB381B-9B2F-4ACF-9F3A-27E7B8B10AC2@strayalpha.com> <CE03DB3D7B45C245BCA0D24327794936306212A0@MX307CL04.corp.emc.com> <CACL_3VGS8-3susS-qm3oDD3=fwT6QmRa4_hgceJKhqjz3n+H5Q@mail.gmail.com> <CALx6S37GyRuVtoERrp1bDr3iCj0tZwGFH5CEsBJG3t0seii=3w@mail.gmail.com> <deae8d1cb6f4af0086a2b48f11a6886d@strayalpha.com> <CACL_3VGdJRJDLLxN6ODtqG3+9X3RkZMWMSo9GMhqWVXhjnxf3w@mail.gmail.com> <20190717212220.GA19997@clarinet.employees.org> <CALx6S345v5AMb4s59S0r7qCU_AzMtLMu2vscU3A2xea9UUVFPQ@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/yeTHgiQ55stcu81vFlEhJzjwGCk>
Subject: Re: [tsvwg] design assumptions - draft-ietf-udp-options
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2019 00:09:34 -0000


> On Jul 17, 2019, at 2:30 PM, Tom Herbert <tom@herbertland.com> wrote:
> 
> For instance, I don't believe TCP-AO has gained much traction.

Agreed, but that’s because vendors are continuing to use the deprecated TCP MD5 instead.

> Also, it's hard to tell where this starts to compete with IPsec.

That’s explained in RFC 5925. It matters more for things like BGP for TCP.

For UDP, its use isn’t particularly clear; it’s included only because it’s easy to model after TCP-AO (which is really just a more general version of TCP MD5, except for key change signaling that isn’t applicable for UDP anyway).

Joe

v2.23.0 | Report a Bug | By Email