Fwd: [Rift] kicking off the charter discussion

Alvaro Retana <aretana.ietf@gmail.com> Sat, 06 January 2018 03:24 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2A06712785F; Fri, 5 Jan 2018 19:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id IPvWOhjlVIfg; Fri, 5 Jan 2018 19:24:38 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (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 AC83312420B; Fri, 5 Jan 2018 19:24:38 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id h2so5455138oti.5; Fri, 05 Jan 2018 19:24:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:date:message-id:subject:to; bh=ZSc08mlMja7KUjNucODdRWuuFebXi8jzmldG5vnD0eU=; b=oW15fyaJejR4TGAnEW+neZb7Xcgx7Niu1+nt/mdzUmGUfloESSEnzArx5/uPmIBWNP sVv4Saqzh9lNJ82nBx486SB5n+zbN9oginxNXjqEhWsBrr7DJu1vz+rniUnx48P+cchW UxJrCslZMSoLf062T/+FVltftHk32lgt6A55aoxDugZRFTTiUFMbiWDpZeBocI6ZZfGv 6uU1COdSWvzwtVlb8PoW+1xf5SHKZjwRyt+j7DWBHVNlb1AONHIh9UtkVpRQXyqHwNgJ PPAPzHuwCkg3l22bBtFPUseba99Idzzkf0QL4IMqzSEIKjkZsdOiOzME/8v494f8Sdbh 1zrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=ZSc08mlMja7KUjNucODdRWuuFebXi8jzmldG5vnD0eU=; b=q8P4B9pc6EIuTxx8euZudt0mzc5lWXtucGFA5Qyn/KOHjBsVoxsPNXafHahHL2Zlbt YBl258yJ019QlrWnSHXKWpV8w2B+RR7JQeyMYMKTwBgV7nc0bbhAIGCsaJxNm7VUAX7R loWDkt/3SQPWIVEdWkR1Pb8IBS9QBUHY99XIMlIqf8Cs+2Q7QoDq9oTTBhDK7wy490/E nhBZGXKJOd6Kq8QBk4ZaDk44yA5FIIlu/0oYlm1JP/RzHar5aBNWagDBTrB0anexzesY g6P56vNWUJNf/KoCYWBeKiqIq2N3sgntrH4O4cXeFUjfzkTVgR9mdfIx/Kz1S6f+h5OG HmcQ==
X-Gm-Message-State: AKwxytdFfHArxVjh0x5FrMerU/SF9pP01E3QMa7vxFFP0UBvvZzQRP54 S3AJwlfHe34/Rd5qFpGTkCl153YwvoPIBfDEfrY=
X-Google-Smtp-Source: ACJfBosVyhhBXULv8ZniCVrUG9xmczCcPXG3T9OwrNX6h7nnnbdOhXQN+/mfY1m9KebYUCWq6e4IvCor97siYtd8Z/E=
X-Received: by with SMTP id u9mr2837566oth.164.1515209077635; Fri, 05 Jan 2018 19:24:37 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 5 Jan 2018 19:24:37 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Fri, 5 Jan 2018 19:24:37 -0800
Message-ID: <CAMMESswZLjEzNrdoCyox4U6sd51T6Cmin=i7hjoEPUa2NCdTJA@mail.gmail.com>
Subject: Fwd: [Rift] kicking off the charter discussion
To: routing-discussion@ietf.org, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="f40304353f64d53da00562131a94"
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/bagmRCX1moBspt717LZH7OodIqs>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Jan 2018 03:24:41 -0000


If you are interested in this topic, please make comments and send feedback
on the rift@ietf.org list.



On January 5, 2018 at 3:03:25 AM, Alia Atlas (akatlas@gmail.com) wrote:

Tony, Jeffrey Zhang, I, and others have been discussing possible RIFT WG
charters with Alvaro.  Here is what we have so far.  Comments and
improvements would be most welcome.

Routing in Fat Trees (RIFT)

Clos and Fat-Tree topologies have gained prominence in data center networks
as a result of a trend towards centralized data center network
architectures that may deliver computation and storage services.

The Routing in Fat Trees (RIFT) protocol addresses the demands of routing
in Clos and Fat-Tree networks via a mixture of both link-state and
distance-vector techniques colloquially described as 'link-state towards
the spine and distance vector towards the leafs'.  RIFT uses this hybrid
approach to focus on networks with regular topologies with a high degree of
connectivity, a defined directionality, and large scale.

The RIFT Working Group will work on a standards track specification of a
specialized, dynamic routing protocol for Clos and fat-tree network
topologies. The protocol will:

- deal with automatic construction of fat-tree topologies based on
detection of links,
- minimize the amount of routing state held at each topology level,
- automatically prune topology distribution exchanges to a
sufficient subset of links,
- support automatic disaggregation of prefixes on link and node failures to
prevent black-holing and suboptimal routing,
- allow traffic steering and re-routing policies,
- and provide mechanisms to synchronize a limited key-value data-store
that can be used after protocol convergence.

It is important that nodes participating in the protocol should need only
very light configuration and should be able to join a network as leaf nodes
simply by connecting to the network using default configuration.

The protocol must support IPv6 and should also support IPv4.

The Working Group may establish additional requirements to constrain and
inform their work.

The RIFT Working Group is chartered for the following list of items:

- A Standards Track specification based on draft-przygienda-rift. The
document will include:

  - an Implementation Status section as described in RFC 7942
  - an Operational Considerations section to explain how the protocol is
configured, deployed, and diagnosed
  - Security and Privacy Considerations, although this material may refer
to a separate Threat Analysis document (q.v.).
  - A YANG module focused on configuration of protocol instances
  - An Applicability Statement that describes how to deploy and configure
the protocol in networks with different topologies
  - A Security Threat Analysis document that describes the attack vectors
and mitigations that shall be sent for publication at the same time as the
protocol specification.


  Feb 2018 Adopt a protocol specification document
  Feb 2019 Submit protocol specification to IESG for publication
  Feb 2019 Submit Threat Analysis to IESG for publication
  Apr 2019 Submit YANG module to IESG for publication
  Apr 2019 Submit Applicability Statement to IESG for publication



Rift mailing list