@techreport{ietf-radext-populating-eapidentity-01,
    number =    {draft-ietf-radext-populating-eapidentity-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-ietf-radext-populating-eapidentity/01/},
    author =    {Stefan Winter},
    title =     {{Considerations regarding the correct use of EAP-Response/Identity}},
    pagetotal = 10,
    year =      2016,
    month =     jul,
    day =       8,
    abstract =  {There are some subtle considerations for an EAP peer regarding the content of the EAP-Response/Identity packet when authenticating with EAP to an EAP server. This document describes two such considerations and suggests workarounds to the associated problems. One of these workarounds is a new requirement for EAP peers that the use of UTF-8 is required for the content of EAP-Response/Identity (which updates RFC3748).},
}