Re: [Sdn] SDN reading list

["WRIGHT, STEVEN A" <[e-mail]>]

+1


best regards
Steven Wright, MBA, PhD, JD.
NFV & SDN Industry Engagement
Standards & Industry Alliances
AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 404.499.7030

[e-mail]<mailto:[e-mail]>
@DrStevenAWright (personal)
www.linkedin.com/in/drstevenawright/<http://www.linkedin.com/in/drstevenawright/>

From: sdn [mailto:[e-mail]] On Behalf Of Matta, Abraham I
Sent: Wednesday, August 03, 2016 3:30 PM
To: Dave Hood <[e-mail]>; Juliano Wickboldt <[e-mail]>; King, Daniel <[e-mail]>
Cc: [e-mail]; Broadbent, Matthew <[e-mail]>; Cristian Lumezanu <[e-mail]>
Subject: Re: [Sdn] SDN reading list

Very much agree with Dave on the recursive nature of networks, see e.g.

http://csr.bu.edu/rina/papers/CoolSDN2014.pdf

Best,
ibrahim

From: sdn <[e-mail]<mailto:[e-mail]>> on behalf of Dave Hood <[e-mail]<mailto:[e-mail]>>
Date: Wednesday, August 3, 2016 at 2:22 PM
To: Juliano Wickboldt <[e-mail]<mailto:[e-mail]>>, "King, Daniel" <[e-mail]<mailto:[e-mail]>>
Cc: "Broadbent, Matthew" <[e-mail]<mailto:[e-mail]>>, "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>, Cristian Lumezanu <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Sdn] SDN reading list

I thought the list was interesting inasmuch as it did not include anything about SDN architecture. It would surely be worth listing SDN architecture 1.1<https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/TR-521_SDN_Architecture_issue_1.1.pdf> [note: the 1.1 overview link below really refers to issue 1.0; it is out of date and should probably be removed from the listing], the relationship between SDN and NFV<https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/onf2015.310_Architectural_comparison.08-2.pdf>, and the paper on SDN and 5G slicing<https://www.opennetworking.org/images/stories/downloads/sdn-resources/technical-reports/Applying_SDN_Architecture_to_5G_Slicing_TR-526.pdf>.

Because of heavily interrelated recursion, the idea of planes becomes less and less useful. One man’s data plane is another man’s control plane is another man’s applications plane. Management and control form a continuum, not separable planes. Services and orchestration and other concepts that appear in planar models are likewise relative and recursive. The upshot is that we are moving away from the idea of planes as useful modeling concepts. FWIW.

Dave

From: sdn [mailto:[e-mail]] On Behalf Of Juliano Wickboldt
Sent: Wednesday, August 03, 2016 9:41 AM
To: King, Daniel <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>; Broadbent, Matthew <[e-mail]<mailto:[e-mail]>>; Cristian Lumezanu <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Sdn] SDN reading list

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". There are several other studies published mainly in the network management community, i.e., IEEE-NOMS (ieee-noms.org<http://ieee-noms.org>), IEEE-IM (ieee-im.org<http://ieee-im.org>), and CNSM (cnsm-conf.org<http://cnsm-conf.org>), that can be included in this section.

Best regards

________________________________

[ttp://www.inf.ufrgs.br/~jwickboldt/wp-content/uploads/inf_email.jpg]

Juliano Araujo Wickboldt
Postdoctoral researcher
http://www.inf.ufrgs.br/~jwickboldt/<http://www.inf.ufrgs.br/%7Ejwickboldt/>


On Mon, Aug 1, 2016 at 8:02 AM, King, Daniel <[e-mail]<mailto:[e-mail]>> 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:[e-mail]<mailto:[e-mail]>] On Behalf Of Broadbent, Matthew
Sent: 01 August 2016 11:58
To: Cristian Lumezanu <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
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" <[e-mail]<mailto:[e-mail]> on behalf of [e-mail]<mailto:[e-mail]>> 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
    [e-mail]<mailto:[e-mail]>
    https://www.irtf.org/mailman/listinfo/sdn


_______________________________________________
sdn mailing list
[e-mail]<mailto:[e-mail]>
https://www.irtf.org/mailman/listinfo/sdn
_______________________________________________
sdn mailing list
[e-mail]<mailto:[e-mail]>
https://www.irtf.org/mailman/listinfo/sdn