<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [ga] Initial Report of the GNSO Fast Flux Hosting Working Group
- To: Joop Teernstra <terastra@xxxxxxxxxxxxxx>, ICANN Policy staff <policy-staff@xxxxxxxxx>, "twomey@xxxxxxxxx" <twomey@xxxxxxxxx>, Peter Dengate Thrush <barrister@xxxxxxxxxxxxxxx>, ICANN SSAC <ssac@xxxxxxxxx>, dave.piscitello@xxxxxxxxx, Steve Crocker <steve@xxxxxxxxxxxx>, Ga <ga@xxxxxxxxxxxxxx>
- Subject: Re: [ga] Initial Report of the GNSO Fast Flux Hosting Working Group
- From: "Jeffrey A. Williams" <jwkckid1@xxxxxxxxxxxxx>
- Date: Mon, 26 Jan 2009 01:00:41 -0800
Joop, Eric and all,
Well surely Eric is correct here. But ICANN was warned early
on back in 1999 that forcing registrants to register Domain Names
via a Credit card, was ill advised for many of the reasons that we
are all now suffering from on a global basis. But the than Interim
Bod disagreed of course. Typical ICANN reasoning, bad reasoning.
Seems to me that ICANN should be the organization to the extent
that the fraudulent use of credit cards for errant registrations be the
barer of the liability of such fraud as it was their policies that to a
degree are responsible for same. However as this is massive fraud
in scope, it would seem that the potential for criminal intent may
indicate more serious legal considerations from ICANN and the than
sitting ICANN Interim Bod.
Unintended consequences? I don't think so!
Joop Teernstra wrote:
> Eric Brunner-Williams' contribution to the WG is worth reading.
>
> Some excerpts:
>
>
>
>> Not only should we be unwilling to accept the consequences of
>> non-registrars-non-registries attempting
>> to socialize their costs to registrars and registries, we should be
>> unwilling to accept the
>> consequences of sub-cost registrars attempting to socialize costs to
>> actual-cost registrars.
>> The RAA does not require us to share the fate of the credit card
>> industry, or to adopt their fraud risk,
>> or place ourselves in the position of being likely to be the target
>> of a take-down attempt or domain
>> hijacking to benefit businesses which elected to share the fate of
>> the credit card industry and adopt
>> their fraud risk. We�re not unaware of the problem, or indi..erent
>> to it, but socializing the cost of theft
>> from some victims, who accepted the risk, to more victims who did
>> not, and have no share in the
>> benefits from that involuntarily shared risk, doesn�t solve the
>> problem, it merely repeats the theft.
>
>
> Unintended Consequences
> There have been unintended consequences.
> We need to reconsider the institutional role of �security� We can
> accept that ICANN�s �security�
> agent may be compromised, and is in the present. Do we leave it
> unminded, pretend it didn�t
> happen, and won�t happen again, or do we take it as a given and
> institutionalize corruption, parcel
> out the �security� budget to the constituencies and get on with
> �security� being both subjective and
> created by compromise? The capture of the �security and stability�
> blob in the org chart by the
> �identity theft� mob is a non-trivial event. The upcoming SSAC Review
> is the appropriate venue to
> pursue the question of the SSAC�s performance, structure, and
> institutional responsibilities.
>
>
> -joop-
Regards,
Spokesman for INEGroup LLA. - (Over 284k members/stakeholders strong!)
"Obedience of the law is the greatest freedom" -
Abraham Lincoln
"YES WE CAN!" Barack ( Berry ) Obama
"Credit should go with the performance of duty and not with what is
very often the accident of glory" - Theodore Roosevelt
"If the probability be called P; the injury, L; and the burden, B;
liability depends upon whether B is less than L multiplied by
P: i.e., whether B is less than PL."
United States v. Carroll Towing (159 F.2d 169 [2d Cir. 1947]
===============================================================
Updated 1/26/04
CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of Information Network Eng. INEG. INC.
ABA member in good standing member ID 01257402 E-Mail
jwkckid1@xxxxxxxxxxxxx
My Phone: 214-244-4827
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|