In December 2011, the partnership submitted to ICANN 31 proposed requirements to ensure the stability and resiliency of “high security” gTLDs like .bank and .pay, covering topics from registration, acceptable use policies, abusive conduct, law enforcement, compliance registrar relations and data security. BITS calls the proposed gTLDs intended for the use of the financial industry as “fTLDs.” In addition, the organization strongly urged the internet governing body to accept the standards proposed by the Security Standards Working Group ([[SSWG]]). Seventeen companies are endorsing BITS proposal.<ref>[http://domainincite.com/high-security-bank-spec-published/ High-security .bank spec published]</ref> The 2011 Proposed Security, Stability and Resiliency Requirements for Financial TLDs submitted by BITS to ICANN is available [http://www.bits.org/publications/doc/SSWGOutreachICANN122111.pdf here]. | In December 2011, the partnership submitted to ICANN 31 proposed requirements to ensure the stability and resiliency of “high security” gTLDs like .bank and .pay, covering topics from registration, acceptable use policies, abusive conduct, law enforcement, compliance registrar relations and data security. BITS calls the proposed gTLDs intended for the use of the financial industry as “fTLDs.” In addition, the organization strongly urged the internet governing body to accept the standards proposed by the Security Standards Working Group ([[SSWG]]). Seventeen companies are endorsing BITS proposal.<ref>[http://domainincite.com/high-security-bank-spec-published/ High-security .bank spec published]</ref> The 2011 Proposed Security, Stability and Resiliency Requirements for Financial TLDs submitted by BITS to ICANN is available [http://www.bits.org/publications/doc/SSWGOutreachICANN122111.pdf here]. |