Subject: [EAP] New Internet-Draft : EAP-Client-side Transport-00

From: [email-masked] (Florent Bersani)
Date: Wed, 16 Apr 2003 17:25:27 +0200

This is a multi-part message in MIME format.

------=_NextPart_000_0290_01C3043D.2C3EB890
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

I would like to annouce the first release of an Internet-Draft regarding
EAP-Client-side Transport :

http://www.ietf.org/internet-drafts/draft-boursetty-eap-cst-00.txt

This document aims at defining an architecture for interoperable =
client-side
transport of authentication with EAP, that is to say the seamless use of
"authentication tokens" (a mobile phone, a "smart" keychain, a PDA...) =
for
authenticating to remote services accessed from a PC. Such services =
could
include Wireless LANs, but we believe that it is a generic architecture
principle.

This architecture complements the usual setup considered in EAP by =
making it
become symmetric: the client-side is divided in two parts, the
Authentication Token and the client, which are analogous respectively to =
the
Authentication Server and the Authenticator on the server-side. =
Moreover,
this document describes a framework for the use of Authentication Tokens
with the EAP protocol.

Beno=EEt de Boursetty and myself, as authors, would very much like you =
to give
us your opinion / comments / etc. on this draft.
We are also looking forward to continuing the development of this =
architecture
in collaboration with anyone willing to join us.

Many thanks in advance & best regards,

Florent Bersani
[email-masked]

Beno=EEt de Boursetty
[email-masked]

------=_NextPart_000_0290_01C3043D.2C3EB890
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DVerdana size=3D2><FONT face=3D"Times New Roman" =
size=3D3>Hi,<BR><BR>I=20
would like to annouce the first release of an Internet-Draft=20
regarding<BR>EAP-Client-side Transport :<BR><BR></FONT><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-boursetty-eap-cst-00.tx=
t"><FONT=20
face=3D"Times New Roman"=20
size=3D3>http://www.ietf.org/internet-drafts/draft-boursetty-eap-cst-00.t=
xt</FONT></A><BR><BR><FONT=20
face=3D"Times New Roman" size=3D3>This document aims at defining an =
architecture for=20
interoperable client-side<BR>transport of authentication with EAP, that =
is to=20
say the seamless use of<BR>"authentication tokens" (a mobile phone, a =
"smart"=20
keychain, a PDA...) for<BR>authenticating to remote services accessed =
from a PC.=20
Such services could<BR>include Wireless LANs, but we believe that it is =
a=20
generic architecture<BR>principle.<BR><BR>This architecture complements =
the=20
usual setup considered in EAP by making it<BR>become symmetric: the =
client-side=20
is divided in two parts, the<BR>Authentication Token and the client, =
which are=20
analogous respectively to the<BR>Authentication Server and the =
Authenticator on=20
the server-side. Moreover,<BR>this document describes a framework for =
the use of=20
Authentication Tokens<BR>with the EAP protocol.<BR><BR>Beno=EEt de =
Boursetty and=20
myself, as authors, would very much like you to give<BR>us your opinion =
/=20
comments / etc. on this draft.<BR>We are also looking forward to =
continuing the=20
development of this architecture<BR>in collaboration with anyone willing =
to join=20
us.<BR><BR>Many thanks in advance &amp; best regards,<BR><BR>Florent=20
Bersani<BR></FONT><A =
href=3D"mailto:[email-masked]"><FONT=20
face=3D"Times New Roman"=20
size=3D3>[email-masked]</FONT></A><BR><BR><FONT=20
face=3D"Times New Roman" size=3D3>Beno=EEt de Boursetty<BR></FONT><A=20
href=3D"mailto:[email-masked]"><FONT face=3D"Times =
New Roman"=20
size=3D3>[email-masked]</FONT></A><BR></FONT></DIV>=
</BODY></HTML>

------=_NextPart_000_0290_01C3043D.2C3EB890--