Re: [rrg] procedural aggregation

William Herrin <bill@herrin.us> Wed, 05 March 2014 18:53 UTC

Return-Path: <wherrin@gmail.com>
X-Original-To: rrg@ietfa.amsl.com
Delivered-To: rrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E64CF1A0162 for <rrg@ietfa.amsl.com>; Wed, 5 Mar 2014 10:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Udf-aBL6VZLI for <rrg@ietfa.amsl.com>; Wed, 5 Mar 2014 10:53:31 -0800 (PST)
Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 95EC61A02A4 for <rrg@irtf.org>; Wed, 5 Mar 2014 10:53:18 -0800 (PST)
Received: by mail-ve0-f171.google.com with SMTP id cz12so1519409veb.30 for <rrg@irtf.org>; Wed, 05 Mar 2014 10:53:14 -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:from:date:message-id :subject:to:cc:content-type; bh=MmjAeB5xXk/HfGop54Px/JyPJrjG2uUB+tcolSGj958=; b=CouYZOfjx93h8jpYhDZUKNM4KM6/TIvue3SQslUJITKGdoJZFp2xjBhh48m0IDYhlO ipZGScY/w/7bNHSe58/lChm9f8EGg0n/JPIYpx2rlKC/qrBxqHmdRrmLF6geeCzm5dtL pZo3ZBgIY5byPPEJOlSsW6Fw44pNF7ba87GcTXw/6uQfqA3WSiF4Qv7Jj7eI7qX1tlLP Ly/oW1Ox6FlBoacS8nAz1eJJg730JfVh0Qaz1UYWDQTjPoz3Z54rVrqQJgrlGaE2/fkN lYPW4nDujqdRHv0jqw8uz05DcWXqUH9dPlCNqna+seu0z7qdlwyxgGnRtUP4+lFoXYGS x8dA==
X-Received: by 10.58.229.4 with SMTP id sm4mr1473164vec.10.1394045594766; Wed, 05 Mar 2014 10:53:14 -0800 (PST)
MIME-Version: 1.0
Sender: wherrin@gmail.com
Received: by 10.52.38.234 with HTTP; Wed, 5 Mar 2014 10:52:54 -0800 (PST)
In-Reply-To: <53176AF6.1040308@joelhalpern.com>
References: <CAP-guGXyxehmCiskATSLOouE0Cx1i9KFroK60r=xWe-Lu7peSA@mail.gmail.com> <8D106691E2F8808-2798-932B@webmail-d162.sysops.aol.com> <CAP-guGU4QCHSOnr99hhvksNa8=zm_OZ9bR34HhHv7WCK55sVvw@mail.gmail.com> <5317511D.20506@joelhalpern.com> <CAP-guGVEXDe=YBgGd4Y_kSTsoRH+osfNvqmd+9KwB5pY3C6x-g@mail.gmail.com> <53176AF6.1040308@joelhalpern.com>
From: William Herrin <bill@herrin.us>
Date: Wed, 5 Mar 2014 13:52:54 -0500
X-Google-Sender-Auth: N4Fn9T1XdklTkhERS7Fh46R0wsg
Message-ID: <CAP-guGXiij8hDSA7W-jrRTmMj+Fr0neAk=iz+gvogoqqX=t1yQ@mail.gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/rrg/1mV4U6bBVQDPClo4LTBhSesHSSM
Cc: RRG <rrg@irtf.org>
Subject: Re: [rrg] procedural aggregation
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg/>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Mar 2014 18:53:33 -0000

On Wed, Mar 5, 2014 at 1:20 PM, Joel M. Halpern <jmh@joelhalpern.com>; wrote:
> 1) The set of traffic allowed is more nuanced and varied than just the two
> categories of transit and peer.

Hi Joel,

Barring a specific example, I respectfully disagree. Service providers
often use BGP communities to give transit customers nuanced control
over their routing, however those are still simple transit business
relationships. If you pay someone for access to networks who aren't
paying him, it's a transit link, however nuanced your actual use may
be.

Likewise, peering can be partial (typically regional) or full but
either way it functions as a peering relationship, nothing else.


> 2) If I have understand your description properly, it looks similar to the
> frequent "valley free" assumption.  And there are multiple papers that make
> it clear that the actual paths are not "valley free".  (Sorry, I do not have
> pointers to the papers.  I am not actually a researcher.)

No problem, Google is an old friend. My understanding is that such
valleys are a result of misconfiguration, not an intentional part of
the system. Nor does the desired function of the system depend on
their presence. Do you disagree?

Regards,
Bill Herrin


-- 
William D. Herrin ................ herrin@dirtside.com  bill@herrin.us
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004