IPv6 over ATM/NBMA

Grenville Armitage <gja@bellcore.com> Thu, 29 February 1996 04:52 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04814; 28 Feb 96 23:52 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab04808; 28 Feb 96 23:52 EST
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa00736; 28 Feb 96 23:52 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 XAA12988; Wed, 28 Feb 1996 23:51:58 -0500 (EST)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id XAA13326 for ip-atm-out; Wed, 28 Feb 1996 23:46:04 -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 XAA13317 for <ip-atm@nexen.com>; Wed, 28 Feb 1996 23:46:01 -0500 (EST)
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id XAA10930 for <ip-atm@nexen.com>; Wed, 28 Feb 1996 23:45:59 -0500 (EST)
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.9/8.6.10) with ESMTP id XAA00664; Wed, 28 Feb 1996 23:45:54 -0500
Message-Id: <199602290445.XAA00664@thumper.bellcore.com>
To: ip-atm@nexen.com
Cc: gja@thumper.bellcore.com, ipng@sunroof.eng.sun.com
Subject: IPv6 over ATM/NBMA
Date: Wed, 28 Feb 1996 23:45:43 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@bellcore.com>
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

This is a question and heads-up combined:

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.)

cheers,
gja
_________________________________________________________________________
Grenville Armitage                               gja@thumper.bellcore.com
Bellcore, 445 South St.      http://gump.bellcore.com:8000/~gja/home.html
Morristown, NJ 07960 USA          (voice) +1 201 829 2635 {.. 2504 (fax)}