ICANN ICANN Email List Archives

[soac-mapo]


<<< Chronological Index >>>    <<< Thread Index >>>

[soac-mapo] RE: some comments & wording change suggestion

  • To: 王亮 <wangliang@xxxxxxx>, "soac-mapo" <soac-mapo@xxxxxxxxx>
  • Subject: [soac-mapo] RE: some comments & wording change suggestion
  • From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
  • Date: Mon, 20 Sep 2010 10:20:52 -0400

Thank you very much Wang for these contributions.  Please see my questions 
below.

Chuck

> -----Original Message-----
> From: 王亮 [mailto:wangliang@xxxxxxx]
> Sent: Monday, September 20, 2010 3:37 AM
> To: soac-mapo
> Cc: Gomes, Chuck
> Subject: some comments & wording change suggestion
> 
> Dear colleagues,
> 
> Some comments on some parts of the CWG’s report .
> 
> 1)    According to the results of the current discussions,CWG endorsed
> the suggestion that using the ”experts panel” to replace “DRSP”,It is
> fine for me. However, as described in DAG4, ICANN had appointed ICC as
> a third-party to deal with Rec 6 related and community-based objection.
> The ICC is a physical body but not the experts panel proposed by CWG.
> Therefore, it is recommended that the CWG should recommend the Board to
> reconsider this issue in the report.
[Gomes, Chuck] I believe that AGv4 proposes that the ICC provide the experts as 
well.  Do you understand it differently?

> 
> 2)If we decide to use “experts panel”, the wording in the text of
> recommendation 9.2 should be adjusted accordingly. Moreover
> recommendation 9.1 has included the situation as described in
> recommendation 9.2, and the description of recommendation 9.1 clearly
> state the status.
[Gomes, Chuck] Do you have specific recommendations for changes to 9.1 & 9.2.

> 
> 
> Wang Liang
> China Academy of Telecommunication Research
> Ministry of Industry and Information Technology
> People's Republic of China
> Tel:+86 10 6230 4024
> Fax:+86 10 62304024
> Email:wangliang@xxxxxxx
> Add:No. 52 Hua Yuan Bei Road,Beijing, P.R.China
> 2010-09-20



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy