Re: [Rift] I-D Action: draft-ietf-rift-applicability-01.txt

Melchior Aelmans <melchior@aelmans.eu> Thu, 15 October 2020 20:08 UTC

Return-Path: <melchior@aelmans.eu>
X-Original-To: rift@ietfa.amsl.com
Delivered-To: rift@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5543A0FF0 for <rift@ietfa.amsl.com>; Thu, 15 Oct 2020 13:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aelmans-eu.20150623.gappssmtp.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 BUz9KQ53ofYW for <rift@ietfa.amsl.com>; Thu, 15 Oct 2020 13:08:14 -0700 (PDT)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 91B5B3A0FDE for <rift@ietf.org>; Thu, 15 Oct 2020 13:08:14 -0700 (PDT)
Received: by mail-pg1-x52e.google.com with SMTP id o7so2482536pgv.6 for <rift@ietf.org>; Thu, 15 Oct 2020 13:08:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aelmans-eu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CF9gf45fC+a3qAh3LSb4NKgwcJ+J9CLKUpgPdxrdlfo=; b=dHdKZyp+uiPLGiXC1WRk/N9exjQlWPPbwrzdYOhVtAL7dhD85r4vTwg85TwQxyqbHG uJ0lMR8Le1Siamm7oLW07AG8nhW1b2xhEDREDJXPAFHPXfl+LLsMWn/9kyyJrVoYW6WO uG4ED7gf14aji4KwDCYJ2zCV5QDNIT4lH28LCROzDNIbCyObrbAfnWf5ZSXNaKE7Px8D tKP1A9H77TSKNm0B76PxwyF1kJovq3sZxwndlkTkrBCH4WBZ6RN3+MNs7uBtag1k+r6h C10K3sputBbytuMCt6TSrSOmMpZ26gBJDH4qh2DxqcVh6XwBvoIpg6URNZuP5MjmKMqc zzQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CF9gf45fC+a3qAh3LSb4NKgwcJ+J9CLKUpgPdxrdlfo=; b=poTTtbkC/9eiluC0eaNsvwQi29bbT8ldPdb7m/Ka0tP6/jXqtatIQOLOYZ8EtV+d0d omDJ/XGP9ZnnYzbDjfeLxZVU7TrSYaS6XMMT4EIckVhYKUr0HNJtsKCAsFwtKZ05t2zf iZLSwUesSqTcpQG2G/Mrz3zBE5TLLXUc+x7Zr/oy0BMOXRDZKSNOa9wiTK0TQmw9W57l e5y/A1vGsQFmGnAR8ZVUzmhVWH1rAW9p/R1ERpS4trnajtjhx8x0Wbi03pbxvt/w5EZy p9bWs4R3iXUIkoKQCcpBHmrT86x1YKZPLAkhQvpuNNRoMsmAcXvVQQ+DnDwYCKgPqtUV 87jg==
X-Gm-Message-State: AOAM532wxojK5GirgM1SiTwL3IQXaKTdqV2onzqz7HOzCPFpxtJzWHZi 3HZKf2fYoMt0MMDamqjV5hAZCNIc3u4cxJgzLHTaiG7yqAD/CznKtDk=
X-Google-Smtp-Source: ABdhPJxPpkyl8pIWt2aee+q3OoUAVpzVDK98gkhlNybRMhAKtmxXmmvqnEiIQcNpoTpdzZvMoNEPvzdRiDYX1nX5/wU=
X-Received: by 2002:a62:cd85:0:b029:152:6881:5e2c with SMTP id o127-20020a62cd850000b029015268815e2cmr323875pfg.36.1602792493795; Thu, 15 Oct 2020 13:08:13 -0700 (PDT)
MIME-Version: 1.0
References: <CALxNLBiMdJMBk9+VTTsLy7x7OnBA9iCYahTaux5STYwp366Pdg@mail.gmail.com> <202010131658021600942@zte.com.cn>
In-Reply-To: <202010131658021600942@zte.com.cn>
From: Melchior Aelmans <melchior@aelmans.eu>
Date: Thu, 15 Oct 2020 22:08:02 +0200
Message-ID: <CALxNLBgxR76ofsRNL_xcsHXVRtTDAG81Dw0m_nvxQApuHRmrLw@mail.gmail.com>
To: wei.yuehua@zte.com.cn
Cc: draft-wei-rift-applicability@ietf.org, rift@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003de32d05b1bb35c9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/_nkdg2dMvKHXlsO0VKEzwH8iFC0>
Subject: Re: [Rift] I-D Action: draft-ietf-rift-applicability-01.txt
X-BeenThere: rift@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of Routing in Fat Trees <rift.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rift>, <mailto:rift-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rift/>
List-Post: <mailto:rift@ietf.org>
List-Help: <mailto:rift-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rift>, <mailto:rift-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 20:08:17 -0000

Thanks for taking into account my suggestions.

I'm rereading the draft again and section 4.10 "Dual Homing Servers"
doesn't really make it clear to me what the benefits are for dual homing
servers to a RIFT fabric.

First, in this specific section you start using Spine and ToR to refer to
this level where in other places in the draft you only refer to this as
Spine. For easier reading I would suggest picking Spine.

Second, although I agree that the loss of a Spine results in more specifics
would they in this example hit the server? From the server perspective the
default still points to the Leaf. The Leaf would indeed need to have more
specifics in order to avoid the blakhole at Spine level but I'm not sure
they are propagated to the servers.

Also, it might be interesting to emphasize little more on the advantages of
multi-homing servers to a RIFT fabric especially when they partake in RIFT;
the avoidance of L2 in between Leaf and server, easier IP mobility, etc.

Looking forward to hearing what you think.
If you are interested I'm willing to (re)write something for this section.

Cheers,
Melchior

On Tue, Oct 13, 2020 at 10:58 AM <wei.yuehua@zte.com.cn> wrote:

> Hi
>
> Will reflect the correction to version -03.
>
> Thank you so much!
>
>
>
>
> Best Regards,
>
> Yuehua Wei
>
> ZTE Corporation
>
> 南京市软件大道50号/No.50, Software Avenue, Nanjing, 210012, P. R. China
>
> M: +86 13851460269 E: wei.yuehua@zte.com.cn
>
> <wei.yuehua@zte.com.cn>
>
>
>
> 原始邮件
> *发件人:*MelchiorAelmans
> *收件人:*draft-wei-rift-applicability@ietf.org;
> *抄送人:*rift@ietf.org;
> *日 期 :*2020年10月12日 21:38
> *主 题 :**Re: [Rift] I-D Action: draft-ietf-rift-applicability-01.txt*
> _______________________________________________
> RIFT mailing list
> RIFT@ietf.org
> https://www.ietf.org/mailman/listinfo/rift
>
> Hi,
>
> I don't believe the below was corrected in the -02 version as it still
> reads "more a specific" instead of "a more specific".
>
> Cheers,
> Melchior
>
> On Sun, May 3, 2020 at 9:37 PM Melchior Aelmans <melchior@aelmans.eu>
> wrote:
>
>> Dear authors,
>>
>> I've spotted a small typo in section 4.6. Positive vs. Negative
>> Disaggregation:
>>
>> Disaggregation is the procedure whereby [RIFT <https://tools.ietf.org/html/draft-ietf-rift-applicability-01#ref-RIFT>] advertises more a specific route Southwards as an exception to the aggregated fabric-default North.
>>
>>
>> I think you are trying to say "advertises a more sepcific".
>>
>> Cheers,
>> Melchior
>>
>> On Fri, Apr 3, 2020 at 10:54 AM <internet-drafts@ietf.org> wrote:
>>
>>>
>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>> directories.
>>> This draft is a work item of the Routing In Fat Trees WG of the IETF.
>>>
>>>         Title           : RIFT Applicability
>>>         Authors         : Yuehua Wei
>>>                           Zheng Zhang
>>>                           Dmitry Afanasiev
>>>                           Tom Verhaeg
>>>                           Jaroslaw Kowalczyk
>>>                           Pascal Thubert
>>>         Filename        : draft-ietf-rift-applicability-01.txt
>>>         Pages           : 29
>>>         Date            : 2020-04-03
>>>
>>> Abstract:
>>>    This document discusses the properties, applicability and operational
>>>    considerations of RIFT in different network scenarios.  It intends to
>>>    provide a rough guide how RIFT can be deployed to simplify routing
>>>    operations in Clos topologies and their variations.
>>>
>>>
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-rift-applicability/
>>>
>>> There are also htmlized versions available at:
>>> https://tools.ietf.org/html/draft-ietf-rift-applicability-01
>>> https://datatracker.ietf.org/doc/html/draft-ietf-rift-applicability-01
>>>
>>> A diff from the previous version is available at:
>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-rift-applicability-01
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>
>>>
>>> _______________________________________________
>>> RIFT mailing list
>>> RIFT@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rift
>>>
>>
>