Last Call: <draft-ietf-rift-applicability-14.txt> (RIFT Applicability) to Informational RFC

The IESG <iesg-secretary@ietf.org> Wed, 17 April 2024 13:44 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-rift-applicability-14.txt> (RIFT Applicability) to Informational RFC
Auto-Submitted: auto-generated
Precedence: bulk
CC: aretana.ietf@gmail.com, draft-ietf-rift-applicability@ietf.org, james.n.guichard@futurewei.com, rift-chairs@ietf.org, rift@ietf.org, zzhang@juniper.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <171336148303.45572.16746790453481750377@ietfa.amsl.com>
Date: Wed, 17 Apr 2024 06:44:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/TE-7VEqoJRzQgdTupZNBiGJhi_E>

The IESG has received a request from the Routing In Fat Trees WG (rift) to
consider the following document: - 'RIFT Applicability'
  <draft-ietf-rift-applicability-14.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-05-01. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document discusses the properties, applicability and operational
   considerations of RIFT in different network scenarios.  It intends to
   provide a rough guide how RIFT can be deployed to simplify routing
   operations in Clos topologies and their variations.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-rift-applicability/



No IPR declarations have been submitted directly on this I-D.

Last Call: <draft-ietf-rift-applicability-14.txt>… The IESG