March 2001 - Test - lists.nanog.org

Re: Namespace conflicts
by Steven M. Bellovin 09 Mar '01

09 Mar '01

In message <20010309064952.B10940(a)eiv.com>, Shawn McMahon writes: > >On Thu, Mar 08, 2001 at 05:27:20PM -0800, Tony Hain wrote: >> More precisely, the courts started getting involved as soon as >> first-come-first-serve stopped working fine. > >No, someone involved the courts when they were second, and the courts >didn't understand so they didn't smack it back at the lawyers "dismissed >with prejudice". > >DNS didn't make the mess, the courts did. In my area of NJ, virtually every town's "obvious" .com domain names were grabbed by one of two competing would-be service providers. They had absolutely no town-specific content -- but if the town wanted a Web site, they had no choice but to deal with these folks. I have no major problem with first-come, first-served *productive* use of a domain name, but frankly, that's not where the problem has been. The problem has been speculators and cybersquatters. --Steve Bellovin, http://www.research.att.com/~smb

6 6

RE: Namespace conflicts
by Mark Borchers 09 Mar '01

09 Mar '01

> ...right. And Delegation of nameservice is a CUSTODIALSHIP for the end > user organization/entity. The pain in .US was felt when some 3rd-level > delegates took on a custodianship for free and then charged folks > underneath them, a form of delegation-squatting, with no intent of > sheparding the resource until clue was imparted to the > more-appropriate > organizations. That's just wrong, and triggered involvement of legal > entities again. Right on target, Joe. For the historical record, I would add that ISI eventually realized that .US subregistries were using the third-level domains as a cash cow. To deal with this, they imposed a requirement that the city/county government concur in new delegations for their communities. However, by that time the profiteers had swallowed up almost all the .US third level domains that had not been previously registered.

1 0

network availability standards
by Miguel Mata-Cardona 09 Mar '01

09 Mar '01

Hi, we are looking for some standards of network availability for broadband networks. Specificaly for backbone availability, last mile availability, mean time to repair, and so on. We have and HFC network (yes, CATV and cablemodems). These customers range from the home users, SOHO, point-to-point and VPNs. Any pointer to these info would be very appreciated. We are trying to set up a SLA paperwork for commercial and corporate customers. -------------------------- Miguel Mata-Cardona CCI El Salvador mmata(a)sv.cciglobal.net

1 0

Re: Namespace conflicts
by owen＠dixon.delong.sj.ca.us 09 Mar '01

09 Mar '01

> On Fri, Mar 09, 2001 at 09:10:09AM -0500, Steven M. Bellovin mailed: > > In my area of NJ, virtually every town's "obvious" .com domain names were > > grabbed by one of two competing would-be service providers. They had > > absolutely no town-specific content -- but if the town wanted a Web > > site, they had no choice but to deal with these folks. I have no major > > problem with first-come, first-served *productive* use of a domain name, > > but frankly, that's not where the problem has been. The problem has > > been speculators and cybersquatters. > > Uh, why couldn't the town just use <name>.nj.us or whatever the city specific > code was long ago and far way. No. However, they could use ci.<name>.nj.us, and that's where I usually go if I'm looking for a particular city's web site. The reason for this distinction is to support things like: ci.alameda.ca.us City of Alameda co.alameda.ca.us County of Alameda joesshoes.alameda.ca.us Joe's Shoe Shop in Alameda, CA etc. There's an RFC that spells all this out (1680 comes to mind, but not sure that's the right number). Owen

4 3

looking for midwest sprint rep
by michael thomas guldan 09 Mar '01

09 Mar '01

hi, looking for a GOOD(ahem) sprint rep for a bid on a customer T-1 in the dublin/hilliard, ohio area. i would prefer referrals from existing customers over direct contact from salespeople. thanks, michael -- e: michael(a)ele-mental.org c: +1.614.260.6716 u: www.ele-mental.org Wir fahr'n fahr'n fahr'n auf der Autobahn

1 0

arrgh
by Joe Abley 09 Mar '01

09 Mar '01

We need a nanog-variant of Godwin's law, with the trigger phrases "ICANN" and "UDRP".

1 0

Re: Namespace conflicts
by Steven M. Bellovin 09 Mar '01

09 Mar '01

In message <20010309100228.A2521(a)redhat.com>, "Bryan C. Andregg" writes: > >--sdtB3X0nJg68CQEu >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Fri, Mar 09, 2001 at 09:10:09AM -0500, Steven M. Bellovin mailed: >> In my area of NJ, virtually every town's "obvious" .com domain names were= >=20 >> grabbed by one of two competing would-be service providers. They had=20 >> absolutely no town-specific content -- but if the town wanted a Web=20 >> site, they had no choice but to deal with these folks. I have no major= >=20 >> problem with first-come, first-served *productive* use of a domain name, >> but frankly, that's not where the problem has been. The problem has=20 >> been speculators and cybersquatters. > >Uh, why couldn't the town just use <name>.nj.us or whatever the city specif= >ic >code was long ago and far way. They grabbed those, too. --Steve Bellovin, http://www.research.att.com/~smb

1 0

Re: Fiber cut in Ontario, Canada cutsoff @home users
by William F. Maton 09 Mar '01

09 Mar '01

On Fri, 9 Mar 2001, Zwiep, Rick wrote: > It's surprising that in this era of huge fiber capacity with SONET, ATM and > MPLS and WDM that a fiber cut should take out an entire province full of > users... Beats me. As one of those users, I did feel it. Everybody else seems to be up and running just fine, so it makes wonder about @home's topology in Ontario. > At one time that fiber link from Toronto to Buffalo was on an unprotected > fiber segment, but that was years ago... hmmm Probably during the good ol' days of "Call before you dig." > rgds - rickz wfms

1 0

PRESS RELEASE: TCH.ORG Expands Internet Naming with New Top Level Domain Names
by Steve Rubin 09 Mar '01

09 Mar '01

The full text of this release is available at http://www.tch.org/tld/press.html San Jose, Calif - March 8, 2001 - TCH.ORG (http://www.tch.org/) a internet incubator, officially announced today that it will begin offering a easy to use alternative to hard to remember "DOT COM" addresses.

3 2

Fiber cut in Ontario, Canada cutsoff @home users
by William F. Maton 09 Mar '01

09 Mar '01

Greets, According to a news report this morning there was a fiber cut which is used to service @Home customers in the province of Ontario. Apparently, the fiber was cut as thieves were trying to salvage copper. First, seti@home's facilities were cut off by a similar act of "simple copper mining" and now it looks like another of the same sort of incident. I wonder if there are statistics available showing a growing trend of network outage due to copper theft. Sean? wfms

1 0