Great Circle Associates Firewalls
(March 1994)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: IP replacement protocols & firewalls
From: "David M. Piscitello" <corecom @ tigger . jvnc . net>
Date: Wed, 16 Mar 94 17:02:32 EST
To: smb @ research . att . com, "Tony DeSimone" <tds @ hoserve . att . com>
Cc: firewalls @ greatcircle . com, jwack @ nist . gov
Reply-to: dave @ corecom . com


>SIPP with source routing requires real authentication.  However, the
>source routing stuff is more important than the corresponding IPv4 feature,
>in my opinion, and so will be harder to filter without loss of functionality.

Steve, just to be clear; the "source routing" we're talking about 
has its origin in the "P" internet protocol (PIP) developed by
Paul Tsuchiya of Bellcore (now Paul Frances of NTT, don't ask it's
a long story...), right? I assume you're talking about the forwarding
table information? It's a bit different than IPv4 traditional source
routing (which is what is available in CLNP/TUBA), but it's also
a part of the SIPP (SIP + PIP = SIPP) proposal that is IMHO entirely
independent of the internet datagram chosen since it has everything
to do with how you route and very little to do with the header bits you
carry the info in.

thanks,

dave
-----
My company endorses very nearly everything I say


Indexed By Date Previous: Telnet application gateway and VMS loginout.exe
From: Tom Irwin - 865-1818 <TRI @ psulias . psu . edu>
Next: Re: SOCKS rftp problem
From: pjh70 @ eng . amdahl . com (Patrick J Horgan)
Indexed By Thread Previous: Re: IP replacement protocols & firewalls
From: smb @ research . att . com
Next: Re: Firewalls Digest V3 #79
From: owen @ netcom . com

Google
 
Search Internet Search www.greatcircle.com