Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches for end users. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and FTTX. It also discusses more advanced multihoming options using BGP with independently assigned IP addresses to achieve redundancy and connection resiliency without requiring end users to manage BGP protocols or obtain their own IP blocks. Simpler approaches that maintain benefits without those requirements are preferable.
This document outlines test scenarios for 4-byte autonomous system numbers (ASNs) in BGP. It discusses: 1) an overview of 4-byte ASNs including the original 2-byte encoding and expanded 4-byte encoding; 2) BGP capabilities for advertising support of 4-byte ASNs; 3) updates to the AS_PATH and AS_AGGREGATOR attributes to support 4-byte ASNs; 4) new optional AS4_PATH and AS4_AGGREGATOR attributes to carry 4-byte ASNs; and 5) proposed test scenarios involving different combinations of 2-byte and 4-byte ASNs traveling through each other and being aggregated.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and how new technologies like FTTX are replacing older ones. It also discusses more robust multihoming options that maintain redundancy and balance traffic across connections without requiring BGP or own IP blocks. The preferred approaches provide benefits like lower cost and complexity while preserving resiliency.
The document summarizes suggestions for migrating to 4-byte AS numbers in BGP. It discusses upgrading routers in a network in stages, beginning with either border routers, route reflectors, or iBGP clients. While this approach is acceptable, operational issues still need to be considered, such as how to handle AS paths if a border router does not support 4-byte AS numbers. The document provides examples of different upgrading strategies and considerations for various common BGP configurations.
FEGTS IP Training - Network Diagnostic IntroductionKae Hsu
This document provides an agenda and overview for an IP network diagnostic training session. The training will cover network diagnostic concepts, hostname resolution verification using nslookup and dig, network connection verification using ping and traceroute, and application condition verification. It includes examples of using these tools and concepts like ICMP packets, TTL, and troubleshooting network reachability. The goal is for students to understand basic network troubleshooting principles and tools.
How To Process And Solve Network Security In ISPKae Hsu
This document discusses security issues and solutions for Internet service providers (ISPs). It covers:
1. Implementing security on the control plane and data plane from both physical and logical positions. This includes securing routers, routing information, and event logging.
2. Examples of control plane security include router access control lists, authenticated routing protocols, route validation databases, and limiting route prefixes.
3. Data plane security focuses on preventing unauthorized packet flows and denial of service attacks on the ISP network.
This document summarizes the history of bots and botnets, how botnets are controlled and used for criminal activities like DDoS attacks and spamming, and the large harms they cause. It discusses how botnets can include millions of compromised systems and generate huge amounts of attack traffic to bring down websites. The document also outlines approaches for detecting and mitigating botnets, including using darknets and honeypots to analyze anomalous traffic and identify infected systems.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches for end users. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and FTTX. It also discusses more advanced multihoming options using BGP with independently assigned IP addresses to achieve redundancy and connection resiliency without requiring end users to manage BGP protocols or obtain their own IP blocks. Simpler approaches that maintain benefits without those requirements are preferable.
This document outlines test scenarios for 4-byte autonomous system numbers (ASNs) in BGP. It discusses: 1) an overview of 4-byte ASNs including the original 2-byte encoding and expanded 4-byte encoding; 2) BGP capabilities for advertising support of 4-byte ASNs; 3) updates to the AS_PATH and AS_AGGREGATOR attributes to support 4-byte ASNs; 4) new optional AS4_PATH and AS4_AGGREGATOR attributes to carry 4-byte ASNs; and 5) proposed test scenarios involving different combinations of 2-byte and 4-byte ASNs traveling through each other and being aggregated.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and how new technologies like FTTX are replacing older ones. It also discusses more robust multihoming options that maintain redundancy and balance traffic across connections without requiring BGP or own IP blocks. The preferred approaches provide benefits like lower cost and complexity while preserving resiliency.
The document summarizes suggestions for migrating to 4-byte AS numbers in BGP. It discusses upgrading routers in a network in stages, beginning with either border routers, route reflectors, or iBGP clients. While this approach is acceptable, operational issues still need to be considered, such as how to handle AS paths if a border router does not support 4-byte AS numbers. The document provides examples of different upgrading strategies and considerations for various common BGP configurations.
FEGTS IP Training - Network Diagnostic IntroductionKae Hsu
This document provides an agenda and overview for an IP network diagnostic training session. The training will cover network diagnostic concepts, hostname resolution verification using nslookup and dig, network connection verification using ping and traceroute, and application condition verification. It includes examples of using these tools and concepts like ICMP packets, TTL, and troubleshooting network reachability. The goal is for students to understand basic network troubleshooting principles and tools.
How To Process And Solve Network Security In ISPKae Hsu
This document discusses security issues and solutions for Internet service providers (ISPs). It covers:
1. Implementing security on the control plane and data plane from both physical and logical positions. This includes securing routers, routing information, and event logging.
2. Examples of control plane security include router access control lists, authenticated routing protocols, route validation databases, and limiting route prefixes.
3. Data plane security focuses on preventing unauthorized packet flows and denial of service attacks on the ISP network.
This document summarizes the history of bots and botnets, how botnets are controlled and used for criminal activities like DDoS attacks and spamming, and the large harms they cause. It discusses how botnets can include millions of compromised systems and generate huge amounts of attack traffic to bring down websites. The document also outlines approaches for detecting and mitigating botnets, including using darknets and honeypots to analyze anomalous traffic and identify infected systems.
This document summarizes a presentation on supporting IPv6 with software defined networking (SDN) and network functions virtualization (NFV). It defines SDN as separating the control plane and data plane in networks to allow for programmable, automated configuration changes. OpenFlow is described as an SDN protocol. NFV aims to virtualize network functions to run on virtual machines. Current carrier-grade NAT (CGNAT) solutions are hardware-based, while SDN/NFV could allow for a virtualized CGNAT with benefits like dynamic load adjustment and disaster recovery. The future of networking is predicted to involve open source SDN controllers and virtual switches running on commercial and open source platforms.
The document discusses CDNs and their evolution. It describes how early CDNs used server farms and caching to improve performance. Modern CDNs now use global server load balancing to distribute content across many locations worldwide. CDNs work by caching content at edge servers close to users to improve response times. This raises issues for ISPs, as DNS responses and traffic patterns may be impacted. The document considers both challenges CDNs pose for ISPs and potential aggressive strategies ISPs could employ to handle CDN traffic.
This document summarizes a presentation on supporting IPv6 with software defined networking (SDN) and network functions virtualization (NFV). It defines SDN as separating the control plane and data plane in networks to allow for programmable, automated configuration changes. OpenFlow is described as an SDN protocol. NFV aims to virtualize network functions to run on virtual machines. Current carrier-grade NAT (CGNAT) solutions are hardware-based, while SDN/NFV could allow for a virtualized CGNAT with benefits like dynamic load adjustment and disaster recovery. The future of networking is predicted to involve open source SDN controllers and virtual switches running on commercial and open source platforms.
The document discusses CDNs and their evolution. It describes how early CDNs used server farms and caching to improve performance. Modern CDNs now use global server load balancing to distribute content across many locations worldwide. CDNs work by caching content at edge servers close to users to improve response times. This raises issues for ISPs, as DNS responses and traffic patterns may be impacted. The document considers both challenges CDNs pose for ISPs and potential aggressive strategies ISPs could employ to handle CDN traffic.
Network and TCP performance relationship workshopKae Hsu
The document discusses TCP performance factors and techniques to improve TCP performance in network environments. It covers TCP operation principles, factors that impact TCP performance like packet loss, out-of-order packets, and congestion. It also discusses approaches to improve performance through the network like reducing packet loss and congestion, and through appliances like TCP offloading and optimization to reduce system resource usage.
The document discusses how the Internet works at a high level. It covers Internet topology, elements like IP addresses, autonomous systems, routers and switches. It describes routing protocols used within and between autonomous systems. It also discusses Internet security, MPLS, and how routing is performed between Internet service providers.
Redundant Internet service provision - customer viewpointKae Hsu
The document discusses redundant internet service provision from the customer's viewpoint. It covers the requirement for redundancy, different types including backup, load-sharing and multihoming. It also discusses the challenges for service providers in providing redundant services, such as needing new equipment and routing architectures. Solutions for customers are explored, as well as other issues like MPLS VPNs. The next challenges in the area are also noted.
Suggestions for end users to deploy multihoming, load-balance and load-sharingKae Hsu
The document discusses recommendations for multihoming, load balancing, and load sharing approaches. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and how new technologies like FTTX are replacing older ones. It also discusses more robust multihoming approaches that maintain redundancy and distribution without requiring BGP or own IP blocks, like using the same protocol across connections without own blocks.
The document discusses recommendations for multihoming, load balancing, and load sharing approaches for end users. It describes commonly used connection and distribution methods like leased lines, ISDN, ADSL and FTTX. It also discusses more robust multihoming options that maintain redundancy and balance traffic across connections without requiring BGP or own IP blocks, like using the same dynamic routing protocol across all ISP connections.