Re: [Dclc] Agenda topics

Toby Moncaster <toby.moncaster@cl.cam.ac.uk> Mon, 27 October 2014 15:44 UTC

Return-Path: <tm444@hermes.cam.ac.uk>
X-Original-To: dclc@ietfa.amsl.com
Delivered-To: dclc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F861A87DB for <dclc@ietfa.amsl.com>; Mon, 27 Oct 2014 08:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 DKuKX96R8_X2 for <dclc@ietfa.amsl.com>; Mon, 27 Oct 2014 08:43:58 -0700 (PDT)
Received: from ppsw-40.csi.cam.ac.uk (ppsw-40.csi.cam.ac.uk [131.111.8.140]) (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 CDDD51AC40D for <dclc@irtf.org>; Mon, 27 Oct 2014 08:43:54 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from ravage.mac.cl.cam.ac.uk ([128.232.56.44]:51719) by ppsw-40.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpsa (PLAIN:tm444) (TLSv1:AES128-SHA:128) id 1XimST-0000lQ-jI (Exim 4.82_3-c0e5623) (return-path <tm444@hermes.cam.ac.uk>); Mon, 27 Oct 2014 15:43:49 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_04A4E9D5-C67B-4B1D-9672-D15EFF503FB5"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Toby Moncaster <toby.moncaster@cl.cam.ac.uk>
In-Reply-To: <CD5957AA-B604-4BBC-8F5E-404585FA2C5E@cisco.com>
Date: Mon, 27 Oct 2014 15:43:51 +0000
Message-Id: <CA449839-C0D4-4D17-B2CD-443FDF620234@cl.cam.ac.uk>
References: <D8EC17A9-A105-484F-B36F-7806A1A80D48@cisco.com> <C5C3BB522B1DDF478AA09545169155B46D842B70@nkgeml507-mbx.china.huawei.com> <1903A114-C834-472D-9AA3-52983FE8972D@netapp.com> <CD5957AA-B604-4BBC-8F5E-404585FA2C5E@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Sender: "T. Moncaster" <tm444@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dclc/Hb3TxMSWhMxIL_Btqvyq2yKsBJk
Cc: Weixinpeng <weixinpeng@huawei.com>, "Eggert, Lars" <lars@netapp.com>, dclc <dclc@irtf.org>
Subject: Re: [Dclc] Agenda topics
X-BeenThere: dclc@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of Data Center Latency Control <dclc.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dclc>, <mailto:dclc-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dclc/>
List-Post: <mailto:dclc@irtf.org>
List-Help: <mailto:dclc-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dclc>, <mailto:dclc-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 2014 15:44:00 -0000

I’m also contemplating whether it needs an IPR disclosure on this:

http://www.google.com/patents/EP2258079B1?cl=en

Which I was working on at BT a few years ago.

Toby

On 27 Oct 2014, at 15:39, Fred Baker (fred) <fred@cisco.com> wrote:

> 
> On Oct 27, 2014, at 2:09 AM, Eggert, Lars <lars@netapp.com> wrote:
> 
>> Hi Xinpeng,
>> 
>> On 2014-10-27, at 09:21, Weixinpeng <weixinpeng@huawei.com> wrote:
>>> It will be appreciated if there is a timeslot for me to show our work on tunnel-based congestion control. 
>>> The following is a link to the document.
>>> http://datatracker.ietf.org/doc/draft-wei-tsvwg-tunnel-congestion-feedback/ 
>> 
>> could you outline how this draft is related to latency control in datacenters? I read an earlier version and it seemed to be all about wide area networks?
>> 
>> Thanks,
>> Lars
> 
> I’m scratching my head as well. Lingli is a co-author, so maybe she can comment here.
> 
> The draft does mention NFV, which can be implemented across multiple data centers connected by a WAN, but if primarily implemented within a data center, and specifically mentions data centers. It also mentioned latency in passing, in the third paragraph of the section on 3GPP.
> 
> Where I’m scratching my head is figuring out what it’s actually trying to say. It explains NFV and that tunnels might be implemented in a vSwitch, which is true, and often the case in architectures such as OpenStack. It doesn’t seem to make obvious points about that such as are made in RFC 2983: when the tunnel is marked as having experienced congestion, that information needs to be reflected in the interior header at the tunnel endpoint. It talks quite a bit about IPFIX. I’m not sure I walked away with “so do this”.
> _______________________________________________
> Dclc mailing list
> Dclc@irtf.org
> https://www.irtf.org/mailman/listinfo/dclc