| |
PA2AGA > TCPDIG 02.12.96 08:20l 176 Lines 6695 Bytes #-10802 (0) @ EU
BID : TCP_96_253A
Read: DG7DAH GUEST
Subj: TCP-Group Digest 96/253A
Path: DB0AAB<DB0PV<DB0MAK<DB0BOX<DB0FP<DB0SWR<DB0RBS<DB0SAO<DB0NDR<PI8AWT<
PI8JYL<PI8WFL<PI8VNW
Sent: 961130/2328 49236@PI8VNW.#ZH2.NLD.EU
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21709 ; Sat, 30 Nov 96 22:03:39 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
id AA00000382 ; Sat, 30 Nov 96 22:41:59 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00000363 ; Sat, 30 Nov 96 22:39:28 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.5.5) with SMTP
id AA00008641 ; Sat, 30 Nov 96 22:39:26 MET
Date: Sat, 30 Nov 96 22:36:00 MET
Message-Id: <tcp_96_253A>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 96/253A
X-BBS-Msg-Type: B
TCP-Group Digest Sat, 30 Nov 96 Volume 96 : Issue 253
Today's Topics:
AX.25 PID for IPv6 (2 msgs)
IPv6 (6 msgs)
tfslip2.7b
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Fri, 29 Nov 1996 17:16:17 GMT
From: brian@nothing.UCSD.EDU (Brian Kantor)
Subject: AX.25 PID for IPv6
There seems to be some confusion over who administrates PID assignments
these days, so I'm going to just pick one and we'll make it official by
using it a lot.
I can't find any record of 0xC6 being used by any other protocol. Do any
of you know of any use of that PID? If nothing turns up, we'll go with it.
Please let me know.
- Brian
------------------------------
Date: Fri, 29 Nov 1996 15:21:14 -0600
From: "Steve Sampson" <ssampson@oklahoma.net>
Subject: AX.25 PID for IPv6
That's fine.
Although 0xC5 would be better, as it connotes a huge
carrier with an oversized cargo. (as in the airplane) :-)
----------
> There seems to be some confusion over who administrates PID assignments
> these days, so I'm going to just pick one and we'll make it official by
> using it a lot.
>
> I can't find any record of 0xC6 being used by any other protocol. Do any
> of you know of any use of that PID? If nothing turns up, we'll go with
it.
------------------------------
Date: Fri, 29 Nov 1996 10:01:34 +1100 (EST)
From: csmall@gonzo.triode.net.au (Craig Small)
Subject: IP v 6
Paul L Taylor typed:
>
> >
> > I propose that we set a goal of transitioning to IPv6 by Jan 1 2001.
> > That's only 5 years away. Do you think we can do it?
> > - Brian
> >
>
> Following the thread of current discussions I think some of the current
> Radio Amateurs will wait for some of the "movers and shakers" to do it for
> them Brian :-)
This will be the only way it will happen. I would be very surprised if many
users knew that IP had versions, let alone that IPv6 was around. They'll
know when it appears on the tellie; "Immenent doom for Internet" or similar.
> I see no reason why we cannot achieve your goal, is there a task force
> that the radio amateurs can model on the IETF to implement it or are you
> discussing this elsewhere Brian. Or was that a prod to discuss the matter.
Are there really that many issues that are different from the Internet? I
know we use some different software.
> Some discussion has of course occured in small groups here in UK and
> Europe, I have personally steered some meetings to be aware of the
> consequences of the adoption of v6 in the near future.
What are the consequences? I'd like to start letting people around here
know.
- 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 10:22:28 +1100 (EST)
From: csmall@gonzo.triode.net.au (Craig Small)
Subject: IPv6
Steve Sampson typed:
>
> Just a quick glance at RFC-1883, and I see the address's are 128 bits
> The complete IP header is 40 bytes (2 address blocks of 16 bytes each,
> and 2 control blocks of 8 bytes total). This doesn't seem too wild,
> considering that packet radio will most likely be based on Spread Spectrum
> devices at 100 kbps or better. So the consideration is that, anything less
> than 100 kbps is a below the IPv6 networking minimum. When you look at
> the Extension Header, you just know those are going to be used a lot, and
> these are probably another 40 bytes...
>
> Seems like there is never a week that goes by, that someone wants to
> have their Windows hooked up to a TNC. So the least common denominator
> should probably be a high level language. One that is portable to all
> platforms (Intel, Motorola, DEC). Maybe even Object Oriented :-) Well,
> you know where I'm headed anyway, and it smells like coffee...
>
> TAPR is actively involved in SS, and plans to offer a 900 MHz radio for
> experimentation (guess that leaves out Colorado, New Mexico, portions of
> Texas and Wyoming. Or is that old rule obsolete, as 900 MHZ phones
> are probably there. 97.303(g) in my 1990 rule book, guess I need something
> a little more recent).
and all of Australia, unless it can be squeezed down to 444 MHz or up to 1.2
GHz
> 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.
So that's 6 bytes gone, I was wondering if, considering there are nice
boundaries for IPv4 how about encoding the existing IPv4 middle two numbers?
Perhaps an example makes it a bit easier;
My call is VK2XLZ, my IPv4 address is 44.136.13.17
"VK2XLZ" = { 0x56, 0x4b, 0x32, 0x58, 0x4c, 0x5a }
136.13 = { 0x5e, 0x0b}
So, a suggested IPv6 address could be;
<something that means ampr>:5e0b:564b:3258:4c5a:0000
| | | | |
136.13 | | | |
VK 2X LZ |
space/SSID
To be continued in digest: tcp_96_253B
Read previous mail | Read next mail
| |
