BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Sabre//Sabre VObject 4.5.8//EN CALSCALE:GREGORIAN LAST-MODIFIED:20240925T180427Z BEGIN:VTIMEZONE TZID:America/Los_Angeles X-MICROSOFT-CDO-TZID:13 BEGIN:STANDARD DTSTART:20231105T090000 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 TZNAME:PST END:STANDARD BEGIN:STANDARD DTSTART:20241103T090000 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 TZNAME:PST END:STANDARD BEGIN:DAYLIGHT DTSTART:20240310T100000 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT UID:4063788d-6e26-4d19-8898-d7ceb448fca9 DTSTAMP:20240925T180427Z SUMMARY:Responsible Integration and New Use Cases of DNS Domain Names DTSTART;TZID=America/Los_Angeles:20240925T111500 DTEND;TZID=America/Los_Angeles:20240925T121500 DESCRIPTION:https://www.w3.org/events/meetings/4063788d-6e26-4d19-8898-d7ce b448fca9/\n\nDomain names have long been used as identifiers in applicatio ns. In the early days of the Domain Name\nSystem (DNS)\, domain names were associated with Teletype Network hosts\, File Transfer Protocol servers\, \nand email services. Later\, they were adopted for web browsing.\n\nOver the last several years\, many novel use cases have emerged that utilize do main names. One such use\ncase is allowing a user to verify control of a d omain name\, e.g.\, to show a verified badge on a profile as is\nseen with GitHub organizations. Another use case is as a social media handle\, e.g. \, as performed in Bluesky.\nBlockchains and other decentralized applicati ons are yet another use case\, e.g.\, where a domain name may\nserve as a reference to a digital wallet address as seen in the Ethereum Name Service (ENS) or in various\nproposed Decentralized Identifiers (DID) methods.\n\ nWe propose naming the process of integrating and maintaining a domain nam e into an application a DNS\nintegration. These integrations have benefits \, such as allowing users to keep a consistent identifier across\ntheir we bsite\, email\, and new application use cases. Another benefit is portabil ity\, as users can opt into or\nout of integrations\, e.g.\, by changing w hat DNS records are associated with their domain name.\n\nThis session wil l raise awareness of DNS integrations\, the challenges they face\, and fac ilitate discussions\naround how such challenges may be addressed. We will also highlight our IETF draft for DNS integrations and\nseek feedback from the community on additional topics to consider in this or future standard s related work.\n\nAgenda\n\n**Chairs:**\nSwapneel Sheth\n\n**Description: **\nDomain names have long been used as identifiers in applications. In th e early days of the Domain Name\nSystem (DNS)\, domain names were associat ed with Teletype Network hosts\, File Transfer Protocol servers\,\nand ema il services. Later\, they were adopted for web browsing.\n\nOver the last several years\, many novel use cases have emerged that utilize domain name s. One such use\ncase is allowing a user to verify control of a domain nam e\, e.g.\, to show a verified badge on a profile as is\nseen with GitHub o rganizations. Another use case is as a social media handle\, e.g.\, as per formed in Bluesky.\nBlockchains and other decentralized applications are y et another use case\, e.g.\, where a domain name may\nserve as a reference to a digital wallet address as seen in the Ethereum Name Service (ENS) or in various\nproposed Decentralized Identifiers (DID) methods.\n\nWe propo se naming the process of integrating and maintaining a domain name into an application a DNS\nintegration. These integrations have benefits\, such a s allowing users to keep a consistent identifier across\ntheir website\, e mail\, and new application use cases. Another benefit is portability\, as users can opt into or\nout of integrations\, e.g.\, by changing what DNS r ecords are associated with their domain name.\n\nThis session will raise a wareness of DNS integrations\, the challenges they face\, and facilitate d iscussions\naround how such challenges may be addressed. We will also high light our IETF draft for DNS integrations and\nseek feedback from the comm unity on additional topics to consider in this or future standards related work.\n\n**Goal(s):**\nRaise awareness of DNS integrations and seek feedb ack for active standards work on providing guidance to applications that w ant to provide a DNS integration\n\n\n**Agenda:**\nThe agenda will be two parts.\nPart one will be a presentation to provide background context that :\n\n- Walks through examples of DNS integrations and their use cases (soc ial\, digital wallets\, identity\, etc.)\n- Explores why applications have chosen to provide DNS integrations\n- Provides measurement results showin g challenges that select DNS integrations face\n- Promotes awareness of ou r IETF draft for DNS integrations and the topics it currently covers\n\nPa rt two will be a discussion among participants about DNS integrations and what additional topics or\nconcepts should be covered in the current IETF draft or future standards work\, including at the W3C.\n\n**Materials:**\n - [Session proposal on GitHub](https://github.com/w3c/tpac2024-breakouts/i ssues/80) STATUS:CONFIRMED CREATED:20240916T220033Z LAST-MODIFIED:20240925T180427Z SEQUENCE:1 ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor eply@w3.org LOCATION:4 Concourse Level - Huntington CATEGORIES:TPAC 2024,Breakout Sessions END:VEVENT END:VCALENDAR