Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?

To: Scott C. Lemon who wrote (30282)	2/12/2000 11:28:00 AM
From: PJ Strifas	Read Replies (2) \| Respond to of 42771

So basically we're talking about "self-regulation" in terms of packet addressing to remove the ability of spoofed packets from traversing from one network to another. This sounds like it could become a very "do-able" solution. I wonder which alliance (IETF, W3C, ISO, ???) would be able to bring all the participants together.... Still, is there nothing that can be done in terms of the IP stack to add "checks/balances" so that tampered packets can be identified and then dropped? Not to force this into a NETWARE discussion but in a NetWare environment (using the Novell Client to log into a Novel network) a user's session has unique identifiers that are used to create and check packets exchanged between a workstation and the network. In this way, packets can be verified in terms of whether or not they have been modified (tampered with) during transmission. Could it be possible that this type of functionality can be worked into the current TCP/IP protocol? Can we add additional layers such as (PKI or) digital certificates to authenticate online sessions at the network, session and/or transport level? (a way to create packet checksums as we have in NetWare?) I am not as fully versed in this topic as I would like to be therefore it may hamper my understanding of what is possible and what is not in the IP world. I surely understand this problem can be "attacked" from more than one angle - perhaps that will be what enables us to find an acceptable solution that balances performance and security. Regards, Peter J Strifas