IETF Logo Mail Archive

Re: [Idr] New draft for data center gateways

Robert Raszuk <robert@raszuk.net> Mon, 23 May 2016 18:14 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11CB312DA5B; Mon, 23 May 2016 11:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level:
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.198, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 cp0J98LVTWpX; Mon, 23 May 2016 11:14:42 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 BE82612D0DE; Mon, 23 May 2016 11:14:41 -0700 (PDT)
Received: by mail-lb0-x233.google.com with SMTP id ww9so58073851lbc.2; Mon, 23 May 2016 11:14:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=fOjztvU2+CFyeUxiW+I6PSvV3Swo6RwMC0qvvMwWS3Y=; b=XKCd4oXiiulLzIm1CYLLvXujAIlhp7YnrrUGvdmQT+wLoHNGi1oUNK5fI/242/02hq kuBT58Seq83auB0r9xusm50DfoWmlnuU2T6+d+wbpT6Rc2AGCnCo2wjZsBYibRGZ7mp+ r7HUBnErjro1x36LsBHi3NVJVniNbRc0wHEnX07Ktmqu9bCLzckrz7Kl+I9c1vu/gqm4 rKAvcYtpaHaEc5/e/8RJUWhGny18iqGoGmMsWGEx4tgza1SnVrgmG+fWrnUlAcHmmAr+ 1JHXQfWg++n0ZJdHl4uRsZoZ2fmr9wh75+jNNa4p8koMkTiUH+s/qZSlfwIU2qDiyfVg ZlXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=fOjztvU2+CFyeUxiW+I6PSvV3Swo6RwMC0qvvMwWS3Y=; b=iY0Qmwzmy3HfDvR54lsPkqnISQusFxa+O4DrGsXJLNmkuVsqnycfu6JCNhx+J9mlMn 0YyBH7Qqy0O02b022QoiEm875AagJxeGGEeLi/h5mgNZpU2c6/ANh0MHAq1crpCXxLR/ AtWnYsWpPUSevl8D6cdtoTvMk/DPhgDa/otAm/By3S8UqjnXmgAWESlfKKhorCjC9BKJ Li8Jwm1TaeAzb4wdDqNnJhDk1VUXD571pdOtsemqMWJk+puS91f5679FkQcJjezOEbyx awXALJLkPJXhvU+lh+lCy3tCoKyXW2nR0iYNxS+l738RJXIyEI60igJNXJVKDhKa4Rvf 5Xjw==
X-Gm-Message-State: AOPr4FU7Nrm5oasCvintQSEJm18wodvx21l7yRX/8Gx5yrFZD533q9CD2uMrnIiX/cdr/hwNsnOooCzcBA4agQ==
MIME-Version: 1.0
X-Received: by 10.112.171.229 with SMTP id ax5mr6361704lbc.115.1464027279811; Mon, 23 May 2016 11:14:39 -0700 (PDT)
Sender: rraszuk@gmail.com
Received: by 10.25.126.210 with HTTP; Mon, 23 May 2016 11:14:39 -0700 (PDT)
In-Reply-To: <01ea01d1b51a$7cf31e60$76d95b20$@olddog.co.uk>
References: <01ea01d1b51a$7cf31e60$76d95b20$@olddog.co.uk>
Date: Mon, 23 May 2016 20:14:39 +0200
X-Google-Sender-Auth: Z9SdVtFWHNYgaik99yYZjvUtN34
Message-ID: <CA+b+ERmKjq9h5LP5k3+dygkRjbwzsXrogyzvopPZ61DTTuaitA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary="001a11c36ed6f46cf505338669e7"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/H5CM86DMoEJZLL8yhwWgGwbVIYA>
Cc: idr wg <idr@ietf.org>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [Idr] New draft for data center gateways
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 18:14:45 -0000

Hi Adrian,

Many thx for sharing the document. Just starting to read it one assertion
repeated at least twice got my attention:

"Segment routing (SR) [I-D.ietf-spring-segment-routing] is a popular
protocol mechanism for operating within a DC"

By "popular protocol mechanism" when building non blocking L3 CLOS IP
fabric are you referring to the below proposal or something else ?

https://tools.ietf.org/html/draft-filsfils-spring-large-scale-interconnect-02

Also by "popular" do you mean something which is perhaps deployed in
production to any level or author's definition of "popular" refers to
something real deployment are yet to see ?

Honestly having been involved in building large scale data centers for the
last few years I have not see SR being anywhere close to be used there.
Especially MPLS flavor of it :)

If anything within DCs draft-lapukhov-bgp-sdn-00 is easy to use and
provides more then sufficient flexibility within properly constructed
intra-dc fabric in terms of traffic engineering.

Many thx,
Robert.


On Mon, May 23, 2016 at 7:42 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
>
> Just posted
> https://datatracker.ietf.org/doc/draft-drake-bess-datacenter-gateway/
>
> We think this covers an important hole. The document defines a mechanism
> using
> the BGP Tunnel Encapsulation attribute to allow each gateway router to
> advertise
> the routes to the prefixes in the data center site to which it provides
> access,
> and also to advertise on behalf of each other gateway to the same data
> center
> site.
>
> We posted this as  BESS draft, so discussion there, please until such time
> that
> the various chairs tell us to move the discussion somewhere else.
>
> Thanks,
> Adrian
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

v2.23.0 | Report a Bug | By Email