ICANN ICANN Email List Archives

[comments-proposed-amend-new-gtld-agreement-31may16]


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

Comments on the proposed changes stated in section 1.7 of Spec 6 in the RA

  • To: "comments-proposed-amend-new-gtld-agreement-31may16@xxxxxxxxx" <comments-proposed-amend-new-gtld-agreement-31may16@xxxxxxxxx>
  • Subject: Comments on the proposed changes stated in section 1.7 of Spec 6 in the RA
  • From: Bonnie Chun <bonnie.chun@xxxxxxxx>
  • Date: Tue, 12 Jul 2016 07:26:06 +0000

Dear Sir/Madam,

Thanks for your effort to compile the proposed changes on the Registry 
Agreement. We have reviewed the proposed changes and found Section 1.7 in 
Specification 6 that states, “Network Ingress Filtering. Registry Operator 
shall implement network ingress filtering checks for its Registry Services as 
described in BCP 38 and BCP 84, which ICANN will also implement.”

We would like to voice out concern and the difficulty by registry operator to 
comply, especially the registry operator who is not the network operator. 
Registry operator would have to request Internet service providers to implement 
BCP38 and BCP84. This may not always be possible. Also it will incur cost and 
contractual responsibility, and with fewer choice for selecting network 
operators.

Hope ICANN will re-consider this requirement seriously.

Kind regards,

Bonnie Chun
Hong Kong Internet Registration Corporation Limited
(Registry operator of .mtr)
Email: bonnie.chun@xxxxxxxx<blocked::blocked::mailto:bonnie.chun@xxxxxxxx>
Website: www.hkirc.hk<blocked::blocked::http://www.hkirc.hk/>

___________________________________________________________
The information in this email is confidential and may be legally privileged.  
If you are not the intended recipient, please notify the sender immediately and 
then delete this e-mail entirely.  You must not retain, copy, distribute or use 
this e-mail for any other purpose not intended by this email or disclose any of 
its content to others.  The recipient should check the email and attachment for 
the presence of viruses.  The company accepts no liability for any damage 
caused by any virus transmitted by this email.
PROTECT OUR ENVIRONMENT - think before printing!



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

Privacy Policy | Terms of Service | Cookies Policy