IETF Logo Mail Archive

Re: [v6ops] draft-xie-v6ops-reqirements-multi-domain-ipv6only

Fred Baker <fredbaker.ietf@gmail.com> Wed, 06 July 2022 03:48 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B49C15C6CC for <v6ops@ietfa.amsl.com>; Tue, 5 Jul 2022 20:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable 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 Siflu6ctXLlp for <v6ops@ietfa.amsl.com>; Tue, 5 Jul 2022 20:48:10 -0700 (PDT)
Received: from mail-pj1-x102d.google.com (mail-pj1-x102d.google.com [IPv6:2607:f8b0:4864:20::102d]) (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 7F90CC15C153 for <v6ops@ietf.org>; Tue, 5 Jul 2022 20:48:10 -0700 (PDT)
Received: by mail-pj1-x102d.google.com with SMTP id o15so9561509pjh.1 for <v6ops@ietf.org>; Tue, 05 Jul 2022 20:48:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2Tjx93meSEY3tUz0d0gUB6dXnURGvUJbdhOiUpxr+Co=; b=qyTf89EmJlUojlisuB+vIMKtp79lc2NKxE7A10495a53JxPjncKF8zbbVbA45GrO6X lk/qpDzKMyXRk+TqbMZQd/JhlOrifNmfVcRipMQZFaR70HYHMDTatBorulsS+R+wNADN Nd2B4LsiewViTHtCoPp7bLsPmNq2HQ7QgD5s24sNHyr/6J9/c0R5hOjfQpOCODr/VUp3 YGkFBKC7XupGJ9a39rHQOBm2l/MRw/YnNiHiyj5112H/f3F7AQXCsxKbLP6xN0J/fvX2 EE7vvu0w8mZCAqlHzXvtP5GaiCdiJkn+edxk03gy2k0LV5G2lp9Sggon1fEmsKDgoeRW V6sA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=2Tjx93meSEY3tUz0d0gUB6dXnURGvUJbdhOiUpxr+Co=; b=e64stJTtHKc7bYzQhkxoRmj4Qnc/iGoDTHx3Hu8pZzZ8MMQedKyMSV624+LHLs4vWg E2kZEYYNByEXs6f2Z7EC2TQa5aqCNQ9cD9FZu70o71myKg2OPSziWCxBEccCNmF0oRwr aUh1Ke1DQVe9kWyvYM7BWdaPqgBtvE7RBTG5KtQbXEDVC6nVGOT1ZM7NaCbrfHHHFsZn k/WGvgYtN6xh6+EXz8VQbGqIDeTVUK/ZFEElLZ2KOyRz/iyKu1RTwp43z5JkTC+vk92C eWWIT41bXAZdQOr+CjerIXTaOC2Yyv3Zen0r1uB6Ven9PyigAIKTQJisRm5W2TTpL87D rItQ==
X-Gm-Message-State: AJIora9TUOT54keFnlJx81IQ8DHXucvU6JFXR2JeOHTtpMZAF9EEvVnJ HqR6PkRtLlc81VHa5tOGtZQ=
X-Google-Smtp-Source: AGRyM1vxo4gOFqAIh0dA63peiTpGShAqu5tL2TyahdLtmmZXQC07byDrYH5JdGyWFy0dlwVRXtBZEg==
X-Received: by 2002:a17:902:6b07:b0:16b:f220:92fb with SMTP id o7-20020a1709026b0700b0016bf22092fbmr7024386plk.96.1657079289932; Tue, 05 Jul 2022 20:48:09 -0700 (PDT)
Received: from smtpclient.apple ([2601:648:8200:dd20:25ef:7ed3:f0d1:79e4]) by smtp.gmail.com with ESMTPSA id u8-20020a170903124800b0016bd8f66ca0sm6880376plh.162.2022.07.05.20.48.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Jul 2022 20:48:09 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.31\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <c39d7d9f7c0748cd9e4635e4e87df0e8@huawei.com>
Date: Tue, 05 Jul 2022 20:48:08 -0700
Cc: "xiechf@chinatelecom.cn" <xiechf@chinatelecom.cn>, v6ops list <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <05875EC2-1E39-4C38-9532-45104C83D1B0@gmail.com>
References: <CABKBHwdDvdiM1S0-trdtBs7KCHdNbo-aQYL76nR+Fn+QO_oEOg@mail.gmail.com> <c39d7d9f7c0748cd9e4635e4e87df0e8@huawei.com>
To: Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3696.120.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/riQNt5NfGQOwYTbe5s-dvQyJDUw>
Subject: Re: [v6ops] draft-xie-v6ops-reqirements-multi-domain-ipv6only
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2022 03:48:14 -0000


> On Jul 5, 2022, at 3:39 PM, Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org> wrote:
> 
> 1.    Section 4: I think the draft identifies a problem that may be worth solving, that is, there is a need for multi-domain IPv6-only solutions to eliminate unnecessary v4-v6 conversions in the middle.

Dumb question: It seems to me like we're really looking for something similar to BGP between the domains. Would the concept discussed in SNAC be of value?

v2.23.0 | Report a Bug | By Email