Skip to main content

Usage Scenarios and Requirements for Multi-hop EAP Lower Layer
draft-ohba-multihop-eap-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Gerardo Giaretta
Last updated 2005-02-14
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

All EAP lower layers that have been defined for network access authentication have the requirement that an EAP peer and an EAP authenticator are in the same IP subnet. This draft describes some scenarios where relaxing this requirement so that the EAP peer and the EAP authenticator are multiple IP hops away from each other could be useful or necessary. The draft also extracts a set of requirements for the design of such a multi-hop EAP lower layer based on the scenarios.

Authors

Gerardo Giaretta

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)