- Timeframe IETF 93 (Prague)
Previous meeting BOFs
- Timeframe IETF 92 (Dallas)
- Timeframe IETF 91 (Honolulu)
- Timeframe IETF 90 (Toronto)
- Timeframe IETF 89 (London)
- Timeframe IETF 88 (Vancouver)
- Timeframe IETF 87 (Berlin)
- Timeframe IETF 86 (Orlando)
- Timeframe IETF 85 (Atlanta)
- Timeframe IETF 84 (Vancouver)
- Timeframe IETF 83 (Paris)
- Timeframe IETF 82 (Taipei)
- Timeframe IETF 81 (Quebec City)
- Timeframe IETF 80 (Prague)
- Timeframe IETF 79 (Beijing)
- Timeframe IETF 78 (Maastricht)
- Timeframe IETF 77 (Anaheim)
- Timeframe IETF 76 (Hiroshima)
- Timeframe IETF 75 (Stockholm)
- Timeframe IETF 74 (San Francisco)
- Timeframe IETF 73 (Minneapolis)
- Timeframe IETF 72 (Dublin)
- Timeframe IETF 71 (Philadelphia)
- Timeframe IETF 70 (Vancouver)
- Timeframe IETF 69 (Chicago)
- Timeframe IETF 68 (Prague)
- Timeframe IETF 67 (San Diego)
- Timeframe IETF 66 (Montreal)
- Timeframe IETF 65 (Dallas)
Birds of a Feather Meetings (IETF Pre-WG Efforts)
This page provides one common place that lists "possible IETF pre-WG efforts", known as Birds of a Feather ("BoF") meetings. Anybody who proposes a BoF is strongly encouraged to register the BoF effort here at such time as appropriate; e.g., during steps 1 and 2 in RFC 5434. Also see http://www.ietf.org/wg/bof-procedures.html.
The IAB will also attempt to provide BoF Shepherds as described in their document on the subject only on request from the IESG. If you feel that your BoF would benefit from an IAB BoF Shepherd, please discuss this with your Area Director.
To allow the Secretariat to schedule a BoF slot if it is approved, each entry MUST include the following items:
- Long name and abbreviation
- Description, including whether the BoF is intended to form a WG or not
- The responsible Area Director (AD)
- BoF Chairs (or the ADs as placeholders)
- Number of people expected to attend
- Length of session (1, 1.5, 2, or 2.5 hours)
- Conflicts to avoid (whole Areas and/or WGs)
- Does it require WebEX? If so, why?
- Does it require Meetecho? If so, why?
- Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
Timeframe IETF 93 (Prague)
Current schedule of "Important Dates" requires that all BOF proposal requests be submitted to Area Directors (ADs) by 2359 UTC Friday, 2015-06-05. The IAB and IESG will hold a joint teleconference to discuss the proposals. ADs will be expected to approve or disapprove the BOF request on that teleconference, ensuring that the Secretariat has all of the information to put the first draft of the agenda together on or before 2015-06-19.
Name: CAPtive PORTal interaction (CAPPORT)
Description: Improve the interaction with captive portals. Captive portals are used in many locations (e.g coffeeshops, hotels). With a move to a more secure Internet, the interception techniques become increasingly problematic. The user experience also leaves much to be desired. This BoF seeks to understand if there is sufficient energy to work on the problem and design a protocol for interacting with captive portals.
Agenda [ To be filled in ]
Status: WG Forming
Responsible AD: Barry Leiba
Number of people expected to attend: 100
Length of session: 1.5 hours (we are fine with longer, whatever works best for scheduling)
Conflicts to avoid: 1st: DANE, DPRIVE, OpsAWG (WK co-chairs these), httpbis 2nd: DNSOP, appawg
Does it require WebEX? No
Does it require Meetecho? Yes
Links to the mailing list, draft charter if any, relevant Internet-Drafts, etc.
Mailing List: https://www.ietf.org/mailman/listinfo/captive-portals
Draft charter: TBD
[ Note: This is a proposed BoF - we are still determining if we sufficient interest to burn meeting time, but figured worth filling in the form now. We had a bar BoF in Dallas with significant interest. See: https://github.com/httpwg/wiki/wiki/Captive-Portals ]