+1 to all from frmr usgovie. We ain't that clever.
On Wednesday, March 22, 2017, Jim Reid <j...@rfc1035.com> wrote: > > > On 21 Mar 2017, at 14:53, Suzanne Woolf <suzworldw...@gmail.com > <javascript:;>> wrote: > > > > RFC 3172 was written in 2001… > > RFC 3172 was an attempt to rewrite history and contrive an acronym: > Address and Routing Parameter Area - really? > > > Respectfully, I’ve always wondered who has this problem (US or non-US) > besides network infrastructure geeks Of a Certain Age (yes, including > myself, and many IETF participants). > > It's a convenient tool for those hostile to USG "control" of the Internet: > ie the US military is responsible for everything under .arpa, the US > military's ARPA has still got some special status in the > operation/development/control of the Internet, etc, etc. [And say things > like "if .arpa isn't for US military control, why can't the string be > changed?" or ".arpa hasn't been renamed since the Internet started 25-30 > years ago. That proves ARPA/DoD is in charge of the Internet.".] It's utter > nonsense of course. But that doesn't stop government officials and > policymakers from making these arguments. I have seen them do this many > times. Sigh. RFC3172 didn't make things better. > > _______________________________________________ > DNSOP mailing list > DNSOP@ietf.org <javascript:;> > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
