From: Ulrich Speidel <u.speidel@auckland.ac.nz>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Sat, 23 Sep 2023 22:53:06 +1200 [thread overview]
Message-ID: <1ad0e825-bacc-4dd4-9526-1554d66a41f9@auckland.ac.nz> (raw)
In-Reply-To: <83e9b47895d019d282e21bbdd4f4cc57@ausics.net>
On 23/09/2023 4:22 pm, Noel Butler via Starlink wrote:
> IPv6 is only 4% of traffic that hits my Mail Servers, it's less than
> 1% on my Web servers.
> Just like TCP, it wont be going anywhere, not quietly, and if it were
> to, likely be long after I'm gone, QUIC seems an interesting project,
> and I guess only the decades ahead of us will tell of it becomes a
> raging success.
Now what that tells me is that you and those that use your mail / web
servers are within networks that are either in networks that are old and
have legacy IPv4 allocations, or that are new, desparate, and rich. And
Geoff, if you asked him, would tell you that this is perfectly fine by
him - as long as you're happy with it. In fact, I can recall a
presentation of his not too long ago (APNIC54, AINTEC22?) where he said
pretty much exactly that he didn't foresee a rapid demise of IPv4.
But if you look at the Internet as a whole - and Geoff does, in a very
ingenious way, I might add - then we notice that the percentage of IPv6
out there has been growing steadily. IPv6 is now what about half of
Internet users use. Maybe not the folk that visit your services, but
Internet users nonetheless. So you're in the process of being
outnumbered. But that's perhaps of academic interest only, for now, at
least.
What's a bit more pertinent in some respects is a point that Vint
brought up, and this is that if you want a new IPv4 address these days,
you will generally need to buy it from someone who has an allocation. Or
lease it - which is a little controversial, but not a debate I'm wanting
to enter here. Let's stay with the buying price tag for a moment.
I came home from APNIC54 last year with the insight that my employer's
/16 IPv4 allocation was worth around US$3.5 million. Since we've had the
/16 for ages, I started wondering whether this was even on our asset
list. I was pretty sure that it ought to be. Turns out it wasn't - when
every $100 monitor in our place is. So I started asking questions and am
told that there was a hastily arranged meeting between IT and Finance.
The upshot is that we now have a $3.5m asset on our books that may
appreciate or depreciate, and people who are responsible for managing
it. In fact, I dug a bit further and found a total of around NZ$100m
worth of IPv4 addresses in NZ's public sector, including a /16 held by a
government department that wasn't part of any AS. NZ's auditor general's
office told me that they expected public sector agencies to list IPv4
holdings on their balance sheets.
Why is this important? Because otherwise, there is nothing that stops an
individual with access to your RIR account from transferring your IPv4
holdings to whichever party they so desire. If the addresses are not on
your asset list, then there's nothing that documents that you own the
value that is inherent in them and thus nothing to sue anyone for. One
imagines this as the ultimate stunt that a disgruntled sysadmin might
pull off before they leave your employ.
But let's get back to that newly-found asset that we now have to manage.
Your next CGNAT now becomes an investment in making that newly-found
asset a little less tradable. A bit like putting a shiny new building
right onto the only access way to your back sections you've just been
told you can actually develop.
Of course, this only applies to folk who sit on larger address blocks -
for a /24, it won't make much of a difference on the balance sheet.
--
****************************************************************
Dr. Ulrich Speidel
School of Computer Science
Room 303S.594 (City Campus)
The University of Auckland
u.speidel@auckland.ac.nz
http://www.cs.auckland.ac.nz/~ulrich/
****************************************************************
next prev parent reply other threads:[~2023-09-23 10:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 4:39 Ulrich Speidel
2023-09-20 1:13 ` Dave Taht
2023-09-23 1:33 ` Noel Butler
2023-09-23 1:47 ` Vint Cerf
2023-09-23 4:22 ` Noel Butler
2023-09-23 6:41 ` Gert Doering
2023-09-23 10:53 ` Ulrich Speidel [this message]
2023-09-23 11:28 ` Sebastian Moeller
2023-09-23 12:56 ` Ulrich Speidel
2023-09-25 4:40 ` Noel Butler
2023-09-25 5:00 ` Ulrich Speidel
2023-09-25 5:10 ` Hayden Simon
2023-09-25 5:51 ` Noel Butler
2023-09-23 12:08 ` Hesham ElBakoury
2023-09-24 18:30 ` Michael Richardson
2023-09-25 4:04 ` Noel Butler
2023-09-21 13:20 ` Alexandre Petrescu
2023-09-21 19:05 ` Inemesit Affia
2023-09-21 19:08 ` Dave Taht
2023-09-22 8:26 ` Alexandre Petrescu
2023-09-22 8:41 ` David Lang
2023-09-22 17:12 ` Michael Richardson
2023-09-22 17:26 ` David Lang
2023-09-22 18:52 ` Michael Richardson
2023-09-23 21:55 ` Larry Press
2023-09-24 2:46 ` Dave Taht
2023-09-24 12:00 ` Hesham ElBakoury
2023-09-25 7:46 ` Alexandre Petrescu
2023-09-25 8:59 ` David Lang
2023-09-25 12:30 ` Frantisek Borsik
2023-09-22 17:00 David Fernández
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1ad0e825-bacc-4dd4-9526-1554d66a41f9@auckland.ac.nz \
--to=u.speidel@auckland.ac.nz \
--cc=starlink@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox