Hey Alvaro,
 
I looked for the sign-up page for [email protected] 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:[email protected]] On Behalf Of Alvaro Retana
Sent: 06 January 2018 03:25
To: [email protected]; [email protected]
Subject: Fwd: [Rift] kicking off the charter discussion
 
FYI..
 
If you are interested in this topic, please make comments and send feedback on 
the [email protected] list.
 
Thanks!
 
Alvaro.
 
On January 5, 2018 at 3:03:25 AM, Alia Atlas ([email protected]) 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 
[email protected] 
https://www.ietf.org/mailman/listinfo/rift 
_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to