IETF Logo Mail Archive

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

Robert Raszuk <robert@raszuk.net> Thu, 19 January 2023 08:56 UTC

Return-Path: <robert@raszuk.net>
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 E860BC14F74E for <idr@ietfa.amsl.com>; Thu, 19 Jan 2023 00:56:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.086
X-Spam-Level:
X-Spam-Status: No, score=-7.086 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, 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, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 8co54QMRtqiJ for <idr@ietfa.amsl.com>; Thu, 19 Jan 2023 00:56:34 -0800 (PST)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com [IPv6:2a00:1450:4864:20::331]) (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 2AB49C1524CD for <idr@ietf.org>; Thu, 19 Jan 2023 00:56:34 -0800 (PST)
Received: by mail-wm1-x331.google.com with SMTP id f19-20020a1c6a13000000b003db0ef4dedcso3049216wmc.4 for <idr@ietf.org>; Thu, 19 Jan 2023 00:56:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6fzqKaue6oMjEUk23OyQRLR3aqPX/QRork4lC8Be8dE=; b=B9txBSH4J0xAJE1KD60BIyOeWM3okP9LHALUtvw1nAP6BzG12XSMoeV/CYVbkNCSo6 dCnIOhddmmaCgLSanVIeaN87QDcwTF11nU9jHI/FmVjlHhe5hymXrRSylRkjQWQvgzkp 8fFIEWdoTXqA5DfdqgHRi1fn9+S9A+veVrNct7pnrsIhLskBdhUvRqX+6TGTutRdzFnC k51JsS2BfTM1Eial+yc2SJcBJvVqy0WPlMw21Swc84hvBddeuQpTDKL8JoPqCqOJj5tL whhRKsRgiM+cO2vsfsH5RPY9SnyDFQSGKNcxTy00hPou54SMxBtYm53agbl4pjY4Eem1 Nm5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=6fzqKaue6oMjEUk23OyQRLR3aqPX/QRork4lC8Be8dE=; b=jsRvIQQiavVM2oAQOf206WXlXMfKdtjCBZtcHAYZyGhiylwXQai/RtY+b7M0RGHcr3 ipcuuXyj5cyPtZD/NcotR0YBuzDitJT+4gcFoUIw8xsK4lMrhutT9jJEntZNFPoRGxH/ 8+pJxUQEhu0YkJKAkW/3FIc8AoOV9pI+VVffJqc8MgVFRDSRn6SbfFMmiFpfHUQoiKMn jsd57VK0W0sXWCGaRMs2J5wq92+FpzA/i5owHLvCYuVpaE6Ys9MzG/W/o1d9qfZqzkEV L5mfq7XIlf7OJyXpr4NC6WXqKlozaFfU5kbLKpTu47/7Jyt8MB4HKSScDk30XRc0NUI1 2tFg==
X-Gm-Message-State: AFqh2kqc1gEE+MS5NNUyItlj2tS/9LnGbV8ImHpz490LapcjArkOOIeg y6F6WK1rP5qHmMam3FMoEVVl9HemH9xrbv0p3Zzr7A==
X-Google-Smtp-Source: AMrXdXsuwes79pbdn/Uf6cqf/pntJGNQ7Cj+boEEtCjAg6wVndDLlfl+U+hWLv7u+qv1ZO2/gbCHujfWF6GBonZDKZs=
X-Received: by 2002:a05:600c:3b86:b0:3d8:f22e:118f with SMTP id n6-20020a05600c3b8600b003d8f22e118fmr579652wms.144.1674118592229; Thu, 19 Jan 2023 00:56:32 -0800 (PST)
MIME-Version: 1.0
References: <202301171936571355178@chinatelecom.cn> <CAOj+MMGpuK51jZo-9+DOLS7u3wX7K9RBoXzw1dO5ns-sB7Jfvw@mail.gmail.com> <2023011809303660331810@chinatelecom.cn> <CAOj+MMGgmkjJegJs0ONDvLG0WUZO98Mz988oDQsEsb-hwf8M1Q@mail.gmail.com> <2023011911292890875314@chinatelecom.cn>
In-Reply-To: <2023011911292890875314@chinatelecom.cn>
From: Robert Raszuk <robert@raszuk.net>
Date: Thu, 19 Jan 2023 09:56:22 +0100
Message-ID: <CAOj+MMHMmaS0yV=q5V67X6JUMBO6aT_TwaZoMs5zx=Dsdoy=Eg@mail.gmail.com>
To: Chongfeng Xie <xiechf@chinatelecom.cn>
Cc: idr-chairs <idr-chairs@ietf.org>, idr <idr@ietf.org>, donggz <donggz@chinatelecom.cn>, xing <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary="00000000000000824205f29a1c71"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ykw2-u1JKSggbnFfMaqVpW0jfXQ>
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: Thu, 19 Jan 2023 08:56:38 -0000

Hi,

Sorry I missed the embedded comment ...

*[Chongfeng]:*  Another issue with the combination of RFC5549 & RFC9012  is
> that it does not support translation. Translation mechanism such as
> stateless NAT64 has been widely implemented in user's devices and operated
> by large-scale operators.  IPv6-only mechanism at the multi-domain transit
> core should consider this scenario, that's another reason we put forward
> this draft.
>
>
NAT64 translation is completely orthogonal from IPv4 transport over IPv6
core. There is no need to mix or bundle those two solutions together.

You can of course use them together as it seems fit your deployment
requirements.

If you design your network with CGN in place your Tunnel
Encapsulation Endpoint will indicate such a gateway node. All machinery
already defined works perfectly fine.

Regards,
Robert

v2.23.0 | Report a Bug | By Email