Domain Names
To the ITPB
For our agenda item on a draft Domain Names policy, I am attaching a draft policy statement and issues description statement (background below) that has been generated by a task force that Max Benavidez, Al Solomon and Jim Davis commissioned to get in front of some rapidly rising issues associated with the assignment and use of web Domain Names. These are issues associated with Domain Names in use for UCLA activities and UCLA-oriented domain names in use for activities that are not UCLA-related. The draft policy basically clarifies how existing policy applies to the assignment and use of domain names. It further proposes new policy especially around the assignment and management of domain names. The essence of this is to create procedures for registration and tracking of domain name usage.
The task force had wide university representation from Marketing and Communications, IT Security and Policy, Faculty (Institute for Cyberspace Law and Privacy), Trademarks and Licensing, Campus Counsel, Marketing programs, Medical Center, Athletics, Marketing and Web Publications, the College, CTS, and Administrative Policies Coordinator. With respect to the procedures, External Affairs emerged as one logical place to oversee domain name assignments. The current version reflects this but it is recognized that this is an administrative point of discussion once there has been discussion on the substance of the proposed policy.
Michael Stone (External Affairs) and Kent Wada (AIS) chaired the task force and will be join us to discuss it. It is recognized that the Domain Names issues are a subset of a much larger set of issues. Michael and Kent will discuss these broader issues and will present preliminary plans to address.
The current draft of the policy has been discussed with EVC Rory Hume and VCs, Pete Blackman, Joe Mandel and Mike Eicher and has been OK'd for broader discussion with the ITPB.
Here are six specific examples to illustrate what the draft policy is intended to address:
1. Protecting UCLA Trademark Outside the .EDU Domain
Ex: ucla.com -- UCLA had to take action against ucla.com, a former porn site and get the name registered to the Regents.
2. Country Codes Purchased by Third Party Entrepreneurs
Ex: ucla.tv or ucla.la -- Some small countries have sold their country codes outright to entrepreneurs who, in turn, are making them available to individuals and corporations at a subscriber cost.
3. Marketing URL's -- Marketing needs sometimes dictate a short memorable URL which may not include the UCLA name, although the ownership is UCLA's.These are sometimes aliases for ucla.edu sites.
Ex: bruinwalk.com -- Registered improperly to a student rather than the UC Regents but trades on the UCLA connection since Bruin Walk physically exists on the campus.
Ex: strokecenter.org (theoretical example) -- A faculty member creates and registers this site using UCLA resources. The name is generic and easy-to-remember. The services are offered by UCLA. Problems could arise when/if the faculty member is hired away by another university and "takes" the website along.
4. Protecting UCLA Ownership of Sites Using "Generic" Names
Ex: uclazer -- A group of physicians, affiliated with UCLA, but in private practice in the Medical Plaza who would like to capitalize on the name/reputation of the university without direct connection/affiliation to university's services.
5. Sites Registered to Individuals or Entities Other than the UC Regents
Ex: uclastorehub.com -- Registered in the name of an ASUCLA employee.
6. UCLA Sites Registered in Name of Third Party Group
Ex: uclabruins.com ? Registered in the name of FansOnly, a third-party provider of athletic websites for a number of major universities. They create the site and provide all hosting, maintenance, etc., and carry banner advertising. UCLA has a contractual agreement.
20 Aug 2001