Subject: GA-DIGEST V1 #1413
From: [email-masked] (GA-DIGEST)
To: [email-masked]

GA-DIGEST          Monday, September 9 2002          Volume 01 : Number 1413

----------------------------------------------------------------------

Date: Mon, 09 Sep 2002 03:47:14 -0400
From: Joanna Lane <[email-masked]>
Subject: RE: [ga] Wednesday, 9-11-02: Transfer TF call: open to interested parties to provide comments and dialogue with TF regarding draft recommendations

> On Wednesday, September 11, 2002, the Transfer Task Force call 
> will be open......

How incredibly insensitive.

Regards,
Joanna
- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Mon, 09 Sep 2002 12:12:41 +0000
From: "Roberto Gaetano" <[email-masked]>
Subject: Re: [ga] YesNIC hoarding joesworld.com

Marc Schneiders wrote:
>
>On Sat, 7 Sep 2002, at 13:19 [=GMT+0200], Vittorio Bertola wrote:
>
> > Well - if this, as it seems, is really a bug about the WHOIS clauses
> > in the Registrar Agreement, I think the WHOIS Task Force should
> > definitely propose a patch to it in its final report.
>
>Why? How can an unused domain do any damage/crime? If you have a car and
>hide it in your garage, you don't need license plates. You cannot hurt
>anybody with it, nor evade road tax.
>

I support the principle that upon registration of a domain name the 
registrant has to provide correct and complete information, but also that 
he/she has the right to "opt-out" from public listing.
This said, I don't see the problem in treating inactive domains the same 
way: info should be provided but can be kept private, if the registrant 
wants.

Regards
Roberto

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Mon, 9 Sep 2002 16:10:01 +0200
From: Thomas Roessler <[email-masked]>
Subject: [ga] Byfield on GA Reform / comments

Ted Byfield has posted some comments on the second implementation  
report and my remarks about it.  See  
<http://www.icannwatch.org/article.php?sid=938>.  My response is  
available in my weblog.

Regards,
- -- 
Thomas Roessler                        http://log.does-not-exist.org/
- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Mon, 9 Sep 2002 16:12:06 +0200
From: Thomas Roessler <[email-masked]>
Subject: [ga] Re: Byfield on GA Reform / comments

On 2002-09-09 16:10:01 +0200, Thomas Roessler wrote:

>Ted Byfield has posted some comments on the second implementation  
>report and my remarks about it.  See  
><http://www.icannwatch.org/article.php?sid=938>.  My response is  
>available in my weblog.

... and here:

   At IcannWatch, [1]Ted Byfield has taken up my brief comments on the
   ERC's [2]Second Implementation Report and its suggestions about the
   GA's future. Bad enough, Ted gets much of this wrong: The ERC does
   indeed move into the right direction, as I wrote.

   First of all, when I say that the ERC is moving, then I have in mind
   from where it is coming: From the [3]blueprint's recommendation that
   the GA should be (1) a cross-constituency meeting place and (2)
   moderated. In particular, the blueprint's GA does not provide for any
   participation by members of the general public; this is in line with
   the [4]Names Council's recommendations on the matter. The second
   implementation report seems to say good-bye to this idea of a forum
   exclusively reserved to constituency members.

   Second, what does moderation (or proper moderation) mean? When reading
   the second implementation report, it doesn't look like the ERC
   actually wants to get into micro-managing discussion lists. Thus, I'll
   take this not to be meant in the technical sense, but rather as "do
   what it takes to facilitate reasonablen discussions." That's an
   approach which I, at least, can certainly live with.

   Third, what about the idea of having the ALAC sponsor a General
   Assembly? Assuming that the ultimate goal is to have a canonical forum
   for intelligent public debate about ICANN issues, this makes a whole
   lot of sense. While many may be skeptic about the ALAC's success, the
   perspective is certainly the right one - as long as there is some
   reasonable home for this kind of discussion in the mean time, and in
   the case that ALAC fails in one way or the other. The second
   implementation report actually provides for such an interim home, by
   basically saying that the GNSO should continue to maintain the current
   DNSO GA.

   The single difference concerns the role of the GA's chair: Currently,
   this function actually shows up in ICANN's bylaws; in the future, it's
   most likely doomed to die. Instead, the second implementation report
   vaguely talks about list managers/moderators which would have to be
   appointed by the Names Council. Byfield emphasizes that power (such as
   it is, in this context) would be transferred from elected
   representatives to interim appointees - as if this was a change. It
   isn't. The current practice of letting the GA elect its chair isn't
   codified in [5]the current ICANN bylaws, either - article VI-B section
   2 (i) actually determines that The NC shall elect the Chairman of the
   GA annually.

   Wrapping up, the new recommendations basically boil down to giving the
   status quo another chance, with the perspective that the GA is
   ultimately transferred to the responsibility of the ALAC, and with the
   desire for stronger moderation. Compare that to declaring the GA
   "closed shop" like in the blueprint and the Names Council's
   recommendations.

   In my view, the most important questions which remain for the close
   future are these:
     * How can the General Assembly (and, later, the ALAC) participate
       directly in the Names Council's deliberations? Would it, for
       instance, be realistic to reserve space for an ALAC liaison on the
       Names Council, and to use (for instance) the GA chair as a
       placeholder for the time until ALAC is operational?
     * How can the General Assembly (and, later, the ALAC) participate
       directly in [6]policy development?

References

   1. http://www.icannwatch.org/article.php?sid=938
   2. http://www.icann.org/committees/evol-reform/second-implementation-report-02sep02.htm#2C1b
   3. http://www.icann.org/committees/evol-reform/blueprint-20jun02.htm#GNSO
   4. http://www.dnso.org/clubpublic/council/Arc10/msg00273.html
   5. http://www.icann.org/general/bylaws.htm#VI-B
   6. http://log.does-not-exist.org/archive-0208.html#02082213231030015387

- -- 
Thomas Roessler                        http://log.does-not-exist.org/
- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

Date: Mon, 09 Sep 2002 12:28:11 -0400
From: [email-masked]
Subject: [ga] is your Internet connection secure from surveilance?

This is a multi-part message in MIME format.
- --------------69F8666E2675F2EC7C2CEFFA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have attached a draft PDF file addressed to Canada's privacy and
information commissioners which outlines my concerns respecting privacy
issues in root operations.

I would welcome any comments.  Please email them directly to me.

kindest regards
joe baptista

- --
www.dot-god.com
  .. on the other side of the internet universe

- --------------69F8666E2675F2EC7C2CEFFA
Content-Type: application/pdf;
 name="Root Server Privacy Complaint.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="Root Server Privacy Complaint.pdf"

- --------------69F8666E2675F2EC7C2CEFFA--

- --
This message was passed to you via the [email-masked] list.
Send mail to [email-masked] to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html

------------------------------

End of GA-DIGEST V1 #1413
*************************