IETF Logo Mail Archive

Re: [Idr] RFC-4893 handling malformed AS4_PATH attributes

cayle.spandon@gmail.com Mon, 15 December 2008 17:51 UTC

Return-Path: <idr-bounces@ietf.org>
X-Original-To: idr-archive@megatron.ietf.org
Delivered-To: ietfarch-idr-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1F673A6804; Mon, 15 Dec 2008 09:51:43 -0800 (PST)
X-Original-To: idr@core3.amsl.com
Delivered-To: idr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DFB23A6804 for <idr@core3.amsl.com>; Mon, 15 Dec 2008 09:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level:
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N+yMHk76gbUj for <idr@core3.amsl.com>; Mon, 15 Dec 2008 09:51:41 -0800 (PST)
Received: from mail-gx0-f70.google.com (mail-gx0-f70.google.com [209.85.217.70]) by core3.amsl.com (Postfix) with ESMTP id B25203A67F7 for <idr@ietf.org>; Mon, 15 Dec 2008 09:51:41 -0800 (PST)
Received: by gxk22 with SMTP id 22so2002042gxk.5 for <idr@ietf.org>; Mon, 15 Dec 2008 09:51:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.99.5 with SMTP id w5mr2319902agb.7.1229363493845; Mon, 15 Dec 2008 09:51:33 -0800 (PST)
Message-ID: <0016361e883459ba8b045e197e41@google.com>
Date: Mon, 15 Dec 2008 17:51:33 +0000
From: cayle.spandon@gmail.com
To: Danny McPherson <danny@tcb.net>, "John G. Scudder" <jgs@juniper.net>, Enke Chen <enkechen@cisco.com>, quaizar.vohra@gmail.com, skh@nexthop.com, Inter-Domain Routing List <idr@ietf.org>, Yakov Rekhter <yakov@juniper.net>, Tony Li <tony.li@tony.li>, Quaizar Vohra <qv@juniper.net>
Subject: Re: [Idr] RFC-4893 handling malformed AS4_PATH attributes
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0445118657=="
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

> While I agree that we don't ever want to ignore updates or provide
> non-deterministic behavior

Note that in this case the decoding of the update got far enough to be able  
to identify the individual routes in the update.

Because of this an alternative is available: instead of ignoring the  
update, we can treat these "illegal" routes as unusable, ie no different  
than -say- a route with an unreachable next-hop.

This will lead to perfectly deterministic behavior, eg pick another route  
to the same prefix as the best route, or if no alternative is available,  
send out withdraws.

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email