Re: [Taps] Comments on draft-gjessing-taps-minset-00.txt
Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com> Thu, 16 July 2015 09:22 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 AEDA21A8724 for <taps@ietfa.amsl.com>; Thu, 16 Jul 2015 02:22:55 -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 ZzpU12VaCDAg for <taps@ietfa.amsl.com>; Thu, 16 Jul 2015 02:22:54 -0700 (PDT)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 149E51A871E for <taps@ietf.org>; Thu, 16 Jul 2015 02:22:54 -0700 (PDT)
Received: by iggp10 with SMTP id p10so8940181igg.0 for <taps@ietf.org>; Thu, 16 Jul 2015 02:22:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tieto.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to:cc :content-type; bh=tbQ85zcWhej3fLlK7p/JpUK4ieF++VJIVdy5k7G/cr0=; b=NGdaWRyErhvzsDFDw4kvw4cQqgUo2Tu3GMiKyShKekSxcpMyHYctJXvQDWRl/2WVEj 73iYLLpdsTWqJ8Wk7J4wGBLicS56BATQm+rYQrigFPgeykEHDMS5PVqnk3gXWYLS/kNr wo21sETGdZ0sfg/4L5aMlOlGQEG8wtr+rjIgQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:cc:content-type; bh=tbQ85zcWhej3fLlK7p/JpUK4ieF++VJIVdy5k7G/cr0=; b=VZdSi6eVwcopR/0J7Ig0erSleMxT6tlT+DeUJXF7zEgwCyfTEulk6l1eF9CvujRDt5 dx1wz557R9Ojs4iJ3nohO11s7uQzupoNhWBARzZeL9HJcjxwsejkbMlWtw/+d2QVrEj3 L+QFl8fOG11S+y1Li1zG//iBEjnA3MyPqDJOXr83E3hDFpDpf9fv22M/6G5xTS0O/yaC X6wSHxXHLaUbF2Zs/TbyjYcleQIWNsdSWo6KevOKeahpzRpeeTiFVnKE8Z2Ula3Kjojz aT/fOEvZlUtFg0qCrQ7iUueIqOYp7ZcVENcSfFhK4k/Ch2rnJAuiV30SXEhvv8ZwVKRl cE1g==
X-Gm-Message-State: ALoCoQkqHQoKa4bHhrY60TJocy4GuZBUoNSr4CpdqOQmtHen6mkAsuAmyLoAZKVTXD1cKcAGOnGD4PrLaYO4GBQLglayTNYAcCrIzGbfXbqWWUUhcEnRfhA=
X-Received: by 10.107.167.2 with SMTP id q2mr11491524ioe.109.1437038573413; Thu, 16 Jul 2015 02:22:53 -0700 (PDT)
From: Karen Elisabeth Egede Nielsen <karen.nielsen@tieto.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdC/qP3G6CRs7LiBSOiwXCHGIUBxIQ==
Date: Thu, 16 Jul 2015 11:22:52 +0200
Message-ID: <5b2e19f286a3eaf18d2ccf7da39abbbf@mail.gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>, taps WG <taps@ietf.org>
Content-Type: text/plain; charset="UTF-8"
X-DomainID: tieto.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/taps/36_K2p4_RZ8PiIax-9SnNshtF3U>
Cc: Stein Gjessing <steing@ifi.uio.no>
Subject: Re: [Taps] Comments on draft-gjessing-taps-minset-00.txt
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: Thu, 16 Jul 2015 09:22:55 -0000
HI, A few initial comments the definition of the transport service features as they appear from section 3 (and TAPS1): Unidirectional/bidirectional: I am not sure what this means exactly: Does it refer to that data transfer is negotiated for both directions perhaps ? But then it only applies to connection oriented transport. Does it refer to that control info is going back ? Does it refer to that messages (which ever form) are going back on the reverse network path ? Then it does not necessarily apply to SCTP MH. o non-reliable delivery: add SCTP o reliable delivery: add SCTP Suggest to rephrase o reliable and partially reliable delivery --> o partially reliable delivery: SCTP o drop notification : add SCTP o ordered delivery: add SCTP o unordered delivery: add SCTP Ideally, I think, then one would use a common term for Nagle(-like) bundling for TCP and SCTP. BR, Karen >-----Original Message----- >From: Taps [mailto:taps-bounces@ietf.org] On Behalf Of Michael Welzl >Sent: Friday, June 26, 2015 9:22 AM >To: taps WG >Cc: Stein Gjessing >Subject: [Taps] Fwd: New Version Notification for draft-gjessing-taps-minset- >00.txt > >Dear all, > >This is a very first stab at a draft addressing the charter's second item - the >minimal set of transport services that end systems should support. > >It is based on version 4 of draft-ietf-taps-transports, so the list of features / >components is not up to date - but that's not really the main point of the >document for now anyway: >it's about showing how the number of exposed services *could* be reduced. >Our hope is that, by sketching the possible destination of our journey, this >helps the current discussion of the first document. > >Cheers, >Michael > > > >> Begin forwarded message: >> >> From: <internet-drafts@ietf.org> >> Subject: New Version Notification for >> draft-gjessing-taps-minset-00.txt >> Date: 22 Jun 2015 14:37:43 CEST >> To: Michael Welzl <michawe@ifi.uio.no>, Stein Gjessing >> <steing@ifi.uio.no>, Stein Gjessing <steing@ifi.uio.no>, Michael Welzl >> <michawe@ifi.uio.no> >> Resent-From: <michawe@ifi.uio.no> >> >> >> A new version of I-D, draft-gjessing-taps-minset-00.txt has been >> successfully submitted by Michael Welzl and posted to the IETF >> repository. >> >> Name: draft-gjessing-taps-minset >> Revision: 00 >> Title: A Minimal Set of Transport Services for TAPS Systems >> Document date: 2015-06-22 >> Group: Individual Submission >> Pages: 10 >> URL: https://www.ietf.org/internet-drafts/draft-gjessing-taps-minset- >00.txt >> Status: https://datatracker.ietf.org/doc/draft-gjessing-taps-minset/ >> Htmlized: https://tools.ietf.org/html/draft-gjessing-taps-minset-00 >> >> >> Abstract: >> This draft will eventually recommend a minimal set of IETF Transport >> Services offered by end systems supporting TAPS, and give guidance on >> choosing among the available mechanisms and protocols. As a starting >> point for discussion, it currently only gives an overview of some >> ways to categorize the set of transport services in the first TAPS >> document (version 4: draft-ietf-taps-transports-04), assuming that >> the eventual minimal set of transport services will be based on a >> similar form of categorization. >> >> >> >> >> Please note that it may take a couple of minutes from the time of >> submission until the htmlized version and diff are available at tools.ietf.org. >> >> The IETF Secretariat >> > >_______________________________________________ >Taps mailing list >Taps@ietf.org >https://www.ietf.org/mailman/listinfo/taps
- Re: [Taps] Comments on draft-gjessing-taps-minset… Karen Elisabeth Egede Nielsen
- Re: [Taps] Comments on draft-gjessing-taps-minset… Michael Welzl
- Re: [Taps] Comments on draft-gjessing-taps-minset… Karen Elisabeth Egede Nielsen
- Re: [Taps] Comments on draft-gjessing-taps-minset… Brian Trammell
- Re: [Taps] Comments on draft-gjessing-taps-minset… Michael Welzl