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

John Leslie <john@jlc.net> Wed, 12 October 2005 20:57 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPnf3-0005vv-3Q; Wed, 12 Oct 2005 16:57:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPnf1-0005vq-Fj for idr@megatron.ietf.org; Wed, 12 Oct 2005 16:57:15 -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 QAA05094 for <idr@ietf.org>; Wed, 12 Oct 2005 16:57:12 -0400 (EDT)
Received: from mailhost.jlc.net ([199.201.159.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPnpO-00050M-BC for idr@ietf.org; Wed, 12 Oct 2005 17:07:59 -0400
Received: by mailhost.jlc.net (Postfix, from userid 104) id 53E8FE04CF; Wed, 12 Oct 2005 16:57:13 -0400 (EDT)
Date: Wed, 12 Oct 2005 16:57:13 -0400
From: John Leslie <john@jlc.net>
To: Enke Chen <enkechen@cisco.com>
Subject: Re: [Idr] Revised text on how to construct the AS path info
Message-ID: <20051012205713.GD27304@verdi>
References: <200510071641.j97GfgG21459@merlot.juniper.net> <Pine.LNX.4.63.0510100013110.3396@sheen.jakma.org> <434ABA2C.1070608@cisco.com> <434C66AC.7080506@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <434C66AC.7080506@cisco.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: idr@ietf.org, Paul Jakma <paul@clubi.ie>
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

Enke Chen <enkechen@cisco.com> wrote:
> 
> Attached is the revised text on how to construct the AS path information.

   I welcome this clarification. It's much easier to determine whether
a particular algorithm matches this description.

> Please comment if you see any issue.
> ----------------------------------------------------------------------
> 
> The exact AS path information can be constructed by taking as many AS
> numbers and path segments as necessary from the leading part of the
> AS_PATH attribute,

   This much is clearly correct.

> and then prepending them to the NEW_AS_PATH attribute so that the
> AS path information has an identical number of AS numbers as the
> AS_PATH attribute.

   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.

> The number of AS numbers is calculated...

   I'd prefer not to comment on this part: I haven't examined it in
detail. At first blush, it looks right.

--
John Leslie <john@jlc.net>

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