Key takeaways
- On Nov. 19, NIST's National Cybersecurity Center of Excellence released the second public draft of SP 1800-42, a guide to accepting mobile driver's licenses (mDLs) online. Comments are due Dec. 20, 2026.
- NIST says 22 states and territories have active mDL programs, yet very few online service providers accept them.
- A specific, well-supported comment puts your expertise in front of the program staff who write the guidance, at almost no cost.
- Once it's filed, the same comment becomes content for your own channels and a relevant, low-pressure reason to contact state ID issuers and benefits agencies.
Most vendors treat a draft standard as something to read after it's final. That's a missed opportunity. While a draft is open for comment, the agency is asking outside experts to tell it what it got wrong, and the people reading those comments are the program staff who shape the work that follows.
NIST's new mobile driver's license guide is a good example, and the window is open for four more weeks.
What NIST released
On Nov. 19, NIST's National Cybersecurity Center of Excellence (NCCoE) published the second public draft of Special Publication 1800-42, Digital Identities — Mobile Driver's License (mDL): Enabling Secure and Interoperable Online Use. The guide shows how organizations can verify a person's identity online with an mDL, built with commercially available technology.
The numbers in NIST's announcement explain why it matters:
- Issuance is growing. Twenty-two U.S. states and territories have active mDL programs, and NIST says at least 5 million mDLs are in use, with about 47% of the population having access to one.
- Online acceptance isn't. NIST says very few online service providers currently accept mDLs. "Our goal is to help overcome the barriers preventing organizations from accepting mDLs online," said Bill Fisher, a NIST security engineer and one of the project's organizers.
- The scope is widening. The first draft, released in March with comments closed May 8, focused on financial institutions. NIST said then that the next phase would cover citizen-to-government identity verification, working with collaborators such as the General Services Administration's Login.gov. According to Govly, NIST expects a final guide in 2027 and is developing a follow-on volume for federal and state credential service providers.
The project's collaborators include the American Association of Motor Vehicle Administrators (AAMVA), the California and New York motor vehicle agencies, the Maryland Department of Transportation and the Department of Homeland Security's Science and Technology Directorate, alongside banks and technology companies.
Why comment periods are underused marketing
Government buyers say the same thing in different ways: they want vendors who understand their problem before the first meeting. A public comment is one of the few places you can show that in writing, to the right audience, without asking anyone for anything.
- It reaches the people who write the guidance. NCCoE staff read the comments, and the state agencies and companies collaborating on the project have a stake in where the guide goes.
- It shows judgment, not a pitch. A comment that points out a gap in a threat model or an interoperability problem says more about your team than a capabilities deck.
- It's early. You engage while the guidance is still being written, not after it shows up in a solicitation.
This applies well beyond mDLs. Federal Register notices, state rulemakings and draft frameworks all open similar windows. Our guide to government buying signals covers where to find them.
How to write a comment program staff remember
NIST accepts comments on this draft by email to mdl-nccoe@nist.gov or as an issue on the project's public GitHub repository, both linked from the project's comments page. Name and organization are optional, but a vendor that wants credit should include them. The comments page asks for a use case reference, the topic your comment addresses and your text.
EPA's archived guidance on effective comments holds up well for any agency:
- Read the instructions. Comment on what the draft actually covers. Off-topic comments get set aside.
- Be specific. Point to the section, suggest replacement language where you can, and use an example from real deployments.
- Say what works, too. Telling the agency which parts you support is as useful as telling it what to change.
- Organize it. Use short headings so each point can be read on its own.
- Skip the sales language. A comment that reads like marketing undercuts the credibility you're trying to build. As EPA puts it, "A single, well-supported comment may carry more weight than a thousand form letters."
Have your subject matter expert write it, and leave product names out unless they're needed to make a technical point.
Turn one comment into content and conversations
The comment itself is a modest win. The bigger value is what you can do with it afterward.
- Publish a short version. A blog post or LinkedIn article summarizing what you told NIST, and why, gives buyers a useful read on a topic they're tracking.
- Brief the trade press. Identity and government technology outlets cover NIST drafts; Biometric Update wrote up the first one in March. Our list of government trade publications is a place to start.
- Contact the buyers the guide affects. State ID issuers and the benefits, licensing and tax agencies that verify identity online are the natural audience. A short note that says what the draft means for online services like theirs, links your comment and asks whether a 20-minute conversation would be useful is easy to answer and easy to decline.
- Follow up when the final guide lands. When NIST publishes the final version, you have a reason to get back in touch, with notes on what changed.
Keep the outreach low-pressure. Agencies on their own mDL timelines won't buy because a comment period is closing, and they don't need to be told they're behind.
How KSG helps
Kensington Sales Group's market intelligence team tracks draft standards, comment periods and other early signals, then identifies the program owners at the agencies they affect. Our SDRs turn that research into respectful, specific outreach and set meetings with buyers who want the conversation. Since 2016 we've set more than 10,000 qualified meetings across Federal, SLED, K-12 & Higher Ed, Healthcare, Tribal, Special Districts and Utilities buyers.
Sources: NIST, NIST project aims to accelerate mobile driver's license adoption (November 19, 2026); NIST NCCoE, Digital Identities: Mobile Driver's License project page; NIST NCCoE, mDL project comments page; NIST, Guidelines on implementing mobile driver's licenses for financial institutions (March 18, 2026); NIST CSRC, SP 1800-42 initial public draft; Govly, NIST advances mobile driver's license integration (November 21, 2026); Biometric Update, NIST publishes draft guidelines for financial firms implementing mDLs (March 2026); U.S. EPA (archived), Tips for providing effective comments.