Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!agate!telecom-request From: cmoore@brl.mil (Carl Moore) Newsgroups: comp.dcom.telecom Subject: Re: It is Now Official: 416 to be Split Into 905 Message-ID: Date: 26 Mar 91 14:41:12 GMT Sender: Telecom@eecs.nwu.edu Organization: TELECOM Digest Lines: 18 Approved: Telecom@eecs.nwu.edu X-Submissions-To: telecom@eecs.nwu.edu X-Administrivia-To: telecom-request@eecs.nwu.edu X-Telecom-Digest: Volume 11, Issue 243, Message 4 of 14 Is 905 (the newly-announced code for area to split from 416) to include the area bordering on 705? The bordering on 705 would make (as Woody pointed out in an old message) 706, the other former pseudo area code for parts of Mexico, a poor choice. Someone else's old note pointed out that when a new area code was being selected for the Oakland (California) area, 909 was a poor choice because it looked a little too much like neighboring area code 707. (Later, we heard of 510 being selected for Oakland and 909 being selected for Riverside and San Bernardino counties in southern California.) Did you notice that 301 has bordered 302 for as long as there have been area codes? (These are the codes for Maryland and Delaware respectively.) Maybe that was why eastern Maryland was picked to get area code 410, so that 301 and 302 will no longer touch. Also, 301, which (before 410 split) covers all of Maryland; touches one exchange area of area 412 in Pennsylvania; the Maryland portion touching area 412 will stay in 301.