Home»Liaisons»IETF Liaison Manager Reports»IETF / IEEE 802 Liaison Reports and Documents»Workshop December 2003
Proposal for the IETF/IEEE 802 Liaison Workshop.
Date: 9-Dec-2003
From: Bernard Aboba
To: IAB
- Location:
- Hyatt Regency
655 Burrard St.
Vancouver, BC
V6C 2R7 Canada
Phone: +1 604 683 1234
Fax: +1 604 689 3707
- Date:
- Sunday, January 11, 2004
- Time:
- Noon – 6 PM
- Info & Reservations:
- Meeting Plan
Group Booking
- Workshop Description:
- This workshop will focus on coordination issues relating to upcoming work in IETF and IEEE 802. As work requiring coordination between the two bodies continues to grow, there is a need for scalable communication mechanisms between the two organization. This workshop will cover specific issues that have arisen within IEEE 802 and IETF WGs within the last year in order to frame the types of issues being encountered. The audience for the workshop are members of the IEEE 802 ExComm, as well as members of the IETF IESG and IAB as well as chairs and editors of selected IEEE 802, IETF and IRTF WGs.
- Potential Attendee list:
- IETF
IESG & IAB
Ex-IESG: Erik Nordmark, Frank Kastenholz
IEEE 802.3 Liason: Dan Romascanu
DNA BOF: Greg Daley
EAP WG: Jari Arkko
AAA WG: David Mitton, John Loughney
RADEXT BOF: David Nelson
CAPWAP BOF: Dorothy Gellert
SEND: Pekka Nikander
IRTF Mobility: Bill Arbaugh
MIPSHOP: Gabriel Montenegro
MIPv4: Henrik LevkowetzIEEE
IEEE 802 ExComm
IEEE 802: Paul Nickolich
IEEE 802.11: Stuart Kerry
IEEE 802.11 Liason: Dorothy Stanley
IEEE 802.1: Tony Jeffree, Mick Seaman, Paul Congdon
IEEE 802.11f: Dave Bagby, Bob O’Hara
IEEE 802.11i: Dave Halasz
Fast Handoff SG: Clint Chapman
Handoff ECSG: David Johnston
3GPP Observer: Stephen Hayes
- Strawman Agenda:
- Introduction
Questions for the Day
How do IETF and IEEE 802 coordinate going forward?
- How should we structure the liason relationship?
- Do IEEE 802 and IETF need to appoint additional liasons?
- How do IEEE 802 and IETF communicate dependencies and status?
- How do we determine the split of work between the two organizations on new items?
Technical Presentations:
- How can L2 protocols provide “strong” hints of subnet change to IP?
Why have previous attempts only generated “weak” hints?
- Case study:
- Inter-subnet roaming and Detection of Network Attachment
- WGs:
- IETF DNA BOF and IEEE 802.21 Handoff WGs
- Discussion leaders:
- Bernard Aboba, Greg Daley, David Johnston
- How do we provide scalable, low latency, ubiquitious network capability discovery?
What are the issues with current network discovery mechanisms?
- Case study:
- Network Selection: EAP and IEEE 802 network discovery
- WGs:
- IETF EAP WG, WFA Public Access, IEEE 802.11, IEEE 802.1ab, IEEE 802.1af
- Discussion leaders:
- Jari Arkko, Dorothy Stanley, Paul Congdon
- How can L2 protocols provide reliable “link up” and “link down” indications to IP?
Why can this be a problem for TCP and IP?
- Case study:
- False “Link up” indications: IEEE 802.11f versus IEEE 802.11i
- WGs:
- IETF DNA BOF, IEEE 802.11i, IEEE 802.11f
- Discussion leader:
- Bernard Aboba
- How can L2 and L3 cooperate so as to reduce total handoff latency while retaining security?
Why are there so many so many security exchanges required for handoff? (e.g. IEEE 802.1X/EAP, 4-way handshake, group-key handshake, DNA, DAD, SEND, MIP)
- WGs:
- IETF EAP WG, DNA BOF, SEND, MIPv6, IEEE 802.11i
- Discussion leaders:
- Bill Arbaugh, James Kempf, Greg Daley
- Documents:
- http://www.ietf.org/internet-drafts/draft-ietf-send-ndopt-00.txt
http://www.ietf.org/internet-drafts/draft-irtf-aaaarch-handoff-04.txt
http://www.ietf.org/internet-drafts/draft-ietf-eap-keying-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-ipv6-24.txt
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-ha-ipsec-06.txt- How should IETF and IEEE handle work relating to “split APs”?
- WGs:
- IETF CAPWAP BOF, IEEE 802.11 WLANNG
- a. Discovery
b. Encapsulation
c. Management
d. Control
- Discussion leaders:
- James Kempf, Bob O’Hara, Dorothy Gellert