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

"John G. Scudder" <jgs@juniper.net> Tue, 16 December 2008 21:01 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 6A2F328C180; Tue, 16 Dec 2008 13:01:08 -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 624D328C180 for <idr@core3.amsl.com>; Tue, 16 Dec 2008 13:01:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.481
X-Spam-Level:
X-Spam-Status: No, score=-6.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 KK4Mp8rULRjb for <idr@core3.amsl.com>; Tue, 16 Dec 2008 13:01:06 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by core3.amsl.com (Postfix) with ESMTP id 5550728C186 for <idr@ietf.org>; Tue, 16 Dec 2008 13:01:06 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKSUgXB2mXHZAwIbPYqgqrpNWba6TgUWIE@postini.com; Tue, 16 Dec 2008 13:00:59 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.311.2; Tue, 16 Dec 2008 12:58:47 -0800
Received: from p-emlb01-sac.jnpr.net ([66.129.254.46]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 12:58:47 -0800
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Dec 2008 12:58:46 -0800
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Dec 2008 12:58:46 -0800
Received: from [172.16.13.200] ([172.16.13.200]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id mBGKwjM07947; Tue, 16 Dec 2008 12:58:46 -0800 (PST) (envelope-from jgs@juniper.net)
Message-ID: <F5B1A3A0-C1DA-4370-9051-0F12E46B0EAD@juniper.net>
From: "John G. Scudder" <jgs@juniper.net>
To: Paul Jakma <paul@clubi.ie>
In-Reply-To: <alpine.LFD.2.00.0812161618080.5839@localhost.localdomain>
MIME-Version: 1.0 (Apple Message framework v929.2)
Date: Tue, 16 Dec 2008 15:58:44 -0500
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> <A35E9CEC-BC77-4CDF-AF3D-1ECFE63D8FD3@tcb.net> <4946F36B.8050903@cisco.com> <alpine.LFD.2.00.0812160932000.5839@localhost.localdomain> <20081216140212.GA55748@verdi> <alpine.LFD.2.00.0812161618080.5839@localhost.localdomain>
X-Mailer: Apple Mail (2.929.2)
X-OriginalArrivalTime: 16 Dec 2008 20:58:46.0575 (UTC) FILETIME=[166403F0:01C95FC1]
Cc: Inter-Domain Routing List <idr@ietf.org>
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

On Dec 16, 2008, at 12:07 PM, Paul Jakma wrote:
> b) It's no doubt implied, but perhaps any RFCbis should make it clear
>   that AS_TRANS MUST be considered to match all ASNs > 65535 when
>   doing AS-Path (in the abstract) loop detection.

Seems to me that this is not required in order to preserve the loop  
free property. We have two possible cases:

1. All the ASes in the path are 4-byte capable, in which case the  
issue does not exist.
2. At least one AS in the path is not 4-byte capable. In that case, if  
there is a loop it will eventually be caught by the regular 2-byte  
AS_PATH.

In neither case is what you describe needed, AFAICT.

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