From Bradley@NorthTech.US Wed Jul  5 19:05:23 2006
Date: Sat, 01 Jul 2006 18:02:17 -0700
From: Bradley D. Thornton <Bradley@NorthTech.US>
To: pr@publicroot.org
Subject: Entire Archives of Public-Dash-Root on ADNS machines...

I thought that, being a private list and all, that it might best serve 
the public at large if the complete archives of the public-dash-root 
email list were moved someplace where they won't be destroyed anytime 
soon ;)

um... One more thing: Peter, I respect the hard work you have put into 
this affair too, and wanted to thank you for the assistance you and 
Karin provided Joe with during the period of time he was in exile 
following his exposure of the criminal aspects of Xennt, his IRA buddy, 
and the other public-dash-root, unidt, and inaic crooks. You're a quite 
competent DNS administrator, and hopefully we can work together at some 
point on a project that's actually worth it - that is actually going to 
make a difference, that's actually not in existence just to serve the 
vanity of someone, or their larcenous heart.

So, without further ado.... here's the public-dash-root archives in 
their entirety :)

<snip>

From jp@adns.net Sat Jan 29 13:32:10 2005
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1CuxOE-0006ma-IY
	for public-root@list.public-root.com; Sat, 29 Jan 2005 13:32:10 -0500
Received: from dhcp-pool-128.adns.net ([10.1.1.128] helo=TAKA)
	by MAIL.ADNS.NET with smtp (Exim 4.24) id 1Cuxxr-00065x-Fq
	for public-root@list.public-root.com; Sat, 29 Jan 2005 14:08:59 -0500
Message-ID: <009101c50632$e8ff15d0$8001010a@ADNSMICHIGAN.ADNS.NET>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Sat, 29 Jan 2005 12:46:57 -0600
Organization: AGN Domain Name Service, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Subject: [Public-root] Test - First Message
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sat, 29 Jan 2005 18:32:10 -0000

TEST

This is the first public-root message. 



From xennt@public-root.com Mon Feb 21 08:41:28 2005
Received: from mail.public-root.com
	([84.22.100.12] helo=mail.cyberbunker.com ident=0)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1D3DoV-00076S-GK
	for public-root@list.public-root.com; Mon, 21 Feb 2005 08:41:27 -0500
Received: from 192.168.0.63 (a84-22-100-10.dns.public-root.com [84.22.100.10])
	by mail.cyberbunker.com (8.12.10/8.12.10) with SMTP id j1LE3mHl005710
	for <public-root@list.public-root.com>; Mon, 21 Feb 2005 15:03:56 +0100
Message-Id: <200502211403.j1LE3mHl005710@mail.cyberbunker.com>
From: xennt@public-root.com
To: public-root@list.public-root.com
CC: 
X-Mailer: NeoPlanet Version: 5.2.0.1704
X-ID: 370D1916390940C4A6C00972E5C86534
X-Brand: NeoPlanet
X-Build: 1704
Subject: [Public-root] [Fwd: Re: Your Name-Space, Root Zone,
	Dns System and Legal Issues]
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: xennt@public-root.com
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
Date: Mon, 21 Feb 2005 13:41:28 -0000
X-Original-Date: 21 Feb 2005 15:02:52 +0100
X-List-Received-Date: Mon, 21 Feb 2005 13:41:28 -0000

We have been noticed by the market. You are all root-operators and no helpdesk.

Please tell Mr. Ali that you are not the right person to direct questions to.
Please suggest him to direct all questions to:  support@inaic.com

Regards,
Xennt

> Hello,
> 
> I find your mission to break free from the legacy
> Name-Space and Root Zone very
> revolutionary. I may join you so some of your
> Name-Space traffic load is
> managed by my server(s) but before I join you I must
> make sure that I know
> about the legal issues and so I would really
> appreciate if you can answer my
> following questions so that I know that I will not be
> falling in trouble with any laws
> of the world.
> 
> Kindly put each of your answers below each of my basic
> questions and then hit the REPLY button.
> This way, you will never miss a question out.
> Also, can you please put my questions (with-out
> putting any references to me)
> up on your website so others, who are new to Alternate
> name-Spaces like me,
> will not bother you again with the same questions.
> 
> Question 1. If I want to operate and run (host) my own
> TLDs and sell or give-away
> 2nd level domain name registrations where you will
> support it on your Root Zone and Name-Space
> then what steps must I take ? Please understand that I
> am not talking about running my own
> Root Zone or Name-Space but am talking about how to
> get you to support it.
> 
> Question 2. Is the DNS system and all or some of it'
> protocols patented or patent
> pending, which will cause you trouble running your own
> Name-Space, Root Zone and TLDs ?
> Can the inventors of these protocols patent their
> invented protocols to
> cause you trouble so that only the legacy
> name-space/legacy registry can operate the
> Name-Space, Root Zone and TLDs or make you start
> paying them up royalties ?
> If so, does that mean, the whole internet will come to
> die if no-one pays
> them royalties?
> 
> Question 3. Who owns the Internet Back-Bone, it'
> protocols, it' DNS system etc. ?
> Or are all this public owned or free from ownership?
> If so, then cannot anybody ever put claim to them to
> own them?
> Can you put claim on any part of the internet? If so,
> then which part(s) ?
> 
> Question 4. Is it illegal for you to compete with the
> legacy Domain-Name Space
> /legacy registry because the USA government owns it or
> used to?
> 
> Question 5. Has the USA government only given license
> to the legacy Name-Space
> /legacy registry to
> create Top Level Domain Names or TLDs to register
> domain names? Which
> means you are acting illegally?
> Does this legacy Name-Space/legacy registry only have
> the Rights to create TLDs and register
> domains with their own invented/created TLDs? If so,
> then are you running
> secretly and illegally?
> 
> Question 6. What happens, when some public
> organisations and private companies like you pops-up
> and
> creates their own Name-Space, Root Zone, TLDs and
> starts creating TLDs and
> registering domain names with those TLDs for their own
> personal/commercial
> use or starts charging the general public to register
> domain names with
> their newly created TLDs (where the members become
> free from the legacy Domain Name-Space/
> legacy registry) and the legacy Name-Space/legacy
> registry loses business because of the new
> competition ? Would these actions of the new
> competitor be illegal according to USA, UK, European
> Union and
> International laws?
> What would happen to you for snatching or damaging the
> legacy Name-Space
> /legacy registry's business?
> Can they drag you and your members to court or sue
> you?
> 
> Question 7. Is the European Union, or UK or any
> Nations of the earth in some kind
> of contract/agreement with the USA government or the
> legacy Domain Name-Space/legacy registry
> that no nation should allow any of it's cititzens
> (individuals, companies,
> organisations, clubs, public) to compete with the
> legacy Name-Space/legacy registry
> by creating new Name-Spaces, Root Zones and TLDs to
> register domain names?
> 
> Question 8. If any
> individual/group/club/company/organisation etc. decide
> that they
> have had enough of the legacy Name-Space/legacy
> registry and decide to launch their own private profit
> or non-progit
> or public Name-Space, Root Zone (like you have) where
> they will be creating and
> hosting new TLD(s) and selling domain names or giving
> away for free to
> certain
> individuals/groups/clubs/companies/organisations etc
> or even to the general public
> then would this new Name-Space, Root Zone, TLD(s)
> founders need to obtain permissions before
> they can launch their own Name-Space, Root Zone and
> TLD/s from any or some or all of the following:
> 
>  The Internet Engineering Task Force (IETF), The
> Internet Engineering
>  Steering Group (IESG), Internet Architecture Board,
> (IAB), The National
>  Science Foundation (NSF), The Internet Society (ISOC)
> The Internet
>  Research Task Force (IRTF), The Internet Assigned
> Numbers Authority
>  (IANA), The Internet Corporation for Assigned Names
> and Numbers (ICANN) ?
> 
> Or is it that obtaining permission from these is not
> necessary atall as
> these ones mentioned above are related to legacy
> Name-Space/legacy registry and are not part of
> any legal entity or government body?
> If this is the case, then from where did you obtain
> permission and license
> to launch and run your own Names-Space, Root Zone and
> TLDs
> legally so you do not end-up in court or behind bars
> or get
> prosecuted or have to pay heavy fines/compensation ?
> 
> Question 9. How do you know what policies of your
> Name-Space, Root Zone and TLDs are
> legal and what is illegal?
> 
> Question 10. Each time you make a policy, is it really
> necessary by law for you to
> go to some legal body in order for them to review that
> your new policies
> are legal? If so, then who are these body/bodies? And
> do you have to go to
> other non-government bodies too such as your Telephone
> Network Provider
> (TNP) and Internet Service Provider (ISP), Point of
> Presence (POPs)
> providers, Network Access Points (NAPs) providers
> (Internet Back-Bone
> providers), or even those who invented the internet
> protocols or DNS
> system and it' protocols because you are using their
> resources?
> 
> Question 11. What were, are the legal requirements for
> you to start and run your
> Name-Space, Root Zone and TLDs with your own newly
> invented/created TLDs for
> non-commercial/profit purposes and commercial/profit
> purposes ?
> 
> Question 12. What legal processes did you go thru
> before you launched/started/opened
> your Name-Space/Root Zone to set-up and run your own
> /invented created
> TLDs? If none, then do you have to go thru some now or
> in the near or
> distant future?
> 
> Question 13. What legal on-going processes (if any)
> are you bound by while you are
> running your Name-Space, Root Zone to host your own
> invented/created TLDs
> and host 2nd level domains and subdomains under those
> TLDs ?
> 
> Question 14. What legal duties, responsibilitites,
> liabilities, etc. are you bound
> by before, after and while you running your own
> Name-Space, Root Zone to
> host your own invented/created TLDs aswell as host 2nd
> level domains and
> subdomains under those TLDs ?
> 
> Question 15. What government and non-government
> bodies/organisations did you need to
> inform regarding your Name-Space, Root Zone and TLDs
> where you run or will be hosting your own
> created TLDs? Did you need to inform them before you
> launch/start/open
> your Name-Space/Root Zone or only afterwards ?
> 
> Question 16. Did you need to obtain any normal or
> special type of License, from the
> government, TNPs, ISPs, POPs, NAPs, or even those who
> invented the
> internet protocols or DNS system and it's protocols
> etc. to launch and run
> your own Name-Space, Root Zone to host your own
> invented/created TLDs
> and host 2nd level domains and subdomains under those
> TLDs ?
> 
> Question 17. Which government/non-government bodies
> are governing you how to start
> and run your Name-Space, Root Zone, TLDs and 2nd level
> domains and subdomains under those TLDs ?
> Is it the TNPs ?, ISPs ?, POPs ?, NAPs ? or even
> those who invented the internet protocols or DNS
> system and it's protocols,
> etc. ? Which ones ?
> Whose Terms & Conditions, Rules & Regulations, etc.
> are you abiding by and
> have to abide by ?
> Do you have to abide by every single one of their's if
> there are more than one or can
> you just abide by any single one's as that single one
> will cover for all the rest ?
> 
> Question 18. Did you need to insure your
> Name-Space/Root Zone where you host your
> own invented/created TLDs? If so, then which parts?
> 
> Question 19. Or are you free from any
> States/Country/Region/Continent laws because
> you are trading on the Internet where no law of any
> State/Country/Region/Continent has any real authority
> over the internet ?
> 
> 
> Thank You very much
> 
> Regards
> 
> I. Ali
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___________________________________________________________
> ALL-NEW Yahoo! Messenger - all new features - even more fun!
> http://uk.messenger.yahoo.com
> 
> 


>** --------- End Original Message ----------- **

> 




>** --------- End Original Message ----------- **

> 




>** --------- End Original Message ----------- **

> 





From jp@adns.net Mon Feb 28 12:40:00 2005
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1D5osC-0005FD-17
	for public-root@list.public-root.com; Mon, 28 Feb 2005 12:40:00 -0500
Received: from [192.234.136.23] (helo=JPALMERWINXP)
	by MAIL.ADNS.NET with smtp (Exim 4.24) id 1D5pYn-0006RI-U9
	for public-root@list.public-root.com; Mon, 28 Feb 2005 13:24:01 -0500
Message-ID: <018701c51dbf$9ad50d20$5919d797@JPALMERWINXP>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Mon, 28 Feb 2005 12:01:32 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0184_01C51D8D.3E30D8B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Subject: [Public-root] New Target date?
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2005 17:40:00 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0184_01C51D8D.3E30D8B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

When is the new target date for the publicity? Tommorrow?=20
I know it was postponed due to WHOIS issues.

John
------=_NextPart_000_0184_01C51D8D.3E30D8B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>When is the new target date for the publicity? =
Tommorrow?=20
</FONT></DIV>
<DIV><FONT size=3D2>I know it was postponed due to WHOIS =
issues.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>John</FONT></DIV></BODY></HTML>

------=_NextPart_000_0184_01C51D8D.3E30D8B0--


From jp@adns.net Mon Feb 28 12:43:00 2005
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1D5ov6-0005FV-Is
	for public-root@list.public-root.com; Mon, 28 Feb 2005 12:43:00 -0500
Received: from [192.234.136.23] (helo=JPALMERWINXP)
	by MAIL.ADNS.NET with smtp (Exim 4.24) id 1D5pbi-0006RU-Qw
	for public-root@list.public-root.com; Mon, 28 Feb 2005 13:27:02 -0500
Message-ID: <019201c51dc0$06a218e0$5919d797@JPALMERWINXP>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Mon, 28 Feb 2005 12:04:32 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_018F_01C51D8D.AA00F1B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Subject: [Public-root] None of the other root operators on the list
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2005 17:43:00 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_018F_01C51D8D.AA00F1B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Just noticed that you and I  are the only ones on this list.
None of the other root operators have joined!!!

I think people are confused because we initially had one list and
now we have two - one public and one for root-operators only.

Xennt - can you ask all of them to join this list??

John
------=_NextPart_000_018F_01C51D8D.AA00F1B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1479" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Just noticed that you and I&nbsp; are the only ones =
on this=20
list.</FONT></DIV>
<DIV><FONT size=3D2>None of the other root operators have =
joined!!!</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I think people are confused because we initially had =
one list=20
and</FONT></DIV>
<DIV><FONT size=3D2>now we have two - one public and one for =
root-operators=20
only.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Xennt - can you ask all of them to join this=20
list??</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>John</FONT></DIV></BODY></HTML>

------=_NextPart_000_018F_01C51D8D.AA00F1B0--


From peter@peter-dambier.de Tue Mar 08 17:51:19 2005
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by LAIR.LIONPOST.NET with smtp (Exim 4.24) id 1D8nXr-0000Vm-4x
	for public-root@list.public-root.com; Tue, 08 Mar 2005 17:51:19 -0500
Received: (qmail 20773 invoked by uid 0); 8 Mar 2005 23:13:30 -0000
Received: from 217.88.218.182 by www18.gmx.net with HTTP;
	Wed, 9 Mar 2005 00:13:30 +0100 (MET)
Date: Wed, 9 Mar 2005 00:13:30 +0100 (MET)
From: "Peter & Karin Dambier" <peter@peter-dambier.de>
To: public-root@list.public-root.com
MIME-Version: 1.0
References: <25797.1110291967@www47.gmx.net>
X-Priority: 3 (Normal)
X-Authenticated: #8956597
Message-ID: <6034.1110323610@www18.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: [Public-root] This is IASON-5 digging DNS-servers
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2005 22:51:19 -0000

Hello,

I hope you have not noticed somebody digging your root-server.
If you have, chance is good this was IASON testing consistency.

Sorry my IP is constantly changeing. You can find me nevertheless.
My personal system can be found via www.no-ip.com

echnaton.serveftp.com

or just finger the suspect system. IASON will reply:

This is IASON-5 digging DNS-servers.

Please visit my homepage:  http://www.inaic/index.php?p=iason

If that fails please visit:  http://www.inaic.com/

  2005-03-08 (67) 14:33:20 loc
  2005-03-08 (67) 13:33:20 UTC


I try to keep digs more then 10 seconds apart. So it should not
disrupt servervices.

The only services echnaton.serveftp.com shows to the outside are my
DNS-server and finger.

Regards
Peter

-- 
Peter und Karin Dambier 
Graeffstrasse 14 
D-64646 Heppenheim 
+49-6252-671788 (Telekom) 
+49-6252-599091 (O2 Genion) 
+49-6252-750308 (Sipgate VoIP)
peter@peter-dambier.de 
www.peter-dambier.de
peter-dambier.site.voila.fr

-- 
Peter und Karin Dambier 
Graeffstrasse 14 
D-64646 Heppenheim 
+49-6252-671788 (Telekom) 
+49-6252-599091 (O2 Genion) 
+49-6252-750308 (Sipgate VoIP)
peter@peter-dambier.de 
www.peter-dambier.de
peter-dambier.site.voila.fr


From baptista@public-root.com Tue Mar 08 21:12:23 2005
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep3.cogeco.net)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1D8qgR-00014w-1I
	for public-root@list.public-root.com; Tue, 08 Mar 2005 21:12:23 -0500
Received: from pmg.dot-god.com (d235-144-209.home1.cgocable.net
	[24.235.144.209])
	by fep3.cogeco.net (Postfix) with ESMTP id 4E067662D
	for <public-root@list.public-root.com>;
	Tue,  8 Mar 2005 21:35:08 -0500 (EST)
From: Joe Baptista <baptista@public-root.com>
Organization: The Public Root
Date: Tue, 8 Mar 2005 22:14:36 -0500
User-Agent: KMail/1.5
To: "General Discussions Public-Root" <public-root@list.public-root.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503082214.36327.baptista@public-root.com>
Subject: [Public-root] FYI: INAIC Telephone System Upgrades
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Wed, 09 Mar 2005 02:12:23 -0000


The INAIC Telephone System will be upgraded tonight and switched to a new
 high speed data center.  The upgrades and switching of the phone system at
 +1-360-226-6583 will be effective at 10:00 PM EST.

There maybe a temporary outage which will last about 2 hours during the
testing phase.  If all goes well the system will be operational by midnight
EST.

Regards
Joe Baptista




From baptista@public-root.com Thu Mar 17 20:53:14 2005
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep6.cogeco.net)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DC6fq-0006Vg-AP
	for public-root@list.public-root.com; Thu, 17 Mar 2005 20:53:14 -0500
Received: from pmg.dot-god.com (d235-144-209.home1.cgocable.net
	[24.235.144.209]) by fep6.cogeco.net (Postfix) with ESMTP id 4F62BB67
	for <public-root@list.public-root.com>;
	Thu, 17 Mar 2005 21:16:41 -0500 (EST)
From: Joe Baptista <baptista@public-root.com>
Organization: The Public Root
Date: Thu, 17 Mar 2005 21:16:35 -0500
User-Agent: KMail/1.5
To: "General Discussions Public-Root" <public-root@list.public-root.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503172116.35786.baptista@public-root.com>
Subject: [Public-root] FYI New Internet-Drafts related to the DNS
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2005 01:53:14 -0000


Dear Public-Root Operators and other interested parties:

>From time to time I will be publishing here lists of Internet-Drafts related 
to the DNS in an effort to keep us up to date on developments in the DNS.

These new Internet-Drafts related to the DNS are available from the on-line 
Internet-Drafts directories at the IETF.  Please see below.

-----------------------------------------------------------------------------
	Title		: Service Discovery using NAPTR records in DNS
	Author(s)	: S. Yamamoto, et al.
	Filename	: draft-yamamoto-naptr-service-discovery-01.txt
	Pages		: 0
	Date		: 2005-2-22

This document describes a method to store and retrieve local
   configuration information from the DNS using NAPTR records in the
   reverse path DNS tree.  It works for both IPv4 in-addr.arpa and IPv6
   ip6.arpa.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-yamamoto-naptr-service-discovery-01
.txt

-----------------------------------------------------------------------------
	Title		: Encouraging the use of DNS IN-ADDR Mapping
	Author(s)	: D. Senie
	Filename	: draft-ietf-dnsop-inaddr-required-06.txt
	Pages		: 7
	Date		: 2005-2-22

Mapping of addresses to names has been a feature of DNS. Many sites,
implement it, many others don't. Some applications attempt to use it
as a part of a security strategy. The goal of this document is to
encourage proper deployment of address to name mappings, and provide
guidance for their use.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-inaddr-required-06.txt

-----------------------------------------------------------------------------
	Title		: DNSSEC Hash Authenticated Denial of Existence
	Author(s)	: B. Laurie, et al.
	Filename	: draft-ietf-dnsext-nsec3-01.txt
	Pages		: 18
	Date		: 2005-2-22

The DNS Security (DNSSEC) NSEC resource record (RR) is intended to be
   used to provide authenticated denial of existence of DNS ownernames
   and types; however, it permits any user to traverse a zone and obtain
   a listing of all ownernames.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsext-nsec3-01.txt

-----------------------------------------------------------------------------
	Title		: DNS authoritative server misconfiguration and
			  a countermeasure in resolver
	Author(s)	: K. Fujiwara, et al.
	Filename	: draft-fujiwara-dnsop-bad-dns-auth-02.txt
	Pages		: 10
	Date		: 2005-2-23

This memo describes misconfigurations of DNS authoritative name
   server and its effect of increasing the load in DNS resolver server.
   In some cases we recommend re-checking DNS authoritative servers with
   a viewpoint of current RFC and point tough DNS resolver server
   implementation requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-fujiwara-dnsop-bad-dns-auth-02.txt

-----------------------------------------------------------------------------
	Title		: IPv6 Host Configuration of DNS Server Information Approaches
	Author(s)	: J. Jeong
	Filename	: draft-ietf-dnsop-ipv6-dns-configuration-05.txt
	Pages		: 26
	Date		: 2005-2-21

This document describes three approaches for IPv6 recursive DNS
   server address configuration.  It details the operational
   attributes of three solutions: RA option, DHCPv6 option, and
   Well-known anycast addresses for recursive DNS servers.
   Additionally, it suggests four deployment scenarios considering
   multi-solution resolution.  Therefore, this document will give the
   audience a guideline for IPv6 DNS configuration to select the
   approaches suitable for their host DNS configuration.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dnsop-ipv6-dns-configuration-0
5.txt

-------------------------------------------------------



From jp@adns.net Sat Mar 19 12:12:45 2005
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DChVF-0005PG-V9
	for public-root@list.public-root.com; Sat, 19 Mar 2005 12:12:45 -0500
Received: from 24-148-29-239.mart-bsr1.chi-mart.il.cable.rcn.com
	([24.148.29.239] helo=TAKA) by MAIL.ADNS.NET with smtp (Exim 4.24)
	id 1DCiGp-0006KF-Ht
	for public-root@list.public-root.com; Sat, 19 Mar 2005 13:01:55 -0500
Message-ID: <016c01c52caa$0ceae3f0$64904002@ADNSMICHIGAN.ADNS.NET>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Sat, 19 Mar 2005 11:35:01 -0600
Organization: AGN Domain Name Service, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Subject: [Public-root] Status of Marketing/Visibility Efforts
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2005 17:12:46 -0000

For operational planning: What are the plans for the big PR push to get 
ISP's and others to use Public-Root?

I have not seen an appreciable increase in traffic to g.public-root
since the announcement that a PR blitz was in the works. This was
supposed to start mid-January and was delayed till March 1st. 

Since then, no news. Also, rumor has it that an entire nation will
require their ISPs to resolve Public-Root. 

Could we get a timeline on all of this and perhaps more detailed plans? 
Planning on the operational side needs to be done. 

John


From baptista@public-root.com Fri Mar 25 06:49:45 2005
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep4.cogeco.net)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DEnJx-0005XS-6P
	for public-root@list.public-root.com; Fri, 25 Mar 2005 06:49:45 -0500
Received: from pmg.dot-god.com (d235-144-209.home1.cgocable.net
	[24.235.144.209])
	by fep4.cogeco.net (Postfix) with ESMTP id 8E2C34CD7
	for <public-root@list.public-root.com>;
	Fri, 25 Mar 2005 07:13:48 -0500 (EST)
From: Joe Baptista <baptista@public-root.com>
Organization: The Public Root
To: "General Discussions Public-Root" <public-root@list.public-root.com>
Date: Fri, 25 Mar 2005 07:13:38 -0500
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503250713.39361.baptista@public-root.com>
Subject: [Public-root] FYI New Internet-Drafts related to the DNS
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2005 11:49:45 -0000


Dear Public-Root Operators and other interested parties:

>From time to time I will be publishing here lists of Internet-Drafts related 
to the DNS in an effort to keep us up to date on developments in the DNS.

These new Internet-Drafts are available from the on-line Internet-Drafts 
directories at the IETF.  Please see below.

======================================================================

This draft is a work item of the IP Version 6 Working Group Working Group of 
the IETF.

	Title		: IP Version 6 Addressing Architecture
	Author(s)	: R. Hinden, S. Deering
	Filename	: draft-ietf-ipv6-addr-arch-v4-02.txt
	Pages		: 25
	Date		: 2005-3-24
	
This specification defines the addressing architecture of the IP
   Version 6 protocol [IPV6].  The document includes the IPv6 addressing
   model, text representations of IPv6 addresses, definition of IPv6
   unicast addresses, anycast addresses, and multicast addresses, and an
   IPv6 node's required addresses.

   This document obsoletes RFC-3513 "IP Version 6 Addressing
   Architecture".

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-addr-arch-v4-02.txt

======================================================================



From baptista@public-root.com Tue Mar 29 03:00:42 2005
Received: from smtp.cogeco.net ([216.221.81.25] helo=fep6.cogeco.net)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DGBeU-0005dH-J0
	for public-root@list.public-root.com; Tue, 29 Mar 2005 03:00:42 -0500
Received: from pmg.dot-god.com (d235-144-209.home1.cgocable.net
	[24.235.144.209]) by fep6.cogeco.net (Postfix) with ESMTP id 4DC498F8
	for <public-root@list.public-root.com>;
	Tue, 29 Mar 2005 03:25:06 -0500 (EST)
From: Joe Baptista <baptista@public-root.com>
Organization: The Public Root
To: "General Discussions Public-Root" <public-root@list.public-root.com>
Date: Tue, 29 Mar 2005 03:24:55 -0500
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503290324.55850.baptista@public-root.com>
Subject: [Public-root] Information and reference for IPv6 Network
	Administration
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2005 08:00:42 -0000

Hello:

Thos on the list involved in IPv6 development efforts may be interested in 
this information and reference manual for IPv6 Network Administration by 
O'Reilly.

regards
joe

IPv6 Network Administration
From: O'Reilly Media <elists-admin@oreillynet.com>

"IPv6 Network Administration" (O'Reilly) offers administrators the
complete inside info on IPv6. This book reveals the many benefits as well
as the potential downsides of this next-generation protocol. It also shows
you exactly how to set up and administer an IPv6 network.

The book is coauthored by Niall Richard Murphy and David Malone.  Malone
is a mathematician and Murphy is a specialist in IP services and next
generation networking.  Murphy played a role in getting global IPv6
address allocation policies changed a few years ago, which has helped pave
the way for IPv6 to replace the current protocol, IPv4.

"IPv6 Network Administration" delivers an even-handed approach to what
will be the most fundamental change to the Internet since its inception.
Some of the IPv6 assets that are covered include:

-routing
-integrated auto-configuration
-quality of service
-enhanced mobility
-end-to-end security

This book explains what works, what doesn't, and most of all, what's
practical when considering upgrading networks from the current protocol to
IPv6.

"'IPv6 Network Administration' is an excellent practical guide to IPv6,
with plenty of real-world examples that have served me as useful reference
material, as well as great primer when introducing people to IPv6." 
--Colm MacCarthaigh, Apache Contributor (particularly IPv6)

To order your copy or for more information, see:
http://www.oreilly.com/catalog/ipv6na/
or call 1-800-998-9938
or email orders@oreilly.com

IPv6 Network Administration
Niall Murphy, David Malone
Publisher: O'Reilly 
ISBN: 0-596-00934-8, 306 pages, $44.95 US, $62.95 CA
http://www.oreilly.com/catalog/ipv6na/



From peter@peter-dambier.de Sat May 07 02:58:24 2005
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by LAIR.LIONPOST.NET with smtp (Exim 4.24) id 1DUJGZ-00005q-SV
	for public-root@list.public-root.com; Sat, 07 May 2005 02:58:24 -0400
Received: (qmail 26849 invoked by uid 0); 4 May 2005 09:38:22 -0000
Received: from 84.167.192.26 by www4.gmx.net with HTTP;
	Wed, 4 May 2005 11:38:22 +0200 (MEST)
Date: Wed, 4 May 2005 11:38:22 +0200 (MEST)
From: "Peter & Karin Dambier" <peter@peter-dambier.de>
To: discussions@list.inaic.com
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-Authenticated: #8956597
Message-ID: <30219.1115199502@www4.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Cc: public-root@list.public-root.com
Subject: [Public-root] Have you noticed EU in the root zone?
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sat, 07 May 2005 06:58:24 -0000

Sorry to post this in both lists,

but I need to reach you!

Between dawn und dust on friday afternoon 2005-04-29
the new country? toplevel domain "EU" appeared in
the ICANNed root-zone like a Loup Garraux out of the
night.

At the very same time "EURid.org" vanished from all
but the ICANNed roots. The Loup Garraux has got it?

All that is left from "EURid.org" is a redirection
to "EURid.eu" that leads to the lost continent of
Atlantis down in the Atlantic Ocean between Europe
and the Americas.

Thank Xennt it took only minutes to bring "EURid"
back to live in the Public-Root.

But I am sorry for all those roots I could not inform
because of badly configured mail blockers (spam filters).
I you can contact them please inform them.

Regards,
Peter Dambier
Public Root
http://iason.site.voila.fr
http://www.kokoom.com/iason

-- 
Peter und Karin Dambier 
Graeffstrasse 14 
D-64646 Heppenheim 
+49-6252-671788 (Telekom) 
+49-6252-599091 (O2 Genion) 
+1-360-226-6583-9738 (INAIC)
peter@peter-dambier.de 
www.peter-dambier.de
peter-dambier.site.voila.fr


From peter@peter-dambier.de Mon May 16 10:58:21 2005
Received: from p54a7c1d7.dip.t-dialin.net ([84.167.193.215]
	helo=echnaton.peter-dambier.de)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DXh2z-00076G-6G
	for public-root@list.public-root.com; Mon, 16 May 2005 10:58:21 -0400
Received: from root by echnaton.peter-dambier.de with local (Exim 4.40)
	id 1DXhAV-0001bz-8D
	for public-root@list.public-root.com; Mon, 16 May 2005 17:06:07 +0200
To: public-root@list.public-root.com
Message-Id: <E1DXhAV-0001bz-8D@echnaton.peter-dambier.de>
From: root <root@echnaton.serveftp.com>
Date: Mon, 16 May 2005 17:06:07 +0200
Subject: [Public-root] SPAMMING what to do?
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2005 14:58:21 -0000

Dear Public-Root Operators and other interested parties:

One of my email addresses has been missued by spammers for
political propaganda. It has been my name and my address.
It has not been my computer nor my mailer.

The adverticed server is

> natnum globalfire.tv

host_look("216.24.175.30","globalfire.tv","3625496350").
host_name("216.24.175.30","www.delta.rietta.com").


I have informed both my isp and the police. As it is about
NAZIs adverticing the german police dont take it likely.

Nevertheless I might need good advice.

Down is the message from mailer that "bounced" at me.
You may exchange *** for a lot of user names. I seems to have
been sent only to this domain but I did not see the messages
that arrived.

Regards,
Peter Dambier
Public-Root

--- Messages from foreign mailer ---
Von: Mail Delivery System <Mailer-Daemon@mx00.bcc.de>
An: dl2fba@peter-dambier.de
Betreff: Mail delivery failed: returning message to sender
Datum: Sun, 15 May 2005 20:56:00 +0200

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  ***@family-newsletter.de
    SMTP error from remote mailer after RCPT
TO:<***@family-newsletter.de>:
    host mail.gerstenberg-direkt1.de [213.252.161.84]:
    550 Unknown local part *** in <***@family-newsletter.de>

------ This is a copy of the message, including all the headers. ------

Return-path: <dl2fba@peter-dambier.de>
Received: from pd9eefe57.dip0.t-ipconnect.de ([217.238.254.87]
helo=panqwvmtg.de)
        by mx00.bcc.de with smtp (Exim 4.43)
        id 1DXOHP-00089s-IQ; Sun, 15 May 2005 20:55:59 +0200
From: dl2fba@peter-dambier.de
To: Gerd.Graus@family-newsletter.de
Date: Sun, 15 May 2005 18:55:19 UTC
Subject: Deutsche werden kuenftig beim Arzt abgezockt
Importance: Normal
X-Mailer: Outlook 6.54
X-Priority: 3 (Normal)
MIME-Version: 1.0
Message-ID: <9f3e733f4e.dbf46fb9b@family-newsletter.de>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"



From jp@adns.net Sat Jun 11 16:29:24 2005
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DhCbc-00007d-0I
	for public-root@list.public-root.com; Sat, 11 Jun 2005 16:29:24 -0400
Received: from dhcp-pool-128.adns.net ([10.1.1.128] helo=TAKA)
	by MAIL.ADNS.NET with smtp (Exim 4.24) id 1DhDQQ-0001Ot-Ux
	for public-root@list.public-root.com; Sat, 11 Jun 2005 17:21:54 -0400
Message-ID: <007201c56ec5$aaf87730$8001010a@ADNSMICHIGAN.ADNS.NET>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Sat, 11 Jun 2005 15:38:57 -0500
Organization: AGN Domain Name Service, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Subject: [Public-root] AXFR Address 
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sat, 11 Jun 2005 20:29:24 -0000


What is the correct address from which to AXFR the root zone? There has recently been confusion
about this question. At this time, we have the following configuration:

        zone "." {
                type slave;
                file "xxxxxx";
                masters { 205.189.71.2; 57.67.193.189; };
        };

Is this the correct order? Should we have additional servers?  There was an 80.x.x.x or 81.x.x.x address that
was given about 6 months ago and this address apparently had a stale root zone that was never being updated.

We need a technical coordinator who can make such announcements to the root operator community so that
we can be sure to have the right root zone at all times.

John




From peter@peter-dambier.de Sat Jun 11 18:25:51 2005
Received: from p54a7b5d0.dip.t-dialin.net ([84.167.181.208]
	helo=echnaton.peter-dambier.de)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DhEQJ-0000T0-7n
	for public-root@list.public-root.com; Sat, 11 Jun 2005 18:25:51 -0400
Received: from lumbamba.niflheim ([192.168.208.226] helo=echnaton.serveftp.com)
	by echnaton.peter-dambier.de with esmtp (Exim 4.40)
	id 1DhEQJ-00029C-W4; Sun, 12 Jun 2005 00:25:52 +0200
Message-ID: <42AB64E7.1060602@echnaton.serveftp.com>
Date: Sun, 12 Jun 2005 00:25:43 +0200
From: Peter Dambier <peter@echnaton.serveftp.com>
Organization: Public-Root
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040921
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Palmer <jp@adns.net>
Subject: Re: [Public-root] AXFR Address
References: <007201c56ec5$aaf87730$8001010a@ADNSMICHIGAN.ADNS.NET>
In-Reply-To: <007201c56ec5$aaf87730$8001010a@ADNSMICHIGAN.ADNS.NET>
X-Enigmail-Version: 0.76.8.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Joe Baptista <joe@public-root.com>, Xennt <xennt@xennt.com>,
	public-root@list.public-root.com, Hans Bakker <hans@public-root.com>,
	Cytrax Cytrax <cytrax@public-root.com>
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: peter@peter-dambier.de
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sat, 11 Jun 2005 22:25:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Palmer wrote:
| What is the correct address from which to AXFR the root zone? There has recently been confusion
| about this question. At this time, we have the following configuration:
|
|         zone "." {
|                 type slave;
|                 file "xxxxxx";
|                 masters { 205.189.71.2; 57.67.193.189; };
|         };
|
| Is this the correct order? Should we have additional servers?  There was an 80.x.x.x or 81.x.x.x address that
| was given about 6 months ago and this address apparently had a stale root zone that was never being updated.
|
| We need a technical coordinator who can make such announcements to the root operator community so that
| we can be sure to have the right root zone at all times.
|
| John
|
|
|
| _______________________________________________
| Public-root mailing list
| Public-root@list.public-root.com
| http://list.public-root.com/mailman/listinfo/public-root
|


Hi John,

you have choosen

host_name("205.189.71.2","a.public-root.net").
host_alias("a.root-servers.public-root.net","a.public-root.net").
host_alias("a.root-servers.newroot.com","a.public-root.net").
host_alias("Amsterdam","a.public-root.net").

and

host_name("57.67.193.189","a.public-root.old").
host_alias("Amsterdam.old","a.public-root.old").

both servers give you a good Public-Root.zone .

My first guess would be

host_name("84.22.100.2","master.public-root.net").
host_alias("master.root-servers.public-root.net","master.public-root.net").
host_alias("master.public-root.net","master.public-root.net").

.  SOA   a.public-root.net. hostmaster.public-root.net. 2005061118

;; Query time: 127 msec
;; SERVER: 84.22.100.2#53(84.22.100.2)
;; WHEN: Sat Jun 11 23:53:25 2005

You can have 3 or more masters.
But that is not the official answer

Regards,
Peter Dambier
- --
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-6252-599091 (O2 Genion)
+1-360-226-6583-9738 (INAIC)
mail: peter@peter-dambier.de
http://iason.site.voila.fr
http://www.kokoom.com/iason
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFCq2TfPGG/Vycj6zYRArjUAJ45d3tHwp3S2QcXIh+FJB75lTQN3wCfQbpU
sPEVPBH94sntS32/eeSL9uo=
=Wy5P
-----END PGP SIGNATURE-----



From peter@peter-dambier.de Wed Jun 15 12:09:55 2005
Received: from p54a7c58a.dip.t-dialin.net ([84.167.197.138]
	helo=echnaton.peter-dambier.de)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1DiaSh-0000CQ-1u
	for Public-root@list.public-root.com; Wed, 15 Jun 2005 12:09:55 -0400
Received: from lumbamba.niflheim ([192.168.208.226] helo=echnaton.serveftp.com)
	by echnaton.peter-dambier.de with esmtp (Exim 4.40)
	id 1Diacd-0000So-DW
	for Public-root@list.public-root.com; Wed, 15 Jun 2005 18:20:11 +0200
Message-ID: <42B0553A.7030209@echnaton.serveftp.com>
Date: Wed, 15 Jun 2005 18:20:10 +0200
From: Peter Dambier <peter@echnaton.serveftp.com>
Organization: Public-Root
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040921
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Public-root@list.public-root.com
Subject: re: Re: [Public-root] AXFR Address
X-Enigmail-Version: 0.76.8.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Cytrax <cytrax@public-root.com>, peter@echnaton.serveftp.com
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Wed, 15 Jun 2005 16:09:55 -0000

*Hi all

All root-servers should slave the root zone file from the master root
(84.22.100.2).

zone "."   { type slave; file "Public-Root.zone"; masters { 84.22.100.2;
}; };

In the past I've asked root operators to slave from the a-root because
the IP-range
in the bunker was suddenly changed, unannounced and should change
another time
while the ip# of the a-root was stable.
Now the bunker IP-range is stable too and the master-root should be used
to slave
from.

regards

Cytrax
*
 > ** Original Subject: Re: [Public-root] AXFR Address
 > ** Original Sender: Peter Dambier <>peter@peter-dambier.de>
<mailto:peter@peter-dambier.de>
 > ** Original Date: Sun, 12 Jun 2005 00:50:03 +0200

 > ** Original Message follows...

 >

 > John Palmer wrote:
 > | What is the correct address from which to AXFR the root zone? There
 > has recently been
 > confusion
 > | about this question. At this time, we have the following configuration:
 > |
 > |         zone "." {
 > |                 type slave;
 > |                 file "xxxxxx";
 > |                 masters { 205.189.71.2; 57.67.193.189; };
 > |         };
 > |
 > | Is this the correct order? Should we have additional servers?  There
 > was an 80.x.x.x or
 > 81.x.x.x address that
 > | was given about 6 months ago and this address apparently had a stale
 > root zone that was
 > never being updated.
 > |
 > | We need a technical coordinator who can make such announcements to
 > the root operator
 > community so that
 > | we can be sure to have the right root zone at all times.
 > |
 > | John
 > |
 > |
 > |
 > | _______________________________________________
 > | Public-root mailing list
 > | Public-root@list.public-root.com
 > <mailto:Public-root@list.public-root.com>
 > | http://list.public-root.com/mailman/listinfo/public-root
 > |
 >
 >
 > Hi John,
 >
 > you have choosen
 >
 > host_name("205.189.71.2","a.public-root.net").
 > host_alias("a.root-servers.public-root.net","a.public-root.net").
 > host_alias("a.root-servers.newroot.com","a.public-root.net").
 > host_alias("Amsterdam","a.public-root.net").
 >
 > and
 >
 > host_name("57.67.193.189","a.public-root.old").
 > host_alias("Amsterdam.old","a.public-root.old").
 >
 > both servers give you a good Public-Root.zone .
 >
 > My first guess would be
 >
 > host_name("84.22.100.2","master.public-root.net").
 > 
host_alias("master.root-servers.public-root.net","master.public-root.net").
 > host_alias("master.public-root.net","master.public-root.net").
 >
 > ..  SOA   a.public-root.net. hostmaster.public-root.net. 2005061118
 >
 > ;; Query time: 127 msec
 > ;; SERVER: 84.22.100.2#53(84.22.100.2)
 > ;; WHEN: Sat Jun 11 23:53:25 2005
 >
 > You can have 3 or more masters.
 > But that is not the official answer
 >
 > Regards,
 > Peter Dambier
 > --
 > Peter and Karin Dambier
 > Public-Root
 > Graeffstrasse 14
 > D-64646 Heppenheim
 > +49-6252-671788 (Telekom)
 > +49-6252-599091 (O2 Genion)
 > +1-360-226-6583-9738 (INAIC)
 > mail: peter@peter-dambier.de <mailto:peter@peter-dambier.de>
 > http://iason.site.voila.fr
 > http://www.kokoom.com/iason


** --------- End Original Message ----------- **



-- 
Peter and Karin Dambier
Public-Root
Graeffstrasse 14
D-64646 Heppenheim
+49-6252-671788 (Telekom)
+49-6252-599091 (O2 Genion)
+1-360-226-6583-9738 (INAIC)
mail: peter@echnaton.serveftp.com
http://iason.site.voila.fr
http://www.kokoom.com/iason




From jp@adns.net Tue Sep 27 12:11:17 2005
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1EKI33-0001i3-V4
	for public-root@list.public-root.com; Tue, 27 Sep 2005 12:11:17 -0400
Received: from [24.148.29.239] (helo=TAKA)
	by MAIL.ADNS.NET with smtp (Exim 4.24)
	id 1EKJKG-0003pM-6k; Tue, 27 Sep 2005 13:33:08 -0400
Message-ID: <009201c5c380$577283c0$64904002@ADNSMICHIGAN.ADNS.NET>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Tue, 27 Sep 2005 11:25:41 -0500
Organization: AGN Domain Name Service, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Cc: discussions@list.inaic.com
Subject: [Public-root] L-Root is not properly configured.
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Tue, 27 Sep 2005 16:11:18 -0000

The L-Root is pointing to illegal data. They are using something called united-root.com. Looking this up
in the WHOIS, I see that they appear to be using a domain obfuscation provider that is designed to allow
domain registrants to hide their identity. 

Suggestion: We give L-Root 24 hours to correct their root server data or else, they simply aren't a 
member of public root anymore. In that case, they need to be removed from the list of public root
servers.
 
John


From jp@adns.net Sat Jul 01 17:49:49 2006
Received: from kovu.adns.net ([199.5.157.52] helo=MAIL.ADNS.NET)
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1FwnLZ-000133-Gg
	for public-root@list.public-root.com; Sat, 01 Jul 2006 17:49:49 -0400
Received: from [10.1.1.130] (helo=TAKA) by MAIL.ADNS.NET with smtp (Exim 4.24)
	id 1FwoT1-0007Hn-Vq
	for public-root@list.public-root.com; Sat, 01 Jul 2006 19:01:35 -0400
Message-ID: <009701c69d58$aa4e0300$8201010a@LOCAL>
From: "John Palmer" <jp@adns.net>
To: <public-root@list.public-root.com>
Date: Sat, 1 Jul 2006 16:52:06 -0500
Organization: AGN Domain Name Service, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Subject: [Public-root] Clean address for Public-root zone-transfer
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sat, 01 Jul 2006 21:49:49 -0000

It appears that there is no valid public-root rootserver running anywhere.

As of last night, all servers either stopped responding or started spewing out
garbage - orchestrated, it appears by Joe Baptista.

Is there a new master-server address from which we secondaries can 
AXFR a valid root zone? If so, it would be NICE if you would contact your
ROOT OPERATORS *AHEAD OF TIME* and inform them of this small
but CRUCIAL information. 

I run G.public-root.com and if someone doesn't straighten out this mess soon,
I'll shut it off. At this time, its answering with data from UnifiedRoot because
no public-root servers have valid data.

If you all don't stop squabbling amongst yourselves, I'm going to shut off
G. and not have anything to do with any of you and I'll also toss these
mailing lists off of my servers.

NOW SOMEOME FIX THIS MAJOR ERROR - NOW!

Thank you for your attention to this matter.


From Bradley@NorthTech.US Sat Jul 01 20:14:29 2006
Received: from vanquish.websitewelcome.com ([70.87.76.162])
	by LAIR.LIONPOST.NET with esmtp (Exim 4.24) id 1FwpbZ-00016L-5P
	for public-root@list.public-root.com; Sat, 01 Jul 2006 20:14:29 -0400
Received: from adsl-69-234-137-140.dsl.irvnca.pacbell.net
	([69.234.137.140]:3109 helo=[192.168.2.31])
	by vanquish.websitewelcome.com with esmtpa (Exim 4.52)
	id 1Fwpdd-00007h-UQ; Sat, 01 Jul 2006 19:16:38 -0500
Message-ID: <44A71066.1010105@NorthTech.US>
Date: Sat, 01 Jul 2006 17:16:38 -0700
From: "Bradley D. Thornton" <Bradley@NorthTech.US>
Organization: NorthTech Communications Group
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: John Palmer <jp@adns.net>
Subject: Re: [Public-root] Clean address for Public-root zone-transfer
References: <009701c69d58$aa4e0300$8201010a@LOCAL>
In-Reply-To: <009701c69d58$aa4e0300$8201010a@LOCAL>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - vanquish.websitewelcome.com
X-AntiAbuse: Original Domain - list.public-root.com
X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12]
X-AntiAbuse: Sender Address Domain - NorthTech.US
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: public-root@list.public-root.com
X-BeenThere: public-root@list.public-root.com
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Public-root Operators List  <public-root.list.public-root.com>
List-Unsubscribe: <http://list.public-root.com/mailman/listinfo/public-root>, 
	<mailto:public-root-request@list.public-root.com?subject=unsubscribe>
List-Archive: <http://list.public-root.com/mailman/private/public-root>
List-Post: <mailto:public-root@list.public-root.com>
List-Help: <mailto:public-root-request@list.public-root.com?subject=help>
List-Subscribe: <http://list.public-root.com/mailman/listinfo/public-root>,
	<mailto:public-root-request@list.public-root.com?subject=subscribe>
X-List-Received-Date: Sun, 02 Jul 2006 00:14:29 -0000

John Palmer wrote:
> It appears that there is no valid public-root rootserver running anywhere.
>   

That is correct John. It's another Baptista Vortex and every query 
resolves to http://CNN.com

> As of last night, all servers either stopped responding or started spewing out
> garbage - orchestrated, it appears by Joe Baptista.
>   

Joe's been explaining how this can happen, and warning against practices 
which invite this sort of calamity for almost a decade now. He shut down 
pretty much half of Diebold itself after they fired Gene Marsh, as they 
were in violation of their contract with him, and they had the audacity 
to call my datacenter up and threaten me about his "Baptista Vortex", 
which pulled all DNS into a single webpage and explained the reasons 
Diebold no longer existed on the Internet.

That in itself was quite entertaining - in part because I have a very 
thick skin, and in part because their attorney realized when speaking 
with me that I had no culpability in the matter - I merely routed Joe's 
IP blocks via my ASN w/confederate BGP announcements. I explained to the 
bonehead that the person he needed to contact and threaten was the RP 
for the IP Blocks in question - aka Joe Baptista, LOL!

At that point I think I heard one of the Diebold guys in the background 
start to sob, because the only person they can address their concerns to 
is the Administrative contact for the IP Block, and not some transitory 
peering point like me, or Mae East or Mae West LOL!

> Is there a new master-server address from which we secondaries can 
> AXFR a valid root zone?

I'm surprised at you John, for not having a recent backup of the 
zonefile that you can load and master in the interim.

>  If so, it would be NICE if you would contact your
> ROOT OPERATORS *AHEAD OF TIME* and inform them of this small
> but CRUCIAL information. 
>
> I run G.public-root.com and if someone doesn't straighten out this mess soon,
> I'll shut it off. At this time, its answering with data from UnifiedRoot because
> no public-root servers have valid data.
>
> If you all don't stop squabbling amongst yourselves, I'm going to shut off
> G. and not have anything to do with any of you and I'll also toss these
> mailing lists off of my servers.
>   

That's prolly the most logical thing to do John. The whole 
public-dash-root system is based on piggy-backed and borrowed IP 
infrastructure wrt the parent. There was never any value in those flat 
TLDs anyway, never any concept for what to do with the TLDs once they 
were registered, and the only fools who signed on board were blind 
corporations governments who wanted to take advantage of a system which 
they had no concept as to what made it tick - they were bamboozled.

Furthermore, I never resigned my position from the council - that was 
forged by someone - Xennt, as I have been repeatedly told by others.
> NOW SOMEOME FIX THIS MAJOR ERROR - NOW!
>   

That's not going to happen John and you know it. Might as well shut it 
all down now and not look back. Gawd! Am I the only person who's been 
running a stable RSC for all these years? Geez!

> Thank you for your attention to this matter.
>   

Y'know John, as an aside note, I just have never been able to understand 
these idiots out there who come up with schemes to rip people off and 
cybersquat on TLDs, thinking that they can run an RSC on IP 
infrastructure not their own - Yes, I got my delegations direct from the 
military in 1985 and began root operations in November of that year - 
predating anything orscians every even thought up by almost a decade. 
But this has been a repeating scenario again and again, and the Turks 
are getting exactly what should happen to them for signing on with 
crooks (Actually, KOC, the Turkish ISP was only down for two hours 
before switching over to the "Deprecated, Alternate root system" 
operated by the USG. So it's a done deal and now poof! It's gone LOL!

um... I would like to say now, that Any "Sane" policies and concepts the 
public-dash-root system incorporated were MINE :) This is supported by 
extensive email archives detailing many months of pre-planning between 
Xennt and myself, while I was preparing to migrate my branding from that 
of my federally Trademarked, "PacificRoot" to that of "The PublicRoot 
Foundation", located on the Internet at http://PublicRoot.Com/Net/Org.

For some reason, Xennt really had other, apparently crimimal designs for 
the commercial operations which I would not condone, nor was I ready to 
release the new PublicRoot system in it's re-branded form until I was 
ready and had all of the SLD registrars and TLD Managers ready to go 
online, so he registered PUBLIC-ROOT.com/net/org (public-dash-root, as 
you will see me call it). He then went ahead and started publishing the 
websites containing all of the plagiarized verbage that I had written 
and explained to him and took it a step further, dumping the whole 
multi-tiered aspect that the Internet operates on - 
TLD-SLD-3LD-4LD...... etc...

Xennt, nor any of these bonehead investors of his, ever had a clue as to 
what the nature of critical mass is, what populating SLDs with unique, 
meaningful content is (or why you would want to), what the significance 
of an SLD registry is, or why this is important - the only thing these 
idiots were interested doing was ripping people (and ideed, countries) 
off and selling them worthless, meaningless TLDs that would never serve 
any purpose other than to flatten out the DNS!

Thanks for helping them out with that John! Shame on you! Coz you know 
better - you know why SLD registries are important and why a TLD is 
meaningless if it is only used for vanity - you operate SLD registries 
too my pioneering Internet brother.

Anyway John, I'm not here to bash you - I really admire all of your hard 
work and know you to be an honest and ethical TLD Manager and Operator. 
But you should have pulled the plug on these idiots a long long time ago 
my friend. I also know that you don't know much of the history of how 
Xennt came up with something that in verbage sounded so good. Now you 
do. Oh, I didn't actually give credit to Joe either, he came along late 
in the game - very late in fact, after xennt had registered 
public-dash-root and started joining international standards 
organizations that never ever existed, and finally convoluting the whole 
thing with his INAIC scheme and the other off-shore-style member orgs 
which I can't even begin to keep track of.

I refused to provide xennt with anymore expertise in writing unless I 
was paid, and he got Joe to do it for much less, who then sub-contracted 
me in writing up some standards and procedures - When xennt failed to 
come up with the promised funds to  gain the release for about 200hrs of 
work that I had performed I refused to deliver the remainder of it.

Joe is not your culprit here John, Xennt is.Don't be upset with Joe - 
he's only making you all sleep in the bed that you guys made.

> _______________________________________________
> Public-root mailing list
> Public-root@list.public-root.com
> http://list.public-root.com/mailman/listinfo/public-root
>
>
>
> __________ NOD32 1.1636 (20060701) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
>
>   


-- 

Kindest regards,


Bradley D. Thornton
Manager Network Services
NorthTech Computer
+1.949.310.3505
http://NorthTech.US
mailto:Bradley@NorthTech.US



</snip>

-- 

Kindest regards,


Bradley D. Thornton
Manager Network Services
NorthTech Computer
+1.949.310.3505
http://NorthTech.US
mailto:Bradley@NorthTech.US