DoD IP Space

Wed Jan 20 15:26:57 UTC 2021

I recently had a discussion with an Asian ISP that was asking the IETF to PLEASE re-declare DoD space to be private space so that they could use it. This particular ISP uses IPv6 extensively (a lot of their services are in fact IPv6-only) but has trouble with its enterprise customers. Frankly, enterprise use of IPv6 is a problem; they seem to push back pretty hard against using IPv6.

I find this thread highly appropriate.

> On Jan 20, 2021, at 6:58 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 --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20210120/d6111e4c/attachment.sig>