Transport-Related Protocol-Design Issues - Lars Eggert
Transport-Related Protocol-Design Issues - Lars Eggert
Transport-Related Protocol-Design Issues - Lars Eggert
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
lide title<br />
40 pt<br />
subtitle<br />
24 pt<br />
Text<br />
24 pt<br />
level 2-5<br />
20 pt<br />
Example: Quality of Service<br />
Relying on QoS mechanisms restricts your protocol to<br />
controlled environments where the deployment and<br />
configuration of those mechanisms can be enforced<br />
Examples<br />
– Differentiated forwarding (DiffServ) RFC 2475<br />
– Capacity reservations (IntServ or static) RFC 1663, 2210-12<br />
Relying on QoS is usually only appropriate for protocols<br />
that are (only) useful for such controlled environments<br />
– e.g., less-than-best-effort PHB [LEPHB] is not going to help with<br />
the Internet-wide P2P flood<br />
IETF-73, Minneapolis, MN, USA WG Chairs Training Lunch 7<br />
November 19, 2008<br />
Top right<br />
corner fo<br />
field-mar<br />
customer<br />
partner lo<br />
See Best<br />
for exam
Change language