[pcp] issue#62: Client-driven or server-driven auth retransmissions

Alper Yegin <alper.yegin@yegin.org> Mon, 05 November 2012 11:35 UTC

Return-Path: <alper.yegin@yegin.org>
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 57B0E21F854A for <pcp@ietfa.amsl.com>; Mon, 5 Nov 2012 03:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level:
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5AEG+Tg+0vW for <pcp@ietfa.amsl.com>; Mon, 5 Nov 2012 03:35:17 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id BD1F421F8549 for <pcp@ietf.org>; Mon, 5 Nov 2012 03:35:17 -0800 (PST)
Received: from [192.168.2.4] (88.247.135.202.static.ttnet.com.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LhwPy-1Szpwn1jjW-00mPRk; Mon, 05 Nov 2012 06:35:17 -0500
From: Alper Yegin <alper.yegin@yegin.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 05 Nov 2012 13:35:01 +0200
Message-Id: <C662B229-05FA-4CEC-BBA2-4B55F2424D2B@yegin.org>
To: pcp@ietf.org
Mime-Version: 1.0 (Apple Message framework v1278)
X-Mailer: Apple Mail (2.1278)
X-Provags-ID: V02:K0:++qHYwHp7ZTuU8YNUJbs8ScF9TlndSqW8EuUdmrgCUT rC3rKfC67HM9INUd/QoHB8VeIXgZr0md7aLN9DwrzQrmTXq/Nq Iclr8u8979zZqfKNXuM5uHS9IqKh29yuQUBoB/lQHw5FNZDUkg 34X/wcNdSMub1ckjjyT0c7J27JfvnC0UmEaaUdbtcTjbZ50DZi Aam+jtzY9eWH81YY3EgHDDmDDf43A6+q0y29rk4SxFLVugVwRF fp9iMh9vbwqVdgMvXIefp40OIDKpX7wdVE2PQQwowvdMSkRBy4 FHWe5izj1SsaGiFpyH4fqN5hyhWJFhyWaXjOFJUNt1IHiyIsgU tz8vdmHZz6nJ20FF+ZH8ZNux1Y+BpgIOPKoK1sv3F7NfBabr51 VunZxsSA1o2bQ==
Subject: [pcp] issue#62: Client-driven or server-driven auth retransmissions
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, 05 Nov 2012 11:35:18 -0000

EAP is a server-driven request/response type protocol.
Defining an EAP lower-layer that's client driven is not trivial, maybe not even possible (to-be seen). 
Sam initiated a discussion on the ABFAB WG mailing list on this matter, and there seems to be issues there (a single packet stalling the protocol flow, see http://www.ietf.org/mail-archive/web/abfab/current/msg01746.html)

Furthermore, as more details of client-driven solution discussed, it became apparent that server still needs to maintain state even when the client is driving the rexmits. So, there are no savings there. In fact, if the savings are targeted at the "PCP implementation", then offloading the authentication to PANA is much more attractive.