Chief Technology Officer at Architelos
Joined on March 9, 2011
Total Post Views: 50,901
CTO Michael Young oversees product development, security and technology, integration services and services delivery platforms for Architelos. In this role he is charged with delivering turn-key solutions for “front-office” registry and TLD management. Front-office solutions comprise the systems, procedures and processes a new registry would need to be operational on day one. These include: contracts compliance and management, automated workflows for channel signup and readiness, financial and business operations, as well as ties to registry infrastructure providers. Michael is an active volunteer in ICANN working and interest groups, a long-standing member of ISOC (Internet Society), and has been a contributor to various IETF (Internet Engineering Task Force) efforts.
Prior to joining Architelos, Michael was a founding member of the management team at Afilias (www.afilias.info), a leading registry infrastructure provider. Over his 10 years at Afilias, Michael was key in building the core technology and managing various operations teams. In his role as Vice President of Product Development, he led new product development, project management, business analysis and customer service. Michael was also a primary author in winning bids for the .ORG, .MOBI, and .IN registries and others. Michael’s IT career has been concentrated in systems operations and software development management, specializing in 24/7 high availability environments.
Michael holds degrees from the University of Toronto, Queen’s University and an MBA from Cornell University.
Wait and see approach on abuse attracts ICANN Stakeholder attention: A few weeks ago I made a detailed argument as to why product safety applies to domains, just like it does to cars and high chairs. I also argued that good products equal good business or "economically advantaged" in the long run. Then I really made a strong statement, I said if we don't actively engage other Internet stakeholders -- those that interact with our products, we would eventually lose the opportunity to self-regulate. more»
There has been a lot of back and forth recently in the ICANN world on what constitutes domain abuse; how it should be identified and reported AND how it should be addressed. On one side of the camp, we have people advocating for taking down a domain that has any hint of misbehaviour about it, and on the other side we have those that still feel Registries and Registrars have no responsibility towards a clean domain space. (Although that side of the camp is in steady decline and moving toward the middle ground). more»
Back when I started working in this industry in 2001, ICANN was small, the industry was tight, and things moved slowly as interest groups negotiated a balance amongst the impacts of change. Change often meant added overhead and, at the very least, a one-time cost effort to implement on the commercial side. Registries and registrars preferred to be hands-off when it came to how their domains were being used. But e-crime became big business during the 2000s. more»
As an industry insider and technologist, it's always tempting when discussing something new, such as the Trademark Clearinghouse (TMCH), to jump into the gritty details to try solving problems. However, in this case, we would be jumping a step ahead because it's fair to say most of the general community is not well informed about the current implementation challenges around the TMCH. more»
This part 3 of the selecting a back-end registry service provider series focuses on Whois and sharing data in new gTLDs. If you've ever looked up information about a domain name you've used a Whois service. It's the public information system about contact information for a domain name or IP addresses, though in this article, we will just talk about domain name Whois. In some generic and sponsored Top Level Domains (gTLDs), Whois is run authoritatively by the gTLD. In older gTLDs such as .com and .net, the authoritative Whois service is run by the registrar responsible for the domain name. While some TLD operators run their own infrastructure... more»
Deciding how and when to launch a new generic Top-Level Domain (gTLD) or brand Top-Level Domain (TLD) is not unlike deciding to conduct a worldwide tour to key destinations to help boost your marketing efforts. You want to decide what results you expect, who you'll target and what messages you want to send them, as well as study your options and understand them clearly. Only after you've done that do you book your travel plans. more»
Brand owners unfamiliar with the domain name system (DNS) are hearing that their first step in registering a top level domain (TLD) is to select a back-end TLD registry provider. The fear instilled in them is that if they don't act quickly, all available service providers will have reached their capacity. Given ICANN's tight and inflexible application submission schedule, brands don't want to be left at the starting gate. more»