Re: ipv6nd-02.txt & autoconfig
Grenville Armitage <gja@bellcore.com> Thu, 09 May 1996 16:40 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18612; 9 May 96 12:40 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18608; 9 May 96 12:40 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa10962; 9 May 96 12:40 EDT
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 MAA15972; Thu, 9 May 1996 12:31:05 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id MAA09827 for ip-atm-out; Thu, 9 May 1996 12:20:21 -0400 (EDT)
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id MAA09818 for <ip-atm@nexen.com>; Thu, 9 May 1996 12:20:17 -0400 (EDT)
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id MAA15880 for <ip-atm@nexen.com>; Thu, 9 May 1996 12:20:15 -0400 (EDT)
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.12/8.6.11) with ESMTP id MAA10091; Thu, 9 May 1996 12:19:37 -0400
Message-Id: <199605091619.MAA10091@thumper.bellcore.com>
To: Albert Manfredi <manfredi@engr05.comsys.rockwell.com>
cc: gja@bellcore.com, IP-ATM Working Group <ip-atm@nexen.com>, gja@thumper.bellcore.com
Subject: Re: ipv6nd-02.txt & autoconfig
In-reply-to: Your message of Thu, 09 May 1996 10:31:40 -0700. <31922BFC.7019@engr05.comsys.rockwell.com>
Date: Thu, 09 May 1996 12:19:20 -0400
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
Disclaimer: This is grumpy response. >>> The SEL field is for _internal_ routing of an incoming call >>> once the physical ATM interface has been located (routed to) using >>> the top 19 bytes. i.e. the top 19 bytes denote the physical host, >>> and SEL can be used internally to the physical hosts (end systems) >>> - aka logical ATM interfaces. This not a new idea. >> >>I guess my point is that the SEL should be viewed as an ATM-only neat-o >>feature. It should not be used to map to different IP addresses. Bert, did you actually digest the paragraph you responded to? SEL field _is_ a neat-o feature, but it _is_ used to create logical ATM interfaces. End of story. Over a logical ATM interface you can layer instances of whatever higher layer interfaces you damn well please. You can have multiprotocol interfaces, or you can decide that only one higher layer protocol is associated with the internal termination point represented by a given SEL. This has nothing to do with IP. What _does_ have something to do with IPv6 is that since multiple IPv6 interfaces are likely to exist, and require unique link-local IPv6 addresses despite being associated with the same physical ATM NIC, you need some mechanism of constructing magic 48 bit tokens. How the underlying logical _ATM_ interface is identified during call SETUP is orthogonal. Lets focus on that, shall we? (btw, for at least one real world example check out FORE's qaa* interfaces, and their association with the local ESI+SEL.) [..] >>For example, using the AEREQUIPA model, the SEL would only be used if >>the two end systems are both ATM. After all, you've already 19 bytes of >>ATM address to play with, compared with the 16 bytes of IPv6. What's the >>big deal? I give up. I can't see your point. gja
- ipv6nd-02.txt & autoconfig Albert Manfredi
- Re: ipv6nd-02.txt & autoconfig Grenville Armitage
- Re: ipv6nd-02.txt & autoconfig schulter
- Re: ipv6nd-02.txt & autoconfig Albert Manfredi
- Re: ipv6nd-02.txt & autoconfig Grenville Armitage
- Re: ipv6nd-02.txt & autoconfig schulter
- Re: ipv6nd-02.txt & autoconfig Grenville Armitage
- Re: ipv6nd-02.txt & autoconfig Masataka Ohta
- Re: ipv6nd-02.txt & autoconfig Andrew Smith
- Re: ipv6nd-02.txt & autoconfig Albert Manfredi
- Re: ipv6nd-02.txt & autoconfig schulter
- Re: ipv6nd-02.txt & autoconfig Albert Manfredi
- Re: ipv6nd-02.txt & autoconfig Andrew Smith
- Re: ipv6nd-02.txt & autoconfig schulter
- Re: ipv6nd-02.txt & autoconfig Andrew Smith
- Re: ipv6nd-02.txt & autoconfig Albert Manfredi
- Re: ipv6nd-02.txt & autoconfig Andrew Smith
- Re: ipv6nd-02.txt & autoconfig Grenville Armitage
- Re: ipv6nd-02.txt & autoconfig Grenville Armitage
- Re: ipv6nd-02.txt & autoconfig Masataka Ohta
- Re: ipv6nd-02.txt & autoconfig Juha Heinanen
- Re: ipv6nd-02.txt & autoconfig Brian Carpenter CERN-CN
- Re: ipv6nd-02.txt & autoconfig Eric W. Gray
- Re: ipv6nd-02.txt & autoconfig Eric W. Gray
- Re: ipv6nd-02.txt & autoconfig Grenville Armitage