Re: [lisp] Terry Manderson's Discuss on draft-ietf-lisp-eid-block-mgmnt-06: (with DISCUSS)

Brian Haberman <brian@innovationslab.net> Thu, 18 February 2016 12:59 UTC

Return-Path: <brian@innovationslab.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 883901A1AA3; Thu, 18 Feb 2016 04:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 wRIKM75IEXAd; Thu, 18 Feb 2016 04:59:47 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8C271A1A9D; Thu, 18 Feb 2016 04:59:46 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id BC8A3880C2; Thu, 18 Feb 2016 04:59:46 -0800 (PST)
Received: from clemson.jhuapl.edu (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 1B62F328081A; Thu, 18 Feb 2016 04:59:46 -0800 (PST)
To: Luigi Iannone <ggx@gigix.net>, Terry Manderson <terry.manderson@icann.org>
References: <20160218000429.12257.2783.idtracker@ietfa.amsl.com> <8EB22CA3-9933-4193-84E1-BC4AAA4D1F62@gigix.net>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <56C5C040.6090100@innovationslab.net>
Date: Thu, 18 Feb 2016 07:59:44 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <8EB22CA3-9933-4193-84E1-BC4AAA4D1F62@gigix.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="rv867lgPXWIaxEOurV0aEnEqF4LWmqIb9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/fcbkujyIzyPr60fZcy9CD1aGZGU>
Cc: lisp-chairs@ietf.org, draft-ietf-lisp-eid-block-mgmnt@ietf.org, lisp@ietf.org, The IESG <iesg@ietf.org>
Subject: Re: [lisp] Terry Manderson's Discuss on draft-ietf-lisp-eid-block-mgmnt-06: (with DISCUSS)
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 18 Feb 2016 12:59:48 -0000

Hi Luigi,
     To clarify... We got a request from IANA to hold the document since
they "still need to double-check the IANA Considerations internally for
this document."

Regards,
Brian

On 2/17/16 7:26 PM, Luigi Iannone wrote:
> HI Terry,
> 
> would be possible to have more information?
> 
> The latest email from IANA, dated 2nd February said:
> 
>> (BEGIN IANA COMMENTS)
>>
>> IESG/Authors/WG Chairs:
>>
>> IANA has completed its review of draft-ietf-lisp-eid-block-mgmnt-06.txt. If any part of this review is inaccurate, please let us know. 
>>
>> IANA understands that, upon approval of this document, there is a single action which IANA must complete.
>>
>> IANA understands that there is an operational requirement for an EID registration service that ensures uniqueness of EIDs according to the requirements described in Section 5 of the current document. Furthermore, there is an operational requirement for EID registration service that allows a lookup of the contact information of the entity that registered the EID.
>>
>> IANA further understands that RIPE NCC has agreed to run both the registration service documented in this draft for the duration of the experiment.
>>
>> IANA understands that this is the only action required to be completed upon approval of this document.
>>
>> Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.  
>>
>>
>> Thank you,
>>
>> Sabrina Tanamal
>> IANA Specialist
>> ICANN
>>
>> (END IANA COMMENTS)
>>
> 
> There is no question section in that mail.
> 
> Anything I am missing?
> 
> thanks 
> 
> Luigi
> 
> 
> 
>> On 18 Feb 2016, at 01:04, Terry Manderson <terry.manderson@icann.org> wrote:
>>
>> Terry Manderson has entered the following ballot position for
>> draft-ietf-lisp-eid-block-mgmnt-06: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-lisp-eid-block-mgmnt/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> This is a DISCUSS on behalf of the IANA who are questioning the clarity
>> of text and construction of the EID registry service.
>>
>>
>>
>>