RE: [wg-c] Specific Implementation Proposal: [Was:Re:nineprinciplesfor domain names]

["Kevin J. Connolly" <CONNOLLK@rspab.com>]

I know because (1)  even tho' the CORE SRS is "open source," 
NSI is not stupid enough to be using that software without a
license from CORE, which it surely does not have; and (2) several
engineers who work for NSI Registrars (and who therefore have 
seen the NSI documentation) have told me the NSI software is a 
rip of someone else's software, not CORE's.  (It should be obvious
whose software they ripped, but I am not going to say it :-)

>>> "Roeland M.J. Meyer" <rmeyer@mhsc.com> 02/23/00 10:44AM >>>
So, you are saying that the NSI abomination has NOTHING to do with the
original CORE SRS? How would you know, unless you've signed the NSI NDA and
have seen the code.(Something which Kent, to his credit, refused to do).

> -----Original Message-----
> From: owner-wg-c@dnso.org [mailto:owner-wg-c@dnso.org]On Behalf Of Kevin
> J. Connolly
> Sent: Wednesday, February 23, 2000 5:08 AM
> To: wg-c@dnso.org 
> Subject: Re: [wg-c] Specific Implementation Proposal: [Was:Re:
> nineprinciplesfor domain names]
>
>
> Karl Auerbach <karl@cavebear.com> 02/23/00 12:12AM wrote:
>
> >> Since there already exists a thoroughly-tested implementation of a
> >> shared registration system
>
> >If you are referring to the thing that is used to "share" the
> NSI operated
> >registry for .com/.net/.edu, then may I suggest that it be used
> as a model
> >of "how not to do it".
>
> >From a technical perspective the current SRS design is underspecified
> >(i.e. there are parts that are not documented), inadequate (e.g. it
> >doesn't know time zones or IPv6), and it is arguably subject to
> >manipulation by less-than scrupulous registrars.
>
> >		--karl--
>
> Good God.  ROFLMAO.  It's been three years since
> I last shilled for NSI :-)  (Unpaid, at that :-)
>
> No, I'm not talking about the
> NSI abomination.  I'm talking about the CORE SRS
> which was intended (at the time I stopped
> being a CORE insider) to be open source.  I would
> not mind inserting a requirement for open source
> code as a precondition for letting *anyone* run the testbed.
> Nor, at this point, do I think that any rational participant in
> the process should object to open source code if it gets the
> fat lady onstage for the end of the first act.
>
> I do know that the CORE SRS code has been beaten
> to death by engineers seeking to . . .  well, I'm not going to
> go into the rationale of the CORE vetting process,
> escpecially since my inside info is nearly two years
> out of date; but I know the engineers who flogged
> the CORE SRS, and I don't doubt for a moment that
> the bugs have been found and fixed.  And I was
> involved, rather intimately, in the design of the anti-
> shenanigans architecture of the system.
>
> And so far as international sensitivity as opposed to
> ugly Americanism, those who are familiar with my work
> know that (a) I am an EC citizen [dual citizenship,
> actually] and (b) I pay very close attention to the needs
> of people from outside North America, even though that
> has been known to erode my political support.  I just
> happen to believe in doing things right.  Like Gabe Battista
> and Don Heath, I do not intend to participate in fouling up
> the Internet beyond all hope of redemption.
>
> Kevin J. Connolly
> The opinions expressed are those of the author, not of
> Robinson Silverman Pearce Aronsohn & Berman LLP
> This note is not legal advice.  If it were, it would come with an invoice.
> As usual, please disregard the trailer which follows.
>
> **********************************************************************
> The information contained in this electronic message is confidential
> and is or may be protected by the attorney-client privilege, the work
> product doctrine, joint defense privileges, trade secret protections,
> and/or other applicable protections from disclosure.  If the reader of
> this message is not the intended recipient, you are hereby notified
> that any use, dissemination, distribution or reproduction of this com-
> munication is strictly prohibited.  If you have received this communi-
> cation in error, please immediately notify us by calling our Help Desk
> at 212-541-2000 ext.3314, or by e-mail to helpdesk@rspab.com 
> **********************************************************************
>

**********************************************************************
The information contained in this electronic message is confidential
and is or may be protected by the attorney-client privilege, the work
product doctrine, joint defense privileges, trade secret protections,
and/or other applicable protections from disclosure.  If the reader of
this message is not the intended recipient, you are hereby notified
that any use, dissemination, distribution or reproduction of this com-
munication is strictly prohibited.  If you have received this communi-
cation in error, please immediately notify us by calling our Help Desk
at 212-541-2000 ext.3314, or by e-mail to helpdesk@rspab.com
**********************************************************************