Re: ATM Forum ATM Addresses for NHRP
Grenville Armitage <gja@thumper.bellcore.com> Mon, 21 August 1995 18:33 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13926;
21 Aug 95 14:33 EDT
Received: from nexen.nexen.com by IETF.CNRI.Reston.VA.US id aa13922;
21 Aug 95 14:33 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by
nexen.nexen.com (8.6.12/8.6.12) with ESMTP id OAA04499;
Mon, 21 Aug 1995 14:20:31 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
OAA09505 for rolc-out; Mon, 21 Aug 1995 14:12:14 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id OAA09494;
Mon, 21 Aug 1995 14:12:10 -0400
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id OAA09687;
Mon, 21 Aug 1995 14:09:36 -0400
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com
(8.6.9/8.6.10) with ESMTP id OAA12170; Mon, 21 Aug 1995 14:10:46 -0400
Message-Id: <199508211810.OAA12170@thumper.bellcore.com>
To: "Andrew G. Malis" <malis@nexen.com>
cc: rolc@nexen.com, gja@thumper.bellcore.com
Subject: Re: ATM Forum ATM Addresses for NHRP
In-reply-to: Your message of Fri, 18 Aug 1995 17:03:50 -0400.
<199508182103.RAA06099@phish.acton.timeplex.com>
Date: Mon, 21 Aug 1995 14:10:44 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@thumper.bellcore.com>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via
ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
[..] >>15 E.164 with NSAP format subaddress (ATM) >> >>However, the format of the encoded address also needs to be specified, >>since it has two variable length portions. I propose a >>straightforward format: >> >>Length of E.164 portion (one octet) >>E.164 portion >>Length of NSAP format portion (one octet) >>NSAP format portion >> >>Any comments before I send the request to IANA? How about borrowing from ATMARP for the contents of address family 15? e.g. 8 bits Type & length of source ATM number 8 bits Type & length of source ATM subaddress qoctets source ATM number roctets source ATM subaddress The T&L fields can be coded as per rfc1577, and infact this would allow address family 15 to cover all three possible ATM address formats. I'm currently working on the IPv6 ND-over-ATM draft and this is the way the Source Link-layer Address and Target Link-layer Address options will be coded for IPv6/ATM interfaces (as AF numbers are not used in NS and NA messages). gja
- ATM Forum ATM Addresses for NHRP Andrew G. Malis
- Re: ATM Forum ATM Addresses for NHRP Grenville Armitage