Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!apple!bionet!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: goudreau@dg-rtp.dg.com (Bob Goudreau)
Newsgroups: comp.dcom.telecom
Subject: Re: New 410 Code For MD
Message-ID: <14837@accuvax.nwu.edu>
Date: 19 Nov 90 22:21:41 GMT
Sender: news@accuvax.nwu.edu
Organization: TELECOM Digest
Lines: 30
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 835, Message 4 of 15


In article <14766@accuvax.nwu.edu>, opel!arinc!vk2bea!eccles!
michael@uunet.uu.net writes:

> The new 410 area code will serve metropolitan Baltimore, the entire
> Eastern Shore, Calvert County and the majority of Carroll, Howard and
> Anne Arundel counties.

> The rest of the state will use the existing 301 area code.

This raises an interesting point.  As far as I can tell, this appears
to be the first time that an area code split has resulted in the
original area code's major metro area getting left out in the cold
(i.e., assigned to the new code, with all the concomitant bother,
rather than getting to keep the old one).  Perhaps the explanation is
that even though Baltimore is the largest city *in* Maryland,
Washington D.C. and environs is the biggest conurbation *near*
Maryland, so the Washington suburbs "win" and get to stay in 301.

Examples of the normal rule include Manhattan (got to keep 212 --
twice now!), Boston (617), San Francisco (415), Houston (713), Denver
(303), Miami (305), "core" Los Angeles (213 -- twice), and probably
several others as well.  But does anyone know of any previous
violations of the rule?


Bob Goudreau			+1 919 248 6231
Data General Corporation        62 Alexander Drive	
goudreau@dg-rtp.dg.com          Research Triangle Park, NC  27709
...!mcnc!rti!xyzzy!goudreau     USA