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

Jeffrey Haas <jhaas@pfrc.org> Mon, 15 December 2008 20:23 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 9D5B528C124; Mon, 15 Dec 2008 12:23:15 -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 E783928C12C for <idr@core3.amsl.com>; Mon, 15 Dec 2008 12:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level:
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 hNahAPh2j-9n for <idr@core3.amsl.com>; Mon, 15 Dec 2008 12:23:13 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by core3.amsl.com (Postfix) with ESMTP id 4F3C828C122 for <idr@ietf.org>; Mon, 15 Dec 2008 12:23:13 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 2CA91244051; Mon, 15 Dec 2008 20:22:54 +0000 (UTC)
Date: Mon, 15 Dec 2008 15:22:54 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Enke Chen <enkechen@cisco.com>
Message-ID: <20081215202254.GC13757@slice>
References: <CD705FABA8532448AA1FB7A96C88FF140898F8A4@emailbng1.jnpr.net> <4D86C4C6-F7CD-46B9-ABBE-04530F4D1278@juniper.net> <164BE5B4-1A18-42D7-A11B-DE2056890C78@tcb.net> <4946AC94.2080605@cisco.com> <5340D990-F446-4C37-8307-1DB31ADF2273@tcb.net> <4946B996.4040907@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4946B996.4040907@cisco.com>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
Cc: Inter-Domain Routing List <idr@ietf.org>, quaizar.vohra@gmail.com, Danny McPherson <danny@tcb.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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Mon, Dec 15, 2008 at 12:09:58PM -0800, Enke Chen wrote:
> Again, I do not see any reason why RFC 4893 should be different from RFC 
> 5056 w.r.t. the processing of unexpected confed segments.

Orthogonal to the "could we do something better about it" discussion:
In 5065, the pain is isolated to an adjacent peering edge.
In 4893, the pain originates far away.

The penalty for pedantically obeying the spec is higher.  We saw this
even for something as simple as the motivation for the 5065 rewrite.

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