<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: Fw: [gnso-acc-sgb] Report for today
- To: Hugh Dierker <hdierker2204@xxxxxxxxx>, gnso-acc-sgb@xxxxxxxxx
- Subject: Re: Fw: [gnso-acc-sgb] Report for today
- From: jwkckid1@xxxxxxxxxxxxx
- Date: Mon, 28 May 2007 14:41:47 -0500 (GMT-05:00)
<HEAD>
<STYLE>body{font-family:
Geneva,Arial,Helvetica,sans-serif;font-size:9pt;background-color:
#ffffff;color: black;}</STYLE>
<META content="MSHTML 6.00.2900.3086" name=GENERATOR></HEAD>
<BODY>
<P>Dr. Dierker and all sgb members,</P>
<P> </P>
<P> I don't believe an "operator" would be able to provide that
information, unless</P>
<P>you are referring to a registrar or registry operator in the borad
sense. A </P>
<P>registrar manager or registry manager should be able to provide an
estimate</P>
<P>however.</P>
<DIV id=compText><BR><BR><BR>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 0px; BORDER-LEFT: #0000ff
2px solid">-----Original Message----- <BR>From: Hugh Dierker
<HDIERKER2204@xxxxxxxxx><BR>Sent: May 28, 2007 2:29 PM <BR>To: Jeff Williams
<JWKCKID1@xxxxxxxxxxxxx>, gnso-acc-sgb@xxxxxxxxx <BR>Subject: Re: Fw:
[gnso-acc-sgb] Report for today <BR><BR>
<DIV>I would be interested to hear from an actual hands on operator of port 43
and her analysis of costing.</DIV>
<DIV> </DIV>
<DIV>Eric<BR><BR><B><I>Jeff Williams <jwkckid1@xxxxxxxxxxxxx></I></B>
wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px;
BORDER-LEFT: #1010ff 2px solid">Margie and all sgb members,<BR><BR>I see and
agree with your and Ross's concern regarding costs to<BR>be covered.<BR>Do you
have a suggestion as to how such costs can be managed<BR>and still provide for
checks and balances so registrants and consumers<BR>privacy is not abused or
misused?<BR><BR>In my view, registrars should not be assuming any of these
costs,<BR>nor should consumers, and I see no need for them to do so as it<BR>is
not their interests which are being served here. Rather third<BR>party wanna
be's and LEA's interests are the interests whom are<BR>being more greatly
served, ergo they should shoulder the bulk of<BR>the costs in terms of fees for
certification, ect. without the ability<BR>to pass such costs on to consumers.
This will give these wanna be<BR>third parties and incentive to behaive
responsibly and give consumers<BR>some level of peace of mind.<BR><BR>Margie
Milam wrote:<BR><BR>> In my view, cost prohibitive would be something that
would require<BR>> a<BR>> significant r&d effort or shift in
operations on the part of<BR>> registrars<BR>> to accommodate, without no
apparent way to recoup the costs.<BR>><BR>><BR>><BR>> All
registrars rely on software, either internally developed or<BR>>
licensed<BR>> from a third party, to perform their domain name
registrations. My<BR>> point is that in developing a WHOIS solution, we need
to take this<BR>> into<BR>> account. Anything that would require a manual
process, such as<BR>> reviewing affidavits or faxes or other documentation
may not be<BR>> scaleable, when you are talking about millions of WHOIS
records.<BR>><BR>><BR>><BR>><BR>><BR>>
Margie<BR>><BR>><BR><BR>
<P>Regards,<BR><BR>Jeffrey A. Williams<BR>Spokesman for INEGroup LLA. - (Over
134k members/stakeholders strong!)<BR>"Obedience of the law is the greatest
freedom" -<BR> Abraham Lincoln<BR><BR>"Credit should go with the
performance of duty and not with what is very<BR>often the accident of glory" -
Theodore Roosevelt<BR><BR>"If the probability be called P; the injury, L; and
the burden, B; liability<BR>depends upon whether B is less than L multiplied
by<BR>P: i.e., whether B is less than PL."<BR>United States v. Carroll
Towing (159 F.2d 169 [2d Cir.
1947]<BR>===============================================================<BR>Updated
1/26/04<BR>CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of<BR>Information Network Eng. INEG. INC.<BR>ABA member in good
standing member ID 01257402 E-Mail jwkckid1@xxxxxxxxxxxxx<BR>Registered Email
addr with the USPS Contact Number:
214-244-4827<BR></P></ZZZBODY></BLOCKQUOTE></BLOCKQUOTE></DIV></BODY>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|