[RAM] Re: [RRG] How to avoid black-hole in LISP-CONS with aggregation mechanism?
Lixia Zhang <lixia@CS.UCLA.EDU> Mon, 27 August 2007 22:01 UTC
Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IPmeh-0005XI-2h; Mon, 27 Aug 2007 18:01:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IPmef-0005Te-P8 for ram@iab.org; Mon, 27 Aug 2007 18:01:53 -0400
Received: from kiwi.cs.ucla.edu ([131.179.128.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPmee-00070v-Av for ram@iab.org; Mon, 27 Aug 2007 18:01:53 -0400
Received: from [192.168.100.152] (p1199-ipbf308kyoto.kyoto.ocn.ne.jp [122.22.1.199]) by kiwi.cs.ucla.edu (8.13.8+Sun/8.13.8/UCLACS-6.0) with ESMTP id l7RM1URX015395; Mon, 27 Aug 2007 15:01:30 -0700 (PDT)
In-Reply-To: <000501c7e887$43bd58e0$5e0c6f0a@china.huawei.com>
References: <000501c7e887$43bd58e0$5e0c6f0a@china.huawei.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <2CAA53D5-D9B9-43B8-B15D-3288D47C7797@cs.ucla.edu>
Content-Transfer-Encoding: 7bit
From: Lixia Zhang <lixia@CS.UCLA.EDU>
Date: Mon, 27 Aug 2007 15:01:33 -0700
To: Xu Xiaohu <xuxh@huawei.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: ram@iab.org
Subject: [RAM] Re: [RRG] How to avoid black-hole in LISP-CONS with aggregation mechanism?
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org
Dear Steven XU, Please do not double-post to both RAM and RRG lists. Per my earlier message, please carry out this discussion on RRG list. Lixia (RAM moderator hat on) PS: to subscribe RRG list, send mail to rrg-request@psg.com with the word "subscribe" in the body of your email. On Aug 27, 2007, at 1:50 AM, Xu Xiaohu wrote: > Hi all, > I have a doubt about how to avoid black-hole in LISP-CONS with > aggregation > mechanism? My doubt is explained as follows: > +---------+ 1.0.0.0/8 CDR-1 > | CDR-3 | > +----+---\+ 1.1.0.0/16 CDR-2 > / \\ > Push 1.0.0.0/8 / \ Push 1.1.0.0/16 > // \\ > +----/---+ 1.1.0.0/16 CAR-1 +--\-----+ > | CDR-1 | 1.2.0.0/16 CAR-2 | CDR-2 | 1.1.0.0/16 > CAR-3 > +---+--\-+ +---+----+ > | \\ | > | \\ Push 1.2.0.0/16 |Push 1.1.0.0/16 > Push 1.1.0.0/16 \\ | > | \\ | > +---+----+ +---\------+ +----+----+ > | CAR-1 | | CAR-2 | | CAR-3 | > +--------+ +----------+ +---------+ > 1.1.0.0/24 1.2.0.0/24 1.1.2.0/24 > 1.1.1.0/24 1.2.1.0/24 1.1.3.0/24 > > As shown in the above figure, CAR-1 has two EID-prefixes, > 1.1.0.0/24 and > 1.1.1.0/24, and it sends an aggregated EID-prefix 1.1.0.0/16 to > CDR-1. CAR-2 > also sends an aggregated EID-prefix 1.2.0.0/16 to CDR-1. CDR-1 > sends an > aggregated EID-prefix 1.0.0.0/8 to its parent CDR, CDR-3. > CAR-3 has two EID-prefixes, 1.1.2.0/24 and 1.1.3.0/24, and it sends an > aggregated EID-prefix 1.1.0.0/16 to CDR-2. CDR-2 sends a EID-prefix > 1.1.0.0/16 to its parent CDR, CDR-3. > Now CDR-3 has two EID-prefixes, one is 1.0.0.0/8 with a nexthop of > CDR-1, > the other is 1.1.0.0/16 with a nexthop of CDR-2. If CDR-3 receives > a mapping > request for longest-matching entry for 1.1.1.1, it will result in a > black-hole. > > How to avoid it? Use the same aggregation granularity within the > same level? > Or aggregation will not be available until all the component EID- > prefixes > exists in the EID-prefix database of the aggregation attempter? > > Best regards, > Steven XU > > > > -- > to unsubscribe send a message to rrg-request@psg.com with the > word 'unsubscribe' in a single line as the message text body. > archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg _______________________________________________ RAM mailing list RAM@iab.org https://www1.ietf.org/mailman/listinfo/ram
- [RAM] How to avoid black-hole in LISP-CONS with a… Xu Xiaohu
- [RAM] How to avoid black-hole in LISP-CONS with a… Xu Xiaohu
- Re: [RAM] How to avoid black-hole in LISP-CONS wi… Noel Chiappa
- Re: [RAM] How to avoid black-hole in LISP-CONS wi… Dino Farinacci
- [RAM] Re: [RRG] How to avoid black-hole in LISP-C… Lixia Zhang
- Re: [RAM] How to avoid black-hole in LISP-CONS wi… Scott Brim