# Talks, Articles & Press This section is the curated public record. Anything we link here is on someone else's site, under their byline, in their own words. It is the place to go when you want to see what is actually being said about vCon in public, by whom, and where. If you arrived here from the home page looking for evidence that vCon is more than a single vendor's idea, the layers below are where that evidence lives. ## Where to look, by what you want to verify The IETF process is itself the strongest evidence that vCon is being built in the open. Specific public statements from carriers, platforms, regulators, and civil society organizations show up across the subsections. * **The standards process.** The [IETF VCON working group datatracker page](https://datatracker.ietf.org/wg/vcon/) is the primary source. Charter, drafts, mailing list archives, and meeting minutes are all public and permanent. See also [IETF Sessions](/talks-articles-press/ietf-sessions.md) below. * **Industry adoption and analyst framing.** [Conference Keynotes](/talks-articles-press/conference-keynotes.md) and [Articles & Press](/talks-articles-press/articles-and-press.md) collect talks and longform writing from TADSummit, TADHack, Telecom Reseller, Medium, and analyst blogs. * **Audio commentary.** [Podcasts](/talks-articles-press/podcasts.md), anchored by Jeff Pulver's ongoing Substack series, is the rolling commentary track on vCon's adoption. * **Related standards work.** SCITT is the IETF effort vCon pairs with for lifecycle integrity. Talks linking the two appear in [Conference Keynotes](/talks-articles-press/conference-keynotes.md) and [Podcasts](/talks-articles-press/podcasts.md); the deep dive lives at [SCITT and vCon](/deep-dives/scitt-supply-chain-integrity-transparency-and-trust.md). ## How to use this section * **Get oriented quickly.** Pick one talk from [Conference Keynotes](/talks-articles-press/conference-keynotes.md) and one article from [Articles & Press](/talks-articles-press/articles-and-press.md). Forty minutes will give you a working mental model. * **Cite vCon.** When you need a durable link for a deck, blog post, or RFP, prefer pinned items at the top of each subsection. * **Track the working group.** [IETF Sessions](/talks-articles-press/ietf-sessions.md) is the closest thing to a primary source for where the spec is going next. * **Find a quote.** Each subsection is reverse chronological. The most recent public statements are at the top. ## Subsections * [IETF Sessions](/talks-articles-press/ietf-sessions.md) — every IETF VCON working group session with recording and minutes * [Conference Keynotes](/talks-articles-press/conference-keynotes.md) — TADSummit, TADHack, Generative AI Expo, and other event talks * [Podcasts](/talks-articles-press/podcasts.md) — audio interviews, including Jeff Pulver's ongoing Substack series * [Articles & Press](/talks-articles-press/articles-and-press.md) — longform writing, press coverage, and analyst commentary ## A note on attribution We link to public material by the speakers and authors who produced it. We do not characterize positions of organizations beyond what those organizations have said themselves in public, on the record. If you want to know what a given carrier, platform, regulator, or civil society organization thinks about vCon, follow the links to their own words. ## Submitting links Recorded a talk, written an article, or run a podcast episode about vCon? The lightest path is a pull request against `talks-articles-press/` in [vcon-dev/vcon-docs](https://github.com/vcon-dev/vcon-docs). Keep entries to one line plus a short takeaway, reverse chronological within each subsection. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.conserver.io/talks-articles-press.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.