Only the crazy would do that!

Sent from my iPhone

On 20 Feb 2020, at 13:11, Stephen Wilcox <[email protected]> wrote:


On Thu, 20 Feb 2020 at 19:39, Tom Bird 
<[email protected]<mailto:[email protected]>> wrote:
On 20/02/2020 12:07, Richard Halfpenny wrote:
> Hi Tom,
>
> On what connectivity (colo/fibre/etc)?

Just on ethernet terminated circuits to customer premises (not PPPoE).

I think for colo people still expect a /29 or so but for access it feels
wrong to be wasting those precious $20 IP addresses if we don't need to,
and I think we should be fine with /31 (and ipv6 of course) but just
wanted to float the idea in case I was missing anything.


Is it that time of the year again already? I was just about to mention all the 
unused Class E space too..... :)

The answer is do what your policy thinks is best. If you want to do it, then do 
it, and deal with the noted adoption and compatibility issues (which are 
reasonably minor). On the other hand, if your existence depends on a few "$20 
IP addresses" and you don't have any and aren't willing to source some, then 
converting your /30s to /31s will be a whole bunch of fun, but you'd have a 
better use of time getting those couple hosting customers to hand back a /25 or 
/26 that you were a bit generous with 10 years ago, but you're likely just 
stalling for runout of your allocation.... ie its not worth the effort for what 
you gain.

Steve


Reply via email to