> On Jan 10, 2017, at 10:21 AM, Fletcher Kittredge wrote:
>
> Numbers for building fiber optic systems are out there if you do the
> research. Joining the FTTH Council is a good start. One thing to recognise
> is that the numbers vary widely based on what is being built and where it
> is being b
Numbers for building fiber optic systems are out there if you do the
research. Joining the FTTH Council is a good start. One thing to recognise
is that the numbers vary widely based on what is being built and where it
is being built. There are large regional, technology, and product
variations. Ver
Hi Joel,
> On 10 Jan 2017, at 06:51, joel jaeggli wrote:
>
> On 1/9/17 2:56 PM, Laurent Vanbever wrote:
>> Hi NANOG,
>>
>> We often read that the Internet (i.e. BGP) is "slow to converge". But how
>> slow
>> is it really? Do you care anyway? And can we (researchers) do anything about
>> it?
>
Dear Baldur,
> I find that the type of outage that affects our network the most is neither
> of the two options you describe. As is probably typical for smaller networks,
> we do not have redundant uplinks to all of our transits. If a transit link
> goes, for example because we had to reboot a
On 10 January 2017 at 19:58, Job Snijders wrote:
> On Tue, Jan 10, 2017 at 03:51:04AM +0100, Baldur Norddahl wrote:
>> If a transit link goes, for example because we had to reboot a router,
>> traffic is supposed to reroute to the remaining transit links.
>> Internally our network handles this fai
> On Jan 10, 2017, at 3:14 PM, Hugo Slabbert wrote:
>
>
> On Tue 2017-Jan-10 20:58:02 +0100, Job Snijders wrote:
>
>> On Tue, Jan 10, 2017 at 03:51:04AM +0100, Baldur Norddahl wrote:
>>> If a transit link goes, for example because we had to reboot a router,
>>> traffic is supposed to reroute
On Tue 2017-Jan-10 20:58:02 +0100, Job Snijders wrote:
On Tue, Jan 10, 2017 at 03:51:04AM +0100, Baldur Norddahl wrote:
If a transit link goes, for example because we had to reboot a router,
traffic is supposed to reroute to the remaining transit links.
Internally our network handles this fai
On Tue, Jan 10, 2017 at 03:51:04AM +0100, Baldur Norddahl wrote:
> If a transit link goes, for example because we had to reboot a router,
> traffic is supposed to reroute to the remaining transit links.
> Internally our network handles this fairly fast for egress traffic.
>
> However the problem is
Hi Baldur,
Have you tried graceful shutdown?
You need redundant links, but not to the same transit.
https://tools.ietf.org/html/draft-ietf-grow-bgp-gshut-06
This draft is expired, but it is actually implemented by several vendors.
I implemented this.
http://www.slideshare.net/bduvivie/bgp-gracefu
I don't know about the rest of the list, but I find these numbers
fascinating. There's probably not that many people who are allowed
to share them, but if more could I think that would be educational
for a lot of folks.
In a message written on Wed, Jan 04, 2017 at 08:37:19AM -0500, Jared Mauch
> On 9 Jan 2017, at 18:19, Mike Lund wrote:
>
> Is this such a thing anywhere?
Try RIPE-Stat:
https://stat.ripe.net
best regards
Wolfgang
--
Wolfgang Tremmel
Phone +49 69 1730902 26 | Fax +49 69 4056 2716 | Mobile +49 171 8600 816 |
wolfgang.trem...@de-cix.net
Geschae
/RTGWG chair hat on
Dear NANOG,
For those, who might be interested, on January 25 we (IETF Routing Area RTGWG)
will be having an interim online meeting, dedicated to Existing problems for
routing in the large Data Centers and potential solutions. Presenters will be
describing (15 minutes
12 matches
Mail list logo
