Extensible Authentication Protocol (EAP) Working Group - PowerPoint PPT Presentation

About This Presentation
Title:

Extensible Authentication Protocol (EAP) Working Group

Description:

Title: RFC 2284bis Open Issues Last modified by: Bernard Aboba Created Date: 9/30/1996 6:28:10 PM Document presentation format: On-screen Show Other titles – PowerPoint PPT presentation

Number of Views:75
Avg rating:3.0/5.0
Slides: 12
Provided by: iet82
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: Extensible Authentication Protocol (EAP) Working Group


1
Extensible Authentication Protocol (EAP)Working
Group
  • http//www.drizzle.com/aboba/IETF56/EAP/
  • IETF 56
  • San Francisco, CA
  • Monday, March 17, 2003
  • 1530 - 1730

2
Agenda, Monday (1/2)
  • Preliminaries, 20 minutes
  • 1. Administrative
  • Bluesheets
  • Minute Takers
  • Agenda Bashing
  • Announcements
  • 2. Document status, chairs, 10 minutes
  • 3. IEEE 802.11 Liason Letter, Dorothy Stanley,
    10 minutes
  • 2284, 60 minutes
  • 4. RFC 2284bis, Henrik Levkowetz and Jari Arkko,
    60 minutes
  • http//www.ietf.org/internet-drafts/draft-ietf-e
    ap-rfc2284bis-01.txt

3
Agenda, Monday (2/2)
  • EAP Methods (Part 1), 10 minutes
  • 5. EAP Support in Smartcards, Pascal Urien, 10
    minutes
  • http//www.ietf.org/internet-drafts/draft-urien-
    eap-smartcard-01.txt
  • Man-in-the-Middle Attacks, 30 minutes
  • 6. Compound Binding, Jose Puthenkulam, 30
    minutes
  • http//www.ietf.org/internet-drafts/draft-puthen
    kulam-eap-binding-02.txt

4
Extensible Authentication Protocol (EAP)Working
Group
  • Thursday, March 20, 2003
  • 1530 - 1730

5
Agenda, Thursday (1/2)
  • Preliminaries, 10 minutes
  • Blue sheets
  • Minute Takers
  • Agenda bash
  • RFC 2869bis, 10 minutes
  • 7. RFC 2869bis, Bernard Aboba, 10 minutes
  • http//www.ietf.org/internet-drafts/draft-aboba-
    radius-rfc2869bis-09.txt
  • EAP Archie, 5 minutes
  • 8. EAP Archie, Jesse Walker, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-jwalke
    r-eap-archie-00.txt
  • Keying Framework, 25 minutes
  • 9. EAP Keying Framework, Bernard Aboba, 15
    minutes
  • http//www.ietf.org/internet-drafts/draft-aboba-
    pppext-key-problem-06.txt
  • 10. EAP Key Derivation for Multiple Apps, Joe
    Salowey, 10 mins
  • http//www.ietf.org/internet-drafts/draft-salowe
    y-eap-key-deriv-00.txt
  • Roadmap, 10 minutes
  • 11. EAP Roadmap, Erik Nordmark Thomas Narten,
    10 minutes

6
Agenda, Thursday (2/2)
  • EAP Methods (Part 2), 35 minutes
  • 14. EAP Protected TLV, Joe Salowey, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-salowe
    y-eap-protectedtlv-01.txt
  • 15. EAP Authorization, Joe Salowey, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-grayso
    n-eap-authorisation-01.txt
  • 16. EAP SIM, Joe Salowey, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-haveri
    nen-pppext-eap-sim-10.txt
  • 17. Tunneled MD5, Paul Funk, 5 minutes
  • http//www.funk.com/documents/draft-funk-eap-md5
    -tunneled-00.txt
  • 18. EAP AKA, Jari Arkko, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-arkko-
    pppext-eap-aka-09.txt
  • 19. EAP over CDMA2000, P. Agashe, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-pagash
    e-eapcdma2000-00.txt
  • 20. EAP GPRS, A. Salkintzis, 5 minutes
  • http//www.ietf.org/internet-drafts/draft-salki-
    pppext-eap-gprs-00.txt

7
Document Status
  • Chairs

8
Document Status (1/4)
  • WG activities
  • Significant effort has been put to completing the
    bis document after IETF 55 -- excellent!
  • Keying and binding issues getting more focus, but
    more work still needed
  • IEEE/3GPP requirements, timelines are tough
  • WG work items
  • RFC 2284bis
  • Significant input and revisions
  • Many issues discovered, but the end is in sight
    (?)
  • WG last call sometime after IETF 56, when all
    issues closed (?)

9
Document Status (2/4)
  • Reminder RFC 2284 bis background and goals
  • Background
  • Original documents were not very precise
  • EAP has had some interoperability problems
  • More interoperability problems expected in the
    future
  • Goals
  • Make the specification precise
  • Limit interoperability problems where possible
  • Backward compatibility
  • Produce the document quickly
  • Read our lips no new features

10
Document Status (3/4)
  • Individual submissions
  • State machine
  • Issues common with 2284 bis the two must be in
    sync
  • Probably more revisions needed than in RFC
    2284bis
  • RFC 2869bis
  • Important issues discovered
  • One issue remains, then done? (83, related to
    2284 74)
  • Key framework
  • Binding problem
  • EAP AKA, SIM
  • Other methods

11
Document Status (4/4)
  • How does my draft become a WG item?
  • Must have had significant review
  • All major issues resolved
Write a Comment
User Comments (0)
About PowerShow.com