[netext] Review of I-D: draft-ietf-netext-wifi-epc-eap-attributes-06

Basavaraj Patil <bpatil1@gmail.com> Mon, 17 March 2014 21:48 UTC

Return-Path: <bpatil1@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 211B51A031F for <netext@ietfa.amsl.com>; Mon, 17 Mar 2014 14:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id XE1jDBRSXQXs for <netext@ietfa.amsl.com>; Mon, 17 Mar 2014 14:48:38 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A467D1A0303 for <netext@ietf.org>; Mon, 17 Mar 2014 14:48:38 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i4so6404007oah.29 for <netext@ietf.org>; Mon, 17 Mar 2014 14:48:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=uE61yYea9HgEltZzMdocyM+whBWkJWHrxhqKC+FrbCo=; b=JC46ImHO8KY3W3Bl/P5OMa93w4+aCpgW5k4sB0kETojTyr4rBn7+OuED12tmVnWtxX +ra8HjSG8cqSfrJlG/wD+7C6Le4CmFgO0xr5DolTccKejAdPtwnG3T6MV78OzHIkQFP6 u3vonfIZy3MUCejKeIqKPbZipEPYORBkzU0erFDd4A6g76YWwcEOlS/fKndTUalToE7A YrUURJ6gu0e6LaoueoDdyOXuOaUuwE0e2QyV/BL1R6YmZMgDBhGxqYKl07/xEOmRt9l8 OX3Cy1wDFIUaKajPyA23lVBp1QlWVQzfkS0c2A23R/15DouHw1HVQVbO/46z9UoswaJ0 fN/A==
MIME-Version: 1.0
X-Received: by with SMTP id u10mr22547766obz.22.1395092910457; Mon, 17 Mar 2014 14:48:30 -0700 (PDT)
Received: by with HTTP; Mon, 17 Mar 2014 14:48:30 -0700 (PDT)
Date: Mon, 17 Mar 2014 17:48:30 -0400
Message-ID: <CAA5F1T1+8wwZaiC2wyVoe+eZZo03doFDddsA15rb7qBMurCGng@mail.gmail.com>
From: Basavaraj Patil <bpatil1@gmail.com>
To: "netext@ietf.org" <netext@ietf.org>
Content-Type: multipart/alternative; boundary="089e013cba625b488b04f4d461e6"
Archived-At: http://mailarchive.ietf.org/arch/msg/netext/XTBz0j87WWOCaHMQJ0_8DN5zQUM
Cc: draft-ietf-netext-wifi-epc-eap-attributes@tools.ietf.org
Subject: [netext] Review of I-D: draft-ietf-netext-wifi-epc-eap-attributes-06
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext/>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Mar 2014 21:48:40 -0000


A few comments following my review of this I-D:

1. A lot of the 3GPP concepts are covered in this document. And there is
not enough explanation of things like the APN etc. I would recommend
referencing RFC6459 (Secs 2, 3 and 4) for a better overview of APNs, PDP
contexts etc.

2. It is not clear as to which EAP messages would include the attributes
for implementers if it was clearly spelled out in a message flow.

3. The attributes to co-relate sessions when moving between 3/4G networks
and WiFi no doubt are useful. But I am not sure if this is sufficient to
enable seamless mobility between these disparate networks. Maybe it would
be useful to clarify that these attributes are required in the context of
an overall 3/4G<->WiFi mobility design.

4. The following statement in Sec 5.3 is not clear as to its intent and the
outcome : "For Multiple PDN Connections only, a Mobile Node uses this
   to indicate whether it wishes the connectivity type to be Non-
   Seamless WLAN Offload or EPC."

5. Lastly I am wondering if it is worth trying to solve multiple problems
such as APN indication, Mobility between networks and Simultaneous
connections to different APNs in this I-D. I see the APN indication and
simulatenous connections to different APNs as something that would be
required in WiFI networks. Maybe the I-D would be simplified if it did not
tackle the seamless mobility aspect and drop the associated attributes


Basavaraj Patil