%% You should probably cite draft-richardson-emu-eap-onboarding-03 instead of this revision.
@techreport{richardson-emu-eap-onboarding-01,
    number =    {draft-richardson-emu-eap-onboarding-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-richardson-emu-eap-onboarding/01/},
    author =    {Alan DeKok and Michael Richardson},
    title =     {{EAP defaults for devices that need to onboard}},
    pagetotal = 9,
    year =      2022,
    month =     jul,
    day =       25,
    abstract =  {This document describes a method by which an unconfigured device can use EAP to join a network on which further device onboarding, network attestation or other remediation can be done. While RFC 5216 supports EAP-TLS without a client certificate, that document defines no method by which unauthenticated EAP-TLS can be used. This draft addresses that issue. First, by defining the @eap.arpa domain, and second by showing how it can be used to provide quarantined network access for onboarding unauthenticated devices.},
}