| |
PA2AGA > TCPDIG 02.12.96 08:35l 180 Lines 6542 Bytes #-10802 (0) @ EU
BID : TCP_96_253B
Read: DG7DAH GUEST
Subj: TCP-Group Digest 96/253B
Path: DB0AAB<DB0MWS<DB0RBS<DB0SAO<DB0NDR<PI8AWT<PI8JYL<PI8WFL<PI8VNW
Sent: 961130/2330 49237@PI8VNW.#ZH2.NLD.EU
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21711 ; Sat, 30 Nov 96 22:06:17 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
id AA00000385 ; Sat, 30 Nov 96 22:42:14 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00000364 ; Sat, 30 Nov 96 22:39:38 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.5.5) with SMTP
id AA00008642 ; Sat, 30 Nov 96 22:39:36 MET
Date: Sat, 30 Nov 96 22:36:01 MET
Message-Id: <tcp_96_253B>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 96/253B
X-BBS-Msg-Type: B
I thought making the SSID/space bit two bytes would be better so things
fit neater.
So what about the <something that means ampr> ?
Back to Steve:
> global provider?? Would UCSD be willing to be the Global Provider for
> AMPR/6?
I think this would be the best spot for it, as UCSD (or is it Brian) looks
after the 44 network numbers. All we would need is a block that allows us
40 bytes to play with.
- Craig vk2xlz
--
// /\ | | | Craig Small VK2XLZ @home: csmall@gonzo.triode.net.au
||==||===|==|=| [44.136.13.17] @play: csmall@gonzo.vk2xlz.ampr.org
\\ \/ | | | @work: csmall@staterail.nsw.gov.au
------------------------------
Date: Fri, 29 Nov 1996 12:08:46 -0600 (CST)
From: Jeffrey Austen <JRA1854@tntech.edu>
Subject: IPv6
>> computed MAC addresses for ARP, etc. That's probably a better route. That
>> a callsign and SSID will be converted to a 48 bit (ethernet compatible) MAC
>> address. This comined 128 bit address being refered to as a Unicast
>> address.
>
> I also believe that crunching the callsign into the IP address would be a
> good idea; but what happens when I run more than one system? So something
> like a 'selector byte', SSID or whatever would be useful.
Why should the callsign be put into the MAC address? This may eliminate the
need for ARP, but if ARP doesn't work (or is too much overhead) on the
network then something is drastically wrong and needs to be fixed.
An identifier is neither a locator nor an interface address.
Jeff, k9ja
------------------------------
Date: Fri, 29 Nov 1996 20:02:19 GMT
From: brian@nothing.UCSD.EDU (Brian Kantor)
Subject: IPv6
The callsign may be put into the V6 address, just as is suggested for
encoding of other MAC-level addresses such as Ethernet, but it is by
no means NECESSARY.
The nice thing about IPv6 is that the address fields are so big that
we can waste them even more inefficiently than we're already doing with
the v4 addresses.
- Brian
------------------------------
Date: Fri, 29 Nov 1996 20:08:46 +0000 (GMT)
From: Alan Cox <alan@cymru.net>
Subject: IPv6
> > I also believe that crunching the callsign into the IP address would be a
> > good idea; but what happens when I run more than one system? So something
> > like a 'selector byte', SSID or whatever would be useful.
>
> Why should the callsign be put into the MAC address? This may eliminate the
> need for ARP, but if ARP doesn't work (or is too much overhead) on the
> network then something is drastically wrong and needs to be fixed.
Pick up the Ipv6 RFC's and look at the requirements for a Link local
address. To start with ARP is abolished in IPv6 for IPv6 neighbour
discovery schemes based on Link local addresses.
Alan
------------------------------
Date: Fri, 29 Nov 1996 17:02:19 -0500
From: "Fred R. Goldstein" <fgoldstein@bbn.com>
Subject: IPv6
Well not to rain on anybody's parade, but how do we know that IPv6 is
actually going anywhere? Proclaiming an AMPRnet "flag day" just doesn't
make sense.
IPv6 has a lot of supporters, but a lot of detractors too. Without taking
sides too blatantly, I'll summarize the problems with it. Basically, you go
through a lot of work doing a new protocol and don't solve all of the
problems that you might want to solve. IPv6 takes a lot to implement, both
at the software-writing and network-transitioning end, and may not really do
what needs to be done. Now maybe that's not a valid assessment, but it
carries weight in the Internet community, which is by no means universal in
support of wholesale IPv6 transition.
We had a "flag day" once, The ARPAnet shut off NCP and required TCP/IP on
New Year's Day 1983. This affected a few hundred hosts. I don't think
it'll happen again; a graceful phase-in will be required.
Why no need for IPv6? Too many workarounds keep IPv4 alive for a long time.
Classless routing makes address assignment much more efficient. (The entire
Net 64-126 upper half of the "Class A" space is reserved. Hmmm.) Corporate
networks are moving more heavily towards the private space (e.g., Net 10)
with narrow (such a one Class C) "visible" windows using Network Address
Translation or application-layer gateways (firewalls).
AMPRnet is by no means making full use of its Class A space. It's not even
connected to the outside. It's the most bandwidth-constrained of all the
major networks (though CDPD is close) so the long headers matter. Thus a
transition to IPv6 adds pain for little if any gain.
I just don't see it.
fred k1io
---
Fred R. Goldstein k1io fgoldstein@bbn.com +1 617 873 3850
Opinions are mine alone. Sharing requires permission.
------------------------------
Date: Fri, 29 Nov 1996 17:56:09 -0600 (CST)
From: Robert E Brose II <bob@kunk.n0qbj.ampr.org>
Subject: tfslip2.7b
Being the curious type, I've downloaded and burnt a rom for the TNC2
version of slip posted here a while ago.
Interestingly, the TNC shows signs of life when powered up but the
RS232 lines are acting strange, kind of like a continuous break condition
on tx. I am certain that the rom is programmed correct and it does the
same thing on 2 different, operational tnc 2's.
Does anyone have this working? Since there are no docs, are there hints about
usuage somewhere?
Thanks,
Bob
--
Robert E. Brose II / N0QBJ / Amateur Radio IP Address Coordinator for
Minnesota
Amprnet: bob@n0qbj-uhf.ampr.org (44.94.9.9)
WWW (Amprnet only): http://kunk.n0qbj.ampr.org/
Packet: N0QBJ@WB0GDB.#STP.MN.USA.NOAM
------------------------------
End of TCP-Group Digest V96 #253
******************************
You can send your message for this bulletin
to: tcp-group@pa2aga on .AMPR.ORG-net
or: tcpaga@pi8vnw.#zh2.nld.eu on BBS-net
------
NOT TO: pa2aga@pa2aga or pa2aga@pi8vnw.#zh2.nld.eu PLEASE!!
It will get posted automatically within a few days
Read previous mail | Read next mail
| |
