On Mon, Mar 19, 2018 at 9:24 PM, Michael Sinatra <mich...@brokendns.net> wrote: > Rather than try for some physical demarcation like "firewall" or "network," > why don't we simply say "organizationally-defined perimeter" or "perimeter > defined by the organization," which leaves it vague enough to support the > "many potential variants"? > > Use: "Where a corporate [enterprise?] network serves partly or completely > different DNS based on a client's location inside or outside of a perimeter > defined by that organization." > > This also gives the enterprise organization both the authority (and onus) to > define its perimeter in a reasonable logical way.
+1 A good idea actually. | Artyom Gavrichenkov | gpg: 2deb 97b1 0a3c 151d b67f 1ee5 00e7 94bc 4d08 9191 | mailto: xima...@gmail.com | fb: ximaera | telegram: xima_era | skype: xima_era | tel. no: +7 916 515 49 58 _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
