Re: [Dcrouting] [Rift] kicking off the charter discussion

Robert Raszuk <robert@raszuk.net> Thu, 04 January 2018 23:13 UTC

Return-Path: <rraszuk@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 DBE18126B71; Thu, 4 Jan 2018 15:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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 1QXHrMx-l9KQ; Thu, 4 Jan 2018 15:13:35 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 30F3312420B; Thu, 4 Jan 2018 15:13:35 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id b141so6301299wme.1; Thu, 04 Jan 2018 15:13:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=TIMiJJbEceqbsi0eZInm8W7y2HyIhMaKM98cY+BhLcU=; b=kRf5dq60K+tBNbTQawUatyzXWSXgqMrdWoycmTQTL3U3J61B7rRuDCM3/21XPJgCri e/pjMKvyLfnLV9niM6rsj2+4BEiRFX36hpf+8dezh/SX5A1WSud8J1qOMgLGsMiGgej3 2LQdj2TTJCb62hX8D5fj8lRmRnf8RETmKqk2mpzTsv6bj8tDk+P0UR1IAA66sZyVoX8q POOQ57NQpPbFIc9fXNOFCyDWla712N0ADYuv2rOAu9KUGH+QDWrmCnSbpf1D4mKHbeHT jUzp3HxUQ2eTWAP+3NqoBSL37eK32OWNR3YiTncfje2NOnZHZukdZmakAj7QweFzLgs9 LfSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=TIMiJJbEceqbsi0eZInm8W7y2HyIhMaKM98cY+BhLcU=; b=l2MUOvEvUV/N6V1W9z4u/qG8IvjQ/jDtSsR4ArcHV5O+o3BKoeCPC66XNmmigPlOly TAO0tjVPWp7phbbmIsZFFu3dKqvipc3a92Fm1HwhaQx/tfxxRLDeF6UuoQQX19gu/bAN jHwe1vCwB/zMN/3KgB+R5IswNLQkV5byNEARygFXx3TfUudm0snj0ZDocBeoDbCpFl5m blOMKMSnk2Bkm4/e3mhOQIyB2oc7yTvB6tlv06RmBjUThtrOvdzJWHiM5UOt62ZD6sQi sAH2tXCX53GSfMBjkVlmAIJiEo33S+vR1+h3muQJo9rvW7bwVSOS6p4taWgBFnZMUuLG TVYQ==
X-Gm-Message-State: AKGB3mKwipnRxQ4rP1d5hn7w+EEy2gG0FyutAjhNlPxAZKdAxpYdasw6 rrzFKg19uvYwsXDtrB05v8vp1R1QqLG1e6hyDUQ=
X-Google-Smtp-Source: ACJfBovw7K5lG+jBVjkzMaMIvWgYmFlDsceEPM9YEp8uCLvUFPCqtchb4xsdsQCfk8X8zoaTXwVUVsd7DhWqsF2nv7k=
X-Received: by 10.28.232.148 with SMTP id f20mr731933wmi.147.1515107613520; Thu, 04 Jan 2018 15:13:33 -0800 (PST)
MIME-Version: 1.0
Sender: rraszuk@gmail.com
Received: by 10.28.54.217 with HTTP; Thu, 4 Jan 2018 15:13:32 -0800 (PST)
In-Reply-To: <CAMMESszh69YiyMoQvsRrzv+LFWzkG8ij9NRrGeF-opF7RO=eww@mail.gmail.com>
References: <CAG4d1rd6=TXVtkHBQHSGkL3KKXF6CPs9ktsr725MWjDSsC9QiQ@mail.gmail.com> <CA+b+ERnLiD8DMmUCJUz72Py3dk2LP=u7Zb4BxfOzs2=7t=h3mA@mail.gmail.com> <CAMMESszh69YiyMoQvsRrzv+LFWzkG8ij9NRrGeF-opF7RO=eww@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 05 Jan 2018 00:13:32 +0100
X-Google-Sender-Auth: eNsIvzejQXL_7-qh-nHpEo9bl-0
Message-ID: <CA+b+ERkawAtmV51ymKSE8EuOZK9xgeu94xLDhxx1qAnvRieORg@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: rift@ietf.org, lsvr@ietf.org, "dcrouting@ietf.org" <dcrouting@ietf.org>
Content-Type: multipart/alternative; boundary="001a1147c49e19b7380561fb7bfa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/fCTM5yLUx4gWsQLsqteGiZtDCQc>
Subject: Re: [Dcrouting] [Rift] kicking off the charter discussion
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: Thu, 04 Jan 2018 23:13:38 -0000

Hi Alvaro,

Happy New Year !!!

> That was pretty much the question asked during the dcrouting BOF in
Singapore.

Well .. in Singapore and during most of list discussions dynamic flooding
proposal was not on the table. Now it is.

To me this is game changer and any conclusions reached previously IMHO
should now be revisited.

As far as outcome of the BOF - I am not sure how the conclusion was derived
that we need new protocols - especially only those presented. In real
practical cases a lot of DC clusters are build with at most few hundreds of
L3 nodes which in all flavors of current link state implementations will
work just fine as is.

For MSDCs use of either eBGP or Open/R is deployed.

Now dynamic flooding can extend link state to scale much larger.

Personally IMHO this case is solved. Maybe time to move on to other areas ?
:)

Best,
R.



On Fri, Jan 5, 2018 at 12:02 AM, Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> On January 5, 2018 at 5:48:23 AM, Robert Raszuk (robert@raszuk.net) wrote:
>
> Robert:
>
> Hi!  Happy New Year!
>
> Do we really need yet one more new routing protocol vs relatively minor
> extension of existing link state protocols ?
>
>
> That was pretty much the question asked during the dcrouting BOF in
> Singapore.  Starting from the assumption that one size doesn’t fit all, the
> room showed interest in working on solutions beyond the current work in
> isis/ospf (which was also quickly reviewed there).
>
> To be clear, the intent of chartering rift doesn’t mean that work in other
> WGs (including new proposals) should stop.  Quite the contrary, if there is
> sustained interest in this effort, then we will go on with it — if there
> isn’t (for whatever reason), then it will be clear as well.  Note that I
> asked the proponents to constrain the proposed charter to work items that
> should be able to be delivered within a short timeframe (around a year) —
> so that we can reassess the interest, and re-charter if appropriate.
>
> The above obviously applies to the lsvr (aka BGP-SPF) proposal, so I’m
> cc’ing that list here to avoid repeating the discussion there.  Also, I
> noticed you forwarded your message to dcrouting, so I’m cc’ing that list as
> well.
>
> Thanks!
>
> Alvaro.
>