IETF Logo Mail Archive

Re: [Dcrouting] DC Routing requirements draft

Fred Baker <fredbaker.ietf@gmail.com> Wed, 01 November 2017 02:19 UTC

Return-Path: <fredbaker.ietf@gmail.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 CE4B413F849 for <dcrouting@ietfa.amsl.com>; Tue, 31 Oct 2017 19:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VrLi4HOqXKv8 for <dcrouting@ietfa.amsl.com>; Tue, 31 Oct 2017 19:19:21 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 7023A13F570 for <dcrouting@ietf.org>; Tue, 31 Oct 2017 19:19:21 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id r196so2233808wmf.2 for <dcrouting@ietf.org>; Tue, 31 Oct 2017 19:19:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=2mOtXhGvZUJWX4Eu33IvcLdOK12ddyvlU565flikGNM=; b=XYp8DW25XGMTbGMdLf7juv5oxBmPacHOwFcgvQLNEvh5LbqfS0IF9z3Q222rezOUU8 h9v2kaOBgy60G6PmPdkbEljTnyriC2xK0aD6BCYmGVfQZWEp9BGQ9AjZfEw/2SAbRNJS pn7ljMnhda613SpJPEwRMWFsrhggkr1Q8aisMrxVU6DtK9Qt9q2fxwcPUXuEtULzg/ex fvBQJ/UVC70pkfZz69KA9+CFyUu6IGDhcRKUOHjZ5leia1fKH8sJDzSXi07XekjrjTDo Kzl75TYiMn/DtAlfHfFw8H/FTChA/LI1ZgWSn05sSowQ/8yZVotUCUu42ugvgk49/6GY WgAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=2mOtXhGvZUJWX4Eu33IvcLdOK12ddyvlU565flikGNM=; b=TcbZbVe8yLjongdSAH0OMuB+oogGDKJlx5HnBwbBAoDaUku8xP4iHeMt6IHbBE3J/K qqljWr/uj0sr6SCpFFc5lL47eADGFCuZis8d11E7dFfMVbQjINlKBsfHSAmnWtvZRLm/ 1Mv9L6Q3PLRfY8ZebiCUz0gpchbOR0Sjx28gh6FKFTz9dhATrLMNbhRzdf3dNmCyNYil sNsYwhmbdgdLhLhzpAwT9GswKZtL9GKxjr44Z92leQ2NpAk1BKTP+XExucwxGA6vGDeB TqjDO+fiqLonWnQzux8fi7hukMnRXVw0e04eb30KwMkfJwz7u/wzfIdVmjm6JQyg46Sl lglw==
X-Gm-Message-State: AMCzsaUW22Os01MlCOHqe4c2EU/GmSIRbR6xOY3EsC2ZcxImScr/V0Ch rTGlhjBoWnF6AX2GQmp0Jnc=
X-Google-Smtp-Source: ABhQp+SYeMijAlAit+2mNC/uOeJEsA7yU+nI3XOq9UWLyveSrOdeShBYpIDcm27Id98whvgd9z64cw==
X-Received: by 10.28.32.136 with SMTP id g130mr3577158wmg.102.1509502759972; Tue, 31 Oct 2017 19:19:19 -0700 (PDT)
Received: from 207.66.20.149.in-addr.arpa (207.66.20.149.in-addr.arpa. [149.20.66.207]) by smtp.gmail.com with ESMTPSA id 64sm1677698wrk.46.2017.10.31.19.19.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Oct 2017 19:19:19 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Message-Id: <4851E755-A28F-43A0-AF4E-77D0F9FC9E3E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_260131C9-E492-4DFD-8528-9C58FD99B686"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Wed, 01 Nov 2017 06:19:10 +0400
In-Reply-To: <1899221575.91902.1509494163197@mail.yahoo.com>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, "dcrouting@ietf.org" <dcrouting@ietf.org>
To: Nalini Elkins <nalini.elkins@insidethestack.com>, Randy Bush <randy@psg.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>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/ApVyL6qMkekMu_kb242GIFk4vmE>
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 02:19:23 -0000


> On Nov 1, 2017, at 3:56 AM, Nalini J Elkins <nalini.elkins@insidethestack.com> wrote:
> 
> The draft in its current state does not have enough about routing.  But, just in case some people are thinking that enterprises do not have data centers, I thought I might post some definitions of "data center".  I hope I have misunderstood the comment.

This feels like a pissing contest.

Yes, enterprises run data centers, and data center operations like Azure, Google, and Facebook run data centers. Where there are data centers, there are networking issues related to data centers. 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.

That said, enterprises *also* run campus networks, which might be as small as the mom and pop grocery on the corner or as large as a Cisco or an IBM, with campuses and offices everywhere. I know of some enterprises whose campus networks rival in Internet itself for breadth.

The two problems are different. Nalini, I think Randy thinks you're solving the second problem and calling it the first. I think you are trying to describe both problems. But he is right in saying that they are not the same problem, and in your document you need to make the differing sets of requirements clear.

v2.23.0 | Report a Bug | By Email