Re: [Sdn] SDN reading list

Christian Esteve Rothenberg <chesteve@gmail.com> Wed, 03 August 2016 21:01 UTC

Return-Path: <chesteve@gmail.com>
X-Original-To: sdn@ietfa.amsl.com
Delivered-To: sdn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C36E12D863 for <sdn@ietfa.amsl.com>; Wed, 3 Aug 2016 14:01:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZuYdD72eP7LC for <sdn@ietfa.amsl.com>; Wed, 3 Aug 2016 14:01:43 -0700 (PDT)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADAD12D85E for <sdn@irtf.org>; Wed, 3 Aug 2016 14:01:43 -0700 (PDT)
Received: by mail-vk0-x233.google.com with SMTP id s189so155404565vkh.1 for <sdn@irtf.org>; Wed, 03 Aug 2016 14:01:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=+8XOhIVWDTaDMwkhBaS70P8M26GMr+6qpEx9Js+ZlvI=; b=okyTBmrAzX1E3gkmSQ+cLTQn3vnHl281NAu86S8JDGNgnWdhRrHXK8hxDWKu3CH2jr 5O+pa4EnYbaSmTXQjBhik8fg/pl25uEiEgOUPVFErV0XazpV4Jr7sbUP1OTT3f1d4FNE 69XV1SguS4XUYiaIKRUwqZXCUXE8hvBVuQKbGxA8Pp8iJI9yR2riG0HuUGToS8a+9IQI litBaALvwmBR5uXP0GyO2ydSWikuvIBKU//ID+ARx3B04ZwnoEtcNBOJjpEP4+d1nCAX 35O6hu7bOdb4TAK7JSNPYxezOyXi0+o48I4UziPStZjj80jzlbxY5l/J4VV8J+URekHo qPhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=+8XOhIVWDTaDMwkhBaS70P8M26GMr+6qpEx9Js+ZlvI=; b=gATdP/xULB+v27/yq+kBTc3tkgn0MBl080F8JtjQkDP3+NdcWztwG6lnVH3iP4QRby XJF1GMs4sZYXYQcZQIH8vOJOXGNxbDwDR6vUjpkuriUW/Ek9dCN4PWmsDAIOwu2fau99 VCwvJmproXvKaiBA/4ztLjdP58LWIsIP6yXi+oaCenPiafK0C1H40BR0Er9sdSDOPlJr xjUCtM6tAK+txc+P6KtjjOK8NYTOZqzoHJqFeEgJY5FxG2hT7ItNMh8cIdVNNY3dug5e sc4oUX2/aiYY2LtOHA0V0IhLGMMUX8pOOorb6u2fiZANBmTvu9DwW6FgbWnpyJWQ+0iE 2JgA==
X-Gm-Message-State: AEkoout5JfgLF079F13iVJuFYhUTcKlHc3PnptR+wfdyzdUP4ukmGevfsX6kcY/fAkahcW6k4AjKCHIzw1y9jw==
X-Received: by 10.31.220.66 with SMTP id t63mr34289808vkg.113.1470258102320; Wed, 03 Aug 2016 14:01:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.80.171 with HTTP; Wed, 3 Aug 2016 14:01:20 -0700 (PDT)
In-Reply-To: <CAEj5p9QoLzmjEBgWDJH-K_Pd2oLdApGvVf++U5H9tFEuTXansg@mail.gmail.com>
References: <71448255-655A-4E36-9A61-A2F973CE5A37@nec-labs.com> <3103D5C4-8312-43CF-8873-3F93E06D64D3@lancaster.ac.uk> <65174429B5AF4C45BD0798810EC48E0A8C43C422@EX-0-MB2.lancs.local> <CACdAPrBymGc3T2rTCi8XCo6_tgvXsn87PZ_b4r7XX=a1so8t5g@mail.gmail.com> <CAEj5p9S6uky77gSCgimmNrMToHQjf=S1H_7fK9z0EPQ0ohf15A@mail.gmail.com> <CAEj5p9QoLzmjEBgWDJH-K_Pd2oLdApGvVf++U5H9tFEuTXansg@mail.gmail.com>
From: Christian Esteve Rothenberg <chesteve@gmail.com>
Date: Wed, 3 Aug 2016 18:01:20 -0300
Message-ID: <CAEj5p9QWHxG2j6gLoPfZ+L=KU_jdBr7GzUv+2kB_AfuMiHkOVw@mail.gmail.com>
To: SDN IRTF list <sdn@irtf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/sdn/AAHPVeCzu-gcwgYJ-Ipep4XLmQU>
Subject: Re: [Sdn] SDN reading list
X-BeenThere: sdn@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List to Discuss SDN Research Group in the IRTF <sdn.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/sdn>, <mailto:sdn-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sdn/>
List-Post: <mailto:sdn@irtf.org>
List-Help: <mailto:sdn-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/sdn>, <mailto:sdn-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2016 21:01:51 -0000

Hi Cristian,

good idea around "crowdsourcing" this effort.

We tried something similar with our SDN survey by making it available
as a github repository:  https://github.com/SDN-Survey/latex/wiki
to keep the work alive over time with up-to-date arxiv versions:
http://arxiv.org/abs/1406.0440
Unfortunately, we only received a few pull requests and Email messages.

In any case, keeping a reading list up-to-date requires less efforts
compared to a survey.

We (cc: Gyanesh) would like to contribute to the Data plane realm. We
will send you a list of selected references per E-Mail.

If you could also add the github link of the SDN survey to its
reference under General design, maybe we can get more traction to
further contributions to that piece of work. Furthermore, keeping up
to date your reading list would pave the way for forthcoming revisions
of the survey by the original authors or new contributors...

Thanks,
Christian

On Wed, Aug 3, 2016 at 2:43 PM, Christian Esteve Rothenberg
<chesteve@dca.fee.unicamp.br> wrote:
> Hi Cristian,
>
> good idea to "crowdsource" this effort.
>
> We tried something similar with our SDN survey by making it available
> as a github repository:  https://github.com/SDN-Survey/latex/wiki
> to keep the work alive over time with up-to-date arxiv versions:
> http://arxiv.org/abs/1406.0440
> Unfortunately, we only received a few pull requests and Email messages.
>
> In any case, keeping a reading list up-to-date requires less efforts
> compared to a survey.
>
> We (cc: Gyanesh) would like to contribute to the Data plane realm. We
> will send you a list of selected references per E-Mail.
>
> If you could also add the github link of the SDN survey to its
> reference under General design, maybe we can get more traction to
> further contributions to that piece of work. Furthermore, keeping up
> to date your reading list would pave the way for forthcoming revisions
> of the survey by the original authors or new contributors...
>
> Thanks,
> Christian
>
>
>
>
>
>
> On Wed, Aug 3, 2016 at 1:41 PM, Juliano Wickboldt
> <jwickboldt@inf.ufrgs.br> wrote:
>>
>> Hi Cristian,
>>
>> Great job organizing this list!
>>
>> I would suggest that you add a "Management Plane" section under SDN Building Blocks, since you have "Control Plane" and "Data Plane" there already. I can be responsible for maintaining this section if you like. In ONF's architecture document (https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/TR_SDN-ARCH-Overview-1.1-11112014.02.pdf) the Management Plane is defined. There is also an RFC 7426 that considers the Management Plane in SDN's architecture, a bit differently though (https://tools.ietf.org/html/rfc7426).
>>
>> For example, design considerations for the management plane of SDN have been presented in "Software-Defined Networking: Management Requirements and Challenges. IEEE Communications Magazine: Network and service management series, Volume 53, Issue 1, January (2015). http://dx.doi.org/10.1109/MCOM.2015.7010546"quot;. There are several other studies published mainly in the network management community, i.e., IEEE-NOMS (ieee-noms.org), IEEE-IM (ieee-im.org), and CNSM (cnsm-conf.org), that can be included in this section.
>>
>> Best regards
>>
>> ________________________________
>> Juliano Araujo Wickboldt
>> Postdoctoral researcher
>> http://www.inf.ufrgs.br/~jwickboldt/
>>
>> On Mon, Aug 1, 2016 at 8:02 AM, King, Daniel <d.king@lancaster.ac.uk> wrote:
>>>
>>> The reading list looks great, we will add a link to the site from our SDN RG Wiki page.
>>>
>>> BR, Dan.
>>>
>>> -----Original Message-----
>>> From: sdn [mailto:sdn-bounces@irtf.org] On Behalf Of Broadbent, Matthew
>>> Sent: 01 August 2016 11:58
>>> To: Cristian Lumezanu <lume@nec-labs.com>
>>> Cc: sdn@irtf.org
>>> Subject: Re: [Sdn] SDN reading list
>>>
>>> Hello Cristian,
>>>
>>> Thank you for your time and effort compiling this reading list. It is certainly comprehensive and covers a number of topics; ideal for newcomers to the area.
>>>
>>> I would like to suggest, and also take responsibility for, a new sub-area: “Content Delivery”. This would fit under the “SDN Applications” title, and include work on how SDN can be used to improve and facilitate the delivery of video (and other types of media) across the Internet.
>>>
>>> Thanks
>>>
>>> Matt
>>>
>>> ―――――――――
>>> Matthew Broadbent
>>> School of Computing & Communications
>>> Lancaster University, UK
>>>
>>> On 27/07/2016, 16:36, "sdn on behalf of Cristian Lumezanu" <sdn-bounces@irtf.org on behalf of lume@nec-labs.com> wrote:
>>>
>>>     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
>>>
>>>     _______________________________________________
>>>     sdn mailing list
>>>     sdn@irtf.org
>>>     https://www.irtf.org/mailman/listinfo/sdn
>>>
>>>
>>> _______________________________________________
>>> sdn mailing list
>>> sdn@irtf.org
>>> https://www.irtf.org/mailman/listinfo/sdn
>>> _______________________________________________
>>> sdn mailing list
>>> sdn@irtf.org
>>> https://www.irtf.org/mailman/listinfo/sdn
>>
>>
>>
>> _______________________________________________
>> sdn mailing list
>> sdn@irtf.org
>> https://www.irtf.org/mailman/listinfo/sdn
>>