multiple prefixes

[Tore Anderson]

* David Barak

> --- On Tue, 2/12/13, Tore Anderson <tore at fud.no> wrote:
> 
>> You'll need [non-free] hardware to run the [free] software 
>> implementation on, even at a small scale.
> 
> Many non-ISP organizations view hardware capital costs (i.e.
> non-recurring) as vastly preferable to monthly recurring charges,
> especially when the term length for the MRC is "forever", even if the
> MRC is low.  Whether or not this is a good idea is a separate
> question, but it's a well-known behavior of many in the enterprise
> world.

Sure. But hardware also comes with recurring charges. Electricity,
hosting, support contracts, sysadmin hours, and so forth.

> I do think the attitude presented by many of the folks who encourage
> IPv6 adoption is not conducive to getting the enterprises to adopt v6
> - we as a community come across as dismissive of the level of effort
> required for the enterprises to learn a whole new way of doing things
> for benefits which are neither obvious not quantifiable in the
> near-term.  Modifying our tone and presentation, and spending more
> time listening to the concerns of the enterprise IT folks, would be
> worth it.

I like facts. If someone has considered the facts, and concluded that
NPTv6 is the best approach for them, then great, that's what they should
be using. Same thing goes for PI or PA or anything else.

My domain name notwithstanding, I don't like FUD. FUD may lead folks to
make the wrong decisions, and that's certainly not, to borrow your
words, conducive to getting the enterprises to adopt v6.

So. Some facts:

- NPTv6 isn't free. It might be cheap, or expensive. It Depends.
- PI isn't free. In the RIPE region, it's cheap.
- NPTv6 has adverse effects on certain applications.
- PI doesn't cause any application breakage.
- NPTv6 doesn't cause DFZ growth.
- PI causes DFZ growth.
- PI doesn't require the end user to run BGP.
- PI and NPTv6 aren't even mutually exclusive.

Best regards,
-- 
Tore Anderson