[Pana] PANA relay implementation status

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Tue, 15 February 2011 16:07 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: pana@core3.amsl.com
Delivered-To: pana@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 288A23A6CD8 for <pana@core3.amsl.com>; Tue, 15 Feb 2011 08:07:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.789
X-Spam-Level:
X-Spam-Status: No, score=-2.789 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zWF+nUF+o9Qj for <pana@core3.amsl.com>; Tue, 15 Feb 2011 08:06:59 -0800 (PST)
Received: from imx2.toshiba.co.jp (inet-tsb5.toshiba.co.jp [202.33.96.24]) by core3.amsl.com (Postfix) with ESMTP id 628413A6CB9 for <pana@ietf.org>; Tue, 15 Feb 2011 08:06:58 -0800 (PST)
Received: from arc1.toshiba.co.jp ([133.199.194.235]) by imx2.toshiba.co.jp with ESMTP id p1FG7Iwx026483; Wed, 16 Feb 2011 01:07:18 +0900 (JST)
Received: (from root@localhost) by arc1.toshiba.co.jp id p1FG7IMI021188; Wed, 16 Feb 2011 01:07:18 +0900 (JST)
Received: from unknown [133.199.192.144] by arc1.toshiba.co.jp with ESMTP id BAA21187; Wed, 16 Feb 2011 01:07:18 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp2.toshiba.co.jp with ESMTP id p1FG7H1E002742; Wed, 16 Feb 2011 01:07:17 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id p1FG7HU8027231; Wed, 16 Feb 2011 01:07:17 +0900 (JST)
Received: from [133.199.75.182] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0LGO007KQ243VO10@mail.po.toshiba.co.jp>; Wed, 16 Feb 2011 01:07:17 +0900 (JST)
Date: Wed, 16 Feb 2011 01:07:03 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
To: pana@ietf.org
Message-id: <4D5AA4A7.3050104@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; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
Cc: Ralph Droms <rdroms@cisco.com>
Subject: [Pana] PANA relay implementation status
X-BeenThere: pana@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Protocol for carrying Authentication for Network Access <pana.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pana>
List-Post: <mailto:pana@ietf.org>
List-Help: <mailto:pana-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pana>, <mailto:pana-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 16:07:00 -0000

I would like to note that PANA relay (and RFC 5191 of course)  is
being implemented by a couple of ZigBee vendors and showing successful
interoperability in ZigBee IP mesh networking environment.

I guess this is something people on this ML wanted to know.

Regards,
Yoshihiro Ohba