1995-02-05 - Re: The SKRONK protocols (version 0.6)

Header Data

From: sdw@lig.net (Stephen D. Williams)
To: strick@yak.net (strick at The Yak)
Message Hash: 1c2c27297ad81283a62e82a94889ca2ae9297e800d08a589f167ea0fc2116f77
Message ID: <m0rb7Za-0009tFC@sdwsys>
Reply To: <199502051002.CAA01090@nando.yak.net>
UTC Datetime: 1995-02-05 19:02:38 UTC
Raw Date: Sun, 5 Feb 95 11:02:38 PST

Raw message

From: sdw@lig.net (Stephen D. Williams)
Date: Sun, 5 Feb 95 11:02:38 PST
To: strick@yak.net (strick at The Yak)
Subject: Re: The SKRONK protocols (version 0.6)
In-Reply-To: <199502051002.CAA01090@nando.yak.net>
Message-ID: <m0rb7Za-0009tFC@sdwsys>
MIME-Version: 1.0
Content-Type: text/plain


...
> /* "Skronk" is a musical term, for a new-york-ish free-jazz 
>  *   massively saxaphonish kind of music, e.g. John Zorn  
>  */
> 
> 
> ---- THE UDP PROTOCOL BEGINS HERE ----
> 
> THE SKRONK MAP DAEMON
> 
> A skronk map daemon is a UDP service that tells what skronked services are
> available from a site, and what alternate TCP server port numbers they
> use.

UDP won't get through most firewalls.

Build in support for non-transparent firewalls (ie: telnet gatekeeper,
c sys port).

Handle getting access to skronked protocols by using the standard telnet
port and logging in as 'skronk' to get access to a service multiplexer.

Just some suggestions to deal with realities of availability.

...

sdw
-- 
Stephen D. Williams    25Feb1965 VW,OH      sdw@lig.net http://www.lig.net/sdw
Senior Consultant    513-865-9599 FAX/LIG   513.496.5223 OH Page BA Aug94-Feb95
OO R&D AI:NN/ES crypto     By Buggy: 2464 Rosina Dr., Miamisburg, OH 45342-6430
Firewall/WWW srvrs ICBM/GPS: 39 38 34N 84 17 12W home, 37 58 41N 122 01 48W wrk
Pres.: Concinnous Consulting,Inc.;SDW Systems;Local Internet Gateway Co.28Jan95




Thread