
From nobody Fri Jan  5 19:24:46 2018
Return-Path: <aretana.ietf@gmail.com>
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 2A06712785F; Fri,  5 Jan 2018 19:24:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 IPvWOhjlVIfg; Fri,  5 Jan 2018 19:24:38 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC83312420B; Fri,  5 Jan 2018 19:24:38 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id h2so5455138oti.5; Fri, 05 Jan 2018 19:24:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:date:message-id:subject:to; bh=ZSc08mlMja7KUjNucODdRWuuFebXi8jzmldG5vnD0eU=; b=oW15fyaJejR4TGAnEW+neZb7Xcgx7Niu1+nt/mdzUmGUfloESSEnzArx5/uPmIBWNP sVv4Saqzh9lNJ82nBx486SB5n+zbN9oginxNXjqEhWsBrr7DJu1vz+rniUnx48P+cchW UxJrCslZMSoLf062T/+FVltftHk32lgt6A55aoxDugZRFTTiUFMbiWDpZeBocI6ZZfGv 6uU1COdSWvzwtVlb8PoW+1xf5SHKZjwRyt+j7DWBHVNlb1AONHIh9UtkVpRQXyqHwNgJ PPAPzHuwCkg3l22bBtFPUseba99Idzzkf0QL4IMqzSEIKjkZsdOiOzME/8v494f8Sdbh 1zrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=ZSc08mlMja7KUjNucODdRWuuFebXi8jzmldG5vnD0eU=; b=q8P4B9pc6EIuTxx8euZudt0mzc5lWXtucGFA5Qyn/KOHjBsVoxsPNXafHahHL2Zlbt YBl258yJ019QlrWnSHXKWpV8w2B+RR7JQeyMYMKTwBgV7nc0bbhAIGCsaJxNm7VUAX7R loWDkt/3SQPWIVEdWkR1Pb8IBS9QBUHY99XIMlIqf8Cs+2Q7QoDq9oTTBhDK7wy490/E nhBZGXKJOd6Kq8QBk4ZaDk44yA5FIIlu/0oYlm1JP/RzHar5aBNWagDBTrB0anexzesY g6P56vNWUJNf/KoCYWBeKiqIq2N3sgntrH4O4cXeFUjfzkTVgR9mdfIx/Kz1S6f+h5OG HmcQ==
X-Gm-Message-State: AKwxytdFfHArxVjh0x5FrMerU/SF9pP01E3QMa7vxFFP0UBvvZzQRP54 S3AJwlfHe34/Rd5qFpGTkCl153YwvoPIBfDEfrY=
X-Google-Smtp-Source: ACJfBosVyhhBXULv8ZniCVrUG9xmczCcPXG3T9OwrNX6h7nnnbdOhXQN+/mfY1m9KebYUCWq6e4IvCor97siYtd8Z/E=
X-Received: by 10.157.89.137 with SMTP id u9mr2837566oth.164.1515209077635; Fri, 05 Jan 2018 19:24:37 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 5 Jan 2018 19:24:37 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Fri, 5 Jan 2018 19:24:37 -0800
Message-ID: <CAMMESswZLjEzNrdoCyox4U6sd51T6Cmin=i7hjoEPUa2NCdTJA@mail.gmail.com>
Subject: Fwd: [Rift] kicking off the charter discussion
To: routing-discussion@ietf.org, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="f40304353f64d53da00562131a94"
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/bagmRCX1moBspt717LZH7OodIqs>
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 03:24:41 -0000

--f40304353f64d53da00562131a94
Content-Type: text/plain; charset="UTF-8"

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

--f40304353f64d53da00562131a94
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word"><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto">FYI..</div><div id=3D"bloop_customfont" style=3D"=
font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px=
;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-he=
ight:auto">If you are interested in this topic, please make comments and se=
nd feedback on the <a href=3D"mailto:rift@ietf.org">rift@ietf.org</a>=C2=A0=
list.</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Aria=
l;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></d=
iv><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-s=
ize:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Thanks!</div><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D=
"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;colo=
r:rgba(0,0,0,1.0);margin:0px;line-height:auto">Alvaro.</div> <br><p class=
=3D"airmail_on">On January 5, 2018 at 3:03:25 AM, Alia Atlas (<a href=3D"ma=
ilto:akatlas@gmail.com">akatlas@gmail.com</a>) wrote:</p> <blockquote type=
=3D"cite" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div dir=3D"ltr">Tony, Jeffrey Zhang, I, and others have been
discussing possible RIFT WG charters with Alvaro.=C2=A0 Here is
what we have so far.=C2=A0 Comments and improvements would be most
welcome.
<div><br></div>
<div>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</div>
<div>Routing in Fat Trees (RIFT)<br>
<br>
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.<br>
=C2=A0<br>
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
&#39;link-state towards the spine and distance vector towards the
leafs&#39;.=C2=A0 RIFT uses this hybrid approach to focus on networks
with regular topologies with a high degree of connectivity, a
defined directionality, and large scale.<br>
<br>
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:<br>
<br>
- deal with automatic construction of fat-tree topologies based on
detection of links,<br>
- minimize the amount of routing state held at each topology
level,<br>
- automatically prune topology distribution exchanges to a
sufficient=C2=A0subset of links,<br>
- support automatic disaggregation of prefixes on link and node
failures to prevent black-holing and suboptimal routing,<br>
- allow traffic steering and re-routing policies,<br>
- and provide mechanisms to synchronize a limited key-value
data-store that=C2=A0can be used after protocol convergence.<br>
<br>
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.<br>
<br>
The protocol must support IPv6 and should also support IPv4.<br>
<br>
The Working Group may establish additional requirements to
constrain and inform their work.<br>
<br>
The RIFT Working Group is chartered for the following list of
items:<br>
<br>
- A Standards Track specification based on draft-przygienda-rift.
The document will include:<br>
<br>
=C2=A0 - an Implementation Status section as described in RFC
7942<br>
=C2=A0 - an Operational Considerations section to explain how the
protocol is configured, deployed, and diagnosed<br>
=C2=A0 - Security and Privacy Considerations, although this
material may refer to a separate Threat Analysis document
(q.v.).<br>
=C2=A0 - A YANG module focused on configuration of protocol
instances<br>
=C2=A0 - An Applicability Statement that describes how to deploy
and configure the protocol in networks with different
topologies<br>
=C2=A0 - 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.<br>
<br>
Milestones<br>
<br>
=C2=A0 Feb 2018 Adopt a protocol specification document<br>
=C2=A0 Feb 2019 Submit protocol specification to IESG for
publication<br>
=C2=A0 Feb 2019 Submit Threat Analysis to IESG for
publication<br>
=C2=A0 Apr 2019 Submit YANG module to IESG for publication<br>
=C2=A0 Apr 2019 Submit Applicability Statement to IESG for
publication
<p class=3D"gmail-MsoNormal">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</p>
<p class=3D"gmail-MsoNormal">Thanks,</p>
<p class=3D"gmail-MsoNormal">Alia</p>
</div>
</div>


_______________________________________________
<br>Rift mailing list
<br><a href=3D"mailto:Rift@ietf.org">Rift@ietf.org</a>
<br><a href=3D"https://www.ietf.org/mailman/listinfo/rift">https://www.ietf=
.org/mailman/listinfo/rift</a>
<br></div></div></span></blockquote> <div id=3D"bloop_sign_1515208978325315=
072" class=3D"bloop_sign"></div></body></html>

--f40304353f64d53da00562131a94--


From nobody Sat Jan  6 11:48:43 2018
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

This is a multipart message in MIME format.

------=_NextPart_000_0027_01D38727.57C244A0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Alvaro,
=20
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.
=20
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.
=20
So, for those who wondered, join the list at =
https://www.ietf.org/mailman/listinfo/rift
=20
But perhaps an AD could fix up the other stuff?
=20
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.
=20
=20
=20
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
=20
FYI..
=20
If you are interested in this topic, please make comments and send =
feedback on the rift@ietf.org list.
=20
Thanks!
=20
Alvaro.
=20
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.=20
=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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.
=20
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=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Thanks,
Alia
_______________________________________________=20
Rift mailing list=20
Rift@ietf.org=20
https://www.ietf.org/mailman/listinfo/rift=20

------=_NextPart_000_0027_01D38727.57C244A0
Content-Type: text/html;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DProgId content=3DWord.Document><meta name=3DGenerator =
content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01D38727.3B577CE0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.airmailon, li.airmailon, div.airmailon
	{mso-style-name:airmail_on;
	mso-style-unhide:no;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
p.gmail-msonormal, li.gmail-msonormal, div.gmail-msonormal
	{mso-style-name:gmail-msonormal;
	mso-style-unhide:no;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Hey =
Alvaro,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>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.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>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.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>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.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>So, for those who wondered, =
join the list at =
https://www.ietf.org/mailman/listinfo/rift<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>But perhaps an AD could fix up =
the other stuff?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>--<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>Support an author and your =
imagination<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>Tales from the Wood - Eighteen =
new fairy tales<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>More Tales from the Wood - =
Eighteen MORE new fairy tales<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-bidi-font-size:10.5pt;font-family:"Calibri"=
,"sans-serif";mso-fareast-font-family:Calibri;mso-bidi-font-family:"Times=
 New =
Roman";color:#1F497D;mso-fareast-language:EN-US;mso-no-proof:yes'>Tales =
from Beyond the Wood - A bumper collection of twenty-two new =
tales<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>https://www.feedaread.com/profiles=
/8604/<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>http://www.amazon.co.uk/Tales-Wood=
-Adrian-Farrel/dp/1786100924<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-fareast-=
font-family:"Times New Roman";mso-bidi-font-family:"Times New =
Roman";color:#1F497D;mso-no-proof:yes'>Or buy from me =
direct.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> rtgwg =
[mailto:rtgwg-bounces@ietf.org] <b>On Behalf Of </b>Alvaro =
Retana<br><b>Sent:</b> 06 January 2018 03:25<br><b>To:</b> =
routing-discussion@ietf.org; rtgwg@ietf.org<br><b>Subject:</b> Fwd: =
[Rift] kicking off the charter =
discussion<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div id=3D"bloop_customfont"><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'>FYI..<o:p></o:p></span></p></div><div =
id=3D"bloop_customfont"><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'><o:p>&nbsp;</o:p></span></p></div><div =
id=3D"bloop_customfont"><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'>If you are interested in this topic, =
please make comments and send feedback on the <a =
href=3D"mailto:rift@ietf.org">rift@ietf.org</a>&nbsp;list.<o:p></o:p></sp=
an></p></div><div id=3D"bloop_customfont"><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'><o:p>&nbsp;</o:p></span></p></div><div =
id=3D"bloop_customfont"><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'>Thanks!<o:p></o:p></span></p></div><div =
id=3D"bloop_customfont"><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'><o:p>&nbsp;</o:p></span></p></div><div =
id=3D"bloop_customfont"><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'>Alvaro.<o:p></o:p></span></p></div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'><o:p>&nbsp;</o:p></span></p><p =
class=3Dairmailon><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif"'>On =
January 5, 2018 at 3:03:25 AM, Alia Atlas (<a =
href=3D"mailto:akatlas@gmail.com">akatlas@gmail.com</a>) =
wrote:<o:p></o:p></span></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'>Tony, Jeffrey Zhang, I, and others have =
been discussing possible RIFT WG charters with Alvaro.&nbsp; Here is =
what we have so far.&nbsp; Comments and improvements would be most =
welcome. <o:p></o:p></span></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New =
Roman"'>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span=
></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New Roman"'>Routing in Fat Trees (RIFT)<br><br>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.<br>&nbsp;<br>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'.&nbsp; RIFT uses this hybrid approach to focus on networks =
with regular topologies with a high degree of connectivity, a defined =
directionality, and large scale.<br><br>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:<br><br>- deal with automatic construction of fat-tree topologies =
based on detection of links,<br>- minimize the amount of routing state =
held at each topology level,<br>- automatically prune topology =
distribution exchanges to a sufficient&nbsp;subset of links,<br>- =
support automatic disaggregation of prefixes on link and node failures =
to prevent black-holing and suboptimal routing,<br>- allow traffic =
steering and re-routing policies,<br>- and provide mechanisms to =
synchronize a limited key-value data-store that&nbsp;can be used after =
protocol convergence.<br><br>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.<br><br>The protocol must support IPv6 and =
should also support IPv4.<br><br>The Working Group may establish =
additional requirements to constrain and inform their work.<br><br>The =
RIFT Working Group is chartered for the following list of =
items:<br><br>- A Standards Track specification based on =
draft-przygienda-rift. The document will include:<br><br>&nbsp; - an =
Implementation Status section as described in RFC 7942<br>&nbsp; - an =
Operational Considerations section to explain how the protocol is =
configured, deployed, and diagnosed<br>&nbsp; - Security and Privacy =
Considerations, although this material may refer to a separate Threat =
Analysis document (q.v.).<br>&nbsp; - A YANG module focused on =
configuration of protocol instances<br>&nbsp; - An Applicability =
Statement that describes how to deploy and configure the protocol in =
networks with different topologies<br>&nbsp; - 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.<br><br>Milestones<br><br>&nbsp; Feb 2018 Adopt a protocol =
specification document<br>&nbsp; Feb 2019 Submit protocol specification =
to IESG for publication<br>&nbsp; Feb 2019 Submit Threat Analysis to =
IESG for publication<br>&nbsp; Apr 2019 Submit YANG module to IESG for =
publication<br>&nbsp; Apr 2019 Submit Applicability Statement to IESG =
for publication <o:p></o:p></span></p><p class=3Dgmail-msonormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif"'>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p><p =
class=3Dgmail-msonormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Thanks,<o=
:p></o:p></span></p><p class=3Dgmail-msonormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Alia<o:p>=
</o:p></span></p></div></div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Helvetica","sans-serif";mso-fareas=
t-font-family:"Times New =
Roman"'>_______________________________________________ <br>Rift mailing =
list <br><a href=3D"mailto:Rift@ietf.org">Rift@ietf.org</a> <br><a =
href=3D"https://www.ietf.org/mailman/listinfo/rift">https://www.ietf.org/=
mailman/listinfo/rift</a> =
<o:p></o:p></span></p></div></div></blockquote></div></div></body></html>
------=_NextPart_000_0027_01D38727.57C244A0--



From nobody Sat Jan  6 16:39:22 2018
Return-Path: <aretana.ietf@gmail.com>
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 DD44012421A; Sat,  6 Jan 2018 16:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.738
X-Spam-Level: 
X-Spam-Status: No, score=-1.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sviqvsAk8X-r; Sat,  6 Jan 2018 16:39:19 -0800 (PST)
Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 141F41242F7; Sat,  6 Jan 2018 16:39:19 -0800 (PST)
Received: by mail-oi0-x243.google.com with SMTP id g6so5350403oib.11; Sat, 06 Jan 2018 16:39:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=JRKfuQfr5mLxniNAyMYSSv0R7u2UkYepC4Pd1C+0/UI=; b=Z0vH19V8kkmJ5bVS34G6DGnreNEi87qFBFAVXw11ZCrovyRPylac5HbKQAGm7uJJ9L Ru3N1WLP1J1cNgGmIcgyndhNq/l8w2oTac/TOtO4AwwqhC1eM3tXBfUXLhg/L6EY6hUe cjXI6CF+ozhtKlwFbTM7KGbGpeW20ufFMaBjyu53lQ9SKHTvFIujz9x/cJJUK7G6tSk3 U8CM6DS96uF9E2CmID2ES8m+zSztZxpndU0V86G8gC+twyGEnsGDThBFpi/HHykq5h+t XyWxssgsnC/eoAi0aMvBZwbyha1en5HwCaotdJWz8JtMeZ6azIErFQ7fO8vJgTRv5MVJ 68OQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=JRKfuQfr5mLxniNAyMYSSv0R7u2UkYepC4Pd1C+0/UI=; b=mCmwkSmQlU212Rh1FE4iRzu93/CfAxX/RLEAlVRge1GP0Pk2QJPz8OyOxYpdyaMKGp LJpC3f+k8AdNtHB4rqIxNNGldHiCo5B7BIHanhCUpH2dtKYN8rzYQG8vDJxys+CHER7Q jwm2XD+d8cH1qBIKNUYcb3zeE38KnKScug7rMaUkSXhOf0H8oFhsCLmQ/zL1XMqec3lA Pn6lKxaN/Sf9cS8u9kTsP7GC0ElHC/jmlPG7s+n8lTrjBazQ9dwa8Me6ZQ45QSjQsoQM rne8X77/FYe9YFVd7Z0IE+Gfo5qyiottKATKaCoGxxrs7IzQkZopp/pGsPME0Bh4wUsA nX2w==
X-Gm-Message-State: AKGB3mKD3W66xRcFy1h5cELs1AKK87eGgNlYhNEl+z0wJzWQohh9eYCF gvdQ2yHBdRkvHIfkL5ZdNaLtfmtdqe6Q9d6a9FA=
X-Google-Smtp-Source: ACJfBosvXIjzJsSMnJcnDi126dbFVwNqfHJbnRuYrm2IaQ47lDwRoXNBcyE2v96cZ1rRV+pYqDCAGkH6Bgxua4p9WN0=
X-Received: by 10.202.79.129 with SMTP id d123mr4015287oib.308.1515285558460;  Sat, 06 Jan 2018 16:39:18 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Sat, 6 Jan 2018 16:39:18 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <002601d38727$57b4b010$071e1030$@olddog.co.uk>
References: <CAMMESswZLjEzNrdoCyox4U6sd51T6Cmin=i7hjoEPUa2NCdTJA@mail.gmail.com> <002601d38727$57b4b010$071e1030$@olddog.co.uk>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Sat, 6 Jan 2018 16:39:18 -0800
Message-ID: <CAMMESszTOdvpm=ZOe59_16YZxiHY1ZHvMntjODKyYoJQYiWyfA@mail.gmail.com>
Subject: RE: [Rift] kicking off the charter discussion
To: adrian@olddog.co.uk
Cc: rtgwg@ietf.org, routing-discussion@ietf.org
Content-Type: multipart/alternative; boundary="001a113d76fa720a4b056224e9a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/YHeT4Cl6BFjdRP3W8U44TVGKCF8>
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: Sun, 07 Jan 2018 00:39:21 -0000

--001a113d76fa720a4b056224e9a0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Adrian:

Hi!

Yes.  I should have included a link.

I don=E2=80=99t know why the list doesn=E2=80=99t show up in the IETF Non-W=
G Mailing Lists
page =E2=80=94 I=E2=80=99ll have the list manager fix that.  I haven=E2=80=
=99t set up the WG-to-be
page yet =E2=80=94 waiting for more discussion.

Thanks!

Alvaro.

On January 7, 2018 at 3:48:35 AM, Adrian Farrel (adrian@olddog.co.uk) wrote=
:

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/rif=
t
 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?

--001a113d76fa720a4b056224e9a0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word"><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto">Adrian:</div><div id=3D"bloop_customfont" style=
=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin=
:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font=
-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;lin=
e-height:auto">Hi!</div><div id=3D"bloop_customfont" style=3D"font-family:H=
elvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:=
auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica=
,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Ye=
s.=C2=A0 I should have included a link.</div><div id=3D"bloop_customfont" s=
tyle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);ma=
rgin:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"=
font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px=
;line-height:auto">I don=E2=80=99t know why the list doesn=E2=80=99t show u=
p in the IETF Non-WG Mailing Lists page =E2=80=94 I=E2=80=99ll have the lis=
t manager fix that.=C2=A0 I haven=E2=80=99t set up the WG-to-be page yet =
=E2=80=94 waiting for more discussion.</div><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"f=
ont-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;=
line-height:auto">Thanks!</div><div id=3D"bloop_customfont" style=3D"font-f=
amily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-=
height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:He=
lvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:a=
uto">Alvaro.</div> <br><p class=3D"airmail_on">On January 7, 2018 at 3:48:3=
5 AM, Adrian Farrel (<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.c=
o.uk</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><di=
v><p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;fo=
nt-family:&#39;Times New Roman&#39;,serif;color:rgb(0,0,0);font-style:norma=
l;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:=
rgb(31,73,125)">I looked for the sign-up page for<span class=3D"Apple-conve=
rted-space">=C2=A0</span><a href=3D"mailto:rift@ietf.org" style=3D"color:pu=
rple;text-decoration:underline">rift@ietf.org</a><span class=3D"Apple-conve=
rted-space">=C2=A0</span>at<span class=3D"Apple-converted-space">=C2=A0</sp=
an><a href=3D"https://datatracker.ietf.org/list/wg/" style=3D"color:purple;=
text-decoration:underline">https://datatracker.ietf.org/list/wg/</a><span c=
lass=3D"Apple-converted-space">=C2=A0</span>and<span class=3D"Apple-convert=
ed-space">=C2=A0</span><a href=3D"https://www.ietf.org/list/nonwg.html" sty=
le=3D"color:purple;text-decoration:underline">https://www.ietf.org/list/non=
wg.html</a><span class=3D"Apple-converted-space">=C2=A0</span>but nothing s=
hows up.</span></p><p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;=
font-size:12pt;font-family:&#39;Times New Roman&#39;,serif;color:rgb(0,0,0)=
;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spaci=
ng:normal;text-align:start;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px"><span style=3D"font-size:11pt;font-family:Calibri,=
sans-serif;color:rgb(31,73,125)">Maybe, I thought, there is a WG page at<sp=
an class=3D"Apple-converted-space">=C2=A0</span><a href=3D"https://datatrac=
ker.ietf.org/wg/rift" style=3D"color:purple;text-decoration:underline">http=
s://datatracker.ietf.org/wg/rift</a><span class=3D"Apple-converted-space">=
=C2=A0</span>where the draft charter shows up and the details of the mailin=
g list can be found, but no.</span></p><p class=3D"MsoNormal" style=3D"marg=
in:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,se=
rif;color:rgb(0,0,0);font-style:normal;font-variant-caps:normal;font-weight=
:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfo=
rm:none;white-space:normal;word-spacing:0px"><span style=3D"font-size:11pt;=
font-family:Calibri,sans-serif;color:rgb(31,73,125)">=C2=A0</span></p><p cl=
ass=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:12pt;font-fami=
ly:&#39;Times New Roman&#39;,serif;color:rgb(0,0,0);font-style:normal;font-=
variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta=
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"=
><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,=
73,125)">Now, of course, I can work it out from the normal format (an there=
 it is in the signature of Alia&#39;s email autogenerated by the list.</spa=
n></p><p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:12p=
t;font-family:&#39;Times New Roman&#39;,serif;color:rgb(0,0,0);font-style:n=
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;tex=
t-align:start;text-indent:0px;text-transform:none;white-space:normal;word-s=
pacing:0px"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;co=
lor:rgb(31,73,125)">=C2=A0</span></p><p class=3D"MsoNormal" style=3D"margin=
:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,seri=
f;color:rgb(0,0,0);font-style:normal;font-variant-caps:normal;font-weight:n=
ormal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px"><span style=3D"font-size:11pt;fo=
nt-family:Calibri,sans-serif;color:rgb(31,73,125)">So, for those who wonder=
ed, join the list at<span class=3D"Apple-converted-space">=C2=A0</span><a h=
ref=3D"https://www.ietf.org/mailman/listinfo/rift" style=3D"color:purple;te=
xt-decoration:underline">https://www.ietf.org/mailman/listinfo/rift</a></sp=
an></p><p class=3D"MsoNormal" style=3D"margin:0cm 0cm 0.0001pt;font-size:12=
pt;font-family:&#39;Times New Roman&#39;,serif;color:rgb(0,0,0);font-style:=
normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;te=
xt-align:start;text-indent:0px;text-transform:none;white-space:normal;word-=
spacing:0px"><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;c=
olor:rgb(31,73,125)">=C2=A0</span></p><p class=3D"MsoNormal" style=3D"margi=
n:0cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,ser=
if;color:rgb(0,0,0);font-style:normal;font-variant-caps:normal;font-weight:=
normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfor=
m:none;white-space:normal;word-spacing:0px"><span style=3D"font-size:11pt;f=
ont-family:Calibri,sans-serif;color:rgb(31,73,125)">But perhaps an AD could=
 fix up the other stuff?</span></p><p class=3D"MsoNormal" style=3D"margin:0=
cm 0cm 0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif;=
color:rgb(0,0,0);font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px"><span style=3D"font-size:11pt;font=
-family:Calibri,sans-serif;color:rgb(31,73,125)">=C2=A0</span></p></div></s=
pan></blockquote> <div id=3D"bloop_sign_1515285394747661056" class=3D"bloop=
_sign"></div></body></html>

--001a113d76fa720a4b056224e9a0--


From nobody Wed Jan 10 17:23:03 2018
Return-Path: <7riw77@gmail.com>
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 4DB8E120713; Wed, 10 Jan 2018 17:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TdLsqSQ2f6cp; Wed, 10 Jan 2018 17:23:00 -0800 (PST)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B1D2120454; Wed, 10 Jan 2018 17:23:00 -0800 (PST)
Received: by mail-yw0-x22a.google.com with SMTP id g191so389773ywe.7; Wed, 10 Jan 2018 17:23:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=/Zxdb5szoVAgwl5qKdrV4XzwlfhNPkoKronBI7kJOUE=; b=k1+inkoSn9IjnPelDFIliTo/uz/jLwFwu/T36hnTIYYvHxjhX3Kporqr6n9miJM+UK ipH/NicFBJAZUxNwcNwae5cvnMbZb9RabW2YXXbj9dYJc46f1IxujJNTCBjSTY5MU/DS D8ANa4njl2y3330YaqNIJrcVgZCOu9uek2lcFV4GiEbK+YK9AvZrBrwedisy0RVhI62d 7o+0vGL5XONVkhAUiS3S8xaBR2OSQc2nAmsAHeh9vSrKqq/is3Z4i3i0XUzpSuz7+k6U /wxdS2kVBEWRMK2BcN6gbIKblDG/bacH4yZV6TDELTKLk4dm8uhYk+TEUENFDX4rcFid /+Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=/Zxdb5szoVAgwl5qKdrV4XzwlfhNPkoKronBI7kJOUE=; b=daiOpA6uwbHmG6MepVWQHGhqu1KJLEjqXAZQ5zTYy0O4UWbUhHP9+lyDNewSN1liXK rLes2GZk12kgVzP6pOZvAe8h4/U+SlEblV04DoWur82bSpXY9CsK8jGKTb3kTxEaT4Ai vWMLC8zjOdkna8zig/zMVTYVUlpt6cP8Rna7s5y20AYY4W0HTAQjuuv+oZp4O2TsnsAP M1SoLFkOiZuFUen4AO33zsdxEkxtxQSWyVzUXYGhJLpAccyj6zMCTFbMob2gacQujQAB //+r2rghNEyzHobGRs0aOXQrvAaA0zLJ3YTl058Lk9eMz+EroEkHcFyAP5sDLznLWFTm lOQQ==
X-Gm-Message-State: AKwxytf5GjYSXevSl0O6CcQU6uSSoIian32+3YVIq4chtu8eqbOhRGZh IOQstCH6zzfVBX5GCTMVb4c=
X-Google-Smtp-Source: ACJfBotysyR0J6r6gC2gu8Nw3PSVDqrEouaXGRiseWs+GmPGzJmlDDvD+icZx3JgZTvvL8mg5yHc+w==
X-Received: by 10.129.72.9 with SMTP id v9mr3285722ywa.241.1515633779832; Wed, 10 Jan 2018 17:22:59 -0800 (PST)
Received: from Russ ([2600:1700:720:1050:9091:85f3:6472:de3d]) by smtp.gmail.com with ESMTPSA id h21sm7680180ywk.43.2018.01.10.17.22.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Jan 2018 17:22:59 -0800 (PST)
From: <7riw77@gmail.com>
To: "'Alvaro Retana'" <aretana.ietf@gmail.com>, <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: Wed, 10 Jan 2018 20:22:58 -0500
Message-ID: <02e901d38a7a$b761a7b0$2624f710$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQMzL2uhu7Viq2qc1OoXva7zQ+HgrqCulRzg
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/ojknmdkCPSE949oROFbavocQFZI>
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: Thu, 11 Jan 2018 01:23:02 -0000

> 	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

I would tend to say "spine and leaf" here, rather than Clod -- Clos is =
one instance of a spine and leaf, but there are others.
=20
> 	- minimize the amount of routing state held at each topology level,

It is probably useful to indicate both topology and reachability state =
here, as they are two different things.

> 	- allow traffic steering and re-routing policies,

This might be a little underspecified ... I think this should probably =
include "using metrics and policy carried within the RIFT control =
plane." You can always hijack a path using PCEP or something else, so =
the requirement, as stated, just feels a little "weak."

> 	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.

"very light" might be better as "minimal?" It would be nice to have =
something with a more definite meaning here, but I=E2=80=99m not certain =
what.

> 	The protocol must support IPv6 and should also support IPv4.

In terms of carrying reachability for, or in terms of running on top of? =
Two different things.

=F0=9F=98=8A /r


From nobody Wed Jan 10 18:50:05 2018
Return-Path: <tonysietf@gmail.com>
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 8811D12E741; Wed, 10 Jan 2018 18:50:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 uzNnEf_5FYm9; Wed, 10 Jan 2018 18:50:00 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14042126C89; Wed, 10 Jan 2018 18:50:00 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id 141so2553942wme.3; Wed, 10 Jan 2018 18:49:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vzm4+xAInc6D8PFQoXWuWsh2jJkoxzvHGDW7QCR+43Y=; b=FyameYVrJjEueWn7kdyYwO3s+rjhHcSTCONTKwfGfDlcemYGyAQ+LNQruKnJD1fMum Fz24eXyXoKJkrjnIVOGFq86HxsABrquUIiainWl8+TkNCgPEHP7JdguIhvqWPr6MKuGQ z6vCv04UcNyLWkobIys4QYnotynXCS5FSzTUJWfmfOMrlkAxekhql9heoZqd76sNbRJp qjygzqgK7nJsxFdeDJbtM5n8Oxkt6LWXitQzbBjWBTiNkcW8wvS2QoYaMmQ7hhU/a2I9 uVaXWdNLReMXTUPu/eQDWjZF1VMsXX9t4Ros6gozYy+OaDaphSh6yXRv95L5YPHZFR6l vOKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vzm4+xAInc6D8PFQoXWuWsh2jJkoxzvHGDW7QCR+43Y=; b=d64AzT9Ivm0FhUrRE/2n093gfv3UPqvJvOy7MmXZWG0hQ4Eg3tDQJ7E79jpWkVS+WG GKB6hQV+4VfnTX8Kbkw4VW4z2gBPTwO1uu2l4ZJ06IXIph674UpLML25kjvezo6i+BXh h8RP7TQDRiv42ESs5oTGNUtx2gM2eBXZpq+ZwbvPS6WuDqXtIfToCtcCFv9BPdpmTh1G Iixd24sFEcZf+mxvTPxZmlT1DTwGjKLjlznt2DEUJ6YV87f6M1YMRaEFtOWF3d0P2pS/ u9zr3pOcQJaKQGxCc6vc3WwJu990hVzNbHReKJkc1d8Z+QDPZpNFUB13fo/azH53Wv5F 1uBA==
X-Gm-Message-State: AKGB3mKNKDGcdlip/3LxoYssJgPkDnRhy6pcYMmHiffSW/qP102D3SyU co8UWcV4rXnZKpP9/WFzv3Qw82Xjfs2yrrbw9KI=
X-Google-Smtp-Source: ACJfBouqMPlecm0+ekTazEMn98+PQBtjEXo0hXRMXGmqEEkZeWShlF38e8sNjN+8dyVDOJL9dPyXj33hDCxb6N0Zk2s=
X-Received: by 10.80.155.89 with SMTP id a25mr28738459edj.290.1515638998514; Wed, 10 Jan 2018 18:49:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.164.199 with HTTP; Wed, 10 Jan 2018 18:49:18 -0800 (PST)
In-Reply-To: <02e901d38a7a$b761a7b0$2624f710$@gmail.com>
References: <CAMMESswZLjEzNrdoCyox4U6sd51T6Cmin=i7hjoEPUa2NCdTJA@mail.gmail.com> <02e901d38a7a$b761a7b0$2624f710$@gmail.com>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Wed, 10 Jan 2018 18:49:18 -0800
Message-ID: <CA+wi2hO2LgDBAaBOE6B1Xs_oJx3-RNfEv4snC4DXtSy8H=KxhQ@mail.gmail.com>
Subject: Re: [Rift] kicking off the charter discussion
To: Russ White <7riw77@gmail.com>
Cc: Alvaro Retana <aretana.ietf@gmail.com>, routing-discussion@ietf.org, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c1aec781d3eee056277343f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/routing-discussion/gcz2o_t7DIeSoL_BLU0Xr0waX2k>
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: Thu, 11 Jan 2018 02:50:03 -0000

--94eb2c1aec781d3eee056277343f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hey Russ, thanks for chimin' in, inlined below

On Wed, Jan 10, 2018 at 5:22 PM, <7riw77@gmail.com> wrote:

>
> >       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
>
> I would tend to say "spine and leaf" here, rather than Clod -- Clos is on=
e
> instance of a spine and leaf, but there are others.
>

Hmm, so it's kind of a broader stroke than that. Based on stubborn demand
;-) we have E-W link support @ each level  (but just for failure healing
purposes since otherwise blocking on fabric becomes hard to predict) and
full leaf-2-leaf routing (and smart people start to observe that this can
be used to do e.g. fully meshed leaf levels in a PoD  ;-)  RIFT _could_ be
extended conceptually to support links 'bypassing' levels up, there's a
section on that in the draft.  I consider it not worth bothering since you
either pay by bow-tie routing which is highly undesirable or you start to
distribute far more topology information to route optimally which will
impact many other requirements negatively.  But in a sense, as long there's
a compass rose involved RIFT could be conceptually made to work ;-) There's
enough more work I have thought through but that would blow up the
framework of email.

So, the topology right now is something like "ordered lattice with backup
horizontal links" if you want but I don't know an easy term for it. In real
terms FAT tree or CLOS variations right now.


>
> >       - minimize the amount of routing state held at each topology leve=
l,
>
> It is probably useful to indicate both topology and reachability state
> here, as they are two different things.
>

yes, that is a correct observation. Both are minimized but link failures
must lead to auto deaggregation which in RIFT does the minimum reachability
info necessary to prevent black-holing but in a sense, yes,  it is more
information albeit amount of "link topology info" doesn't change. Unless we
consider prefixes as being part of topology,  I don't think there's an
agreement on that.


>
> >       - allow traffic steering and re-routing policies,
>
> This might be a little underspecified ... I think this should probably
> include "using metrics and policy carried within the RIFT control plane."
> You can always hijack a path using PCEP or something else, so the
> requirement, as stated, just feels a little "weak."
>

first, to be honest, traffic engineering on the fabrics is a bit of a red
herring.  PGPs will let you go wild from north and south ;-) to steer your
traffic around but yes, they need more thinking and push from real
applications. And a protocol's policy is always just acting on protocol
info (unless you do time of day thingies or tag redistribution or something
;-) so I don't know what your comment is aiming at precisely.


>
> >       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.
>
> "very light" might be better as "minimal?" It would be nice to have
> something with a more definite meaning here, but I=E2=80=99m not certain =
what.
>

OK, so the ZTP has been done and is in last review of the authors. In fact
it was supposed to be published Monday, it will be probably Friday. If you
read it carefully then you'll realize that RIFT can do absolute minimal
config but if you mis-cable your topology you may end in ugly situations so
we allow optionally a bit more than minimal, what you could call "very
light" really. And you can mix ZTP nodes with normal modes, that all works
BTW.  And RIFT ZTP works actually for whole fabric, not only leafs. We can
chat more once the draft is out and you looked @ the diffs.


>
> >       The protocol must support IPv6 and should also support IPv4.
>
> In terms of carrying reachability for, or in terms of running on top of?
> Two different things.
>
>
>
Well, RIFT doesn't need ANY addressing really, it just carries "prefixes"
around and uses own node IDs and link IDs for everything to allow fabrics
without any particular address provisioning. Now, running on UDP forces
_some_ kind of addresses but if you look @ the spec it just says "just send
back to the same thing you got your LIE unicast on". Well, plus a port ;-)
which means we imply something like v4 local/v6 local or something (once we
get UDP over MPLS [yeah, the other way round ;-)]) working natively ...
And yes, you probably want a loopback to get to the node as well ...

On the other hand we don't want to do AF VPN_UCAST or some such thing so I
struggle how we could formulate that part of the charter better beside
saying "must do v4/v6 reachability to the leafs and optionally fabric
nodes" ...

So give me next rev of your comments based on this input, pls ...

--- tony

--94eb2c1aec781d3eee056277343f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hey Russ, thanks for chimin&#39; in, inlined below <br><di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Jan 10,=
 2018 at 5:22 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:7riw77@gmail.com=
" target=3D"_blank">7riw77@gmail.com</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-"><br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0The Routing in Fat Trees (RIFT) protocol add=
resses the demands of<br>
&gt; routing in Clos and Fat-Tree networks via a mixture of both link-state=
 and<br>
<br>
</span>I would tend to say &quot;spine and leaf&quot; here, rather than Clo=
d -- Clos is one instance of a spine and leaf, but there are others.<br></b=
lockquote><div><br></div><div>Hmm, so it&#39;s kind of a broader stroke tha=
n that. Based on stubborn demand ;-) we have E-W link support @ each level=
=C2=A0 (but just for failure healing purposes since otherwise blocking on f=
abric becomes hard to predict) and full leaf-2-leaf routing (and smart peop=
le start to observe that this can be used to do e.g. fully meshed leaf leve=
ls in a PoD=C2=A0 ;-)=C2=A0 RIFT _could_ be extended conceptually to suppor=
t links &#39;bypassing&#39; levels up, there&#39;s a section on that in the=
 draft.=C2=A0 I consider it not worth bothering since you either pay by bow=
-tie routing which is highly undesirable or you start to distribute far mor=
e topology information to route optimally which will impact many other requ=
irements negatively.=C2=A0 But in a sense, as long there&#39;s a compass ro=
se involved RIFT could be conceptually made to work ;-) There&#39;s enough =
more work I have thought through but that would blow up the framework of em=
ail. <br></div><div><br></div><div>So, the topology right now is something =
like &quot;ordered lattice with backup horizontal links&quot; if you want b=
ut I don&#39;t know an easy term for it. In real terms FAT tree or CLOS var=
iations right now. <br></div><div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
<span class=3D"gmail-"><br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- minimize the amount of routing state held =
at each topology level,<br>
<br>
</span>It is probably useful to indicate both topology and reachability sta=
te here, as they are two different things.<br></blockquote><div><br></div><=
div>yes, that is a correct observation. Both are minimized but link failure=
s must lead to auto deaggregation which in RIFT does the minimum reachabili=
ty info necessary to prevent black-holing but in a sense, yes,=C2=A0 it is =
more information albeit amount of &quot;link topology info&quot; doesn&#39;=
t change. Unless we consider prefixes as being part of topology,=C2=A0 I do=
n&#39;t think there&#39;s an agreement on that. <br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=3D"gmail-"><br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0- allow traffic steering and re-routing poli=
cies,<br>
<br>
</span>This might be a little underspecified ... I think this should probab=
ly include &quot;using metrics and policy carried within the RIFT control p=
lane.&quot; You can always hijack a path using PCEP or something else, so t=
he requirement, as stated, just feels a little &quot;weak.&quot;<br></block=
quote><div><br></div><div>first, to be honest, traffic engineering on the f=
abrics is a bit of a red herring.=C2=A0 PGPs will let you go wild from nort=
h and south ;-) to steer your traffic around but yes, they need more thinki=
ng and push from real applications. And a protocol&#39;s policy is always j=
ust acting on protocol info (unless you do time of day thingies or tag redi=
stribution or something ;-) so I don&#39;t know what your comment is aiming=
 at precisely. <br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
<span class=3D"gmail-"><br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0It is important that nodes participating in =
the protocol should need only<br>
&gt; very light configuration and should be able to join a network as leaf =
nodes<br>
&gt; simply by connecting to the network using default configuration.<br>
<br>
</span>&quot;very light&quot; might be better as &quot;minimal?&quot; It wo=
uld be nice to have something with a more definite meaning here, but I=E2=
=80=99m not certain what.<br></blockquote><div><br></div><div>OK, so the ZT=
P has been done and is in last review of the authors. In fact it was suppos=
ed to be published Monday, it will be probably Friday. If you read it caref=
ully then you&#39;ll realize that RIFT can do absolute minimal config but i=
f you mis-cable your topology you may end in ugly situations so we allow op=
tionally a bit more than minimal, what you could call &quot;very light&quot=
; really. And you can mix ZTP nodes with normal modes, that all works BTW.=
=C2=A0 And RIFT ZTP works actually for whole fabric, not only leafs. We can=
 chat more once the draft is out and you looked @ the diffs. <br></div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class=3D"gmail-"><br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0The protocol must support IPv6 and should al=
so support IPv4.<br>
<br>
</span>In terms of carrying reachability for, or in terms of running on top=
 of? Two different things.<br>
<br><br></blockquote><div><br></div><div>Well, RIFT doesn&#39;t need ANY ad=
dressing really, it just carries &quot;prefixes&quot; around and uses own n=
ode IDs and link IDs for everything to allow fabrics without any particular=
 address provisioning. Now, running on UDP forces _some_ kind of addresses =
but if you look @ the spec it just says &quot;just send back to the same th=
ing you got your LIE unicast on&quot;. Well, plus a port ;-) which means we=
 imply something like v4 local/v6 local or something (once we get UDP over =
MPLS [yeah, the other way round ;-)]) working natively ...=C2=A0 And yes, y=
ou probably want a loopback to get to the node as well ... <br></div><div><=
br></div><div>On the other hand we don&#39;t want to do AF VPN_UCAST or som=
e such thing so I struggle how we could formulate that part of the charter =
better beside saying &quot;must do v4/v6 reachability to the leafs and opti=
onally fabric nodes&quot; ...=C2=A0</div><div><br></div><div>So give me nex=
t rev of your comments based on this input, pls ... <br></div><div><br></di=
v><div>--- tony <br></div></div><br></div></div></div>

--94eb2c1aec781d3eee056277343f--

