Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bu.edu!telecom-request From: cmoore@brl.mil (VLD/VMB) Newsgroups: comp.dcom.telecom Subject: Re: Forts Meade and Ritchie in Maryland Message-ID: <74369@bu.edu.bu.edu> Date: 10 Feb 91 04:06:18 GMT Sender: news@bu.edu.bu.edu Organization: TELECOM Digest Lines: 62 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 105, Message 1 of 7 Responding to Carl Wright: No, the ideas I see regarding the Baltimore-DC area aren't all that hard. I just got through checking out some zipcodes and phone prefixes near the future 301/410 border (I'll be looking for some phone numbers around a portion of the Carroll-Frederick county line), and I already figured out North Beach, Maryland 20714, which I would list as 410 in the zip-area directory when it picks up the 301/410 split. The prefixes serving the North Beach area are currently in area 301, and are: 257 -- apparently the "default" and apparently what is found on pay phones; goes into 410. 855 -- although it was/is North Beach on a phone bill, it is a DC-metro exchange and stays in 301. Similar prefixes exist around Chicago (right?) and Los Angeles. In the Los Angeles area, there are prefixes which show up on a phone bill as Los Angeles (different procedure from what I just cited for North Beach), but which serve areas beyond Los Angeles (such as Burbank and Pasadena, even though the other prefixes serving Burbank and Pasadena went into area 818. Back in Maryland: In Laurel, the "Waterloo-service" prefixes go into 410 because they are local to Baltimore, and the other Laurel prefixes (which are local to Washington) stay in 301. >...Carl Moore is quoted as saying that his zip code will >be splitting along the with area code split. The only remark by me about a split zip code might be: > As far as I know (not having been to Fort Meade), > the other phones on that post are in the Odenton exchange, which is > going into 410 (causing a problem as to how to list the area code for > zip code 20755?). I was writing about 301-688 prefix, which is to stay in 301. 20755, which is between Baltimore and Washington, is not "my" zip code, as I live in Delaware, and (w/r to Washington) have an office about 30 miles beyond Baltimore. When I write about zipcodes and phone prefixes, I might be writing about areas I don't call, write or visit! I am quite well aware that phone prefixes and zip codes do not necessarily match, and a concern I sent to the publisher of the zip-area directory is that if a zipcode falls along an area code border, I end up having to list it based on where a "majority" of that zipcode falls. I am hesitant about pointing out specific split zipcodes, because there are probably a slew of such splits which I have no way of knowing. [Moderator's Note: We've got cases here where 'Post Office Chicago', i.e. 606-anything extends into a few suburbs which are now 708. The rule you can generally follow here is that 606xx = 312 and 600xx, 601xx, 602xx, 604xx = 708 or 815; however 815 takes in several more one mprovement

lan codes as well. PAT]