[ietf78-tech] Admission Control: Just to be completely clear

[Joel Jaeggli]

Not the it helps or anything but John and I will be in the same location at the end of the week it think.

I think modula the 802.1x digression we have consensus around the following things.

Prototype captive portal
A need for two machines
Identy token (email address) and secret key (registration code)
Hopefully the non mandatory nature of the experiment.

Item 3 is what gets socialized with Ray and Russ.

Joel 

Joel's iPad

On Jun 27, 2010, at 8:18 PM, Jim Martin <jim at daedelus.com> wrote:

> Gentlepeople,
> 	From some of the comments that have flown around here in the last day or so, I'm concerned that we aren't all in sync on what we're trying to do with the admission control project. Here's an attempt to clarify it from my point of view. If anyone disagrees with this, please speak up!
> 
> Goal
> ------
> 	The IETF Meeting in Beijing this fall will have a network that is designed to connect to the Internet in a completely unfiltered way. Due to this lack of filtering, we've been asked to ensure that only IETF attendees can gain access to that network. At this point, the requested authentication tokens are a simple shared username/password that are distributed to the attendees as they arrive, however we'd like to ensure that per-user authentication is possible should the requirements become more strict. 
> 
> 	To this end, we'd like to prototype this admission control system for Maastricht, both to validate the system under load and to provide a "heads up" to the attendees that this will be the way things are in Beijing.  This also allows us to disable the admission control if there's a problem, an option not available in Beijing. 
> 
> Caveats
> -----------
> 	-  We're late. We need to socialize what we'll be doing to the IETF community via Ray (IETF Administrative Director) and Russ (IETF Chair), so we need to get them information soon.
> 
> 	- We have people with very limited laptops/devices, so we cannot assume they can to 802.1x
> 
> 	- We have some very privacy focused individuals which will undoubtedly be concerned with anything we do. We simply need to avoid stirring up the hornets more than we need to.
> 
> 	- The equipment being used in Maastricht is not guaranteed to be the same equipment being used in Beijing. Keeping things as device agnostic as possible is a good thing. 
> 
> 	- Failure /IS/ an option in Maastricht, but would be very bad in Beijing
> 
> 
> Timeline
> ------------
> 	We really need a fleshed out plan ASAP. There an administrative call for the Maastricht IETF early (US) Tuesday morning where we should be able to put details forward.
> 
> 	- Jim
> 
> _______________________________________________
> ietf78-tech mailing list
> ietf78-tech at daedelus.com
> http://www.daedelus.com/mailman/listinfo/ietf78-tech