Re: [lisp] #27: ETR may claim a larger prefix than is delegated to it
"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 18 March 2011 20:21 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B6A33A6A19 for <lisp@core3.amsl.com>; Fri, 18 Mar 2011 13:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.436
X-Spam-Level:
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3tQocJ9uVRA6 for <lisp@core3.amsl.com>; Fri, 18 Mar 2011 13:21:46 -0700 (PDT)
Received: from hermes.out.tigertech.net (hermes.out.tigertech.net [74.114.88.72]) by core3.amsl.com (Postfix) with ESMTP id 28D1B3A6A09 for <lisp@ietf.org>; Fri, 18 Mar 2011 13:21:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 1F8814300DF; Fri, 18 Mar 2011 13:23:16 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-52-147.clppva.btas.verizon.net [71.161.52.147]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 4AF1F4300D2; Fri, 18 Mar 2011 13:23:15 -0700 (PDT)
Message-ID: <4D83BF39.6080707@joelhalpern.com>
Date: Fri, 18 Mar 2011 16:23:21 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: lisp issue tracker <trac+lisp@trac.tools.ietf.org>
References: <060.ac703c54e9577175255bc2d3a9ba9079@trac.tools.ietf.org> <069.a3dd071174a9e4d1edf923b613cf08da@trac.tools.ietf.org>
In-Reply-To: <069.a3dd071174a9e4d1edf923b613cf08da@trac.tools.ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Cc: lisp@ietf.org
Subject: Re: [lisp] #27: ETR may claim a larger prefix than is delegated to it
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2011 20:21:47 -0000
The general issue of authorization for address claims was noted early on as being something for later work, not within scope for the experiment. This is dealt with in greater detail, including some pointers to ideas that we believe will address the over-claiming problem (some initial, and some more complete ideas) are described in http://datatracker.ietf.org/doc/draft-saucez-lisp-security/, which will be discussed in the upcoming meeting and likely be a future work item for the working group. Based on this, I do not see any changes needed to the LISP document to resolve this ticket. Yours, Joel M. Halpern On 3/16/2011 4:02 PM, lisp issue tracker wrote: > #27: ETR may claim a larger prefix than is delegated to it > > Changes (by yakov@…): > > * status: closed => reopened > * resolution: fixed => > > > Comment: > > Before closing the ticket please document how the issue raised by the > ticket is resolved. >
- [lisp] #27: ETR may claim a larger prefix than is… lisp issue tracker
- Re: [lisp] #27: ETR may claim a larger prefix tha… lisp issue tracker
- Re: [lisp] #27: ETR may claim a larger prefix tha… lisp issue tracker
- Re: [lisp] #27: ETR may claim a larger prefix tha… lisp issue tracker
- Re: [lisp] #27: ETR may claim a larger prefix tha… Joel M. Halpern
- Re: [lisp] #27: ETR may claim a larger prefix tha… Vince Fuller
- Re: [lisp] #27: ETR may claim a larger prefix tha… Sam Hartman
- Re: [lisp] #27: ETR may claim a larger prefix tha… Joel M. Halpern
- Re: [lisp] #27: ETR may claim a larger prefix tha… Sam Hartman
- Re: [lisp] #27: ETR may claim a larger prefix tha… Vince Fuller
- Re: [lisp] #27: ETR may claim a larger prefix tha… Joel M. Halpern
- Re: [lisp] #27: ETR may claim a larger prefix tha… Vince Fuller
- Re: [lisp] #27: ETR may claim a larger prefix tha… Fabio Maino
- Re: [lisp] #27: ETR may claim a larger prefix tha… Eliot Lear
- Re: [lisp] #27: ETR may claim a larger prefix tha… lisp issue tracker
- Re: [lisp] #27: ETR may claim a larger prefix tha… Yakov Rekhter
- Re: [lisp] #27: ETR may claim a larger prefix tha… lisp issue tracker
- Re: [lisp] #27: ETR may claim a larger prefix tha… Dino Farinacci
- Re: [lisp] #27: ETR may claim a larger prefix tha… Yakov Rekhter
- Re: [lisp] #27: ETR may claim a larger prefix tha… Dino Farinacci
- Re: [lisp] #27: ETR may claim a larger prefix tha… Yakov Rekhter
- Re: [lisp] #27: ETR may claim a larger prefix tha… Dino Farinacci
- Re: [lisp] #27: ETR may claim a larger prefix tha… Yakov Rekhter
- [lisp] Control Plane Load (was RE: #27: ETR may c… Ross Callon
- Re: [lisp] Control Plane Load (was RE: #27: ETR m… Dino Farinacci
- Re: [lisp] Control Plane Load (was RE: #27: ETR m… Luigi Iannone
- Re: [lisp] Control Plane Load (was RE: #27: ETR m… Luigi Iannone
- Re: [lisp] Control Plane Load (was RE: #27: ETR m… Ross Callon
- Re: [lisp] Control Plane Load (was RE: #27: ETR m… Ross Callon