The eduroam architecture for network roaming
draft-wierenga-ietf-eduroam-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-01-21
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-wierenga-ietf-eduroam
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        K. Wierenga
Internet-Draft                                             Cisco Systems
Intended status: Informational                                 S. Winter
Expires: July 25, 2014                                           RESTENA
                                                           T. Wolniewicz
                                          Nicolaus Copernicus University
                                                        January 21, 2014

              The eduroam architecture for network roaming
                   draft-wierenga-ietf-eduroam-02.txt

Abstract

   This document describes the architecture of the eduroam service for
   federated (wireless) network access in academia.  The combination of
   802.1X, EAP and RADIUS that is used in eduroam provides a secure,
   scalable and deployable service for roaming network access.  The
   successful deployment of eduroam over the last decade in the
   educational sector may serve as an example for other sectors, hence
   this document.  In particular the initial architectural and standards
   choices and the changes that were prompted by operational experience
   are highlighted.

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 July 25, 2014.

Copyright Notice

   Copyright (c) 2014 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

Wierenga, et al.          Expires July 25, 2014                 [Page 1]
Internet-Draft                   eduroam                    January 2014

   (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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
     1.3.  Design Goals  . . . . . . . . . . . . . . . . . . . . . .   4
     1.4.  Solutions that were considered  . . . . . . . . . . . . .   5
   2.  Classic Architecture  . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Authentication  . . . . . . . . . . . . . . . . . . . . .   6
       2.1.1.  802.1X  . . . . . . . . . . . . . . . . . . . . . . .   6
       2.1.2.  EAP . . . . . . . . . . . . . . . . . . . . . . . . .   7
     2.2.  Federation Trust Fabric . . . . . . . . . . . . . . . . .   8
       2.2.1.  RADIUS  . . . . . . . . . . . . . . . . . . . . . . .   8
   3.  Issues with initial Trust Fabric  . . . . . . . . . . . . . .  10
     3.1.  Server Failure Handling . . . . . . . . . . . . . . . . .  10
     3.2.  No error condition signalling . . . . . . . . . . . . . .  12
     3.3.  Routing table complexity  . . . . . . . . . . . . . . . .  13
     3.4.  UDP Issues  . . . . . . . . . . . . . . . . . . . . . . .  13
     3.5.  Insufficient payload encryption and EAP server validation  14
   4.  New Trust Fabric  . . . . . . . . . . . . . . . . . . . . . .  16
     4.1.  RADIUS with TLS . . . . . . . . . . . . . . . . . . . . .  16
     4.2.  Dynamic Discovery . . . . . . . . . . . . . . . . . . . .  18
       4.2.1.  Discovery of responsible server . . . . . . . . . . .  18
       4.2.2.  Verifying server authorisation  . . . . . . . . . . .  19
       4.2.3.  Operational Experience  . . . . . . . . . . . . . . .  20
       4.2.4.  Possible Alternatives . . . . . . . . . . . . . . . .  20
   5.  Abuse prevention and incident handling  . . . . . . . . . . .  20
     5.1.  Incident Handling . . . . . . . . . . . . . . . . . . . .  21
     5.2.  Operator Name . . . . . . . . . . . . . . . . . . . . . .  22
     5.3.  Chargeable User Identity  . . . . . . . . . . . . . . . .  23
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  24
     6.1.  Collusion of Service Providers  . . . . . . . . . . . . .  24
     6.2.  Exposing user credentials . . . . . . . . . . . . . . . .  24
Show full document text