1 / 6

EAP WG Methods Process

EAP WG Methods Process. IETF-60 Jari Arkko Bernard Aboba. Types of Processes & Some History. There were no IANA considerations in RFC 2284 But RFC 3748 has well-defined rules on how to specify new methods

mjobe
Télécharger la présentation

EAP WG Methods Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EAP WGMethods Process IETF-60 Jari Arkko Bernard Aboba

  2. Types of Processes & Some History • There were no IANA considerations in RFC 2284 • But RFC 3748 has well-defined rules on how to specify new methods • Note: Many of the methods currently in the process at RFC Editor, IESG, etc. have gotten their allocations prior to RFC 3748 publication • What about Standards Track methods?

  3. Case 1: Old Methods • IANA acted on First Come First Served basis • No specification required, no IETF approval needed • A lot of vendor specific, undocumented methods exist in this space • Many of them are no longer in use

  4. Case 2: Leftovers from the old times... • Some EAP methods that are currently in RFC Editor queue or IESG processing, and they have a Type number • If there is already a Type number for the method, then usual IETF rules apply: • Informational/individual submissions: no official review, but can not be used to do an “end run” • Standards track: AD sponsored or WG item • Note: in any case, other IETF rules on IANA allocations must be obeyed, e.g., TLS extensions need to be on the standards track

  5. Case 3: New methods • RFC 3748 requires an Expert Review for EAP Type number allocation • Vendor specific EAP methods can be allocated by vendors on their own

  6. Case 4: Standards Track Methods • Need to be WG items for standards track • Or AD sponsored individual submissions • EAP WG to take up the development of a standard method(s)? • There has been recent interest on this • The ADs have been positive to the idea • But we need (a) High quality contributions (maybe PSK/IKEv2/PAX?) (b) People willing to work on them (c) A WG (and world) who cares and who will use the results

More Related