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

Alvaro Retana <aretana.ietf@gmail.com> Thu, 04 January 2018 23:02 UTC

Return-Path: <aretana.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 BB9C1126BF7; Thu, 4 Jan 2018 15:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 L5uNiMSXIB4a; Thu, 4 Jan 2018 15:02:42 -0800 (PST)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::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 DA06B126B6E; Thu, 4 Jan 2018 15:02:41 -0800 (PST)
Received: by mail-ot0-x236.google.com with SMTP id 97so36270otj.13; Thu, 04 Jan 2018 15:02:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=/vharC6XqmhTbYQsojGFS3lPraWqh5fOutlWSGfXu90=; b=VhU+RU12PhnIrcFgBXB6i1fcAkAspPiCizdh2pZWTGCIbf+4ELbSMwTqnQC1Vj2hJN Iczz/xkk19qers1qylNEXaxTjZtjY2/yLoviOy/j5TX/7Yv5KygegvucprRfNYTDgc6c 2vSbdtxNFZHHJdSjrz5idVv8XxJpxVP/l7p4U2LklqmfXLRMv/wTX8EDWkR0St3qls31 PYkdVJ3yFhzeTHuNxCo5HFrWZ7XInxNSxQBQM1Hnftech7ob8hmC+Xxgx8zM6xKcgnC9 wZGynDFU1+Uua89KttprfCZ7hlmYiO3YUvUZrmZIUZBPEpAvPD1g1scXZ8mBs5+Jdfnw Em3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=/vharC6XqmhTbYQsojGFS3lPraWqh5fOutlWSGfXu90=; b=Ry/MGoQc1/rGKdOoM8xxXBPC/usP29tDa6B08RCX85sdozGfgU7OsxgoCc3KM+YFbS Xegf59WSNFg12pAF563stS1MYbUG25X/73N3MqORsWUglNPmJr7uzYIjzkUHNVhSNXKV iOaCYeqSz5cMZAM2XQFerrHBEz6avwRH6alPANrBNfFhhpHIm2hHVvMAGn+/aU0SC0ID 3jkN16gk1LHlxaSq2IcEJpax68rKIG5TTEjVv6lJA1OGCScL3h7MsbaSUcP2PnVMcAs/ YhcoBePzdzgvblIqzBMqgJQ5OWNKBg5kkVWgdvEKAYJgoHT2wuVyGJk3S8Nx0Fdo44TO L8Kg==
X-Gm-Message-State: AKwxyteAm3hgXsTT4A7M9Ph3RXDexY56v4+mIkudQCff4A1tQwmyucP/ PfG9FXFfy3ElakuI9q2J5dgBZgO9fuKlaijAtmE=
X-Google-Smtp-Source: ACJfBosGobI0+2nrcxLrPc2op9uNqoxPxrbinSB0vMMfyF1Ag61N0OXQf7QZJW6u+ZONVTAzzTbS+a2ub+LnQJzKRvM=
X-Received: by 10.157.89.137 with SMTP id u9mr702509oth.164.1515106961235; Thu, 04 Jan 2018 15:02:41 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 4 Jan 2018 15:02:40 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CA+b+ERnLiD8DMmUCJUz72Py3dk2LP=u7Zb4BxfOzs2=7t=h3mA@mail.gmail.com>
References: <CAG4d1rd6=TXVtkHBQHSGkL3KKXF6CPs9ktsr725MWjDSsC9QiQ@mail.gmail.com> <CA+b+ERnLiD8DMmUCJUz72Py3dk2LP=u7Zb4BxfOzs2=7t=h3mA@mail.gmail.com>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Thu, 04 Jan 2018 15:02:40 -0800
Message-ID: <CAMMESszh69YiyMoQvsRrzv+LFWzkG8ij9NRrGeF-opF7RO=eww@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Cc: rift@ietf.org, lsvr@ietf.org, "dcrouting@ietf.org" <dcrouting@ietf.org>
Content-Type: multipart/alternative; boundary="f40304353f6438a2010561fb5471"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dcrouting/1-X4ULLQrwQ9H5azFvGbui8tYbs>
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:02:45 -0000

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.