IETF Logo Mail Archive

Re: [Taps] IETF planning

Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com> Tue, 27 October 2015 09:44 UTC

Return-Path: <karen.nielsen@tieto.com>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C76361A6F2B for <taps@ietfa.amsl.com>; Tue, 27 Oct 2015 02:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level:
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001] autolearn=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 p-S5iOgRRwpr for <taps@ietfa.amsl.com>; Tue, 27 Oct 2015 02:44:52 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 5B9FC1A6EED for <taps@ietf.org>; Tue, 27 Oct 2015 02:44:52 -0700 (PDT)
Received: by iofz202 with SMTP id z202so214339721iof.2 for <taps@ietf.org>; Tue, 27 Oct 2015 02:44:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Z4XrJtrIbM0vK085jZ5Zl/rnXcJsFqnBQorVuq71tQo=; b=Knsi7bO+CijM+SPJwWUktPKj22nBjhyYQw3IC+hTSEZsAJ/3ci7zOcZoLG2MpRQBm9 agWhaIqQX8cnXEMyX4fAORiQRVk669QfZlQKfgCg8wySSaEBNzSMTKE+ffI8kKdwl7QL U5jQs/Gcfz6KAMFYk1tg39NnExhWUXOM6LaFw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=Z4XrJtrIbM0vK085jZ5Zl/rnXcJsFqnBQorVuq71tQo=; b=SVG0zLALgHPBITdhrjgjw50RBIo5VaMlsL0KN7vjpWCajk4H9xO7GOvIZJCcsGPz3p VZUquv+uSRkjvkPq6OL5i6cETfmlthDouQy995O4E4s2NX1KjXjUIG4C2Q/BTpYA6lhw n2zQt1kkebQM0EqZzb63n/qulFakxrgoImHib/LMvYVSz4xWzyZWVt/hSGNsFfNqBetA pQKFrDxeNx17EumLm8w51wpRZzkJgz/jcXVkR88IIYzXxbgGOEm7L8CLHxxoBfKzazve ChJtw4Z6Iudo9wmBctmuOOTKns299knjOetIfQ3hCHsaZg3bS9U56JvZIBMT6iD2XZ7E AgKw==
X-Gm-Message-State: ALoCoQlizRFhnBNPDxBjYz4qAhM1PpZ2oLeZ39ivV6kSojyErkoLvi9d/lkNiPl1G4JGE4w+vlLs/rCTNAT4ZdljIZ7UFVISjM7mpwDN4QY5VOV8Qdl8RxI=
X-Received: by 10.107.10.217 with SMTP id 86mr21642652iok.145.1445939091820; Tue, 27 Oct 2015 02:44:51 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
References: <64271754-EED2-4322-BB0E-51CB66365682@gmail.com> <B36B9E5E-0EB5-418A-A6A1-E103C8ECF500@ifi.uio.no> <CCC80AEF-66CD-4497-A374-2ED89DF4FA17@trammell.ch> <CAD62q9XQMSyuG_=HYjXKe12iE=-F3HasXqrmJs+RAQeBZbddCQ@mail.gmail.com> <562DF846.7090901@erg.abdn.ac.uk> <CAD62q9XjebXmRHUebJLrd35=PnrLPGCZFv4LBO5omYBh2J+72Q@mail.gmail.com> <564DD3D7-446B-4ABC-9A40-26E79DADD50E@ifi.uio.no> <562E3CC2.1010008@erg.abdn.ac.uk>
In-Reply-To: <562E3CC2.1010008@erg.abdn.ac.uk>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 15.0
thread-index: AQLnIZNWolJn6oOSV5yTes39Ry1l7wE3EKfUAj1+V1oBGpplrwKU7z00AeovEUkCuc7VVwL9pdiBm9zGfVA=
Date: Tue, 27 Oct 2015 10:44:50 +0100
Message-ID: <c2ab6d9ba042eb77d782b797d21d2a5a@mail.gmail.com>
To: gorry@erg.abdn.ac.uk, Michael Welzl <michawe@ifi.uio.no>, Aaron Falk <aaron.falk@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/owx0tsJVGofag6liGwpod-RHHAk>
Cc: Brian Trammell <ietf@trammell.ch>, Stein Gjessing <steing@ifi.uio.no>, taps@ietf.org
Subject: Re: [Taps] IETF planning
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 27 Oct 2015 09:44:55 -0000

HI,

Just a note. Not necessarily relevant for the overall argument however.

> >
> > So we’re i) describing services; ii) narrowing them down somehow; iii)
> > describing how to build this thing.
> > My concern is with iii) being something feasible and useful, not an
> > obscure sci-fi document.
> >
> > Say we include DCCP. It’ll add some services that aren’t in the other
> > protocols listed so far in this mail - e.g. drop notification (see
> > section 3.6.3 in draft-ietf-taps-transports). Say, in step ii), we
> > find no good arguments to remove drop notification. Then, in step
> > iii), we’ll have to say how a TAPS system can support drop
> > notification. So, to build a working TAPS system, one has to either:
> > - include DCCP in the code base
> > - extend other protocols to provide this functionality
> >

 SCTP also provides drop notification (SEND_FAILURE).

BR, Karen

v2.23.0 | Report a Bug | By Email