Agent Name Service - DNW Podcast #568 - CourtneyR.dev's 2nd Brain

Agent Name Service - DNW Podcast #568 🔗 **Source:** [Agent Name Service - DNW Podcast #568](https://www.youtube.com/watch?v=nXBRlPU29iw) > [!note]+ Document Notes > tags: [agent-name-service, dns-policy, domain-industry] > author: Domain Name Wire Podcast > source: YouTube > reference: [https://www.youtube.com/watch?v=nXBRlPU29iw] > date created: 2025-01-03 14:30 > > # 🏷️ Title: Agent Name Service - DNW Podcast #568 >  ## 🧰 Action Inbox - [H1] Join Internet Commerce Association for domain investor advocacy — membership provides policy synthesis #policy - [H2] Attend ICANN's Annual General Meeting for maximum impact — October 2026 in Oman #icann - [H3] Monitor IETF standards development for ANS proposals — technical RFC submissions upcoming #ans ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [GoDaddy Agent Name Service Blog](https://godaddy.com/blog) - [Internet Commerce Association](https://internetcommerce.org) ## 📝 Summary - James Bladel (GoDaddy VP) discusses Agent Name Service proposal and domain policy - ANS leverages existing DNS infrastructure to support billions of AI agents by 2030 - ICANN policy updates on DNS abuse requirements and new gTLD timeline (April 2026) - Policy fragmentation concerns across states and countries affecting internet operations - Bottom line: Domain industry must adapt to AI agents while navigating complex policy landscape ## 📖 Main Content GoDaddy proposes Agent Name Service (ANS) as an open standard to leverage DNS infrastructure for AI agent identity and discoverability. With over 1 billion autonomous AI agents projected by 2030, ANS would use fully qualified domain names plus SSL certificates to establish trust and enable agent-to-agent communications. The proposal addresses two critical challenges: agent identity verification and service discoverability. Rather than proprietary standards or closed ecosystems, ANS builds on proven DNS infrastructure that already handles 350 million active domains. ICANN policy developments include confirmed new gTLD applications opening April 30, 2026, through August 12, 2026. However, government advisory committee requirements for "meaningful DNS abuse policies" before activating new TLDs remain vaguely defined, creating potential implementation hurdles. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/nXBRlPU29iw?t=0) — [H1] Show Introduction and SquadCast Domain Expiration - Key idea: Domain expiration interrupted podcast recording mid-session - Evidence: "SquadCast forgot to renew its domain name" causing DNS interruption #### ⏱️ [08:30](https://youtu.be/nXBRlPU29iw?t=510) — [H1] James Bladel Joins ICA Board - Key idea: Former GoDaddy colleague Paul Nicks retired, Bladel brings registrar perspective - Evidence: "Voice of the reg was somewhat absent from policy discussions" #### ⏱️ [12:15](https://youtu.be/nXBRlPU29iw?t=735) — [H2] ICA-WIPO UDRP Collaboration Success - Key idea: Joint expertise accelerated policy development beyond traditional adversarial positions - Evidence: "Blown away by that collaboration... completely different perspectives" #### ⏱️ [18:45](https://youtu.be/nXBRlPU29iw?t=1125) — [H2] UDRP Reform Timeline Delayed - Key idea: Policy development process operates on glacial timeline - Evidence: "Probably looking like later in the year... possibly early 27" #### ⏱️ [22:30](https://youtu.be/nXBRlPU29iw?t=1350) — [H1] Agent Name Service Introduction - Key idea: Over 1 billion autonomous AI agents projected by 2030 need identity infrastructure - Evidence: "350 million active domain names... has the potential to dwarf the existing DNS" #### ⏱️ [26:00](https://youtu.be/nXBRlPU29iw?t=1560) — [H2] ANS Technical Architecture - Key idea: Combines DNS plus SSL certificates for agent identity and trust verification - Evidence: "Using those two existing standards... build an infrastructure for Agentic AI" #### ⏱️ [31:15](https://youtu.be/nXBRlPU29iw?t=1875) — [H2] Agent Autonomy and Learning - Key idea: Agents can learn and make autonomous decisions beyond initial programming - Evidence: "Learn to identify and locate and interact with new services" #### ⏱️ [35:20](https://youtu.be/nXBRlPU29iw?t=2120) — [H3] ANS Domain Structure - Key idea: Each ANS verified agent would have its own fully qualified domain name - Evidence: "Each ANS verified agent would have its own fully qualified domain name" #### ⏱️ [38:45](https://youtu.be/nXBRlPU29iw?t=2325) — [H3] IETF Standards Process - Key idea: Technical adoption requires IETF RFC submission and community review - Evidence: "Submit a proposal or an RFC and other companies could comment" #### ⏱️ [43:30](https://youtu.be/nXBRlPU29iw?t=2610) — [H1] New gTLD Timeline Confirmation - Key idea: ICANN committed to April 30, 2026 application opening through August 12 - Evidence: "No later than midnight on April 30th, 2026... open for 105 days" #### ⏱️ [48:00](https://youtu.be/nXBRlPU29iw?t=2880) — [H2] Government DNS Abuse Requirements - Key idea: Vague government advisory creates potential roadblocks for new gTLD activation - Evidence: "Very non-specific about what the outcome looked like" #### ⏱️ [55:15](https://youtu.be/nXBRlPU29iw?t=3315) — [H2] Associated Domain Checks Policy - Key idea: New requirements for registrars to investigate related domains in abuse cases - Evidence: "Continue to look at that account and other domain names" #### ⏱️ [62:30](https://youtu.be/nXBRlPU29iw?t=3750) — [H3] Federal Data Protection Fragmentation - Key idea: State-by-state data protection creates compliance complexity - Evidence: "Find that high watermark between all the different states" #### ⏱️ [67:45](https://youtu.be/nXBRlPU29iw?t=4065) — [H2] Section 230 Risk Assessment - Key idea: Platform liability protection changes could devastate tech industry - Evidence: "S&P 500 drop 20% in one day, go ahead and cancel section 230" #### ⏱️ [72:00](https://youtu.be/nXBRlPU29iw?t=4320) — [H3] ICANN Meeting Recommendations - Key idea: Annual General Meeting provides most impactful policy discussions - Evidence: "More impactful work is discussed and completed in the AGM" ## 📚 References - [GoDaddy Agent Name Service Technical Resources](https://godaddy.com/blog) - [Internet Commerce Association](https://internetcommerce.org) - [ICANN Policy Development Process](https://icann.org) - [IETF RFC Process](https://ietf.org) ## 🗣️ Paraphrase - GoDaddy proposes using proven DNS infrastructure to handle the massive scale of AI agents expected by 2030 - Policy development at ICANN moves extremely slowly, but joint stakeholder collaboration can accelerate progress - Government requirements for DNS abuse mitigation lack clear success metrics, creating implementation uncertainty ## 📰 Newsletter The domain industry faces a pivotal moment with AI agents and policy changes on the horizon. GoDaddy's Agent Name Service proposal could create massive growth opportunities by leveraging existing DNS infrastructure for AI agent identity verification. Meanwhile, ICANN's confirmed April 2026 new gTLD timeline brings both opportunities and regulatory challenges. For WordPress developers, these changes highlight the importance of understanding domain infrastructure and staying engaged with policy developments that affect the broader web ecosystem. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Create technical content explaining ANS benefits for AI developers - Education: Develop workshops on DNS infrastructure for emerging technologies - Developer experience: Document integration patterns for agent-to-service communications #### Community - Maintainers: Monitor IETF standards development for ANS protocol specifications - Contributors: Engage with domain policy discussions affecting web platform development - Sponsors: Evaluate investment opportunities in DNS infrastructure for AI applications #### WordPress - Core: Assess implications of agent-driven web interactions for WordPress APIs - Documentation: Create guidance for developers building AI agent integrations - Meta: Monitor domain policy changes affecting .org operations ## 🧪 Hypotheses - Agent Name Service adoption will correlate with AI agent proliferation rates by 2030 - Open DNS-based standards will outcompete proprietary agent identity systems - Government DNS abuse requirements will delay new gTLD activations beyond 2026 - Domain registration volume will increase significantly with AI agent deployment ### 📊 Methodology - Track IETF RFC submissions and adoption rates for ANS proposals - Monitor domain registration patterns in relation to AI development cycles - Analyze policy implementation timelines versus government requirement fulfillment ### ❓ Questions - How will existing certificate authorities adapt to AI agent verification requirements? - What governance model will prevent ANS from becoming centralized or captured? - How can DNS infrastructure scale to handle billion-agent scenarios? ### 🔮 Future Research - Economic impact analysis of AI agent domain requirements on registrar business models - Technical scalability studies for DNS infrastructure under extreme load scenarios - Policy framework development for AI agent accountability and governance ### 💡 Implications - Practice: Domain professionals must understand AI agent infrastructure requirements - Policy: Clear DNS abuse metrics needed to prevent arbitrary regulatory delays - Security: Agent identity verification becomes critical internet infrastructure component - Education: Technical community needs AI agent and DNS integration training ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade #### 👀 Visual learners - Present: None identified in audio format - Improve: DNS architecture diagrams, AI agent interaction flows, policy timeline charts #### 🔊 Aural learners - Present: Full podcast interview format with detailed verbal explanations - Improve: Shorter audio summaries of key technical concepts #### 🗣️ Verbal learners - Present: Analogies to existing web infrastructure, plain language explanations - Improve: Glossary of technical terms, comparison frameworks #### 🧩 Kinesthetic learners - Present: None identified - Improve: ANS implementation labs, DNS configuration exercises, policy simulation games #### 🧠 Logical learners - Present: Timeline discussions, cause-effect policy relationships - Improve: Decision trees for ANS adoption, policy flowcharts, technical specifications #### 🧑‍🤝‍🧑 Social learners - Present: Interview format, industry collaboration examples - Improve: Discussion prompts for technical teams, collaboration frameworks #### 🧘‍♀️ Solitary learners - Present: Detailed technical explanations suitable for individual study - Improve: Self-assessment checklists, reflection questions on implementation strategies #### 🌿 Naturalistic learners - Present: Internet ecosystem analogies - Improve: Infrastructure evolution patterns, system adaptation examples ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Transcript provides full content access - Improve: Structured headings in audio description, technical term definitions #### Keyboard navigation - Present: Standard podcast player controls - Improve: Chapter navigation, transcript search functionality #### Contrast and readability - Present: Text transcript available - Improve: High contrast transcript formatting options #### Text resizing and reflow - Present: Standard web text scaling - Improve: Mobile-optimized transcript layout #### Media and captions - Present: Full transcript provided - Improve: Time-synced captions, downloadable transcript formats #### Forms and interactions - Present: Basic podcast controls - Improve: Accessible chapter selection, speed controls with labels ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global ICANN meeting locations mentioned - Improve: International perspective on DNS governance, diverse regulatory examples #### Inclusive language - Present: Professional technical language, defined acronyms - Improve: Non-technical summaries, avoid industry jargon assumptions #### Neurodiversity support - Present: Structured interview format, clear topic transitions - Improve: Consistent heading structure, predictable information organization #### Representation - Present: Industry leadership perspective - Improve: Diverse stakeholder voices, community impact examples #### Psychological safety - Present: Professional, respectful discussion - Improve: Acknowledgment of different technical skill levels, learning pace considerations ### ✅ Logical Validity #### Strong reasoning - Deductive strength: DNS infrastructure proven → AI agents need identity → ANS leverages existing infrastructure - Inductive strength: Past policy delays → Current vague requirements → Future implementation challenges likely - Causal reasoning: Government pressure → DNS abuse requirements → New gTLD delays - Analogical strength: Web SSL certificates → Agent identity verification → Trust establishment #### Fallacies - Appeal to authority: "GoDaddy is pushing this" - source credibility doesn't guarantee technical merit - False dilemma: "ANS or walled gardens" - other open alternatives may exist #### Tone of voice - Overall tone: Professional, informative, industry-insider perspective with appropriate technical depth ### 🛡️ DARVO Analysis - Deny: No denial patterns identified - Attack: No attack patterns on accusers identified - Reverse victim/offender: No victim/offender reversal identified - Emotional cues and rhetoric: Professional, factual discussion without manipulative elements ## 🎯 Conclusion Agent Name Service represents a strategic opportunity for the domain industry to leverage existing DNS infrastructure for the coming AI agent revolution. However, success depends on open standards adoption through IETF and industry coordination beyond any single company's control. The parallel challenge of navigating increasingly complex policy requirements, particularly around DNS abuse, highlights the critical importance of clear metrics and stakeholder engagement in preventing regulatory capture or arbitrary delays. Domain professionals should monitor both technical standards development and policy implementation timelines to position themselves effectively for these converging technological and regulatory changes. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad Purpose: Stage CEE units that become Literature notes. Split level: H3 ### [H1] DNS infrastructure scales to support billion AI agents > [!quote] Agent Name Service - DNW Podcast #568 by Domain Name Wire Podcast via YouTube. Published 2025-01-03. Accessed 2025-01-03. > "Over a billion autonomous AI agents operating on the internet by 2030." Establishes market scale justification for ANS proposal. [view highlight](https://youtu.be/nXBRlPU29iw?t=1350#H1) #xref #articleseed ID:rw_ans_scale ### [H2] Government DNS abuse requirements lack clear metrics > [!quote] Agent Name Service - DNW Podcast #568 > "Very non-specific about what the outcome looked like." Creates implementation uncertainty for new gTLD activation. [view highlight](https://youtu.be/nXBRlPU29iw?t=2880#H2) #xref ID:rw_policy_metrics --- ### --- ## Full Transcript [00:01] [music] [00:06] [music] [00:10] Welcome to the Domain name wire podcast. [00:13] I'm your host Andrew Alamman and this is [00:15] episode number 568. [00:18] My guest this week is James Bladel. He's [00:20] the VP of corporate and government [00:22] affairs at GoDaddy. We're going to talk [00:25] about the proposal for agent name [00:27] service and how this could impact the [00:30] domain name industry. James also talks [00:32] about some policy items that people in [00:34] the domain industry should be paying [00:36] close attention to in 2026 and beyond. [00:40] An interesting thing happened while [00:42] James and I were recording this show. I [00:44] use a platform called SquadCast to [00:46] record my shows. It records the guest [00:48] side locally which improves the sound [00:51] quality. Well, James and I finished [00:52] recording and then got an error message [00:54] that the recording could not be [00:56] uploaded. After troubleshooting, I [00:58] refreshed squadcast.fm [01:00] and it forwarded to a parked page. So, I [01:03] looked at the FM who is record and saw [01:06] that the issue was SquadCast forgot to [01:08] renew its domain name. Like many [01:10] registries, the FM registry interrupts [01:12] the DNS for domains at some point after [01:14] they expire. This alerts the domain [01:17] owner that their domain has expired so [01:19] it doesn't go into full deletion. In [01:21] this case, we happen to be recording at [01:23] the exact moment the FM changed the DNS [01:26] for this domain. Fortunately, I know the [01:28] people at thefm registry and reached out [01:30] to them to alert them about this [01:32] expiration. They're obviously very big [01:35] in the podcasting space and didn't want [01:38] this domain to expire. They worked with [01:40] Squadcast to renew the domain name. I've [01:42] learned to always make a local backup of [01:45] my podcast recordings. So, fortunately, [01:47] we didn't lose any of this great [01:49] interview with James. Normally at this [01:51] point in the podcast, we talk about news [01:53] in the domain business from the past [01:54] week, but I was traveling for the [01:56] holiday last week. So, we're going to [01:57] skip straight to the interview segment, [02:00] but I still published stories last week, [02:02] so please check out domainamewire.com [02:04] for the latest news. Now, let's chat [02:07] with James Bladel. [02:10] [music] [02:15] My guest is James Bladel. He is the VP [02:18] of corporate and government affairs at [02:20] GoDaddy. James, welcome to the show. [02:22] >> Thanks, Andrew. Thanks for having me. [02:24] >> So, want to start by first of all [02:26] congratulating you. You've been named as [02:28] a new board member for the Internet [02:30] Commerce Association. What do you think [02:32] you'll bring to the table to help a [02:34] >> Well, thanks. Well, first I should [02:36] probably acknowledge that Paul Nicks and [02:38] I started at GoDaddy about a week apart. [02:40] So I had a front row seat to his work [02:42] and his work with the ICA and just the [02:44] overall impact that he had on the [02:46] industry and I just can't say enough [02:47] good things uh about him and of course [02:50] wish him well in his retirement. I've [02:52] always been a fan of the internet [02:53] commerce association. I believe it [02:55] brings a different perspective [02:56] particularly to uh organizations like I [02:59] can which has been my focus for most of [03:01] my time at godaddy. I've always felt [03:03] that the voice of the reg was somewhat [03:05] absent from policy discussions. I mean [03:08] as a registar we try to function as a [03:10] proxy for our customers of course but I [03:13] think ICA can potentially be more [03:15] effective in bringing those interests [03:17] into policy discussions um because [03:20] otherwise I think you're you're missing [03:21] an important stakeholder when you think [03:23] about those things that are impactful to [03:25] the folks who really don't know about [03:27] IAN and really don't care how it works [03:29] and just want their domain names to [03:31] serve their uh their identity and their [03:32] business and and are really relying on [03:34] organizations like ICA to act on their [03:36] behalf. So, I'm really looking forward [03:38] to that work and hopefully I can bring a [03:40] slightly different [03:42] perspective to the board the based that [03:45] draws upon just my years of experience [03:48] operating in IAN. [03:49] >> Yeah, I think Zach's really happy. Of [03:51] course, Zach isn't a board member. He's [03:53] the general counsel, Zack Muskovich, but [03:55] he had the deepest policy knowledge [03:57] there. Certainly I think that you know a [03:59] lot of the board members are domain [04:01] investors and such which is great but to [04:03] have someone else who's already going to [04:05] all the I can meetings anyway [snorts] [04:07] you know being on the board I think will [04:09] be a big help to the organization. Why [04:11] don't we start by you know I had Zach on [04:13] the show very recently and he was [04:15] talking about the internet commerce [04:17] association's collaboration with the [04:19] World Intellectual Property Organization [04:21] WIPO on evaluating UDRP. You've been [04:25] around I can for a long time. you've [04:27] been involved for a long time. It seems [04:29] like it can take forever for things to [04:31] get done there. So, what do you think [04:33] about what the AA and WIPO did here to [04:35] kind of bring a a work product or a [04:37] starting point that hopefully I can [04:40] process will now consider? [04:42] >> To be blown, I was blown away by that [04:44] collaboration for a number of reasons. I [04:46] mean one first off here you have two of [04:49] probably the recognized bodies of [04:51] expertise on this issue in the internet [04:54] commerce association and WIPO and folks [04:57] who have been around I can long enough [04:59] and really you don't have to be around I [05:00] can that long to realize they're [05:02] probably going to come at a lot of these [05:03] issues from completely different [05:05] perspectives in serving their [05:07] stakeholders. So for them to be able to [05:09] work together and identify and [05:12] contribute and lend their expertise to [05:14] these issues and identify some areas of [05:18] common ground for improvement. I think [05:20] it is amazingly helpful and can really [05:22] accelerate the policy development [05:25] process. I was encouraged to see that [05:28] they agreed mostly that the UDRP was [05:30] functioning as it was intended 25 years [05:33] ago when it was first created and that [05:35] it doesn't really need wholesale reform. [05:38] It needs some improvements and benefit [05:40] from some enhancements around the edges. [05:42] But generally, I really hope that this [05:44] kind of a model can serve the community [05:47] for future PDPs and sticky issues of how [05:50] we can jumpstart that policy development [05:52] process and get it moving a little [05:54] faster because in my view, I've watched [05:56] it slow down to the point where it's [05:59] almost operating on a glacial timeline. [06:01] >> You talking about I can or the [06:03] >> I can's process. Yeah. [06:04] >> For UDRP review [06:06] >> for any policy. [06:07] >> For any Yeah. because I think there are [06:10] so many calcified positions that are [06:12] unwilling to communicate or work [06:15] together. So, I'm really hoping that [06:17] this A and WIPO collaboration can serve [06:20] as a as a breakthrough and maybe a sign [06:22] for ways that we can improve the PDP and [06:24] make it more responsive and more [06:25] functional. It's interesting when I was [06:27] at the IAN meeting in Seattle last year, [06:31] there was someone who had was very much [06:33] involved in ICAN many years ago. I kind [06:36] of stepped away, changed the role, [06:38] changed company focus and they came back [06:40] to that one and they said, "Wow, it's [06:42] the same thing but much slower. [06:46] Much slower." I think we're talking [06:48] about the same individual who said [06:50] something like, "It's good. Good news is [06:53] I get to see all of my friends again. [06:54] Everyone's still here." here. The bad [06:55] news is you're still talking about the [06:57] same stuff you were when I left 5 years [06:59] ago. So hopefully this collaboration and [07:01] other joint efforts like it can really [07:04] kind of punch through some of those [07:05] roadblocks and get some of these policy [07:08] development efforts moving again. [07:10] >> So speaking specifically about what ICA [07:12] and WIPO did, when do you think UDRP [07:15] when do you think this PDP as policy [07:17] development process picks up again at [07:20] IAN? Yeah, unfortunately I think that [07:22] the calendar is already filling up for [07:24] 2026 in terms of what I can can [07:26] realistically take on. I think it's [07:28] probably looking like later in the year [07:31] it would be considered for an initiation [07:33] and possibly early 27. [07:35] >> Okay, so late 26, early 27 hopefully. [07:38] >> Yeah, hopefully. [07:39] >> Nobody ever lost money betting uh [07:40] against delays at I can right as a rule. [07:43] >> I think that there's an opportunity. it [07:45] would be a lot slower and we' probably [07:47] be talking into the possibly even into [07:49] the 2030s had they not put this report [07:52] out there. So that's I think this bought [07:53] us a couple of years pulling the process [07:55] forward. We'll talk more about policy [07:58] later, but uh in case some people are [08:00] falling asleep uh listening to the show [08:02] who aren't really into policy. It's [08:04] funny I say that in Jess because it used [08:07] to be if I wrote about policy people are [08:09] like, "Oh, come on. It's so boring." But [08:11] I will say over the past 10 years [08:13] there's been a pretty big change there [08:14] where policy stories have become some of [08:16] my more popular ones and I think people [08:19] realize the importance of it even if [08:21] it's not like immediate to them whether [08:24] they're a domain investor of course [08:25] registars registries they realize how [08:27] important it is absolutely and and I [08:31] think that you know it's a it's a credit [08:33] to what you're doing and and those of us [08:34] who are trying to communicate these very [08:37] dry and complex policy issues into uh [08:40] audiences that can understand then how [08:43] it impacts their business and their use [08:45] of domain names. You know, I can for all [08:47] of its faults is rewriting the landscape [08:50] and changing the rule book in its wake. [08:52] You know, we have to participate in that [08:54] and we have to be actively engaged in [08:56] those processes otherwise we'll get run [08:58] over. Well, we'll come back to policy in [09:00] a bit, but I want to talk to you about [09:03] GoDaddy has been kind of pitching this [09:05] idea of this agent name service or ANS. [09:09] I've received a few press releases about [09:11] it that frankly I read them and didn't [09:13] understand what it meant whatsoever. So [09:15] I want to unpack that a little bit [09:17] today. What is this idea behind agent [09:20] name service? Sure. And yeah, some of [09:22] the stuff uh is pretty technical, but [09:24] just in a nutshell, I think agent name [09:27] service is a way to leverage the proven [09:30] infrastructure of the DNS to support [09:32] Gent AI. I think we all kind of hear the [09:35] hype around Agentic AI, but even in the [09:38] most conservative estimates that I'm [09:40] reading, there could be over a billion [09:43] autonomous AI agents operating on the on [09:46] the internet by 2030. And if you think [09:49] about there's I don't know the number [09:50] [clears throat] 300 350 million active [09:53] domain names. So this is something that [09:56] is already has the potential to dwarf [09:58] the existing DNS because all of those [10:01] agents are going to have two problems. [10:03] They're going to have the the challenge [10:04] of identity and discoverability but also [10:07] the uh challenges associated with trust [10:10] and how do you know that an agent is [10:12] operating is who it claims to be when [10:14] you're interacting with it. I think the [10:16] good news is is that we've already [10:18] solved those problems. We've used the [10:20] DNS uh as a ubiquitous and unique naming [10:22] schema to establish those identities and [10:25] make those services discoverable and we [10:27] have uh SSL certificates and the [10:29] verification that goes into those to [10:31] establish the trust. So by using those [10:34] two services, those two existing [10:37] standards, [10:38] >> DNS and SSL certificate, [10:40] >> DNS plus SSL certificate, we can build [10:43] an infrastructure for Aentic AI that [10:46] operates at the scale that's going to be [10:48] necessary, you know, in the next in the [10:50] next few years. And, you know, for the [10:52] domain name industry, I think that this [10:53] is important because it leverages what [10:56] we're already doing. I think the [10:59] alternatives are concerning because they [11:01] could be a number of competing and [11:03] proprietary standards or it could be a [11:05] lot of closed gardens like we see with [11:06] app stores and other ecosystems like [11:08] that. So, GoDaddy is pushing this not as [11:10] a product announcement or a service that [11:12] we're excited about but more as [11:14] something that we can rally the domain [11:16] name industry around as an open standard [11:19] and use what we know already works to [11:22] support Agentic AI. So is the idea here [11:25] about using domains in the DNS is the [11:28] idea that if I'm going to if some agent [11:30] is going to go out and wants to say [11:34] register a domain name that the agents [11:37] it interacts with it knows that they are [11:40] who they are because of their domain [11:42] name and it's kind of been registered [11:44] for as the definitive agent for this [11:48] agent or this company that sort of [11:50] thing. Yeah, I think it would be [11:51] analogous to when you use a browser to [11:53] go to an e-commerce site and you see the [11:55] padlock or the green navigation bar that [11:58] says that, you know, the SSL certificate [11:59] matches, you know, who claims to have [12:02] registered this domain name. So, it's [12:04] using the fully qualified domain name [12:05] plus the SSL certificate to establish [12:08] that discoverability and trust. And [12:10] also, by the way, it could be consumer [12:12] to agent interactions that require [12:15] discoverability and trust or it could be [12:16] agent to agent interactions. So this is [12:19] uh something that could be built into [12:21] the agent itself and then you would use [12:25] ANS to locate an agent. You know, you [12:28] could for example gain even more [12:31] information about what it does, who's [12:34] operating it, what language does it [12:35] speak, what communications is it [12:37] expecting. It really is repurposing that [12:41] service agnostic system of the DNS as a [12:45] platform on which to build this whole [12:47] new internet. [12:48] So when I think of agents right now, I [12:52] think they're generally serving they're [12:54] going out to do one purpose and I feel [12:57] like if they interact with other agents, [12:59] they're literally kind of programmed to [13:01] interact with them at this point. Am I [13:04] correct? Like they aren't going out and [13:06] searching for agents and then to do [13:08] something for them or are we there yet? [13:10] I think there's certainly some folks [13:12] inside GoDaddy that have more AI [13:14] specific expertise than I do, but my [13:16] understanding is as the agents and what [13:18] distinguishes them from just bots and [13:20] other web automation is they're able to [13:24] learn and make autonomous decisions. So [13:27] that they could, for example, be [13:29] initially set out to interact with [13:31] specific agents or services, but they [13:34] could over time learn to identify and [13:36] locate and interact with new services [13:39] that were not part of their original [13:41] instructions. They could potentially [13:43] decide to create an agent for themselves [13:46] to follow a specific path or to provide [13:48] some function. So I think it's the [13:51] autonomy and the ability to modify their [13:54] own initial functions and add to their [13:57] services that makes them really exciting [14:00] and also maybe problematic without very [14:04] scary at the same time. [14:05] >> Yeah. I mean, if you don't trust them or [14:06] if you can't find them or if you maybe [14:09] you have interacted with an agent and [14:10] you really liked that interaction and [14:12] you want to do business with them again, [14:14] having a a unique identifier like a [14:17] fully qualified domain name under ANS is [14:19] really going to establish that [14:21] repeatable interaction. [14:24] So, GoDaddy pitches this idea, right? [14:28] There have been some blog posts, that [14:29] sort of thing. What happens next? I [14:31] mean, how do you get traction on this as [14:34] an idea? because as you mentioned there [14:35] are some competing ways to do this some [14:37] of which would be closed if you will. So [14:41] how does that work? [14:42] >> Well I think we're I mean the short [14:44] answer is we're talking to everyone who [14:46] we think wants to listen and can [14:48] contribute to this. So we're talking to [14:50] the talking to you and the folks at Ian [14:53] and the other counterparts in the DNS [14:54] industry. We are speaking with a lot of [14:57] the main publishers of the um AI models [15:00] and counterparts at other and other [15:02] vertical industries. We're working [15:04] through some of the techn technical [15:06] organizations like IETF to get standards [15:08] published and I believe we are seeing [15:10] some discussion around our proposals [15:12] there really u trying you know making [15:15] sure that we're putting this message out [15:17] on every channel that we participate in [15:19] to spread the word that this or it's a [15:22] bunch of walled gardens. And I think as [15:24] a domain name industry company, we [15:26] believe, of course, we're well situated [15:28] to, you know, help this succeed. But we [15:31] can't do it alone. And we want to make [15:33] sure that there's a recognition of the [15:35] benefits for all of the participants in [15:37] the DNS industry. Even, you know, other [15:40] registars and other registries, even [15:41] domain name investors, for example, [15:43] could see benefits from a standard like [15:45] this taking off. [15:46] >> Yeah. I mean, presumably ultimately more [15:48] domains registered. Are we talking about [15:50] agents having their own domain name or [15:52] being associated with a company's domain [15:54] name? [15:55] >> My understanding is it's each ANS [15:58] verified agent would have its own fully [16:00] qualified domain name and a specific SSL [16:03] ser. [16:03] >> Yeah. So that would that would obviously [16:06] boost the the number of domain [16:07] registrations which helps all of us [16:09] regardless of if the domains are if the [16:12] whole idea of having a great generic [16:13] domain matters or not in this [16:15] circumstance. So I mean you mentioned [16:17] GoDaddy can't do it on its own. It can't [16:19] also be seen as like a GoDaddy thing [16:22] necessarily, right? It needs to be a [16:25] standard. And how does something like [16:28] that do you have like a standards board [16:30] that oversees something like that or how [16:32] does that ultimately look? [16:34] >> I think the starting point for that is [16:36] the IETF and some of the other technical [16:38] bodies. They operate very very [16:39] different. [16:40] >> Tell me about what the IETF what their [16:42] role typically is. And well, now you're [16:44] getting probably beyond my level of [16:47] expertise, but generally speaking, you [16:49] would submit a proposal or an RFC and [16:52] other companies could comment on that [16:54] and then it would ultimately I think at [16:56] the end of that process be adopted as a [16:58] protocol that can be incorporated into [17:00] other code bases and products. I think [17:03] you know I've always understood for [17:04] example the internet to be have three [17:06] components names numbers and protocols [17:08] and I can handle the names and the RA's [17:11] handled the protocol the numbers but [17:13] IETF owned the protocols and so of those [17:16] areas to adopt this as an open standard [17:20] and it makes sense in a way if you think [17:22] about the DNS as a service agnostic [17:25] platform is just a lookup engine. The [17:27] fact that we use it mostly to look up [17:29] websites is how it gained its traction. [17:32] But this could be a second life for the [17:34] DNS beyond just web resources and email [17:36] servers and using it to connect these [17:39] autonomous agents to us and to each [17:42] other. [17:43] >> Got it. So I'll drop in a link to where [17:46] people can learn more about this because [17:48] it doesn't appear that there's a website [17:50] created specifically for it. Am I right [17:52] there? [17:53] >> I think so. I think we have uh some blog [17:55] posts that also link to u some u of our [17:59] technical resources and I would [18:01] encourage folks who are more technical [18:03] than I am to take a look at some of [18:05] those some of those libraries. [18:06] >> I'll drop some links in so people can [18:08] learn more about this and you know again [18:11] it could this sounds like it could be [18:12] really exciting for the domain name [18:14] industry as a whole. Um and as you [18:16] mentioned here the alternatives aren't [18:18] necessarily pretty or they're all about [18:20] driving profit to wall gardens. So I now [18:23] understand a bit more about this. I [18:25] think I think that this blog post [18:27] explaining it really kind of helped me [18:30] as opposed to the press releases which [18:32] press releases are press releases, [18:33] right? So I do think this is [18:35] interesting. So it'll be interesting to [18:36] see how this plays out. So I'll [18:38] definitely drop some links here into the [18:40] show so people can check that out. But [18:43] now I want to talk a little bit more [18:45] about kind of general policy stuff [18:46] again. And so first of all, new top [18:49] level domains application is supposed to [18:52] open in what April of 2026. Now I [18:56] remember last time it was like okay [18:58] we're going to open in a few months or 6 [19:00] months and then it didn't happen. But it [19:02] seems like this time I can's really like [19:06] this is going to happen. What what's [19:07] your take on this as an observer and [19:09] participant? [19:10] >> I also shared your skepticism. I've been [19:13] invested in I can deadlines and dates [19:16] too many times only to be disappointed. [19:18] But just before we were recording, in [19:20] fact within maybe the last 12 hours or [19:22] so, I can announced that they'll be [19:24] opening uh applications no later than uh [19:27] midnight on April 30th, 2026. And that [19:30] they'll be and they'll be open for 105 [19:33] days, closing on August 12th. That came [19:36] through actually just a few hours ago. [19:37] So it seems like they are committed to [19:40] this timeline. We've had some [19:41] developments where governments in [19:43] particular in the Gak were the [19:45] government advisory committee were [19:46] putting new hurdles on the critical [19:48] path. [19:49] >> Even the US, right? Wasn't the [19:51] >> Yeah, even the US. Most of which involve [19:54] domain name abuse, which we can talk [19:56] about a little bit later, but it looks [19:58] like all signs at this point are still [20:00] pointing to that April 30th, late April [20:03] through August application window. Yeah, [20:06] I I think it's probably, you know, I [20:07] think although governments have pushed [20:09] back for a long time, I think they were [20:11] being pushed by trademark interests who [20:12] are pushing back, you know, and so it [20:15] seems like it's less scary this time [20:17] because we know what happened last time. [20:19] >> Yeah, I think that's correct. And I [20:20] think I can correctly determine that the [20:23] government advice was aimed more at [20:25] allocating and activating the TLDDS in [20:27] the domain name system as opposed to [20:29] allowing the application process to [20:31] proceed. So, [20:32] >> okay, [20:32] >> it seems like I can is learning to walk [20:34] and chew bubble gum at the same time and [20:36] do a couple of things in parallel as [20:38] opposed to, you know, gatekeeping each [20:41] step of the process with the previous [20:43] requirements. Now, that said, one of my [20:46] concerns about that government advice is [20:48] it was very non-specific about what the [20:52] outcome looked like. I think if you say [20:55] that you know you are requiring [20:56] something to be a prerequisite you know [20:58] for being able to allocate domain names [21:02] top level domains in the route I think [21:04] we need to be very clear about what's [21:05] our baseline and what's the percentage [21:07] improvement that we're looking for [21:09] otherwise I think it opens itself up to [21:11] more debate later on in the process [21:13] >> explain specifically what the [21:14] governments are asking for here [21:16] >> yeah I think what the government and I [21:18] don't have the exact language in front [21:20] of me but essentially they advised I can [21:22] that they wanted to see meaningful [21:24] policies developed and implemented to [21:27] address some issues regarding DNS abuse. [21:29] >> Okay. [21:30] >> Prior to activating new TLDDS for the [21:32] next round in the DNS route. And my [21:34] question is what does that look like? I [21:36] mean we've already had direct contract [21:38] negotiations between registries [21:40] registars and I can [21:43] undertake some policy development uh [21:45] work to build on those and expand those [21:48] efforts. But I'm not sure what [21:50] improvement looks like. I mean certainly [21:52] I don't think the expectation should be [21:54] that there is no fraud or crime ever on [21:57] the internet. So what sort of [21:59] improvements are we looking for? How do [22:01] we measure that? What baseline are we [22:02] establishing as our means of comparison? [22:04] And really just getting more towards a [22:06] data descriptive success outcome as [22:10] opposed to just kind of leaving the door [22:12] open for another scathing report that [22:15] will slow down the process, you know, 6 [22:17] to 12 months from now. I think about DNS [22:20] abuse and I think there's been language [22:23] re fairly recently added to what [22:26] registar accreditation agreements or was [22:28] it registry about DNS abuse right it was [22:32] both and they're implemented and they're [22:34] in force but I think you rais a good [22:36] point is they were so recent it's very [22:38] difficult to see what kind of measurable [22:41] impact they've had on the problem of DNS [22:43] abuse so we're following them up with [22:46] more work but we haven't really in my [22:48] view we haven't really controlled for [22:50] all the variables yet [22:51] >> and we don't want to come into a [22:52] situation where everyone applies they [22:54] send in their money and then we've got [22:57] this this still kind of this hurdle [23:00] hanging out there before they actually [23:02] go on the web [23:03] >> yeah I think that's right and and I [23:05] think I'm mostly concerned about just [23:07] the lack of definition and description [23:10] on how to get past that hurdle and it [23:12] just kind of we don't want to create a [23:14] situation where it's just very easy to [23:16] move the goalpost [23:17] And you know I I think about it and [23:19] there are lots of groups doing things [23:21] outside of I can on DNS abuse you [23:23] know.org has created an entire almost I [23:26] don't know if it's a subsidiary but you [23:28] know it's kind of a group there that's [23:30] focusing on it. I think Net Beacon [23:32] Institute is its current name, but I [23:34] think there's a lot of advocacy around [23:36] here and I think most players realize [23:40] this is important and it'd be great if [23:42] the industry could regulate it itself, [23:45] but there's always this competing push [23:48] here on, you know, if the industry [23:49] doesn't regulate itself and do a good [23:51] job, then that's when governments step [23:52] in. Is that [23:53] >> Yeah, I think that's a fair [23:54] characterization and I think it's in [23:56] this conversation it's important that we [23:59] don't lose sight of all those individual [24:02] organization and industry efforts and to [24:04] highlight them as you know the [24:06] responsible operators are already taking [24:09] measurable and meaningful steps to [24:11] address these problems either alone or [24:14] in conjunction with their industry [24:15] peers. And it really depends also on the [24:17] type of abuse that we're talking about. [24:19] if it's fishing malware or botn nets [24:21] there are different groups that are [24:23] spoke narrowly targeting those types of [24:25] issues that we also participate in [24:28] outside of I can I think it's important [24:30] to not lose sight of that when you go [24:32] into an IAN conversation and folks are [24:34] saying well what are we doing about DNS [24:36] abuse it's like just because it isn't [24:37] happening here doesn't mean it's not [24:39] happening anything else on DNS abuse [24:41] before we move on [24:43] >> yeah that's going to be a big topic I [24:44] think for 2026 and one of the reasons [24:46] why I think the calendar is pretty full [24:49] for other topics like UDRP reform and [24:52] why they're going to get squeezed into [24:53] 2027. There's going to be, I think, a [24:56] PDP or policy development process [24:58] launched early in 2026, perhaps at the [25:01] first meeting that will focus on new [25:04] requirements for registries and [25:05] registars. for example, put more [25:08] stringent security controls in front of [25:11] API tools and other registration [25:13] platforms to conduct what they're [25:15] calling associated domain checks with [25:17] reports of abuse. So that if for [25:19] example, if you reported to GoDaddy that [25:21] there was something happening with a [25:23] particular domain name and we did [25:25] discover that it was being used in an [25:27] abusive or malicious or fraudulent way, [25:29] we wouldn't stop the investigation [25:30] there. we would continue to look at that [25:32] account and other domain names that were [25:34] registered by that uh by that customer [25:36] to see if there was any other associated [25:38] abuse. That is a best practice that I [25:41] think most of the major players are [25:43] doing currently. But uh I think that's a [25:45] pretty big complaint which is okay. You [25:48] you shut down this one the same credit [25:50] card was used for another thousand [25:51] domains. Are you actually going to [25:53] follow up on that? [25:53] >> Exactly. just keep pulling on those [25:55] threads uh until you know you find that [25:58] that common connection in a way to [26:01] marginalize their impact on your [26:03] platform because we don't want these [26:04] folks on our platform either if they're [26:06] going to use our services for illegal [26:08] purposes. [26:10] >> Yeah. Anything else on I can I want to [26:12] talk briefly about what's going on in uh [26:14] Washington DC? No, I think for the first [26:16] half of a year it's going to be uh most [26:19] of the conversations are going to center [26:21] around DNS abuse work and also on the [26:23] new GTLD application window. There of [26:25] course are some it's I can so of course [26:27] they'll always find something new and [26:29] controversial to discuss but I think [26:31] that's going to be the sideshow and [26:32] those are going to be the two main [26:33] events for 2026. [26:35] >> Got it. So Washington, you know, it's [26:38] interesting. I I follow the NTIA's [26:40] website which is under Department of [26:42] Commerce and they hadn't announced [26:44] anything since, you know, the renewal of [26:46] the Verisign contract until just [26:49] recently actually, which we don't need [26:51] to dig into it because it directly [26:52] impacts GoDaddy. It was the US contract [26:55] which GoDaddy registry still manages. [26:58] But I was kind of like, are we going to [26:59] hear anything out of here, you know, and [27:01] what's going on? So what should we be [27:03] keeping an eye on in DC right now? Yeah, [27:06] I think there are a few things that are [27:07] not specific to the domain name [27:08] industry, but just technology in general [27:10] that are worth watching. I mean, the [27:13] first one is the US still does not have [27:16] data protection legislation at the [27:18] federal level. So, it's popping up in [27:20] different states. I know you live in [27:22] Washington now. It has pretty robust uh [27:24] data protection laws on the books at the [27:26] state level. In other states, it may be [27:28] just still completely absent. I think [27:31] the challenge now is that if you try to [27:33] introduce uh data protection at the [27:35] federal level, it runs into the [27:38] congressional delegations from the [27:39] states that already have solid [27:41] protections like Washington or [27:42] California. They're not obviously [27:44] they're not going to support or vote for [27:46] something that reduces the protections [27:48] that they're residents currently have on [27:50] the internet. This is challenging for [27:52] companies like GoDaddy that operate in [27:55] every state and also globally is trying [27:57] to find that high watermark between all [28:00] the different states of what the most uh [28:02] stringent data protection framework is [28:05] and then aim our services and products [28:07] towards that and not just us but also [28:10] helping our customers navigate those [28:12] waters. I think we're also seeing a lot [28:14] of work on a lot of conversations about [28:17] section 230 which is something that [28:19] comes up quite a bit in my circles but I [28:21] don't know if that's uh something your [28:23] audience [28:23] >> this is the one that kind of protects [28:24] like well if someone comments on domain [28:27] name wire that sort of thing about if [28:29] it's my you know on X or Facebook am I [28:31] responsible for it or is the other [28:33] person [28:34] >> exactly it gives you as a platform [28:36] operator some degree of protection from [28:38] the things that third party users you [28:41] you know say and do on [28:43] on your service. And you can imagine, [28:45] for example, a company that was a [28:47] massive web host, if they were [28:49] responsible for everything that their [28:51] customers generated on the web, that [28:53] would be a completely different legal [28:54] landscape than what we're operating in [28:56] today. So, I think we continue to see [28:59] talk of either reforming section 230 or [29:03] even sunsetting it. And I think that [29:05] would be for so many businesses that [29:08] would be just almost an existential [29:10] impact to their risk profile. I was [29:13] joking, but not only half joking. I [29:15] said, you know, if you want to see the [29:16] S&P 500 drop 20% in one day, go ahead [29:19] and cancel section 230. [29:20] >> Get rid of 230. Huh. Yeah. Yeah. [29:23] Definitely. It's interesting even as a [29:24] website operator, you know, you see [29:26] you've got the EU's rules. You've got, [29:29] you know, I know a lot of sites now say, [29:30] you know, California residents, if you [29:32] want to do this, you know, click here. [29:34] you know, kind of thing on their site. [29:35] And that's obviously not ideal for any [29:38] anyone in the internet space. So, [29:40] >> yeah. And if you're traveling overseas [29:41] and you try to access your hometown [29:43] newspaper or look up something, you [29:45] know, for sports local sports team and [29:47] you find you're blocked because of, you [29:48] know, they don't want to [29:49] >> Google News is blocked in a lot of [29:51] countries, right? Cuz the countries are [29:52] like, you've got to pay the public, you [29:54] know. So yeah, [29:55] >> it's changing the way that I grew up [29:58] with the internet in that it was a [30:00] consistent uh customer and user [30:03] experience no matter where you were, you [30:05] know, on the planet or no matter, you [30:06] know, where you were in the country. And [30:08] unfortunately, it's just part of that [30:10] continued fragmentation along national [30:12] and state boundaries. So final question [30:15] for domain investors that are listening [30:17] to this show that have never gone to an [30:19] ICAN meeting. There are so next year [30:21] there's the the spring meeting. That's [30:24] the what do they call the spring [30:26] meeting? [30:26] >> That is good question. I think that's [30:28] the community forum. [30:30] >> That's not the summer one. No, the [30:32] summer is the policy form. So it goes [30:34] community policy and annual. So you've [30:37] got but you know everything gets talked [30:38] about at all of them right to some [30:41] degree. So you've got Mumbai in the [30:43] spring, you've got Sevilla in the [30:46] summer, and then you have Oman, [30:49] >> back to Oman, [30:49] >> and back to Oman in the fall. And then, [30:51] of course, there's a contracted party [30:53] summit as well, which I believe is April [30:56] in Europe. I know they haven't formally [30:57] announced the place. Most people are [30:59] talking about it anyway, but [31:00] >> Exactly. [31:01] >> But if someone were to go to the first [31:03] meeting and they're a domain investor, [31:05] which of those, you know, geography, you [31:08] know, doesn't matter. Which of those [31:09] would you recommend that they go to next [31:11] year? [31:12] >> Wow, good question. I mean, I always say [31:14] geography does matter. I mean, that's [31:16] why the Seattle meeting was so popular. [31:19] >> But if that were not a consideration, I [31:21] think more impactful work is discussed [31:24] and completed in the AGM, the larger [31:26] meeting at the end of the year [31:28] >> where it's not only the policy work, but [31:30] also, you know, the internal [31:31] housekeeping and governance more [31:33] broadly. Uh whether it's, you know, [31:35] council turnover and or board leadership [31:38] changes. I think that's where that's [31:39] where more work is being done. But [31:42] honestly, I think that really there's [31:44] only um a few issues that are currently [31:48] bouncing around ICAM that could impact a [31:50] main investors. For example, [31:53] understanding um you know what's going [31:55] to happen with the next round and [31:57] whether or not they want to participate [31:58] in some of those TLDs that are coming [32:00] out or potentially changes around the [32:04] rules for privacy and proxy services. [32:06] Some I think some investors may like [32:08] those because it allows them to have a [32:10] portfolio acquisition without tipping [32:13] their hand on what their strategy might [32:14] be and some domain investors may not [32:16] like those because it's friction in [32:18] between them and maybe transacting with [32:20] another party that might be uh using a [32:22] privacy service. So changing around [32:24] rules about those and then I think yeah [32:26] and then understanding what the [32:29] registries and registars are doing [32:31] separately in terms of their strategies [32:32] like right now I think a lot of [32:34] registries and registars have [32:35] acknowledged that domain name parking [32:37] revenue has gone off a cliff and so what [32:39] does that mean for their product [32:40] offering are they going to scale back [32:42] their you know their focus in serving [32:44] those clients so all of that I think is [32:46] worth paying attention to and I think [32:48] again just going back to how we opened [32:50] our conversation it's why it's so [32:52] important for folks like you, folks like [32:55] me and other folks in this space to be [32:57] able to sit on a lot of these hour-long [33:00] calls and and attend these week-long [33:02] meetings so that we can bring back those [33:03] nuggets of valuable information and [33:05] those those truly impactful bits of [33:08] policy work and then synthesize those [33:10] for a more mainstream audience that [33:13] really doesn't have the time to follow [33:15] this stuff as closely as we do. [33:16] >> And so specifically, one way to do that [33:18] is to join the Internet Commerce [33:20] Association. [33:21] >> Absolutely. And they do do a good job of [33:23] synthesiz not getting into the weeds [33:26] unless you want to you know they [33:28] obviously call on people to participate [33:29] at a higher level but just to understand [33:32] kind of what's going on and provide [33:33] feedback because even amongst you know [33:36] the ICA board they're there people with [33:38] different interests right who might have [33:40] different opinions on things so you know [33:42] uh providing feedback on how the A [33:45] should advocate [33:46] >> yeah I think understanding what the [33:49] legislative pri and policy priorities [33:51] should be is half the battle. You know, [33:53] once you have that nailed down and [33:55] established, then going out and taking [33:56] that into I can or taking that into [33:58] Washington DC. I don't want to say [34:00] that's the easier part, but it's [34:01] certainly the more straightforward [34:02] exercise. But understanding what the [34:05] membership of a group like a wants. It [34:08] can't just be to stop everything from [34:10] changing, but maybe there could be [34:12] something to advancing their ideals and [34:14] their interests and getting that fed [34:16] into the policy development process. [34:18] Well, James, thanks so much for coming [34:20] on the show today. I'll of course uh [34:22] check out the blog post here for links [34:24] to information about agent name service [34:26] if you want to dig into that more. And [34:28] then James, I assume you'll be at the [34:29] ICA meeting in January. [34:31] >> Yep. Looking forward to it. My first [34:32] one. [34:33] >> If anyone hasn't met James, there's a [34:35] great opportunity to do that. So, thanks [34:37] so much for coming on the show. [34:39] >> Thanks for having me. It's always a [34:40] pleasure. [34:40] >> My guest this week has been James [34:42] Bladel. He is the VP of corporate and [34:44] government affairs at GoDaddy. That's a [34:47] wrap on this week's Domainwire podcast. [34:49] You can listen to all previous episodes [34:51] at dnw.com/mpodcast [34:53] or on your favorite podcast app. Thanks [34:56] for [music] listening. [35:04] [music] [35:12] >> [music]