Re: [Dcrouting] DC Routing requirements draft

Nalini J Elkins <nalini.elkins@insidethestack.com> Wed, 01 November 2017 17:38 UTC

Return-Path: <nalini.elkins@insidethestack.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 66A5413F95F for <dcrouting@ietfa.amsl.com>; Wed, 1 Nov 2017 10:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.309
X-Spam-Level: **
X-Spam-Status: No, score=2.309 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.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 j9Ko7MD9sNWL for <dcrouting@ietfa.amsl.com>; Wed, 1 Nov 2017 10:38:35 -0700 (PDT)
Received: from sonic311-28.consmr.mail.gq1.yahoo.com (sonic311-28.consmr.mail.gq1.yahoo.com [98.137.65.209]) (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 3F4C813F9EE for <dcrouting@ietf.org>; Wed, 1 Nov 2017 10:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1509557914; bh=2QlW0nLHOfox2e3SawDH23pOlgy9Beb+k2vA6EX+aNY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=TVVYna4hEXRlvgkAWZZbaWxX+ORmgpM5jBNUeV/I8ZaexHGN4Pm+9+YPuDwrvqsLY5uBZp9pEh8VUP9MSuKNjrjW8gW+u69teqGvEIMtsthMyqa9/0BzAjenZzc99VNgSEithRiIaL06pDufoGp3c050JkjhKJVJWUBvm5tUuUMSkDe8vssXzi17WLAKOl0PgPE6ivlZnqyMkE9R8noxHNjHx8OYG5hg9F1qhDUXedVco9EPYWTQ/9z4uRMoY2aDBpqQ9ZOQacpDyMyQIxFIDjPetqL09VOvrjipXchDtjGoA4JR+eqH1I5z1GCJGULvNAurOntklwfcFgv/fyz6Qw==
X-YMail-OSG: 81AjdBoVM1lKCQ64Uw07DaFEo2OTMZ8a7TaHu5BX0e44u4o2mudFldpsclrYPfG XL4KQFZGTueUEf5BhIZabdk.cGh.fyo49Mblf3Qmz50H.AffHPS8jSbqBkrsQxcM1WI3KpF1lEhE zMNYLoiP_HUatmT53NT..JUBlX9Ze4S3aNO9bsDk6pqp3XMYed7sAG4R9cIfnnjSBPaK47xYQkJh AySwY_0viXpCzqI3zKTA5l3_r_.yiaDJ8wLeibaCni7Ww_u7d1gGpwVNlwJweEie4G99Xj7Lmm19 qiylEbIw9ePW.4j4gaZ8d9luoQgJR44bhIuaQTWhfZWE.kgB2LiKmzdR_.HOspk6pPPsHzLX7HO5 oHKy1_o40k6jjAtTt1SrjN0UI2jOmFFLBjYBQLrL0sFyl5YMnHb0l8hSlTXV4jEAPIus3WL8636B s6i8yb4SLxl8e84UJvYV.Mm1rZaK8p7xzvHZOxU020I7atrh91JvOKfEHAEW0zoU4WHCLp1RSxr6 ZTrSQy8pHyDAXl0yXkn544fz4cNwmSrcb7s643l3C9Vzr9VA_s6EkPQXToMjxy3RpY6x_S1GNeaG yxNDzRLcyBTuZyOGHNSQ6SpXygLaLiwhgXR5xR6Ldkc_jS_Ok5KE-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Wed, 1 Nov 2017 17:38:34 +0000
Date: Wed, 01 Nov 2017 17:38:24 +0000
From: Nalini J Elkins <nalini.elkins@insidethestack.com>
Reply-To: Nalini J Elkins <nalini.elkins@insidethestack.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, Randy Bush <randy@psg.com>
Cc: Jeff Tantsura <jefftant.ietf@gmail.com>, "dcrouting@ietf.org" <dcrouting@ietf.org>
Message-ID: <299602974.559004.1509557904949@mail.yahoo.com>
In-Reply-To: <852F82B5-D625-437E-87B2-A81D594BD335@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> <m2efpi36zl.wl-randy@psg.com> <852F82B5-D625-437E-87B2-A81D594BD335@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: WebService/1.1.10849 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/uCjwNDUp5-l98w05HS0YGkaeZYg>
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 17:38:36 -0000

> 



>>> But, just in case some people are thinking that enterprises do not
>>> have data centers
> 
>> i doubt anyone questions that enterprises sometimes have datacenters.
>> enterprises sometimes also have printers.  this does not mean

>> enterprises *are* printers.

> That may be the rub here. I doubt that enterprises that have data centers *are* data centers in either of your minds, any more than enterprises that *have* printers *are* printers. 
> However, in the data centers that enterprises have, they may have specific requirements that don't map well to the likes of Azure or Google, but which are in fact requirements of a 
> class of data centers.

Guys, I am getting another of my enterprise folks involved who had a good comment:

"We will have an underlay network [in our data center], which I think is going to still be OSPF and BGP, and an overlay network of VXLAN that allows ACI connectivity, which I think is what you're calling a big LAN (extended layer 2 subnets between pods and even between data centers).  I think this is reality for the modern data center.  We're also still keeping the brick and mortar components from your draft, overlaid on top of the "big lan"; firewalls, load balancers, web tier, app tier, middleware, etc....  So both models are true, one overlaid on top of the other.  In other words, when you route from the load balancer to the web server, you're traversing the ACI/VXLAN network to get there." 

I think this is a good discussion.   I am working to get this enterprise to also help co-author and explain their environment.   My brick and mortar draft ( 
https://datatracker.ietf.org/doc/draft-elkins-brickmortar-architecture) has a fair amount of stuff that is non-routing related because we are just getting started.  We will likely split it into more documents as this develops.  I am also adding in stuff about our diagnostic needs.  Have been talking to people about that as well. 

Sorry to get so behind on everything.  My best estimate for a new draft is tomorrow (Thursday) afternoon.

Thanks for your patience and comments.

Nalini