ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Amendment to the RrSG motion (motion 8 on the motions page)

  • To: "GNSO Council" <council@xxxxxxxxxxxxxx>
  • Subject: [council] Amendment to the RrSG motion (motion 8 on the motions page)
  • From: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Date: Thu, 22 Sep 2011 11:01:54 -0700
  • List-id: council@xxxxxxxxxxxxxx
  • Reply-to: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Web-Based Email 5.6.01

After further discussion within our SG we have been asked to amend our
motion (motion 8 on the motions page) as follows:

1. REPLACE "NOW THEREFORE, the GNSO Council recommends to the ICANN
Board of Directors that:" WITH "RESOLVED, the GNSO Council requests an
Issues Report on the following possible policy revisions and/or
additions:"

2. Strike the section labeled 5. altogether.

I accept those changes as friendly and hopefully Carlos will as well.
This will direct things officially down the PDP path. We can discuss
further on today's call.

Tim

The motion would then read in its entirety as follows:

----------

WHEREAS, the Registrar Stakeholder Group has consulted extensively with
representatives of international law enforcement agencies regarding the
nature of Internet-based criminal activity and the information and tools
available to help address crime that involves the domain name system;
and

WHEREAS, the Registrar Stakeholder Group has reviewed law enforcement
proposals and requests regarding registrar cooperation in addressing
online crime; and

WHEREAS, the GNSO Council is prepared to assist law enforcement in its
long-term effort to address Internet-based criminal activity;

RESOLVED, the GNSO Council requests an Issues Report on the following
possible policy revisions and/or additions:

1. ICANN-accredited registrars must provide to ICANN staff, and ICANN
staff must keep on record, a valid physical address for the purpose of
receiving legal service.  This record must include a valid street
address, city, appropriate region, telephone number and fax number. 
Registrars must publish this information on their respective web sites,
and must notify ICANN staff and update their published addresses within
30 days of a change of address.

2. ICANN-accredited registrars must provide to ICANN staff, and ICANN
staff must keep on record, the names of each registrar’s respective
corporate President, Vice President, and Secretary, or the appropriate
equivalents of those positions.  These data may be made available upon
request to a verified representative of a law enforcement agency, in a
manner agreed to by ICANN staff, ICANN-accredited registrars, and
representatives of law enforcement agencies.  Registrars will notify
ICANN of any changes in this information within 30 days of a change.

3. ICANN-accredited registrars must publish on their respective web
sites e-mail and postal mail addresses to which law enforcement actions
may be directed.  The e-mail address will use a uniform convention
(example: lawenforcement@xxxxxxxxxxx) to facilitate ease of use by law
enforcement agencies.  Registrars may, at their individual discretion,
include language in this section of their web sites, directed to the
general public, that makes clear the use and expected outcomes of these
points of contact and identifies the appropriate points of contact for
other forms of business.  Requests submitted by verified law enforcement
agencies to this discrete point of contact must receive an
acknowledgement of receipt from the registrar within 24 hours.

4. Law enforcement agencies provide, within six months of the date of
approval of this policy by the ICANN Board and via the general advice of
the GAC to the Board, their recommendations for a database and
identification system that allows for expedient identification to a
registrar of a law enforcement agency, and verification of the
contacting party as a law enforcement agency upon that agency’s first
contact with a registrar.






<<< Chronological Index >>>    <<< Thread Index >>>