Saturday, September 29, 2012

Journals vs. Conferences

I am knee deep in INFOCOM reviews and like most of the TPC (Technical Program Committee), I have of course been a really good reviewer and done all of my reviews weeks in advance.  Or not.  On the plus side, I am on read number two after the initial skim where my trusty red or blue pen gets a work out.  6k+ characters for the last review is none too shabby though it does help when I have done work in that exact particular area.  Anonymity fail perhaps with that one. 

On a side note, I think I got blessed by the random paper assignment overlords this time.  I have to say that I am thoroughly enjoying all of the papers in my stack.  Does not mean that I am giving out all accepts but well done overall.  Though I think I have a huge sample of TPC area leads.  Huge kudos for whomever cut out of the rank this paper field from prior years.  That was always tedious to go back to all of the reviews and rank them once you got through the pile.

Anyway, paging through the reviews, one particular thought struck me.  Given that systems / networking research tends to view itself as being a bit of a "special flower" where journals are optional, does that mean that I as the reviewer for a top tier conference need to raise the bar and require additional completeness in the paper?

For example, suppose a paper is an area where the author (senior researcher) has published for 3+ years.  Said author submits a paper in that same area which reads tremendously well but is fairly incremental.  Should there any consideration for me as the reviewer to note that the author does not go the journal route and hence is unlikely to ever really "complete" the work if it does not end up in a thesis?

The simple answer is that no, I don't think it would be fair for me to take that into consideration as I think that would impose an unexpected burden on the author.  The unforeseen burden is especially keen given that nearly all papers are driven by the students and it is definitely unfair to weigh the student with the prior behavior of the adviser (though for some reason, the converse never applies but never mind). 

The more nuanced answer is that I think this is something that we as a community (networking / systems) need to deal with.  I think we have long ago passed the threshold where one can get by doing "one off" papers that might have some justification for a more conference-centric view.  I don't think a reviewer can do this either as that is bound to end up disastrous.  We already have enough subjective evaluation, let's not add another one to the mix.  It is rather something to discuss at the community level, say a TCCC or other level and I think it has to be a community ethic sort of thing.  

Particularly for those who care deeply that conferences are more important than journals, I think there has to be a serious answer as to when the work gets "complete."  Otherwise, it becomes yet another item to add to criticisms of why CS will have difficulty supporting the conferences-only notion for promotion and tenure.  In a later posting, I'll add my thoughts on the article by my department chair (Kevin Bowyer) on conferences versus journals and how a junior faculty should view them.  If you have not garnered by above, I am largely in agreement and the above is yet another reason why I think he is right for promotion / tenure.  
Note: For anyone reading this if you think that I did this to your INFOCOM paper, no I did not and you are happy to drop me a note for me if you want to break the veil of anonymity.  Whoot, go, go, gadget tenure :)   

Sunday, September 9, 2012

Visit - Sprint at the Wireless Institute

One of the nice perks of being at Notre Dame is the wicked, cool set of speakers that we get to have the privilege of listening to.  For this past week, we were the host of Bob Azzi, Sprint's senior vice president of network operations.  Unfortunately due to obligations related my Associate Chair hat, I had to duck out early from the question and answer session and missed the second half of the session.

A few interesting bits from the talk and Q&A that stood out for me:
  • A certain other cell network when they had employed data caps expecting to see revenue generation.  In reality, users heavily capped their behavior when they hit the limit and it ended up not generating any substantial new revenue.  It definitely raises some interesting questions related to our WiFi offloading study as a comment was raised whether or not users will modify their behaviors as they get closer to the cap.  With our Cell Phone Study getting our data services from Sprint, this was not an issue due to the unlimited data plans.  It certainly would have some interesting effects for non-Sprint customers if we could monitor several in our study.  From a larger perspective, I have to think data like that would give execs at Verizon pause as the whole shared data plan sort of thing could get ugly in a heartbeat. 
  • DPI (Deep Packet Inspection) and video translation for the win.  18-20% reduction by whacking certain low hanging video streams from 1080p when the type of mobile device is known (non-tethered too I assume) to be more appropriate for the screen size.  I'll have to do a bit more digging to see what devices are involved but very smart plays to re-encode said video to alleviate the last mile. 
  • As academics in networking, we sometimes can forget that the real network is messy and that any sort of pico / metro cell magic is going to be awful due to the sheer scope / complexity of rolling it out for real.  Techniques like SON (Self-Optimizing Networks) are going to be essential for realizing HetNets.  Right of way / property are powerful things indeed (i.e. how do power / cable / get permission to install a pico or metro cell).
  • Similarly, cell networks are not nearly as monolithic as one would imagine, often involving many agreements across a variety of networks to be able to provide full nation-wide coverage.  It definitely adds a unique complexity wrinkle to deployment that the community needs to be more mindful of.
  • Finally, like all things technology, technology is only one part of it and policy, particularly public policy is a very, very important part.  We really need more engineers who can correctly inform technology decisions.
Hopefully we will be able to post up a video on the Wirelss Institute webpage in the next week or so with a recording of the core part of Azzi's talk.