IETF Logo Mail Archive

Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt

Joe Touch <touch@isi.edu> Mon, 10 October 2016 14:36 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 16B29129526 for <taps@ietfa.amsl.com>; Mon, 10 Oct 2016 07:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.896
X-Spam-Level:
X-Spam-Status: No, score=-9.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-2.996] 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 MN5G8n9o4Rj5 for <taps@ietfa.amsl.com>; Mon, 10 Oct 2016 07:36:30 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 C0289129479 for <taps@ietf.org>; Mon, 10 Oct 2016 07:36:30 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-251-17.socal.res.rr.com [172.250.251.17]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u9AEZTLv002962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 10 Oct 2016 07:35:31 -0700 (PDT)
To: "Gorry (erg)" <gorry@erg.abdn.ac.uk>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>
References: <147570039954.28203.15079213691092104439.idtracker@ietfa.amsl.com> <57F5FBCE.6080609@erg.abdn.ac.uk> <D0AEB91E-8E9F-4089-B599-9A8428A0642C@ifi.uio.no> <4E80BDBC-E3E5-4933-9315-3540DDCAA3A9@gmail.com> <2663468C-7687-40D8-9185-78C65FDE03FC@tik.ee.ethz.ch> <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <ab32eada-9fac-07a5-7438-268ee41a3680@isi.edu>
Date: Mon, 10 Oct 2016 07:35:28 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <982D00B7-4D14-4932-8A72-21548C6CE484@erg.abdn.ac.uk>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/v2YmUdq2EFQWuCnRZXi-iHRN2dM>
Cc: Aaron Falk <aaron.falk@gmail.com>, Michael Welzl <michawe@ifi.uio.no>, taps@ietf.org
Subject: Re: [Taps] New Version Notification for draft-fairhurst-taps-transports-usage-udp-03.txt
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: Mon, 10 Oct 2016 14:36:32 -0000


On 10/10/2016 3:15 AM, Gorry (erg) wrote:
> ... There is no document in the RFC series that document UDP API - this may be helpful roadmap to find this info. Two documents are easier to maintain and cite than one.

RFC1122 defines one in Section 4.1.4, but it basically points off to a
definition of the IP API in Section 3.4, which ignores the issue of
controlling source and destination ports.

The true UDP API ought to be defined in the same way the TCP API is
defined in RFC793, FWIW.

I've proposed a way forward for UDP options; as a result, I'd be glad to
take a shot at a draft UDP API doc if useful.

Joe

v2.23.0 | Report a Bug | By Email