Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC

"Bert Wijnen (IETF)" <bertietf@bwijnen.net> Thu, 15 November 2012 14:46 UTC

Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA98321F88B7; Thu, 15 Nov 2012 06:46:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, 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 q0-FHuNo6W21; Thu, 15 Nov 2012 06:46:57 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 2241B21F8928; Thu, 15 Nov 2012 06:46:57 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TZ0iT-00018J-Op; Thu, 15 Nov 2012 15:46:54 +0100
Received: from cat.ripe.net ([193.0.1.249] helo=guest165.guestnet.ripe.net) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TZ0iT-0004Ec-EU; Thu, 15 Nov 2012 15:46:53 +0100
Message-ID: <50A5005D.2080704@bwijnen.net>
Date: Thu, 15 Nov 2012 15:46:53 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Luigi Iannone <ggx@gigix.net>
Subject: Re: Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
References: <50A4CA14.9010909@bwijnen.net> <79AB8650-BB45-4F56-B7C2-B1D36DF5ADDD@gigix.net>
In-Reply-To: <79AB8650-BB45-4F56-B7C2-B1D36DF5ADDD@gigix.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121115 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points: -2.9 points pts rule name description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd49c4d59811551b7ded1ee84cc640e623a
Cc: lisp@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 14:46:58 -0000

Nice to try and keep it short.

But I was hoping for some more detail and explanation.
I have not followed the discussions (if any) in the WG
so I may be missing the reasons why you need this much
space. I would hope that the WG (if they have consensus
(which may be something different than "the WG felt"))
could elaborate or summarize the discussions that lead
to the conclusion that this amount of space is needed
and makes sense.

Pointers to the WG mlist discussions where the pros
and cons of various prefixes sizes are discussed or
summarize would also be welcome.

Bert

On 11/15/12 3:46 PM, Luigi Iannone wrote:
> Hi Bert,
>
> On 15 Nov. 2012, at 11:55 , Bert Wijnen (IETF) <bertietf@bwijnen.net> wrote:
>
> [snip]
>>
>> So it is not asking just a /16 but also asking for reservation of a /12.
>>
>> Pretty big space.
>>
>> And in the list of reasons, I mainly read that it is "sufficiently large",
>> but not much about why it needs to be this big. Why would a smaller
>> allocation not be sufficient?
>>
>
> Well, to keep it short, the WG felt that /16 is the "right size", and that if the growth of LISP would be so important as to need a bigger space would be nice to have it contiguous (so implementations can just change the prefix length).
>
> Luigi
>
>> Bert
>
>