Re: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6

Ketan Talaulikar <ketant.ietf@gmail.com> Mon, 12 February 2024 14:27 UTC

Return-Path: <ketant.ietf@gmail.com>
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 2DF69C151081; Mon, 12 Feb 2024 06:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpN9pPbv49qW; Mon, 12 Feb 2024 06:27:37 -0800 (PST)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F3D4C14F600; Mon, 12 Feb 2024 06:27:37 -0800 (PST)
Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-a28a6cef709so436705566b.1; Mon, 12 Feb 2024 06:27:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707748055; x=1708352855; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=hvn6C2+sR3Ena5vgq6sS9G03GRpQq5gNLjVpQNV/BA4=; b=CR6wCJaJlTIHw50dl1cyI1DeawjhYwbZaP2d551htDmKZDGWJWxHFqXOxYOUwIrQ7c Xj+yGp6vYAiND8j24i/1sB+LGptO5/1CM//K1wbQ8tIDyGDJ7laX7O7jEPg1aMyHRHQ7 Vu0P4jeRi4H49tysjBTZbpoO0eQDTIz3UwMWoidWBWk24POwXezVUjQotJ580xI4I7Gj p50YIoxeGEJt3bsM1NkPlNA254elE53iDd15TenSIo3GXhPEuUjX3zW+uQE9fenVngcG X1nokCon0KtjTpNuC6nRunYDS0gA58L+bhdrpLtqiUgqIPUc0wRNPAOgbPieVzIahRB+ N4aw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707748055; x=1708352855; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=hvn6C2+sR3Ena5vgq6sS9G03GRpQq5gNLjVpQNV/BA4=; b=MnJBaLAiv5mvuBbWgxHMwsc/+o+qy2rRr+pACVw6ASwHd0TG6MjEiEoytq7AqRs2XE TYcVAudbqIe90hqggF3JmiiXSggBFBAPUiuhpTOEo1q8TODpnzP8sHy/oV0TxO7yZe/g 3SPQugDqKn6aBTolcnTp6n7PD02dpiJQ6gLW3GTjXzoaBgm4RwOjFobJoyOYttZKNn0W Da2CUgFXHMoAtA4EmLzRS+b+lHLdp3uP40oHk1DdXsZiw8N5zeIcGw48k73ximbOZC8t SHRT1c9lRBPgMy93ArAbb2PZA1tPd1e72w4u8J2JypO/Lk+nN2L43NnsaqhWiqiZlTZO NnjQ==
X-Forwarded-Encrypted: i=1; AJvYcCUtTc+BL65efvPit2Yrvbgr9hydhx6/JvvbUw0gVvEJFK/4G+ix6EXXkJAxZvkcDsR6sNKuVihfglsGBda0WaU8NcF7aahGzyHR3h3XUMCvL7HFgtR1+T3EHzUpSBTnKWHXrwk8bp14YWWe
X-Gm-Message-State: AOJu0YyEHtHthgGV9ry12MzykSFNICtH1h3HqjUkcZh3aHJRfEns5qbE UCE3swulDXFWr5/zkmwlbtuSYr9xhCrsATZ8S4Xws/GgufYM+rRcqI5dp5325LxyuXVp7MhcHTj 8kxzRlgyZ9w4uu469t2nPQ3E3pxY=
X-Google-Smtp-Source: AGHT+IH4K91xcNjEj+lRP+oycCRs858bAPjTxG/QIMD24qcAmgomSb13h+CYUeU3/Sx0bcqSH/VXwY0l3wTsUnp1vQI=
X-Received: by 2002:a17:906:34cf:b0:a3c:59c2:305a with SMTP id h15-20020a17090634cf00b00a3c59c2305amr3125435ejb.5.1707748055221; Mon, 12 Feb 2024 06:27:35 -0800 (PST)
MIME-Version: 1.0
References: <BYAPR08MB487294F5C1EE87A8184EDC8BB3AEA@BYAPR08MB4872.namprd08.prod.outlook.com> <tencent_CBB12F958C85FDF962D76180EB1C51662408@qq.com> <20240122223242.GA29681@pfrc.org> <tencent_446B00493916CCB662EB2AC90A17F2AFAF09@qq.com> <DB175FC2-BD0A-424A-B8E6-31345BEAC8D6@pfrc.org> <tencent_FF24FFF11A1B308B03C3EC27F6B8B2B09005@qq.com> <F64BDA83-5A46-4FEA-AD6F-16CDDD817EAA@pfrc.org> <tencent_6F855FF963D740807C1C166681B1FD950908@qq.com>
In-Reply-To: <tencent_6F855FF963D740807C1C166681B1FD950908@qq.com>
From: Ketan Talaulikar <ketant.ietf@gmail.com>
Date: Mon, 12 Feb 2024 19:57:18 +0530
Message-ID: <CAH6gdPzMfZ8NFXcGiMkFJu_=eA9jAW+oj6ir4sbaVvyAzbzzEQ@mail.gmail.com>
To: Chongfeng Xie <chongfeng.xie@foxmail.com>, draft-xie-idr-mpbgp-extension-4map6 <draft-xie-idr-mpbgp-extension-4map6@ietf.org>
Cc: jhaas <jhaas@pfrc.org>, Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000328951061130144b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/mfUy1ZlWPZ6u9AJxjBW1OvCZFBY>
Subject: Re: [Idr] Please discuss the use cases for draft-xie-idr-mpbgp-extention-4map6
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, 12 Feb 2024 14:27:41 -0000

Hi Chongfeng/Authors,

Thanks for your updates to the document.

I am still struggling to find the answer to the question on why it is
necessary to perform mapping from IPv4 to IPv6 and then back to IPv4 when
providing IPv4 connectivity service over an IPv6 core? Why is it not
sufficient to simply encapsulate the IPv4 payload into any encapsulation
(e.g., IPv4-in-IPv6, SRv6, MPLS, GRE, etc.) using RFC8950 encoding for the
IPv4 unicast/VPN SAFI. These solutions are documented
in draft-mishra-idr-v4-islands-v6-core-4pe

Perhaps I am missing something and it would help me understand the need for
such mapping by service provider PE routers.

Thanks,
Ketan


On Thu, Feb 8, 2024 at 5:14 AM Chongfeng Xie <chongfeng.xie@foxmail.com>
wrote:

>
>
> Hi Jeff,
>
> We have submitted a new version of draft-xie-idr-mpbgp-extention-4map6.
> Based on your suggestions, the contents of new attribute is placed in a new
> TLV in the tunnel encapsulation attribute of RFC9012, and the format of the
> NLRI is revised as well. In addition, the section of operation has been
> changed accordingly.
>
>
>         Name:     draft-xie-idr-mpbgp-extension-4map6
>         Revision: 09
>         Title:    MP-BGP Extension and the Procedures for IPv4/IPv6
> Mapping Advertisement
>         Date:     2024-02-09
>         Group:    idr
>         Pages:    16
>         URL:
> https://www.ietf.org/archive/id/draft-xie-idr-mpbgp-extension-4map6-09.txt
>         Status:
> https://datatracker.ietf.org/doc/draft-xie-idr-mpbgp-extension-4map6/
>         HTMLized:
> https://datatracker.ietf.org/doc/html/draft-xie-idr-mpbgp-extension-4map6
>         Diff:
> https://author-tools.ietf.org/iddiff?url2=draft-xie-idr-mpbgp-extension-4map6-09
>
> We express sincere thanks to you for reviewing the draft as WG chair and
> providing a couple of important suggestions.  We also thank idr WG for the
> comments and suggestions received so far.
>
> If you have any new comments or suggestions, please feel free to let me
> know. Thanks!
>
> Best regards
> Chongfeng
>
>
> *From:* 【外部账号】Jeffrey Haas <jhaas@pfrc.org>
> *Date:* 2024-02-05 00:02
> *To:* Chongfeng Xie <chongfeng.xie@foxmail.com>
> *CC:* Sue Hares <shares@ndzh.com>; idr <idr@ietf.org>;
> draft-xie-idr-mpbgp-extension-4map6
> <draft-xie-idr-mpbgp-extension-4map6@ietf.org>
> *Subject:* Re: [Idr] Please discuss the use cases for
> draft-xie-idr-mpbgp-extention-4map6
> Chongfeng,
>
>
> On Jan 29, 2024, at 10:38 AM, Chongfeng Xie <chongfeng.xie@foxmail.com>
> wrote:
> Based on your comment and suggestions, we have made the following
> revisions and submitted a new version,
>
>
>
> [...]
>
> If you have any further comments, please feel free to let me know.
>
>
> Your changes significantly address my operational concerns.  Thank you.
>
> -- Jeff
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>