Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00

Nick Hilliard <nick@foobar.org> Wed, 12 December 2012 21:08 UTC

Return-Path: <nick@foobar.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B99EB21E8037 for <idr@ietfa.amsl.com>; Wed, 12 Dec 2012 13:08:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D2Y+0W5RZVG4 for <idr@ietfa.amsl.com>; Wed, 12 Dec 2012 13:08:42 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id F255521E8034 for <idr@ietf.org>; Wed, 12 Dec 2012 13:08:41 -0800 (PST)
X-Envelope-To: idr@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:79d2:636d:2532:9d2f]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBCL72tV050581 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 12 Dec 2012 21:07:08 GMT (envelope-from nick@foobar.org)
Message-ID: <50C8F252.4000706@foobar.org>
Date: Wed, 12 Dec 2012 21:08:34 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian Dickson <brian.peter.dickson@gmail.com>
References: <CA+b+ERnuWZ+r2O-eFhe3hU00uoU4UKnRcbhLNVXU7p5+DjoWbQ@mail.gmail.com> <C6C16AE3B7961044B04A1BCEC6E2F93603D12A0C@xmb-rcd-x14.cisco.com> <20121210225858.GC24937@puck.nether.net> <m2d2yh32cw.wl%randy@psg.com> <CA+b+ERnSVvewSpftXs3FhW12-S+sgnB1SwD4L+xqFW+hhbQayw@mail.gmail.com> <7120600D-71BD-4E61-8F06-25B7C2BAE6A8@riw.us> <20121211185917.GA21813@puck.nether.net> <CA+b+ERnzo2BLWjE1J_dMfYuExbG9WYJroPE4ZAWg++KK2_jy1g@mail.gmail.com> <CA+b+ERm=Agr7b6JXcXOwiP4wBjnEFmnVNt5fAJrn18R0hGtSzg@mail.gmail.com> <50C78C29.3070406@foobar.org> <50C8B8D9.4090903@umn.edu> <50C8C491.4040705@foobar.org> <CAH1iCio8Sh_ASLAa8DOcVXa5n19LgCAnSwTQV9edn2On1KPJbw@mail.gmail.com>
In-Reply-To: <CAH1iCio8Sh_ASLAa8DOcVXa5n19LgCAnSwTQV9edn2On1KPJbw@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: IETF IDR Working Group <idr@ietf.org>
Subject: Re: [Idr] WGLC on draft-ietf-idr-as-private-reservation-00
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 12 Dec 2012 21:08:42 -0000

On 12/12/2012 18:52, Brian Dickson wrote:
> Okay, in as-plain, here goes:

ah, thanks - that's saved me the bother of sitting down and exercising the
grey matter of an evening.  In fact you can optimise it by taking
characters out from the front, which I've done below.  On some systems with
recursive RE libs, you can do more of this and shorter the RE string.  On
other RE libs which support specifying the atom instance count, you can
replace sequences of dots with squiggly braces, but that won't help much
with readability and it's not portable across all of the various vendor
regexp libs (and it will just make it look like modem-induced line-noise).
 I've taken out the 42 and cut-n-pasted it into a cisco router, and it now
looks like this:

> ip as-path access-list 499 permit _42(781900[8-9].|78190[1-9]..|7819[1-9]...|78[2-9].....|79......|8.......|9[0-3]......|94[0-8].....|949[0-5]....|9496[0-6]...|94967[0-1]..|949672[0-8].|9496729[0-4])_

It will be similar but not the same on other vendors.

If we aim for a decimal-aligned system, in the worst case this is reduced to:

> ip as-path access-list 499 permit _XXX......._

... for some simple numeric value of XXX.

I know which regular expression I'd prefer to deal with.

Nick