OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
PA2AGA > TCPDIG   04.12.96 05:37l 173 Lines 6421 Bytes #-10800 (0) @ EU
BID : TCP_96_255
Read: DG7DAH GUEST
Subj: TCP-Group Digest 96/255
Path: DB0AAB<DB0PV<DB0MAK<DB0HOT<DB0DLN<DB0TUD<DB0NDR<PI8AWT<PI8JYL<PI8WFL<
      PI8MBQ<PI8VNW
Sent: 961203/1908 51012@PI8VNW.#ZH2.NLD.EU
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To  : TCPDIG@EU

Received: from pa2aga by pi1hvh with SMTP
        id AA21857 ; Tue, 03 Dec 96 18:38:52 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.62/7.1) with SMTP
        id AA00000522 ; Tue, 03 Dec 96 19:02:50 MET
Received: from pa2aga-1 by pa2aga with SMTP
        id AA00000502 ; Tue, 03 Dec 96 18:58:21 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.62/7.5.5) with SMTP
        id AA00008669 ; Tue, 03 Dec 96 18:58:19 MET
Date: Tue, 03 Dec 96 18:53:11 MET
Message-Id: <tcp_96_255>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 96/255
X-BBS-Msg-Type: B


TCP-Group Digest            Mon,  2 Dec 96       Volume 96 : Issue  255

Today's Topics:
                           IP v 6 (3 msgs)
                        IPv6 and MTU for 1200
tcp-group->tcp-digest-input@mail.ucsd.edu periodic subscription verification

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: Sun, 1 Dec 1996 08:07:47 -0600
From: "Steve Sampson" <ssampson@oklahoma.net>
Subject: IP v 6

Dennis Rosenauer <rosenave@octoblob.rfnet.sfu.ca> says:

> I think this MTU discussion is kind of pointless.  You just run what
> makes sense for the local RF network in question.

Wow, that's pretty technical.  Can we quote you?

Steve

------------------------------

Date: Sun, 1 Dec 1996 17:02:32 GMT
From: brian@nothing.UCSD.EDU (Brian Kantor)
Subject: IP v 6

>Isn't 256 the maximum packet length for the standard ax25 ??

Yes, officially.  We've been ignoring that restriction for years.
 - Brian

------------------------------

Date: Mon, 02 Dec 1996 00:04:19 -0500
From: "Fred R. Goldstein" <fgoldstein@bbn.com>
Subject: IPv6

At 09:03 PM 11/30/96 GMT, Brian Kantor wrote:
>Since Fred is far from being a Luddite, I'd be interested in more
>discussion of v4 vs v6 and why we might NOT want to change over
>from him and from others.

The race for bigger address space comes about because of the growth in
TCP/IP usage, which really is spectacular.  But we're no longer seeing
addresses being assigned as rapidly as TCP/IP stations come onto the net.

There are two large groups of new TCP/IP users.  One is corporate
intranets", using TCP/IP where in the past they might have used DECnet, SNA
or IPX.  These often use the private address space, like Net 10.  This has
security benefits, making the networks less reachable from undesirables
outside the perimeter.  Firewalls implement Network Address Translation or
application relaying, so there is still public connectivity; the firewall in
turn owns a small window of addresses used for these features, shared by the
whole intranet.

The other large group is The Great Unwashed, public dial-in ISP subscribers.
These as a general rule use dynamic IP, addresses leased for the term of the
phone call.  Since only 2-5% of ISP retail users are usually on line at
once, even given a required "quiet" time after the call, there are many more
potential users (subscribers) than addresses required (active lines).

Dynamic addresses are issued over LANs using DHCP, and over dial-up using
IPCP.  Our old static host addresses, familiar on AMPRnet, are a luxury.
Static still has its role for servers, etc., and for non-broadcast multiple
access media, and other special cases like radio.  But there is less
pressure on the address space than before.  IPv4 can keep going for years to
come.

And given the free market ("cheap") nature of the Internet, who's to say
that anyone will pay for a transition that isn't really necessary?
---
Fred R. Goldstein     k1io    fgoldstein@bbn.com   +1 617 873 3850
Opinions are mine alone.  Sharing requires permission.

------------------------------

Date: Sun, 1 Dec 96 15:56:47 DST
From: "Demetre Ch. Valaris" <sv1uy@nest.sv1uy.ampr.org>
Subject: IPv6 and MTU for 1200

Dear friends,

I have been following the discussion about IPv6 and I saw that someone said
that you only use 256 bytes MTU on 1200 bps links.
Well here in Athens we have been using an MTU of 576 on 1200 bps RF links
over the last 5 years with very few problems!!! When one station has a
problematic RF link, we urge him to have an MTYU of 256 and again this solves
the problem. Everyone else uses 576 and is fully compatible with him (on IPv4
of course).

Again on 9600 bps we use 576 and all seems to work fine here in Athens!!!

I am reading all the discussion about IPv6 with great interest!!!

73 from Demetre - SV1UY - IP coordinator of AMPRnet in Greece
+-----------------------------------------------------------------------------
+
| Demetre Ch. Valaris - SV1UY                      /////  ////  ////  /  ////
|
| e-mail (home) : sv1uy@sv1uy.ampr.org              /   /     ////  /  ////  
|
| e-mail (work) : sv1uy@natbank.ath.forthnet.gr   /   ////  /     /  /       
|
| AX25 packet   : SV1UY@SV1AAW.ATH.GRC.EURO                                  
|
+-----------------------------------------------------------------------------
+
|    Recyclable bits and bytes have been used for the message above.         
|
+-----------------------------------------------------------------------------
+
------------------------------

Date: Sun, 1 Dec 1996 01:55:20 -0800 (PST)
From: ListServ@ucsd.edu (The UCSD Subscription Robot)
Subject: tcp-group->tcp-digest-input@mail.ucsd.edu periodic subscription
verification

unsub tcp-digest-input@mail.ucsd.edu tcp-group

in mail to LISTSERV@UCSD.EDU will unsubscribe you from this mailing list.

If you wish to remain subscribed, DO NOTHING.  Just discard this message.

------------------------------

End of TCP-Group Digest V96 #255
******************************

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


 30.06.2026 16:28:07lGo back Go up