IETF Logo Mail Archive

Re: [Taps] Drive-by comments on draft-fairhurst-taps-transports-usage-udp-01

Joe Touch <touch@isi.edu> Thu, 07 April 2016 19:13 UTC

Return-Path: <touch@isi.edu>
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 B7D1412D547 for <taps@ietfa.amsl.com>; Thu, 7 Apr 2016 12:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 DemHNi3WW23L for <taps@ietfa.amsl.com>; Thu, 7 Apr 2016 12:13:33 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC87412D1F0 for <taps@ietf.org>; Thu, 7 Apr 2016 12:13:28 -0700 (PDT)
Received: from [207.151.56.219] (guest-wireless-207-151-056-219.usc.edu [207.151.56.219]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id u37JC1Ys026882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 7 Apr 2016 12:12:12 -0700 (PDT)
To: "Dale R. Worley" <worley@ariadne.com>
References: <87bn5ltg0s.fsf@hobgoblin.ariadne.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <5706B0FF.5090501@isi.edu>
Date: Thu, 07 Apr 2016 12:11:59 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <87bn5ltg0s.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/lCCzUooZMggFGukssdUZiKdmJFA>
Cc: gorry@erg.abdn.ac.uk, taps@ietf.org, touch@isi.edu
Subject: Re: [Taps] Drive-by comments on draft-fairhurst-taps-transports-usage-udp-01
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions on Transport Services <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, 07 Apr 2016 19:13:34 -0000


On 4/7/2016 11:44 AM, Dale R. Worley wrote:
> Joe Touch <touch@isi.edu> writes:
>> For connectionless protocols, "CONNECT" is often the basic primitive by
>> which a user indicates the socket pair (address/port) of the remote end.
> 
> The trouble I see is that the concept of "listening" is not covered.

It depends on what you mean by "listen".

If you mean "wait for a message", that's a "read"

If you mean "coordinate state with the other end", that is not part of
UDP semantics.

> The passive or listening endpoint doesn't initiate a "connect" operation
> to indicate the address/port of the remote end, that is indicated by the
> arrival of a packet from the remote end.  As I read the draft, it seems
> to assume that both ends can do a "connect" before they exchange any
> packets at all.

IMO that's a failure of the current text to match UDP semantics.

Joe

v2.23.0 | Report a Bug | By Email