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

"George, Wes" <wesley.george@twcable.com> Wed, 21 November 2012 20:25 UTC

Return-Path: <wesley.george@twcable.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 798EB21F85FC; Wed, 21 Nov 2012 12:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.409
X-Spam-Level:
X-Spam-Status: No, score=-0.409 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 P39HwDp9I7ew; Wed, 21 Nov 2012 12:25:10 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id B08F321F85DF; Wed, 21 Nov 2012 12:25:09 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.83,294,1352091600"; d="scan'208";a="456095235"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 21 Nov 2012 15:24:51 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 21 Nov 2012 15:25:08 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
Date: Wed, 21 Nov 2012 15:25:12 -0500
Subject: RE: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Topic: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
Thread-Index: Ac3IEeLx7gw52o/PQTOjMBiBnBLqwwAE4fQg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD592303385FBF7A@PRVPEXVS15.corp.twcable.com>
References: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
In-Reply-To: <20121121175836.EE11B18C0D3@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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 20:25:10 -0000

> 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.