text:
Book of Amos
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Tanakh (Judaism)
Torah (Instruction)[show]
Genesis
Brʾeišyt
Exodus
Šemot
Leviticus
Wayiqra
Numbers
Bəmidbar
Deuteronomy
Devarim
Nevi'im (Prophets)[hide]
Former
Joshua
Yehoshua
Judges
Shofetim
Samuel
Shemuel
Kings
Melakhim
Latter
Isaiah
Yeshayahu
Jeremiah
Yirmeyahu
Ezekiel
Yekhezqel
Minor
Hosea
Joel
Amos
Obadiah
Jonah
Micah
Nahum
Habakkuk
Zephaniah
Haggai
Zechariah
Malachi
Ketuvim (Writings)[show]
Poetic
Psalms
Təhillîm
Proverbs
Mishlei
Job
Iyov
Five Megillot (Scrolls)
Song of Songs
Shir Hashirim
Ruth
Rut
Lamentations
Eikhah
Ecclesiastes
Qoheleth
Esther
Ester
Historical
Daniel
Daniyyel
Ezra–Nehemiah
Ezra
Chronicles
Dibh're Hayyamim
Old Testament (Christianity)
Pentateuch[show]
Genesis
Exodus
Leviticus
Numbers
Deuteronomy
Historical[show]
Joshua
Judges
Ruth
1 and 2 Samuel
1 and 2 Kings
1 and 2 Chronicles
Ezra
Nehemiah
Esther
Wisdom
Poetry
[show]
Job
Psalms
Proverbs
Ecclesiastes
Song of Songs
Prophetic[hide]
Major prophets
Isaiah
Jeremiah
Lamentations
Ezekiel
Daniel
Minor prophets
Hosea
Joel
Amos
Obadiah
Jonah
Micah
Nahum
Habakkuk
Zephaniah
Haggai
Zechariah
Malachi
Deuterocanonical[show]
Tobit
Judith
Additions to Esther
1 Maccabees
2 Maccabees
Wisdom of Solomon
Sirach
Baruch / Letter of Jeremiah
Additions to Daniel
Orthodox only
1 Esdras
2 Esdras
Prayer of Manasseh
Psalm 151
3 Maccabees
4 Maccabees
Odes
Orthodox Tewahedo
1 Enoch
Jubilees
1, 2, and 3 Meqabyan
Paralipomena of Baruch
Broader canon
Bible portal
v
t
e
The Book of Amos is the third of the Twelve Minor Prophets in the Hebrew Bible/Old Testament and the second in the Greek Septuagint tradition.[1] Amos, an older contemporary of Hosea and Isaiah,[2] was active c. 750 BCE during the reign of Jeroboam II[2] (788–747 BCE),[3] making the Book of Amos the first biblical prophetic book written. Amos lived in the kingdom of Judah but preached in the northern kingdom of Israel.[2] His major themes of social justice, God's omnipotence, and divine judgment became staples of prophecy.[2]
Contents
[hide]
1 Structure
2 Summary
3 Composition
4 Themes
5 References
6 Bibliography
7 External links
Structure[edit]
Papyrus Oxyrhynchus 846: Amos 2 (LXX)
(Michael D. Coogan, A Brief Introduction to the Old Testament, 2009, p. 256.)
Oracles against the nations (1.3–2.6)
Addresses to groups in Israel
Women of Samaria (4.1–3)
Rich persons in Samaria (6.1–7)
Rich persons in Jerusalem (8.4–8)
Five symbolic visions of God's judgment on Israel, interrupted by a confrontation between Amos and his listeners at Bethel (7.10–17):
Locusts (7.1–3)
Fire (7.4–6)
A plumb line (7.7–9)
A basket of fruit (8.1–3)
God beside the altar (9.1–8a)
Epilogue 9:8b–15
Summary[edit]
The book opens with a historical note about the prophet, then a short oracle announcing Yahweh's judgement (repeated in the Book of Joel).[4] The prophet denounces the crimes against humanity committed by the gentile nations, tells Israel that even they have sinned and are guilty of the same crimes, and report five symbolic visions prophesying the destruction of Israel.[5] Included in this, with no apparent order, are an oracle on the nature of prophecy, snippets of hymns, oracles of woe, a third-person prose narrative concerning the prophet, and an oracle promising restoration of the House of David, which had not yet fallen in Amos's lifetime.[4]
Composition[edit]
Amos prophesied during the reign of Jeroboam II, King of Israel, and of Uzziah of Judah, which places him in the first half of the 8th century BCE. According to the book's superscription (Amos 1:1) he was from Tekoa, a town in Judah south of Jerusalem, but his prophetic mission was in the northern kingdom. He is called a "shepherd" and a "dresser of sycamore trees", but the book's literary qualities suggest a man of education rather than a poor farmer.[6]
Scholars have long recognized that Amos utilized an ancient hymn within his prophecy, verses of which are found at 4.13; 5.8–9; 8.8; 9.5–6.[7] This hymn is best understood as praising YHWH for His judgment, demonstrated in His destructive power, rather than praise for creation.[8] Scholarship has also identified 'Sumerian City Lament' (SCL) motifs within Amos and particularly the hymn, offering the possibility that Amos used SCL as a literary template for his prophecy of Jerusalem's destruction.[9] The Amos hymn has also been discussed in terms of a 'covenant curse' which was used to warn Israel of the consequences of breaking the covenant, and in particular a 'Flood covenant-curse' motif, first identified by D.R. Hillers.[10] Recent scholarship has shown Amos' hymn is an ancient narrative text, has identified a new verse at 7.4; and has compared the hymn to the Genesis Flood account and Job 9:5–10.[11]
Themes[edit]
The central idea of the book of Amos is that God puts his people on the same level as the surrounding nations – God expects the same purity of them all. As it is with all nations that rise up against the kingdom of God, even Israel and Judah will not be exempt from the judgment of God because of their idolatry and unjust ways. The nation that represents YHWH must be made pure of anything or anyone that profanes the name of God. God's name must be exalted.
Amos is the first prophet to use the term "the Day of the Lord.[12] This phrase becomes important within future prophetic and apocalyptic literature. For the people of Israel "the day of the LORD" is the day when God will fight against his and their enemies, and it will be a day of victory for Israel. However, Amos and other prophets include Israel as an enemy of God, as Israel is guilty of injustice toward the innocent, poor, and young women.[13] To Amos "the day of the Lord" will be a day of doom.
Other major ideas in the book of Amos include: social justice and concern for the disadvantaged; the idea that Israel's covenant with God did not exempt them from accountability for sin; God is God of all nations; God is judge of all nations; God is God of moral righteousness; God made all people; God elected Israel and then liberated Israel so that He would be known throughout the world; election by God means that those elected are responsible to live according to the purposes clearly outlined to them in the covenant; if God destroys the unjust, a remnant will remain; and God is free to judge whether to redeem Israel.
References[edit]
Jump up ^ Sweeney 2000, p. unpaginated.
^ Jump up to: a b c d Harris, Stephen L., Understanding the Bible. Palo Alto: Mayfield. 1985.
Jump up ^ Finkelstein, Israel. The Forgotten Kingdom: The Archaeology and History of Ancient Israel. Atlanta: SBL, 2013. Ancient Near East Monographs, Number 5. p. 4.
^ Jump up to: a b Coogan 2008, p. 84.
Jump up ^ O'Brien 1990, pp. 26–27.
Jump up ^ Carroll R. 2003, p. 690.
Jump up ^ H.W. Wolff, Joel und Amos (Hermeneia; Philadelphia: Fortress Press, 1977), p. 215.
Jump up ^ P. Carny, ‘Doxologies: A Scientific Myth’, Hebrew Studies 18 (1977), pp. 149–59 (157)
Jump up ^ J. Radine, The Book of Amos in Emergent Judah (Tübingen: Mohr Siebeck, 2010)
Jump up ^ D.R. Hillers, ‘Treaty-Curses and the Old Testament Prophets’ (unpublished PhD dissertation); Rome Pontical Biblical Institute, 1964
Jump up ^ G. Cox, The ‘Hymn’ of Amos: An Ancient Flood Narrative. Journal for the Study of the Old Testament Vol 38.1 (2013): pp. 81–108
Jump up ^ Coogan, M. A Brief Introduction to the Old Testament: The Hebrew Bible in its Context. (Oxford University Press: Oxford 2009). p. 260
Jump up ^ Coogan, M. A Brief Introduction to the Old Testament: The Hebrew Bible in its Context. Oxford University Press: Oxford, 2009. pp. 258–59.
Bibliography[edit]
Bandstra, Barry L. (2008). Reading the Old Testament: an introduction to the Hebrew Bible. Cengage Learning. ISBN 0495391050.
Barton, John (2012). The Theology of the Book of Amos. Cambridge University Press.
Carroll R., M. Daniel (2003). "Amos". In Dunn, James D. G.; Rogerson, John William. Eerdmans Commentary on the Bible. Eerdmans. ISBN 9780802837110.
Collins, John J. (2014). Introduction to the Hebrew Scriptures. Fortress Press.
Coogan, Michael (2008). Reading the Old Testament: an introduction to the Hebrew Bible. Oxford University Press. ISBN 0495391050.
Hayes, Christine (2015). Introduction to the Bible. Yale University Press.
Sweeney, Marvin A. (2000). The Twelve Prophets: Volume 1: Hosea, Joel, Amos, Obadiah, Jonah. Liturgical Press. ISBN 9780814682432.
Bulkeley, Tim Amos: Hypertext Bible Commentary. Auckland: Hypertext Bible, 2005. Amos: Hypertext Bible Commentary
R. Carroll; M. Daniel (2002). Amos: The Prophet and His Oracles. Louisville: Westminster John Knox Press. , focus on historiography
Coote, Robert B. (1981). Amos Among the Prophets: Composition and Theology. Philadelphia: Fortress Press.
Doorly, William J. (1989). Prophet of Justice: Understanding the Book of Amos. New York: Paulist Press.
Easton's Bible Dictionary, 1897.
Hasel, Gerhard F. (1991). Understanding the Book of Amos: Basic Issues in Current Interpretations. Grand Rapids: Baker Book House.
Haynes, John H. (1988). Amos the Eighth Century Prophet: His Times and His Preaching. Nashville: Abingdon Press.
Keil, C. F. (1986). Commentary on the Old Testament in Ten Volumes. Grand Rapids: William B. Eerdmans Publishing Company.
LaSor, William Sanford; et al. (1996). Old Testament Survey: The Message, Form, and Background of the Old Testament. Grand Rapids: William B. Eerdmans. CS1 maint: Explicit use of et al. (link)
Metzger, Bruce M.; et al. (1993). The Oxford Companion to the Bible. New York: Oxford University Press. CS1 maint: Explicit use of et al. (link)
Möller, Karl (2003). A Prophet in Debate: the Rhetoric of Persuasion in the Book of Amos. London: Sheffield Academic Press.
Paul, Shalom M. (1991). Amos: A Commentary on the Book of Amos. Hermeneia. Minneapolis: Fortress Press.
External links[edit]
Wikisource has original text related to this article:
Amos
Online translations of Book of Amos:
Jewish translations:
Amos (Judaica Press) translation [with Rashi's commentary] at Chabad.org
Christian translations:
Online Bible at GospelHall.org (English Standard Version)
Amos at Wikisource (Authorised King James Version)
Nicholas Whyte on Amos
New Advent Catholic Encyclopedia, Amos
Forward Movement, Amos an Introduction
Bible: Amos public domain audiobook at LibriVox Various versions
Book of Amos
Minor prophets
Preceded by
Joel Hebrew Bible Succeeded by
Obadiah
Christian
Old Testament
[show]
v
t
e
Book of Amos
Bible
Amos 1
2
3
4
5
6
7
8
9
Place
Ammon
Aram
Ashdod
Assyria
Bashan
Beersheba
Bethel
Calneh
Caphtor
Carmel
Dan
Edom
Ethiopia
Philistine
Gath
Gaza
Gilgal
Hamath
Hermon
Jerusalem
Kir
Samaria
Sodom and Gomorrah
Syria
Tekoa
Zion
People
Amaziah
Amorites
Amos
Jacob
Joseph
Jeroboam
Joash
Uzziah
Term
Nazarite
Orion
Pleiades
Prophet
Sources
Hebrew Bible
Septuagint
Latin Vulgate
Wycliffe Version
King James Version
American Standard Version
World English Version
← Book of Joel (chapter 3)
Book of Obadiah) →
[show]
v
t
e
Books of the Bible
Principal
divisions
Hebrew Bible/
Old Testament Protocanon
Genesis
Exodus
Leviticus
Numbers
Deuteronomy
Joshua
Judges
Ruth
1–2 Samuel
1–2 Kings
1–2 Chronicles
Ezra
Nehemiah
Esther
Job
Psalms
Proverbs
Ecclesiastes
Song
Isaiah
Jeremiah
Lamentations
Ezekiel
Daniel
Hosea
Joel
Amos
Obadiah
Jonah
Micah
Nahum
Habakkuk
Zephaniah
Haggai
Zechariah
Malachi
Deuterocanon
and Apocrypha
Catholic
Orthodox
Tobit
Judith
Additions to Esther
1 Maccabees
2 Maccabees
Wisdom
Sirach
Baruch / Letter of Jeremiah
Additions to Daniel
Susanna
Song of the Three Children
Bel and the Dragon)
Orthodox only
1 Esdras
2 Esdras
Prayer of Manasseh
Psalm 151
3 Maccabees
4 Maccabees
Odes
Tewahedo Orthodox
Enoch
Jubilees
1, 2, and 3 Meqabyan
Paralipomena of Baruch
Broader canon
Syriac
Letter of Baruch
2 Baruch
Psalms 152–155
New Testament
Matthew
Mark
Luke
John
Acts
Romans
1 Corinthians
2 Corinthians
Galatians
Ephesians
Philippians
Colossians
1 Thessalonians
2 Thessalonians
1 Timothy
2 Timothy
Titus
Philemon
Hebrews
James
1 Peter
2 Peter
1 John
2 John
3 John
Jude
Revelation
Subdivisions
Chapters and verses
Pentateuch
Wisdom
Major prophets / Minor prophets
Gospels
Synoptic
Epistles
Pauline
Johannine
Pastoral
Catholic
Apocalyptic literature
Development
Old Testament canon
New Testament canon
Antilegomena
Jewish canon
Christian canon
Manuscripts
Dead Sea Scrolls
Samaritan Pentateuch
Septuagint
Targum
Diatessaron
Muratorian fragment
Peshitta
Vetus Latina
Masoretic Text
New Testament manuscript categories
New Testament papyri
New Testament uncials
See also
Biblical canon
Luther's canon
Authorship
English Bible translations
Other books referenced in the Bible
Pseudepigrapha
list
New Testament apocrypha
Studies
Synod of Hippo
Textual criticism
Category
Portal
WikiProject
Book
Authority control
WorldCat Identities
VIAF: 183065024
LCCN: n79082390
GND: 4001761-8
SELIBR: 171353
SUDOC: 028922433
BNF: cb120657971 (data)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Book_of_Amos&oldid=825401660"
Categories:
8th-century BC books
Twelve Minor Prophets
Book of Amos
Hidden categories:
CS1 maint: Explicit use of et al.
Articles with LibriVox links
Wikipedia articles with VIAF identifiers
Wikipedia articles with LCCN identifiers
Wikipedia articles with GND identifiers
Wikipedia articles with SELIBR identifiers
Wikipedia articles with BNF identifiers
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Wikisource
Languages
Afrikaans
Alemannisch
العربية
Беларуская (тарашкевіца)
Boarisch
Brezhoneg
Català
Cebuano
Čeština
Dansk
Deutsch
Eesti
Español
Esperanto
Euskara
فارسی
Français
Frysk
Gaeilge
Gàidhlig
गोंयची कोंकणी / Gõychi Konknni
한국어
Hrvatski
Bahasa Indonesia
Italiano
עברית
Basa Jawa
ქართული
Kiswahili
Lietuvių
Magyar
Malagasy
മലയാളം
Bahasa Melayu
Mìng-dĕ̤ng-ngṳ̄
Nederlands
日本語
Norsk
Polski
Português
Română
Runa Simi
Русский
Gagana Samoa
Simple English
Slovenčina
Српски / srpski
Srpskohrvatski / српскохрватски
Suomi
Tagalog
தமிழ்
Türkçe
Українська
اردو
Vepsän kel’
Winaray
Wolof
Yorùbá
粵語
中文
Edit links
This page was last edited on 13 February 2018, at 05:00.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

values: Joshua 1:1 as recorded in the Aleppo Codex

attrs: href class title

attrs: class id href

values: NavToggle NavToggle1 #

values: width:22em;border-collapse:collapse; border-spacing:0px; border:none; width:100%; margin:0px; font-size:100%; clear:none; float:none;width:11.5em;margin-left:auto;margin-right:auto;line-height:1.2em;white-space:nowrap;

values: font-size: 105%; padding: 0.2em 0px 0.4em; text-align: center; display: none;

values: width:22em;border-collapse:collapse; border-spacing:0px; border:none; width:100%; margin:0px; font-size:100%; clear:none; float:none;width:10.0em;margin-left:auto;margin-right:auto;line-height:1.2em;white-space:nowrap;

values: width:22em;border-collapse:collapse; border-spacing:0px; border:none; width:100%; margin:0px; font-size:100%; clear:none; float:none;width:15.5em;margin-left:auto;margin-right:auto;line-height:1.2em;white-space:nowrap;

values: font-size: 105%; padding: 0.2em 0px 0.4em; text-align: center; border-bottom-width: 1px; border-bottom-style: solid; border-bottom-color: rgb(170, 170, 170); display: none;

values: float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse; border-spacing:0px; border:none; width:100%; margin:0px; font-size:100%; clear:none; float:none;line-height:1.4em;

values:
/wiki/Sapiential_Books
mw-redirect
Sapiential Books

values: padding:0.3em 0.4em 0.3em;font-weight:bold;border-top:1px solid #aaa;font-size:105%;border-bottom:1px solid #aaa;

values: float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%;line-height:1.4em;

values:
/wiki/Day_of_the_Lord
mw-redirect
Day of the Lord

values:
/wiki/Stephen_L_Harris
mw-redirect
Stephen L Harris

values: Category:CS1 maint: Explicit use of et al.

values:
/wiki/Minor_prophet
mw-redirect
Minor prophet

values: border-top: 5px solid #FFD700; text-align:center;

values: wikisource:la:Biblia Sacra Vulgata (Stuttgartensia)/Amos

values: nowraplinks hlist collapsible autocollapse navbox-inner

values: The Prayer of Azariah and Song of the Three Holy Children

values: Development of the Christian biblical canon

values: Non-canonical books referenced in the Bible

values:
nofollow
external text
https://viaf.org/viaf/183065024

values:
nofollow
external text
https://d-nb.info/gnd/4001761-8

values:
nofollow
external text
https://libris.kb.se/auth/171353

values:
nofollow
external text
https://www.idref.fr/028922433

values: Category:Wikipedia articles with VIAF identifiers

values: Category:Wikipedia articles with LCCN identifiers

values: Category:Wikipedia articles with GND identifiers

values: Category:Wikipedia articles with SELIBR identifiers

values: Category:Wikipedia articles with BNF identifiers

values: Discussion about edits from this IP address [ctrl-alt-n]

values:
/wiki/Book_of_Amos
View the content page [ctrl-alt-c]
c

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values:
https://af.wikipedia.org/wiki/Amos
Amos – Afrikaans
af
af
interlanguage-link-target

values: سفر عاموس – Arabic

values: Кніга прарока Амоса – Belarusian (Taraškievica orthography)

values:
https://br.wikipedia.org/wiki/Levr_Amos
Levr Amos – Breton
br
br
interlanguage-link-target

values:
https://de.wikipedia.org/wiki/Amos
Amos – German
de
de
interlanguage-link-target

values: کتاب عاموس – Persian

values:
https://gd.wikipedia.org/wiki/Amos
Amos – Scottish Gaelic
gd
gd
interlanguage-link-target

values: आमस आचें पुस्तक – Goan Konkani

values: ספר עמוס – Hebrew

values:
https://jv.wikipedia.org/wiki/Amos
Amos – Javanese
jv
jv
interlanguage-link-target

values: წინაწარმეტყველება ამოსისი – Georgian

values: ആമോസിന്റെ പുസ്തകം – Malayalam

values: Книга пророка Амоса – Russian

values: O le tusi a le Perofeta o Amosa – Samoan

values: Књига пророка Амоса – Serbian

values: ஆமோஸ் (நூல்) – Tamil

values: Книга пророка Амоса – Ukrainian

values: کتاب عاموس – Urdu

values:
https://wo.wikipedia.org/wiki/Amos
Amos – Wolof
wo
wo
interlanguage-link-target

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Book_of_Amos rootpage-Book_of_Amos skin-vector action-view


text:
Software-defined networking
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Not to be confused with ISDN (Integrated Services Digital Network).
hideThis article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)
This article has been nominated to be checked for its neutrality. Discussion of this nomination can be found on the talk page. (August 2014) (Learn how and when to remove this template message)
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (November 2014) (Learn how and when to remove this template message)
(Learn how and when to remove this template message)
Software-defined networking (SDN) technology is a novel approach to cloud computing that facilitates network management and enables programmatically efficient network configuration in order to improve network performance and monitoring.[1] SDN is meant to address the fact that the static architecture of traditional networks is decentralized and complex while current networks require more flexibility and easy troubleshooting. SDN suggests to centralize network intelligence in one network component by disassociating the forwarding process of network packets (Data Plane) from the routing process (Control plane). The control plane consists of one or more controllers which are considered as the brain of SDN network where the whole intelligence is incorporated. However, the intelligence centralization has its own drawbacks when it comes to security,[2] scalability and elasticity[3] and this is the main issue of SDN.
SDN was commonly associated with the OpenFlow protocol (for remote communication with network plane elements for the purpose of determining the path of network packets across network switches) since the latter's emergence in 2011. Since 2012,[4][5] however, for many companies OpenFlow is no longer an exclusive solution, they added proprietary techniques. These include Cisco Systems' Open Network Environment and Nicira's network virtualization platform.
SD-WAN applies similar technology to a wide area network (WAN).[6]
Contents
[hide]
1 History
2 Concept
3 The need for a new network architecture
4 Architectural components
5 SDN Control Plane
6 SDN flow forwarding (sdn)
7 Applications
7.1 SDMN
7.2 SD-WAN
7.3 SD-LAN
7.4 Security using the SDN paradigm
7.5 Group Data Delivery Using SDN
8 See also
9 References
10 External links
History[edit]
This section may need to be rewritten entirely to comply with Wikipedia's quality standards, as it seems to deviate from the SDN development history as described in this source. You can help. The discussion page may contain suggestions. (August 2015)
This section's factual accuracy is disputed. Relevant discussion may be found on Talk:Software-defined networking. Please help to ensure that disputed statements are reliably sourced. (November 2016) (Learn how and when to remove this template message)
The history of SDN principles can be traced back to the separation of the control and data plane first used in the public switched telephone network as a way to simplify provisioning and management well before this architecture began to be used in data networks.
The Internet Engineering Task Force (IETF) began considering various ways to decouple the control and forwarding functions in a proposed interface standard published in 2004 appropriately named "Forwarding and Control Element Separation" (ForCES).[7] The ForCES Working Group also proposed a companion SoftRouter Architecture.[8] Additional early standards from the IETF that pursued separating control from data include the Linux Netlink as an IP Services Protocol[9] and A Path Computation Element (PCE)-Based Architecture.[10]
These early attempts failed to gain traction for two reasons. One is that many in the Internet community viewed separating control from data to be risky, especially owing to the potential for a failure in the control plane. The second is that vendors were concerned that creating standard application programming interfaces (APIs) between the control and data planes would result in increased competition.
The use of open source software in split control/data plane architectures traces its roots to the Ethane project at Stanford's computer sciences department. Ethane's simple switch design led to the creation of OpenFlow.[11] An API for OpenFlow was first created in 2008.[12] That same year witnessed the creation of NOX—an operating system for networks.[13]
Work on OpenFlow continued at Stanford, including with the creation of testbeds to evaluate use of the protocol in a single campus network, as well as across the WAN as a backbone for connecting multiple campuses.[14] In academic settings there were a few research and production networks based on OpenFlow switches from NEC and Hewlett-Packard; as well as based on Quanta Computer whiteboxes, starting from about 2009.[15]
Beyond academia, the first deployments were by Nicira in 2010 to control OVS from Onix, co-developed with NTT and Google.[16] A notable deployment was Google's B4 deployment in 2012.[17][18] Later Google acknowledged their first OpenFlow with Onix deployments in their Datacenters at the same time.[19] Another known large deployment is at China Mobile.[20]
The Open Networking Foundation was founded in 2011 to promote SDN and OpenFlow.
At the 2014 Interop and Tech Field Day, software-defined networking was demonstrated by Avaya using shortest path bridging (IEEE 802.1aq and OpenStack as an automated campus, extending automation from the data center to the end device, removing manual provisioning from service delivery.[21][22]
Concept[edit]
Software-defined networking (SDN) is an architecture purporting to be dynamic, manageable, cost-effective, and adaptable, seeking to be suitable for the high-bandwidth, dynamic nature of today's applications. SDN architectures decouple network control and forwarding functions, enabling network control to become directly programmable and the underlying infrastructure to be abstracted from applications and network services.[23]
The OpenFlow protocol can be used in SDN technologies. The SDN architecture is:
Directly programmable: Network control is directly programmable because it is decoupled from forwarding functions.
Agile: Abstracting control from forwarding lets administrators dynamically adjust network-wide traffic flow to meet changing needs.
Centrally managed: Network intelligence is (logically) centralized in software-based SDN controllers that maintain a global view of the network, which appears to applications and policy engines as a single, logical switch.
Programmatically configured: SDN lets network managers configure, manage, secure, and optimize network resources very quickly via dynamic, automated SDN programs, which they can write themselves because the programs do not depend on proprietary software.
Open standards-based and vendor-neutral: When implemented through open standards, SDN simplifies network design and operation because instructions are provided by SDN controllers instead of multiple, vendor-specific devices and protocols.
The need for a new network architecture[edit]
The explosion of mobile devices and content, server virtualization, and advent of cloud services are among the trends driving the networking industry to re-examine traditional network architectures.[24] Many conventional networks are hierarchical, built with tiers of Ethernet switches arranged in a tree structure. This design made sense when client-server computing was dominant, but such a static architecture is ill-suited to the dynamic computing and storage needs of today's enterprise data centers, campuses, and carrier environments.[25] Some of the key computing trends driving the need for a new network paradigm include:
Changing traffic patterns
Within the enterprise data center, traffic patterns have changed significantly. In contrast to client-server applications where the bulk of the communication occurs between one client and one server, today's applications access different databases and servers, creating a flurry of "east-west" machine-to-machine traffic before returning data to the end user device in the classic "north-south" traffic pattern. At the same time, users are changing network traffic patterns as they push for access to corporate content and applications from any type of device (including their own), connecting from anywhere, at any time. Finally, many enterprise data centers managers are contemplating a utility computing model, which might include a private cloud, public cloud, or some mix of both, resulting in additional traffic across the wide area network.
The "consumerization of IT"
Users are increasingly employing mobile personal devices such as smartphones, tablets, and notebooks to access the corporate network. IT is under pressure to accommodate these personal devices in a fine-grained manner while protecting corporate data and intellectual property and meeting compliance mandates.
The rise of cloud services
Enterprises have enthusiastically embraced both public and private cloud services, resulting in unprecedented growth of these services. Enterprise business units now want the agility to access applications, infrastructure, and other IT resources on demand and à la carte. To add to the complexity, IT's planning for cloud services must be done in an environment of increased security, compliance, and auditing requirements, along with business reorganizations, consolidations, and mergers that can change assumptions overnight. Providing self-service provisioning, whether in a private or public cloud, requires elastic scaling of computing, storage, and network resources, ideally from a common viewpoint and with a common suite of tools.
"Big data" means more bandwidth
Handling today's "big data" or mega datasets requires massive parallel processing on thousands of servers, all of which need direct connections to each other. The rise of mega datasets is fueling a constant demand for additional network capacity in the data center. Operators of hyperscale data center networks face the daunting task of scaling the network to previously unimaginable size, maintaining any-to-any connectivity without going broke.
Architectural components[edit]
A high-level overview of the software-defined networking architecture
The following list defines and explains the architectural components:[26]
SDN Application
SDN Applications are programs that explicitly, directly, and programmatically communicate their network requirements and desired network behavior to the SDN Controller via a northbound interface (NBI). In addition they may consume an abstracted view of the network for their internal decision-making purposes. An SDN Application consists of one SDN Application Logic and one or more NBI Drivers. SDN Applications may themselves expose another layer of abstracted network control, thus offering one or more higher-level NBIs through respective NBI agents.
SDN Controller
The SDN Controller is a logically centralized entity in charge of (i) translating the requirements from the SDN Application layer down to the SDN Datapaths and (ii) providing the SDN Applications with an abstract view of the network (which may include statistics and events). An SDN Controller consists of one or more NBI Agents, the SDN Control Logic, and the Control to Data-Plane Interface (CDPI) driver. Definition as a logically centralized entity neither prescribes nor precludes implementation details such as the federation of multiple controllers, the hierarchical connection of controllers, communication interfaces between controllers, nor virtualization or slicing of network resources.
SDN Datapath
The SDN Datapath is a logical network device that exposes visibility and uncontested control over its advertised forwarding and data processing capabilities. The logical representation may encompass all or a subset of the physical substrate resources. An SDN Datapath comprises a CDPI agent and a set of one or more traffic forwarding engines and zero or more traffic processing functions. These engines and functions may include simple forwarding between the datapath's external interfaces or internal traffic processing or termination functions. One or more SDN Datapaths may be contained in a single (physical) network element—an integrated physical combination of communications resources, managed as a unit. An SDN Datapath may also be defined across multiple physical network elements. This logical definition neither prescribes nor precludes implementation details such as the logical to physical mapping, management of shared physical resources, virtualization or slicing of the SDN Datapath, interoperability with non-SDN networking, nor the data processing functionality, which can include OSI layer 4-7 functions.
SDN Control to Data-Plane Interface (CDPI)
The SDN CDPI is the interface defined between an SDN Controller and an SDN Datapath, which provides at least (i) programmatic control of all forwarding operations, (ii) capabilities advertisement, (iii) statistics reporting, and (iv) event notification. One value of SDN lies in the expectation that the CDPI is implemented in an open, vendor-neutral and interoperable way.
SDN Northbound Interfaces (NBI)
SDN NBIs are interfaces between SDN Applications and SDN Controllers and typically provide abstract network views and enable direct expression of network behavior and requirements. This may occur at any level of abstraction (latitude) and across different sets of functionality (longitude). One value of SDN lies in the expectation that these interfaces are implemented in an open, vendor-neutral and interoperable way.
SDN Control Plane[edit]
Centralized - Hierarchical - Distributed
The implementation of the SDN control plane can follow a centralized, hierarchical, or decentralized design. Initial SDN control plane proposals focused on a centralized solution, where a single control entity has a global view of the network. While this simplifies the implementation of the control logic, it has scalability limitations as the size and dynamics of the network increase. To overcome these limitations, several approaches have been proposed in the literature that fall into two categories, hierarchical and fully distributed approaches. In hierarchical solutions,[27][28] distributed controllers operate on a partitioned network view, while decisions that require network-wide knowledge are taken by a logically centralized root controller. In distributed approaches,[29][30] controllers operate on their local view or they may exchange synchronization messages to enhance their knowledge. Distributed solutions are more suitable for supporting adaptive SDN applications.
Controller Placement
A key issue when designing a distributed SDN control plane is to decide on the number and placement of control entities. An important parameter to consider while doing so is the propagation delay between the controllers and the network devices,[31] especially in the context of large networks. Other objectives that have been considered involve control path reliability,[32] fault tolerance,[33] and application requirements.[34]
SDN flow forwarding (sdn)[edit]
Proactive vs Reactive vs Hybrid[35][36]
OpenFlow uses TCAM tables to route packet sequences (flows). If flows arrive at a switch, a flow table lookup is performed. Depending on the flow table implementation this is done in a software flow table if a vSwitch is used or in an ASIC if it's implemented in hardware. In the case when no matching flow is found, a request to the controller for further instructions is sent. This is handled in one of three different modes. In reactive mode the controller acts after these requests and creates and installs a rule in the flow table for the corresponding packet if necessary. In proactive mode the controller populates flow table entries for all possible traffic matches possible for this switch in advance. This mode can be compared with typical routing table entries today, where all static entries are installed ahead of time. Following this no request is sent to the controller since all incoming flows will find a matching entry. A major advantage in proactive mode is that all packets are forwarded in line rate (considering all flow table entries in TCAM) and no delay is added. The third mode, hybrid mode, follows the flexibility of a reactive mode for a set of traffic and the low-latency forwarding (proactive mode) for the rest of the traffic.
Applications[edit]
SDMN[edit]
Software-defined mobile networking (SDMN)[37][38] is an approach to the design of mobile networks where all protocol-specific features are implemented in software, maximizing the use of generic and commodity hardware and software in both the core network and radio access network.[39] It is proposed as an extension of SDN paradigm to incorporate mobile network specific functionalities.[40]
SD-WAN[edit]
An SD-WAN is a Wide Area Network (WAN) managed using the principles of software-defined networking.[41] The main driver of SD-WAN is to lower WAN costs using more affordable and commercially available leased lines, as an alternative or partial replacement of more expensive MPLS lines. Control and management is administered separately from the hardware with central controllers allowing for easier configuration and administration.[42]
SD-LAN[edit]
A SD-LAN is a Local area network (LAN) built around the principles of software-defined networking, though there are key differences in topology, network security, application visibility and control, management and quality of service.[43] SD-LAN decouples control management, and data planes to enable a policy driven architecture for wired and wireless LANs. SD-LANs are characterized by their use of a cloud management system and wireless connectivity without the presence of a physical controller.[44]
Security using the SDN paradigm[edit]
SDN architecture may enable, facilitate or enhance network-related security applications due to the controller's central view of the network, and its capacity to reprogram the data plane at any time. While security of SDN architecture itself remains an open question that has already been studied a couple of times in the research community,[45][46][47][48] the following paragraphs only focus on the security applications made possible or revisited using SDN.
Several research works on SDN have already investigated security applications built upon the SDN controller, with different aims in mind. Distributed Denial of Service (DDoS) detection and mitigation,[49][50] as well as botnet[51] and worm propagation,[52] are some concrete use-cases of such applications: basically, the idea consists in periodically collecting network statistics from the forwarding plane of the network in a standardized manner (e.g. using Openflow), and then apply classification algorithms on those statistics in order to detect any network anomalies. If an anomaly is detected, the application instructs the controller how to reprogram the data plane in order to mitigate it.
Another kind of security application leverages the SDN controller by implementing some moving target defense (MTD) algorithms. MTD algorithms are typically used to make any attack on a given system or network more difficult than usual by periodically hiding or changing key properties of that system or network. In traditional networks, implementing MTD algorithms is not a trivial task since it is difficult to build a central authority able of determining - for each part of the system to be protected - which key properties are hid or changed. In an SDN network, such tasks become more straightforward thanks to the centrality of the controller. One application can for example periodically assign virtual IPs to hosts within the network, and the mapping virtual IP/real IP is then performed by the controller.[53] Another application can simulate some fake opened/closed/filtered ports on random hosts in the network in order to add significant noise during reconnaissance phase (e.g. scanning) performed by an attacker.[54]
Additional value regarding security in SDN enabled networks can also be gained using FlowVisor[55] and FlowChecker[56] respectively. The former tries to use a single hardware forwarding plane sharing multiple separated logical networks. Following this approach the same hardware resources can be used for production and development purposes as well as separating monitoring, configuration and internet traffic, where each scenario can have its own logical topology which is called slice. In conjunction with this approach FlowChecker[55] realizes the validation of new OpenFlow rules that are deployed by users using their own slice.
SDN controller applications are mostly deployed in large-scale scenarios, which requires comprehensive checks of possible programming errors. A system to do this called NICE was described in 2012.[57] Introducing an overarching security architecture requires a comprehensive and protracted approach to SDN. Since it was introduced, designers are looking at possible ways to secure SDN that do not compromise scalability. One architecture called SN-SECA (SDN+NFV) Security Architecture.[58]
Group Data Delivery Using SDN[edit]
Distributed applications that run across datacenters usually replicate data for the purpose of synchronization, fault resiliency, load balancing and getting data closer to users (which reduces latency to users and increases their perceived throughput). Also, many applications, such as Hadoop, replicate data within a datacenter across multiple racks to increase fault tolerance and make data recovery easier. All of these operations require data delivery from one machine or datacenter to multiple machines or datacenters. The process of reliably delivering data from one machine to multiple machines is referred to as Reliable Group Data Delivery (RGDD).
SDN switches can be used for RGDD via installation of rules that allow forwarding to multiple outgoing ports. For example, OpenFlow provides support for Group Tables since version 1.1[59] which makes this possible. Using SDN, a central controller can carefully and intelligently setup forwarding trees for RGDD. Such trees can be built while paying attention to network congestion/load status to improve performance. For example, MCTCP[60] is a scheme for delivery to many nodes inside datacenters that relies on regular and structured topologies of datacenter networks while DCCast[61] and QuickCast[62] are approaches for fast and efficient data and content replication across datacenters over private WANs.
See also[edit]
Computer networking portal
Active networking
Frenetic (programming language)
IEEE 802.1aq
Intel Data Plane Development Kit (DPDK)
List of SDN controller software
Network functions virtualization
ONOS
OpenDaylight Project
SD-WAN
Software-defined data center
Software-defined mobile network
Software-defined protection
References[edit]
Jump up ^ Benzekki Kamal et al.Software‐defined networking (SDN): a survey., Security and Communication Networks 9, no. 18 (2016): 5803-5833.
Jump up ^ Benzekki Kamal et al.Devolving IEEE 802.1 X authentication capability to data plane in software‐defined networking (SDN) architecture., Security and Communication Networks 9.17 (2016): 4369-4377.
Jump up ^ Benzekki Kamal et al Software‐defined networking (SDN): a survey., Security and Communication Networks 9, no. 18 (2016): 5803-5833.
Jump up ^ "Software-defined networking is not OpenFlow, companies proclaim". searchsdn.techtarget.com.
Jump up ^ http://searchsdn.techtarget.com/guides/Guide-OpenFlow-SDN-not-the-only-show-in-town-for-vendors. Missing or empty |title= (help)
Jump up ^ "Predicting SD-WAN Adoption". gartner.com. 2015-12-15. Retrieved 2016-06-27.
Jump up ^ L. Yang (Intel Corp.), R. Dantu (Univ. of North Texas), T. Anderson (Intel Corp.) & R. Gopal (Nokia.) (April 2004). "Forwarding and Control Element Separation (ForCES) Framework". CS1 maint: Multiple names: authors list (link)
Jump up ^ T. V. Lakshman, T. Nandagopal, R. Ramjee, K. Sabnani, and T. Woo (Nov 2004). "The SoftRouter Architecture" (PDF). CS1 maint: Multiple names: authors list (link)
Jump up ^ J. Salim (Znyx Networks), H. Khosravi (Intel), A. Kleen (Suse), and A. Kuznetsov (INR/Swsoft) (July 2003). "Linux Netlink as an IP Services Protocol". CS1 maint: Multiple names: authors list (link)
Jump up ^ A. Farrel (Old Dog Consulting), J. Vasseur (Cisco Systems, Inc.), and J. Ash (AT&T) (August 2006). "A Path Computation Element (PCE)-Based Architecture". CS1 maint: Multiple names: authors list (link)
Jump up ^ Martìn Casado, Michael J. Freedman, Justin Pettit, Jianying Luo, and Nick McKeown (Stanford University) (August 2007). "Ethane: Taking Control of the Enterprise" (PDF). CS1 maint: Multiple names: authors list (link)
Jump up ^ N. McKeown, T. Anderson, H. Balakrishnan, G. Parulkar, L. Peterson, J. Rexford, S. Shenker, and J. Turner. (April 2008). "OpenFlow: Enabling Innovation in Campus Networks" (PDF). CS1 maint: Multiple names: authors list (link)
Jump up ^ N. Gude, T. Koponen, J. Pettit, B. Pfaff, M. Casado, N. McKeown, and S. Shenker. (July 2008). "NOX: Towards an Operating System for Networks" (PDF). CS1 maint: Multiple names: authors list (link)
Jump up ^ "GENI. Campus OpenFlow topology". 2011.
Jump up ^ Kuang-Ching “KC” Wang (Oct 3, 2011). "Software Defined Networking and OpenFlow for Universities: Motivation, Strategy, and Uses" (PDF).
Jump up ^ "What are SDN Controllers (or SDN Controllers Platforms)?".
Jump up ^ Sushant Jain, Alok Kumar, Subhasree Mandal, Joon Ong, Leon Poutievski, Arjun Singh, Subbaiah Venkata, Jim Wanderer, Junlan Zhou, Min Zhu, Jonathan Zolla, Urs Hölzle, Stephen Stuart and Amin Vahdat (Google) (August 12–16, 2013). "B4: Experience with a Globally-Deployed Software Defined WAN" (PDF). CS1 maint: Multiple names: authors list (link)
Jump up ^ brent salisbury (May 14, 2013). "Inside Google's Software-Defined Network".
Jump up ^ Arjun Singh, Joon Ong, Amit Agarwal, Glen Anderson, Ashby Armistead, Roy Bannon, Seb Boving, Gaurav Desai, Bob Felderman, Paulie Germano, Anand Kanagala, Jeff Provost, Jason Simmons, Eiichi Tanda, Jim Wanderer, Urs Hölzle, Stephen Stuart, Amin Vahdat (2015). "Jupiter Rising: A Decade of Clos Topologies and Centralized Control in Google's Datacenter Network". CS1 maint: Multiple names: authors list (link)
Jump up ^ ""MPLS-TP OpenFlow Protocol Extensions for SPTN" becomes a formal ONF standard by unanimous approval". June 27, 2017.
Jump up ^ Camille Campbell (February 6, 2014). "Avaya Debuts Networking Innovations at 'Tech Field Day'".
Jump up ^ Elizabeth Miller Coyne (September 23, 2016). "Huawei Exec: SDN's Become a 'Completely Meaningless Term'".
Jump up ^ "Software-Defined Networking (SDN) Definition". Opennetworking.org. Retrieved 26 October 2014.
Jump up ^ "White Papers". Opennetworking.org. Retrieved 26 October 2014.
Jump up ^ Montazerolghaem, Ahmadreza.; Yaghmaee, M. H.; Leon-Garcia, A. (2017). "OpenSIP: Toward Software-Defined SIP Networking". IEEE Transactions on Network and Service Management. PP (99): 1–1. doi:10.1109/tnsm.2017.2741258. ISSN 1932-4537.
Jump up ^ "SDN Architecture Overview" (PDF). Opennetworking.org. Retrieved 22 November 2014.
Jump up ^ S.H. Yeganeh, Y. Ganjali, "Kandoo: A Framework for Efficient and Scalable Offloading of Control Applications," proceedings of HotSDN, Helsinki, Finland, 2012.
Jump up ^ R. Ahmed, R. Boutaba, "Design considerations for managing wide area software defined networks," Communications Magazine, IEEE, vol. 52, no. 7, pp. 116–123, July 2014.
Jump up ^ T. Koponen et al, "Onix: A Distributed Control Platform for Large scale Production Networks," proceedings USENIX, ser. OSDI’10, Vancouver, Canada, 2010.
Jump up ^ D. Tuncer, M. Charalambides, S. Clayman, G. Pavlou, "Adaptive Resource Management and Control in Software Defined Networks," Network and Service Management, IEEE Transactions on, vol. 12, no. 1, pp. 18–33, March 2015.
Jump up ^ B. Heller, R. Sherwood, and N. McKeown, "The Controller Placement Problem," proceedings of HotSDN’12, 2012.
Jump up ^ Y.N. Hu, W.D. Wang, X.Y. Gong, X.R. Que, S.D. Cheng, "On the placement of controllers in software-defined networks," Journal of China Universities of Posts and Telecommunications, vol. 19, Supplement 2, no. 0, pp. 92 – 171, 2012.
Jump up ^ F.J. Ros, P.M. Ruiz, "Five nines of southbound reliability in software defined networks," proceedings of HotSDN’14, 2014.
Jump up ^ D. Tuncer, M. Charalambides, S. Clayman, G. Pavlou, "On the Placement of Management and Control Functionality in Software Defined Networks," proceedings of 2nd IEEE International Workshop on Management of SDN and NFV Systems (ManSDN/NFV), Barcelona, Spain, November 2015.
Jump up ^ "OpenFlow: Proactive vs Reactive". NetworkStatic.net. Retrieved 2014-07-01.
Jump up ^ "Reactive, Proactive, Predictive: SDN Models | F5 DevCentral". Devcentral.f5.com. Retrieved 2016-06-30.
Jump up ^ Kostas Pentikousis, Yan Wang, Weihua Hu, MobileFlow: Toward Software-Defined Mobile Networks, Communications Magazine, IEEE, vol. 51, no. 7, pp. 44–53, July 2013.
Jump up ^ Liyanage, Madhusanka (2015). Software Defined Mobile Networks (SDMN): Beyond LTE Network Architecture. UK: John Wiley. pp. 1–438. ISBN 978-1-118-90028-4.
Jump up ^ Jose Costa-Requena, Jesús Llorente Santos, Vicent Ferrer Guasch, Kimmo Ahokas, Gopika Premsankar, Sakari Luukkainen, Ijaz Ahmed, Madhusanka Liyanage, Mika Ylianttila, Oscar López Pérez, Mikel Uriarte Itzazelaia, Edgardo Montes de Oca, SDN and NFV Integration in Generalized Mobile Network Architecture , in Proc. of European Conference on Networks and Communications (EUCNC), Paris, France. June 2015.
Jump up ^ Madhusanka Liyanage, Mika Ylianttila, Andrei Gurtov, Securing the Control Channel of Software-Defined Mobile Networks , in Proc. of IEEE 15th International Symposium on World of Wireless, Mobile and Multimedia Networks (WoWMoM), Sydney, Australia. June 2014.
Jump up ^ Haranas, Mark (8 October 2016). "16 Hot Networking Products Putting The Sizzle In SD-WAN". CRN. Retrieved 1 November 2016.
Jump up ^ "SD-WAN: What it is and why you'll use it one day". networkworld.com. 2016-02-10. Retrieved 2016-06-27.
Jump up ^ Serries, William (12 September 2016). "SD-LAN et SD-WAN : Deux Approches Différentes pour le Software Defined Networking". ZDNet. Retrieved 1 November 2016.
Jump up ^ Kerravala, Zeus (13 September 2016). "Aerohive Introduces the Software-defined LAN". Network World. Retrieved 1 November 2016.
Jump up ^ Kreutz, Diego; Ramos, Fernando; Verissimo, Paulo (2013). "Towards secure and dependable software-defined networks". Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking. pp. 50–60.
Jump up ^ Scott-Hayward, Sandra; O'Callaghan, Gemma; Sezer, Sakir (2013). "SDN security: A survey". Future Networks and Services (SDN4FNS), 2013 IEEE SDN for. pp. 1–7.
Jump up ^ Benton, Kevin; Camp, L Jean; Small, Chris (2013). "Openflow vulnerability assessment". Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking. pp. 151–152.
Jump up ^ Abdou, AbdelRahman; van Oorschot, Paul; Wan, Tao (May 2018). "A Framework and Comparative Analysis of Control Plane Security of SDN and Conventional Networks". IEEE Communications Surveys and Tutorials. IEEE. "to appear".
Jump up ^ Giotis, K; Argyropoulos, Christos; Androulidakis, Georgios; Kalogeras, Dimitrios; Maglaris, Vasilis (2014). "Combining OpenFlow and sFlow for an effective and scalable anomaly detection and mitigation mechanism on SDN environments". Computer Networks. 62: 122–136. doi:10.1016/j.bjp.2013.10.014.
Jump up ^ Braga, Rodrigo; Mota, Edjard; Passito, Alexandre (2010). "Lightweight DDoS flooding attack detection using NOX/OpenFlow". Local Computer Networks (LCN), 2010 IEEE 35th Conference on. pp. 408–415.
Jump up ^ Feamster, Nick (2010). "Outsourcing home network security". Proceedings of the 2010 ACM SIGCOMM workshop on Home networks. pp. 37–42.
Jump up ^ Jin, Ruofan & Wang, Bing (2013). "Malware detection for mobile devices using software-defined networking". Research and Educational Experiment Workshop (GREE), 2013 Second GENI. 81-88.
Jump up ^ Jafarian, Jafar Haadi; Al-Shaer, Ehab; Duan, Qi (2012). "Openflow random host mutation: transparent moving target defense using software defined networking". Proceedings of the first workshop on Hot topics in software defined networks. pp. 127–132.
Jump up ^ Kampanakis, Panos; Perros, Harry; Beyene, Tsegereda. SDN-based solutions for Moving Target Defense network protection (PDF). Retrieved 23 July 2014.
^ Jump up to: a b Sherwood, Rob; Gibb, Glen; Yap, Kok-Kiong; Appenzeller, Guido; Casado, Martin; McKeown, Nick; Parulkar, Guru (2009). "Flowvisor: A network virtualization layer". OpenFlow Switch Consortium, Tech. Rep.
Jump up ^ Al-Shaer, Ehab & Al-Haj, Saeed (2010). "FlowChecker: Configuration analysis and verification of federated OpenFlow infrastructures". Proceedings of the 3rd ACM workshop on Assurable and usable security configuration. pp. 37–44.
Jump up ^ Canini, Marco; Venzano, Daniele; Peresini, Peter; Kostic, Dejan; Rexford, Jennifer; et al. (2012). A NICE Way to Test OpenFlow Applications. NSDI. pp. 127–140.
Jump up ^ Bernardo and Chua (2015). Introduction and Analysis of SDN and NFV Security Architecture (SA-SECA). 29th IEEE AINA 2015. pp. 796–801.
Jump up ^ B. Pfaf; et al. (February 28, 2011). "OpenFlow Switch Specification" (PDF). Retrieved July 8, 2017. CS1 maint: Explicit use of et al. (link)
Jump up ^ T. Zhu; et al. (October 18, 2016). "MCTCP: Congestion-aware and robust multicast TCP in Software-Defined networks". IEEE. Retrieved July 3, 2017. CS1 maint: Explicit use of et al. (link)
Jump up ^ M. Noormohammadpour; et al. (July 10, 2017). "DCCast: Efficient Point to Multipoint Transfers Across Datacenters". USENIX. Retrieved July 3, 2017. CS1 maint: Explicit use of et al. (link)
Jump up ^ M. Noormohammadpour; et al. (2018). "QuickCast: Fast and Efficient Inter-Datacenter Transfers using Forwarding Tree Cohorts". Retrieved January 23, 2018. CS1 maint: Explicit use of et al. (link)
Nadeau, Thomas D.; Gray, W. Ken. SDN: Software Defined Networks. ISBN 1-449342302.
External links[edit]
Open Networking Foundation's definition of SDN
Coursera Course on SDN, by Nick Feamster
OpenFlow-enabled SDN and Network Functions Virtualization
SDN Security Considerations in the Data Center
Floodlight, an open source Java based OpenFlow controller
Network Function Virtualization (NFV)
Decoding SDN
Software-defined networking (SDN) for the non-technical
Operational Opportunities and Challenges of SDN/NFV Programmable Infrastructure – a report from the ATIS Technology and Operations Council
What is Software Defined Networking – an introduction
Cherry, an open source OpenFlow controller written in Go
Faucet, an open source OpenFlow controller written in Python based on Ryu for Production networks
Retrieved from "https://en.wikipedia.org/w/index.php?title=Software-defined_networking&oldid=846254734"
Categories:
Configuration management
Emerging technologies
Network architecture
Hidden categories:
Pages with citations lacking titles
Pages with citations having bare URLs
CS1 maint: Multiple names: authors list
CS1 maint: Explicit use of et al.
Articles needing POV-check from August 2014
Articles needing additional references from November 2014
All articles needing additional references
Articles with multiple maintenance issues
Wikipedia articles needing rewrite from August 2015
All articles needing rewrite
Accuracy disputes from November 2016
All accuracy disputes
Pages using div col with deprecated parameters
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
العربية
Deutsch
Español
فارسی
Français
한국어
Bahasa Indonesia
Italiano
עברית
മലയാളം
Монгол
日本語
Polski
Português
Русский
Українська
中文
8 more
Edit links
This page was last edited on 17 June 2018, at 13:44.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

key: html

type: local

value: div

attrs: id class

values: mw-page-base noprint

values: mw-head-base noprint

value: a

attrs: id class lang

values: firstHeading firstHeading en

values: siteSub noprint

attrs: class href

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

attrs: href title

attrs: role class

values:
note
hatnote navigation-not-searchable

value: img

attrs: alt src width height srcset data-file-width data-file-height

value: td

value: span

attrs: class role tabindex

value: b

value: i

value: small

values:
plainlinks metadata ambox ambox-content
presentation

values: Help:Introduction to referencing with Wiki Markup/1

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values:
mw-collapsible mw-made-collapsible
width:95%; margin: 0.2em 0;

values: plainlinks metadata ambox ambox-content ambox-multiple_issues compact-ambox

values: plainlinks metadata ambox ambox-content ambox-disputed

values: Edit section: The need for a new network architecture

attrs: alt src width height class srcset data-file-width data-file-height

values:
/wiki/Core_network
mw-redirect
Core network

values:
/wiki/Wide_Area_Network
mw-redirect
Wide Area Network

values: Edit section: Security using the SDN paradigm

values: Edit section: Group Data Delivery Using SDN

values:
/wiki/Portal:Computer_networking
mw-redirect
Portal:Computer networking

values: display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle

values: margin:0.5em 0 0.5em 1em;border:solid #aaa 1px

values:
/wiki/Intel_Data_Plane_Development_Kit
mw-redirect
Intel Data Plane Development Kit

values:
/wiki/Network_functions_virtualization
mw-redirect
Network functions virtualization

values: -moz-column-width: 22em; -webkit-column-width: 22em; column-width: 22em;

values:
nofollow
external text
https://tools.ietf.org/html/rfc3746

values: Category:CS1 maint: Multiple names: authors list

values:
nofollow
external text
https://tools.ietf.org/html/rfc3549

values:
nofollow
external text
https://tools.ietf.org/html/rfc4655

values:
nofollow
external text
https://benpfaff.org/papers/nox.pdf

values:
nofollow
external text
//doi.org/10.1109%2Ftnsm.2017.2741258

values:
nofollow
external text
//www.worldcat.org/issn/1932-4537

values:
nofollow
external text
//doi.org/10.1016%2Fj.bjp.2013.10.014

values:
nofollow
external text
http://www4.ncsu.edu/~hp/Panos.pdf

values: Category:CS1 maint: Explicit use of et al.

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values:
nofollow
external text
https://www.coursera.org/learn/sdn

values:
nofollow
https://github.com/superkkt/cherry/
external text

values:
nofollow
https://github.com/onfsdn/faucet/
external text

values: Category:Pages with citations lacking titles

values: Category:Pages with citations having bare URLs

values: Category:Articles needing POV-check from August 2014

values: Category:Articles needing additional references from November 2014

values: Category:All articles needing additional references

values: Category:Articles with multiple maintenance issues

values: Category:Wikipedia articles needing rewrite from August 2015

values: Category:Accuracy disputes from November 2016

values: Category:Pages using div col with deprecated parameters

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Software-defined_networking
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values: الشبكات المعرفة بالبرمجيات – Arabic

values: شبکه نرم‌افزارمحور – Persian

values:
interlanguage-link interwiki-fa
display: none;

values: 소프트웨어 정의 네트워킹 – Korean

values:
interlanguage-link interwiki-ko
display: none;

values: Software-defined networking – Indonesian

values:
interlanguage-link interwiki-it
display: none;

values:
interlanguage-link interwiki-he
display: none;

values: സോഫ്റ്റ്‌വെയർ അധിഷ്ഠിത ശൃംഖല – Malayalam

values:
interlanguage-link interwiki-ml
display: none;

values:
https://mn.wikipedia.org/wiki/SDN
SDN – Mongolian
mn
mn
interlanguage-link-target

values:
interlanguage-link interwiki-mn
display: none;

values:
interlanguage-link interwiki-pl
display: none;

values: Software defined networking – Portuguese

values: Программно-определяемая сеть – Russian

values: Програмно-конфігурована мережа – Ukrainian

values:
interlanguage-link interwiki-uk
display: none;

values: 軟體定義網路 – Chinese

values: All languages (initial selection from common choices by you and others)

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Software-defined_networking rootpage-Software-defined_networking skin-vector action-view