On 19 March 2018 at 17:24, 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"? > > E.g. in Paul H.'s original text > > Instead of: "Where a corporate network serves up partly or completely > different DNS inside and outside its firewall." > > 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. And I would leave off "corporate", "enterprise" and any other qualification of who's using the technology. If there's no reason to specify the type of network it might get used on, then we shouldn't.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
