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

Dino Farinacci <farinacci@gmail.com> Wed, 21 November 2012 22:01 UTC

Return-Path: <farinacci@gmail.com>
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 76B9821F8528; Wed, 21 Nov 2012 14:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.535
X-Spam-Level:
X-Spam-Status: No, score=-3.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 wY4+CFdZCvqL; Wed, 21 Nov 2012 14:01:18 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id E2D1621F84DF; Wed, 21 Nov 2012 14:01:17 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so3381321pad.31 for <multiple recipients>; Wed, 21 Nov 2012 14:01:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=8XtVZ4N29/ajQjbRF6boaEj6+v/EqX8IbB+wwMAgjWw=; b=WPjcm9eFmqImKzJ1QhL9G8CsG2iGn0XRy0xXiP71bgdCWbUu0uAjQk2ZMhtCFyW7pu OsjxEVEJ/LzWD6YyUv7/KjAX5PLd8Ep2yFwpdYGQt/KdhOM8TJGzrCtaWpySuRVTo4qy Gz7glm+jBqTz6YwCJ25o0WnPxuCMiL18iO6v4qG2qKt2i1/v0XpqVvpdpAeWjby032rD FVFIjIy5KvL0onGgL0E9bOIHWwwhPFf+8hUpmvIyT2y8FMCHuXLrJGAMT3sqcekKSBmW G59e4UkSB/qYfoteA1TdtujmuQBIDnhJh6JtNg+T5FrbuV7qzof9tMCcikVf7Ktd8QZD 5dmA==
Received: by 10.66.72.136 with SMTP id d8mr21110216pav.4.1353535277735; Wed, 21 Nov 2012 14:01:17 -0800 (PST)
Received: from sjc-vpn5-1696.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id v9sm661678paz.6.2012.11.21.14.01.14 (version=SSLv3 cipher=OTHER); Wed, 21 Nov 2012 14:01:15 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>
Date: Wed, 21 Nov 2012 14:01:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A19BAA78-C359-4AB5-8C22-046938B64ACB@gmail.com>
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu> <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>
To: "George, Wes" <wesley.george@twcable.com>
X-Mailer: Apple Mail (2.1499)
Cc: "lisp@ietf.org" <lisp@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@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: Wed, 21 Nov 2012 22:01:18 -0000

Make it an allocation for EIDs and ILNP can use it too.

Dino

On Nov 21, 2012, at 12:25 PM, "George, Wes" <wesley.george@twcable.com> wrote:

>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Noel Chiappa
>> 
>>> If a single permanent allocation that never changes is truly
>> necessary
>> 
>> Allocation != reservation. Nobody is asking for the entire chunk to be
>> _allocated_ (i.e. given out), just that it be _reserved_ for this use.
>> 
> 
> [WEG] You're hairsplitting on semantics in a way that is mostly unhelpful to the discussion at hand. Reserving the block for LISP means that it cannot be used for anything else. Whether that's an IANA reservation or an RIR allocation is really immaterial to the point I was making, which is that if you truly believe we have to identify a block once and for all for LISP that is the correct size to be used permanently and indefinitely, you need a better justification than you've given, and using "experimental" as a justification for not having the details worked out isn't going to be acceptable.
> 
> Regards,
> 
> Wes George
> 
> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp