Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!agate!shelby!riacs!nsipo.arc.nasa.gov!medin
From: medin@nsipo.arc.nasa.gov (Milo S. Medin)
Newsgroups: comp.protocols.appletalk
Subject: Re: Global assignment of network numbers
Keywords: AppleTalk network management
Message-ID: <1990Dec18.065106.17895@riacs.edu>
Date: 18 Dec 90 06:51:06 GMT
References: <1990Dec17.180642.22176@ux1.cso.uiuc.edu>
Sender: news@riacs.edu (James A. Woods)
Reply-To: medin@cincsac.arc.nasa.gov (Milo S. Medin)
Organization: NASA Science Internet Project Office
Lines: 14

Actually, the Apple-IP group in the IETF is working on a tunnelling
spec that will operate in very large apple internets.  We have come
to the conclusion that about the only way to make this work 
is use apple net number mapping in the tunnel, ala what Van and company
at LBL have done to build WAAN support.  This obviates the need for
local nets to be consistent with other local apple nets (what I call
Appletalk Classic).  The encapsulation hosts do all the mapping and thus
are the only ones who need to deal with the ugly addressing issues.

The solution should work fairly well, but if you are looking for
elegance, I suggest you give up on appletalk and use IP.

						Thanks,
						    Milo