Re: [Taps] Some comments on draft-ietf-taps-impl-12

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Sat, 06 August 2022 07:29 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 B5913C159485; Sat, 6 Aug 2022 00:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 4yDRQZxGil7L; Sat, 6 Aug 2022 00:29:10 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 25850C157B3B; Sat, 6 Aug 2022 00:29:07 -0700 (PDT)
Received: from [192.168.1.64] (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id A7F4F1B000FA; Sat, 6 Aug 2022 08:29:02 +0100 (BST)
Message-ID: <bd0be39a-ca60-6269-df58-959d60fdaebb@erg.abdn.ac.uk>
Date: Sat, 6 Aug 2022 08:29:01 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
To: Fernando Gont <fgont@si6networks.com>, draft-ietf-taps-impl@ietf.org
Cc: taps@ietf.org
References: <44f25f19-8ef4-8113-d854-0457e5ade6d6@si6networks.com> <91cd7c54-9f0f-1f48-d2e7-22b9d2bcf428@erg.abdn.ac.uk> <257d155e-03f1-6657-ab04-1aaad0cd5f02@si6networks.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
In-Reply-To: <257d155e-03f1-6657-ab04-1aaad0cd5f02@si6networks.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/fdcWLzNxQsI9PWp8U_P6VcFzeKo>
Subject: Re: [Taps] Some comments on draft-ietf-taps-impl-12
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 06 Aug 2022 07:29:11 -0000

On 05/08/2022 21:40, Fernando Gont wrote:
> Hi, Gorry,
>
> Thanks for all your responses! In-line....
>
> On 5/8/22 12:00, Gorry Fairhurst wrote:
>>>
>>> Section 4.7.2.:
>>>> On platforms with facilities to create a "virtual connection" for
>>>> connectionless protocols implementations should use these mechanisms
>>>> to minimise the handling of datagrams intended for already created
>>>> Connection objects.
>>>
>>> I don't necessarily disagree, but you should probably elaborate here 
>>> -- e.g., on one hand, "stateless" is good in the sense that you 
>>> don't tie system resources unnecessarily. However, it's also more 
>>> prone to spoofing, to the extent that an attacker might require "a 
>>> lot of work" from a server without even proving that it can receive 
>>> the return packets.
>>
>> I'm not quite sure what you are asking here. What I think was 
>> intended was very similar to the way UDP sockets in BSD can be used 
>> with "connect", is there something else you were expecting to see in 
>> the text?
>
> Looks like I got confused -- my bad, sorry! -- No changes expected here.
>
> Thanks,

OK, no problem we'll cross this one off. Thanks for the review though.

Gorry