Really nice site indeed. Here are some papers I haven't found in the site:

General Design
  Abstractions for software-defined networks
  http://dl.acm.org/citation.cfm?id=2661063

Control plane
  DISCO: Distributed multi-domain SDN controllers
  http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6838330

  ASIC: an architecture for scalable intra-domain control in OpenFlow
  http://dl.acm.org/citation.cfm?id=2377317

  Ravana: controller fault-tolerance in software-defined networking
  http://dl.acm.org/citation.cfm?id=2774996

  Rosemary: A Robust, Secure, and High-performance Network Operating System
  http://dl.acm.org/citation.cfm?id=2660353

  Towards an elastic distributed SDN controller
  http://dl.acm.org/citation.cfm?id=2491193

  Pratyaastha: an efficient elastic distributed SDN control plane
  http://dl.acm.org/citation.cfm?id=2620748

Data Plane
  NetPaxos: consensus at network speed
  http://dl.acm.org/citation.cfm?id=2774999

Security
  Attacking software-defined networks: a first feasibility study
  http://dl.acm.org/citation.cfm?id=2491220

  OpenFlow vulnerability assessment
  http://dl.acm.org/citation.cfm?id=2491222

  AVANT-GUARD: scalable and vigilant switch flow management in
software-defined networks
  http://dl.acm.org/citation.cfm?id=2516684

  Byzantine-Resilient Secure Software-Defined Networks with Multiple
Controllers in Cloud

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?reload=true&arnumber=6893017

  A security enforcement kernel for OpenFlow networks
  http://dl.acm.org/citation.cfm?id=2342466
    (Which led to:)
    Securing the Software-Defined Network Control Layer
    http://www.internetsociety.org/sites/default/files/10_3_2.pdf

  Five nines of southbound reliability in software-defined networks
  http://dl.acm.org/citation.cfm?id=2620752

Hope it can help.

Quamar Niyaz <quamarniyaz.zh...@gmail.com> escreveu no dia quarta,
27/07/2016 às 19:27:

> Hello Cristian,
> I am ready for volunteering. My area of research is on SDN Security, so I
> can be helpful for updating the security section.
>
> On Wed, Jul 27, 2016 at 11:48 AM, HENRYDOSS, JAMES <jd5...@att.com> wrote:
>
>> Hi Cristian,
>>
>> Please include my name. I am  available to support this website. This is
>> an excellent google page with latest updates on the SDN field.
>>
>> James Henrydoss
>> (404)-345-2524
>>
>> -----Original Message-----
>> From: openflow-discuss [mailto:
>> openflow-discuss-boun...@mailman.stanford.edu] On Behalf Of Cristian
>> Lumezanu
>> Sent: Wednesday, July 27, 2016 11:37 AM
>> To: s...@irtf.org; openflow-discuss@lists.stanford.edu <
>> openflow-disc...@mailman.stanford.edu>
>> Subject: [openflow-discuss] SDN reading list
>>
>> Hi everybody,
>>
>> I have been maintaining an SDN reading list (
>> https://sites.google.com/site/sdnreadinglist/) for the last four years.
>> My original goal was to provide a centralized repository of SDN research to
>> better help both newcomers and experienced researchers navigate this rather
>> new research area. The number of hits that the website receives every day
>> makes me think that this effort was not in vain. However, as the field of
>> SDN has grown rapidly in the past few years, so has the number of projects,
>> conferences, and papers that I must keep track of and update. This is
>> slowly taking up more time than I can allocate to it and the freshness of
>> the list suffers.
>>
>> Therefore, I would like to turn the SDN reading list into a collaborative
>> project. For this, I am looking for volunteers who would like to take over
>> the task of updating (and keeping up-to-date) small parts of the site. A
>> “part” could be a sub-area of SDN research, such as “verification” or
>> “monitoring and measurement". If it’s your own research area, even better,
>> you are probably following all related work anyway and would need little
>> time to keep your part up-to-date.
>>
>> If you can help with this, please send me a personal email with what
>> sub-areas you are comfortable updating and any other constraints that you
>> may have. Even if you don’t have time for this but you have suggestions for
>> how this reading list might better serve the community, please send them
>> along.
>>
>> Cristian
>>
>> _______________________________________________
>> openflow-discuss mailing list
>> openflow-discuss@lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>> _______________________________________________
>> openflow-discuss mailing list
>> openflow-discuss@lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>>
>
>
>
> --
> With regards,
> Quamar Niyaz
>
> _______________________________________________
> openflow-discuss mailing list
> openflow-discuss@lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
>
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss

Reply via email to