RE: [Rift] kicking off the charter discussion

"Adrian Farrel" <adrian@olddog.co.uk> Sat, 06 January 2018 19:48 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76BC8128959; Sat, 6 Jan 2018 11:48:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
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 H1eIKA46z_-Z; Sat, 6 Jan 2018 11:48:38 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A666D124205; Sat, 6 Jan 2018 11:48:37 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id w06JmYfb006343; Sat, 6 Jan 2018 19:48:34 GMT
Received: from 950129200 ([193.56.243.35]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id w06JmWfF006330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 6 Jan 2018 19:48:33 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Alvaro Retana'" <aretana.ietf@gmail.com>
Cc: <routing-discussion@ietf.org>, <rtgwg@ietf.org>
References: <CAMMESswZLjEzNrdoCyox4U6sd51T6Cmin=i7hjoEPUa2NCdTJA@mail.gmail.com>
In-Reply-To: <CAMMESswZLjEzNrdoCyox4U6sd51T6Cmin=i7hjoEPUa2NCdTJA@mail.gmail.com>
Subject: RE: [Rift] kicking off the charter discussion
Date: Sat, 6 Jan 2018 19:48:34 -0000
Message-ID: <002601d38727$57b4b010$071e1030$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01D38727.57C244A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMzL2uhu7Viq2qc1OoXva7zQ+HgrqCn7hkQ
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.2.0.1013-23578.002
X-TM-AS-Result: No--25.718-10.0-31-10
X-imss-scan-details: No--25.718-10.0-31-10
X-TMASE-MatchedRID: 8HTFlOrbAtG6dV6AbIg41p1U1lojafr/g3XZcphu4kupxIL5viAGNAFx JQwzL/yF2YJ36PQpkbzbAqeSI3xDnShAwBpwK3XPW7gz/Gbgpl4K3iJpXUOQQxW+93iqRvX7V2O iGxTSnduuqVF0LsZuzRHyJWk7t0ytOaS9U7Z42f57sw7yO+Y9LNZKsq3DGpalvQIe0iBJ63EnP8 WWLvfAyFVuZQG2jzkwDMkIXnVvXPuziThmwPb+1TCj6xe3SuezB4Id7CiQcz/AzMkrlTL3Pp3xj riW4ma/m2CJNcBHUtXn1xYiO/F4jXjxgHkp9duC7T+j7/gPsPMS12tj9Zvd82so23uKlCJjfiJg EbG3V+QFiULpPd2fD+YshxIte+eXkdwNWPvebh2628cXbnOhT0yWLwjUVKFu+VFLFq8A8jW2fEb PR0rynzFn1ScbWur/QrbWJq0bZcjaqMoBhXwtRiBg3q+CymTwWEPEl3ozFuNXJyCkmYopd/ENJs pW4K4YPVLKIEs0GLW0F0wsmVGCn+RSSJk4GjSywkMSqacJzSum17CUF0OKCb/FQgGhXj1Wc66U8 x0uyZmQtPeY3/HeX0zs6tP/J/n0mv/lCFMzyYLQfDWILG9BqTTbofuc5kuvf7FDYGpyXq3QarbX +8U9GYIrAaGdidrJqSfQEB91VdVcNOa3zFU5XzGfHCHX/mgUbv16+gil4jdMOjKUxCZwr3mGgNm gsYErgHo2pwB65bSnRkwgj4khmPJn3YGdiqTm/O70vD0Lt8ATbU1KYGoQp3XwPGvwnyr47/+9sw uISRVYVA2Tj4cKiIcypU5vI8wyw1hXve9gEVCeAiCmPx4NwGmRqNBHmBve1B0Hk1Q1KyJck9lvx NcntYEliUr8JkQ/SrGvbSw43pZbkqQpDu0tbAW8XWTVw2sCZm9x7imJdKxYqTIUvCfO1A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/1jmnpDRv9K80qLqM2xa4otleJzs>
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 19:48:41 -0000

Hey Alvaro,
 
I looked for the sign-up page for rift@ietf.org at https://datatracker.ietf.org/list/wg/ and https://www.ietf.org/list/nonwg.html but nothing shows up.
Maybe, I thought, there is a WG page at https://datatracker.ietf.org/wg/rift where the draft charter shows up and the details of the mailing list can be found, but no.
 
Now, of course, I can work it out from the normal format (an there it is in the signature of Alia's email autogenerated by the list.
 
So, for those who wondered, join the list at https://www.ietf.org/mailman/listinfo/rift
 
But perhaps an AD could fix up the other stuff?
 
Cheers,
Adrian
--
Support an author and your imagination
Tales from the Wood - Eighteen new fairy tales
More Tales from the Wood - Eighteen MORE new fairy tales
Tales from Beyond the Wood - A bumper collection of twenty-two new tales
https://www.feedaread.com/profiles/8604/
http://www.amazon.co.uk/Tales-Wood-Adrian-Farrel/dp/1786100924
Or buy from me direct.
 
 
 
From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alvaro Retana
Sent: 06 January 2018 03:25
To: routing-discussion@ietf.org; rtgwg@ietf.org
Subject: Fwd: [Rift] kicking off the charter discussion
 
FYI..
 
If you are interested in this topic, please make comments and send feedback on the rift@ietf.org list.
 
Thanks!
 
Alvaro.
 
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.

Milestones

  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 
============
Thanks,
Alia
_______________________________________________ 
Rift mailing list 
Rift@ietf.org 
https://www.ietf.org/mailman/listinfo/rift