Re: [Spud] SPUD for Datacenters

Caitlin Bestler <caitlin.bestler@nexenta.com> Mon, 30 March 2015 20:06 UTC

Return-Path: <caitlin.bestler@nexenta.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A57391AD35F for <spud@ietfa.amsl.com>; Mon, 30 Mar 2015 13:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 Co29cyMqncrw for <spud@ietfa.amsl.com>; Mon, 30 Mar 2015 13:06:16 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (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 20DAF1AD365 for <spud@ietf.org>; Mon, 30 Mar 2015 13:06:16 -0700 (PDT)
Received: by pacgg7 with SMTP id gg7so47652575pac.0 for <spud@ietf.org>; Mon, 30 Mar 2015 13:06:15 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EcR4Ik0oYOE2f5pC095b3t1La9EANbo9yF7NTFqWOLw=; b=h1TRTk7849oJn5o9UUcFf2d/+mcTGmsUXEQ4UwcKQR+TU1kCK5C8khYeBXUWCM7msT 6z5wlGJ+JwzANfsc7esi6d9ILDi9uZS4YoneAoOjCteAT0fKi5sIOenwxt7qi9UTWeYH GyovmlS2kzoGlx6bmwK9hfqaRknI+PqPtuDiIoFCx8Tb/i2B6XjGkWlPzhF1re2x5Z3G kU1i4UQTaNsm4bS3OE0iE2fh9TCDKlwNCTKZF9XBzznsIN7QOmm1EUdDPHSX5d+g76SH bSlKeKQ0iKEQSQaAaM7yEkerumq88kTmwXymrM1H+bqJ+w1rheS4OoFSkwdAJRzFKGFq L4KQ==
X-Gm-Message-State: ALoCoQksX7CAfjthLI7g2m2NDhDc8Q5jCpOJxKOwMxI2aMRE5awRH4yH+ZZjDSBZJzTXI6ic9Zmd
X-Received: by 10.66.235.169 with SMTP id un9mr60044223pac.45.1427745975800; Mon, 30 Mar 2015 13:06:15 -0700 (PDT)
Received: from Macintosh-2.local (67-207-110-172.static.wiline.com. [67.207.110.172]) by mx.google.com with ESMTPSA id zd14sm10913039pab.20.2015.03.30.13.06.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Mar 2015 13:06:14 -0700 (PDT)
Message-ID: <5519ACB5.6060900@nexenta.com>
Date: Mon, 30 Mar 2015 13:06:13 -0700
From: Caitlin Bestler <caitlin.bestler@nexenta.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>
References: <55142E8A.1000509@nexenta.com> <39481497-0304-4B99-863B-BC78364FB59A@tik.ee.ethz.ch>
In-Reply-To: <39481497-0304-4B99-863B-BC78364FB59A@tik.ee.ethz.ch>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/MBxbyn_QNm72XVjWrn8TmtLFEu4>
Cc: spud@ietf.org
Subject: Re: [Spud] SPUD for Datacenters
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2015 20:06:28 -0000


On 3/30/15 11:24 AM, Mirja Kühlewind wrote:
> Hi Caitlin,
>
> just a quick response. To my experience designing thing for the Internet is usually harder that for data centers. However, what works in the Internet should usually also work in data centers. (If that’s the most efficient way to do things in a data center, is a different question). However, I think it is most important that we can come up with something that can be use in the Internet. And as this is today hard problem, I’d prefer to focus on this part.
>
> Mirja
>
>
I would agree that getting things to work for the Internet is harder.

What I am suggesting is that we at least think about the datacenter 
impact for each specific method we come up with.
Careful phrasing of requirements can result in no additional work for 
the Internet deployment but enable an efficient
datacenter implementation as well. But if we don't do that check before 
we freeze language we will end up forcing
some inefficiency for datacenter implementations.

Datacenter specific optimizations, such as enhanced interactions for 
short round-trip-times, should be deferred.
Make it work everywhere first.