[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: News from the ORSC



Roeland and all,

  Roeland, don't worry too much about Kents premature attempt to
preempt the wonderful founding of a OPEN DNSO process with
DNSO.NET.  It may be useful to understand where Kents misplaced
loyalties lie (I.E. gtld-MoU/PAB).  Enough said.

Roeland M.J. Meyer wrote:

> Well Kenty ol' boy,
>
> Thanks for stealing my thunder <frown>, I was waiting for the DNS data to
> propogate before making the official announcement. Are you trying to imply
> something with this violation of my good wishes? I certainly didn't
> authorize you to be the PR man for either ORSC or MHSC. Yes, the ORSC is an
> OPEN system. That is why this dispicable move of yours is possible. But, I
> *really* wanted to make this announcement myself. At least, you could have
> waited until the DNS had propogated.
>
> I will make a formal announcement by Monday. If anyone else wants to follow
> progress then join the ORSC list. Unlike some others, it is open to all
> whom are interested. I am currently instantiating mailer-lists for
> DNSO.NET. That job is not complete yet. Further information will be
> available in the formal announcement. As stated in this illicitly forwarded
> message, DNSO.NET will develop and distribute operational software and data
> for ISPs and others, that want localized root.zone services and data. I am
> also considering making it the home of the development of the public
> registry software project. MHSC is really an inappropriate home for that
> project.
>
> If you want to look at the web-site and your name servers haven't recieved
> the zone data yet then you can use the names servers at <DNS:NS1.MHSC.NET>
> or <IP:199.108.175.25>. It takes anywhere from 10 to 25 hours for zone data
> to propogate, throughout the Internet, on an emergency basis. The normal
> case takes much longer (days).
>
> Again, thank you Kenty for an early release, before it's ready.
>
> At 08:27 PM 12/18/98 , Kent Crispin wrote:
> >Thought you all might find this message from the ORSC list somewhat
> >interesting...
> >
> >----- Forwarded message from "Roeland M.J. Meyer" <rmeyer@mhsc.com> -----
> >
> >Date: Fri, 18 Dec 1998 11:33:49 -0800
> >To: domain-policy@open-rsc.org
> >From: "Roeland M.J. Meyer" <rmeyer@mhsc.com>
> >Subject: !Oh shit, it just got serious!
> >Reply-To: domain-policy@open-rsc.org
> >
> >As of this morning DNSO.NET is in the roots. Since Richard has DNSO.COM
> >this leaves the DNSO folk with only DNSO.ORG. Note that DNSO.COM is on HOLD
> >status, while DNSO.NET is not only active, but has a web-server attached at
> ><http://www.dnso.net>. There is also a <http://download.dnso.net>, both are
> >being run out of www.svcs.mhsc.net, and MHSC production host. This host is
> >running Apache with SSL and mod_perl extentions and I am adding server-side
> >java capability now, so we can do some really cool stuff with it,
> >web-server-wise.
> >
> >I did this primarily as a stress-reliever, I needed to do something funny
> >and light-hearted. For that purpose, personally, it worked. I had a good
> >time with it. However, there is a serious side to it as well. Those who
> >know me well, know that I *never* do something with *only* a single
> >purpose, or even just two purposes. It appears that Stef just instantiated
> >the serious side of all this.
> >
> >I had envisioned that DNSO.NET could be an operational arm of a DNSO, where
> >root.zone data is managed and distributed as well as, other network
> >operations of a DNSO. This is very much the way MHSC is organized, in that,
> >MHSC.COM is the business end and MHSC.NET is the operations end of the same
> >organization. The location of DNSO.NET can be changed with a simple DNS
> >entry so I can re-assign it anywhere I want to, if that is requested of me.
> >
> >Vaguely, what I had in mind, was distribution of basic root.zone, as
> >discussed on the IFWP list. This has value-add to the current ISP
> >community. I am RTFMing the ListServ docs now (if anyone has a better
> >suggestion for mailer-list software, I am all ears). In addition, the ORSC
> >root.zone can be distributed via a similar mechanism, rather a different
> >list. The ISP can then choose which list to join.
> >
> >Realize this also, DNSO.NET is running on a system which is using the ORSC
> >root.zone for BIND resolution. This means that ALL ORSC TLDs have access to
> >this server. In other words, DNSO.NET is INCLUSIVE by default.
> >
> >Operationally, we still have much to discuss.
> >1) We need to define operationally, what a DNSO would do.
> >2) MHSC.NET does not have the bandwidth that VRX.NET has, is this an issue?
> >3) We need to get DNSO.COM out of HOLD status now and instantiate it properly.
> >4) For the present, MHSC.NET will absorb the cost of operating DNSO.NET.
> >5) Other issues need to be presented.
> >
> >At 12:18 AM 12/18/98 , Einar Stefferud wrote:
> >>On the subject of formig a more open DNSO, I suggest that ORSC is
> >>perhaps well positioned to do so, and I strongly suggest that the ORSC
> >>version should promptly incorporate in Deleware, as that is where we
> >>know how to do it quickly and efficiently, and where we can obtain the
> >>right kind of non-profit trade association with proper accountability
> >>to its membership.  I suggest the name be "DNSO.COM, Inc."
> >
> >DNSO.NET is instantiated as "Domain Name Services Organization".
> >
> >Thank you.
> >
> >>ORSC should now lead an effort to create a set of bylaws that
> >>incorporate as much as possible from the current ORSC bylaws submitted
> >>to to NTIA as a counter to ICANN, and also meld in as much as posible
> >>from the latest DSNO.ORG draft, and also obtain recommendations from
> >>iaTLD, and other DNS/TLD groups and organizations.
> >>
> >>ORSC has experience in running open mailing lists with civil discourse
> >>rules, and we will be pleased to apply that experience here.
> >>
> >>Our objective will be to draw into this new effort all possible DNS
> >>stakeholders.
> >>
> >>Do we have any takers?  Who wants to go for it with a real outreach
> >>and effort to really pull everyone into it.
> >
> >___________________________________________________
> >Roeland M.J. Meyer -
> >e-mail:                                      mailto:rmeyer@mhsc.com
> >Internet phone:                                hawk.lvrmr.mhsc.com
> >Personal web pages:             http://staff.mhsc.com/~rmeyer
> >Company web-site:                           http://www.mhsc.com
> >___________________________________________________
> >Who is John Galt?
> >               - "Atlas Shrugged" - Ayn Rand
> >
> >----- End forwarded message -----
> >
> >--
> >Kent Crispin, PAB Chair                                "Do good, and you'll be
> >kent@songbird.com                              lonesome." -- Mark Twain
>
> ___________________________________________________
> Roeland M.J. Meyer -
> e-mail:                                      mailto:rmeyer@mhsc.com
> Internet phone:                                hawk.lvrmr.mhsc.com
> Personal web pages:             http://staff.mhsc.com/~rmeyer
> Company web-site:                           http://www.mhsc.com
> ___________________________________________________
> Who is John Galt?
>                - "Atlas Shrugged" - Ayn Rand

Regards,

--
Jeffrey A. Williams
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number:  972-447-1894
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208

S/MIME Cryptographic Signature