Re: [v6ops] IPREF as a transitioning tool

Owen DeLong <owen@delong.com> Sun, 12 November 2023 19:36 UTC

Return-Path: <owen@delong.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 1A390C151097 for <v6ops@ietfa.amsl.com>; Sun, 12 Nov 2023 11:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 (1024-bit key) header.d=delong.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 96XjDUCRF26n for <v6ops@ietfa.amsl.com>; Sun, 12 Nov 2023 11:36:48 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id B3F82C15109A for <v6ops@ietf.org>; Sun, 12 Nov 2023 11:36:48 -0800 (PST)
Received: from smtpclient.apple ([192.168.100.168]) (authenticated bits=0) by owen.delong.com (8.17.1/8.15.2) with ESMTPSA id 3ACJalBM3302605 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT); Sun, 12 Nov 2023 19:36:47 GMT
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com 3ACJalBM3302605
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1699817807; bh=X8yv9SfqUIsFgwDCxnUm+wFYKczgngLZfHTCW/H5PZE=; h=From:Subject:Date:References:Cc:In-Reply-To:To:From; b=26s+h2eW3m9FRUCNOBXwmneHpv6wVSqbO/wjkJ5AeBL0biwjw8sgDi8zip4qqhRLk bPWCy08wVCxujQci6BVV4T2R02NUU5YAiEqJAxWULR5gM19mEXlyRCStJsrrxK+ddu S+Sud1DJVn8zLy58hT68wX7UCkqhHK6pu75GgzUc=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Owen DeLong <owen@delong.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 12 Nov 2023 11:36:36 -0800
Message-Id: <A57D3372-BEDE-4C76-BC9A-1A1A22C24FA0@delong.com>
References: <ZVEU_tZubRnfn_3n@Space.Net>
Cc: waldemar <waldemar@wdmsys.com>, v6ops@ietf.org
In-Reply-To: <ZVEU_tZubRnfn_3n@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: iPhone Mail (20G81)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.4 (owen.delong.com [192.159.10.2]); Sun, 12 Nov 2023 19:36:47 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pZLZyFNHThEjB02XuBUWL-Ct5to>
Subject: Re: [v6ops] IPREF as a transitioning tool
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: Sun, 12 Nov 2023 19:36:53 -0000

Facebook has demonstrated the latter. Mobile carriers have not. I’m not making value judgments, merely pointing out that there are significant implementation and trade off differences between the two. 

It felt like you were holding mobile carriers up as an example of demonstrating IPv4AAS architecture on the server side.

Facebook is a relatively constrained example with a very large team to manage the implementation and work out the issues as they arise.

Not saying it can’t or won’t work, just saying it’s not as straightforward as we’d like it to be. 

Owen


> On Nov 12, 2023, at 10:10, Gert Doering <gert@space.net> wrote:
> 
> Hi,
> 
>> On Sun, Nov 12, 2023 at 09:28:06AM -0800, Owen DeLong wrote:
>> In fairness, what mobile operators have demonstrated is a relatively limited
>> set of clients being not significantly worse off with iPv6 only and an IPv4AAS
>> capability on the client side to reach IPv4-only services.
>> 
>> That???s not so much the case with IPv6-only on the server side and some form
>> of IPv4AAS to handle IPv4-only clients.
> 
> Not sure I understand.  Are you saying server side works better, or worse?
> 
> (Facebook has demonstrated the latter case)
> 
> Gert Doering
>        -- NetMaster
> -- 
> have you enabled IPv6 on something today...?
> 
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279