Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!sri-spam!mordor!lll-lcc!ames!ucbcad!ucbvax!its63b.ed.ac.uk!adam
From: adam@its63b.ed.ac.uk.UUCP
Newsgroups: mod.protocols
Subject: (none)
Message-ID: <8703060508.AA23602@mcvax.cwi.nl>
Date: Thu, 5-Mar-87 12:05:50 EST
Article-I.D.: mcvax.8703060508.AA23602
Posted: Thu Mar  5 12:05:50 1987
Date-Received: Fri, 13-Mar-87 02:08:40 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26
Approved: protocols@red.rutgers.edu

Newsgroups: comp.protocols
Subject: Re: Numbering Plans
References: <8702251951.AA00974@rutgers.edu>
Reply-To: adam@its63b.ed.ac.uk (ERCF02 Adam Hamilton)
Distribution: world
Organization: I.T. School, Univ. of Edinburgh, U.K.

In article <8702251951.AA00974@rutgers.edu> sullivan@EDN-VAX.ARPA (Pat Sullivan) writes:
>
>Has anyone out there done any thinking about numbering plan
>strategies which would eventually reconcile different addressing
>schemes, such as voice (E.163), ISDN (E.164), data (1822, X.121,
>IP) and eventually lead to a uniform addressing standard?
> .............
>Thanks,
>Pat Sullivan
>Defense Communications Engineering Center
>Reston, VA.

ISO 8348 on the Network Service definition has a Draft Addendum 2 on
Network Layer Addressing.  This proposes a scheme for globally unique
NSAPs which includes X.121, E.163, E.164, F.69 (Telex) and a couple of
others as subsets.  There is (currently) no provision for 1822 or IP.
This document is a must if you want to know what ISO thinks is right
for a global addressing scheme.
				Adam Hamilton