[gnso-dow123] Next week's call

[Jordyn Buchanan <jordyn.buchanan@xxxxxxxxx>]

On next week's call (Nov. 15 @ 9:30 AM EST), plan to discuss the following
issues:

1) Is the whois-tech definition a reasonable definition of the purpose of
the technical contact? The definition would probably read something along
these lines:

The technical contact is a a contact capable of investigating technical
problems involving the registration and
resolution of a domain name (e.g., lame delegation, incorrect DNS
configuration) and taking action to resolve the problem.

Explanatory note:
Technical problems involving the registration and resolution of a
domain name include inappropriate or incorrect domain name server
configuration data in the registration record (including lame delegation and
incorrect configuration of the DNS).

2) Steve M. (and others are welcome) to follow up with some elaboration of
how to identify which content/internet resources the admin contact is
responsible for. (What content is the admin contact of
blogware.com<http://blogware.com>responsible for? How do we identify
which content is affiliated with the
registrant/admin contact and which content is controlled by third parties?
Is there a clear way to define this?)

It would probably be worthwhile to have another topic/question as well. I am
open to suggestions for this last topic.