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

Geoff Huston <gih@apnic.net> Wed, 08 October 2014 19:39 UTC

Return-Path: <gih@apnic.net>
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 815481A017A for <lisp@ietfa.amsl.com>; Wed, 8 Oct 2014 12:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level:
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, USER_IN_WHITELIST=-100] 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 c-6AbBaVam5g for <lisp@ietfa.amsl.com>; Wed, 8 Oct 2014 12:39:11 -0700 (PDT)
Received: from ia-mailgw.apnic.net (ia-mailgw.apnic.net [IPv6:2001:dd8:a:851::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58B91A0187 for <lisp@ietf.org>; Wed, 8 Oct 2014 12:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer:return-path; bh=EYEs24hHOxT2RoI5V+nVKkhBdeh46dYf6h/9rk+GmVQ=; b=ZUvFx/rFJxk9kszp5pBwHB7uzsHU1RoQxcUGh8lPXg5B/gGgE+0e7muyRzMFLoF+BhZwyaz/+lobk ETMiRlgudJsBy5T7eWy5nimAqBCsEqVezoMtugutezHjGpl0hzF1BbKGozdAZSayRGTRKawwufQZbX eQSeP/2f7BJxFPd4=
Received: from NXMDA1.org.apnic.net (unknown [203.119.101.249]) by ia-mailgw.apnic.net (Halon Mail Gateway) with ESMTPS; Thu, 9 Oct 2014 05:39:05 +1000 (EST)
Received: from [192.252.242.83] (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Thu, 9 Oct 2014 05:39:05 +1000
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <543587CA.5070105@joelhalpern.com>
Date: Thu, 09 Oct 2014 06:38:54 +1100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EBCE7085-C0FF-4DD8-BC6B-797438FD72C2@apnic.net>
References: <543538A8.30405@joelhalpern.com> <20141008111526504441.351ecc0f@sniff.de> <54358282.30905@joelhalpern.com> <20141008114923108851.765e002a@sniff.de> <543587CA.5070105@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/eKAR65xBO19AzhE_mLsuwKsn3DI
Cc: Roger Jorgensen <rogerj@gmail.com>, "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 19:39:14 -0000

Hi,

I thought that after the last round of discussion on this topic we had come to the
point where the WG specified the technical characteristics of the registry
that would be appropriate for support of this experiment, and the IESG and IAB
would direct the IANA as appropriate to operate a registry that was consistent
with this.

I had also thought that in this dialogue between the IESG, IAB and the IANA, the 
RIRs may well be in a position to provide registry support that would be entirely
consistent with the technical requirements to support this experiment.

So from that perspective I had thought that this draft was clear in intent
and suitable to support the experiment. 


regards,

   Geoff

 
On 9 Oct 2014, at 5:51 am, Joel M. Halpern <jmh@joelhalpern.com> wrote:

> It would seem to me to be rather odd to spend time working out an agreement for what we want to do with a permanent allocation.  We are defining the rules for the experimental allocation.
> 
> Is there a specific text change that would make that clear enough to alleviate your concern?
> 
> Yours,
> Joel
> 
> On 10/8/14, 2:49 PM, Marc Binderberger wrote:
>> Hello Joel,
>> 
>>> The document is very clear that any potential transition to permanent
>>> allocation would have to be discussed and coordianted with multiple
>>> parties, including the RIRs.
>> 
>> Correct, the document is saying this. Maybe I have a different idea of "very
>> clear" though, all it says there must be a discussion.
>> I would prefer a clear statement that these policies are ending either when
>> the EID block experiment ends (obvious) or when the EID block turns into
>> something permanent.
>> 
>> 
>>> Equally, until such time as a permanent allocation is made, the document is
>>> not declaring the RIRs to be "the " allocation authority.
>> 
>> Agree - and I'm not making such a statement.
>> 
>> 
>>> If the RIRs can
>>> and wish to engage in LISP EID allocation in accordance with the policy,
>>> they can.  But the document does not promise the role to them.
>> 
>> If the document deviates from how RIRs operate then the document should not
>> be valid at the point any LISP EID blocks becomes permanent. My opinion.
>> 
>> 
>>> It may, or may not, make sesen if and when we do a permanent allocation to
>>> specify a role for the RIRs.  That however will be negotiated then.
>> 
>> This "may or may not" is the vagueness I mentioned and why I express my lack
>> of comfort with the document.
>> 
>> 
>> Let me word it differently: the EID block as a sandbox for a large-scale,
>> real-life experiment to learn how LISP becomes (or is already)
>> production-ready for the Internet - great idea. Beyond that I don't see a
>> need for anything special or different for LISP and we have working
>> procedures how to allocate/assign address space. This is also the promise,
>> that LISP is blending in.
>> 
>> 
>> Regards, Marc
>> 
>> 
>> 
>>> On 10/8/14, 2:15 PM, Marc Binderberger wrote:
>>>> Hello Joel, authors and lisp list,
>>>> 
>>>> while I think the document is overall reasonably written it has one
>>>> problem:
>>>> it's bound to an proposed EID address block that has no guaranteed end of
>>>> life.
>>>> 
>>>> If this experiment would clearly terminate after 3+3 years then I would say
>>>> it's good to go. It's not the way the RIRs have written their documents
>>>> but I
>>>> think that's okay for a experiment and a 6 year time frame. But the
>>>> proposals
>>>> allow the requested /32 EID block to be turned into something permanently.
>>>> For a permanent EID block it's reasonable to assume the RIRs deal with the
>>>> allocation/assignment work ([1]) and then the document would need more
>>>> alignment with RIR policy documents. A simple example would be the
>>>> language,
>>>> "allocation" is used throughout while "assignment" is only mentioned in the
>>>> Introduction. I checked both ARIN and RIPE and it's clearly defined there.
>>>> It's also going too far in telling IANA to not have a regional policy.
>>>> 
>>>> 
>>>> So in short (and in all honesty): not feeling comfortable with the document
>>>> in the context of a potential permanent impact of the document.
>>>> 
>>>> 
>>>> Regards, Marc
>>>> 
>>>> [1]: if the proposal is to have finally an additional authority beside the
>>>> RIRs for address allocation then I would reject the proposal.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Wed, 08 Oct 2014 09:14:16 -0400, Joel M. Halpern 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
>>>>> 
>>>> 
>>> 
>>