Key Points
References
| Reference_description_with_linked_URLs____________________________ | Notes_____________________________________________________________ |
|---|---|
| m TCP Networks | |
Key Concepts
TCP/IP
HTTPS
FTP
SSH
DNS
DHCP
LDAP
Proxy Servers - HTTPS vs SOCKS
http://www.jguru.com/faq/view.jsp?EID=227532
A SOCKS server is a general purpose proxy server that establishes a TCP connection to another server on behalf of a client, then routes all the traffic back and forth between the client and the server. It works for any kind of network protocol on any port. SOCKS Version 5 adds additional support for security and UDP. The SOCKS server does not interpret the network traffic between client and server in any way, and is often used because clients are behind a firewall and are not permitted to establish TCP connections to servers outside the firewall unless they do it through the SOCKS server. Most web browsers for example can be configured to talk to a web server via a SOCKS server. Because the client must first make a connection to the SOCKS server and tell it the host it wants to connect to, the client must be "SOCKS enabled." On Windows, it is possible to "shim" the TCP stack so that all client software is SOCKS enabled. A free SOCKS shim is available from Hummingbird at http://www.hummingbird.com/products/nc/socks/index.html.
An HTTP proxy is similar, and may be used for the same purpose when clients are behind a firewall and are prevented from making outgoing TCP connections to servers outside the firewall. However, unlike the SOCKS server, an HTTP proxy does understand and interpret the network traffic that passes between the client and downstream server, namely the HTTP protocol. Because of this the HTTP proxy can ONLY be used to handle HTTP traffic, but it can be very smart about how it does it. In particular, it can recognize often repeated requests and cache the replies to improve performance. Many ISPs use HTTP proxies regardless of how the browser is configured because they simply route all traffic on port 80 through the proxy server.
Other Protocols
SD-WAN Concepts
SD-WAN Topology Whitepaper. link
SD-WAN_Topology_Whitepaper.pdf. file
1. Introduction
2. Why is the Network Architecture Important?
3. Right Network Architecture = Right Kind of Application Performance
4. Understanding the Basic Fabrics: Public vs Private
5. The Traditional Internet
6. Multiprotocol Label Switching
7. SD-WAN: The Next Chapter
8. Which is the Right One For You?
9. Aryaka: Fly Business Class Over the Middle-Mile
10. Litmus Test
11. Litmus Test Results
12. The Aryaka Difference
13. Conclusions
End point address: IP address, MPLS, SD
MPLS = Multiprotocol Label Switching is a routing technique in telecommunications networks that directs data from one node to the next based on labels rather than network addresses. Whereas network addresses identify endpoints, the labels identify established paths between endpoints.
Enterprise networks carry a varied range of traffic, such as video, voice, and data. Each one of these traffic classes has its own set of performance requirements and traffic characteristics. A wisely carved out network framework places the right elements to facilitate sufficient resources to each traffic class in order to guarantee the required quality-of-service (QoS) and incremental performance improvements.
A Hybrid WAN architecture for example, combines broadband and MPLS, allowing network managers to keep mission critical traffic on the MPLS network and offload best effort traffic like e-mail and remote backups. This is certainly a better use of bandwidth than running everything over the MPLS network.
SD-WAN - combines all protcols, traffic into a single software-defined flexible appliance including routing, security, firewall for a single control plane
r>> users going to cloud platforms more than data center now
v>> independent of the ISP so you can mix providers as needed, where needed
v>> mix protocols including wireless for failure if needed
f>> QOS controlled well in private net but SD-WAN has dynamic QOS optimization services that normally do well for MOST use cases on latency
h>> migrate apps to SD-WAN as needed moving P2P
SDN, SD-WAN, & SD-Access Simplified... Seriously!
https://www.youtube.com/watch?v=dE7VUuXJs0k
Introduction to Software Defined Technologies: The video introduces software-defined technologies, including Software-Defined Networking (SDN), Software-Defined WAN (SD-WAN), and Software-Defined Access (SD-Access), discussing their roles and components in Cisco's solutions.
Traditional Networking Devices: Discusses traditional networking devices like routers and switches, which operate on three planes: data plane (handling data forwarding), control plane (running algorithms like OSPF or spanning tree protocol), and management plane (for configuration and administration).
Shift to SDN: SDN represents a shift from traditional networking, moving from a distributed control plane, where each device has its own control plane, to a centralized model where the control plane is managed by an SDN controller.
Role of APIs in SDN: Emphasizes the use of Application Programming Interfaces (APIs) in SDN, particularly southbound interfaces (SBIs) for communication between the controller and devices, and northbound interfaces (NBIs) for communication between the controller and applications.
Intent-Based Networking: Highlights the concept of intent-based networking in SDN, allowing administrators to express network intentions through applications rather than configuring each device individually.
Cisco's SDN Solutions: Distinguishes Cisco's SDN solutions in different contexts: Cisco APIC (Application Policy Infrastructure Controller) in data centers as part of Cisco's ACI (Application Centric Infrastructure) and Cisco DNA Center for enterprise networks.
SD-WAN Overview: Introduces SD-WAN, noting its advantages over traditional WAN by creating virtual, secure, and efficient overlay networks, thus overcoming inefficiencies like backhauling through a headquarters or data center.
Cisco’s Viptela-Based SD-WAN Solution: Cisco's SD-WAN solution, based on technology from their Viptela acquisition, includes components like vSmart for centralized control and vBond for network orchestration and zero-touch provisioning.
SD-WAN Network Infrastructure: Details the structure of SD-WAN networks, distinguishing between the physical underlay network and the virtual overlay network, with secure IPsec tunnels forming the data plane.
SD-Access as ACL Replacement: Describes SD-Access as an advancement over traditional access control lists (ACLs), enabling more dynamic policy enforcement using security groups and identities, irrespective of physical location.
Cisco's SD Access Architecture: Breaks down Cisco's SD Access solution into layers, starting from the physical layer (infrastructure devices) up to the management layer, indicating its comprehensive approach to network management.
Closing Remarks and Learning Opportunities: Concludes with a reminder of the educational opportunities available for learning more about these technologies, encouraging viewers to explore further through Cisco's training courses.
WAN Security Concepts
Unifying_Security_WAN_and_Ops_HP_WP_4AA4_2697_US.pdf link
Unifying_Security_WAN_and_Ops_HP_WP_4AA4_2697_US.pdf file
Cellular - 4G, 5G, 6G, 7G
5G concepts, value
6G concepts, value
https://en.wikipedia.org/wiki/6G_(network)
https://www.techtarget.com/searchnetworking/definition/6G
7G concepts
Compared to 6G, 7G is designed to do the following:
- deliver data up to 46 Gbps -- nearly five times the rate of 6G projections;
- double the size of the channel to 320 MHz; and
- afford 16 spatial streams, compared to eight in 6G.
LoRaWan
https://lora-alliance.org/resource-hub/what-lorawanr
Helium
https://www.techradar.com/news/building-the-worlds-first-peer-to-peer-wireless-network
a blockchain protocol for p2p data sharing over LoRaWan
As the number of IoT devices continues to grow, keeping them all connected to the internet in an affordable way has proven difficult which is why Napster’s Co-creator Shawn Fanning, Sproutling founder Chris Bruce and Amir Haleem set out to build the word’s first peer-to-peer wireless network. Their company, Helium has created its own hotspot that is used to power the People’s Network. In addition to providing IoT devices with connectivity, the Helium hotspot also rewards its users with a new cryptocurrency that can be used to offset the initial cost of the device.
To learn more about the Helium hotspot and the peer-to-peer wireless network it powers, TechRadar Pro spoke with Helium’s CEO Amir Haleem.
- Education gets smart: how the IoT is changing our schools
- PayPal might offer cryptocurrency transactions for its 325 million users soon
- These are the best wireless routers available today
What inspired you and Helium’s other co-founders to create the world’s first peer-to-peer wireless network?
We had a few friends that were building hardware businesses. Everything from counting foot traffic in retail buildings, to connected baby monitors.
They all had the same problem when it came to getting data back to the internet - either you needed a phone nearby, or the sensor itself needed a cellular plan. It was pretty impossible to scale any kind of sensor-based business when the cellular connectivity alone was going to cost $30/mo or more per sensor. What was needed was a low-cost and energy efficient network that was designed specifically for these sub-voice devices, like sensors.
Shawn and I decided to find a way to remove these barriers and this ultimately led us to start building The People’s Network - a low-cost network for IoT that works everywhere, even outdoors.
Who is your target market? What kind of customers will be able to benefit from these products?
Helium is very much like Airbnb or Lyft. We have created a two-sided market. On the supply side, Helium Hotspot owners could be anyone with Internet access at home. We call them Hotspot Hosts or members of The People’s Network. They own and operate the Helium Hotspots themselves, which means they provide wireless coverage for IoT devices surrounding them using LongFi technology.
LongFi combines the popular LoRaWAN open wireless standard with the Helium blockchain. The Helium Hotspot also serves as a full node of the blockchain, and mines the Helium cryptocurrency (HNT) for proving its location and coverage to the network. The Helium blockchain is the engine that drives both the health of the network and the economic system that makes both sides of the marketplace work.
The demand side of our business are users who benefit from the network. This ranges from IoT hobbyists to large corporations with the need to connect small sensors to the internet. Some examples of companies who are already enjoying the benefits of our network include beverage delivery service company Nestle’s ReadyRefresh, agricultural tech company Agulus, and Conserv, a collections-focused environmental monitoring platform that provides widespread coverage to art and cultural collections to its clients.
Potential Value Opportunities
Potential Challenges
Candidate Solutions
Step-by-step guide for Example
sample code block