Article View: dnet.ham
Article #138Re: RFC1226 - Internet Protocol Encapsulation of AX.25 Frames
From: Tim Shepard
Date: Tue, 14 May 1991 21:42
Date: Tue, 14 May 1991 21:42
16 lines
1190 bytes
1190 bytes
On a campus network, there's no real secure method of determining where the packet came from at the IP level. If a campus network (or other open IP network) were used for tunneling of frames, what mechanism would be required to verify the authenticity of the AX.25 frame well enough to be legal on the air? This is an issue regardless of whether the campus network is carrying AX.25 in IP or IP in IP or just routing IP. Right? (DES based signatures with a private key on both ends of the tunnel?) Is there a corresponding RFC for the IP in IP stuff that I see was added to NOS 910423? -Tim
Technical Details
Message-ID:
<9105141926.AA12210@PTT.LCS.MIT.EDU>Path:
arc1-ca.pugleaf.net!gmdzi!unido!infoac!news-mail-gatewayReferences:
<33863@ucsd.Edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 12f11c,a6c936a51a0f492a X-Google-Attributes: gid12f11c,public X-Google-ArrivalTime: 1991-05-15 02:00:54 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!infoac!news-mail-gateway From: shep@lcs.mit.EDU (Tim Shepard) Newsgroups: dnet.ham Subject: Re: RFC1226 - Internet Protocol Encapsulation of AX.25 Frames Message-ID: <9105141926.AA12210@PTT.LCS.MIT.EDU> Date: 14 May 91 21:42:32 GMT References: <33863@ucsd.Edu> Sender: shep@ALLSPICE.LCS.MIT.EDU Organization: RMI Net INFO.box Systems * Aachen * Hamburg * Flensburg Lines: 16