IETF Logo Mail Archive

Re: [Idr] Revised text on how to construct the AS path info

Enke Chen <enkechen@cisco.com> Thu, 13 October 2005 06:29 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPwaq-0005MQ-K9; Thu, 13 Oct 2005 02:29:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPwan-0005MA-6b for idr@megatron.ietf.org; Thu, 13 Oct 2005 02:29:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27266 for <idr@ietf.org>; Thu, 13 Oct 2005 02:29:24 -0400 (EDT)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPwlF-0000XT-0v for idr@ietf.org; Thu, 13 Oct 2005 02:40:18 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 12 Oct 2005 23:29:19 -0700
X-IronPort-AV: i="3.97,209,1125903600"; d="scan'208"; a="665743126:sNHT24563204"
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j9D6T39E026061; Wed, 12 Oct 2005 23:29:16 -0700 (PDT)
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Oct 2005 23:29:14 -0700
Received: from [10.21.123.14] ([10.21.123.14]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Oct 2005 23:29:14 -0700
Message-ID: <434DFEB9.4090307@cisco.com>
Date: Wed, 12 Oct 2005 23:29:13 -0700
From: Enke Chen <enkechen@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: [Idr] Revised text on how to construct the AS path info
References: <200510071641.j97GfgG21459@merlot.juniper.net> <Pine.LNX.4.63.0510100013110.3396@sheen.jakma.org> <434ABA2C.1070608@cisco.com> <434C66AC.7080506@cisco.com> <20051012205713.GD27304@verdi>
In-Reply-To: <20051012205713.GD27304@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Oct 2005 06:29:14.0066 (UTC) FILETIME=[6DF8EB20:01C5CFBF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
Cc: idr@ietf.org
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Sender: idr-bounces@ietf.org
Errors-To: idr-bounces@ietf.org

Hi, John:

What types of "inconsistencies" between AS_PATH and NEW_AS_PATH you are 
concerned about, beyond the one described in the Transition Section 
(Please see my reply to Paul on that one)?

If your concern is about bogus AS path info somehow got propagated 
around, that seems to be a general issue, independent of the 4byte AS.

-- Enke

John Leslie wrote:

[snip]

>   It's very important to be clear that the AS_PATH "length" MUST be
>the same as the AS_PATH received from the OLD BGP speaker.
>
>   This algorithm should be appropriate, provided a reasonable test
>for consistency between AS_PATH and NEW_AS_PATH is performed. (I'd
>be happy to discuss my ideas for such a test.)
>
>   I think we need to add a provision that the NLRI MAY (or even
>SHOULD) be discarded if the two are inconsistent.
>  
>

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

v2.23.0 | Report a Bug | By Email