Browse Prior Art Database

Extensible Authentication Protocol (EAP) Attributes for (RFC7458)

IP.com Disclosure Number: IPCOM000240768D
Original Publication Date: 2015-Feb-01
Included in the Prior Art Database: 2015-Feb-27
Document File: 36 page(s) / 39K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Valmikam: AUTHOR [+2]

Abstract

Wi-Fi has emerged as a "trusted" access technology for mobile service providers; see [EPC2] for reference to the 3rd Generation Partnership Project (3GPP) description of "trusted" access. Advances in IEEE 802.11u [IEEE802.11u] and "HotSpot 2.0" [hs20] have enabled seamless roaming, in which a Mobile Node can select and connect to a Wi-Fi access network just as it would roam into a cellular network. It has thus become important to provide certain functions in Wi-Fi that are commonly supported in licensed-spectrum networks such as 3G and 4G networks. This document specifies a few new EAP attributes for an MN to interact with the network to support some of these functions (see below). These new attributes serve as a trigger for Proxy Mobile IPv6 network nodes to undertake the relevant mobility operations. For instance, when the MN requests a new IP session (i.e., a new APN in 3GPP) and the network agrees, the corresponding attribute (defined below) acts as a trigger for the Mobile Anchor Gateway (MAG) to initiate a new mobility session with the Local Mobility Anchor (LMA). This document refers to [RFC6459] for the basic definitions of mobile network terminology (such as APN) used here.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Internet Engineering Task Force (IETF)                       R. Valmikam Request for Comments: 7458                                  Unaffiliated Category: Informational                                        R. Koodli ISSN: 2070-1721                                                    Intel                                                            February 2015

         Extensible Authentication Protocol (EAP) Attributes for              Wi-Fi Integration with the Evolved Packet Core

Abstract

   With Wi-Fi emerging as a crucial access network for mobile service    providers, it has become important to provide functions commonly    available in 3G and 4G networks in Wi-Fi access networks as well.    Such functions include Access Point Name (APN) Selection, multiple    Packet Data Network (PDN) connections, and seamless mobility between    Wi-Fi and 3G/4G networks.

   The EAP Authentication and Key Agreement (EAP-AKA), and EAP-AKA',    protocol is required for mobile devices to access the mobile Evolved    Packet Core (EPC) via Wi-Fi networks.  This document defines a few    new EAP attributes to enable the above-mentioned functions in such    networks.  The attributes are exchanged between a client (such as a    Mobile Node (MN)) and its network counterpart (such as an    Authentication, Authorization, and Accounting (AAA) server) in the    service provider's infrastructure.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7458.

 Valmikam & Koodli             Informational                     [Page 1]
 RFC 7458       EAP Attributes for Wi-Fi - EPC Integration  February 2015

 Copyright Notice

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