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

Steve Coya <scoya@ietf.org> Thu, 06 July 2000 17:38 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21701; Thu, 6 Jul 2000 13:38:51 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25783; Thu, 6 Jul 2000 13:38:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA25744 for <pso-discuss@pso.icann.org>; Thu, 6 Jul 2000 13:38:48 -0400 (EDT)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106]) by ietf.org (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 <scoya@ietf.org>
To: chiari mario <chiari.hm@flashnet.it>
cc: pso-discuss@pso.icann.org
Subject: Re: [Pso-discuss] (correction) Looking for a layman example on what PSO does.
In-Reply-To: <3.0.5.32.20000706190246.0087cb40@mbox2.flashnet.it>
Message-ID: <Pine.WNT.3.96.1000706132837.-329693D-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: pso-discuss-admin@pso.icann.org
Errors-To: pso-discuss-admin@pso.icann.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: PSO Discussion List <pso-discuss.pso.icann.org>
X-BeenThere: pso-discuss@pso.icann.org

Mario,

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

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.


Steve


>>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
PSO-Discuss@pso.icann.org
http://www.pso.icann.org/mailman/listinfo/pso-discuss