From pso-discuss-admin@pso.icann.org Thu Jul 6 12:30:22 2000 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 MAA20212; Thu, 6 Jul 2000 12:30:21 -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 MAA24773; Thu, 6 Jul 2000 12:30:19 -0400 (EDT) Received: from relay.flashnet.it (root@ems.flashnet.it [194.247.160.44]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA24746 for ; Thu, 6 Jul 2000 12:30:17 -0400 (EDT) Received: from oemcomputer (ip118.pool-250.cyb.it [195.191.1.118]) by relay.flashnet.it (EMS-RELAY/8.10.0) with SMTP id e66GUFm24337 for ; Thu, 6 Jul 2000 18:30:16 +0200 Message-Id: <3.0.5.32.20000706183708.008799c0@mbox2.flashnet.it> X-Sender: fn035144@mbox2.flashnet.it X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 06 Jul 2000 18:37:08 +0200 To: pso-discuss@pso.icann.org From: chiari mario Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [Pso-discuss] Looking for a layman example on what PSO does. 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 X-BeenThere: pso-discuss@pso.icann.org Dear PSO, I am trying to write a document on what ICANN and related SO are and do. I am writing for layman reader who is very interested in Internet and could be interested to join the ICANN's at large membership. 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 ......... I have given a look at RFC 1340 : ASSIGNED NUMBERS, but I couldn't make sense of it. I really appreciate any advise on this matter. Thanks Regards mario chiari (from Parma, Italy) _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss From pso-discuss-admin@pso.icann.org Thu Jul 6 12:55:49 2000 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 MAA20907; Thu, 6 Jul 2000 12:55:49 -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 MAA25145; Thu, 6 Jul 2000 12:55:46 -0400 (EDT) Received: from relay.flashnet.it (root@ems.flashnet.it [194.247.160.44]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA25108 for ; Thu, 6 Jul 2000 12:55:44 -0400 (EDT) Received: from oemcomputer (ip118.pool-250.cyb.it [195.191.1.118]) by relay.flashnet.it (EMS-RELAY/8.10.0) with SMTP id e66Gthm17153 for ; Thu, 6 Jul 2000 18:55:43 +0200 Message-Id: <3.0.5.32.20000706190246.0087cb40@mbox2.flashnet.it> X-Sender: fn035144@mbox2.flashnet.it X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 06 Jul 2000 19:02:46 +0200 To: pso-discuss@pso.icann.org From: chiari mario Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [Pso-discuss] (correction) Looking for a layman example on what PSO does. 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 X-BeenThere: pso-discuss@pso.icann.org Please reply to chiari.hm@flashnet.it **************************************** Dear PSO, I am trying to write a document on what ICANN and related SO's are and do. I am writing for layman readers who are very interested in Internet and could be interested to join the ICANN's at large membership. 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 ......... I have given a look at RFC 1340 : ASSIGNED NUMBERS, but I couldn't make sense of it. I really appreciate any advise on this matter. Thanks Regards mario chiari (from Parma, Italy) _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss From pso-discuss-admin@pso.icann.org Thu Jul 6 13:38:51 2000 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 ; 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 To: chiari mario 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: 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 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 From pso-discuss-admin@pso.icann.org Fri Jul 7 14:20:33 2000 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 OAA08528; Fri, 7 Jul 2000 14:20:33 -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 OAA19665; Fri, 7 Jul 2000 14:20:31 -0400 (EDT) Received: from relay.flashnet.it (root@ems.flashnet.it [194.247.160.44]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19634 for ; Fri, 7 Jul 2000 14:20:28 -0400 (EDT) Received: from oemcomputer (ip130.pool-250.cyb.it [195.191.1.130]) by relay.flashnet.it (EMS-RELAY/8.10.0) with SMTP id e67IKJ306749; Fri, 7 Jul 2000 20:20:19 +0200 Message-Id: <3.0.5.32.20000707201347.007c4100@mbox2.flashnet.it> X-Sender: fn035144@mbox2.flashnet.it (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 07 Jul 2000 20:13:47 +0200 To: Steve Coya From: chiari mario Subject: Re: [Pso-discuss] Looking for a layman example on what PSO does. Cc: pso-discuss@pso.icann.org In-Reply-To: References: <3.0.5.32.20000706190246.0087cb40@mbox2.flashnet.it> 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 X-BeenThere: pso-discuss@pso.icann.org Steve thanks for your reply. It helps, though I am trying do write a less abstract statement. Would you say that the following statement conveys a correct understanding of the matter of fact: ---- the Internet protocol contains numerous parameters, for example to identify the character set of a text, or a operating system. (A character set is a set of conventions to code a traditional alphabet, e.g. latin, cyrillic, japanese). The values of these parameters need to be assigned uniquely. ICANN/PSO is to make those unique assignments and to maintain a registry of the currently assigned values. (here I am cutting & pasting statements from IANA's web site) mario ps do you have a two lines definition of what a port is? At 13.37 06/07/00 -0400, Steve Coya wrote: > >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 From pso-discuss-admin@pso.icann.org Fri Jul 7 14:28:55 2000 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 OAA08922; Fri, 7 Jul 2000 14:28:55 -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 OAA19920; Fri, 7 Jul 2000 14:28:53 -0400 (EDT) Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA19886 for ; Fri, 7 Jul 2000 14:28:51 -0400 (EDT) Received: from postal.research.att.com (postal.research.att.com [135.207.23.30]) by mail-blue.research.att.com (Postfix) with ESMTP id B75324CE0B; Fri, 7 Jul 2000 14:28:45 -0400 (EDT) Received: from smb.research.att.com (sigaba.research.att.com [135.207.23.169]) by postal.research.att.com (8.8.7/8.8.7) with ESMTP id OAA22297; Fri, 7 Jul 2000 14:28:43 -0400 (EDT) Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1]) by smb.research.att.com (Postfix) with ESMTP id 7789F35DC2; Fri, 7 Jul 2000 14:28:43 -0400 (EDT) X-Mailer: exmh version 2.2 06/23/2000 with version: MH 6.8.3 #1[UCI] X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox From: "Steven M. Bellovin" To: chiari mario Cc: Steve Coya , pso-discuss@pso.icann.org Subject: Re: [Pso-discuss] Looking for a layman example on what PSO does. Mime-Version: 1.0 Content-Type: text/plain Date: Fri, 07 Jul 2000 14:28:43 -0400 Message-Id: <20000707182843.7789F35DC2@smb.research.att.com> 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 X-BeenThere: pso-discuss@pso.icann.org In message <3.0.5.32.20000707201347.007c4100@mbox2.flashnet.it>, chiari mario w rites: >Steve > >thanks for your reply. >It helps, though I am trying do write a less abstract statement. > >Would you say that the following statement conveys a correct understanding >of the matter of fact: > >---- the Internet protocol contains numerous parameters, for example to >identify the character set of a text, or a operating system. (A character >set is a set of conventions to code a traditional alphabet, e.g. latin, >cyrillic, japanese). The values of these parameters need to be assigned >uniquely. ICANN/PSO is to make those unique assignments and to maintain a >registry of the currently assigned values. > >(here I am cutting & pasting statements from IANA's web site) > >mario > >ps do you have a two lines definition of what a port is? A "port" is analoguous to a room number in an office building. The street address gets you to the building, but you go to a particular room for particular services. The problem is that ICANN and the PSO don't do that stuff -- IANA does. The PSO's main job is making sure that decisions by ICANN are technically sound with respect to protocols on the Internet. _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss From pso-discuss-admin@pso.icann.org Tue Jul 25 09:11:06 2000 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 JAA10024; Tue, 25 Jul 2000 09:11:06 -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 JAA12865; Tue, 25 Jul 2000 09:11:06 -0400 (EDT) Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12828 for ; Tue, 25 Jul 2000 09:11:05 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10005; Tue, 25 Jul 2000 09:11:03 -0400 (EDT) Message-Id: <200007251311.JAA10005@ietf.org> From: The ICANN PSO Protocol Council To: IETF-Announce: ; cc: pso-discuss@pso.icann.org Reply-to: pso-discuss@pso.icann.org Date: Tue, 25 Jul 2000 09:11:03 -0400 Subject: [Pso-discuss] Protocol Supporting Organization General Assembly 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 X-BeenThere: pso-discuss@pso.icann.org The ICANN Protocol Supporting Organization General Assembly meeting will be held Thursday evening, August 3, 2000, the South Room 11/12 in The David L. Lawrence Convention Center, beginning at 7:30pm (1930). This is an open meeting. The agenda (also available at http://www.pso.icann.org/GA-AGENDA.txt) for the General Assembly is below: Protocol Supporting Organization General Assembly Agenda 1. Opening Leslie Daigle and Steve Bellovin 2. An ICANN overview Presentation Louis Touton 3. Presentation on role and Brian Moore responsibilities of the PSO 4. Introduction of the signatories Everyone ITU - Fabio IETF - Leslie ETSI - Bridget W3C - Danny 5. Presentation on activities of Gerry Lawrence PSO-PC to date 6. Presentation on plans for election Steve Coya of ICANN Board member this year 7. Open discussion and feedback Leslie Daigle and Steve Bellovin The URL for the PSO is http://www.pso.icann.org/ _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss From pso-discuss-admin@pso.icann.org Tue Jul 25 18:07:09 2000 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 SAA22730; Tue, 25 Jul 2000 18:07:09 -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 SAA21771; Tue, 25 Jul 2000 18:07:06 -0400 (EDT) Received: from lotl.clari.net.au (lotl.clari.net.au [203.26.127.210]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA21734 for ; Tue, 25 Jul 2000 18:07:03 -0400 (EDT) From: gbs@spa.com.au Received: from spa.com.au (ppp-214.dialup.clari.net.au [203.57.253.214]) by lotl.clari.net.au (8.9.3/8.9.1) with SMTP id IAA91184 for ; Wed, 26 Jul 2000 08:06:04 +1000 (EST) (envelope-from gbs@spa.com.au) Received: from spa.com.au [192.168.0.100] by spa.com.au [192.168.0.100] with RAW (MDaemon.v2.7.SP5.R) for ; Wed, 26 Jul 2000 08:04:26 +1000 Date: Wed, 26 Jul 2000 08:04:26 +1000 To: pso-discuss@pso.icann.org X-MDaemon-Deliver-To: pso-discuss@pso.icann.org Reply-To: pso-discuss@pso.icann.org Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Actual-From: gbs@spa.com.au Subject: [Pso-discuss] RE: Protocol Supporting Organization General Assembly 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 X-BeenThere: pso-discuss@pso.icann.org Dear pso-secretary@ietf.org, Thanks for your recent message regarding `Protocol Supporting Organization General Assembly`. I am travelling right now but will be back on the 31st of July 2000. Thanks again! gbs@spa.com.au _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss From pso-discuss-admin@pso.icann.org Tue Jul 25 19:06:55 2000 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 TAA14151; Tue, 25 Jul 2000 19:06:55 -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 TAA22644; Tue, 25 Jul 2000 19:06:52 -0400 (EDT) Received: from c004.sfo.cp.net (c004-mx003.c004.sfo.cp.net [209.228.13.216]) by optimus.ietf.org (8.9.1a/8.9.1) with SMTP id TAA22608 for ; Tue, 25 Jul 2000 19:06:49 -0400 (EDT) From: Abbas@khorasan.com Received: (cpmta 28358 invoked from network); 25 Jul 2000 16:06:19 -0700 Date: 25 Jul 2000 16:06:19 -0700 Message-ID: <20000725230619.28357.cpmta@c004.sfo.cp.net> X-Sent: 25 Jul 2000 23:06:19 GMT X-LoopDetect: AutoResponder To: pso-discuss@pso.icann.org Subject: [Pso-discuss] (auto-response) Re: Protocol Supporting Organization General Assembly 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 X-BeenThere: pso-discuss@pso.icann.org Your message has been received. We will come back to you as soon as possible. Best Regards, Abbas Datoo ----------- Original message follows ----------- The ICANN Protocol Supporting Organization General Assembly meeting will be held Thursday evening, August 3, 2000, the South Room 11/12 in The David L. Lawrence Convention Center, beginning at 7:30pm (1930). This is an open meeting. The agenda (also available at http://www.pso.icann.org/GA-AGENDA.txt) for the General Assembly is below: Protocol Supporting Organization General Assembly Agenda 1. Opening Leslie Daigle and Steve Bellovin 2. An ICANN overview Presentation Louis Touton 3. Presentation on role and Brian Moore responsibilities of the PSO 4. Introduction of the signatories Everyone ITU - Fabio IETF - Leslie ETSI - Bridget W3C - Danny 5. Presentation on activities of Gerry Lawrence PSO-PC to date 6. Presentation on plans for election Steve Coya of ICANN Board member this year 7. Open discussion and feedback Leslie Daigle and Steve Bellovin The URL for the PSO is http://www.pso.icann.org/ _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss From pso-discuss-admin@pso.icann.org Tue Jul 25 19:41:34 2000 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 TAA24468; Tue, 25 Jul 2000 19:41:33 -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 TAA23071; Tue, 25 Jul 2000 19:41:33 -0400 (EDT) Received: from ts16-a550.dial.sovam.com (ts16-a550.dial.sovam.com [195.239.7.42]) by optimus.ietf.org (8.9.1a/8.9.1) with SMTP id TAA23036 for ; Tue, 25 Jul 2000 19:41:28 -0400 (EDT) From: To: Date: ×ò, 06 èþë 2000 12:01:05 +0400 Message-ID: <46821354840787406@ts16-a550.dial.sovam.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: [Pso-discuss] Hi, its for you ! 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 X-BeenThere: pso-discuss@pso.icann.org Content-Transfer-Encoding: 7bit Hi! We are Russian girls - Lilia, Alyona, Natalia. We would like to correspond with you. Visit our site and see our photos. http://www.russiangirls.h1.ru With interest, Lilia, Alyona, Natalia. P.S. This is not spam. You can unsubscribe at any time by sending an email to freelist@nm.ruwith the subject UNSUBSCRIBE. P.P.S. This message is being sent to you in compliance with the proposed Federal legislation for commercial e-mail (S.1618-SECTION 301). "Pursuant to Section 301, Paragraph (a)(2)(C) of S. 1618, further transmissions to you by the sender of this e-mail may be stopped at no cost to you by clicking mailto:sngl@soon.com and placing REMOVE in the subject. _______________________________________________ PSO-Discuss mailing list PSO-Discuss@pso.icann.org http://www.pso.icann.org/mailman/listinfo/pso-discuss