IETF Logo Mail Archive

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

Christopher Morrow <morrowc.lists@gmail.com> Wed, 12 December 2012 18:48 UTC

Return-Path: <christopher.morrow@gmail.com>
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 2480221F881A for <idr@ietfa.amsl.com>; Wed, 12 Dec 2012 10:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ex8EusFSPn-K for <idr@ietfa.amsl.com>; Wed, 12 Dec 2012 10:48:20 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id C6DB021E8109 for <idr@ietf.org>; Wed, 12 Dec 2012 10:48:19 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so362937eaa.31 for <idr@ietf.org>; Wed, 12 Dec 2012 10:48:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=/xrrHfvjYdX100D1EInlDzwwTApl7xh/KvDRCKbZ9rE=; b=tEo+2ln9ZNNEoXDz1vdk6Tf1TImHeHgEyVGCfBxZu7HlyNHOGe24a5///jt0i7cn82 ASldGV73yBsMaZ+7X5Zd82brFtkXN7SYfvYJOKSk4qC1MT8eAaSDqrckJzRxNu0fErq1 nbK2iMS/qBOyKoXWrb63FAhXNosOhTXFLjDQcHq/ulMtGB1qFVNHPWQUCPMTXXZb8jfl jeFay/M9PV6BDUWoK9K5OhDFAYfiQTI35mADc1ee3KcmrrjlB5oN3A1M/3toDC3jj3qh TZ6TAP/Xth5LRyO7ogasNaAyp9K7bPD7T1KW/j+pXMkVE6/LcVD5WmapW+9WtalrUC03 dmXA==
MIME-Version: 1.0
Received: by 10.14.202.3 with SMTP id c3mr5091375eeo.4.1355338098816; Wed, 12 Dec 2012 10:48:18 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.223.177.5 with HTTP; Wed, 12 Dec 2012 10:48:18 -0800 (PST)
In-Reply-To: <CA+b+ER=tp+tdmNomjAXpaRBG8cYNo1SybAr1WoJ9frBUSGoOrg@mail.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> <CAH1iCiqfZRLv2pBEg3gKxT=ZXf7AXCPJ_+QibOpgeFfOuqFK7g@mail.gmail.com> <50C8CE86.10103@umn.edu> <50C8CF69.4070202@foobar.org> <CA+b+ER=tp+tdmNomjAXpaRBG8cYNo1SybAr1WoJ9frBUSGoOrg@mail.gmail.com>
Date: Wed, 12 Dec 2012 13:48:18 -0500
X-Google-Sender-Auth: 0nICYV8EUW_ijxPde5aLd1ZL7ds
Message-ID: <CAL9jLaaenLrpG7Rw2N2+CpBXmazS+tufa_2UZAHJT-GOn580Fw@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Content-Type: text/plain; charset="ISO-8859-1"
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 18:48:21 -0000

On Wed, Dec 12, 2012 at 1:43 PM, Robert Raszuk <robert@raszuk.net> wrote:
> Are you putting this regex in today ?
>
> Otherwise the sooner this goes through your vendors will be able to
> provide you one keyword match for the new private AS range in the
> policy language of your choice.
>
> So I can't quite see what's the point of this regex debate now ....

to rephrase, I think Robert is asking: "Would you not just ask your
vendor to include a macro like: 'PrivateASNGroup' to match on in
routing policy language?"

seems reasonable... except that my SFO router may not get upgraded at
the same as my NYC router, nevermind fast-mover Nick over there who's
always happy to load nightly code on his elbonian routers... so do we
have to delay usage of this new shiny space until reasonably close to
all public bgp speakers upgrade? Or build a mechanism like AS4
required for as2 only realms stuck in the middle of the AS4 world?

v2.31.3 | Report a Bug | By Email | System Status