A Beginner's Guide to the Internet/INTERNET.ISO/text/telediag/tc13-132.txt

Text File | 1996-05-06 | 21.2 KB | 522 lines

TELECOM Digest     Fri, 26 Feb 93 01:09:30 CST    Volume 13 : Issue 132

Index To This Issue:                      Moderator: Patrick A. Townson

    History of Area Code Splits, 25 Feb 1993 (Carl Moore)
    Infocom '93 (Mike Hluchyj)
    White House: A Computer Nerdville (New York Times via Eric De Mund)
    Help Wanted (Hannu Komulainen)
----------------------------------------------------------------------

Date: Thu, 25 Feb 93 10:37:50 EST
From: Carl Moore (VLD/VMB) <[e-mail]>
Subject: History of Area Code Splits, 25 Feb 1993


[Moderator's Note: Carl updates this file in the Telecom Archives on a
regular basis (where it is filed as 'history.of.area.splits' and also
as 'areacode.history'), but I only print it here in the Digest once a
year or so after several revisions have been incorporated into it.
This file, and others in the archives are accessible using anonymous
ftp lcs.mit.edu.  PAT]

                        -------------

Generalizing prefixes from NNX to NXX (i.e., allowing N0X/N1X) is an
alternative to splitting an area which has had only NNX up to this
point.  When an area has NXX (not NNX) prefixes, its long distance
dialing instructions usually are:

  7D or 1 + NPA + 7D within area (can no longer use 1 + 7D);
  1 + NPA + 7D to other areas (can no longer use NPA + 7D);
  for 0+ calls, try 0 + NPA + 7D (some 0 + 7D would require timeout).

In other words, the leading 1 (or 0) means that what follows is an
area code.  These instructions can, without further revision,
accommodate area codes of form NXX, not just of form N0X/N1X, and thus
I believe they will become universal when area codes must generalize
to NXX, for which the deadline is January 1, 1995 (had been July 1,
1995).  But since the first batch of NNX area codes will be of NN0
form, some areas might be able to keep 1 + 7D for intra-NPA long
distance by disallowing prefixes of NN0 form; I do not know if this
will be affected by use of 52x codes (x not necessarily 0) for Mexico.
It is unclear how generalizing area codes to NXX would affect the
policy of not using N0X/N1X prefixes until NNX starts running short.

An exception to the above dialing instructions was discovered in
Feb 1992 for 215-267 (Denver) and 215-484 (Adamstown) in Pennsylvania.
These exchanges are served by Denver & Ephrata Telephone & Telegraph,
which also serves a part of the 717 area, and which is keeping the
old instructions (1 + 7D and 0 + 7D within area code), even though
this will necessitate timeout resolution for some calls from the 215
portion of their service area.  This will change only when it is
about time for the NXX area codes.

The suggestion (at least from Bellcore) has been seen that ideally,
all calls should be makeable as 1+NPA+7D (this does not necessarily
forbid shorter forms).

These areas have N0X/N1X prefixes:
213, California, July 1973
 (7D on all calls within it)
 (later 213/818, now 213/310/818)
 (this area continued to publish 0+7D instruction for
  within-NPA 0+ calls)
212, New York, some days after 24 Nov 1980
 (7D on all calls within it)
 (later 212/718, now 212/917/718)
312, Illinois, Oct 1982--but got 1st N0X/N1X spring 1983?
 (7D on all calls within it)
 (now 312/708)
201, New Jersey
 (7D on all calls within it; also applies to 609)
 (now 201/908)
214, Texas, 1986 or 1987 (by July 1987)
 (1+NPA+7D on all toll calls; also applies to 817,
  at least in Fort Worth area)
 (now 214/903)
301/202/703, Maryland/DC/Virginia, 1987, due to DC area growth
 (1+NPA+7D on all toll calls)
 (301 now 301/410)
415, California, Feb 1989?
 (7D on all calls within it)
 (now 415/510)
404, Georgia, Oct 1989?
 (1+NPA+7D on all toll calls; also applies to 912)
 (now 404/706)
919, North Carolina, 2 Mar 1990
 (1+NPA+7D on all toll calls; also applies to 704)
 (to become 919/910)
416, Ontario, 3 Mar 1990
 (1+NPA+7D on all toll calls)
 (to become 416/905)
602, Arizona, 1 July 1990
 (1+NPA+7D on all toll calls)
313, Michigan, 1990?
 (1+NPA+7D on all toll calls)
 (to become 313/810)
512, Texas, 9 Sept 1990
 (1+NPA+7D on all toll calls)
 (now 512/210)
205, Alabama, Dec 1990
 (1+NPA+7D on all toll calls)
215, Pennsylvania, 20 May 1991
 (7D on all calls within it; exception noted above, but the new
  instructions were also applied to:
  717-354,355 New Holland
  717-656,661 Leola
  717-768 Intercourse)
 (to become 215/610)
206, Washington, 12 Jan 1992
 (1+NPA+7D on all toll calls)
813, Florida, 7 Mar 1992
 (1+NPA+7D on all toll calls; also applies to 305,407,904)
713, Texas, 8 Mar 1992 (permissive dialing 8 Dec 1991)
 (1+NPA+7D on all toll calls)
714, California, 1992?
 (7D on all calls within it)
 (now 714/909)
503, Oregon, 10 July 1993
 (1+NPA+7D on all toll calls)

No note about N0X/N1X prefixes, but instructions are being changed
to accommodate the coming of NXX area codes:
207, Maine; 413,508,617, Massachusetts; 603, New Hampshire;
 401, Rhode Island; 802, Vermont (all New England areas
 except Connecticut); 1993-1994
 (7D on all calls within area code)
303,719, Colorado; other U.S. West areas; 1993-1994
 (1+NPA+7D on all toll calls)

Areacode splits:

If no date appears, the split may not have been announced publicly due
to lack of direct-dial facility at the time, or may never have
occurred.  Early splits can only be guessed at with the following
guidelines: If an areacode is of form N1X, it is in a state or
province with more than 1 areacode. (The reverse, if it was ever true,
is now obsolete.)  If an areacode is in a state or province with only
1 areacode, it is of form N0X.  (The reverse, if it was ever true, is
now obsolete.)

what?/209 California
what?/707 California
what?/805 California
305/813 Florida
404/912 Georgia, 1953 or 1954
    December 1991 Greater Atlanta call guide, in discussing 404/706
    split, said "It's been 38 years since Georgia added an Area Code."
what?/309 Illinois
502/606 Kentucky
504/318 Louisiana
616/906 Michigan, sometime after Nov 1960
612/507 Minnesota
402/308 Nebraska
what?/607 New York
704/919 North Carolina
405/918 Oklahoma
what?/519 Ontario, 1953
901/615 Tennessee
what?/806 Texas
206/509 Washington
what?/608 Wisconsin
what?/705 Ontario, 1957
201/609 New Jersey, late 1950s
what?/807 Ontario, 1962
415/408 California, 1960
305/904 Florida, July 1965
703/804 Virginia, 24 June 1973 at 2:01 AM
714/619 California, Nov 1982
713/409 Texas, Mar 1983 (full cutover 90 days later)
213/818 California, Jan 1984
212/718 New York, 2 Sept 1984 (full cutover 31 Dec 1984)
    Brooklyn, Queens, Staten Island became 718;
    Manhattan & Bronx stayed in 212;
    Bronx switched from 212 to 718, 1 July 1992 (full cutover
    15 May 1993; but until then, calls from Bronx to Brooklyn/
    Queens/Staten Island must still be dialed 1+718+7D, and
    effective 25 Sept 1993 must be dialed 7D)
303/719 Colorado, 5 Mar 1988
305/407 Florida, 16 Apr 1988
617/508 Massachusetts, 16 July 1988
312/708 Illinois, Nov 1989 (full cutover 9 Feb 1990)
202 District of Columbia & vicinity, 1 Oct 1990
    This behaved somewhat like a split despite no new area code.
    202 area code, previously useable for all but the outermost
    Maryland and Virginia suburbs, was restricted to DC proper.
    (Use 301 or 703, as the case may be, to reach the suburbs.)
    As a result, government offices (now including the Pentagon)
    using zipcodes starting with 200,202,203,204,205 and located
    in Md. or Va. can no longer be listed in area 202.  Prefixes

    in the Pentagon, which is in Virginia, were previously in area
    202 (not 703), and in 1990 were moved to area 703.  (Local
    calls across area code border changed from 7D to NPA+7D.)
214/903 Texas, 4 Nov 1990 (full cutover 4 May 1991)
201/908 New Jersey, 1 Jan 1991 (full cutover 8 June 1991)
415/510 California, 2 Sept 1991 (full cutover 27 Jan 1992)
301/410 Maryland, 1 Nov 1991 (full cutover 1 Nov 1992)
213/310 California, 2 Nov 1991 (full cutover 16 May 1992; was
     to be 2 May 1992, but was postponed indefinitely because
     of riots just before then)
    (all GTE plus some PacBell went into 310)
212/718/917 New York, 1 Jan 1992 (917, to be overlaid on
     212 & 718, is to be used for cellular & pagers)
404/706 Georgia, 3 May 1992 (full cutover 3 Aug 1992)
512/210 Texas, 1 Nov 1992 (full cutover 1 May 1993)
714/909 California, 14 Nov 1992 (full cutover 14 Aug 1993)
    (Riverside and San Bernardino counties go into 909;
     Orange County remains in 714)
416/905 Ontario, 4 Oct 1993 (full cutover 10 Jan 1994)
919/910 North Carolina, 14 Nov 1993 (full cutover 13 Feb 1994)
313/810 Michigan, 10 Aug 1994
215/610 Pennsylvania, 1994

On Feb 1, 1991, area codes 706 and 905, which had been used in the
U.S. for calling parts of Mexico, were discontinued.  Country code 52,
already available for such calls, was to be used.  706 and 905 thus
became available for use elsewhere, and were later announced for use
in Georgia and Ontario respectively.

------------------------------

From: [e-mail] (Mike Hluchyj)
Subject: Infocom '93
Organization: Motorola Codex, Canton, Massachusetts
Date: Thu, 25 Feb 1993 19:40:12 GMT


                   *  *  *  *  *  *  *  *  *  *

Announcing . . . .

IEEE INFOCOM '93
The Conference on Computer Communications

March 28 - April 1, 1993

Hotel Nikko, San Francisco, California

Now in its 12th year, IEEE INFOCOM is the premier international
technical conference devoted to computer communications and
networking.  Papers presented at INFOCOM represent the leading edge of
understanding and development in this fast moving field, and are
accepted only after a rigorous review process.  Half-day and full-day
tutorials are given by leading experts and afford the participant an
opportunity to stay current with the latest directions in
communication networks.  IEEE INFOCOM '93 is sponsored by the IEEE
Computer and Communications Societies.

The major themes of INFOCOM are shaped each year by the papers
submitted and the directions set by the Technical Program Committee.
This year, as in recent years, a major theme is multimedia and
integrated networking.  In particular, many aspects of ATM transport
are explored.  Modelling of multimedia traffic (including video),
admission and congestion control, switching, optical networking, and
quality of service guarantees are prominent in this year's program.
There are also sessions on routing, wireless networks, and local and
metropolitan area networks, along with sessions on conformance testing
and interoperability, protocol design and evaluation, protocol
specification and verification, protocol implementation and analysis,
and high speed protocols.

The panels this year cover formal methods and telecommunication system
software, all-optical networking, and the future of network theory.

We are especially fortunate to have Prof. Robert G. Gallager of MIT
deliver the plenary address on "Network and Communication Research in
the Information Age."

The first two days of the conference (March 28 and 29) are devoted to
tutorials, and this year one can select from among the following
outstanding tutorials:

   Quality-of-Service Control and Management for Broadband
   Networks,
   Aurel A. Lazar, Columbia University

   Theoretical Aspects of Multi-Stage Networks for Broadband
   Networks,
   Gaylord W. Richards, AT&T Bell Labs

   Design of Local ATM Networks,
   Jonathan Turner, Washington University

   Multimedia Communications and Services,
   Sid Ahuja, AT&T Bell Labs

   Advanced Topics in Broadband Systems: ATM Switches and Optical
   Networks,
   Anthony S. Acampora, Columbia University

   Wireless Information Networks,
   David Goodman, Rutgers University

                   *  *  *  *  *  *  *  *  *  *

To receive an electronic copy of the INFOCOM '93 Advance Program send
Email to: [e-mail]

To receive a printed copy of the INFOCOM '93 Advance Program call
Gerry Hansen at [phone] or send a FAX to Michael G. Hluchyj,
INFOCOM '93 General Chair at [phone].

------------------------------

From: Eric De Mund <[e-mail]>
Subject: White House: A Computer Nerdville
Reply-To: Eric De Mund <[e-mail]>
Organization: Netcom Online Communications Services
Date: Thu, 25 Feb 1993 21:41:24 GMT


[NYT, Saturday, February 20, 1993]

                White House: A Computer Nerdville
                         By STEVE LOHR

                 Special to The New York Times


  WASHINGTON -- In policy and practice, this is supposed to be a
high-tech Presidency.

  Bill Clinton's vision of America's future is of a nation linked by a
"data superhighway" -- a web of fiberoptics wizardry able to bring
everything from libraries to movies to blueprints into every home,
school and office at the touch of a button.

  On the campaign trail, his people regarded laptop personal computers
as casual tools of everyday life, plugging them into computer bulletin
boards and firing off electronic-mail messages around the country.

                          Big Job for 2 Mavens

  And through electronic town halls and electronic mail, President
Clinton pledges to bring the Government to the people.

  Perhaps, but the White House itself seems trapped in the technological
dark ages. And it is the job of Andrew Aultz and Bill Krause, two
technology mavens, to bring the telephones and computers in the
Executive Offices into the modern world -- no small order, given the
budget squeeze.

  "We'd love to give this place all the latest toys, but we can't," Mr.
Krause said, sitting beneath a freshly framed picture of President
Clinton and leafing through a computer magazine.

  Many phone calls in the White House are still connected manually by
operators plugging cords into a switchboard. Mr. Aultz, a 35-year-old
telecommunications specialist, says its archaic inefficiency is one
reason callers cannot get through to register their views on the
Presidential comments line, generating up to 50,000 busy signals a day.

  Mr. Krause, a 42-year-old computer expert, complains of a chronic
shortage of personal computers and tells of young staff members appalled
to find typewriters on their desks.

  The PC's that are there are a couple of generations old -- four years
or more -- and are arrayed in a hodgepodge of 21 networks that cannot
talk to one another. One result: the President's daily schedule is still
printed on paper and distributed by hand instead of by computer, so some
people get it a couple of hours late.

  In many ways, the challenge at the White House is similar to that
confronted daily in corporate America as companies try to tailor fast-
changing technology to their organizational needs.

  "The White House is like a small holding company -- and a very
important one," said Warren McFarlan, a professor at the Harvard
Business School. "And it is grappling with the same technology issues
that companies must address every day."

  The Clinton staff got used to high-speed technology on the campaign
trail, scouring the news wires constantly by computer and reacting
almost instantly with statements, position papers and rebuttals to
charges or controversies. These messages were distributed through an
elaborate electronic mail system linked to campaign offices in all 50
states.

  "Our motto on the campaign was that speed kills," explained Jeff
Eller, the White House director of media affairs.


  The technological hurdle for the White House is magnified by the
generation gap between the Clinton and Bush Administrations and very
different styles of government.

                       It Worked in the Campaign

  The use of modern technology to speed reaction times and deal with the
public directly, whether in televised town meetings or a program for
electronically distributing White House statements nationally, is a
central tenet of the Clinton Administration. As much as possible, the
President wants his message delivered as he presents it, not filtered,
or analyzed, by the news media. The catch phrase, used by White House
officials, is that Mr. Clinton intends to speak "to people" instead of
speaking "through people."

  It worked in the campaign, they say, and it will be used in the
White House, especially to rally support for ambitious programs like
the Clinton economic policy.

  "Clinton plans to run his Government like a campaign," said Raymond
Strother, a Democratic political consultant, "To do that, you need the
technology to run at that speed."

  The demand for technology by the young White House staff members is
running well ahead of supply. Personal computers are being rationed
and the backlog of PC's ordered but not yet delivered is 50, though
that is down from 100 two weeks ago.

  "Our people are hooked on the flow of information," Mr. Krause said,
"so everybody wants his or her own PC."

                         A Flood of Daily Calls

  The jammed phone lines at the White House are apparently a result of
the higher volume of calls from the public. During the Reagan and Bush
years there would be about 5,500 calls to the White House general
number on a busy day, though the numbers would rise in crisis periods
like the Persian Gulf war.

  By contrast, there are 40,000 to 65,000 calls a day now to the
general number alone, according to Mr. Aultz. The steady flood of
calls, White House officials say, is explained by the new
Administration's more open, informal style.

  "Where people might not have dared call when Reagan or Bush were in
the White House, they will call here now," Mr. Aultz said.

  While the White House phone service how badly needs upgrading, Mr.
Aultz concedes it met the requirements in the past.

                       Working With Phone Company

  "In fairness, we found a telephone system that was suited for the way
they did business," Mr. Aultz said. "But it is terribly inefficient for
the way we do business."

  The White House is working with the local phone company, Chesapeake
& Potomoc, and American Telephone and Telegraph to streamline and
expand the White House phone systems.

  On the computer front, Mr. Krause plans to replace many of the White
House PC's, mostly I.B.M. models dating to 1988 and 1989, with more
powerful machines that run faster and can handle graphics and possibly
even information in both video and audio form, so-called multimedia.

                      No Substitute for Decisions

  The Iran-Contra affair put a dent in the White House computer budget
because all the hard disks had to be removed and replaced after a
Federal panel ruled last month that all E-mail messages from the Bush
Administration had to be saved. The Clintonites insist that the
precedent for opening up E-mail messages to public scrutiny will not
deter them from using the technology freely.

  For the moment, the bigger problem is bringing the White House
computer systems up to speed.

------------------------------

From: [e-mail] (Hannu Komulainen)
Subject: Help Wanted With Development Project
Date: 24 Feb 93 08:35:24 GMT
Organization: Telecom Finland


I would appreciate your help on our (Telecom Research Centre, Finland)
new development project concerning "Remote-Line-Activation" or as we
call it "INSTANT-service". Here is short description what it is all
about.

Introduction:

Every now and then people move from one residence to other and of
course want to move their telephone lines there too. Or perhaps the
customer wants to get some new service in his/her telephone line. So,
what happens?  Customer goes to Telecom Finland's public service point
and makes agreement about that previous mentioned service. Personnel
at the service point give customer timescedule when order is ready.
And then custom have just to wait!

What if the customer can get right away new service activated or new
residence telephone line activated instantly, too, and old residence
telefone line deactivated at the same time? Or perhaps these events
can be made timed.

Our goal is to get this process more easy and faster.

The main problem here in Finland is that we have several types of
switches e.g. Nokias DX200, Ericssons AXE and Siemens EWSD.  And every
one of those needs specific MML -commands.

Question:

So, we need to get connection between our customer service host
(ATLAS, Unix) and our switches to put MML commands on switches
automatically.  Moreover we are interested about interface between
customer service host and it's users, in the other words what
information customer servicer put in the system (customer home
address, switch card number, ...).

I would be most grateful if you could give me some or any information
that kind of (commercial or your own developed) software or hardware.

Please sent this request forward if you can't answer it yourself. Or
if you know some person/persons who might can answer, sent his/her
e-mail address or telephone number to me, so I can contact to them.


Yours sincerely,

Hannu Komulainen    Telecom Research Centre, Finland
x.400: g=Hannu s=Komulainen ou1=Tkk o=Tele p=Inet a=Mailnet c=Fi
[e-mail]   Telecom Research Centre, Finland

------------------------------

End of TELECOM Digest V13 #132
******************************