Re: redo the nSAP address allocation plans?
A.A.L.Reijnierse@research.ptt.nl Mon, 19 September 1994 11:01 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01396; 19 Sep 94 7:01 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01392; 19 Sep 94 7:01 EDT
Received: from mailhost.lanl.gov by CNRI.Reston.VA.US id aa03216; 19 Sep 94 7:01 EDT
Received: from noc-gw.lanl.gov by mailhost.lanl.gov (8.6.8.1/1.2) id FAA07398; Mon, 19 Sep 1994 05:01:07 -0600
Received: by noc-gw.lanl.gov (8.6.8.1/SMI-4.1) id FAA24164; Mon, 19 Sep 1994 05:00:55 -0600
Received: from mailhost.lanl.gov by noc-gw.lanl.gov (8.6.8.1/SMI-4.1) id FAA24161; Mon, 19 Sep 1994 05:00:55 -0600
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: A.A.L.Reijnierse@research.ptt.nl
Received: from dnlts0.research.ptt.nl by mailhost.lanl.gov (8.6.8.1/1.2) id FAA07387; Mon, 19 Sep 1994 05:00:50 -0600
Received: from alex (alex.research.ptt.nl) by research.ptt.nl (PMDF V4.3-11 #2928) id <01HHAPQKZ86O9YFJP4@research.ptt.nl>; Mon, 19 Sep 1994 13:01:38 +0200
Date: Mon, 19 Sep 1994 12:52:02 -0000
Subject: Re: redo the nSAP address allocation plans?
X-Orig-Sender: Alex Reijnierse <A.A.L.Reijnierse@research.ptt.nl>
To: Brian Carpenter CERN-CN <brian@dxcoms.cern.ch>
Cc: wg-llt-clns@rare.nl, sn3plus-clns@surfnet.nl, tuba@lanl.gov
Message-id: <Chameleon.4.01.1.940919130115.reynier@alex>
X-Envelope-to: tuba@Lanl.GOV
MIME-version: 1.0
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
Content-type: TEXT/PLAIN; CHARSET="US-ASCII"
Content-transfer-encoding: 7bit
Hello Brian, >> I have designed DCC and ICD NSAP structures for EMPB/EuropaNET that >> include 18 and 20 octets NSAPs respectively. The ICD NSAPs are not >> in use yet, the DCC NSAPs are. Upon request of EMPB i will try to >> create "light" :-) versions of these structures. >> >If you do, then please try to do it in terms of the mapping >described in draft-carpenter-ip6-nsap-map-00.txt and let >us know whether it works. > >However it is FAR too soon to do this except as a paper exercise. >Despite having co-authored the NSAP mapping proposal for IPv6, >I am not yet convinced that it is any use or that it will ever >be standardised. There are several alternative approaches to >OSI/IPv6 under discussion. I agree. Like i said, i will only do this upon request of EMPB. I will await the outcome of the alternative approaches. I still cannot understand why they just didn't choose SIPP with NSAP addresses. It seems like such a waste of effort if we have to create new address structures, addressing authorities, application forms, databases, address encapsulation standards etc. Why not add 4 octets and use NSAPs. It is so marginal a change. Sigh..... - Alex ----------------------------------------------- Name: Alex Reijnierse Organisation: PTT Research Address: P.O. Box 421 2260 AK Leidschendam The Netherlands E-mail: A.A.L.Reijnierse@research.ptt.nl Date: 09/19/94 MIME OK! Time: 12:52:02 -----------------------------------------------
- RE: redo the nSAP address allocation plans? A.A.L.Reijnierse
- Re: redo the nSAP address allocation plans? Brian Carpenter CERN-CN
- Re: redo the nSAP address allocation plans? A.A.L.Reijnierse
- Re: redo the nSAP address allocation plans? Juha Heinanen
- Re: redo the nSAP address allocation plans? Brian Carpenter CERN-CN
- Re: redo the nSAP address allocation plans? Juha Heinanen
- Re: redo the nSAP address allocation plans? rcoltun
- Re: redo the nSAP address allocation plans? Juha Heinanen