%% You should probably cite draft-ietf-emu-eaptlscert-08 instead of this revision.
@techreport{ietf-emu-eaptlscert-07,
	number =	{draft-ietf-emu-eaptlscert-07},
	type =		{Internet-Draft},
	institution =	{Internet Engineering Task Force},
	publisher =	{Internet Engineering Task Force},
	note =		{Work in Progress},
	url =		{https://datatracker.ietf.org/doc/html/draft-ietf-emu-eaptlscert-07},
        author =	{Mohit Sethi and John Preuß Mattsson and Sean Turner},
	title =		{{Handling Large Certificates and Long Certificate Chains in TLS-based EAP Methods}},
	pagetotal =	14,
	year =		** No value found for 'doc.pub_date.year' **,
	month =		** No value found for 'doc.pub_date' **,
	day =		** No value found for 'doc.pub_date.day' **,
	abstract =	{The Extensible Authentication Protocol (EAP), defined in RFC3748, provides a standard mechanism for support of multiple authentication methods. EAP-Transport Layer Security (EAP-TLS) and other TLS-based EAP methods are widely deployed and used for network access authentication. Large certificates and long certificate chains combined with authenticators that drop an EAP session after only 40 - 50 round-trips is a major deployment problem. This document looks at this problem in detail and describes the potential solutions available.},
}