(sipp) Revised NSAPA mapping (fwd)

Brian Carpenter CERN-CN <brian@dxcoms.cern.ch> Tue, 19 July 1994 07:47 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00380; 19 Jul 94 3:47 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00376; 19 Jul 94 3:47 EDT
Received: from Sun.COM by CNRI.Reston.VA.US id aa00470; 19 Jul 94 3:40 EDT
Received: from Eng.Sun.COM (zigzag.Eng.Sun.COM) by Sun.COM (sun-barr.Sun.COM) id AA07396; Tue, 19 Jul 94 00:38:49 PDT
Received: from sunroof2.Eng.Sun.COM by Eng.Sun.COM (4.1/SMI-4.1) id AA13113; Tue, 19 Jul 94 00:39:47 PDT
Received: by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA00712; Tue, 19 Jul 94 00:40:47 PDT
Received: from Eng.Sun.COM (engnews1) by sunroof2.Eng.Sun.COM (4.1/SMI-4.1) id AA00706; Tue, 19 Jul 94 00:40:41 PDT
Received: from Sun.COM (sun-barr) by Eng.Sun.COM (4.1/SMI-4.1) id AA06836; Tue, 19 Jul 94 00:38:28 PDT
Received: from dxmint.cern.ch by Sun.COM (sun-barr.Sun.COM) id AA07328; Tue, 19 Jul 94 00:38:20 PDT
Received: from dxcoms.cern.ch by dxmint.cern.ch (5.65/DEC-Ultrix/4.3) id AA03969; Tue, 19 Jul 1994 09:38:17 +0200
Received: by dxcoms.cern.ch (5.65/DEC-Ultrix/4.3) id AA18377; Tue, 19 Jul 1994 09:38:14 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Brian Carpenter CERN-CN <brian@dxcoms.cern.ch>
Message-Id: <9407190738.AA18377@dxcoms.cern.ch>
Subject: (sipp) Revised NSAPA mapping (fwd)
To: sipp@sunroof.eng.sun.com
Date: Tue, 19 Jul 1994 09:38:13 +0200
X-Mailer: ELM [version 2.4 PL22]
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Content-Length: 4088
X-Orig-Sender: owner-sipp@sunroof.eng.sun.com
Precedence: bulk
Reply-To: sipp@sunroof.eng.sun.com

SIPPers,

FYI, this is the current version of the NSAPA-in-128 bits mapping
proposal (and its converse). The version summarised in the SIPP ROAD
draft is slightly out of date, and this version will also be modified
further.

Regards,
	Brian.Carpenter@cern.ch (brian@dxcoms.cern.ch)
			 voice +41 22 767 4967, fax +41 22 767 7155

>--------- Text sent by brian follows:
From brian Mon Jul 18 14:10:51 1994
Subject: Revised NSAPA mapping
To: tuba@lanl.gov, ipng@cmf.nrl.navy.mil
Date: Mon, 18 Jul 1994 14:10:51 +0200 (MET DST)
Reply-To: Brian.Carpenter@cern.ch
X-Mailer: ELM [version 2.4 PL22]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 3375      

[Acknowledgements for useful comments: Scott Bradner, John Curran,
Bob Hinden, Yakov Rekhter. And for the main improvement: Cyndi Jung.]

BTW, I haven't bothered to write down a mapping for NSAPAs inside
the BigTen 24-byte address format, but it is clearly trivial.

  Brian

1. NSAPAs inside a 16-byte IPng address


 The main goal of this embedding is to allow pre-existing  NSAPA
 allocations, profiled for CLNP, to be re-used for IPng routing. It does
 not offer a mapping for arbitrary NSAPAs.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 0-3  |1 1 0 0 0 0|x x| AFcode| IDI (last 3 digits)   |Prefix(octet 0)|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 4-7  |             Prefix (octets 1 through 3)       | Area (octet 0)|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 8-11 | Area (octet 1)|    ID (octets 0 through 2)                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 12-15|       ID (octets 3 through 5)                 |   NSEL        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+



 The AFcode is 1111 (hexadecimal F) to represent AFI code 39 (DCC, digital
 country code). Otherwise, AFI code 47 (ICD, international code
 designator) is implicit and AFcode is the first digit of the ICD.

 The longest CLNP prefixes in use today appear to be 4 octets, in
 NORDUNET (the Nordic academic network). Thus the semantics of existing
 20-octet NSAPAs are fully mapped. DECnet/OSI address semantics are also
 fully mapped.

 The NSEL octet is retained. It is of no use for TCP and UDP traffic,
 but would be of use if a future revision of CLNP used the same format.
 The alignment is similar to that for 20-octet NSAPAs.


2. 16-byte IPng addresses inside a 20-octet NSAPA

 The main goal of this embedding is to allow CLNP packets that encapsulate
 IPng packets to be routed in a CLNP network using the IPng address
 architecture. An arbitrary number of bytes of the IPng address can be
 used as a CLNP routing prefix.

 The first three octets are an IDP meaning "this NSAPA embeds a
 16 byte IPng address" and the last octet is a dummy selector.
 Sorry about the alignment, but it seems very risky to overload
 the selector octet.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 0-3  |  AFI = 47     |   ICD = ISoc (TBD)            | IPng (byte 0) |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 4-7  |             IPng (bytes 1-4)                                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 8-11 |             IPng (bytes 5-8)                                  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 12-15|             IPng (bytes 9-12)                                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 16-19|       IPng (bytes 13-15)                      |  NSEL = dummy |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


---


 ------------------------------------------------------------------------------
IETF SIPP Working Group - Archives:  parcftp.xerox.com:/pub/sipp
Unsubscribe:	unsubscribe sipp		(as message body, not subject)
Direct all administrative requests to majordomo@sunroof.eng.sun.com