Old Stuff

This is just a quick copy/paste of what was on the previous conference WIKI. Remember that it is just provided for historical reference and does not reflect any decisions made for the 2010 conference.

1. Location

Baker University in Baldwin City. Room rental is a very affordable $50/room/day, lunch $7/person. Rooms already have projectors and wireless access can be made available.

Dale: Lodging could either be here in town at “ The Lodge”, or at a hotel on the south edge of Lawrence. I don’t know the number of rooms available at either, but can certainly look into that if we decide on either.

2. Tracks

Keith: I'd like to suggest that it be a single-track conference, for three reasons. First, I hate having to choose between two good sessions; I'd like to be able to attend every session that interests me.

Second, in the past, I've felt that less-interesting sessions got second-tracked instead of rejected. I would much prefer that we're forced to choose the best sessions and have a strong conference rather than host sessions that we know will be poorly attended but don't have the guts to decline.

And third, the KanREN conference always has great conversations happening in the halls outside the presentations. In my book, there's no shame in having sessions that are good but which don't appeal to everyone, and encouraging those hallway conversations to happen.

(Seems to have consensus.)

3. Rooms

Keith + Cort: Suggest have three rooms:

Presentation room, as small as possible to get the audience up front and engaged.
"Cry room" with A/V run from presentation room and projected here also, for attendees who want to multitask during presentations. Anyone wanting to check email during a talk should get out of the presentation room.
"Networking room," a designated area (could be a hallway lounge) to encourage those informal conversations to happen.

2008 Conference Dates and Schedule

Work Schedule

Target Date
Drop Dead Date
Date and facilities
. . . Investigate Washburn option
Washburn won't be able to host
. . . Settle on date, location, and duration
. . . Announce date / location to membership
. . . Reserve location
. . . Contact hotel for accommodations
. . . Calculate cost for conference fees
. . . KanREN order/purchase food, supplies, etc.
. . . Generate list of proposed sessions
. . . Compose CFP
. . . Send out
Discuss format
. . . Number of days
. . . Number of sessions
. . . Meal requirements
. . . Room requirements
Select presentations
. . . Presentation proposals due back
. . . Select presentations
. . . Notify / confirm presenters
. . . Settle on agenda
. . . Presentation slides due from presenters
. . . Open registration
. . . Early registration cutoff
. . . Print and compile handouts
KanREN reserve rooms for presenters
. . . Coordinate setup / staffing with KanREN
. . . Setup rooms at location
. . . Have conference
Dale: The only dates that are available for Baker to be able to host would be October 16 and 17. This is due to classes being in session. If we want to look into some other avenue, I am certainly open to it. FYI if we want Baker to host it this year, we need to get a move on as hotel rooms in the area will be VERY hard to come by as this is the Thursday and Friday before the Annual Maple leaf Festival here in Baldwin.

1. Lightning talks

Keith: I'd like to organize a session's worth of lightning talks, five-minute presentations from many different presenters. The individual talks can be short intros or overviews of something you've done or are working on, teasers that will lead people to contact you for more information, or whatever you want, EXCEPT they shouldn't be "commercials" for a longer talk later in the conference. The MC is strict with the clock to keep things moving and to give all the presenters a fair chance.

2. Non-Internet uses of the KanREN backbone

I know PSU is exploring a remote SAN solution with FHSU, and I'd like to hear about it in detail. And by "in detail," I mean mostly from the storage, server, and logistics perspective, and a little bit (but pretty light) on the WAN configuration.

Most of the conference attendees are never going to set up MPLS VLANs (or whatever this uses), and it's not particularly important for us to know every last detail of how they work -- just a general overview of how they fit this application and how their characteristics might fit other applications. But seeing from the member side what you can do with the new backbone that (1) we couldn't before, and (2) we might not have thought of yet, has huge potential benefit.

3. Survey of universities' traffic-shaping practices

WSU does no shaping and no internal QoS, and (even before the new KanREN backbone) has better performance than when we were using a PacketShaper. I'd like to hear what everyone else is doing, where shaping is positioned within the topology, what the network staff's interactions with it are like, and what the user experience and feedback is.

I'm thinking ASAP send out a survey to the techreps list, gather the results, and have someone go through them and plot out a panel session. Have a representative from each site present their overall shaping strategy, and have whoever coordinates the session pick particularly interesting survey results to dig into in more detail.

4. Survey of universities' firewall practices

Same type of information as above.

2008 KanREN Annual Representatives Conference Call for Proposals

The 2008 KanREN conference planning committee would like to open the floor to presentation proposals for the fall conference, October 16 2008. We'd also like to invite you to request presentations you'd like to see, and we'll try to find someone to present them for you.

If you have proposals for session topics, either a session you'd like to present or a session you'd like to attend, please email the proposals to conference@kanren.net . Session length will be flexible, probably between 40 and 55 minutes, at the presenter's discretion.

Please include the following when submitting a proposal:

Description of activity, project, or solution
Importance or relevance for other institutions
Name(s) of presenter(s) and title(s)
Contact information: Name, title, phone number, and email address
As the regents universities are the largest members of KanREN and seem to have the most resources and the most projects underway, the committee would like to request that each university submit at least one proposal.

Proposals will be accepted until Friday, July 25, and presenters will be notified by Friday, August 1 of which sessions have been selected.

Free registration will be provided for all accepted presentations.

We've listed some topics below for which we'd be interested in receiving detailed proposals. We welcome any and all proposals, and hope that these will get some ideas flowing.

Non-Internet uses of the KanREN backbone
We've traditionally thought of KanREN as providing Internet and I2 connectivity; but with the new backbone, KanREN has dramatically increased the flexibility of services that can be provided. PSU and FHSU are partnering to explore a remote SAN solution, and a presentation on the member perspective of that experience would be very welcome.
Survey of university and/or non-university traffic-shaping practices
Different KanREN members have different approaches to prioritizing traffic and blocking or limiting P2P. Someone could survey the members and then host a panel to present and discuss the results, perhaps focusing on where shaping is positioned within the campus network, what the network staff's interactions with it are like, and what the user experience and feedback is. For sheer size considerations, it might make sense to limit this to only universities or only non-university sites, with the hope that the findings would be interesting to other sites as well.
Survey of university and/or non-university firewall practices
Similar to the traffic-shaping idea, survey and host a panel discussion on what types of firewalls are in use (appliances, router ACLs, Unix/Windows-based, etc.), where they're positioned within the campus network, how they're managed, and what the user response is like.
Subpages (1): test