Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-00.txt

GangChen <phdgang@gmail.com> Tue, 12 August 2014 06:13 UTC

Return-Path: <phdgang@gmail.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABA451A06A1 for <pcp@ietfa.amsl.com>; Mon, 11 Aug 2014 23:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 tKUuNwiXsL_N for <pcp@ietfa.amsl.com>; Mon, 11 Aug 2014 23:13:21 -0700 (PDT)
Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 306391A059F for <pcp@ietf.org>; Mon, 11 Aug 2014 23:13:20 -0700 (PDT)
Received: by mail-qg0-f46.google.com with SMTP id z60so9146318qgd.19 for <pcp@ietf.org>; Mon, 11 Aug 2014 23:13:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iwZe9XG9HQk92fPLlWPv2uTIfP7wlGmR/G/u4Vcz3Q4=; b=Fs5sysRp8QR2lqRkQxAwOWm0Ba8aG3UVr3wvZ1rANQfFkzXtL5PsBkDdoA2EmoPf7P mjPGqzO2n1y2kn8302rmsOHrVRvjy6x45FKDoBCfz1/nV8CzjTpLvL2EHXoumnBL5X4d shPLBUVf79lRu68nYavO2JfaheF/daHxxxuURIh/BievL+OH3Ub/xa2bkCmbggDUwKZk AbnGoB/AMwdpvNPRc+d2lXJ9TYo3gBt5ApHItznbPexQoBtkY/mA0k7tFdTIMsIS/lKW BFKr+83lFdlKVW2gnKeBbCpNLUFdQVxVxfQfAjnGcCmncCRY+xqFR9sd5HbRHwK/J65u 05xA==
MIME-Version: 1.0
X-Received: by 10.140.103.180 with SMTP id y49mr3289611qge.8.1407823999296; Mon, 11 Aug 2014 23:13:19 -0700 (PDT)
Received: by 10.224.46.10 with HTTP; Mon, 11 Aug 2014 23:13:19 -0700 (PDT)
In-Reply-To: <913383AAA69FF945B8F946018B75898A28303333@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A28303333@xmb-rcd-x10.cisco.com>
Date: Tue, 12 Aug 2014 14:13:19 +0800
Message-ID: <CAM+vMER8S8aa1hecGxnj7JA3EwYSFVgMR2uP1FcDE_oFLAFxQg@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/pcp/rxfh5U_BDUAnu_Fgb_QchESbcuY
Cc: "pcp@ietf.org" <pcp@ietf.org>
Subject: Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-authentication-sim-00.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp/>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Aug 2014 06:13:22 -0000

Hi Tiru,
2014-08-08 19:00 GMT+08:00, Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>:
>> -----Original Message-----
>> From: GangChen [mailto:phdgang@gmail.com]
>> Sent: Friday, August 08, 2014 12:32 PM
>> To: Tirumaleswar Reddy (tireddy)
>> Cc: pcp@ietf.org
>> Subject: Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-
>> authentication-sim-00.txt
>>
>> 2014-08-01 1:32 GMT+08:00, Tirumaleswar Reddy (tireddy)
>> <tireddy@cisco.com>:
>> >> -----Original Message-----
>> >> From: GangChen [mailto:phdgang@gmail.com]
>> >> Sent: Wednesday, July 23, 2014 5:17 PM
>> >> To: Tirumaleswar Reddy (tireddy)
>> >> Cc: pcp@ietf.org
>> >> Subject: Re: [pcp] Fwd: New Version Notification for draft-chen-pcp-
>> >> authentication-sim-00.txt
>> >>
>> >> 2014-07-21 22:17 GMT+08:00, Tirumaleswar Reddy (tireddy)
>> >> <tireddy@cisco.com>:
>> >> >> -----Original Message-----
>> >> >> From: GangChen [mailto:phdgang@gmail.com]
>> >> >> Sent: Friday, July 04, 2014 3:41 PM
>> >> >> To: pcp@ietf.org
>> >> >> Subject: [pcp] Fwd: New Version Notification for
>> >> >> draft-chen-pcp-authentication-
>> >> >> sim-00.txt
>> >> >>
>> >> >> WG,
>> >> >>
>> >> >> I have submitted a draft to describe the consideration of PCP
>> >> >> authentication with (U)SIM support. The process is detailed in EAP
>> >> >> and GBA framework.
>> >> >
>> >> > Interesting draft. This solves the problem that for PCP
>> >> > authentication
>> >> > to work in Mobile networks, PCP client does not have use username
>> >> > and
>> >> > password but only use SIM credentials (EAP-SIM).  Other operators
>> >> > like
>> >> > Deutsche-Telekom are already using SIM authentication for ISP
>> >> > offered
>> >> > services (Slide 11
>> >> > http://www.gsma.com/personaldata/wp-
>> content/uploads/2014/03/OpenID-
>> >> Con
>> >> > nect-at-Deutsche-Telekom-Torsten-Lodderstedt.pdf)
>> >>
>> >> Thank you for the comments. I would like to further highlight the
>> >> technical
>> >> advantage using GBA to PCP. The thought is to leverage the deployed
>> >> GBA
>> >> infrastructure. AFAIK, GBA is indispensable to the mobile operators,
>> >> who
>> >> like to
>> >> offer voice service in the LTE age. It's low-cost and lightweight
>> >> implementation
>> >> to the PCP server.(only one simply message extension makes it work, as
>> >> draft
>> >> proposed at Section 3).
>> >
>> > The other technique mentioned in the draft is using HTTP authentication
>> and
>> > not EAP.
>> >
>> > 1. what is the need for this mechanism when EAP-SIM can be used ?
>>
>> EAP requires layer 2 support. However, if a user directly use 3GPP
>> radio link, it can't support the EAP framework.
>
> I don't see a problem. EAP-SIM will be exchanged over PCP i.e. EAP messages
> will be sent in the EAP Payload option defined in PCP authentication draft.

The issue is EAP is out of 3GPP-access security architecture. Please
refer to 33.401 which describes the security framework of 3GPP access,
e.g. 3G, 4G.

EAP is normally used at non-3GPP access, you could refer to 33.402.
It's applied to WLAN access.

BRs

Gang
> -Tiru
>
>>
>> Gang
>>
>>
>> > 2. It deviates from REQ-6 of fate sharing
>> > http://tools.ietf.org/html/draft-reddy-pcp-auth-req-04 that was
>> > discussed
>> in
>> > the WG sometime back.
>> >
>> > -Tiru
>> >
>> >>
>> >> BRs
>> >>
>> >> Gang
>> >>
>> >>
>> >> >
>> >> > -Tiru
>> >> >
>> >> >> Thank you for the comments in advance.
>> >> >>
>> >> >> Best Regards
>> >> >>
>> >> >> Gang
>> >> >>
>> >> >> ---------- Forwarded message ----------
>> >> >> From: internet-drafts@ietf.org
>> >> >> Date: Fri, 04 Jul 2014 03:03:05 -0700
>> >> >> Subject: New Version Notification for
>> >> >> draft-chen-pcp-authentication-sim-00.txt
>> >> >> To: Gang Chen <phdgang@gmail.com>
>> >> >>
>> >> >>
>> >> >> A new version of I-D, draft-chen-pcp-authentication-sim-00.txt
>> >> >> has been successfully submitted by Gang Chen and posted to the IETF
>> >> >> repository.
>> >> >>
>> >> >> Name:		draft-chen-pcp-authentication-sim
>> >> >> Revision:	00
>> >> >> Title:		(U)SIM based PCP Authentication
>> >> >> Document date:	2014-07-03
>> >> >> Group:		Individual Submission
>> >> >> Pages:		8
>> >> >> URL:
>> >> >> http://www.ietf.org/internet-drafts/draft-chen-pcp-authentication-sim
>> >> >> -00.txt
>> >> >> Status:
>> >> >> https://datatracker.ietf.org/doc/draft-chen-pcp-authentication-sim/
>> >> >> Htmlized:
>> >> >> http://tools.ietf.org/html/draft-chen-pcp-authentication-sim-00
>> >> >>
>> >> >>
>> >> >> Abstract:
>> >> >>    With (U)SIM support, PCP authentication could leverage the
>> >> >>    credentials stored in (U)SIM.  The document details PCP
>> >> >>    authentication considerations based on (U)SIM support.  The
>> >> >>    authentication procedures in EAP and GBA framework have been
>> >> >>    specifically elaborated.  In order to complete the process, new
>> >> >> code
>> >> >>    and option are also proposed.
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> Please note that it may take a couple of minutes from the time of
>> >> >> submission until the htmlized version and diff are available at
>> >> >> tools.ietf.org.
>> >> >>
>> >> >> The IETF Secretariat
>> >> >>
>> >> >
>> >> >
>> >
>