DoD IP Space

Wed Jan 20 15:05:42 UTC 2021

I am aware of some companies that have used parts of a DoD /8 internally to
address devices in the field that are too old to ever support IPV6.  Those
devices also never interact with the public internet, and never will, so
for them, I guess the only risk would be that some other internal system
that wants to talk to those devices would not also be able to talk to any
endpoint on the public internet that wound up using space allocated from
that block, some time in the future.  Is that about right or am I missing
some key failure point?

On Wed, Jan 20, 2021 at 9:59 AM j k <jsklein at gmail.com> wrote:

> My question becomes, what level of risk are these companies taking on by
> using the DoD ranges on their internal networks? And have they
> quantified the costs of this outage against moving to IPv6?
>
> Joe Klein
>
> "inveniet viam, aut faciet" --- Seneca's Hercules Furens (Act II, Scene 1)
> "*I skate to where the puck is going to be, not to where it has been."
> -- *Wayne Gretzky
> "I never lose. I either win or learn" - Nelson Mandela
>
>
> On Wed, Jan 20, 2021 at 9:06 AM John Curran <jcurran at istaff.org> wrote:
>
>> Indeed.
>> /John
>>
>> > On Jan 20, 2021, at 8:47 AM, Cynthia Revström <me at cynthia.re> wrote:
>> >
>> > But if you do this, make sure you keep track of where you might have
>> put policies like this in, in case the DoD sells some the space or whatever
>> in the future.
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20210120/5bdae2b7/attachment.html>