RE: [gnso-idn-wg] ***SPAM: Liaison to the joint ccNSO-GAC IDN WG

["Marilyn Cade" <marilynscade@xxxxxxxxxxx>]

Perhaps it might even be feasible to have two liaisons, given the
criticality of the feedback, and the high work load,  

 

  _____  

From: owner-gnso-idn-wg@xxxxxxxxx [mailto:owner-gnso-idn-wg@xxxxxxxxx] On
Behalf Of Sophia B
Sent: Monday, January 22, 2007 3:09 AM
To: rmohan@xxxxxxxxxxxx
Cc: gnso-idn-wg@xxxxxxxxx
Subject: Re: [gnso-idn-wg] ***SPAM: Liaison to the joint ccNSO-GAC IDN WG

 

Thanks for the clarifications, Ram

 

' In discussions with the working groups, it appears that there may be
several meetings that are held that conflict with pre-set GNSO Council
schedules/meetings. 

 

 

Does the above mean that GNSO councilors may not be likely candidates? 

Sophia


 

On 21/01/07, Ram Mohan <rmohan@xxxxxxxxxxxx > wrote: 

Spam detection software, running on the system "mail00.afilias.info
<http://mail00.afilias.info/> ", has 
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details. 

Content preview:  Dear GNSO IDN WG members, I am pleased to see interest
 in the liaison role; several WG members have written in to express their
 interest. One common question has been what the "qualifications" are. 
 Please note the following observations regarding the liaison role: [...]

Content analysis details:   (7.5 points, 5.0 required)

 pts rule name              description
---- ----------------------
-------------------------------------------------- 
 0.0 HTML_MESSAGE           BODY: HTML included in message
 1.8 RCVD_IN_DSBL           RBL: Received via a relay in list.dsbl.org
<http://list.dsbl.org/> 
                           [<http://dsbl.org/listing?203.145.128.5>]
 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
<http://bl.spamcop.net/> 
              [Blocked - see <
<http://www.spamcop.net/bl.shtml?203.145.128.5>
http://www.spamcop.net/bl.shtml?203.145.128.5>]
 3.1 RCVD_IN_XBL            RBL: Received via a relay in Spamhaus XBL
                           [ <http://203.145.128.5/>  203.145.128.5 listed
in sbl-xbl.spamhaus.org <http://sbl-xbl.spamhaus.org/> ]
 1.2 RCVD_IN_SORBS_WEB      RBL: SORBS: sender is a abuseable web server 
                           [203.145.128.5 <http://203.145.128.5/>  listed in
dnsbl.sorbs.net <http://dnsbl.sorbs.net/> ]

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view 
it, it may be safer to save it to a file and open it with an editor.


 



---------- Forwarded message ----------
From: "Ram Mohan" < rmohan@xxxxxxxxxxxx  <mailto:rmohan@xxxxxxxxxxxx> >
To: <gnso-idn-wg@xxxxxxxxx>
Date: Sun, 21 Jan 2007 21:09:41 -0500
Subject: Liaison to the joint ccNSO-GAC IDN WG

Dear GNSO IDN WG members,

I am pleased to see interest in the liaison role; several WG members have
written in to express their interest.  One common question has been what the
"qualifications" are. 

 

Please note the following observations regarding the liaison role:

-          The observer post is a relaying job, in many ways.  

-          The "qualifications" for the job is for someone who does not
insert their opinion, but rather listens keenly, relays the GNSO WG
positions and status, and similarly relays back to the GNSO WG positions and
status from the ccNSO-GAC IDN WG. 

-          Having the time to attend all GNSO IDN WG meetings, and also all
ccNSO-GAC IDN WG meetings will be essential.  We are talking about probably
16-20 meetings in the next 10 weeks, and a time commitment of probably an
extra 25-40 hours in addition to the time required on the GNSO IDN WG. 

-          Understanding the underpinnings of IDNs, especially the technical
issues (and therefore being able to distinguish signal from noise) is a
clear advantage.  Much of the discussions on IDNs still involve significant
technical areas. 

-    In our call this Tuesday, I plan to hold a *very* brief agenda item on
this area, but do not intend to allow our work to be slowed down by this
topic. 

 

Regards,

Ram

--------------------------------------------------------------------------
Ram Mohan
Vice President, Business Operations
Chief Technology Officer 
Afilias ( <http://www.afilias.info/>  http://www.afilias.info)
p: +1.215.706.5700 x103; f: +1.215.706.5701
m: +1.215.431.0958 
e:  <mailto:rmohan@xxxxxxxxxxxx> rmohan@xxxxxxxxxxxx | skype: gliderpilot30
--------------------------------------------------------------------------