Re: IPv6 over ATM/NBMA
Michael Smirnow <smirnow@fokus.gmd.de> Thu, 29 February 1996 16:31 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14928; 29 Feb 96 11:31 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14924; 29 Feb 96 11:31 EST
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa08525; 29 Feb 96 11:31 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id LAA16799; Thu, 29 Feb 1996 11:29:45 -0500 (EST)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id LAA18895 for ip-atm-out; Thu, 29 Feb 1996 11:22:51 -0500 (EST)
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id LAA18886 for <ip-atm@nexen.com>; Thu, 29 Feb 1996 11:22:47 -0500 (EST)
Received: from ceres.fokus.gmd.de (ceres.fokus.gmd.de [192.35.149.15]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id LAA22241 for <ip-atm@nexen.com>; Thu, 29 Feb 1996 11:22:44 -0500 (EST)
Received: from lotos.gmd.de (actually lotos.fokus.gmd.de) by ceres.fokus.gmd.de with SMTP (PP-ICR1v5); Thu, 29 Feb 1996 17:22:09 +0100
Received: by lotos.gmd.de (5.x/SMI-SVR4) id AA18113; Thu, 29 Feb 1996 17:19:45 +0100
Date: Thu, 29 Feb 1996 17:19:45 +0100
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Michael Smirnow <smirnow@fokus.gmd.de>
Message-Id: <9602291619.AA18113@lotos.gmd.de>
To: ip-atm@nexen.com
Subject: Re: IPv6 over ATM/NBMA
Cc: ipng@sunroof.eng.sun.com
X-Sun-Charset: US-ASCII
X-Orig-Sender: owner-ip-atm@nexen.com
Precedence: bulk
X-Info: Submissions to ip-atm@nexen.com
X-Info: [Un]Subscribe requests to majordomo@nexen.com
X-Info: Archives via http://cell-relay.indiana.edu/cell-relay/archives/IPATM/IPATM.html
On G. Armitage's message (Thu Feb 29 06:04:28 1996 - see below): except Armitage's contributions and well known RFCs (from IPATM, IDMR, ROLC,...) I found also useful (at least for me) the following: Endpoint Identifier Destination Option [draft-ietf-nimrod-eid-00]: it treats routing related info (endpoint IDs) separately from topology (locators) - results in scalability; DNS Resource Records for Nimrod Routing Architecture [draft-ietf-nimrod-dns-01]: DNS Resource Records descriptions for the above; IPv6 Stateless Address Autoconfiguration [draft-ietf-addrconf-ipv6-auto-06]: proposes how host can autoconfigure its interfaces in IPv6 An ATMARP Client Autoconfiguration [draft-marcinik-ipatm-auto-arp-00]: cooperation of Classical ATMARP servers (simple cache consistency). Michael > Most people are probably aware that the IP-ATM working group's > charter now includes IPv6 over ATM. We have a session in LA > covering this very topic because it encompasses a number of > inter-twined areas. We had some vigorous discussions during > late Dec, early January on the issue of generating link-local > tokens (interface IDs), and there's an outstanding issue of > how to provide Neighbour Discovery (or how _much_ to provide). > > I was poking around looking for the relevant I-Ds to pre-read > before this meeting and came up with: > > draft-ietf-ipatm-ipv6nd-01.txt > draft-schulter-ipv6atm-framework-01.txt > and > draft-ahl-ipv6-nbma-00.txt > > My heads-up is to request people interested in this area to > pre-read these I-Ds before the meeting. > > My question is to people interested in this area - is there > a relevant I-D I've missed? Could you post additions here? > (e.g. I suspect draft-ietf-ipngwg-iid-01.txt may have some > impact on any token generation scheme, but I haven't thought > it through yet.)
- IPv6 over ATM/NBMA Grenville Armitage
- Re: IPv6 over ATM/NBMA Andrew G. Malis
- Re: IPv6 over ATM/NBMA Michael Smirnow