IETF Logo Mail Archive

Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-31.txt

"touch@strayalpha.com" <touch@strayalpha.com> Wed, 06 March 2024 14:29 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 8C4D4C14F689 for <tsvwg@ietfa.amsl.com>; Wed, 6 Mar 2024 06:29:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.325
X-Spam-Level:
X-Spam-Status: No, score=-6.325 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 vTyDvwys657s for <tsvwg@ietfa.amsl.com>; Wed, 6 Mar 2024 06:28:59 -0800 (PST)
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 A4CFCC14F683 for <tsvwg@ietf.org>; Wed, 6 Mar 2024 06:28:59 -0800 (PST)
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=adqW2DpV+DwuC+S0rEYxVL2Lo94Mnhi40G44O6p4biA=; b=rfRsvI+whqvWIFJj9NsY0PVdVI noUUMckyfPs6TB1ufOg1cwnl6JivaGnaN9HYDEeJsYsNVPf4tJpaSW2/VkZ82c62DHXFAEgsnwJv9 HUU3Hd2AtBYfi+1H5mEiZYA6JChCW1n4qQcIVa3DL7pBN9eegvNsoTooo7D6IFqI9wG9ivIYOsWne 6lIh4wneXY5O9ec5qU1pVUCSXkqd95C54etgYk8kXMQWPQLevdrfcuqYexvxAwHVrROexc8uXB2SR h9fDB2/ycgxWtmOh00yagZ2NnmGwYsdB0vg9QFs9l8iUQQ0TdywfMzPGrPLVCPhFVuAW4TCw9iWkh eFrcc+Ng==;
Received: from [172.56.187.185] (port=14715 helo=smtpclient.apple) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <touch@strayalpha.com>) id 1rhsGJ-000yGl-2U; Wed, 06 Mar 2024 09:28:56 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_0FFA6302-BA63-4BAE-8935-3809F36EB375"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
From: "touch@strayalpha.com" <touch@strayalpha.com>
In-Reply-To: <CACL_3VH9VLVh99ZCWz2oN4yvQf_bGjyK6WCqc7nP5TT3n6t1AA@mail.gmail.com>
Date: Wed, 06 Mar 2024 06:28:38 -0800
Cc: "Gorry (erg)" <gorry@erg.abdn.ac.uk>, Tom Herbert <tom@herbertland.com>, TSVWG <tsvwg@ietf.org>
Message-Id: <5CCDE98E-35F3-4A38-8C47-96C7CAC6A090@strayalpha.com>
References: <CALx6S37S61eKrPTefdBTKfw=BoV31_C4nwadP+QxrctfduF0iw@mail.gmail.com> <E82B3F27-CD79-4ED0-9FE6-27CAAB8E41AE@erg.abdn.ac.uk> <CACL_3VH9VLVh99ZCWz2oN4yvQf_bGjyK6WCqc7nP5TT3n6t1AA@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
X-Mailer: Apple Mail (2.3774.400.31)
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/Nw_YSCywMLwbx-OBfAMGHWNo_rI>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-31.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 06 Mar 2024 14:29:03 -0000

+1

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com

> On Mar 6, 2024, at 6:14 AM, C. M. Heard <heard@pobox.com> wrote:
> 
> On Wed, Mar 6, 2024 at 1:10 AM Gorry (erg) wrote:
>> My suggestion is that we do not need to add a new UDP requirement, but to say something like:
>> 
>> Section 3.4 of RFC 8085 advises developers to use additional payload protection when “  where data integrity is important”.
>> 
>> The APC option can be used to provide this by applications  enabling this at the sender and also requiring the presence of a valid APC crc at the receiver.
>> 
>> Gorry (as a WG member, not a chair)
> 
> +1
> 
> Mike Heard

v2.23.0 | Report a Bug | By Email