North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Namespace conflicts

  • From: Clayton Fiske
  • Date: Fri Mar 09 13:33:29 2001

On Fri, Mar 09, 2001 at 09:21:50AM -0800, Owen DeLong wrote:
> > 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 
[snip]
> > 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).

RFC1480 seems to be the one. 

-c