Re: [Hipsec] HIP & EAP
<yoshihiro.ohba@toshiba.co.jp> Fri, 04 April 2014 01:36 UTC
Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7411A03BC for <hipsec@ietfa.amsl.com>; Thu, 3 Apr 2014 18:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level:
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=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 9mIXcnlVRhCi for <hipsec@ietfa.amsl.com>; Thu, 3 Apr 2014 18:36:51 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id DD2A01A003B for <hipsec@ietf.org>; Thu, 3 Apr 2014 18:36:50 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id s341afRh012544; Fri, 4 Apr 2014 10:36:41 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp id s341afDv002783; Fri, 4 Apr 2014 10:36:41 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id LAA02782; Fri, 4 Apr 2014 10:36:41 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id s341aeFn008073; Fri, 4 Apr 2014 10:36:40 +0900 (JST)
Received: from TGXML208.toshiba.local by toshiba.co.jp id s341aeEO010986; Fri, 4 Apr 2014 10:36:40 +0900 (JST)
Received: from TGXML210.toshiba.local ([169.254.4.147]) by TGXML208.toshiba.local ([133.199.70.17]) with mapi id 14.03.0174.001; Fri, 4 Apr 2014 10:36:40 +0900
From: yoshihiro.ohba@toshiba.co.jp
To: rgm@htt-consult.com, hipsec@ietf.org
Thread-Topic: [Hipsec] HIP & EAP
Thread-Index: AQHPT6RkVR3x5Lr+6keVn+cmx489rJsArGEA
Date: Fri, 04 Apr 2014 01:36:40 +0000
Message-ID: <674F70E5F2BE564CB06B6901FD3DD78B2721EE7F@TGXML210.toshiba.local>
References: <533E094B.3010706@htt-consult.com>
In-Reply-To: <533E094B.3010706@htt-consult.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
x-originating-ip: [133.196.20.215]
msscp.transfermailtomossagent: 103
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/1qrw21q_rXvMYbnSjweXE3Ze6F4
Subject: Re: [Hipsec] HIP & EAP
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 01:36:55 -0000
I am interested in writing up such an I-D if it is not done yet. Yoshihiro Ohba -----Original Message----- From: Hipsec [mailto:hipsec-bounces@ietf.org] On Behalf Of Robert Moskowitz Sent: Friday, April 4, 2014 10:22 AM To: HIP Subject: [Hipsec] HIP & EAP Long ago Samu wrote an ID for EAP within HIP. I need HIP within EAP, as an EAP method. Kind of like RFC 5106. Why? To work over 802.1X and within PANA. Details available in a bit. Has anyone written such an ID? _______________________________________________ Hipsec mailing list Hipsec@ietf.org https://www.ietf.org/mailman/listinfo/hipsec
- Re: [Hipsec] HIP & EAP Robert Moskowitz
- [Hipsec] HIP & EAP Robert Moskowitz
- Re: [Hipsec] HIP & EAP yoshihiro.ohba