ABFAB Working Group S. Winter
Internet-Draft RESTENA
Intended status: Standards Track J. Salowey
Expires: September 19, 2013 Cisco
March 18, 2013
Update to the EAP Applicability Statement for ABFAB
draft-ietf-abfab-eapapplicability-02
Abstract
This document updates the Extensible Authentication Protocol (EAP)
applicability statement from RFC3748 to reflect recent usage of the
EAP protocol in the Application Bridging for Federated Access Beyond
web (ABFAB) working group.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 19, 2013.
Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Winter & Salowey Expires September 19, 2013 [Page 1]
Internet-Draft EAP Applicability March 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Uses of EAP for Application-Layer Access . . . . . . . . . . 2
2.1. Retransmission . . . . . . . . . . . . . . . . . . . . . 4
2.2. Re-Authentication . . . . . . . . . . . . . . . . . . . . 4
3. Revised EAP applicability statement . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. Informational References . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The EAP applicability statement in [RFC3748] defines the scope of the
Extensible Authentication Protocol to be "for use in network access
authentication, where IP layer connectivity may not be available.",
and states that "Use of EAP for other purposes, such as bulk data
transport, is NOT RECOMMENDED.".
While some of the recommendation against usage of EAP for bulk data
transport is still valid, some of the other provisions in the
applicability statement have turned out to be too narrow. Section 2
describes the example where EAP is used to authenticate application
layer access. Section 3 provides new text to update the paragraph
1.3. "Applicability" in [RFC3748].
1.1. Requirements Language
In this document, several words are used to signify the requirements
of the specification. The key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in RFC 2119. [RFC2119]
2. Uses of EAP for Application-Layer Access
Ongoing work in the IETF (abfab working group) specifies the use of
EAP over GSSAPI for generic application layer access. In the past,
using EAP in this context has met resistance due to the lack of
datatracker.ietf.org