Document Action: 'EAP Attributes for Wi-Fi - EPC Integration' to Informational RFC (draft-ietf-netext-wifi-epc-eap-attributes-16.txt)

The IESG <iesg-secretary@ietf.org> Mon, 05 January 2015 18:22 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41CE91A8777; Mon, 5 Jan 2015 10:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level:
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_22=0.6, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qzdZl9MvqH5S; Mon, 5 Jan 2015 10:22:48 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEED1A879D; Mon, 5 Jan 2015 10:22:32 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'EAP Attributes for Wi-Fi - EPC Integration' to Informational RFC (draft-ietf-netext-wifi-epc-eap-attributes-16.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150105182232.16842.18193.idtracker@ietfa.amsl.com>
Date: Mon, 05 Jan 2015 10:22:32 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/DPmLHjzo5KCMfaT-F48-iMjvnrY
Cc: netext mailing list <netext@ietf.org>, netext chair <netext-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jan 2015 18:22:50 -0000

The IESG has approved the following document:
- 'EAP Attributes for Wi-Fi - EPC Integration'
  (draft-ietf-netext-wifi-epc-eap-attributes-16.txt) as Informational RFC

This document is the product of the Network-Based Mobility Extensions
Working Group.

The IESG contact persons are Brian Haberman and Ted Lemon.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-netext-wifi-epc-eap-attributes/




Technical Summary:

   With WiFi beginning to establishing itself as a trusted access
   network for service providers, it has become important to provide
   functions commonly available in 3G and 4G networks in WiFi access
   networks.  Such functions include Access Point Name (APN) Selection,
   multiple Packet Data Network (PDN) connections and seamless mobility
   between WiFi and 3G/4G networks.

   EAP/AKA (and EAP/AKA') is standardized by 3GPP as the access
   authentication protocol for trusted access networks.  This IETF
   specification is required for mobile devices to access the 3GPP
   Evolved Packet Core (EPC) networks.  This document defines a few new
   EAP attributes and procedures to provide the above-mentioned
   functions in trusted WiFi access networks.

Working Group Summary:

This document has been in a dormant state for a while. There is no
controversy regarding the document. Using EAP attributes to address a
problem that is faced in mobile networks when attaching via WiFi is
one solution. And there is enough consensus in the WG w.r.t the
solution.


Document Quality:

There are no known implementations of the attributes for EAP defined
by this document. At this time there is'nt any indication from vendors
or 3GPP to use the approach specified by this document.
The document has acknowledged the one person who has helped in
improving the specification. The document does not specify any media
type or MIB and hence no specialists have been consulted for reviews.

Personnel:

Document Shepherd: Basavaraj Patil
Responsible AD: Brian Haberman