Adam-
There are a couple of clever Diffserv-TE (what your calling IntServ)
deployments out there. Both RDM & MAM are deployed. Truthfully, they are
pretty quiet, mainly, because the upfront planning that is required to go into
them and the relative lack of variations in the deployments. Diffserv-TE
offers some interesting per class/sub-pool BW protection options that other
deployments(see below) may not. Multi-class LSPs are also possible.
What is much more commonly deployed is what I would refer to as Class-Based
Forwarding. Your still combing COS based forwarding policies (like
Diffserv-TE), in the data-plane, with LSP BW reservations in the control-plane
but without the sub-pool BW reservations and relatively complicated BW sharing
models offered by RDM or MAM.
Both have their place depending on your specific service requirements.
Hth,
-Colby
On 10/1/18, 6:45 AM, "juniper-nsp on behalf of adamv0...@netconsultings.com"
<juniper-nsp-boun...@puck.nether.net on behalf of adamv0...@netconsultings.com>
wrote:
Hi folks,
Another pooling question from me,
This time I'm interested on what are your thoughts on DiffServ vs IntServ in
MPLS backbones and what use cases for IntServ can you think of please.
So what I have in mind specifically is RSVP-TE in combination with DiffServ
(standard QoS) vs IntServ (in all its glory i.e. BW pools and sub-pools,
allocation models RDM/MAM, etc..).
adam
netconsultings.com
::carrier-class solutions for the telecommunications industry::
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_juniper-2Dnsp&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=3lVLtwWQROCdl4DSF6Gy-pAupMaX1AvOyICNqk7ML5U&m=3QGSTryRPkSQi9gbZ4EEoEZq15OCtNIEr95BxH8E4Io&s=L1GMCwDLD4n9VecEVDCtJmZnunojow1JU1KeHEnFPwo&e=
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
