On 31/03/2017 03:50, Ted Lemon wrote:
> On Mar 30, 2017, at 9:45 AM, Michael Richardson wrote:
>> It would hand out space via HNCP, and if it ran out of space, get more.
>
> This can also be done with DHCP.
Indeed. I'm not trying to force the Anima approach, just pointing out that
it will be ava
Pierre Pfister wrote:
> Absolutely. RFC7695 Applicability Statement (Section 3.) explains that
> the algorithm can be used as
> long as participating nodes gets configured with an eventually
> consistent set of non-overlaping prefixes,
> which are then used to carve-out sub-pr
On Mar 30, 2017, at 9:45 AM, Michael Richardson wrote:
> It would hand out space via HNCP, and if it ran out of space, get more.
This can also be done with DHCP.
___
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima
Juliusz Chroboczek wrote:
>>> Could you please clarify what you mean by "negotiate"? Current HNCP
>>> implementations are provided with a bunch of External Prefixes, which
they
>>> then carve into /64, one per prefix. Are you envisioning a scenario
where
>>> the HNCP implement
> Le 29 mars 2017 à 18:04, Brian E Carpenter a
> écrit :
>
> On 30/03/2017 11:14, Mark Townsley (townsley) wrote:
>>
>>> On Mar 29, 2017, at 10:04 AM, Michael Richardson
>>> wrote:
>>>
>>>
>>> This discussion started in a private thread, so I'll try to bring people
>>> up-to-date by repeat
On 30/03/2017 11:14, Mark Townsley (townsley) wrote:
>
>> On Mar 29, 2017, at 10:04 AM, Michael Richardson
>> wrote:
>>
>>
>> This discussion started in a private thread, so I'll try to bring people
>> up-to-date by repeating and moving around text.
>>
>> The ANIMA GRASP reference problem Autono
On 30/03/2017 10:04, Juliusz Chroboczek wrote:
>> There's already a thing called an HNCP agent. Why couldn't
>> it be enhanced to negotiate with an upstream ASA for resources?
>
> Could you please clarify what you mean by "negotiate"? Current HNCP
> implementations are provided with a bunch of Ex
> On Mar 29, 2017, at 10:04 AM, Michael Richardson
> wrote:
>
>
> This discussion started in a private thread, so I'll try to bring people
> up-to-date by repeating and moving around text.
>
> The ANIMA GRASP reference problem Autonomic Service Agent (ASA), is
> to do distributed prefix alloc
>> Could you please clarify what you mean by "negotiate"? Current HNCP
>> implementations are provided with a bunch of External Prefixes, which they
>> then carve into /64, one per prefix. Are you envisioning a scenario where
>> the HNCP implementation actually performs active negotiation on its
Juliusz Chroboczek wrote:
>> There's already a thing called an HNCP agent. Why couldn't
>> it be enhanced to negotiate with an upstream ASA for resources?
> Could you please clarify what you mean by "negotiate"? Current HNCP
> implementations are provided with a bunch of Externa
> There's already a thing called an HNCP agent. Why couldn't
> it be enhanced to negotiate with an upstream ASA for resources?
Could you please clarify what you mean by "negotiate"? Current HNCP
implementations are provided with a bunch of External Prefixes, which they
then carve into /64, one pe
brian> But if the CE includes a little autonomic service agent (ASA) which
brian> is in the ISP's security domain (not the SOHO domain), it can act for
brian> HNCP to solicit address space from the ISP. That's the southern side
brian> of the CASM model and the northern side of HNCP.
HNCP just does
12 matches
Mail list logo
