[pcp] An example of PANA implementation guides

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Fri, 09 November 2012 15:13 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
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 1F67621F870F for <pcp@ietfa.amsl.com>; Fri, 9 Nov 2012 07:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.422
X-Spam-Level:
X-Spam-Status: No, score=-5.422 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 rJG7IWKFpiAI for <pcp@ietfa.amsl.com>; Fri, 9 Nov 2012 07:13:11 -0800 (PST)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by ietfa.amsl.com (Postfix) with ESMTP id DB20A21F852D for <pcp@ietf.org>; Fri, 9 Nov 2012 07:13:10 -0800 (PST)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id qA9FDAtH011737 for <pcp@ietf.org>; Sat, 10 Nov 2012 00:13:10 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id qA9FD9d5007139 for pcp@ietf.org; Sat, 10 Nov 2012 00:13:09 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id AAA07138; Sat, 10 Nov 2012 00:13:09 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id qA9FD998018920 for <pcp@ietf.org>; Sat, 10 Nov 2012 00:13:09 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id qA9FD9px024961; Sat, 10 Nov 2012 00:13:09 +0900 (JST)
Received: from [133.199.16.4] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPSA id <0MD800GIH7LL73D0@mail.po.toshiba.co.jp> for pcp@ietf.org; Sat, 10 Nov 2012 00:13:09 +0900 (JST)
Date: Sat, 10 Nov 2012 00:13:01 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
To: "pcp@ietf.org" <pcp@ietf.org>
Message-id: <509D1D7D.6040602@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-2022-JP"
Content-transfer-encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
Subject: [pcp] An example of PANA implementation guides
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: Fri, 09 Nov 2012 15:13:13 -0000

Section 6.4.1 of http://tools.ietf.org/html/draft-ietf-lwig-guidance-02
describes light-weight implementation guidelines for PANA.

The draft says that (i) PANA liveness test does not need to be supported
and (ii) PAA-initiated re-authentication does not need to be supported.

My point is that we can create similar guidelines for PCP use of PANA
once the PCP authentication issues are resolved and PANA is chosen as
the solution for PCP authentication.

Regards,
Yoshihiro Ohba