Re: [Rift] IPv4 vs IPv6

Tony Przygienda <tonysietf@gmail.com> Fri, 19 July 2019 02:46 UTC

Return-Path: <tonysietf@gmail.com>
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 9BE001200B4 for <rift@ietfa.amsl.com>; Thu, 18 Jul 2019 19:46:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 U6rz6qlddIL9 for <rift@ietfa.amsl.com>; Thu, 18 Jul 2019 19:45:59 -0700 (PDT)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 9DD8E12014F for <rift@ietf.org>; Thu, 18 Jul 2019 19:45:59 -0700 (PDT)
Received: by mail-ed1-x534.google.com with SMTP id m10so33089779edv.6 for <rift@ietf.org>; Thu, 18 Jul 2019 19:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7KGFKhMQMGRLo5BOkOtAWF5lL05dC6WWVQTjcWxHkoA=; b=tB2np++wxJ+FrERqJC+vhjhT/iTvqHpMHN17Tz+3tocrQmz+8K38cV+gqJdimpVY2w B0nAV9TSub86GGUQWMv7InN+lY3mNgDcEN0D048XjZaEOBUIkzfH1T82dcUoUgH9fCis nJfhnA6e1knrcp7dBHbQkpQsZcoAnlGc4it4ghAYeJlID+h1yrt7hGz01XwZ03cwk5sP SBiolFhBBYoedcSIV8oPMvcEH3cgmpeCiNbyNgLcAF7EWH8/SakHiUnmH7zHR/n3XlNS wPC/jqjo1/XmUQB030aJC8Ucv2XncIEIq2Wp0Gxy+SrUwcZtPQMWSr8hETVuyk2OdH/g vQlg==
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=7KGFKhMQMGRLo5BOkOtAWF5lL05dC6WWVQTjcWxHkoA=; b=cEU9w2BQSIOXcSO0/8SU9bZ/7GepEW6K8kdK+pfORn+DMlOwJgx/pFG/KkT5NibUUt N5t2rHFaLXBo2p9B5JW83bIXvYLGw738O5bwnW2dyLy3lAFb6j+Mjjrs2GyPqZhAWLqV e1Bip8p1KinhMI6ergvcQyo4GN+z5Uj9i6dSt8OBB3esd5dnoblU1Yh2pDQx/9mro0L7 yQz5FuAQglRA7CNuVDR/WWikB0RZHEunDAj6GpLCoQnznXoL4v/a0c6ODW2iHvE7iHx2 F/uUrZFcZxmMFvL7YQ27DbSGqoNIs9u78saR84AZppV5uAjPR2TqKKMDUVxqJIKuMNpN TvuQ==
X-Gm-Message-State: APjAAAUcnQ0EzW4UDDnFwgsq8y7eiIcMbemViu+4/dSaLpPrg5Q/s58q RmQRxU4V/atweK3PiH49RWuzRhqiiK3Oz2L1Lq8=
X-Google-Smtp-Source: APXvYqwpunRUjU2retzABZDSxOmf5ZHdEK6SW8Ocju8GLZpLuQ7rJ39P+0H9zPYp6Vlk9Atu93WWyItfRbyCX+iddIk=
X-Received: by 2002:a17:906:1e85:: with SMTP id e5mr38397336ejj.200.1563504358265; Thu, 18 Jul 2019 19:45:58 -0700 (PDT)
MIME-Version: 1.0
References: <alpine.DEB.2.20.1907180636330.19225@uplift.swm.pp.se> <CA+wi2hP6K3Or7ynOUzKovxkx8ZtvnTUdKVDvjRcB8=4yjFD6aQ@mail.gmail.com> <alpine.DEB.2.20.1907182001590.19225@uplift.swm.pp.se> <CA+wi2hOkZH0O44yTikfabmDpJSqZN+_qmZnDBA1gsyFoVhzYuQ@mail.gmail.com> <CAMMESsznSPyS7zEKQNE2Ey8uZh-64P2MFE+fJt1054oaScyJtw@mail.gmail.com>
In-Reply-To: <CAMMESsznSPyS7zEKQNE2Ey8uZh-64P2MFE+fJt1054oaScyJtw@mail.gmail.com>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Thu, 18 Jul 2019 22:45:22 -0400
Message-ID: <CA+wi2hPSa7HAijtNAd4niWEZ0muGikkvp=8SDFUiHRbYBL2WYg@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, rift@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e1171e058dffb934"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/Ie4T88ZMKYlCGgFQY6VZCb1sW9Q>
Subject: Re: [Rift] IPv4 vs IPv6
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: Fri, 19 Jul 2019 02:46:02 -0000

If the consensus is that we should be dropping the sentence completely in
the next versions and not specify any RIFT router requirements, I think
that's perfectly reasonable as well.

--- tony

On Thu, Jul 18, 2019 at 4:39 PM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> On July 18, 2019 at 3:50:34 PM, Tony Przygienda (tonysietf@gmail.com)
> wrote:
>
> [Speaking as a WG member.]
>
> Aha ok, what you say is reasonable. I was steered here originally by the
> fact the even cheapest stuff today
> <http://airmail.calendar/2019-07-18%2012:00:00%20GMT-3> does v4 and if we
> have v6 support on the fabric v4 forwarding over v6 nexthops is possible at
> basically zero config cost and you have a great v4 to v6 migration story.
> but with the angle you propose I see that writing "SHOULD support v4" would
> be better assuming silicon will become v6 only over years and v4 will
> vanish.
>
> We can't write of course "MUST support v6" since that makes the stuff
> undeployable in foreseable future albeit we all wish the world would have
> moved on for last 20 years :-}
>
> Other opinions?
>
> I would go all the way and not make specific support Normative.  Even a
> “SHOULD support IPv4” could raise a lot of questions.
>
> My 2c.
>
> Alvaro.
>
>