IETF Logo Mail Archive

Re: [v6ops] [GROW] Deaggregation by large organizations

"Russ White" <russw@riw.us> Thu, 16 October 2014 11:39 UTC

Return-Path: <russw@riw.us>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70BD01AD065; Thu, 16 Oct 2014 04:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level:
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 vV0JrLOkOiip; Thu, 16 Oct 2014 04:39:21 -0700 (PDT)
Received: from server.riw.us (server.riw.us [162.144.32.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 359011A1A66; Thu, 16 Oct 2014 04:39:20 -0700 (PDT)
Received: from 108-78-210-25.lightspeed.chrlnc.sbcglobal.net ([108.78.210.25]:53944 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <russw@riw.us>) id 1XejOn-0007BF-3Z; Thu, 16 Oct 2014 11:39:17 +0000
From: Russ White <russw@riw.us>
To: 'Iljitsch van Beijnum' <iljitsch@muada.com>, v6ops@ietf.org, grow@ietf.org
References: <F5C06CAF-0AD2-4225-8EE7-FC72CE9913F0@muada.com> <755DE4C3-CDDF-41AF-BA9C-E8EC5B4DFC4C@muada.com>
In-Reply-To: <755DE4C3-CDDF-41AF-BA9C-E8EC5B4DFC4C@muada.com>
Date: Thu, 16 Oct 2014 07:39:14 -0400
Message-ID: <011101cfe935$d0e8a600$72b9f200$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQIU7+zpyiakeI4w4w1+I7Zew5YFCQFFO9hQm55hjDA=
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/l8CRTbscdBXbIPjsYMBl37eT6Ms
X-Mailman-Approved-At: Thu, 16 Oct 2014 12:16:35 -0700
Subject: Re: [v6ops] [GROW] Deaggregation by large organizations
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Oct 2014 11:39:24 -0000


> Injecting an aggregate as a point of last resort:
> 
> I think this can be done today and probably is done today. But a document
> describing how to do it would probably be helpful. I'm thinking along the
> following lines:
> 
> The AoLR (Aggregate of Last Resort) service would entail a service
provider
> announcing the aggregate without necessarily providing connectivity
towards
> all the places announcing more specifics covered by the aggregate. So if
ISP A
> announces the AoLR and ISP B provides connectivity to a more specific, ISP
C
> would send traffic to A as per the aggregate and then A would immediately
> hand it over to B.

Or perhaps something simpler would work here -- bounding longest match.

:-)

Russ

v2.23.0 | Report a Bug | By Email