[secdir] [new-work] WG Review: Routing In Fat Trees (rift)

The IESG <iesg@ietf.org> Fri, 26 January 2018 21:05 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF7012DA45; Fri, 26 Jan 2018 13:05:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1517000716; bh=Wo5HLa/QGGs73z52dOUpmq8wYYKZlT9zsfM8bRRHHEE=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=v4NBIrHr8r+mMYfTzzD9k1dnYG0edSCO8aKoxUlKSKLXz6e2cax9hZBrfuXVZ/VjR pB+6FTd4em8v6H3NPJQyWyXcAWFuDjOQxoTAAZ1zAFyUyh2QAhkep8wArSwiXn8FCF VLN1YYOLdMeWpWI31Bglj6aQJG45rfaWtiuHhB4M=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC5712DA12 for <new-work@ietf.org>; Fri, 26 Jan 2018 13:05:09 -0800 (PST)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: <new-work@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.70.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Reply_to: <iesg@ietf.org>
Message-ID: <151700070949.4399.17288791167199581988.idtracker@ietfa.amsl.com>
Date: Fri, 26 Jan 2018 13:05:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-work/q5oQqHBd5MekEihUKCUL0HqXjE8>
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.22
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: "new-work" <new-work-bounces@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/ESzxTjuv5m_HOUYNMnS6Oy1Tq34>
X-Mailman-Approved-At: Fri, 26 Jan 2018 13:45:10 -0800
Subject: [secdir] [new-work] WG Review: Routing In Fat Trees (rift)
X-BeenThere: secdir@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 21:05:16 -0000

A new IETF WG has been proposed in the Routing Area. The IESG has not made
any determination yet. The following draft charter was submitted, and is
provided for informational purposes only. Please send your comments to the
IESG mailing list (iesg@ietf.org) by 2018-02-05.

Routing In Fat Trees (rift)
Current status: Proposed WG

  Zhaohui Zhang <zzhang@juniper.net>;

Assigned Area Director:
  Alvaro Retana <aretana.ietf@gmail.com>;

Routing Area Directors:
  Alia Atlas <akatlas@gmail.com>;
  Alvaro Retana <aretana.ietf@gmail.com>;
  Deborah Brungard <db3546@att.com>;

Mailing list:
  Address: rift@ietf.org
  To subscribe: https://www.ietf.org/mailman/listinfo/rift
  Archive: https://mailarchive.ietf.org/arch/search/?email_list=rift

Group page: https://datatracker.ietf.org/group/rift/

Charter: https://datatracker.ietf.org/doc/charter-ietf-rift/

Data Centers have been steadily growing to commonly host tens of thousands
of end points, or more, in a single network.  Because of their topologies
(traditional and emerging), traffic patterns, need for fast restoration,
and for low human intervention, data center networks have a unique set of
requirements that is resulting in the design of routing solutions specific
to them.  Clos and Fat-Tree topologies have gained popularity 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 that 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

 - A YANG module focused on configuration and monitoring 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


Mar 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

new-work mailing list