Re: [Pso-discuss] (correction) Looking for a layman example on what PSO does.

Steve Coya <> Thu, 06 July 2000 17:38 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id NAA21701; Thu, 6 Jul 2000 13:38:51 -0400 (EDT)
Received: from (localhost []) by (8.9.1a/8.9.1) with ESMTP id NAA25783; Thu, 6 Jul 2000 13:38:49 -0400 (EDT)
Received: from (odin []) by (8.9.1a/8.9.1) with ESMTP id NAA25744 for <>; Thu, 6 Jul 2000 13:38:48 -0400 (EDT)
Received: from ( []) by (8.9.1a/8.9.1a) with SMTP id NAA21696; Thu, 6 Jul 2000 13:38:46 -0400 (EDT)
Date: Thu, 6 Jul 2000 13:37:51 -0400 (Eastern Daylight Time)
From: Steve Coya <>
To: chiari mario <>
Subject: Re: [Pso-discuss] (correction) Looking for a layman example on what PSO does.
In-Reply-To: <>
Message-ID: <>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: PSO Discussion List <>


I'm not a technical expert (or any other kind), but I can take a stab at

If one were to look at the construct of certain header records (IP, TCP,
ICMP, etc), there are fields which can contain certain values. Some of
these fields define the set of permissible values from which the
appropriate value is selected/chosen. Many protocol header records include
a space for the inclusion of options,
each of which is assigned a particular value for uniqueness.

For example, in the IP header, there is a IP Version field. There are
also such things as Type of Service fields, option fields, protocol
fields, traffic class fields (in IPv6), etc.

I hope this helps.


>>Due to lack of technical knowledge, I am not sure to understand what
>>'assignment of parameters for Internet protocols' really means. (I
>>understand that that is PSO main business, isn't it?) 
>>Any 'easy to understand'  explanation is very welcome. In particular, I
>>would appreciate a couple of simple examples of the kind: the protocol
>>..... includes the parameters ....., and they are usually fixed in such and
>>such way as ......... 

PSO-Discuss mailing list