Skip to main content

Bolstering ICANN’s Contractual Compliance Team

We are pleased to announce two new hires who are joining ICANN’s contractual compliance team. If you’re unfamiliar with the contractual compliance team, it provides the backbone of ICANN’s enforcement of the rules negotiated with contracted parties.

Maguy Serad, an experienced technology and business manager, has been named Senior Director of Contractual compliance.

Ms. Serad has more than two decades of experience in compliance, technology, program management and global business operations. She has most recently served in senior manager positions in the Information Systems Department and Value UP and Synergy Departments of Nissan North America, Inc.

While at Nissan, Ms. Serad became a certified Black Belt Six Sigma expert, who has led multiple strategic organization projects and cross-functional teams in support of Nissan’s strategic objectives. Maguy is fluent in English, French and Arabic. She will begin her role on April 4th.

Contractual Compliance Manager/Auditor

Carlos Alvarez, an accomplished intellectual property attorney, also joins the contractual compliance team as ICANN’s Contractual Compliance Manager/Auditor.

Before joining ICANN on February 28, Alvarez practiced law in Colombia and the United States for over 10 years.

Alvarez was an attorney in Colombia for many years, where he led teams and coordinated audit activities for over 4,500 companies regarding software piracy. Carlos is bilingual in English and Spanish.

Thanks to Current Team

I would also like to thank ICANN Contractual Compliance team members Pam Little and Stacy Burnette, who have coordinated to manage the team during the international search for the new departmental manager. I can attest that since I started working directly with managing this team late last year, they have maintained excellence within the Contractual Compliance group and have been a part of selecting the new team members and building the department.

Starting in April, Maguy will report directly to me and will begin leading and continuing to build this team, with the full support of the existing and talented Contractual Compliance team that has already been built.

Comments

    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."