IETF Logo Mail Archive

Re: [Dcrouting] DC Routing requirements draft

Randy Bush <randy@psg.com> Wed, 01 November 2017 04:36 UTC

Return-Path: <randy@psg.com>
X-Original-To: dcrouting@ietfa.amsl.com
Delivered-To: dcrouting@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7208213FAC5 for <dcrouting@ietfa.amsl.com>; Tue, 31 Oct 2017 21:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 XzcC0YUIIYJ8 for <dcrouting@ietfa.amsl.com>; Tue, 31 Oct 2017 21:36:48 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 7157D13FAC3 for <dcrouting@ietf.org>; Tue, 31 Oct 2017 21:36:48 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1e9kli-0001Ww-Dd; Wed, 01 Nov 2017 04:36:46 +0000
Date: Wed, 01 Nov 2017 04:36:45 +0000
Message-ID: <m2mv46399e.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: dcrouting@ietf.org
In-Reply-To: <4851E755-A28F-43A0-AF4E-77D0F9FC9E3E@gmail.com>
References: <56F12355-DBF1-47C8-B7F7-C057DC40F1B0@gmail.com> <m2vaiv2jd2.wl-randy@psg.com> <2BD778A9-868D-444B-BCFA-EE060923C64E@gmail.com> <1899221575.91902.1509494163197@mail.yahoo.com> <4851E755-A28F-43A0-AF4E-77D0F9FC9E3E@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/Tez9Sdn98y6bjrz56MJVzRvFr3A>
Subject: Re: [Dcrouting] DC Routing requirements draft
X-BeenThere: dcrouting@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Routing in the Data Center: discussions about problems, requirements and potential solutions." <dcrouting.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dcrouting>, <mailto:dcrouting-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dcrouting/>
List-Post: <mailto:dcrouting@ietf.org>
List-Help: <mailto:dcrouting-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dcrouting>, <mailto:dcrouting-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Nov 2017 04:36:49 -0000

> Randy, I don't understand your questioning the concept that
> enterprises might run their own data centers instead of or in addition
> to the well known public data center services.

this may be because i made, or at least intended, no such assertion.

yes, enterprises sometimes have datacenters on the side.  and data
centers almost always have enterprises on the side, if only to churn out
the billing, but usually more.

> The two problems are different.

and here we agree.  though, i suspect some folk think they have a
univerdsal solvent.  as it has yet to be revealed, it is premature
to judge.

randy

v2.23.0 | Report a Bug | By Email