
From rjs@rob.sh  Wed Jan  2 03:39:01 2013
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A58221F909B; Wed,  2 Jan 2013 03:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 Vctg7HnjL0Ni; Wed,  2 Jan 2013 03:39:01 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id DF08421F9099; Wed,  2 Jan 2013 03:39:00 -0800 (PST)
Received: from [217.41.228.29] (helo=[10.10.2.216]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1TqMbq-0003QA-09; Wed, 02 Jan 2013 11:35:46 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <03c501cde845$54f82b30$fee88190$@highwayman.com>
Date: Wed, 2 Jan 2013 11:39:07 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A1782EC-9389-4F95-A7DC-BD9B67686EB7@rob.sh>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com>
To: Chris Hall <chris.hall@highwayman.com>, Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 11:39:01 -0000

On 1 Jan 2013, at 17:27, Chris Hall <chris.hall@highwayman.com> wrote:

> [=85snip=85]


Hi All.

I think this is a good summary of the different approaches. In =
ops-reqs-for-bgp-error-handling-06, there is no category of "fatal" =
essentially because (as you highlight) the line between the fatal and =
the critical cases is somewhat blurry. I would propose that we do not =
add another category of error for "fatal".

If I go back to the proposal I made on 31/12:

> Would the GROW working group be happy if we address Chris' concern =
related to "lost NLRI" (which AFAICS is really the case where we have >1 =
type of NLRI attribute within a single message) by adding a note that an =
error remains Non-Critical if _at least one_ NLRI attributes can be =
successfully parsed? I'm unclear here as to whether we're addressing a =
common situation where multiple sets of NLRI are being contained within =
a single message [1]. If so, then adding "at least one" and then a =
further point that an implementation SHOULD use a single NLRI attribute =
per UPDATE message, and put this at the start of the attributes would =
seem to be a fair way forward.

I would suggest that adding the following wording to =A7 3 of the draft =
addresses this, and clarifies the issue of "lost" NLRI:

"An error SHOULD be defined as Non-Critical if at least one NLRI =
attribute within an erroneous message can be successfully parsed. In =
cases where more than one attribute containing NLRI is included within a =
single UPDATE message, this may result in cases where some NLRI =
contained within subsequent attributes are missed, particularly where =
length errors exist in the message. In order to minimise the risk of =
such occurrences, it is recommended that an implementation SHOULD =
include only one attribute containing NLRI per message."=20

Additionally -- from the discussions that Jeff Wheeler raised, around =
repeated errors. In =A7 5, it seems that there is a further requirement, =
which I would suggest that we state as:

"In order to address repeated instances of critical errors, an =
implementation SHOULD provide a means by which an operator can enable =
such errors to be ignored. Where a mechanism of this nature is =
implemented, it provides a means by which an operator may avoid =
prolonged session failure which results in isolation from one, or more, =
routing domains. An operator deploying such a mechanism MUST be aware =
that holding such sessions up may result in inconsistency within the =
RIB, which may cause incorrect forwarding of traffic (e.g., loops, or =
blackholing)."

Some feedback on whether this addresses the points discussed over the =
last few days would be appreciated.

Happy New Year,
r.=

From jared@puck.nether.net  Wed Jan  2 07:26:38 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF61321F8525; Wed,  2 Jan 2013 07:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=-0.098,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 wNzG53wp3gMw; Wed,  2 Jan 2013 07:26:38 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDC321F8505; Wed,  2 Jan 2013 07:26:38 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r02FQXgO008570 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Jan 2013 10:26:34 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <03c501cde845$54f82b30$fee88190$@highwayman.com>
Date: Wed, 2 Jan 2013 10:26:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com>
To: "Chris Hall" <chris.hall@highwayman.com>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Wed, 02 Jan 2013 10:26:34 -0500 (EST)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 15:26:38 -0000

On Jan 1, 2013, at 12:27 PM, Chris Hall wrote:

> It is a truth universally acknowledged (AFAICS), that if NLRI in a
> broken UPDATE are treated-as-withdraw, that is no worse than
> session-reset and much to be preferred.
>=20
> So, treat-as-withdraw is a reasonable thing for any implementation to
> do, by default, where it can.
>=20
> The problem is that when things are broken, it may not be possible to
> identify all the NLRI -- some may be "lost".  [At this point I
> recommend: "The Engineer", AA Milne.]

I've been following this draft and wanted to chime in with some =
concerns.

1) in the (big) "Internet" space, lost NLRI are a huge deal for =
customers.

2) When we see a software defect that results in a session being closed, =
we regularly need help from the vendor to identify the offending =
NLRI/message.

3) The biggest problems we've seen are where vendor A and vendor B (or =
their sub-variants that run another OS) behave differently with the same =
NLRI.

I've seen a small number of theses cases over the past ~12 years and am =
very concerned with the amount of effort trying to error correct the =
error handling system when one side has a software defect.  I want to =
make it clear that all these cases attempting to resync at 0xffff etc =
are correcting for a defect.  Some of these defects resulted in an =
improperly formatted UPDATE message from a sender, and others were the =
result of problems on the receiver.

The instability this possibly introduces into an enterprise or large =
scale network is of significant concern.

To solve the "treat as withdraw" (aka: possibly create a per-node =
routing loop) problem, I would expect BGP users to demand a "periodic =
resend all NLRIs" feature to flush the state, creating further entropy =
in the system unnecessarily.

At some point, the equipment that is sending or receiving the BGP =
message will need to be maintained by the owner.  The dropping of the =
session is meant to draw attention to the problem in the same way as =
others that use ABORT or ASSERT in their code to handle an unexpected =
condition.

We can not correct for every error, nor should we make that a goal as =
the results in writing the error handling code quickly get complex.  =
(Speaking as someone who attempted to write a BGP implementation once.. =
ugh).

Asbestos suit on,

- Jared=

From jsw@inconcepts.biz  Mon Dec 31 08:59:17 2012
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DE9D21F88C3 for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 08:59:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.739
X-Spam-Level: 
X-Spam-Status: No, score=-2.739 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 byi4Y1yxVmlH for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 08:59:16 -0800 (PST)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by ietfa.amsl.com (Postfix) with ESMTP id 6442A21F8961 for <grow@ietf.org>; Mon, 31 Dec 2012 08:59:16 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id c11so15011817ieb.5 for <grow@ietf.org>; Mon, 31 Dec 2012 08:59:16 -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 :content-transfer-encoding:x-gm-message-state; bh=UQga9xK3+Szvg2Y9hlrJ3jaazunZbbfH88VwAJdVsQg=; b=ocBf2oZ2VIEPrOhGkSWhDPdGrUReQE9CmakG1yTgejGB56+Ny0+NK6nKScayto3Sia fb8CK+dYbMTkcx9USZIPm/dyrHNpYTvpfQP85CXTmVKLoz9lXn+WApVY6I6nCW5AJJ54 0ObFk0Nl9Vu6hK+lofxUGsEaqhe5RIUQXdrC/QuPnGCSvzOID/yRJRotwjDo0r2fhkFj gzuMbzaG8neAdeGJLd/qieNJV0IP6v4H+GRUjJvMq344DXgXLw3C3UGkk1eW0HvttPto 5UGzYP+jVyC9dt17aSFKUx1++FDDCKU0seVeQEyX2pb54V7nh3sieH/JSnLSD0QDUfpM leeQ==
MIME-Version: 1.0
Received: by 10.50.173.34 with SMTP id bh2mr36085608igc.70.1356973155917; Mon, 31 Dec 2012 08:59:15 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Mon, 31 Dec 2012 08:59:15 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <6EC403F6-43EE-4A70-860A-3196B1CF266C@rob.sh>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <6EC403F6-43EE-4A70-860A-3196B1CF266C@rob.sh>
Date: Mon, 31 Dec 2012 11:59:15 -0500
Message-ID: <CAPWAtbK4kOM2ruYGHSt8FuG+65GU0wpOYnNa1euodeZCp8OFdQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Rob Shakir <rjs@rob.sh>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkrEXE1X106gATFbnKUnNWaKT3pBXnGmRmb5sccPhBz3LMSZkGoj1dnQuMGKr1vnkI7trQr
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:01:50 -0800
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 16:59:17 -0000

On Mon, Dec 31, 2012 at 5:52 AM, Rob Shakir <rjs@rob.sh> wrote:
> If we tear down the session based on a single bad UPDATE, then Bad Things=
=99 happen.

This is why I'm confused why you aren't more interested in giving the
vendor (ultimately, the operator) the choice to simply ignore bad
updates.

You know that error-handling already leaves the RIB (network) in a bad
state.  You might as well give the option to reset the session under
even fewer circumstances.

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

From jsw@inconcepts.biz  Mon Dec 31 10:13:52 2012
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE8121F8836 for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 10:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.739
X-Spam-Level: 
X-Spam-Status: No, score=-2.739 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 f3ur++rUFSl4 for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 10:13:52 -0800 (PST)
Received: from mail-ia0-f177.google.com (mail-ia0-f177.google.com [209.85.210.177]) by ietfa.amsl.com (Postfix) with ESMTP id 16F7921F87FD for <grow@ietf.org>; Mon, 31 Dec 2012 10:13:52 -0800 (PST)
Received: by mail-ia0-f177.google.com with SMTP id u21so10799201ial.36 for <grow@ietf.org>; Mon, 31 Dec 2012 10:13:51 -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 :content-transfer-encoding:x-gm-message-state; bh=p26aorl2upw71e+E8nixMbqeSDDA2WRioFANLxiKL6Q=; b=WbZ0T3UKTRKiuABAESXVInJSUTn0G41vbS2hjYzcL/VtC/oF98UvoHbDuayTwMoptp Ud7FB5YRqVPHzMmSl2ZciE4wxvn1c6Tq24/nmkdqlajlibF6eLEgrDTHbeGmMAlbwzyg DMgUr2LiDlRAHOtychteVJIC2Z4ThcBeT0CE0PwTxjbTnk7WV98fmpeZvoBAwFsOVBkP JT+5LXYItmX/quYk6jPrTws7tSsBldSsp6IZviSCBwDuv6L+IdZgZyxiU2UJZRS7UaXg w56ijGydGz5Fxyr/eCerrTsqch1f+7BIIorGBl3/PsZXTEJyWzpiK9lRSZCtsHr8j8r7 ljTw==
MIME-Version: 1.0
Received: by 10.50.152.240 with SMTP id vb16mr35381902igb.45.1356977631657; Mon, 31 Dec 2012 10:13:51 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Mon, 31 Dec 2012 10:13:51 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <20121231030925.GB62942@verdi> <CA+b+ERkYE61CSCxmZosxRO1LHhddRLsNmXYtB_nnBa8pVpy4Hw@mail.gmail.com> <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com>
Date: Mon, 31 Dec 2012 13:13:51 -0500
Message-ID: <CAPWAtb+v4W4qVQ6ceTdewc4u_nBOyZLztXe_m7vT_QCna2WWfQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlMPDTKBiAjqFoyeNvXav1csgqWhUqZwEFphaAK7HK02iPOPAP/rVoY5s+gGXcidmV9mcMi
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:01:50 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 18:13:52 -0000

On Mon, Dec 31, 2012 at 12:54 PM, Jakob Heitz <jakob.heitz@ericsson.com> wr=
ote:
> I don't think treat-as-withdraw is trying to fix a single session reset. =
Graceful restart can fix that. It's the rolling resets that need a human to=
 remove a buggy router or a config that triggered the bug. That takes sever=
al hours. Treat-as-withdraw limits the damage during those hours.
>
> Could we please settle on that without trying to solve the impossible?

If you read my posts to IDR on this topic, you'll see where I explain
how it is possible to solve the "impossible."

Specifically, you can ignore just about any bad update, or bad message
of any kind, as long as you can figure out where the next message
starts.  This fixes the rolling resets.

You may know that a lot of businesses suffered multi-hour outages in
October simply because of 5 DFZ routes announced by LANL that had
illegal attributes.  This is very hard for operators to troubleshoot
on most routers.  The routers that experienced rolling resets were
buggy but if the operators simply had a panic button, "ignore bad
messages," their networks would have been up and they would not have
been losing money by the minute.

This is not the only time bad updates have propagated through the DFZ
and caused big problems.  It has happened repeatedly.

I believe it will begin to happen more often inside datacenter
networks, because BGP is being used for more and more things, like
EVPN.  Operators are going to need BGP to become more robust.

You can make it a lot more robust just by deciding to ignore
everything in a bad message.  This is not good, but it is a lot better
than session-reset, in most cases.

Please, read my posts on this topic, and do not treat this problem as
an unsolvable one.  It can be largely solved in a way that gives a
very useful fallback option to operators.

This whole draft is about fallback options, and it is pretty stupid to
have a large amount of complexity to solve a small set of potential
bugs, when you could ALTERNATIVELY or IN ADDITION to that, have a very
low-complexity option that solves more problems.

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

From john@jlc.net  Mon Dec 31 10:41:39 2012
Return-Path: <john@jlc.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7D621F8767; Mon, 31 Dec 2012 10:41:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.16
X-Spam-Level: 
X-Spam-Status: No, score=-106.16 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 Fjn-v+-lciQt; Mon, 31 Dec 2012 10:41:38 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 9522121F870C; Mon, 31 Dec 2012 10:41:38 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8098833C3D; Mon, 31 Dec 2012 13:41:38 -0500 (EST)
Date: Mon, 31 Dec 2012 13:41:38 -0500
From: John Leslie <john@jlc.net>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Message-ID: <20121231184138.GA25817@verdi>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com>
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:01:50 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 18:41:39 -0000

Jakob Heitz <jakob.heitz@ericsson.com> wrote:
> On Dec 31, 2012, at 1:21 AM, "Robert Raszuk" <robert@raszuk.net> wrote:
>> On Mon, Dec 31, 2012 at 4:09 AM, John Leslie <john@jlc.net> wrote:
>>> Brian Dickson <brian.peter.dickson@gmail.com> wrote:
>>>> 
>>>> But, the basic problem is this: missing an UPDATE won't trigger either
>>>> condition, it will at worst cause sub-optimal routing.

   I apologize for careless reading here. I took Brian to mean failing
to process an UPDATE which changed the NLRI from a peer, but didn't
change the _reachability_ of that block from that peer, breaks things
but mildly.

>>>> Missing a WITHDRAW _CAN_ cause Bad Things (TM) to happen.
>>> 
>>>   +1

   I meant to +1 the statement that missing the notice that an NLRI
was being withdrawn and not replaced (thereby changing reachability
from positive to negative) is a much more serious breakage, since
you may keep sending packets to that peer which no longer has the
reachability you think it does.

>> How about if we would mandate Enhance Route Refresh request to be send
>> to such peer who's bad updates triggered treat-as-withdraw action ?

   A Route-Refresh cycle would ensure that we have the actual
reachability status of that peer (if the Route-Refresh completes)
instead of some outdated NLRI the peer intended to withdraw without
replacement.

>> Yes that means that "treat-as-withdraw" should be applied only to
>> those peers which support Enhanced Route Refresh.

   We're discussing an area where "treat-as-withdraw" may no longer
be a useful term, since we're considering an UPDATE so badly formed
that we can't even extract which CIDR blocks are the subject of it.

   Personally, I'd prefer a Route-Refresh approach, where we make it
perfectly clear to the peer in question that we no longer have a
trustworthy state of its current advertised routing.

> I don't think treat-as-withdraw is trying to fix a single session reset.
> Graceful restart can fix that. It's the rolling resets that need a
> human to remove a buggy router or a config that triggered the bug.
> That takes several hours. Treat-as-withdraw limits the damage during
> those hours.

   I agree with Jakob that we're _trying_ to discuss that -- but I
don't agree we're succeeding very well.

> Could we please settle on that without trying to solve the impossible?

   I'm not sure we can...

   First of all, most of us _aren't_ trying to solve the impossible:
we're trying to design an error-management paradigm which passes _enough_
information on which to base intelligent routing decisions.

   And, I'm not sure what it means to "settle on" "treat-as-withdraw"
that some of us consider "good enough" for a "limited" period while
humans are working to resolve the actual problem. We know that the
"limits" on such a period correlate all to well with the amount of
pain being inflicted on paying customers.

--
John Leslie <john@jlc.net>

From jsw@inconcepts.biz  Mon Dec 31 11:59:22 2012
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26E221F87B4 for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 11:59:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.74
X-Spam-Level: 
X-Spam-Status: No, score=-2.74 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 gT9mzTOQpRxl for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 11:59:21 -0800 (PST)
Received: from mail-ia0-f176.google.com (mail-ia0-f176.google.com [209.85.210.176]) by ietfa.amsl.com (Postfix) with ESMTP id 56E9421F8798 for <grow@ietf.org>; Mon, 31 Dec 2012 11:59:21 -0800 (PST)
Received: by mail-ia0-f176.google.com with SMTP id y26so10746277iab.21 for <grow@ietf.org>; Mon, 31 Dec 2012 11:59:20 -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=Cxd405Mu9Cj+XOBlF/lk+l5o5dSXmSNp+tW6LWTSM0k=; b=ZwQEAKC0PERjbxKXJJXiXlRxe2kzcBXv9oH87UEbRrmzxqYVR/nRkWGcGwtf2JJNaJ JW8wJqowRGh2bwHKLQ2Cxr3o6S/bTOcD6kpL8wQJjPI8VhOtQzfVGn6MITgnZOtpOyGO NCM8XmDkr0bkORFpTxZIO49/K0zTPU9C9at0j84ltiyfreJZ5RdeaCpC9ikmqUZAmaoq DF1bGI4IJG/bNpZQqLS148f7/1EJdGhNOmIMV8/PZPVGd1sFotvHYsGSSzQkobOKhwPC 2rB+8OWeFEIycHtL49m0bW21RV+uHIFZ19e8VtHBxkc9/TMWdXcIXdlQGvYNNhMzIpJ1 4L3A==
MIME-Version: 1.0
Received: by 10.50.173.34 with SMTP id bh2mr36385916igc.70.1356983960831; Mon, 31 Dec 2012 11:59:20 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Mon, 31 Dec 2012 11:59:20 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <20121231184138.GA25817@verdi>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com> <20121231184138.GA25817@verdi>
Date: Mon, 31 Dec 2012 14:59:20 -0500
Message-ID: <CAPWAtbJTE1mnkHMHVfh0-66HmtG4ERTFbODRPYay42g2khJnnA@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: John Leslie <john@jlc.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQm724bxj4ERd9enzE+9E7AI5FF4hE97heZDTLBLe7W9+tK3thNsc4HruvJgZzq6Kh25ewDv
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:01:50 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 19:59:22 -0000

On Mon, Dec 31, 2012 at 1:41 PM, John Leslie <john@jlc.net> wrote:
>    And, I'm not sure what it means to "settle on" "treat-as-withdraw"
> that some of us consider "good enough" for a "limited" period while
> humans are working to resolve the actual problem. We know that the
> "limits" on such a period correlate all to well with the amount of
> pain being inflicted on paying customers.

It means just that, "settle on."  Treat-As-Withdraw leaves plenty of
circumstances where BGP will still be reset, perhaps endlessly until
clue arrives.

Let me just go through the explanation of what happened to many
networks in October 2012 again.  LANL announced some malformed routes
to the DFZ.  Most routers propagated them and ignored the malformed
bits.  Some routers did not, and instead, they reset the BGP session.
That was a bug, but the customers had NO OPTIONS TO WORK AROUND THIS.
Their ONLY CHOICE was to wait for a patch from their vendor (for folks
whose vendor routers did this) or install a patch (for the lucky users
who were running OpenBSD) or to ask their transit provider to install
a prefix-list to block the 5 malformed paths from going to them.

If customers had treat-as-withdraw in the form being discussed today,
it would not have helped.  Why?  Malformed Attribute Flags are not one
of the criteria it addresses.

What networks need is an IGNORE BAD MESSAGES option so BGP can avoid
session-reset, even if the cost is rather high (say a lot of RIB
inconsistency.)  Let the network operator choose when the cost of bad
RIB information becomes so high that he would rather have BGP reset.
After all, this will vary from one network to the next based on
business needs, so there should be flexibility.

That is why treat-as-withdraw is "settling."  Ignore bad messages is a
very simple option that "fixes" (mitigates) virtually all problems so
the operator can buy time to diagnose it in detail, or wait for his
vendor to provide a software update, or whatever.

I'm not arguing this should be the only option or even the default
option.  I'm arguing that it should be ONE OPTION.  As far as I'm
concerned, you can have treat-as-withdraw, and you can build as much
complicated error handling logic into it as you want.  That effort
might help me someday.  But if it doesn't, I know for sure that IGNORE
BAD MESSAGES is something I can fall back on, which is very likely to
buy me the time I need.

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

From jsw@inconcepts.biz  Mon Dec 31 12:36:11 2012
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC68821F85B4 for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 12:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level: 
X-Spam-Status: No, score=-2.741 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 AQBLaL-CCtCH for <grow@ietfa.amsl.com>; Mon, 31 Dec 2012 12:36:11 -0800 (PST)
Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by ietfa.amsl.com (Postfix) with ESMTP id 321A221F884D for <grow@ietf.org>; Mon, 31 Dec 2012 12:36:11 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id 13so15379237iea.21 for <grow@ietf.org>; Mon, 31 Dec 2012 12:36:05 -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=0ZYTIiDsVsBy5z6lIkNJaqxS9V9Y2v0I3ZOvXvBxrIY=; b=ZDdvD4SBS61ETYb3a8n/lmpSpxdCYhuekYCY4JREbBhidLDw1AJt2+IVtdOnH0nOU/ PXZ/r4Qxu+n1GHLTxwaqfvCkp6fBk3dpneif2yFc6MemjYr/4FS7iL9WyZMhxoPUq0VX lrJke5c8cqQNHdsCZEotBXqE8E/BkAcrdrVx6dWxhQsPrFdOiN2DxxZODRtDsV0Elh02 5u4uUQYPvbcaMnGMnWXyYE6rx2iNfCRlKXqrxazCN7FPvBpaxDzKfkKU1DZHkDAki65Q CJLkCkOWqTT+Lm9q3XyNogtRhR1iNlRVa8VlXNW2KIf7tiXvecOVkfJ3ItwfjekhQ4tE HMHw==
MIME-Version: 1.0
Received: by 10.42.180.65 with SMTP id bt1mr31909870icb.41.1356986165804; Mon, 31 Dec 2012 12:36:05 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Mon, 31 Dec 2012 12:36:05 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E147337@eusaamb109.ericsson.se>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com> <20121231184138.GA25817@verdi> <CAPWAtbJTE1mnkHMHVfh0-66HmtG4ERTFbODRPYay42g2khJnnA@mail.gmail.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E147337@eusaamb109.ericsson.se>
Date: Mon, 31 Dec 2012 15:36:05 -0500
Message-ID: <CAPWAtbJgafPta3dNciHX1e3vtC9TFuV3CbxN81U_82JmsmPrYQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmsYunPNigEus6oyAwO9xS3RhS1lkPnHMF2zBUcysODhIS7O1hdpdJrlJpgsJOClrX5J9Tc
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:01:50 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Dec 2012 20:36:12 -0000

On Mon, Dec 31, 2012 at 3:24 PM, Jakob Heitz <jakob.heitz@ericsson.com> wrote:
> That covers malformed attribute flags.

Except in the MP_REACH_NLRI or MP_UNREACH_NLRI, which is not a foolish
exception if the goal is to recover all the NLRI; but if the goal is
to avoid session-reset, it is.

Like I keep saying, the goal of error-handling should be to make
session-reset avoidable.  Today it is not.  It is creating complex
rules which must be supported by both sides of the BGP session to try
very hard to keep the network in a good state.

This is a good goal in itself, but not to the exclusion of avoiding
session-reset.

Again, the existing draft also ignores conflicts with RFC4271.  So do
the updates to RFC4760.  You are not allowed to put attributes into
the attribute list in any order you want.  RFC4271 explicitly requires
that attributes be sorted by Attribute Type Code.  A Capability
negotiation is necessary to change the ordering of attributes.

Finally, because the current error-handling concept can't be
implemented without such a capability, it's not useful if the other
BGP speaker lacks support.  That is why IGNORE BAD MESSAGES is needed.
 It doesn't require support on both sides.

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

From chris.hall@highwayman.com  Tue Jan  1 09:27:58 2013
Return-Path: <chris.hall@highwayman.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD0E21E8041; Tue,  1 Jan 2013 09:27:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.156
X-Spam-Level: 
X-Spam-Status: No, score=0.156 tagged_above=-999 required=5 tests=[AWL=0.468,  BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227]
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 t57VC4LCu17R; Tue,  1 Jan 2013 09:27:57 -0800 (PST)
Received: from smtp.demon.co.uk (mdfmta004.mxout.tch.inty.net [91.221.169.45]) by ietfa.amsl.com (Postfix) with ESMTP id A5BF221E803F; Tue,  1 Jan 2013 09:27:56 -0800 (PST)
Received: from mdfmta004.tch.inty.net (unknown [127.0.0.1]) by mdfmta004.tch.inty.net (Postfix) with ESMTP id 3C8BFAC43CD; Tue,  1 Jan 2013 17:27:55 +0000 (GMT)
Received: from mdfmta004.tch.inty.net (unknown [127.0.0.1])	by mdfmta004.tch.inty.net (Postfix) with ESMTP id 01EF9AC43CA; Tue,  1 Jan 2013 17:27:55 +0000 (GMT)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta004.tch.inty.net (Postfix) with ESMTP; Tue,  1 Jan 2013 17:27:54 +0000 (GMT)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1Tq5d3-0000zw-Uz; Tue, 01 Jan 2013 17:27:54 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <idr@ietf.org>,	<grow@ietf.org>
Date: Tue, 1 Jan 2013 17:27:48 -0000
Organization: Highwayman
Message-ID: <03c501cde845$54f82b30$fee88190$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3oRU5I57qn1PrRSQSfRRimyGjioQ==
Content-Language: en-gb
X-MDF-HostID: 17
X-Mailman-Approved-At: Wed, 02 Jan 2013 08:01:49 -0800
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Jan 2013 17:27:58 -0000

Jeff Wheeler wrote (on Mon 31-Dec-2012 at 20:36 +0000):
....
> Like I keep saying, the goal of error-handling should be to make
> session-reset avoidable.  Today it is not.  It is creating complex
> rules which must be supported by both sides of the BGP session to
> try very hard to keep the network in a good state.

It is a truth universally acknowledged (AFAICS), that if NLRI in a
broken UPDATE are treated-as-withdraw, that is no worse than
session-reset and much to be preferred.

So, treat-as-withdraw is a reasonable thing for any implementation to
do, by default, where it can.

The problem is that when things are broken, it may not be possible to
identify all the NLRI -- some may be "lost".  [At this point I
recommend: "The Engineer", AA Milne.]

The effects of "lost NLRI" range from "ho hum" to "arghh", depending.
The possibility of "lost NLRI" ranges from "small, I think" through
"dunno" to "don't care".

The incidence of "lost NLRI" can be reduced by some simple rule
changes on the ordering of attributes.

But, there is a desire to improve things without changes at the sender
end.  Also, there is a desire to avoid session-reset at (almost) all
costs -- right up to the point where sessions are never reset
(re-syncing on 16 x 0xFF as required).  So, since we cannot eliminate
"lost NLRI" let us learn to love them (or at least learn some
tolerance).

The risks posed by "lost NLRI" are unknown, and the effects context
dependent.  Given the uncertainty, I do not think it is reasonable to
accept anything more than a (vanishingly) small risk of "lost NLRI",
by default.  So, AFAICS, we are in the land of the knob.

Suppose three categories of error in an UPDATE message:

  * Non-Critical -- ie treat-as-withdraw or otherwise

    in general terms: all NLRI accounted for.

    More accurately: the risk of "lost NLRI" is deemed
    negligible.

  * Critical -- ie bad, but not session-reset

    in general terms: "lost NLRI", ie:

      either: there is reason to believe that there
        are "lost NLRI" (eg. a broken MP_UNREACH_NLRI
        attribute)

      or: it is not sufficiently clear that all NLRI
        are accounted for.

    NLRI that can be accounted for may be treated in
    a Non-Critical sort of a way, but some other
    response(s) may be triggered to mitigate the
    effect of "lost NLRI".

   * Fatal -- ie session-reset

     things are FUBAR -- by some definition.

     (Graceful Restart and enhancements thereof may blur
      the line between Fatal and Critical errors.  But
      that's another story.) 

The message is broken... things are uncertain, so: a key knob is the
one which allows the operator to select criteria for Criticality --
anything less is Non-Critical, anything more is Fatal.  Other knobs
may select for specific responses to different forms of Critical and
Non-Critical errors.

This is all starting to look complicated :-(  But at least it avoids
trying to square the circle.  [When you have eliminated the
impossible, what remains, ....]

At a practical level, I observe:

  1) if (or as) most implementations only send one
     collection of NLRI per message, then extracting
     one collection is enough to be reasonably sure
     there are no "lost NLRI".

  2) the worst case of "lost NLRI" is lost Withdrawn
     NLRI... which, per (1), are going to be the
     only NLRI in the message, and hence unlikely
     to be lost.

So, a knob or two can allow the operator to settle on what works best
for them, and allow the implementer to provide stuff which an adult
operator may use in the privacy of their own network.  And, one can
envisage Emergency Knobs -- for when there is limited time to Save the
World, and being fastidious about the specification just gets in the
way.

Stepping back from the minutiae of unpacking UPDATE messages, in
routeing terms the above categories are (I think):

  * Non-Critical:

      - some routes which the sender has offered have been
        filtered out, because the attributes were garbled,
        (ie treat-as-withdraw),

      - some routes which the sender offered had partly
        invalid attributes, but they have been accepted,
        in some form (ie other mechanisms),

      - BUT the routes which remain are *valid*,

      - AND the receiver knows which prefixes have been
        affected.

  * Critical:

      - some routes which the sender has offered are not
        available to the receiver,

      - some routes which should have been withdrawn
        may still be in use,

      - some routes whose attributes should have been
        changed may still be in use,

      - AND the receiver does not know which of the
        routes which remain are in doubt.

   * Fatal -- FUBAR

Incidentally, in the absence of any better, novel mechanism: having
reset and restarted a session, there is (much) less reason to worry
about "lost NLRI" -- at least until End-of-RIB rolls up (or some
time-out).  But in any case, some things which are Fatal in normal
running could be downgraded, for some period, after a session-reset ?

Happy New Year,

Chris


From tony.li@tony.li  Wed Jan  2 09:58:47 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7CD121F8780 for <grow@ietfa.amsl.com>; Wed,  2 Jan 2013 09:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.288
X-Spam-Level: 
X-Spam-Status: No, score=-100.288 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 Z21cUepD7esi for <grow@ietfa.amsl.com>; Wed,  2 Jan 2013 09:58:47 -0800 (PST)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2A821F8770 for <grow@ietf.org>; Wed,  2 Jan 2013 09:58:46 -0800 (PST)
Received: from omta14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by qmta01.emeryville.ca.mail.comcast.net with comcast id j3Vo1k0071HpZEsA15ym35; Wed, 02 Jan 2013 17:58:46 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta14.emeryville.ca.mail.comcast.net with comcast id j5wW1k00f52qHCY8a5wZKk; Wed, 02 Jan 2013 17:56:44 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net>
Date: Wed, 2 Jan 2013 09:56:30 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357149526; bh=EkU9Aq57tmHbIe+yDlK7UDVvGTUXTIIoFHPYZ7sA6y0=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=MIceq0YaA0JwYrZlNbLOSSH+ZrnZhnBTEh5JHYHGzG7Aypw8IR79wGgD2dH0Uh7iD or6YLKV1iUbUxg9ci1WsnxRDp8BH2QILnRNTS4ZhZiyW2TVhM5SUL0i7jiZmfMjP1m Wn/l3waInostloNBI07265nquL/+AA5RQDH/FoShsfDQO/DHitZ8UB/oPdjxXrPCaJ eQA3HWYm7Ckru/P4sMNmjw+b7oi+s2E6hJnjylv1+XOP09WVgreVoBuMXRCPk0yxY5 ootzuPOUOvA+GzycvOPtaAt7cHTiik+zvU0lErYisF4QkoJVOPwwaw0LCVEII4sDJC aL1egpi+c0HIQ==
Cc: idr@ietf.org, grow@ietf.org, Chris Hall <chris.hall@highwayman.com>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 17:58:48 -0000

On Jan 2, 2013, at 7:26 AM, Jared Mauch <jared@puck.nether.net> wrote:

> We can not correct for every error, nor should we make that a goal as =
the results in writing the error handling code quickly get complex.=20


+1

I'd also like the folks in the operational community who feel that =
treat-as-withdraw is a too liberal policy to please speak up.  I know =
folks still call their vendors and raise the roof when a single prefix =
is improperly handled.  Your voices need to be heard here too.

While we can do SOME things to decrease session resets, we cannot fix =
all cases and simply treating things as a withdraw and walking away is =
wholly unacceptable, as some of you will hopefully agree.  Creating =
arbitrary hair here is NOT going to help as the error handling code =
itself will become fraught with errors.

Ergo: KISS

Tony


From jakob.heitz@ericsson.com  Wed Jan  2 12:05:50 2013
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D112321F867E; Wed,  2 Jan 2013 12:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.338
X-Spam-Level: 
X-Spam-Status: No, score=-6.338 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 uw3CKhLXdE1j; Wed,  2 Jan 2013 12:05:49 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id C005921F867D; Wed,  2 Jan 2013 12:05:38 -0800 (PST)
Received: from EUSAAHC008.ericsson.se ([147.117.188.96]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r02KIwqk024597; Wed, 2 Jan 2013 14:19:00 -0600
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0318.004; Wed, 2 Jan 2013 15:05:11 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Tony Li <tony.li@tony.li>, Jared Mauch <jared@puck.nether.net>
Thread-Topic: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6RLnMUudy3dkzUCvAnw0oYxCOZg2dB2Q
Date: Wed, 2 Jan 2013 20:05:11 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E14A3CC@eusaamb109.ericsson.se>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li>
In-Reply-To: <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, Chris Hall <chris.hall@highwayman.com>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 20:05:51 -0000

On , Tony Li <> wrote:

> simply treating things as a withdraw
> and walking away is wholly unacceptable,

It's worth reiterating that Robert and I (at least) have advocated
for using
http://tools.ietf.org/html/draft-ietf-idr-operational-message-00
when an error is detected but no NOTIFICATION is sent.

BTW, I notice that this draft has expired.


--=20
Jakob Heitz.

From chris.hall@highwayman.com  Wed Jan  2 10:15:41 2013
Return-Path: <chris.hall@highwayman.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD70721F86E7; Wed,  2 Jan 2013 10:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.134
X-Spam-Level: 
X-Spam-Status: No, score=0.134 tagged_above=-999 required=5 tests=[AWL=0.446,  BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227]
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 CChUJJCGWpLY; Wed,  2 Jan 2013 10:15:39 -0800 (PST)
Received: from smtp.demon.co.uk (mdfmta004.mxout.tbr.inty.net [91.221.168.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC2D21F8461; Wed,  2 Jan 2013 10:15:39 -0800 (PST)
Received: from mdfmta004.tbr.inty.net (unknown [127.0.0.1]) by mdfmta004.tbr.inty.net (Postfix) with ESMTP id F2EAAA0C084; Wed,  2 Jan 2013 18:15:37 +0000 (GMT)
Received: from mdfmta004.tbr.inty.net (unknown [127.0.0.1])	by mdfmta004.tbr.inty.net (Postfix) with ESMTP id CC2EDA0C081; Wed,  2 Jan 2013 18:15:37 +0000 (GMT)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta004.tbr.inty.net (Postfix) with ESMTP; Wed,  2 Jan 2013 18:15:37 +0000 (GMT)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1TqSqm-000113-Rm; Wed, 02 Jan 2013 18:15:36 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <idr@ietf.org>,	<grow@ietf.org>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <0A1782EC-9389-4F95-A7DC-BD9B67686EB7@rob.sh>
In-Reply-To: <0A1782EC-9389-4F95-A7DC-BD9B67686EB7@rob.sh>
Date: Wed, 2 Jan 2013 18:15:31 -0000
Organization: Highwayman
Message-ID: <044401cde915$29b64ad0$7d22e070$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJc3CmccD8qr+UA8XZaw8qzk1ZbRwFwQA1TlwyHO6A=
Content-Language: en-gb
X-MDF-HostID: 9
X-Mailman-Approved-At: Wed, 02 Jan 2013 12:32:10 -0800
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jan 2013 18:15:41 -0000

Rob Shakir wrote (on Wed 02-Jan-2013 at 11:39 +0000):
> On 1 Jan 2013, at 17:27, Chris Hall wrote:
> > [=85snip=85]
=20
> I think this is a good summary of the different approaches. In ops-
> reqs-for-bgp-error-handling-06, there is no category of "fatal"
> essentially because (as you highlight) the line between the fatal
> and the critical cases is somewhat blurry. I would propose that we
> do not add another category of error for "fatal".

OK.  Old-fashioned session-reset (unadorned by Graceful Restart or
other mitigation, past present or future) is Bad.  The Fatal category
would capture cases where an old-fashioned session-reset is the only
available response.  As old-fashioned session-reset fades into distant
memory, that distinction will be less useful.

I think that what this boils down to is:

  Non-Critical =3D> per-Message response is sufficient

  Critical     =3D> per-Session (or possibly per-AFI/SAFI)
                  response is required.

The anatomy of per-Message response may include:

  1) treat-as-withdraw all NLRI that can be identified

  2) scrubbing round some attribute errors and proceeding
     with some or all announced NLRI.

  3) other (novel) means to recover the state of particular
     NLRI.

  4) (implicitly) ignoring any known or unknown "lost-NLRI".

The anatomy of per-Session response may include:

  a) old-fashioned session-reset, where nothing else is
     available.

  b) complete session-drop, where patience is exhausted.

  c) other means, old and new, to restore the session,
     to some level of health.

  d) some means to control cycles of repeated errors
     generating the same (inadequate) response.

     [Definition of madness: doing the same thing over
      and over again in the expectation of a different
      outcome.]=20

It seems to me that there are two contexts for error-handling: (i) in
normal running, and (ii) during error-recovery.

Things which are deemed Critical in normal running may be deemed
Non-Critical during error-recovery.  That may be part of the automatic
per-Session response to an error, or may be some override settable by
the Operator.

What an operator deems Non-Critical in normal running will depend on
their assessment of the risk/impact of "lost NLRI" and the impact/cost
of the available per-Session response(s).  The risk of "lost NLRI"
depends on sender behaviour and on the acceptable
"degree-of-broken-ness".  The impact of "lost NLRI" is context
dependent.  The impact/cost of any per-Session response depends on
what is supported by both ends of the session.

My conclusion is that there is no "one size fits all" allocation of
errors to class of error.  Hence, the requirement is for operator
control over error classification and over error response/recovery --
on a per Session basis -- both for normal running and error-recovery.

Having got this far... I'm tempted to back away from talking about
Critical/Non-Critical *Errors*, and talk, instead, about
Message-Level/Session-Level *Recovery*... not much of the existing
draft would be affected if the focus shifted from Errors to Recovery.

.....
> I would suggest that adding the following wording to =A7 3 of the
> draft addresses this, and clarifies the issue of "lost" NLRI:
>=20
> "An error SHOULD be defined as Non-Critical if at least one NLRI
> attribute within an erroneous message can be successfully parsed. In
> cases where more than one attribute containing NLRI is included
> within a single UPDATE message, this may result in cases where some
> NLRI contained within subsequent attributes are missed, particularly
> where length errors exist in the message. In order to minimise the
> risk of such occurrences, it is recommended that an implementation
> SHOULD include only one attribute containing NLRI per message."

The way in which attributes and NLRI are packed in a (current) UPDATE
message is unhelpful.  But, I don't think this is the place to solve
that problem.

Further, changes to the specification of UPDATE messages cannot ensure
that software will follow that (or any other) specification.  After
all, we are only here because software is less than perfect !  And,
there is some desire to cope with errors which cannot be addressed by
any amount of specification-tweaking.

And, there is the need to do better without changes at the sender end.

Hence, IMHO the question of what should be handled at the
Message-Level, and what should be handled at the Session-Level, is
best decided by the operator... as above.

Further, this approach would allow the requirements to avoid the
quicksand which is UPDATE message parsing.  [Huzzah !]

-----

The requirements could recommend new defaults for the classification
of errors.  There's no absolute need for this: given the ability to
choose something which suits them better, I'm sure operators will
happily enable what they want.

I guess any *default* would err on the side of caution, ie:
Message-Level Recovery is appropriate only where there is a
(vanishingly) small risk of "lost NLRI".

The appropriate default for a given session may depend on the
behaviour of the peer, which may be the subject of negotiation,
configuration or sweeping generalisation.

The requirements could recommend that UPDATE messages should be
altered to reduce the risk of "lost NLRI" or be generally more robust.
If that is constrained by the need for new-form UPDATE messages to be
downwards compatible with existing ones, the requirements should
mention that.  If the default classification depends on new sender
behaviour, I think that implies the requirement for a C.... but I
won't repeat that heresy :-)

I'm skirting around the quicksand here, I don't want to get sucked
down again...

Chris=20


From randy@psg.com  Wed Jan  2 16:03:55 2013
Return-Path: <randy@psg.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0BA21F8889; Wed,  2 Jan 2013 16:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 bKNwYH6815xe; Wed,  2 Jan 2013 16:03:55 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 966D721F8881; Wed,  2 Jan 2013 16:03:55 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TqYHq-0000SP-AY; Thu, 03 Jan 2013 00:03:54 +0000
Date: Thu, 03 Jan 2013 09:03:53 +0900
Message-ID: <m2zk0r9lp2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Wed, 02 Jan 2013 17:26:50 -0800
Cc: idr wg <idr@ietf.org>, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 00:03:56 -0000

> 1) in the (big) "Internet" space, lost NLRI are a huge deal for
> customers.

indeed.

> At some point, the equipment that is sending or receiving the BGP
> message will need to be maintained by the owner.

early.  i want to hear it from my network management system before i get
a call from the customer.

> We can not correct for every error, nor should we make that a goal as
> the results in writing the error handling code quickly get complex.

as a naggumite, i call this 'do-gooder' software.  when it does the
right thing, no one notices and says thanks.  when it does the wrong
thing, the flamage gets pretty hot, and justifiably so.

randy

From Donald.Smith@CenturyLink.com  Thu Jan  3 09:31:19 2013
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B25111E80D2; Thu,  3 Jan 2013 09:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.227
X-Spam-Level: 
X-Spam-Status: No, score=0.227 tagged_above=-999 required=5 tests=[SARE_SUB_OBFU_Q1=0.227]
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 wbEKciMAPFfK; Thu,  3 Jan 2013 09:31:18 -0800 (PST)
Received: from sudnp799.qwest.com (sudnp799.qwest.com [155.70.32.99]) by ietfa.amsl.com (Postfix) with ESMTP id 88C3911E809C; Thu,  3 Jan 2013 09:31:12 -0800 (PST)
Received: from lxdenvmpc030.qintra.com (lxdenvmpc030.qintra.com [10.1.51.30]) by sudnp799.qwest.com (8.14.4/8.14.4) with ESMTP id r03HV6Kq026146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jan 2013 10:31:07 -0700 (MST)
Received: from lxdenvmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id E10F91E0053; Thu,  3 Jan 2013 10:31:00 -0700 (MST)
Received: from suomp60i.qintra.com (unknown [151.119.91.93]) by lxdenvmpc030.qintra.com (Postfix) with ESMTP id A5C631E0071; Thu,  3 Jan 2013 10:31:00 -0700 (MST)
Received: from suomp60i.qintra.com (localhost [127.0.0.1]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id r03HV0Pf003479; Thu, 3 Jan 2013 11:31:00 -0600 (CST)
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.qintra.com [151.119.128.29]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id r03HUxL6003459 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Jan 2013 11:30:59 -0600 (CST)
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([2002:9777:801d::9777:801d]) with mapi id 14.02.0318.001; Thu, 3 Jan 2013 10:30:59 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "'Jeff Wheeler'" <jsw@inconcepts.biz>, "'Jakob Heitz'" <jakob.heitz@ericsson.com>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN54Kas8SJjgcJ/kuMjaNWVJ0hMJg33/hw
Date: Thu, 3 Jan 2013 17:30:58 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D0A29D756@PDDCWMBXEX503.ctl.intranet>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <20121231030925.GB62942@verdi> <CA+b+ERkYE61CSCxmZosxRO1LHhddRLsNmXYtB_nnBa8pVpy4Hw@mail.gmail.com> <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com> <CAPWAtb+v4W4qVQ6ceTdewc4u_nBOyZLztXe_m7vT_QCna2WWfQ@mail.gmail.com>
In-Reply-To: <CAPWAtb+v4W4qVQ6ceTdewc4u_nBOyZLztXe_m7vT_QCna2WWfQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.7]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'idr@ietf.org'" <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 17:31:19 -0000

"Pampers use multiple layers of protection to prevent leakage. Rommel used =
defense in depth to defend European fortresses." (A.White) Donald.Smith@Cen=
turyLink.com


>-----Original Message-----
>From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of
>Jeff Wheeler
>Sent: Monday, December 31, 2012 11:14 AM
>To: Jakob Heitz
>Cc: idr@ietf.org; grow@ietf.org
>Subject: Re: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-
>error-handling-06.txt
>
>On Mon, Dec 31, 2012 at 12:54 PM, Jakob Heitz <jakob.heitz@ericsson.com>
>wrote:
>> I don't think treat-as-withdraw is trying to fix a single session
>reset. Graceful restart can fix that. It's the rolling resets that need
>a human to remove a buggy router or a config that triggered the bug.
>That takes several hours. Treat-as-withdraw limits the damage during
>those hours.
>>
>> Could we please settle on that without trying to solve the impossible?
>
>If you read my posts to IDR on this topic, you'll see where I explain
>how it is possible to solve the "impossible."
>
>Specifically, you can ignore just about any bad update, or bad message
>of any kind, as long as you can figure out where the next message
>starts.  This fixes the rolling resets.
Exactly. Ignore (not treat as withdraw, not reset session, ...) seems the s=
anest approach to me also!

>
>You may know that a lot of businesses suffered multi-hour outages in
>October simply because of 5 DFZ routes announced by LANL that had
>illegal attributes.  This is very hard for operators to troubleshoot
>on most routers.  The routers that experienced rolling resets were
>buggy but if the operators simply had a panic button, "ignore bad
>messages," their networks would have been up and they would not have
>been losing money by the minute.
>
>This is not the only time bad updates have propagated through the DFZ
>and caused big problems.  It has happened repeatedly.
>
>I believe it will begin to happen more often inside datacenter
>networks, because BGP is being used for more and more things, like
>EVPN.  Operators are going to need BGP to become more robust.
>
>You can make it a lot more robust just by deciding to ignore
>everything in a bad message.  This is not good, but it is a lot better
>than session-reset, in most cases.
>
>Please, read my posts on this topic, and do not treat this problem as
>an unsolvable one.  It can be largely solved in a way that gives a
>very useful fallback option to operators.
>
>This whole draft is about fallback options, and it is pretty stupid to
>have a large amount of complexity to solve a small set of potential
>bugs, when you could ALTERNATIVELY or IN ADDITION to that, have a very
>low-complexity option that solves more problems.
>
>--
>Jeff S Wheeler <jsw@inconcepts.biz>
>Sr Network Operator  /  Innovative Network Concepts
>_______________________________________________
>Idr mailing list
>Idr@ietf.org
>https://www.ietf.org/mailman/listinfo/idr

From jared@puck.nether.net  Thu Jan  3 09:40:20 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32B1721F86DC; Thu,  3 Jan 2013 09:40:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.227
X-Spam-Level: 
X-Spam-Status: No, score=0.227 tagged_above=-999 required=5 tests=[SARE_SUB_OBFU_Q1=0.227]
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 Kcz-ukpTXrkU; Thu,  3 Jan 2013 09:40:19 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 73A6121F86D6; Thu,  3 Jan 2013 09:40:19 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r03HeFfd001462 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jan 2013 12:40:16 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com>
Date: Thu, 3 Jan 2013 12:40:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <806CF05A-6EBE-47FF-A6AA-F262A288DB3D@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 03 Jan 2013 12:40:17 -0500 (EST)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 17:40:20 -0000

Jeff,

On Jan 3, 2013, at 11:51 AM, Jeff Wheeler wrote:

> On Wed, Jan 2, 2013 at 12:56 PM, Tony Li <tony.li@tony.li> wrote:
>> While we can do SOME things to decrease session resets, we cannot fix =
all cases and simply treating things as a withdraw and walking away is =
wholly unacceptable, as some of you will hopefully agree.  Creating =
arbitrary hair here is NOT going to help as the error handling code =
itself will become fraught with errors.
>=20
> Tony,
>=20
> Every operator I've asked thinks "ignore bad BGP messages," which is
> even more extreme than treat-as-withdraw, is a good idea.

Not sure who you're asking, but I think this whole draft is an idealist =
attempt to workaround software defects that may be uncorrectable as a =
whole.  (I say this as a $large_operator as measured here: =
http://as-rank.caida.org/?mode0=3Das-ranking&n=3D10&ranksort=3D1 )

The missing prefix because it was ignored, or routing loop because a =
withdraw was ignored will quickly change these folks minds.

Take one of the most recent defects:

http://www.cisco.com/en/US/products/csa/cisco-sa-20100827-bgp.html

The device takes a valid route on the receive side and corrupts it as it =
forwards it.  While ignoring may be one solutions, there is no way to =
actually know or get remediation of this prefix and software defect.

There are 3 classes of BGP operators:

1) Core networks
2) Edge/Mid-tier networks
3) People using it as their IGP/datacenter/vpn/private networks (these =
may eventually connect to the internet, but those UPDATE messages won't =
necessarily reach)

> I'm not saying anyone thinks this would be a good default.  These
> things can just be knobs used when they are appropriate or necessary.
>=20

Methinks you underestimate the complexity that would be added to the =
error handling code.  While finding a marker/0xff may be easier, =
understanding the large block of updates in the flood of activity and =
low latency of large tcp windows make this much harder and more prone to =
error.

> Respectfully, you are about as wrong as one could get on this issue.
> Of course customers don't want one prefix to be broken.  Fifteen years
> of "CEF problem" have taught us all that these conditions are hard to
> troubleshoot.  However, it is often preferable to have one or many
> prefixes broken, than have a BGP session flap endlessly due to some
> bug.

For some operators, the only chance to workaround defects is to have =
something catastrophic happen to provide the justification to management =
to actually pick up the $new_software that corrects the problems you've =
been applying band-aids to.=20

There are many people who now are having trouble diagnosing network =
problems due to a workaround from early 2009:

http://puck.nether.net/pipermail/cisco-nsp/2009-February/058512.html

> The vendor should have some standards body coverage for giving the
> operator this knob, and customers are right to ask for it.  Sure,
> you're giving us more rope.  Sometimes that is what we need.

I'm generally in the more-rope camp, but this is effectively throwing =
out years of well worn code path and introducing new code (and likely =
defects) in the handling of error cases which can only make things =
worse.  There wasn't a broad-reaching bgp attribute problem in 2012 that =
i'm aware of, putting us in the "there is stability in the core" camp.  =
I'm seeing a well intentioned but unneeded element of meddling here.

People on the edge also need to learn to maintain their devices.  This =
isn't a standards body issue, and IMHO off-topic for here, but an =
important datapoint.

- Jared


From tony.li@tony.li  Thu Jan  3 10:02:15 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05FC021F8C6F for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 10:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.611
X-Spam-Level: 
X-Spam-Status: No, score=-97.611 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 VO60wk-DYope for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 10:02:14 -0800 (PST)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id 3D20321F8BCE for <grow@ietf.org>; Thu,  3 Jan 2013 10:02:13 -0800 (PST)
Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta01.emeryville.ca.mail.comcast.net with comcast id jQwt1k00416AWCUA1W2DXN; Thu, 03 Jan 2013 18:02:13 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta06.emeryville.ca.mail.comcast.net with comcast id jW001k00K52qHCY8SW02Bq; Thu, 03 Jan 2013 18:00:11 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com>
Date: Thu, 3 Jan 2013 10:00:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357236133; bh=y3WiVCV+pLSwvUOw3h1cPoCrlJXUT9kIRmuTLWPjf44=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=hd+I08qDiVXLKDAGykCAaMdojkonv5AsvDFwDbzsAMcOWbzB1nLPuMYQTeMqwDTzc J6PQ3kzceTrk7eVJKguCJ5F0lhw/n3qvwKZ4RZoCH7eD/L6maxA7sWUb6eSb6cCNKF RIpGtyETJqKWZOZ2WGUrNPv+SJW7OrkDJ8blhklkpNzd5xrF17260a5BTS31qrCG21 0w3ar8dkyxETeqBWtjQyGwI2iYn9GrvXWcAYIGAuIbUefJDjqxyRT9SMqg/vAYNUJe J3ubKcg57hor47WwXUHpldbOoGfo4avlMvOvEog67fCLJDRI6x31d7pB9R5EbdzDLg tXOg+rDCYHpCQ==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 18:02:15 -0000

Jeff,

>> While we can do SOME things to decrease session resets, we cannot fix =
all cases and simply treating things as a withdraw and walking away is =
wholly unacceptable, as some of you will hopefully agree.  Creating =
arbitrary hair here is NOT going to help as the error handling code =
itself will become fraught with errors.
>=20
> Every operator I've asked thinks "ignore bad BGP messages," which is
> even more extreme than treat-as-withdraw, is a good idea.


I'm sure if you asked folks if they wanted anything that helped them and =
completely ignored the costs, they would say yes.  However, if you want =
to make a reasonable, rational, and justified decision, you must =
consider the implications of the request.  That's what I'm asking.  =
Consider implementor input as well, because there are some practical =
considerations here.


> Respectfully, you are about as wrong as one could get on this issue.


Respectfully, I think you're misunderstanding my position completely.  =
My point is that a reasonable implementation cannot possibly live up to =
the expectations that you're setting up here.  To be specific, once an =
implementation loses the syntactic parsing of the data stream, =
realistically, the session is corrupt and an eventual reset is =
inevitable.  Or, in other words, BGP cannot possible ignore bad =
messages.  That's not the way it works.


> Of course customers don't want one prefix to be broken.  Fifteen years
> of "CEF problem" have taught us all that these conditions are hard to
> troubleshoot.  However, it is often preferable to have one or many
> prefixes broken, than have a BGP session flap endlessly due to some
> bug.


All of the marketing that you're doing here is positioning this as a =
'solution'.  It's not.  Yes, it will stop the flap, but it does NOTHING =
to fix or deal with the underlying bug.  All it does is gloss it over, =
and as such, it will have implications in the field whereby this papers =
over real bugs and we have now promoted BGP errors into RIB errors.  =
That's NOT making things easier to debug, that's just applying a =
band-aid.

A more constructive way to address the real problem here would be to =
talk about whether we should even re-establish the session after an =
error.  Long ago, we made an implementation decision to simply retry.  =
That would seem to be the real issue at hand.


> The vendor should have some standards body coverage for giving the
> operator this knob, and customers are right to ask for it.  Sure,
> you're giving us more rope.  Sometimes that is what we need.


Sorry, but the point of the standards body is to standardize PROTOCOL =
changes.  Everything that has been discussed here are IMPLEMENTATION =
ISSUES.  We don't standardize those, for very good reasons.  And the =
vendors need zero help from the IETF in making implementation issues.  =
If real customers want a particular behavior, they can always just ask =
for it, as always.


> Related to this, what is your plan for dealing with BGP Attribute
> re-ordering in the rewrite of RFC4760? =20


My plan?  My personal plan is to ban the use of all MP extensions, as =
all of that is simply evil and should be scrubbed off the face of the =
earth. =20

I'll be putting this in place as soon as I'm elected Emperor of the =
Universe.  ;-)


> Currently there is no
> mechanism for telling a BGP neighbor that you intend to send the
> MP-NLRIs before other Attributes.  Doing that goes against RFC4271's
> recommendations.  Relying on that behavior (e.g. for error-handling)
> is not possible unless the neighbor promises to do it.  Thus far,
> there seems to be no intent to allocate another Capability Code for
> this.  The MP-BGP Capabilities Optional Parameter was not designed to
> be extended to do other things besides announce to the neighbor what
> AFI/SAFIs it supports.


RFC 4271 doesn't require a specific ordering because it would be bad =
protocol design.  As soon as you require ordering, some implementation =
is going to check that ordering.  There will be more bugs that occur =
because the mandated ordering was not followed, and more sessions will =
be dropped.   As always, the right thing is to follow Postel's law: be =
liberal in what you accept. =20

Requiring a specific ordering in order to improve error handling is a =
bad tradeoff: you're creating a host of additional bugs so that you can =
try to simplify error handling on another set of bugs.

Tony



From jsw@inconcepts.biz  Thu Jan  3 08:52:10 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E797E21F8B37 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 08:52:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.741
X-Spam-Level: 
X-Spam-Status: No, score=-2.741 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 297qKddQ6VQs for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 08:52:10 -0800 (PST)
Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com [209.85.210.174]) by ietfa.amsl.com (Postfix) with ESMTP id 2916421F8C97 for <grow@ietf.org>; Thu,  3 Jan 2013 08:52:09 -0800 (PST)
Received: by mail-ia0-f174.google.com with SMTP id y25so12973348iay.33 for <grow@ietf.org>; Thu, 03 Jan 2013 08:52:00 -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 :content-transfer-encoding:x-gm-message-state; bh=zefhF1br2xZP4rK74IB34Dvho8Y8Xp0rwOXaLjFObRw=; b=D/8rDij4b0J4LkfFyjjFU/FAIPRWGDVLRWTJ7Goi70wT5xFdhpSK+myPQbcWfj1/PI mi2uGN1VhGHWzo8YKXElQ7Ex5pXi0H+rRWNnLCWaJUdiZ8NyTmUaZIEpTOg1z95pFw5/ vgVW5O1+J+VatkcxHSQ9NWdCv0SUXp4p8rF+QsrgRCumbfT0kUWpQU/7L1WDROB1Etil wAwTPn6Pu9nobJDhBqcf15aDrMFV/plTcaLTMeJVl/UQltV2/PbmtZTSCYpeGX/5AQ0a Ob4hZXbB4Qi6eslqqZVqv/axosoiiS466sEc0Hqw7RXj2ccSizCC1bUrok5ewyQ9jjRg fCNw==
MIME-Version: 1.0
Received: by 10.50.104.232 with SMTP id gh8mr42291503igb.45.1357231920166; Thu, 03 Jan 2013 08:52:00 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 08:51:59 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li>
Date: Thu, 3 Jan 2013 11:51:59 -0500
Message-ID: <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlJFm8hwX5T1vgShbXXHcvykRFY4EyDTL24NkfV9IY8ovBvTb/zRLfRH4huWCJNLASR6tAE
X-Mailman-Approved-At: Thu, 03 Jan 2013 10:08:17 -0800
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 16:52:11 -0000

On Wed, Jan 2, 2013 at 12:56 PM, Tony Li <tony.li@tony.li> wrote:
> While we can do SOME things to decrease session resets, we cannot fix all=
 cases and simply treating things as a withdraw and walking away is wholly =
unacceptable, as some of you will hopefully agree.  Creating arbitrary hair=
 here is NOT going to help as the error handling code itself will become fr=
aught with errors.

Tony,

Every operator I've asked thinks "ignore bad BGP messages," which is
even more extreme than treat-as-withdraw, is a good idea.

I'm not saying anyone thinks this would be a good default.  These
things can just be knobs used when they are appropriate or necessary.

Respectfully, you are about as wrong as one could get on this issue.
Of course customers don't want one prefix to be broken.  Fifteen years
of "CEF problem" have taught us all that these conditions are hard to
troubleshoot.  However, it is often preferable to have one or many
prefixes broken, than have a BGP session flap endlessly due to some
bug.

The vendor should have some standards body coverage for giving the
operator this knob, and customers are right to ask for it.  Sure,
you're giving us more rope.  Sometimes that is what we need.


Related to this, what is your plan for dealing with BGP Attribute
re-ordering in the rewrite of RFC4760?  Currently there is no
mechanism for telling a BGP neighbor that you intend to send the
MP-NLRIs before other Attributes.  Doing that goes against RFC4271's
recommendations.  Relying on that behavior (e.g. for error-handling)
is not possible unless the neighbor promises to do it.  Thus far,
there seems to be no intent to allocate another Capability Code for
this.  The MP-BGP Capabilities Optional Parameter was not designed to
be extended to do other things besides announce to the neighbor what
AFI/SAFIs it supports.

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

From rraszuk@gmail.com  Thu Jan  3 10:50:13 2013
Return-Path: <rraszuk@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB1021F869B; Thu,  3 Jan 2013 10:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.151
X-Spam-Level: 
X-Spam-Status: No, score=-0.151 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 WwLXTi8ZJ62X; Thu,  3 Jan 2013 10:50:12 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC6721F8692; Thu,  3 Jan 2013 10:50:12 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id k10so19107738iea.29 for <multiple recipients>; Thu, 03 Jan 2013 10:50:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ymgXddIZoNjrvsJBjE2MrnDKVnflbHMUP43cuklaT9M=; b=Mgqj/7ITIfUM7o4OvILBgZdINNajcg2lFAskXlBERDSFARHpq21Ly6X/nm8OabgqFf lNaNY4nxeObiEfAAb7rdYOYDoTkcgE2Nf93jOrt9gMvHQ39pUJbHFHb2rmbwLP9jGEjN 5+8zVsmU7oWiuz2wpIjcoHkN9bhciGrqViE4nTgenWbVqXD47fewraRz4Er67O4xrc4T orPj5e4hJbPEsRqV81ocjrI8APg5HaeQVPS7KqdzybAVX8h6MxtVko/+/LomGQH1SytM q7Kb9sYUGpzfXM76pS5jyd3Mz6qFQIZzvhed0/ad73whxHK3PJTn2VRpYJ7/1vxMiI22 aYGA==
MIME-Version: 1.0
Received: by 10.50.41.231 with SMTP id i7mr38648632igl.98.1357239008851; Thu, 03 Jan 2013 10:50:08 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.167.204 with HTTP; Thu, 3 Jan 2013 10:50:08 -0800 (PST)
In-Reply-To: <68EFACB32CF4464298EA2779B058889D0A29D756@PDDCWMBXEX503.ctl.intranet>
References: <025801cde4f6$d7783700$8668a500$@highwayman.com> <3B3C1AA7-40DB-4566-9BD0-C25E5845935D@rob.sh> <028701cde525$bf262070$3d726150$@highwayman.com> <CAH1iCip=sm9rEDw8GnmejWU62sLJ32MZNOJ6EPsyF9b1MQWCZg@mail.gmail.com> <EC5968D3-A05B-4942-BE7A-B0BF1277330A@rob.sh> <CAH1iCir+wpd2LP4dXXQWtXrOt4ZfuUMN4OU4FWWuGbD7nLErQg@mail.gmail.com> <20121231030925.GB62942@verdi> <CA+b+ERkYE61CSCxmZosxRO1LHhddRLsNmXYtB_nnBa8pVpy4Hw@mail.gmail.com> <6D642BD9-C87F-4987-9C32-0A4463E6A542@ericsson.com> <CAPWAtb+v4W4qVQ6ceTdewc4u_nBOyZLztXe_m7vT_QCna2WWfQ@mail.gmail.com> <68EFACB32CF4464298EA2779B058889D0A29D756@PDDCWMBXEX503.ctl.intranet>
Date: Thu, 3 Jan 2013 19:50:08 +0100
X-Google-Sender-Auth: YjteBN7nie4602ezDuGNnSjJiko
Message-ID: <CA+b+ERmjfNeHPA555F4WQZcpOqLMP0i8sqcVJBNGE+w2M0R3iQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "Smith, Donald" <Donald.Smith@centurylink.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, Jeff Wheeler <jsw@inconcepts.biz>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 18:50:13 -0000

> On Thu, Jan 3, 2013 at 6:30 PM, Smith, Donald <Donald.Smith@centurylink.com> wrote:
> Exactly. Ignore (not treat as withdraw, not reset session, ...) seems the sanest approach to me also!

That's equally good as starting to drill little holes in the ship in
the middle of ocean. Sure it will still swim for a while, but when it
starts to drown it will be too late.

You may as well run BGP over UDP and have app level acks for received
datagrams. Problem solved - no sessions resets to worry about.

Cheers,
R.

From mlong@us.ntt.net  Thu Jan  3 11:35:56 2013
Return-Path: <mlong@us.ntt.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53BAA21F8D00; Thu,  3 Jan 2013 11:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.308
X-Spam-Level: 
X-Spam-Status: No, score=-0.308 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HOST_MISMATCH_NET=0.311, RDNS_DYNAMIC=0.1, SARE_SUB_OBFU_Q1=0.227]
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 ZRJXgSD+MOB7; Thu,  3 Jan 2013 11:35:55 -0800 (PST)
Received: from destroyer.troyspaws.com (destroyer.troyspaws.com [IPv6:2001:418:c01::27]) by ietfa.amsl.com (Postfix) with ESMTP id A765321F8CFF; Thu,  3 Jan 2013 11:35:55 -0800 (PST)
Received: from [192.168.1.108] (99-16-97-27.lightspeed.snrsca.sbcglobal.net [99.16.97.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by destroyer.troyspaws.com (Postfix) with ESMTP id B49515C207E5; Thu,  3 Jan 2013 19:35:54 +0000 (GMT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Michael Long <mlong@us.ntt.net>
In-Reply-To: <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li>
Date: Thu, 3 Jan 2013 11:35:54 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li>
To: Tony Li <tony.li@tony.li>
X-Mailer: Apple Mail (2.1499)
Cc: idr@ietf.org, grow@ietf.org, Jeff Wheeler <jsw@inconcepts.biz>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 19:35:56 -0000

On Jan 3, 2013, at 10:00 AM, Tony Li <tony.li@tony.li> wrote:
>=20
>=20
> All of the marketing that you're doing here is positioning this as a =
'solution'.  It's not.  Yes, it will stop the flap, but it does NOTHING =
to fix or deal with the underlying bug.  All it does is gloss it over, =
and as such, it will have implications in the field whereby this papers =
over real bugs and we have now promoted BGP errors into RIB errors.  =
That's NOT making things easier to debug, that's just applying a =
band-aid.

I understand what you are saying and I agree 100%, however, from an my =
operations perspective the "fix" is the same. Either upgrade to fixed =
code or policy out the offending announcement. I would rather deal with =
a customer routing issue vs a frantic call from our noc saying 15+ att =
peers globally are bouncing. The latter being a much bigger impact on =
our network.=20

I can live with a couple of /24's not working for a few customers. I =
can't have 15+ peers bouncing because of bad updates and even more peers =
bouncing because of missed keepalives due to cpu pegged trying to deal =
with 15 peers bouncing globally.=20

>=20
> A more constructive way to address the real problem here would be to =
talk about whether we should even re-establish the session after an =
error.  Long ago, we made an implementation decision to simply retry.  =
That would seem to be the real issue at hand.

I would back this provided adequate logging as to why the session is =
down. It would be much like tripping max-prefixes where we could hard =
clear a single single session for debug. I could live with this.=20

Mike
--=20
Michael Long
NTT Communications Global IP Network
ph. 214.915.1352
jabber: mlong@jabber.gin.ntt.net




From enkechen@cisco.com  Thu Jan  3 11:36:11 2013
Return-Path: <enkechen@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA6C21F8D2C; Thu,  3 Jan 2013 11:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.371
X-Spam-Level: 
X-Spam-Status: No, score=-10.371 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
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 0WYfkjA70Y4L; Thu,  3 Jan 2013 11:36:10 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 209A421F8CFF; Thu,  3 Jan 2013 11:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3448; q=dns/txt; s=iport; t=1357241769; x=1358451369; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=tmfAlhV/UsZ2PAH0VdMoXbPYKjzL83DzcRz7urYMtjg=; b=c97EXntFX7X5AKqxfMzPhh0aVdhLA5UkgVpFrM1Rv0xuNxquGxt0+q3S 3n8DwgkvwTlvq8kf+GpOGRx5VBGu2z9MWEcqkBUiYLt72aY+5Mahm4etl lCLthmhEgNV0JeOQcselQu5xtlwMylOC5VZsHvPiVFVZYYswFh+nF+3E1 k=;
X-IronPort-AV: E=Sophos;i="4.84,404,1355097600"; d="scan'208,217";a="22767278"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 03 Jan 2013 19:36:07 +0000
Received: from [171.71.139.31] (dhcp-171-71-139-31.cisco.com [171.71.139.31]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r03Ja40n021644; Thu, 3 Jan 2013 19:36:05 GMT
Message-ID: <50E5DDA3.5060709@cisco.com>
Date: Thu, 03 Jan 2013 11:36:03 -0800
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Jeff Wheeler <jsw@inconcepts.biz>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <806CF05A-6EBE-47FF-A6AA-F262A288DB3D@puck.nether.net> <CAPWAtbKUne9PNmnyLzbEeJQ8VBFv0geab+v3S7T8DCsDTdUWtw@mail.gmail.com>
In-Reply-To: <CAPWAtbKUne9PNmnyLzbEeJQ8VBFv0geab+v3S7T8DCsDTdUWtw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030105080406040904070108"
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 19:36:11 -0000

This is a multi-part message in MIME format.
--------------030105080406040904070108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi, Jeff:

On 1/3/13 11:22 AM, Jeff Wheeler wrote:

[snip]

>
>> Respectfully, I think you're misunderstanding my position completely.  My point is that a reasonable implementation cannot possibly live up to the expectations that you're setting up here.  To be specific, once an implementation loses the syntactic parsing of the data stream, realistically, the session is corrupt and an eventual reset is inevitable.  Or, in other words, BGP cannot possible ignore bad messages.  That's not the way it works.
> Of course BGP can ignore bad messages.  To say otherwise is simply
> telling a lie because you haven't made a good argument.
>
>

A good argument (IMO) has been made in the error handling draft:

---------
http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/

4. Operational Considerations

    Note that "treat-as-withdraw" is different from discarding an UPDATE
    message.  The latter violates the basic BGP principle of incremental
    update, and could cause invalid routes to be kept.  (See also
    Appendix A.)

---------

-- Enke


--------------030105080406040904070108
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">hi, Jeff:<br>
      <br>
      On 1/3/13 11:22 AM, Jeff Wheeler wrote:<br>
      <br>
      [snip]<br>
      <br>
    </div>
    <blockquote
cite="mid:CAPWAtbKUne9PNmnyLzbEeJQ8VBFv0geab+v3S7T8DCsDTdUWtw@mail.gmail.com"
      type="cite"><br>
      <blockquote type="cite">
        <pre wrap="">Respectfully, I think you're misunderstanding my position completely.  My point is that a reasonable implementation cannot possibly live up to the expectations that you're setting up here.  To be specific, once an implementation loses the syntactic parsing of the data stream, realistically, the session is corrupt and an eventual reset is inevitable.  Or, in other words, BGP cannot possible ignore bad messages.  That's not the way it works.
</pre>
      </blockquote>
      <pre wrap="">
Of course BGP can ignore bad messages.  To say otherwise is simply
telling a lie because you haven't made a good argument.


</pre>
    </blockquote>
    <br>
    A good argument (IMO) has been made in the error handling draft:<br>
    <br>
    ---------<br>
    <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/">http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/</a><br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre><span class="m_h">4. Operational Considerations</span></pre>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre>   Note that "treat-as-withdraw" is different from discarding an UPDATE
   message.  The latter violates the basic BGP principle of incremental
   update, and could cause invalid routes to be kept.  (See also
   Appendix A.)</pre>
    ---------<br>
    <br>
    -- Enke<br>
    <br>
  </body>
</html>

--------------030105080406040904070108--

From jared@puck.nether.net  Thu Jan  3 11:58:07 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E75621F85ED; Thu,  3 Jan 2013 11:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.073
X-Spam-Level: 
X-Spam-Status: No, score=-1.073 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 3eNXp7CLDyNy; Thu,  3 Jan 2013 11:58:06 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 4711921F85E8; Thu,  3 Jan 2013 11:58:06 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r03Jw2WX026264 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jan 2013 14:58:03 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net>
Date: Thu, 3 Jan 2013 14:58:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A29FF9DC-358E-4CD0-8931-D9B890CB8A6F@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net>
To: Michael Long <mlong@us.ntt.net>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 03 Jan 2013 14:58:04 -0500 (EST)
Cc: idr@ietf.org, grow@ietf.org, Jeff Wheeler <jsw@inconcepts.biz>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 19:58:07 -0000

On Jan 3, 2013, at 2:35 PM, Michael Long wrote:

>=20
> On Jan 3, 2013, at 10:00 AM, Tony Li <tony.li@tony.li> wrote:
>>=20
>>=20
>> All of the marketing that you're doing here is positioning this as a =
'solution'.  It's not.  Yes, it will stop the flap, but it does NOTHING =
to fix or deal with the underlying bug.  All it does is gloss it over, =
and as such, it will have implications in the field whereby this papers =
over real bugs and we have now promoted BGP errors into RIB errors.  =
That's NOT making things easier to debug, that's just applying a =
band-aid.
>=20
> I understand what you are saying and I agree 100%, however, from an my =
operations perspective the "fix" is the same. Either upgrade to fixed =
code or policy out the offending announcement. I would rather deal with =
a customer routing issue vs a frantic call from our noc saying 15+ att =
peers globally are bouncing. The latter being a much bigger impact on =
our network.=20

I'm very concerned with the case of ignoring a route update and having a =
month-long discussion about why some route is missing from the =
$carrier_a network when it's being sent from $carrier_b and they show it =
going out just fine.

You don't know there's an issue until someone reports it and your =
long-tail to problem resolution takes forever.

> I can live with a couple of /24's not working for a few customers. I =
can't have 15+ peers bouncing because of bad updates and even more peers =
bouncing because of missed keepalives due to cpu pegged trying to deal =
with 15 peers bouncing globally.=20

While related, this is an implementation defect on the part of vendors =
and their poorly optimized TCP and BGP implementations being unable to =
get their basic job done.  I recall vendors blaming our "slow" system =
CPU then finally fixing their logic defect that always returned 1 or 0 =
when it thought it was idle.  (sometimes those if statements look really =
complex).

>> A more constructive way to address the real problem here would be to =
talk about whether we should even re-establish the session after an =
error.  Long ago, we made an implementation decision to simply retry.  =
That would seem to be the real issue at hand.
>=20
> I would back this provided adequate logging as to why the session is =
down. It would be much like tripping max-prefixes where we could hard =
clear a single single session for debug. I could live with this.=20

I certainly agree there needs to be better logging from the vendors.

I remain convinced that attempts to address this problem will create =
more complex situations vs provide the desired result of a stable BGP =
core.

- Jared=

From rraszuk@gmail.com  Thu Jan  3 12:18:17 2013
Return-Path: <rraszuk@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3BDB21F8CD7; Thu,  3 Jan 2013 12:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level: 
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 IfNanO1TUf-S; Thu,  3 Jan 2013 12:18:17 -0800 (PST)
Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id B686C21F86AA; Thu,  3 Jan 2013 12:18:10 -0800 (PST)
Received: by mail-ia0-f182.google.com with SMTP id x2so13202059iad.13 for <multiple recipients>; Thu, 03 Jan 2013 12:18:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=MbNSvARGedGHiab26we4mCykbiJitAMaucTvgM4brHU=; b=KR62OOCr7dI6sD+p+RkfUBuCBTHSYac3wjakS/LDLhJ8n02rP1JIxZyP6LTBfv1ACb xF24rCpg6wvi9hMM+DMBRZ20piS04TEOBzWKrdBiqA1HUbXnedkzV7wzWAq5hdK9e9p/ E43+ZVib4TwNWVYeu3k5QBkBm6gqpDrps9rx0QVTEY9r9Wb+4mjNR8dGGS87MRcH81iT tyX3+bTdyMT7l75DzTMGGYsWW1dkzQjHiAF+RM5I2bDsYiZNZVfzu9tSj0I7HD6KGscR 9Gk39vPvkY4iyIFT7v0lIDAuDeWZVAeLAWoX8I/KFeZdMh8xQ+IP/aira9FSXkU3nRys MwHQ==
MIME-Version: 1.0
Received: by 10.50.41.231 with SMTP id i7mr38835124igl.98.1357244290134; Thu, 03 Jan 2013 12:18:10 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.167.204 with HTTP; Thu, 3 Jan 2013 12:18:09 -0800 (PST)
In-Reply-To: <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com>
Date: Thu, 3 Jan 2013 21:18:09 +0100
X-Google-Sender-Auth: 4OwqZ3nXQyPDJbfOjCmu3zpLDrU
Message-ID: <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Jeff Wheeler <jsw@inconcepts.biz>
Content-Type: text/plain; charset=ISO-8859-1
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 20:18:17 -0000

Hi Jeff,

> Ignore-bad-message is very simple and provides a band-aid for more
> problems, including unforeseen problems.

How are you going to clean the NLRIs in your network (both transit or
stub) which were withdrawn in the messages your BGP implementation
declared "bad" and decided to ignore ?

r.

From jared@puck.nether.net  Thu Jan  3 13:28:05 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3874621F86C3; Thu,  3 Jan 2013 13:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level: 
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 LmQIy8dE6AyR; Thu,  3 Jan 2013 13:28:04 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 9028B21F865B; Thu,  3 Jan 2013 13:28:04 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r03LS1Qv007713 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jan 2013 16:28:02 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
Date: Thu, 3 Jan 2013 16:28:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 03 Jan 2013 16:28:02 -0500 (EST)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 21:28:05 -0000

On Jan 3, 2013, at 4:19 PM, Jeff Wheeler wrote:

> On Thu, Jan 3, 2013 at 3:18 PM, Robert Raszuk <robert@raszuk.net> =
wrote:
> > How are you going to clean the NLRIs in your network (both transit =
or
> > stub) which were withdrawn in the messages your BGP implementation
> > declared "bad" and decided to ignore ?
>=20
> I can fix them later, maybe even after I've had time to fully analyze =
the problem and get a software update from my vendor.  Maybe I'll try a =
refresh or a session-reset, but I won't be at the mercy of repeatedly =
flapping session and phone ringing off the hook with angry customers!

They're going to complain no matter what.

Also, if you're not a fully-peered DFZ ISP, perhaps you don't need full =
routes to make your decisions anyways.

I am sympathetic to a point, but either way someone has to look at the =
problem and correct it (likely with a code spin) assuming you don't take =
the offending device offline.

This is the shared fate everyone has in the BGP world for the =
distributed online database we operate.

Also, if you're seeing some problem, I'm sure that some other set of =
people out there will be seeing it as well.  The shared pain/cost will =
exist.  If you can't take the risk of speaking BGP, have your ISP send =
you default (or nothing) and advert your prefixes and call it a day.

- jared=

From rraszuk@gmail.com  Thu Jan  3 13:28:44 2013
Return-Path: <rraszuk@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B20121F86C3; Thu,  3 Jan 2013 13:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 ADWpExsvSxHa; Thu,  3 Jan 2013 13:28:43 -0800 (PST)
Received: from mail-ia0-f173.google.com (mail-ia0-f173.google.com [209.85.210.173]) by ietfa.amsl.com (Postfix) with ESMTP id 21B8321F865B; Thu,  3 Jan 2013 13:28:43 -0800 (PST)
Received: by mail-ia0-f173.google.com with SMTP id w21so13254803iac.18 for <multiple recipients>; Thu, 03 Jan 2013 13:28:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=epRXKGXvCn3gccj9mn/2neVz9496J5B6ZPbsnBWlnw0=; b=AgmllRDzbP7+UPlqzqwDa0tpU3qVEaQvXNmDRnFufYEoxK/urMmu2Mdiz3DCPJjLec KmZ6k1aUu7rl+7oCJeObWLtnp4YYBOwAvB0GCH7sdtfu2H5TdhASdbYrFacEflm0xsno CpsTy7CltXnKF7TAIqBFAr4r2SrNzT33f9fJT6fzP/BYcpoXXxujxm08xq56MuRr8z4Z EEzFJRWqITBxMTSCYxASaZdOIZB42p0asTyVIWyc3srG6Lxc4InoC4sVdajxj8Njn+/2 O8fWvLRfWDXJeiwiVc/IUMFwPXV0itfvsceWyCpdZUGpmt5nu3WN1oVJbllDiFeNhL+Q NEvg==
MIME-Version: 1.0
Received: by 10.50.94.134 with SMTP id dc6mr38291492igb.80.1357248522216; Thu, 03 Jan 2013 13:28:42 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.167.204 with HTTP; Thu, 3 Jan 2013 13:28:42 -0800 (PST)
In-Reply-To: <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
Date: Thu, 3 Jan 2013 22:28:42 +0100
X-Google-Sender-Auth: zu81QcNrGPlweIRUKrEKnyiZUqg
Message-ID: <CA+b+ER=tbx9xm4ysQo3NX1ePxuNJgZDdLGo=_W8xUPCCXD2qsA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Jeff Wheeler <jsw@inconcepts.biz>
Content-Type: text/plain; charset=ISO-8859-1
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 21:28:44 -0000

Jeff,

> I can fix them later, maybe even after I've had time to fully analyze the
> problem and get a software update from my vendor.

Well that assumes you have even noticed the problem in the first place.

On the point of flapping - completely agree. But the knob - already
available in some implementations - not to flap, but to keep the
session down till manual intervention - is completely different thing
and this is completely safe solution from protocol correctness pov.

--

Yes I understand your motivations, but the problem with BGP doing
things like treat-as-withdraw by default are really not what you are
describing.

Cheers,
R.




On Thu, Jan 3, 2013 at 10:19 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:
> On Thu, Jan 3, 2013 at 3:18 PM, Robert Raszuk <robert@raszuk.net> wrote:
>> How are you going to clean the NLRIs in your network (both transit or
>> stub) which were withdrawn in the messages your BGP implementation
>> declared "bad" and decided to ignore ?
>
> I can fix them later, maybe even after I've had time to fully analyze the
> problem and get a software update from my vendor.  Maybe I'll try a refresh
> or a session-reset, but I won't be at the mercy of repeatedly flapping
> session and phone ringing off the hook with angry customers!
>
> A lot of folks are thinking about this problem in the context of the big
> carrier who doesn't want a hard-to-diagnose problem of 1 RIB entry being
> wrong.  That's okay, it is one way to think about it.
>
> A second way to think of it is as a small/regional ISP.  If one or more of
> his transits are flapping because of a bad path on the DFZ, that is going to
> cost him money and customers.  If he has no way to mitigate it, he is at the
> mercy of external parties.  He could just use "ignore bad messages" and at
> least stop bleeding money.  He does not care if he can't reach  5 /24s at
> LANL, they are unimportant to him.  What is important is if he has any
> customers left next week.
>
> A third way is the small- or medium-datacenter network.  Imagine you are a
> typical small/medium shop and you have some Cisco/Juniper/Brocade stuff for
> your ASBRs and your core, but you bought a bunch of RainbowPoop Router Co
> switches for your racks, because they are inexpensive and they support EVPN,
> L3VPN, VPLS, or some other feature you want but Cisco/Juniper/Brocade don't
> put into their inexpensive product.
>
> So your network looks like this:
>
> ISP1    ISP2
>
>   CISCO  JUNIPER
>   |    \/
>   |    /\                \   |
>   |   /  \                \  |
>   TOR1    TOR2    ....    TOR99
>
> Now imagine your JUNIPER supports NewVpnThing and that's a feature you
> decided to use on the RainbowPoop TOR devices.  But TOR1 sends a bad BGP
> update.  JUNIPER knows about NewVpnThing and sees a bad BGP attribute (that
> it recognizes) so it does whatever the NewVpnThing spec says, and tears down
> the session to TOR1.
>
> CISCO on the other hand, does not know about NewVpnThing so this router
> doesn't even understand the update is bad.  It just passes it along to TOR2
> .. TOR99.  Now those boxes all tear down their session to the CISCO.  Then
> they re-establish.  Then they go down again.  They keep on doing this and
> the network is freaking out.
>
> By the time your in-house clue notices, your symptom is that 99 identical
> TORs are flapping their BGP to your CISCO.  You probably don't even notice
> the 1 TOR that is flapping to JUNIPER.  Maybe JUNIPER even logs something
> helpful but you may not investigate it for a while.
>
> So your CISCO which is following the base spec is carrying a buggy update to
> your 99 other RainbowPoop TORs and they are all failing.  Your JUNIPER which
> knows about the NewVpnThing is following its spec and protecting the other
> TORs from this problem, but it is probably not helpful since your network is
> in chaos from all the flapping.
>
> What do you do?  Call vendor support.  Probably for CISCO and RainbowPoop.
> Well, now you are expecting the TAC of Cisco and the TAC of RainbowPoop to
> cooperate, which they'll have trouble doing; and it may take ages before
> anyone identifies the root cause of the problem is really TOR1.
>
> There are going to be a lot of RainbowPoop routers in the future, and many
> of them may use BGP.  We should make BGP more robust.
>
>
> --
> Jeff S Wheeler <jsw@inconcepts.biz>
> Sr Network Operator  /  Innovative Network Concepts
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>

From jared@puck.nether.net  Thu Jan  3 14:05:36 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 272D721F8D8C; Thu,  3 Jan 2013 14:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.939
X-Spam-Level: 
X-Spam-Status: No, score=-1.939 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 kN01FY0p9dq4; Thu,  3 Jan 2013 14:05:35 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFF721F8D87; Thu,  3 Jan 2013 14:05:35 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r03M5S5g012806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jan 2013 17:05:29 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com>
Date: Thu, 3 Jan 2013 17:05:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 03 Jan 2013 17:05:29 -0500 (EST)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:05:36 -0000

On Jan 3, 2013, at 5:01 PM, Jeff Wheeler wrote:

> On Thu, Jan 3, 2013 at 4:28 PM, Jared Mauch <jared@puck.nether.net> =
wrote:
>> Also, if you're seeing some problem, I'm sure that some other set of
>> people out there will be seeing it as well.  The shared pain/cost =
will
>> exist.  If you can't take the risk of speaking BGP, have your ISP =
send you
>> default (or nothing) and advert your prefixes and call it a day.
>=20
> There may be no shared pain if you are using BGP only within your
> datacenter network.  This is precisely why I provided the RainbowPoop
> scenario.  This is not your 1990s BGP anymore.  Anyone who has MPLS
> VPNs signaled using BGP already knows this but maybe isn't cognizant
> of it in this context.
>=20
> You continue to make this argument that breaking your network so you
> notice a problem is good.  I would like to have the option to notice
> the problem by actually parsing my syslogs and NOT having my network
> break and cost me and customers a bunch of money.  That's not what I
> would really do, though.  I would just re-actively configure
> ignore-bad-messages if I needed to.  Because I agree with you, I would
> like BGP to flap if something unexpected happens.  However, I might
> need to stop it from flapping to remain in business.

Oh, I understand all these use-cases, but there is a case for a =
well-designed network not always sharing/mixing the NLRI.  eg: We don't =
transport v4 NLRI in v6 transport, nor v6 NLRI in v4 transport.  If you =
have a single session with massive shared fate, perhaps it's not a =
protocol design error but a network design error.

- Jared=

From tony.li@tony.li  Thu Jan  3 14:07:49 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27DD321F8CE8 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:07:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.911
X-Spam-Level: 
X-Spam-Status: No, score=-98.911 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 rLsh35UdvjD0 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:07:48 -0800 (PST)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by ietfa.amsl.com (Postfix) with ESMTP id 772CD21F8CD8 for <grow@ietf.org>; Thu,  3 Jan 2013 14:07:48 -0800 (PST)
Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta15.emeryville.ca.mail.comcast.net with comcast id jToH1k0051eYJf8AFa7oCl; Thu, 03 Jan 2013 22:07:48 +0000
Received: from [10.155.35.198] ([128.107.239.234]) by omta19.emeryville.ca.mail.comcast.net with comcast id ja5a1k00L547xYo01a5cFv; Thu, 03 Jan 2013 22:05:45 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <051801cde9fc$228a93f0$679fbbd0$@highwayman.com>
Date: Thu, 3 Jan 2013 14:05:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <02C95055-0597-4574-AF2E-F6AB5C473051@tony.li>
References: <051801cde9fc$228a93f0$679fbbd0$@highwayman.com>
To: "Chris Hall" <chris.hall@highwayman.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357250868; bh=7tj3GwFVwtE7RDKCQog3ZQHc3DOQyf6eTzqMSqFnD/M=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=ttdY3l/QkUi2GG8fms9WFS1dR1Ltvpz+BzRO1gRfwG7EQDzVFHURiCsySOsHDoWVG AWjq/Oj4plT1lGLGJ68J1Rgi8cP+xaSOKhIhdgH2R1xdc1CLkAnjpH54wPNkb38Ru3 +gWDMy/G/cQ5N8E7JYI6qysuVEFi56VTXGWUFfx5ewvVRhROpeeACeKOyR6j94aAi/ pN+qcCsuDEQXenNcuuxUjOfdg4Kke7il8RJhWf4EuBzt4fjGKNQ9jpkHDS/MxrvM6k 7/qx9BV+TTA3Nauf3GV47d+ajg/rjIfnw8qiJii2eE/UWnuvkUZ3Fz/R6q530fomL1 flJ2mdfUWBLXQ==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:07:49 -0000

On Jan 3, 2013, at 1:48 PM, "Chris Hall" <chris.hall@highwayman.com> =
wrote:

> However bad or difficult to clean up, what if that's not as bad as the
> alternative ?


Clearly, the treat-as-withdraw alternative is better.  You're not =
leaving bogus state in the rest of the network.

Tony


From jsw@inconcepts.biz  Thu Jan  3 14:15:51 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 963A321F8D75 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:15:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level: 
X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 LTxLIOIOGnmF for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:15:50 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7F09921F8DB7 for <grow@ietf.org>; Thu,  3 Jan 2013 14:15:44 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so13424289iaz.31 for <grow@ietf.org>; Thu, 03 Jan 2013 14:15:40 -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 :content-transfer-encoding:x-gm-message-state; bh=s2vl52g4iRiszy6f1UOL2fLIFIOxsgyXobP7inM8JGs=; b=pexDcLppaG/Zqjak2Wi236XXGE49ClwslhbaVnfUuLfsOx4y9g971FVqVXa8aVtkUE lj6rzoAh+1habTpvg4fWy88Sai10bMpyAWdWxo2HjKxknm43zQ2KhCzfO13yXONUMqg1 PIidIqhPQ73FTRuHe0M7kMcmz4NlZzMdNcKL9r5Uae4S4CmaJON6B6GrIxz7egzmAogU jKSeG6yTOP/I3GFfac5tw8dCnHfyHGwfEI2sqIfQo2XrcvTA1BcxtMgNv95aioPOH3xC KP/9aPcT64yq0f4o4ICwNAu1mPeJv6h9jV8BYTmSIdBM4gQjMsgIp4rrvlxc/g/4/ZTi Ftpw==
MIME-Version: 1.0
Received: by 10.50.104.232 with SMTP id gh8mr42965712igb.45.1357251340401; Thu, 03 Jan 2013 14:15:40 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 14:15:40 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net>
Date: Thu, 3 Jan 2013 17:15:40 -0500
Message-ID: <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Jared Mauch <jared@puck.nether.net>, Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQngDEoHZTFMoGbNOay+KdvBrbAv56dEXIIUQUXpPkW2Coi7jy5BewWaIxjiBSrAa68Ls6i0
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:15:51 -0000

On Thu, Jan 3, 2013 at 5:05 PM, Jared Mauch <jared@puck.nether.net> wrote:
> Oh, I understand all these use-cases, but there is a case for a well-desi=
gned network not always sharing/mixing the NLRI.  eg: We don't transport v4=
 NLRI in v6 transport, nor v6 NLRI in v4 transport.  If you have a single s=
ession with massive shared fate, perhaps it's not a protocol design error b=
ut a network design error.

it is not just a shared-fate problem.  Even if you have distinct BGP
sessions per AFI, the RainbowPoop scenario still breaks the datacenter
network if they actually depend on NewVpnThing.  Most networks will
still have a very hard time troubleshooting it, and they'll be
bleeding customers until they do.

I noticed you've omitted MPLS VPNs.  We also do not use the same BGP
sessions for IPv4 and IPv6, but we do use IPv4 sessions for MPLS VPNs.
 It is avoidable but I would bet that most networks do not avoid it.
Do yours?

On Thu, Jan 3, 2013 at 5:05 PM, Tony Li <tony.li@tony.li> wrote:
> On Jan 3, 2013, at 1:48 PM, "Chris Hall" <chris.hall@highwayman.com> wrot=
e:
>> However bad or difficult to clean up, what if that's not as bad as the
>> alternative ?
>
> Clearly, the treat-as-withdraw alternative is better.  You're not leaving=
 bogus state in the rest of the network.

Does this mean you support treat-as-withdraw, even though you dislike
its high complexity?  My read of your postings today is that you
dislike the whole error-handling idea.

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

From tony.li@tony.li  Thu Jan  3 14:18:35 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DDC21F8D87 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:18:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.777
X-Spam-Level: 
X-Spam-Status: No, score=-99.777 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 9KRPCIpuuPh4 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:18:34 -0800 (PST)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2CF21F886D for <grow@ietf.org>; Thu,  3 Jan 2013 14:18:34 -0800 (PST)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta01.emeryville.ca.mail.comcast.net with comcast id jS3w1k00B1wfjNsA1aJaHR; Thu, 03 Jan 2013 22:18:34 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta23.emeryville.ca.mail.comcast.net with comcast id jaGK1k00e52qHCY8jaGNNj; Thu, 03 Jan 2013 22:16:32 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
Date: Thu, 3 Jan 2013 14:16:19 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4E7344B-FF83-4CC2-AF46-A5B9640763D1@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357251514; bh=pRCmZq2SX0RoJ70Nns1pppVpU9/pNXuASb0NnQXd/4U=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=cLKQ34J9s8NCffDi++mtJsvJgdbOhtE1M6p25qfe3j8lAKGeDz9KUpgOnUv1NlL+m 3XoFUm7vvZNUX19DRgfHVbh/BBbOq7yNTLHox+qghtw/JII00RIpSwuvdOaWxsPIXa L3ZDaXYnjmkdC7l3E7qwXuvhEFdTR7zBvA1R0GEaKnIWxXoMc8Lxemyk3Mb5aOO99T dIfwa3YSSsmsxvBriICorvF3ClxSqGkrnIdJfo1Gr3s3l4DePqU6M5ZD/I8+0laq1s 3bEIoUckwgdQkKsif/3oGMIce6mkBnylqC6M12Ck/AjLThKURz383pC89s35xyVi4B dd7VNjhkVvvBQ==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:18:35 -0000

On Jan 3, 2013, at 1:19 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:

> A lot of folks are thinking about this problem in the context of the =
big carrier who doesn't want a hard-to-diagnose problem of 1 RIB entry =
being wrong.  That's okay, it is one way to think about it.


Unfortunately, the code is NOT going to be that sensitive to the =
variations of the use case.  The same code that the Tier 1 carrier is =
using is the same code on much smaller systems.  We need to find a =
behavior that is amenable to all.


> We should make BGP more robust.


I'm glad we agree on one thing.

Tony


From jsw@inconcepts.biz  Thu Jan  3 14:23:58 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D29521F8CFE for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.668
X-Spam-Level: 
X-Spam-Status: No, score=-2.668 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 DIxMi-5UPeCR for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:23:57 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 91BB121F8626 for <grow@ietf.org>; Thu,  3 Jan 2013 14:23:57 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so13431280iaz.31 for <grow@ietf.org>; Thu, 03 Jan 2013 14:23:56 -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=EXIk5F39lNII/LpoAL/mXwr5+LR2dAnLc9oy0oSAsaQ=; b=jcIqJ+gS04OOEhASUCQViV7zdd6f3TJgD4DF6z1phWhAbN1WjcWkFPTjjyYy4euqpU lVr9jgAO9u+Kb77bi1eRdaysmo8Wrm0iaoP8OnkmbKo8YvSbdomDMcmAYaXSVJhTGc/d ggF4XgZ4JIsnEJVnWYYVndTtMgw+yEPapDnn7HNRWrw7GQ0vgM+IwjPWZ7MnOeAZiztE /yuIOrduKKtD4QJVjZ9zRIGzkRET+yJz+y4efe59ceKOtGKWWdeDx83sBB/a60/k9E1N U/hDX6x/5kc7A3xU5joF5GhE+uoxSHEohAfFh8D2NsxFBeSj0CeUr6p3mRpNVFm6ksfM i9SA==
MIME-Version: 1.0
Received: by 10.50.152.240 with SMTP id vb16mr42603328igb.45.1357251836882; Thu, 03 Jan 2013 14:23:56 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 14:23:56 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <E4E7344B-FF83-4CC2-AF46-A5B9640763D1@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <E4E7344B-FF83-4CC2-AF46-A5B9640763D1@tony.li>
Date: Thu, 3 Jan 2013 17:23:56 -0500
Message-ID: <CAPWAtbL3eT9gPpkxERPrSNZH4a-as_fJi0+SBL0G7Ku=VeZNYg@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkGa5ZbrJMH9TAPDMSWGUmJvPXq3BbEL8zqw8khpuaHN1SOknczFvQnxFQaLGKqWz7iZit7
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:23:58 -0000

On Thu, Jan 3, 2013 at 5:16 PM, Tony Li <tony.li@tony.li> wrote:
> Unfortunately, the code is NOT going to be that sensitive to the variations of the use case.  The same code that the Tier 1 carrier is using is the same code on much smaller systems.  We need to find a behavior that is amenable to all.

One behavior may not suit all cases.  That's why we have options.

If we only had one router I guess it would be the biggest, most
expensive router possible; because big networks need these.
Fortunately vendors understand that they need to produce options to
suit different kinds of customers.  They also need to produce
configuration knobs to suit different kinds of customers.  This
standards body creates options every time it uses a capitalized word
except MUST or MUST NOT.  If options weren't needed, RFC2119 would be
a lot shorter.

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

From tony.li@tony.li  Thu Jan  3 14:33:33 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF3D421F8DC5 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:33:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.95
X-Spam-Level: 
X-Spam-Status: No, score=-99.95 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 FrVooEc6f5xJ for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:33:33 -0800 (PST)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id 142C021F8DC1 for <grow@ietf.org>; Thu,  3 Jan 2013 14:33:32 -0800 (PST)
Received: from omta20.emeryville.ca.mail.comcast.net ([76.96.30.87]) by qmta01.emeryville.ca.mail.comcast.net with comcast id jRSM1k00F1smiN4A1aZXV2; Thu, 03 Jan 2013 22:33:31 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta20.emeryville.ca.mail.comcast.net with comcast id jaXG1k00P52qHCY8gaXJv1; Thu, 03 Jan 2013 22:31:29 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com>
Date: Thu, 3 Jan 2013 14:31:16 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357252411; bh=0E63Q7sXqlt7YDI8a/y9kpgzq7NXCTvk3RtZ0Qu+RrA=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=HQhiL1bdD+EVjnwXv4J6aiHOVW4MMQVL7ypUE1GsC9S+WYXYYt+Mnkhd+MPmnXKDl GgbYUGJODuy8J4T831ufcnoeS9VcqEeKktGoDE1AX2/NMGtJkZWGLHEsSZXDdZdfsA gkmbvvC50iHqnW9USbh+cSzUzB/r7IuLG3oU4anGLUq54hJdotXPjiwCD0R99KC9yB pbZSpaqxZ9z7seo3xGKEo7aiKCFY327zEZIJRWrH39hXuHQP8cvnJEtKPLh2+LB6mM vttQLcO1VZQwvSaIcpyiVjxLNj5PitJNsj+FXEdPD/F1t5SlrBOpfq67lwte2eDDjM ZWX70kEjPVzKg==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:33:33 -0000

On Jan 3, 2013, at 2:15 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:

>>> However bad or difficult to clean up, what if that's not as bad as =
the
>>> alternative ?
>>=20
>> Clearly, the treat-as-withdraw alternative is better.  You're not =
leaving bogus state in the rest of the network.
>=20
> Does this mean you support treat-as-withdraw, even though you dislike
> its high complexity?  My read of your postings today is that you
> dislike the whole error-handling idea.


Jeff,

I support the general concept of improved error handling and softer =
failures when possible.

As I've said before, errors can be reasonably classified into two =
groups: syntactic and semantic. =20

A syntactic error would be any inconsistency of length fields, =
incompatibility between a type and a length, or any other error that =
would introduce any doubt about the parsing of the message.  Once this =
type of error has occurred, then the remainder of the data stream is =
wholly in doubt.  A session reset seems like the only (conservative) way =
of handling this, as it's unclear that further data would be accurate.

I'm very open to a discussion of alternatives to session flap for these =
cases.  Should we require manual intervention before session restart?  =
This would seem reasonable.

Semantic errors would be consistency violations within the contents of =
the message.  In these cases, treat-as-withdraw seems reasonable.

Tony


From tony.li@tony.li  Thu Jan  3 14:38:39 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8754621F8DD0 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:38:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.048
X-Spam-Level: 
X-Spam-Status: No, score=-100.048 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 Zxk9OwLJustS for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:38:39 -0800 (PST)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:228]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5FB21F8DA6 for <grow@ietf.org>; Thu,  3 Jan 2013 14:38:39 -0800 (PST)
Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta15.emeryville.ca.mail.comcast.net with comcast id jXrQ1k0061ZMdJ4AFaefQE; Thu, 03 Jan 2013 22:38:39 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta16.emeryville.ca.mail.comcast.net with comcast id jacS1k00J52qHCY8cacVF1; Thu, 03 Jan 2013 22:36:37 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtbL3eT9gPpkxERPrSNZH4a-as_fJi0+SBL0G7Ku=VeZNYg@mail.gmail.com>
Date: Thu, 3 Jan 2013 14:36:26 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <05E0568C-1A73-4F67-B484-5FB65427C563@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <E4E7344B-FF83-4CC2-AF46-A5B9640763D1@tony.li> <CAPWAtbL3eT9gPpkxERPrSNZH4a-as_fJi0+SBL0G7Ku=VeZNYg@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357252719; bh=rKDqjru0KuHWLFAjf/x13D38M5PoGvMwu3+/ukT14WA=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=VFthJ3zZUiBBrS8d8E8dm2aaePpcb3R6hU9sBJxzNYjXeZFxu1yL8dsrfUN5NSZQB znJfb9ltWLzJThJrScRJUvf/5F3QF6KfqZpPlfZVyu5cCQbLZ4H8jmhck3ey1ZQ2QS RjRqraCHd3FljB5mO8t1bgpcTecl7TdMH4mLexV/B3PjdKpe34IHj83GwWXV0DS3gu 2U/RvWSprjVqFbfq4NU3vArcHQBGPzG8BtfRjuSxsVP19WjNX3CC96uFRx3SWLAtGq p0qU7k8vfX+OZ4ouAEibeF20vgNAhoWaPDYKrgPYh+9SVjMNmdpUBsPogJ8UGUOR4X 498zqR0Ujar2w==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:38:39 -0000

On Jan 3, 2013, at 2:23 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:

> Fortunately vendors understand that they need to produce options to
> suit different kinds of customers. =20


Fortunately, this vendor has been around long enough to understand that =
adding options to suit every possible behavior results in complexity in =
the underlying code.  We, as a collective IETF group, learned long ago =
that adding 'nerd knobs' is generally a bad idea.

Tony


From Donald.Smith@CenturyLink.com  Thu Jan  3 14:55:00 2013
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CDD21F8DD3; Thu,  3 Jan 2013 14:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.073
X-Spam-Level: 
X-Spam-Status: No, score=-1.073 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 RYTW+qKFHOZX; Thu,  3 Jan 2013 14:54:59 -0800 (PST)
Received: from sudnp799.qwest.com (sudnp799.qwest.com [155.70.32.99]) by ietfa.amsl.com (Postfix) with ESMTP id 2B76A21F8DC5; Thu,  3 Jan 2013 14:54:59 -0800 (PST)
Received: from lxomavmpc030.qintra.com (lxomavmpc030.qintra.com [151.117.207.30]) by sudnp799.qwest.com (8.14.4/8.14.4) with ESMTP id r03MsvHI000063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Jan 2013 15:54:58 -0700 (MST)
Received: from lxomavmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id B78C91E0063; Thu,  3 Jan 2013 16:54:52 -0600 (CST)
Received: from suomp60i.qintra.com (unknown [10.6.10.61]) by lxomavmpc030.qintra.com (Postfix) with ESMTP id 9D1281E005D; Thu,  3 Jan 2013 16:54:52 -0600 (CST)
Received: from suomp60i.qintra.com (localhost [127.0.0.1]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id r03Mspk9029436; Thu, 3 Jan 2013 16:54:51 -0600 (CST)
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.qintra.com [151.119.128.29]) by suomp60i.qintra.com (8.14.4/8.14.4) with ESMTP id r03MspnX029426 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Jan 2013 16:54:51 -0600 (CST)
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([2002:9777:801d::9777:801d]) with mapi id 14.02.0318.001; Thu, 3 Jan 2013 15:54:50 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "'Tony Li'" <tony.li@tony.li>, "'Jeff Wheeler'" <jsw@inconcepts.biz>
Thread-Topic: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6gJgTRHM4SAHqUGXAu6gBw2r45g4M8pw
Date: Thu, 3 Jan 2013 22:54:50 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
In-Reply-To: <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.7]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'idr@ietf.org'" <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:55:00 -0000

"Pampers use multiple layers of protection to prevent leakage. Rommel used =
defense in depth to defend European fortresses." (A.White) Donald.Smith@Cen=
turyLink.com


>-----Original Message-----
>From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
>Tony Li
>Sent: Thursday, January 03, 2013 3:31 PM
>To: Jeff Wheeler
>Cc: idr@ietf.org; grow@ietf.org
>Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-
>error-handling-06.txt
>
>
>On Jan 3, 2013, at 2:15 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:
>
>>>> However bad or difficult to clean up, what if that's not as bad as
>the
>>>> alternative ?
>>>
>>> Clearly, the treat-as-withdraw alternative is better.  You're not
>leaving bogus state in the rest of the network.
>>
>> Does this mean you support treat-as-withdraw, even though you dislike
>> its high complexity?  My read of your postings today is that you
>> dislike the whole error-handling idea.
>
>
>Jeff,
>
>I support the general concept of improved error handling and softer
>failures when possible.
>
>As I've said before, errors can be reasonably classified into two
>groups: syntactic and semantic.
>
>A syntactic error would be any inconsistency of length fields,
>incompatibility between a type and a length, or any other error that
>would introduce any doubt about the parsing of the message.  Once this
>type of error has occurred, then the remainder of the data stream is
>wholly in doubt.  A session reset seems like the only (conservative) way
>of handling this, as it's unclear that further data would be accurate.
I disagree. Does a session reset fix the issue? It hasn't the last few time=
s I have seen this.
It exasperated it by causing peers to drop and having to rebuild ribs/fibs =
etc... continuously.

Other than getting it noticed I doubt a reset will ever make a misbehaving =
router stop misbehaving.

=20
>
>I'm very open to a discussion of alternatives to session flap for these
>cases.  Should we require manual intervention before session restart?
Manual intervention will be required in most cases but if we "require" manu=
al intervention haven't we left the programming side (state machine) and go=
ne into the operational control side of things?

>This would seem reasonable.
>
>Semantic errors would be consistency violations within the contents of
>the message.  In these cases, treat-as-withdraw seems reasonable.
I would also like the ignore option here. You know your neighbor is saying =
something you don't understand, possibly due to a lack of in your vocabular=
y but you understand other elements so you nod and continue listening to th=
e rest:)

This is what happened recently. ALU announced attributes with 1 bit set tha=
t others didn't understand. If the routers that didn't understand that bit =
could have ignored just that element everything would have been fine.


>
>Tony
>
>_______________________________________________
>GROW mailing list
>GROW@ietf.org
>https://www.ietf.org/mailman/listinfo/grow

From tony.li@tony.li  Thu Jan  3 15:17:01 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94D121F8770 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 15:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.08
X-Spam-Level: 
X-Spam-Status: No, score=-100.08 tagged_above=-999 required=5 tests=[AWL=0.130, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 yw9tReZugIF4 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 15:17:01 -0800 (PST)
Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:56]) by ietfa.amsl.com (Postfix) with ESMTP id 3522721F8860 for <grow@ietf.org>; Thu,  3 Jan 2013 15:17:01 -0800 (PST)
Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta06.emeryville.ca.mail.comcast.net with comcast id jbCL1k0021ZMdJ4A6bH1pw; Thu, 03 Jan 2013 23:17:01 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta16.emeryville.ca.mail.comcast.net with comcast id jbEm1k00C52qHCY8cbEoHA; Thu, 03 Jan 2013 23:14:59 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet>
Date: Thu, 3 Jan 2013 15:14:45 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B697CA52-4D41-4E27-AE65-E579CE7198A6@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet>
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357255021; bh=vEtEtkoAVLhVqlAB0CemEyHzBUnJ50fX6BmvTPUbnGs=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=PxJsfe6Sy9ZXFLzEL2ndpUQTDLaCoWWjqOv0GjSTaQfdq0XTaZFKWVWH66Nwpfihw KFnGokdgWmq8rWY40iVK8xy/VXS4oKH2hLqXniLkZpnlTYFV1xSN+iPfOgT/8djUYK snK11M1NeHpSWp5F9shp9STvi90bqOKNMuYSuydHzt6ojNXtCrVlBjsrudsEIQNe5N A+hQanEnm2Rz1xU0e5eZtLPup7ta+/xFnfEhMXjaHutAGQ6XzzQaB39NB2kavYH89v G4LlesLRsghFe4bWhKgB1oe5gikNg10s4SivyMQ/upc0P+OMbWKrPNp+yyPMSZTsA3 pV5KqDzyzU7FA==
Cc: "'idr@ietf.org'" <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 23:17:02 -0000

Hi Donald,

>> A session reset seems like the only (conservative) way
>> of handling this, as it's unclear that further data would be =
accurate.
> I disagree. Does a session reset fix the issue? It hasn't the last few =
times I have seen this.
> It exasperated it by causing peers to drop and having to rebuild =
ribs/fibs etc... continuously.


Which is why I suggested that re-opening the connection is perhaps not =
optimal.


> Other than getting it noticed I doubt a reset will ever make a =
misbehaving router stop misbehaving.


The point is that once you've lost context in the data stream, =
subsequent messages cannot be accepted with a reasonable certainty of =
correct parsing. =20


>> I'm very open to a discussion of alternatives to session flap for =
these
>> cases.  Should we require manual intervention before session restart?
> Manual intervention will be required in most cases but if we "require" =
manual intervention haven't we left the programming side (state machine) =
and gone into the operational control side of things?


Correct.  The programming side has failed.  As you note, trying again is =
not likely to help.  Adding Artificial Intelligence to BGP to recover is =
unlikely to be effective or an efficient means of making progress.


>> Semantic errors would be consistency violations within the contents =
of
>> the message.  In these cases, treat-as-withdraw seems reasonable.
> I would also like the ignore option here. You know your neighbor is =
saying something you don't understand, possibly due to a lack of in your =
vocabulary but you understand other elements so you nod and continue =
listening to the rest:)


The entire problem with the ignore option is that it leaves bogus =
information in the network.  Suppose that the update contains an AS path =
change for a prefix.  If you ignore the update, then you ignore that =
path change, AND, you fail to propagate that change to your upstream =
neighbors.  Now, BGP's loop prevention mechanism is out the window and, =
in the worst case, you've created an inter-domain forwarding loop.

If, on the other hand, you withdraw that prefix, then any alternate =
connectivity for that prefix can come into play.

In short, treat-as-withdraw is a fail safe approach.  Ignoring updates =
is not.

Tony


From brian.peter.dickson@gmail.com  Thu Jan  3 15:34:49 2013
Return-Path: <brian.peter.dickson@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55EF921F8D51; Thu,  3 Jan 2013 15:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.371
X-Spam-Level: 
X-Spam-Status: No, score=-3.371 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 LbGqflifkKg5; Thu,  3 Jan 2013 15:34:48 -0800 (PST)
Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9B16521F8D44; Thu,  3 Jan 2013 15:34:47 -0800 (PST)
Received: by mail-ee0-f51.google.com with SMTP id d4so7626642eek.10 for <multiple recipients>; Thu, 03 Jan 2013 15:34:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KEk3OZcEnMnCgqmTRUy9eSq7aWWFT+/VhfB/xRhOQg4=; b=E+BQcAIobEPCdbS75OSKwqKVFrnII82fzIs2fh+fESS5QxVVriT7jXJBYJcAuC9wvX YCJlgIj318+M91U32thPsUJXmXKhosngvDEp63Z3ZsOSGkxLZZ/3dodVmPGFBQGZjnn0 p0Fb1XSwhGj61wYI4aFldw3xrXyOzRAFPyVuQxK62mx+BKGcnbTHUCoupHRKVAF8M1Tw F2HR1kVtMgww5f/LeubP4JglSy5V+IcbR5NsUMWIRw2UJIHU6FBNnCGpyhDbPHqlX5cZ qPP5cb9IQhS+ixCxgspvDCQ7/MAF+U2fs2DI1rJqbq2p1A/uVsY7TXfa4g1zTXCTckXo wagg==
MIME-Version: 1.0
Received: by 10.14.173.69 with SMTP id u45mr138182079eel.21.1357256069425; Thu, 03 Jan 2013 15:34:29 -0800 (PST)
Received: by 10.223.173.199 with HTTP; Thu, 3 Jan 2013 15:34:29 -0800 (PST)
In-Reply-To: <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet>
Date: Thu, 3 Jan 2013 18:34:29 -0500
Message-ID: <CAH1iCiqkqmN45KYiZyRpSvwVkOuPOLbGhe9QaNEbxFmBUUjkRQ@mail.gmail.com>
From: Brian Dickson <brian.peter.dickson@gmail.com>
To: "Smith, Donald" <Donald.Smith@centurylink.com>
Content-Type: multipart/alternative; boundary=047d7b6039f4e32ae604d26acdf9
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 23:34:49 -0000

--047d7b6039f4e32ae604d26acdf9
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 3, 2013 at 5:54 PM, Smith, Donald
<Donald.Smith@centurylink.com>wrote:
>
> >-----Original Message-----
> >From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf Of
> >Tony Li
> >Sent: Thursday, January 03, 2013 3:31 PM
> >To: Jeff Wheeler
> >Cc: idr@ietf.org; grow@ietf.org
> >Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-
> >error-handling-06.txt
> >
>
> >I support the general concept of improved error handling and softer
> >failures when possible.
> >
> It exasperated it by causing peers to drop and having to rebuild ribs/fibs
> etc... continuously.
>
> Other than getting it noticed I doubt a reset will ever make a misbehaving
> router stop misbehaving.


The "continuously" points to the problem. If a session drops because of
syntactic issues, it should stay down.
Does that make sense? It is analogous to "treat-as-withdraw", just using a
much larger hammer. :-)


> >Semantic errors would be consistency violations within the contents of
> >the message.  In these cases, treat-as-withdraw seems reasonable.
> I would also like the ignore option here. You know your neighbor is saying
> something you don't understand, possibly due to a lack of in your
> vocabulary but you understand other elements so you nod and continue
> listening to the rest:)
>
> This is what happened recently. ALU announced attributes with 1 bit set
> that others didn't understand. If the routers that didn't understand that
> bit could have ignored just that element everything would have been fine.


Here's a couple of problems with what you're suggesting here.

You don't know whether that 1 bit changes the logic that should be used
(e.g. "This is a back-up route only", or "Black-hole this prefix, please".)
Presuming that you should use the announcement is dangerous.

And then what should you do with the announcement - forward to appropriate
peers, or not?
If you forward it, should you keep the bit set, or not?

IMHO, the safe thing to do with "unknown bit set", is treat-as-withdraw.

Maybe, MAYBE, have a knob to "listen to but ignore unknown bit".

DEFINITELY, do NOT announce bits you don't understand. (liberal accept,
conservative send).

And PROBABLY do NOT announce things if you twiddled unknown bit(s).
You are potentially messing with unknown semantics, to the probable
detriment of your peers.
(Here there be dragons.)

The safest thing is to not announce. The conservative approach is to "treat
as withdraw".
And put a suitable error message wherever error messages normally go.

Again, IMHO.

Brian

--047d7b6039f4e32ae604d26acdf9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Thu, Jan 3, 2013 at 5:54 PM, Smith, D=
onald <span dir=3D"ltr">&lt;<a href=3D"mailto:Donald.Smith@centurylink.com"=
 target=3D"_blank">Donald.Smith@centurylink.com</a>&gt;</span> wrote:<block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<div class=3D"im">
&gt;-----Original Message-----<br>
</div><div class=3D"im">&gt;From: <a href=3D"mailto:grow-bounces@ietf.org">=
grow-bounces@ietf.org</a> [mailto:<a href=3D"mailto:grow-bounces@ietf.org">=
grow-bounces@ietf.org</a>] On Behalf Of<br>
</div><div class=3D"im">&gt;Tony Li<br>
&gt;Sent: Thursday, January 03, 2013 3:31 PM<br>
&gt;To: Jeff Wheeler<br>
&gt;Cc: <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mailto=
:grow@ietf.org">grow@ietf.org</a><br>
</div><div><div class=3D"h5">&gt;Subject: Re: [GROW] [Idr] I-D Action: draf=
t-ietf-grow-ops-reqs-for-bgp-<br>
&gt;error-handling-06.txt<br>
&gt;<br><br>
&gt;I support the general concept of improved error handling and softer<br>
&gt;failures when possible.<br>
&gt;<br></div></div>
It exasperated it by causing peers to drop and having to rebuild ribs/fibs =
etc... continuously.<br>
<br>
Other than getting it noticed I doubt a reset will ever make a misbehaving =
router stop misbehaving.</blockquote><div><br></div><div>The &quot;continuo=
usly&quot; points to the problem. If a session drops because of syntactic i=
ssues, it should stay down.</div>
<div>Does that make sense? It is analogous to &quot;treat-as-withdraw&quot;=
, just using a much larger hammer. :-)</div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div class=3D"im">
&gt;Semantic errors would be consistency violations within the contents of<=
br>
&gt;the message. =A0In these cases, treat-as-withdraw seems reasonable.<br>
</div>I would also like the ignore option here. You know your neighbor is s=
aying something you don&#39;t understand, possibly due to a lack of in your=
 vocabulary but you understand other elements so you nod and continue liste=
ning to the rest:)<br>

<br>
This is what happened recently. ALU announced attributes with 1 bit set tha=
t others didn&#39;t understand. If the routers that didn&#39;t understand t=
hat bit could have ignored just that element everything would have been fin=
e.</blockquote>
<div><br></div><div>Here&#39;s a couple of problems with what you&#39;re su=
ggesting here.</div><div><br></div><div>You don&#39;t know whether that 1 b=
it changes the logic that should be used (e.g. &quot;This is a back-up rout=
e only&quot;, or &quot;Black-hole this prefix, please&quot;.)</div>
<div>Presuming that you should use the announcement is dangerous.</div><div=
><br></div><div>And then what should you do with the announcement - forward=
 to appropriate peers, or not?</div><div>If you forward it, should you keep=
 the bit set, or not?</div>
<div><br></div><div>IMHO, the safe thing to do with &quot;unknown bit set&q=
uot;, is treat-as-withdraw.</div><div><br></div><div>Maybe, MAYBE, have a k=
nob to &quot;listen to but ignore unknown bit&quot;.</div><div><br></div>
<div>DEFINITELY, do NOT announce bits you don&#39;t understand. (liberal ac=
cept, conservative send).</div><div><br></div><div>And PROBABLY do NOT anno=
unce things if you twiddled unknown bit(s).</div><div>You are potentially m=
essing with unknown semantics, to the probable detriment of your peers.</di=
v>
<div>(Here there be dragons.)</div><div><br></div><div>The safest thing is =
to not announce. The conservative approach is to &quot;treat as withdraw&qu=
ot;.</div><div>And put a suitable error message wherever error messages nor=
mally go.</div>
<div><br></div><div>Again, IMHO.</div><div><br></div><div>Brian</div></div>

--047d7b6039f4e32ae604d26acdf9--

From jared@puck.nether.net  Thu Jan  3 15:42:16 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8579921F8CA1; Thu,  3 Jan 2013 15:42:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.047
X-Spam-Level: 
X-Spam-Status: No, score=-2.047 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 3f2uNVT49OfZ; Thu,  3 Jan 2013 15:42:15 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 9B8C421F8830; Thu,  3 Jan 2013 15:42:15 -0800 (PST)
Received: from [10.0.0.129] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r03Ng6mk026413 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 3 Jan 2013 18:42:07 -0500
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAH1iCiqkqmN45KYiZyRpSvwVkOuPOLbGhe9QaNEbxFmBUUjkRQ@mail.gmail.com>
Date: Thu, 3 Jan 2013 18:42:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AA25EC1F-C47D-4F90-8E99-EA479ED7A1A9@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet> <CAH1iCiqkqmN45KYiZyRpSvwVkOuPOLbGhe9QaNEbxFmBUUjkRQ@mail.gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Thu, 03 Jan 2013 18:42:07 -0500 (EST)
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 23:42:16 -0000

On Jan 3, 2013, at 6:34 PM, Brian Dickson =
<brian.peter.dickson@gmail.com> wrote:

>=20
>=20
> On Thu, Jan 3, 2013 at 5:54 PM, Smith, Donald =
<Donald.Smith@centurylink.com> wrote:
> >-----Original Message-----
> >From: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] On Behalf =
Of
> >Tony Li
> >Sent: Thursday, January 03, 2013 3:31 PM
> >To: Jeff Wheeler
> >Cc: idr@ietf.org; grow@ietf.org
> >Subject: Re: [GROW] [Idr] I-D Action: =
draft-ietf-grow-ops-reqs-for-bgp-
> >error-handling-06.txt
> >
>=20
> >I support the general concept of improved error handling and softer
> >failures when possible.
> >
> It exasperated it by causing peers to drop and having to rebuild =
ribs/fibs etc... continuously.
>=20
> Other than getting it noticed I doubt a reset will ever make a =
misbehaving router stop misbehaving.
>=20
> The "continuously" points to the problem. If a session drops because =
of syntactic issues, it should stay down.
> Does that make sense? It is analogous to "treat-as-withdraw", just =
using a much larger hammer. :-)
>=20

I think that Mike Long had it right earlier today in saying that the =
vendor implementation should shut the session just like max-prefix. =
(perhaps with a default restart-timer measured in tens of minutes)?  =
This doesn't seem to need a protocol change though.  I am also a bit =
wary of as Tony put it .. "nerd knobs".  I've seen how some of these =
legacy knobs break in some new/future release as they migrate through =
our templates/platforms over the years.  Nobody even knows what it does =
anymore, and the original purpose is gone but the parser still takes it =
...

- Jared=

From m.hallgren@free.fr  Thu Jan  3 15:51:38 2013
Return-Path: <m.hallgren@free.fr>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6400921F8235 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 15:51:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
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 5VJjw7lrK5Hw for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 15:51:37 -0800 (PST)
Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) by ietfa.amsl.com (Postfix) with ESMTP id 9452121F8E03 for <grow@ietf.org>; Thu,  3 Jan 2013 15:51:29 -0800 (PST)
Received: from [IPv6:2a01:e35:2e49:1280:e4a7:9c7d:cfe8:d467] (unknown [IPv6:2a01:e35:2e49:1280:e4a7:9c7d:cfe8:d467]) by smtp1-g21.free.fr (Postfix) with ESMTP id 5995E9400D3 for <grow@ietf.org>; Fri,  4 Jan 2013 00:51:22 +0100 (CET)
Message-ID: <50E61979.20009@free.fr>
Date: Fri, 04 Jan 2013 00:51:21 +0100
From: Michael Hallgren <m.hallgren@free.fr>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: grow@ietf.org
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <806CF05A-6EBE-47FF-A6AA-F262A288DB3D@puck.nether.net> <CAPWAtbKUne9PNmnyLzbEeJQ8VBFv0geab+v3S7T8DCsDTdUWtw@mail.gmail.com> <50E5DDA3.5060709@cisco.com>
In-Reply-To: <50E5DDA3.5060709@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: multipart/alternative; boundary="------------050905080304070903010309"
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 23:51:38 -0000

This is a multi-part message in MIME format.
--------------050905080304070903010309
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Le 03/01/2013 20:36, Enke Chen a écrit :
> hi, Jeff:
>
> On 1/3/13 11:22 AM, Jeff Wheeler wrote:
>
> [snip]
>
>>
>>> Respectfully, I think you're misunderstanding my position completely.  My point is that a reasonable implementation cannot possibly live up to the expectations that you're setting up here.  To be specific, once an implementation loses the syntactic parsing of the data stream, realistically, the session is corrupt and an eventual reset is inevitable.  Or, in other words, BGP cannot possible ignore bad messages.  That's not the way it works.
>> Of course BGP can ignore bad messages.  To say otherwise is simply
>> telling a lie because you haven't made a good argument.
>>
>>
>
> A good argument (IMO) has been made in the error handling draft:
>
> ---------
> http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/
>
> 4. Operational Considerations
>    Note that "treat-as-withdraw" is different from discarding an UPDATE
>    message.  The latter violates the basic BGP principle of incremental
>    update, and could cause invalid routes to be kept.  (See also
>    Appendix A.)
> ---------


+1

mh

>
> -- Enke
>
>
>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow


--------------050905080304070903010309
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Le 03/01/2013 20:36, Enke Chen a
      &eacute;crit&nbsp;:<br>
    </div>
    <blockquote cite="mid:50E5DDA3.5060709@cisco.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">hi, Jeff:<br>
        <br>
        On 1/3/13 11:22 AM, Jeff Wheeler wrote:<br>
        <br>
        [snip]<br>
        <br>
      </div>
      <blockquote
cite="mid:CAPWAtbKUne9PNmnyLzbEeJQ8VBFv0geab+v3S7T8DCsDTdUWtw@mail.gmail.com"
        type="cite"><br>
        <blockquote type="cite">
          <pre wrap="">Respectfully, I think you're misunderstanding my position completely.  My point is that a reasonable implementation cannot possibly live up to the expectations that you're setting up here.  To be specific, once an implementation loses the syntactic parsing of the data stream, realistically, the session is corrupt and an eventual reset is inevitable.  Or, in other words, BGP cannot possible ignore bad messages.  That's not the way it works.
</pre>
        </blockquote>
        <pre wrap="">Of course BGP can ignore bad messages.  To say otherwise is simply
telling a lie because you haven't made a good argument.


</pre>
      </blockquote>
      <br>
      A good argument (IMO) has been made in the error handling draft:<br>
      <br>
      ---------<br>
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
        href="http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/">http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/</a><br>
      <br>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <pre><span class="m_h">4. Operational Considerations</span></pre>
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      <pre>   Note that "treat-as-withdraw" is different from discarding an UPDATE
   message.  The latter violates the basic BGP principle of incremental
   update, and could cause invalid routes to be kept.  (See also
   Appendix A.)</pre>
      ---------<br>
    </blockquote>
    <br>
    <br>
    +1<br>
    <br>
    mh<br>
    <br>
    <blockquote cite="mid:50E5DDA3.5060709@cisco.com" type="cite"> <br>
      -- Enke<br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
GROW mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GROW@ietf.org">GROW@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/grow">https://www.ietf.org/mailman/listinfo/grow</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050905080304070903010309--

From jsw@inconcepts.biz  Thu Jan  3 16:26:42 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30F4E21F849A for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 16:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.683
X-Spam-Level: 
X-Spam-Status: No, score=-2.683 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 YdltMFkDPjYx for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 16:26:41 -0800 (PST)
Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) by ietfa.amsl.com (Postfix) with ESMTP id E82B221F8464 for <grow@ietf.org>; Thu,  3 Jan 2013 16:26:40 -0800 (PST)
Received: by mail-ie0-f180.google.com with SMTP id c10so18741525ieb.39 for <grow@ietf.org>; Thu, 03 Jan 2013 16:26:40 -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 :content-transfer-encoding:x-gm-message-state; bh=TjaqyWNdofijDgTJwDCFBZ+mugYQd48wzXcNvh2e3C0=; b=bGhT1LM44AEQsqLSbkzIoN2XWsXw9CcsEcA9M38tgcQuiN3Tm/rVQ9N1+I+txn4UV/ eNNwbxn9R9DL+SGSoCiJOAcnh6kzd3AyKeAWxwz78LEKTqgabFUc6JmA1VRZoit2/SOe xDmYzITBThFCxLXjtzynooGZwdL+7saoAE6o5PlbcYtj3N/SOqImUQ/WummN9hnX7j1u orf61KQ4VJEAhnNuyqDJr+bODnWSwYycbS3g2uxo40UE2cins9vauUbX9PMhbwDmOLNm KPIrDhT5r5zzVLUG6syBS1+kgv+cYbU4cr4xs+EoJ8FFsHySLuvMBnzjacAWik1ZUzqK TV5g==
MIME-Version: 1.0
Received: by 10.50.104.232 with SMTP id gh8mr43175350igb.45.1357259200448; Thu, 03 Jan 2013 16:26:40 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 16:26:40 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
Date: Thu, 3 Jan 2013 19:26:40 -0500
Message-ID: <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkUwVPWbCK/4FJ2wnjznWujSA/A0xZuhTsv+ryK9PpwfXiDtzP6hR3BaRCptfvc3e1r2Hvn
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 00:26:42 -0000

On Thu, Jan 3, 2013 at 5:31 PM, Tony Li <tony.li@tony.li> wrote:
> A syntactic error would be any inconsistency of length fields, incompatib=
ility between a type and a length, or any other error that would introduce =
any doubt about the parsing of the message.  Once this type of error has oc=
curred, then the remainder of the data stream is wholly in doubt.  A sessio=
n reset seems like the only (conservative) way of handling this, as it's un=
clear that further data would be accurate.
>
> I'm very open to a discussion of alternatives to session flap for these c=
ases.  Should we require manual intervention before session restart?  This =
would seem reasonable.

I've already posted an alternative.  The BGP MARKER makes it possible
to recover Message framing.  I'm not sure I think this is a good idea.
 I am sure I would wish for it at 2am on a Saturday morning, if it
fixed my problem.  So if my vendor supplied it as an option, I might
be glad for that someday.

> Semantic errors would be consistency violations within the contents of th=
e message.  In these cases, treat-as-withdraw seems reasonable.

The current draft for "treat-as-withdraw" has a great deal of
complexity.  You seem to both favor this solution, and hate the
complexity.  I also hate the complexity, and "ignore-bad-message" is
my alternative.

Would you rather the draft simply eliminate a lot of the complexity?
I would, because the complexity is what creates more opportunities for
session-reset.  It also may catalyze bugs.

None of these are "nerd knobs" when they fix your operational problem
and allow you to stop bleeding money.  TCP Path MTU Detection for BGP
is a "nerd knob."  Yet, there it is, along with plenty of other things
that might tweak your router a bit; but they're not there to save your
butt in a crisis.  That's what error-handling should do -- save your
butt.

On Thu, Jan 3, 2013 at 5:54 PM, Smith, Donald
<Donald.Smith@centurylink.com> wrote:
> Other than getting it noticed I doubt a reset will ever make a misbehavin=
g router stop misbehaving.

Maybe not, but I've certainly seen it solve problems.  For example,
Cisco 6500/7600s used to send > MTU sized Ethernet frames to eBGP
neighbors if TCP MD5 for BGP was in use.  I had a eBGP session to a
transit network which would fail every few days because the Cisco box
would repeatedly try to send an illegally-large frame, my router would
discard the frames, and the Cisco would keep trying to retransmit it.
Eventually my HoldTime would expire.  As you might imagine, this took
quite some time for us to diagnose; but at least the auto-reset caused
the network to return to a good state pretty quickly.

> This is what happened recently. ALU announced attributes with 1 bit set t=
hat others didn't understand. If the routers that didn't understand that bi=
t could have ignored just that element everything would have been fine.

Actually the problematic routers that reset their sessions "MUST have
ignored [this bit] when received," according to RFC4271, but they
didn't do that.  So the reason why those routers broke is that THEY
were buggy AND the originating router was buggy.  It is also arguable
that routers in the DFZ should not have propagated this 1 bit.  Some
routers didn't while others did.

So if the receiving routers weren't buggy in the first place, they
would not have experienced any problem.  However, ignore-bad-message
or treat-as-withdraw would be a good catch-all that an operator could
use, even if his router was buggy, to keep his network functioning.

On Thu, Jan 3, 2013 at 6:14 PM, Tony Li <tony.li@tony.li> wrote:
> The entire problem with the ignore option is that it leaves bogus informa=
tion in the network.  Suppose that the update contains an AS path change fo=
r a prefix.  If you ignore the update, then you ignore that path change, AN=
D, you fail to propagate that change to your upstream neighbors.  Now, BGP'=
s loop prevention mechanism is out the window and, in the worst case, you'v=
e created an inter-domain forwarding loop.
>
> If, on the other hand, you withdraw that prefix, then any alternate conne=
ctivity for that prefix can come into play.
>
> In short, treat-as-withdraw is a fail safe approach.  Ignoring updates is=
 not.

Treat-as-withdraw is NOT fail-safe.  It can create loops or blackholes
in your network.  Claiming over and over that it is safe will not make
it true.

Ignore-bad-message has bad qualities, which are just as bad as
treat-as-withdraw, except it is less complicated to implement and
there is a greater chance it can avoid a potentially crippling
session-reset loop.

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

From tony.li@tony.li  Thu Jan  3 17:04:04 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1BAA21F8E11 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 17:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.102
X-Spam-Level: 
X-Spam-Status: No, score=-100.102 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 tNrAaoAvp3Du for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 17:04:04 -0800 (PST)
Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:32]) by ietfa.amsl.com (Postfix) with ESMTP id 4062821F8E17 for <grow@ietf.org>; Thu,  3 Jan 2013 17:04:04 -0800 (PST)
Received: from omta23.emeryville.ca.mail.comcast.net ([76.96.30.90]) by qmta03.emeryville.ca.mail.comcast.net with comcast id jSmf1k0041wfjNsA3d44cy; Fri, 04 Jan 2013 01:04:04 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta23.emeryville.ca.mail.comcast.net with comcast id jd1q1k01352qHCY8jd1tlV; Fri, 04 Jan 2013 01:02:02 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com>
Date: Thu, 3 Jan 2013 17:01:50 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357261444; bh=ycB8dX8P6kAOT5ESsxaX6j/7upJa3DOyoK10RrDk9xQ=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=s+e9+PARHf1klE25LZHx2MgIrqc+NBxtH6BmMGJH3uNuYt58LQL5JbWMbICmuaI3x FOO/8CO/vUDF48rnf3mZmRKc303iMfOO0WYRmHl+0gWbP+KqDwFrq+sTv6m2UX9CJp AEEjjnqoio4Excae5qdDgKUhrsEvtgqnO66x5LuCnkdsVYmlCSXabswQkhpLs9/OPh CkZatCbEsguKBTaW7mPGRASrCU7amZoSpPnlTqPkn3lF/raUiNujyUNpCpiHvPCTw0 Yzy9l+qZ9Qm4ob9KVSRq5hFDM35OHxX4TYPxOcgRIOnRAKwCDuLX75/tEMDV7fzavp dXZHXF2szjnww==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 01:04:04 -0000

Hi Jeff,


> I've already posted an alternative.  The BGP MARKER makes it possible
> to recover Message framing.  I'm not sure I think this is a good idea.


I'm pretty convinced that it's NOT a good idea.   What happens if the =
marker is preceded by 0xFF?   Ok, you can make some educated guesses =
based on what looks to be a length field (probably NOT starting with =
0xFF), but you are just guessing.   =20

And what if the error was egregious and your parsing is off by more than =
a byte or two?  That marker might be a path attribute.  Now what?

Ok, yes, you could take a risk and see if you can keep parsing, but then =
what happens if you hit another error?  Just keep guessing along?  Your =
odds of guessing correctly are falling.  Or do you try to be really, =
really smart?

While you may be willing to gamble with your domain, please remember =
that you are also gambling with every network that accepts updates from =
you, transitively.  For lots of folks, that's the bulk of the Internet.  =
Is this a good gamble?  I'm not convinced.


>> Semantic errors would be consistency violations within the contents =
of the message.  In these cases, treat-as-withdraw seems reasonable.
>=20
> The current draft for "treat-as-withdraw" has a great deal of
> complexity.  You seem to both favor this solution, and hate the
> complexity.  I also hate the complexity, and "ignore-bad-message" is
> my alternative.


To be specific, treat-as-withdraw seems to be less dangerous.  As =
implemented (and perhaps NOT as envisioned), treat-as-withdraw can be =
done with an acceptable amount of complexity, IMHO.  It needs to be done =
VERY simply.


> Would you rather the draft simply eliminate a lot of the complexity?
> I would, because the complexity is what creates more opportunities for
> session-reset.  It also may catalyze bugs.


I would welcome that, but we should recognize that we're making a =
tradeoff.  4271 opts for maximum simplicity: if there's an error, shut =
it down.  Anything more than that will be added complexity.  What we're =
trying to do is to add some small amounts of complexity for a hopefully =
significant amount of robustness.  If done right, that would be a =
reasonable tradeoff.  If done wrong, this could be a major disaster.


>> The entire problem with the ignore option is that it leaves bogus =
information in the network.  Suppose that the update contains an AS path =
change for a prefix.  If you ignore the update, then you ignore that =
path change, AND, you fail to propagate that change to your upstream =
neighbors.  Now, BGP's loop prevention mechanism is out the window and, =
in the worst case, you've created an inter-domain forwarding loop.
>>=20
>> If, on the other hand, you withdraw that prefix, then any alternate =
connectivity for that prefix can come into play.
>>=20
>> In short, treat-as-withdraw is a fail safe approach.  Ignoring =
updates is not.
>=20
> Treat-as-withdraw is NOT fail-safe.  It can create loops or blackholes
> in your network.  Claiming over and over that it is safe will not make
> it true.


Example please?  Assuming that the prefixes are parsed out of the =
message correctly, then treating them as withdrawn should be hazard =
free.


> Ignore-bad-message has bad qualities, which are just as bad as
> treat-as-withdraw, except it is less complicated to implement and
> there is a greater chance it can avoid a potentially crippling
> session-reset loop.


Non-sequitur.  Cyclic resets are orthogonal to treat-as-withdraw.  As =
enumerated above, ignore-bad-message is harder to implement and is more =
dangerous.
 =20
Tony


From jsw@inconcepts.biz  Thu Jan  3 18:33:50 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29FB721F8E50 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 18:33:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 0E6Rjz+dxo8k for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 18:33:49 -0800 (PST)
Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) by ietfa.amsl.com (Postfix) with ESMTP id 73FF721F8E51 for <grow@ietf.org>; Thu,  3 Jan 2013 18:33:49 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id k13so18581741iea.8 for <grow@ietf.org>; Thu, 03 Jan 2013 18:33:49 -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=kyffh7qcBoFlHR2kP0VkO8PghPZC8cvUxl752tq87dc=; b=hEp1ipE8m/r2TyARrOTZv1tkiYgioRmkaMTtKG/IpDH2KjkH+AKEzufIr+naFdzBL9 LvlXfLc+DEHrbM4NTx2bkCDPhk3MQN037oR/C6YW5kIZFdlYhUo0ZeqB1hqUilzSI5GE ygNX/MS9c77t9rX8HNDj/2XONbDhMH1gQKzjZp4TWE7Lo0lVI3qyIX5koajU6kBfh1fy Ua2KeOdHkQ7ExlS6V4jLE3Bn1rq+YNjKD5KYijrCvCISjIJq+Hdi+DWiqDAkS4drVHKy h6h49Cb23CPXoR2/JvUWyqFJ73Ow/xj4LfnvvwAWpScqxSIz21o5r8DJbvw2AEhQjOXP p6nw==
MIME-Version: 1.0
Received: by 10.50.104.232 with SMTP id gh8mr43361657igb.45.1357266828863; Thu, 03 Jan 2013 18:33:48 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 18:33:48 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li>
Date: Thu, 3 Jan 2013 21:33:48 -0500
Message-ID: <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQljRsG+ujpM1RNsjPSQzRKHSdi5Rn1IYsFqr17bzXIuVAFjUky7VHgtWf1wp9xlJPdeFrer
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 02:33:50 -0000

On Thu, Jan 3, 2013 at 8:01 PM, Tony Li <tony.li@tony.li> wrote:
> Example please?  Assuming that the prefixes are parsed out of the message correctly, then treating them as withdrawn should be hazard free.

If a transit router in your AS treats-as-withdraw a prefix, other
routers may try to send traffic across it, but the router which has
treated-as-withdraw will either have no information for that route, or
it will have made a different bestpath choice.  This could cause a
loop or a blackhole.

> Non-sequitur.  Cyclic resets are orthogonal to treat-as-withdraw.  As enumerated above, ignore-bad-message is harder to implement and is more dangerous.

No, ignore-bad-message is not harder to implement.  To say so is simply a lie.

To treat-as-withdraw you have to follow some rules, parse a damaged
message to look for NLRI, and then withdraw them.

Treat-as-withdraw is unquestionably harder than simply ignoring the
whole contents of a message.

Your argument is some hand-waving about how hard it is to ignore a
message, and your incorrect belief that treat-as-withdraw can't leave
the RIB in state that can cause forwarding problems.

I'm not picking at your position just for the sake of argument.  I
agree with you that error-handling (current draft) is too complicated.
 I'm suggesting alternatives, as well as modifications that should be
made to either RFC4760bis or to error-handling to make it actually
work.

Just to move beyond ignore-bad-message vs. treat-as-withdraw arguments
for now, I believe some basic questions need to be answered for
treat-as-withdraw to be a useful option.

1) should a BGP speaker be able to promise that MP attributes will be
sent first?
   if so, a capability code is needed
   this could be done by error-handling or RFC4760bis

2) should non-MP NLRIs in the message be moved in the way
error-handling suggests?
   if so, a capability is absolutely required
   the basic encoding of BGP Messages changes if this is to be done

3) there are numerous attribute-specific rules in error-handling now.
They are not crazy but they are complicated.  Is this complexity
enough to deter vendors from implementing error-handling at all?  Are
they likely to catalyze bugs?  Do the attribute-specific rules do more
harm than good?

If you are in favor of treat-as-withdraw then the above are important
questions to answer.

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

From jsw@inconcepts.biz  Thu Jan  3 11:22:51 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51B1F21F8CFC for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 11:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.75
X-Spam-Level: 
X-Spam-Status: No, score=-2.75 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 YWt2Vqodd2A9 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 11:22:50 -0800 (PST)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) by ietfa.amsl.com (Postfix) with ESMTP id 932A921F8CC8 for <grow@ietf.org>; Thu,  3 Jan 2013 11:22:48 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id 17so18711357iea.2 for <grow@ietf.org>; Thu, 03 Jan 2013 11:22:48 -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 :content-transfer-encoding:x-gm-message-state; bh=QQNWR3dviH/iq9/nJFuf3gjIcsTnacBHyt08pPi429g=; b=LpegqRNQfjcu80WaG4hJjnXpEGipyNWHpUaWhjF3hJJ2d+wwjv85Bud/MNiLnjN2Pr 8BgonOmKkuK14dbh0sQsmD4vns2lRjAgcU8/gAwrQ1hiuk5oStYw1BNbDViJnX+w0wmL MeTkOlDxhwiWPbPcUm5QmNuFsY0MNo58VCLuMH4YO/2NCA4g8cbao5Tep9YoRdLmyDOn 3ryzl2IwjdIyza8FJ7uTwU9Fc/EPNH7CCYpyDLVla6T5UdotwL1SUI0oXTz0DNAQQyLP cNidwJUqljq2iK7jf76L/2GmtYFB0Bpq1mPsP7R9s2hF2eczXBmCd76wYJAC/P4K4cQv 3sWg==
MIME-Version: 1.0
Received: by 10.50.152.240 with SMTP id vb16mr42253550igb.45.1357240967982; Thu, 03 Jan 2013 11:22:47 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 11:22:47 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <806CF05A-6EBE-47FF-A6AA-F262A288DB3D@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <806CF05A-6EBE-47FF-A6AA-F262A288DB3D@puck.nether.net>
Date: Thu, 3 Jan 2013 14:22:47 -0500
Message-ID: <CAPWAtbKUne9PNmnyLzbEeJQ8VBFv0geab+v3S7T8DCsDTdUWtw@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Jared Mauch <jared@puck.nether.net>, Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmpSwPF9ol+Gm2uXcLA5dcERyW1PPEmyY93mI0DKVuHISxblnu098m55a9HAjIMn3zbmrPr
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:19 -0800
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 19:22:52 -0000

On Thu, Jan 3, 2013 at 12:40 PM, Jared Mauch <jared@puck.nether.net> wrote:
> Not sure who you're asking, but I think this whole draft is an idealist a=
ttempt to workaround software defects that may be uncorrectable as a whole.=
  (I say this as a $large_operator as measured here: http://as-rank.caida.o=
rg/?mode0=3Das-ranking&n=3D10&ranksort=3D1 )
>
> The missing prefix because it was ignored, or routing loop because a with=
draw was ignored will quickly change these folks minds.

Yes, the existing draft contains a great deal of complexity to work
around specific problems that have been imagined.

It would be very simple to just ignore bad updates.  That is not
complicated.  It's not "good" but it's less bad than your network
being down because you received one bad update from your DFZ neighbor,
which in the case of a small network, might be one or all of their
transit providers.

Having had to support networks who were down because of this condition
recently, I understand their pain, because they were down with no hope
of being back up until external parties helped them.

> Methinks you underestimate the complexity that would be added to the erro=
r handling code.  While finding a marker/0xff may be easier, understanding =
the large block of updates in the flood of activity and low latency of larg=
e tcp windows make this much harder and more prone to error.

I don't think I underestimate it at all.  I think the complexity
introduced by the error-handling draft is a bad idea.  I know that
"ignore bad updates" is extremely simple and a very broad catch-all
tool which can be utilized if there are no better options.  Having
your network be down because you can't keep BGP sessions to your
transit providers established is not an option.

> For some operators, the only chance to workaround defects is to have some=
thing catastrophic happen to provide the justification to management to act=
ually pick up the $new_software that corrects the problems you've been appl=
ying band-aids to.

Your position is that you don't want a feature that can mitigate
problems, because it would provide you with an opportunity to mitigate
problems instead of fix them?  Do you have to sabotage your network to
get problems fixed or capacity upgraded, too?

> I'm generally in the more-rope camp, but this is effectively throwing out=
 years of well worn code path and introducing new code (and likely defects)=
 in the handling of error cases which can only make things worse.  There wa=
sn't a broad-reaching bgp attribute problem in 2012 that i'm aware of, putt=
ing us in the "there is stability in the core" camp.  I'm seeing a well int=
entioned but unneeded element of meddling here.

LANL's announcement of invalid paths caused about 3000 prefixes to
instantly disappear from the DFZ.  This lasted for several hours.
Those missing prefixes are just networks who didn't have any working
transit at all.  Some small networks that I worked with were affected
on only some transit sessions and not others.  The affect of this is
difficult to measure, but almost 1% of the DFZ disappearing because of
one bad update demonstrates just why BGP is a very vulnerable single
point-of-failure.

> People on the edge also need to learn to maintain their devices.  This is=
n't a standards body issue, and IMHO off-topic for here, but an important d=
atapoint.

While true, if their vendor hasn't identified and corrected a bug yet,
they don't have any software upgrade option.  I believe this was
recently the case for Alcatel during same event caused by the LANL
announcements.

On Thu, Jan 3, 2013 at 1:00 PM, Tony Li <tony.li@tony.li> wrote:
> I'm sure if you asked folks if they wanted anything that helped them and =
completely ignored the costs, they would say yes.  However, if you want to =
make a reasonable, rational, and justified decision, you must consider the =
implications of the request.  That's what I'm asking.  Consider implementor=
 input as well, because there are some practical considerations here.

Do you think the error-handling draft is too complex to be worth
implementing?  I do.  That is exactly why I suggest "ignore bad
messages" as an alternative.  It is not complicated.

> Respectfully, I think you're misunderstanding my position completely.  My=
 point is that a reasonable implementation cannot possibly live up to the e=
xpectations that you're setting up here.  To be specific, once an implement=
ation loses the syntactic parsing of the data stream, realistically, the se=
ssion is corrupt and an eventual reset is inevitable.  Or, in other words, =
BGP cannot possible ignore bad messages.  That's not the way it works.

Of course BGP can ignore bad messages.  To say otherwise is simply
telling a lie because you haven't made a good argument.

There are three types of situations worth considering.

1) message is bad and we don't know if Message Length is, because
another MARKER hasn't yet arrived
This is very easy to deal with.  Simply ignore the message.  If a
MARKER doesn't arrive next, reset the session.  Avoids complexity.
Your code should already be able to deal with a message that contains
nothing it understands -- for example, a message with no NLRI and
nothing but an optional, non-transitive attribute that it doesn't
recognize.

1) message is bad but Message Length is fine, and the next MARKER
appears as expected
This is also very easy to deal with.  Just ignore the message.  It is
exactly the same as the above case except perhaps you waited for the
next message to start arriving before you decided what to do about the
previous, corrupt message.

2) message is bad and Message Length is bad, so the next MARKER is not
where it should be
This is a little harder to deal with.  It may be a lot harder for a
BGP implementation that pathologically integrates TCP and BGP Message
parsing.  Perhaps some implementations would choose to try to recover
without session-reset by hoping a new MARKER will arrive soon to
"re-sync" the session.  Perhaps not.  I think the value of this is
quite questionable and highly dependent on how much work it is for the
implementor -- and what he feels are the chances of introducing new
bugs.

> All of the marketing that you're doing here is positioning this as a 'sol=
ution'.  It's not.  Yes, it will stop the flap, but it does NOTHING to fix =
or deal with the underlying bug.  All it does is gloss it over, and as such=
, it will have implications in the field whereby this papers over real bugs=
 and we have now promoted BGP errors into RIB errors.  That's NOT making th=
ings easier to debug, that's just applying a band-aid.

It does do something to keep the network functioning.  Is it
functioning well?  No, of course not.  But there may be only 1 or a
few routes that are bad.

In the case of the LANL incident, 5 /24s were bad.  I can live with
not being able to reach 5 /24s that were announced with bad attribute
flags.  I can even live with a loop in my network for those /24s.  I
can't live with my network down because BGP is flapping.

You are right, this is a band-aid.  It is a very good one when you are
bleeding money.

> A more constructive way to address the real problem here would be to talk=
 about whether we should even re-establish the session after an error.  Lon=
g ago, we made an implementation decision to simply retry.  That would seem=
 to be the real issue at hand.

If you have received bad messages from all your transit providers, it
will not matter if you re-establish the sessions or not, if the bad
messages keep coming.  All your transit will be down and you'll be
bleeding money.

> Sorry, but the point of the standards body is to standardize PROTOCOL cha=
nges.  Everything that has been discussed here are IMPLEMENTATION ISSUES.  =
We don't standardize those, for very good reasons.  And the vendors need ze=
ro help from the IETF in making implementation issues.  If real customers w=
ant a particular behavior, they can always just ask for it, as always.

Would you like a list of some standards-track documents that do not
modify protocols?

>> Related to this, what is your plan for dealing with BGP Attribute
>> re-ordering in the rewrite of RFC4760?
>
> My plan?  My personal plan is to ban the use of all MP extensions, as all=
 of that is simply evil and should be scrubbed off the face of the earth.
>
> I'll be putting this in place as soon as I'm elected Emperor of the Unive=
rse.  ;-)

I agree that MP-BGP is less than ideal.  That's true of many
extensions to BGP.  Sadly, there isn't BGP-5, and BGP-5 would be
needed to clean all of this up.

The reason I ask is because the work on MP-BGP makes a specific
recommendation to re-order the attributes in such a way that is the
opposite of a specific recommendation in the base BGP spec.  If other
work, such as error-handling, wants to depend on the MP-BGP
recommendation being followed, then MP-BGP should actually provide a
way for the neighbor to signal its intent to follow that
recommendation.

That can and perhaps should be done with a new Capability Code.

If that is not done, then a lot of the rules in the error-handling
draft are not useful unless error-handling itself allocates such
Capability Code.

I don't understand the reason for adding this recommendation to MP-BGP
if you don't also think there should be a mechanism by which you and
your neighbor can agree to depend on it.

Also, I'd like to repeat that a lot of the rules in error-handling are
not useful unless the neighbor supports it.  This means it might be
useful within your datacenter network but is probably not useful to
most transit or peers for a long time.

> RFC 4271 doesn't require a specific ordering because it would be bad prot=
ocol design.  As soon as you require ordering, some implementation is going=
 to check that ordering.  There will be more bugs that occur because the ma=
ndated ordering was not followed, and more sessions will be dropped.   As a=
lways, the right thing is to follow Postel's law: be liberal in what you ac=
cept.
>
> Requiring a specific ordering in order to improve error handling is a bad=
 tradeoff: you're creating a host of additional bugs so that you can try to=
 simplify error handling on another set of bugs.

I gather that your general opinion is error-handling is bad.

In addition, you think that specifically promising to order attributes
in the way needed by error-handling is further bad.  Do you think the
recommendation for ordering attributes should be removed from
RFC4760bis?

IMO this is important.

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

From jsw@inconcepts.biz  Thu Jan  3 12:05:46 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15BD321F8DBF for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 12:05:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.75
X-Spam-Level: 
X-Spam-Status: No, score=-2.75 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 pD-HcJTK1HkX for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 12:05:45 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7433821F8DC5 for <grow@ietf.org>; Thu,  3 Jan 2013 12:05:45 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so19053742ieb.31 for <grow@ietf.org>; Thu, 03 Jan 2013 12:05:45 -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=KoTy5Hoynb1b4pOvfTehiHIN3K+bOGTz7bcR78DAqRk=; b=D+pLxFC7oy+6pqzCnV+VHIm4D96GCHik0SWCGCpQ00tU+NxiFkodLTxw7eS80jgAPZ KLOZL5XYlor/twj9J+jWEbdvt8mhS3SU/ZE2v36r3jk20S+VtOMS6LT0wiYvfZwGM70w qhWNtVpgeo2ylodYZVYP98u5HynvMw51K9UxhctEcIHNzVDEEIzTQKyrx3UIDX8e3Nt1 2d1cQfRSKAXSpwJ2Q7MArvmax46jIQaokq0t07sWlilWR9gphzJgChRZzQIia51jqlIa Y1PbhZ6o+/y/Ut59n1FaPn81PkkLI+gCOm3HhN3lODZxwdAM6jL6OgQWebLOisihO3Aa nPBA==
MIME-Version: 1.0
Received: by 10.50.104.232 with SMTP id gh8mr42715935igb.45.1357243544985; Thu, 03 Jan 2013 12:05:44 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 12:05:44 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net>
Date: Thu, 3 Jan 2013 15:05:44 -0500
Message-ID: <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Michael Long <mlong@us.ntt.net>, enkechen@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkoa3q2HO4/QYUvaYJLl2dmUrUsPOL89MQ8aHLUclwbSWb6L7T71uQuYQLSpy0gKRYKfd/Y
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:19 -0800
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 20:05:46 -0000

On Thu, Jan 3, 2013 at 2:35 PM, Michael Long <mlong@us.ntt.net> wrote:
> Either upgrade to fixed code or policy out the offending announcement.

You actually can't policy out the announcement on the receiving side.

This is why I continue to state that you need help from external
parties to solve these problems.  Vendor, BGP neighbor, etc.

When I got called because some of my transit customers were having
their sessions flap endlessly and their routers were logging errors
they did not understand, it took be about an hour to figure out what
prefixes were causing it.  That's because my router had equally poor
logging.  Then I asked the customers if they wanted me to filter out
the 5 bad prefixes from going to them.  That is what they needed until
they could upgrade their software.

On Thu, Jan 3, 2013 at 2:36 PM, Enke Chen <enkechen@cisco.com> wrote:
> A good argument (IMO) has been made in the error handling draft:
>
> ---------
> http://datatracker.ietf.org/doc/draft-ietf-idr-error-handling/
>
> 4. Operational Considerations
>
>    Note that "treat-as-withdraw" is different from discarding an UPDATE
>    message.  The latter violates the basic BGP principle of incremental
>    update, and could cause invalid routes to be kept.  (See also
>    Appendix A.)

I hope we all understand that treat-as-withdraw violates exactly the
same principle.  It just throws away routes which may be valid,
instead of keeping them.

I don't understand the perspective from which you are looking at this
problem.  From mine, there could be a buggy router in my AS, and it
could be withdrawing routes from its RIB.  Then other routers could be
trying to transit traffic across that router, which is then mis-routed
(could be looped) or discarded.

The error-handling draft does not keep the RIB in a good state.
Anyone who thinks otherwise is simply incorrect.

So treat-as-withdraw puts the RIB in a bad state.  Ignore-bad-message
puts the RIB in a bad state.  Exactly how it is bad differs, but
treat-as-withdraw in the current draft is very complicated and does
not provide a band-aid for "all" problems.  Ignore-bad-message is very
simple and provides a band-aid for more problems, including unforeseen
problems.

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

From chris.hall@highwayman.com  Thu Jan  3 13:11:23 2013
Return-Path: <chris.hall@highwayman.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C512721F8D63; Thu,  3 Jan 2013 13:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.312
X-Spam-Level: 
X-Spam-Status: No, score=-0.312 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227]
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 f-2u1Lapce8U; Thu,  3 Jan 2013 13:11:23 -0800 (PST)
Received: from smtp.demon.co.uk (mdfmta005.mxout.tbr.inty.net [91.221.168.46]) by ietfa.amsl.com (Postfix) with ESMTP id C445921F8D61; Thu,  3 Jan 2013 13:11:22 -0800 (PST)
Received: from mdfmta005.tbr.inty.net (unknown [127.0.0.1]) by mdfmta005.tbr.inty.net (Postfix) with ESMTP id CE82FA642FC; Thu,  3 Jan 2013 21:11:20 +0000 (GMT)
Received: from mdfmta005.tbr.inty.net (unknown [127.0.0.1])	by mdfmta005.tbr.inty.net (Postfix) with ESMTP id AA3C5A642F5; Thu,  3 Jan 2013 21:11:20 +0000 (GMT)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta005.tbr.inty.net (Postfix) with ESMTP; Thu,  3 Jan 2013 21:11:20 +0000 (GMT)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1Tqs4N-00012D-Jg; Thu, 03 Jan 2013 21:11:19 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <idr@ietf.org>,	<grow@ietf.org>
Date: Thu, 3 Jan 2013 21:11:14 -0000
Organization: Highwayman
Message-ID: <051101cde9f6$e051b450$a0f51cf0$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3p9tqXZ6AxQf7wTw69zzvTCQm03Q==
Content-Language: en-gb
X-MDF-HostID: 8
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:19 -0800
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 21:11:23 -0000

Jared Mauch wrote (on Thu 03-Jan-2013 at 17:40 +0000):
....
> Not sure who you're asking, but I think this whole draft is an
> idealist attempt to workaround software defects that may be
> uncorrectable as a whole.  (I say this as a $large_operator as
> measured here: http://as-rank.caida.org/?mode0=as-
> ranking&n=10&ranksort=1 )
> 
> The missing prefix because it was ignored, or routing loop because a
> withdraw was ignored will quickly change these folks minds.

I agree with you: if a software defect breaks routeing, then no amount
of extra software can put it together again.

I also agree with you: the issue of "lost NLRI" has to be addressed.
I do not know whether some routeing issues are *always* worse than
wholesale loss of routeing, or wholesale bouncing up and down of
routes.  But some folk would like to be given the choice.

I think that some extra facilities to mitigate the effects of software
defects can be devised, and each operator can then decide which ones
are appropriate to the circumstances, from time to time.

> Take one of the most recent defects:
> 
> http://www.cisco.com/en/US/products/csa/cisco-sa-20100827-bgp.html
> 
> The device takes a valid route on the receive side and corrupts it
> as it forwards it.  While ignoring may be one solutions, there is no
> way to actually know or get remediation of this prefix and software
> defect.

That is an interesting case.

I understand that the bug was: Attribute Type 99 was received with a
length of 3000 bytes; that attribute was sent out as if it was 184
bytes, except that the Length Field in the outgoing attribute still
said 3000.  This is a fine example of a broken attribute hiding any
and all attributes which follow it.  Note that the Message Length,
Withdraw Length and Total Attributes Length were consistent with each
other and with what was actually sent -- so the overall UPDATE Message
was "correctly framed".

What appears to have happened here is that some previously unused and
under-tested code for handling unknown, optional, transitive
attributes did something foolish.  3000 is 0xBB8 and 184 is 0xB8.  So,
the left hand knew that the attribute length was two bytes, while the
right hand only used the less significant byte.  If the programmer had
got things consistently wrong, and used the less significant byte of
the length throughout, there would have been far less excitement !

One can draw some comfort from the fact that the packing of the
overall message -- code which is exercised micro-second in,
micro-second out -- got things right.

A very small minority of routes carried the Attribute 99.  So,
crashing the session threw away many entirely innocent routes.  And,
of course, the bug didn't go away, so sessions cycled up and down.

In this particular case the source of Attribute 99 shut itself down
within 30 minutes -- because that was the planned duration for the
experiment, *not* because it had been identified as the source of some
calamity.  So, perhaps unusually, the source of the problem simply
went away.  I wonder if future latent bugs will be swept up as quickly
?

Suppose such a latent bug strikes a particularly common BGP
implementation.  Suppose I am a little ISP and both my Transit
Providers' border routers do something equally unfortunate.  And
suppose either:

  a) sessions bounce up and down until... until...

or:

  b) my shiny new BGP implementation recovers from this
     Message-Level error by treating-as-withdraw the
     affected prefix(es)...

...vote now :-)

Chris


From jsw@inconcepts.biz  Thu Jan  3 13:19:59 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF7F021F8BCE for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 13:19:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level: 
X-Spam-Status: No, score=-2.008 tagged_above=-999 required=5 tests=[AWL=-0.742, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 GQv8t9hnvCGU for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 13:19:59 -0800 (PST)
Received: from mail-ie0-f174.google.com (mail-ie0-f174.google.com [209.85.223.174]) by ietfa.amsl.com (Postfix) with ESMTP id 6529D21F8B6D for <grow@ietf.org>; Thu,  3 Jan 2013 13:19:59 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id c11so18565946ieb.5 for <grow@ietf.org>; Thu, 03 Jan 2013 13:19:57 -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=VB1oEF5eTAd+ovvAxVi609AsHGoQJTr8iiQDMpyvHVc=; b=pgpEFlKjPDJ8go/tQeqhSO+9KWpKnRigHMa2va8KBni0ED674cQDgmIIECSgQdJ83E 5qYiALmBjvSVpbND9Q1jtafDzYXImP7qIOXmNGEFoEb3K787S/yZh6my8yIFg5Ve0Xk5 PPV/40TwObnOGHlFHLS50q58KJOjSNYkd2x5LD26inrJEPFc6jW6L/6eAgF9stlBXAfC lKn/YIVAF0+bWDVFkwQgL5vtKYYYR6161pwxjVrCggrTL5rvR6qSs6sML9OxGVGNr0Hq huSQkb168jhr+2NoBfkZSFOgKbmLA7rT9yzZPv89GzSkqxQff4oUdURlJazorbAZ94gF uOgQ==
MIME-Version: 1.0
Received: by 10.50.187.225 with SMTP id fv1mr39120986igc.96.1357247997718; Thu, 03 Jan 2013 13:19:57 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 13:19:57 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com>
Date: Thu, 3 Jan 2013 16:19:57 -0500
Message-ID: <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Robert Raszuk <robert@raszuk.net>
Content-Type: multipart/alternative; boundary=14dae9340fe1c6b13104d268eca0
X-Gm-Message-State: ALoCoQla3w4/fDFHps66RZztIJyyj4DewLQko7XyYl1sXFUvkOFHRI0dJYo586ciZjWbY12+BGvi
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:19 -0800
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 21:19:59 -0000

--14dae9340fe1c6b13104d268eca0
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jan 3, 2013 at 3:18 PM, Robert Raszuk <robert@raszuk.net> wrote:
> How are you going to clean the NLRIs in your network (both transit or
> stub) which were withdrawn in the messages your BGP implementation
> declared "bad" and decided to ignore ?

I can fix them later, maybe even after I've had time to fully analyze the
problem and get a software update from my vendor.  Maybe I'll try a refresh
or a session-reset, but I won't be at the mercy of repeatedly flapping
session and phone ringing off the hook with angry customers!

A lot of folks are thinking about this problem in the context of the big
carrier who doesn't want a hard-to-diagnose problem of 1 RIB entry being
wrong.  That's okay, it is one way to think about it.

A second way to think of it is as a small/regional ISP.  If one or more of
his transits are flapping because of a bad path on the DFZ, that is going
to cost him money and customers.  If he has no way to mitigate it, he is at
the mercy of external parties.  He could just use "ignore bad messages" and
at least stop bleeding money.  He does not care if he can't reach  5 /24s
at LANL, they are unimportant to him.  What is important is if he has any
customers left next week.

A third way is the small- or medium-datacenter network.  Imagine you are a
typical small/medium shop and you have some Cisco/Juniper/Brocade stuff for
your ASBRs and your core, but you bought a bunch of RainbowPoop Router Co
switches for your racks, because they are inexpensive and they support
EVPN, L3VPN, VPLS, or some other feature you want but Cisco/Juniper/Brocade
don't put into their inexpensive product.

So your network looks like this:

ISP1    ISP2

  CISCO  JUNIPER
  |    \/
  |    /\                \   |
  |   /  \                \  |
  TOR1    TOR2    ....    TOR99

Now imagine your JUNIPER supports NewVpnThing and that's a feature you
decided to use on the RainbowPoop TOR devices.  But TOR1 sends a bad BGP
update.  JUNIPER knows about NewVpnThing and sees a bad BGP attribute (that
it recognizes) so it does whatever the NewVpnThing spec says, and tears
down the session to TOR1.

CISCO on the other hand, does not know about NewVpnThing so this router
doesn't even understand the update is bad.  It just passes it along to TOR2
.. TOR99.  Now those boxes all tear down their session to the CISCO.  Then
they re-establish.  Then they go down again.  They keep on doing this and
the network is freaking out.

By the time your in-house clue notices, your symptom is that 99 identical
TORs are flapping their BGP to your CISCO.  You probably don't even notice
the 1 TOR that is flapping to JUNIPER.  Maybe JUNIPER even logs something
helpful but you may not investigate it for a while.

So your CISCO which is following the base spec is carrying a buggy update
to your 99 other RainbowPoop TORs and they are all failing.  Your JUNIPER
which knows about the NewVpnThing is following its spec and protecting the
other TORs from this problem, but it is probably not helpful since your
network is in chaos from all the flapping.

What do you do?  Call vendor support.  Probably for CISCO and RainbowPoop.
 Well, now you are expecting the TAC of Cisco and the TAC of RainbowPoop to
cooperate, which they'll have trouble doing; and it may take ages before
anyone identifies the root cause of the problem is really TOR1.

There are going to be a lot of RainbowPoop routers in the future, and many
of them may use BGP.  We should make BGP more robust.

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

--14dae9340fe1c6b13104d268eca0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 3, 2013 at 3:18 PM, Robert Raszuk &lt;<a href=3D"mailto:robert@=
raszuk.net">robert@raszuk.net</a>&gt; wrote:<br>&gt; How are you going to c=
lean the NLRIs in your network (both transit or<br>&gt; stub) which were wi=
thdrawn in the messages your BGP implementation<br>
&gt; declared &quot;bad&quot; and decided to ignore ?<br><br>I can fix them=
 later, maybe even after I&#39;ve had time to fully analyze the problem and=
 get a software update from my vendor. =A0Maybe I&#39;ll try a refresh or a=
 session-reset, but I won&#39;t be at the mercy of repeatedly flapping sess=
ion and phone ringing off the hook with angry customers!<br>
<br>A lot of folks are thinking about this problem in the context of the bi=
g carrier who doesn&#39;t want a hard-to-diagnose problem of 1 RIB entry be=
ing wrong. =A0That&#39;s okay, it is one way to think about it.<div><br></d=
iv>
<div>A second way to think of it is as a small/regional ISP. =A0If one or m=
ore of his transits are flapping because of a bad path on the DFZ, that is =
going to cost him money and customers. =A0If he has no way to mitigate it, =
he is at the mercy of external parties. =A0He could just use &quot;ignore b=
ad messages&quot; and at least stop bleeding money. =A0He does not care if =
he can&#39;t reach =A05 /24s at LANL, they are unimportant to him. =A0What =
is important is if he has any customers left next week.<br>
<br>A third way is the small- or medium-datacenter network. =A0Imagine you =
are a typical small/medium shop and you have some Cisco/Juniper/Brocade stu=
ff for your ASBRs and your core, but you bought a bunch of RainbowPoop Rout=
er Co switches for your racks, because they are inexpensive and they suppor=
t EVPN, L3VPN, VPLS, or some other feature you want but Cisco/Juniper/Broca=
de don&#39;t put into their inexpensive product.<br>
<br>So your network looks like this:<br><br><font class=3D"Apple-style-span=
" face=3D"&#39;courier new&#39;, monospace">ISP1 =A0 =A0ISP2</font><div><fo=
nt class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monospace"><br=
></font></div>
<div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
ace">=A0 CISCO =A0JUNIPER</font></div><div><font class=3D"Apple-style-span"=
 face=3D"&#39;courier new&#39;, monospace">=A0 | =A0 =A0\/</font></div><div=
><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monospace"=
>=A0 | =A0 =A0/\ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0\ =A0 |</font></div>
<div><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monosp=
ace">=A0 | =A0 / =A0\ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0\ =A0|</font></div><di=
v><font class=3D"Apple-style-span" face=3D"&#39;courier new&#39;, monospace=
">=A0 TOR1 =A0 =A0TOR2 =A0 =A0.... =A0 =A0TOR99<br>
</font><br>Now imagine your JUNIPER supports NewVpnThing and that&#39;s a f=
eature you decided to use on the RainbowPoop TOR devices. =A0But TOR1 sends=
 a bad BGP update. =A0JUNIPER knows about NewVpnThing and sees a bad BGP at=
tribute (that it recognizes) so it does whatever the NewVpnThing spec says,=
 and tears down the session to TOR1.</div>
<div><br></div><div>CISCO on the other hand, does not know about NewVpnThin=
g so this router doesn&#39;t even understand the update is bad. =A0It just =
passes it along to TOR2 .. TOR99. =A0Now those boxes all tear down their se=
ssion to the CISCO. =A0Then they re-establish. =A0Then they go down again. =
=A0They keep on doing this and the network is freaking out.<br>
<br>By the time your in-house clue notices, your symptom is that 99 identic=
al TORs are flapping their BGP to your CISCO. =A0You probably don&#39;t eve=
n notice the 1 TOR that is flapping to JUNIPER. =A0Maybe JUNIPER even logs =
something helpful but you may not investigate it for a while.</div>
<div><br></div><div>So your CISCO which is following the base spec is carry=
ing a buggy update to your 99 other RainbowPoop TORs and they are all faili=
ng. =A0Your JUNIPER which knows about the NewVpnThing is following its spec=
 and protecting the other TORs from this problem, but it is probably not he=
lpful since your network is in chaos from all the flapping.</div>
<div><br></div><div>What do you do? =A0Call vendor support. =A0Probably for=
 CISCO and RainbowPoop. =A0Well, now you are expecting the TAC of Cisco and=
 the TAC of RainbowPoop to cooperate, which they&#39;ll have trouble doing;=
 and it may take ages before anyone identifies the root cause of the proble=
m is really TOR1.</div>
<div><br></div><div>There are going to be a lot of RainbowPoop routers in t=
he future, and many of them may use BGP. =A0We should make BGP more robust.=
<br><br>-- <br>Jeff S Wheeler &lt;<a href=3D"mailto:jsw@inconcepts.biz">jsw=
@inconcepts.biz</a>&gt;<br>
Sr Network Operator =A0/ =A0Innovative Network Concepts<br></div></div>

--14dae9340fe1c6b13104d268eca0--

From chris.hall@highwayman.com  Thu Jan  3 13:49:01 2013
Return-Path: <chris.hall@highwayman.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD4C21F8D63; Thu,  3 Jan 2013 13:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.312
X-Spam-Level: 
X-Spam-Status: No, score=-0.312 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227]
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 RcEkYi5PWFjs; Thu,  3 Jan 2013 13:49:01 -0800 (PST)
Received: from smtp.demon.co.uk (mdfmta009.mxout.tbr.inty.net [91.221.168.50]) by ietfa.amsl.com (Postfix) with ESMTP id D7AAA21F8D61; Thu,  3 Jan 2013 13:49:00 -0800 (PST)
Received: from mdfmta009.tbr.inty.net (unknown [127.0.0.1]) by mdfmta009.tbr.inty.net (Postfix) with ESMTP id 5A876384083; Thu,  3 Jan 2013 21:48:59 +0000 (GMT)
Received: from mdfmta009.tbr.inty.net (unknown [127.0.0.1])	by mdfmta009.tbr.inty.net (Postfix) with ESMTP id 4093E384081; Thu,  3 Jan 2013 21:48:59 +0000 (GMT)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta009.tbr.inty.net (Postfix) with ESMTP; Thu,  3 Jan 2013 21:48:59 +0000 (GMT)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1Tqsen-00012I-QO; Thu, 03 Jan 2013 21:48:58 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <idr@ietf.org>,	<grow@ietf.org>
Date: Thu, 3 Jan 2013 21:48:52 -0000
Organization: Highwayman
Message-ID: <051801cde9fc$228a93f0$679fbbd0$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3p/B8DLkTuV2qMRGSIZ+VdYn4fOw==
Content-Language: en-gb
X-MDF-HostID: 4
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:19 -0800
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 21:49:01 -0000

Robert Raszuk wrote (on Thu 03-Jan-2013 at 20:18 +0000):
> To: Jeff Wheeler
> 
> Hi Jeff,
> 
> > Ignore-bad-message is very simple and provides a band-aid for more
> > problems, including unforeseen problems.

> How are you going to clean the NLRIs in your network (both transit
> or stub) which were withdrawn in the messages your BGP
> implementation declared "bad" and decided to ignore ?

It's a good question.  But not, I think, the entire question.

However bad or difficult to clean up, what if that's not as bad as the
alternative ?

[So: all alone somewhere up a remote, cold mountain you slip and your
arm gets stuck firmly in a crevice.  Clearly, you are fond of it and
hacking it off has its drawbacks.  But compared to hypothermia... ?
Mind you, if mountaineering standards are dead-set against the hacking
off of arms, perhaps your mountaineering equipment won't include a
knife :-)]

Chris


From jsw@inconcepts.biz  Thu Jan  3 14:01:10 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68F621F8D7C for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.626
X-Spam-Level: 
X-Spam-Status: No, score=-2.626 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 n1XXugTfWF8I for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 14:01:09 -0800 (PST)
Received: from mail-ie0-f169.google.com (mail-ie0-f169.google.com [209.85.223.169]) by ietfa.amsl.com (Postfix) with ESMTP id 25E5C21F8D59 for <grow@ietf.org>; Thu,  3 Jan 2013 14:01:09 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id c14so18935751ieb.14 for <grow@ietf.org>; Thu, 03 Jan 2013 14:01:08 -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=N5gbpLsm99xrON5H+PvRkpdeiMLte8Vnw4Nu7kOdxe4=; b=FHLFwdbqt7us7K0x0KOmolDKWEvLQ1O/wj8nVkCNHWamKT9XYXtFZmzZe/TNL/ZlFW tWs2gBD4tVagECcOxq5uFCXde6dI1l17QyABa6ddJRP+XQ+UrhTsAO3Wwx8NNVRg06Sc tYuFa2dmspu8HqMfwqcpu3QUsz44gMYM/CP6rQGzukwx1E28d9rb2Nb/p7EvN7UZ4Pzf jNN3z1ZKj6Kx4qUxo8Va/vexlAstOqJuo2c0oX/Tt2LB9m49BNm0JfjdlGqciesSMKSC nQgPN5udRnrsqqBxSk1uAeG45GhHPp+gZ/elEXbjCLZ5wlohJDmHDGvVD8/UhUm7pKp5 HZGw==
MIME-Version: 1.0
Received: by 10.50.187.225 with SMTP id fv1mr39200775igc.96.1357250468349; Thu, 03 Jan 2013 14:01:08 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 14:01:08 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net>
Date: Thu, 3 Jan 2013 17:01:08 -0500
Message-ID: <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Jared Mauch <jared@puck.nether.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQklJN/ntIRCrkOoIyrFVw7V8d42hyvVg/YxxTROZsCNsSo7/iteJuju4VnsgKbIPjt+m22z
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:19 -0800
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 22:01:10 -0000

On Thu, Jan 3, 2013 at 4:28 PM, Jared Mauch <jared@puck.nether.net> wrote:
> Also, if you're seeing some problem, I'm sure that some other set of
> people out there will be seeing it as well.  The shared pain/cost will
> exist.  If you can't take the risk of speaking BGP, have your ISP send you
> default (or nothing) and advert your prefixes and call it a day.

There may be no shared pain if you are using BGP only within your
datacenter network.  This is precisely why I provided the RainbowPoop
scenario.  This is not your 1990s BGP anymore.  Anyone who has MPLS
VPNs signaled using BGP already knows this but maybe isn't cognizant
of it in this context.

You continue to make this argument that breaking your network so you
notice a problem is good.  I would like to have the option to notice
the problem by actually parsing my syslogs and NOT having my network
break and cost me and customers a bunch of money.  That's not what I
would really do, though.  I would just re-actively configure
ignore-bad-messages if I needed to.  Because I agree with you, I would
like BGP to flap if something unexpected happens.  However, I might
need to stop it from flapping to remain in business.

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

From randy@psg.com  Thu Jan  3 15:48:30 2013
Return-Path: <randy@psg.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA7521F8E04; Thu,  3 Jan 2013 15:48:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 0xzMxl7OmTUj; Thu,  3 Jan 2013 15:48:30 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 547D921F8E03; Thu,  3 Jan 2013 15:48:30 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TquWS-0004Te-6D; Thu, 03 Jan 2013 23:48:28 +0000
Date: Fri, 04 Jan 2013 08:48:26 +0900
Message-ID: <m238yhkeut.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tony Li <tony.li@tony.li>
In-Reply-To: <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:36:13 -0800
Cc: idr wg <idr@ietf.org>, grow <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 23:48:30 -0000

> A syntactic error would be any inconsistency of length fields,
> incompatibility between a type and a length, or any other error that
> would introduce any doubt about the parsing of the message.  Once this
> type of error has occurred, then the remainder of the data stream is
> wholly in doubt.  A session reset seems like the only (conservative)
> way of handling this, as it's unclear that further data would be
> accurate.

both ears

> I'm very open to a discussion of alternatives to session flap for
> these cases.  Should we require manual intervention before session
> restart?  This would seem reasonable.

you may have more faith in the alacrity of manual response than i

> Semantic errors would be consistency violations within the contents of
> the message.  In these cases, treat-as-withdraw seems reasonable.

and the tail

randy

From sairay@cisco.com  Thu Jan  3 18:37:19 2013
Return-Path: <sairay@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9D121F8E4E; Thu,  3 Jan 2013 18:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.372
X-Spam-Level: 
X-Spam-Status: No, score=-10.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
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 yjfHA39+lWAs; Thu,  3 Jan 2013 18:37:18 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id B734421F88B2; Thu,  3 Jan 2013 18:37:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1115; q=dns/txt; s=iport; t=1357267039; x=1358476639; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=QuiKMeOUxFe9uZZwkNKy2sXtCehC/53JwBeRFzi9M7g=; b=mHeyOS2ErcWnJlpmHy/X4S/6FxDIhJEzN5INLX+pcJwbYdXf/G3BV5wW ent8VLIjrJMP+/KmiiHyhvx3nU5xUP1PfUDEZWKgwY5HeMSLMX39avBbZ lJBL2E0lGi2wSlf/dynUY7ICddbDq6CE8GPGseSlaK32RpHdmzj+GkrzF I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJE/5lCtJXHA/2dsb2JhbABFvUwWc4IeAQEBBDo/DAQCAQgOAwQBAQEKFAkHMhQJCAIEAQ0FCIgKAbZxkDlhA6ZUgnSBaAc3
X-IronPort-AV: E=Sophos;i="4.84,406,1355097600"; d="scan'208";a="158719339"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 04 Jan 2013 02:37:18 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r042bHYk010453 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jan 2013 02:37:18 GMT
Received: from xmb-rcd-x13.cisco.com ([169.254.3.77]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.02.0318.004; Thu, 3 Jan 2013 20:37:17 -0600
From: "Saikat Ray (sairay)" <sairay@cisco.com>
To: Jeff Wheeler <jsw@inconcepts.biz>, Tony Li <tony.li@tony.li>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6iP9zU1iOSP0s0au+0QHwDr5iJg4c+tQ
Date: Fri, 4 Jan 2013 02:37:16 +0000
Message-ID: <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com>
In-Reply-To: <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.71.139.156]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 03 Jan 2013 18:38:02 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 02:37:19 -0000

-----Original Message-----
From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Jeff =
Wheeler
Sent: Thursday, January 03, 2013 6:34 PM
To: Tony Li
Cc: idr@ietf.org; grow@ietf.org
Subject: Re: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-erro=
r-handling-06.txt

On Thu, Jan 3, 2013 at 8:01 PM, Tony Li <tony.li@tony.li> wrote:
> Example please?  Assuming that the prefixes are parsed out of the message=
 correctly, then treating them as withdrawn should be hazard free.

If a transit router in your AS treats-as-withdraw a prefix, other routers m=
ay try to send traffic across it, but the router which has treated-as-withd=
raw will either have no information for that route, or it will have made a =
different bestpath choice.  This could cause a loop or a blackhole.

[SR] If the transit router treated the prefix as "withdrawn", then it will =
remove the corresponding path. If there are no other paths for that net, th=
en the router would send withdraws for that prefix to its own peers. So no =
other router would send traffic to it in the steady state.


From jsw@inconcepts.biz  Thu Jan  3 18:48:36 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B917421F8E07 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 18:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.704
X-Spam-Level: 
X-Spam-Status: No, score=-2.704 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 VbBTcDLEyEWS for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 18:48:36 -0800 (PST)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3512121F8DFD for <grow@ietf.org>; Thu,  3 Jan 2013 18:48:36 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id 17so19147687iea.2 for <grow@ietf.org>; Thu, 03 Jan 2013 18:48:35 -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 :content-transfer-encoding:x-gm-message-state; bh=a9iEo2bBz8vgUqyh1ntqrao1f0Lgo1OZdYImHhMiQHw=; b=ZJ6+tBUNpOc7vECVmxjin/elMbtpCL+gtxnxQ4NDa4XKphXKotvO2BG0rTWwqYsQkR JGfr4sCbJP6HEVv6+WXzEyqZGblNHFmJr2ZguUXdnF2OOEphsjmRX7nJ2MqmQB9ddxay iLyCTFRmbjCiqjjdPwbGSh09B9p54AuTlVu31k75eDWaOQLVqBsNL0WD0xUldIecQR5X 3LKl/1YJj2md+PpfrUgb2RA3hhyZZ4fjhS8uIGjRFkxfeMd7tHaBclGgj7Oh614Nq3sB xgapQA//HUb9PmmdKY4WPZAtizW5mPsPPOxqhJa87XK20IzTS1FiK7vHrh34Ki6hoJCN 25AA==
MIME-Version: 1.0
Received: by 10.50.104.232 with SMTP id gh8mr43382290igb.45.1357267715845; Thu, 03 Jan 2013 18:48:35 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Thu, 3 Jan 2013 18:48:35 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com>
Date: Thu, 3 Jan 2013 21:48:35 -0500
Message-ID: <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: "Saikat Ray (sairay)" <sairay@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlVsAmcxxZdhD0nzg97D+O0u+7LoXTgEb7KeV9O9daWLe2ncby4lrrcGi/kCnD1x60yii5C
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 02:48:36 -0000

On Thu, Jan 3, 2013 at 9:37 PM, Saikat Ray (sairay) <sairay@cisco.com> wrot=
e:
> If a transit router in your AS treats-as-withdraw a prefix, other routers=
 may try to send traffic across it, but the router which has treated-as-wit=
hdraw will either have no information for that route, or it will have made =
a different bestpath choice.  This could cause a loop or a blackhole.
>
> [SR] If the transit router treated the prefix as "withdrawn", then it wil=
l remove the corresponding path. If there are no other paths for that net, =
then the router would send withdraws for that prefix to its own peers. So n=
o other router would send traffic to it in the steady state.

Perhaps you read "ASBR" where in fact I wrote "transit router?"  The
behavior you describe is wrong.

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

From sairay@cisco.com  Thu Jan  3 18:53:16 2013
Return-Path: <sairay@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1FD621F8E8C; Thu,  3 Jan 2013 18:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.372
X-Spam-Level: 
X-Spam-Status: No, score=-10.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
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 4OmXGtj+r0vC; Thu,  3 Jan 2013 18:53:15 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1C53421F8E69; Thu,  3 Jan 2013 18:53:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1799; q=dns/txt; s=iport; t=1357267987; x=1358477587; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=evAURXRPjF8Fx9mtuu8IeJgFq2CJJHFbQx8oXWQTD58=; b=PWqFm/Lm4iFpamwGP8hUnJY/ciWtm1Gq7cXbAMBWnpZTbpZM84Ro/EZE 7Y6ODj3t6j2T/pJgi8nNwrywziLg4OX+zVsZJYNv/zyXef7jnGaczGizi Ak2uWZa0/lChqu8LjrsQA/R/wYtzdAG4kXt53F67A09vX/YL7Zg2f5osU U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIFD5lCtJXHB/2dsb2JhbABFvUwWc4IeAQEBBDo/DAQCAQgOAwQBAQEKFAkHMhQJCAIEDgUIiAoBtnOQOWEDplSCdIFoBzc
X-IronPort-AV: E=Sophos;i="4.84,406,1355097600"; d="scan'208";a="158507013"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-1.cisco.com with ESMTP; 04 Jan 2013 02:53:06 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r042r6dM027556 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jan 2013 02:53:06 GMT
Received: from xmb-rcd-x13.cisco.com ([169.254.3.77]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.004; Thu, 3 Jan 2013 20:53:06 -0600
From: "Saikat Ray (sairay)" <sairay@cisco.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6iX+pP5muDGR70G7eUwvXv72hJg4d8fg
Date: Fri, 4 Jan 2013 02:53:05 +0000
Message-ID: <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com>
In-Reply-To: <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [171.71.139.156]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 02:53:16 -0000

-----Original Message-----
From: Jeff Wheeler [mailto:jsw@inconcepts.biz]=20
Sent: Thursday, January 03, 2013 6:49 PM
To: Saikat Ray (sairay)
Cc: idr@ietf.org; grow@ietf.org
Subject: Re: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-erro=
r-handling-06.txt

On Thu, Jan 3, 2013 at 9:37 PM, Saikat Ray (sairay) <sairay@cisco.com> wrot=
e:
> If a transit router in your AS treats-as-withdraw a prefix, other routers=
 may try to send traffic across it, but the router which has treated-as-wit=
hdraw will either have no information for that route, or it will have made =
a different bestpath choice.  This could cause a loop or a blackhole.
>
> [SR] If the transit router treated the prefix as "withdrawn", then it wil=
l remove the corresponding path. If there are no other paths for that net, =
then the router would send withdraws for that prefix to its own peers. So n=
o other router would send traffic to it in the steady state.

Perhaps you read "ASBR" where in fact I wrote "transit router?"  The behavi=
or you describe is wrong.

[SR] Wrong in what sense? BGP code does not care whether it is a transit or=
 an ASBR. What I described is exactly what the code will do.
                (i) a path for a prefix (a "net") is withdrawn.
              (ii) BGP deletes the path from that net.
            (iii) BGP reruns bestpath computation.
            (iv) If the bestpath changes,=20
                    (a) if there is a new bestpath, then BGP readvertises t=
he new bestpath to all its peers
                    (b) if there is no bestpath (which would be the case wh=
en there is no path for the net), BGP will send withdraws to all its peers.



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

From tony.li@tony.li  Thu Jan  3 18:56:27 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2DEA21F8E94 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 18:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.117
X-Spam-Level: 
X-Spam-Status: No, score=-100.117 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 uRz2+EVdM2Q4 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 18:56:27 -0800 (PST)
Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:48]) by ietfa.amsl.com (Postfix) with ESMTP id 2935121F8EA7 for <grow@ietf.org>; Thu,  3 Jan 2013 18:56:27 -0800 (PST)
Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta05.emeryville.ca.mail.comcast.net with comcast id je7y1k0021ZMdJ4A5ewTMZ; Fri, 04 Jan 2013 02:56:27 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta16.emeryville.ca.mail.comcast.net with comcast id jeuE1k00A52qHCY8ceuGPr; Fri, 04 Jan 2013 02:54:25 +0000
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com>
Date: Thu, 3 Jan 2013 18:54:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6737CEC8-E3CF-419B-84BF-8713CB67D709@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj =kdJKVYww@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357268187; bh=euXDSWnq3cK4jTWcumRYHFy2ERyVePBZ+cvLfiq0qmg=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=kAa8GXO6OrJoRO0pjwzDztxbwlwRdPUJBMp79ZEuoE2BXagwH7E3ZYQgeuo6h1NLB UvGYtLDHl7VQwzpCuchFjueHUjMllRAZpBU2mgvLpDqMFydVsW+frwXzsHhlcYybDb KrSru8JvfuL+PKoxSZfWbZ+mlH07ldQPsvElMgE9DdLI/imqpb4mO3zL7r+j2OrqJ6 MB0AVlu9KthSDHoIOQbfBA8fWmLgo4NyoT8c7w7Wn5q94HkfyBvD7xg7QWYxBAskar SYsdB/ySuuJCff+vE0xhl5r774WIHrEBPi/uTrW3UjDOWv9R5tQU3VTUltEI/eoo9u FquEDfPqQ9bng==
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 02:56:27 -0000

On Jan 3, 2013, at 6:33 PM, Jeff Wheeler <jsw@inconcepts.biz> wrote:

>> Non-sequitur.  Cyclic resets are orthogonal to treat-as-withdraw.  As =
enumerated above, ignore-bad-message is harder to implement and is more =
dangerous.
>=20
> No, ignore-bad-message is not harder to implement.  To say so is =
simply a lie.


I'm sorry, but this conversation has taken a turn for the worse.   I may =
be wrong (I really don't think so), but I am not lying.

You owe me an apology and I'm not going to continue this conversation =
until you do.

Tony


From jsw@inconcepts.biz  Thu Jan  3 22:41:44 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A0921F8696 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 22:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.706
X-Spam-Level: 
X-Spam-Status: No, score=-2.706 tagged_above=-999 required=5 tests=[AWL=0.044,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 O495t+n1tU2R for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 22:41:43 -0800 (PST)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8C22F21F8689 for <grow@ietf.org>; Thu,  3 Jan 2013 22:41:43 -0800 (PST)
Received: by mail-oa0-f53.google.com with SMTP id j6so14827506oag.12 for <grow@ietf.org>; Thu, 03 Jan 2013 22:41:43 -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=Cb6gRitiz7xJPChGl6HRGs/hag1hhO3trM6Axq02QLg=; b=c0GkZMGEvoRtufb87zS0p39Oo3s7nCy3WGt7mrlxUv5tTG3b9RN76BFD0Bb9/kbZ5+ Iq/bgnBZ1YpODMEkJCbeTxoaQlYZyg50KYCL6wrJw1SV1DrmQrttU942Ch4w1ToU8W8E uZyG2Ecw9upYESZZ7sjogsru/KdmtNWlCMGRCSz2/vwF0qpp1WAg0N1MX3rSADu9IJBo xE9EYwpsMAbqR54kF9frPX+LonKcQPzc0IyFWa6wG6KClXP6wZYIC4W+0eaX9sxRS1ND uLp/lx+Vs1YGOqE5iI4o6dc/0J8N/JdbeRWNQ9KS780BvbyeGpSTWc8jSHnxy0Jx4NKY 9uRA==
MIME-Version: 1.0
Received: by 10.182.162.66 with SMTP id xy2mr38593043obb.82.1357281702864; Thu, 03 Jan 2013 22:41:42 -0800 (PST)
Received: by 10.76.139.232 with HTTP; Thu, 3 Jan 2013 22:41:42 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com>
Date: Fri, 4 Jan 2013 01:41:42 -0500
Message-ID: <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: "Saikat Ray (sairay)" <sairay@cisco.com>, Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlSkdgzJViB//wgdpYxXD6h8CtyyO/vpapZqV68fOjOv9C2bI2ejavepaTLBR5n+WM6GN7/
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 06:41:44 -0000

On Thu, Jan 3, 2013 at 9:53 PM, Saikat Ray (sairay) <sairay@cisco.com> wrote:
> [SR] Wrong in what sense? BGP code does not care whether it is a transit or an ASBR. What I described is exactly what the code will do.
>                 (i) a path for a prefix (a "net") is withdrawn.
>               (ii) BGP deletes the path from that net.
>             (iii) BGP reruns bestpath computation.
>             (iv) If the bestpath changes,
>                     (a) if there is a new bestpath, then BGP readvertises the new bestpath to all its peers
>                     (b) if there is no bestpath (which would be the case when there is no path for the net), BGP will send withdraws to all its peers.

Bugs can be present at other places than an ASBR.  Imagine the
following very ordinary network:

AS100 --- [ ASBR2 --- AR3 --- ASBR4 --- ] AS500

ASBR2 will have iBGP routing exchange with ASBR4 by some means.  This
may be an ordinary iBGP session, via a route-reflector, or whatever.
If AR3 is buggy but it is in the forwarding path between ASBR2 and
ASBR4, then ASBR4 potentially will send packets to AR3, yet AR3 has
treat-as-withdraw a route.  ASBR4 is not subject to the bug, receives
and installs the iBGP-learnt route from ASBR2, and happily announces
it to AS500.

Now you see that ASBR4 and AS500 can both send traffic into the
network which is either blackholed or looped because of a bug in AR3.

This is exactly why the base BGP specification has a lot of rules
about what kind of routing policy you shouldn't apply to iBGP-learnt
routes.

You can create loops or blackholes with no malfunction at all, if your
vendor has given you a little bit of rope -- the ability to apply a
route-map to an iBGP neighbor and alter local-preference or various
other path attributes which influence the bestpath decision.

You certainly will encounter blackholes or loops if a router in the
middle of your network is buggy and does treat-as-withdraw.

If every AS contained only one router (or two), you would be correct.
However, you have overlooked the possibility of a bug affecting just a
path learnt by a transit router in the middle of an AS.

On Thu, Jan 3, 2013 at 9:54 PM, Tony Li <tony.li@tony.li> wrote:
>> No, ignore-bad-message is not harder to implement.  To say so is simply a lie.
>
> I'm sorry, but this conversation has taken a turn for the worse.   I may be wrong (I really don't think so), but I am not lying.
>
> You owe me an apology and I'm not going to continue this conversation until you do.

If calling your statement a lie has offended you, I apologize.  It is,
however, absolutely wrong; and you've framed it as absolutely right.

To review, you've said that ignoring a BGP message is not even
possible.  Of course we know that isn't true.  You've also said it is
harder to ignore a message than to treat-as-withdraw.  This is not
true either.  To do treat-as-withdraw you have to, at minimum, extract
NLRI from a known to be damaged message.  The current error-handling
draft then requires you to apply numerous rules.  Only then may you
decide if you treat-as-withdraw or terminate the BGP session.  Your
assertions cannot possibly be correct in any implementation, period.

The fact is you don't want to ignore messages.  I am much more
persuaded by your argument that ignoring messages may result in the
persistence of bad RIB entries which may be re-forwarded within or
outside the AS.  That is a good argument.  It's not constructive,
however, to cloud the issue by making absurd statements like "ignoring
a message is impossible."  It is possible, you just feel strongly that
it is the wrong approach.


Operators continuously feel that the IETF does not understand their
concerns.  The IETF feels that operators don't participate.  Both are
right.

I'm giving you the operator perspective and I am perfectly willing to
admit that my suggestion is both extreme and potentially stupid; but I
think it is still be smarter than the one on the table right now.  It
would be more productive for you to state the reason why you think
ignoring messages is stupid, than to simply say it's not possible or
it's too hard.

If you want operators to participate in the process, you have got to
be forthright with people who may have a very different view than you.
 I can say, I want to crush my thumb with a hammer, and you can tell
me that's stupid and be right.  If you say it's not possible because
hammers don't work that way, of course I'm going to call you out
because I know hammers can be swung in all manner of dangerous ways.
If you tell me my position is stupid, at least that is a matter of
opinion and open to argument.

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

From sairay@cisco.com  Thu Jan  3 22:54:12 2013
Return-Path: <sairay@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719E121F8E64; Thu,  3 Jan 2013 22:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.372
X-Spam-Level: 
X-Spam-Status: No, score=-10.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227]
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 fyBFqK4E+xFU; Thu,  3 Jan 2013 22:54:11 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id AC77721F8E76; Thu,  3 Jan 2013 22:54:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=744; q=dns/txt; s=iport; t=1357282451; x=1358492051; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BxdHJP3wjNr6X5rr9ym9lkqftZMBQUBbrMXPISA7QGU=; b=IYfyQklL5kKiTEBJl9AnCUSPYKaQEYAwapJILOxQsb90T7ULE9QqFI70 zGrrckXikBL7D1sCuAb41DXdx5n1GqxiUy+vysg2HwlnsP7QS85dM91Yr FHgs8xjGxc2qToktIcjzfM0gV8J/OsnQGgP1dQYJrUnRYEOlHV2lxxUbr 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMZ75lCtJXHB/2dsb2JhbABFvU8Wc4IfAQEEOj8QAgEIDhQUEDIlAgQBDQ2IC7ZlkDhhA6ZUgnSCJg
X-IronPort-AV: E=Sophos;i="4.84,408,1355097600"; d="scan'208";a="155776746"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 04 Jan 2013 06:54:11 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r046sApG013898 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jan 2013 06:54:10 GMT
Received: from xmb-rcd-x13.cisco.com ([169.254.3.77]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Fri, 4 Jan 2013 00:54:10 -0600
From: "Saikat Ray (sairay)" <sairay@cisco.com>
To: Jeff Wheeler <jsw@inconcepts.biz>, Tony Li <tony.li@tony.li>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6iX+pP5muDGR70G7eUwvXv72hJg4d8fggAClngD//5vq0A==
Date: Fri, 4 Jan 2013 06:54:10 +0000
Message-ID: <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com>
In-Reply-To: <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.89.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 06:54:12 -0000

Bugs can be present at other places than an ASBR.  Imagine the following ve=
ry ordinary network:

AS100 --- [ ASBR2 --- AR3 --- ASBR4 --- ] AS500

ASBR2 will have iBGP routing exchange with ASBR4 by some means.  This may b=
e an ordinary iBGP session, via a route-reflector, or whatever.
If AR3 is buggy but it is in the forwarding path between ASBR2 and ASBR4, t=
hen ASBR4 potentially will send packets to AR3, yet AR3 has treat-as-withdr=
aw a route.  ASBR4 is not subject to the bug, receives and installs the iBG=
P-learnt route from ASBR2, and happily announces it to AS500.

[SR] Ok. This however does not happen in bgp-free core (ASBR2 will tunnel=20
          the packet to ASBR4 even if AR3 is in the forwarding path).


From tony.li@tony.li  Thu Jan  3 23:01:57 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C231021F86F5 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 23:01:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.21
X-Spam-Level: 
X-Spam-Status: No, score=-100.21 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 t0aEAMuGSi3b for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 23:01:56 -0800 (PST)
Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:212]) by ietfa.amsl.com (Postfix) with ESMTP id D4BBF21F846E for <grow@ietf.org>; Thu,  3 Jan 2013 23:01:56 -0800 (PST)
Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta14.emeryville.ca.mail.comcast.net with comcast id jj1w1k0011eYJf8AEj1wiS; Fri, 04 Jan 2013 07:01:56 +0000
Received: from [192.168.2.103] ([98.248.36.188]) by omta19.emeryville.ca.mail.comcast.net with comcast id jj1t1k00J43ZcXW01j1uuW; Fri, 04 Jan 2013 07:01:56 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
Date: Thu, 3 Jan 2013 23:01:53 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <987CD2AD-61DA-46A3-83F3-F12483B4DD37@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj =kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
To: "Saikat Ray (sairay)" <sairay@cisco.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357282916; bh=xn2Gfa3YHMHE8bE8C8dM2gKO9jP6LE6yVcynsb5ASF0=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=gBy4isZx7F9av89vh8KRDvlWQ9aqZtn2ck2LcD2hTYDEjwIP3ZwLKNN2HWtX1En0m ST4BPFgG0a0e3JEPSjRbW0WumgWI5U0RdAJsjM42lggzQFuVEfSHtZ3nxdqKg2iaMa 8w0CKqrS1OXiJqlO13qxJ3D7Jvy2lamDHCyJ56U5w6vo7RfW3ubpKCdzs0K61hyJtR buLwBVFrt4i3jZhsoRMTBKiYPYfbYJV4M1goOEfR5UKiQKFI40g+wSfK/RvuRfMSAa rfAXGO0zuG7/FCXRHXkPu0YEX3I6TnePN1yMksCBsLIJXwgG6ZtDJWZj71gdGx7Jcq WyQcmTFwLSH8w==
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 07:01:57 -0000

> Bugs can be present at other places than an ASBR.  Imagine the =
following very ordinary network:
>=20
> AS100 --- [ ASBR2 --- AR3 --- ASBR4 --- ] AS500
>=20
> ASBR2 will have iBGP routing exchange with ASBR4 by some means.  This =
may be an ordinary iBGP session, via a route-reflector, or whatever.
> If AR3 is buggy but it is in the forwarding path between ASBR2 and =
ASBR4, then ASBR4 potentially will send packets to AR3, yet AR3 has =
treat-as-withdraw a route.  ASBR4 is not subject to the bug, receives =
and installs the iBGP-learnt route from ASBR2, and happily announces it =
to AS500.
>=20
> [SR] Ok. This however does not happen in bgp-free core (ASBR2 will =
tunnel=20
>          the packet to ASBR4 even if AR3 is in the forwarding path).


And we should also note that this can happen with ANY error recovery =
mechanism.  Anytime AR3 and ASBR4 receive different information or =
process it differently, you'll have a problem.  Also true with simple =
session reset: if AR3 detects an error and shuts down its iBGP =
connection, then ASBR4 won't know it and you've got a blackhole.

Bottom line: this situation already occurs with session reset, will =
occur with treat-as-withdraw, and will occur with ignore-bad-messages.

So, what was the point of this argument again?

Tony


From tony.li@tony.li  Thu Jan  3 23:15:49 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3759421F8EA1 for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 23:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.21
X-Spam-Level: 
X-Spam-Status: No, score=-100.21 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 GTISFiazc5QS for <grow@ietfa.amsl.com>; Thu,  3 Jan 2013 23:15:48 -0800 (PST)
Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:243]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA6721F8E9D for <grow@ietf.org>; Thu,  3 Jan 2013 23:15:48 -0800 (PST)
Received: from omta16.emeryville.ca.mail.comcast.net ([76.96.30.72]) by qmta13.emeryville.ca.mail.comcast.net with comcast id jj7J1k0011ZMdJ4ADjFoUH; Fri, 04 Jan 2013 07:15:48 +0000
Received: from [192.168.2.103] ([98.248.36.188]) by omta16.emeryville.ca.mail.comcast.net with comcast id jjFm1k00N43ZcXW8cjFm01; Fri, 04 Jan 2013 07:15:47 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com>
Date: Thu, 3 Jan 2013 23:15:45 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AECA3F87-A663-42D9-9AD2-2B2CFA8C5FE5@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj =kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357283748; bh=GyFUidsC0zpR7vC298nPOmXXWx8G+9zXvmb7aMmBUxM=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=s05QWS4HSX7zJDeJg32Q6krnaWFCf3NjgySSzyHXWK24lEg4g0map6nqzpoRJeogr MABQsiVjfKDwj1RcLG3vz0jRpVtnUxQpBDXMQYnvj5Gbom5pmW+wtJsF8vuCscDbPm 0fDujEJD5ZgCe7HDvXLKvecNgCucM+/32WM/KlDk1juXm+dKsfgp1Hf9gwLVUubcS3 KcID2LIm+w3AH5FYtqevpm99N76qZHwZ2RINCdV8aCSlG/93FSObMsvMO28EO7zSdg TaSQBT7HhDIMJCKK25q5usR1QbD1cr/wW5H9MhmxJL0y2AaWfNDUQbW4hkwtSMEI4i 6R87QGaFj0lyA==
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "Saikat Ray \(sairay\)" <sairay@cisco.com>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 07:15:49 -0000

Jeff,


>>> No, ignore-bad-message is not harder to implement.  To say so is =
simply a lie.
>>=20
>> I'm sorry, but this conversation has taken a turn for the worse.   I =
may be wrong (I really don't think so), but I am not lying.
>>=20
>> You owe me an apology and I'm not going to continue this conversation =
until you do.
>=20
> If calling your statement a lie has offended you, I apologize. =20


Thank you.


> It is,
> however, absolutely wrong; and you've framed it as absolutely right.


You're welcome to disagree.  It remains my opinion about the coding =
complexity.  I think my experience with BGP coding speaks for itself.  =
What's yours again?


> To review, you've said that ignoring a BGP message is not even
> possible.  Of course we know that isn't true. =20


Do we?  Given an arbitrary set of errors on a byte stream where there =
are no guaranteed delimiters, how do you propose to resynchronize with =
absolute certainty.  My position is that it is risky as it requires =
certain inferences.


> You've also said it is
> harder to ignore a message than to treat-as-withdraw.  This is not
> true either.


So you can tell us what's true and what's not?

I'm dying to know about O.J., L.H. Oswald, and Marilyn.  Do tell.  ;-)


Yes, in my professional opinion, trying to recover from the semantic =
errors is pretty straightforward.  Recovering from the syntactic errors =
is not going to work and will end up as a reset.  Guessing about the =
message delimiters is going to be messy and hard.


>  To do treat-as-withdraw you have to, at minimum, extract
> NLRI from a known to be damaged message.  The current error-handling
> draft then requires you to apply numerous rules.  Only then may you
> decide if you treat-as-withdraw or terminate the BGP session.  Your
> assertions cannot possibly be correct in any implementation, period.


Again, I was speaking to a practical implementation, not necessarily =
what the draft is currently specifying.  The reality is simple: extract =
the NLRI.  If you can do so cleanly, then treat them all as withdrawn =
and syslog loudly.  If you can't extract the NLRI cleanly, then it's =
reset time.


> The fact is you don't want to ignore messages.  I am much more
> persuaded by your argument that ignoring messages may result in the
> persistence of bad RIB entries which may be re-forwarded within or
> outside the AS.  That is a good argument.  It's not constructive,
> however, to cloud the issue by making absurd statements like "ignoring
> a message is impossible."  It is possible, you just feel strongly that
> it is the wrong approach.


It is impossible to do so in the general case with 100% certainty.  You =
have lost context on the data stream.  You can no longer distinguish =
between data and TLV overhead.  There is (unfortunately) no redundancy =
that you can use to determine that any hypothetical recovery is correct. =
 That makes it a poor error recovery approach.

Now, if we had thought to have put a CRC-16 at the end of each message, =
we'd be in much better shape.  Sigh.

Tony



From heas@shrubbery.net  Thu Jan  3 23:59:43 2013
Return-Path: <heas@shrubbery.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE03E21F8E92; Thu,  3 Jan 2013 23:59:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.372
X-Spam-Level: 
X-Spam-Status: No, score=-6.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 mL6-x+xaN79v; Thu,  3 Jan 2013 23:59:43 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C64C21F86A5; Thu,  3 Jan 2013 23:59:43 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 2EF799A022; Fri,  4 Jan 2013 07:59:44 +0000 (UTC)
Date: Fri, 4 Jan 2013 07:59:44 +0000
From: heasley <heas@shrubbery.net>
To: Tony Li <tony.li@tony.li>
Message-ID: <20130104075944.GS86753@shrubbery.net>
References: <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 07:59:44 -0000

Thu, Jan 03, 2013 at 02:31:16PM -0800, Tony Li:
> As I've said before, errors can be reasonably classified into two groups: syntactic and semantic.  
> 
> A syntactic error would be any inconsistency of length fields, incompatibility between a type and a length, or any other error that would introduce any doubt about the parsing of the message.  Once this type of error has occurred, then the remainder of the data stream is wholly in doubt.  A session reset seems like the only (conservative) way of handling this, as it's unclear that further data would be accurate.

Amen.  if you've come upon a syntactic error and therefore have zero
confidence that any bit in the message is correct, I dont understand how you
could have any confidence that treat-as-withdraw is treating the right
prefix(es) as withdrawn, or even logging the right prefix(es).  you cant
even have confidence about the length of the message.

The aforementioned sesson re-establishment suppression seems a far better
and consistent approach; it also doesnt seem to be the subject for an rfc.

From jsw@inconcepts.biz  Fri Jan  4 00:29:56 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EEDF21F8E0C for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 00:29:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 zx0qejM1aafz for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 00:29:55 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0E45521F8E0B for <grow@ietf.org>; Fri,  4 Jan 2013 00:29:54 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id k10so19474851iea.1 for <grow@ietf.org>; Fri, 04 Jan 2013 00:29:54 -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 :content-transfer-encoding:x-gm-message-state; bh=qGzGxfTTd+eZhuKZGgoiPfmS/Oayb1pH2OVc4alQ0aA=; b=E5nAJHqrSzI9h0g+OAe/adY3+8iTfW4FNIHJhbUXFB2h6H4UlJajmwRdMP4QiVq9+a ji8De6Z7teiDYGI1Seg/2Wsahs7d1Maj7gRDx0mYT8ZzwKZmDBT7ip9lZlHtCsSPQX0C EccClQv+Nrtw5DqC4lKPsjciFpJsmjiiOQyfADaCBsIQFQH79SgSDf4UNetopHg5Vcf1 FpzdmmVO0j7C2GFLYpjj8H/ACVNQfGcznfxeavfGgzztiJoDV7ys66bdQ1KpglPbBVV7 xaL/mL8gNP6DnbHnneNT/he+LaeGrML/QFbj5oQNkqp5OmNhUd2rMteOPcWwrwNUQh2q h3+Q==
MIME-Version: 1.0
Received: by 10.50.88.136 with SMTP id bg8mr40143175igb.96.1357288194435; Fri, 04 Jan 2013 00:29:54 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Fri, 4 Jan 2013 00:29:54 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
Date: Fri, 4 Jan 2013 03:29:54 -0500
Message-ID: <CAPWAtbKDDrNqgYaH+z1K0raqTy0nubaauakObt0qoBr2PSemig@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: "Saikat Ray (sairay)" <sairay@cisco.com>, Tony Li <tony.li@tony.li>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQke/ty5zW2TR7U8NyJJBdNo1CIlmZWNzhPlHCVaSonddRm4pPgGIOvbpRopCTDwE/+Lf0aM
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 08:29:56 -0000

On Fri, Jan 4, 2013 at 1:54 AM, Saikat Ray (sairay) <sairay@cisco.com> wrot=
e:
> [SR] Ok. This however does not happen in bgp-free core (ASBR2 will tunnel
>           the packet to ASBR4 even if AR3 is in the forwarding path).

Yes, absolutely true.

On Fri, Jan 4, 2013 at 2:01 AM, Tony Li <tony.li@tony.li> wrote:
> And we should also note that this can happen with ANY error recovery mech=
anism.  Anytime AR3 and ASBR4 receive different information or process it d=
ifferently, you'll have a problem.  Also true with simple session reset: if=
 AR3 detects an error and shuts down its iBGP connection, then ASBR4 won't =
know it and you've got a blackhole.
>
> Bottom line: this situation already occurs with session reset, will occur=
 with treat-as-withdraw, and will occur with ignore-bad-messages.
>
> So, what was the point of this argument again?

The point is that treat-as-withdraw is relatively complicated and does
not solve all the problems that many list participants might expect it
to.

Ignore-bad-message is less complicated.  It has similar problems to
treat-as-withdraw but the implementation cost, and bug risk, is lower.

Because several posters have expressed concern about the complexity of
additional code required to implement treat-as-withdraw, and because
some aspects of it truly haven't been thought through yet, it is
useful to compare treat-as-withdraw to something simple, even if it
may seem stupid at first.

On Fri, Jan 4, 2013 at 2:15 AM, Tony Li <tony.li@tony.li> wrote:
> You're welcome to disagree.  It remains my opinion about the coding compl=
exity.  I think my experience with BGP coding speaks for itself.  What's yo=
urs again?

For 13 years I've maintained a reference implementation of BGP for the
purpose of troubleshooting vendor implementations.

I'm posting, however, to speak from the operator perspective.  There
are plenty of programmers participating in the IETF process, and not
enough operators.

>> To review, you've said that ignoring a BGP message is not even
>> possible.  Of course we know that isn't true.
>
> Do we?  Given an arbitrary set of errors on a byte stream where there are=
 no guaranteed delimiters, how do you propose to resynchronize with absolut=
e certainty.  My position is that it is risky as it requires certain infere=
nces.

If you read back a few posts, you'll note that I suggest it is
possible (without certainty, though) to re-synchronize using the
MARKER.

I'm not saying you must do that.  To ignore a Message you can just
ignore all of its contents.  If the Message Length is correct, then
you do not need to re-synchronize, because the Message framing won't
have been lost.  I also suggested this in the same post.

You've tied a need to re-sync the Message stream, to the simple
ability to ignore Messages.  You don't have to do both.  If your
argument is that re-sync is too hard to be worthwhile, I'll buy into
your opinion; but you should still consider the simple case if
ignoring Messages with no re-sync feature.

All you need to do to just ignore Messages is ignore the content of a
malformed message and move on.  Either the Message Length will be
correct and the following Message will begin with a MARKER, or it
won't.  What this buys you is much of what treat-as-withdraw intends
to fix with almost no implementation cost.

>> You've also said it is
>> harder to ignore a message than to treat-as-withdraw.  This is not
>> true either.
>
> So you can tell us what's true and what's not?
>
> I'm dying to know about O.J., L.H. Oswald, and Marilyn.  Do tell.  ;-)

I've written several times how to ignore messages easily.  You already
know how though, you just think it's a bad idea.  This is a reasonable
place to disagree.

I'll save my opinion about JFK for another time.

> Now, if we had thought to have put a CRC-16 at the end of each message, w=
e'd be in much better shape.  Sigh.

Indeed.

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

From rjs@rob.sh  Fri Jan  4 00:52:31 2013
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB4621F8E91; Fri,  4 Jan 2013 00:52:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_35=0.6, SARE_SUB_OBFU_Q1=0.227]
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 3n4mn8bVbTT3; Fri,  4 Jan 2013 00:52:31 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id D9C0E21F8E51; Fri,  4 Jan 2013 00:52:25 -0800 (PST)
Received: from [46.65.174.227] (helo=latte.munster) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1Tr2xf-0006Lw-MT; Fri, 04 Jan 2013 08:49:07 +0000
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net>
Date: Fri, 4 Jan 2013 08:52:20 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A571FEC-A4B9-49BF-B55B-C617B302F388@rob.sh>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net>
To: Jared Mauch <jared@puck.nether.net>
X-Mailer: Apple Mail (2.1283)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 08:52:31 -0000

On 3 Jan 2013, at 22:05, Jared Mauch wrote:

> Oh, I understand all these use-cases, but there is a case for a =
well-designed network not always sharing/mixing the NLRI.  eg: We don't =
transport v4 NLRI in v6 transport, nor v6 NLRI in v4 transport.  If you =
have a single session with massive shared fate, perhaps it's not a =
protocol design error but a network design error.

I would highlight that public Internet networks are NOT the only =
implementation of BGP. Yes, in the Internet you can divide the two =
topologies that you have (the v4 DFZ and the v6 DFZ) into separate =
sessions to separate fate. However, a (I will assert, significant) =
number of operators run networks which run one address family that has =
numerous entirely separate topologies within it (e.g., L3VPN). There are =
no mechanisms that provide separation between such routing topologies =
within that AFI, SAFI, and it is not practical or scalable to divide =
these into individual sessions per-topology.

One of the taxes that we have with MP-BGP is that there are multiple =
applications which may not all have exactly the same deployment =
characteristics, or sensitivities. IMHO, we need to make sure we are =
considering all applications of BGP when considering this subject (this =
is one of the points that the draft that this thread relates to tries to =
cover). Having said that, where there are means where failure domains =
can be limited e.g. multi-session and/or separating AFI,SAFIs onto =
different transport sessions, of course, these form part of the =
solution.

Cheers,
r.



From rraszuk@gmail.com  Fri Jan  4 02:45:30 2013
Return-Path: <rraszuk@gmail.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE36C21F8ED9; Fri,  4 Jan 2013 02:45:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.217
X-Spam-Level: 
X-Spam-Status: No, score=-2.217 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 ug7FUbzHLLdw; Fri,  4 Jan 2013 02:45:26 -0800 (PST)
Received: from mail-ia0-f181.google.com (mail-ia0-f181.google.com [209.85.210.181]) by ietfa.amsl.com (Postfix) with ESMTP id 9665221F8ED7; Fri,  4 Jan 2013 02:45:26 -0800 (PST)
Received: by mail-ia0-f181.google.com with SMTP id s32so13704020iak.12 for <multiple recipients>; Fri, 04 Jan 2013 02:45:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=oUT0g0yEznUWNk5P9tQ/zlpBlfvg0RCkOhqE3pv58B4=; b=G4sl5S4QUG1Hhvy+JmQdpsTnfJUawBTpQsOX3pH0tnh0Y3Wrj3bU+1sHRpjSA6v4OL sTsxFvLnXMHLidmKVok1qWsXMOcy/3GSUgyVwYIXeLYfY4k7lnwT3A6cTfEduFYXAHSA sXnm+l16tI59PRXKApfMA62OaICSdsMfqXe1L9c3E65xzpAuRfSbBMf3XFd79xS0SEsH VBhCe3URlKPVLd9rYhHS6IO4YxDW9MeWh8PSVgy4Ewmue+a5dGatwygWG6p/cgcouLuo +BcPeXB0keksQAFclQW2hdHxDeMZmYNANe9o4EyKP0mGgfq9PKiSaJXgmvX3PV71gM1M DZNA==
MIME-Version: 1.0
Received: by 10.50.94.134 with SMTP id dc6mr39482648igb.80.1357296326213; Fri, 04 Jan 2013 02:45:26 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.167.204 with HTTP; Fri, 4 Jan 2013 02:45:25 -0800 (PST)
In-Reply-To: <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com>
Date: Fri, 4 Jan 2013 11:45:25 +0100
X-Google-Sender-Auth: 9uDSzeghrbMYBya_jiPoPUQaQ-k
Message-ID: <CA+b+ER=yTt_Ndq-BpCvhAyB9LNjX6riCm01_b80CZ_CKOJm4KA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "Saikat Ray (sairay)" <sairay@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 10:45:31 -0000

Saikat,

> [SR] Ok. This however does not happen in bgp-free core (ASBR2 will tunnel
>           the packet to ASBR4 even if AR3 is in the forwarding path).

True but http://tools.ietf.org/html/draft-ietf-idr-error-handling-03
does not mandate nor recommend to use "treat-as-withdraw" in IBGP in
tunneled only networks. Once you upgrade your router to new release it
careless if there is MPLS or GRE running in your domain.

In fact it says quite clearly:

   Although the "treat-as-withdraw" error-handling behavior defined in
   Section 2 makes every effort to preserve BGP's correctness, we note
   that if an UPDATE received on an IBGP session is subjected to this
   treatment, inconsistent routing within the affected Autonomous System
   may result.  The consequences of inconsistent routing can include
   long-lived forwarding loops and black holes.

Rgs,
R.

From jared@puck.nether.net  Fri Jan  4 05:51:40 2013
Return-Path: <jared@puck.nether.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B2F21F8930; Fri,  4 Jan 2013 05:51:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level: 
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 RTfqoipC01Mo; Fri,  4 Jan 2013 05:51:39 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) by ietfa.amsl.com (Postfix) with ESMTP id AD1D621F892F; Fri,  4 Jan 2013 05:51:39 -0800 (PST)
Received: from [10.0.0.137] (173-167-0-106-michigan.hfc.comcastbusiness.net [173.167.0.106]) (authenticated bits=0) by puck.nether.net (8.14.4/8.14.4) with ESMTP id r04DpaQ0026656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 4 Jan 2013 08:51:37 -0500
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com>
Date: Fri, 4 Jan 2013 08:51:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA095918-03DF-41DD-B374-D82FF4D38E31@puck.nether.net>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZ! j=kdJKVYww@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (puck.nether.net [204.42.254.5]); Fri, 04 Jan 2013 08:51:38 -0500 (EST)
Cc: idr@ietf.org, grow@ietf.org
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 13:51:40 -0000

On Jan 3, 2013, at 9:33 PM, Jeff Wheeler wrote:

>> Non-sequitur.  Cyclic resets are orthogonal to treat-as-withdraw.  As =
enumerated above, ignore-bad-message is harder to implement and is more =
dangerous.
>=20
> No, ignore-bad-message is not harder to implement.  To say so is =
simply a lie.

Jeff,

The challenge I see here is that the NLRI is always at the END of the =
message.  The parsing problem is going to happen before the NLRI.  I =
certainly don't want my BGP implementation doing 'fuzzy' things with the =
message and producing further poor results.  It's no way to run a =
network, and can be difficult to code.

Once again I must assert that this is a problem best left to be fixed in =
the individual implementations.  We can certainly expect a high level of =
standard for software, but expecting no defects is unrealistic.

- Jared=

From tony.li@tony.li  Fri Jan  4 09:43:03 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0573821F8855 for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 09:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.473
X-Spam-Level: 
X-Spam-Status: No, score=-97.473 tagged_above=-999 required=5 tests=[AWL=-2.263, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, GB_SUMOF=5, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 M5-ypm-CdQ7h for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 09:43:02 -0800 (PST)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id 42A1921F885C for <grow@ietf.org>; Fri,  4 Jan 2013 09:43:02 -0800 (PST)
Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta01.emeryville.ca.mail.comcast.net with comcast id jpQb1k0051bwxycA1tj2nk; Fri, 04 Jan 2013 17:43:02 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta18.emeryville.ca.mail.comcast.net with comcast id jtgl1k00o52qHCY8etgoQA; Fri, 04 Jan 2013 17:40:59 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <CAPWAtbKDDrNqgYaH+z1K0raqTy0nubaauakObt0qoBr2PSemig@mail.gmail.com>
Date: Fri, 4 Jan 2013 09:02:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <23798B91-D652-4A61-9BF2-83F617C78F84@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj =kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com> <CAPWAtbKDDrNqgYaH+z1K0raqTy0nubaauakObt0qoBr2PSemig@mail.gmail.com>
To: Jeff Wheeler <jsw@inconcepts.biz>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357321382; bh=B/y1XL36d6gmyIg3fDnXVUMw3VnqUkfk0gjJk3Ce+ME=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=ltlLc8aQbywcsO6zZC675KBuYavPFcGjRU8qcnL75QHpNee9KbpPRCoRZrrDDDBg/ dWWOQHjxQ9kQfDqcyDwjGxI21bnFy7O77EqD8ro6Pna9Ke3b9N3Nr7Cr888wkFT1Sl hGrjaDJ+GOdgoJdAIin3pkArrdZGoriBfwF4S0ClHJ8Ze6KNxMSgcqJKBKYhQEdhIX t5WiyQVh3EsyX2QMAXACdbzEtti7+MYzJ1ia2UXUc1Cb3JKUcYOZ4lEFaigoHlUAMe ApXFKk4vKVkzWqNe7FEESKI1HiHqJYoXLHaqa9RW8yMiYvxvskcGBf9vzJQIfq9PT5 Ryo/fnFM2WMOQ==
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "Saikat Ray \(sairay\)" <sairay@cisco.com>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 17:43:03 -0000

Jeff,


>>> To review, you've said that ignoring a BGP message is not even
>>> possible.  Of course we know that isn't true.
>>=20
>> Do we?  Given an arbitrary set of errors on a byte stream where there =
are no guaranteed delimiters, how do you propose to resynchronize with =
absolute certainty.  My position is that it is risky as it requires =
certain inferences.
>=20
> If you read back a few posts, you'll note that I suggest it is
> possible (without certainty, though) to re-synchronize using the
> MARKER.
>=20
> I'm not saying you must do that.  To ignore a Message you can just
> ignore all of its contents.  If the Message Length is correct, then
> you do not need to re-synchronize, because the Message framing won't
> have been lost.  I also suggested this in the same post.


True, but again, we're trying to deal with error handling.  When the =
interesting syntactic errors occur, then the Message Length is very much =
in doubt.  A typical syntactic error is an off-by-one inconsistency =
between the Message Length and the sum of all of the lengths of the TLVs =
(and overhead).  There is no good reason to believe the Message Length =
or the lengths of the TLVs is correct, so our code should probably check =
both.  Then check to see if the Marker (no need to shout ;-) is in the =
right place.

That's reasonable for off-by-one, but that's not the only possible =
mistake.  It's easy to have an inconsistency which is in the tens or =
hundreds of bytes.  Now what?  We could again check both alternatives, =
but again, the presence of a Marker, even in one of the possible =
locations, is no guarantee.  You could easily skip over an entire =
message, for example, and end up ignoring two updates, not just one.


> You've tied a need to re-sync the Message stream, to the simple
> ability to ignore Messages.  You don't have to do both.  If your
> argument is that re-sync is too hard to be worthwhile, I'll buy into
> your opinion; but you should still consider the simple case if
> ignoring Messages with no re-sync feature.


As I've argued above, yes, I'd say that the re-sync risk vs. effort vs. =
return tradeoff isn't worthwhile.

I'm not sure why we would discuss a different error recovery mechanism =
that doesn't deal with the syntactic errors.  Again, if there are no =
syntactic errors, then recovery by ignoring the message leaves the =
network in an inconsistent state, as you've stipulated.  Clearly, =
treat-as-withdraw is preferable for this case.  The remaining question =
is how to deal with the syntactic errors.  I've argued that we shouldn't =
mess around and should just accept the session reset.


> All you need to do to just ignore Messages is ignore the content of a
> malformed message and move on.  Either the Message Length will be
> correct and the following Message will begin with a MARKER, or it
> won't.  What this buys you is much of what treat-as-withdraw intends
> to fix with almost no implementation cost.


I agree that the Message Length will either be correct or it won't.  =
Now, all us need is an oracle (the computer science kind ;-), to tell us =
which is which.  Got any handy?  ;-)

Regards,
Tony



From Donald.Smith@CenturyLink.com  Fri Jan  4 09:54:30 2013
Return-Path: <Donald.Smith@CenturyLink.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32A4D21F889D; Fri,  4 Jan 2013 09:54:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.722
X-Spam-Level: 
X-Spam-Status: No, score=-1.722 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 hJF9pELBQTBT; Fri,  4 Jan 2013 09:54:29 -0800 (PST)
Received: from suomp64i.qwest.com (suomp64i.qwest.com [155.70.16.237]) by ietfa.amsl.com (Postfix) with ESMTP id 5076E21F858A; Fri,  4 Jan 2013 09:54:29 -0800 (PST)
Received: from lxomavmpc030.qintra.com (lxomavmpc030.qintra.com [151.117.207.30]) by suomp64i.qwest.com (8.14.4/8.14.4) with ESMTP id r04HsRER005195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jan 2013 11:54:28 -0600 (CST)
Received: from lxomavmpc030.qintra.com (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id A7DFF1E0053; Fri,  4 Jan 2013 11:54:22 -0600 (CST)
Received: from suomp61i.qintra.com (unknown [10.6.10.61]) by lxomavmpc030.qintra.com (Postfix) with ESMTP id 8764C1E0073; Fri,  4 Jan 2013 11:54:22 -0600 (CST)
Received: from suomp61i.qintra.com (localhost [127.0.0.1]) by suomp61i.qintra.com (8.14.4/8.14.4) with ESMTP id r04HsMFs010921; Fri, 4 Jan 2013 11:54:22 -0600 (CST)
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.qintra.com [151.119.128.29]) by suomp61i.qintra.com (8.14.4/8.14.4) with ESMTP id r04HsLXh010900 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Jan 2013 11:54:21 -0600 (CST)
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([2002:9777:801d::9777:801d]) with mapi id 14.02.0318.001; Fri, 4 Jan 2013 10:54:20 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "'Tony Li'" <tony.li@tony.li>
Thread-Topic: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6ghxXiZLU84V50OUaJbShrXQr5g5aGnw
Date: Fri, 4 Jan 2013 17:54:20 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D0A29F4B1@PDDCWMBXEX503.ctl.intranet>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet> <B697CA52-4D41-4E27-AE65-E579CE7198A6@tony.li>
In-Reply-To: <B697CA52-4D41-4E27-AE65-E579CE7198A6@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [151.119.128.7]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "'idr@ietf.org'" <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 17:54:30 -0000

"Pampers use multiple layers of protection to prevent leakage. Rommel used =
defense in depth to defend European fortresses." (A.White) Donald.Smith@Cen=
turyLink.com


>-----Original Message-----
>From: Tony Li [mailto:tony.li@tony.li]
>Sent: Thursday, January 03, 2013 4:15 PM
>To: Smith, Donald
>Cc: 'Jeff Wheeler'; 'idr@ietf.org'; 'grow@ietf.org'
>Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-
>error-handling-06.txt
>
>
>Hi Donald,
>
>>> A session reset seems like the only (conservative) way
>>> of handling this, as it's unclear that further data would be
>accurate.
>> I disagree. Does a session reset fix the issue? It hasn't the last few
>times I have seen this.
>> It exasperated it by causing peers to drop and having to rebuild
>ribs/fibs etc... continuously.
>
>
>Which is why I suggested that re-opening the connection is perhaps not
>optimal.
Agreed.

>
>
>> Other than getting it noticed I doubt a reset will ever make a
>misbehaving router stop misbehaving.
>
>
>The point is that once you've lost context in the data stream,
>subsequent messages cannot be accepted with a reasonable certainty of
>correct parsing.
>
>
Understood on over runs or under runs (length errors). I am not sure that i=
s true for ALL other issues.
Such as the recent issue where the attribute had non-zero bits in the lower=
 nibble.

>>> I'm very open to a discussion of alternatives to session flap for
>these
>>> cases.  Should we require manual intervention before session restart?
>> Manual intervention will be required in most cases but if we "require"
>manual intervention haven't we left the programming side (state machine)
>and gone into the operational control side of things?
>
>
>Correct.  The programming side has failed.  As you note, trying again is
>not likely to help.  Adding Artificial Intelligence to BGP to recover is
>unlikely to be effective or an efficient means of making progress.
>
>
>>> Semantic errors would be consistency violations within the contents
>of
>>> the message.  In these cases, treat-as-withdraw seems reasonable.
>> I would also like the ignore option here. You know your neighbor is
>saying something you don't understand, possibly due to a lack of in your
>vocabulary but you understand other elements so you nod and continue
>listening to the rest:)
>
>
>The entire problem with the ignore option is that it leaves bogus
>information in the network.  Suppose that the update contains an AS path
>change for a prefix.  If you ignore the update, then you ignore that
>path change, AND, you fail to propagate that change to your upstream
>neighbors.  Now, BGP's loop prevention mechanism is out the window and,
>in the worst case, you've created an inter-domain forwarding loop.
Agreed I now have bad data (incorrect or incomplete) from one peer but ever=
ything else is still working.
I haven't flapped the session. Now I have to talk to that peer (assuming th=
is is noticed via syslog or snmp or something). Or that peer calls us and s=
ays "why aren't you propagating this announcement" and we begin joint AS tr=
oubleshooting. That is probably the best solution:)

>
>If, on the other hand, you withdraw that prefix, then any alternate
>connectivity for that prefix can come into play.
That makes sense and in big ISPs there will nearly always be another path.


>
>In short, treat-as-withdraw is a fail safe approach.  Ignoring updates
>is not.
But in a peering world you have potentially just withdrawn all of your rout=
es to a peer from that peer.

You will now prefer some other peer for all of that peers traffic (or anoth=
er connection to that peer in another location).

If you can ignore a single update error from a peer while you troubleshoot =
the issue with that peer it would allow a better path for the rest of that =
peers announcements. Again anything with a overrun or under run issue sort =
of implies the rest of the updates from that point forward are corrupted/un=
trustworthy.
Can you detect overrun and under runs without FPs or FNs? Probably not in a=
ll cases.



>
>Tony


From tony.li@tony.li  Fri Jan  4 10:04:59 2013
Return-Path: <tony.li@tony.li>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A4F321F88A8 for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 10:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.839
X-Spam-Level: 
X-Spam-Status: No, score=-99.839 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 d2kH1Ou2f0T5 for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 10:04:58 -0800 (PST)
Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:64]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC4D21F88A1 for <grow@ietf.org>; Fri,  4 Jan 2013 10:04:58 -0800 (PST)
Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by qmta07.emeryville.ca.mail.comcast.net with comcast id jtN51k00717UAYkA7u4yvj; Fri, 04 Jan 2013 18:04:58 +0000
Received: from [10.155.35.198] ([128.107.239.233]) by omta13.emeryville.ca.mail.comcast.net with comcast id ju2j1k00R52qHCY8Zu2lNa; Fri, 04 Jan 2013 18:02:56 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Tony Li <tony.li@tony.li>
In-Reply-To: <68EFACB32CF4464298EA2779B058889D0A29F4B1@PDDCWMBXEX503.ctl.intranet>
Date: Fri, 4 Jan 2013 10:02:43 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <531D282B-9B6E-4D38-8D32-64011DF9854F@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <68EFACB32CF4464298EA2779B058889D0A29EF86@PDDCWMBXEX503.ctl.intranet> <B697CA52-4D41-4E27-AE65-E579CE7198A6@tony.li> <68EFACB32CF4464298EA2779B058889D0A29F4B1@ PDDCWMBXEX503.ctl.intranet>
To: "Smith, Donald" <Donald.Smith@CenturyLink.com>
X-Mailer: Apple Mail (2.1499)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1357322698; bh=vLb1hMiMym4ONB8M1x/DsZYxjafD2qzn4Lz/32Kg6qs=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To; b=KT9OEoREhFP9VIzfHKerLTZRaDx36OBPTfErN4JKJeGztQ7syRKp4aH5uBeztIxiT mpWSPxRmorhG1rMyh6ponN7BUNZdfG6+aTV3UO3owLUSxQFQY2wO7145+iywxyTjGa oQbDhAsLBItoessgi2KQcD+AvhP41JAeA33Tnfai7a4P95ACrnPUrE38aA84qvLHkx Eu3b7Ts7qb1mKop3491dH0WUMVJ7Oxtdcpfr2SRZDOvDLuxUsJI6cp/x9WstHmXZbn QzwRa5djwvHbV3uvoZ/eAYydp7McThKTd5DYy5sDqJLLQoJ1IAjCTvQTZumDL3/lxD /hGPMkOY7tfpg==
Cc: "'idr@ietf.org'" <idr@ietf.org>, "'grow@ietf.org'" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 18:04:59 -0000

On Jan 4, 2013, at 9:54 AM, "Smith, Donald" =
<Donald.Smith@CenturyLink.com> wrote:

>> In short, treat-as-withdraw is a fail safe approach.  Ignoring =
updates
>> is not.
> But in a peering world you have potentially just withdrawn all of your =
routes to a peer from that peer.
>=20
> You will now prefer some other peer for all of that peers traffic (or =
another connection to that peer in another location).
>=20
> If you can ignore a single update error from a peer while you =
troubleshoot the issue with that peer it would allow a better path for =
the rest of that peers announcements. Again anything with a overrun or =
under run issue sort of implies the rest of the updates from that point =
forward are corrupted/untrustworthy.
> Can you detect overrun and under runs without FPs or FNs? Probably not =
in all cases.
>=20


Donald,

As I would implement treat-as-withdraw, the scope of the withdrawal =
would ONLY be for the message in question, and again it would only apply =
to semantic errors where the NLRI could be cleanly extracted.  So only =
the prefixes in error would be affected, not necessarily everything from =
that peer. =20

Detecting overrun and under run is not too hard.  Again, the most common =
cases are when the Message Length and TLV lengths are inconsistent.  The =
presence of the marker for the next message and a sane length field for =
the next message are also helpful checks for detection.

Again, some kind of redundancy for framing would have been a better =
long-term design.  I'll note that if folks are sufficiently motivated, =
this COULD be retro-fit.  Add an attribute that is a CRC-16 of the =
entire message.

Tony




From jakob.heitz@ericsson.com  Fri Jan  4 10:27:58 2013
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5DBA21F8947; Fri,  4 Jan 2013 10:27:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.429
X-Spam-Level: 
X-Spam-Status: No, score=-6.429 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 SSawY5hQox9C; Fri,  4 Jan 2013 10:27:58 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAB021F8911; Fri,  4 Jan 2013 10:27:57 -0800 (PST)
Received: from EUSAAHC005.ericsson.se ([147.117.188.87]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r04Ifr5W025196; Fri, 4 Jan 2013 12:41:55 -0600
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0318.004; Fri, 4 Jan 2013 13:27:49 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Tony Li <tony.li@tony.li>, Jeff Wheeler <jsw@inconcepts.biz>
Thread-Topic: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6qMAIoORt/SJvkGUT2B4yn6gmZg5etwQ
Date: Fri, 4 Jan 2013 18:27:49 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E14DB1E@eusaamb109.ericsson.se>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj	=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com> <CAPWAtbKDDrNqgYaH+z1K0raqTy0nubaauakObt0qoBr2PSemig@mail.gmail.com> <23798B91-D652-4A61-9BF2-83F617C78F84@tony.li>
In-Reply-To: <23798B91-D652-4A61-9BF2-83F617C78F84@tony.li>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, "Saikat Ray \(sairay\)" <sairay@cisco.com>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 18:27:59 -0000

On , Tony Li <> wrote:

> possible mistake.  It's easy to have an inconsistency which
> is in the tens or hundreds of bytes.  Now what?  We could
> again check both alternatives, but again, the presence of a
> Marker, even in one of the possible locations, is no
> guarantee.  You could easily skip over an entire message, for
> example, and end up ignoring two updates, not just one.

Or waiting for a very long time for that marker to arrive.
Suppose the length is 40. You think it's 4000. You will sit
there patiently for an eternity waiting for more bytes to
arrive so you can read your next marker.

I support
http://tools.ietf.org/html/draft-ietf-idr-error-handling-03

with the understanding that it's the best we can do
in a tricky situation to limit the damage. Damage will
occur, but this limits it as best we can.

--=20
Jakob Heitz.

From jsw@inconcepts.biz  Fri Jan  4 11:51:01 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557D221F88B4 for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 11:51:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.716
X-Spam-Level: 
X-Spam-Status: No, score=-2.716 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 k-anpM3eQ72s for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 11:50:55 -0800 (PST)
Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id A4EA321F8799 for <grow@ietf.org>; Fri,  4 Jan 2013 11:50:51 -0800 (PST)
Received: by mail-ia0-f182.google.com with SMTP id x2so14026855iad.41 for <grow@ietf.org>; Fri, 04 Jan 2013 11:50:51 -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 :content-transfer-encoding:x-gm-message-state; bh=OGefrLs2FtRMdAIny96SQs1tDn2eKQzf7uCK8qT/rAk=; b=JwCuqo0Z2PkCv4V61RNEjXVBP0XXVw/o5nXDTWtdoUuiH0QW2j5/XLP3DptVKgGY2h ISuRW3rjAjIJLDkKSSFcE6Hr1/dPspxscmhefNPN80mwr7H5AVQKQc45Bqp1PzEtYDEP HUduEfNvwgLq2YwoRJtPmoNYc6VJKabwsdkSEmUO6l6d+z4iBV25TbbAoOWzq9L8VPSF GvyJceJI39bslJ4izQll4BBqxaTj6SoFILzyu+ESGdCS3wK9IJG282ySefI3nA5d+i7w J4cTfVzXpMxmyFs6ViOYxsf0HSH5YmllL9O+wpZT9t66Yjweb9hFyxihYMpPjBjhDljz kmYg==
MIME-Version: 1.0
Received: by 10.42.180.65 with SMTP id bt1mr40253887icb.41.1357329050662; Fri, 04 Jan 2013 11:50:50 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Fri, 4 Jan 2013 11:50:50 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <23798B91-D652-4A61-9BF2-83F617C78F84@tony.li>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <CAPWAtbLt=Lx_EcM-zEuvYRcxM1NGBJjNjVNhBp+0o1iuqJ1wVg@mail.gmail.com> <CA+b+ERkRoezeNjz499=xS+5Kb97A_RB9A_Q+U1FeUTGtcpu7jQ@mail.gmail.com> <CAPWAtbL4uoOmcEk-bZ7VyRSsd=+5qWLWq9K5jNC9WhqQ6kJW5Q@mail.gmail.com> <72CF9D03-9A2A-46D6-B65B-10849204879C@puck.nether.net> <CAPWAtb++eLdDHDrDbeUqLpbz91JSWFdhDfJO4uEkgRFXR9naoQ@mail.gmail.com> <54358BA2-AEE3-4AE5-9F5F-917CC0A17D70@puck.nether.net> <CAPWAtbLvJnY4TQS604+pMvsHQETJZFhXSz5Thg774uf3Rmjqug@mail.gmail.com> <92C046A2-560E-47EA-AED5-B04EB333CF84@tony.li> <CAPWAtb+9yVeiRoS5PPmCi38OMuMru+61xywv2eVqD_NqxwQUeQ@mail.gmail.com> <FC6F4BCE-A7B9-48ED-B5D5-6C1D4E01DFDE@tony.li> <CAPWAtbL9Xpbj0K-Nmr=OnSKzQsGCUoWwa22LEjhZj=kdJKVYww@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109800@xmb-rcd-x13.cisco.com> <CAPWAtb+3bU4a7kNYTD0ifPOPtaZN9pMhaoQTPar0u6Hm5xL7rg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A10983B@xmb-rcd-x13.cisco.com> <CAPWAtbJ_mKu+iGUtwJgSdL=KvEqNMyt42zssHuRbLprWe=TEUg@mail.gmail.com> <8ED5B0B0F5B4854A912480C1521F973A109942@xmb-rcd-x13.cisco.com> <CAPWAtbKDDrNqgYaH+z1K0raqTy0nubaauakObt0qoBr2PSemig@mail.gmail.com> <23798B91-D652-4A61-9BF2-83F617C78F84@tony.li>
Date: Fri, 4 Jan 2013 14:50:50 -0500
Message-ID: <CAPWAtbJD42qBsThs09rvD2E1=XVYQGfzd6Br8AWJ14kCfSOrTA@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: Tony Li <tony.li@tony.li>, Jakob Heitz <jakob.heitz@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlS9amrnCoySoCW3Z7RE114MNMV9WLqx3LdRNm7mfrTIuew3Tt+GKMfogm4dlxi4UM6jCM0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 19:51:01 -0000

Almost no one has commented on whether or not a capability code should
be used to re-order the contents of BGP Messages, and Attributes, as
suggested by error-handling.

This is really important if error-handling is to rely on such
re-ordering.  Many folks are saying error-handling needs it, the draft
says it, yet no mechanism is proposed to do it?  The closest thing is
a recommendation in RFC4760bis but it is the opposite of what RFC4271
recommends.  You can't actually know if your neighbor plans to follow
this new recommendation because there's no way to signal that intent.

In short, I suggest RFC4760bis should add a second capability that
indicates the BGP speaker promises to send the MP attributes before
all other attributes, as it recommends.

I further suggest any re-ordering of native NLRI information in the
Message needs to be addressed .. somewhere.

On Fri, Jan 4, 2013 at 12:02 PM, Tony Li <tony.li@tony.li> wrote:
> That's reasonable for off-by-one, but that's not the only possible mistak=
e.  It's easy to have an inconsistency which is in the tens or hundreds of =
bytes.  Now what?  We could again check both alternatives, but again, the p=
resence of a Marker, even in one of the possible locations, is no guarantee=
.  You could easily skip over an entire message, for example, and end up ig=
noring two updates, not just one.

I'm glad you raise this possibility.  Indeed, if you tried to re-sync
the message stream by searching for a MARKER, you might skip many
messages without realizing it.  The potential damage to the RIB is
high, so it is a high price to pay to avoid session-reset.

> I agree that the Message Length will either be correct or it won't.  Now,=
 all us need is an oracle (the computer science kind ;-), to tell us which =
is which.  Got any handy?  ;-)

As you know, when more data arrives from the neighbor, you can make a
good guess based on the marker.  I don't think divine intervention is
necessary.

On Fri, Jan 4, 2013 at 1:27 PM, Jakob Heitz <jakob.heitz@ericsson.com> wrot=
e:
> Or waiting for a very long time for that marker to arrive.
> Suppose the length is 40. You think it's 4000. You will sit
> there patiently for an eternity waiting for more bytes to
> arrive so you can read your next marker.

Sure, but this is not different than many other cases where the
neighbor fails and you sit there waiting for HoldTime to expire.

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

From chris.hall@highwayman.com  Fri Jan  4 15:44:18 2013
Return-Path: <chris.hall@highwayman.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E84721F8A6F; Fri,  4 Jan 2013 15:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.306
X-Spam-Level: 
X-Spam-Status: No, score=-0.306 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, GUARANTEED_100_PERCENT=0.012, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, SARE_SUB_OBFU_Q1=0.227]
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 Pv7YNBPmjI2S; Fri,  4 Jan 2013 15:44:17 -0800 (PST)
Received: from smtp.demon.co.uk (mdfmta005.mxout.tbr.inty.net [91.221.168.46]) by ietfa.amsl.com (Postfix) with ESMTP id 6DAAF21F8A69; Fri,  4 Jan 2013 15:44:17 -0800 (PST)
Received: from mdfmta005.tbr.inty.net (unknown [127.0.0.1]) by mdfmta005.tbr.inty.net (Postfix) with ESMTP id DB69AA6434A; Fri,  4 Jan 2013 23:44:15 +0000 (GMT)
Received: from mdfmta005.tbr.inty.net (unknown [127.0.0.1])	by mdfmta005.tbr.inty.net (Postfix) with ESMTP id B6171A64340; Fri,  4 Jan 2013 23:44:15 +0000 (GMT)
Received: from hestia.halldom.com (unknown [80.177.246.130])	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))	(No client certificate requested)	by mdfmta005.tbr.inty.net (Postfix) with ESMTP; Fri,  4 Jan 2013 23:44:15 +0000 (GMT)
Received: from hyperion.halldom.com ([80.177.246.170] helo=HYPERION)	by hestia.halldom.com with esmtpsa (TLSv1:AES128-SHA:128)	(Exim 4.76)	(envelope-from <chris.hall@highwayman.com>)	id 1TrGvu-00013M-RW; Fri, 04 Jan 2013 23:44:14 +0000
From: "Chris Hall" <chris.hall@highwayman.com>
To: <idr@ietf.org>,	<grow@ietf.org>
Date: Fri, 4 Jan 2013 23:44:09 -0000
Organization: Highwayman
Message-ID: <059d01cdead5$676701f0$363505d0$@highwayman.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3q1WF/iDYQH8sbSQq326HmotM7Ug==
Content-Language: en-gb
X-MDF-HostID: 8
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jan 2013 23:44:18 -0000

Tony Li wrote (on Fri 04-Jan-2013 at 17:02 +0000):
> To: Jeff Wheeler
....
> I agree that the Message Length will either be correct or it won't.
> Now, all us need is an oracle (the computer science kind ;-), to
> tell us which is which.  Got any handy?  ;-)

The outermost framing for the message is the Marker (16 x 0xFF)
followed by two octets of Message Length and one of Type.  Message
Length must be > 19 <= 4096 (currently), and >= 23 for an UPDATE
message.  So, there are some constraints there.

The next level of framing is the Withdrawn Routes Length and the Total
Path Attributes Length.  And 23 + those must equal the Message Length.

That (as per the drafts) is about it, oracle-wise.  A CRC would be
nice -- but not amongst the Attributes, except, perhaps between the
MP_XXX at the front of the Attributes and the rest.  But long runs of
0xFF are pretty rare in the body of a message, so the Marker is not
bad.

When we start considering what buggy software might be capable of
throwing out, I think we are in danger of running,
Wile-E.-Coyote-wise, out into mid-air...

Most code is tested before release.  Some parts of the code are in
constant use.  I think it is practical to consider some things
dependable.  (Never 100% guaranteed, but many-sigma.)

The outermost framing for a BGP Message is common to all messages.
The code which writes the Message Length can be written so that the
value is very closely tied to the value used to dispatch the message
to the output buffers.  This stuff is pretty well exercised, and I
think that a systematic error here is unlikely.  I can imagine some
memory management, or multi-threading, or random corruption, or other
exotic bug which could affect this outermost framing.  And such a bug
could lie dormant for a long time.  These sorts of issues are
notoriously capricious and hard to reproduce.  Which is a Bad Thing
but also a Good Thing, because following a session reset the bug may
never be seen again !

The inner framing of Withdrawn Routes, Path Attribute and NLRI is also
code in constant use.  Given a discrepancy between the lengths of
these and the Message Length, if pushed I would go with the Message
Length.  But, I would prefer to treat such a discrepancy as a
session-reset.  Mostly because I think that the balance of
probabilities is that an error here is more likely to be a symptom of
some exotic error than anything else.

[Plenty of hostages to fortune there... I look forward to hearing of
counter examples :-)]

This is all per the drafts.

When it comes down to it, the most likely place for systematic errors
to occur is in obscure corners of attribute handling.  eg the
well-known RIPE/DUKE "experiment".  I think that concentrating on
those would be the most productive.  There are enough issues to
resolve there to keep one busy.

It occurs to me: one issue with treating the Marker etc. as the one
true message boundary, is that if the code finds itself reading
forwards, looking for the next start of message, that implies that the
Message Length on the _previous_ one was probably wrong...  but all
decisions relating to that previous message have already been made :-(
That's not a problem if you reset the session.  In extremis I guess
one has bigger issues to worry about !

An option to resync on Marker etc, as a last-ditch,
keep-the-session-up-at-all-costs measure, doesn't seem that difficult
to me -- and wouldn't (key consideration) interfere with code for
normal running.

Chris


From jakob.heitz@ericsson.com  Fri Jan  4 16:00:33 2013
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB6721F8A8E; Fri,  4 Jan 2013 16:00:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level: 
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599, GUARANTEED_100_PERCENT=0.012, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 2e0wClLu9HAX; Fri,  4 Jan 2013 16:00:32 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id CB19421F846E; Fri,  4 Jan 2013 16:00:32 -0800 (PST)
Received: from EUSAAHC001.ericsson.se ([147.117.188.75]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r050EU8f009828; Fri, 4 Jan 2013 18:14:31 -0600
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.02.0318.004; Fri, 4 Jan 2013 19:00:24 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Chris Hall <chris.hall@highwayman.com>, "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: Ac3q1WF/t97q/gmUgEurMinxhJgROQAAU9CA
Date: Sat, 5 Jan 2013 00:00:23 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com>
In-Reply-To: <059d01cdead5$676701f0$363505d0$@highwayman.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:00:34 -0000

Current usages of BGP probably will not have anything matching
a marker in the byte stream other than the marker.

But future additions could well do that.
There is a draft to increase the maximum length,
so you can't rely on that being <=3D 4096.
What about a notification message or a possible future
operational message that replays the errant update.
That will look just like an update to the resync code.

On , Chris Hall <> wrote:

> Tony Li wrote (on Fri 04-Jan-2013 at 17:02 +0000):
>> To: Jeff Wheeler
> ....
>> I agree that the Message Length will either be correct or it won't.
>> Now, all us need is an oracle (the computer science kind ;-), to
>> tell us which is which.  Got any handy?  ;-)
>=20
> The outermost framing for the message is the Marker (16 x 0xFF)
> followed by two octets of Message Length and one of Type.  Message
> Length must be > 19 <=3D 4096 (currently), and >=3D 23 for an UPDATE
> message.  So, there are some constraints there.
>=20
> The next level of framing is the Withdrawn Routes Length and the Total
> Path Attributes Length.  And 23 + those must equal the Message Length.
>=20
> That (as per the drafts) is about it, oracle-wise.  A CRC would be
> nice -- but not amongst the Attributes, except, perhaps between the
> MP_XXX at the front of the Attributes and the rest.  But long runs of
> 0xFF are pretty rare in the body of a message, so the Marker is not
> bad.=20
>=20
> When we start considering what buggy software might be capable of
> throwing out, I think we are in danger of running,
> Wile-E.-Coyote-wise, out into mid-air...
>=20
> Most code is tested before release.  Some parts of the code are in
> constant use.  I think it is practical to consider some things
> dependable.  (Never 100% guaranteed, but many-sigma.)
>=20
> The outermost framing for a BGP Message is common to all messages.
> The code which writes the Message Length can be written so that the
> value is very closely tied to the value used to dispatch the message
> to the output buffers.  This stuff is pretty well exercised, and I
> think that a systematic error here is unlikely.  I can imagine some
> memory management, or multi-threading, or random corruption, or other
> exotic bug which could affect this outermost framing.  And such a bug
> could lie dormant for a long time.  These sorts of issues are
> notoriously capricious and hard to reproduce.  Which is a Bad Thing
> but also a Good Thing, because following a session reset the bug may
> never be seen again !=20
>=20
> The inner framing of Withdrawn Routes, Path Attribute and NLRI is also
> code in constant use.  Given a discrepancy between the lengths of
> these and the Message Length, if pushed I would go with the Message
> Length.  But, I would prefer to treat such a discrepancy as a
> session-reset.  Mostly because I think that the balance of
> probabilities is that an error here is more likely to be a symptom of
> some exotic error than anything else.
>=20
> [Plenty of hostages to fortune there... I look forward to hearing of
> counter examples :-)]=20
>=20
> This is all per the drafts.
>=20
> When it comes down to it, the most likely place for systematic errors
> to occur is in obscure corners of attribute handling.  eg the
> well-known RIPE/DUKE "experiment".  I think that concentrating on
> those would be the most productive.  There are enough issues to
> resolve there to keep one busy.
>=20
> It occurs to me: one issue with treating the Marker etc. as the one
> true message boundary, is that if the code finds itself reading
> forwards, looking for the next start of message, that implies that the
> Message Length on the _previous_ one was probably wrong...  but all
> decisions relating to that previous message have already been made :-(
> That's not a problem if you reset the session.  In extremis I guess
> one has bigger issues to worry about !
>=20
> An option to resync on Marker etc, as a last-ditch,
> keep-the-session-up-at-all-costs measure, doesn't seem that difficult
> to me -- and wouldn't (key consideration) interfere with code for
> normal running.=20
>=20
> Chris

--=20
Jakob Heitz.

From jakob.heitz@ericsson.com  Fri Jan  4 16:49:38 2013
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE82C21F850C; Fri,  4 Jan 2013 16:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.416
X-Spam-Level: 
X-Spam-Status: No, score=-6.416 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 YciEsAX+V-LT; Fri,  4 Jan 2013 16:49:38 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 571EF21F8506; Fri,  4 Jan 2013 16:49:38 -0800 (PST)
Received: from EUSAAHC007.ericsson.se ([147.117.188.93]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r0513WMc012460; Fri, 4 Jan 2013 19:03:38 -0600
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0318.004; Fri, 4 Jan 2013 19:49:35 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: John Leslie <john@jlc.net>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6txy2tR5Cg4rSE6gxRq5GR1+ZJg55kBw
Date: Sat, 5 Jan 2013 00:49:33 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E14E0BC@eusaamb109.ericsson.se>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se> <20130105003432.GJ25817@verdi>
In-Reply-To: <20130105003432.GJ25817@verdi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:49:38 -0000

On Friday, January 04, 2013 4:35 PM, John Leslie <mailto:john@jlc.net> wrot=
e:

>> What about a notification message or a possible future
>> operational message that replays the errant update.
>=20
>    Definitely a bad idea!
>=20
>    Replay of an errant update can't help, and would likely crash its
> receiver. Don't do that!=20

Sorry, that's not what I meant.
I meant a future operational message that says
"this update message caused me a problem and here is
the update message for your reference". It is a copy of
the message, not actually a replay.

--=20
Jakob Heitz.

From john@jlc.net  Fri Jan  4 16:34:33 2013
Return-Path: <john@jlc.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 679CC21F8A9B; Fri,  4 Jan 2013 16:34:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.372
X-Spam-Level: 
X-Spam-Status: No, score=-106.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 uE9ZI6SlEK2l; Fri,  4 Jan 2013 16:34:32 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3429B21F8B13; Fri,  4 Jan 2013 16:34:32 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 499B233D29; Fri,  4 Jan 2013 19:34:32 -0500 (EST)
Date: Fri, 4 Jan 2013 19:34:32 -0500
From: John Leslie <john@jlc.net>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Message-ID: <20130105003432.GJ25817@verdi>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se>
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Fri, 04 Jan 2013 18:09:04 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 00:34:33 -0000

Jakob Heitz <jakob.heitz@ericsson.com> wrote:
> 
> Current usages of BGP probably will not have anything matching
> a marker in the byte stream other than the marker.

   I can't think of any way for it to get there that isn't an error...

> But future additions could well do that.

   Sounds like a very bad idea to me.

> There is a draft to increase the maximum length,
> so you can't rely on that being <= 4096.

   Indeed: it will probably grow past 4096 sometime.

> What about a notification message or a possible future
> operational message that replays the errant update.

   Definitely a bad idea!

   Replay of an errant update can't help, and would likely crash its
receiver. Don't do that!

> That will look just like an update to the resync code.

   I'm not saying resync is necessarily a good thing -- but I believe
a marker (16 bytes all ones) in the middle of _any_ message deserves
an error of some kind.

   Lacking a TLV structure for messages, we should not let go of a
marker which separates messages.

--
John Leslie <john@jlc.net>

From jsw@inconcepts.biz  Fri Jan  4 21:29:58 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3405621F880F for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 21:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 m9S-wtCpTZc6 for <grow@ietfa.amsl.com>; Fri,  4 Jan 2013 21:29:56 -0800 (PST)
Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) by ietfa.amsl.com (Postfix) with ESMTP id A4F4221F87DF for <grow@ietf.org>; Fri,  4 Jan 2013 21:29:54 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id 13so20516496iea.21 for <grow@ietf.org>; Fri, 04 Jan 2013 21:29:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=aurlkeVlbudEVpiIOY+FTf6g1u4/RMrluZ9vz03lqX4=; b=alD1WJezlbSkc93RwhDGb5M4I8kdZ9DLXcS2J5DGrotRqfOizR5iqabDhUupNSPUfm qIaBmi0mgLHYSSRLMBPxrr67T8I8WkDRc4mtXjoF+owwzMXNInZzmfUfr9fs3BLQnNXZ jp6tn43VgaEuRd+zAAibZ6ZmGzCEp5sflNQ/Xe9pszqfPnQ2LeM5xLiVdqSBNm2SUPXw 9BJYeswAQ08IJscwSAPkd0DZKqGzAcYaFeiRXbmOClBfYGwlPIulC/Nlub6UzXphFS8i 6ByrX9MfLKdOD2hxaAikkIZMImEh5FNfKVZNWMGM5bbL0cqDDVpZCKLP1ArhR3TfMsYk VeAw==
MIME-Version: 1.0
X-Received: by 10.50.170.102 with SMTP id al6mr743982igc.70.1357363785841; Fri, 04 Jan 2013 21:29:45 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Fri, 4 Jan 2013 21:29:45 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <20130105003432.GJ25817@verdi>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se> <20130105003432.GJ25817@verdi>
Date: Sat, 5 Jan 2013 00:29:45 -0500
Message-ID: <CAPWAtbJP8w-uRbaFr3_7fQg_hNNHuSwgEysJTUtE8a5O=uxVgQ@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: John Leslie <john@jlc.net>, Jakob Heitz <jakob.heitz@ericsson.com>,  Chris Hall <chris.hall@highwayman.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmCR4YYIMPrT7V6eYfdQc6G/jg4vda2Hm50E0YOA6JlraQm9WZYtz/m6q1xzSbmozoGQFfS
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 05:29:59 -0000

On Fri, Jan 4, 2013 at 7:34 PM, John Leslie <john@jlc.net> wrote:
>    Lacking a TLV structure for messages, we should not let go of a
> marker which separates messages.

Even if you were inventing "BGP 5" and you cleaned up all the messy
extensions and implied field lengths, I think you would be persuaded
to keep MARKER around as a good "dummy check" on the message stream.
Historically, protocol designers have often conserved octets because
it seems like a good way to keep protocol overhead low.  For
control-plane protocols whose encoding/transmission overhead is
insignificant, this has sometimes produced poor results.

On Fri, Jan 4, 2013 at 7:49 PM, Jakob Heitz <jakob.heitz@ericsson.com> wrote:
> Sorry, that's not what I meant.
> I meant a future operational message that says
> "this update message caused me a problem and here is
> the update message for your reference". It is a copy of
> the message, not actually a replay.

I liked your idea the first time I read it, and I continue to like it.
 This would be VERY helpful for troubleshooting.

We had some discussion before about what would happen if the original
message, being echoed back in a "this was broken" for diagnostic
purposes, could not fit into the maximum message length for the
session.

What if you didn't include the original Message header, the MARKER,
Message Type and Length?  Your "broken message" echo Message would
then be exactly the same Length as the bad one so it would definitely
fit in the maximum length, and you don't need to tell the other side
what the original Length was because it will know by the Length of
your echo Message.

As long as it is only for "broken UPDATE" and not for other kinds of
messages, then you don't need to encode the Message Type field.

The only downside is it wouldn't work for anything except a broken
UPDATE, and it would need to be extended in the future if new types of
messages are added to BGP.  These seem like reasonable limitations
though.

On Fri, Jan 4, 2013 at 6:44 PM, Chris Hall <chris.hall@highwayman.com> wrote:
> An option to resync on Marker etc, as a last-ditch,
> keep-the-session-up-at-all-costs measure, doesn't seem that difficult
> to me -- and wouldn't (key consideration) interfere with code for
> normal running.

I don't think it's that difficult either, but I do not know if the
cost of implementing it is worth the reward.

Attribute errors are things that, historically, we've seen propagate
through the DFZ (and they might inside a datacenter network too) and
the cost of dealing with them is probably going to be worthwhile.  A
message length error isn't going to cascade through anybody's network
right now, let alone cross domain boundaries; so is it worth doing?

I only brought up re-sync because it is possible to do and it might
have some limited value if we had Jakob's "i got this bad message,
here it is" feature.  I'm still not necessarily advocating the re-sync
idea.

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

From jakob.heitz@ericsson.com  Fri Jan  4 21:50:18 2013
Return-Path: <jakob.heitz@ericsson.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D072921F84B2; Fri,  4 Jan 2013 21:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.409
X-Spam-Level: 
X-Spam-Status: No, score=-6.409 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
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 p9UaOHTJIVU7; Fri,  4 Jan 2013 21:50:18 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id E695921F8480; Fri,  4 Jan 2013 21:50:17 -0800 (PST)
Received: from EUSAAHC007.ericsson.se ([147.117.188.93]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id r0564G1a019852; Sat, 5 Jan 2013 00:04:17 -0600
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.02.0318.004; Sat, 5 Jan 2013 00:50:08 -0500
From: Jakob Heitz <jakob.heitz@ericsson.com>
To: Jeff Wheeler <jsw@inconcepts.biz>, John Leslie <john@jlc.net>, Chris Hall <chris.hall@highwayman.com>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN6wW4ArX4RXLSC02HvqTfuOalqpg6OUkQ
Date: Sat, 5 Jan 2013 05:50:07 +0000
Message-ID: <2F3EBB88EC3A454AAB08915FBF0B8C7E14E2CE@eusaamb109.ericsson.se>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se> <20130105003432.GJ25817@verdi> <CAPWAtbJP8w-uRbaFr3_7fQg_hNNHuSwgEysJTUtE8a5O=uxVgQ@mail.gmail.com>
In-Reply-To: <CAPWAtbJP8w-uRbaFr3_7fQg_hNNHuSwgEysJTUtE8a5O=uxVgQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 05:50:18 -0000

On Friday, January 04, 2013 9:30 PM, Jeff Wheeler <mailto:jsw@inconcepts.bi=
z> wrote:

> Jakob's "i got this bad message, here it is" feature.

Just to set the record straight, it's not my idea and
I was referring to the older discussion about this.

I'll note that=20
http://tools.ietf.org/html/draft-ietf-idr-operational-message-00
has expired. It would be a good complement to
http://tools.ietf.org/html/draft-ietf-idr-error-handling-03
if it were revived.

--=20
Jakob Heitz.

From john@jlc.net  Sat Jan  5 03:50:50 2013
Return-Path: <john@jlc.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FE921F86E8; Sat,  5 Jan 2013 03:50:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.372
X-Spam-Level: 
X-Spam-Status: No, score=-106.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
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 yqwq0HXQ3e3a; Sat,  5 Jan 2013 03:50:50 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id EAD1921F8481; Sat,  5 Jan 2013 03:50:49 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 90AF333D56; Sat,  5 Jan 2013 06:50:49 -0500 (EST)
Date: Sat, 5 Jan 2013 06:50:49 -0500
From: John Leslie <john@jlc.net>
To: Jakob Heitz <jakob.heitz@ericsson.com>
Message-ID: <20130105115049.GK25817@verdi>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se> <20130105003432.GJ25817@verdi> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E0BC@eusaamb109.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E14E0BC@eusaamb109.ericsson.se>
User-Agent: Mutt/1.4.1i
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 11:50:50 -0000

Jakob Heitz <jakob.heitz@ericsson.com> wrote:
> On Friday, January 04, 2013 4:35 PM, John Leslie <mailto:john@jlc.net> wrote:
> 
>> Replay of an errant update can't help, and would likely crash its
>> receiver. Don't do that! 
> 
> Sorry, that's not what I meant.
> I meant a future operational message that says
> "this update message caused me a problem and here is
> the update message for your reference". It is a copy of
> the message, not actually a replay.

   Danger, Will Robinson!

   Actually, we could invent a message type which reflects the content
of a "bad" update, but it would only be useful for logging at the
sending peer for human perusal; and, to be useful to that human it
would need to classify the problem and indicate what part(s) of the
update have been acted upon.

   Under no circumstances should we do this without making its length
abundantly clear -- both the length we assumed when reading it and the
length of what we are returning (which need not be the same: humans
get the best value out of the first few hundred bytes in most cases).
In particular, if we detect 16-bytes of marker within it, we MUST NOT
return that marker un-escaped.

   This would probably be the most helpful when we _don't_ expect to
be able to continue without a NOTIFY. We would need to send this only
to a peer that advertised the capability to log it; and that might
include the ability to recognize it _after_ the NOTIFY if we decide
that sending it before the NOTIFY is too risky...

--
John Leslie <john@jlc.net>

From rjs@rob.sh  Sat Jan  5 05:31:50 2013
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF9421F8473; Sat,  5 Jan 2013 05:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level: 
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 BsvsMA5-LXoN; Sat,  5 Jan 2013 05:31:49 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id DC8A821F843B; Sat,  5 Jan 2013 05:31:48 -0800 (PST)
Received: from [46.65.174.229] (helo=[172.16.1.8]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1TrTnb-0004pq-1s; Sat, 05 Jan 2013 13:28:31 +0000
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <2F3EBB88EC3A454AAB08915FBF0B8C7E14E2CE@eusaamb109.ericsson.se>
Date: Sat, 5 Jan 2013 13:31:44 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <128732A4-0343-4022-88E0-A21004D173DC@rob.sh>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se> <20130105003432.GJ25817@verdi> <CAPWAtbJP8w-uRbaFr3_7fQg_hNNHuSwgEysJTUtE8a5O=uxVgQ@mail.gmail.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E2CE@eusaamb109.ericsson.se>
To: Jakob Heitz <jakob.heitz@ericsson.com>
X-Mailer: Apple Mail (2.1257)
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>, Chris Hall <chris.hall@highwayman.com>, John Leslie <john@jlc.net>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 13:31:50 -0000

Hi Jakob,

We (the authors) are working on a re-spin of this draft. My aim is to do =
this within the next week or so.

Kind regards,
r.

On 5 Jan 2013, at 05:50, Jakob Heitz wrote:

> On Friday, January 04, 2013 9:30 PM, Jeff Wheeler =
<mailto:jsw@inconcepts.biz> wrote:
>=20
>> Jakob's "i got this bad message, here it is" feature.
>=20
> Just to set the record straight, it's not my idea and
> I was referring to the older discussion about this.
>=20
> I'll note that=20
> http://tools.ietf.org/html/draft-ietf-idr-operational-message-00
> has expired. It would be a good complement to
> http://tools.ietf.org/html/draft-ietf-idr-error-handling-03
> if it were revived.
>=20
> --=20
> Jakob Heitz.
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr


From jsw@inconcepts.biz  Sat Jan  5 09:26:05 2013
Return-Path: <jsw@inconcepts.biz>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F8221F8599 for <grow@ietfa.amsl.com>; Sat,  5 Jan 2013 09:26:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227]
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 hj6fTQbujXnc for <grow@ietfa.amsl.com>; Sat,  5 Jan 2013 09:26:05 -0800 (PST)
Received: from mail-ia0-f182.google.com (mail-ia0-f182.google.com [209.85.210.182]) by ietfa.amsl.com (Postfix) with ESMTP id DE58421F8581 for <grow@ietf.org>; Sat,  5 Jan 2013 09:26:04 -0800 (PST)
Received: by mail-ia0-f182.google.com with SMTP id x2so14895666iad.27 for <grow@ietf.org>; Sat, 05 Jan 2013 09:26:04 -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=bfGk1aICDFT6p2hipYjC6leGnTqt089Av7AEDQCs2Ck=; b=kfNd4y1MJZTyjQnftOl4Tlv7r72IbeS3tHucnsVY4uvQseImAdh1qasd5mP/UIIkyv /msOGlyTXW4UnUxCujX+GUf2RnEXTPWyP6DXKLDa/ricuYtc4hjLdBumiL+rF8DjIMOb gL2C+bH/m9y0SYp/A+/EKpteSs13ZiGR20+P5/rI6YVo4ZKRWYYIFTWVpAOqxhLSiSQ1 g+0AnsUsXNFjNZwXYAPDIqXg+Ut9dQ7xvL17uMt4PjB/H87JFMDCIhJ8I2OIjF2Zw3Eu PNQGlmBpKQBFMGgexDGbpwhwyVvUXbw0QRH4ILlxWIR36oDxrb+Upko3Y7Im5cfYAXMe VCZQ==
MIME-Version: 1.0
Received: by 10.50.152.240 with SMTP id vb16mr1858328igb.45.1357406764469; Sat, 05 Jan 2013 09:26:04 -0800 (PST)
Received: by 10.64.132.33 with HTTP; Sat, 5 Jan 2013 09:26:04 -0800 (PST)
X-Originating-IP: [74.134.22.105]
In-Reply-To: <20130105115049.GK25817@verdi>
References: <059d01cdead5$676701f0$363505d0$@highwayman.com> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E005@eusaamb109.ericsson.se> <20130105003432.GJ25817@verdi> <2F3EBB88EC3A454AAB08915FBF0B8C7E14E0BC@eusaamb109.ericsson.se> <20130105115049.GK25817@verdi>
Date: Sat, 5 Jan 2013 12:26:04 -0500
Message-ID: <CAPWAtbLstkZrkbWBS4DuFEn5sxx8TkYrjY28vHj4JHJrmbP3zw@mail.gmail.com>
From: Jeff Wheeler <jsw@inconcepts.biz>
To: John Leslie <john@jlc.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQna8FnRC0INF7EVskBgJsUQvCUs6liX0Y/7ThgPIwiM6Dc2//yNF8j0YOMhYVHZ+W3lSWX0
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jan 2013 17:26:05 -0000

On Sat, Jan 5, 2013 at 6:50 AM, John Leslie <john@jlc.net> wrote:
>    Actually, we could invent a message type which reflects the content
> of a "bad" update, but it would only be useful for logging at the
> sending peer for human perusal; and, to be useful to that human it
> would need to classify the problem and indicate what part(s) of the
> update have been acted upon.

I don't think the message necessarily has to describe the problem, but
BGP already has some mechanisms for this.

If a receiver detects a malformed attribute, it will send a
Notification with the bad attribute in the Data part of the notice.
So the existing Notification will at least tell you about that.

Imagine if you are an ISP and your customer's router is complaining of
bad messages and resetting the session.  His logging is not good so
you don't have very much information to go on.  Maybe you get a
malformed attribute notice but your routers don't have any way for you
to search for what paths carry that attribute.  You will be debugging
for a while!

If the customer's router sent you the whole message you could
troubleshoot the problem more quickly even if the customer router
doesn't tell you why it choked on the message or produce any useful
log entries for the customer tech.

>    Under no circumstances should we do this without making its length
> abundantly clear -- both the length we assumed when reading it and the
> length of what we are returning (which need not be the same: humans
> get the best value out of the first few hundred bytes in most cases).
> In particular, if we detect 16-bytes of marker within it, we MUST NOT
> return that marker un-escaped.

I agree that returning the un-escaped MARKER could have unintended consequences!

I think the whole message is useful ESPECIALLY if the NLRI are moved
to the beginning of messages at some time in the future.  After all,
if they are moved, then attributes will be at the end of the message,
so you might need them.

If the "oh no" message is literally the bad message with a different
Message Type, then you will get everything including what the receiver
thought the length was.  The only things you will not get is the
original marker and message type.  If you only generate "oh no" if the
marker is believed to be legit and the Message Type was UPDATE, then
these are implicit whenever you get an "oh no" message.

>    This would probably be the most helpful when we _don't_ expect to
> be able to continue without a NOTIFY. We would need to send this only
> to a peer that advertised the capability to log it; and that might
> include the ability to recognize it _after_ the NOTIFY if we decide
> that sending it before the NOTIFY is too risky...

Actually if error-handling introduces the ability to treat-as-withdraw
or ignore-bad-message then it seems like it will become useful to have
this new diagnostic message even if the BGP session is not reset.
That way both sides of the session have some diagnostic information
about problems that are potentially being masked by the use of
error-handling.

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

From bruno.decraene@orange.com  Tue Jan  8 02:57:20 2013
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 838C521F8DAE; Tue,  8 Jan 2013 02:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 PWv5u8LVHQ1S; Tue,  8 Jan 2013 02:57:14 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id A267121F8D8B; Tue,  8 Jan 2013 02:57:13 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 28B94338002; Tue,  8 Jan 2013 11:57:12 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id E752835C102; Tue,  8 Jan 2013 11:57:08 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0318.004; Tue, 8 Jan 2013 11:57:08 +0100
From: <bruno.decraene@orange.com>
To: Rob Shakir <rjs@rob.sh>
Thread-Topic: [Idr] Fwd: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN5GI5uUvvkzXFTkC50Ybfet8IiZg9vUmg
Date: Tue, 8 Jan 2013 10:57:08 +0000
Message-ID: <31774_1357642629_50EBFB84_31774_520_1_53C29892C857584299CBF5D05346208A122AFB@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <CD024583.EA71%rob.shakir@bt.com> <B60B37DD-9A43-45B3-B8F4-5D4BF8475F6B@rob.sh>
In-Reply-To: <B60B37DD-9A43-45B3-B8F4-5D4BF8475F6B@rob.sh>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.2]
Content-Type: multipart/alternative; boundary="_000_53C29892C857584299CBF5D05346208A122AFBPEXCVZYM11corpora_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.12.31.121227
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] Fwd: I-D Action:	draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 10:57:20 -0000

--_000_53C29892C857584299CBF5D05346208A122AFBPEXCVZYM11corpora_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Rob, all,



Thanks for the updated document.

New version is definitely an improvement. Thanks for the work.

Please find below some comments.





1)  Critical error (=A73)



IMHO, the term "critical error" is mixing both technical/protocol considera=
tions (e.g. can't read the update) and requirements considerations (BGP ses=
sions state is too degraded and I prefer shutting it down rather than runni=
ng on a degraded mode) which IMHO is unfortunate and does not help the disc=
ussion. I'd much prefer that we distinguish both by defining technical leve=
ls of errors and then defining the requirements for each plus  the conseque=
nces/drawbacks of the decision (whether to keep or shut the session).

For the protocol standpoint, I would propose the following level of errors,=
 based on the protocol encoding layers: session, update, attribute.

- attribute level error: semantic or syntax error in the attribute value or=
 attribute flags

- session level error: error in the update length / marker. i.e. if skippin=
g the update length I can't find the marker of the next bgp message.

- update level error: any other error in the update message



We can further distinguish if the NLRIs can be parsed or not.



2)  Business Requirements

In the current text, I found the requirements a bit too technically oriente=
d. I'd rather add business requirements independent of the current solution=
s. I would propose:



In VPN networks, VPN are supposed to be isolated from each others and from =
the others services (most notably the Internet). Hence, an error on routes/=
BGP messages related to a VPN SHOULD NOT negatively impact others VPN. Simi=
larly, an error on routes/BGP messages related to a non VPN service SHOULD =
not negatively impact the VPN service.

In Internet networks, ASes are supposed to be Autonomous. Hence an error on=
 routes/BGP messages originated by an AS SHOULD NOT negatively impact desti=
nations originated from others ASes.



By "negatively impact", we mean losing reachability for a destination (NLRI=
), typically by losing all the paths in the Loc-RIB to that destination (NL=
RI). Note that those paths may be learnt through multiple BGP sessions and =
hence the requirement span multiple BGP sessions. The consequence is that i=
f the BGP error is believed to be limited to a single BGP session (e.g. a s=
ession level error), then in a network with redundancy, the destination is =
believed to be still known through another session and hence the session MA=
Y be chosen to be shutdown and all path learned from that session removed. =
On the contrary, if the BGP error has a chance to be also met on the redund=
ant paths/sessions, then the BGP session and the routes learned from that s=
ession SHOULD be preserved, until the negatives consequences are considered=
 too important. When evaluating those consequences, the fact that all redun=
dant paths/sessions may suffer from the same error and hence will inherit t=
he same decision MUST be considered.



As an illustration, we typically seek to avoid that because of a single BGP=
 error a PE lose both its redundant iBGP session with its BGP RR. And by "a=
 PE" I really mean all PE experiencing this condition. Could easily be 10s =
of PE, even 100s.



3)  Technical requirements

For session level error, the BGP session is dead so need to be shutdown/gra=
ceful shutdown/graceful restart. If the update length is set to the number =
of octets sent to the peer (or vice versa) rather than computed based on th=
e content of the update, there is a chance to 1) limit the number of such s=
ession level errors and 2) increase the probability that this error is loca=
l to that session and not likely to happen on a redundant/backup session. T=
here is probably a limited part of the BGP code which needs to be hardened =
to reduce such unrecoverable errors. And if those errors are still frequent=
, we may further propose technical solutions (e.g. replacing TCP by SCTP wh=
ich can provides message boundaries, among others things (e.g. some benefit=
s of multi-sessions))



For attribute & update level error when the NLRI can be parsed, cf draft-er=
ror-handling (treat as withdraw).



Now let the discussion begin :). For attribute & update level error when th=
e NLRI cannot be extracted IMHO there is room for discussion and analysis o=
f the consequences.

"since the NLRI cannot be extracted, error handling mechanisms must be appl=
ied at the per-session level" (=A75)

Well, IMO, this is a choice to be made rather than a "must".





If we were to skip a BGP update:

For Internet, probably the worst case would be to miss a BGP update with a =
loop in the AS path and hence create a loop for me and my upstream ASes for=
 the NLRI in the missed updated. How much probable is this? 0 for iBGP sess=
ions. TBE for eBGP. Then what would be the consequences? loss of connectivi=
ty for the NLRI until the problem is manually solved by an AS between the o=
rigin and me, possible forwarding congestions for others. I'm not sure I ca=
re too much about loosing reachability to NLRI in faulty BGP update as most=
 likely, if only one BGP update (out of millions) is faulty, the reason may=
 come from the origin AS playing with a specific bit or attribute and if th=
ey chose to play with their update, they should bear the responsibility. To=
 be compared by the probability of losing all redundant paths (if the error=
 is seen on redundant path) and the consequences (PE -possibly all PEs- dow=
n).



For VPN, probably the worst case would be to keep a VPN label previously al=
located to VPN 1 and re-allocated to another VPN (VPN breach Cf http://tool=
s.ietf.org/html/draft-uttaro-idr-bgp-persistence-01#section-8)

Again, the pro and con could be discussed (e.g. possibly one way partial VP=
N breach for some time (that basically no one can exploit) vs all VPN/PE be=
ing down. IMHO, if we believe such issue could be corrected in 30-60 minute=
s, I would probably favor keeping the session up.



>From the lively discussions, looks like the opinions may vary depending on =
the AS, people and circumstances. E.g. how much my redundant BGP paths are =
failure independent? (e.g. use different BGP implementations)

As such, what about defining severity levels for BGP error handling? As one=
 may wish to accept only low severity errors while others may be willing to=
 accept high severity errors (including when the NLRI cannot be found) e.g.=
 the network has been down for 30 minutes, while waiting for the patch, one=
 may want to be able to restore some service at all costs (can't possibly b=
e worst).



Again, IMHO it would be good to discuss the drawbacks depending on the situ=
ation (iBGP, eBGP; hop by hop routed, tunneled ...) in this requirement doc=
ument to make sure we are all on the same page, we have constructive discus=
sions and SP enabling revised error handling are fully aware of the consequ=
ences.



4)  Security consideration

In =A77 "security considerations" I would discuss the fact that current BGP=
 error handling (or a (too) strict one) could be exploited by attackers to =
create a remote DOS attack.

Should we also ask a review of the SIDR WG since "The purpose of the SIDR w=
orking group is to reduce vulnerabilities in the inter-domain routing syste=
m." ? ...



Best regards,

Bruno





























>-----Original Message-----

>From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of Rob

>Shakir

>Sent: Thursday, December 27, 2012 7:44 PM

>To: idr@ietf.org

>Subject: [Idr] Fwd: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-er=
ror-

>handling-06.txt

>

>Hi IDR!

>

>FYI -- please find an updated relating to a new version of draft-ietf-grow=
-ops-

>reqs-for-bgp-error-handling.

>

>Any comments very welcome (to me or grow@).

>

>Seasons greetings!

>r.

>

>Begin forwarded message:

>

>> From: <rob.shakir@bt.com<mailto:rob.shakir@bt.com>>

>> Subject: Re: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-

>handling-06.txt

>> Date: 27 December 2012 18:41:50 GMT

>> To: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>, <i-d-an=
nounce@ietf.org<mailto:i-d-announce@ietf.org>>

>> Cc: grow@ietf.org<mailto:grow@ietf.org>

>>

>> On 27/12/2012 18:35, "internet-drafts@ietf.org<mailto:internet-drafts@ie=
tf.org>" <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>

>> wrote:

>>

>>>

>>> A New Internet-Draft is available from the on-line Internet-Drafts

>>> directories.

>>> This draft is a work item of the Global Routing Operations Working Group

>>> of the IETF.

>>>

>>>   Title           : Operational Requirements for Enhanced Error Handling

>>> Behaviour in BGP-4

>>>   Author(s)       : Rob Shakir

>>>   Filename        : draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.=
txt

>>>   Pages           : 19

>>>   Date            : 2012-12-27

>>

>> Hi GROW!

>>

>> This update is a fairly major re-spin of the BGP Error Handling

>> requirements draft. The technical content should be as per the previous

>> revisions however, following the ietf/RtgDir last call comments, I have

>> made the following changes:

>>

>> * Made the amendments that were discussed and there was no disagreement

>> with from our meeting in Atlanta -- this is essentially renaming the

>> Critical/Semantic error types to Critical/Non-Critical.

>>

>> * Significant de-duplication within the text including merging the

>> operational monitoring/toolset discussions into the error handling

>> sections.

>>

>> * Adoption of rfc2119 language throughout to clarify the requirements.

>>

>> * Removal of some of the discussion around more detailed justifications

>> for why particular decisions were made. I think this was useful through

>> the discussion phase of this draft, but it seems like GROW/IDR have

>> converged on a relatively stable set of requirements, so I have trimmed

>> back some of this discussion.

>>

>> I'd really welcome any further comments on this before we re-submit for

>> publication. To eke these out - Peter/Chris - can you kick off a WGLC for

>> this draft please? :-)

>>

>> Seasons greetings!

>> r.

>>

>> _______________________________________________

>> GROW mailing list

>> GROW@ietf.org<mailto:GROW@ietf.org>

>> https://www.ietf.org/mailman/listinfo/grow

>

>_______________________________________________

>Idr mailing list

>Idr@ietf.org<mailto:Idr@ietf.org>

>https://www.ietf.org/mailman/listinfo/idr

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.


--_000_53C29892C857584299CBF5D05346208A122AFBPEXCVZYM11corpora_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 89.5pt 72.0pt 89.5pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:373192298;
	mso-list-type:hybrid;
	mso-list-template-ids:674153560 67895313 67895321 67895323 67895311 678953=
21 67895323 67895311 67895321 67895323;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"FR" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi Rob, all,<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Thanks for the updated docum=
ent.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">New version is definitely an=
 improvement. Thanks for the work.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please find below some comme=
nts.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">1=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Critical error (=A73)<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">IMHO, the term &#8220;critic=
al error&#8221; is mixing both technical/protocol considerations (e.g. can&=
#8217;t read the update) and requirements considerations (BGP sessions stat=
e is too degraded and I prefer shutting it down rather
 than running on a degraded mode) which IMHO is unfortunate and does not he=
lp the discussion. I&#8217;d much prefer that we distinguish both by defini=
ng technical levels of errors and then defining the requirements for each p=
lus &nbsp;the consequences/drawbacks of the
 decision (whether to keep or shut the session).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">For the protocol standpoint,=
 I would propose the following level of errors, based on the protocol encod=
ing layers: session, update, attribute.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">- attribute level error: sem=
antic or syntax error in the attribute value or attribute flags<o:p></o:p><=
/span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">- session level error: error=
 in the update length / marker. i.e. if skipping the update length I can&#8=
217;t find the marker of the next bgp message.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">- update level error: any ot=
her error in the update message<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">We can further distinguish i=
f the NLRIs can be parsed or not.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">2=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Business Requirements<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">In the current text, I found=
 the requirements a bit too technically oriented. I&#8217;d rather add busi=
ness requirements independent of the current solutions. I would propose:<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">In VPN networks, VPN are sup=
posed to be isolated from each others and from the others services (most no=
tably the Internet). Hence, an error on routes/BGP messages related to a VP=
N SHOULD NOT negatively impact others
 VPN. Similarly, an error on routes/BGP messages related to a non VPN servi=
ce SHOULD not negatively impact the VPN service.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">In Internet networks, ASes a=
re supposed to be Autonomous. Hence an error on routes/BGP messages origina=
ted by an AS SHOULD NOT negatively impact destinations originated from othe=
rs ASes.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">By &#8220;negatively impact&=
#8221;, we mean losing reachability for a destination (NLRI), typically by =
losing all the paths in the Loc-RIB to that destination (NLRI). Note that t=
hose paths may be learnt through multiple BGP sessions
 and hence the requirement span multiple BGP sessions. The consequence is t=
hat if the BGP error is believed to be limited to a single BGP session (e.g=
. a session level error), then in a network with redundancy, the destinatio=
n is believed to be still known
 through another session and hence the session MAY be chosen to be shutdown=
 and all path learned from that session removed. On the contrary, if the BG=
P error has a chance to be also met on the redundant paths/sessions, then t=
he BGP session and the routes learned
 from that session SHOULD be preserved, until the negatives consequences ar=
e considered too important. When evaluating those consequences, the fact th=
at all redundant paths/sessions may suffer from the same error and hence wi=
ll inherit the same decision MUST
 be considered.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">As an illustration, we typic=
ally seek to avoid that because of a single BGP error a PE lose both its re=
dundant iBGP session with its BGP RR. And by &#8220;a PE&#8221; I really me=
an all PE experiencing this condition. Could easily
 be 10s of PE, even 100s.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">3=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Technical requirements<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">For session level error, the=
 BGP session is dead so need to be shutdown/graceful shutdown/graceful rest=
art. If the update length is set to the number of octets sent to the peer (=
or vice versa) rather than computed
 based on the content of the update, there is a chance to 1) limit the numb=
er of such session level errors and 2) increase the probability that this e=
rror is local to that session and not likely to happen on a redundant/backu=
p session. There is probably a limited
 part of the BGP code which needs to be hardened to reduce such unrecoverab=
le errors. And if those errors are still frequent, we may further propose t=
echnical solutions (e.g. replacing TCP by SCTP which can provides message b=
oundaries, among others things (e.g.
 some benefits of multi-sessions))<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">For attribute &amp; update l=
evel error when the NLRI can be parsed, cf draft-error-handling (treat as w=
ithdraw).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Now let the discussion begin=
 </span><span lang=3D"EN-US" style=3D"font-family:Wingdings">J</span><span =
lang=3D"EN-US">. For attribute &amp; update level error when the NLRI canno=
t be extracted IMHO there is room for discussion
 and analysis of the consequences.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;">&#8220;since the NLRI cannot be extracted, =
error handling mechanisms must be applied at the per-session level&#8221; (=
=A75)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Well, IMO, this is a choice =
to be made rather than a &#8220;must&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">If we were to skip a BGP upd=
ate:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">For Internet, probably the w=
orst case would be to miss a BGP update with a loop in the AS path and henc=
e create a loop for me and my upstream ASes for the NLRI in the missed upda=
ted. How much probable is this? 0 for
 iBGP sessions. TBE for eBGP. Then what would be the consequences? loss of =
connectivity for the NLRI until the problem is manually solved by an AS bet=
ween the origin and me, possible forwarding congestions for others. I&#8217=
;m not sure I care too much about loosing
 reachability to NLRI in faulty BGP update as most likely, if only one BGP =
update (out of millions) is faulty, the reason may come from the origin AS =
playing with a specific bit or attribute and if they chose to play with the=
ir update, they should bear the
 responsibility. To be compared by the probability of losing all redundant =
paths (if the error is seen on redundant path) and the consequences (PE -po=
ssibly all PEs- down).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">For VPN, probably the worst =
case would be to keep a VPN label previously allocated to VPN 1 and re-allo=
cated to another VPN (VPN breach Cf
<a href=3D"http://tools.ietf.org/html/draft-uttaro-idr-bgp-persistence-01#s=
ection-8">
http://tools.ietf.org/html/draft-uttaro-idr-bgp-persistence-01#section-8</a=
>)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Again, the pro and con could=
 be discussed (e.g. possibly one way partial VPN breach for some time (that=
 basically no one can exploit) vs all VPN/PE being down. IMHO, if we believ=
e such issue could be corrected in 30-60
 minutes, I would probably favor keeping the session up.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">From the lively discussions,=
 looks like the opinions may vary depending on the AS, people and circumsta=
nces. E.g. how much my redundant BGP paths are failure independent? (e.g. u=
se different BGP implementations)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">As such, what about defining=
 severity levels for BGP error handling? As one may wish to accept only low=
 severity errors while others may be willing to accept high severity errors=
 (including when the NLRI cannot be
 found) e.g. the network has been down for 30 minutes, while waiting for th=
e patch, one may want to be able to restore some service at all costs (can&=
#8217;t possibly be worst).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Again, IMHO it would be good=
 to discuss the drawbacks depending on the situation (iBGP, eBGP; hop by ho=
p routed, tunneled &#8230;) in this requirement document to make sure we ar=
e all on the same page, we have constructive
 discussions and SP enabling revised error handling are fully aware of the =
consequences.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo1">
<![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:Ignore">4=
)<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Security consideration<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">In =A77 &#8220;security cons=
iderations&#8221; I would discuss the fact that current BGP error handling =
(or a (too) strict one) could be exploited by attackers to create a remote =
DOS attack.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Should we also ask a review =
of the SIDR WG since &#8220;The purpose of the SIDR working group is to red=
uce vulnerabilities in the inter-domain routing system.&#8221; ? ...<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Best regards,<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Bruno<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt;</span><span lang=3D"EN-=
US">-----Original Message-----</span><span lang=3D"EN-US"><o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt;</span><span lang=3D"EN-=
US">From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of R=
ob</span><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt;</span><span lang=3D"EN-=
US">Shakir</span><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&gt;</span><span lang=3D"EN-=
US">Sent: </span>
Thursday, December 27, 2012 7:44 PM<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;To: idr@ietf.org<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;Subject: [Idr] Fwd: [GROW] I-D Action: draft-=
ietf-grow-ops-reqs-for-bgp-error-<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;handling-06.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;Hi IDR!<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;FYI -- please find an updated relating to a n=
ew version of draft-ietf-grow-ops-<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;reqs-for-bgp-error-handling.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;Any comments very welcome (to me or grow@).<o=
:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;Seasons greetings!<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;r.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;Begin forwarded message:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; From: &lt;<a href=3D"mailto:rob.shakir@b=
t.com"><span style=3D"color:windowtext;text-decoration:none">rob.shakir@bt.=
com</span></a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Subject: Re: [GROW] I-D Action: draft-ie=
tf-grow-ops-reqs-for-bgp-error-<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;handling-06.txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Date: 27 December 2012 18:41:50 GMT<o:p>=
</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; To: &lt;<a href=3D"mailto:internet-draft=
s@ietf.org"><span style=3D"color:windowtext;text-decoration:none">internet-=
drafts@ietf.org</span></a>&gt;, &lt;<a href=3D"mailto:i-d-announce@ietf.org=
"><span style=3D"color:windowtext;text-decoration:none">i-d-announce@ietf.o=
rg</span></a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Cc: <a href=3D"mailto:grow@ietf.org"><sp=
an style=3D"color:windowtext;text-decoration:none">grow@ietf.org</span></a>=
<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; On 27/12/2012 18:35, &quot;<a href=3D"ma=
ilto:internet-drafts@ietf.org"><span style=3D"color:windowtext;text-decorat=
ion:none">internet-drafts@ietf.org</span></a>&quot; &lt;<a href=3D"mailto:i=
nternet-drafts@ietf.org"><span style=3D"color:windowtext;text-decoration:no=
ne">internet-drafts@ietf.org</span></a>&gt;<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; wrote:<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; A New Internet-Draft is available fr=
om the on-line Internet-Drafts<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; directories.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; This draft is a work item of the Glo=
bal Routing Operations Working Group<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; of the IETF.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; &nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Operational Requirements for Enhance=
d Error Handling<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; Behaviour in BGP-4<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; &nbsp; Author(s)&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; : Rob Shakir<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; &nbsp; Filename&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; : draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.=
txt<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; &nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 19<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;&gt; &nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2012-12-27<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Hi GROW!<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; This update is a fairly major re-spin of=
 the BGP Error Handling<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; requirements draft. The technical conten=
t should be as per the previous<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; revisions however, following the ietf/Rt=
gDir last call comments, I have<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; made the following changes:<o:p></o:p></=
p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; * Made the amendments that were discusse=
d and there was no disagreement<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; with from our meeting in Atlanta -- this=
 is essentially renaming the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Critical/Semantic error types to Critica=
l/Non-Critical.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; * Significant de-duplication within the =
text including merging the<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; operational monitoring/toolset discussio=
ns into the error handling<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; sections.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; * Adoption of rfc2119 language throughou=
t to clarify the requirements.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; * Removal of some of the discussion arou=
nd more detailed justifications<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; for why particular decisions were made. =
I think this was useful through<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; the discussion phase of this draft, but =
it seems like GROW/IDR have<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; converged on a relatively stable set of =
requirements, so I have trimmed<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; back some of this discussion.<o:p></o:p>=
</p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; I'd really welcome any further comments =
on this before we re-submit for<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; publication. To eke these out - Peter/Ch=
ris - can you kick off a WGLC for<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; this draft please? :-)<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; Seasons greetings!<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; r.<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; ________________________________________=
_______<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; GROW mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"mailto:GROW@ietf.org"><span s=
tyle=3D"color:windowtext;text-decoration:none">GROW@ietf.org</span></a><o:p=
></o:p></p>
<p class=3D"MsoPlainText">&gt;&gt; <a href=3D"https://www.ietf.org/mailman/=
listinfo/grow"><span style=3D"color:windowtext;text-decoration:none">https:=
//www.ietf.org/mailman/listinfo/grow</span></a><o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt;_____________________________________________=
__<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;Idr mailing list<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt;<a href=3D"mailto:Idr@ietf.org"><span style=
=3D"color:windowtext;text-decoration:none">Idr@ietf.org</span></a><o:p></o:=
p></p>
<p class=3D"MsoPlainText">&gt;<a href=3D"https://www.ietf.org/mailman/listi=
nfo/idr"><span style=3D"color:windowtext;text-decoration:none">https://www.=
ietf.org/mailman/listinfo/idr</span></a><o:p></o:p></p>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>

--_000_53C29892C857584299CBF5D05346208A122AFBPEXCVZYM11corpora_--

From pds@lugs.com  Thu Jan 10 09:00:56 2013
Return-Path: <pds@lugs.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCAF521F89CB for <grow@ietfa.amsl.com>; Thu, 10 Jan 2013 09:00:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.998
X-Spam-Level: 
X-Spam-Status: No, score=-99.998 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 LaL2uDQp4bpO for <grow@ietfa.amsl.com>; Thu, 10 Jan 2013 09:00:56 -0800 (PST)
Received: from murdock.lugs.com (murdock.lugs.com [192.80.15.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAB121F8960 for <grow@ietf.org>; Thu, 10 Jan 2013 09:00:56 -0800 (PST)
Received: from r9m1fw1 (unknown [31.104.55.66]) by murdock.lugs.com (Postfix) with ESMTPSA id A81C3D35B0 for <grow@ietf.org>; Thu, 10 Jan 2013 12:00:54 -0500 (EST)
From: "Peter Schoenmaker" <pds@lugs.com>
To: <grow@ietf.org>
Date: Thu, 10 Jan 2013 17:00:47 -0000
Message-ID: <21ad01cdef54$0bd3be90$237b3bb0$@lugs.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_21AE_01CDEF54.0BD56C40"
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: Ac3vU7bG1lnetPGlT5S4hEWCaBQj2g==
Subject: [GROW] time slots for orlando ietf
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jan 2013 17:00:57 -0000

This is a multipart message in MIME format.

------=_NextPart_000_21AE_01CDEF54.0BD56C40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 

We have started to put together the agenda for the next IETF.  I would like
to ask if anyone would like to request a time slot to present.

 

Thanks

 

Peter

 

 


------=_NextPart_000_21AE_01CDEF54.0BD56C40
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>We have =
started to put together the agenda for the next IETF.&nbsp; I would like =
to ask if anyone would like to request a time slot to =
present.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Thanks<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Peter<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_21AE_01CDEF54.0BD56C40--


From chandra.appanna@yahoo.com  Mon Jan 14 18:37:30 2013
Return-Path: <chandra.appanna@yahoo.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D446711E809A for <grow@ietfa.amsl.com>; Mon, 14 Jan 2013 18:37:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_OBFU_Q1=0.227]
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 ANlWpAhMbRWi for <grow@ietfa.amsl.com>; Mon, 14 Jan 2013 18:37:29 -0800 (PST)
Received: from nm13.bullet.mail.bf1.yahoo.com (nm13.bullet.mail.bf1.yahoo.com [98.139.212.172]) by ietfa.amsl.com (Postfix) with SMTP id 8B1D021F8BBC for <grow@ietf.org>; Mon, 14 Jan 2013 18:37:28 -0800 (PST)
Received: from [98.139.212.145] by nm13.bullet.mail.bf1.yahoo.com with NNFMP; 15 Jan 2013 02:37:27 -0000
Received: from [98.139.212.200] by tm2.bullet.mail.bf1.yahoo.com with NNFMP; 15 Jan 2013 02:37:27 -0000
Received: from [127.0.0.1] by omp1009.mail.bf1.yahoo.com with NNFMP; 15 Jan 2013 02:37:27 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 836079.9419.bm@omp1009.mail.bf1.yahoo.com
Received: (qmail 22852 invoked by uid 60001); 15 Jan 2013 02:37:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1358217447; bh=LxEi3fGA1sPPkRzmIMCYtS+mTa1pbv8CcAvKVyLshxs=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=Ap4CMtSlCgElPp7FOrgtkmCZTevm9IhWmVURdxn4wLAhgEiNqBpJEnb4P6zF4s+5Bfu8rFoDk4ytrg07Daheqs7IgqRw9iGYLZd/Pi2wJJIOyKYbxOsqSsLcl/0dJ0VP4lMExtRDazp9n1fWNw6shDt5GSbtb58540CzD6pkvv8=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=6G1Oh4ckxn9Anm7u+Ah6IE5gZwB3WKPX8GRHsJiQxSpOQBUf3Z6pBVAZiiSug05cFHkJB29m5o079nptuRobv8SIp8X8AaUSzIMc1+3TNu7yBtUm3ySlNhTMhtsJcfJUx7lJQGaO4e0oULUMDAbwOfY0LwoL0xL0LAKlMMYvav4=;
X-YMail-OSG: MwGQtWsVM1mnExkxST_EzUqWZ3Mq._.gucF6b9QgF4cenIs N4yuXW_EnKJLtG2XJF1OkR6ACcihiN094AgIdQTwbqKYK43SW7PqMerMk17l oyZ8S06aPHx69t.8q7Vm8XVRKCtNsxXPak3rRUIB8qk_4T60Gnz5YMQsv5cI zs8QatPjdfSiiYDwJ9AaIV_elRj_dG7jsfmczwg.nlnglqyIm80qRA0vicjj oBobMUZLt7kjS7jORByYG0dpX6XjjE4A13_yzGYuJtksr.Ujc2piDJ7WuDVa EeVhbvNwG2fdOU1BbHx_hEVpqwEXQ05dZBNLo1xZ6_xnRzk_k5_az8Dd9FRt QKy60KoiIT.cYpV.USPUfpO3KF84qwCtPquEabFVSeh1uBVsPJphvmDyA.0o o145BOK63c5HMi1r7zASD0DmxrlqrW_xabuj8pMwcDouam6vPz.ngwa_oYip jNkbbY_7vH.HvmUvWN3q.6XDfUFLIiMqa.mH2J3YoySTg8Oh0Xbt.EQzyc.T _inkMBg2l.mJtsofHWgvpjy_q
Received: from [4.53.128.218] by web162901.mail.bf1.yahoo.com via HTTP; Mon, 14 Jan 2013 18:37:27 PST
X-Rocket-MIMEInfo: 001.001, UmF0aGVyIGxhdGUgcmVwbHkgb24gdGhpcyB0b3BpYy4uIEJ1dCBJIGhhcHBlbiB0byBhZ3JlZSB3aXRoIEphcmVkLgpJIGRpZCBzdGFydCBvdXQgdGhpbmtpbmcgdGhhdCB0aGUgYmdwIGVycm9yIGhhbmRsaW5nIGlkZWEgd2FzIGEgbmV3CnR3aXN0IG9mIGEgc29sdXRpb24gdGhhdCB3YXMgdmVyeSBpbnRlcmVzdGluZyBidXQgYWZ0ZXIgYWxsIHRoaXMgZGViYXRlCmFuZCBteSBvd24gaW50cm9zcGVjdGlvbiwgSSBhbSBhY3R1YWxseSBiYWNrIGluIHRoZSBjYW1wIG9mIG5vdCBiZWxpZXZpbmcKaW4gdGhlIGkBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.130.494
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <A29FF9DC-358E-4CD0-8931-D9B890CB8A6F@puck.nether.net>
Message-ID: <1358217447.9527.YahooMailNeo@web162901.mail.bf1.yahoo.com>
Date: Mon, 14 Jan 2013 18:37:27 -0800 (PST)
From: Chandra Appanna <chandra.appanna@yahoo.com>
To: Jared Mauch <jared@puck.nether.net>, Michael Long <mlong@us.ntt.net>
In-Reply-To: <A29FF9DC-358E-4CD0-8931-D9B890CB8A6F@puck.nether.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1846104760-87129825-1358217447=:9527"
X-Mailman-Approved-At: Mon, 14 Jan 2013 19:19:19 -0800
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Chandra Appanna <chandra.appanna@yahoo.com>
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 02:37:30 -0000

---1846104760-87129825-1358217447=:9527
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Rather late reply on this topic.. But I happen to agree with Jared.=0AI did=
 start out thinking that the bgp error handling idea was a new=0Atwist of a=
 solution that was very interesting but after all this debate=0Aand my own =
introspection, I am actually back in the camp of not believing=0Ain the ide=
a of soft corrections in the face of malformed updates and such=0Asituation=
s. I for one have not seen a lot of real data from the SPs and=0Aother newe=
rusers of BGP in my dealings of many years that reflect the need for=0Asuch=
 solutions in the real world. I do remain convinced that this is=0Astill a =
very interesting and challenging and 's..y' software and protocol=0Adevelop=
ment point but from a practical point of view I am not sure.=0AI have also =
seen discussions in development teams about how to structure=0Acode to hand=
le such treat-as-withdraw scenarios and it seems to me=0Athat it is very po=
ssible that it might only make code more fragile than robust.=0AIf only I h=
ad a penny for every time I thought I had written bug free=0Aautomatic bug =
handling code... :)=0A=0A0.02,=0AChandra.=0A=0A=0A=0A=0A___________________=
_____________=0A From: Jared Mauch <jared@puck.nether.net>=0ATo: Michael Lo=
ng <mlong@us.ntt.net> =0ACc: idr@ietf.org; grow@ietf.org; Tony Li <tony.li@=
tony.li> =0ASent: Thursday, January 3, 2013 11:58 AM=0ASubject: Re: [Idr] [=
GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt=0A=
 =0A=0AOn Jan 3, 2013, at 2:35 PM, Michael Long wrote:=0A=0A> =0A> On Jan 3=
, 2013, at 10:00 AM, Tony Li <tony.li@tony.li> wrote:=0A>> =0A>> =0A>> All =
of the marketing that you're doing here is positioning this as a 'solution'=
.=A0 It's not.=A0 Yes, it will stop the flap, but it does NOTHING to fix or=
 deal with the underlying bug.=A0 All it does is gloss it over, and as such=
, it will have implications in the field whereby this papers over real bugs=
 and we have now promoted BGP errors into RIB errors.=A0 That's NOT making =
things easier to debug, that's just applying a band-aid.=0A> =0A> I underst=
and what you are saying and I agree 100%, however, from an my operations pe=
rspective the "fix" is the same. Either upgrade to fixed code or policy out=
 the offending announcement. I would rather deal with a customer routing is=
sue vs a frantic call from our noc saying 15+ att peers globally are bounci=
ng. The latter being a much bigger impact on our network. =0A=0AI'm very co=
ncerned with the case of ignoring a route update and having a month-long di=
scussion about why some route is missing from the $carrier_a network when i=
t's being sent from $carrier_b and they show it going out just fine.=0A=0AY=
ou don't know there's an issue until someone reports it and your long-tail =
to problem resolution takes forever.=0A=0A> I can live with a couple of /24=
's not working for a few customers. I can't have 15+ peers bouncing because=
 of bad updates and even more peers bouncing because of missed keepalives d=
ue to cpu pegged trying to deal with 15 peers bouncing globally. =0A=0AWhil=
e related, this is an implementation defect on the part of vendors and thei=
r poorly optimized TCP and BGP implementations being unable to get their ba=
sic job done.=A0 I recall vendors blaming our "slow" system CPU then finall=
y fixing their logic defect that always returned 1 or 0 when it thought it =
was idle.=A0 (sometimes those if statements look really complex).=0A=0A>> A=
 more constructive way to address the real problem here would be to talk ab=
out whether we should even re-establish the session after an error.=A0 Long=
 ago, we made an implementation decision to simply retry.=A0 That would see=
m to be the real issue at hand.=0A> =0A> I would back this provided adequat=
e logging as to why the session is down. It would be much like tripping max=
-prefixes where we could hard clear a single single session for debug. I co=
uld live with this. =0A=0AI certainly agree there needs to be better loggin=
g from the vendors.=0A=0AI remain convinced that attempts to address this p=
roblem will create more complex situations vs provide the desired result of=
 a stable BGP core.=0A=0A- Jared=0A________________________________________=
_______=0AIdr mailing list=0AIdr@ietf.org=0Ahttps://www.ietf.org/mailman/li=
stinfo/idr
---1846104760-87129825-1358217447=:9527
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:Co=
urier New, courier, monaco, monospace, sans-serif;font-size:14pt"><span sty=
le=3D"font-size: 16px;">Rather late reply on this topic</span>.. <span styl=
e=3D"font-size: 16px;">But I happen to agree with Jared.<br>I did start out=
 thinking that the bgp error handling idea was a new<br>twist of a solution=
 that was very interesting but after all this debate<br>and my own introspe=
ction, I am actually back in the camp of not believing<br>in the idea of so=
ft corrections in the face of malformed updates and such<br>situations. I f=
or one have not seen a lot of real data from the SPs and<br>other newer use=
rs of BGP in my dealings of many years that reflect the need for<br>such so=
lutions in the real world. I do remain convinced that this is<br>still a ve=
ry interesting and challenging and 's..y' software and protocol<br>developm=
ent point but from a practical point of view I am not sure.<br>I have also
 seen discussions in development teams about how to structure<br>code to ha=
ndle such treat-as-withdraw scenarios and it seems to me<br>that it is very=
 possible that it might only make code more fragile than robust.<br>If only=
 I had a penny for every time I thought I had written bug free<br>automatic=
 bug handling code... :)<br><br>0.02,<br>Chandra.<br></span><div><span><br>=
</span></div><div><br></div>  <div style=3D"font-family: Courier New, couri=
er, monaco, monospace, sans-serif; font-size: 14pt;"> <div style=3D"font-fa=
mily: times new roman, new york, times, serif; font-size: 12pt;"> <div dir=
=3D"ltr"> <font face=3D"Arial" size=3D"2"> <hr size=3D"1">  <b><span style=
=3D"font-weight:bold;">From:</span></b> Jared Mauch &lt;jared@puck.nether.n=
et&gt;<br> <b><span style=3D"font-weight: bold;">To:</span></b> Michael Lon=
g &lt;mlong@us.ntt.net&gt; <br><b><span style=3D"font-weight: bold;">Cc:</s=
pan></b> idr@ietf.org; grow@ietf.org; Tony Li &lt;tony.li@tony.li&gt; <br> =
<b><span
 style=3D"font-weight: bold;">Sent:</span></b> Thursday, January 3, 2013 11=
:58 AM<br> <b><span style=3D"font-weight: bold;">Subject:</span></b> Re: [I=
dr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.t=
xt<br> </font> </div> <br><br>On Jan 3, 2013, at 2:35 PM, Michael Long wrot=
e:<br><br>&gt; <br>&gt; On Jan 3, 2013, at 10:00 AM, Tony Li &lt;<a ymailto=
=3D"mailto:tony.li@tony.li" href=3D"mailto:tony.li@tony.li">tony.li@tony.li=
</a>&gt; wrote:<br>&gt;&gt; <br>&gt;&gt; <br>&gt;&gt; All of the marketing =
that you're doing here is positioning this as a 'solution'.&nbsp; It's not.=
&nbsp; Yes, it will stop the flap, but it does NOTHING to fix or deal with =
the underlying bug.&nbsp; All it does is gloss it over, and as such, it wil=
l have implications in the field whereby this papers over real bugs and we =
have now promoted BGP errors into RIB errors.&nbsp; That's NOT making thing=
s easier to debug, that's just applying a band-aid.<br>&gt; <br>&gt; I
 understand what you are saying and I agree 100%, however, from an my opera=
tions perspective the "fix" is the same. Either upgrade to fixed code or po=
licy out the offending announcement. I would rather deal with a customer ro=
uting issue vs a frantic call from our noc saying 15+ att peers globally ar=
e bouncing. The latter being a much bigger impact on our network. <br><br>I=
'm very concerned with the case of ignoring a route update and having a mon=
th-long discussion about why some route is missing from the $carrier_a netw=
ork when it's being sent from $carrier_b and they show it going out just fi=
ne.<br><br>You don't know there's an issue until someone reports it and you=
r long-tail to problem resolution takes forever.<br><br>&gt; I can live wit=
h a couple of /24's not working for a few customers. I can't have 15+ peers=
 bouncing because of bad updates and even more peers bouncing because of mi=
ssed keepalives due to cpu pegged trying to deal with 15 peers
 bouncing globally. <br><br>While related, this is an implementation defect=
 on the part of vendors and their poorly optimized TCP and BGP implementati=
ons being unable to get their basic job done.&nbsp; I recall vendors blamin=
g our "slow" system CPU then finally fixing their logic defect that always =
returned 1 or 0 when it thought it was idle.&nbsp; (sometimes those if stat=
ements look really complex).<br><br>&gt;&gt; A more constructive way to add=
ress the real problem here would be to talk about whether we should even re=
-establish the session after an error.&nbsp; Long ago, we made an implement=
ation decision to simply retry.&nbsp; That would seem to be the real issue =
at hand.<br>&gt; <br>&gt; I would back this provided adequate logging as to=
 why the session is down. It would be much like tripping max-prefixes where=
 we could hard clear a single single session for debug. I could live with t=
his. <br><br>I certainly agree there needs to be better logging from
 the vendors.<br><br>I remain convinced that attempts to address this probl=
em will create more complex situations vs provide the desired result of a s=
table BGP core.<br><br>- Jared<br>_________________________________________=
______<br>Idr mailing list<br><a ymailto=3D"mailto:Idr@ietf.org" href=3D"ma=
ilto:Idr@ietf.org">Idr@ietf.org</a><br><a href=3D"https://www.ietf.org/mail=
man/listinfo/idr" target=3D"_blank">https://www.ietf.org/mailman/listinfo/i=
dr</a><br><br><br> </div> </div>  </div></body></html>
---1846104760-87129825-1358217447=:9527--

From nick@inex.ie  Tue Jan 15 07:57:19 2013
Return-Path: <nick@inex.ie>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7963B21F8623; Tue, 15 Jan 2013 07:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level: 
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
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 MENabYJjqBzr; Tue, 15 Jan 2013 07:57:19 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id A737921F8574; Tue, 15 Jan 2013 07:57:17 -0800 (PST)
X-Envelope-To: grow@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100::110]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id r0FFt3cT021724 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Jan 2013 15:55:09 GMT (envelope-from nick@inex.ie)
Message-ID: <50F57C56.5060501@inex.ie>
Date: Tue, 15 Jan 2013 15:57:10 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Chandra Appanna <chandra.appanna@yahoo.com>
References: <03c501cde845$54f82b30$fee88190$@highwayman.com> <04FA2CED-CC6E-486D-BCAF-2F1B37B0D778@puck.nether.net> <22E579A6-6732-476A-A0F7-4D9CB87E4069@tony.li> <CAPWAtb+ESwifB9UC5MnvzSHK=oz0xr9ObGoFnZBgNAUND2Po=Q@mail.gmail.com> <A62B8A46-0198-4D66-BD00-207688FD809E@tony.li> <CDCF89DF-1CA8-48C1-9224-90BA842BE87C@us.ntt.net> <A29FF9DC-358E-4CD0-8931-D9B890CB8A6F@puck.nether.net> <1358217447.9527.YahooMailNeo@web162901.mail.bf1.yahoo.com>
In-Reply-To: <1358217447.9527.YahooMailNeo@web162901.mail.bf1.yahoo.com>
X-Enigmail-Version: 1.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jan 2013 15:57:19 -0000

On 15/01/2013 02:37, Chandra Appanna wrote:
> I for one have not seen a lot of real data from the SPs and
> other newer users of BGP in my dealings of many years that reflect the need for
> such solutions in the real world.

Chandra,

This particular problem tends only to crop up every so often, but when it
happens, the results can be devastating on a global scale, causing
wide-scale outages across the entire Internet.  The last couple of times,
the problem has been caused by malformed attributes and has affect entire
products lines, e.g. all Junipers routers in the propagation path, or all
Cisco IOS boxes, or whatever.  Or better still, when you have one vendor
for your routers and another vendor for your RRs, you can be guaranteed of
failure until all your upstreams figure out some way of filtering out the
offending UPDATEs.  It is a very real and very serious problem.  There is
lots of noise about this on nanog-l.

Nick

From rjs@rob.sh  Mon Jan 28 10:49:27 2013
Return-Path: <rjs@rob.sh>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B613421F8718; Mon, 28 Jan 2013 10:49:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.372
X-Spam-Level: 
X-Spam-Status: No, score=-2.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 9+QhgehDwQgc; Mon, 28 Jan 2013 10:49:26 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id 158F321F8717; Mon, 28 Jan 2013 10:49:26 -0800 (PST)
Received: from [217.41.232.50] (helo=[10.10.3.134]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1TztiP-0008Tq-LL; Mon, 28 Jan 2013 18:45:57 +0000
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=windows-1252
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <31774_1357642629_50EBFB84_31774_520_1_53C29892C857584299CBF5D05346208A122AFB@PEXCVZYM11.corporate.adroot.infra.ftgroup>
Date: Mon, 28 Jan 2013 18:49:23 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD65B8BA-442A-4FA5-BCF7-FB44BD2954DE@rob.sh>
References: <CD024583.EA71%rob.shakir@bt.com> <B60B37DD-9A43-45B3-B8F4-5D4BF8475F6B@rob.sh> <31774_1357642629_50EBFB84_31774_520_1_53C29892C857584299CBF5D05346208A122AFB@PEXCVZYM11.corporate.adroot.infra.ftgroup>
To: bruno.decraene@orange.com
X-Mailer: Apple Mail (2.1499)
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jan 2013 18:49:27 -0000

Hi Bruno,

Thanks for the review of this version of the draft. I've added some =
feedback in-line as [rjs]. My apologies for the delay in responding.

On 8 Jan 2013, at 10:57, bruno.decraene@orange.com wrote:

> 1)  Critical error (=A73)
> =20
> IMHO, the term =93critical error=94 is mixing both technical/protocol =
considerations (e.g. can=92t read the update) and requirements =
considerations (BGP sessions state is too degraded and I prefer shutting =
it down rather than running on a degraded mode) which IMHO is =
unfortunate and does not help the discussion. I=92d much prefer that we =
distinguish both by defining technical levels of errors and then =
defining the requirements for each plus  the consequences/drawbacks of =
the decision (whether to keep or shut the session).
> For the protocol standpoint, I would propose the following level of =
errors, based on the protocol encoding layers: session, update, =
attribute.
> - attribute level error: semantic or syntax error in the attribute =
value or attribute flags
> - session level error: error in the update length / marker. i.e. if =
skipping the update length I can=92t find the marker of the next bgp =
message.
> - update level error: any other error in the update message
> =20
> We can further distinguish if the NLRIs can be parsed or not.

[rjs]: I would observe that there are two ways that we can consider how =
to classify errors here -- one based on the definition of the impact on =
the UPDATE of errors, and then one based on the reaction to those =
errors. The current draft (clearly) takes the latter approach for =
classification and reaction, however, as you say, it could be =
advantageous to classify the significance of the error to determine how =
"broken" the UPDATE is, and then map this to the possible approaches for =
handling the error.

[rjs]: If we were to take this approach -- then we could end up with a =
mapping of errors of:
	- For attribute-level errors, if it is not the NLRI-carrying =
attribute affected, then this is NLRI-level error handling, otherwise =
use session level error handling.
	- For session-level errors, only use session-level error =
handling.
	- For UPDATE-level errors, if the NLRI attribute can be parsed, =
then use error handling targeted to the NLRI, else handle it at a =
session level.
I am not clear where we would have UPDATE errors that do not fall within =
either the attribute, or session categories - do you have any example to =
help me understand? Also, do you envisage cases where there are =
session-level errors that we would map to any NLRI-level error handling?

[rjs]: It does sound advantageous to note the caveats of holding the =
session up for each type of error -- I will work to add a paragraph to =A7=
 3 that describes the motivation for wanting to hold the session up in =
some cases, and the drawbacks of doing so.


>  2)  Business Requirements
> In the current text, I found the requirements a bit too technically =
oriented. I=92d rather add business requirements independent of the =
current solutions. I would propose:
> =20
> In VPN networks, VPN are supposed to be isolated from each others and =
from the others services (most notably the Internet). Hence, an error on =
routes/BGP messages related to a VPN SHOULD NOT negatively impact others =
VPN. Similarly, an error on routes/BGP messages related to a non VPN =
service SHOULD not negatively impact the VPN service.
> In Internet networks, ASes are supposed to be Autonomous. Hence an =
error on routes/BGP messages originated by an AS SHOULD NOT negatively =
impact destinations originated from others ASes.
> =20
> By =93negatively impact=94, we mean losing reachability for a =
destination (NLRI), typically by losing all the paths in the Loc-RIB to =
that destination (NLRI). Note that those paths may be learnt through =
multiple BGP sessions and hence the requirement span multiple BGP =
sessions. The consequence is that if the BGP error is believed to be =
limited to a single BGP session (e.g. a session level error), then in a =
network with redundancy, the destination is believed to be still known =
through another session and hence the session MAY be chosen to be =
shutdown and all path learned from that session removed. On the =
contrary, if the BGP error has a chance to be also met on the redundant =
paths/sessions, then the BGP session and the routes learned from that =
session SHOULD be preserved, until the negatives consequences are =
considered too important. When evaluating those consequences, the fact =
that all redundant paths/sessions may suffer from the same error and =
hence will inherit the same decision MUST be considered.

[rjs]: I will go through and review this section to try and align it =
more with the service/business requirements for BGP deployments. It =
strikes me that the suggestion above is more related to an additional =
point that is not clearly included in this section around the different =
requirements for differing networks in which BGP is deployed. I would =
suggest that this is something that is added to the latter part of =A72, =
and the existing text remains. I'm keen that we provide some background =
as to *why* there is motivation for change in terms of deployment =
characteristics, as well as covering the business requirements you =
mention above.

> =20
> As an illustration, we typically seek to avoid that because of a =
single BGP error a PE lose both its redundant iBGP session with its BGP =
RR. And by =93a PE=94 I really mean all PE experiencing this condition. =
Could easily be 10s of PE, even 100s.
> =20
> 3)  Technical requirements
> For session level error, the BGP session is dead so need to be =
shutdown/graceful shutdown/graceful restart. If the update length is set =
to the number of octets sent to the peer (or vice versa) rather than =
computed based on the content of the update, there is a chance to 1) =
limit the number of such session level errors and 2) increase the =
probability that this error is local to that session and not likely to =
happen on a redundant/backup session. There is probably a limited part =
of the BGP code which needs to be hardened to reduce such unrecoverable =
errors. And if those errors are still frequent, we may further propose =
technical solutions (e.g. replacing TCP by SCTP which can provides =
message boundaries, among others things (e.g. some benefits of =
multi-sessions))
> =20
> For attribute & update level error when the NLRI can be parsed, cf =
draft-error-handling (treat as withdraw).

[rjs]: AIUI, if we added this requirement, then we could say that the =
total UPDATE length should be trusted as the "real" length of the =
transmitted UPDATE (which would be further validated by the subsequent =
presence of the marker). In this case, (and I expect we are getting =
towards draft-ietf-idr-error-handling here), then do you think that =
there is a capability required to indicate that an implementation has =
used this method of calculation? Without one, then we have the ambiguity =
of whether an implementation used this "trick" and hence are not clear =
whether we should trust it.

> Now let the discussion begin J. For attribute & update level error =
when the NLRI cannot be extracted IMHO there is room for discussion and =
analysis of the consequences.
> =20
> =93since the NLRI cannot be extracted, error handling mechanisms must =
be applied at the per-session level=94 (=A75)
> Well, IMO, this is a choice to be made rather than a =93must=94.

[rjs]: Do you envisage that this is a requirement in all scenarios, or a =
special case to be able to hold the session up following repeated =
errors? If during normal operation one tries to apply treat-as-withdraw, =
then this cannot be done (safely) unless we can determine to which NLRI =
this should be applied to. I'm unclear whether this not being a MUST =
(although at the moment it's a lower-case 'must') really implies that we =
have a requirement for a solution akin to the persistence draft as a =
"last resort" mechanism?

[rjs]: I think that this in-line with your later discussion -- =
essentially, the different levels as to how conservative one might want =
to be are very black and white at the current time (within the draft), =
as it's really whether you have these mechanisms "on", or "off". Is your =
suggestion that we evaluate more levels of error handling (i.e., include =
the "ignore all errors and continue operating") within this document, or =
is it an evaluation between the current on/off levels? Extending the =
draft to cover the "hold up" use case potentially expands it outside of =
BGP error handling that is applicable to most deployments of BGP into =
more special cases in my view. I'd like to understand whether the =
working group feels that this problem space falls within the scope of =
this draft.

Thanks,
r.

> If we were to skip a BGP update:
> For Internet, probably the worst case would be to miss a BGP update =
with a loop in the AS path and hence create a loop for me and my =
upstream ASes for the NLRI in the missed updated. How much probable is =
this? 0 for iBGP sessions. TBE for eBGP. Then what would be the =
consequences? loss of connectivity for the NLRI until the problem is =
manually solved by an AS between the origin and me, possible forwarding =
congestions for others. I=92m not sure I care too much about loosing =
reachability to NLRI in faulty BGP update as most likely, if only one =
BGP update (out of millions) is faulty, the reason may come from the =
origin AS playing with a specific bit or attribute and if they chose to =
play with their update, they should bear the responsibility. To be =
compared by the probability of losing all redundant paths (if the error =
is seen on redundant path) and the consequences (PE -possibly all PEs- =
down).
> =20
> For VPN, probably the worst case would be to keep a VPN label =
previously allocated to VPN 1 and re-allocated to another VPN (VPN =
breach Cf =
http://tools.ietf.org/html/draft-uttaro-idr-bgp-persistence-01#section-8)
> Again, the pro and con could be discussed (e.g. possibly one way =
partial VPN breach for some time (that basically no one can exploit) vs =
all VPN/PE being down. IMHO, if we believe such issue could be corrected =
in 30-60 minutes, I would probably favor keeping the session up.
> =20
> =46rom the lively discussions, looks like the opinions may vary =
depending on the AS, people and circumstances. E.g. how much my =
redundant BGP paths are failure independent? (e.g. use different BGP =
implementations)
> As such, what about defining severity levels for BGP error handling? =
As one may wish to accept only low severity errors while others may be =
willing to accept high severity errors (including when the NLRI cannot =
be found) e.g. the network has been down for 30 minutes, while waiting =
for the patch, one may want to be able to restore some service at all =
costs (can=92t possibly be worst).
> =20
> Again, IMHO it would be good to discuss the drawbacks depending on the =
situation (iBGP, eBGP; hop by hop routed, tunneled =85) in this =
requirement document to make sure we are all on the same page, we have =
constructive discussions and SP enabling revised error handling are =
fully aware of the consequences.
> =20
> 4)  Security consideration
> In =A77 =93security considerations=94 I would discuss the fact that =
current BGP error handling (or a (too) strict one) could be exploited by =
attackers to create a remote DOS attack.
> Should we also ask a review of the SIDR WG since =93The purpose of the =
SIDR working group is to reduce vulnerabilities in the inter-domain =
routing system.=94 ? ...
> =20
> Best regards,
> Bruno
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> =20
> >-----Original Message-----
> >From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of =
Rob
> >Shakir
> >Sent: Thursday, December 27, 2012 7:44 PM
> >To: idr@ietf.org
> >Subject: [Idr] Fwd: [GROW] I-D Action: =
draft-ietf-grow-ops-reqs-for-bgp-error-
> >handling-06.txt
> >=20
> >Hi IDR!
> >=20
> >FYI -- please find an updated relating to a new version of =
draft-ietf-grow-ops-
> >reqs-for-bgp-error-handling.
> >=20
> >Any comments very welcome (to me or grow@).
> >=20
> >Seasons greetings!
> >r.
> >=20
> >Begin forwarded message:
> >=20
> >> From: <rob.shakir@bt.com>
> >> Subject: Re: [GROW] I-D Action: =
draft-ietf-grow-ops-reqs-for-bgp-error-
> >handling-06.txt
> >> Date: 27 December 2012 18:41:50 GMT
> >> To: <internet-drafts@ietf.org>, <i-d-announce@ietf.org>
> >> Cc: grow@ietf.org
> >>=20
> >> On 27/12/2012 18:35, "internet-drafts@ietf.org" =
<internet-drafts@ietf.org>
> >> wrote:
> >>=20
> >>>=20
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >>> directories.
> >>> This draft is a work item of the Global Routing Operations Working =
Group
> >>> of the IETF.
> >>>=20
> >>>   Title           : Operational Requirements for Enhanced Error =
Handling
> >>> Behaviour in BGP-4
> >>>   Author(s)       : Rob Shakir
> >>>   Filename        : =
draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
> >>>   Pages           : 19
> >>>   Date            : 2012-12-27
> >>=20
> >> Hi GROW!
> >>=20
> >> This update is a fairly major re-spin of the BGP Error Handling
> >> requirements draft. The technical content should be as per the =
previous
> >> revisions however, following the ietf/RtgDir last call comments, I =
have
> >> made the following changes:
> >>=20
> >> * Made the amendments that were discussed and there was no =
disagreement
> >> with from our meeting in Atlanta -- this is essentially renaming =
the
> >> Critical/Semantic error types to Critical/Non-Critical.
> >>=20
> >> * Significant de-duplication within the text including merging the
> >> operational monitoring/toolset discussions into the error handling
> >> sections.
> >>=20
> >> * Adoption of rfc2119 language throughout to clarify the =
requirements.
> >>=20
> >> * Removal of some of the discussion around more detailed =
justifications
> >> for why particular decisions were made. I think this was useful =
through
> >> the discussion phase of this draft, but it seems like GROW/IDR have
> >> converged on a relatively stable set of requirements, so I have =
trimmed
> >> back some of this discussion.
> >>=20
> >> I'd really welcome any further comments on this before we re-submit =
for
> >> publication. To eke these out - Peter/Chris - can you kick off a =
WGLC for
> >> this draft please? :-)
> >>=20
> >> Seasons greetings!
> >> r.
> >>=20
> >> _______________________________________________
> >> GROW mailing list
> >> GROW@ietf.org
> >> https://www.ietf.org/mailman/listinfo/grow
> >=20
> >_______________________________________________
> >Idr mailing list
> >Idr@ietf.org
> >https://www.ietf.org/mailman/listinfo/idr
> =
__________________________________________________________________________=
_______________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations =
confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez =
recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les =
messages electroniques etant susceptibles d'alteration,
> France Telecom - Orange decline toute responsabilite si ce message a =
ete altere, deforme ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or =
privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
> As emails may be altered, France Telecom - Orange is not liable for =
messages that have been modified, changed or falsified.
> Thank you.
>=20


From bruno.decraene@orange.com  Tue Jan 29 03:11:48 2013
Return-Path: <bruno.decraene@orange.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166FB21F87F3; Tue, 29 Jan 2013 03:11:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, UNPARSEABLE_RELAY=0.001]
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 v8yGamWhzrjh; Tue, 29 Jan 2013 03:11:46 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 03FD621F87DF; Tue, 29 Jan 2013 03:11:45 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id A015B3242CB; Tue, 29 Jan 2013 12:11:44 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 8344823804B; Tue, 29 Jan 2013 12:11:44 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0318.004; Tue, 29 Jan 2013 12:11:44 +0100
From: <bruno.decraene@orange.com>
To: Rob Shakir <rjs@rob.sh>
Thread-Topic: [Idr] [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
Thread-Index: AQHN/YgyDXXczkGpk0WalTZDUDPs25hgBKBg
Date: Tue, 29 Jan 2013 11:11:43 +0000
Message-ID: <9382_1359457904_5107AE70_9382_708_1_53C29892C857584299CBF5D05346208A12C433@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <CD024583.EA71%rob.shakir@bt.com> <B60B37DD-9A43-45B3-B8F4-5D4BF8475F6B@rob.sh> <31774_1357642629_50EBFB84_31774_520_1_53C29892C857584299CBF5D05346208A122AFB@PEXCVZYM11.corporate.adroot.infra.ftgroup> <DD65B8BA-442A-4FA5-BCF7-FB44BD2954DE@rob.sh>
In-Reply-To: <DD65B8BA-442A-4FA5-BCF7-FB44BD2954DE@rob.sh>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.10.24.110314
Cc: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
Subject: Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 11:11:48 -0000

Hi Rob,

Thanks for your reply. More inline.

>From: Rob Shakir [mailto:rjs@rob.sh] >Sent: Monday, January 28, 2013 7:49 =
PM
>
>Hi Bruno,
>
>Thanks for the review of this version of the draft. I've added some feedba=
ck
>in-line as [rjs]. My apologies for the delay in responding.
>
>On 8 Jan 2013, at 10:57, bruno.decraene@orange.com wrote:
>
>> 1)  Critical error (=A73)
>>
>> IMHO, the term "critical error" is mixing both technical/protocol
>considerations (e.g. can't read the update) and requirements considerations
>(BGP sessions state is too degraded and I prefer shutting it down rather t=
han
>running on a degraded mode) which IMHO is unfortunate and does not help the
>discussion. I'd much prefer that we distinguish both by defining technical
>levels of errors and then defining the requirements for each plus  the
>consequences/drawbacks of the decision (whether to keep or shut the sessio=
n).
>> For the protocol standpoint, I would propose the following level of erro=
rs,
>based on the protocol encoding layers: session, update, attribute.
>> - attribute level error: semantic or syntax error in the attribute value=
 or
>attribute flags
>> - session level error: error in the update length / marker. i.e. if skip=
ping
>the update length I can't find the marker of the next bgp message.
>> - update level error: any other error in the update message
>>
>> We can further distinguish if the NLRIs can be parsed or not.
>
>[rjs]: I would observe that there are two ways that we can consider how to
>classify errors here -- one based on the definition of the impact on the U=
PDATE
>of errors, and then one based on the reaction to those errors.=20

[Bruno]: Indeed, but the point of the draft is discussing the requirements =
for those reactions, since we would like them to change.
If you define, at the very beginning of the draft, which errors are "critic=
al" and hence require a bgp session shut, then IMHO the discussion is close=
d and the draft done after those lines.

>The current
>draft (clearly) takes the latter approach for classification and reaction,
>however, as you say, it could be advantageous to classify the significance=
 of
>the error to determine how "broken" the UPDATE is, and then map this to the
>possible approaches for handling the error.
>
>[rjs]: If we were to take this approach -- then we could end up with a map=
ping
>of errors of:
>	- For attribute-level errors, if it is not the NLRI-carrying attribute
>affected, then this is NLRI-level error handling, otherwise use session le=
vel
>error handling.
>	- For session-level errors, only use session-level error handling.
>	- For UPDATE-level errors, if the NLRI attribute can be parsed, then use
>error handling targeted to the NLRI, else handle it at a session level.
>I am not clear where we would have UPDATE errors that do not fall within e=
ither
>the attribute, or session categories - do you have any example to help me
>understand?=20

[Bruno]:=20
- attribute-level error: the error is limited to an attribute (within a sin=
gle attribute). Example: "attribute low bits flags" set
- update-level error: I can't parse the next attributes in that update. Exa=
mple: RIP labs incident. The error is more than a single attribute, however=
 the session could still survive as session level length was ok.

>Also, do you envisage cases where there are session-level errors
>that we would map to any NLRI-level error handling?

[Bruno]: No. For session-level erros, I can't parse the current update nor =
any subsequent data, including next update.

>[rjs]: It does sound advantageous to note the caveats of holding the sessi=
on up
>for each type of error -- I will work to add a paragraph to =A7 3 that des=
cribes
>the motivation for wanting to hold the session up in some cases, and the
>drawbacks of doing so.

[Bruno]: Thank you.

>>  2)  Business Requirements
>> In the current text, I found the requirements a bit too technically orie=
nted.
>I'd rather add business requirements independent of the current solutions.=
 I
>would propose:
>>
>> In VPN networks, VPN are supposed to be isolated from each others and fr=
om
>the others services (most notably the Internet). Hence, an error on routes=
/BGP
>messages related to a VPN SHOULD NOT negatively impact others VPN. Similar=
ly,
>an error on routes/BGP messages related to a non VPN service SHOULD not
>negatively impact the VPN service.
>> In Internet networks, ASes are supposed to be Autonomous. Hence an error=
 on
>routes/BGP messages originated by an AS SHOULD NOT negatively impact
>destinations originated from others ASes.
>>
>> By "negatively impact", we mean losing reachability for a destination (N=
LRI),
>typically by losing all the paths in the Loc-RIB to that destination (NLRI=
).
>Note that those paths may be learnt through multiple BGP sessions and henc=
e the
>requirement span multiple BGP sessions. The consequence is that if the BGP
>error is believed to be limited to a single BGP session (e.g. a session le=
vel
>error), then in a network with redundancy, the destination is believed to =
be
>still known through another session and hence the session MAY be chosen to=
 be
>shutdown and all path learned from that session removed. On the contrary, =
if
>the BGP error has a chance to be also met on the redundant paths/sessions,=
 then
>the BGP session and the routes learned from that session SHOULD be preserv=
ed,
>until the negatives consequences are considered too important. When evalua=
ting
>those consequences, the fact that all redundant paths/sessions may suffer =
from
>the same error and hence will inherit the same decision MUST be considered.
>
>[rjs]: I will go through and review this section to try and align it more =
with
>the service/business requirements for BGP deployments. It strikes me that =
the
>suggestion above is more related to an additional point that is not clearly
>included in this section around the different requirements for differing
>networks in which BGP is deployed. I would suggest that this is something =
that
>is added to the latter part of =A72, and the existing text remains. I'm ke=
en that
>we provide some background as to *why* there is motivation for change in t=
erms
>of deployment characteristics, as well as covering the business requiremen=
ts
>you mention above.

[Bruno]: "Why" is good. But I wish we could also clarify/discuss what our (=
ultimate) goals/requirements are. Indeed, my proposition is service depende=
nt. But the reality is that BGP is used for different services/business and=
 hence the business requirements are per service.
The current draft is good, but other the time, most of its requirements are=
 now already covered with some proposed solution. Ideally, I'd like the doc=
ument to also pave the road for the future and future solutions.
IMHO, my above business requirements are reasonable, at least the VPN one. =
But they are still not covered by existing proposed solutions, nor the requ=
irement draft.

Regarding the organization of the draft, I would leave it to you.
I fine if this is added in the latter part of =A72.
2 comments:
- IMHO, I would rename "2. Problem Statement" into "2. Introduction" and "2=
.1. Role of BGP-4 in Service Provider Networks" into "3 Problem Statement".=
 And I would add the business requirements in last =A7.
- at the end of current =A72.1: "This document defines a set of requirement=
s for protocol developments"  I would propose :s/requirements/technical req=
uirements  (to make the distinction between business requirements which=20
are in this =A7 and the technical requirements in the next.

>>
>> As an illustration, we typically seek to avoid that because of a single =
BGP
>error a PE lose both its redundant iBGP session with its BGP RR. And by "a=
 PE"
>I really mean all PE experiencing this condition. Could easily be 10s of P=
E,
>even 100s.
>>
>> 3)  Technical requirements
>> For session level error, the BGP session is dead so need to be
>shutdown/graceful shutdown/graceful restart. If the update length is set t=
o the
>number of octets sent to the peer (or vice versa) rather than computed bas=
ed on
>the content of the update, there is a chance to 1) limit the number of such
>session level errors and 2) increase the probability that this error is lo=
cal
>to that session and not likely to happen on a redundant/backup session. Th=
ere
>is probably a limited part of the BGP code which needs to be hardened to r=
educe
>such unrecoverable errors. And if those errors are still frequent, we may
>further propose technical solutions (e.g. replacing TCP by SCTP which can
>provides message boundaries, among others things (e.g. some benefits of mu=
lti-
>sessions))
>>
>> For attribute & update level error when the NLRI can be parsed, cf draft-
>error-handling (treat as withdraw).
>
>[rjs]: AIUI, if we added this requirement, then we could say that the total
>UPDATE length should be trusted as the "real" length of the transmitted UP=
DATE
>(which would be further validated by the subsequent presence of the marker=
).=20

[Bruno]: correct. With possibly :s/"real"/specified

> In
>this case, (and I expect we are getting towards draft-ietf-idr-error-handl=
ing
>here), then do you think that there is a capability required to indicate t=
hat
>an implementation has used this method of calculation? Without one, then we
>have the ambiguity of whether an implementation used this "trick" and henc=
e are
>not clear whether we should trust it.

[Bruno]: So far, IMO, I don't see a need for a capability.
For the receiver: Update message length indicates where is located the next=
 update. We could see the marker as a check. Then either I can read the nex=
t update or not. Seems within the existing BGP spec. No trick.
For the sender: IMO clearly specifying that the receiver will use the updat=
e message length as the message delimiter, will put emphasize on making thi=
s field right (which seems doable to me as it's independent of the attribut=
es within the message. That's just the number of byte that I'm sending) oth=
erwise the session is dead.

>> Now let the discussion begin J. For attribute & update level error when =
the
>NLRI cannot be extracted IMHO there is room for discussion and analysis of=
 the
>consequences.
>>
>> "since the NLRI cannot be extracted, error handling mechanisms must be
>applied at the per-session level" (=A75)
>> Well, IMO, this is a choice to be made rather than a "must".
>
>[rjs]: Do you envisage that this is a requirement in all scenarios, or a
>special case to be able to hold the session up following repeated errors? =
If
>during normal operation one tries to apply treat-as-withdraw, then this ca=
nnot
>be done (safely) unless we can determine to which NLRI this should be appl=
ied
>to.=20

[Bruno]:
IMO if in some scenario, this tool is required to fulfill business requirem=
ents, we should not forbid it. Possibly combined with other tools to make i=
t safer.
That being said, I don't believe we will do the full work (analysis & solut=
ions) to address those business requirements. So let's start with a first p=
hase, and then we'll see if this is enough or not. So I'm fine with keeping=
 the session up even if some NLRI cannot be parsed, only for special cases =
manually enabled.

> I'm unclear whether this not being a MUST (although at the moment it's a
>lower-case 'must') really implies that we have a requirement for a solution
>akin to the persistence draft as a "last resort" mechanism?

To clarify, here I was referring to update level errors or MP attribute lev=
el errors where NLRI cannot be extracted.
The persistence draft would be for session level errors where the session c=
annot be re-established.=20

>[rjs]: I think that this in-line with your later discussion -- essentially=
, the
>different levels as to how conservative one might want to be are very blac=
k and
>white at the current time (within the draft), as it's really whether you h=
ave
>these mechanisms "on", or "off". Is your suggestion that we evaluate more
>levels of error handling (i.e., include the "ignore all errors and continue
>operating") within this document,=20

[Bruno]: yes. My suggestion was that we evaluate, or at least not forbid an=
d explicitly leave if for the future, other response to error condition. Sp=
ecifically session "hold up"

>or is it an evaluation between the current
>on/off levels? Extending the draft to cover the "hold up" use case potenti=
ally
>expands it outside of BGP error handling that is applicable to most deploy=
ments
>of BGP into more special cases in my view.=20

[Bruno]: rather than "more special cases", I'd say "type of BGP errors not =
yet widely faced"

>I'd like to understand whether the
>working group feels that this problem space falls within the scope of this
>draft.

[Bruno]: I believe that the error handling requirement should cover all cas=
es, otherwise this means that we don't have requirements for other cases (o=
k, more realistically, we don't want to bother thinking on hypothetical cas=
es). But I'm fine with leaving this as a next phase. In which case, IMO the=
 draft should not close the door but rather hint for a possible next phase.

Many thanks Rob. You picked a difficult work on a difficult subject.

Bruno

>Thanks,
>r.
>
>> If we were to skip a BGP update:
>> For Internet, probably the worst case would be to miss a BGP update with=
 a
>loop in the AS path and hence create a loop for me and my upstream ASes fo=
r the
>NLRI in the missed updated. How much probable is this? 0 for iBGP sessions=
. TBE
>for eBGP. Then what would be the consequences? loss of connectivity for the
>NLRI until the problem is manually solved by an AS between the origin and =
me,
>possible forwarding congestions for others. I'm not sure I care too much a=
bout
>loosing reachability to NLRI in faulty BGP update as most likely, if only =
one
>BGP update (out of millions) is faulty, the reason may come from the origi=
n AS
>playing with a specific bit or attribute and if they chose to play with th=
eir
>update, they should bear the responsibility. To be compared by the probabi=
lity
>of losing all redundant paths (if the error is seen on redundant path) and=
 the
>consequences (PE -possibly all PEs- down).
>>
>> For VPN, probably the worst case would be to keep a VPN label previously
>allocated to VPN 1 and re-allocated to another VPN (VPN breach Cf
>http://tools.ietf.org/html/draft-uttaro-idr-bgp-persistence-01#section-8)
>> Again, the pro and con could be discussed (e.g. possibly one way partial=
 VPN
>breach for some time (that basically no one can exploit) vs all VPN/PE bei=
ng
>down. IMHO, if we believe such issue could be corrected in 30-60 minutes, I
>would probably favor keeping the session up.
>>
>> From the lively discussions, looks like the opinions may vary depending =
on
>the AS, people and circumstances. E.g. how much my redundant BGP paths are
>failure independent? (e.g. use different BGP implementations)
>> As such, what about defining severity levels for BGP error handling? As =
one
>may wish to accept only low severity errors while others may be willing to
>accept high severity errors (including when the NLRI cannot be found) e.g.=
 the
>network has been down for 30 minutes, while waiting for the patch, one may=
 want
>to be able to restore some service at all costs (can't possibly be worst).
>>
>> Again, IMHO it would be good to discuss the drawbacks depending on the
>situation (iBGP, eBGP; hop by hop routed, tunneled .) in this requirement
>document to make sure we are all on the same page, we have constructive
>discussions and SP enabling revised error handling are fully aware of the
>consequences.
>>
>> 4)  Security consideration
>> In =A77 "security considerations" I would discuss the fact that current =
BGP
>error handling (or a (too) strict one) could be exploited by attackers to
>create a remote DOS attack.
>> Should we also ask a review of the SIDR WG since "The purpose of the SIDR
>working group is to reduce vulnerabilities in the inter-domain routing sys=
tem."
>? ...
>>
>> Best regards,
>> Bruno
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> >-----Original Message-----
>> >From: idr-bounces@ietf.org [mailto:idr-bounces@ietf.org] On Behalf Of R=
ob
>> >Shakir
>> >Sent: Thursday, December 27, 2012 7:44 PM
>> >To: idr@ietf.org
>> >Subject: [Idr] Fwd: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-
>error-
>> >handling-06.txt
>> >
>> >Hi IDR!
>> >
>> >FYI -- please find an updated relating to a new version of draft-ietf-g=
row-
>ops-
>> >reqs-for-bgp-error-handling.
>> >
>> >Any comments very welcome (to me or grow@).
>> >
>> >Seasons greetings!
>> >r.
>> >
>> >Begin forwarded message:
>> >
>> >> From: <rob.shakir@bt.com>
>> >> Subject: Re: [GROW] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-erro=
r-
>> >handling-06.txt
>> >> Date: 27 December 2012 18:41:50 GMT
>> >> To: <internet-drafts@ietf.org>, <i-d-announce@ietf.org>
>> >> Cc: grow@ietf.org
>> >>
>> >> On 27/12/2012 18:35, "internet-drafts@ietf.org" <internet-drafts@ietf=
.org>
>> >> wrote:
>> >>
>> >>>
>> >>> A New Internet-Draft is available from the on-line Internet-Drafts
>> >>> directories.
>> >>> This draft is a work item of the Global Routing Operations Working G=
roup
>> >>> of the IETF.
>> >>>
>> >>>   Title           : Operational Requirements for Enhanced Error Hand=
ling
>> >>> Behaviour in BGP-4
>> >>>   Author(s)       : Rob Shakir
>> >>>   Filename        : draft-ietf-grow-ops-reqs-for-bgp-error-handling-
>06.txt
>> >>>   Pages           : 19
>> >>>   Date            : 2012-12-27
>> >>
>> >> Hi GROW!
>> >>
>> >> This update is a fairly major re-spin of the BGP Error Handling
>> >> requirements draft. The technical content should be as per the previo=
us
>> >> revisions however, following the ietf/RtgDir last call comments, I ha=
ve
>> >> made the following changes:
>> >>
>> >> * Made the amendments that were discussed and there was no disagreeme=
nt
>> >> with from our meeting in Atlanta -- this is essentially renaming the
>> >> Critical/Semantic error types to Critical/Non-Critical.
>> >>
>> >> * Significant de-duplication within the text including merging the
>> >> operational monitoring/toolset discussions into the error handling
>> >> sections.
>> >>
>> >> * Adoption of rfc2119 language throughout to clarify the requirements.
>> >>
>> >> * Removal of some of the discussion around more detailed justificatio=
ns
>> >> for why particular decisions were made. I think this was useful throu=
gh
>> >> the discussion phase of this draft, but it seems like GROW/IDR have
>> >> converged on a relatively stable set of requirements, so I have trimm=
ed
>> >> back some of this discussion.
>> >>
>> >> I'd really welcome any further comments on this before we re-submit f=
or
>> >> publication. To eke these out - Peter/Chris - can you kick off a WGLC=
 for
>> >> this draft please? :-)
>> >>
>> >> Seasons greetings!
>> >> r.
>> >>
>> >> _______________________________________________
>> >> GROW mailing list
>> >> GROW@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/grow
>> >
>> >_______________________________________________
>> >Idr mailing list
>> >Idr@ietf.org
>> >https://www.ietf.org/mailman/listinfo/idr
>>
>__________________________________________________________________________=
_____
>__________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations
>confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez r=
ecu
>ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>electroniques etant susceptibles d'alteration,
>> France Telecom - Orange decline toute responsabilite si ce message a ete
>altere, deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and d=
elete
>this message and its attachments.
>> As emails may be altered, France Telecom - Orange is not liable for mess=
ages
>that have been modified, changed or falsified.
>> Thank you.
>>


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete al=
tere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for message=
s that have been modified, changed or falsified.
Thank you.

