Re: [iccrg] ICCRG meeting minutes

hiren panchasara <hiren@strugglingcoder.info> Wed, 13 April 2016 06:43 UTC

Return-Path: <hiren@strugglingcoder.info>
X-Original-To: iccrg@ietfa.amsl.com
Delivered-To: iccrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9982812DD47 for <iccrg@ietfa.amsl.com>; Tue, 12 Apr 2016 23:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.896
X-Spam-Level:
X-Spam-Status: No, score=-2.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.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 tZDVAMNgAZkW for <iccrg@ietfa.amsl.com>; Tue, 12 Apr 2016 23:43:35 -0700 (PDT)
Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by ietfa.amsl.com (Postfix) with ESMTP id E459312DD46 for <iccrg@irtf.org>; Tue, 12 Apr 2016 23:43:35 -0700 (PDT)
Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 6033017C79; Tue, 12 Apr 2016 23:43:35 -0700 (PDT)
Date: Tue, 12 Apr 2016 23:43:35 -0700
From: hiren panchasara <hiren@strugglingcoder.info>
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Message-ID: <20160413064335.GR31516@strugglingcoder.info>
References: <CAGD1bZaijEKEqXLaLfnCZ28vpnw7ogPO9Nsc+O=02q1w0hDY=A@mail.gmail.com> <20160412221530.GP31516@strugglingcoder.info> <3F408D90-6241-4564-9A55-126BB5022B04@lurchi.franken.de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="2DJuma0xDHN2clgl"
Content-Disposition: inline
In-Reply-To: <3F408D90-6241-4564-9A55-126BB5022B04@lurchi.franken.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/iccrg/dVnEgDR050rDNsUUPnfvspTvfqU>
Cc: Jana Iyengar <jri@google.com>, iccrg@irtf.org, Michael Welzl <michawe@ifi.uio.no>
Subject: Re: [iccrg] ICCRG meeting minutes
X-BeenThere: iccrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussions of Internet Congestion Control Research Group \(ICCRG\)" <iccrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/iccrg>, <mailto:iccrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iccrg/>
List-Post: <mailto:iccrg@irtf.org>
List-Help: <mailto:iccrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/iccrg>, <mailto:iccrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2016 06:43:37 -0000

On 04/13/16 at 06:59P, Michael Tuexen wrote:
> 
> > On 13 Apr 2016, at 00:15, hiren panchasara <hiren@strugglingcoder.info> wrote:
> > 
> > On 04/12/16 at 05:14P, Jana Iyengar wrote:
> >> Hi all,
> >> 
> >> The minutes of the ICCRG meeting at IETF95 are now posted
> >> <https://www.ietf.org/proceedings/95/minutes/minutes-95-iccrg>. Please send
> >> corrections to the list or to the chairs.
> >> 
> >> Thanks much, Gorry, for taking these down!
> > 
> > Thanks for the notes. 
> > 
> > It'd be awesome if I can get a clarification in following though:
> > 
> > From - Michael Welzl: TCP in UDP (draft-welzl-irtf-iccrg-tcp-in-udp-00)
> > Michael Tuexen: How do you ensure the right sequence of UDP packets and
> > TCP-in-UDP packets on the server side, when using multicore systems?
> > Michael: In our cases this worked.
> > 
> > Was there more discussed and is missed in the notes? Can Michael Welzl or
> > someone else elaborate?
> My point was that some NICs distribute incoming packets to multiple
> threads and that the TCP/IP and TCP/UDP/IP might end up in different
> threads. So it is hard to ensure sequence preservation in that case.
> If you only use a single thread, there might be no issue.
> 
> I think a couple of other agreed that this is an issue and we stopped
> discussing it.

I do understand the problem. I was wondering if there was any discussion
towards possible solutions specific to this draft/work.

Thanks for clarifying.

Cheers,
Hiren