Page History

...

There should be investigation and evaluation of the applicant as relates* to *fraudulent domain use, park pages on domains (that should have content), WHOIS enforcement, user confusion, arbitrary domain takedowns and objectionable names. 
E. Vertical Integration and Morality and Public Order While primarily restricted to the ICANN's legal-technical area, i.e. class 1 (IN) and to the "internal internet" (i.e. pre-IDNA2008) understanding of naming; there is impact on end-user in terms of intellectual property rights.

  Wiki Markup{{{_}

NOT SURE IF TO INCLUDE- _{}}}{{{}_\ [Also the{_}{}}}_ _{{{}{_}exploration of the Class IN issues are of interest and in some cases may be transposed to the three other{_}{}}}_ _{{{}{_}naming contexts up for debate (after the IAB has{_}{}}}_ _{{{}{_}decided/commented on the organization of this debate)._{}}}_ _  The four naming contexts under consideration are:  {{{_}1. referent: system unique allocator - using a non-phishable{_}{}}}_ _{{{}{_}character recognition system (Unicode restriction) - no IP involved._{}}}_ _the exploration of the Class IN issues are of interest and in some cases may be transposed to the three other naming contexts up for debate (after the IAB has decided/commented on the organization of this debate).  
The four naming contexts under consideration are:
 1. referent: system unique allocator - using a non-phishable character recognition system (Unicode restriction) - no IP involved. 

2. identification: (possibly delegated) authority decides - this is the Registries discussed area ICANN tries to control - IP issues being involved. 

...

The Working Group shares ALAC’s concern and objections (both on substance and process) to the precedent and lack of consistency this action sets.

Wiki Markup_\[to insert link to ALAC statement drafted by Evan\]_

G. Communication to to Application Support Vendors and Web-Based Service Providers

...