Re: [apnic-talk]FW: requesting hard data sources on ramifications of ver
It was recognized and reported that the Bind Patches that were
applied actually made the situation worse not better as well as
.museum is also using Wild Cards which made ICANN's threat
to sue Verisign an empty threat. ICANN had plenty of "Hard
Data" prior to the Oct. 7 meeting. It appeared that the ICANN
staff did not have adequate time to review the data it was provided
or was unable to review that data adequately as was already
publicly reported.
Verisign has reintroduced Site Finder as well, and announced the sale
or NSI...
APNIC Secretariat wrote:
> ----- Forwarded message from k claffy <kc at caida dot org> -----
>
> Date: Thu, 16 Oct 2003 12:26:15 -0700
> From: k claffy <kc at caida dot org>
> Subject: requesting hard data sources on ramifications of verisign
> wildcard
> To: nanog at nanog dot org
>
>
> as already mentioned, fascinating public policy theatre
> is going on in DC on the verisign wildcard issue, see
> http://secsac.icann.org/
> [all video and even transcripts of both meetings online. go icann.]
> you are encouraged to read through all of it before making public
> comments
> on this issue at nanog. (or, hope springs eternal, to this list.)
>
> caida has the following request on behalf of icann's secsac committee
> [an exceptionally competent group who is approaching this issue
> with impressive speed, equaniminity, and integrity.
> http://www.icann.org/committees/security/
> i believe we're in good hands here. let's give the process a chance
> and constructively contribute where we can.]
>
> a common theme over the last week is an admitted lack of hard data
> [rather than lists of theoretical breakages, and anecdotal evidence,
> and predictions] from the operational community on actual loss of
> stability in Internet performance or functionality.
> david from XO gave an outstanding talk on 7 oct,
> http://www.icann.org/presentations/shairer-secsac-dc-07oct03.ppt
> but, as with many other providers, he deployed the bind patch
> within 24 hours so he didn't really have useful hard data
> to put on the table. i get similar comments from others.
> ben from harvard also gave some hard alexa data, fwiw
> http://www.icann.org/presentations/edelman-secsac-dc-15oct03.ppt
> but from a specific vantage point. we need more of these.
>
> icann's secsac committee is in a much stronger position to
> provide technically sound and equitable guidance if we can
> provide them with as specific, concrete examples (*hard data*)
> that indicate extent of various types of breakage.
>
> please save the arguments regarding the legitimacy and short notice
> of this request until you've read the hours of discussion about
> it that has already occurred among many qualified folks in DC
> (and in any case the meta-issue still stretches AUP of nanog list).
>
> the inconvenient reality is that the secsac committee needs concrete
> data (imagine), in addition to bulleted lists of things that break,
> for the policy process to work most effectively here. and nanog is
> in a position to make a difference. you are hereby encouraged to do
> so.
>
> please send any hard data reflecting observed ramifications on
> security and stability of Internet infrastructure to
>
> secsac-comment at icann dot org
>
> no hard data will be refused service
> k
>
> ----- End forwarded message -----
>
> _______________________________________________
> apnic-talk mailing list
> apnic-talk at lists dot apnic dot net
> http://mailman.apnic.net/mailman/listinfo/apnic-talk
Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup LLA. - (Over 134k members/stakeholders strong!)
"Be precise in the use of words and expect precision from others" -
Pierre Abelard
===============================================================
CEO/DIR. Internet Network Eng. SR. Eng. Network data security
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1 at ix dot netcom dot com
Contact Number: 214-244-4827 or 214-244-3801