<aol>
Me too!
</aol>
On Feb 25, 2011, at 11:44 AM, Renwei li wrote:
+1
Renwei
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Henderickx, Wim (Wim)
Sent: Wednesday, February 23, 2011 9:57 PM
To: Chris White; Smith, Donald
Cc: [email protected]; [email protected]
Subject: Re: [GROW] [Idr] Fwd: New Version Notification for draft-
shakir-idr-ops-reqs-for-bgp-error-handling-01
+1
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf
Of Chris White
Sent: woensdag 23 februari 2011 23:57
To: Smith, Donald
Cc: [email protected]; [email protected]
Subject: Re: [GROW] [Idr] Fwd: New Version Notification for draft-
shakir-idr-ops-reqs-for-bgp-error-handling-01
+1
Chris
On Feb 23, 2011, at 8:32 AM, Smith, Donald wrote:
+1 reasonable bgp error handling (rather then dropping sessions and
flushing routes) is a good idea.
Ignorance is Bliss. "Bliss (Basic Language for Implementation of
System Software) was a
systems programming language originally for the PDP-10 and
DECsystem-20 written at CMU." K-Oberman
[email protected]
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of
Colin Petrie
Sent: Wednesday, February 23, 2011 2:25 AM
To: [email protected]
Cc: [email protected]
Subject: Re: [GROW] [Idr] Fwd: New Version Notification for draft-
shakir-idr-ops-reqs-for-bgp-error-handling-01
On 22/02/11 14:50, Neil J. McRae wrote:
Rob,
This is a great document and as a network operator I think this is
something that I'd like to see implemented. The downsides of a
minute
inconsistency are not great enough compared to a complete BGP
failure
with
my organisations network*
I totally agree. This document is a pretty good summary of the
requirements on this, and a reasonable suggested implementation to
mitigate the problems we have seen before too many times.
Great work, thanks Rob :)
Cheers
Colin
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
This communication is the property of Qwest and may contain
confidential or
privileged information. Unauthorized use of this communication is
strictly
prohibited and may be unlawful. If you have received this
communication
in error, please immediately notify the sender by reply e-mail and
destroy
all copies of the communication and any attachments.
_______________________________________________
Idr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/idr
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
