From: Bob Briscoe <bob.briscoe@bt.com>
To: <curtis@ipv6.occnc.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>,
"iccrg@irtf.org" <iccrg@irtf.org>,
"Akhtar, Shahid \(Shahid\)" <shahid.akhtar@alcatel-lucent.com>,
bloat <bloat@lists.bufferbloat.net>,
"aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [Bloat] [aqm] [iccrg] AQM deployment status?
Date: Tue, 5 Nov 2013 02:56:24 +0000 [thread overview]
Message-ID: <201311050256.rA52uPeG027636@bagheera.jungle.bt.co.uk> (raw)
In-Reply-To: <201310141707.r9EH7wC7068478@gateway1.orleans.occnc.com>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
Curtis & all,
At 17:07 14/10/2013, Curtis Villamizar wrote:
>In enterprise and data center there is also very good control over
>what equipment is used and how it is used. However, clue density
>decreases exponentially farther from the core and approaches zero in
>some data centers and in some enterprise IT departments. This is also
>true of the part of service provider organizations that pick stuff for
>consumer access. Where clue density is lowest, you'll find ignorance
>of AQM and buffer issues and lack of consideration for buffering and
>AQM when picking equipment for deployment and configuring it.
We (BT) use WRED extensively at the edge routers into our global
enterprise MPLS network (see the
<http://www2.bt.com/btPortal/application;JSESSIONID_btPortalWebApp=Jq1gl1Qz8sbdOQjvnRTGVGo1IfBs47bTe6Amy69S3bYcsw5A99sp!6984303?namespace=pns_catalogue&origin=mb_navigator_right_cd_editorial.jsp&event=link.print.editorial&PorS=products&contentType=techinicalspec&contentitemid=editorial/tech_spec/mpls_ts.xml&productDetail=products/mpls.xml>BT
MPLS technical
<http://www2.bt.com/btPortal/application;JSESSIONID_btPortalWebApp=Jq1gl1Qz8sbdOQjvnRTGVGo1IfBs47bTe6Amy69S3bYcsw5A99sp!6984303?namespace=pns_catalogue&origin=mb_navigator_right_cd_editorial.jsp&event=link.print.editorial&PorS=products&contentType=techinicalspec&contentitemid=editorial/tech_spec/mpls_ts.xml&productDetail=products/mpls.xml>specification).
Bob
________________________________________________________________
Bob Briscoe, BT
[-- Attachment #2: Type: text/html, Size: 2080 bytes --]
next prev parent reply other threads:[~2013-11-05 2:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Your message of "Fri, 11 Oct 2013 23:18:05 EDT." <12845.1381547885@sandelman.ca>
[not found] ` <201310141707.r9EH7wC7068478@gateway1.orleans.occnc.com>
2013-10-16 1:00 ` Wesley Eddy
2013-11-05 2:56 ` Bob Briscoe [this message]
2013-09-24 17:21 [Bloat] " Naeem Khademi
2013-09-25 14:20 ` [Bloat] [aqm] " Akhtar, Shahid (Shahid)
2013-09-25 14:31 ` [Bloat] [iccrg] " Eggert, Lars
2013-09-25 14:35 ` Steinar H. Gunderson
2013-09-25 18:51 ` Akhtar, Shahid (Shahid)
2013-09-25 19:19 ` [Bloat] [aqm] [iccrg] " Naeem Khademi
2013-09-27 16:49 ` Akhtar, Shahid (Shahid)
2013-09-25 19:24 ` Mikael Abrahamsson
2013-09-26 9:39 ` [Bloat] [iccrg] [aqm] " Scheffenegger, Richard
2013-09-27 2:59 ` Mikael Abrahamsson
2013-09-27 9:06 ` Eggert, Lars
2013-09-28 7:01 ` Mikael Abrahamsson
2013-09-28 7:04 ` Eggert, Lars
2013-09-29 1:16 ` [Bloat] [aqm] [iccrg] " Bob Briscoe
2013-09-29 9:37 ` Mikael Abrahamsson
2013-11-13 17:50 ` Fred Baker (fred)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201311050256.rA52uPeG027636@bagheera.jungle.bt.co.uk \
--to=bob.briscoe@bt.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=curtis@ipv6.occnc.com \
--cc=iccrg@irtf.org \
--cc=mcr+ietf@sandelman.ca \
--cc=shahid.akhtar@alcatel-lucent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox