>> really do not want to get drawn into this. but while looking into lags
>> a few years back, we found a lot of them split across line cards, with
>> resilience to line card failure being the stated reason.
>
> even in fixed configuration 1 and 2ru switches you may split them across
> asics for
Thu, Jan 18, 2018 at 11:10:38AM -0500, Jay Borkenhagen:
> [resend - apologies for any dupes]
>
> Distro cut *way* down.
>
> Regarding the suggestion for "logging knobs":
>
> - if it's just logging that a gshut action was taken, that's a local
> implementation decision -- no need to mention it
Distro cut *way* down.
Regarding the suggestion for "logging knobs":
- if it's just logging that a gshut action was taken, that's a local
implementation decision -- no need to mention it in the draft.
- if it's "Possibly raising alarms when something seems wrong", that
would be a bad idea.
[resend - apologies for any dupes]
Distro cut *way* down.
Regarding the suggestion for "logging knobs":
- if it's just logging that a gshut action was taken, that's a local
implementation decision -- no need to mention it in the draft.
- if it's "Possibly raising alarms when something seems w
OK,
Thanks Susan.
--Bruno
> -Original Message-
> From: Susan Hares [mailto:sha...@ndzh.com]
> Sent: Thursday, January 18, 2018 12:25 PM
> To: DECRAENE Bruno IMT/OLN
> Cc: grow@ietf.org; draft-ietf-grow-bgp-gshut@ietf.org; i...@ietf.org;
> ops-...@ietf.org
> Subject: RE: Opsdir
Bruno:
I'm sorry I'm this late for the review. On the editorial nit, if you think it
helps - send it to the RFC editor.
On the logging knobs, you understood my point. Logs should cover what is
section 4.2. However, since the document is in the RFC editor's queue - it is
your choice. If
Hi Susan,
Thanks for your time reviewing this document and you below comments.
Please see my replies inline [Bruno]
Note that however fast I'm answering to your review, that document is now in
RFC editor queue, and hence technical changes are much more difficult. (AFAIK,
would require specific
Reviewer: Susan Hares
Review result: Has Nits
Status: Nits
The operational procedures described in this process for the gshut comment are
accurately covered, and SHOULD work well. The Appendices A-C add to an
operations document and should be retained for publication.
Technical nit:
location of
