Re: [v6ops] Is there a problem? [was: Why enterprises aren't adopting IPv6]
Owen DeLong <owen@delong.com> Thu, 07 October 2021 05:47 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 8290D3A0AE0 for <v6ops@ietfa.amsl.com>; Wed, 6 Oct 2021 22:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYIvzLie1YKa for <v6ops@ietfa.amsl.com>; Wed, 6 Oct 2021 22:47:03 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 306B73A0ADC for <v6ops@ietf.org>; Wed, 6 Oct 2021 22:47:03 -0700 (PDT)
Received: from smtpclient.apple ([IPv6:2620:0:930:0:7800:cdc0:cc78:e6ae]) (authenticated bits=0) by owen.delong.com (8.16.1/8.15.2) with ESMTPSA id 1975l0I3101222 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 6 Oct 2021 22:47:02 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com 1975l0I3101222
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1633585622; bh=CPbgIh1CKxfpthj+Rfwhd0FXkkcB2WiQvv6EYcIt/1w=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=D+BKnpE02FwH8kUZttBEhep/ejQX7I7AcvV77u+IiO0ZANjTWx2FQYKit7+UQbcv5 9S7gshMAUSxrjyzEeW5VR1qXkZbnrKSUw86bPQqALZ+wlSR3iZUcDkWcUE/p4gY9Gx 1XsfH9WN25AzcebPX+OWk9G2JqXe5xPAx7ICWVyU=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <m1mWc20-0000IcC@stereo.hq.phicoh.net>
Date: Wed, 06 Oct 2021 22:47:00 -0700
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <557CF2DF-0259-45FC-A03B-8EC4931EECE9@delong.com>
References: <m1mWPCU-0000JAC@stereo.hq.phicoh.net> <C7F9DE00-8460-47AA-94BA-91EDCB805813@delong.com> <m1mWc20-0000IcC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops-10@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.4 (owen.delong.com [IPv6:2620:0:930:0:0:0:200:2]); Wed, 06 Oct 2021 22:47:02 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/sEG4ZijnoDDSeSbGiz8fBb66EUM>
Subject: Re: [v6ops] Is there a problem? [was: Why enterprises aren't adopting IPv6]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Oct 2021 05:47:13 -0000
> On Oct 2, 2021, at 03:14 , Philip Homburg <pch-v6ops-10@u-1.phicoh.com> wrote: > >> Eyeball providers are out of IPv4 addresses and acquisition cost >> exceeds customer value. Eyeball providers need a much larger supply >> of IPv4 addresses to support IPv4-only content providers than the >> content providers do. > > As far as I know, eyeball providers have waited until the last possible > moment with offering IPv6 to customers. For example, my phone got IPv6 address > (on mobile) just weeks ago. Depends on where you live. T-Mo in the US has been v6 for years… Same with VZW and even ATT. Not sure where SPRINT/Softbank/whatever they became (T-mo?) is now, but they’ve been trying their best to become irrelevant in the US market for years now. MVNOs still lag, but most of them aren’t significant fractions of the market any more anyway. I think “Metro by T-Mo” is still lagging as well. > Even then, most countries have less than 50% adoption of IPv6 by eyeball > providers. That depends on how you measure. If you just count by number of providers, that’s probably true because the many many small ISPs are among the biggest laggards in that market. If you count eyeballs passed, not sure that’s so much the case, at least in the US. Comcast, AT&T, Cox, and others have all deployed IPv6 to their eyeball customers. Verizon FIOS is still lagging here, to the best of my knowledge. > So it seems like eyeball providers didn't do IPv6 when they had enough > IPv4 addresses. And that they are out of address suddenly everybody has > to do IPv6. Not at all… But even if they had done IPv6 much earlier (and many of the larger ones did), until the content providers their customers most care about reaching are on IPv6, they don’t have the option of running IPv6-only customers. > Of course, I'm happy that my phone now finally has an IPv6 address. > >> Major eyeball providers could, actually start demanding higher >> settlements for IPv4 peering than v6 and use that to start pushing >> some of the V4 costs back onto the content providers. > > I think for a long time, the internet community at large has argued against > eyeball providers demanding money from content providers. Not very successfully so far, though that is admittedly changing recently. > However, in the cases where an eyeball provider is already collecting > money from content providers, what is stopping them from offloading the > cost of the CGNAT and IPv4 addresses to the content providers? That seems like > an easy way out. There are multiple types of costs and some of them are hard to quantify. It’s not as simple as one might hope, but yes, this might be possible. > The classical argument again this is that the customers of the eyeball ISP > should pay for access to IPv4. They are the ones that want the content. Which comes back to my argument that eyeball providers should start offering a discount to customers willing to take IPv6-only services and/or surcharge customers demanding IPv4 service. Owen
- [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Erik Kline
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Jen Linkova
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Bob Harold
- Re: [v6ops] Implementation Status of PREF64 daveb
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Fernando Gont
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 STARK, BARBARA H
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 JORDI PALET MARTINEZ
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 JORDI PALET MARTINEZ
- Re: [v6ops] Implementation Status of PREF64 Fernando Gont
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 JORDI PALET MARTINEZ
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Nick Hilliard
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 sthaug
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Ola Thoresen
- Re: [v6ops] Implementation Status of PREF64 Ola Thoresen
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Fernando Gont
- Re: [v6ops] Implementation Status of PREF64 Fernando Gont
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Nick Hilliard
- Re: [v6ops] Implementation Status of PREF64 Nick Hilliard
- [v6ops] Why enterprises aren't adopting IPv6 (Re:… Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Chris Cummings
- Re: [v6ops] Implementation Status of PREF64 Nick Buraglio
- Re: [v6ops] Implementation Status of PREF64 Kevin Myers
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Mikael Abrahamsson
- Re: [v6ops] Implementation Status of PREF64 Dale W. Carder
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Nick Hilliard
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Owen DeLong
- Re: [v6ops] Why enterprises aren't adopting IPv6 … otroan
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Nick Buraglio
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Gert Doering
- Re: [v6ops] Why enterprises aren't adopting IPv6 … otroan
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Owen DeLong
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Owen DeLong
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Gábor LENCSE
- Re: [v6ops] Why enterprises aren't adopting IPv6 … otroan
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Owen DeLong
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Gert Doering
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Gert Doering
- Re: [v6ops] Why enterprises aren't adopting IPv6 … otroan
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Owen DeLong
- [v6ops] Is there a problem? [was: Why enterprises… Brian E Carpenter
- Re: [v6ops] Is there a problem? [was: Why enterpr… Gert Doering
- Re: [v6ops] Is there a problem? [was: Why enterpr… Clark Gaylord
- Re: [v6ops] Is there a problem? [was: Why enterpr… Brian E Carpenter
- Re: [v6ops] Is there a problem? [was: Why enterpr… Hamilton, Robert
- Re: [v6ops] Is there a problem? [was: Why enterpr… Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Is there a problem? [was: Why enterpr… Gert Doering
- Re: [v6ops] Is there a problem? [was: Why enterpr… Brian E Carpenter
- Re: [v6ops] Is there a problem? [was: Why enterpr… Philip Homburg
- Re: [v6ops] Is there a problem? [was: Why enterpr… Owen DeLong
- Re: [v6ops] Is there a problem? [was: Why enterpr… Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Is there a problem? [was: Why enterpr… Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Nick Hilliard
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 STARK, BARBARA H
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Why enterprises aren't adopting IPv6 … Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 otroan
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 STARK, BARBARA H
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Ted Lemon
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 STARK, BARBARA H
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Clark Gaylord
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Ted Lemon
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 STARK, BARBARA H
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Lorenzo Colitti
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] RFC7934 BCP 'Host Address Avaialabili… Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] When Android might disconnect because… Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] When Android might disconnect because… Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Philip Homburg
- Re: [v6ops] When Android might disconnect because… Philip Homburg
- Re: [v6ops] When Android might disconnect because… David Farmer
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] University WiFi (was: Implementation … David Farmer
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 STARK, BARBARA H
- Re: [v6ops] Implementation Status of PREF64 Simon
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Mark Smith
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 David Farmer
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Vasilenko Eduard
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Pascal Thubert (pthubert)
- Re: [v6ops] Implementation Status of PREF64 Dale W. Carder
- Re: [v6ops] Implementation Status of PREF64 Ted Lemon
- Re: [v6ops] Implementation Status of PREF64 Ole Troan
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- [v6ops] Campus roaming [was Re: Implementation St… Brian E Carpenter
- Re: [v6ops] Implementation Status of PREF64 Simon
- Re: [v6ops] Implementation Status of PREF64 Ted Lemon
- Re: [v6ops] Implementation Status of PREF64 Gert Doering
- Re: [v6ops] Implementation Status of PREF64 Ted Lemon
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] Implementation Status of PREF64 Owen DeLong
- Re: [v6ops] When Android might disconnect because… Alexandre Petrescu
- Re: [v6ops] When Android might disconnect because… Alexandre Petrescu
- Re: [v6ops] "all hosts SHOULD implement address c… Alexandre Petrescu
- Re: [v6ops] Implementation Status of PREF64 Fred Baker
- Re: [v6ops] "all hosts SHOULD implement address c… Alexandre Petrescu