Re: [Idr] Fw: Re: New Version Notification for draft-xie-idr-mpbgp-extention-4map6-00.txt

Jeffrey Haas <jhaas@pfrc.org> Mon, 06 November 2023 10:03 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADF3C15108F; Mon, 6 Nov 2023 02:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6as8YRLvolMa; Mon, 6 Nov 2023 02:03:54 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 497BEC14CF1C; Mon, 6 Nov 2023 02:03:54 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id DECDC1E2F2; Mon, 6 Nov 2023 05:03:53 -0500 (EST)
Date: Mon, 06 Nov 2023 05:03:53 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Cc: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>, Chongfeng Xie <xiechf@chinatelecom.cn>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, idr <idr@ietf.org>, xing <xing@cernet.edu.cn>
Message-ID: <20231106100353.GC3251@pfrc.org>
References: <2023012517403527261033@chinatelecom.cn> <CAOj+MMGyr8uowrY2oJKTncKJ25Ey0Y7otq2iqRzutd8u7Dk=ow@mail.gmail.com> <2023012708023871817347@chinatelecom.cn> <CAOj+MMGXHWf=gLOMJ1mRF_xaPapCC6ZhCzz4NEwDH9fMVQhQMg@mail.gmail.com> <2023012808483046168910@chinatelecom.cn> <CAOj+MMGzkDT4x6RL3_3n=fVGTKSZ_scRFFD7EYRd3dOJW2p9Tg@mail.gmail.com> <4573a0f3d9f9445db81ba02d6e0e5c39@huawei.com> <CAOj+MMFf4HtLMAgUHLd72jBFQCzYcw8-hUHUtORFzxU+9RmAxA@mail.gmail.com> <20231106093115.GK27820@pfrc.org> <CAOj+MMHVY4_a49-qoPSwM7DNNfUo=8TrwYuVqT=50t68TnAyXw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAOj+MMHVY4_a49-qoPSwM7DNNfUo=8TrwYuVqT=50t68TnAyXw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/8Bpp_GzafKbr8wXYak9RVHCugIQ>
Subject: Re: [Idr] Fw: Re: New Version Notification for draft-xie-idr-mpbgp-extention-4map6-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2023 10:03:55 -0000

Robert,

On Mon, Nov 06, 2023 at 10:39:45AM +0100, Robert Raszuk wrote:
> If edge nodes do not carry IPv4 routes don't we have number of solutions
> already as well like pseudowires or EPE which could provide a pipe model
> through the transit network not doing any lookup ?

The consideration I'm raising is not the "edge" nodes, it's that carrying
IPv4 routes with tunneling information would require all intervening
networks to also support that family and tunneling.

> Let's note that that not doing IPv4 lookup on the ingress/egress here is
> very deployment limiting too especially if number of sites you are
> interconnecting grows.

I don't believe the procedures here are requsting that we avoid IPv4 lookup.
Rather, it's the lookup is done utilizing the mapping database constructed
using this feature.  However, that's my interpretation of the feature in the
draft.

The procedures for populating the IPv4 FIB, including route selection
considerations for loop detection, are underspecified in my opinion. These
are in need of further discussion by the authors and the working group.

-- Jeff