Re: [Rift] Ipv4 and ipv6 cooperating in rift

Alvaro Retana <aretana.ietf@gmail.com> Thu, 11 July 2019 15:15 UTC

Return-Path: <aretana.ietf@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 235181200E6 for <rift@ietfa.amsl.com>; Thu, 11 Jul 2019 08:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level:
X-Spam-Status: No, score=-0.701 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, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 AFj3Bk5AlHNR for <rift@ietfa.amsl.com>; Thu, 11 Jul 2019 08:15:14 -0700 (PDT)
Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (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 6DBC1120135 for <rift@ietf.org>; Thu, 11 Jul 2019 08:15:14 -0700 (PDT)
Received: by mail-ed1-x531.google.com with SMTP id i11so6192312edq.0 for <rift@ietf.org>; Thu, 11 Jul 2019 08:15:14 -0700 (PDT)
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=n1mZPFfeAWw4KnCh9+/qYuTmT3p8a7HU5BlTPwmSH4w=; b=EaY6xUyii6dKUH/+RZYMBrVTs1tCXNXRDypWoWs1LEeCVq4PlIIle912NemHRrXkBp mKTfveoxVvPk8NjTJKnlemaH3Q3XA66j3MSdmFIjieZI8jxV+9hfXCLLTkF8FI/kiWfV y3lAzE4yBv1SSn3Xh1mOoOPDHWY7Os9ewAH1iISR3AYm4mkTfdi1b6zKiB3wYct2vPVF uei0Wqi+XV5liK1AkFktFNoqKwEVfM5/6UstxMc7rXQRM6xdBFShX6k7+yU1hgMnDh2z XTc75Y/HGuSfvB+4ucxqM+tis85egY2pRC/Hh9CUvRP2LPbT7ALzHFcvVF5YcR90jvhI cUuw==
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=n1mZPFfeAWw4KnCh9+/qYuTmT3p8a7HU5BlTPwmSH4w=; b=h0p0m38uttfOjr81QIv0CiTpEMI2mBP/mdwrGwHCpR0W/Ls73naSqPh1LbqJChcfrX 12aFFhrrEcC3ZapK5b6CJ9RkmSSRni5RC/hJX3fPwomTpUEZiY3XmLCI3+PcsuaNjYXZ uc3B2Fd1hfEeEKqUN3no7Y49EkTGoVCSXxbe5gQo2xNYE7sdaCyTI+EXfjjYBHPMd9cH 5INazt1XNC55LO+qb2Uta4Nq5xZFvpt26eg41h/9ho2CMkycQgOzm4Xz8SOqbRVFi4nn Zg6gJagU76yc4pucGhIXeTY9LUVVhWQLtIl8/eYa0UYgEwtirmGgAowxYFa5WEq6bL42 twbw==
X-Gm-Message-State: APjAAAWYOMQ5G6GtuXVoG7GJcxZuQF8qOk5Ph2XRRQE4I3wh6dNJcgaE wrIX1cShOzrajz0YC9mZ/7U4TtngM7z7kYeedwU=
X-Google-Smtp-Source: APXvYqyTH6tVJRXuY1siyqkZwEnt5SiF7QEMDJI3EPJQwS/TQtfYnQHEbuf/XM59zHSqSPFjEyZGX6pbzOHPn8aD/O0=
X-Received: by 2002:aa7:c313:: with SMTP id l19mr4116607edq.258.1562858113053; Thu, 11 Jul 2019 08:15:13 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 11 Jul 2019 08:15:11 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <MWHPR05MB3279B78E6D9AECB771D2497FACF00@MWHPR05MB3279.namprd05.prod.outlook.com>
References: <201907101656125835263@zte.com.cn> <MWHPR05MB3279B78E6D9AECB771D2497FACF00@MWHPR05MB3279.namprd05.prod.outlook.com>
MIME-Version: 1.0
Date: Thu, 11 Jul 2019 08:15:11 -0700
Message-ID: <CAMMESsyLRtyTaMTFqzuizuNgxfRm6iuFqfun-711ayq5H4Cb8A@mail.gmail.com>
To: Antoni Przygienda <prz=40juniper.net@dmarc.ietf.org>, "xu.benchong@zte.com.cn" <xu.benchong@zte.com.cn>
Cc: "rift@ietf.org" <rift@ietf.org>, "EXT-zhang.zheng@zte.com.cn" <zhang.zheng@zte.com.cn>, "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
Content-Type: multipart/alternative; boundary="000000000000a9b796058d694270"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rift/DlFg6L9TcsPyUtA1Ki82lLGaekU>
Subject: Re: [Rift] Ipv4 and ipv6 cooperating in rift
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, 11 Jul 2019 15:15:16 -0000

On July 10, 2019 at 11:05:40 AM, Antoni Przygienda (
prz=40juniper.net@dmarc.ietf.org) wrote:

Hi!

I might be jumping in without proper context, but this text caught my
attention...

b) If you want the "laziest" possible implementation then in fact yes, you
can fall back on

"

All RIFT routers MUST support IPv4 forwarding and MAY support IPv6
   forwarding.  A three way adjacency over IPv6 addresses implies
   support for IPv4 forwarding.

"

…because the WG Charter says that "The protocol must support IPv6 and
should also support IPv4.”   So the text above contradicts the Charter.

Alvaro.