From henry.haverinen@nokia.com  Thu Jun  6 10:48:51 2002
From: henry.haverinen@nokia.com (henry.haverinen@nokia.com)
Date: Thu, 6 Jun 2002 12:48:51 +0300
Subject: [eap] EAP SIM version 4
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B015D0F31@trebe003.NOE.Nokia.com>

Hi all,

I just submitted version 4 of the EAP SIM draft to the IETF
directories. A preview is available at the following URL:
http://www.cs.tut.fi/~haverinh/draft-haverinen-pppext-eap-sim-04.txt

Changes to version 03:
- all comments I have received since February are addressed.
  Most significantly the draft now uses 128-bit MAC codes (AT_MAC and
  AT_MAC_SRES) and integrity keys (K_int), and there is a new PRF based =
on=20
  NIST FIPS Publication 186
- zero configuration support

If you have an implementation, we'd be very happy to test =
interoperability
with the Nokia implementation. Please contact me so we can arrange
the testing. To facilitate interoperable implementations, I'm going to =
avoid
making incompatible updates to the version 04.

Regards,
Henry

PS. Jari and I are also working on the version 04 of the EAP AKA draft,
which will be shortly available too.


From gdweber@cisco.com  Wed Jun 12 18:51:49 2002
From: gdweber@cisco.com (Greg Weber)
Date: Wed, 12 Jun 2002 13:51:49 -0400 (EDT)
Subject: [eap] EAP BOF/WG at Yokohama?
Message-ID: <200206121751.NAA06183@cisco.com>


Will there be an EAP meeting in Yokohama?  
I don't see it mentioned in the draft agenda below...

Greg


Forwarded message:
> To: IETF-Announce: ;
> From: agenda@ietf.org
> Subject: 54th IETF Draft Agenda (As of June 7, 2002)
> Date: Fri, 07 Jun 2002 16:07:59 -0400
> 
> Please find below the Draft Agenda of the 54 IETF Meeting
> in Yokohama, Japan.
> 
> Also this information will be available on the IETF web site
> at http://www.ietf.org/meetings/agenda_54.txt TOMORROW.
> Check http://www.ietf.org/meetings/wg_agenda_54.html
> for WG and BOF Agenda.
> 
> Please be aware that it's a Draft Agenda and can be changed
> before June 21 when Working Group and BOF scheduling closes. 
> 
> +++
> 
> Draft Agenda of the Fifty-fourth IETF
> July 14-19, 2002
> 
> SUNDAY, July 14, 2002
> 1000-1700 IEPG Meeting - 
> 1200-1900 Registration -
> 1300-1330 Newcomer's Orientation -
> 1330-1400 IETF Standards Process Orientation -
> 1500-1700 Security Tutorial - 
> 1700-1900 Welcome Reception - 
> 
> MONDAY, July 15, 2002
> 0800-1930 IETF Registration -  
> 0800-0900 Continental Breakfast  
> 0900-1130 Morning Sessions 
> APP     apparea   Applications Open Area Meeting 
> INT     ipoib     IP over InfiniBand WG
> OPS     bmwg      Benchmarking Methodology WG
> TSV     nsis      Next Steps in Signaling WG
> TSV     pwe3      Pseudo Wire Emulation Edge to Edge WG
>                 
> 1130-1300 Break 
> 1300-1500 Afternoon Sessions I
> APP     trade     Internet Open Trading Protocol WG
> SEC     smime     S/MIME Mail Security WG
> SUB     ccamp     Common Control and Measurement Plane WG
> TSV     enum      Telephone Number Mapping WG
> TSV     ippm      IP Performance Metrics WG
> 
> 1500-1530 Break (Refreshments provided) - 
> 1530-1730 Afternoon Sessions II
> APP     jabber    Jabber Protocol BOF
> INT     pana      Protocol for carrying Authentication for Network Access WG
> OPS     ipfix     IP Flow Information Export WG
> RTG     msdp      Multicast Source Discovery Protocol WG
> TSV     rserpool  Reliable Server Pooling WG
> TSV     sip       Session Initiation Protocol WG
>         
> 1730-1930 Break
> 1930-2200 Evening Sessions
> APP     fax&vpim  Internet Fax WG & Voice Profile for Internet Mail WG
> INT     mobileip  IP Routing for Wireless/Mobile Hosts WG
> OPS     rmonmib   Remote Network Monitoring WG
> RTG     rtgarea   Routing Area Meeting
> TSV     ips       IP Storage WG
> TSV     midcom    Middlebox Communication WG
> 
> TUESDAY, July 16, 2002
> 0800-1700 IETF Registration - 
> 0800-0900 Continental Breakfast - 
> 0900-1130 Morning Sessions
> APP     webdav    WWW Distributed Authoring and Versioning WG
> INT     dhc       Dynamic Host Configuration WG
> OPS     psamp     Packet Sampling BOF
> RTG     pim       Protocol Independent Multicast WG
> SUB     ppvpn     Provider Provisioned Virtual Private Networks WG
> TSV     sipping   Session Initiation Proposal Investigation WG 
> 
> 1130-1300 Break
> 1300-1400 Afternoon Sessions I
> OPS     ptomaine  Prefix Taxonomy Ongoing Measurement & Inter Network Experiment WG
> TSV     ips       IP Storage WG
> TSV     spirits   Service in the PSTN/IN Requesting InTernet Service WG
>         
> 1415-1515 Afternoon Sessions II
> INT     l2pext    Layer Two Tunneling Protocol Extensions WG
> OPS     entmib    Entity MIB WG
> SEC     krb-wg    Kerberos WG
> SUB     ipo       IP over Optical WG
> TSV     rmt       Reliable Multicast Transport WG
>         
> 1515-1545 Break (Refreshments provided) - 
> 1545-1645 Afternoon Sessions III
> INT     dnsext    DNS Extensions WG
> TSV     iptel     IP Telephony WG
> TSV     rmt       Reliable Multicast Transport WG
> 
> 1700-1800 Afternoon Sessions IV
> APP     opes      Open Pluggable Edge Services WG
> INT     send      SEcuring Neighbor Discovery BOF
> RTG     vrrp      Virtual Router Redundancy Protocol WG
> OPS     bridge    Bridge MIB WG
> TSV     tsvwg     Transport Area Working Group WG
> 
> WEDNESDAY, July 17, 2002
> 0800-1700 IETF Registration - 
> 0800-0900 Continental Breakfast - 
> 0900-1130 Morning Sessions
> APP     simple    SIP for Instant Messaging and Presence Leveraging Extensions WG
> OPS     ngtrans   Next Generation Transition WG
> RTG     manet     Mobile Ad-hoc Networks WG
> TSV     ieprep    Internet Emergency Preparedness WG
> TSV     rohc      Robust Header Compression WG
> 
> 1130-1300 Break
> 1300-1500 Afternoon Sessions I  
> INT     magma     Multicast & Anycast Group Membership WG
> OPS     sming     Next Generation Structure of Management Information WG
> RTG     isis      IS-IS for IP Internets WG
> SEC     pkix      Public-Key Infrastructure (X.509) WG
> TSV     nfsv4     Network File System Version 4 WG
> TSV     sip       Session Initiation Protocol WG 
> 
> 1500-1530 Break (Refreshments provided) - 
> 1530-1730 Afternoon Sessions II
> APP     ldapbis   LDAP (v3) Revision WG
> OPS     opsarea   Operations & Management Open Area
> RTG     idr       Inter-Domain Routing WG
> SEC     ipsec     IP Security Protocol WG
> TSV     avt       Audio/Video Transport WG
> TSV     cats      Control of ASR and TTS Servers BOF 
> 
> 1730-1930 Break
> 1930-2200 IESG Open Plenary - 
>  
> 2230 Late Night Session - PGP Key Signing 
> 
> THURSDAY, July 18, 2002
> 0800-1700 IETF Registration - 
> 0800-0900 Continental Breakfast - 
> 0900-1130 Morning Sessions      
> INT     ipv6      IP Version 6 Working Group WG
> SUB     mpls      Multiprotocol Label Switching WG
> TSV     mmusic    Multiparty Multimedia Session Control WG
>         
> 1130-1300 Break
> 1300-1500 Afternoon Sessions I
> TSV     sipping   Session Initiation Proposal Investigation WG 
>         
> 1500-1530 Break (Refreshments provided) - 
> 1530-1730 Afternoon Sessions II
> APP     impp      Instant Messaging and Presence Protocol WG
> RTG     forces    Forwarding and Control Element Separation WG
> OPS     mboned    MBONE Deployment WG
> SEC     inch      Extended Incident Handling BOF
> TSV     avt       Audio/Video Transport WG
> TSV     ieprep    Internet Emergency Preparedness WG
> 
> 1730-1930 Break
> 1930-2200 Open IAB Plenary - 
> 
> FRIDAY, July 19, 2002
> 0800-1000 IETF Registration - 
> 0800-0900 Continental Breakfast - 
> 0900-1130 Morning Sessions
> GEN     ipr       Intellectual Property Rights BOF
> 
> 
> 
> 
> 
> 
> 


From jhw@wetware.com  Wed Jun 12 20:55:34 2002
From: jhw@wetware.com (james woodyatt)
Date: Wed, 12 Jun 2002 12:55:34 -0700
Subject: [eap] EAP BOF/WG at Yokohama?
In-Reply-To: <200206121751.NAA06183@cisco.com>
Message-ID: <5BF7B268-7E3E-11D6-BD2F-000502DB38F5@wetware.com>

On Wednesday, June 12, 2002, at 10:51 AM, Greg Weber wrote:
>
> Will there be an EAP meeting in Yokohama?
> I don't see it mentioned in the draft agenda below...

And if so-- will it be a WG or a BOF?

For those of us who have no plans yet to attend IETF 54, it might be 
helpful to know whether an EAP meeting is likely to happen.

I'm pretty sure I can poke my employers into expensing my trip to 
Yokohama if there's going to be an EAP meeting.  Otherwise not.  I'm 
running out of time to schedule this.


--
j h woodyatt <jhw@wetware.com>


From aboba@internaut.com  Fri Jun 14 00:14:10 2002
From: aboba@internaut.com (Bernard Aboba)
Date: Thu, 13 Jun 2002 16:14:10 -0700 (PDT)
Subject: [eap] Re: EAP BOF at Yokahama?
Message-ID: <Pine.LNX.4.44.0206131612430.30566-100000@internaut.com>

>Will there be an EAP meeting in Yokohama? If so, will it be a BOF? A WG?

At the moment, EAP work (including RFC 2284bis) is still chartered within
the PPPEXT WG. Unfortunately, Karl Fox has indicated that he will not be
going to Yokohama and so PPPEXT WG will not meet.

I am told that the IESG will take up the subject of formation of an EAP WG
at their next teleconference call. If you have any opinions on the
formation of an EAP WG and the appropriate charter for such a WG (strawman
is enclosed below), I'd suggest sending mail to the Internet Area ADs.

With respect to an EAP BOF at IETF 54 in Yokahama, there is currently none
scheduled. While IETF rules state that 3 BOFs may not be held on a single
topic, and EAP has been the subject of two BOFs (one at IETF 43 in
Orlando, and another at IETF 53), it is possible that the rules could be
bent, given the separation between the BOFs.


Strawman EAP WG Charter
-------------------------------------------------------------------
 EAP Working Group (EAP)

 Chair(s):
    This space for rent

 Area Director(s):
    Thomas Narten <narten@us.ibm.com
    Erik Nordmark <nordmark@eng.sun.com

 Security Advisors:
    Bill Arbaugh <waa@cs.umd.edu

 Mailing Lists:

 General discussion: eap@frascone.com
 To subscribe: send a message with "subscribe" in the subject to
               eap-request@frascone.com
 Archive: http://mail.frascone.com/pipermail/eap/

 The EAP working group will restrict itself to the following
 work items in order to fully document and improve the
 interoperability of the existing EAP protocol:

 1.  IANA considerations for EAP.
 2.  Type space extension to support an expanded Type space.
 3.  EAP usage model.
 4.  Threat model and security requirements.
 5.  EAP state machine.
 6.  Documentation of interaction between EAP and other layers.
 7.  Resolution of interoperability issues.
 8.  EAP keying problem description and requirements.

 Items 1-7 are intended to be covered within RFC 2248bis, the
 revision to the EAP specification. Item 8 will be covered within
 a separate document

 The EAP WG is not currently chartered to review or standardize EAP
 methods. However, when these work items are completed, the WG may be
 rechartered, or a new WG may be formed to evaluate proposed methods.

 Goals and Milestones

 Dec  02   RFC 2284bis published as a Proposed Standard RFC.
 Jun  03   EAP keying problem document published as an Informational RFC.

 Internet-Drafts

 RFC 2284bis
 http://www.ietf.org/internet-drafts/draft-ietf-pppext-rfc2284bis-04.txt

 Request for Comments

 RFC 2284, http://www.ietf.org/rfc/rfc2284.txt





From Jacques.Caron@IPsector.com  Tue Jun 25 19:31:18 2002
From: Jacques.Caron@IPsector.com (Jacques Caron)
Date: Tue, 25 Jun 2002 20:31:18 +0200
Subject: [eap] OT: Open (public WLAN) roaming mailing list
Message-ID: <5.1.0.14.0.20020625203106.03e44a88@wheresmymailserver.com>

Hi,

Sorry for the interruption...

In an effort to create a working group dedicated to open roaming (for 
public WLANs mainly) within the IETF, I have created a mailing list 
dedicated to the topic:
http://lists.ipsector.com/listinfo/openroaming

There are also a few internet-drafts on the subject that probably need 
quite a bit of discussion, especially:
http://www.ietf.org/internet-drafts/draft-caron-public-wlan-roaming-issues-00.txt
which describes most of the issues, requirements, and possible or needed 
solutions.

Since EAP (within 802.1X) will probably be used extensively in this 
context, I thought some of you might be interested in joining and commenting!

... and now back to our regular program...

Thanks,

Jacques. 


From henry.haverinen@nokia.com  Fri Jun 28 13:35:49 2002
From: henry.haverinen@nokia.com (henry.haverinen@nokia.com)
Date: Fri, 28 Jun 2002 15:35:49 +0300
Subject: [eap] New EAP AKA draft
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B015D0FC0@trebe003.NOE.Nokia.com>

Hi there,

Jari and I have submitted a new version of the EAP AKA
draft to the I-D directories. It is also available at:

http://www.cs.tut.fi/~haverinh/draft-arkko-pppext-eap-aka-04.txt

The changes are visible in the following pdf file:
http://www.cs.tut.fi/~haverinh/eap-aka-04-changes.pdf

Changes to version 03:
- all comments since February 2002 addressed. Most significantly,
  there are 128-bit MAC codes and a new PRF based on NIST FIBS 186-2
- zero configuration
- independence of EAP-Response/Identity
- improved IANA considerations
- lot of editorial changes

Best regards,
Henry

From henry.haverinen@nokia.com  Fri Jun 28 13:39:34 2002
From: henry.haverinen@nokia.com (henry.haverinen@nokia.com)
Date: Fri, 28 Jun 2002 15:39:34 +0300
Subject: [eap] EAP SIM version 5
Message-ID: <DED1F2C6CE07FA498D7AD0CCAC03401B015D0FC1@trebe003.NOE.Nokia.com>

Hi folks,

EAP SIM version 5 should be shortly available in
the I-D directories. It is also available at

http://www.cs.tut.fi/~haverinh/draft-haverinen-pppext-eap-sim-05.txt

The changes are visible in the pdf file available at

http://www.cs.tut.fi/~haverinh/eap-sim-05-changes.pdf

Changes to version 04:
- updated reference to NIST FIPS 182-2
- independence of EAP-Response/Identity
- improved IANA considerations
- editorial changes

> Changes to version 03:
> - all comments I have received since February are addressed.
>   Most significantly the draft now uses 128-bit MAC codes (AT_MAC and
>   AT_MAC_SRES) and integrity keys (K_int), and there is a new=20
> PRF based on=20
>   NIST FIPS Publication 186
> - zero configuration support

Best regards,
Henry

