Re: [lisp] WG Last Call on draft-ietf-lisp-eid-block-mgmnt-02

Dino Farinacci <farinacci@gmail.com> Wed, 08 October 2014 17:16 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF0AC1ACD0D for <lisp@ietfa.amsl.com>; Wed, 8 Oct 2014 10:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9x-VzbB_dL93 for <lisp@ietfa.amsl.com>; Wed, 8 Oct 2014 10:16:23 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF18F1ACD05 for <lisp@ietf.org>; Wed, 8 Oct 2014 10:16:20 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id j107so7305186qga.2 for <lisp@ietf.org>; Wed, 08 Oct 2014 10:16:20 -0700 (PDT)
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; bh=U6wQREEimsRuT3niyyXyiCG1XEqNH/uDCKESaveXPcc=; b=UHhpCaX8H10QS0BjcRHeMMOrBukpOYvuHptdorbgilE4BV6I0aAnx1+emK8yK6cMoP tTXQ4u9ftbXTNL2nKgZeeSc9NrSEoG1GXBnc5RarBCMItuk3WUY8xPpOYUj8QOKwhb4J ovBYrsqYlQUQ5mRQt04kU1pd+ze/qN+6HH4vfiSEB9er2ezq1SVDZ7TinfUGup2egDHK JH0wkvnW5u3D89wQRhbcXKdMvgkY5r9JvtXCCOC8kVBSaogv2EYw8pwuRdCzSjBvZGf2 kue2dGKs44Ql7BXHUVd2J+BILlUTbDeLNTG8ayBlKS87AoknaxkD6ASbdYzulAJr4LR9 nUfA==
X-Received: by 10.224.71.206 with SMTP id i14mr3431300qaj.100.1412788578674; Wed, 08 Oct 2014 10:16:18 -0700 (PDT)
Received: from [192.168.1.32] (pool-72-92-14-140.phlapa.east.verizon.net. [72.92.14.140]) by mx.google.com with ESMTPSA id u18sm412457qac.41.2014.10.08.10.16.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Oct 2014 10:16:18 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <62831524-AB42-461D-B129-50CB799F2936@terrym.net>
Date: Wed, 08 Oct 2014 10:15:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8002309D-50E7-4E31-9572-A39665C76883@gmail.com>
References: <543538A8.30405@joelhalpern.com> <62831524-AB42-461D-B129-50CB799F2936@terrym.net>
To: Terry Manderson <terry@terrym.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/0wn00WbSGA6G6K7ALE_Uv9Xz5v0
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] WG Last Call on draft-ietf-lisp-eid-block-mgmnt-02
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 08 Oct 2014 17:16:28 -0000

I too read the draft and only have a couple of comments. But first a question, can you remind me why this effort is separated out into 2 documents?

Comments:

> The allocation of EID prefixes MUST be done under the following
>    policies:

Can you make it clear that this is for both IPv4 and IPv6 prefixes? That is, if you believe that is true. Or if there won't be enough IPv4 prefixes, then you may want to say most of these address policies are applicable to IPv6 prefixes.

>  6.  When an allocation is freed because of non-renewal or the
>        termination of an experiment, the address space is returned to
>        the global pool of free EID prefixes.  This freed allocation MUST
>        NOT be announced through registration on Map Servers in the LISP
>        mapping system for at least 72 hours to ensure expiration of all
>        cached map entries in the global LISP infrastructure.

I think you should also say these prefixes need to be deconfigured from the Map-Servers. Otherwise, what will be returned to Map-Resolvers using the LISP-DDT will be "configured-but-not-registered" (MS_NOT_REGISTERED) return codes in Map-Referrals. That will mislead operators that the EID-prefix is valid but just not currently registered. You want Map-Resolvers to return to ITRs/PITRs/RTRs "native-forward" since the reuse of the prefix could be used normally with a BGP advertisement associated with it.

Dino

On Oct 8, 2014, at 6:42 AM, Terry Manderson <terry@terrym.net> wrote:

> I have read the draft, and in my reading I could not see any text that I object to, nor any aspect that needed correction nor fixing.
> 
> I suspect the IANA Considerations section will end up having some work done on it - but right now I'm not sure in what direction that may take.
> 
> I think it is well constructed and ready to hand to the AD.
> 
> Cheers
> Terry
> 
> On 8 Oct 2014, at 11:14 pm, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
>> All,
>> 
>> The work on the draft-ietf-lisp-eid-block-mgmnt-02 seems done and the authors requested a work group last call.
>> 
>> This email starts a 14 day WG last call, to end CoB PDT October 22, 2014.
>> 
>> You will find the document here:
>> http://www.ietf.org/id/draft-ietf-lisp-eid-block-mgmnt-02.txt
>> 
>> Please review this WG document.  Let the working group know if you agree that it is ready for handing to the AD, or if you see issues with it. If you see issues, please be as specific as possible about the problems, and if possible suggest text to resolve them.
>> 
>> Yours,
>> Joel
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp