Internet Architecture Board

RFC2850

June 2004

June 2004 IETF/IEEE 802 Liaison Report

Status of IEEE 802 Liaison Requests

  1. Request for priority publication of RFC 2284bis: Document (assigned RFC 3748) in Author 48 hours.
  2. Request for publication of draft-walker-ieee802-req-01.txt: Document sponsored by Margaret Wasserman, placed on June 10th IESG telechat, for publication as an Informational RFC. (Letter from Stuart Kerry, Chair of 802.11 enclosed below).
  3. Request that EAP method documents requesting publication and claiming conformance to IEEE 802 WLAN Requirements undergo IETF Last Call: Handling of non-WG EAP method documents requesting publication as AD-sponsored individual submissions under consideration by M. Wasserman.
  4. EAP State Machine document (related to IEEE 802.1X-REV, now in Sponsor Ballot): approved by IESG for publication as an Informational RFC.
  5. Request that work on EAP Network Discovery be discussed in IEEE 802.11 WIEN Study Group prior to chartering of solution work items: EAP WG charter to include work on network selection problem statement only.
  6. Request for notice of potential IETF New Work: IEEE 802 representatives subscribed to New Work list (Thanks to Bert Wijnen, Tony Jeffree, Paul Congdon)
  7. Request for publication of dependencies of IEEE 802.1X-REV and IEEE 802.11i: All dependencies satisfied, IEEE 802.11i completes Sponsor Ballot, IEEE 802.1X-REV in Sponsor Ballot.

From Dan Romascanu <dromasca@avaya.com>, Liaison to IEEE 802.1:

    • IEEE 802.1 held an interim meeting May 17-20 in Barcelona, Spain. IEEE 802.1AB is currently in recirculation ballot, and the MIB sections have been commented on by Dave Harrington, Les Bell, and myself — although no formal ‘MIB Doctor’ review was performed.

A re-charter proposal of the IETF Bridge MIB WG was distributed for comments. Dave Harrington proposed to take the 802.1X MIB and the SMIv2 update for RFC 1493 out of the charter, leaving the scope of work to a minimum of two items covering MIB support for extensions to the Bridge standards defined in 802.1t, 802.1u, 802.1v and 802.1w. AFAIK, there was no resolution to this by now.

Status of IETF Liaison Requests

——————————-

    1. Request for early notice of potential PARs: B. Aboba subscribed to new PAR list, forwarded PAR info received so far to IESG & IAB. Need to followup on posting to “New Work” list.

Request for Secretariat notification of IEEE 802 meeting schedule: Forwarded by Paul Congdon, passed on to IETF Secretariat

Request for a letter granting access to IEEE 802 archives to IETF Chairs & WGs with need to know: Not forthcoming (will follow up with Paul Nikolich, Chair of IEEE 802)

Request for IEEE 802.11 review of CAPWAP Taxonomy: Review comments approved at IEEE 802.11 plenary, sent to Bert Wijnen, CAPWAP WG chairs, posted to CAPWAP WG mailing list.

Discussion within IEEE 802.11 on need for Study Group on Access Point Functional Description: 802.11 Study Group to develop a PAR and 5 crteria approved by vote of 802.11.

For pointers to related documents, see:
http://www.drizzle.com/~aboba/IEEE/index.html#liaison

Liaison Communications received by IETF

From:  Stuart Kerry <stuart.kerry@philips.com>
To: iesg@ietf.org Date: 5/21/04

Dear IESG members,

The purpose of this e-mail is to request that draft-walker-ieee802-req-01.txt be published as an RFC, or at your discretion, as an IETF Best Current Practice Document. This document incorporates the agreed changes from the IETF last call review comments. The IEEE 802.11 WG has agreed with the proposed changes, per adoption of IEEE 802.11 document 04/160r5, “EAP Method Requirements for Wireless LANs” at the May 10-14 meeting.

The IEEE 802.11 WG believes that review of an EAP method’s claimed conformance to the stated EAP Method Requirements is required, and has stated the requirement that EAP methods claiming conformance to the IEEE 802.11 wireless LAN requirements for EAP methods must complete IETF last call review. Please confirm that this process is acceptable to you.

Thank you for the early assignment of a RFC number for RFC 3748, per my previous request, and for your ongoing support of IEEE 802.11 requests.

Regards,

Stuart
Stuart J. Kerry
Chair, IEEE 802.11 WLANs WG