Those guidelines apply to the second level of namespace Jeff.
There is nothing to indicate they apply to the first level.
Please try and come up with better arguments that actually apply to namespace
we are discussing.
BTW, is there a trademark filing for INEG? Any references?
A multibillion dollar company is sure to have a trademark on it's name. Two
domain names are currently registered (ineg.net and ineg.com) that INEG would
surely want to prevent others from misusing. And all it would take is a letter
from INEG to NSI to stop them. Why has INEG not done this?
On 01-Mar-99 jeff Williams wrote:
> William and all,
>
> The short answer is NO. Once a string or trademark is used in commerce
> as stated clearly in the January 16th Trademark guidelines for Domain Names
> or names use in the internet, it applies throughout.
>
> William X. Walsh wrote:
>
> > so then wouldn't the trademark apply only to the use of that string with
> > regard
> > to naming within the MHSC network and not the root zone/entire internet?
> >
> > On 01-Mar-99 Roeland M.J. Meyer wrote:
> > > At 12:35 AM 3/1/99 -0800, Bill Lovell wrote:
> > > >At 01:39 AM 2/28/99 -0800, you wrote:
> > > >
> > > > However, I acknowledge that ICANN is a different beastie than
> > > >>NSI. BTW, from a tech stand-point, I already have the TLDs running
> > > >>internally and providing service, for which I get paid. Also, the ICANN
> > > >>is
> > > >>not the sole gate-keeper of the Internet.
> > > >>
> > > >>Uh, I'm on the net whether ICANN likes it or not. Therefore your first
> > > >>"if"
> > > >>fails. Also, I don't have to state a dependency of getting into the
> > > >>root. I
> > > >>can provide the service under a private TLD and thus qualify for
> > > >>trademark
> > > >>registration. Anyone using my name servers (which include my own
> > > >>root-server cluster) can access my TLD. Now I want wider access for the
> > > >>TLD
> > > >>and I petition the ICANN for root-server inclusion. Failing there, I
> > > >>file
> > > >suit.
> > > >></hypothetical>
> > > >>
> > > >Picking out just one aspect of this bit, you say you're on the net
> > > >whether
> > > >ICANN likes it or not, but at a particular stage you are not included in
> > > >the
> > > >root server. So, who knows you're there?
> > >
> > > a.root-srvr.mhsc.net
> > > b.root-srvr.mhsc.net
> > > c.root-srvr.mhsc.net
> > > d.root-srvr.mhsc.net
> > > e.root-rvr.mhsc.net
> > >
> > > Which are indirectly available through our NS(n).MHSC.NET name server
> > > system.
> > >
> > > >Will I get your site if I enter it here from the wilds of Oregon?
> > >
> > > Yes, our name server system are available to the net. We can give
> > > selective
> > > access via routing. We do dynamic routing via gated. MHSC has an ASN
> > > with
> > > ARIN and we are multi-homed through four different up streams.
> > >
> > > >What DNS will you be on?
> > >
> > > MHSC.NET
> > >
> > > >Do you show up in anyone's whois? Which one(s)?
> > >
> > > whois.InterNIC.net
> > >
> > > >Could I email you, and you email me?
> > >
> > > That gets a little tricky. If we want to connect our private TLDs to the
> > > Internet mail system we have to do a little MX magic. This wouldn't be
> > > required if they were in the roots.
> > >
> > > >Can you get the newsgroups, download messages and upload your
> > > >own?
> > >
> > > >From inside our private TLDs, the users have full access to the
> > > >Internet.
> > > If the external hosts use the MHSC.NET name servers, or secondary their
> > > data, they can access our internal TLDs.
> > >
> > > >What if I PINGed you? etc., etc. In short, what would you have
> > > >if you were included in the root server that you don't have now?
> > >
> > > Full public name server resolution not completely dependent on MHSC.NET
> > > name servers. You must understand that the root server system is merely
> > > a
> > > lookup of other name servers. It does not provide the TLD info by
> > > itself,
> > > only the reference to the TLD root-servers. MHSC, as a TLD registry,
> > > would
> > > have to run it's own TLD root-servers, as would any other TLD registry,
> > > as
> > > does NSI.
> > >
> > > >Who would your alternative gate keeper(s) be?
> > >
> > > The NS(n).MHSC.NET name server system.
> > >
> > > >These are not smart alec questions: I just want to make sure we're
> > > >operating from the same premises. Uh, logical premises, that is. :-)
> > >
> > > Understood.
> > > ___________________________________________________
> > > Roeland M.J. Meyer -
> > > e-mail: mailto:[EMAIL PROTECTED]
> > > Internet phone: hawk.lvrmr.mhsc.com
> > > Personal web pages: http://staff.mhsc.com/~rmeyer
> > > Company web-site: http://www.mhsc.com
> > > ___________________________________________________
> > > KISS ... gotta love it!
> >
> > ----------------------------------
> > E-Mail: William X. Walsh <[EMAIL PROTECTED]>
> > Date: 01-Mar-99
> > Time: 12:46:02
> > ----------------------------------
> > "We may well be on our way to a society overrun by hordes
> > of lawyers, hungry as locusts."
> > - Chief Justice Warren Burger, US Supreme Court, 1977
>
> Regards,
>
> --
> Jeffrey A. Williams
> CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
> Information Network Eng. Group. INEG. INC.
> E-Mail [EMAIL PROTECTED]
> Contact Number: 972-447-1894
> Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
----------------------------------
E-Mail: William X. Walsh <[EMAIL PROTECTED]>
Date: 01-Mar-99
Time: 19:29:47
----------------------------------
"We may well be on our way to a society overrun by hordes
of lawyers, hungry as locusts."
- Chief Justice Warren Burger, US Supreme Court, 1977
