Re: [pcp] draft-chen-pcp-mobile-deployment-04

"Cao,Zhen" <zehn.cao@gmail.com> Mon, 19 August 2013 08:00 UTC

Return-Path: <zehn.cao@gmail.com>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96DF11E820C for <pcp@ietfa.amsl.com>; Mon, 19 Aug 2013 01:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHy7P+aSFvBl for <pcp@ietfa.amsl.com>; Mon, 19 Aug 2013 01:00:28 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBE411E8211 for <pcp@ietf.org>; Mon, 19 Aug 2013 01:00:27 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id x12so3215947wgg.0 for <pcp@ietf.org>; Mon, 19 Aug 2013 01:00:26 -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=Vy6cyFkj1+LI7wN0eVMYoKKs2sdwan9q5S8o5h637BE=; b=RJkO/hxaYH5pe5gm9tZqBPKUT/mHFX5dUidGImh6ZaBT5rCwCwUzy5MUmtONWAqrLi Ped9v+B4pz3Bcm7xFZQQhEJDj5UrNj+TZ1tf4r5Arf1z80er0pUb5NYecyKDeLAHr577 8kb45PEmtK1G2ifx3QpOZ/vKFjVt6QAOJfKXX1Apii0yFo6YCXZTUD6wZxawmHcNuHWn yjm1caZAh10qRLoU2wG61xTWATc8WWUSWhBVoyAXw9n5upoV5+/KPMKTGmauscgIA72k pWJ+jrQvjnvbTDdiib6ltTUd4BdTaMtnOfbNzQQUuYjyo3uxRxUeOS7GDKCcIB+gvfOK A/2A==
MIME-Version: 1.0
X-Received: by 10.180.100.225 with SMTP id fb1mr7180877wib.22.1376899226588; Mon, 19 Aug 2013 01:00:26 -0700 (PDT)
Received: by 10.216.90.201 with HTTP; Mon, 19 Aug 2013 01:00:26 -0700 (PDT)
In-Reply-To: <241A5C64-7861-4501-A04E-DF3D99203E18@yegin.org>
References: <2E25F372-58FF-482F-9210-5526953A08D0@yegin.org> <913383AAA69FF945B8F946018B75898A1902003F@xmb-rcd-x10.cisco.com> <241A5C64-7861-4501-A04E-DF3D99203E18@yegin.org>
Date: Mon, 19 Aug 2013 16:00:26 +0800
Message-ID: <CAProHAQpi9Y8B_kgRj8NqFW6gxUP7Ho_cKRLCbyo=xx1Vm6hUw@mail.gmail.com>
From: "Cao,Zhen" <zehn.cao@gmail.com>
To: Alper Yegin <alper.yegin@yegin.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "pcp@ietf.org" <pcp@ietf.org>, Tirumaleswar Reddy <tireddy@cisco.com>
Subject: Re: [pcp] draft-chen-pcp-mobile-deployment-04
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 19 Aug 2013 08:00:29 -0000

>> Can you provide more details why in 3GPP network PCP auth is not required ?
>>
>
> Both the PCP client and the PCP server are inside the 3GPP network which is secured at L2.

The PCP server may be a standalone server on the Gi-LAN, where the
3GPP layer 2 protection does not suffice?

-cz