General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Ing-Jyh Tsang <ing-jyh.tsang@alcatel-lucent.com>
To: <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] other people's VLAN congestion
Date: Thu, 21 Mar 2013 16:25:34 +0100	[thread overview]
Message-ID: <514B266E.8000000@alcatel-lucent.com> (raw)
In-Reply-To: <25677.1363877592@sandelman.ca>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Those queues can and should be correctly managed and configured. Both in 
terms of queue size and/or use of /RFC 2697/ 
<http://www.ietf.org/rfc/rfc2697.txt>
or /RFC 2698/ <https://tools.ietf.org/rfc/rfc2698.txt>, depend on each 
operator and what they are selling (SLA) ....

On 21/03/2013 15:53, Michael Richardson wrote:
> This is for the page where we list places that you may have bufferbloat
> and be unable to see it.  I think that there is a place in the wiki, but
> I have to locate it, and I started writing this offline.
>
> Many owners of (managed) fiber sell NNI to Access Port "LAN Extension"
> services. Typically there is a 1GB/s ethernet NNI in the data center,
> and a VLAN is assigned to travel to a 10Mb/s or 100Mb/s port at each site.
>
> The consumer of this service is usually (Boutique) ISPs, but also larger
> enterprises.   Without oversubscribing the NNI, the provider of the
> fiber may have oversubscribed the service, and this can cause queues to
> develop inside of this layer-2 network.  Even without oversubscription
> in the provider network, instantaenous bursts can sometimes cause
> significant jitter and buffer consumption.
>
> These buffers may have nothing to do with the consumer's
> traffic. Addition of buffers here reduces the drop probability therefore
> appears to the provider to be a good idea.
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


[-- Attachment #2: Type: text/html, Size: 2700 bytes --]

  reply	other threads:[~2013-03-21 15:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 14:53 Michael Richardson
2013-03-21 15:25 ` Ing-Jyh Tsang [this message]
2013-03-21 16:53   ` Michael Richardson
2013-03-22  7:11     ` Ing-Jyh Tsang

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=514B266E.8000000@alcatel-lucent.com \
    --to=ing-jyh.tsang@alcatel-lucent.com \
    --cc=bloat@lists.bufferbloat.net \
    /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