[Rift] RIFT charter discussion

["Jeffrey (Zhaohui) Zhang" <[e-mail]>]

Hi,

One of the agenda items is charter discussion.

We had a discussion in IETF114 based on one slide:


This time we want to look at the detailed text (see below) and start a more formal charter review.

Please note that the first two paragraphs are the same as in current charter.
The first two items for continued work were spun off the early base spec, and the last two items are new additions (not discussed in IETF114).

Appreciate your review, comments, and discussions.

Thanks.
Jeff & Jeffrey

---- proposed new charter ----

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 leaves'.  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 is chartered work on a standards track specification of a
specialized, dynamic routing protocol for Clos and fat-tree network topologies,
and has finished the following work items:

 - A Standards Track base protocol specification: draft-ietf-rift-rift
 - A YANG module focused on configuration and monitoring of protocol instances:
   draft-ietf-rift-yang
 - An Applicability Statement that describes how to deploy and configure the
   protocol in networks with different topologies: draft-ietf-rift-applicability

The WG will continue to work on standards track specifications on the following:

 - KV Registry
 - Policy Guided Prefix
 - Segment Routing support
 - Using RIFT Zero Touch Provisioning mechanism to automatically provision an
   EVPN overlay
 - Using RIFT Zero Touch Provisioning mechanism to automatically provision
   IS-IS Flood Reflection topologies
 - Multicast support
 - Leaf ring support

Juniper Business Use Only