Network Direction Traffic Marking - Quality of Service (Part 2)

🎯 Загружено автоматически через бота: 🚫 Оригинал видео: 📺 Данное видео принадлежит каналу «Network Direction» (@NetworkDirection). Оно представлено в нашем сообществе исключительно в информационных, научных, образовательных или культурных целях. Наше сообщество не утверждает никаких прав на данное видео. Пожалуйста, поддержите автора, посетив его оригинальный канал. ✉️ Если у вас есть претензии к авторским правам на данное видео, пожалуйста, свяжитесь с нами по почте support@, и мы немедленно удалим его. 📃 Оригинальное описание: QoS needs to be considered, not just on a single device, but on the entire network. The first step to this is marking packets, which we will discuss in this video Once traffic has been identified, the IP header can be given a marking. This makes it easier for other devices to handle the packets later. There are three ways this might be done. Class of Service (CoS) marking is done on the packets passing over a trunk link. The marking is a special value (CS0 - CS7) in the header. IP Precedence was the original type of marking for IP packets. It’s very similar to CoS, as it allows for eight different markings (categories). This has been replaced with DiffServ (DSCP), which allows for many different markings, and is compatible with both IPv4 and IPv6. There are still eight major categories, but each category has up to eight more sub-categories, called drop probabilities. Now that we can mark traffic, we can identify it, and add it to one of these classes. We don’t need to use every class though. We could start with a simple 4 or 5 class model, and grow from there. The key is to not over-complicate! Overview of this video: Introduction What is Marking? Class of Service IP Precedence DSCP Organizing Traffic Types Patreon information: LET’S CONNECT 🌏 🌏 🌏 🌏 #NetworkDirection #networking #QoS