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

"Chris Hall" <chris.hall@highwayman.com> Sun, 09 December 2012 22:57 UTC

Return-Path: <chris.hall@highwayman.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7959821F8D3C for <idr@ietfa.amsl.com>; Sun, 9 Dec 2012 14:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level:
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311]
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 GL3LZYyxi+ts for <idr@ietfa.amsl.com>; Sun, 9 Dec 2012 14:57:11 -0800 (PST)
Received: from smtp.demon.co.uk (mdfmta009.mxout.tch.inty.net [91.221.169.50]) by ietfa.amsl.com (Postfix) with ESMTP id C431421F8CE2 for <idr@ietf.org>; Sun, 9 Dec 2012 14:57:10 -0800 (PST)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1]) by mdfmta009.tch.inty.net (Postfix) with ESMTP id 4AD3512840D; Sun, 9 Dec 2012 22:57:09 +0000 (GMT)
Received: from mdfmta009.tch.inty.net (unknown [127.0.0.1]) by mdfmta009.tch.inty.net (Postfix) with ESMTP id 1FB0C12840C; Sun, 9 Dec 2012 22:57:09 +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.tch.inty.net (Postfix) with ESMTP; Sun, 9 Dec 2012 22:57:08 +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 1Thpo4-0005fi-8m; Sun, 09 Dec 2012 22:57:08 +0000
From: Chris Hall <chris.hall@highwayman.com>
To: idr@ietf.org
References: <20121121191321.6164.6887.idtracker@ietfa.amsl.com> <50AD2986.90705@cisco.com> <058b01cdd3b4$9f5193b0$ddf4bb10$@highwayman.com> <8ED5B0B0F5B4854A912480C1521F973A0F4940@xmb-rcd-x13.cisco.com> <94913EE5-2864-4EE2-B474-9631430B1E22@ericsson.com> <068701cdd478$2cf01cf0$86d056d0$@highwayman.com> <CAEGVVtBy-zdLz8hVajLnuAqgzfgQHrseK4r-N9=pOZGtqV7LbA@mail.gmail.com> <CAH1iCipfup-GEeJduBti_KHvX1pUZfmZLA3Zz5Y9Aw9xV3fQ9w@mail.gmail.com> <079901cdd601$9901b630$cb052290$@highwayman.com> <50C4D7EC.4070309@cisco.com> <CAH1iCiok=sp6=X0ZSAMqHHHCgM4z--tiTpLyKnze64c5M0ck3A@mail.gmail.com>
In-Reply-To: <CAH1iCiok=sp6=X0ZSAMqHHHCgM4z--tiTpLyKnze64c5M0ck3A@mail.gmail.com>
Date: Sun, 09 Dec 2012 22:57:01 -0000
Organization: Highwayman
Message-ID: <07de01cdd660$83c28420$8b478c60$@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: AQHwJ9rDNhpCAk7gfRWZlMlTSLUu6QFwpw6KAjDRnx0CVlUcVAFHaBeAARUnQBoBYBPk8QGYNqrRAQ+Sq64BU0/mmgIDSabIl07VpzA=
Content-Language: en-gb
X-MDF-HostID: 22
Subject: Re: [Idr] I-D Action: draft-ietf-idr-error-handling-03.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Dec 2012 22:57:13 -0000

Brian Dickson wrote (on Sun 09-Dec-2012 at 20:20 +0000)
>
> What Chris is proposing is a negotiated option where the
> sender COMMITS to observing the specified order in which
> to send the attributes.
>
> Without that negotiated option, there is no method of
> influencing the sender's behavior. 

It would be straightforward for a BGP implementation to always use the
specified order, and always announce the "capability" -- this is
essentially unilateral.

The key thing is that receivers who understand the significance of the
capability can factor that into their error handling strategy.  (And
receivers who do not understand the capability can simply ignore it.)

> This is not to say that SOME senders won't use that order.

Indeed, in the absence of the capability, the receiver has to assume
that attributes may be sent in any order (as per current RFC)...

> However, any implementation that supports this new
> option negotiation, and either defaults to or exposes
> a "knob" for enabling it, will then need to use the
> SPECIFIC order to be compliant.

...or have some "knob" to force it to assume something else.

Chris