Dino,
But who are the registries? The RIRs? Large ISPs? IANA? I think you
should specify clearly either: what a registry is or that is not defined
yet.
Point taken on "This draft is purely a draft to REQUEST space. There
will need to be a deployment guide on how to allocate EIDs, in general."
But then it should be written somewhere in the document.
Although it could be enough only to clearly say that a deployment guide
would define allocation guides in the future; for the sake of clarity
and usefulness (now, after the space is allocated by IANA it will be
there left unused because there is not a clearly indication how is going
to be used) I would recommend to discuss how the space is going to be
allocated.
Regards
as
On 15/11/2012 16:25, Dino Farinacci wrote:
>> Luigi,
>>
>> On 15/11/2012 12:33, Luigi Iannone wrote:
>>>
>>> On 15 Nov. 2012, at 10:43 , Sander Steffann <[email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>>> I have to ask, who can request an netblock from this address space and
>>>>> from where?
>>>>> I might be blind but I couldn't find it mentioned anywhere.
>>>>
>>>> Good question. Will there be a central registry, or will parts of the
>>>> space be delegated to i.e. LISP based ISPs?
>>>>
>>>
>>> Hi Sander,
>>>
>>> no central registry has been ever discussed, was more about delegated the
>>> space to LISP ISPs.
>>
>>
>> How are you going to allocate space to ISPs?
>
> This is PI space. The registries will take portions of this space to allocate
> to end devices. This is endpoint ID space. ISPs will continue to allocate
> addresses for LISP RLOCs. And they will have to allocate orders of magnitude
> less address space now.
>
>> Who is going to track the allocations made to ISPs, how are they going
>> to be published, what are the requirements to ask for space, what data
>> needs to be registered, where I can see allocations data?
>
> Registries will track allocations to end sites.
>
>> You asked George why the document is not ready to be published. Well,
>> the undocumented rules on how the space is going to be managed is one
>> important reason IMHO.
>
> This draft is purely a draft to REQUEST space. There will need to be a
> deployment guide on how to allocate EIDs, in general.
>
> Dino
>
>>
>> Regards,
>> as
>>
>>
>>>
>>> Luigi
>>>
>>>
>>>> - Sander
>>>>
>>>> _______________________________________________
>>>> lisp mailing list
>>>> [email protected]
>>>> https://www.ietf.org/mailman/listinfo/lisp
>>>
>>> _______________________________________________
>>> lisp mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/lisp
>>>
>> _______________________________________________
>> lisp mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
