[Taps] NEAT's abstract API: an old snapshot showing our design process
Michael Welzl <michawe@ifi.uio.no> Fri, 17 March 2017 16:41 UTC
Return-Path: <michawe@ifi.uio.no>
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 BED741294CA for <taps@ietfa.amsl.com>; Fri, 17 Mar 2017 09:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 YkgQ1cnAC7l9 for <taps@ietfa.amsl.com>; Fri, 17 Mar 2017 09:41:32 -0700 (PDT)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (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 2EA13129462 for <taps@ietf.org>; Fri, 17 Mar 2017 09:41:32 -0700 (PDT)
Received: from mail-mx02.uio.no ([129.240.10.43]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1couwU-0000SB-DI for taps@ietf.org; Fri, 17 Mar 2017 17:41:30 +0100
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx02.uio.no with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1couwT-0003DQ-NC for taps@ietf.org; Fri, 17 Mar 2017 17:41:30 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <735DD439-E086-4294-86F3-3B9DCE7F7924@ifi.uio.no>
Date: Fri, 17 Mar 2017 17:41:29 +0100
To: taps WG <taps@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx02.uio.no: 129.240.68.135 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.68.135; envelope-from=michawe@ifi.uio.no; helo=boomerang.ifi.uio.no;
X-UiO-Ratelimit-Test: rcpts/h 3 msgs/h 3 sum rcpts/h 5 sum msgs/h 5 total rcpts 52871 max rcpts/h 54 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=0.008, RP_MATCHES_RCVD=-0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 5DE2F4DD8D8E8A01A4C53F635314C043AC333393
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 12678 max/h 21 blacklist 0 greylist 0 ratelimit 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/_tO0uPbcy0A7qkFTTi5NCyyDNsI>
Subject: [Taps] NEAT's abstract API: an old snapshot showing our design process
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 17 Mar 2017 16:41:35 -0000
Dear all, I'm writing this on behalf of the NEAT project: We have decided to release a relatively old snapshot of a document that is continuously evolving (our "deliverable D1.2"), just to give folks an idea about the design process that we use to develop our own API. It's about how we get from IETF drafts (and, in our case, also requirements derived from use cases) to running code. We thought that this would be of interest to the TAPS community - here's the link: https://www.neat-project.org/2017/03/abstract-api-description-released/ Again, I'd like to stress that this does *not* capture the current state of NEAT - it captures a significantly older state of it, in the form of an abstract API, illustrating our design process. (our concrete API is also quite different in style - many of the "primitives" in this abstract API are just elements of a data structure in our actual call-back-based implementation). With this, I wish y'all a nice weekend, Michael
- [Taps] NEAT's abstract API: an old snapshot showi… Michael Welzl