IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-error-handling-03.txt

Jeff Wheeler <jsw@inconcepts.biz> Mon, 10 December 2012 17:12 UTC

Return-Path: <jsw@inconcepts.biz>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB52521F850D for <idr@ietfa.amsl.com>; Mon, 10 Dec 2012 09:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level:
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[AWL=0.292, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5FVeOp4LOpLo for <idr@ietfa.amsl.com>; Mon, 10 Dec 2012 09:12:10 -0800 (PST)
Received: from mail-ia0-f180.google.com (mail-ia0-f180.google.com [209.85.210.180]) by ietfa.amsl.com (Postfix) with ESMTP id AA96521F84E4 for <idr@ietf.org>; Mon, 10 Dec 2012 09:12:10 -0800 (PST)
Received: by mail-ia0-f180.google.com with SMTP id t4so6091209iag.39 for <idr@ietf.org>; Mon, 10 Dec 2012 09:12:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=A/PuVYJhjaMDgkuLRm+Q408XQBpenCRo9/R16MKbWPQ=; b=TNs/txOBYErG0fv9sts+meGe9n/hivEcGjWg+2zy4g1TmwIA3XgjQEmAQlhUloIWdA Q7PEiEeb+d/wYitdLihgrrmpwjaRZBZLpw0sADiBBVdSX+NUdQQ9wqov7ohtLWdQWIgN YzLHDYDYC5grC9n+NHI5SBIWtEMo1kCUD95oGYWSBDPI6V7/2TIUWs7AGXuX3Q4Q1v87 ZKdKATJHh5cM6C5hGYujAc9ED7C0xtKH+E4zCdnN0aUKJxm4ZlBAbjOJ0uyFm557Hajk ayBshfODnrNO9KLl3rkyeomBgNvRF+qQd3luI3d5Dw9LN/YTP+jJsH4Rud7/o2MGZx8/ Uj7g==
MIME-Version: 1.0
Received: by 10.50.209.65 with SMTP id mk1mr7209878igc.8.1355159530223; Mon, 10 Dec 2012 09:12:10 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Mon, 10 Dec 2012 09:12:09 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <007801cdd6f2$069cc720$13d65560$@highwayman.com>
References: <20121121191321.6164.6887.idtracker@ietfa.amsl.com> <50AD2986.90705@cisco.com> <058b01cdd3b4$9f5193b0$ddf4bb10$@highwayman.com> <8ED5B0B0F5B4854A912480C1521F973A0F4940@xmb-rcd-x13.cisco.com> <94913EE5-2864-4EE2-B474-9631430B1E22@ericsson.com> <068701cdd478$2cf01cf0$86d056d0$@highwayman.com> <CAEGVVtBy-zdLz8hVajLnuAqgzfgQHrseK4r-N9=pOZGtqV7LbA@mail.gmail.com> <CAH1iCipfup-GEeJduBti_KHvX1pUZfmZLA3Zz5Y9Aw9xV3fQ9w@mail.gmail.com> <07e901cdd667$31c593e0$9550bba0$@highwayman.com> <CAPWAtbJ4WqoyrzE87v-7hJpp_=fL=B-LevdSe9Q-_m8FLYdFZw@mail.gmail.com> <007801cdd6f2$069cc720$13d65560$@highwayman.com>
Date: Mon, 10 Dec 2012 12:12:09 -0500
Message-ID: <CAPWAtbJ_1rwFuRC5sKfDUgpbGr=yyFb68fz+zjNuQmTfCB-9Lg@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Chris Hall <chris.hall@highwayman.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQmi/+PAMBbWq+jx5S67aI1GudxclbOoHM4k9apNixKDuU+suQ+IssOZcPbpm95BKOgyXUlx
Cc: idr@ietf.org
Subject: Re: [Idr] I-D Action: draft-ietf-idr-error-handling-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 17:12:14 -0000

On Mon, Dec 10, 2012 at 11:18 AM, Chris Hall <chris.hall@highwayman.com> wrote:
> Mind you, I suspect that operational remedies will also depend on the
> accurate identification of all affected NLRI, which is the horse I
> rode in on :-(

Yes, but I think removing the need to quickly identify the affected
NLRI, in order to get the network functioning again, is a good goal.
Most operators do not have the necessary knowledge to figure these
things out on their own.  Maybe the software can't exactly figure out
which NLRI are affected either, but it can still work around the
problem if IGNORE is one of the available options.

--
Jeff S Wheeler <jsw@inconcepts.biz>
Sr Network Operator  /  Innovative Network Concepts

v2.23.0 | Report a Bug | By Email